Alcatel BSC Counters Catalogue - B10

Alcatel-Lucent
15/01/2009
BSC COUNTERS
CATALOGUE B10
Edition: 13 Released BSC Counters Catalogue 3BK 11203 0135 DSZZA
Alcatel-Lucent
Type number: Counter - 1
Type name: Traffic measurements
Type scope (per BSS): One or several cells
Candidate for Standard No
Type limitations (per BSS):
1) The union of all observed cells per BSS for the detailed measurement types 1, 2, 3, 4, 5, 6, 19 (if
used as Detailed), 26, 28 (if used as Detailed), 29 (if used as Detailed), 31 (if used as detailed), 34 (if
used as Detailed) must not exceed 40 cells.
Type definition:
Set of counters related to the traffic evaluation per telecom procedures
C01 Type 1 : Traffic measurements
Counter Name : NB_IMM_ASS_SUCC_MT Counter Integer
SFD reference : No reference. Length: 4
Data collection Cumulative Measured number
Release Measured object Package
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure (QoS)
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
Counter definition:
Number of immediate assignment plus SDCCH normal assignment successes for Mobile Terminating procedure.
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION message is received from a CELL, with the L3_INFORMATION
field including a 44.018 PAGING RESPONSE message.
External comment:
--
Edition: 13 Released BSC Counters Catalogue 3BK 11203 0135 DSZZA Page 2
Alcatel-Lucent
Counter Name : NB_IMM_ASS_SUCC_MO Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of immediate assignment successes for Mobile Originating procedure.

MC02 = C02 = C02a+C02b+C02c+C02d+C02e+C02f+C02g+C02h+C02i.
The following counters C02a/b/c/d/e/f/g/h/i provide the distribution of the MO telecom procedures on SDCCH.
Trigger condition:
External comment:
--
C02a Type 1 : Traffic measurements
Counter Name : NB_IMM_ASS_SUCC_MO_LOC_UPD Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
case: Location Update request (except the "follow on" procedure)
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION message is received from a cell, with the L3 INFORMATION field
containing a 44.018 L3 message with an MIE message type set to LOCATION UPDATING REQUEST and with
an
MIE Location updating type not set to a RESERVED value and a bit FOR set to 0.
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.
External comment:
--
Alcatel-Lucent
C02b Type 1 : Traffic measurements
Counter Name : NB_IMM_ASS_SUCC_MO_SMS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
case: SMS procedure on SDCCH
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION message is received from a CELL, with the L3 INFORMATION
field
containing a 44.018 L3 message with an MIE message type set to CM SERVICE REQUEST and with an MIE
CM service type set to "SMS".
External comment:
--
C02c Type 1 : Traffic measurements
Counter Name : NB_IMM_ASS_SUCC_MO_SUP_SERV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
case: Supplementary Service
Trigger condition:
field
CM service type set to "Supplementary Service".
External comment:
--
Alcatel-Lucent
C02d Type 1 : Traffic measurements
Counter Name : NB_IMM_ASS_SUCC_MO_FOLLOW_ON Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
case: Location Update request ("follow on" procedure)
Trigger condition:
field
an MIE Location updating type not set to a RESERVED value and a bit FOR set to 1.
External comment:
--
C02e Type 1 : Traffic measurements
Counter Name : NB_IMM_ASS_SUCC_MO_CM_REEST Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
case: CM Re-establishment procedure
Trigger condition:
field
containing a 44.018 L3 message with an MIE message type set to CM RE-ESTABLISHMENT REQUEST
message.
External comment:
--
Alcatel-Lucent
C02f Type 1 : Traffic measurements
Counter Name : NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC02f=C02f, number of immediate assignment successes for Mobile Originationg procedure, in case of L3 Info
(within 48.058 ESTABLISH INDICATION) unknown by the BSC but transferred to the MSC.
Trigger condition:
External comment:
--
C02g Type 1 : Traffic measurements
Counter Name : NB_IMM_ASS_SUCC_MO_IMSI_DETACH Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC02g=C02g, number of immediate assignment successes for Mobile Originationg procedure, in case of IMSI
Detach Indication.
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION message is received from a CELL, with L3_INFORMATION field
containing a 44.018 L3 message with an MIE message type set to IMSI DETACH INDICATION. This counter is
incremented only if the L3 info message received has to be forwarded to the MSC.
External comment:
--
Alcatel-Lucent
C02h Type 1 : Traffic measurements
Counter Name : NB_IMM_ASS_SUCC_MO_CALL_EST Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
case: normal or emergency call establishment
Trigger condition:
field
containg a 44.018 L3 message with an MIE message type set to CM SERVICE REQUEST and an MIE CM
service type set to either :
- "emergency call establishment",
- or "mobile originating call establishment"
External comment:
--
C02i Type 1 : Traffic measurements
Counter Name : NB_IMM_ASS_SUCC_MO_LCS Counter Integer
SFD reference : 3BK 10204 0540 DTZZA ("Location services (LCS)") Length: 4
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
case: Mobile originated LCS procedure on SDCCH
Trigger condition:
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
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_SDCCH_HO_SUCC Counter Integer
SFD reference : 3BK 10204 0413 DSZZA ("PM Counters Improvements in B6") Length: 4
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: SDCCH
Counter definition:
MC03=C03, Number of outgoing SDCCH handover (any kind) successes.
Trigger condition:
External SDCCH handover in the following cases:
1/ 48.008 CLEAR COMMAND (cause= "handover successful") is received on the serving BSC.
2/ 48.008 CLEAR COMMAND (cause= "normal event/call control") received while T8 is running.

Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Counter Name : NB_IMM_ASS_PREP_FAIL_CONG Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Domain: Quality of Service Sub domain-3: Failure
Counter definition:
MC04=C04, number of immediate assignment preparation failures due to congestion.
Trigger condition:
All SDCCH sub-channels in the required cell were either Busy or Out of Service, when the 48.058 CHANNEL
REQUIRED message was received.
External comment:
--
Alcatel-Lucent
Counter Name : NB_SDCCH_DROP_OUT_HO Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter 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.
External comment:
--
Counter Name : NB_INC_SDCCH_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter definition:
MC10=C10, Number of incoming SDCCH handover (any kind) successes.
Trigger condition:
Internal inter-cell or external SDCCH handover: whenever a 44.018 HANDOVER COMPLETE message is
received
on Abis interface from the target cell for an SDCCH Sub-channel.

External comment:
--
Alcatel-Lucent
Counter Name : NB_SDCCH_DROP_EST_PHAS_BSS_PB Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Established Phase
Sub domain-2: SDCCH
Counter definition:
MC137=C137, Number of SDCCH drops in SDCCH established phase due to BSS problem.It may happen that
several causes of failures mentioned below are detected consecutively. In that case, the counter will only be
incremented once, as soon as the call is released.
Trigger condition:
1) LapD failure detected during the stable phase of an SDCCH transaction.
2) SDCCH was released due to 48.058 ERROR REPORT with any cause value being received during the stable
phase of an SDCCH transaction.
3) Telecom Supervisory module caused the call to be cleared.
4) SDCCH was released due to 0180 CLEAR_CMD message being received from BSSAPduring the stable phase
of an SDCCH transaction : O&M has disabled the DTC
External comment:
--
Alcatel-Lucent
Counter Name : NB_SDCCH_DROP_EST_PHAS_RLF Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter definition:
Number of SDCCH drops on SDCCH established phase due to radio link failure (radio link timeout or Lapdm timer
expiry).
Trigger condition:
1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "radio link failure" is
received on Abis interface for an SDCCH channel.
2) Whenever an 48.058 ERROR INDICATION message is received on Abis interface and leads to a loss of
channel.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_QUEUED Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure (Traffic Load)
Sub domain-2: Normal Assignment
Domain: Traffic Load Sub domain-3:
Counter 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".
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_TCH_HO_QUEUED Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Handover
Domain: Traffic Load Sub domain-3: TCH
Counter 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:
ii) when the handover request is queued in the cell if the queuing is not authorised by the MSC and the request

Note: MC13b = C13b

External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_SDCCH_HO_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Domain: Traffic Load Sub domain-3: SDCCH
Counter definition:
MC147=C147, Number of incoming internal or external SDCCH handovers -whose target SDCCH channel is
allocated by the BSC.
Trigger condition:
Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent on Abis Interface to activate an
SDCCH
channel for any handover purposes.

External comment:
--
Counter Name : NB_IMM_ASS_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of immediate assignment plus SDCCH normal assignments -whose SDCCH channel is allocated by the
BSC.
Trigger condition:
SDCCH
channel for any purpose other than handover.
External comment:
--
Alcatel-Lucent
Counter Name : NB_IMM_ASS_EXEC_FAIL_RADIO Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of immediate assignment -execution failures due to MS access problem.
Trigger condition:
Whenever the timer supervising the Immediate Assignment Procedure (T3101) expires during the establishment
of
an SDCCH sub-channel.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter 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) Whenever the BSC receives on Abis interface from the target cell negative acknowledgment to the TCH
channel
activation involved in the handover procedure.
2) Whenever the timer supervising the Channel Activation procedure (T9103) expires on the target cell during
activation of a TCH channel involved in the handover procedure.
3) Whenever an 48.058 ERROR REPORT message with a cause value of "O&M intervention" is received on Abis
interface from either the serving or the target cell during the external or internal inter-cell handover procedure and
leads to a transaction failure.
interface on either the old or the new channel during the internal intra-cell handover procedure and leads to a
transaction failure.
5) Whenever an 48.058 ERROR REPORT message on SAPI 0 with a cause value of "message sequence error"
is
received on Abis interface from the serving cell between the sending of the 48.058 CHANNEL ACTIVATION
message and the reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGMENT during the internal
inter-cell TCH handover and leads to a transaction failure.
is
received on Abis interface on the old channel between the sending of the 48.058 CHANNEL ACTIVATION
message and the reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGE during the internal intra-cell
TCH handover and leads to a transaction failure.
7) Whenever a LAPD failure related to either serving or target cell is reported to the Layer 3 of the BSC (for an
RSL supporting a TCH transaction for handover purpose) and leads to a transaction failure.
8) Whenever an TCH handover abortion is 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).
9) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "remote transcoder
failure" is received on Abis interface from the old channel between the sending of the 48.058 CHANNEL
ACTIVATION message and the reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGE during an
internal intra-cell or inter-cellTCH handover procedure and leads to a transaction failure.

Notes :
1. TCH handover failures which are due to O&M operator actions on BTS or BSC should not be counted. Indeed,
in case of numerous failures due to O&M commands, this counter will overestimate failures which are due to
Alcatel-Lucent

unit:
mechanism: unit:
External comment:
--
Counter Name : NB_TCH_DROP_EST_PHAS_BSS_PB Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
problems which are internal to the BSS. Counter definition:
However, due to the current implementation which does not allow to be aware of the origin of the failure, O&M
Number of TCH (in HR or FR usage) drops in TCH established phase due to BSS problem.
operator actions will also be counted. It may happen that several causes of failures mentioned below are
detected consecutively. In that case, the
2. It may happen that the counter can not be incremented since it is implemented within the faulty entity. counter
will only be incremented once, as soon as the call is released.
This counter takes into account TCH in traffic or in signaling mode. It is not incremented in case of TCH drop
during a normal assignment, a handover or a DTM assignment.
Trigger condition:
1) Whenever a 48.058 ERROR REPORT message with a cause value of "O&M intervention" is received on Abis
interface after TCH seizure and leads to a loss of call.
2) Whenever a 48.058 ERROR REPORT message on SAPI 0 with a cause value of "message sequence error" is
received on Abis interface after TCH seizure and leads to a loss of call.
3) Whenever a LAPD failure is reported to the Layer 3 of the BSC (for an RSL supporting a TCH transaction after
successful TCH seizure) and leads to a loss of call.
4) Whenever a TCH call release is initiated by the BSS O&M FAULT MANAGEMENT application part or by the
BSS TELECOM application part as the result of a system defense action which may be due to BSS equipment
failures external to the BSC (e.g. RSL failure or CU recovery failure), or due to BSC internal hardware problems
(e.g. TCU failure or DTC failure) or due to BSC internal software problems (e.g. inconsistencies detected between
software modules or lack of software resources (memory, timer reference, file reference...) or communication
problems between different processor boards).

Notes :
1. TCH call releases which are due to O&M operator actions on BTS or BSC should not be counted. Indeed, in
case of numerous failures due to O&M commands, this counter will overestimate failures which are due to
problems which are internal to the BSS.
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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_IDR_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Directed Retry
Domain: Traffic Load Sub domain-3: Internal
Counter definition:
MC15a=C15a, Number of incoming internal directed retry (towards a TCH channel in HR or FR usage) whose
target channel is allocated by the BSC.
Trigger condition:
The counter is incremented on the target cell whenever the 48.058 CHANNEL ACTIVATION message of a TCH
channel is about to be sent during an internal directed retry.
External comment:
--
Counter Name : NB_INC_TCH_HO_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming TCH (in HR or FR usage) handover (internal or external) -whose target channel is allocated
by
the BSC.
Since there are no reliable means at the target BSC to distinguish external directed retry from external handover,
the external directed retries are counted by this counter.
Trigger condition:
channel is about to be sent during any handover procedure.

External comment:
--
Alcatel-Lucent
Counter Name : NB_DTAP_MO_NOR_ASS_SUCC Counter Integer
SFD reference : RFD 3BKA55CBR035191 Length: 4
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: DTAP Assignment
Counter definition:
Number of mobile originating normal assignment - DTAP successes.
Trigger condition:
Whenever a 44.018 CONNECT ACK is received on Abis interface.
External comment:
--
Counter Name : NB_DTAP_MT_NOR_ASS_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of mobile terminating normal assignment - DTAP successes.
Trigger condition:
Whenever a 44.018 CONNECT ACK is sent on Abis interface.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_DTAP_EST_PHAS_RLF Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
Number of TCH (in HR or FR usage) drops in TCH DTAP established phase due to radio link failure (radio link
timeout or Lapdm timer expiry).
After an external handover, the target BSC considers that the CONNECT ACK has not already been received.
Trigger condition:
received on Abis interface for a TCH channel (after successful DTAP establishment).
2) Whenever an 48.058 ERROR INDICATION message is received on Abis interface and leads to a loss of call.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_DTAP_EST_PHAS_BSS_PB Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
Number of TCH (in HR or FR usage) drops in TCH DTAP established phase due to BSS problem.
counter
After an external handover, the target BSC considers that the CONNECT ACK has not already been received.
Trigger condition:

is

received on Abis interface after TCHDTAP establishment and leads to a loss of call.




Notes :
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_DTAP_EST_PHAS_REM_TRANS_FAIL Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
Number of TCH (in HR or FR usage) drops in TCH DTAP established phase due to remote transcoder failure.
This
counter is not concerned by the channel change procedure.
Trigger condition:
Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "remote transcoder
failure" is received on Abis interface for a TCH channel (for an established call).
External comment:
--
Alcatel-Lucent
Counter Name : NB_CALL_TFO Counter Integer
SFD reference : 3BK 10204 0478 DTZZA ("Tandem Free Operation") Length: 4
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Speech
Sub domain-2: TFO
Domain: Quality of Service Sub domain-3:
Counter 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
External comment:
--
Alcatel-Lucent
Counter Name : NB_TFO_CODEC_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TFO
Counter definition:
Number of codec mismatch resolutions or codec optimisations requested to the BSC.
Trigger condition:
Whenever a 48.058 REMOTE CODEC CONFIGURATION REPORT is received by the BSC.
External comment:
--
Counter Name : NB_TIMES_TRAF_DETECTED_HIGH Counter Integer
SFD reference : 3BK 10204 0326 DSZZA ("Traffic Management in HO Length: 4
Algorithms")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Domain: Resource Availability & Usage Sub domain-3:
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TIMES_TRAF_DETECTED_LOW Counter Integer
Algorithms")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2:
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH (in HR or FR usage) normal assignment preparation failures because of the non-queuing of the
ASSIGNMENT REQUEST message.
Case: 48.008ASSIGNMENT REQUEST on TCH (in HR or FR usage) is received when no TCH is available in the
cell. The request is rejected (by 48.008ASSIGNMENT FAILURE, cause: "no radio resource available"), because
the queuing procedure is either:
1) disabled within the BSC (i.e. (T11=0 and QUEUE_ANYWAY=0), OR (T11_forced=0 and
QUEUE_ANYWAY=1)), or
2) enabled within the BSC, i.e. T11 <> 0, but not requested by the MSC when QUEUE_ANYWAY=0.
Trigger condition:
The counter is incremented upon the sending of 48.008 ASSIGNMENT FAILURE (cause: "no radio resource
available") for a TCH channel because no TCH is available and either the queuing is disabled in the BSC (T11=0
and QUEUE_ANYWAY=0, or T11_forced=0 and QUEUE_ANYWAY=1), or the queuing is enabled,
QUEUE_ANYWAY=0, and the MSC does not request a queuing.


Note 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
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC612b=C612b, Case: 48.008ASSIGNMENT REQUEST on TCH (in FR or HR usage) is received when no TCH
is
available in the cell. The queuing is enabled within the BSC, but the request is rejected (by 48.008ASSIGNMENT
FAILURE, cause: "no radio resource available"), because the queue is full and no request of lower priority can be
dequeued from the BSC queue.
Trigger condition:
available") for a TCH channel because the queue is full and no request of lower priority can be de-queued.

by one.

parameter
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2:
Counter definition:
Case: 48.008ASSIGNMENT REQUEST is queued because no TCH (in HR or FR usage) is available in the cell,
timer T11 (case MSC requests for queuing whatever QUEUE_ANYWAY value may be) or timer T11_forced (case
QUEUE_ANYWAY=1, i.e. the queuing is forced within the BSC) is started, and no free TCH can be found before
timer expiry, consequently the request is rejected (by 48.008 CLEAR REQUEST cause: "no radio resource
available").
Remark: If an internal directed retry is attempted and failed while T11/T11_forced is running, the request is
un-holded and the BSC waits for the expiry of the relevant timer. Consequently, this counter must not be
incremented upon the failure of an internal directed retry.
Trigger condition:
The counter is incremented upon the sending of 48.008 CLEAR REQUEST (cause : "no radio resource available")
-following the expiry of T11 or T11 forced for a queued TCH normal assignment.


by one.

parameter
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
QUEUE_ANYWAY=1, i.e. the queuing is forced within the BSC) is started, and before the timer expiry, the
request is dequeued due to the receipt of a higher priority request (i.e. 48.008ASSIGNMENT REQUEST) : the
BSC sends 48.008ASSIGNMENT FAILURE (cause: "no radio resource available") for the first transaction.
Remark: As soon as an internal directed retry is attempted, the request is blocked within the BSC and cannot be
dequeued by a higher priority request.
Trigger condition:
The counter is incremented upon the sending of the 48.008 ASSIGMENT FAILURE (cause: "no radio resource
available") for a de-queued TCH request (i.e. normal assignment) due to the receipt of a higher priority request.


by one.

parameter
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_OUT_HO_EXEC_TRX Counter Integer
SFD reference : 3BK 10204 0470 DTZZA ("B7 counters improvements") Length: 2
B10 TRX 0
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
Number of TCH drops during the execution of any TCH outgoing handover, per TRX. This counter takes into
account handovers from TCH in traffic or in signaling mode.
MC621 = C621
Trigger condition:
1) Inter-cell TCH handover: whenever the timer supervising the handover procedure (T3103) expires.

2) External TCH handover (2G -> 2G): whenever the timer supervising the handover procedure on the serving cell
(T8) expires, except if a 48.008 CLEAR COMMAND with "normal event/call control" cause was received from the
MSC, leading to a normal call release. In such a case, the handover is considered as successful.

3) Intra-cell TCH handover: whenever the timer supervising the handover procedure (T3107) expires.

4) 2G -> 3G HO: whenever the timer supervising the 2G-3G handover procedure on the serving cell (T3121)
expires, except if a 48.008 CLEAR COMMAND with "normal event/call control" cause was received from the
MSC, leading to a normal call release. In such a case, the 2G->3G handover is considered as successful.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_FR_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Service
Counter 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.
External comment:
--
Counter Name : NB_TCH_DR_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH normal assignments requests from dual rate mobiles.
Trigger condition:
algorithm version 1 full rate and GSM speech coding algorithm version 1 half rate allowed.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DR_EFR_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.
External comment:
--
Counter Name : NB_TCH_AMR_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH normal assignment requests from AMR mobiles.
Trigger condition:
version 3 full rate or half rate allowed.
External comment:
--
Alcatel-Lucent
C701e Type 1 : Traffic measurements
Counter Name : NB_TCH_DATA_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH normal assignment requests for data calls.
Trigger condition:
Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for data call.
External comment:
--
Counter Name : NB_TCH_NOR_FR_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH normal assignment/mode modify in FR usage - whose channel is allocated in the BSC. This
counter takes into account mode modify from TCH signaling to TCH traffic (following a DTM assignment with a
TCH in signaling mode).
Trigger condition:
48.058 CHANNEL ACTIVATION/ MODE MODIFY about to be sent to the BTS, indicating a FR channel with GSM
speech coding algorithm version 1, not related to handover.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_HR_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
number of TCH normal assignment/mode modify in HR usage - whose channel is allocated in the BSC.
Trigger condition:
48.058 CHANNEL ACTIVATION / MODE MODIFY about to be sent to the BTS, indicating a HR channel with
GSM speech coding algorithm version 1, not related to handover.
External comment:
--
Counter Name : NB_TCH_NOR_EFR_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH normal assignment/mode modify in EFR usage - whose channel is allocated in the BSC. This
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_ALLOC_TRX Counter Integer
B10 TRX 0
B8 TRX 0
B9 TRX 1
Counter definition:
Number of TCH (in HR or FR usage) normal assignment whose RTCH channel is allocated in the BSC, per TRX.
This counter also takes into account normal assignment whose RTCH channel is allocated in the BSC in
signaling mode (FR usage only), for DTM.
MC703 = C703
Trigger condition:
Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent on Abis Interface to activate a TCH
channel for normal assignment, or for DTM assignment with a TCH in signaling mode.
External comment:
--
Counter Name : NB_TCH_NOR_AMR_FR_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH normal assignment/mode modify in FR AMR usage - whose channel is allocated in the BSC. This
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_AMR_HR_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
number of TCH normal assignment/mode modify in HR AMR usage - whose channel is allocated in the BSC.
Trigger condition:
48.058 CHANNEL ACTIVATION/ MODE MODIFY about to be sent to the BTS, indicating a HR channel with GSM
External comment:
--
Counter Name : NB_TCH_NOR_DATA_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_EGSM_MS_ACCESS_EXCEPT_LU Counter Integer
SFD reference : 3BK 10204 0519 DTZZA ("E-GSM support") Length: 4
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: E-GSM
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_OUT_HO_REQ_TRX Counter Integer
B10 TRX 0
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Outgoing
Domain: Handover Sub domain-3:
Counter 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.

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX Counter Integer
B10 TRX 0
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter 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.

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_OUT_HO_SUCC_TRX Counter Integer
B10 TRX 0
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
Nb of outgoing TCH handover successes, per TRX. Intracell, internal intercell and external handovers are counted
MC712 = C712
Trigger condition:
1) External HO in the following cases:
1a) 48.008CLEAR COMMAND (cause = "handover successful") is received on the serving BSC on the TCH
channel.
1b) 48.008 CLEAR COMMAND (cause = "normal event/call control") is received while T8 is running.
2) Internal inter-cell HO: whenever 44.018HANDOVER COMPLETE is received from the MS via the target cell on
the TCH channel.
3) Internal intra-cell HO: whenever 44.018 ASSIGNMENT COMPLETE is received from the MS via the cell on the
TCH channel.

Note 1: This counter counts both inter-PLMN and intra-PLMN handover events.
Note 2: This counter counts handover to UMTS.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_OUT_HO_FAIL_REV_TRX Counter Integer
B10 TRX 0
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
Nb of outgoing TCH handover -execution failures due to MS access problem with reversion of the mobile to the
old
channel. Intracell, internal intercell and external handovers are counted together. This counter takes into account
handovers from TCH in traffic or in signaling mode. It does not take into account DTM Assignments.
MC713 = C713
Trigger condition:
1) External HO: Whenever a 44.018 HANDOVER FAILURE message is received on Abis interface from the
serving cell, during an external TCH handover.
2) Internal inter-cell HO: Whenever a 44.018 HANDOVER FAILURE message is received on Abis interface from
the serving cell, during an internal inter-cell TCH handover.
3) Intracell HO: Whenever a 44.018 ASSIGNMENT FAILURE message is received on Abis interface on the
serving
channel, during an internal intra-cell TCH handover.

Note: This counter counts handover to UMTS.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_OUT_HO_FAIL_NO_REV_TRX Counter Integer
B10 TRX 0
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
Nb of outgoing TCH handover -execution failures due to MS access problem without reversion of the mobile to the
old channel (call drop). Intracell, internal intercell and external handovers are counted together. This counter takes
into account handovers from TCH in traffic or in signaling mode. It does not take into account DTM Assignments.

MC714 = C714
Trigger condition:
1) External TCH HO: Whenever the timer supervising the handover procedure on the serving cell (T8) expires,
except if a 48.008 CLEAR COMMAND with "normal event/call control" cause was received from the MSC, leading
to a normal call release. In such a case, the handover is considered as successful.
2) Internal intercell TCH HO: Whenever the timer supervising the handover procedure (T3103) expires during an
internal inter-cell TCH handover.
3) Intracell TCH HO: Whenever the timer supervising the handover procedure (T3107) expires during an internal
intra-cell

Note: This counter counts hantover to UMTS
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_IDR_SUCC_TRX Counter Integer
B10 TRX 0
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Counter definition:
Number of incoming directed retry (towards a TCH channel in HR or FR usage) successes, per TRX.
MC717a = C717a
Trigger condition:
Whenever a 44.018 HANDOVER COMPLETE message is received on Abis interface from the target cell for a
TCH
channel involved in an internal directed retry procedure.
External comment:
--
Counter Name : NB_INC_TCH_HO_SUCC_TRX Counter Integer
B10 TRX 0
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter 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,
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.

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_SUCC_TRX Counter Integer
B10 TRX 0
B8 TRX 0
B9 TRX 1
Counter definition:
Number of TCH (in HR or FR usage) normal assignment successes, per TRX. This counter also takes into
account normal assignment successes for TCH establishment in signaling mode (FR usage only), for DTM.
MC718 = C718
Trigger condition:
Whenever a 44.018 ASSIGNMENT COMPLETE message is received on Abis interface for a TCH channel that is
not involved in a handover procedure, in traffic or in signaling mode.
External comment:
--
Counter Name : NB_TCH_DROP_EST_PHAS_RLF_TRX Counter Integer
B10 TRX 0
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
Number of TCH (in HR or FR usage) drops in TCH established phase due to radio link failure (radio link timeout or
Lapdm timer expiry), per TRX. This counter takes into account TCH in traffic or in signaling mode.
MC736 = C736
Trigger condition:
received on Abis interface for a TCH channel (after successful seizure).
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX Counter Integer
B10 TRX 0
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
Number of TCH (in HR or FR usage) drops in TCH established phase due to remote transcoder failures (per
TRX).
Trigger condition:
The counter is incremented whenever a 48.058 CONNECTION FAILURE INDICATION message with cause
"Remote Transcoder Failure" is received on Abis interface for an established TCH connection. The BSC considers
a TCH connection as "established" once a 44.018 ASSIGNMENT COMPLETE message (in case of normal
assignments or an internal intra-cell handovers) or a 44.018 HANDOVER COMPLETE message (in case of an
internal inter-cell incoming HO or an external inter-cell incoming
HO) has been received for the TCH connection.

Note 1: MC739 = C739.
Note 2: The counter is incremented only once per established TCH connection. Thus, even if the BTS sends
several 48.058 CONNECTION FAILURE INDICATION messages with cause "Remote Transcoder Failure" for a
particular established TCH connection, BSC will increment the counter only once for that connection.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX Counter Integer
B10 TRX 0
B8 TRX 0
B9 TRX 1
Counter definition:
Number of TCH (in HR or FR usage) normal assignment -execution failures due to MS access problem, per TRX.
This counter also takes into account DTM assignment -execution failures due to MS access problem for TCH
establishment in signaling mode (FR usage only).
MC746b = C746b
Trigger condition:
1) The timer T3107 in the BSS supervising the TCH channel seizure by the mobile expires (following the sending
of 44.018 ASSIGNMENT COMMAND for a TCH channel that is not involved in a handover procedure).
2) The timer T3107 in the BSS supervising the TCH channel seizure by the mobile expires, following the sending
of 44.018 DTM ASSIGNMENT COMMAND for a TCH channel in signaling mode.
3) The BSC receives a 44.018 ASSIGNMENT FAILURE on the old (SDCCH) channel during the normal
assignment procedure except in case of multiband cell, when the normal assignment procedure is performed in
the inner zone and the ASSIGNMENT FAILURE is received with the cause "protocol error unspecified".
4) The BSC receives a 44.018 DTM ASSIGNMENT FAILURE on the old (SDCCH) channel during the DTM
assignment procedure, for a TCH in signaling mode.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC812 = C812 = C612a + C612b + C612c + C612d
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Multiband
Counter 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,
DCS1900 bands", or,
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:
DCS1800 bands", or,
DCS1900 bands", or,

External comment:
--
Alcatel-Lucent
Counter Name : NB_Suspend_Resume_req Counter Integer
SFD reference : 3BK 10204 0503 DTZZA ("GPRS suspend / resume for class Length: 4
B mobiles")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2:
Counter definition:
Number of suspend / Resume requests.
A request could lead to a success, a failure or a stop.
Trigger condition:
Emission of MS Suspend message by the BSC to the MFS
Emission of MS Resume message by the BSC to the MFS
A suspend message received from MS with a "suspend cause" filtered by BSC will not be counted. Stop causes
could be:
1) External handover
2) MS channel failure.
External comment:
--
Counter Name : Nb_Suspend_fail Counter Integer
B mobiles")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2:
Counter definition:
Number of suspend/resume procedure failures.
Trigger condition:
Reception of -Suspend nack or resume nack, or expiration of T_GPRS_Resume.
External comment:
--
Alcatel-Lucent
Counter Name : Nb_Suspend_succ Counter Integer
B mobiles")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2:
Counter definition:
Number of suspensions successes.
Trigger condition:
Reception of Resume ack message from MFS.
External comment:
--
Alcatel-Lucent
Type name: Resource availability measurements
Type definition:
Set of counters related to the availability of the CCCH, SDCCH or TCH channels
C141 Type 2 : Resource availability measurements
Counter Name : AV_NB_TCH_QUEUED Counter Round (10
Data collection Status Inspection (polling=10s) Measured number
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TCH
Domain: Resource Availability & Usage Sub domain-3: Usage
Counter definition:
Average number of queued TCH (in HR or FR usage) normal assignment or external handover requests.
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. In order to provide one decimal place, the averaged value
(real) is multiplied by ten and then rounded up or down to the nearest integer value.
Note that the counter value that is indicated in the ASCII file, which can be obtained via the OBSYNT interface,
still has to be divided by 10, whereas the value that is provided at the user interface is the correct one.
External comment:
--
Alcatel-Lucent
Counter Name : AV_NB_NOT_AVAIL_TRX_TS Counter Round (x)
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TRX_TS
Domain: Resource Availability & Usage Sub domain-3: Availability
Counter definition:
Average number of not available radio timeslots (TRX_TS).
Trigger condition:
summed and divided by the number of observations. The averaged value (real) is rounded up or down to the
nearest integer value.
External comment:
--
Counter Name : AV_NB_AVAIL_TCH Counter Round (x)
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
Average number of available TCH/PDCH timeslots for traffic usage (i.e. TCH (for HR or FR usage) or PDCH).
Trigger condition:
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.
External comment:
--
Alcatel-Lucent
Counter Name : AV_NB_AVAIL_SDCCH Counter Round (x)
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter definition:
Average number of available static SDCCH sub-channels (i.e. on static SDCCH timeslots).
Trigger condition:

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".
External comment:
--
Counter Name : AV_NB_AVAIL_CCCH Counter Round (x)
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: CCCH
Counter definition:
Average number of available CCCH channels.
Trigger condition:
External comment:
--
Alcatel-Lucent
C28a Type 2 : Resource availability measurements
Counter Name : AV_NB_BUSY_CS_TS Counter Round (10
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_MAX_SIMUL_BUSY_CS_TS Counter Integer
SFD reference : 3BK 10204 0511 DTZZA ("Dynamic SDCCH allocation") Length: 2
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
Maximum number of simultaneously busy TCH radio timeslots (in HR or FR usage, in traffic or in signaling mode)
and simultaneously busy dynamic SDCCH/8 radio timeslots allocated as TCH.
Trigger condition:
Whenever a TCH radio timeslot or a dynamic SDCCH/8 radio timeslot allocated as TCH becomes busy, the BSC
determines the current number of busy TCH radio timeslots (in HR or FR usage) and busy dynamic SDCCH/8
radio timeslots allocated as TCH. This counter is the maximum value of this number during the accumulation
period.

This counter does not take into account the PDCHs allocated to the MFS.
External comment:
--
Alcatel-Lucent
Counter Name : AV_NB_BUSY_SDCCH Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter 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:
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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_MAX_SIMUL_BUSY_SDCCH Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter definition:
Maximum number of simultaneously busy SDCCH subchannels, taking into account the following SDCCH
sub-channels: 1) Static SDCCH/x sub-channels, 2) Dynamic SDCCH sub-channels which are dynamically
allocated on the dynamic SDCCH/8 timeslots.
Trigger condition:
At each 48.058 CHANNEL ACTIVATION (SDCCH subchannel) sent to the cell:
C31 = MAX ["old" C31 value (i.e. before the channel activation), number of busy SDCCH subchannels observed
for
the cell].
External comment:
--
Counter Name : AV_NB_IDLE_TCH_INTERF_BAND1 Counter Round (x)
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter 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:
External comment:
--
Alcatel-Lucent
C320b Type 2 : Resource availability measurements
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
This
Trigger condition:
summed and divided by the number of observations. The average value (real) is rounded up or down to the
nearest
integer value.
External comment:
--
C320c Type 2 : Resource availability measurements
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
This
Trigger condition:
External comment:
--
Alcatel-Lucent
C320d Type 2 : Resource availability measurements
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter 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:
External comment:
--
C320e Type 2 : Resource availability measurements
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
This
Trigger condition:
nearest
integer value.
External comment:
--
Alcatel-Lucent
Counter Name : TIME_ALL_AVAIL_TRX_TS_BUSY Counter Integer
Data collection Cumulative Measured seconds
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : TIME_SDCCH_CONGESTION Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter 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.
External comment:
--
Alcatel-Lucent
Type name: Resource usage on CCCH channel measurements
2) The maximum number of CCCH channels per cell that can be measured is limited to 8.
Type definition:
Set of counters related to the usage of the CCCH channel (PCH load, AGCH load, RACH load)
C8a Type 3 : Resource usage on CCCH channel measurements
Counter Name : NB_PAGING_CMD Counter Integer
B10 TRX_TS 1
B8 TRX_TS 0
B9 TRX_TS 1
Sub domain-2: CCCH
Counter 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.
External comment:
--
Alcatel-Lucent
C8b Type 3 : Resource usage on CCCH channel measurements
Counter Name : NB_IMM_ASS_CMD Counter Integer
B10 TRX_TS 1
B8 TRX_TS 0
B9 TRX_TS 1
Sub domain-2: CCCH
Counter definition:
AGCH load: number of 48.058 IMMEDIATE ASSIGN COMMAND messages sent for CS traffic on Abis to the MS.
Trigger condition:
Whenever a 48.058 IMMEDIATE ASSIGN COMMAND message for CS traffic is about to be sent on Abis
interface
to the cell on the related TRX timeslot.

Note: This counter does not take into account the 48.058 IMMEDIATE ASSIGN COMMAND messages sent for
PS traffic.
External comment:
--
C8c Type 3 : Resource usage on CCCH channel measurements
Counter Name : NB_CHAN_REQD Counter Integer
B10 TRX_TS 1
B8 TRX_TS 0
B9 TRX_TS 1
Sub domain-2: CCCH
Counter 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.
External comment:
--
Alcatel-Lucent
C8d Type 3 : Resource usage on CCCH channel measurements
Counter Name : NB_IMM_ASS_REJ Counter Integer
SFD reference : 3BK 10204 0314 DSZZA ("Immediate Assignment Reject") Length: 4
B10 TRX_TS 1
B8 TRX_TS 0
B9 TRX_TS 1
Sub domain-2: CCCH
Counter definition:
Number of 48.058 CHANNEL REQUIRED received while no SDCCH can be allocated by the BSC (congestion),
i.e. the number of 44.018IMMEDIATE ASSIGNMENT REJECT sent to the MS via the selected cell.
Trigger condition:
Whenever a 48.058 IMMEDIATE ASSIGNMENT COMMAND message is about to be sent on Abis interface to the
cell on the related TRX timeslot with a "Full Immediate Assignment" Info Element containing a 44.018
IMMEDIATE ASSIGNMENT REJECT message.

Note: This counter only applies to CS traffic.
External comment:
--
Alcatel-Lucent
Type name: Resource usage on SDCCH channel measurements
2) The maximum number of SDCCH subchannels per cell that can be observed is limited to 16.
Type definition:
Set of counters related to the usage of the SDCCH channel
C39 Type 4 : Resource usage on SDCCH channel measurements
Counter Name : NB_TIMES_SDCCH_BUSY Counter Integer
B10 TRX_TS 1
B8 TRX_TS 0
B9 TRX_TS 1
Sub domain-2: SDCCH
Counter definition:
Number of times the SDCCH sub-channels belonging to the radio timeslot are busy.
Trigger condition:
Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent to a CELL to activate an SDCCH
Sub-channel on the related TRX timeslot.
External comment:
--
Alcatel-Lucent
C40 Type 4 : Resource usage on SDCCH channel measurements
Counter Name : TIME_SDCCH_BUSY Counter Integer
B10 TRX_TS 1
B8 TRX_TS 0
B9 TRX_TS 1
Sub domain-2: SDCCH
Counter 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.
External comment:
--
Alcatel-Lucent
Type name: Resource usage on TCH channel measurements
2) The maximum number of TCH channels per cell that can be observed is limited to 63.
Type definition:
Set of counters releated to the usage of the TCH channel (in HR or FR usage)
C370a Type 5 : Resource usage on TCH channel measurements
Counter Name : NB_TCH_FR_ALLOC Counter Integer
B10 TRX_TS 1
B8 TRX_TS 0
B9 TRX_TS 1
Sub domain-2: TCH
Counter definition:
Number of times a TCH radio timeslot or a dynamic SDCCH/8 timeslot is allocated in FR usage, for normal
assignment, for DTM assignment or handover, in traffic or in signaling mode.
Trigger condition:
Whenever a 48.058CHANNEL_ACTIVATION message is about to be sent to the cell to activate a full rate TCH
channel for normal assignment, for DTM assignment or handover, in traffic or in signaling mode.
External comment:
--
Alcatel-Lucent
C370b Type 5 : Resource usage on TCH channel measurements
Counter Name : NB_TCH_HR_ALLOC Counter Integer
B10 TRX_TS 1
B8 TRX_TS 0
B9 TRX_TS 1
Sub domain-2: TCH
Counter definition:
Number of times a TCH radio timeslot or a dynamic SDCCH/8 timeslot is allocated in HR usage (i.e. the upper or
lower HR sub-channel of the radio timeslot is allocated), for normal assignment or handover.
Trigger condition:
Whenever a CHANNEL_ACTIVATION message is about to be sent to the cell to activate a half rate TCH
subchannel (either upper or lower) for normal assignment or handover.
External comment:
--
Alcatel-Lucent
Counter Name : TIME_FR_TCH_BUSY Counter Integer
B10 TRX_TS 1
B8 TRX_TS 0
B9 TRX_TS 1
Sub domain-2: TCH
Counter 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.
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.
External comment:
--
Alcatel-Lucent
Counter Name : TIME_HR_TCH_BUSY Counter Integer
B10 TRX_TS 1
B8 TRX_TS 0
B9 TRX_TS 1
Sub domain-2: TCH
Counter 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.
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.
External comment:
--
Alcatel-Lucent
Counter Name : TIME_FR_TCH_BUSY_BY_MULTIBAND_MS Counter Integer
SFD reference : 3BK 10204 0286 DSZZA ("Multiband Operation in one BSC") Length: 4
B10 TRX_TS 1
B8 TRX_TS 0
B9 TRX_TS 1
Sub domain-2: TCH
Counter 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.
DCS1800 bands", or,
DCS1900 bands", or,
Trigger condition:
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:
DCS1800 bands", or,
DCS1900 bands", or,
ACKNOWLEDGE message or the expiry of timer T_RCR_ACK twice (after the sending of the 48.058 RF
CHANNEL RELEASE.
External comment:
--
Alcatel-Lucent
Counter Name : TIME_HR_TCH_BUSY_BY_MULTIBAND_MS Counter Integer
B10 TRX_TS 1
B8 TRX_TS 0
B9 TRX_TS 1
Sub domain-2: TCH
Counter 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.
DCS1800 bands", or,
DCS1900 bands", or,
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.
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:
DCS1800 bands", or,
DCS1900 bands", or,

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.
External comment:
--
Alcatel-Lucent
Type name: TCH handover measurements
Type definition:
Set of counters related to the TCH handover procedure. The counters are provided per handover
category : incoming and outgoing, internal (inter-cell and intra-cell) and external. The handover causes
are also provided.
C220 Type 6 : TCH handover measurements
Counter Name : NB_INC_EXT_TCH_HO_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Incoming External
Counter definition:
Number of incoming external TCH (in HR or FR usage) handover requests.
Trigger condition:
Whenever 48.008HANDOVER REQUEST received by the target BSC for the target cell on TCH.

External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_TCH_HO_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming external TCH (in HR or FR usage) handover attempts.
Trigger condition:
Whenever 48.008HANDOVER REQUEST ACK is sent by the target BSC containing the 44.018HANDOVER
COMMAND towards the target cell on TCH.

External comment:
--
Counter Name : NB_INC_INT_TCH_HO_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Incoming Internal
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_INT_TCH_HO_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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,
External comment:
--
Counter Name : NB_INTRA_TCH_HO_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INTRA_TCH_HO_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter 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.
External comment:
--
Counter Name : NB_OUT_INT_TCH_HO_IDR_IN_ZONE_REQ Counter Integer
SFD reference : 3BK 10204 0363 DSZZA ("Improvements in Radio Channel Length: 4
Selection")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Outgoing Internal
Counter definition:
Number of outgoing internal inter-cell TCH (in HR or FR usage) handover requests, plus the number of internal
directed retries requests, towards the inner zone of a target concentric cell.
Trigger condition:
Whenever the BSC process responsible for the handover procedure at the serving cell generates an HO alarm
towards the inner zone of a target concentric cell for internal inter-cell TCH handover, or for an internal directed
retry.
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_INT_TCH_HO_IDR_IN_ZONE_EXEC_FAIL Counter Integer
Selection")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing internal inter-cell TCH (in HR or FR usage) handover -executions failures, plus the number of
internal directed retries -execution failures due to MS access problem, towards the inner zone of a target
concentric cell.
This counter permits to tune the EN_BETTER_ZONE_HO parameter.
Trigger condition:
1) Receipts of 44.018HANDOVER FAILURE (cause=radio interface failure, reversion to old channel).
2) Timer T3103 expiry (this timer starts upon the sending of 44.018HANDOVER COMMAND and is stopped upon
the receipt of 44.018HANDOVER COMPLETE).
External comment:
--
Counter Name : NB_TCH_NOR_ASS_INNER_ZONE_ALLOC Counter Integer
Selection")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH (in HR or FR usage) normal assignment -whose ressource is allocated in the BSC, in the inner
zone of a concentric cell.
Trigger condition:
Whenever 48.058CHANNEL ACTIVATION is about to be send on Abis to activate a TCH channel in the inner
zone
of the concentric cell for any normal assignment.
External comment:
--
Alcatel-Lucent
C41b Type 6 : TCH handover measurements
Counter Name : NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming external TCH (in HR or FR usage) handover -preparation failures due to A-traffic-channel
status mismatch between the BSC and the MSC.
Trigger condition:
1) Whenever a 48.008 HANDOVER FAILURE message with a cause value of "requested terrestrial resource
unavailable" is sent on A interface from the target BSC to the MSC.
2) Whenever a 48.008 HANDOVER FAILURE message with a cause value of "terrestrial circuit already allocated"
is sent on A interface from the target BSC to the MSC.
3) Whenever a 48.008 HANDOVER FAILURE message with a cause value of "BSS not equipped" is sent on A
interface from the target BSC to the MSC.

External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_TCH_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming external TCH (in HR or FR usage) handover successes.
Trigger condition:
TCH
channel that is involved in an external TCH handover.

External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_TCH_HO_EXEC_FAIL_MS_ACCESS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming external TCH (in HR or FR usage) handover -execution failures due to MS access problem.
Trigger condition:
1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "handover access
failure" is received on Abis interface from the target cell for a TCH channel during an external TCH handover.
2) Whenever the timer supervising the handover procedure on the target cell (T9113), expires during an external
TCH handover.
3) Whenever a 48.008 CLEAR COMMAND with a cause value of "radio interface failure - reversion to old
channel"
is received on A interface on the target BSC from the MSC during an external TCH handover.

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ATPT_23_TrafHandover Counter Integer
Algorithms")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Counter definition:
MC440=C440, Number of inter-cell internal or external handover attempts, with the cause 23: "traffic handover"
on
a TCH channel (in HR or FR usage).
Trigger condition:
Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 23. This counter is
incremented in the serving cell.

External comment:
--
Counter Name : NB_TCH_HO_ATPT_24_GenCaptureHandover Counter Integer
Algorithms")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ATPT_26_BadQualHR Counter Integer
SFD reference : 3BK 10204 0479 DTZZA ("Adaptive MultiRate Codec") Length: 4
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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.
External comment:
--
Counter Name : NB_TCH_HO_ATPT_27_GoodQualFR Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ATPT_28_FastTraffic Counter Integer
SFD reference : 3BK 10204 0475 DTZZA ("Instantaneous Peaks Management") Length: 4
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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.
External comment:
--
Counter Name : NB_TCH_HO_ATPT_22_TooShortDistance Counter Integer
SFD reference : 3BK 10204 0327 DSZZA ("General HO Algorithms Length: 4
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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

External comment:
--
Alcatel-Lucent
C45a Type 6 : TCH handover measurements
Counter Name : NB_OUT_EXT_TCH_REAL_HO_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Outgoing External
Counter 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


External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_EXT_TCH_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing external TCH (in HR or FR usage) handover successes. This counter takes into account
Trigger condition:
External TCH handover in the following cases:
1/ a 48.008 CLEAR COMMAND message with a cause value of "handover successful" is received on A interface
on the serving BSC from the MSC.
2/ 48.008 CLEAR COMMAND (cause= "normal event/call control") is received while T8 is running.

Note: This counter doesnt count hantover to UMTS
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ALLOC_EMERGENCY_PRES Counter Integer
SFD reference : 3BK 10204 0362 DTZZA ("Preservation of on-going calls") Length: 4
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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 2: The HMI name of the parameter NUM_TCH_EGNCY_HO is "NUM_TCH_EMERGENCY_HO".
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ATPT_29_TFO Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
Number of intra-cell handover - attempts, with the cause 29 (TFO mismatch resolution, TFO optimisation).
MC461 = C461
Trigger condition:
External comment:
--
Counter Name : NB_OUT_EXT_TCH_HO_EXEC_FAIL_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing external TCH (in HR or FR usage) handover -execution failures due to MS access problem
with reversion of the mobile to the old channel. This counter takes into account handovers from TCH in traffic or in
signaling mode.
Trigger condition:
Whenever a 44.018 HANDOVER FAILURE message is received on Abis interface from the serving cell , during
an
external TCH handover.
Note 2: This counter does not count hantover to UMTS.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ATPT_2_TooLowQualUp Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:
incremented in the serving cell,

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ATPT_3_TooLowLevUp Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
Number of inter-cell internal or external handover attempts, with cause 2: "uplink quality too low" on a TCH
Trigger condition:

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ATPT_4_TooLowQualDown Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
Number of inter-cell internal or external handover attempts, with cause 4: "downlink quality too low" on a TCH
Trigger condition:
Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTS because of cause 4. This counter is

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ATPT_5_TooLowLevDown Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
Number of inter-cell internal or external handover attempts, with cause 5: "downlink level too low" on a TCH
Trigger condition:

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ATPT_6_TooLongDistance Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
Number of inter-cell internal or external handover attempts, with cause 6: "MS-BTS distance too long" on a TCH
Trigger condition:

External comment:
--
Counter Name : NB_TCH_HO_ATPT_15_TooHighLevInterfUp Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ATPT_16_TooHighLevInterfDown Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:
External comment:
--
Counter Name : NB_TCH_HO_ATPT_12_TooLowPowBudg Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ATPT_21_HighLevNeigCellPrefBand Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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

External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_EXT_TCH_HO_EXEC_FAIL_NO_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing external TCH (in HR or FR usage) handover execution failures due to MS access problem
without reversion of the mobile to the old channel (call drop). This counter takes into account handovers from TCH
in traffic or in signaling mode.
Trigger condition:
Whenever the timer supervising the handover procedure on the serving cell (T8), expires during an external TCH
handover, except if a 48.008 CLEAR COMMAND with "normal event/call control" cause was received from the

Note: This counter does not count handover to UMTS
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_EXT_TCH_HO_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing external TCH (in HR or FR usage) handover attempts. This counter takes into account
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 2: This counter does not count handover to UMTS
External comment:
--
Counter Name : NB_INC_INT_TCH_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming internal inter-cell TCH (in HR or FR usage) handover successes.
Trigger condition:
TCH
channel that is involved in an internal inter-cell TCH handover.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_INT_TCH_HO_EXEC_FAIL_MS_ACCESS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming internal inter-cell TCH (in HR or FR usage) handover -execution failures due to MS access
problem; the mobile either reverts or does not to the old channel.
Trigger condition:
Whenever the timer supervising the handover procedure (T3103) expires during an internal inter-cell TCH
handover.
External comment:
--
Counter Name : NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS Counter Integer
SFD reference : 3BK 10204 0518 DTZZA ("A bis and A ter dynamic allocation") Length: 2
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming external TCH (in HR or FR usage) handover -preparation failures due to congestion (C541a),
or A-traffic-channel status mismatch between the BSC and the MSC (C41b).
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming external TCH (in HR or FR usage) handover -preparation failures due to congestion.
Trigger condition:
Whenever a 48.008 HANDOVER FAILURE message with a cause value of "no radio resource available" is sent
on
A interface from the target BSC to the MSC during an external TCH handover.


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

parameter
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming internal inter-cell TCH (in HR or FR usage) handover -preparation failures due to congestion.
Trigger condition:
Whenever an internal inter-cell TCH handover cannot be performed, because the target cell is congested (no free
TCH channel).

Note 1: In MX BSC, this counter is incremented whenever an internal inter-cell TCH handover cannot be
performed
due to the TCH processing capacity of CCP reaches the limit defined by the MAX_TCH_PER_CCP parameter. In
this case, MC926 is also incremented by one.

parameter
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_INT_TCH_HO_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing internal inter-cell TCH (in HR or FR usage) handover requests. This counter takes into
Trigger condition:
cells) for internal inter cell TCH handover.
External comment:
--
Counter Name : NB_OUT_INT_TCH_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing internal inter-cell TCH (in HR or FR usage) handover successes. This counter takes into
Trigger condition:
Whenever a 44.018 HANDOVER COMPLETE message is received on Abis interface from the target cell , during
an internal inter-cell TCH handover.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter definition:
Number of intra-cell TCH (in HR or FR usage) handover -preparation failures due to congestion. This counter
takes
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.

parameter
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_INT_TCH_HO_EXEC_FAIL_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing internal inter-cell TCH (in HR or FR usage) handover -execution failures due to MS access
problem with reversion of the mobile to the old channel. This counter takes into account handovers from TCH in
traffic or in signaling mode.
Trigger condition:
Whenever a 44.018 HANDOVER FAILURE message is received on Abis interface from the serving cell, during an
External comment:
--
Counter Name : NB_OUT_INT_TCH_HO_EXEC_FAIL_NO_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing internal inter-cell TCH (in HR or FR usage) handover -execution failures due to MS access
problem without reversion of the mobile to the old channel (call drop). This counter takes into account handovers
from TCH in traffic or in signaling mode.
Trigger condition:
Whenever the timer supervising the handover procedure (T3103) expires during an internal inter-cell TCH
handover.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ATPT_7_ConsBadSACCHmicroCell Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
Number of inter-cell internal or external handover attempts, with cause 7: "several consecutive bad SACCH
frames
received in a micro cell" on a TCH channel (in HR or FR usage). This counter takes into account handovers from
TCH in traffic or in signaling mode. This counter is related to micro cell environment.
Trigger condition:

External comment:
--
Alcatel-Lucent
C585d Type 6 : TCH handover measurements
Counter Name : NB_TCH_HO_ATPT_17_TooLowLevUpMicroCell Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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
This counter is related to micro cell environment.
Trigger condition:

External comment:
--
Alcatel-Lucent
C585e Type 6 : TCH handover measurements
Counter Name : NB_TCH_HO_ATPT_18_TooLowLevDownMicroCell Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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
This counter is related to micro cell environment.
Trigger condition:

External comment:
--
Alcatel-Lucent
C585f Type 6 : TCH handover measurements
Counter Name : NB_TCH_HO_ATPT_14_HighLevNeigLowCellSlowMS Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:

External comment:
--
Counter Name : NB_TCH_HO_ATPT_10_TooLowLevUpInZone Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:
External comment:
--
Alcatel-Lucent
C586b Type 6 : TCH handover measurements
Counter Name : NB_TCH_HO_ATPT_11_TooLowLevDownInZone Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:
External comment:
--
C586c Type 6 : TCH handover measurements
Counter Name : NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_INT_TCH_HO_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing internal inter-cell TCH (in HR or FR usage) handover attempts. This counter takes into
Trigger condition:
an internal inter-cell TCH handover procedure.
External comment:
--
Counter Name : NB_INTRA_TCH_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter definition:
Number of intra-cell TCH (in HR or FR usage) handover successes. This counter takes into account handovers
from TCH in traffic or in signaling mode. It does not take into account DTM Assignments.
Trigger condition:
Whenever a 44.018 ASSIGNMENT COMPLETE message is received on Abis interface on the target channel for a
TCH channel that is involved in an internal intra-cell TCH handover.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INTRA_TCH_HO_EXEC_FAIL_NO_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter definition:
Number of intra-cell TCH (in HR or FR usage) handover execution failures due MS access problem; the mobile is
lost. This counter takes into account handovers from TCH in traffic or in signaling mode. It does not take into
Trigger condition:
Whenever the timer supervising the handover procedure (T3107) expires during an internal intra-cell.
External comment:
--
Counter Name : NB_INTRA_TCH_HO_EXEC_FAIL_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter 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
Trigger condition:
Whenever a 44.018 ASSIGNMENT FAILURE message is received on Abis interface on the serving channel,
during
an internal intra-cell TCH handover.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_MSC_TRIG Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
Number of external handovers triggered by the MSC but not required by the BSS.
Trigger condition:
Whenever a 48.008 HANDOVER COMMAND message is received on A interface from the MSC and timer
T_HO_REQ_LOST is not running.

Note: This counter does not count hantover to UMTS
External comment:
--
Alcatel-Lucent
Type name: LapD measurements
Type scope (per BSS): BSC
Candidate for Standard Yes
- In Standard usage: none
- In Detailed usage : none
Type definition:
Set of counters related to the LapD logical links
L1.1 Type 7 : LapD measurements
Counter Name : NB_LAPD_INFO_FRAME_SENT Counter Integer
B10 LapD 1
B8 LapD 0
B9 LapD 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: Abis
Domain: Traffic Load Sub domain-3: LapD
Counter 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:
--
Alcatel-Lucent
Counter Name : NB_LAPD_CRC_ERROR Counter Integer
B10 LapD 1
B8 LapD 0
B9 LapD 1
Sub domain-2: Abis
Domain: Quality of Service Sub domain-3: LapD
Counter definition:
Number of frames received with CRC error on the LapD link.
Trigger condition:
Whenever the HDLC Formatter handling the Physical LAPD link detects a CRC error in a received Frame.
Note 1: In case of LapD over UDP, this counter is meaningless and shall always be set to 0.
External comment:
--
Counter Name : NB_LAPD_INFO_FRAME_RESENT Counter Integer
B10 LapD 1
B8 LapD 0
B9 LapD 1
Sub domain-2: Abis
Counter definition:
Number of Information frames re-transmitted on the LapD link.
Trigger condition:
Whenever an Information Frame is retransmitted on a logical LAPD link.
External comment:
--
Alcatel-Lucent
Counter Name : TIME_LAPD_UNAVAIL Counter Integer
B10 LapD 1
B8 LapD 0
B9 LapD 1
Sub domain-2: Abis
Counter definition:
Time (in seconds) during which the LapD link is unavailable for any cause.
Trigger condition:
1) This counter will be incremented with the number of seconds elapsed between LAPD layer entities initiation
(first DL_ESTABLISH_ REQUEST primitive sent by Layer 3 to Layer 2 for that logical LAPD link) and reception of
the DL-ESTABLISH-CONFIRM primitive for that logical LAPD link.
2) This counter will also be incremented with the number of seconds elapsed between reception of the
DL-RELEASE-INDICATION primitive and reception of the DL_ESTABLISH-CONFIRM primitive for that logical
LAPD link.
External comment:
--
Counter Name : NB_LAPD_EST Counter Integer
B10 LapD 1
B8 LapD 0
B9 LapD 1
Sub domain-2: Abis
Counter definition:
Number of data link establishment, re-establishment and reset on the LapD link.
Trigger condition:
1) Whenever the layer 2 receives a SABME frame in state MF Established or Timer recovery (data link reset
initiated by the BTS).
2) Whenever the layer 2 receives an UA frame in the state Awaiting Establishment (i.e. data link establishment,
re-establishment or link reset initiated by the BSC).
External comment:
--
Alcatel-Lucent
Counter Name : TIME_LAPD_CONG Counter Integer
SFD reference : 3BK 10204 0541 DTZZA ("B8 BSC Counter and Indicator Length: 4
Improvements")
B10 LapD 1
B8 LapD 0
B9 LapD 1
Sub domain-2: Abis
Counter definition:
Time in seconds during which the LapD link is congested in transmission in the BSC.
Trigger condition:
This counter will be incremented with the number of seconds elapsed between the reception of
L2_CONGESTION_IND and the reception of L2_END_CONGESTION_IND by the Layer 3 in the BSC
External comment:
--
Counter Name : NB_LAPD_INFO_FRAME_REC Counter Integer
B10 LapD 1
B8 LapD 0
B9 LapD 1
Sub domain-2: Abis
Domain: Traffic Load Sub domain-3: LapD
Counter definition:
Number of Information frames received on the LapD link, excluding the re-transmissions.
Trigger condition:
Whenever an Information Frame is received on a logical LAPD link.
External comment:
--
Alcatel-Lucent
Counter Name : NB_LAPD_RNR_SENT Counter Integer
B10 LapD 1
B8 LapD 0
B9 LapD 1
Sub domain-2: Abis
Counter definition:
Number of Receive Not Ready (RNR) frames transmitted on the LapD link.
Trigger condition:
Whenever an RNR Frame is transmitted on a logical LAPD link.
External comment:
--
Counter Name : NB_LAPD_RNR_REC Counter Integer
B10 LapD 1
B8 LapD 0
B9 LapD 1
Sub domain-2: Abis
Counter definition:
Number of Receive Not Ready (RNR) frames received on the LapD link.
Trigger condition:
Whenever an RNR Frame is received on a logical LAPD link.
External comment:
--
Alcatel-Lucent
Type name: X25 measurements
Type definition:
Set of counters related to the X25 links OMC-BSC
X3.20 Type 8 : X25 measurements
Counter Name : NB_X25_INC_CALL_SUCC_CLOSED Counter Integer
B10 X25 1
B8 X25 0
B9 X25 1
Sub domain-2: OMC-BSC
Domain: Traffic Load Sub domain-3: X25
Counter definition:
Number of incoming X.25 calls that are successfully closed by the BSC.
Trigger condition:
Whenever an incoming X.25 CALL is successfully closed.
External comment:
--
Alcatel-Lucent
Counter Name : NB_X25_OUT_CALL_SUCC_CLOSED Counter Integer
B10 X25 1
B8 X25 0
B9 X25 1
Domain: Traffic Load Sub domain-3: X25
Counter definition:
Number of outgoing X.25 calls that are successfully closed by the BSC.
Trigger condition:
Whenever an outgoing X.25 CALL is successfully closed.
External comment:
--
Counter Name : NB_X25_INC_CALL_ABNORM_CLOSED Counter Integer
B10 X25 1
B8 X25 0
B9 X25 1
Domain: Quality of Service Sub domain-3: X25
Counter definition:
Number of incoming X.25 calls that are closed in an abnormal way, as seen by the BSC.
Trigger condition:
Whenever an incoming X.25 CALL is closed in an abnormal way.
External comment:
--
Alcatel-Lucent
Counter Name : NB_X25_OUT_CALL_ABNORM_CLOSED Counter Integer
B10 X25 1
B8 X25 0
B9 X25 1
Domain: Quality of Service Sub domain-3: X25
Counter definition:
Number of outgoing X.25 calls that are closed in an abnormal way, as seen by the BSC.
Trigger condition:
Whenever an outgoing X.25 CALL is closed in an abnormal way.
External comment:
--
Alcatel-Lucent
Type name: N7 measurements
Type definition:
Set of counters related to the N7 Signalling Links. Note that in the BSS context, the Link Set and the
Route Set are identical.
N1.1 Type 9 : N7 measurements
Counter Name : TIME_N7_ALIGNED Counter Integer
B10 N7 Signalling Link 1
Sub domain-2: A
Counter definition:
Time (in seconds) during which the N7 SL is correctly aligned.
Trigger condition:
Whenever the No.7 Signalling channel between the MSC and BSS is correctly aligned, this counter will be
incremented every second.
External comment:
--
Alcatel-Lucent
Counter Name : NB_N7_CHANGEOVER Counter Integer
Sub domain-2: A
Domain: Quality of Service Sub domain-3: Layers1-2-3
Counter definition:
Number of changeovers from the primary (observed) N7 SL to another secondary one.
Trigger condition:
Whenever a changeover is made from using the primary signalling link to the secondary signalling link.
External comment:
--
Counter Name : NB_N7_CHANGEBACK Counter Integer
Sub domain-2: A
Counter definition:
Number of changebacks from the secondary (observed) N7 SL to the primary one.
Trigger condition:
Whenever a change back is made from using the secondary signalling link to the primary signalling link.
External comment:
--
Alcatel-Lucent
Counter Name : NB_N7_RESTORATION Counter Integer
Sub domain-2: A
Counter definition:
Number of N7 SL restorations (i.e. correctly aligned after a failure).
Trigger condition:
Whenever the No.7 Signalling channel between the MSC and BSS is correctly aligned after the removal of a
failure
condition, this counter will be incremented.
External comment:
--
Counter Name : NB_N7_LINK_FAIL_ANY_CAUSE Counter Integer
Sub domain-2: A
Counter definition:
Number of N7 SL failures (any reason).
Trigger condition:
1) Whenever a No.7 Signalling Link failure is detected due to an abnormal Forward Indicator Bit (FIB) being
received by the BSS.
2) Whenever a No.7 Signalling Link failure is detected due to an abnormal Backward Sequence Number (BSN)
being received by the BSS.
3) Whenever the timer supervising the reception of an acknowledgement message (T7) expires.
4) Whenever a No.7 Signalling Link failure is detected due to an excessive signal unit error rate being detected.
5) Whenever a No.7 Signalling Link failure is detected due to an excessive duration of Signalling Link congestion.
External comment:
--
Alcatel-Lucent
Counter Name : NB_N7_LINK_FAIL_FIB_BSN Counter Integer
Sub domain-2: A
Counter 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.
External comment:
--
Counter Name : NB_N7_LINK_FAIL_T7_EXP Counter Integer
Sub domain-2: A
Counter definition:
Number of N7 SL failures due to non acknowledgment in time.
Trigger condition:
Whenever the timer supervising the reception of an acknowledgement message (T7) expires.
External comment:
--
Alcatel-Lucent
Counter Name : NB_N7_LINK_FAIL_SU_ERROR_RATE Counter Integer
Sub domain-2: A
Counter definition:
Number of N7 SL failures due to exessive signal unit error rate.
Trigger condition:
Whenever a No.7 Signalling Link failure is detected due to an excessive Signal Unit error rate.
External comment:
--
Counter Name : NB_N7_LINK_FAIL_CONG Counter Integer
Sub domain-2: A
Counter definition:
Number of N7 SL failures due to congestion during an extended period of time.
Trigger condition:
Whenever a No.7 Signalling Link failure is detected due to an excessive duration of Signalling Link congestion.
External comment:
--
Alcatel-Lucent
Counter Name : NB_N7_LINK_FAIL_ALIGNMENT Counter Integer
Sub domain-2: A
Counter definition:
Number of N7 SL failures due to expiry of timer supervising the alignment.
Trigger condition:
Whenever the timer supervising the alignment of the Signalling Link (T2) expires.
External comment:
--
Counter Name : NB_N7_SU_REC_WITH_ERROR Counter Integer
Sub domain-2: A
Counter definition:
Number of Signalling Units received with errors on the N7 SL.
Trigger condition:
Whenever a Signalling Unit is received which is found to be in error.
External comment:
--
Alcatel-Lucent
Counter Name : NB_N7_NEG_ACK_REC Counter Integer
Sub domain-2: A
Counter definition:
Number of Negative Acknowledgment receieved on the N7 SL.
Trigger condition:
Whenever a Negative Acknowledgement (NACK) is received.
External comment:
--
Counter Name : TIME_N7_UNAVAIL_ERROR_SL Counter Integer
Sub domain-2: A
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : TIME_N7_UNAVAIL_MSC_PROC_OUTAGE Counter Integer
Sub domain-2: A
Counter 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.
External comment:
--
Counter Name : NB_N7_SIF_SIO_SENT Counter Integer
Sub domain-2: A
Domain: Traffic Load Sub domain-3: Layers1-2-3
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_N7_MSU_DISC_DUE_CONG Counter Integer
Sub domain-2: A
Counter 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.
External comment:
--
Counter Name : NB_N7_CONG_WITH_MSU_LOST Counter Integer
Sub domain-2: A
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_N7_OCTETS_RESENT Counter Integer
Sub domain-2: A
Counter definition:
Number of octets re-transmitted on the N7 SL.
Trigger condition:
Whenever an octet has to be re-transmitted.
External comment:
--
Counter Name : NB_N7_MSU_SENT Counter Integer
Sub domain-2: A
Counter definition:
Number of Message Signalling Units (MSU) transmitted on the N7 SL.
Trigger condition:
Whenever a Message Signalling Unit (MSU) is transmitted.
External comment:
--
Alcatel-Lucent
Counter Name : NB_N7_SIF_SIO_REC Counter Integer
Sub domain-2: A
Counter 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.
External comment:
--
Counter Name : NB_N7_MSU_REC Counter Integer
Sub domain-2: A
Counter definition:
Number of Message Signalling Units (MSU) received on the N7 SL.
Trigger condition:
Whenever a Message Signalling Unit (MSU) is received.
External comment:
--
Alcatel-Lucent
Counter Name : TIME_N7_UNAVAIL_CONG Counter Integer
Sub domain-2: A
Counter 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.
External comment:
--
Counter Name : TIME_N7_UNAVAIL_LINK_SET Counter Integer
B10 N7 Link Set 1
B8 N7 Link Set 0
B9 N7 Link Set 1
Sub domain-2: A
Counter definition:
Time (in seconds) during which the Link Set towards the MSC is not available on the N7.
Trigger condition:
Whenever the Link Set towards the MSC is unavailable, this counter will be updated every second.
External comment:
--
Alcatel-Lucent
Type number: Observation - 10
Type name: SDCCH observations
The maximum number of cells observed for this measurement type is 15 cells.
Type definition:
This measurement type provides observations on SDCCH channel.
An observation is composed of a set of records, each record being related to a single channel seizure
within the observed cell.
A record is a consistent structure of data made up of several fields (called DER) providing information
about the radio configuration and about specific events that are cumulated.
Not all channel seizures are observed in the cell, but one per sample_rate value.
For an observed SDCCH channel, the recording of data starts in the BSC as soon as 08.58CHANNEL
ACTIVATION is sent on Abis.
S01 Type 10 : SDCCH observations
Observation Name : CHANNEL_ID (SCCH) Length: 5
Measured number
Observation
The SDCCH sub-channel identity to which the observation relates, including BTS number, sector number, TRX
number, TRX timeslot and sub-channel.
Note : the sub-channel field may take a value contained between 0 and 7.
External comment:
--
Observation Name : CHAN_SEIZ_TIME Length: 16
Measured Date/Time
Observation
The Absolute Date and Time at which the SDCCH Sub-channel was activated (i.e. when the 48.058 CHANNEL
ACTIVATION message was sent to the CELL).

The time is accurate to tenths of seconds.
External comment:
--
Alcatel-Lucent
Observation Name : CHAN_RELEASE_TIME Length: 16
Measured Date/Time
Observation
The Absolute Date and Time at which the SDCCH Sub-channel was released (i.e. when the 48.058 RF CHANNEL
RELEASE ACKNOWLEDGE message was received from the CELL or when the T_RCR_ACK timer expires for
the
second time).

The time is accurate to tenths of seconds.
External comment:
--
Observation Name : END_INDICATION (SDCCH) Length: 1
Measured number
Observation
Describes how the SDCCH sub-channel was released. Viz.:

0/ successful release of SDCCH sub-channel, initiated either by the MS, the NSS or the BSS in case of handover

1: LAPD failure

2: other BSS problems
- unsuccessful channel activation
- transcoder failure on the old channel in case of SDCCH normal assignment (TCH -> SDCCH)
- hardware failure (BSC or BTS or transmission equipment)
- software failure (BSC or BTS or transmission equipment)

3: radio failures during the channel established phase: radio link failures or LAPDm failures
- 48.058 CONNECTION FAILURE INDICATION message received with a cause value of "radio link failure"
- 48.058 ERROR INDICATION message received

4: MS access problems during the channel establishment phase or a channel change procedure
- T3101 expiry during immediate assignment
- 44.018 ASSIGNMENT FAILURE received during SDCCH normal assignment or internal intra-cell SDCCH
handover
- T3107 expiry during normal assignment (SDCCH or TCH) or internal intra-cell SDCCH handover
- T3103 expiry during internal inter-cell SDCCH handover or internal directed retry
- 44.018 HANDOVER FAILURE message received during internal inter-cell SDCCH handover
- 48.058 CONNECTION FAILURE INDICATION message received with a cause value of "handover access
failure"
during internal inter-cell SDCCH handover or external SDCCH handover
- T9113 expiry during external SDCCH handover
- T8 expiry during 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 channel change
procedure is
considered as successful.
-48.008 CLEAR COMMAND message received with a cause value of "radio interface failure - reversion to old
channel"
during external SDCCH handover.
External comment:
--
Alcatel-Lucent
Observation Name : SEIZURE_TYPE (SDCCH) Length: 1
Measured number
Observation
Describes the purpose for which the SDCCH sub-channel was seized. Viz :
0: Mobile Originating Call (MO) excluding procedures corresponding to values 2, 5, 6, 7, 8, 9 & 10
1: Mobile Terminating transaction (MT)
2: MO : call re-establishment
3: the sub-channel was allocated but was never seized by the mobile
4: the sub-channel was a target of an SDCCH handover or a TCH to SDCCH assignment
5: MO : Location Updating Request
6: MO : Location Updating Request - Follow on
7: MO : Short Message Service
8 : MO : Supplementary Service
9 : MO : IMSI detach indication
10: MO : Emergency Call

The table below summerises information about the seizure and release of the observed SDCCH channel. S05
provides in formation on channel seizure. S04 provides information on channel release.
---------------------------------------------------------------------------------------------------------------------------------------
S05/ | 3: | 0,1,2,5,6,7,8,9,10: | 4:
|
| chan not seized by the MS | chan seized by the MS as part | chan seized by the MS as
part |
| as part of any SDCCH | of immediate assignment | of SDCCH handover or
|
S04 | transaction | | SDCCH normal
assignment |
---------------------------------------------------------------------------------------------------------------------------------------
0: normal rel | applicable for NSS release | applicable for MS, NSS, and BSS | applicable for MS, NSS and
BSS |
req by MS, | only | release | release
|
NSS, or BSS | | |
|
----------------------------------------------------------------------------------------------------------------------------------------
1,2 : abnormal | applicable | applicable | applicable
|
rel. due to BSS | | |
|
problem | | |
|
----------------------------------------------------------------------------------------------------------------------------------------
3 : abnormal | not applicable | applicable | applicable
|
rel due to radio | | |
|
link failure | | |
|
-----------------------------------------------------------------------------------------------------------------------------------------
4 : abnormal | applicable for : | applicable for : | applicable for :
|
release due to | - immediate assignment | - TCH normal assignment | - SDCCH handover (old
channel) |
MS access pb | - SDCCH normal assignt | - internal directed retry |
|
| - SDCCH handover (new | - SDCCH handover (old channel) |
|
| channel) | |
Alcatel-Lucent

unit:
definition:
|
--------------------------------------------------------------------------------------------------------------------------------------
Notes :

1) S04=4 and S05=3 means :
- S05=3 : observed SDCCH channel not seized by the mobile
- S04=4 : MS access problems on observed SDCCH channel
Observed SDCCH channel released before having been seized by the mobile (SDCCH is the target channel for
immediate assignment, SDCCH normal assignment or SDCCH handover)

2) S04=4 and S05=0,1,2,5,6,7,8,9 or 10 means :
- S05 = 0,1,2,5,6,7,8,9 or 10 : observed SDCCH channel seizure by the mobile as the result of an immediate
assignment (specific usage is given by the value of S05)
- S04 = 4 : MS problem on accessing a new channel
Observed SDCCH channel first seized by the mobile as the result of an immediate assignment and then released
during a channel change procedure (TCH normal assignment, internal directed retry, SDCCH handover)

3) S04=4 and S05=4 means :
- S05=4 : observed SDCCH channel seized by the mobile as the result of an SDCCH normal assignment or of an
SDCCH handover External comment:
- S04=4 : MS problem on accessing a new channel
Observed SDCCH channel first seized by the mobile as the result of an SDCCH nomal assignment or of an
SDCCH --
handover and then released during an SDCCH handover.
Observation Name : MS_POWER Length: 2
Measured dB
Observation
Indicates the last commanded MS Power Level on the SACCH Channel to the Mobile.

This counter corresponds to the MS_POWER field of the 48.058 PHYSICAL CONTEXT CONFIRM message.
External comment:
--
Observation Name : BS_POWER Length: 2
Measured dB
Observation
Indicates the last commanded BS Power Level to the encoder.

This counter corresponds to the BS_POWER field of the 48.058 PHYSICAL CONTEXT CONFIRM message.
External comment:
--
Alcatel-Lucent
Observation Name : TIMING_ADVANCE Length: 2
Measured bper
Observation
Indicates the last commanded Timing Advance on the SACCH Channel to the Mobile.

This counter corresponds to the TIMING_ADVANCE field of the 48.058 PHYSICAL CONTEXT CONFIRM
message.
External comment:
--
Observation Name : NB_FRAMES_NOT_REPEATED Length: 2
Measured number
Observation
Indicates the number of SAPI 0 frames that were not repeated.

This counter corresponds to the CNT_I_TX field of the 48.058 PHYSICAL CONTEXT CONFIRM message.
External comment:
--
Observation Name : NB_FRAMES_REPEATED Length: 2
Measured number
Observation
Indicates the number of SAPI 0 frames that were repeated at least once.

This counter corresponds to the CNT_I_RETX field of the 48.058 PHYSICAL CONTEXT CONFIRM message.
External comment:
--
Observation Name : NB_SABM_AFTER_UA_SENT Length: 1
Measured number
Observation
Indicates the number of SABM received on SAPI 0 when UA has already been sent (i.e. SABM received in
established or timer recovery state).

This counter corresponds to the CNT_SABM_RX field of the 48.058 PHYSICAL CONTEXT CONFIRM message.
External comment:
--
Alcatel-Lucent
Observation Name : NB_PHYSICAL_INFO_SENT Length: 1
Measured number
Observation
Indicates the number of times 44.018 PHYSICAL INFORMATION message has been sent in case of
asynchronous
handover.

This counter corresponds to the CNT_PHY_INFO_TX field of the 48.058 PHYSICAL CONTEXT CONFIRM
message.
External comment:
--
Observation Name : NB_ERRONEOUS_FRAMES_SENT Length: 1
Measured number
Observation
Indicates the number of erroneous frames that were received.

This counter corresponds to the CNT_ERR_RX field of the 48.058 PHYSICAL CONTEXT CONFIRM message.
External comment:
--
Observation Name : NB_REJ_FRAMES_SENT Length: 1
Measured number
Observation
Indicates the number of Reject (REJ) frames that were transmitted.

This counter corresponds to the CNT_REJ_TX field of the 48.058 PHYSICAL CONTEXT CONFIRM message.
External comment:
--
Observation Name : NB_REJ_FRAMES_RECEIVED Length: 1
Measured number
Observation
Indicates the number of Reject (REJ) frames that were received.

This counter corresponds to the CNT_REJ_RX field of the 48.058 PHYSICAL CONTEXT CONFIRM message.
External comment:
--
Alcatel-Lucent
Observation Name : NB_MS_TX_PWR_MAX_SENT Length: 1
Measured number
Observation
This counter indicates the number of 48.058 CONNECTION FAILURE INDICATION messages that were sent to
the
BSS with a cause value of "set YY_TXPWR_M".

This counter corresponds to the CNT_MS_TXPWR_MAX field of the 48.058 PHYSICAL CONTEXT CONFIRM
message.
External comment:
--
Observation Name : RADIO_LINK_FAILURE_INDICATION Length: 1
Measured number
Observation
Indicates whether or not a Radio Link Failure was detected or not.

0: No connection failure occurred on the SDCCH Sub-channel
1: A 48.058 CONNECTION FAILURE INDICATION message was received with a cause value of "radio link
failure".

This counter corresponds to the RL_FAILURE_INDICATOR field of the 48.058 PHYSICAL CONTEXT CONFIRM
message.
External comment:
--
Observation Name : PERC_INCOR_SACCH_FRAMES_REC Length: 1
Measured %
Observation
Indicates the percentage of SACCH frames that could not be decoded.

This counter corresponds to the CNT_SA_BFI_RX/CNT_SA_RX field of the 48.058 PHYSICAL CONTEXT
CONFIRM
message.
External comment:
--
Alcatel-Lucent
Observation Name : PERC_INCOR_SDCCH_FRAMES_REC Length: 1
Measured %
Observation
Indicates the percentage of SDCCH frames that could not be decoded.

This counter corresponds to the CNT_SD_BFI_RX/CNT_SD_RX field of the 48.058 PHYSICAL CONTEXT
CONFIRM
message.
External comment:
--
Observation Name : SAMPLE_RATE Length: 1
Measured number
Observation
Indicates the sample rate value at the time the observation is collected.
External comment:
--
Alcatel-Lucent
Type name: TCH measurements observations
Type scope (per BSS): One cell
The maximum number of cells observed for this measurement type is 1 cell.
Type definition:
This measurement type provides observations on the 48.058 MEASUREMENT REPORTS for a TCH
(in HR or FR usage) channel.
The counters related to GSM neighbour cells can be repeated for up to 32 neighbour cells. The
concerned counters are named eg "Rnn13" were "nn" belongs to the range 00 to 31.
The counters related to 3G neighbour cells can be repeated for up to 8 neighbour cells. The concerned

counters are named eg "Rn18" were "n" belongs to the range 0 to 8.
For an observed channel, the recording of data starts in the BSC as soon as 48.058 MEASUREMENT
REPORT is received on Abis by the BSC.
R01 Type 11 : TCH measurements observations
Observation Name : CHANNEL_ID (TCH) Length: 5
Measured number
Observation
The RTCH channel identity to which the Observation relates, including BTS Number, Sector Number, TRX
Number,
TRX Timeslot and Sub-channel which is only significant in case of an half rate TCH channel.

Note : The sub-channel field may take a value contained between 0 and 1 in case of an half rate TCH channel. In
case of a full rate TCH channel the sub-channel field which is not significant is set to zero.
External comment:
--
R01a Type 11 : TCH measurements observations
Observation Name : RTCH_TYPE Length: 1
Measured number
Observation
The RTCH channel type to which the Observation relates :

0: for a full rate RTCH channel
1: for an half rate RTCH channel.
External comment:
--
Alcatel-Lucent
Observation Name : RECEIVED_TIMESTAMP Length: 16
Measured Date/Time
Observation
The Absolute Date and Time at which the measurement result message was received from the CELL by the BSS.
The time is accurate to tenths of a second.
External comment:
--
Observation Name : AV_RXLEV_UL_HO (11) Length: 1
Measured dBm
Observation
Indicates the average receive uplink level of the serving cell, as used by the handover algorithm.
External comment:
--
Observation Name : AV_RXLEV_UL_MCHO (11) Length: 1
Measured dBm
Observation
This observation data is only related to microcellular environment. It indicates the average receive uplink level of
the
serving cell, as used by the handover algorithm.
External comment:
--
Observation Name : AV_RXLEV_DL_HO (11) Length: 1
Measured dBm
Observation
Indicates the average receive downlink level of the serving cell, as used by the handover algorithm.
External comment:
--
Alcatel-Lucent
Observation Name : AV_RXLEV_DL_MCHO (11) Length: 1
Measured dBm
Observation
This observation data is only related to microcellular environment. It indicates the average receive downlink level
of
the serving cll, as used by the handover algorithm.
External comment:
--
Observation Name : AV_RXLEV_PBGT_HO (11) Length: 1
Measured dBm
Observation
Indicates the average received Downlink Level of the serving cell, as used by the Power Budget algorithm.
External comment:
--
Observation Name : AV_RXQUAL_UL_HO (11) Length: 1
Measured number
Observation
Indicates the average receive uplink quality of the serving cell, as used by the handover algorithm.
External comment:
--
Observation Name : AV_RXQUAL_DL_HO (11) Length: 1
Measured number
Observation
Indicates the average receive downlink quality of the serving cell, as used by the handover algorithm.
External comment:
--
Alcatel-Lucent
Observation Name : AV_RANGE_HO (11) Length: 1
Measured sec
Observation
Indicates the average distanc between Mobile and Base station, as used by the handover algorithm.
External comment:
--
Observation Name : MS_TXPWR Length: 1
Measured dBm
Observation
Transmit power at the Mobile.
External comment:
--
Observation Name : BSIC Length: 1
Measured number
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation Name : BCCH_FREQ Length: 2
Measured number
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Alcatel-Lucent
Observation Name : AV_RXLEV_NCELL Length: 1
Measured dBm
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Observation Name : PBGT Length: 1
Measured dBm
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation Name : BS_TXPWR Length: 1
Measured dB
Observation
Transmit power at the BTS.
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Observation Name : SCRAMBLING_CODE Length: 2
Measured number
Observation
The scrambling code of a 3G FDD neighboring cell.
External comment:
--
Alcatel-Lucent
Observation Name : FDD_FREQ Length: 2
Measured number
Observation
The UTRAN Absolute Radio Frequency Number of a 3G FDD neighboring cell.
External comment:
--
Observation Name : BTSNUM Length: 1
Measured number
Observation
Indicates the number of neighboring cells for which measurements made by the Mobile are available during the
averaging interval. Measurements of up to 32 Neighboring cells can be provided.
External comment:
--
Observation Name : AV_ECNO Length: 1
Measured dBm
Observation
The average receive Ec/No of a 3G FDD neighboring cell as seen by the Mobile.
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Type name: Internal handover observations
Type definition:
This measurement type provides observations on internal intra-cell or inter-cell SDCCH or TCH (in HR
or FR usage) handover.
For an observed channel, the recording of data starts in the BSC as soon as 04.08HANDOVER
COMMAND (for inter-cell handover) or 04.08ASSIGNMENT COMMAND (for intra-cell handover) is sent
on Abis by the BSC.
HO1 Type 12 : Internal handover observations
Observation Name : SIGNALLING_TRAFFIC_IND Length: 1
Measured number
Observation
Indicates whether or not the observation record relates to an SDCCH handover or RTCH handover attempt. Valid
coding is provided below, all other codings are invalid.

0: handover was for an SDCCH Sub-channel
1: handover was for an RTCH channel.
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Observation Name : FREQ Length: 2
Measured number
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation Name : RXLEV Length: 4
Measured dBm
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Alcatel-Lucent
Observation Name : HO_CAUSE Length: 1
Measured number
Observation
Indicates the reason for the external handover attempt.

Valid codings for handovers are as follows in the left column of the table below.
All other codings are invalid.

The right column of the table gives the causes reported to the MSC on the A interface in the 48.008 HANDOVER
REQUIRED message and which are in accordance with GSM 48.008 .
ALCATEL BSS causes for Emergency handovers | A interface GSM 48.008 cause value
------------------------------------------------------------------------------------------------------------------------------------
7: several consecutive bad SACCH frames received in a micro-cell | 0000010: uplink quality
17: too low level on the uplink in a microcell compared to a high | 0000011: uplink strength
threshold |
18: too low level on the downlink in a microcell compared to a high | 0000101: downlink strength
threshold |
2: too low quality on the uplink | 0000010: uplink quality
4: too low quality on the downlink | 0000100: downlink quality
3: too low level on the uplink | 0000011: uplink strength
5: too low level on the downlink | 0000101: downlink strength
6: too long MS-BTS distance | 0000110: distance

ALCATEL BSS causes for Better cell handovers | A interface GSM 48.008 cause value
----------------------------------------------------------------------------------------------------------------------------------
14: high level in neighbour overlaid cell for slow MS | 0001100: better cell
12: too low power budget ("better cell") | 0000011: better cell
21: preferred band handover | 0001100: better cell
23: traffic handover | 0001111: traffic

remark : causes numbered 8 & 9 have been removed for release 4.

- Causes 2, 3, 4, 5 & 6 apply to any kind of serving cells (macro/micro, single layer/lower layer/upper layer,
normal/concentric).
As these causes are internal to the cell, there is no constraint relatively to the cell environment.
- Causes 7, 17, 18 apply only to serving micro-cells.
As cause 7 is internal to the cell, the target cell may be a neighbour upper layer cell or a neighbour micro-cell.
Causes 17 & 18 apply to a serving micro-cell handover towards a target upper layer cell.
- Cause 12 applies to both serving and target neighbour cells belonging to the same layer whatever their size is.
For
macro/micro cells, this cause applies to handovers :
from single layer to single layer
from single layer to upper layer
from upper layer to upper layer
from upper layer to single layer
from lower layer to lower layer
- Cause 14 applies to a serving upper layer cell handover towards a target macro/micro lower layer cell.
- Cause 21 applies to handover from a serving cell of the classical band towards a target cell of the preferred
band.
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Observation Name : SYNCHRONIZED Length: 1
Measured number
Observation
Indicates whether or not the observed external incoming handover is between 2 synchronized BTS. Valid coding
is
provided below, all other codings are invalid.

0: The Target and Serving BTS are not synchronized
1: The Target and Serving BTS are synchronized.

It should be noted that synchronized external handovers only occur when they are Intra-BSS.
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Observation Name : INTRA_INTER_CELL_IND Length: 1
Measured number
Observation
Indicates whether or not the observation record relates to an intra-cell handover or an inter-cell handover
attempt.
Valid coding is provided below, all other codings are invalid.

0: An intra-cell handover was attempted
1: An inter-cell handover was attempted.
External comment:
--
Observation Name : A_LEV_HO Length: 1
Measured Samfr
Observation
Averaging window size for calculating the Uplink and Downlink Levels of the serving cell. This value is in the range
1
to 31 SACCH Multi-frames.
External comment:
--
Alcatel-Lucent
HO23a Type 12 : Internal handover observations
Observation Name : A_LEV_MCHO Length: 1
Measured Samfr
Observation
This Observation data is only related to microcellular environment. It is the averaging window size for calculating
the
Uplink and Downlink Levels of the serving cell in a microcellular environment. This value is in the range 1 to 15
SACCH Multi-frames.
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured dBm
Observation
The last average Uplink Level of the serving cell.
External comment:
--
Measured dBm
Observation
This Observation data is only related to microcellular environment. It is the last average Uplink Level for microcell
handover purposes of the serving cell.
External comment:
--
Measured dBm
Observation
The last average Downlink Level of the serving cell.
External comment:
--
Measured dBm
Observation
This Observation data is only related to microcellular environment. It indicates the average receive Downlink Level
of
the serving cell, as used by the handover algorithm.
External comment:
--
Alcatel-Lucent
Observation Name : A_PBGT_HO Length: 1
Measured Samfr
Observation
Averaging window size for calculating the Power Budget of the serving cell relating to the neighbouring cells. This
value is in the range 1 to 31 SACCH Multi-frames.
External comment:
--
Measured dBm
Observation
The last average Downlink Power Budget of the serving cell.
External comment:
--
Observation Name : HO_REQUIRED_TIME_STAMP Length: 16
Measured Date/Time
Observation
Indicates the Absolute Date and Time at which the 48.008 HANDOVER REQUIRED message was sent. The time
is
accurate to tenths of seconds.
External comment:
--
Observation Name : A_QUAL_HO Length: 1
Measured Samfr
Observation
Averaging window size for calculating the Uplink and Downlink Qualities of the serving cell. This value is in the
range
1 to 31 SACCH Multi-frames.
External comment:
--
Alcatel-Lucent
Measured number
Observation
The last average Uplink Quality of the serving cell.
External comment:
--
Measured number
Observation
The last average Downlink Quality of the serving cell.
External comment:
--
Observation Name : A_RANGE_HO Length: 1
Measured Samfr
Observation
Averaging window size for calculating the Distance of the serving cell. This value is in the range 1 to 31 SACCH
Multi-frames.
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured sec
Observation
The last average Distance of the serving cell.
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured dB
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Observation Name : OLD_CHANNEL_ID Length: 5
Measured number
Observation
The serving channel identity of the external handover, including BTS Number, Sector Number, TRX Number, TRX
Timeslot, and Sub-channel which is only significant in case of an SDCCH channel or in case of an half rate TCH
channel.

Note : The sub-channel field may take a value contained between 0 and 7 in case of an SDCCH channel. It may
take
a value contained between 0 and 1 in case of an half rate TCH channel. In case of a full rate TCH channel the
sub-channel field which is not significant is set to zero.
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Observation Name : OLD_RTCH_TYPE Length: 1
Measured number
Observation
This counter is only relevant in case the serving channel is an RTCH channel.

The serving channel type of the internal handover to which the Observation relates :

1: for an half rate RTCH channel

In case of an SDCCH channel, the non-significant value 0xFF is used.
External comment:
--
Observation Name : NEW_CHANNEL_ID Length: 5
Measured number
Observation
The target channel identity of the external incoming handover, including BTS Number, Sector Number, TRX
Number,
TRX Timeslot, and Sub-channel which is only significant in case of an SDCCH channel or in case of an half rate
TCH
channel. If the target channel identity is not known, then the BTS Number and Sector Number are provided, and
TRX
Number, TRX Timeslot, and Sub-channel are set to zero.

Note : The sub-channel field may take a value contained between 0 and 7 in case of an SDCCH channel. It takes
a
value contained between 0 and 1 in case of an half rate TCH channel. In case of a full rate TCH channel the
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Observation Name : NEW_RTCH_TYPE Length: 1
Measured number
Observation
This counter is only relevant in case the target channel is an RTCH channel.

The target channel type of the internal handover to which the Observation relates :


External comment:
--
Alcatel-Lucent
Observation Name : INT_HO_SUCCESS_FAILURE_IND Length: 1
Measured number
Observation
Indicates whether the observed internal handover is successful or not. Valid coding is provided below, all other
codings are invalid.

0: Successful handover
- 44.018 HANDOVER COMPLETE or 44.018 ASSIGNMENT COMPLETE message was received during an
internal
handover

1: LAPD failure

2: Other BSS problems

3: MS access problems where the mobile reverts to the old channel
- 44.018 HANDOVER FAILURE or 44.018 ASSIGNMENT FAILURE message was received during an internal
handover

4: MS access problems where the mobile does not revert to the old channel
- T3103 expiry (internal intercell handover)
- T3107 expiry (internal intracell handover
- 48.058 CONNECTION FAILURE INDICATION(radio interface failure) or 48.058 ERROR INDICATION(any
cause) was
received during an internal handover
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Observation Name : MS_SPEED Length: 1
Measured number
Observation
This Observation data is only related to microcellular environment. It is an estimation for mobile speed
discrimination
process used to initiate or not a handover from an upper layer cell to an lower layer cell. The coding of this
parameter
is the following:
- 0 : indefinite
- 1 : slow
- 2 : fast
External comment:
--
Observation Name : HO_DURATION Length: 2
Measured 100ms
Observation
Indicates the time in tenths of seconds between the sending of the 44.018 HANDOVER COMMAND message and
the reception of the 44.018 HANDOVER COMPLETE message for an internal inter-cell handover.

Indicates the time in tenths of seconds between the sending of the 44.018 ASSIGNMENT COMMAND message
and
the reception of the 44.018 ASSIGNMENT COMPLETE message for an internal intra-cell handover.
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Type name: Incoming external handover observations
Type definition:
This measurement type provides observations on incoming external SDCCH or TCH (in HR or FR
usage) handover.
For an observed channel, the recording of data starts in the BSC as soon as 08.08HANDOVER
REQUEST is sent on A interface by the BSC.
HO40 Type 13 : Incoming external handover observations
Measured number
Observation

External comment:
--
Observation Name : INCOMING_HO_IND Length: 1
Measured number
Observation
Indicates whether or not the observation record relates to an external incoming handover. Valid coding is provided
below, all other codings are invalid.

1: handover was external incoming to the identified channel.
External comment:
--
Alcatel-Lucent
Observation Name : HO_REQUEST_TIME_STAMP Length: 16
Measured Date/Time
Observation
Indicates the Absolute Date and Time at which the 48.008 HANDOVER REQUEST message was received. The
time
is accurate to tenths of seconds.
External comment:
--
Observation Name : NEW_CHANNEL_ID Length: 5
Measured number
Observation
The target channel identity of the external incoming handover, including BTS Number, Sector Number, TRX
Number,
TRX Timeslot, and Sub-channel which is only significant in case of an SDCCH channel or in case of an half rate
TCH
channel. If the target channel identity is not known, then the BTS Number and Sector Number are provided, and
TRX
Number, TRX Timeslot, and Sub-channel are set to zero.

Note : The sub-channel field may take a value contained between 0 and 7 in case of an SDCCH channel. It takes
a
value contained between 0 and 1 in case of an half rate TCH channel. In case of a full rate TCH channel the
External comment:
--
HO43a Type 13 : Incoming external handover observations
Observation Name : NEW_RTCH_TYPE Length: 1
Measured number
Observation
This counter is only relevant in case the target channel is an RTCH channel.

The target channel type of the internal handover to which the Observation relates :


External comment:
--
Alcatel-Lucent
Observation Name : INC_EXT_HO_SUCCESS_FAILURE_IND Length: 1
Measured number
Observation
Indicates whether the observed incomming external handover is successful or not. Valid coding is provided below,
all
other codings are invalid.

0: Successful handover
- 44.018 HANDOVER COMPLETE message was received during an incoming external handover

1: LAPD failure


- 48.008 CLEAR COMMAND(radio interface failure, reversion to old channel) message was received while waiting
for
an answer from the MS
- an SCCP connection was released while waiting an answer from the MS or a CLEAR COMMAND
- T9113 expiry during an incoming external handover
- 48.058 CONNECTION FAILURE INDICATION(handover access failure) message was received

- 48.008 CLEAR COMMAND message was received before having sent HANDOVER COMMAND to the MS
- 48.008 CLEAR COMMAND(any cause but radio interface failure, reversion to old channel) message was
received
while waiting for an answe from the MS
- RESET message was received from the MSC
External comment:
--
Observation Name : SYNCHRONIZED Length: 1
Measured number
Observation
Indicates whether or not the observed external incoming handover is between 2 synchronized BTS. Valid coding
is
provided below, all other codings are invalid.

0: The Target and Serving BTS are not synchronized
1: The Target and Serving BTS are synchronized.

It should be noted that synchronized external handovers only occur when they are Intra-BSS.
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Alcatel-Lucent
Type name: Outgoing external handover observations
Type definition:
This measurement type provides observations on outgoing external SDCCH or TCH (in HR or FR
usage) handover.
For an observed channel, the recording of data starts in the BSC as soon as 48.008 HANDOVER
COMMAND is received on A interface by the BSC.
HO10100 Type 14 : Outgoing external handover observations
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation

External comment:
--
Observation Name : OUTGOING_HO_IND Length: 1
Measured number
Observation
Indicates whether or not the observation record relates to an external outgoing handover. Valid coding is provided
below, all other codings are invalid.

0: handover was external outgoing from the identified channel.
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Observation Name : HO_REQUIRED_TIME_STAMP Length: 16
Measured Date/Time
Observation
Indicates the Absolute Date and Time at which the 48.008 HANDOVER REQUIRED message was sent. The time
is
accurate to tenths of seconds.
External comment:
--
Alcatel-Lucent
Observation Name : HO_REQUIRED_NB Length: 2
Measured number
Observation
Indicates the number of BSS generated 48.008 HANDOVER REQUIRED messages generated during the
handover
procedure.
External comment:
--
Observation Name : OLD_CHANNEL_ID Length: 5
Measured number
Observation
The serving channel identity of the external handover, including BTS Number, Sector Number, TRX Number, TRX
Timeslot, and Sub-channel which is only significant in case of an SDCCH channel or in case of an half rate TCH
channel.

Note : The sub-channel field may take a value contained between 0 and 7 in case of an SDCCH channel. It may
take
a value contained between 0 and 1 in case of an half rate TCH channel. In case of a full rate TCH channel the
External comment:
--
HO64a Type 14 : Outgoing external handover observations
Observation Name : OLD_RTCH_TYPE Length: 1
Measured number
Observation
This counter is only relevant in case the serving channel is an RTCH channel.

The serving channel type of the internal handover to which the Observation relates :


External comment:
--
Alcatel-Lucent
Observation Name : OUT_EXT_HO_SUCCESS_FAILURE_IND Length: 1
Measured number
Observation
Indicates whether the observed external handover is successful or not. Valid coding is provided below, all other
codings are invalid.

0: Successful handover or call released while external handover
- 48.008 CLEAR COMMAND message received with a cause value of "handover successful" during external
handover

- 48.008 CLEAR COMMAND message received with a cause value of "normal event/call control" while T8 is
running

1: LAPD failure


- 44.018 HANDOVER FAILURE message received during external handover

- T8 expiry during external handover or a 48.058 ERROR INDICATION(any cause) message is received
External comment:
--
Alcatel-Lucent
Observation Name : HO_CAUSE Length: 1
Measured number
Observation
Indicates the reason for the external handover attempt.

Valid codings for handovers are as follows in the left column of the table below.
All other codings are invalid.

The right column of the table gives the causes reported to the MSC on the A interface in the 48.008 HANDOVER
REQUIRED message and which are in accordance with GSM 48.008 .
ALCATEL BSS causes for Emergency handovers | A interface GSM 48.008 cause value
------------------------------------------------------------------------------------------------------------------------------------
7: several consecutive bad SACCH frames received in a micro-cell | 0000010: uplink quality
17: too low level on the uplink in a microcell compared to a high | 0000011: uplink strength
threshold |
18: too low level on the downlink in a microcell compared to a high | 0000101: downlink strength
threshold |
2: too low quality on the uplink | 0000010: uplink quality
4: too low quality on the downlink | 0000100: downlink quality
3: too low level on the uplink | 0000011: uplink strength
5: too low level on the downlink | 0000101: downlink strength
6: too long MS-BTS distance | 0000110: distance

ALCATEL BSS causes for Better cell handovers | A interface GSM 48.008 cause value
----------------------------------------------------------------------------------------------------------------------------------
14: high level in neighbour overlaid cell for slow MS | 0001100: better cell
12: too low power budget ("better cell") | 0000011: better cell
21: preferred band handover | 0001100: better cell
23: traffic handover | 0001111: traffic

remark : causes numbered 8 & 9 have been removed for release 4.

- Causes 2, 3, 4, 5 & 6 apply to any kind of serving cells (macro/micro, single layer/lower layer/upper layer,
normal/concentric).
As these causes are internal to the cell, there is no constraint relatively to the cell environment.
- Causes 7, 17, 18 apply only to serving micro-cells.
As cause 7 is internal to the cell, the target cell may be a neighbour upper layer cell or a neighbour micro-cell.
Causes 17 & 18 apply to a serving micro-cell handover towards a target upper layer cell.
- Cause 12 applies to both serving and target neighbour cells belonging to the same layer whatever their size is.
For
macro/micro cells, this cause applies to handovers :
from single layer to single layer
from single layer to upper layer
from upper layer to upper layer
from upper layer to single layer
from lower layer to lower layer
- Cause 14 applies to a serving upper layer cell handover towards a target macro/micro lower layer cell.
- Cause 21 applies to handover from a serving cell of the classical band towards a target cell of the preferred
band.
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Observation Name : MS_SPEED Length: 1
Measured number
Observation
This Observation data is only related to microcellular environment. It is an estimation for mobile speed
discrimination
process used to initiate or not a handover from an upper layer cell to an lower layer cell. The coding of this
parameter
is the following:
- 0 : indefinite
- 1 : slow
- 2 : fast
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Observation Name : A_LEV_HO Length: 1
Measured Samfr
Observation
Averaging window size for calculating the Uplink and Downlink Levels of the serving cell. This value is in the range
1
to 31 SACCH Multi-frames.
External comment:
--
Observation Name : A_LEV_MCHO Length: 1
Measured Samfr
Observation
This Observation data is only related to microcellular environment. It is the averaging window size for calculating
the
Uplink and Downlink Levels of the serving cell in a microcellular environment. This value is in the range 1 to 15
SACCH Multi-frames.
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dBm
Observation
The last average Uplink Level of the serving cell.
External comment:
--
Alcatel-Lucent
Measured dBm
Observation
This Observation data is only related to microcellular environment. It is the last average Uplink Level for microcell
handover purposes of the serving cell.
External comment:
--
Measured dBm
Observation
The last average Downlink Level of the serving cell.
External comment:
--
Measured dBm
Observation
This Observation data is only related to microcellular environment. It indicates the average receive Downlink Level
of
the serving cell, as used by the handover algorithm.
External comment:
--
Observation Name : A_PBGT_HO Length: 1
Measured Samfr
Observation
Averaging window size for calculating the Power Budget of the serving cell relating to the neighbouring cells. This
value is in the range 1 to 31 SACCH Multi-frames.
External comment:
--
Alcatel-Lucent
Measured dBm
Observation
The last average Downlink Power Budget of the serving cell.
External comment:
--
Observation Name : A_QUAL_HO Length: 1
Measured Samfr
Observation
Averaging window size for calculating the Uplink and Downlink Qualities of the serving cell. This value is in the
range
1 to 31 SACCH Multi-frames.
External comment:
--
Measured number
Observation
The last average Uplink Quality of the serving cell.
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Measured number
Observation
The last average Downlink Quality of the serving cell.
External comment:
--
Observation Name : A_RANGE_HO Length: 1
Measured Samfr
Observation
Averaging window size for calculating the Distance of the serving cell. This value is in the range 1 to 31 SACCH
Multi-frames.
External comment:
--
Measured dBm
Observation
External comment:
--
Alcatel-Lucent
Measured sec
Observation
The last average Distance of the serving cell.
External comment:
--
Measured dBm
Observation
External comment:
--
Measured dB
Observation
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Measured number
Observation
External comment:
--
Alcatel-Lucent
Type name: TCH observation
Type definition:
This measurement type provides observations on the TCH channel.
For an observed channel, the recording of data starts in the BSC as soon as 08.58CHANNEL
ACTIVATION is sent on Abis interface by the BSC.
T01 Type 15 : TCH observation
Observation Name : CHANNEL_ID (TCH) Length: 5
Measured number
Observation
The RTCH channel identity to which the Observation relates, including BTS Number, Sector Number, TRX
Number,
TRX Timeslot and Sub-channel which is only significant in case of an half rate TCH channel.

Note : The sub-channel field may take a value contained between 0 and 1 in case of an half rate TCH channel. In
case of a full rate TCH channel the sub-channel field which is not significant is set to zero.
External comment:
--
T01a Type 15 : TCH observation
Observation Name : RTCH_TYPE Length: 1
Measured number
Observation
The RTCH channel type to which the Observation relates :

1: for an half rate RTCH channel.
External comment:
--
Alcatel-Lucent
Observation Name : CHANNEL_SEIZURE_TIME Length: 16
Measured Date/Time
Observation
The Absolute Date and Time at which the RTCH channel was activated (i.e. when the 48.058 CHANNEL
ACTIVATION message was sent to the CELL).

External comment:
--
Observation Name : CHANNEL_RELEASE_TIME Length: 16
Measured Date/Time
Observation
The Absolute Date and Time at which the RTCH channel was released (i.e. when the 48.058 RF CHANNEL
RELEASE ACKNOWLEDGE message was received from the CELL or when the T_RCR_ACK timer expires for
the
second time).

External comment:
--
Alcatel-Lucent
Observation Name : END_INDICATION (TCH) Length: 1
Measured number
Observation
Describes how the RTCH channel is released. Viz. :

0: Successful release of RTCH channel
- initiated either by the MS, the NSS or the BSS in case of handover

1: LAPD failure

- unsuccessful channel activation
- transcoder failure

3: Radio failures during the channel established phase : Radio Link Failures or LAPDm failures
- 48.058 CONNECTION FAILURE INDICATION message received with a cause value of "radio link failure"
- 48.058 ERROR INDICATION message received

4: MS access problems during the channel establishment phase or a channel change procedure
- 44.018 ASSIGNMENT FAILURE received during SDCCH to TCH assignment or internal intra-cell TCH handover
- T3107 expiry during normal assignment (SDCCH to TCH or TCH to SDCCH) or internal intra-cell TCH handover
- T3103 expiry during internal inter-cell TCH handover or internal directed retry
- 44.018 HANDOVER FAILURE message received during internal inter-cell TCH handover or internal directed
retry
- 48.058 CONNECTION FAILURE INDICATION message received with a cause value of "handover access
failure"
during internal inter-cell TCH handover or internal directed retry or external handover
- T9113 expiry during external TCH handover
- T8 or T3121 expiry during 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 channel change
procedure is considered as successful.
External comment:
--
Alcatel-Lucent
T04a Type 15 : TCH observation
Observation Name : SEIZURE_TYPE (TCH) Length: 1
Measured number
Observation
Describes the purpose for which the TCH channel was seized. Viz :

0: The channel was allocated but was never seized by the mobile
1: SDCCH to TCH assignment
2: the channel was the target of a TCH handover or an internal directed retry.

The table below summerizes information about the seizure and release of the observed TCH channel.
T04a provides information on channel seizure. T04 provides information on channel release.
-----------------------------------------------------------------------------------------------------------------------------
T04a / | 0: | 1: | 2: |

| chan not seized by the MS| chan seized by the MS as part | chan seized by the MS as part |
| as part of any TCH | of TCH normal assignment | of TCH handover or |
T04 | transaction | | internal directed retry |
-----------------------------------------------------------------------------------------------------------------------------
0: normal rel | applicable for NSS release | applicable for MS, NSS, and | applicable for MS, NSS, and |
req by MS, | only | BSS release | BSS release |

NSS, or BSS | | |
|
------------------------------------------------------------------------------------------------------------------------------
1,2: abnormal | applicable | applicable | applicable |
rel due to BSS | | |
|
problem | | |
|
------------------------------------------------------------------------------------------------------------------------------
3: abnormal | not applicable | applicable | applicable |
rel due to radio | | |
|
link failure | | |
|
------------------------------------------------------------------------------------------------------------------------------
4: abnormal | applicable for: | applicable for: | applicable for: |
release due to | - TCH normal assignment | - SDCCH normal assignment | - SDCCH normal assignment |
MS access pb | - internal directed retry | - TCH handover (old | - TCH handover (old |
| - TCH handover (new | channel) | channel) |
| channel) | |
|
-------------------------------------------------------------------------------------------------------------------------------
Notes :
1) T04 = 4 and T04a = 0 means :
- T04a = 0 : observed TCH channel not seized by the mobile
- T04 = 4 : MS access problems on observed TCH channel
Observed TCH channel released before having been seized by the mobile (TCH is the target channel of normal
assignment, internal directed retry or TCH handover)

2) T04 = 4 and T04a = 1 means :
- T04a = 1 : observed TCH channel seized by the mobile as the result of an TCH normal assignment
- T04 = 4 : MS problem on accessing a new channel
Observed TCH channel first seized by the mobile as the result of a TCH normal assignment and then released
during
a channel change procedure (SDCCH normal assignment or TCH handover)

External comment:
Alcatel-Lucent
--

unit:
Observation Name : definition: MS_POWER Length: 2
3) T04 = 4 and T04a = 2 means : Measured dB
- T04a = 2 : observed SDCCH channel seized by the mobile as the result of an internal directed retry or of a TCH
handover Observation
- T04 = 4 : MS problem on accessing a new channel Indicates the last commanded MS Power Level on the
SACCH Channel to the Mobile.
Observed TCH channel first seized by the mobile as the result of an internal directed retry or of a TCH handover
and
then released during a channel change procedure (SDCCH normal assignment or TCH handover) This
counter corresponds to the MS_POWER field of the 48.058 PHYSICAL CONTEXT CONFIRM message.
External comment:
--
Observation Name : BS_POWER Length: 2
Measured dB
Observation
Indicates the last commanded BS Power Level to the encoder.

This counter corresponds to the BS_POWER field of the 48.058 PHYSICAL CONTEXT CONFIRM message.
External comment:
--
Observation Name : TIMING_ADVANCE Length: 2
Measured bper
Observation
Indicates the last commanded Timing Advance on the SACCH Channel to the Mobile.

This counter corresponds to the TIMING_ADVANCE field of the 48.058 PHYSICAL CONTEXT CONFIRM
message.
External comment:
--
Alcatel-Lucent
Observation Name : NB_FRAMES_NOT_REPEATED Length: 2
Measured number
Observation
Indicates the number of SAPI 0 frames that were not repeated.

This counter corresponds to the CNT_I_TX field of the 48.058 PHYSICAL CONTEXT CONFIRM message.
External comment:
--
Observation Name : NB_FRAMES_REPEATED Length: 2
Measured number
Observation
Indicates the number of SAPI 0 frames that were repeated at least once.

This counter corresponds to the CNT_I_RETX field of the 48.058 PHYSICAL CONTEXT CONFIRM message.
External comment:
--
Observation Name : NB_SABM_AFTER_UA_SENT Length: 1
Measured number
Observation
Indicates the number of SABM received on SAPI 0 when UA has already been sent (i.e. SABM received in
established or timer recovery state).

This counter corresponds to the CNT_SABM_RX field of the 48.058 PHYSICAL CONTEXT CONFIRM message.
External comment:
--
Alcatel-Lucent
Observation Name : NB_PHYSICAL_INFO_SENT Length: 1
Measured number
Observation
Indicates the number of times 44.018 PHYSICAL INFORMATION message has been sent in case of
asynchronous
handover.

This counter corresponds to the CNT_PHY_INFO_TX field of the 48.058 PHYSICAL CONTEXT CONFIRM
message.
External comment:
--
Observation Name : NB_ERRONEOUS_FRAMES_SENT Length: 1
Measured number
Observation
Indicates the number of erroneous frames that were received.

This counter corresponds to the CNT_ERR_RX field of the 48.058 PHYSICAL CONTEXT CONFIRM message.
External comment:
--
Observation Name : NB_REJ_FRAMES_SENT Length: 1
Measured number
Observation
Indicates the number of Reject (REJ) frames that were transmitted.

This counter corresponds to the CNT_REJ_TX field of the 48.058 PHYSICAL CONTEXT CONFIRM message.
External comment:
--
Observation Name : NB_REJ_FRAMES_REC Length: 1
Measured number
Observation
Indicates the number of Reject (REJ) frames that were received.

This counter corresponds to the CNT_REJ_RX field of the 48.058 PHYSICAL CONTEXT CONFIRM message.
External comment:
--
Alcatel-Lucent
Observation Name : NB_MS_TX_PWR_MAX_SENT Length: 1
Measured number
Observation
This counter indicates the number of 48.058 CONNECTION FAILURE INDICATION messages that were sent to
the
BSS with a cause value of "set YY_TXPWR_M".

This counter corresponds to the CNT_MS_TXPWR_MAX field of the 48.058 PHYSICAL CONTEXT CONFIRM
message.
External comment:
--
Observation Name : RADIO_LINK_FAILURE_IND Length: 1
Measured number
Observation
Indicates whether or not a Radio Link Failure was detected or not.

0: No connection failure occurred on the RTCH channel
1: A 48.058 CONNECTION FAILURE INDICATION message was received with a cause value of "radio link
failure".

This counter corresponds to the RL_FAILURE_INDICATOR field of the 48.058 PHYSICAL CONTEXT CONFIRM
message.
External comment:
--
Observation Name : PERC_INCOR_SACCH_FRAMES_REC Length: 1
Measured %
Observation
Indicates the percentage of SACCH frames that could not be decoded.

This counter corresponds to the CNT_SA_BFI_RX/CNT_SA_RX field of the 48.058 PHYSICAL CONTEXT
CONFIRM
message.
External comment:
--
Alcatel-Lucent
Observation Name : PERC_INCOR_SDCCH_FRAMES_REC Length: 1
Measured %
Observation
Indicates the percentage of SDCCH frames that could not be decoded.

This counter corresponds to the CNT_SD_BFI_RX/CNT_SD_RX field of the 48.058 PHYSICAL CONTEXT
CONFIRM
message.
External comment:
--
Measured number
Observation
External comment:
--
Alcatel-Lucent
Type name: A interface measurements
Type definition:
Set of counters related to the different causes of 08.08CLEAR REQUEST and 08.08ASSIGNMENT
FAILURE
C180a Type 18 : A interface measurements
Counter Name : NB_N7_CLEAR_REQ_RadioIntMessFail Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
Counter definition:
Number of 48.008CLEAR REQUEST (cause="radio interface message failure") sent to the MSC.
Trigger condition:
Whenever a 48.008 CLEAR REQUEST message with a cause value of "radio interface message failure" is sent
on
A interface to the MSC.
External comment:
--
Alcatel-Lucent
C180b Type 18 : A interface measurements
Counter Name : NB_N7_CLEAR_REQ_O&Minterv Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Counter definition:
Number of 48.008CLEAR REQUEST (cause="O&M intervention") sent to the MSC.
Trigger condition:
Whenever a 48.008 CLEAR REQUEST message with a cause value of "O&M intervention" is sent on A interface
to the MSC.
External comment:
--
C180c Type 18 : A interface measurements
Counter Name : NB_N7_CLEAR_REQ_EquipFail Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Counter definition:
Number of 48.008CLEAR REQUEST (cause="equipment failure") sent to the MSC.
Trigger condition:
Whenever a 48.008 CLEAR REQUEST message with a cause value of "equipment failure" is sent on A interface
to the MSC.
External comment:
--
Alcatel-Lucent
C180d Type 18 : A interface measurements
Counter Name : NB_N7_CLEAR_REQ_RadioIntFail Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Counter definition:
Number of 48.008CLEAR REQUEST (cause="radio interface failure") sent to the MSC.
Trigger condition:
Whenever a 48.008 CLEAR REQUEST message with a cause value of "radio interface failure" is sent on A
interface to the MSC.
External comment:
--
C180e Type 18 : A interface measurements
Counter Name : NB_N7_CLEAR_REQ_NoRadioResAvail Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Counter definition:
Number of 48.008CLEAR REQUEST (cause="no radio resource available") sent to the MSC.
Trigger condition:
Whenever a 48.008 CLEAR REQUEST message with a cause value of "no radio resource available" is sent on A
External comment:
--
Alcatel-Lucent
C181a Type 18 : A interface measurements
Counter Name : NB_N7_ASS_FAIL_RadioIntMessFail Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Counter definition:
Number of 48.008ASSIGNMENT FAILURE (cause="radio interface message failure") sent to the MSC.
Trigger condition:
Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "radio interface message failure" is
sent on A interface to the MSC.
External comment:
--
C181b Type 18 : A interface measurements
Counter Name : NB_N7_ASS_FAIL_O&Minterv Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Counter definition:
Number of 48.008ASSIGNMENT FAILURE (cause="O&M intervention") sent to the MSC.
Trigger condition:
Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "O&M intervention" is sent on A
External comment:
--
Alcatel-Lucent
C181c Type 18 : A interface measurements
Counter Name : NB_N7_ASS_FAIL_EquipFail Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Counter definition:
Number of 48.008ASSIGNMENT FAILURE (cause="equipment failure") sent to the MSC.
Trigger condition:
Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "equipment failure" is sent on A
External comment:
--
C181d Type 18 : A interface measurements
Counter Name : NB_N7_ASS_FAIL_NoRadioResAvail Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Counter definition:
Number of 48.008ASSIGNMENT FAILURE (cause="no radio resource available") sent to the MSC.
Trigger condition:
Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "no radio resource available" is sent
on A interface to the MSC.
External comment:
--
Alcatel-Lucent
C181e Type 18 : A interface measurements
Counter Name : NB_N7_ASS_FAIL_ReqTerResUnav/Alloc Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Counter definition:
Number of 48.008ASSIGNMENT FAILURE (cause="requested terrestrial resource unavailable", or "terrestrial
resource already allocated") sent to the MSC.
Trigger condition:
1) Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "requested terrestrial resource
unavailable" is sent on A interface to the MSC.
2) Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "terrestrial resource already
allocated" is sent on A interface to the MSC.
External comment:
--
C181f Type 18 : A interface measurements
Counter Name : NB_N7_ASS_FAIL_ReqTrans/RateUnav Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Counter definition:
Number of 48.008ASSIGNMENT FAILURE (cause="requested transcoding/rate adaptation unavailable") sent to
the MSC.
Trigger condition:
Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "requested transcoding/rate
adaptation unavailable" is sent on A interface to the MSC.
External comment:
--
Alcatel-Lucent
C181g Type 18 : A interface measurements
Counter Name : NB_N7_ASS_FAIL_RadioIntFailRevOldChan Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Counter definition:
Number of 48.008ASSIGNMENT FAILURE (cause="radio interface failure -reversion to old channel") sent to the
MSC.
Trigger condition:
Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "radio interface failure - reversion to
old channel" is sent on A interface to the MSC.
External comment:
--
C181h Type 18 : A interface measurements
Counter Name : NB_N7_ASS_FAIL_RadioIntFail Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Counter definition:
Number of 48.008ASSIGNMENT FAILURE (cause="radio interface failure") sent to the MSC.
Trigger condition:
Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "radio interface failure" is sent on A
External comment:
--
Alcatel-Lucent
C181i Type 18 : A interface measurements
Counter Name : NB_N7_ASS_FAIL_CipherAlgoNotSupp Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Counter definition:
Number of 48.008ASSIGNMENT FAILURE (cause="ciphering algorithm not supported") sent to the MSC.
Trigger condition:
Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "cipher algorithm not supported" is
sent on A interface to the MSC.
External comment:
--
C181j Type 18 : A interface measurements
Counter Name : NB_N7_ASS_FAIL_BSSnotEquip Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Counter definition:
Number of 48.008ASSIGNMENT FAILURE (cause="BSS not equiped") sent to the MSC.
Trigger condition:
Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "BSS not equiped" is sent on A
External comment:
--
Alcatel-Lucent
C181k Type 18 : A interface measurements
Counter Name : NB_N7_ASS_FAIL_ProtocolError Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Counter definition:
Number of 48.008ASSIGNMENT FAILURE (cause="protocol error between BSC and MSC") sent to the MSC.
Trigger condition:
Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "protocol error between BSC and
MSC" is sent on A interface to the MSC.
External comment:
--
C181l Type 18 : A interface measurements
Counter Name : NB_N7_ASS_FAIL_ReqSpeechVersUnav Counter Integer
SFD reference : 3BK 10204 0238 DSZZA ("Support of Enhanced Full Rate Length: 4
Mobiles")
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Counter definition:
Number of 48.008ASSIGNMENT FAILURE (cause="requested speech version unavailable") sent to the MSC.
Trigger condition:
Whenever a 48.008 ASSIGNMENT FAILURE message with a cause value of "requested speech version
unavailable" is sent on A interface to the MSC.
External comment:
--
Alcatel-Lucent
C182 Type 18 : A interface measurements
Counter Name : NB_N7_CLEAR_REQ_EST_PHAS Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A
Counter definition:
Number of 48.008 CLEAR REQUEST sent to the MSC for calls in TCH established phase, and for internal
inter-cell and external TCH handover failures.
Intra-cell handover failures are not taken into account.
This counter takes into account TCH in traffic mode or in signaling mode.
Trigger condition:
1) Whenever a 48.008 CLEAR REQUEST message, whatever the cause, is sent on A interface to the MSC, for a
call in TCH established phase. Note that this trigger takes into account TCH in traffic mode or in signaling mode.
2) Whenever a 48.008 CLEAR REQUEST message is sent on A interface to the MSC, after a Handover
command
is sent, during a TCH internal inter-cell HO.
3) Whenever a 48.008 CLEAR REQUEST message is sent on A interface to the MSC, after a Handover
command
is sent, during a TCH external HO.
4) Whenever a 48.008 CLEAR REQUEST message is sent on A interface to the MSC, after a DTM Assignment
Command is sent, during a DTM assignment, for a MS which already had a TCH allocated (i.e. the TCH in DTM
Assignment Command is established in traffic mode).
External comment:
--
Alcatel-Lucent
Counter Name : TIME_A_CHANNEL_BUSY Counter Integer
B10 A interface channel 1
Sub domain-2: A
Counter definition:
Time (in seconds) during which the A channel is busy.
Trigger condition:
The counter cumulates over the Accumulation Period, all unit times during which the A channel is busy.
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).
External comment:
--
Counter Name : NB_A_CHANNEL_ALLOC Counter Integer
Sub domain-2: A
Counter definition:
Number of allocations of the A-channel.
Trigger condition:
1) Whenever a A channel is allocated following the reception of 48.008 ASSIGNMENT REQUEST.
2) Whenever a A channel is allocated following the reception of 48.008 HANDOVER REQUEST
3) Whenever a A channel is allocated during an internal handover procedure
External comment:
--
Alcatel-Lucent
Type name: SMS PP measurements
- In Detailed usage : The union of all observed cells per BSS for the detailed measurement types 1, 2,
3, 4, 5, 6, 19, 26, 28 (if used as Detailed), 29 (if used as Detailed), 31 (if used as detailed), 34 (if used
as Detailed) must not exceed 40 cells.
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.
C190 Type 19 : SMS PP measurements
Counter Name : NB_SMS_PP_CON_MO_SDCCH Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Short Message Service
Sub domain-2: Point to Point
Counter definition:
Number of Mobile Originating SMS connections on SDCCH.
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION (SAPI = 3) message related to an SDCCH sub-channel is
received
by the BSC.
External comment:
--
Alcatel-Lucent
Counter Name : NB_SMS_PP_CON_MT_SDCCH Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of Mobile Terminating SMS connections on SDCCH.
Trigger condition:
Whenever an ESTABLISH CONFIRM (SAPI = 3) message related to an SDCCH sub-channel is received by the
BSC.
External comment:
--
Counter Name : NB_SMS_PP_CON_MO_SACCH Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of Mobile Originating SMS connections on SACCH.
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION (SAPI = 3) message related to an SACCH sub-channel is
received
by the BSC.
External comment:
--
Alcatel-Lucent
Counter Name : NB_SMS_PP_CON_MT_SACCH Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of Mobile Terminating SMS connections on SACCH.
Trigger condition:
Whenever an ESTABLISH CONFIRM (SAPI = 3) message related to an SACCH sub-channel is received by the
BSC.
External comment:
--
C194a Type 19 : SMS PP measurements
Counter Name : NB_SMS_PP_CON_REJ_RadioIntFail Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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".
External comment:
--
Alcatel-Lucent
C194b Type 19 : SMS PP measurements
Counter Name : NB_SMS_PP_CON_REJ_BSSnotEquip Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.
External comment:
--
C194c Type 19 : SMS PP measurements
Counter Name : NB_SMS_PP_CON_REJ_ProtocolError Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_SMS_PP_CON_REL_LAPDM_ERROR Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of SMS connection releases of established SMS SAPI 3 connections by the BSC due to a LAPDm error.
Trigger condition:
Whenever an 48.058 ERROR INDICATION message related to SAPI 3 is received by the BSC with one of the
following cause values :
a) timer T200 expired (N200+1) times
b) unsolicited DM response, multiple frame established state
c) sequence error.
External comment:
--
Alcatel-Lucent
Type name: SCCP measurements
- In Detailed usage: none
Type definition:
Set of counters related to the SCCP layer of the N7 Signalling Links
C153a Type 25 : SCCP measurements
Counter Name : NB_N7_CON_EST_FAIL_DUE_NSS Counter Integer
Sub domain-2: A
Domain: Quality of Service Sub domain-3: SCCP
Counter definition:
Number of BSS originating SCCP connection failures due to the NSS.
Trigger condition:
1) CREF received.
2) RLSD received for a connection that was not established (this could indicate that the Connection Confirm from
the MSC was not received).
External comment:
--
Alcatel-Lucent
C153b Type 25 : SCCP measurements
Counter Name : NB_N7_CON_EST_FAIL_DUE_BSS Counter Integer
Sub domain-2: A
Counter 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.
External comment:
--
C251 Type 25 : SCCP measurements
Counter Name : NB_N7_UNIT_DATA_SENT Counter Integer
Sub domain-2: A
Domain: Traffic Load Sub domain-3: SCCP
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_N7_UNIT_DATA_REC Counter Integer
Sub domain-2: A
Counter 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.
External comment:
--
Counter Name : NB_N7_CON_REQ_SENT Counter Integer
Sub domain-2: A
Counter definition:
Number of CONNECTION REQUEST sent to the MSC.
Trigger condition:
Whenever a CONNECTION REQUEST message is sent on A interface from the BSC to the MSC.
External comment:
--
Alcatel-Lucent
Counter Name : NB_N7_CON_REQ_REC Counter Integer
Sub domain-2: A
Counter definition:
Number of CONNECTION REQUEST received from the MSC.
Trigger condition:
Whenever a CONNECTION REQUEST message is received on A interface from the MSC.
External comment:
--
Counter Name : NB_N7_CON_CONF_SENT Counter Integer
Sub domain-2: A
Counter definition:
Number of CONNECTION CONFIRM sent to the MSC.
Trigger condition:
Whenever a CONNECTION CONFIRM message is sent on A interface from the BSC to the MSC.
External comment:
--
Alcatel-Lucent
Counter Name : NB_N7_CON_CONF_REC Counter Integer
Sub domain-2: A
Counter definition:
Number of CONNECTION CONFIRM received from the MSC.
Trigger condition:
Whenever a CONNECTION CONFIRM message is received on A interface from the MSC.
External comment:
--
Counter Name : NB_N7_CON_REF_SENT Counter Integer
Sub domain-2: A
Counter definition:
Number of CONNECTION REFUSED sent to the MSC.
Trigger condition:
Whenever a CONNECTION REFUSED message is sent on A interface from the BSC to the MSC.
External comment:
--
Alcatel-Lucent
Counter Name : NB_N7_CON_REF_REC Counter Integer
Sub domain-2: A
Counter definition:
Number of CONNECTION REFUSED received from the MSC.
Trigger condition:
Whenever a CONNECTION REFUSED message is received on A interface from the MSC.
External comment:
--
Alcatel-Lucent
Type name: TCH outgoing handover per adjacency measurements
Type scope (per BSS): One or several serving cells
1) Up to 40 serving cells can be selected per BSC.
2) These counters are provided for external handover.
3) The PM counters of Type 26 only report a PM measurement on an adjacency link on which at least
an handover took place.
Type definition:
Set of counters related to outgoing TCH handover provided per adjacency.
C720 Type 26 : TCH outgoing handover per adjacency measurements
Counter Name : NB_ADJ_SCELL_OUT_TCH_HO_ATPT Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Technology: GSM Sub domain-1: Fixed serving Cell
Sub domain-2:
Domain: Adjacency Sub domain-3:
Counter 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.

External comment:
--
Alcatel-Lucent
Counter Name : NB_ADJ_SCELL_OUT_TCH_HO_SUCC Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Sub domain-2:
Counter definition:
Number of outgoing external and internal inter-cell TCH (in HR or FR usage) handover successes. This counter
takes into account handovers from TCH in traffic or in signaling mode.
Trigger condition:
1) Internal handover: whenever 44.018 HANDOVER_COMPLETE message is received on Abis interface from the
variable target cell during an internal inter-cell TCH handover attempted from the fixed serving cell.

2) External handover from the fixed serving cell to the 2G target cell in the following cases:
2a) 48.008 CLEAR COMMAND (cause = "handover successful") is received at the serving BSC from the MSC.

External comment:
--
Alcatel-Lucent
Counter Name : NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_REV Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Sub domain-2:
Counter 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
Trigger condition:
Whenever a 44.018 HANDOVER FAILURE message is received on Abis interface from the fixed serving cell
during an external or internal inter-cell TCH handover attempted towards the variable 2G target cell.

External comment:
--
Alcatel-Lucent
Counter Name : NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_NO_REV Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Sub domain-2:
Counter 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
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.

External comment:
--
Alcatel-Lucent
Counter Name : NB_ADJ_SCELL_OUT_TCH_HO_EMERGENCY_ATPT Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Sub domain-2:
Counter 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.

External comment:
--
Counter Name : NB_ADJ_SCELL_OUT_TCH_HO_BETTERCELL_ATPT Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Sub domain-2:
Counter definition:
Number of outgoing external and internal inter-cell TCH (in HR or FR usage) handover attempts with better cell
cause. This counter takes into account handovers from TCH in traffic or in signaling mode.
Trigger condition:
for an outgoing handover cause 12, 14, 21 on a TCH channel, from the fixed serving cell to the variable target
cell.

External comment:
--
Alcatel-Lucent
Counter Name : NB_ADJ_SCELL_OUT_TCH_HO_TRAFFIC_ATPT Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Sub domain-2:
Counter definition:
Number of outgoing external and internal inter-cell TCH (in HR or FR usage) handover attempts with traffic cause.
Trigger condition:
for an outgoing handover cause 23,24, 28 on a TCH channel, from the fixed serving cell to the variable target cell.

External comment:
--
Counter Name : NB_ADJ_SCELL_OUT_ FORCED_DR_ATPT Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Sub domain-2:
Counter 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.
External comment:
--
Alcatel-Lucent
Type name: 2G TCH incoming handover per adjacency measurements
Type scope (per BSS): One target cell
1) Only one target cell can be selected per BSS
2) In B5 : the counters are not provided for external handover (this is done in B62)
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).
C730 Type 27 : 2G TCH incoming handover per adjacency
Counter Name : NB_ADJ_TCELL_INC_TCH_HO_ATPT Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Technology: GSM Sub domain-1: Fixed target Cell
Sub domain-2:
Counter definition:
Number of incoming 2G to 2G external and internal inter-cell TCH (in HR or FR usage) handover attempts.
Trigger condition:
1) Internal handover : whenever 44.018HANDOVER COMMAND is sent to the MS via the variable serving cell for
an internal inter-cell TCH handover towards the fixed target cell.
2) External handover : whenever 48.008HANDOVER REQUEST ACK is sent to the MSC from the target BSC for
an external TCH handover from the variable 2G serving cell towards the fixed target cell. The Cell-identity of the
serving and target cells is provided in the 48.008HANDOVER REQUEST. Only handovers from a 2G cell shall be
taken into account (if the field Cell Identifier discriminator in the I.E. Cell Identifier (serving) of the 48.008
HANDOVER REQUEST is set to 0000 or 0001).

External comment:
--
Alcatel-Lucent
Counter Name : NB_ADJ_TCELL_INC_TCH_HO_SUCC Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Sub domain-2:
Counter definition:
Number of incoming 2G to 2G external and internal inter-cell TCH (in HR or FR usage) handover successes.
Trigger condition:
1) Whenever a 44.018 HANDOVER COMPLETE message is received on Abis interface from the fixed target cell
during an external or internal inter-cell TCH handover attempted from the variable serving cell. Only handovers
from
a 2G cell shall be taken into account (if the field Cell Identifier discriminator in the I.E. Cell Identifier (serving) of
the 48.008 HANDOVER REQUEST is set to 0000 or 0001).

External comment:
--
Alcatel-Lucent
Counter Name : NB_ADJ_TCELL_INC_TCH_HO_EXEC_FAIL_MS_ACC Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Sub domain-2:
Counter definition:
Number of incoming 2G to 2G external and internal inter-cell TCH (in HR or FR usage) handover -execution
failures due to MS access problem, with or without reversion of the mobile to the old channel.
Trigger condition:
1) Internal handover :
- 44.018HANDOVER FAILURE (cause= "radio interface failure, reversion to old channel") received from the
variable serving cell during an internal inter-cell TCH handover towards the fixed target cell.
- T3103 expiry
2) External handover :
- 48.058CONNECTION FAILURE INDICATION (cause= "handover access failure") received on the new channel
from the fixed target cell
- 48.008CLEAR COMMAND (cause= "radio interface failure, reversion to old channel") received on the target
BSC.

Only handovers from a 2G cell shall be taken into account (if the field Cell Identifier discriminator in the I.E. Cell
Identifier (serving) of the 48.008 HANDOVER REQUEST is set to 0000 or 0001).

External comment:
--
Alcatel-Lucent
Counter Name : NB_ADJ_TCELL_INC_TCH_HO_EMERGENCY_ATPT Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Sub domain-2:
Counter definition:
Number of incoming 2G to 2G external and internal inter-cell TCH (in HR or FR usage) handover attempts, with
emergency cause.
Trigger condition:
1) Internal inter-cell handover : whenever 44.018HANDOVER COMMAND is sent to the MS via the variable
serving
cell for an internal inter-cell TCH handover towards the fixed target cell, with cause 2, 3, 4, 5, 6, 7, 17, 18, 22
an external TCH handover from the variable serving cell towards the fixed target cell. The Cell-identity of the
serving and target cells is provided in the 48.008HANDOVER REQUEST with 48.008 cause 2, 3, 4, 5, 6

External comment:
--
Alcatel-Lucent
Counter Name : NB_ADJ_TCELL_INC_TCH_HO_BETTERCELL_ATPT Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Sub domain-2:
Counter definition:
better cell cause.
Trigger condition:
1) Internal intercell handover : whenever 44.018HANDOVER COMMAND is sent to the MS via the variable
serving
cell for an internal inter-cell TCH handover towards the fixed target cell, with cause 12, 14, 21
serving and target cells is provided in the 48.008HANDOVER REQUEST with 48.008 cause 12

External comment:
--
Alcatel-Lucent
Counter Name : NB_ADJ_TCELL_INC_TCH_HO_TRAFFIC_ATPT Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Sub domain-2:
Counter definition:
traffic cause.
Trigger condition:
an internal inter-cell TCH handover towards the fixed target cell, with cause 23, 24, 28
serving and target cells is provided in the 48.008HANDOVER REQUEST with 48.008 cause 15.

External comment:
--
Alcatel-Lucent
Counter Name : NB_ADJ_TCELL_INC_FORCED_DR_ATPT Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Sub domain-2:
Counter definition:
Number of incoming 2G to 2G external and internal inter-cell directed retries attempts, with Forced directed retry
cause.
Trigger condition:
an internal inter-cell TCH handover towards the fixed target cell, with cause 20
serving and target cells is provided in the 48.008HANDOVER REQUEST with 48.008 cause 13.

External comment:
--
Alcatel-Lucent
Counter Name : NB_ADJ_TCELL_INC_TCH_HO_OTHER_ATPT Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Sub domain-2:
Counter definition:
unknown or missing cause.
Trigger condition:
an internal inter-cell TCH handover towards the fixed target cell, with unknown or missing cause.
serving and target cells is provided in the 48.008HANDOVER REQUEST with unknown or missing 48.008 cause,
or 48.008 cause different from 2, 3, 4, 5, 6, 12, 13, 15.

External comment:
--
Alcatel-Lucent
Type name: SDCCH handover
- In Detailed usage :The union of all observed cells per BSS for the detailed measurement types 1, 2,
3, 4, 5, 6, 19 (if used as Detailed), 26, 28, 29 (if used as Detailed), 31 (if used as detailed), 34 (if used
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.
C100 Type 28 : SDCCH handover
Counter Name : NB_OUT_INT_SDCCH_HO_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Counter definition:
Number of outgoing internal inter-cell SDCCH handover attempts.
Trigger condition:
Whenever the 44.018 HANDOVER COMMAND message is sent on Abis interface to the mobile via the serving
cell, during an internal inter-cell SDCCH handover procedure.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INTRA_SDCCH_HO_PREP_FAIL_CONG Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter definition:
MC101=C101, Number of intra-cell SDCCH handover -preparation failures due to congestion.
Trigger condition:
Whenever a internal intra-cell SDCCH handover cannot be performed, because there is no free SDCCH
Sub-channel to allocate the handover to.
External comment:
--
Counter Name : NB_INTRA_SDCCH_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter definition:
Number of intra-cell SDCCH handover successes.
Trigger condition:
Whenever a ASSIGNEMENT COMPLETE message is received on the target channel during an internal intra-cell
SDCCH handover.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INTRA_SDCCH_HO_EXEC_FAIL_NO_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter definition:
Number of intra-cell SDCCH handover -execution failures due to MS access problem without reversion to the old
channel.
Trigger condition:
Whenever the timer supervising the internal intra-cell SDCCH handover procedure (T3107) expires.
External comment:
--
Counter Name : NB_INTRA_SDCCH_HO_EXEC_FAIL_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter definition:
Number of intra-cell SDCCH handover -execution failures due to MS access problem with reversion to the old
channel.
Trigger condition:
Whenever a 44.018 ASSIGNMENT FAILURE message is received on the Serving Sub-channel, during an internal
intra-cell SDCCH handover.
External comment:
--
Alcatel-Lucent
Counter Name : NB_SDCCH_HO_MSC_TRIG Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
Number of external handovers triggered by the MSC but not required by the BSS.
Trigger condition:
Whenever a 48.008 HANDOVER COMMAND message is received on A interface from the MSC and timer
T_HO_REQ_LOST is not running.

External comment:
--
Counter Name : NB_INC_EXT_SDCCH_HO_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming external SDCCH handover requests.
Trigger condition:
48.008HANDOVER REQUEST is received by the target BSC for the target cell on the SDCCH channel.

External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_SDCCH_HO_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming external SDCCH handover attempts.
Trigger condition:
48.008HANDOVER REQUEST ACK is sent by the target BSC containing the 44.018HANDOVER COMMAND
towards the target cell on the SDCCH channel.

External comment:
--
Counter Name : NB_INC_INT_SDCCH_HO_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming internal inter-cell SDCCH handover requests.
Trigger condition:
cells) for internal inter cell SDCCH handover.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_INT_SDCCH_HO_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming internal inter-cell SDCCH handover attempts.
Trigger condition:
44.018HANDOVER COMMAND is sent to the MS via the serving cell for internal inter cell SDCCH handover.
However, the counter is incremented in the TARGET cell, based on the target cell ID indicated by the HO
Command message,
External comment:
--
Counter Name : NB_INTRA_SDCCH_HO_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter definition:
Number of intra-cell SDCCH handover requests.
Trigger condition:
Whenever the BSC process responsible for the handover procedure starts an intra cell SDCCH handover
procedure.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INTRA_SDCCH_HO_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter definition:
Number of intra-cell SDCCH handover attempts.
Trigger condition:
44.018ASSIGNMENT COMMAND is sent to the MS via the cell for intra cell handover on SDCCH.
External comment:
--
Counter Name : NB_SDCCH_HO_ATPT_23_TrafHandover Counter Integer
Algorithms")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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

External comment:
--
Alcatel-Lucent
Counter Name : NB_SDCCH_HO_ATPT_24_GenCaptureHandover Counter Integer
Algorithms")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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

External comment:
--
Counter Name : NB_SDCCH_HO_ATPT_22_TooShortDistance Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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.

External comment:
--
Alcatel-Lucent
Counter Name : NB_SDCCH_HO_ATPT_2_TooLowQualUp Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
Number of SDCCH inter-cell internal or external handover attempts triggered with cause 2: "uplink quality too
low".
Trigger condition:
External comment:
--
Counter Name : NB_SDCCH_HO_ATPT_3_TooLowLevUp Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
Number of SDCCH inter-cell internal or external handover attempts with cause 3: "uplink level too low".
Trigger condition:

External comment:
--
Alcatel-Lucent
Counter Name : NB_SDCCH_HO_ATPT_4_TooLowQualDown Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
Number of SDCCH inter-cell internal or external handover attempts with cause 4: "downlink quality too low".
Trigger condition:

External comment:
--
Counter Name : NB_SDCCH_HO_ATPT_5_TooLowLevDown Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
Number of SDCCH inter-cell internal or external handover attempts triggered with cause 5: "downlink level too
low".
Trigger condition:

External comment:
--
Alcatel-Lucent
Counter Name : NB_SDCCH_HO_ATPT_6_TooLongDistance Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
Number of SDCCH inter-cell internal or external handover attempts with cause 6: "MS-BTS distance too long".
Trigger condition:

External comment:
--
Counter Name : NB_SDCCH_HO_ATPT_15_TooHighLevInterfUp Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
Number of SDCCH intra-cell handover attempts with cause 15: "too high level interference on uplink".
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_SDCCH_HO_ATPT_16_TooHighLevInterfDown Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
Number of SDCCH intra-cell handover attempts with cause 16: "too high level interference on downlink".
Trigger condition:
External comment:
--
Counter Name : NB_SDCCH_HO_ATPT_12_TooLowPowBudg Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
Number of SDCCH inter-cell internal or external handover attempts with cause 12: "too low power budget".
Trigger condition:

External comment:
--
Alcatel-Lucent
Counter Name : NB_SDCCH_HO_ATPT_21_HighLevNeigCellPrefBand Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:

External comment:
--
C605a Type 28 : SDCCH handover
Counter Name : NB_SDCCH_HO_ATPT_7_ConsBadSACCHmicroCell Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:

External comment:
--
Alcatel-Lucent
C605d Type 28 : SDCCH handover
Counter Name : NB_SDCCH_HO_ATPT_17_TooLowLevUpMicroCell Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:

External comment:
--
C605e Type 28 : SDCCH handover
Counter Name : NB_SDCCH_HO_ATPT_18_TooLowLevDownMicroCell Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:

External comment:
--
Alcatel-Lucent
C605f Type 28 : SDCCH handover
Counter Name : NB_SDCCH_HO_ATPT_14_HighLevNeigLowCellSlowMS Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:

External comment:
--
Counter Name : NB_SDCCH_HO_ATPT_20_HighLevNeigCellForcDR Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:

External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC81=C81, Number of incoming external SDCCH handover -preparation failures due to congestion.
Trigger condition:
on
A interface from the target BSC to the MSC during an external SDCCH handover.

External comment:
--
Counter Name : NB_INC_EXT_SDCCH_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming external SDCCH handover successes.
Trigger condition:
Whenever a 44.018 HANDOVER COMPLETE message is received on Abis interface from the target cell for an
SDCCH Sub-channel that is involved in an external SDCCH handover.

External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_SDCCH_HO_EXEC_FAIL_MS_ACCESS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming external SDCCH handover -execution failures due to MS access problem.
Trigger condition:
1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "handover access
failure" is received on Abis interface from the target cell, for an SDCCH Sub-channel during an external SDCCH
handover.
2) Whenever the timer supervising the handover procedure on the target cell (T9113), expires during an external
SDCCH handover.
3) Whenever a 48.008 CLEAR COMMAND with a cause value of "radio interface failure - reversion to old
channel"
is received on A interface on the target BSC from the MSC during an external SDCCH handover.

External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_EXT_SDCCH_REAL_HO_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing external SDCCH handover requests.
Trigger condition:
Whenever a 48.008 HANDOVER REQUIRED message is sent on A interface to the MSC for a SDCCH handover.
If more than one 48.008 HANDOVER REQUIRED is sent in the frame of the same Handover procedure, the
counter is incremented only once.

48.008 HANDOVER REQUIRED is sent in following situations :

External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_EXT_SDCCH_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing external SDCCH handover successes.
Trigger condition:
1/ a 48.008 CLEAR COMMAND message with a cause of "handover successful" is received on A interface on the
serving BSC from the MSC.

External comment:
--
Counter Name : NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outoing external SDCCH handover -execution failures due to MS access problem with reversion to the
old channel.
Trigger condition:
Whenever a HANDOVER FAILURE message is received on Abis interface from the serving cell, during an
external
SDCCH handover.

External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_NO_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number outoing external SDCCH handover -execution failures due to MS access problem without reversion to the
old channel.
Trigger condition:
Whenever the timer supervising the handover procedure on the serving cell (T8), expires during an external
SDCCH handover, except if a 48.008 CLEAR COMMAND with "normal event/call control" cause was received
from
the MSC, leading to a normal call release. In such a case, the handover is considered as successful.

External comment:
--
Counter Name : NB_OUT_EXT_SDCCH_HO_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing external SDCCH handover attempts.
Trigger condition:
an external SDCCH handover procedure.

External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC91=C91, Number of incoming internal inter-cell SDCCH handover -preparation failures due to congestion.
Trigger condition:
Whenever a internal inter-cell SDCCH handover cannot be performed, because there is no free SDCCH
External comment:
--
Counter Name : NB_INC_INT_SDCCH_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming internal inter-cell SDCCH handover successes.
Trigger condition:
Whenever a 44.018 HANDOVER COMPLETE message is received on Abis interface from the target cell during
an
internal inter-cell SDCCH handover.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_INT_SDCCH_HO_EXEC_FAIL_MS_ACCESS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming internal inter-cell SDCCH handover -execution failures due to MS access problem.
Trigger condition:
1) Whenever the timer supervising the handover procedure (T3103) expires during an internal inter-cell SDCCH
handover.
2) Whenever a HANDOVER FAILURE message is received on Abis interface from the serving cell during and
internal inter-cell SDCCH handover.
External comment:
--
Counter Name : NB_OUT_INT_SDCCH_HO_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing internal inter-cell SDCCH handover requests.
Trigger condition:
cells) for internal inter cell SDCCH handover.
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_INT_SDCCH_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing internal inter-cell SDCCH handover successes.
Trigger condition:
Whenever a 44.018 HANDOVER COMPLETE message is received on Abis interface from the target cell, during
an internal inter-cell SDCCH handover.
External comment:
--
Counter Name : NB_OUT_INT_SDCCH_HO_EXEC_FAIL_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_INT_SDCCH_HO_EXEC_FAIL_NO_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.
External comment:
--
Alcatel-Lucent
Type name: Directed retry measurements
- In Detailed usage :The union of all observed cells per BSS for the detailed measurement types 1, 2,
3, 4, 5, 6, 19 (if used as Detailed), 26, 28, 29 (if used as Detailed), 31 (if used as detailed), 34 (if used
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.
C142a Type 29 : Directed retry measurements
Counter Name : NB_OUT_FORCED_IDR_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Domain: Handover Sub domain-3: Outgoing
Counter 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.
External comment:
--
Alcatel-Lucent
C142b Type 29 : Directed retry measurements
Counter Name : NB_OUT_FORCED_EDR_SUCC Counter Integer
SFD reference : 3BK 10204 0165 DSZZA ("External Directed Retry") Length: 4
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: External
Counter definition:
Number of outgoing forced external directed retry (towards a TCH channel in HR or FR usage) successes.
Trigger condition:
Forced external directed retry in the following cases:
1/ 48.008CLEAR COMMAND (cause = "handover successful") is received on the serving BSC
2/ 48.008 CLEAR COMMAND (cause = "normal event/call control") received while T8 is running.

External comment:
--
C142c Type 29 : Directed retry measurements
Counter Name : NB_OUT_NOR_IDR_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.
External comment:
--
Alcatel-Lucent
C142d Type 29 : Directed retry measurements
Counter Name : NB_OUT_NOR_EDR_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing normal external directed retry (towards a TCH channel in HR or FR usage) successes.
Trigger condition:
Normal external directed retry in the following cases:
1/ 48.008 CLEAR COMMAND (cause = "handover successful") is received on the serving BSC

External comment:
--
Counter Name : NB_OUT_FORCED_IDR_EXEC_FAIL_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_FORCED_IDR_EXEC_FAIL_NO_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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).
External comment:
--
Counter Name : NB_OUT_FORCED_EDR_EXEC_FAIL_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing forced external directed retry -execution failures due to MS access problem with reversion to
Trigger condition:
Whenever 44.018 HANDOVER FAILURE is received from the MS via the serving cell on the old channel
(SDCCH).

External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_FORCED_EDR_EXEC_FAIL_NO_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing forced external directed retry -execution failures due to MS access problem without reversion
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.

External comment:
--
C143e Type 29 : Directed retry measurements
Counter Name : NB_OUT_NOR_IDR_EXEC_FAIL_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing normal internal directed retry -execution failures due to MS access problem with reversion to
Trigger condition:
44.018HANDOVER FAILURE on SDCCH received from the MS via the serving cell.
External comment:
--
Alcatel-Lucent
C143f Type 29 : Directed retry measurements
Counter Name : NB_OUT_NOR_IDR_EXEC_FAIL_NO_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing normal internal directed retry -execution failures due to MS access problem without reversion
Trigger condition:
Timer T3103 expiry (this timer supervizes the 44.018HANDOVER COMMAND).
External comment:
--
C143g Type 29 : Directed retry measurements
Counter Name : NB_OUT_NOR_EDR_EXEC_FAIL_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing normal external directed retry -execution failures due to MS access problem with reversion to
Trigger condition:
Whenever 44.018 HANDOVER FAILURE is received from the MS via the serving cell on the old channel
(SDCCH).

External comment:
--
Alcatel-Lucent
C143h Type 29 : Directed retry measurements
Counter Name : NB_OUT_NOR_EDR_EXEC_FAIL_NO_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing normal external directed retry -execution failures due to MS access problem without reversion
Trigger condition:
Whenever the timer supervising the handover procedure (T8) expires during a normal external directed retry,
to a normal call release. In such a case, the directed retry is considered as successful.

External comment:
--
Counter Name : NB_OUT_FORCED_IDR_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_FORCED_EDR_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.

External comment:
--
Counter Name : NB_OUT_NOR_IDR_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_NOR_EDR_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.

External comment:
--
Counter Name : NB_OUT_FORCED_IDR_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_FORCED_EDR_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing forced external directed retry attempts. The target TCH channel can be in HR or FR usage.
Trigger condition:
forced external directed retry.

External comment:
--
Counter Name : NB_OUT_NOR_IDR_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing normal internal directed retry attempts. The target TCH channel can be in HR or FR usage.
Trigger condition:
normal internal directed retry.
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_NOR_EDR_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of outgoing normal external directed retry attempts. The target TCH channel can be in HR or FR usage.
Trigger condition:
normal external directed retry.

External comment:
--
C151 Type 29 : Directed retry measurements
Counter Name : NB_INC_IDR_SUCC (29) Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Domain: Handover Sub domain-3: Incoming
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_IDR_EXEC_FAIL_MS_ACCESS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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)
External comment:
--
Counter Name : NB_INC_IDR_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC153=C153, Number of incoming internal directed retry (forced or normal) requests. The target TCH channel
can
be in HR or FR usage.
Trigger condition:
Whenever the BSC process responsible for handover procedure selects the target cell for forced or normal
internal
directed retry.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_IDR_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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,
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_IDR_PREP_FAIL_CONG_R_ABIS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming internal directed retry (forced or normal) -preparation failures due to congestion (on Air or
A-bis interface). The target TCH channel can be in HR or FR usage.
Trigger condition:
1) Whenever there are no free TCH in the target cell during a forced or normal internal directed retry.
2) Whenever no TCH resource is available on A-bis interface for a forced or normal internal directed retry. (not
valid
in B7).

Note 1: In MX BSC, this counter is incremented whenever a TCH cannot be not allocated due to the TCH
processing capacity of CCP reaches the limit defined by the MAX_TCH_PER_CCP parameter. In this case,
MC926 is also incremented by one.

parameter
External comment:
--
Alcatel-Lucent
Type name: SMS CB measurements
Type definition:
Set of counters related to the Short Message Service Cell Broadcast.
CB601 Type 30 : SMS CB measurements
Counter Name : NB_SMSCB_WRITE_REPL_SUCC Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: Short Message Service
Domain: Traffic Load Sub domain-3: Cell Broadcast
Counter definition:
Number of cells successfully served for a WRITE REPLACE.
A WRITE REPLACE request coming from the CBC is received by the BSC. This request is addressed to a list of
cells. The BSC is able to process the request either :
- entirely (i.e. for all cells of the list) : the BSC sends a REPORT SUCCESS to the CBC
- partially (i.e. for a part of the list) : the BSC returns a REPORT SUCCESS to the CBC
- not at all (i.e. for no cell) : the BSC returns a REPORT FAILURE to the CBC if the cause of the reject is the
same for all cells, otherwise a REPORT SUCCESS is returned.
When a REPORT SUCCESS is returned, the No-of-Broadcasts-completed-list optional Information Element
specifies the number of cells successfully served by the request. This IE is not provided when no cells can be
served.
Trigger condition:
Whenever a REPORT SUCCESS to a WRITE REPLACE is sent to the CBC, the counter is incremented by the
No-of-Broadcasts-completed-list optional IE (if not provided; the counter is not incremented, since it means that
no cells are served).
External comment:
--
Alcatel-Lucent
Counter Name : NB_SMSCB_KILL_MESS_SUCC Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: Short Message Service
Domain: Traffic Load Sub domain-3: Cell Broadcast
Counter definition:
Number of cells successfully served for a KILL MESSAGE.
A KILL MESSAGE request coming from the CBC is received by the BSC. This request is addressed to a list of
cells. The BSC is able to process the request either :
When a REPORT SUCCESS is returned, the No-of-Broadcasts-completed-list optional Information Element
specifies the number of cells successfully served by the request. This IE is not provided when no cells can be
served.
Trigger condition:
Whenever a REPORT SUCCESS to a KILL MESSAGE is sent to the CBC, the counter is incremented by the
No-of-Broadcasts-completed-list optional IE (if not provided, the counter is not incremented, since it means that
no cells are served).
External comment:
--
Alcatel-Lucent
Counter Name : NB_SMS_CB_FAIL_IND Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: Cell Broadcast
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_SMS_CB_WRITE_REP_KILL_MESS_REJ Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: Cell Broadcast
Counter 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 :
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.
External comment:
--
Alcatel-Lucent
Type name: Radio Measurement Statistics
- In Detailed usage: The union of all observed cells per BSS for the detailed measurement types 1, 2,
3, 4, 5, 6, 19 (if used as Detailed), 26, 28 (if used as Detailed), 29 (if used as Detailed), 31, 34 (if used
Type definition:
Set of counters describing result of radio measurements for a given cell / TRX.
RMS10 Type 31 : Radio Measurement Statistics
Counter Name : VQ_NOISY_UL_INTERFERENCE Counter Integer
SFD reference : 3BK 10204 0486 DTZZA ("RMS") Length: 2
B10 TRX 1
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Counter definition:
Number of calls suffering from problem of interference on the uplink path.
Trigger condition:
Whenever a call verifies : 100*(INTERFERED_UL_SAMPLES / NUM_UL_SAMPLES) > VQ_INTF_THRESHOLD
This calculation is done when 48.058 RF CHANNEL RELEASE is received for the observed call.

INTERFERED_UL_SAMPLES = nb of times where AV_RXQUAL_UL_VQ > VQ_RXQUAL and
AV_RXLEV_UL_VQ>VQ_RXLEV

AV_RXQUAL_UL_VQ : average on VQ_AVERAGE measurements of RXQUAL_UL
AV_RXLEV_UL_VQ : average on VQ_AVERAGE measurements of RXLEV_UL
NUM_UL_SAMPLES : total number of averages calculated on UL measurements during the call on the
considered TRX
External comment:
--
Alcatel-Lucent
Counter Name : VQ_NOISY_DL_INTERFERENCE Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Number of calls suffering from problems of interference on the downlink path.
Trigger condition:
Whenever a call verifies : 100*(INTERFERED_DL_SAMPLES / NUM_DL_SAMPLES) > VQ_INTF_THRESHOLD

INTERFERED_DL_SAMPLES = nb of times where AV_RXQUAL_DL_VQ > VQ_RXQUAL and
AV_RXLEV_DL_VQ>VQ_RXLEV

AV_RXQUAL_DL_VQ : average on VQ_AVERAGE measurements of RXQUAL_DL
AV_RXLEV_DL_VQ : average on VQ_AVERAGE measurements of RXLEV_DL
NUM_DL_SAMPLES : total number of averages calculated on DL measurements during the call on the
considered TRX
External comment:
--
Alcatel-Lucent
Counter Name : VQ_NOISY_UL_COVERAGE Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Number of calls suffering from bad coverage on the uplink path.
Trigger condition:
Whenever a call verifies : 100*(BAD_COVERAGE_UL_SAMPLES / NUM_UL_SAMPLES) >
VQ_INTF_THRESHOLD

BAD_COVERAGE_UL_SAMPLES = nb of times where AV_RXQUAL_UL_VQ > VQ_RXQUAL and
AV_RXLEV_UL_VQ<=VQ_RXLEV

NUM_UL_SAMPLES : total number of averages calculated on DL measurements during the call on the
considered TRX
External comment:
--
Alcatel-Lucent
Counter Name : VQ_NOISY_DL_COVERAGE Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Number of calls suffering from bad coverage on the downlink path.
Trigger condition:
Whenever a call verifies : 100*(BAD_COVERAGE_DL_SAMPLES / NUM_DL_SAMPLES) >
VQ_INTF_THRESHOLD

BAD_COVERAGE_DL_SAMPLES = nb of times where AV_RXQUAL_DL_VQ > VQ_RXQUAL and
AV_RXLEV_DL_VQ<=VQ_RXLEV

considered TRX
External comment:
--
Alcatel-Lucent
Counter Name : VQ_NOISY_UL_UNDEFINED Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Number of calls suffering from both problem of interference and bad coverage on the uplink path.
These calls are not counted in VQ_NOISY_UL_COVERAGE or VQ_NOISY_UL_INTERFERENCE.
Trigger condition:
Whenever a call verifies :
100*(BAD_COVERAGE_UL_SAMPLES / NUM_UL_SAMPLES) <= VQ_INTF_THRESHOLD
and
100*(INTERFERED_UL_SAMPLES / NUM_UL_SAMPLES) <= VQ_INTF_THRESHOLD
and
100*(BAD_QUALITY_UL_SAMPLES / NUM_UL_SAMPLES) > VQ_INTF_THRESHOLD

BAD_COVERAGE_UL_SAMPLES = nb of times where AV_RXQUAL_UL_VQ > VQ_RXQUAL and
AV_RXLEV_UL_VQ<=VQ_RXLEV
INTERFERED_UL_SAMPLES = nb of times when AV_RXQUAL_UL_VQ > VQ_RXQUAL and
AV_RXLEV_UL_VQ > VQ_RXLEV
BAD_QUALITY_UL_SAMPLES = INTERFERED_UL_SAMPLES + BAD_COVERAGE_UL_SAMPLES
= nb of times when AV_RXQUAL_UL_VQ > VQ_RXQUAL

considered TRX
External comment:
--
Alcatel-Lucent
Counter Name : VQ_NOISY_DL_UNDEFINED Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Number of calls suffering from both problem of interference and bad coverage on the downlink path.
These calls are not counted in VQ_NOISY_DL_COVERAGE or VQ_NOISY_DL_INTERFERENCE.
Trigger condition:
100*(BAD_COVERAGE_DL_SAMPLES / NUM_DL_SAMPLES) <= VQ_INTF_THRESHOLD
and
100*(INTERFERED_DL_SAMPLES / NUM_DL_SAMPLES) <= VQ_INTF_THRESHOLD
and
100*(BAD_QUALITY_DL_SAMPLES / NUM_DL_SAMPLES) > VQ_INTF_THRESHOLD

BAD_COVERAGE_DL_SAMPLES = nb of times where AV_RXQUAL_DL_VQ > VQ_RXQUAL and
AV_RXLEV_DL_VQ<=VQ_RXLEV
INTERFERED_DL_SAMPLES = nb of times when AV_RXQUAL_DL_VQ > VQ_RXQUAL and
AV_RXLEV_DL_VQ > VQ_RXLEV
BAD_QUALITY_DL_SAMPLES = INTERFERED_DL_SAMPLES + BAD_COVERAGE_DL_SAMPLES
= nb of times when AV_RXQUAL_DL_VQ > VQ_RXQUAL

considered TRX
External comment:
--
Alcatel-Lucent
Counter Name : VQ_NOISY_UL_BAD_FER Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Number of calls with bad quality measurements and with bad FER measurements on the uplink path.
Trigger condition:
and
100*(BAD_QUAL_BAD_FER_UL_SAMPLES / BAD_QUALITY_UL_SAMPLES) > VQ_FER_THRESHOLD

In the equations above, the following notations are used:
* BAD_QUALITY_UL_SAMPLES = INTERFERED_UL_SAMPLES + BAD_COVERAGE_UL_SAMPLES = nb of
times when AV_RXQUAL_UL_VQ > VQ_RXQUAL

* BAD_QUAL_BAD_FER_UL_SAMPLES = nb of times when AV_RXQUAL_UL_VQ > VQ_RXQUAL_VS_RXFER
and AV_RXFER_UL_VQ > VQ_BAD_RXFER

* AV_RXQUAL_UL_VQ : average on VQ_AVERAGE measurements of RXQUAL_UL

* AV_RXLEV_UL_VQ : average on VQ_AVERAGE measurements of RXLEV_UL

* NUM_UL_SAMPLES : total number of averages calculated on UL measurements during the call on the
considered TRX
External comment:
--
Alcatel-Lucent
Counter Name : VQ_NOISY_UL_GOOD_FER Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Number of calls with bad quality measurements but with good FER measurements on the uplink path.
Trigger condition:
and
100*(BAD_QUAL_GOOD_FER_UL_SAMPLES / BAD_QUALITY_UL_SAMPLES) > VQ_FER_THRESHOLD

BAD_QUALITY_UL_SAMPLES = INTERFERED_UL_SAMPLES + BAD_COVERAGE_UL_SAMPLES
= nb of times when AV_RXQUAL_UL_VQ > VQ_RXQUAL
BAD_QUAL_GOOD_FER_UL_SAMPLES = nb of times when AV_RXQUAL_UL_VQ >
VQ_RXQUAL_VS_RXFER
and AV_RXFER_UL_VQ <= VQ_GOOD_RXFER

AV_RXFER_UL_VQ : average on VQ_AVERAGE measurements of FER_UL
considered TRX
External comment:
--
Alcatel-Lucent
Counter Name : VQ_ABNORMAL_BAD_FER Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Number of calls with fair quality measurements but with bad FER measurements on the uplink path.
Trigger condition:
100*(FAIR_QUAL_BAD_FER_UL_SAMPLES / FAIR_QUALITY_UL_SAMPLES) > VQ_FER_THRESHOLD

FAIR_QUAL_BAD_FER_UL_SAMPLES = nb of times when AV_RXQUAL_UL_VQ<VQ_RXQUAL_VS_RXFER
and AV_RXFER_UL_VQ>VQ_BAD_RXFER

AV_RXFER_UL_VQ : average on VQ_AVERAGE measurements of FER_UL
considered TRX
External comment:
--
Alcatel-Lucent
Observation Name : TRE_BAND Length: 1
Measured number
Observation
Frequency band of the TRX.

The frequency band of the TRX is encoded as follows:
00: The frequencies defined are those available
for a P-GSM TRX (See external comment)
for a DCS1800 TRX (See external comment)
for a E-GSM TRX (See external comment)
for a DCS1900 TRX (See external comment)
04: Not used
05: Not used
for a GSM850 TRX (See external comment)
External comment:
The term E-GSM TRX refers to :
1. a TRX configured with at least one frequency belonging to the G1 band in an E-GSM cell (i.e. a cell where
Observation Name : IND_TRE_OVERLOAD Length: 1
Measured number
Observation
Indicator whether a TRX overload occurred.
External comment:
--
Observation Name : IND_RMS_RESTARTED Length: 1
Measured number
Observation
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).
External comment:
--
Alcatel-Lucent
Observation Name : IND_CI_PARTIAL_OBSERVATION Length: 1
Measured number
Observation
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
External comment:
--
Observation Name : IND_CI_OVERFLOW Length: 1
Measured number
Observation
Flag indicating that the upper limit of 42 CI vectors is exceeded => each new result (couple (BSIC, ARFCN) ) will
not
be taken into account.
External comment:
--
Alcatel-Lucent
Counter Name : TOT_SEIZ_TCH Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
Number of successful TCH seizures for the concerned cell. This counter takes into account TCH in traffic or in
signaling mode.
Trigger condition:
Whenever an ESTABLISH INDICATION message is received from the MS to indicate the activation of a TCH
channel for normal assignment or handover.
External comment:
--
Counter Name : TOT_MEAS Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : TOT_MEAS_L1INFO_NOL3INFO Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Number of MEASUREMENT RESULTS messages sent without Layer 3 information but with Layer 1 present.
The result is first calculated by the BTS at a TRX level, then compilated by the BSC at a cell level.
This counter reflects the uplink quality, it is incremented due to bad uplink radio quality or long handover
interruptions.
Trigger condition:
Whenever a 48.058 MEASUREMENT RESULTS message is sent by the BTS without Layer 3 information but with
Layer 1 present, and used for RMS.
External comment:
--
Counter Name : TOT_MEAS_DTX_UL Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : TOT_MEAS_DTX_DL Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter 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.
External comment:
--
Counter Name : PERC_TA_GT_TA_STAT Counter Round (x)
Data collection Cumulative Measured %
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Reserved for internal Alcatel-Lucent usage (PS detection on TS basis for Edge capable TRX)
Trigger condition:
External comment:
--
Alcatel-Lucent
Observation Name : MAX_TA Length: 1
Measured bper
Observation
Reserved for internal Alcatel-Lucent usage (PS detection on TS basis for Edge capable TRX)
External comment:
--
Counter Name : TOT_EMR Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Total number of Extended Measurement Results.
Trigger condition:
External comment:
--
Alcatel-Lucent
RMS3a Type 31 : Radio Measurement Statistics
Counter Name : TPR_RXQUAL_UL_RXLEV_UL Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Table of 3x 8x10 results.
Each cell (i,j) of the table contains :
1) number of reports in which UL RXQUAL is equal to j and UL RXLEV is reported in level band i (Cij)
2) corresponding averaged value of MS power level
3) corresponding averaged value of Timing Advance
For Cij, the result is given as follows :
Cij=Vij x 254 / Max_i, where Vij represents the real number of measurements, and Max_i the greatest value of Vij,
for i given (see RMS3b).
Cij=0 indicates 'number of measurements = 0'
Cij=254 indicates 'number of measurements = Max_i'
Cij=255 is reserved to indicate overflow.
The values of the average MS power level (2) and the average Timing Advance (3) are directly given, both with a
precision of 0.25. Note that these values (2 and 3) that are indicated in the ASCII file, which can be obtained via
the OBSYNT interface, still have to be divided by 4, whereas the values that are provided at the user interface are
the correct ones.

UL RXQUAL can take values from 0 to 7.
Level band i is defined by : MEAS_STAT_LEV_(i-1)<= RXLEV < MEAS_STAT_LEV_i
MEAS_STAT_LEV_0 = -47 dBm, MEAS_STAT_LEV_10 = -110 dBm
According to 3GPP, values of RXLEV lower than -110 dBm are considered as equal to -110 dBm
Trigger condition:
Whenever in a 44.018 MEASUREMENT RESULT uplink RXQUAL is equal to j, while uplink RXLEV for the same
call is in the given interval of MEAS_STAT_LEV.
External comment:
--
Alcatel-Lucent
RMS3b Type 31 : Radio Measurement Statistics
Counter Name : TMR_RXQUAL_UL_RXLEV_UL Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Table of 10 maximum results.
Each cell Ci of the table indicates the greatest value of the Vij for a i given in RMS3a.
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : AMR_WB_GMSK_FR_UL_BAD Counter Integer
SFD reference : 3BK 10204 0095 DTZZA (AMR WB speech codec GMSK) Length: 3
B10 TRX 1
Sub domain-2:
Counter definition:
Table of 3 results

Each cell (i) of the table contains:
number of FR AMR WB GMSK UL bad speech frames.

The result is given as follows :
- Ci=MAX(Round[Vi x 254 / Max], 1), where Vi represents the real number of measurements, and Max the
greatest value of Vi (see RMS41b).
- Ci=0 indicates 'number of measurements = 0'
- Ci=254 indicates 'number of measurements = Max'
- Ci=255 is reserved to indicate overflow.

FR AMR WB GMSK codecs are defined by :
- codec 1 = 6.60 kbit/s, codec 2 = 8.85 kbit/s, codec 3 = 12.65 kbit/s.
Trigger condition:
The TRE counts for each AMR WB call and for each FR AMR WB GMSK codec the number of bad speech
frames received from the MS (or sent to the TC) in uplink. Only speech frames of type "Speech_Degraded",
"Speech_Bad" or "SID_Bad" shall be taken into account.
External comment:
This counter is only reported for cells mapped on Evolium BTS.
Alcatel-Lucent
Counter Name : MAX_AMR_WB_GMSK_FR_UL_BAD Counter Integer
B10 TRX 1
Sub domain-2:
Counter definition:
Greatest values of the Vi in RM41a.
Trigger condition:
External comment:
Alcatel-Lucent
Counter Name : AMR_WB_GMSK _FR_UL_RXLEV_UL Counter Integer
B10 TRX 1
Sub domain-2:
Counter definition:
Table of 3x10 results

Each cell (i,k) of the table contains:
1) number of correct UL speech frames using FR AMR WB GMSK codec k for which UL RXLEV is reported in
level band i. The result is given as follows:
- Cik=MAX(Round[Vik x 254 / Max_i], 1), where Vik represents the real number of measurements, and Max_i the
greatest value of Vik, for i given (see RMS42b).
- Cik=0 indicates 'number of measurements = 0'
- Cik=254 indicates 'number of measurements = Max_i'
- Cik=255 is reserved to indicate overflow.

Level band i is defined by : MEAS_STAT_LEV_j<= RXLEV < MEAS_STAT_LEV_I
j = i 1

FR AMR WB GMSK codecs are defined by:
codec 1 = 6.60 kbit/s, codec 2 = 8.85 kbit/s, codec 3 = 12.65 kbit/s.

Trigger condition:
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.
External comment:
Alcatel-Lucent
Counter Name : MAX_AMR_WB_GMSK_FR_UL_RXLEV_UL Counter Integer
B10 TRX 1
Sub domain-2:
Counter definition:

Each cell Ci of the table indicates the greatest value of the Vik for a i given in RMS42a.
Trigger condition:
External comment:
Alcatel-Lucent
Counter Name : AMR_WB_GMSK_FR_DL_RXLEV_DL Counter Integer
B10 TRX 1
Sub domain-2:
Counter definition:

Each cell (i,k) of the table contains :
1) number of correct DL speech frames using FR AMR WB GMSK codec k for which DL RXLEV is reported in
level band i.


Cik=MAX(Round[Vik x 254 / Max_i], 1), where Vik represents the real number of measurements, and Max_I the
Cik=0 indicates 'number of measurements = 0'
Cik=254 indicates 'number of measurements = Max_i'
Cik=255 is reserved to indicate overflow.

Level band i is defined by : MEAS_STAT_LEV_j<= RXLEV < MEAS_STAT_LEV_i
j = i - 1

FR AMR WB GMSK codecs are defined by:
codec 1 = 6.60 kbit/s, codec 2 = 8.85 kbit/s, codec 3 = 12.65 kbit/s.
Trigger condition:
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.
External comment:
Alcatel-Lucent
Counter Name : MAX_AMR_WB_GMSK_FR_DL_RXLEV_DL Counter Integer
B10 TRX 1
Sub domain-2:
Counter definition:
Trigger condition:
External comment:
Alcatel-Lucent
Counter Name : AMR_FR_UL_BAD Counter Integer
SFD reference : 3BK 10204 0544 DTZZA ("RMS improvements") Length: 8
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
Table of 8 results
Each cell (i) of the table contains :
number of AMR FR UL bad speech frames.
Ci=MAX(Round[Vi x 254 / Max], 1), where Vi represents the real number of measurements, and Max the greatest
value of Vi (see RMS44b).
Ci=0 indicates 'number of measurements = 0'
Ci=254 indicates 'number of measurements = Max'
Ci=255 is reserved to indicate overflow.

AMR FR codecs are defined by :
codec 1 = 4.75 kbit/s, codec 2 = 5.15 kbit/s, codec 3 = 5.9 kbit/s, codec 4 = 6.7 kbit/s, codec 5 = 7.4 kbit/s,
codec 6 = 7.95 kbit/s, codec 7 = 10.2 kbit/s, codec 8 = 12.2 kbit/s
Trigger condition:
The TRE counts for each AMR call and for each AMR FR codec the number of bad speech frames received from
the MS (or sent to the TC) in uplink. Only speech frames of type "Speech_Degraded", "Speech_Bad" or
"SID_Bad" shall be taken into account.
External comment:
Alcatel-Lucent
Counter Name : MAX_AMR_FR_UL_BAD Counter Integer
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
Greatest value of the Vi in RM44a.
Trigger condition:
External comment:
Alcatel-Lucent
Counter Name : AMR_HR_UL_BAD Counter Integer
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
Table of 5 results
number of AMR HR UL bad speech frames.
Ci=MAX(Round[Vi x 254 / Max], 1), where Vi represents the real number of measurements, and Max the greatest
value of Vi (see RMS45b).

AMR HR codecs are defined by :
codec 1 = 4.75 kbit/s, codec 2 = 5.15 kbit/s, codec 3 = 5.9 kbit/s, codec 4 = 6.7 kbit/s, codec 5 = 7.4 kbit/s
Trigger condition:
The TRE counts for each AMR call and for each AMR HR codec the number of bad speech frames received from
the MS (or sent to the TC) in uplink. Only speech frames of type "Speech_Degraded", "Speech_Bad" or
"SID_Bad" shall be taken into account.
External comment:
Alcatel-Lucent
Counter Name : MAX_AMR_HR_UL_BAD Counter Integer
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
Trigger condition:
External comment:
Alcatel-Lucent
Counter Name : AMR_FR_UL_RXLEV_UL Counter Integer
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
1) number of correct UL speech frames using AMR FR codec k for which UL RXLEV is reported in level band i.
Cik=MAX(Round[Vik x 254 / Max_i], 1), where Vik represents the real number of measurements, and Max_i the


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.
External comment:
Alcatel-Lucent
Counter Name : MAX_AMR_FR_UL_RXLEV_UL Counter Integer
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
Trigger condition:
External comment:
Alcatel-Lucent
Counter Name : AMR_FR_DL_RXLEV_DL Counter Integer
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
1) number of correct DL speech frames using AMR FR codec k for which DL RXLEV is reported in level band i.


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
corresponding to reported DL RXLEV.
External comment:
Alcatel-Lucent
Counter Name : MAX_AMR_FR_DL_RXLEV_DL Counter Integer
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
Trigger condition:
External comment:
Alcatel-Lucent
Counter Name : AMR_HR_UL_RXLEV_UL Counter Integer
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
1) number of correct speech frames using AMR HR codec k for which UL RXLEV is reported in level band i.


codec 1 = 4.75 kbit/s, codec 2 = 5.15 kbit/s, codec 3 = 5.9 kbit/s, codec 4 = 6.7 kbit/s, codec 5 = 7.4 kbit/s.
Trigger condition:
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
External comment:
Alcatel-Lucent
Counter Name : MAX_AMR_HR_UL_RXLEV_UL Counter Integer
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
Trigger condition:
External comment:
Alcatel-Lucent
Counter Name : AMR_HR_DL_RXLEV_DL Counter Integer
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
1) number of correct DL speech frames using AMR HR codec k for which DL RXLEV is reported in level band i.


codec 1 = 4.75 kbit/s, codec 2 = 5.15 kbit/s, codec 3 = 5.9 kbit/s, codec 4 = 6.7 kbit/s, codec 5 = 7.4 kbit/s.
Trigger condition:
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
corresponding to reported DL RXLEV.
External comment:
Alcatel-Lucent
Counter Name : MAX_AMR_HR_DL_RXLEV_DL Counter Integer
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
Trigger condition:
.
External comment:
Alcatel-Lucent
Counter Name : TPR_RXQUAL_DL_RXLEV_DL Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Table of 3x 8x10 results.
1) number of reports in which DL RXQUAL is equal to j and DL RXLEV is reported in level band I (Cij)
2) corresponding averaged value of BS power level :
For G2 BTS : corresponding averaged value of [BTS_MAX_OUTPUT_POWER - abs(BS_TXPWR)]
For Evolium BTS : corresponding averaged value of [ MAX_POWER_PER_TRX- abs(BS_TXPWR)].
BS_TXPWR is the BTS transmitted power defined relatively to the maximum absolute output power of the BTS.
BS_TXPWR is expressed in dB, whereas BTS_MAX_OUTPUT_POWER is expressed in dBm. Note that the
formula is written independently of the coding used for the variables. The function abs() gives the absolute value
of
its argument.
3) corresponding averaged value of Timing Advance
For Cij, the result is given as follows :
The values of the average BS power level (2) and the average Timing Advance (3) are directly given, both with a
precision of 0.25. Note that these values (2 and 3) that are indicated in the ASCII file, which can be obtained via
the OBSYNT interface, still have to be divided by 4, whereas the values that are provided at the user interface are
the correct ones.

DL RXQUAL can take values from 0 to 7.
Trigger condition:
Whenever in a 44.018 MEASUREMENT RESULT DL RXQUAL is equal to j, while DL RXLEV for the same call is
in the given interval of MEAS_STAT_LEV.
External comment:
--
Alcatel-Lucent
Counter Name : TMR_RXQUAL_DL_RXLEV_DL Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : TPR_TIMING_ADVANCE Counter Integer
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
Table of 10 results
1) number of reports in which Timing Advance is in Timing Advance band i
Ci=MAX(ROUND[Vi x 254 / Max], 1), where Vi represents the real number of measurements, and Max the
greatest value of Vi, (see RMS50b).

Timing Advancee band is defined by :
MEAS_STAT_TA_(i-1)<= Timing Advance < MEAS_STAT_TA_i
MEAS_STAT_TA_0 = 0 bper, MEAS_STAT_TA_10 = 63 bper
Trigger condition:
Whenever in a 44.018 MEASUREMENT RESULT the Timing Advance is in the given interval of
MEAS_STAT_TA.
External comment:
Alcatel-Lucent
Counter Name : MAX_TIMING_ADVANCE Counter Integer
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
Trigger condition:
External comment:
Counter Name : TPR_UL_RXLEV_TA_BAND Counter Integer
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
Table of 10 results
average value of UpLink Rxlev of reports in TA band i.
Averaged Rxlev is given with a precision of 2 digits after the comma (step size for coding = 0.01, -110 dBm coded
0, -109.99 dBm coded 1...).

i = 1...10

TA band i is defined by : MEAS_STAT_TA_ (i-1)<= Timing Advance < MEAS_STAT_TA_i
MEAS_STAT_TA_0 = 0 bper, MEAS_STAT_TA_10 = 63 bper.
Trigger condition:
Whenever a MEASUREMENT RESULT is received, UL RXLEV is stored.
At the end of the measurement period, UL RXLEV corresponding to the same TA band are averaged.
External comment:
Alcatel-Lucent
Counter Name : TPR_DL_RXLEV_TA_BAND Counter Integer
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
Table of 10 results
average value of DownLink Rxlev of reports in TA band i.
Averaged Rxlev is given with a precision of 2 digits after the comma (step size for coding = 0.01, -110 dBm coded
0, -109.99 dBm coded 1...).

i = 1...10

Trigger condition:
Whenever a MEASUREMENT RESULT is received, DL RXLEV is stored.
At the end of the measurement period, DL RXLEV corresponding to the same TA band are averaged.
External comment:
Alcatel-Lucent
Counter Name : TPR_UL_RXQUAL_TA_BAND Counter Integer
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
Table of 10 results
average value of UpLink Rxqual of reports in TA band i.
Averaged Rxqual is given with a precision of 2 digits after the comma (step size for coding = 0.01, 0 coded 0, 0.01
coded 1, ...).

i = 1...10

Trigger condition:
Whenever a MEASUREMENT RESULT is received, UL RXQUAL is stored.
At the end of the measurement period, UL RXQUAL corresponding to the same TA band are averaged.
External comment:
Alcatel-Lucent
Counter Name : TPR_DL_RXQUAL_TA_BAND Counter Integer
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
Table of 10 results
average value of DownLink Rxqual of reports in TA band i.
Averaged Rxqual is given with a precision of 2 digits after the comma (step size for coding = 0.01, 0 coded 0, 0.01
coded 1, ...).

i = 1...10

Trigger condition:
Whenever a MEASUREMENT RESULT is received, DL RXQUAL is stored.
At the end of the measurement period, DL RXQUAL corresponding to the same TA band are averaged.
External comment:
Alcatel-Lucent
Counter Name : TPR_BFI_RXLEV_UL Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
1) number of reports in which consecutive BFI counter is in BFI band j and UL RXLEV is reported in level band I
(Cij)

BFI band is defined by : MEAS_STAT_BFI_(j-1)<= Consecutive BFI counter < MEAS_STAT_BFI_j
MEAS_STAT_BFI_0 = 0, MEAS_STAT_BFI_10 = 25
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.
External comment:
--
Alcatel-Lucent
Counter Name : TMR_BFI_RXLEV_UL Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : TPR_RADIO_LINK Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Table of 10 results
1) number of reports in which Radio linkI counter is in S band i
Ci=Vi x 254 / Max_i, where Vi represents the real number of measurements, and Max_i the greatest value of Vi
(see RMS6b).
Ci=254 indicates 'number of measurements = Max_i'

S band is defined by : MEAS_STAT_S_(i-1)<= Radio link counter < MEAS_STAT_S_i
MEAS_STAT_S_0 = 0, MEAS_STAT_S_10 = 128
Trigger condition:
Whenever the Radio Link counter (S) is in the given interval of MEAS_STAT_S.
External comment:
--
Counter Name : MAX_RADIO_LINK Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Greatest value of the Vi in RMS6a.
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : TPR_PATH_BALANCE Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Table of 10 results
1) number of reports in which Path Balance is in Path Balance band i
Ci=Vi x 254 / Max_i, where Vi represents the real number of measurements, and Max_i the greatest value of Vi,
(see RMS7b).

Path Balance band is defined by :
MEAS_STAT_PATH_BALANCE_(i-1)<= Path balance < MEAS_STAT_PATH_BALANCE_i
MEAS_STAT_PATH_BALANCE_0 = -110 dB, MEAS_STAT_PATH_BALANCE_10 = 110 dB
Trigger condition:
Whenever in a 44.018 MEASUREMENT RESULT the Path Balance is in the given interval of
MEAS_STAT_PATH_BALANCE.

Path Balance = (RXLEV_UL-MS_TXPWR) - (RXLEV_DL - [BTS_MAX_OUTPUT_POWER - abs(BS_TXPWR)]),
where BS_TXPWR is the BTS transmitted power defined relatively to the maximum absolute output power of the
BTS. BS_TXPWR is expressed in dB, whereas BTS_MAX_OUTPUT_POWER is expressed in dBm. RXLEV_UL
and RXLEV_DL are the received signal levels by the base station and by the mobile station respectively. They are
expressed in dBm. MS_TXPWR is the transmission power of the mobile station and expressed in dBm, too. Note
that the formula is written independently of the coding used for the variables. The function abs() gives the
absolute
value of its argument.
External comment:
--
Alcatel-Lucent
Counter Name : MAX_PATH_BALANCE Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : TPR_CIN Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Table of 10 results per neighbour cell.
Each cell i of the table contains :
1) number of reports in which the C/I related to the neighbour cell is reported in C/I band i.
Ci=Vi x 254 / RMS8b, where Vi represents the real number of measurements

C/I band is defined by :
MEAS_STAT_PATH_C_I_(i-1)<= C/I < MEAS_STAT_C_I_i
MEAS_STAT_PATH_C_I_0 = -63 dB, MEAS_STAT_PATH_C_I_10 = 63 dB

If EN_BALANCED_CI = TRUE then
C/I (dB) = RXLEV_DL + abs(BS_TXPWR - BS_TXPWR_MAX) - RXLEV_NCELL
Note that the formula is written independently of the coding used for the variables. RXLEV_DL and
RXLEV_NCELL
are the received signal levels of the serving and of the neighbour cells, expressed in dBm. BS_TXPWR is the
BTS
transmitted power and BS_TXPWR_MAX is the maximum allowed BTS transmission power. Both are defined
relatively to the maximum absolute output power of the BTS (BTS_MAX_OUTPUT_POWER). BS_TXPWR and
BS_TXPWR_MAX are expressed in dB. The function abs() gives the absolute value of its argument.
else
C/I (dB) = RXLEV_DL (dBm) - RXLEV_NCELL (dBm)
Trigger condition:
Whenever a measurement report indicates that C/I value for the call related to the neighbour cell is included in
the
corresponding interval.
External comment:
--
Alcatel-Lucent
Counter Name : MR_CIN Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : TPR_CIF Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Table of 10 results per frequency reported by extended measurement.
Each cell i of the table contains :
1) number of reports in which the C/I related to the extended measurement frequency is reported in C/I band i.
Ci=Vi x 254 / RMS9b, where Vi represents the real number of measurements

C/I band is defined by :
MEAS_STAT_PATH_C_I_(i-1)<= C/I < MEAS_STAT_C_I_i
MEAS_STAT_PATH_C_I_0 = -63 dBm, MEAS_STAT_PATH_C_I_10 = 63 dBm

If EN_BALANCED_CI = TRUE then
C/I (dB) = RXLEV_DL + abs(BS_TXPWR - BS_TXPWR_MAX) - RXLEV_NCELL
Note that the formula is written independently of the coding used for the variables. RXLEV_DL and
RXLEV_NCELL
are the received signal levels of the serving and of the neighbour cells, expressed in dBm. BS_TXPWR is the
BTS
transmitted power and BS_TXPWR_MAX is the maximum allowed BTS transmission power. Both are defined
relatively to the maximum absolute output power of the BTS (BTS_MAX_OUTPUT_POWER). BS_TXPWR and
BS_TXPWR_MAX are expressed in dB. The function abs() gives the absolute value of its argument.
else
C/I (dB) = RXLEV_DL (dBm) - RXLEV_NCELL (dBm)
Trigger condition:
Whenever a measurement report indicates that C/I value for the extended measurement frequency is included in
the corresponding interval.
External comment:
--
Alcatel-Lucent
Counter Name : MR_CIF Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2:
Counter definition:
Trigger condition:
External comment:
--
RMSp80
Parameter Name : NEIGB_CELL_ID Type 31 : Radio Measurement Statistics
Measured unit: number
Parameter definition:
BCCH ARFCN and BSIC of the neighbour cell.
External comment:
--
RMSp90
Parameter Name : Frequency ARFCN Type 31 : Radio Measurement Statistics
ARFCN of the frequency reported via Extended Measurement Reporting.
External comment:
--
Alcatel-Lucent
RMSpa
Parameter Name : PAR_EN_BALANCED_CI Type 31 : Radio Measurement Statistics
Indicates if the C/I measure is balanced or not.
External comment:
--
RMSpb
Parameter Name : PAR_TA_STAT Type 31 : Radio Measurement Statistics
Measured unit: bper
Contains the value of the parameter TA_STAT.
TA_STAT is a Threshold on timing advance to define the cell limit used for Radio Measurements Statistics.
Min = 0 bit, max = 64 bit
External comment:
--
RMSpc
Parameter Name : PAR_VQ_AVERAGE Type 31 : Radio Measurement Statistics
Measured unit: Samfr
PAR_VQ_AVERAGE contains the value of the parameter VQ_AVERAGE for the concerned cell.
VQ_AVERAGE represents the Average window size on measurements to obtain samples for Voice Quality
statistics.
Min=0 Samfr, max=128 Samfr
External comment:
--
RMSpd
Parameter Name : PAR_VQ_RXLEV Type 31 : Radio Measurement Statistics
Measured unit: dBm
PAR_VQ_RXLEV contains the value of the parameter VQ_RXLEV for the concerned cell.
VQ_RXLEV is Radio level threshold to specify bad quality samples for Voice Quality statistics.
Min = -110 dBm, max=-65 dBm
External comment:
--
Alcatel-Lucent
RMSpe
Parameter Name : PAR_VQ_RXQUAL Type 31 : Radio Measurement Statistics
PAR_VQ_RXQUAL represents the value of the parameter VQ_RXQUAL.
VQ_RXQUAL is a Radio quality threshold to specify bad quality samples for Voice Quality statistics.
Min = 0, Max = 7
External comment:
--
RMSpf
Parameter Name : PAR_VQ_RXQUAL_VS_RXFER Type 31 : Radio Measurement Statistics
PAR_VQ_RX contains the value of the parameter VQ_RXQUAL_VS_RXFER for the concerned cell.
VQ_RXQUAL_VS_RXFER is a Radio quality threshold to specify correlation between quality samples for Voice
Quality statistics.
Min = 0, Max = 7
External comment:
--
RMSpg
Parameter Name : PAR_VQ_GOOD_RXFER Type 31 : Radio Measurement Statistics
Measured unit: %
PAR_VQ_GOOD_RXFER contains the value of the parameter VQ_GOOD_RXFER for the concerned cell.
VQ_GOOD_RXFER is a Radio good FER threshold to specify bad quality samples for Voice Quality statistics.
Min = 0%, Max = 20%
External comment:
--
Alcatel-Lucent
RMSph
Parameter Name : PAR_VQ_BAD_RXFER Type 31 : Radio Measurement Statistics
Measured unit: %
PAR_VQ_BAD_RXFER contains the value of the parameter VQ_BAD_RXFER for the concerned cell.
VQ_BAD_RXFER is the Radio bad FER threshold to specify bad quality samples for Voice Quality statistics.
Min = 0 %, max= 20%
External comment:
--
RMSpi
Parameter Name : PAR_VQ_INTF_THRESHOLD Type 31 : Radio Measurement Statistics
Measured unit: %
PAR_VQ_INTF_THRESHOLD contains the value of the parameter VQ_INTF_THRESHOLD for the concerned
cell.
VQ_INTF_THRESHOLD is the Radio interference threshold to detect noisy calls for Voice Quality statistics.
Min = 0%, Max= 100%
External comment:
--
RMSpj
Parameter Name : PAR_VQ_FER_THRESHOLD Type 31 : Radio Measurement Statistics
Measured unit: %
PAR_VQ_FER_THRESHOLD contains the value of the parameter VQ_FER_THRESHOLD for the concerned cell.
VQ_FER_THRESHOLD is the Radio FER threshold to detect calls with bad speech quality for Voice Quality
statistics.
Min=0%, Max=100%
External comment:
--
Alcatel-Lucent
RMSpt1
Parameter Name : TAB_PAR_MEAS_C/I Type 31 : Radio Measurement Statistics
Measured unit: dB
Table of value for 9 parameters : MEAS_STAT_C_I1 to MEAS_STAT_C_I9
MEAS_STAT_C_Ii is a Threshold on radio C/I (Carrier/Interference) measurements to define bands used for
Radio
Measurements Statistics
Min value = -63 dB, max value= 63 dB
External comment:
--
RMSpt2
Parameter Name : TAB_PAR_MEAS_STAT_BFI Type 31 : Radio Measurement Statistics
Table of value for 9 parameters : MEAS_STAT_BFI1 to MEAS_STAT_BFI9
MEAS_STAT_BFIi is a Threshold on successive Bad Frame Indication to define bands used for Radio
Measurements Statistics.
Min value =0, max value= 25
External comment:
--
RMSpt3
Parameter Name : TAB_PAR_MEAS_STAT_S Type 31 : Radio Measurement Statistics
Measured unit: Samfr
Table of value for 9 parameters : MEAS_STAT_S1 to MEAS_STAT_S9
MEAS_STAT_Si is a Threshold on radio link counter to define bands used for Radio Measurements Statistics.
Min value =0 Samfr, max value= 128 Samfr
External comment:
--
Alcatel-Lucent
RMSpt4
Parameter Name : TAB_PAR_MEAS_PATH_BALANCE Type 31 : Radio Measurement Statistics
Measured unit: dB
Table of value for 9 parameters : MEAS_STAT_PATH_BAL1 to MEAS_STAT_PATH_BAL9
MEAS_STAT_PATH_BALi is a Threshold on path balance to define bands used for Radio Measurements
Statistics.

Min value =-110 dB, max value= 110 dB
External comment:
--
RMSpt5
Parameter Name : TAB_PAR_MEAS_LEVEL Type 31 : Radio Measurement Statistics
Measured unit: dBm
Table of value for 9 parameters : MEAS_STAT_LEV1 to MEAS_STAT_LEV9
MEAS_STAT_LEVi is a threshold on radio level to define bands used for Radio Measurements Statistics.
Min value = -110 dBm, max value= -47 dBm
External comment:
--
RMSpt6
Parameter Name : TAB_PAR_MEAS_STAT_TA Type 31 : Radio Measurement Statistics
Measured unit: bper
Table of value for 9 parameters : MEAS_STAT_TA1 to MEAS_STAT_TA9
MEAS_STAT_TAi is a Threshold on Timing Advance measurements to define bands used for Radio
Measurements
Statistics
Min value = 0 bper, max value= 63 bper
External comment:
Alcatel-Lucent
RMSpw1
Parameter Name : BS_TX_PWRMAX Type 31 : Radio Measurement Statistics
Measured unit: dB
Value of the parameter BS_TX_PWRMAX (BTS maximum allowed transmit power).
If the cell is concentric, the value of the inner or the outer zone will be reported, depending on the TRX.
External comment:
--
RMSpw2
Parameter Name : MS_TX_PWRMAX Type 31 : Radio Measurement Statistics
Measured unit: dBm
Value of the parameter MS_TX_PWRMAX (MS maximum allowed transmit power).
If the cell is concentric, the value of the inner or the outer zone will be reported, depending on the TRX.
External comment:
--
RMSPw3 Type 31 : Radio Measurement Statistics
Counter Name : MAX_POWER_PER_TRX Counter Integer
Data collection Cumulative Measured dBm
B10 TRX 1
B9 TRX 1
Sub domain-2:
Counter definition:
Maximum GMSK TRX power level applied at the BTS antenna output connector in dBm.
The power takes into account the different losses (cables, internal combiners) and the internal/ external leveling
but it does not take into account the BS-TXPWR-MAX, attenuation required by the OMC_R.
If the feature "unbalancing TRX output power per BTS sector" is activated (parameter
"En-Unbalanced-Output-Power" set to 1), the counter is set by the BTS to the power required by the BSC for the
corresponding TRE (i.e. for the TRE on which is mapped that TRX).
If the operator defines a fine attenuation which will impact the power of TREs in the cell, then RMSpw3 will also
reflect this extra attenuation.
Trigger condition:
Information provided by the BTS in RMS_DATA_IND message.
External comment:
Alcatel-Lucent
Type name: Change of frequency band measurements
In Standard usage: None
In Detailed usage: None
Type definition:
Set of counters related to handovers including a change of the TCH frequency band.
C403a Type 32 : Change of frequency band measurements
Counter Name : NB_INC_EXT_TCH_HO_NEW_BAND_ATPT Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
Number of incoming external TCH (in HR or FR usage) handover attempts including a change of the (TCH)
frequency band.
Trigger condition:
Whenever 48.008 HANDOVER_REQUEST_ACK is sent by the target BSC containing the 44.018HANDOVER
COMMAND towards the target cell on TCH and the target and serving cell belong to different frequency bands.

Remark: The change of the (TCH) frequency band for an incoming external handover can only be detected and
taken into account if the adjacency link is defined in both directions. In case of multiband cells, the BCCH
frequency band of the serving cell will be taken as reference.

External comment:
--
Alcatel-Lucent
C403b Type 32 : Change of frequency band measurements
Counter Name : NB_INC_EXT_TCH_HO_NEW_BAND_SUCC Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
Number of incoming external TCH (in HR or FR usage) handover successes including a change of the (TCH)
frequency band.
Trigger condition:
TCH
channel that is involved in an external TCH handover with a change of the frequency band.

Remark: The change of the (TCH) frequency band for an incoming external handover can only be detected and
taken into account if the adjacency link is defined in both directions. In case of multiband cells, the BCCH
frequency band of the serving cell will be taken as reference.

External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_EXT_TCH_HO_NEW_BAND_ATPT Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
Number of outgoing external TCH (in HR or FR usage) handover attempts including a change of the (TCH)
frequency band.
Trigger condition:
an external 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_EXT_TCH_HO_NEW_BAND_SUCC Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
Number of outgoing external TCH (in HR or FR usage) handover successes including a change of the (TCH)
frequency band.
Trigger condition:
External TCH handover including a change of the TCH frequency band, in the following cases:
1/ 48.008 CLEAR COMMAND message with a cause value of "handover successful" is received.
2/ 48.008 CLEAR COMMAND (cause = "normal event/call control") is received while T8 is running.

External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_INT_TCH_HO_NEW_BAND_ATPT Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
Number of incoming internal TCH (in HR or FR usage) handover attempts including a change of the (TCH)
frequency band.
Trigger condition:
Whenever a 44.018HANDOVER COMMAND with a target cell belonging to a different frequency band is sent to
the serving BTS for internal inter cell TCH handover. However, the counter is incremented in the TARGET cell,
based on the target cell ID indicated by the HO Command message.
External comment:
--
Counter Name : NB_INC_INT_TCH_HO_NEW_BAND_SUCC Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
Number of incoming internal TCH (in HR or FR usage) handover successes including a change of the (TCH)
frequency band.
Trigger condition:
TCH
channel that is involved in an internal inter-cell TCH handover including a change of the (TCH) frequency band.
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_INT_TCH_HO_NEW_BAND_ATPT Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
Number of outgoing internal TCH (in HR or FR usage) handover attempts including a change of the (TCH)
frequency band.
Trigger condition:
an internal inter-cell TCH handover procedure including a change of the (TCH) frequency band.
External comment:
--
Counter Name : NB_OUT_INT_TCH_HO_NEW_BAND_SUCC Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
Number of outgoing internal TCH (in HR or FR usage) handover successes including a change of the (TCH)
frequency band.
Trigger condition:
Whenever a 44.018 HANDOVER COMPLETE message is received on Abis interface from the target cell , during
an internal inter-cell TCH handover including a change of the (TCH) frequency band.
External comment:
--
Alcatel-Lucent
Type name: Electro-Magnetic Emission counters
Type definition:
Set of counters related to electromagetic emission measurements in the BTS.
E01 Type 33 : Electro-Magnetic Emission counters
Counter Name : EME_PWR_GSM Counter Integer
SFD reference : 3BK 10204 0626 DTZZA ("EME supervision") Length: 2
Data collection Status Inspection (polling=10s) Measured Watt
B10 Common cell 1
B9 Common cell 1
Technology: GSM Sub domain-1: --
Sub domain-2:
Domain: Electro-Magnetic Emission Sub domain-3:
Counter 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.
External comment:
Counter coded in tenth of Watt. Value 0 indicates that TRX frequency is neither 900 MHz nor 850 MHz.
Alcatel-Lucent
E02 Type 33 : Electro-Magnetic Emission counters
Counter Name : EME_PWR_DCS Counter Integer
SFD reference : 3BK 10204 0626 DTZZA ("EME supervision") Length: 2
Data collection Status Inspection (polling=10s) Measured Watt
B10 Common cell 1
B9 Common cell 1
Technology: GSM Sub domain-1: --
Sub domain-2:
Domain: Electro-Magnetic Emission Sub domain-3:
Counter 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.
External comment:
Alcatel-Lucent
Type name: Voice Group Call Services
Type scope (per BSS): one or several cells
In Detailed usage: The union of all observed cells per BSS for the detailed measurement types 1, 2, 3,
4, 5, 6, 19 (if used as Detailed), 26, 28 (if used as Detailed), 29 (if used as Detailed), 31, 34 (if used
Type definition:
Set of counters related to Voice Group Call Services (VGCS).
V01 Type 34 : Voice Group Call Services
Counter Name : NB_PTP_CALL_PREEMPTED_VGCS Counter Integer
SFD reference : 3BK 10204 0652 DTZZA ("VGCS - eMLPP improvements") Length: 2
Data collection Cumulative Measured event
B10 Common cell 2
B9 Common cell 2
Counter definition:
Number of point-to-point CS-calls pre-empted for VGC channels per cell during observation period.
Trigger condition:
This counter is incremented each time a 48.008 CLEAR REQUEST message is sent to the MSC under the three
following conditions :
- "Cause" parameter is set to "Premption (0101001)" ;
- sent on a point-to-point SCCP connection, excluding the
VGCS talker connexion ;
- sent further to the reception and processing of either
- a 48.008 VGCS/VBS ASSIGNEMENT REQUEST
message received from the MSC with "Priority" parameter
having the information element "Preemption Capability
indicator (pci)" set to "this allocation request may preemt
an existing connection (1)" ; or
- a 48.008 ASSIGNEMENT REQUEST message
received from the MSC with "talker flag" parameter present
and with "Priority" parameter having the information
element "Preemption Capability indicator (pci)" set to "this
allocation request may preemt an existing connection (1)".
External comment:
--
Alcatel-Lucent
Counter Name : AV_PARALLEL_TCH_VGCS Counter Round (10
B10 Common cell 2
B9 Common cell 2
Sub domain-2: TCH
Counter definition:
Average number of parallel TCH in use for VGCS per cell during observation period.
TCH used for VGC listening service and TCH used for VGC talking service are both counted.
Trigger condition:
The BSC takes periodically a sample of the number of busy TCH radio timeslots allocated for VGCS.
The sampling period is set to the value indicated in the Status Inspection field.
At the expiry of the accumulation period, all samples are averaged with an accuracy of 0.1 (i.e. summed,
multiplied by 10 and divided by the number of samples). The averaged value is rounded up or down to the nearest
value.
Note : The reported value shall then be divided by 10 so that the value that is taken into acount (interger and
decimal parts) is the correct one.
External comment:
--
Counter Name : MAX_PARALLEL_TCH_VGCS Counter Integer
B10 Common cell 2
B9 Common cell 2
Sub domain-2: TCH
Counter definition:
Maximum number of parallel TCH in use for VGCS per cell during observation period.
TCH used for VGC listening service and TCH used for VGC talking service are both counted.
Trigger condition:
Whenever a TCH radio timeslot is allocated for VGCS, the BSC determines the current number of busy TCH radio
timeslots allocated to VGCS. This counter is the maximum value of this number during the accumulation period.
Note: both talker TCH and listener TCH are counted.
External comment:
--
Alcatel-Lucent
Counter Name : NB_VGCS_ESTABLISHMENT_REQ Counter Integer
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
Number of VGC establishment requests per cell during observation period.
Trigger condition:
This counter is incremented each time the BSS receives a 48.008 VGCS/VBS ASSIGNMENT REQUEST from the
MSC.
External comment:
--
Counter Name : NB_VGCS_ESTABLISHMENT_SUCC Counter Integer
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
Number of successfully established VGC per cell during observation period.
Trigger condition:
This counter is incremented each time the BSS sends the first 48.008 VGCS/VBS ASSIGNMENT RESULT to the
MSC corresponding to a VGCS/VBS ASSIGNMENT REQUEST.
External comment:
--
Alcatel-Lucent
Counter Name : NB_CM_SERV_REQ_VGCS Counter Integer
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
Number of received CM_SERVICE-REQ for VGC per cell during observation period.
Trigger condition:
This counter is incremented each time the BSS receives a CM SERVICE REQUEST message with parameter
CM Service Type set to "Voice group call establishment (1001)".
External comment:
--
Counter Name : NB_VGC_RELEASED_VGCS Counter Integer
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
Number of released VGC per cell during observation period.
Trigger condition:
This counter is incremented each time a 48.008 CLEAR COMMAND is received from the MSC on the VGCS
resource controlling SCCP connection, i. e. on the SCCP connection initiated with VGCS/VBS ASSIGNMENT
REQUEST.
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_VGCS_HO_ATPT Counter Integer
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
Number of outgoing handover attempts for VGC-talker per cell during observation period.
Intracell, internal intercell and external handovers are counted together.
Trigger condition:
Internal intercell HO, external HO :
This counter is incremented each time the 44.018 HANDOVER COMMAND message is sent to the MS on the
serving channel, during a TCH handover procedure for a VGCS talker.

Intracell HO :
This counter is incremented each time a 44.018 ASSIGNMENT COMMAND message is sent to the MS for a TCH
handover procedure for a VGCS talker.
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_VGCS_HO_SUCC Counter Integer
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
Number of successful outgoing handover for VGC-talker per cell during observation period.
Trigger condition:
This counter is incremented in following cases :
1) External HO: whenever 48.008 CLEAR COMMAND (cause="handover successful") is received on the serving
BSC on the channel of the CGCS talker ;
2) Internal inter-cell HO: whenever 44.018 HANDOVER COMPLETE is received from the MS via the target cell on
the channel of the VGCS talker ;
channel of the VGCS talker.
External comment:
--
Counter Name : NB_INC_VGCS_HO_SUCC Counter Integer
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
Number of successful incoming handover for VGC-talker per cell during observation period.
Intracell handover are not counted.
Trigger condition:
This counter is incremented for internal inter-cell or external handover, i. e. : whenever a 44.018 HANDOVER
COMPLETE message is received from the MS in the target cell for the channel of the VGCS talker.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_VGCS_HO_ATPT Counter Integer
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
Number of incoming handover attempts for VGC-talker per cell during observation period.
Intracell handover are not counted.
Trigger condition:
External handover :
COMMAND towards the target cell on TCH, for a VGC-talker.

Internal intercell handover :
Whenever a 44.018HANDOVER COMMAND is sent to the serving BTS for internal inter cell TCH handover, for a
VGC talker. However, the counter is incremented in the TARGET cell, based on the target cell ID indicated by the
HO Command message.
External comment:
--
Counter Name : NB_TALKER_CHANGE_VGCS Counter Integer
B10 BSC 2
B9 BSC 2
Sub domain-2:
Counter definition:
Number of talker change in the BSC during observation period.
This counter is the TOTAL number of talker change in the BSC during the observation period.
Trigger condition:
This counter is increment each time the BSC sends a 48.008 UPLINK REQUEST CONFIRMATION message to
the MSC.
External comment:
--
Alcatel-Lucent
Counter Name : NB_VGC_BLOCKED_VGCS Counter Integer
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
Number of blocked VGC due to lack of resources per cell during observation period.
Trigger condition:
This counter is incremented when the BSC cannot allocate the VGCH, i. e. sends to the MSC:
- The 48.008 VGCS/VBS ASSIGNMENT FAILURE message
with cause parameter set to "Resource unavailable (010)"
whenever
1/ no TCH is available and either:
- queuing was not requested by the MSC (parameter
"priority.qa" set to "queuing not allowed 0") in case of
immediate allocation (parameter "assignment requirement"
set to "immediate and the resources shall not be
de-allocated until the end of the call (channel
establishment on demand forbidden by the MSC)
00000001" or "immediate and the resources may further
be de-allocated by the BSS (channel establishment on
demand forbidden by the MSC) 00000010" ;
- queuing was requested by the MSC (parameter
"priority.qa" set to "queuing allowed 1") but disabled in
the BSC ;
- queuing was requested by the MSC but the queue is full
and no request of lower priority can be dequeued ;
- the request is dequeued due to the reception of higher
priority request ;
- the request is dequeued due to T14 timer expiry ;
2/ the maximum number of TCH allowed for VGCs
has been reached ;
- the 48.008 CLEAR REQUEST message with cause
parameter set to "resource unavailable 010" in case of
delayed allocation for a VGCH (i. e. sent over an SCCP
connection previously established with a 48.008
VGCS/VBS ASSIGNMENT REQUEST message with
parameter "assignment requirement" set to "delay allowed
00000000" and parameter "priority.qa" set to "queuing not
allowed 0", whenever no more TCH is available or the
maximum number of TCH allowed for VGCs has been
reached.
External comment:
--
Alcatel-Lucent
Counter Name : NB_VGCS_NOTIFIFICATION_FACCH Counter Integer
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
Number of VGC notifications sent over FACCH per cell during observation period.
Trigger condition:
This counter is incremented each time the BSC sends a 48.058 UNIT DATA REQUEST (NOTIFICATION/FACCH)
message to the BTS with the indication "Group Call Information".
Note : this counter does not include paging requests.
External comment:
--
Counter Name : NB_ASS_REQ_ABLE_PREEMT Counter Integer
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
Number of ASSIGNEMENT REQUEST able to pre-empt per cell during observation period.
Trigger condition:
This counter is incremented each time the BSC receives a 48.008 ASSIGNEMENT REQUEST message with
"Preemption Capability indicator (pci)" of "Priority" parameter set to "this allocation request may preempt an
existing connection (1)".
Notes :
1) This counter is not limited to VGC, so it also counts messages related to point-to-point calls.
2) Repetitions of the ASSIGNMENT REQUEST message in case of channel modification are not counted.
External comment:
--
Alcatel-Lucent
Counter Name : NB_VGCS_ASS_REQ_ABLE_TO_PREEMPT Counter Integer
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
Number of VGCS/VBS ASSIGNEMENT REQUEST able to pre-empt per cell during observation period.
Trigger condition:
This counter is incremented each time the BSC receives from the MSC a VGCS/VBS ASSIGNEMENT REQUEST
message with "Preemption Capability indicator (pci)" of "Priority" parameter set to "this allocation request may
preempt an existing connection (1)".
External comment:
--
Counter Name : NB_VGCS_QUEUED Counter Integer
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
Number of VGC queued per cell during the polling period.
Trigger condition:
This counter is incremented each time a VGCS/VBS QUEUING INDICATION message is sent to the MSC.
External comment:
--
Alcatel-Lucent
Counter Name : NB_VGCS_ESTABLISHED Counter Integer
B10 BSC 2
B9 BSC 2
Sub domain-2:
Counter definition:
Number of VGC successfully established per BSC during the observation period.
Trigger condition:
This counter is incremented each time the BSC sens a 48.008 VGCS/VBS SETUP ACKNOWLEDGE message
to the MSC.
External comment:
--
Counter Name : NB_PREEMTED_TCH_VGCS Counter Integer
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
Number of pre-empted TCHper cell during observation period.
Trigger condition:
This counter is incremented each time a 48.008 CLEAR REQUEST or a 48.008 UPLINK RELEASE INDICATION
with parameter "Cause" set to "pre-emption (0101001)" is sent to the MSC.
Note 1: Any pre-empted TCH is counted (i. e. point-to-point
call TCH, VGC talker TCH, VGC listener TCH).
Note 2: Whatever the TCH is pre-emted for (point-to-point
call TCH, VGC talker TCH, VGC listener TCH),
the counter is incremented.
External comment:
--
Alcatel-Lucent
Counter Name : NB_PAGING_FACCH Counter Integer
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
Number of PTP pagings sent over FACCH per cell during observation period.
Trigger condition:
This counter is incremented each time the BSC sends a 48.058 UNIT DATA REQUEST (NOTIFICATION/FACCH)
message to the BTS with the indication "Paging Information".
Note : this counter does not include notification of VGCS.
External comment:
--
Counter Name : VGCS20 Counter Integer
B10 Common cell 2
B9 Common cell 2
Technology: GSM Sub domain-1: BSC
Sub domain-2:
Domain: Sub domain-3:
Counter definition:
Provision for VGCS
Trigger condition:
--
External comment:
--
Alcatel-Lucent
Type name: Overview measurements
Type definition:
Set of global counters providing an overview of each measurement type
MC01 Type 110 : Overview measurements
Counter Name : NB_IMM_ASS_SUCC_MT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of immediate assignment plus SDCCH normal assignment successes for Mobile Terminating procedure.
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION message is received from a CELL, with the L3_INFORMATION
field including a 44.018 PAGING RESPONSE message.
External comment:
--
Alcatel-Lucent
Counter Name : NB_IMM_ASS_SUCC_MO Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of immediate assignment successes for Mobile Originating procedure.

MC02 = C02 = C02a+C02b+C02c+C02d+C02e+C02f+C02g+C02h+C02i.
The following counters C02a/b/c/d/e/f/g/h/i provide the distribution of the MO telecom procedures on SDCCH.
Trigger condition:
External comment:
--
MC02a Type 110 : Overview measurements
Counter Name : NB_IMM_ASS_SUCC_MO_LOC_UPD Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
case: Location Update request (except the "follow on" procedure)
Trigger condition:
an
MIE Location updating type not set to a RESERVED value and a bit FOR set to 0.
External comment:
--
Alcatel-Lucent
MC02b Type 110 : Overview measurements
Counter Name : NB_IMM_ASS_SUCC_MO_SMS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
case: SMS procedure on SDCCH
Trigger condition:
field
CM service type set to "SMS".
External comment:
--
MC02c Type 110 : Overview measurements
Counter Name : NB_IMM_ASS_SUCC_MO_SUP_SERV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
case: Supplementary Service
Trigger condition:
field
CM service type set to "Supplementary Service".
External comment:
--
Alcatel-Lucent
MC02d Type 110 : Overview measurements
Counter Name : NB_IMM_ASS_SUCC_MO_FOLLOW_ON Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
case: Location Update request ("follow on" procedure)
Trigger condition:
field
an MIE Location updating type not set to a RESERVED value and a bit FOR set to 1.
External comment:
--
MC02e Type 110 : Overview measurements
Counter Name : NB_IMM_ASS_SUCC_MO_CM_REEST Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
case: CM Re-establishment procedure
Trigger condition:
field
containing a 44.018 L3 message with an MIE message type set to CM RE-ESTABLISHMENT REQUEST
message.
External comment:
--
Alcatel-Lucent
MC02f Type 110 : Overview measurements
Counter Name : NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC02f=C02f, number of immediate assignment successes for Mobile Originationg procedure, in case of L3 Info
(within 48.058 ESTABLISH INDICATION) unknown by the BSC but transferred to the MSC.
Trigger condition:
External comment:
--
MC02g Type 110 : Overview measurements
Counter Name : NB_IMM_ASS_SUCC_MO_IMSI_DETACH Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC02g=C02g, number of immediate assignment successes for Mobile Originationg procedure, in case of IMSI
Detach Indication.
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION message is received from a CELL, with L3_INFORMATION field
containing a 44.018 L3 message with an MIE message type set to IMSI DETACH INDICATION. This counter is
incremented only if the L3 info message received has to be forwarded to the MSC.
External comment:
--
Alcatel-Lucent
MC02h Type 110 : Overview measurements
Counter Name : NB_IMM_ASS_SUCC_MO_CALL_EST Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
case: normal or emergency call establishment
Trigger condition:
field
containg a 44.018 L3 message with an MIE message type set to CM SERVICE REQUEST and an MIE CM
service type set to either :
- "emergency call establishment",
- or "mobile originating call establishment"
External comment:
--
MC02i Type 110 : Overview measurements
Counter Name : NB_IMM_ASS_SUCC_MO_LCS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
case: Mobile originated LCS procedure on SDCCH
Trigger condition:
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
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_SDCCH_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter definition:
MC03=C03, Number of outgoing SDCCH handover (any kind) successes.
Trigger condition:
1/ 48.008 CLEAR COMMAND (cause= "handover successful") is received on the serving BSC.

External comment:
--
Counter Name : NB_IMM_ASS_PREP_FAIL_CONG Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC04=C04, number of immediate assignment preparation failures due to congestion.
Trigger condition:
All SDCCH sub-channels in the required cell were either Busy or Out of Service, when the 48.058 CHANNEL
REQUIRED message was received.
External comment:
--
Alcatel-Lucent
Counter Name : NB_SDCCH_DROP_OUT_HO Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter 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.
External comment:
--
Counter Name : NB_INC_SDCCH_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter definition:
MC10=C10, Number of incoming SDCCH handover (any kind) successes.
Trigger condition:
Internal inter-cell or external SDCCH handover: whenever a 44.018 HANDOVER COMPLETE message is
received
on Abis interface from the target cell for an SDCCH Sub-channel.

External comment:
--
Alcatel-Lucent
Counter Name : NB_INTRA_SDCCH_HO_PREP_FAIL_CONG Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter definition:
MC101=C101, Number of intra-cell SDCCH handover -preparation failures due to congestion.
Trigger condition:
Whenever a internal intra-cell SDCCH handover cannot be performed, because there is no free SDCCH
External comment:
--
Counter Name : NB_HO_ATPT_23_TrafHandover Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC1040=C440+C445
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_HO_ATPT_24_gencapture Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC1044=C444+C446
Trigger condition:
External comment:
--
Counter Name : NB_HO_22_TooShortDistance Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC1050=C450+C454
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_SDCCH_DROP_EST_PHAS_BSS_PB Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter definition:
MC137=C137, Number of SDCCH drops in SDCCH established phase due to BSS problem.It may happen that
several causes of failures mentioned below are detected consecutively. In that case, the counter will only be
incremented once, as soon as the call is released.
Trigger condition:
1) LapD failure detected during the stable phase of an SDCCH transaction.
2) SDCCH was released due to 48.058 ERROR REPORT with any cause value being received during the stable
phase of an SDCCH transaction.
3) Telecom Supervisory module caused the call to be cleared.
4) SDCCH was released due to 0180 CLEAR_CMD message being received from BSSAPduring the stable phase
of an SDCCH transaction : O&M has disabled the DTC
External comment:
--
Alcatel-Lucent
Counter Name : NB_SDCCH_DROP_EST_PHAS_RLF Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter definition:
Number of SDCCH drops on SDCCH established phase due to radio link failure (radio link timeout or Lapdm timer
expiry).
Trigger condition:
received on Abis interface for an SDCCH channel.
2) Whenever an 48.058 ERROR INDICATION message is received on Abis interface and leads to a loss of
channel.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_QUEUED Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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:
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

Note 1: MC13a = C13a
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_TCH_HO_QUEUED Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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:
ii) when the handover request is queued in the cell if the queuing is not authorised by the MSC and the request

Note: MC13b = C13b

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_REQ Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
1) Number of normal assignment requests for TCH establishment (in HR or FR usage).
2) Number of BSCGP DTM assignment command received from MFS, for MS camping on a SDCCH (i.e. the
cases where a TCH was already allocated to the MS are not taken into account). In this case, the TCH is
established in signaling mode
Trigger condition:
1) Whenever a 48.008 ASSIGNMENT REQUEST message for a normal TCH assignment is received from the
MSC.
2) Whenever a BSCGP DTM ASSIGNMENT COMMAND message is received from MFS for a MS camping on a
SDCCH
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_ATPT Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of normal assignment attempts for TCH establishment (in HR or FR usage). This counter also takes into
account DTM assignment commands for TCH establishment in signaling mode (FR usage only).
Trigger condition:
1) Whenever a 44.018 ASSIGNMENT COMMAND message for a normal TCH assignment is sent to the MS. In
case of multiband cell, only the first 44.018 ASSIGNMENT COMMAND message is counted (when sent in the
inner zone); the second 44.018 ASSIGNMENT COMMAND message sent in the outer zone (further to the
ASSIGNEMENT FAILURE received with the cause protocol error unspecified in the inner zone) is not counted.

2) Whenever a 44.018 DTM ASSIGNMENT COMMAND message is sent to the MS, containing the assignment of
a TCH in signaling mode.
External comment:
--
Alcatel-Lucent
Counter Name : AV_NB_TCH_QUEUED Counter Round (10
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
Average number of queued TCH (in HR or FR usage) normal assignment or external handover requests.
Trigger condition:
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.
External comment:
--
Counter Name : NB_OUT_IDR_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC142e=C142a+C142c
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_EDR_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC142f=C142b+C142d
Trigger condition:
External comment:
--
Counter Name : NB_OUT_IDR_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC144e=C144a+C144c
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_EDR_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Domain: Traffic Load Sub domain-3: External
Counter definition:
MC144f=C144b+C144d
Trigger condition:
External comment:
--
Counter Name : NB_INC_SDCCH_HO_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Domain: Traffic Load Sub domain-3: SDCCH
Counter definition:
MC147=C147, Number of incoming internal or external SDCCH handovers -whose target SDCCH channel is
allocated by the BSC.
Trigger condition:
SDCCH
channel for any handover purposes.

External comment:
--
Alcatel-Lucent
Counter Name : NB_IMM_ASS_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of immediate assignment plus SDCCH normal assignments -whose SDCCH channel is allocated by the
BSC.
Trigger condition:
SDCCH
channel for any purpose other than handover.
External comment:
--
Counter Name : NB_IMM_ASS_EXEC_FAIL_RADIO Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of immediate assignment -execution failures due to MS access problem.
Trigger condition:
Whenever the timer supervising the Immediate Assignment Procedure (T3101) expires during the establishment
of
an SDCCH sub-channel.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter 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.
counter will only be incremented once, as soon as the handover procedure fails.
Trigger condition:
1) Whenever the BSC receives on Abis interface from the target cell negative acknowledgment to the TCH
channel
activation involved in the handover procedure.
2) Whenever the timer supervising the Channel Activation procedure (T9103) expires on the target cell during
activation of a TCH channel involved in the handover procedure.
interface from either the serving or the target cell during the external or internal inter-cell handover procedure and
leads to a transaction failure.
interface on either the old or the new channel during the internal intra-cell handover procedure and leads to a
transaction failure.
is
received on Abis interface from the serving cell between the sending of the 48.058 CHANNEL ACTIVATION
message and the reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGMENT during the internal
inter-cell TCH handover and leads to a transaction failure.
is
received on Abis interface on the old channel between the sending of the 48.058 CHANNEL ACTIVATION
message and the reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGE during the internal intra-cell
TCH handover and leads to a transaction failure.
7) Whenever a LAPD failure related to either serving or target cell is reported to the Layer 3 of the BSC (for an
RSL supporting a TCH transaction for handover purpose) and leads to a transaction failure.
8) Whenever an TCH handover abortion is 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).
9) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "remote transcoder
failure" is received on Abis interface from the old channel between the sending of the 48.058 CHANNEL
ACTIVATION message and the reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGE during an
internal intra-cell or inter-cellTCH handover procedure and leads to a transaction failure.

Notes :
1. TCH handover failures which are due to O&M operator actions on BTS or BSC should not be counted. Indeed,
in case of numerous failures due to O&M commands, this counter will overestimate failures which are due to
Alcatel-Lucent

unit:
mechanism: unit:
External comment:
--
Counter Name : NB_TCH_DROP_EST_PHAS_BSS_PB Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
problems which are internal to the BSS. Counter definition:
Number of TCH (in HR or FR usage) drops in TCH established phase due to BSS problem.
operator actions will also be counted. It may happen that several causes of failures mentioned below are
detected consecutively. In that case, the
2. It may happen that the counter can not be incremented since it is implemented within the faulty entity. counter
This counter takes into account TCH in traffic or in signaling mode. It is not incremented in case of TCH drop
during a normal assignment, a handover or a DTM assignment.
Trigger condition:
1) Whenever a 48.058 ERROR REPORT message with a cause value of "O&M intervention" is received on Abis
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.

Notes :
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_IDR_SUCC (29) Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.
External comment:
--
Counter Name : NB_INC_IDR_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC153=C153, Number of incoming internal directed retry (forced or normal) requests. The target TCH channel
can
be in HR or FR usage.
Trigger condition:
Whenever the BSC process responsible for handover procedure selects the target cell for forced or normal
internal
directed retry.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_IDR_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC15a=C15a, Number of incoming internal directed retry (towards a TCH channel in HR or FR usage) whose
target channel is allocated by the BSC.
Trigger condition:
channel is about to be sent during an internal directed retry.
External comment:
--
Counter Name : NB_INC_TCH_HO_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming TCH (in HR or FR usage) handover (internal or external) -whose target channel is allocated
by
the BSC.
Trigger condition:
channel is about to be sent during any handover procedure.

External comment:
--
Alcatel-Lucent
Counter Name : NB_DTAP_NOR_ASS_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC161 = C161a + C161b
Trigger condition:
Whenever a 44.018 CONNECT ACK is received on Abis interface.
External comment:
--
Counter Name : NB_TCH_DROP_DTAP_EST_PHAS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
MC162 = C162a + C162b + C162c
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_CALL_TFO Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TFO
Counter definition:
Number of TCHs assigned in the serving cell for which TFO has been successfully established.
Trigger condition:
the BSC, indicating that TFO is established (i.e. TFO = 1 in the TFO Status IE).

assigned TCH).


Note 3: MC170 = C170
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_HO_PREP_FAIL_ACHAN_MIS (110) Counter Integer
B10 BSC 1
B8 BSC 0
B9 BSC 1
Counter definition:
Number of TCH (in HR or FR usage) normal assignment and external handover -preparation failures due to
A-channel status mismatch between the BSC and the MSC.
Trigger condition:
1) Whenever an 48.008 ASSIGNMENT REQUEST message selects a TTCH which is found to be unavailable by
the BSS (Blocked or Busy).
2) Whenever a 48.008 HANDOVER REQUEST message selects a TTCH which is found to be unavailable by the
BSS (Blocked or Busy).

External comment:
--
Counter Name : NB_SMS_PP_CON_MT_SDCCH Counter Integer
B10 Common cell 1
Counter definition:
Number of Mobile Terminating SMS connections on SDCCH.
Trigger condition:
Whenever an ESTABLISH CONFIRM (SAPI = 3) message related to an SDCCH sub-channel is received by the
BSC.
External comment:
--
Alcatel-Lucent
Counter Name : NB_SMS_PP_CON_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC196=C190+C191+C192+C193
Trigger condition:
External comment:
--
Counter Name : NB_SMS_PP_CON_FAIL Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC197=C194a+C194b+C194c+C195
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : AV_NB_NOT_AVAIL_TRX_TS Counter Round (x)
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Average number of not available radio timeslots (TRX_TS).
Trigger condition:
External comment:
--
Counter Name : AV_NB_AVAIL_TCH Counter Round (x)
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
Average number of available TCH/PDCH timeslots for traffic usage (i.e. TCH (for HR or FR usage) or PDCH).
Trigger condition:
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.
External comment:
--
Alcatel-Lucent
Counter Name : AV_NB_AVAIL_SDCCH Counter Round (x)
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter definition:
Average number of available static SDCCH sub-channels (i.e. on static SDCCH timeslots).
Trigger condition:

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".
External comment:
--
Counter Name : AV_NB_AVAIL_CCCH Counter Round (x)
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: CCCH
Counter definition:
Average number of available CCCH channels.
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : AV_NB_BUSY_CS_TS Counter Round (10
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_MAX_SIMUL_BUSY_CS_TS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
Maximum number of simultaneously busy TCH radio timeslots (in HR or FR usage, in traffic or in signaling mode)
and simultaneously busy dynamic SDCCH/8 radio timeslots allocated as TCH.
Trigger condition:
Whenever a TCH radio timeslot or a dynamic SDCCH/8 radio timeslot allocated as TCH becomes busy, the BSC
determines the current number of busy TCH radio timeslots (in HR or FR usage) and busy dynamic SDCCH/8
radio timeslots allocated as TCH. This counter is the maximum value of this number during the accumulation
period.

This counter does not take into account the PDCHs allocated to the MFS.
External comment:
--
Counter Name : NB_MAX_SIMUL_BUSY_SDCCH Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter definition:
Maximum number of simultaneously busy SDCCH subchannels, taking into account the following SDCCH
sub-channels: 1) Static SDCCH/x sub-channels, 2) Dynamic SDCCH sub-channels which are dynamically
allocated on the dynamic SDCCH/8 timeslots.
Trigger condition:
At each 48.058 CHANNEL ACTIVATION (SDCCH subchannel) sent to the cell:
C31 = MAX ["old" C31 value (i.e. before the channel activation), number of busy SDCCH subchannels observed
for
the cell].
External comment:
--
Alcatel-Lucent
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
This
Trigger condition:
External comment:
--
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
This
Trigger condition:
nearest
integer value.
External comment:
--
Alcatel-Lucent
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
This
Trigger condition:
External comment:
--
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter 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:
External comment:
--
Alcatel-Lucent
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter definition:
This
Trigger condition:
nearest
integer value.
External comment:
--
Counter Name : TIME_ALL_AVAIL_TRX_TS_BUSY Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : AV_NB_A_TRAF_CHAN_BLOCK_OUT_OF_SERV Counter Round (x)
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A channel
Counter 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).
External comment:
--
Counter Name : NB_N7_CON_REQ Counter Integer
Sub domain-2: A
Counter definition:
MC350=C253+C254
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_N7_CON_CONF Counter Integer
Sub domain-2: A
Counter definition:
MC351=C255+C256
Trigger condition:
External comment:
--
Counter Name : AV_NB_AVAIL_A_TRAF_CHAN Counter Round (x)
B10 BSC 1
B8 BSC 0
B9 BSC 1
Sub domain-2: A channel
Counter definition:
Average number of available A-traffic-channels channels (i.e. all A-channels except for N7, SPC and synchro).
Trigger condition:
Every 20 seconds, the TTCHs that satisfay one of the following conditions are counted :
Maintenance state is either IN TRAFFIC or FAULTY IN TRAFFIC or WAIT TRAFFIC CLEAR and Telephonic state
is available free or available busy.

Note:
This counter is not incremented if the channel is in the Maintenance state NOT EQUIPPED, or if the channel is in
use for signalling (N7), for a semi-permanent connection (SPC), or for synchronisation (channel 0).
External comment:
--
Alcatel-Lucent
Counter Name : NB_TRX_FR_ALLOC Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
MC370A= SUM(all TRX_TS of the TRX) (C370A)
Trigger condition:
External comment:
--
Counter Name : NB_TRX_HR_ALLOC Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
MC370B= SUM(all TRX_TS of the TRX) (C370B)
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : TIME_TRX_FR_BUSY Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
Time (in seconds) during which the TCH radio timeslot in FR usage is busy
Trigger condition:
MC380A= SUM (all TRX_TS of the TRX) (C380A)
External comment:
--
Counter Name : TIME_TRX_HR_BUSY Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
Time (in seconds) during which the TCH radio timeslot in HR usage is busy
Trigger condition:
MC380B= SUM (all TRX_TS of the TRX) (C380B)
External comment:
--
Alcatel-Lucent
Counter Name : TIME_TRX_GSM_FR_BUSY Counter Integer
Improvements")
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter 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:
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.
External comment:
--
Alcatel-Lucent
Counter Name : TIME_TRX_GSM_HR_BUSY Counter Integer
Improvements")
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : TIME_TRX_DCS_FR_BUSY Counter Integer
Improvements")
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter 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:
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
the 48.058 RF CHANNEL RELEASE message) concerning the TCH channel previously activated on the related
TRX timeslot.
External comment:
--
Alcatel-Lucent
Counter Name : TIME_TRX_DCS_HR_BUSY Counter Integer
Improvements")
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter 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
the 48.058 RF CHANNEL RELEASE message) concerning the TCH channel previously activated on the related
TRX timeslot.
External comment:
--
Counter Name : TIME_TRX_TCH_BUSY_BY_MULTIBAND_MS Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
MC381= SUM (over all TRX_TS of the TRX) (C381A+C381B)
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_TIMES_SDCCH_BUSY (110) Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: SDCCH
Counter definition:
MC390=SUM (all TRX_TS of the TRX) C39, C39 is NB_TIMES_SDCCH_BUSY in type 4.
Trigger condition:
External comment:
--
Counter Name : TIME_TRX_SDCCH_BUSY Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: SDCCH
Counter definition:
MC400= SUM (all TRX_TS of the TRX) C40
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming external TCH (in HR or FR usage) handover -preparation failures due to A-traffic-channel
status mismatch between the BSC and the MSC.
Trigger condition:
1) Whenever a 48.008 HANDOVER FAILURE message with a cause value of "requested terrestrial resource
unavailable" is sent on A interface from the target BSC to the MSC.
2) Whenever a 48.008 HANDOVER FAILURE message with a cause value of "terrestrial circuit already allocated"
is sent on A interface from the target BSC to the MSC.
3) Whenever a 48.008 HANDOVER FAILURE message with a cause value of "BSS not equipped" is sent on A

External comment:
--
Counter Name : NB_TCH_HO_ATPT_26_BadQualHR Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ATPT_27_GoodQualFR Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:
External comment:
--
Counter Name : NB_TCH_HO_ATPT_28_FastTraffic Counter Integer
SFD reference : 3BK 10204 0475 DTZZA ("Instantaneous Peaks Management") Length: 4
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_EMERGENCY_HO_PRESERVATION Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Domain: Handover Sub domain-3: Success
Counter definition:
Number of high priority TCH requests served when
1) the number of free TCH timeslots is less than or equal to NUM_TCH_EGNCY_HO and,
2) the queue for this cell is not empty.
Trigger condition:
The counter is incremented on the serving cell whenever the 48.058 CHANNEL ACTIVATION message allocating
a TCH channel is sent and the following two conditions are both fulfilled:

1) the TCH is allocated to serve i) an internal handover Cause 2, 3, 4, 5, 6, 7, 10, 11, 12, 15, 16, 17, 18, 22, 27,
or, ii) an external handover Cause "Uplink quality", "Uplink strength", "Downlink quality", "Downlink strength",
"Distance", or iii) a normal assignment or an external handover with the preemption indicator set (i.e. Preemption
Capability Indicator = 1 and EN_TCH_PREEMPT = Enable).

2) the number of free TCH timeslots is less than or equal to NUM_TCH_EGNCY_HO and there is at least one
request queued for this cell.


Note 2: The HMI name of the parameter NUM_TCH_EGNCY_HO is "NUM_TCH_EMERGENCY_HO".
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ATPT_29_TFO Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
Number of intra-cell handover - attempts, with the cause 29 (TFO mismatch resolution, TFO optimisation).
MC461 = C461
Trigger condition:
External comment:
--
Counter Name : NB_OUT_INTER_PLMN_TCH_HO_REQ Counter Integer
SFD reference : 3BK 10204 0600 DTZZA ("Outgoing inter-PLMN handovers") Length: 2
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of inter-PLMN TCH outgoing handover or directed retry requests. This counter takes into account TCH in
Trigger condition:
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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_INTER_PLMN_TCH_HO_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of inter-PLMN TCH outgoing handover or directed retry attempts. This counter takes into account TCH in
Trigger condition:
Whenever a 44.018 HANDOVER COMMAND message is sent to the MS on Abis interface for an external TCH
handover or an external directed retry triggered towards a 2G cell belonging to a PLMN different from the PLMN
of
the serving cell.
External comment:
--
Counter Name : NB_OUT_INTER_PLMN_TCH_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of inter-PLMN TCH outgoing handover or directed retry successes. This counter takes into account TCH
in traffic or in signaling mode.
Trigger condition:
External handover or directed retry towards a 2G cell belonging to a PLMN different from the PLMN of the serving
cell in the following cases:
1/ 48.008 CLEAR COMMAND message with Cause "Handover successful" is received from the MSC.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_INTER_PLMN_TCH_HO_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of inter-PLMN TCH incoming handover or directed retry requests
Trigger condition:
Whenever a 48.008 HANDOVER REQUEST message is received from the MSC on A interface for an external
TCH handover or an external directed retry triggered towards the target cell from a serving cell belonging to a
PLMN different from the PLMN of the target cell.
External comment:
--
Counter Name : NB_INC_INTER_PLMN_TCH_HO_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of inter-PLMN TCH incoming handover or directed retry attempts
Trigger condition:
Whenever a 48.008 HANDOVER REQUEST ACK message is sent by the target BSC containing the 44.018
HANDOVER COMMAND message for an external TCH handover or an external directed retry triggered towards
the target cell from a serving cell belonging to a PLMN different from the PLMN of the target cell.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_INTER_PLMN_TCH_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of inter-PLMN TCH incoming handover or directed retry successes
Trigger condition:
Whenever a 44.018 HANDOVER COMPLETE message is received from the MS on Abis interface for an external
TCH handover or an external directed retry triggered towards the target cell from a serving cell belonging to a
PLMN different from the PLMN of the target cell.
External comment:
--
Counter Name : NB_TCH_HO_REQ_30_ReturnCSZone Counter Integer
SFD reference : 3BK 10204 0609 DTZZA ("Autonomous Packet Resource Length: 2
Allocation (RAE-4)")
B10 Common cell 1
B9 Common cell 1
Sub domain-2:
Counter definition:
Number of TCH intracell HO cause 30 requests
Trigger condition:
Whenever the BSC detects that a TCH needs to be moved from PS zone to CS zone, I.e. whenever at
MAX_SPDCH_LIMIT calculation time, the BSC detects that 1 TCH is allocated in both MAX_SPDCH_LIMIT zone
and the non pre-emptable PS zone and EN_RETURN_CS_ZONE_HO = Enabled.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ATPT_30_ReturnCSZone Counter Integer
B10 Common cell 1
B9 Common cell 1
Sub domain-2:
Counter definition:
Number of TCH intracell HO cause 30 attempts.
Trigger condition:
Whenever a 44.018 Assignment Command is sent to the MS for a TCH HO cause 30.
External comment:
--
Counter Name : NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming external TCH (in HR or FR usage) handover -preparation failures due to congestion (C541a),
or A-traffic-channel status mismatch between the BSC and the MSC (C41b).
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming external TCH (in HR or FR usage) handover -preparation failures due to congestion.
Trigger condition:
on
A interface from the target BSC to the MSC during an external TCH handover.


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.

parameter
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming internal inter-cell TCH (in HR or FR usage) handover -preparation failures due to congestion.
Trigger condition:
Whenever an internal inter-cell TCH handover cannot be performed, because the target cell is congested (no free
TCH channel).

Note 1: In MX BSC, this counter is incremented whenever an internal inter-cell TCH handover cannot be
performed
due to the TCH processing capacity of CCP reaches the limit defined by the MAX_TCH_PER_CCP parameter. In
this case, MC926 is also incremented by one.

parameter
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_IDR_PREP_FAIL_CONG_R_ABIS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of incoming internal directed retry (forced or normal) -preparation failures due to congestion (on Air or
A-bis interface). The target TCH channel can be in HR or FR usage.
Trigger condition:
1) Whenever there are no free TCH in the target cell during a forced or normal internal directed retry.
2) Whenever no TCH resource is available on A-bis interface for a forced or normal internal directed retry. (not
valid
in B7).

Note 1: In MX BSC, this counter is incremented whenever a TCH cannot be not allocated due to the TCH
processing capacity of CCP reaches the limit defined by the MAX_TCH_PER_CCP parameter. In this case,
MC926 is also incremented by one.

parameter
External comment:
--
Alcatel-Lucent
Counter Name : NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter definition:
Number of intra-cell TCH (in HR or FR usage) handover -preparation failures due to congestion. This counter
takes
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.

parameter
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ATPT_10_TooLowLevUpInZone Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:
External comment:
--
Counter Name : NB_TCH_HO_ATPT_11_TooLowLevDownInZone Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter 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:
External comment:
--
Counter Name : NB_SDCCH_HO_20_HighLevNeigCellForcDR Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC607=C607, Number of SDCCH inter-cell internal or external handover attempts with cause 20: "forced directed
retry". This counter is related to a forced directed retry (internal or external).
Trigger condition:
Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTS because of cause 20.

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH (in HR or FR usage) normal assignment preparation failures because of the non-queuing of the
ASSIGNMENT REQUEST message.
Case: 48.008ASSIGNMENT REQUEST on TCH (in HR or FR usage) is received when no TCH is available in the
cell. The request is rejected (by 48.008ASSIGNMENT FAILURE, cause: "no radio resource available"), because
the queuing procedure is either:
1) disabled within the BSC (i.e. (T11=0 and QUEUE_ANYWAY=0), OR (T11_forced=0 and
QUEUE_ANYWAY=1)), or
2) enabled within the BSC, i.e. T11 <> 0, but not requested by the MSC when QUEUE_ANYWAY=0.
Trigger condition:
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.


by one.

parameter
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC612b=C612b, Case: 48.008ASSIGNMENT REQUEST on TCH (in FR or HR usage) is received when no TCH
is
available in the cell. The queuing is enabled within the BSC, but the request is rejected (by 48.008ASSIGNMENT
FAILURE, cause: "no radio resource available"), because the queue is full and no request of lower priority can be
dequeued from the BSC queue.
Trigger condition:
available") for a TCH channel because the queue is full and no request of lower priority can be de-queued.

by one.

parameter
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2:
Counter definition:
QUEUE_ANYWAY=1, i.e. the queuing is forced within the BSC) is started, and no free TCH can be found before
timer expiry, consequently the request is rejected (by 48.008 CLEAR REQUEST cause: "no radio resource
available").
Remark: If an internal directed retry is attempted and failed while T11/T11_forced is running, the request is
un-holded and the BSC waits for the expiry of the relevant timer. Consequently, this counter must not be
incremented upon the failure of an internal directed retry.
Trigger condition:
The counter is incremented upon the sending of 48.008 CLEAR REQUEST (cause : "no radio resource available")
-following the expiry of T11 or T11 forced for a queued TCH normal assignment.


by one.

parameter
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
QUEUE_ANYWAY=1, i.e. the queuing is forced within the BSC) is started, and before the timer expiry, the
request is dequeued due to the receipt of a higher priority request (i.e. 48.008ASSIGNMENT REQUEST) : the
BSC sends 48.008ASSIGNMENT FAILURE (cause: "no radio resource available") for the first transaction.
Remark: As soon as an internal directed retry is attempted, the request is blocked within the BSC and cannot be
dequeued by a higher priority request.
Trigger condition:
The counter is incremented upon the sending of the 48.008 ASSIGMENT FAILURE (cause: "no radio resource
available") for a de-queued TCH request (i.e. normal assignment) due to the receipt of a higher priority request.


by one.

parameter
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_OUT_HO_EXEC_TRX Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
Number of TCH drops during the execution of any TCH outgoing handover, per TRX. This counter takes into
MC621 = C621
Trigger condition:
1) Inter-cell TCH handover: whenever the timer supervising the handover procedure (T3103) expires.

2) External TCH handover (2G -> 2G): whenever the timer supervising the handover procedure on the serving cell
(T8) expires, except if a 48.008 CLEAR COMMAND with "normal event/call control" cause was received from the

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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC642=C42+C82
Trigger condition:
External comment:
--
Counter Name : NB_INC_EXT_HO_EXEC_FAIL_MS_ACCESS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC643=C43+C83
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_EXT_REAL_HO_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC645a = C45a + C85a
Trigger condition:
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.

External comment:
--
Counter Name : NB_OUT_EXT_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC646=C46+C86
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_EXT_HO_EXEC_FAIL_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC647=C47+C87
Trigger condition:
External comment:
--
Counter Name : NB_OUT_EXT_HO_EXEC_FAIL_NO_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC648=C48+C88
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_EXT_HO_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC650=C50+C90
Trigger condition:
External comment:
--
Counter Name : NB_INC_INT_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC652=C52+C92
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_INT_HO_EXEC_FAIL_MS_ACCESS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC653=C53+C93
Trigger condition:
External comment:
--
Counter Name : NB_OUT_INT_HO_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC655a=C55a+C95a
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_INT_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC656=C56+C96
Trigger condition:
External comment:
--
Counter Name : NB_OUT_INT_HO_EXEC_FAIL_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC657=C57+C97
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_INT_HO_EXEC_FAIL_NO_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC658=C58+C98
Trigger condition:
External comment:
--
Counter Name : NB_OUT_INT_HO_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC660=C60+C100
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_INTRA_HO_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter definition:
MC662=C62+C102
Trigger condition:
External comment:
--
Counter Name : NB_INTRA_HO_EXEC_FAIL_NO_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter definition:
MC663=C63+C103
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_INTRA_HO_EXEC_FAIL_REV Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter definition:
MC667=C67+C107
Trigger condition:
External comment:
--
Counter Name : NB_HO_2_TooLowQualUp Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC670=C470+C510
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_HO_3_TooLowLevUp Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC671=C471+C511
Trigger condition:
External comment:
--
Counter Name : NB_HO_4_TooLowQualDown Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC672=C472+C512
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_HO_5_TooLowLevDown Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC673=C473+C513
Trigger condition:
External comment:
--
Counter Name : NB_HO_6_TooLongDistance Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC674=C474+C514
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_HO_MSC_TRIG Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC675=C75+C115
Trigger condition:
External comment:
--
Counter Name : NB_HO_15_TooHighLevInterfUp Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC676=C476+C516
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_HO_16_TooHighLevInterfDown Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC677=C477+C517
Trigger condition:
External comment:
--
Counter Name : NB_HO_12_TooLowPowBudg Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC678=C478+C518
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_HO_21_HighLevNeigCellPrefBand Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC679=C479+C519
Trigger condition:
External comment:
--
Counter Name : NB_TCH_FR_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH normal assignments requests from FR only mobiles (after possible filtering from the MSC).
Trigger condition:
algorithm version 1 full rate allowed.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DR_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH normal assignments requests from dual rate mobiles.
Trigger condition:
algorithm version 1 full rate and GSM speech coding algorithm version 1 half rate allowed.
External comment:
--
Counter Name : NB_TCH_DR_EFR_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH normal assignment requests from mobiles supporting FR, HR and EFR.
Trigger condition:
version 1 full rate, GSM speech coding algorithm version 1 half rate and GSM speech coding algorithm version 2
full rate allowed.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_AMR_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH normal assignment requests from AMR mobiles.
Trigger condition:
version 3 full rate or half rate allowed.
External comment:
--
Counter Name : NB_TCH_DATA_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH normal assignment requests for data calls.
Trigger condition:
Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for data call.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_FR_EFR_REQ Counter Integer
B10 Common cell 1
Counter definition:
Number of TCH normal assignments requests from mobiles supporting only FR and EFR (after possible filtering
from the MSC).
Trigger condition:
algorithm version 1 full rate and GSM speech coding algorithm version 2 full rate allowed.
External comment:
--
Counter Name : NB_TCH_NO_FR_REQ Counter Integer
B10 Common cell 1
Counter 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
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
Alcatel-Lucent
Counter Name : NB_TCH_NOR_FR_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH normal assignment/mode modify in FR usage - whose channel is allocated in the BSC. This
Trigger condition:
External comment:
--
Counter Name : NB_TCH_NOR_HR_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
number of TCH normal assignment/mode modify in HR usage - whose channel is allocated in the BSC.
Trigger condition:
48.058 CHANNEL ACTIVATION / MODE MODIFY about to be sent to the BTS, indicating a HR channel with
GSM speech coding algorithm version 1, not related to handover.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_EFR_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH normal assignment/mode modify in EFR usage - whose channel is allocated in the BSC. This
Trigger condition:
External comment:
--
Counter Name : NB_TCH_NOR_ASS_ALLOC_TRX Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Counter definition:
Number of TCH (in HR or FR usage) normal assignment whose RTCH channel is allocated in the BSC, per TRX.
This counter also takes into account normal assignment whose RTCH channel is allocated in the BSC in
signaling mode (FR usage only), for DTM.
MC703 = C703
Trigger condition:
Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent on Abis Interface to activate a TCH
channel for normal assignment, or for DTM assignment with a TCH in signaling mode.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_AMR_FR_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH normal assignment/mode modify in FR AMR usage - whose channel is allocated in the BSC. This
Trigger condition:
External comment:
--
Counter Name : NB_TCH_NOR_AMR_HR_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
number of TCH normal assignment/mode modify in HR AMR usage - whose channel is allocated in the BSC.
Trigger condition:
48.058 CHANNEL ACTIVATION/ MODE MODIFY about to be sent to the BTS, indicating a HR channel with GSM
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_DATA_ALLOC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.
External comment:
--
Counter Name : NB_EGSM_MS_ACCESS_EXCEPT_LU Counter Integer
SFD reference : 3BK 10204 0519 DTZZA ("E-GSM support") Length: 4
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: E-GSM
Counter 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.

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_OUT_HO_REQ_TRX Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: Outgoing
Counter definition:
Nb of TCH outgoing handover requests, per TRX. Intracell, internal intercell and external handovers are counted
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


External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter 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
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.


External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_OUT_HO_SUCC_TRX Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
Nb of outgoing TCH handover successes, per TRX. Intracell, internal intercell and external handovers are counted
MC712 = C712
Trigger condition:
1) External HO in the following cases:
1a) 48.008CLEAR COMMAND (cause = "handover successful") is received on the serving BSC on the TCH
channel.
2) Internal inter-cell HO: whenever 44.018HANDOVER COMPLETE is received from the MS via the target cell on
the TCH channel.
TCH channel.

Note 2: This counter counts handover to UMTS.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_OUT_HO_FAIL_REV_TRX Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
Nb of outgoing TCH handover -execution failures due to MS access problem with reversion of the mobile to the
old
channel. Intracell, internal intercell and external handovers are counted together. This counter takes into account
handovers from TCH in traffic or in signaling mode. It does not take into account DTM Assignments.
MC713 = C713
Trigger condition:
1) External HO: Whenever a 44.018 HANDOVER FAILURE message is received on Abis interface from the
serving cell, during an external TCH handover.
2) Internal inter-cell HO: Whenever a 44.018 HANDOVER FAILURE message is received on Abis interface from
the serving cell, during an internal inter-cell TCH handover.
3) Intracell HO: Whenever a 44.018 ASSIGNMENT FAILURE message is received on Abis interface on the
serving
channel, during an internal intra-cell TCH handover.

Note: This counter counts handover to UMTS.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_OUT_HO_FAIL_NO_REV_TRX Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
Nb of outgoing TCH handover -execution failures due to MS access problem without reversion of the mobile to the
old channel (call drop). Intracell, internal intercell and external handovers are counted together. This counter takes

MC714 = C714
Trigger condition:
1) External TCH HO: Whenever the timer supervising the handover procedure on the serving cell (T8) expires,
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
3) Intracell TCH HO: Whenever the timer supervising the handover procedure (T3107) expires during an internal
intra-cell

Note: This counter counts hantover to UMTS
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_IDR_SUCC_TRX Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Counter definition:
Number of incoming directed retry (towards a TCH channel in HR or FR usage) successes, per TRX.
MC717a = C717a
Trigger condition:
TCH
channel involved in an internal directed retry procedure.
External comment:
--
Counter Name : NB_INC_TCH_HO_SUCC_TRX Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter 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,
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.

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_SUCC_TRX Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Counter definition:
Number of TCH (in HR or FR usage) normal assignment successes, per TRX. This counter also takes into
account normal assignment successes for TCH establishment in signaling mode (FR usage only), for DTM.
MC718 = C718
Trigger condition:
Whenever a 44.018 ASSIGNMENT COMPLETE message is received on Abis interface for a TCH channel that is
not involved in a handover procedure, in traffic or in signaling mode.
External comment:
--
Counter Name : NB_TCH_DROP_EST_PHAS_RLF_TRX Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
Number of TCH (in HR or FR usage) drops in TCH established phase due to radio link failure (radio link timeout or
Lapdm timer expiry), per TRX. This counter takes into account TCH in traffic or in signaling mode.
MC736 = C736
Trigger condition:
received on Abis interface for a TCH channel (after successful seizure).
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Sub domain-2: TCH
Counter definition:
Number of TCH (in HR or FR usage) drops in TCH established phase due to remote transcoder failures (per
TRX).
Trigger condition:
The counter is incremented whenever a 48.058 CONNECTION FAILURE INDICATION message with cause
"Remote Transcoder Failure" is received on Abis interface for an established TCH connection. The BSC considers
a TCH connection as "established" once a 44.018 ASSIGNMENT COMPLETE message (in case of normal
assignments or an internal intra-cell handovers) or a 44.018 HANDOVER COMPLETE message (in case of an
internal inter-cell incoming HO or an external inter-cell incoming
HO) has been received for the TCH connection.

Note 1: MC739 = C739.
Note 2: The counter is incremented only once per established TCH connection. Thus, even if the BTS sends
several 48.058 CONNECTION FAILURE INDICATION messages with cause "Remote Transcoder Failure" for a
particular established TCH connection, BSC will increment the counter only once for that connection.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX Counter Integer
B10 TRX 1
B8 TRX 0
B9 TRX 1
Counter definition:
Number of TCH (in HR or FR usage) normal assignment -execution failures due to MS access problem, per TRX.
This counter also takes into account DTM assignment -execution failures due to MS access problem for TCH
establishment in signaling mode (FR usage only).
MC746b = C746b
Trigger condition:
1) The timer T3107 in the BSS supervising the TCH channel seizure by the mobile expires (following the sending
of 44.018 ASSIGNMENT COMMAND for a TCH channel that is not involved in a handover procedure).
2) The timer T3107 in the BSS supervising the TCH channel seizure by the mobile expires, following the sending
of 44.018 DTM ASSIGNMENT COMMAND for a TCH channel in signaling mode.
3) The BSC receives a 44.018 ASSIGNMENT FAILURE on the old (SDCCH) channel during the normal
assignment procedure except in case of multiband cell, when the normal assignment procedure is performed in
the inner zone and the ASSIGNMENT FAILURE is received with the cause "protocol error unspecified".
4) The BSC receives a 44.018 DTM ASSIGNMENT FAILURE on the old (SDCCH) channel during the DTM
assignment procedure, for a TCH in signaling mode.
External comment:
--
Alcatel-Lucent
Counter Name : NB_HO_7_ConsBadSACCHmicroCell Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC785a=C585a+C605a
Trigger condition:
External comment:
--
Counter Name : NB_HO_17_TooLowLevUpMicroCell Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC785d=C585d+C605d
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_HO_18_TooLowLevDownMicroCell Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC785e=C585e+C605e
Trigger condition:
External comment:
--
Counter Name : NB_HO_14_HighLevNeigLowCellSlowMS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Cause
Counter definition:
MC785f=C585f+C605f
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : AV_NB_AVAIL_DYN_TS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter definition:
Average number of available dynamic SDCCH/8 timeslots.
Trigger condition:
integer value.
External comment:
--
Alcatel-Lucent
Counter Name : AV_NB_BUSY_DYN_TCH Counter Round (10
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter 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
External comment:
--
Alcatel-Lucent
Counter Name : MAX_NB_BUSY_DYN_TCH Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: TCH
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : AV_NB_BUSY_DYN_SDCCH Counter Round (10
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter definition:
Average number of busy SDCCH sub-channels allocated on the dynamic SDCCH/8 timeslots.
Trigger condition:
The BSC takes periodically a sample of the number of busy dynamic SDCCH sub-channels. The sampling period
is set to the value indicated in the Status Inspection field. At the expiry of the accumulation period, all samples
are averaged (i.e. summed and divided by the number of samples). The averaged value is rounded up or down to
the nearest value with an accuracy of 0.1.

A dynamic SDCCH sub-channel is considered as busy during the time it is allocated to a given MS for SDCCH
traffic.

Note that the counter value that is indicated in the ASCII file (which can be obtained via the OBSYNT interface) is
an integer value (i.e. it is as if the BSC multiplies by 10 the average). The reported value shall then be divided by
10 afterwards so that the value that is displayed to the end-user is the correct one
External comment:
--
Alcatel-Lucent
Counter Name : MAX_NB_BUSY_DYN_SDCCH Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter definition:
Maximum number of busy dynamic SDCCH sub-channels allocated on the dynamic SDCCH/8 timeslots.
Trigger condition:
Whenever a dynamic SDCCH sub-channel becomes busy, the BSC determines the current number of busy
dynamic SDCCH sub-channels. Counter MC802b is the maximum value of this number during the accumulation
period.
External comment:
--
Counter Name : TIME_SDCCH_CONGESTION Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: SDCCH
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_UL_SINGLE_BLOCK_SIG_RACH Counter Integer
SFD reference : 3BK 10204 0555 DTZZA ("Enhanced Cell Reselections for R97 Length: 4
onwards MS")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: CCCH
Counter 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.
External comment:
--
Counter Name : NB_UL_ONE_PHASE_SIG_RACH Counter Integer
onwards MS")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: CCCH
Counter definition:
Number of Channel Request messages with access cause "One phase packet access with request for single
timeslot uplink transmission" received by the BSS.
Trigger condition:
This counter is incremented whenever a 48.058 CHANNEL REQUIRED message with access cause "One phase
packet access with request for single timeslot uplink transmission" is received on Abis interface.
External comment:
--
Alcatel-Lucent
Counter Name : NB_CHANNEL_ASSIGN_DL_AGCH Counter Integer
onwards MS")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: CCCH
Counter 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.
External comment:
--
Counter Name : NB_CHANNEL_ASSIGN_DL_PCH Counter Integer
onwards MS")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: CCCH
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC81=C81, Number of incoming external SDCCH handover -preparation failures due to congestion.
Trigger condition:
on
A interface from the target BSC to the MSC during an external SDCCH handover.

External comment:
--
Counter Name : NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC812 = C812 = C612a + C612b + C612c + C612d
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_HO_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC820=C220+C310
Trigger condition:
External comment:
--
Counter Name : NB_INC_EXT_HO_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC821=C221+C311
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_INT_HO_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC830=C230+C330
Trigger condition:
External comment:
--
Counter Name : NB_INC_INT_HO_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC831=C231+C331
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Multiband
Counter 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.
DCS1800 bands", or,
DCS1900 bands", or,
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:
DCS1800 bands", or,
DCS1900 bands", or,

External comment:
--
Alcatel-Lucent
Counter Name : NB_INTRA_HO_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter definition:
MC870=C270+C360
Trigger condition:
External comment:
--
Counter Name : NB_INTRA_HO_ATPT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: Intra
Counter definition:
MC871=C271+C361
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_CELL_PAGING_CMD Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: CCCH
Counter definition:
MC8A= SUM (all TRX_TS of the Cell) C8A
Trigger condition:
External comment:
--
Counter Name : NB_CELL_IMM_ASS_CMD Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: CCCH
Counter definition:
MC8B= SUM (all TRX_TS of the Cell) C8B
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_CELL_CHAN_REQD Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: CCCH
Counter definition:
MC8C= SUM (all TRX_TS of the cell) C8C
Trigger condition:
External comment:
--
Counter Name : NB_CELL_IMM_ASS_REJ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2: CCCH
Counter definition:
MC8D= SUM (all TRX_TS of the cell) C8D
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_Suspend_Resume_req Counter Integer
B mobiles")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2:
Counter definition:
Number of suspend / Resume requests.
A request could lead to a success, a failure or a stop.
Trigger condition:
Emission of MS Suspend message by the BSC to the MFS
Emission of MS Resume message by the BSC to the MFS
A suspend message received from MS with a "suspend cause" filtered by BSC will not be counted. Stop causes
could be:
1) External handover
2) MS channel failure.
External comment:
--
Counter Name : Nb_Suspend_fail Counter Integer
B mobiles")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2:
Counter definition:
Number of suspend/resume procedure failures.
Trigger condition:
Reception of -Suspend nack or resume nack, or expiration of T_GPRS_Resume.
External comment:
--
Alcatel-Lucent
Counter Name : Nb_Suspend_succ Counter Integer
B mobiles")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2:
Counter definition:
Number of suspensions successes.
Trigger condition:
Reception of Resume ack message from MFS.
External comment:
--
Counter Name : NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
MC91=C91, Number of incoming internal inter-cell SDCCH handover -preparation failures due to congestion.
Trigger condition:
Whenever a internal inter-cell SDCCH handover cannot be performed, because there is no free SDCCH
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_NOR_ASS_HO_REQ_ABLE_TO_PREEMPT Counter Integer
SFD reference : 3BK 10204 0308 DTZZA ("Pre-emption and eMLPP") Length: 2
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of TCH Normal Assignment- and incoming external TCH Handover/Directed Retry Requests with the
ability to preempt another call with lower priority.
Trigger condition:
1) Whenever the BSC receives a 48.008 ASSIGNMENT REQUEST message with the pre-emption capability
indication set (pci bit=1 in the Priority IE), repetitions of the ASSIGNMENT REQUEST message in case of
channel modification are not counted, or
2) Whenever the BSC receives a 48.008 HANDOVER REQUEST message requesting a TCH
channel with
i) the pre-emption capability indication set (pci bit=1) and Extra Information IE (or Old BSS to New BSS IE) is
absent, or
ii) the pre-emption capability indication set (pci bit = 1) and the Pre-emption Recommendation of the Extra
Information IE is set (prec bit = 1).

External comment:
--
Alcatel-Lucent
Counter Name : NB_PREEMPT_CAP_ALLOC_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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).
External comment:
--
Counter Name : NB_PREEMPTED_CALLS Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter definition:
Number of pre-empted calls in the cell.
Trigger condition:
Whenever a 48.008 CLEAR REQUEST or UPLINK RELEASE INDICATION message with preemption cause is
sent to the MSC.
External comment:
--
Alcatel-Lucent
Counter Name : NB_PREEMPT_CAP_OUT_DR_ALLOC_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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.
External comment:
--
Counter Name : NB_TCH_NOR_ASS_HO_SUCC_PREEMPTABLE Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Counter 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).

External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_3G_2G_HO_REQ Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2:
Counter 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)
External comment:
--
Counter Name : NB_INC_EXT_3G_2G_HO_SUCC Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2:
Counter definition:
Number of incoming external SDCCH and TCH HO successes from a UMTS system.
Trigger condition:
44.018HANDOVER_COMPLETE message received from the MS. Only handovers from a UMTS system shall be
taken into account (if the field Cell Identifier discriminator in the I.E. Cell Identifier (serving) of the corresponding
48.008 HANDOVER REQUEST is set to 1011).
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_3G_2G_HO_EXEC_FAIL_MS_ACC Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2:
Counter definition:
Number of incoming external TCH and SDCCH UMTS to GSM HO execution failures due to MS access problem,
with or without reversion of the mobile to the old channel.
Trigger condition:
1) Reception of 48.058CONNECTION FAILURE INDICATION (cause= "handover access failure") for a HO from a
UMTS system.
2) Reception of 48.008CLEAR COMMAND (cause= "radio interface failure, reversion to old channel") for a HO
from a UMTS system. Handovers from a UMTS system are identified as follows: the field Cell Identifier
discriminator in the I.E. Cell Identifier (serving) of the 48.008 HANDOVER REQUEST is set to 1011)
External comment:
--
Counter Name : NB_INC_EXT_3G_2G_HO_ATPT Counter Integer
Improvements")
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2:
Counter definition:
Number of incoming external SDCCH and TCH HO attempts from a UMTS system.
Trigger condition:
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)
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_TCH_3G_2G_HO_EMERGENCY_REQ Counter Integer
SFD reference : 3BK 10204 0616 DTZZA ("Load based 3G Handover filtering") Length: 2
B10 Common cell 1
B9 Common cell 1
Sub domain-2:
Counter definition:
Number of incoming 3G to 2G external inter-cell TCH (in HR or FR usage) handover requests, with emergency
cause.
Trigger condition:
Whenever a 48.008 HANDOVER REQUEST is received for a TCH with a SAI in the source cell identifier and
indicating an emergency cause (uplink quality, uplink strength, downlink quality, downlink strength, distance).
External comment:
--
Counter Name : NB_INC_EXT_TCH_3G_2G_HO_REQ Counter Integer
B10 Common cell 1
B9 Common cell 1
Sub domain-2:
Counter definition:
Number of incoming 3G to 2G external inter-cell TCH (in HR or FR usage) handover requests.
Trigger condition:
Whenever a 48.008 HANDOVER REQUEST is received for a TCH with a SAI in the source cell identifier
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_TCH_3G_2G_HO_PREP_FAIL_3GCONG Counter Integer
B10 Common cell 1
B9 Common cell 1
Sub domain-2:
Counter definition:
Number of 3G to 2G TCH hand over failures in preparation phase due to 3G high load in the target cell.
Trigger condition:
Whenever a 48.008 HANDOVER FAILURE message is sent to the MSC with cause "no radio resource available"
for a TCH HO request coming from 3G, due to 3G high load in the target cell. This counter shall be incremented
only if THR_CELL_LOAD_3G_REJECT < 100%.
External comment:
--
Counter Name : TIME_3G_HOReject_HL Counter Integer
B10 Common cell 1
B9 Common cell 1
Sub domain-2:
Counter 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%.
External comment:
--
Alcatel-Lucent
Counter Name : NB_LCS_REQ Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Technology: LCS Sub domain-1: LCS
Sub domain-2:
Counter definition:
Number of LCS requests received from the MSC in CS domain. The LCS requests encompass the geographic
location requests and the LCS assistance data requests.
Trigger condition:
Whenever a 48.008 PERFORM LOCATION REQUEST message is received by the BSC from the MSC.
External comment:
--
Counter Name : NB_LCS_SUCC Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2:
Counter definition:
Number of successful LCS requests.The successful LCS requests encompass the successful geographic location
estimate and the successful LCS assistance data delivery.
Trigger condition:
Whenever a 48.008 PERFORM LOCATION RESPONSE message is sent to the MSC without including the OIE
LCS Cause.
External comment:
--
Alcatel-Lucent
Counter Name : NB_LCS_FAIL_LB Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2:
Counter definition:
Number of LCS requests rejected by the SMLC. The failed LCS requests indicated by the SMLC to the BSC
encompass the failure to determine geographic location estimate and the failure of LCS assistance data delivery.
Trigger condition:
Whenever a 09.31 PERFORM LOCATION RESPONSE message is received from the SMLC with the OIE LCS
Cause.
External comment:
--
Counter Name : NB_LCS_ABORT Counter Integer
B10 Common cell 1
B8 Common cell 0
B9 Common cell 1
Sub domain-2:
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : TIME_SPDCH_LIMIT_HIGH_LOAD Counter Integer
B10 Common cell 2
B9 Common cell 2
Technology: GPRS Sub domain-1: Channel
Sub domain-2: TCH
Counter 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.
External comment:
This counter replaces the B8 MFS counter P1.
Alcatel-Lucent
Counter Name : NB_OUT_2G_3G_HO_REQ Counter Integer
SFD reference : 3BK 10204 0615 DTZZA ("2G to 3G Handover") Length: 2
B10 Common cell 2
B9 Common cell 2
Counter definition:
Number of outgoing external TCH (in HR or FR usage) handover requests to a 3G cell.
Trigger condition:
Whenever a 48.008 HANDOVER REQUIRED message is sent on A interface to the MSC for a TCH handover to a
3G FDD cell.

48.008 HANDOVER REQUIRED is sent in following situations :
1) An external handover alarm has been raised, with corresponding list of candidate cells including a 3G cell.

External comment:
--
Counter Name : NB_OUT_2G_3G_HO_SUCC Counter Integer
B10 Common cell 2
B9 Common cell 2
Counter definition:
Number of outgoing external TCH (in HR or FR usage) handover successes to a 3G cell.
Trigger condition:
External TCH handover to a 3G cell, in the following cases:
1/ 48.008 CLEAR COMMAND message with a cause value of "handover successful" is received on A interface
on
the serving BSC from the MSC.

External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_2G_3G_HO_ATPT Counter Integer
B10 Common cell 2
B9 Common cell 2
Counter definition:
Number of outgoing external TCH (in HR or FR usage) handover attempts to a 3G cell.
Trigger condition:
an external TCH handover procedure to a 3G cell.

External comment:
--
Counter Name : NB_OUT_2G_3G_HO_EXEC_FAIL_NO_REV Counter Integer
B10 Common cell 2
B9 Common cell 2
Counter definition:
Number of outgoing external TCH (in HR or FR usage) handover execution failures to a 3G cell due to MS access
problem without reversion of the mobile to the old channel (call drop).
Trigger condition:
Whenever the timer supervising the handover procedure on the serving cell (T3121), expires during an external
TCH handover to a 3G cell, except if a 48.008 CLEAR COMMAND with "normal event/call control" cause was
received from the MSC, leading to a normal call release. In such a case, the handover is considered as
successful.

External comment:
--
Alcatel-Lucent
Counter Name : NB_OUT_2G_3G_HO_EXEC_FAIL_REV Counter Integer
B10 Common cell 2
B9 Common cell 2
Counter definition:
Number of outgoing external TCH (in HR or FR usage) handover -execution failures to a 3G cell due to MS
access
problem with reversion of the mobile to the old channel.
Trigger condition:
Whenever a 44.018 HANDOVER FAILURE message is received on Abis interface from the serving cell , during
an
external TCH handover to a 3G cell.

External comment:
--
Counter Name : NB_OUT_2G_3G_HO_PREP_FAIL Counter Integer
B10 Common cell 2
B9 Common cell 2
Counter definition:
Nb of outgoing TCH handover -preparation failures to a 3G cell.
Trigger condition:
Whenever a 48.008 HANDOVER REQUIRED REJECT is received from the MSC by the serving BSC for an
outgoing external TCH HO to a 3G cell.
External comment:
--
Alcatel-Lucent
Counter Name : NB_2G_3G_HO_8 Counter Integer
SFD reference : Length: 2
Data collection Measured None
B10 Common cell 2
B9 Common cell 2
Technology: Sub domain-1:
Sub domain-2:
Counter definition:
Provision for 2G to 3G HO
Trigger condition:
External comment:
--
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
Trigger condition:
External comment:
--
Alcatel-Lucent
MC924j Type 110 : Overview measurements
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
Trigger condition:
External comment:
--
MC924k Type 110 : Overview measurements
B10 Common cell 2
B9 Common cell 2
Sub domain-2:
Counter definition:
provision for 2G to 3G HO
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_AGCH_USEFUL_BLOCKS_SENT Counter Integer
SFD reference : 3BK 10204 0028 DTZZA ("Multiple CCCH") Length: 4
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of useful blocks sent on AGCH channel (The dummy blocks are not counted).
Trigger condition:
This counter is increased each time an IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED
or
IMMEDIATE ASSIGNMENT REJECT or PACKET UPLINK ASSIGNMENT or PACKET DOWNLINK
ASSIGNMENT message is taken from one AGCH queue and put on AGCH channel.

Note: for cells mapped on non-Evolium BTS, the value of this counter is set to zero.
External comment:
--
Counter Name : NB_PCH_USEFUL_BLOCKS_SENT Counter Integer
B10 Common cell 1
Sub domain-2:
Counter 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.

External comment:
--
Alcatel-Lucent
Counter Name : NB_BUSY_RACH_SLOTS Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of busy RACH slots.
Trigger condition:
Each 51-multiframes the Layer 1 reports the load on the RACH via the RACH_MEASUREMENTS_RESULTS
message, which contains the following information:
- N_VRACH: number of Access Bursts successfully decoded
- N_BUSY: number of RACH busy slots

On reception of this message, the following counters are updated:
- NB_BUSY_RACH_SLOTS = NB_BUSY_RACH_SLOTS + N_BUSY

External comment:
--
Alcatel-Lucent
Counter Name : NB_CHANNEL_RQ_RADIO Counter Integer
B10 Common cell 1
Technology: GPRS Sub domain-1: Channel
Sub domain-2:
Counter 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

External comment:
--
Alcatel-Lucent
Counter Name : NB_ASSIGN_CMD_RECEIVED_ABIS Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of 48.058 IMMEDIATE ASSIGN COMMAND messages received by the BTS on Abis and had to be sent
for CS and PS traffic to the MS.

Note: This counter does not count what it is really sent on the interface radio on the AGCH channel because
some messages can be discarded due to congestion some others can be merged in one message (Immediate
assignment extended) and some others sent in PCH channel when the AGCH is up to 100%.
Trigger condition:
This counter is increased each time an IMMEDIATE ASSIGNMENT COMMAND message is received on Abis
interface.

External comment:
--
Counter Name : NB_ASSIGN_CMD_DISCARDED Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of 48.058 IMMEDIATE ASSIGN COMMAND messages received by the BTS on Abis and discarded due
to congestion.
Trigger condition:
This counter is increased each time an IMMEDIATE ASSIGNMENT COMMAND messages is discarded on
detection of AGCH FIFO overload.

External comment:
--
Alcatel-Lucent
Counter Name : NB_PAGING_CMD_RECEIVED_ABIS Counter Integer
B10 Common cell 1
Sub domain-2:
Counter 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).

External comment:
--
Alcatel-Lucent
Counter Name : NB_PAGING_CMD_DISCARDED Counter Integer
B10 Common cell 1
Sub domain-2:
Counter 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.

External comment:
--
Counter Name : TCH_BLOCKING_OCCURENCES_BSC Counter Integer
SFD reference : 3BK 12204 0031 DTZZA ("MX capacity improvements") Length: 4
B10 BSC 1
Sub domain-2:
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_DTM_UL_TCH_ASS_ATPT Counter Integer
SFD reference : 3BK 10204 0032 DTZZA ("DUAL TRANSFER MODE") Length: 4
B10 Common cell 1
Technology: DTM Sub domain-1: Resource Allocation & Management
Sub domain-2: DTM Assignment
Counter 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.
External comment:
--
Counter Name : NB_DTM_DL_TCH_ASS_ATPT Counter Integer
B10 Common cell 1
Counter 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.
External comment:
--
Alcatel-Lucent
Counter Name : NB_DTM_UL_PACKET_ASS_ATPT Counter Integer
B10 Common cell 1
Counter definition:
Number of UL TBF establishment attempts in DTM without reallocation of the TCH (sending of Packet Assignment
Command with UL TBF).
Trigger condition:
Whenever the BSC sends (through the BTS) 44.018 PACKET ASSIGNMENT message that includes the
"Description of the Uplink Packet Channel Assignment" optional IE.
External comment:
--
Counter Name : NB_DTM_DL_PACKET_ASS_ATPT Counter Integer
B10 Common cell 1
Counter definition:
Number of DL TBF establishment attempts in DTM without reallocation of the TCH (sending of Packet Assignment
Command with DL TBF).
Trigger condition:
Whenever the BSC sends (through the BTS) 44.018 PACKET ASSIGNMENT message that includes the
"Description of the Downlink Packet Channel Assignment" optional IE.
External comment:
--
Alcatel-Lucent
Counter Name : NB_DTM_UL_TCH_ASS_EXEC_FAIL_RADIO Counter Integer
B10 Common cell 1
Counter definition:
Number of UL TBF establishment in DTM with reallocation of the TCH - execution failures due to MS access
problem.
Trigger condition:
1) Whenever the BSC receives from the BTS a DATA INDICATION (DTM ASSIGNMENT FAILURE) message
after
having sent (through the BTS) 44.018 DTM ASSIGNMENT COMMAND message that includes the "Description of
the Uplink Packet Channel Assignment" optional IE.
2) After having sent (through the BTS) 44.018 DTM ASSIGNMENT COMMAND message that includes the
"Description of the Uplink Packet Channel Assignment" optional IE, upon T3107 expiry, the BSC does not receive
neither DTM ASSIGNMENT FAILURE (on the old channel) nor ASSIGNMENT COMPLETE (on the new channel)
messages.
External comment:
--
Alcatel-Lucent
Counter Name : NB_DTM_DL_TCH_ASS_EXEC_FAIL_RADIO Counter Integer
B10 Common cell 1
Counter definition:
Number of DL TBF establishment in DTM with reallocation of the TCH - execution failures due to MS access
problem.
Trigger condition:
1) Whenever the BSC receives from the BTS a DATA INDICATION (DTM ASSIGNMENT FAILURE) message
after
having sent (through the BTS) 44.018 DTM ASSIGNMENT COMMAND message that includes the "Description of
the Downlink Packet Channel Assignment" optional IE.
2) After having sent (through the BTS) 44.018 DTM ASSIGNMENT COMMAND message that includes the
"Description of the Downlink Packet Channel Assignment" optional IE, upon T3107 expiry, the BSC does not
receive neither DTM ASSIGNMENT FAILURE (on the old channel) nor ASSIGNMENT COMPLETE (on the new
channel) messages.
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_UL Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of TCH drops due to Cause 2 (Too low quality in UL).
Trigger condition:
1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with cause "radio link failure" is received
on
Abis interface for a TCH channel (after successful seizure).
2) Whenever an 48.058 ERROR INDICATION message is received on Abis interface after TCH seizure and leads
to a loss of call.
3) Whenever the timer supervising the handover procedure (T3103) expires during the inter-cell TCH handover.
4) Whenever the timer supervising the handover procedure on the serving cell (T8) expires during the external
TCH
handover.

The BSC uses the last valid measurements (Note) received for this MS. The counter is incremented if the
following
condition is fulfilled:

AV_RXQUAL_UL_HO > L_RXQUAL_UL_H + OFFSET_RXQUAL_FH
And
AV_RXLEV_UL_HO <= RXLEV_UL_IH

Note: "Last valid measurements" means the last received 48.058 MEASUREMENT RESULT messages with
S-BFI flag set to "0".
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_UL Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of TCH drops due to Cause 3 (Too low level in UL).
Trigger condition:
on
to a loss of call.
TCH
handover.

The BSC uses the last valid measurements received for this MS (Note). The counter is incremented if the
following

a) the Cause 2 (MC928a) and Cause 4 (MC928c) are not eligible;

b) and the following condition is fulfilled:

AV_RXQUAL_UL_HO <= L_RXQUAL_UL_H + OFFSET_RXQUAL_FH
And
AV_RXLEV_UL_HO < L_RXLEV_UL_H

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_DL Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of TCH drops due to Cause 4 (Too low quality on the downlink).
Trigger condition:
on
to a loss of call.
TCH
handover.

following

a) the Cause 2 (MC928a) is not eligible.


AV_RXQUAL_DL_HO > L_RXQUAL_DL_H + OFFSET_RXQUAL_FH
And
AV_RXLEV_DL_HO <= RXLEV_DL_IH

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_DL Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of TCH drops due to Cause 5 (Too low level in DL).
Trigger condition:
on
to a loss of call.
TCH
handover.

following

a) the Cause 2 (MC928a), Cause 4 (MC928c) and Cause 3 (MC928b) are not eligible;


AV_RXQUAL_DL_HO <= L_RXQUAL_DL_H + OFFSET_RXQUAL_FH
And
AV_RXLEV_DL_HO < L_RXLEV_DL_H

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_CAUSE_TOO_LONG_MS_BS_DISTANCE Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of TCH drops due to Cause 6 (Too long MS-BS distance).
Trigger condition:
on
to a loss of call.
TCH
handover.

following

a) the Cause 2 (MC928a), Cause 4 (MC928c), Cause 3 (MC928b) and Cause 5 (MC928d) are not eligible;


AV_RANGE_HO > U_TIME_ADVANCE

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_CAUSE_TOO_SHORT_MS_BS_DISTANC Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of TCH drops due to Cause 22 (Too short MS-BS distance).
Trigger condition:
on
to a loss of call.
TCH
handover.

following

a) the Cause 2 (MC928a), Cause 4 (MC928c), Cause 3 (MC928b), Cause 5 (MC928d) and Cause 6 (MC928e)
are
not eligible;


AV_RANGE_HO <= L_TIME_ADVANCE

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_CAUSE_TOO_HIGH_INTERFERENCE_UP Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of TCH drops due to Cause 15 (Too high interference level on the uplink).
Trigger condition:
on
to a loss of call.
3) Whenever the timer supervising the handover procedure (T3107) expires during the intra-cell TCH handover.

following

a) the Cause 2 (MC928a), Cause 4 (MC928c), Cause 3 (MC928b), Cause 5 (MC928d), Cause 6 (MC928e) and
Cause 22 (MC928f) are not eligible;


AV_RXQUAL_UL_HO > THR_RXQUAL_CAUSE_15 + OFFSET_RXQUAL_FH
And
AV_RXLEV_UL_HO > RXLEV_UL_IH

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_CAUSE_TOO_HIGH_INTERFERENCE_DO Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of TCH drops due to Cause 16 (Too high interference level on the downlink).
Trigger condition:
on
to a loss of call.

following

a) the Cause 2 (MC928a), Cause 3 (MC928b), Cause 4 (MC928c), Cause 5 (MC928d), Cause 6 (MC928e),
Cause
22 (MC928f) and Cause 15 (MC928g) are not eligible;


AV_RXQUAL_DL_HO > THR_RXQUAL_CAUSE_16 + OFFSET_RXQUAL_FH
And
AV_RXLEV_DL_HO > RXLEV_DL_IH

External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_DROP_OTHER_CAUSES Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of TCH drops due to other causes than Cause 2 (Too low quality in UL), Cause 3 (Too low level in UL),
Cause 4 (Too low quality on the downlink), Cause 5 (Too low level in DL), Cause 6 (Too long MS-BS distance),
Cause 15 (Too high interference level on the uplink), Cause 16 (Too high interference level on the downlink),
Cause
22 (Too short MS-BS distance).
Trigger condition:
on
to a loss of call.
TCH
handover.

The BSC uses the last measurements received for this MS. The counter is incremented if the following condition
is fulfilled:

a) the Cause 2 (MC928a), Cause 3 (MC928b), Cause 4 (MC928c), Cause 5 (MC928e), Cause 6 (MC928e),
Cause
22 (MC928f), Cause 15 (MC928g) and Cause 16 (MC928h) are not eligible.
External comment:
--
Alcatel-Lucent
Counter Name : NB_ABIS_PAGING_MESSAGE_RECEIVED Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of PAGING COMMAND / MULTIPLE PAGING COMMAND message received by the BTS on Abis.
Trigger condition:
For legacy BSC, the value of this counter shall be set to "0".

For BSC EVOLUTION:
a) This counter is increased by one each time a PAGING COMMAND message is received on Abis interface.
b) This counter is increased by one each time a MULTIPLE PAGING COMMAND message is received on Abis
interface.

External comment:
--
Counter Name : NB_TCH_NOR_AMR_WB_GMSK_FR_ALLOC Counter Integer
B10 Common cell 1
Counter definition:
Number of TCH normal assignment/mode modify in FR AMR WB GMSK usage - whose channel is allocated in
the BSC. This counter takes into account mode modify from TCH signaling to TCH traffic (following a DTM
assignment with a TCH in signaling mode).
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_TCH_AMR_WB_GMSK_REQ Counter Integer
B10 Common cell 1
Counter definition:
Number of TCH normal assignment requests from AMR WB GMSK mobiles
Trigger condition:
version 5 full rate allowed.
External comment:
--
Counter Name : NB_TCH_NOR_ASS_PREP_FAIL_PMIS Counter Integer
B10 Common cell 1
Counter definition:
Number of TCH (in HR or FR usage) normal assignment preparation failures due to A interface mismatch
between
the BSC and the MSC.
Trigger condition:
The counter is incremented upon the sending of 48.008 ASSIGNMENT FAILURE (cause: "circuit pool mismatch")
External comment:
--
Alcatel-Lucent
Counter Name : NB_INC_EXT_TCH_HO_PREP_FAIL_PMIS Counter Integer
B10 Common cell 1
Counter definition:
Number of incoming external TCH (in HR or FR usage) handover -preparation failures due to A interface
mismatch
between the BSC and the MSC.
Trigger condition:
Whenever a 48.008 HANDOVER FAILURE message with a cause value of "circuit pool mismatch" is sent on A
Note: This counter counts both inter-PLMN and intra-PLMN handover event
External comment:
--
Counter Name : NB_CALL_TFO_AMR_WB Counter Integer
SFD reference : 3BK 10204 0096 DTZZA (TFO for AMR-NB and AMR-WB) Length: 4
B10 Common cell 1
Sub domain-2: TFO
Counter definition:
Number of TCH assigned using AMR-WB for which TFO has been successfully established.
Trigger condition:
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).
assigned TCH).
External comment:
--
Alcatel-Lucent
Counter Name : NB_HO_INTER_TFO_AMR_WB Counter Integer
B10 Common cell 1
Sub domain-2: TFO
Counter 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).

assigned TCH).

Note 2: This means that the counter is incremented only if the TCH is assigned to serve an incoming inter-cell
handover.
External comment:
--
Alcatel-Lucent
Counter Name : NB_HO_EXT_TFO_AMR_WB Counter Integer
B10 Common cell 1
Sub domain-2: TFO
Counter 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).

assigned TCH).

Note 2: This means that the counter is incremented only if the TCH is assigned to serve an incoming iexternal
handover.
External comment:
--
Counter Name : NB_CALL_TFO_AMR Counter Integer
B10 Common cell 1
Technology: Sub domain-1: --
Sub domain-2:
Counter definition:
For future usage (Number of TCH assigned using AMR for which TFO has been successfully established).
Trigger condition:
The value of this provisioned counter shall be set to "0".
External comment:
--
Alcatel-Lucent
Counter Name : NB_HO_INTER_TFO_AMR Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage (Number of TCH assigned using AMR for which TFO has been successfully established after an
inter cell handover).
Trigger condition:
External comment:
--
Counter Name : Reserve_BSC_1 Counter Integer
B10 BSC 1
Sub domain-2:
Counter definition:
For future usage
Trigger condition:
The value of this provisioned counter shall be set to "0"
External comment:
--
Alcatel-Lucent
B10 BSC 1
Sub domain-2:
Counter definition:
For future usage
Trigger condition:
External comment:
--
B10 BSC 1
Sub domain-2:
Counter definition:
For future usage
Trigger condition:
External comment:
--
Alcatel-Lucent
B10 BSC 1
Sub domain-2:
Counter definition:
For Future usage
Trigger condition:
External comment:
--
B10 BSC 1
Sub domain-2:
Counter definition:
For future usage
Trigger condition:
External comment:
--
Alcatel-Lucent
B10 BSC 1
Sub domain-2:
Counter definition:
For future usage
Trigger condition:
External comment:
--
Counter Name : NB_HO_EXT_TFO_AMR Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage (Number of TCH assigned using AMR for which TFO has been successfully established after an
external handover).
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : Reserve_cell_12 Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
Alcatel-Lucent
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
Alcatel-Lucent
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
Alcatel-Lucent
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_PS_CHAN_REQD Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of 48.058 CHANNEL REQUIRED (for packet service) received via the selected cell.
Trigger condition:
This counter is incremented by one if:
1) the "RA (Random Access Reference)" byte in the 48.058 CHANNEL REQUIRED message equals to the
following values: 011110xx, 01111x0x, 01111xx0 (one phase packet access); 01110xxx (single block packet
access), or;
2) EGPRS Request Reference optional IE is included in the 48.058 CHANNEL REQUIRED message.
External comment:
--
Alcatel-Lucent
Counter Name : NB_DISCARDED_PS_CHAN_REQD_BECAUSE_GSL_CON Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of 48.058 CHANNEL REQUIRED (for packet service) received and discarded by the BSC in case of GSL
CONGESTION.
Trigger condition:
"48.058 CHANNEL REQUIRED (for packet service)" refers to one 48.058 CHANNEL REQUIRED message that
contains the "EGPRS Request Reference" optional IE; or the "RA (Random Access Reference)" byte of 48.058
CHANNEL REQUIRED message equals to the following values: 011110xx, 01111x0x, 01111xx0 (one phase
packet access); 01110xxx (single block packet access).

This counter is incremented by one if a "48.058 CHANNEL REQUIRED (for packet service)" message is
discarded
by the BSC in case of GSL congestion (for the handling of the GSL congestion: cf. the BTP parameters
NB_MSG_GSL_OUTPUT_BUFFER_XON_G2_BSC, NB_MSG_GSL_OUTPUT_BUFFER_XOFF_G2_BSC,
NB_MSG_GSL_OUTPUT_BUFFER_XON_MX_BSC and NB_MSG_GSL_OUTPUT_BUFFER_XOFF_MX_BSC).
External comment:
--
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
Alcatel-Lucent
Counter Name : NB_INVALID_CHAN_REQD_RECEIVED_BY_BSC Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of invalid 48.058 CHANNEL REQUIRED (for all establishment cause) messages received by the BSC.
Trigger condition:
Upon reception of a 48.058 CHANNEL REQUIRED message from the BTS, the BSC checks firstly the content of
message. If an error is found, the received 48.058 CHANNEL REQUIRED message is discarded by the BSC.
The counter MC962 is incremented by one each time the received 48.058 CHANNEL REQUIRED message is
discarded because one of the following errors have been detected by the BSC:
1) The message syntax errors, for example (list non-exclusive):
1a) the message length is incorrect: i.e., the EGPRS Request Reference OIE is not present, but the length of
message does not equal to "10"; or the EGPRS Request Reference OIE is present, but the length of message
does not equal to "13" (Note 1).
1b) the IE length is incorrect.
2) the Timeslot Number received in the CHANNEL REQUIRED message does not equal to 0 or 2 (only timeslot 0
or 2 can be used as BCCH Timeslots).
3) The C-bits (C5, C4, C3, C2 & C1) of Channel Number MIE is not equal to the coding 10001 "Uplink CCCH
(RACH)".
4) In case where the GPRS service is allowed (EN_GPRS = TRUE) and the GPRS service has already been
activated in the cell: the BSC checks the presence of EGPRS Request Reference optional IE. If this OIE is not
included, then the BSC checks the "RA (Random Access Reference)" byte in the 48.058 CHANNEL REQUIRED
message: if the bits 8, 7 and 6 of "RA (does not equal to one of the following values: 000, 100, 101, 110, 111 and
"RA (Random Access Reference)" byte in the 48.058 CHANNEL REQUIRED message does not equal to the
following values: 011110xx, 01111x0x, 01111xx0 (one phase packet access); 01110xxx (single block packet
access), Note 2.
5) In case where the GPRS service is not allowed (EN_GPRS = FALSE) or the GPRS service has not yet been
activated in the cell: if the bits 8, 7 and 6 of "RA (Random Access Reference)" byte in the 48.058 CHANNEL
REQUIRED message does not equal to one of the following values: 000, 100, 101, 110, 111; or if EGPRS
Request Reference optional IE is included in the 48.058 CHANNEL REQUIRED message.
6) The Access delay value is greater than or equal to RACH_TA_FILTER.

Note 1: the EGPRS Request Reference IE is an optional (ALU proprietary) in the CHANNEL REQUIRED
message. If this optional IE is present, the length of CHANNEL REQUIRED message is 13 instead of 10.
Note 2: if the EGPRS Request Reference OIE is included, the BSC does not check the "RA (Random Access
Reference)" byte in the 48.058 CHANNEL REQUIRED message.
External comment:
--
Alcatel-Lucent
Counter Name : NB_NON_PS_CHAN_REQD_DISCRADED_BECAUSE_CON Counter Integer
B10 Common cell 1
Sub domain-2:
Counter definition:
Number of valid 48.058 CHANNEL REQUIRED (for non-(E)GPRS related establishment cause) discarded by the
BSC due to the congestion.
Trigger condition:
Upon reception of a 48.058 CHANNEL REQUIRED message from the BTS, the BSC checks firstly the content of
received message (see counter MC962).
After having passed successfully this check, the BSC checks the establishment cause in the received message.
If the received 48.058 CHANNEL REQUIRED message does not contain the "EGPRS Request Reference"
optional IE; or the "RA (Random Access Reference)" byte does not equal to the following values: 011110xx,
01111x0x, 01111xx0 (one phase packet access); 01110xxx (single block packet access), then this message is
considered as a "CHANNEL REQUIRED (for non-(E)GPRS related establishment cause)" message.
The BSC may discard a "CHANNEL REQUIRED (for non-(E)GPRS related establishment cause)" message in
case of cell congestion.
MC963 is incremented by one each time a "CHANNEL REQUIRED (for non-(E)GPRS related establishment
cause)" message is discarded because one of the following reasons:
1) The cell is unavailable for telecom traffic
2) there is no SDCCH available and EN_IM_ASS_REJ = "disabled".
3) there is no SDCCH available, and EN_IM_ASS_REJ = "enabled", and the Bits 8, 7 and 6 of "RA (Random
Access Reference)" byte in the 48.058 CHANNEL REQUIRED message equals to "000", and the value of
parameter WI_OP equals to 255.
Access Reference)" byte in the 48.058 CHANNEL REQUIRED message equals to "100".
parameter WI_EC equals to 255.
parameter WI_CR equals to 255.
parameter WI_OC equals to 255.
8) there is BSC inter-process congestion.
External comment:
--
Alcatel-Lucent
Counter Name : NB_VALID_LOCATION_UPDATE_RECEIVED_BY_BSC Counter Integer
B10 Common cell 1
Sub domain-2:
Counter 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)".
External comment:
--
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
Alcatel-Lucent
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
Alcatel-Lucent
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
Alcatel-Lucent
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
Alcatel-Lucent
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
Alcatel-Lucent
B10 Common cell 1
Sub domain-2:
Counter definition:
For future usage.
Trigger condition:
External comment:
--
MN1.1 Type 110 : Overview measurements
Counter Name : TIME_N7_ALIGNED Counter Integer
Sub domain-2: A
Counter definition:
Time (in seconds) during which the N7 SL is correctly aligned.
Trigger condition:
Whenever the No.7 Signalling channel between the MSC and BSS is correctly aligned, this counter will be
incremented every second.
External comment:
--
Alcatel-Lucent
Type name: 2G Traffic flow measurements
Type definition:
Set of incoming external or internal inter-cell SDCCH or TCH (in HR or FR usage) handover counters
provided per adjacency: variable serving cell - variable target cell. The internal and external directed
retries are counted. Only handovers / directed retries from 2G cells are taken into account (i.e.
handovers from 3G are not counted in type 180).
C400 Type 180 : 2G Traffic flow measurements
Counter Name : NB_ADJ_BSC_INC_HO_REQ Counter Integer
SFD reference : 3BK 10204 0411 DSZZA ("Traffic Flow Measurements") Length: 4
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Sub domain-2:
Counter definition:
Number of incoming 2G to 2G external or internal inter-cell SDCCH or TCH (in HR or FR usage) handover
requests. The internal and external directed retries are counted.
Trigger condition:
1) Internal handover : whenever an internal inter-cell SDCCH or TCH handover is initiated by the handover
process
within the BSC from the serving cell to the target cell.
2) External handover : 48.008 HANDOVER REQUEST received (including the MIE "Cell identifier" of the serving
cell) by the BSC for an SDCCH or TCH external handover towards the target cell.

External comment:
--
Alcatel-Lucent
Counter Name : NB_ADJ_BSC_INC_HO_ATPT Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Sub domain-2:
Counter definition:
Number of incoming 2G to 2G external or internal inter cell SDCCH or TCH (in HR or FR usage) handover
attempts. The internal and external directed retries are counted.
Trigger condition:
1) Internal handover : 44.018 HANDOVER COMMAND sent to the MS via the serving cell for an internal inter-cell
SDCCH or TCH handover towards the target cell.
2) External handover : 48.008 HANDOVER REQUEST ACK sent to the MSC from the target BSC for an external
SDCCH or TCH handover from the serving cell to the target cell. The MIE "Cell-Identifier" of the serving
cell&target
cell are provided in 48.008 HANDOVER REQUEST.

External comment:
--
Alcatel-Lucent
Counter Name : NB_ADJ_BSC_INC_HO_SUCC Counter Integer
B10 Adjacency-CGI 1
B8 Adjacency 0
B9 Adjacency-CGI 1
Sub domain-2:
Counter definition:
Number of incoming 2G to 2G external or internal inter cell SDCCH or TCH (in HR or FR usage) handover
successes. The internal and external directed retries are counted.
Trigger condition:
44.018HANDOVER_COMPLETE message received from the MS via the target cell for an external or internal
inter-cell SDCCH or TCH handover from the serving cell.

External comment:
--
Alcatel-Lucent
ANNEX
Block layout
The information given in this report is complementary to the
information given in the "OMC-BSS file format specification"
document (3BK 11204 0321 DSZZA).
Details on blocks of observations and RMS (i.e. types 10 to 15 and 31)
can be found in the OMC-BSC file format specification.
The block length indicated here corresponds to the sum of the Entity
Selector Size and the size of the counter block.
Type 1 Traffic measurements
Block Number 11 Entity Selector Size: 2 Block Length 224
Status Offset Short Name Name Length
0 C01 NB_IMM_ASS_SUCC_MT 4
4 C02 NB_IMM_ASS_SUCC_MO 4
8 C04 NB_IMM_ASS_PREP_FAIL_CONG 4
12 C07 NB_SDCCH_DROP_OUT_HO 4
16 C10 NB_INC_SDCCH_HO_SUCC 4
20 C137 NB_SDCCH_DROP_EST_PHAS_BSS_PB 4
24 C138 NB_SDCCH_DROP_EST_PHAS_RLF 4
28 C14a NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB 4
32 C14c NB_TCH_DROP_EST_PHAS_BSS_PB 4
36 C147 NB_INC_SDCCH_HO_ALLOC 4
40 C148 NB_IMM_ASS_ALLOC 4
44 C149 NB_IMM_ASS_EXEC_FAIL_RADIO 4
48 C850 NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL 4
52 C02a NB_IMM_ASS_SUCC_MO_LOC_UPD 4
56 C02b NB_IMM_ASS_SUCC_MO_SMS 4
60 C02c NB_IMM_ASS_SUCC_MO_SUP_SERV 4
64 C02d NB_IMM_ASS_SUCC_MO_FOLLOW_ON 4
68 C02e NB_IMM_ASS_SUCC_MO_CM_REEST 4
72 C02f NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW 4
76 C02g NB_IMM_ASS_SUCC_MO_IMSI_DETACH 4
80 C02h NB_IMM_ASS_SUCC_MO_CALL_EST 4
Alcatel-Lucent
84 C442 NB_TIMES_TRAF_DETECTED_HIGH 4
88 C443 NB_TIMES_TRAF_DETECTED_LOW 4
92 C03 NB_OUT_SDCCH_HO_SUCC 4
96 C13a NB_TCH_NOR_ASS_QUEUED 4
100 C13b NB_INC_EXT_TCH_HO_QUEUED 4
104 C15a NB_INC_IDR_ALLOC 4
108 C15b NB_INC_TCH_HO_ALLOC 4
112 C812 NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS 4
116 C612a NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE 4
120 C612b NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL 4
124 C612c NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP 4
128 C612d NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ 4
132 C161a NB_DTAP_MO_NOR_ASS_SUCC 4
136 C161b NB_DTAP_MT_NOR_ASS_SUCC 4
140 C162a NB_TCH_DROP_DTAP_EST_PHAS_RLF 4
144 C162b NB_TCH_DROP_DTAP_EST_PHAS_BSS_PB 4
148 C162c NB_TCH_DROP_DTAP_EST_PHAS_REM_TRANS_FAIL 4
152 C170 NB_CALL_TFO 4
156 C171 NB_TFO_CODEC_REQ 4
160 C701a NB_TCH_FR_REQ 4
164 C701b NB_TCH_DR_REQ 4
168 C701c NB_TCH_DR_EFR_REQ 4
172 C701d NB_TCH_AMR_REQ 4
176 C701e NB_TCH_DATA_REQ 4
180 C702a NB_TCH_NOR_FR_ALLOC 4
184 C702b NB_TCH_NOR_HR_ALLOC 4
188 C702c NB_TCH_NOR_EFR_ALLOC 4
192 C704a NB_TCH_NOR_AMR_FR_ALLOC 4
196 C704b NB_TCH_NOR_AMR_HR_ALLOC 4
200 C705 NB_TCH_NOR_DATA_ALLOC 4
204 C706 NB_EGSM_MS_ACCESS_EXCEPT_LU 4
208 C901 NB_Suspend_Resume_req 4
212 C902 Nb_Suspend_fail 4
Alcatel-Lucent
216 C903 Nb_Suspend_succ 4
220 C02i NB_IMM_ASS_SUCC_MO_LCS 4
0 C621 NB_TCH_DROP_OUT_HO_EXEC_TRX 2
2 C703 NB_TCH_NOR_ASS_ALLOC_TRX 2
4 C710 NB_TCH_OUT_HO_REQ_TRX 2
6 C711 NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX 2
8 C712 NB_TCH_OUT_HO_SUCC_TRX 2
10 C713 NB_TCH_OUT_HO_FAIL_REV_TRX 2
12 C714 NB_TCH_OUT_HO_FAIL_NO_REV_TRX 2
14 C717a NB_INC_IDR_SUCC_TRX 2
16 C717b NB_INC_TCH_HO_SUCC_TRX 2
18 C718 NB_TCH_NOR_ASS_SUCC_TRX 2
20 C736 NB_TCH_DROP_EST_PHAS_RLF_TRX 2
22 C739 NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX 2
24 C746b NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX 2
Type 2 Resource availability measurements
0 C24 AV_NB_NOT_AVAIL_TRX_TS 2
2 C250 AV_NB_AVAIL_TCH 2
4 C26 AV_NB_AVAIL_SDCCH 2
6 C320a AV_NB_IDLE_TCH_INTERF_BAND1 2
8 C320b AV_NB_IDLE_TCH_INTERF_BAND2 2
10 C320c AV_NB_IDLE_TCH_INTERF_BAND3 2
12 C320d AV_NB_IDLE_TCH_INTERF_BAND4 2
14 C320e AV_NB_IDLE_TCH_INTERF_BAND5 2
16 C27 AV_NB_AVAIL_CCCH 2
18 C28a AV_NB_BUSY_CS_TS 2
20 C29a NB_MAX_SIMUL_BUSY_CS_TS 2
22 C30 AV_NB_BUSY_SDCCH 2
Alcatel-Lucent
24 C31 NB_MAX_SIMUL_BUSY_SDCCH 2
26 C34 TIME_ALL_AVAIL_TRX_TS_BUSY 2
28 C803 TIME_SDCCH_CONGESTION 2
30 C141 AV_NB_TCH_QUEUED 2
Type 3 Resource usage on CCCH channel
0 C8c NB_CHAN_REQD 4
4 C8b NB_IMM_ASS_CMD 4
8 C8a NB_PAGING_CMD 4
12 C8d NB_IMM_ASS_REJ 4
Type 4 Resource usage on SDCCH channel
0 C39 NB_TIMES_SDCCH_BUSY 4
4 C40 TIME_SDCCH_BUSY 4
Type 5 Resource usage on TCH channel
0 C370a NB_TCH_FR_ALLOC 4
4 C370b NB_TCH_HR_ALLOC 4
8 C380a TIME_FR_TCH_BUSY 4
12 C380b TIME_HR_TCH_BUSY 4
16 C381a TIME_FR_TCH_BUSY_BY_MULTIBAND_MS 4
20 C381b TIME_HR_TCH_BUSY_BY_MULTIBAND_MS 4
Type 6 TCH handover measurements
0 C42 NB_INC_EXT_TCH_HO_SUCC 4
4 C43 NB_INC_EXT_TCH_HO_EXEC_FAIL_MS_ACCESS 2
Alcatel-Lucent
6 C541 NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS 2
8 C46 NB_OUT_EXT_TCH_HO_SUCC 4
12 C45a NB_OUT_EXT_TCH_REAL_HO_REQ 4
16 C48 NB_OUT_EXT_TCH_HO_EXEC_FAIL_NO_REV 2
18 C47 NB_OUT_EXT_TCH_HO_EXEC_FAIL_REV 2
20 C56 NB_OUT_INT_TCH_HO_SUCC 4
24 C57 NB_OUT_INT_TCH_HO_EXEC_FAIL_REV 2
26 C58 NB_OUT_INT_TCH_HO_EXEC_FAIL_NO_REV 2
28 C55a NB_OUT_INT_TCH_HO_REQ 4
32 C551 NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS 2
34 C52 NB_INC_INT_TCH_HO_SUCC 4
38 C53 NB_INC_INT_TCH_HO_EXEC_FAIL_MS_ACCESS 2
40 C561 NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS 2
42 C62 NB_INTRA_TCH_HO_SUCC 4
46 C63 NB_INTRA_TCH_HO_EXEC_FAIL_NO_REV 2
48 C67 NB_INTRA_TCH_HO_EXEC_FAIL_REV 2
50 C470 NB_TCH_HO_ATPT_2_TooLowQualUp 4
54 C471 NB_TCH_HO_ATPT_3_TooLowLevUp 4
58 C472 NB_TCH_HO_ATPT_4_TooLowQualDown 4
62 C473 NB_TCH_HO_ATPT_5_TooLowLevDown 4
66 C474 NB_TCH_HO_ATPT_6_TooLongDistance 4
70 C75 NB_TCH_HO_MSC_TRIG 4
74 C476 NB_TCH_HO_ATPT_15_TooHighLevInterfUp 4
78 C477 NB_TCH_HO_ATPT_16_TooHighLevInterfDown 4
82 C478 NB_TCH_HO_ATPT_12_TooLowPowBudg 4
86 C585a NB_TCH_HO_ATPT_7_ConsBadSACCHmicroCell 4
90 C585d NB_TCH_HO_ATPT_17_TooLowLevUpMicroCell 4
94 C585e NB_TCH_HO_ATPT_18_TooLowLevDownMicroCell 4
98 C585f NB_TCH_HO_ATPT_14_HighLevNeigLowCellSlowMS 4
102 C541a NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS 2
104 C41b NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH 2
106 C586a NB_TCH_HO_ATPT_10_TooLowLevUpInZone 4
110 C586b NB_TCH_HO_ATPT_11_TooLowLevDownInZone 4
Alcatel-Lucent
114 C586c NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone 4
118 C479 NB_TCH_HO_ATPT_21_HighLevNeigCellPrefBand 4
122 C50 NB_OUT_EXT_TCH_HO_ATPT 4
126 C60 NB_OUT_INT_TCH_HO_ATPT 4
130 C411 NB_OUT_INT_TCH_HO_IDR_IN_ZONE_REQ 4
134 C412 NB_OUT_INT_TCH_HO_IDR_IN_ZONE_EXEC_FAIL 2
136 C413 NB_TCH_NOR_ASS_INNER_ZONE_ALLOC 4
140 C440 NB_TCH_HO_ATPT_23_TrafHandover 4
144 C444 NB_TCH_HO_ATPT_24_GenCaptureHandover 4
148 C450 NB_TCH_HO_ATPT_22_TooShortDistance 4
152 C220 NB_INC_EXT_TCH_HO_REQ 4
156 C221 NB_INC_EXT_TCH_HO_ATPT 4
160 C230 NB_INC_INT_TCH_HO_REQ 4
164 C231 NB_INC_INT_TCH_HO_ATPT 4
168 C270 NB_INTRA_TCH_HO_REQ 4
172 C271 NB_INTRA_TCH_HO_ATPT 4
176 C447 NB_TCH_HO_ATPT_26_BadQualHR 4
180 C448 NB_TCH_HO_ATPT_27_GoodQualFR 4
184 C449 NB_TCH_HO_ATPT_28_FastTraffic 4
188 C460 NB_TCH_HO_ALLOC_EMERGENCY_PRES 4
192 C461 NB_TCH_HO_ATPT_29_TFO 4
Type 7 LapD measurements
0 L1.1 NB_LAPD_INFO_FRAME_SENT 4
4 L1.2 NB_LAPD_INFO_FRAME_REC 4
8 L1.15 NB_LAPD_INFO_FRAME_RESENT 4
12 L1.5 NB_LAPD_RNR_SENT 4
16 L1.6 NB_LAPD_RNR_REC 4
20 L1.12 NB_LAPD_CRC_ERROR 4
24 L1.16 TIME_LAPD_UNAVAIL 4
28 L1.17 NB_LAPD_EST 4
Alcatel-Lucent
32 L1.18 TIME_LAPD_CONG 4
Type 8 X25 measurements
0 X3.20 NB_X25_INC_CALL_SUCC_CLOSED 2
2 X3.21 NB_X25_OUT_CALL_SUCC_CLOSED 2
4 X3.22 NB_X25_INC_CALL_ABNORM_CLOSED 2
6 X3.23 NB_X25_OUT_CALL_ABNORM_CLOSED 2
Type 9 N7 measurements
0 N1.1 TIME_N7_ALIGNED 4
4 N1.2 NB_N7_LINK_FAIL_ANY_CAUSE 2
6 N1.3 NB_N7_LINK_FAIL_FIB_BSN 2
8 N1.4 NB_N7_LINK_FAIL_T7_EXP 2
10 N1.5 NB_N7_LINK_FAIL_SU_ERROR_RATE 2
12 N1.6 NB_N7_LINK_FAIL_CONG 2
14 N1.7 NB_N7_LINK_FAIL_ALIGNMENT 2
16 N1.10 NB_N7_CHANGEOVER 2
18 N1.11 NB_N7_CHANGEBACK 2
20 N1.12 NB_N7_RESTORATION 2
22 N2.7 TIME_N7_UNAVAIL_ERROR_SL 2
24 N2.9 TIME_N7_UNAVAIL_MSC_PROC_OUTAGE 2
26 N3.7 TIME_N7_UNAVAIL_CONG 2
28 N3.10 NB_N7_MSU_DISC_DUE_CONG 4
32 N3.11 NB_N7_CONG_WITH_MSU_LOST 2
34 N1.8 NB_N7_SU_REC_WITH_ERROR 4
38 N1.9 NB_N7_NEG_ACK_REC 4
42 N3.1 NB_N7_SIF_SIO_SENT 4
46 N3.2 NB_N7_OCTETS_RESENT 4
50 N3.3 NB_N7_MSU_SENT 4
54 N3.4 NB_N7_SIF_SIO_REC 4
Alcatel-Lucent
58 N3.5 NB_N7_MSU_REC 4
0 N4.2 TIME_N7_UNAVAIL_LINK_SET 4
Type 18 A interface measurements
0 C180a NB_N7_CLEAR_REQ_RadioIntMessFail 4
4 C180b NB_N7_CLEAR_REQ_O&Minterv 4
8 C180c NB_N7_CLEAR_REQ_EquipFail 4
12 C180d NB_N7_CLEAR_REQ_RadioIntFail 4
16 C180e NB_N7_CLEAR_REQ_NoRadioResAvail 4
20 C181a NB_N7_ASS_FAIL_RadioIntMessFail 4
24 C181b NB_N7_ASS_FAIL_O&Minterv 4
28 C181c NB_N7_ASS_FAIL_EquipFail 4
32 C181d NB_N7_ASS_FAIL_NoRadioResAvail 4
36 C181e NB_N7_ASS_FAIL_ReqTerResUnav/Alloc 4
40 C181f NB_N7_ASS_FAIL_ReqTrans/RateUnav 4
44 C181g NB_N7_ASS_FAIL_RadioIntFailRevOldChan 4
48 C181h NB_N7_ASS_FAIL_RadioIntFail 4
52 C181i NB_N7_ASS_FAIL_CipherAlgoNotSupp 4
56 C181j NB_N7_ASS_FAIL_BSSnotEquip 4
60 C181k NB_N7_ASS_FAIL_ProtocolError 4
64 C181l NB_N7_ASS_FAIL_ReqSpeechVersUnav 4
68 C182 NB_N7_CLEAR_REQ_EST_PHAS 4
0 C750 TIME_A_CHANNEL_BUSY 4
4 C751 NB_A_CHANNEL_ALLOC 4
Type 19 SMS PP measurements
Alcatel-Lucent
0 C190 NB_SMS_PP_CON_MO_SDCCH 4
4 C191 NB_SMS_PP_CON_MT_SDCCH 4
8 C192 NB_SMS_PP_CON_MO_SACCH 4
12 C193 NB_SMS_PP_CON_MT_SACCH 4
16 C194a NB_SMS_PP_CON_REJ_RadioIntFail 4
20 C194b NB_SMS_PP_CON_REJ_BSSnotEquip 4
24 C194c NB_SMS_PP_CON_REJ_ProtocolError 4
28 C195 NB_SMS_PP_CON_REL_LAPDM_ERROR 4
Type 25 SCCP measurements
0 C251 NB_N7_UNIT_DATA_SENT 4
4 C252 NB_N7_UNIT_DATA_REC 4
8 C253 NB_N7_CON_REQ_SENT 4
12 C254 NB_N7_CON_REQ_REC 4
16 C255 NB_N7_CON_CONF_SENT 4
20 C256 NB_N7_CON_CONF_REC 4
24 C257 NB_N7_CON_REF_SENT 4
28 C258 NB_N7_CON_REF_REC 4
32 C153a NB_N7_CON_EST_FAIL_DUE_NSS 4
36 C153b NB_N7_CON_EST_FAIL_DUE_BSS 4
Type 26 TCH outgoing handover per adjacency
0 C720 NB_ADJ_SCELL_OUT_TCH_HO_ATPT 2
2 C721 NB_ADJ_SCELL_OUT_TCH_HO_SUCC 2
4 C722 NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_REV 2
6 C723 NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_NO_REV 2
8 C724 NB_ADJ_SCELL_OUT_TCH_HO_EMERGENCY_ATPT 4
12 C725 NB_ADJ_SCELL_OUT_TCH_HO_BETTERCELL_ATPT 4
16 C727 NB_ADJ_SCELL_OUT_TCH_HO_TRAFFIC_ATPT 4
20 C728 NB_ADJ_SCELL_OUT_ FORCED_DR_ATPT 4
Alcatel-Lucent
Type 27 2G TCH incoming handover per
0 C730 NB_ADJ_TCELL_INC_TCH_HO_ATPT 2
2 C731 NB_ADJ_TCELL_INC_TCH_HO_SUCC 2
4 C733 NB_ADJ_TCELL_INC_TCH_HO_EXEC_FAIL_MS_ACC 2
6 C734 NB_ADJ_TCELL_INC_TCH_HO_EMERGENCY_ATPT 4
10 C735 NB_ADJ_TCELL_INC_TCH_HO_BETTERCELL_ATPT 4
14 C737 NB_ADJ_TCELL_INC_TCH_HO_TRAFFIC_ATPT 4
18 C738 NB_ADJ_TCELL_INC_FORCED_DR_ATPT 4
22 C753 NB_ADJ_TCELL_INC_TCH_HO_OTHER_ATPT 4
Type 28 SDCCH handover
0 C82 NB_INC_EXT_SDCCH_HO_SUCC 4
4 C83 NB_INC_EXT_SDCCH_HO_EXEC_FAIL_MS_ACCESS 2
6 C81 NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG 2
8 C86 NB_OUT_EXT_SDCCH_HO_SUCC 4
12 C85a NB_OUT_EXT_SDCCH_REAL_HO_REQ 4
16 C88 NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_NO_REV 2
18 C87 NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_REV 2
20 C96 NB_OUT_INT_SDCCH_HO_SUCC 4
24 C97 NB_OUT_INT_SDCCH_HO_EXEC_FAIL_REV 2
26 C98 NB_OUT_INT_SDCCH_HO_EXEC_FAIL_NO_REV 2
28 C95a NB_OUT_INT_SDCCH_HO_REQ 4
32 C91 NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG 2
34 C92 NB_INC_INT_SDCCH_HO_SUCC 4
38 C93 NB_INC_INT_SDCCH_HO_EXEC_FAIL_MS_ACCESS 2
40 C101 NB_INTRA_SDCCH_HO_PREP_FAIL_CONG 2
42 C102 NB_INTRA_SDCCH_HO_SUCC 4
46 C103 NB_INTRA_SDCCH_HO_EXEC_FAIL_NO_REV 2
48 C107 NB_INTRA_SDCCH_HO_EXEC_FAIL_REV 2
Alcatel-Lucent
50 C510 NB_SDCCH_HO_ATPT_2_TooLowQualUp 4
54 C511 NB_SDCCH_HO_ATPT_3_TooLowLevUp 4
58 C512 NB_SDCCH_HO_ATPT_4_TooLowQualDown 4
62 C513 NB_SDCCH_HO_ATPT_5_TooLowLevDown 4
66 C514 NB_SDCCH_HO_ATPT_6_TooLongDistance 4
70 C115 NB_SDCCH_HO_MSC_TRIG 4
74 C516 NB_SDCCH_HO_ATPT_15_TooHighLevInterfUp 4
78 C517 NB_SDCCH_HO_ATPT_16_TooHighLevInterfDown 4
82 C518 NB_SDCCH_HO_ATPT_12_TooLowPowBudg 4
86 C605a NB_SDCCH_HO_ATPT_7_ConsBadSACCHmicroCell 4
90 C605d NB_SDCCH_HO_ATPT_17_TooLowLevUpMicroCell 4
94 C605e NB_SDCCH_HO_ATPT_18_TooLowLevDownMicroCell 4
98 C605f NB_SDCCH_HO_ATPT_14_HighLevNeigLowCellSlowMS 4
102 C607 NB_SDCCH_HO_ATPT_20_HighLevNeigCellForcDR 4
106 C519 NB_SDCCH_HO_ATPT_21_HighLevNeigCellPrefBand 4
110 C90 NB_OUT_EXT_SDCCH_HO_ATPT 4
114 C100 NB_OUT_INT_SDCCH_HO_ATPT 4
118 C445 NB_SDCCH_HO_ATPT_23_TrafHandover 4
122 C446 NB_SDCCH_HO_ATPT_24_GenCaptureHandover 4
126 C454 NB_SDCCH_HO_ATPT_22_TooShortDistance 4
130 C310 NB_INC_EXT_SDCCH_HO_REQ 4
134 C311 NB_INC_EXT_SDCCH_HO_ATPT 4
138 C330 NB_INC_INT_SDCCH_HO_REQ 4
142 C331 NB_INC_INT_SDCCH_HO_ATPT 4
146 C360 NB_INTRA_SDCCH_HO_REQ 4
150 C361 NB_INTRA_SDCCH_HO_ATPT 4
Type 29 Directed retry measurements
0 C142a NB_OUT_FORCED_IDR_SUCC 4
4 C142b NB_OUT_FORCED_EDR_SUCC 4
8 C142c NB_OUT_NOR_IDR_SUCC 4
Alcatel-Lucent
12 C142d NB_OUT_NOR_EDR_SUCC 4
16 C143a NB_OUT_FORCED_IDR_EXEC_FAIL_REV 2
18 C143b NB_OUT_FORCED_IDR_EXEC_FAIL_NO_REV 2
20 C143c NB_OUT_FORCED_EDR_EXEC_FAIL_REV 2
22 C143d NB_OUT_FORCED_EDR_EXEC_FAIL_NO_REV 2
24 C143e NB_OUT_NOR_IDR_EXEC_FAIL_REV 2
26 C143f NB_OUT_NOR_IDR_EXEC_FAIL_NO_REV 2
28 C143g NB_OUT_NOR_EDR_EXEC_FAIL_REV 2
30 C143h NB_OUT_NOR_EDR_EXEC_FAIL_NO_REV 2
32 C144a NB_OUT_FORCED_IDR_REQ 4
36 C144b NB_OUT_FORCED_EDR_REQ 4
40 C144c NB_OUT_NOR_IDR_REQ 4
44 C144d NB_OUT_NOR_EDR_REQ 4
48 C145a NB_OUT_FORCED_IDR_ATPT 4
52 C145b NB_OUT_FORCED_EDR_ATPT 4
56 C145c NB_OUT_NOR_IDR_ATPT 4
60 C145d NB_OUT_NOR_EDR_ATPT 4
64 C151 NB_INC_IDR_SUCC (29) 4
68 C152 NB_INC_IDR_EXEC_FAIL_MS_ACCESS 2
70 C153 NB_INC_IDR_REQ 4
74 C154 NB_INC_IDR_ATPT 4
78 C555 NB_INC_IDR_PREP_FAIL_CONG_R_ABIS 2
Type 30 SMS CB measurements
0 CB601 NB_SMSCB_WRITE_REPL_SUCC 4
4 CB602 NB_SMSCB_KILL_MESS_SUCC 4
8 CB603 NB_SMS_CB_FAIL_IND 2
10 CB604 NB_SMS_CB_WRITE_REP_KILL_MESS_REJ 2
Type 32 Change of frequency band
Alcatel-Lucent
0 C403a NB_INC_EXT_TCH_HO_NEW_BAND_ATPT 4
4 C403b NB_INC_EXT_TCH_HO_NEW_BAND_SUCC 4
8 C404a NB_OUT_EXT_TCH_HO_NEW_BAND_ATPT 4
12 C404b NB_OUT_EXT_TCH_HO_NEW_BAND_SUCC 4
16 C420a NB_INC_INT_TCH_HO_NEW_BAND_ATPT 4
20 C420b NB_INC_INT_TCH_HO_NEW_BAND_SUCC 4
24 C421a NB_OUT_INT_TCH_HO_NEW_BAND_ATPT 4
28 C421b NB_OUT_INT_TCH_HO_NEW_BAND_SUCC 4
Type 33 Electro-Magnetic Emission counters
0 E01 EME_PWR_GSM 2
2 E02 EME_PWR_DCS 2
Type 34 Voice Group Call Services
0 V11 NB_TALKER_CHANGE_VGCS 2
2 V17 NB_VGCS_ESTABLISHED 2
0 V01 NB_PTP_CALL_PREEMPTED_VGCS 2
2 V021 AV_PARALLEL_TCH_VGCS 2
4 V022 MAX_PARALLEL_TCH_VGCS 2
6 V03 NB_VGCS_ESTABLISHMENT_REQ 2
8 V04 NB_VGCS_ESTABLISHMENT_SUCC 2
10 V05 NB_CM_SERV_REQ_VGCS 2
12 V06 NB_VGC_RELEASED_VGCS 2
14 V07 NB_OUT_VGCS_HO_ATPT 2
16 V08 NB_OUT_VGCS_HO_SUCC 2
18 V09 NB_INC_VGCS_HO_SUCC 2
20 V10 NB_INC_VGCS_HO_ATPT 2
22 V12 NB_VGC_BLOCKED_VGCS 2
Alcatel-Lucent
24 V13 NB_VGCS_NOTIFIFICATION_FACCH 2
26 V14 NB_ASS_REQ_ABLE_PREEMT 2
28 V15 NB_VGCS_ASS_REQ_ABLE_TO_PREEMPT 2
30 V16 NB_VGCS_QUEUED 2
32 V18 NB_PREEMTED_TCH_VGCS 2
34 V19 NB_PAGING_FACCH 2
36 V20 VGCS20 2
Type 110 Overview measurements
0 MC01 NB_IMM_ASS_SUCC_MT 4
4 MC02 NB_IMM_ASS_SUCC_MO 4
8 MC02a NB_IMM_ASS_SUCC_MO_LOC_UPD 4
12 MC02b NB_IMM_ASS_SUCC_MO_SMS 4
16 MC02c NB_IMM_ASS_SUCC_MO_SUP_SERV 4
20 MC02d NB_IMM_ASS_SUCC_MO_FOLLOW_ON 4
24 MC02e NB_IMM_ASS_SUCC_MO_CM_REEST 4
28 MC02f NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW 4
32 MC02g NB_IMM_ASS_SUCC_MO_IMSI_DETACH 4
36 MC02h NB_IMM_ASS_SUCC_MO_CALL_EST 4
40 MC03 NB_OUT_SDCCH_HO_SUCC 4
44 MC04 NB_IMM_ASS_PREP_FAIL_CONG 4
48 MC07 NB_SDCCH_DROP_OUT_HO 4
52 MC10 NB_INC_SDCCH_HO_SUCC 4
56 MC13a NB_TCH_NOR_ASS_QUEUED 4
60 MC13b NB_INC_EXT_TCH_HO_QUEUED 4
64 MC14a NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB 4
68 MC14c NB_TCH_DROP_EST_PHAS_BSS_PB 4
72 MC15a NB_INC_IDR_ALLOC 4
76 MC15b NB_INC_TCH_HO_ALLOC 4
80 MC137 NB_SDCCH_DROP_EST_PHAS_BSS_PB 4
84 MC138 NB_SDCCH_DROP_EST_PHAS_RLF 4
Alcatel-Lucent
88 MC147 NB_INC_SDCCH_HO_ALLOC 4
92 MC148 NB_IMM_ASS_ALLOC 4
96 MC149 NB_IMM_ASS_EXEC_FAIL_RADIO 4
100 MC24 AV_NB_NOT_AVAIL_TRX_TS 2
102 MC27 AV_NB_AVAIL_CCCH 2
104 MC141 AV_NB_TCH_QUEUED 2
106 MC8a NB_CELL_PAGING_CMD 4
110 MC8b NB_CELL_IMM_ASS_CMD 4
114 MC8c NB_CELL_CHAN_REQD 4
118 MC8d NB_CELL_IMM_ASS_REJ 4
122 MC541a NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS 2
124 MC41b NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH 2
126 MC586a NB_TCH_HO_ATPT_10_TooLowLevUpInZone 4
130 MC586b NB_TCH_HO_ATPT_11_TooLowLevDownInZone 4
134 MC586c NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone 4
138 MC142e NB_OUT_IDR_SUCC 4
142 MC142f NB_OUT_EDR_SUCC 4
146 MC144e NB_OUT_IDR_REQ 4
150 MC144f NB_OUT_EDR_REQ 4
154 MC850 NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL 4
158 MC151 NB_INC_IDR_SUCC (29) 4
162 MC153 NB_INC_IDR_REQ 4
166 MC555 NB_INC_IDR_PREP_FAIL_CONG_R_ABIS 2
168 MC196 NB_SMS_PP_CON_SUCC 4
172 MC197 NB_SMS_PP_CON_FAIL 4
176 MC170 NB_CALL_TFO 4
180 MC461 NB_TCH_HO_ATPT_29_TFO 4
184 MC921a NB_TCH_NOR_ASS_HO_REQ_ABLE_TO_PREEMPT 2
186 MC921b NB_PREEMPT_CAP_ALLOC_SUCC 2
188 MC921c NB_PREEMPTED_CALLS 2
190 MC921d NB_PREEMPT_CAP_OUT_DR_ALLOC_SUCC 2
192 MC921e NB_TCH_NOR_ASS_HO_SUCC_PREEMPTABLE 2
Alcatel-Lucent
0 MC607 NB_SDCCH_HO_20_HighLevNeigCellForcDR 4
4 MC812 NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS 4
8 MC612a NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE 4
12 MC612b NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL 4
16 MC612c NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP 4
20 MC612d NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ 4
24 MC541 NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS 2
26 MC81 NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG 2
28 MC642 NB_INC_EXT_HO_SUCC 4
32 MC643 NB_INC_EXT_HO_EXEC_FAIL_MS_ACCESS 2
34 MC645a NB_OUT_EXT_REAL_HO_REQ 4
38 MC646 NB_OUT_EXT_HO_SUCC 4
42 MC647 NB_OUT_EXT_HO_EXEC_FAIL_REV 2
44 MC648 NB_OUT_EXT_HO_EXEC_FAIL_NO_REV 2
46 MC650 NB_OUT_EXT_HO_ATPT 4
50 MC551 NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS 2
52 MC91 NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG 2
54 MC652 NB_INC_INT_HO_SUCC 4
58 MC653 NB_INC_INT_HO_EXEC_FAIL_MS_ACCESS 2
60 MC655a NB_OUT_INT_HO_REQ 4
64 MC656 NB_OUT_INT_HO_SUCC 4
68 MC657 NB_OUT_INT_HO_EXEC_FAIL_REV 2
70 MC658 NB_OUT_INT_HO_EXEC_FAIL_NO_REV 2
72 MC660 NB_OUT_INT_HO_ATPT 4
76 MC561 NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS 2
78 MC101 NB_INTRA_SDCCH_HO_PREP_FAIL_CONG 2
80 MC662 NB_INTRA_HO_SUCC 4
84 MC663 NB_INTRA_HO_EXEC_FAIL_NO_REV 2
86 MC667 NB_INTRA_HO_EXEC_FAIL_REV 2
88 MC670 NB_HO_2_TooLowQualUp 4
92 MC671 NB_HO_3_TooLowLevUp 4
Alcatel-Lucent
96 MC672 NB_HO_4_TooLowQualDown 4
100 MC673 NB_HO_5_TooLowLevDown 4
104 MC674 NB_HO_6_TooLongDistance 4
108 MC675 NB_HO_MSC_TRIG 4
112 MC676 NB_HO_15_TooHighLevInterfUp 4
116 MC677 NB_HO_16_TooHighLevInterfDown 4
120 MC678 NB_HO_12_TooLowPowBudg 4
124 MC679 NB_HO_21_HighLevNeigCellPrefBand 4
128 MC706 NB_EGSM_MS_ACCESS_EXCEPT_LU 4
132 MC785a NB_HO_7_ConsBadSACCHmicroCell 4
136 MC785d NB_HO_17_TooLowLevUpMicroCell 4
140 MC785e NB_HO_18_TooLowLevDownMicroCell 4
144 MC785f NB_HO_14_HighLevNeigLowCellSlowMS 4
148 MC820 NB_INC_EXT_HO_REQ 4
152 MC320a AV_NB_IDLE_TCH_INTERF_BAND1 2
154 MC320b AV_NB_IDLE_TCH_INTERF_BAND2 2
156 MC320c AV_NB_IDLE_TCH_INTERF_BAND3 2
158 MC320d AV_NB_IDLE_TCH_INTERF_BAND4 2
160 MC320e AV_NB_IDLE_TCH_INTERF_BAND5 2
162 MC821 NB_INC_EXT_HO_ATPT 4
166 MC250 AV_NB_AVAIL_TCH 2
168 MC26 AV_NB_AVAIL_SDCCH 2
170 MC28a AV_NB_BUSY_CS_TS 2
172 MC29a NB_MAX_SIMUL_BUSY_CS_TS 2
174 MC830 NB_INC_INT_HO_REQ 4
178 MC831 NB_INC_INT_HO_ATPT 4
182 MC34 TIME_ALL_AVAIL_TRX_TS_BUSY 2
184 MC31 NB_MAX_SIMUL_BUSY_SDCCH 2
186 MC870 NB_INTRA_HO_REQ 4
190 MC871 NB_INTRA_HO_ATPT 4
194 MC803 TIME_SDCCH_CONGESTION 2
196 MC1040 NB_HO_ATPT_23_TrafHandover 4
200 MC1044 NB_HO_ATPT_24_gencapture 4
Alcatel-Lucent
204 MC1050 NB_HO_22_TooShortDistance 4
208 MC161 NB_DTAP_NOR_ASS_SUCC 4
212 MC162 NB_TCH_DROP_DTAP_EST_PHAS 4
0 MC448a NB_TCH_HO_ATPT_26_BadQualHR 4
4 MC448b NB_TCH_HO_ATPT_27_GoodQualFR 4
8 MC449 NB_TCH_HO_ATPT_28_FastTraffic 4
12 MC701a NB_TCH_FR_REQ 4
16 MC701b NB_TCH_DR_REQ 4
20 MC701c NB_TCH_DR_EFR_REQ 4
24 MC701d NB_TCH_AMR_REQ 4
28 MC701e NB_TCH_DATA_REQ 4
32 MC702a NB_TCH_NOR_FR_ALLOC 4
36 MC702b NB_TCH_NOR_HR_ALLOC 4
40 MC702c NB_TCH_NOR_EFR_ALLOC 4
44 MC704a NB_TCH_NOR_AMR_FR_ALLOC 4
48 MC704b NB_TCH_NOR_AMR_HR_ALLOC 4
52 MC705 NB_TCH_NOR_DATA_ALLOC 4
56 MC901 NB_Suspend_Resume_req 4
60 MC902 Nb_Suspend_fail 4
64 MC903 Nb_Suspend_succ 4
68 MC140a NB_TCH_NOR_ASS_REQ 4
72 MC140b NB_TCH_NOR_ASS_ATPT 4
76 MC460a NB_TCH_EMERGENCY_HO_PRESERVATION 4
80 MC922a NB_INC_EXT_3G_2G_HO_REQ 4
84 MC922b NB_INC_EXT_3G_2G_HO_SUCC 4
88 MC922c NB_INC_EXT_3G_2G_HO_EXEC_FAIL_MS_ACC 4
92 MC922d NB_INC_EXT_3G_2G_HO_ATPT 4
96 MC800 AV_NB_AVAIL_DYN_TS 2
98 MC801a AV_NB_BUSY_DYN_TCH 2
100 MC801b MAX_NB_BUSY_DYN_TCH 2
102 MC802a AV_NB_BUSY_DYN_SDCCH 2
Alcatel-Lucent
104 MC802b MAX_NB_BUSY_DYN_SDCCH 2
106 MC804a NB_UL_SINGLE_BLOCK_SIG_RACH 4
110 MC804b NB_UL_ONE_PHASE_SIG_RACH 4
114 MC805a NB_CHANNEL_ASSIGN_DL_AGCH 4
118 MC805b NB_CHANNEL_ASSIGN_DL_PCH 4
122 MC923a NB_LCS_REQ 4
126 MC923b NB_LCS_SUCC 4
130 MC923c NB_LCS_FAIL_LB 4
134 MC923d NB_LCS_ABORT 4
138 MC02i NB_IMM_ASS_SUCC_MO_LCS 4
142 MC462a NB_OUT_INTER_PLMN_TCH_HO_REQ 2
144 MC462b NB_OUT_INTER_PLMN_TCH_HO_ATPT 2
146 MC462c NB_OUT_INTER_PLMN_TCH_HO_SUCC 2
148 MC463a NB_INC_INTER_PLMN_TCH_HO_REQ 2
150 MC463b NB_INC_INTER_PLMN_TCH_HO_ATPT 2
152 MC463c NB_INC_INTER_PLMN_TCH_HO_SUCC 2
154 MC922e NB_INC_EXT_TCH_3G_2G_HO_EMERGENCY_REQ 2
156 MC922f NB_INC_EXT_TCH_3G_2G_HO_REQ 2
158 MC922g NB_INC_EXT_TCH_3G_2G_HO_PREP_FAIL_3GCONG 2
160 MC922h TIME_3G_HOReject_HL 2
162 MC480 NB_TCH_HO_REQ_30_ReturnCSZone 2
164 MC481 NB_TCH_HO_ATPT_30_ReturnCSZone 2
166 MC924a TIME_SPDCH_LIMIT_HIGH_LOAD 2
168 MC924b NB_OUT_2G_3G_HO_REQ 2
170 MC924c NB_OUT_2G_3G_HO_SUCC 2
172 MC924d NB_OUT_2G_3G_HO_ATPT 2
174 MC924e NB_OUT_2G_3G_HO_EXEC_FAIL_NO_REV 2
176 MC924f NB_OUT_2G_3G_HO_EXEC_FAIL_REV 2
178 MC924g NB_OUT_2G_3G_HO_PREP_FAIL 2
180 MC924h NB_2G_3G_HO_8 2
182 MC924i NB_2G_3G_HO_9 2
184 MC924j NB_2G_3G_HO_10 2
186 MC924k NB_2G_3G_HO_11 2
Alcatel-Lucent
1 MC621 NB_TCH_DROP_OUT_HO_EXEC_TRX 2
3 MC703 NB_TCH_NOR_ASS_ALLOC_TRX 2
5 MC710 NB_TCH_OUT_HO_REQ_TRX 2
7 MC711 NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX 2
9 MC712 NB_TCH_OUT_HO_SUCC_TRX 2
11 MC713 NB_TCH_OUT_HO_FAIL_REV_TRX 2
13 MC714 NB_TCH_OUT_HO_FAIL_NO_REV_TRX 2
15 MC717a NB_INC_IDR_SUCC_TRX 2
17 MC717b NB_INC_TCH_HO_SUCC_TRX 2
19 MC718 NB_TCH_NOR_ASS_SUCC_TRX 2
21 MC736 NB_TCH_DROP_EST_PHAS_RLF_TRX 2
23 MC739 NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX 2
25 MC746b NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX 2
27 MC370a NB_TRX_FR_ALLOC 6
33 MC370b NB_TRX_HR_ALLOC 6
39 MC380a TIME_TRX_FR_BUSY 6
45 MC380b TIME_TRX_HR_BUSY 6
51 MC380c TIME_TRX_GSM_FR_BUSY 6
57 MC380d TIME_TRX_GSM_HR_BUSY 6
63 MC380e TIME_TRX_DCS_FR_BUSY 6
69 MC380f TIME_TRX_DCS_HR_BUSY 6
75 MC381 TIME_TRX_TCH_BUSY_BY_MULTIBAND_MS 6
81 MC390 NB_TIMES_SDCCH_BUSY (110) 6
87 MC400 TIME_TRX_SDCCH_BUSY 6
0 MN1.1 TIME_N7_ALIGNED 4
4 MC350 NB_N7_CON_REQ 4
8 MC351 NB_N7_CON_CONF 4
Alcatel-Lucent
0 MC19 NB_TCH_NOR_ASS_HO_PREP_FAIL_ACHAN_MIS (110) 4
4 MC35 AV_NB_A_TRAF_CHAN_BLOCK_OUT_OF_SERV 4
8 MC36 AV_NB_AVAIL_A_TRAF_CHAN 4
Type 180 2G Traffic flow measurements
0 C400 NB_ADJ_BSC_INC_HO_REQ 4
4 C401 NB_ADJ_BSC_INC_HO_ATPT 4
8 C402 NB_ADJ_BSC_INC_HO_SUCC 4
C01 NB_IMM_ASS_SUCC_MT 1
C02 NB_IMM_ASS_SUCC_MO 1
C02a NB_IMM_ASS_SUCC_MO_LOC_UPD 1
C02b NB_IMM_ASS_SUCC_MO_SMS 1
C02c NB_IMM_ASS_SUCC_MO_SUP_SERV 1
C02d NB_IMM_ASS_SUCC_MO_FOLLOW_ON 1
C02e NB_IMM_ASS_SUCC_MO_CM_REEST 1
C02f NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW 1
C02g NB_IMM_ASS_SUCC_MO_IMSI_DETACH 1
C02h NB_IMM_ASS_SUCC_MO_CALL_EST 1
C02i NB_IMM_ASS_SUCC_MO_LCS 1
C03 NB_OUT_SDCCH_HO_SUCC 1
C04 NB_IMM_ASS_PREP_FAIL_CONG 1
C07 NB_SDCCH_DROP_OUT_HO 1
C10 NB_INC_SDCCH_HO_SUCC 1
C100 NB_OUT_INT_SDCCH_HO_ATPT 28
C101 NB_INTRA_SDCCH_HO_PREP_FAIL_CONG 28
C102 NB_INTRA_SDCCH_HO_SUCC 28
C103 NB_INTRA_SDCCH_HO_EXEC_FAIL_NO_REV 28
C107 NB_INTRA_SDCCH_HO_EXEC_FAIL_REV 28
C115 NB_SDCCH_HO_MSC_TRIG 28
C137 NB_SDCCH_DROP_EST_PHAS_BSS_PB 1
C138 NB_SDCCH_DROP_EST_PHAS_RLF 1
C13a NB_TCH_NOR_ASS_QUEUED 1
C13b NB_INC_EXT_TCH_HO_QUEUED 1
C141 AV_NB_TCH_QUEUED 2
C142a NB_OUT_FORCED_IDR_SUCC 29
Alcatel-Lucent
C142b NB_OUT_FORCED_EDR_SUCC 29
C142c NB_OUT_NOR_IDR_SUCC 29
C142d NB_OUT_NOR_EDR_SUCC 29
C143a NB_OUT_FORCED_IDR_EXEC_FAIL_REV 29
C143b NB_OUT_FORCED_IDR_EXEC_FAIL_NO_REV 29
C143c NB_OUT_FORCED_EDR_EXEC_FAIL_REV 29
C143d NB_OUT_FORCED_EDR_EXEC_FAIL_NO_REV 29
C143e NB_OUT_NOR_IDR_EXEC_FAIL_REV 29
C143f NB_OUT_NOR_IDR_EXEC_FAIL_NO_REV 29
C143g NB_OUT_NOR_EDR_EXEC_FAIL_REV 29
C143h NB_OUT_NOR_EDR_EXEC_FAIL_NO_REV 29
C144a NB_OUT_FORCED_IDR_REQ 29
C144b NB_OUT_FORCED_EDR_REQ 29
C144c NB_OUT_NOR_IDR_REQ 29
C144d NB_OUT_NOR_EDR_REQ 29
C145a NB_OUT_FORCED_IDR_ATPT 29
C145b NB_OUT_FORCED_EDR_ATPT 29
C145c NB_OUT_NOR_IDR_ATPT 29
C145d NB_OUT_NOR_EDR_ATPT 29
C147 NB_INC_SDCCH_HO_ALLOC 1
C148 NB_IMM_ASS_ALLOC 1
C149 NB_IMM_ASS_EXEC_FAIL_RADIO 1
C14a NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB 1
C14c NB_TCH_DROP_EST_PHAS_BSS_PB 1
C151 NB_INC_IDR_SUCC (29) 29
C152 NB_INC_IDR_EXEC_FAIL_MS_ACCESS 29
C153 NB_INC_IDR_REQ 29
C153a NB_N7_CON_EST_FAIL_DUE_NSS 25
C153b NB_N7_CON_EST_FAIL_DUE_BSS 25
C154 NB_INC_IDR_ATPT 29
C15a NB_INC_IDR_ALLOC 1
C15b NB_INC_TCH_HO_ALLOC 1
C161a NB_DTAP_MO_NOR_ASS_SUCC 1
C161b NB_DTAP_MT_NOR_ASS_SUCC 1
C162a NB_TCH_DROP_DTAP_EST_PHAS_RLF 1
C162b NB_TCH_DROP_DTAP_EST_PHAS_BSS_PB 1
C162c NB_TCH_DROP_DTAP_EST_PHAS_REM_TRANS_FAIL 1
C170 NB_CALL_TFO 1
Alcatel-Lucent
C171 NB_TFO_CODEC_REQ 1
C180a NB_N7_CLEAR_REQ_RadioIntMessFail 18
C180b NB_N7_CLEAR_REQ_O&Minterv 18
C180c NB_N7_CLEAR_REQ_EquipFail 18
C180d NB_N7_CLEAR_REQ_RadioIntFail 18
C180e NB_N7_CLEAR_REQ_NoRadioResAvail 18
C181a NB_N7_ASS_FAIL_RadioIntMessFail 18
C181b NB_N7_ASS_FAIL_O&Minterv 18
C181c NB_N7_ASS_FAIL_EquipFail 18
C181d NB_N7_ASS_FAIL_NoRadioResAvail 18
C181e NB_N7_ASS_FAIL_ReqTerResUnav/Alloc 18
C181f NB_N7_ASS_FAIL_ReqTrans/RateUnav 18
C181g NB_N7_ASS_FAIL_RadioIntFailRevOldChan 18
C181h NB_N7_ASS_FAIL_RadioIntFail 18
C181i NB_N7_ASS_FAIL_CipherAlgoNotSupp 18
C181j NB_N7_ASS_FAIL_BSSnotEquip 18
C181k NB_N7_ASS_FAIL_ProtocolError 18
C181l NB_N7_ASS_FAIL_ReqSpeechVersUnav 18
C182 NB_N7_CLEAR_REQ_EST_PHAS 18
C190 NB_SMS_PP_CON_MO_SDCCH 19
C191 NB_SMS_PP_CON_MT_SDCCH 19
C192 NB_SMS_PP_CON_MO_SACCH 19
C193 NB_SMS_PP_CON_MT_SACCH 19
C194a NB_SMS_PP_CON_REJ_RadioIntFail 19
C194b NB_SMS_PP_CON_REJ_BSSnotEquip 19
C194c NB_SMS_PP_CON_REJ_ProtocolError 19
C195 NB_SMS_PP_CON_REL_LAPDM_ERROR 19
C220 NB_INC_EXT_TCH_HO_REQ 6
C221 NB_INC_EXT_TCH_HO_ATPT 6
C230 NB_INC_INT_TCH_HO_REQ 6
C231 NB_INC_INT_TCH_HO_ATPT 6
C24 AV_NB_NOT_AVAIL_TRX_TS 2
C250 AV_NB_AVAIL_TCH 2
C251 NB_N7_UNIT_DATA_SENT 25
C252 NB_N7_UNIT_DATA_REC 25
C253 NB_N7_CON_REQ_SENT 25
C254 NB_N7_CON_REQ_REC 25
C255 NB_N7_CON_CONF_SENT 25
Alcatel-Lucent
C256 NB_N7_CON_CONF_REC 25
C257 NB_N7_CON_REF_SENT 25
C258 NB_N7_CON_REF_REC 25
C26 AV_NB_AVAIL_SDCCH 2
C27 AV_NB_AVAIL_CCCH 2
C270 NB_INTRA_TCH_HO_REQ 6
C271 NB_INTRA_TCH_HO_ATPT 6
C28a AV_NB_BUSY_CS_TS 2
C29a NB_MAX_SIMUL_BUSY_CS_TS 2
C30 AV_NB_BUSY_SDCCH 2
C31 NB_MAX_SIMUL_BUSY_SDCCH 2
C310 NB_INC_EXT_SDCCH_HO_REQ 28
C311 NB_INC_EXT_SDCCH_HO_ATPT 28
C320a AV_NB_IDLE_TCH_INTERF_BAND1 2
C320b AV_NB_IDLE_TCH_INTERF_BAND2 2
C320c AV_NB_IDLE_TCH_INTERF_BAND3 2
C320d AV_NB_IDLE_TCH_INTERF_BAND4 2
C320e AV_NB_IDLE_TCH_INTERF_BAND5 2
C330 NB_INC_INT_SDCCH_HO_REQ 28
C331 NB_INC_INT_SDCCH_HO_ATPT 28
C34 TIME_ALL_AVAIL_TRX_TS_BUSY 2
C360 NB_INTRA_SDCCH_HO_REQ 28
C361 NB_INTRA_SDCCH_HO_ATPT 28
C370a NB_TCH_FR_ALLOC 5
C370b NB_TCH_HR_ALLOC 5
C380a TIME_FR_TCH_BUSY 5
C380b TIME_HR_TCH_BUSY 5
C381a TIME_FR_TCH_BUSY_BY_MULTIBAND_MS 5
C381b TIME_HR_TCH_BUSY_BY_MULTIBAND_MS 5
C39 NB_TIMES_SDCCH_BUSY 4
C40 TIME_SDCCH_BUSY 4
C400 NB_ADJ_BSC_INC_HO_REQ 180
C401 NB_ADJ_BSC_INC_HO_ATPT 180
C402 NB_ADJ_BSC_INC_HO_SUCC 180
C403a NB_INC_EXT_TCH_HO_NEW_BAND_ATPT 32
C403b NB_INC_EXT_TCH_HO_NEW_BAND_SUCC 32
C404a NB_OUT_EXT_TCH_HO_NEW_BAND_ATPT 32
C404b NB_OUT_EXT_TCH_HO_NEW_BAND_SUCC 32
Alcatel-Lucent
C411 NB_OUT_INT_TCH_HO_IDR_IN_ZONE_REQ 6
C412 NB_OUT_INT_TCH_HO_IDR_IN_ZONE_EXEC_FAIL 6
C413 NB_TCH_NOR_ASS_INNER_ZONE_ALLOC 6
C41b NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH 6
C42 NB_INC_EXT_TCH_HO_SUCC 6
C420a NB_INC_INT_TCH_HO_NEW_BAND_ATPT 32
C420b NB_INC_INT_TCH_HO_NEW_BAND_SUCC 32
C421a NB_OUT_INT_TCH_HO_NEW_BAND_ATPT 32
C421b NB_OUT_INT_TCH_HO_NEW_BAND_SUCC 32
C43 NB_INC_EXT_TCH_HO_EXEC_FAIL_MS_ACCESS 6
C440 NB_TCH_HO_ATPT_23_TrafHandover 6
C442 NB_TIMES_TRAF_DETECTED_HIGH 1
C443 NB_TIMES_TRAF_DETECTED_LOW 1
C444 NB_TCH_HO_ATPT_24_GenCaptureHandover 6
C445 NB_SDCCH_HO_ATPT_23_TrafHandover 28
C446 NB_SDCCH_HO_ATPT_24_GenCaptureHandover 28
C447 NB_TCH_HO_ATPT_26_BadQualHR 6
C448 NB_TCH_HO_ATPT_27_GoodQualFR 6
C449 NB_TCH_HO_ATPT_28_FastTraffic 6
C450 NB_TCH_HO_ATPT_22_TooShortDistance 6
C454 NB_SDCCH_HO_ATPT_22_TooShortDistance 28
C45a NB_OUT_EXT_TCH_REAL_HO_REQ 6
C46 NB_OUT_EXT_TCH_HO_SUCC 6
C460 NB_TCH_HO_ALLOC_EMERGENCY_PRES 6
C461 NB_TCH_HO_ATPT_29_TFO 6
C47 NB_OUT_EXT_TCH_HO_EXEC_FAIL_REV 6
C470 NB_TCH_HO_ATPT_2_TooLowQualUp 6
C471 NB_TCH_HO_ATPT_3_TooLowLevUp 6
C472 NB_TCH_HO_ATPT_4_TooLowQualDown 6
C473 NB_TCH_HO_ATPT_5_TooLowLevDown 6
C474 NB_TCH_HO_ATPT_6_TooLongDistance 6
C476 NB_TCH_HO_ATPT_15_TooHighLevInterfUp 6
C477 NB_TCH_HO_ATPT_16_TooHighLevInterfDown 6
C478 NB_TCH_HO_ATPT_12_TooLowPowBudg 6
C479 NB_TCH_HO_ATPT_21_HighLevNeigCellPrefBand 6
C48 NB_OUT_EXT_TCH_HO_EXEC_FAIL_NO_REV 6
C50 NB_OUT_EXT_TCH_HO_ATPT 6
C510 NB_SDCCH_HO_ATPT_2_TooLowQualUp 28
Alcatel-Lucent
C511 NB_SDCCH_HO_ATPT_3_TooLowLevUp 28
C512 NB_SDCCH_HO_ATPT_4_TooLowQualDown 28
C513 NB_SDCCH_HO_ATPT_5_TooLowLevDown 28
C514 NB_SDCCH_HO_ATPT_6_TooLongDistance 28
C516 NB_SDCCH_HO_ATPT_15_TooHighLevInterfUp 28
C517 NB_SDCCH_HO_ATPT_16_TooHighLevInterfDown 28
C518 NB_SDCCH_HO_ATPT_12_TooLowPowBudg 28
C519 NB_SDCCH_HO_ATPT_21_HighLevNeigCellPrefBand 28
C52 NB_INC_INT_TCH_HO_SUCC 6
C53 NB_INC_INT_TCH_HO_EXEC_FAIL_MS_ACCESS 6
C541 NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS 6
C541a NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS 6
C551 NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS 6
C555 NB_INC_IDR_PREP_FAIL_CONG_R_ABIS 29
C55a NB_OUT_INT_TCH_HO_REQ 6
C56 NB_OUT_INT_TCH_HO_SUCC 6
C561 NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS 6
C57 NB_OUT_INT_TCH_HO_EXEC_FAIL_REV 6
C58 NB_OUT_INT_TCH_HO_EXEC_FAIL_NO_REV 6
C585a NB_TCH_HO_ATPT_7_ConsBadSACCHmicroCell 6
C585d NB_TCH_HO_ATPT_17_TooLowLevUpMicroCell 6
C585e NB_TCH_HO_ATPT_18_TooLowLevDownMicroCell 6
C585f NB_TCH_HO_ATPT_14_HighLevNeigLowCellSlowMS 6
C586a NB_TCH_HO_ATPT_10_TooLowLevUpInZone 6
C586b NB_TCH_HO_ATPT_11_TooLowLevDownInZone 6
C586c NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone 6
C60 NB_OUT_INT_TCH_HO_ATPT 6
C605a NB_SDCCH_HO_ATPT_7_ConsBadSACCHmicroCell 28
C605d NB_SDCCH_HO_ATPT_17_TooLowLevUpMicroCell 28
C605e NB_SDCCH_HO_ATPT_18_TooLowLevDownMicroCell 28
C605f NB_SDCCH_HO_ATPT_14_HighLevNeigLowCellSlowMS 28
C607 NB_SDCCH_HO_ATPT_20_HighLevNeigCellForcDR 28
C612a NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE 1
C612b NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL 1
C612c NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP 1
C612d NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ 1
C62 NB_INTRA_TCH_HO_SUCC 6
C621 NB_TCH_DROP_OUT_HO_EXEC_TRX 1
Alcatel-Lucent
C63 NB_INTRA_TCH_HO_EXEC_FAIL_NO_REV 6
C67 NB_INTRA_TCH_HO_EXEC_FAIL_REV 6
C701a NB_TCH_FR_REQ 1
C701b NB_TCH_DR_REQ 1
C701c NB_TCH_DR_EFR_REQ 1
C701d NB_TCH_AMR_REQ 1
C701e NB_TCH_DATA_REQ 1
C702a NB_TCH_NOR_FR_ALLOC 1
C702b NB_TCH_NOR_HR_ALLOC 1
C702c NB_TCH_NOR_EFR_ALLOC 1
C703 NB_TCH_NOR_ASS_ALLOC_TRX 1
C704a NB_TCH_NOR_AMR_FR_ALLOC 1
C704b NB_TCH_NOR_AMR_HR_ALLOC 1
C705 NB_TCH_NOR_DATA_ALLOC 1
C706 NB_EGSM_MS_ACCESS_EXCEPT_LU 1
C710 NB_TCH_OUT_HO_REQ_TRX 1
C711 NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX 1
C712 NB_TCH_OUT_HO_SUCC_TRX 1
C713 NB_TCH_OUT_HO_FAIL_REV_TRX 1
C714 NB_TCH_OUT_HO_FAIL_NO_REV_TRX 1
C717a NB_INC_IDR_SUCC_TRX 1
C717b NB_INC_TCH_HO_SUCC_TRX 1
C718 NB_TCH_NOR_ASS_SUCC_TRX 1
C720 NB_ADJ_SCELL_OUT_TCH_HO_ATPT 26
C721 NB_ADJ_SCELL_OUT_TCH_HO_SUCC 26
C722 NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_REV 26
C723 NB_ADJ_SCELL_OUT_TCH_HO_EXEC_FAIL_NO_REV 26
C724 NB_ADJ_SCELL_OUT_TCH_HO_EMERGENCY_ATPT 26
C725 NB_ADJ_SCELL_OUT_TCH_HO_BETTERCELL_ATPT 26
C727 NB_ADJ_SCELL_OUT_TCH_HO_TRAFFIC_ATPT 26
C728 NB_ADJ_SCELL_OUT_ FORCED_DR_ATPT 26
C730 NB_ADJ_TCELL_INC_TCH_HO_ATPT 27
C731 NB_ADJ_TCELL_INC_TCH_HO_SUCC 27
C733 NB_ADJ_TCELL_INC_TCH_HO_EXEC_FAIL_MS_ACC 27
C734 NB_ADJ_TCELL_INC_TCH_HO_EMERGENCY_ATPT 27
C735 NB_ADJ_TCELL_INC_TCH_HO_BETTERCELL_ATPT 27
C736 NB_TCH_DROP_EST_PHAS_RLF_TRX 1
C737 NB_ADJ_TCELL_INC_TCH_HO_TRAFFIC_ATPT 27
Alcatel-Lucent
C738 NB_ADJ_TCELL_INC_FORCED_DR_ATPT 27
C739 NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX 1
C746b NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX 1
C75 NB_TCH_HO_MSC_TRIG 6
C750 TIME_A_CHANNEL_BUSY 18
C751 NB_A_CHANNEL_ALLOC 18
C753 NB_ADJ_TCELL_INC_TCH_HO_OTHER_ATPT 27
C803 TIME_SDCCH_CONGESTION 2
C81 NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG 28
C812 NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS 1
C82 NB_INC_EXT_SDCCH_HO_SUCC 28
C83 NB_INC_EXT_SDCCH_HO_EXEC_FAIL_MS_ACCESS 28
C850 NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL 1
C85a NB_OUT_EXT_SDCCH_REAL_HO_REQ 28
C86 NB_OUT_EXT_SDCCH_HO_SUCC 28
C87 NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_REV 28
C88 NB_OUT_EXT_SDCCH_HO_EXEC_FAIL_NO_REV 28
C8a NB_PAGING_CMD 3
C8b NB_IMM_ASS_CMD 3
C8c NB_CHAN_REQD 3
C8d NB_IMM_ASS_REJ 3
C90 NB_OUT_EXT_SDCCH_HO_ATPT 28
C901 NB_Suspend_Resume_req 1
C902 Nb_Suspend_fail 1
C903 Nb_Suspend_succ 1
C91 NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG 28
C92 NB_INC_INT_SDCCH_HO_SUCC 28
C93 NB_INC_INT_SDCCH_HO_EXEC_FAIL_MS_ACCESS 28
C95a NB_OUT_INT_SDCCH_HO_REQ 28
C96 NB_OUT_INT_SDCCH_HO_SUCC 28
C97 NB_OUT_INT_SDCCH_HO_EXEC_FAIL_REV 28
C98 NB_OUT_INT_SDCCH_HO_EXEC_FAIL_NO_REV 28
CB601 NB_SMSCB_WRITE_REPL_SUCC 30
CB602 NB_SMSCB_KILL_MESS_SUCC 30
CB603 NB_SMS_CB_FAIL_IND 30
CB604 NB_SMS_CB_WRITE_REP_KILL_MESS_REJ 30
E01 EME_PWR_GSM 33
E02 EME_PWR_DCS 33
Alcatel-Lucent
HO1 SIGNALLING_TRAFFIC_IND 12
HO10100 RXLEV 14
HO1047 BSIC 12
HO1048 FREQ 12
HO1049 RXLEV 12
HO1098 BSIC 14
HO1099 FREQ 14
HO11 HO_CAUSE 12
HO1100 RXLEV 14
HO1101 SCRAMBLING_CODE 14
HO1102 FDD_FREQ 14
HO1103 AV_ECNO 14
HO111 SAMPLE_RATE 14
HO11100 RXLEV 14
HO1147 BSIC 12
HO1148 FREQ 12
HO1149 RXLEV 12
HO1198 BSIC 14
HO1199 FREQ 14
HO12 SYNCHRONIZED 12
HO12100 RXLEV 14
HO1247 BSIC 12
HO1248 FREQ 12
HO1249 RXLEV 12
HO1298 BSIC 14
HO1299 FREQ 14
HO13100 RXLEV 14
HO1347 BSIC 12
HO1348 FREQ 12
HO1349 RXLEV 12
HO1398 BSIC 14
HO1399 FREQ 14
HO14100 RXLEV 14
HO1447 BSIC 12
HO1448 FREQ 12
HO1449 RXLEV 12
HO147 BSIC 12
HO148 FREQ 12
Alcatel-Lucent
HO149 RXLEV 12
HO1498 BSIC 14
HO1499 FREQ 14
HO15100 RXLEV 14
HO1547 BSIC 12
HO1548 FREQ 12
HO1549 RXLEV 12
HO1598 BSIC 14
HO1599 FREQ 14
HO16100 RXLEV 14
HO1647 BSIC 12
HO1648 FREQ 12
HO1649 RXLEV 12
HO1698 BSIC 14
HO1699 FREQ 14
HO198 BSIC 14
HO199 FREQ 14
HO2 INTRA_INTER_CELL_IND 12
HO2100 RXLEV 14
HO2102 FDD_FREQ 14
HO2103 AV_ECNO 14
HO23 A_LEV_HO 12
HO23a A_LEV_MCHO 12
HO247 BSIC 12
HO248 FREQ 12
HO249 RXLEV 12
HO25 AV_RXLEV_UL_HO (12) 12
HO25a AV_RXLEV_UL_MCHO (12) 12
HO26 AV_RXLEV_DL_HO (12) 12
HO26a AV_RXLEV_DL_MCHO (12) 12
HO27 A_PBGT_HO 12
HO29 AV_RXLEV_PBGT_HO (12) 12
HO298 BSIC 14
HO299 FREQ 14
HO3 HO_REQUIRED_TIME_STAMP 12
HO30 A_QUAL_HO 12
HO3100 RXLEV 14
Alcatel-Lucent
HO3102 FDD_FREQ 14
HO3103 AV_ECNO 14
HO32 AV_RXQUAL_UL_HO (12) 12
HO33 AV_RXQUAL_DL_HO (12) 12
HO34 A_RANGE_HO 12
HO347 BSIC 12
HO348 FREQ 12
HO349 RXLEV 12
HO36 AV_RANGE_HO (12) 12
HO37 MS_TXPWR 12
HO38 BS_TXPWR 12
HO398 BSIC 14
HO399 FREQ 14
HO41 INCOMING_HO_IND 13
HO4100 RXLEV 14
HO4102 FDD_FREQ 14
HO4103 AV_ECNO 14
HO42 HO_REQUEST_TIME_STAMP 13
HO43 NEW_CHANNEL_ID 13
HO43a NEW_RTCH_TYPE 13
HO44 INC_EXT_HO_SUCCESS_FAILURE_IND 13
HO447 BSIC 12
HO448 FREQ 12
HO449 RXLEV 12
HO45 SYNCHRONIZED 13
HO46 SAMPLE_RATE 13
HO498 BSIC 14
HO499 FREQ 14
HO5 OLD_CHANNEL_ID 12
HO5100 RXLEV 14
HO5102 FDD_FREQ 14
HO5103 AV_ECNO 14
HO547 BSIC 12
HO548 FREQ 12
Alcatel-Lucent
HO549 RXLEV 12
HO598 BSIC 14
HO599 FREQ 14
HO5a OLD_RTCH_TYPE 12
HO6 NEW_CHANNEL_ID 12
HO61 OUTGOING_HO_IND 14
HO6100 RXLEV 14
HO6102 FDD_FREQ 14
HO6103 AV_ECNO 14
HO62 HO_REQUIRED_TIME_STAMP 14
HO63 HO_REQUIRED_NB 14
HO64 OLD_CHANNEL_ID 14
HO647 BSIC 12
HO648 FREQ 12
HO649 RXLEV 12
HO64a OLD_RTCH_TYPE 14
HO65 OUT_EXT_HO_SUCCESS_FAILURE_IND 14
HO68 HO_CAUSE 14
HO698 BSIC 14
HO699 FREQ 14
HO6a NEW_RTCH_TYPE 12
HO7 INT_HO_SUCCESS_FAILURE_IND 12
HO7100 RXLEV 14
HO7102 FDD_FREQ 14
HO7103 AV_ECNO 14
HO74 SAMPLE_RATE 12
HO747 BSIC 12
HO748 FREQ 12
HO749 RXLEV 12
HO75 MS_SPEED 12
HO76 MS_SPEED 14
HO798 BSIC 14
HO799 FREQ 14
HO8 HO_DURATION 12
HO80 A_LEV_HO 14
Alcatel-Lucent
HO80a A_LEV_MCHO 14
HO8100 RXLEV 14
HO8102 FDD_FREQ 14
HO8103 AV_ECNO 14
HO82 AV_RXLEV_UL_HO (12) 14
HO82a AV_RXLEV_UL_MCHO (12) 14
HO83 AV_RXLEV_DL_HO (12) 14
HO83a AV_RXLEV_DL_MCHO (12) 14
HO84 A_PBGT_HO 14
HO847 BSIC 12
HO848 FREQ 12
HO849 RXLEV 12
HO86 AV_RXLEV_PBGT_HO (12) 14
HO87 A_QUAL_HO 14
HO89 AV_RXQUAL_UL_HO (12) 14
HO898 BSIC 14
HO899 FREQ 14
HO90 AV_RXQUAL_DL_HO (12) 14
HO91 A_RANGE_HO 14
HO9100 RXLEV 14
HO93 AV_RANGE_HO (12) 14
HO94 MS_TXPWR 14
HO947 BSIC 12
HO948 FREQ 12
HO949 RXLEV 12
HO95 BS_TXPWR 14
HO998 BSIC 14
HO999 FREQ 14
L1.1 NB_LAPD_INFO_FRAME_SENT 7
L1.12 NB_LAPD_CRC_ERROR 7
L1.15 NB_LAPD_INFO_FRAME_RESENT 7
L1.16 TIME_LAPD_UNAVAIL 7
L1.17 NB_LAPD_EST 7
L1.18 TIME_LAPD_CONG 7
L1.2 NB_LAPD_INFO_FRAME_REC 7
L1.5 NB_LAPD_RNR_SENT 7
L1.6 NB_LAPD_RNR_REC 7
Alcatel-Lucent
MC01 NB_IMM_ASS_SUCC_MT 110
MC02 NB_IMM_ASS_SUCC_MO 110
MC02a NB_IMM_ASS_SUCC_MO_LOC_UPD 110
MC02b NB_IMM_ASS_SUCC_MO_SMS 110
MC02c NB_IMM_ASS_SUCC_MO_SUP_SERV 110
MC02d NB_IMM_ASS_SUCC_MO_FOLLOW_ON 110
MC02e NB_IMM_ASS_SUCC_MO_CM_REEST 110
MC02f NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW 110
MC02g NB_IMM_ASS_SUCC_MO_IMSI_DETACH 110
MC02h NB_IMM_ASS_SUCC_MO_CALL_EST 110
MC02i NB_IMM_ASS_SUCC_MO_LCS 110
MC03 NB_OUT_SDCCH_HO_SUCC 110
MC04 NB_IMM_ASS_PREP_FAIL_CONG 110
MC07 NB_SDCCH_DROP_OUT_HO 110
MC10 NB_INC_SDCCH_HO_SUCC 110
MC101 NB_INTRA_SDCCH_HO_PREP_FAIL_CONG 110
MC1040 NB_HO_ATPT_23_TrafHandover 110
MC1044 NB_HO_ATPT_24_gencapture 110
MC1050 NB_HO_22_TooShortDistance 110
MC137 NB_SDCCH_DROP_EST_PHAS_BSS_PB 110
MC138 NB_SDCCH_DROP_EST_PHAS_RLF 110
MC13a NB_TCH_NOR_ASS_QUEUED 110
MC13b NB_INC_EXT_TCH_HO_QUEUED 110
MC140a NB_TCH_NOR_ASS_REQ 110
MC140b NB_TCH_NOR_ASS_ATPT 110
MC141 AV_NB_TCH_QUEUED 110
MC142e NB_OUT_IDR_SUCC 110
MC142f NB_OUT_EDR_SUCC 110
MC144e NB_OUT_IDR_REQ 110
MC144f NB_OUT_EDR_REQ 110
MC147 NB_INC_SDCCH_HO_ALLOC 110
MC148 NB_IMM_ASS_ALLOC 110
MC149 NB_IMM_ASS_EXEC_FAIL_RADIO 110
MC14a NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB 110
MC14c NB_TCH_DROP_EST_PHAS_BSS_PB 110
MC151 NB_INC_IDR_SUCC (29) 110
MC153 NB_INC_IDR_REQ 110
MC15a NB_INC_IDR_ALLOC 110
Alcatel-Lucent
MC15b NB_INC_TCH_HO_ALLOC 110
MC161 NB_DTAP_NOR_ASS_SUCC 110
MC162 NB_TCH_DROP_DTAP_EST_PHAS 110
MC170 NB_CALL_TFO 110
MC19 NB_TCH_NOR_ASS_HO_PREP_FAIL_ACHAN_MIS (110) 110
MC191 NB_SMS_PP_CON_MT_SDCCH 110
MC196 NB_SMS_PP_CON_SUCC 110
MC197 NB_SMS_PP_CON_FAIL 110
MC24 AV_NB_NOT_AVAIL_TRX_TS 110
MC250 AV_NB_AVAIL_TCH 110
MC26 AV_NB_AVAIL_SDCCH 110
MC27 AV_NB_AVAIL_CCCH 110
MC28a AV_NB_BUSY_CS_TS 110
MC29a NB_MAX_SIMUL_BUSY_CS_TS 110
MC31 NB_MAX_SIMUL_BUSY_SDCCH 110
MC320a AV_NB_IDLE_TCH_INTERF_BAND1 110
MC320b AV_NB_IDLE_TCH_INTERF_BAND2 110
MC320c AV_NB_IDLE_TCH_INTERF_BAND3 110
MC320d AV_NB_IDLE_TCH_INTERF_BAND4 110
MC320e AV_NB_IDLE_TCH_INTERF_BAND5 110
MC34 TIME_ALL_AVAIL_TRX_TS_BUSY 110
MC35 AV_NB_A_TRAF_CHAN_BLOCK_OUT_OF_SERV 110
MC350 NB_N7_CON_REQ 110
MC351 NB_N7_CON_CONF 110
MC36 AV_NB_AVAIL_A_TRAF_CHAN 110
MC370a NB_TRX_FR_ALLOC 110
MC370b NB_TRX_HR_ALLOC 110
MC380a TIME_TRX_FR_BUSY 110
MC380b TIME_TRX_HR_BUSY 110
MC380c TIME_TRX_GSM_FR_BUSY 110
MC380d TIME_TRX_GSM_HR_BUSY 110
MC380e TIME_TRX_DCS_FR_BUSY 110
MC380f TIME_TRX_DCS_HR_BUSY 110
MC381 TIME_TRX_TCH_BUSY_BY_MULTIBAND_MS 110
MC390 NB_TIMES_SDCCH_BUSY (110) 110
MC400 TIME_TRX_SDCCH_BUSY 110
MC41b NB_INC_EXT_TCH_HO_PREP_FAIL_NO_TTCH 110
MC448a NB_TCH_HO_ATPT_26_BadQualHR 110
Alcatel-Lucent
MC448b NB_TCH_HO_ATPT_27_GoodQualFR 110
MC449 NB_TCH_HO_ATPT_28_FastTraffic 110
MC460a NB_TCH_EMERGENCY_HO_PRESERVATION 110
MC461 NB_TCH_HO_ATPT_29_TFO 110
MC462a NB_OUT_INTER_PLMN_TCH_HO_REQ 110
MC462b NB_OUT_INTER_PLMN_TCH_HO_ATPT 110
MC462c NB_OUT_INTER_PLMN_TCH_HO_SUCC 110
MC463a NB_INC_INTER_PLMN_TCH_HO_REQ 110
MC463b NB_INC_INTER_PLMN_TCH_HO_ATPT 110
MC463c NB_INC_INTER_PLMN_TCH_HO_SUCC 110
MC480 NB_TCH_HO_REQ_30_ReturnCSZone 110
MC481 NB_TCH_HO_ATPT_30_ReturnCSZone 110
MC541 NB_INC_EXT_TCH_HO_PREP_FAIL_R_ABIS 110
MC541a NB_INC_EXT_TCH_HO_PREP_FAIL_CONG_R_ABIS 110
MC551 NB_INC_INT_TCH_HO_PREP_FAIL_CONG_R_ABIS 110
MC555 NB_INC_IDR_PREP_FAIL_CONG_R_ABIS 110
MC561 NB_INTRA_TCH_HO_PREP_FAIL_CONG_R_ABIS 110
MC586a NB_TCH_HO_ATPT_10_TooLowLevUpInZone 110
MC586b NB_TCH_HO_ATPT_11_TooLowLevDownInZone 110
MC586c NB_TCH_HO_ATPT_13_TooHighLevUpDownOutZone 110
MC607 NB_SDCCH_HO_20_HighLevNeigCellForcDR 110
MC612a NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE 110
MC612b NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL 110
MC612c NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP 110
MC612d NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ 110
MC621 NB_TCH_DROP_OUT_HO_EXEC_TRX 110
MC642 NB_INC_EXT_HO_SUCC 110
MC643 NB_INC_EXT_HO_EXEC_FAIL_MS_ACCESS 110
MC645a NB_OUT_EXT_REAL_HO_REQ 110
MC646 NB_OUT_EXT_HO_SUCC 110
MC647 NB_OUT_EXT_HO_EXEC_FAIL_REV 110
MC648 NB_OUT_EXT_HO_EXEC_FAIL_NO_REV 110
MC650 NB_OUT_EXT_HO_ATPT 110
MC652 NB_INC_INT_HO_SUCC 110
MC653 NB_INC_INT_HO_EXEC_FAIL_MS_ACCESS 110
MC655a NB_OUT_INT_HO_REQ 110
MC656 NB_OUT_INT_HO_SUCC 110
MC657 NB_OUT_INT_HO_EXEC_FAIL_REV 110
Alcatel-Lucent
MC658 NB_OUT_INT_HO_EXEC_FAIL_NO_REV 110
MC660 NB_OUT_INT_HO_ATPT 110
MC662 NB_INTRA_HO_SUCC 110
MC663 NB_INTRA_HO_EXEC_FAIL_NO_REV 110
MC667 NB_INTRA_HO_EXEC_FAIL_REV 110
MC670 NB_HO_2_TooLowQualUp 110
MC671 NB_HO_3_TooLowLevUp 110
MC672 NB_HO_4_TooLowQualDown 110
MC673 NB_HO_5_TooLowLevDown 110
MC674 NB_HO_6_TooLongDistance 110
MC675 NB_HO_MSC_TRIG 110
MC676 NB_HO_15_TooHighLevInterfUp 110
MC677 NB_HO_16_TooHighLevInterfDown 110
MC678 NB_HO_12_TooLowPowBudg 110
MC679 NB_HO_21_HighLevNeigCellPrefBand 110
MC701a NB_TCH_FR_REQ 110
MC701b NB_TCH_DR_REQ 110
MC701c NB_TCH_DR_EFR_REQ 110
MC701d NB_TCH_AMR_REQ 110
MC701e NB_TCH_DATA_REQ 110
MC701f NB_TCH_FR_EFR_REQ 110
MC701g NB_TCH_NO_FR_REQ 110
MC702a NB_TCH_NOR_FR_ALLOC 110
MC702b NB_TCH_NOR_HR_ALLOC 110
MC702c NB_TCH_NOR_EFR_ALLOC 110
MC703 NB_TCH_NOR_ASS_ALLOC_TRX 110
MC704a NB_TCH_NOR_AMR_FR_ALLOC 110
MC704b NB_TCH_NOR_AMR_HR_ALLOC 110
MC705 NB_TCH_NOR_DATA_ALLOC 110
MC706 NB_EGSM_MS_ACCESS_EXCEPT_LU 110
MC710 NB_TCH_OUT_HO_REQ_TRX 110
MC711 NB_TCH_OUT_HO_PREP_FAIL_CONG_TRX 110
MC712 NB_TCH_OUT_HO_SUCC_TRX 110
MC713 NB_TCH_OUT_HO_FAIL_REV_TRX 110
MC714 NB_TCH_OUT_HO_FAIL_NO_REV_TRX 110
MC717a NB_INC_IDR_SUCC_TRX 110
MC717b NB_INC_TCH_HO_SUCC_TRX 110
MC718 NB_TCH_NOR_ASS_SUCC_TRX 110
Alcatel-Lucent
MC736 NB_TCH_DROP_EST_PHAS_RLF_TRX 110
MC739 NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX 110
MC746b NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX 110
MC785a NB_HO_7_ConsBadSACCHmicroCell 110
MC785d NB_HO_17_TooLowLevUpMicroCell 110
MC785e NB_HO_18_TooLowLevDownMicroCell 110
MC785f NB_HO_14_HighLevNeigLowCellSlowMS 110
MC800 AV_NB_AVAIL_DYN_TS 110
MC801a AV_NB_BUSY_DYN_TCH 110
MC801b MAX_NB_BUSY_DYN_TCH 110
MC802a AV_NB_BUSY_DYN_SDCCH 110
MC802b MAX_NB_BUSY_DYN_SDCCH 110
MC803 TIME_SDCCH_CONGESTION 110
MC804a NB_UL_SINGLE_BLOCK_SIG_RACH 110
MC804b NB_UL_ONE_PHASE_SIG_RACH 110
MC805a NB_CHANNEL_ASSIGN_DL_AGCH 110
MC805b NB_CHANNEL_ASSIGN_DL_PCH 110
MC81 NB_INC_EXT_SDCCH_HO_PREP_FAIL_CONG 110
MC812 NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS 110
MC820 NB_INC_EXT_HO_REQ 110
MC821 NB_INC_EXT_HO_ATPT 110
MC830 NB_INC_INT_HO_REQ 110
MC831 NB_INC_INT_HO_ATPT 110
MC850 NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL 110
MC870 NB_INTRA_HO_REQ 110
MC871 NB_INTRA_HO_ATPT 110
MC8a NB_CELL_PAGING_CMD 110
MC8b NB_CELL_IMM_ASS_CMD 110
MC8c NB_CELL_CHAN_REQD 110
MC8d NB_CELL_IMM_ASS_REJ 110
MC901 NB_Suspend_Resume_req 110
MC902 Nb_Suspend_fail 110
MC903 Nb_Suspend_succ 110
MC91 NB_INC_INT_SDCCH_HO_PREP_FAIL_CONG 110
MC921a NB_TCH_NOR_ASS_HO_REQ_ABLE_TO_PREEMPT 110
MC921b NB_PREEMPT_CAP_ALLOC_SUCC 110
MC921c NB_PREEMPTED_CALLS 110
MC921d NB_PREEMPT_CAP_OUT_DR_ALLOC_SUCC 110
Alcatel-Lucent
MC921e NB_TCH_NOR_ASS_HO_SUCC_PREEMPTABLE 110
MC922a NB_INC_EXT_3G_2G_HO_REQ 110
MC922b NB_INC_EXT_3G_2G_HO_SUCC 110
MC922c NB_INC_EXT_3G_2G_HO_EXEC_FAIL_MS_ACC 110
MC922d NB_INC_EXT_3G_2G_HO_ATPT 110
MC922e NB_INC_EXT_TCH_3G_2G_HO_EMERGENCY_REQ 110
MC922f NB_INC_EXT_TCH_3G_2G_HO_REQ 110
MC922g NB_INC_EXT_TCH_3G_2G_HO_PREP_FAIL_3GCONG 110
MC922h TIME_3G_HOReject_HL 110
MC923a NB_LCS_REQ 110
MC923b NB_LCS_SUCC 110
MC923c NB_LCS_FAIL_LB 110
MC923d NB_LCS_ABORT 110
MC924a TIME_SPDCH_LIMIT_HIGH_LOAD 110
MC924b NB_OUT_2G_3G_HO_REQ 110
MC924c NB_OUT_2G_3G_HO_SUCC 110
MC924d NB_OUT_2G_3G_HO_ATPT 110
MC924e NB_OUT_2G_3G_HO_EXEC_FAIL_NO_REV 110
MC924f NB_OUT_2G_3G_HO_EXEC_FAIL_REV 110
MC924g NB_OUT_2G_3G_HO_PREP_FAIL 110
MC924h NB_2G_3G_HO_8 110
MC924i NB_2G_3G_HO_9 110
MC924j NB_2G_3G_HO_10 110
MC924k NB_2G_3G_HO_11 110
MC925a NB_AGCH_USEFUL_BLOCKS_SENT 110
MC925b NB_PCH_USEFUL_BLOCKS_SENT 110
MC925c NB_BUSY_RACH_SLOTS 110
MC925d NB_CHANNEL_RQ_RADIO 110
MC925e NB_ASSIGN_CMD_RECEIVED_ABIS 110
MC925f NB_ASSIGN_CMD_DISCARDED 110
MC925g NB_PAGING_CMD_RECEIVED_ABIS 110
MC925h NB_PAGING_CMD_DISCARDED 110
MC926 TCH_BLOCKING_OCCURENCES_BSC 110
MC927a NB_DTM_UL_TCH_ASS_ATPT 110
MC927b NB_DTM_DL_TCH_ASS_ATPT 110
MC927c NB_DTM_UL_PACKET_ASS_ATPT 110
MC927d NB_DTM_DL_PACKET_ASS_ATPT 110
MC927e NB_DTM_UL_TCH_ASS_EXEC_FAIL_RADIO 110
Alcatel-Lucent
MC927f NB_DTM_DL_TCH_ASS_EXEC_FAIL_RADIO 110
MC928a NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_UL 110
MC928b NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_UL 110
MC928c NB_TCH_DROP_CAUSE_TOO_LOW_QUALITY_DL 110
MC928d NB_TCH_DROP_CAUSE_TOO_LOW_LEVEL_DL 110
MC928e NB_TCH_DROP_CAUSE_TOO_LONG_MS_BS_DISTANCE 110
MC928f NB_TCH_DROP_CAUSE_TOO_SHORT_MS_BS_DISTANCE 110
MC928g NB_TCH_DROP_CAUSE_TOO_HIGH_INTERFERENCE_UPLINK 110
MC928h NB_TCH_DROP_CAUSE_TOO_HIGH_INTERFERENCE_DOWNLINK 110
MC928i NB_TCH_DROP_OTHER_CAUSES 110
MC930 NB_ABIS_PAGING_MESSAGE_RECEIVED 110
MC931 NB_TCH_NOR_AMR_WB_GMSK_FR_ALLOC 110
MC932 NB_TCH_AMR_WB_GMSK_REQ 110
MC933 NB_TCH_NOR_ASS_PREP_FAIL_PMIS 110
MC934 NB_INC_EXT_TCH_HO_PREP_FAIL_PMIS 110
MC935 NB_CALL_TFO_AMR_WB 110
MC936 NB_HO_INTER_TFO_AMR_WB 110
MC937 NB_HO_EXT_TFO_AMR_WB 110
MC938 NB_CALL_TFO_AMR 110
MC939 NB_HO_INTER_TFO_AMR 110
MC940 Reserve_BSC_1 110
MC950 NB_HO_EXT_TFO_AMR 110
MC951 Reserve_cell_12 110
MC959 NB_PS_CHAN_REQD 110
MC960 NB_DISCARDED_PS_CHAN_REQD_BECAUSE_GSL_CONGESTION 110
Alcatel-Lucent
MC962 NB_INVALID_CHAN_REQD_RECEIVED_BY_BSC 110
MC963 NB_NON_PS_CHAN_REQD_DISCRADED_BECAUSE_CONGESTION 110
MC964 NB_VALID_LOCATION_UPDATE_RECEIVED_BY_BSC 110
MN1.1 TIME_N7_ALIGNED 110
N1.1 TIME_N7_ALIGNED 9
N1.10 NB_N7_CHANGEOVER 9
N1.11 NB_N7_CHANGEBACK 9
N1.12 NB_N7_RESTORATION 9
N1.2 NB_N7_LINK_FAIL_ANY_CAUSE 9
N1.3 NB_N7_LINK_FAIL_FIB_BSN 9
N1.4 NB_N7_LINK_FAIL_T7_EXP 9
N1.5 NB_N7_LINK_FAIL_SU_ERROR_RATE 9
N1.6 NB_N7_LINK_FAIL_CONG 9
N1.7 NB_N7_LINK_FAIL_ALIGNMENT 9
N1.8 NB_N7_SU_REC_WITH_ERROR 9
N1.9 NB_N7_NEG_ACK_REC 9
N2.7 TIME_N7_UNAVAIL_ERROR_SL 9
N2.9 TIME_N7_UNAVAIL_MSC_PROC_OUTAGE 9
N3.1 NB_N7_SIF_SIO_SENT 9
N3.10 NB_N7_MSU_DISC_DUE_CONG 9
N3.11 NB_N7_CONG_WITH_MSU_LOST 9
N3.2 NB_N7_OCTETS_RESENT 9
N3.3 NB_N7_MSU_SENT 9
N3.4 NB_N7_SIF_SIO_REC 9
N3.5 NB_N7_MSU_REC 9
N3.7 TIME_N7_UNAVAIL_CONG 9
N4.2 TIME_N7_UNAVAIL_LINK_SET 9
R01 CHANNEL_ID (TCH) 11
Alcatel-Lucent
R01a RTCH_TYPE 11
R03 RECEIVED_TIMESTAMP 11
R04 AV_RXLEV_UL_HO (11) 11
R04a AV_RXLEV_UL_MCHO (11) 11
R05 AV_RXLEV_DL_HO (11) 11
R05a AV_RXLEV_DL_MCHO (11) 11
R06 AV_RXLEV_PBGT_HO (11) 11
R07 AV_RXQUAL_UL_HO (11) 11
R08 AV_RXQUAL_DL_HO (11) 11
R09 AV_RANGE_HO (11) 11
R10 MS_TXPWR 11
R1013 BSIC 11
R1014 BCCH_FREQ 11
R1015 AV_RXLEV_NCELL 11
R1016 PBGT 11
R11 BS_TXPWR 11
R1113 BSIC 11
R1114 BCCH_FREQ 11
R1116 PBGT 11
R113 BSIC 11
R114 BCCH_FREQ 11
R116 PBGT 11
R118 SCRAMBLING_CODE 11
R119 FDD_FREQ 11
R12 BTSNUM 11
R120 AV_ECNO 11
R1213 BSIC 11
R1214 BCCH_FREQ 11
R1216 PBGT 11
R1313 BSIC 11
R1314 BCCH_FREQ 11
R1316 PBGT 11
R1413 BSIC 11
R1414 BCCH_FREQ 11
Alcatel-Lucent
R1416 PBGT 11
R1513 BSIC 11
R1514 BCCH_FREQ 11
R1516 PBGT 11
R1613 BSIC 11
R1614 BCCH_FREQ 11
R1616 PBGT 11
R17 SAMPLE_RATE 11
R1713 BSIC 11
R1714 BCCH_FREQ 11
R1716 PBGT 11
R1813 BSIC 11
R1814 BCCH_FREQ 11
R1816 PBGT 11
R1913 BSIC 11
R1914 BCCH_FREQ 11
R1916 PBGT 11
R2013 BSIC 11
R2014 BCCH_FREQ 11
R2016 PBGT 11
R2113 BSIC 11
R2114 BCCH_FREQ 11
R2116 PBGT 11
R213 BSIC 11
R214 BCCH_FREQ 11
R216 PBGT 11
R219 FDD_FREQ 11
R220 AV_ECNO 11
Alcatel-Lucent
R2213 BSIC 11
R2214 BCCH_FREQ 11
R2216 PBGT 11
R2313 BSIC 11
R2314 BCCH_FREQ 11
R2316 PBGT 11
R2413 BSIC 11
R2414 BCCH_FREQ 11
R2416 PBGT 11
R2513 BSIC 11
R2514 BCCH_FREQ 11
R2516 PBGT 11
R2613 BSIC 11
R2614 BCCH_FREQ 11
R2616 PBGT 11
R2713 BSIC 11
R2714 BCCH_FREQ 11
R2716 PBGT 11
R2813 BSIC 11
R2814 BCCH_FREQ 11
R2816 PBGT 11
R2913 BSIC 11
R2914 BCCH_FREQ 11
R2916 PBGT 11
R3013 BSIC 11
R3014 BCCH_FREQ 11
R3016 PBGT 11
R3113 BSIC 11
R3114 BCCH_FREQ 11
Alcatel-Lucent
R3116 PBGT 11
R313 BSIC 11
R314 BCCH_FREQ 11
R316 PBGT 11
R319 FDD_FREQ 11
R320 AV_ECNO 11
R3213 BSIC 11
R3214 BCCH_FREQ 11
R3216 PBGT 11
R413 BSIC 11
R414 BCCH_FREQ 11
R416 PBGT 11
R419 FDD_FREQ 11
R420 AV_ECNO 11
R513 BSIC 11
R514 BCCH_FREQ 11
R516 PBGT 11
R519 FDD_FREQ 11
R520 AV_ECNO 11
R613 BSIC 11
R614 BCCH_FREQ 11
R616 PBGT 11
R619 FDD_FREQ 11
R620 AV_ECNO 11
R713 BSIC 11
R714 BCCH_FREQ 11
R716 PBGT 11
Alcatel-Lucent
R719 FDD_FREQ 11
R720 AV_ECNO 11
R813 BSIC 11
R814 BCCH_FREQ 11
R816 PBGT 11
R819 FDD_FREQ 11
R820 AV_ECNO 11
R913 BSIC 11
R914 BCCH_FREQ 11
R916 PBGT 11
RMS10 VQ_NOISY_UL_INTERFERENCE 31
RMS11 VQ_NOISY_DL_INTERFERENCE 31
RMS12 VQ_NOISY_UL_COVERAGE 31
RMS13 VQ_NOISY_DL_COVERAGE 31
RMS14 VQ_NOISY_UL_UNDEFINED 31
RMS15 VQ_NOISY_DL_UNDEFINED 31
RMS16 VQ_NOISY_UL_BAD_FER 31
RMS17 VQ_NOISY_UL_GOOD_FER 31
RMS18 VQ_ABNORMAL_BAD_FER 31
RMS20 TRE_BAND 31
RMS21 IND_TRE_OVERLOAD 31
RMS22 IND_RMS_RESTARTED 31
RMS23 IND_CI_PARTIAL_OBSERVATION 31
RMS24 IND_CI_OVERFLOW 31
RMS31 TOT_SEIZ_TCH 31
RMS32 TOT_MEAS 31
RMS33 TOT_MEAS_L1INFO_NOL3INFO 31
RMS34 TOT_MEAS_DTX_UL 31
RMS35 TOT_MEAS_DTX_DL 31
RMS36 PERC_TA_GT_TA_STAT 31
RMS37 MAX_TA 31
RMS38 TOT_EMR 31
RMS3a TPR_RXQUAL_UL_RXLEV_UL 31
RMS3b TMR_RXQUAL_UL_RXLEV_UL 31
Alcatel-Lucent
RMS41a AMR_WB_GMSK_FR_UL_BAD 31
RMS41b MAX_AMR_WB_GMSK_FR_UL_BAD 31
RMS42a AMR_WB_GMSK _FR_UL_RXLEV_UL 31
RMS42b MAX_AMR_WB_GMSK_FR_UL_RXLEV_UL 31
RMS43a AMR_WB_GMSK_FR_DL_RXLEV_DL 31
RMS43b MAX_AMR_WB_GMSK_FR_DL_RXLEV_DL 31
RMS44a AMR_FR_UL_BAD 31
RMS44b MAX_AMR_FR_UL_BAD 31
RMS45a AMR_HR_UL_BAD 31
RMS45b MAX_AMR_HR_UL_BAD 31
RMS46a AMR_FR_UL_RXLEV_UL 31
RMS46b MAX_AMR_FR_UL_RXLEV_UL 31
RMS47a AMR_FR_DL_RXLEV_DL 31
RMS47b MAX_AMR_FR_DL_RXLEV_DL 31
RMS48a AMR_HR_UL_RXLEV_UL 31
RMS48b MAX_AMR_HR_UL_RXLEV_UL 31
RMS49a AMR_HR_DL_RXLEV_DL 31
RMS49b MAX_AMR_HR_DL_RXLEV_DL 31
RMS4a TPR_RXQUAL_DL_RXLEV_DL 31
RMS4b TMR_RXQUAL_DL_RXLEV_DL 31
RMS50a TPR_TIMING_ADVANCE 31
RMS50b MAX_TIMING_ADVANCE 31
RMS51 TPR_UL_RXLEV_TA_BAND 31
RMS52 TPR_DL_RXLEV_TA_BAND 31
RMS53 TPR_UL_RXQUAL_TA_BAND 31
RMS54 TPR_DL_RXQUAL_TA_BAND 31
RMS5a TPR_BFI_RXLEV_UL 31
RMS5b TMR_BFI_RXLEV_UL 31
RMS6a TPR_RADIO_LINK 31
RMS6b MAX_RADIO_LINK 31
RMS7a TPR_PATH_BALANCE 31
RMS7b MAX_PATH_BALANCE 31
RMS8a TPR_CIN 31
RMS8b MR_CIN 31
RMS9a TPR_CIF 31
RMS9b MR_CIF 31
RMSp80 NEIGB_CELL_ID 31
RMSp90 Frequency ARFCN 31
Alcatel-Lucent
RMSpa PAR_EN_BALANCED_CI 31
RMSpb PAR_TA_STAT 31
RMSpc PAR_VQ_AVERAGE 31
RMSpd PAR_VQ_RXLEV 31
RMSpe PAR_VQ_RXQUAL 31
RMSpf PAR_VQ_RXQUAL_VS_RXFER 31
RMSpg PAR_VQ_GOOD_RXFER 31
RMSph PAR_VQ_BAD_RXFER 31
RMSpi PAR_VQ_INTF_THRESHOLD 31
RMSpj PAR_VQ_FER_THRESHOLD 31
RMSpt1 TAB_PAR_MEAS_C/I 31
RMSpt2 TAB_PAR_MEAS_STAT_BFI 31
RMSpt3 TAB_PAR_MEAS_STAT_S 31
RMSpt4 TAB_PAR_MEAS_PATH_BALANCE 31
RMSpt5 TAB_PAR_MEAS_LEVEL 31
RMSpt6 TAB_PAR_MEAS_STAT_TA 31
RMSpw1 BS_TX_PWRMAX 31
RMSpw2 MS_TX_PWRMAX 31
RMSPw3 MAX_POWER_PER_TRX 31
S01 CHANNEL_ID (SCCH) 10
S02 CHAN_SEIZ_TIME 10
S03 CHAN_RELEASE_TIME 10
S04 END_INDICATION (SDCCH) 10
S05 SEIZURE_TYPE (SDCCH) 10
S06 MS_POWER 10
S07 BS_POWER 10
S08 TIMING_ADVANCE 10
S09 NB_FRAMES_NOT_REPEATED 10
S16 NB_FRAMES_REPEATED 10
S17 NB_SABM_AFTER_UA_SENT 10
S18 NB_PHYSICAL_INFO_SENT 10
S19 NB_ERRONEOUS_FRAMES_SENT 10
S20 NB_REJ_FRAMES_SENT 10
S21 NB_REJ_FRAMES_RECEIVED 10
S22 NB_MS_TX_PWR_MAX_SENT 10
S23 RADIO_LINK_FAILURE_INDICATION 10
S24 PERC_INCOR_SACCH_FRAMES_REC 10
S25 PERC_INCOR_SDCCH_FRAMES_REC 10
Alcatel-Lucent
S26 SAMPLE_RATE 10
T01 CHANNEL_ID (TCH) 15
T01a RTCH_TYPE 15
T02 CHANNEL_SEIZURE_TIME 15
T03 CHANNEL_RELEASE_TIME 15
T04 END_INDICATION (TCH) 15
T04a SEIZURE_TYPE (TCH) 15
T05 MS_POWER 15
T06 BS_POWER 15
T07 TIMING_ADVANCE 15
T08 NB_FRAMES_NOT_REPEATED 15
T15 NB_FRAMES_REPEATED 15
T16 NB_SABM_AFTER_UA_SENT 15
T17 NB_PHYSICAL_INFO_SENT 15
T18 NB_ERRONEOUS_FRAMES_SENT 15
T19 NB_REJ_FRAMES_SENT 15
T20 NB_REJ_FRAMES_REC 15
T21 NB_MS_TX_PWR_MAX_SENT 15
T22 RADIO_LINK_FAILURE_IND 15
T23 PERC_INCOR_SACCH_FRAMES_REC 15
T24 PERC_INCOR_SDCCH_FRAMES_REC 15
T25 SAMPLE_RATE 15
V01 NB_PTP_CALL_PREEMPTED_VGCS 34
V021 AV_PARALLEL_TCH_VGCS 34
V022 MAX_PARALLEL_TCH_VGCS 34
V03 NB_VGCS_ESTABLISHMENT_REQ 34
V04 NB_VGCS_ESTABLISHMENT_SUCC 34
V05 NB_CM_SERV_REQ_VGCS 34
V06 NB_VGC_RELEASED_VGCS 34
V07 NB_OUT_VGCS_HO_ATPT 34
V08 NB_OUT_VGCS_HO_SUCC 34
V09 NB_INC_VGCS_HO_SUCC 34
V10 NB_INC_VGCS_HO_ATPT 34
V11 NB_TALKER_CHANGE_VGCS 34
V12 NB_VGC_BLOCKED_VGCS 34
V13 NB_VGCS_NOTIFIFICATION_FACCH 34
V14 NB_ASS_REQ_ABLE_PREEMT 34
V15 NB_VGCS_ASS_REQ_ABLE_TO_PREEMPT 34
Alcatel-Lucent
V16 NB_VGCS_QUEUED 34
V17 NB_VGCS_ESTABLISHED 34
V18 NB_PREEMTED_TCH_VGCS 34
V19 NB_PAGING_FACCH 34
V20 VGCS20 34
X3.20 NB_X25_INC_CALL_SUCC_CLOSED 8
X3.21 NB_X25_OUT_CALL_SUCC_CLOSED 8
X3.22 NB_X25_INC_CALL_ABNORM_CLOSED 8
X3.23 NB_X25_OUT_CALL_ABNORM_CLOSED 8
END OF DOCUMENT

Alcatel BSC Counters Catalogue - B10

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Alcatel BSC Counters Catalogue - B10

Загружено:

Авторское право:

Доступные форматы

Alcatel-Lucent

Вам также может понравиться