Alcatel-Lucent GSM PM Counters Guide
Alcatel-Lucent GSM PM Counters Guide
PM Counters Dictionary
OMC Document
Reference Guide
Release B11
Status RELEASED
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1 BSC-TYPE 1 - Traffic measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1 All TYPE 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.2 Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.4 Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
1.5 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
2 BSC-TYPE 2 - Resource availability measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
2.1 All TYPE 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
2.2 Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
3 BSC-TYPE 3 - Resource usage on CCCH channel measurements . . . . . . . . . . . . . . . . . . . . . . . . . . 105
3.1 All TYPE 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
3.2 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
4 BSC-TYPE 4 - Resource usage on SDCCH channel measurements . . . . . . . . . . . . . . . . . . . . . . . . . 111
4.1 All TYPE 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
4.2 Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
4.3 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
5 BSC-TYPE 5 - Resource usage on TCH channel measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.1 All TYPE 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.2 Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.3 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
6 BSC-TYPE 6 - TCH handover measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
6.1 All TYPE 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
6.2 Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
6.3 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
7 BSC-TYPE 7 - LapD measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
7.1 All TYPE 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
7.2 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
7.3 Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
7.4 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
8 BSC-TYPE 8 - X25 measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
8.1 All TYPE 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
8.2 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
8.3 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
9 BSC-TYPE 9 - N7 measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
9.1 All TYPE 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
9.2 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
9.3 Resource Availability & Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
9.4 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
10 BSC-TYPE 18 - A interface measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
10.1 All TYPE 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
10.2 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
10.3 Traffic Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
11 BSC-TYPE 19 - SMS PP measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
11.1 All TYPE 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
11.2 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
12 BSC-TYPE 20 - Radio Measurement Statistics Improvement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
12.1 All TYPE 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Preface
Purpose The PM Counters include description of:
GSM Counters
GPRS Counters
LCS Counters.
In Edition 07
This document was generated from the BSC Counters database edition 10
and from the MFS Counters database edition e10.
In Edition 06
This document was generated from the BSC Counters database edition 10
and from the MFS Counters database edition e09.
In Edition 05
This document was generated from the BSC Counters database edition 09
and from the MFS Counters database edition e09.
In Edition 04
This document was generated from the BSC Counters database edition 09
and from the MFS Counters database edition e08.
In Edition 03
This document was generated from the BSC Counters database edition 09
and from the MFS Counters database edition e05.
In Edition 02
This document was generated from the BSC Counters database edition 08
and from the MFS Counters database edition e06.
In Edition 01
First official release of the document for B11.
This document was generated from the BSC Counters database edition 06
and from the MFS Counters database edition 05.
Audience This manual is designed for Operations & Maintenance Center-Radio (OMC-R)
users, O&M technicians and system designers.
1.2 Handover
1.2.1 All Handover
C710 - NB_TCH_OUT_HO_REQ_TRX (Section 1.2.2.1 )
1.2.2 TCH
1.2.2.1 C710 - NB_TCH_OUT_HO_REQ_TRX
Definition Nb of TCH outgoing handover requests, per TRX. Intracell, internal intercell
and external handovers are counted together. This counter takes into account
handovers from TCH in traffic or in signaling mode. It does not take into account
DTM Assignments.
MC710 = C710
Trigger condition 1) Intracell HO: Whenever the BSC process responsible for the handover
procedure starts an intra cell TCH handover procedure.
2) Internal intercell HO: Whenever the BSC process responsible for the
handover procedure selects a target cell (among a list of target cells) for internal
inter cell TCH handover.
3) External HO: Whenever a 48.008 HANDOVER REQUIRED message is sent
on A interface to the MSC. If more than one 48.008 HANDOVER REQUIRED is
sent in the frame of the same Handover procedure, the counter is incremented
only once.
48.008 HANDOVER REQUIRED is sent in following situations:
1) An external handover alarm has been raised, with corresponding list of
candidate cells.
2) The list of candidate cells for the current alarm has been updated.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
Definition Number of SDCCH drops on SDCCH established phase due to radio link failure
(radio link timeout or Lapdm timer expiry).
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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.
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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).
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.
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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.
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.
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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).
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Definition Number of TCH (in HR or FR usage) drops due to remote transcoder failures
(per TRX).
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
1.3.4 Handover
1.3.4.1 C03 - NB_OUT_SDCCH_HO_SUCC
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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.
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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.
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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.
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 ACK 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 on the old channel between the
sending of the 48.058 CHANNEL ACTIVATION and the reception of the 48.058
CHANNEL ACTIVATION ACK 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 interface 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.
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Definition Nb of outgoing TCH handover -preparation failures due to congestion, per TRX.
Intracell, internal intercell and external handovers are counted together. This
counter takes into account handovers from TCH in traffic or in signaling mode. It
does not take into account DTM Assignments.
MC711 = C711
Trigger condition 1) Intracell HO: Whenever an intra-cell TCH handover cannot be performed,
because there is no free TCH channel to allocate the handover to.
2) Internal inter-cell HO: Whenever a internal inter-cell TCH handover cannot be
performed, because there is no free TCH channel to allocate the handover to.
3) External HO: Whenever a 48.008 HANDOVER REQUIRED REJECT with
cause "no radio resource available" is received from the MSC by the serving
BSC for an outgoing external TCH HO.
Note : the counter will be incremented for external TCH HO if and only if the
parameter RESP_REQ is set to 1.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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.
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Definition Number of incoming internal and external TCH (in HR or FR usage) handover
successes per TRX;
since there are no reliable means at the target BSC to distinguish external
directed retry from external handover, the external directed retries are counted
by this counter.
MC717b = C717b
Trigger condition 1) Internal inter-cell or external TCH handover: whenever a 44.018 HANDOVER
COMPLETE message is received on Abis interface from the target cell for a
TCH channel.
2) Intra-cell handover: whenever an 44.018 ASSIGNMENT COMPLETE
message is received on Abis interface on the target channel.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
1.3.5 Speech
1.3.5.1 C170 - 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 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Sub Domain 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
Trigger condition –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
Definition case: Location Update request (except the "follow on" procedure)
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
Trigger condition –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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.
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
Trigger condition Whenever the timer supervising the Immediate Assignment Procedure (T3101)
expires during the establishment of an SDCCH sub-channel.
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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 2 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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.
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Trigger condition –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Definition Number of times the traffic_load is "high", i.e. when a certain number
(N_TRAFFIC_LOAD) of traffic averages (AV_LOAD) verify each: AV_LOAD
> HIGH_THRESHOLD. The traffic_load is evaluated per cell at each
A_TRAFFIC_LOAD period.
This counter permits to tune the following parameters: A_TRAFFIC_LOAD,
N_TRAFFIC_LOAD and HIGH_THRESHOLD.
This counter relates to the number of free TCH timeslots.
Trigger condition At each A_TRAFFIC_LOAD period, whenever the BSC decision process detects
a "high" traffic_load.
Sub Domain 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
Definition Number of times the traffic_load is "low", i.e. when a certain number
(N_TRAFFIC_LOAD) of traffic averages (AV_LOAD) verify each: AV_LOAD
< LOW_THRESHOLD. The traffic_load is evaluated per cell at each
A_TRAFFIC_LOAD period.
This counter permits to tune the following parameters: A_TRAFFIC_LOAD,
N_TRAFFIC_LOAD and LOW_THRESHOLD.
This counter relates to the number of free TCH timeslots.
Trigger condition At each A_TRAFFIC_LOAD period, whenever the BSC decision process detects
a "low" traffic_load.
Remark : the number of "indefinite" traffic load can be deduced from the
counters NB_LOW_TRAFFIC_LOAD and NB_HIGH_TRAFFIC_LOAD over the
Accumulation Period.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for data call.
Sub Domain 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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, 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 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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.
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
Sub Domain 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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.
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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.
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
Feature Name –
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
Sub Domain 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
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 3 –
Type Definition Set of counters related to the traffic evaluation per telecom procedures
External Comment –
2.2.2 Channel
2.2.2.1 C141 - AV_NB_TCH_QUEUED
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.
Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment –
Feature Name –
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.
Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment –
Feature Name –
Definition Average number of available TCH/PDCH timeslots for traffic usage (i.e. TCH (for
HR or FR usage) 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.
Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment –
Feature Name –
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".
Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment –
Feature Name –
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.
Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment –
Feature Name –
Definition Average number of busy TCH radio timeslot (in FR or HR usage, in traffic or in
signaling mode) and busy dynamic SDCCH/8 radio timeslot allocated as TCH.
Trigger condition The BSC takes periodically a sample of the number of busy TCH radio timeslots
and busy dynamic SDCCH/8 radio timeslots allocated as TCH. The sampling
period is set to the value indicated in the Status Inspection field. At the expiry of
the accumulation period, all samples are averaged (i.e. summed and divided
by the number of samples). The averaged value is rounded up or down to the
nearest value with an accuracy of 0.1.
A TCH radio timeslot is considered as busy during the time it is allocated to a
given MS for TCH traffic (in HR or FR usage). A dynamic SDCCH/8 timeslot
allocated as TCH is considered as busy during the time it is allocated to a given
MS for TCH traffic.
Note 1: the counter value that is indicated in the ASCII file (which can be
obtained via the OBSYNT interface) is an integer value (i.e. it is as if the BSC
multiplies by 10 the average). The reported value shall then be divided by 10
afterwards so that the value that is displayed to the end-user is the correct one.
Note 2: This counter does not take into account the PDCH radio timeslots
allocated to the MFS.
Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment –
Feature Name –
Trigger condition Whenever a TCH radio timeslot or a dynamic SDCCH/8 radio timeslot allocated
as TCH becomes busy, the BSC determines the current number of busy TCH
radio timeslots (in HR or FR usage) and busy dynamic SDCCH/8 radio timeslots
allocated as TCH. This counter is the maximum value of this number during the
accumulation period.
This counter does not take into account the PDCHs allocated to the MFS.
Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment –
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.
Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment –
Feature Name –
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].
Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment –
Feature Name –
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.
Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment –
Feature Name –
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 nearest
integer value.
Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment –
Feature Name –
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 nearest
integer value.
Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment –
Feature Name –
Definition Average number of free TCH and free dynamic SDCCH/8 radio timeslots in FR
or HR usage belonging to the interference band 4. This number is updated upon
the receipt of 48.058 RF RESOURCE INDICATION.
Trigger condition 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.
Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment –
Feature Name –
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 nearest
integer value.
Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment –
Feature Name –
Definition Cumulated time (in seconds) during which there is no free FR TCH sub-channel
to serve an incoming FR TCH request.
A TCH sub-channel is seen as busy:
i) if the TCH sub-channel is occupied by a HR or FR CS call (in particular if it is
occupied by the CS part of a DTM call), or
ii) if the TCH sub-channel is allocated to the MFS to carry PS traffic.
Trigger condition The counter is started when there is no free FR TCH sub-channel to serve an
incoming FR TCH request.
The counter is stopped when there is a free FR TCH sub-channel to serve
an incoming FR TCH request.
Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment –
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 3 –
Type Definition Set of counters related to the availability of the CCCH, SDCCH or TCH channels
External Comment –
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 3 –
Type Definition Set of counters related to the usage of the CCCH channel (PCH load, AGCH
load, RACH load)
External Comment –
Feature Name –
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 3 –
Type Definition Set of counters related to the usage of the CCCH channel (PCH load, AGCH
load, RACH load)
External Comment –
Feature Name –
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 3 –
Type Definition Set of counters related to the usage of the CCCH channel (PCH load, AGCH
load, RACH load)
External Comment –
Feature Name –
Sub Domain 3 –
Type Definition Set of counters related to the usage of the CCCH channel (PCH load, AGCH
load, RACH load)
External Comment –
Feature Name –
4.2.2 Channel
4.2.2.1 C39 - NB_TIMES_SDCCH_BUSY
Definition Number of times the SDCCH sub-channels belonging to the radio timeslot are
busy.
Type Definition Set of counters related to the usage of the SDCCH channel
External Comment –
Feature Name –
Definition Cumulated time during which the SDCCH sub-channels belonging to the related
static or dynamic SDCCH timeslot are busy.
Trigger condition For the related static or dynamic SDCCH timeslot, the counter cumulates, over
the Accumulation Period, all time unit during which a SDCCH sub-channel is
busy.
For each SDCCH allocation of the sub-channel:
1) The counter starts being incremented after the sending of the 48.058
CHANNEL ACTIVATION message concerning an SDCCH sub-channel on the
related TRX timeslot.
2) The counter stops being incremented after the reception of a 48.058 RF
CHANNEL RELEASE ACKNOWLEDGE message or the expiry of timer
T_RCR_ACK twice (supervising 48.058 RF CHANNEL RELEASE message)
concerning the SDCCH sub-channel previously activated on the related static or
dynamic SDCCH timeslot.
Example;
Let us consider that on a given static SDCCH/8 timeslot,
- SDCCH sub-channel 1 has been busy for 10 s,
- SDCCH sub-channel 2 has been busy for 20 s,
- SDCCH sub-channel n (with 3 <= n <= 8) has not been busy at all.
Then, at the expiry of the reporting period, the value reported by this counter
is 10 + 20 = 30 s.
Sub Domain 3 –
Type Definition Set of counters related to the usage of the SDCCH channel
External Comment –
Feature Name –
5.2.2 Channel
5.2.2.1 C370a - NB_TCH_FR_ALLOC
Type Definition Set of counters releated to the usage of the TCH channel (in HR or FR usage)
External Comment –
Feature Name –
Type Definition Set of counters releated to the usage of the TCH channel (in HR or FR usage)
External Comment –
Feature Name –
Definition Time (in seconds) during which a TCH radio timeslot or a dynamic SDCCH/8
timeslot in FR usage (in traffic or in signaling mode) is busy.
Trigger condition The counter cumulates over the Accumulation Period, per radio timeslot, all unit
times during which the TCH FR channel is busy.
For each channel allocation:
1) The counter starts being incremented after the sending of the 48.058
CHANNEL ACTIVATION message to the cell concerning a full rate TCH channel
(in traffic or in signaling mode) for the related TRX timeslot.
2) The counter stops being incremented after the reception of a 48.058 RF
CHANNEL RELEASE ACKNOWLEDGE message or the expiry of timer
T_RCR_ACK twice (after the sending of the 48.058 RF CHANNEL RELEASE
message) concerning the TCH channel previously activated on the related TRX
timeslot.
Sub Domain 3 –
Type Definition Set of counters releated to the usage of the TCH channel (in HR or FR usage)
External Comment –
Feature Name –
Definition Time during which a TCH radio timeslot or a dynamic SDCCH/8 timeslot in
HR usage is busy.
Trigger condition The counter cumulates, over the Accumulation Period, per half radio timeslot, all
unit times during which the TCH HR channel (or the dynamic SDCCH/8 timeslot)
is busy. Both "HR timeslots" are counted independently.
For each channel allocation:
1) The counter starts being incremented after the sending of the 48.058
CHANNEL ACTIVATION message concerning a dynamic SDCCH/8 timeslot or
an half rate TCH sub-channel mapped either on the upper half or the lower half
of the related TRX timeslot.
2) The counter stops being incremented when no HR sub-channel is active
anymore on the related TRX channel.
This is after the reception of a 48.058 RF CHANNEL RELEASE
ACKNOWLEDGE message or the expiry of timer T_RCR_ACK twice (after the
sending of the 48.058 RF CHANNEL RELEASE message) or the BSC internal
radio resource release due to any BSS problem concerning the last HR TCH
channel (or the dynamic SDCCH/8 timeslot) which was active on the related
TRX timeslot.
Sub Domain 3 –
Type Definition Set of counters releated to the usage of the TCH channel (in HR or FR usage)
External Comment –
Feature Name –
Definition Time (in seconds) during which the TCH radio timeslot or the dynamic SDCCH/8
timeslot in FR usage (in traffic or in signaling mode) is busy by a multiband
mobile station.
A MS is considered as multiband if it supports:
- the P-GSM (or E-GSM 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 FR channel (or the dynamic SDCCH/8 timeslot) is
busy (in traffic or in signaling mode).
For each channel allocation :
1) The counter starts being incremented after the sending of the 48.058
CHANNEL ACTIVATION message to the cell concerning :
- a full rate TCH channel (or the dynamic SDCCH/8 timeslot) for the related TRX
timeslot
- a mobile which has sent a 44.018 CLASSMARK CHANGE message with a
"Mobile Station Classmark 3" Information Element field 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 3 –
Type Definition Set of counters releated to the usage of the TCH channel (in HR or FR usage)
External Comment –
Feature Name –
Definition Time during which the TCH radio timeslot or the dynamic SDCCH/8 timeslot
in HR usage is busy by a multiband mobile station. A TCH radio timeslot (or a
dynamic SDCCH/8 timeslot) in HR usage is said busy by a multiband mobile
station when one or two HR sub-channels are busy by a multiband mobile
station.
A MS is considered as multiband if it supports:
- the P-GSM (or E-GSM 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.
For each channel allocation:
1) The counter starts being incremented after the sending of the 48.058
CHANNEL ACTIVATION message concerning :
- an half rate TCH channel (or a dynamic SDCC/8 timeslot) mapped either on
the upper half or the lower half of the related TRX timeslot.
- a mobile which has sent a 44.018 CLASSMARK CHANGE message with a
"Mobile Station Classmark 3" Information Element field specifying that it is a
multiband MS. the MS supports:
- the P-GSM (or E-GSM or R-GSM) and the DCS1800 bands if the
PLMN_FREQUENCY_BANDS parameter is set to "GSM900 and DCS1800
bands", or,
- the GSM850 and the DCS1800 bands 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 3 –
Type Definition Set of counters releated to the usage of the TCH channel (in HR or FR usage)
External Comment –
Feature Name –
6.2 Handover
6.2.1 All Handover
C220 - NB_INC_EXT_TCH_HO_REQ (Section 6.2.3.1 )
C221 - NB_INC_EXT_TCH_HO_ATPT (Section 6.2.3.2 )
C230 - NB_INC_INT_TCH_HO_REQ (Section 6.2.3.3 )
C231 - NB_INC_INT_TCH_HO_ATPT (Section 6.2.3.4 )
C270 - NB_INTRA_TCH_HO_REQ (Section 6.2.3.5 )
C271 - NB_INTRA_TCH_HO_ATPT (Section 6.2.3.6 )
C411 - NB_OUT_INT_TCH_HO_IDR_IN_ZONE_REQ (Section 6.2.3.7 )
C412 - NB_OUT_INT_TCH_HO_IDR_IN_ZONE_EXEC_FAIL (Section 6.2.3.8 )
C41b - NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH (Section 6.2.3.9 )
C42 - NB_INC_EXT_TCH_HO_SUCC (Section 6.2.3.10 )
C43 - NB_INC_EXT_TCH_HO_EXEC_FAIL_MS_ACCESS (Section 6.2.3.11 )
C440 - NB_TCH_HO_ATPT_23_TrafHandover (Section 6.2.2.1 )
C444 - NB_TCH_HO_ATPT_24_GenCaptureHandover (Section 6.2.3.12 )
6.2.2 SDCCH+TCH
6.2.2.1 C440 - NB_TCH_HO_ATPT_23_TrafHandover
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 3 –
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 –
6.2.3 TCH
6.2.3.1 C220 - NB_INC_EXT_TCH_HO_REQ
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
Definition Number of intra cell TCH (in HR or FR usage) handover requests. This counter
takes into account handovers from TCH in traffic or in signaling mode. It does
not take into account DTM Assignments.
Trigger condition Whenever the BSC process responsible for the handover procedure starts an
intra cell TCH handover procedure.
Sub Domain 3 –
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 –
Definition Number of intra cell TCH (in HR or FR usage) handover attempts. This counter
takes into account handovers from TCH in traffic or in signaling mode. It does
not take into account DTM Assignments.
Trigger condition 44.018 ASSIGNMENT COMMAND is sent to the BTS for intra cell handover
on TCH.
Sub Domain 3 –
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 –
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 3 –
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 –
Sub Domain 3 –
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 –
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 3 –
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 –
Sub Domain 3 –
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 –
Sub Domain 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
Sub Domain 3 –
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 –
Definition Number of high priority TCH requests served when the number of free TCH
timeslots is less than or equal to NUM_TCH_EGNCY_HO.
Trigger condition The counter is incremented on the serving cell whenever the 48.058 CHANNEL
ACTIVATION message allocating a TCH channel is sent and the following two
conditions are both fulfilled:
1) the TCH is allocated to serve i) an internal handover Cause 2, 3, 4, 5, 6, 7, 10,
11, 12, 15, 16, 17, 18, 22, 27, or, ii) an external handover Cause "Uplink quality",
"Uplink strength", "Downlink quality", "Downlink strength", "Distance", or iii) a
normal assignment or an external handover with the preemption indicator set
(i.e. Preemption Capability Indicator = 1 and EN_TCH_PREEMPT = Enable).
2) the number of free TCH timeslots is less than or equal to
NUM_TCH_EGNCY_HO.
Note 1: This counter counts both inter-PLMN and intra-PLMN handover events.
Note 2: The HMI name of the parameter NUM_TCH_EGNCY_HO is
"NUM_TCH_EMERGENCY_HO".
Sub Domain 3 –
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 –
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 3 –
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 –
Sub Domain 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
Sub Domain 3 –
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 –
Trigger condition Whenever the timer supervising the handover procedure (T3103) expires during
an internal inter-cell TCH handover.
Sub Domain 3 –
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 –
Trigger condition Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
Sub Domain 3 –
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 –
Trigger condition Whenever a internal intra-cell TCH handover cannot be performed, because
there is no free TCH channel to serve the handover.
Note 1: In MX BSC, this counter is incremented whenever an intra-cell TCH
handover cannot be performed due to the TCH processing capacity of CCP
reaches the limit defined by the MAX_TCH_PER_CCP parameter. In this case,
MC926 is also incremented by one.
Note 2: In IP mode, this counter is increased by 1 if:
- the cell mapped on a BTS is in IP congestion status;
- or the TCH processing capacity of AbisBTSGroup reaches the limit defined by
the NB_MAX_ACTIVE_TCH_TS parameter
Sub Domain 3 –
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 –
Sub Domain 3 –
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 –
Trigger condition Whenever the timer supervising the handover procedure (T3103) expires during
an internal inter-cell TCH handover.
Sub Domain 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
Sub Domain 3 –
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 –
Trigger condition Whenever the timer supervising the handover procedure (T3107) expires during
an internal intra-cell.
Sub Domain 3 –
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 –
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.
Sub Domain 3 –
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 –
Definition Number of external handovers triggered by the MSC but not required by the BSS.
Sub Domain 3 –
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 –
Sub Domain 3 –
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 –
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.
External Comment –
Feature Name –
Trigger condition Whenever an Information Frame is retransmitted on a logical RSL LAPD link.
External Comment –
Feature Name –
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.
External Comment –
Feature Name –
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.
External Comment –
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.
External Comment –
Feature Name –
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.
External Comment –
Feature Name –
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 3 –
External Comment –
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 3 –
External Comment –
Trigger condition Whenever an Information Frame is retransmitted on a logical GSL LAPD link.
Sub Domain 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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.
External Comment –
Feature Name –
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.
External Comment –
Feature Name –
Definition Number of Information frames received on the LapD link, excluding the
re-transmissions.
External Comment –
Feature Name –
Definition Number of incoming X.25 calls that are closed in an abnormal way, as seen
by the BSC.
External Comment –
Feature Name –
Definition Number of outgoing X.25 calls that are closed in an abnormal way, as seen
by the BSC.
External Comment –
Feature Name –
Definition Number of incoming X.25 calls that are successfully closed by the BSC.
External Comment –
Feature Name –
Definition Number of outgoing X.25 calls that are successfully closed by the BSC.
External Comment –
Feature Name –
9 BSC-TYPE 9 - N7 measurements
Trigger condition Whenever a changeover is made from using the primary signalling link to the
secondary signalling link.
Sub Domain 2 A
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 –
Trigger condition Whenever a change back is made from using the secondary signalling link
to the primary signalling link.
Sub Domain 2 A
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 –
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 2 A
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 –
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 2 A
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 –
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 2 A
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 –
Trigger condition Whenever the timer supervising the reception of an acknowledgement message
(T7) expires.
Sub Domain 2 A
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 –
Trigger condition Whenever a No.7 Signalling Link failure is detected due to an excessive Signal
Unit error rate.
Sub Domain 2 A
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 –
Trigger condition Whenever a No.7 Signalling Link failure is detected due to an excessive duration
of Signalling Link congestion.
Sub Domain 2 A
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 –
Trigger condition Whenever the timer supervising the alignment of the Signalling Link (T2) expires.
Sub Domain 2 A
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 –
Sub Domain 2 A
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 –
Sub Domain 2 A
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 –
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 2 A
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 –
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 2 A
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 –
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 2 A
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 –
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 2 A
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 –
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 2 A
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 –
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 2 A
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 –
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 2 A
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 –
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 2 A
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 –
Sub Domain 2 A
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 –
Sub Domain 2 A
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 –
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 2 A
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 –
Sub Domain 2 A
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 –
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 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Feature Name –
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 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Feature Name –
Trigger condition Whenever a 48.008 CLEAR REQUEST message with a cause value of
"equipment failure" is sent on A interface to the MSC.
Sub Domain 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Feature Name –
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 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Feature Name –
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 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Feature Name –
Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of
"radio interface message failure" is sent on A interface to the MSC.
Sub Domain 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Feature Name –
Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of
"O&M intervention" is sent on A interface to the MSC.
Sub Domain 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Feature Name –
Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of
"equipment failure" is sent on A interface to the MSC.
Sub Domain 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Feature Name –
Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of
"no radio resource available" is sent on A interface to the MSC.
Sub Domain 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Feature Name –
Trigger condition 1) Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of
"requested terrestrial resource unavailable" is sent on A interface to the MSC.
2) Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of
"terrestrial resource already allocated" is sent on A interface to the MSC.
Sub Domain 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Feature Name –
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 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Feature Name –
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 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Feature Name –
Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of
"radio interface failure" is sent on A interface to the MSC.
Sub Domain 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Feature Name –
Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of
"cipher algorithm not supported" is sent on A interface to the MSC.
Sub Domain 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Feature Name –
Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of
"BSS not equiped" is sent on A interface to the MSC.
Sub Domain 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Feature Name –
Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of
"protocol error between BSC and MSC" is sent on A interface to the MSC.
Sub Domain 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Feature Name –
Trigger condition Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of
"requested speech version unavailable" is sent on A interface to the MSC.
Sub Domain 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Feature Name –
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 2 A
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
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 2 A
Sub Domain 3 –
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
Sub Domain 2 A
Sub Domain 3 –
Type Definition Set of counters related to the different causes of 08.08CLEAR REQUEST and
08.08ASSIGNMENT FAILURE
External Comment –
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 –
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 –
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 –
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 –
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".
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 –
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.
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 –
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.
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 –
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 –
12.2 Handover
12.2.1 All Handover
RMSI63b - MR_MAT_AVSS_VS_NAVSS (Section 12.2.2.1 )
12.2.2 RMS
12.2.2.1 RMSI63b - MR_MAT_AVSS_VS_NAVSS
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
12.3.2 RMS
12.3.2.1 RMSI3a - TPR_RXQUAL_UL_RXLEV_UL_I
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition Whenever in a 44.018 MEASUREMENT RESULT the Timing Advance is equal
to i.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition Whenever in a 44.018 MEASUREMENT RESULT the calculated UL Path Loss
is in the given interval .
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition Whenever in a 44.018 MEASUREMENT RESULT the calculated DL Path Loss
is in the given interval .
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition Whenever in a 44.018 MEASUREMENT RESULT the Path Balance is in the
given interval .
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Definition Number of BSS originating SCCP connection failures due to the NSS.
Sub Domain 2 A
Type Definition Set of counters related to the SCCP layer of the N7 Signalling Links
External Comment –
Feature Name –
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 2 A
Type Definition Set of counters related to the SCCP layer of the N7 Signalling Links
External Comment –
Feature Name –
Sub Domain 2 A
Type Definition Set of counters related to the SCCP layer of the N7 Signalling Links
External Comment –
Feature Name –
Sub Domain 2 A
Type Definition Set of counters related to the SCCP layer of the N7 Signalling Links
External Comment –
Feature Name –
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 2 A
Type Definition Set of counters related to the SCCP layer of the N7 Signalling Links
External Comment –
Feature Name –
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 2 A
Type Definition Set of counters related to the SCCP layer of the N7 Signalling Links
External Comment –
Feature Name –
Sub Domain 2 A
Type Definition Set of counters related to the SCCP layer of the N7 Signalling Links
External Comment –
Feature Name –
Sub Domain 2 A
Type Definition Set of counters related to the SCCP layer of the N7 Signalling Links
External Comment –
Feature Name –
Sub Domain 2 A
Type Definition Set of counters related to the SCCP layer of the N7 Signalling Links
External Comment –
Feature Name –
Sub Domain 2 A
Type Definition Set of counters related to the SCCP layer of the N7 Signalling Links
External Comment –
Feature Name –
14.2 Adjacency
14.2.1 All Adjacency
C720 - NB_ADJ_SCELL_OUT_TCH_HO_ATPT (Section 14.2.2.1 )
C721 - NB_ADJ_SCELL_OUT_TCH_HO_SUCC (Section 14.2.2.2 )
C722 - NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_REV (Section 14.2.2.3 )
C723 - NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_NO_REV (Section
14.2.2.4 )
C724 - NB_ADJ_SCELL_OUT_TCH_HO_EMERGENCY_ATPT (Section
14.2.2.5 )
C725 - NB_ADJ_SCELL_OUT_TCH_HO_BETTERCELL_ATPT (Section
14.2.2.6 )
C727 - NB_ADJ_SCELL_OUT_TCH_HO_TRAFFIC_ATPT (Section 14.2.2.7 )
C728 - NB_ADJ_SCELL_OUT_ FORCED_DR_ATPT (Section 14.2.2.8 )
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 2 –
Sub Domain 3 –
Type Definition Set of counters related to outgoing TCH handover provided per adjacency.
External Comment –
Feature Name –
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.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters related to outgoing TCH handover provided per adjacency.
External Comment –
Feature Name –
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.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters related to outgoing TCH handover provided per adjacency.
External Comment –
Feature Name –
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.
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 2 –
Sub Domain 3 –
Type Definition Set of counters related to outgoing TCH handover provided per adjacency.
External Comment –
Feature Name –
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 2 –
Sub Domain 3 –
Type Definition Set of counters related to outgoing TCH handover provided per adjacency.
External Comment –
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.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters related to outgoing TCH handover provided per adjacency.
External Comment –
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.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters related to outgoing TCH handover provided per adjacency.
External Comment –
Definition Number of outgoing (external or internal) inter-cell directed retries attempts with
Forced directed retry cause.
Trigger condition Whenever a 44.018 HANDOVER COMMAND message is sent to the MS for an
outgoing (external or internal) inter-cell directed retry Cause 20 from the serving
cell to a given target cell.
Note: This counter counts both inter-PLMN and intra-PLMN directed retry
events.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters related to outgoing TCH handover provided per adjacency.
External Comment –
15.2 Adjacency
15.2.1 All Adjacency
C730 - NB_ADJ_TCELL_INC_TCH_HO_ATPT (Section 15.2.2.1 )
C731 - NB_ADJ_TCELL_INC_TCH_HO_SUCC (Section 15.2.2.2 )
C733 - NB_ADJ_TCELL_INC_TCH_HO_EXEC_FAIL_MS_ACC (Section
15.2.2.3 )
C734 - NB_ADJ_TCELL_INC_TCH_HO_EMERGENCY_ATPT (Section
15.2.2.4 )
C735 - NB_ADJ_TCELL_INC_TCH_HO_BETTERCELL_ATPT (Section
15.2.2.5 )
C737 - NB_ADJ_TCELL_INC_TCH_HO_TRAFFIC_ATPT (Section 15.2.2.6 )
C738 - NB_ADJ_TCELL_INC_FORCED_DR_ATPT (Section 15.2.2.7 )
C753 - NB_ADJ_TCELL_INC_TCH_HO_OTHER_ATPT (Section 15.2.2.8 )
Sub Domain 2 –
Sub Domain 3 –
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 –
Sub Domain 2 –
Sub Domain 3 –
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 –
Sub Domain 2 –
Sub Domain 3 –
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 –
Sub Domain 2 –
Sub Domain 3 –
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 –
Sub Domain 2 –
Sub Domain 3 –
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 –
Sub Domain 2 –
Sub Domain 3 –
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 –
Sub Domain 2 –
Sub Domain 3 –
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 –
Sub Domain 2 –
Sub Domain 3 –
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 –
16.2 Handover
16.2.1 All Handover
C100 - NB_OUT_INT_SDCCH_HO_ATPT (Section 16.2.2.1 )
C101 - NB_INTRA_SDCCH_HO_PREP_FAIL_CONG (Section 16.2.2.2 )
C102 - NB_INTRA_SDCCH_HO_SUCC (Section 16.2.2.3 )
C103 - NB_INTRA_SDCCH_HO_EXEC_FAIL_NO_REV (Section 16.2.2.4 )
C107 - NB_INTRA_SDCCH_HO_EXEC_FAIL_REV (Section 16.2.2.5 )
C115 - NB_SDCCH_HO_MSC_TRIG (Section 16.2.2.6 )
C310 - NB_INC_EXT_SDCCH_HO_REQ (Section 16.2.2.7 )
C311 - NB_INC_EXT_SDCCH_HO_ATPT (Section 16.2.2.8 )
C330 - NB_INC_INT_SDCCH_HO_REQ (Section 16.2.2.9 )
C331 - NB_INC_INT_SDCCH_HO_ATPT (Section 16.2.2.10 )
C360 - NB_INTRA_SDCCH_HO_REQ (Section 16.2.2.11 )
C361 - NB_INTRA_SDCCH_HO_ATPT (Section 16.2.2.12 )
C445 - NB_SDCCH_HO_ATPT_23_TrafHandover (Section 16.2.2.13 )
C446 - NB_SDCCH_HO_ATPT_24_GenCaptureHandover (Section 16.2.2.14 )
C454 - NB_SDCCH_HO_ATPT_22_TooShortDistance (Section 16.2.2.15 )
C510 - NB_SDCCH_HO_ATPT_2_TooLowQualUp (Section 16.2.2.16 )
C511 - NB_SDCCH_HO_ATPT_3_TooLowLevUp (Section 16.2.2.17 )
C512 - NB_SDCCH_HO_ATPT_4_TooLowQualDown (Section 16.2.2.18 )
C513 - NB_SDCCH_HO_ATPT_5_TooLowLevDown (Section 16.2.2.19 )
C514 - NB_SDCCH_HO_ATPT_6_TooLongDistance (Section 16.2.2.20 )
C516 - NB_SDCCH_HO_ATPT_15_TooHighLevInterfUp (Section 16.2.2.21 )
C517 - NB_SDCCH_HO_ATPT_16_TooHighLevInterfDown (Section 16.2.2.22 )
C518 - NB_SDCCH_HO_ATPT_12_TooLowPowBudg (Section 16.2.2.23 )
16.2.2 SDCCH
16.2.2.1 C100 - NB_OUT_INT_SDCCH_HO_ATPT
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 3 –
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 –
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 3 –
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 –
Sub Domain 3 –
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 –
Trigger condition Whenever the timer supervising the internal intra-cell SDCCH handover
procedure (T3107) expires.
Sub Domain 3 –
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 –
Sub Domain 3 –
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 –
Definition Number of external handovers triggered by the MSC but not required by the BSS.
Sub Domain 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
Trigger condition Whenever the BSC process responsible for the handover procedure starts an
intra cell SDCCH handover procedure.
Sub Domain 3 –
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 –
Trigger condition 44.018ASSIGNMENT COMMAND is sent to the MS via the cell for intra cell
handover on SDCCH.
Sub Domain 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
Definition Number of SDCCH inter-cell internal or external handover attempts with cause
20: "forced directed retry". This counter is related to a forced directed retry
(internal or external).
Trigger condition Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTS
because of cause 20. This counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 3 –
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 –
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 3 –
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 –
Sub Domain 3 –
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 –
Sub Domain 3 –
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 –
Sub Domain 3 –
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 –
Sub Domain 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
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 3 –
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 –
Sub Domain 3 –
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 –
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 3 –
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 –
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 3 –
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 –
Sub Domain 3 –
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 –
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 3 –
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 –
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 3 –
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 –
17.2 Handover
17.2.1 All Handover
C142a - NB_OUT_FORCED_IDR_SUCC (Section 17.2.2.1 )
C142b - NB_OUT_FORCED_EDR_SUCC (Section 17.2.2.2 )
C142c - NB_OUT_NOR_IDR_SUCC (Section 17.2.2.3 )
C142d - NB_OUT_NOR_EDR_SUCC (Section 17.2.2.4 )
C143a - NB_OUT_FORCED_IDR_EXEC_FAIL_REV (Section 17.2.2.5 )
C143b - NB_OUT_FORCED_IDR_EXEC_FAIL_NO_REV (Section 17.2.2.6 )
C143c - NB_OUT_FORCED_EDR_EXEC_FAIL_REV (Section 17.2.2.7 )
C143d - NB_OUT_FORCED_EDR_EXEC_FAIL_NO_REV (Section 17.2.2.8 )
C143e - NB_OUT_NOR_IDR_EXEC_FAIL_REV (Section 17.2.2.9 )
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.
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 –
Definition Number of outgoing forced external directed retry (towards a TCH channel in
HR or FR usage) successes.
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 –
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.
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 –
Definition Number of outgoing normal external directed retry (towards a TCH channel in
HR or FR usage) successes.
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 –
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.
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 –
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).
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 –
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.
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 –
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.
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 –
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.
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 –
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).
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 –
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.
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 –
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.
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 –
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.
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 –
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.
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 –
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.
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 –
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.
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 –
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.
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 –
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.
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 –
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.
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 –
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.
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 –
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.
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 –
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)
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 –
Trigger condition Whenever the BSC process responsible for handover procedure selects the
target cell for forced or normal internal directed retry.
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 –
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,
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 –
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
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 –
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.
Type Definition Set of counters related to the Short Message Service Cell Broadcast.
External Comment –
Feature Name –
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.
Type Definition Set of counters related to the Short Message Service Cell Broadcast.
External Comment –
Feature Name –
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).
Type Definition Set of counters related to the Short Message Service Cell Broadcast.
External Comment –
Feature Name –
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).
Type Definition Set of counters related to the Short Message Service Cell Broadcast.
External Comment –
Feature Name –
19.2.2 RMS
19.2.2.1 RMS10 - VQ_NOISY_UL_INTERFERENCE
Definition Number of calls suffering from problem of interference on the uplink path.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Definition Number of calls suffering from problems of interference on the downlink path.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Definition Number of calls suffering from bad coverage on the uplink path.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Definition Number of calls suffering from bad coverage on the downlink path.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Definition Number of calls with bad quality measurements and with bad FER
measurements on the uplink path.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Definition Number of calls with bad quality measurements but with good FER
measurements on the uplink path.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Definition Number of calls with fair quality measurements but with bad FER measurements
on the uplink path.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Definition Number of measurement results indicating that DTX is used on the downlink
path, used for RMS.
Trigger condition Whenever a 48.058 MEASUREMENT RESULTS message is sent by the BTS,
with DTX_UL=1, and used for RMS.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Definition Reserved for internal Alcatel-Lucent usage (PS detection on TS basis for Edge
capable TRX)
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Feature Name –
Definition Reserved for internal Alcatel-Lucent usage (PS detection on TS basis for Edge
capable TRX)
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Feature Name –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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 2 –
Sub Domain 3 –
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.
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
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.
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 2 –
Sub Domain 3 –
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.
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
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.
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 2 –
Sub Domain 3 –
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.
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
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.
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 2 –
Sub Domain 3 –
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.
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
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.
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 2 –
Sub Domain 3 –
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.
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
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.
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 2 –
Sub Domain 3 –
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.
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
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.
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 2 –
Sub Domain 3 –
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.
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
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.
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 2 –
Sub Domain 3 –
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.
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 2 –
Sub Domain 3 –
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.
Trigger condition .
Sub Domain 2 –
Sub Domain 3 –
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.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Sub Domain 2 –
Sub Domain 3 –
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.
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
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.
Sub Domain 2 –
Sub Domain 3 –
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.
Sub Domain 2 –
Sub Domain 3 –
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.
Sub Domain 2 –
Sub Domain 3 –
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.
Sub Domain 2 –
Sub Domain 3 –
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.
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 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition Whenever the Radio Link counter (S) is in the given interval of MEAS_STAT_S.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition Whenever a measurement report indicates that C/I value for the extended
measurement frequency is included in the corresponding interval.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
19.2.3 Speech
19.2.3.1 RMS48b - MAX_AMR_HR_UL_RXLEV_UL
Trigger condition –
Sub Domain 2 –
Sub Domain 3 –
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.
19.3.2 Channel
19.3.2.1 RMS31 - 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.
Type Definition Set of counters describing result of radio measurements for a given cell / TRX.
External Comment –
20.2.2 Handover
20.2.2.1 C403a - NB_INC_EXT_TCH_HO_NEW_BAND_ATPT
Sub Domain 3 –
Type Definition Set of counters related to handovers including a change of the TCH frequency
band.
External Comment –
Sub Domain 3 –
Type Definition Set of counters related to handovers including a change of the TCH frequency
band.
External Comment –
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 3 –
Type Definition Set of counters related to handovers including a change of the TCH frequency
band.
External Comment –
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.
Sub Domain 3 –
Type Definition Set of counters related to handovers including a change of the TCH frequency
band.
External Comment –
Sub Domain 3 –
Type Definition Set of counters related to handovers including a change of the TCH frequency
band.
External Comment –
Sub Domain 3 –
Type Definition Set of counters related to handovers including a change of the TCH frequency
band.
External Comment –
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 3 –
Type Definition Set of counters related to handovers including a change of the TCH frequency
band.
External Comment –
Sub Domain 3 –
Type Definition Set of counters related to handovers including a change of the TCH frequency
band.
External Comment –
Definition Average emitted power at the BTS antenna output connector for the GSM
frequency band (GSM850 or E-GSM or P-GSM).
Counter coded in tenth of Watt. Value 0 indicates that the TRX frequency is
neither GSM850 nor E-GSM nor P-GSM band. Value FFFFh indicates overflow
of the measurement period.
Trigger condition TRE collects permanently power data. At the end of each measurement period,
triggered by reception of EME_DATA_REQ message from the BSC, the average
emitted power is calculated and sent back to the BSC.
Sub Domain 2 –
Sub Domain 3 –
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.
Definition Average emitted power at the BTS antenna output connector for the DCS
frequency band (DCS1800 or DCS1900).
Counter coded in tenth of Watt. Value 0 indicates that the TRX frequency is
neither DCS1800 nor DCS1900 band. Value FFFFh indicates overflow of the
measurement period.
Trigger condition TRE collects permanently power data. At the end of each measurement period,
triggered by reception of EME_DATA_REQ message from the BSC, the average
emitted power is calculated and sent back to the BSC.
Sub Domain 2 –
Sub Domain 3 –
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.
22 BSC-TYPE 35 - IP transport
22.2.2 IP (QoS)
22.2.2.1 IP11 - 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 2 –
Sub Domain 3 –
External Comment –
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 2 –
Sub Domain 3 –
External Comment –
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 2 –
Sub Domain 3 –
External Comment –
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 2 –
Sub Domain 3 –
External Comment –
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 2 –
Sub Domain 3 –
External Comment –
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 2 –
Sub Domain 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 2 –
Sub Domain 3 –
External Comment –
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 2 –
Sub Domain 3 –
External Comment –
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 2 –
Sub Domain 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 2 –
Sub Domain 3 –
External Comment –
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 2 –
Sub Domain 3 –
External Comment –
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 2 –
Sub Domain 3 –
External Comment –
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 2 –
Sub Domain 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
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.
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 3 –
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.
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 3 –
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"
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 3 –
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"
Definition Minimum clock difference of all pollings to the frequency synchro time server 1
during the last evaluation period (default value 24h).
Sub Domain 3 –
Definition Minimum clock difference of all pollings to the frequency synchro time server 2
during the last evaluation period (default value 24h).
Sub Domain 3 –
Definition Round trip time of the last polling performed by the BTS to the frequency
synchro time server 1 during the Granularity Period (15’).
Sub Domain 3 –
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.
Definition Round trip time of the last polling performed by the BTS to the frequency
synchro time server 2 during the Granularity Period (15’).
Sub Domain 3 –
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.
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 3 –
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.
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 3 –
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.
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 3 –
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 3 –
Definition Gradient (calculated frequency offset) of the last accepted evaluation performed
by the BTS using the frequency synchro time server 1.
Sub Domain 3 –
Definition Gradient (calculated frequency offset) of the last accepted evaluation performed
by the BTS using the frequency synchro time server 2
Sub Domain 3 –
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.
Sub Domain 3 –
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.
Sub Domain 3 –
Definition BTS OCXO last tuning using the frequency synchro time server (0 = no tuning,
1 = primary, 2 = secondary).
Sub Domain 3 –
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.
Definition BTS OCXO last tuning DAC Digital Analog Converter correction value (range
0..4095,).
Sub Domain 3 –
External Comment The current OCXO frequency is a linear function of this value.
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
Definition Counts the number of bytes of the IP_BSSAsig 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 3 –
External Comment –
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 3 –
External Comment –
Definition Counts the number of SCTP packets sent by an IP TC to a given IP BSC for
the IP_BSSAsig 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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
Definition Counts the number of payload bytes of the UL MUXTRAUP packets sent by an
IP BTS to the IP TC.
Trigger condition Each time an UL MUXTRAUP packet is sent by the IP BTS to a given IP TC,
this counter is increased by the number of bytes of the UDP payload of this
message. This counter is managed by the SUM.
The UDP payload of a MUXTRAUP packet is defined as the MUXTRAUP packet
format without IP and UDP header.
Sub Domain 3 –
External Comment –
Trigger condition Each time an UL MUXTRAUP packet is sent by the IP BTS, this counter is
increased by 1.
Sub Domain 3 –
External Comment –
Definition Definition: Counts the number of payload bytes of the DL MUXTRAUP packets
sent by all the TC racks to a given IP BTS.
Trigger condition Each time a DL MUXTRAUP packet is sent by all the TC racks 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 3 –
External Comment –
Definition Counts the number of DL IPTCH packets (i.e. MUXTRAUP frames) sent by
the primary IP TC 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 3 –
External Comment –
Definition Counts the max number of payload bytes of the DL MUXTRAUP packets sent
by all the TC racks 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 all the TC racks 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 3 –
External Comment –
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 2 –
Sub Domain 3 –
External Comment –
Definition Counts the number of payload bytes of the eTRAUP packets (DL & UL) sent by
a TC rack to all other TC racks.
Trigger condition Each time a TC rack sends an eTRAUP packet (DL or 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 2 –
Sub Domain 3 –
External Comment –
Definition Counts the number of eTRAUP packets (DL & UL) sent by a TC rack to all
other TC racks.
Trigger condition Each time a TC rack sends a eTRAUP packet (DL or UL) to another TC rack,
this counter is increased by 1. Such routing is performed in the TCIF board.
Sub Domain 2 –
Sub Domain 3 –
External Comment –
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 2 –
Sub Domain 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
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 3 –
External Comment –
Definition Number of CONNECTION REQUEST received from the RNC by the BSC, when
Iur-g interface is used.
Sub Domain 3 –
External Comment –
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 3 –
External Comment –
24.2 Handover
24.2.1 All Handover
MC101 - NB_INTRA_SDCCH_HO_PREP_FAIL_CONG (Section 24.2.4.1 )
MC1040 - NB_HO_ATPT_23_TrafHandover (Section 24.2.5.1 )
MC1044 - NB_HO_ATPT_24_gencapture (Section 24.2.5.2 )
MC1050 - NB_HO_22_TooShortDistance (Section 24.2.5.3 )
MC151 - NB_INC_IDR_SUCC (29) (Section 24.2.2.1 )
MC153 - NB_INC_IDR_REQ (Section 24.2.2.2 )
MC41b - NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH (Section 24.2.7.1 )
MC448a - NB_TCH_HO_ATPT_26_BadQualHR (Section 24.2.7.2 )
MC448b - NB_TCH_HO_ATPT_27_GoodQualFR (Section 24.2.7.3 )
MC449 - NB_TCH_HO_ATPT_28_FastTraffic (Section 24.2.7.4 )
MC460a - NB_TCH_EMERGENCY_HO_PRESERVATION (Section 24.2.7.5 )
MC461 - NB_TCH_HO_ATPT_29_TFO (Section 24.2.7.6 )
MC462a - NB_OUT_INTER_PLMN_TCH_HO_REQ (Section 24.2.7.7 )
MC462b - NB_OUT_INTER_PLMN_TCH_HO_ATPT (Section 24.2.7.8 )
MC462c - NB_OUT_INTER_PLMN_TCH_HO_SUCC (Section 24.2.7.9 )
MC463a - NB_INC_INTER_PLMN_TCH_HO_REQ (Section 24.2.7.10 )
MC463b - NB_INC_INTER_PLMN_TCH_HO_ATPT (Section 24.2.7.11 )
MC463c - NB_INC_INTER_PLMN_TCH_HO_SUCC (Section 24.2.7.12 )
MC480 - NB_TCH_HO_REQ_30_ReturnCSZone (Section 24.2.3.1 )
MC481 - NB_TCH_HO_ATPT_30_ReturnCSZone (Section 24.2.3.2 )
MC482 - NB_TCH_HO_REQ_30_ABORTED (Section 24.2.3.3 )
MC541 - NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS (Section 24.2.7.13 )
MC541a - NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS (Section
24.2.7.14 )
MC551 - NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS (Section
24.2.7.15 )
MC555 - NB_INC_IDR_PREP_FAIL_CONG_R_ABIS (Section 24.2.2.3 )
MC561 - NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS (Section
24.2.7.16 )
MC586a - NB_TCH_HO_ATPT_10_TooLowLevUpInZone (Section 24.2.7.17 )
MC586b - NB_TCH_HO_ATPT_11_TooLowLevDownInZone (Section 24.2.7.18
)
MC586c - NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone (Section
24.2.7.19 )
MC607 - NB_SDCCH_HO_20_HighLevNeigCellForcDR (Section 24.2.4.2 )
MC642 - NB_INC_EXT_HO_SUCC (Section 24.2.5.4 )
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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Trigger condition Whenever the BSC process responsible for handover procedure selects the
target cell for forced or normal internal directed retry.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Trigger condition Whenever a 44.018 Assignment Command is sent to the MS for a TCH HO
cause 30.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
24.2.4 SDCCH
24.2.4.1 MC101 - NB_INTRA_SDCCH_HO_PREP_FAIL_CONG
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Trigger condition Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTS
because of cause 20.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
24.2.5 SDCCH+TCH
24.2.5.1 MC1040 - NB_HO_ATPT_23_TrafHandover
Definition MC1040=C440+C445
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC1044=C444+C446
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC1050=C450+C454
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC642=C42+C82
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC643=C43+C83
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition MC646=C46+C86
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC647=C47+C87
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC648=C48+C88
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC650=C50+C90
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC652=C52+C92
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC653=C53+C93
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC655a=C55a+C95a
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC656=C56+C96
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC657=C57+C97
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC658=C58+C98
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC660=C60+C100
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC662=C62+C102
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC663=C63+C103
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC667=C67+C107
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC670=C470+C510
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC671=C471+C511
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC672=C472+C512
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC673=C473+C513
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC674=C474+C514
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC675=C75+C115
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC676=C476+C516
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC677=C477+C517
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC678=C478+C518
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC679=C479+C519
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC785a=C585a+C605a
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC785d=C585d+C605d
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC785e=C585e+C605e
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC785f=C585f+C605f
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC820=C220+C310
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC821=C221+C311
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC830=C230+C330
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC831=C231+C331
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC870=C270+C360
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC871=C271+C361
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Number of incoming external SDCCH and TCH HO requests from a UMTS
system.
Trigger condition 48.008 HANDOVER REQUEST received by the BSC for an SDCCH or TCH
external handover towards the target cell. Only handovers from a UMTS system
shall be taken into account (if the field Cell Identifier discriminator in the I.E. Cell
Identifier (serving) of the 48.008 HANDOVER REQUEST is set to ’1011’),
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Number of incoming external SDCCH and TCH HO successes from a UMTS
system.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Number of incoming external SDCCH and TCH HO attempts from a UMTS
system.
Trigger condition Whenever 48.008HANDOVER REQUEST ACK is sent by the target BSC
containing the 44.018HANDOVER COMMAND towards the target cell.
Only handovers from a UMTS system shall be taken into account (if the field Cell
Identifier discriminator in the I.E. Cell Identifier (serving) of the corresponding
48.008 HANDOVER REQUEST is set to ’1011’).
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
24.2.6 Speech
24.2.6.1 MC936 - 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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
24.2.7 TCH
24.2.7.1 MC41b - NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Trigger condition The counter is incremented on the serving cell whenever the 48.058 CHANNEL
ACTIVATION message allocating a TCH channel is sent and the following two
conditions are both fulfilled:
1) the TCH is allocated to serve i) an internal handover Cause 2, 3, 4, 5, 6, 7, 10,
11, 12, 15, 16, 17, 18, 22, 27, or, ii) an external handover Cause "Uplink quality",
"Uplink strength", "Downlink quality", "Downlink strength", "Distance", or iii) a
normal assignment or an external handover with the preemption indicator set
(i.e. Preemption Capability Indicator = 1 and EN_TCH_PREEMPT = Enable).
2) the number of free TCH timeslots is less than or equal to
NUM_TCH_EGNCY_HO and there is at least one request queued for this cell.
Note 1: This counter counts both inter-PLMN and intra-PLMN handover events.
Note 2: The HMI name of the parameter NUM_TCH_EGNCY_HO is
"NUM_TCH_EMERGENCY_HO".
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Number of inter-PLMN TCH outgoing handover or directed retry attempts. This
counter takes into account TCH in traffic or in signaling mode.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Trigger condition Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Trigger condition Whenever a internal intra-cell TCH handover cannot be performed, because
there is no free TCH channel to serve the handover.
Note 1: In MX BSC, this counter is incremented whenever an intra-cell TCH
handover cannot be performed due to the TCH processing capacity of CCP
reaches the limit defined by the MAX_TCH_PER_CCP parameter. In this case,
MC926 is also incremented by one.
Note 2: In IP mode, this counter is increased by 1 if:
- the cell mapped on a BTS is in IP congestion status;
- or the TCH processing capacity of AbisBTSGroup reaches the limit defined by
the NB_MAX_ACTIVE_TCH_TS parameter
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Nb of TCH outgoing handover requests, per TRX. Intracell, internal intercell
and external handovers are counted together. This counter takes into account
handovers from TCH in traffic or in signaling mode. It does not take into account
DTM Assignments.
MC710 = C710
Trigger condition 1) Intracell HO: Whenever the BSC process responsible for the handover
procedure starts an intra cell TCH handover procedure.
2) Internal intercell HO: Whenever the BSC process responsible for the
handover procedure selects a target cell (among a list of target cells) for internal
inter cell TCH handover.
3) External HO: Whenever a 48.008 HANDOVER REQUIRED message is sent
on A interface to the MSC. If more than one 48.008 HANDOVER REQUIRED is
sent in the frame of the same Handover procedure, the counter is incremented
only once.
48.008 HANDOVER REQUIRED is sent in following situations:
1) An external handover alarm has been raised, with corresponding list of
candidate cells.
2) The list of candidate cells for the current alarm has been updated.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Trigger condition Whenever a 48.008 HANDOVER REQUEST is received for a TCH with a SAI
in the source cell identifier and indicating an emergency cause (uplink quality,
uplink strength, downlink quality, downlink strength, distance).
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Trigger condition Whenever a 48.008 HANDOVER REQUEST is received for a TCH with a SAI in
the source cell identifier
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
MC960 -
NB_DISCARDED_PS_CHAN_REQD_BECAUSE_GSL_CONGESTION
(Section 24.3.2.2 )
MC962 - NB_INVALID_CHAN_REQD_RECEIVED_BY_BSC (Section 24.3.2.3
)
MC963 -
NB_NON_PS_CHAN_REQD_DISCRADED_BECAUSE_CONGESTION
(Section 24.3.2.4 )
MC964 - NB_VALID_LOCATION_UPDATE_RECEIVED_BY_BSC (Section
24.3.2.5 )
MC965 - NB_LCS_INTERRUPTED_INTRA_BSC_HO (Section 24.3.7.7 )
MC966 - NB_LCS_INTERRUPTED_INTER_BSC_HO (Section 24.3.7.8 )
MC990 - NB_MS_REPEATED_ACCH_CAPABLE (Section 24.3.8.3 )
MC991 - NB_CALLS_RFACCH_ACTIVATED (Section 24.3.8.4 )
MC992 - NB_CALLS_RSACCH_ACTIVATED (Section 24.3.8.5 )
MC993 - NB_AMR_TCH_DROP_RLF_TRX (Section 24.3.4.7 )
MC994 - NB_AMR_TCH_DROP_RLF_TRX_RSACCH (Section 24.3.4.8 )
MC995 - NB_AMR_TCH_DROP_OUT_HO_TRX (Section 24.3.5.21 )
MC996 - NB_AMR_TCH_DROP_OUT_HO_TRX_RFACCH (Section 24.3.5.22 )
24.3.2 BSC
24.3.2.1 MC959 - NB_PS_CHAN_REQD
Definition Number of 48.058 CHANNEL REQUIRED (for packet service) received via
the selected cell.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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_G2_BSC,
NB_MSG_GSL_OUTPUT_BUFFER_XOFF_G2_BSC,
NB_MSG_GSL_OUTPUT_BUFFER_XON_MX_BSC and
NB_MSG_GSL_OUTPUT_BUFFER_XOFF_MX_BSC).
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Number of invalid 48.058 CHANNEL REQUIRED (for all establishment cause)
messages received by the BSC.
Trigger condition Upon reception of a 48.058 CHANNEL REQUIRED message from the BTS, the
BSC checks firstly the content of message. If an error is found, the received
48.058 CHANNEL REQUIRED message is discarded by the BSC.
The counter MC962 is incremented by one each time the received 48.058
CHANNEL REQUIRED message is discarded because one of the following
errors have been detected by the BSC:
1) The message syntax errors, for example (list non-exclusive):
1a) the message length is incorrect: i.e., the EGPRS Request Reference OIE is
not present, but the length of message does not equal to "10"; or the EGPRS
Request Reference OIE is present, but the length of message does not equal to
"13" (Note 1).
1b) the IE length is incorrect;
2) the Timeslot Number received in the CHANNEL REQUIRED message does
not equal to 0 or 2 (only timeslot 0 or 2 can be used as BCCH Timeslots).
3) The C-bits (C5, C4, C3, C2 & C1) of Channel Number MIE is not equal to the
coding 10001 "Uplink CCCH (RACH)".
4) In case where the GPRS service is allowed (EN_GPRS = TRUE) and the
GPRS service has already been activated in the cell: the BSC checks the
presence of EGPRS Request Reference optional IE. If this OIE is not included,
then the BSC checks the "RA (Random Access Reference)" byte in the 48.058
CHANNEL REQUIRED message : if the bits 8, 7 and 6 of "RA (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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Number of valid 48.058 CHANNEL REQUIRED message, received by the BSC,
indicating the location update in their "establishment cause".
Trigger condition MC964 is incremented to one whenever the "RA" octet (Octet 2 of Request
Reference IE) of valid 48.058 CHANNEL REQUIRED equals to "000xxxxx
(Location updating and the network does not set NECI bit to 1)".
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC142e=C142a+C142c
Trigger condition –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC142f=C142b+C142d
Trigger condition –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Number of SDCCH drops on SDCCH established phase due to radio link failure
(radio link timeout or Lapdm timer expiry).
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Trigger condition –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Number of TCH (in HR or FR usage) drops due to remote transcoder failures
(per TRX).
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment This counter is applicable for both G2 and Evolution BSC.
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
24.3.5 Handover
24.3.5.1 MC03 - NB_OUT_SDCCH_HO_SUCC
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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.
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 ACK 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 on the old channel between the
sending of the 48.058 CHANNEL ACTIVATION and the reception of the 48.058
CHANNEL ACTIVATION ACK 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 interface 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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Nb of outgoing TCH handover -preparation failures due to congestion, per TRX.
Intracell, internal intercell and external handovers are counted together. This
counter takes into account handovers from TCH in traffic or in signaling mode. It
does not take into account DTM Assignments.
MC711 = C711
Trigger condition 1) Intracell HO: Whenever an intra-cell TCH handover cannot be performed,
because there is no free TCH channel to allocate the handover to.
2) Internal inter-cell HO: Whenever a internal inter-cell TCH handover cannot be
performed, because there is no free TCH channel to allocate the handover to.
3) External HO: Whenever a 48.008 HANDOVER REQUIRED REJECT with
cause "no radio resource available" is received from the MSC by the serving
BSC for an outgoing external TCH HO.
Note : the counter will be incremented for external TCH HO if and only if the
parameter RESP_REQ is set to 1.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Number of incoming internal and external TCH (in HR or FR usage) handover
successes per TRX;
since there are no reliable means at the target BSC to distinguish external
directed retry from external handover, the external directed retries are counted
by this counter.
MC717b = C717b
Trigger condition 1) Internal inter-cell or external TCH handover: whenever a 44.018 HANDOVER
COMPLETE message is received on Abis interface from the target cell for a
TCH channel.
2) Intra-cell handover: whenever an 44.018 ASSIGNMENT COMPLETE
message is received on Abis interface on the target channel.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Number of incoming internal and external TCH (in HR or FR usage) handover
successes for speech 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 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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Nb of outgoing TCH handover successes for speech 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.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Number of intra-cell TCH (in HR or FR usage) handover successes for speech
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.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment This counter is applicable for both G2 and Evolution BSC.
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
Definition Number of BSS originating SCCP connection failures due to the NSS, when
A signaling over IP is used.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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
Sub Domain 2 A
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 A
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 A
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 A
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 A
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
24.3.7 LCS
24.3.7.1 MC923a - 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.
Sub Domain 2 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Trigger condition Whenever a 48.008 PERFORM LOCATION RESPONSE message is sent to the
MSC without including the OIE LCS Cause.
Sub Domain 2 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Trigger condition Whenever a BSSMAP-LE RESET message is received from the SMLC.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC196=C190+C191+C192+C193
Trigger condition –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC197=C194a+C194b+C194c+C195
Trigger condition –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
24.3.10 Speech
24.3.10.1 MC170 - 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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Number of TCH assigned using AMR-NB 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 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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
24.3.11 TCH
24.3.11.1 MC928a - NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_UL
Definition Number of TCH drops due to Cause 2 (Too low quality in UL).
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Number of TCH drops due to Cause 3 (Too low level in UL).
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Number of TCH drops due to Cause 4 (Too low quality on the downlink).
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Number of TCH drops due to Cause 5 (Too low level in DL).
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Number of TCH drops due to Cause 6 (Too long MS-BS distance).
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Number of TCH drops due to Cause 22 (Too short MS-BS distance).
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Number of TCH drops due to Cause 15 (Too high interference level on the
uplink).
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
24.3.11.8 MC928h -
NB_TCH_DROP_CAUSE_TOO_HIGH_INTERFERENCE_DOWNLINK
Definition Number of TCH drops due to Cause 16 (Too high interference level on the
downlink).
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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).
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Trigger condition –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition case: Location Update request (except the "follow on" procedure)
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Trigger condition –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Trigger condition 1) Whenever a 44.018 ASSIGNMENT COMMAND message for a normal TCH
assignment is sent to the MS. In case of multiband cell, only the first 44.018
ASSIGNMENT COMMAND message is counted (when sent in the inner zone);
the second 44.018 ASSIGNMENT COMMAND message sent in the outer zone
(further to the ASSIGNEMENT FAILURE received with the cause "protocol error
unspecified" in the inner zone) is not counted.
2) Whenever a 44.018 DTM ASSIGNMENT COMMAND message is sent to the
MS, containing the assignment of a TCH in signaling mode.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Trigger condition Whenever the timer supervising the Immediate Assignment Procedure (T3101)
expires during the establishment of an SDCCH sub-channel.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 2 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Trigger condition –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Trigger condition The counter is incremented upon the sending of 48.008 ASSIGNMENT
FAILURE (cause: "circuit pool mismatch")
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
24.4.2 Channel
24.4.2.1 MC141 - AV_NB_TCH_QUEUED
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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Average number of available TCH/PDCH timeslots for traffic usage (i.e. TCH (for
HR or FR usage) 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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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".
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Average number of busy TCH radio timeslot (in FR or HR usage, in traffic or in
signaling mode) and busy dynamic SDCCH/8 radio timeslot allocated as TCH.
Trigger condition The BSC takes periodically a sample of the number of busy TCH radio timeslots
and busy dynamic SDCCH/8 radio timeslots allocated as TCH. The sampling
period is set to the value indicated in the Status Inspection field. At the expiry of
the accumulation period, all samples are averaged (i.e. summed and divided
by the number of samples). The averaged value is rounded up or down to the
nearest value with an accuracy of 0.1.
A TCH radio timeslot is considered as busy during the time it is allocated to a
given MS for TCH traffic (in HR or FR usage). A dynamic SDCCH/8 timeslot
allocated as TCH is considered as busy during the time it is allocated to a given
MS for TCH traffic.
Note 1: the counter value that is indicated in the ASCII file (which can be
obtained via the OBSYNT interface) is an integer value (i.e. it is as if the BSC
multiplies by 10 the average). The reported value shall then be divided by 10
afterwards so that the value that is displayed to the end-user is the correct one.
Note 2: This counter does not take into account the PDCH radio timeslots
allocated to the MFS.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Trigger condition Whenever a TCH radio timeslot or a dynamic SDCCH/8 radio timeslot allocated
as TCH becomes busy, the BSC determines the current number of busy TCH
radio timeslots (in HR or FR usage) and busy dynamic SDCCH/8 radio timeslots
allocated as TCH. This counter is the maximum value of this number during the
accumulation period.
This counter does not take into account the PDCHs allocated to the MFS.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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].
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 nearest
integer value.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 nearest
integer value.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Average number of free TCH and free dynamic SDCCH/8 radio timeslots in FR
or HR usage belonging to the interference band 4. This number is updated upon
the receipt of 48.058 RF RESOURCE INDICATION.
Trigger condition 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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 nearest
integer value.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Cumulated time (in seconds) during which there is no free FR TCH sub-channel
to serve an incoming FR TCH request.
A TCH sub-channel is seen as busy:
i) if the TCH sub-channel is occupied by a HR or FR CS call (in particular if it is
occupied by the CS part of a DTM call), or
ii) if the TCH sub-channel is allocated to the MFS to carry PS traffic.
Trigger condition The counter is started when there is no free FR TCH sub-channel to serve an
incoming FR TCH request.
The counter is stopped when there is a free FR TCH sub-channel to serve
an incoming FR TCH request.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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).
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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).
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Trigger condition –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Trigger condition –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Trigger condition –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Average number of busy dynamic SDCCH/8 timeslots allocated as TCH (in FR or
HR usage). This counter takes into account TCH in traffic or in signaling mode.
Trigger condition The BSC takes periodically a sample of the number of busy dynamic SDCCH/8
timeslots allocated as TCH. The sampling period is set to the value indicated in
the Status Inspection field. At the expiry of the accumulation period, all samples
are averaged (i.e. summed and divided by the number of samples). The
averaged value is rounded up or down to the nearest value with an accuracy of
0.1.
A dynamic SDCCH/8 timeslot is considered as busy and allocated as TCH
during the time it is allocated to a given MS for TCH traffic (in FR or HR usage).
Note that the counter value that is indicated in the ASCII file (which can be
obtained via the OBSYNT interface) is an integer value (i.e. it is as if the BSC
multiplies by 10 the average). The reported value shall then be divided by 10
afterwards so that the value that is displayed to the end-user is the correct one
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Maximum number of busy dynamic SDCCH/8 timeslots allocated as TCH (in
FR or HR usage). This counter takes into account TCH in traffic or in signaling
mode.
Trigger condition Whenever a dynamic SDCCH/8 timeslot allocated as TCH becomes busy, the
BSC determines the current number of busy dynamic SDCCH/8 timeslots
allocated as TCH (in HR or FR usage). Counter MC801b is the maximum value
of this number during the accumulation period.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 A
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Trigger condition Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for data call.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
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).
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Number of TCH normal assignment requests for A5/3 capable mobiles.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Cumulated time during which a transmission power reduction of 1dB is applied
by the BTS on the downlink power-controlled GMSK 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) which are not transmitted on the BCCH frequency of the
cell.
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 1dB is applied by the BTS on the downlink
GMSK bursts (only the ones linked to TCHs, TBFs) of the TRX.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Cumulated time during which a transmission power reduction of 2dB is applied
by the BTS on the downlink power-controlled GMSK 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) which are not transmitted on the BCCH frequency of the
cell.
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 bursts (only the ones linked to TCHs, TBFs) of the TRX.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Cumulated time during which a transmission power reduction of 3dB is applied
by the BTS on the downlink power-controlled GMSK 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) which are not transmitted on the BCCH frequency of the
cell.
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 bursts (only the ones linked to TCHs, TBFs) of the TRX.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Cumulated time during which a transmission power reduction strictly higher than
3dB is applied by the BTS on the downlink power-controlled GMSK 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) which are not transmitted on the BCCH frequency of the
cell.
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 bursts (only the ones linked to TCHs, TBFs ) of the TRX.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 not already counted
in the TIME_PWR_RED_8PSK_1 and TIME_PWR_RED_GMSK_1 counters
corresponding either to signalling non-BCCH bursts (SDCCH/FACCH/SACCH)
or either bursts sent with the BCH frequency.
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 not already counted
in the TIME_PWR_RED_8PSK_2 and TIME_PWR_RED_GMSK_2 counters
corresponding either to signalling non-BCCH bursts (SDCCH/FACCH/SACCH)
or either bursts sent with the BCH frequency.
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 not already counted
in the TIME_PWR_RED_8PSK_3 and TIME_PWR_RED_GMSK_3 counters
corresponding either to signalling non-BCCH bursts (SDCCH/FACCH/SACCH)
or either bursts sent with the BCH frequency.
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 not already counted
in the TIME_PWR_RED_8PSK_4 and TIME_PWR_RED_GMSK_4 counters
corresponding either to signalling non-BCCH bursts (SDCCH/FACCH/SACCH)
or either bursts sent with the BCH frequency.
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 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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Cumulated time during which downlink power-controlled GMSK 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) which are not transmitted on the BCCH frequency of the
cell.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 burst linked to TCHs, TBFs (in GMSK mode)
is transmitted on the TRX.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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.
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
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.
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 2 –
Sub Domain 3 –
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.
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 3 –
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.
Sub Domain 2 –
Sub Domain 3 –
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 -100C to -1C
100 represent 0C
101 to 254 represent positive temperatur from 1C to 154C
255 represent an invalid value (no measurement available over the whole
accumulation period)
24.6.2 BSC
24.6.2.1 MC926 - 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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Trigger condition Each time the BSC application server (AS) sends an ASPUP to any MSC, this
counter is incremented by one.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Trigger condition Each time the BSC application server (AS) sends an ASPDOWN to any MSC,
this counter is incremented by one.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Trigger condition Each time the BSC application server (AS) sends an ASPACTIVE to any MSC,
this counter is incremented by one.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Trigger condition Each time the BSC application server (AS) sends an ASPINACTIVE to any
MSC, this counter is incremented by one.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Number of CONNECTION REQUEST received from the MSC by the BSC, when
A signaling over IP is used.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Number of CONNECTION REFUSED received from the MSC by the BSC, when
A signaling over IP is used..
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition MC350=C253+C254
Trigger condition –
Sub Domain 2 A
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC351=C255+C256
Trigger condition –
Sub Domain 2 A
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 2 A
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Time (in seconds) during which the TCH radio timeslot in FR usage is busy
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Time (in seconds) during which the TCH radio timeslot in HR usage is busy
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition Time (in seconds) during which the TCH radio timeslot or dynamic SDCCH/8
timeslot in the GSM frequency band is busy in FR usage. This counter takes
into account TCH in traffic or in signaling mode.
Trigger condition 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. For
each channel allocation: The counter starts being incremented after the sending
of the 48.058 CHANNEL ACTIVATION message to the cell concerning a full rate
TCH channel for the related TRX timeslot. The counter stops being incremented
after the reception of a 48.058 RF CHANNEL RELEASE ACKNOWLEDGE
message or the expiry of timer T_RCR_ACK twice (after the sending of the
48.058 RF CHANNEL RELEASE message) concerning the TCH channel
previously activated on the related TRX timeslot.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Time (in seconds) during which the TCH radio timeslot or dynamic SDCCH/8
timeslot in the GSM frequency band is busy in HR usage.
Trigger condition The counter cumulates over the Accumulation Period, per radio timeslot, all unit
times during which the TCH HR channel in the GSM frequency band is busy.
For each channel allocation: The counter starts being incremented after the
sending of the 48.058 CHANNEL ACTIVATION message to the cell concerning
a half rate TCH channel for the related TRX timeslot. The counter stops
being incremented after the reception of a 48.058 RF CHANNEL RELEASE
ACKNOWLEDGE message or the expiry of timer T_RCR_ACK twice (after the
sending of the 48.058 RF CHANNEL RELEASE message) concerning the TCH
channel previously activated on the related TRX timeslot.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Time (in seconds) during which the TCH radio timeslot or dynamic SDCCH/8
timeslot in the DCS/PCS frequency band is busy in FR usage. This counter
takes into account TCH in traffic or in signaling mode.
Trigger condition The counter cumulates over the Accumulation Period, per radio timeslot, all
unit times during which the TCH FR channel in the DCS/PCS frequency band
is busy. For each channel allocation: The counter starts being incremented
after the sending of the 48.058 CHANNEL ACTIVATION message to the
cell concerning a full rate TCH channel for the related TRX timeslot. The
counter stops being incremented after the reception of a 48.058 RF CHANNEL
RELEASE ACKNOWLEDGE message or the expiry of timer T_RCR_ACK twice
(after the sending of the 48.058 RF CHANNEL RELEASE message) concerning
the TCH channel previously activated on the related TRX timeslot.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Time (in seconds) during which the TCH radio timeslot or dynamic SDCCH/8
timeslot in the DCS/PCS frequency band is busy in HR usage.
Trigger condition The counter cumulates over the Accumulation Period, per radio timeslot, all
unit times during which the TCH HR channel in the DCS/PCS frequency band
is busy. For each channel allocation: The counter starts being incremented
after the sending of the 48.058 CHANNEL ACTIVATION message to the
cell concerning a half rate TCH channel for the related TRX timeslot. The
counter stops being incremented after the reception of a 48.058 RF CHANNEL
RELEASE ACKNOWLEDGE message or the expiry of timer T_RCR_ACK twice
(after the sending of the 48.058 RF CHANNEL RELEASE message) concerning
the TCH channel previously activated on the related TRX timeslot.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Number of Channel Request messages with access cause "One phase packet
access with request for single timeslot uplink transmission" received by the BSS.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Number of Immediate Assignment messages sent on AGCH for GPRS traffic.
Trigger condition Whenever a BSCGP Channel Assignment Downlink message is received for
MS in non-DRX mode.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Definition Number of Immediate Assignment messages sent on PCH for GPRS traffic.
Trigger condition Whenever a BSCGP Channel Assignment Downlink message is received for
MS in DRX mode.
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Trigger condition –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
Definition Number of useful blocks sent on AGCH channel (The dummy blocks are not
counted).
Sub Domain 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 2 –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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, 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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC144e=C144a+C144c
Trigger condition –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Definition MC144f=C144b+C144d
Trigger condition –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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.
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
Feature Name –
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
Sub Domain 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
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 3 –
Type Definition Set of global counters providing an overview of each measurement type
External Comment –
25.2 Adjacency
25.2.1 All Adjacency
C400 - NB_ADJ_BSC_INC_HO_REQ (Section 25.2.2.1 )
C401 - NB_ADJ_BSC_INC_HO_ATPT (Section 25.2.2.2 )
C402 - NB_ADJ_BSC_INC_HO_SUCC (Section 25.2.2.3 )
25.2.2 BSC
25.2.2.1 C400 - NB_ADJ_BSC_INC_HO_REQ
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 2 –
Sub Domain 3 –
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 –
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 2 –
Sub Domain 3 –
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 –
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 2 –
Sub Domain 3 –
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 –
26 MFS-GPRS Counters
Trigger Condition Whenever an Info frame is retransmitted on the logical LapD link.
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 /
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.
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 /
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.
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 /
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.
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 /
26.2.3 Gb interface
26.2.3.1 P3a - 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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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".
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
26.2.4 GSL
26.2.4.1 P7a - NB_BSCGP_MSG_SENT
Trigger Condition The counter is incremented each time a BSCGP message sent by the MFS to
the BSC.
External Comment –
Feature Name /
Trigger Condition Each time a BSCGP message sent by MFS is discarded, the counter is
incremented.
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
Trigger Condition The counter is incremented each time a BSCGP CHANNEL REQUEST, DTM
REQUEST messages are received by the MFS from the BSC.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
Trigger Condition The counter is incremented whenever a DL TBF establishment fails due to:
1) a too low number of available GCH.
For BTS evolium :
The number of GCH available (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:
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 be incremented for RT PFCs.
The counter is incremented at the expiry of the PDU lifetime when the last attempt
to establish the DL TBF has failed due to too low number of available GCH (too
many TBF on the TRX compared to the number of available GCH) or due to the
MAX_TBF_TRX_DL_GP[U] constraint.
External Comment –
Trigger Condition The counter is incremented whenever a UL TBF establishment fails due to:
1) a too low number of available GCH.
For BTS evolium :
The number of GCH available (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:
For BTS evolium :
The MAX_TBF_TRX_UL_GP[U] limit is reached on all the TRXs available for PS
traffic in the cell.
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
Trigger Condition –
External Comment –
Feature Name /
Trigger Condition –
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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).
External Comment –
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).
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
Trigger Condition Within the granularity period, this counter counts the number of
RAN_INFORMATION_REQUEST received from a eNodeB (both single and
multiple reports).
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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.
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 /
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.
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 /
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.
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 /
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.
External Comment –
Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)
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.
External Comment –
Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)
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.
External Comment –
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.
External Comment –
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.
External Comment –
Feature Name /
Trigger Condition - incremented, in the target cell, when a RT-PFC is forwarded from another cell
following a cell reselection.
External Comment –
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
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 /
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 .
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 /
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 .
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 /
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.
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 /
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 .
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 /
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 .
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 /
Trigger Condition When a CS pre-emption is detected, RRM-PCC increments the counter each
time a RT-PFC is impacted.
External Comment –
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.
External Comment –
Feature Name /
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.
External Comment –
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.
External Comment –
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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
External Comment –
Feature Name /
External Comment –
Feature Name /
External Comment –
Feature Name /
External Comment –
Feature Name /
External Comment –
Feature Name /
External Comment –
Feature Name /
26.2.5.64 P302c_4 -
NB_UL_TBF_REL_DUE_TO_RADIO_FAILURE_N_POLLING_EUTM
External Comment –
Feature Name /
External Comment –
Feature Name /
External Comment –
Feature Name /
External Comment –
Feature Name /
Trigger Condition When the TBF start indication is received during an UL TBF establishment on
PACCH.
External Comment –
Feature Name /
External Comment –
Feature Name /
Trigger Condition When the TBF start indication is received during an UL TBF establishment in
EGPRS mode on PACCH.
External Comment –
Feature Name /
Definition Number of DL TBF releases because the transmit window has been stagnating
for too long a time.
External Comment –
Feature Name /
Definition Number of UL TBF releases because the receive window has been stagnating
for too long a time.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment Note that NC2 cell reselections can only be triggered if the MS is in packet transfer
mode
Feature Name /
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).
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 3 T1
External Comment –
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 3 T2
External Comment –
Feature Name /
Definition Number of downlink TBFs for which the corresponding Mobile Station was
candidate for resource reallocation upon T_CANDIDATE_TBF_REALLOC expiry
(due to trigger T3). Only candidate MSs for which the resource allocation algorithm
was called are taken into account.
Sub Domain 3 T3
External Comment –
Feature Name /
Definition Number of downlink TBFs for which the corresponding Mobile Station was
candidate for resource reallocation upon T_CANDIDATE_TBF_REALLOC expiry
(due to Trigger T4). Only candidate MSs for which the resource allocation
algorithm was called are taken into account.
Sub Domain 3 T4
External Comment –
Feature Name /
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 3 T1
External Comment –
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 3 T2
External Comment –
Feature Name /
Definition Number of uplink TBFs for which the corresponding Mobile Station was candidate
for resource reallocation upon T_CANDIDATE_TBF_REALLOC expiry (due to
trigger T3). Only candidate MSs for which the resource allocation algorithm was
called are taken into account.
Sub Domain 3 T3
External Comment –
Feature Name /
Definition Number of uplink TBFs for which the corresponding Mobile Station was candidate
for resource reallocation upon T_CANDIDATE_TBF_REALLOC expiry (due to
Trigger T4). Only candidate MSs for which the resource allocation algorithm was
called are taken into account.
Sub Domain 3 T4
External Comment –
Feature Name /
Sub Domain 3 T1
External Comment –
Feature Name /
Sub Domain 3 T2
External Comment –
Feature Name /
Sub Domain 3 T3
External Comment –
Feature Name /
Sub Domain 3 T4
External Comment The counter can be used to compute the success rate of the reallocation execution
phase.
Feature Name /
Sub Domain 3 T1
External Comment –
Feature Name /
Sub Domain 3 T2
External Comment –
Feature Name /
Sub Domain 3 T3
External Comment –
Feature Name /
Sub Domain 3 T4
External Comment The counter can be used to compute the success rate of the reallocation execution
phase.
Feature Name /
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 3 T1
External Comment –
Feature Name /
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 3 T2
External Comment –
Feature Name /
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 3 T3
External Comment –
Feature Name /
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 3 T4
External Comment –
Feature Name /
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 3 T1
External Comment –
Feature Name /
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.
Sub Domain 3 T2
External Comment –
Feature Name /
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 3 T3
External Comment –
Feature Name /
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 3 T4
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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 3 T1
External Comment –
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 3 T2
External Comment –
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 3 T3
External Comment –
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 3 T4
External Comment –
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 3 T1
External Comment –
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 3 T2
External Comment –
Feature Name /
Definition Number of periodic attempts for uplink TBFs which were candidate for resource
reallocation due to T3 but for which no candidate allocation could be found apart
from their current allocation. The uplink TBFs were therefore not reallocated.
Trigger Condition The counter is incremented each time an uplink TBF is candidate for resource
reallocation due to T3 but after the radio resource reallocation algorithm is run,
it is decided not to change its current allocation. As such, it corresponds to a
resource reallocation preparation failure.
Sub Domain 3 T3
External Comment –
Feature Name /
Definition Number of periodic attempts for uplink TBFs which were candidate for T4 resource
reallocation but for which no suitable candidate allocation could be found apart
from their current allocation. The uplink TBFs were therefore not re-allocated.
Trigger Condition The counter is incremented each time an uplink TBF is candidate for resource
reallocation due to Trigger T4 but after the radio resource reallocation algorithm is
run, it is decided not to change its current allocation. As such, it corresponds to a
resource reallocation preparation failure.
Sub Domain 3 T4
External Comment –
Feature Name /
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 3 T1
External Comment –
Feature Name /
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 3 T2
External Comment –
Feature Name /
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 3 T3
External Comment –
Feature Name /
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 3 T4
External Comment –
Feature Name /
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 3 T1
External Comment –
Feature Name /
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).
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 3 T2
External Comment –
Feature Name /
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 3 T3
External Comment –
Feature Name /
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 3 T4
External Comment –
Feature Name /
Trigger Condition Tide mark recording the maximum value of Counter P209
External Comment –
Feature Name /
Trigger Condition Tide mark recording the minimum value of Counter P209
External Comment –
Feature Name /
Trigger Condition Tide mark recording the maximum value of Counter P210
External Comment –
Feature Name /
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
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
Definition Number of NC2 cell reselection requests for a MS in packet transfer mode due to
a "detection of a better neighbour cell" (Cause PT2)
Trigger Condition 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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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".
External Comment –
Feature Name /
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".
External Comment –
Feature Name /
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
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
External Comment –
Feature Name /
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.
External Comment –
Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)
Trigger Condition In NC0 mode : Whenever neighbour (P)SI messages are sent by RRM to RLC
following a reception of PACKET CELL CHANGE
External Comment –
Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)
Trigger Condition Tide mark recording the maximum value of Counter P212.
External Comment –
Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)
Trigger Condition Tide mark recording the minimum value of Counter P212.
External Comment –
Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)
External Comment –
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".
External Comment –
Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)
External Comment –
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
Definition Number of time the BSS cannot get the PFC characteristics from SGSN
External Comment –
Trigger Condition Incremented by RRM-PCC each time a PFC-CREATION is received and the PFC
is either a streaming or a conversational.
External Comment –
Trigger Condition Incremented by RRM-PCC each time a PFC-CREATION is received and the PFC
is either a background or an interactive.
External Comment –
External Comment –
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.
External Comment –
External Comment –
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.
External Comment –
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).
External Comment –
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)
External Comment –
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.
External Comment –
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.
External Comment –
Feature Name /
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.
External Comment –
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).
External Comment –
Feature Name /
Trigger Condition This counter is incremented when MFS receives the BSCGP DTM Request
message.
External Comment –
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.
External Comment –
Feature Name /
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.
External Comment –
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.
External Comment –
Feature Name /
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.
External Comment –
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.
External Comment –
Feature Name /
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.
External Comment –
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.
External Comment –
Feature Name /
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
Definition Number of RT PFC downgraded to Best Effort for a DTM MS in dedicated mode.
External Comment –
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.
External Comment –
Definition Number of RT PFC downgraded to Best Effort for a DTM MS in DTM mode.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
Trigger Condition Each time a DL or UL RT PFC is refused due to a lack of radio resource , this
counter is incremented.
External Comment –
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.
External Comment –
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 .
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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).
External Comment –
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.
External Comment –
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.)
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.)
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
26.2.5.201 P9 - NB_DL_TBF_NORM_REL
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.
External Comment –
Feature Name /
External Comment –
Feature Name /
External Comment –
Feature Name /
External Comment –
Feature Name /
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
External Comment –
Feature Name /
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
External Comment –
Feature Name /
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
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).
External Comment –
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:
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.
External Comment –
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.
External Comment –
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.
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.
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.
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.
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.
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
Definition Atermux congestion duration (in seconds) due to a lack of Ater nibbles on the
Atermux interface.
External Comment –
Feature Name /
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
External Comment –
Feature Name /
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
26.3.4 Gb interface
26.3.4.1 P33 - TIME_BEAR_CHAN_NOT_AVAIL
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).
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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".
External Comment –
26.3.4.4 P4 - 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).
External Comment –
Feature Name /
26.3.4.5 P5 - TIME_PVC_CONG_LEVEL1
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).
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
Definition Time during which the DL TBF establishment is impossible due to congestion
(no radio resource in the MFS).
External Comment –
Definition Cumulated overall time (i.e. active and delayed) of DL TBF connections.
Trigger Condition The counter measures the cumulated time duration of all DL TBF connections in
the cell over the Granularity period.
Active as well as delayed release periods are taken into account.
Each time duration starts upon reception from the Mobile Station of 04.60 PACKET
CONTROL ACKNOWLEDGMENT on PACCH/U during the DL TBF establishment
procedure (either in response to a PACKET DOWNLINK ASSIGNMENT or
PACKET TIMESLOT RECONFIGURE, whichever is applicable).
In case of normal DL TBF releases, the counter stops for a given DL TBF upon
reception of the reply to the 04.60 RLC DATA BLOCK (FBI=1, polling) sent by the
MFS for the last RLC block to send, i.e. 04.60 (EGPRS) PACKET DOWNLINK
ACK/NACK from the MS and there is no retransmission required, if the TBF was in
RLC acknowledged mode or 04.60 PACKET CONTROL ACK if the TBF was in
RLC unacknowledged mode. This last RLC data block is the last actual data block
of the TBF, i.e. the last useful RLC data block for a TBF in normal release mode,
or the last dummy RLC data block for a TBF in delayed release mode.
In case of abnormal DL TBF releases during active phase (i.e. not delayed phase),
the counter stops for a given DL TBF:
- at the time when the RRM layer has received the acknowledgment of the last DL
LLC PDU (in case of RLC acknowledged mode), or,
- at the time when the RRM layer has sent the last DL LLC PDU to the RLC layer
(in case of RLC unacknowledged mode).
In case of abnormal DL TBF releases during delayed phase, the counter stops for
a given DL TBF at the time when the RRM layer has been informed that the DL
TBF has entered the delayed phase.
The case the DL TBF is released due to a NC cell reselection is managed as an
abnormal DL TBF release.
The time is provided in seconds with one significant value after the comma (I.e.
ROUND(10x)/10).
The DL TBFs still established at the expiration of the granularity period are not
taken into account in the cumulated value. They are taken into account only
when the DL TBFs are released. In case of traffic profile including a lot of "very
long" TBF, this may lead to a temporary under-estimated (then over-estimated)
cumulated value.
External Comment –
Feature Name /
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.
External Comment –
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.
External Comment –
Feature Name /
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.
External Comment –
Definition Number of uplink TBF establishment requests requesting 2 or 3 slots which are
totally satisfied at once by the initial allocation..
Trigger Condition Whenever the MFS allocates exactly 2 PDCHs (or 3 PDCHs) for an UL TBF in
case of an MS requesting 2 slots UL (or 3 slots UL).
When determining the number of timeslots requested by the mobile station for the
UL TBF, the MFS takes into 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.
External Comment –
Feature Name /
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.
External Comment –
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.
External Comment –
Feature Name /
Definition Time during which the UL TBF establishment is impossible due to congestion
(no radio resource in the MFS).
External Comment –
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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.
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 /
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.
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 /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
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
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.
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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 :
External Comment –
Feature Name /
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).
External Comment –
Trigger Condition An internal counter tracks the current number of used slave PDCH in the cell. This
internal counter is
- Incremented when one UL or DL TBF is carried by a salve PDCH.
- Decremented when no UL or DL TBF is carried by a slave PDCH.
Whenever this internal counter is incremented, its new value is compared with the
stored maximum number of
used PDCHs in the cell. If this value is higher than the stored maximum value, the
value becomes the new maximum.
The master PDCHs are excluded from this counter.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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 .
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
26.4.3 Gb interface
26.4.3.1 P180a - NB_SGSN_SELECTION_NSF
Trigger Condition Each time a SGSN is selected by the Node Selection Function and whatever the
cause of the selection, this counter is incremented.
External Comment –
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.
External Comment –
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.
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
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.
External Comment –
Feature Name /
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.
External Comment –
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.
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
26.4.4 IP interface
26.4.4.1 P541a - 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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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).
External Comment –
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.
External Comment –
Feature Name /
Definition Number of LLC PDU transferred (UL+ DL), Sum of P74 and P75 (cell counters) for
each cells mapped on GPU.
Trigger Condition –
External Comment –
Feature Name /
Definition This counter cumulates the time during which at least a DSP is in CPU load state.
Trigger Condition During the granularity period, the cumulated time during which at least a DSP is
loaded is computed.
The time is provided in seconds with one significant value after the comma (i.e.
ROUND(10x) / 10).
Note :
A DSP is said loaded when its CPU load is > =DSP_LOAD_THR1 and <
DSP_LOAD_THR2.
External Comment –
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.
External Comment –
Definition This counter cumulates the time during which at least a DSP is in CPU overload
state.
Trigger Condition During the granularity period, the cumulated time during which at least a DSP is
overloaded is computed.
The time is provided in seconds with one significant value after the comma (i.e.
ROUND(10x) / 10).
Note :
A DSP is said overloaded when its CPU load is > =DSP_LOAD_THR2.
External Comment –
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.
External Comment –
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
Trigger Condition Detected transitions from SI=0 to SI=1 for an EGPRS uplink TBF (stall indications
from the MS).
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
Trigger Condition Each time TX_EFFICIENCY is tested on a DL TBF established in GPRS mode.
External Comment –
Feature Name /
Trigger Condition Each time TX_EFFICIENCY is tested on an UL TBF established in GPRS mode.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
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.
External Comment –
Trigger Condition The counter cumulates the time when a GPU has stepped into the first level of
buffer congestion.
External Comment –
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.
External Comment –
Trigger Condition Whenever a CS Paging message is sent on (DL) PACCH the counter is
incremented.
External Comment –
External Comment –
Feature Name /
External Comment –
Feature Name /
Trigger Condition Whenever a CS paging request with GLOBAL_CN_ID IE is received from the
SGSN.
Note: P391b is also incremented.
External Comment –
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.
External Comment –
Feature Name /
Definition Maximum number of active contexts of MS (in RRM) observed during the
granularity period.
External Comment –
Feature Name /
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).
External Comment –
Feature Name /
External Comment –
Feature Name /
External Comment –
Feature Name /
Definition Cumulative time during which the GPU stays in the PPC CPU overload state due
to PPC CPU power limitations.
External Comment –
Feature Name /
Definition Number of (E)GPRS sessions. A session corresponds to a mobile station and the
BSS exchanging packet data using downlink TBFs, uplink TBFs or both. There is
always at least one TBF active across the whole duration of a session or T3192 is
running.
Trigger Condition A (E)GPRS session starts when for one mobile station, there was no on-going
TBF and one TBF is established. It ends when for that mobile station, there was
one (or two) on-going TBF(s) and one (or both) is (are) released and T3192 is no
longer running. During a session, TBFs may be established and released in both
directions provided there is always at least one direction for which there is an
on-going TBF or T3192 is running.
The detailed triggers are described below:
1) if an MS has got no TBF established and a DL or UL TBF is established then
the session starts when the first RLC data block is sent or received on that TBF;
2) in case an MS has got an UL TBF only, the current session ends when the
last UL RLC data block is received (and no retransmission is required in RLC
acknowledged mode);
3) in case an MS has got a DL TBF only, the current session ends when the final
(EGPRS) PACKET DOWNLINK ACK/NACK is received and no retransmission is
required in RLC acknowledged mode, if T3192 is not started (i.e. T3192 = 0);
4) in case an MS has got a DL TBF only, the final (EGPS) PACKET DOWNLINK
ACK/NACK is received and no retransmission is required in RLC acknowledged
mode, if T3192 is started, the session continues;
5) in case an MS has got a DL (resp UL) TBF on-going and an UL (resp DL) TBF
is established, then the session continues;
6) in case an MS has got both a DL and an UL TBFs on-going and one of the
TBFs gets released, then the session continues;
7) in case an MS has got both a DL and an UL TBFs on-going and both TBFs
are released at the same time, but the timer T3192 is started, then the session
continues (otherwise if T3192=0, then the session ends);
8) in case an MS has got no TBF established, T3192 is running and reaches its
expiry value, the session ends.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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".
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Definition Signalling load induced in the cell by the procedure of broadcast of (P)SI messages
External Comment –
Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)
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.
External Comment –
Feature Name Enhanced packet cell reselection (NACC and Packet SI Status)
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.
External Comment –
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
Definition Number of MS contexts created for MS whose multislot class belongs to the set
of multislot classes 11 to 12.
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
Definition Number of MS contexts created for MS whose DTM high multislot class belongs
to 31-33.
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,
External Comment –
Feature Name /
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, ...)
External Comment –
Feature Name /
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, ...)
External Comment –
Feature Name /
External Comment –
Feature Name /
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.
External Comment –
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
Definition Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH
encoded in MCS-7.
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
External Comment –
Feature Name /
Definition Average PMU CPU power budget observed during the granularity period.
Trigger Condition The counter is the average value of all the samples of the PMU CPU power budget
over the granularity period.
External Comment –
Feature Name /
Definition Maximum value of the PMU CPU power budget observed during the granularity
period.
External Comment –
Feature Name /
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.
External Comment –
Feature Name /
Trigger Condition Flush message received in the serving cell with rerouting conditions not fulfilled.
External Comment –
Feature Name /
Definition Number of DL LLC bytes rerouted (i.e. received) from another cell.
External Comment –
Feature Name /
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".
External Comment –
Feature Name /
27 MFS-LCS Counters
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"
External Comment –
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.
External Comment –
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).
External Comment –
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".
External Comment –
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".
External Comment –
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".
External Comment –
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".
External Comment –
Trigger Condition Incremented each times a geographical location is processed using PCF "CI+TA"
External Comment –
Trigger Condition Incremented each times "CI+TA" PCF algorithm returns a positioning estimation
without error indications.
External Comment –
Trigger Condition Incremented each times a location estimate is performed in the SMLC using PCF
"Conventional GPS".
External Comment –
Trigger Condition Incremented each times a location estimate is performed in the SMLC using PCF
"MS assisted GPS".
External Comment –
Trigger Condition Incremented each times the PCF "MS-assisted A-GPS" returns a position estimate
without error indications.
External Comment –
Trigger Condition Incremented each times a location estimate is performed in the SMLC using PCF
"MS-based A-GPS".
External Comment –
Trigger Condition Incremented each times PCF "MS-based A-GPS" returns a position estimate
with no error indication.
External Comment –
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
External Comment –
Definition Number of failed LCS procedures (considering LCS requests for MS positioning
and LCS requests for GPS assistance data) due to intra-BSC handover.
External Comment –
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.
External Comment –
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.
External Comment –
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)
External Comment –
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
External Comment –
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.
External Comment –
Trigger Condition Incremented each times "Conventional GPS" PCF returns a position estimation
without error indication.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
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.
External Comment –
Definition Standard deviation of the latitude of the mobile stations obtained with TA
positioning PCF
External Comment –
Definition Standard deviation of the longitude of the mobile stations obtained with TA
positioning PCF
External Comment –
Definition Standard deviation of the latitude of the mobile stations obtained with Conventional
GPS PCF
External Comment –
Definition Standard deviation of the longitude of the mobile stations obtained with
Conventional GPS PCF
External Comment –
Definition Standard deviation of the latitude of the mobile stations obtained with MS Assisted
A-GPS PCF
External Comment –
Definition Standard deviation of the longitude of the mobile stations obtained with MS
Assisted A-GPS PCF
External Comment –
Definition Standard deviation of the latitude of the mobile stations obtained with MS Based
A-GPS PCF
External Comment –
Definition Standard deviation of the longitude of the mobile stations obtained with MS Based
A-GPS PCF
External Comment –