Sie sind auf Seite 1von 1358

Title page

Alcatel-Lucent 9153
Operation & Maintenance Center Radio | B12
PM Counters Dictionary
9YZ-03803-1635-TQZZA
Issue 13 | September 2014
Legal notice

Legal notice

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective
owners.

The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright © 2014 Alcatel-Lucent. All rights reserved.
Contents

About this document


Purpose .................................................................................................................................................................................... lxxxiii
lxxxiii

What's new ............................................................................................................................................................................. lxxxiii


lxxxiii

Intended audience ................................................................................................................................................................ lxxxiii


lxxxiii

Supported systems ............................................................................................................................................................... lxxxiii


lxxxiii

How to use this document ................................................................................................................................................ lxxxiv


lxxxiv

How to comment .................................................................................................................................................................. lxxxiv


lxxxiv

Part I: BSC-TYPE 1 - Traffic measurements

1 Handover

TCH

Overview ...................................................................................................................................................................................... 1-1


1-1

C710 - NB_TCH_OUT_HO_REQ_TRX ........................................................................................................................ 1-1


1-1

2 Quality of Service

Directed Retry

Overview ...................................................................................................................................................................................... 2-1


2-1

C717a - NB_INC_IDR_SUCC_TRX ............................................................................................................................... 2-1


2-1

Established Phase

Overview ...................................................................................................................................................................................... 2-3


2-3

C137 - NB_SDCCH_DROP_EST_PHAS_BSS_PB .................................................................................................. 2-3


2-3

C138 - NB_SDCCH_DROP_EST_PHAS_RLF ........................................................................................................... 2-4


2-4

C14c - NB_TCH_DROP_EST_PHAS_BSS_PB ......................................................................................................... 2-4


2-4

C162a - NB_TCH_DROP_DTAP_EST_PHAS_RLF ................................................................................................ 2-5


2-5

C162b - NB_TCH_DROP_DTAP_EST_PHAS_BSS_PB ........................................................................................ 2-6


2-6
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R iii
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
C162c - NB_TCH_DROP_DTAP_EST_PHAS_REM_TRANS_FAIL ............................................................... 2-8
2-8

C736 - NB_TCH_DROP_EST_PHAS_RLF_TRX ..................................................................................................... 2-8


2-8

C739 - NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX ................................................................... 2-9


2-9

Handover

Overview ................................................................................................................................................................................... 2-10


2-10

C03 - NB_OUT_SDCCH_HO_SUCC ........................................................................................................................... 2-10


2-10

C07 - NB_SDCCH_DROP_OUT_HO ........................................................................................................................... 2-11


2-11

C10 - NB_INC_SDCCH_HO_SUCC ............................................................................................................................. 2-11


2-11

C14a - NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB ............................................................................. 2-12


2-12

C621 - NB_TCH_DROP_OUT_HO_EXEC_TRX ................................................................................................... 2-14


2-14

C711 - NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX ...................................................................................... 2-14


2-14

C712 - NB_TCH_OUT_HO_SUCC_TRX .................................................................................................................. 2-15


2-15

C713 - NB_TCH_OUT_HO_FAIL_REV_TRX ........................................................................................................ 2-16


2-16

C714 - NB_TCH_OUT_HO_FAIL_NO_REV_TRX ............................................................................................... 2-17


2-17

C717b - NB_INC_TCH_HO_SUCC_TRX .................................................................................................................. 2-17


2-17

Speech

Overview ................................................................................................................................................................................... 2-19


2-19

C170 - NB_CALL_TFO ...................................................................................................................................................... 2-19


2-19

C171 - NB_TFO_CODEC_REQ ...................................................................................................................................... 2-20


2-20

Telecom Procedure (QoS)

Overview ................................................................................................................................................................................... 2-21


2-21

C01 - NB_IMM_ASS_SUCC_MT .................................................................................................................................. 2-22


2-22

C02 - NB_IMM_ASS_SUCC_MO ................................................................................................................................. 2-22


2-22

C02a - NB_IMM_ASS_SUCC_MO_LOC_UPD ...................................................................................................... 2-23


2-23

C02b - NB_IMM_ASS_SUCC_MO_SMS .................................................................................................................. 2-23


2-23

C02c - NB_IMM_ASS_SUCC_MO_SUP_SERV ..................................................................................................... 2-24


2-24

....................................................................................................................................................................................................................................
iv Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
C02d - NB_IMM_ASS_SUCC_MO_FOLLOW_ON .............................................................................................. 2-24
2-24

C02e - NB_IMM_ASS_SUCC_MO_CM_REEST ................................................................................................... 2-25


2-25

C02f - NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW ................................................................................... 2-26


2-26

C02g - NB_IMM_ASS_SUCC_MO_IMSI_DETACH ........................................................................................... 2-26


2-26

C02h - NB_IMM_ASS_SUCC_MO_CALL_EST .................................................................................................... 2-27


2-27

C02i - NB_IMM_ASS_SUCC_MO_LCS .................................................................................................................... 2-27


2-27

C04 - NB_IMM_ASS_PREP_FAIL_CONG ............................................................................................................... 2-28


2-28

C149 - NB_IMM_ASS_EXEC_FAIL_RADIO .......................................................................................................... 2-28


2-28

C161a - NB_DTAP_MO_NOR_ASS_SUCC ............................................................................................................. 2-29


2-29

C161b - NB_DTAP_MT_NOR_ASS_SUCC .............................................................................................................. 2-29


2-29

C612a - NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE ................................................................................. 2-30


2-30

C612b - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL ............................................................................ 2-31


2-31

C612c - NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP ........................................................................................ 2-31


2-31

C612d - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ ................................................................................ 2-32


2-32

C718 - NB_TCH_NOR_ASS_SUCC_TRX ................................................................................................................ 2-33


2-33

C746b - NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX .............................................................................. 2-34


2-34

C812 - NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS ............................................................................. 2-34


2-34

C901 - NB_Suspend_Resume_req .................................................................................................................................. 2-35


2-35

C902 - Nb_Suspend_fail ..................................................................................................................................................... 2-36


2-36

C903 - Nb_Suspend_succ ................................................................................................................................................... 2-36


2-36

3 Resource Availability & Usage

Resource Allocation & Management

Overview ...................................................................................................................................................................................... 3-1


3-1

C442 - NB_TIMES_TRAF_DETECTED_HIGH ........................................................................................................ 3-2


3-2

C443 - NB_TIMES_TRAF_DETECTED_LOW ......................................................................................................... 3-2


3-2

C701a - NB_TCH_FR_REQ ................................................................................................................................................ 3-3


3-3

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R v
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
C701b - NB_TCH_DR_REQ ............................................................................................................................................... 3-3
3-3

C701c - NB_TCH_DR_EFR_REQ .................................................................................................................................... 3-4


3-4

C701d - NB_TCH_AMR_REQ .......................................................................................................................................... 3-4


3-4

C701e - NB_TCH_DATA_REQ ......................................................................................................................................... 3-5


3-5

C702a - NB_TCH_NOR_FR_ALLOC ............................................................................................................................ 3-5


3-5

C702b - NB_TCH_NOR_HR_ALLOC ........................................................................................................................... 3-6


3-6

C702c - NB_TCH_NOR_EFR_ALLOC ......................................................................................................................... 3-6


3-6

C704a - NB_TCH_NOR_AMR_FR_ALLOC ............................................................................................................... 3-7


3-7

C704b - NB_TCH_NOR_AMR_HR_ALLOC .............................................................................................................. 3-7


3-7

C705 - NB_TCH_NOR_DATA_ALLOC ........................................................................................................................ 3-8


3-8

C706 - NB_EGSM_MS_ACCESS_EXCEPT_LU ...................................................................................................... 3-8


3-8

4 Traffic Load

Telecom Procedure (Traffic Load)

Overview ...................................................................................................................................................................................... 4-1


4-1

C13a - NB_TCH_NOR_ASS_QUEUED ........................................................................................................................ 4-2


4-2

C13b - NB_INC_EXT_TCH_HO_QUEUED ............................................................................................................... 4-2


4-2

C147 - NB_INC_SDCCH_HO_ALLOC ......................................................................................................................... 4-3


4-3

C148 - NB_IMM_ASS_ALLOC ........................................................................................................................................ 4-4


4-4

C15a - NB_INC_IDR_ALLOC ........................................................................................................................................... 4-4


4-4

C15b - NB_INC_TCH_HO_ALLOC ............................................................................................................................... 4-5


4-5

C703 - NB_TCH_NOR_ASS_ALLOC_TRX ............................................................................................................... 4-5


4-5

C850 - NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL ........................................................................ 4-6


4-6

Part II: BSC-TYPE 2 - Resource availability measurements

5 Resource Availability & Usage

Channel

Overview ...................................................................................................................................................................................... 5-1


5-1

....................................................................................................................................................................................................................................
vi Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
C141 - AV_NB_TCH_QUEUED ........................................................................................................................................ 5-2
5-2

C24 - AV_NB_NOT_AVAIL_TRX_TS ........................................................................................................................... 5-2


5-2

C250 - AV_NB_AVAIL_TCH .............................................................................................................................................. 5-3


5-3

C26 - AV_NB_AVAIL_SDCCH .......................................................................................................................................... 5-3


5-3

C27 - AV_NB_AVAIL_CCCH ............................................................................................................................................. 5-4


5-4

C28a - AV_NB_BUSY_CS_TS ........................................................................................................................................... 5-4


5-4

C29a - NB_MAX_SIMUL_BUSY_CS_TS ................................................................................................................... 5-5


5-5

C30 - AV_NB_BUSY_SDCCH ........................................................................................................................................... 5-6


5-6

C31 - NB_MAX_SIMUL_BUSY_SDCCH ................................................................................................................... 5-6


5-6

C320a - AV_NB_IDLE_TCH_INTERF_BAND1 ........................................................................................................ 5-7


5-7

C320b - AV_NB_IDLE_TCH_INTERF_BAND2 ....................................................................................................... 5-8


5-8

C320c - AV_NB_IDLE_TCH_INTERF_BAND3 ........................................................................................................ 5-9


5-9

C320d - AV_NB_IDLE_TCH_INTERF_BAND4 ..................................................................................................... 5-10


5-10

C320e - AV_NB_IDLE_TCH_INTERF_BAND5 ..................................................................................................... 5-11


5-11

C34 - TIME_ALL_AVAIL_TRX_TS_BUSY ............................................................................................................. 5-12


5-12

C803 - TIME_SDCCH_CONGESTION ....................................................................................................................... 5-12


5-12

Part III: BSC-TYPE 3 - Resource usage on CCCH channel measurements

6 Traffic Load

Radio Channel (Traffic Load)

Overview ...................................................................................................................................................................................... 6-1


6-1

C8a - NB_PAGING_CMD .................................................................................................................................................... 6-1


6-1

C8b - NB_IMM_ASS_CMD ................................................................................................................................................ 6-2


6-2

C8c - NB_CHAN_REQD ...................................................................................................................................................... 6-2


6-2

C8d - NB_IMM_ASS_REJ ................................................................................................................................................... 6-3


6-3

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R vii
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
Part IV: BSC-TYPE 4 - Resource usage on SDCCH channel measurements

7 Resource Availability & Usage

Channel

Overview ...................................................................................................................................................................................... 7-1


7-1

C39 - NB_TIMES_SDCCH_BUSY .................................................................................................................................. 7-1


7-1

8 Traffic Load

Radio Channel (Traffic Load)

Overview ...................................................................................................................................................................................... 8-1


8-1

C40 - TIME_SDCCH_BUSY .............................................................................................................................................. 8-1


8-1

Part V: BSC-TYPE 5 - Resource usage on TCH channel measurements

9 Resource Availability & Usage

Channel

Overview ...................................................................................................................................................................................... 9-1


9-1

C370a - NB_TCH_FR_ALLOC ......................................................................................................................................... 9-1


9-1

C370b - NB_TCH_HR_ALLOC ........................................................................................................................................ 9-2


9-2

10 Traffic Load

Radio Channel (Traffic Load)

Overview ................................................................................................................................................................................... 10-1


10-1

C380a - TIME_FR_TCH_BUSY ..................................................................................................................................... 10-1


10-1

C380b - TIME_HR_TCH_BUSY .................................................................................................................................... 10-2


10-2

C381a - TIME_FR_TCH_BUSY_BY_MULTIBAND_MS .................................................................................. 10-3


10-3

C381b - TIME_HR_TCH_BUSY_BY_MULTIBAND_MS ................................................................................. 10-5


10-5

....................................................................................................................................................................................................................................
viii Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
Part VI: BSC-TYPE 6 - TCH handover measurements

11 Handover

SDCCH+TCH

Overview ................................................................................................................................................................................... 11-1


11-1

C440 - NB_TCH_HO_ATPT_23_TrafHandover ....................................................................................................... 11-1


11-1

TCH

Overview ................................................................................................................................................................................... 11-3


11-3

C220 - NB_INC_EXT_TCH_HO_REQ ........................................................................................................................ 11-5


11-5

C221 - NB_INC_EXT_TCH_HO_ATPT ...................................................................................................................... 11-5


11-5

C230 - NB_INC_INT_TCH_HO_REQ ......................................................................................................................... 11-6


11-6

C231 - NB_INC_INT_TCH_HO_ATPT ....................................................................................................................... 11-6


11-6

C270 - NB_INTRA_TCH_HO_REQ ............................................................................................................................. 11-7


11-7

C271 - NB_INTRA_TCH_HO_ATPT ........................................................................................................................... 11-7


11-7

C411 - NB_OUT_INT_TCH_HO_IDR_IN_ZONE_REQ ..................................................................................... 11-8


11-8

C412 - NB_OUT_INT_TCH_HO_IDR_IN_ZONE_EXEC_FAIL ..................................................................... 11-8


11-8

C41b - NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH ............................................................................... 11-9


11-9

C42 - NB_INC_EXT_TCH_HO_SUCC ..................................................................................................................... 11-10


11-10

C43 - NB_INC_EXT_TCH_HO_EXEC_FAIL_MS_ACCESS ......................................................................... 11-10


11-10

C444 - NB_TCH_HO_ATPT_24_GenCaptureHandover ..................................................................................... 11-11


11-11

C447 - NB_TCH_HO_ATPT_26_BadQualHR ........................................................................................................ 11-12


11-12

C448 - NB_TCH_HO_ATPT_27_GoodQualFR ...................................................................................................... 11-12


11-12

C449 - NB_TCH_HO_ATPT_28_FastTraffic ........................................................................................................... 11-13


11-13

C450 - NB_TCH_HO_ATPT_22_TooShortDistance ............................................................................................. 11-13


11-13

C45a - NB_OUT_EXT_TCH_REAL_HO_REQ .................................................................................................... 11-14


11-14

C46 - NB_OUT_EXT_TCH_HO_SUCC ................................................................................................................... 11-15


11-15

C460 - NB_TCH_HO_ALLOC_EMERGENCY_PRES ...................................................................................... 11-15


11-15

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R ix
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
C461 - NB_TCH_HO_ATPT_29_TFO ....................................................................................................................... 11-16
11-16

C47 - NB_OUT_EXT_TCH_HO_EXEC_FAIL_REV ......................................................................................... 11-17


11-17

C470 - NB_TCH_HO_ATPT_2_TooLowQualUp .................................................................................................. 11-17


11-17

C471 - NB_TCH_HO_ATPT_3_TooLowLevUp .................................................................................................... 11-18


11-18

C472 - NB_TCH_HO_ATPT_4_TooLowQualDown ............................................................................................ 11-19


11-19

C473 - NB_TCH_HO_ATPT_5_TooLowLevDown .............................................................................................. 11-19


11-19

C474 - NB_TCH_HO_ATPT_6_TooLongDistance ............................................................................................... 11-20


11-20

C476 - NB_TCH_HO_ATPT_15_TooHighLevInterfUp ...................................................................................... 11-21


11-21

C477 - NB_TCH_HO_ATPT_16_TooHighLevInterfDown ................................................................................ 11-21


11-21

C478 - NB_TCH_HO_ATPT_12_TooLowPowBudg ............................................................................................ 11-22


11-22

C479 - NB_TCH_HO_ATPT_21_HighLevNeigCellPrefBand .......................................................................... 11-22


11-22

C48 - NB_OUT_EXT_TCH_HO_EXEC_FAIL_NO_REV ................................................................................ 11-23


11-23

C50 - NB_OUT_EXT_TCH_HO_ATPT .................................................................................................................... 11-24


11-24

C52 - NB_INC_INT_TCH_HO_SUCC ...................................................................................................................... 11-24


11-24

C53 - NB_INC_INT_TCH_HO_EXEC_FAIL_MS_ACCESS .......................................................................... 11-25


11-25

C541 - NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS ................................................................................... 11-25


11-25

C541a - NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS ................................................................ 11-26


11-26

C551 - NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS ................................................................... 11-27


11-27

C55a - NB_OUT_INT_TCH_HO_REQ ..................................................................................................................... 11-27


11-27

C56 - NB_OUT_INT_TCH_HO_SUCC .................................................................................................................... 11-28


11-28

C561 - NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS ....................................................................... 11-29


11-29

C57 - NB_OUT_INT_TCH_HO_EXEC_FAIL_REV ........................................................................................... 11-29


11-29

C58 - NB_OUT_INT_TCH_HO_EXEC_FAIL_NO_REV ................................................................................. 11-30


11-30

C585a - NB_TCH_HO_ATPT_7_ConsBadSACCHmicroCell .......................................................................... 11-31


11-31

C585d - NB_TCH_HO_ATPT_17_TooLowLevUpMicroCell ........................................................................... 11-31


11-31

C585e - NB_TCH_HO_ATPT_18_TooLowLevDownMicroCell ..................................................................... 11-32


11-32

C585f - NB_TCH_HO_ATPT_14_HighLevNeigLowCellSlowMS ................................................................. 11-33


11-33
....................................................................................................................................................................................................................................
x Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
C586a - NB_TCH_HO_ATPT_10_TooLowLevUpInZone ................................................................................. 11-33
11-33

C586b - NB_TCH_HO_ATPT_11_TooLowLevDownInZone ........................................................................... 11-34


11-34

C586c - NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone ................................................................. 11-34


11-34

C60 - NB_OUT_INT_TCH_HO_ATPT ..................................................................................................................... 11-35


11-35

C62 - NB_INTRA_TCH_HO_SUCC .......................................................................................................................... 11-35


11-35

C63 - NB_INTRA_TCH_HO_EXEC_FAIL_NO_REV ....................................................................................... 11-36


11-36

C67 - NB_INTRA_TCH_HO_EXEC_FAIL_REV ................................................................................................. 11-36


11-36

C75 - NB_TCH_HO_MSC_TRIG ................................................................................................................................ 11-37


11-37

12 Traffic Load

Telecom Procedure (Traffic Load)

Overview ................................................................................................................................................................................... 12-1


12-1

C413 - NB_TCH_NOR_ASS_INNER_ZONE_ALLOC ........................................................................................ 12-1


12-1

Part VII: BSC-TYPE 7 - LapD measurements

13 Quality of Service

Interface (QoS)

Overview ................................................................................................................................................................................... 13-1


13-1

L1.12 - NB_LAPD_CRC_ERROR ................................................................................................................................. 13-2


13-2

L1.15 - NB_LAPD_INFO_FRAME_RESENT .......................................................................................................... 13-2


13-2

L1.17 - NB_LAPD_EST ..................................................................................................................................................... 13-3


13-3

L1.18 - TIME_LAPD_CONG ........................................................................................................................................... 13-3


13-3

L1.5 - NB_LAPD_RNR_SENT ........................................................................................................................................ 13-4


13-4

L1.6 - NB_LAPD_RNR_REC .......................................................................................................................................... 13-4


13-4

L2.1 - NB_GSL_LAPD_ESTAB ..................................................................................................................................... 13-5


13-5

L2.2 - NB_GSL_LAPD_CRC_ERROR ........................................................................................................................ 13-5


13-5

L2.3 - NB_GSL_LAPD_INFO_FRAME_RESENT ................................................................................................ 13-6


13-6

L2.4 - NB_GSL_LAPD_RNR_SENT ............................................................................................................................ 13-6


13-6

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xi
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
L2.5 - NB_GSL_LAPD_RNR_REC .............................................................................................................................. 13-7
13-7

L2.6 - TIME_GSL_LAPD_UNAVAIL .......................................................................................................................... 13-7


13-7

L2.7 - TIME_GSL_LAPD_CONG .................................................................................................................................. 13-8


13-8

14 Resource Availability & Usage

Interface (Resource Availability)

Overview ................................................................................................................................................................................... 14-1


14-1

L1.16 - TIME_LAPD_UNAVAIL .................................................................................................................................... 14-1


14-1

15 Traffic Load

Interface (Traffic Load)

Overview ................................................................................................................................................................................... 15-1


15-1

L1.1 - NB_LAPD_INFO_FRAME_SENT ................................................................................................................... 15-1


15-1

L1.2 - NB_LAPD_INFO_FRAME_REC ..................................................................................................................... 15-2


15-2

Part VIII: BSC-TYPE 8 - X25 measurements

16 Quality of Service

Interface (QoS)

Overview ................................................................................................................................................................................... 16-1


16-1

X3.22 - NB_X25_INC_CALL_ABNORM_CLOSED ............................................................................................ 16-1


16-1

X3.23 - NB_X25_OUT_CALL_ABNORM_CLOSED .......................................................................................... 16-2


16-2

17 Traffic Load

Interface (Traffic Load)

Overview ................................................................................................................................................................................... 17-1


17-1

X3.20 - NB_X25_INC_CALL_SUCC_CLOSED ..................................................................................................... 17-1


17-1

X3.21 - NB_X25_OUT_CALL_SUCC_CLOSED ................................................................................................... 17-2


17-2

....................................................................................................................................................................................................................................
xii Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
Part IX: BSC-TYPE 9 - N7 measurements

18 Quality of Service

Interface (QoS)

Overview ................................................................................................................................................................................... 18-1


18-1

N1.10 - NB_N7_CHANGEOVER .................................................................................................................................. 18-2


18-2

N1.11 - NB_N7_CHANGEBACK .................................................................................................................................. 18-2


18-2

N1.12 - NB_N7_RESTORATION ................................................................................................................................... 18-3


18-3

N1.2 - NB_N7_LINK_FAIL_ANY_CAUSE .............................................................................................................. 18-3


18-3

N1.3 - NB_N7_LINK_FAIL_FIB_BSN ........................................................................................................................ 18-4


18-4

N1.4 - NB_N7_LINK_FAIL_T7_EXP .......................................................................................................................... 18-4


18-4

N1.5 - NB_N7_LINK_FAIL_SU_ERROR_RATE ................................................................................................... 18-5


18-5

N1.6 - NB_N7_LINK_FAIL_CONG ............................................................................................................................. 18-5


18-5

N1.7 - NB_N7_LINK_FAIL_ALIGNMENT .............................................................................................................. 18-6


18-6

N1.8 - NB_N7_SU_REC_WITH_ERROR .................................................................................................................. 18-6


18-6

N1.9 - NB_N7_NEG_ACK_REC .................................................................................................................................... 18-7


18-7

N3.10 - NB_N7_MSU_DISC_DUE_CONG ............................................................................................................... 18-7


18-7

N3.11 - NB_N7_CONG_WITH_MSU_LOST ........................................................................................................... 18-8


18-8

19 Resource Availability & Usage

Interface (Resource Availability)

Overview ................................................................................................................................................................................... 19-1


19-1

N1.1 - TIME_N7_ALIGNED ............................................................................................................................................ 19-1


19-1

N2.7 - TIME_N7_UNAVAIL_ERROR_SL ................................................................................................................. 19-2


19-2

N2.9 - TIME_N7_UNAVAIL_MSC_PROC_OUTAGE .......................................................................................... 19-2


19-2

N3.7 - TIME_N7_UNAVAIL_CONG ............................................................................................................................ 19-3


19-3

N4.2 - TIME_N7_UNAVAIL_LINK_SET ................................................................................................................... 19-3


19-3

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xiii
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
20 Traffic Load

Interface (Traffic Load)

Overview ................................................................................................................................................................................... 20-1


20-1

N3.1 - NB_N7_SIF_SIO_SENT ...................................................................................................................................... 20-1


20-1

N3.2 - NB_N7_OCTETS_RESENT ............................................................................................................................... 20-2


20-2

N3.3 - NB_N7_MSU_SENT ............................................................................................................................................. 20-2


20-2

N3.4 - NB_N7_SIF_SIO_REC ......................................................................................................................................... 20-3


20-3

N3.5 - NB_N7_MSU_REC ................................................................................................................................................ 20-3


20-3

Part X: BSC-TYPE 18 - A interface measurements

21 Quality of Service

Interface (QoS)

Overview ................................................................................................................................................................................... 21-1


21-1

C180a - NB_N7_CLEAR_REQ_RadioIntMessFail ................................................................................................. 21-2


21-2

C180b - NB_N7_CLEAR_REQ_O&Minterv ............................................................................................................. 21-2


21-2

C180c - NB_N7_CLEAR_REQ_EquipFail ................................................................................................................. 21-3


21-3

C180d - NB_N7_CLEAR_REQ_RadioIntFail ........................................................................................................... 21-3


21-3

C180e - NB_N7_CLEAR_REQ_NoRadioResAvail ................................................................................................. 21-4


21-4

C181a - NB_N7_ASS_FAIL_RadioIntMessFail ........................................................................................................ 21-4


21-4

C181b - NB_N7_ASS_FAIL_O&Minterv ................................................................................................................... 21-5


21-5

C181c - NB_N7_ASS_FAIL_EquipFail ........................................................................................................................ 21-5


21-5

C181d - NB_N7_ASS_FAIL_NoRadioResAvail ....................................................................................................... 21-6


21-6

C181e - NB_N7_ASS_FAIL_ReqTerResUnav/Alloc .............................................................................................. 21-6


21-6

C181f - NB_N7_ASS_FAIL_ReqTrans/RateUnav ................................................................................................... 21-7


21-7

C181g - NB_N7_ASS_FAIL_RadioIntFailRevOldChan ........................................................................................ 21-8


21-8

C181h - NB_N7_ASS_FAIL_RadioIntFail .................................................................................................................. 21-8


21-8

C181i - NB_N7_ASS_FAIL_CipherAlgoNotSupp ................................................................................................... 21-9


21-9

....................................................................................................................................................................................................................................
xiv Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
C181j - NB_N7_ASS_FAIL_BSSnotEquip ................................................................................................................. 21-9
21-9

C181k - NB_N7_ASS_FAIL_ProtocolError ............................................................................................................. 21-10


21-10

C181l - NB_N7_ASS_FAIL_ReqSpeechVersUnav ................................................................................................ 21-10


21-10

C181m - NB_N7_ASS_FAIL_ReqAintNotSupp/Unav ......................................................................................... 21-11


21-11

C181n - NB_N7_ASS_FAIL_ReqCodecNotSupp/Unav ...................................................................................... 21-11


21-11

C181p - NB_N7_ASS_FAIL_call_ident_alloc ......................................................................................................... 21-12


21-12

C182 - NB_N7_CLEAR_REQ_EST_PHAS ............................................................................................................ 21-12


21-12

22 Traffic Load

Interface (Traffic Load)

Overview ................................................................................................................................................................................... 22-1


22-1

C750 - TIME_A_CHANNEL_BUSY ............................................................................................................................ 22-1


22-1

C751 - NB_A_CHANNEL_ALLOC .............................................................................................................................. 22-2


22-2

Part XI: BSC-TYPE 19 - SMS PP measurements

23 Quality of Service

Short Message Service

Overview ................................................................................................................................................................................... 23-1


23-1

C190 - NB_SMS_PP_CON_MO_SDCCH .................................................................................................................. 23-2


23-2

C191 - NB_SMS_PP_CON_MT_SDCCH ................................................................................................................... 23-2


23-2

C192 - NB_SMS_PP_CON_MO_SACCH .................................................................................................................. 23-3


23-3

C193 - NB_SMS_PP_CON_MT_SACCH ................................................................................................................... 23-3


23-3

C194a - NB_SMS_PP_CON_REJ_RadioIntFail ....................................................................................................... 23-4


23-4

C194b - NB_SMS_PP_CON_REJ_BSSnotEquip ..................................................................................................... 23-4


23-4

C194c - NB_SMS_PP_CON_REJ_ProtocolError ..................................................................................................... 23-5


23-5

C195 - NB_SMS_PP_CON_REL_LAPDM_ERROR ............................................................................................. 23-5


23-5

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xv
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
Part XII: BSC-TYPE 20 - RMSI (Radio Measurement Statistics Improvement)

24 Adjacency

Fixed target Cell

Overview ................................................................................................................................................................................... 24-1


24-1

RMSIp80 - NEIGB_CELL_ID_I ..................................................................................................................................... 24-1


24-1

25 Handover

RMS

Overview ................................................................................................................................................................................... 25-1


25-1

RMSI63b - MR_MAT_AVSS_VS_NAVSS ................................................................................................................. 25-1


25-1

26 Quality of Service

RMS

Overview ................................................................................................................................................................................... 26-1


26-1

RMSI3a - TPR_RXQUAL_UL_RXLEV_UL_I ........................................................................................................ 26-2


26-2

RMSI3b - TMR_RXQUAL_UL_RXLEV_UL_I ...................................................................................................... 26-4


26-4

RMSI4a - TPR_RXQUAL_DL_RXLEV_DL_I ........................................................................................................ 26-5


26-5

RMSI4b - TMR_RXQUAL_DL_RXLEV_DL_I ...................................................................................................... 26-7


26-7

RMSI50a - TPR_TIMING_ADVANCE_I .................................................................................................................... 26-8


26-8

RMSI50b - MAX_TIMING_ADVANCE_I ................................................................................................................. 26-9


26-9

RMSI61a - TIMES1 .............................................................................................................................................................. 26-9


26-9

RMSI61b - TIMES2 ........................................................................................................................................................... 26-10


26-10

RMSI61c - TIMES3 ............................................................................................................................................................ 26-11


26-11

RMSI62a - NAVSS ............................................................................................................................................................. 26-11


26-11

RMSI62b - MR_NAVSS ................................................................................................................................................... 26-13


26-13

RMSI63a - MAT_AVSS_VS_NAVSS ......................................................................................................................... 26-13


26-13

RMSI64a - Path_Loss_UL ............................................................................................................................................... 26-15


26-15

RMSI64b - MR_Path_Loss_UL ..................................................................................................................................... 26-17


26-17

....................................................................................................................................................................................................................................
xvi Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
RMSI65a - Path_Loss_DL ............................................................................................................................................... 26-18
26-18

RMSI65b - MR_Path_Loss_DL ..................................................................................................................................... 26-20


26-20

RMSI66a - MS_Power_I .................................................................................................................................................. 26-21


26-21

RMSI66b - MR_MS_Power_I ........................................................................................................................................ 26-22


26-22

RMSI67a - BS_Power_I .................................................................................................................................................... 26-22


26-22

RMSI67b - MR_BS_Power_I ......................................................................................................................................... 26-24


26-24

RMSI7a - TPR_PATH_BALANCE_I .......................................................................................................................... 26-24


26-24

RMSI7b - MAX_PATH_BALANCE_I ....................................................................................................................... 26-26


26-26

RMSI8a - TPR_CIN_I ....................................................................................................................................................... 26-26


26-26

RMSI8b - MR_CIN_I ........................................................................................................................................................ 26-28


26-28

RMSIOLC3a - OLC_TPR_RXQUAL_UL_RXLEV_UL_I ................................................................................ 26-28


26-28

RMSIOLC3b - OLC_TMR_RXQUAL_UL_RXLEV_UL_I .............................................................................. 26-30


26-30

RMSIOLC4a - OLC_TPR_RXQUAL_DL_RXLEV_DL_I ................................................................................ 26-31


26-31

RMSIOLC4b - OLC_TMR_RXQUAL_DL_RXLEV_DL_I .............................................................................. 26-33


26-33

RMSIOLC50a - OLC_TPR_TIMING_ADVANCE_I ........................................................................................... 26-34


26-34

RMSIOLC50b - OLC_MAX_TIMING_ADVANCE_I ........................................................................................ 26-35


26-35

RMSIOLC62a - OLC_NAVSS ....................................................................................................................................... 26-35


26-35

RMSIOLC62b - OLC_MR_NAVSS ............................................................................................................................ 26-37


26-37

RMSIOLC7a - OLC_TPR_PATH_BALANCE_I .................................................................................................... 26-37


26-37

RMSIOLC7b - OLC_MAX_PATH_BALANCE_I ................................................................................................. 26-39


26-39

RMSIOLC8a - OLC_TPR_CIN_I ................................................................................................................................. 26-39


26-39

RMSIOLC8b - OLC_MR_CIN_I .................................................................................................................................. 26-41


26-41

Part XIII: BSC-TYPE 25 - SCCP measurements

27 Quality of Service

Interface (QoS)

Overview ................................................................................................................................................................................... 27-1


27-1

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xvii
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
C153a - NB_N7_CON_EST_FAIL_DUE_NSS ......................................................................................................... 27-1
27-1

C153b - NB_N7_CON_EST_FAIL_DUE_BSS ......................................................................................................... 27-2


27-2

C257 - NB_N7_CON_REF_SENT ................................................................................................................................. 27-2


27-2

C258 - NB_N7_CON_REF_REC .................................................................................................................................... 27-3


27-3

28 Traffic Load

Interface (Traffic Load)

Overview ................................................................................................................................................................................... 28-1


28-1

C251 - NB_N7_UNIT_DATA_SENT ............................................................................................................................ 28-2


28-2

C252 - NB_N7_UNIT_DATA_REC ............................................................................................................................... 28-2


28-2

C253 - NB_N7_CON_REQ_SENT ................................................................................................................................ 28-3


28-3

C254 - NB_N7_CON_REQ_REC ................................................................................................................................... 28-3


28-3

C255 - NB_N7_CON_CONF_SENT ............................................................................................................................. 28-4


28-4

C256 - NB_N7_CON_CONF_REC ................................................................................................................................ 28-4


28-4

Part XIV: BSC-TYPE 26 - TCH outgoing handover per adjacency measurements

29 Adjacency

Fixed serving Cell

Overview ................................................................................................................................................................................... 29-1


29-1

C720 - NB_ADJ_SCELL_OUT_TCH_HO_ATPT ................................................................................................... 29-2


29-2

C721 - NB_ADJ_SCELL_OUT_TCH_HO_SUCC .................................................................................................. 29-2


29-2

C722 - NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_REV ........................................................................ 29-3


29-3

C723 - NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_NO_REV .............................................................. 29-3


29-3

C724 - NB_ADJ_SCELL_OUT_TCH_HO_EMERGENCY_ATPT ................................................................. 29-4


29-4

C725 - NB_ADJ_SCELL_OUT_TCH_HO_BETTERCELL_ATPT ................................................................. 29-5


29-5

C727 - NB_ADJ_SCELL_OUT_TCH_HO_TRAFFIC_ATPT ............................................................................ 29-5


29-5

C728 - NB_ADJ_SCELL_OUT_ FORCED_DR_ATPT ........................................................................................ 29-6


29-6

....................................................................................................................................................................................................................................
xviii Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
Part XV: BSC-TYPE 27 - 2G TCH incoming handover per adjacency measurements

30 Adjacency

Fixed target Cell

Overview ................................................................................................................................................................................... 30-1


30-1

C730 - NB_ADJ_TCELL_INC_TCH_HO_ATPT .................................................................................................... 30-2


30-2

C731 - NB_ADJ_TCELL_INC_TCH_HO_SUCC ................................................................................................... 30-2


30-2

C733 - NB_ADJ_TCELL_INC_TCH_HO_EXEC_FAIL_MS_ACC ................................................................ 30-3


30-3

C734 - NB_ADJ_TCELL_INC_TCH_HO_EMERGENCY_ATPT ................................................................... 30-4


30-4

C735 - NB_ADJ_TCELL_INC_TCH_HO_BETTERCELL_ATPT ................................................................... 30-4


30-4

C737 - NB_ADJ_TCELL_INC_TCH_HO_TRAFFIC_ATPT ............................................................................. 30-5


30-5

C738 - NB_ADJ_TCELL_INC_FORCED_DR_ATPT ........................................................................................... 30-6


30-6

C753 - NB_ADJ_TCELL_INC_TCH_HO_OTHER_ATPT ................................................................................. 30-7


30-7

Part XVI: BSC-TYPE 28 - SDCCH handover

31 Handover

SDCCH

Overview ................................................................................................................................................................................... 31-1


31-1

C100 - NB_OUT_INT_SDCCH_HO_ATPT ............................................................................................................... 31-3


31-3

C101 - NB_INTRA_SDCCH_HO_PREP_FAIL_CONG ....................................................................................... 31-3


31-3

C102 - NB_INTRA_SDCCH_HO_SUCC ................................................................................................................... 31-4


31-4

C103 - NB_INTRA_SDCCH_HO_EXEC_FAIL_NO_REV ................................................................................ 31-4


31-4

C107 - NB_INTRA_SDCCH_HO_EXEC_FAIL_REV .......................................................................................... 31-5


31-5

C115 - NB_SDCCH_HO_MSC_TRIG .......................................................................................................................... 31-5


31-5

C310 - NB_INC_EXT_SDCCH_HO_REQ ................................................................................................................. 31-6


31-6

C311 - NB_INC_EXT_SDCCH_HO_ATPT ............................................................................................................... 31-6


31-6

C330 - NB_INC_INT_SDCCH_HO_REQ .................................................................................................................. 31-7


31-7

C331 - NB_INC_INT_SDCCH_HO_ATPT ................................................................................................................ 31-7


31-7

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xix
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
C360 - NB_INTRA_SDCCH_HO_REQ ...................................................................................................................... 31-8
31-8

C361 - NB_INTRA_SDCCH_HO_ATPT .................................................................................................................... 31-8


31-8

C445 - NB_SDCCH_HO_ATPT_23_TrafHandover ................................................................................................ 31-9


31-9

C446 - NB_SDCCH_HO_ATPT_24_GenCaptureHandover .............................................................................. 31-10


31-10

C454 - NB_SDCCH_HO_ATPT_22_TooShortDistance ...................................................................................... 31-10


31-10

C510 - NB_SDCCH_HO_ATPT_2_TooLowQualUp ............................................................................................ 31-11


31-11

C511 - NB_SDCCH_HO_ATPT_3_TooLowLevUp .............................................................................................. 31-11


31-11

C512 - NB_SDCCH_HO_ATPT_4_TooLowQualDown ...................................................................................... 31-12


31-12

C513 - NB_SDCCH_HO_ATPT_5_TooLowLevDown ........................................................................................ 31-12


31-12

C514 - NB_SDCCH_HO_ATPT_6_TooLongDistance ......................................................................................... 31-13


31-13

C516 - NB_SDCCH_HO_ATPT_15_TooHighLevInterfUp ............................................................................... 31-14


31-14

C517 - NB_SDCCH_HO_ATPT_16_TooHighLevInterfDown ......................................................................... 31-14


31-14

C518 - NB_SDCCH_HO_ATPT_12_TooLowPowBudg ..................................................................................... 31-15


31-15

C519 - NB_SDCCH_HO_ATPT_21_HighLevNeigCellPrefBand ................................................................... 31-15


31-15

C605a - NB_SDCCH_HO_ATPT_7_ConsBadSACCHmicroCell ................................................................... 31-16


31-16

C605d - NB_SDCCH_HO_ATPT_17_TooLowLevUpMicroCell .................................................................... 31-16


31-16

C605e - NB_SDCCH_HO_ATPT_18_TooLowLevDownMicroCell .............................................................. 31-17


31-17

C605f - NB_SDCCH_HO_ATPT_14_HighLevNeigLowCellSlowMS .......................................................... 31-17


31-17

C607 - NB_SDCCH_HO_ATPT_20_HighLevNeigCellForcDR ...................................................................... 31-18


31-18

C81 - NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG ................................................................................. 31-19


31-19

C82 - NB_INC_EXT_SDCCH_HO_SUCC .............................................................................................................. 31-19


31-19

C83 - NB_INC_EXT_SDCCH_HO_EXEC_FAIL_MS_ACCESS .................................................................. 31-20


31-20

C85a - NB_OUT_EXT_SDCCH_REAL_HO_REQ .............................................................................................. 31-20


31-20

C86 - NB_OUT_EXT_SDCCH_HO_SUCC ............................................................................................................ 31-21


31-21

C87 - NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_REV ................................................................................... 31-22


31-22

C88 - NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_NO_REV ......................................................................... 31-22


31-22

C90 - NB_OUT_EXT_SDCCH_HO_ATPT ............................................................................................................. 31-23


31-23
....................................................................................................................................................................................................................................
xx Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
C91 - NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG ................................................................................... 31-23
31-23

C92 - NB_INC_INT_SDCCH_HO_SUCC ............................................................................................................... 31-24


31-24

C93 - NB_INC_INT_SDCCH_HO_EXEC_FAIL_MS_ACCESS ................................................................... 31-25


31-25

C95a - NB_OUT_INT_SDCCH_HO_REQ .............................................................................................................. 31-25


31-25

C96 - NB_OUT_INT_SDCCH_HO_SUCC .............................................................................................................. 31-26


31-26

C97 - NB_OUT_INT_SDCCH_HO_EXEC_FAIL_REV .................................................................................... 31-26


31-26

C98 - NB_OUT_INT_SDCCH_HO_EXEC_FAIL_NO_REV .......................................................................... 31-27


31-27

Part XVII: BSC-TYPE 29 - Directed retry measurements

32 Handover

Directed Retry

Overview ................................................................................................................................................................................... 32-1


32-1

C142a - NB_OUT_FORCED_IDR_SUCC .................................................................................................................. 32-2


32-2

C142b - NB_OUT_FORCED_EDR_SUCC ................................................................................................................ 32-3


32-3

C142c - NB_OUT_NOR_IDR_SUCC ........................................................................................................................... 32-3


32-3

C142d - NB_OUT_NOR_EDR_SUCC ......................................................................................................................... 32-4


32-4

C143a - NB_OUT_FORCED_IDR_EXEC_FAIL_REV ........................................................................................ 32-4


32-4

C143b - NB_OUT_FORCED_IDR_EXEC_FAIL_NO_REV .............................................................................. 32-5


32-5

C143c - NB_OUT_FORCED_EDR_EXEC_FAIL_REV ....................................................................................... 32-5


32-5

C143d - NB_OUT_FORCED_EDR_EXEC_FAIL_NO_REV ............................................................................. 32-6


32-6

C143e - NB_OUT_NOR_IDR_EXEC_FAIL_REV ................................................................................................. 32-6


32-6

C143f - NB_OUT_NOR_IDR_EXEC_FAIL_NO_REV ........................................................................................ 32-7


32-7

C143g - NB_OUT_NOR_EDR_EXEC_FAIL_REV ................................................................................................ 32-7


32-7

C143h - NB_OUT_NOR_EDR_EXEC_FAIL_NO_REV ...................................................................................... 32-8


32-8

C144a - NB_OUT_FORCED_IDR_REQ ..................................................................................................................... 32-8


32-8

C144b - NB_OUT_FORCED_EDR_REQ ................................................................................................................... 32-9


32-9

C144c - NB_OUT_NOR_IDR_REQ .............................................................................................................................. 32-9


32-9

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xxi
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
C144d - NB_OUT_NOR_EDR_REQ .......................................................................................................................... 32-10
32-10

C145a - NB_OUT_FORCED_IDR_ATPT ................................................................................................................ 32-10


32-10

C145b - NB_OUT_FORCED_EDR_ATPT ............................................................................................................... 32-11


32-11

C145c - NB_OUT_NOR_IDR_ATPT .......................................................................................................................... 32-11


32-11

C145d - NB_OUT_NOR_EDR_ATPT ........................................................................................................................ 32-12


32-12

C151 - NB_INC_IDR_SUCC (29) ................................................................................................................................ 32-12


32-12

C152 - NB_INC_IDR_EXEC_FAIL_MS_ACCESS ............................................................................................. 32-13


32-13

C153 - NB_INC_IDR_REQ ............................................................................................................................................ 32-13


32-13

C154 - NB_INC_IDR_ATPT .......................................................................................................................................... 32-14


32-14

C555 - NB_INC_IDR_PREP_FAIL_CONG_R_ABIS ......................................................................................... 32-14


32-14

Part XVIII: BSC-TYPE 30 - SMS CB measurements

33 Quality of Service

Short Message Service

Overview ................................................................................................................................................................................... 33-1


33-1

CB603 - NB_SMS_CB_FAIL_IND ................................................................................................................................ 33-1


33-1

CB604 - NB_SMS_CB_WRITE_REP_KILL_MESS_REJ ................................................................................... 33-2


33-2

34 Traffic Load

Telecom Procedure (Traffic Load)

Overview ................................................................................................................................................................................... 34-1


34-1

CB601 - NB_SMSCB_WRITE_REPL_SUCC .......................................................................................................... 34-1


34-1

CB602 - NB_SMSCB_KILL_MESS_SUCC .............................................................................................................. 34-2


34-2

Part XIX: BSC-TYPE 31 - RMS (Radio Measurement Statistics)

35 Quality of Service

RMS

Overview ................................................................................................................................................................................... 35-1


35-1

RMS10 - VQ_NOISY_UL_INTERFERENCE .......................................................................................................... 35-3


35-3
....................................................................................................................................................................................................................................
xxii Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
RMS11 - VQ_NOISY_DL_INTERFERENCE .......................................................................................................... 35-4
35-4

RMS12 - VQ_NOISY_UL_COVERAGE .................................................................................................................... 35-4


35-4

RMS13 - VQ_NOISY_DL_COVERAGE .................................................................................................................... 35-5


35-5

RMS14 - VQ_NOISY_UL_UNDEFINED ................................................................................................................... 35-6


35-6

RMS15 - VQ_NOISY_DL_UNDEFINED ................................................................................................................... 35-7


35-7

RMS16 - VQ_NOISY_UL_BAD_FER ......................................................................................................................... 35-8


35-8

RMS17 - VQ_NOISY_UL_GOOD_FER ..................................................................................................................... 35-9


35-9

RMS18 - VQ_ABNORMAL_BAD_FER .................................................................................................................. 35-10


35-10

RMS20 - TRE_BAND ....................................................................................................................................................... 35-10


35-10

RMS21 - IND_TRE_OVERLOAD .............................................................................................................................. 35-12


35-12

RMS22 - IND_RMS_RESTARTED ............................................................................................................................. 35-13


35-13

RMS23 - IND_CI_PARTIAL_OBSERVATION ...................................................................................................... 35-13


35-13

RMS24 - IND_CI_OVERFLOW .................................................................................................................................. 35-14


35-14

RMS32 - TOT_MEAS ....................................................................................................................................................... 35-14


35-14

RMS33 - TOT_MEAS_L1INFO_NOL3INFO ......................................................................................................... 35-15


35-15

RMS34 - TOT_MEAS_DTX_UL ................................................................................................................................. 35-15


35-15

RMS35 - TOT_MEAS_DTX_DL ................................................................................................................................. 35-16


35-16

RMS36 - PERC_TA_GT_TA_STAT ............................................................................................................................ 35-16


35-16

RMS37 - MAX_TA ............................................................................................................................................................ 35-17


35-17

RMS38 - TOT_EMR .......................................................................................................................................................... 35-17


35-17

RMS3a - TPR_RXQUAL_UL_RXLEV_UL ............................................................................................................ 35-18


35-18

RMS3b - TMR_RXQUAL_UL_RXLEV_UL .......................................................................................................... 35-19


35-19

RMS41a - AMR_WB_GMSK_FR_UL_BAD .......................................................................................................... 35-19


35-19

RMS41b - MAX_AMR_WB_GMSK_FR_UL_BAD ........................................................................................... 35-20


35-20

RMS42a - AMR_WB_GMSK _FR_UL_RXLEV_UL ......................................................................................... 35-20


35-20

RMS42b - MAX_AMR_WB_GMSK_FR_UL_RXLEV_UL ............................................................................ 35-22


35-22

RMS43a - AMR_WB_GMSK_FR_DL_RXLEV_DL ........................................................................................... 35-22


35-22
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xxiii
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
RMS43b - MAX_AMR_WB_GMSK_FR_DL_RXLEV_DL ............................................................................ 35-23
35-23

RMS44a - AMR_FR_UL_BAD ..................................................................................................................................... 35-24


35-24

RMS44b - MAX_AMR_FR_UL_BAD ...................................................................................................................... 35-25


35-25

RMS45a - AMR_HR_UL_BAD .................................................................................................................................... 35-25


35-25

RMS45b - MAX_AMR_HR_UL_BAD ...................................................................................................................... 35-26


35-26

RMS46a - AMR_FR_UL_RXLEV_UL ...................................................................................................................... 35-26


35-26

RMS46b - MAX_AMR_FR_UL_RXLEV_UL ....................................................................................................... 35-28


35-28

RMS47a - AMR_FR_DL_RXLEV_DL ...................................................................................................................... 35-28


35-28

RMS47b - MAX_AMR_FR_DL_RXLEV_DL ....................................................................................................... 35-29


35-29

RMS48a - AMR_HR_UL_RXLEV_UL ..................................................................................................................... 35-30


35-30

RMS49a - AMR_HR_DL_RXLEV_DL ..................................................................................................................... 35-31


35-31

RMS49b - MAX_AMR_HR_DL_RXLEV_DL ...................................................................................................... 35-32


35-32

RMS4a - TPR_RXQUAL_DL_RXLEV_DL ............................................................................................................ 35-32


35-32

RMS4b - TMR_RXQUAL_DL_RXLEV_DL .......................................................................................................... 35-34


35-34

RMS50a - TPR_TIMING_ADVANCE ....................................................................................................................... 35-34


35-34

RMS50b - MAX_TIMING_ADVANCE .................................................................................................................... 35-35


35-35

RMS51 - TPR_UL_RXLEV_TA_BAND .................................................................................................................. 35-35


35-35

RMS52 - TPR_DL_RXLEV_TA_BAND .................................................................................................................. 35-36


35-36

RMS53 - TPR_UL_RXQUAL_TA_BAND .............................................................................................................. 35-37


35-37

RMS54 - TPR_DL_RXQUAL_TA_BAND .............................................................................................................. 35-38


35-38

RMS5a - TPR_BFI_RXLEV_UL .................................................................................................................................. 35-38


35-38

RMS5b - TMR_BFI_RXLEV_UL ................................................................................................................................ 35-40


35-40

RMS6a - TPR_RADIO_LINK ........................................................................................................................................ 35-40


35-40

RMS6b - MAX_RADIO_LINK ..................................................................................................................................... 35-41


35-41

RMS7a - TPR_PATH_BALANCE ................................................................................................................................ 35-41


35-41

RMS7b - MAX_PATH_BALANCE ............................................................................................................................. 35-43


35-43

RMS8a - TPR_CIN ............................................................................................................................................................. 35-43


35-43
....................................................................................................................................................................................................................................
xxiv Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
RMS8b - MR_CIN .............................................................................................................................................................. 35-45
35-45

RMS9a - TPR_CIF .............................................................................................................................................................. 35-45


35-45

RMS9b - MR_CIF ............................................................................................................................................................... 35-47


35-47

Speech

Overview ................................................................................................................................................................................. 35-48


35-48

RMS48b - MAX_AMR_HR_UL_RXLEV_UL ...................................................................................................... 35-48


35-48

36 Resource Availability & Usage

Channel

Overview ................................................................................................................................................................................... 36-1


36-1

RMS31 - TOT_SEIZ_TCH ................................................................................................................................................ 36-1


36-1

Part XX: BSC-TYPE 32 - Change of frequency band measurements

37 Quality of Service

Handover

Overview ................................................................................................................................................................................... 37-1


37-1

C403a - NB_INC_EXT_TCH_HO_NEW_BAND_ATPT ..................................................................................... 37-2


37-2

C403b - NB_INC_EXT_TCH_HO_NEW_BAND_SUCC .................................................................................... 37-2


37-2

C404a - NB_OUT_EXT_TCH_HO_NEW_BAND_ATPT ................................................................................... 37-3


37-3

C404b - NB_OUT_EXT_TCH_HO_NEW_BAND_SUCC .................................................................................. 37-3


37-3

C420a - NB_INC_INT_TCH_HO_NEW_BAND_ATPT ...................................................................................... 37-4


37-4

C420b - NB_INC_INT_TCH_HO_NEW_BAND_SUCC ..................................................................................... 37-5


37-5

C421a - NB_OUT_INT_TCH_HO_NEW_BAND_ATPT ..................................................................................... 37-5


37-5

C421b - NB_OUT_INT_TCH_HO_NEW_BAND_SUCC ................................................................................... 37-6


37-6

Part XXI: BSC-TYPE 33 - EME (Electro-Magnetic Emission) measurements

38 Sustainable & safety

Electro-Magnetic Emission

Overview ................................................................................................................................................................................... 38-1


38-1
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xxv
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
E01 - EME_PWR_GSM ...................................................................................................................................................... 38-1
38-1

E02 - EME_PWR_DCS ....................................................................................................................................................... 38-2


38-2

Part XXII: BSC-TYPE 35 - IP transport measurements

39 Quality of Service

IP (QoS)

Overview ................................................................................................................................................................................... 39-1


39-1

IP11 - NB_CS_CALL_REJECTED_DUE_TO_IP_CONGESTION ................................................................. 39-3


39-3

IP12 - CUMULATED_TIME_IP_CONGESTION ................................................................................................... 39-3


39-3

IP13 - NB_MAX_ACTIVE_TCH_REJ ......................................................................................................................... 39-4


39-4

IP21 - NB_ATERMUX_NIBBLE_ALLOC_REQ .................................................................................................... 39-4


39-4

IP22 - NB_ATERMUX_NIBBLE_ALLOC_FAIL_CONG ................................................................................... 39-5


39-5

IP23 - TIME_ATERMUX_NIBBLE_CONG .............................................................................................................. 39-5


39-5

IP26e - NB_BTS_RESENT_RSL-I_LAPD FRAMES ............................................................................................ 39-6


39-6

IP27e - NB_BSC_RESENT_SS7_IP_PACKETS ...................................................................................................... 39-6


39-6

IP28e - NB_TC_RESENT_SS7_IP_PACKETS ......................................................................................................... 39-7


39-7

IP29k - NB_BTS_RCVD_DL_MUXTRAUP_PACKETS_OUT_OF_DELAY ............................................ 39-7


39-7

IP29m - NB_BTS_NOT_RCVD_DL_MUXTRAUP_PACKETS ....................................................................... 39-8


39-8

IP30m - NB_TC_NOT_RCVD_UL_MUXTRAUP_PACKETS ......................................................................... 39-8


39-8

IP30q - NB_TC_NOT_RCVD_UL_MUXTRAUP_PACKETS_BSC ............................................................... 39-9


39-9

IP31c - NB_BTS_DROPPED_IP_PACKETS_PRIORITY0 ................................................................................. 39-9


39-9

IP31d - NB_BTS_DROPPED_IP_PACKETS_PRIORITY1 .............................................................................. 39-10


39-10

IP31e - NB_BTS_DROPPED_IP_PACKETS_PRIORITY2 .............................................................................. 39-10


39-10

IP31f - NB_BTS_DROPPED_IP_PACKETS_PRIORITY3 ............................................................................... 39-11


39-11

IP32a - NB_BSC_SENT_ALL_FLOWS_BYTES .................................................................................................. 39-11


39-11

IP32b - NB_BSC_RCVD_ALL_FLOWS_BYTES ................................................................................................ 39-12


39-12

IP32c - NB_BSC_DROPPED_IP_PACKETS_PRIORITY0 .............................................................................. 39-12


39-12

....................................................................................................................................................................................................................................
xxvi Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
IP32d - NB_BSC_DROPPED_IP_PACKETS_PRIORITY1 .............................................................................. 39-13
39-13

IP32e - NB_BSC_DROPPED_IP_PACKETS_PRIORITY2 .............................................................................. 39-13


39-13

IP32f - NB_BSC_DROPPED_IP_PACKETS_PRIORITY3 ............................................................................... 39-14


39-14

IP35c - NB_BSC_RCVD_DL_MUXTRAUP_PACKETS_OUT_OF_DELAY .......................................... 39-14


39-14

IP35d - NB_BSC_NOT_RCVD_DL_MUXTRAUP_PACKETS ..................................................................... 39-15


39-15

IP40b - NB_BTS_RESENT_IPGCHU_GBR_IP_PACKETS ............................................................................ 39-15


39-15

IP41b - NB_BTS_RESENT_IPGCHU_BE_IP_PACKETS ................................................................................ 39-16


39-16

IP62 - NB_BSC_NOT_RCVD_UL_MUXTRAUP_PACKETS ........................................................................ 39-16


39-16

IP70 - NB_ACC_TIME_SVR1 ...................................................................................................................................... 39-17


39-17

IP71 - NB_ACC_TIME_SVR2 ...................................................................................................................................... 39-17


39-17

IP72 - NB_SUCC_ACC_TIME_SVR1 ....................................................................................................................... 39-18


39-18

IP73 - NB_SUCC_ACC_TIME_SVR2 ....................................................................................................................... 39-18


39-18

IP74 - LAST_CLK_DIFF_TIME_SVR1 .................................................................................................................... 39-19


39-19

IP75 - LAST_CLK_DIFF_TIME_SVR2 .................................................................................................................... 39-19


39-19

IP76 - MIN_CLK_DIFF_TIME_SVR1 ...................................................................................................................... 39-20


39-20

IP77 - MIN_CLK_DIFF_TIME_SVR2 ...................................................................................................................... 39-20


39-20

IP78 - LAST_RTT_TIME_SVR1 .................................................................................................................................. 39-21


39-21

IP79 - LAST_RTT_TIME_SVR2 .................................................................................................................................. 39-21


39-21

IP80 - NB_EVALS_RETUNE_TIME_SVR1 ........................................................................................................... 39-22


39-22

IP81 - NB_EVALS_RETUNE_TIME_SVR2 ........................................................................................................... 39-22


39-22

IP82 - NB_ACC_EVALS_RETUNE_TIME_SVR1 .............................................................................................. 39-23


39-23

IP83 - NB_ACC_EVALS_RETUNE_TIME_SVR2 .............................................................................................. 39-24


39-24

IP84 - GRADIENT_TIME_SVR1 ................................................................................................................................ 39-24


39-24

IP85 - GRADIENT_TIME_SVR2 ................................................................................................................................ 39-25


39-25

IP86 - MEAN_GRADIENT_TIME_SVR1 ............................................................................................................... 39-25


39-25

IP87 - MEAN_GRADIENT_TIME_SVR2 ............................................................................................................... 39-26


39-26

IP88 - OCXO_TUNING_TIME_SVR ......................................................................................................................... 39-26


39-26
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xxvii
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
IP89 - OCXO_TUNING_VALUE ................................................................................................................................. 39-27
39-27

40 Traffic Load

IP (Traffic Load)

Overview ................................................................................................................................................................................... 40-1


40-1

IP25a - NB_BSC_SENT_OMLRSL_IP_BYTES ...................................................................................................... 40-3


40-3

IP25b - NB_BSC_SENT_OMLRSL_IP_PACKETS ................................................................................................ 40-3


40-3

IP25c - NB_BSC_SENT_OMLRSL_IP_BYTES_MAX_MN ............................................................................. 40-4


40-4

IP26a - NB_BTS_SENT_OML_IP_BYTES ............................................................................................................... 40-4


40-4

IP26b - NB_BTS_SENT_RSL_IP_BYTES ................................................................................................................. 40-5


40-5

IP26c - NB_BTS_SENT_OML_IP_PACKETS ......................................................................................................... 40-5


40-5

IP26d - NB_BTS_SENT_RSL_IP_PACKETS ........................................................................................................... 40-6


40-6

IP27a - NB_BSC_SENT_TCSL_IP_BYTES .............................................................................................................. 40-6


40-6

IP27b - NB_BSC_SENT_SS7_IP_BYTES .................................................................................................................. 40-7


40-7

IP27c - NB_BSC_SENT_TCSL_IP_PACKETS ........................................................................................................ 40-7


40-7

IP27d - NB_BSC_SENT_SS7_IP_PACKETS ............................................................................................................ 40-8


40-8

IP27g - NB_BSC_SENT_SS7_IP_BYTES_MAX_MN ......................................................................................... 40-8


40-8

IP27h - NB_BSC_SENT_TCSL_IP_BYTES_MAX_MN ..................................................................................... 40-9


40-9

IP28a - NB_TC_SENT_TCSL_IP_BYTES ................................................................................................................. 40-9


40-9

IP28b - NB_TC_SENT_SS7_IP_BYTES .................................................................................................................. 40-10


40-10

IP28c - NB_TC_SENT_TCSL_IP_PACKETS ........................................................................................................ 40-10


40-10

IP28d - NB_TC_SENT_SS7_IP_PACKETS ............................................................................................................ 40-11


40-11

IP28g - NB_TC_SENT_SS7_IP_BYTES_MAX_MN .......................................................................................... 40-11


40-11

IP28h - NB_TC_SENT_TCSL_IP_BYTES_MAX_MN ...................................................................................... 40-12


40-12

IP29a - NB_BTS_SENT_UL_MUXTRAUP_BYTES .......................................................................................... 40-12


40-12

IP29c - NB_BTS_SENT_UL_MUXTRAUP_PACKETS .................................................................................... 40-13


40-13

IP30a - NB_TC_SENT_DL_MUXTRAUP_BYTES ............................................................................................ 40-13


40-13

....................................................................................................................................................................................................................................
xxviii Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
IP30c - NB_TC_SENT_DL_MUXTRAUP_PACKETS ....................................................................................... 40-14
40-14

IP30g - NB_TC_SENT_DL_MUXTRAUP_BYTES_MAX_MN .................................................................... 40-14


40-14

IP30n - NB_TC_SENT_DL_MUXTRAUP_KBYTES_BSC ............................................................................. 40-15


40-15

IP30o - NB_TC_SENT_DL_MUXTRAUP_PACKETS_BSC .......................................................................... 40-15


40-15

IP30p - NB_TC_SENT_DL_MUXTRAUP_BYTES_MAX_MN_BSC ........................................................ 40-16


40-16

IP31a - NB_BTS_SENT_ALL_FLOW_BYTES_MAX_MN ............................................................................ 40-16


40-16

IP33a - NB_TC_TO_TC_SENT_UL_eTRAUP_BYTES .................................................................................... 40-17


40-17

IP33c - NB_TC_TO_TC_SENT_UL_eTRAUP_PACKETS .............................................................................. 40-17


40-17

IP33f - NB_TC_TO_TC_SENT_UL_eTRAUP_BYTES_MAX_MN ............................................................ 40-18


40-18

IP35a - NB_BSC_SENT_UL_MUXTRAUP_KBYTES ...................................................................................... 40-18


40-18

IP35b - NB_BSC_SENT_UL_MUXTRAUP_PACKETS ................................................................................... 40-19


40-19

IP40a - NB_BTS_SENT_IPGCHU_GBR_IP_PACKETS ................................................................................... 40-19


40-19

IP40d - NB_BTS_SENT_IPGCHU_GBR_IP_BYTES ........................................................................................ 40-20


40-20

IP41a - NB_BTS_SENT_IPGCHU_BE_IP_PACKETS ....................................................................................... 40-20


40-20

IP41d - NB_BTS_SENT_IPGCHU_BE_IP_BYTES ............................................................................................ 40-21


40-21

IP42a - NB_BTS_SENT_IPGCHC_CTRL_TCP_SEGMENTS ....................................................................... 40-21


40-21

IP42d - NB_BTS_SENT_IPGCHC_CTRL_IP_BYTES ...................................................................................... 40-22


40-22

IP59 - NB_BSC_SENT_DL_MUXTRAUP_BYTES ............................................................................................ 40-22


40-22

IP60 - NB_BSC_SENT_DL_MUXTRAUP_PACKETS ...................................................................................... 40-23


40-23

IP61 - NB_BSC_SENT_DL_MUXTRAUP_BYTES_MAX_MN ................................................................... 40-23


40-23

Part XXIII: BSC-TYPE 36 - Iur-g interface measurements

41 Traffic Load

Interface (Traffic Load)

Overview ................................................................................................................................................................................... 41-1


41-1

MC1301 - NB_BSC_SENT_SS7_IP_BYTES_IURG ............................................................................................. 41-2


41-2

MC1302 - NB_BSC_SENT_SS7_IP_PACKETS_IURG ....................................................................................... 41-2


41-2

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xxix
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC1303 - NB_BSC_RESENT_SS7_IP_PACKETS_IURG ................................................................................. 41-3
41-3

MC1304 - NB_BSC_SENT_SS7_IP_BYTES_MAX_MN_IURG ..................................................................... 41-3


41-3

MC1305 - NB_N7_CON_REQ_REC_IURG .............................................................................................................. 41-4


41-4

MC1306 - NB_N7_CON_CONF_SENT_IURG ....................................................................................................... 41-4


41-4

Part XXIV: BSC-TYPE 37 - VAMOS measurements

42 Handover

TCH

Overview ................................................................................................................................................................................... 42-1


42-1

MC1404a - NB_TCH_PAIR_HO_ATPT_NON_SAIC ........................................................................................... 42-2


42-2

MC1404b - NB_TCH_PAIR_HO_ATPT_SAIC ........................................................................................................ 42-2


42-2

MC1404c - NB_TCH_PAIR_HO_ATPT_VAMOS1 ................................................................................................ 42-3


42-3

MC1404d - NB_TCH_PAIR_HO_ATPT_VAMOS2 ................................................................................................ 42-3


42-3

MC1405a - NB_TCH_PAIR_HO_SUCC_NON_SAIC .......................................................................................... 42-4


42-4

MC1405b - NB_TCH_PAIR_HO_SUCC_SAIC ....................................................................................................... 42-4


42-4

MC1405c - NB_TCH_PAIR_HO_SUCC_VAMOS1 ............................................................................................... 42-5


42-5

MC1405d - NB_TCH_PAIR_HO_SUCC_VAMOS2 ............................................................................................... 42-5


42-5

MC1420a - NB_TCH_HO_ATPT_35_pairing_NON_SAIC ................................................................................. 42-6


42-6

MC1420b - NB_TCH_HO_ATPT_35_pairing_SAIC .............................................................................................. 42-6


42-6

MC1420c - NB_TCH_HO_ATPT_35_pairing_VAMOS1 ..................................................................................... 42-7


42-7

MC1420d - NB_TCH_HO_ATPT_35_pairing_VAMOS2 ..................................................................................... 42-8


42-8

MC1421a - NB_TCH_HO_ATPT_34_unpairing_NON_SAIC ............................................................................ 42-8


42-8

MC1421b - NB_TCH_HO_ATPT_34_unpairing_SAIC ......................................................................................... 42-9


42-9

MC1421c - NB_TCH_HO_ATPT_34_unpairing_VAMOS1 ................................................................................ 42-9


42-9

MC1421d - NB_TCH_HO_ATPT_34_unpairing_VAMOS2 .............................................................................. 42-10


42-10

MC1424a - NB_INTRA_TCH_HO_35_PREP_FAIL_NO_PAIRING ........................................................... 42-10


42-10

....................................................................................................................................................................................................................................
xxx Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
43 Quality of Service

Channel

Overview ................................................................................................................................................................................... 43-1


43-1

MC1426d - DISTRIB_4_SCPIR_NON_SAIC_SAIC ............................................................................................. 43-1


43-1

Established Phase

Overview ................................................................................................................................................................................... 43-3


43-3

MC1406a - NB_TCH_EST_PAIR_DROP_NON_SAIC ........................................................................................ 43-3


43-3

MC1406b - NB_TCH_EST_PAIR_DROP_SAIC ..................................................................................................... 43-4


43-4

MC1406c - NB_TCH_EST_PAIR_DROP_VAMOS1 ............................................................................................. 43-4


43-4

MC1406d - NB_TCH_EST_PAIR_DROP_VAMOS2 ............................................................................................. 43-5


43-5

MC1407a - NB_TCH_EST_UNPAIR_DROP_NON_SAIC ................................................................................. 43-6


43-6

MC1407b - NB_TCH_EST_UNPAIR_DROP_SAIC .............................................................................................. 43-6


43-6

MC1407c - NB_TCH_EST_UNPAIR_DROP_VAMOS1 ...................................................................................... 43-7


43-7

MC1407d - NB_TCH_EST_UNPAIR_DROP_VAMOS2 ...................................................................................... 43-8


43-8

Telecom Procedure (QoS)

Overview ................................................................................................................................................................................... 43-9


43-9

MC1422a - AV_RXQUAL_DL_VAMOS_NON_SAIC .......................................................................................... 43-9


43-9

MC1422b - AV_RXQUAL_DL_VAMOS_SAIC .................................................................................................... 43-10


43-10

MC1422c - AV_RXQUAL_DL_VAMOS_VAMOS1 ............................................................................................ 43-11


43-11

MC1422d - AV_RXQUAL_DL_VAMOS_VAMOS2 ............................................................................................ 43-12


43-12

MC1423a - AV_RXQUAL_UL_VAMOS_NON_SAIC ....................................................................................... 43-12


43-12

MC1423b - AV_RXQUAL_UL_VAMOS_SAIC .................................................................................................... 43-13


43-13

MC1423c - AV_RXQUAL_UL_VAMOS_VAMOS1 ............................................................................................ 43-14


43-14

MC1423d - AV_RXQUAL_UL_VAMOS_VAMOS2 ............................................................................................ 43-15


43-15

MC1424d - NB_INTRA_TCH_HO_35_REQ .......................................................................................................... 43-15


43-15

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xxxi
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
44 Resource Availability & Usage

Channel

Overview ................................................................................................................................................................................... 44-1


44-1

MC1408a - NB_PAIR_PER_MS_NON_SAIC .......................................................................................................... 44-3


44-3

MC1408b - NB_PAIR_PER_MS_SAIC ....................................................................................................................... 44-3


44-3

MC1408c - NB_PAIR_PER_MS_VAMOS1 ............................................................................................................... 44-4


44-4

MC1408d - NB_PAIR_PER_MS_VAMOS2 ............................................................................................................... 44-5


44-5

MC1409a - NB_UNPAIR_PER_MS_NON_SAIC ................................................................................................... 44-5


44-5

MC1409b - NB_UNPAIR_PER_MS_SAIC ................................................................................................................ 44-6


44-6

MC1409c - NB_UNPAIR_PER_MS_VAMOS1 ........................................................................................................ 44-6


44-6

MC1409d - NB_UNPAIR_PER_MS_VAMOS2 ........................................................................................................ 44-7


44-7

MC1410a - NB_ONE_CALL_PER_RADIO_TS_NON_VAMOS ..................................................................... 44-7


44-7

MC1410b - NB_TWO_CALLS_PER_RADIO_TS_NON_VAMOS ................................................................. 44-8


44-8

MC1410c - NB_TWO_CALLS_PER_RADIO_TS_VAMOS .............................................................................. 44-9


44-9

MC1410d - NB_THREE_CALLS_PER_RADIO_TS_VAMOS ......................................................................... 44-9


44-9

MC1410e - NB_FOUR_CALLS_PER_RADIO_TS .............................................................................................. 44-10


44-10

MC1411a - DISTRIB_1_SCPIR_NON_SAIC_VAMOS1 ................................................................................... 44-11


44-11

MC1411b - DISTRIB_2_SCPIR_NON_SAIC_VAMOS1 ................................................................................... 44-11


44-11

MC1411c - DISTRIB_3_SCPIR_NON_SAIC_VAMOS1 ................................................................................... 44-12


44-12

MC1411d - DISTRIB_4_SCPIR_NON_SAIC_VAMOS1 .................................................................................. 44-13


44-13

MC1412a - DISTRIB_1_SCPIR_NON_SAIC_VAMOS2 ................................................................................... 44-13


44-13

MC1412b - DISTRIB_2_SCPIR_NON_SAIC_VAMOS2 .................................................................................. 44-14


44-14

MC1412c - DISTRIB_3_SCPIR_NON_SAIC_VAMOS2 ................................................................................... 44-15


44-15

MC1412d - DISTRIB_4_SCPIR_NON_SAIC_VAMOS2 .................................................................................. 44-15


44-15

MC1413a - DISTRIB_1_SCPIR_SAIC_VAMOS1 ................................................................................................ 44-16


44-16

MC1413b - DISTRIB_2_SCPIR_SAIC_VAMOS1 ................................................................................................ 44-17


44-17

MC1413c - DISTRIB_3_SCPIR_SAIC_VAMOS1 ................................................................................................ 44-17


44-17
....................................................................................................................................................................................................................................
xxxii Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC1413d - DISTRIB_4_SCPIR_SAIC_VAMOS1 ................................................................................................ 44-18
44-18

MC1414a - DISTRIB_1_SCPIR_SAIC_VAMOS2 ................................................................................................ 44-19


44-19

MC1414b - DISTRIB_2_SCPIR_SAIC_VAMOS2 ................................................................................................ 44-19


44-19

MC1414c - DISTRIB_3_SCPIR_SAIC_VAMOS2 ................................................................................................ 44-20


44-20

MC1414d - DISTRIB_4_SCPIR_SAIC_VAMOS2 ................................................................................................ 44-21


44-21

MC1415a - DISTRIB_1_SCPIR_VAMOS1_VAMOS1 ....................................................................................... 44-21


44-21

MC1415b - DISTRIB_2_SCPIR_VAMOS1_VAMOS1 ....................................................................................... 44-22


44-22

MC1415c - DISTRIB_3_SCPIR_VAMOS1_VAMOS1 ....................................................................................... 44-23


44-23

MC1415d - DISTRIB_4_SCPIR_VAMOS1_VAMOS1 ....................................................................................... 44-23


44-23

MC1416a - DISTRIB_1_SCPIR_VAMOS1_VAMOS2 ....................................................................................... 44-24


44-24

MC1416b - DISTRIB_2_SCPIR_VAMOS1_VAMOS2 ....................................................................................... 44-25


44-25

MC1416c - DISTRIB_3_SCPIR_VAMOS1_VAMOS2 ....................................................................................... 44-25


44-25

MC1416d - DISTRIB_4_SCPIR_VAMOS1_VAMOS2 ....................................................................................... 44-26


44-26

MC1417a - DISTRIB_1_SCPIR_VAMOS2_VAMOS1 ....................................................................................... 44-27


44-27

MC1417b - DISTRIB_2_SCPIR_VAMOS2_VAMOS1 ....................................................................................... 44-27


44-27

MC1417c - DISTRIB_3_SCPIR_VAMOS2_VAMOS1 ....................................................................................... 44-28


44-28

MC1417d - DISTRIB_4_SCPIR_VAMOS2_VAMOS1 ....................................................................................... 44-29


44-29

MC1418a - DISTRIB_1_SCPIR_VAMOS2_VAMOS2 ....................................................................................... 44-29


44-29

MC1418b - DISTRIB_2_SCPIR_VAMOS2_VAMOS2 ....................................................................................... 44-30


44-30

MC1418c - DISTRIB_3_SCPIR_VAMOS2_VAMOS2 ....................................................................................... 44-31


44-31

MC1418d - DISTRIB_4_SCPIR_VAMOS2_VAMOS2 ....................................................................................... 44-31


44-31

MC1419a - DISTRIB_1_SCPIR_SAIC_SAIC ........................................................................................................ 44-32


44-32

MC1419b - DISTRIB_2_SCPIR_SAIC_SAIC ........................................................................................................ 44-33


44-33

MC1419c - DISTRIB_3_SCPIR_SAIC_SAIC ........................................................................................................ 44-33


44-33

MC1419d - DISTRIB_4_SCPIR_SAIC_SAIC ........................................................................................................ 44-34


44-34

MC1425a - DISTRIB_1_SCPIR_NON_SAIC_NON_SAIC .............................................................................. 44-35


44-35

MC1425b - DISTRIB_2_SCPIR_NON_SAIC_NON_SAIC .............................................................................. 44-35


44-35
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xxxiii
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC1425c - DISTRIB_3_SCPIR_NON_SAIC_NON_SAIC .............................................................................. 44-36
44-36

MC1425d - DISTRIB_4_SCPIR_NON_SAIC_NON_SAIC .............................................................................. 44-37


44-37

MC1426a - DISTRIB_1_SCPIR_NON_SAIC_SAIC ........................................................................................... 44-38


44-38

MC1426b - DISTRIB_2_SCPIR_NON_SAIC_SAIC ........................................................................................... 44-39


44-39

MC1426c - DISTRIB_3_SCPIR_NON_SAIC_SAIC ........................................................................................... 44-40


44-40

Resource Allocation & Management

Overview ................................................................................................................................................................................. 44-41


44-41

MC1401a - NB_TCH_REQ_NON_SAIC .................................................................................................................. 44-41


44-41

MC1401b - NB_TCH_REQ_SAIC ............................................................................................................................... 44-42


44-42

MC1401c - NB_TCH_REQ_VAMOS1 ...................................................................................................................... 44-42


44-42

MC1401d - NB_TCH_REQ_VAMOS2 ...................................................................................................................... 44-43


44-43

MC1402a - NB_TCH_PAIR_ATPT_NON_SAIC .................................................................................................. 44-43


44-43

MC1402b - NB_TCH_PAIR_ATPT_SAIC ............................................................................................................... 44-44


44-44

MC1402c - NB_TCH_PAIR_ATPT_VAMOS1 ....................................................................................................... 44-44


44-44

MC1402d - NB_TCH_PAIR_ATPT_VAMOS2 ....................................................................................................... 44-45


44-45

MC1403a - NB_TCH_PAIR_SUCC_NON_SAIC ................................................................................................. 44-45


44-45

MC1403b - NB_TCH_PAIR_SUCC_SAIC .............................................................................................................. 44-46


44-46

MC1403c - NB_TCH_PAIR_SUCC_VAMOS1 ...................................................................................................... 44-46


44-46

MC1403d - NB_TCH_PAIR_SUCC_VAMOS2 ...................................................................................................... 44-47


44-47

MC1427 - NB_MS_NON_SAIC_VAMOS_CAPABLE ....................................................................................... 44-47


44-47

45 Traffic Load

Radio Channel (Traffic Load)

Overview ................................................................................................................................................................................... 45-1


45-1

MC1424b - TIME_VAMOS_FR_TCH_BUSY .......................................................................................................... 45-1


45-1

MC1424c - TIME_VAMOS_HR_TCH_BUSY .......................................................................................................... 45-2


45-2

....................................................................................................................................................................................................................................
xxxiv Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
Part XXV: BSC-TYPE 110 - Overview measurements

46 Handover

Directed Retry

Overview ................................................................................................................................................................................... 46-1


46-1

MC151 - NB_INC_IDR_SUCC (29) .............................................................................................................................. 46-1


46-1

MC153 - NB_INC_IDR_REQ .......................................................................................................................................... 46-2


46-2

MC555 - NB_INC_IDR_PREP_FAIL_CONG_R_ABIS ....................................................................................... 46-2


46-2

Resource Allocation & Management

Overview ................................................................................................................................................................................... 46-4


46-4

MC480 - NB_TCH_HO_REQ_30_ReturnCSZone ................................................................................................... 46-4


46-4

MC481 - NB_TCH_HO_ATPT_30_ReturnCSZone ................................................................................................. 46-5


46-5

MC482 - NB_TCH_HO_REQ_30_ABORTED ......................................................................................................... 46-5


46-5

MC922g - NB_INC_EXT_TCH_3G_2G_HO_PREP_FAIL_3GCONG .......................................................... 46-6


46-6

MC929g - NB_INC_EXT_TCH_4G_2G_HO_PREP_FAIL_4GCONG .......................................................... 46-6


46-6

SDCCH

Overview ................................................................................................................................................................................... 46-8


46-8

MC101 - NB_INTRA_SDCCH_HO_PREP_FAIL_CONG .................................................................................. 46-8


46-8

MC607 - NB_SDCCH_HO_20_HighLevNeigCellForcDR ................................................................................... 46-9


46-9

MC81 - NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG ............................................................................... 46-9


46-9

MC91 - NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG .............................................................................. 46-10


46-10

SDCCH+TCH

Overview ................................................................................................................................................................................. 46-11


46-11

MC1040 - NB_HO_ATPT_23_TrafHandover .......................................................................................................... 46-13


46-13

MC1044 - NB_HO_ATPT_24_gencapture ................................................................................................................ 46-13


46-13

MC1050 - NB_HO_22_TooShortDistance ................................................................................................................ 46-14


46-14

MC642 - NB_INC_EXT_HO_SUCC .......................................................................................................................... 46-14


46-14

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xxxv
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC643 - NB_INC_EXT_HO_EXEC_FAIL_MS_ACCESS .............................................................................. 46-15
46-15

MC645a - NB_OUT_EXT_REAL_HO_REQ .......................................................................................................... 46-15


46-15

MC646 - NB_OUT_EXT_HO_SUCC ........................................................................................................................ 46-16


46-16

MC647 - NB_OUT_EXT_HO_EXEC_FAIL_REV ............................................................................................... 46-16


46-16

MC648 - NB_OUT_EXT_HO_EXEC_FAIL_NO_REV ..................................................................................... 46-17


46-17

MC650 - NB_OUT_EXT_HO_ATPT ......................................................................................................................... 46-17


46-17

MC652 - NB_INC_INT_HO_SUCC ........................................................................................................................... 46-18


46-18

MC653 - NB_INC_INT_HO_EXEC_FAIL_MS_ACCESS ............................................................................... 46-18


46-18

MC655a - NB_OUT_INT_HO_REQ .......................................................................................................................... 46-19


46-19

MC656 - NB_OUT_INT_HO_SUCC .......................................................................................................................... 46-19


46-19

MC657 - NB_OUT_INT_HO_EXEC_FAIL_REV ................................................................................................ 46-20


46-20

MC658 - NB_OUT_INT_HO_EXEC_FAIL_NO_REV ...................................................................................... 46-20


46-20

MC660 - NB_OUT_INT_HO_ATPT ........................................................................................................................... 46-21


46-21

MC662 - NB_INTRA_HO_SUCC ............................................................................................................................... 46-21


46-21

MC663 - NB_INTRA_HO_EXEC_FAIL_NO_REV ............................................................................................ 46-22


46-22

MC667 - NB_INTRA_HO_EXEC_FAIL_REV ...................................................................................................... 46-22


46-22

MC670 - NB_HO_2_TooLowQualUp ......................................................................................................................... 46-23


46-23

MC671 - NB_HO_3_TooLowLevUp ........................................................................................................................... 46-23


46-23

MC672 - NB_HO_4_TooLowQualDown ................................................................................................................... 46-24


46-24

MC673 - NB_HO_5_TooLowLevDown .................................................................................................................... 46-24


46-24

MC674 - NB_HO_6_TooLongDistance ...................................................................................................................... 46-25


46-25

MC675 - NB_HO_MSC_TRIG ..................................................................................................................................... 46-25


46-25

MC676 - NB_HO_15_TooHighLevInterfUp ............................................................................................................ 46-26


46-26

MC677 - NB_HO_16_TooHighLevInterfDown ...................................................................................................... 46-26


46-26

MC678 - NB_HO_12_TooLowPowBudg .................................................................................................................. 46-27


46-27

MC679 - NB_HO_21_HighLevNeigCellPrefBand ................................................................................................ 46-27


46-27

MC785a - NB_HO_7_ConsBadSACCHmicroCell ................................................................................................ 46-28


46-28
....................................................................................................................................................................................................................................
xxxvi Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC785d - NB_HO_17_TooLowLevUpMicroCell ................................................................................................. 46-28
46-28

MC785e - NB_HO_18_TooLowLevDownMicroCell ........................................................................................... 46-29


46-29

MC785f - NB_HO_14_HighLevNeigLowCellSlowMS ....................................................................................... 46-29


46-29

MC820 - NB_INC_EXT_HO_REQ ............................................................................................................................. 46-30


46-30

MC821 - NB_INC_EXT_HO_ATPT ........................................................................................................................... 46-30


46-30

MC830 - NB_INC_INT_HO_REQ .............................................................................................................................. 46-31


46-31

MC831 - NB_INC_INT_HO_ATPT ............................................................................................................................ 46-31


46-31

MC870 - NB_INTRA_HO_REQ .................................................................................................................................. 46-32


46-32

MC871 - NB_INTRA_HO_ATPT ................................................................................................................................. 46-32


46-32

MC922a - NB_INC_EXT_3G_2G_HO_REQ .......................................................................................................... 46-33


46-33

MC922b - NB_INC_EXT_3G_2G_HO_SUCC ...................................................................................................... 46-33


46-33

MC922c - NB_INC_EXT_3G_2G_HO_EXEC_FAIL_MS_ACC ................................................................... 46-34


46-34

MC922d - NB_INC_EXT_3G_2G_HO_ATPT ....................................................................................................... 46-34


46-34

MC929a - NB_INC_EXT_4G_2G_HO_REQ .......................................................................................................... 46-35


46-35

MC929b - NB_INC_EXT_4G_2G_HO_SUCC ...................................................................................................... 46-35


46-35

MC929c - NB_INC_EXT_4G_2G_HO_EXEC_FAIL_MS_ACC ................................................................... 46-36


46-36

MC929d - NB_INC_EXT_4G_2G_HO_ATPT ....................................................................................................... 46-37


46-37

Speech

Overview ................................................................................................................................................................................. 46-38


46-38

MC936 - NB_HO_INTER_TFO_AMR_WB ........................................................................................................... 46-38


46-38

MC937 - NB_HO_EXT_TFO_AMR_WB ................................................................................................................ 46-39


46-39

TCH

Overview ................................................................................................................................................................................. 46-40


46-40

MC41b - NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH ........................................................................ 46-41


46-41

MC448a - NB_TCH_HO_ATPT_26_BadQualHR ................................................................................................. 46-42


46-42

MC448b - NB_TCH_HO_ATPT_27_GoodQualFR ............................................................................................... 46-42


46-42

MC449 - NB_TCH_HO_ATPT_28_FastTraffic ...................................................................................................... 46-43


46-43
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xxxvii
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC460a - NB_TCH_EMERGENCY_HO_PRESERVATION .......................................................................... 46-43
46-43

MC461 - NB_TCH_HO_ATPT_29_TFO .................................................................................................................. 46-44


46-44

MC462a - NB_OUT_INTER_PLMN_TCH_HO_REQ ....................................................................................... 46-44


46-44

MC462b - NB_OUT_INTER_PLMN_TCH_HO_ATPT ..................................................................................... 46-45


46-45

MC462c - NB_OUT_INTER_PLMN_TCH_HO_SUCC .................................................................................... 46-45


46-45

MC463a - NB_INC_INTER_PLMN_TCH_HO_REQ ......................................................................................... 46-46


46-46

MC463b - NB_INC_INTER_PLMN_TCH_HO_ATPT ....................................................................................... 46-47


46-47

MC463c - NB_INC_INTER_PLMN_TCH_HO_SUCC ...................................................................................... 46-47


46-47

MC490a - NB_HO_INTRA_ATPT_33_MSC_trigg_int ...................................................................................... 46-48


46-48

MC490b - NB_HO_INTER_ATPT_33_MSC_trigg_int ....................................................................................... 46-48


46-48

MC541 - NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS .............................................................................. 46-49


46-49

MC541a - NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS ........................................................... 46-49


46-49

MC551 - NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS ............................................................... 46-50


46-50

MC561 - NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS ................................................................... 46-51


46-51

MC586a - NB_TCH_HO_ATPT_10_TooLowLevUpInZone ............................................................................. 46-51


46-51

MC586b - NB_TCH_HO_ATPT_11_TooLowLevDownInZone ....................................................................... 46-52


46-52

MC586c - NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone ............................................................. 46-52


46-52

MC710 - NB_TCH_OUT_HO_REQ_TRX ............................................................................................................... 46-53


46-53

MC922e - NB_INC_EXT_TCH_3G_2G_HO_EMERGENCY_REQ ............................................................ 46-54


46-54

MC922f - NB_INC_EXT_TCH_3G_2G_HO_REQ .............................................................................................. 46-54


46-54

MC924b - NB_OUT_2G_3G_HO_REQ .................................................................................................................... 46-55


46-55

MC924c - NB_OUT_2G_3G_HO_SUCC ................................................................................................................. 46-55


46-55

MC924d - NB_OUT_2G_3G_HO_ATPT .................................................................................................................. 46-56


46-56

MC924e - NB_OUT_2G_3G_HO_EXEC_FAIL_NO_REV .............................................................................. 46-56


46-56

MC924f - NB_OUT_2G_3G_HO_EXEC_FAIL_REV ........................................................................................ 46-57


46-57

MC924g - NB_OUT_2G_3G_HO_PREP_FAIL ..................................................................................................... 46-57


46-57

MC929e - NB_INC_EXT_TCH_4G_2G_HO_EMERGENCY_REQ ............................................................ 46-58


46-58
....................................................................................................................................................................................................................................
xxxviii Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC929f - NB_INC_EXT_TCH_4G_2G_HO_REQ .............................................................................................. 46-59
46-59

MC934 - NB_INC_EXT_TCH_HO_PREP_FAIL_PMIS ................................................................................... 46-59


46-59

MC975a - NB_BSS_Int_HO_with_MSC_REQ ...................................................................................................... 46-60


46-60

MC975b - NB_BSS_Int_HO_with_MSC_SUCC ................................................................................................... 46-60


46-60

MC975c - NB_BSS_Int_HO_with_MSC_ALLOC ................................................................................................ 46-61


46-61

MC975d - NB_BSS_Int_HO_with_MSC_ATPT .................................................................................................... 46-61


46-61

47 Quality of Service

BSC

Overview ................................................................................................................................................................................... 47-1


47-1

MC1614 - OLC_ NB_DISCARDED_CHN_REQD_ACCESS_DELAY ......................................................... 47-2


47-2

MC959 - NB_PS_CHAN_REQD .................................................................................................................................... 47-2


47-2

MC960 - NB_DISCARDED_PS_CHAN_REQD_BECAUSE_GSL_CONGESTION .............................. 47-3


47-3

MC962 - NB_INVALID_CHAN_REQD_RECEIVED_BY_BSC ..................................................................... 47-3


47-3

MC963 - NB_NON_PS_CHAN_REQD_DISCRADED_BECAUSE_CONGESTION ............................. 47-5


47-5

MC964 - NB_VALID_LOCATION_UPDATE_RECEIVED_BY_BSC .......................................................... 47-6


47-6

Directed Retry

Overview ................................................................................................................................................................................... 47-7


47-7

MC142e - NB_OUT_IDR_SUCC ................................................................................................................................... 47-7


47-7

MC142f - NB_OUT_EDR_SUCC .................................................................................................................................. 47-8


47-8

MC717a - NB_INC_IDR_SUCC_TRX ......................................................................................................................... 47-8


47-8

MC719a - NB_INC_IDR_SUCC_NON_AMR .......................................................................................................... 47-9


47-9

MC719b - NB_INC_IDR_SUCC_ALL_AMR ........................................................................................................... 47-9


47-9

Established Phase

Overview ................................................................................................................................................................................. 47-11


47-11

MC137 - NB_SDCCH_DROP_EST_PHAS_BSS_PB ......................................................................................... 47-11


47-11

MC138 - NB_SDCCH_DROP_EST_PHAS_RLF ................................................................................................. 47-12


47-12

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xxxix
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC14c - NB_TCH_DROP_EST_PHAS_BSS_PB ................................................................................................ 47-13
47-13

MC1610 - OLC_NB_TCH_DROP_EST_PHAS_RLF_TRX ............................................................................. 47-14


47-14

MC1611 - OLC_NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX ........................................... 47-14


47-14

MC1613 - OLC_NB_TCH_DROP_EST_PHAS_BSS_PB_TRX .................................................................... 47-15


47-15

MC162 - NB_TCH_DROP_DTAP_EST_PHAS ..................................................................................................... 47-16


47-16

MC736 - NB_TCH_DROP_EST_PHAS_RLF_TRX ............................................................................................ 47-17


47-17

MC739 - NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX .......................................................... 47-17


47-17

MC993 - NB_AMR_TCH_DROP_RLF_TRX ........................................................................................................ 47-18


47-18

MC994 - NB_AMR_TCH_DROP_RLF_TRX_RSACCH .................................................................................. 47-19


47-19

Handover

Overview ................................................................................................................................................................................. 47-20


47-20

MC03 - NB_OUT_SDCCH_HO_SUCC .................................................................................................................... 47-21


47-21

MC07 - NB_SDCCH_DROP_OUT_HO .................................................................................................................... 47-21


47-21

MC10 - NB_INC_SDCCH_HO_SUCC ...................................................................................................................... 47-22


47-22

MC14a - NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB ...................................................................... 47-22


47-22

MC1612 - OLC_NB_TCH_DROP_OUT_HO_EXEC_TRX ............................................................................. 47-24


47-24

MC621 - NB_TCH_DROP_OUT_HO_EXEC_TRX ............................................................................................ 47-25


47-25

MC711 - NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX ............................................................................... 47-25


47-25

MC712 - NB_TCH_OUT_HO_SUCC_TRX ............................................................................................................ 47-26


47-26

MC713 - NB_TCH_OUT_HO_FAIL_REV_TRX ................................................................................................. 47-27


47-27

MC714 - NB_TCH_OUT_HO_FAIL_NO_REV_TRX ........................................................................................ 47-28


47-28

MC717b - NB_INC_TCH_HO_SUCC_TRX ........................................................................................................... 47-28


47-28

MC719c - NB_INC_TCH_HO_SUCC_NON_AMR ............................................................................................ 47-29


47-29

MC719d - NB_INC_TCH_HO_SUCC_ALL_AMR ............................................................................................. 47-30


47-30

MC719e - NB_TCH_OUT_HO_SUCC_NON_AMR ........................................................................................... 47-31


47-31

MC719f - NB_TCH_OUT_HO_SUCC_ALL_AMR ............................................................................................ 47-32


47-32

MC719g - NB_INTRA_TCH_HO_SUCC_NON_AMR ...................................................................................... 47-33


47-33
....................................................................................................................................................................................................................................
xl Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC719h - NB_INTRA_TCH_HO_SUCC_ALL_AMR ....................................................................................... 47-33
47-33

MC719i - NB_INC_IDR_SUCC_RACCH ................................................................................................................ 47-34


47-34

MC719j - NB_INC_TCH_HO_SUCC_RACCH ..................................................................................................... 47-35


47-35

MC719k - NB_TCH_OUT_HO_SUCC_RACCH .................................................................................................. 47-35


47-35

MC719l - NB_INTRA_TCH_HO_SUCC_RACCH .............................................................................................. 47-36


47-36

MC995 - NB_AMR_TCH_DROP_OUT_HO_TRX .............................................................................................. 47-37


47-37

MC996 - NB_AMR_TCH_DROP_OUT_HO_TRX_RFACCH ........................................................................ 47-38


47-38

Interface (QoS)

Overview ................................................................................................................................................................................. 47-39


47-39

AIP11 - NB_BSC_RCVD_DL_RTP_PACKETS_OUT_OF_DELAY ............................................................ 47-40


47-40

AIP12 - NB_BSC_NOT_RCVD_DL_RTP_PACKETS ....................................................................................... 47-40


47-40

AIP50 - NB_SSRC_COLLISIONS .............................................................................................................................. 47-41


47-41

MC1113a - NB_N7_CON_EST_FAIL_DUE_NSS_Asig_IP ............................................................................. 47-41


47-41

MC1113b - NB_N7_CON_EST_FAIL_DUE_BSS_Asig_IP ............................................................................. 47-42


47-42

MC1204 - NB_TIMES_MSC_SELECTION_NRI ................................................................................................. 47-42


47-42

MC1205 - NB_TIMES_MSC_SELECTION_IMSI ............................................................................................... 47-43


47-43

MC1206 - NB_TIMES_MSC_SELECTION_LB ................................................................................................... 47-43


47-43

MC1207 - NB_TIMES_MSC_SELECTION_STORED ...................................................................................... 47-44


47-44

MC1307 - NB_ENH_RELOC_REQ_IURG ............................................................................................................. 47-44


47-44

MC1308 - NB_ENH_RELOC_RESP_IURG ........................................................................................................... 47-45


47-45

MC1309 - NB_ENH_RELOC_FAIL_IURG ............................................................................................................. 47-45


47-45

MC182 - NB_N7_CLEAR_REQ_EST_PHAS ........................................................................................................ 47-46


47-46

MC182a - NB_N7_CLEAR_REQ_EST_PHAS_CELL ....................................................................................... 47-47


47-47

LCS

Overview ................................................................................................................................................................................. 47-48


47-48

MC923a - NB_LCS_REQ ................................................................................................................................................ 47-49


47-49

MC923b - NB_LCS_SUCC ............................................................................................................................................. 47-49


47-49
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xli
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC923c - NB_LCS_FAIL_LB ...................................................................................................................................... 47-50
47-50

MC923d - NB_LCS_ABORT ......................................................................................................................................... 47-50


47-50

MC923e - NB_LCS_REQ_EM_LI ............................................................................................................................... 47-51


47-51

MC923f - NB_LCS_REQ_PLMN ................................................................................................................................ 47-51


47-51

MC923g - NB_LCS_REQ_VADD ................................................................................................................................ 47-52


47-52

MC923h - NB_LCS_REQ_POS_ESTIMATE .......................................................................................................... 47-52


47-52

MC942 - NB_LCS_RESET_TX .................................................................................................................................... 47-53


47-53

MC943 - NB_LCS_RESET_RX .................................................................................................................................... 47-53


47-53

MC946a - NB_LCS_COI_MS_POSITION_CMD_RX ....................................................................................... 47-54


47-54

MC946b - NB_LCS_COI_MS_POSITION_RESP_TX ....................................................................................... 47-54


47-54

MC946c - NB_LCS_COI__ABORT_TX ................................................................................................................... 47-55


47-55

MC946d - NB_LCS_COI_REJECT_TX .................................................................................................................... 47-55


47-55

MC946e - NB_LCS_LOC_ABORT_TIMEOUT_TX ........................................................................................... 47-56


47-56

MC946f - NB_LCS_INTERRUPTED_INTRA_BSC_HO_TX ........................................................................ 47-56


47-56

MC946g - NB_LCS_INTERRUPTED_INTER_BSC_HO_TX ........................................................................ 47-57


47-57

MC946h - NB_LCS_TA_REQUEST_RX ................................................................................................................. 47-57


47-57

MC965 - NB_LCS_INTERRUPTED_INTRA_BSC_HO ................................................................................... 47-58


47-58

MC966 - NB_LCS_INTERRUPTED_INTER_BSC_HO .................................................................................... 47-58


47-58

Repeated ACCH

Overview ................................................................................................................................................................................. 47-59


47-59

MC718g - NB_TCH_REP_FACCH_ASS_COMP ................................................................................................. 47-59


47-59

MC718h - NB_TCH_REP_SACCH_ASS_COMP ................................................................................................. 47-60


47-60

MC990 - NB_MS_REPEATED_ACCH_CAPABLE ............................................................................................ 47-60


47-60

MC991 - NB_CALLS_RFACCH_ACTIVATED .................................................................................................... 47-61


47-61

MC992 - NB_CALLS_RSACCH_ACTIVATED .................................................................................................... 47-61


47-61

Short Message Service

Overview ................................................................................................................................................................................. 47-62


47-62
....................................................................................................................................................................................................................................
xlii Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC191 - NB_SMS_PP_CON_MT_SDCCH ............................................................................................................ 47-62
47-62

MC196 - NB_SMS_PP_CON_SUCC ......................................................................................................................... 47-63


47-63

MC197 - NB_SMS_PP_CON_FAIL ............................................................................................................................ 47-63


47-63

Speech

Overview ................................................................................................................................................................................. 47-64


47-64

MC170 - NB_CALL_TFO ............................................................................................................................................... 47-64


47-64

MC935 - NB_CALL_TFO_AMR_WB ....................................................................................................................... 47-65


47-65

MC938 - NB_CALL_TFO_AMR_NB ........................................................................................................................ 47-65


47-65

MC939 - NB_HO_INTER_TFO_AMR_NB ............................................................................................................ 47-66


47-66

MC950 - NB_HO_EXT_TFO_AMR_NB ................................................................................................................. 47-67


47-67

TCH

Overview ................................................................................................................................................................................. 47-68


47-68

MC928a - NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_UL ............................................................. 47-68


47-68

MC928b - NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_UL ................................................................... 47-69


47-69

MC928c - NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_DL ............................................................. 47-70


47-70

MC928d - NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_DL ................................................................... 47-71


47-71

MC928e - NB_TCH_DROP_CAUSE_TOO_LONG_MS_BS_DISTANCE ............................................... 47-72


47-72

MC928f - NB_TCH_DROP_CAUSE_TOO_SHORT_MS_BS_DISTANCE .............................................. 47-73


47-73

MC928g - NB_TCH_DROP_CAUSE_TOO_HIGH_INTERFERENCE_UPLINK .................................. 47-74


47-74

MC928h - NB_TCH_DROP_CAUSE_TOO_HIGH_INTERFERENCE_DOWNLINK ........................ 47-75


47-75

MC928i - NB_TCH_DROP_OTHER_CAUSES .................................................................................................... 47-76


47-76

Telecom Procedure (QoS)

Overview ................................................................................................................................................................................. 47-78


47-78

MC01 - NB_IMM_ASS_SUCC_MT ........................................................................................................................... 47-79


47-79

MC02 - NB_IMM_ASS_SUCC_MO .......................................................................................................................... 47-80


47-80

MC02a - NB_IMM_ASS_SUCC_MO_LOC_UPD ............................................................................................... 47-80


47-80

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xliii
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC02b - NB_IMM_ASS_SUCC_MO_SMS ........................................................................................................... 47-81
47-81

MC02c - NB_IMM_ASS_SUCC_MO_SUP_SERV .............................................................................................. 47-81


47-81

MC02d - NB_IMM_ASS_SUCC_MO_FOLLOW_ON ....................................................................................... 47-82


47-82

MC02e - NB_IMM_ASS_SUCC_MO_CM_REEST ............................................................................................ 47-83


47-83

MC02f - NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW ............................................................................ 47-83


47-83

MC02g - NB_IMM_ASS_SUCC_MO_IMSI_DETACH ..................................................................................... 47-84


47-84

MC02h - NB_IMM_ASS_SUCC_MO_CALL_EST ............................................................................................. 47-84


47-84

MC02i - NB_IMM_ASS_SUCC_MO_LCS ............................................................................................................. 47-85


47-85

MC04 - NB_IMM_ASS_PREP_FAIL_CONG ........................................................................................................ 47-85


47-85

MC140a - NB_TCH_NOR_ASS_REQ ....................................................................................................................... 47-86


47-86

MC140b - NB_TCH_NOR_ASS_ATPT .................................................................................................................... 47-86


47-86

MC149 - NB_IMM_ASS_EXEC_FAIL_RADIO ................................................................................................... 47-87


47-87

MC1601 - OLC_NB_IMM_ASS_EXEC_FAIL_RADIO .................................................................................... 47-88


47-88

MC1602 - OLC_NB_TCH_NOR_ASS_SUCC_TRX ........................................................................................... 47-88


47-88

MC1603 - OLC_NB_TCH_NOR_ASS_ATPT ........................................................................................................ 47-89


47-89

MC1604 - OLC_NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX ........................................................... 47-89


47-89

MC161 - NB_DTAP_NOR_ASS_SUCC ................................................................................................................... 47-90


47-90

MC1701 - NB_REDIRECT_ATTEMPT .................................................................................................................... 47-90


47-90

MC1702 - NB_REDIRECT_COMMAND ................................................................................................................ 47-91


47-91

MC1703 - NB_REDIRECT_COMMAND_CS_PS_COORD ............................................................................ 47-91


47-91

MC1704 - NB_REDIRECT_COMPLETE ................................................................................................................ 47-92


47-92

MC1705 - NB_REDIRECT_COMPLETE_ MS_NOT ACCEPTED .............................................................. 47-92


47-92

MC1706 - NB_REDIRECT_COMPLETE_ MS_ALREADY_REG ............................................................... 47-93


47-93

MC19 - NB_TCH_NOR_ASS_HO_PREP_FAIL_ACHAN_MIS (110) ....................................................... 47-93


47-93

MC612a - NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE ........................................................................... 47-94


47-94

MC612b - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL ..................................................................... 47-95


47-95

MC612c - NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP ................................................................................. 47-95


47-95
....................................................................................................................................................................................................................................
xliv Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC612d - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ ......................................................................... 47-96
47-96

MC718 - NB_TCH_NOR_ASS_SUCC_TRX ......................................................................................................... 47-97


47-97

MC746b - NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX ........................................................................ 47-98


47-98

MC812 - NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS ...................................................................... 47-98


47-98

MC901 - NB_Suspend_Resume_req ............................................................................................................................ 47-99


47-99

MC902 - Nb_Suspend_fail ............................................................................................................................................ 47-100


47-100

MC903 - Nb_Suspend_succ .......................................................................................................................................... 47-100


47-100

MC921a - NB_TCH_NOR_ASS_HO_REQ_ABLE_TO_PREEMPT ......................................................... 47-101


47-101

MC921b - NB_PREEMPT_CAP_ALLOC_SUCC .............................................................................................. 47-101


47-101

MC921c - NB_PREEMPTED_CALLS .................................................................................................................... 47-102


47-102

MC921d - NB_PREEMPT_CAP_OUT_DR_ALLOC_SUCC ........................................................................ 47-102


47-102

MC921e - NB_TCH_NOR_ASS_HO_SUCC_PREEMPTABLE .................................................................. 47-103


47-103

MC933 - NB_TCH_NOR_ASS_PREP_FAIL_PMIS ......................................................................................... 47-104


47-104

48 Resource Availability & Usage

Channel

Overview ................................................................................................................................................................................... 48-1


48-1

MC141 - AV_NB_TCH_QUEUED ................................................................................................................................. 48-3


48-3

MC1605 - OLC_AV_NB_IDLE_TCH_INTERF_BAND1_TRX ....................................................................... 48-3


48-3

MC1606 - OLC_AV_NB_IDLE_TCH_INTERF_BAND2_TRX ....................................................................... 48-4


48-4

MC1607 - OLC_AV_NB_IDLE_TCH_INTERF_BAND3_TRX ....................................................................... 48-4


48-4

MC1608 - OLC_AV_NB_IDLE_TCH_INTERF_BAND4_TRX ....................................................................... 48-5


48-5

MC1609 - OLC_AV_NB_IDLE_TCH_INTERF_BAND5_TRX ....................................................................... 48-6


48-6

MC24 - AV_NB_NOT_AVAIL_TRX_TS .................................................................................................................... 48-6


48-6

MC250 - AV_NB_AVAIL_TCH ....................................................................................................................................... 48-7


48-7

MC26 - AV_NB_AVAIL_SDCCH ................................................................................................................................... 48-7


48-7

MC27 - AV_NB_AVAIL_CCCH ...................................................................................................................................... 48-8


48-8

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xlv
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC28a - AV_NB_BUSY_CS_TS .................................................................................................................................... 48-8
48-8

MC29a - NB_MAX_SIMUL_BUSY_CS_TS ............................................................................................................ 48-9


48-9

MC31 - NB_MAX_SIMUL_BUSY_SDCCH .......................................................................................................... 48-10


48-10

MC320a - AV_NB_IDLE_TCH_INTERF_BAND1 .............................................................................................. 48-10


48-10

MC320b - AV_NB_IDLE_TCH_INTERF_BAND2 .............................................................................................. 48-11


48-11

MC320c - AV_NB_IDLE_TCH_INTERF_BAND3 .............................................................................................. 48-12


48-12

MC320d - AV_NB_IDLE_TCH_INTERF_BAND4 .............................................................................................. 48-13


48-13

MC320e - AV_NB_IDLE_TCH_INTERF_BAND5 .............................................................................................. 48-14


48-14

MC320f - AV_NB_IDLE_TCH_INTERF_BAND1_TRX .................................................................................. 48-15


48-15

MC320g - AV_NB_IDLE_TCH_INTERF_BAND2_TRX .................................................................................. 48-16


48-16

MC320h - AV_NB_IDLE_TCH_INTERF_BAND3_TRX .................................................................................. 48-17


48-17

MC320i - AV_NB_IDLE_TCH_INTERF_BAND4_TRX ................................................................................... 48-17


48-17

MC320j - AV_NB_IDLE_TCH_INTERF_BAND5_TRX ................................................................................... 48-18


48-18

MC320k - AV_NB_IDLE_CHA_INTERF_BAND1_TRX ................................................................................. 48-18


48-18

MC320l - AV_NB_IDLE_CHA_INTERF_BAND2_TRX .................................................................................. 48-20


48-20

MC320m - AV_NB_IDLE_CHA_INTERF_BAND3_TRX ................................................................................ 48-21


48-21

MC320n - AV_NB_IDLE_CHA_INTERF_BAND4_TRX ................................................................................. 48-22


48-22

MC320o - AV_NB_IDLE_CHA_INTERF_BAND5_TRX ................................................................................. 48-23


48-23

MC34 - TIME_ALL_AVAIL_TRX_TS_BUSY ...................................................................................................... 48-24


48-24

MC35 - AV_NB_A_TRAF_CHAN_BLOCK_OUT_OF_SERV ....................................................................... 48-24


48-24

MC36 - AV_NB_AVAIL_A_TRAF_CHAN ............................................................................................................. 48-25


48-25

MC370a - NB_TRX_FR_ALLOC ................................................................................................................................ 48-26


48-26

MC370b - NB_TRX_HR_ALLOC ............................................................................................................................... 48-26


48-26

MC390 - NB_TIMES_SDCCH_BUSY (110) .......................................................................................................... 48-27


48-27

MC800 - AV_NB_AVAIL_DYN_TS ........................................................................................................................... 48-27


48-27

MC801a - AV_NB_BUSY_DYN_TCH ...................................................................................................................... 48-28


48-28

MC801b - MAX_NB_BUSY_DYN_TCH ................................................................................................................ 48-28


48-28
....................................................................................................................................................................................................................................
xlvi Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC802a - AV_NB_BUSY_DYN_SDCCH ............................................................................................................... 48-29
48-29

MC802b - MAX_NB_BUSY_DYN_SDCCH .......................................................................................................... 48-30


48-30

MC803 - TIME_SDCCH_CONGESTION ................................................................................................................ 48-30


48-30

Interface (Resource Availability)

Overview ................................................................................................................................................................................. 48-32


48-32

MN1.1 - TIME_N7_ALIGNED ..................................................................................................................................... 48-32


48-32

Resource Allocation & Management

Overview ................................................................................................................................................................................. 48-33


48-33

MC701a - NB_TCH_FR_REQ ....................................................................................................................................... 48-34


48-34

MC701b - NB_TCH_DR_REQ ...................................................................................................................................... 48-35


48-35

MC701c - NB_TCH_DR_EFR_REQ .......................................................................................................................... 48-35


48-35

MC701d - NB_TCH_AMR_REQ ................................................................................................................................. 48-36


48-36

MC701e - NB_TCH_DATA_REQ ................................................................................................................................ 48-36


48-36

MC701f - NB_TCH_FR_EFR_REQ ............................................................................................................................ 48-37


48-37

MC701g - NB_TCH_NO_FR_REQ ............................................................................................................................. 48-37


48-37

MC701i - NB_TCH_ATDM_REQ ............................................................................................................................... 48-38


48-38

MC701j - NB_TCH_AIP_REQ ...................................................................................................................................... 48-38


48-38

MC702a - NB_TCH_NOR_FR_ALLOC ................................................................................................................... 48-39


48-39

MC702b - NB_TCH_NOR_HR_ALLOC .................................................................................................................. 48-39


48-39

MC702c - NB_TCH_NOR_EFR_ALLOC ................................................................................................................ 48-40


48-40

MC704a - NB_TCH_NOR_AMR_FR_ALLOC ..................................................................................................... 48-40


48-40

MC704b - NB_TCH_NOR_AMR_HR_ALLOC .................................................................................................... 48-41


48-41

MC705 - NB_TCH_NOR_DATA_ALLOC .............................................................................................................. 48-41


48-41

MC706 - NB_EGSM_MS_ACCESS_EXCEPT_LU ............................................................................................. 48-42


48-42

MC718a - NB_TCH_FR_ASS_COMP ....................................................................................................................... 48-42


48-42

MC718b - NB_TCH_HR_ASS_COMP ...................................................................................................................... 48-43


48-43

MC718c - NB_TCH_EFR_ASS_COMP .................................................................................................................... 48-43


48-43
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xlvii
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC718d - NB_TCH_FR_AMR_ASS_COMP ......................................................................................................... 48-44
48-44

MC718e - NB_TCH_HR_AMR_ASS_COMP ........................................................................................................ 48-45


48-45

MC718f - NB_TCH_AMR_WB_GMSK_ASS_COMP ....................................................................................... 48-45


48-45

MC718i - NB_TCH_ATDM_REP ................................................................................................................................ 48-46


48-46

MC718j - NB_TCH_AIP_REP ...................................................................................................................................... 48-46


48-46

MC922h - TIME_3G_HOReject_HL ........................................................................................................................... 48-47


48-47

MC927a - NB_DTM_UL_TCH_ASS_ATPT ........................................................................................................... 48-47


48-47

MC927b - NB_DTM_DL_TCH_ASS_ATPT ........................................................................................................... 48-48


48-48

MC927c - NB_DTM_UL_PACKET_ASS_ATPT .................................................................................................. 48-48


48-48

MC927d - NB_DTM_DL_PACKET_ASS_ATPT .................................................................................................. 48-49


48-49

MC927e - NB_DTM_UL_TCH_ASS_EXEC_FAIL_RADIO ........................................................................... 48-49


48-49

MC927f - NB_DTM_DL_TCH_ASS_EXEC_FAIL_RADIO ........................................................................... 48-50


48-50

MC929h - TIME_4G_HOReject_HL ........................................................................................................................... 48-50


48-50

MC931 - NB_TCH_NOR_AMR_WB_GMSK_FR_ALLOC ............................................................................ 48-51


48-51

MC932 - NB_TCH_AMR_WB_GMSK_REQ ........................................................................................................ 48-51


48-51

MC951 - NB_TCH_A5_3_REQ .................................................................................................................................... 48-52


48-52

MC952 - NB_CIPHER_CMD_A5_3 ........................................................................................................................... 48-52


48-52

MC953 - NB_SUCC_CIPHER_CMD_A5_3 ........................................................................................................... 48-53


48-53

MC954 - NB_TCH_A5_3_ASS ..................................................................................................................................... 48-53


48-53

MC955 - NB_TCH_A5_3_ASS_NO_TRX ............................................................................................................... 48-54


48-54

MC956 - NB_ASS_HO_CMD_A5_3_NO_TRX .................................................................................................... 48-55


48-55

49 Sustainable & safety

Dynamic power allocation

Overview ................................................................................................................................................................................... 49-1


49-1

MC1208 - TIME_PWR_RED_8PSK_1 ........................................................................................................................ 49-2


49-2

MC1209 - TIME_PWR_RED_8PSK_2 ........................................................................................................................ 49-2


49-2

....................................................................................................................................................................................................................................
xlviii Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC1210 - TIME_PWR_RED_8PSK_3 ........................................................................................................................ 49-3
49-3

MC1211 - TIME_PWR_RED_8PSK_4 ......................................................................................................................... 49-4


49-4

MC1212 - TIME_PWR_RED_GMSK_1 ...................................................................................................................... 49-4


49-4

MC1213 - TIME_PWR_RED_GMSK_2 ...................................................................................................................... 49-5


49-5

MC1214 - TIME_PWR_RED_GMSK_3 ...................................................................................................................... 49-6


49-6

MC1215 - TIME_PWR_RED_GMSK_4 ...................................................................................................................... 49-6


49-6

MC1216 - TIME_PWR_RED_DEFENSE_1 .............................................................................................................. 49-7


49-7

MC1217 - TIME_PWR_RED_DEFENSE_2 .............................................................................................................. 49-8


49-8

MC1218 - TIME_PWR_RED_DEFENSE_3 .............................................................................................................. 49-9


49-9

MC1219 - TIME_PWR_RED_DEFENSE_4 .............................................................................................................. 49-9


49-9

MC1220 - TIME_8PSK_BURST_TRANSMISSION ........................................................................................... 49-10


49-10

MC1221 - TIME_GMSK_BURST_TRANSMISSION ........................................................................................ 49-11


49-11

MC1222 - TIME_DEFENSE_BURST_TRANSMISSION ................................................................................. 49-11


49-11

Power saving

Overview ................................................................................................................................................................................. 49-13


49-13

MC1201 - TIME_PA_BIAS_ON_TRX ...................................................................................................................... 49-13


49-13

MC957 - TIME_TS_BUSY ............................................................................................................................................. 49-14


49-14

MC958 - TIME_PA_BIAS_ON ..................................................................................................................................... 49-15


49-15

Temperature logging

Overview ................................................................................................................................................................................. 49-16


49-16

MC1200 - TRX_MAX_TEMPERATURE ................................................................................................................. 49-16


49-16

50 Traffic Load

BSC

Overview ................................................................................................................................................................................... 50-1


50-1

MC1540 - BSCHA00 ............................................................................................................................................................ 50-1


50-1

MC1541 - BSCHA01 ............................................................................................................................................................ 50-2


50-2

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R xlix
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC926 - TCH_BLOCKING_OCCURENCES_BSC .............................................................................................. 50-3
50-3

Interface (Traffic Load)

Overview ................................................................................................................................................................................... 50-4


50-4

AIP10a - NB_BSC_SENT_UL_RTP_KBYTES ........................................................................................................ 50-6


50-6

AIP10b - NB_BSC_SENT_UL_RTP_PACKETS ..................................................................................................... 50-6


50-6

AIP10c - NB_BSC_SENT_UL_RTP_BYTES_MAX_MN ................................................................................... 50-7


50-7

AIP10d - NB_BSC_RCVD_DL_RTP_KBYTES ...................................................................................................... 50-7


50-7

AIP10e - NB_BSC_RCVD_DL_RTP_PACKETS .................................................................................................... 50-8


50-8

AIP20a - NB_BSC_SENT_UL_MUXRTP_KBYTES ............................................................................................ 50-8


50-8

AIP20b - NB_BSC_SENT_UL_MUXRTP_PACKETS .......................................................................................... 50-9


50-9

AIP20c - NB_BSC_SENT_UL_MUXRTP_BYTES_MAX_MN ....................................................................... 50-9


50-9

AIP20d - NB_BSC_RCVD_DL_MUXRTP_KBYTES ........................................................................................ 50-10


50-10

AIP20e - NB_BSC_RCVD_DL_MUXRTP_PACKETS ...................................................................................... 50-10


50-10

AIP30a - NB_BSC_SENT_UL_RTCP_BYTES ...................................................................................................... 50-11


50-11

AIP30b - NB_BSC_SENT_UL_RTCP_PACKETS ................................................................................................ 50-11


50-11

AIP30c - NB_BSC_SENT_UL_RTCP_BYTES_MAX_MN ............................................................................. 50-12


50-12

AIP40 - NB_BSC_SENT_ALL_FLOW_BYTES_MAX_MN .......................................................................... 50-12


50-12

MC1060 - NB_GSL_MSG_SENT ................................................................................................................................ 50-13


50-13

MC1061 - NB_GSL_MSG_DISCARDED ................................................................................................................ 50-13


50-13

MC1062 - NB_GSL_MSG_RESENT ......................................................................................................................... 50-14


50-14

MC1063 - NB_GSL_MSG_RECEIVED .................................................................................................................... 50-14


50-14

MC1064 - NB_GSL_BYTES_SENT ........................................................................................................................... 50-15


50-15

MC1065 - MAX_NB_GSL_BYTES_SENT ............................................................................................................. 50-15


50-15

MC1066 - MAX_NB_GSL_MSG_SENT .................................................................................................................. 50-16


50-16

MC1067 - AVERAGE_NB_MSG_IN_GSL_QUEUE .......................................................................................... 50-16


50-16

MC1101 - NB_ASPUP_TX ............................................................................................................................................. 50-17


50-17

MC1102 - NB_ASPUP_RX ............................................................................................................................................. 50-17


50-17
....................................................................................................................................................................................................................................
l Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC1103 - NB_ASPDOWN_TX .................................................................................................................................... 50-18
50-18

MC1104 - NB_ASPDOWN_RX ................................................................................................................................... 50-18


50-18

MC1105 - NB_ASPACTIVE_TX ................................................................................................................................. 50-19


50-19

MC1106 - NB_ASPACTIVE_RX ................................................................................................................................. 50-19


50-19

MC1107 - NB_ASPINACTIVE_TX ............................................................................................................................ 50-20


50-20

MC1108 - NB_ASPINACTIVE_RX ........................................................................................................................... 50-20


50-20

MC1109 - NB_BSC_SENT_SS7_IP_BYTES_Asig_IP ....................................................................................... 50-21


50-21

MC1110 - NB_BSC_SENT_SS7_IP_PACKETS_Asig_IP ................................................................................. 50-21


50-21

MC1111 - NB_BSC_RESENT_SS7_IP_PACKETS_Asig_IP ........................................................................... 50-22


50-22

MC1112 - NB_BSC_SENT_SS7_IP_BYTES_MAX_MN_Asig_IP .............................................................. 50-22


50-22

MC1114 - NB_N7_UNIT_DATA_SENT_Asig_IP ................................................................................................ 50-23


50-23

MC1115 - NB_N7_UNIT_DATA_REC_Asig_IP ................................................................................................... 50-23


50-23

MC1116 - NB_N7_CON_REQ_SENT_Asig_IP ..................................................................................................... 50-24


50-24

MC1117 - NB_N7_CON_REQ_REC_Asig_IP ....................................................................................................... 50-24


50-24

MC1118 - NB_N7_CON_CONF_SENT_Asig_IP ................................................................................................. 50-25


50-25

MC1119 - NB_N7_CON_CONF_REC_Asig_IP .................................................................................................... 50-25


50-25

MC1120 - NB_N7_CON_REF_SENT_Asig_IP ..................................................................................................... 50-26


50-26

MC1121 - NB_N7_CON_REF_REC_Asig_IP ........................................................................................................ 50-26


50-26

MC1700 - TIME_A_CHANNELS_MSC_BUSY ................................................................................................... 50-27


50-27

MC350 - NB_N7_CON_REQ ........................................................................................................................................ 50-27


50-27

MC351 - NB_N7_CON_CONF ..................................................................................................................................... 50-28


50-28

MC940 - NB_A_PAGING_MSG .................................................................................................................................. 50-28


50-28

IP (Traffic Load)

Overview ................................................................................................................................................................................. 50-29


50-29

MC941 - NB_INIT_L3_MSG_CM_SERV_REQ_NRI_UNKNOWN ........................................................... 50-29


50-29

MC980 - NB_INIT_L3_MSG_PAGING_RESPONSE_NRI ............................................................................. 50-30


50-30

MC981 - NB_INIT_L3_MSG_IMSI_DETACH_IND_NRI ............................................................................... 50-30


50-30
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R li
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC982 - NB_INIT_L3_MSG_CM_RE_ESTABL_REQ_NRI ......................................................................... 50-31
50-31

MC983 - NB_INIT_L3_MSG_IMSI_ATTACH_NRI ........................................................................................... 50-31


50-31

MC984 - NB_INIT_L3_MSG_LOC_UPD_NRI ..................................................................................................... 50-32


50-32

MC985a - NB_INIT_L3_MSG_CM_SERV_REQ_SMS_NRI .......................................................................... 50-32


50-32

MC985b - NB_INIT_L3_MSG_CM_SERV_REQ_SUP_SERV_NRI ........................................................... 50-33


50-33

MC985c - NB_INIT_L3_MSG_CM_SERV_REQ_CALL_EST_NRI ........................................................... 50-33


50-33

MC985d - NB_INIT_L3_MSG_CM_SERV_REQ_LOC_SERV_NRI ........................................................... 50-34


50-34

MC985e - NB_INIT_L3_MSG_CM_SERV_REQ_OTHERS_NRI ................................................................ 50-34


50-34

Radio Channel (Traffic Load)

Overview ................................................................................................................................................................................. 50-36


50-36

MC1520 - BSCHE20 .......................................................................................................................................................... 50-37


50-37

MC1521 - BSCHE21 .......................................................................................................................................................... 50-38


50-38

MC1522 - BSCHE22 .......................................................................................................................................................... 50-39


50-39

MC1523 - BSCHE23 .......................................................................................................................................................... 50-40


50-40

MC1524 - BSCHE24 .......................................................................................................................................................... 50-41


50-41

MC1525 - BSCHE2x .......................................................................................................................................................... 50-42


50-42

MC1600 - OLC_NB_CHAN_REQD ........................................................................................................................... 50-43


50-43

MC380a - TIME_TRX_FR_BUSY .............................................................................................................................. 50-43


50-43

MC380b - TIME_TRX_HR_BUSY ............................................................................................................................. 50-44


50-44

MC380c - TIME_TRX_GSM_FR_BUSY ................................................................................................................. 50-44


50-44

MC380d - TIME_TRX_GSM_HR_BUSY ................................................................................................................ 50-45


50-45

MC380e - TIME_TRX_DCS_FR_BUSY .................................................................................................................. 50-46


50-46

MC380f - TIME_TRX_DCS_HR_BUSY .................................................................................................................. 50-46


50-46

MC381 - TIME_TRX_TCH_BUSY_BY_MULTIBAND_MS .......................................................................... 50-47


50-47

MC400 - TIME_TRX_SDCCH_BUSY ...................................................................................................................... 50-48


50-48

MC804a - NB_UL_SINGLE_BLOCK_SIG_RACH ............................................................................................. 50-48


50-48

MC804b - NB_UL_ONE_PHASE_SIG_RACH ..................................................................................................... 50-49


50-49
....................................................................................................................................................................................................................................
lii Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC805a - NB_CHANNEL_ASSIGN_DL_AGCH ................................................................................................ 50-49
50-49

MC805b - NB_CHANNEL_ASSIGN_DL_PCH .................................................................................................... 50-50


50-50

MC8a - NB_CELL_PAGING_CMD ........................................................................................................................... 50-50


50-50

MC8b - NB_CELL_IMM_ASS_CMD ....................................................................................................................... 50-51


50-51

MC8c - NB_CELL_CHAN_REQD .............................................................................................................................. 50-51


50-51

MC8d - NB_CELL_IMM_ASS_REJ .......................................................................................................................... 50-52


50-52

MC924a - TIME_SPDCH_LIMIT_HIGH_LOAD ................................................................................................. 50-52


50-52

MC925a - NB_AGCH_USEFUL_BLOCKS_SENT ............................................................................................. 50-53


50-53

MC925b - NB_PCH_USEFUL_BLOCKS_SENT ................................................................................................. 50-53


50-53

MC925c - NB_BUSY_RACH_SLOTS ...................................................................................................................... 50-54


50-54

MC925d - NB_CHANNEL_RQ_RADIO .................................................................................................................. 50-54


50-54

MC925e - NB_ASSIGN_CMD_RECEIVED_ABIS ............................................................................................. 50-55


50-55

MC925f - NB_ASSIGN_CMD_DISCARDED ....................................................................................................... 50-56


50-56

MC925g - NB_PAGING_CMD_RECEIVED_ABIS ............................................................................................ 50-56


50-56

MC925h - NB_PAGING_CMD_DISCARDED ...................................................................................................... 50-57


50-57

MC930 - NB_ABIS_PAGING_MESSAGE_RECEIVED ................................................................................... 50-58


50-58

MC961 - NB_CELL_CS_PAGING_WITH_IMSI .................................................................................................. 50-58


50-58

Telecom Procedure (Traffic Load)

Overview ................................................................................................................................................................................. 50-60


50-60

MC13a - NB_TCH_NOR_ASS_QUEUED ............................................................................................................... 50-60


50-60

MC13b - NB_INC_EXT_TCH_HO_QUEUED ...................................................................................................... 50-61


50-61

MC144e - NB_OUT_IDR_REQ .................................................................................................................................... 50-62


50-62

MC144f - NB_OUT_EDR_REQ ................................................................................................................................... 50-62


50-62

MC147 - NB_INC_SDCCH_HO_ALLOC ............................................................................................................... 50-63


50-63

MC148 - NB_IMM_ASS_ALLOC ............................................................................................................................... 50-63


50-63

MC15a - NB_INC_IDR_ALLOC ................................................................................................................................. 50-64


50-64

MC15b - NB_INC_TCH_HO_ALLOC ...................................................................................................................... 50-64


50-64
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R liii
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
MC703 - NB_TCH_NOR_ASS_ALLOC_TRX ...................................................................................................... 50-65
50-65

MC850 - NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL .............................................................. 50-65


50-65

Part XXVI: BSC-TYPE 180 - 2G Traffic flow measurements

51 Adjacency

BSC

Overview ................................................................................................................................................................................... 51-1


51-1

C400 - NB_ADJ_BSC_INC_HO_REQ ......................................................................................................................... 51-1


51-1

C401 - NB_ADJ_BSC_INC_HO_ATPT ....................................................................................................................... 51-2


51-2

C402 - NB_ADJ_BSC_INC_HO_SUCC ...................................................................................................................... 51-3


51-3

Part XXVII: MFS-GPRS Counters

52 Quality of service

Ater interface

P2a - NB_LAPD_INFO_FRAME_RESENT .............................................................................................................. 52-1


52-1

P2b - NB_LAPD_RNR_SENT ......................................................................................................................................... 52-2


52-2

P2c - NB_LAPD_RNR_REC ............................................................................................................................................ 52-2


52-2

P2d - NB_LAPD_EST ......................................................................................................................................................... 52-3


52-3

Gb interface

P3a - NB_BEAR_CHAN_FRAMES_DISC_INVALID_FCS .............................................................................. 52-4


52-4

P3b - NB_BEAR_CHAN_FRAMES_DISC_INVALID_ADDR ......................................................................... 52-4


52-4

P6a - NB_PVC_FRAMES_DISC_7_CONSEC_1 .................................................................................................... 52-5


52-5

P6b - NB_PVC_FRAMES_DISC_ZERO_INSER .................................................................................................... 52-5


52-5

P6c - NB_PVC_FRAMES_DISC_LENGTH_TOO_LARGE .............................................................................. 52-6


52-6

P6d - NB_PVC_FRAMES_DISC_LENGTH_TOO_SHORT .............................................................................. 52-6


52-6

GSL

P7a - NB_BSCGP_MSG_SENT ...................................................................................................................................... 52-7


52-7

P7b - NB_BSCGP_MSG_DISCARDED ...................................................................................................................... 52-7


52-7
....................................................................................................................................................................................................................................
liv Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P7c_1 - CUMULATED_TIME_ONGOING_QUEUE_A_FULL ....................................................................... 52-8
52-8

P7c_2 - CUMULATED_TIME_ONGOING_QUEUE_B_FULL ....................................................................... 52-8


52-8

P7d - NB_BSCGP_MSG_RESENT ............................................................................................................................... 52-9


52-9

P7e - NB_BSCGP_MSG_RECEIVED .......................................................................................................................... 52-9


52-9

P7f - NB_BSCGP_CHANNEL_REQ_RECEIVED ............................................................................................... 52-10


52-10

P7g - NB_BSCGP_BYTES_SENT .............................................................................................................................. 52-10


52-10

P7h - MAX_NB_BSCGP_BYTES_SENT ................................................................................................................ 52-11


52-11

P7i - MAX_NB_BSCGP_MSG_SENT ....................................................................................................................... 52-11


52-11

Radio interface

P105c - NB_DL_TBF_EST_FAIL_GPU_CONG ................................................................................................... 52-12


52-12

P105d - NB_UL_TBF_EST_FAIL_GPU_CONG ................................................................................................... 52-12


52-12

P105e - NB_DL_TBF_EST_FAIL_CPU_GPU ....................................................................................................... 52-13


52-13

P105f - NB_UL_TBF_EST_FAIL_CPU_GPU ........................................................................................................ 52-13


52-13

P105g - NB_DL_TBF_EST_FAIL_CONG_ATER ................................................................................................ 52-14


52-14

P105h - NB_UL_TBF_EST_FAIL_CONG_ATER ................................................................................................ 52-14


52-14

P105i - NB_DL_TBF_EST_FAIL_CONG_ABIS .................................................................................................. 52-15


52-15

P105j - NB_UL_TBF_EST_FAIL_CONG_ABIS .................................................................................................. 52-16


52-16

P105k - NB_DL_TBF_EST_FAIL_TOO_MANY_TBF ...................................................................................... 52-17


52-17

P105l - NB_UL_TBF_EST_FAIL_TOO_MANY_TBF ....................................................................................... 52-18


52-18

P105m - NB_DL_TBF_EST_FAIL_PTU_CONG .................................................................................................. 52-19


52-19

P105n - NB_UL_TBF_EST_FAIL_PTU_CONG ................................................................................................... 52-19


52-19

P105o - NB_DL_TBF_EST_FAIL_GPU_BUFFER_CONG ............................................................................. 52-20


52-20

P105p - NB_UL_TBF_EST_FAIL_GPU_BUFFER_CONG ............................................................................. 52-20


52-20

P106 - NB_TBF_EST_SUCC_GPU ............................................................................................................................ 52-21


52-21

P107 - NB_TBF_EST_REQ_GPU ............................................................................................................................... 52-21


52-21

P11 - NB_DL_TBF_REL_GB_PB_MStransDL ..................................................................................................... 52-22


52-22

P14 - NB_DL_TBF_EST_FAIL_CONG .................................................................................................................... 52-22


52-22
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R lv
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P146 - NB_DL_TBF_REL_PREEMPTradio ............................................................................................................ 52-23
52-23

P147 - NB_UL_TBF_REL_PREEMPTradio ............................................................................................................ 52-23


52-23

P15 - NB_DL_TBF_EST_FAIL_RADIO_PB .......................................................................................................... 52-24


52-24

P181a - NB_DL_TBF_REL_SIG .................................................................................................................................. 52-24


52-24

P181b - NB_UL_TBF_REL_SIG .................................................................................................................................. 52-25


52-25

P182a - NB_SERVING_INTER_BSS_NACC ......................................................................................................... 52-25


52-25

P182b - NB_SERVING_INTER_RAT_NACC ........................................................................................................ 52-26


52-26

P182c - NB_CONTROLLING_INTER_BSS_NACC ........................................................................................... 52-26


52-26

P182d - NB_RAN_INFO_REQ_INTER_BSS_NACC ......................................................................................... 52-27


52-27

P182e - TIME_RIM_NACC_PROC_SUCC ............................................................................................................. 52-27


52-27

P182f - NB_SERVING_INTER_LTE_NACC ......................................................................................................... 52-28


52-28

P200 - NB_DOWNGRADED_MOVING_RT_PFC .............................................................................................. 52-28


52-28

P203 - NB_DL_TBF_EST_FAIL_PTU_LOAD ...................................................................................................... 52-29


52-29

P204 - NB_UL_TBF_EST_FAIL_PTU_LOAD ...................................................................................................... 52-29


52-29

P207 - NB_DL_TBF_REL_DL_DELAYED ............................................................................................................ 52-30


52-30

P208 - NB_UL_TBF_REL_EXTENDED_UL ......................................................................................................... 52-30


52-30

P209 - TIME_SOURCE_NC2_CELL_RESEL ........................................................................................................ 52-31


52-31

P210 - TIME_TARGET_NC2_CELL_RESEL ........................................................................................................ 52-31


52-31

P211 - NB_TARGET_NC2_CELL_RESEL ............................................................................................................. 52-32


52-32

P212 - TIME_SOURCE_NACC_CELL_RESEL ................................................................................................... 52-33


52-33

P213 - NB_SOURCE_NACC_CELL_RESEL ........................................................................................................ 52-33


52-33

P214 - NB_UL_TBF_ENT_EXTENDED_UPLINK ............................................................................................. 52-34


52-34

P215 - NB_UL_TBF_RESUME_IN_EXTENDED_UPLINK ........................................................................... 52-34


52-34

P22 - NB_UL_TBF_NORM_REL ................................................................................................................................ 52-35


52-35

P220 - NB_MOVING_RT_PFC .................................................................................................................................... 52-35


52-35

P221 - NB_PCCO_ACK_UL_NC2_CELL_RESEL ............................................................................................. 52-36


52-36

P222 - NB_PCCO_ACK_DL_NC2_CELL_RESEL ............................................................................................. 52-36


52-36
....................................................................................................................................................................................................................................
lvi Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P223 - NB_PCCO_NC2_CELL_RESEL_DL_TBF ............................................................................................... 52-37
52-37

P224 - NB_FLUSH_NC2_CELL_RESEL_DL_TBF ............................................................................................ 52-37


52-37

P225 - NB_PCCF_NC2_CELL_RESEL_DL_TBF ............................................................................................... 52-38


52-38

P226 - NB_PCCO_NC2_CELL_RESEL_UL_TBF ............................................................................................... 52-38


52-38

P227 - NB_FLUSH_NC2_CELL_RESEL_UL_TBF ............................................................................................ 52-39


52-39

P228 - NB_PCCF_NC2_CELL_RESEL_UL_TBF ............................................................................................... 52-39


52-39

P229 - NB_RT_PFC_PREEMPTED ............................................................................................................................ 52-40


52-40

P22a - NB_UL_TBF_NORM_REL_EGPRS ............................................................................................................ 52-40


52-40

P231 - NB_DOWNGRADED_RT_PFC_DEFENCE ............................................................................................ 52-41


52-41

P232 - NB_MOVING_RT_PFC_TARGET ............................................................................................................... 52-41


52-41

P24 - NB_UL_TBF_REL_GB_PB_MStransUL ..................................................................................................... 52-42


52-42

P27 - NB_UL_TBF_EST_FAIL_CONG .................................................................................................................... 52-42


52-42

P28 - NB_UL_TBF_EST_FAIL_RADIO_PB .......................................................................................................... 52-43


52-43

P302b_1 - NB_DL_TBF_REL_DUE_TO_RADIO_FAILURE_N3105 ........................................................ 52-43


52-43

P302b_2 - NB_DL_TBF_REL_DUE_TO_RADIO_FAILURE_TX_EFF .................................................... 52-44


52-44

P302c_1 - NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N3101 ......................................................... 52-44


52-44

P302c_2 - NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N3103 ......................................................... 52-45


52-45

P302c_3 - NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_TX_EFF .................................................... 52-45


52-45

P302c_4 - NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N_POLLING_EUTM .......................... 52-46


52-46

P303a - NB_ABNORMAL_DL_TBF_REL .............................................................................................................. 52-46


52-46

P303b - NB_ABNORMAL_UL_TBF_REL ............................................................................................................. 52-47


52-47

P30a - NB_UL_TBF_EST_SUCC_MSidle_MastChan ........................................................................................ 52-48


52-48

P30b - NB_UL_TBF_EST_SUCC_MStransDL ...................................................................................................... 52-48


52-48

P30c - NB_UL_TBF_EST_SUCC_MSidle_NO_MastChan .............................................................................. 52-49


52-49

P30e - NB_UL_TBF_EST_SUCC_EGPRS_MStransDL .................................................................................... 52-49


52-49

P385a - NB_DL_TBF_REL_STAGWINDOW ........................................................................................................ 52-50


52-50

P385b - NB_UL_TBF_REL_STAGWINDOW ....................................................................................................... 52-50


52-50
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R lvii
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P396a - NB_RLC_DL_TBF_RELEASE_REQ_FOR_CR .................................................................................. 52-51
52-51

P396b - NB_RLC_UL_TBF_RELEASE_REQ_FOR_CR .................................................................................. 52-51


52-51

P397 - NB_FLUSH_MESSAGES ................................................................................................................................. 52-52


52-52

P403a - NB_DL_RES_REALLOC_REQ_T1 ........................................................................................................... 52-52


52-52

P403b - NB_DL_RES_REALLOC_REQ_T2 .......................................................................................................... 52-53


52-53

P403c - NB_DL_RES_REALLOC_REQ_T3 ........................................................................................................... 52-54


52-54

P403d - NB_DL_RES_REALLOC_REQ_T4 .......................................................................................................... 52-54


52-54

P404a - NB_UL_RES_REALLOC_REQ_T1 ........................................................................................................... 52-55


52-55

P404b - NB_UL_RES_REALLOC_REQ_T2 .......................................................................................................... 52-56


52-56

P404c - NB_UL_RES_REALLOC_REQ_T3 ........................................................................................................... 52-56


52-56

P404d - NB_UL_RES_REALLOC_REQ_T4 .......................................................................................................... 52-57


52-57

P405a - NB_DL_RES_REALLOC_SUCC_T1 ....................................................................................................... 52-58


52-58

P405b - NB_DL_RES_REALLOC_SUCC_T2 ....................................................................................................... 52-58


52-58

P405c - NB_DL_RES_REALLOC_SUCC_T3 ....................................................................................................... 52-59


52-59

P405d - NB_DL_RES_REALLOC_SUCC_T4 ....................................................................................................... 52-60


52-60

P406a - NB_UL_RES_REALLOC_SUCC_T1 ....................................................................................................... 52-60


52-60

P406b - NB_UL_RES_REALLOC_SUCC_T2 ....................................................................................................... 52-61


52-61

P406c - NB_UL_RES_REALLOC_SUCC_T3 ....................................................................................................... 52-62


52-62

P406d - NB_UL_RES_REALLOC_SUCC_T4 ....................................................................................................... 52-62


52-62

P407a - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T1 ..................................................................... 52-63


52-63

P407b - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T2 .................................................................... 52-63


52-63

P407c - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T3 ..................................................................... 52-64


52-64

P407d - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T4 .................................................................... 52-64


52-64

P408a - NB_UL_TBF_REL_RADIO_PB_RES_REALLOC_T1 ..................................................................... 52-65


52-65

P408b - NB_UL_TBF_REL_RADIO_PB_RES_REALLOC_T2 .................................................................... 52-65


52-65

P408c - NB_UL_TBF_RADIO_PB_RES_REALLOC_T3 ................................................................................. 52-66


52-66

P408d - NB_UL_TBF_RADIO_PB_RES_REALLOC_T4 ................................................................................ 52-67


52-67
....................................................................................................................................................................................................................................
lviii Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P422 - NB_DL_TBF_TRANSFER_RESUMPTION_IN_DELAYED_REL_STATE .............................. 52-67
52-67

P423a - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T1 ....................................................... 52-68


52-68

P423b - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T2 ....................................................... 52-68


52-68

P423c - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T3 ....................................................... 52-69


52-69

P423d - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T4 ....................................................... 52-69


52-69

P424a - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T1 ....................................................... 52-70


52-70

P424b - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T2 ....................................................... 52-70


52-70

P424c - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T3 ....................................................... 52-71


52-71

P424d - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T4 ....................................................... 52-71


52-71

P425a - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T1 ....................................................................... 52-72


52-72

P425b - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T2 ....................................................................... 52-72


52-72

P425c - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T3 ....................................................................... 52-73


52-73

P425d - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T4 ....................................................................... 52-73


52-73

P426a - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T1 ....................................................................... 52-74


52-74

P426b - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T2 ....................................................................... 52-74


52-74

P426c - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T3 ....................................................................... 52-75


52-75

P426d - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T4 ....................................................................... 52-76


52-76

P431b - MAX_SOURCE_NC2_CELL_RESEL_TIME ....................................................................................... 52-76


52-76

P431c - MIN_SOURCE_NC2_CELL_RESEL_TIME ......................................................................................... 52-77


52-77

P432b - MAX_TARGET_NC2_CELL_RESEL_TIME ....................................................................................... 52-77


52-77

P432c - MIN_TARGET_NC2_CELL_RESEL_TIME .......................................................................................... 52-78


52-78

P433a - NB_NC2_CELL_RESEL_REQ_PT1 ......................................................................................................... 52-78


52-78

P433b - NB_NC2_CELL_RESEL_REQ_PT2 ......................................................................................................... 52-79


52-79

P433c - NB_NC2_CELL_RESEL_REQ_PT3 ......................................................................................................... 52-79


52-79

P433d - NB_NC2_CELL_RESEL_REQ_PT4 ......................................................................................................... 52-80


52-80

P434a - NB_NC2_UL_TBF_RELEASE .................................................................................................................... 52-80


52-80

P434b - NB_NC2_DL_TBF_RELEASE .................................................................................................................... 52-81


52-81
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R lix
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P434c - NB_NC0_UL_TBF_RELEASE .................................................................................................................... 52-81
52-81

P434d - NB_NC0_DL_TBF_RELEASE .................................................................................................................... 52-82


52-82

P435a - NB_NC2_CELL_RESEL_SUCC_PT1 ...................................................................................................... 52-82


52-82

P435b - NB_NC2_CELL_RESEL_SUCC_PT2 ...................................................................................................... 52-83


52-83

P435c - NB_NC2_CELL_RESEL_SUCC_PT3 ...................................................................................................... 52-83


52-83

P435d - NB_NC2_CELL_RESEL_SUCC_PT4 ...................................................................................................... 52-84


52-84

P436 - NB_NC0_CELL_RESEL_Mstrans ................................................................................................................ 52-84


52-84

P437a - NB_NC2_CELL_RESEL_FAIL_REJECT_CELL ................................................................................ 52-85


52-85

P437b - NB_NC2_CELL_RESEL_FAIL_NO_REJECT_CELL ....................................................................... 52-85


52-85

P440a - NB_REROUTING_INTRA_NSE ................................................................................................................ 52-86


52-86

P440b - NB_REROUTING_INTER_NSE_INTRA_BSS .................................................................................... 52-86


52-86

P440c - NB_REROUTING_INTER_NSE_INTER_BSS .................................................................................... 52-87


52-87

P441a - NB_IMPOSSIBLE_OR_UNREQUESTED_REROUTING_INR ................................................... 52-87


52-87

P441b - NB_UNREQUESTED_REROUTING_NOT_INR ............................................................................... 52-88


52-88

P441c - NB_IMPOSSIBLE_REROUTING_NOT_INR ....................................................................................... 52-88


52-88

P456 - NB_PSI_PROC ...................................................................................................................................................... 52-89


52-89

P458 - NB_NEIGH_PSI_PROC .................................................................................................................................... 52-89


52-89

P460b - MAX_SOURCE_NACC_CELL_RESEL_TIME ................................................................................... 52-90


52-90

P460c - MIN_SOURCE_NACC_CELL_RESEL_TIME ..................................................................................... 52-90


52-90

P463 - NB_PFC_DOWNLOAD .................................................................................................................................... 52-91


52-91

P464 - NB_NC2_CELL_RESEL_FAIL_LOAD ..................................................................................................... 52-91


52-91

P488 - NB_RT_DL_TBF .................................................................................................................................................. 52-92


52-92

P489 - NB_RT_UL_TBF .................................................................................................................................................. 52-92


52-92

P490 - NB_UNACK_NRT_PFC_CREATION ......................................................................................................... 52-93


52-93

P491 - NB_UNACK_RT_PFC_CREATION ............................................................................................................ 52-93


52-93

P492 - NB_DOWNGRADED_RT_PFC ..................................................................................................................... 52-94


52-94

P493 - NB_PFC_REJECTED ......................................................................................................................................... 52-94


52-94
....................................................................................................................................................................................................................................
lx Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P494 - NB_PFC_DOWNLOAD_FAIL ....................................................................................................................... 52-95
52-95

P497 - NB_RT_PFC_CREATION ................................................................................................................................ 52-95


52-95

P498 - NB_NRT_PFC_CREATION ............................................................................................................................. 52-96


52-96

P499 - NB_RT_PFC_CREATION_OK ....................................................................................................................... 52-96


52-96

P500 - NB_DTM_CAPABLE_MS_CONTEXT_GPU ......................................................................................... 52-97


52-97

P501 - NB_DTM_MS_CONTEXT_CELL ............................................................................................................... 52-97


52-97

P502 - CUMULATED_DTM_TIME ........................................................................................................................... 52-98


52-98

P503 - CUMULATED_DTM_DEDICATED_TIME ............................................................................................. 52-98


52-98

P504 - CUMULATED_DTM_PTM_TIME ............................................................................................................... 52-99


52-99

P505 - NB_DTM_DL_TBF_EST_REQ ..................................................................................................................... 52-99


52-99

P505a - NB_DTM_DL_TBF_EST_REQ_EGPRS ............................................................................................... 52-100


52-100

P506 - NB_DTM_DL_TBF_EST_SUCC ................................................................................................................ 52-100


52-100

P506a - NB_DTM_DL_TBF_EST_SUCC_EGPRS ............................................................................................ 52-101


52-101

P507 - NB_DTM_UL_TBF_EST_REQ ................................................................................................................... 52-101


52-101

P507a - NB_DTM_UL_TBF_EST_REQ_EGPRS ............................................................................................... 52-102


52-102

P508 - NB_DTM_UL_TBF_EST_SUCC ................................................................................................................ 52-102


52-102

P508a - NB_DTM_UL_TBF_EST_SUCC_EGPRS ............................................................................................ 52-103


52-103

P509 - NB_DTM_CS_DL_TBF_RELEASE .......................................................................................................... 52-103


52-103

P509a - NB_DTM_CS_DL_TBF_RELEASE_EGPRS ...................................................................................... 52-104


52-104

P510 - NB_DTM_CS_UL_TBF_RELEASE .......................................................................................................... 52-104


52-104

P510a - NB_DTM_CS_UL_TBF_RELEASE_EGPRS ...................................................................................... 52-105


52-105

P511 - NB_DTM_DL_TBF_FAIL_CONG ............................................................................................................. 52-106


52-106

P512 - NB_DTM_UL_TBF_FAIL_CONG ............................................................................................................. 52-106


52-106

P513 - NB_UL_LLC_BYTES_GTTP ....................................................................................................................... 52-107


52-107

P514 - NB_DL_LLC_BYTES_GTTP ....................................................................................................................... 52-107


52-107

P515 - NB_RT_PFC_CREATION_DTM_DEDICATED .................................................................................. 52-108


52-108

P516 - NB_RT_PFC_DOWNGRADED_DTM_DEDICATED ...................................................................... 52-108


52-108
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R lxi
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P518 - NB_RT_PFC_CREATION_DTM_MODE ............................................................................................... 52-109
52-109

P519 - NB_RT_PFC_DOWNGRADED_DTM_MODE .................................................................................... 52-109


52-109

P520 - NB_DL_TBF_EST_FAIL_DTM .................................................................................................................. 52-110


52-110

P521 - NB_UL_TBF_EST_FAIL_DTM .................................................................................................................. 52-110


52-110

P540b - NB_REFUSED_RT_PFC_LACK_BANDWIDTH ............................................................................. 52-111


52-111

P540c - NB_REFUSED_RT_PFC_LACK_RADIO ............................................................................................ 52-111


52-111

P540d - MAX_DL_GBR_BW_GRANTED ........................................................................................................... 52-112


52-112

P540e - MAX_UL_GBR_BW_GRANTED ............................................................................................................ 52-112


52-112

P552 - NB_UL_TBF_REL_UL_LLC_PDU_SEQ_FLOW_PB ...................................................................... 52-113


52-113

P594 - NB_EDA_MS_CONTEXT_GPU ................................................................................................................ 52-113


52-113

P595 - CUMULATED_TIME_ACTIVE_UL_CONNECTED_TIME_EDA_MODE ............................ 52-114


52-114

P596 - NB_EDA_USED_UL_TBF ............................................................................................................................ 52-115


52-115

P597 - NB_EDA_ALLOWED_UL_TBF ................................................................................................................ 52-115


52-115

P598 - NB_DA_EDA_REALLOC_UL_TBF ........................................................................................................ 52-116


52-116

P62a - NB_UL_TBF_EST_REQ_MSidle_MastChan ......................................................................................... 52-116


52-116

P62b - NB_UL_TBF_EST_REQ_MStransDL ....................................................................................................... 52-117


52-117

P62c - NB_UL_TBF_EST_REQ_MSidle_NO_MastChan ............................................................................... 52-117


52-117

P62e - NB_UL_TBF_EST_REQ_EGPRS_MStransDL ..................................................................................... 52-118


52-118

P65 - NB_DL_TBF_EST_FAIL_GB_PB ................................................................................................................ 52-119


52-119

P66 - NB_UL_TBF_EST_FAIL_GB_PB ................................................................................................................ 52-119


52-119

P9 - NB_DL_TBF_NORM_REL ................................................................................................................................ 52-120


52-120

P90a - NB_DL_TBF_EST_SUCC_MS_Idle_DRX_MPDCH ......................................................................... 52-120


52-120

P90b - NB_DL_TBF_EST_SUCC_MS_Transfer_UL ....................................................................................... 52-121


52-121

P90c - NB_DL_TBF_EST_SUCC_MS_IDLE_DRX_NO_MPDCH ........................................................... 52-121


52-121

P90d - NB_DL_TBF_EST_SUCC_MS_Non_DRX_MPDCH ....................................................................... 52-122


52-122

P90e - NB_DL_TBF_EST_SUCC_T3192 .............................................................................................................. 52-122


52-122

P90f - NB_DL_TBF_EST_SUCC_MS_Non_DRX_NO_MPDCH ............................................................... 52-123


52-123
....................................................................................................................................................................................................................................
lxii Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P90h - NB_DL_TBF_EST_SUCC_EGPRS_MS_Transfer_UL ..................................................................... 52-123
52-123

P90i - NB_DL_TBF_EST_SUCC_EGPRS_T3192 ............................................................................................. 52-124


52-124

P91a - NB_DL_TBF_EST_REQ_MS_IDLE_DRX_MPDCH ........................................................................ 52-124


52-124

P91b - NB_DL_TBF_EST_REQ_MS_Transfer_UL .......................................................................................... 52-125


52-125

P91c - NB_DL_TBF_EST_REQ_MS_IDLE_DRX_NO_MPDCH .............................................................. 52-125


52-125

P91d - NB_DL_TBF_EST_REQ_MS_Non_DRX_MPDCH ........................................................................... 52-126


52-126

P91e - NB_DL_TBF_EST_REQ_T3192 ................................................................................................................. 52-126


52-126

P91f - NB_DL_TBF_EST_REQ_MS_Non_DRX_NO_MPDCH .................................................................. 52-127


52-127

P91h - NB_DL_TBF_EST_REQ_EGPRS_MS_Transfer_UL ........................................................................ 52-127


52-127

P91i - NB_DL_TBF_EST_REQ_EGPRS_T3192 ................................................................................................ 52-128


52-128

P98a - NB_DL_TBF_REL_SUSP .............................................................................................................................. 52-128


52-128

P98b - NB_UL_TBF_REL_SUSP .............................................................................................................................. 52-129


52-129

P98c - NB_SUSPEND_REQ_FOR_DL_TBF ....................................................................................................... 52-129


52-129

P98d - NB_SUSPEND_REQ_FOR_UL_TBF ....................................................................................................... 52-130


52-130

P98e - NB_SUSP_DL_TBF_REL .............................................................................................................................. 52-130


52-130

P98f - NB_SUSP_UL_TBF_REL ............................................................................................................................... 52-131


52-131

P9a - NB_DL_TBF_NORM_REL_EGPRS ............................................................................................................ 52-131


52-131

53 Resource availability and usage

Abis interface

P465 - MAX_NB_USED_EXTRA_BONUS_ABIS_NIBBLES ......................................................................... 53-1


53-1

P466 - CUMULATED_TIME_USED_EXTRA_BONUS_ABIS_NIBBLES ................................................. 53-2


53-2

P472 - CUMULATED_TIME_FREE_EXTRA_BONUS_ABIS_NIBBLES ................................................. 53-2


53-2

P484 - MIN_NB_FREE_EXTRA_BONUS_ABIS_NIBBLE .............................................................................. 53-3


53-3

Ater interface

P100c - CUMULATED_TIME_BUSY_GCH_CELL .............................................................................................. 53-4


53-4

P100d - MAX_NB_BUSY_GCH_CELL ...................................................................................................................... 53-4


53-4

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R lxiii
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P100e - MIN_NB_BUSY_GCH_CELL ........................................................................................................................ 53-5
53-5

P100f - MAX_NB_GCH_BUSY_GPU ......................................................................................................................... 53-6


53-6

P101 - CUMULATED_TIME_AVAIL_GCH_GPU ................................................................................................. 53-6


53-6

P32 - TIME_LAPD_NOT_AVAIL .................................................................................................................................. 53-7


53-7

P383a - TIME_ATERMUX_CONG ............................................................................................................................... 53-7


53-7

P383b - TIME_HIGH_ATER_USAGE ......................................................................................................................... 53-8


53-8

P469 - MAX_NB_DEFICIT_GCH ................................................................................................................................. 53-8


53-8

P470 - CUMULATED_TIME_DEFICIT_GCH ...................................................................................................... 53-10


53-10

P471 - CUMULATED_TIME_EXCESS_GCH ....................................................................................................... 53-11


53-11

P474 - CUMULATED_TIME_FREE_ATER_NIBBLES .................................................................................... 53-12


53-12

P486 - MIN_NB_FREE_ATER_NIBBLE ................................................................................................................. 53-12


53-12

P80a - CUMULATED_TIME_ATER_CONG .......................................................................................................... 53-13


53-13

P80b - CUMULATED_TIME_NON_ATER_CONG ............................................................................................ 53-13


53-13

P81a - DL_BLKS_NOT_FULLY_SCHEDULED_ATER_CONG .................................................................. 53-14


53-14

P81b - DL_BLKS_SCHEDULED_ATER_CONG ................................................................................................. 53-14


53-14

P82a - UL_BLKS_NOT_FULLY_SCHEDULED_ATER_CONG .................................................................. 53-15


53-15

P82b - UL_BLKS_SCHEDULED_ATER_CONG ................................................................................................. 53-16


53-16

P83a - CUMULATED_MISSING_GCH_DL_ATER_CONG ........................................................................... 53-16


53-16

P83b - CUMULATED_ESTABLISHED_GCH_DL_ATER ............................................................................... 53-17


53-17

P84a - CUMULATED_MISSING_GCH_UL_ATER_CONG ........................................................................... 53-17


53-17

P84b - CUMULATED_ESTABLISHED_GCH_UL_ATER ............................................................................... 53-18


53-18

P85 - UL_BLKS_DISCARDED_BY_BTS_ATER_CONG ............................................................................... 53-18


53-18

P87a - ATER_EQUITY_REALLOCATED_GCH .................................................................................................. 53-19


53-19

P87b - ATER_EQUITY_MIN_RATIO_TBF_PER_GCH .................................................................................... 53-19


53-19

P87c - ATER_EQUITY_MAX_RATIO_TBF_PER_GCH .................................................................................. 53-20


53-20

P87d - ATER_EQUITY_AVG_RATIO_TBF_PER_GCH ................................................................................... 53-20


53-20

P87e - ATER_EQUITY_TIME_TARGET_NOT_REACHED .......................................................................... 53-21


53-21
....................................................................................................................................................................................................................................
lxiv Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P88a - ATER_EQUITY_MIN_RATIO_GPU_GCH_NEEDS ............................................................................ 53-21
53-21

P88b - ATER_EQUITY_MAX_RATIO_GPU_GCH_NEEDS .......................................................................... 53-22


53-22

P88c - ATER_EQUITY_AVG_RATIO_GPU_GCH_NEEDS ............................................................................ 53-22


53-22

Gb interface

P33 - TIME_BEAR_CHAN_NOT_AVAIL ............................................................................................................... 53-23


53-23

P34 - TIME_PVC_NOT_AVAIL ................................................................................................................................... 53-23


53-23

P34a - TIME_SGSN_IP_ENDPOINT_NOT_AVAIL_GBIP .............................................................................. 53-24


53-24

P4 - TIME_PVC_CONG_FRAME_RELAY ............................................................................................................ 53-24


53-24

P5 - TIME_PVC_CONG_LEVEL1 .............................................................................................................................. 53-25


53-25

P67 - TIME_BVC_NOT_AVAIL .................................................................................................................................. 53-25


53-25

Radio interface

P129a - CUMULATED_ACTIVE_UL_CONNECTED_TIME_GPRS_ACK ............................................. 53-26


53-26

P129b - CUMULATED_ACTIVE_UL_CONNECTED_TIME_GPRS_NACK ......................................... 53-27


53-27

P129c - CUMULATED_ACTIVE_UL_CONNECTED_TIME_EGPRS_ACK ......................................... 53-28


53-28

P129d - CUMULATED_ACTIVE_UL_CONNECTED_TIME_EGPRS_NACK ...................................... 53-29


53-29

P13 - TIME_DL_PDCH_CONG ................................................................................................................................... 53-30


53-30

P16 - CUMULATED_OVERALL_DL_CONNECTION_TIME ...................................................................... 53-30


53-30

P160 - NB_DL_TBF_1_succ .......................................................................................................................................... 53-32


53-32

P161 - NB_UL_TBF_1_succ .......................................................................................................................................... 53-32


53-32

P162 - NB_DL_TBF_2_3_succ ..................................................................................................................................... 53-33


53-33

P163 - NB_UL_TBF_2_3_succ ..................................................................................................................................... 53-33


53-33

P164 - NB_DL_TBF_4_5_succ ..................................................................................................................................... 53-34


53-34

P165 - NB_UL_TBF_4_5_succ ..................................................................................................................................... 53-35


53-35

P26 - TIME_UL_PDCH_CONG ................................................................................................................................... 53-35


53-35

P30d - NB_UL_TBF_EST_SUCC_EGPRS_PIM .................................................................................................. 53-36


53-36

P35 - MAX_NB_DL_TBF_SIMUL_EST .................................................................................................................. 53-36


53-36

P36 - AV_NB_DL_TBF_SIMUL_EST ....................................................................................................................... 53-37


53-37
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R lxv
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P38b - CUMULATED_TIME_PDCH_USED .......................................................................................................... 53-37
53-37

P38c - CUMULATED_TIME_PDCH_USED_EGPRS ........................................................................................ 53-38


53-38

P38e - CUMULATED_TIME_PDCH_USED_DL_CELL .................................................................................. 53-38


53-38

P38f - CUMULATED_TIME_PDCH_USED_UL_CELL ................................................................................... 53-39


53-39

P38g - CUMULATED_TIME_PDCH_USED_GPRS ........................................................................................... 53-39


53-39

P39 - MAX_NB_UL_TBF_SIMUL_EST .................................................................................................................. 53-40


53-40

P40 - AV_NB_UL_TBF_SIMUL_EST ....................................................................................................................... 53-40


53-40

P409 - CUMULATED_TIME_DL_BIASED_AND_OPTIMAL_DL_ALLOCATION ........................... 53-41


53-41

P410 - CUMULATED_TIME_UL_BIASED_AND_OPTIMAL_UL_ALLOCATION ........................... 53-42


53-42

P411 - CUMULATED_TIME_DL_BIASED_DL_TBF ....................................................................................... 53-43


53-43

P412 - CUMULATED_TIME_UL_BIASED_UL_TBF ....................................................................................... 53-44


53-44

P414bis - CUMULATED_TIME_ALLOCATED_SPDCH ................................................................................. 53-44


53-44

P415bis - MAX_OF_ALLOCATED_SPDCH .......................................................................................................... 53-45


53-45

P415ter - MAX_NB_ALLOCATED_SPDCH_GPU ............................................................................................. 53-45


53-45

P416bis - MIN_OF_ALLOCATED_SPDCH ............................................................................................................ 53-46


53-46

P417 - NB_PREEMPTED_PDCH ................................................................................................................................ 53-46


53-46

P419 - CUMULATED_TIME_DL_BIASED ........................................................................................................... 53-47


53-47

P420 - CUMULATED_TIME_UL_BIASED ........................................................................................................... 53-48


53-48

P451a - CUMULATED_TIME_PDCH_UL_TBF_CELL ................................................................................... 53-49


53-49

P451b - CUMULATED_TIME_PDCH_DL_TBF_CELL ................................................................................... 53-49


53-49

P452 - CUMULATED_TIME_PDCH_DL_TBF_GMM_SIG_CELL ............................................................ 53-50


53-50

P453a_1 - DISTRIB_UL_TBF_DURATION_1 ...................................................................................................... 53-50


53-50

P453a_10 - DISTRIB_UL_TBF_DURATION_10 ................................................................................................. 53-51


53-51

P453a_2 - DISTRIB_UL_TBF_DURATION_2 ...................................................................................................... 53-51


53-51

P453a_3 - DISTRIB_UL_TBF_DURATION_3 ...................................................................................................... 53-52


53-52

P453a_4 - DISTRIB_UL_TBF_DURATION_4 ...................................................................................................... 53-53


53-53

P453a_5 - DISTRIB_UL_TBF_DURATION_5 ...................................................................................................... 53-53


53-53
....................................................................................................................................................................................................................................
lxvi Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P453a_6 - DISTRIB_UL_TBF_DURATION_6 ...................................................................................................... 53-54
53-54

P453a_7 - DISTRIB_UL_TBF_DURATION_7 ...................................................................................................... 53-54


53-54

P453a_8 - DISTRIB_UL_TBF_DURATION_8 ...................................................................................................... 53-55


53-55

P453a_9 - DISTRIB_UL_TBF_DURATION_9 ...................................................................................................... 53-55


53-55

P453b_1 - DISTRIB_DL_TBF_DURATION_1 ...................................................................................................... 53-56


53-56

P453b_10 - DISTRIB_DL_TBF_DURATION_10 ................................................................................................. 53-57


53-57

P453b_2 - DISTRIB_DL_TBF_DURATION_2 ...................................................................................................... 53-57


53-57

P453b_3 - DISTRIB_DL_TBF_DURATION_3 ...................................................................................................... 53-58


53-58

P453b_4 - DISTRIB_DL_TBF_DURATION_4 ...................................................................................................... 53-58


53-58

P453b_5 - DISTRIB_DL_TBF_DURATION_5 ...................................................................................................... 53-59


53-59

P453b_6 - DISTRIB_DL_TBF_DURATION_6 ...................................................................................................... 53-60


53-60

P453b_7 - DISTRIB_DL_TBF_DURATION_7 ...................................................................................................... 53-60


53-60

P453b_8 - DISTRIB_DL_TBF_DURATION_8 ...................................................................................................... 53-61


53-61

P453b_9 - DISTRIB_DL_TBF_DURATION_9 ...................................................................................................... 53-61


53-61

P454a_1 - DISTRIB_UL_TBF_VOLUME_1 .......................................................................................................... 53-62


53-62

P454a_10 - DISTRIB_UL_TBF_VOLUME_10 ..................................................................................................... 53-63


53-63

P454a_2 - DISTRIB_UL_TBF_VOLUME_2 .......................................................................................................... 53-63


53-63

P454a_3 - DISTRIB_UL_TBF_VOLUME_3 .......................................................................................................... 53-64


53-64

P454a_4 - DISTRIB_UL_TBF_VOLUME_4 .......................................................................................................... 53-64


53-64

P454a_5 - DISTRIB_UL_TBF_VOLUME_5 .......................................................................................................... 53-65


53-65

P454a_6 - DISTRIB_UL_TBF_VOLUME_6 .......................................................................................................... 53-66


53-66

P454a_7 - DISTRIB_UL_TBF_VOLUME_7 .......................................................................................................... 53-66


53-66

P454a_8 - DISTRIB_UL_TBF_VOLUME_8 .......................................................................................................... 53-67


53-67

P454a_9 - DISTRIB_UL_TBF_VOLUME_9 .......................................................................................................... 53-67


53-67

P454b_1 - DISTRIB_DL_TBF_VOLUME_1 .......................................................................................................... 53-68


53-68

P454b_10 - DISTRIB_DL_TBF_VOLUME_10 ..................................................................................................... 53-69


53-69

P454b_2 - DISTRIB_DL_TBF_VOLUME_2 .......................................................................................................... 53-69


53-69
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R lxvii
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P454b_3 - DISTRIB_DL_TBF_VOLUME_3 .......................................................................................................... 53-70
53-70

P454b_4 - DISTRIB_DL_TBF_VOLUME_4 .......................................................................................................... 53-70


53-70

P454b_5 - DISTRIB_DL_TBF_VOLUME_5 .......................................................................................................... 53-71


53-71

P454b_6 - DISTRIB_DL_TBF_VOLUME_6 .......................................................................................................... 53-72


53-72

P454b_7 - DISTRIB_DL_TBF_VOLUME_7 .......................................................................................................... 53-72


53-72

P454b_8 - DISTRIB_DL_TBF_VOLUME_8 .......................................................................................................... 53-73


53-73

P454b_9 - DISTRIB_DL_TBF_VOLUME_9 .......................................................................................................... 53-73


53-73

P455a_1 - DISTRIB_UL_PDCH_UNIT_ALLOC_1 ............................................................................................ 53-74


53-74

P455a_10 - DISTRIB_UL_PDCH_UNIT_ALLOC_10 ....................................................................................... 53-75


53-75

P455a_2 - DISTRIB_UL_PDCH_UNIT_ALLOC_2 ............................................................................................ 53-76


53-76

P455a_3 - DISTRIB_UL_PDCH_UNIT_ALLOC_3 ............................................................................................ 53-77


53-77

P455a_4 - DISTRIB_UL_PDCH_UNIT_ALLOC_4 ............................................................................................ 53-78


53-78

P455a_5 - DISTRIB_UL_PDCH_UNIT_ALLOC_5 ............................................................................................ 53-79


53-79

P455a_6 - DISTRIB_UL_PDCH_UNIT_ALLOC_6 ............................................................................................ 53-80


53-80

P455a_7 - DISTRIB_UL_PDCH_UNIT_ALLOC_7 ............................................................................................ 53-81


53-81

P455a_8 - DISTRIB_UL_PDCH_UNIT_ALLOC_8 ............................................................................................ 53-82


53-82

P455a_9 - DISTRIB_UL_PDCH_UNIT_ALLOC_9 ............................................................................................ 53-83


53-83

P455b_1 - DISTRIB_DL_PDCH_UNIT_ALLOC_1 ............................................................................................ 53-84


53-84

P455b_10 - DISTRIB_DL_PDCH_UNIT_ALLOC_10 ....................................................................................... 53-85


53-85

P455b_2 - DISTRIB_DL_PDCH_UNIT_ALLOC_2 ............................................................................................ 53-86


53-86

P455b_3 - DISTRIB_DL_PDCH_UNIT_ALLOC_3 ............................................................................................ 53-87


53-87

P455b_4 - DISTRIB_DL_PDCH_UNIT_ALLOC_4 ............................................................................................ 53-88


53-88

P455b_5 - DISTRIB_DL_PDCH_UNIT_ALLOC_5 ............................................................................................ 53-89


53-89

P455b_6 - DISTRIB_DL_PDCH_UNIT_ALLOC_6 ............................................................................................ 53-90


53-90

P455b_7 - DISTRIB_DL_PDCH_UNIT_ALLOC_7 ............................................................................................ 53-91


53-91

P455b_8 - DISTRIB_DL_PDCH_UNIT_ALLOC_8 ............................................................................................ 53-92


53-92

P455b_9 - DISTRIB_DL_PDCH_UNIT_ALLOC_9 ............................................................................................ 53-93


53-93
....................................................................................................................................................................................................................................
lxviii Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P461 - CUMULATED_ACT_EXT_UL_CONNECTION_TIME .................................................................... 53-94
53-94

P495 - MAX_NB_USED_SPDCH_CELL ................................................................................................................ 53-95


53-95

P495bis - EST_MAX_USED_SPDCH_GPU_CAPACITY ................................................................................ 53-95


53-95

P495ter - MAX_NB_USED_SPDCH_GPU .............................................................................................................. 53-96


53-96

P496 - MIN_NB_USED_SPDCH_CELL .................................................................................................................. 53-96


53-96

P52a - CUMULATED_ACTIVE_DL_CONNECTION_TIME_GPRS_ACK ............................................. 53-97


53-97

P52b - CUMULATED_ACTIVE_DL_CONNECTION_TIME_GPRS_NACK ......................................... 53-98


53-98

P52c - CUMULATED_ACTIVE_DL_CONNECTION_TIME_EGPRS_ACK .......................................... 53-99


53-99

P52d - CUMULATED_ACTIVE_DL_CONNECTION_TIME_EGPRS_NACK ................................... 53-100


53-100

P531a_1 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_1 ....................................................... 53-101


53-101

P531a_10 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_10 .................................................. 53-101


53-101

P531a_11 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_11 ................................................... 53-102


53-102

P531a_2 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_2 ....................................................... 53-103


53-103

P531a_3 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_3 ....................................................... 53-103


53-103

P531a_4 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_4 ....................................................... 53-104


53-104

P531a_5 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_5 ....................................................... 53-105


53-105

P531a_6 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_6 ....................................................... 53-105


53-105

P531a_7 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_7 ....................................................... 53-106


53-106

P531a_8 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_8 ....................................................... 53-107


53-107

P531a_9 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_9 ....................................................... 53-107


53-107

P531b_1 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_1 ....................................................... 53-108


53-108

P531b_10 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_10 .................................................. 53-109


53-109

P531b_11 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_11 .................................................. 53-109


53-109

P531b_2 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_2 ....................................................... 53-110


53-110

P531b_3 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_3 ....................................................... 53-111


53-111

P531b_4 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_4 ....................................................... 53-111


53-111

P531b_5 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_5 ....................................................... 53-112


53-112
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R lxix
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P531b_6 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_6 ....................................................... 53-113
53-113

P531b_7 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_7 ....................................................... 53-113


53-113

P531b_8 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_8 ....................................................... 53-114


53-114

P531b_9 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_9 ....................................................... 53-115


53-115

P532a_1 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_1 .......................................................... 53-115


53-115

P532a_10 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_10 ..................................................... 53-116


53-116

P532a_2 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_2 .......................................................... 53-117


53-117

P532a_3 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_3 .......................................................... 53-117


53-117

P532a_4 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_4 .......................................................... 53-118


53-118

P532a_5 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_5 .......................................................... 53-119


53-119

P532a_6 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_6 .......................................................... 53-119


53-119

P532a_7 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_7 .......................................................... 53-120


53-120

P532a_8 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_8 .......................................................... 53-121


53-121

P532a_9 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_9 .......................................................... 53-121


53-121

P532b_1 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_1 .......................................................... 53-122


53-122

P532b_10 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_10 ..................................................... 53-123


53-123

P532b_2 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_2 .......................................................... 53-123


53-123

P532b_3 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_3 .......................................................... 53-124


53-124

P532b_4 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_4 .......................................................... 53-125


53-125

P532b_5 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_5 .......................................................... 53-125


53-125

P532b_6 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_6 .......................................................... 53-126


53-126

P532b_7 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_7 .......................................................... 53-127


53-127

P532b_8 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_8 .......................................................... 53-127


53-127

P532b_9 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_9 .......................................................... 53-128


53-128

P62d - NB_UL_TBF_EST_REQ_EGPRS_PIM ................................................................................................... 53-129


53-129

P90g - NB_DL_TBF_EST_SUCC_EGPRS_PIM ................................................................................................ 53-129


53-129

P91g - NB_DL_TBF_EST_REQ_EGPRS_PIM ................................................................................................... 53-130


53-130
....................................................................................................................................................................................................................................
lxx Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
54 Traffic load

Ater interface

P103 - NB_ERROR_UL_GCH_FRAME ..................................................................................................................... 54-1


54-1

P41 - NB_KBYTES_SENT_TO_BSC ........................................................................................................................... 54-2


54-2

P42 - NB_KBYTES_RECEIVED_FROM_BSC ....................................................................................................... 54-2


54-2

Gb interface

P180a - NB_SGSN_SELECTION_NSF ....................................................................................................................... 54-3


54-3

P180b - NB_SGSN_SELECTION_NSF_RIM ........................................................................................................... 54-3


54-3

P23 - NB_UL_LLC_BYTES_DISC_CONG ............................................................................................................... 54-4


54-4

P43 - NB_DL_LLC_BYTES ............................................................................................................................................. 54-4


54-4

P44 - NB_UL_LLC_BYTES ............................................................................................................................................. 54-5


54-5

P45 - NB_KBYTES_RECEIVED_FROM_SGSN .................................................................................................... 54-5


54-5

P45a - NB_KBYTES_RECEIVED_FROM_SGSN_GBIP .................................................................................... 54-6


54-6

P46 - NB_KBYTES_SENT_TO_SGSN ....................................................................................................................... 54-6


54-6

P46a - NB_KBYTES_SENT_TO_SGSN_GBIP ....................................................................................................... 54-7


54-7

P600 - NB_REDIRECT_ATTEMPT .............................................................................................................................. 54-7


54-7

P601 - NB_REDIRECT_COMMAND .......................................................................................................................... 54-8


54-8

P602 - NB_REDIRECT_COMMAND_CS_PS_COORD ...................................................................................... 54-8


54-8

P603 - NB_REDIRECT_COMPLETE .......................................................................................................................... 54-9


54-9

P604 - NB_REDIRECT_COMPLETE_MS_NOT_ACCEPTED ........................................................................ 54-9


54-9

P605 - NB_REDIRECT_COMPLETE_MS_ALREADY_REG ........................................................................ 54-10


54-10

P68 - NB_DL_LLC_COUNT_IM ................................................................................................................................. 54-10


54-10

P69 - NB_DL_LLC_BYTES_IM .................................................................................................................................. 54-11


54-11

IP interface

P541a - NB_MFS_SENT_IPGCHU_GBR_IP_PACKETS ................................................................................. 54-12


54-12

P541b - NB_MFS_RESENT_IPGCHU_GBR_IP_PACKETS .......................................................................... 54-12


54-12

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R lxxi
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P541d - NB_MFS_SENT_IPGCHU_GBR_IP_BYTES ....................................................................................... 54-13
54-13

P542a - NB_MFS_SENT_IPGCHU_BE_IP_PACKETS ..................................................................................... 54-13


54-13

P542b - NB_MFS_RESENT_IPGCHU_BE_IP_PACKETS .............................................................................. 54-14


54-14

P542d - NB_MFS_SENT_IPGCHU_BE_IP_BYTES .......................................................................................... 54-14


54-14

P543a - NB_MFS_SENT_IPGCHC_IP_PACKETS .............................................................................................. 54-15


54-15

P543d - NB_MFS_SENT_IPGCHC_IP_BYTES .................................................................................................... 54-15


54-15

P549a - TIME_PS_DL_BE_CONGESTION ............................................................................................................ 54-16


54-16

Radio interface

P10 - NB_DL_LLC_BYTES_DISC_CONG ............................................................................................................ 54-17


54-17

P104 - NB_LLC_PDU_GPU .......................................................................................................................................... 54-17


54-17

P201 - TIME_PTU_CPU_TDM_LOAD .................................................................................................................... 54-18


54-18

P201bis - TIME_SCP_CPU_LOAD ............................................................................................................................ 54-18


54-18

P202 - TIME_PTU_CPU_TDM_OVERLOAD ....................................................................................................... 54-19


54-19

P202bis - TIME_SCP_CPU_OVERLOAD ............................................................................................................... 54-19


54-19

P20a - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS1 ................................................................................ 54-20


54-20

P20b - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS2 ................................................................................ 54-20


54-20

P20c - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS3 ................................................................................ 54-21


54-21

P20d - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS4 ................................................................................ 54-22


54-22

P20f - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS1 ............................................................................ 54-22


54-22

P20g - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS2 ........................................................................... 54-23


54-23

P20h - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS3 ........................................................................... 54-24


54-24

P20i - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS4 ............................................................................ 54-24


54-24

P20j - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS5 ............................................................................ 54-25


54-25

P20k - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS6 ........................................................................... 54-26


54-26

P20l - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS7 ............................................................................ 54-27


54-27

P20m - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS8 .......................................................................... 54-27


54-27

P20n - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS9 ........................................................................... 54-28


54-28
....................................................................................................................................................................................................................................
lxxii Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P21a - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS1 ................................................................................ 54-29
54-29

P21b - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS2 ................................................................................ 54-29


54-29

P21c - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS3 ................................................................................ 54-30


54-30

P21d - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS4 ................................................................................ 54-30


54-30

P21f - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS1 ............................................................................ 54-31


54-31

P21g - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS2 ........................................................................... 54-31


54-31

P21h - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS3 ........................................................................... 54-32


54-32

P21i - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS4 ............................................................................ 54-32


54-32

P21j - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS5 ............................................................................ 54-33


54-33

P21k - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS6 ........................................................................... 54-33


54-33

P21l - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS7 ............................................................................ 54-34


54-34

P21m - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS8 .......................................................................... 54-34


54-34

P21n - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS9 ........................................................................... 54-35


54-35

P310a - NB_STALL_IND_MS_GPRS ........................................................................................................................ 54-35


54-35

P310b - NB_STALL_IND_MS_EGPRS .................................................................................................................... 54-36


54-36

P310c - NB_STALL_STATE_GPRS_DL_TBF ....................................................................................................... 54-36


54-36

P310d - NB_STALL_STATE_EGPRS_DL_TBF .................................................................................................... 54-37


54-37

P335 - AV_DL_TX_EFF_GPRS .................................................................................................................................... 54-37


54-37

P336 - AV_UL_TX_EFF_GPRS .................................................................................................................................... 54-38


54-38

P350a - NB_DL_RADIO_BLOCK_PDTCH ............................................................................................................ 54-38


54-38

P350b - NB_UL_RADIO_BLOCK_PDTCH ........................................................................................................... 54-39


54-39

P351a - NB_DL_CS_ADAPT_INCREASE .............................................................................................................. 54-39


54-39

P351b - NB_DL_CS_ADAPT_DECREASE ............................................................................................................ 54-40


54-40

P352a - NB_UL_CS_ADAPT_INCREASE .............................................................................................................. 54-40


54-40

P352b - NB_UL_CS_ADAPT_DECREASE ............................................................................................................ 54-41


54-41

P384 - Time_DSP_Cong ................................................................................................................................................... 54-41


54-41

P384bis - TIME_SCP_CONG ........................................................................................................................................ 54-42


54-42
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R lxxiii
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P384ter - TIME_GPU_BUFFER_CONG ................................................................................................................... 54-43
54-43

P390a - NB_BSS_CS_PAGING_REQ_GPU ........................................................................................................... 54-43


54-43

P390b - NB_CS_PAGING_REQ_PACCH ................................................................................................................ 54-44


54-44

P391a - NB_PS_PAGING_REQ_GPU ....................................................................................................................... 54-44


54-44

P391b - NB_CS_PAGING_REQ_GPU ....................................................................................................................... 54-45


54-45

P391c - NB_CS_PAGING_WITH_GLOBAL_CN_ID_GPU ............................................................................ 54-45


54-45

P392a - AV_NB_MS_CONTEXTS .............................................................................................................................. 54-46


54-46

P392b - MAX_NB_MS_CONTEXTS ......................................................................................................................... 54-46


54-46

P399 - SIG_BLKS_PRACH_LOAD ............................................................................................................................ 54-47


54-47

P400 - SIG_BLKS_PAGCH_LOAD ............................................................................................................................ 54-47


54-47

P401 - SIG_BLKS_PACCH_UL_LOAD ................................................................................................................... 54-48


54-48

P402 - TIME_PMU_OVERLOAD ............................................................................................................................... 54-49


54-49

P413 - NB_GPRS_SESSIONS ....................................................................................................................................... 54-49


54-49

P421 - NB_DUMMY_RLC_DATA_BLOCKS ........................................................................................................ 54-50


54-50

P438a - SIG_BLKS_NC2_UL_PACCH_PTM_LOAD ........................................................................................ 54-51


54-51

P438b - SIG_BLKS_NC2_DL_PACCH_PTM_LOAD ........................................................................................ 54-51


54-51

P438c - SIG_BLKS_NC2_UL_PACCH_CCCH_LOAD ..................................................................................... 54-52


54-52

P438d - SIG_BLKS_NC2_PRACH_LOAD ............................................................................................................. 54-52


54-52

P439 - SIG_BLKS_UL_PACCH_CCCH_PRR_LOAD ....................................................................................... 54-53


54-53

P43a - NB_DL_LLC_BYTES_GPRS_ACK ............................................................................................................ 54-53


54-53

P43b - NB_DL_LLC_BYTES_GPRS_NACK ......................................................................................................... 54-54


54-54

P43c - NB_DL_LLC_BYTES_EGPRS_ACK ......................................................................................................... 54-54


54-54

P43d - NB_DL_LLC_BYTES_EGPRS_NACK ...................................................................................................... 54-55


54-55

P44a - NB_UL_LLC_BYTES_GPRS_ACK ............................................................................................................ 54-55


54-55

P44b - NB_UL_LLC_BYTES_GPRS_NACK ......................................................................................................... 54-56


54-56

P44c - NB_UL_LLC_BYTES_EGPRS_ACK ......................................................................................................... 54-56


54-56

P44d - NB_UL_LLC_BYTES_EGPRS_NACK ...................................................................................................... 54-57


54-57
....................................................................................................................................................................................................................................
lxxiv Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P450a - NB_R97_R98_MS_CONTEXT_GPU ........................................................................................................ 54-57
54-57

P450b - NB_GPRS_R99_MS_CONTEXT_GPU ................................................................................................... 54-58


54-58

P450c - NB_EGPRS_R99_MS_CONTEXT_GPU ................................................................................................. 54-58


54-58

P450d - NB_MS_CONTEXT_GPU ............................................................................................................................. 54-59


54-59

P450e - NB_GERAN_FEATURE_PACK1_MS_CONTEXT_GPU ................................................................ 54-59


54-59

P450f - NB_E_UTRA_FDD_CAPABLE_MS_CONTEXT_GPU ................................................................... 54-60


54-60

P450g - NB_UTRA_FDD_CAPABLE_MS_CONTEXT_GPU ........................................................................ 54-60


54-60

P450h - NB_UTRA_TDD_CAPABLE_MS_CONTEXT_GPU ........................................................................ 54-61


54-61

P450i - NB_E_UTRA_TDD_CAPABLE_MS_CONTEXT_GPU ................................................................... 54-61


54-61

P457 - NB_PSI_MES ......................................................................................................................................................... 54-62


54-62

P459 - NB_NEIGH_PSI_MES ....................................................................................................................................... 54-62


54-62

P462 - NB_DUMMY_UL_BLOCKS .......................................................................................................................... 54-63


54-63

P49 - NB_IMM_ASS_AGCH ......................................................................................................................................... 54-63


54-63

P51 - NB_USEFUL_PDDCB_SCHEDULED ......................................................................................................... 54-64


54-64

P52 - NB_USELESS_PDDCB_SCHEDULED ....................................................................................................... 54-64


54-64

P530a_1 - NB_MS_MULTISLOT_CLASS_0_TO_10 ......................................................................................... 54-65


54-65

P530a_2 - NB_MS_MULTISLOT_CLASS_11_TO_12 ....................................................................................... 54-65


54-65

P530a_3 - NB_MS_MULTISLOT_CLASS_3X ...................................................................................................... 54-66


54-66

P530a_4 - NB_MS_MULTISLOT_CLASS_4X ...................................................................................................... 54-67


54-67

P530a_5 - NB_MS_MULTISLOT_CLASS_30_TO_34 ...................................................................................... 54-68


54-68

P530b_5 - NB_MS_MULTISLOT_CLASS_31_TO_33 ...................................................................................... 54-68


54-68

P53a - NB_PS_PAGING_REQ_PCH .......................................................................................................................... 54-69


54-69

P53b - NB_CS_PAGING_REQ_PCH ......................................................................................................................... 54-70


54-70

P53c - NB_IMM_ASS_PCH ........................................................................................................................................... 54-70


54-70

P53d - NB_CS_PAGING_WITH_GLOBAL_CN_ID_PCH ............................................................................... 54-71


54-71

P55a - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS1 .................................................................................... 54-71


54-71

P55b - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS2 .................................................................................... 54-72


54-72
....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R lxxv
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P55c - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS3 .................................................................................... 54-72
54-72

P55d - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS4 .................................................................................... 54-73


54-73

P55e - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS1 ............................................................................... 54-73


54-73

P55f - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS2 ................................................................................ 54-74


54-74

P55g - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS3 ............................................................................... 54-74


54-74

P55h - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS4 ............................................................................... 54-75


54-75

P55i - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS5 ................................................................................ 54-75


54-75

P55j - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS6 ................................................................................ 54-76


54-76

P55k - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS7 ............................................................................... 54-76


54-76

P55l - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS8 ................................................................................ 54-77


54-77

P55m - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS9 .............................................................................. 54-78


54-78

P57a - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS1 .................................................................................... 54-78


54-78

P57b - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS2 .................................................................................... 54-79


54-79

P57c - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS3 .................................................................................... 54-79


54-79

P57d - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS4 .................................................................................... 54-80


54-80

P57e - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS1 ............................................................................... 54-80


54-80

P57f - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS2 ................................................................................ 54-81


54-81

P57g - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS3 ............................................................................... 54-81


54-81

P57h - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS4 ............................................................................... 54-82


54-82

P57i - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS5 ................................................................................ 54-82


54-82

P57j - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS6 ................................................................................ 54-83


54-83

P57k - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS7 ............................................................................... 54-83


54-83

P57l - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS8 ................................................................................ 54-84


54-84

P57m - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS9 .............................................................................. 54-84


54-84

P59 - NB_DL_RLC_BLOCK_PACCH ....................................................................................................................... 54-85


54-85

P60 - NB_UL_RLC_BLOCK_PACCH ....................................................................................................................... 54-85


54-85

P61 - SIG_BLKS_PPCH_LOAD .................................................................................................................................. 54-86


54-86
....................................................................................................................................................................................................................................
lxxvi Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P61a - NB_PACK_PS_PAGING_REQ_PPCH ........................................................................................................ 54-87
54-87

P61b - NB_PACK_CS_PAGING_REQ_PPCH ....................................................................................................... 54-87


54-87

P72c - NB_DL_RLC_BYTES_PDTCH_LOST_CS .............................................................................................. 54-88


54-88

P72d - NB_DL_RLC_BYTES_PDTCH_LOST_MCS ......................................................................................... 54-88


54-88

P73c - NB_UL_RLC_BYTES_PDTCH_LOST_CS .............................................................................................. 54-89


54-89

P73d - NB_UL_RLC_BYTES_PDTCH_LOST_MCS ......................................................................................... 54-89


54-89

P74 - NB_DL_PDU_TRANSMITTED ....................................................................................................................... 54-90


54-90

P75 - NB_UL_PDU_TRANSMITTED ....................................................................................................................... 54-90


54-90

P76a - AV_PMU_CPU_POWER_BUDGET ............................................................................................................ 54-91


54-91

P76b - AV_CORE_PMU_CPU_POWER_BUDGET ............................................................................................ 54-91


54-91

P77a - MAX_PMU_CPU_POWER_BUDGET ....................................................................................................... 54-92


54-92

P86_0 - NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_0 ....................................................................... 54-92


54-92

P86_1 - NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_2 ....................................................................... 54-93


54-93

P86_2 - NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_4 ....................................................................... 54-93


54-93

P86_3 - NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_6 ....................................................................... 54-94


54-94

P86_4 - NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_8 ....................................................................... 54-94


54-94

P86_5 - NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_10 ..................................................................... 54-95


54-95

P95 - NB_DL_LLC_BYTES_REROUTED .............................................................................................................. 54-95


54-95

P96 - NB_DL_LLC_BYTES_NOT_REROUTED ................................................................................................. 54-96


54-96

P97 - NB_DL_LLC_BYTES_REROUTED_RECEIVED ................................................................................... 54-96


54-96

P99 - NB_LLC_BYTES_DISC_SUSPEND ............................................................................................................. 54-97


54-97

Part XXVIII: MFS-LCS Counters

55 Quality of service

Radio interface

P800 - NB_LOC_REQ ......................................................................................................................................................... 55-1


55-1

P801 - NB_ASSIST_DATA_REQ ................................................................................................................................... 55-2


55-2

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R lxxvii
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P802 - NB_ASSIST_DATA_SUCC ................................................................................................................................ 55-2
55-2

P803 - NB_LOC_TA_SUCC ............................................................................................................................................. 55-3


55-3

P804 - NB_LOC_CONV_GPS_SUCC .......................................................................................................................... 55-3


55-3

P805 - NB_LOC_MA_AGPS_SUCC ............................................................................................................................ 55-4


55-4

P806 - NB_LOC_MB_AGPS_SUCC ............................................................................................................................ 55-4


55-4

P807 - NB_LOC_TA_PCF_REQ ..................................................................................................................................... 55-5


55-5

P808 - NB_LOC_TA_PCF_SUCC .................................................................................................................................. 55-5


55-5

P809 - NB_LOC_CONV_GPS_PCF_REQ ................................................................................................................. 55-6


55-6

P810 - NB_LOC_MA_AGPS_PCF_REQ .................................................................................................................... 55-6


55-6

P811 - NB_LOC_MA_AGPS_PCF_SUCC ................................................................................................................. 55-7


55-7

P812 - NB_LOC_MB_AGPS_PCF_REQ .................................................................................................................... 55-7


55-7

P813 - NB_LOC_MB_AGPS_PCF_SUCC ................................................................................................................. 55-8


55-8

P814 - NB_LCS_PROTOCOL_ERROR ...................................................................................................................... 55-8


55-8

P815 - NB_LCS_INTERRUPTED_INTRA_BSC_HO ........................................................................................... 55-9


55-9

P816 - NB_LCS_INTERRUPTED_INTER_BSC_HO ........................................................................................... 55-9


55-9

P817 - NB_LCS_FAILURE_RRLP .............................................................................................................................. 55-10


55-10

P818 - NB_LCS_FAILURE_TIMER_EXPIRY ...................................................................................................... 55-10


55-10

P819 - NB_LCS_FAILURE_INTERNAL ................................................................................................................. 55-11


55-11

P820 - NB_UNKNOWN_LCS_REQ ........................................................................................................................... 55-11


55-11

P821 - NB_LOC_CONV_GPS_PCF_SUCC ............................................................................................................ 55-12


55-12

56 Traffic load

Radio interface

P822 - AV_TA_LAT .............................................................................................................................................................. 56-1


56-1

P823 - AV_TA_LONG ......................................................................................................................................................... 56-2


56-2

P824 - AV_CONV_GPS_LAT ........................................................................................................................................... 56-2


56-2

P825 - AV_CONV_GPS_LONG ...................................................................................................................................... 56-3


56-3

....................................................................................................................................................................................................................................
lxxviii Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................
P826 - AV_MA_AGPS_LAT ............................................................................................................................................. 56-3
56-3

P827 - AV_MA_AGPS_LONG ........................................................................................................................................ 56-4


56-4

P828 - AV_MB_AGPS_LAT ............................................................................................................................................. 56-4


56-4

P829 - AV_MB_AGPS_LONG ......................................................................................................................................... 56-5


56-5

P830 - ST_DEV_TA_LAT .................................................................................................................................................. 56-5


56-5

P831 - ST_DEV_TA_LONG ............................................................................................................................................. 56-6


56-6

P832 - ST_DEV_CONV_GPS_LAT .............................................................................................................................. 56-7


56-7

P833 - ST_DEV_CONV_GPS_LONG .......................................................................................................................... 56-7


56-7

P834 - ST_DEV_MA_AGPS_LAT ................................................................................................................................. 56-8


56-8

P835 - ST_DEV_MA_AGPS_LONG ............................................................................................................................ 56-9


56-9

P836 - ST_DEV_MB_AGPS_LAT ............................................................................................................................... 56-10


56-10

P837 - ST_DEV_MB_AGPS_LONG .......................................................................................................................... 56-10


56-10

A Reference

Reissue history .......................................................................................................................................................................... A-1


A-1

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R lxxix
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Contents

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
lxxx Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
List of tables

1 Issue 13, September 2014, What’s new ....................................................................................................... lxxxiii

A-1 Issue 12, July 2014, What’s new ......................................................................................................................... A-1

A-2 Issue 11, June 2014, What’s new ........................................................................................................................ A-1

A-3 Issue 10, February 2014, What’s new ............................................................................................................... A-2

A-4 Issue 9, January 2014, Reason for reissue ....................................................................................................... A-2

A-5 Issue 8, April 2013, Reason for reissue ............................................................................................................ A-3

A-6 Issue 7, March 2013, Reason for reissue ......................................................................................................... A-3

A-7 Issue 6, February 2013, Reason for reissue .................................................................................................... A-3

A-8 Issue 5, September 2012, Reason for reissue ................................................................................................. A-4

A-9 Issue 4, September 2012, Reason for reissue ................................................................................................. A-4

A-10 Issue 3, June 2012, Reason for reissue ............................................................................................................. A-4

A-11 Issue 2, March 2012, Reason for reissue ......................................................................................................... A-5

A-12 Issue 1, March 2012, Reason for reissue ......................................................................................................... A-5

A-13 Issue 01p03, December 2011, Reason for reissue ........................................................................................ A-5

A-14 Issue 01p02, 2011, Reason for reissue .............................................................................................................. A-5

A-15 Issue 01p01, 2010, Reason for reissue .............................................................................................................. A-6

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R lxxxi
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
List of tables

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
lxxxii Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
About this document
About this document

Purpose
The PM Counters include description of:
• GSM Counters
• GPRS Counters
• LCS Counters.

What's new
The major changes introduced in this issue of the document are described in the following
paragraphs. Changes introduced in prior issues of the document are shown in Appendix
A, “Reference”.

Table 1 Issue 13, September 2014, What’s new

Feature/enhancement Description Location


Documentation changes
Update BSC Counters Standard issue Part I: “BSC-TYPE 1 - Traffic
This document was generated measurements”
from the BSC Counters
database edition 02.08.

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

Supported systems
This document applies to Release B12 of the BSS.

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R lxxxiii
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
About this document

....................................................................................................................................................................................................................................
How to use this document
No specific recommendation applies regarding the way readers should read this
document.

How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatel-
lucent.com/comments/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).

....................................................................................................................................................................................................................................
lxxxiv Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part I: BSC-TYPE 1 - Traffic
measurements

Overview
Purpose
All type 1.

Contents

Chapter 1, Handover 1-1


Chapter 2, Quality of Service 2-1
Chapter 3, Resource Availability & Usage 3-1
Chapter 4, Traffic Load 4-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R I-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 1 - Traffic measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
I-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
1 Handover
1

TCH

Overview
Purpose
This section contains TCH parameters.

Contents

C710 - NB_TCH_OUT_HO_REQ_TRX 1-1

C710 - NB_TCH_OUT_HO_REQ_TRX
Descripton

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

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 1-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C710 - NB_TCH_OUT_HO_REQ_TRX
TCH
....................................................................................................................................................................................................................................

Trigger condition 1) Intracell HO: Whenever the BSC process responsible for the handover procedure starts an intra cell TCH
handover procedure, excluding handover initiation for VAMOS HO cause 34 and 35.
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 --
Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
1-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
2 Quality of Service
2

Directed Retry

Overview
Purpose
This section contains Directed Retry parameters.

Contents

C717a - NB_INC_IDR_SUCC_TRX 2-1

C717a - NB_INC_IDR_SUCC_TRX
Descripton

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 Traffic measurements

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

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C717a - NB_INC_IDR_SUCC_TRX
Directed Retry
....................................................................................................................................................................................................................................

Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
2-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Established Phase
....................................................................................................................................................................................................................................

Established Phase

Overview
Purpose
This section contains Established Phase parameters.

Contents

C137 - NB_SDCCH_DROP_EST_PHAS_BSS_PB 2-3


C138 - NB_SDCCH_DROP_EST_PHAS_RLF 2-4
C14c - NB_TCH_DROP_EST_PHAS_BSS_PB 2-4
C162a - NB_TCH_DROP_DTAP_EST_PHAS_RLF 2-5
C162b - NB_TCH_DROP_DTAP_EST_PHAS_BSS_PB 2-6
C162c - NB_TCH_DROP_DTAP_EST_PHAS_REM_TRANS_FAIL 2-8
C736 - NB_TCH_DROP_EST_PHAS_RLF_TRX 2-8
C739 - NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX 2-9

C137 - NB_SDCCH_DROP_EST_PHAS_BSS_PB
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C137 - NB_SDCCH_DROP_EST_PHAS_BSS_PB
Established Phase
....................................................................................................................................................................................................................................

Type Name Traffic measurements

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

Feature Name --

C138 - NB_SDCCH_DROP_EST_PHAS_RLF
Descripton

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 Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures

External Comment --
Feature Name --

C14c - NB_TCH_DROP_EST_PHAS_BSS_PB
Descripton

Long Name NB_TCH_DROP_EST_PHAS_BSS_PB

Definition Number of TCH (in HR or FR usage) drops 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.
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.

....................................................................................................................................................................................................................................
2-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C14c - NB_TCH_DROP_EST_PHAS_BSS_PB
Established Phase
....................................................................................................................................................................................................................................

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 Traffic measurements


Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --
Feature Name --

C162a - NB_TCH_DROP_DTAP_EST_PHAS_RLF
Descripton

Long Name NB_TCH_DROP_DTAP_EST_PHAS_RLF


Definition Number of TCH (in HR or FR usage) drops in TCH DTAP established phase (i.e. after the BSC having
received the 24.008 CONNECT ACKNOWLEDGE message from the MS or from the MSC) due to radio
link failure (radio link timeout or LAPDm timer expiry).

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C162a - NB_TCH_DROP_DTAP_EST_PHAS_RLF
Established Phase
....................................................................................................................................................................................................................................

Trigger condition The BSC has an internal flag named �B_CONNECT_ACK_RECEIVED�. This flag is set to �TRUE�
if the BSC has received:
a) the 24.008 CONNECT ACKNOWLEDGE message from the MS.
b) the 24.008 CONNECT ACKNOWLEDGE message from the MSC.
It should be noted that, after an external handover, the target BSC considers the flag �B_CONNECT_ACK_
RECEIVED� has value �FALSE�.
If the flag �B_CONNECT_ACK_RECEIVED� has the value �TRUE�, this counter is incremented by
one: 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "radio
link failure" is received on Abis interface for a TCH channel (after successful DTAP establishment).
2) Whenever a 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 Traffic measurements

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

Feature Name --

C162b - NB_TCH_DROP_DTAP_EST_PHAS_BSS_PB
Descripton

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 (i.e. after the BSC having
received the 24.008 CONNECT ACKNOWLEDGE message from the MS or from the MSC) 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.

....................................................................................................................................................................................................................................
2-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C162b - NB_TCH_DROP_DTAP_EST_PHAS_BSS_PB
Established Phase
....................................................................................................................................................................................................................................

Trigger condition The BSC has an internal flag named �B_CONNECT_ACK_RECEIVED�. This flag is set to �TRUE�
if the BSC has received:
a) the 24.008 CONNECT ACKNOWLEDGE message from the MS.
b) the 24.008 CONNECT ACKNOWLEDGE message from the MSC.
It should be noted that, after an external handover, the target BSC considers the flag �B_CONNECT_ACK_
RECEIVED� has value �FALSE�.
If the flag �B_CONNECT_ACK_RECEIVED� has the value �TRUE�, this counter is incremented by
one: 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 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).
Note :
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 Traffic measurements

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

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C162c - NB_TCH_DROP_DTAP_EST_PHAS_REM_TRANS_FAIL
Established Phase
....................................................................................................................................................................................................................................

C162c - NB_TCH_DROP_DTAP_EST_PHAS_REM_TRANS_FAIL
Descripton

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 (i.e. after the BSC having
received the 24.008 CONNECT ACKNOWLEDGE message from the MS or from the MSC) due to remote
transcoder failure. This counter is not concerned by the channel change procedure.
Trigger condition The BSC has an internal flag named �B_CONNECT_ACK_RECEIVED�. This flag is set to �TRUE�
if the BSC has received:
a) the 24.008 CONNECT ACKNOWLEDGE message from the MS.
b) the 24.008 CONNECT ACKNOWLEDGE message from the MSC.
It should be noted that, after an external handover, the target BSC considers the flag �B_CONNECT_ACK_
RECEIVED� has value �FALSE�.
If the flag �B_CONNECT_ACK_RECEIVED� has the value �TRUE�, this counter is incremented by
one 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 Traffic measurements


Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --
Feature Name --

C736 - NB_TCH_DROP_EST_PHAS_RLF_TRX
Descripton

Long Name NB_TCH_DROP_EST_PHAS_RLF_TRX

Definition Number of non-AMR TCH (in HR or FR usage) drops 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 For TCH using non-AMR codecs:


1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "radio link
failure" is received on Abis interface for a TCH channel (after successful seizure).
2) Whenever a 48.058 ERROR INDICATION message is received on Abis interface and leads to a loss of
call.
Sub Domain 1 Established Phase

....................................................................................................................................................................................................................................
2-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C736 - NB_TCH_DROP_EST_PHAS_RLF_TRX
Established Phase
....................................................................................................................................................................................................................................

Sub Domain 2 TCH

Sub Domain 3 Failure


Measured Object TRX

Type Name Traffic measurements


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

External Comment --
Feature Name B7.1 counters improvements

C739 - NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX
Descripton

Long Name NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX


Definition Number of TCH (in HR or FR usage) drops due to 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. Whether A User plane Interface over IP AUPoIP applies to
the call, in case of normal assignment or directed retry cases, the BSC considers a TCH connection as
"established" only once first DL RTP has been received from MGW.
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 Traffic measurements


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

Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Handover
....................................................................................................................................................................................................................................

Handover

Overview
Purpose
This section contains Handover parameters.

Contents

C03 - NB_OUT_SDCCH_HO_SUCC 2-10


C07 - NB_SDCCH_DROP_OUT_HO 2-11
C10 - NB_INC_SDCCH_HO_SUCC 2-11
C14a - NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB 2-12
C621 - NB_TCH_DROP_OUT_HO_EXEC_TRX 2-14
C711 - NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX 2-14
C712 - NB_TCH_OUT_HO_SUCC_TRX 2-15
C713 - NB_TCH_OUT_HO_FAIL_REV_TRX 2-16
C714 - NB_TCH_OUT_HO_FAIL_NO_REV_TRX 2-17
C717b - NB_INC_TCH_HO_SUCC_TRX 2-17

C03 - NB_OUT_SDCCH_HO_SUCC
Descripton

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 Traffic measurements

....................................................................................................................................................................................................................................
2-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C03 - NB_OUT_SDCCH_HO_SUCC
Handover
....................................................................................................................................................................................................................................

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

External Comment --
Feature Name --

C07 - NB_SDCCH_DROP_OUT_HO
Descripton

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 Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --

Feature Name --

C10 - NB_INC_SDCCH_HO_SUCC
Descripton

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 Traffic measurements


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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C10 - NB_INC_SDCCH_HO_SUCC
Handover
....................................................................................................................................................................................................................................

External Comment --

Feature Name --

C14a - NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB
Descripton

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 are detected consecutively. In that case, the
counter will only be incremented once, as soon as the handover procedure fails.
This counter takes into account handovers from TCH in traffic or in signaling mode.

....................................................................................................................................................................................................................................
2-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C14a - NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB
Handover
....................................................................................................................................................................................................................................

Trigger condition 1) When the BSC receives on Abis from the target cell negative ack to the TCH channel activation involved
in the handover.
2) When the timer supervising the Channel Activation (T9103) expires on the target cell during activation of
a TCH channel involved in the handover.
3) When an 48.058 ERROR REPORT with a cause value of "O&M intervention" is received on Abis from
either the serving or the target cell during the external or internal inter-cell handover and leads to a
transaction failure.
4) When an 48.058 ERROR REPORT with a cause value of "O&M intervention" is received on Abis on
either the old or the new channel during the internal intra-cell handover and leads to a transaction failure.
5) When an 48.058 ERROR REPORT on SAPI 0 with a cause value of "message sequence error" is received
on Abis from the serving cell between the sending of the 48.058 CHANNEL ACTIVATION and the
reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGMENT during the internal inter-cell
TCH handover and leads to a transaction failure.
6) When an 48.058 ERROR REPORT on SAPI 0 with a cause value of "message sequence error" is received
on Abis interface on the old channel between the sending of the 48.058 CHANNEL ACTIVATION and the
reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGE during the internal intra-cell TCH
handover and leads to a transaction failure.
7) When 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) When an TCH handover abortion is initiated by the BSS O&M FAULT MANAGEMENT or by the BSS
TELECOM 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 or communication problems between
different processor boards).
9) When a 48.058 CONNECTION FAILURE INDICATION with a cause value of "remote transcoder
failure" is received on Abis from the old channel between the sending of the 48.058 CHANNEL
ACTIVATION and the reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGE during an
internal intra-cell or inter-cellTCH handover and leads to a transaction failure.
10) When the timer supervising the A INTERFACE CHANNEL ID toward BTS (T_aintcid) expires during
activation of a TCH channel involved in the handover performed with Iur-g support.
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 Traffic measurements


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

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C621 - NB_TCH_DROP_OUT_HO_EXEC_TRX
Handover
....................................................................................................................................................................................................................................

C621 - NB_TCH_DROP_OUT_HO_EXEC_TRX
Descripton

Long Name NB_TCH_DROP_OUT_HO_EXEC_TRX

Definition Number of non-AMR 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 For TCH using non-AMR codecs:


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 Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --
Feature Name B7.1 counters improvements

C711 - NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX
Descripton

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

....................................................................................................................................................................................................................................
2-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C711 - NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX
Handover
....................................................................................................................................................................................................................................

Trigger condition 1) Intracell HO: Whenever an intra-cell TCH handover in non VAMOS mode cannot be performed, because
there is no free TCH channel to allocate the handover to (In VAMOS mode when no pairing target candidate
is found, this counter is not incremented)
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 Traffic measurements


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

External Comment --
Feature Name B7.1 counters improvements

C712 - NB_TCH_OUT_HO_SUCC_TRX
Descripton

Long Name NB_TCH_OUT_HO_SUCC_TRX


Definition Nb of outgoing TCH handover successes, 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.
MC712 = C712
Trigger condition 1) External HO in the following cases:
1a) 48.008CLEAR COMMAND (cause = "handover successful") is received on the serving BSC on the
TCH channel.
1b) 48.008 CLEAR COMMAND (cause = "normal event/call control") is 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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C712 - NB_TCH_OUT_HO_SUCC_TRX
Handover
....................................................................................................................................................................................................................................

Measured Object TRX

Type Name Traffic measurements


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

External Comment --
Feature Name B7.1 counters improvements

C713 - NB_TCH_OUT_HO_FAIL_REV_TRX
Descripton

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 handovers from TCH in traffic or in signaling mode. It does not take into account DTM
Assignments.
MC713 = C713
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 Traffic measurements

Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --
Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
2-16 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C714 - NB_TCH_OUT_HO_FAIL_NO_REV_TRX
Handover
....................................................................................................................................................................................................................................

C714 - NB_TCH_OUT_HO_FAIL_NO_REV_TRX
Descripton

Long Name NB_TCH_OUT_HO_FAIL_NO_REV_TRX

Definition Nb of outgoing TCH handover -execution failures due to MS access problem 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 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.
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 Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --
Feature Name B7.1 counters improvements

C717b - NB_INC_TCH_HO_SUCC_TRX
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-17
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C717b - NB_INC_TCH_HO_SUCC_TRX
Handover
....................................................................................................................................................................................................................................

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 Traffic measurements


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

External Comment --
Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
2-18 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Speech
....................................................................................................................................................................................................................................

Speech

Overview
Purpose
This section contains Speech parameters.

Contents

C170 - NB_CALL_TFO 2-19


C171 - NB_TFO_CODEC_REQ 2-20

C170 - NB_CALL_TFO
Descripton

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 Traffic measurements

Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --
Feature Name Support of TFO (Tandem Free Operation)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-19
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C171 - NB_TFO_CODEC_REQ
Speech
....................................................................................................................................................................................................................................

C171 - NB_TFO_CODEC_REQ
Descripton

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 Traffic measurements


Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --
Feature Name Support of TFO (Tandem Free Operation)

....................................................................................................................................................................................................................................
2-20 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Telecom Procedure (QoS)

Overview
Purpose
This section contains Telecom Procedure (QoS) parameters.

Contents

C01 - NB_IMM_ASS_SUCC_MT 2-22


C02 - NB_IMM_ASS_SUCC_MO 2-22
C02a - NB_IMM_ASS_SUCC_MO_LOC_UPD 2-23
C02b - NB_IMM_ASS_SUCC_MO_SMS 2-23
C02c - NB_IMM_ASS_SUCC_MO_SUP_SERV 2-24
C02d - NB_IMM_ASS_SUCC_MO_FOLLOW_ON 2-24
C02e - NB_IMM_ASS_SUCC_MO_CM_REEST 2-25
C02f - NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW 2-26
C02g - NB_IMM_ASS_SUCC_MO_IMSI_DETACH 2-26
C02h - NB_IMM_ASS_SUCC_MO_CALL_EST 2-27
C02i - NB_IMM_ASS_SUCC_MO_LCS 2-27
C04 - NB_IMM_ASS_PREP_FAIL_CONG 2-28
C149 - NB_IMM_ASS_EXEC_FAIL_RADIO 2-28
C161a - NB_DTAP_MO_NOR_ASS_SUCC 2-29
C161b - NB_DTAP_MT_NOR_ASS_SUCC 2-29
C612a - NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE 2-30
C612b - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL 2-31
C612c - NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP 2-31
C612d - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ 2-32
C718 - NB_TCH_NOR_ASS_SUCC_TRX 2-33
C746b - NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX 2-34
C812 - NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS 2-34
C901 - NB_Suspend_Resume_req 2-35
C902 - Nb_Suspend_fail 2-36

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-21
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

C903 - Nb_Suspend_succ 2-36

C01 - NB_IMM_ASS_SUCC_MT
Descripton

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 Telecom Procedure (QoS)


Sub Domain 2 Immediate Assignment
Sub Domain 3 Success
Measured Object Common cell
Type Name Traffic measurements

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

Feature Name --

C02 - NB_IMM_ASS_SUCC_MO
Descripton

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 Telecom Procedure (QoS)
Sub Domain 2 Immediate Assignment

Sub Domain 3 Success

Measured Object Common cell


Type Name Traffic measurements

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

....................................................................................................................................................................................................................................
2-22 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C02 - NB_IMM_ASS_SUCC_MO
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

External Comment --

Feature Name --

C02a - NB_IMM_ASS_SUCC_MO_LOC_UPD
Descripton

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 Telecom Procedure (QoS)

Sub Domain 2 Immediate Assignment


Sub Domain 3 Success

Measured Object Common cell


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

External Comment --
Feature Name --

C02b - NB_IMM_ASS_SUCC_MO_SMS
Descripton

Long Name NB_IMM_ASS_SUCC_MO_SMS


Definition case: SMS procedure on SDCCH

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from 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 "SMS".
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.
Sub Domain 1 Telecom Procedure (QoS)

Sub Domain 2 Immediate Assignment


Sub Domain 3 Success

Measured Object Common cell

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-23
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C02b - NB_IMM_ASS_SUCC_MO_SMS
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Type Name Traffic measurements

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

Feature Name --

C02c - NB_IMM_ASS_SUCC_MO_SUP_SERV
Descripton

Long Name NB_IMM_ASS_SUCC_MO_SUP_SERV

Definition case: Supplementary Service


Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from 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 "Supplementary Service".
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.
Sub Domain 1 Telecom Procedure (QoS)

Sub Domain 2 Immediate Assignment


Sub Domain 3 Success
Measured Object Common cell
Type Name Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --
Feature Name --

C02d - NB_IMM_ASS_SUCC_MO_FOLLOW_ON
Descripton

Long Name NB_IMM_ASS_SUCC_MO_FOLLOW_ON

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

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from 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 1.
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.

Sub Domain 1 Telecom Procedure (QoS)


Sub Domain 2 Immediate Assignment

....................................................................................................................................................................................................................................
2-24 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C02d - NB_IMM_ASS_SUCC_MO_FOLLOW_ON
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Sub Domain 3 Success

Measured Object Common cell


Type Name Traffic measurements

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

Feature Name --

C02e - NB_IMM_ASS_SUCC_MO_CM_REEST
Descripton

Long Name NB_IMM_ASS_SUCC_MO_CM_REEST


Definition case: CM Re-establishment procedure
Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from a CELL, with the L3
INFORMATION field containing a 44.018 L3 message with an MIE message type set to CM
RE-ESTABLISHMENT REQUEST message.
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.

Sub Domain 1 Telecom Procedure (QoS)


Sub Domain 2 Immediate Assignment

Sub Domain 3 Success


Measured Object Common cell
Type Name Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-25
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C02f - NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

C02f - NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW
Descripton

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 Telecom Procedure (QoS)


Sub Domain 2 Immediate Assignment

Sub Domain 3 Success


Measured Object Common cell

Type Name Traffic measurements


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

Feature Name --

C02g - NB_IMM_ASS_SUCC_MO_IMSI_DETACH
Descripton

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 Whenever an 48.058 ESTABLISH INDICATION message is received from a 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 Telecom Procedure (QoS)

Sub Domain 2 Immediate Assignment

Sub Domain 3 Success


Measured Object Common cell

Type Name Traffic measurements


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

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
2-26 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C02h - NB_IMM_ASS_SUCC_MO_CALL_EST
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

C02h - NB_IMM_ASS_SUCC_MO_CALL_EST
Descripton

Long Name NB_IMM_ASS_SUCC_MO_CALL_EST

Definition case: normal or emergency call establishment


Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from a 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 Telecom Procedure (QoS)

Sub Domain 2 Immediate Assignment


Sub Domain 3 Success

Measured Object Common cell


Type Name Traffic measurements

Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --
Feature Name --

C02i - NB_IMM_ASS_SUCC_MO_LCS
Descripton

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 Telecom Procedure (QoS)

Sub Domain 2 Immediate Assignment

Sub Domain 3 Success


Measured Object Common cell
Type Name Traffic measurements

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

External Comment --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-27
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C02i - NB_IMM_ASS_SUCC_MO_LCS
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Feature Name Location services (LCS)

C04 - NB_IMM_ASS_PREP_FAIL_CONG
Descripton

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 Telecom Procedure (QoS)


Sub Domain 2 Immediate Assignment

Sub Domain 3 Failure


Measured Object Common cell
Type Name Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --

Feature Name --

C149 - NB_IMM_ASS_EXEC_FAIL_RADIO
Descripton

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 Telecom Procedure (QoS)

Sub Domain 2 Immediate Assignment


Sub Domain 3 Failure
Measured Object Common cell

Type Name Traffic measurements

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

Feature Name --

....................................................................................................................................................................................................................................
2-28 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C161a - NB_DTAP_MO_NOR_ASS_SUCC
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

C161a - NB_DTAP_MO_NOR_ASS_SUCC
Descripton

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 Telecom Procedure (QoS)


Sub Domain 2 DTAP Assignment

Sub Domain 3 Success


Measured Object Common cell

Type Name Traffic measurements


Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --
Feature Name --

C161b - NB_DTAP_MT_NOR_ASS_SUCC
Descripton

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 Telecom Procedure (QoS)
Sub Domain 2 DTAP Assignment

Sub Domain 3 Success

Measured Object Common cell


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

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-29
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C612a - NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

C612a - NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE
Descripton

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 Telecom Procedure (QoS)
Sub Domain 2 Normal Assignment
Sub Domain 3 Failure
Measured Object Common cell
Type Name Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --

Feature Name --

....................................................................................................................................................................................................................................
2-30 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C612b - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

C612b - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL
Descripton

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 The counter is incremented upon the sending of 48.008 ASSIGNMENT FAILURE (cause: "no radio
resource available") for a TCH channel because the queue is full and no request of lower priority can be
dequeued.
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 status;
- or the TCH processing capacity of AbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_
TCH_TS parameter

Sub Domain 1 Telecom Procedure (QoS)


Sub Domain 2 Normal Assignment
Sub Domain 3 Failure
Measured Object Common cell
Type Name Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --

Feature Name --

C612c - NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP
Descripton

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.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-31
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C612c - NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

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 Telecom Procedure (QoS)

Sub Domain 2 --
Sub Domain 3 Failure
Measured Object Common cell

Type Name Traffic measurements

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

Feature Name --

C612d - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ
Descripton

Long Name NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ


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

....................................................................................................................................................................................................................................
2-32 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C612d - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Sub Domain 1 Telecom Procedure (QoS)

Sub Domain 2 Normal Assignment


Sub Domain 3 Failure

Measured Object Common cell


Type Name Traffic measurements

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

Feature Name --

C718 - NB_TCH_NOR_ASS_SUCC_TRX
Descripton

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 Telecom Procedure (QoS)

Sub Domain 2 Normal Assignment


Sub Domain 3 Success
Measured Object TRX
Type Name Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures

External Comment --
Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-33
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C746b - NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

C746b - NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX
Descripton

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 Telecom Procedure (QoS)


Sub Domain 2 Normal Assignment
Sub Domain 3 Failure
Measured Object TRX
Type Name Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --

Feature Name B7.1 counters improvements

C812 - NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS
Descripton

Long Name NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS


Definition MC812 = C812 = C612a + C612b + C612c + C612d
Trigger condition --

Sub Domain 1 Telecom Procedure (QoS)

Sub Domain 2 Normal Assignment


Sub Domain 3 Failure

Measured Object Common cell

....................................................................................................................................................................................................................................
2-34 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C812 - NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Type Name Traffic measurements

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

Feature Name --

C901 - NB_Suspend_Resume_req
Descripton

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 Traffic measurements

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

Feature Name Suspend/Resume for class B mobiles

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 2-35
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C902 - Nb_Suspend_fail
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

C902 - Nb_Suspend_fail
Descripton

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 Telecom Procedure (QoS)


Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name Traffic measurements


Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --
Feature Name Suspend/Resume for class B mobiles

C903 - Nb_Suspend_succ
Descripton

Long Name Nb_Suspend_succ


Definition Number of suspensions successes.
Trigger condition Reception of Resume ack message from MFS.
Sub Domain 1 Telecom Procedure (QoS)
Sub Domain 2 --

Sub Domain 3 --

Measured Object Common cell


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

External Comment --

Feature Name Suspend/Resume for class B mobiles

....................................................................................................................................................................................................................................
2-36 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
3 3esource Availability &
R
Usage

Resource Allocation & Management

Overview
Purpose
This section contains Resource Allocation & Management parameters.

Contents

C442 - NB_TIMES_TRAF_DETECTED_HIGH 3-2


C443 - NB_TIMES_TRAF_DETECTED_LOW 3-2
C701a - NB_TCH_FR_REQ 3-3
C701b - NB_TCH_DR_REQ 3-3
C701c - NB_TCH_DR_EFR_REQ 3-4
C701d - NB_TCH_AMR_REQ 3-4
C701e - NB_TCH_DATA_REQ 3-5
C702a - NB_TCH_NOR_FR_ALLOC 3-5
C702b - NB_TCH_NOR_HR_ALLOC 3-6
C702c - NB_TCH_NOR_EFR_ALLOC 3-6
C704a - NB_TCH_NOR_AMR_FR_ALLOC 3-7
C704b - NB_TCH_NOR_AMR_HR_ALLOC 3-7
C705 - NB_TCH_NOR_DATA_ALLOC 3-8
C706 - NB_EGSM_MS_ACCESS_EXCEPT_LU 3-8

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 3-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C442 - NB_TIMES_TRAF_DETECTED_HIGH
Resource Allocation & Management
....................................................................................................................................................................................................................................

C442 - NB_TIMES_TRAF_DETECTED_HIGH
Descripton

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 timeslots (in TCH usage). A radio timeslot in TCH VAMOS usage
is said not free when at least one of the VAMOS subchannels is busy.
Trigger condition At each A_TRAFFIC_LOAD period, whenever the BSC decision process detects a "high" traffic_load.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Normal Assignment

Sub Domain 3 --
Measured Object Common cell
Type Name Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --

Feature Name --

C443 - NB_TIMES_TRAF_DETECTED_LOW
Descripton

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 timeslots (in TCH usage). A radio timeslot in TCH VAMOS usage
is said not free when at least one of the VAMOS subchannels is busy.
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 --

....................................................................................................................................................................................................................................
3-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C443 - NB_TIMES_TRAF_DETECTED_LOW
Resource Allocation & Management
....................................................................................................................................................................................................................................

Measured Object Common cell

Type Name Traffic measurements


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

External Comment --
Feature Name --

C701a - NB_TCH_FR_REQ
Descripton

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 Resource Allocation & Management


Sub Domain 2 Service
Sub Domain 3 --
Measured Object Common cell
Type Name Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --

Feature Name B7.1 counters improvements

C701b - NB_TCH_DR_REQ
Descripton

Long Name NB_TCH_DR_REQ


Definition Number of TCH normal assignments requests from dual rate mobiles.
Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call with only GSM speech coding
algorithm version 1 full rate and GSM speech coding algorithm version 1 half rate allowed.
Sub Domain 1 Resource Allocation & Management

Sub Domain 2 Service

Sub Domain 3 --
Measured Object Common cell
Type Name Traffic measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 3-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C701b - NB_TCH_DR_REQ
Resource Allocation & Management
....................................................................................................................................................................................................................................

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

External Comment --
Feature Name B7.1 counters improvements

C701c - NB_TCH_DR_EFR_REQ
Descripton

Long Name NB_TCH_DR_EFR_REQ

Definition Number of TCH normal assignment requests from mobiles supporting FR, HR and EFR.
Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call with 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 Resource Allocation & Management


Sub Domain 2 Service
Sub Domain 3 --
Measured Object Common cell
Type Name Traffic measurements

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

Feature Name B7.1 counters improvements

C701d - NB_TCH_AMR_REQ
Descripton

Long Name NB_TCH_AMR_REQ

Definition Number of TCH normal assignment requests from AMR mobiles.


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

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service

Sub Domain 3 --

Measured Object Common cell


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

....................................................................................................................................................................................................................................
3-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C701d - NB_TCH_AMR_REQ
Resource Allocation & Management
....................................................................................................................................................................................................................................

External Comment --

Feature Name B7.1 counters improvements

C701e - NB_TCH_DATA_REQ
Descripton

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 Resource Allocation & Management


Sub Domain 2 Service

Sub Domain 3 --
Measured Object Common cell
Type Name Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --
Feature Name B7.1 counters improvements

C702a - NB_TCH_NOR_FR_ALLOC
Descripton

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 Resource Allocation & Management

Sub Domain 2 Service


Sub Domain 3 --
Measured Object Common cell

Type Name Traffic measurements

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 3-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C702a - NB_TCH_NOR_FR_ALLOC
Resource Allocation & Management
....................................................................................................................................................................................................................................

Feature Name B7.1 counters improvements

C702b - NB_TCH_NOR_HR_ALLOC
Descripton

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 Resource Allocation & Management


Sub Domain 2 Service

Sub Domain 3 --
Measured Object Common cell
Type Name Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --

Feature Name B7.1 counters improvements

C702c - NB_TCH_NOR_EFR_ALLOC
Descripton

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 48.058 CHANNEL ACTIVATION/ MODE MODIFY about to be sent to the BTS, indicating a FR channel
with GSM speech coding algorithm version 2, not related to handover.

Sub Domain 1 Resource Allocation & Management

Sub Domain 2 Service


Sub Domain 3 --
Measured Object Common cell

Type Name Traffic measurements

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

....................................................................................................................................................................................................................................
3-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C702c - NB_TCH_NOR_EFR_ALLOC
Resource Allocation & Management
....................................................................................................................................................................................................................................

Feature Name B7.1 counters improvements

C704a - NB_TCH_NOR_AMR_FR_ALLOC
Descripton

Long Name NB_TCH_NOR_AMR_FR_ALLOC

Definition Number of TCH normal assignment/mode modify in FR AMR 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 3, not related to handover.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service
Sub Domain 3 --
Measured Object Common cell
Type Name Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --

Feature Name B7.1 counters improvements

C704b - NB_TCH_NOR_AMR_HR_ALLOC
Descripton

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 48.058 CHANNEL ACTIVATION/ MODE MODIFY about to be sent to the BTS, indicating a HR channel
with GSM speech coding algorithm version 3, not related to handover.

Sub Domain 1 Resource Allocation & Management

Sub Domain 2 Service


Sub Domain 3 --
Measured Object Common cell

Type Name Traffic measurements

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 3-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C704b - NB_TCH_NOR_AMR_HR_ALLOC
Resource Allocation & Management
....................................................................................................................................................................................................................................

Feature Name B7.1 counters improvements

C705 - NB_TCH_NOR_DATA_ALLOC
Descripton

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 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 data call, not
related to handover.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service
Sub Domain 3 --
Measured Object Common cell
Type Name Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --

Feature Name B7.1 counters improvements

C706 - NB_EGSM_MS_ACCESS_EXCEPT_LU
Descripton

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 Resource Allocation & Management


Sub Domain 2 E-GSM

Sub Domain 3 --

Measured Object Common cell

....................................................................................................................................................................................................................................
3-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C706 - NB_EGSM_MS_ACCESS_EXCEPT_LU
Resource Allocation & Management
....................................................................................................................................................................................................................................

Type Name Traffic measurements

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

Feature Name E-GSM support

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 3-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C706 - NB_EGSM_MS_ACCESS_EXCEPT_LU

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
3-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
4 Traffic Load
4

Telecom Procedure (Traffic Load)

Overview
Purpose
This section contains Telecom Procedure (Traffic Load) parameters.

Contents

C13a - NB_TCH_NOR_ASS_QUEUED 4-2


C13b - NB_INC_EXT_TCH_HO_QUEUED 4-2
C147 - NB_INC_SDCCH_HO_ALLOC 4-3
C148 - NB_IMM_ASS_ALLOC 4-4
C15a - NB_INC_IDR_ALLOC 4-4
C15b - NB_INC_TCH_HO_ALLOC 4-5
C703 - NB_TCH_NOR_ASS_ALLOC_TRX 4-5
C850 - NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL 4-6

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 4-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C13a - NB_TCH_NOR_ASS_QUEUED
Telecom Procedure (Traffic Load)
....................................................................................................................................................................................................................................

C13a - NB_TCH_NOR_ASS_QUEUED
Descripton

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 INDICATION message if the queuing is authorised by the MSC,
or,
ii) when the assignment request is queued in the cell if the queuing is not authorised by the MSC and the
parameter QUEUE_ANYWAY is set (in particular when the assignment request is queued due to a forced
directed retry (cause 20) or preferred band forced directed retry (cause 36)), 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 Telecom Procedure (Traffic Load)
Sub Domain 2 Normal Assignment
Sub Domain 3 --

Measured Object Common cell


Type Name Traffic measurements

Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --
Feature Name --

C13b - NB_INC_EXT_TCH_HO_QUEUED
Descripton

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 Telecom Procedure (Traffic Load)

....................................................................................................................................................................................................................................
4-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C13b - NB_INC_EXT_TCH_HO_QUEUED
Telecom Procedure (Traffic Load)
....................................................................................................................................................................................................................................

Sub Domain 2 Handover

Sub Domain 3 TCH


Measured Object Common cell

Type Name Traffic measurements


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

External Comment --
Feature Name --

C147 - NB_INC_SDCCH_HO_ALLOC
Descripton

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: This counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 Telecom Procedure (Traffic Load)


Sub Domain 2 Handover

Sub Domain 3 SDCCH


Measured Object Common cell
Type Name Traffic measurements
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 4-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C148 - NB_IMM_ASS_ALLOC
Telecom Procedure (Traffic Load)
....................................................................................................................................................................................................................................

C148 - NB_IMM_ASS_ALLOC
Descripton

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 Telecom Procedure (Traffic Load)


Sub Domain 2 Immediate Assignment

Sub Domain 3 --

Measured Object Common cell


Type Name Traffic measurements

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

Feature Name --

C15a - NB_INC_IDR_ALLOC
Descripton

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 Traffic measurements

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

Feature Name --

....................................................................................................................................................................................................................................
4-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C15b - NB_INC_TCH_HO_ALLOC
Telecom Procedure (Traffic Load)
....................................................................................................................................................................................................................................

C15b - NB_INC_TCH_HO_ALLOC
Descripton

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 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 any handover procedure.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 Telecom Procedure (Traffic Load)


Sub Domain 2 Handover

Sub Domain 3 TCH


Measured Object Common cell

Type Name Traffic measurements


Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment --
Feature Name --

C703 - NB_TCH_NOR_ASS_ALLOC_TRX
Descripton

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 Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent on Abis Interface to activate a
TCH channel for normal assignment, or for DTM assignment with a TCH in signaling mode.

Sub Domain 1 Telecom Procedure (Traffic Load)


Sub Domain 2 Normal Assignment
Sub Domain 3 --

Measured Object TRX

Type Name Traffic measurements


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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 4-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C703 - NB_TCH_NOR_ASS_ALLOC_TRX
Telecom Procedure (Traffic Load)
....................................................................................................................................................................................................................................

External Comment --

Feature Name B7.1 counters improvements

C850 - NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL
Descripton

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 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".
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 Telecom Procedure (Traffic Load)
Sub Domain 2 Multiband

Sub Domain 3 --
Measured Object Common cell
Type Name Traffic measurements

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

External Comment --
Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
4-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C850 - NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 4-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C850 - NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
4-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part II: BSC-TYPE 2 - Resource
availability measurements

Overview
Purpose
All type 2.

Contents

Chapter 5, Resource Availability & Usage 5-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R II-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 2 - Resource availability measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
II-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
5 5esource Availability &
R
Usage

Channel

Overview
Purpose
This section contains Channel parameters.

Contents

C141 - AV_NB_TCH_QUEUED 5-2


C24 - AV_NB_NOT_AVAIL_TRX_TS 5-2
C250 - AV_NB_AVAIL_TCH 5-3
C26 - AV_NB_AVAIL_SDCCH 5-3
C27 - AV_NB_AVAIL_CCCH 5-4
C28a - AV_NB_BUSY_CS_TS 5-4
C29a - NB_MAX_SIMUL_BUSY_CS_TS 5-5
C30 - AV_NB_BUSY_SDCCH 5-6
C31 - NB_MAX_SIMUL_BUSY_SDCCH 5-6
C320a - AV_NB_IDLE_TCH_INTERF_BAND1 5-7
C320b - AV_NB_IDLE_TCH_INTERF_BAND2 5-8
C320c - AV_NB_IDLE_TCH_INTERF_BAND3 5-9
C320d - AV_NB_IDLE_TCH_INTERF_BAND4 5-10
C320e - AV_NB_IDLE_TCH_INTERF_BAND5 5-11
C34 - TIME_ALL_AVAIL_TRX_TS_BUSY 5-12
C803 - TIME_SDCCH_CONGESTION 5-12

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 5-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C141 - AV_NB_TCH_QUEUED
Channel
....................................................................................................................................................................................................................................

C141 - AV_NB_TCH_QUEUED
Descripton

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 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. In order to provide one decimal place, the averaged
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 TCH


Sub Domain 3 Usage
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 --
Feature Name --

C24 - AV_NB_NOT_AVAIL_TRX_TS
Descripton

Long Name AV_NB_NOT_AVAIL_TRX_TS


Definition Average number of not available radio timeslots (TRX_TS). The timeslot is not available if it is "blocked" or
"out of service".

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 TRX_TS

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

....................................................................................................................................................................................................................................
5-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C24 - AV_NB_NOT_AVAIL_TRX_TS
Channel
....................................................................................................................................................................................................................................

Feature Name --

C250 - AV_NB_AVAIL_TCH
Descripton

Long Name AV_NB_AVAIL_TCH

Definition Average number of available radio timeslots for traffic usage (i.e. TCH (for HR or FR usage in VAMOS
mode or not) or PDCH).
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 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 Resource availability measurements
Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment --

Feature Name --

C26 - AV_NB_AVAIL_SDCCH
Descripton

Long Name AV_NB_AVAIL_SDCCH

Definition Average number of available static SDCCH sub-channels (i.e. on static SDCCH timeslots).
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.
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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 5-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C26 - AV_NB_AVAIL_SDCCH
Channel
....................................................................................................................................................................................................................................

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 --
Feature Name --

C27 - AV_NB_AVAIL_CCCH
Descripton

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

Feature Name --

C28a - AV_NB_BUSY_CS_TS
Descripton

Long Name AV_NB_BUSY_CS_TS


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

....................................................................................................................................................................................................................................
5-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C28a - AV_NB_BUSY_CS_TS
Channel
....................................................................................................................................................................................................................................

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 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 radio timeslot in VAMOS usage is said busy when at least one of the VAMOS subchannels is
busy. 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 Resource availability measurements


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

External Comment --
Feature Name --

C29a - NB_MAX_SIMUL_BUSY_CS_TS
Descripton

Long Name NB_MAX_SIMUL_BUSY_CS_TS


Definition Maximum number of simultaneously busy radio timeslots (in HR TCH or FR TCH 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 radio timeslots (in HR TCH or FR TCH usage) and busy
dynamic SDCCH/8 radio timeslots allocated as TCH. A radio timeslot in VAMOS usage is said busy when
at least one of the VAMOS subchannels is busy. 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 Resource availability measurements

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 5-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C29a - NB_MAX_SIMUL_BUSY_CS_TS
Channel
....................................................................................................................................................................................................................................

External Comment --

Feature Name Dynamic SDCCH allocation

C30 - AV_NB_BUSY_SDCCH
Descripton

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 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. 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 Resource availability measurements


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

External Comment --
Feature Name --

C31 - NB_MAX_SIMUL_BUSY_SDCCH
Descripton

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

....................................................................................................................................................................................................................................
5-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C31 - NB_MAX_SIMUL_BUSY_SDCCH
Channel
....................................................................................................................................................................................................................................

Sub Domain 3 Usage

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

Feature Name --

C320a - AV_NB_IDLE_TCH_INTERF_BAND1
Descripton

Long Name AV_NB_IDLE_TCH_INTERF_BAND1


Definition Average number of radio timeslots with free resources (timeslot in TCH usage and dynamic SDCCH/8
allocated as TCH) belonging to the interference band 1. This number is updated upon the receipt of 48.058
RF RESOURCE INDICATION. In this message, one interference level is reported for every time slot with
an idle channel or an idle subchannel
When VAMOS is enabled, the BTS sends idle measurements only when the physical resource is unused:
-For an idle channel, BTS sends idle measurement for a channel.
-When a FR TCH is allocated in non-VAMOS mode, then no idle measurements is sent.
-When a HR TCH is allocated in non-VAMOS mode, the BTS reports idle measurements if the other
subchannel on the same timeslot is idle.
-When a MS is allocated in non-VAMOS mode on a HR TCH and another MS is allocated in non-VAMOS
mode in the other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and one MS is allocated in non-VAMOS mode in the
other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and the other subchannel on the same timeslot is idle,
then idle measurements is sent for the idle subchannel.

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 TCH

Sub Domain 3 Usage

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 --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 5-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C320b - AV_NB_IDLE_TCH_INTERF_BAND2
Channel
....................................................................................................................................................................................................................................

C320b - AV_NB_IDLE_TCH_INTERF_BAND2
Descripton

Long Name AV_NB_IDLE_TCH_INTERF_BAND2

Definition Average number of radio timeslots with free resources (timeslot in TCH usage and free dynamic SDCCH/8
allocated as TCH) belonging to the interference band 2. This number is updated upon the receipt of 48.058
RF RESOURCE INDICATION.In this message, one interference level is reported for every time slot with
an idle channel or an idle subchannel
When VAMOS is enabled, the BTS sends idle measurements only when the physical resource is unused:
-For an idle channel, BTS sends idle measurement for a channel.
-When a FR TCH is allocated in non-VAMOS mode, then no idle measurements is sent.
-When a HR TCH is allocated in non-VAMOS mode, the BTS reports idle measurements if the other
subchannel on the same timeslot is idle.
-When a MS is allocated in non-VAMOS mode on a HR TCH and another MS is allocated in non-VAMOS
mode in the other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and one MS is allocated in non-VAMOS mode in the
other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and the other subchannel on the same timeslot is idle,
then idle measurements is sent for the idle subchannel.
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 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 Resource availability measurements

Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment --
Feature Name --

....................................................................................................................................................................................................................................
5-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C320c - AV_NB_IDLE_TCH_INTERF_BAND3
Channel
....................................................................................................................................................................................................................................

C320c - AV_NB_IDLE_TCH_INTERF_BAND3
Descripton

Long Name AV_NB_IDLE_TCH_INTERF_BAND3

Definition Average number of radio timeslots with free resources (timeslot in TCH usage and dynamic SDCCH/8
allocated as TCH) belonging to the interference band 3. This number is updated upon the receipt of 48.058
RF RESOURCE INDICATION.In this message, one interference level is reported for every time slot with
an idle channel or an idle subchannel
When VAMOS is enabled, the BTS sends idle measurements only when the physical resource is unused:
-For an idle channel, BTS sends idle measurement for a channel.
-When a FR TCH is allocated in non-VAMOS mode, then no idle measurements is sent.
-When a HR TCH is allocated in non-VAMOS mode, the BTS reports idle measurements if the other
subchannel on the same timeslot is idle.
-When a MS is allocated in non-VAMOS mode on a HR TCH and another MS is allocated in non-VAMOS
mode in the other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and one MS is allocated in non-VAMOS mode in the
other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and the other subchannel on the same timeslot is idle,
then idle measurements is sent for the idle subchannel.
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 TCH

Sub Domain 3 Usage


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 --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 5-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C320d - AV_NB_IDLE_TCH_INTERF_BAND4
Channel
....................................................................................................................................................................................................................................

C320d - AV_NB_IDLE_TCH_INTERF_BAND4
Descripton

Long Name AV_NB_IDLE_TCH_INTERF_BAND4

Definition Average number of radio timeslots with free resources (timeslot in TCH usage and dynamic SDCCH/8
allocated as TCH) belonging to the interference band 4. This number is updated upon the receipt of 48.058
RF RESOURCE INDICATION.In this message, one interference level is reported for every time slot with
an idle channel or an idle subchannel
When VAMOS is enabled, the BTS sends idle measurements only when the physical resource is unused:
-For an idle channel, BTS sends idle measurement for a channel.
-When a FR TCH is allocated in non-VAMOS mode, then no idle measurements is sent.
-When a HR TCH is allocated in non-VAMOS mode, the BTS reports idle measurements if the other
subchannel on the same timeslot is idle.
-When a MS is allocated in non-VAMOS mode on a HR TCH and another MS is allocated in non-VAMOS
mode in the other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and one MS is allocated in non-VAMOS mode in the
other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and the other subchannel on the same timeslot is idle,
then idle measurements is sent for the idle subchannel.
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 TCH

Sub Domain 3 Usage


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 --
Feature Name --

....................................................................................................................................................................................................................................
5-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C320e - AV_NB_IDLE_TCH_INTERF_BAND5
Channel
....................................................................................................................................................................................................................................

C320e - AV_NB_IDLE_TCH_INTERF_BAND5
Descripton

Long Name AV_NB_IDLE_TCH_INTERF_BAND5

Definition Average number of radio timeslots with free resources (timeslot in TCH usage and dynamic SDCCH/8
allocated as TCH) belonging to the interference band 5. This number is updated upon the receipt of 48.058
RF RESOURCE INDICATION.In this message, one interference level is reported for every time slot with
an idle channel or an idle subchannel
When VAMOS is enabled, the BTS sends idle measurements only when the physical resource is unused:
-For an idle channel, BTS sends idle measurement for a channel.
-When a FR TCH is allocated in non-VAMOS mode, then no idle measurements is sent.
-When a HR TCH is allocated in non-VAMOS mode, the BTS reports idle measurements if the other
subchannel on the same timeslot is idle.
-When a MS is allocated in non-VAMOS mode on a HR TCH and another MS is allocated in non-VAMOS
mode in the other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and one MS is allocated in non-VAMOS mode in the
other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and the other subchannel on the same timeslot is idle,
then idle measurements is sent for the idle subchannel.
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 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 Resource availability measurements

Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 5-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C34 - TIME_ALL_AVAIL_TRX_TS_BUSY
Channel
....................................................................................................................................................................................................................................

C34 - TIME_ALL_AVAIL_TRX_TS_BUSY
Descripton

Long Name TIME_ALL_AVAIL_TRX_TS_BUSY

Definition Cumulated time (in seconds) during which there is no free radio timeslot to serve an incoming FR TCH
request.
A radio timeslot is seen as busy:
i) if the timeslot is occupied by a HR TCH or FR TCH CS call in VAMOS or non-VAMOS mode (in
particular if it is occupied by the CS part of a DTM call), or
ii) if the timeslot is allocated to the MFS to carry PS traffic.
Trigger condition The counter is started when there is no free radio timeslot to serve an incoming FR TCH request.
The counter is stopped when there is a free radio timeslot 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 Resource availability measurements


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

External Comment --
Feature Name Dynamic SDCCH allocation

C803 - TIME_SDCCH_CONGESTION
Descripton

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

....................................................................................................................................................................................................................................
5-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C803 - TIME_SDCCH_CONGESTION
Channel
....................................................................................................................................................................................................................................

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 --
Feature Name Dynamic SDCCH allocation

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 5-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C803 - TIME_SDCCH_CONGESTION

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
5-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part III: BSC-TYPE 3 - Resource
usage on CCCH channel
measurements

Overview
Purpose
All type 3.

Contents

Chapter 6, Traffic Load 6-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R III-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 3 - Resource usage on CCCH channel Overview
measurements
....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
III-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
6 Traffic Load
6

Radio Channel (Traffic Load)

Overview
Purpose
This section contains Radio Channel (Traffic Load) parameters.

Contents

C8a - NB_PAGING_CMD 6-1


C8b - NB_IMM_ASS_CMD 6-2
C8c - NB_CHAN_REQD 6-2
C8d - NB_IMM_ASS_REJ 6-3

C8a - NB_PAGING_CMD
Descripton

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 Radio Channel (Traffic Load)

Sub Domain 2 CCCH


Sub Domain 3 --

Measured Object TRX_TS

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 6-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C8a - NB_PAGING_CMD
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

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

Feature Name --

C8b - NB_IMM_ASS_CMD
Descripton

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 Radio Channel (Traffic Load)
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 --
Feature Name --

C8c - NB_CHAN_REQD
Descripton

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 Radio Channel (Traffic Load)

Sub Domain 2 CCCH


Sub Domain 3 --

....................................................................................................................................................................................................................................
6-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C8c - NB_CHAN_REQD
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

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 --
Feature Name --

C8d - NB_IMM_ASS_REJ
Descripton

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 Radio Channel (Traffic Load)
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 --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 6-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C8d - NB_IMM_ASS_REJ

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
6-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part IV: BSC-TYPE 4 - Resource
usage on SDCCH channel
measurements

Overview
Purpose
All type 4.

Contents

Chapter 7, Resource Availability & Usage 7-1


Chapter 8, Traffic Load 8-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R IV-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 4 - Resource usage on SDCCH channel Overview
measurements
....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
IV-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
7 7esource Availability &
R
Usage

Channel

Overview
Purpose
This section contains Channel parameters.

Contents

C39 - NB_TIMES_SDCCH_BUSY 7-1

C39 - NB_TIMES_SDCCH_BUSY
Descripton

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

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 7-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C39 - NB_TIMES_SDCCH_BUSY
Channel
....................................................................................................................................................................................................................................

Feature Name --

....................................................................................................................................................................................................................................
7-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
8 Traffic Load
8

Radio Channel (Traffic Load)

Overview
Purpose
This section contains Radio Channel (Traffic Load) parameters.

Contents

C40 - TIME_SDCCH_BUSY 8-1

C40 - TIME_SDCCH_BUSY
Descripton

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.

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 8-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C40 - TIME_SDCCH_BUSY
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

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 Radio Channel (Traffic Load)

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 --
Feature Name --

....................................................................................................................................................................................................................................
8-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C40 - TIME_SDCCH_BUSY

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 8-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C40 - TIME_SDCCH_BUSY

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
8-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part V: BSC-TYPE 5 - Resource
usage on TCH channel
measurements

Overview
Purpose
All type 5.

Contents

Chapter 9, Resource Availability & Usage 9-1


Chapter 10, Traffic Load 10-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R V-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 5 - Resource usage on TCH channel measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
V-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
9 9esource Availability &
R
Usage

Channel

Overview
Purpose
This section contains Channel parameters.

Contents

C370a - NB_TCH_FR_ALLOC 9-1


C370b - NB_TCH_HR_ALLOC 9-2

C370a - NB_TCH_FR_ALLOC
Descripton

Long Name NB_TCH_FR_ALLOC


Definition Number of times a radio timeslot (TCH or a dynamic SDCCH/8 allocated as TCH) 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. In
VAMOS mode, the counter is incremented for each FR TCH VAMOS subchannel of the timeslot.
Sub Domain 1 Channel

Sub Domain 2 TCH

Sub Domain 3 Usage


Measured Object TRX_TS
Type Name Resource usage on TCH channel measurements

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 9-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage C370a - NB_TCH_FR_ALLOC
Channel
....................................................................................................................................................................................................................................

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

External Comment --
Feature Name --

C370b - NB_TCH_HR_ALLOC
Descripton

Long Name NB_TCH_HR_ALLOC

Definition Number of times a radio timeslot (TCH or a dynamic SDCCH/8 allocated as TCH) is allocated in HR usage,
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. In VAMOS mode, the counter is
incremented for each HR TCH VAMOS subchannel of the timeslot.

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

Feature Name --

....................................................................................................................................................................................................................................
9-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
10 Traffic Load
10

Radio Channel (Traffic Load)

Overview
Purpose
This section contains Radio Channel (Traffic Load) parameters.

Contents

C380a - TIME_FR_TCH_BUSY 10-1


C380b - TIME_HR_TCH_BUSY 10-2
C381a - TIME_FR_TCH_BUSY_BY_MULTIBAND_MS 10-3
C381b - TIME_HR_TCH_BUSY_BY_MULTIBAND_MS 10-5

C380a - TIME_FR_TCH_BUSY
Descripton

Long Name TIME_FR_TCH_BUSY


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

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 10-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C380a - TIME_FR_TCH_BUSY
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

Trigger condition In non-VAMOS mode, the counter cumulates over the Accumulation Period, per radio timeslot, all unit
times during which the TCH FR channel is busy.In VAMOS mode, The counter cumulates, over the
Accumulation Period all unit times during which a VAMOS TCH FR channel of the timeslot is busy. Both
VAMOS TCH FR of the timeslot are counted independently.
For example, in an extreme case of 100% VAMOS FR allocations for 1 hour on 1 TRX, C380a will count
2*3600s.
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) or in VAMOS mode a FR
VAMOS subchannel, 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 Radio Channel (Traffic Load)


Sub Domain 2 TCH

Sub Domain 3 --
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 --

Feature Name --

C380b - TIME_HR_TCH_BUSY
Descripton

Long Name TIME_HR_TCH_BUSY

Definition Time during which a radio timeslot (TCH or a dynamic SDCCH/8) in TCH HR usage is busy.

....................................................................................................................................................................................................................................
10-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C380b - TIME_HR_TCH_BUSY
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

Trigger condition In non-VAMOS mode, 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.In VAMOS mode, the counter cumulates, over the Accumulation Period all unit
times during which a
VAMOS TCH HR channel of the timeslot is busy. All VAMOS TCH HR of the timeslot are counted
independently.
For example, in an extreme case of 100% VAMOS HR allocations for 1 hour on 1 TRX, C380b will count
4*3600s.
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 or in VAMOS mode an HR VAMOS subchannel mapped on
any place of the related TRX timeslot..
2) The counter stops being incremented when no HR 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 Radio Channel (Traffic Load)


Sub Domain 2 TCH

Sub Domain 3 --
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 --
Feature Name --

C381a - TIME_FR_TCH_BUSY_BY_MULTIBAND_MS
Descripton

Long Name TIME_FR_TCH_BUSY_BY_MULTIBAND_MS

Definition Time (in seconds) during which the radio timeslot (TCH or the dynamic SDCCH/8) in TCH 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 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".

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 10-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C381a - TIME_FR_TCH_BUSY_BY_MULTIBAND_MS
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

Trigger condition In non-VAMOS mode, 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).In VAMOS mode, the counter cumulates, over the Accumulation Period all unit times
during which a VAMOS TCH FR channel of the timeslot is busy. Both VAMOS TCH FR of the timeslot are
counted independently.
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 or in VAMOS
mode a FR VAMOS subchannel 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 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 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".
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 Radio Channel (Traffic Load)
Sub Domain 2 TCH
Sub Domain 3 --
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 --

Feature Name --

....................................................................................................................................................................................................................................
10-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C381b - TIME_HR_TCH_BUSY_BY_MULTIBAND_MS
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

C381b - TIME_HR_TCH_BUSY_BY_MULTIBAND_MS
Descripton

Long Name TIME_HR_TCH_BUSY_BY_MULTIBAND_MS

Definition Time during which the radio timeslot (TCH or the dynamic SDCCH/8) in TCH HR usage is busy by a
multiband mobile station. A radio timeslot (TCH 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 in non-VAMOS mode, or at least
one HR VAMOS subchannel is busy
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 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.In VAMOS mode, the counter cumulates,
over the Accumulation Period all unit times during which a VAMOS TCH HR channel of the timeslot is
busy. All VAMOS TCH HR of the timeslot are counted independently
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.
- in VAMOS mode an HR VAMOS subchannel mapped on any place 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 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".
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 Radio Channel (Traffic Load)

Sub Domain 2 TCH

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 10-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C381b - TIME_HR_TCH_BUSY_BY_MULTIBAND_MS
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

Sub Domain 3 --

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

Feature Name --

....................................................................................................................................................................................................................................
10-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C381b - TIME_HR_TCH_BUSY_BY_MULTIBAND_MS

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 10-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C381b - TIME_HR_TCH_BUSY_BY_MULTIBAND_MS

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
10-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part VI: BSC-TYPE 6 - TCH
handover measurements

Overview
Purpose
All type 6.

Contents

Chapter 11, Handover 11-1


Chapter 12, Traffic Load 12-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R VI-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 6 - TCH handover measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
VI-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
11 Handover
11

SDCCH+TCH

Overview
Purpose
This section contains SDCCH+TCH parameters.

Contents

C440 - NB_TCH_HO_ATPT_23_TrafHandover 11-1

C440 - NB_TCH_HO_ATPT_23_TrafHandover
Descripton

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 counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 SDCCH+TCH


Sub Domain 2 Cause

Sub Domain 3 --

Measured Object Common cell


Type Name TCH handover measurements

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C440 - NB_TCH_HO_ATPT_23_TrafHandover
SDCCH+TCH
....................................................................................................................................................................................................................................

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 --
Feature Name --

....................................................................................................................................................................................................................................
11-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover Overview
TCH
....................................................................................................................................................................................................................................

TCH

Overview
Purpose
This section contains TCH parameters.

Contents

C220 - NB_INC_EXT_TCH_HO_REQ 11-5


C221 - NB_INC_EXT_TCH_HO_ATPT 11-5
C230 - NB_INC_INT_TCH_HO_REQ 11-6
C231 - NB_INC_INT_TCH_HO_ATPT 11-6
C270 - NB_INTRA_TCH_HO_REQ 11-7
C271 - NB_INTRA_TCH_HO_ATPT 11-7
C411 - NB_OUT_INT_TCH_HO_IDR_IN_ZONE_REQ 11-8
C412 - NB_OUT_INT_TCH_HO_IDR_IN_ZONE_EXEC_FAIL 11-8
C41b - NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH 11-9
C42 - NB_INC_EXT_TCH_HO_SUCC 11-10
C43 - NB_INC_EXT_TCH_HO_EXEC_FAIL_MS_ACCESS 11-10
C444 - NB_TCH_HO_ATPT_24_GenCaptureHandover 11-11
C447 - NB_TCH_HO_ATPT_26_BadQualHR 11-12
C448 - NB_TCH_HO_ATPT_27_GoodQualFR 11-12
C449 - NB_TCH_HO_ATPT_28_FastTraffic 11-13
C450 - NB_TCH_HO_ATPT_22_TooShortDistance 11-13
C45a - NB_OUT_EXT_TCH_REAL_HO_REQ 11-14
C46 - NB_OUT_EXT_TCH_HO_SUCC 11-15
C460 - NB_TCH_HO_ALLOC_EMERGENCY_PRES 11-15
C461 - NB_TCH_HO_ATPT_29_TFO 11-16
C47 - NB_OUT_EXT_TCH_HO_EXEC_FAIL_REV 11-17
C470 - NB_TCH_HO_ATPT_2_TooLowQualUp 11-17
C471 - NB_TCH_HO_ATPT_3_TooLowLevUp 11-18
C472 - NB_TCH_HO_ATPT_4_TooLowQualDown 11-19

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover Overview
TCH
....................................................................................................................................................................................................................................

C473 - NB_TCH_HO_ATPT_5_TooLowLevDown 11-19


C474 - NB_TCH_HO_ATPT_6_TooLongDistance 11-20
C476 - NB_TCH_HO_ATPT_15_TooHighLevInterfUp 11-21
C477 - NB_TCH_HO_ATPT_16_TooHighLevInterfDown 11-21
C478 - NB_TCH_HO_ATPT_12_TooLowPowBudg 11-22
C479 - NB_TCH_HO_ATPT_21_HighLevNeigCellPrefBand 11-22
C48 - NB_OUT_EXT_TCH_HO_EXEC_FAIL_NO_REV 11-23
C50 - NB_OUT_EXT_TCH_HO_ATPT 11-24
C52 - NB_INC_INT_TCH_HO_SUCC 11-24
C53 - NB_INC_INT_TCH_HO_EXEC_FAIL_MS_ACCESS 11-25
C541 - NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS 11-25
C541a - NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS 11-26
C551 - NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS 11-27
C55a - NB_OUT_INT_TCH_HO_REQ 11-27
C56 - NB_OUT_INT_TCH_HO_SUCC 11-28
C561 - NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS 11-29
C57 - NB_OUT_INT_TCH_HO_EXEC_FAIL_REV 11-29
C58 - NB_OUT_INT_TCH_HO_EXEC_FAIL_NO_REV 11-30
C585a - NB_TCH_HO_ATPT_7_ConsBadSACCHmicroCell 11-31
C585d - NB_TCH_HO_ATPT_17_TooLowLevUpMicroCell 11-31
C585e - NB_TCH_HO_ATPT_18_TooLowLevDownMicroCell 11-32
C585f - NB_TCH_HO_ATPT_14_HighLevNeigLowCellSlowMS 11-33
C586a - NB_TCH_HO_ATPT_10_TooLowLevUpInZone 11-33
C586b - NB_TCH_HO_ATPT_11_TooLowLevDownInZone 11-34
C586c - NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone 11-34
C60 - NB_OUT_INT_TCH_HO_ATPT 11-35
C62 - NB_INTRA_TCH_HO_SUCC 11-35
C63 - NB_INTRA_TCH_HO_EXEC_FAIL_NO_REV 11-36
C67 - NB_INTRA_TCH_HO_EXEC_FAIL_REV 11-36
C75 - NB_TCH_HO_MSC_TRIG 11-37

....................................................................................................................................................................................................................................
11-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C220 - NB_INC_EXT_TCH_HO_REQ
TCH
....................................................................................................................................................................................................................................

C220 - NB_INC_EXT_TCH_HO_REQ
Descripton

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 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 --
Feature Name --

C221 - NB_INC_EXT_TCH_HO_ATPT
Descripton

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

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C230 - NB_INC_INT_TCH_HO_REQ
TCH
....................................................................................................................................................................................................................................

C230 - NB_INC_INT_TCH_HO_REQ
Descripton

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

Sub Domain 1 TCH


Sub Domain 2 Incoming Internal

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 --
Feature Name --

C231 - NB_INC_INT_TCH_HO_ATPT
Descripton

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

Feature Name --

....................................................................................................................................................................................................................................
11-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C270 - NB_INTRA_TCH_HO_REQ
TCH
....................................................................................................................................................................................................................................

C270 - NB_INTRA_TCH_HO_REQ
Descripton

Long Name NB_INTRA_TCH_HO_REQ

Definition Number of intra cell TCH (in HR or FR usage) handover requests excluding handover initiation for VAMOS
HO cause 34 and 35. 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, excluding handover initiation for VAMOS HO cause 34 (unpairing) and 35 (pairing).

Sub Domain 1 TCH


Sub Domain 2 Intra

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 --
Feature Name --

C271 - NB_INTRA_TCH_HO_ATPT
Descripton

Long Name NB_INTRA_TCH_HO_ATPT


Definition Number of intra cell TCH (in HR or FR usage) handover attempts excluding handover attempts for VAMOS
HO cause 34 and 35. 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, excluding handover
attempts for VAMOS HO cause 34 and 35.
Sub Domain 1 TCH

Sub Domain 2 Intra


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.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C271 - NB_INTRA_TCH_HO_ATPT
TCH
....................................................................................................................................................................................................................................

External Comment --

Feature Name --

C411 - NB_OUT_INT_TCH_HO_IDR_IN_ZONE_REQ
Descripton

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 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 --
Feature Name --

C412 - NB_OUT_INT_TCH_HO_IDR_IN_ZONE_EXEC_FAIL
Descripton

Long Name NB_OUT_INT_TCH_HO_IDR_IN_ZONE_EXEC_FAIL


Definition Number of outgoing internal inter-cell TCH (in HR or FR usage) handover -executions failures, plus the
number of internal directed retries -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

....................................................................................................................................................................................................................................
11-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C412 - NB_OUT_INT_TCH_HO_IDR_IN_ZONE_EXEC_FAIL
TCH
....................................................................................................................................................................................................................................

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

Feature Name --

C41b - NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH
Descripton

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 intra-PLMN handover events.
Sub Domain 1 TCH

Sub Domain 2 Incoming External


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

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C42 - NB_INC_EXT_TCH_HO_SUCC
TCH
....................................................................................................................................................................................................................................

C42 - NB_INC_EXT_TCH_HO_SUCC
Descripton

Long Name NB_INC_EXT_TCH_HO_SUCC

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


Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abis 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 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 --
Feature Name --

C43 - NB_INC_EXT_TCH_HO_EXEC_FAIL_MS_ACCESS
Descripton

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 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a 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

....................................................................................................................................................................................................................................
11-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C43 - NB_INC_EXT_TCH_HO_EXEC_FAIL_MS_ACCESS
TCH
....................................................................................................................................................................................................................................

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

Feature Name --

C444 - NB_TCH_HO_ATPT_24_GenCaptureHandover
Descripton

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 Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 24. This
counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1 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 --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C447 - NB_TCH_HO_ATPT_26_BadQualHR
TCH
....................................................................................................................................................................................................................................

C447 - NB_TCH_HO_ATPT_26_BadQualHR
Descripton

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 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 --
Feature Name Introduction of AMR (NB-AMR)

C448 - NB_TCH_HO_ATPT_27_GoodQualFR
Descripton

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 Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 27 on TCH.

Sub Domain 1 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 --
Feature Name Introduction of AMR (NB-AMR)

....................................................................................................................................................................................................................................
11-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C449 - NB_TCH_HO_ATPT_28_FastTraffic
TCH
....................................................................................................................................................................................................................................

C449 - NB_TCH_HO_ATPT_28_FastTraffic
Descripton

Long Name NB_TCH_HO_ATPT_28_FastTraffic

Definition Number of handover attempts, with the cause 28 (Fast Traffic Handover).
Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS 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 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 --
Feature Name Instantaneous Peaks Management

C450 - NB_TCH_HO_ATPT_22_TooShortDistance
Descripton

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 because of cause 22 on
TCH. This counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1 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 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C450 - NB_TCH_HO_ATPT_22_TooShortDistance
TCH
....................................................................................................................................................................................................................................

Feature Name --

C45a - NB_OUT_EXT_TCH_REAL_HO_REQ
Descripton

Long Name NB_OUT_EXT_TCH_REAL_HO_REQ

Definition Number of outgoing external TCH (in HR or FR usage) handover requests. This counter takes into account
handovers from 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 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 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 --
Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
11-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C46 - NB_OUT_EXT_TCH_HO_SUCC
TCH
....................................................................................................................................................................................................................................

C46 - NB_OUT_EXT_TCH_HO_SUCC
Descripton

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 does not count hantover to UMTS

Sub Domain 1 TCH


Sub Domain 2 Outgoing External

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 --
Feature Name --

C460 - NB_TCH_HO_ALLOC_EMERGENCY_PRES
Descripton

Long Name NB_TCH_HO_ALLOC_EMERGENCY_PRES


Definition Number of high priority TCH requests served in non VAMOS mode when the number of free 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 conditions are 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 timeslots is less than or equal to NUM_TCH_EGNCY_HO.
3) TCH is not allocated in VAMOS mode
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".

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C460 - NB_TCH_HO_ALLOC_EMERGENCY_PRES
TCH
....................................................................................................................................................................................................................................

Sub Domain 1 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 --
Feature Name Preservation of on going calls

C461 - NB_TCH_HO_ATPT_29_TFO
Descripton

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 Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 29 on TCH.
Sub Domain 1 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 --

Feature Name Support of TFO (Tandem Free Operation)

....................................................................................................................................................................................................................................
11-16 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C47 - NB_OUT_EXT_TCH_HO_EXEC_FAIL_REV
TCH
....................................................................................................................................................................................................................................

C47 - NB_OUT_EXT_TCH_HO_EXEC_FAIL_REV
Descripton

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

Feature Name --

C470 - NB_TCH_HO_ATPT_2_TooLowQualUp
Descripton

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 Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 2. This counter
is incremented in the serving cell,
Note: This counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 TCH


Sub Domain 2 Cause

Sub Domain 3 --

Measured Object Common cell


Type Name TCH handover measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-17
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C470 - NB_TCH_HO_ATPT_2_TooLowQualUp
TCH
....................................................................................................................................................................................................................................

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 --
Feature Name --

C471 - NB_TCH_HO_ATPT_3_TooLowLevUp
Descripton

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 Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 3. This counter
is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1 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 --
Feature Name --

....................................................................................................................................................................................................................................
11-18 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C472 - NB_TCH_HO_ATPT_4_TooLowQualDown
TCH
....................................................................................................................................................................................................................................

C472 - NB_TCH_HO_ATPT_4_TooLowQualDown
Descripton

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 because of cause 4. This
counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1 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 --
Feature Name --

C473 - NB_TCH_HO_ATPT_5_TooLowLevDown
Descripton

Long Name NB_TCH_HO_ATPT_5_TooLowLevDown


Definition Number of inter-cell internal or external handover attempts, with cause 5: "downlink level too low" on a
TCH channel (in HR or FR usage). This 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 BTS because of cause 5. This counter
is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 TCH


Sub Domain 2 Cause

Sub Domain 3 --
Measured Object Common cell

Type Name TCH handover measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-19
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C473 - NB_TCH_HO_ATPT_5_TooLowLevDown
TCH
....................................................................................................................................................................................................................................

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 --
Feature Name --

C474 - NB_TCH_HO_ATPT_6_TooLongDistance
Descripton

Long Name NB_TCH_HO_ATPT_6_TooLongDistance

Definition Number of inter-cell internal or external handover attempts, with cause 6: "MS-BTS distance too long" on a
TCH channel (in HR or FR usage). 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 because of cause 6. This
counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1 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 --
Feature Name --

....................................................................................................................................................................................................................................
11-20 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C476 - NB_TCH_HO_ATPT_15_TooHighLevInterfUp
TCH
....................................................................................................................................................................................................................................

C476 - NB_TCH_HO_ATPT_15_TooHighLevInterfUp
Descripton

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 takes into account handovers from TCH in traffic or in signaling
mode.
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 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 --
Feature Name --

C477 - NB_TCH_HO_ATPT_16_TooHighLevInterfDown
Descripton

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 takes into account handovers from TCH in traffic or in signaling
mode.

Trigger condition Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 16.
Sub Domain 1 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 --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-21
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C478 - NB_TCH_HO_ATPT_12_TooLowPowBudg
TCH
....................................................................................................................................................................................................................................

C478 - NB_TCH_HO_ATPT_12_TooLowPowBudg
Descripton

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 Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTS because of cause 12. This
counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1 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 --
Feature Name --

C479 - NB_TCH_HO_ATPT_21_HighLevNeigCellPrefBand
Descripton

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 Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTS because of cause 21 on TCH.
This counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 TCH


Sub Domain 2 Cause

Sub Domain 3 --

Measured Object Common cell


Type Name TCH handover measurements

....................................................................................................................................................................................................................................
11-22 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C479 - NB_TCH_HO_ATPT_21_HighLevNeigCellPrefBand
TCH
....................................................................................................................................................................................................................................

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 --
Feature Name --

C48 - NB_OUT_EXT_TCH_HO_EXEC_FAIL_NO_REV
Descripton

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 traffic or in signaling mode.
Trigger condition Whenever the timer supervising the handover procedure on the serving cell (T8), expires during an external
TCH handover, except if a 48.008 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 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 --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-23
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C50 - NB_OUT_EXT_TCH_HO_ATPT
TCH
....................................................................................................................................................................................................................................

C50 - NB_OUT_EXT_TCH_HO_ATPT
Descripton

Long Name NB_OUT_EXT_TCH_HO_ATPT

Definition Number of outgoing external TCH (in HR or FR usage) handover attempts. This counter takes into account
handovers from TCH in traffic or in signaling mode.
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 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 --

Feature Name --

C52 - NB_INC_INT_TCH_HO_SUCC
Descripton

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 Whenever a 44.018 HANDOVER COMPLETE message is received on Abis 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 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 --

....................................................................................................................................................................................................................................
11-24 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C52 - NB_INC_INT_TCH_HO_SUCC
TCH
....................................................................................................................................................................................................................................

Feature Name --

C53 - NB_INC_INT_TCH_HO_EXEC_FAIL_MS_ACCESS
Descripton

Long Name NB_INC_INT_TCH_HO_EXEC_FAIL_MS_ACCESS

Definition Number of incoming internal inter-cell TCH (in HR or FR usage) handover -execution failures due to MS
access problem; the mobile either reverts or does not to the old channel.
Trigger condition Whenever the timer supervising the handover procedure (T3103) expires during an internal inter-cell TCH
handover.

Sub Domain 1 TCH


Sub Domain 2 Incoming Internal
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 --
Feature Name --

C541 - NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS
Descripton

Long Name NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS


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

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

Sub Domain 2 Incoming External

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.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-25
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C541 - NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS
TCH
....................................................................................................................................................................................................................................

External Comment --

Feature Name Enhanced Transmission Resource management

C541a - NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS
Descripton

Long Name NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS

Definition Number of incoming external TCH (in HR or FR usage) handover -preparation 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, 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 TCH
Sub Domain 2 Incoming External
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 --
Feature Name --

....................................................................................................................................................................................................................................
11-26 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C551 - NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS
TCH
....................................................................................................................................................................................................................................

C551 - NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS
Descripton

Long Name NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS

Definition Number of incoming internal inter-cell TCH (in HR or FR usage) handover -preparation failures due to
congestion.
Trigger condition Whenever an internal inter-cell TCH handover cannot be performed, 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 NB_MAX_ACTIVE_
TCH_TS parameter

Sub Domain 1 TCH


Sub Domain 2 Incoming Internal

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 --
Feature Name --

C55a - NB_OUT_INT_TCH_HO_REQ
Descripton

Long Name NB_OUT_INT_TCH_HO_REQ

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

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

Sub Domain 1 TCH

Sub Domain 2 Outgoing Internal


Sub Domain 3 --
Measured Object Common cell

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-27
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C55a - NB_OUT_INT_TCH_HO_REQ
TCH
....................................................................................................................................................................................................................................

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

Feature Name --

C56 - NB_OUT_INT_TCH_HO_SUCC
Descripton

Long Name NB_OUT_INT_TCH_HO_SUCC


Definition Number of outgoing internal inter-cell TCH (in HR or FR usage) handover successes. This counter takes
into account handovers from TCH in traffic or in signaling mode.
Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abis interface from the target cell ,
during an internal inter-cell TCH handover. Whenever an handover execution procedure (HANDOVER
COMMAND being sent) is interrupted due to normal call release by the user. In this case the handover is
considered as successful.
Sub Domain 1 TCH
Sub Domain 2 Outgoing Internal
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 --
Feature Name --

....................................................................................................................................................................................................................................
11-28 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C561 - NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS
TCH
....................................................................................................................................................................................................................................

C561 - NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS
Descripton

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 in non
VAMOS mode. 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 in non VAMOS mode cannot be performed, because there is
no free TCH channel to serve the handover (In VAMOS mode when no pairing target candidate is found,
this counter is not incremented)
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 processing capacity of AbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_
TCH_TS parameter

Sub Domain 1 TCH


Sub Domain 2 Intra

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 --
Feature Name Enhanced Transmission Resource management

C57 - NB_OUT_INT_TCH_HO_EXEC_FAIL_REV
Descripton

Long Name NB_OUT_INT_TCH_HO_EXEC_FAIL_REV


Definition Number of outgoing internal inter-cell TCH (in HR or FR usage) handover -execution failures due to MS
access problem with reversion of the mobile 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 internal inter-cell TCH handover.

Sub Domain 1 TCH


Sub Domain 2 Outgoing Internal

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-29
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C57 - NB_OUT_INT_TCH_HO_EXEC_FAIL_REV
TCH
....................................................................................................................................................................................................................................

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

Feature Name --

C58 - NB_OUT_INT_TCH_HO_EXEC_FAIL_NO_REV
Descripton

Long Name NB_OUT_INT_TCH_HO_EXEC_FAIL_NO_REV


Definition Number of outgoing internal inter-cell TCH (in HR or FR usage) handover -execution failures due to MS
access problem without reversion of the mobile to the old channel (call drop). This counter takes into
account handovers from TCH in traffic or in signaling mode.
Trigger condition Whenever the timer supervising the handover procedure (T3103) expires 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 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 --

Feature Name --

....................................................................................................................................................................................................................................
11-30 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C585a - NB_TCH_HO_ATPT_7_ConsBadSACCHmicroCell
TCH
....................................................................................................................................................................................................................................

C585a - NB_TCH_HO_ATPT_7_ConsBadSACCHmicroCell
Descripton

Long Name NB_TCH_HO_ATPT_7_ConsBadSACCHmicroCell

Definition Number of inter-cell internal or external handover attempts, with cause 7: "several consecutive bad SACCH
frames received in a micro cell" on a 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 Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 7. This counter
is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1 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 --
Feature Name --

C585d - NB_TCH_HO_ATPT_17_TooLowLevUpMicroCell
Descripton

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 from TCH in traffic or in signaling mode.
This counter is related to micro cell environment.

Trigger condition Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTS because of cause 17. This
counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1 TCH

Sub Domain 2 Cause


Sub Domain 3 --

Measured Object Common cell

Type Name TCH handover measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-31
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C585d - NB_TCH_HO_ATPT_17_TooLowLevUpMicroCell
TCH
....................................................................................................................................................................................................................................

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 --
Feature Name --

C585e - NB_TCH_HO_ATPT_18_TooLowLevDownMicroCell
Descripton

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 from TCH in traffic or in signaling mode.
This counter is related to micro cell environment.
Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 18. This
counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 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 --

Feature Name --

....................................................................................................................................................................................................................................
11-32 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C585f - NB_TCH_HO_ATPT_14_HighLevNeigLowCellSlowMS
TCH
....................................................................................................................................................................................................................................

C585f - NB_TCH_HO_ATPT_14_HighLevNeigLowCellSlowMS
Descripton

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 Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 14. This
counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1 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 --
Feature Name --

C586a - NB_TCH_HO_ATPT_10_TooLowLevUpInZone
Descripton

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 Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 10.
Sub Domain 1 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 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-33
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C586a - NB_TCH_HO_ATPT_10_TooLowLevUpInZone
TCH
....................................................................................................................................................................................................................................

Feature Name --

C586b - NB_TCH_HO_ATPT_11_TooLowLevDownInZone
Descripton

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 concentric cell environment.
Trigger condition Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 11.

Sub Domain 1 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 --
Feature Name --

C586c - NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone
Descripton

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 Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 13.

Sub Domain 1 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.

....................................................................................................................................................................................................................................
11-34 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C586c - NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone
TCH
....................................................................................................................................................................................................................................

External Comment --

Feature Name --

C60 - NB_OUT_INT_TCH_HO_ATPT
Descripton

Long Name NB_OUT_INT_TCH_HO_ATPT

Definition Number of outgoing internal inter-cell TCH (in HR or FR usage) handover attempts. This counter takes into
account handovers from TCH in traffic or in signaling mode.
Trigger condition Whenever the 44.018 HANDOVER COMMAND message is sent on Abis 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 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 --
Feature Name --

C62 - NB_INTRA_TCH_HO_SUCC
Descripton

Long Name NB_INTRA_TCH_HO_SUCC

Definition Number of intra-cell TCH (in HR or FR usage) handover successes. 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 44.018 ASSIGNMENT COMPLETE message is received on Abis 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 TCH handover measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-35
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C62 - NB_INTRA_TCH_HO_SUCC
TCH
....................................................................................................................................................................................................................................

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 --
Feature Name --

C63 - NB_INTRA_TCH_HO_EXEC_FAIL_NO_REV
Descripton

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 handovers from TCH in traffic or in signaling mode. It does
not take into account DTM Assignments.
Trigger condition Whenever the timer supervising the handover procedure (T3107) expires during an internal intra-cell.

Sub Domain 1 TCH


Sub Domain 2 Intra
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 --
Feature Name --

C67 - NB_INTRA_TCH_HO_EXEC_FAIL_REV
Descripton

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

....................................................................................................................................................................................................................................
11-36 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C67 - NB_INTRA_TCH_HO_EXEC_FAIL_REV
TCH
....................................................................................................................................................................................................................................

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

Feature Name --

C75 - NB_TCH_HO_MSC_TRIG
Descripton

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

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 11-37
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C75 - NB_TCH_HO_MSC_TRIG

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
11-38 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
12 Traffic Load
12

Telecom Procedure (Traffic Load)

Overview
Purpose
This section contains Telecom Procedure (Traffic Load) parameters.

Contents

C413 - NB_TCH_NOR_ASS_INNER_ZONE_ALLOC 12-1

C413 - NB_TCH_NOR_ASS_INNER_ZONE_ALLOC
Descripton

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 Telecom Procedure (Traffic Load)

Sub Domain 2 Normal Assignment


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.

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 12-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C413 - NB_TCH_NOR_ASS_INNER_ZONE_ALLOC
Telecom Procedure (Traffic Load)
....................................................................................................................................................................................................................................

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
12-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C413 - NB_TCH_NOR_ASS_INNER_ZONE_ALLOC

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 12-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C413 - NB_TCH_NOR_ASS_INNER_ZONE_ALLOC

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
12-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part VII: BSC-TYPE 7 - LapD
measurements

Overview
Purpose
All type 7.

Contents

Chapter 13, Quality of Service 13-1


Chapter 14, Resource Availability & Usage 14-1
Chapter 15, Traffic Load 15-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R VII-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 7 - LapD measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
VII-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
13 Quality of Service
13

Interface (QoS)

Overview
Purpose
This section contains Interface (QoS) parameters.

Contents

L1.12 - NB_LAPD_CRC_ERROR 13-2


L1.15 - NB_LAPD_INFO_FRAME_RESENT 13-2
L1.17 - NB_LAPD_EST 13-3
L1.18 - TIME_LAPD_CONG 13-3
L1.5 - NB_LAPD_RNR_SENT 13-4
L1.6 - NB_LAPD_RNR_REC 13-4
L2.1 - NB_GSL_LAPD_ESTAB 13-5
L2.2 - NB_GSL_LAPD_CRC_ERROR 13-5
L2.3 - NB_GSL_LAPD_INFO_FRAME_RESENT 13-6
L2.4 - NB_GSL_LAPD_RNR_SENT 13-6
L2.5 - NB_GSL_LAPD_RNR_REC 13-7
L2.6 - TIME_GSL_LAPD_UNAVAIL 13-7
L2.7 - TIME_GSL_LAPD_CONG 13-8

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 13-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service L1.12 - NB_LAPD_CRC_ERROR
Interface (QoS)
....................................................................................................................................................................................................................................

L1.12 - NB_LAPD_CRC_ERROR
Descripton

Long Name NB_LAPD_CRC_ERROR

Definition Number of frames received with CRC error on the RSL LapD link.
Trigger condition Whenever the HDLC Formatter handling the Physical RSL LAPD link detects a CRC error in a received
Frame.
Note 1: In case of LapD over UDP for IP transport in the BSS, this counter is meaningless and shall always
be set to 0.
Sub Domain 1 Interface (QoS)

Sub Domain 2 Abis (QoS)


Sub Domain 3 LapD

Measured Object LapD


Type Name LapD measurements
Type Definition Set of counters related to the LapD logical links
External Comment --
Feature Name --

L1.15 - NB_LAPD_INFO_FRAME_RESENT
Descripton

Long Name NB_LAPD_INFO_FRAME_RESENT


Definition Number of Information frames re-transmitted on the RSL LapD link.
Trigger condition Whenever an Information Frame is retransmitted on a logical RSL LAPD link.
Sub Domain 1 Interface (QoS)

Sub Domain 2 Abis (QoS)


Sub Domain 3 LapD

Measured Object LapD

Type Name LapD measurements


Type Definition Set of counters related to the LapD logical links
External Comment --

Feature Name --

....................................................................................................................................................................................................................................
13-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service L1.17 - NB_LAPD_EST
Interface (QoS)
....................................................................................................................................................................................................................................

L1.17 - NB_LAPD_EST
Descripton

Long Name NB_LAPD_EST

Definition Number of data link establishment, re-establishment and reset on the RSL 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).
This applies to RSL LapD link.

Sub Domain 1 Interface (QoS)


Sub Domain 2 Abis (QoS)

Sub Domain 3 LapD


Measured Object LapD

Type Name LapD measurements


Type Definition Set of counters related to the LapD logical links

External Comment --
Feature Name --

L1.18 - TIME_LAPD_CONG
Descripton

Long Name TIME_LAPD_CONG


Definition Time in seconds during which the RSL 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
for a RSL LapD link.

Sub Domain 1 Interface (QoS)

Sub Domain 2 Abis (QoS)


Sub Domain 3 LapD
Measured Object LapD

Type Name LapD measurements

Type Definition Set of counters related to the LapD logical links


External Comment --

Feature Name B8 BSC counters improvements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 13-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service L1.5 - NB_LAPD_RNR_SENT
Interface (QoS)
....................................................................................................................................................................................................................................

L1.5 - NB_LAPD_RNR_SENT
Descripton

Long Name NB_LAPD_RNR_SENT

Definition Number of Receive Not Ready (RNR) frames transmitted on the RSL LapD link.
Trigger condition Whenever an RNR Frame is transmitted on a logical RSL LAPD link.

Sub Domain 1 Interface (QoS)


Sub Domain 2 Abis (QoS)

Sub Domain 3 LapD


Measured Object LapD

Type Name LapD measurements


Type Definition Set of counters related to the LapD logical links
External Comment --
Feature Name --

L1.6 - NB_LAPD_RNR_REC
Descripton

Long Name NB_LAPD_RNR_REC


Definition Number of Receive Not Ready (RNR) frames received on the RSL LapD link.
Trigger condition Whenever an RNR Frame is received on a logical RSL LAPD link.
Sub Domain 1 Interface (QoS)
Sub Domain 2 Abis (QoS)

Sub Domain 3 LapD

Measured Object LapD


Type Name LapD measurements
Type Definition Set of counters related to the LapD logical links

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
13-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service L2.1 - NB_GSL_LAPD_ESTAB
Interface (QoS)
....................................................................................................................................................................................................................................

L2.1 - NB_GSL_LAPD_ESTAB
Descripton

Long Name NB_GSL_LAPD_ESTAB

Definition Number of data link establishment, re-establishment and reset on the GSL 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 MFS).
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).
This applies to GSL LapD link.

Sub Domain 1 Interface (QoS)


Sub Domain 2 GSL link (QoS)

Sub Domain 3 --
Measured Object GSL LAPD

Type Name LapD measurements


Type Definition Set of counters related to the LapD logical links

External Comment --
Feature Name New GSL counters

L2.2 - NB_GSL_LAPD_CRC_ERROR
Descripton

Long Name NB_GSL_LAPD_CRC_ERROR


Definition Number of frames received with CRC error on the GSL LapD link.
Trigger condition Whenever the HDLC Formatter handling the Physical GSL LAPD link detects a CRC error in a received
Frame.

Sub Domain 1 Interface (QoS)


Sub Domain 2 GSL link (QoS)

Sub Domain 3 --

Measured Object GSL LAPD


Type Name LapD measurements
Type Definition Set of counters related to the LapD logical links

External Comment --

Feature Name New GSL counters

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 13-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service L2.3 - NB_GSL_LAPD_INFO_FRAME_RESENT
Interface (QoS)
....................................................................................................................................................................................................................................

L2.3 - NB_GSL_LAPD_INFO_FRAME_RESENT
Descripton

Long Name NB_GSL_LAPD_INFO_FRAME_RESENT

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


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

Sub Domain 1 Interface (QoS)


Sub Domain 2 GSL link (QoS)

Sub Domain 3 --
Measured Object GSL LAPD

Type Name LapD measurements


Type Definition Set of counters related to the LapD logical links
External Comment --
Feature Name New GSL counters

L2.4 - NB_GSL_LAPD_RNR_SENT
Descripton

Long Name NB_GSL_LAPD_RNR_SENT


Definition Number of Receive Not Ready (RNR) frames transmitted on the GSL LapD link.
Trigger condition Whenever a Receiver Not Ready (RNR) Frame is transmitted on a logical GSL LAPD link.
Sub Domain 1 Interface (QoS)
Sub Domain 2 GSL link (QoS)

Sub Domain 3 --

Measured Object GSL LAPD


Type Name LapD measurements
Type Definition Set of counters related to the LapD logical links

External Comment --

Feature Name New GSL counters

....................................................................................................................................................................................................................................
13-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service L2.5 - NB_GSL_LAPD_RNR_REC
Interface (QoS)
....................................................................................................................................................................................................................................

L2.5 - NB_GSL_LAPD_RNR_REC
Descripton

Long Name NB_GSL_LAPD_RNR_REC

Definition Number of Receive Not Ready (RNR) frames received on the GSL LapD link.
Trigger condition Whenever a Receiver Not Ready (RNR) Frame is received on a logical GSL LAPD link.

Sub Domain 1 Interface (QoS)


Sub Domain 2 GSL link (QoS)

Sub Domain 3 --
Measured Object GSL LAPD

Type Name LapD measurements


Type Definition Set of counters related to the LapD logical links
External Comment --
Feature Name New GSL counters

L2.6 - TIME_GSL_LAPD_UNAVAIL
Descripton

Long Name TIME_GSL_LAPD_UNAVAIL


Definition Time (in seconds) during which the GSL 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 GSL
LAPD link) and reception of the DL-ESTABLISH-CONFIRM primitive for that logical GSL 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 GSL LAPD link.
Sub Domain 1 Interface (QoS)

Sub Domain 2 GSL link (QoS)

Sub Domain 3 --
Measured Object GSL LAPD

Type Name LapD measurements


Type Definition Set of counters related to the LapD logical links

External Comment --
Feature Name New GSL counters

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 13-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service L2.7 - TIME_GSL_LAPD_CONG
Interface (QoS)
....................................................................................................................................................................................................................................

L2.7 - TIME_GSL_LAPD_CONG
Descripton

Long Name TIME_GSL_LAPD_CONG

Definition Time in seconds during which the GSL 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
for a GSL LapD link.

Sub Domain 1 Interface (QoS)


Sub Domain 2 GSL link (QoS)

Sub Domain 3 --

Measured Object GSL LAPD


Type Name LapD measurements

Type Definition Set of counters related to the LapD logical links


External Comment --

Feature Name New GSL counters

....................................................................................................................................................................................................................................
13-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
14 14
Resource Availability &
Usage

Interface (Resource Availability)

Overview
Purpose
This section contains Interface (Resource Availability) parameters.

Contents

L1.16 - TIME_LAPD_UNAVAIL 14-1

L1.16 - TIME_LAPD_UNAVAIL
Descripton

Long Name TIME_LAPD_UNAVAIL


Definition Time (in seconds) during which the RSL 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 RSL
LAPD link) and reception of the DL-ESTABLISH-CONFIRM primitive for that logical RSL 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 RSL LAPD link.
Sub Domain 1 Interface (Resource Availability)
Sub Domain 2 Abis (Resource Availability)

Sub Domain 3 Availability

Measured Object LapD


Type Name LapD measurements

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 14-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage L1.16 - TIME_LAPD_UNAVAIL
Interface (Resource Availability)
....................................................................................................................................................................................................................................

Type Definition Set of counters related to the LapD logical links

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
14-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
15 Traffic Load
15

Interface (Traffic Load)

Overview
Purpose
This section contains Interface (Traffic Load) parameters.

Contents

L1.1 - NB_LAPD_INFO_FRAME_SENT 15-1


L1.2 - NB_LAPD_INFO_FRAME_REC 15-2

L1.1 - NB_LAPD_INFO_FRAME_SENT
Descripton

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 (Traffic Load)

Sub Domain 2 Abis (Traffic Load)

Sub Domain 3 LapD


Measured Object LapD
Type Name LapD measurements

Type Definition Set of counters related to the LapD logical links

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 15-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load L1.1 - NB_LAPD_INFO_FRAME_SENT
Interface (Traffic Load)
....................................................................................................................................................................................................................................

External Comment --

Feature Name --

L1.2 - NB_LAPD_INFO_FRAME_REC
Descripton

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 (Traffic Load)


Sub Domain 2 Abis (Traffic Load)

Sub Domain 3 LapD


Measured Object LapD
Type Name LapD measurements
Type Definition Set of counters related to the LapD logical links
External Comment --
Feature Name --

....................................................................................................................................................................................................................................
15-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load L1.2 - NB_LAPD_INFO_FRAME_REC

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 15-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load L1.2 - NB_LAPD_INFO_FRAME_REC

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
15-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part VIII: BSC-TYPE 8 - X25
measurements

Overview
Purpose
All type 8.

Contents

Chapter 16, Quality of Service 16-1


Chapter 17, Traffic Load 17-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R VIII-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 8 - X25 measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
VIII-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
16 Quality of Service
16

Interface (QoS)

Overview
Purpose
This section contains Interface (QoS) parameters.

Contents

X3.22 - NB_X25_INC_CALL_ABNORM_CLOSED 16-1


X3.23 - NB_X25_OUT_CALL_ABNORM_CLOSED 16-2

X3.22 - NB_X25_INC_CALL_ABNORM_CLOSED
Descripton

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 (QoS)

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

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 16-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service X3.22 - NB_X25_INC_CALL_ABNORM_CLOSED
Interface (QoS)
....................................................................................................................................................................................................................................

Feature Name --

X3.23 - NB_X25_OUT_CALL_ABNORM_CLOSED
Descripton

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 (QoS)


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 --
Feature Name --

....................................................................................................................................................................................................................................
16-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
17 Traffic Load
17

Interface (Traffic Load)

Overview
Purpose
This section contains Interface (Traffic Load) parameters.

Contents

X3.20 - NB_X25_INC_CALL_SUCC_CLOSED 17-1


X3.21 - NB_X25_OUT_CALL_SUCC_CLOSED 17-2

X3.20 - NB_X25_INC_CALL_SUCC_CLOSED
Descripton

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 (Traffic Load)

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

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 17-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load X3.20 - NB_X25_INC_CALL_SUCC_CLOSED
Interface (Traffic Load)
....................................................................................................................................................................................................................................

Feature Name --

X3.21 - NB_X25_OUT_CALL_SUCC_CLOSED
Descripton

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 (Traffic Load)


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 --
Feature Name --

....................................................................................................................................................................................................................................
17-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load X3.21 - NB_X25_OUT_CALL_SUCC_CLOSED

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 17-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load X3.21 - NB_X25_OUT_CALL_SUCC_CLOSED

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
17-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part IX: BSC-TYPE 9 - N7
measurements

Overview
Purpose
All type 9.

Contents

Chapter 18, Quality of Service 18-1


Chapter 19, Resource Availability & Usage 19-1
Chapter 20, Traffic Load 20-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R IX-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 9 - N7 measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
IX-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
18 Quality of Service
18

Interface (QoS)

Overview
Purpose
This section contains Interface (QoS) parameters.

Contents

N1.10 - NB_N7_CHANGEOVER 18-2


N1.11 - NB_N7_CHANGEBACK 18-2
N1.12 - NB_N7_RESTORATION 18-3
N1.2 - NB_N7_LINK_FAIL_ANY_CAUSE 18-3
N1.3 - NB_N7_LINK_FAIL_FIB_BSN 18-4
N1.4 - NB_N7_LINK_FAIL_T7_EXP 18-4
N1.5 - NB_N7_LINK_FAIL_SU_ERROR_RATE 18-5
N1.6 - NB_N7_LINK_FAIL_CONG 18-5
N1.7 - NB_N7_LINK_FAIL_ALIGNMENT 18-6
N1.8 - NB_N7_SU_REC_WITH_ERROR 18-6
N1.9 - NB_N7_NEG_ACK_REC 18-7
N3.10 - NB_N7_MSU_DISC_DUE_CONG 18-7
N3.11 - NB_N7_CONG_WITH_MSU_LOST 18-8

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 18-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service N1.10 - NB_N7_CHANGEOVER
Interface (QoS)
....................................................................................................................................................................................................................................

N1.10 - NB_N7_CHANGEOVER
Descripton

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 (QoS)


Sub Domain 2 A

Sub Domain 3 Layers1-2-3


Measured Object N7 Signalling Link

Type Name N7 measurements


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

Feature Name --

N1.11 - NB_N7_CHANGEBACK
Descripton

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 (QoS)

Sub Domain 2 A
Sub Domain 3 Layers1-2-3

Measured Object N7 Signalling Link


Type Name N7 measurements

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

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
18-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service N1.12 - NB_N7_RESTORATION
Interface (QoS)
....................................................................................................................................................................................................................................

N1.12 - NB_N7_RESTORATION
Descripton

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 (QoS)


Sub Domain 2 A

Sub Domain 3 Layers1-2-3


Measured Object N7 Signalling Link

Type Name N7 measurements


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

Feature Name --

N1.2 - NB_N7_LINK_FAIL_ANY_CAUSE
Descripton

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 (QoS)


Sub Domain 2 A

Sub Domain 3 Layers1-2-3


Measured Object N7 Signalling Link

Type Name N7 measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 18-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service N1.2 - NB_N7_LINK_FAIL_ANY_CAUSE
Interface (QoS)
....................................................................................................................................................................................................................................

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 --
Feature Name --

N1.3 - NB_N7_LINK_FAIL_FIB_BSN
Descripton

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 (QoS)
Sub Domain 2 A
Sub Domain 3 Layers1-2-3
Measured Object N7 Signalling Link
Type Name N7 measurements
Type Definition Set of counters related to the N7 Signalling Links. Note that in the BSS context, the Link Set and the Route
Set are identical.

External Comment --
Feature Name --

N1.4 - NB_N7_LINK_FAIL_T7_EXP
Descripton

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 (QoS)

Sub Domain 2 A
Sub Domain 3 Layers1-2-3

Measured Object N7 Signalling Link

....................................................................................................................................................................................................................................
18-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service N1.4 - NB_N7_LINK_FAIL_T7_EXP
Interface (QoS)
....................................................................................................................................................................................................................................

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

Feature Name --

N1.5 - NB_N7_LINK_FAIL_SU_ERROR_RATE
Descripton

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 (QoS)
Sub Domain 2 A

Sub Domain 3 Layers1-2-3


Measured Object N7 Signalling Link
Type Name N7 measurements
Type Definition Set of counters related to the N7 Signalling Links. Note that in the BSS context, the Link Set and the Route
Set are identical.
External Comment --

Feature Name --

N1.6 - NB_N7_LINK_FAIL_CONG
Descripton

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 (QoS)
Sub Domain 2 A

Sub Domain 3 Layers1-2-3

Measured Object N7 Signalling Link


Type Name N7 measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 18-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service N1.6 - NB_N7_LINK_FAIL_CONG
Interface (QoS)
....................................................................................................................................................................................................................................

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 --
Feature Name --

N1.7 - NB_N7_LINK_FAIL_ALIGNMENT
Descripton

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 (QoS)
Sub Domain 2 A

Sub Domain 3 Layers1-2-3


Measured Object N7 Signalling Link
Type Name N7 measurements
Type Definition Set of counters related to the N7 Signalling Links. Note that in the BSS context, the Link Set and the Route
Set are identical.
External Comment --

Feature Name --

N1.8 - NB_N7_SU_REC_WITH_ERROR
Descripton

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 (QoS)


Sub Domain 2 A

Sub Domain 3 Layers1-2-3


Measured Object N7 Signalling Link

Type Name N7 measurements

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

....................................................................................................................................................................................................................................
18-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service N1.8 - NB_N7_SU_REC_WITH_ERROR
Interface (QoS)
....................................................................................................................................................................................................................................

External Comment --

Feature Name --

N1.9 - NB_N7_NEG_ACK_REC
Descripton

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 (QoS)


Sub Domain 2 A

Sub Domain 3 Layers1-2-3


Measured Object N7 Signalling Link
Type Name N7 measurements
Type Definition Set of counters related to the N7 Signalling Links. Note that in the BSS context, the Link Set and the Route
Set are identical.
External Comment --

Feature Name --

N3.10 - NB_N7_MSU_DISC_DUE_CONG
Descripton

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 (QoS)

Sub Domain 2 A
Sub Domain 3 Layers1-2-3
Measured Object N7 Signalling Link

Type Name N7 measurements

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 18-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service N3.10 - NB_N7_MSU_DISC_DUE_CONG
Interface (QoS)
....................................................................................................................................................................................................................................

Feature Name --

N3.11 - NB_N7_CONG_WITH_MSU_LOST
Descripton

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 MSU's are lost due to congestion on the signalling link.

Sub Domain 1 Interface (QoS)


Sub Domain 2 A

Sub Domain 3 Layers1-2-3


Measured Object N7 Signalling Link
Type Name N7 measurements
Type Definition Set of counters related to the N7 Signalling Links. Note that in the BSS context, the Link Set and the Route
Set are identical.
External Comment --

Feature Name --

....................................................................................................................................................................................................................................
18-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
19 19
Resource Availability &
Usage

Interface (Resource Availability)

Overview
Purpose
This section contains Interface (Resource Availability) parameters.

Contents

N1.1 - TIME_N7_ALIGNED 19-1


N2.7 - TIME_N7_UNAVAIL_ERROR_SL 19-2
N2.9 - TIME_N7_UNAVAIL_MSC_PROC_OUTAGE 19-2
N3.7 - TIME_N7_UNAVAIL_CONG 19-3
N4.2 - TIME_N7_UNAVAIL_LINK_SET 19-3

N1.1 - TIME_N7_ALIGNED
Descripton

Long Name TIME_N7_ALIGNED


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

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

Sub Domain 1 Interface (Resource Availability)


Sub Domain 2 A

Sub Domain 3 Availability

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 19-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage N1.1 - TIME_N7_ALIGNED
Interface (Resource Availability)
....................................................................................................................................................................................................................................

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 --
Feature Name --

N2.7 - TIME_N7_UNAVAIL_ERROR_SL
Descripton

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 (Resource Availability)


Sub Domain 2 A
Sub Domain 3 Availability
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 --

Feature Name --

N2.9 - TIME_N7_UNAVAIL_MSC_PROC_OUTAGE
Descripton

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 (Resource Availability)

Sub Domain 2 A
Sub Domain 3 Availability

....................................................................................................................................................................................................................................
19-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage N2.9 - TIME_N7_UNAVAIL_MSC_PROC_OUTAGE
Interface (Resource Availability)
....................................................................................................................................................................................................................................

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 --
Feature Name --

N3.7 - TIME_N7_UNAVAIL_CONG
Descripton

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 (Resource Availability)
Sub Domain 2 A

Sub Domain 3 Availability


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

Feature Name --

N4.2 - TIME_N7_UNAVAIL_LINK_SET
Descripton

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 (i.e all the links of the set), this counter will be
updated every second.
Sub Domain 1 Interface (Resource Availability)

Sub Domain 2 A

Sub Domain 3 Availability


Measured Object N7 Link Set

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 19-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage N4.2 - TIME_N7_UNAVAIL_LINK_SET
Interface (Resource Availability)
....................................................................................................................................................................................................................................

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

Feature Name --

....................................................................................................................................................................................................................................
19-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
20 Traffic Load
20

Interface (Traffic Load)

Overview
Purpose
This section contains Interface (Traffic Load) parameters.

Contents

N3.1 - NB_N7_SIF_SIO_SENT 20-1


N3.2 - NB_N7_OCTETS_RESENT 20-2
N3.3 - NB_N7_MSU_SENT 20-2
N3.4 - NB_N7_SIF_SIO_REC 20-3
N3.5 - NB_N7_MSU_REC 20-3

N3.1 - NB_N7_SIF_SIO_SENT
Descripton

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 (Traffic Load)


Sub Domain 2 A

Sub Domain 3 Layers1-2-3

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 20-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load N3.1 - NB_N7_SIF_SIO_SENT
Interface (Traffic Load)
....................................................................................................................................................................................................................................

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 --
Feature Name --

N3.2 - NB_N7_OCTETS_RESENT
Descripton

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 (Traffic Load)
Sub Domain 2 A

Sub Domain 3 Layers1-2-3


Measured Object N7 Signalling Link
Type Name N7 measurements
Type Definition Set of counters related to the N7 Signalling Links. Note that in the BSS context, the Link Set and the Route
Set are identical.
External Comment --

Feature Name --

N3.3 - NB_N7_MSU_SENT
Descripton

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 (Traffic Load)


Sub Domain 2 A
Sub Domain 3 Layers1-2-3

Measured Object N7 Signalling Link

Type Name N7 measurements

....................................................................................................................................................................................................................................
20-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load N3.3 - NB_N7_MSU_SENT
Interface (Traffic Load)
....................................................................................................................................................................................................................................

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 --
Feature Name --

N3.4 - NB_N7_SIF_SIO_REC
Descripton

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 (Traffic Load)
Sub Domain 2 A
Sub Domain 3 Layers1-2-3

Measured Object N7 Signalling Link


Type Name N7 measurements

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

N3.5 - NB_N7_MSU_REC
Descripton

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 (Traffic Load)

Sub Domain 2 A
Sub Domain 3 Layers1-2-3

Measured Object N7 Signalling Link


Type Name N7 measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 20-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load N3.5 - NB_N7_MSU_REC
Interface (Traffic Load)
....................................................................................................................................................................................................................................

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 --
Feature Name --

....................................................................................................................................................................................................................................
20-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load N3.5 - NB_N7_MSU_REC

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 20-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load N3.5 - NB_N7_MSU_REC

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
20-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part X: BSC-TYPE 18 - A
interface measurements

Overview
Purpose
All type 18.

Contents

Chapter 21, Quality of Service 21-1


Chapter 22, Traffic Load 22-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R X-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 18 - A interface measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
X-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
21 Quality of Service
21

Interface (QoS)

Overview
Purpose
This section contains Interface (QoS) parameters.

Contents

C180a - NB_N7_CLEAR_REQ_RadioIntMessFail 21-2


C180b - NB_N7_CLEAR_REQ_O&Minterv 21-2
C180c - NB_N7_CLEAR_REQ_EquipFail 21-3
C180d - NB_N7_CLEAR_REQ_RadioIntFail 21-3
C180e - NB_N7_CLEAR_REQ_NoRadioResAvail 21-4
C181a - NB_N7_ASS_FAIL_RadioIntMessFail 21-4
C181b - NB_N7_ASS_FAIL_O&Minterv 21-5
C181c - NB_N7_ASS_FAIL_EquipFail 21-5
C181d - NB_N7_ASS_FAIL_NoRadioResAvail 21-6
C181e - NB_N7_ASS_FAIL_ReqTerResUnav/Alloc 21-6
C181f - NB_N7_ASS_FAIL_ReqTrans/RateUnav 21-7
C181g - NB_N7_ASS_FAIL_RadioIntFailRevOldChan 21-8
C181h - NB_N7_ASS_FAIL_RadioIntFail 21-8
C181i - NB_N7_ASS_FAIL_CipherAlgoNotSupp 21-9
C181j - NB_N7_ASS_FAIL_BSSnotEquip 21-9
C181k - NB_N7_ASS_FAIL_ProtocolError 21-10

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 21-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Interface (QoS)
....................................................................................................................................................................................................................................

C181l - NB_N7_ASS_FAIL_ReqSpeechVersUnav 21-10


C181m - NB_N7_ASS_FAIL_ReqAintNotSupp/Unav 21-11
C181n - NB_N7_ASS_FAIL_ReqCodecNotSupp/Unav 21-11
C181p - NB_N7_ASS_FAIL_call_ident_alloc 21-12
C182 - NB_N7_CLEAR_REQ_EST_PHAS 21-12

C180a - NB_N7_CLEAR_REQ_RadioIntMessFail
Descripton

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 (QoS)


Sub Domain 2 A
Sub Domain 3 BSSAP
Measured Object BSC
Type Name A interface measurements
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and 08.08ASSIGNMENT
FAILURE
External Comment --

Feature Name --

C180b - NB_N7_CLEAR_REQ_O&Minterv
Descripton

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 (QoS)
Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC

....................................................................................................................................................................................................................................
21-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C180b - NB_N7_CLEAR_REQ_O&Minterv
Interface (QoS)
....................................................................................................................................................................................................................................

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

Feature Name --

C180c - NB_N7_CLEAR_REQ_EquipFail
Descripton

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 (QoS)


Sub Domain 2 A
Sub Domain 3 BSSAP
Measured Object BSC
Type Name A interface measurements
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and 08.08ASSIGNMENT
FAILURE
External Comment --

Feature Name --

C180d - NB_N7_CLEAR_REQ_RadioIntFail
Descripton

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 (QoS)

Sub Domain 2 A

Sub Domain 3 BSSAP


Measured Object BSC

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 21-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C180d - NB_N7_CLEAR_REQ_RadioIntFail
Interface (QoS)
....................................................................................................................................................................................................................................

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

Feature Name --

C180e - NB_N7_CLEAR_REQ_NoRadioResAvail
Descripton

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 (QoS)


Sub Domain 2 A
Sub Domain 3 BSSAP
Measured Object BSC
Type Name A interface measurements
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and 08.08ASSIGNMENT
FAILURE
External Comment --

Feature Name --

C181a - NB_N7_ASS_FAIL_RadioIntMessFail
Descripton

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 (QoS)

Sub Domain 2 A

Sub Domain 3 BSSAP


Measured Object BSC

....................................................................................................................................................................................................................................
21-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C181a - NB_N7_ASS_FAIL_RadioIntMessFail
Interface (QoS)
....................................................................................................................................................................................................................................

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

Feature Name --

C181b - NB_N7_ASS_FAIL_O&Minterv
Descripton

Long Name NB_N7_ASS_FAIL_O&Minterv

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


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

Sub Domain 1 Interface (QoS)


Sub Domain 2 A
Sub Domain 3 BSSAP
Measured Object BSC
Type Name A interface measurements
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and 08.08ASSIGNMENT
FAILURE
External Comment --

Feature Name --

C181c - NB_N7_ASS_FAIL_EquipFail
Descripton

Long Name NB_N7_ASS_FAIL_EquipFail


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

Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "equipment failure" is sent on
A interface to the MSC.
Sub Domain 1 Interface (QoS)

Sub Domain 2 A

Sub Domain 3 BSSAP


Measured Object BSC

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 21-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C181c - NB_N7_ASS_FAIL_EquipFail
Interface (QoS)
....................................................................................................................................................................................................................................

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

Feature Name --

C181d - NB_N7_ASS_FAIL_NoRadioResAvail
Descripton

Long Name NB_N7_ASS_FAIL_NoRadioResAvail

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

Sub Domain 1 Interface (QoS)


Sub Domain 2 A
Sub Domain 3 BSSAP
Measured Object BSC
Type Name A interface measurements
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and 08.08ASSIGNMENT
FAILURE
External Comment --

Feature Name --

C181e - NB_N7_ASS_FAIL_ReqTerResUnav/Alloc
Descripton

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) Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "terrestrial resource already
allocated" is sent on A interface to the MSC.

Sub Domain 1 Interface (QoS)

Sub Domain 2 A

....................................................................................................................................................................................................................................
21-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C181e - NB_N7_ASS_FAIL_ReqTerResUnav/Alloc
Interface (QoS)
....................................................................................................................................................................................................................................

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

Feature Name --

C181f - NB_N7_ASS_FAIL_ReqTrans/RateUnav
Descripton

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 Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "requested transcoding/rate
adaptation unavailable" is sent on A interface to the MSC.
Sub Domain 1 Interface (QoS)

Sub Domain 2 A
Sub Domain 3 BSSAP
Measured Object BSC

Type Name A interface measurements


Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and 08.08ASSIGNMENT
FAILURE

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 21-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C181g - NB_N7_ASS_FAIL_RadioIntFailRevOldChan
Interface (QoS)
....................................................................................................................................................................................................................................

C181g - NB_N7_ASS_FAIL_RadioIntFailRevOldChan
Descripton

Long Name NB_N7_ASS_FAIL_RadioIntFailRevOldChan

Definition Number of 48.008ASSIGNMENT FAILURE (cause="radio interface failure -reversion to old channel") sent
to the MSC.
Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "radio interface failure -
reversion to old channel" is sent on A interface to the MSC.

Sub Domain 1 Interface (QoS)


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC


Type Name A interface measurements

Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and 08.08ASSIGNMENT
FAILURE
External Comment --
Feature Name --

C181h - NB_N7_ASS_FAIL_RadioIntFail
Descripton

Long Name NB_N7_ASS_FAIL_RadioIntFail


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

Sub Domain 1 Interface (QoS)


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC


Type Name A interface measurements
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and 08.08ASSIGNMENT
FAILURE
External Comment --

Feature Name --

....................................................................................................................................................................................................................................
21-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C181i - NB_N7_ASS_FAIL_CipherAlgoNotSupp
Interface (QoS)
....................................................................................................................................................................................................................................

C181i - NB_N7_ASS_FAIL_CipherAlgoNotSupp
Descripton

Long Name NB_N7_ASS_FAIL_CipherAlgoNotSupp

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

Sub Domain 1 Interface (QoS)


Sub Domain 2 A

Sub Domain 3 BSSAP


Measured Object BSC

Type Name A interface measurements


Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and 08.08ASSIGNMENT
FAILURE
External Comment --

Feature Name --

C181j - NB_N7_ASS_FAIL_BSSnotEquip
Descripton

Long Name NB_N7_ASS_FAIL_BSSnotEquip


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

Sub Domain 1 Interface (QoS)


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC


Type Name A interface measurements
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and 08.08ASSIGNMENT
FAILURE
External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 21-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C181k - NB_N7_ASS_FAIL_ProtocolError
Interface (QoS)
....................................................................................................................................................................................................................................

C181k - NB_N7_ASS_FAIL_ProtocolError
Descripton

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 Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "protocol error between BSC
and MSC" is sent on A interface to the MSC.

Sub Domain 1 Interface (QoS)


Sub Domain 2 A

Sub Domain 3 BSSAP

Measured Object BSC


Type Name A interface measurements

Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and 08.08ASSIGNMENT
FAILURE
External Comment --
Feature Name --

C181l - NB_N7_ASS_FAIL_ReqSpeechVersUnav
Descripton

Long Name NB_N7_ASS_FAIL_ReqSpeechVersUnav


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

Sub Domain 1 Interface (QoS)

Sub Domain 2 A
Sub Domain 3 BSSAP
Measured Object BSC

Type Name A interface measurements

Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and 08.08ASSIGNMENT
FAILURE

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
21-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C181m - NB_N7_ASS_FAIL_ReqAintNotSupp/Unav
Interface (QoS)
....................................................................................................................................................................................................................................

C181m - NB_N7_ASS_FAIL_ReqAintNotSupp/Unav
Descripton

Long Name NB_N7_ASS_FAIL_ReqAintNotSupp/Unav

Definition Number of 48.008ASSIGNMENT FAILURE (cause="requested A-Interface type not supported" or


"requested A-Interface type unavailable") sent to the MSC
Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "requested A-Interface type
not supported" or "requested A-Interface type unavailable" is sent on A interface to the MSC.

Sub Domain 1 Interface (QoS)


Sub Domain 2 A

Sub Domain 3 --

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 --
Feature Name AUPoIP A interface user plane over IP

C181n - NB_N7_ASS_FAIL_ReqCodecNotSupp/Unav
Descripton

Long Name NB_N7_ASS_FAIL_ReqCodecNotSupp/Unav


Definition Number of 48.008ASSIGNMENT FAILURE (cause="requested codec type or codec conf not supported", or
"requested codec type or codec conf unavailable") sent to the MSC.
Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "requested codec type or
codec conf not supported", or "requested codec type or codec conf unavailable" is sent on A interface to the
MSC.

Sub Domain 1 Interface (QoS)


Sub Domain 2 A

Sub Domain 3 --

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

Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 21-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C181p - NB_N7_ASS_FAIL_call_ident_alloc
Interface (QoS)
....................................................................................................................................................................................................................................

C181p - NB_N7_ASS_FAIL_call_ident_alloc
Descripton

Long Name NB_N7_ASS_FAIL_call_ident_alloc

Definition Number of 48.008ASSIGNMENT FAILURE (cause="Call Identifier already allocated") sent to the MSC.
Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "Call identifier already
allocated" is sent on A interface to the MSC.

Sub Domain 1 Interface (QoS)


Sub Domain 2 A

Sub Domain 3 --
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 --

Feature Name AUPoIP A interface user plane over IP

C182 - NB_N7_CLEAR_REQ_EST_PHAS
Descripton

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.
C182=MC182
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 (QoS)


Sub Domain 2 A

....................................................................................................................................................................................................................................
21-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C182 - NB_N7_CLEAR_REQ_EST_PHAS
Interface (QoS)
....................................................................................................................................................................................................................................

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

Feature Name Circuit Switched telecom improvements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 21-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C182 - NB_N7_CLEAR_REQ_EST_PHAS

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
21-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
22 Traffic Load
22

Interface (Traffic Load)

Overview
Purpose
This section contains Interface (Traffic Load) parameters.

Contents

C750 - TIME_A_CHANNEL_BUSY 22-1


C751 - NB_A_CHANNEL_ALLOC 22-2

C750 - TIME_A_CHANNEL_BUSY
Descripton

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 (Traffic Load)

Sub Domain 2 A

Sub Domain 3 --

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 22-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C750 - TIME_A_CHANNEL_BUSY
Interface (Traffic Load)
....................................................................................................................................................................................................................................

Measured Object A interface channel

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 --
Feature Name B7.1 counters improvements

C751 - NB_A_CHANNEL_ALLOC
Descripton

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 (Traffic Load)
Sub Domain 2 A

Sub Domain 3 --
Measured Object A interface channel

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

Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
22-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C751 - NB_A_CHANNEL_ALLOC

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 22-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C751 - NB_A_CHANNEL_ALLOC

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
22-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XI: BSC-TYPE 19 - SMS PP
measurements

Overview
Purpose
All type 19.

Contents

Chapter 23, Quality of Service 23-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XI-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 19 - SMS PP measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XI-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
23 Quality of Service
23

Short Message Service

Overview
Purpose
This section contains Short Message Service parameters.

Contents

C190 - NB_SMS_PP_CON_MO_SDCCH 23-2


C191 - NB_SMS_PP_CON_MT_SDCCH 23-2
C192 - NB_SMS_PP_CON_MO_SACCH 23-3
C193 - NB_SMS_PP_CON_MT_SACCH 23-3
C194a - NB_SMS_PP_CON_REJ_RadioIntFail 23-4
C194b - NB_SMS_PP_CON_REJ_BSSnotEquip 23-4
C194c - NB_SMS_PP_CON_REJ_ProtocolError 23-5
C195 - NB_SMS_PP_CON_REL_LAPDM_ERROR 23-5

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 23-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C190 - NB_SMS_PP_CON_MO_SDCCH
Short Message Service
....................................................................................................................................................................................................................................

C190 - NB_SMS_PP_CON_MO_SDCCH
Descripton

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 Short Message Service


Sub Domain 2 Point to Point

Sub Domain 3 Success


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

Feature Name --

C191 - NB_SMS_PP_CON_MT_SDCCH
Descripton

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 Short Message Service


Sub Domain 2 Point to Point

Sub Domain 3 Success

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

Feature Name --

....................................................................................................................................................................................................................................
23-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C192 - NB_SMS_PP_CON_MO_SACCH
Short Message Service
....................................................................................................................................................................................................................................

C192 - NB_SMS_PP_CON_MO_SACCH
Descripton

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 Short Message Service


Sub Domain 2 Point to Point

Sub Domain 3 Success


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

Feature Name --

C193 - NB_SMS_PP_CON_MT_SACCH
Descripton

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-channel is received
by the BSC.

Sub Domain 1 Short Message Service


Sub Domain 2 Point to Point

Sub Domain 3 Success

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

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 23-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C194a - NB_SMS_PP_CON_REJ_RadioIntFail
Short Message Service
....................................................................................................................................................................................................................................

C194a - NB_SMS_PP_CON_REJ_RadioIntFail
Descripton

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

Feature Name --

C194b - NB_SMS_PP_CON_REJ_BSSnotEquip
Descripton

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

Feature Name --

....................................................................................................................................................................................................................................
23-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C194c - NB_SMS_PP_CON_REJ_ProtocolError
Short Message Service
....................................................................................................................................................................................................................................

C194c - NB_SMS_PP_CON_REJ_ProtocolError
Descripton

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

Feature Name --

C195 - NB_SMS_PP_CON_REL_LAPDM_ERROR
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 23-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C195 - NB_SMS_PP_CON_REL_LAPDM_ERROR
Short Message Service
....................................................................................................................................................................................................................................

Feature Name --

....................................................................................................................................................................................................................................
23-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C195 - NB_SMS_PP_CON_REL_LAPDM_ERROR

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 23-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C195 - NB_SMS_PP_CON_REL_LAPDM_ERROR

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
23-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XII: BSC-TYPE 20 - RMSI
(Radio Measurement
Statistics Improvement)

Overview
Purpose
All type 20.

Contents

Chapter 24, Adjacency 24-1


Chapter 25, Handover 25-1
Chapter 26, Quality of Service 26-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XII-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 20 - RMSI (Radio Measurement Statistics Overview
Improvement)
....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XII-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
24 Adjacency
24

Fixed target Cell

Overview
Purpose
This section contains Fixed target Cell parameters.

Contents

RMSIp80 - NEIGB_CELL_ID_I 24-1

RMSIp80 - NEIGB_CELL_ID_I
Descripton

Long Name NEIGB_CELL_ID_I


Definition BCCH ARFCN and BSIC of the neighbour cell.
Trigger condition --

Sub Domain 1 Fixed target Cell

Sub Domain 2 --
Sub Domain 3 --

Measured Object Common cell

Type Name RMSI (Radio Measurement Statistics Improvement)


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

Feature Name Radio Measurement Statistics Improvement

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 24-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency RMSIp80 - NEIGB_CELL_ID_I

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
24-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
25 Handover
25

RMS

Overview
Purpose
This section contains RMS parameters.

Contents

RMSI63b - MR_MAT_AVSS_VS_NAVSS 25-1

RMSI63b - MR_MAT_AVSS_VS_NAVSS
Descripton

Long Name MR_MAT_AVSS_VS_NAVSS


Definition Greatest value of the Vij in RMSI63a.
Trigger condition --

Sub Domain 1 RMS

Sub Domain 2 --
Sub Domain 3 --

Measured Object Common cell

Type Name RMSI (Radio Measurement Statistics Improvement)


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

Feature Name Radio Measurement Statistics Improvement

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 25-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover RMSI63b - MR_MAT_AVSS_VS_NAVSS

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
25-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
26 Quality of Service
26

RMS

Overview
Purpose
This section contains RMS parameters.

Contents

RMSI3a - TPR_RXQUAL_UL_RXLEV_UL_I 26-2


RMSI3b - TMR_RXQUAL_UL_RXLEV_UL_I 26-4
RMSI4a - TPR_RXQUAL_DL_RXLEV_DL_I 26-5
RMSI4b - TMR_RXQUAL_DL_RXLEV_DL_I 26-7
RMSI50a - TPR_TIMING_ADVANCE_I 26-8
RMSI50b - MAX_TIMING_ADVANCE_I 26-9
RMSI61a - TIMES1 26-9
RMSI61b - TIMES2 26-10
RMSI61c - TIMES3 26-11
RMSI62a - NAVSS 26-11
RMSI62b - MR_NAVSS 26-13
RMSI63a - MAT_AVSS_VS_NAVSS 26-13
RMSI64a - Path_Loss_UL 26-15
RMSI64b - MR_Path_Loss_UL 26-17
RMSI65a - Path_Loss_DL 26-18
RMSI65b - MR_Path_Loss_DL 26-20

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
RMS
....................................................................................................................................................................................................................................

RMSI66a - MS_Power_I 26-21


RMSI66b - MR_MS_Power_I 26-22
RMSI67a - BS_Power_I 26-22
RMSI67b - MR_BS_Power_I 26-24
RMSI7a - TPR_PATH_BALANCE_I 26-24
RMSI7b - MAX_PATH_BALANCE_I 26-26
RMSI8a - TPR_CIN_I 26-26
RMSI8b - MR_CIN_I 26-28
RMSIOLC3a - OLC_TPR_RXQUAL_UL_RXLEV_UL_I 26-28
RMSIOLC3b - OLC_TMR_RXQUAL_UL_RXLEV_UL_I 26-30
RMSIOLC4a - OLC_TPR_RXQUAL_DL_RXLEV_DL_I 26-31
RMSIOLC4b - OLC_TMR_RXQUAL_DL_RXLEV_DL_I 26-33
RMSIOLC50a - OLC_TPR_TIMING_ADVANCE_I 26-34
RMSIOLC50b - OLC_MAX_TIMING_ADVANCE_I 26-35
RMSIOLC62a - OLC_NAVSS 26-35
RMSIOLC62b - OLC_MR_NAVSS 26-37
RMSIOLC7a - OLC_TPR_PATH_BALANCE_I 26-37
RMSIOLC7b - OLC_MAX_PATH_BALANCE_I 26-39
RMSIOLC8a - OLC_TPR_CIN_I 26-39
RMSIOLC8b - OLC_MR_CIN_I 26-41

RMSI3a - TPR_RXQUAL_UL_RXLEV_UL_I
Descripton

Long Name TPR_RXQUAL_UL_RXLEV_UL_I

....................................................................................................................................................................................................................................
26-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI3a - TPR_RXQUAL_UL_RXLEV_UL_I
RMS
....................................................................................................................................................................................................................................

Definition Table of 3x 8x 64 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 equal to 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 RMSI3b).
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 still have to be divided by 4, whereas the values that are provided at the user
interface are the correct ones.
The averaged value of MS power level only meaningful for GSM900 and DCS1800 TRX. For other bands
this value always set to 0.
RXQUAL can take values from 0 to 7 defined in 3GPP TS 45.008:
RXQUAL_0 BER<0,2 %
RXQUAL_1 0,2 BER<0,4 %
RXQUAL_2 0,4 BER<0,8 %
RXQUAL_3 0,8 BER<1,6 %
RXQUAL_4 1,6 BER<3,2 %
RXQUAL_5 3,2 BER<6,4 %
RXQUAL_6 6,4 BER<12,8 %
RXQUAL_7 12,8 BER
RXLEV values to be used (between 0 and 63) are defined in 3GPP TS 45.008:
RXLEV 0=less than -110 dBm
RXLEV 1=-110 dBm to -109 dBm
RXLEV 2= -109 dBm to -108 dBm
:
:
RXLEV 62= -49 dBm to -48 dBm
RXLEV 63=greater than -48 dBm
The MS power found in MEASUREMENT RESULT message is converted to dBm according to 3GPP:
MS Power control level = Nominal Output power
GSM900:
PWCLEV 0-2 39
PWCLEV 3 37
.
.
PWCLEV 18 7
PWCLEV 19-31 5
DCS1800:
PWCLEV 0 30
....................................................................................................................................................................................................................................
PWCLEV 1 28
Alcatel-Lucent 9153 OMC-R 26-3
9YZ-03803-1635-TQZZA B12 .
Issue 13 September 2014
.
PWCLEV 14 2
PWCLEV 15 0
Quality of Service RMSI3a - TPR_RXQUAL_UL_RXLEV_UL_I
RMS
....................................................................................................................................................................................................................................

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

Sub Domain 1 RMS

Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX


Type Name RMSI (Radio Measurement Statistics Improvement)

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

Feature Name Radio Measurement Statistics Improvement

RMSI3b - TMR_RXQUAL_UL_RXLEV_UL_I
Descripton

Long Name TMR_RXQUAL_UL_RXLEV_UL_I


Definition Table of 64 maximum results.
Each cell Ci of the table indicates the greatest value of the Vij for a i given in RMSI3a.
Trigger condition --
Sub Domain 1 RMS
Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX
Type Name RMSI (Radio Measurement Statistics Improvement)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.

External Comment --

Feature Name Radio Measurement Statistics Improvement

....................................................................................................................................................................................................................................
26-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI4a - TPR_RXQUAL_DL_RXLEV_DL_I
RMS
....................................................................................................................................................................................................................................

RMSI4a - TPR_RXQUAL_DL_RXLEV_DL_I
Descripton

Long Name TPR_RXQUAL_DL_RXLEV_DL_I

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI4a - TPR_RXQUAL_DL_RXLEV_DL_I
RMS
....................................................................................................................................................................................................................................

Definition Table of 3x 8x 64 results.


Each cell (i,j) of the table contains :
1) number of reports in which DL RXQUAL is equal to j and DL RXLEV equal to i (Cij)
2) corresponding averaged value of BS 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 RMSI4b).
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 still have to be
divided by 4, whereas the values that are provided at the user interface are the correct ones.
RXQUAL can take values from 0 to 7 defined in 3GPP TS 45.008:
RXQUAL_0 BER<0,2 %
RXQUAL_1 0,2 BER<0,4 %
RXQUAL_2 0,4 BER<0,8 %
RXQUAL_3 0,8 BER<1,6 %
RXQUAL_4 1,6 BER<3,2 %
RXQUAL_5 3,2 BER<6,4 %
RXQUAL_6 6,4 BER<12,8 %
RXQUAL_7 12,8 BER
RXLEV values to be used (between 0 and 63) are defined in 3GPP TS 45.008:
RXLEV 0=less than -110 dBm
RXLEV 1=-110 dBm to -109 dBm
RXLEV 2= -109 dBm to -108 dBm
:
:
RXLEV 62= -49 dBm to -48 dBm
RXLEV 63=greater than -48 dBm
BS power level is the transmission power of the base station at the antenna connector (TOC) expressed in
dBm.
BS power level (binary value between 0 and 15) received in MEASUREMENT RESULT is as follows:
Value Power level (Pn = nominal value)
0 Pn
1 Pn - 2 dB
2 Pn - 4 dB
.
.
14 Pn - 28 dB
15 Pn - 30 dB
Pn = Max-Power-Per-Sector GSM/DCS (dBm) - BS_TXPWR_ATTENUATION (dB)
except for concentric cell configuration
....................................................................................................................................................................................................................................
Outerzone-Pn = Outerzone-Output-Power (dBm) - BS_TXPWR_ATTENUATION Alcatel-Lucent 9153 OMC-R
26-6
Innerzone-Pn = Innerzone-Output-Power (dBm) - BS_TXPWR_ATTENUATION_INNER 9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
The TA values (between 0 and 63) are those defined in 3GPP TS 45.010
Quality of Service RMSI4a - TPR_RXQUAL_DL_RXLEV_DL_I
RMS
....................................................................................................................................................................................................................................

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

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name RMSI (Radio Measurement Statistics Improvement)


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

External Comment --

Feature Name Radio Measurement Statistics Improvement

RMSI4b - TMR_RXQUAL_DL_RXLEV_DL_I
Descripton

Long Name TMR_RXQUAL_DL_RXLEV_DL_I


Definition Table of 64 maximum results.
Each cell Ci of the table indicates the greatest value of the Vij for a i given in RMSI4a.
Trigger condition --
Sub Domain 1 RMS
Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX
Type Name RMSI (Radio Measurement Statistics Improvement)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.

External Comment --
Feature Name Radio Measurement Statistics Improvement

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI50a - TPR_TIMING_ADVANCE_I
RMS
....................................................................................................................................................................................................................................

RMSI50a - TPR_TIMING_ADVANCE_I
Descripton

Long Name TPR_TIMING_ADVANCE_I

Definition Table of 64 results


Each cell (i) of the table contains :
Number of reports in which Timing Advance is equal to i
The result is given as follows :
Ci=Vi x 254 / RMSI50b, where Vi represents the real number of measurements).
Ci=0 indicates 'number of measurements = 0'
Ci=254 indicates 'number of measurements = Max'
Ci=255 is reserved to indicate overflow.
Timing Advance band is defined by :
The TA values to be used (between 0 and 63) are defined in 3GPP TS 45.010:
The timing advance shall be in the range 0 to 63. The value 0 corresponds to no timing advance, i.e. the MS
transmissions to the BTS are 468,75 symbol periods behind. The value 63 corresponds to maximum timing
advance, i.e. the MS transmissions are 468,75 - 63 symbol periods behind.
Trigger condition Whenever in a 44.018 MEASUREMENT RESULT the Timing Advance is equal to i.
Sub Domain 1 RMS

Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX


Type Name RMSI (Radio Measurement Statistics Improvement)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name Radio Measurement Statistics Improvement

....................................................................................................................................................................................................................................
26-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI50b - MAX_TIMING_ADVANCE_I
RMS
....................................................................................................................................................................................................................................

RMSI50b - MAX_TIMING_ADVANCE_I
Descripton

Long Name MAX_TIMING_ADVANCE_I

Definition Greatest value of the Vi in RMSI50a.


Trigger condition --

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name RMSI (Radio Measurement Statistics Improvement)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name Radio Measurement Statistics Improvement

RMSI61a - TIMES1
Descripton

Long Name TIMES1


Definition For each neighbour cell, the PM is [number of samples which is ranked in first stand of the RxLevel in
measurement results message]/[sum of all neighbour cell sample counts in measurement results ]
The value is rounded up or down to the nearest value with an accuracy of 0.1.
Note : The reported value shall then be divided by 10 so that the value that is taken into acount (integer and
decimal parts) is the correct one.
Trigger condition In each measurement result message received from BTS, there is up to 6 best Neighbour cell downlink
measurement results. In this message, RXLEV NCELL i , the received signal strength on the i'th neighbour
cell (1<=i<=6) is reported together with the Base station identity code of the i'th neighboring cell
(BSIC-NCELL i). The measured signal level are mapped to a RXLEV band between 0 and 63.(3GPP TS
45.008)
The first highest RXLEV value in the message is taken into account to increment the counter.
Level 0 is the lowest Rxlev; level 63 is the highest Rxlev.

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name RMSI (Radio Measurement Statistics Improvement)


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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI61a - TIMES1
RMS
....................................................................................................................................................................................................................................

External Comment --

Feature Name Radio Measurement Statistics Improvement

RMSI61b - TIMES2
Descripton

Long Name TIMES2

Definition For each neighbour cell, the PM is [number of samples which is ranked in second stand of the RxLevel in
measurement results message]/[sum of all neighbour cell sample counts in measurement results ]
The value is rounded up or down to the nearest value with an accuracy of 0.1.
Note : The reported value shall then be divided by 10 so that the value that is taken into acount (integer and
decimal parts) is the correct one.
Trigger condition In each measurement result message received from BTS, there is up to 6 best Neighbour cell downlink
measurement results. In this message, RXLEV NCELL i , the received signal strength on the i'th neighbour
cell (1<i=<=6) is reported together with the Base station identity code of the i'th neighboring cell
(BSIC-NCELL i).The measured signal level are mapped to a RXLEV band between 0 and 63.(3GPP TS
45.008)
The second highest RXLEV value in the message is taken into account to increment the counter.
Level 0 is the lowest Rxlev; level 63 is the highest Rxlev.
Sub Domain 1 RMS
Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name RMSI (Radio Measurement Statistics Improvement)


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

Feature Name Radio Measurement Statistics Improvement

....................................................................................................................................................................................................................................
26-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI61c - TIMES3
RMS
....................................................................................................................................................................................................................................

RMSI61c - TIMES3
Descripton

Long Name TIMES3

Definition For each neighbour cell, the KPI is [number of samples which is ranked in third stand of the RxLevel in
measurement results message]/[sum of all neighbour cell sample counts in measurement results ]
The value is rounded up or down to the nearest value with an accuracy of 0.1.
Note : The reported value shall then be divided by 10 so that the value that is taken into acount (integer and
decimal parts) is the correct one.
Trigger condition In each measurement result message received from BTS, there is up to 6 best Neighbour cell downlink
measurement results. In this message, RXLEV NCELL i , the received signal strength on the i'th neighbour
cell (1<=i<=6) is reported together with the Base station identity code of the i'th neighboring cell
(BSIC-NCELL i).The measured signal level are mapped to a RXLEV band between 0 and 63.(3GPP TS
45.008)
The third highest RXLEV value in the message is taken into account to increment the counter.
Level 0 is the lowest Rxlev; level 63 is the highest Rxlev.
Sub Domain 1 RMS
Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name RMSI (Radio Measurement Statistics Improvement)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name Radio Measurement Statistics Improvement

RMSI62a - NAVSS
Descripton

Long Name NAVSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI62a - NAVSS
RMS
....................................................................................................................................................................................................................................

Definition Table of 64 results per neighbour cell.


Each cell i of the table contains :
Number of reports in which the downlink RXLEV related to the neighbour cell is reported in RXLEV band
i.
The measured signal level are mapped to a RXLEV band between 0 and 63.(3GPP TS 45.008)
The result is given as follows :
Ci=Vi x 254 / RMSI62b, 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. RXLEV band is defined by :
Each mobile station sends up to 6 Neighbour cell downlink measurement result in the MEASUREMENT
REPORT. In this message, RXLEV NCELL i , the received signal strength on the i'th neighbour cell
(1<=i<=6) is reported together with the Base station identity code of the i'th neighboring cell (BSIC-NCELL
i) 0: NAVSS_0= the number of samples which Rx level belongs to Level Band 0 (RXLEV_0 = less than
-110 dBm)
1: NAVSS_1= the number of samples which Rx level belongs to Level Band 1 (RXLEV_1 = -110 dBm to
-109 dBm)
....
62: NAVSS_62= the number of samples which Rx level belongs to Level Band 62 (RXLEV_62 = -49 dBm
to -48 dBm)
63: NAVSS_63= the number of samples which Rx level belongs to Level Band 63 (RXLEV_63 = greater
than -48 dBm )
Trigger condition Whenever a measurement report indicates that RXLEV 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 Common cell


Type Name RMSI (Radio Measurement Statistics Improvement)

Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name Radio Measurement Statistics Improvement

....................................................................................................................................................................................................................................
26-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI62b - MR_NAVSS
RMS
....................................................................................................................................................................................................................................

RMSI62b - MR_NAVSS
Descripton

Long Name MR_NAVSS

Definition Greatest value of the Vi in RMSI62a


Trigger condition --

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name RMSI (Radio Measurement Statistics Improvement)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name Radio Measurement Statistics Improvement

RMSI63a - MAT_AVSS_VS_NAVSS
Descripton

Long Name MAT_AVSS_VS_NAVSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI63a - MAT_AVSS_VS_NAVSS
RMS
....................................................................................................................................................................................................................................

Definition Table of 11x11 matrix results per neighbour cell.


Each cell i of the table contains :
The matrix of serving cell DL received signal level (i) and neighbour cell signal level (j); the Rx Level of
serving and neighbour cells are divided into 11 bands; so for each neighbour cell, it will have a 11*11
matrix.
The result is given as follows :
Cij=Vij x 254 / RMSI63b(i,j), where Vij represents the real number of measurement. Just divide (round
down).
Cij=0 indicates 'number of measurements = 0'
Cij=254 indicates 'number of measurements = Max_ij'
Cij=255 is reserved to indicate overflow. RXLEV band is defined by :
Each mobile station sends serving cell downlink measurement and up to 6 Neighbour cell downlink
measurement result in the MEASUREMENT REPORT
The band defined by the RxLevel each 5 dB from -100dbm to -55dB
i = 0..10
0: Serving cell RXLEV <-100dbm
1: Serving cell RXLEV ]-95dbm,-100dbm]
...
10:Serving cell RXLEV >=-55dbm
j = 0..10
0: Neighbour cell A RXLEV <-100dbm
1: Neighbour cell A RXLEV ]-95dbm,-100dbm]
...
10:Neighbour cell A RXLEV >=-55dbm
i,j: MAT_AVSS_VS_NAVSS_00 to MAT_AVSS_VS_NAVSS_120
0,0:MAT_AVSS_VS_NAVSS_00 the numbers of samples whose Rxlevel of the serving cell and neigbour
cell are distributed in band0
1,0:MAT_AVSS_VS_NAVSS_11 the numbers of samples whose Rxlevel of the serving cell and neigbour
cell are distributed in band11
..
10,10: MAT_AVSS_VS_NAVSS_120 the numbers of samples whose Rxlevel of the serving cell and
neigbour cell are distributed in band120

Trigger condition Whenever a measurement report indicates that RXLEV value for the call related to the serving and
neighbour cell is included in the corresponding matrix case.
Sub Domain 1 RMS

Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name RMSI (Radio Measurement Statistics Improvement)


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

External Comment --
Feature Name Radio Measurement Statistics Improvement

....................................................................................................................................................................................................................................
26-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI64a - Path_Loss_UL
RMS
....................................................................................................................................................................................................................................

RMSI64a - Path_Loss_UL
Descripton

Long Name Path_Loss_UL

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI64a - Path_Loss_UL
RMS
....................................................................................................................................................................................................................................

Definition Table of 60 results.


Each cell (i) of the table contains :
Number of reports in which UL path Loss is in UL Path Loss 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 RMSI64b).
Ci=0 indicates 'number of measurements = 0'
Ci=254 indicates 'number of measurements = Max_i'
Ci=255 is reserved to indicate overflow.
This counter is only applicable to GSM-900 and DCS1800 TRX. Value 0 indicates that the TRX frequency
is not in GSM900 and DCS1800 bands.
Path Loss band PLOSSUL is defined by :
Reported value Measured quantity value(dB)
PLOSSUL0 30-31
PLOSSUL1 32-33
PLOSSUL2 34-35
PLOSSUL3 36-37
......
PLOSSUL57 144-145
PLOSSUL58 146-147
PLOSSUL59 148-153
These bands are not configurable.
UL Path Loss = (MS power level - RXLEV_UL)
RXLEV_UL is the received signal levels by the base station (dBm)
RXLEV 0=less than -110 dBm
RXLEV 1=-110 dBm to -109 dBm
RXLEV 2= -109 dBm to -108 dBm
:
:
RXLEV 62= -49 dBm to -48 dBm
RXLEV 63=greater than -48 dBm
MS power level is the transmission power of the mobile station expressed in dBm
MS Power control level Nominal Output power(dBm)
GSM900:
PWCLEV 0-2 39
PWCLEV 3 37
.
.
PWCLEV 18 7
PWCLEV 19-31 5
DCS1800:
PWCLEV 0 30
PWCLEV 1 28
.
....................................................................................................................................................................................................................................
26-16 Alcatel-Lucent 9153 OMC-R
.
9YZ-03803-1635-TQZZA B12
PWCLEV 14 2 Issue 13 September 2014

PWCLEV 15 0
Quality of Service RMSI64a - Path_Loss_UL
RMS
....................................................................................................................................................................................................................................

Trigger condition Whenever in a 44.018 MEASUREMENT RESULT the calculated UL Path Loss is in the given interval .

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name RMSI (Radio Measurement Statistics Improvement)


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

External Comment --
Feature Name Radio Measurement Statistics Improvement

RMSI64b - MR_Path_Loss_UL
Descripton

Long Name MR_Path_Loss_UL


Definition Greatest value of the Vi in RMSI64a
Trigger condition --
Sub Domain 1 RMS
Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX
Type Name RMSI (Radio Measurement Statistics Improvement)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name Radio Measurement Statistics Improvement

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-17
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI65a - Path_Loss_DL
RMS
....................................................................................................................................................................................................................................

RMSI65a - Path_Loss_DL
Descripton

Long Name Path_Loss_DL

....................................................................................................................................................................................................................................
26-18 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI65a - Path_Loss_DL
RMS
....................................................................................................................................................................................................................................

Definition Table of 65 results


Each cell (i) of the table contains :
Number of reports in which DL path Loss is in DL Path Loss 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 RMSI65b).
Ci=0 indicates 'number of measurements = 0'
Ci=254 indicates 'number of measurements = Max_i'
Ci=255 is reserved to indicate overflow.
Path Loss band PLOSSDL is defined by :Reported value Measured quantity value(dB)
PLOSSDL0 30-31
PLOSSDL1 32-33
PLOSSDL2 34-35
PLOSSDL3 36-37
..
PLOSSDL62 154-155
PLOSSDL63 156-157
PLOSSDL64 158-190
These bands are not configurable.
DL Path Loss = (BS power level - RXLEV_DL )
RXLEV_DL is the received signal levels by the mobile station (dBm).
RXLEV 0=less than -110 dBm
RXLEV 1=-110 dBm to -109 dBm
RXLEV 2= -109 dBm to -108 dBm
:
:
RXLEV 62= -49 dBm to -48 dBm
RXLEV 63=greater than -48 dBm
BS power level is the transmission power of the base station at the antenna connector (TOC) expressed in
dBm.
Consequently combiner loss is taken into account.
BS power level (binary value between 0 and 15) received in MEASUREMENT RESULT is as follows:
Value Power level (Pn = nominal value)
0 Pn
1 Pn - 2 dB
2 Pn - 4 dB
.
.
14 Pn - 28 dB
15 Pn - 30 dB
Pn = Max-Power-Per-Sector GSM/DCS (dBm) - BS_TXPWR_ATTENUATION (dB)
except for concentric cell configuration
Outerzone-Pn = Outerzone-Output-Power (dBm) - BS_TXPWR_ATTENUATION
....................................................................................................................................................................................................................................
Innerzone-Pn = Innerzone-Output-Power (dBm) - BS_TXPWR_ATTENUATION_INNER
Alcatel-Lucent 9153 OMC-R 26-19
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI65a - Path_Loss_DL
RMS
....................................................................................................................................................................................................................................

Trigger condition Whenever in a 44.018 MEASUREMENT RESULT the calculated DL Path Loss is in the given interval .

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name RMSI (Radio Measurement Statistics Improvement)


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

External Comment --
Feature Name Radio Measurement Statistics Improvement

RMSI65b - MR_Path_Loss_DL
Descripton

Long Name MR_Path_Loss_DL


Definition Greatest value of the Vi in RMSI65a
Trigger condition --
Sub Domain 1 RMS
Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX
Type Name RMSI (Radio Measurement Statistics Improvement)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name Radio Measurement Statistics Improvement

....................................................................................................................................................................................................................................
26-20 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI66a - MS_Power_I
RMS
....................................................................................................................................................................................................................................

RMSI66a - MS_Power_I
Descripton

Long Name MS_Power_I

Definition Table of 20 results


Each cell (i) of the table contains :
Number of reports in which MS power is in MS power 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 RMSI66b).
Ci=0 indicates 'number of measurements = 0'
Ci=254 indicates 'number of measurements = Max_i'
Ci=255 is reserved to indicate overflow.
This counter is only applicable to GSM-900 and DCS1800 TRX. Value 0 indicates that the TRX frequency
is not in GSM900 or DCS1800 bands.
MS Power control level Nominal Output power(dBm)
GSM900:
PWCLEV 0-2 39
PWCLEV 3 37
.
.
PWCLEV 18 7
PWCLEV 19-31 5
DCS1800:
PWCLEV 0 30
PWCLEV 1 28
.
.
PWCLEV 14 2
PWCLEV 15 0
Consequently 20 bands are defined according tp MS Power control level:
Band 1: 0
Band 2: 1
....
Band 20: 19-31
These bands are not configurable.

Trigger condition Whenever in a 44.018 MEASUREMENT RESULT the MS power level (binary value between 0 and 31) is
in the given interval .

Sub Domain 1 RMS

Sub Domain 2 --
Sub Domain 3 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-21
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI66a - MS_Power_I
RMS
....................................................................................................................................................................................................................................

Measured Object TRX

Type Name RMSI (Radio Measurement Statistics Improvement)


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

External Comment --
Feature Name Radio Measurement Statistics Improvement

RMSI66b - MR_MS_Power_I
Descripton

Long Name MR_MS_Power_I


Definition Greatest value of the Vi in RMSI66a
Trigger condition --
Sub Domain 1 RMS
Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX
Type Name RMSI (Radio Measurement Statistics Improvement)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name Radio Measurement Statistics Improvement

RMSI67a - BS_Power_I
Descripton

Long Name BS_Power_I

....................................................................................................................................................................................................................................
26-22 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI67a - BS_Power_I
RMS
....................................................................................................................................................................................................................................

Definition Table of 16 results


Each cell (i) of the table contains :
Number of reports in which BS power is in BS power 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 RMSI67b).
Ci=0 indicates 'number of measurements = 0'
Ci=254 indicates 'number of measurements = Max_i'
Ci=255 is reserved to indicate overflow.
BS power ranges are defined according to 3GPP by :
Value Power level (Pn = nominal value)
0 Pn
1 Pn - 2 dB
2 Pn - 4 dB
.
.
14 Pn - 28 dB
15 Pn - 30 dB
These bands are not configurable.
Trigger condition Whenever in a 44.018 MEASUREMENT RESULT the BS power level (binary value between 0 and 15) is
in the given interval .
Sub Domain 1 RMS
Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX


Type Name RMSI (Radio Measurement Statistics Improvement)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name Radio Measurement Statistics Improvement

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-23
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI67b - MR_BS_Power_I
RMS
....................................................................................................................................................................................................................................

RMSI67b - MR_BS_Power_I
Descripton

Long Name MR_BS_Power_I

Definition Greatest value of the Vi in RMSI67a


Trigger condition --

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name RMSI (Radio Measurement Statistics Improvement)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name Radio Measurement Statistics Improvement

RMSI7a - TPR_PATH_BALANCE_I
Descripton

Long Name TPR_PATH_BALANCE_I

....................................................................................................................................................................................................................................
26-24 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI7a - TPR_PATH_BALANCE_I
RMS
....................................................................................................................................................................................................................................

Definition Table of 51 results


Each cell (i) of the table contains :
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 RMSI7b).
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 :
Band0 <- 24dB
Band1 -24
Band2 -23
Band3 -22
..
Band48 23
Band49 24
Band50 >24
These bands are not configurable.
Path balance = difference in dB between UL and DL pass loss as defined in RMSI64 and RMSI65.
Path balance = DL Path Loss - UL Path Loss = (BS power level - RXLEV_DL ) - (MS power level -
RXLEV_UL)
Trigger condition Whenever in a 44.018 MEASUREMENT RESULT the Path Balance is in the given interval .
Sub Domain 1 RMS
Sub Domain 2 --
Sub Domain 3 --
Measured Object TRX
Type Name RMSI (Radio Measurement Statistics Improvement)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.

External Comment --

Feature Name Radio Measurement Statistics Improvement

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-25
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI7b - MAX_PATH_BALANCE_I
RMS
....................................................................................................................................................................................................................................

RMSI7b - MAX_PATH_BALANCE_I
Descripton

Long Name MAX_PATH_BALANCE_I

Definition Greatest value of the Vi in RMSI7a.


Trigger condition --

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name RMSI (Radio Measurement Statistics Improvement)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name Radio Measurement Statistics Improvement

RMSI8a - TPR_CIN_I
Descripton

Long Name TPR_CIN_I

....................................................................................................................................................................................................................................
26-26 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI8a - TPR_CIN_I
RMS
....................................................................................................................................................................................................................................

Definition Table of 51 results per neighbour cell.


Each cell i of the table contains :
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 / RMSI8b, 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 bands are defined by :
Band 0: C/I <- 24dB,
Band 1: C/I =-24dB,
Band 2: C/I =-23dB
.
Band 48: C/I=23dB,
Band 49: C/I=24dB,
Band 50: C/I>24dB.
These bands are not configurable.
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 RMSI (Radio Measurement Statistics Improvement)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name Radio Measurement Statistics Improvement

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-27
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSI8b - MR_CIN_I
RMS
....................................................................................................................................................................................................................................

RMSI8b - MR_CIN_I
Descripton

Long Name MR_CIN_I

Definition Greatest value of the Vi in RMSI8a.


Trigger condition --

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name RMSI (Radio Measurement Statistics Improvement)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name Radio Measurement Statistics Improvement

RMSIOLC3a - OLC_TPR_RXQUAL_UL_RXLEV_UL_I
Descripton

Long Name OLC_TPR_RXQUAL_UL_RXLEV_UL_I

....................................................................................................................................................................................................................................
26-28 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSIOLC3a - OLC_TPR_RXQUAL_UL_RXLEV_UL_I
RMS
....................................................................................................................................................................................................................................

Definition Table of 3x 8x 64 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 equal to 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 RMSIOLC3b).
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 still have to be divided by 4, whereas the values that are provided at the user
interface are the correct ones.
The averaged value of MS power level only meaningful for GSM900 and DCS1800 TRX. For other bands
this value always set to 0.
RXQUAL can take values from 0 to 7 defined in 3GPP TS 45.008:
RXQUAL_0 BER<0,2 %
RXQUAL_1 0,2 BER<0,4 %
RXQUAL_2 0,4 BER<0,8 %
RXQUAL_3 0,8 BER<1,6 %
RXQUAL_4 1,6 BER<3,2 %
RXQUAL_5 3,2 BER<6,4 %
RXQUAL_6 6,4 BER<12,8 %
RXQUAL_7 12,8 BER
RXLEV values to be used (between 0 and 63) are defined in 3GPP TS 45.008:
RXLEV 0=less than -110 dBm
RXLEV 1=-110 dBm to -109 dBm
RXLEV 2= -109 dBm to -108 dBm
:
:
RXLEV 62= -49 dBm to -48 dBm
RXLEV 63=greater than -48 dBm
The MS power found in MEASUREMENT RESULT message is converted to dBm according to 3GPP:
MS Power control level = Nominal Output power
GSM900:
PWCLEV 0-2 39
PWCLEV 3 37
.
.
PWCLEV 18 7
PWCLEV 19-31 5
DCS1800:
PWCLEV 0 30
PWCLEV 1 28
....................................................................................................................................................................................................................................
.
Alcatel-Lucent 9153 OMC-R 26-29
9YZ-03803-1635-TQZZA B12 .
Issue 13 September 2014
PWCLEV 14 2
PWCLEV 15 0
The TA values (between 0 and 63) are those defined in 3GPP TS 45.010
Quality of Service RMSIOLC3a - OLC_TPR_RXQUAL_UL_RXLEV_UL_I
RMS
....................................................................................................................................................................................................................................

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

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object Site_TRX

Type Name RMSI (Radio Measurement Statistics Improvement)


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

External Comment --

Feature Name --

RMSIOLC3b - OLC_TMR_RXQUAL_UL_RXLEV_UL_I
Descripton

Long Name OLC_TMR_RXQUAL_UL_RXLEV_UL_I


Definition Table of 64 maximum results.
Each cell Ci of the table indicates the greatest value of the Vij for a i given in RMSIOLC3a.
Trigger condition --
Sub Domain 1 RMS
Sub Domain 2 --

Sub Domain 3 --
Measured Object Site_TRX
Type Name RMSI (Radio Measurement Statistics Improvement)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
26-30 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSIOLC4a - OLC_TPR_RXQUAL_DL_RXLEV_DL_I
RMS
....................................................................................................................................................................................................................................

RMSIOLC4a - OLC_TPR_RXQUAL_DL_RXLEV_DL_I
Descripton

Long Name OLC_TPR_RXQUAL_DL_RXLEV_DL_I

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-31
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSIOLC4a - OLC_TPR_RXQUAL_DL_RXLEV_DL_I
RMS
....................................................................................................................................................................................................................................

Definition Table of 3x 8x 64 results.


Each cell (i,j) of the table contains :
1) number of reports in which DL RXQUAL is equal to j and DL RXLEV equal to i (Cij)
2) corresponding averaged value of BS 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 RMSIOLC4b).
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 still have to be
divided by 4, whereas the values that are provided at the user interface are the correct ones.
RXQUAL can take values from 0 to 7 defined in 3GPP TS 45.008:
RXQUAL_0 BER<0,2 %
RXQUAL_1 0,2 BER<0,4 %
RXQUAL_2 0,4 BER<0,8 %
RXQUAL_3 0,8 BER<1,6 %
RXQUAL_4 1,6 BER<3,2 %
RXQUAL_5 3,2 BER<6,4 %
RXQUAL_6 6,4 BER<12,8 %
RXQUAL_7 12,8 BER
RXLEV values to be used (between 0 and 63) are defined in 3GPP TS 45.008:
RXLEV 0=less than -110 dBm
RXLEV 1=-110 dBm to -109 dBm
RXLEV 2= -109 dBm to -108 dBm
:
:
RXLEV 62= -49 dBm to -48 dBm
RXLEV 63=greater than -48 dBm
BS power level is the transmission power of the base station at the antenna connector (TOC) expressed in
dBm.
BS power level (binary value between 0 and 15) received in MEASUREMENT RESULT is as follows:
Value Power level (Pn = nominal value)
0 Pn
1 Pn - 2 dB
2 Pn - 4 dB
.
.
14 Pn - 28 dB
15 Pn - 30 dB
Pn = Max-Power-Per-Sector GSM/DCS (dBm) - BS_TXPWR_ATTENUATION (dB)
except for concentric cell configuration
....................................................................................................................................................................................................................................
Outerzone-Pn = Outerzone-Output-Power (dBm) - BS_TXPWR_ATTENUATION Alcatel-Lucent 9153 OMC-R
26-32
Innerzone-Pn = Innerzone-Output-Power (dBm) - BS_TXPWR_ATTENUATION_INNER 9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
The TA values (between 0 and 63) are those defined in 3GPP TS 45.010
Quality of Service RMSIOLC4a - OLC_TPR_RXQUAL_DL_RXLEV_DL_I
RMS
....................................................................................................................................................................................................................................

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

Sub Domain 1 RMS

Sub Domain 2 --
Sub Domain 3 --

Measured Object Site_TRX


Type Name RMSI (Radio Measurement Statistics Improvement)

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

Feature Name --

RMSIOLC4b - OLC_TMR_RXQUAL_DL_RXLEV_DL_I
Descripton

Long Name OLC_TMR_RXQUAL_DL_RXLEV_DL_I


Definition Table of 64 maximum results.
Each cell Ci of the table indicates the greatest value of the Vij for a i given in RMSIOLC4a.
Trigger condition --
Sub Domain 1 RMS
Sub Domain 2 --

Sub Domain 3 --
Measured Object Site_TRX
Type Name RMSI (Radio Measurement Statistics Improvement)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-33
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSIOLC50a - OLC_TPR_TIMING_ADVANCE_I
RMS
....................................................................................................................................................................................................................................

RMSIOLC50a - OLC_TPR_TIMING_ADVANCE_I
Descripton

Long Name OLC_TPR_TIMING_ADVANCE_I

Definition Table of 64 results


Each cell (i) of the table contains :
Number of reports in which Timing Advance is equal to i
The result is given as follows :
Ci=Vi x 254 / RMSIOLC50b, where Vi represents the real number of measurements).
Ci=0 indicates 'number of measurements = 0'
Ci=254 indicates 'number of measurements = Max'
Ci=255 is reserved to indicate overflow.
Timing Advance band is defined by :
The TA values to be used (between 0 and 63) are defined in 3GPP TS 45.010:
The timing advance shall be in the range 0 to 63. The value 0 corresponds to no timing advance, i.e. the MS
transmissions to the BTS are 468,75 symbol periods behind. The value 63 corresponds to maximum timing
advance, i.e. the MS transmissions are 468,75 - 63 symbol periods behind
Trigger condition Whenever in a 44.018 MEASUREMENT RESULT the Timing Advance is equal to i
Sub Domain 1 RMS

Sub Domain 2 --
Sub Domain 3 --

Measured Object Site_TRX


Type Name RMSI (Radio Measurement Statistics Improvement)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name --

....................................................................................................................................................................................................................................
26-34 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSIOLC50b - OLC_MAX_TIMING_ADVANCE_I
RMS
....................................................................................................................................................................................................................................

RMSIOLC50b - OLC_MAX_TIMING_ADVANCE_I
Descripton

Long Name OLC_MAX_TIMING_ADVANCE_I

Definition Greatest value of the Vi in RMSIOLC50a.


Trigger condition --

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object Site_TRX

Type Name RMSI (Radio Measurement Statistics Improvement)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name --

RMSIOLC62a - OLC_NAVSS
Descripton

Long Name OLC_NAVSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-35
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSIOLC62a - OLC_NAVSS
RMS
....................................................................................................................................................................................................................................

Definition Table of 64 results per neighbour cell.


Each cell i of the table contains :
Number of reports in which the downlink RXLEV related to the neighbour cell is reported in RXLEV band
i.
The measured signal level are mapped to a RXLEV band between 0 and 63.(3GPP TS 45.008)
The result is given as follows :
Ci=Vi x 254 / RMSIOLC62b, 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. RXLEV band is defined by :
Each mobile station sends up to 6 Neighbour cell downlink measurement result in the MEASUREMENT
REPORT. In this message, RXLEV NCELL i , the received signal strength on the i'th neighbour cell
(1<=i<=6) is reported together with the Base station identity code of the i'th neighboring cell (BSIC-NCELL
i) 0: NAVSS_0= the number of samples which Rx level belongs to Level Band 0 (RXLEV_0 = less than
-110 dBm)
1: NAVSS_1= the number of samples which Rx level belongs to Level Band 1 (RXLEV_1 = -110 dBm to
-109 dBm)
....
62: NAVSS_62= the number of samples which Rx level belongs to Level Band 62 (RXLEV_62 = -49 dBm
to -48 dBm)
63: NAVSS_63= the number of samples which Rx level belongs to Level Band 63 (RXLEV_63 = greater
than -48 dBm )
Trigger condition Whenever a measurement report indicates that RXLEV 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 Site


Type Name RMSI (Radio Measurement Statistics Improvement)

Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name --

....................................................................................................................................................................................................................................
26-36 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSIOLC62b - OLC_MR_NAVSS
RMS
....................................................................................................................................................................................................................................

RMSIOLC62b - OLC_MR_NAVSS
Descripton

Long Name OLC_MR_NAVSS

Definition Greatest value of the Vi in RMSIOLC62a


Trigger condition --

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object Site

Type Name RMSI (Radio Measurement Statistics Improvement)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name --

RMSIOLC7a - OLC_TPR_PATH_BALANCE_I
Descripton

Long Name OLC_TPR_PATH_BALANCE_I

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-37
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSIOLC7a - OLC_TPR_PATH_BALANCE_I
RMS
....................................................................................................................................................................................................................................

Definition Table of 51 results


Each cell (i) of the table contains :
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 RMSIOLC7b).
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 :
Band0 <- 24dB
Band1 -24
Band2 -23
Band3 -22
..
Band48 23
Band49 24
Band50 >24
These bands are not configurable.
Path balance = difference in dB between UL and DL pass loss as defined in RMSI64 and RMSI65.
Path balance = DL Path Loss - UL Path Loss = (BS power level - RXLEV_DL ) - (MS power level -
RXLEV_UL)
Trigger condition Whenever in a 44.018 MEASUREMENT RESULT the Path Balance is in the given interval .
Sub Domain 1 RMS
Sub Domain 2 --
Sub Domain 3 --
Measured Object Site_TRX
Type Name RMSI (Radio Measurement Statistics Improvement)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
26-38 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSIOLC7b - OLC_MAX_PATH_BALANCE_I
RMS
....................................................................................................................................................................................................................................

RMSIOLC7b - OLC_MAX_PATH_BALANCE_I
Descripton

Long Name OLC_MAX_PATH_BALANCE_I

Definition Greatest value of the Vi in RMSIOLC7a.


Trigger condition --

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object Site_TRX

Type Name RMSI (Radio Measurement Statistics Improvement)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name --

RMSIOLC8a - OLC_TPR_CIN_I
Descripton

Long Name OLC_TPR_CIN_I

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-39
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSIOLC8a - OLC_TPR_CIN_I
RMS
....................................................................................................................................................................................................................................

Definition Table of 51 results per neighbour cell.


Each cell i of the table contains :
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 / RMSIOLC8b, 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 bands are defined by :
Band 0: C/I <- 24dB,
Band 1: C/I =-24dB,
Band 2: C/I =-23dB
.
Band 48: C/I=23dB,
Band 49: C/I=24dB,
Band 50: C/I>24dB.
These bands are not configurable.
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 Site_TRX
Type Name RMSI (Radio Measurement Statistics Improvement)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --

Feature Name --

....................................................................................................................................................................................................................................
26-40 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSIOLC8b - OLC_MR_CIN_I
RMS
....................................................................................................................................................................................................................................

RMSIOLC8b - OLC_MR_CIN_I
Descripton

Long Name OLC_MR_CIN_I

Definition Greatest value of the Vi in RMSIOLC8a.


Trigger condition --

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object Site_TRX

Type Name RMSI (Radio Measurement Statistics Improvement)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 26-41
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMSIOLC8b - OLC_MR_CIN_I

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
26-42 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XIII: BSC-TYPE 25 - SCCP
measurements

Overview
Purpose
All type 25.

Contents

Chapter 27, Quality of Service 27-1


Chapter 28, Traffic Load 28-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XIII-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 25 - SCCP measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XIII-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
27 Quality of Service
27

Interface (QoS)

Overview
Purpose
This section contains Interface (QoS) parameters.

Contents

C153a - NB_N7_CON_EST_FAIL_DUE_NSS 27-1


C153b - NB_N7_CON_EST_FAIL_DUE_BSS 27-2
C257 - NB_N7_CON_REF_SENT 27-2
C258 - NB_N7_CON_REF_REC 27-3

C153a - NB_N7_CON_EST_FAIL_DUE_NSS
Descripton

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 (QoS)

Sub Domain 2 A

Sub Domain 3 SCCP

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 27-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C153a - NB_N7_CON_EST_FAIL_DUE_NSS
Interface (QoS)
....................................................................................................................................................................................................................................

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 --
Feature Name --

C153b - NB_N7_CON_EST_FAIL_DUE_BSS
Descripton

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 (QoS)
Sub Domain 2 A

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 --
Feature Name --

C257 - NB_N7_CON_REF_SENT
Descripton

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 (QoS)

Sub Domain 2 A

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

....................................................................................................................................................................................................................................
27-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C257 - NB_N7_CON_REF_SENT
Interface (QoS)
....................................................................................................................................................................................................................................

External Comment --

Feature Name --

C258 - NB_N7_CON_REF_REC
Descripton

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 (QoS)


Sub Domain 2 A

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 --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 27-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C258 - NB_N7_CON_REF_REC

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
27-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
28 Traffic Load
28

Interface (Traffic Load)

Overview
Purpose
This section contains Interface (Traffic Load) parameters.

Contents

C251 - NB_N7_UNIT_DATA_SENT 28-2


C252 - NB_N7_UNIT_DATA_REC 28-2
C253 - NB_N7_CON_REQ_SENT 28-3
C254 - NB_N7_CON_REQ_REC 28-3
C255 - NB_N7_CON_CONF_SENT 28-4
C256 - NB_N7_CON_CONF_REC 28-4

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 28-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C251 - NB_N7_UNIT_DATA_SENT
Interface (Traffic Load)
....................................................................................................................................................................................................................................

C251 - NB_N7_UNIT_DATA_SENT
Descripton

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 (Traffic Load)


Sub Domain 2 A

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

Feature Name --

C252 - NB_N7_UNIT_DATA_REC
Descripton

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 (Traffic Load)

Sub Domain 2 A
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 --
Feature Name --

....................................................................................................................................................................................................................................
28-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C253 - NB_N7_CON_REQ_SENT
Interface (Traffic Load)
....................................................................................................................................................................................................................................

C253 - NB_N7_CON_REQ_SENT
Descripton

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 (Traffic Load)


Sub Domain 2 A

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 --
Feature Name --

C254 - NB_N7_CON_REQ_REC
Descripton

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 (Traffic Load)
Sub Domain 2 A

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

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 28-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C255 - NB_N7_CON_CONF_SENT
Interface (Traffic Load)
....................................................................................................................................................................................................................................

C255 - NB_N7_CON_CONF_SENT
Descripton

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 (Traffic Load)


Sub Domain 2 A

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 --
Feature Name --

C256 - NB_N7_CON_CONF_REC
Descripton

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 (Traffic Load)
Sub Domain 2 A

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

Feature Name --

....................................................................................................................................................................................................................................
28-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C256 - NB_N7_CON_CONF_REC

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 28-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load C256 - NB_N7_CON_CONF_REC

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
28-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XIV: BSC-TYPE 26 - TCH
outgoing handover per
adjacency measurements

Overview
Purpose
All type 26.

Contents

Chapter 29, Adjacency 29-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XIV-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 26 - TCH outgoing handover per adjacency Overview
measurements
....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XIV-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
29 Adjacency
29

Fixed serving Cell

Overview
Purpose
This section contains Fixed serving Cell parameters.

Contents

C720 - NB_ADJ_SCELL_OUT_TCH_HO_ATPT 29-2


C721 - NB_ADJ_SCELL_OUT_TCH_HO_SUCC 29-2
C722 - NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_REV 29-3
C723 - NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_NO_REV 29-3
C724 - NB_ADJ_SCELL_OUT_TCH_HO_EMERGENCY_ATPT 29-4
C725 - NB_ADJ_SCELL_OUT_TCH_HO_BETTERCELL_ATPT 29-5
C727 - NB_ADJ_SCELL_OUT_TCH_HO_TRAFFIC_ATPT 29-5
C728 - NB_ADJ_SCELL_OUT_ FORCED_DR_ATPT 29-6

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 29-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency C720 - NB_ADJ_SCELL_OUT_TCH_HO_ATPT
Fixed serving Cell
....................................................................................................................................................................................................................................

C720 - NB_ADJ_SCELL_OUT_TCH_HO_ATPT
Descripton

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 --
Feature Name --

C721 - NB_ADJ_SCELL_OUT_TCH_HO_SUCC
Descripton

Long Name NB_ADJ_SCELL_OUT_TCH_HO_SUCC


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

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 = "normal event/call control") is received while T8 is running.
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

....................................................................................................................................................................................................................................
29-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency C721 - NB_ADJ_SCELL_OUT_TCH_HO_SUCC
Fixed serving Cell
....................................................................................................................................................................................................................................

Type Name TCH outgoing handover per adjacency measurements

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

Feature Name --

C722 - NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_REV
Descripton

Long Name NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_REV

Definition Number of outgoing external and internal inter-cell TCH (in HR or FR usage) handover -execution failures
due to MS access problem with reversion of 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 fixed serving
cell during an external or internal inter-cell TCH handover attempted towards the variable 2G 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 --
Feature Name --

C723 - NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_NO_REV
Descripton

Long Name NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_NO_REV

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 29-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency C723 - NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_NO_REV
Fixed serving Cell
....................................................................................................................................................................................................................................

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 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 --
Feature Name --

C724 - NB_ADJ_SCELL_OUT_TCH_HO_EMERGENCY_ATPT
Descripton

Long Name NB_ADJ_SCELL_OUT_TCH_HO_EMERGENCY_ATPT


Definition Number of outgoing external and internal inter-cell TCH (in HR or FR usage) handover attempts with
emergency cause. This counter takes into 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 2, 3, 4, 5, 6, 7, 17, 18, 22 on a TCH channel, from the fixed
serving cell to the variable target cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 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 --

Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
29-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency C725 - NB_ADJ_SCELL_OUT_TCH_HO_BETTERCELL_ATPT
Fixed serving Cell
....................................................................................................................................................................................................................................

C725 - NB_ADJ_SCELL_OUT_TCH_HO_BETTERCELL_ATPT
Descripton

Long Name NB_ADJ_SCELL_OUT_TCH_HO_BETTERCELL_ATPT

Definition Number of outgoing external and internal inter-cell TCH (in HR or FR usage) handover attempts with better
cell cause. This counter takes into 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 12, 14, 21 on a TCH channel, from the fixed serving cell to the
variable target cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 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 --
Feature Name B7.1 counters improvements

C727 - NB_ADJ_SCELL_OUT_TCH_HO_TRAFFIC_ATPT
Descripton

Long Name NB_ADJ_SCELL_OUT_TCH_HO_TRAFFIC_ATPT


Definition Number of outgoing external and internal inter-cell TCH (in HR or FR usage) handover attempts with traffic
cause. This counter takes into account 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 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 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 29-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency C727 - NB_ADJ_SCELL_OUT_TCH_HO_TRAFFIC_ATPT
Fixed serving Cell
....................................................................................................................................................................................................................................

Feature Name B7.1 counters improvements

C728 - NB_ADJ_SCELL_OUT_ FORCED_DR_ATPT


Descripton

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 or Cause 36 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 TCH outgoing handover per adjacency measurements
Type Definition Set of counters related to outgoing TCH handover provided per adjacency.
External Comment --
Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
29-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency C728 - NB_ADJ_SCELL_OUT_ FORCED_DR_ATPT

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 29-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency C728 - NB_ADJ_SCELL_OUT_ FORCED_DR_ATPT

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
29-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XV: BSC-TYPE 27 - 2G TCH
incoming handover per
adjacency measurements

Overview
Purpose
All type 27.

Contents

Chapter 30, Adjacency 30-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XV-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 27 - 2G TCH incoming handover per adjacency Overview
measurements
....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XV-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
30 Adjacency
30

Fixed target Cell

Overview
Purpose
This section contains Fixed target Cell parameters.

Contents

C730 - NB_ADJ_TCELL_INC_TCH_HO_ATPT 30-2


C731 - NB_ADJ_TCELL_INC_TCH_HO_SUCC 30-2
C733 - NB_ADJ_TCELL_INC_TCH_HO_EXEC_FAIL_MS_ACC 30-3
C734 - NB_ADJ_TCELL_INC_TCH_HO_EMERGENCY_ATPT 30-4
C735 - NB_ADJ_TCELL_INC_TCH_HO_BETTERCELL_ATPT 30-4
C737 - NB_ADJ_TCELL_INC_TCH_HO_TRAFFIC_ATPT 30-5
C738 - NB_ADJ_TCELL_INC_FORCED_DR_ATPT 30-6
C753 - NB_ADJ_TCELL_INC_TCH_HO_OTHER_ATPT 30-7

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 30-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency C730 - NB_ADJ_TCELL_INC_TCH_HO_ATPT
Fixed target Cell
....................................................................................................................................................................................................................................

C730 - NB_ADJ_TCELL_INC_TCH_HO_ATPT
Descripton

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 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 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 --
Feature Name --

C731 - NB_ADJ_TCELL_INC_TCH_HO_SUCC
Descripton

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

....................................................................................................................................................................................................................................
30-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency C731 - NB_ADJ_TCELL_INC_TCH_HO_SUCC
Fixed target Cell
....................................................................................................................................................................................................................................

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

Feature Name --

C733 - NB_ADJ_TCELL_INC_TCH_HO_EXEC_FAIL_MS_ACC
Descripton

Long Name NB_ADJ_TCELL_INC_TCH_HO_EXEC_FAIL_MS_ACC

Definition Number of incoming 2G to 2G external and internal inter-cell TCH (in HR or FR 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: 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 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 --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 30-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency C734 - NB_ADJ_TCELL_INC_TCH_HO_EMERGENCY_ATPT
Fixed target Cell
....................................................................................................................................................................................................................................

C734 - NB_ADJ_TCELL_INC_TCH_HO_EMERGENCY_ATPT
Descripton

Long Name NB_ADJ_TCELL_INC_TCH_HO_EMERGENCY_ATPT

Definition Number of incoming 2G to 2G external and internal inter-cell TCH (in HR or FR 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 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 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 --
Feature Name B7.1 counters improvements

C735 - NB_ADJ_TCELL_INC_TCH_HO_BETTERCELL_ATPT
Descripton

Long Name NB_ADJ_TCELL_INC_TCH_HO_BETTERCELL_ATPT

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

....................................................................................................................................................................................................................................
30-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency C735 - NB_ADJ_TCELL_INC_TCH_HO_BETTERCELL_ATPT
Fixed target Cell
....................................................................................................................................................................................................................................

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 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 --
Feature Name Support of TFO (Tandem Free Operation)

C737 - NB_ADJ_TCELL_INC_TCH_HO_TRAFFIC_ATPT
Descripton

Long Name NB_ADJ_TCELL_INC_TCH_HO_TRAFFIC_ATPT


Definition Number of incoming 2G to 2G external and internal inter-cell TCH (in HR or FR usage) handover attempts,
with traffic 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 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 2G TCH incoming handover per adjacency measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 30-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency C737 - NB_ADJ_TCELL_INC_TCH_HO_TRAFFIC_ATPT
Fixed target Cell
....................................................................................................................................................................................................................................

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 --
Feature Name B7.1 counters improvements

C738 - NB_ADJ_TCELL_INC_FORCED_DR_ATPT
Descripton

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 or Cause 36
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 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 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 --

Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
30-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency C753 - NB_ADJ_TCELL_INC_TCH_HO_OTHER_ATPT
Fixed target Cell
....................................................................................................................................................................................................................................

C753 - NB_ADJ_TCELL_INC_TCH_HO_OTHER_ATPT
Descripton

Long Name NB_ADJ_TCELL_INC_TCH_HO_OTHER_ATPT

Definition Number of incoming 2G to 2G external and internal inter-cell TCH (in HR or FR usage) handover attempts,
with unknown or missing 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 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 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 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 --
Feature Name Support of TFO (Tandem Free Operation)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 30-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency C753 - NB_ADJ_TCELL_INC_TCH_HO_OTHER_ATPT

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
30-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XVI: BSC-TYPE 28 - SDCCH
handover

Overview
Purpose
All type 28.

Contents

Chapter 31, Handover 31-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XVI-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 28 - SDCCH handover Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XVI-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
31 Handover
31

SDCCH

Overview
Purpose
This section contains SDCCH parameters.

Contents

C100 - NB_OUT_INT_SDCCH_HO_ATPT 31-3


C101 - NB_INTRA_SDCCH_HO_PREP_FAIL_CONG 31-3
C102 - NB_INTRA_SDCCH_HO_SUCC 31-4
C103 - NB_INTRA_SDCCH_HO_EXEC_FAIL_NO_REV 31-4
C107 - NB_INTRA_SDCCH_HO_EXEC_FAIL_REV 31-5
C115 - NB_SDCCH_HO_MSC_TRIG 31-5
C310 - NB_INC_EXT_SDCCH_HO_REQ 31-6
C311 - NB_INC_EXT_SDCCH_HO_ATPT 31-6
C330 - NB_INC_INT_SDCCH_HO_REQ 31-7
C331 - NB_INC_INT_SDCCH_HO_ATPT 31-7
C360 - NB_INTRA_SDCCH_HO_REQ 31-8
C361 - NB_INTRA_SDCCH_HO_ATPT 31-8
C445 - NB_SDCCH_HO_ATPT_23_TrafHandover 31-9
C446 - NB_SDCCH_HO_ATPT_24_GenCaptureHandover 31-10
C454 - NB_SDCCH_HO_ATPT_22_TooShortDistance 31-10
C510 - NB_SDCCH_HO_ATPT_2_TooLowQualUp 31-11

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 31-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover Overview
SDCCH
....................................................................................................................................................................................................................................

C511 - NB_SDCCH_HO_ATPT_3_TooLowLevUp 31-11


C512 - NB_SDCCH_HO_ATPT_4_TooLowQualDown 31-12
C513 - NB_SDCCH_HO_ATPT_5_TooLowLevDown 31-12
C514 - NB_SDCCH_HO_ATPT_6_TooLongDistance 31-13
C516 - NB_SDCCH_HO_ATPT_15_TooHighLevInterfUp 31-14
C517 - NB_SDCCH_HO_ATPT_16_TooHighLevInterfDown 31-14
C518 - NB_SDCCH_HO_ATPT_12_TooLowPowBudg 31-15
C519 - NB_SDCCH_HO_ATPT_21_HighLevNeigCellPrefBand 31-15
C605a - NB_SDCCH_HO_ATPT_7_ConsBadSACCHmicroCell 31-16
C605d - NB_SDCCH_HO_ATPT_17_TooLowLevUpMicroCell 31-16
C605e - NB_SDCCH_HO_ATPT_18_TooLowLevDownMicroCell 31-17
C605f - NB_SDCCH_HO_ATPT_14_HighLevNeigLowCellSlowMS 31-17
C607 - NB_SDCCH_HO_ATPT_20_HighLevNeigCellForcDR 31-18
C81 - NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG 31-19
C82 - NB_INC_EXT_SDCCH_HO_SUCC 31-19
C83 - NB_INC_EXT_SDCCH_HO_EXEC_FAIL_MS_ACCESS 31-20
C85a - NB_OUT_EXT_SDCCH_REAL_HO_REQ 31-20
C86 - NB_OUT_EXT_SDCCH_HO_SUCC 31-21
C87 - NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_REV 31-22
C88 - NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_NO_REV 31-22
C90 - NB_OUT_EXT_SDCCH_HO_ATPT 31-23
C91 - NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG 31-23
C92 - NB_INC_INT_SDCCH_HO_SUCC 31-24
C93 - NB_INC_INT_SDCCH_HO_EXEC_FAIL_MS_ACCESS 31-25
C95a - NB_OUT_INT_SDCCH_HO_REQ 31-25
C96 - NB_OUT_INT_SDCCH_HO_SUCC 31-26
C97 - NB_OUT_INT_SDCCH_HO_EXEC_FAIL_REV 31-26
C98 - NB_OUT_INT_SDCCH_HO_EXEC_FAIL_NO_REV 31-27

....................................................................................................................................................................................................................................
31-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C100 - NB_OUT_INT_SDCCH_HO_ATPT
SDCCH
....................................................................................................................................................................................................................................

C100 - NB_OUT_INT_SDCCH_HO_ATPT
Descripton

Long Name NB_OUT_INT_SDCCH_HO_ATPT

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


Trigger condition Whenever the 44.018 HANDOVER COMMAND message is sent on Abis 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 Set of counters related to SDCCH 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 --
Feature Name --

C101 - NB_INTRA_SDCCH_HO_PREP_FAIL_CONG
Descripton

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 there is no free SDCCH
Sub-channel to allocate the handover to.

Sub Domain 1 SDCCH


Sub Domain 2 Intra

Sub Domain 3 --

Measured Object Common cell


Type Name SDCCH handover
Type Definition Set of counters related to SDCCH 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 --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 31-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C102 - NB_INTRA_SDCCH_HO_SUCC
SDCCH
....................................................................................................................................................................................................................................

C102 - NB_INTRA_SDCCH_HO_SUCC
Descripton

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 Set of counters related to SDCCH 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 --
Feature Name --

C103 - NB_INTRA_SDCCH_HO_EXEC_FAIL_NO_REV
Descripton

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 Set of counters related to SDCCH 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 --
Feature Name --

....................................................................................................................................................................................................................................
31-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C107 - NB_INTRA_SDCCH_HO_EXEC_FAIL_REV
SDCCH
....................................................................................................................................................................................................................................

C107 - NB_INTRA_SDCCH_HO_EXEC_FAIL_REV
Descripton

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 Set of counters related to SDCCH 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 --
Feature Name --

C115 - NB_SDCCH_HO_MSC_TRIG
Descripton

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 counter counts both inter-PLMN and intra-PLMN handover events.
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 provided per handover category :
incoming and outgoing, internal (inter-cell and intra-cell) and external. The handover causes are also
provided.
External Comment --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 31-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C115 - NB_SDCCH_HO_MSC_TRIG
SDCCH
....................................................................................................................................................................................................................................

Feature Name --

C310 - NB_INC_EXT_SDCCH_HO_REQ
Descripton

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 intra-PLMN handover events.
Sub Domain 1 SDCCH

Sub Domain 2 Incoming External


Sub Domain 3 --

Measured Object Common cell


Type Name SDCCH handover
Type Definition Set of counters related to SDCCH 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 --
Feature Name --

C311 - NB_INC_EXT_SDCCH_HO_ATPT
Descripton

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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1 SDCCH

Sub Domain 2 Incoming External

Sub Domain 3 --
Measured Object Common cell

Type Name SDCCH handover

....................................................................................................................................................................................................................................
31-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C311 - NB_INC_EXT_SDCCH_HO_ATPT
SDCCH
....................................................................................................................................................................................................................................

Type Definition Set of counters related to SDCCH 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 --
Feature Name --

C330 - NB_INC_INT_SDCCH_HO_REQ
Descripton

Long Name NB_INC_INT_SDCCH_HO_REQ

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


Trigger condition Whenever the BSC process responsible for the handover procedure selects a 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 Set of counters related to SDCCH 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 --
Feature Name --

C331 - NB_INC_INT_SDCCH_HO_ATPT
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 31-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C331 - NB_INC_INT_SDCCH_HO_ATPT
SDCCH
....................................................................................................................................................................................................................................

Type Name SDCCH handover

Type Definition Set of counters related to SDCCH 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 --

Feature Name --

C360 - NB_INTRA_SDCCH_HO_REQ
Descripton

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 Set of counters related to SDCCH 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 --
Feature Name --

C361 - NB_INTRA_SDCCH_HO_ATPT
Descripton

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

....................................................................................................................................................................................................................................
31-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C361 - NB_INTRA_SDCCH_HO_ATPT
SDCCH
....................................................................................................................................................................................................................................

Type Name SDCCH handover

Type Definition Set of counters related to SDCCH 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 --

Feature Name --

C445 - NB_SDCCH_HO_ATPT_23_TrafHandover
Descripton

Long Name NB_SDCCH_HO_ATPT_23_TrafHandover


Definition Number of inter-cell internal or external handover attempts, with the cause 23: "traffic handover" on
SDCCH. This counter counts also the directed retries.
Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 23 on
SDCCH. This counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
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 provided per handover category :
incoming and outgoing, internal (inter-cell and intra-cell) and external. The handover causes are also
provided.

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 31-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C446 - NB_SDCCH_HO_ATPT_24_GenCaptureHandover
SDCCH
....................................................................................................................................................................................................................................

C446 - NB_SDCCH_HO_ATPT_24_GenCaptureHandover
Descripton

Long Name NB_SDCCH_HO_ATPT_24_GenCaptureHandover

Definition Number of inter-cell internal or external handover attempts, with the cause 24: "general capture handover"
on SDCCH. This counter counts also the directed retries.
Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 24 on
SDCCH. This counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
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 provided per handover category :
incoming and outgoing, internal (inter-cell and intra-cell) and external. The handover causes are also
provided.

External Comment --
Feature Name --

C454 - NB_SDCCH_HO_ATPT_22_TooShortDistance
Descripton

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 because of cause 22 on
SDCCH. This counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.

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 provided per handover category :
incoming and outgoing, internal (inter-cell and intra-cell) and external. The handover causes are also
provided.

....................................................................................................................................................................................................................................
31-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C454 - NB_SDCCH_HO_ATPT_22_TooShortDistance
SDCCH
....................................................................................................................................................................................................................................

External Comment --

Feature Name --

C510 - NB_SDCCH_HO_ATPT_2_TooLowQualUp
Descripton

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 Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS 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 Set of counters related to SDCCH 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 --
Feature Name --

C511 - NB_SDCCH_HO_ATPT_3_TooLowLevUp
Descripton

Long Name NB_SDCCH_HO_ATPT_3_TooLowLevUp

Definition Number of SDCCH inter-cell internal or external handover attempts with cause 3: "uplink level too low".
Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 3. This counter
is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 --
Measured Object Common cell
Type Name SDCCH handover

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 31-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C511 - NB_SDCCH_HO_ATPT_3_TooLowLevUp
SDCCH
....................................................................................................................................................................................................................................

Type Definition Set of counters related to SDCCH 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 --
Feature Name --

C512 - NB_SDCCH_HO_ATPT_4_TooLowQualDown
Descripton

Long Name NB_SDCCH_HO_ATPT_4_TooLowQualDown

Definition Number of SDCCH inter-cell internal or external handover attempts with cause 4: "downlink quality too
low".
Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 4. This counter
is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
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 provided per handover category :
incoming and outgoing, internal (inter-cell and intra-cell) and external. The handover causes are also
provided.

External Comment --
Feature Name --

C513 - NB_SDCCH_HO_ATPT_5_TooLowLevDown
Descripton

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 Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 5. This counter
is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 SDCCH

....................................................................................................................................................................................................................................
31-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C513 - NB_SDCCH_HO_ATPT_5_TooLowLevDown
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 provided per handover category :
incoming and outgoing, internal (inter-cell and intra-cell) and external. The handover causes are also
provided.

External Comment --

Feature Name --

C514 - NB_SDCCH_HO_ATPT_6_TooLongDistance
Descripton

Long Name NB_SDCCH_HO_ATPT_6_TooLongDistance


Definition Number of SDCCH inter-cell internal or external handover attempts with cause 6: "MS-BTS distance too
long".
Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 6. This counter
is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.

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 provided per handover category :
incoming and outgoing, internal (inter-cell and intra-cell) and external. The handover causes are also
provided.
External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 31-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C516 - NB_SDCCH_HO_ATPT_15_TooHighLevInterfUp
SDCCH
....................................................................................................................................................................................................................................

C516 - NB_SDCCH_HO_ATPT_15_TooHighLevInterfUp
Descripton

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 Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 15.

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 provided per handover category :
incoming and outgoing, internal (inter-cell and intra-cell) and external. The handover causes are also
provided.
External Comment --

Feature Name --

C517 - NB_SDCCH_HO_ATPT_16_TooHighLevInterfDown
Descripton

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 Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 16.
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 provided per handover category :
incoming and outgoing, internal (inter-cell and intra-cell) and external. The handover causes are also
provided.
External Comment --

Feature Name --

....................................................................................................................................................................................................................................
31-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C518 - NB_SDCCH_HO_ATPT_12_TooLowPowBudg
SDCCH
....................................................................................................................................................................................................................................

C518 - NB_SDCCH_HO_ATPT_12_TooLowPowBudg
Descripton

Long Name NB_SDCCH_HO_ATPT_12_TooLowPowBudg

Definition Number of SDCCH inter-cell internal or external handover attempts with cause 12: "too low power budget".
Trigger condition Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTS because of cause 12. This
counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
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 provided per handover category :
incoming and outgoing, internal (inter-cell and intra-cell) and external. The handover causes are also
provided.

External Comment --
Feature Name --

C519 - NB_SDCCH_HO_ATPT_21_HighLevNeigCellPrefBand
Descripton

Long Name NB_SDCCH_HO_ATPT_21_HighLevNeigCellPrefBand


Definition Number of SDCCH inter-cell internal or external handover attempts with cause 21: "high level in neighbour
cell in the preferred band". This counter is related to multiband.
Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 21. This
counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.

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 provided per handover category :
incoming and outgoing, internal (inter-cell and intra-cell) and external. The handover causes are also
provided.
External Comment --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 31-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C519 - NB_SDCCH_HO_ATPT_21_HighLevNeigCellPrefBand
SDCCH
....................................................................................................................................................................................................................................

Feature Name --

C605a - NB_SDCCH_HO_ATPT_7_ConsBadSACCHmicroCell
Descripton

Long Name NB_SDCCH_HO_ATPT_7_ConsBadSACCHmicroCell

Definition Number of SDCCH inter-cell internal or external handover attempts with cause 7: "several consecutive bad
SACCH frames received in a micro cell". This counter is related to micro cell environment.
Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 7. This counter
is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
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 provided per handover category :
incoming and outgoing, internal (inter-cell and intra-cell) and external. The handover causes are also
provided.

External Comment --
Feature Name --

C605d - NB_SDCCH_HO_ATPT_17_TooLowLevUpMicroCell
Descripton

Long Name NB_SDCCH_HO_ATPT_17_TooLowLevUpMicroCell

Definition Number of SDCCH inter-cell internal or external handover attempts with cause 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 Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 17. This
counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1 SDCCH

Sub Domain 2 Cause

Sub Domain 3 --
Measured Object Common cell

Type Name SDCCH handover

....................................................................................................................................................................................................................................
31-16 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C605d - NB_SDCCH_HO_ATPT_17_TooLowLevUpMicroCell
SDCCH
....................................................................................................................................................................................................................................

Type Definition Set of counters related to SDCCH 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 --
Feature Name --

C605e - NB_SDCCH_HO_ATPT_18_TooLowLevDownMicroCell
Descripton

Long Name NB_SDCCH_HO_ATPT_18_TooLowLevDownMicroCell

Definition Number of SDCCH inter-cell internal or external handover attempts with cause 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 Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 18. This
counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
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 provided per handover category :
incoming and outgoing, internal (inter-cell and intra-cell) and external. The handover causes are also
provided.

External Comment --
Feature Name --

C605f - NB_SDCCH_HO_ATPT_14_HighLevNeigLowCellSlowMS
Descripton

Long Name NB_SDCCH_HO_ATPT_14_HighLevNeigLowCellSlowMS


Definition Number of SDCCH inter-cell internal or external handover attempts with cause 14: "high level in neighbour
lower layer cell for slow mobile". This counter is related to micro cell environment.
Trigger condition Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTS because of cause 14. This
counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 SDCCH

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 31-17
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C605f -
SDCCH NB_SDCCH_HO_ATPT_14_HighLevNeigLowCellSlowMS
....................................................................................................................................................................................................................................

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 provided per handover category :
incoming and outgoing, internal (inter-cell and intra-cell) and external. The handover causes are also
provided.

External Comment --

Feature Name --

C607 - NB_SDCCH_HO_ATPT_20_HighLevNeigCellForcDR
Descripton

Long Name NB_SDCCH_HO_ATPT_20_HighLevNeigCellForcDR


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

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

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 provided per handover category :
incoming and outgoing, internal (inter-cell and intra-cell) and external. The handover causes are also
provided.

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
31-18 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C81 - NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG
SDCCH
....................................................................................................................................................................................................................................

C81 - NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG
Descripton

Long Name NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG

Definition MC81=C81, Number of incoming external SDCCH handover -preparation 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 SDCCH handover.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1 SDCCH

Sub Domain 2 Incoming External


Sub Domain 3 --

Measured Object Common cell


Type Name SDCCH handover

Type Definition Set of counters related to SDCCH 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 --
Feature Name --

C82 - NB_INC_EXT_SDCCH_HO_SUCC
Descripton

Long Name NB_INC_EXT_SDCCH_HO_SUCC


Definition Number of incoming external SDCCH handover successes.

Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abis 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 intra-PLMN handover events.

Sub Domain 1 SDCCH


Sub Domain 2 Incoming External

Sub Domain 3 --
Measured Object Common cell

Type Name SDCCH handover


Type Definition Set of counters related to SDCCH 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 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 31-19
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C82 - NB_INC_EXT_SDCCH_HO_SUCC
SDCCH
....................................................................................................................................................................................................................................

Feature Name --

C83 - NB_INC_EXT_SDCCH_HO_EXEC_FAIL_MS_ACCESS
Descripton

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 1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a 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 intra-PLMN handover events.
Sub Domain 1 SDCCH

Sub Domain 2 Incoming External


Sub Domain 3 --

Measured Object Common cell


Type Name SDCCH handover

Type Definition Set of counters related to SDCCH 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 --

Feature Name --

C85a - NB_OUT_EXT_SDCCH_REAL_HO_REQ
Descripton

Long Name NB_OUT_EXT_SDCCH_REAL_HO_REQ

Definition Number of outgoing external SDCCH handover requests.

....................................................................................................................................................................................................................................
31-20 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C85a - NB_OUT_EXT_SDCCH_REAL_HO_REQ
SDCCH
....................................................................................................................................................................................................................................

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 Set of counters related to SDCCH 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 --

Feature Name B7.1 counters improvements

C86 - NB_OUT_EXT_SDCCH_HO_SUCC
Descripton

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 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 Set of counters related to SDCCH 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 --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 31-21
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C87 - NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_REV
SDCCH
....................................................................................................................................................................................................................................

C87 - NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_REV
Descripton

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 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 Set of counters related to SDCCH 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 --
Feature Name --

C88 - NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_NO_REV
Descripton

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 Whenever the timer supervising the handover procedure on the serving cell (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

....................................................................................................................................................................................................................................
31-22 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C88 - NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_NO_REV
SDCCH
....................................................................................................................................................................................................................................

Type Definition Set of counters related to SDCCH 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 --
Feature Name --

C90 - NB_OUT_EXT_SDCCH_HO_ATPT
Descripton

Long Name NB_OUT_EXT_SDCCH_HO_ATPT

Definition Number of outgoing external SDCCH handover attempts.


Trigger condition Whenever the 44.018 HANDOVER COMMAND message is sent on Abis 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 Set of counters related to SDCCH 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 --
Feature Name --

C91 - NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG
Descripton

Long Name NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG


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

Trigger condition Whenever a internal inter-cell SDCCH handover cannot be performed, 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 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 31-23
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C91 - NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG
SDCCH
....................................................................................................................................................................................................................................

Measured Object Common cell

Type Name SDCCH handover


Type Definition Set of counters related to SDCCH 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 --
Feature Name --

C92 - NB_INC_INT_SDCCH_HO_SUCC
Descripton

Long Name NB_INC_INT_SDCCH_HO_SUCC


Definition Number of incoming internal inter-cell SDCCH handover successes.
Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abis 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 Set of counters related to SDCCH 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 --
Feature Name --

....................................................................................................................................................................................................................................
31-24 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C93 - NB_INC_INT_SDCCH_HO_EXEC_FAIL_MS_ACCESS
SDCCH
....................................................................................................................................................................................................................................

C93 - NB_INC_INT_SDCCH_HO_EXEC_FAIL_MS_ACCESS
Descripton

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 Set of counters related to SDCCH 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 --
Feature Name --

C95a - NB_OUT_INT_SDCCH_HO_REQ
Descripton

Long Name NB_OUT_INT_SDCCH_HO_REQ


Definition Number of outgoing internal inter-cell SDCCH handover requests.
Trigger condition Whenever the BSC process responsible for the handover procedure selects a 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 Set of counters related to SDCCH 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 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 31-25
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C95a - NB_OUT_INT_SDCCH_HO_REQ
SDCCH
....................................................................................................................................................................................................................................

Feature Name --

C96 - NB_OUT_INT_SDCCH_HO_SUCC
Descripton

Long Name NB_OUT_INT_SDCCH_HO_SUCC

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


Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abis 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 Set of counters related to SDCCH 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 --
Feature Name --

C97 - NB_OUT_INT_SDCCH_HO_EXEC_FAIL_REV
Descripton

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 Set of counters related to SDCCH 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.

....................................................................................................................................................................................................................................
31-26 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C97 - NB_OUT_INT_SDCCH_HO_EXEC_FAIL_REV
SDCCH
....................................................................................................................................................................................................................................

External Comment --

Feature Name --

C98 - NB_OUT_INT_SDCCH_HO_EXEC_FAIL_NO_REV
Descripton

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 Set of counters related to SDCCH 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 --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 31-27
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C98 - NB_OUT_INT_SDCCH_HO_EXEC_FAIL_NO_REV

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
31-28 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XVII: BSC-TYPE 29 -
Directed retry
measurements

Overview
Purpose
All type 29.

Contents

Chapter 32, Handover 32-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XVII-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 29 - Directed retry measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XVII-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
32 Handover
32

Directed Retry

Overview
Purpose
This section contains Directed Retry parameters.

Contents

C142a - NB_OUT_FORCED_IDR_SUCC 32-2


C142b - NB_OUT_FORCED_EDR_SUCC 32-3
C142c - NB_OUT_NOR_IDR_SUCC 32-3
C142d - NB_OUT_NOR_EDR_SUCC 32-4
C143a - NB_OUT_FORCED_IDR_EXEC_FAIL_REV 32-4
C143b - NB_OUT_FORCED_IDR_EXEC_FAIL_NO_REV 32-5
C143c - NB_OUT_FORCED_EDR_EXEC_FAIL_REV 32-5
C143d - NB_OUT_FORCED_EDR_EXEC_FAIL_NO_REV 32-6
C143e - NB_OUT_NOR_IDR_EXEC_FAIL_REV 32-6
C143f - NB_OUT_NOR_IDR_EXEC_FAIL_NO_REV 32-7
C143g - NB_OUT_NOR_EDR_EXEC_FAIL_REV 32-7
C143h - NB_OUT_NOR_EDR_EXEC_FAIL_NO_REV 32-8
C144a - NB_OUT_FORCED_IDR_REQ 32-8
C144b - NB_OUT_FORCED_EDR_REQ 32-9
C144c - NB_OUT_NOR_IDR_REQ 32-9
C144d - NB_OUT_NOR_EDR_REQ 32-10

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 32-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover Overview
Directed Retry
....................................................................................................................................................................................................................................

C145a - NB_OUT_FORCED_IDR_ATPT 32-10


C145b - NB_OUT_FORCED_EDR_ATPT 32-11
C145c - NB_OUT_NOR_IDR_ATPT 32-11
C145d - NB_OUT_NOR_EDR_ATPT 32-12
C151 - NB_INC_IDR_SUCC (29) 32-12
C152 - NB_INC_IDR_EXEC_FAIL_MS_ACCESS 32-13
C153 - NB_INC_IDR_REQ 32-13
C154 - NB_INC_IDR_ATPT 32-14
C555 - NB_INC_IDR_PREP_FAIL_CONG_R_ABIS 32-14

C142a - NB_OUT_FORCED_IDR_SUCC
Descripton

Long Name NB_OUT_FORCED_IDR_SUCC


Definition Number of outgoing forced internal directed retry (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
internal directed retry procedure.
Sub Domain 1 Directed Retry

Sub Domain 2 Internal


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 --
Feature Name --

....................................................................................................................................................................................................................................
32-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C142b - NB_OUT_FORCED_EDR_SUCC
Directed Retry
....................................................................................................................................................................................................................................

C142b - NB_OUT_FORCED_EDR_SUCC
Descripton

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 --
Feature Name --

C142c - NB_OUT_NOR_IDR_SUCC
Descripton

Long Name NB_OUT_NOR_IDR_SUCC


Definition Number of outgoing normal internal directed retry (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 normal
internal directed retry procedure.

Sub Domain 1 Directed Retry

Sub Domain 2 Internal


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

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 32-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C142d - NB_OUT_NOR_EDR_SUCC
Directed Retry
....................................................................................................................................................................................................................................

C142d - NB_OUT_NOR_EDR_SUCC
Descripton

Long Name NB_OUT_NOR_EDR_SUCC

Definition Number of outgoing normal external directed retry (towards a TCH channel in HR or FR usage) successes.
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 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 --
Feature Name --

C143a - NB_OUT_FORCED_IDR_EXEC_FAIL_REV
Descripton

Long Name NB_OUT_FORCED_IDR_EXEC_FAIL_REV


Definition Number of outgoing forced internal 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 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 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 --

Feature Name --

....................................................................................................................................................................................................................................
32-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C143b - NB_OUT_FORCED_IDR_EXEC_FAIL_NO_REV
Directed Retry
....................................................................................................................................................................................................................................

C143b - NB_OUT_FORCED_IDR_EXEC_FAIL_NO_REV
Descripton

Long Name NB_OUT_FORCED_IDR_EXEC_FAIL_NO_REV

Definition Number of outgoing forced internal directed retry -execution failures due to MS access problem without
reversion to the old channel. The target TCH channel can be in HR or FR usage.
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 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 --

Feature Name --

C143c - NB_OUT_FORCED_EDR_EXEC_FAIL_REV
Descripton

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 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 --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 32-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C143d - NB_OUT_FORCED_EDR_EXEC_FAIL_NO_REV
Directed Retry
....................................................................................................................................................................................................................................

C143d - NB_OUT_FORCED_EDR_EXEC_FAIL_NO_REV
Descripton

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 can be in HR or FR usage.
Trigger condition Whenever the timer supervising the handover procedure (T8) expires during 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 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 --
Feature Name --

C143e - NB_OUT_NOR_IDR_EXEC_FAIL_REV
Descripton

Long Name NB_OUT_NOR_IDR_EXEC_FAIL_REV


Definition Number of outgoing normal internal 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 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 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 --

Feature Name --

....................................................................................................................................................................................................................................
32-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C143f - NB_OUT_NOR_IDR_EXEC_FAIL_NO_REV
Directed Retry
....................................................................................................................................................................................................................................

C143f - NB_OUT_NOR_IDR_EXEC_FAIL_NO_REV
Descripton

Long Name NB_OUT_NOR_IDR_EXEC_FAIL_NO_REV

Definition Number of outgoing normal internal directed retry -execution failures due to MS access problem without
reversion to the old channel. The target TCH channel can be in HR or FR usage.
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 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 --

Feature Name --

C143g - NB_OUT_NOR_EDR_EXEC_FAIL_REV
Descripton

Long Name NB_OUT_NOR_EDR_EXEC_FAIL_REV


Definition Number of outgoing normal 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 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 --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 32-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C143h - NB_OUT_NOR_EDR_EXEC_FAIL_NO_REV
Directed Retry
....................................................................................................................................................................................................................................

C143h - NB_OUT_NOR_EDR_EXEC_FAIL_NO_REV
Descripton

Long Name NB_OUT_NOR_EDR_EXEC_FAIL_NO_REV

Definition Number of outgoing normal external directed retry -execution failures due to MS access problem without
reversion to the old channel. The target TCH channel can be in HR or FR usage.
Trigger condition Whenever the timer supervising the handover procedure (T8) expires during 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 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 --
Feature Name --

C144a - NB_OUT_FORCED_IDR_REQ
Descripton

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

Feature Name --

....................................................................................................................................................................................................................................
32-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C144b - NB_OUT_FORCED_EDR_REQ
Directed Retry
....................................................................................................................................................................................................................................

C144b - NB_OUT_FORCED_EDR_REQ
Descripton

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 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 --
Feature Name --

C144c - NB_OUT_NOR_IDR_REQ
Descripton

Long Name NB_OUT_NOR_IDR_REQ


Definition Number of outgoing normal internal directed retry requests. The target TCH channel can be in HR or FR
usage.
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 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 --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 32-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C144d - NB_OUT_NOR_EDR_REQ
Directed Retry
....................................................................................................................................................................................................................................

C144d - NB_OUT_NOR_EDR_REQ
Descripton

Long Name NB_OUT_NOR_EDR_REQ

Definition Number of outgoing normal 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 normal external directed retry from
the serving cell.
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 --
Feature Name --

C145a - NB_OUT_FORCED_IDR_ATPT
Descripton

Long Name NB_OUT_FORCED_IDR_ATPT


Definition Number of outgoing forced internal directed retry attempts. The target TCH channel can be in HR or FR
usage.
Trigger condition Whenever a 44.018HANDOVER COMMAND is sent to the MS via the serving 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 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 --

Feature Name --

....................................................................................................................................................................................................................................
32-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C145b - NB_OUT_FORCED_EDR_ATPT
Directed Retry
....................................................................................................................................................................................................................................

C145b - NB_OUT_FORCED_EDR_ATPT
Descripton

Long Name NB_OUT_FORCED_EDR_ATPT

Definition Number of outgoing forced external directed retry attempts. The target TCH channel can be in HR or FR
usage.
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 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 --
Feature Name --

C145c - NB_OUT_NOR_IDR_ATPT
Descripton

Long Name NB_OUT_NOR_IDR_ATPT


Definition Number of outgoing normal internal directed retry attempts. The target TCH channel can be in HR or FR
usage.
Trigger condition Whenever a 44.018HANDOVER COMMAND is sent to the MS via the serving 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 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 --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 32-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C145d - NB_OUT_NOR_EDR_ATPT
Directed Retry
....................................................................................................................................................................................................................................

C145d - NB_OUT_NOR_EDR_ATPT
Descripton

Long Name NB_OUT_NOR_EDR_ATPT

Definition Number of outgoing normal external directed retry attempts. The target TCH channel can be in HR or FR
usage.
Trigger condition Whenever a 44.018HANDOVER COMMAND is sent to the MS via the serving 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 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 --
Feature Name --

C151 - NB_INC_IDR_SUCC (29)


Descripton

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

Feature Name --

....................................................................................................................................................................................................................................
32-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C152 - NB_INC_IDR_EXEC_FAIL_MS_ACCESS
Directed Retry
....................................................................................................................................................................................................................................

C152 - NB_INC_IDR_EXEC_FAIL_MS_ACCESS
Descripton

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 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 --
Feature Name --

C153 - NB_INC_IDR_REQ
Descripton

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 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 --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 32-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C154 - NB_INC_IDR_ATPT
Directed Retry
....................................................................................................................................................................................................................................

C154 - NB_INC_IDR_ATPT
Descripton

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 Whenever a 44.018HANDOVER COMMAND is sent to the MS via the serving 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 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 --

Feature Name --

C555 - NB_INC_IDR_PREP_FAIL_CONG_R_ABIS
Descripton

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 can be in HR or FR usage.

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

....................................................................................................................................................................................................................................
32-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C555 - NB_INC_IDR_PREP_FAIL_CONG_R_ABIS
Directed Retry
....................................................................................................................................................................................................................................

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 --
Feature Name Enhanced Transmission Resource management

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 32-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover C555 - NB_INC_IDR_PREP_FAIL_CONG_R_ABIS

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
32-16 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XVIII: BSC-TYPE 30 - SMS CB
measurements

Overview
Purpose
All type 30.

Contents

Chapter 33, Quality of Service 33-1


Chapter 34, Traffic Load 34-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XVIII-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 30 - SMS CB measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XVIII-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
33 Quality of Service
33

Short Message Service

Overview
Purpose
This section contains Short Message Service parameters.

Contents

CB603 - NB_SMS_CB_FAIL_IND 33-1


CB604 - NB_SMS_CB_WRITE_REP_KILL_MESS_REJ 33-2

CB603 - NB_SMS_CB_FAIL_IND
Descripton

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 Short Message Service


Sub Domain 2 Cell Broadcast

Sub Domain 3 Failure

Measured Object BSC


Type Name SMS CB measurements

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 33-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service CB603 - NB_SMS_CB_FAIL_IND
Short Message Service
....................................................................................................................................................................................................................................

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

External Comment --
Feature Name --

CB604 - NB_SMS_CB_WRITE_REP_KILL_MESS_REJ
Descripton

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 Short Message Service


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 --
Feature Name --

....................................................................................................................................................................................................................................
33-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
34 Traffic Load
34

Telecom Procedure (Traffic Load)

Overview
Purpose
This section contains Telecom Procedure (Traffic Load) parameters.

Contents

CB601 - NB_SMSCB_WRITE_REPL_SUCC 34-1


CB602 - NB_SMSCB_KILL_MESS_SUCC 34-2

CB601 - NB_SMSCB_WRITE_REPL_SUCC
Descripton

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.

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 34-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load CB601 - NB_SMSCB_WRITE_REPL_SUCC
Telecom Procedure (Traffic Load)
....................................................................................................................................................................................................................................

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 Telecom Procedure (Traffic Load)


Sub Domain 2 Short Message Service

Sub Domain 3 Cell Broadcast


Measured Object BSC

Type Name SMS CB measurements

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

Feature Name --

CB602 - NB_SMSCB_KILL_MESS_SUCC
Descripton

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 Telecom Procedure (Traffic Load)


Sub Domain 2 Short Message Service

Sub Domain 3 Cell Broadcast

Measured Object BSC


Type Name SMS CB measurements
Type Definition Set of counters related to the Short Message Service Cell Broadcast.

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
34-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load CB602 - NB_SMSCB_KILL_MESS_SUCC

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 34-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load CB602 - NB_SMSCB_KILL_MESS_SUCC

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
34-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XIX: BSC-TYPE 31 - RMS
(Radio Measurement
Statistics)

Overview
Purpose
All type 31.

Contents

Chapter 35, Quality of Service 35-1


Chapter 36, Resource Availability & Usage 36-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XIX-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 31 - RMS (Radio Measurement Statistics) Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XIX-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
35 Quality of Service
35

RMS

Overview
Purpose
This section contains RMS parameters.

Contents

RMS10 - VQ_NOISY_UL_INTERFERENCE 35-3


RMS11 - VQ_NOISY_DL_INTERFERENCE 35-4
RMS12 - VQ_NOISY_UL_COVERAGE 35-4
RMS13 - VQ_NOISY_DL_COVERAGE 35-5
RMS14 - VQ_NOISY_UL_UNDEFINED 35-6
RMS15 - VQ_NOISY_DL_UNDEFINED 35-7
RMS16 - VQ_NOISY_UL_BAD_FER 35-8
RMS17 - VQ_NOISY_UL_GOOD_FER 35-9
RMS18 - VQ_ABNORMAL_BAD_FER 35-10
RMS20 - TRE_BAND 35-10
RMS21 - IND_TRE_OVERLOAD 35-12
RMS22 - IND_RMS_RESTARTED 35-13
RMS23 - IND_CI_PARTIAL_OBSERVATION 35-13
RMS24 - IND_CI_OVERFLOW 35-14
RMS32 - TOT_MEAS 35-14
RMS33 - TOT_MEAS_L1INFO_NOL3INFO 35-15

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
RMS
....................................................................................................................................................................................................................................

RMS34 - TOT_MEAS_DTX_UL 35-15


RMS35 - TOT_MEAS_DTX_DL 35-16
RMS36 - PERC_TA_GT_TA_STAT 35-16
RMS37 - MAX_TA 35-17
RMS38 - TOT_EMR 35-17
RMS3a - TPR_RXQUAL_UL_RXLEV_UL 35-18
RMS3b - TMR_RXQUAL_UL_RXLEV_UL 35-19
RMS41a - AMR_WB_GMSK_FR_UL_BAD 35-19
RMS41b - MAX_AMR_WB_GMSK_FR_UL_BAD 35-20
RMS42a - AMR_WB_GMSK _FR_UL_RXLEV_UL 35-20
RMS42b - MAX_AMR_WB_GMSK_FR_UL_RXLEV_UL 35-22
RMS43a - AMR_WB_GMSK_FR_DL_RXLEV_DL 35-22
RMS43b - MAX_AMR_WB_GMSK_FR_DL_RXLEV_DL 35-23
RMS44a - AMR_FR_UL_BAD 35-24
RMS44b - MAX_AMR_FR_UL_BAD 35-25
RMS45a - AMR_HR_UL_BAD 35-25
RMS45b - MAX_AMR_HR_UL_BAD 35-26
RMS46a - AMR_FR_UL_RXLEV_UL 35-26
RMS46b - MAX_AMR_FR_UL_RXLEV_UL 35-28
RMS47a - AMR_FR_DL_RXLEV_DL 35-28
RMS47b - MAX_AMR_FR_DL_RXLEV_DL 35-29
RMS48a - AMR_HR_UL_RXLEV_UL 35-30
RMS49a - AMR_HR_DL_RXLEV_DL 35-31
RMS49b - MAX_AMR_HR_DL_RXLEV_DL 35-32
RMS4a - TPR_RXQUAL_DL_RXLEV_DL 35-32
RMS4b - TMR_RXQUAL_DL_RXLEV_DL 35-34
RMS50a - TPR_TIMING_ADVANCE 35-34
RMS50b - MAX_TIMING_ADVANCE 35-35
RMS51 - TPR_UL_RXLEV_TA_BAND 35-35
RMS52 - TPR_DL_RXLEV_TA_BAND 35-36
RMS53 - TPR_UL_RXQUAL_TA_BAND 35-37
RMS54 - TPR_DL_RXQUAL_TA_BAND 35-38
RMS5a - TPR_BFI_RXLEV_UL 35-38
....................................................................................................................................................................................................................................
35-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
RMS
....................................................................................................................................................................................................................................

RMS5b - TMR_BFI_RXLEV_UL 35-40


RMS6a - TPR_RADIO_LINK 35-40
RMS6b - MAX_RADIO_LINK 35-41
RMS7a - TPR_PATH_BALANCE 35-41
RMS7b - MAX_PATH_BALANCE 35-43
RMS8a - TPR_CIN 35-43
RMS8b - MR_CIN 35-45
RMS9a - TPR_CIF 35-45
RMS9b - MR_CIF 35-47

RMS10 - VQ_NOISY_UL_INTERFERENCE
Descripton

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 RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.

External Comment --

Feature Name RMS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS11 - VQ_NOISY_DL_INTERFERENCE
RMS
....................................................................................................................................................................................................................................

RMS11 - VQ_NOISY_DL_INTERFERENCE
Descripton

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 when 48.058 RF CHANNEL RELEASE is received for the observed call.
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 RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name RMS

RMS12 - VQ_NOISY_UL_COVERAGE
Descripton

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 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
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 DL measurements during the call on the
considered TRX

....................................................................................................................................................................................................................................
35-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS12 - VQ_NOISY_UL_COVERAGE
RMS
....................................................................................................................................................................................................................................

Sub Domain 1 RMS

Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX


Type Name RMS (Radio Measurement Statistics)

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

Feature Name RMS

RMS13 - VQ_NOISY_DL_COVERAGE
Descripton

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 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
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 RMS (Radio Measurement Statistics)

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

External Comment --
Feature Name RMS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS14 - VQ_NOISY_UL_UNDEFINED
RMS
....................................................................................................................................................................................................................................

RMS14 - VQ_NOISY_UL_UNDEFINED
Descripton

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 RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.

External Comment --
Feature Name RMS

....................................................................................................................................................................................................................................
35-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS15 - VQ_NOISY_DL_UNDEFINED
RMS
....................................................................................................................................................................................................................................

RMS15 - VQ_NOISY_DL_UNDEFINED
Descripton

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 RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.

External Comment --
Feature Name RMS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS16 - VQ_NOISY_UL_BAD_FER
RMS
....................................................................................................................................................................................................................................

RMS16 - VQ_NOISY_UL_BAD_FER
Descripton

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 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 RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --

Feature Name RMS

....................................................................................................................................................................................................................................
35-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS17 - VQ_NOISY_UL_GOOD_FER
RMS
....................................................................................................................................................................................................................................

RMS17 - VQ_NOISY_UL_GOOD_FER
Descripton

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 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 RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --

Feature Name RMS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS18 - VQ_ABNORMAL_BAD_FER
RMS
....................................................................................................................................................................................................................................

RMS18 - VQ_ABNORMAL_BAD_FER
Descripton

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 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 RMS (Radio Measurement Statistics)


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

External Comment --
Feature Name RMS

RMS20 - TRE_BAND
Descripton

Long Name TRE_BAND

....................................................................................................................................................................................................................................
35-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS20 - TRE_BAND
RMS
....................................................................................................................................................................................................................................

Definition Frequency band of the TRX.


The frequency band of the TRX is encoded as follows:
00: The frequencies defined are those available
for a P-GSM TRX (See external comment)
01: The frequencies defined are those available
for a DCS1800 TRX (See external comment)
02: The frequencies defined are those available
for a E-GSM TRX (See external comment)
03: The frequencies defined are those available
for a DCS1900 TRX (See external comment)
04: Not used
05: Not used
06: The frequencies defined are those available
for a GSM850 TRX (See external comment)

Trigger condition --
Sub Domain 1 RMS

Sub Domain 2 --
Sub Domain 3 --
Measured Object TRX
Type Name RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS20 - TRE_BAND
RMS
....................................................................................................................................................................................................................................

External Comment The term E-GSM TRX refers to :


1. a TRX configured with at least one frequency belonging to the G1 band in an E-GSM cell (i.e. a cell
where
FREQUENCY_RANGE is set to EGSM or E-GSM-DCS1800) if the EGSM_RR_ALLOC_STRATEGY
parameter is
set to Same behaviour for E-GSM capable MS, or
2. a TRX configured with all the frequencies belonging to the E-GSM band in an E-GSM cell (i.e. a cell
where
FREQUENCY_RANGE is set to EGSM or E-GSM-DCS1800) if the EGSM_RR_ALLOC_STRATEGY
parameter is
set to Same behaviour for E-GSM capable MS.
The term P-GSM TRX refers to a TRX configured with all the frequencies belonging to the P-GSM band :
1. in an E-GSM cell (i.e. a cell where FREQUENCY_RANGE is set to EGSM or EGSM-DCS1800) if the
EGSM_RR_ALLOC_STRATEGY parameter is set to Different behaviour for E-GSM capable MS
2. in a P-GSM cell (i.e. a cell where FREQUENCY_RANGE is set to PGSM or PGSM-DCS1800).
The term DCS1800 TRX refers to a TRX configured with frequencies belonging to the DCS1800 band
(i.e. a cell where FREQUENCY RANGE is set to DCS1800, PGSM-DCS1800 or EGSM-DCS1800).
The term DCS1900 TRX refers to a TRX configured with frequencies belonging to the DCS1900 band
(i.e. a cell where FREQUENCY RANGE is set to DCS1900).
The term GSM850 TRX refers to a TRX configured with frequencies belonging to the GSM850 band
(i.e. a cell where FREQUENCY RANGE is set to GSM850).
Feature Name RMS

RMS21 - IND_TRE_OVERLOAD
Descripton

Long Name IND_TRE_OVERLOAD


Definition Indicator whether a TRX overload occurred.
Trigger condition --

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --

Measured Object TRX


Type Name RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.

External Comment --

Feature Name RMS

....................................................................................................................................................................................................................................
35-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS22 - IND_RMS_RESTARTED
RMS
....................................................................................................................................................................................................................................

RMS22 - IND_RMS_RESTARTED
Descripton

Long Name IND_RMS_RESTARTED

Definition Flag set/reset by BSC. Flag is set when during the RMS campaign, the RMS
job is restarted on the concerned TRE (case modification of threshold
params, TRE reset).

Trigger condition --

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name RMS (Radio Measurement Statistics)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name RMS

RMS23 - IND_CI_PARTIAL_OBSERVATION
Descripton

Long Name IND_CI_PARTIAL_OBSERVATION


Definition bit map indicating that the measurements (for and only for CI vector computation) on either NMR
("Normal" Measurements Reports) or on EMR (Extended Measurements Reports) or on both or none were
RESTARTED during RMS job duration.
This counter is encoded as follows:
0: no CI partial result
1: EMO/EMR CI partial result
2: NMR CI partial result
3: EMR and NMR partial result

Trigger condition --

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name RMS (Radio Measurement Statistics)


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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS23 - IND_CI_PARTIAL_OBSERVATION
RMS
....................................................................................................................................................................................................................................

External Comment --

Feature Name RMS

RMS24 - IND_CI_OVERFLOW
Descripton

Long Name IND_CI_OVERFLOW

Definition Flag indicating that the upper limit of CI vectors to be reported is exceeded => each new result (couple
(BSIC, ARFCN) ) will not be taken into account.
Trigger condition --

Sub Domain 1 RMS


Sub Domain 2 --
Sub Domain 3 --
Measured Object TRX
Type Name RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --

Feature Name RMS

RMS32 - TOT_MEAS
Descripton

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 RMS (Radio Measurement Statistics)

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

Feature Name RMS

....................................................................................................................................................................................................................................
35-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS33 - TOT_MEAS_L1INFO_NOL3INFO
RMS
....................................................................................................................................................................................................................................

RMS33 - TOT_MEAS_L1INFO_NOL3INFO
Descripton

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 RMS (Radio Measurement Statistics)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name RMS

RMS34 - TOT_MEAS_DTX_UL
Descripton

Long Name TOT_MEAS_DTX_UL


Definition Number of measurement results used for RMS, where DTX is used on the uplink path.
Trigger condition Whenever a 48.058 MEASUREMENT RESULTS message is sent by the BTS, with DTX_UL=1, used for
RMS.

Sub Domain 1 RMS

Sub Domain 2 --
Sub Domain 3 --
Measured Object TRX

Type Name RMS (Radio Measurement Statistics)

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

Feature Name RMS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS35 - TOT_MEAS_DTX_DL
RMS
....................................................................................................................................................................................................................................

RMS35 - TOT_MEAS_DTX_DL
Descripton

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 When DL DTX is enabled, whenever a 48.058 MEASUREMENT RESULTS message is sent by the BTS,
with DTX_DL=1, and used for RMS

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name RMS (Radio Measurement Statistics)


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

Feature Name RMS

RMS36 - PERC_TA_GT_TA_STAT
Descripton

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 RMS (Radio Measurement Statistics)

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

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
35-16 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS37 - MAX_TA
RMS
....................................................................................................................................................................................................................................

RMS37 - MAX_TA
Descripton

Long Name MAX_TA

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 RMS (Radio Measurement Statistics)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name --

RMS38 - TOT_EMR
Descripton

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 RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.

External Comment --

Feature Name RMS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-17
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS3a - TPR_RXQUAL_UL_RXLEV_UL
RMS
....................................................................................................................................................................................................................................

RMS3a - TPR_RXQUAL_UL_RXLEV_UL
Descripton

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.
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 RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.

External Comment --
Feature Name RMS

....................................................................................................................................................................................................................................
35-18 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS3b - TMR_RXQUAL_UL_RXLEV_UL
RMS
....................................................................................................................................................................................................................................

RMS3b - TMR_RXQUAL_UL_RXLEV_UL
Descripton

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 RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --

Feature Name RMS

RMS41a - AMR_WB_GMSK_FR_UL_BAD
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-19
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS41a - AMR_WB_GMSK_FR_UL_BAD
RMS
....................................................................................................................................................................................................................................

Sub Domain 3 --

Measured Object TRX


Type Name RMS (Radio Measurement Statistics)

Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.

Feature Name AMR WB speech codec GMSK

RMS41b - MAX_AMR_WB_GMSK_FR_UL_BAD
Descripton

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 RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.
Feature Name AMR WB speech codec GMSK

RMS42a - AMR_WB_GMSK _FR_UL_RXLEV_UL


Descripton

Long Name AMR_WB_GMSK _FR_UL_RXLEV_UL

....................................................................................................................................................................................................................................
35-20 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS42a - AMR_WB_GMSK _FR_UL_RXLEV_UL
RMS
....................................................................................................................................................................................................................................

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 RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.

Feature Name AMR WB speech codec GMSK

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-21
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS42b - MAX_AMR_WB_GMSK_FR_UL_RXLEV_UL
RMS
....................................................................................................................................................................................................................................

RMS42b - MAX_AMR_WB_GMSK_FR_UL_RXLEV_UL
Descripton

Long Name MAX_AMR_WB_GMSK_FR_UL_RXLEV_UL

Definition Table of 10 maximum results.


Each cell Ci of the table indicates the greatest 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 RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.

Feature Name AMR WB speech codec GMSK

RMS43a - AMR_WB_GMSK_FR_DL_RXLEV_DL
Descripton

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

....................................................................................................................................................................................................................................
35-22 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS43a - AMR_WB_GMSK_FR_DL_RXLEV_DL
RMS
....................................................................................................................................................................................................................................

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 RMS (Radio Measurement Statistics)

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

External Comment This counter is only reported for cells mapped on Evolium BTS.
Feature Name AMR WB speech codec GMSK

RMS43b - MAX_AMR_WB_GMSK_FR_DL_RXLEV_DL
Descripton

Long Name MAX_AMR_WB_GMSK_FR_DL_RXLEV_DL


Definition Table of 10 maximum results.
Each cell Ci of the table indicates the greatest value of the Vik for a i given in RMS43a.
Trigger condition --
Sub Domain 1 RMS
Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX
Type Name RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.

External Comment This counter is only reported for cells mapped on Evolium BTS.
Feature Name AMR WB speech codec GMSK

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-23
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS44a - AMR_FR_UL_BAD
RMS
....................................................................................................................................................................................................................................

RMS44a - AMR_FR_UL_BAD
Descripton

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 RMS (Radio Measurement Statistics)

Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.
Feature Name RMS

....................................................................................................................................................................................................................................
35-24 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS44b - MAX_AMR_FR_UL_BAD
RMS
....................................................................................................................................................................................................................................

RMS44b - MAX_AMR_FR_UL_BAD
Descripton

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 RMS (Radio Measurement Statistics)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.
Feature Name RMS

RMS45a - AMR_HR_UL_BAD
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-25
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS45a - AMR_HR_UL_BAD
RMS
....................................................................................................................................................................................................................................

Measured Object TRX

Type Name RMS (Radio Measurement Statistics)


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

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

RMS45b - MAX_AMR_HR_UL_BAD
Descripton

Long Name MAX_AMR_HR_UL_BAD


Definition Greatest value of the Vi in RM45a.
Trigger condition --
Sub Domain 1 RMS
Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX
Type Name RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.
Feature Name RMS

RMS46a - AMR_FR_UL_RXLEV_UL
Descripton

Long Name AMR_FR_UL_RXLEV_UL

....................................................................................................................................................................................................................................
35-26 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS46a - AMR_FR_UL_RXLEV_UL
RMS
....................................................................................................................................................................................................................................

Definition Table of 8x10 results


Each cell (i,k) of the table contains :
1) number of correct 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 : MEAS_STAT_LEV_(i-1)<= RXLEV < MEAS_STAT_LEV_i
MEAS_STAT_LEV_0 = -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 RMS (Radio Measurement Statistics)

Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.

Feature Name RMS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-27
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS46b - MAX_AMR_FR_UL_RXLEV_UL
RMS
....................................................................................................................................................................................................................................

RMS46b - MAX_AMR_FR_UL_RXLEV_UL
Descripton

Long Name MAX_AMR_FR_UL_RXLEV_UL

Definition Table of 10 maximum results.


Each cell Ci of the table indicates the greatest value of the Vik for a i given in RMS46a.

Trigger condition --
Sub Domain 1 RMS

Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX


Type Name RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.

Feature Name RMS

RMS47a - AMR_FR_DL_RXLEV_DL
Descripton

Long Name AMR_FR_DL_RXLEV_DL


Definition Table of 8x10 results
Each cell (i,k) of the table contains :
1) number of correct DL speech frames using AMR FR 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 RMS47b).
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_(i-1)<= RXLEV < MEAS_STAT_LEV_i
MEAS_STAT_LEV_0 = -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

....................................................................................................................................................................................................................................
35-28 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS47a - AMR_FR_DL_RXLEV_DL
RMS
....................................................................................................................................................................................................................................

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 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
corresponding to reported DL RXLEV.
Sub Domain 1 RMS

Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX


Type Name RMS (Radio Measurement Statistics)

Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.

Feature Name RMS

RMS47b - MAX_AMR_FR_DL_RXLEV_DL
Descripton

Long Name MAX_AMR_FR_DL_RXLEV_DL


Definition Table of 10 maximum results.
Each cell Ci of the table indicates the greatest value of the Vik for a i given in RMS47a.
Trigger condition --
Sub Domain 1 RMS
Sub Domain 2 --

Sub Domain 3 --

Measured Object TRX


Type Name RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.

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

Feature Name RMS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-29
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS48a - AMR_HR_UL_RXLEV_UL
RMS
....................................................................................................................................................................................................................................

RMS48a - AMR_HR_UL_RXLEV_UL
Descripton

Long Name AMR_HR_UL_RXLEV_UL

Definition Table of 5x10 results


Each cell (i,k) of the table contains :
1) number of correct 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
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 : MEAS_STAT_LEV_(i-1)<= RXLEV < MEAS_STAT_LEV_i
MEAS_STAT_LEV_0 = -47 dBm, MEAS_STAT_LEV_10 = -110 dBm
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.
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 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 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 RMS (Radio Measurement Statistics)

Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.

Feature Name RMS

....................................................................................................................................................................................................................................
35-30 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS49a - AMR_HR_DL_RXLEV_DL
RMS
....................................................................................................................................................................................................................................

RMS49a - AMR_HR_DL_RXLEV_DL
Descripton

Long Name AMR_HR_DL_RXLEV_DL

Definition Table of 5x10 results


Each cell (i,k) of the table contains :
1) number of correct DL speech frames using AMR HR 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 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 : MEAS_STAT_LEV_(i-1)<= RXLEV < MEAS_STAT_LEV_i
MEAS_STAT_LEV_0 = -47 dBm, MEAS_STAT_LEV_10 = -110 dBm
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.
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 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 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 DL RXLEV.
Sub Domain 1 RMS
Sub Domain 2 --
Sub Domain 3 --
Measured Object TRX
Type Name RMS (Radio Measurement Statistics)

Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.

Feature Name RMS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-31
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS49b - MAX_AMR_HR_DL_RXLEV_DL
RMS
....................................................................................................................................................................................................................................

RMS49b - MAX_AMR_HR_DL_RXLEV_DL
Descripton

Long Name MAX_AMR_HR_DL_RXLEV_DL

Definition Table of 10 maximum results.


Each cell Ci of the table indicates the greatest value of the Vik for a i given in RMS49a.

Trigger condition .
Sub Domain 1 RMS

Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX


Type Name RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.

Feature Name RMS

RMS4a - TPR_RXQUAL_DL_RXLEV_DL
Descripton

Long Name TPR_RXQUAL_DL_RXLEV_DL

....................................................................................................................................................................................................................................
35-32 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS4a - TPR_RXQUAL_DL_RXLEV_DL
RMS
....................................................................................................................................................................................................................................

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 Evolium BTS : corresponding averaged value of [ MAX_POWER_PER_TRX- abs(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.
DL 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 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 RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.

External Comment --

Feature Name RMS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-33
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS4b - TMR_RXQUAL_DL_RXLEV_DL
RMS
....................................................................................................................................................................................................................................

RMS4b - TMR_RXQUAL_DL_RXLEV_DL
Descripton

Long Name TMR_RXQUAL_DL_RXLEV_DL

Definition Table of 10 maximum results.


Each cell Ci of the table indicates the greatest value of the Vij for a i given in RMS4a.

Trigger condition --
Sub Domain 1 RMS

Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX


Type Name RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --

Feature Name RMS

RMS50a - TPR_TIMING_ADVANCE
Descripton

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

....................................................................................................................................................................................................................................
35-34 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS50a - TPR_TIMING_ADVANCE
RMS
....................................................................................................................................................................................................................................

Sub Domain 3 --

Measured Object TRX


Type Name RMS (Radio Measurement Statistics)

Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.

Feature Name RMS

RMS50b - MAX_TIMING_ADVANCE
Descripton

Long Name MAX_TIMING_ADVANCE


Definition Greatest value of the Vi in RM50a.
Trigger condition --
Sub Domain 1 RMS

Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX


Type Name RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.
Feature Name RMS

RMS51 - TPR_UL_RXLEV_TA_BAND
Descripton

Long Name TPR_UL_RXLEV_TA_BAND

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-35
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS51 - TPR_UL_RXLEV_TA_BAND
RMS
....................................................................................................................................................................................................................................

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 RMS (Radio Measurement Statistics)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.
Feature Name RMS

RMS52 - TPR_DL_RXLEV_TA_BAND
Descripton

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 TA band are averaged.

Sub Domain 1 RMS


Sub Domain 2 --

....................................................................................................................................................................................................................................
35-36 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS52 - TPR_DL_RXLEV_TA_BAND
RMS
....................................................................................................................................................................................................................................

Sub Domain 3 --

Measured Object TRX


Type Name RMS (Radio Measurement Statistics)

Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.

Feature Name RMS

RMS53 - TPR_UL_RXQUAL_TA_BAND
Descripton

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 TA band are averaged.
Sub Domain 1 RMS

Sub Domain 2 --
Sub Domain 3 --
Measured Object TRX

Type Name RMS (Radio Measurement Statistics)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.

Feature Name RMS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-37
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS54 - TPR_DL_RXQUAL_TA_BAND
RMS
....................................................................................................................................................................................................................................

RMS54 - TPR_DL_RXQUAL_TA_BAND
Descripton

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 TA band are averaged.

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX
Type Name RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.
Feature Name RMS

RMS5a - TPR_BFI_RXLEV_UL
Descripton

Long Name TPR_BFI_RXLEV_UL

....................................................................................................................................................................................................................................
35-38 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS5a - TPR_BFI_RXLEV_UL
RMS
....................................................................................................................................................................................................................................

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 : 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 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 RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --

Feature Name RMS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-39
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS5b - TMR_BFI_RXLEV_UL
RMS
....................................................................................................................................................................................................................................

RMS5b - TMR_BFI_RXLEV_UL
Descripton

Long Name TMR_BFI_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 RMS5a.

Trigger condition --
Sub Domain 1 RMS

Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX


Type Name RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --

Feature Name RMS

RMS6a - TPR_RADIO_LINK
Descripton

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

....................................................................................................................................................................................................................................
35-40 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS6a - TPR_RADIO_LINK
RMS
....................................................................................................................................................................................................................................

Type Name RMS (Radio Measurement Statistics)

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

Feature Name RMS

RMS6b - MAX_RADIO_LINK
Descripton

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 RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name RMS

RMS7a - TPR_PATH_BALANCE
Descripton

Long Name TPR_PATH_BALANCE

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-41
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS7a - TPR_PATH_BALANCE
RMS
....................................................................................................................................................................................................................................

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 RMS (Radio Measurement Statistics)

Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name RMS

....................................................................................................................................................................................................................................
35-42 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS7b - MAX_PATH_BALANCE
RMS
....................................................................................................................................................................................................................................

RMS7b - MAX_PATH_BALANCE
Descripton

Long Name MAX_PATH_BALANCE

Definition Greatest value of the Vi in RMS7a.


Trigger condition --

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name RMS (Radio Measurement Statistics)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name RMS

RMS8a - TPR_CIN
Descripton

Long Name TPR_CIN

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-43
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS8a - TPR_CIN
RMS
....................................................................................................................................................................................................................................

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 RMS (Radio Measurement Statistics)


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

Feature Name RMS

....................................................................................................................................................................................................................................
35-44 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS8b - MR_CIN
RMS
....................................................................................................................................................................................................................................

RMS8b - MR_CIN
Descripton

Long Name MR_CIN

Definition Greatest value of the Vi in RMS8a.


Trigger condition --

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name RMS (Radio Measurement Statistics)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name RMS

RMS9a - TPR_CIF
Descripton

Long Name TPR_CIF

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-45
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS9a - TPR_CIF
RMS
....................................................................................................................................................................................................................................

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 RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name RMS

....................................................................................................................................................................................................................................
35-46 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service RMS9b - MR_CIF
RMS
....................................................................................................................................................................................................................................

RMS9b - MR_CIF
Descripton

Long Name MR_CIF

Definition Greatest value of the Vi in RMS9a.


Trigger condition --

Sub Domain 1 RMS


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name RMS (Radio Measurement Statistics)


Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment --
Feature Name RMS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 35-47
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Speech
....................................................................................................................................................................................................................................

Speech

Overview
Purpose
This section contains Speech parameters.

Contents

RMS48b - MAX_AMR_HR_UL_RXLEV_UL 35-48

RMS48b - MAX_AMR_HR_UL_RXLEV_UL
Descripton

Long Name MAX_AMR_HR_UL_RXLEV_UL


Definition Table of 10 maximum results.
Each cell Ci of the table indicates the greatest value of the Vik for a i given in RMS48a.
Trigger condition --
Sub Domain 1 Speech

Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX


Type Name RMS (Radio Measurement Statistics)
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment This counter is only reported for cells mapped on Evolium BTS.

Feature Name RMS

....................................................................................................................................................................................................................................
35-48 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
36 36
Resource Availability &
Usage

Channel

Overview
Purpose
This section contains Channel parameters.

Contents

RMS31 - TOT_SEIZ_TCH 36-1

RMS31 - TOT_SEIZ_TCH
Descripton

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 RMS (Radio Measurement Statistics)


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

External Comment --

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 36-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage RMS31 - TOT_SEIZ_TCH
Channel
....................................................................................................................................................................................................................................

Feature Name RMS

....................................................................................................................................................................................................................................
36-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage RMS31 - TOT_SEIZ_TCH

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 36-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage RMS31 - TOT_SEIZ_TCH

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
36-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XX: BSC-TYPE 32 - Change
of frequency band
measurements

Overview
Purpose
All type 32.

Contents

Chapter 37, Quality of Service 37-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XX-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 32 - Change of frequency band measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XX-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
37 Quality of Service
37

Handover

Overview
Purpose
This section contains Handover parameters.

Contents

C403a - NB_INC_EXT_TCH_HO_NEW_BAND_ATPT 37-2


C403b - NB_INC_EXT_TCH_HO_NEW_BAND_SUCC 37-2
C404a - NB_OUT_EXT_TCH_HO_NEW_BAND_ATPT 37-3
C404b - NB_OUT_EXT_TCH_HO_NEW_BAND_SUCC 37-3
C420a - NB_INC_INT_TCH_HO_NEW_BAND_ATPT 37-4
C420b - NB_INC_INT_TCH_HO_NEW_BAND_SUCC 37-5
C421a - NB_OUT_INT_TCH_HO_NEW_BAND_ATPT 37-5
C421b - NB_OUT_INT_TCH_HO_NEW_BAND_SUCC 37-6

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 37-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C403a - NB_INC_EXT_TCH_HO_NEW_BAND_ATPT
Handover
....................................................................................................................................................................................................................................

C403a - NB_INC_EXT_TCH_HO_NEW_BAND_ATPT
Descripton

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 intra-PLMN handover events.

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

Feature Name B8 BSC counters improvements

C403b - NB_INC_EXT_TCH_HO_NEW_BAND_SUCC
Descripton

Long Name NB_INC_EXT_TCH_HO_NEW_BAND_SUCC

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

Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abis 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 intra-PLMN handover events.

Sub Domain 1 Handover


Sub Domain 2 TCH
Sub Domain 3 --

Measured Object Common cell

....................................................................................................................................................................................................................................
37-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C403b - NB_INC_EXT_TCH_HO_NEW_BAND_SUCC
Handover
....................................................................................................................................................................................................................................

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

Feature Name B8 BSC counters improvements

C404a - NB_OUT_EXT_TCH_HO_NEW_BAND_ATPT
Descripton

Long Name NB_OUT_EXT_TCH_HO_NEW_BAND_ATPT

Definition Number of outgoing external TCH (in HR or FR usage) handover attempts including a change of the (TCH)
frequency band.
Trigger condition Whenever the 44.018 HANDOVER COMMAND message is sent on Abis 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 Change of frequency band measurements


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

External Comment --
Feature Name B8 BSC counters improvements

C404b - NB_OUT_EXT_TCH_HO_NEW_BAND_SUCC
Descripton

Long Name NB_OUT_EXT_TCH_HO_NEW_BAND_SUCC


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

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 = "normal event/call control") is received while T8 is running.
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.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 37-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C404b - NB_OUT_EXT_TCH_HO_NEW_BAND_SUCC
Handover
....................................................................................................................................................................................................................................

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

Feature Name B8 BSC counters improvements

C420a - NB_INC_INT_TCH_HO_NEW_BAND_ATPT
Descripton

Long Name NB_INC_INT_TCH_HO_NEW_BAND_ATPT


Definition Number of incoming internal TCH (in HR or FR usage) handover attempts including a change of the (TCH)
frequency band.
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 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 Change of frequency band measurements
Type Definition Set of counters related to handovers including a change of the TCH frequency band.

External Comment --
Feature Name B8 BSC counters improvements

....................................................................................................................................................................................................................................
37-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C420b - NB_INC_INT_TCH_HO_NEW_BAND_SUCC
Handover
....................................................................................................................................................................................................................................

C420b - NB_INC_INT_TCH_HO_NEW_BAND_SUCC
Descripton

Long Name NB_INC_INT_TCH_HO_NEW_BAND_SUCC

Definition Number of incoming internal TCH (in HR or FR usage) handover successes including a change of the
(TCH) frequency band.
Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abis 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 Change of frequency band measurements
Type Definition Set of counters related to handovers including a change of the TCH frequency band.

External Comment --
Feature Name B8 BSC counters improvements

C421a - NB_OUT_INT_TCH_HO_NEW_BAND_ATPT
Descripton

Long Name NB_OUT_INT_TCH_HO_NEW_BAND_ATPT


Definition Number of outgoing internal TCH (in HR or FR usage) handover attempts including a change of the (TCH)
frequency band.
Trigger condition Whenever the 44.018 HANDOVER COMMAND message is sent on Abis 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 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 Change of frequency band measurements

Type Definition Set of counters related to handovers including a change of the TCH frequency band.
External Comment --

Feature Name B8 BSC counters improvements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 37-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C421b - NB_OUT_INT_TCH_HO_NEW_BAND_SUCC
Handover
....................................................................................................................................................................................................................................

C421b - NB_OUT_INT_TCH_HO_NEW_BAND_SUCC
Descripton

Long Name NB_OUT_INT_TCH_HO_NEW_BAND_SUCC

Definition Number of outgoing internal TCH (in HR or FR usage) handover successes including a change of the (TCH)
frequency band.
Trigger condition Whenever a 44.018 HANDOVER COMPLETE message is received on Abis 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 Change of frequency band measurements
Type Definition Set of counters related to handovers including a change of the TCH frequency band.
External Comment --
Feature Name B8 BSC counters improvements

....................................................................................................................................................................................................................................
37-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C421b - NB_OUT_INT_TCH_HO_NEW_BAND_SUCC

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 37-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service C421b - NB_OUT_INT_TCH_HO_NEW_BAND_SUCC

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
37-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XXI: BSC-TYPE 33 - EME
(Electro-Magnetic
Emission) measurements

Overview
Purpose
All type 33.

Contents

Chapter 38, Sustainable & safety 38-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XXI-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 33 - EME (Electro-Magnetic Emission) Overview
measurements
....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XXI-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
38 Sustainable & safety
38

Electro-Magnetic Emission

Overview
Purpose
This section contains Electro-Magnetic Emission parameters.

Contents

E01 - EME_PWR_GSM 38-1


E02 - EME_PWR_DCS 38-2

E01 - EME_PWR_GSM
Descripton

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

Sub Domain 1 Electro-Magnetic Emission

Sub Domain 2 --
Sub Domain 3 --

Measured Object Common cell

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 38-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety E01 - EME_PWR_GSM
Electro-Magnetic Emission
....................................................................................................................................................................................................................................

Type Name EME (Electro-Magnetic Emission) measurements

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.
This counter may be not relevant for OLC one logical cell configuration.

Feature Name EME supervision

E02 - EME_PWR_DCS
Descripton

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

Sub Domain 1 Electro-Magnetic Emission


Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name EME (Electro-Magnetic Emission) measurements


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

External Comment This counter is only reported for cells mapped on Evolium BTS.
This counter may be not relevant for OLC one logical cell configuration.

Feature Name EME supervision

....................................................................................................................................................................................................................................
38-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety E02 - EME_PWR_DCS

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 38-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety E02 - EME_PWR_DCS

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
38-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XXII: BSC-TYPE 35 - IP
transport measurements

Overview
Purpose
All type 35.

Contents

Chapter 39, Quality of Service 39-1


Chapter 40, Traffic Load 40-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XXII-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 35 - IP transport measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XXII-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
39 Quality of Service
39

IP (QoS)

Overview
Purpose
This section contains IP (QoS) parameters.

Contents

IP11 - NB_CS_CALL_REJECTED_DUE_TO_IP_CONGESTION 39-3


IP12 - CUMULATED_TIME_IP_CONGESTION 39-3
IP13 - NB_MAX_ACTIVE_TCH_REJ 39-4
IP21 - NB_ATERMUX_NIBBLE_ALLOC_REQ 39-4
IP22 - NB_ATERMUX_NIBBLE_ALLOC_FAIL_CONG 39-5
IP23 - TIME_ATERMUX_NIBBLE_CONG 39-5
IP26e - NB_BTS_RESENT_RSL-I_LAPD FRAMES 39-6
IP27e - NB_BSC_RESENT_SS7_IP_PACKETS 39-6
IP28e - NB_TC_RESENT_SS7_IP_PACKETS 39-7
IP29k - NB_BTS_RCVD_DL_MUXTRAUP_PACKETS_OUT_OF_DELAY 39-7
IP29m - NB_BTS_NOT_RCVD_DL_MUXTRAUP_PACKETS 39-8
IP30m - NB_TC_NOT_RCVD_UL_MUXTRAUP_PACKETS 39-8
IP30q - NB_TC_NOT_RCVD_UL_MUXTRAUP_PACKETS_BSC 39-9
IP31c - NB_BTS_DROPPED_IP_PACKETS_PRIORITY0 39-9
IP31d - NB_BTS_DROPPED_IP_PACKETS_PRIORITY1 39-10
IP31e - NB_BTS_DROPPED_IP_PACKETS_PRIORITY2 39-10

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 39-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
IP (QoS)
....................................................................................................................................................................................................................................

IP31f - NB_BTS_DROPPED_IP_PACKETS_PRIORITY3 39-11


IP32a - NB_BSC_SENT_ALL_FLOWS_BYTES 39-11
IP32b - NB_BSC_RCVD_ALL_FLOWS_BYTES 39-12
IP32c - NB_BSC_DROPPED_IP_PACKETS_PRIORITY0 39-12
IP32d - NB_BSC_DROPPED_IP_PACKETS_PRIORITY1 39-13
IP32e - NB_BSC_DROPPED_IP_PACKETS_PRIORITY2 39-13
IP32f - NB_BSC_DROPPED_IP_PACKETS_PRIORITY3 39-14
IP35c - NB_BSC_RCVD_DL_MUXTRAUP_PACKETS_OUT_OF_DELAY 39-14
IP35d - NB_BSC_NOT_RCVD_DL_MUXTRAUP_PACKETS 39-15
IP40b - NB_BTS_RESENT_IPGCHU_GBR_IP_PACKETS 39-15
IP41b - NB_BTS_RESENT_IPGCHU_BE_IP_PACKETS 39-16
IP62 - NB_BSC_NOT_RCVD_UL_MUXTRAUP_PACKETS 39-16
IP70 - NB_ACC_TIME_SVR1 39-17
IP71 - NB_ACC_TIME_SVR2 39-17
IP72 - NB_SUCC_ACC_TIME_SVR1 39-18
IP73 - NB_SUCC_ACC_TIME_SVR2 39-18
IP74 - LAST_CLK_DIFF_TIME_SVR1 39-19
IP75 - LAST_CLK_DIFF_TIME_SVR2 39-19
IP76 - MIN_CLK_DIFF_TIME_SVR1 39-20
IP77 - MIN_CLK_DIFF_TIME_SVR2 39-20
IP78 - LAST_RTT_TIME_SVR1 39-21
IP79 - LAST_RTT_TIME_SVR2 39-21
IP80 - NB_EVALS_RETUNE_TIME_SVR1 39-22
IP81 - NB_EVALS_RETUNE_TIME_SVR2 39-22
IP82 - NB_ACC_EVALS_RETUNE_TIME_SVR1 39-23
IP83 - NB_ACC_EVALS_RETUNE_TIME_SVR2 39-24
IP84 - GRADIENT_TIME_SVR1 39-24
IP85 - GRADIENT_TIME_SVR2 39-25
IP86 - MEAN_GRADIENT_TIME_SVR1 39-25
IP87 - MEAN_GRADIENT_TIME_SVR2 39-26
IP88 - OCXO_TUNING_TIME_SVR 39-26
IP89 - OCXO_TUNING_VALUE 39-27

....................................................................................................................................................................................................................................
39-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP11 - NB_CS_CALL_REJECTED_DUE_TO_IP_CONGESTION
IP (QoS)
....................................................................................................................................................................................................................................

IP11 - NB_CS_CALL_REJECTED_DUE_TO_IP_CONGESTION
Descripton

Long Name NB_CS_CALL_REJECTED_DUE_TO_IP_CONGESTION

Definition Number of CS calls rejected due to IP congestion reported by the BTS to the BSC.
Trigger condition Each time a TCH cannot be allocated because the target cell is mapped on an IP BTS which in IP congestion
status (i.e IP congestion indication sent by the BTS to the BSC), this counter is increased by 1.
Note: when the concerned BTS is in IP congestion status and if the request can be queued, then IP11 is
increased by 1 only once the queuing timer expires for this request and that the IP congestion in the BTS
still exists.
Sub Domain 1 IP (QoS)

Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell
Type Name IP transport measurements
Type Definition Set of counters related to IP transport

External Comment --
Feature Name IP transport in the BSS

IP12 - CUMULATED_TIME_IP_CONGESTION
Descripton

Long Name CUMULATED_TIME_IP_CONGESTION


Definition Cumulated time during which the IP congestion is reported for a given IP BTS.

Trigger condition The counter is started when the BSC receives the CONGESTION INDICATION from a given IP BTS with
congestion status: Congestion or High Congestion.
The counter is stopped when the BSC receives the CONGESTION INDICATION from this IP BTS with
congestion status: No Congestion.

Sub Domain 1 IP (QoS)


Sub Domain 2 --

Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 39-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP13 - NB_MAX_ACTIVE_TCH_REJ
IP (QoS)
....................................................................................................................................................................................................................................

IP13 - NB_MAX_ACTIVE_TCH_REJ
Descripton

Long Name NB_MAX_ACTIVE_TCH_REJ

Definition Number of rejected incoming call when NB_MAX_ACTIVE_TCH_TS limitation is reached.


Trigger condition Whenever a TCH cannot be allocated due to the TCH processing capacity of AbisBTSGroup reaches the
limit defined by the NB_MAX_ACTIVE_TCH_TS parameter (Note).
Note: In case where the TCH processing capacity of AbisBTSGroup reaches the limit defined by the
NB_MAX_ACTIVE_TCH_TS parameter and if the request can be queued, then IP13 will not be
incremented by 1. If the queuing timer expires for this request, then IP13 is increased by 1 if IP congestion
still exists.
Sub Domain 1 IP (QoS)

Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell

Type Name IP transport measurements


Type Definition Set of counters related to IP transport

External Comment --
Feature Name IP transport in the BSS

IP21 - NB_ATERMUX_NIBBLE_ALLOC_REQ
Descripton

Long Name NB_ATERMUX_NIBBLE_ALLOC_REQ


Definition Number of Atermux Nibble allocation requests.
Trigger condition The counter is incremented by the IP BSC whenever the 48.058 CHANNEL ACTIVATION
ACKNOWLEDGE message is received for a TCH call to be established in a TDM BTS.

Sub Domain 1 IP (QoS)


Sub Domain 2 --

Sub Domain 3 --

Measured Object BSC-TC rack


Type Name IP transport measurements
Type Definition Set of counters related to IP transport

External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
39-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP22 - NB_ATERMUX_NIBBLE_ALLOC_FAIL_CONG
IP (QoS)
....................................................................................................................................................................................................................................

IP22 - NB_ATERMUX_NIBBLE_ALLOC_FAIL_CONG
Descripton

Long Name NB_ATERMUX_NIBBLE_ALLOC_FAIL_CONG

Definition Number of Atermux Nibble allocation failure due to Atermux congestion.


Trigger condition Whenever no Atermux Nibble can be allocated by an IP BSC for an incoming TCH request due to no free
Atermux Nibble on the TC. See OP in the header document to know which cause is sent in the
ASSIGNMENT FAILURE to the MSC in this case.

Sub Domain 1 IP (QoS)


Sub Domain 2 --

Sub Domain 3 --

Measured Object BSC-TC rack


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

IP23 - TIME_ATERMUX_NIBBLE_CONG
Descripton

Long Name TIME_ATERMUX_NIBBLE_CONG


Definition Cumulated time during which the Atermux interface between the IP BSC and a given IP TC is in congestion
state (i.e there is no more free Atermux nibble for incoming TCH).
Trigger condition The counter is started when the IP BSC detects that there is no free Atermux Nibble for a given TC to serve
an incoming TCH request for a TDM BTS.
The counter is stopped and reset when he IP BSC detects that there is a free Atermux Nibble to serve an
incoming TCH request for a TDM BTS.
Sub Domain 1 IP (QoS)

Sub Domain 2 --

Sub Domain 3 --
Measured Object BSC-TC rack
Type Name IP transport measurements

Type Definition Set of counters related to IP transport

External Comment --
Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 39-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP26e - NB_BTS_RESENT_RSL-I_LAPD FRAMES
IP (QoS)
....................................................................................................................................................................................................................................

IP26e - NB_BTS_RESENT_RSL-I_LAPD FRAMES


Descripton

Long Name NB_BTS_RESENT_RSL-I_LAPD FRAMES

Definition Counts the number of RSL-I LAPD frames resent by the BTS. The purpose is to measure the quality of the
link.
Trigger condition Each time an RSL-I frame is resent by the BTS, this counter is increased by 1.

Sub Domain 1 IP (QoS)


Sub Domain 2 Abis (QoS IP)

Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport
External Comment --

Feature Name IP transport in the BSS

IP27e - NB_BSC_RESENT_SS7_IP_PACKETS
Descripton

Long Name NB_BSC_RESENT_SS7_IP_PACKETS


Definition Counts the number of SCTP packets resent by an IP BSC to a given IP TC for the SS7 flow.
Trigger condition Each time a SCTP segment containing a SS7 packet is resent by the BSC to a given TC, this counter is
increased by 1.
Sub Domain 1 IP (QoS)

Sub Domain 2 SS7 over IP / SCTP (QoS)


Sub Domain 3 --

Measured Object BSC-TC rack

Type Name IP transport measurements


Type Definition Set of counters related to IP transport

External Comment --
Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
39-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP28e - NB_TC_RESENT_SS7_IP_PACKETS
IP (QoS)
....................................................................................................................................................................................................................................

IP28e - NB_TC_RESENT_SS7_IP_PACKETS
Descripton

Long Name NB_TC_RESENT_SS7_IP_PACKETS

Definition Counts the number of SCTP packets resent by an IP TC to a given IP BSC for the IP_BSSAsig flow.
Trigger condition Each time a SCTP segment containing a IP_BSSAsig packet is resent by a TC to the BSC, this counter is
increased by 1.
Sub Domain 1 IP (QoS)

Sub Domain 2 SS7 over IP / SCTP (QoS)


Sub Domain 3 --

Measured Object BSC-TC rack


Type Name IP transport measurements
Type Definition Set of counters related to IP transport
External Comment --

Feature Name IP transport in the BSS

IP29k - NB_BTS_RCVD_DL_MUXTRAUP_PACKET-
S_OUT_OF_DELAY
Descripton

Long Name NB_BTS_RCVD_DL_MUXTRAUP_PACKETS_OUT_OF_DELAY


Definition Counts the number of DL MUXTRAUP packets received by an IP BTS, and which have an excessive jitter.
Trigger condition Each time the IP BTS receives a MUXTRAUP packet with an excessive jitter, this counter is increased by 1.
This counter only considers the packets addressed to a given IP BTS.

Sub Domain 1 IP (QoS)


Sub Domain 2 IPTCH (QoS)(MUXTRAUP frames)

Sub Domain 3 --

Measured Object BTS


Type Name IP transport measurements
Type Definition Set of counters related to IP transport

External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 39-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP29m - NB_BTS_NOT_RCVD_DL_MUXTRAUP_PACKETS
IP (QoS)
....................................................................................................................................................................................................................................

IP29m - NB_BTS_NOT_RCVD_DL_MUXTRAUP_PACKETS
Descripton

Long Name NB_BTS_NOT_RCVD_DL_MUXTRAUP_PACKETS

Definition Counts the number of lost DL MUXTRAUP packets, i.e not received by the IP BTS.
Trigger condition Each time the IP BTS detects that the MUXTRAUP for a given sequence number is missing, this counter is
increased by 1.

Sub Domain 1 IP (QoS)


Sub Domain 2 IPTCH (QoS)(MUXTRAUP frames)

Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport
External Comment As the counter is based on the sequence number, the counter value may be underestimate in particular if
more than 128 consecutives packets are lost.

Feature Name IP transport in the BSS

IP30m - NB_TC_NOT_RCVD_UL_MUXTRAUP_PACKETS
Descripton

Long Name NB_TC_NOT_RCVD_UL_MUXTRAUP_PACKETS


Definition Counts the number of lost UL MUXTRAUP packets, i.e not received by the IP TC from a given BTS.
Trigger condition Each time the IP TC detects that the MUXTRAUP for a given sequence number is missing in the UL IPTCH
flow for a given BTS, this counter is increased by 1.

Sub Domain 1 IP (QoS)


Sub Domain 2 IPTCH (QoS)(MUXTRAUP frames)

Sub Domain 3 --

Measured Object BTS


Type Name IP transport measurements
Type Definition Set of counters related to IP transport

External Comment As the counter is based on the sequence number, the counter value may be underestimate in particular if
more than 128 consecutives packets are lost.

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
39-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP30q - NB_TC_NOT_RCVD_UL_MUXTRAUP_PACKETS_BSC
IP (QoS)
....................................................................................................................................................................................................................................

IP30q - NB_TC_NOT_RCVD_UL_MUXTRAUP_PACKETS_BSC
Descripton

Long Name NB_TC_NOT_RCVD_UL_MUXTRAUP_PACKETS_BSC

Definition Counts the number of lost UL MUXTRAUP packets, i.e not received by the IP TC from a BSC.
Trigger condition Each time the IP TC detects that the MUXTRAUP for a given sequence number is missing in the UL IPTCH
flow for a BSC, this counter is increased by 1.

Sub Domain 1 IP (QoS)


Sub Domain 2 IPTCH (QoS)(MUXTRAUP frames)

Sub Domain 3 --
Measured Object BSC-TC rack

Type Name IP transport measurements


Type Definition Set of counters related to IP transport
External Comment --

Feature Name AUPoIP A interface user plane over IP

IP31c - NB_BTS_DROPPED_IP_PACKETS_PRIORITY0
Descripton

Long Name NB_BTS_DROPPED_IP_PACKETS_PRIORITY0


Definition Counts the number of UL IP packets with priority 0 dropped in the IP BTS because of a lack of transmission
bandwidth.
Trigger condition Each time the SUM of an IP BTS drops an UL IP packet in the priority 0 queue, this counter is increased by
1.
Sub Domain 1 IP (QoS)

Sub Domain 2 Abis (QoS IP)

Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport

External Comment --
Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 39-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP31d - NB_BTS_DROPPED_IP_PACKETS_PRIORITY1
IP (QoS)
....................................................................................................................................................................................................................................

IP31d - NB_BTS_DROPPED_IP_PACKETS_PRIORITY1
Descripton

Long Name NB_BTS_DROPPED_IP_PACKETS_PRIORITY1

Definition Counts the number of UL IP packets with priority 1 dropped in the IP BTS because of a lack of transmission
bandwidth.
Trigger condition Each time the SUM of an IP BTS drops an UL IP packet in the priority 1 queue, this counter is increased by
1.

Sub Domain 1 IP (QoS)


Sub Domain 2 --

Sub Domain 3 --

Measured Object BTS


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

IP31e - NB_BTS_DROPPED_IP_PACKETS_PRIORITY2
Descripton

Long Name NB_BTS_DROPPED_IP_PACKETS_PRIORITY2


Definition Counts the number of UL IP packets with priority 2 dropped in the IP BTS because of a lack of transmission
bandwidth.
Trigger condition Each time the SUM of an IP BTS drops an UL IP packet in the priority 2 queue, this counter is increased by
1.

Sub Domain 1 IP (QoS)

Sub Domain 2 --
Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
39-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP31f - NB_BTS_DROPPED_IP_PACKETS_PRIORITY3
IP (QoS)
....................................................................................................................................................................................................................................

IP31f - NB_BTS_DROPPED_IP_PACKETS_PRIORITY3
Descripton

Long Name NB_BTS_DROPPED_IP_PACKETS_PRIORITY3

Definition Counts the number of UL IP packets with priority 3 dropped in the IP BTS because of a lack of transmission
bandwidth.
Trigger condition Each time the SUM of an IP BTS drops an UL IP packet in the priority 3 queue, this counter is increased by
1.

Sub Domain 1 IP (QoS)


Sub Domain 2 --

Sub Domain 3 --

Measured Object BTS


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

IP32a - NB_BSC_SENT_ALL_FLOWS_BYTES
Descripton

Long Name NB_BSC_SENT_ALL_FLOWS_BYTES


Definition Counts the number of DL bytes sent on a given E1 link used for IP transport for all priorities.
Trigger condition Each time the TPGSM board of an IP BSS sends a message on an E1 link, this counter is increased by the
number of bytes of this message.

Sub Domain 1 IP (QoS)


Sub Domain 2 Abis (QoS IP)

Sub Domain 3 --

Measured Object IPoE1 Abis link


Type Name IP transport measurements
Type Definition Set of counters related to IP transport

External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 39-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP32b - NB_BSC_RCVD_ALL_FLOWS_BYTES
IP (QoS)
....................................................................................................................................................................................................................................

IP32b - NB_BSC_RCVD_ALL_FLOWS_BYTES
Descripton

Long Name NB_BSC_RCVD_ALL_FLOWS_BYTES

Definition Counts the number of UL bytes received by the BSC on a given E1 link used for IP transport for all
priorities.
Trigger condition Each time the TPGSM board of an IP BSS receives a message on an E1 link, this counter is increased by the
number of bytes of this message.

Sub Domain 1 IP (QoS)


Sub Domain 2 Abis (QoS IP)

Sub Domain 3 --

Measured Object IPoE1 Abis link


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

IP32c - NB_BSC_DROPPED_IP_PACKETS_PRIORITY0
Descripton

Long Name NB_BSC_DROPPED_IP_PACKETS_PRIORITY0


Definition Counts the number of DL IP packets with priority 0 dropped in the IP BSC because of a lack of transmission
bandwidth.
Trigger condition Each time the TPGSM board of an IP BSC drops a DL IP packet in the priority 0 queue, this counter is
increased by 1.

Sub Domain 1 IP (QoS)

Sub Domain 2 --
Sub Domain 3 --
Measured Object IPoE1 Abis link

Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
39-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP32d - NB_BSC_DROPPED_IP_PACKETS_PRIORITY1
IP (QoS)
....................................................................................................................................................................................................................................

IP32d - NB_BSC_DROPPED_IP_PACKETS_PRIORITY1
Descripton

Long Name NB_BSC_DROPPED_IP_PACKETS_PRIORITY1

Definition Counts the number of DL IP packets with priority 1 dropped in the IP BSC because of a lack of transmission
bandwidth.
Trigger condition Each time the TPGSM board of an IP BSC drops a DL IP packet in the priority 1 queue, this counter is
increased by 1.

Sub Domain 1 IP (QoS)


Sub Domain 2 --

Sub Domain 3 --

Measured Object IPoE1 Abis link


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

IP32e - NB_BSC_DROPPED_IP_PACKETS_PRIORITY2
Descripton

Long Name NB_BSC_DROPPED_IP_PACKETS_PRIORITY2


Definition Counts the number of DL IP packets with priority 2 dropped in the IP BSC because of a lack of transmission
bandwidth.
Trigger condition Each time the TPGSM board of an IP BSC drops a DL IP packet in the priority 2 queue, this counter is
increased by 1.

Sub Domain 1 IP (QoS)

Sub Domain 2 --
Sub Domain 3 --
Measured Object IPoE1 Abis link

Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 39-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP32f - NB_BSC_DROPPED_IP_PACKETS_PRIORITY3
IP (QoS)
....................................................................................................................................................................................................................................

IP32f - NB_BSC_DROPPED_IP_PACKETS_PRIORITY3
Descripton

Long Name NB_BSC_DROPPED_IP_PACKETS_PRIORITY3

Definition Counts the number of DL IP packets with priority 3 dropped in the IP BSC because of a lack of transmission
bandwidth.
Trigger condition Each time the TPGSM board of an IP BSC drops a DL IP packet in the priority 3 queue, this counter is
increased by 1.

Sub Domain 1 IP (QoS)


Sub Domain 2 --

Sub Domain 3 --

Measured Object IPoE1 Abis link


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

IP35c - NB_BSC_RCVD_DL_MUXTRAUP_PACKET-
S_OUT_OF_DELAY
Descripton

Long Name NB_BSC_RCVD_DL_MUXTRAUP_PACKETS_OUT_OF_DELAY


Definition Counts the number of DL MUXTRAUP packets received by the BSC from a given TC and which have an
excessive jitter.

Trigger condition Each time the BSC receives a DL MUXTRAUP packet with an excessive jitter, this counter is increased by
1
Sub Domain 1 IP (QoS)

Sub Domain 2 IPTCH (QoS)(MUXTRAUP frames)


Sub Domain 3 --

Measured Object BSC-TC rack

Type Name IP transport measurements


Type Definition Set of counters related to IP transport

External Comment --
Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
39-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP35d - NB_BSC_NOT_RCVD_DL_MUXTRAUP_PACKETS
IP (QoS)
....................................................................................................................................................................................................................................

IP35d - NB_BSC_NOT_RCVD_DL_MUXTRAUP_PACKETS
Descripton

Long Name NB_BSC_NOT_RCVD_DL_MUXTRAUP_PACKETS

Definition Counts the number of lost DL MUXTRAUP packets, i.e not received by the BSC from a given TC
Trigger condition Each time the BSC detects that the MUXTRAUP for a given sequence number is missing in the DL flow for
a given TC, this counter is increased by 1

Sub Domain 1 IP (QoS)


Sub Domain 2 IPTCH (QoS)(MUXTRAUP frames)

Sub Domain 3 --
Measured Object BSC-TC rack

Type Name IP transport measurements


Type Definition Set of counters related to IP transport
External Comment --

Feature Name AUPoIP A interface user plane over IP

IP40b - NB_BTS_RESENT_IPGCHU_GBR_IP_PACKETS
Descripton

Long Name NB_BTS_RESENT_IPGCHU_GBR_IP_PACKETS


Definition Counts the number of IPGCHU segments resent by an IP BTS to the MFS for the GBR flow.
Trigger condition Each time the BTS resends an UL IPGCHU segment (from any TRE) to the MFS for a GBR flow, this
counter is increased by 1. This counter is managed by the SUM board.
Sub Domain 1 IP (QoS)

Sub Domain 2 IPGCHU (QoS)


Sub Domain 3 --

Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport

External Comment --
Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 39-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP41b - NB_BTS_RESENT_IPGCHU_BE_IP_PACKETS
IP (QoS)
....................................................................................................................................................................................................................................

IP41b - NB_BTS_RESENT_IPGCHU_BE_IP_PACKETS
Descripton

Long Name NB_BTS_RESENT_IPGCHU_BE_IP_PACKETS

Definition Counts the number of IPGCHU segments resent by an IP BTS to the MFS for the BE flow.
Trigger condition Each time the BTS resends an UL IPGCHU segment (from any TRE) to the MFS for a BE flow, this counter
is increased by 1. This counter is managed by the SUM board.

Sub Domain 1 IP (QoS)


Sub Domain 2 IPGCHU (QoS)

Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport
External Comment --

Feature Name IP transport in the BSS

IP62 - NB_BSC_NOT_RCVD_UL_MUXTRAUP_PACKETS
Descripton

Long Name NB_BSC_NOT_RCVD_UL_MUXTRAUP_PACKETS


Definition Counts the number of lost UL MUXTRAUP packets, i.e not received by the BSC from a given BTS
Trigger condition Each time the BSC detects that the MUXTRAUP for a given sequence number is missing in the UL IPTCH
flow for a given BTS, this counter is increased by 1.
Sub Domain 1 IP (QoS)

Sub Domain 2 IPTCH (QoS)(MUXTRAUP frames)


Sub Domain 3 --

Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport

External Comment --
Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
39-16 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP70 - NB_ACC_TIME_SVR1
IP (QoS)
....................................................................................................................................................................................................................................

IP70 - NB_ACC_TIME_SVR1
Descripton

Long Name NB_ACC_TIME_SVR1

Definition Number of BTS accesses (polls) to the frequency synchro time server 1, cumulated during the Granularity
Period (15').
Trigger condition When the BTS send a polling request to the frequency synchro time server 1.

Sub Domain 1 IP (QoS)


Sub Domain 2 BTS Freq. Sync.

Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport
External Comment --

Feature Name IP transport in the BSS

IP71 - NB_ACC_TIME_SVR2
Descripton

Long Name NB_ACC_TIME_SVR2


Definition Number of BTS accesses (polls) to the frequency synchro time server 2, cumulated during the Granularity
Period (15').
Trigger condition When the BTS send a polling request to the frequency synchro time server 2.
Sub Domain 1 IP (QoS)

Sub Domain 2 BTS Freq. Sync.


Sub Domain 3 --

Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport

External Comment --
Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 39-17
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP72 - NB_SUCC_ACC_TIME_SVR1
IP (QoS)
....................................................................................................................................................................................................................................

IP72 - NB_SUCC_ACC_TIME_SVR1
Descripton

Long Name NB_SUCC_ACC_TIME_SVR1

Definition Number of successful BTS accesses (polls) to the frequency synchro time server 1, cumulated during the
Granularity Period (15').
Trigger condition When the BTS receives a polling answer from the frequency synchro time server 1 and this response is
usable.

Sub Domain 1 IP (QoS)


Sub Domain 2 BTS Freq. Sync.

Sub Domain 3 --

Measured Object BTS


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment An answer received from the frequency synchro time server is considered "usable" if the response indicates
that the time service is stable and there is no "leap second" detected.
Allows to compute the unavailability of the frequency synchro time server 1 during the GP.
Feature Name IP transport in the BSS

IP73 - NB_SUCC_ACC_TIME_SVR2
Descripton

Long Name NB_SUCC_ACC_TIME_SVR2


Definition Number of successful BTS accesses (polls) to the frequency synchro time server 2, cumulated during the
Granularity Period (15').
Trigger condition When the BTS receives a polling answer from the frequency synchro time server 2 and this response is
usable.
Sub Domain 1 IP (QoS)

Sub Domain 2 BTS Freq. Sync.

Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport

External Comment An answer received from the frequency synchro time server is considered "usable" if the response indicates
that the time service is stableand there is no "leap second" detected.
Allow to compute the unavailability of the frequency synchro time server 1 during the GP.

....................................................................................................................................................................................................................................
39-18 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP73 - NB_SUCC_ACC_TIME_SVR2
IP (QoS)
....................................................................................................................................................................................................................................

Feature Name IP transport in the BSS

IP74 - LAST_CLK_DIFF_TIME_SVR1
Descripton

Long Name LAST_CLK_DIFF_TIME_SVR1

Definition Clock difference (i.e.: time in the BTS vs time in the frequency synchro time server) of the last polling to the
frequency synchro time server 1 during the Granularity Period (15').
Trigger condition When the BTS receives a polling answer or a timeout from the frequency synchro time server 1.

Sub Domain 1 IP (QoS)


Sub Domain 2 BTS Freq. Sync.

Sub Domain 3 --
Measured Object BTS
Type Name IP transport measurements
Type Definition Set of counters related to IP transport
External Comment The clock_diff is the essential value calculated from each frequency synchro time server response and it is
the input of the frequency synchro tuning algo. Here the delay jitter of the response message of the last poll
is visible
FFFF FFFEh means "no access to the time server"
Feature Name IP transport in the BSS

IP75 - LAST_CLK_DIFF_TIME_SVR2
Descripton

Long Name LAST_CLK_DIFF_TIME_SVR2


Definition Clock difference (i.e.: time in the BTS vs time in the frequency synchro time server) of the last polling to the
frequency synchro time server 2 during the Granularity Period (15').
Trigger condition When the BTS receives a polling answer or a timeout from the frequency synchro time server 2

Sub Domain 1 IP (QoS)

Sub Domain 2 BTS Freq. Sync.


Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements

Type Definition Set of counters related to IP transport

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 39-19
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP75 - LAST_CLK_DIFF_TIME_SVR2
IP (QoS)
....................................................................................................................................................................................................................................

External Comment The clock_diff is the essential value calculated from each frequency synchro time server response and it is
the input of the frequency synchro tuning algo. Here the delay jitter of the response message of the last poll
is visible.
FFFF FFFEh means "no access to the time server"
Feature Name IP transport in the BSS

IP76 - MIN_CLK_DIFF_TIME_SVR1
Descripton

Long Name MIN_CLK_DIFF_TIME_SVR1

Definition Minimum clock difference of all pollings to the frequency synchro time server 1 during the last evaluation
period (default value 24h).
Trigger condition At the end of each evaluation task

Sub Domain 1 IP (QoS)


Sub Domain 2 BTS Freq. Sync.
Sub Domain 3 --
Measured Object BTS
Type Name IP transport measurements
Type Definition Set of counters related to IP transport
External Comment FFFF FFFEh means "no access to time server"

Feature Name IP transport in the BSS

IP77 - MIN_CLK_DIFF_TIME_SVR2
Descripton

Long Name MIN_CLK_DIFF_TIME_SVR2


Definition Minimum clock difference of all pollings to the frequency synchro time server 2 during the last evaluation
period (default value 24h).
Trigger condition At the end of each evaluation task

Sub Domain 1 IP (QoS)

Sub Domain 2 BTS Freq. Sync.


Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements

Type Definition Set of counters related to IP transport

....................................................................................................................................................................................................................................
39-20 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP77 - MIN_CLK_DIFF_TIME_SVR2
IP (QoS)
....................................................................................................................................................................................................................................

External Comment FFFF FFFEh means "no access to time server"

Feature Name IP transport in the BSS

IP78 - LAST_RTT_TIME_SVR1
Descripton

Long Name LAST_RTT_TIME_SVR1

Definition Round trip time of the last polling performed by the BTS to the frequency synchro time server 1 during the
Granularity Period (15').
Trigger condition At the end of each time server 1 polling task.

Sub Domain 1 IP (QoS)


Sub Domain 2 BTS Freq. Sync.
Sub Domain 3 --
Measured Object BTS
Type Name IP transport measurements
Type Definition Set of counters related to IP transport
External Comment This counter shows the reactivity of the frequency synchro time servers (through the IP network) and allows
to show the quality of the service provided by the IP network of the customer.

Feature Name IP transport in the BSS

IP79 - LAST_RTT_TIME_SVR2
Descripton

Long Name LAST_RTT_TIME_SVR2

Definition Round trip time of the last polling performed by the BTS to the frequency synchro time server 2 during the
Granularity Period (15').

Trigger condition End of each time server 2 polling task.

Sub Domain 1 IP (QoS)


Sub Domain 2 BTS Freq. Sync.

Sub Domain 3 --

Measured Object BTS


Type Name IP transport measurements
Type Definition Set of counters related to IP transport

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 39-21
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP79 - LAST_RTT_TIME_SVR2
IP (QoS)
....................................................................................................................................................................................................................................

External Comment This counter shows the reactivity of the frequency synchro time servers (through the IP network) and allows
to show the quality of the service provided by the IP network of the customer.

Feature Name IP transport in the BSS

IP80 - NB_EVALS_RETUNE_TIME_SVR1
Descripton

Long Name NB_EVALS_RETUNE_TIME_SVR1

Definition Cumulated number of evaluations performed by the BTS, using the frequency synchro time server 1, since
algorithm restart or OCXO retune.
Trigger condition At the end of each evaluation task using the frequency synchro time server 1.

Sub Domain 1 IP (QoS)


Sub Domain 2 BTS Freq. Sync.
Sub Domain 3 --
Measured Object BTS
Type Name IP transport measurements
Type Definition Set of counters related to IP transport
External Comment Allow to measure when the last OCXO tuning happened:
It is (for the sustained phase): NB_EVALS_RETUNE_TIME_SVR1 * FREQ_SYNC_POLLS_PER_EVAL
* FREQ_SYNC_POLLING_TIME_SUSTAINED
Note: NB_EVALS_RETUNE_TIME_SVR1, FREQ_SYNC_POLLS_PER_EVAL and FREQ_SYNC_POLLING_
TIME_SUSTAINED are defined in the BTP.
Feature Name IP transport in the BSS

IP81 - NB_EVALS_RETUNE_TIME_SVR2
Descripton

Long Name NB_EVALS_RETUNE_TIME_SVR2


Definition Cumulated number of evaluations performed by the BTS, using the frequency synchro time server 2, since
algorithm restart or OCXO retune.
Trigger condition End of each evaluation task using the frequency synchro time server 2.
Sub Domain 1 IP (QoS)

Sub Domain 2 BTS Freq. Sync.

Sub Domain 3 --
Measured Object BTS

....................................................................................................................................................................................................................................
39-22 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP81 - NB_EVALS_RETUNE_TIME_SVR2
IP (QoS)
....................................................................................................................................................................................................................................

Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment Allow to measure when the last OCXO tuning happened:
It is (for the sustained phase): NB_EVALS_RETUNE_TIME_SVR2 * FREQ_SYNC_POLLS_PER_EVAL
* FREQ_SYNC_POLLING_TIME_SUSTAINED
Note: NB_EVALS_RETUNE_TIME_SVR2, FREQ_SYNC_POLLS_PER_EVAL and FREQ_SYNC_POLLING_
TIME_SUSTAINED are defined in the BTP.
Feature Name IP transport in the BSS

IP82 - NB_ACC_EVALS_RETUNE_TIME_SVR1
Descripton

Long Name NB_ACC_EVALS_RETUNE_TIME_SVR1


Definition Cumulated number of accepted evaluations performed by the BTS, using the frequency synchro time server
1, since algorithm restart or OCXO retune.
Trigger condition At the end of each evaluation task using the frequency synchro time server 1: if the calculated gradient is
accepted (i.e. is not considered as an outlier).
Sub Domain 1 IP (QoS)

Sub Domain 2 BTS Freq. Sync.


Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport

External Comment An evaluation is done after a fixed number of polls (parameter FREQ_SYNC_POLLS_PER_EVAL). A new
gradient is calculated using MIN_CLK_DIFF_TIME_SVR1 from this and the last evaluation: If this
gradient is considered to be an outlier (much higher or lower than the average) then the gradient evaluation
is "not accepted".
A "not accepted" evaluation can happen when there was an IP route change with a sudden delay increase or
decrease.
This counter shows the stability of inputs and allows the measurement of the quality of service provided by
the IP network and the time server of the customer:
If this counter is much lower than NB_EVALS_RETUNE_TIME_SVR1, the network to the frequency
synchro time server 1 is not stable enough (many IP route changes or similar) or always overloaded or the
time server is not reliable and the BTS has problems to calculate a confident gradient and to tune the OCXO
Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 39-23
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP83 - NB_ACC_EVALS_RETUNE_TIME_SVR2
IP (QoS)
....................................................................................................................................................................................................................................

IP83 - NB_ACC_EVALS_RETUNE_TIME_SVR2
Descripton

Long Name NB_ACC_EVALS_RETUNE_TIME_SVR2

Definition Cumulated number of accepted evaluations performed by the BTS, using the frequency synchro time server
2, since algorithm restart or OCXO retune.
Trigger condition At the end of each evaluation task using the frequency synchro time server 2: if the calculated gradient is
accepted (i.e. is not considered as an outlier).

Sub Domain 1 IP (QoS)


Sub Domain 2 BTS Freq. Sync.

Sub Domain 3 --

Measured Object BTS


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment An evaluation is done after a fixed number of polls (parameter FREQ_SYNC_POLLS_PER_EVAL). A new
gradient is calculated using MIN_CLK_DIFF_TIME_SVR1 from this and the last evaluation: If this
gradient is considered to be an outlier (much higher or lower than the average) then the gradient evaluation
is "not accepted".
A "not accepted" evaluation can happen when there was an IP route change with a sudden delay increase or
decrease.
This counter shows the stability of inputs and allows the measurement of the quality of service provided by
the IP network and the time server of the customer:
If this counter is much lower than NB_EVALS_RETUNE_TIME_SVR2, the network to the frequency
synchro time server 2 is not stable enough (many IP route changes or similar) or always overloaded or the
time server is not reliable and the BTS has problems to calculate a confident gradient and to tune the OCXO.
Feature Name IP transport in the BSS

IP84 - GRADIENT_TIME_SVR1
Descripton

Long Name GRADIENT_TIME_SVR1

Definition Gradient (calculated frequency offset) of the last accepted evaluation performed by the BTS using the
frequency synchro time server 1.

Trigger condition At the end of evaluation task.

Sub Domain 1 IP (QoS)


Sub Domain 2 BTS Freq. Sync.

Sub Domain 3 --

Measured Object BTS

....................................................................................................................................................................................................................................
39-24 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP84 - GRADIENT_TIME_SVR1
IP (QoS)
....................................................................................................................................................................................................................................

Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment Unit 0.1 ppb
This is the estimated frequency deviation using the MIN_CLK_DIFF_TIME_SVR1 of the last 2
evaluations.
Feature Name IP transport in the BSS

IP85 - GRADIENT_TIME_SVR2
Descripton

Long Name GRADIENT_TIME_SVR2


Definition Gradient (calculated frequency offset) of the last accepted evaluation performed by the BTS using the
frequency synchro time server 2
Trigger condition At the end of evaluation task.

Sub Domain 1 IP (QoS)


Sub Domain 2 BTS Freq. Sync.
Sub Domain 3 --
Measured Object BTS
Type Name IP transport measurements
Type Definition Set of counters related to IP transport
External Comment Unit 0.1 ppb
This is the estimated frequency deviation using the MIN_CLK_DIFF_TIME_SVR2 of the last 2
evaluations.
Feature Name IP transport in the BSS

IP86 - MEAN_GRADIENT_TIME_SVR1
Descripton

Long Name MEAN_GRADIENT_TIME_SVR1


Definition Mean gradient of all accepted evaluations (since the last OCXO tuning) performed by the BTS using the
frequency synchro time server 1 . When this value converges it will be used for the OCXO tuning.
Trigger condition At the end of evaluation task
Sub Domain 1 IP (QoS)

Sub Domain 2 BTS Freq. Sync.

Sub Domain 3 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 39-25
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP86 - MEAN_GRADIENT_TIME_SVR1
IP (QoS)
....................................................................................................................................................................................................................................

Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport

External Comment Unit 0.1 ppb


Feature Name IP transport in the BSS

IP87 - MEAN_GRADIENT_TIME_SVR2
Descripton

Long Name MEAN_GRADIENT_TIME_SVR2


Definition Mean gradient of all accepted evaluations (since the last OCXO tuning) performed by the BTS using the
frequency synchro time server 2. When this value converges it will be used for the OCXO tuning.
Trigger condition At the end of evaluation task.

Sub Domain 1 IP (QoS)


Sub Domain 2 BTS Freq. Sync.
Sub Domain 3 --
Measured Object BTS
Type Name IP transport measurements
Type Definition Set of counters related to IP transport
External Comment Unit 0.1 ppb

Feature Name IP transport in the BSS

IP88 - OCXO_TUNING_TIME_SVR
Descripton

Long Name OCXO_TUNING_TIME_SVR


Definition BTS OCXO last tuning using the frequency synchro time server (0 = no tuning, 1 = primary, 2 = secondary).
Trigger condition At the OCXO tuning.

Sub Domain 1 IP (QoS)

Sub Domain 2 BTS Freq. Sync.


Sub Domain 3 --

Measured Object BTS

Type Name IP transport measurements

....................................................................................................................................................................................................................................
39-26 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP88 - OCXO_TUNING_TIME_SVR
IP (QoS)
....................................................................................................................................................................................................................................

Type Definition Set of counters related to IP transport

External Comment This value shows if there was an OCXO tuning and if yes, by which time server. So the value changes
normally only after several hours or days. Then also OCXO_TUNING_VALUE is changed and the 4
counters NB_EVALS_RETUNE and NB_ACC_EVALS_RETUNE are reset to zero.
Feature Name IP transport in the BSS

IP89 - OCXO_TUNING_VALUE
Descripton

Long Name OCXO_TUNING_VALUE

Definition BTS OCXO last tuning DAC Digital Analog Converter correction value (range 0..4095,).
Trigger condition At the OCXO tuning
Sub Domain 1 IP (QoS)
Sub Domain 2 BTS Freq. Sync.

Sub Domain 3 --
Measured Object BTS
Type Name IP transport measurements
Type Definition Set of counters related to IP transport
External Comment The current OCXO frequency is a linear function of this value.
Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 39-27
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service IP89 - OCXO_TUNING_VALUE

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
39-28 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
40 Traffic Load
40

IP (Traffic Load)

Overview
Purpose
This section contains IP (Traffic Load) parameters.

Contents

IP25a - NB_BSC_SENT_OMLRSL_IP_BYTES 40-3


IP25b - NB_BSC_SENT_OMLRSL_IP_PACKETS 40-3
IP25c - NB_BSC_SENT_OMLRSL_IP_BYTES_MAX_MN 40-4
IP26a - NB_BTS_SENT_OML_IP_BYTES 40-4
IP26b - NB_BTS_SENT_RSL_IP_BYTES 40-5
IP26c - NB_BTS_SENT_OML_IP_PACKETS 40-5
IP26d - NB_BTS_SENT_RSL_IP_PACKETS 40-6
IP27a - NB_BSC_SENT_TCSL_IP_BYTES 40-6
IP27b - NB_BSC_SENT_SS7_IP_BYTES 40-7
IP27c - NB_BSC_SENT_TCSL_IP_PACKETS 40-7
IP27d - NB_BSC_SENT_SS7_IP_PACKETS 40-8
IP27g - NB_BSC_SENT_SS7_IP_BYTES_MAX_MN 40-8
IP27h - NB_BSC_SENT_TCSL_IP_BYTES_MAX_MN 40-9
IP28a - NB_TC_SENT_TCSL_IP_BYTES 40-9
IP28b - NB_TC_SENT_SS7_IP_BYTES 40-10
IP28c - NB_TC_SENT_TCSL_IP_PACKETS 40-10

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 40-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load Overview
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP28d - NB_TC_SENT_SS7_IP_PACKETS 40-11


IP28g - NB_TC_SENT_SS7_IP_BYTES_MAX_MN 40-11
IP28h - NB_TC_SENT_TCSL_IP_BYTES_MAX_MN 40-12
IP29a - NB_BTS_SENT_UL_MUXTRAUP_BYTES 40-12
IP29c - NB_BTS_SENT_UL_MUXTRAUP_PACKETS 40-13
IP30a - NB_TC_SENT_DL_MUXTRAUP_BYTES 40-13
IP30c - NB_TC_SENT_DL_MUXTRAUP_PACKETS 40-14
IP30g - NB_TC_SENT_DL_MUXTRAUP_BYTES_MAX_MN 40-14
IP30n - NB_TC_SENT_DL_MUXTRAUP_KBYTES_BSC 40-15
IP30o - NB_TC_SENT_DL_MUXTRAUP_PACKETS_BSC 40-15
IP30p - NB_TC_SENT_DL_MUXTRAUP_BYTES_MAX_MN_BSC 40-16
IP31a - NB_BTS_SENT_ALL_FLOW_BYTES_MAX_MN 40-16
IP33a - NB_TC_TO_TC_SENT_UL_eTRAUP_BYTES 40-17
IP33c - NB_TC_TO_TC_SENT_UL_eTRAUP_PACKETS 40-17
IP33f - NB_TC_TO_TC_SENT_UL_eTRAUP_BYTES_MAX_MN 40-18
IP35a - NB_BSC_SENT_UL_MUXTRAUP_KBYTES 40-18
IP35b - NB_BSC_SENT_UL_MUXTRAUP_PACKETS 40-19
IP40a - NB_BTS_SENT_IPGCHU_GBR_IP_PACKETS 40-19
IP40d - NB_BTS_SENT_IPGCHU_GBR_IP_BYTES 40-20
IP41a - NB_BTS_SENT_IPGCHU_BE_IP_PACKETS 40-20
IP41d - NB_BTS_SENT_IPGCHU_BE_IP_BYTES 40-21
IP42a - NB_BTS_SENT_IPGCHC_CTRL_TCP_SEGMENTS 40-21
IP42d - NB_BTS_SENT_IPGCHC_CTRL_IP_BYTES 40-22
IP59 - NB_BSC_SENT_DL_MUXTRAUP_BYTES 40-22
IP60 - NB_BSC_SENT_DL_MUXTRAUP_PACKETS 40-23
IP61 - NB_BSC_SENT_DL_MUXTRAUP_BYTES_MAX_MN 40-23

....................................................................................................................................................................................................................................
40-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP25a - NB_BSC_SENT_OMLRSL_IP_BYTES
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP25a - NB_BSC_SENT_OMLRSL_IP_BYTES
Descripton

Long Name NB_BSC_SENT_OMLRSL_IP_BYTES

Definition Counts the cumulated number of bytes of the OML and RSL flows, sent by an IP BSC to a given IP BTS.
Trigger condition Each time an Abis message is sent by the BSC on the OML or on the RSL for a given BTS, this counter is
increased by the number of bytes of this message.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 Abis (Traffic Load IP)

Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport
External Comment --

Feature Name IP transport in the BSS

IP25b - NB_BSC_SENT_OMLRSL_IP_PACKETS
Descripton

Long Name NB_BSC_SENT_OMLRSL_IP_PACKETS


Definition Counts the number of OML and RSL IP packets sent by a IP BSC to a given IP BTS. The purpose is to
measure the used bandwidth by adding the headers size compared to IP25a.
Trigger condition Each time a packet is sent by the BSC on the OML or on the RSL for a given BTS, this counter is increased
by 1. Note that the retransmissions linked to the transport layer (TCP) are also counted.
Sub Domain 1 IP (Traffic Load)

Sub Domain 2 Abis (Traffic Load IP)

Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport

External Comment --
Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 40-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP25c - NB_BSC_SENT_OMLRSL_IP_BYTES_MAX_MN
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP25c - NB_BSC_SENT_OMLRSL_IP_BYTES_MAX_MN
Descripton

Long Name NB_BSC_SENT_OMLRSL_IP_BYTES_MAX_MN

Definition Counts the max number of bytes of the OML and RSL cumulated flows sent by an IP BSC to a given IP
BTS in one minute during the granularity period of monitoring.
Trigger condition Every minute, the number of bytes of each Abis message sent by the BSC on the OML or on the RSL for a
given BTS, is counted. The maximum value obtained for 1 minute during the granularity period of
monitoring is reported.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 Abis (Traffic Load IP)

Sub Domain 3 --
Measured Object BTS
Type Name IP transport measurements
Type Definition Set of counters related to IP transport
External Comment --

Feature Name IP transport in the BSS

IP26a - NB_BTS_SENT_OML_IP_BYTES
Descripton

Long Name NB_BTS_SENT_OML_IP_BYTES


Definition Counts the number of bytes of the OML flow sent by an IP BTS to an IP BSC.
Trigger condition Each time an Abis message is sent by the BTS on the OML to the BSC, this counter is increased by the
number of bytes of this message.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 Abis (Traffic Load IP)

Sub Domain 3 --

Measured Object BTS


Type Name IP transport measurements
Type Definition Set of counters related to IP transport

External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
40-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP26b - NB_BTS_SENT_RSL_IP_BYTES
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP26b - NB_BTS_SENT_RSL_IP_BYTES
Descripton

Long Name NB_BTS_SENT_RSL_IP_BYTES

Definition Counts the number of bytes of the RSL flow sent by an IP BTS to an IP BSC.
Trigger condition Each time an Abis message is sent by the BTS on the RSL to the BSC, this counter is increased by the
number of bytes of this message.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 Abis (Traffic Load IP)

Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport
External Comment --

Feature Name IP transport in the BSS

IP26c - NB_BTS_SENT_OML_IP_PACKETS
Descripton

Long Name NB_BTS_SENT_OML_IP_PACKETS


Definition Counts the number of OML IP packets sent by an IP BTS. The purpose is to measure the used bandwidth by
adding the headers size compared to IP26a.
Trigger condition Each time a packet is sent by the BTS on the OML, this counter is increased by 1. Note that the
retransmissions linked to the transport layer (TCP) are also counted.
Sub Domain 1 IP (Traffic Load)

Sub Domain 2 Abis (Traffic Load IP)

Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport

External Comment --
Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 40-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP26d - NB_BTS_SENT_RSL_IP_PACKETS
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP26d - NB_BTS_SENT_RSL_IP_PACKETS
Descripton

Long Name NB_BTS_SENT_RSL_IP_PACKETS

Definition Counts the number of RSL IP packets sent by an IP BTS. The purpose is to measure the used bandwidth by
adding the headers size compared to IP26b.
Trigger condition Each time a packet is sent by the BTS on the RSL, this counter is increased by 1. Note that the
retransmissions linked to the transport layer (TCP) are also counted.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 Abis (Traffic Load IP)

Sub Domain 3 --

Measured Object BTS


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

IP27a - NB_BSC_SENT_TCSL_IP_BYTES
Descripton

Long Name NB_BSC_SENT_TCSL_IP_BYTES


Definition Counts the number of bytes of the TCSL flow sent by an IP BSC to a given IP TC.
Trigger condition Each time an TCSL message is sent by the BSC to a given TC, this counter is increased by the number of
bytes of this message.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 TCSL (Traffic Load)(BSC-TC O&Mover IP)

Sub Domain 3 --

Measured Object BSC-TC rack


Type Name IP transport measurements
Type Definition Set of counters related to IP transport

External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
40-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP27b - NB_BSC_SENT_SS7_IP_BYTES
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP27b - NB_BSC_SENT_SS7_IP_BYTES
Descripton

Long Name NB_BSC_SENT_SS7_IP_BYTES

Definition Counts the number of bytes of the SS7 flow sent by an IP BSC to a given IP TC.
Trigger condition Each time an SS7 message is sent by the BSC to a given TC, this counter is increased by the number of
bytes of this message.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 SS7 over IP (Traffic Load)(BSC-TC Telecom over IP)

Sub Domain 3 --
Measured Object BSC-TC rack

Type Name IP transport measurements


Type Definition Set of counters related to IP transport
External Comment --

Feature Name IP transport in the BSS

IP27c - NB_BSC_SENT_TCSL_IP_PACKETS
Descripton

Long Name NB_BSC_SENT_TCSL_IP_PACKETS


Definition Counts the number of TCSL packets sent by an IP BSC to a given IP TC. It corresponds to the number of
TCP segments sent, counted by the TCP stack.
Trigger condition Each time a TCP segment containing TCSL packet is sent by the BSC to a given TC, this counter is
increased by 1.
Sub Domain 1 IP (Traffic Load)

Sub Domain 2 TCSL (Traffic Load)(BSC-TC O&Mover IP)

Sub Domain 3 --
Measured Object BSC-TC rack

Type Name IP transport measurements


Type Definition Set of counters related to IP transport

External Comment --
Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 40-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP27d - NB_BSC_SENT_SS7_IP_PACKETS
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP27d - NB_BSC_SENT_SS7_IP_PACKETS
Descripton

Long Name NB_BSC_SENT_SS7_IP_PACKETS

Definition Counts the number of SCTP packets sent by an IP BSC to a given IP TC for the SS7 flow. It corresponds to
is the number of SCTP segments sent, counted by the SCTP stack.
Trigger condition Each time a SCTP segment containing a SS7 packet is sent by the BSC to a given TC, this counter is
increased by 1.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 SS7 over IP (Traffic Load)(BSC-TC Telecom over IP)

Sub Domain 3 --

Measured Object BSC-TC rack


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

IP27g - NB_BSC_SENT_SS7_IP_BYTES_MAX_MN
Descripton

Long Name NB_BSC_SENT_SS7_IP_BYTES_MAX_MN


Definition Counts the max number of bytes of the SS7 flow sent by an IP BSC to a given IP TC in one minute during
the granularity period of monitoring.
Trigger condition Every minute, the number of bytes of each SS7 message sent by the BSC to a given TC, is counted. The
maximum value obtained for 1 minute during the granularity period of monitoring is reported.

Sub Domain 1 IP (Traffic Load)

Sub Domain 2 SS7 over IP (Traffic Load)(BSC-TC Telecom over IP)


Sub Domain 3 --
Measured Object BSC-TC rack

Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
40-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP27h - NB_BSC_SENT_TCSL_IP_BYTES_MAX_MN
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP27h - NB_BSC_SENT_TCSL_IP_BYTES_MAX_MN
Descripton

Long Name NB_BSC_SENT_TCSL_IP_BYTES_MAX_MN

Definition Counts the max number of bytes of the TCSL flow sent by an IP BSC to a given IP TC in one minute during
the granularity period of monitoring.
Trigger condition Every minute, the number of bytes of each TCSL message sent by the BSC to a given TC, is counted. The
maximum value obtained for 1 minute during the granularity period of monitoring is reported.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 TCSL (Traffic Load)(BSC-TC O&Mover IP)

Sub Domain 3 --

Measured Object BSC-TC rack


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

IP28a - NB_TC_SENT_TCSL_IP_BYTES
Descripton

Long Name NB_TC_SENT_TCSL_IP_BYTES


Definition Counts the number of bytes of the TCSL flow sent by an IP TC to a given IP BSC.
Trigger condition Each time an TCSL message is sent by the TC to a given BSC, this counter is increased by the number of
bytes of this message.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 TCSL (Traffic Load)(BSC-TC O&Mover IP)

Sub Domain 3 --

Measured Object BSC-TC rack


Type Name IP transport measurements
Type Definition Set of counters related to IP transport

External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 40-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP28b - NB_TC_SENT_SS7_IP_BYTES
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP28b - NB_TC_SENT_SS7_IP_BYTES
Descripton

Long Name NB_TC_SENT_SS7_IP_BYTES

Definition Counts the number of bytes of the IP_BSS Asig flow sent by an IP TC to a given IP BSC.
Trigger condition Each time an IP_BSSAsig message is sent by a TC to the BSC, this counter is increased by the number of
bytes of this message.
.
Sub Domain 1 IP (Traffic Load)

Sub Domain 2 SS7 over IP (Traffic Load)(BSC-TC Telecom over IP)


Sub Domain 3 --

Measured Object BSC-TC rack


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --
Feature Name IP transport in the BSS

IP28c - NB_TC_SENT_TCSL_IP_PACKETS
Descripton

Long Name NB_TC_SENT_TCSL_IP_PACKETS


Definition Counts the number of TCSL packets sent by an IP TC to a given IP BSC. It corresponds to the number of
TCP segments sent, counted by the TCP stack.
Trigger condition Each time a TCP segment containing TCSL packet is sent by the TC to a given BSC, this counter is
increased by 1.

Sub Domain 1 IP (Traffic Load)

Sub Domain 2 TCSL (Traffic Load)(BSC-TC O&Mover IP)


Sub Domain 3 --
Measured Object BSC-TC rack

Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
40-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP28d - NB_TC_SENT_SS7_IP_PACKETS
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP28d - NB_TC_SENT_SS7_IP_PACKETS
Descripton

Long Name NB_TC_SENT_SS7_IP_PACKETS

Definition Counts the number of SCTP packets sent by an IP TC to a given IP BSC for the IP_BSS Asig flow. It
corresponds to is the number of SCTP segments sent, counted by the SCTP stack.
Trigger condition Each time a SCTP segment containing a IP_BSSAsig packet is sent by a TC to the BSC, this counter is
increased by 1.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 SS7 over IP (Traffic Load)(BSC-TC Telecom over IP)

Sub Domain 3 --

Measured Object BSC-TC rack


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

IP28g - NB_TC_SENT_SS7_IP_BYTES_MAX_MN
Descripton

Long Name NB_TC_SENT_SS7_IP_BYTES_MAX_MN


Definition Counts the max number of bytes of the SS7 flow sent by an IP TC to an IP BSC in one minute during the
granularity period of monitoring.
Trigger condition Every minute, the number of bytes of each SS7 message sent by the TC to the BSC, is counted. The
maximum value obtained for 1 minute during the granularity period of monitoring is reported.

Sub Domain 1 IP (Traffic Load)

Sub Domain 2 SS7 over IP (Traffic Load)(BSC-TC Telecom over IP)


Sub Domain 3 --
Measured Object BSC-TC rack

Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 40-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP28h - NB_TC_SENT_TCSL_IP_BYTES_MAX_MN
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP28h - NB_TC_SENT_TCSL_IP_BYTES_MAX_MN
Descripton

Long Name NB_TC_SENT_TCSL_IP_BYTES_MAX_MN

Definition Counts the max number of bytes of the TCSL flow sent by an IP TC to an IP BSC in one minute during the
granularity period of monitoring.
Trigger condition Every minute, the number of bytes of each TCSL message sent by the TC to the BSC, is counted. The
maximum value obtained for 1 minute during the granularity period of monitoring is reported.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 TCSL (Traffic Load)(BSC-TC O&Mover IP)

Sub Domain 3 --

Measured Object BSC-TC rack


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

IP29a - NB_BTS_SENT_UL_MUXTRAUP_BYTES
Descripton

Long Name NB_BTS_SENT_UL_MUXTRAUP_BYTES


Definition Counts the number of payload bytes of the UL MUXTRAUP packets sent by an IP BTS
Trigger condition Each time an UL MUXTRAUP packet is sent by the IP BTS, this counter is increased by the number of
bytes of the UDP payload of this message. This counter is managed by the SUM.
Only MUXTRAUPs related to traffic are taken into account (e.g.supervision keep alive MUXTRAUPs are
not counted).
The UDP payload of a MUXTRAUP packet is defined as the MUXTRAUP packet format without IP and
UDP header.
Sub Domain 1 IP (Traffic Load)

Sub Domain 2 IPTCH (Traffic Load)(TRAUP frames)

Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --
Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
40-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP29c - NB_BTS_SENT_UL_MUXTRAUP_PACKETS
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP29c - NB_BTS_SENT_UL_MUXTRAUP_PACKETS
Descripton

Long Name NB_BTS_SENT_UL_MUXTRAUP_PACKETS

Definition Counts the number of UL MUXTRAUP packets sent by an IP BTS.


Trigger condition Each time an UL MUXTRAUP packet is sent by the IP BTS, this counter is increased by 1.Only
MUXTRAUPs related to traffic are taken into account (e.g. supervision keep alive MUXTRAUPs are not
counted)

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 IPTCH (Traffic Load)(MUXTRAUP frames)

Sub Domain 3 --

Measured Object BTS


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

IP30a - NB_TC_SENT_DL_MUXTRAUP_BYTES
Descripton

Long Name NB_TC_SENT_DL_MUXTRAUP_BYTES


Definition Definition: Counts the number of payload bytes of the DL MUXTRAUP packets sent by the primary TC
rack to a given IP BTS.
Trigger condition Each time a DL MUXTRAUP packet is sent by the primary TC rack to a given IP BTS, this counter is
increased by the number of bytes of the UDP payload of this message. The UDP payload of a MUXTRAUP
packet is defined as the MUXTRAUP packet format without IP and UDP header.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 IPTCH (Traffic Load)(TRAUP frames)

Sub Domain 3 --

Measured Object BTS


Type Name IP transport measurements
Type Definition Set of counters related to IP transport

External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 40-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP30c - NB_TC_SENT_DL_MUXTRAUP_PACKETS
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP30c - NB_TC_SENT_DL_MUXTRAUP_PACKETS
Descripton

Long Name NB_TC_SENT_DL_MUXTRAUP_PACKETS

Definition Counts the number of DL MUXTRAUP packets sent by the primary IP TC rack to a given IP BTS.
Trigger condition Each time a DL MUXTRAUP packet is sent by the primary TC to a given BTS, this counter is increased by
1.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 IPTCH (Traffic Load)(MUXTRAUP frames)

Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport
External Comment --

Feature Name IP transport in the BSS

IP30g - NB_TC_SENT_DL_MUXTRAUP_BYTES_MAX_MN
Descripton

Long Name NB_TC_SENT_DL_MUXTRAUP_BYTES_MAX_MN


Definition Counts the max number of payload bytes of the DL MUXTRAUP packets sent by primary TC rack to an IP
BTS in one minute during the granularity period of monitoring.
Trigger condition Every minute, the number of UDP payload bytes of the DL MUXTRAUP packets sent by the primary TC
rack to a given IP BTS, is counted. The maximum value obtained for 1 minute during the granularity period
of monitoring is reported.
The UDP payload of a MUXTRAUP packet is defined as the MUXTRAUP packet format without IP and
UDP header.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 IPTCH (Traffic Load)(TRAUP frames)

Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
40-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP30n - NB_TC_SENT_DL_MUXTRAUP_KBYTES_BSC
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP30n - NB_TC_SENT_DL_MUXTRAUP_KBYTES_BSC
Descripton

Long Name NB_TC_SENT_DL_MUXTRAUP_KBYTES_BSC

Definition Definition: Counts the number of payload kilobytes of the DL MUXTRAUP packets sent by a primary TC
rack to a BSC.
Trigger condition Each time a DL MUXTRAUP packet is sent by a primary TC rack to BSC, this counter is increased by the
number of bytes of the UDP payload of this message. At accumulation period the counter is calculated in
Kilo (1000) bytes.The UDP payload of a MUXTRAUP packet is defined as the MUXTRAUP packet format
without IP and UDP header.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 IPTCH (Traffic Load)(MUXTRAUP frames)

Sub Domain 3 --
Measured Object BSC-TC rack
Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name AUPoIP A interface user plane over IP

IP30o - NB_TC_SENT_DL_MUXTRAUP_PACKETS_BSC
Descripton

Long Name NB_TC_SENT_DL_MUXTRAUP_PACKETS_BSC


Definition Counts the number of DL IPTCH packets (i.e. MUXTRAUP frames) sent by a primary IP TC rack to a BSC.
Trigger condition Each time a DL MUXTRAUP packet is sent by a primary TC rack to a BSC, this counter is increased by 1.
Sub Domain 1 IP (Traffic Load)

Sub Domain 2 IPTCH (Traffic Load)(MUXTRAUP frames)


Sub Domain 3 --

Measured Object BSC-TC rack

Type Name IP transport measurements


Type Definition Set of counters related to IP transport
External Comment --

Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 40-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP30p - NB_TC_SENT_DL_MUXTRAUP_BYTES_MAX_MN_BSC
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP30p - NB_TC_SENT_DL_MUXTRAUP_BYTES_MAX_MN_BSC
Descripton

Long Name NB_TC_SENT_DL_MUXTRAUP_BYTES_MAX_MN_BSC

Definition Counts the max number of payload bytes of the DL MUXTRAUP packets sent by a primary TC rack to a
BSC in one minute during the granularity period of monitoring.
Trigger condition Every minute, the number of UDP payload bytes of the DL MUXTRAUP packets sent by a primary TC
rackto a BSC, is counted. The maximum value obtained for 1 minute during the granularity period of
monitoring is reported. The UDP payload of a MUXTRAUP packet is defined as the MUXTRAUP packet
format without IP and UDP header.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 IPTCH (Traffic Load)(MUXTRAUP frames)

Sub Domain 3 --
Measured Object BSC-TC rack
Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name AUPoIP A interface user plane over IP

IP31a - NB_BTS_SENT_ALL_FLOW_BYTES_MAX_MN
Descripton

Long Name NB_BTS_SENT_ALL_FLOW_BYTES_MAX_MN


Definition Counts the maximum number of bytes sent by an IP BTS for all the flows in one minute during the
granularity period of monitoring (i.e. IPTCH+IPGCHC+IPGCHU+RSL+OML).

Trigger condition Every minute, the number of bytes of all the message/frame sent by the IP BTS, is counted. The maximum
value obtained for 1 minute during the granularity period of monitoring is reported.
Sub Domain 1 IP (Traffic Load)

Sub Domain 2 --
Sub Domain 3 --

Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport

External Comment --
Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
40-16 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP33a - NB_TC_TO_TC_SENT_UL_eTRAUP_BYTES
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP33a - NB_TC_TO_TC_SENT_UL_eTRAUP_BYTES
Descripton

Long Name NB_TC_TO_TC_SENT_UL_eTRAUP_BYTES

Definition Counts the number of payload bytes of the UL eTRAUP packets sent by the primaryTC rack to all other TC
racks during the Granularity Period..
Trigger condition Each time the primary TC rack sends an eTRAUP packet (UL) to any other TC rack, this counter is
increased by the number of bytes of the UDP payload of the eTRAUP packet. Such routing is performed in
the TCIF board. The UDP payload of an eTRAUP packet is defined as the eTRAUP packet format without
IP and UDP header.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 --

Sub Domain 3 --
Measured Object TC rack
Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

IP33c - NB_TC_TO_TC_SENT_UL_eTRAUP_PACKETS
Descripton

Long Name NB_TC_TO_TC_SENT_UL_eTRAUP_PACKETS


Definition Counts the number of eTRAUP packets (UL) sent by the primary TC rack to all other TC racks during the
Granularity Period.

Trigger condition Each time the primary TC rack sends a eTRAUP packet (UL) to another TC rack, this counter is increased
by 1. Such routing is performed in the TCIF board.
Sub Domain 1 IP (Traffic Load)

Sub Domain 2 --
Sub Domain 3 --

Measured Object TC rack

Type Name IP transport measurements


Type Definition Set of counters related to IP transport

External Comment --
Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 40-17
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP33f - NB_TC_TO_TC_SENT_UL_eTRAUP_BYTES_MAX_MN
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP33f - NB_TC_TO_TC_SENT_UL_eTRAUP_BYTES_MAX_MN
Descripton

Long Name NB_TC_TO_TC_SENT_UL_eTRAUP_BYTES_MAX_MN

Definition Counts the max number of IPTCH bytes (i.e. TRAUP frames) sent by the primary TC to all other TC racks
in one minute during the granularity period of monitoring.
Trigger condition Every minute, the number of bytes of all the TRAUP frames sent by the primary TC to secondary TC racks,
is counted. The maximum value obtained for 1 minute during the granularity period of monitoring is
reported. The UDP payload of an eTRAUP packet is defined as the eTRAUP packet format without IP and
UDP header.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 --

Sub Domain 3 --
Measured Object TC rack
Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

IP35a - NB_BSC_SENT_UL_MUXTRAUP_KBYTES
Descripton

Long Name NB_BSC_SENT_UL_MUXTRAUP_KBYTES


Definition Counts the number of payload kilobytes of the UL MUXTRAUP packets sent by the BSC to a given TC
Trigger condition Each time an UL MUXTRAUP packet is sent by a BSC to a given TC, this counter is increased by the
number of bytes of the UDP payload of this message. At accumulation period the counter is calculated in
Kilo (1000) bytes.Only MUXTRAUPs related to traffic are taken into account (e.g. supervision keep alive
MUXTRAUPs are not counted). The UDP payload of a MUXTRAUP packet is defined as the MUXTRAUP
packet format without IP and UDP header.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 IPTCH (Traffic Load)(MUXTRAUP frames)
Sub Domain 3 --

Measured Object BSC-TC rack

Type Name IP transport measurements


Type Definition Set of counters related to IP transport

External Comment --
Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
40-18 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP35b - NB_BSC_SENT_UL_MUXTRAUP_PACKETS
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP35b - NB_BSC_SENT_UL_MUXTRAUP_PACKETS
Descripton

Long Name NB_BSC_SENT_UL_MUXTRAUP_PACKETS

Definition Counts the number of UL MUXTRAUP packets sent by the BSC to a given TC
Trigger condition Each time an UL MUXTRAUP packet is sent by the BSC to a given TC, this counter is increased by 1. Only
MUXTRAUPs related to traffic are taken into account (e.g. supervision keep alive MUXTRAUPs are not
counted).

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 IPTCH (Traffic Load)(MUXTRAUP frames)

Sub Domain 3 --

Measured Object BSC-TC rack


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name AUPoIP A interface user plane over IP

IP40a - NB_BTS_SENT_IPGCHU_GBR_IP_PACKETS
Descripton

Long Name NB_BTS_SENT_IPGCHU_GBR_IP_PACKETS


Definition Counts the number of IPGCHU segments sent by an IP BTS to the MFS for the GBR flow.
Trigger condition Each time the BTS sends an UL IPGCHU segment (from any TRE) to the MFS for a GBR flow, this counter
is increased by 1. This counter is managed by the SUM board. Retransmissions are not counted here.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 IPGCHU (Traffic Load)

Sub Domain 3 --

Measured Object BTS


Type Name IP transport measurements
Type Definition Set of counters related to IP transport

External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 40-19
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP40d - NB_BTS_SENT_IPGCHU_GBR_IP_BYTES
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP40d - NB_BTS_SENT_IPGCHU_GBR_IP_BYTES
Descripton

Long Name NB_BTS_SENT_IPGCHU_GBR_IP_BYTES

Definition Counts the number of bytes of the IPGCHU segments sent by an IP BTS to the MFS for the GBR flow.
Trigger condition Each time the BTS sends an UL IPGCHU segment (from any TRE) to the MFS for a GBR flow, this counter
is increased by the number of bytes of this segment. This counter is managed by the SUM board.
Retransmissions are not counted here.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 IPGCHU (Traffic Load)

Sub Domain 3 --

Measured Object BTS


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

IP41a - NB_BTS_SENT_IPGCHU_BE_IP_PACKETS
Descripton

Long Name NB_BTS_SENT_IPGCHU_BE_IP_PACKETS


Definition Counts the number of IPGCHU segments sent by an IP BTS to the MFS for the BE flow.
Trigger condition Each time the BTS sends an UL IPGCHU segment (from any TRE) to the MFS for a BE flow, this counter is
increased by 1. This counter is managed by the SUM board. Retransmissions are not counted here.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 IPGCHU (Traffic Load)

Sub Domain 3 --

Measured Object BTS


Type Name IP transport measurements
Type Definition Set of counters related to IP transport

External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
40-20 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP41d - NB_BTS_SENT_IPGCHU_BE_IP_BYTES
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP41d - NB_BTS_SENT_IPGCHU_BE_IP_BYTES
Descripton

Long Name NB_BTS_SENT_IPGCHU_BE_IP_BYTES

Definition Counts the number of bytes of the IPGCHU segments sent by an IP BTS to the MFS for the BE flow.
Trigger condition Each time the BTS sends an UL IPGCHU segment (from any TRE) to the MFS for a BE flow, this counter is
increased by the number of bytes of this segment. This counter is managed by the SUM board.
Retransmissions are not counted here.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 IPGCHU (Traffic Load)

Sub Domain 3 --

Measured Object BTS


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

IP42a - NB_BTS_SENT_IPGCHC_CTRL_TCP_SEGMENTS
Descripton

Long Name NB_BTS_SENT_IPGCHC_CTRL_TCP_SEGMENTS


Definition Counts the number of IPGCHC TCP segments sent by an IP BTS to the MFS for the IPGCH control flow.
Trigger condition Each time the BTS sends an UL IPGCHC TCP segment (from any TRE) to the MFS, this counter is
increased by 1. IPGCHC TCP retransmissions are also counted, as this counter is managed by the SUM
(considered as acceptable, as the IPGCH retransmissions should be rare).

Sub Domain 1 IP (Traffic Load)

Sub Domain 2 IPGCHC (Traffic Load)


Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 40-21
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP42d - NB_BTS_SENT_IPGCHC_CTRL_IP_BYTES
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP42d - NB_BTS_SENT_IPGCHC_CTRL_IP_BYTES
Descripton

Long Name NB_BTS_SENT_IPGCHC_CTRL_IP_BYTES

Definition Counts the number of bytes of the IPGCHC TCP segments sent by an IP BTS to the MFS for the IPGCH
control flow.
Trigger condition Each time the BTS sends an UL IPGCHC TCP segment (from any TRE) to the MFS, this counter is
increased by the number of bytes of this TCP segment. IPGCHC TCP retransmissions are also counted, as
this counter is managed by the SUM (considered as acceptable, as the IPGCH retransmissions should be
rare).

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 IPGCHC (Traffic Load)

Sub Domain 3 --
Measured Object BTS
Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name IP transport in the BSS

IP59 - NB_BSC_SENT_DL_MUXTRAUP_BYTES
Descripton

Long Name NB_BSC_SENT_DL_MUXTRAUP_BYTES


Definition Counts the number of payload bytes of the DL MUXTRAUP packets sent by the BSC to a given IP BTS
Trigger condition Each time a DL MUXTRAUP packet is sent by a BSC to a given IP BTS, this counter is increased by the
number of bytes of the UDP payload of this message. The UDP payload of a MUXTRAUP packet is defined
as the MUXTRAUP packet format without IP and UDP header.
Sub Domain 1 IP (Traffic Load)

Sub Domain 2 IPTCH (Traffic Load)(MUXTRAUP frames)


Sub Domain 3 --

Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport

External Comment --
Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
40-22 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP60 - NB_BSC_SENT_DL_MUXTRAUP_PACKETS
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP60 - NB_BSC_SENT_DL_MUXTRAUP_PACKETS
Descripton

Long Name NB_BSC_SENT_DL_MUXTRAUP_PACKETS

Definition Counts the number of DL IPTCH packets (i.e. MUXTRAUP frames) sent by the BSC to a given IP BTS
Trigger condition Each time a DL MUXTRAUP packet is sent by the BSC to a given BTS, this counter is increased by 1.

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 IPTCH (Traffic Load)(MUXTRAUP frames)

Sub Domain 3 --
Measured Object BTS

Type Name IP transport measurements


Type Definition Set of counters related to IP transport
External Comment --
Feature Name AUPoIP A interface user plane over IP

IP61 - NB_BSC_SENT_DL_MUXTRAUP_BYTES_MAX_MN
Descripton

Long Name NB_BSC_SENT_DL_MUXTRAUP_BYTES_MAX_MN


Definition Counts the max number of payload bytes of the DL MUXTRAUP packets sent by the BSC to an IP BTS in
one minute during the granularity period of monitoring
Trigger condition Every minute, the number of UDP payload bytes of the DL MUXTRAUP packets sent by the BSC to a
given IP BTS, is counted. The maximum value obtained for 1 minute during the granularity period of
monitoring is reported.The UDP payload of a MUXTRAUP packet is defined as the MUXTRAUP packet
format without IP and UDP header.
Sub Domain 1 IP (Traffic Load)
Sub Domain 2 IPTCH (Traffic Load)(MUXTRAUP frames)

Sub Domain 3 --

Measured Object BTS


Type Name IP transport measurements

Type Definition Set of counters related to IP transport


External Comment --

Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 40-23
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load IP61 - NB_BSC_SENT_DL_MUXTRAUP_BYTES_MAX_MN

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
40-24 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XXIII: BSC-TYPE 36 - Iur-g
interface measurements

Overview
Purpose
All type 36.

Contents

Chapter 41, Traffic Load 41-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XXIII-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 36 - Iur-g interface measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XXIII-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
41 Traffic Load
41

Interface (Traffic Load)

Overview
Purpose
This section contains Interface (Traffic Load) parameters.

Contents

MC1301 - NB_BSC_SENT_SS7_IP_BYTES_IURG 41-2


MC1302 - NB_BSC_SENT_SS7_IP_PACKETS_IURG 41-2
MC1303 - NB_BSC_RESENT_SS7_IP_PACKETS_IURG 41-3
MC1304 - NB_BSC_SENT_SS7_IP_BYTES_MAX_MN_IURG 41-3
MC1305 - NB_N7_CON_REQ_REC_IURG 41-4
MC1306 - NB_N7_CON_CONF_SENT_IURG 41-4

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 41-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1301 - NB_BSC_SENT_SS7_IP_BYTES_IURG
Interface (Traffic Load)
....................................................................................................................................................................................................................................

MC1301 - NB_BSC_SENT_SS7_IP_BYTES_IURG
Descripton

Long Name NB_BSC_SENT_SS7_IP_BYTES_IURG

Definition Counts the number of bytes of the SS7 flow sent by a BSC to the RNC when Iur-g is used.
Trigger condition Each time an SS7 message is sent by the BSC to the RNC on the Iur-g interface, this counter is increased by
the number of bytes of this message.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 Iur-g (Traffic Load)

Sub Domain 3 --
Measured Object BSC_RNC

Type Name Iur-g interface measurements


Type Definition Set of counters related to Iur-g interface
External Comment --

Feature Name Iur-g

MC1302 - NB_BSC_SENT_SS7_IP_PACKETS_IURG
Descripton

Long Name NB_BSC_SENT_SS7_IP_PACKETS_IURG


Definition Counts the number of SCTP packets sent by a BSC to a given RNC for the SS7 flow when Iur-g interface is
used. It corresponds to the number of SCTP segments sent, counted by the SCTP stack.
Trigger condition Each time a SCTP segment containing a SS7 packet is sent by the BSC to the RNC, this counter is increased
by 1.
Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 Iur-g (Traffic Load)

Sub Domain 3 --
Measured Object BSC_RNC

Type Name Iur-g interface measurements


Type Definition Set of counters related to Iur-g interface

External Comment --
Feature Name Iur-g

....................................................................................................................................................................................................................................
41-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1303 - NB_BSC_RESENT_SS7_IP_PACKETS_IURG
Interface (Traffic Load)
....................................................................................................................................................................................................................................

MC1303 - NB_BSC_RESENT_SS7_IP_PACKETS_IURG
Descripton

Long Name NB_BSC_RESENT_SS7_IP_PACKETS_IURG

Definition Counts the number of SCTP packets resent by a BSC to a given RNC for the SS7 flow, when Iur-g interface
is used.
Trigger condition Each time a SCTP segment containing a SS7 packet is resent by the BSC to a given RNC with Iur-g
interface, this counter is increased by 1

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 Iur-g (Traffic Load)

Sub Domain 3 --

Measured Object BSC_RNC


Type Name Iur-g interface measurements

Type Definition Set of counters related to Iur-g interface


External Comment --

Feature Name Iur-g

MC1304 - NB_BSC_SENT_SS7_IP_BYTES_MAX_MN_IURG
Descripton

Long Name NB_BSC_SENT_SS7_IP_BYTES_MAX_MN_IURG


Definition Counts the max number of bytes of the SS7 flow sent by a BSC to a given RNC in one minute during the
granularity period of monitoring, when Iur-g interface is used.
Trigger condition Every minute, the number of bytes of each SS7 message sent by the BSC to a given RNC over the Iur-g
interface, is counted. The maximum value obtained for 1 minute during the granularity period of monitoring
is reported.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 Iur-g (Traffic Load)

Sub Domain 3 --

Measured Object BSC_RNC


Type Name Iur-g interface measurements
Type Definition Set of counters related to Iur-g interface

External Comment --

Feature Name Iur-g

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 41-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1305 - NB_N7_CON_REQ_REC_IURG
Interface (Traffic Load)
....................................................................................................................................................................................................................................

MC1305 - NB_N7_CON_REQ_REC_IURG
Descripton

Long Name NB_N7_CON_REQ_REC_IURG

Definition Number of CONNECTION REQUEST received from the RNC by the BSC, when Iur-g interface is used.
Trigger condition Whenever a CONNECTION REQUEST message is received on Iur-g interface by the BSC from the RNC,
when Iur-g is used.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 Iur-g (Traffic Load)

Sub Domain 3 --
Measured Object BSC_RNC

Type Name Iur-g interface measurements


Type Definition Set of counters related to Iur-g interface
External Comment --

Feature Name Iur-g

MC1306 - NB_N7_CON_CONF_SENT_IURG
Descripton

Long Name NB_N7_CON_CONF_SENT_IURG


Definition Number of CONNECTION CONFIRM sent to the RNC by the BSC, when Iur-g interface is used.
Trigger condition Whenever a CONNECTION CONFIRM message is sent by the BSC to the RNC, when Iur-g interface is
used.
Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 Iur-g (Traffic Load)


Sub Domain 3 --

Measured Object BSC_RNC

Type Name Iur-g interface measurements


Type Definition Set of counters related to Iur-g interface

External Comment --
Feature Name Iur-g

....................................................................................................................................................................................................................................
41-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1306 - NB_N7_CON_CONF_SENT_IURG

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 41-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1306 - NB_N7_CON_CONF_SENT_IURG

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
41-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XXIV: BSC-TYPE 37 - VAMOS
measurements

Overview
Purpose
All type 37.

Contents

Chapter 42, Handover 42-1


Chapter 43, Quality of Service 43-1
Chapter 44, Resource Availability & Usage 44-1
Chapter 45, Traffic Load 45-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XXIV-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 37 - VAMOS measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XXIV-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
42 Handover
42

TCH

Overview
Purpose
This section contains TCH parameters.

Contents

MC1404a - NB_TCH_PAIR_HO_ATPT_NON_SAIC 42-2


MC1404b - NB_TCH_PAIR_HO_ATPT_SAIC 42-2
MC1404c - NB_TCH_PAIR_HO_ATPT_VAMOS1 42-3
MC1404d - NB_TCH_PAIR_HO_ATPT_VAMOS2 42-3
MC1405a - NB_TCH_PAIR_HO_SUCC_NON_SAIC 42-4
MC1405b - NB_TCH_PAIR_HO_SUCC_SAIC 42-4
MC1405c - NB_TCH_PAIR_HO_SUCC_VAMOS1 42-5
MC1405d - NB_TCH_PAIR_HO_SUCC_VAMOS2 42-5
MC1420a - NB_TCH_HO_ATPT_35_pairing_NON_SAIC 42-6
MC1420b - NB_TCH_HO_ATPT_35_pairing_SAIC 42-6
MC1420c - NB_TCH_HO_ATPT_35_pairing_VAMOS1 42-7
MC1420d - NB_TCH_HO_ATPT_35_pairing_VAMOS2 42-8
MC1421a - NB_TCH_HO_ATPT_34_unpairing_NON_SAIC 42-8
MC1421b - NB_TCH_HO_ATPT_34_unpairing_SAIC 42-9
MC1421c - NB_TCH_HO_ATPT_34_unpairing_VAMOS1 42-9
MC1421d - NB_TCH_HO_ATPT_34_unpairing_VAMOS2 42-10

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 42-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover Overview
TCH
....................................................................................................................................................................................................................................

MC1424a - NB_INTRA_TCH_HO_35_PREP_FAIL_NO_PAIRING 42-10

MC1404a - NB_TCH_PAIR_HO_ATPT_NON_SAIC
Descripton

Long Name NB_TCH_PAIR_HO_ATPT_NON_SAIC

Definition Number of intra-cell TCH (in HR or FR usage) handover with VAMOS pairing attempt related to non-SAIC
capable MS
Trigger condition Whenever the BSC process responsible for the handover procedure starts an intra cell TCH handover
procedure (any causes) with a VAMOS pairing attempt (48.058 CHANNEL ACTIVATION sent to the BTS,
indicating a channel in VAMOS mode) related to a non-SAIC capable MS .

Sub Domain 1 TCH


Sub Domain 2 Intra
Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1404b - NB_TCH_PAIR_HO_ATPT_SAIC
Descripton

Long Name NB_TCH_PAIR_HO_ATPT_SAIC

Definition Number of intra-cell TCH (in HR or FR usage) handover with VAMOS pairing attempt related to SAIC
capable MS.

Trigger condition Whenever the BSC process responsible for the handover procedure starts an intra cell TCH handover
procedure (any causes) with a VAMOS pairing attempt (48.058 CHANNEL ACTIVATION sent to the BTS,
indicating a channel in VAMOS mode) related to a SAIC capable MS .

Sub Domain 1 TCH


Sub Domain 2 Intra

Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS

....................................................................................................................................................................................................................................
42-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC1404b - NB_TCH_PAIR_HO_ATPT_SAIC
TCH
....................................................................................................................................................................................................................................

External Comment --

Feature Name VAMOS

MC1404c - NB_TCH_PAIR_HO_ATPT_VAMOS1
Descripton

Long Name NB_TCH_PAIR_HO_ATPT_VAMOS1

Definition Number of intra-cell TCH (in HR or FR usage) handover with VAMOS pairing attempt related to VAMOS-1
capable MS.
Trigger condition Whenever the BSC process responsible for the handover procedure starts an intra cell TCH handover
procedure (any causes) with a VAMOS pairing attempt (48.058 CHANNEL ACTIVATION sent to the BTS,
indicating a channel in VAMOS mode) related to a VAMOS-1 capable MS .

Sub Domain 1 TCH


Sub Domain 2 Intra
Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1404d - NB_TCH_PAIR_HO_ATPT_VAMOS2
Descripton

Long Name NB_TCH_PAIR_HO_ATPT_VAMOS2


Definition Number of intra-cell TCH (in HR or FR usage) handover with VAMOS pairing attempt related to VAMOS-2
capable MS.

Trigger condition Whenever the BSC process responsible for the handover procedure starts an intra cell TCH handover
procedure (any causes) with a VAMOS pairing attempt (48.058 CHANNEL ACTIVATION sent to the BTS,
indicating a channel in VAMOS mode) concerning VAMOS-2 capable mobiles.
Sub Domain 1 TCH

Sub Domain 2 Intra

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 42-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC1404d - NB_TCH_PAIR_HO_ATPT_VAMOS2
TCH
....................................................................................................................................................................................................................................

Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1405a - NB_TCH_PAIR_HO_SUCC_NON_SAIC
Descripton

Long Name NB_TCH_PAIR_HO_SUCC_NON_SAIC

Definition Number of intra-cell TCH (in HR or FR usage) handover successes related to non-SAIC capable MS that are
established in Vamos mode (after pairing).
Trigger condition Whenever a 44.018 ASSIGNMENT COMPLETE message is received on Abis interface on the target
channel for a TCH channel established in Vamos mode (after pairing), involved in an internal intra-cell TCH
handover and related to a non-SAIC capable MS.

Sub Domain 1 TCH


Sub Domain 2 Intra
Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1405b - NB_TCH_PAIR_HO_SUCC_SAIC
Descripton

Long Name NB_TCH_PAIR_HO_SUCC_SAIC


Definition Number of intra-cell TCH (in HR or FR usage) handover successes related to SAIC capable MS that are
established in Vamos mode (after pairing).

Trigger condition Whenever a 44.018 ASSIGNMENT COMPLETE message is received on Abis interface on the target
channel for a TCH channel established in Vamos mode (after pairing), involved in an internal intra-cell TCH
handover and related to a SAIC capable MS.
Sub Domain 1 TCH

Sub Domain 2 Intra


Sub Domain 3 --

Measured Object Common cell

....................................................................................................................................................................................................................................
42-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC1405b - NB_TCH_PAIR_HO_SUCC_SAIC
TCH
....................................................................................................................................................................................................................................

Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

MC1405c - NB_TCH_PAIR_HO_SUCC_VAMOS1
Descripton

Long Name NB_TCH_PAIR_HO_SUCC_VAMOS1

Definition Number of intra-cell TCH (in HR or FR usage) handover successes related to legacy VAMOS-1 capable MS
that are established in Vamos mode (after pairing).
Trigger condition Whenever a 44.018 ASSIGNMENT COMPLETE message is received on Abis interface on the target
channel for a TCH channel established in Vamos mode (after pairing), involved in an internal intra-cell TCH
handover and related to a VAMOS-1 capable MS.

Sub Domain 1 TCH


Sub Domain 2 Intra
Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1405d - NB_TCH_PAIR_HO_SUCC_VAMOS2
Descripton

Long Name NB_TCH_PAIR_HO_SUCC_VAMOS2


Definition Number of intra-cell TCH (in HR or FR usage) handover successes related to legacy VAMOS-2 capable MS
that are established in Vamos mode (after pairing).
Trigger condition Whenever a 44.018 ASSIGNMENT COMPLETE message is received on Abis interface on the target
channel for a TCH channel established in Vamos mode (after pairing), involved in an internal intra-cell TCH
handover and related to a VAMOS-2 capable MS.
Sub Domain 1 TCH

Sub Domain 2 Intra

Sub Domain 3 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 42-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC1405d - NB_TCH_PAIR_HO_SUCC_VAMOS2
TCH
....................................................................................................................................................................................................................................

Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1420a - NB_TCH_HO_ATPT_35_pairing_NON_SAIC
Descripton

Long Name NB_TCH_HO_ATPT_35_pairing_NON_SAIC


Definition Number of handover attempts, with the cause 35 (VAMOS pairing channel adaptation: Good radio quality,
high signal level and high load leading to handover of one user on a VAMOS channel) related to non-SAIC
capable MS.
Trigger condition Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTS because of intra-cell
handover cause 35 on TCH related to non-SAIC capable MS.

Sub Domain 1 TCH


Sub Domain 2 Cause
Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1420b - NB_TCH_HO_ATPT_35_pairing_SAIC
Descripton

Long Name NB_TCH_HO_ATPT_35_pairing_SAIC

Definition Number of handover attempts, with the cause 35 (VAMOS pairing channel adaptation: Good radio quality,
high signal level and high load leading to handover of one user on a VAMOS channel) related to SAIC
capable MS.

Trigger condition Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTS because of intra-cell
handover cause 35 on TCH related to SAIC capable MS.

Sub Domain 1 TCH

Sub Domain 2 Cause

....................................................................................................................................................................................................................................
42-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC1420b - NB_TCH_HO_ATPT_35_pairing_SAIC
TCH
....................................................................................................................................................................................................................................

Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

MC1420c - NB_TCH_HO_ATPT_35_pairing_VAMOS1
Descripton

Long Name NB_TCH_HO_ATPT_35_pairing_VAMOS1


Definition Number of handover attempts, with the cause 35 (VAMOS pairing channel adaptation: Good radio quality,
high signal level and high load leading to handover of one user on a VAMOS channel) related to VAMOS1
capable MS.

Trigger condition Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTS because of intra-cell
handover cause 35 on TCH related to VAMOS1 capable MS.
Sub Domain 1 TCH

Sub Domain 2 Cause


Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 42-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC1420d - NB_TCH_HO_ATPT_35_pairing_VAMOS2
TCH
....................................................................................................................................................................................................................................

MC1420d - NB_TCH_HO_ATPT_35_pairing_VAMOS2
Descripton

Long Name NB_TCH_HO_ATPT_35_pairing_VAMOS2

Definition Number of handover attempts, with the cause 35 (VAMOS pairing channel adaptation: Good radio quality,
high signal level and high load leading to handover of one user on a VAMOS channel) related to VAMOS2
capable MS.
Trigger condition Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTS because of intra-cell
handover cause 35 on TCH related to VAMOS2 capable MS.

Sub Domain 1 TCH


Sub Domain 2 Cause

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1421a - NB_TCH_HO_ATPT_34_unpairing_NON_SAIC
Descripton

Long Name NB_TCH_HO_ATPT_34_unpairing_NON_SAIC


Definition Number of handover attempts, with the cause 34 (VAMOS unpairing channel adaptation: Too bad radio
quality for a VAMOS subchannel leading to handover of one or both paired user) related to non-SAIC
capable MS.
Trigger condition Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTS because of intra-cell
handover cause 34 on TCH related to non-SAIC capable MS.

Sub Domain 1 TCH


Sub Domain 2 Cause

Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS

External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
42-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC1421b - NB_TCH_HO_ATPT_34_unpairing_SAIC
TCH
....................................................................................................................................................................................................................................

MC1421b - NB_TCH_HO_ATPT_34_unpairing_SAIC
Descripton

Long Name NB_TCH_HO_ATPT_34_unpairing_SAIC

Definition Number of handover attempts, with the cause 34 (VAMOS unpairing channel adaptation: Too bad radio
quality for a VAMOS subchannel leading to handover of one or both paired user) related to SAIC capable
MS.
Trigger condition Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTS because of intra-cell
handover cause 34 on TCH related to SAIC capable MS.

Sub Domain 1 TCH


Sub Domain 2 Cause

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1421c - NB_TCH_HO_ATPT_34_unpairing_VAMOS1
Descripton

Long Name NB_TCH_HO_ATPT_34_unpairing_VAMOS1


Definition Number of handover attempts, with the cause 34 (VAMOS unpairing channel adaptation: Too bad radio
quality for a VAMOS subchannel leading to handover of one or both paired user) related to VAMOS1
capable MS.
Trigger condition Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTS because of intra-cell
handover cause 34 on TCH related to VAMOS1 capable MS.

Sub Domain 1 TCH


Sub Domain 2 Cause

Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS

External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 42-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC1421d - NB_TCH_HO_ATPT_34_unpairing_VAMOS2
TCH
....................................................................................................................................................................................................................................

MC1421d - NB_TCH_HO_ATPT_34_unpairing_VAMOS2
Descripton

Long Name NB_TCH_HO_ATPT_34_unpairing_VAMOS2

Definition Number of handover attempts, with the cause 34 (VAMOS unpairing channel adaptation: Too bad radio
quality for a VAMOS subchannel leading to handover of one or both paired user) related to VAMOS2
capable MS.
Trigger condition Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTS because of intra-cell
handover cause 34 on TCH related to VAMOS2 capable MS.

Sub Domain 1 TCH


Sub Domain 2 Cause

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1424a - NB_INTRA_TCH_HO_35_PREP_FAIL_NO_PAIRING
Descripton

Long Name NB_INTRA_TCH_HO_35_PREP_FAIL_NO_PAIRING


Definition Number of intra-cell TCH (in HR or FR usage) handover cause 35 (VAMOS pairing) preparation failures
due to no pairing target found.
Trigger condition Whenever an internal intra-cell TCH handover cause 35 (VAMOS pairing) cannot be performed, because
there is no pairing target available to serve the handover.

Sub Domain 1 TCH

Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
42-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
43 Quality of Service
43

Channel

Overview
Purpose
This section contains Channel parameters.

Contents

MC1426d - DISTRIB_4_SCPIR_NON_SAIC_SAIC 43-1

MC1426d - DISTRIB_4_SCPIR_NON_SAIC_SAIC
Descripton

Long Name DISTRIB_4_SCPIR_NON_SAIC_SAIC


Definition Fourth cell of distribution of SCPIR for a TCH in non SAIC MS / SAIC MS pair or SAIC / non SAIC pair.
A non SAIC MS is a MS which does not indicate SAIC capability in Classmark.
This pair is only possible when the non SAIC MS is in reality a SAIC MS which does not declare its SAIC
capability to the network.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a non SAIC MS / SAIC MS pair or SAIC / non
SAIC pair whose SCPIR lies during a measurement reporting period within the fourth SCPIR range defined
by the values above the threshold
[SCPIR_SAIC_SAIC_THR_3.
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 43-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1426d - DISTRIB_4_SCPIR_NON_SAIC_SAIC
Channel
....................................................................................................................................................................................................................................

Trigger condition This counter is incremented when a SCPIR in the range 4 is applied to a channel used by a non SAIC MS /
SAIC MS pair or SAIC / non SAIC pair during a measurement reporting period. It is incremented at the end
of the measurement period
(SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
43-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Established Phase
....................................................................................................................................................................................................................................

Established Phase

Overview
Purpose
This section contains Established Phase parameters.

Contents

MC1406a - NB_TCH_EST_PAIR_DROP_NON_SAIC 43-3


MC1406b - NB_TCH_EST_PAIR_DROP_SAIC 43-4
MC1406c - NB_TCH_EST_PAIR_DROP_VAMOS1 43-4
MC1406d - NB_TCH_EST_PAIR_DROP_VAMOS2 43-5
MC1407a - NB_TCH_EST_UNPAIR_DROP_NON_SAIC 43-6
MC1407b - NB_TCH_EST_UNPAIR_DROP_SAIC 43-6
MC1407c - NB_TCH_EST_UNPAIR_DROP_VAMOS1 43-7
MC1407d - NB_TCH_EST_UNPAIR_DROP_VAMOS2 43-8

MC1406a - NB_TCH_EST_PAIR_DROP_NON_SAIC
Descripton

Long Name NB_TCH_EST_PAIR_DROP_NON_SAIC


Definition Number of 48.008 CLEAR REQUEST sent to the MSC for speech CS calls in TCH established phase
(traffic) in VAMOS mode related to non-SAIC capable MS.
Inter-cell internal and external TCH handover failures related to theses calls are also taken into account.

Trigger condition Same as MC182a for a speech call in VAMOS mode (paired at drop time) related to non-SAIC capable MS
:1) Whenever a 48.008 CLEAR REQUEST message, whatever the cause, is sent on A interface to the MSC,
for a
Sub Domain 1 Established Phase

Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 43-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1406a - NB_TCH_EST_PAIR_DROP_NON_SAIC
Established Phase
....................................................................................................................................................................................................................................

External Comment --

Feature Name VAMOS

MC1406b - NB_TCH_EST_PAIR_DROP_SAIC
Descripton

Long Name NB_TCH_EST_PAIR_DROP_SAIC

Definition Number of 48.008 CLEAR REQUEST sent to the MSC for speech CS calls in TCH established phase
(traffic) in VAMOS mode related to SAIC capable MS. Inter-cell internal and external TCH handover
failures related to theses calls are also taken into account.

Trigger condition Same as MC182a for a speech call in VAMOS mode (paired at drop time) related to SAIC capable MS:1)
Whenever a 48.008 CLEAR REQUEST message, whatever the cause, is sent on A interface to the MSC, for
a speech call in TCH established phase (traffic). 2) Whenever a 48.008 CLEAR REQUEST message is sent
on A interface to the MSC, after a Handover
Sub Domain 1 Established Phase
Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS
External Comment --
Feature Name VAMOS

MC1406c - NB_TCH_EST_PAIR_DROP_VAMOS1
Descripton

Long Name NB_TCH_EST_PAIR_DROP_VAMOS1

Definition Number of 48.008 CLEAR REQUEST sent to the MSC for speech calls in TCH established phase (traffic)
in VAMOS mode related to VAMOS-1 capable MS.
Inter-cell internal and external TCH handover failures related to theses calls are also taken into account.

Trigger condition Same as MC182a for a speech call in VAMOS mode (paired at drop time) related to VAMOS-1 capable
MS:1) Whenever a 48.008 CLEAR REQUEST message, whatever the cause, is sent on A interface to the
MSC, for a speech call in TCH established phase (traffic). 2) Whenever a 48.008 CLEAR REQUEST
message is sent on A interface to the MSC, after a Handover

Sub Domain 1 Established Phase

....................................................................................................................................................................................................................................
43-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1406c - NB_TCH_EST_PAIR_DROP_VAMOS1
Established Phase
....................................................................................................................................................................................................................................

Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1406d - NB_TCH_EST_PAIR_DROP_VAMOS2
Descripton

Long Name NB_TCH_EST_PAIR_DROP_VAMOS2


Definition Number of 48.008 CLEAR REQUEST sent to the MSC for speech CS calls in TCH established phase
(traffic) in VAMOS mode related to VAMOS-2 capable MS.
Inter-cell internal and external TCH handover failures related to theses calls are also taken into account.

Trigger condition Same as MC182a for a speech call in VAMOS mode (paired at drop time) related to VAMOS-2 capable
MS:1) Whenever a 48.008 CLEAR REQUEST message, whatever the cause, is sent on A interface to the
MSC, for a speech call in TCH established phase (traffic). 2) Whenever a 48.008 CLEAR REQUEST
message is sent on A interface to the MSC, after a Handover
Sub Domain 1 Established Phase

Sub Domain 2 TCH


Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 43-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1407a - NB_TCH_EST_UNPAIR_DROP_NON_SAIC
Established Phase
....................................................................................................................................................................................................................................

MC1407a - NB_TCH_EST_UNPAIR_DROP_NON_SAIC
Descripton

Long Name NB_TCH_EST_UNPAIR_DROP_NON_SAIC

Definition Number of 48.008 CLEAR REQUEST sent to the MSC for speech CS calls in TCH established phase
(traffic) in non VAMOS mode related to non-SAIC capable MS.
Inter-cell internal and external TCH handover failures related to theses calls are also taken into account.

Trigger condition Same as MC182a for a call in non VAMOS mode (unpaired at drop time) related to non-SAIC capable
MS:1) Whenever a 48.008 CLEAR REQUEST message, whatever the cause, is sent on A interface to the
MSC, for a speech call in TCH established phase (traffic). 2) Whenever a 48.008 CLEAR REQUEST
message is sent on A interface to the MSC, after a Handover

Sub Domain 1 Established Phase


Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1407b - NB_TCH_EST_UNPAIR_DROP_SAIC
Descripton

Long Name NB_TCH_EST_UNPAIR_DROP_SAIC


Definition Number of 48.008 CLEAR REQUEST sent to the MSC for speech CS calls in TCH established phase
(traffic) in non VAMOS mode related to SAIC capable MS.
Inter-cell internal and external TCH handover failures related to theses calls are also taken into account.

Trigger condition Same as MC182a for a call in TCH established phase (traffic) in non VAMOS mode (unpaired at drop time)
related to SAIC capable MS:1) Whenever a 48.008 CLEAR REQUEST message, whatever the cause, is sent
on A interface to the MSC, for a speech call in TCH established phase (traffic). 2) Whenever a 48.008
CLEAR REQUEST message is sent on A interface to the MSC, after a Handover

Sub Domain 1 Established Phase


Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell

....................................................................................................................................................................................................................................
43-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1407b - NB_TCH_EST_UNPAIR_DROP_SAIC
Established Phase
....................................................................................................................................................................................................................................

Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

MC1407c - NB_TCH_EST_UNPAIR_DROP_VAMOS1
Descripton

Long Name NB_TCH_EST_UNPAIR_DROP_VAMOS1

Definition Number of 48.008 CLEAR REQUEST sent to the MSC for speech CS calls in TCH established phase
(traffic) in non VAMOS mode related to VAMOS-1 capable MS.
Inter-cell internal and external TCH handover failures related to theses calls are also taken into account.

Trigger condition Same as MC182a for a call in non VAMOS mode (unpaired at drop time) related to VAMOS-1 capable MS:
1) Whenever a 48.008 CLEAR REQUEST message, whatever the cause, is sent on A interface to the MSC,
for a speech call in TCH established phase (traffic).2) Whenever a 48.008 CLEAR REQUEST message is
sent on A interface to the MSC, after a Handover

Sub Domain 1 Established Phase


Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 43-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1407d - NB_TCH_EST_UNPAIR_DROP_VAMOS2
Established Phase
....................................................................................................................................................................................................................................

MC1407d - NB_TCH_EST_UNPAIR_DROP_VAMOS2
Descripton

Long Name NB_TCH_EST_UNPAIR_DROP_VAMOS2

Definition Number of 48.008 CLEAR REQUEST sent to the MSC for speech CS calls in TCH established phase
(traffic) in non VAMOS mode related to VAMOS-2 capable MS.
Inter-cell internal and external TCH handover failures related to theses calls are also taken into account.

Trigger condition Same as MC182a for a call in non VAMOS mode (unpaired at drop time) related to VAMOS-2 capable
MS:1) Whenever a 48.008 CLEAR REQUEST message, whatever the cause, is sent on A interface to the
MSC, for a speech call in TCH established phase (traffic). 2) Whenever a 48.008 CLEAR REQUEST
message is sent on A interface to the MSC, after a Handover

Sub Domain 1 Established Phase


Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
43-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Telecom Procedure (QoS)

Overview
Purpose
This section contains Telecom Procedure (QoS) parameters.

Contents

MC1422a - AV_RXQUAL_DL_VAMOS_NON_SAIC 43-9


MC1422b - AV_RXQUAL_DL_VAMOS_SAIC 43-10
MC1422c - AV_RXQUAL_DL_VAMOS_VAMOS1 43-11
MC1422d - AV_RXQUAL_DL_VAMOS_VAMOS2 43-12
MC1423a - AV_RXQUAL_UL_VAMOS_NON_SAIC 43-12
MC1423b - AV_RXQUAL_UL_VAMOS_SAIC 43-13
MC1423c - AV_RXQUAL_UL_VAMOS_VAMOS1 43-14
MC1423d - AV_RXQUAL_UL_VAMOS_VAMOS2 43-15
MC1424d - NB_INTRA_TCH_HO_35_REQ 43-15

MC1422a - AV_RXQUAL_DL_VAMOS_NON_SAIC
Descripton

Long Name AV_RXQUAL_DL_VAMOS_NON_SAIC

Definition Indicates the average receive downlink quality (0..7) of the serving cell measured by non-SAIC MSs in
VAMOS mode (paired).

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 43-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1422a - AV_RXQUAL_DL_VAMOS_NON_SAIC
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Trigger condition RXQUAL_DL of the serving cell is obtained in 44.018 MEASUREMENT REPORT received from
non-SAIC MSs in VAMOS mode (paired).
This counter is the average value of RXQUAL_DL for all relevant MS measurements during accumulation
period.
For each MEASUREMENT REPORT received by BSC, increment the number of MS of a given type for the
quality reported => Quality(q) with number(n) of measurements for MS type(t) then at the end of
accumulation period the weighted average is computed: MC1422a = SUMq [Quality (q) * Number (n) ] /
SUMq [Number (n) ] with 0 <= q <= 7 for non-SAIC MSs in VAMOS mode (paired).
In order to provide one decimal place, the averaged 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 Telecom Procedure (QoS)


Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --
Feature Name VAMOS

MC1422b - AV_RXQUAL_DL_VAMOS_SAIC
Descripton

Long Name AV_RXQUAL_DL_VAMOS_SAIC


Definition Indicates the average receive downlink quality (0..7) of the serving cell measured by SAIC MSs in VAMOS
mode (paired).
Trigger condition RXQUAL_DL of the serving cell is obtained in 44.018 MEASUREMENT REPORT received from SAIC
MSs in VAMOS mode (paired).
This counter is the average value of RXQUAL_DL for all relevant MS measurements during accumulation
period.
For each MEASUREMENT REPORT received by BSC, increment the number of MS of a given type for the
quality reported => Quality(q) with number(n) of measurements for MS type(t) then at the end of
accumulation period the weighted average is computed MC1422b = SUMq [Quality (q) * Number (n) ] /
SUMq [Number (n) ] with 0 <= q <= 7 for SAIC MSs in VAMOS mode (paired).
In order to provide one decimal place, the averaged 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 Telecom Procedure (QoS)

....................................................................................................................................................................................................................................
43-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1422b - AV_RXQUAL_DL_VAMOS_SAIC
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1422c - AV_RXQUAL_DL_VAMOS_VAMOS1
Descripton

Long Name AV_RXQUAL_DL_VAMOS_VAMOS1


Definition Indicates the average receive downlink quality (0..7) of the serving cell measured by VAMOS-1 MSs in
VAMOS mode (paired).
Trigger condition RXQUAL_DL of the serving cell is obtained in 44.018 MEASUREMENT REPORT received from
VAMOS-1 MSs in VAMOS mode (paired).
This counter is the average value of RXQUAL_DL for all relevant MS measurements during accumulation
period.
For each MEASUREMENT REPORT received by BSC, increment the number of MS of a given type for the
quality reported => Quality(q) with number(n) of measurements for MS type(t) then at the end of
accumulation period the weighted average is computed MC1422c = SUMq [Quality (q) * Number (n) ] /
SUMq [Number (n) ] with 0 <= q <= 7 for VAMOS1 MSs in VAMOS mode (paired).
In order to provide one decimal place, the averaged 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 Telecom Procedure (QoS)

Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --
Feature Name VAMOS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 43-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1422d - AV_RXQUAL_DL_VAMOS_VAMOS2
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

MC1422d - AV_RXQUAL_DL_VAMOS_VAMOS2
Descripton

Long Name AV_RXQUAL_DL_VAMOS_VAMOS2

Definition Indicates the average receive downlink quality (0..7) of the serving cell measured by VAMOS-2 MSs in
VAMOS mode (paired).
Trigger condition RXQUAL_DL of the serving cell is obtained in 44.018 MEASUREMENT REPORT received from
VAMOS-2 MSs in VAMOS mode (paired).
This counter is the average value of RXQUAL_DL for all relevant MS measurements during accumulation
period.
For each MEASUREMENT REPORT received by BSC, increment the number of MS of a given type for the
quality reported => Quality(q) with number(n) of measurements for MS type(t) then at the end of
accumulation period the weighted average is computed MC1422d = SUMq [Quality (q) * Number (n) ] /
SUMq [Number (n) ] with 0 <= q <= 7 for VAMOS2 MSs in VAMOS mode (paired).
In order to provide one decimal place, the averaged 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 Telecom Procedure (QoS)
Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --
Feature Name VAMOS

MC1423a - AV_RXQUAL_UL_VAMOS_NON_SAIC
Descripton

Long Name AV_RXQUAL_UL_VAMOS_NON_SAIC


Definition Indicates the average receive uplink quality (0..7) of the serving cell measured by the BTS related to
non-SAIC MSs in VAMOS mode (paired).

....................................................................................................................................................................................................................................
43-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1423a - AV_RXQUAL_UL_VAMOS_NON_SAIC
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Trigger condition RXQUAL_UL of the serving cell is obtained in Abis MEASUREMENT RESULT message received from
BTS.
This counter is the average value of RXQUAL_UL for all measurements during accumulation period related
to non-SAIC MSs in VAMOS mode (paired).
For each MEASUREMENT RESULT received by BSC, increment the number of MS of a given type for the
quality reported => Quality(q) with number(n) of measurements for MS type(t) then at the end of
accumulation period the weighted average is computed: MC1423a = SUMq [Quality (q) * Number (n) ] /
SUMq [Number (n) ] with 0 <= q <= 7 for non-SAIC MSs in VAMOS mode (paired).
In order to provide one decimal place, the averaged 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 Telecom Procedure (QoS)


Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --
Feature Name VAMOS

MC1423b - AV_RXQUAL_UL_VAMOS_SAIC
Descripton

Long Name AV_RXQUAL_UL_VAMOS_SAIC


Definition Indicates the average receive uplink quality (0..7) of the serving cell measured by the BTS related to SAIC
MSs in VAMOS mode (paired).
Trigger condition RXQUAL_UL of the serving cell is obtained in Abis MEASUREMENT RESULT message received from
BTS.
This counter is the average value of RXQUAL_UL for all measurements during accumulation period related
to SAIC MSs in VAMOS mode (paired).
For each MEASUREMENT RESULT received by BSC, increment the number of MS of a given type for the
quality reported => Quality(q) with number(n) of measurements for MS type(t) then at the end of
accumulation period the weighted average is computed MC1423b = SUMq [Quality (q) * Number (n) ] /
SUMq [Number (n) ] with 0 <= q <= 7 for SAIC MSs in VAMOS mode (paired).
In order to provide one decimal place, the averaged 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 Telecom Procedure (QoS)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 43-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1423b - AV_RXQUAL_UL_VAMOS_SAIC
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1423c - AV_RXQUAL_UL_VAMOS_VAMOS1
Descripton

Long Name AV_RXQUAL_UL_VAMOS_VAMOS1


Definition Indicates the average receive uplink quality (0..7) of the serving cell measured by the BTS related to
VAMOS-1 MSs in VAMOS mode (paired).
Trigger condition RXQUAL_UL of the serving cell is obtained in Abis MEASUREMENT RESULT message received from
BTS.
This counter is the average value of RXQUAL_UL for all measurements during accumulation period related
to VAMOS-1 MSs in VAMOS mode (paired).
For each MEASUREMENT RESULT received by BSC, increment the number of MS of a given type for the
quality reported => Quality(q) with number(n) of measurements for MS type(t) then at the end of
accumulation period the weighted average is computed MC1423c = SUMq [Quality (q) * Number (n) ] /
SUMq [Number (n) ] with 0 <= q <= 7 for VAMOS1 MSs in VAMOS mode (paired).
In order to provide one decimal place, the averaged 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 Telecom Procedure (QoS)

Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --
Feature Name VAMOS

....................................................................................................................................................................................................................................
43-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1423d - AV_RXQUAL_UL_VAMOS_VAMOS2
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

MC1423d - AV_RXQUAL_UL_VAMOS_VAMOS2
Descripton

Long Name AV_RXQUAL_UL_VAMOS_VAMOS2

Definition Indicates the average receive uplink quality (0..7) of the serving cell measured by the BTS related to
VAMOS-2 MSs in VAMOS mode (paired).
Trigger condition RXQUAL_UL of the serving cell is obtained in Abis MEASUREMENT RESULT message received from
BTS.
This counter is the average value of RXQUAL_UL for all measurements during accumulation period related
to VAMOS-2 MSs in VAMOS mode (paired).
For each MEASUREMENT RESULT received by BSC, increment the number of MS of a given type for the
quality reported => Quality(q) with number(n) of measurements for MS type(t) then at the end of
accumulation period the weighted average is computed MC1423d = SUMq [Quality (q) * Number (n) ] /
SUMq [Number (n) ] with 0 <= q <= 7 for VAMOS2 MSs in VAMOS mode (paired).
In order to provide one decimal place, the averaged 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 Telecom Procedure (QoS)
Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --
Feature Name VAMOS

MC1424d - NB_INTRA_TCH_HO_35_REQ
Descripton

Long Name NB_INTRA_TCH_HO_35_REQ


Definition Number of intra cell TCH (in HR or FR usage) handover requests related to VAMOS HO cause 35

Trigger condition Whenever the BSC process responsible for the handover procedure starts an intra cell TCH handover related
to VAMOS HO cause 35 (pairing).

Sub Domain 1 Telecom Procedure (QoS)


Sub Domain 2 --

Sub Domain 3 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 43-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1424d - NB_INTRA_TCH_HO_35_REQ
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

....................................................................................................................................................................................................................................
43-16 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
44 44
Resource Availability &
Usage

Channel

Overview
Purpose
This section contains Channel parameters.

Contents

MC1408a - NB_PAIR_PER_MS_NON_SAIC 44-3


MC1408b - NB_PAIR_PER_MS_SAIC 44-3
MC1408c - NB_PAIR_PER_MS_VAMOS1 44-4
MC1408d - NB_PAIR_PER_MS_VAMOS2 44-5
MC1409a - NB_UNPAIR_PER_MS_NON_SAIC 44-5
MC1409b - NB_UNPAIR_PER_MS_SAIC 44-6
MC1409c - NB_UNPAIR_PER_MS_VAMOS1 44-6
MC1409d - NB_UNPAIR_PER_MS_VAMOS2 44-7
MC1410a - NB_ONE_CALL_PER_RADIO_TS_NON_VAMOS 44-7
MC1410b - NB_TWO_CALLS_PER_RADIO_TS_NON_VAMOS 44-8
MC1410c - NB_TWO_CALLS_PER_RADIO_TS_VAMOS 44-9
MC1410d - NB_THREE_CALLS_PER_RADIO_TS_VAMOS 44-9
MC1410e - NB_FOUR_CALLS_PER_RADIO_TS 44-10
MC1411a - DISTRIB_1_SCPIR_NON_SAIC_VAMOS1 44-11
MC1411b - DISTRIB_2_SCPIR_NON_SAIC_VAMOS1 44-11
MC1411c - DISTRIB_3_SCPIR_NON_SAIC_VAMOS1 44-12

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage Overview
Channel
....................................................................................................................................................................................................................................

MC1411d - DISTRIB_4_SCPIR_NON_SAIC_VAMOS1 44-13


MC1412a - DISTRIB_1_SCPIR_NON_SAIC_VAMOS2 44-13
MC1412b - DISTRIB_2_SCPIR_NON_SAIC_VAMOS2 44-14
MC1412c - DISTRIB_3_SCPIR_NON_SAIC_VAMOS2 44-15
MC1412d - DISTRIB_4_SCPIR_NON_SAIC_VAMOS2 44-15
MC1413a - DISTRIB_1_SCPIR_SAIC_VAMOS1 44-16
MC1413b - DISTRIB_2_SCPIR_SAIC_VAMOS1 44-17
MC1413c - DISTRIB_3_SCPIR_SAIC_VAMOS1 44-17
MC1413d - DISTRIB_4_SCPIR_SAIC_VAMOS1 44-18
MC1414a - DISTRIB_1_SCPIR_SAIC_VAMOS2 44-19
MC1414b - DISTRIB_2_SCPIR_SAIC_VAMOS2 44-19
MC1414c - DISTRIB_3_SCPIR_SAIC_VAMOS2 44-20
MC1414d - DISTRIB_4_SCPIR_SAIC_VAMOS2 44-21
MC1415a - DISTRIB_1_SCPIR_VAMOS1_VAMOS1 44-21
MC1415b - DISTRIB_2_SCPIR_VAMOS1_VAMOS1 44-22
MC1415c - DISTRIB_3_SCPIR_VAMOS1_VAMOS1 44-23
MC1415d - DISTRIB_4_SCPIR_VAMOS1_VAMOS1 44-23
MC1416a - DISTRIB_1_SCPIR_VAMOS1_VAMOS2 44-24
MC1416b - DISTRIB_2_SCPIR_VAMOS1_VAMOS2 44-25
MC1416c - DISTRIB_3_SCPIR_VAMOS1_VAMOS2 44-25
MC1416d - DISTRIB_4_SCPIR_VAMOS1_VAMOS2 44-26
MC1417a - DISTRIB_1_SCPIR_VAMOS2_VAMOS1 44-27
MC1417b - DISTRIB_2_SCPIR_VAMOS2_VAMOS1 44-27
MC1417c - DISTRIB_3_SCPIR_VAMOS2_VAMOS1 44-28
MC1417d - DISTRIB_4_SCPIR_VAMOS2_VAMOS1 44-29
MC1418a - DISTRIB_1_SCPIR_VAMOS2_VAMOS2 44-29
MC1418b - DISTRIB_2_SCPIR_VAMOS2_VAMOS2 44-30
MC1418c - DISTRIB_3_SCPIR_VAMOS2_VAMOS2 44-31
MC1418d - DISTRIB_4_SCPIR_VAMOS2_VAMOS2 44-31
MC1419a - DISTRIB_1_SCPIR_SAIC_SAIC 44-32
MC1419b - DISTRIB_2_SCPIR_SAIC_SAIC 44-33
MC1419c - DISTRIB_3_SCPIR_SAIC_SAIC 44-33
MC1419d - DISTRIB_4_SCPIR_SAIC_SAIC 44-34
....................................................................................................................................................................................................................................
44-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage Overview
Channel
....................................................................................................................................................................................................................................

MC1425a - DISTRIB_1_SCPIR_NON_SAIC_NON_SAIC 44-35


MC1425b - DISTRIB_2_SCPIR_NON_SAIC_NON_SAIC 44-35
MC1425c - DISTRIB_3_SCPIR_NON_SAIC_NON_SAIC 44-36
MC1425d - DISTRIB_4_SCPIR_NON_SAIC_NON_SAIC 44-37
MC1426a - DISTRIB_1_SCPIR_NON_SAIC_SAIC 44-38
MC1426b - DISTRIB_2_SCPIR_NON_SAIC_SAIC 44-39
MC1426c - DISTRIB_3_SCPIR_NON_SAIC_SAIC 44-40

MC1408a - NB_PAIR_PER_MS_NON_SAIC
Descripton

Long Name NB_PAIR_PER_MS_NON_SAIC


Definition Average number of VAMOS pairing (due to any reason) per CS call for a non-SAIC capable MS.
Trigger condition Whenever a CS call related to a non-SAIC capable MS is VAMOS paired, this counter is incremented.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --
Feature Name VAMOS

MC1408b - NB_PAIR_PER_MS_SAIC
Descripton

Long Name NB_PAIR_PER_MS_SAIC


Definition Average number of VAMOS pairing (due to any reason) per CS call for a SAIC capable MS.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1408b - NB_PAIR_PER_MS_SAIC
Channel
....................................................................................................................................................................................................................................

Trigger condition Whenever a CS call related to a SAIC capable MS is VAMOS paired, this counter is incremented. A CS call
can be paired due to its own TCH assignment (at establishment or at handover : 44.018 ASSIGNMENT
COMPLETE received on Abis for a TCH established in VAMOS mode (after pairing)) or because another
call is paired with it on a radio time slot (in this case MC1408x (x matching the relevant MS type) are
incremented twice, one for each VAMOS call).
At accumulation period, the average value is calculated by dividing the counter value by the number of
VAMOS calls (calls paired during the period) for SAIC capable MS, if positive. The result is rounded to the
nearest integer value.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1408c - NB_PAIR_PER_MS_VAMOS1
Descripton

Long Name NB_PAIR_PER_MS_VAMOS1


Definition Avergae number of VAMOS pairing (due to any reason) per CS call for a VAMOS-1 capable MS.
Trigger condition Whenever a CS call related to a VAMOS-1 capable MS is VAMOS paired, this counter is incremented. A CS
call can be paired due to its own TCH assignment (at establishment or at handover : 44.018 ASSIGNMENT
COMPLETE received on Abis for a TCH established in VAMOS mode (after pairing)) or because another
call is paired with it on a radio time slot (in this case MC1408x (x matching the relevant MS type) are
incremented twice, one for each VAMOS call).
At accumulation period, the average value is calculated by dividing the counter value by the number of
VAMOS calls (calls paired during the period) for VAMOS-1 capable MS, if positive. The result is rounded
to the nearest integer value.

Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
44-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1408d - NB_PAIR_PER_MS_VAMOS2
Channel
....................................................................................................................................................................................................................................

MC1408d - NB_PAIR_PER_MS_VAMOS2
Descripton

Long Name NB_PAIR_PER_MS_VAMOS2

Definition Average number of VAMOS pairing (due to any reason) per CS call for a VAMOS-2 capable MS.
Trigger condition Whenever a CS call related to a VAMOS-2 capable MS is VAMOS paired, this counter is incremented. A CS
call can be paired due to its own TCH assignment (at establishment or at handover : 44.018 ASSIGNMENT
COMPLETE received on Abis for a TCH established in VAMOS mode (after pairing)) or because another
call is paired with it on a radio time slot (in this case MC1408x (x matching the relevant MS type) are
incremented twice, one for each VAMOS call).
At accumulation period, the average value is calculated by dividing the counter value by the number of
VAMOS calls (calls paired during the period) for VAMOS-2 capable MS, if positive. The result is rounded
to the nearest integer value.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1409a - NB_UNPAIR_PER_MS_NON_SAIC
Descripton

Long Name NB_UNPAIR_PER_MS_NON_SAIC


Definition Average number of unpairing (due to any reason e.g. release of paired call) per CS call for a non-SAIC
capable MS. Release of the call is not considered as unpairing.
Trigger condition Whenever a CS call related to a non-SAIC capable MS is VAMOS unpaired due to any reason:
-

Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1409a - NB_UNPAIR_PER_MS_NON_SAIC
Channel
....................................................................................................................................................................................................................................

Feature Name VAMOS

MC1409b - NB_UNPAIR_PER_MS_SAIC
Descripton

Long Name NB_UNPAIR_PER_MS_SAIC

Definition Average number of unpairing (due to any reason e.g. release of paired call) per CS call for a SAIC capable
MS. Release of the call is not considered as unpairing.
Trigger condition Whenever a CS call related to a SAIC capable MS is VAMOS unpaired due to any reason:
-
Sub Domain 1 Channel
Sub Domain 2 TCH
Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --
Feature Name VAMOS

MC1409c - NB_UNPAIR_PER_MS_VAMOS1
Descripton

Long Name NB_UNPAIR_PER_MS_VAMOS1

Definition Average number of unpairing (due to any reason e.g. release of paired call) per CS call for a VAMOS-1
capable MS. Release of the call is not considered as unpairing.

Trigger condition Whenever a CS call related to a VAMOS1 capable MS is VAMOS unpaired due to any reason:
-
Sub Domain 1 Channel
Sub Domain 2 TCH

Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS

External Comment --

....................................................................................................................................................................................................................................
44-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1409c - NB_UNPAIR_PER_MS_VAMOS1
Channel
....................................................................................................................................................................................................................................

Feature Name VAMOS

MC1409d - NB_UNPAIR_PER_MS_VAMOS2
Descripton

Long Name NB_UNPAIR_PER_MS_VAMOS2

Definition Average number of unpairing (due to any reason e.g. release of paired call) per CS call for a VAMOS-2
capable MS. Release of the call is not considered as unpairing.
Trigger condition Whenever a CS call related to a VAMOS2 capable MS is VAMOS unpaired due to any reason:
-
Sub Domain 1 Channel
Sub Domain 2 TCH
Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --
Feature Name VAMOS

MC1410a - NB_ONE_CALL_PER_RADIO_TS_NON_VAMOS
Descripton

Long Name NB_ONE_CALL_PER_RADIO_TS_NON_VAMOS

Definition Number of speech CS calls which are alone on a radio time slot (one call per radio time slot). It matches a
FR TCH or one HR TCH allocated in non-VAMOS mode on a radio time slot.

Trigger condition At each polling period, the number of radio timeslot with only one speech FR or HR TCH in non-VAMOS
mode is determined.
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. In order to provide one decimal place, the averaged
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 TCH

Sub Domain 3 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1410a - NB_ONE_CALL_PER_RADIO_TS_NON_VAMOS
Channel
....................................................................................................................................................................................................................................

Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1410b - NB_TWO_CALLS_PER_RADIO_TS_NON_VAMOS
Descripton

Long Name NB_TWO_CALLS_PER_RADIO_TS_NON_VAMOS


Definition Number of speech CS calls which share a radio time slot with another call (two calls per radio time slot) in
case of two HR TCH allocated in non-VAMOS mode.
Trigger condition At each polling period, the number of radio timeslot with two speech HR TCH in non-VAMOS mode is
determined.
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. In order to provide one decimal place, the averaged
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 TCH
Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
44-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1410c - NB_TWO_CALLS_PER_RADIO_TS_VAMOS
Channel
....................................................................................................................................................................................................................................

MC1410c - NB_TWO_CALLS_PER_RADIO_TS_VAMOS
Descripton

Long Name NB_TWO_CALLS_PER_RADIO_TS_VAMOS

Definition Number of speech CS calls which share a radio time slot with another call (two calls per radio time slot) in
case of two FR TCH allocated in VAMOS mode or two HR TCH in VAMOS mode.
Trigger condition At each polling period, the number of radio timeslot with two FR TCH in VAMOS mode or two HR TCH in
VAMOS mode is determined. 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. In order to provide one
decimal place, the averaged 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 TCH


Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1410d - NB_THREE_CALLS_PER_RADIO_TS_VAMOS
Descripton

Long Name NB_THREE_CALLS_PER_RADIO_TS_VAMOS

Definition Number of speech CS calls which share a radio time slot with two other calls (three calls per radio time
slot). It matches the case of two HR TCH in VAMOS mode and one HR TCH in non-VAMOS mode on a
radio time slot.
Trigger condition At each polling period, the number of radio timeslot used with two HR TCH in VAMOS mode and one HR
TCH in non-VAMOS mode is determined. 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. In order
to provide one decimal place, the averaged 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 TCH


Sub Domain 3 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1410d - NB_THREE_CALLS_PER_RADIO_TS_VAMOS
Channel
....................................................................................................................................................................................................................................

Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1410e - NB_FOUR_CALLS_PER_RADIO_TS
Descripton

Long Name NB_FOUR_CALLS_PER_RADIO_TS


Definition Number of speech CS calls which share a radio time slot with three other calls during the accumulation
period (four calls per radio time slot). It matches the case of four HR TCH in VAMOS mode on a radio time
slot.
Trigger condition At each polling period, the number of radio timeslot with four HR TCH in VAMOS mode is determined. 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. In order to provide one decimal place, the averaged
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 TCH


Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

....................................................................................................................................................................................................................................
44-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1411a - DISTRIB_1_SCPIR_NON_SAIC_VAMOS1
Channel
....................................................................................................................................................................................................................................

MC1411a - DISTRIB_1_SCPIR_NON_SAIC_VAMOS1
Descripton

Long Name DISTRIB_1_SCPIR_NON_SAIC_VAMOS1

Definition First cell of distribution of SCPIR for a non-SAIC MS / VAMOS1 MS pair.


Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.This counter allows to
monitor the distribution of calls for a non-SAIC MS / VAMOS1 MS pair whose SCPIR lies during a
measurement reporting period within the first SCPIR range defined by the values strictly below the
threshold SCPIR_NON_SAIC_VAMOS1_THR_1.
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 1 is applied to a channel used by a non-SAIC MS /
VAMOS1 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel


Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --
Feature Name VAMOS

MC1411b - DISTRIB_2_SCPIR_NON_SAIC_VAMOS1
Descripton

Long Name DISTRIB_2_SCPIR_NON_SAIC_VAMOS1

Definition Second cell of distribution of SCPIR for a non-SAIC MS / VAMOS1 MS pair.


Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a non-SAIC MS / VAMOS1 MS pair whose
SCPIR lies during a measurement reporting period within the second SCPIR range defined by the values
between the thresholds [SCPIR_NON_SAIC_VAMOS1_THR_1, SCPIR_NON_SAIC_VAMOS1_THR_2 [
(notation [a,b[ equivalent to notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 2 is applied to a channel used by a non-SAIC MS /
VAMOS1 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1411b - DISTRIB_2_SCPIR_NON_SAIC_VAMOS1
Channel
....................................................................................................................................................................................................................................

Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1411c - DISTRIB_3_SCPIR_NON_SAIC_VAMOS1
Descripton

Long Name DISTRIB_3_SCPIR_NON_SAIC_VAMOS1


Definition Third cell of distribution of SCPIR for a non-SAIC MS / VAMOS1 MS pair.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a non-SAIC MS / VAMOS1 MS pair whose
SCPIR lies during a measurement reporting period within the third SCPIR range defined by the values
between the thresholds [SCPIR_NON_SAIC_VAMOS1_THR_2 ,SCPIR_NON_SAIC_VAMOS1_THR_3[
(notation [a,b[ equivalent to notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 3 is applied to a channel used by a non-SAIC MS /
VAMOS1 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel


Sub Domain 2 TCH
Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
44-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1411d - DISTRIB_4_SCPIR_NON_SAIC_VAMOS1
Channel
....................................................................................................................................................................................................................................

MC1411d - DISTRIB_4_SCPIR_NON_SAIC_VAMOS1
Descripton

Long Name DISTRIB_4_SCPIR_NON_SAIC_VAMOS1

Definition Fourth cell of distribution of SCPIR for a non-SAIC MS / VAMOS1 MS pair.


Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a non-SAIC MS / VAMOS1 MS pair whose
SCPIR lies during a measurement reporting period within the fourth SCPIR range defined by the values
above the threshold SCPIR_NON_SAIC_VAMOS1_THR_3 (included).
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 4 is applied to a channel used by a non-SAIC MS /
VAMOS1 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --
Feature Name VAMOS

MC1412a - DISTRIB_1_SCPIR_NON_SAIC_VAMOS2
Descripton

Long Name DISTRIB_1_SCPIR_NON_SAIC_VAMOS2


Definition First cell of distribution of SCPIR for a non-SAIC MS / VAMOS2 MS pair.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a non-SAIC MS / VAMOS2 MS pair whose
SCPIR lies during a measurement reporting period within the first SCPIR range defined by the values
strictly below the threshold SCPIR_NON_SAIC_VAMOS2_THR_1.
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 1 is applied to a channel used by a non-SAIC MS /
VAMOS2 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1412a - DISTRIB_1_SCPIR_NON_SAIC_VAMOS2
Channel
....................................................................................................................................................................................................................................

Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1412b - DISTRIB_2_SCPIR_NON_SAIC_VAMOS2
Descripton

Long Name DISTRIB_2_SCPIR_NON_SAIC_VAMOS2


Definition Second cell of distribution of SCPIR for a non-SAIC MS / VAMOS2 MS pair.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a non-SAIC MS / VAMOS2 MS pair whose
SCPIR lies during a measurement reporting period within the second SCPIR range defined by the values
between the thresholds [SCPIR_NON_SAIC_VAMOS2_THR_1, SCPIR_NON_SAIC_VAMOS2_THR_2[
(notation [a,b[ equivalent to notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 2 is applied to a channel used by a non-SAIC MS /
VAMOS2 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel


Sub Domain 2 TCH
Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
44-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1412c - DISTRIB_3_SCPIR_NON_SAIC_VAMOS2
Channel
....................................................................................................................................................................................................................................

MC1412c - DISTRIB_3_SCPIR_NON_SAIC_VAMOS2
Descripton

Long Name DISTRIB_3_SCPIR_NON_SAIC_VAMOS2

Definition Third cell of distribution of SCPIR for a non-SAIC MS / VAMOS2 MS pair.


Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a non-SAIC MS / VAMOS2 MS pair whose
SCPIR lies during a measurement reporting period within the third SCPIR range defined by the values
between the thresholds [SCPIR_NON_SAIC_VAMOS2_THR_2, SCPIR_NON_SAIC_VAMOS2_THR_3[
(notation [a,b[ equivalent to notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 3 is applied to a channel used by a non-SAIC MS /
VAMOS2 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1412d - DISTRIB_4_SCPIR_NON_SAIC_VAMOS2
Descripton

Long Name DISTRIB_4_SCPIR_NON_SAIC_VAMOS2

Definition Fourth cell of distribution of SCPIR for a non-SAIC MS / VAMOS2 MS pair.


Whenever a Fr or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a non-SAIC MS / VAMOS2 MS pair whose
SCPIR lies during a measurement reporting period within the fourth SCPIR range defined by the values
above the threshold SCPIR_NON_SAIC_VAMOS2_THR_3 (included).
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 4 is applied to a channel used by a non-SAIC MS /
VAMOS2 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1412d - DISTRIB_4_SCPIR_NON_SAIC_VAMOS2
Channel
....................................................................................................................................................................................................................................

Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1413a - DISTRIB_1_SCPIR_SAIC_VAMOS1
Descripton

Long Name DISTRIB_1_SCPIR_SAIC_VAMOS1


Definition First cell of distribution of SCPIR for a SAIC MS / VAMOS1 MS pair.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a SAIC MS / VAMOS1 MS pair whose SCPIR
lies during a measurement reporting period within the first SCPIR range defined by the values strictly below
the threshold SCPIR_SAIC_VAMOS1_THR_1.
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 1 is applied to a channel used by a SAIC MS /
VAMOS1 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel


Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS

External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
44-16 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1413b - DISTRIB_2_SCPIR_SAIC_VAMOS1
Channel
....................................................................................................................................................................................................................................

MC1413b - DISTRIB_2_SCPIR_SAIC_VAMOS1
Descripton

Long Name DISTRIB_2_SCPIR_SAIC_VAMOS1

Definition Second cell of distribution of SCPIR for a SAIC MS / VAMOS1 MS pair.


Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a SAIC MS / VAMOS1 MS pair whose SCPIR
lies during a measurement reporting period within the second SCPIR range defined by the values between
the thresholds [SCPIR_SAIC_VAMOS1_THR_1,SCPIR_SAIC_VAMOS1_THR_2[ (notation [a,b[
equivalent to notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range

Trigger condition This counter is incremented when a SCPIR in the range 2 is applied to a channel used by a SAIC MS /
VAMOS1 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1413c - DISTRIB_3_SCPIR_SAIC_VAMOS1
Descripton

Long Name DISTRIB_3_SCPIR_SAIC_VAMOS1

Definition Third cell of distribution of SCPIR for a SAIC MS / VAMOS1 MS pair.


Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a SAIC MS / VAMOS1 MS pair whose SCPIR
lies during a measurement reporting period within the third SCPIR range defined by the values between the
thresholds [SCPIR_SAIC_VAMOS1_THR_2 and SCPIR_SAIC_VAMOS1_THR_3[ (notation [a,b[
equivalent to notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 3 is applied to a channel used by a SAIC MS /
VAMOS1 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-17
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1413c - DISTRIB_3_SCPIR_SAIC_VAMOS1
Channel
....................................................................................................................................................................................................................................

Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

MC1413d - DISTRIB_4_SCPIR_SAIC_VAMOS1
Descripton

Long Name DISTRIB_4_SCPIR_SAIC_VAMOS1


Definition Fourth cell of distribution of SCPIR for a SAIC MS / VAMOS1 MS pair.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a SAIC MS / VAMOS1 MS pair whose SCPIR
lies during a measurement reporting period within the fourth SCPIR range defined by the values above the
threshold SCPIR_SAIC_VAMOS1_THR_3 (included).
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 4 is applied to a channel used by a SAIC MS /
VAMOS1 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

....................................................................................................................................................................................................................................
44-18 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1414a - DISTRIB_1_SCPIR_SAIC_VAMOS2
Channel
....................................................................................................................................................................................................................................

MC1414a - DISTRIB_1_SCPIR_SAIC_VAMOS2
Descripton

Long Name DISTRIB_1_SCPIR_SAIC_VAMOS2

Definition First cell of distribution of SCPIR for a SAIC MS / VAMOS2 MS pair.


Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a SAIC MS / VAMOS2 MS pair whose SCPIR
lies during a measurement reporting period within the first SCPIR range defined by the values strictly below
the threshold SCPIR_SAIC_VAMOS2_THR_1.
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 1 is applied to a channel used by a SAIC MS /
VAMOS2 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --
Feature Name VAMOS

MC1414b - DISTRIB_2_SCPIR_SAIC_VAMOS2
Descripton

Long Name DISTRIB_2_SCPIR_SAIC_VAMOS2


Definition Second cell of distribution of SCPIR for a SAIC MS / VAMOS2 MS pair.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a SAIC MS / VAMOS2 MS pair whose SCPIR
lies during a measurement reporting period within the second SCPIR range defined by the values between
the thresholds [SCPIR_SAIC_VAMOS2_THR_1,SCPIR_SAIC_VAMOS2_THR_2[ (notation [a,b[
equivalent to notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 2 is applied to a channel used by a SAIC MS /
VAMOS2 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-19
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1414b - DISTRIB_2_SCPIR_SAIC_VAMOS2
Channel
....................................................................................................................................................................................................................................

Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1414c - DISTRIB_3_SCPIR_SAIC_VAMOS2
Descripton

Long Name DISTRIB_3_SCPIR_SAIC_VAMOS2


Definition Third cell of distribution of SCPIR for a SAIC MS / VAMOS2 MS pair.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a SAIC MS / VAMOS2 MS pair whose SCPIR
lies during a measurement reporting period within the third SCPIR range defined by the values between the
thresholds [SCPIR_SAIC_VAMOS2_THR_2,SCPIR_SAIC_VAMOS2_THR_3[ (notation [a,b[ equivalent
to notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 3 is applied to a channel used by a SAIC MS /
VAMOS2 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel


Sub Domain 2 TCH
Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
44-20 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1414d - DISTRIB_4_SCPIR_SAIC_VAMOS2
Channel
....................................................................................................................................................................................................................................

MC1414d - DISTRIB_4_SCPIR_SAIC_VAMOS2
Descripton

Long Name DISTRIB_4_SCPIR_SAIC_VAMOS2

Definition Fourth cell of distribution of SCPIR for a SAIC MS / VAMOS2 MS pair.


Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a SAIC MS / VAMOS2 MS pair whose SCPIR
lies during a measurement reporting period within the fourth SCPIR range defined by the values above the
threshold SCPIR_SAIC_VAMOS2_THR_3 (included).
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 4 is applied to a channel used by a SAIC MS /
VAMOS2 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --
Feature Name VAMOS

MC1415a - DISTRIB_1_SCPIR_VAMOS1_VAMOS1
Descripton

Long Name DISTRIB_1_SCPIR_VAMOS1_VAMOS1


Definition First cell of distribution of SCPIR for a VAMOS1 MS / VAMOS1 MS pair.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a VAMOS1 MS / VAMOS1 MS pair whose
SCPIR lies during a measurement reporting period within the first SCPIR range defined by the values
strictly below the threshold SCPIR_VAMOS1_VAMOS1_THR_1.
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 1 is applied to a channel used by a VAMOS1 MS /
VAMOS1 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-21
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1415a - DISTRIB_1_SCPIR_VAMOS1_VAMOS1
Channel
....................................................................................................................................................................................................................................

Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1415b - DISTRIB_2_SCPIR_VAMOS1_VAMOS1
Descripton

Long Name DISTRIB_2_SCPIR_VAMOS1_VAMOS1


Definition Second cell of distribution of SCPIR for a VAMOS1 MS / VAMOS1 MS pair.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a VAMOS1 MS / VAMOS1 MS pair whose
SCPIR lies during a measurement reporting period within the second SCPIR range defined by the values
between the thresholds [SCPIR_VAMOS1_VAMOS1_THR_1,SCPIR_VAMOS1_VAMOS1_THR_2[
(notation [a,b[ equivalent to notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 2 is applied to a channel used by a VAMOS1 MS /
VAMOS1 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel


Sub Domain 2 TCH
Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
44-22 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1415c - DISTRIB_3_SCPIR_VAMOS1_VAMOS1
Channel
....................................................................................................................................................................................................................................

MC1415c - DISTRIB_3_SCPIR_VAMOS1_VAMOS1
Descripton

Long Name DISTRIB_3_SCPIR_VAMOS1_VAMOS1

Definition Third cell of distribution of SCPIR for a VAMOS1 MS / VAMOS1 MS pair.


Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a VAMOS1 MS / VAMOS1 MS pair whose
SCPIR lies during a measurement reporting period within the third SCPIR range defined by the values
between the thresholds [SCPIR_VAMOS1_VAMOS1_THR_2,SCPIR_VAMOS1_VAMOS1_THR_3[
(notation [a,b[ equivalent to notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 3 is applied to a channel used by a VAMOS1 MS /
VAMOS1 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1415d - DISTRIB_4_SCPIR_VAMOS1_VAMOS1
Descripton

Long Name DISTRIB_4_SCPIR_VAMOS1_VAMOS1

Definition Fourth cell of distribution of SCPIR for a VAMOS1 MS / VAMOS1 MS pair.


Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a VAMOS1 MS / VAMOS1 MS pair whose
SCPIR lies during a measurement reporting period within the fourth SCPIR range defined by the values
above the threshold SCPIR_VAMOS1_VAMOS1_THR_3 (included).
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 4 is applied to a channel used by a VAMOS1 MS /
VAMOS1 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-23
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1415d - DISTRIB_4_SCPIR_VAMOS1_VAMOS1
Channel
....................................................................................................................................................................................................................................

Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1416a - DISTRIB_1_SCPIR_VAMOS1_VAMOS2
Descripton

Long Name DISTRIB_1_SCPIR_VAMOS1_VAMOS2


Definition First cell of distribution of SCPIR for a VAMOS1 MS / VAMOS2 MS pair.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a VAMOS1 MS / VAMOS2 MS pair whose
SCPIR lies during a measurement reporting period within the first SCPIR range defined by the values
strictly below the threshold SCPIR_VAMOS1_VAMOS2_THR_1.
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 1 is applied to a channel used by a VAMOS1 MS /
VAMOS2 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel


Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS

External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
44-24 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1416b - DISTRIB_2_SCPIR_VAMOS1_VAMOS2
Channel
....................................................................................................................................................................................................................................

MC1416b - DISTRIB_2_SCPIR_VAMOS1_VAMOS2
Descripton

Long Name DISTRIB_2_SCPIR_VAMOS1_VAMOS2

Definition Second cell of distribution of SCPIR for a VAMOS1 MS / VAMOS2 MS pair.


Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a VAMOS1 MS / VAMOS2 MS pair whose
SCPIR lies during a measurement reporting period within the second SCPIR range defined by the values
between the thresholds [SCPIR_VAMOS1_VAMOS2_THR_1,SCPIR_VAMOS1_VAMOS2_THR_2[
(notation [a,b[ equivalent to notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 2 is applied to a channel used by a VAMOS1 MS /
VAMOS2 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1416c - DISTRIB_3_SCPIR_VAMOS1_VAMOS2
Descripton

Long Name DISTRIB_3_SCPIR_VAMOS1_VAMOS2

Definition Third cell of distribution of SCPIR for a VAMOS1 MS / VAMOS2 MS pair.


Whenever a Fr or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a VAMOS1 MS / VAMOS2 MS pair whose
SCPIR lies during a measurement reporting period within the third SCPIR range defined by the values
between the thresholds [SCPIR_VAMOS1_VAMOS2_THR_2,SCPIR_VAMOS1_VAMOS2_THR_3[
(notation [a,b[ equivalent to notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 3 is applied to a channel used by a VAMOS1 MS /
VAMOS2 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-25
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1416c - DISTRIB_3_SCPIR_VAMOS1_VAMOS2
Channel
....................................................................................................................................................................................................................................

Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

MC1416d - DISTRIB_4_SCPIR_VAMOS1_VAMOS2
Descripton

Long Name DISTRIB_4_SCPIR_VAMOS1_VAMOS2


Definition Fourth cell of distribution of SCPIR for a VAMOS1 MS / VAMOS2 MS pair.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a VAMOS1 MS / VAMOS2 MS pair whose
SCPIR lies during a measurement reporting period within the fourth SCPIR range defined by the values
above the threshold SCPIR_VAMOS1_VAMOS2_THR_3 (included).
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 4 is applied to a channel used by a VAMOS1 MS /
VAMOS2 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

....................................................................................................................................................................................................................................
44-26 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1417a - DISTRIB_1_SCPIR_VAMOS2_VAMOS1
Channel
....................................................................................................................................................................................................................................

MC1417a - DISTRIB_1_SCPIR_VAMOS2_VAMOS1
Descripton

Long Name DISTRIB_1_SCPIR_VAMOS2_VAMOS1

Definition First cell of distribution of SCPIR for a VAMOS2 MS / VAMOS1 MS pair.


Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a VAMOS2 MS / VAMOS1 MS pair whose
SCPIR lies during a measurement reporting period within the first SCPIR range defined by the values
strictly below the threshold SCPIR_VAMOS2_VAMOS1_THR_1.
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 1 is applied to a channel used by a VAMOS2 MS /
VAMOS1 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --
Feature Name VAMOS

MC1417b - DISTRIB_2_SCPIR_VAMOS2_VAMOS1
Descripton

Long Name DISTRIB_2_SCPIR_VAMOS2_VAMOS1


Definition Second cell of distribution of SCPIR for a VAMOS2 MS / VAMOS1 MS pair.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a VAMOS2 MS / VAMOS1 MS pair whose
SCPIR lies during a measurement reporting period within the second SCPIR range defined by the values
between the thresholds [SCPIR_VAMOS2_VAMOS1_THR_1,SCPIR_VAMOS2_VAMOS1_THR_2[
(notation [a,b[ equivalent to notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 2 is applied to a channel used by a VAMOS2 MS /
VAMOS1 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-27
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1417b - DISTRIB_2_SCPIR_VAMOS2_VAMOS1
Channel
....................................................................................................................................................................................................................................

Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1417c - DISTRIB_3_SCPIR_VAMOS2_VAMOS1
Descripton

Long Name DISTRIB_3_SCPIR_VAMOS2_VAMOS1


Definition Third cell of distribution of SCPIR for a VAMOS2 MS / VAMOS1 MS pair.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a VAMOS2 MS / VAMOS1 MS pair whose
SCPIR lies during a measurement reporting period within the third SCPIR range defined by the values
between the thresholds [SCPIR_VAMOS2_VAMOS1_THR_2,SCPIR_VAMOS2_VAMOS1_THR_3[
(notation [a,b[ equivalent to notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 3 is applied to a channel used by a VAMOS2 MS /
VAMOS1 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel


Sub Domain 2 TCH
Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
44-28 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1417d - DISTRIB_4_SCPIR_VAMOS2_VAMOS1
Channel
....................................................................................................................................................................................................................................

MC1417d - DISTRIB_4_SCPIR_VAMOS2_VAMOS1
Descripton

Long Name DISTRIB_4_SCPIR_VAMOS2_VAMOS1

Definition Fourth cell of distribution of SCPIR for a VAMOS2 MS / VAMOS1 MS pair.


Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a VAMOS2 MS / VAMOS1 MS pair whose
SCPIR lies during a measurement reporting period within the fourth SCPIR range defined by the values
above the threshold SCPIR_VAMOS2_VAMOS1_THR_3 (included).
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 4 is applied to a channel used by a VAMOS2 MS /
VAMOS1 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --
Feature Name VAMOS

MC1418a - DISTRIB_1_SCPIR_VAMOS2_VAMOS2
Descripton

Long Name DISTRIB_1_SCPIR_VAMOS2_VAMOS2


Definition First cell of distribution of SCPIR for a VAMOS2 MS / VAMOS2 MS pair.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a VAMOS2 MS / VAMOS2 MS pair whose
SCPIR lies during a measurement reporting period within the first SCPIR range defined by the values
strictly below the threshold SCPIR_VAMOS2_VAMOS2_THR_1.
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 1 is applied to a channel used by a VAMOS2 MS /
VAMOS2 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-29
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1418a - DISTRIB_1_SCPIR_VAMOS2_VAMOS2
Channel
....................................................................................................................................................................................................................................

Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1418b - DISTRIB_2_SCPIR_VAMOS2_VAMOS2
Descripton

Long Name DISTRIB_2_SCPIR_VAMOS2_VAMOS2


Definition Second cell of distribution of SCPIR for a VAMOS2 MS / VAMOS2 MS pair.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a VAMOS2 MS / VAMOS2 MS pair whose
SCPIR lies during a measurement reporting period within the second SCPIR range defined by the values
between the thresholds [SCPIR_VAMOS2_VAMOS2_THR_1,SCPIR_VAMOS2_VAMOS2_THR_2[
(notation [a,b[ equivalent to notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 2 is applied to a channel used by a VAMOS2 MS /
VAMOS2 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel


Sub Domain 2 TCH
Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
44-30 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1418c - DISTRIB_3_SCPIR_VAMOS2_VAMOS2
Channel
....................................................................................................................................................................................................................................

MC1418c - DISTRIB_3_SCPIR_VAMOS2_VAMOS2
Descripton

Long Name DISTRIB_3_SCPIR_VAMOS2_VAMOS2

Definition Third cell of distribution of SCPIR for a VAMOS2 MS / VAMOS2 MS pair.


Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a VAMOS2 MS / VAMOS2 MS pair whose
SCPIR lies during a measurement reporting period within the third SCPIR range defined by the values
between the thresholds [SCPIR_VAMOS2_VAMOS2_THR_2,SCPIR_VAMOS2_VAMOS2_THR_3[
(notation [a,b[ equivalent to notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 3 is applied to a channel used by a VAMOS2 MS /
VAMOS2 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1418d - DISTRIB_4_SCPIR_VAMOS2_VAMOS2
Descripton

Long Name DISTRIB_4_SCPIR_VAMOS2_VAMOS2

Definition Fourth cell of distribution of SCPIR for a VAMOS2 MS / VAMOS2 MS pair.


Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a VAMOS2 MS / VAMOS2 MS pair whose
SCPIR lies during a measurement reporting period within the fourth SCPIR range defined by the values
above the threshold SCPIR_VAMOS2_VAMOS2_THR_3 (included).
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 4 is applied to a channel used by a VAMOS2 MS /
VAMOS2 MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-31
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1418d - DISTRIB_4_SCPIR_VAMOS2_VAMOS2
Channel
....................................................................................................................................................................................................................................

Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1419a - DISTRIB_1_SCPIR_SAIC_SAIC
Descripton

Long Name DISTRIB_1_SCPIR_SAIC_SAIC


Definition First cell of distribution of SCPIR for a SAIC MS / SAIC MS pair.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a SAIC MS / SAIC MS pair whose SCPIR lies
during a measurement reporting period within the first SCPIR range defined by the values strictly below the
threshold SCPIR_SAIC_SAIC_THR_1.
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 1 is applied to a channel used by a SAIC MS / SAIC
MS pair during a measurement reporting period. It is incremented at the end of the measurement period
(SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel


Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS

External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
44-32 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1419b - DISTRIB_2_SCPIR_SAIC_SAIC
Channel
....................................................................................................................................................................................................................................

MC1419b - DISTRIB_2_SCPIR_SAIC_SAIC
Descripton

Long Name DISTRIB_2_SCPIR_SAIC_SAIC

Definition Second cell of distribution of SCPIR for a SAIC MS / SAIC MS pair.


Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a SAIC MS / SAIC MS pair whose SCPIR lies
during a measurement reporting period within the second SCPIR range defined by the values between the
thresholds [SCPIR_SAIC_SAIC_THR_1,SCPIR_SAIC_SAIC_THR_2[ (notation [a,b[ equivalent to
notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 2 is applied to a channel used by a SAIC MS / SAIC
MS pair during a measurement reporting period. It is incremented at the end of the measurement period
(SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1419c - DISTRIB_3_SCPIR_SAIC_SAIC
Descripton

Long Name DISTRIB_3_SCPIR_SAIC_SAIC

Definition Third cell of distribution of SCPIR for a SAIC MS / SAIC MS pair.


Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a SAIC MS /SAIC MS pair whose SCPIR lies
during a measurement reporting period within the third SCPIR range defined by the values between the
thresholds [SCPIR_SAIC_SAIC_THR_2 and SCPIR_SAIC_SAIC_THR_3[ (notation [a,b[ equivalent to
notation [a,b), b is excluded)
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 3 is applied to a channel used by a SAIC MS / SAIC
MS pair during a measurement reporting period. It is incremented at the end of the measurement period
(SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-33
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1419c - DISTRIB_3_SCPIR_SAIC_SAIC
Channel
....................................................................................................................................................................................................................................

Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

MC1419d - DISTRIB_4_SCPIR_SAIC_SAIC
Descripton

Long Name DISTRIB_4_SCPIR_SAIC_SAIC


Definition Fourth cell of distribution of SCPIR for a SAIC MS / SAIC MS pair.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a SAIC MS / SAIC MS pair whose SCPIR lies
during a measurement reporting period within the fourth SCPIR range defined by the values above the
threshold SCPIR_SAIC_SAIC_THR_3 (included).
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 4 is applied to a channel used by a SAIC MS / SAIC
MS pair during a measurement reporting period. It is incremented at the end of the measurement period
(SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

....................................................................................................................................................................................................................................
44-34 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1425a - DISTRIB_1_SCPIR_NON_SAIC_NON_SAIC
Channel
....................................................................................................................................................................................................................................

MC1425a - DISTRIB_1_SCPIR_NON_SAIC_NON_SAIC
Descripton

Long Name DISTRIB_1_SCPIR_NON_SAIC_NON_SAIC

Definition First cell of distribution of SCPIR for a TCH in non SAIC MS / non SAIC MS pair.
A non SAIC MS is a MS which does not indicate SAIC capability in Classmark.
A non SAIC / non SAIC pair is only possible when both paired MSs are in reality SAIC MSs which do not
declare their SAIC capabilities to the network.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a non SAIC MS / non SAIC MS pair whose
SCPIR lies during a measurement reporting period within the first SCPIR range defined by the values
strictly below the threshold SCPIR_SAIC_SAIC_THR_1.
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 1 is applied to a channel used by a non SAIC MS /
non SAIC MS pair during a measurement reporting period. It is incremented at the end of the measurement
period
SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel


Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --
Feature Name VAMOS

MC1425b - DISTRIB_2_SCPIR_NON_SAIC_NON_SAIC
Descripton

Long Name DISTRIB_2_SCPIR_NON_SAIC_NON_SAIC

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-35
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1425b - DISTRIB_2_SCPIR_NON_SAIC_NON_SAIC
Channel
....................................................................................................................................................................................................................................

Definition Second cell of distribution of SCPIR for a TCH in non SAIC MS / non SAIC MS pair.
A non SAIC MS is a MS which does not indicate SAIC capability in Classmark.
A non SAIC / non SAIC pair is only possible when both paired MSs are in reality SAIC MSs which do not
declare their SAIC capabilities to the network.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a non SAIC MS / non SAIC MS pair whose
SCPIR lies during a measurement reporting period within the second SCPIR range defined by the values
between the thresholds
[SCPIR_SAIC_SAIC_THR_1,SCPIR_SAIC_SAIC_THR_2[.
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 2 is applied to a channel used by a non SAIC MS /
non SAIC MS pair during a measurement reporting period. It is incremented at the end of the measurement
period
(SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel
Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS
External Comment --
Feature Name VAMOS

MC1425c - DISTRIB_3_SCPIR_NON_SAIC_NON_SAIC
Descripton

Long Name DISTRIB_3_SCPIR_NON_SAIC_NON_SAIC

Definition Third cell of distribution of SCPIR for a TCH in non SAIC MS / non SAIC MS pair.
A non SAIC MS is a MS which does not indicate SAIC capability in Classmark.
A non SAIC / non SAIC pair is only possible when both paired MSs are in reality SAIC MSs which do not
declare their SAIC capabilities to the network.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a non SAIC MS /non SAIC MS pair whose
SCPIR lies during a measurement reporting period within the third SCPIR range defined by the values
between the thresholds
[SCPIR_SAIC_SAIC_THR_2 and SCPIR_SAIC_SAIC_THR_3[.
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range

....................................................................................................................................................................................................................................
44-36 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1425c - DISTRIB_3_SCPIR_NON_SAIC_NON_SAIC
Channel
....................................................................................................................................................................................................................................

Trigger condition This counter is incremented when a SCPIR in the range 3 is applied to a channel used by a non SAIC MS /
non SAIC MS pair during a measurement reporting period. It is incremented at the end of the measurement
period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.

Sub Domain 1 Channel


Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

MC1425d - DISTRIB_4_SCPIR_NON_SAIC_NON_SAIC
Descripton

Long Name DISTRIB_4_SCPIR_NON_SAIC_NON_SAIC


Definition Fourth cell of distribution of SCPIR for a TCH in non SAIC MS / non SAIC MS pair.
A non SAIC MS is a MS which does not indicate SAIC capability in Classmark.
A non SAIC / non SAIC pair is only possible when both paired MSs are in reality SAIC MSs which do not
declare their SAIC capabilities to the network.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a non SAIC MS / non SAIC MS pair whose
SCPIR lies during a measurement reporting period within the fourth SCPIR range defined by the values
above the threshold
[SCPIR_SAIC_SAIC_THR_3.
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 4 is applied to a channel used by a non SAIC MS /
non SAIC MS pair during a measurement reporting period. It is incremented at the end of the measurement
period
(SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel

Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-37
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1425d - DISTRIB_4_SCPIR_NON_SAIC_NON_SAIC
Channel
....................................................................................................................................................................................................................................

Feature Name VAMOS

MC1426a - DISTRIB_1_SCPIR_NON_SAIC_SAIC
Descripton

Long Name DISTRIB_1_SCPIR_NON_SAIC_SAIC

Definition First cell of distribution of SCPIR for a TCH in non SAIC MS / SAIC MS pair or SAIC / non SAIC pair.
A non SAIC MS is a MS which does not indicate SAIC capability in Classmark.
This pair is only possible when the non SAIC MS is in reality a SAIC MS which does not declare its SAIC
capability to the network.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a non SAIC MS / SAIC MS pair or SAIC / non
SAIC pair whose SCPIR lies during a measurement reporting period within the first SCPIR range defined by
the values strictly below the threshold SCPIR_SAIC_SAIC_THR_1.
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.

Trigger condition This counter is incremented when a SCPIR in the range 1 is applied to a channel used by a non SAIC MS /
SAIC MS pair or SAIC / non SAIC pair during a measurement reporting period. It is incremented at the end
of the measurement period (SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is
received.
Sub Domain 1 Channel
Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
44-38 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1426b - DISTRIB_2_SCPIR_NON_SAIC_SAIC
Channel
....................................................................................................................................................................................................................................

MC1426b - DISTRIB_2_SCPIR_NON_SAIC_SAIC
Descripton

Long Name DISTRIB_2_SCPIR_NON_SAIC_SAIC

Definition Second cell of distribution of SCPIR for a TCH in non SAIC MS / SAIC MS pair or SAIC / non SAIC pair.
A non SAIC MS is a MS which does not indicate SAIC capability in Classmark.
This pair is only possible when the non SAIC MS is in reality a SAIC MS which does not declare its SAIC
capability to the network.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a non SAIC MS / SAIC MS pair or SAIC / non
SAIC pair whose SCPIR lies during a measurement reporting period within the second SCPIR range defined
by the values between the thresholds
[SCPIR_SAIC_SAIC_THR_1,SCPIR_SAIC_SAIC_THR_2[.
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range
Trigger condition This counter is incremented when a SCPIR in the range 2 is applied to a channel used by a non SAIC MS /
SAIC MS pair or SAIC / non SAIC pair during a measurement reporting period. It is incremented at the end
of the measurement period

Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --
Feature Name VAMOS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-39
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1426c - DISTRIB_3_SCPIR_NON_SAIC_SAIC
Channel
....................................................................................................................................................................................................................................

MC1426c - DISTRIB_3_SCPIR_NON_SAIC_SAIC
Descripton

Long Name DISTRIB_3_SCPIR_NON_SAIC_SAIC

Definition Third cell of distribution of SCPIR for a TCH in non SAIC MS / SAIC MS pair or SAIC / non SAIC pair.
A non SAIC MS is a MS which does not indicate SAIC capability in Classmark.
This pair is only possible when the non SAIC MS is in reality a SAIC MS which does not declare its SAIC
capability to the network.
Whenever a FR or HR channel is in VAMOS mode, a SCPIR is determined and sent to the BTS at allocation
time (first establishment or intra-cell HO) and may change due to power control.
This counter allows to monitor the distribution of calls for a non SAIC MS / SAIC MS pair or SAIC / non
SAIC pair whose SCPIR lies during a measurement reporting period within the third SCPIR range defined
by the values between the thresholds
[SCPIR_SAIC_SAIC_THR_2 and SCPIR_SAIC_SAIC_THR_3[.
Consequently this counter allows to have a measure of the time spent by all the relevant calls in this range.
Trigger condition This counter is incremented when a SCPIR in the range 3 is applied to a channel used by a non SAIC MS /
SAIC MS pair or SAIC / non SAIC pair during a measurement reporting period. It is incremented at the end
of the measurement period
(SACCH multiframe: 480ms) i.e. when 44.018 MEASUREMENT REPORT is received.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --
Feature Name VAMOS

....................................................................................................................................................................................................................................
44-40 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage Overview
Resource Allocation & Management
....................................................................................................................................................................................................................................

Resource Allocation & Management

Overview
Purpose
This section contains Resource Allocation & Management parameters.

Contents

MC1401a - NB_TCH_REQ_NON_SAIC 44-41


MC1401b - NB_TCH_REQ_SAIC 44-42
MC1401c - NB_TCH_REQ_VAMOS1 44-42
MC1401d - NB_TCH_REQ_VAMOS2 44-43
MC1402a - NB_TCH_PAIR_ATPT_NON_SAIC 44-43
MC1402b - NB_TCH_PAIR_ATPT_SAIC 44-44
MC1402c - NB_TCH_PAIR_ATPT_VAMOS1 44-44
MC1402d - NB_TCH_PAIR_ATPT_VAMOS2 44-45
MC1403a - NB_TCH_PAIR_SUCC_NON_SAIC 44-45
MC1403b - NB_TCH_PAIR_SUCC_SAIC 44-46
MC1403c - NB_TCH_PAIR_SUCC_VAMOS1 44-46
MC1403d - NB_TCH_PAIR_SUCC_VAMOS2 44-47
MC1427 - NB_MS_NON_SAIC_VAMOS_CAPABLE 44-47

MC1401a - NB_TCH_REQ_NON_SAIC
Descripton

Long Name NB_TCH_REQ_NON_SAIC


Definition Number of TCH normal assignments requests from non-SAIC capable mobiles related to speech CS call.

Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call related to non-SAIC capable
mobiles.
Sub Domain 1 Resource Allocation & Management

Sub Domain 2 Service

Sub Domain 3 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-41
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1401a - NB_TCH_REQ_NON_SAIC
Resource Allocation & Management
....................................................................................................................................................................................................................................

Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1401b - NB_TCH_REQ_SAIC
Descripton

Long Name NB_TCH_REQ_SAIC


Definition Number of TCH normal assignments requests from SAIC capable mobiles related to speech CS call.
Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call related to SAIC capable
mobiles.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service
Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1401c - NB_TCH_REQ_VAMOS1
Descripton

Long Name NB_TCH_REQ_VAMOS1


Definition Number of TCH normal assignments requests from VAMOS-1 capable mobiles related to speech CS call.
Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call related to VAMOS-1 capable
mobiles.
Sub Domain 1 Resource Allocation & Management

Sub Domain 2 Service

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements

....................................................................................................................................................................................................................................
44-42 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1401c - NB_TCH_REQ_VAMOS1
Resource Allocation & Management
....................................................................................................................................................................................................................................

Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1401d - NB_TCH_REQ_VAMOS2
Descripton

Long Name NB_TCH_REQ_VAMOS2

Definition Number of TCH normal assignments requests from VAMOS-2 capable mobiles related to speech CS call.
Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call related to VAMOS-2 capable
mobiles.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service
Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1402a - NB_TCH_PAIR_ATPT_NON_SAIC
Descripton

Long Name NB_TCH_PAIR_ATPT_NON_SAIC

Definition Number of TCH normal assignment from non-SAIC capable mobiles for which pairing attempt is triggered.

Trigger condition 48.058 CHANNEL ACTIVATION sent to the BTS, indicating a channel in VAMOS mode concerning
non-SAIC capable mobiles, not related to handover.
Sub Domain 1 Resource Allocation & Management

Sub Domain 2 Service


Sub Domain 3 --

Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-43
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1402a - NB_TCH_PAIR_ATPT_NON_SAIC
Resource Allocation & Management
....................................................................................................................................................................................................................................

Feature Name VAMOS

MC1402b - NB_TCH_PAIR_ATPT_SAIC
Descripton

Long Name NB_TCH_PAIR_ATPT_SAIC

Definition Number of TCH normal assignment from SAIC capable mobiles for which pairing attempt is triggered.
Trigger condition 48.058 CHANNEL ACTIVATION sent to the BTS, indicating a channel in VAMOS mode concerning SAIC
capable mobiles, not related to handover.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service

Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1402c - NB_TCH_PAIR_ATPT_VAMOS1
Descripton

Long Name NB_TCH_PAIR_ATPT_VAMOS1


Definition Number of TCH normal assignment from VAMOS-1 capable mobiles for which pairing attempt is triggered
Trigger condition 48.058 CHANNEL ACTIVATION sent to the BTS, indicating a channel in VAMOS mode concerning
VAMOS-1 capable mobiles, not related to handover.

Sub Domain 1 Resource Allocation & Management

Sub Domain 2 Service


Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
44-44 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1402d - NB_TCH_PAIR_ATPT_VAMOS2
Resource Allocation & Management
....................................................................................................................................................................................................................................

MC1402d - NB_TCH_PAIR_ATPT_VAMOS2
Descripton

Long Name NB_TCH_PAIR_ATPT_VAMOS2

Definition Number of TCH normal assignment from VAMOS-2 capable mobiles for which pairing attempt is triggered.
Trigger condition 48.058 CHANNEL ACTIVATION sent to the BTS, indicating a channel in VAMOS mode concerning
VAMOS-2 capable mobiles, not related to handover.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS
External Comment --

Feature Name VAMOS

MC1403a - NB_TCH_PAIR_SUCC_NON_SAIC
Descripton

Long Name NB_TCH_PAIR_SUCC_NON_SAIC


Definition Number of TCH normal assignment from non-SAIC capable mobiles whose channel is allocated in the BSC
in VAMOS mode after pairing.
Trigger condition Whenever a 44.018 ASSIGNMENT COMPLETE message is received on Abis interface for a TCH channel
established in Vamos mode (after pairing), not related to handover and related to a non-SAIC capable MS.
Sub Domain 1 Resource Allocation & Management

Sub Domain 2 Service

Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements


Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-45
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1403b - NB_TCH_PAIR_SUCC_SAIC
Resource Allocation & Management
....................................................................................................................................................................................................................................

MC1403b - NB_TCH_PAIR_SUCC_SAIC
Descripton

Long Name NB_TCH_PAIR_SUCC_SAIC

Definition Number of TCH normal assignment from SAIC capable mobiles whose channel is allocated in the BSC in
VAMOS mode after pairing.
Trigger condition Whenever a 44.018 ASSIGNMENT COMPLETE message is received on Abis interface for a TCH channel
established in Vamos mode (after pairing), not related to handover and related to a SAIC capable MS.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service

Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

MC1403c - NB_TCH_PAIR_SUCC_VAMOS1
Descripton

Long Name NB_TCH_PAIR_SUCC_VAMOS1


Definition Number of TCH normal assignment from VAMOS-1 capable mobiles whose channel is allocated in the BSC
in VAMOS mode after pairing.
Trigger condition Whenever a 44.018 ASSIGNMENT COMPLETE message is received on Abis interface for a TCH channel
established in Vamos mode (after pairing), not related to handover and related to a VAMOS1 capable MS.

Sub Domain 1 Resource Allocation & Management

Sub Domain 2 Service


Sub Domain 3 --
Measured Object Common cell

Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
44-46 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1403d - NB_TCH_PAIR_SUCC_VAMOS2
Resource Allocation & Management
....................................................................................................................................................................................................................................

MC1403d - NB_TCH_PAIR_SUCC_VAMOS2
Descripton

Long Name NB_TCH_PAIR_SUCC_VAMOS2

Definition Number of TCH normal assignment from VAMOS-2 capable mobiles whose channel is allocated in the BSC
in VAMOS mode after pairing.
Trigger condition Whenever a 44.018 ASSIGNMENT COMPLETE message is received on Abis interface for a TCH channel
established in Vamos mode (after pairing), not related to handover and related to a VAMOS2 capable MS.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service

Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements

Type Definition Set of counters related to VAMOS


External Comment --

Feature Name VAMOS

MC1427 - NB_MS_NON_SAIC_VAMOS_CAPABLE
Descripton

Long Name NB_MS_NON_SAIC_VAMOS_CAPABLE


Definition Number of non-SAIC MS which are tested as VAMOS capable (undeclared SAIC capability for voice
services).
Trigger condition Incremented each time a non SAIC MS set "to be tested " is checked successfully as VAMOS capable

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service

Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS

External Comment --

Feature Name VAMOS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 44-47
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1427 - NB_MS_NON_SAIC_VAMOS_CAPABLE

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
44-48 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
45 Traffic Load
45

Radio Channel (Traffic Load)

Overview
Purpose
This section contains Radio Channel (Traffic Load) parameters.

Contents

MC1424b - TIME_VAMOS_FR_TCH_BUSY 45-1


MC1424c - TIME_VAMOS_HR_TCH_BUSY 45-2

MC1424b - TIME_VAMOS_FR_TCH_BUSY
Descripton

Long Name TIME_VAMOS_FR_TCH_BUSY


Definition Time during which the radio timeslots of a cell (TCH or a dynamic SDCCH/8) in VAMOS TCH FR usage
are busy.

Trigger condition The counter cumulates over the Accumulation Period all unit times during which a VAMOS TCH FR
channel of the timeslot is busy. Both VAMOS TCH FR of the timeslot are counted independently.

Sub Domain 1 Radio Channel (Traffic Load)


Sub Domain 2 TCH

Sub Domain 3 --

Measured Object Common cell


Type Name VAMOS measurements

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 45-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1424b - TIME_VAMOS_FR_TCH_BUSY
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

Type Definition Set of counters related to VAMOS

External Comment --
Feature Name VAMOS

MC1424c - TIME_VAMOS_HR_TCH_BUSY
Descripton

Long Name TIME_VAMOS_HR_TCH_BUSY

Definition Time during which the radio timeslots of a cell (TCH or a dynamic SDCCH/8) in VAMOS TCH HR usage
are busy.
Trigger condition The counter cumulates over the Accumulation Period all unit times during which a VAMOS TCH HR
channel of the timeslot is busy. All VAMOS TCH HR of the timeslot are counted independently.

Sub Domain 1 Radio Channel (Traffic Load)

Sub Domain 2 TCH


Sub Domain 3 --
Measured Object Common cell
Type Name VAMOS measurements
Type Definition Set of counters related to VAMOS
External Comment --
Feature Name VAMOS

....................................................................................................................................................................................................................................
45-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1424c - TIME_VAMOS_HR_TCH_BUSY

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 45-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1424c - TIME_VAMOS_HR_TCH_BUSY

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
45-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XXV: BSC-TYPE 110 -
Overview measurements

Overview
Purpose
All type 110.

Contents

Chapter 46, Handover 46-1


Chapter 47, Quality of Service 47-1
Chapter 48, Resource Availability & Usage 48-1
Chapter 49, Sustainable & safety 49-1
Chapter 50, Traffic Load 50-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XXV-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 110 - Overview measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XXV-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
46 Handover
46

Directed Retry

Overview
Purpose
This section contains Directed Retry parameters.

Contents

MC151 - NB_INC_IDR_SUCC (29) 46-1


MC153 - NB_INC_IDR_REQ 46-2
MC555 - NB_INC_IDR_PREP_FAIL_CONG_R_ABIS 46-2

MC151 - NB_INC_IDR_SUCC (29)


Descripton

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 Overview measurements

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC151 - NB_INC_IDR_SUCC (29)
Directed Retry
....................................................................................................................................................................................................................................

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

External Comment --
Feature Name --

MC153 - NB_INC_IDR_REQ
Descripton

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 Overview measurements

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

Feature Name --

MC555 - NB_INC_IDR_PREP_FAIL_CONG_R_ABIS
Descripton

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 can be in HR or FR usage.

....................................................................................................................................................................................................................................
46-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC555 - NB_INC_IDR_PREP_FAIL_CONG_R_ABIS
Directed Retry
....................................................................................................................................................................................................................................

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 Overview measurements

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

Feature Name Enhanced Transmission Resource management

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover Overview
Resource Allocation & Management
....................................................................................................................................................................................................................................

Resource Allocation & Management

Overview
Purpose
This section contains Resource Allocation & Management parameters.

Contents

MC480 - NB_TCH_HO_REQ_30_ReturnCSZone 46-4


MC481 - NB_TCH_HO_ATPT_30_ReturnCSZone 46-5
MC482 - NB_TCH_HO_REQ_30_ABORTED 46-5
MC922g - NB_INC_EXT_TCH_3G_2G_HO_PREP_FAIL_3GCONG 46-6
MC929g - NB_INC_EXT_TCH_4G_2G_HO_PREP_FAIL_4GCONG 46-6

MC480 - NB_TCH_HO_REQ_30_ReturnCSZone
Descripton

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 Resource Allocation & Management

Sub Domain 2 --
Sub Domain 3 --

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name Autonomous Packet Resource Allocation (RAE-4)

....................................................................................................................................................................................................................................
46-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC481 - NB_TCH_HO_ATPT_30_ReturnCSZone
Resource Allocation & Management
....................................................................................................................................................................................................................................

MC481 - NB_TCH_HO_ATPT_30_ReturnCSZone
Descripton

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 Resource Allocation & Management


Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Autonomous Packet Resource Allocation (RAE-4)

MC482 - NB_TCH_HO_REQ_30_ABORTED
Descripton

Long Name NB_TCH_HO_REQ_30_ABORTED


Definition Number of TCH intra-cell HO cause 30 requests avoided because the HO Cause 30 delay is stopped due to a
Dedicated to DTM transition with no TCH reallocation.
Trigger condition Whenever the BSC receives a Radio Resource Usage Indication message from the MFS with a radio
timeslot usage changed from (allocated for TCH for DTM, not used for PS) to (allocated for TCH for DTM,
used for PS) while a HO cause delay is running for this radio timeslot, then the counter is incremented by 1.
This is the case of a DTM Assignment with no TCH reallocation occurring before a HO cause 30 request is
triggered.
This counter is significant only if (EN_RETURN_CS_ZONE_HO = Enabled) and (N_DELAYED_HO_
CAUSE30 <> 0) for the corresponding cell.
By definition the counter does not take into account abnormal events (e.g GPRS stop/reset and cell/TRX
reset), nor CS call releases (e.g reception of Assignment Complete for the new TCH, which corresponds to
the case of a DTM Assignment with TCH reallocation).

Sub Domain 1 Resource Allocation & Management

Sub Domain 2 --
Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC482 - NB_TCH_HO_REQ_30_ABORTED
Resource Allocation & Management
....................................................................................................................................................................................................................................

External Comment --

Feature Name Avoid ping-pong between CS and PS zones for DTM MS

MC922g - NB_INC_EXT_TCH_3G_2G_HO_PREP_FAIL_3GCONG
Descripton

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 Resource Allocation & Management


Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements

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

Feature Name 2G/3G inter-operability

MC929g - NB_INC_EXT_TCH_4G_2G_HO_PREP_FAIL_4GCONG
Descripton

Long Name NB_INC_EXT_TCH_4G_2G_HO_PREP_FAIL_4GCONG

Definition Number of 4G to 2G TCH hand over failures in preparation phase due to 4G high load in the target cell.
Trigger condition Whenever a 48.008 HANDOVER FAILURE message is sent with cause "no radio resource available" for a
TCH HO request coming from 4G, due to high load in the target cell. This counter shall be incremented only
if THR_CELL_LOAD_LTE_REJECT < 100%.

Sub Domain 1 Resource Allocation & Management

Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements

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

....................................................................................................................................................................................................................................
46-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC929g - NB_INC_EXT_TCH_4G_2G_HO_PREP_FAIL_4GCONG
Resource Allocation & Management
....................................................................................................................................................................................................................................

External Comment --

Feature Name LTE to GSM handover (SRVCC)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover Overview
SDCCH
....................................................................................................................................................................................................................................

SDCCH

Overview
Purpose
This section contains SDCCH parameters.

Contents

MC101 - NB_INTRA_SDCCH_HO_PREP_FAIL_CONG 46-8


MC607 - NB_SDCCH_HO_20_HighLevNeigCellForcDR 46-9
MC81 - NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG 46-9
MC91 - NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG 46-10

MC101 - NB_INTRA_SDCCH_HO_PREP_FAIL_CONG
Descripton

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 there is no free SDCCH
Sub-channel to allocate the handover to.
Sub Domain 1 SDCCH

Sub Domain 2 Intra

Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements

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

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
46-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC607 - NB_SDCCH_HO_20_HighLevNeigCellForcDR
SDCCH
....................................................................................................................................................................................................................................

MC607 - NB_SDCCH_HO_20_HighLevNeigCellForcDR
Descripton

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" or cause 36 : "preferred band forced directed retry". This counter is related to a forced
directed retry (internal or external).
Trigger condition Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTS because of cause 20 or cause
36.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1 SDCCH

Sub Domain 2 Cause


Sub Domain 3 --

Measured Object Common cell


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

External Comment --
Feature Name --

MC81 - NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG
Descripton

Long Name NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG


Definition MC81=C81, Number of incoming external SDCCH handover -preparation 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 SDCCH handover.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 SDCCH


Sub Domain 2 Incoming External

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC91 - NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG
SDCCH
....................................................................................................................................................................................................................................

MC91 - NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG
Descripton

Long Name NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG

Definition MC91=C91, Number of incoming internal inter-cell SDCCH handover -preparation failures due to
congestion.
Trigger condition Whenever a internal inter-cell SDCCH handover cannot be performed, 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 Overview measurements

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

Feature Name --

....................................................................................................................................................................................................................................
46-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover Overview
SDCCH+TCH
....................................................................................................................................................................................................................................

SDCCH+TCH

Overview
Purpose
This section contains SDCCH+TCH parameters.

Contents

MC1040 - NB_HO_ATPT_23_TrafHandover 46-13


MC1044 - NB_HO_ATPT_24_gencapture 46-13
MC1050 - NB_HO_22_TooShortDistance 46-14
MC642 - NB_INC_EXT_HO_SUCC 46-14
MC643 - NB_INC_EXT_HO_EXEC_FAIL_MS_ACCESS 46-15
MC645a - NB_OUT_EXT_REAL_HO_REQ 46-15
MC646 - NB_OUT_EXT_HO_SUCC 46-16
MC647 - NB_OUT_EXT_HO_EXEC_FAIL_REV 46-16
MC648 - NB_OUT_EXT_HO_EXEC_FAIL_NO_REV 46-17
MC650 - NB_OUT_EXT_HO_ATPT 46-17
MC652 - NB_INC_INT_HO_SUCC 46-18
MC653 - NB_INC_INT_HO_EXEC_FAIL_MS_ACCESS 46-18
MC655a - NB_OUT_INT_HO_REQ 46-19
MC656 - NB_OUT_INT_HO_SUCC 46-19
MC657 - NB_OUT_INT_HO_EXEC_FAIL_REV 46-20
MC658 - NB_OUT_INT_HO_EXEC_FAIL_NO_REV 46-20
MC660 - NB_OUT_INT_HO_ATPT 46-21
MC662 - NB_INTRA_HO_SUCC 46-21
MC663 - NB_INTRA_HO_EXEC_FAIL_NO_REV 46-22
MC667 - NB_INTRA_HO_EXEC_FAIL_REV 46-22
MC670 - NB_HO_2_TooLowQualUp 46-23
MC671 - NB_HO_3_TooLowLevUp 46-23
MC672 - NB_HO_4_TooLowQualDown 46-24
MC673 - NB_HO_5_TooLowLevDown 46-24

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover Overview
SDCCH+TCH
....................................................................................................................................................................................................................................

MC674 - NB_HO_6_TooLongDistance 46-25


MC675 - NB_HO_MSC_TRIG 46-25
MC676 - NB_HO_15_TooHighLevInterfUp 46-26
MC677 - NB_HO_16_TooHighLevInterfDown 46-26
MC678 - NB_HO_12_TooLowPowBudg 46-27
MC679 - NB_HO_21_HighLevNeigCellPrefBand 46-27
MC785a - NB_HO_7_ConsBadSACCHmicroCell 46-28
MC785d - NB_HO_17_TooLowLevUpMicroCell 46-28
MC785e - NB_HO_18_TooLowLevDownMicroCell 46-29
MC785f - NB_HO_14_HighLevNeigLowCellSlowMS 46-29
MC820 - NB_INC_EXT_HO_REQ 46-30
MC821 - NB_INC_EXT_HO_ATPT 46-30
MC830 - NB_INC_INT_HO_REQ 46-31
MC831 - NB_INC_INT_HO_ATPT 46-31
MC870 - NB_INTRA_HO_REQ 46-32
MC871 - NB_INTRA_HO_ATPT 46-32
MC922a - NB_INC_EXT_3G_2G_HO_REQ 46-33
MC922b - NB_INC_EXT_3G_2G_HO_SUCC 46-33
MC922c - NB_INC_EXT_3G_2G_HO_EXEC_FAIL_MS_ACC 46-34
MC922d - NB_INC_EXT_3G_2G_HO_ATPT 46-34
MC929a - NB_INC_EXT_4G_2G_HO_REQ 46-35
MC929b - NB_INC_EXT_4G_2G_HO_SUCC 46-35
MC929c - NB_INC_EXT_4G_2G_HO_EXEC_FAIL_MS_ACC 46-36
MC929d - NB_INC_EXT_4G_2G_HO_ATPT 46-37

....................................................................................................................................................................................................................................
46-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC1040 - NB_HO_ATPT_23_TrafHandover
SDCCH+TCH
....................................................................................................................................................................................................................................

MC1040 - NB_HO_ATPT_23_TrafHandover
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC1044 - NB_HO_ATPT_24_gencapture
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC1050 - NB_HO_22_TooShortDistance
SDCCH+TCH
....................................................................................................................................................................................................................................

MC1050 - NB_HO_22_TooShortDistance
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC642 - NB_INC_EXT_HO_SUCC
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
46-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC643 - NB_INC_EXT_HO_EXEC_FAIL_MS_ACCESS
SDCCH+TCH
....................................................................................................................................................................................................................................

MC643 - NB_INC_EXT_HO_EXEC_FAIL_MS_ACCESS
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC645a - NB_OUT_EXT_REAL_HO_REQ
Descripton

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 Overview measurements

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

Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC646 - NB_OUT_EXT_HO_SUCC
SDCCH+TCH
....................................................................................................................................................................................................................................

MC646 - NB_OUT_EXT_HO_SUCC
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC647 - NB_OUT_EXT_HO_EXEC_FAIL_REV
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
46-16 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC648 - NB_OUT_EXT_HO_EXEC_FAIL_NO_REV
SDCCH+TCH
....................................................................................................................................................................................................................................

MC648 - NB_OUT_EXT_HO_EXEC_FAIL_NO_REV
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC650 - NB_OUT_EXT_HO_ATPT
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-17
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC652 - NB_INC_INT_HO_SUCC
SDCCH+TCH
....................................................................................................................................................................................................................................

MC652 - NB_INC_INT_HO_SUCC
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC653 - NB_INC_INT_HO_EXEC_FAIL_MS_ACCESS
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
46-18 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC655a - NB_OUT_INT_HO_REQ
SDCCH+TCH
....................................................................................................................................................................................................................................

MC655a - NB_OUT_INT_HO_REQ
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC656 - NB_OUT_INT_HO_SUCC
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-19
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC657 - NB_OUT_INT_HO_EXEC_FAIL_REV
SDCCH+TCH
....................................................................................................................................................................................................................................

MC657 - NB_OUT_INT_HO_EXEC_FAIL_REV
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC658 - NB_OUT_INT_HO_EXEC_FAIL_NO_REV
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
46-20 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC660 - NB_OUT_INT_HO_ATPT
SDCCH+TCH
....................................................................................................................................................................................................................................

MC660 - NB_OUT_INT_HO_ATPT
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC662 - NB_INTRA_HO_SUCC
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-21
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC663 - NB_INTRA_HO_EXEC_FAIL_NO_REV
SDCCH+TCH
....................................................................................................................................................................................................................................

MC663 - NB_INTRA_HO_EXEC_FAIL_NO_REV
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC667 - NB_INTRA_HO_EXEC_FAIL_REV
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
46-22 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC670 - NB_HO_2_TooLowQualUp
SDCCH+TCH
....................................................................................................................................................................................................................................

MC670 - NB_HO_2_TooLowQualUp
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC671 - NB_HO_3_TooLowLevUp
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-23
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC672 - NB_HO_4_TooLowQualDown
SDCCH+TCH
....................................................................................................................................................................................................................................

MC672 - NB_HO_4_TooLowQualDown
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC673 - NB_HO_5_TooLowLevDown
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
46-24 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC674 - NB_HO_6_TooLongDistance
SDCCH+TCH
....................................................................................................................................................................................................................................

MC674 - NB_HO_6_TooLongDistance
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC675 - NB_HO_MSC_TRIG
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-25
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC676 - NB_HO_15_TooHighLevInterfUp
SDCCH+TCH
....................................................................................................................................................................................................................................

MC676 - NB_HO_15_TooHighLevInterfUp
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC677 - NB_HO_16_TooHighLevInterfDown
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
46-26 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC678 - NB_HO_12_TooLowPowBudg
SDCCH+TCH
....................................................................................................................................................................................................................................

MC678 - NB_HO_12_TooLowPowBudg
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC679 - NB_HO_21_HighLevNeigCellPrefBand
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-27
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC785a - NB_HO_7_ConsBadSACCHmicroCell
SDCCH+TCH
....................................................................................................................................................................................................................................

MC785a - NB_HO_7_ConsBadSACCHmicroCell
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC785d - NB_HO_17_TooLowLevUpMicroCell
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
46-28 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC785e - NB_HO_18_TooLowLevDownMicroCell
SDCCH+TCH
....................................................................................................................................................................................................................................

MC785e - NB_HO_18_TooLowLevDownMicroCell
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC785f - NB_HO_14_HighLevNeigLowCellSlowMS
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-29
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC820 - NB_INC_EXT_HO_REQ
SDCCH+TCH
....................................................................................................................................................................................................................................

MC820 - NB_INC_EXT_HO_REQ
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC821 - NB_INC_EXT_HO_ATPT
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
46-30 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC830 - NB_INC_INT_HO_REQ
SDCCH+TCH
....................................................................................................................................................................................................................................

MC830 - NB_INC_INT_HO_REQ
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC831 - NB_INC_INT_HO_ATPT
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-31
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC870 - NB_INTRA_HO_REQ
SDCCH+TCH
....................................................................................................................................................................................................................................

MC870 - NB_INTRA_HO_REQ
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC871 - NB_INTRA_HO_ATPT
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
46-32 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC922a - NB_INC_EXT_3G_2G_HO_REQ
SDCCH+TCH
....................................................................................................................................................................................................................................

MC922a - NB_INC_EXT_3G_2G_HO_REQ
Descripton

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' and
SAI value does not indicate E-UTRAN),

Sub Domain 1 SDCCH+TCH


Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name B8 BSC counters improvements

MC922b - NB_INC_EXT_3G_2G_HO_SUCC
Descripton

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 and SAI value does not indicate E-UTRAN).

Sub Domain 1 SDCCH+TCH

Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements

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

Feature Name B8 BSC counters improvements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-33
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC922c - NB_INC_EXT_3G_2G_HO_EXEC_FAIL_MS_ACC
SDCCH+TCH
....................................................................................................................................................................................................................................

MC922c - NB_INC_EXT_3G_2G_HO_EXEC_FAIL_MS_ACC
Descripton

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' and SAI value does not indicate E-UTRAN)

Sub Domain 1 SDCCH+TCH


Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name B8 BSC counters improvements

MC922d - NB_INC_EXT_3G_2G_HO_ATPT
Descripton

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' and
SAI value does not indicate E-UTRAN).

Sub Domain 1 SDCCH+TCH

Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements

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

....................................................................................................................................................................................................................................
46-34 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC922d - NB_INC_EXT_3G_2G_HO_ATPT
SDCCH+TCH
....................................................................................................................................................................................................................................

External Comment --

Feature Name B8 BSC counters improvements

MC929a - NB_INC_EXT_4G_2G_HO_REQ
Descripton

Long Name NB_INC_EXT_4G_2G_HO_REQ

Definition Number of incoming external SDCCH and TCH HO requests from a LTE 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 LTE 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' and
SAI value indicates E-UTRAN ),
Sub Domain 1 SDCCH+TCH
Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name LTE to GSM handover (SRVCC)

MC929b - NB_INC_EXT_4G_2G_HO_SUCC
Descripton

Long Name NB_INC_EXT_4G_2G_HO_SUCC


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

Trigger condition 44.018HANDOVER_COMPLETE message received from the MS. Only handovers from a LTE 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 and SAI value indicates E-UTRAN).
Sub Domain 1 SDCCH+TCH

Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-35
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC929b - NB_INC_EXT_4G_2G_HO_SUCC
SDCCH+TCH
....................................................................................................................................................................................................................................

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

External Comment --
Feature Name LTE to GSM handover (SRVCC)

MC929c - NB_INC_EXT_4G_2G_HO_EXEC_FAIL_MS_ACC
Descripton

Long Name NB_INC_EXT_4G_2G_HO_EXEC_FAIL_MS_ACC

Definition Number of incoming external TCH and SDCCH LTE 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 LTE system.
2) Reception of 48.008CLEAR COMMAND (cause= "radio interface failure, reversion to old channel") for
a HO from a LTE system.
Handovers from a LTE 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' and SAI value indicates
E-UTRAN.
Sub Domain 1 SDCCH+TCH
Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements

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

Feature Name LTE to GSM handover (SRVCC)

....................................................................................................................................................................................................................................
46-36 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC929d - NB_INC_EXT_4G_2G_HO_ATPT
SDCCH+TCH
....................................................................................................................................................................................................................................

MC929d - NB_INC_EXT_4G_2G_HO_ATPT
Descripton

Long Name NB_INC_EXT_4G_2G_HO_ATPT

Definition Number of incoming external SDCCH and TCH HO attempts from a LTE 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 LTE 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') and
SAI value indicates E-UTRAN.
Sub Domain 1 SDCCH+TCH

Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name LTE to GSM handover (SRVCC)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-37
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover Overview
Speech
....................................................................................................................................................................................................................................

Speech

Overview
Purpose
This section contains Speech parameters.

Contents

MC936 - NB_HO_INTER_TFO_AMR_WB 46-38


MC937 - NB_HO_EXT_TFO_AMR_WB 46-39

MC936 - NB_HO_INTER_TFO_AMR_WB
Descripton

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 Overview measurements

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

External Comment --
Feature Name Support of TFO on NB-AMR

....................................................................................................................................................................................................................................
46-38 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC937 - NB_HO_EXT_TFO_AMR_WB
Speech
....................................................................................................................................................................................................................................

MC937 - NB_HO_EXT_TFO_AMR_WB
Descripton

Long Name NB_HO_EXT_TFO_AMR_WB

Definition Number of TCH assigned using AMR-WB for which TFO has been successfully 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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Support of TFO on NB-AMR

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-39
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover Overview
TCH
....................................................................................................................................................................................................................................

TCH

Overview
Purpose
This section contains TCH parameters.

Contents

MC41b - NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH 46-41


MC448a - NB_TCH_HO_ATPT_26_BadQualHR 46-42
MC448b - NB_TCH_HO_ATPT_27_GoodQualFR 46-42
MC449 - NB_TCH_HO_ATPT_28_FastTraffic 46-43
MC460a - NB_TCH_EMERGENCY_HO_PRESERVATION 46-43
MC461 - NB_TCH_HO_ATPT_29_TFO 46-44
MC462a - NB_OUT_INTER_PLMN_TCH_HO_REQ 46-44
MC462b - NB_OUT_INTER_PLMN_TCH_HO_ATPT 46-45
MC462c - NB_OUT_INTER_PLMN_TCH_HO_SUCC 46-45
MC463a - NB_INC_INTER_PLMN_TCH_HO_REQ 46-46
MC463b - NB_INC_INTER_PLMN_TCH_HO_ATPT 46-47
MC463c - NB_INC_INTER_PLMN_TCH_HO_SUCC 46-47
MC490a - NB_HO_INTRA_ATPT_33_MSC_trigg_int 46-48
MC490b - NB_HO_INTER_ATPT_33_MSC_trigg_int 46-48
MC541 - NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS 46-49
MC541a - NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS 46-49
MC551 - NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS 46-50
MC561 - NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS 46-51
MC586a - NB_TCH_HO_ATPT_10_TooLowLevUpInZone 46-51
MC586b - NB_TCH_HO_ATPT_11_TooLowLevDownInZone 46-52
MC586c - NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone 46-52
MC710 - NB_TCH_OUT_HO_REQ_TRX 46-53
MC922e - NB_INC_EXT_TCH_3G_2G_HO_EMERGENCY_REQ 46-54
MC922f - NB_INC_EXT_TCH_3G_2G_HO_REQ 46-54

....................................................................................................................................................................................................................................
46-40 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover Overview
TCH
....................................................................................................................................................................................................................................

MC924b - NB_OUT_2G_3G_HO_REQ 46-55


MC924c - NB_OUT_2G_3G_HO_SUCC 46-55
MC924d - NB_OUT_2G_3G_HO_ATPT 46-56
MC924e - NB_OUT_2G_3G_HO_EXEC_FAIL_NO_REV 46-56
MC924f - NB_OUT_2G_3G_HO_EXEC_FAIL_REV 46-57
MC924g - NB_OUT_2G_3G_HO_PREP_FAIL 46-57
MC929e - NB_INC_EXT_TCH_4G_2G_HO_EMERGENCY_REQ 46-58
MC929f - NB_INC_EXT_TCH_4G_2G_HO_REQ 46-59
MC934 - NB_INC_EXT_TCH_HO_PREP_FAIL_PMIS 46-59
MC975a - NB_BSS_Int_HO_with_MSC_REQ 46-60
MC975b - NB_BSS_Int_HO_with_MSC_SUCC 46-60
MC975c - NB_BSS_Int_HO_with_MSC_ALLOC 46-61
MC975d - NB_BSS_Int_HO_with_MSC_ATPT 46-61

MC41b - NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH
Descripton

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 intra-PLMN handover events.
Sub Domain 1 TCH

Sub Domain 2 Incoming External


Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-41
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC448a - NB_TCH_HO_ATPT_26_BadQualHR
TCH
....................................................................................................................................................................................................................................

MC448a - NB_TCH_HO_ATPT_26_BadQualHR
Descripton

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 Overview measurements


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

Feature Name Introduction of AMR (NB-AMR)

MC448b - NB_TCH_HO_ATPT_27_GoodQualFR
Descripton

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 Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 27 on TCH.
Sub Domain 1 TCH

Sub Domain 2 Cause


Sub Domain 3 --

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name Introduction of AMR (NB-AMR)

....................................................................................................................................................................................................................................
46-42 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC449 - NB_TCH_HO_ATPT_28_FastTraffic
TCH
....................................................................................................................................................................................................................................

MC449 - NB_TCH_HO_ATPT_28_FastTraffic
Descripton

Long Name NB_TCH_HO_ATPT_28_FastTraffic

Definition Number of handover attempts, with the cause 28 (Fast Traffic Handover).
Trigger condition Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS 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 Overview measurements


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

Feature Name Instantaneous Peaks Management

MC460a - NB_TCH_EMERGENCY_HO_PRESERVATION
Descripton

Long Name NB_TCH_EMERGENCY_HO_PRESERVATION


Definition Number of high priority TCH requests served in non VAMOS mode when
1) the number of free 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 conditions are 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 timeslots is less than or equal to NUM_TCH_EGNCY_HO and there is at least one
request queued for this cell.
3) TCH is not allocated in VAMOS mode
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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-43
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC460a - NB_TCH_EMERGENCY_HO_PRESERVATION
TCH
....................................................................................................................................................................................................................................

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name B8 BSC counters improvements

MC461 - NB_TCH_HO_ATPT_29_TFO
Descripton

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 Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 29 on TCH.
Sub Domain 1 TCH

Sub Domain 2 Cause


Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name Support of TFO (Tandem Free Operation)

MC462a - NB_OUT_INTER_PLMN_TCH_HO_REQ
Descripton

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

....................................................................................................................................................................................................................................
46-44 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC462a - NB_OUT_INTER_PLMN_TCH_HO_REQ
TCH
....................................................................................................................................................................................................................................

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name --

MC462b - NB_OUT_INTER_PLMN_TCH_HO_ATPT
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name --

MC462c - NB_OUT_INTER_PLMN_TCH_HO_SUCC
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-45
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC462c - NB_OUT_INTER_PLMN_TCH_HO_SUCC
TCH
....................................................................................................................................................................................................................................

Sub Domain 2 Outgoing External

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name --

MC463a - NB_INC_INTER_PLMN_TCH_HO_REQ
Descripton

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 Overview measurements


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

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
46-46 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC463b - NB_INC_INTER_PLMN_TCH_HO_ATPT
TCH
....................................................................................................................................................................................................................................

MC463b - NB_INC_INTER_PLMN_TCH_HO_ATPT
Descripton

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 Overview measurements

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

Feature Name --

MC463c - NB_INC_INTER_PLMN_TCH_HO_SUCC
Descripton

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 Overview measurements

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

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-47
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC490a - NB_HO_INTRA_ATPT_33_MSC_trigg_int
TCH
....................................................................................................................................................................................................................................

MC490a - NB_HO_INTRA_ATPT_33_MSC_trigg_int
Descripton

Long Name NB_HO_INTRA_ATPT_33_MSC_trigg_int

Definition Number of MSC initiated internal handover (cause 33: codec change triggered by the core network)
triggering an intra cell handover
Trigger condition Whenever 44.018 ASSIGNMENT COMMAND/HANDOVER COMMAND is sent to the MS via the BTS
because of intra cell handover cause 33 on TCH
In this case the BSC triggers a "BSS internal handover with MSC support" procedure on MSC request
(INTERNAL HANDOVER ENQUIRY).
Sub Domain 1 TCH

Sub Domain 2 Cause


Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name AUPoIP A interface user plane over IP

MC490b - NB_HO_INTER_ATPT_33_MSC_trigg_int
Descripton

Long Name NB_HO_INTER_ATPT_33_MSC_trigg_int


Definition Number of MSC initiated internal handover (cause 33: codec change triggered by the core network)
triggering an inter cell handover
Trigger condition Whenever 44.018 ASSIGNMENT COMMAND/HANDOVER COMMAND is sent to the MS via the BTS
because of inter cell handover cause 33 on TCH
In this case the BSC triggers a "BSS internal handover with MSC support" procedure on MSC request
(INTERNAL HANDOVER ENQUIRY).

Sub Domain 1 TCH


Sub Domain 2 Cause

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

....................................................................................................................................................................................................................................
46-48 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC490b - NB_HO_INTER_ATPT_33_MSC_trigg_int
TCH
....................................................................................................................................................................................................................................

Feature Name AUPoIP A interface user plane over IP

MC541 - NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS
Descripton

Long Name NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS

Definition Number of incoming external TCH (in HR or FR usage) handover -preparation failures due to congestion
(C541a), or A-traffic-channel status mismatch between the BSC and the MSC (C41b).
Trigger condition Note: This counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 TCH


Sub Domain 2 Incoming External

Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name Enhanced Transmission Resource management

MC541a - NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS
Descripton

Long Name NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS


Definition Number of incoming external TCH (in HR or FR usage) handover -preparation 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, 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 TCH
Sub Domain 2 Incoming External

Sub Domain 3 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-49
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC541a - NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS
TCH
....................................................................................................................................................................................................................................

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name --

MC551 - NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS
Descripton

Long Name NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS


Definition Number of incoming internal inter-cell TCH (in HR or FR usage) handover -preparation failures due to
congestion.
Trigger condition Whenever an internal inter-cell TCH handover cannot be performed, 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 NB_MAX_ACTIVE_
TCH_TS parameter

Sub Domain 1 TCH


Sub Domain 2 Incoming Internal

Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
46-50 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC561 - NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS
TCH
....................................................................................................................................................................................................................................

MC561 - NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS
Descripton

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 in non
VAMOS mode. 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 in non VAMOS mode cannot be performed, because there is
no free TCH channel to serve the handover (In VAMOS mode when no pairing target candidate is found,
this counter is not incremented)
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 processing capacity of AbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_
TCH_TS parameter

Sub Domain 1 TCH


Sub Domain 2 Intra

Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Enhanced Transmission Resource management

MC586a - NB_TCH_HO_ATPT_10_TooLowLevUpInZone
Descripton

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 Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 10.

Sub Domain 1 TCH


Sub Domain 2 Cause

Sub Domain 3 --

Measured Object Common cell

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-51
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC586a - NB_TCH_HO_ATPT_10_TooLowLevUpInZone
TCH
....................................................................................................................................................................................................................................

Type Name Overview measurements

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

Feature Name --

MC586b - NB_TCH_HO_ATPT_11_TooLowLevDownInZone
Descripton

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 concentric cell environment.
Trigger condition Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 11.

Sub Domain 1 TCH


Sub Domain 2 Cause
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name --

MC586c - NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone
Descripton

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 Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 13.

Sub Domain 1 TCH


Sub Domain 2 Cause

Sub Domain 3 --

Measured Object Common cell


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

....................................................................................................................................................................................................................................
46-52 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC586c -
TCH NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone
....................................................................................................................................................................................................................................

External Comment --

Feature Name --

MC710 - NB_TCH_OUT_HO_REQ_TRX
Descripton

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, excluding handover initiation for VAMOS HO cause 34 and 35.
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 Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-53
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC922e - NB_INC_EXT_TCH_3G_2G_HO_EMERGENCY_REQ
TCH
....................................................................................................................................................................................................................................

MC922e - NB_INC_EXT_TCH_3G_2G_HO_EMERGENCY_REQ
Descripton

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
which does not indicate E-UTRAN 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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name 2G/3G inter-operability

MC922f - NB_INC_EXT_TCH_3G_2G_HO_REQ
Descripton

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
which does not indicate E-UTRAN

Sub Domain 1 TCH


Sub Domain 2 --

Sub Domain 3 --

Measured Object Common cell


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

External Comment --

Feature Name 2G/3G inter-operability

....................................................................................................................................................................................................................................
46-54 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC924b - NB_OUT_2G_3G_HO_REQ
TCH
....................................................................................................................................................................................................................................

MC924b - NB_OUT_2G_3G_HO_REQ
Descripton

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 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 Overview measurements


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

External Comment --
Feature Name 2G/3G inter-operability

MC924c - NB_OUT_2G_3G_HO_SUCC
Descripton

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: 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 Overview measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-55
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC924c - NB_OUT_2G_3G_HO_SUCC
TCH
....................................................................................................................................................................................................................................

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

External Comment --
Feature Name 2G/3G inter-operability

MC924d - NB_OUT_2G_3G_HO_ATPT
Descripton

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 Whenever the 44.018 HANDOVER COMMAND message is sent on Abis 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 Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name 2G/3G inter-operability

MC924e - NB_OUT_2G_3G_HO_EXEC_FAIL_NO_REV
Descripton

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 Whenever the timer supervising the handover procedure on the serving cell (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 intra-PLMN handover events.

Sub Domain 1 TCH


Sub Domain 2 Outgoing External

Sub Domain 3 --

....................................................................................................................................................................................................................................
46-56 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC924e - NB_OUT_2G_3G_HO_EXEC_FAIL_NO_REV
TCH
....................................................................................................................................................................................................................................

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name 2G/3G inter-operability

MC924f - NB_OUT_2G_3G_HO_EXEC_FAIL_REV
Descripton

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 Whenever a 44.018 HANDOVER FAILURE message is received on Abis interface from the serving cell ,
during an external TCH handover 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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name 2G/3G inter-operability

MC924g - NB_OUT_2G_3G_HO_PREP_FAIL
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-57
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC924g - NB_OUT_2G_3G_HO_PREP_FAIL
TCH
....................................................................................................................................................................................................................................

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

Feature Name 2G/3G inter-operability

MC929e - NB_INC_EXT_TCH_4G_2G_HO_EMERGENCY_REQ
Descripton

Long Name NB_INC_EXT_TCH_4G_2G_HO_EMERGENCY_REQ


Definition Number of incoming 4G 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 SAI value indicating E-UTRAN
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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name LTE to GSM handover (SRVCC)

....................................................................................................................................................................................................................................
46-58 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC929f - NB_INC_EXT_TCH_4G_2G_HO_REQ
TCH
....................................................................................................................................................................................................................................

MC929f - NB_INC_EXT_TCH_4G_2G_HO_REQ
Descripton

Long Name NB_INC_EXT_TCH_4G_2G_HO_REQ

Definition Number of incoming 4G 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
and SAI value indicating E-UTRAN.

Sub Domain 1 TCH


Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

Feature Name LTE to GSM handover (SRVCC)

MC934 - NB_INC_EXT_TCH_HO_PREP_FAIL_PMIS
Descripton

Long Name NB_INC_EXT_TCH_HO_PREP_FAIL_PMIS


Definition Number of incoming external TCH (in HR or FR usage) handover -preparation failures due to A interface
mismatch between the BSC and the MSC.
Trigger condition Whenever a 48.008 HANDOVER FAILURE message with a cause value of "circuit pool mismatch" is sent
on A interface from the target BSC to 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 Overview measurements

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

Feature Name AMR WB speech codec GMSK

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-59
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC975a - NB_BSS_Int_HO_with_MSC_REQ
TCH
....................................................................................................................................................................................................................................

MC975a - NB_BSS_Int_HO_with_MSC_REQ
Descripton

Long Name NB_BSS_Int_HO_with_MSC_REQ

Definition Number of "BSS internal handover with MSC support" request


Trigger condition BSC selects a BSS internal handover with MSC support when AoIP interface applies with the sending to the
MSC of INTERNAL HANDOVER REQUIRED.

Sub Domain 1 TCH


Sub Domain 2 Internal MSC Support

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

Feature Name AUPoIP A interface user plane over IP

MC975b - NB_BSS_Int_HO_with_MSC_SUCC
Descripton

Long Name NB_BSS_Int_HO_with_MSC_SUCC


Definition Number of "BSS internal handover with MSC support" success.
Trigger condition Whenever a 44.018 ASSIGNMENT COMPLETE/HANDOVER COMPLETE message is received on Abis
interface from the target cell for a TCH channel that is involved in an BSS internal handover with MSC
support and is reported to MSC in HANDOVER COMPLETE message.
Sub Domain 1 TCH

Sub Domain 2 Internal MSC Support

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
46-60 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC975c - NB_BSS_Int_HO_with_MSC_ALLOC
TCH
....................................................................................................................................................................................................................................

MC975c - NB_BSS_Int_HO_with_MSC_ALLOC
Descripton

Long Name NB_BSS_Int_HO_with_MSC_ALLOC

Definition Number of allocation due to "BSS internal handover with MSC support"
Trigger condition 08.58 CHANNEL ACTIVATION to be sent to the BTS due to receipt of INTERNAL HANDOVER
COMMAND from MSC.

Sub Domain 1 TCH


Sub Domain 2 Internal MSC Support

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

Feature Name AUPoIP A interface user plane over IP

MC975d - NB_BSS_Int_HO_with_MSC_ATPT
Descripton

Long Name NB_BSS_Int_HO_with_MSC_ATPT


Definition Number of "BSS internal handover with MSC support" attempts.
Trigger condition Sending of 04.08ASSIGNMENT COMMAND/HANDOVER COMMAND to the MS on the serving
channel. Only handovers which has triggered "BSS internal handover with MSC support" procedure shall be
taken into account.
Sub Domain 1 TCH

Sub Domain 2 Internal MSC Support

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 46-61
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Handover MC975d - NB_BSS_Int_HO_with_MSC_ATPT

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
46-62 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
47 Quality of Service
47

BSC

Overview
Purpose
This section contains BSC parameters.

Contents

MC1614 - OLC_ NB_DISCARDED_CHN_REQD_ACCESS_DELAY 47-2


MC959 - NB_PS_CHAN_REQD 47-2
MC960 - NB_DISCARDED_PS_CHAN_REQD_BECAUSE_GSL_ 47-3
CONGESTION
MC962 - NB_INVALID_CHAN_REQD_RECEIVED_BY_BSC 47-3
MC963 - NB_NON_PS_CHAN_REQD_DISCRADED_BECAUSE_ 47-5
CONGESTION
MC964 - NB_VALID_LOCATION_UPDATE_RECEIVED_BY_BSC 47-6

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1614 - OLC_ NB_DISCARDED_CHN_REQD_ACCESS_DELAY
BSC
....................................................................................................................................................................................................................................

MC1614 - OLC_ NB_DISCARDED_CHN_REQD_ACCESS_DELAY


Descripton

Long Name OLC_ NB_DISCARDED_CHN_REQD_ACCESS_DELAY

Definition Number of discarded 48.058 CHANNEL REQUIRED (for all establishment cause) messages received by
the BSC due to too high access delay
Trigger condition Whenever a 48.058 CHANNEL REQUIRED message (either for PS traffic or for CS traffic) is received on
Abis
interface from a TRX of a site (RRH) in an OLC configuration with the Access delay value greater than or
equal to RRH_RACH_TA_FILTER.
Sub Domain 1 BSC

Sub Domain 2 --
Sub Domain 3 --
Measured Object Site_TRX
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name --

MC959 - NB_PS_CHAN_REQD
Descripton

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 Overview measurements

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

....................................................................................................................................................................................................................................
47-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC959 - NB_PS_CHAN_REQD
BSC
....................................................................................................................................................................................................................................

Feature Name --

MC960 - NB_DISCARDED_PS_CHAN_REQD_BECAU-
SE_GSL_CONGESTION
Descripton

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: see the BTP
parameters : 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 Overview measurements


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

External Comment --
Feature Name --

MC962 - NB_INVALID_CHAN_REQD_RECEIVED_BY_BSC
Descripton

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.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC962 - NB_INVALID_CHAN_REQD_RECEIVED_BY_BSC
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 (Random Access Reference)" 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 Overview measurements

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

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
47-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC963 - NB_NON_PS_CHAN_REQD_DISCRADED_BE-
BSC CAUSE_CONGESTION
....................................................................................................................................................................................................................................

MC963 - NB_NON_PS_CHAN_REQD_DISCRADED_BE-
CAUSE_CONGESTION
Descripton

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 8, 7 and 6 of "RA
(Random Access Reference)" byte in the 48.058 CHANNEL 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 8, 7 and 6 of "RA
(Random Access Reference)" byte in the 48.058 CHANNEL 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 Overview measurements


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

External Comment --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC963 - NB_NON_PS_CHAN_REQD_DISCRADED_BE-
BSC CAUSE_CONGESTION
....................................................................................................................................................................................................................................

Feature Name --

MC964 - NB_VALID_LOCATION_UPDATE_RECEIVED_BY_BSC
Descripton

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". Note that from 3GPP rel 11 (TS 44.018), UE shall not indicate
location update in their establishment cause for CS fallback (Location update with follow on request
(MOC)). The behaviour of pre-Rel11 UE is not 3GPP defined and may vary.
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 Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

....................................................................................................................................................................................................................................
47-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Directed Retry
....................................................................................................................................................................................................................................

Directed Retry

Overview
Purpose
This section contains Directed Retry parameters.

Contents

MC142e - NB_OUT_IDR_SUCC 47-7


MC142f - NB_OUT_EDR_SUCC 47-8
MC717a - NB_INC_IDR_SUCC_TRX 47-8
MC719a - NB_INC_IDR_SUCC_NON_AMR 47-9
MC719b - NB_INC_IDR_SUCC_ALL_AMR 47-9

MC142e - NB_OUT_IDR_SUCC
Descripton

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 Overview measurements


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

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC142f - NB_OUT_EDR_SUCC
Directed Retry
....................................................................................................................................................................................................................................

MC142f - NB_OUT_EDR_SUCC
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC717a - NB_INC_IDR_SUCC_TRX
Descripton

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 Overview measurements

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

Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
47-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC719a - NB_INC_IDR_SUCC_NON_AMR
Directed Retry
....................................................................................................................................................................................................................................

MC719a - NB_INC_IDR_SUCC_NON_AMR
Descripton

Long Name NB_INC_IDR_SUCC_NON_AMR

Definition Number of incoming directed retry (towards a TCH channel in HR or FR usage) successes for speech calls
which has been established with non-AMR codec types (GSM FR/HR or EFR).
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 for a speech call established with a non-AMR
codec type.
48.008 ASSIGNMENT COMPLETE is considered for speech version discrimination.
This counter is triggered only when 48.008 ASSIGNMENT COMPLETE was sent from BSC to MSC on A
interface for a TCH channel assigned indicating the usage of speech version 1 (FR or HR channel type) or
speech version 2 (EFR channel type)
Sub Domain 1 Directed Retry
Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

MC719b - NB_INC_IDR_SUCC_ALL_AMR
Descripton

Long Name NB_INC_IDR_SUCC_ALL_AMR

Definition Number of incoming directed retry (towards a TCH channel in HR or FR usage) successes for speech calls
which has been established with an AMR codec types (AMR or AMR-WB).

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 for a speech call established with an AMR
codec type.
48.008 ASSIGNMENT COMPLETE is considered for speech version discrimination.
This counter is triggered only when 48.008 ASSIGNMENT COMPLETE was sent from BSC to MSC on A
interface for a TCH channel assigned indicating the usage of speech version 3 (AMR-FR and AMR-HR) or
speech version 5 (AMR-WB channel type)

Sub Domain 1 Directed Retry

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC719b - NB_INC_IDR_SUCC_ALL_AMR
Directed Retry
....................................................................................................................................................................................................................................

Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

....................................................................................................................................................................................................................................
47-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Established Phase
....................................................................................................................................................................................................................................

Established Phase

Overview
Purpose
This section contains Established Phase parameters.

Contents

MC137 - NB_SDCCH_DROP_EST_PHAS_BSS_PB 47-11


MC138 - NB_SDCCH_DROP_EST_PHAS_RLF 47-12
MC14c - NB_TCH_DROP_EST_PHAS_BSS_PB 47-13
MC1610 - OLC_NB_TCH_DROP_EST_PHAS_RLF_TRX 47-14
MC1611 - OLC_NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX 47-14
MC1613 - OLC_NB_TCH_DROP_EST_PHAS_BSS_PB_TRX 47-15
MC162 - NB_TCH_DROP_DTAP_EST_PHAS 47-16
MC736 - NB_TCH_DROP_EST_PHAS_RLF_TRX 47-17
MC739 - NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX 47-17
MC993 - NB_AMR_TCH_DROP_RLF_TRX 47-18
MC994 - NB_AMR_TCH_DROP_RLF_TRX_RSACCH 47-19

MC137 - NB_SDCCH_DROP_EST_PHAS_BSS_PB
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC137 - NB_SDCCH_DROP_EST_PHAS_BSS_PB
Established Phase
....................................................................................................................................................................................................................................

Sub Domain 2 SDCCH

Sub Domain 3 Failure


Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name --

MC138 - NB_SDCCH_DROP_EST_PHAS_RLF
Descripton

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 Overview measurements

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

Feature Name --

....................................................................................................................................................................................................................................
47-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC14c - NB_TCH_DROP_EST_PHAS_BSS_PB
Established Phase
....................................................................................................................................................................................................................................

MC14c - NB_TCH_DROP_EST_PHAS_BSS_PB
Descripton

Long Name NB_TCH_DROP_EST_PHAS_BSS_PB

Definition Number of TCH (in HR or FR usage) drops 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.
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 Overview measurements

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

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1610 - OLC_NB_TCH_DROP_EST_PHAS_RLF_TRX
Established Phase
....................................................................................................................................................................................................................................

MC1610 - OLC_NB_TCH_DROP_EST_PHAS_RLF_TRX
Descripton

Long Name OLC_NB_TCH_DROP_EST_PHAS_RLF_TRX

Definition Number of TCH (in HR or FR usage) drops due to radio link failure (radio link timeout or LAPDm
timer expiry), in OLC configuration, per TRX and per site.
This counter takes into account TCH in traffic or in signaling mode.

Trigger condition For TCH using AMR and non-AMR codecs:


1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "radio link
failure" is received on Abis interface for a TCH channel (after successful seizure).
2) Whenever a 48.058 ERROR INDICATION message is received on Abis interface and leads to a loss of
call.
The identification of the site (RRH) inside the One Logical Cell OLC is obtained by BSC via RRH ID in
MEASUREMENT RESULT

Sub Domain 1 Established Phase


Sub Domain 2 TCH
Sub Domain 3 --
Measured Object Site_TRX
Type Name Overview measurements

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

Feature Name --

MC1611 - OLC_NB_TCH_DROP_EST_PHAS_REM_TRANS-
_FAIL_TRX
Descripton

Long Name OLC_NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX

Definition Number of TCH (in HR or FR usage) drops due to remote transcoder failures in OLC configuration, per
TRX and per site.

....................................................................................................................................................................................................................................
47-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1611 - OLC_NB_TCH_DROP_EST_PHAS_REM_TRANS-
Established Phase _FAIL_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. Whether A User plane Interface over IP AUPoIP applies to
the call, in case of normal assignment or directed retry cases, the BSC considers a TCH connection as
"established" only once first DL RTP has been received from MGW.
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.
The identification of the site (RRH) inside the One Logical Cell OLC is obtained by BSC via RRH ID in
MEASUREMENT RESULT.

Sub Domain 1 Established Phase


Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Site_TRX
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name --

MC1613 - OLC_NB_TCH_DROP_EST_PHAS_BSS_PB_TRX
Descripton

Long Name OLC_NB_TCH_DROP_EST_PHAS_BSS_PB_TRX

Definition Number of TCH (in HR or FR usage) drops due to BSS problem in OLC configuration, per TRX and per
site.
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.
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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1613 - OLC_NB_TCH_DROP_EST_PHAS_BSS_PB_TRX
Established Phase
....................................................................................................................................................................................................................................

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).
The identification of the site (RRH) inside the One Logical Cell OLC is obtained by BSC via RRH ID in
MEASUREMENT RESULT

Sub Domain 1 Established Phase


Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Site_TRX
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name --

MC162 - NB_TCH_DROP_DTAP_EST_PHAS
Descripton

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 Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

....................................................................................................................................................................................................................................
47-16 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC736 - NB_TCH_DROP_EST_PHAS_RLF_TRX
Established Phase
....................................................................................................................................................................................................................................

MC736 - NB_TCH_DROP_EST_PHAS_RLF_TRX
Descripton

Long Name NB_TCH_DROP_EST_PHAS_RLF_TRX

Definition Number of non-AMR TCH (in HR or FR usage) drops 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 For TCH using non-AMR codecs:


1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "radio link
failure" is received on Abis interface for a TCH channel (after successful seizure).
2) Whenever a 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 Overview measurements

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

Feature Name B7.1 counters improvements

MC739 - NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX
Descripton

Long Name NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX


Definition Number of TCH (in HR or FR usage) drops due to 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. Whether A User plane Interface over IP AUPoIP applies to
the call, in case of normal assignment or directed retry cases, the BSC considers a TCH connection as
"established" only once first DL RTP has been received from MGW.
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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-17
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC739 - NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX
Established Phase
....................................................................................................................................................................................................................................

Sub Domain 2 TCH

Sub Domain 3 Failure


Measured Object TRX

Type Name Overview measurements


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

External Comment --
Feature Name B7.1 counters improvements

MC993 - NB_AMR_TCH_DROP_RLF_TRX
Descripton

Long Name NB_AMR_TCH_DROP_RLF_TRX


Definition Number of AMR TCH (NB or WB AMR) for which Repeated SACCH is not activated, dropped in
established TCH phase due to radio link failure (radio link timeout or Lapdm timer expiry), per TRX.
Trigger condition For TCH using AMR codecs (NB or WB) but for which the feature Repeated SACCH is not activated by the
BSC:
1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "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 and leads to a loss of
call.
Sub Domain 1 Established Phase

Sub Domain 2 TCH


Sub Domain 3 --
Measured Object TRX
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name AMR signaling improvements (Repeated S/FACCH)

....................................................................................................................................................................................................................................
47-18 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC994 - NB_AMR_TCH_DROP_RLF_TRX_RSACCH
Established Phase
....................................................................................................................................................................................................................................

MC994 - NB_AMR_TCH_DROP_RLF_TRX_RSACCH
Descripton

Long Name NB_AMR_TCH_DROP_RLF_TRX_RSACCH

Definition Number of AMR TCH (NB or WB AMR) for which Repeated SACCH is activated, dropped in established
TCH phase due to radio link failure (radio link timeout or Lapdm timer expiry), per TRX. This counter takes
into account TCH in traffic.
Trigger condition For TCH using AMR codecs (NB or WB) but for which the feature Repeated SACCH is activated by the
BSC:
1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "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 and leads to a loss of
call.
Sub Domain 1 Established Phase
Sub Domain 2 TCH

Sub Domain 3 --
Measured Object TRX

Type Name Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name AMR signaling improvements (Repeated S/FACCH)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-19
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Handover
....................................................................................................................................................................................................................................

Handover

Overview
Purpose
This section contains Handover parameters.

Contents

MC03 - NB_OUT_SDCCH_HO_SUCC 47-21


MC07 - NB_SDCCH_DROP_OUT_HO 47-21
MC10 - NB_INC_SDCCH_HO_SUCC 47-22
MC14a - NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB 47-22
MC1612 - OLC_NB_TCH_DROP_OUT_HO_EXEC_TRX 47-24
MC621 - NB_TCH_DROP_OUT_HO_EXEC_TRX 47-25
MC711 - NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX 47-25
MC712 - NB_TCH_OUT_HO_SUCC_TRX 47-26
MC713 - NB_TCH_OUT_HO_FAIL_REV_TRX 47-27
MC714 - NB_TCH_OUT_HO_FAIL_NO_REV_TRX 47-28
MC717b - NB_INC_TCH_HO_SUCC_TRX 47-28
MC719c - NB_INC_TCH_HO_SUCC_NON_AMR 47-29
MC719d - NB_INC_TCH_HO_SUCC_ALL_AMR 47-30
MC719e - NB_TCH_OUT_HO_SUCC_NON_AMR 47-31
MC719f - NB_TCH_OUT_HO_SUCC_ALL_AMR 47-32
MC719g - NB_INTRA_TCH_HO_SUCC_NON_AMR 47-33
MC719h - NB_INTRA_TCH_HO_SUCC_ALL_AMR 47-33
MC719i - NB_INC_IDR_SUCC_RACCH 47-34
MC719j - NB_INC_TCH_HO_SUCC_RACCH 47-35
MC719k - NB_TCH_OUT_HO_SUCC_RACCH 47-35
MC719l - NB_INTRA_TCH_HO_SUCC_RACCH 47-36
MC995 - NB_AMR_TCH_DROP_OUT_HO_TRX 47-37
MC996 - NB_AMR_TCH_DROP_OUT_HO_TRX_RFACCH 47-38

....................................................................................................................................................................................................................................
47-20 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC03 - NB_OUT_SDCCH_HO_SUCC
Handover
....................................................................................................................................................................................................................................

MC03 - NB_OUT_SDCCH_HO_SUCC
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC07 - NB_SDCCH_DROP_OUT_HO
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-21
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC10 - NB_INC_SDCCH_HO_SUCC
Handover
....................................................................................................................................................................................................................................

MC10 - NB_INC_SDCCH_HO_SUCC
Descripton

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 Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC14a - NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB
Descripton

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 are detected consecutively. In that case, the
counter will only be incremented once, as soon as the handover procedure fails.
This counter takes into account handovers from TCH in traffic or in signaling mode.

....................................................................................................................................................................................................................................
47-22 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC14a - NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB
Handover
....................................................................................................................................................................................................................................

Trigger condition 1) When the BSC receives on Abis from the target cell negative ack to the TCH channel activation involved
in the handover.
2) When the timer supervising the Channel Activation (T9103) expires on the target cell during activation of
a TCH channel involved in the handover.
3) When an 48.058 ERROR REPORT with a cause value of "O&M intervention" is received on Abis from
either the serving or the target cell during the external or internal inter-cell handover and leads to a
transaction failure.
4) When an 48.058 ERROR REPORT with a cause value of "O&M intervention" is received on Abis on
either the old or the new channel during the internal intra-cell handover and leads to a transaction failure.
5) When an 48.058 ERROR REPORT on SAPI 0 with a cause value of "message sequence error" is received
on Abis from the serving cell between the sending of the 48.058 CHANNEL ACTIVATION and the
reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGMENT during the internal inter-cell
TCH handover and leads to a transaction failure.
6) When an 48.058 ERROR REPORT on SAPI 0 with a cause value of "message sequence error" is received
on Abis interface on the old channel between the sending of the 48.058 CHANNEL ACTIVATION and the
reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGE during the internal intra-cell TCH
handover and leads to a transaction failure.
7) When 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) When an TCH handover abortion is initiated by the BSS O&M FAULT MANAGEMENT or by the BSS
TELECOM 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 or communication problems between
different processor boards).
9) When a 48.058 CONNECTION FAILURE INDICATION with a cause value of "remote transcoder
failure" is received on Abis from the old channel between the sending of the 48.058 CHANNEL
ACTIVATION and the reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGE during an
internal intra-cell or inter-cellTCH handover and leads to a transaction failure.
10) When the timer supervising the A INTERFACE CHANNEL ID toward BTS (T_aintcid) expires during
activation of a TCH channel involved in the handover performed with Iur-g support.
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 Overview measurements


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

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-23
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1612 - OLC_NB_TCH_DROP_OUT_HO_EXEC_TRX
Handover
....................................................................................................................................................................................................................................

MC1612 - OLC_NB_TCH_DROP_OUT_HO_EXEC_TRX
Descripton

Long Name OLC_NB_TCH_DROP_OUT_HO_EXEC_TRX

Definition Number of TCH drops during the execution of any TCH outgoing handover, in OLC configuration, per TRX
and per site.
This counter takes into account handovers from TCH in traffic or in signaling mode

Trigger condition For TCH using AMR and non-AMR codecs:


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.
The identification of the site (RRH) inside the One Logical Cell OLC is obtained by BSC via via RRH ID in
MEASUREMENT RESULT
Sub Domain 1 Handover

Sub Domain 2 TCH


Sub Domain 3 --
Measured Object Site_TRX
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

....................................................................................................................................................................................................................................
47-24 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC621 - NB_TCH_DROP_OUT_HO_EXEC_TRX
Handover
....................................................................................................................................................................................................................................

MC621 - NB_TCH_DROP_OUT_HO_EXEC_TRX
Descripton

Long Name NB_TCH_DROP_OUT_HO_EXEC_TRX

Definition Number of non-AMR 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 For TCH using non-AMR codecs:


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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name B7.1 counters improvements

MC711 - NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-25
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC711 - NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX
Handover
....................................................................................................................................................................................................................................

Trigger condition 1) Intracell HO: Whenever an intra-cell TCH handover in non VAMOS mode cannot be performed, because
there is no free TCH channel to allocate the handover to (In VAMOS mode when no pairing target candidate
is found, this counter is not incremented)
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 Overview measurements


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

External Comment --
Feature Name B7.1 counters improvements

MC712 - NB_TCH_OUT_HO_SUCC_TRX
Descripton

Long Name NB_TCH_OUT_HO_SUCC_TRX


Definition Nb of outgoing TCH handover successes, 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.
MC712 = C712
Trigger condition 1) External HO in the following cases:
1a) 48.008CLEAR COMMAND (cause = "handover successful") is received on the serving BSC on the
TCH channel.
1b) 48.008 CLEAR COMMAND (cause = "normal event/call control") is 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

....................................................................................................................................................................................................................................
47-26 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC712 - NB_TCH_OUT_HO_SUCC_TRX
Handover
....................................................................................................................................................................................................................................

Measured Object TRX

Type Name Overview measurements


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

External Comment --
Feature Name B7.1 counters improvements

MC713 - NB_TCH_OUT_HO_FAIL_REV_TRX
Descripton

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 handovers from TCH in traffic or in signaling mode. It does not take into account DTM
Assignments.
MC713 = C713
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 Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-27
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC714 - NB_TCH_OUT_HO_FAIL_NO_REV_TRX
Handover
....................................................................................................................................................................................................................................

MC714 - NB_TCH_OUT_HO_FAIL_NO_REV_TRX
Descripton

Long Name NB_TCH_OUT_HO_FAIL_NO_REV_TRX

Definition Nb of outgoing TCH handover -execution failures due to MS access problem 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 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.
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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name B7.1 counters improvements

MC717b - NB_INC_TCH_HO_SUCC_TRX
Descripton

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

....................................................................................................................................................................................................................................
47-28 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC717b - NB_INC_TCH_HO_SUCC_TRX
Handover
....................................................................................................................................................................................................................................

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 Overview measurements


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

External Comment --
Feature Name B7.1 counters improvements

MC719c - NB_INC_TCH_HO_SUCC_NON_AMR
Descripton

Long Name NB_INC_TCH_HO_SUCC_NON_AMR


Definition Number of incoming internal and external TCH (in HR or FR usage) handover successes for speech calls
which has been established with non-AMR codec types (GSM FR/HR or EFR).
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 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.
only for a speech call established with a non-AMR codec type. 48.008 ASSIGNMENT COMPLETE is
considered for speech version discrimination.
This counter is triggered only when 48.008 ASSIGNMENT COMPLETE was sent from BSC to MSC on A
interface for a TCH channel assigned indicating the usage of speech version 1 (FR or HR channel type) or
speech version 2 (EFR channel type)

Sub Domain 1 Handover


Sub Domain 2 TCH

Sub Domain 3 --

Measured Object Common cell


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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-29
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC719c - NB_INC_TCH_HO_SUCC_NON_AMR
Handover
....................................................................................................................................................................................................................................

External Comment --

Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

MC719d - NB_INC_TCH_HO_SUCC_ALL_AMR
Descripton

Long Name NB_INC_TCH_HO_SUCC_ALL_AMR

Definition Number of incoming internal and external TCH (in HR or FR usage) handover successes for speech calls
which has been established with an AMR codec types (AMR or AMR-WB).
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 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.
only for a speech call established with an AMR codec type. 48.008 ASSIGNMENT COMPLETE is
considered for speech version discrimination.
This counter is triggered only when 48.008 ASSIGNMENT COMPLETE was sent from BSC to MSC on A
interface for a TCH channel assigned indicating the usage of speech version 3 (AMR-FR and AMR-HR) or
speech version 5 (AMR-WB channel type)

Sub Domain 1 Handover


Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

....................................................................................................................................................................................................................................
47-30 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC719e - NB_TCH_OUT_HO_SUCC_NON_AMR
Handover
....................................................................................................................................................................................................................................

MC719e - NB_TCH_OUT_HO_SUCC_NON_AMR
Descripton

Long Name NB_TCH_OUT_HO_SUCC_NON_AMR

Definition Nb of outgoing TCH handover successes for speech calls which has been established with non-AMR codec
types (GSM FR/HR or EFR).
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.

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.
only for a speech call established with a non-AMR codec type. 48.008 ASSIGNMENT COMPLETE is
considered for speech version discrimination.
This counter is triggered only when 48.008 ASSIGNMENT COMPLETE was sent from BSC to MSC on A
interface for a TCH channel assigned indicating the usage of speech version 1 (FR or HR channel type) or
speech version 2 (EFR channel type)
Sub Domain 1 Handover
Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-31
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC719f - NB_TCH_OUT_HO_SUCC_ALL_AMR
Handover
....................................................................................................................................................................................................................................

MC719f - NB_TCH_OUT_HO_SUCC_ALL_AMR
Descripton

Long Name NB_TCH_OUT_HO_SUCC_ALL_AMR

Definition Nb of outgoing TCH handover successes for speech calls which has been established with an AMR codec
types (AMR or AMR-WB).
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.

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.
only for a speech call established with an AMR codec type. 48.008 ASSIGNMENT COMPLETE is
considered for speech version discrimination.
This counter is triggered only when 48.008 ASSIGNMENT COMPLETE was sent from BSC to MSC on A
interface for a TCH channel assigned indicating the usage of speech version 3 (AMR-FR and AMR-HR) or
speech version 5 (AMR-WB channel type)
Sub Domain 1 Handover
Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

....................................................................................................................................................................................................................................
47-32 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC719g - NB_INTRA_TCH_HO_SUCC_NON_AMR
Handover
....................................................................................................................................................................................................................................

MC719g - NB_INTRA_TCH_HO_SUCC_NON_AMR
Descripton

Long Name NB_INTRA_TCH_HO_SUCC_NON_AMR

Definition Number of intra-cell TCH (in HR or FR usage) handover successes for speech calls which has been
established with non-AMR codec types (GSM FR/HR or EFR).
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 44.018 ASSIGNMENT COMPLETE message is received on Abis interface on the target
channel
for a TCH channel that is involved in an internal intra-cell TCH handover for a call established with a
non-AMR codec type.
48.008 ASSIGNMENT COMPLETE is considered for speech version discrimination.
This counter is triggered only when 48.008 ASSIGNMENT COMPLETE was sent from BSC to MSC on A
interface for a TCH channel assigned indicating the usage of speech version 1 (FR or HR channel type) or
speech version 2 (EFR channel type)

Sub Domain 1 Handover


Sub Domain 2 TCH
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

MC719h - NB_INTRA_TCH_HO_SUCC_ALL_AMR
Descripton

Long Name NB_INTRA_TCH_HO_SUCC_ALL_AMR

Definition Number of intra-cell TCH (in HR or FR usage) handover successes for speech calls which has been
established with an AMR codec types (AMR or AMR-WB).
This counter takes into account handovers from TCH in traffic or in signaling mode. It does not take into
account DTM Assignments.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-33
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC719h - NB_INTRA_TCH_HO_SUCC_ALL_AMR
Handover
....................................................................................................................................................................................................................................

Trigger condition Whenever a 44.018 ASSIGNMENT COMPLETE message is received on Abis interface on the target
channel
for a TCH channel that is involved in an internal intra-cell TCH handover for a call established with an
AMR codec type.
48.008 ASSIGNMENT COMPLETE is considered for speech version discrimination.
This counter is triggered only when 48.008 ASSIGNMENT COMPLETE was sent from BSC to MSC on A
interface for a TCH channel assigned indicating the usage of speech version 3 (AMR-FR and AMR-HR) or
speech version 5 (AMR-WB channel type)
Sub Domain 1 Handover

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

MC719i - NB_INC_IDR_SUCC_RACCH
Descripton

Long Name NB_INC_IDR_SUCC_RACCH


Definition Number of incoming directed retry (towards a TCH channel in HR or FR usage) successes for speech AMR
calls with repeated ACCH feature activated.
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 for speech AMR calls whose Abis messages
Channel activation or Mode Modify indicates the activation of RSACCH and/or RDFACCH in the IE
repeated ACCH activation.
Sub Domain 1 Handover
Sub Domain 2 TCH

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

....................................................................................................................................................................................................................................
47-34 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC719j - NB_INC_TCH_HO_SUCC_RACCH
Handover
....................................................................................................................................................................................................................................

MC719j - NB_INC_TCH_HO_SUCC_RACCH
Descripton

Long Name NB_INC_TCH_HO_SUCC_RACCH

Definition Number of incoming internal and external TCH (in HR or FR usage) handover successes for speech AMR
calls with repeated ACCH feature activated.
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 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.
only for speech AMR calls whose Abis messages Channel activation or Mode Modify indicates the
activation of RSACCH and/or RDFACCH in the IE repeated ACCH activation.
Sub Domain 1 Handover

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

MC719k - NB_TCH_OUT_HO_SUCC_RACCH
Descripton

Long Name NB_TCH_OUT_HO_SUCC_RACCH

Definition Nb of outgoing TCH handover successes for speech AMR calls with repeated ACCH feature activated.
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.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-35
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC719k - NB_TCH_OUT_HO_SUCC_RACCH
Handover
....................................................................................................................................................................................................................................

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.
only for speech AMR calls whose Abis messages Channel activation or Mode Modify indicates the
activation of RSACCH and/or RDFACCH in the IE repeated ACCH activation.
Sub Domain 1 Handover

Sub Domain 2 TCH


Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

MC719l - NB_INTRA_TCH_HO_SUCC_RACCH
Descripton

Long Name NB_INTRA_TCH_HO_SUCC_RACCH


Definition Number of intra-cell TCH (in HR or FR usage) handover successes for speech AMR calls with repeated
ACCH feature activated.
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 44.018 ASSIGNMENT COMPLETE message is received on Abis interface on the target
channel
for a TCH channel that is involved in an internal intra-cell TCH handover only for speech AMR calls whose
Abis messages Channel activation or Mode Modify indicates the activation of RSACCH and/or RDFACCH
in the IE repeated ACCH activation.
Sub Domain 1 Handover

Sub Domain 2 TCH

Sub Domain 3 --

....................................................................................................................................................................................................................................
47-36 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC719l - NB_INTRA_TCH_HO_SUCC_RACCH
Handover
....................................................................................................................................................................................................................................

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

MC995 - NB_AMR_TCH_DROP_OUT_HO_TRX
Descripton

Long Name NB_AMR_TCH_DROP_OUT_HO_TRX


Definition Number of TCH using AMR codecs (NB or WB) but with Repeated FACCH not activated, dropped during
the execution of any TCH outgoing handover, per TRX. This counter takes into account handovers from
TCH in traffic.
Trigger condition For TCH using AMR codecs (NB or WB) but for which the feature Repeated FACCH is not activated by the
BSC:
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 --

Measured Object TRX


Type Name Overview measurements

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

External Comment --
Feature Name AMR signaling improvements (Repeated S/FACCH)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-37
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC996 - NB_AMR_TCH_DROP_OUT_HO_TRX_RFACCH
Handover
....................................................................................................................................................................................................................................

MC996 - NB_AMR_TCH_DROP_OUT_HO_TRX_RFACCH
Descripton

Long Name NB_AMR_TCH_DROP_OUT_HO_TRX_RFACCH

Definition Number of TCH using AMR codecs (NB or WB) and with Repeated FACCH activated, dropped during the
execution of any TCH outgoing handover, per TRX. This counter takes into account handovers from TCH in
traffic or in signaling mode.
Trigger condition For TCH using AMR codecs (NB or WB) but for which the feature Repeated FACCH is activated by the
BSC:
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 --
Measured Object TRX
Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name AMR signaling improvements (Repeated S/FACCH)

....................................................................................................................................................................................................................................
47-38 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Interface (QoS)
....................................................................................................................................................................................................................................

Interface (QoS)

Overview
Purpose
This section contains Interface (QoS) parameters.

Contents

AIP11 - NB_BSC_RCVD_DL_RTP_PACKETS_OUT_OF_DELAY 47-40


AIP12 - NB_BSC_NOT_RCVD_DL_RTP_PACKETS 47-40
AIP50 - NB_SSRC_COLLISIONS 47-41
MC1113a - NB_N7_CON_EST_FAIL_DUE_NSS_Asig_IP 47-41
MC1113b - NB_N7_CON_EST_FAIL_DUE_BSS_Asig_IP 47-42
MC1204 - NB_TIMES_MSC_SELECTION_NRI 47-42
MC1205 - NB_TIMES_MSC_SELECTION_IMSI 47-43
MC1206 - NB_TIMES_MSC_SELECTION_LB 47-43
MC1207 - NB_TIMES_MSC_SELECTION_STORED 47-44
MC1307 - NB_ENH_RELOC_REQ_IURG 47-44
MC1308 - NB_ENH_RELOC_RESP_IURG 47-45
MC1309 - NB_ENH_RELOC_FAIL_IURG 47-45
MC182 - NB_N7_CLEAR_REQ_EST_PHAS 47-46
MC182a - NB_N7_CLEAR_REQ_EST_PHAS_CELL 47-47

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-39
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service AIP11 - NB_BSC_RCVD_DL_RTP_PACKETS_OUT_OF_DELAY
Interface (QoS)
....................................................................................................................................................................................................................................

AIP11 - NB_BSC_RCVD_DL_RTP_PACKETS_OUT_OF_DELAY
Descripton

Long Name NB_BSC_RCVD_DL_RTP_PACKETS_OUT_OF_DELAY

Definition Counts the number of DL RTP packets received out of delay by the BSC from a given MGW IP@. Shall
take into account RTP packets coming from both multiplexed and non-multiplexed RTP streams.
Trigger condition Each time the BSC detects that the RTP packet is received ot of delay, this counter is increased by 1

Sub Domain 1 Interface (QoS)


Sub Domain 2 A User Plane over IP (QoS)

Sub Domain 3 --
Measured Object MGW_IP@

Type Name Overview measurements


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

Feature Name AUPoIP A interface user plane over IP

AIP12 - NB_BSC_NOT_RCVD_DL_RTP_PACKETS
Descripton

Long Name NB_BSC_NOT_RCVD_DL_RTP_PACKETS


Definition Counts the number of lost DL RTP packets, i.e. not received by the BSC from a given MGW IP@. Shall
take into account RTP packets coming from both multiplexed and non-multiplexed RTP streams.
Trigger condition Each time the BSC detects that the RTP packet is missing, this counter is increased by 1
Sub Domain 1 Interface (QoS)

Sub Domain 2 A User Plane over IP (QoS)


Sub Domain 3 --

Measured Object MGW_IP@

Type Name Overview measurements


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

External Comment --
Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
47-40 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service AIP50 - NB_SSRC_COLLISIONS
Interface (QoS)
....................................................................................................................................................................................................................................

AIP50 - NB_SSRC_COLLISIONS
Descripton

Long Name NB_SSRC_COLLISIONS

Definition Counts the number of SSRC collisions detected by the BSC on the received RTP streams from a given
MGW IP@
Trigger condition This counter is increased by one each time the BSC receives an RTP packet with an SSRC having the same
value as the SSRC used by the BSC

Sub Domain 1 Interface (QoS)


Sub Domain 2 A User Plane over IP (QoS)

Sub Domain 3 --

Measured Object MGW_IP@


Type Name Overview measurements

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

Feature Name AUPoIP A interface user plane over IP

MC1113a - NB_N7_CON_EST_FAIL_DUE_NSS_Asig_IP
Descripton

Long Name NB_N7_CON_EST_FAIL_DUE_NSS_Asig_IP


Definition Number of BSS originating SCCP connection failures due to the NSS, when A signaling over IP is used.
Trigger condition When A signaling over IP is used :
1) CONNECTION REFUSED is received.
2) RLSD (request to release one SCCP connection) 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 (QoS)


Sub Domain 2 A signaling over IP (QoS)

Sub Domain 3 --
Measured Object MSC_BSC

Type Name Overview measurements

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

Feature Name A signaling over IP

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-41
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1113b - NB_N7_CON_EST_FAIL_DUE_BSS_Asig_IP
Interface (QoS)
....................................................................................................................................................................................................................................

MC1113b - NB_N7_CON_EST_FAIL_DUE_BSS_Asig_IP
Descripton

Long Name NB_N7_CON_EST_FAIL_DUE_BSS_Asig_IP

Definition Number of BSS originating SCCP connection failures due to the BSS, when A signaling over IP is used.
Trigger condition When A signaling over IP is used, number of N_DISC_REQ received from BSSAP for a connection that
was not established yet (i.e BSSAP requests SCCP to stop the establishment of one SCCP connection).

Sub Domain 1 Interface (QoS)


Sub Domain 2 A signaling over IP (QoS)

Sub Domain 3 --
Measured Object MSC_BSC

Type Name Overview measurements


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

Feature Name A signaling over IP

MC1204 - NB_TIMES_MSC_SELECTION_NRI
Descripton

Long Name NB_TIMES_MSC_SELECTION_NRI


Definition Number of times the MSC is selected by deriving the NRI from the TMSI included in the Layer 3 message
received from the MS
Trigger condition Whenever a 44.018 PAGING RESPONSE, 24.008 LOCATION UPDATING REQUEST, 24.008 IMSI
DETACH INDICATION, 24.008 CM SERVICE REQUEST or 24.008 CM Re-Establishment Request is
forwarded to the MSC and the MSC is selected by using the NRI derived from the TMSI included in
"Mobile Identity" MIE of those messages.
Sub Domain 1 Interface (QoS)

Sub Domain 2 A

Sub Domain 3 --
Measured Object MSC_BSC

Type Name Overview measurements


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

External Comment --
Feature Name A-Flex

....................................................................................................................................................................................................................................
47-42 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1205 - NB_TIMES_MSC_SELECTION_IMSI
Interface (QoS)
....................................................................................................................................................................................................................................

MC1205 - NB_TIMES_MSC_SELECTION_IMSI
Descripton

Long Name NB_TIMES_MSC_SELECTION_IMSI

Definition Number of times the MSC is selected by the IMSI included in the 44.018 PAGING RESPONSE received
from the MS
Trigger condition Whenever a 44.018 PAGING RESPONSE is forwarded to the MSC and the MSC is selected by using the
IMSI included in "Mobile Identity" MIE of that message.

Sub Domain 1 Interface (QoS)


Sub Domain 2 A

Sub Domain 3 --

Measured Object MSC_BSC


Type Name Overview measurements

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

Feature Name A-Flex

MC1206 - NB_TIMES_MSC_SELECTION_LB
Descripton

Long Name NB_TIMES_MSC_SELECTION_LB


Definition Number of times the MSC is selected by the load balancing algorithm
Trigger condition Whenever a 24.008 LOCATION UPDATING REQUEST, 24.008 IMSI DETACH INDICATION, 24.008
CM SERVICE REQUEST or 24.008 CM Re-Establishment Request is forwarded to the MSC and the MSC
is selected by using the load balancing algorithm. Cases are:
- "Mobile Identity" MIE does not contain neither TMSI nor IMSI;
- the "NULL NRI" has been derived from TMSI;
- MSC cannot be found neither from IMSI nor from NRI derived fromTMSI, or it is not available.
Sub Domain 1 Interface (QoS)

Sub Domain 2 A
Sub Domain 3 --

Measured Object MSC_BSC


Type Name Overview measurements

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

External Comment --
Feature Name A-Flex

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-43
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1207 - NB_TIMES_MSC_SELECTION_STORED
Interface (QoS)
....................................................................................................................................................................................................................................

MC1207 - NB_TIMES_MSC_SELECTION_STORED
Descripton

Long Name NB_TIMES_MSC_SELECTION_STORED

Definition Number of times the MSC is selected by using the stored MSC identity
Trigger condition Whenever a 44.018 PAGING RESPONSE is forwarded to the MSC and the MSC is selected by using the
MSC identity stored when the PAGING REQUEST was received. This case occurs when the Paging
Request was received with TMSI and wrong NRI (i.e. TMSI having NRI equal to NULL NRI or NRI not
mapped to any MSC). Note: Load Balancing Mechanism cannot be performed in this case (Mobile
Terminating Call) as for MT call Paging Response should go to same MSC that has sent Paging Request

Sub Domain 1 Interface (QoS)


Sub Domain 2 A

Sub Domain 3 --
Measured Object MSC_BSC
Type Name Overview measurements

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

Feature Name A-Flex

MC1307 - NB_ENH_RELOC_REQ_IURG
Descripton

Long Name NB_ENH_RELOC_REQ_IURG


Definition Number of ENHANCED RELOCATION RESOURCE REQUEST received from the RNC by the BSC,
when Iur-g interface is used

Trigger condition Whenever a ENHANCED RELOCATION RESOURCE REQUEST message is received by the BSC from
the RNC, when Iur-g interface is used
Sub Domain 1 Interface (QoS)

Sub Domain 2 Iur-g (QoS)


Sub Domain 3 --

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name Iur-g

....................................................................................................................................................................................................................................
47-44 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1308 - NB_ENH_RELOC_RESP_IURG
Interface (QoS)
....................................................................................................................................................................................................................................

MC1308 - NB_ENH_RELOC_RESP_IURG
Descripton

Long Name NB_ENH_RELOC_RESP_IURG

Definition Number of ENHANCED RELOCATION RESOURCE RESPONSE sent to the RNC by the BSC, when
Iur-g interface is used.
Trigger condition Whenever a ENHANCED RELOCATION RESOURCE RESPONSE message is sent by the BSC to the
RNC, when Iur-g interface is used.

Sub Domain 1 Interface (QoS)


Sub Domain 2 Iur-g (QoS)

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

Feature Name Iur-g

MC1309 - NB_ENH_RELOC_FAIL_IURG
Descripton

Long Name NB_ENH_RELOC_FAIL_IURG


Definition Number of ENHANCED RELOCATION RESOURCE FAILURE sent to the RNC by the BSC, when Iur-g
interface is used.
Trigger condition Whenever a ENHANCED RELOCATION RESOURCE FAILURE message is sent by the BSC to the RNC,
when Iur-g interface is used.

Sub Domain 1 Interface (QoS)

Sub Domain 2 Iur-g (QoS)


Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements

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

Feature Name Iur-g

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-45
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC182 - NB_N7_CLEAR_REQ_EST_PHAS
Interface (QoS)
....................................................................................................................................................................................................................................

MC182 - NB_N7_CLEAR_REQ_EST_PHAS
Descripton

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.
C182=MC182
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 (QoS)


Sub Domain 2 A

Sub Domain 3 BSSAP


Measured Object BSC
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name Circuit Switched telecom improvements

....................................................................................................................................................................................................................................
47-46 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC182a - NB_N7_CLEAR_REQ_EST_PHAS_CELL
Interface (QoS)
....................................................................................................................................................................................................................................

MC182a - NB_N7_CLEAR_REQ_EST_PHAS_CELL
Descripton

Long Name NB_N7_CLEAR_REQ_EST_PHAS_CELL

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.
This counter is similar to MC182 but at cell level instead of being global (BSC level).
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 (QoS)


Sub Domain 2 A
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-47
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
LCS
....................................................................................................................................................................................................................................

LCS

Overview
Purpose
This section contains LCS parameters.

Contents

MC923a - NB_LCS_REQ 47-49


MC923b - NB_LCS_SUCC 47-49
MC923c - NB_LCS_FAIL_LB 47-50
MC923d - NB_LCS_ABORT 47-50
MC923e - NB_LCS_REQ_EM_LI 47-51
MC923f - NB_LCS_REQ_PLMN 47-51
MC923g - NB_LCS_REQ_VADD 47-52
MC923h - NB_LCS_REQ_POS_ESTIMATE 47-52
MC942 - NB_LCS_RESET_TX 47-53
MC943 - NB_LCS_RESET_RX 47-53
MC946a - NB_LCS_COI_MS_POSITION_CMD_RX 47-54
MC946b - NB_LCS_COI_MS_POSITION_RESP_TX 47-54
MC946c - NB_LCS_COI__ABORT_TX 47-55
MC946d - NB_LCS_COI_REJECT_TX 47-55
MC946e - NB_LCS_LOC_ABORT_TIMEOUT_TX 47-56
MC946f - NB_LCS_INTERRUPTED_INTRA_BSC_HO_TX 47-56
MC946g - NB_LCS_INTERRUPTED_INTER_BSC_HO_TX 47-57
MC946h - NB_LCS_TA_REQUEST_RX 47-57
MC965 - NB_LCS_INTERRUPTED_INTRA_BSC_HO 47-58
MC966 - NB_LCS_INTERRUPTED_INTER_BSC_HO 47-58

....................................................................................................................................................................................................................................
47-48 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC923a - NB_LCS_REQ
LCS
....................................................................................................................................................................................................................................

MC923a - NB_LCS_REQ
Descripton

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 A

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

Feature Name Location services (LCS)

MC923b - NB_LCS_SUCC
Descripton

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 A

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-49
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC923c - NB_LCS_FAIL_LB
LCS
....................................................................................................................................................................................................................................

MC923c - NB_LCS_FAIL_LB
Descripton

Long Name NB_LCS_FAIL_LB

Definition Number of LCS requests rejected by the BSS or the SMLC. The failed LCS requests encompass the failure
to determine geographic location estimate and the failure of LCS assistance data delivery.
Trigger condition Whenever a 48.008 PERFORM LOCATION RESPONSE message is sent to the MSC with the OIE LCS
Cause.

Sub Domain 1 LCS


Sub Domain 2 A

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

Feature Name Location services (LCS)

MC923d - NB_LCS_ABORT
Descripton

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 A

Sub Domain 3 --

Measured Object Common cell


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

External Comment --

Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
47-50 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC923e - NB_LCS_REQ_EM_LI
LCS
....................................................................................................................................................................................................................................

MC923e - NB_LCS_REQ_EM_LI
Descripton

Long Name NB_LCS_REQ_EM_LI

Definition Number of LCS requests received from the MSC in CS domain for Lawful Intercept services or Emergency
services
Trigger condition Whenever a 48.008 PERFORM LOCATION REQUEST message is received by the BSC from the MSC
with Client category of LCS client type parameter set to Lawful Intercept services or Emergency services

Sub Domain 1 LCS


Sub Domain 2 A

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

Feature Name LCS GPS support

MC923f - NB_LCS_REQ_PLMN
Descripton

Long Name NB_LCS_REQ_PLMN


Definition Number of LCS requests received from the MSC in CS domain for PLMN operator services
Trigger condition Whenever a 48.008 PERFORM LOCATION REQUEST message is received by the BSC from the MSC
with Client category of LCS client type parameter set to PLMN operator

Sub Domain 1 LCS


Sub Domain 2 A

Sub Domain 3 --

Measured Object Common cell


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

External Comment --

Feature Name LCS GPS support

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-51
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC923g - NB_LCS_REQ_VADD
LCS
....................................................................................................................................................................................................................................

MC923g - NB_LCS_REQ_VADD
Descripton

Long Name NB_LCS_REQ_VADD

Definition Number of LCS requests received from the MSC in CS domain for value added services
Trigger condition Whenever a 48.008 PERFORM LOCATION REQUEST message is received by the BSC from the MSC
with Client category of LCS client type parameter set to value added client

Sub Domain 1 LCS


Sub Domain 2 A

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

Feature Name LCS GPS support

MC923h - NB_LCS_REQ_POS_ESTIMATE
Descripton

Long Name NB_LCS_REQ_POS_ESTIMATE


Definition Number of LCS requests received from the MSC in CS domain with location information set to current
geographic location
Trigger condition Whenever a 48.008 PERFORM LOCATION REQUEST message is received by the BSC from the MSC
with location information of Location type parameter set to current geographic location
Sub Domain 1 LCS

Sub Domain 2 A

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name LCS GPS support

....................................................................................................................................................................................................................................
47-52 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC942 - NB_LCS_RESET_TX
LCS
....................................................................................................................................................................................................................................

MC942 - NB_LCS_RESET_TX
Descripton

Long Name NB_LCS_RESET_TX

Definition Number of BSSMAP-LE RESET sent to the SMLC.


Trigger condition Whenever a BSSMAP-LE RESET message is sent to the SMLC.

Sub Domain 1 LCS


Sub Domain 2 Lb

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 --
Feature Name Lb interface

MC943 - NB_LCS_RESET_RX
Descripton

Long Name NB_LCS_RESET_RX


Definition Number of BSSMAP-LE RESET received from the SMLC.
Trigger condition Whenever a BSSMAP-LE RESET message is received from the SMLC.
Sub Domain 1 LCS
Sub Domain 2 Lb

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

Feature Name Lb interface

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-53
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC946a - NB_LCS_COI_MS_POSITION_CMD_RX
LCS
....................................................................................................................................................................................................................................

MC946a - NB_LCS_COI_MS_POSITION_CMD_RX
Descripton

Long Name NB_LCS_COI_MS_POSITION_CMD_RX

Definition Number of BSSAP-LE MS POSITION CMD received from the SMLC


Trigger condition Whenever a 49.031 CONNECTION ORIENTED INFORMATION (48.071 MS POSITION COMMAND)
message is received from the SMLC

Sub Domain 1 LCS


Sub Domain 2 Lb

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

Feature Name LCS GPS support

MC946b - NB_LCS_COI_MS_POSITION_RESP_TX
Descripton

Long Name NB_LCS_COI_MS_POSITION_RESP_TX


Definition Number of BSSAP-LE MS POSITION RESP sent to the SMLC
Trigger condition Whenever a 49.031 CONNECTION ORIENTED INFORMATION (48.071 MS POSITION RESPONSE)
message is sent to the SMLC
Sub Domain 1 LCS

Sub Domain 2 Lb
Sub Domain 3 --

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name LCS GPS support

....................................................................................................................................................................................................................................
47-54 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC946c - NB_LCS_COI__ABORT_TX
LCS
....................................................................................................................................................................................................................................

MC946c - NB_LCS_COI__ABORT_TX
Descripton

Long Name NB_LCS_COI__ABORT_TX

Definition Number of BSSAP-LE ABORT sent to the SMLC


Trigger condition Whenever a 49.031 CONNECTION ORIENTED INFORMATION (48.071 ABORT) message is sent to the
SMLC

Sub Domain 1 LCS


Sub Domain 2 Lb

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

Feature Name LCS GPS support

MC946d - NB_LCS_COI_REJECT_TX
Descripton

Long Name NB_LCS_COI_REJECT_TX


Definition Number of BSSAP-LE REJECT sent to the SMLC with cause set to congestion
Trigger condition Whenever a 49.031 CONNECTION ORIENTED INFORMATION (48.071 REJECT cause congestion)
message is sent to the SMLC
Sub Domain 1 LCS

Sub Domain 2 Lb
Sub Domain 3 --

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name LCS GPS support

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-55
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC946e - NB_LCS_LOC_ABORT_TIMEOUT_TX
LCS
....................................................................................................................................................................................................................................

MC946e - NB_LCS_LOC_ABORT_TIMEOUT_TX
Descripton

Long Name NB_LCS_LOC_ABORT_TIMEOUT_TX

Definition Number of LOCATION ABORT sent to SMLC due to T_Location_Longer_LB expiry


Trigger condition Whenever on T_Location_Longer_LB expiry, BSC sends a 49.031 PERFORM LOCATION ABORT (cause
Location request aborted) to the SMLC. Whenever on T_Location_Longer_LB expiry BSC sends a 49.031
CONNECTION ORIENTED INFORMATION (48.071 ABORT) message to the SMLC

Sub Domain 1 LCS


Sub Domain 2 Lb

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

Feature Name LCS GPS support

MC946f - NB_LCS_INTERRUPTED_INTRA_BSC_HO_TX
Descripton

Long Name NB_LCS_INTERRUPTED_INTRA_BSC_HO_TX


Definition Number of failed LCS procedures on Lb interface due to intra-BSC handover
Trigger condition Whenever the BSC sends to the SMLC 49.031 PERFORM LOCATION ABORT with LCS cause setting to
�Intra-BSC HO Complete�" or when it sends either a 49.031 CONNECTION ORIENTED
INFORMATION (48.071 RESET) or a 49.031 CONNECTION ORIENTED INFORMATION (48.071
ABORT) with cause "intra-BSS hand-over".

Sub Domain 1 LCS


Sub Domain 2 Lb

Sub Domain 3 --

Measured Object Common cell


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

External Comment --

Feature Name LCS GPS support

....................................................................................................................................................................................................................................
47-56 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC946g - NB_LCS_INTERRUPTED_INTER_BSC_HO_TX
LCS
....................................................................................................................................................................................................................................

MC946g - NB_LCS_INTERRUPTED_INTER_BSC_HO_TX
Descripton

Long Name NB_LCS_INTERRUPTED_INTER_BSC_HO_TX

Definition Number of failed LCS procedures on Lb interface due to inter-BSC handover


Trigger condition Whenever the BSC sends to the SMLC 49.031 PERFORM LOCATION ABORT with LCS cause set to

Sub Domain 1 LCS

Sub Domain 2 Lb
Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name LCS GPS support

MC946h - NB_LCS_TA_REQUEST_RX
Descripton

Long Name NB_LCS_TA_REQUEST_RX


Definition Number of TA REQUEST received from the SMLC
Trigger condition Whenever a 49.031 CONNECTION ORIENTED INFORMATION (48.071 TA REQUEST) message is
received from the SMLC

Sub Domain 1 LCS


Sub Domain 2 --

Sub Domain 3 --

Measured Object Common cell


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

External Comment --

Feature Name LCS GPS support

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-57
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC965 - NB_LCS_INTERRUPTED_INTRA_BSC_HO
LCS
....................................................................................................................................................................................................................................

MC965 - NB_LCS_INTERRUPTED_INTRA_BSC_HO
Descripton

Long Name NB_LCS_INTERRUPTED_INTRA_BSC_HO

Definition Number of failed LCS procedures due to intra-BSC handover


Trigger condition Whenever the BSC sends to the MSC 48.008 PERFORM LOCATION RESPONSE with LCS cause setting
to �Intra-BSC HO Complete�

Sub Domain 1 LCS


Sub Domain 2 A

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

Feature Name Lb interface

MC966 - NB_LCS_INTERRUPTED_INTER_BSC_HO
Descripton

Long Name NB_LCS_INTERRUPTED_INTER_BSC_HO


Definition Number of failed LCS procedures due to inter-BSC handover
Trigger condition Whenever the BSC sends to the MSC 48.008 PERFORM LOCATION RESPONSE with LCS cause set to
�Inter-BSC HO Ongoing�
Sub Domain 1 LCS

Sub Domain 2 A
Sub Domain 3 --

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name Lb interface

....................................................................................................................................................................................................................................
47-58 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Repeated ACCH
....................................................................................................................................................................................................................................

Repeated ACCH

Overview
Purpose
This section contains Repeated ACCH parameters.

Contents

MC718g - NB_TCH_REP_FACCH_ASS_COMP 47-59


MC718h - NB_TCH_REP_SACCH_ASS_COMP 47-60
MC990 - NB_MS_REPEATED_ACCH_CAPABLE 47-60
MC991 - NB_CALLS_RFACCH_ACTIVATED 47-61
MC992 - NB_CALLS_RSACCH_ACTIVATED 47-61

MC718g - NB_TCH_REP_FACCH_ASS_COMP
Descripton

Long Name NB_TCH_REP_FACCH_ASS_COMP


Definition Number of TCH normal assignment successes for speech calls with GSM speech versions 3 and 5 (FR
AMR, HR AMR and FR AMR-WB) with repeated DL FACCH allowed.
Trigger condition Sending of 48.008 ASSIGNMENT COMPLETE from the BSC to the MSC for a speech call with GSM
speech version 3 or 5 (FR AMR, HR AMR or FR AMR-WB) that is not involved in a handover procedure
and whose Abis messages Channel activation or Mode Modify indicated the activation of Repeated DL
FACCH in the IE Repeated ACCH Activation.

Sub Domain 1 Repeated ACCH


Sub Domain 2 --
Sub Domain 3 --

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-59
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC718h - NB_TCH_REP_SACCH_ASS_COMP
Repeated ACCH
....................................................................................................................................................................................................................................

MC718h - NB_TCH_REP_SACCH_ASS_COMP
Descripton

Long Name NB_TCH_REP_SACCH_ASS_COMP

Definition Number of TCH normal assignment successes for speech calls with GSM speech versions 3 and 5 (FR
AMR, HR AMR and FR AMR-WB) with repeated SACCH allowed.
Trigger condition Sending of 48.008 ASSIGNMENT COMPLETE from the BSC to the MSC for a speech call with GSM
speech version 3 or 5 (FR AMR, HR AMR or FR AMR-WB) that is not involved in a handover procedure
and whose Abis messages Channel activation or Mode Modify indicated the activation of Repeated SACCH
in the IE Repeated ACCH Activation.

Sub Domain 1 Repeated ACCH


Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements

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

Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

MC990 - NB_MS_REPEATED_ACCH_CAPABLE
Descripton

Long Name NB_MS_REPEATED_ACCH_CAPABLE


Definition Number of calls for which the mobile stations support the repeated ACCH capability

Trigger condition Each time the BSC gets for a call the indication of the corresponding MS Repeated ACCH Capability in the
classmark 3 IE at the time of Channel Activation or Mode modify messages sending, this counter is
incremented by one.
Sub Domain 1 Repeated ACCH

Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name Overview measurements


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

External Comment This counter is applicable only for Evolution BSC.


Feature Name AMR signaling improvements (Repeated S/FACCH)

....................................................................................................................................................................................................................................
47-60 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC991 - NB_CALLS_RFACCH_ACTIVATED
Repeated ACCH
....................................................................................................................................................................................................................................

MC991 - NB_CALLS_RFACCH_ACTIVATED
Descripton

Long Name NB_CALLS_RFACCH_ACTIVATED

Definition Number of calls for which repeated DL FACCH is allowed by the BSC
Trigger condition Each time the BSC sends a Channel Activation or a Mode Modify to a BTS indicating that RDFACCH is
activated for LAPDm command frames and/or LAPDm response frames, then this counter is incremented by
1. For Mode Modify trigger, only the cases where RDFACCH was not activated in the Channel Activation
message previously sent by the BSC are counted.

Sub Domain 1 Repeated ACCH


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment This counter is applicable only for Evolution BSC.

Feature Name AMR signaling improvements (Repeated S/FACCH)

MC992 - NB_CALLS_RSACCH_ACTIVATED
Descripton

Long Name NB_CALLS_RSACCH_ACTIVATED


Definition Number of calls for which repeated SACCH (DL or UL) is allowed by the BSC
Trigger condition Each time the BSC sends a Channel Activation or a Mode Modify to a BTS indicating that RSACCH (UL
and/or DL) is activated, then this counter is incremented by 1. For Mode Modify trigger, only the cases
where RSACCH was not activated in the Channel Activation message previously sent by the BSC are
counted

Sub Domain 1 Repeated ACCH


Sub Domain 2 --

Sub Domain 3 --

Measured Object TRX


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

External Comment This counter is applicable only for Evolution BSC.

Feature Name AMR signaling improvements (Repeated S/FACCH)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-61
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Short Message Service
....................................................................................................................................................................................................................................

Short Message Service

Overview
Purpose
This section contains Short Message Service parameters.

Contents

MC191 - NB_SMS_PP_CON_MT_SDCCH 47-62


MC196 - NB_SMS_PP_CON_SUCC 47-63
MC197 - NB_SMS_PP_CON_FAIL 47-63

MC191 - NB_SMS_PP_CON_MT_SDCCH
Descripton

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 Short Message Service

Sub Domain 2 Point to Point


Sub Domain 3 Success
Measured Object Common cell
Type Name Overview measurements

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

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
47-62 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC196 - NB_SMS_PP_CON_SUCC
Short Message Service
....................................................................................................................................................................................................................................

MC196 - NB_SMS_PP_CON_SUCC
Descripton

Long Name NB_SMS_PP_CON_SUCC

Definition MC196=C190+C191+C192+C193
Trigger condition --

Sub Domain 1 Short Message Service


Sub Domain 2 Point to Point

Sub Domain 3 Success


Measured Object Common cell

Type Name Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC197 - NB_SMS_PP_CON_FAIL
Descripton

Long Name NB_SMS_PP_CON_FAIL


Definition MC197=C194a+C194b+C194c+C195
Trigger condition --
Sub Domain 1 Short Message Service
Sub Domain 2 Point to Point

Sub Domain 3 Failure

Measured Object Common cell


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

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-63
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Speech
....................................................................................................................................................................................................................................

Speech

Overview
Purpose
This section contains Speech parameters.

Contents

MC170 - NB_CALL_TFO 47-64


MC935 - NB_CALL_TFO_AMR_WB 47-65
MC938 - NB_CALL_TFO_AMR_NB 47-65
MC939 - NB_HO_INTER_TFO_AMR_NB 47-66
MC950 - NB_HO_EXT_TFO_AMR_NB 47-67

MC170 - NB_CALL_TFO
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

....................................................................................................................................................................................................................................
47-64 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC170 - NB_CALL_TFO
Speech
....................................................................................................................................................................................................................................

Feature Name Support of TFO (Tandem Free Operation)

MC935 - NB_CALL_TFO_AMR_WB
Descripton

Long Name NB_CALL_TFO_AMR_WB

Definition Number of TCH assigned using AMR-WB 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) 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 Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Support of TFO on NB-AMR

MC938 - NB_CALL_TFO_AMR_NB
Descripton

Long Name NB_CALL_TFO_AMR_NB


Definition Number of TCH assigned using AMR-NB for which TFO has been successfully established.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-65
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC938 - NB_CALL_TFO_AMR_NB
Speech
....................................................................................................................................................................................................................................

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) and the used
codec is an AMR NB one (i.e. FR or HR sv3).
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 Overview measurements

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

Feature Name Support of TFO on NB-AMR

MC939 - NB_HO_INTER_TFO_AMR_NB
Descripton

Long Name NB_HO_INTER_TFO_AMR_NB


Definition Number of TCH assigned using AMR-NB 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 NB one (i.e. FR or HR sv3).
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 Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Support of TFO on NB-AMR

....................................................................................................................................................................................................................................
47-66 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC950 - NB_HO_EXT_TFO_AMR_NB
Speech
....................................................................................................................................................................................................................................

MC950 - NB_HO_EXT_TFO_AMR_NB
Descripton

Long Name NB_HO_EXT_TFO_AMR_NB

Definition Number of TCH assigned using AMR-NB for which TFO has been successfully 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 NB one (i.e. FR or HR sv3).
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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Support of TFO on NB-AMR

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-67
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
TCH
....................................................................................................................................................................................................................................

TCH

Overview
Purpose
This section contains TCH parameters.

Contents

MC928a - NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_UL 47-68


MC928b - NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_UL 47-69
MC928c - NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_DL 47-70
MC928d - NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_DL 47-71
MC928e - NB_TCH_DROP_CAUSE_TOO_LONG_MS_BS_DISTANCE 47-72
MC928f - NB_TCH_DROP_CAUSE_TOO_SHORT_MS_BS_DISTANCE 47-73
MC928g - NB_TCH_DROP_CAUSE_TOO_HIGH_INTERFERENCE_ 47-74
UPLINK
MC928h - NB_TCH_DROP_CAUSE_TOO_HIGH_INTERFERENCE_ 47-75
DOWNLINK
MC928i - NB_TCH_DROP_OTHER_CAUSES 47-76

MC928a - NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_UL
Descripton

Long Name NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_UL

Definition Number of TCH drops due to Cause 2 (Too low quality in UL).

....................................................................................................................................................................................................................................
47-68 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC928a - NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_UL
TCH
....................................................................................................................................................................................................................................

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 (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.
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 TCH
Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC928b - NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_UL
Descripton

Long Name NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_UL


Definition Number of TCH drops due to Cause 3 (Too low level in UL).

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-69
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC928b - NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_UL
TCH
....................................................................................................................................................................................................................................

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 (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.
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 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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name --

MC928c - NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_DL
Descripton

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

....................................................................................................................................................................................................................................
47-70 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC928c - NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_DL
TCH
....................................................................................................................................................................................................................................

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 (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.
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 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" 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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name --

MC928d - NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_DL
Descripton

Long Name NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_DL


Definition Number of TCH drops due to Cause 5 (Too low level in DL).

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-71
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC928d - NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_DL
TCH
....................................................................................................................................................................................................................................

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 (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.
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 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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name --

MC928e - NB_TCH_DROP_CAUSE_TOO_LONG_MS_BS_DISTANCE
Descripton

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

....................................................................................................................................................................................................................................
47-72 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC928e - NB_TCH_DROP_CAUSE_TOO_LONG_MS_BS_DIS-
TCH TANCE
....................................................................................................................................................................................................................................

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 (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.
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 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) 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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC928f - NB_TCH_DROP_CAUSE_TOO_SHORT_MS_BS_DISTANCE
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-73
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC928f - NB_TCH_DROP_CAUSE_TOO_SHORT_MS_BS-
TCH _DISTANCE
....................................................................................................................................................................................................................................

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 (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.
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 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) and Cause 6
(MC928e) are not eligible;
b) and the following condition is fulfilled:
AV_RANGE_HO <= L_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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name --

MC928g - NB_TCH_DROP_CAUSE_TOO_HIGH_INTER-
FERENCE_UPLINK
Descripton

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

....................................................................................................................................................................................................................................
47-74 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC928g - NB_TCH_DROP_CAUSE_TOO_HIGH_INTER-
TCH FERENCE_UPLINK
....................................................................................................................................................................................................................................

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 (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.
3) Whenever the timer supervising the handover procedure (T3107) expires 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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC928h - NB_TCH_DROP_CAUSE_TOO_HIGH_INTER-
FERENCE_DOWNLINK
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-75
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC928h - NB_TCH_DROP_CAUSE_TOO_HIGH_INTER-
TCH FERENCE_DOWNLINK
....................................................................................................................................................................................................................................

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 (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.
3) Whenever the timer supervising the handover procedure (T3107) expires 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" 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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC928i - NB_TCH_DROP_OTHER_CAUSES
Descripton

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

....................................................................................................................................................................................................................................
47-76 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC928i - NB_TCH_DROP_OTHER_CAUSES
TCH
....................................................................................................................................................................................................................................

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 (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.
3) Whenever the timer supervising the handover procedure (T3103) expires during the inter-cell TCH
handover.
4) Whenever the timer supervising the handover 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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-77
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Telecom Procedure (QoS)

Overview
Purpose
This section contains Telecom Procedure (QoS) parameters.

Contents

MC01 - NB_IMM_ASS_SUCC_MT 47-79


MC02 - NB_IMM_ASS_SUCC_MO 47-80
MC02a - NB_IMM_ASS_SUCC_MO_LOC_UPD 47-80
MC02b - NB_IMM_ASS_SUCC_MO_SMS 47-81
MC02c - NB_IMM_ASS_SUCC_MO_SUP_SERV 47-81
MC02d - NB_IMM_ASS_SUCC_MO_FOLLOW_ON 47-82
MC02e - NB_IMM_ASS_SUCC_MO_CM_REEST 47-83
MC02f - NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW 47-83
MC02g - NB_IMM_ASS_SUCC_MO_IMSI_DETACH 47-84
MC02h - NB_IMM_ASS_SUCC_MO_CALL_EST 47-84
MC02i - NB_IMM_ASS_SUCC_MO_LCS 47-85
MC04 - NB_IMM_ASS_PREP_FAIL_CONG 47-85
MC140a - NB_TCH_NOR_ASS_REQ 47-86
MC140b - NB_TCH_NOR_ASS_ATPT 47-86
MC149 - NB_IMM_ASS_EXEC_FAIL_RADIO 47-87
MC1601 - OLC_NB_IMM_ASS_EXEC_FAIL_RADIO 47-88
MC1602 - OLC_NB_TCH_NOR_ASS_SUCC_TRX 47-88
MC1603 - OLC_NB_TCH_NOR_ASS_ATPT 47-89
MC1604 - OLC_NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX 47-89
MC161 - NB_DTAP_NOR_ASS_SUCC 47-90
MC1701 - NB_REDIRECT_ATTEMPT 47-90
MC1702 - NB_REDIRECT_COMMAND 47-91
MC1703 - NB_REDIRECT_COMMAND_CS_PS_COORD 47-91
MC1704 - NB_REDIRECT_COMPLETE 47-92

....................................................................................................................................................................................................................................
47-78 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service Overview
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

MC1705 - NB_REDIRECT_COMPLETE_ MS_NOT ACCEPTED 47-92


MC1706 - NB_REDIRECT_COMPLETE_ MS_ALREADY_REG 47-93
MC19 - NB_TCH_NOR_ASS_HO_PREP_FAIL_ACHAN_MIS (110) 47-93
MC612a - NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE 47-94
MC612b - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL 47-95
MC612c - NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP 47-95
MC612d - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ 47-96
MC718 - NB_TCH_NOR_ASS_SUCC_TRX 47-97
MC746b - NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX 47-98
MC812 - NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS 47-98
MC901 - NB_Suspend_Resume_req 47-99
MC902 - Nb_Suspend_fail 47-100
MC903 - Nb_Suspend_succ 47-100
MC921a - NB_TCH_NOR_ASS_HO_REQ_ABLE_TO_PREEMPT 47-101
MC921b - NB_PREEMPT_CAP_ALLOC_SUCC 47-101
MC921c - NB_PREEMPTED_CALLS 47-102
MC921d - NB_PREEMPT_CAP_OUT_DR_ALLOC_SUCC 47-102
MC921e - NB_TCH_NOR_ASS_HO_SUCC_PREEMPTABLE 47-103
MC933 - NB_TCH_NOR_ASS_PREP_FAIL_PMIS 47-104

MC01 - NB_IMM_ASS_SUCC_MT
Descripton

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 Telecom Procedure (QoS)
Sub Domain 2 Immediate Assignment

Sub Domain 3 Success

Measured Object Common cell


Type Name Overview measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-79
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC01 - NB_IMM_ASS_SUCC_MT
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

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

External Comment --
Feature Name --

MC02 - NB_IMM_ASS_SUCC_MO
Descripton

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 Telecom Procedure (QoS)
Sub Domain 2 Immediate Assignment

Sub Domain 3 Success


Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name --

MC02a - NB_IMM_ASS_SUCC_MO_LOC_UPD
Descripton

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 Telecom Procedure (QoS)


Sub Domain 2 Immediate Assignment

Sub Domain 3 Success

....................................................................................................................................................................................................................................
47-80 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC02a - NB_IMM_ASS_SUCC_MO_LOC_UPD
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name --

MC02b - NB_IMM_ASS_SUCC_MO_SMS
Descripton

Long Name NB_IMM_ASS_SUCC_MO_SMS


Definition case: SMS procedure on SDCCH
Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from 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 "SMS".
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.
Sub Domain 1 Telecom Procedure (QoS)

Sub Domain 2 Immediate Assignment


Sub Domain 3 Success
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC02c - NB_IMM_ASS_SUCC_MO_SUP_SERV
Descripton

Long Name NB_IMM_ASS_SUCC_MO_SUP_SERV


Definition case: Supplementary Service

Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from 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 "Supplementary Service".
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.

Sub Domain 1 Telecom Procedure (QoS)

Sub Domain 2 Immediate Assignment

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-81
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC02c - NB_IMM_ASS_SUCC_MO_SUP_SERV
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Sub Domain 3 Success

Measured Object Common cell


Type Name Overview measurements

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

Feature Name --

MC02d - NB_IMM_ASS_SUCC_MO_FOLLOW_ON
Descripton

Long Name NB_IMM_ASS_SUCC_MO_FOLLOW_ON


Definition case: Location Update request ("follow on" procedure)
Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from 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 1.
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.

Sub Domain 1 Telecom Procedure (QoS)


Sub Domain 2 Immediate Assignment

Sub Domain 3 Success


Measured Object Common cell
Type Name Overview measurements

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

Feature Name --

....................................................................................................................................................................................................................................
47-82 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC02e - NB_IMM_ASS_SUCC_MO_CM_REEST
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

MC02e - NB_IMM_ASS_SUCC_MO_CM_REEST
Descripton

Long Name NB_IMM_ASS_SUCC_MO_CM_REEST

Definition case: CM Re-establishment procedure


Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from a CELL, with the L3
INFORMATION field containing a 44.018 L3 message with an MIE message type set to CM
RE-ESTABLISHMENT REQUEST message.
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.
Sub Domain 1 Telecom Procedure (QoS)

Sub Domain 2 Immediate Assignment


Sub Domain 3 Success

Measured Object Common cell


Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC02f - NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW
Descripton

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 Telecom Procedure (QoS)

Sub Domain 2 Immediate Assignment

Sub Domain 3 Success


Measured Object Common cell
Type Name Overview measurements

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

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-83
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC02g - NB_IMM_ASS_SUCC_MO_IMSI_DETACH
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

MC02g - NB_IMM_ASS_SUCC_MO_IMSI_DETACH
Descripton

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 Whenever an 48.058 ESTABLISH INDICATION message is received from a 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 Telecom Procedure (QoS)


Sub Domain 2 Immediate Assignment

Sub Domain 3 Success


Measured Object Common cell
Type Name Overview measurements

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

Feature Name --

MC02h - NB_IMM_ASS_SUCC_MO_CALL_EST
Descripton

Long Name NB_IMM_ASS_SUCC_MO_CALL_EST


Definition case: normal or emergency call establishment
Trigger condition Whenever an 48.058 ESTABLISH INDICATION message is received from a 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 Telecom Procedure (QoS)

Sub Domain 2 Immediate Assignment

Sub Domain 3 Success


Measured Object Common cell

Type Name Overview measurements

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

....................................................................................................................................................................................................................................
47-84 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC02h - NB_IMM_ASS_SUCC_MO_CALL_EST
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

External Comment --

Feature Name --

MC02i - NB_IMM_ASS_SUCC_MO_LCS
Descripton

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 Telecom Procedure (QoS)

Sub Domain 2 Immediate Assignment


Sub Domain 3 Success
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Location services (LCS)

MC04 - NB_IMM_ASS_PREP_FAIL_CONG
Descripton

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 Telecom Procedure (QoS)

Sub Domain 2 Immediate Assignment


Sub Domain 3 Failure
Measured Object Common cell

Type Name Overview measurements

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-85
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC04 - NB_IMM_ASS_PREP_FAIL_CONG
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

External Comment --

Feature Name --

MC140a - NB_TCH_NOR_ASS_REQ
Descripton

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 Telecom Procedure (QoS)


Sub Domain 2 Normal Assignment

Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name B8 BSC counters improvements

MC140b - NB_TCH_NOR_ASS_ATPT
Descripton

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.

....................................................................................................................................................................................................................................
47-86 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC140b - NB_TCH_NOR_ASS_ATPT
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Sub Domain 1 Telecom Procedure (QoS)

Sub Domain 2 Normal Assignment


Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

Feature Name B8 BSC counters improvements

MC149 - NB_IMM_ASS_EXEC_FAIL_RADIO
Descripton

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 Telecom Procedure (QoS)


Sub Domain 2 Immediate Assignment
Sub Domain 3 Failure
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-87
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1601 - OLC_NB_IMM_ASS_EXEC_FAIL_RADIO
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

MC1601 - OLC_NB_IMM_ASS_EXEC_FAIL_RADIO
Descripton

Long Name OLC_NB_IMM_ASS_EXEC_FAIL_RADIO

Definition Number of immediate assignment -execution failures due to MS access problem in OLC configuration per
TRX and per site.
Trigger condition Whenever the timer supervising the Immediate Assignment Procedure (T3101) expires during the
establishment of an SDCCH sub-channel.
The identification of the site (RRH) inside the One Logical Cell OLC is obtained by BSC via RRH ID in
CHANNEL REQUIRED
Sub Domain 1 Telecom Procedure (QoS)

Sub Domain 2 Immediate Assignment


Sub Domain 3 --
Measured Object Site_TRX
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name --

MC1602 - OLC_NB_TCH_NOR_ASS_SUCC_TRX
Descripton

Long Name OLC_NB_TCH_NOR_ASS_SUCC_TRX


Definition Number of TCH (in HR or FR usage) normal assignment successes in OLC configuration, per TRX and per
site.
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.
The identification of the site (RRH) inside the One Logical Cell OLC is obtained by BSC via RRH ID in
ESTABLISH INDICATION

Sub Domain 1 Telecom Procedure (QoS)


Sub Domain 2 Normal Assignment

Sub Domain 3 --

Measured Object Site_TRX


Type Name Overview measurements

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

....................................................................................................................................................................................................................................
47-88 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1602 - OLC_NB_TCH_NOR_ASS_SUCC_TRX
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Feature Name --

MC1603 - OLC_NB_TCH_NOR_ASS_ATPT
Descripton

Long Name OLC_NB_TCH_NOR_ASS_ATPT

Definition Number of normal assignment attempts for TCH establishment (in HR or FR usage) in OLC configuration,
per TRX and per site.
Trigger condition Whenever a 44.018 ASSIGNMENT COMMAND message for a normal TCH assignment is received from
the MSC.
The identification of the site (RRH) inside the One Logical Cell OLC is obtained by BSC via RRH ID in
ESTABLISH INDICATION.
Sub Domain 1 Telecom Procedure (QoS)
Sub Domain 2 Normal Assignment
Sub Domain 3 --
Measured Object Site_TRX
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name --

MC1604 - OLC_NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX
Descripton

Long Name OLC_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, in
OLC configuration, per TRX and per site.
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 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".
The identification of the site (RRH) inside the One Logical Cell OLC is obtained by BSC via RRH ID in
ESTABLISH INDICATION.
Sub Domain 1 Telecom Procedure (QoS)

Sub Domain 2 Normal Assignment

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-89
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1604 - OLC_NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Sub Domain 3 --

Measured Object Site_TRX


Type Name Overview measurements

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

Feature Name --

MC161 - NB_DTAP_NOR_ASS_SUCC
Descripton

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 Telecom Procedure (QoS)

Sub Domain 2 DTAP Assignment


Sub Domain 3 Success

Measured Object Common cell


Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC1701 - NB_REDIRECT_ATTEMPT
Descripton

Long Name NB_REDIRECT_ATTEMPT

Definition Nb of attach request with redirect attempt flag set sent by the BSC
Trigger condition Whenever a 48.008 COMPLETE LAYER 3 INFORMATION message, with the parameter Redirect Attempt
Flag set, is sent on A interface to the MSC,
Sub Domain 1 Telecom Procedure (QoS)
Sub Domain 2 --

Sub Domain 3 --

Measured Object MSC_BSC

....................................................................................................................................................................................................................................
47-90 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1701 - NB_REDIRECT_ATTEMPT
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Type Name Overview measurements

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

Feature Name MOCN

MC1702 - NB_REDIRECT_COMMAND
Descripton

Long Name NB_REDIRECT_COMMAND

Definition Nb of reroute command received by the BSC


Trigger condition Whenever the BSC receives a 48.008 REROUTE COMMAND message, whatever the reroute reject cause
Sub Domain 1 Telecom Procedure (QoS)
Sub Domain 2 --

Sub Domain 3 --
Measured Object MSC_BSC
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name MOCN

MC1703 - NB_REDIRECT_COMMAND_CS_PS_COORD
Descripton

Long Name NB_REDIRECT_COMMAND_CS_PS_COORD

Definition Nb of reroute command received by the BSC with CS/PS coordination cause

Trigger condition Whenever the BSC receives a 48.008 REROUTE COMMAND message, with the reroute reject cause set to
CS/PS domain registration coordination required
Sub Domain 1 Telecom Procedure (QoS)

Sub Domain 2 --
Sub Domain 3 --

Measured Object MSC_BSC

Type Name Overview measurements


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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-91
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1703 - NB_REDIRECT_COMMAND_CS_PS_COORD
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

External Comment --

Feature Name MOCN

MC1704 - NB_REDIRECT_COMPLETE
Descripton

Long Name NB_REDIRECT_COMPLETE

Definition Nb of reroute complete received by the BSC


Trigger condition Whenever the BSC receives a 48.008 REROUTE COMPLETE message, whatever the Reroute complete
outcome

Sub Domain 1 Telecom Procedure (QoS)


Sub Domain 2 --
Sub Domain 3 --
Measured Object MSC_BSC
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name MOCN

MC1705 - NB_REDIRECT_COMPLETE_ MS_NOT ACCEPTED


Descripton

Long Name NB_REDIRECT_COMPLETE_ MS_NOT ACCEPTED


Definition Nb of reroute complete received by the BSC with cause MS not accepted

Trigger condition Whenever the BSC receives a 48.008 REROUTE COMPLETE message, with the Reroute complete
outcome set to MS is not accepted

Sub Domain 1 Telecom Procedure (QoS)

Sub Domain 2 --
Sub Domain 3 --
Measured Object MSC_BSC

Type Name Overview measurements

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

Feature Name MOCN

....................................................................................................................................................................................................................................
47-92 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC1706 - NB_REDIRECT_COMPLETE_ MS_ALREADY_REG
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

MC1706 - NB_REDIRECT_COMPLETE_ MS_ALREADY_REG


Descripton

Long Name NB_REDIRECT_COMPLETE_ MS_ALREADY_REG

Definition Nb of reroute complete received by the BSC with cause MS already registered
Trigger condition Whenever the BSC receives a 48.008 REROUTE COMPLETE message, with the Reroute complete
outcome set to MS is already registered

Sub Domain 1 Telecom Procedure (QoS)


Sub Domain 2 --

Sub Domain 3 --
Measured Object MSC_BSC

Type Name Overview measurements


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

Feature Name MOCN

MC19 - NB_TCH_NOR_ASS_HO_PREP_FAIL_ACHAN_MIS (110)


Descripton

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 inter-PLMN and intra-PLMN handover events.
Sub Domain 1 Telecom Procedure (QoS)

Sub Domain 2 Normal Assignment


Sub Domain 3 Failure

Measured Object BSC


Type Name Overview measurements

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

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-93
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC612a - NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

MC612a - NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE
Descripton

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 Telecom Procedure (QoS)
Sub Domain 2 Normal Assignment
Sub Domain 3 Failure
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name --

....................................................................................................................................................................................................................................
47-94 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC612b - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

MC612b - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL
Descripton

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 The counter is incremented upon the sending of 48.008 ASSIGNMENT FAILURE (cause: "no radio
resource available") for a TCH channel because the queue is full and no request of lower priority can be
dequeued.
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 status;
- or the TCH processing capacity of AbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_
TCH_TS parameter

Sub Domain 1 Telecom Procedure (QoS)


Sub Domain 2 Normal Assignment
Sub Domain 3 Failure
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name --

MC612c - NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP
Descripton

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.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-95
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC612c - NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

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 Telecom Procedure (QoS)

Sub Domain 2 --
Sub Domain 3 Failure
Measured Object Common cell

Type Name Overview measurements

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

Feature Name --

MC612d - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ
Descripton

Long Name NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ


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

....................................................................................................................................................................................................................................
47-96 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC612d - NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Sub Domain 1 Telecom Procedure (QoS)

Sub Domain 2 Normal Assignment


Sub Domain 3 Failure

Measured Object Common cell


Type Name Overview measurements

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

Feature Name --

MC718 - NB_TCH_NOR_ASS_SUCC_TRX
Descripton

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 Telecom Procedure (QoS)

Sub Domain 2 Normal Assignment


Sub Domain 3 Success
Measured Object TRX
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-97
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC746b - NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

MC746b - NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX
Descripton

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 Telecom Procedure (QoS)


Sub Domain 2 Normal Assignment
Sub Domain 3 Failure
Measured Object TRX
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name B7.1 counters improvements

MC812 - NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS
Descripton

Long Name NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS


Definition MC812 = C812 = C612a + C612b + C612c + C612d
Trigger condition --

Sub Domain 1 Telecom Procedure (QoS)

Sub Domain 2 Normal Assignment


Sub Domain 3 Failure

Measured Object Common cell

....................................................................................................................................................................................................................................
47-98 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC812 - NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Type Name Overview measurements

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

Feature Name --

MC901 - NB_Suspend_Resume_req
Descripton

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 Overview measurements

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

Feature Name Suspend/Resume for class B mobiles

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-99
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC902 - Nb_Suspend_fail
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

MC902 - Nb_Suspend_fail
Descripton

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 Telecom Procedure (QoS)


Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Suspend/Resume for class B mobiles

MC903 - Nb_Suspend_succ
Descripton

Long Name Nb_Suspend_succ


Definition Number of suspensions successes.
Trigger condition Reception of Resume ack message from MFS.
Sub Domain 1 Telecom Procedure (QoS)
Sub Domain 2 --

Sub Domain 3 --

Measured Object Common cell


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

External Comment --

Feature Name Suspend/Resume for class B mobiles

....................................................................................................................................................................................................................................
47-100 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC921a - NB_TCH_NOR_ASS_HO_REQ_ABLE_TO_PREEMPT
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

MC921a - NB_TCH_NOR_ASS_HO_REQ_ABLE_TO_PREEMPT
Descripton

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 Telecom Procedure (QoS)


Sub Domain 2 Normal Assignment

Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name eMLPP (preemption)

MC921b - NB_PREEMPT_CAP_ALLOC_SUCC
Descripton

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 Telecom Procedure (QoS)

Sub Domain 2 Normal Assignment


Sub Domain 3 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-101
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC921b - NB_PREEMPT_CAP_ALLOC_SUCC
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name eMLPP (preemption)

MC921c - NB_PREEMPTED_CALLS
Descripton

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 Telecom Procedure (QoS)


Sub Domain 2 Normal Assignment
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name eMLPP (preemption)

MC921d - NB_PREEMPT_CAP_OUT_DR_ALLOC_SUCC
Descripton

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 Telecom Procedure (QoS)

Sub Domain 2 Normal Assignment


Sub Domain 3 --

Measured Object Common cell

....................................................................................................................................................................................................................................
47-102 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC921d - NB_PREEMPT_CAP_OUT_DR_ALLOC_SUCC
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

Type Name Overview measurements

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

Feature Name eMLPP (preemption)

MC921e - NB_TCH_NOR_ASS_HO_SUCC_PREEMPTABLE
Descripton

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 counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1 Telecom Procedure (QoS)

Sub Domain 2 Normal Assignment


Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name eMLPP (preemption)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 47-103
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of Service MC933 - NB_TCH_NOR_ASS_PREP_FAIL_PMIS
Telecom Procedure (QoS)
....................................................................................................................................................................................................................................

MC933 - NB_TCH_NOR_ASS_PREP_FAIL_PMIS
Descripton

Long Name NB_TCH_NOR_ASS_PREP_FAIL_PMIS

Definition Number of TCH (in HR or FR usage) normal assignment preparation failures due to A interface mismatch
between the BSC and the MSC.
Trigger condition The counter is incremented upon the sending of 48.008 ASSIGNMENT FAILURE (cause: "circuit pool
mismatch")

Sub Domain 1 Telecom Procedure (QoS)


Sub Domain 2 Normal Assignment

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

Feature Name AMR WB speech codec GMSK

....................................................................................................................................................................................................................................
47-104 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
48 48
Resource Availability &
Usage

Channel

Overview
Purpose
This section contains Channel parameters.

Contents

MC141 - AV_NB_TCH_QUEUED 48-3


MC1605 - OLC_AV_NB_IDLE_TCH_INTERF_BAND1_TRX 48-3
MC1606 - OLC_AV_NB_IDLE_TCH_INTERF_BAND2_TRX 48-4
MC1607 - OLC_AV_NB_IDLE_TCH_INTERF_BAND3_TRX 48-4
MC1608 - OLC_AV_NB_IDLE_TCH_INTERF_BAND4_TRX 48-5
MC1609 - OLC_AV_NB_IDLE_TCH_INTERF_BAND5_TRX 48-6
MC24 - AV_NB_NOT_AVAIL_TRX_TS 48-6
MC250 - AV_NB_AVAIL_TCH 48-7
MC26 - AV_NB_AVAIL_SDCCH 48-7
MC27 - AV_NB_AVAIL_CCCH 48-8
MC28a - AV_NB_BUSY_CS_TS 48-8
MC29a - NB_MAX_SIMUL_BUSY_CS_TS 48-9
MC31 - NB_MAX_SIMUL_BUSY_SDCCH 48-10
MC320a - AV_NB_IDLE_TCH_INTERF_BAND1 48-10
MC320b - AV_NB_IDLE_TCH_INTERF_BAND2 48-11
MC320c - AV_NB_IDLE_TCH_INTERF_BAND3 48-12

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage Overview
Channel
....................................................................................................................................................................................................................................

MC320d - AV_NB_IDLE_TCH_INTERF_BAND4 48-13


MC320e - AV_NB_IDLE_TCH_INTERF_BAND5 48-14
MC320f - AV_NB_IDLE_TCH_INTERF_BAND1_TRX 48-15
MC320g - AV_NB_IDLE_TCH_INTERF_BAND2_TRX 48-16
MC320h - AV_NB_IDLE_TCH_INTERF_BAND3_TRX 48-17
MC320i - AV_NB_IDLE_TCH_INTERF_BAND4_TRX 48-17
MC320j - AV_NB_IDLE_TCH_INTERF_BAND5_TRX 48-18
MC320k - AV_NB_IDLE_CHA_INTERF_BAND1_TRX 48-18
MC320l - AV_NB_IDLE_CHA_INTERF_BAND2_TRX 48-20
MC320m - AV_NB_IDLE_CHA_INTERF_BAND3_TRX 48-21
MC320n - AV_NB_IDLE_CHA_INTERF_BAND4_TRX 48-22
MC320o - AV_NB_IDLE_CHA_INTERF_BAND5_TRX 48-23
MC34 - TIME_ALL_AVAIL_TRX_TS_BUSY 48-24
MC35 - AV_NB_A_TRAF_CHAN_BLOCK_OUT_OF_SERV 48-24
MC36 - AV_NB_AVAIL_A_TRAF_CHAN 48-25
MC370a - NB_TRX_FR_ALLOC 48-26
MC370b - NB_TRX_HR_ALLOC 48-26
MC390 - NB_TIMES_SDCCH_BUSY (110) 48-27
MC800 - AV_NB_AVAIL_DYN_TS 48-27
MC801a - AV_NB_BUSY_DYN_TCH 48-28
MC801b - MAX_NB_BUSY_DYN_TCH 48-28
MC802a - AV_NB_BUSY_DYN_SDCCH 48-29
MC802b - MAX_NB_BUSY_DYN_SDCCH 48-30
MC803 - TIME_SDCCH_CONGESTION 48-30

....................................................................................................................................................................................................................................
48-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC141 - AV_NB_TCH_QUEUED
Channel
....................................................................................................................................................................................................................................

MC141 - AV_NB_TCH_QUEUED
Descripton

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 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. In order to provide one decimal place, the averaged
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 TCH


Sub Domain 3 Usage
Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name --

MC1605 - OLC_AV_NB_IDLE_TCH_INTERF_BAND1_TRX
Descripton

Long Name OLC_AV_NB_IDLE_TCH_INTERF_BAND1_TRX


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 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.
The identification of the site (RRH) inside the One Logical Cell OLC is obtained by BSC via RRHID in RF
RESOURCE INDICATION

Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Site_TRX

Type Name Overview measurements


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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1605 - OLC_AV_NB_IDLE_TCH_INTERF_BAND1_TRX
Channel
....................................................................................................................................................................................................................................

External Comment --

Feature Name --

MC1606 - OLC_AV_NB_IDLE_TCH_INTERF_BAND2_TRX
Descripton

Long Name OLC_AV_NB_IDLE_TCH_INTERF_BAND2_TRX

Definition Average number of free TCH and free dynamic SDCCH/8 radio timeslots belonging to the interference band
2.This number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.
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 average value (real) is rounded up or down to the
the nearest integer value.
The identification of the site (RRH) inside the One Logical Cell OLC is obtained by BSC via RRHID in RF
RESOURCE INDICATION
Sub Domain 1 Channel
Sub Domain 2 TCH

Sub Domain 3 --
Measured Object Site_TRX

Type Name Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC1607 - OLC_AV_NB_IDLE_TCH_INTERF_BAND3_TRX
Descripton

Long Name OLC_AV_NB_IDLE_TCH_INTERF_BAND3_TRX

Definition Average number of free TCH and free dynamic SDCCH/8 radio timeslots belonging to the interference band
3.This number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.

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
the nearest integer value.
The identification of the site (RRH) inside the One Logical Cell OLC is obtained by BSC via RRHID in RF
RESOURCE INDICATION

Sub Domain 1 Channel

Sub Domain 2 TCH

....................................................................................................................................................................................................................................
48-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1607 - OLC_AV_NB_IDLE_TCH_INTERF_BAND3_TRX
Channel
....................................................................................................................................................................................................................................

Sub Domain 3 --

Measured Object Site_TRX


Type Name Overview measurements

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

Feature Name --

MC1608 - OLC_AV_NB_IDLE_TCH_INTERF_BAND4_TRX
Descripton

Long Name OLC_AV_NB_IDLE_TCH_INTERF_BAND4_TRX


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 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
the nearest integer value.
The identification of the site (RRH) inside the One Logical Cell OLC is obtained by BSC via RRHID in RF
RESOURCE INDICATION
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Site_TRX


Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC1609 - OLC_AV_NB_IDLE_TCH_INTERF_BAND5_TRX
Channel
....................................................................................................................................................................................................................................

MC1609 - OLC_AV_NB_IDLE_TCH_INTERF_BAND5_TRX
Descripton

Long Name OLC_AV_NB_IDLE_TCH_INTERF_BAND5_TRX

Definition Average number of free TCH and free dynamic SDCCH/8 radio timeslots belonging to the interference band
5.This number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.
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 average value (real) is rounded up or down to the
the nearest integer value.
Sub Domain 1 Channel

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Site_TRX


Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC24 - AV_NB_NOT_AVAIL_TRX_TS
Descripton

Long Name AV_NB_NOT_AVAIL_TRX_TS


Definition Average number of not available radio timeslots (TRX_TS). The timeslot is not available if it is "blocked" or
"out of service".

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 TRX_TS

Sub Domain 3 Availability


Measured Object Common cell
Type Name Overview measurements

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

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
48-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC250 - AV_NB_AVAIL_TCH
Channel
....................................................................................................................................................................................................................................

MC250 - AV_NB_AVAIL_TCH
Descripton

Long Name AV_NB_AVAIL_TCH

Definition Average number of available radio timeslots for traffic usage (i.e. TCH (for HR or FR usage in VAMOS
mode or not) or PDCH).
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 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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name --

MC26 - AV_NB_AVAIL_SDCCH
Descripton

Long Name AV_NB_AVAIL_SDCCH


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

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


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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC26 - AV_NB_AVAIL_SDCCH
Channel
....................................................................................................................................................................................................................................

External Comment --

Feature Name --

MC27 - AV_NB_AVAIL_CCCH
Descripton

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 Overview measurements

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

Feature Name --

MC28a - AV_NB_BUSY_CS_TS
Descripton

Long Name AV_NB_BUSY_CS_TS

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

....................................................................................................................................................................................................................................
48-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC28a - AV_NB_BUSY_CS_TS
Channel
....................................................................................................................................................................................................................................

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 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 radio timeslot in VAMOS usage is said busy when at least one of the VAMOS subchannels is
busy. 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 Overview measurements


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

External Comment --
Feature Name --

MC29a - NB_MAX_SIMUL_BUSY_CS_TS
Descripton

Long Name NB_MAX_SIMUL_BUSY_CS_TS


Definition Maximum number of simultaneously busy radio timeslots (in HR TCH or FR TCH 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 radio timeslots (in HR TCH or FR TCH usage) and busy
dynamic SDCCH/8 radio timeslots allocated as TCH. A radio timeslot in VAMOS usage is said busy when
at least one of the VAMOS subchannels is busy. 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 Overview measurements

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC29a - NB_MAX_SIMUL_BUSY_CS_TS
Channel
....................................................................................................................................................................................................................................

External Comment --

Feature Name Dynamic SDCCH allocation

MC31 - NB_MAX_SIMUL_BUSY_SDCCH
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name --

MC320a - AV_NB_IDLE_TCH_INTERF_BAND1
Descripton

Long Name AV_NB_IDLE_TCH_INTERF_BAND1

....................................................................................................................................................................................................................................
48-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC320a - AV_NB_IDLE_TCH_INTERF_BAND1
Channel
....................................................................................................................................................................................................................................

Definition Average number of radio timeslots with free resources (timeslot in TCH usage and dynamic SDCCH/8
allocated as TCH) belonging to the interference band 1. This number is updated upon the receipt of 48.058
RF RESOURCE INDICATION. In this message, one interference level is reported for every time slot with
an idle channel or an idle subchannel
When VAMOS is enabled, the BTS sends idle measurements only when the physical resource is unused:
-For an idle channel, BTS sends idle measurement for a channel.
-When a FR TCH is allocated in non-VAMOS mode, then no idle measurements is sent.
-When a HR TCH is allocated in non-VAMOS mode, the BTS reports idle measurements if the other
subchannel on the same timeslot is idle.
-When a MS is allocated in non-VAMOS mode on a HR TCH and another MS is allocated in non-VAMOS
mode in the other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and one MS is allocated in non-VAMOS mode in the
other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and the other subchannel on the same timeslot is idle,
then idle measurements is sent for the idle subchannel.

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 TCH
Sub Domain 3 Usage

Measured Object Common cell


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

External Comment --
Feature Name --

MC320b - AV_NB_IDLE_TCH_INTERF_BAND2
Descripton

Long Name AV_NB_IDLE_TCH_INTERF_BAND2

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC320b - AV_NB_IDLE_TCH_INTERF_BAND2
Channel
....................................................................................................................................................................................................................................

Definition Average number of radio timeslots with free resources (timeslot in TCH usage and free dynamic SDCCH/8
allocated as TCH) belonging to the interference band 2. This number is updated upon the receipt of 48.058
RF RESOURCE INDICATION.In this message, one interference level is reported for every time slot with
an idle channel or an idle subchannel
When VAMOS is enabled, the BTS sends idle measurements only when the physical resource is unused:
-For an idle channel, BTS sends idle measurement for a channel.
-When a FR TCH is allocated in non-VAMOS mode, then no idle measurements is sent.
-When a HR TCH is allocated in non-VAMOS mode, the BTS reports idle measurements if the other
subchannel on the same timeslot is idle.
-When a MS is allocated in non-VAMOS mode on a HR TCH and another MS is allocated in non-VAMOS
mode in the other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and one MS is allocated in non-VAMOS mode in the
other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and the other subchannel on the same timeslot is idle,
then idle measurements is sent for the idle subchannel.

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 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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name --

MC320c - AV_NB_IDLE_TCH_INTERF_BAND3
Descripton

Long Name AV_NB_IDLE_TCH_INTERF_BAND3

....................................................................................................................................................................................................................................
48-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC320c - AV_NB_IDLE_TCH_INTERF_BAND3
Channel
....................................................................................................................................................................................................................................

Definition Average number of radio timeslots with free resources (timeslot in TCH usage and dynamic SDCCH/8
allocated as TCH) belonging to the interference band 3. This number is updated upon the receipt of 48.058
RF RESOURCE INDICATION.In this message, one interference level is reported for every time slot with
an idle channel or an idle subchannel
When VAMOS is enabled, the BTS sends idle measurements only when the physical resource is unused:
-For an idle channel, BTS sends idle measurement for a channel.
-When a FR TCH is allocated in non-VAMOS mode, then no idle measurements is sent.
-When a HR TCH is allocated in non-VAMOS mode, the BTS reports idle measurements if the other
subchannel on the same timeslot is idle.
-When a MS is allocated in non-VAMOS mode on a HR TCH and another MS is allocated in non-VAMOS
mode in the other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and one MS is allocated in non-VAMOS mode in the
other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and the other subchannel on the same timeslot is idle,
then idle measurements is sent for the idle subchannel.

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 TCH
Sub Domain 3 Usage

Measured Object Common cell


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

External Comment --
Feature Name --

MC320d - AV_NB_IDLE_TCH_INTERF_BAND4
Descripton

Long Name AV_NB_IDLE_TCH_INTERF_BAND4

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC320d - AV_NB_IDLE_TCH_INTERF_BAND4
Channel
....................................................................................................................................................................................................................................

Definition Average number of radio timeslots with free resources (timeslot in TCH usage and dynamic SDCCH/8
allocated as TCH) belonging to the interference band 4. This number is updated upon the receipt of 48.058
RF RESOURCE INDICATION.In this message, one interference level is reported for every time slot with
an idle channel or an idle subchannel
When VAMOS is enabled, the BTS sends idle measurements only when the physical resource is unused:
-For an idle channel, BTS sends idle measurement for a channel.
-When a FR TCH is allocated in non-VAMOS mode, then no idle measurements is sent.
-When a HR TCH is allocated in non-VAMOS mode, the BTS reports idle measurements if the other
subchannel on the same timeslot is idle.
-When a MS is allocated in non-VAMOS mode on a HR TCH and another MS is allocated in non-VAMOS
mode in the other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and one MS is allocated in non-VAMOS mode in the
other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and the other subchannel on the same timeslot is idle,
then idle measurements is sent for the idle subchannel.

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 TCH
Sub Domain 3 Usage

Measured Object Common cell


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

External Comment --
Feature Name --

MC320e - AV_NB_IDLE_TCH_INTERF_BAND5
Descripton

Long Name AV_NB_IDLE_TCH_INTERF_BAND5

....................................................................................................................................................................................................................................
48-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC320e - AV_NB_IDLE_TCH_INTERF_BAND5
Channel
....................................................................................................................................................................................................................................

Definition Average number of radio timeslots with free resources (timeslot in TCH usage and dynamic SDCCH/8
allocated as TCH) belonging to the interference band 5. This number is updated upon the receipt of 48.058
RF RESOURCE INDICATION.In this message, one interference level is reported for every time slot with
an idle channel or an idle subchannel
When VAMOS is enabled, the BTS sends idle measurements only when the physical resource is unused:
-For an idle channel, BTS sends idle measurement for a channel.
-When a FR TCH is allocated in non-VAMOS mode, then no idle measurements is sent.
-When a HR TCH is allocated in non-VAMOS mode, the BTS reports idle measurements if the other
subchannel on the same timeslot is idle.
-When a MS is allocated in non-VAMOS mode on a HR TCH and another MS is allocated in non-VAMOS
mode in the other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and one MS is allocated in non-VAMOS mode in the
other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and the other subchannel on the same timeslot is idle,
then idle measurements is sent for the idle subchannel.

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 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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name --

MC320f - AV_NB_IDLE_TCH_INTERF_BAND1_TRX
Descripton

Long Name AV_NB_IDLE_TCH_INTERF_BAND1_TRX


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.This counter is similar
to MC320a but at TRX level instead of cell level.

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 TCH

Sub Domain 3 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC320f - AV_NB_IDLE_TCH_INTERF_BAND1_TRX
Channel
....................................................................................................................................................................................................................................

Measured Object TRX

Type Name Overview measurements


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

External Comment --
Feature Name --

MC320g - AV_NB_IDLE_TCH_INTERF_BAND2_TRX
Descripton

Long Name AV_NB_IDLE_TCH_INTERF_BAND2_TRX


Definition Average number of free TCH and free dynamic SDCCH/8 radio timeslots belonging to the interference band
2.This number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.This counter is similar
to MC320b but at TRX level instead of cell level.
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 average value (real) is rounded up or down to the
nearest integer value.
Sub Domain 1 Channel
Sub Domain 2 --
Sub Domain 3 --
Measured Object TRX
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
48-16 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC320h - AV_NB_IDLE_TCH_INTERF_BAND3_TRX
Channel
....................................................................................................................................................................................................................................

MC320h - AV_NB_IDLE_TCH_INTERF_BAND3_TRX
Descripton

Long Name AV_NB_IDLE_TCH_INTERF_BAND3_TRX

Definition Average number of free TCH and free dynamic SDCCH/8 radio timeslots belonging to the interference band
3.This number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.This counter is similar
to MC320c but at TRX level instead of cell level.
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 --
Sub Domain 3 --
Measured Object TRX
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name --

MC320i - AV_NB_IDLE_TCH_INTERF_BAND4_TRX
Descripton

Long Name AV_NB_IDLE_TCH_INTERF_BAND4_TRX


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.This counter is similar to MC320d but at TRX level instead of cell level.

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

Sub Domain 3 --

Measured Object TRX


Type Name Overview measurements

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-17
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC320i - AV_NB_IDLE_TCH_INTERF_BAND4_TRX
Channel
....................................................................................................................................................................................................................................

Feature Name --

MC320j - AV_NB_IDLE_TCH_INTERF_BAND5_TRX
Descripton

Long Name AV_NB_IDLE_TCH_INTERF_BAND5_TRX

Definition Average number of free TCH and free dynamic SDCCH/8 radio timeslots belonging to the interference band
5.This number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.This counter is similar
to MC320e but at TRX level instead of cell level.
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 average value (real) is rounded up or down to the
nearest integer value.
Sub Domain 1 Channel
Sub Domain 2 --
Sub Domain 3 --
Measured Object TRX
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name --

MC320k - AV_NB_IDLE_CHA_INTERF_BAND1_TRX
Descripton

Long Name AV_NB_IDLE_CHA_INTERF_BAND1_TRX

....................................................................................................................................................................................................................................
48-18 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC320k - AV_NB_IDLE_CHA_INTERF_BAND1_TRX
Channel
....................................................................................................................................................................................................................................

Definition Average number of (partially) free timeslots usable as


- TCH and dynamic SDCCH/8 radio timeslots
- PDCH
- SDCCH
belonging to the interference band 1.
This number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.
In this message, related to TCH, one interference level is reported for every time slot with an idle channel or
an idle subchannel
When VAMOS is enabled, the BTS sends idle measurements only when the physical resource is unused:
-For an idle channel, BTS sends idle measurement for a channel.
-When a FR TCH is allocated in non-VAMOS mode, then no idle measurements is sent.
-When a HR TCH is allocated in non-VAMOS mode, the BTS reports idle measurements if the other
subchannel on the same timeslot is idle.
-When a MS is allocated in non-VAMOS mode on a HR TCH and another MS is allocated in non-VAMOS
mode in the other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and one MS is allocated in non-VAMOS mode in the
other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and the other subchannel on the same timeslot is idle,
then idle measurements is sent for the idle subchannel.
In this message, related to SDCCH, for static SDCCH/4 or SDCCH/8, idle means that all subchannels of the
time slot are free. Consequently, the BTS sends idle measurements for SDCCH only when the physical
resource (channel or subchannel) is totally unused.

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. This counter is filled only if EN_INTFBD_PM is active.

Sub Domain 1 Channel


Sub Domain 2 --
Sub Domain 3 --
Measured Object TRX
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-19
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC320l - AV_NB_IDLE_CHA_INTERF_BAND2_TRX
Channel
....................................................................................................................................................................................................................................

MC320l - AV_NB_IDLE_CHA_INTERF_BAND2_TRX
Descripton

Long Name AV_NB_IDLE_CHA_INTERF_BAND2_TRX

Definition Average number of (partially) free timeslots usable as


-TCH and dynamic SDCCH/8 radio timeslots
-PDCH
-SDCCH
belonging to the interference band 2.
This number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.
In this message, related to TCH, one interference level is reported for every time slot with an idle channel or
an idle subchannel
When VAMOS is enabled, the BTS sends idle measurements only when the physical resource is unused:
-For an idle channel, BTS sends idle measurement for a channel.
-When a FR TCH is allocated in non-VAMOS mode, then no idle measurements is sent.
-When a HR TCH is allocated in non-VAMOS mode, the BTS reports idle measurements if the other
subchannel on the same timeslot is idle.
-When a MS is allocated in non-VAMOS mode on a HR TCH and another MS is allocated in non-VAMOS
mode in the other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and one MS is allocated in non-VAMOS mode in the
other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and the other subchannel on the same timeslot is idle,
then idle measurements is sent for the idle subchannel.
In this message, related to SDCCH, for static SDCCH/4 or SDCCH/8, idle means that all subchannels of the
time slot are free. Consequently, the BTS sends idle measurements for SDCCH only when the physical
resource (channel or subchannel) is totally unused.

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 average value (real) is rounded up or down to the
nearest integer value.
This counter is filled only if EN_INTFBD_PM is active.
Sub Domain 1 Channel
Sub Domain 2 --

Sub Domain 3 --

Measured Object TRX


Type Name Overview measurements

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

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
48-20 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC320m - AV_NB_IDLE_CHA_INTERF_BAND3_TRX
Channel
....................................................................................................................................................................................................................................

MC320m - AV_NB_IDLE_CHA_INTERF_BAND3_TRX
Descripton

Long Name AV_NB_IDLE_CHA_INTERF_BAND3_TRX

Definition Average number of (partially) free timeslots usable as


-TCH and dynamic SDCCH/8 radio timeslots
-PDCH
-SDCCH
belonging to the interference band 3.
This number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.
In this message, related to TCH, one interference level is reported for every time slot with an idle channel or
an idle subchannel
When VAMOS is enabled, the BTS sends idle measurements only when the physical resource is unused:
-For an idle channel, BTS sends idle measurement for a channel.
-When a FR TCH is allocated in non-VAMOS mode, then no idle measurements is sent.
-When a HR TCH is allocated in non-VAMOS mode, the BTS reports idle measurements if the other
subchannel on the same timeslot is idle.
-When a MS is allocated in non-VAMOS mode on a HR TCH and another MS is allocated in non-VAMOS
mode in the other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and one MS is allocated in non-VAMOS mode in the
other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and the other subchannel on the same timeslot is idle,
then idle measurements is sent for the idle subchannel.
In this message, related to SDCCH, for static SDCCH/4 or SDCCH/8, idle means that all subchannels of the
time slot are free. Consequently, the BTS sends idle measurements for SDCCH only when the physical
resource (channel or subchannel) is totally unused.

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 average value (real) is rounded up or down to the
nearest integer value.
This counter is filled only if EN_INTFBD_PM is active
Sub Domain 1 Channel
Sub Domain 2 --

Sub Domain 3 --

Measured Object TRX


Type Name Overview measurements

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

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-21
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC320n - AV_NB_IDLE_CHA_INTERF_BAND4_TRX
Channel
....................................................................................................................................................................................................................................

MC320n - AV_NB_IDLE_CHA_INTERF_BAND4_TRX
Descripton

Long Name AV_NB_IDLE_CHA_INTERF_BAND4_TRX

Definition Average number of (partially) free timeslots usable as


-TCH and dynamic SDCCH/8 radio timeslots
-PDCH
-SDCCH
belonging to the interference band 4.
This number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.
In this message, related to TCH, one interference level is reported for every time slot with an idle channel or
an idle subchannel
When VAMOS is enabled, the BTS sends idle measurements only when the physical resource is unused:
-For an idle channel, BTS sends idle measurement for a channel.
-When a FR TCH is allocated in non-VAMOS mode, then no idle measurements is sent.
-When a HR TCH is allocated in non-VAMOS mode, the BTS reports idle measurements if the other
subchannel on the same timeslot is idle.
-When a MS is allocated in non-VAMOS mode on a HR TCH and another MS is allocated in non-VAMOS
mode in the other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and one MS is allocated in non-VAMOS mode in the
other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and the other subchannel on the same timeslot is idle,
then idle measurements is sent for the idle subchannel.
In this message, related to SDCCH, for static SDCCH/4 or SDCCH/8, idle means that all subchannels of the
time slot are free. Consequently, the BTS sends idle measurements for SDCCH only when the physical
resource (channel or subchannel) is totally unused.

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 average value (real) is rounded up or down to the
nearest integer value.
This counter is filled only if EN_INTFBD_PM is active
Sub Domain 1 Channel
Sub Domain 2 --

Sub Domain 3 --

Measured Object TRX


Type Name Overview measurements

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

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
48-22 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC320o - AV_NB_IDLE_CHA_INTERF_BAND5_TRX
Channel
....................................................................................................................................................................................................................................

MC320o - AV_NB_IDLE_CHA_INTERF_BAND5_TRX
Descripton

Long Name AV_NB_IDLE_CHA_INTERF_BAND5_TRX

Definition Average number of (partially) free timeslots usable as


-TCH and dynamic SDCCH/8 radio timeslots
-PDCH
-SDCCH
belonging to the interference band 5.
This number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.
In this message, related to TCH, one interference level is reported for every time slot with an idle channel or
an idle subchannel
When VAMOS is enabled, the BTS sends idle measurements only when the physical resource is unused:
-For an idle channel, BTS sends idle measurement for a channel.
-When a FR TCH is allocated in non-VAMOS mode, then no idle measurements is sent.
-When a HR TCH is allocated in non-VAMOS mode, the BTS reports idle measurements if the other
subchannel on the same timeslot is idle.
-When a MS is allocated in non-VAMOS mode on a HR TCH and another MS is allocated in non-VAMOS
mode in the other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and one MS is allocated in non-VAMOS mode in the
other HR TCH on the same timeslot, then no idle measurements is sent.
-When two MSs are paired on two VAMOS HR TCHs and the other subchannel on the same timeslot is idle,
then idle measurements is sent for the idle subchannel.
In this message, related to SDCCH, for static SDCCH/4 or SDCCH/8, idle means that all subchannels of the
time slot are free. Consequently, the BTS sends idle measurements for SDCCH only when the physical
resource (channel or subchannel) is totally unused.

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 average value (real) is rounded up or down to the
nearest integer value.
This counter is filled only if EN_INTFBD_PM is active
Sub Domain 1 Channel
Sub Domain 2 --

Sub Domain 3 --

Measured Object TRX


Type Name Overview measurements

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

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-23
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC34 - TIME_ALL_AVAIL_TRX_TS_BUSY
Channel
....................................................................................................................................................................................................................................

MC34 - TIME_ALL_AVAIL_TRX_TS_BUSY
Descripton

Long Name TIME_ALL_AVAIL_TRX_TS_BUSY

Definition Cumulated time (in seconds) during which there is no free radio timeslot to serve an incoming FR TCH
request.
A radio timeslot is seen as busy:
i) if the timeslot is occupied by a HR TCH or FR TCH CS call in VAMOS or non-VAMOS mode (in
particular if it is occupied by the CS part of a DTM call), or
ii) if the timeslot is allocated to the MFS to carry PS traffic.
Trigger condition The counter is started when there is no free radio timeslot to serve an incoming FR TCH request.
The counter is stopped when there is a free radio timeslot 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 Overview measurements


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

External Comment --
Feature Name Dynamic SDCCH allocation

MC35 - AV_NB_A_TRAF_CHAN_BLOCK_OUT_OF_SERV
Descripton

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

....................................................................................................................................................................................................................................
48-24 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC35 - AV_NB_A_TRAF_CHAN_BLOCK_OUT_OF_SERV
Channel
....................................................................................................................................................................................................................................

Sub Domain 3 Availability

Measured Object BSC


Type Name Overview measurements

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

Feature Name --

MC36 - AV_NB_AVAIL_A_TRAF_CHAN
Descripton

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 Overview measurements

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

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-25
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC370a - NB_TRX_FR_ALLOC
Channel
....................................................................................................................................................................................................................................

MC370a - NB_TRX_FR_ALLOC
Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC370b - NB_TRX_HR_ALLOC
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
48-26 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC390 - NB_TIMES_SDCCH_BUSY (110)
Channel
....................................................................................................................................................................................................................................

MC390 - NB_TIMES_SDCCH_BUSY (110)


Descripton

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 Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC800 - AV_NB_AVAIL_DYN_TS
Descripton

Long Name AV_NB_AVAIL_DYN_TS


Definition Average number of available dynamic SDCCH/8 timeslots.
Trigger condition At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The averaged value is rounded up or down to the
nearest integer value.

Sub Domain 1 Channel


Sub Domain 2 SDCCH

Sub Domain 3 Availability

Measured Object Common cell


Type Name Overview measurements

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

Feature Name Dynamic SDCCH allocation

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-27
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC801a - AV_NB_BUSY_DYN_TCH
Channel
....................................................................................................................................................................................................................................

MC801a - AV_NB_BUSY_DYN_TCH
Descripton

Long Name AV_NB_BUSY_DYN_TCH

Definition Average number of busy dynamic SDCCH/8 timeslots allocated as TCH (in FR or HR usage in VAMOS
mode and non-VAMOS mode). 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 Overview measurements

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

Feature Name Dynamic SDCCH allocation

MC801b - MAX_NB_BUSY_DYN_TCH
Descripton

Long Name MAX_NB_BUSY_DYN_TCH

Definition Maximum number of busy dynamic SDCCH/8 timeslots allocated as TCH (in FR or HR usage in VAMOS
mode and non-VAMOS mode). 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 Overview measurements

....................................................................................................................................................................................................................................
48-28 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC801b - MAX_NB_BUSY_DYN_TCH
Channel
....................................................................................................................................................................................................................................

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

External Comment --
Feature Name Dynamic SDCCH allocation

MC802a - AV_NB_BUSY_DYN_SDCCH
Descripton

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 Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Dynamic SDCCH allocation

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-29
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC802b - MAX_NB_BUSY_DYN_SDCCH
Channel
....................................................................................................................................................................................................................................

MC802b - MAX_NB_BUSY_DYN_SDCCH
Descripton

Long Name MAX_NB_BUSY_DYN_SDCCH

Definition Maximum number of busy dynamic SDCCH sub-channels allocated on the dynamic SDCCH/8 timeslots.
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 Overview measurements

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

Feature Name Dynamic SDCCH allocation

MC803 - TIME_SDCCH_CONGESTION
Descripton

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 Overview measurements

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

....................................................................................................................................................................................................................................
48-30 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC803 - TIME_SDCCH_CONGESTION
Channel
....................................................................................................................................................................................................................................

External Comment --

Feature Name Dynamic SDCCH allocation

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-31
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage Overview
Interface (Resource Availability)
....................................................................................................................................................................................................................................

Interface (Resource Availability)

Overview
Purpose
This section contains Interface (Resource Availability) parameters.

Contents

MN1.1 - TIME_N7_ALIGNED 48-32

MN1.1 - TIME_N7_ALIGNED
Descripton

Long Name TIME_N7_ALIGNED


Definition Time (in seconds) during which the N7 SL is correctly aligned.
Trigger condition Whenever the No.7 Signalling channel between the MSC and BSS is correctly aligned, this counter will be
incremented every second.

Sub Domain 1 Interface (Resource Availability)


Sub Domain 2 A
Sub Domain 3 Availability
Measured Object N7 Signalling Link
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
48-32 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage Overview
Resource Allocation & Management
....................................................................................................................................................................................................................................

Resource Allocation & Management

Overview
Purpose
This section contains Resource Allocation & Management parameters.

Contents

MC701a - NB_TCH_FR_REQ 48-34


MC701b - NB_TCH_DR_REQ 48-35
MC701c - NB_TCH_DR_EFR_REQ 48-35
MC701d - NB_TCH_AMR_REQ 48-36
MC701e - NB_TCH_DATA_REQ 48-36
MC701f - NB_TCH_FR_EFR_REQ 48-37
MC701g - NB_TCH_NO_FR_REQ 48-37
MC701i - NB_TCH_ATDM_REQ 48-38
MC701j - NB_TCH_AIP_REQ 48-38
MC702a - NB_TCH_NOR_FR_ALLOC 48-39
MC702b - NB_TCH_NOR_HR_ALLOC 48-39
MC702c - NB_TCH_NOR_EFR_ALLOC 48-40
MC704a - NB_TCH_NOR_AMR_FR_ALLOC 48-40
MC704b - NB_TCH_NOR_AMR_HR_ALLOC 48-41
MC705 - NB_TCH_NOR_DATA_ALLOC 48-41
MC706 - NB_EGSM_MS_ACCESS_EXCEPT_LU 48-42
MC718a - NB_TCH_FR_ASS_COMP 48-42
MC718b - NB_TCH_HR_ASS_COMP 48-43
MC718c - NB_TCH_EFR_ASS_COMP 48-43
MC718d - NB_TCH_FR_AMR_ASS_COMP 48-44
MC718e - NB_TCH_HR_AMR_ASS_COMP 48-45
MC718f - NB_TCH_AMR_WB_GMSK_ASS_COMP 48-45
MC718i - NB_TCH_ATDM_REP 48-46
MC718j - NB_TCH_AIP_REP 48-46

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-33
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage Overview
Resource Allocation & Management
....................................................................................................................................................................................................................................

MC922h - TIME_3G_HOReject_HL 48-47


MC927a - NB_DTM_UL_TCH_ASS_ATPT 48-47
MC927b - NB_DTM_DL_TCH_ASS_ATPT 48-48
MC927c - NB_DTM_UL_PACKET_ASS_ATPT 48-48
MC927d - NB_DTM_DL_PACKET_ASS_ATPT 48-49
MC927e - NB_DTM_UL_TCH_ASS_EXEC_FAIL_RADIO 48-49
MC927f - NB_DTM_DL_TCH_ASS_EXEC_FAIL_RADIO 48-50
MC929h - TIME_4G_HOReject_HL 48-50
MC931 - NB_TCH_NOR_AMR_WB_GMSK_FR_ALLOC 48-51
MC932 - NB_TCH_AMR_WB_GMSK_REQ 48-51
MC951 - NB_TCH_A5_3_REQ 48-52
MC952 - NB_CIPHER_CMD_A5_3 48-52
MC953 - NB_SUCC_CIPHER_CMD_A5_3 48-53
MC954 - NB_TCH_A5_3_ASS 48-53
MC955 - NB_TCH_A5_3_ASS_NO_TRX 48-54
MC956 - NB_ASS_HO_CMD_A5_3_NO_TRX 48-55

MC701a - NB_TCH_FR_REQ
Descripton

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 Resource Allocation & Management

Sub Domain 2 Service


Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements

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

Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
48-34 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC701b - NB_TCH_DR_REQ
Resource Allocation & Management
....................................................................................................................................................................................................................................

MC701b - NB_TCH_DR_REQ
Descripton

Long Name NB_TCH_DR_REQ

Definition Number of TCH normal assignments requests from dual rate mobiles.
Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call with only GSM speech coding
algorithm version 1 full rate and GSM speech coding algorithm version 1 half rate allowed.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

Feature Name B7.1 counters improvements

MC701c - NB_TCH_DR_EFR_REQ
Descripton

Long Name NB_TCH_DR_EFR_REQ


Definition Number of TCH normal assignment requests from mobiles supporting FR, HR and EFR.
Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call with 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 Resource Allocation & Management

Sub Domain 2 Service

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-35
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC701d - NB_TCH_AMR_REQ
Resource Allocation & Management
....................................................................................................................................................................................................................................

MC701d - NB_TCH_AMR_REQ
Descripton

Long Name NB_TCH_AMR_REQ

Definition Number of TCH normal assignment requests from AMR mobiles.


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

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

Feature Name B7.1 counters improvements

MC701e - NB_TCH_DATA_REQ
Descripton

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 Resource Allocation & Management

Sub Domain 2 Service


Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

External Comment --
Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
48-36 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC701f - NB_TCH_FR_EFR_REQ
Resource Allocation & Management
....................................................................................................................................................................................................................................

MC701f - NB_TCH_FR_EFR_REQ
Descripton

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 Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call with only GSM speech coding
algorithm version 1 full rate and GSM speech coding algorithm version 2 full rate allowed.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

Feature Name B7.1 counters improvements

MC701g - NB_TCH_NO_FR_REQ
Descripton

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 Resource Allocation & Management

Sub Domain 2 Service


Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-37
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC701g - NB_TCH_NO_FR_REQ
Resource Allocation & Management
....................................................................................................................................................................................................................................

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).
Feature Name B7.1 counters improvements

MC701i - NB_TCH_ATDM_REQ
Descripton

Long Name NB_TCH_ATDM_REQ

Definition Number of TCH normal assignments requests for TDM only A user plane interface
Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC with TDM A interface only allowed in Codec
List (MSC Preferred)

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name AUPoIP A interface user plane over IP

MC701j - NB_TCH_AIP_REQ
Descripton

Long Name NB_TCH_AIP_REQ


Definition Number of TCH normal assignments requests for IP only A user plane interface

Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC with IP A interface only allowed in Codec List
(MSC Preferred)

Sub Domain 1 Resource Allocation & Management

Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements

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

....................................................................................................................................................................................................................................
48-38 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC701j - NB_TCH_AIP_REQ
Resource Allocation & Management
....................................................................................................................................................................................................................................

External Comment --

Feature Name AUPoIP A interface user plane over IP

MC702a - NB_TCH_NOR_FR_ALLOC
Descripton

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 Resource Allocation & Management


Sub Domain 2 Service
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name B7.1 counters improvements

MC702b - NB_TCH_NOR_HR_ALLOC
Descripton

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 Resource Allocation & Management

Sub Domain 2 Service

Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-39
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC702b - NB_TCH_NOR_HR_ALLOC
Resource Allocation & Management
....................................................................................................................................................................................................................................

External Comment --

Feature Name B7.1 counters improvements

MC702c - NB_TCH_NOR_EFR_ALLOC
Descripton

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 48.058 CHANNEL ACTIVATION/ MODE MODIFY about to be sent to the BTS, indicating a FR channel
with GSM speech coding algorithm version 2, not related to handover.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name B7.1 counters improvements

MC704a - NB_TCH_NOR_AMR_FR_ALLOC
Descripton

Long Name NB_TCH_NOR_AMR_FR_ALLOC


Definition Number of TCH normal assignment/mode modify in FR AMR 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 3, not related to handover.
Sub Domain 1 Resource Allocation & Management

Sub Domain 2 Service

Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements

....................................................................................................................................................................................................................................
48-40 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC704a - NB_TCH_NOR_AMR_FR_ALLOC
Resource Allocation & Management
....................................................................................................................................................................................................................................

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

External Comment --
Feature Name B7.1 counters improvements

MC704b - NB_TCH_NOR_AMR_HR_ALLOC
Descripton

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 48.058 CHANNEL ACTIVATION/ MODE MODIFY about to be sent to the BTS, indicating a HR channel
with GSM speech coding algorithm version 3, not related to handover.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements

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

Feature Name B7.1 counters improvements

MC705 - NB_TCH_NOR_DATA_ALLOC
Descripton

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 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 data call, not
related to handover.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-41
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC705 - NB_TCH_NOR_DATA_ALLOC
Resource Allocation & Management
....................................................................................................................................................................................................................................

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

External Comment --
Feature Name B7.1 counters improvements

MC706 - NB_EGSM_MS_ACCESS_EXCEPT_LU
Descripton

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 Resource Allocation & Management


Sub Domain 2 E-GSM

Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name E-GSM support

MC718a - NB_TCH_FR_ASS_COMP
Descripton

Long Name NB_TCH_FR_ASS_COMP


Definition Number of TCH normal assignment successes for speech calls with GSM speech full rate version 1 (GSM
FR) not involved in a handover procedure.
Trigger condition Sending of 48.008 ASSIGNMENT COMPLETE from the BSC to the MSC for a speech call with GSM
speech full rate version 1 (GSM FR) that is not involved in a handover procedure.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 --

Sub Domain 3 --

....................................................................................................................................................................................................................................
48-42 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC718a - NB_TCH_FR_ASS_COMP
Resource Allocation & Management
....................................................................................................................................................................................................................................

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

MC718b - NB_TCH_HR_ASS_COMP
Descripton

Long Name NB_TCH_HR_ASS_COMP


Definition Number of TCH normal assignment successes for speech calls with GSM speech half rate version 1 (GSM
HR) not involved in a handover procedure.
Trigger condition Sending of 48.008 ASSIGNMENT COMPLETE from the BSC to the MSC for a speech call with GSM
speech half rate version 1 (GSM HR) that is not involved in a handover procedure.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements

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

Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

MC718c - NB_TCH_EFR_ASS_COMP
Descripton

Long Name NB_TCH_EFR_ASS_COMP

Definition Number of TCH normal assignment successes for speech calls with GSM speech full rate version 2 (GSM
EFR) not involved in a handover procedure.

Trigger condition Sending of 48.008 ASSIGNMENT COMPLETE from the BSC to the MSC for a speech call with GSM
speech full rate version 2 (GSM EFR) that is not involved in a handover procedure.
Sub Domain 1 Resource Allocation & Management

Sub Domain 2 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-43
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC718c - NB_TCH_EFR_ASS_COMP
Resource Allocation & Management
....................................................................................................................................................................................................................................

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

MC718d - NB_TCH_FR_AMR_ASS_COMP
Descripton

Long Name NB_TCH_FR_AMR_ASS_COMP


Definition Number of TCH normal assignment successes for speech calls with GSM speech full rate version 3 (FR
AMR) not involved in a handover procedure.
Trigger condition Sending of 48.008 ASSIGNMENT COMPLETE from the BSC to the MSC for a speech call with GSM
speech full rate version 3 (FR AMR) that is not involved in a handover procedure.
Sub Domain 1 Resource Allocation & Management

Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

....................................................................................................................................................................................................................................
48-44 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC718e - NB_TCH_HR_AMR_ASS_COMP
Resource Allocation & Management
....................................................................................................................................................................................................................................

MC718e - NB_TCH_HR_AMR_ASS_COMP
Descripton

Long Name NB_TCH_HR_AMR_ASS_COMP

Definition Number of TCH normal assignment successes for speech calls with GSM speech half rate version 3 (HR
AMR) not involved in a handover procedure.
Trigger condition Sending of 48.008 ASSIGNMENT COMPLETE from the BSC to the MSC for a speech call with GSM
speech half rate version 3 (HR AMR) that is not involved in a handover procedure.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 --

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

MC718f - NB_TCH_AMR_WB_GMSK_ASS_COMP
Descripton

Long Name NB_TCH_AMR_WB_GMSK_ASS_COMP


Definition Number of TCH normal assignment successes for speech calls with GSM speech full rate version 5 (FR
AMR-WB) not involved in a handover procedure.
Trigger condition Sending of 48.008 ASSIGNMENT COMPLETE from the BSC to the MSC for a speech call with GSM
speech full rate version 5 (FR AMR-WB) that is not involved in a handover procedure.

Sub Domain 1 Resource Allocation & Management

Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements

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

Feature Name Counters on ASSIGNMENT/HANDOVER COMPLETE messages based on codecs and Repeated ACCH
activation.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-45
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC718i - NB_TCH_ATDM_REP
Resource Allocation & Management
....................................................................................................................................................................................................................................

MC718i - NB_TCH_ATDM_REP
Descripton

Long Name NB_TCH_ATDM_REP

Definition Number of TCH normal assignments successes for TDM A user plane interface
Trigger condition Sending of 48.008 ASSIGNMENT COMPLETE from the BSC to the MSC with TDM A interface in Speech
Codec (Chosen)

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

Feature Name AUPoIP A interface user plane over IP

MC718j - NB_TCH_AIP_REP
Descripton

Long Name NB_TCH_AIP_REP


Definition Number of TCH normal assignments successes for IP A user plane interface
Trigger condition Sending of 48.008 ASSIGNMENT COMPLETE from the BSC to the MSC with IP A interface in Speech
Codec (Chosen)
Sub Domain 1 Resource Allocation & Management

Sub Domain 2 --
Sub Domain 3 --

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
48-46 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC922h - TIME_3G_HOReject_HL
Resource Allocation & Management
....................................................................................................................................................................................................................................

MC922h - TIME_3G_HOReject_HL
Descripton

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 Resource Allocation & Management


Sub Domain 2 --

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

Feature Name 2G/3G inter-operability

MC927a - NB_DTM_UL_TCH_ASS_ATPT
Descripton

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 Resource Allocation & Management

Sub Domain 2 DTM Assignment


Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements

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

Feature Name Dual Transfer Mode (DTM)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-47
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC927b - NB_DTM_DL_TCH_ASS_ATPT
Resource Allocation & Management
....................................................................................................................................................................................................................................

MC927b - NB_DTM_DL_TCH_ASS_ATPT
Descripton

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 Resource Allocation & Management


Sub Domain 2 DTM Assignment

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

Feature Name Dual Transfer Mode (DTM)

MC927c - NB_DTM_UL_PACKET_ASS_ATPT
Descripton

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 Resource Allocation & Management

Sub Domain 2 DTM Assignment


Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements

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

Feature Name Dual Transfer Mode (DTM)

....................................................................................................................................................................................................................................
48-48 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC927d - NB_DTM_DL_PACKET_ASS_ATPT
Resource Allocation & Management
....................................................................................................................................................................................................................................

MC927d - NB_DTM_DL_PACKET_ASS_ATPT
Descripton

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 Resource Allocation & Management


Sub Domain 2 DTM Assignment

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

Feature Name Dual Transfer Mode (DTM)

MC927e - NB_DTM_UL_TCH_ASS_EXEC_FAIL_RADIO
Descripton

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 Resource Allocation & Management


Sub Domain 2 DTM Assignment
Sub Domain 3 --

Measured Object Common cell

Type Name Overview measurements


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

External Comment --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-49
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC927e - NB_DTM_UL_TCH_ASS_EXEC_FAIL_RADIO
Resource Allocation & Management
....................................................................................................................................................................................................................................

Feature Name Dual Transfer Mode (DTM)

MC927f - NB_DTM_DL_TCH_ASS_EXEC_FAIL_RADIO
Descripton

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 Resource Allocation & Management
Sub Domain 2 DTM Assignment
Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name Dual Transfer Mode (DTM)

MC929h - TIME_4G_HOReject_HL
Descripton

Long Name TIME_4G_HOReject_HL

Definition Cumulative time (in seconds) during which the Cell is in 4G high load state.
Trigger condition Whenever the LTE_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_LTE_REJECT <
100%.

Sub Domain 1 Resource Allocation & Management

Sub Domain 2 --
Sub Domain 3 --

Measured Object Common cell

....................................................................................................................................................................................................................................
48-50 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC929h - TIME_4G_HOReject_HL
Resource Allocation & Management
....................................................................................................................................................................................................................................

Type Name Overview measurements

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

Feature Name LTE to GSM handover (SRVCC)

MC931 - NB_TCH_NOR_AMR_WB_GMSK_FR_ALLOC
Descripton

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 48.058 CHANNEL ACTIVATION/ MODE MODIFY about to be sent to the BTS, indicating a FR channel
with GSM speech coding algorithm version 5, not related to handover.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name AMR WB speech codec GMSK

MC932 - NB_TCH_AMR_WB_GMSK_REQ
Descripton

Long Name NB_TCH_AMR_WB_GMSK_REQ


Definition Number of TCH normal assignment requests from AMR WB GMSK mobiles

Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call with GSM speech coding
algorithm version 5 full rate allowed.
Sub Domain 1 Resource Allocation & Management

Sub Domain 2 Service

Sub Domain 3 --
Measured Object Common cell

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-51
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC932 - NB_TCH_AMR_WB_GMSK_REQ
Resource Allocation & Management
....................................................................................................................................................................................................................................

Type Name Overview measurements

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

Feature Name AMR WB speech codec GMSK

MC951 - NB_TCH_A5_3_REQ
Descripton

Long Name NB_TCH_A5_3_REQ

Definition Number of TCH normal assignment requests for A5/3 capable mobiles.
Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC:
- either the Classmark 2 IE is present and indicates that the MS supports A5/3 algorithm,
- or the Classmark 2 IE is not present but was received earlier from the MS, stored by the BSC and indicates
that the MS supports A5/3 algorithm.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service

Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name Support of A5/3

MC952 - NB_CIPHER_CMD_A5_3
Descripton

Long Name NB_CIPHER_CMD_A5_3

Definition Number of Cipher Mode Command messages received from the MSC, allowing A5/3 for a MS supporting
A5/3 in a cell where A5/3 is enabled

Trigger condition Receipt of 48.008 CIPHER MODE COMMAND from the MSC with encryption information indicating that
A5/3 usage is allowed for a MS A5/3 capable, in a cell where A5/3 is enabled.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service

Sub Domain 3 --

....................................................................................................................................................................................................................................
48-52 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC952 - NB_CIPHER_CMD_A5_3
Resource Allocation & Management
....................................................................................................................................................................................................................................

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name Support of A5/3

MC953 - NB_SUCC_CIPHER_CMD_A5_3
Descripton

Long Name NB_SUCC_CIPHER_CMD_A5_3


Definition Number of successful Cipher Mode Command messages for usage of A5/3
Trigger condition Receipt of 44.018 CIPHERING MODE COMPLETE from the MS, subsequently to a 44.018 CIPHERING
MODE COMMAND with cipher mode setting indicating usage of A5/3 usage.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name Support of A5/3

MC954 - NB_TCH_A5_3_ASS
Descripton

Long Name NB_TCH_A5_3_ASS


Definition Number of 44.018 ASSIGNMENT COMMAND or HANDOVER COMMAND sent to a MS requiring the
usage of A5/3 ciphering algorithm

Trigger condition Incremented by 1 each time the BSC sends


1) if the cell is a serving cell: a 44.018 ASSIGNMENT COMMAND message with the target ciphering
algorithm to be used by the MS for this call set to A5/3 (whatever the ciphering algorithm used before);
2) if the cell is the target cell of an intra-cell handover, or inter-cell handover, or external handover or
internal/external directed retry: or a 44.018 HANDOVER COMMAND message via the serving cell with
the target ciphering algorithm to be used by the MS for this call in the target cell set to A5/3 (whatever the
ciphering algorithm used before).

Sub Domain 1 Resource Allocation & Management

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-53
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC954 - NB_TCH_A5_3_ASS
Resource Allocation & Management
....................................................................................................................................................................................................................................

Sub Domain 2 Service

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name Support of A5/3

MC955 - NB_TCH_A5_3_ASS_NO_TRX
Descripton

Long Name NB_TCH_A5_3_ASS_NO_TRX


Definition Number of unsuccessful A5/3 cipher mode command due to non A5/3 support on the TRX used for the MS
allocation.
Trigger condition Incremented by 1 each time a CIPHER MODE REJECT message is sent with cause "Ciphering algorithm
not supported" in response to a CIPHER MODE COMMAND indicating A5/3 as permitted algorithm but
the TRX on which the MS is allocated does not support A5/3.
Sub Domain 1 Resource Allocation & Management

Sub Domain 2 Service


Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name Support of A5/3

....................................................................................................................................................................................................................................
48-54 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC956 - NB_ASS_HO_CMD_A5_3_NO_TRX
Resource Allocation & Management
....................................................................................................................................................................................................................................

MC956 - NB_ASS_HO_CMD_A5_3_NO_TRX
Descripton

Long Name NB_ASS_HO_CMD_A5_3_NO_TRX

Definition Number of 44.018 ASSIGNMENT COMMAND or HANDOVER COMMAND sent without A5/3 usage,
because the TRX for the MS allocation does not support A5/3.
Trigger condition Incremented by 1 each time the BSC sends
1) if the cell is a serving cell: a 44.018 ASSIGNMENT COMMAND message to an A5/3 capable MS
without requiring the usage of A5/3, because the TRX on which the MS is being allocated in the serving cell
does not support A5/3;
2) if the cell is the target cell of an intra-cell handover, or inter-cell handover, or external handover or
internal/external directed retry: or a 44.018 HANDOVER COMMAND message to an A5/3 capable MS via
the serving cell, without requiring the usage of A5/3, because the TRX on which the MS will be allocated in
the target cell does not support A5/3.

Sub Domain 1 Resource Allocation & Management


Sub Domain 2 Service
Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Support of A5/3

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 48-55
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource Availability & Usage MC956 - NB_ASS_HO_CMD_A5_3_NO_TRX

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
48-56 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
49 Sustainable & safety
49

Dynamic power allocation

Overview
Purpose
This section contains Dynamic power allocation parameters.

Contents

MC1208 - TIME_PWR_RED_8PSK_1 49-2


MC1209 - TIME_PWR_RED_8PSK_2 49-2
MC1210 - TIME_PWR_RED_8PSK_3 49-3
MC1211 - TIME_PWR_RED_8PSK_4 49-4
MC1212 - TIME_PWR_RED_GMSK_1 49-4
MC1213 - TIME_PWR_RED_GMSK_2 49-5
MC1214 - TIME_PWR_RED_GMSK_3 49-6
MC1215 - TIME_PWR_RED_GMSK_4 49-6
MC1216 - TIME_PWR_RED_DEFENSE_1 49-7
MC1217 - TIME_PWR_RED_DEFENSE_2 49-8
MC1218 - TIME_PWR_RED_DEFENSE_3 49-9
MC1219 - TIME_PWR_RED_DEFENSE_4 49-9
MC1220 - TIME_8PSK_BURST_TRANSMISSION 49-10
MC1221 - TIME_GMSK_BURST_TRANSMISSION 49-11
MC1222 - TIME_DEFENSE_BURST_TRANSMISSION 49-11

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 49-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety MC1208 - TIME_PWR_RED_8PSK_1
Dynamic power allocation
....................................................................................................................................................................................................................................

MC1208 - TIME_PWR_RED_8PSK_1
Descripton

Long Name TIME_PWR_RED_8PSK_1

Definition Cumulated time during which a transmission power reduction of 1dB is applied by the BTS on the downlink
8-PSK bursts of the TRX due to dynamic power allocation. Only the bursts which are not transmitted on the
BCCH frequency of the cell are considered.
This counter can only be strictly positive if the TRX is supported by a MC module for which dynamic
power allocation is applied.
This counter corresponds to the group 1 for the power reduction algorithm of the dynamic power allocation
handling in the BTS.
This counter will always be equal to 0 if the TRX is supported by a G3, G4 or G5 (twin) module.

Trigger condition A transmission power reduction of 1dB is applied by the BTS on the downlink 8-PSK bursts of the TRX
Sub Domain 1 Dynamic power allocation

Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX


Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Support of Multi Carrier Modules

MC1209 - TIME_PWR_RED_8PSK_2
Descripton

Long Name TIME_PWR_RED_8PSK_2

Definition Cumulated time during which a transmission power reduction of 2dB is applied by the BTS on the downlink
8-PSK bursts of the TRX due to dynamic power allocation. Only the bursts which are not transmitted on the
BCCH frequency of the cell are considered.
This counter can only be strictly positive if the TRX is supported by a MC module for which dynamic
power allocation is applied.
This counter corresponds to the group 1 for the power reduction algorithm of the dynamic power allocation
handling in the BTS.
This counter will always be equal to 0 if the TRX is supported by a G3, G4 or G5 (twin) module.

Trigger condition A transmission power reduction of 2dB is applied by the BTS on the downlink 8-PSK bursts of the TRX.
Sub Domain 1 Dynamic power allocation

Sub Domain 2 --
Sub Domain 3 --

....................................................................................................................................................................................................................................
49-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety MC1209 - TIME_PWR_RED_8PSK_2
Dynamic power allocation
....................................................................................................................................................................................................................................

Measured Object TRX

Type Name Overview measurements


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

External Comment --
Feature Name Support of Multi Carrier Modules

MC1210 - TIME_PWR_RED_8PSK_3
Descripton

Long Name TIME_PWR_RED_8PSK_3


Definition Cumulated time during which a transmission power reduction of 3dB is applied by the BTS on the downlink
8-PSK bursts of the TRX due to dynamic power allocation. Only the bursts which are not transmitted on the
BCCH frequency of the cell are considered.
This counter can only be strictly positive if the TRX is supported by a MC module for which dynamic
power allocation is applied.
This counter corresponds to the group 1 for the power reduction algorithm of the dynamic power allocation
handling in the BTS.
This counter will always be equal to 0 if the TRX is supported by a G3, G4 or G5 (twin) module.
Trigger condition A transmission power reduction of 3dB is applied by the BTS on the downlink 8-PSK bursts of the TRX.
Sub Domain 1 Dynamic power allocation

Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX


Type Name Overview measurements

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

External Comment --
Feature Name Support of Multi Carrier Modules

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 49-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety MC1211 - TIME_PWR_RED_8PSK_4
Dynamic power allocation
....................................................................................................................................................................................................................................

MC1211 - TIME_PWR_RED_8PSK_4
Descripton

Long Name TIME_PWR_RED_8PSK_4

Definition Cumulated time during which a transmission power reduction strictly higher than 3dB is applied by the BTS
on the downlink 8-PSK bursts of the TRX due to dynamic power allocation. Only the bursts which are not
transmitted on the BCCH frequency of the cell are considered.
This counter can only be strictly positive if the TRX is supported by a MC module for which dynamic
power allocation is applied.
This counter corresponds to the group 1 for the power reduction algorithm of the dynamic power allocation
handling in the BTS.
This counter will always be equal to 0 if the TRX is supported by a G3, G4 or G5 (twin) module.

Trigger condition A transmission power reduction strictly higher than 3dB is applied by the BTS on the downlink 8-PSK
bursts of the TRX.
Sub Domain 1 Dynamic power allocation

Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX


Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Support of Multi Carrier Modules

MC1212 - TIME_PWR_RED_GMSK_1
Descripton

Long Name TIME_PWR_RED_GMSK_1


Definition Cumulated time during which a transmission power reduction of 1dB is applied by the BTS on the downlink
power-controlled GMSK/AQPSK bursts of the TRX due to dynamic power allocation.
The only downlink bursts which are concerned are the ones linked to TCHs, TBFs (in GMSK mode or
AQPSK) which are not transmitted on the BCCH frequency of the cell. AQPSK bursts transmitting a
signalling frame for at least one of the two VAMOS sub-channels (either in the whole burst or in a half
burst) are not concerned
This counter can only be strictly positive if the TRX is supported by a MC module for which dynamic
power allocation is applied.
This counter corresponds to the group 2 for the power reduction algorithm of the dynamic power allocation
handling in the BTS.
This counter will always be equal to 0 if the TRX is supported by a G3, G4 or G5 (twin) module.

....................................................................................................................................................................................................................................
49-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety MC1212 - TIME_PWR_RED_GMSK_1
Dynamic power allocation
....................................................................................................................................................................................................................................

Trigger condition A transmission power reduction of 1dB is applied by the BTS on the downlink GMSK/AQPSK bursts (only
the ones linked to TCHs, TBFs ) of the TRX.

Sub Domain 1 Dynamic power allocation


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name Overview measurements


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

External Comment --

Feature Name Support of Multi Carrier Modules

MC1213 - TIME_PWR_RED_GMSK_2
Descripton

Long Name TIME_PWR_RED_GMSK_2


Definition Cumulated time during which a transmission power reduction of 2dB is applied by the BTS on the downlink
power-controlled GMSK/AQPSK bursts of the TRX due to dynamic power allocation.
The only downlink bursts which are concerned are the ones linked to TCHs, TBFs (in GMSK mode or
AQPSK), and which are not transmitted on the BCCH frequency of the cell. AQPSK bursts transmitting a
signalling frame for at least one of the two VAMOS sub-channels (either in the whole burst or in a half
burst) are not concerned.
This counter can only be strictly positive if the TRX is supported by a MC module for which dynamic
power allocation is applied.
This counter corresponds to the group 2 for the power reduction algorithm of the dynamic power allocation
handling in the BTS.
This counter will always be equal to 0 if the TRX is supported by a G3, G4 or G5 (twin) module.
Trigger condition A transmission power reduction of 2dB is applied by the BTS on the downlink GMSK/AQPSK bursts (only
the ones linked to TCHs, TBFs ) of the TRX.
Sub Domain 1 Dynamic power allocation

Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX

Type Name Overview measurements


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

Feature Name Support of Multi Carrier Modules

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 49-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety MC1214 - TIME_PWR_RED_GMSK_3
Dynamic power allocation
....................................................................................................................................................................................................................................

MC1214 - TIME_PWR_RED_GMSK_3
Descripton

Long Name TIME_PWR_RED_GMSK_3

Definition Cumulated time during which a transmission power reduction of 3dB is applied by the BTS on the downlink
power-controlled GMSK/AQPSK bursts of the TRX due to dynamic power allocation.
The only downlink bursts which are concerned are the ones linked to TCHs, TBFs (in GMSK mode or
AQPSK), and which are not transmitted on the BCCH frequency of the cell. AQPSK bursts transmitting a
signalling frame for at least one of the two VAMOS sub-channels (either in the whole burst or in a half
burst) are not concerned.
This counter can only be strictly positive if the TRX is supported by a MC module for which dynamic
power allocation is applied.
This counter corresponds to the group 2 for the power reduction algorithm of the dynamic power allocation
handling in the BTS.
This counter will always be equal to 0 if the TRX is supported by a G3, G4 or G5 (twin) module.

Trigger condition A transmission power reduction of 3dB is applied by the BTS on the downlink GMSK/AQPSK bursts (only
the ones linked to TCHs, TBFs ) of the TRX.

Sub Domain 1 Dynamic power allocation


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Support of Multi Carrier Modules

MC1215 - TIME_PWR_RED_GMSK_4
Descripton

Long Name TIME_PWR_RED_GMSK_4

....................................................................................................................................................................................................................................
49-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety MC1215 - TIME_PWR_RED_GMSK_4
Dynamic power allocation
....................................................................................................................................................................................................................................

Definition Cumulated time during which a transmission power reduction strictly higher than 3dB is applied by the BTS
on the downlink power-controlled GMSK/AQPSK bursts of the TRX due to dynamic power allocation.
The only downlink bursts which are concerned are the ones linked to TCHs, TBFs (in GMSK mode or
AQPSK), and which are not transmitted on the BCCH frequency of the cell. AQPSK bursts transmitting a
signalling frame for at least one of the two VAMOS sub-channels (either in the whole burst or in a half
burst) are not concerned.
This counter can only be strictly positive if the TRX is supported by a MC module for which dynamic
power allocation is applied.
This counter corresponds to the group 2 for the power reduction algorithm of the dynamic power allocation
handling in the BTS.
This counter will always be equal to 0 if the TRX is supported by a G3, G4 or G5 (twin) module.
Trigger condition A transmission power reduction strictly higher than 3dB is applied by the BTS on the downlink
GMSK/AQPSK bursts (only the ones linked to TCHs, TBFs ) of the TRX.
Sub Domain 1 Dynamic power allocation

Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX


Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Support of Multi Carrier Modules

MC1216 - TIME_PWR_RED_DEFENSE_1
Descripton

Long Name TIME_PWR_RED_DEFENSE_1


Definition Cumulated time during which a transmission power reduction of 1dB is applied by the BTS on the downlink
"control" bursts of the TRX due to dynamic power allocation.
The only downlink bursts which are concerned are the ones corresponding either to signalling non-BCCH
bursts (SDCCH/FACCH/SACCH) or either bursts sent with the BCH frequency i.e. not already counted in
the TIME_PWR_RED_8PSK_1 and TIME_PWR_RED_GMSK_1 counters
This counter can only be strictly positive if the TRX is supported by a MC module for which dynamic
power allocation is applied.
This counter corresponds to the group 3 and group 4 (defense step) for the power reduction algorithm of the
dynamic power allocation handling in the BTS.
This counter will always be equal to 0 if the TRX is supported by a G3, G4 or G5 (twin) module.
Trigger condition A transmission power reduction of 1dB is applied by the BTS on the downlink bursts (not already counted
in the TIME_PWR_RED_8PSK_1 and TIME_PWR_RED_GMSK_1 counters) of the TRX.

Sub Domain 1 Dynamic power allocation


Sub Domain 2 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 49-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety MC1216 - TIME_PWR_RED_DEFENSE_1
Dynamic power allocation
....................................................................................................................................................................................................................................

Sub Domain 3 --

Measured Object TRX


Type Name Overview measurements

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

Feature Name Support of Multi Carrier Modules

MC1217 - TIME_PWR_RED_DEFENSE_2
Descripton

Long Name TIME_PWR_RED_DEFENSE_2


Definition Cumulated time during which a transmission power reduction of 2dB is applied by the BTS on the downlink
"control" bursts of the TRX due to dynamic power allocation.
The only downlink bursts which are concerned are the ones corresponding either to signalling non-BCCH
bursts (SDCCH/FACCH/SACCH) or either bursts sent with the BCH frequency i.e. not already counted in
the TIME_PWR_RED_8PSK_2 and TIME_PWR_RED_GMSK_2 counters
This counter can only be strictly positive if the TRX is supported by a MC module for which dynamic
power allocation is applied.
This counter corresponds to the group 3 and group 4 (defense step) for the power reduction algorithm of the
dynamic power allocation handling in the BTS.
This counter will always be equal to 0 if the TRX is supported by a G3, G4 or G5 (twin) module.
Trigger condition A transmission power reduction of 2dB is applied by the BTS on the downlink bursts (not already counted
in the TIME_PWR_RED_8PSK_2 and TIME_PWR_RED_GMSK_2 counters) of the TRX.
Sub Domain 1 Dynamic power allocation

Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX

Type Name Overview measurements


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

Feature Name Support of Multi Carrier Modules

....................................................................................................................................................................................................................................
49-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety MC1218 - TIME_PWR_RED_DEFENSE_3
Dynamic power allocation
....................................................................................................................................................................................................................................

MC1218 - TIME_PWR_RED_DEFENSE_3
Descripton

Long Name TIME_PWR_RED_DEFENSE_3

Definition Cumulated time during which a transmission power reduction of 3dB is applied by the BTS on the downlink
"control" bursts of the TRX due to dynamic power allocation.
The only downlink bursts which are concerned are the ones corresponding either to signalling non-BCCH
bursts (SDCCH/FACCH/SACCH) or either bursts sent with the BCH frequency i.e. not already counted in
the TIME_PWR_RED_8PSK_3 and TIME_PWR_RED_GMSK_3 counters
This counter can only be strictly positive if the TRX is supported by a MC module for which dynamic
power allocation is applied.
This counter corresponds to the group 3 and group 4 (defense step) for the power reduction algorithm of the
dynamic power allocation handling in the BTS.
This counter will always be equal to 0 if the TRX is supported by a G3, G4 or G5 (twin) module.
Trigger condition A transmission power reduction of 3dB is applied by the BTS on the downlink bursts (not already counted
in the TIME_PWR_RED_8PSK_3 and TIME_PWR_RED_GMSK_3 counters) of the TRX.
Sub Domain 1 Dynamic power allocation
Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Support of Multi Carrier Modules

MC1219 - TIME_PWR_RED_DEFENSE_4
Descripton

Long Name TIME_PWR_RED_DEFENSE_4

Definition Cumulated time during which a transmission power reduction strictly higher than 3dB is applied by the BTS
on the downlink "control" bursts of the TRX due to dynamic power allocation.
The only downlink bursts which are concerned are the ones corresponding either to signalling non-BCCH
bursts (SDCCH/FACCH/SACCH) or either bursts sent with the BCH frequency i.e. not already counted in
the TIME_PWR_RED_8PSK_4 and TIME_PWR_RED_GMSK_4 counters
This counter can only be strictly positive if the TRX is supported by a MC module for which dynamic
power allocation is applied.
This counter corresponds to the group 3 and group 4 (defense step) for the power reduction algorithm of the
dynamic power allocation handling in the BTS.
This counter will always be equal to 0 if the TRX is supported by a G3, G4 or G5 (twin) module.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 49-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety MC1219 - TIME_PWR_RED_DEFENSE_4
Dynamic power allocation
....................................................................................................................................................................................................................................

Trigger condition A transmission power reduction strictly higher than 3dB is applied by the BTS on the downlink bursts (not
already counted in the TIME_PWR_RED_8PSK_4 and TIME_PWR_RED_GMSK_4 counters) of the TRX.

Sub Domain 1 Dynamic power allocation


Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name Overview measurements


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

External Comment --

Feature Name Support of Multi Carrier Modules

MC1220 - TIME_8PSK_BURST_TRANSMISSION
Descripton

Long Name TIME_8PSK_BURST_TRANSMISSION


Definition Cumulated time during which downlink 8-PSK bursts need to be transmitted on the TRX. Only the bursts
which are not transmitted on the BCCH frequency of the cell are considered.This counter will always be
equal to 0 if the TRX is supported by a G3, G4 or G5 (twin) module.

Trigger condition Downlink 8-PSK burst is transmitted on the TRX.


Sub Domain 1 Dynamic power allocation

Sub Domain 2 --
Sub Domain 3 --
Measured Object TRX

Type Name Overview measurements


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

External Comment --
Feature Name Support of Multi Carrier Modules

....................................................................................................................................................................................................................................
49-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety MC1221 - TIME_GMSK_BURST_TRANSMISSION
Dynamic power allocation
....................................................................................................................................................................................................................................

MC1221 - TIME_GMSK_BURST_TRANSMISSION
Descripton

Long Name TIME_GMSK_BURST_TRANSMISSION

Definition Cumulated time during which downlink power-controlled GMSK/AQPSK bursts need to be transmitted on
the TRX.
The only downlink bursts which are concerned are the ones linked to TCHs, TBFs (in GMSK mode or
AQPSK), and which are not transmitted on the BCCH frequency of the cell. AQPSK bursts transmitting a
signalling frame for at least one of the two VAMOS sub-channels (either in the whole burst or in a half
burst) are not concerned. This counter will always be equal to 0 if the TRX is supported by a G3, G4 or G5
(twin) module.

Trigger condition Downlink power-controlled GMSK/AQPSK burst linked to TCHs, TBFs (in GMSK/AQPSK mode) is
transmitted on the TRX.
Sub Domain 1 Dynamic power allocation

Sub Domain 2 --
Sub Domain 3 --
Measured Object TRX

Type Name Overview measurements


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

External Comment --
Feature Name Support of Multi Carrier Modules

MC1222 - TIME_DEFENSE_BURST_TRANSMISSION
Descripton

Long Name TIME_DEFENSE_BURST_TRANSMISSION


Definition Cumulated time during which downlink "control" bursts need to be transmitted on the TRX.
The only downlink bursts which are concerned are the ones not already counted in the TIME_8PSK_BURST_
TRANSMISSION and TIME_GMSK_BURST_TRANSMISSION counters corresponding either to
signalling non-BCCH bursts (SDCCH/FACCH/SACCH) or either bursts sent with the BCH frequency. This
counter will always be equal to 0 if the TRX is supported by a G3, G4 or G5 (twin) module.
Trigger condition Downlink burst not already counted in the TIME_8PSK_BURST_TRANSMISSION and TIME_GMSK_
BURST_TRANSMISSION counters is transmitted on the TRX.
Sub Domain 1 Dynamic power allocation

Sub Domain 2 --
Sub Domain 3 --

Measured Object TRX


Type Name Overview measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 49-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety MC1222 - TIME_DEFENSE_BURST_TRANSMISSION
Dynamic power allocation
....................................................................................................................................................................................................................................

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

External Comment --
Feature Name Support of Multi Carrier Modules

....................................................................................................................................................................................................................................
49-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety Overview
Power saving
....................................................................................................................................................................................................................................

Power saving

Overview
Purpose
This section contains Power saving parameters.

Contents

MC1201 - TIME_PA_BIAS_ON_TRX 49-13


MC957 - TIME_TS_BUSY 49-14
MC958 - TIME_PA_BIAS_ON 49-15

MC1201 - TIME_PA_BIAS_ON_TRX
Descripton

Long Name TIME_PA_BIAS_ON_TRX


Definition Cumulated time during which the PA bias is "on" or partially "on" on a given TRX.
Trigger condition Sum of all periods during which the PA bias is "on" or partially "on" on a given TRX, computed as follows:
[ 1.0 * number of bursts where the PA bias of the TRX is "on"
+ 0.1 * number of transitions "off -> on" for the PA bias of the TRX
+ 0.1 * number of transitions "on -> off -> on" for the PA bias of the TRX ] * 0.577ms.
The number of transitions "on -> off" for the PA bias of the TRX is not taken into account in the above
formula because the PA bias is switched off immediately after an active TS (when possible) and because the
time to switch off the PA bias is nearly 0 TS (<< 0.1 TS).
The above formula is valid and applicable to all the TRE generations: G3, G4, G5 and MC modules. On G3,
G4 and G5 modules, this counter is valid whether the "Dynamic power saving DPS" feature (cf. the
EN_POWER_SAVING parameter) is enabled or disabled. If it is disabled, then this counter will be equal to
the total reporting time (as if the PA bias was always "on" on the concerned TRX). Because the "Dynamic
power saving DPS" feature is not directly applicable on MC modules, this counter will be set to its
maximum value when computed on TRXs belonging to MC modules (i.e. to the total reporting time, as if
the PA bias was
always "on" on the concerned TRX(s)).
Sub Domain 1 Power saving

Sub Domain 2 --

Sub Domain 3 --
Measured Object TRX

Type Name Overview measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 49-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety MC1201 - TIME_PA_BIAS_ON_TRX
Power saving
....................................................................................................................................................................................................................................

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

External Comment The lower the counter value, the higher the power savings. However, that counter does not allow to exactly
derive the power savings in Watt.h brought by the "TRX dynamic power save" feature: indeed, the actual
power savings brought by the feature depend on various and complex factors like temperature effects,
variation of component (transistor) properties, etc...
As there are times where the PA bias of a TRX is switched on (for a whole burst) without DL transmission,
the TIME_TS_BUSY counter (at cell level) cannot be directly assimilated to the TIME_PA_BIAS_ON_
TRX counter. For example, for G4 and G5 TREs, the PA bias needs to be switched on from time to time
during idle timeslots in order to control the bias current.
However, TIME_TS_BUSY (at cell level) is obviously always less or equal to TIME_PA_BIAS_ON_TRX,
after having summed the TIME_PA_BIAS_ON_TRX values for the TRXs of a given cell.
Feature Name TRX dynamic power save

MC957 - TIME_TS_BUSY
Descripton

Long Name TIME_TS_BUSY


Definition Cumulated time during which TSs are "busy in DL" on the TRXs of the cell (i.e. a DL transmission is
needed on that TS, whatever the nature of the DL transmission: useful or dummy bursts).
Trigger condition Sum of all TSs (1 TS is about 0.577 ms) which are "busy in DL" on the TRXs of the cell, among all the
successive TDMA frames associated to those TRXs.This is applicable to all the TRE generations: G3, G4
,G5 and MC modules.
Sub Domain 1 Power saving

Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment As there are times where the PA bias of a TRX is switched on (for a whole burst) without DL transmission,
the TIME_TS_BUSY counter cannot be directly assimilated to the TIME_PA_BIAS_ON counter. For
example, for G4 and G5 TREs, the PA bias needs to be switched on from time to time during idle timeslots
in order to control the bias current.
However, TIME_TS_BUSY is obviously always less or equal to TIME_PA_BIAS_ON.

Feature Name TRX dynamic power save

....................................................................................................................................................................................................................................
49-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety MC958 - TIME_PA_BIAS_ON
Power saving
....................................................................................................................................................................................................................................

MC958 - TIME_PA_BIAS_ON
Descripton

Long Name TIME_PA_BIAS_ON

Definition Cumulated time during which the PA bias is "on" or partially "on" on the TRXs of the cell.
Trigger condition Sum of all periods during which the PA bias is "on" or partially "on" on the TRXs of the cell. For each TRX
of the cell, the counter shall be incremented by:
[ 1.0 * number of bursts where the PA bias of the TRX is "on"
+ 0.1 * number of transitions "off -> on" for the PA bias of the TRX
+ 0.1 * number of transitions "on -> off -> on" for the PA bias of the TRX ] * 0.577ms.
The number of transitions "on -> off" for the PA bias of the TRX is not taken into account in the above
formula because the PA bias is switched off immediately after an active TS (when possible) and because the
time to switch off the PA bias is nearly 0 TS (<< 0.1 TS).
The above formula is valid and applicable to all the TRE generations: G3, G4, G5 and MC modules. On G3,
G4 and G5 modules, this counter is valid whether the "Dynamic power saving DPS" feature (cf. the
EN_POWER_SAVING parameter) is enabled or disabled. If it is disabled, then this counter will be equal to
the total reporting time (as if the PA bias was always "on" on the concerned TRX(s)). Because the "Dynamic
power saving DPS" feature is not directly applicable on MC modules, this counter will be set to its
maximum value when computed on TRXs belonging to MC modules (i.e. to the total reporting time, as if
the PA bias was always "on" on the concerned TRX(s))
Sub Domain 1 Power saving
Sub Domain 2 TRX_TS
Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment The lower the counter value, the higher the power savings. However, that counter does not allow to exactly
derive the power savings in Watt.h brought by the "TRX dynamic power save" feature: indeed, the actual
power savings brought by the feature depend on various and complex factors like temperature effects,
variation of component (transistor) properties, etc...
As there are times where the PA bias of a TRX is switched on (for a whole burst) without DL transmission,
the TIME_TS_BUSY counter cannot be directly assimilated to the TIME_PA_BIAS_ON counter. For
example, for G4 and G5 TREs, the PA bias needs to be switched on from time to time during idle timeslots
in order to control the bias current.
However, TIME_TS_BUSY is obviously always less or equal to TIME_PA_BIAS_ON.

Feature Name TRX dynamic power save

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 49-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Sustainable & safety Overview
Temperature logging
....................................................................................................................................................................................................................................

Temperature logging

Overview
Purpose
This section contains Temperature logging parameters.

Contents

MC1200 - TRX_MAX_TEMPERATURE 49-16

MC1200 - TRX_MAX_TEMPERATURE
Descripton

Long Name TRX_MAX_TEMPERATURE


Definition Maximum temperature of the TRX during the accumulation period.
Trigger condition Reception of TRX_COUNTER_REPORT messages on RSL interface. If the counter reported by the BTS is
0xFF, this value is ignored. If the message is received out of delay, the counter value is ignored.

Sub Domain 1 Temperature logging


Sub Domain 2 --
Sub Domain 3 --
Measured Object TRX
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment Counter coded in Celcius degrees, with an offset of +100, so that:
0 to 99 represent negative temperatures from -100�C to -1�C
100 represent 0�C
101 to 254 represent positive temperatur from 1�C to 154�C
255 represent an invalid value (no measurement available over the whole accumulation period)

Feature Name Temperature Logging at OMC-R

....................................................................................................................................................................................................................................
49-16 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
50 Traffic Load
50

BSC

Overview
Purpose
This section contains BSC parameters.

Contents

MC1540 - BSCHA00 50-1


MC1541 - BSCHA01 50-2
MC926 - TCH_BLOCKING_OCCURENCES_BSC 50-3

MC1540 - BSCHA00
Descripton

Long Name BSCHA00


Definition The average load of CPU (OMCP) of BSC during a test period equal to 5 minutes.
At Accumulation Period (AP) expiry, the average value of all measurements obtained during the AP is taken
into account.
The value is rounded up or down to the nearest value with an accuracy of 0.1.
Note : The reported value shall then be divided by 10 so that the value that is taken into acount (integer and
decimal parts) is the correct one.The counter is available only when EN_SPECIFIC_PM is active.
Trigger condition BSC collects permanently (each second) OMCP load data. At the end of each polling period, the average
OMCP load is calculated.

Sub Domain 1 BSC


Sub Domain 2 --

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1540 - BSCHA00
BSC
....................................................................................................................................................................................................................................

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

Feature Name new Type B counter requirements

MC1541 - BSCHA01
Descripton

Long Name BSCHA01


Definition The max value of CPU (OMCP) load of BSC during a test period equal to 5 minutes.
At Accumulation Period (AP) expiry, the maximum value of all measurements obtained during the AP is
taken into account.
The value is rounded up or down to the nearest value with an accuracy of 0.1.
Note : The reported value shall then be divided by 10 so that the value that is taken into acount (integer and
decimal parts) is the correct one.The counter is available only when EN_SPECIFIC_PM is active.
Trigger condition BSC collects permanently (each second) OMCP load data. At the end of each polling period, the max
OMCP load is calculated

Sub Domain 1 BSC


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

Feature Name new Type B counter requirements

....................................................................................................................................................................................................................................
50-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC926 - TCH_BLOCKING_OCCURENCES_BSC
BSC
....................................................................................................................................................................................................................................

MC926 - TCH_BLOCKING_OCCURENCES_BSC
Descripton

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 Overview measurements


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

Feature Name BSC Evolution capacity improvement

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load Overview
Interface (Traffic Load)
....................................................................................................................................................................................................................................

Interface (Traffic Load)

Overview
Purpose
This section contains Interface (Traffic Load) parameters.

Contents

AIP10a - NB_BSC_SENT_UL_RTP_KBYTES 50-6


AIP10b - NB_BSC_SENT_UL_RTP_PACKETS 50-6
AIP10c - NB_BSC_SENT_UL_RTP_BYTES_MAX_MN 50-7
AIP10d - NB_BSC_RCVD_DL_RTP_KBYTES 50-7
AIP10e - NB_BSC_RCVD_DL_RTP_PACKETS 50-8
AIP20a - NB_BSC_SENT_UL_MUXRTP_KBYTES 50-8
AIP20b - NB_BSC_SENT_UL_MUXRTP_PACKETS 50-9
AIP20c - NB_BSC_SENT_UL_MUXRTP_BYTES_MAX_MN 50-9
AIP20d - NB_BSC_RCVD_DL_MUXRTP_KBYTES 50-10
AIP20e - NB_BSC_RCVD_DL_MUXRTP_PACKETS 50-10
AIP30a - NB_BSC_SENT_UL_RTCP_BYTES 50-11
AIP30b - NB_BSC_SENT_UL_RTCP_PACKETS 50-11
AIP30c - NB_BSC_SENT_UL_RTCP_BYTES_MAX_MN 50-12
AIP40 - NB_BSC_SENT_ALL_FLOW_BYTES_MAX_MN 50-12
MC1060 - NB_GSL_MSG_SENT 50-13
MC1061 - NB_GSL_MSG_DISCARDED 50-13
MC1062 - NB_GSL_MSG_RESENT 50-14
MC1063 - NB_GSL_MSG_RECEIVED 50-14
MC1064 - NB_GSL_BYTES_SENT 50-15
MC1065 - MAX_NB_GSL_BYTES_SENT 50-15
MC1066 - MAX_NB_GSL_MSG_SENT 50-16
MC1067 - AVERAGE_NB_MSG_IN_GSL_QUEUE 50-16
MC1101 - NB_ASPUP_TX 50-17
MC1102 - NB_ASPUP_RX 50-17

....................................................................................................................................................................................................................................
50-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load Overview
Interface (Traffic Load)
....................................................................................................................................................................................................................................

MC1103 - NB_ASPDOWN_TX 50-18


MC1104 - NB_ASPDOWN_RX 50-18
MC1105 - NB_ASPACTIVE_TX 50-19
MC1106 - NB_ASPACTIVE_RX 50-19
MC1107 - NB_ASPINACTIVE_TX 50-20
MC1108 - NB_ASPINACTIVE_RX 50-20
MC1109 - NB_BSC_SENT_SS7_IP_BYTES_Asig_IP 50-21
MC1110 - NB_BSC_SENT_SS7_IP_PACKETS_Asig_IP 50-21
MC1111 - NB_BSC_RESENT_SS7_IP_PACKETS_Asig_IP 50-22
MC1112 - NB_BSC_SENT_SS7_IP_BYTES_MAX_MN_Asig_IP 50-22
MC1114 - NB_N7_UNIT_DATA_SENT_Asig_IP 50-23
MC1115 - NB_N7_UNIT_DATA_REC_Asig_IP 50-23
MC1116 - NB_N7_CON_REQ_SENT_Asig_IP 50-24
MC1117 - NB_N7_CON_REQ_REC_Asig_IP 50-24
MC1118 - NB_N7_CON_CONF_SENT_Asig_IP 50-25
MC1119 - NB_N7_CON_CONF_REC_Asig_IP 50-25
MC1120 - NB_N7_CON_REF_SENT_Asig_IP 50-26
MC1121 - NB_N7_CON_REF_REC_Asig_IP 50-26
MC1700 - TIME_A_CHANNELS_MSC_BUSY 50-27
MC350 - NB_N7_CON_REQ 50-27
MC351 - NB_N7_CON_CONF 50-28
MC940 - NB_A_PAGING_MSG 50-28

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load AIP10a - NB_BSC_SENT_UL_RTP_KBYTES
Interface (Traffic Load)
....................................................................................................................................................................................................................................

AIP10a - NB_BSC_SENT_UL_RTP_KBYTES
Descripton

Long Name NB_BSC_SENT_UL_RTP_KBYTES

Definition Counts the number of payload Kilobytes of the UL RTP packets sent by the BSC toward a given MGW
IP@.
Trigger condition This counter is increased by the number of bytes of the payload of the UL RTP packet that is sent by the
BSC toward a given MGW IP@. At accumulation period the counter is calculated in Kilo (1000) bytes.The
payload of an RTP packet is defined as the RTP packet format without IP and UDP header.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A User Plane over IP (Traffic Load)

Sub Domain 3 --
Measured Object MGW_IP@
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name AUPoIP A interface user plane over IP

AIP10b - NB_BSC_SENT_UL_RTP_PACKETS
Descripton

Long Name NB_BSC_SENT_UL_RTP_PACKETS


Definition Counts the number of RTP packets sent by the BSC toward a given MGW IP@
Trigger condition This counter is increased by one each time an UL RTP packet is sent by the BSC toward a given MGW IP@.
Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 A User Plane over IP (Traffic Load)

Sub Domain 3 --
Measured Object MGW_IP@

Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
50-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load AIP10c - NB_BSC_SENT_UL_RTP_BYTES_MAX_MN
Interface (Traffic Load)
....................................................................................................................................................................................................................................

AIP10c - NB_BSC_SENT_UL_RTP_BYTES_MAX_MN
Descripton

Long Name NB_BSC_SENT_UL_RTP_BYTES_MAX_MN

Definition Counts the max number of payload bytes of the UL RTP packets sent by the BSC toward a given MGW IP@
in one minute during the granularity period of monitoring
Trigger condition Every minute, the number of payload bytes of the UL RTP packets sent by the BSC toward a given MGW
IP@ is counted. The maximum value obtained for 1 minute during the granularity period of monitoring is
reported. The payload of an RTP packet is defined as the RTP packet format without IP and UDP header.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A User Plane over IP (Traffic Load)

Sub Domain 3 --
Measured Object MGW_IP@
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name AUPoIP A interface user plane over IP

AIP10d - NB_BSC_RCVD_DL_RTP_KBYTES
Descripton

Long Name NB_BSC_RCVD_DL_RTP_KBYTES


Definition Counts the number of payload kilobytes of the DL RTP packets received by the BSC from a given MGW
IP@
Trigger condition This counter is increased by the number of bytes of the payload of the DL RTP packet that is received by the
BSC from a given MGW IP@. At accumulation period the counter is calculated in Kilo (1000) bytes.
The payload of an RTP packet is defined as the RTP packet format without IP and UDP header.

Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 A User Plane over IP (Traffic Load)


Sub Domain 3 --

Measured Object MGW_IP@

Type Name Overview measurements


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

Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load AIP10e - NB_BSC_RCVD_DL_RTP_PACKETS
Interface (Traffic Load)
....................................................................................................................................................................................................................................

AIP10e - NB_BSC_RCVD_DL_RTP_PACKETS
Descripton

Long Name NB_BSC_RCVD_DL_RTP_PACKETS

Definition Counts the number of RTP packets received by the BSC from a given MGW IP@
Trigger condition This counter is increased by one each time an DL RTP packet is received by the BSC from a given MGW
IP@

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A User Plane over IP (Traffic Load)

Sub Domain 3 --
Measured Object MGW_IP@

Type Name Overview measurements


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

Feature Name AUPoIP A interface user plane over IP

AIP20a - NB_BSC_SENT_UL_MUXRTP_KBYTES
Descripton

Long Name NB_BSC_SENT_UL_MUXRTP_KBYTES


Definition Counts the number of payload kilobytes of the UL MUXRTP packets sent by the BSC toward a given MGW
IP@
Trigger condition This counter is increased by the number of bytes of the payload of the UL MUXRTP packet that is sent by
the BSC toward a given MGW IP@. At accumulation period the counter is calculated in Kilo (1000)
bytes.The payload of a MUXRTP packet is defined as the RTP packet format without IP and UDP header.
Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 A User Plane over IP (Traffic Load)


Sub Domain 3 --

Measured Object MGW_IP@

Type Name Overview measurements


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

External Comment --
Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
50-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load AIP20b - NB_BSC_SENT_UL_MUXRTP_PACKETS
Interface (Traffic Load)
....................................................................................................................................................................................................................................

AIP20b - NB_BSC_SENT_UL_MUXRTP_PACKETS
Descripton

Long Name NB_BSC_SENT_UL_MUXRTP_PACKETS

Definition Counts the number of MUXRTP packets sent by the BSC toward a given MGW IP@
Trigger condition This counter is increased by one each time an UL MUXRTP packet is sent by the BSC to a given MGW
IP@.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A User Plane over IP (Traffic Load)

Sub Domain 3 --
Measured Object MGW_IP@

Type Name Overview measurements


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

Feature Name AUPoIP A interface user plane over IP

AIP20c - NB_BSC_SENT_UL_MUXRTP_BYTES_MAX_MN
Descripton

Long Name NB_BSC_SENT_UL_MUXRTP_BYTES_MAX_MN


Definition Counts the max number of payload bytes of the UL MUXRTP packets sent by the BSC toward a given
MGW IP@ in one minute during the granularity period of monitoring
Trigger condition Every minute, the number of payload bytes of the UL MUXRTP packets sent by the BSC toward a given
MGW IP@ is counted. The maximum value obtained for 1 minute during the granularity period of
monitoring is reported. The payload of a MUXRTP packet is defined as the MUXRTP packet format without
IP and UDP header.
Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 A User Plane over IP (Traffic Load)

Sub Domain 3 --
Measured Object MGW_IP@

Type Name Overview measurements


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

External Comment --
Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load AIP20d - NB_BSC_RCVD_DL_MUXRTP_KBYTES
Interface (Traffic Load)
....................................................................................................................................................................................................................................

AIP20d - NB_BSC_RCVD_DL_MUXRTP_KBYTES
Descripton

Long Name NB_BSC_RCVD_DL_MUXRTP_KBYTES

Definition Counts the number of payload kilobytes of the DL MUXRTP packets received by the BSC from a given
MGW IP@
Trigger condition This counter is increased by the number of bytes of the payload of the DL MUXRTP packet that is received
by the
BSC from a given MGW IP@. At accumulation period the counter is calculated in Kilo (1000) bytes.
The payload of a MUXRTP packet is defined as the RTP packet format without IP and UDP header.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A User Plane over IP (Traffic Load)

Sub Domain 3 --
Measured Object MGW_IP@

Type Name Overview measurements


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

External Comment --
Feature Name AUPoIP A interface user plane over IP

AIP20e - NB_BSC_RCVD_DL_MUXRTP_PACKETS
Descripton

Long Name NB_BSC_RCVD_DL_MUXRTP_PACKETS


Definition Counts the number of MUXRTP packets received by the BSC from a given MGW IP@
Trigger condition This counter is increased by one each time an DL MUXRTP packet is received by the BSC from a given
MGW IP@

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A User Plane over IP (Traffic Load)

Sub Domain 3 --

Measured Object MGW_IP@


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

External Comment --

Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
50-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load AIP30a - NB_BSC_SENT_UL_RTCP_BYTES
Interface (Traffic Load)
....................................................................................................................................................................................................................................

AIP30a - NB_BSC_SENT_UL_RTCP_BYTES
Descripton

Long Name NB_BSC_SENT_UL_RTCP_BYTES

Definition Counts the number of payload bytes of the UL RTCP packets sent by the BSC toward a given MGW IP@
Trigger condition This counter is increased by the number of bytes of the payload of the UL RTCP packet that is sent by the
BSC toward a given MGW IP@. The payload of an RTCP packet is defined as the RTCP packet format
without IP and UDP header.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A User Plane over IP (Traffic Load)

Sub Domain 3 --

Measured Object MGW_IP@


Type Name Overview measurements

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

Feature Name AUPoIP A interface user plane over IP

AIP30b - NB_BSC_SENT_UL_RTCP_PACKETS
Descripton

Long Name NB_BSC_SENT_UL_RTCP_PACKETS


Definition Counts the number of RTCP packets sent by the BSC toward a given MGW IP@
Trigger condition This counter is increased by one each time an UL RTCP packet is sent by the BSC to a given MGW IP@.
Sub Domain 1 Interface (Traffic Load)
Sub Domain 2 A User Plane over IP (Traffic Load)

Sub Domain 3 --
Measured Object MGW_IP@

Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load AIP30c - NB_BSC_SENT_UL_RTCP_BYTES_MAX_MN
Interface (Traffic Load)
....................................................................................................................................................................................................................................

AIP30c - NB_BSC_SENT_UL_RTCP_BYTES_MAX_MN
Descripton

Long Name NB_BSC_SENT_UL_RTCP_BYTES_MAX_MN

Definition Counts the max number of payload bytes of the UL RTCP packets sent by the BSC toward a given MGW
IP@ in one minute during the granularity period of monitoring
Trigger condition Every minute, the number of payload bytes of the UL RTCP packets sent by the BSC toward a given MGW
IP@ is counted. The maximum value obtained for 1 minute during the granularity period of monitoring is
reported. The payload of a RTCP packet is defined as the RTCP packet format without IP and UDP header.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A User Plane over IP (Traffic Load)

Sub Domain 3 --
Measured Object MGW_IP@
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name AUPoIP A interface user plane over IP

AIP40 - NB_BSC_SENT_ALL_FLOW_BYTES_MAX_MN
Descripton

Long Name NB_BSC_SENT_ALL_FLOW_BYTES_MAX_MN


Definition Counts the max number of the whole payload bytes sent by the BSC toward a given MGW IP@ in one
minute during the granularity period of monitoring
Trigger condition AIP10c+AIP20c+AIP30c

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A User Plane over IP (Traffic Load)

Sub Domain 3 --

Measured Object MGW_IP@


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

External Comment --

Feature Name AUPoIP A interface user plane over IP

....................................................................................................................................................................................................................................
50-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1060 - NB_GSL_MSG_SENT
Interface (Traffic Load)
....................................................................................................................................................................................................................................

MC1060 - NB_GSL_MSG_SENT
Descripton

Long Name NB_GSL_MSG_SENT

Definition Number of GSL messages sent by the BSC to the MFS on one GSL link (this could be BSCGP or BSCLP
messages).
Trigger condition The counter is incremented by 1 each time a GSL message is sent by the BSC to the MFS.
As this counter is at application (L3) level, L2 retry are not taken into account.
Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 GSL link (Traffic Load)


Sub Domain 3 --

Measured Object GSL link


Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name New GSL counters

MC1061 - NB_GSL_MSG_DISCARDED
Descripton

Long Name NB_GSL_MSG_DISCARDED


Definition Number of GSL messages discarded by the BSC (i.e not sent to the MFS) on one GSL link (this could be
BSCGP or BSCLP messages).
Trigger condition The counter is incremented by 1 each time a GSL message (BSCGP or BSCLP) is discarded by the BSC (i.e
not sent to the MFS) in the following cases:
1. GPRS RESET is going on: any new BSCGP messages cannot be sent
2. GSL Connection is not working anymore, but the application modules are not yet aware of it.
3. GPRSAP DTC is not working anymore.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 GSL link (Traffic Load)

Sub Domain 3 --
Measured Object GSL link

Type Name Overview measurements


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

External Comment --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1061 - NB_GSL_MSG_DISCARDED
Interface (Traffic Load)
....................................................................................................................................................................................................................................

Feature Name New GSL counters

MC1062 - NB_GSL_MSG_RESENT
Descripton

Long Name NB_GSL_MSG_RESENT

Definition Number of GSL messages resent by the BSC to the MFS on one GSL link (this could be BSCGP or BSCLP
messages).
Trigger condition The counter is incremented each time a GSL message is resent by the BSC to the MFS This counter does not
take into account L2 or TCP retries, but only the messages which need to be resent by the application
modules (Layer 3).
Note: the initial sending is not taken into account.
Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 GSL link (Traffic Load)


Sub Domain 3 --

Measured Object GSL link


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

External Comment --
Feature Name New GSL counters

MC1063 - NB_GSL_MSG_RECEIVED
Descripton

Long Name NB_GSL_MSG_RECEIVED


Definition Number of BSCGP messages received by the BSC from the MFS on one GSL link.

Trigger condition The counter is incremented by 1 each time a BSCGP message is received by the BSC from the MFS.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 GSL link (Traffic Load)

Sub Domain 3 --

Measured Object GSL link


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

External Comment --

....................................................................................................................................................................................................................................
50-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1063 - NB_GSL_MSG_RECEIVED
Interface (Traffic Load)
....................................................................................................................................................................................................................................

Feature Name New GSL counters

MC1064 - NB_GSL_BYTES_SENT
Descripton

Long Name NB_GSL_BYTES_SENT

Definition Number of bytes sent to the MFS on 1 GSL link.


Trigger condition For each message sent to the MFS on a GSL link, the counter is incremented by the number of bytes of the
message.
The resent messages are taken into account. L2 retry are not taken into account.
Sub Domain 1 Interface (Traffic Load)
Sub Domain 2 GSL link (Traffic Load)
Sub Domain 3 --

Measured Object GSL link


Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name IP transport in the BSS

MC1065 - MAX_NB_GSL_BYTES_SENT
Descripton

Long Name MAX_NB_GSL_BYTES_SENT

Definition Counts the maximum number of bytes of the GSL flow sent by the BSC to a given GPU in one minute
during the granularity period of monitoring.

Trigger condition Every minute, the number of bytes sent in the GSL flow by the BSC to a given GPU is counted. The
maximum value obtained for 1 minute during the granularity period of monitoring is reported.

Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 GSL link (Traffic Load)


Sub Domain 3 --
Measured Object GSL link

Type Name Overview measurements

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1065 - MAX_NB_GSL_BYTES_SENT
Interface (Traffic Load)
....................................................................................................................................................................................................................................

Feature Name IP transport in the BSS

MC1066 - MAX_NB_GSL_MSG_SENT
Descripton

Long Name MAX_NB_GSL_MSG_SENT

Definition Counts the maximum number of GSL messages (BSCGP or BSCLP) sent by the BSC on a given GSL link
to the MFS in one minute during the granularity period of monitoring.
Trigger condition Every minute, the number of GSL messages sent on a given GSL link by the BSC to the MFS is counted.
The maximum value obtained for 1 minute during the granularity period of monitoring is reported.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 GSL link (Traffic Load)
Sub Domain 3 --
Measured Object GSL link
Type Name Overview measurements

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

Feature Name IP transport in the BSS

MC1067 - AVERAGE_NB_MSG_IN_GSL_QUEUE
Descripton

Long Name AVERAGE_NB_MSG_IN_GSL_QUEUE


Definition Average number of GSL messages (BSCGP or BSCLP) queued in the BSC transmission buffer of one GSL
link (at Layer 2 level).

Trigger condition At the end of the granularity period of monitoring, all observations of this counter done at each polling
period are averaged, i.e. summed and divided by the number of observations. In order to provide one
decimal place, the averaged value (real) is multiplied by ten and then rounded up or down to the nearest
integer value.
It must be noted that this counter is managed at Layer 2 level, contrary to the other counters of this block
which are at application/L3 level.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 GSL link (Traffic Load)

Sub Domain 3 --

Measured Object GSL link


Type Name Overview measurements

....................................................................................................................................................................................................................................
50-16 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1067 - AVERAGE_NB_MSG_IN_GSL_QUEUE
Interface (Traffic Load)
....................................................................................................................................................................................................................................

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

External Comment --
Feature Name New GSL counters

MC1101 - NB_ASPUP_TX
Descripton

Long Name NB_ASPUP_TX

Definition Number of ASPUP messages sent by the BSC to any MSC


Trigger condition Each time the BSC application server (AS) sends an ASPUP to any MSC, this counter is incremented by
one.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A signaling over IP (Traffic Load)
Sub Domain 3 --
Measured Object MSC_BSC
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name A signaling over IP

MC1102 - NB_ASPUP_RX
Descripton

Long Name NB_ASPUP_RX

Definition Number of ASPUP messages received by the BSC from a given MSC

Trigger condition Each time the BSC application server (AS) receives an ASPUP from a given MSC, this counter is
incremented by one.
Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 A signaling over IP (Traffic Load)


Sub Domain 3 --

Measured Object MSC_BSC

Type Name Overview measurements


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

External Comment --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-17
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1102 - NB_ASPUP_RX
Interface (Traffic Load)
....................................................................................................................................................................................................................................

Feature Name A signaling over IP

MC1103 - NB_ASPDOWN_TX
Descripton

Long Name NB_ASPDOWN_TX

Definition Number of ASPDOWN messages sent by the BSC to any MSC


Trigger condition Each time the BSC application server (AS) sends an ASPDOWN to any MSC, this counter is incremented
by one.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A signaling over IP (Traffic Load)

Sub Domain 3 --
Measured Object MSC_BSC
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name A signaling over IP

MC1104 - NB_ASPDOWN_RX
Descripton

Long Name NB_ASPDOWN_RX


Definition Number of ASPDOWN messages received by the BSC from a given MSC
Trigger condition Each time the BSC application server (AS) receives an ASPDOWN from a given MSC, this counter is
incremented by one.

Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 A signaling over IP (Traffic Load)


Sub Domain 3 --
Measured Object MSC_BSC

Type Name Overview measurements

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

Feature Name A signaling over IP

....................................................................................................................................................................................................................................
50-18 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1105 - NB_ASPACTIVE_TX
Interface (Traffic Load)
....................................................................................................................................................................................................................................

MC1105 - NB_ASPACTIVE_TX
Descripton

Long Name NB_ASPACTIVE_TX

Definition Number of ASPACTIVE messages sent by the BSC to any MSC


Trigger condition Each time the BSC application server (AS) sends an ASPACTIVE to any MSC, this counter is incremented
by one.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A signaling over IP (Traffic Load)

Sub Domain 3 --
Measured Object MSC_BSC

Type Name Overview measurements


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

Feature Name A signaling over IP

MC1106 - NB_ASPACTIVE_RX
Descripton

Long Name NB_ASPACTIVE_RX


Definition Number of ASPACTIVE messages received by the BSC from a given MSC
Trigger condition Each time the BSC application server (AS) receives an ASPACTIVE from a given MSC, this counter is
incremented by one.
Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 A signaling over IP (Traffic Load)


Sub Domain 3 --

Measured Object MSC_BSC

Type Name Overview measurements


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

External Comment --
Feature Name A signaling over IP

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-19
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1107 - NB_ASPINACTIVE_TX
Interface (Traffic Load)
....................................................................................................................................................................................................................................

MC1107 - NB_ASPINACTIVE_TX
Descripton

Long Name NB_ASPINACTIVE_TX

Definition Number of ASPINACTIVE messages sent by the BSC to any MSC


Trigger condition Each time the BSC application server (AS) sends an ASPINACTIVE to any MSC, this counter is
incremented by one.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A signaling over IP (Traffic Load)

Sub Domain 3 --
Measured Object MSC_BSC

Type Name Overview measurements


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

Feature Name A signaling over IP

MC1108 - NB_ASPINACTIVE_RX
Descripton

Long Name NB_ASPINACTIVE_RX


Definition Number of ASPINACTIVE messages received by the BSC from a given MSC
Trigger condition Each time the BSC application server (AS) receives an ASPINACTIVE from a given MSC, this counter is
incremented by one.
Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 A signaling over IP (Traffic Load)


Sub Domain 3 --

Measured Object MSC_BSC

Type Name Overview measurements


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

External Comment --
Feature Name A signaling over IP

....................................................................................................................................................................................................................................
50-20 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1109 - NB_BSC_SENT_SS7_IP_BYTES_Asig_IP
Interface (Traffic Load)
....................................................................................................................................................................................................................................

MC1109 - NB_BSC_SENT_SS7_IP_BYTES_Asig_IP
Descripton

Long Name NB_BSC_SENT_SS7_IP_BYTES_Asig_IP

Definition Counts the number of bytes of the SS7 flow sent by a BSC to the MSC (MSC-CS) when A signaling over IP
is used.
Trigger condition Each time an SS7 message is sent by the BSC to the MSC on the A signaling over IP interface, this counter
is increased by the number of bytes of this message.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A signaling over IP (Traffic Load)

Sub Domain 3 --

Measured Object MSC_BSC


Type Name Overview measurements

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

Feature Name A signaling over IP

MC1110 - NB_BSC_SENT_SS7_IP_PACKETS_Asig_IP
Descripton

Long Name NB_BSC_SENT_SS7_IP_PACKETS_Asig_IP


Definition Counts the number of SCTP packets sent by a BSC to a given MSC for the SS7 flow when A signaling over
IP is used. It corresponds to is the number of SCTP segments sent, counted by the SCTP stack.
Trigger condition Each time a SCTP segment containing a SS7 packet is sent by the BSC to the MSC, this counter is increased
by 1.

Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 A signaling over IP (Traffic Load)


Sub Domain 3 --
Measured Object MSC_BSC

Type Name Overview measurements

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

Feature Name A signaling over IP

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-21
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1111 - NB_BSC_RESENT_SS7_IP_PACKETS_Asig_IP
Interface (Traffic Load)
....................................................................................................................................................................................................................................

MC1111 - NB_BSC_RESENT_SS7_IP_PACKETS_Asig_IP
Descripton

Long Name NB_BSC_RESENT_SS7_IP_PACKETS_Asig_IP

Definition Counts the number of SCTP packets resent by a BSC to a given MSC for the SS7 flow, when A signaling
over IP is used.
Trigger condition Each time a SCTP segment containing a SS7 packet is resent by the BSC to a given MSC with A signaling
interface over IP, this counter is increased by 1.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A signaling over IP (Traffic Load)

Sub Domain 3 --

Measured Object MSC_BSC


Type Name Overview measurements

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

Feature Name A signaling over IP

MC1112 - NB_BSC_SENT_SS7_IP_BYTES_MAX_MN_Asig_IP
Descripton

Long Name NB_BSC_SENT_SS7_IP_BYTES_MAX_MN_Asig_IP


Definition Counts the max number of bytes of the SS7 flow sent by a BSC to a given MSC in one minute during the
granularity period of monitoring, when A signaling over IP is used.
Trigger condition Every minute, the number of bytes of each SS7 message sent by the BSC to a given MSC over the A
signaling interface over IP, is counted. The maximum value obtained for 1 minute during the granularity
period of monitoring is reported.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A signaling over IP (Traffic Load)

Sub Domain 3 --

Measured Object MSC_BSC


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

External Comment --

Feature Name A signaling over IP

....................................................................................................................................................................................................................................
50-22 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1114 - NB_N7_UNIT_DATA_SENT_Asig_IP
Interface (Traffic Load)
....................................................................................................................................................................................................................................

MC1114 - NB_N7_UNIT_DATA_SENT_Asig_IP
Descripton

Long Name NB_N7_UNIT_DATA_SENT_Asig_IP

Definition Number of connectionless Unit Data messages class 0 sent to the MSC, when A signaling over IP is used.
Trigger condition Whenever a UNIT DATA message (with protocol class parameter equal to 0) is sent from the BSC to the
MSC, when A signaling over IP is used..

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A signaling over IP (Traffic Load)

Sub Domain 3 --
Measured Object MSC_BSC

Type Name Overview measurements


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

Feature Name A signaling over IP

MC1115 - NB_N7_UNIT_DATA_REC_Asig_IP
Descripton

Long Name NB_N7_UNIT_DATA_REC_Asig_IP


Definition Number of connectionless Unit Data messages class 0 received from the MSC, when A signaling over IP is
used.
Trigger condition Whenever a UNIT DATA message (with protocol class parameter equal to 0) is received from the MSC,
when A signaling over IP is used.
Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 --

Sub Domain 3 --
Measured Object MSC_BSC

Type Name Overview measurements


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

External Comment --
Feature Name A signaling over IP

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-23
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1116 - NB_N7_CON_REQ_SENT_Asig_IP
Interface (Traffic Load)
....................................................................................................................................................................................................................................

MC1116 - NB_N7_CON_REQ_SENT_Asig_IP
Descripton

Long Name NB_N7_CON_REQ_SENT_Asig_IP

Definition Number of CONNECTION REQUEST sent to the MSC by the BSC, when A signaling over IP is used.
Trigger condition Whenever a CONNECTION REQUEST message is sent on A interface from the BSC to the MSC, when A
signaling over IP is used.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A signaling over IP (Traffic Load)

Sub Domain 3 --
Measured Object MSC_BSC

Type Name Overview measurements


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

Feature Name A signaling over IP

MC1117 - NB_N7_CON_REQ_REC_Asig_IP
Descripton

Long Name NB_N7_CON_REQ_REC_Asig_IP


Definition Number of CONNECTION REQUEST received from the MSC by the BSC, when A signaling over IP is
used.
Trigger condition Whenever a CONNECTION REQUEST message is received on A interface by the BSC from the MSC,
when A signaling over IP is used.
Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 A signaling over IP (Traffic Load)

Sub Domain 3 --
Measured Object MSC_BSC

Type Name Overview measurements


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

External Comment --
Feature Name A signaling over IP

....................................................................................................................................................................................................................................
50-24 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1118 - NB_N7_CON_CONF_SENT_Asig_IP
Interface (Traffic Load)
....................................................................................................................................................................................................................................

MC1118 - NB_N7_CON_CONF_SENT_Asig_IP
Descripton

Long Name NB_N7_CON_CONF_SENT_Asig_IP

Definition Number of CONNECTION CONFIRM sent to the MSC by the BSC, when A signaling over Ip is used.
Trigger condition Whenever a CONNECTION CONFIRM message is sent by the BSC to the MSC, when A interface over IP
is used.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A signaling over IP (Traffic Load)

Sub Domain 3 --
Measured Object MSC_BSC

Type Name Overview measurements


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

Feature Name A signaling over IP

MC1119 - NB_N7_CON_CONF_REC_Asig_IP
Descripton

Long Name NB_N7_CON_CONF_REC_Asig_IP


Definition Number of CONNECTION CONFIRM sent from the MSC by the BSC, when A signaling over Ip is used.
Trigger condition Whenever a CONNECTION CONFIRM message is received by the BSC from the MSC, when A interface
over IP is used.
Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 A signaling over IP (Traffic Load)


Sub Domain 3 --

Measured Object MSC_BSC

Type Name Overview measurements


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

External Comment --
Feature Name A signaling over IP

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-25
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1120 - NB_N7_CON_REF_SENT_Asig_IP
Interface (Traffic Load)
....................................................................................................................................................................................................................................

MC1120 - NB_N7_CON_REF_SENT_Asig_IP
Descripton

Long Name NB_N7_CON_REF_SENT_Asig_IP

Definition Number of CONNECTION REFUSED sent to the MSC by the BSC, when A signaling over IP is used.
Trigger condition Whenever a CONNECTION REFUSED message is sent on A interface from the BSC to the MSC, when A
signaling over IP is used.

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A signaling over IP (Traffic Load)

Sub Domain 3 --
Measured Object MSC_BSC

Type Name Overview measurements


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

Feature Name A signaling over IP

MC1121 - NB_N7_CON_REF_REC_Asig_IP
Descripton

Long Name NB_N7_CON_REF_REC_Asig_IP


Definition Number of CONNECTION REFUSED received from the MSC by the BSC, when A signaling over IP is
used..
Trigger condition Whenever a CONNECTION REFUSED message is received on A interface by the BSC from the MSC,
when A signaling over IP is used.
Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 A signaling over IP (Traffic Load)

Sub Domain 3 --
Measured Object MSC_BSC

Type Name Overview measurements


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

External Comment --
Feature Name A signaling over IP

....................................................................................................................................................................................................................................
50-26 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1700 - TIME_A_CHANNELS_MSC_BUSY
Interface (Traffic Load)
....................................................................................................................................................................................................................................

MC1700 - TIME_A_CHANNELS_MSC_BUSY
Descripton

Long Name TIME_A_CHANNELS_MSC_BUSY

Definition Time (in seconds) during which the A channels handled by a given MSC through the MGWs are busy.
Trigger condition The counter cumulates over the Accumulation Period, all unit times during which the A channels handled by
a given MSC through the MGWs are busy.

Sub Domain 1 Interface (Traffic Load)

Sub Domain 2 A
Sub Domain 3 --

Measured Object MSC_BSC


Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name MOCN

MC350 - NB_N7_CON_REQ
Descripton

Long Name NB_N7_CON_REQ


Definition MC350=C253+C254
Trigger condition --
Sub Domain 1 Interface (Traffic Load)
Sub Domain 2 A

Sub Domain 3 SCCP


Measured Object N7 Signalling Link

Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-27
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC351 - NB_N7_CON_CONF
Interface (Traffic Load)
....................................................................................................................................................................................................................................

MC351 - NB_N7_CON_CONF
Descripton

Long Name NB_N7_CON_CONF

Definition MC351=C255+C256
Trigger condition --

Sub Domain 1 Interface (Traffic Load)


Sub Domain 2 A

Sub Domain 3 SCCP


Measured Object N7 Signalling Link

Type Name Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC940 - NB_A_PAGING_MSG
Descripton

Long Name NB_A_PAGING_MSG


Definition Number of 48.008 PAGING messages received by the BSC from any MSC
Trigger condition Each time the BSC received a PAGING message from a MSC, this counter is increased by one
Sub Domain 1 Interface (Traffic Load)
Sub Domain 2 A

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

Feature Name New counters of discarded messages (NE request)

....................................................................................................................................................................................................................................
50-28 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load Overview
IP (Traffic Load)
....................................................................................................................................................................................................................................

IP (Traffic Load)

Overview
Purpose
This section contains IP (Traffic Load) parameters.

Contents

MC941 - NB_INIT_L3_MSG_CM_SERV_REQ_NRI_UNKNOWN 50-29


MC980 - NB_INIT_L3_MSG_PAGING_RESPONSE_NRI 50-30
MC981 - NB_INIT_L3_MSG_IMSI_DETACH_IND_NRI 50-30
MC982 - NB_INIT_L3_MSG_CM_RE_ESTABL_REQ_NRI 50-31
MC983 - NB_INIT_L3_MSG_IMSI_ATTACH_NRI 50-31
MC984 - NB_INIT_L3_MSG_LOC_UPD_NRI 50-32
MC985a - NB_INIT_L3_MSG_CM_SERV_REQ_SMS_NRI 50-32
MC985b - NB_INIT_L3_MSG_CM_SERV_REQ_SUP_SERV_NRI 50-33
MC985c - NB_INIT_L3_MSG_CM_SERV_REQ_CALL_EST_NRI 50-33
MC985d - NB_INIT_L3_MSG_CM_SERV_REQ_LOC_SERV_NRI 50-34
MC985e - NB_INIT_L3_MSG_CM_SERV_REQ_OTHERS_NRI 50-34

MC941 - NB_INIT_L3_MSG_CM_SERV_REQ_NRI_UNKNOWN
Descripton

Long Name NB_INIT_L3_MSG_CM_SERV_REQ_NRI_UNKNOWN


Definition Number of CM SERVICE REQUEST received with an unknown NRI
Trigger condition Whenever a 48.058 ESTABLISH INDICATION message with "L3 Information" OIE containing a 24.008
"CM SERVICE REQUEST" message and the "Mobile Identity" MIE contains a TMSI with an unknown
NRI (i.e. a not configured NRI).
Sub Domain 1 IP (Traffic Load)

Sub Domain 2 Abis (Traffic Load IP)


Sub Domain 3 --

Measured Object BSC

Type Name Overview measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-29
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC941 - NB_INIT_L3_MSG_CM_SERV_REQ_NRI_UNKNOWN
IP (Traffic Load)
....................................................................................................................................................................................................................................

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

External Comment --
Feature Name A-Flex

MC980 - NB_INIT_L3_MSG_PAGING_RESPONSE_NRI
Descripton

Long Name NB_INIT_L3_MSG_PAGING_RESPONSE_NRI

Definition Number of 44.018 PAGING RESPONSE message


Trigger condition Whenever a 48.058 ESTABLISH INDICATION message with "L3 Information" OIE containing a 44.018
PAGING RESPONSE message and the "Mobile Identity" MIE contains a TMSI with a known NRI (i.e. a
configured NRI, including the NULL NRI).

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 Abis (Traffic Load IP)
Sub Domain 3 --
Measured Object NRI
Type Name Overview measurements

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

Feature Name A-Flex

MC981 - NB_INIT_L3_MSG_IMSI_DETACH_IND_NRI
Descripton

Long Name NB_INIT_L3_MSG_IMSI_DETACH_IND_NRI

Definition Number of 24.008 IMSI DETACH INDICATION message


Trigger condition Whenever a 48.058 ESTABLISH INDICATION message with "L3 Information" OIE containing a 24.008
IMSI DETACH INDICATION message and the "Mobile Identity" MIE contains a TMSI with a known NRI
(i.e. a configured NRI, including the NULL NRI).

Sub Domain 1 IP (Traffic Load)

Sub Domain 2 Abis (Traffic Load IP)


Sub Domain 3 --
Measured Object NRI

Type Name Overview measurements

....................................................................................................................................................................................................................................
50-30 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC981 - NB_INIT_L3_MSG_IMSI_DETACH_IND_NRI
IP (Traffic Load)
....................................................................................................................................................................................................................................

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

External Comment --
Feature Name A-Flex

MC982 - NB_INIT_L3_MSG_CM_RE_ESTABL_REQ_NRI
Descripton

Long Name NB_INIT_L3_MSG_CM_RE_ESTABL_REQ_NRI

Definition Number of 24.008 CM RE-ESTABLISHMENT REQUEST message


Trigger condition Whenever a 48.058 ESTABLISH INDICATION message with "L3 Informatio" OIE containing a 24.008
CM RE-ESTABLISHMENT REQUEST message and the "Mobile Identity" MIE contains a TMSI with a
known NRI (i.e. a configured NRI, including the NULL NRI).

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 Abis (Traffic Load IP)
Sub Domain 3 --
Measured Object NRI
Type Name Overview measurements

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

Feature Name A-Flex

MC983 - NB_INIT_L3_MSG_IMSI_ATTACH_NRI
Descripton

Long Name NB_INIT_L3_MSG_IMSI_ATTACH_NRI

Definition Number of IMSI attach


Trigger condition Whenever a 48.058 ESTABLISH INDICATION message with "L3 Information" OIE containing a 24.008
"LOCATION UPDATING REQUEST" message with "Location updating type" MIE set to "IMSI attach"
and the "Mobile Identity" MIE contains a TMSI with a known NRI (i.e. a configured NRI, including the
NULL NRI).

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 Abis (Traffic Load IP)

Sub Domain 3 --

Measured Object NRI


Type Name Overview measurements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-31
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC983 - NB_INIT_L3_MSG_IMSI_ATTACH_NRI
IP (Traffic Load)
....................................................................................................................................................................................................................................

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

External Comment --
Feature Name A-Flex

MC984 - NB_INIT_L3_MSG_LOC_UPD_NRI
Descripton

Long Name NB_INIT_L3_MSG_LOC_UPD_NRI

Definition Number of Location Updating


Trigger condition Whenever a 48.058 ESTABLISH INDICATION message with "L3 Information" OIE containing a 24.008
"LOCATION UPDATING REQUEST" message with "Location updating type" MIE set to "Normal location
updating" or "Periodic updating" and the "Mobile Identity" MIE contains a TMSI with a known NRI (i.e. a
configured NRI, including the NULL NRI).

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 Abis (Traffic Load IP)
Sub Domain 3 --
Measured Object NRI
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name A-Flex

MC985a - NB_INIT_L3_MSG_CM_SERV_REQ_SMS_NRI
Descripton

Long Name NB_INIT_L3_MSG_CM_SERV_REQ_SMS_NRI


Definition Number of CM SERVICE REQUEST for "Short message service"
Trigger condition Whenever a 48.058 ESTABLISH INDICATION message with "L3 Information" OIE containing a 24.008
"CM SERVICE REQUEST" message with "CM service type" MIE set to "Short message service" and the
"Mobile Identity" MIE contains a TMSI with a known NRI (i.e. a configured NRI, including the NULL
NRI).
Sub Domain 1 IP (Traffic Load)

Sub Domain 2 Abis (Traffic Load IP)


Sub Domain 3 --

Measured Object NRI

....................................................................................................................................................................................................................................
50-32 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC985a - NB_INIT_L3_MSG_CM_SERV_REQ_SMS_NRI
IP (Traffic Load)
....................................................................................................................................................................................................................................

Type Name Overview measurements

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

Feature Name A-Flex

MC985b - NB_INIT_L3_MSG_CM_SERV_REQ_SUP_SERV_NRI
Descripton

Long Name NB_INIT_L3_MSG_CM_SERV_REQ_SUP_SERV_NRI

Definition Number of CM SERVICE REQUEST for "Supplementary service activation"


Trigger condition Whenever a 48.058 ESTABLISH INDICATION message with "L3 Information" OIE containing a 24.008
"CM SERVICE REQUEST" message with "CM service type" MIE set to"Supplementary service activation"
and the "Mobile Identity" MIE contains a TMSI with a known NRI (i.e. a configured NRI, including the
NULL NRI).

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 Abis (Traffic Load IP)
Sub Domain 3 --
Measured Object NRI
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name A-Flex

MC985c - NB_INIT_L3_MSG_CM_SERV_REQ_CALL_EST_NRI
Descripton

Long Name NB_INIT_L3_MSG_CM_SERV_REQ_CALL_EST_NRI


Definition Number of CM SERVICE REQUEST for "Mobile originating call" or "packet mode connection" or
"Emergency call" establishment
Trigger condition Whenever a 48.058 ESTABLISH INDICATION message with "L3 Information" OIE containing a 24.008
"CM SERVICE REQUEST" message with "CM service type" MIE set to "Mobile originating call
establishment or packet mode connection establishment" or "Emergency call establishment" and the "Mobile
Identity" MIE contains a TMSI with a known NRI (i.e. a configured NRI, including the NULL NRI).

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 Abis (Traffic Load IP)

Sub Domain 3 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-33
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC985c - NB_INIT_L3_MSG_CM_SERV_REQ_CALL_EST_NRI
IP (Traffic Load)
....................................................................................................................................................................................................................................

Measured Object NRI

Type Name Overview measurements


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

External Comment --
Feature Name A-Flex

MC985d - NB_INIT_L3_MSG_CM_SERV_REQ_LOC_SERV_NRI
Descripton

Long Name NB_INIT_L3_MSG_CM_SERV_REQ_LOC_SERV_NRI


Definition Number of CM SERVICE REQUEST for "Location Services"
Trigger condition Whenever a 48.058 ESTABLISH INDICATION message with "L3 Information" OIE containing a 24.008
"CM SERVICE REQUEST" message with "CM service type" MIE set to "Location Services" and the
"Mobile Identity" MIE contains a TMSI with a known NRI (i.e. a configured NRI, including the NULL
NRI).

Sub Domain 1 IP (Traffic Load)


Sub Domain 2 Abis (Traffic Load IP)
Sub Domain 3 --
Measured Object NRI
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --

Feature Name A-Flex

MC985e - NB_INIT_L3_MSG_CM_SERV_REQ_OTHERS_NRI
Descripton

Long Name NB_INIT_L3_MSG_CM_SERV_REQ_OTHERS_NRI

Definition Number of CM SERVICE REQUEST for other services

Trigger condition Whenever a 48.058 ESTABLISH INDICATION message with "L3 Information" OIE containing a 24.008
"CM SERVICE REQUEST" message with "CM service type" MIE set to none of "Short message service",
"Supplementary service activation", "Mobile originating call establishment or packet mode connection
establishment", "Emergency call establishment", "Location Services" and the "Mobile Identity" MIE
contains a TMSI with a known NRI (i.e. a configured NRI, including the NULL NRI).
Sub Domain 1 IP (Traffic Load)

Sub Domain 2 Abis (Traffic Load IP)

....................................................................................................................................................................................................................................
50-34 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC985e - NB_INIT_L3_MSG_CM_SERV_REQ_OTHERS_NRI
IP (Traffic Load)
....................................................................................................................................................................................................................................

Sub Domain 3 --

Measured Object NRI


Type Name Overview measurements

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

Feature Name A-Flex

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-35
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load Overview
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

Radio Channel (Traffic Load)

Overview
Purpose
This section contains Radio Channel (Traffic Load) parameters.

Contents

MC1520 - BSCHE20 50-37


MC1521 - BSCHE21 50-38
MC1522 - BSCHE22 50-39
MC1523 - BSCHE23 50-40
MC1524 - BSCHE24 50-41
MC1525 - BSCHE2x 50-42
MC1600 - OLC_NB_CHAN_REQD 50-43
MC380a - TIME_TRX_FR_BUSY 50-43
MC380b - TIME_TRX_HR_BUSY 50-44
MC380c - TIME_TRX_GSM_FR_BUSY 50-44
MC380d - TIME_TRX_GSM_HR_BUSY 50-45
MC380e - TIME_TRX_DCS_FR_BUSY 50-46
MC380f - TIME_TRX_DCS_HR_BUSY 50-46
MC381 - TIME_TRX_TCH_BUSY_BY_MULTIBAND_MS 50-47
MC400 - TIME_TRX_SDCCH_BUSY 50-48
MC804a - NB_UL_SINGLE_BLOCK_SIG_RACH 50-48
MC804b - NB_UL_ONE_PHASE_SIG_RACH 50-49
MC805a - NB_CHANNEL_ASSIGN_DL_AGCH 50-49
MC805b - NB_CHANNEL_ASSIGN_DL_PCH 50-50
MC8a - NB_CELL_PAGING_CMD 50-50
MC8b - NB_CELL_IMM_ASS_CMD 50-51
MC8c - NB_CELL_CHAN_REQD 50-51
MC8d - NB_CELL_IMM_ASS_REJ 50-52
MC924a - TIME_SPDCH_LIMIT_HIGH_LOAD 50-52

....................................................................................................................................................................................................................................
50-36 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load Overview
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

MC925a - NB_AGCH_USEFUL_BLOCKS_SENT 50-53


MC925b - NB_PCH_USEFUL_BLOCKS_SENT 50-53
MC925c - NB_BUSY_RACH_SLOTS 50-54
MC925d - NB_CHANNEL_RQ_RADIO 50-54
MC925e - NB_ASSIGN_CMD_RECEIVED_ABIS 50-55
MC925f - NB_ASSIGN_CMD_DISCARDED 50-56
MC925g - NB_PAGING_CMD_RECEIVED_ABIS 50-56
MC925h - NB_PAGING_CMD_DISCARDED 50-57
MC930 - NB_ABIS_PAGING_MESSAGE_RECEIVED 50-58
MC961 - NB_CELL_CS_PAGING_WITH_IMSI 50-58

MC1520 - BSCHE20
Descripton

Long Name BSCHE20


Definition AMR FR traffic volume. The sum of period from Assignment Complete/Handover Complete to Clear
Command on all TCHs of one cell, using AMR FR codec.
Trigger condition In non-VAMOS mode, the counter cumulates over the Accumulation Period, per cell, all unit times during
which a TCH FR channel with speech AMR codec is busy. All radio timeslots of all TRXs of the cell are
cumulated.
In VAMOS mode, the counter cumulates, over the Accumulation Period all unit times during which a
VAMOS TCH FR channel of the timeslot with speech AMR codec is busy. Both VAMOS TCH FR of the
timeslot are counted independently. All radio timeslots of all TRXs of the cell are cumulated.
For each channel allocation (any causes: call establishment or handover)
1) The counter starts being incremented after the receipt of the 48.058 ASSIGNMENT COMPLETE or
HANDOVER COMPLETE message to the cell concerning a full rate TCH channel used with AMR FR
codec 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 Radio Channel (Traffic Load)
Sub Domain 2 TCH

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-37
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1520 - BSCHE20
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

External Comment --

Feature Name Traffic volume by codec type

MC1521 - BSCHE21
Descripton

Long Name BSCHE21

Definition AMR HR traffic volume. The sum of period from Assignment Complete/Handover Complete to Clear
Command on all TCHs of one cell, using AMR HR codec.
Trigger condition In non-VAMOS mode, the counter cumulates over the Accumulation Period, per cell, all unit times during
which a TCH HR channel with speech AMR codec is busy. All radio timeslots of all TRXs of the cell are
cumulated.
In VAMOS mode, the counter cumulates, over the Accumulation Period all unit times during which a
VAMOS TCH HR channel of the timeslot with speech AMR codec is busy. VAMOS TCH HR of the
timeslot are counted independently. All radio timeslots of all TRXs of the cell are cumulated.
For each channel allocation (any causes: call establishment or handover)
1) The counter starts being incremented after the receipt of the 48.058 ASSIGNMENT COMPLETE or
HANDOVER COMPLETE message to the cell concerning a full rate TCH channel used with AMR HR
codec 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 Radio Channel (Traffic Load)
Sub Domain 2 TCH
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Traffic volume by codec type

....................................................................................................................................................................................................................................
50-38 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1522 - BSCHE22
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

MC1522 - BSCHE22
Descripton

Long Name BSCHE22

Definition EFR traffic volume. The sum of period from Assignment Complete/Handover Complete to Clear Command
on all TCHs of one cell, using EFR codec.
Trigger condition In non-VAMOS mode, the counter cumulates over the Accumulation Period, per cell, all unit times during
which a TCH FR channel with speech EFR codec is busy. All radio timeslots of all TRXs of the cell are
cumulated.
In VAMOS mode, the counter cumulates, over the Accumulation Period all unit times during which a
VAMOS TCH FR channel of the timeslot with speech EFR codec is busy. Both VAMOS TCH FR of the
timeslot are counted independently. All radio timeslots of all TRXs of the cell are cumulated.
For each channel allocation (any causes: call establishment or handover)
1) The counter starts being incremented after the receipt of the 48.058 ASSIGNMENT COMPLETE or
HANDOVER COMPLETE message to the cell concerning a full rate TCH channel used with EFR codec 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 Radio Channel (Traffic Load)
Sub Domain 2 TCH
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Traffic volume by codec type

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-39
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1523 - BSCHE23
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

MC1523 - BSCHE23
Descripton

Long Name BSCHE23

Definition FR traffic volume.The sum of period from Assignment Complete/Handover Complete to Clear Command on
all TCHs of one cell, using GSM FR codec.
Trigger condition In non-VAMOS mode, the counter cumulates over the Accumulation Period, per cell, all unit times during
which a TCH FR channel with speech GSM FR codec is busy. All radio timeslots of all TRXs of the cell are
cumulated.
In VAMOS mode, the counter cumulates, over the Accumulation Period all unit times during which a
VAMOS TCH FR channel of the timeslot with speech GSM FR codec is busy. Both VAMOS TCH FR of the
timeslot are counted independently. All radio timeslots of all TRXs of the cell are cumulated.
For each channel allocation (any causes: call establishment or handover)
1) The counter starts being incremented after the receipt of the 48.058 ASSIGNMENT COMPLETE or
HANDOVER COMPLETE message to the cell concerning a full rate TCH channel used with GSM FR
codec 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 Radio Channel (Traffic Load)
Sub Domain 2 TCH
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Traffic volume by codec type

....................................................................................................................................................................................................................................
50-40 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1524 - BSCHE24
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

MC1524 - BSCHE24
Descripton

Long Name BSCHE24

Definition HR traffic volume.The sum of period from Assignment Complete/Handover Complete to Clear Command
on all TCHs of one cell, using HR codec.
Trigger condition In non-VAMOS mode, the counter cumulates over the Accumulation Period, per cell, all unit times during
which a TCH HR channel with speech GSM HR codec is busy. All radio timeslots of all TRXs of the cell are
cumulated.
In VAMOS mode, the counter cumulates, over the Accumulation Period all unit times during which a
VAMOS TCH HR channel of the timeslot with speech GSM HR codec is busy. VAMOS TCH HR of the
timeslot are counted independently. All radio timeslots of all TRXs of the cell are cumulated.
For each channel allocation (any causes: call establishment or handover)
1) The counter starts being incremented after the receipt of the 48.058 ASSIGNMENT COMPLETE or
HANDOVER COMPLETE message to the cell concerning a full rate TCH channel used with GSM HR
codec 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 Radio Channel (Traffic Load)
Sub Domain 2 TCH
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Traffic volume by codec type

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-41
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1525 - BSCHE2x
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

MC1525 - BSCHE2x
Descripton

Long Name BSCHE2x

Definition WB-AMR traffic volume. The sum of period from Assignment Complete/Handover Complete to Clear
Command on all TCHs of one cell, using WB-AMR codec.
Trigger condition In non-VAMOS mode, the counter cumulates over the Accumulation Period, per cell, all unit times during
which a TCH FR channel with speech WB-AMR codec is busy. All radio timeslots of all TRXs of the cell
are cumulated.
In VAMOS mode, the counter cumulates, over the Accumulation Period all unit times during which a
VAMOS TCH FR channel of the timeslot with speech WB-AMR codec is busy. Both VAMOS TCH FR of
the timeslot are counted independently. All radio timeslots of all TRXs of the cell are cumulated.
For each channel allocation (any causes: call establishment or handover)
1) The counter starts being incremented after the receipt of the 48.058 ASSIGNMENT COMPLETE or
HANDOVER COMPLETE message to the cell concerning a full rate TCH channel used with WB-AMR FR
codec 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 Radio Channel (Traffic Load)
Sub Domain 2 TCH
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Traffic volume by codec type

....................................................................................................................................................................................................................................
50-42 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC1600 - OLC_NB_CHAN_REQD
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

MC1600 - OLC_NB_CHAN_REQD
Descripton

Long Name OLC_NB_CHAN_REQD

Definition Number of valid 48.058 CHANNEL REQUIRED received via the selected site in OCL configuration per
TRX and per site.
Number of 48.058 CHANNEL REQUIRED (for packet service as defined in MC959) received via the
selected cell are not counted.
Number of invalid (as defined in MC962) 48.058 CHANNEL REQUIRED (for all establishment cause)
messages received by the BSC are not counted.

Trigger condition Whenever a 48.058 CHANNEL REQUIRED message ( for CS traffic) is received on Abis interface.
The identification of the site (RRH) inside the One Logical Cell OLC is obtained by BSC via RRH ID in
CHANNEL REQUIRED.

Sub Domain 1 Radio Channel (Traffic Load)

Sub Domain 2 CCCH


Sub Domain 3 --

Measured Object Site_TRX


Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC380a - TIME_TRX_FR_BUSY
Descripton

Long Name TIME_TRX_FR_BUSY

Definition Time (in seconds) during which the radio timeslot in FR TCH usage is busy
Trigger condition MC380A= SUM (all TRX_TS of the TRX) (C380A)

Sub Domain 1 Radio Channel (Traffic Load)


Sub Domain 2 TCH

Sub Domain 3 --
Measured Object TRX

Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-43
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC380b - TIME_TRX_HR_BUSY
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

MC380b - TIME_TRX_HR_BUSY
Descripton

Long Name TIME_TRX_HR_BUSY

Definition Time (in seconds) during which the radio timeslot in HR TCH usage is busy
Trigger condition MC380B= SUM (all TRX_TS of the TRX) (C380B)

Sub Domain 1 Radio Channel (Traffic Load)


Sub Domain 2 TCH

Sub Domain 3 --
Measured Object TRX

Type Name Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC380c - TIME_TRX_GSM_FR_BUSY
Descripton

Long Name TIME_TRX_GSM_FR_BUSY


Definition Time (in seconds) during which the radio timeslot (TCH or dynamic SDCCH/8) in the GSM frequency band
is busy in TCH FR usage. This counter takes into account TCH in traffic or in signaling mode.
Trigger condition In non-VAMOS mode, the counter cumulates over the Accumulation Period, per radio timeslot, all unit
times during which the TCH FR channel in the GSM frequency band is busy. In VAMOS mode, the counter
cumulates, over the Accumulation Period all unit times during which a
VAMOS TCH FR channel of the timeslot in the GSM frequency band is busy. Both VAMOS TCH FR of the
timeslot are counted independently.
For example, in an extreme case of 100% VAMOS FR allocations for 1 hour on 1 TRX, MC380c will count
2*3600s.
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 or in VAMOS mode a FR
VAMOS suchannel 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 Radio Channel (Traffic Load)


Sub Domain 2 TCH

Sub Domain 3 --
Measured Object TRX

....................................................................................................................................................................................................................................
50-44 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC380c - TIME_TRX_GSM_FR_BUSY
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

Type Name Overview measurements

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

Feature Name B8 BSC counters improvements

MC380d - TIME_TRX_GSM_HR_BUSY
Descripton

Long Name TIME_TRX_GSM_HR_BUSY

Definition Time (in seconds) during which the radio timeslot (TCH or dynamic SDCCH/8) in the GSM frequency band
is busy in HR TCH usage.
Trigger condition In non-VAMOS mode, the counter cumulates over the Accumulation Period, per radio timeslot, all unit
times during which the TCH HR channel in the GSM frequency band is busy. In VAMOS mode, The
counter cumulates, over the Accumulation Period all unit times during which a VAMOS TCH HR channel of
the timeslot in the GSM frequency band is busy. All VAMOS TCH HR of the timeslot are counted
independently.
For example, in an extreme case of 100% VAMOS HR allocations for 1 hour on 1 TRX, C380b will count
4*3600s.
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 or in VAMOS mode an
HR VAMOS suchannel mapped on any place of the related timeslot, 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 Radio Channel (Traffic Load)
Sub Domain 2 TCH
Sub Domain 3 --
Measured Object TRX

Type Name Overview measurements


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

External Comment --

Feature Name B8 BSC counters improvements

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-45
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC380e - TIME_TRX_DCS_FR_BUSY
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

MC380e - TIME_TRX_DCS_FR_BUSY
Descripton

Long Name TIME_TRX_DCS_FR_BUSY

Definition Time (in seconds) during which the radio timeslot (TCH or dynamic SDCCH/8) in the DCS/PCS frequency
band is busy in TCH FR usage. This counter takes into account TCH in traffic or in signaling mode.
Trigger condition In non-VAMOS mode, 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.In VAMOS mode, the
counter cumulates, over the Accumulation Period all unit times during which a
VAMOS TCH FR channel of the timeslot in the DCS/PCS frequency band is busy. Both VAMOS TCH FR
of the timeslot are counted independently.
For example, in an extreme case of 100% VAMOS FR allocations for 1 hour on 1 TRX, C380c will count
2*3600s.
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 or in VAMOS mode a FR
VAMOS suchannel 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 Radio Channel (Traffic Load)
Sub Domain 2 TCH

Sub Domain 3 --
Measured Object TRX

Type Name Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name B8 BSC counters improvements

MC380f - TIME_TRX_DCS_HR_BUSY
Descripton

Long Name TIME_TRX_DCS_HR_BUSY


Definition Time (in seconds) during which the radio timeslot (TCH or dynamic SDCCH/8) in the DCS/PCS frequency
band is busy in HR usage.

....................................................................................................................................................................................................................................
50-46 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC380f - TIME_TRX_DCS_HR_BUSY
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

Trigger condition In non-VAMOS mode, 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.In VAMOS mode, The
counter cumulates, over the Accumulation Period all unit times during which a
VAMOS TCH HR channel of the timeslot in the DCS/PCS frequency band is busy. All VAMOS TCH HR of
the timeslot are counted independently.
For example, in an extreme case of 100% VAMOS HR allocations for 1 hour on 1 TRX, C380b will count
4*3600s.
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 Radio Channel (Traffic Load)


Sub Domain 2 TCH

Sub Domain 3 --
Measured Object TRX

Type Name Overview measurements


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

External Comment --
Feature Name B8 BSC counters improvements

MC381 - TIME_TRX_TCH_BUSY_BY_MULTIBAND_MS
Descripton

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 Radio Channel (Traffic Load)

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object TRX

Type Name Overview measurements


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

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-47
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC400 - TIME_TRX_SDCCH_BUSY
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

MC400 - TIME_TRX_SDCCH_BUSY
Descripton

Long Name TIME_TRX_SDCCH_BUSY

Definition MC400= SUM (all TRX_TS of the TRX) C40


Trigger condition --

Sub Domain 1 Radio Channel (Traffic Load)


Sub Domain 2 SDCCH

Sub Domain 3 --
Measured Object TRX

Type Name Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC804a - NB_UL_SINGLE_BLOCK_SIG_RACH
Descripton

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 Radio Channel (Traffic Load)

Sub Domain 2 CCCH


Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements

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

Feature Name Enhanced Cell Re-selection (R97)

....................................................................................................................................................................................................................................
50-48 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC804b - NB_UL_ONE_PHASE_SIG_RACH
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

MC804b - NB_UL_ONE_PHASE_SIG_RACH
Descripton

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 Radio Channel (Traffic Load)


Sub Domain 2 CCCH

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

Feature Name Enhanced Cell Re-selection (R97)

MC805a - NB_CHANNEL_ASSIGN_DL_AGCH
Descripton

Long Name NB_CHANNEL_ASSIGN_DL_AGCH


Definition Number of Immediate Assignment messages sent on AGCH for GPRS traffic.
Trigger condition Whenever a Packet Downlink Assignment messages on Abis is sent for MS in non-DRX mode.
Sub Domain 1 Radio Channel (Traffic Load)
Sub Domain 2 CCCH

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Enhanced Cell Re-selection (R97)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-49
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC805b - NB_CHANNEL_ASSIGN_DL_PCH
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

MC805b - NB_CHANNEL_ASSIGN_DL_PCH
Descripton

Long Name NB_CHANNEL_ASSIGN_DL_PCH

Definition Number of Immediate Assignment messages sent on PCH for GPRS traffic.
Trigger condition Whenever a Packet Downlink Assignment messages on Abis is sent for MS in DRX mode.

Sub Domain 1 Radio Channel (Traffic Load)


Sub Domain 2 CCCH

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Enhanced Cell Re-selection (R97)

MC8a - NB_CELL_PAGING_CMD
Descripton

Long Name NB_CELL_PAGING_CMD


Definition MC8A= SUM (all TRX_TS of the Cell) C8A
Trigger condition --
Sub Domain 1 Radio Channel (Traffic Load)
Sub Domain 2 CCCH

Sub Domain 3 --

Measured Object Common cell


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

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
50-50 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC8b - NB_CELL_IMM_ASS_CMD
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

MC8b - NB_CELL_IMM_ASS_CMD
Descripton

Long Name NB_CELL_IMM_ASS_CMD

Definition MC8B= SUM (all TRX_TS of the Cell) C8B


Trigger condition --

Sub Domain 1 Radio Channel (Traffic Load)


Sub Domain 2 CCCH

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC8c - NB_CELL_CHAN_REQD
Descripton

Long Name NB_CELL_CHAN_REQD


Definition MC8C= SUM (all TRX_TS of the cell) C8C
Trigger condition --
Sub Domain 1 Radio Channel (Traffic Load)
Sub Domain 2 CCCH

Sub Domain 3 --

Measured Object Common cell


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

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-51
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC8d - NB_CELL_IMM_ASS_REJ
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

MC8d - NB_CELL_IMM_ASS_REJ
Descripton

Long Name NB_CELL_IMM_ASS_REJ

Definition MC8D= SUM (all TRX_TS of the cell) C8D


Trigger condition --

Sub Domain 1 Radio Channel (Traffic Load)


Sub Domain 2 CCCH

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC924a - TIME_SPDCH_LIMIT_HIGH_LOAD
Descripton

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 Radio Channel (Traffic Load)

Sub Domain 2 TCH


Sub Domain 3 --

Measured Object Common cell

Type Name Overview measurements


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

External Comment This counter replaces the B8 MFS counter P1.


Feature Name Autonomous Packet Resource Allocation (RAE-4)

....................................................................................................................................................................................................................................
50-52 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC925a - NB_AGCH_USEFUL_BLOCKS_SENT
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

MC925a - NB_AGCH_USEFUL_BLOCKS_SENT
Descripton

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 Radio Channel (Traffic Load)

Sub Domain 2 --
Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Multiple CCCH

MC925b - NB_PCH_USEFUL_BLOCKS_SENT
Descripton

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 Radio Channel (Traffic Load)

Sub Domain 2 --

Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Multiple CCCH

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-53
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC925c - NB_BUSY_RACH_SLOTS
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

MC925c - NB_BUSY_RACH_SLOTS
Descripton

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 Radio Channel (Traffic Load)


Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements

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

Feature Name Multiple CCCH

MC925d - NB_CHANNEL_RQ_RADIO
Descripton

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 Radio Channel (Traffic Load)


Sub Domain 2 --

....................................................................................................................................................................................................................................
50-54 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC925d - NB_CHANNEL_RQ_RADIO
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

Feature Name Multiple CCCH

MC925e - NB_ASSIGN_CMD_RECEIVED_ABIS
Descripton

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 Radio Channel (Traffic Load)

Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name Multiple CCCH

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-55
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC925f - NB_ASSIGN_CMD_DISCARDED
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

MC925f - NB_ASSIGN_CMD_DISCARDED
Descripton

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 Radio Channel (Traffic Load)

Sub Domain 2 --
Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name Multiple CCCH

MC925g - NB_PAGING_CMD_RECEIVED_ABIS
Descripton

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 Radio Channel (Traffic Load)


Sub Domain 2 --

Sub Domain 3 --

....................................................................................................................................................................................................................................
50-56 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC925g - NB_PAGING_CMD_RECEIVED_ABIS
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name Multiple CCCH

MC925h - NB_PAGING_CMD_DISCARDED
Descripton

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 Radio Channel (Traffic Load)
Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name Multiple CCCH

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-57
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC930 - NB_ABIS_PAGING_MESSAGE_RECEIVED
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

MC930 - NB_ABIS_PAGING_MESSAGE_RECEIVED
Descripton

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 Radio Channel (Traffic Load)

Sub Domain 2 --
Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name Multiple CCCH

MC961 - NB_CELL_CS_PAGING_WITH_IMSI
Descripton

Long Name NB_CELL_CS_PAGING_WITH_IMSI


Definition Number of CS 48.058 PAGING COMMAND message with IMSI
Trigger condition Whenever, for CS traffic only, a 48.058 PAGING COMMAND message with "Type of identity" of the "MS
Identity" MIE set to "IMSI" is about to be sent on the Abis interface to the related cell.
Sub Domain 1 Radio Channel (Traffic Load)

Sub Domain 2 CCCH

Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements

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

External Comment --

....................................................................................................................................................................................................................................
50-58 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC961 - NB_CELL_CS_PAGING_WITH_IMSI
Radio Channel (Traffic Load)
....................................................................................................................................................................................................................................

Feature Name A-Flex

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-59
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load Overview
Telecom Procedure (Traffic Load)
....................................................................................................................................................................................................................................

Telecom Procedure (Traffic Load)

Overview
Purpose
This section contains Telecom Procedure (Traffic Load) parameters.

Contents

MC13a - NB_TCH_NOR_ASS_QUEUED 50-60


MC13b - NB_INC_EXT_TCH_HO_QUEUED 50-61
MC144e - NB_OUT_IDR_REQ 50-62
MC144f - NB_OUT_EDR_REQ 50-62
MC147 - NB_INC_SDCCH_HO_ALLOC 50-63
MC148 - NB_IMM_ASS_ALLOC 50-63
MC15a - NB_INC_IDR_ALLOC 50-64
MC15b - NB_INC_TCH_HO_ALLOC 50-64
MC703 - NB_TCH_NOR_ASS_ALLOC_TRX 50-65
MC850 - NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL 50-65

MC13a - NB_TCH_NOR_ASS_QUEUED
Descripton

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 INDICATION message if the queuing is authorised by the MSC,
or,
ii) when the assignment request is queued in the cell if the queuing is not authorised by the MSC and the
parameter QUEUE_ANYWAY is set (in particular when the assignment request is queued due to a forced
directed retry (cause 20) or preferred band forced directed retry (cause 36)), 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".

....................................................................................................................................................................................................................................
50-60 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC13a - NB_TCH_NOR_ASS_QUEUED
Telecom Procedure (Traffic Load)
....................................................................................................................................................................................................................................

Sub Domain 1 Telecom Procedure (Traffic Load)

Sub Domain 2 Normal Assignment


Sub Domain 3 --

Measured Object Common cell


Type Name Overview measurements

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

Feature Name --

MC13b - NB_INC_EXT_TCH_HO_QUEUED
Descripton

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 Telecom Procedure (Traffic Load)
Sub Domain 2 Handover
Sub Domain 3 TCH
Measured Object Common cell

Type Name Overview measurements


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

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-61
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC144e - NB_OUT_IDR_REQ
Telecom Procedure (Traffic Load)
....................................................................................................................................................................................................................................

MC144e - NB_OUT_IDR_REQ
Descripton

Long Name NB_OUT_IDR_REQ

Definition MC144e=C144a+C144c
Trigger condition --

Sub Domain 1 Telecom Procedure (Traffic Load)


Sub Domain 2 Directed Retry

Sub Domain 3 Internal


Measured Object Common cell

Type Name Overview measurements


Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC144f - NB_OUT_EDR_REQ
Descripton

Long Name NB_OUT_EDR_REQ


Definition MC144f=C144b+C144d
Trigger condition --
Sub Domain 1 Telecom Procedure (Traffic Load)
Sub Domain 2 Directed Retry

Sub Domain 3 External

Measured Object Common cell


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

External Comment --

Feature Name --

....................................................................................................................................................................................................................................
50-62 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC147 - NB_INC_SDCCH_HO_ALLOC
Telecom Procedure (Traffic Load)
....................................................................................................................................................................................................................................

MC147 - NB_INC_SDCCH_HO_ALLOC
Descripton

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: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 1 Telecom Procedure (Traffic Load)

Sub Domain 2 Handover


Sub Domain 3 SDCCH

Measured Object Common cell


Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

MC148 - NB_IMM_ASS_ALLOC
Descripton

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 Telecom Procedure (Traffic Load)

Sub Domain 2 Immediate Assignment


Sub Domain 3 --

Measured Object Common cell

Type Name Overview measurements


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

External Comment --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-63
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC15a - NB_INC_IDR_ALLOC
Telecom Procedure (Traffic Load)
....................................................................................................................................................................................................................................

MC15a - NB_INC_IDR_ALLOC
Descripton

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 Overview measurements

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

Feature Name --

MC15b - NB_INC_TCH_HO_ALLOC
Descripton

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 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 any handover procedure.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 Telecom Procedure (Traffic Load)


Sub Domain 2 Handover

Sub Domain 3 TCH


Measured Object Common cell

Type Name Overview measurements

Type Definition Set of global counters providing an overview of each measurement type
External Comment --
Feature Name --

....................................................................................................................................................................................................................................
50-64 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC703 - NB_TCH_NOR_ASS_ALLOC_TRX
Telecom Procedure (Traffic Load)
....................................................................................................................................................................................................................................

MC703 - NB_TCH_NOR_ASS_ALLOC_TRX
Descripton

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 Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent on Abis Interface to activate a
TCH channel for normal assignment, or for DTM assignment with a TCH in signaling mode.
Sub Domain 1 Telecom Procedure (Traffic Load)

Sub Domain 2 Normal Assignment


Sub Domain 3 --
Measured Object TRX
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name B7.1 counters improvements

MC850 - NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-65
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC850 - NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL
Telecom Procedure (Traffic Load)
....................................................................................................................................................................................................................................

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 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".
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 Telecom Procedure (Traffic Load)


Sub Domain 2 Multiband

Sub Domain 3 --
Measured Object Common cell
Type Name Overview measurements
Type Definition Set of global counters providing an overview of each measurement type

External Comment --
Feature Name B7.1 counters improvements

....................................................................................................................................................................................................................................
50-66 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC850 - NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 50-67
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic Load MC850 - NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
50-68 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XXVI: BSC-TYPE 180 - 2G
Traffic flow measurements

Overview
Purpose
All type 180.

Contents

Chapter 51, Adjacency 51-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XXVI-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
BSC-TYPE 180 - 2G Traffic flow measurements Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XXVI-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
51 Adjacency
51

BSC

Overview
Purpose
This section contains BSC parameters.

Contents

C400 - NB_ADJ_BSC_INC_HO_REQ 51-1


C401 - NB_ADJ_BSC_INC_HO_ATPT 51-2
C402 - NB_ADJ_BSC_INC_HO_SUCC 51-3

C400 - NB_ADJ_BSC_INC_HO_REQ
Descripton

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').
Note: This counter counts both inter-PLMN and intra-PLMN handover events.

Sub Domain 1 BSC

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 51-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency C400 - NB_ADJ_BSC_INC_HO_REQ
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 --

Feature Name --

C401 - NB_ADJ_BSC_INC_HO_ATPT
Descripton

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 and target cell are provided in 48.008 HANDOVER 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 inter-PLMN and intra-PLMN handover events.

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

Feature Name --

....................................................................................................................................................................................................................................
51-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency C402 - NB_ADJ_BSC_INC_HO_SUCC
BSC
....................................................................................................................................................................................................................................

C402 - NB_ADJ_BSC_INC_HO_SUCC
Descripton

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 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 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 --
Feature Name --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 51-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Adjacency C402 - NB_ADJ_BSC_INC_HO_SUCC

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
51-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XXVII: MFS-GPRS Counters

Overview
Purpose
All MFS-GPRS.

Contents

Chapter 52, Quality of service 52-1


Chapter 53, Resource availability and usage 53-1
Chapter 54, Traffic load 54-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XXVII-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
MFS-GPRS Counters Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XXVII-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
52 Quality of service
52

Ater interface

P2a - NB_LAPD_INFO_FRAME_RESENT
Descripton

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
Feature Name /

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P2b - NB_LAPD_RNR_SENT
Ater interface
....................................................................................................................................................................................................................................

P2b - NB_LAPD_RNR_SENT
Descripton

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 The (decimal) value 1 000 000 means Driver LAPD not available. LAPD not established.
Note : P32 indicates the time the LAPD is not available
Feature Name /

P2c - NB_LAPD_RNR_REC
Descripton

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 The (decimal) value 1 000 000 means Driver LAPD not available. LAPD not established.
Note : P32 indicates the time the LAPD is not available
Feature Name /

....................................................................................................................................................................................................................................
52-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P2d - NB_LAPD_EST
Ater interface
....................................................................................................................................................................................................................................

P2d - NB_LAPD_EST
Descripton

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 The (decimal) value 1 000 000 means Driver LAPD not available. LAPD not established.
Note : P32 indicates the time the LAPD is not available
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P3a - NB_BEAR_CHAN_FRAMES_DISC_INVALID_FCS
Gb interface
....................................................................................................................................................................................................................................

Gb interface

P3a - NB_BEAR_CHAN_FRAMES_DISC_INVALID_FCS
Descripton

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 --
Feature Name /

P3b - NB_BEAR_CHAN_FRAMES_DISC_INVALID_ADDR
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
52-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P6a - NB_PVC_FRAMES_DISC_7_CONSEC_1
Gb interface
....................................................................................................................................................................................................................................

P6a - NB_PVC_FRAMES_DISC_7_CONSEC_1
Descripton

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 --
Feature Name /

P6b - NB_PVC_FRAMES_DISC_ZERO_INSER
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P6c - NB_PVC_FRAMES_DISC_LENGTH_TOO_LARGE
Gb interface
....................................................................................................................................................................................................................................

P6c - NB_PVC_FRAMES_DISC_LENGTH_TOO_LARGE
Descripton

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 --
Feature Name /

P6d - NB_PVC_FRAMES_DISC_LENGTH_TOO_SHORT
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
52-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P7a - NB_BSCGP_MSG_SENT
GSL
....................................................................................................................................................................................................................................

GSL

P7a - NB_BSCGP_MSG_SENT
Descripton

Long Name NB_BSCGP_MSG_SENT

Definition Number of BSCGP messages sent by the MFS to the BSC.


Trigger condition The counter is incremented each time a BSCGP message sent by the MFS to the BSC.

Sub Domain 1 GSL


Sub Domain 2 N/A

Sub Domain 3 N/A


Measured Object Sub_BSS (BSC/FABRIC)
External Comment --
Feature Name /

P7b - NB_BSCGP_MSG_DISCARDED
Descripton

Long Name NB_BSCGP_MSG_DISCARDED


Definition Number of BSCGP messages sent by MFS that are discarded.
Trigger condition Each time a BSCGP message sent by MFS is discarded, the counter is incremented.
Sub Domain 1 GSL
Sub Domain 2 N/A

Sub Domain 3 N/A


Measured Object Sub_BSS (BSC/FABRIC)

External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P7c_1 - CUMULATED_TIME_ONGOING_QUEUE_A_FULL
GSL
....................................................................................................................................................................................................................................

P7c_1 - CUMULATED_TIME_ONGOING_QUEUE_A_FULL
Descripton

Long Name CUMULATED_TIME_ONGOING_QUEUE_A_FULL

Definition This counter cumulates the time during which the on going QUEUE_A is full during the GP.
Trigger condition During the GP, the time during which the on going QUEUE_A is full, is cumulated.
The time is provided in seconds with one significant value after the comma (i.e. ROUND(10x) / 10).
Sub Domain 1 GSL

Sub Domain 2 N/A


Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)


External Comment --
Feature Name /

P7c_2 - CUMULATED_TIME_ONGOING_QUEUE_B_FULL
Descripton

Long Name CUMULATED_TIME_ONGOING_QUEUE_B_FULL


Definition This counter cumulates the time during which the on going QUEUE_B is full during the GP.
Trigger condition During the GP, the time during which the on going QUEUE_B is full is cumulated.
The time is provided in seconds with one significant value after the comma (i.e. ROUND(10x) / 10).
Sub Domain 1 GSL
Sub Domain 2 N/A

Sub Domain 3 N/A


Measured Object Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
52-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P7d - NB_BSCGP_MSG_RESENT
GSL
....................................................................................................................................................................................................................................

P7d - NB_BSCGP_MSG_RESENT
Descripton

Long Name NB_BSCGP_MSG_RESENT

Definition Number of BSCGP messages resent by the MFS to the BSC.


Trigger condition The counter is incremented each time a BSCGP message is resent by the MFS to the BSC.
Note:
- The initial sending is not taken into account.
- The BSCGP messages resent in infinite sending attempts are counted once.

Sub Domain 1 GSL

Sub Domain 2 N/A


Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)


External Comment --
Feature Name /

P7e - NB_BSCGP_MSG_RECEIVED
Descripton

Long Name NB_BSCGP_MSG_RECEIVED


Definition Number of BSCGP messages received by the MFS from the BSC.
Trigger condition The counter is incremented each time a BSCGP message is received by the MFS from the BSC.
Note: In case of RACH overflow on BSCGP, even the discarded BSCGP messages are counted.
Sub Domain 1 GSL

Sub Domain 2 N/A


Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)


External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P7f - NB_BSCGP_CHANNEL_REQ_RECEIVED
GSL
....................................................................................................................................................................................................................................

P7f - NB_BSCGP_CHANNEL_REQ_RECEIVED
Descripton

Long Name NB_BSCGP_CHANNEL_REQ_RECEIVED

Definition Number of BSCGP CHANNEL REQUEST and DTM REQUEST messages received by the MFS from the
BSC.
Trigger condition The counter is incremented each time a BSCGP CHANNEL REQUEST, DTM REQUEST messages are
received by the MFS from the BSC.

Sub Domain 1 GSL


Sub Domain 2 N/A

Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)


External Comment --

Feature Name /

P7g - NB_BSCGP_BYTES_SENT
Descripton

Long Name NB_BSCGP_BYTES_SENT


Definition Number of bytes of BSCGP messages sent by the MFS to the BSC.
Trigger condition The counter is incremented, each time a BSCGP message is sent by the MFS to the BSC, with the amount of
bytes of the message.
Sub Domain 1 GSL

Sub Domain 2 N/A


Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
52-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P7h - MAX_NB_BSCGP_BYTES_SENT
GSL
....................................................................................................................................................................................................................................

P7h - MAX_NB_BSCGP_BYTES_SENT
Descripton

Long Name MAX_NB_BSCGP_BYTES_SENT

Definition Maximum number of bytes of BSCGP messages sent by the MFS to the BSC in one minute.
Trigger condition During each minute of the GP, the number of bytes of BSCGP messages sent by the MFS is observed.
The counter reports the maximum of these values encountered during the GP.
Sub Domain 1 GSL

Sub Domain 2 N/A


Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)


External Comment --
Feature Name /

P7i - MAX_NB_BSCGP_MSG_SENT
Descripton

Long Name MAX_NB_BSCGP_MSG_SENT


Definition Maximum number of BSCGP messages sent by the MFS to the BSC in one minute.
Trigger condition During each minute of the GP, the number of BSCGP messages sent by MFS is observed.
The counter reports the maximum of these values encountered during the GP.
Sub Domain 1 GSL
Sub Domain 2 N/A

Sub Domain 3 N/A


Measured Object Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P105c - NB_DL_TBF_EST_FAIL_GPU_CONG
Radio interface
....................................................................................................................................................................................................................................

Radio interface

P105c - NB_DL_TBF_EST_FAIL_GPU_CONG
Descripton

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 --
Feature Name Support of GPRS QoS

P105d - NB_UL_TBF_EST_FAIL_GPU_CONG
Descripton

Long Name NB_UL_TBF_EST_FAIL_GPU_CONG


Definition Number of UL TBF establishment failures due to GPU congestion.
Note: This counter applies to GPRS and EGPRS MS.
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

....................................................................................................................................................................................................................................
52-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P105d - NB_UL_TBF_EST_FAIL_GPU_CONG
Radio interface
....................................................................................................................................................................................................................................

Measured Object Cell

External Comment --
Feature Name /

P105e - NB_DL_TBF_EST_FAIL_CPU_GPU
Descripton

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 DL TBF establishments


Sub Domain 3 N/A

Measured Object Cell


External Comment --
Feature Name /

P105f - NB_UL_TBF_EST_FAIL_CPU_GPU
Descripton

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 UL TBF establishments

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P105g - NB_DL_TBF_EST_FAIL_CONG_ATER
Radio interface
....................................................................................................................................................................................................................................

P105g - NB_DL_TBF_EST_FAIL_CONG_ATER
Descripton

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.
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 DL TBF establishments
Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name Enhanced Transmission Resource Management

P105h - NB_UL_TBF_EST_FAIL_CONG_ATER
Descripton

Long Name NB_UL_TBF_EST_FAIL_CONG_ATER


Definition Number of UL TBF establishment failures due to a lack of Ater resources.
Note: This counter applies to GPRS and EGPRS MS.

Trigger condition The counter is incremented whenever a UL TBF establishment fails due to a 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.
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

....................................................................................................................................................................................................................................
52-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P105h - NB_UL_TBF_EST_FAIL_CONG_ATER
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 2 UL TBF establishments

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name Enhanced Transmission Resource Management

P105i - NB_DL_TBF_EST_FAIL_CONG_ABIS
Descripton

Long Name NB_DL_TBF_EST_FAIL_CONG_ABIS


Definition Number of DL TBF establishment failures due to a lack of Abis resources.
Note: This counter applies to GPRS and EGPRS MS.
Trigger condition The counter is incremented whenever a DL TBF establishment fails due to a 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.
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 DL TBF establishments


Sub Domain 3 N/A

Measured Object Cell


External Comment --
Feature Name Enhanced Transmission Resource Management

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P105j - NB_UL_TBF_EST_FAIL_CONG_ABIS
Radio interface
....................................................................................................................................................................................................................................

P105j - NB_UL_TBF_EST_FAIL_CONG_ABIS
Descripton

Long Name NB_UL_TBF_EST_FAIL_CONG_ABIS

Definition Number of UL TBF establishment failures due to a lack of Abis resources.


Note: This counter applies to GPRS and EGPRS MS.

Trigger condition The counter is incremented whenever a UL TBF establishment fails 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.
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 UL TBF establishments

Sub Domain 3 N/A


Measured Object Cell
External Comment --
Feature Name Enhanced Transmission Resource Management

....................................................................................................................................................................................................................................
52-16 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P105k - NB_DL_TBF_EST_FAIL_TOO_MANY_TBF
Radio interface
....................................................................................................................................................................................................................................

P105k - NB_DL_TBF_EST_FAIL_TOO_MANY_TBF
Descripton

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_GP[U] constraint.
- or the TRX cannot be established or created.
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 (TDM mode).
For BTS evolium:
The number of GCH available (excluding those currently reserved for release) to serve the DL TBF is less
than Min_Nb_GCH and less than Nb_GCH_For_TBF_Estab.
2) or the MAX_TBF_TRX_DL_GP[U] constraint (TDM mode).
For BTS evolium:
The MAX_TBF_TRX_DL_GP[U] limit is reached on all the TRXs available for PS traffic in the cell.
Note: this counter is not incremented for RT PFCs.
3) or the TRX cannot be established or created (TDM or IP mode).
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_GP[U] constraint or due to the failure to establish or
create the TRX.
Sub Domain 1 Radio interface
Sub Domain 2 DL TBF establishments
Sub Domain 3 N/A
Measured Object Cell
External Comment --

Feature Name Enhanced Transmission Resource Management

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-17
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P105l - NB_UL_TBF_EST_FAIL_TOO_MANY_TBF
Radio interface
....................................................................................................................................................................................................................................

P105l - NB_UL_TBF_EST_FAIL_TOO_MANY_TBF
Descripton

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_GP[U] constraint.
- or the TRX cannot be established or created.
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 (TDM mode).
For BTS evolium:
The number of GCH available (excluding those currently reserved for release) to serve the UL TBF is less
than Min_Nb_GCH and less than Nb_GCH_For_TBF_Estab.
2) or the MAX_TBF_TRX_UL_GP[U] constraint (TDM mode).
For BTS evolium:
The MAX_TBF_TRX_UL_GP[U] limit is reached on all the TRXs available for PS traffic in the cell.
3) or the TRX cannot be established or created (TDM or IP mode).
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_GP[U] constraint or due to the failure
to establish or create the TRX.
Sub Domain 1 Radio interface
Sub Domain 2 UL TBF establishments

Sub Domain 3 N/A


Measured Object Cell
External Comment --

Feature Name Enhanced Transmission Resource Management

....................................................................................................................................................................................................................................
52-18 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P105m - NB_DL_TBF_EST_FAIL_PTU_CONG
Radio interface
....................................................................................................................................................................................................................................

P105m - NB_DL_TBF_EST_FAIL_PTU_CONG
Descripton

Long Name NB_DL_TBF_EST_FAIL_PTU_CONG

Definition Number of DL TBF establishment failures due to PTU congestion.


Note: This counter applies to GPRS and EGPRS MS.

Trigger condition When a DL TBF cannot be established, due to PTU congestion. PTU congestion means that the maximum
capacity of one PTU is reached in terms of resources TBF or memory.
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 --
Feature Name IP transport in the BSS

P105n - NB_UL_TBF_EST_FAIL_PTU_CONG
Descripton

Long Name NB_UL_TBF_EST_FAIL_PTU_CONG


Definition Number of UL TBF establishment failures due to PTU congestion.
Note: This counter applies to GPRS and EGPRS MS.
Trigger condition When an UL TBF cannot be established, due to PTU congestion. PTU congestion means that the maximum
capacity is reached in terms of resources TBF or memory.
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 --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-19
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P105o - NB_DL_TBF_EST_FAIL_GPU_BUFFER_CONG
Radio interface
....................................................................................................................................................................................................................................

P105o - NB_DL_TBF_EST_FAIL_GPU_BUFFER_CONG
Descripton

Long Name NB_DL_TBF_EST_FAIL_GPU_BUFFER_CONG

Definition Number of DL TBF establishment failures due to GPU buffer congestion.


Note: This counter applies to GPRS and EGPRS MS.

Trigger condition When a DL TBF cannot be established, due to GPU buffer congestion.
Generally, for all counters related to TBF establishment failures, only the last reported failure cause is taken
into account.
Note:
*) At 1st level of GPU buffer congestion, only DL LLC PDU for MS in PIM or in dedicated mode are
concerned.
**) At 2nd level of GPU buffer congestion, any DL LLC PDU is concerned.
***) P105o can be incremented only once during a buffer congestion period.
Sub Domain 1 Radio interface
Sub Domain 2 DL TBF establishments

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name MFS Defence and Investigation Facilities

P105p - NB_UL_TBF_EST_FAIL_GPU_BUFFER_CONG
Descripton

Long Name NB_UL_TBF_EST_FAIL_GPU_BUFFER_CONG


Definition Number of UL TBF establishment failures due to GPU buffer congestion.
Note: This counter applies to GPRS and EGPRS MS.
Trigger condition When an UL TBF cannot be established, due to GPU buffer congestion.
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 44.060 PACKET MEASUREMENT REPORT message or a 44.060 PACKET CELL CHANGE
FAILURE message.
**) This concerns MS in PIM or in dedicated mode. In case of MS in dedicated mode, a DTM reject is sent.

Sub Domain 1 Radio interface


Sub Domain 2 UL TBF establishments

....................................................................................................................................................................................................................................
52-20 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P105p - NB_UL_TBF_EST_FAIL_GPU_BUFFER_CONG
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name MFS Defence and Investigation Facilities

P106 - NB_TBF_EST_SUCC_GPU
Descripton

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 --
Feature Name /

P107 - NB_TBF_EST_REQ_GPU
Descripton

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 Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-21
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P11 - NB_DL_TBF_REL_GB_PB_MStransDL
Radio interface
....................................................................................................................................................................................................................................

P11 - NB_DL_TBF_REL_GB_PB_MStransDL
Descripton

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

Feature Name /

P14 - NB_DL_TBF_EST_FAIL_CONG
Descripton

Long Name NB_DL_TBF_EST_FAIL_CONG


Definition Number of DL TBF establishment failures due to a lack of radio resources.
Note: This counter applies to GPRS and EGPRS MS.
Trigger condition The counter is incremented whenever a DL TBF establishment fails due to a 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 DL TBF establishments

Sub Domain 3 N/A

Measured Object Cell


External Comment --
Feature Name /

....................................................................................................................................................................................................................................
52-22 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P146 - NB_DL_TBF_REL_PREEMPTradio
Radio interface
....................................................................................................................................................................................................................................

P146 - NB_DL_TBF_REL_PREEMPTradio
Descripton

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.
Trigger condition i) Each time that upon T_PDCH pre-emption timer expiry for lack of resources (T1 TBF reallocation
failure), a DL TBF is released.
ii) 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.
Note: ii) is not significant in IP transport.

Sub Domain 1 Radio interface


Sub Domain 2 DL TBF releases

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P147 - NB_UL_TBF_REL_PREEMPTradio
Descripton

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 i)Each time that upon T_PDCH_pre-emption timer expiry for lack of resources (T1 TBF reallocation
failure), an UL TBF is released.
ii)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.
Note: ii) is not significant in IP transport.

Sub Domain 1 Radio interface


Sub Domain 2 UL TBF releases

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-23
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P15 - NB_DL_TBF_EST_FAIL_RADIO_PB
Radio interface
....................................................................................................................................................................................................................................

P15 - NB_DL_TBF_EST_FAIL_RADIO_PB
Descripton

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 DL TBF establishments
Sub Domain 3 N/A
Measured Object Cell
External Comment --

Feature Name /

P181a - NB_DL_TBF_REL_SIG
Descripton

Long Name NB_DL_TBF_REL_SIG


Definition Number of DL TBF released which carries signalling data.
Trigger condition Each time a DL TBF is released (normaly or abnormaly) and its traffic type is signaling at release time, the
counter is incremented.
Sub Domain 1 Radio interface

Sub Domain 2 DL TBF releases

Sub Domain 3 N/A


Measured Object Cell
External Comment --

Feature Name /

....................................................................................................................................................................................................................................
52-24 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P181b - NB_UL_TBF_REL_SIG
Radio interface
....................................................................................................................................................................................................................................

P181b - NB_UL_TBF_REL_SIG
Descripton

Long Name NB_UL_TBF_REL_SIG

Definition Number of UL TBF released which carries signalling data.


Trigger condition Each time an UL TBF is released (normaly or abnormaly) and its traffic type is signaling at release time, the
counter is incremented.

Sub Domain 1 Radio interface


Sub Domain 2 UL TBF releases

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P182a - NB_SERVING_INTER_BSS_NACC
Descripton

Long Name NB_SERVING_INTER_BSS_NACC


Definition Number of received RAN_Information_Req from a controlling BSS.
Trigger condition Within the granularity period, this counter counts the number of RAN_INFORMATION_REQUEST
received from a BSS (both single and multiple reports but not stop).

Sub Domain 1 Radio interface


Sub Domain 2 Cell reselections
Sub Domain 3 RIM-NACC
Measured Object Cell

External Comment --

Feature Name Inter-BSS/Inter-RAT NACC

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-25
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P182b - NB_SERVING_INTER_RAT_NACC
Radio interface
....................................................................................................................................................................................................................................

P182b - NB_SERVING_INTER_RAT_NACC
Descripton

Long Name NB_SERVING_INTER_RAT_NACC

Definition Number of received RAN_Information_Req from a controlling RNC.


Trigger condition Within the granularity period, this counter counts the number of RAN_INFORMATION_REQUEST
received from a RNC (both single and multiple reports but not stop).

Sub Domain 1 Radio interface


Sub Domain 2 Cell reselections

Sub Domain 3 RIM-NACC


Measured Object Cell

External Comment --
Feature Name Inter-BSS/Inter-RAT NACC

P182c - NB_CONTROLLING_INTER_BSS_NACC
Descripton

Long Name NB_CONTROLLING_INTER_BSS_NACC


Definition Number of successfull RAN-Information requests sent to an another BSS.
Trigger condition Within the granularity period, this counter is incremented when a RAN-Information Initial is received from
an other BSS in response to RAN-information-request.
Note: This counter is per target cell.
Sub Domain 1 Radio interface
Sub Domain 2 Cell reselections
Sub Domain 3 RIM-NACC

Measured Object ADJ_cell


External Comment --

Feature Name Inter-BSS/Inter-RAT NACC

....................................................................................................................................................................................................................................
52-26 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P182d - NB_RAN_INFO_REQ_INTER_BSS_NACC
Radio interface
....................................................................................................................................................................................................................................

P182d - NB_RAN_INFO_REQ_INTER_BSS_NACC
Descripton

Long Name NB_RAN_INFO_REQ_INTER_BSS_NACC

Definition Number of RAN_Information_Req sent towards a BSS.


Trigger condition Within the granularity period, each time a RAN_INFORMATION_REQUEST with indication Single Report
or Multiple Report is sent towards a BSS, the counter is incremented. RAN_INFORMATION_REQUEST
with indication Stop are not counted.
The retries are taken into account.
Note: This counter is per target cell.

Sub Domain 1 Radio interface


Sub Domain 2 Cell reselections

Sub Domain 3 RIM-NACC


Measured Object ADJ_cell

External Comment --
Feature Name Inter-BSS/Inter-RAT NACC

P182e - TIME_RIM_NACC_PROC_SUCC
Descripton

Long Name TIME_RIM_NACC_PROC_SUCC


Definition Time duration of succesfull RIM procedures.
Trigger condition The counter cumulates , over the granularity period, the duration of each successfull RIM procedure i.e. the
time between RAN_Informatrion_Request and the 1st received RAN_Information/Initial, Multiple report in
response.
Note 1: This counter is per target cell
Note 2: The time is provided in seconds with one significant value after the comma (i.e. ROUND(10x) / 10):
for example, if the time is 15.1 seconds, this duration of time is provided with the number 151.

Sub Domain 1 Radio interface


Sub Domain 2 Cell reselections

Sub Domain 3 RIM-NACC


Measured Object ADJ_cell

External Comment --
Feature Name Inter-BSS/Inter-RAT NACC

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-27
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P182f - NB_SERVING_INTER_LTE_NACC
Radio interface
....................................................................................................................................................................................................................................

P182f - NB_SERVING_INTER_LTE_NACC
Descripton

Long Name NB_SERVING_INTER_LTE_NACC

Definition Number of received RAN_Information_Req from a controlling eNodeB.


Trigger condition Within the granularity period, this counter counts the number of RAN_INFORMATION_REQUEST
received from a eNodeB (both single and multiple reports).

Sub Domain 1 Radio interface


Sub Domain 2 Cell reselections

Sub Domain 3 RIM-NACC


Measured Object Cell

External Comment --
Feature Name Inter-BSS/Inter-RAT NACC

P200 - NB_DOWNGRADED_MOVING_RT_PFC
Descripton

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

Feature Name Support of GPRS QoS

....................................................................................................................................................................................................................................
52-28 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P203 - NB_DL_TBF_EST_FAIL_PTU_LOAD
Radio interface
....................................................................................................................................................................................................................................

P203 - NB_DL_TBF_EST_FAIL_PTU_LOAD
Descripton

Long Name NB_DL_TBF_EST_FAIL_PTU_LOAD

Definition Number of DL TBF establishment failures due to PTUs 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 PTU in load/overload.
Sub Domain 1 Radio interface

Sub Domain 2 DL TBF establishments


Sub Domain 3 N/A

Measured Object Cell


External Comment --
Feature Name Enhanced Transmission Resource Management

P204 - NB_UL_TBF_EST_FAIL_PTU_LOAD
Descripton

Long Name NB_UL_TBF_EST_FAIL_PTU_LOAD


Definition Number of UL TBF establishment failures due to PTUs 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 PTU in load/overload.
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 UL TBF establishments

Sub Domain 3 N/A

Measured Object Cell


External Comment --
Feature Name Enhanced Transmission Resource Management

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-29
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P207 - NB_DL_TBF_REL_DL_DELAYED
Radio interface
....................................................................................................................................................................................................................................

P207 - NB_DL_TBF_REL_DL_DELAYED
Descripton

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

Feature Name /

P208 - NB_UL_TBF_REL_EXTENDED_UL
Descripton

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 (N3101 exceeds its limit).
- 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 --

Feature Name /

....................................................................................................................................................................................................................................
52-30 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P209 - TIME_SOURCE_NC2_CELL_RESEL
Radio interface
....................................................................................................................................................................................................................................

P209 - TIME_SOURCE_NC2_CELL_RESEL
Descripton

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 Cell reselections in NC2

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.

Feature Name /

P210 - TIME_TARGET_NC2_CELL_RESEL
Descripton

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 Cell reselections in NC2

Sub Domain 3 N/A

Measured Object Cell

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-31
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P210 - TIME_TARGET_NC2_CELL_RESEL
Radio interface
....................................................................................................................................................................................................................................

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.
Feature Name /

P211 - NB_TARGET_NC2_CELL_RESEL
Descripton

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 Cell reselections in NC2

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.
Feature Name /

....................................................................................................................................................................................................................................
52-32 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P212 - TIME_SOURCE_NACC_CELL_RESEL
Radio interface
....................................................................................................................................................................................................................................

P212 - TIME_SOURCE_NACC_CELL_RESEL
Descripton

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.
Note: Intra-BSS NACC and Inter-BSS NACC are taken into account.
Sub Domain 1 Radio interface
Sub Domain 2 Cell reselections

Sub Domain 3 NACC


Measured Object Cell

External Comment --
Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)

P213 - NB_SOURCE_NACC_CELL_RESEL
Descripton

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.
Note: Intra-BSS NACC and Inter-BSS NACC are taken into account.
Sub Domain 1 Radio interface

Sub Domain 2 Cell reselections


Sub Domain 3 NACC

Measured Object Cell

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-33
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P213 - NB_SOURCE_NACC_CELL_RESEL
Radio interface
....................................................................................................................................................................................................................................

External Comment --

Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)

P214 - NB_UL_TBF_ENT_EXTENDED_UPLINK
Descripton

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 UL TBF establishments


Sub Domain 3 N/A

Measured Object Cell


External Comment --
Feature Name Extended UL TBF mode

P215 - NB_UL_TBF_RESUME_IN_EXTENDED_UPLINK
Descripton

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 UL TBF establishments


Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name Extended UL TBF mode

....................................................................................................................................................................................................................................
52-34 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P22 - NB_UL_TBF_NORM_REL
Radio interface
....................................................................................................................................................................................................................................

P22 - NB_UL_TBF_NORM_REL
Descripton

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

Feature Name /

P220 - NB_MOVING_RT_PFC
Descripton

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

Feature Name Support of GPRS QoS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-35
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P221 - NB_PCCO_ACK_UL_NC2_CELL_RESEL
Radio interface
....................................................................................................................................................................................................................................

P221 - NB_PCCO_ACK_UL_NC2_CELL_RESEL
Descripton

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 Cell reselections in NC2


Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P222 - NB_PCCO_ACK_DL_NC2_CELL_RESEL
Descripton

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 Cell reselections in NC2

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
52-36 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P223 - NB_PCCO_NC2_CELL_RESEL_DL_TBF
Radio interface
....................................................................................................................................................................................................................................

P223 - NB_PCCO_NC2_CELL_RESEL_DL_TBF
Descripton

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 Cell reselections in NC2

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.
Feature Name /

P224 - NB_FLUSH_NC2_CELL_RESEL_DL_TBF
Descripton

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 Cell reselections in NC2
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.

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-37
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P225 - NB_PCCF_NC2_CELL_RESEL_DL_TBF
Radio interface
....................................................................................................................................................................................................................................

P225 - NB_PCCF_NC2_CELL_RESEL_DL_TBF
Descripton

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 Cell reselections in NC2

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

Feature Name /

P226 - NB_PCCO_NC2_CELL_RESEL_UL_TBF
Descripton

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 Cell reselections in NC2
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.
Feature Name /

....................................................................................................................................................................................................................................
52-38 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P227 - NB_FLUSH_NC2_CELL_RESEL_UL_TBF
Radio interface
....................................................................................................................................................................................................................................

P227 - NB_FLUSH_NC2_CELL_RESEL_UL_TBF
Descripton

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 Cell reselections in NC2

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.

Feature Name /

P228 - NB_PCCF_NC2_CELL_RESEL_UL_TBF
Descripton

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 Cell reselections in NC2


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.

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-39
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P229 - NB_RT_PFC_PREEMPTED
Radio interface
....................................................................................................................................................................................................................................

P229 - NB_RT_PFC_PREEMPTED
Descripton

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 --
Feature Name Support of GPRS QoS

P22a - NB_UL_TBF_NORM_REL_EGPRS
Descripton

Long Name NB_UL_TBF_NORM_REL_EGPRS


Definition Number of UL TBFin EGPRS mode 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.
Note: The counter only concerns TBF in EGPRS mode.

Sub Domain 1 Radio interface


Sub Domain 2 UL TBF releases

Sub Domain 3 N/A

Measured Object Cell


External Comment --
Feature Name /

....................................................................................................................................................................................................................................
52-40 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P231 - NB_DOWNGRADED_RT_PFC_DEFENCE
Radio interface
....................................................................................................................................................................................................................................

P231 - NB_DOWNGRADED_RT_PFC_DEFENCE
Descripton

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 --
Feature Name Support of GPRS QoS

P232 - NB_MOVING_RT_PFC_TARGET
Descripton

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

Feature Name Support of GPRS QoS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-41
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P24 - NB_UL_TBF_REL_GB_PB_MStransUL
Radio interface
....................................................................................................................................................................................................................................

P24 - NB_UL_TBF_REL_GB_PB_MStransUL
Descripton

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

Feature Name /

P27 - NB_UL_TBF_EST_FAIL_CONG
Descripton

Long Name NB_UL_TBF_EST_FAIL_CONG


Definition Number of UL TBF establishment failures due to a lack of radio resources.
Note: This counter applies to GPRS and EGPRS MS.
Trigger condition The counter is incremented whenever an UL TBF establishment fails due to a 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 UL TBF establishments

Sub Domain 3 N/A

....................................................................................................................................................................................................................................
52-42 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P27 - NB_UL_TBF_EST_FAIL_CONG
Radio interface
....................................................................................................................................................................................................................................

Measured Object Cell

External Comment --
Feature Name /

P28 - NB_UL_TBF_EST_FAIL_RADIO_PB
Descripton

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 UL TBF establishments
Sub Domain 3 N/A
Measured Object Cell

External Comment --
Feature Name /

P302b_1 - NB_DL_TBF_REL_DUE_TO_RADIO_FAILURE_N3105
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-43
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P302b_1 - NB_DL_TBF_REL_DUE_TO_RADIO_FAILURE_N3105
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P302b_2 - NB_DL_TBF_REL_DUE_TO_RADIO_FAILURE_TX_EFF
Descripton

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 --
Feature Name /

P302c_1 - NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N3101
Descripton

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 radio failure is:
- a radio link lost due to N3101 (N3101 exceeds its limit)

Trigger condition A UL TBF is released because of a radio failure.


Considered radio failure is:
- a radio link lost due to N3101 (N3101 exceeds its limit)

Sub Domain 1 Radio interface

Sub Domain 2 UL TBF releases

....................................................................................................................................................................................................................................
52-44 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P302c_1 - NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N3101
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P302c_2 - NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N3103
Descripton

Long Name NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N3103

Definition Number of times a UL TBF is released because of a radio failure.


Considered radio failure is:
- a radio link lost due to N3103 (N3103 exceeds its limit)
Trigger condition A UL TBF is released because of a radio failure.
Considered radio failure is:
- a radio link lost due to N3103 (N3103 exceeds its limit)
Sub Domain 1 Radio interface
Sub Domain 2 UL TBF releases
Sub Domain 3 N/A
Measured Object Cell

External Comment --
Feature Name /

P302c_3 - NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_TX_EFF
Descripton

Long Name NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_TX_EFF


Definition Number of times a UL TBF is released because of a radio failure.
Considered 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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-45
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P302c_3 - NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_TX_EFF
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P302c_4 - NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N-
_POLLING_EUTM
Descripton

Long Name NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N_POLLING_EUTM


Definition Number of times a UL TBF is released because of a radio failure.
Considered radio failure is:
- a radio link lost due to N_POLLING_EUTM (N_POLLING_EUTM exceeds its limit)
Trigger condition A UL TBF is released because of a radio failure.
Considered radio failure is:
- a 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 --
Feature Name /

P303a - NB_ABNORMAL_DL_TBF_REL
Descripton

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.

....................................................................................................................................................................................................................................
52-46 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P303a - NB_ABNORMAL_DL_TBF_REL
Radio interface
....................................................................................................................................................................................................................................

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 --
Feature Name /

P303b - NB_ABNORMAL_UL_TBF_REL
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-47
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P303b - NB_ABNORMAL_UL_TBF_REL
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P30a - NB_UL_TBF_EST_SUCC_MSidle_MastChan
Descripton

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 counter applies to GPRS and EGPRS MS.
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 UL TBF establishments
Sub Domain 3 N/A
Measured Object Cell
External Comment --

Feature Name /

P30b - NB_UL_TBF_EST_SUCC_MStransDL
Descripton

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 UL TBF establishments
Sub Domain 3 N/A

....................................................................................................................................................................................................................................
52-48 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P30b - NB_UL_TBF_EST_SUCC_MStransDL
Radio interface
....................................................................................................................................................................................................................................

Measured Object Cell

External Comment --
Feature Name /

P30c - NB_UL_TBF_EST_SUCC_MSidle_NO_MastChan
Descripton

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 counter applies to GPRS and EGPRS MS.
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 UL TBF establishments
Sub Domain 3 N/A
Measured Object Cell
External Comment --

Feature Name /

P30e - NB_UL_TBF_EST_SUCC_EGPRS_MStransDL
Descripton

Long Name NB_UL_TBF_EST_SUCC_EGPRS_MStransDL

Definition Number of UL TBFsuccesfully established in EGPRS mode when the MS is in downlink packet transfer
mode.

Trigger condition When the TBF start indication is received during an UL TBF establishment in EGPRS mode on PACCH.
Sub Domain 1 Radio interface

Sub Domain 2 UL TBF establishments


Sub Domain 3 N/A

Measured Object Cell

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-49
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P30e - NB_UL_TBF_EST_SUCC_EGPRS_MStransDL
Radio interface
....................................................................................................................................................................................................................................

External Comment --

Feature Name /

P385a - NB_DL_TBF_REL_STAGWINDOW
Descripton

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 --
Feature Name /

P385b - NB_UL_TBF_REL_STAGWINDOW
Descripton

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

....................................................................................................................................................................................................................................
52-50 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P385b - NB_UL_TBF_REL_STAGWINDOW
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 2 UL TBF releases

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P396a - NB_RLC_DL_TBF_RELEASE_REQ_FOR_CR
Descripton

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 --
Feature Name /

P396b - NB_RLC_UL_TBF_RELEASE_REQ_FOR_CR
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-51
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P396b - NB_RLC_UL_TBF_RELEASE_REQ_FOR_CR
Radio interface
....................................................................................................................................................................................................................................

Feature Name /

P397 - NB_FLUSH_MESSAGES
Descripton

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
Feature Name /

P403a - NB_DL_RES_REALLOC_REQ_T1
Descripton

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 impacted TBFs of those Mobile Stations (thanks to trigger T1).

....................................................................................................................................................................................................................................
52-52 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P403a - NB_DL_RES_REALLOC_REQ_T1
Radio interface
....................................................................................................................................................................................................................................

Trigger condition The counter is incremented by one each time a downlink TBF (or its concurrent uplink TBF) is impacted by
a CS pre-emption process.
Three cases are possible:
Case 1) a downlink TBF has its PACCH impacted by a soft PDCH pre-emption,
Case 2) 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-pre-empted 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
pre-emption 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, see Note 1.
Case 3) In case where a downlink TBF is not impacted as described in Case 1 or Case 2, the counter is also
incremented by one each time this non-impacted downlink TBF has a concurrent uplink TBF impacted by
the CS pre-emption process (see the conditions to increment counter P404a).
In all above cases, the MFS will try to reallocate the impacted resources of the MS, which will require
reallocating the TBFs in one or in both directions.
Note 1: Case 2 is not significant in IP transport.

Sub Domain 1 Radio interface


Sub Domain 2 DL TBF re-allocations
Sub Domain 3 T1
Measured Object Cell
External Comment --
Feature Name Enhanced Transmission Resource Management

P403b - NB_DL_RES_REALLOC_REQ_T2
Descripton

Long Name NB_DL_RES_REALLOC_REQ_T2


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 DL TBF re-allocations

Sub Domain 3 T2

Measured Object Cell


External Comment --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-53
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P403b - NB_DL_RES_REALLOC_REQ_T2
Radio interface
....................................................................................................................................................................................................................................

Feature Name /

P403c - NB_DL_RES_REALLOC_REQ_T3
Descripton

Long Name NB_DL_RES_REALLOC_REQ_T3

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 DL TBF re-allocations
Sub Domain 3 T3
Measured Object Cell

External Comment --
Feature Name /

P403d - NB_DL_RES_REALLOC_REQ_T4
Descripton

Long Name NB_DL_RES_REALLOC_REQ_T4

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.

....................................................................................................................................................................................................................................
52-54 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P403d - NB_DL_RES_REALLOC_REQ_T4
Radio interface
....................................................................................................................................................................................................................................

Trigger condition Upon each expiry of T_CANDIDATE_TBF_REALLOC, the counter is incremented 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 DL TBF re-allocations


Sub Domain 3 T4

Measured Object Cell


External Comment --

Feature Name /

P404a - NB_UL_RES_REALLOC_REQ_T1
Descripton

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
impacted TBFs of those Mobile Stations (thanks to trigger T1).

Trigger condition The counter is incremented by one each time an uplink TBF (or its concurrent downlink TBF) is impacted
by a CS pre-emption process.
Three cases are possible:
Case 1) an uplink TBF has its PACCH impacted by a soft PDCH pre-emption,
Case 2) the maximum allowed (M)CS of an uplink TBF (taking into account the number of GCHs and also
the EGPRS capability of the MS (i.e. limitation to MCS-4 for an UL EGPRS TBF if the MS is not 8-PSK
capable)) 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
an 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, see Note 1.
Case 3) In case where an uplink TBF is not impacted as described in Case 1 or Case 2, the counter is also
incremented by one each time this non-impacted uplink TBF has a concurrent downlink TBF impacted by
the CS pre-emption process (see the conditions to increment counter P403a).
In all above cases, the MFS will try to reallocate the impacted resources of the MS, which will require
reallocating the TBFs in one or in both directions.
Note 1: Case 2 is not significant in IP transport.

Sub Domain 1 Radio interface

Sub Domain 2 UL TBF re-allocations

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-55
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P404a - NB_UL_RES_REALLOC_REQ_T1
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 T1

Measured Object Cell


External Comment --

Feature Name Support of GPRS QoS

P404b - NB_UL_RES_REALLOC_REQ_T2
Descripton

Long Name NB_UL_RES_REALLOC_REQ_T2

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 UL TBF re-allocations


Sub Domain 3 T2
Measured Object Cell
External Comment --
Feature Name /

P404c - NB_UL_RES_REALLOC_REQ_T3
Descripton

Long Name NB_UL_RES_REALLOC_REQ_T3


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.

....................................................................................................................................................................................................................................
52-56 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P404c - NB_UL_RES_REALLOC_REQ_T3
Radio interface
....................................................................................................................................................................................................................................

Trigger condition Upon each expiry of T_CANDIDATE_TBF_REALLOC, the counter is incremented 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 UL TBF re-allocations

Sub Domain 3 T3

Measured Object Cell


External Comment --

Feature Name /

P404d - NB_UL_RES_REALLOC_REQ_T4
Descripton

Long Name NB_UL_RES_REALLOC_REQ_T4


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 Upon each expiry of T_CANDIDATE_TBF_REALLOC, the counter is incremented 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 UL TBF re-allocations
Sub Domain 3 T4

Measured Object Cell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-57
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P405a - NB_DL_RES_REALLOC_SUCC_T1
Radio interface
....................................................................................................................................................................................................................................

P405a - NB_DL_RES_REALLOC_SUCC_T1
Descripton

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 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 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 DL TBF re-allocations
Sub Domain 3 T1

Measured Object Cell


External Comment --
Feature Name /

P405b - NB_DL_RES_REALLOC_SUCC_T2
Descripton

Long Name NB_DL_RES_REALLOC_SUCC_T2


Definition Number of resource reallocation attempts that lead to reallocating successfully a downlink TBF (due to
trigger T2).
Trigger condition A PACKET CONTROL ACKNOWLEDGEMENT is received following a resource 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 DL TBF re-allocations

....................................................................................................................................................................................................................................
52-58 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P405b - NB_DL_RES_REALLOC_SUCC_T2
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 T2

Measured Object Cell


External Comment --

Feature Name /

P405c - NB_DL_RES_REALLOC_SUCC_T3
Descripton

Long Name NB_DL_RES_REALLOC_SUCC_T3

Definition Number of resource reallocation attempts that lead to reallocating successfully a downlink TBF (due to
trigger T3).
Trigger condition A PACKET CONTROL ACKNOWLEDGEMENT is received following a resource reallocation attempt for
a downlink TBF due to T3. If the PACKET CONTROL ACKNOWLEDGEMENT acknowledges
reallocation of both an uplink and a 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 compute the success rate of the reallocation execution phase.
Sub Domain 1 Radio interface
Sub Domain 2 DL TBF re-allocations
Sub Domain 3 T3

Measured Object Cell


External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-59
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P405d - NB_DL_RES_REALLOC_SUCC_T4
Radio interface
....................................................................................................................................................................................................................................

P405d - NB_DL_RES_REALLOC_SUCC_T4
Descripton

Long Name NB_DL_RES_REALLOC_SUCC_T4

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 resource reallocation algorithm is run for a candidate Mobile Station having two 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 DL TBF re-allocations


Sub Domain 3 T4

Measured Object Cell


External Comment The counter can be used to compute the success rate of the reallocation execution phase.
Feature Name /

P406a - NB_UL_RES_REALLOC_SUCC_T1
Descripton

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

....................................................................................................................................................................................................................................
52-60 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P406a - NB_UL_RES_REALLOC_SUCC_T1
Radio interface
....................................................................................................................................................................................................................................

Trigger condition A PACKET CONTROL ACKNOWLEDGEMENT is received following a resource reallocation attempt for
that uplink 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 P405a.
If after the resource reallocation algorithm is run for a candidate Mobile Station having two 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 the reallocation protocol outcome. Indeed, even if the
reallocation protocol fails for the downlink TBF, the uplink 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 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 UL TBF re-allocations
Sub Domain 3 T1

Measured Object Cell


External Comment --

Feature Name /

P406b - NB_UL_RES_REALLOC_SUCC_T2
Descripton

Long Name NB_UL_RES_REALLOC_SUCC_T2


Definition Number of resource reallocation attempts that lead to reallocating successfully an uplink TBF (due to trigger
T2).
Trigger condition A PACKET CONTROL ACKNOWLEDGEMENT is received following a resource 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 UL TBF re-allocations


Sub Domain 3 T2

Measured Object Cell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-61
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P406c - NB_UL_RES_REALLOC_SUCC_T3
Radio interface
....................................................................................................................................................................................................................................

P406c - NB_UL_RES_REALLOC_SUCC_T3
Descripton

Long Name NB_UL_RES_REALLOC_SUCC_T3

Definition Number of resource reallocation attempts that lead to reallocating successfully an uplink TBF (due to trigger
T3).
Trigger condition A PACKET CONTROL ACKNOWLEDGEMENT is received following a resource reallocation attempt for
an uplink TBF due to T3. If the PACKET CONTROL ACKNOWLEDGEMENT acknowledges reallocation
of both an uplink and a downlink TBF, this counter shall be incremented as well as P405c.
If after the resource reallocation algorithm is run for a candidate Mobile Station having two TBFs following
T3, only the resources of the downlink TBF need to be reallocated, the procedure shall be considered
successful for the uplink TBF, irrespective of the reallocation protocol outcome. Indeed, even if the
reallocation protocol fails for the downlink TBF, the uplink 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 P404c
has been incremented.
The counter can be used to compute the success rate of the reallocation execution phase.
Sub Domain 1 Radio interface
Sub Domain 2 UL TBF re-allocations
Sub Domain 3 T3

Measured Object Cell


External Comment --

Feature Name /

P406d - NB_UL_RES_REALLOC_SUCC_T4
Descripton

Long Name NB_UL_RES_REALLOC_SUCC_T4

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 resource reallocation algorithm is run for a candidate Mobile Station having two TBFs following
T4, only the resources of the downlink TBF need to be reallocated, the procedure shall be considered
successful for the uplink TBF, irrespective of the reallocation protocol outcome. Indeed, even if the
reallocation protocol fails for the downlink TBF, the uplink 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
P404d has been incremented.

Sub Domain 1 Radio interface

Sub Domain 2 UL TBF re-allocations

....................................................................................................................................................................................................................................
52-62 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P406d - NB_UL_RES_REALLOC_SUCC_T4
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 T4

Measured Object Cell


External Comment The counter can be used to compute the success rate of the reallocation execution phase.

Feature Name /

P407a - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T1
Descripton

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 DL TBF re-allocations


Sub Domain 3 T1

Measured Object Cell


External Comment --
Feature Name /

P407b - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T2
Descripton

Long Name NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T2

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

Trigger condition After Max_Retrans_DL attempts to obtain acknowledgement from the MS for resource reallocation due to
T2 for a downlink TBF but it was never received, the TBF is released and this counter is incremented.
Assuming that the 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.
Note : because the corresponding uplink TBF could not be established too, then P28 is also incremented.

Sub Domain 1 Radio interface

Sub Domain 2 DL TBF re-allocations

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-63
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P407b - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T2
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 T2

Measured Object Cell


External Comment --

Feature Name /

P407c - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T3
Descripton

Long Name NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T3

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 T3).
Trigger condition After Max_Retrans_DL attempts to obtain acknowledgement from the MS for resource reallocation due to
T3 for a downlink TBF but it was never received, the TBF is released and this counter is incremented.
Assuming that the 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 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 DL TBF re-allocations


Sub Domain 3 T3

Measured Object Cell


External Comment --
Feature Name /

P407d - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T4
Descripton

Long Name NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T4

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 After Max_Retrans_DL attempts to obtain acknowledgement from the MS for 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 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 was attempted but failed had two TBFs and both were being
reallocated, then both counters P407d and P408d shall be incremented.

Sub Domain 1 Radio interface

....................................................................................................................................................................................................................................
52-64 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P407d - NB_DL_TBF_REL_RADIO_PB_RES_REALLOC_T4
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 2 DL TBF re-allocations

Sub Domain 3 T4
Measured Object Cell

External Comment --
Feature Name /

P408a - NB_UL_TBF_REL_RADIO_PB_RES_REALLOC_T1
Descripton

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 After Max_Retrans_DL attempts to obtain acknowledgement from the MS for resource reallocation due to
T1 for an uplink TBF but it was never received, the TBF is released and this counter is incremented.
Assuming that the 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 UL TBF re-allocations


Sub Domain 3 T1

Measured Object Cell


External Comment --
Feature Name /

P408b - NB_UL_TBF_REL_RADIO_PB_RES_REALLOC_T2
Descripton

Long Name NB_UL_TBF_REL_RADIO_PB_RES_REALLOC_T2

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

Trigger condition After Max_Retrans_DL attempts to obtain acknowledgement from the MS for resource reallocation due to
T2 for an uplink TBF but it was never received, the TBF is released and this counter is incremented.
Assuming that the 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.
Note :
because the corresponding downlink TBF could not be established, then P15 is also incremented.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-65
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P408b - NB_UL_TBF_REL_RADIO_PB_RES_REALLOC_T2
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 1 Radio interface

Sub Domain 2 UL TBF re-allocations


Sub Domain 3 T2

Measured Object Cell


External Comment --

Feature Name /

P408c - NB_UL_TBF_RADIO_PB_RES_REALLOC_T3
Descripton

Long Name NB_UL_TBF_RADIO_PB_RES_REALLOC_T3


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 T3).
Trigger condition After Max_Retrans_DL attempts to obtain acknowledgement from the MS for resource reallocation due to
T3 for an uplink TBF but it was never received, the TBF is released and this counter is incremented.
Assuming that the 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 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 UL TBF re-allocations

Sub Domain 3 T3
Measured Object Cell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
52-66 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P408d - NB_UL_TBF_RADIO_PB_RES_REALLOC_T4
Radio interface
....................................................................................................................................................................................................................................

P408d - NB_UL_TBF_RADIO_PB_RES_REALLOC_T4
Descripton

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 After Max_Retrans_DL attempts to obtain acknowledgement from the MS for resource reallocation due to
Trigger T4 for an uplink TBF but it was never received, the TBF is released and this counter is incremented.
Assuming that the 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 was attempted but failed had two TBFs and both were being
reallocated, then both counters P407d and P408d shall be incremented.

Sub Domain 1 Radio interface


Sub Domain 2 UL TBF re-allocations

Sub Domain 3 T4
Measured Object Cell

External Comment --
Feature Name /

P422 - NB_DL_TBF_TRANSFER_RESUMPTION_IN-
_DELAYED_REL_STATE
Descripton

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 DL TBF establishments

Sub Domain 3 N/A

Measured Object Cell


External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-67
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P423a - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T1
Radio interface
....................................................................................................................................................................................................................................

P423a - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T1
Descripton

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 DL TBF re-allocations

Sub Domain 3 T1
Measured Object Cell
External Comment --
Feature Name Enhanced Transmission Resource Management

P423b - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T2
Descripton

Long Name NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T2


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 DL TBF re-allocations

Sub Domain 3 T2
Measured Object Cell

External Comment --

Feature Name Support of GPRS QoS

....................................................................................................................................................................................................................................
52-68 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P423c - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T3
Radio interface
....................................................................................................................................................................................................................................

P423c - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T3
Descripton

Long Name NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T3

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 DL TBF re-allocations

Sub Domain 3 T3
Measured Object Cell
External Comment --

Feature Name Support of GPRS QoS

P423d - NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T4
Descripton

Long Name NB_DL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T4


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 resource reallocation preparation failure.

Sub Domain 1 Radio interface


Sub Domain 2 DL TBF re-allocations

Sub Domain 3 T4

Measured Object Cell


External Comment --
Feature Name Support of GPRS QoS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-69
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P424a - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T1
Radio interface
....................................................................................................................................................................................................................................

P424a - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T1
Descripton

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 UL TBF re-allocations

Sub Domain 3 T1
Measured Object Cell
External Comment --
Feature Name Enhanced Transmission Resource Management

P424b - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T2
Descripton

Long Name NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T2


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 UL TBF re-allocations

Sub Domain 3 T2
Measured Object Cell

External Comment --

Feature Name /

....................................................................................................................................................................................................................................
52-70 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P424c - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T3
Radio interface
....................................................................................................................................................................................................................................

P424c - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T3
Descripton

Long Name NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T3

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 resource reallocation preparation failure.

Sub Domain 1 Radio interface


Sub Domain 2 UL TBF re-allocations

Sub Domain 3 T3
Measured Object Cell
External Comment --

Feature Name /

P424d - NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T4
Descripton

Long Name NB_UL_TBF_RES_REALLOC_PREP_NOT_POSSIBLE_T4


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 resource reallocation preparation failure.

Sub Domain 1 Radio interface

Sub Domain 2 UL TBF re-allocations


Sub Domain 3 T4
Measured Object Cell

External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-71
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P425a - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T1
Radio interface
....................................................................................................................................................................................................................................

P425a - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T1
Descripton

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 DL TBF re-allocations


Sub Domain 3 T1

Measured Object Cell


External Comment --

Feature Name /

P425b - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T2
Descripton

Long Name NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T2


Definition Number of downlink TBFs for which the resource reallocation protocol is running following T2 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 DL TBF re-allocations


Sub Domain 3 T2

Measured Object Cell


External Comment --

....................................................................................................................................................................................................................................
52-72 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P425b - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T2
Radio interface
....................................................................................................................................................................................................................................

Feature Name /

P425c - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T3
Descripton

Long Name NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T3

Definition Number of downlink TBFs for which the resource reallocation protocol is running following T3 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 DL TBF re-allocations


Sub Domain 3 T3

Measured Object Cell


External Comment --

Feature Name /

P425d - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T4
Descripton

Long Name NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T4


Definition Number of downlink TBFs for which the resource reallocation protocol is running 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 The counter is incremented each time the resources of a downlink TBF are 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 DL TBF re-allocations

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-73
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P425d - NB_DL_TBF_REL_EXT_REQ_RES_REALLOC_T4
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 T4

Measured Object Cell


External Comment --

Feature Name /

P426a - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T1
Descripton

Long Name NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T1

Definition Number of uplink 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 an uplink TBF are being reallocated (ie 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 is received.
Sub Domain 1 Radio interface

Sub Domain 2 UL TBF re-allocations


Sub Domain 3 T1

Measured Object Cell


External Comment --

Feature Name /

P426b - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T2
Descripton

Long Name NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T2

Definition Number of uplink TBFs for which the resource reallocation protocol is running following T2 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).

....................................................................................................................................................................................................................................
52-74 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P426b - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T2
Radio interface
....................................................................................................................................................................................................................................

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

Sub Domain 1 Radio interface


Sub Domain 2 UL TBF re-allocations

Sub Domain 3 T2

Measured Object Cell


External Comment --

Feature Name /

P426c - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T3
Descripton

Long Name NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T3


Definition Number of uplink TBFs for which the resource reallocation protocol is running following T3 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 an uplink TBF are being reallocated (ie 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 is received.

Sub Domain 1 Radio interface


Sub Domain 2 UL TBF re-allocations

Sub Domain 3 T3
Measured Object Cell

External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-75
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P426d - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T4
Radio interface
....................................................................................................................................................................................................................................

P426d - NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T4
Descripton

Long Name NB_UL_TBF_REL_EXT_REQ_RES_REALLOC_T4

Definition Number of uplink TBFs for which the resource reallocation protocol is running 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 The counter is incremented each time the resources of an uplink TBF are 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 UL TBF re-allocations


Sub Domain 3 T4

Measured Object Cell


External Comment --

Feature Name /

P431b - MAX_SOURCE_NC2_CELL_RESEL_TIME
Descripton

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 Cell reselections in NC2

Sub Domain 3 N/A

Measured Object Cell


External Comment --
Feature Name /

....................................................................................................................................................................................................................................
52-76 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P431c - MIN_SOURCE_NC2_CELL_RESEL_TIME
Radio interface
....................................................................................................................................................................................................................................

P431c - MIN_SOURCE_NC2_CELL_RESEL_TIME
Descripton

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 Cell reselections in NC2

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P432b - MAX_TARGET_NC2_CELL_RESEL_TIME
Descripton

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 Cell reselections in NC2


Sub Domain 3 N/A
Measured Object Cell
External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-77
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P432c - MIN_TARGET_NC2_CELL_RESEL_TIME
Radio interface
....................................................................................................................................................................................................................................

P432c - MIN_TARGET_NC2_CELL_RESEL_TIME
Descripton

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 Cell reselections in NC2

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P433a - NB_NC2_CELL_RESEL_REQ_PT1
Descripton

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 Cell reselections in NC2
Sub Domain 3 N/A

Measured Object Cell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
52-78 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P433b - NB_NC2_CELL_RESEL_REQ_PT2
Radio interface
....................................................................................................................................................................................................................................

P433b - NB_NC2_CELL_RESEL_REQ_PT2
Descripton

Long Name NB_NC2_CELL_RESEL_REQ_PT2

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 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 the "detection of a better neighbour cell" (Cause PT2).
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 Cell reselections in NC2


Sub Domain 3 N/A
Measured Object Cell
External Comment --
Feature Name /

P433c - NB_NC2_CELL_RESEL_REQ_PT3
Descripton

Long Name NB_NC2_CELL_RESEL_REQ_PT3


Definition Number of NC2 cell reselection requests for a MS in packet transfer mode due to a "too bad downlink radio
quality" (Cause PT3)
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 bad downlink radio quality" (Cause PT3).
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 Cell reselections in NC2


Sub Domain 3 N/A
Measured Object Cell

External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-79
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P433d - NB_NC2_CELL_RESEL_REQ_PT4
Radio interface
....................................................................................................................................................................................................................................

P433d - NB_NC2_CELL_RESEL_REQ_PT4
Descripton

Long Name NB_NC2_CELL_RESEL_REQ_PT4

Definition Number of NC2 cell reselection requests for a MS in packet transfer mode due to a "too bad uplink radio
quality" (Cause PT4)
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 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 Cell reselections in NC2


Sub Domain 3 N/A
Measured Object Cell
External Comment --
Feature Name /

P434a - NB_NC2_UL_TBF_RELEASE
Descripton

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

....................................................................................................................................................................................................................................
52-80 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P434a - NB_NC2_UL_TBF_RELEASE
Radio interface
....................................................................................................................................................................................................................................

Feature Name /

P434b - NB_NC2_DL_TBF_RELEASE
Descripton

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 --
Feature Name /

P434c - NB_NC0_UL_TBF_RELEASE
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-81
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P434c - NB_NC0_UL_TBF_RELEASE
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P434d - NB_NC0_DL_TBF_RELEASE
Descripton

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 --
Feature Name /

P435a - NB_NC2_CELL_RESEL_SUCC_PT1
Descripton

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 Cell reselections in NC2


Sub Domain 3 N/A

Measured Object Cell

....................................................................................................................................................................................................................................
52-82 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P435a - NB_NC2_CELL_RESEL_SUCC_PT1
Radio interface
....................................................................................................................................................................................................................................

External Comment --

Feature Name /

P435b - NB_NC2_CELL_RESEL_SUCC_PT2
Descripton

Long Name NB_NC2_CELL_RESEL_SUCC_PT2

Definition Number of NC2 cell reselection successes for a MS in packet transfer mode due to a "detection of a better
neighbour cell" (Cause PT2)
Trigger condition This counter is incremented upon receipt of a Flush-LL message corresponding 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 Cell reselections in NC2
Sub Domain 3 N/A
Measured Object Cell
External Comment --

Feature Name /

P435c - NB_NC2_CELL_RESEL_SUCC_PT3
Descripton

Long Name NB_NC2_CELL_RESEL_SUCC_PT3


Definition Number of NC2 cell reselection successes for a MS in packet transfer mode due to a "too bad downlink
radio quality" (Cause PT3)
Trigger condition This counter is incremented upon receipt of a Flush-LL message corresponding to a NC2 cell reselection
triggered due to a "too bad downlink radio quality" (Cause PT3).

Sub Domain 1 Radio interface


Sub Domain 2 Cell reselections in NC2

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-83
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P435d - NB_NC2_CELL_RESEL_SUCC_PT4
Radio interface
....................................................................................................................................................................................................................................

P435d - NB_NC2_CELL_RESEL_SUCC_PT4
Descripton

Long Name NB_NC2_CELL_RESEL_SUCC_PT4

Definition Number of NC2 cell reselection successes for a MS in packet transfer mode due to a "too bad uplink radio
quality" (Cause PT4)
Trigger condition This counter is incremented upon receipt of a Flush-LL message corresponding to a NC2 cell reselection
triggered due to a "too bad uplink radio quality" (Cause PT4).

Sub Domain 1 Radio interface


Sub Domain 2 Cell reselections in NC2

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P436 - NB_NC0_CELL_RESEL_Mstrans
Descripton

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 Cell reselections in NC0

Sub Domain 3 N/A


Measured Object Cell

External Comment --

Feature Name /

....................................................................................................................................................................................................................................
52-84 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P437a - NB_NC2_CELL_RESEL_FAIL_REJECT_CELL
Radio interface
....................................................................................................................................................................................................................................

P437a - NB_NC2_CELL_RESEL_FAIL_REJECT_CELL
Descripton

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 Cell reselections in NC2

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P437b - NB_NC2_CELL_RESEL_FAIL_NO_REJECT_CELL
Descripton

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 Cell reselections in NC2

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-85
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P440a - NB_REROUTING_INTRA_NSE
Radio interface
....................................................................................................................................................................................................................................

P440a - NB_REROUTING_INTRA_NSE
Descripton

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 --
Feature Name /

P440b - NB_REROUTING_INTER_NSE_INTRA_BSS
Descripton

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 Inter-NSE DL LLC PDU re-routing


Sub Domain 3 N/A
Measured Object Cell

External Comment --

Feature Name /

....................................................................................................................................................................................................................................
52-86 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P440c - NB_REROUTING_INTER_NSE_INTER_BSS
Radio interface
....................................................................................................................................................................................................................................

P440c - NB_REROUTING_INTER_NSE_INTER_BSS
Descripton

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 BSS, within the same
routing area.
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 --
Feature Name /

P441a - NB_IMPOSSIBLE_OR_UNREQUESTED_REROUTING_INR
Descripton

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 Inter-NSE DL LLC PDU re-routing


Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-87
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P441b - NB_UNREQUESTED_REROUTING_NOT_INR
Radio interface
....................................................................................................................................................................................................................................

P441b - NB_UNREQUESTED_REROUTING_NOT_INR
Descripton

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
(EN_AUTONOMOUS_REROUTING set to enabled) and the MFS receives a 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 Inter-NSE DL LLC PDU re-routing


Sub Domain 3 N/A
Measured Object Cell

External Comment --
Feature Name /

P441c - NB_IMPOSSIBLE_REROUTING_NOT_INR
Descripton

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
(EN_AUTONOMOUS_REROUTING set to enabled) and the MFS receives a FLUSH-LL message
following a cell change occuring between two different routing areas.

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 --
Feature Name /

....................................................................................................................................................................................................................................
52-88 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P456 - NB_PSI_PROC
Radio interface
....................................................................................................................................................................................................................................

P456 - NB_PSI_PROC
Descripton

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 --
Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)

P458 - NB_NEIGH_PSI_PROC
Descripton

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 --
Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-89
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P460b - MAX_SOURCE_NACC_CELL_RESEL_TIME
Radio interface
....................................................................................................................................................................................................................................

P460b - MAX_SOURCE_NACC_CELL_RESEL_TIME
Descripton

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 --
Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)

P460c - MIN_SOURCE_NACC_CELL_RESEL_TIME
Descripton

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 --
Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)

....................................................................................................................................................................................................................................
52-90 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P463 - NB_PFC_DOWNLOAD
Radio interface
....................................................................................................................................................................................................................................

P463 - NB_PFC_DOWNLOAD
Descripton

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 --
Feature Name Support of GPRS QoS

P464 - NB_NC2_CELL_RESEL_FAIL_LOAD
Descripton

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 Cell reselections in NC2

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-91
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P488 - NB_RT_DL_TBF
Radio interface
....................................................................................................................................................................................................................................

P488 - NB_RT_DL_TBF
Descripton

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 --
Feature Name Support of GPRS QoS

P489 - NB_RT_UL_TBF
Descripton

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 --
Feature Name Support of GPRS QoS

....................................................................................................................................................................................................................................
52-92 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P490 - NB_UNACK_NRT_PFC_CREATION
Radio interface
....................................................................................................................................................................................................................................

P490 - NB_UNACK_NRT_PFC_CREATION
Descripton

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 --
Feature Name Support of GPRS QoS

P491 - NB_UNACK_RT_PFC_CREATION
Descripton

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 --
Feature Name Support of GPRS QoS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-93
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P492 - NB_DOWNGRADED_RT_PFC
Radio interface
....................................................................................................................................................................................................................................

P492 - NB_DOWNGRADED_RT_PFC
Descripton

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

Feature Name Support of GPRS QoS

P493 - NB_PFC_REJECTED
Descripton

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 --
Feature Name Support of GPRS QoS

....................................................................................................................................................................................................................................
52-94 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P494 - NB_PFC_DOWNLOAD_FAIL
Radio interface
....................................................................................................................................................................................................................................

P494 - NB_PFC_DOWNLOAD_FAIL
Descripton

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 --
Feature Name Support of GPRS QoS

P497 - NB_RT_PFC_CREATION
Descripton

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

Feature Name Support of GPRS QoS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-95
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P498 - NB_NRT_PFC_CREATION
Radio interface
....................................................................................................................................................................................................................................

P498 - NB_NRT_PFC_CREATION
Descripton

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 --
Feature Name Support of GPRS QoS

P499 - NB_RT_PFC_CREATION_OK
Descripton

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

Feature Name Support of GPRS QoS

....................................................................................................................................................................................................................................
52-96 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P500 - NB_DTM_CAPABLE_MS_CONTEXT_GPU
Radio interface
....................................................................................................................................................................................................................................

P500 - NB_DTM_CAPABLE_MS_CONTEXT_GPU
Descripton

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 Sub_BSS (BSC/FABRIC)


External Comment --
Feature Name Dual Transfer Mode (DTM)

P501 - NB_DTM_MS_CONTEXT_CELL
Descripton

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

Feature Name Dual Transfer Mode (DTM)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-97
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P502 - CUMULATED_DTM_TIME
Radio interface
....................................................................................................................................................................................................................................

P502 - CUMULATED_DTM_TIME
Descripton

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 --
Feature Name Dual Transfer Mode (DTM)

P503 - CUMULATED_DTM_DEDICATED_TIME
Descripton

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

....................................................................................................................................................................................................................................
52-98 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P503 - CUMULATED_DTM_DEDICATED_TIME
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name Dual Transfer Mode (DTM)

P504 - CUMULATED_DTM_PTM_TIME
Descripton

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

Feature Name Dual Transfer Mode (DTM)

P505 - NB_DTM_DL_TBF_EST_REQ
Descripton

Long Name NB_DTM_DL_TBF_EST_REQ

Definition Number of DL TBF establishment requests on DCCH for MS operating in DTM.


Note: This counter applies to GPRS and EGPRS MS.

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-99
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P505 - NB_DTM_DL_TBF_EST_REQ
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name Dual Transfer Mode (DTM)

P505a - NB_DTM_DL_TBF_EST_REQ_EGPRS
Descripton

Long Name NB_DTM_DL_TBF_EST_REQ_EGPRS

Definition Number of DL TBF establishment requests on DCCH for EGPRS capable 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.
*) 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 DTM
Sub Domain 3 N/A
Measured Object Cell
External Comment --

Feature Name /

P506 - NB_DTM_DL_TBF_EST_SUCC
Descripton

Long Name NB_DTM_DL_TBF_EST_SUCC

Definition Number of DL TBF establishment successes on DCCH for MS operating in DTM.


Note: This counter applies to GPRS and EGPRS MS.

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

....................................................................................................................................................................................................................................
52-100 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P506 - NB_DTM_DL_TBF_EST_SUCC
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 2 DTM

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name Dual Transfer Mode (DTM)

P506a - NB_DTM_DL_TBF_EST_SUCC_EGPRS
Descripton

Long Name NB_DTM_DL_TBF_EST_SUCC_EGPRS


Definition Number of DL TBF establishment successes on DCCH successfully served in EGPRS mode for EGPRS
capable 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).

Sub Domain 1 Radio interface


Sub Domain 2 DTM
Sub Domain 3 N/A
Measured Object Cell
External Comment --

Feature Name /

P507 - NB_DTM_UL_TBF_EST_REQ
Descripton

Long Name NB_DTM_UL_TBF_EST_REQ

Definition Number of UL TBF establishment requests on DCCH for MS operating in DTM.


Note: This counter applies to GPRS and EGPRS MS.
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 --
Feature Name Dual Transfer Mode (DTM)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-101
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P507a - NB_DTM_UL_TBF_EST_REQ_EGPRS
Radio interface
....................................................................................................................................................................................................................................

P507a - NB_DTM_UL_TBF_EST_REQ_EGPRS
Descripton

Long Name NB_DTM_UL_TBF_EST_REQ_EGPRS

Definition Number of UL TBF establishment requests on DCCH for EGPRS capable MS operating in DTM.
Trigger condition This counter is incremented when MFS receives the BSCGP DTM Request message from an EGPRS
capable MS.
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 DTM

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P508 - NB_DTM_UL_TBF_EST_SUCC
Descripton

Long Name NB_DTM_UL_TBF_EST_SUCC


Definition Number of UL TBF establishment successes on DCCH for MS operating in DTM.
Note: This counter applies to GPRS and EGPRS MS.
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 --
Feature Name Dual Transfer Mode (DTM)

....................................................................................................................................................................................................................................
52-102 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P508a - NB_DTM_UL_TBF_EST_SUCC_EGPRS
Radio interface
....................................................................................................................................................................................................................................

P508a - NB_DTM_UL_TBF_EST_SUCC_EGPRS
Descripton

Long Name NB_DTM_UL_TBF_EST_SUCC_EGPRS

Definition Number of UL TBF establishment successes on DCCH successfully served in EGPRS mode 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 --
Feature Name /

P509 - NB_DTM_CS_DL_TBF_RELEASE
Descripton

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.
Note: This counter applies to GPRS and EGPRS MS.
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 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-103
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P509 - NB_DTM_CS_DL_TBF_RELEASE
Radio interface
....................................................................................................................................................................................................................................

Feature Name Dual Transfer Mode (DTM)

P509a - NB_DTM_CS_DL_TBF_RELEASE_EGPRS
Descripton

Long Name NB_DTM_CS_DL_TBF_RELEASE_EGPRS

Definition Number of DL TBF established in EGPRS mode 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 EGPRS 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 --

Feature Name /

P510 - NB_DTM_CS_UL_TBF_RELEASE
Descripton

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.
Note: This counter applies to GPRS and EGPRS MS.
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

....................................................................................................................................................................................................................................
52-104 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P510 - NB_DTM_CS_UL_TBF_RELEASE
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 2 DTM

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name Dual Transfer Mode (DTM)

P510a - NB_DTM_CS_UL_TBF_RELEASE_EGPRS
Descripton

Long Name NB_DTM_CS_UL_TBF_RELEASE_EGPRS


Definition Number of UL TBF established in EGPRS mode 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 EGPRS 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 --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-105
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P511 - NB_DTM_DL_TBF_FAIL_CONG
Radio interface
....................................................................................................................................................................................................................................

P511 - NB_DTM_DL_TBF_FAIL_CONG
Descripton

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.
Note: This counter applies to GPRS and EGPRS MS.

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

Feature Name Dual Transfer Mode (DTM)

P512 - NB_DTM_UL_TBF_FAIL_CONG
Descripton

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.
Note: This counter applies to GPRS and EGPRS MS.
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 --

Feature Name Dual Transfer Mode (DTM)

....................................................................................................................................................................................................................................
52-106 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P513 - NB_UL_LLC_BYTES_GTTP
Radio interface
....................................................................................................................................................................................................................................

P513 - NB_UL_LLC_BYTES_GTTP
Descripton

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 --
Feature Name Dual Transfer Mode (DTM)

P514 - NB_DL_LLC_BYTES_GTTP
Descripton

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

Feature Name Dual Transfer Mode (DTM)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-107
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P515 - NB_RT_PFC_CREATION_DTM_DEDICATED
Radio interface
....................................................................................................................................................................................................................................

P515 - NB_RT_PFC_CREATION_DTM_DEDICATED
Descripton

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 --
Feature Name Dual Transfer Mode (DTM)

P516 - NB_RT_PFC_DOWNGRADED_DTM_DEDICATED
Descripton

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

Feature Name Dual Transfer Mode (DTM)

....................................................................................................................................................................................................................................
52-108 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P518 - NB_RT_PFC_CREATION_DTM_MODE
Radio interface
....................................................................................................................................................................................................................................

P518 - NB_RT_PFC_CREATION_DTM_MODE
Descripton

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 --
Feature Name Dual Transfer Mode (DTM)

P519 - NB_RT_PFC_DOWNGRADED_DTM_MODE
Descripton

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

Feature Name Dual Transfer Mode (DTM)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-109
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P520 - NB_DL_TBF_EST_FAIL_DTM
Radio interface
....................................................................................................................................................................................................................................

P520 - NB_DL_TBF_EST_FAIL_DTM
Descripton

Long Name NB_DL_TBF_EST_FAIL_DTM

Definition Number of DL TBF establishment failures due to DTM.


This counter also counts the DTM DL TBF that fail to establish.

Trigger condition This counter is incremented for DTM capable MS with establishing DL TBF, when an abnormal DL TBF
release, occurs:
- when the dedicated mode is entered;
- when an UL DTM TBF establishment is detected;
- when on a DL DTM TBF establishment, an intercell or an intracell handover occurs;
- when a DTM DL TBF fails to establish.

Sub Domain 1 Radio interface


Sub Domain 2 DTM
Sub Domain 3 N/A
Measured Object Cell
External Comment --

Feature Name Dual Transfer Mode (DTM)

P521 - NB_UL_TBF_EST_FAIL_DTM
Descripton

Long Name NB_UL_TBF_EST_FAIL_DTM


Definition Number of UL TBF establishment failure due to DTM.
This counter also counts the DTM UL TBF that fail to establish.
Trigger condition This counter is incremented for DTM capable MS with establishing UL TBF, when an abnormal UL TBF
release, occurs:
- when the dedicated mode is entered;
- when an DL DTM TBF establishment is detected;
- when on a UL DTM TBF establishment, an intercell or an intracell handover occurs;
- when a DTM UL TBF fails to establish.

Sub Domain 1 Radio interface


Sub Domain 2 DTM
Sub Domain 3 N/A

Measured Object Cell

External Comment --

....................................................................................................................................................................................................................................
52-110 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P521 - NB_UL_TBF_EST_FAIL_DTM
Radio interface
....................................................................................................................................................................................................................................

Feature Name Dual Transfer Mode (DTM)

P540b - NB_REFUSED_RT_PFC_LACK_BANDWIDTH
Descripton

Long Name NB_REFUSED_RT_PFC_LACK_BANDWIDTH

Definition Number of RT PFC creation refused due to lack of bandwidth reserved for GBR PFC.
Trigger condition Each time a DL or UL RT PFC is refused due to a lack of reserved bandwidth for GBR , this counter is
incremented.

Sub Domain 1 Radio interface


Sub Domain 2 PFC

Sub Domain 3 N/A


Measured Object Cell
External Comment --
Feature Name Support of GPRS QoS

P540c - NB_REFUSED_RT_PFC_LACK_RADIO
Descripton

Long Name NB_REFUSED_RT_PFC_LACK_RADIO


Definition Number of RT PFC creation refused due to lack of radio ressource.
Trigger condition Each time a DL or UL RT PFC is refused due to a lack of radio resource , this counter is incremented.
Sub Domain 1 Radio interface
Sub Domain 2 PFC

Sub Domain 3 N/A


Measured Object Cell

External Comment --

Feature Name Support of GPRS QoS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-111
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P540d - MAX_DL_GBR_BW_GRANTED
Radio interface
....................................................................................................................................................................................................................................

P540d - MAX_DL_GBR_BW_GRANTED
Descripton

Long Name MAX_DL_GBR_BW_GRANTED

Definition Maximum of the DL BW granted for DL GBRs.


Trigger condition This counter provides the maximum value of the bandwidth consumed by DL GBRs.
Each time a DL RT PFC creation is accepted, a DL RT PFC deletion occurs or a DL RT PFC time life
expires or a DL RT PFC is downgraded or DL RT PFC is refused, the total bandwidth granted to the DL
GBRs is computed.
The counter stores the maximum of the values encountered during the GP.
Note : The value is provided in Kbits per second.

Sub Domain 1 Radio interface

Sub Domain 2 PFC


Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name Support of GPRS QoS

P540e - MAX_UL_GBR_BW_GRANTED
Descripton

Long Name MAX_UL_GBR_BW_GRANTED


Definition Maximum of the UL BW granted for UL GBRs.
Trigger condition This counter provides the maximum value of the bandwidth consumed by UL GBRs.
Each time a UL RT PFC creation is accepted, a UL RT PFC deletion occurs or a UL RT PFC time life
expires or a UL RT PFC is downgraded or UL RT PFC is refused, the total bandwidth granted to the UL
GBRs is computed.
The counter stores the maximum of the values encountered during the GP.
Note : The value is provided in Kbits per second .
Sub Domain 1 Radio interface

Sub Domain 2 PFC


Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name Support of GPRS QoS

....................................................................................................................................................................................................................................
52-112 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P552 - NB_UL_TBF_REL_UL_LLC_PDU_SEQ_FLOW_PB
Radio interface
....................................................................................................................................................................................................................................

P552 - NB_UL_TBF_REL_UL_LLC_PDU_SEQ_FLOW_PB
Descripton

Long Name NB_UL_TBF_REL_UL_LLC_PDU_SEQ_FLOW_PB

Definition Number of UL TBF releases due to discrepancies in the reception of UL_LLC_PDU sequence flow.
Trigger condition This counter is incremented each time an UL TBF is released when
- UL_LLC_PDU reception buffer overflows (PCC_T_MAX_UL_BUFFERING is overpassed).
- Timer PCC_UL_TBF_GUARD_TIMER elapses.
- The maximum number of TBF signature is reached.

Sub Domain 1 Radio interface

Sub Domain 2 UL TBF releases


Sub Domain 3 N/A

Measured Object Cell


External Comment --
Feature Name IP transport in the BSS

P594 - NB_EDA_MS_CONTEXT_GPU
Descripton

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 Sub_BSS (BSC/FABRIC)


External Comment --

Feature Name Extended Dynamic Allocation

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-113
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P595 - CUMULATED_TIME_ACTIVE_UL_CONNECT-
Radio interface ED_TIME_EDA_MODE
....................................................................................................................................................................................................................................

P595 - CUMULATED_TIME_ACTIVE_UL_CONNECT-
ED_TIME_EDA_MODE
Descripton

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 delay final PUAN or 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 --
Feature Name Extended Dynamic Allocation

....................................................................................................................................................................................................................................
52-114 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P596 - NB_EDA_USED_UL_TBF
Radio interface
....................................................................................................................................................................................................................................

P596 - NB_EDA_USED_UL_TBF
Descripton

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

Feature Name Extended Dynamic Allocation

P597 - NB_EDA_ALLOWED_UL_TBF
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-115
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P597 - NB_EDA_ALLOWED_UL_TBF
Radio interface
....................................................................................................................................................................................................................................

Feature Name Extended Dynamic Allocation

P598 - NB_DA_EDA_REALLOC_UL_TBF
Descripton

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

Feature Name Extended Dynamic Allocation

P62a - NB_UL_TBF_EST_REQ_MSidle_MastChan
Descripton

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 UL TBF establishments


Sub Domain 3 N/A

Measured Object Cell

....................................................................................................................................................................................................................................
52-116 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P62a - NB_UL_TBF_EST_REQ_MSidle_MastChan
Radio interface
....................................................................................................................................................................................................................................

External Comment --

Feature Name /

P62b - NB_UL_TBF_EST_REQ_MStransDL
Descripton

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 UL TBF establishments


Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P62c - NB_UL_TBF_EST_REQ_MSidle_NO_MastChan
Descripton

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 44.060 PACKET MEASUREMENT REPORT message or a 44.060
PACKET CELL CHANGE FAILURE message (when the NC2 feature is activated).

Trigger condition This counter is incremented whenever a 44.018 CHANNEL REQUEST message with access cause "One
phase packet access" or "Single block packet access", or a 44.018 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.)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-117
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P62c - NB_UL_TBF_EST_REQ_MSidle_NO_MastChan
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 1 Radio interface

Sub Domain 2 UL TBF establishments


Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P62e - NB_UL_TBF_EST_REQ_EGPRS_MStransDL
Descripton

Long Name NB_UL_TBF_EST_REQ_EGPRS_MStransDL


Definition Number of UL TBF establishment requests when the EGPRS MS is in downlink packet transfer mode.
Note: This counter applies to 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.
Note:
- The counter applies only to EGPRS capable MS.
- 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 UL TBF establishments


Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

....................................................................................................................................................................................................................................
52-118 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P65 - NB_DL_TBF_EST_FAIL_GB_PB
Radio interface
....................................................................................................................................................................................................................................

P65 - NB_DL_TBF_EST_FAIL_GB_PB
Descripton

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 DL TBF establishments


Sub Domain 3 N/A

Measured Object Cell


External Comment --
Feature Name /

P66 - NB_UL_TBF_EST_FAIL_GB_PB
Descripton

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 UL TBF establishments


Sub Domain 3 N/A
Measured Object Cell

External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-119
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P9 - NB_DL_TBF_NORM_REL
Radio interface
....................................................................................................................................................................................................................................

P9 - NB_DL_TBF_NORM_REL
Descripton

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).
Note: This counter applies to GPRS and EGPRS MS.

Sub Domain 1 Radio interface


Sub Domain 2 DL TBF releases

Sub Domain 3 N/A


Measured Object Cell
External Comment --
Feature Name /

P90a - NB_DL_TBF_EST_SUCC_MS_Idle_DRX_MPDCH
Descripton

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 DL TBF establishments

Sub Domain 3 N/A


Measured Object Cell
External Comment --

Feature Name /

....................................................................................................................................................................................................................................
52-120 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P90b - NB_DL_TBF_EST_SUCC_MS_Transfer_UL
Radio interface
....................................................................................................................................................................................................................................

P90b - NB_DL_TBF_EST_SUCC_MS_Transfer_UL
Descripton

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 This counter is incremented whenever a PACKET CONTROL ACKNOWLEDGEMENT message is
received on PACCH subsequent to a DL TBF establishment performed on PACCH for a MS in packet
transfer mode.
Sub Domain 1 Radio interface

Sub Domain 2 DL TBF establishments


Sub Domain 3 N/A

Measured Object Cell


External Comment --
Feature Name /

P90c - NB_DL_TBF_EST_SUCC_MS_IDLE_DRX_NO_MPDCH
Descripton

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 This counter is incremented whenever a PACKET CONTROL ACKNOWLEDGEMENT message is
received on PACCH subsequent to a DL TBF establishment performed on CCCH for a MS in packet idle
mode and DRX mode.
Sub Domain 1 Radio interface

Sub Domain 2 DL TBF establishments


Sub Domain 3 N/A

Measured Object Cell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-121
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P90d - NB_DL_TBF_EST_SUCC_MS_Non_DRX_MPDCH
Radio interface
....................................................................................................................................................................................................................................

P90d - NB_DL_TBF_EST_SUCC_MS_Non_DRX_MPDCH
Descripton

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 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 non-DRX mode.
Sub Domain 1 Radio interface

Sub Domain 2 DL TBF establishments


Sub Domain 3 N/A
Measured Object Cell
External Comment --
Feature Name /

P90e - NB_DL_TBF_EST_SUCC_T3192
Descripton

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 ACKNOWLEDGEMENT message is
received on PACCH subsequent to a DL TBF establishment triggered while the timer T3192n was running.
Sub Domain 1 Radio interface

Sub Domain 2 DL TBF establishments

Sub Domain 3 N/A


Measured Object Cell

External Comment --

Feature Name /

....................................................................................................................................................................................................................................
52-122 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P90f - NB_DL_TBF_EST_SUCC_MS_Non_DRX_NO_MPDCH
Radio interface
....................................................................................................................................................................................................................................

P90f - NB_DL_TBF_EST_SUCC_MS_Non_DRX_NO_MPDCH
Descripton

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 This counter is incremented whenever a PACKET CONTROL ACKNOWLEDGEMENT message is
received on PACCH subsequent to a DL TBF establishment performed on CCCH for a MS in packet idle
mode and non-DRX mode.
Sub Domain 1 Radio interface

Sub Domain 2 DL TBF establishments


Sub Domain 3 N/A
Measured Object Cell
External Comment --
Feature Name /

P90h - NB_DL_TBF_EST_SUCC_EGPRS_MS_Transfer_UL
Descripton

Long Name NB_DL_TBF_EST_SUCC_EGPRS_MS_Transfer_UL


Definition Number of DL TBF successfully established in EGPRS mode when MS is in uplink packet transfer mode.
Trigger condition This counter is incremented whenever a PACKET CONTROL ACKNOWLEDGEMENT message is
received on PACCH subsequent to a DL TBF establishment in EGPRS mode performed on PACCH for a
MS in packet transfer mode.
Sub Domain 1 Radio interface

Sub Domain 2 DL TBF establishments


Sub Domain 3 N/A

Measured Object Cell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-123
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P90i - NB_DL_TBF_EST_SUCC_EGPRS_T3192
Radio interface
....................................................................................................................................................................................................................................

P90i - NB_DL_TBF_EST_SUCC_EGPRS_T3192
Descripton

Long Name NB_DL_TBF_EST_SUCC_EGPRS_T3192

Definition Number of DL TBF successfully established in EGPRS mode on PACCH while the timer T3192 is running
at BSS side.
Note: This counter applies to EGPRS MS.

Trigger condition The counter is incremented whenever a PACKET CONTROL ACKNOWLEDGEMENT message is
received on PACCH subsequent to a DL TBF establishment in EGPRS mode triggered while the timer
T3192n was running.
Sub Domain 1 Radio interface

Sub Domain 2 DL TBF establishments


Sub Domain 3 N/A
Measured Object Cell
External Comment --
Feature Name /

P91a - NB_DL_TBF_EST_REQ_MS_IDLE_DRX_MPDCH
Descripton

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: This counter applies to GPRS and EGPRS MS.
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 DL TBF establishments


Sub Domain 3 N/A

Measured Object Cell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
52-124 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P91b - NB_DL_TBF_EST_REQ_MS_Transfer_UL
Radio interface
....................................................................................................................................................................................................................................

P91b - NB_DL_TBF_EST_REQ_MS_Transfer_UL
Descripton

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 DL TBF establishments


Sub Domain 3 N/A

Measured Object Cell


External Comment --
Feature Name /

P91c - NB_DL_TBF_EST_REQ_MS_IDLE_DRX_NO_MPDCH
Descripton

Long Name NB_DL_TBF_EST_REQ_MS_IDLE_DRX_NO_MPDCH


Definition Number of DL TBF establishment requests when the MS is in packet idle mode and DRX mode in case
there is no PCCCH established in the cell.
Note: This counter applies to GPRS and EGPRS MS.
Trigger condition This counter is incremented whenever the MFS receives a DL LLC PDU for 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 DL TBF establishments


Sub Domain 3 N/A

Measured Object Cell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-125
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P91d - NB_DL_TBF_EST_REQ_MS_Non_DRX_MPDCH
Radio interface
....................................................................................................................................................................................................................................

P91d - NB_DL_TBF_EST_REQ_MS_Non_DRX_MPDCH
Descripton

Long Name NB_DL_TBF_EST_REQ_MS_Non_DRX_MPDCH

Definition Number of DL TBF establishment requests when the MS is in packet idle mode 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 This counter is incremented whenever the MFS receives a DL LLC PDU for a MS 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 requests only take into account the first attempt, i.e. no
repetitions are counted.

Sub Domain 1 Radio interface


Sub Domain 2 DL TBF establishments

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P91e - NB_DL_TBF_EST_REQ_T3192
Descripton

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 DL TBF establishments


Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

....................................................................................................................................................................................................................................
52-126 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P91f - NB_DL_TBF_EST_REQ_MS_Non_DRX_NO_MPDCH
Radio interface
....................................................................................................................................................................................................................................

P91f - NB_DL_TBF_EST_REQ_MS_Non_DRX_NO_MPDCH
Descripton

Long Name NB_DL_TBF_EST_REQ_MS_Non_DRX_NO_MPDCH

Definition Number of DL TBF establishment requests when the MS is in packet idle mode and non-DRX mode , in
case there is no PCCCH established in the cell.
Note: This counter applies to GPRS and EGPRS MS.

Trigger condition This counter is incremented whenever the MFS receives a DL LLC PDU for a MS 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 DL TBF establishments

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P91h - NB_DL_TBF_EST_REQ_EGPRS_MS_Transfer_UL
Descripton

Long Name NB_DL_TBF_EST_REQ_EGPRS_MS_Transfer_UL


Definition Number of DL TBF establishment requests when MS is in uplink packet transfer mode.
Note: This counter applies to 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.
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 DL TBF establishments

Sub Domain 3 N/A


Measured Object Cell

External Comment --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-127
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P91h - NB_DL_TBF_EST_REQ_EGPRS_MS_Transfer_UL
Radio interface
....................................................................................................................................................................................................................................

Feature Name /

P91i - NB_DL_TBF_EST_REQ_EGPRS_T3192
Descripton

Long Name NB_DL_TBF_EST_REQ_EGPRS_T3192

Definition Number of DL TBF establishment requests received while the timer T3192 is running at BSS side.
Note: This counter applies to 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.
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 DL TBF establishments

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P98a - NB_DL_TBF_REL_SUSP
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
52-128 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P98b - NB_UL_TBF_REL_SUSP
Radio interface
....................................................................................................................................................................................................................................

P98b - NB_UL_TBF_REL_SUSP
Descripton

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 --
Feature Name /

P98c - NB_SUSPEND_REQ_FOR_DL_TBF
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-129
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P98d - NB_SUSPEND_REQ_FOR_UL_TBF
Radio interface
....................................................................................................................................................................................................................................

P98d - NB_SUSPEND_REQ_FOR_UL_TBF
Descripton

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 --
Feature Name /

P98e - NB_SUSP_DL_TBF_REL
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
52-130 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P98f - NB_SUSP_UL_TBF_REL
Radio interface
....................................................................................................................................................................................................................................

P98f - NB_SUSP_UL_TBF_REL
Descripton

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 --
Feature Name /

P9a - NB_DL_TBF_NORM_REL_EGPRS
Descripton

Long Name NB_DL_TBF_NORM_REL_EGPRS


Definition Number of DL TBF in EGPRS mode 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).
Note: The counter only concerns TBF in EGPRS mode.

Sub Domain 1 Radio interface


Sub Domain 2 DL TBF releases

Sub Domain 3 N/A


Measured Object Cell

External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 52-131
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P9a - NB_DL_TBF_NORM_REL_EGPRS

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
52-132 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
53 53
Resource availability and
usage

Abis interface

P465 - MAX_NB_USED_EXTRA_BONUS_ABIS_NIBBLES
Descripton

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

Feature Name Enhanced Transmission Resource Management

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P466 - CUMULATED_TIME_USED_EXTRA_BONUS-
Abis interface _ABIS_NIBBLES
....................................................................................................................................................................................................................................

P466 - CUMULATED_TIME_USED_EXTRA_BONUS_ABIS_NIBBLES
Descripton

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 --
Feature Name Enhanced Transmission Resource Management

P472 - CUMULATED_TIME_FREE_EXTRA_BONUS_ABIS_NIBBLES
Descripton

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

Feature Name Enhanced Transmission Resource Management

....................................................................................................................................................................................................................................
53-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P484 - MIN_NB_FREE_EXTRA_BONUS_ABIS_NIBBLE
Abis interface
....................................................................................................................................................................................................................................

P484 - MIN_NB_FREE_EXTRA_BONUS_ABIS_NIBBLE
Descripton

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

Feature Name Enhanced Transmission Resource Management

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P100c - CUMULATED_TIME_BUSY_GCH_CELL
Ater interface
....................................................................................................................................................................................................................................

Ater interface

P100c - CUMULATED_TIME_BUSY_GCH_CELL
Descripton

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 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.
Feature Name Enhanced Transmission Resource Management

P100d - MAX_NB_BUSY_GCH_CELL
Descripton

Long Name MAX_NB_BUSY_GCH_CELL


Definition Maximum number of busy GCH (16k channel) in the cell.
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 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.

....................................................................................................................................................................................................................................
53-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P100d - MAX_NB_BUSY_GCH_CELL
Ater interface
....................................................................................................................................................................................................................................

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.
Feature Name Enhanced Transmission Resource Management

P100e - MIN_NB_BUSY_GCH_CELL
Descripton

Long Name MIN_NB_BUSY_GCH_CELL


Definition Minimum number of busy GCH (16k channel) in the GPU.
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 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.


Feature Name Enhanced Transmission Resource Management

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P100f - MAX_NB_GCH_BUSY_GPU
Ater interface
....................................................................................................................................................................................................................................

P100f - MAX_NB_GCH_BUSY_GPU
Descripton

Long Name MAX_NB_GCH_BUSY_GPU

Definition Maximum number of busy GCH (16k channel) in the GPU.


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 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 Sub_BSS (BSC/FABRIC)


External Comment It is the equivalent of P100b (B8) at GPU level.

Feature Name Enhanced Transmission Resource Management

P101 - CUMULATED_TIME_AVAIL_GCH_GPU
Descripton

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

....................................................................................................................................................................................................................................
53-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P101 - CUMULATED_TIME_AVAIL_GCH_GPU
Ater interface
....................................................................................................................................................................................................................................

Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)


External Comment --

Feature Name /

P32 - TIME_LAPD_NOT_AVAIL
Descripton

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

Feature Name /

P383a - TIME_ATERMUX_CONG
Descripton

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 Sub_BSS (BSC/FABRIC)


External Comment --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P383a - TIME_ATERMUX_CONG
Ater interface
....................................................................................................................................................................................................................................

Feature Name /

P383b - TIME_HIGH_ATER_USAGE
Descripton

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 Sub_BSS (BSC/FABRIC)


External Comment --
Feature Name /

P469 - MAX_NB_DEFICIT_GCH
Descripton

Long Name MAX_NB_DEFICIT_GCH


Definition Maximum number of GCH in deficit reached in the cell.

....................................................................................................................................................................................................................................
53-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P469 - MAX_NB_DEFICIT_GCH
Ater interface
....................................................................................................................................................................................................................................

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.
Sub Domain 1 Ater interface
Sub Domain 2 GCH
Sub Domain 3 N/A

Measured Object Cell


External Comment --
Feature Name Enhanced Transmission Resource Management

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P470 - CUMULATED_TIME_DEFICIT_GCH
Ater interface
....................................................................................................................................................................................................................................

P470 - CUMULATED_TIME_DEFICIT_GCH
Descripton

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

Feature Name Enhanced Transmission Resource Management

....................................................................................................................................................................................................................................
53-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P471 - CUMULATED_TIME_EXCESS_GCH
Ater interface
....................................................................................................................................................................................................................................

P471 - CUMULATED_TIME_EXCESS_GCH
Descripton

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 :
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 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.
Sub Domain 1 Ater interface

Sub Domain 2 GCH

Sub Domain 3 N/A


Measured Object Cell
External Comment --

Feature Name Enhanced Transmission Resource Management

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P474 - CUMULATED_TIME_FREE_ATER_NIBBLES
Ater interface
....................................................................................................................................................................................................................................

P474 - CUMULATED_TIME_FREE_ATER_NIBBLES
Descripton

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 Sub_BSS (BSC/FABRIC)


External Comment --

Feature Name Enhanced Transmission Resource Management

P486 - MIN_NB_FREE_ATER_NIBBLE
Descripton

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 Sub_BSS (BSC/FABRIC)


External Comment --

Feature Name Enhanced Transmission Resource Management

....................................................................................................................................................................................................................................
53-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P80a - CUMULATED_TIME_ATER_CONG
Ater interface
....................................................................................................................................................................................................................................

P80a - CUMULATED_TIME_ATER_CONG
Descripton

Long Name CUMULATED_TIME_ATER_CONG

Definition Number of block periods during which some TBFs are not fully scheduled due to transmission congestion.
Trigger condition The counter cumulates the number of block periods when MAC fails to schedule a DL (or UL) radio block
due to GCH shortage on an established TRX.
Notes:
1) the counter is cumulated over all the TRX of the cell.
2) the time is provided in number of 20ms block period.

Sub Domain 1 Ater interface


Sub Domain 2 GCH

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P80b - CUMULATED_TIME_NON_ATER_CONG
Descripton

Long Name CUMULATED_TIME_NON_ATER_CONG


Definition Number of block periods during which no Ater congestion is detected by MAC layer in the scheduling
phase.
Trigger condition The counter cumulates the number of block periods when the number of GCH available on an established
TRX is sufficient for traffic scheduling.
Notes:
1) the counter is cumulated over all the TRX of the cell.
2) the time is provided in number of 20ms block period.
Sub Domain 1 Ater interface

Sub Domain 2 GCH


Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P81a - DL_BLKS_NOT_FULLY_SCHEDULED_ATER_CONG
Ater interface
....................................................................................................................................................................................................................................

P81a - DL_BLKS_NOT_FULLY_SCHEDULED_ATER_CONG
Descripton

Long Name DL_BLKS_NOT_FULLY_SCHEDULED_ATER_CONG

Definition Number of radio blocks not fully scheduled in DL during block periods when transmission congestion is
detected.
Trigger condition When transmission congestion is detected in a given block period, this counter computes the number of
PDCH that fulfill the following condition:
* One DL useful radio block (control or data block) is foreseen to be scheduled on the PDCH but due to
GCH shortage, the block is not scheduled in DL finally.
Notes:
1) a PDCH used to transfer another block with lower coding scheme is counted (considered as not fully
scheduled from transmission resource point of view).
2) the counter is cumulated over all the TRX of the cell.

Sub Domain 1 Ater interface


Sub Domain 2 GCH
Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P81b - DL_BLKS_SCHEDULED_ATER_CONG
Descripton

Long Name DL_BLKS_SCHEDULED_ATER_CONG

Definition Number of radio blocks scheduled in DL during block periods when transmission congestion is detected.
Trigger condition When transmission congestion is detected in a given block period, this counter computes the number of
PDCH scheduled in DL for useful radio blocks (control or data block) with sufficient GCH. The PDDCB is
excluded.
Notes:
1) if there is no transmission congestion in a given block period, then the counter is not increased.
2) a PDCH already considered in P81a is not counted.
3) the counter is cumulated over all the TRX of the cell.
Sub Domain 1 Ater interface

Sub Domain 2 GCH

Sub Domain 3 N/A


Measured Object Cell

....................................................................................................................................................................................................................................
53-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P81b - DL_BLKS_SCHEDULED_ATER_CONG
Ater interface
....................................................................................................................................................................................................................................

External Comment --

Feature Name /

P82a - UL_BLKS_NOT_FULLY_SCHEDULED_ATER_CONG
Descripton

Long Name UL_BLKS_NOT_FULLY_SCHEDULED_ATER_CONG

Definition Number of radio blocks not fully scheduled in UL during block periods when transmission congestion is
detected.
Trigger condition When transmission congestion is detected in a given block period, this counter computes the number of
PDCH that fulfill the following condition:
One UL useful radio block is foreseen to be scheduled on the PDCH, but due to GCH shortage:
* the data block is not scheduled,
* or the control block is not scheduled smoothly.
Notes:
1) a PDCH to be scheduled for a TBF in extended mode is counted.
2) a PDCH used to transfer another block with lower coding scheme is counted (considered as not fully
scheduled from transmission resource point of view).
3) for the control block, even if no GCH resources are available for it, MAC will still try to schedule it as
this block is scheduled by polling or one block reservation in previous BPs. The term not-smooth here
means the transmission resources are not well reserved for the control blocks.
4) the counter is cumulated over all the TRX of the cell.
Sub Domain 1 Ater interface

Sub Domain 2 GCH


Sub Domain 3 N/A
Measured Object Cell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P82b - UL_BLKS_SCHEDULED_ATER_CONG
Ater interface
....................................................................................................................................................................................................................................

P82b - UL_BLKS_SCHEDULED_ATER_CONG
Descripton

Long Name UL_BLKS_SCHEDULED_ATER_CONG

Definition Number of radio blocks scheduled in UL during block periods when transmission congestion is detected.
Trigger condition When transmission congestion is detected in a given block period, this counter computes the number of
PDCH scheduled in UL for useful radio blocks (control or data block) with sufficient GCH.
Notes:
1) if there is no transmission congestion in a given block period, then the counter is not increased.
2) a PDCH already considered in P82a is not counted.
3) the counter is cumulated over all the TRX of the cell.
Sub Domain 1 Ater interface

Sub Domain 2 GCH

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P83a - CUMULATED_MISSING_GCH_DL_ATER_CONG
Descripton

Long Name CUMULATED_MISSING_GCH_DL_ATER_CONG


Definition Difference between the number of GCH required for the fully scheduling in DL and the number of available
GCH during block periods when transmission congestion is detected.
Trigger condition For a given TRX, if the number of allocated GCH is not enough to fully schedule all DL blocks in a given
block period, this counter computes each additional missing GCH.
Note: the counter is cumulated over all the TRX of the cell.

Sub Domain 1 Ater interface

Sub Domain 2 GCH


Sub Domain 3 N/A

Measured Object Cell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
53-16 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P83b - CUMULATED_ESTABLISHED_GCH_DL_ATER
Ater interface
....................................................................................................................................................................................................................................

P83b - CUMULATED_ESTABLISHED_GCH_DL_ATER
Descripton

Long Name CUMULATED_ESTABLISHED_GCH_DL_ATER

Definition Number of GCH available during block periods in DL when transmission congestion is detected.
Trigger condition For a given TRX, if the number of allocated GCH is not enough to fully schedule all DL blocks in a given
block period, this counter computes the number of GCH established on the TRX.
Note: the counter is cumulated over all the TRX of the cell.
Sub Domain 1 Ater interface

Sub Domain 2 GCH


Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P84a - CUMULATED_MISSING_GCH_UL_ATER_CONG
Descripton

Long Name CUMULATED_MISSING_GCH_UL_ATER_CONG


Definition Difference between the number of GCH required for the fully scheduling in UL and the number of GCH
available during block periods when transmission congestion is detected.
Trigger condition For a given TRX, if the number of allocated GCH is not enough to fully schedule all UL blocks in a given
block period, this counter computes each additional missing GCH.
Note: the counter is cumulated over all the TRX of the cell.

Sub Domain 1 Ater interface


Sub Domain 2 GCH

Sub Domain 3 N/A


Measured Object Cell

External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-17
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P84b - CUMULATED_ESTABLISHED_GCH_UL_ATER
Ater interface
....................................................................................................................................................................................................................................

P84b - CUMULATED_ESTABLISHED_GCH_UL_ATER
Descripton

Long Name CUMULATED_ESTABLISHED_GCH_UL_ATER

Definition Number of GCH available during block periods in UL when transmission congestion is detected.
Trigger condition For a given TRX, if the number of allocated GCH is not enough to fully schedule all UL blocks in a given
block period, this counter computes the number of GCH established on the TRX.
Note: the counter is cumulated over all the TRX of the cell.
Sub Domain 1 Ater interface

Sub Domain 2 GCH


Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P85 - UL_BLKS_DISCARDED_BY_BTS_ATER_CONG
Descripton

Long Name UL_BLKS_DISCARDED_BY_BTS_ATER_CONG


Definition Number of UL radio blocks discarded by BTS due to Ater congestion.
Trigger condition On reception of DISCARD_COLLECT message from BTS, this counter computes the number of radio
blocks discarded.
Sub Domain 1 Ater interface

Sub Domain 2 GCH


Sub Domain 3 N/A

Measured Object Cell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
53-18 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P87a - ATER_EQUITY_REALLOCATED_GCH
Ater interface
....................................................................................................................................................................................................................................

P87a - ATER_EQUITY_REALLOCATED_GCH
Descripton

Long Name ATER_EQUITY_REALLOCATED_GCH

Definition Cumulative number of GCH (16k channel) reallocated by the Ater GCH Equity process.
Trigger condition The counter cumulates over the Granularity Period the number of GCH reallocated by Ater GCH Equity to
lowest TRX that is calculated at each trigger of the Ater GCH Equity algorithm.

Sub Domain 1 Ater interface


Sub Domain 2 GCH

Sub Domain 3 N/A


Measured Object Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name Ater GCH Equity Algorithm (Step1)

P87b - ATER_EQUITY_MIN_RATIO_TBF_PER_GCH
Descripton

Long Name ATER_EQUITY_MIN_RATIO_TBF_PER_GCH


Definition Minimum value per GPU of the ratio (number of GCH divided by number of allocated TBF) calculated per
TRX.
Trigger condition The counter gives the MIN of the ratio (number of GCH divided by number of allocated TBF) of all TRX
and used in the Ater GCH Equity for selecting the lowest TRX. The ratios are calculated at each trigger of
the Ater GCH Equity algorithm.
Note: number of GCH = Nb Estab GCH + Nb Reserved GCH _ Nb Release GCH
Sub Domain 1 Ater interface

Sub Domain 2 GCH


Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name Ater GCH Equity Algorithm (Step1)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-19
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P87c - ATER_EQUITY_MAX_RATIO_TBF_PER_GCH
Ater interface
....................................................................................................................................................................................................................................

P87c - ATER_EQUITY_MAX_RATIO_TBF_PER_GCH
Descripton

Long Name ATER_EQUITY_MAX_RATIO_TBF_PER_GCH

Definition Maximum value per GPU of the ratio (number of GCH divided by number of allocated TBF) calculated per
TRX.
Trigger condition The counter gives the MAX of the ratio (number of GCH divided by number of allocated TBF) of all TRX
and used in the Ater GCH Equity for selecting the lowest TRX. The ratios are calculated at each trigger of
the Ater GCH Equity algorithm.
Note: number of GCH = Nb Estab GCH + Nb Reserved GCH _ Nb Release GCH
Sub Domain 1 Ater interface

Sub Domain 2 GCH


Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)


External Comment --
Feature Name Ater GCH Equity Algorithm (Step1)

P87d - ATER_EQUITY_AVG_RATIO_TBF_PER_GCH
Descripton

Long Name ATER_EQUITY_AVG_RATIO_TBF_PER_GCH


Definition Average value per GPU of the ratio (number of GCH divided by number of allocated TBF) calculated per
TRX.
Trigger condition The counter gives the AVERAGE of the ratio (number of GCH divided by number of allocated TBF) of all
TRX and used in the Ater GCH Equity for selecting the lowest TRX. The ratios are calculated at each trigger
of the Ater GCH Equity algorithm.
Note: number of GCH = Nb Estab GCH + Nb Reserved GCH _ Nb Release GCH

Sub Domain 1 Ater interface


Sub Domain 2 GCH

Sub Domain 3 N/A


Measured Object Sub_BSS (BSC/FABRIC)

External Comment --

Feature Name Ater GCH Equity Algorithm (Step1)

....................................................................................................................................................................................................................................
53-20 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P87e - ATER_EQUITY_TIME_TARGET_NOT_REACHED
Ater interface
....................................................................................................................................................................................................................................

P87e - ATER_EQUITY_TIME_TARGET_NOT_REACHED
Descripton

Long Name ATER_EQUITY_TIME_TARGET_NOT_REACHED

Definition Cumulative time (in seconds) per GPU during which the Ater GCH Equity has not reached to reallocate
enough GCH to a lowest TRX.
Trigger condition The counting is started at a Ater GCH Equity trigger when the number of GCH that can be reallocated to a
lowest TRX is not enough to fulfill the requirement for this lowest TRX.
The counting is stopped when the number of reallocated GCH is enough.
Sub Domain 1 Ater interface

Sub Domain 2 GCH


Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)


External Comment --
Feature Name Ater GCH Equity Algorithm (Step1)

P88a - ATER_EQUITY_MIN_RATIO_GPU_GCH_NEEDS
Descripton

Long Name ATER_EQUITY_MIN_RATIO_GPU_GCH_NEEDS


Definition Minimum value per GPU of the ratio between current number of GCHs allocated by PMU and number of
GCHs needed by PTU calculated per TRX.
Trigger condition The counter gives the MIN of the ratio between current number of GCHs allocated by PMU and number of
GCHs needed by PTU of all TRX and used in the Ater GCH Equity (Step2) for selecting the lowest and
highest TRX. The ratios are calculated at each trigger of the Ater GCH Equity algorithm.

Sub Domain 1 Ater interface


Sub Domain 2 GCH

Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)


External Comment --
Feature Name Ater GCH Equity Algorithm (Step2)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-21
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P88b - ATER_EQUITY_MAX_RATIO_GPU_GCH_NEEDS
Ater interface
....................................................................................................................................................................................................................................

P88b - ATER_EQUITY_MAX_RATIO_GPU_GCH_NEEDS
Descripton

Long Name ATER_EQUITY_MAX_RATIO_GPU_GCH_NEEDS

Definition Maximum value per GPU of the ratio between current number of GCHs allocated by PMU and number of
GCHs needed by PTU calculated per TRX.
Trigger condition The counter gives the MAX of the ratio between current number of GCHs allocated by PMU and number of
GCHs needed by PTU of all TRX and used in the Ater GCH Equity (Step2) for selecting the lowest and
highest TRX. The ratios are calculated at each trigger of the Ater GCH Equity Algorithm.

Sub Domain 1 Ater interface


Sub Domain 2 GCH

Sub Domain 3 N/A


Measured Object Sub_BSS (BSC/FABRIC)
External Comment --
Feature Name Ater GCH Equity Algorithm (Step2)

P88c - ATER_EQUITY_AVG_RATIO_GPU_GCH_NEEDS
Descripton

Long Name ATER_EQUITY_AVG_RATIO_GPU_GCH_NEEDS


Definition Average value per GPU of the ratio between current number of GCHs allocated by PMU and number of
GCHs needed by PTU calculated per TRX.
Trigger condition The counter gives the AVERAGE of the ratio between current number of GCHs allocated by PMU and
number of GCHs needed by PTU of all TRX and used in the Ater GCH Equity (Step2) for selecting the
lowest and highest TRX. The ratios are calculated at each trigger of the Ater GCH Equity algorithm.

Sub Domain 1 Ater interface


Sub Domain 2 GCH

Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)


External Comment --
Feature Name Ater GCH Equity Algorithm (Step2)

....................................................................................................................................................................................................................................
53-22 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P33 - TIME_BEAR_CHAN_NOT_AVAIL
Gb interface
....................................................................................................................................................................................................................................

Gb interface

P33 - TIME_BEAR_CHAN_NOT_AVAIL
Descripton

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 --
Feature Name /

P34 - TIME_PVC_NOT_AVAIL
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-23
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P34a - TIME_SGSN_IP_ENDPOINT_NOT_AVAIL_GBIP
Gb interface
....................................................................................................................................................................................................................................

P34a - TIME_SGSN_IP_ENDPOINT_NOT_AVAIL_GBIP
Descripton

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 --
Feature Name Gb over IP

P4 - TIME_PVC_CONG_FRAME_RELAY
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
53-24 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P5 - TIME_PVC_CONG_LEVEL1
Gb interface
....................................................................................................................................................................................................................................

P5 - TIME_PVC_CONG_LEVEL1
Descripton

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

Feature Name /

P67 - TIME_BVC_NOT_AVAIL
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-25
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P129a - CUMULATED_ACTIVE_UL_CONNECTED-
Radio interface _TIME_GPRS_ACK
....................................................................................................................................................................................................................................

Radio interface

P129a - CUMULATED_ACTIVE_UL_CONNECTED_TIME_GPRS_ACK
Descripton

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 abnormal UL TBF
release.
The time is provided in seconds with one significant value after the comma (i.e. ROUND(10x) / 10): for
example, if the time is 15.1 seconds, this duration of time is provided with the number 151.
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 --
Feature Name Extended UL TBF mode

....................................................................................................................................................................................................................................
53-26 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P129b - CUMULATED_ACTIVE_UL_CONNECTED-
Radio interface _TIME_GPRS_NACK
....................................................................................................................................................................................................................................

P129b - CUMULATED_ACTIVE_UL_CONNECTED-
_TIME_GPRS_NACK
Descripton

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 not in extended phase.

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 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 --
Feature Name Extended UL TBF mode

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-27
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P129c - CUMULATED_ACTIVE_UL_CONNECTED-
Radio interface _TIME_EGPRS_ACK
....................................................................................................................................................................................................................................

P129c - CUMULATED_ACTIVE_UL_CONNECTED-
_TIME_EGPRS_ACK
Descripton

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 not in extended phase.

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 : 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 --
Feature Name Extended UL TBF mode

....................................................................................................................................................................................................................................
53-28 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P129d - CUMULATED_ACTIVE_UL_CONNECTED-
Radio interface _TIME_EGPRS_NACK
....................................................................................................................................................................................................................................

P129d - CUMULATED_ACTIVE_UL_CONNECTED-
_TIME_EGPRS_NACK
Descripton

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 not in extended phase.

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

Feature Name Extended UL TBF mode

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-29
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P13 - TIME_DL_PDCH_CONG
Radio interface
....................................................................................................................................................................................................................................

P13 - TIME_DL_PDCH_CONG
Descripton

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 --
Feature Name Autonomous Packet Resource Allocation (RAE-4)

P16 - CUMULATED_OVERALL_DL_CONNECTION_TIME
Descripton

Long Name CUMULATED_OVERALL_DL_CONNECTION_TIME


Definition Cumulated overall time (i.e. active and delayed) of DL TBF connections.

....................................................................................................................................................................................................................................
53-30 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P16 - CUMULATED_OVERALL_DL_CONNECTION_TIME
Radio interface
....................................................................................................................................................................................................................................

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

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-31
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P160 - NB_DL_TBF_1_succ
Radio interface
....................................................................................................................................................................................................................................

P160 - NB_DL_TBF_1_succ
Descripton

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 --
Feature Name Support of GPRS QoS

P161 - NB_UL_TBF_1_succ
Descripton

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

....................................................................................................................................................................................................................................
53-32 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P161 - NB_UL_TBF_1_succ
Radio interface
....................................................................................................................................................................................................................................

External Comment --

Feature Name /

P162 - NB_DL_TBF_2_3_succ
Descripton

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 PDCH allocation for DL TBF

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name Support of GPRS QoS

P163 - NB_UL_TBF_2_3_succ
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-33
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P163 - NB_UL_TBF_2_3_succ
Radio interface
....................................................................................................................................................................................................................................

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

Sub Domain 1 Radio interface


Sub Domain 2 PDCH allocation for UL TBF

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P164 - NB_DL_TBF_4_5_succ
Descripton

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 PDCH allocation for DL TBF


Sub Domain 3 N/A

Measured Object Cell

External Comment --
Feature Name Support of GPRS QoS

....................................................................................................................................................................................................................................
53-34 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P165 - NB_UL_TBF_4_5_succ
Radio interface
....................................................................................................................................................................................................................................

P165 - NB_UL_TBF_4_5_succ
Descripton

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 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 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 PDCH allocation for UL TBF


Sub Domain 3 N/A

Measured Object Cell


External Comment --
Feature Name /

P26 - TIME_UL_PDCH_CONG
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-35
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P26 - TIME_UL_PDCH_CONG
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name Autonomous Packet Resource Allocation (RAE-4)

P30d - NB_UL_TBF_EST_SUCC_EGPRS_PIM
Descripton

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 UL TBF establishments

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P35 - MAX_NB_DL_TBF_SIMUL_EST
Descripton

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 PDCH allocation for DL TBF


Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

....................................................................................................................................................................................................................................
53-36 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P36 - AV_NB_DL_TBF_SIMUL_EST
Radio interface
....................................................................................................................................................................................................................................

P36 - AV_NB_DL_TBF_SIMUL_EST
Descripton

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 PDCH allocation for DL TBF

Sub Domain 3 N/A


Measured Object Cell
External Comment --
Feature Name /

P38b - CUMULATED_TIME_PDCH_USED
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-37
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P38c - CUMULATED_TIME_PDCH_USED_EGPRS
Radio interface
....................................................................................................................................................................................................................................

P38c - CUMULATED_TIME_PDCH_USED_EGPRS
Descripton

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 --
Feature Name /

P38e - CUMULATED_TIME_PDCH_USED_DL_CELL
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
53-38 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P38f - CUMULATED_TIME_PDCH_USED_UL_CELL
Radio interface
....................................................................................................................................................................................................................................

P38f - CUMULATED_TIME_PDCH_USED_UL_CELL
Descripton

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 --
Feature Name /

P38g - CUMULATED_TIME_PDCH_USED_GPRS
Descripton

Long Name CUMULATED_TIME_PDCH_USED_GPRS


Definition Cumulated time during which the slave PDCHs carry at least one UL or DL TBF established in GPRS 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 GPRS 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 --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-39
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P39 - MAX_NB_UL_TBF_SIMUL_EST
Radio interface
....................................................................................................................................................................................................................................

P39 - MAX_NB_UL_TBF_SIMUL_EST
Descripton

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 PDCH allocation for UL TBF

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P40 - AV_NB_UL_TBF_SIMUL_EST
Descripton

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 PDCH allocation for UL TBF
Sub Domain 3 N/A
Measured Object Cell

External Comment --

Feature Name /

....................................................................................................................................................................................................................................
53-40 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P409 - CUMULATED_TIME_DL_BIASED_AND_OPTI-
Radio interface MAL_DL_ALLOCATION
....................................................................................................................................................................................................................................

P409 - CUMULATED_TIME_DL_BIASED_AND_OPTI-
MAL_DL_ALLOCATION
Descripton

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.
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-41
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P410 - CUMULATED_TIME_UL_BIASED_AND_OPTI-
Radio interface MAL_UL_ALLOCATION
....................................................................................................................................................................................................................................

P410 - CUMULATED_TIME_UL_BIASED_AND_OPTI-
MAL_UL_ALLOCATION
Descripton

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. 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 optimal UL biaised 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 - 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.

Feature Name /

....................................................................................................................................................................................................................................
53-42 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P411 - CUMULATED_TIME_DL_BIASED_DL_TBF
Radio interface
....................................................................................................................................................................................................................................

P411 - CUMULATED_TIME_DL_BIASED_DL_TBF
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-43
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P412 - CUMULATED_TIME_UL_BIASED_UL_TBF
Radio interface
....................................................................................................................................................................................................................................

P412 - CUMULATED_TIME_UL_BIASED_UL_TBF
Descripton

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 --
Feature Name /

P414bis - CUMULATED_TIME_ALLOCATED_SPDCH
Descripton

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

....................................................................................................................................................................................................................................
53-44 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P414bis - CUMULATED_TIME_ALLOCATED_SPDCH
Radio interface
....................................................................................................................................................................................................................................

External Comment Replaces P414 (B8 counter).

Feature Name Autonomous Packet Resource Allocation (RAE-4)

P415bis - MAX_OF_ALLOCATED_SPDCH
Descripton

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,
the value of allocated SPDCH is stored.
At the end of the granularity period, the maximum 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 Replaces P415 (B8 counter).
Feature Name Autonomous Packet Resource Allocation (RAE-4)

P415ter - MAX_NB_ALLOCATED_SPDCH_GPU
Descripton

Long Name MAX_NB_ALLOCATED_SPDCH_GPU

Definition This counter gives the maximum number of allocated SPDCH at GPU level during the whole granularity
period.

Trigger condition Every time the cells mapped on the GPU receive a BSCGP RADIO-RESOURCE-ALLOCATION-
INDICATION message from the BSC, the sum of the allocated PDCHs at cell level (provided by the bitmap
"SPDCH_Allocation_List" in the message) is computed on all the cells mapped on the GPU. If the new
value is higher than the stored one, it becomes the new maximum value.

Sub Domain 1 Radio interface

Sub Domain 2 PDCH


Sub Domain 3 N/A
Measured Object Sub_BSS (BSC/FABRIC)

External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-45
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P416bis - MIN_OF_ALLOCATED_SPDCH
Radio interface
....................................................................................................................................................................................................................................

P416bis - MIN_OF_ALLOCATED_SPDCH
Descripton

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 Replaces P416 (B8 counter).
Feature Name Autonomous Packet Resource Allocation (RAE-4)

P417 - NB_PREEMPTED_PDCH
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
53-46 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P419 - CUMULATED_TIME_DL_BIASED
Radio interface
....................................................................................................................................................................................................................................

P419 - CUMULATED_TIME_DL_BIASED
Descripton

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 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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-47
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P420 - CUMULATED_TIME_UL_BIASED
Radio interface
....................................................................................................................................................................................................................................

P420 - CUMULATED_TIME_UL_BIASED
Descripton

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 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 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 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 --
Feature Name /

....................................................................................................................................................................................................................................
53-48 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P451a - CUMULATED_TIME_PDCH_UL_TBF_CELL
Radio interface
....................................................................................................................................................................................................................................

P451a - CUMULATED_TIME_PDCH_UL_TBF_CELL
Descripton

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 value after the comma (i.e. ROUND(10x) / 10).

Sub Domain 1 Radio interface


Sub Domain 2 PDCH allocation for UL TBF

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P451b - CUMULATED_TIME_PDCH_DL_TBF_CELL
Descripton

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 value after the comma (i.e. ROUND(10x) / 10).

Sub Domain 1 Radio interface

Sub Domain 2 PDCH allocation for DL TBF


Sub Domain 3 N/A
Measured Object Cell

External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-49
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P452 - CUMULATED_TIME_PDCH_DL_TBF_GMM_SIG_CELL
Radio interface
....................................................................................................................................................................................................................................

P452 - CUMULATED_TIME_PDCH_DL_TBF_GMM_SIG_CELL
Descripton

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 PDCH allocation for DL TBF

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P453a_1 - DISTRIB_UL_TBF_DURATION_1
Descripton

Long Name DISTRIB_UL_TBF_DURATION_1


Definition First cell of the distribution on UL TBF duration.
It contains :
1) number of UL TBFs whose duration is in duration band 1
Duration band 1 is defined by :
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 unacknowledged mode are taken
into account. Only the active phase of the TBF 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 --

....................................................................................................................................................................................................................................
53-50 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P453a_1 - DISTRIB_UL_TBF_DURATION_1
Radio interface
....................................................................................................................................................................................................................................

Feature Name /

P453a_10 - DISTRIB_UL_TBF_DURATION_10
Descripton

Long Name DISTRIB_UL_TBF_DURATION_10

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 UL 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.
Duration is measured as for P129a, P129b, P129c, P129d.
Whenever a TBF duration exceeds PD_UL_TBF_DURATION_THR_10, then it is not taken into account.

Sub Domain 1 Radio interface


Sub Domain 2 UL TBF duration

Sub Domain 3 N/A


Measured Object DistCell
External Comment --
Feature Name /

P453a_2 - DISTRIB_UL_TBF_DURATION_2
Descripton

Long Name DISTRIB_UL_TBF_DURATION_2


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 :
PD_UL_TBF_DURATION_THR_1<= duration < PD_UL_TBF_DURATION_THR_2

Trigger condition UL 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.
Duration is measured as for P129a, P129b, P129c, P129d.

Sub Domain 1 Radio interface

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-51
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P453a_2 - DISTRIB_UL_TBF_DURATION_2
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 2 UL TBF duration

Sub Domain 3 N/A


Measured Object DistCell

External Comment --
Feature Name /

P453a_3 - DISTRIB_UL_TBF_DURATION_3
Descripton

Long Name DISTRIB_UL_TBF_DURATION_3


Definition Third cell of the distribution on UL TBF duration.
It contains :
1) number of UL TBFs whose duration is in duration band 3
Duration band 3 is defined by :
PD_UL_TBF_DURATION_THR_2<= duration < PD_UL_TBF_DURATION_THR_3

Trigger condition UL 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.
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 --

Feature Name /

....................................................................................................................................................................................................................................
53-52 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P453a_4 - DISTRIB_UL_TBF_DURATION_4
Radio interface
....................................................................................................................................................................................................................................

P453a_4 - DISTRIB_UL_TBF_DURATION_4
Descripton

Long Name DISTRIB_UL_TBF_DURATION_4

Definition Fourth cell of the distribution on UL TBF duration.


It contains :
1) number of UL TBFs whose duration is in duration band 4
Duration band 4 is defined by :
PD_UL_TBF_DURATION_THR_3<= duration < PD_UL_TBF_DURATION_THR_4

Trigger condition UL 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.
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 --

Feature Name /

P453a_5 - DISTRIB_UL_TBF_DURATION_5
Descripton

Long Name DISTRIB_UL_TBF_DURATION_5


Definition Fifth cell of the distribution on UL TBF duration.
It contains :
1) number of UL TBFs whose duration is in duration band 5
Duration band 5 is defined by :
PD_UL_TBF_DURATION_THR_4<= duration < PD_UL_TBF_DURATION_THR_5
Trigger condition UL 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.
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 --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-53
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P453a_5 - DISTRIB_UL_TBF_DURATION_5
Radio interface
....................................................................................................................................................................................................................................

Feature Name /

P453a_6 - DISTRIB_UL_TBF_DURATION_6
Descripton

Long Name DISTRIB_UL_TBF_DURATION_6

Definition Sixth cell of the distribution on UL TBF duration.


It contains :
1) number of UL TBFs whose duration is in duration band 6
Duration band 6 is defined by :
PD_UL_TBF_DURATION_THR_5<= duration < PD_UL_TBF_DURATION_THR_6

Trigger condition UL 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.
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 --

Feature Name /

P453a_7 - DISTRIB_UL_TBF_DURATION_7
Descripton

Long Name DISTRIB_UL_TBF_DURATION_7


Definition Seventh cell of the distribution on UL TBF duration.
It contains :
1) number of UL TBFs whose duration is in duration band 7
Duration band 7 is defined by :
PD_UL_TBF_DURATION_THR_6<= duration < PD_UL_TBF_DURATION_THR_7

Trigger condition UL 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.
Duration is measured as for P129a, P129b, P129c, P129d.

Sub Domain 1 Radio interface

Sub Domain 2 UL TBF duration

....................................................................................................................................................................................................................................
53-54 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P453a_7 - DISTRIB_UL_TBF_DURATION_7
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 N/A

Measured Object DistCell


External Comment --

Feature Name /

P453a_8 - DISTRIB_UL_TBF_DURATION_8
Descripton

Long Name DISTRIB_UL_TBF_DURATION_8

Definition Eighth cell of the distribution on UL TBF duration.


It contains :
1) number of UL TBFs whose duration is in duration band 8
Duration band 8 is defined by :
PD_UL_TBF_DURATION_THR_7<= duration < PD_UL_TBF_DURATION_THR_8

Trigger condition UL 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.
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 --

Feature Name /

P453a_9 - DISTRIB_UL_TBF_DURATION_9
Descripton

Long Name DISTRIB_UL_TBF_DURATION_9

Definition Nineth cell of the distribution on UL TBF duration.


It contains :
1) number of UL TBFs whose duration is in duration band 9
Duration band 9 is defined by :
PD_UL_TBF_DURATION_THR_8<= duration < PD_UL_TBF_DURATION_THR_9

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-55
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P453a_9 - DISTRIB_UL_TBF_DURATION_9
Radio interface
....................................................................................................................................................................................................................................

Trigger condition UL 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.
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 --

Feature Name /

P453b_1 - DISTRIB_DL_TBF_DURATION_1
Descripton

Long Name DISTRIB_DL_TBF_DURATION_1


Definition First cell of the distribution 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 --

Feature Name /

....................................................................................................................................................................................................................................
53-56 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P453b_10 - DISTRIB_DL_TBF_DURATION_10
Radio interface
....................................................................................................................................................................................................................................

P453b_10 - DISTRIB_DL_TBF_DURATION_10
Descripton

Long Name DISTRIB_DL_TBF_DURATION_10

Definition Tenth cell of the distribution 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 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.
Whenever a TBF duration exceeds PD_DL_TBF_DURATION_THR_10, then it is not taken into account.

Sub Domain 1 Radio interface


Sub Domain 2 DL TBF duration

Sub Domain 3 N/A


Measured Object DistCell
External Comment --
Feature Name /

P453b_2 - DISTRIB_DL_TBF_DURATION_2
Descripton

Long Name DISTRIB_DL_TBF_DURATION_2


Definition Second cell of the distribution on DL TBF duration.
It contains :
1) number of DL TBFs whose duration is in duration band 2
Duration band 2 is defined by :
PD_DL_TBF_DURATION_THR_1<= duration < PD_DL_TBF_DURATION_THR_2
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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-57
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P453b_2 - DISTRIB_DL_TBF_DURATION_2
Radio interface
....................................................................................................................................................................................................................................

Measured Object DistCell

External Comment --
Feature Name /

P453b_3 - DISTRIB_DL_TBF_DURATION_3
Descripton

Long Name DISTRIB_DL_TBF_DURATION_3

Definition Third cell of the distribution on DL TBF duration.


It contains :
1) number of DL TBFs whose duration is in duration band 3
Duration band 3 is defined by :
PD_DL_TBF_DURATION_THR_2<= duration < PD_DL_TBF_DURATION_THR_3

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

Feature Name /

P453b_4 - DISTRIB_DL_TBF_DURATION_4
Descripton

Long Name DISTRIB_DL_TBF_DURATION_4

Definition Fourth cell of the distribution on DL TBF duration.


It contains :
1) number of DL TBFs whose duration is in duration band 4
Duration band 4 is defined by :
PD_DL_TBF_DURATION_THR_3<= duration < PD_DL_TBF_DURATION_THR_4
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.

....................................................................................................................................................................................................................................
53-58 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P453b_4 - DISTRIB_DL_TBF_DURATION_4
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 1 Radio interface

Sub Domain 2 DL TBF duration


Sub Domain 3 N/A

Measured Object DistCell


External Comment --

Feature Name /

P453b_5 - DISTRIB_DL_TBF_DURATION_5
Descripton

Long Name DISTRIB_DL_TBF_DURATION_5


Definition Fifth cell of the distribution on DL TBF duration.
It contains :
1) number of DL TBFs whose duration is in duration band 5
Duration band 5 is defined by :
PD_DL_TBF_DURATION_THR_4<= duration < PD_DL_TBF_DURATION_THR_5
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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-59
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P453b_6 - DISTRIB_DL_TBF_DURATION_6
Radio interface
....................................................................................................................................................................................................................................

P453b_6 - DISTRIB_DL_TBF_DURATION_6
Descripton

Long Name DISTRIB_DL_TBF_DURATION_6

Definition Sixth cell of the distribution on DL TBF duration.


It contains :
1) number of DL TBFs whose duration is in duration band 6
Duration band 6 is defined by :
PD_DL_TBF_DURATION_THR_5<= duration < PD_DL_TBF_DURATION_THR_6

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

Feature Name /

P453b_7 - DISTRIB_DL_TBF_DURATION_7
Descripton

Long Name DISTRIB_DL_TBF_DURATION_7


Definition Seventh cell of the distribution on DL TBF duration.
It contains :
1) number of DL TBFs whose duration is in duration band 7.
Duration band 7 is defined by :
PD_DL_TBF_DURATION_THR_6<= duration < PD_DL_TBF_DURATION_THR_7
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 --

....................................................................................................................................................................................................................................
53-60 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P453b_7 - DISTRIB_DL_TBF_DURATION_7
Radio interface
....................................................................................................................................................................................................................................

Feature Name /

P453b_8 - DISTRIB_DL_TBF_DURATION_8
Descripton

Long Name DISTRIB_DL_TBF_DURATION_8

Definition Eighth cell of the distribution on DL TBF duration.


It contains :
1) number of DL TBFs whose duration is in duration band 8
Duration band 8 is defined by :
PD_DL_TBF_DURATION_THR_7<= duration < PD_DL_TBF_DURATION_THR_8

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

Feature Name /

P453b_9 - DISTRIB_DL_TBF_DURATION_9
Descripton

Long Name DISTRIB_DL_TBF_DURATION_9


Definition Ninth cell of the distribution on DL TBF duration.
It contains :
1) number of DL TBFs whose duration is in duration band 9
Duration band 9 is defined by :
PD_DL_TBF_DURATION_THR_8<= duration < PD_DL_TBF_DURATION_THR_9

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-61
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P453b_9 - DISTRIB_DL_TBF_DURATION_9
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 N/A

Measured Object DistCell


External Comment --

Feature Name /

P454a_1 - DISTRIB_UL_TBF_VOLUME_1
Descripton

Long Name DISTRIB_UL_TBF_VOLUME_1

Definition First cell of the distribution on volume of UL TBF.


It contains:
1) number of UL TBFs whose LLC volume is in LLC volume band 1.
LLC volume band 1 is defined by :
PD_UL_TBF_VOLUME_THR_0<= LLC volume < PD_UL_TBF_VOLUME_THR_1
PD_UL_TBF_VOLUME_THR_0 = 0 byte
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 UL TBF LLC volume


Sub Domain 3 N/A

Measured Object DistCell


External Comment --
Feature Name /

....................................................................................................................................................................................................................................
53-62 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P454a_10 - DISTRIB_UL_TBF_VOLUME_10
Radio interface
....................................................................................................................................................................................................................................

P454a_10 - DISTRIB_UL_TBF_VOLUME_10
Descripton

Long Name DISTRIB_UL_TBF_VOLUME_10

Definition Tenth cell of the distribution on volume of UL TBF.


It contains:
1) number of UL TBFs whose LLC volume is in LLC volume band 10.
LLC volume band 10 is defined by :
PD_UL_TBF_VOLUME_THR_9<= LLC volume < PD_UL_TBF_VOLUME_THR_10
PD_UL_TBF_VOLUME_THR_10 = 100 000 000 bytes
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.
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 --
Feature Name /

P454a_2 - DISTRIB_UL_TBF_VOLUME_2
Descripton

Long Name DISTRIB_UL_TBF_VOLUME_2


Definition Second cell of the distribution on volume of UL TBF.
It contains:
1) number of UL TBFs whose LLC volume is in LLC volume band 2.
LLC volume band 2 is defined by :
PD_UL_TBF_VOLUME_THR_1<= LLC volume < PD_UL_TBF_VOLUME_THR_2
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 UL TBF LLC volume


Sub Domain 3 N/A

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-63
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P454a_2 - DISTRIB_UL_TBF_VOLUME_2
Radio interface
....................................................................................................................................................................................................................................

Measured Object DistCell

External Comment --
Feature Name /

P454a_3 - DISTRIB_UL_TBF_VOLUME_3
Descripton

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 UL TBF LLC volume
Sub Domain 3 N/A
Measured Object DistCell
External Comment --

Feature Name /

P454a_4 - DISTRIB_UL_TBF_VOLUME_4
Descripton

Long Name DISTRIB_UL_TBF_VOLUME_4

Definition Fourth cell of the distribution on volume of UL TBF.


It contains:
1) number of UL TBFs whose LLC volume is in LLC volume band 4.
LLC volume band 1 is defined by :
PD_UL_TBF_VOLUME_THR_3<= LLC volume < PD_UL_TBF_VOLUME_THR_4
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.

....................................................................................................................................................................................................................................
53-64 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P454a_4 - DISTRIB_UL_TBF_VOLUME_4
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 1 Radio interface

Sub Domain 2 UL TBF LLC volume


Sub Domain 3 N/A

Measured Object DistCell


External Comment --

Feature Name /

P454a_5 - DISTRIB_UL_TBF_VOLUME_5
Descripton

Long Name DISTRIB_UL_TBF_VOLUME_5


Definition Fifth cell of the distribution on volume of UL TBF.
It contains:
1) number of UL TBFs whose LLC volume is in LLC volume band 5.
LLC volume band 5 is defined by :
PD_UL_TBF_VOLUME_THR_4<= LLC volume < PD_UL_TBF_VOLUME_THR_5
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 UL TBF LLC volume


Sub Domain 3 N/A
Measured Object DistCell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-65
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P454a_6 - DISTRIB_UL_TBF_VOLUME_6
Radio interface
....................................................................................................................................................................................................................................

P454a_6 - DISTRIB_UL_TBF_VOLUME_6
Descripton

Long Name DISTRIB_UL_TBF_VOLUME_6

Definition Sixth cell of the distribution on volume of UL TBF.


It contains:
1) number of UL TBFs whose LLC volume is in LLC volume band 6.
LLC volume band 1 is defined by :
PD_UL_TBF_VOLUME_THR_5<= LLC volume < PD_UL_TBF_VOLUME_THR_6

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 UL TBF LLC volume
Sub Domain 3 N/A
Measured Object DistCell
External Comment --

Feature Name /

P454a_7 - DISTRIB_UL_TBF_VOLUME_7
Descripton

Long Name DISTRIB_UL_TBF_VOLUME_7


Definition Seventh cell of the distribution on volume of UL TBF.
It contains:
1) number of UL TBFs whose LLC volume is in LLC volume band 7.
LLC volume band 7 is defined by :
PD_UL_TBF_VOLUME_THR_6<= LLC volume < PD_UL_TBF_VOLUME_THR_7
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 UL TBF LLC volume


Sub Domain 3 N/A

Measured Object DistCell

External Comment --

....................................................................................................................................................................................................................................
53-66 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P454a_7 - DISTRIB_UL_TBF_VOLUME_7
Radio interface
....................................................................................................................................................................................................................................

Feature Name /

P454a_8 - DISTRIB_UL_TBF_VOLUME_8
Descripton

Long Name DISTRIB_UL_TBF_VOLUME_8

Definition Eighth cell of the distribution on volume of UL TBF.


It contains:
1) number of UL TBFs whose LLC volume is in LLC volume band 81.
LLC volume band 8 is defined by :
PD_UL_TBF_VOLUME_THR_7<= LLC volume < PD_UL_TBF_VOLUME_THR_8

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 UL TBF LLC volume
Sub Domain 3 N/A
Measured Object DistCell
External Comment --

Feature Name /

P454a_9 - DISTRIB_UL_TBF_VOLUME_9
Descripton

Long Name DISTRIB_UL_TBF_VOLUME_9


Definition Ninth cell of the distribution on volume of UL TBF.
It contains:
1) number of UL TBFs whose LLC volume is in LLC volume band 9.
LLC volume band 9 is defined by :
PD_UL_TBF_VOLUME_THR_8<= LLC volume < PD_UL_TBF_VOLUME_THR_9

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 UL TBF LLC volume

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-67
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P454a_9 - DISTRIB_UL_TBF_VOLUME_9
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 N/A

Measured Object DistCell


External Comment --

Feature Name /

P454b_1 - DISTRIB_DL_TBF_VOLUME_1
Descripton

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 TBF in GPRS and EGPRS mode, in RLC acknowledged and RLC unacknowledged mode are taken into
account.
The volume is calculated as in P43.
Sub Domain 1 Radio interface

Sub Domain 2 DL TBF LLC volume


Sub Domain 3 N/A

Measured Object DistCell


External Comment --
Feature Name /

....................................................................................................................................................................................................................................
53-68 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P454b_10 - DISTRIB_DL_TBF_VOLUME_10
Radio interface
....................................................................................................................................................................................................................................

P454b_10 - DISTRIB_DL_TBF_VOLUME_10
Descripton

Long Name DISTRIB_DL_TBF_VOLUME_10

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 TBF in GPRS and EGPRS mode, in RLC acknowledged and RLC unacknowledged 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 --
Feature Name /

P454b_2 - DISTRIB_DL_TBF_VOLUME_2
Descripton

Long Name DISTRIB_DL_TBF_VOLUME_2


Definition Second cell of the distribution on volume of DL TBF.
It contains:
1) number of DL TBFs whose LLC volume is in LLC volume band 2.
LLC volume band 2 is defined by :
PD_DL_TBF_VOLUME_THR_1<= LLC volume < PD_DL_TBF_VOLUME_THR_2
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 P43.

Sub Domain 1 Radio interface

Sub Domain 2 DL TBF LLC volume


Sub Domain 3 N/A

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-69
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P454b_2 - DISTRIB_DL_TBF_VOLUME_2
Radio interface
....................................................................................................................................................................................................................................

Measured Object DistCell

External Comment --
Feature Name /

P454b_3 - DISTRIB_DL_TBF_VOLUME_3
Descripton

Long Name DISTRIB_DL_TBF_VOLUME_3

Definition Third cell of the distribution on volume of DL TBF.


It contains:
1) number of DL TBFs whose LLC volume is in LLC volume band 3.
LLC volume band 3 is defined by :
PD_DL_TBF_VOLUME_THR_2<= LLC volume < PD_DL_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 P43.

Sub Domain 1 Radio interface


Sub Domain 2 DL TBF LLC volume
Sub Domain 3 N/A
Measured Object DistCell
External Comment --

Feature Name /

P454b_4 - DISTRIB_DL_TBF_VOLUME_4
Descripton

Long Name DISTRIB_DL_TBF_VOLUME_4

Definition Fourth cell of the distribution on volume of DL TBF.


It contains:
1) number of DL TBFs whose LLC volume is in LLC volume band 4.
LLC volume band 4 is defined by :
PD_DL_TBF_VOLUME_THR_3<= LLC volume < PD_DL_TBF_VOLUME_THR_4
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 P43.

....................................................................................................................................................................................................................................
53-70 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P454b_4 - DISTRIB_DL_TBF_VOLUME_4
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 1 Radio interface

Sub Domain 2 DL TBF LLC volume


Sub Domain 3 N/A

Measured Object DistCell


External Comment --

Feature Name /

P454b_5 - DISTRIB_DL_TBF_VOLUME_5
Descripton

Long Name DISTRIB_DL_TBF_VOLUME_5


Definition Fifth cell of the distribution on volume of DL TBF.
It contains:
1) number of DL TBFs whose LLC volume is in LLC volume band 5.
LLC volume band 5 is defined by :
PD_DL_TBF_VOLUME_THR_4<= LLC volume < PD_DL_TBF_VOLUME_THR_5
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 P43.
Sub Domain 1 Radio interface

Sub Domain 2 DL TBF LLC volume


Sub Domain 3 N/A
Measured Object DistCell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-71
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P454b_6 - DISTRIB_DL_TBF_VOLUME_6
Radio interface
....................................................................................................................................................................................................................................

P454b_6 - DISTRIB_DL_TBF_VOLUME_6
Descripton

Long Name DISTRIB_DL_TBF_VOLUME_6

Definition Sixth cell of the distribution on volume of DL TBF.


It contains:
1) number of DL TBFs whose LLC volume is in LLC volume band 6.
LLC volume band 6 is defined by :
PD_DL_TBF_VOLUME_THR_5<= LLC volume < PD_DL_TBF_VOLUME_THR_6

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

Sub Domain 1 Radio interface


Sub Domain 2 DL TBF LLC volume
Sub Domain 3 N/A
Measured Object DistCell
External Comment --

Feature Name /

P454b_7 - DISTRIB_DL_TBF_VOLUME_7
Descripton

Long Name DISTRIB_DL_TBF_VOLUME_7


Definition Seventh cell of the distribution on volume of DL TBF.
It contains:
1) number of DL TBFs whose LLC volume is in LLC volume band 7.
LLC volume band 7 is defined by :
PD_DL_TBF_VOLUME_THR_6<= LLC volume < PD_DL_TBF_VOLUME_THR_7
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 P43.

Sub Domain 1 Radio interface

Sub Domain 2 DL TBF LLC volume


Sub Domain 3 N/A

Measured Object DistCell

External Comment --

....................................................................................................................................................................................................................................
53-72 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P454b_7 - DISTRIB_DL_TBF_VOLUME_7
Radio interface
....................................................................................................................................................................................................................................

Feature Name /

P454b_8 - DISTRIB_DL_TBF_VOLUME_8
Descripton

Long Name DISTRIB_DL_TBF_VOLUME_8

Definition Eighth cell of the distribution on volume of DL TBF.


It contains:
1) number of DL TBFs whose LLC volume is in LLC volume band 8.
LLC volume band 1 is defined by :
PD_DL_TBF_VOLUME_THR_7<= LLC volume < PD_DL_TBF_VOLUME_THR_8

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

Sub Domain 1 Radio interface


Sub Domain 2 DL TBF LLC volume
Sub Domain 3 N/A
Measured Object DistCell
External Comment --

Feature Name /

P454b_9 - DISTRIB_DL_TBF_VOLUME_9
Descripton

Long Name DISTRIB_DL_TBF_VOLUME_9


Definition Ninth cell of the distribution on volume of DL TBF.
It contains:
1) number of DL TBFs whose LLC volume is in LLC volume band 9.
LLC volume band 9 is defined by :
PD_DL_TBF_VOLUME_THR_8<= LLC volume < PD_DL_TBF_VOLUME_THR_9

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

Sub Domain 1 Radio interface

Sub Domain 2 DL TBF LLC volume

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-73
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P454b_9 - DISTRIB_DL_TBF_VOLUME_9
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 N/A

Measured Object DistCell


External Comment --

Feature Name /

P455a_1 - DISTRIB_UL_PDCH_UNIT_ALLOC_1
Descripton

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 units is in PDCH units band 1.
PDCH units band 1 is defined by :
PD_UL_PDCH_UNIT_ALLOC_THR_0<= allocated PDCH units < PD_UL_PDCH_UNIT_ALLOC_THR_
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 PDCH allocation for UL TBF

Sub Domain 3 N/A

Measured Object DistCell


External Comment --
Feature Name /

....................................................................................................................................................................................................................................
53-74 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455a_10 - DISTRIB_UL_PDCH_UNIT_ALLOC_10
Radio interface
....................................................................................................................................................................................................................................

P455a_10 - DISTRIB_UL_PDCH_UNIT_ALLOC_10
Descripton

Long Name DISTRIB_UL_PDCH_UNIT_ALLOC_10

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 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 PDCH allocation for UL TBF
Sub Domain 3 N/A
Measured Object DistCell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-75
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455a_2 - DISTRIB_UL_PDCH_UNIT_ALLOC_2
Radio interface
....................................................................................................................................................................................................................................

P455a_2 - DISTRIB_UL_PDCH_UNIT_ALLOC_2
Descripton

Long Name DISTRIB_UL_PDCH_UNIT_ALLOC_2

Definition Second cell of the distribution on units of PDCH allocated to UL TBFs.


It contains :
1) number of UL TBFs whose number of PDCH allocated units is in PDCH units band 2.
PDCH units band 2 is defined by :
PD_UL_PDCH_UNIT_ALLOC_THR_1<= allocated PDCH units < PD_UL_PDCH_UNIT_ALLOC_THR_
2

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 PDCH allocation for UL TBF
Sub Domain 3 N/A
Measured Object DistCell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
53-76 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455a_3 - DISTRIB_UL_PDCH_UNIT_ALLOC_3
Radio interface
....................................................................................................................................................................................................................................

P455a_3 - DISTRIB_UL_PDCH_UNIT_ALLOC_3
Descripton

Long Name DISTRIB_UL_PDCH_UNIT_ALLOC_3

Definition Third cell of the distribution on units of PDCH allocated to UL TBFs.


It contains :
1) number of UL TBFs whose number of PDCH allocated units is in PDCH units band 3.
PDCH units band 3 is defined by :
PD_UL_PDCH_UNIT_ALLOC_THR_2<= allocated PDCH units < PD_UL_PDCH_UNIT_ALLOC_THR_
3

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 PDCH allocation for UL TBF
Sub Domain 3 N/A
Measured Object DistCell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-77
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455a_4 - DISTRIB_UL_PDCH_UNIT_ALLOC_4
Radio interface
....................................................................................................................................................................................................................................

P455a_4 - DISTRIB_UL_PDCH_UNIT_ALLOC_4
Descripton

Long Name DISTRIB_UL_PDCH_UNIT_ALLOC_4

Definition Fourth cell of the distribution on units of PDCH allocated to UL TBFs.


It contains :
1) number of UL TBFs whose number of PDCH allocated units is in PDCH units band 4.
PDCH units band 4 is defined by :
PD_UL_PDCH_UNIT_ALLOC_THR_3<= allocated PDCH units < PD_UL_PDCH_UNIT_ALLOC_THR_
4

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 PDCH allocation for UL TBF
Sub Domain 3 N/A
Measured Object DistCell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
53-78 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455a_5 - DISTRIB_UL_PDCH_UNIT_ALLOC_5
Radio interface
....................................................................................................................................................................................................................................

P455a_5 - DISTRIB_UL_PDCH_UNIT_ALLOC_5
Descripton

Long Name DISTRIB_UL_PDCH_UNIT_ALLOC_5

Definition Fifth cell of the distribution on units of PDCH allocated to UL TBFs.


It contains :
1) number of UL TBFs whose number of PDCH allocated units is in PDCH units band 5.
PDCH units band 5 is defined by :
PD_UL_PDCH_UNIT_ALLOC_THR_4<= allocated PDCH units < PD_UL_PDCH_UNIT_ALLOC_THR_
5

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 PDCH allocation for UL TBF
Sub Domain 3 N/A
Measured Object DistCell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-79
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455a_6 - DISTRIB_UL_PDCH_UNIT_ALLOC_6
Radio interface
....................................................................................................................................................................................................................................

P455a_6 - DISTRIB_UL_PDCH_UNIT_ALLOC_6
Descripton

Long Name DISTRIB_UL_PDCH_UNIT_ALLOC_6

Definition Sixth cell of the distribution on units of PDCH allocated to UL TBFs.


It contains :
1) number of UL TBFs whose number of PDCH allocated units is in PDCH units band 6.
PDCH units band 6 is defined by :
PD_UL_PDCH_UNIT_ALLOC_THR_5<= allocated PDCH units < PD_UL_PDCH_UNIT_ALLOC_THR_
6

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 PDCH allocation for UL TBF
Sub Domain 3 N/A
Measured Object DistCell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
53-80 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455a_7 - DISTRIB_UL_PDCH_UNIT_ALLOC_7
Radio interface
....................................................................................................................................................................................................................................

P455a_7 - DISTRIB_UL_PDCH_UNIT_ALLOC_7
Descripton

Long Name DISTRIB_UL_PDCH_UNIT_ALLOC_7

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 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 PDCH allocation for UL TBF
Sub Domain 3 N/A
Measured Object DistCell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-81
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455a_8 - DISTRIB_UL_PDCH_UNIT_ALLOC_8
Radio interface
....................................................................................................................................................................................................................................

P455a_8 - DISTRIB_UL_PDCH_UNIT_ALLOC_8
Descripton

Long Name DISTRIB_UL_PDCH_UNIT_ALLOC_8

Definition Eighth cell of the distribution on units of PDCH allocated to UL TBFs.


It contains :
1) number of UL TBFs whose number of PDCH allocated units is in PDCH units band 8.
PDCH units band 8 is defined by :
PD_UL_PDCH_UNIT_ALLOC_THR_7<= allocated PDCH units < PD_UL_PDCH_UNIT_ALLOC_THR_
8

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 PDCH allocation for UL TBF
Sub Domain 3 N/A
Measured Object DistCell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
53-82 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455a_9 - DISTRIB_UL_PDCH_UNIT_ALLOC_9
Radio interface
....................................................................................................................................................................................................................................

P455a_9 - DISTRIB_UL_PDCH_UNIT_ALLOC_9
Descripton

Long Name DISTRIB_UL_PDCH_UNIT_ALLOC_9

Definition Ninth cell of the distribution on units of PDCH allocated to UL TBFs.


It contains :
1) number of UL TBFs whose number of PDCH allocated units is in PDCH units band 9.
PDCH units band 9 is defined by :
PD_UL_PDCH_UNIT_ALLOC_THR_8<= allocated PDCH units < PD_UL_PDCH_UNIT_ALLOC_THR_
9

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 PDCH allocation for UL TBF
Sub Domain 3 N/A
Measured Object DistCell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-83
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455b_1 - DISTRIB_DL_PDCH_UNIT_ALLOC_1
Radio interface
....................................................................................................................................................................................................................................

P455b_1 - DISTRIB_DL_PDCH_UNIT_ALLOC_1
Descripton

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 PDCH allocation for DL TBF

Sub Domain 3 N/A


Measured Object DistCell
External Comment --

Feature Name /

....................................................................................................................................................................................................................................
53-84 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455b_10 - DISTRIB_DL_PDCH_UNIT_ALLOC_10
Radio interface
....................................................................................................................................................................................................................................

P455b_10 - DISTRIB_DL_PDCH_UNIT_ALLOC_10
Descripton

Long Name DISTRIB_DL_PDCH_UNIT_ALLOC_10

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 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 PDCH allocation for DL TBF

Sub Domain 3 N/A


Measured Object DistCell
External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-85
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455b_2 - DISTRIB_DL_PDCH_UNIT_ALLOC_2
Radio interface
....................................................................................................................................................................................................................................

P455b_2 - DISTRIB_DL_PDCH_UNIT_ALLOC_2
Descripton

Long Name DISTRIB_DL_PDCH_UNIT_ALLOC_2

Definition Second cell of the distribution on units of PDCH allocated to DL TBFs.


It contains :
1) number of DL TBFs whose number of PDCH allocated units is in PDCH units band 2.
PDCH units band 2 is defined by :
PD_DL_PDCH_UNIT_ALLOC_THR_1<= allocated PDCH units < PD_DL_PDCH_UNIT_ALLOC_THR_
2

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 PDCH allocation for DL TBF
Sub Domain 3 N/A
Measured Object DistCell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
53-86 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455b_3 - DISTRIB_DL_PDCH_UNIT_ALLOC_3
Radio interface
....................................................................................................................................................................................................................................

P455b_3 - DISTRIB_DL_PDCH_UNIT_ALLOC_3
Descripton

Long Name DISTRIB_DL_PDCH_UNIT_ALLOC_3

Definition Third cell of the distribution on units of PDCH allocated to DL TBFs.


It contains :
1) number of DL TBFs whose number of PDCH allocated units is in PDCH units band 3.
PDCH units band 3 is defined by :
PD_DL_PDCH_UNIT_ALLOC_THR_2<= allocated PDCH units < PD_DL_PDCH_UNIT_ALLOC_THR_
3

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 PDCH allocation for DL TBF
Sub Domain 3 N/A
Measured Object DistCell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-87
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455b_4 - DISTRIB_DL_PDCH_UNIT_ALLOC_4
Radio interface
....................................................................................................................................................................................................................................

P455b_4 - DISTRIB_DL_PDCH_UNIT_ALLOC_4
Descripton

Long Name DISTRIB_DL_PDCH_UNIT_ALLOC_4

Definition Fourth cell of the distribution on units of PDCH allocated to DL TBFs.


It contains :
1) number of DL TBFs whose number of PDCH allocated units is in PDCH units band 4.
PDCH units band 4 is defined by :
PD_DL_PDCH_UNIT_ALLOC_THR_3<= allocated PDCH units < PD_DL_PDCH_UNIT_ALLOC_THR_
4

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 PDCH allocation for DL TBF
Sub Domain 3 N/A
Measured Object DistCell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
53-88 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455b_5 - DISTRIB_DL_PDCH_UNIT_ALLOC_5
Radio interface
....................................................................................................................................................................................................................................

P455b_5 - DISTRIB_DL_PDCH_UNIT_ALLOC_5
Descripton

Long Name DISTRIB_DL_PDCH_UNIT_ALLOC_5

Definition Fifth cell of the distribution on units of PDCH allocated to DL TBFs.


It contains :
1) number of DL TBFs whose number of PDCH allocated units is in PDCH units band 5.
PDCH units band 5 is defined by :
PD_DL_PDCH_UNIT_ALLOC_THR_4<= allocated PDCH units < PD_DL_PDCH_UNIT_ALLOC_THR_
5

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 PDCH allocation for DL TBF
Sub Domain 3 N/A
Measured Object DistCell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-89
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455b_6 - DISTRIB_DL_PDCH_UNIT_ALLOC_6
Radio interface
....................................................................................................................................................................................................................................

P455b_6 - DISTRIB_DL_PDCH_UNIT_ALLOC_6
Descripton

Long Name DISTRIB_DL_PDCH_UNIT_ALLOC_6

Definition Sixth cell of the distribution on units of PDCH allocated to DL TBFs.


It contains :
1) number of DL TBFs whose number of PDCH allocated units is in PDCH units band 6.
PDCH units band 6 is defined by :
PD_DL_PDCH_UNIT_ALLOC_THR_5<= allocated PDCH units < PD_DL_PDCH_UNIT_ALLOC_THR_
6

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 PDCH allocation for DL TBF
Sub Domain 3 N/A
Measured Object DistCell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
53-90 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455b_7 - DISTRIB_DL_PDCH_UNIT_ALLOC_7
Radio interface
....................................................................................................................................................................................................................................

P455b_7 - DISTRIB_DL_PDCH_UNIT_ALLOC_7
Descripton

Long Name DISTRIB_DL_PDCH_UNIT_ALLOC_7

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 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 PDCH allocation for DL TBF
Sub Domain 3 N/A
Measured Object DistCell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-91
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455b_8 - DISTRIB_DL_PDCH_UNIT_ALLOC_8
Radio interface
....................................................................................................................................................................................................................................

P455b_8 - DISTRIB_DL_PDCH_UNIT_ALLOC_8
Descripton

Long Name DISTRIB_DL_PDCH_UNIT_ALLOC_8

Definition Eighth cell of the distribution on units of PDCH allocated to DL TBFs.


It contains :
1) number of DL TBFs whose number of PDCH allocated units is in PDCH units band 8.
PDCH units band 8 is defined by :
PD_DL_PDCH_UNIT_ALLOC_THR_7<= allocated PDCH units < PD_DL_PDCH_UNIT_ALLOC_THR_
8

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 PDCH allocation for DL TBF
Sub Domain 3 N/A
Measured Object DistCell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
53-92 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P455b_9 - DISTRIB_DL_PDCH_UNIT_ALLOC_9
Radio interface
....................................................................................................................................................................................................................................

P455b_9 - DISTRIB_DL_PDCH_UNIT_ALLOC_9
Descripton

Long Name DISTRIB_DL_PDCH_UNIT_ALLOC_9

Definition Ninth cell of the distribution on units of PDCH allocated to DL TBFs.


It contains :
1) number of DL TBFs whose number of PDCH allocated units is in PDCH units band 9.
PDCH units band 9 is defined by :
PD_DL_PDCH_UNIT_ALLOC_THR_8<= allocated PDCH units < PD_DL_PDCH_UNIT_ALLOC_THR_
9

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 PDCH allocation for DL TBF
Sub Domain 3 N/A
Measured Object DistCell
External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-93
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P461 - CUMULATED_ACT_EXT_UL_CONNECTION_TIME
Radio interface
....................................................................................................................................................................................................................................

P461 - CUMULATED_ACT_EXT_UL_CONNECTION_TIME
Descripton

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, 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).
Sub Domain 1 Radio interface
Sub Domain 2 UL TBF duration
Sub Domain 3 N/A
Measured Object Cell
External Comment --

Feature Name Extended UL TBF mode

....................................................................................................................................................................................................................................
53-94 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P495 - MAX_NB_USED_SPDCH_CELL
Radio interface
....................................................................................................................................................................................................................................

P495 - MAX_NB_USED_SPDCH_CELL
Descripton

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 slave 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 --
Feature Name /

P495bis - EST_MAX_USED_SPDCH_GPU_CAPACITY
Descripton

Long Name EST_MAX_USED_SPDCH_GPU_CAPACITY


Definition This counter gives an estimation of the maximum number of used SPDCH (i.e. PDCHs that carry at least
one UL or DL TBF) at GPU level (at a given CPU load which corresponds to overload). Its aim is to provide
an estimation of the GPU capacity.

Trigger condition This counter is computed at the end of the granularity period. Its value depends mainly on the following
parameters: P76a, sum on all cells of the GPU of P495, PMU_OVERLOAD_GP2 (in case of GP2 board) or
PMU_OVERLOAD_GP3 (in case of GP3 board).
Sub Domain 1 Radio interface

Sub Domain 2 PDCH

Sub Domain 3 N/A


Measured Object Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-95
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P495ter - MAX_NB_USED_SPDCH_GPU
Radio interface
....................................................................................................................................................................................................................................

P495ter - MAX_NB_USED_SPDCH_GPU
Descripton

Long Name MAX_NB_USED_SPDCH_GPU

Definition This counter gives the maximum number of used SPDCH (i.e. PDCH that carry at least one UL or DL TBF)
at GPU level during the whole granularity period.
Trigger condition Every time the cells mapped on the GPU send a BSCGP RADIO-RESOURCE-USAGE-INDICATION
message to the BSC, the sum of the used PDCHs at cell level (provided by the bitmap "SPDCHs_Radio_Usage_
List" in the message) is computed on all the cells mapped on the GPU. If the new value is higher than the
stored one, it becomes the new maximum value.

Sub Domain 1 Radio interface


Sub Domain 2 PDCH

Sub Domain 3 N/A


Measured Object Sub_BSS (BSC/FABRIC)
External Comment --

Feature Name /

P496 - MIN_NB_USED_SPDCH_CELL
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
53-96 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P52a - CUMULATED_ACTIVE_DL_CONNECTION-
Radio interface _TIME_GPRS_ACK
....................................................................................................................................................................................................................................

P52a - CUMULATED_ACTIVE_DL_CONNECTION_TIME_GPRS_ACK
Descripton

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 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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-97
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P52b - CUMULATED_ACTIVE_DL_CONNECTION-
Radio interface _TIME_GPRS_NACK
....................................................................................................................................................................................................................................

P52b - CUMULATED_ACTIVE_DL_CONNECTION-
_TIME_GPRS_NACK
Descripton

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 The counter measures the cumulated time duration of all active DL TBFs established in GPRS 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 GPRS mode and RLC
unacknowledged 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 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 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 --

Feature Name /

....................................................................................................................................................................................................................................
53-98 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P52c - CUMULATED_ACTIVE_DL_CONNECTION-
Radio interface _TIME_EGPRS_ACK
....................................................................................................................................................................................................................................

P52c - CUMULATED_ACTIVE_DL_CONNECTION-
_TIME_EGPRS_ACK
Descripton

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 The counter measures the cumulated time duration of all active DL TBFs established in EGPRS 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 EGPRS 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 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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-99
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P52d - CUMULATED_ACTIVE_DL_CONNECTION-
Radio interface _TIME_EGPRS_NACK
....................................................................................................................................................................................................................................

P52d - CUMULATED_ACTIVE_DL_CONNECTION-
_TIME_EGPRS_NACK
Descripton

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 The counter measures the cumulated time duration of all active DL TBFs 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 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 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
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 --
Feature Name /

....................................................................................................................................................................................................................................
53-100 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P531a_1 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_1
Radio interface
....................................................................................................................................................................................................................................

P531a_1 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_1
Descripton

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 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 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.
- MS context with no received UL LLC PDU are not 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 --
Feature Name /

P531a_10 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_10
Descripton

Long Name DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_10

Definition Tenth class of the distribution on number of EGPRS UL LLC throughput.


It contains :
1) number of EGPRS UL LLC throughput whose 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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-101
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P531a_10 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT-
Radio interface _CLASS_10
....................................................................................................................................................................................................................................

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 --
Feature Name /

P531a_11 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_11
Descripton

Long Name DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_11


Definition Eleventh class of the distribution on number of EGPRS UL LLC throughput.
It contains :
1) number of EGPRS UL LLC throughput whose throughput is in EGPRS LLC throughput class 11.
EGPRS LLC throughput class 11 is defined by :
EGPRS_LLC_throughput_THR_10<= LLC throughput < EGPRS_LLC_throughput_THR_11

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

Feature Name /

....................................................................................................................................................................................................................................
53-102 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P531a_2 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_2
Radio interface
....................................................................................................................................................................................................................................

P531a_2 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_2
Descripton

Long Name DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_2

Definition Second class of the distribution on number of EGPRS UL LLC throughput.


It contains :
1) number of EGPRS UL LLC throughput whose throughput is in EGPRS LLC throughput class 2.
EGPRS LLC throughput class 2 is defined by :
EGPRS_LLC_throughput_THR_1<= LLC throughput < EGPRS_LLC_throughput_THR_2

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 --
Feature Name /

P531a_3 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_3
Descripton

Long Name DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_3

Definition Third class of the distribution on number of EGPRS UL LLC throughput.


It contains :
1) number of EGPRS UL LLC throughput whose throughput is in EGPRS LLC throughput class 3.
EGPRS LLC throughput class 3 is defined by :
EGPRS_LLC_throughput_THR_2<= LLC throughput < EGPRS_LLC_throughput_THR_3

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-103
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P531a_3 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_3
Radio interface
....................................................................................................................................................................................................................................

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 --
Feature Name /

P531a_4 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_4
Descripton

Long Name DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_4


Definition Fourth class of the distribution on number of EGPRS UL LLC throughput.
It contains :
1) number of EGPRS UL LLC throughput whose throughput is in EGPRS LLC throughput class 4.
EGPRS LLC throughput class 4 is defined by :
EGPRS_LLC_throughput_THR_3<= LLC throughput < EGPRS_LLC_throughput_THR_4

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

Feature Name /

....................................................................................................................................................................................................................................
53-104 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P531a_5 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_5
Radio interface
....................................................................................................................................................................................................................................

P531a_5 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_5
Descripton

Long Name DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_5

Definition Fifth class of the distribution on number of EGPRS UL LLC throughput.


It contains :
1) number of EGPRS UL LLC throughput whose throughput is in EGPRS LLC throughput class 5.
EGPRS LLC throughput class 5 is defined by :
EGPRS_LLC_throughput_THR_4<= LLC throughput < EGPRS_LLC_throughput_THR_5

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 --
Feature Name /

P531a_6 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_6
Descripton

Long Name DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_6

Definition Sixth class of the distribution on number of EGPRS UL LLC throughput.


It contains :
1) number of EGPRS UL LLC throughput whose throughput is in EGPRS LLC throughput class 6.
EGPRS LLC throughput class 6 is defined by :
EGPRS_LLC_throughput_THR_5<= LLC throughput < EGPRS_LLC_throughput_THR_6

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-105
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P531a_6 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_6
Radio interface
....................................................................................................................................................................................................................................

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 --
Feature Name /

P531a_7 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_7
Descripton

Long Name DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_7


Definition Seventh class of the distribution on number of EGPRS UL LLC throughput.
It contains :
1) number of EGPRS UL LLC throughput whose throughput is in EGPRS LLC throughput class 7.
EGPRS LLC throughput class 7 is defined by :
EGPRS_LLC_throughput_THR_6<= LLC throughput < EGPRS_LLC_throughput_THR_7

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

Feature Name /

....................................................................................................................................................................................................................................
53-106 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P531a_8 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_8
Radio interface
....................................................................................................................................................................................................................................

P531a_8 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_8
Descripton

Long Name DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_8

Definition Eighth class of the distribution on number of EGPRS UL LLC throughput.


It contains :
1) number of EGPRS UL LLC throughput whose throughput is in EGPRS LLC throughput class 8.
EGPRS LLC throughput class 8 is defined by :
EGPRS_LLC_throughput_THR_7<= LLC throughput < EGPRS_LLC_throughput_THR_8

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 --
Feature Name /

P531a_9 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_9
Descripton

Long Name DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_9

Definition Ninth class of the distribution on number of EGPRS UL LLC throughput.


It contains :
1) number of EGPRS UL LLC throughput whose throughput is in EGPRS LLC throughput class 9.
EGPRS LLC throughput class 9 is defined by :
EGPRS_LLC_throughput_THR_8<= LLC throughput < EGPRS_LLC_throughput_THR_9

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-107
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P531a_9 - DISTRIB_UL_EGPRS_LLC_THROUGHPUT_CLASS_9
Radio interface
....................................................................................................................................................................................................................................

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 --
Feature Name /

P531b_1 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_1
Descripton

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.
- MS context with no sent DL LLC PDU are not 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 --

....................................................................................................................................................................................................................................
53-108 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P531b_1 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_1
Radio interface
....................................................................................................................................................................................................................................

Feature Name /

P531b_10 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_10
Descripton

Long Name DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_10

Definition Tenth 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 10.
EGPRS LLC throughput class 10 is defined by :
EGPRS_LLC_throughput_THR_9<= LLC throughput < EGPRS_LLC_throughput_THR_10

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 --
Feature Name /

P531b_11 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_11
Descripton

Long Name DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_11


Definition Eleventh 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 11.
EGPRS LLC throughput class 11 is defined by :
EGPRS_LLC_throughput_THR_10 <= LLC throughput < EGPRS_LLC_throughput_THR_11

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-109
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P531b_11 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT-
Radio interface _CLASS_11
....................................................................................................................................................................................................................................

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 --
Feature Name /

P531b_2 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_2
Descripton

Long Name DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_2


Definition Second 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 2.
EGPRS LLC throughput class 2 is defined by :
EGPRS_LLC_throughput_THR_1<= LLC throughput < EGPRS_LLC_throughput_THR_2

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

Feature Name /

....................................................................................................................................................................................................................................
53-110 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P531b_3 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_3
Radio interface
....................................................................................................................................................................................................................................

P531b_3 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_3
Descripton

Long Name DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_3

Definition Third 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 class3.
EGPRS LLC throughput class 3 is defined by :
EGPRS_LLC_throughput_THR_2<= LLC throughput < EGPRS_LLC_throughput_THR_3

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 --
Feature Name /

P531b_4 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_4
Descripton

Long Name DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_4

Definition Fourth 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 4.
EGPRS LLC throughput class 4 is defined by :
EGPRS_LLC_throughput_THR_3<= LLC throughput < EGPRS_LLC_throughput_THR_4

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-111
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P531b_4 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_4
Radio interface
....................................................................................................................................................................................................................................

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 --
Feature Name /

P531b_5 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_5
Descripton

Long Name DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_5


Definition Fifth 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 5.
EGPRS LLC throughput class 5 is defined by :
EGPRS_LLC_throughput_THR_4<= LLC throughput < EGPRS_LLC_throughput_THR_5

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

Feature Name /

....................................................................................................................................................................................................................................
53-112 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P531b_6 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_6
Radio interface
....................................................................................................................................................................................................................................

P531b_6 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_6
Descripton

Long Name DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_6

Definition Sixth 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 6.
EGPRS LLC throughput class 6 is defined by :
EGPRS_LLC_throughput_THR_5<= LLC throughput < EGPRS_LLC_throughput_THR_6

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 --
Feature Name /

P531b_7 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_7
Descripton

Long Name DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_7

Definition Seventh 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 7.
EGPRS LLC throughput class 7 is defined by :
EGPRS_LLC_throughput_THR_6<= LLC throughput < EGPRS_LLC_throughput_THR_7

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-113
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P531b_7 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_7
Radio interface
....................................................................................................................................................................................................................................

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 --
Feature Name /

P531b_8 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_8
Descripton

Long Name DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_8


Definition Eighth 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 8.
EGPRS LLC throughput class 8 is defined by :
EGPRS_LLC_throughput_THR_7<= LLC throughput < EGPRS_LLC_throughput_THR_8

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

Feature Name /

....................................................................................................................................................................................................................................
53-114 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P531b_9 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_9
Radio interface
....................................................................................................................................................................................................................................

P531b_9 - DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_9
Descripton

Long Name DISTRIB_DL_EGPRS_LLC_THROUGHPUT_CLASS_9

Definition Ninth 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 9.
EGPRS LLC throughput class 9 is defined by :
EGPRS_LLC_throughput_THR_8<= LLC throughput < EGPRS_LLC_throughput_THR_9

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 --
Feature Name /

P532a_1 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_1
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-115
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P532a_1 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_1
Radio interface
....................................................................................................................................................................................................................................

Trigger condition During MS context lifetime , the size of the UL LLC PDU received in the TBF established in GPRS 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.
- MS context with no received UL LLC PDU are not 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 --

Feature Name /

P532a_10 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_10
Descripton

Long Name DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_10


Definition Tenth class of the distribution on number of GPRS UL LLC throughput.
It contains :
1) number of GPRS UL LLC throughput whose throughput is in GPRS LLC throughput class 10.
GPRS LLC throughput class 10 is defined by :
GPRS_LLC_throughput_THR_9<= LLC throughput < GPRS_LLC_throughput_THR_10

Trigger condition During MS context lifetime , the size of the UL LLC PDU received in the TBF established in GPRS 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 --

....................................................................................................................................................................................................................................
53-116 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P532a_10 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_10
Radio interface
....................................................................................................................................................................................................................................

Feature Name /

P532a_2 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_2
Descripton

Long Name DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_2

Definition Second class of the distribution on number of GPRS UL LLC throughput.


It contains :
1) number of GPRS UL LLC throughput whose throughput is in GPRS LLC throughput class 2.
GPRS LLC throughput class 2 is defined by :
GPRS_LLC_throughput_THR_1<= LLC throughput < GPRS_LLC_throughput_THR_2

Trigger condition During MS context lifetime , the size of the UL LLC PDU received in the TBF established in GPRS 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 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 --
Feature Name /

P532a_3 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_3
Descripton

Long Name DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_3


Definition Third class of the distribution on number of GPRS UL LLC throughput.
It contains :
1) number of GPRS UL LLC throughput whose throughput is in GPRS LLC throughput class 3.
GPRS LLC throughput class 3 is defined by :
GPRS_LLC_throughput_THR_2<= LLC throughput < GPRS_LLC_throughput_THR_3

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-117
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P532a_3 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_3
Radio interface
....................................................................................................................................................................................................................................

Trigger condition During MS context lifetime , the size of the UL LLC PDU received in the TBF established in GPRS 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 --
Feature Name /

P532a_4 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_4
Descripton

Long Name DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_4


Definition Fourth class of the distribution on number of GPRS UL LLC throughput.
It contains :
1) number of GPRS UL LLC throughput whose throughput is in GPRS LLC throughput class 4.
GPRS LLC throughput class 4 is defined by :
GPRS_LLC_throughput_THR_3<= LLC throughput < GPRS_LLC_throughput_THR_4

Trigger condition During MS context lifetime , the size of the UL LLC PDU received in the TBF established in GPRS 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 --

Feature Name /

....................................................................................................................................................................................................................................
53-118 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P532a_5 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_5
Radio interface
....................................................................................................................................................................................................................................

P532a_5 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_5
Descripton

Long Name DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_5

Definition Fifth class of the distribution on number of GPRS UL LLC throughput.


It contains :
1) number of GPRS UL LLC throughput whose throughput is in GPRS LLC throughput class 5.
GPRS LLC throughput class 5 is defined by :
GPRS_LLC_throughput_THR_4<= LLC throughput < GPRS_LLC_throughput_THR_5

Trigger condition During MS context lifetime , the size of the UL LLC PDU received in the TBF established in GPRS 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 --
Feature Name /

P532a_6 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_6
Descripton

Long Name DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_6

Definition Sixth class of the distribution on number of GPRS UL LLC throughput.


It contains :
1) number of GPRS UL LLC throughput whose throughput is in GPRS LLC throughput class 6.
GPRS LLC throughput class 6 is defined by :
GPRS_LLC_throughput_THR_5<= LLC throughput < GPRS_LLC_throughput_THR_6

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-119
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P532a_6 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_6
Radio interface
....................................................................................................................................................................................................................................

Trigger condition During MS context lifetime , the size of the UL LLC PDU received in the TBF established in GPRS 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 --
Feature Name /

P532a_7 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_7
Descripton

Long Name DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_7


Definition Seventh class of the distribution on number of GPRS UL LLC throughput.
It contains :
1) number of GPRS UL LLC throughput whose throughput is in GPRS LLC throughput class 7.
GPRS LLC throughput class 7 is defined by :
GPRS_LLC_throughput_THR_6<= LLC throughput < GPRS_LLC_throughput_THR_7

Trigger condition During MS context lifetime , the size of the UL LLC PDU received in the TBF established in GPRS 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 --

Feature Name /

....................................................................................................................................................................................................................................
53-120 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P532a_8 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_8
Radio interface
....................................................................................................................................................................................................................................

P532a_8 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_8
Descripton

Long Name DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_8

Definition Eighth class of the distribution on number of GPRS UL LLC throughput.


It contains :
1) number of GPRS UL LLC throughput whose throughput is in GPRS LLC throughput class 8.
GPRS LLC throughput class 8 is defined by :
GPRS_LLC_throughput_THR_7<= LLC throughput < GPRS_LLC_throughput_THR_8

Trigger condition During MS context lifetime , the size of the UL LLC PDU received in the TBF established in GPRS 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 --
Feature Name /

P532a_9 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_9
Descripton

Long Name DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_9

Definition Ninth class of the distribution on number of GPRS UL LLC throughput.


It contains :
1) number of GPRS UL LLC throughput whose throughput is in GPRS LLC throughput class 9.
GPRS LLC throughput class 9 is defined by :
GPRS_LLC_throughput_THR_8<= LLC throughput < GPRS_LLC_throughput_THR_9

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-121
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P532a_9 - DISTRIB_UL_GPRS_LLC_THROUGHPUT_CLASS_9
Radio interface
....................................................................................................................................................................................................................................

Trigger condition During MS context lifetime , the size of the UL LLC PDU received in the TBF established in GPRS 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 --
Feature Name /

P532b_1 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_1
Descripton

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 During MS context lifetime , the DL LLC PDU size sent in the TBF established in GPRS 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.
- MS context with no sent DL LLC PDU are not 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 --

....................................................................................................................................................................................................................................
53-122 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P532b_1 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_1
Radio interface
....................................................................................................................................................................................................................................

Feature Name /

P532b_10 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_10
Descripton

Long Name DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_10

Definition Tenth 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 10.
GPRS LLC throughput class 10 is defined by :
GPRS_LLC_throughput_THR_9<= LLC throughput < GPRS_LLC_throughput_THR_10

Trigger condition During MS context lifetime , the DL LLC PDU size sent in the TBF established in GPRS 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 --
Feature Name /

P532b_2 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_2
Descripton

Long Name DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_2


Definition Second 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 2.
GPRS LLC throughput class 2 is defined by :
GPRS_LLC_throughput_THR_1<= LLC throughput < GPRS_LLC_throughput_THR_2

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-123
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P532b_2 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_2
Radio interface
....................................................................................................................................................................................................................................

Trigger condition During MS context lifetime , the DL LLC PDU size sent in the TBF established in GPRS 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 --
Feature Name /

P532b_3 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_3
Descripton

Long Name DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_3


Definition Third 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 3.
GPRS LLC throughput class 3 is defined by :
GPRS_LLC_throughput_THR_2<= LLC throughput < GPRS_LLC_throughput_THR_3

Trigger condition During MS context lifetime , the DL LLC PDU size sent in the TBF established in GPRS 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 --

Feature Name /

....................................................................................................................................................................................................................................
53-124 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P532b_4 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_4
Radio interface
....................................................................................................................................................................................................................................

P532b_4 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_4
Descripton

Long Name DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_4

Definition Fourth 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 4.
GPRS LLC throughput class 4 is defined by :
GPRS_LLC_throughput_THR_3<= LLC throughput < GPRS_LLC_throughput_THR_4

Trigger condition During MS context lifetime , the DL LLC PDU size sent in the TBF established in GPRS 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 --
Feature Name /

P532b_5 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_5
Descripton

Long Name DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_5

Definition Fifth 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 5.
GPRS LLC throughput class 5 is defined by :
GPRS_LLC_throughput_THR_4<= LLC throughput < GPRS_LLC_throughput_THR_5

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-125
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P532b_5 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_5
Radio interface
....................................................................................................................................................................................................................................

Trigger condition During MS context lifetime , the DL LLC PDU size sent in the TBF established in GPRS 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 --
Feature Name /

P532b_6 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_6
Descripton

Long Name DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_6


Definition Sixth 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 6.
GPRS LLC throughput class 6 is defined by :
GPRS_LLC_throughput_THR_5<= LLC throughput < GPRS_LLC_throughput_THR_6

Trigger condition During MS context lifetime , the DL LLC PDU size sent in the TBF established in GPRS 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 --

Feature Name /

....................................................................................................................................................................................................................................
53-126 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P532b_7 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_7
Radio interface
....................................................................................................................................................................................................................................

P532b_7 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_7
Descripton

Long Name DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_7

Definition Seventh 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 7.
GPRS LLC throughput class 7 is defined by :
GPRS_LLC_throughput_THR_6<= LLC throughput < GPRS_LLC_throughput_THR_7

Trigger condition During MS context lifetime , the DL LLC PDU size sent in the TBF established in GPRS 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 --
Feature Name /

P532b_8 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_8
Descripton

Long Name DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_8

Definition Eighth 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 8.
GPRS LLC throughput class 8 is defined by :
GPRS_LLC_throughput_THR_7<= LLC throughput < GPRS_LLC_throughput_THR_8

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-127
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P532b_8 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_8
Radio interface
....................................................................................................................................................................................................................................

Trigger condition During MS context lifetime , the DL LLC PDU size sent in the TBF established in GPRS 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 --
Feature Name /

P532b_9 - DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_9
Descripton

Long Name DISTRIB_DL_GPRS_LLC_THROUGHPUT_CLASS_9


Definition Ninth 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 9.
GPRS LLC throughput class 9 is defined by :
GPRS_LLC_throughput_THR_8<= LLC throughput < GPRS_LLC_throughput_THR_9

Trigger condition During MS context lifetime , the DL LLC PDU size sent in the TBF established in GPRS 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 --

Feature Name /

....................................................................................................................................................................................................................................
53-128 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P62d - NB_UL_TBF_EST_REQ_EGPRS_PIM
Radio interface
....................................................................................................................................................................................................................................

P62d - NB_UL_TBF_EST_REQ_EGPRS_PIM
Descripton

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 44.018 EGPRS PACKET CHANNEL REQUEST message on RACH, or
- An 44.060 EGPRS PACKET CHANNEL REQUEST message on PRACH, or
- An 44.060 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 UL TBF establishments

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P90g - NB_DL_TBF_EST_SUCC_EGPRS_PIM
Descripton

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 DL TBF establishments


Sub Domain 3 N/A
Measured Object Cell

External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 53-129
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Resource availability and usage P91g - NB_DL_TBF_EST_REQ_EGPRS_PIM
Radio interface
....................................................................................................................................................................................................................................

P91g - NB_DL_TBF_EST_REQ_EGPRS_PIM
Descripton

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 requests only take into account the first attempt, i.e. no
repetitions are counted.
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 DL TBF establishments

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
53-130 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
54 Traffic load
54

Ater interface

P103 - NB_ERROR_UL_GCH_FRAME
Descripton

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 Sub_BSS (BSC/FABRIC)
External Comment --
Feature Name /

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P41 - NB_KBYTES_SENT_TO_BSC
Ater interface
....................................................................................................................................................................................................................................

P41 - NB_KBYTES_SENT_TO_BSC
Descripton

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 --
Feature Name /

P42 - NB_KBYTES_RECEIVED_FROM_BSC
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
54-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P180a - NB_SGSN_SELECTION_NSF
Gb interface
....................................................................................................................................................................................................................................

Gb interface

P180a - NB_SGSN_SELECTION_NSF
Descripton

Long Name NB_SGSN_SELECTION_NSF

Definition Number of time a SGSN is selected by the Node Selection Function.


Trigger condition Each time a SGSN is selected by the Node Selection Function and whatever the cause of the selection, this
counter is incremented.

Sub Domain 1 Gb interface


Sub Domain 2 Gbflex

Sub Domain 3 N/A


Measured Object SGSN_ID
External Comment --
Feature Name Gb-Flex

P180b - NB_SGSN_SELECTION_NSF_RIM
Descripton

Long Name NB_SGSN_SELECTION_NSF_RIM


Definition Number of time a SGSN is selected by the Node Selection Function for RIM_NACC.
Trigger condition Each time a SGSN is selected by the Node Selection Function and the selection is for RIM_NACC, this
counter is incremented.

Sub Domain 1 Gb interface


Sub Domain 2 Gbflex

Sub Domain 3 N/A

Measured Object SGSN_ID


External Comment --
Feature Name Gb-Flex

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P23 - NB_UL_LLC_BYTES_DISC_CONG
Gb interface
....................................................................................................................................................................................................................................

P23 - NB_UL_LLC_BYTES_DISC_CONG
Descripton

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 Gb interface


Sub Domain 2 PVC

Sub Domain 3 N/A

Measured Object PVC


External Comment --

Feature Name /

P43 - NB_DL_LLC_BYTES
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
54-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P44 - NB_UL_LLC_BYTES
Gb interface
....................................................................................................................................................................................................................................

P44 - NB_UL_LLC_BYTES
Descripton

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 --
Feature Name /

P45 - NB_KBYTES_RECEIVED_FROM_SGSN
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P45a - NB_KBYTES_RECEIVED_FROM_SGSN_GBIP
Gb interface
....................................................................................................................................................................................................................................

P45a - NB_KBYTES_RECEIVED_FROM_SGSN_GBIP
Descripton

Long Name NB_KBYTES_RECEIVED_FROM_SGSN_GBIP

Definition Number of kilo bytes received from one IpEndPoint.


Trigger condition For each message received from one IpEndPoint, 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 --
Feature Name Gb over IP

P46 - NB_KBYTES_SENT_TO_SGSN
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
54-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P46a - NB_KBYTES_SENT_TO_SGSN_GBIP
Gb interface
....................................................................................................................................................................................................................................

P46a - NB_KBYTES_SENT_TO_SGSN_GBIP
Descripton

Long Name NB_KBYTES_SENT_TO_SGSN_GBIP

Definition Number of kilo bytes sent to one IpEndPoint.


Trigger condition For each message sent to one IpEndPoint, 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 --
Feature Name Gb over IP

P600 - NB_REDIRECT_ATTEMPT
Descripton

Long Name NB_REDIRECT_ATTEMPT


Definition Number of attach request with redirect attempt flag set sent by the MFS.
Trigger condition Whenever a BSSGP UL-UNITDATA message with the parameter "Redirect Attempt Flag" set is sent on Gb
interface to a SGSN, this counter is incremented.

Sub Domain 1 Gb interface


Sub Domain 2 MOCN
Sub Domain 3 N/A
Measured Object SGSN_ID

External Comment --

Feature Name BSS sharing (MOCN 3GPP Release 10)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P601 - NB_REDIRECT_COMMAND
Gb interface
....................................................................................................................................................................................................................................

P601 - NB_REDIRECT_COMMAND
Descripton

Long Name NB_REDIRECT_COMMAND

Definition Number of redirection command received by the MFS.


Trigger condition Whenever the MFS receives a BSSGP DL-UNITDATA message with the redirection indication flag set
(whatever the reroute reject cause value), this counter is incremented.

Sub Domain 1 Gb interface


Sub Domain 2 MOCN

Sub Domain 3 N/A


Measured Object SGSN_ID

External Comment --
Feature Name BSS sharing (MOCN 3GPP Release 10)

P602 - NB_REDIRECT_COMMAND_CS_PS_COORD
Descripton

Long Name NB_REDIRECT_COMMAND_CS_PS_COORD


Definition Number of redirection command received by the MFS with CS/PS coordination cause.
Trigger condition Whenever the MFS receives a BSSGP DL-UNITDATA message with the redirection indication flag set and
the "reroute reject cause" set to "CS/PS domain registration coordination required", this counter is
incremented.

Sub Domain 1 Gb interface


Sub Domain 2 MOCN
Sub Domain 3 N/A

Measured Object SGSN_ID


External Comment --

Feature Name BSS sharing (MOCN 3GPP Release 10)

....................................................................................................................................................................................................................................
54-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P603 - NB_REDIRECT_COMPLETE
Gb interface
....................................................................................................................................................................................................................................

P603 - NB_REDIRECT_COMPLETE
Descripton

Long Name NB_REDIRECT_COMPLETE

Definition Number of redirection complete received by the MFS.


Trigger condition Whenever the MFS receives a BSSGP DL-UNITDATA message with the redirection completed flag set
(whatever the outcome value), this counter is incremented.

Sub Domain 1 Gb interface


Sub Domain 2 MOCN

Sub Domain 3 N/A


Measured Object SGSN_ID

External Comment --
Feature Name BSS sharing (MOCN 3GPP Release 10)

P604 - NB_REDIRECT_COMPLETE_MS_NOT_ACCEPTED
Descripton

Long Name NB_REDIRECT_COMPLETE_MS_NOT_ACCEPTED


Definition Number of redirection complete received by the MFS with cause MS not accepted.
Trigger condition Whenever the MFS receives a BSSGP DL-UNITDATA message with the redirection completed flag set and
the "outcome" set to "MS is not accepted", this counter is incremented.

Sub Domain 1 Gb interface


Sub Domain 2 MOCN
Sub Domain 3 N/A
Measured Object SGSN_ID

External Comment --

Feature Name BSS sharing (MOCN 3GPP Release 10)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P605 - NB_REDIRECT_COMPLETE_MS_ALREADY_REG
Gb interface
....................................................................................................................................................................................................................................

P605 - NB_REDIRECT_COMPLETE_MS_ALREADY_REG
Descripton

Long Name NB_REDIRECT_COMPLETE_MS_ALREADY_REG

Definition Number of redirection complete received by the MFS with cause MS already registered.
Trigger condition Whenever the MFS receives a BSSGP DL-UNITDATA message with the redirection completed flag set and
the "outcome" set to "MS is already registered", this counter is incremented.

Sub Domain 1 Gb interface


Sub Domain 2 MOCN

Sub Domain 3 N/A


Measured Object SGSN_ID

External Comment --
Feature Name BSS sharing (MOCN 3GPP Release 10)

P68 - NB_DL_LLC_COUNT_IM
Descripton

Long Name NB_DL_LLC_COUNT_IM


Definition Number of DL LLC-PDU received from the SGSN at BSSGP level per cell coming from Instant Message
Service such as QQ.
Trigger condition Whenever the MFS receives a DL UNITDATA from the SGSN to transmit to the cell with its Service Class
Indicator (SCI) corresponding to Instant Message Service (x11 in hexadecimal), the counter is incremented
by 1.

Sub Domain 1 Gb interface


Sub Domain 2 BVC (Cell)
Sub Domain 3 N/A
Measured Object Cell

External Comment --

Feature Name /

....................................................................................................................................................................................................................................
54-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P69 - NB_DL_LLC_BYTES_IM
Gb interface
....................................................................................................................................................................................................................................

P69 - NB_DL_LLC_BYTES_IM
Descripton

Long Name NB_DL_LLC_BYTES_IM

Definition Number of DL LLC-PDU bytes received from the SGSN at BSSGP level per cell coming from Instant
Message Service such as QQ.
Trigger condition Whenever the MFS receives a DL UNITDATA from the SGSN to transmit to the cell with its Service Class
Indicator (SCI) corresponding to Instant Message Service (x11 in hexadecimal), 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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P541a - NB_MFS_SENT_IPGCHU_GBR_IP_PACKETS
IP interface
....................................................................................................................................................................................................................................

IP interface

P541a - NB_MFS_SENT_IPGCHU_GBR_IP_PACKETS
Descripton

Long Name NB_MFS_SENT_IPGCHU_GBR_IP_PACKETS

Definition This counter counts the number of IPGCHU segments sent to a BTS by MFS on the GBR flow during the
GP.
Trigger condition Each time a IPGCHU segments is sent to a BTS by MFS in a GBR flow, the counter is incremented.
Note:
Retransmitted IPGCHU IP segments are not taken into account.
Sub Domain 1 IP interface
Sub Domain 2 GCH IP

Sub Domain 3 N/A


Measured Object BTS

External Comment --
Feature Name IP transport in the BSS

P541b - NB_MFS_RESENT_IPGCHU_GBR_IP_PACKETS
Descripton

Long Name NB_MFS_RESENT_IPGCHU_GBR_IP_PACKETS


Definition This counter counts the number of IPGCHU segments resent to a BTS by MFS on the GBR flow during the
GP.

Trigger condition Each time a IPGCHU segments is resent to a BTS by MFS in a GBR flow, the counter is incremented.
Note:
Only Retransmitted IPGCHU segments are taken into account.

Sub Domain 1 IP interface

Sub Domain 2 GCH IP


Sub Domain 3 N/A
Measured Object BTS

External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
54-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P541d - NB_MFS_SENT_IPGCHU_GBR_IP_BYTES
IP interface
....................................................................................................................................................................................................................................

P541d - NB_MFS_SENT_IPGCHU_GBR_IP_BYTES
Descripton

Long Name NB_MFS_SENT_IPGCHU_GBR_IP_BYTES

Definition This counter counts the number of bytes of IPGCHU segments sent to a BTS by the MFS on the GBR flow
during the GP.
Trigger condition Each time a IPGCHU segments is sent in a GBR flow, the counter is incremented by the amount of bytes of
IPGCHU segments.
Note:
- IPGCHU headers are taken into account
- Retransmitted segments are not taken into account.

Sub Domain 1 IP interface

Sub Domain 2 GCH IP


Sub Domain 3 N/A

Measured Object BTS


External Comment --

Feature Name IP transport in the BSS

P542a - NB_MFS_SENT_IPGCHU_BE_IP_PACKETS
Descripton

Long Name NB_MFS_SENT_IPGCHU_BE_IP_PACKETS


Definition This counter counts the number of IPGCHU segments sent to a BTS by MFS on the BE flow during the GP.
Trigger condition Each time a IPGCHU segment is sent to a BTS by MFS in a BE flow, the counter is incremented.
Note:
Retransmitted IPGCHU segments are not taken into account.

Sub Domain 1 IP interface


Sub Domain 2 GCH IP

Sub Domain 3 N/A


Measured Object BTS

External Comment --
Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-13
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P542b - NB_MFS_RESENT_IPGCHU_BE_IP_PACKETS
IP interface
....................................................................................................................................................................................................................................

P542b - NB_MFS_RESENT_IPGCHU_BE_IP_PACKETS
Descripton

Long Name NB_MFS_RESENT_IPGCHU_BE_IP_PACKETS

Definition This counter counts the number of IPGCHU segments resent to a BTS by MFS on the BE flow during the
GP.
Trigger condition Each time a IPGCHU segment is resent to a BTS by MFS in a BE flow, the counter is incremented.
Note:
Only Retransmitted IPGCHU segments are taken into account.

Sub Domain 1 IP interface


Sub Domain 2 GCH IP

Sub Domain 3 N/A


Measured Object BTS

External Comment --
Feature Name IP transport in the BSS

P542d - NB_MFS_SENT_IPGCHU_BE_IP_BYTES
Descripton

Long Name NB_MFS_SENT_IPGCHU_BE_IP_BYTES


Definition This counter counts the number of bytes of IPGCHU segments sent to a BTS by the MFS on the BE flow
during the GP.
Trigger condition Each time a IPGCHU segment is sent in a BE flow, the counter is incremented by the amount of bytes of
IPGCHU IP packets.
Note:
- IPGCHU headers are taken into account
-Retransmitted IPGCHU segments are not taken into account.
Sub Domain 1 IP interface

Sub Domain 2 GCH IP

Sub Domain 3 N/A


Measured Object BTS

External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
54-14 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P543a - NB_MFS_SENT_IPGCHC_IP_PACKETS
IP interface
....................................................................................................................................................................................................................................

P543a - NB_MFS_SENT_IPGCHC_IP_PACKETS
Descripton

Long Name NB_MFS_SENT_IPGCHC_IP_PACKETS

Definition This counter counts the number of IPGCHC control messages sent to a BTS by the MFS on the control flow
during the GP.
Trigger condition Each time a IPGCHU control message is sent in a control flow, the counter is incremented.

Sub Domain 1 IP interface


Sub Domain 2 GCH IP

Sub Domain 3 N/A


Measured Object BTS

External Comment --
Feature Name IP transport in the BSS

P543d - NB_MFS_SENT_IPGCHC_IP_BYTES
Descripton

Long Name NB_MFS_SENT_IPGCHC_IP_BYTES


Definition This counter counts the number of bytes of IPGCHC control messages sent to a BTS by MFS on the control
flow during the GP.
Trigger condition Each time a IPGCHC control message is sent to a BTS by the MFS in a control flow, the counter is
incremented by the amount of bytes of the messages.

Sub Domain 1 IP interface


Sub Domain 2 GCH IP
Sub Domain 3 N/A

Measured Object BTS


External Comment --

Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-15
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P549a - TIME_PS_DL_BE_CONGESTION
IP interface
....................................................................................................................................................................................................................................

P549a - TIME_PS_DL_BE_CONGESTION
Descripton

Long Name TIME_PS_DL_BE_CONGESTION

Definition Time during which the Abis bandwidth in DL is in congestion.


Trigger condition Each time a delay measurement is received in the MFS, the MFS cumulates the time the Abis bandwidth in
DL is in congestion.
The Abis bandwidth in DL is in congestion when measured delay => IPGCHU_DELAY_HIGH_THRES_
DL.
The time is provided in seconds with one significant value after the comma (i.e. ROUND(10x) / 10).

Sub Domain 1 IP interface


Sub Domain 2 GCH IP

Sub Domain 3 N/A


Measured Object Abis_BTS_Group

External Comment --
Feature Name IP transport in the BSS

....................................................................................................................................................................................................................................
54-16 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P10 - NB_DL_LLC_BYTES_DISC_CONG
Radio interface
....................................................................................................................................................................................................................................

Radio interface

P10 - NB_DL_LLC_BYTES_DISC_CONG
Descripton

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.
3) Whenever the MFS receives a DL LLC PDU that needs to be discarded due to 1st or 2nd level of GPU
buffer congestion, the counter is incremented by the number of bytes of the LLC PDU to discard.
4) When the number of DL PDU in the queue is higher than PDU_REORDER_INHIBIT_THRES_GP(U)
(BTP parameter) during a TBF re-establishment following an abnormal TBF release, the remaining DL PDU
are discarded and 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 --
Feature Name /

P104 - NB_LLC_PDU_GPU
Descripton

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 Sub_BSS (BSC/FABRIC)

External Comment --

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-17
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P104 - NB_LLC_PDU_GPU
Radio interface
....................................................................................................................................................................................................................................

Feature Name /

P201 - TIME_PTU_CPU_TDM_LOAD
Descripton

Long Name TIME_PTU_CPU_TDM_LOAD

Definition This counter cumulates the time during which at least one of the processors supporting the function PTU is
in CPU load state.
Trigger condition During the granularity period, the cumulated time during which at least one of the processors supporting the
function PTU is loaded is computed.
The processor is hardware dependent: a DSP (non GP boosted case) or a core (GP boosted case).
The time is provided in seconds with one significant value after the comma (i.e. ROUND(10x) / 10).
Note :
A DSP (non GP boosted case) or a core (GP boosted case) 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 Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name Enhanced Transmission Resource Management

P201bis - TIME_SCP_CPU_LOAD
Descripton

Long Name TIME_SCP_CPU_LOAD


Definition This counter cumulates the time during which at least a BTS module (SCP) is in CPU load state.

Trigger condition During the granularity period, the cumulated time during which at least a BTS module (SCP) is loaded is
computed.
The time is provided in seconds with one significant value after the comma (i.e. ROUND(10x) / 10).
Note :
A SCP is said loaded when its CPU load is >= IP_BTS_LOAD_THR_1 and < IP_BTS_LOAD_THR_2.

Sub Domain 1 Radio interface


Sub Domain 2 GPU load

Sub Domain 3 N/A

Measured Object BTS

....................................................................................................................................................................................................................................
54-18 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P201bis - TIME_SCP_CPU_LOAD
Radio interface
....................................................................................................................................................................................................................................

External Comment --

Feature Name Enhanced Transmission Resource Management

P202 - TIME_PTU_CPU_TDM_OVERLOAD
Descripton

Long Name TIME_PTU_CPU_TDM_OVERLOAD

Definition This counter cumulates the time during which at least one of the processors supporting the function PTU is
in CPU overload state.
Trigger condition During the granularity period, the cumulated time during which at least one of the processors supporting the
function PTU is overloaded is computed.
The processor is hardware dependent: a DSP (non GP boosted case) or a core (GP boosted case).
The time is provided in seconds with one significant value after the comma (i.e. ROUND(10x) / 10).
Note :
A DSP (non GP boosted case) or a core (GP boosted case) 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 Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name Enhanced Transmission Resource Management

P202bis - TIME_SCP_CPU_OVERLOAD
Descripton

Long Name TIME_SCP_CPU_OVERLOAD

Definition This counter cumulates the time during which at least a BTS module (SCP) is in CPU overload state.

Trigger condition During the granularity period, the cumulated time during which at least a BTS module (SCP) is overloaded
is computed.
The time is provided in seconds with one significant value after the comma (i.e. ROUND(10x) / 10).
Note :
A SCP is said overloaded when its CPU load is >= IP_BTS_LOAD_THR_2.
Sub Domain 1 Radio interface

Sub Domain 2 GPU load


Sub Domain 3 N/A

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-19
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P202bis - TIME_SCP_CPU_OVERLOAD
Radio interface
....................................................................................................................................................................................................................................

Measured Object BTS

External Comment --
Feature Name Enhanced Transmission Resource Management

P20a - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS1
Descripton

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 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 --
Feature Name /

P20b - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS2
Descripton

Long Name NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS2

Definition In acknowledged mode, number of DL RLC blocks (except RLC blocks containing LLC Dummy UI
Commands only) on PDTCH encoded in CS-2 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-2 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, 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
not taken into account.

Sub Domain 1 Radio interface

....................................................................................................................................................................................................................................
54-20 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P20b - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS2
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 2 DL RLC data flow

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P20c - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS3
Descripton

Long Name NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS3


Definition In acknowledged mode, number of DL RLC blocks (except RLC blocks containing LLC Dummy UI
Commands only) on PDTCH encoded in CS-3 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-3 is retransmitted to the MS. The retransmissions of DL RLC DATA blocks in PENDING
status within the transmit window are not counted (these blocks may be re-transmitted at the end of a TBF 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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-21
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P20d - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS4
Radio interface
....................................................................................................................................................................................................................................

P20d - NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS4
Descripton

Long Name NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS4

Definition In acknowledged mode, number of DL RLC blocks (except RLC blocks containing LLC Dummy UI
Commands only) on PDTCH encoded in CS-4 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-4 is retransmitted to the MS. The retransmissions of DL RLC DATA blocks in PENDING
status within the transmit window are not counted (these blocks may be re-transmitted at the end of a TBF 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 --
Feature Name /

P20f - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS1
Descripton

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 Whenever a DL 04.60 RLC DATA BLOCK (in NACK state within the emission 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.

....................................................................................................................................................................................................................................
54-22 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P20f - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS1
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 1 Radio interface

Sub Domain 2 DL RLC data flow


Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P20g - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS2
Descripton

Long Name NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS2


Definition In acknowledged mode, number of DL RLC data blocks (except RLC blocks containing LLC Dummy UI
Commands only) on PDTCH encoded in MCS-2 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
MCS-2 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 --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-23
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P20h - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS3
Radio interface
....................................................................................................................................................................................................................................

P20h - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS3
Descripton

Long Name NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS3

Definition In acknowledged mode, number of DL RLC data blocks (except RLC blocks containing LLC Dummy UI
Commands only) on PDTCH encoded in MCS-3 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
MCS-3 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 --
Feature Name /

P20i - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS4
Descripton

Long Name NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS4


Definition In acknowledged mode, number of DL RLC data blocks (except RLC blocks containing LLC Dummy UI
Commands only) on PDTCH encoded in MCS-4 retransmitted due to unacknowledgement of the MS.

....................................................................................................................................................................................................................................
54-24 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P20i - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS4
Radio interface
....................................................................................................................................................................................................................................

Trigger condition Whenever a DL 04.60 RLC DATA BLOCK (in NACK state within the emission window) on PDTCH
encoded in
MCS-4 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 --
Feature Name /

P20j - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS5
Descripton

Long Name NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS5


Definition In acknowledged mode, number of DL RLC data blocks (except RLC blocks containing LLC Dummy UI
Commands only) on PDTCH encoded in MCS-5 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
MCS-5 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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-25
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P20j - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS5
Radio interface
....................................................................................................................................................................................................................................

External Comment --

Feature Name /

P20k - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS6
Descripton

Long Name NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS6

Definition In acknowledged mode, number of DL RLC data blocks (except RLC blocks containing LLC Dummy UI
Commands only) on PDTCH encoded in MCS-6 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
MCS-6 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 --
Feature Name /

....................................................................................................................................................................................................................................
54-26 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P20l - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS7
Radio interface
....................................................................................................................................................................................................................................

P20l - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS7
Descripton

Long Name NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS7

Definition In acknowledged mode, number of DL RLC data blocks (except RLC blocks containing LLC Dummy UI
Commands only) on PDTCH encoded in MCS-7 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
MCS-7 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 --
Feature Name /

P20m - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS8
Descripton

Long Name NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS8


Definition In acknowledged mode, number of DL RLC data blocks (except RLC blocks containing LLC Dummy UI
Commands only) on PDTCH encoded in MCS-8 retransmitted due to unacknowledgement of the MS.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-27
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P20m - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS8
Radio interface
....................................................................................................................................................................................................................................

Trigger condition Whenever a DL 04.60 RLC DATA BLOCK (in NACK state within the emission window) on PDTCH
encoded in
MCS-8 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 --
Feature Name /

P20n - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS9
Descripton

Long Name NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS9


Definition In acknowledged mode, number of DL RLC data blocks (except RLC blocks containing LLC Dummy UI
Commands only) on PDTCH encoded in MCS-9 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
MCS-9 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

....................................................................................................................................................................................................................................
54-28 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P20n - NB_DL_RLC_BLOCK_PDTCH_RETRANS_MCS9
Radio interface
....................................................................................................................................................................................................................................

External Comment --

Feature Name /

P21a - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS1
Descripton

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 --
Feature Name /

P21b - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS2
Descripton

Long Name NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS2


Definition In acknowledged mode, number of UL RLC blocks on PDTCH encoded in CS-2 retransmitted due to
unacknowledgement of the MFS.

Trigger condition Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encoded in CS-2 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 --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-29
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P21c - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS3
Radio interface
....................................................................................................................................................................................................................................

P21c - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS3
Descripton

Long Name NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS3

Definition In acknowledged mode, number of UL RLC blocks on PDTCH encoded in CS-3 retransmitted due to
unacknowledgement of the MFS.
Trigger condition Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encoded in CS-3 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 --
Feature Name /

P21d - NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS4
Descripton

Long Name NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS4


Definition In acknowledged mode, number of UL RLC blocks on PDTCH encoded in CS-4 retransmitted due to
unacknowledgement of the MFS.
Trigger condition Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encoded in CS-4 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 --

Feature Name /

....................................................................................................................................................................................................................................
54-30 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P21f - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS1
Radio interface
....................................................................................................................................................................................................................................

P21f - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS1
Descripton

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 --
Feature Name /

P21g - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS2
Descripton

Long Name NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS2


Definition In acknowledged mode, number of UL RLC data blocks received on PDTCH encoded in MCS-2
retransmitted due to unacknowledgement of the MFS.

Trigger condition Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-2 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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-31
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P21h - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS3
Radio interface
....................................................................................................................................................................................................................................

P21h - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS3
Descripton

Long Name NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS3

Definition In acknowledged mode, number of UL RLC data blocks received on PDTCH encoded in MCS-3
retransmitted due to unacknowledgement of the MFS.
Trigger condition Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-3 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 --
Feature Name /

P21i - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS4
Descripton

Long Name NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS4


Definition In acknowledged mode, number of UL RLC data blocks received on PDTCH encoded in MCS-4
retransmitted due to unacknowledgement of the MFS.

Trigger condition Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-4 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 --
Feature Name /

....................................................................................................................................................................................................................................
54-32 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P21j - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS5
Radio interface
....................................................................................................................................................................................................................................

P21j - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS5
Descripton

Long Name NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS5

Definition In acknowledged mode, number of UL RLC data blocks received on PDTCH encoded in MCS-5
retransmitted due to unacknowledgement of the MFS.
Trigger condition Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-5 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 --
Feature Name /

P21k - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS6
Descripton

Long Name NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS6


Definition In acknowledged mode, number of UL RLC data blocks received on PDTCH encoded in MCS-6
retransmitted due to unacknowledgement of the MFS.

Trigger condition Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-6 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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-33
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P21l - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS7
Radio interface
....................................................................................................................................................................................................................................

P21l - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS7
Descripton

Long Name NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS7

Definition In acknowledged mode, number of UL RLC data blocks received on PDTCH encoded in MCS-7
retransmitted due to unacknowledgement of the MFS.
Trigger condition Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-7 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 --
Feature Name /

P21m - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS8
Descripton

Long Name NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS8


Definition In acknowledged mode, number of UL RLC data blocks received on PDTCH encoded in MCS-8
retransmitted due to unacknowledgement of the MFS.

Trigger condition Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-8 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 --
Feature Name /

....................................................................................................................................................................................................................................
54-34 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P21n - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS9
Radio interface
....................................................................................................................................................................................................................................

P21n - NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS9
Descripton

Long Name NB_UL_RLC_BLOCK_PDTCH_RETRANS_MCS9

Definition In acknowledged mode, number of UL RLC data blocks received on PDTCH encoded in MCS-9
retransmitted due to unacknowledgement of the MFS.
Trigger condition Whenever a retransmitted UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-9 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 --
Feature Name /

P310a - NB_STALL_IND_MS_GPRS
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-35
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P310b - NB_STALL_IND_MS_EGPRS
Radio interface
....................................................................................................................................................................................................................................

P310b - NB_STALL_IND_MS_EGPRS
Descripton

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 Link control at RLC layer

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P310c - NB_STALL_STATE_GPRS_DL_TBF
Descripton

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 Link control at RLC layer


Sub Domain 3 N/A

Measured Object Cell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
54-36 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P310d - NB_STALL_STATE_EGPRS_DL_TBF
Radio interface
....................................................................................................................................................................................................................................

P310d - NB_STALL_STATE_EGPRS_DL_TBF
Descripton

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 Link control at RLC layer

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P335 - AV_DL_TX_EFF_GPRS
Descripton

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 Link control at RLC layer


Sub Domain 3 N/A

Measured Object Cell

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-37
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P336 - AV_UL_TX_EFF_GPRS
Radio interface
....................................................................................................................................................................................................................................

P336 - AV_UL_TX_EFF_GPRS
Descripton

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 Link control at RLC layer

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P350a - NB_DL_RADIO_BLOCK_PDTCH
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
54-38 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P350b - NB_UL_RADIO_BLOCK_PDTCH
Radio interface
....................................................................................................................................................................................................................................

P350b - NB_UL_RADIO_BLOCK_PDTCH
Descripton

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 --
Feature Name /

P351a - NB_DL_CS_ADAPT_INCREASE
Descripton

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 Link control at RLC layer


Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-39
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P351b - NB_DL_CS_ADAPT_DECREASE
Radio interface
....................................................................................................................................................................................................................................

P351b - NB_DL_CS_ADAPT_DECREASE
Descripton

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 The counter is incremented whenever the RLC layer triggers a change of coding 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 Link control at RLC layer

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P352a - NB_UL_CS_ADAPT_INCREASE
Descripton

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 The counter is incremented whenever the RLC layer triggers a change of coding 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 Link control at RLC layer


Sub Domain 3 N/A

Measured Object Cell

External Comment --

....................................................................................................................................................................................................................................
54-40 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P352a - NB_UL_CS_ADAPT_INCREASE
Radio interface
....................................................................................................................................................................................................................................

Feature Name /

P352b - NB_UL_CS_ADAPT_DECREASE
Descripton

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 The counter is incremented whenever the RLC layer triggers a change of coding 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 Link control at RLC layer

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P384 - Time_DSP_Cong
Descripton

Long Name Time_DSP_Cong

Definition DSP congestion duration (in seconds).

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-41
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P384 - Time_DSP_Cong
Radio interface
....................................................................................................................................................................................................................................

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 Sub_BSS (BSC/FABRIC)
External Comment --
Feature Name Enhanced Transmission Resource Management

P384bis - TIME_SCP_CONG
Descripton

Long Name TIME_SCP_CONG


Definition BTS module (SCP) congestion duration (in seconds).
Trigger condition The counter is started when a BTS module (SCP) enters the congestion state because one of the following
conditions is met:
i) the maximum number of TBFs that can be handled by a PTU is reached (MAX_TBF_PTU_XX_IP value)
,
ii) the percentage of RLC and/or IPGCH memory resources used within a SCP does not allow to serve new
TBF (on this SCP) (current RLC and/or IPGCH memory congestion state is different from
NO_CONGESTION).
The counter is stopped: when all the SCP of a BTS have left the congestion state.
Sub Domain 1 Radio interface

Sub Domain 2 GPU load


Sub Domain 3 N/A

Measured Object BTS


External Comment --

Feature Name Enhanced Transmission Resource Management

....................................................................................................................................................................................................................................
54-42 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P384ter - TIME_GPU_BUFFER_CONG
Radio interface
....................................................................................................................................................................................................................................

P384ter - TIME_GPU_BUFFER_CONG
Descripton

Long Name TIME_GPU_BUFFER_CONG

Definition GPU buffer congestion duration.


Trigger condition The counter cumulates the time when a GPU has stepped into the first level of buffer congestion.

Sub Domain 1 Radio interface


Sub Domain 2 GPU load

Sub Domain 3 N/A


Measured Object Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name MFS Defence and Investigation Facilities

P390a - NB_BSS_CS_PAGING_REQ_GPU
Descripton

Long Name NB_BSS_CS_PAGING_REQ_GPU


Definition Number of CS paging requests coming from the BSC received by the GPU.
Trigger condition Whenever a PAGING COORDINATION REQUEST message is received from the BSC the counter is
incremented by the number of valid CS Paging IEs contained within the message.
Sub Domain 1 Radio interface

Sub Domain 2 GPU load


Sub Domain 3 N/A
Measured Object Sub_BSS (BSC/FABRIC)
External Comment --

Feature Name Enhanced DTM and Paging Coordination

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-43
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P390b - NB_CS_PAGING_REQ_PACCH
Radio interface
....................................................................................................................................................................................................................................

P390b - NB_CS_PAGING_REQ_PACCH
Descripton

Long Name NB_CS_PAGING_REQ_PACCH

Definition Number of CS Paging messages sent on PACCH.


Trigger condition Whenever a CS Paging message is sent on (DL) PACCH the counter is incremented.

Sub Domain 1 Radio interface


Sub Domain 2 DL PACCH

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name Enhanced DTM and Paging Coordination

P391a - NB_PS_PAGING_REQ_GPU
Descripton

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 Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
54-44 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P391b - NB_CS_PAGING_REQ_GPU
Radio interface
....................................................................................................................................................................................................................................

P391b - NB_CS_PAGING_REQ_GPU
Descripton

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 Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name /

P391c - NB_CS_PAGING_WITH_GLOBAL_CN_ID_GPU
Descripton

Long Name NB_CS_PAGING_WITH_GLOBAL_CN_ID_GPU


Definition Number of CS paging requests with GLOBAL_CN_ID IE processed by the GPU.
Trigger condition Whenever a CS paging request with GLOBAL_CN_ID IE is received from the SGSN.
Note: P391b is also incremented.
Sub Domain 1 Radio interface
Sub Domain 2 GPU load

Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)


External Comment --
Feature Name A-Flex

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-45
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P392a - AV_NB_MS_CONTEXTS
Radio interface
....................................................................................................................................................................................................................................

P392a - AV_NB_MS_CONTEXTS
Descripton

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 Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name /

P392b - MAX_NB_MS_CONTEXTS
Descripton

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 Sub_BSS (BSC/FABRIC)


External Comment --
Feature Name /

....................................................................................................................................................................................................................................
54-46 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P399 - SIG_BLKS_PRACH_LOAD
Radio interface
....................................................................................................................................................................................................................................

P399 - SIG_BLKS_PRACH_LOAD
Descripton

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 --
Feature Name /

P400 - SIG_BLKS_PAGCH_LOAD
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-47
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P400 - SIG_BLKS_PAGCH_LOAD
Radio interface
....................................................................................................................................................................................................................................

Measured Object Cell

External Comment --
Feature Name /

P401 - SIG_BLKS_PACCH_UL_LOAD
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
54-48 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P402 - TIME_PMU_OVERLOAD
Radio interface
....................................................................................................................................................................................................................................

P402 - TIME_PMU_OVERLOAD
Descripton

Long Name TIME_PMU_OVERLOAD

Definition Cumulative time during which the GPU stays in the PPC CPU overload state due to PPC CPU power
limitations.
Trigger condition The counter:
- Starts when the GPU enters the PPC CPU overload state, i.e. when the PPC CPU power budget is strictly
higher than the threshold PMU_CPU_Overload.
- Stops when the GPU leaves the PPC CPU overload state, i.e. when the PPC CPU power budget is below or
equal to the threshold PMU_CPU_Overload.
Note: for GP boosted, this corresponds to the case when at least one of the cores supporting the PMU
function is in overload state.

Sub Domain 1 Radio interface

Sub Domain 2 GPU load


Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)


External Comment --

Feature Name /

P413 - NB_GPRS_SESSIONS
Descripton

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.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-49
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P413 - NB_GPRS_SESSIONS
Radio interface
....................................................................................................................................................................................................................................

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 --
Feature Name /

P421 - NB_DUMMY_RLC_DATA_BLOCKS
Descripton

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

....................................................................................................................................................................................................................................
54-50 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P421 - NB_DUMMY_RLC_DATA_BLOCKS
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P438a - SIG_BLKS_NC2_UL_PACCH_PTM_LOAD
Descripton

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

Feature Name /

P438b - SIG_BLKS_NC2_DL_PACCH_PTM_LOAD
Descripton

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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-51
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P438b - SIG_BLKS_NC2_DL_PACCH_PTM_LOAD
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 2 DL PACCH

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name /

P438c - SIG_BLKS_NC2_UL_PACCH_CCCH_LOAD
Descripton

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

Feature Name /

P438d - SIG_BLKS_NC2_PRACH_LOAD
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
54-52 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P439 - SIG_BLKS_UL_PACCH_CCCH_PRR_LOAD
Radio interface
....................................................................................................................................................................................................................................

P439 - SIG_BLKS_UL_PACCH_CCCH_PRR_LOAD
Descripton

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

Feature Name /

P43a - NB_DL_LLC_BYTES_GPRS_ACK
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-53
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P43b - NB_DL_LLC_BYTES_GPRS_NACK
Radio interface
....................................................................................................................................................................................................................................

P43b - NB_DL_LLC_BYTES_GPRS_NACK
Descripton

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 Whenever the RRM layer is informed that an 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 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 --
Feature Name /

P43c - NB_DL_LLC_BYTES_EGPRS_ACK
Descripton

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 Whenever the RRM layer is informed that an DL LLC PDU has been correctly 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 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 --
Feature Name /

....................................................................................................................................................................................................................................
54-54 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P43d - NB_DL_LLC_BYTES_EGPRS_NACK
Radio interface
....................................................................................................................................................................................................................................

P43d - NB_DL_LLC_BYTES_EGPRS_NACK
Descripton

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 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 --
Feature Name /

P44a - NB_UL_LLC_BYTES_GPRS_ACK
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-55
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P44b - NB_UL_LLC_BYTES_GPRS_NACK
Radio interface
....................................................................................................................................................................................................................................

P44b - NB_UL_LLC_BYTES_GPRS_NACK
Descripton

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 Whenever the RRM layer receives an UL LLC PDU from the RLC layer on an UL TBF established in
GPRS mode and RLC unacknowledged 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 --
Feature Name /

P44c - NB_UL_LLC_BYTES_EGPRS_ACK
Descripton

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 Whenever the RRM layer receives an UL LLC PDU from the RLC layer on an UL TBF established in
EGPRS 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 --
Feature Name /

....................................................................................................................................................................................................................................
54-56 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P44d - NB_UL_LLC_BYTES_EGPRS_NACK
Radio interface
....................................................................................................................................................................................................................................

P44d - NB_UL_LLC_BYTES_EGPRS_NACK
Descripton

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 Whenever the RRM layer receives an UL LLC PDU from the RLC layer on an UL TBF established in
EGPRS mode and RLC unacknowledged 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 --
Feature Name /

P450a - NB_R97_R98_MS_CONTEXT_GPU
Descripton

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 Sub_BSS (BSC/FABRIC)


External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-57
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P450b - NB_GPRS_R99_MS_CONTEXT_GPU
Radio interface
....................................................................................................................................................................................................................................

P450b - NB_GPRS_R99_MS_CONTEXT_GPU
Descripton

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 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 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 Sub_BSS (BSC/FABRIC)


External Comment --

Feature Name /

P450c - NB_EGPRS_R99_MS_CONTEXT_GPU
Descripton

Long Name NB_EGPRS_R99_MS_CONTEXT_GPU


Definition Number of MS contexts created for EGPRS capable Release 1999 onwards 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 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 Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
54-58 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P450d - NB_MS_CONTEXT_GPU
Radio interface
....................................................................................................................................................................................................................................

P450d - NB_MS_CONTEXT_GPU
Descripton

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 Sub_BSS (BSC/FABRIC)


External Comment --
Feature Name /

P450e - NB_GERAN_FEATURE_PACK1_MS_CONTEXT_GPU
Descripton

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 Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-59
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P450f - NB_E_UTRA_FDD_CAPABLE_MS_CONTEXT_GPU
Radio interface
....................................................................................................................................................................................................................................

P450f - NB_E_UTRA_FDD_CAPABLE_MS_CONTEXT_GPU
Descripton

Long Name NB_E_UTRA_FDD_CAPABLE_MS_CONTEXT_GPU

Definition Number of MS contexts created for the E-UTRA FDD capable MS.
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 E-UTRA FDD.

Sub Domain 1 Radio interface


Sub Domain 2 MS capability

Sub Domain 3 N/A


Measured Object Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name Inter-BSS/Inter-RAT NACC

P450g - NB_UTRA_FDD_CAPABLE_MS_CONTEXT_GPU
Descripton

Long Name NB_UTRA_FDD_CAPABLE_MS_CONTEXT_GPU


Definition Number of MS contexts created for the UTRA FDD capable MS.
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 UTRA FDD.

Sub Domain 1 Radio interface


Sub Domain 2 MS capability
Sub Domain 3 N/A
Measured Object Sub_BSS (BSC/FABRIC)

External Comment --

Feature Name /

....................................................................................................................................................................................................................................
54-60 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P450h - NB_UTRA_TDD_CAPABLE_MS_CONTEXT_GPU
Radio interface
....................................................................................................................................................................................................................................

P450h - NB_UTRA_TDD_CAPABLE_MS_CONTEXT_GPU
Descripton

Long Name NB_UTRA_TDD_CAPABLE_MS_CONTEXT_GPU

Definition Number of MS contexts created for the UTRA TDD capable MS.
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 UTRA TDD.

Sub Domain 1 Radio interface


Sub Domain 2 MS capability

Sub Domain 3 N/A


Measured Object Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name /

P450i - NB_E_UTRA_TDD_CAPABLE_MS_CONTEXT_GPU
Descripton

Long Name NB_E_UTRA_TDD_CAPABLE_MS_CONTEXT_GPU


Definition Number of MS contexts created for the E-UTRA TDD capable MS.
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 E-UTRA TDD.

Sub Domain 1 Radio interface


Sub Domain 2 MS capability
Sub Domain 3 N/A
Measured Object Sub_BSS (BSC/FABRIC)

External Comment --

Feature Name Inter-BSS/Inter-RAT NACC

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-61
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P457 - NB_PSI_MES
Radio interface
....................................................................................................................................................................................................................................

P457 - NB_PSI_MES
Descripton

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 --
Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)

P459 - NB_NEIGH_PSI_MES
Descripton

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 --
Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)

....................................................................................................................................................................................................................................
54-62 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P462 - NB_DUMMY_UL_BLOCKS
Radio interface
....................................................................................................................................................................................................................................

P462 - NB_DUMMY_UL_BLOCKS
Descripton

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 This counter is incremented at each reception of Packet Uplink Dummy Control block.
Sub Domain 1 Radio interface

Sub Domain 2 UL RLC data flow


Sub Domain 3 N/A

Measured Object Cell


External Comment --
Feature Name Extended UL TBF mode

P49 - NB_IMM_ASS_AGCH
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-63
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P51 - NB_USEFUL_PDDCB_SCHEDULED
Radio interface
....................................................................................................................................................................................................................................

P51 - NB_USEFUL_PDDCB_SCHEDULED
Descripton

Long Name NB_USEFUL_PDDCB_SCHEDULED

Definition Number of useful PDDCB scheduled.


Trigger condition Whenever a useful PDDCB is scheduled, this counter is increased. It corresponds to:
- USF signalling to MS,
- PR_MODE_B synchronisation.

Sub Domain 1 Radio interface


Sub Domain 2 DL PACCH

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name Removal of unnecessary PDDCB (PS DTX - RFD313920)

P52 - NB_USELESS_PDDCB_SCHEDULED
Descripton

Long Name NB_USELESS_PDDCB_SCHEDULED


Definition Number of useless PDDCB scheduled.
Trigger condition Whenever a useless PDDCB is scheduled, this counter is increased. It corresponds to PDDCB not counted in
P51 and it includes next UL block signalling to BTS.

Sub Domain 1 Radio interface


Sub Domain 2 DL PACCH
Sub Domain 3 N/A

Measured Object Cell


External Comment --
Feature Name Removal of unnecessary PDDCB (PS DTX - RFD313920)

....................................................................................................................................................................................................................................
54-64 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P530a_1 - NB_MS_MULTISLOT_CLASS_0_TO_10
Radio interface
....................................................................................................................................................................................................................................

P530a_1 - NB_MS_MULTISLOT_CLASS_0_TO_10
Descripton

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 Sub_BSS (BSC/FABRIC)
External Comment --
Feature Name /

P530a_2 - NB_MS_MULTISLOT_CLASS_11_TO_12
Descripton

Long Name NB_MS_MULTISLOT_CLASS_11_TO_12


Definition Number of MS contexts created for MS whose multislot class belongs to the set of multislot classes 11 to
12.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-65
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P530a_2 - NB_MS_MULTISLOT_CLASS_11_TO_12
Radio interface
....................................................................................................................................................................................................................................

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 11 to 12.
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 Sub_BSS (BSC/FABRIC)
External Comment --
Feature Name /

P530a_3 - NB_MS_MULTISLOT_CLASS_3X
Descripton

Long Name NB_MS_MULTISLOT_CLASS_3X


Definition Number of MS contexts created for MS whose multislot class belongs to the set of multislot classes of type
3X .
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 of type 3X.
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

....................................................................................................................................................................................................................................
54-66 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P530a_3 - NB_MS_MULTISLOT_CLASS_3X
Radio interface
....................................................................................................................................................................................................................................

Measured Object Sub_BSS (BSC/FABRIC)

External Comment --
Feature Name /

P530a_4 - NB_MS_MULTISLOT_CLASS_4X
Descripton

Long Name NB_MS_MULTISLOT_CLASS_4X

Definition Number of MS contexts created for MS whose multislot class belongs to the set of multislot classes of type
4X .
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 of type 4X.
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 Sub_BSS (BSC/FABRIC)
External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-67
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P530a_5 - NB_MS_MULTISLOT_CLASS_30_TO_34
Radio interface
....................................................................................................................................................................................................................................

P530a_5 - NB_MS_MULTISLOT_CLASS_30_TO_34
Descripton

Long Name NB_MS_MULTISLOT_CLASS_30_TO_34

Definition Number of MS contexts created for MS whose (PTM) high multislot class belongs to 30-34.
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 (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 Sub_BSS (BSC/FABRIC)
External Comment --
Feature Name /

P530b_5 - NB_MS_MULTISLOT_CLASS_31_TO_33
Descripton

Long Name NB_MS_MULTISLOT_CLASS_31_TO_33

Definition Number of MS contexts created for MS whose DTM high multislot class belongs to 31-33.

....................................................................................................................................................................................................................................
54-68 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P530b_5 - NB_MS_MULTISLOT_CLASS_31_TO_33
Radio interface
....................................................................................................................................................................................................................................

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 DTM high multislot class belongs to 31-33.
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 Sub_BSS (BSC/FABRIC)
External Comment --
Feature Name /

P53a - NB_PS_PAGING_REQ_PCH
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-69
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P53b - NB_CS_PAGING_REQ_PCH
Radio interface
....................................................................................................................................................................................................................................

P53b - NB_CS_PAGING_REQ_PCH
Descripton

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 --
Feature Name /

P53c - NB_IMM_ASS_PCH
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
54-70 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P53d - NB_CS_PAGING_WITH_GLOBAL_CN_ID_PCH
Radio interface
....................................................................................................................................................................................................................................

P53d - NB_CS_PAGING_WITH_GLOBAL_CN_ID_PCH
Descripton

Long Name NB_CS_PAGING_WITH_GLOBAL_CN_ID_PCH

Definition Number of (BSCGP) PAGING REQUEST for CS paging with GLOBAL_CN_ID IE 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 with GLOBAL_CN_ID IE is sent to the MS for CS paging
whatever may be the paging area (RA, LA, ...).
Note: P53b is also incremented.

Sub Domain 1 Radio interface


Sub Domain 2 PCH

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name A-Flex

P55a - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS1
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-71
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P55b - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS2
Radio interface
....................................................................................................................................................................................................................................

P55b - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS2
Descripton

Long Name NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS2

Definition Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in CS-2. 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-2 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 --
Feature Name /

P55c - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS3
Descripton

Long Name NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS3


Definition Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in CS-3. 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-3 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 --

Feature Name /

....................................................................................................................................................................................................................................
54-72 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P55d - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS4
Radio interface
....................................................................................................................................................................................................................................

P55d - NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS4
Descripton

Long Name NB_USEFUL_DL_RLC_BLOCK_PDTCH_CS4

Definition Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in CS-4. 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-4 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 --
Feature Name /

P55e - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS1
Descripton

Long Name NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS1


Definition Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH 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 --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-73
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P55f - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS2
Radio interface
....................................................................................................................................................................................................................................

P55f - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS2
Descripton

Long Name NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS2

Definition Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-2.
Trigger condition Whenever a DL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-2 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 --
Feature Name /

P55g - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS3
Descripton

Long Name NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS3


Definition Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-3.
Trigger condition Whenever a DL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-3 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 --

....................................................................................................................................................................................................................................
54-74 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P55g - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS3
Radio interface
....................................................................................................................................................................................................................................

Feature Name /

P55h - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS4
Descripton

Long Name NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS4

Definition Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-4
Trigger condition Whenever a DL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-4 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 --
Feature Name /

P55i - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS5
Descripton

Long Name NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS5


Definition Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-5.
Trigger condition Whenever a DL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-5 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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-75
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P55i - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS5
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P55j - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS6
Descripton

Long Name NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS6

Definition Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-6
Trigger condition Whenever a DL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-6 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 --
Feature Name /

P55k - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS7
Descripton

Long Name NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS7

Definition Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-7.

....................................................................................................................................................................................................................................
54-76 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P55k - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS7
Radio interface
....................................................................................................................................................................................................................................

Trigger condition Whenever a DL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-7 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 --

Feature Name /

P55l - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS8
Descripton

Long Name NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS8


Definition Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-8.
Trigger condition Whenever a DL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-8 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 --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-77
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P55m - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS9
Radio interface
....................................................................................................................................................................................................................................

P55m - NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS9
Descripton

Long Name NB_USEFUL_DL_RLC_BLOCK_PDTCH_MCS9

Definition Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in MCS-9.
Trigger condition Whenever a DL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-9 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 --
Feature Name /

P57a - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS1
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
54-78 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P57b - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS2
Radio interface
....................................................................................................................................................................................................................................

P57b - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS2
Descripton

Long Name NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS2

Definition Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in CS-2. The
retransmitted blocks are not counted.
Trigger condition Whenever an UL 04.60 RLC DATA BLOCK on PDTCH encoded in CS-2 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 --
Feature Name /

P57c - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS3
Descripton

Long Name NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS3


Definition Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in CS-3. The
retransmitted blocks are not counted.
Trigger condition Whenever an UL 04.60 RLC DATA BLOCK on PDTCH encoded in CS-3/4 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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-79
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P57d - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS4
Radio interface
....................................................................................................................................................................................................................................

P57d - NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS4
Descripton

Long Name NB_USEFUL_UL_RLC_BLOCK_PDTCH_CS4

Definition Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in CS-4. The
retransmitted blocks are not counted.
Trigger condition Whenever an UL 04.60 RLC DATA BLOCK on PDTCH encoded in CS-4 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 --
Feature Name /

P57e - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS1
Descripton

Long Name NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS1


Definition Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-1.
The retransmitted blocks are not counted.
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.
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 --
Feature Name /

....................................................................................................................................................................................................................................
54-80 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P57f - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS2
Radio interface
....................................................................................................................................................................................................................................

P57f - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS2
Descripton

Long Name NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS2

Definition Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-2.
The retransmitted blocks are not counted.

Trigger condition Whenever an UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-2 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 --
Feature Name /

P57g - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS3
Descripton

Long Name NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS3


Definition Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-3.
The retransmitted blocks are not counted.
Trigger condition Whenever an UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-3 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 --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-81
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P57h - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS4
Radio interface
....................................................................................................................................................................................................................................

P57h - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS4
Descripton

Long Name NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS4

Definition Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-4.
The retransmitted blocks are not counted.

Trigger condition Whenever an UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-4 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 --
Feature Name /

P57i - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS5
Descripton

Long Name NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS5


Definition Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-5.
The retransmitted blocks are not counted.
Trigger condition Whenever an UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-5 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 --

Feature Name Enhanced support of E-GPRS in uplink

....................................................................................................................................................................................................................................
54-82 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P57j - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS6
Radio interface
....................................................................................................................................................................................................................................

P57j - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS6
Descripton

Long Name NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS6

Definition Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-6.
The retransmitted blocks are not counted.

Trigger condition Whenever an UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-6 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 --
Feature Name Enhanced support of E-GPRS in uplink

P57k - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS7
Descripton

Long Name NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS7


Definition Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-7.
The retransmitted blocks are not counted.
Trigger condition Whenever an UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-7 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 --

Feature Name Enhanced support of E-GPRS in uplink

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-83
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P57l - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS8
Radio interface
....................................................................................................................................................................................................................................

P57l - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS8
Descripton

Long Name NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS8

Definition Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-8.
The retransmitted blocks are not counted.

Trigger condition Whenever an UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-8 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 --
Feature Name Enhanced support of E-GPRS in uplink

P57m - NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS9
Descripton

Long Name NB_USEFUL_UL_RLC_BLOCK_PDTCH_MCS9


Definition Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in MCS-9.
The retransmitted blocks are not counted.
Trigger condition Whenever an UL 04.60 RLC DATA BLOCK on PDTCH encoded in MCS-9 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 --

Feature Name Enhanced support of E-GPRS in uplink

....................................................................................................................................................................................................................................
54-84 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P59 - NB_DL_RLC_BLOCK_PACCH
Radio interface
....................................................................................................................................................................................................................................

P59 - NB_DL_RLC_BLOCK_PACCH
Descripton

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 --
Feature Name /

P60 - NB_UL_RLC_BLOCK_PACCH
Descripton

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.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-85
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P60 - NB_UL_RLC_BLOCK_PACCH
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 1 Radio interface

Sub Domain 2 UL PACCH


Sub Domain 3 N/A

Measured Object Cell


External Comment --

Feature Name /

P61 - SIG_BLKS_PPCH_LOAD
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
54-86 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P61a - NB_PACK_PS_PAGING_REQ_PPCH
Radio interface
....................................................................................................................................................................................................................................

P61a - NB_PACK_PS_PAGING_REQ_PPCH
Descripton

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 --
Feature Name /

P61b - NB_PACK_CS_PAGING_REQ_PPCH
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-87
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P72c - NB_DL_RLC_BYTES_PDTCH_LOST_CS
Radio interface
....................................................................................................................................................................................................................................

P72c - NB_DL_RLC_BYTES_PDTCH_LOST_CS
Descripton

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 --
Feature Name /

P72d - NB_DL_RLC_BYTES_PDTCH_LOST_MCS
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
54-88 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P73c - NB_UL_RLC_BYTES_PDTCH_LOST_CS
Radio interface
....................................................................................................................................................................................................................................

P73c - NB_UL_RLC_BYTES_PDTCH_LOST_CS
Descripton

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 --
Feature Name /

P73d - NB_UL_RLC_BYTES_PDTCH_LOST_MCS
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-89
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P74 - NB_DL_PDU_TRANSMITTED
Radio interface
....................................................................................................................................................................................................................................

P74 - NB_DL_PDU_TRANSMITTED
Descripton

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 --
Feature Name /

P75 - NB_UL_PDU_TRANSMITTED
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
54-90 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P76a - AV_PMU_CPU_POWER_BUDGET
Radio interface
....................................................................................................................................................................................................................................

P76a - AV_PMU_CPU_POWER_BUDGET
Descripton

Long Name AV_PMU_CPU_POWER_BUDGET

Definition Average PMU CPU power budget observed during the granularity period.
Trigger condition In the case of non GP boosted, the counter is the average value of all the samples of the PMU CPU power
budget over the granularity period.
In the case of GP boosted, the counter corresponds to the maximum of the average values computed per
PMU core.
Sub Domain 1 Radio interface

Sub Domain 2 GPU load


Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)


External Comment --
Feature Name /

P76b - AV_CORE_PMU_CPU_POWER_BUDGET
Descripton

Long Name AV_CORE_PMU_CPU_POWER_BUDGET


Definition Average of the average values of the CPU power budget computed per PMU core during the granularity
period.
Trigger condition The counter is the average of the average values computed per PMU core over the granularity period.
Note: this counter is only meaningful for GP boosted.
Sub Domain 1 Radio interface
Sub Domain 2 GPU load

Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)


External Comment --

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-91
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P77a - MAX_PMU_CPU_POWER_BUDGET
Radio interface
....................................................................................................................................................................................................................................

P77a - MAX_PMU_CPU_POWER_BUDGET
Descripton

Long Name MAX_PMU_CPU_POWER_BUDGET

Definition Maximum value of the PMU CPU power budget observed during the granularity period.
Trigger condition In the case of non GP boosted, the counter corresponds to the tidemark of the counter P76a.
In the case of GP boosted, the counter corresponds to the maximum of the maximum values computed per
PMU core.
Sub Domain 1 Radio interface

Sub Domain 2 GPU load


Sub Domain 3 N/A

Measured Object Sub_BSS (BSC/FABRIC)


External Comment --

Feature Name /

P86_0 - NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_0
Descripton

Long Name NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_0


Definition Number of EGPRS RLC/MAC blocks sent with a power reduction of 0 dB (relative to P0).
Trigger condition Whenever an EGPRS RLC/MAC block is sent with a power reduction of 0 dB relative to P0, then the
counter is increased.
Sub Domain 1 Radio interface

Sub Domain 2 DL RLC data flow


Sub Domain 3 N/A

Measured Object Cell

External Comment --
Feature Name Downlink Power Control for PS (RFD311492)

....................................................................................................................................................................................................................................
54-92 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P86_1 - NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_2
Radio interface
....................................................................................................................................................................................................................................

P86_1 - NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_2
Descripton

Long Name NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_2

Definition Number of EGPRS RLC/MAC blocks sent with a power reduction of 2 dB (relative to P0).
Trigger condition Whenever an EGPRS RLC/MAC block is sent with a power reduction of 2 dB relative to P0, then the
counter is increased.

Sub Domain 1 Radio interface


Sub Domain 2 DL RLC data flow

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name Downlink Power Control for PS (RFD311492)

P86_2 - NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_4
Descripton

Long Name NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_4


Definition Number of EGPRS RLC/MAC blocks sent with a power reduction of 4 dB (relative to P0).
Trigger condition Whenever an EGPRS RLC/MAC block is sent with a power reduction of 4 dB relative to P0, then the
counter is increased.

Sub Domain 1 Radio interface


Sub Domain 2 DL RLC data flow
Sub Domain 3 N/A
Measured Object Cell

External Comment --

Feature Name Downlink Power Control for PS (RFD311492)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-93
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P86_3 - NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_6
Radio interface
....................................................................................................................................................................................................................................

P86_3 - NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_6
Descripton

Long Name NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_6

Definition Number of EGPRS RLC/MAC blocks sent with a power reduction of 6 dB (relative to P0).
Trigger condition Whenever an EGPRS RLC/MAC block is sent with a power reduction of 6 dB relative to P0, then the
counter is increased.

Sub Domain 1 Radio interface


Sub Domain 2 DL RLC data flow

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name Downlink Power Control for PS (RFD311492)

P86_4 - NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_8
Descripton

Long Name NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_8


Definition Number of EGPRS RLC/MAC blocks sent with a power reduction of 8 dB (relative to P0).
Trigger condition Whenever an EGPRS RLC/MAC block is sent with a power reduction of 8 dB relative to P0, then the
counter is increased.

Sub Domain 1 Radio interface


Sub Domain 2 DL RLC data flow
Sub Domain 3 N/A
Measured Object Cell

External Comment --

Feature Name Downlink Power Control for PS (RFD311492)

....................................................................................................................................................................................................................................
54-94 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P86_5 - NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_10
Radio interface
....................................................................................................................................................................................................................................

P86_5 - NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_10
Descripton

Long Name NB_EGPRS_BLOCK_SENT_POW_RED_LEVEL_10

Definition Number of EGPRS RLC/MAC blocks sent with a power reduction of 10 dB (relative to P0).
Trigger condition Whenever an EGPRS RLC/MAC block is sent with a power reduction of 10 dB relative to P0, then the
counter is increased.

Sub Domain 1 Radio interface


Sub Domain 2 DL RLC data flow

Sub Domain 3 N/A


Measured Object Cell

External Comment --
Feature Name Downlink Power Control for PS (RFD311492)

P95 - NB_DL_LLC_BYTES_REROUTED
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-95
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P96 - NB_DL_LLC_BYTES_NOT_REROUTED
Radio interface
....................................................................................................................................................................................................................................

P96 - NB_DL_LLC_BYTES_NOT_REROUTED
Descripton

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 --
Feature Name /

P97 - NB_DL_LLC_BYTES_REROUTED_RECEIVED
Descripton

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 --
Feature Name /

....................................................................................................................................................................................................................................
54-96 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P99 - NB_LLC_BYTES_DISC_SUSPEND
Radio interface
....................................................................................................................................................................................................................................

P99 - NB_LLC_BYTES_DISC_SUSPEND
Descripton

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

Feature Name /

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 54-97
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P99 - NB_LLC_BYTES_DISC_SUSPEND

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
54-98 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Part XXVIII: MFS-LCS Counters

Overview
Purpose
All MFS-LCS.

Contents

Chapter 55, Quality of service 55-1


Chapter 56, Traffic load 56-1

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R XXVIII-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
MFS-LCS Counters Overview

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
XXVIII-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
55 Quality of service
55

Radio interface

P800 - NB_LOC_REQ
Descripton

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 --
Feature Name Location services (LCS)

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 55-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P801 - NB_ASSIST_DATA_REQ
Radio interface
....................................................................................................................................................................................................................................

P801 - NB_ASSIST_DATA_REQ
Descripton

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 --
Feature Name Location services (LCS)

P802 - NB_ASSIST_DATA_SUCC
Descripton

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 --
Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
55-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P803 - NB_LOC_TA_SUCC
Radio interface
....................................................................................................................................................................................................................................

P803 - NB_LOC_TA_SUCC
Descripton

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

Feature Name Location services (LCS)

P804 - NB_LOC_CONV_GPS_SUCC
Descripton

Long Name NB_LOC_CONV_GPS_SUCC


Definition Number of successful location response sent to the BSC using Conventional GPS 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 "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 --
Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 55-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P805 - NB_LOC_MA_AGPS_SUCC
Radio interface
....................................................................................................................................................................................................................................

P805 - NB_LOC_MA_AGPS_SUCC
Descripton

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

Feature Name Location services (LCS)

P806 - NB_LOC_MB_AGPS_SUCC
Descripton

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 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 "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 --
Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
55-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P807 - NB_LOC_TA_PCF_REQ
Radio interface
....................................................................................................................................................................................................................................

P807 - NB_LOC_TA_PCF_REQ
Descripton

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 --
Feature Name Location services (LCS)

P808 - NB_LOC_TA_PCF_SUCC
Descripton

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 --
Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 55-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P809 - NB_LOC_CONV_GPS_PCF_REQ
Radio interface
....................................................................................................................................................................................................................................

P809 - NB_LOC_CONV_GPS_PCF_REQ
Descripton

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 --
Feature Name Location services (LCS)

P810 - NB_LOC_MA_AGPS_PCF_REQ
Descripton

Long Name NB_LOC_MA_AGPS_PCF_REQ


Definition Number of location calculation attempts with MS Assisted A-GPS PCF.
Trigger condition Incremented each times a location estimate is performed in the SMLC using PCF "MS assisted GPS".
Sub Domain 1 Radio interface

Sub Domain 2 Positioning method


Sub Domain 3 N/A

Measured Object LcsCell

External Comment --
Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
55-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P811 - NB_LOC_MA_AGPS_PCF_SUCC
Radio interface
....................................................................................................................................................................................................................................

P811 - NB_LOC_MA_AGPS_PCF_SUCC
Descripton

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 --
Feature Name Location services (LCS)

P812 - NB_LOC_MB_AGPS_PCF_REQ
Descripton

Long Name NB_LOC_MB_AGPS_PCF_REQ


Definition Number of location calculation attempts with MS Based A-GPS PCF.
Trigger condition Incremented each times a location estimate is performed in the SMLC using PCF "MS-based A-GPS".
Sub Domain 1 Radio interface

Sub Domain 2 Positioning method


Sub Domain 3 N/A

Measured Object LcsCell

External Comment --
Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 55-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P813 - NB_LOC_MB_AGPS_PCF_SUCC
Radio interface
....................................................................................................................................................................................................................................

P813 - NB_LOC_MB_AGPS_PCF_SUCC
Descripton

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 --
Feature Name Location services (LCS)

P814 - NB_LCS_PROTOCOL_ERROR
Descripton

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 --
Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
55-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P815 - NB_LCS_INTERRUPTED_INTRA_BSC_HO
Radio interface
....................................................................................................................................................................................................................................

P815 - NB_LCS_INTERRUPTED_INTRA_BSC_HO
Descripton

Long Name NB_LCS_INTERRUPTED_INTRA_BSC_HO

Definition Number of failed LCS procedures (considering LCS requests for MS positioning 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 Location estimate / Assistance data for MS

Sub Domain 3 N/A


Measured Object LcsCell
External Comment --
Feature Name Location services (LCS)

P816 - NB_LCS_INTERRUPTED_INTER_BSC_HO
Descripton

Long Name NB_LCS_INTERRUPTED_INTER_BSC_HO


Definition Number of failed LCS procedures (considering LCS requests for MS positioning 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 Location estimate / Assistance data for MS

Sub Domain 3 N/A

Measured Object LcsCell


External Comment --
Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 55-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P817 - NB_LCS_FAILURE_RRLP
Radio interface
....................................................................................................................................................................................................................................

P817 - NB_LCS_FAILURE_RRLP
Descripton

Long Name NB_LCS_FAILURE_RRLP

Definition Number of failed LCS procedures (considering LCS requests for MS positioning 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 Location estimate / Assistance data for MS

Sub Domain 3 N/A

Measured Object LcsCell


External Comment --

Feature Name Location services (LCS)

P818 - NB_LCS_FAILURE_TIMER_EXPIRY
Descripton

Long Name NB_LCS_FAILURE_TIMER_EXPIRY


Definition Number of failed LCS procedures (considering LCS requests for MS positioning 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 Location estimate / Assistance data for MS


Sub Domain 3 N/A

Measured Object LcsCell

External Comment --
Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
55-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P819 - NB_LCS_FAILURE_INTERNAL
Radio interface
....................................................................................................................................................................................................................................

P819 - NB_LCS_FAILURE_INTERNAL
Descripton

Long Name NB_LCS_FAILURE_INTERNAL

Definition Number of failed LCS procedures (considering LCS requests for MS positioning 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 Location estimate / Assistance data for MS

Sub Domain 3 N/A


Measured Object LcsCell

External Comment --
Feature Name Location services (LCS)

P820 - NB_UNKNOWN_LCS_REQ
Descripton

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 Location estimate / Assistance data for MS

Sub Domain 3 N/A


Measured Object LcsCell

External Comment --
Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 55-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Quality of service P821 - NB_LOC_CONV_GPS_PCF_SUCC
Radio interface
....................................................................................................................................................................................................................................

P821 - NB_LOC_CONV_GPS_PCF_SUCC
Descripton

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 --
Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
55-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
56 Traffic load
56

Radio interface

P822 - AV_TA_LAT
Descripton

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 Positioning statistics


Sub Domain 3 TA positioning

Measured Object LcsCell


External Comment --

Feature Name Location services (LCS)

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 56-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P823 - AV_TA_LONG
Radio interface
....................................................................................................................................................................................................................................

P823 - AV_TA_LONG
Descripton

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. Whenever "CI+TA" 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 Positioning statistics


Sub Domain 3 TA positioning

Measured Object LcsCell


External Comment --
Feature Name Location services (LCS)

P824 - AV_CONV_GPS_LAT
Descripton

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 --
Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
56-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P825 - AV_CONV_GPS_LONG
Radio interface
....................................................................................................................................................................................................................................

P825 - AV_CONV_GPS_LONG
Descripton

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 Positioning statistics


Sub Domain 3 Conventional GPS

Measured Object LcsCell


External Comment --
Feature Name Location services (LCS)

P826 - AV_MA_AGPS_LAT
Descripton

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 obtained sum by the
obtained number of measurements.

Sub Domain 1 Radio interface


Sub Domain 2 Positioning statistics

Sub Domain 3 MS assisted A-GPS

Measured Object LcsCell


External Comment --
Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 56-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P827 - AV_MA_AGPS_LONG
Radio interface
....................................................................................................................................................................................................................................

P827 - AV_MA_AGPS_LONG
Descripton

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 A-GPS PCF. Whenever MS Assisted A-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 Positioning statistics


Sub Domain 3 MS assisted A-GPS

Measured Object LcsCell


External Comment --
Feature Name Location services (LCS)

P828 - AV_MB_AGPS_LAT
Descripton

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 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 MS based A-GPS

Measured Object LcsCell


External Comment --
Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
56-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P829 - AV_MB_AGPS_LONG
Radio interface
....................................................................................................................................................................................................................................

P829 - AV_MB_AGPS_LONG
Descripton

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 PCF. Whenever MS Based A-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 Positioning statistics


Sub Domain 3 MS based A-GPS

Measured Object LcsCell


External Comment --
Feature Name Location services (LCS)

P830 - ST_DEV_TA_LAT
Descripton

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.
Whenever "CI+TA" 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

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 56-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P830 - ST_DEV_TA_LAT
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 2 Positioning statistics

Sub Domain 3 TA positioning


Measured Object LcsCell

External Comment --
Feature Name Location services (LCS)

P831 - ST_DEV_TA_LONG
Descripton

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 Positioning statistics


Sub Domain 3 TA positioning

Measured Object LcsCell

External Comment --
Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
56-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P832 - ST_DEV_CONV_GPS_LAT
Radio interface
....................................................................................................................................................................................................................................

P832 - ST_DEV_CONV_GPS_LAT
Descripton

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 Positioning statistics


Sub Domain 3 Conventional GPS

Measured Object LcsCell


External Comment --
Feature Name Location services (LCS)

P833 - ST_DEV_CONV_GPS_LONG
Descripton

Long Name ST_DEV_CONV_GPS_LONG


Definition Standard deviation of the longitude of the mobile stations obtained with Conventional GPS PCF

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 56-7
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P833 - ST_DEV_CONV_GPS_LONG
Radio interface
....................................................................................................................................................................................................................................

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 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 Positioning statistics
Sub Domain 3 Conventional GPS

Measured Object LcsCell


External Comment --

Feature Name Location services (LCS)

P834 - ST_DEV_MA_AGPS_LAT
Descripton

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 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 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 Positioning statistics

....................................................................................................................................................................................................................................
56-8 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P834 - ST_DEV_MA_AGPS_LAT
Radio interface
....................................................................................................................................................................................................................................

Sub Domain 3 MS assisted A-GPS

Measured Object LcsCell


External Comment --

Feature Name Location services (LCS)

P835 - ST_DEV_MA_AGPS_LONG
Descripton

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 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 Positioning statistics


Sub Domain 3 MS assisted A-GPS

Measured Object LcsCell


External Comment --

Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 56-9
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P836 - ST_DEV_MB_AGPS_LAT
Radio interface
....................................................................................................................................................................................................................................

P836 - ST_DEV_MB_AGPS_LAT
Descripton

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 PCF.
Whenever MS Based A-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.
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 Positioning statistics
Sub Domain 3 MS based A-GPS
Measured Object LcsCell
External Comment --
Feature Name Location services (LCS)

P837 - ST_DEV_MB_AGPS_LONG
Descripton

Long Name ST_DEV_MB_AGPS_LONG


Definition Standard deviation of the longitude of the mobile stations obtained with MS Based A-GPS PCF

....................................................................................................................................................................................................................................
56-10 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P837 - ST_DEV_MB_AGPS_LONG
Radio interface
....................................................................................................................................................................................................................................

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 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 Positioning statistics
Sub Domain 3 MS based A-GPS

Measured Object LcsCell


External Comment --

Feature Name Location services (LCS)

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R 56-11
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Traffic load P837 - ST_DEV_MB_AGPS_LONG

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
56-12 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Appendix A: Reference

Reissue history
Purpose
The reissue history of this document is described in the following paragraphs.

Issue 12
The reissue history for Issue 12 is shown in the following table.

Table A-1 Issue 12, July 2014, What’s new

Feature/enhancement Description Location


Documentation changes
Update BSC Counters and Standard issue Part I: “BSC-TYPE 1 - Traffic
MFS Counters This document was generated measurements”
from the BSC Counters Part XXVII: “MFS-GPRS
database edition 02.07 and Counters”
from the MFS Counters
database edition 02.05.

Issue 11
The reissue history for Issue 11 is shown in the following table.

Table A-2 Issue 11, June 2014, What’s new

Feature/enhancement Description Location


Documentation changes

...................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R A-1
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Reference Reissue history

....................................................................................................................................................................................................................................
Table A-2 Issue 11, June 2014, What’s new (continued)

Feature/enhancement Description Location


Update BSC Counters and Standard issue Part I: “BSC-TYPE 1 - Traffic
MFS Counters This document was generated measurements”
from the BSC Counters Part XXVII: “MFS-GPRS
database edition 02.06 and Counters”
from the MFS Counters
database edition 02.03.

Issue 10
The reissue history for Issue 10 is shown in the following table.

Table A-3 Issue 10, February 2014, What’s new

Feature/enhancement Description Location


Documentation changes
Update BSC Counters and Standard issue Part I: “BSC-TYPE 1 - Traffic
MFS Counters This document was generated measurements”
from the BSC Counters Part XXVII: “MFS-GPRS
database edition 02.05 and Counters”
from the MFS Counters
database edition 02.03.

Issue 9
The reissue history for Issue 9 is shown in the following table.

Table A-4 Issue 9, January 2014, Reason for reissue

Location Change
Part I: “BSC-TYPE 1 - Traffic Standard issue
measurements” This document was generated from the BSC Counters
Part XXVII: “MFS-GPRS Counters” database edition 02.04 and from the MFS Counters
database edition 02.03.

....................................................................................................................................................................................................................................
A-2 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Reference Reissue history

....................................................................................................................................................................................................................................
Issue 8
The reissue history for Issue 8 is shown in the following table.

Table A-5 Issue 8, April 2013, Reason for reissue

Location Change
Part I: “BSC-TYPE 1 - Traffic Standard issue
measurements” This document was generated from the BSC Counters
Part XXVII: “MFS-GPRS Counters” database edition 08 and from the MFS Counters
database edition 05.

Issue 7
The reissue history for Issue 7 is shown in the following table.

Table A-6 Issue 7, March 2013, Reason for reissue

Location Change
Part I: “BSC-TYPE 1 - Traffic Standard issue
measurements” This document was generated from the BSC Counters
Part XXVII: “MFS-GPRS Counters” database edition 08 and from the MFS Counters
database edition 04.

Issue 6
The reissue history for Issue 6 is shown in the following table.

Table A-7 Issue 6, February 2013, Reason for reissue

Location Change
Part I: “BSC-TYPE 1 - Traffic Standard issue
measurements” This document was generated from the BSC Counters
Part XXVII: “MFS-GPRS Counters” database edition 08 and from the MFS Counters
database edition 04.

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R A-3
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Reference Reissue history

....................................................................................................................................................................................................................................
Issue 5
The reissue history for Issue 5 is shown in the following table.

Table A-8 Issue 5, September 2012, Reason for reissue

Location Change
Part I: “BSC-TYPE 1 - Traffic Standard issue
measurements” This document was generated from the BSC Counters
Part XXVII: “MFS-GPRS Counters” database edition 07 and from the MFS Counters
database edition 03.

Issue 4
The reissue history for Issue 4 is shown in the following table.

Table A-9 Issue 4, September 2012, Reason for reissue

Location Change
Part I: “BSC-TYPE 1 - Traffic Standard issue
measurements” This document was generated from the BSC Counters
Part XXVII: “MFS-GPRS Counters” database edition 06 and from the MFS Counters
database edition 03.

Issue 3
The reissue history for Issue 3 is shown in the following table.

Table A-10 Issue 3, June 2012, Reason for reissue

Location Change
Part I: “BSC-TYPE 1 - Traffic Standard issue
measurements” This document was generated from the BSC Counters
Part XXVII: “MFS-GPRS Counters” database edition 05 and from the MFS Counters
database edition 03.

....................................................................................................................................................................................................................................
A-4 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Reference Reissue history

....................................................................................................................................................................................................................................
Issue 2
The reissue history for Issue 2 is shown in the following table.

Table A-11 Issue 2, March 2012, Reason for reissue

Location Change
Part I: “BSC-TYPE 1 - Traffic Standard issue
measurements”
Part XXVII: “MFS-GPRS Counters”

Issue 1
The reissue history for Issue 1 is shown in the following table.

Table A-12 Issue 1, March 2012, Reason for reissue

Location Change
Part I: “BSC-TYPE 1 - Traffic Draft issue
measurements”
Part XXVII: “MFS-GPRS Counters”

Issue 01p03
The reissue history for Issue 01p03 is shown in the following table.

Table A-13 Issue 01p03, December 2011, Reason for reissue

Location Change
Part I: “BSC-TYPE 1 - Traffic Draft issue
measurements”
Part XXVII: “MFS-GPRS Counters”

Issue 01p02
The reissue history for Issue 01p02 is shown in the following table.

Table A-14 Issue 01p02, 2011, Reason for reissue

Location Change
Part I: “BSC-TYPE 1 - Traffic Draft issue
measurements”
Part XXVII: “MFS-GPRS Counters”

....................................................................................................................................................................................................................................
Alcatel-Lucent 9153 OMC-R A-5
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014
Reference Reissue history

....................................................................................................................................................................................................................................
Issue 01p01
The reissue history for Issue 01p01 is shown in the following table.

Table A-15 Issue 01p01, 2010, Reason for reissue

Location Change
Part I: “BSC-TYPE 1 - Traffic Draft issue
measurements”
Part XXVII: “MFS-GPRS Counters”

....................................................................................................................................................................................................................................
A-6 Alcatel-Lucent 9153 OMC-R
9YZ-03803-1635-TQZZA B12
Issue 13 September 2014

Das könnte Ihnen auch gefallen