Beruflich Dokumente
Kultur Dokumente
BSC COUNTERS
CATALOGUE B9
Type definition:
Set of counters related to the traffic evaluation per telecom procedures
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
Counter definition:
Number of immediate assignment successes for Mobile Originating procedure.
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
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".
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
Counter definition:
case: Supplementary Service
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION message is received from a CELL, with the L3 INFORMATION
field
containing a 44.018 L3 message with an MIE message type set to CM SERVICE REQUEST and with an MIE CM
service type set to "Supplementary Service".
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
Counter definition:
case: Location Update request ("follow on" procedure)
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION message is received from a CELL, with the L3 INFORMATION
field
containing a 44.018 L3 message with an MIE message type set to LOCATION UPDATING REQUEST and with
an MIE
Location updating type not set to a RESERVED value and a bit FOR set to 1.
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
Counter definition:
case: CM Re-establishment procedure
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION message is received from a CELL, with the L3 INFORMATION
field
containing a 44.018 L3 message with an MIE message type set to CM RE-ESTABLISHMENT REQUEST
message.
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
Counter definition:
case: normal or emergency call establishment
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION message is received from a CELL, with the L3 INFORMATION
field
containg a 44.018 L3 message with an MIE message type set to CM SERVICE REQUEST and an MIE CM
service
type set to either :
- "emergency call establishment",
- or "mobile originating call establishment"
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
Counter definition:
case: Mobile originated LCS procedure on SDCCH
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION message is received from a cell, with the L3 INFORMATION field
containing a 44.018 L3 message with an MIE message type set to CM SERVICE REQUEST and with an MIE CM
service type set to "Location Services" (LCS).
This counter is incremented only if the L3 info message received has to be forwarded to the MSC
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: SDCCH
Domain: Quality of Service Sub domain-3: Success
Counter definition:
MC03=C03, Number of outgoing SDCCH handover (any kind) successes.
Trigger condition:
External SDCCH handover: whenever 48.008 CLEAR COMMAND (cause= "handover successful") is received on
the serving BSC on the SDCCH channel.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: SDCCH
Domain: Quality of Service Sub domain-3: Failure
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: SDCCH
Domain: Quality of Service Sub domain-3: Success
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Established Phase
Sub domain-2: SDCCH
Domain: Quality of Service Sub domain-3: Failure
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Established Phase
Sub domain-2: SDCCH
Domain: Quality of Service Sub domain-3: Failure
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
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').
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
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:
i) upon the sending of a 48.008 QUEUING INDICATION message if the queuing is authorised by the MSC, or,
ii) when the handover request is queued in the cell if the queuing is not authorised by the MSC and the request
has
its pre-emption indicator set (provided that the flag EN_TCH_PREEMPT is set to 'Enable').
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Handover
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Traffic Load Sub domain-3:
Counter definition:
Number of immediate assignment plus SDCCH normal assignments -whose SDCCH channel is allocated by the
BSC.
Trigger condition:
Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent on Abis Interface to activate an
SDCCH
channel for any purpose other than handover.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Failure
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
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.
Trigger condition:
1) Whenever the BSC receives on Abis interface from the target cell negative acknowledgment to the TCH
channel
activation involved in the handover procedure.
2) Whenever the timer supervising the Channel Activation procedure (T9103) expires on the target cell during
activation of a TCH channel involved in the handover procedure.
3) Whenever an 48.058 ERROR REPORT message with a cause value of "O&M intervention" is received on Abis
interface from either the serving or the target cell during the external or internal inter-cell handover procedure and
leads to a transaction failure.
4) Whenever an 48.058 ERROR REPORT message with a cause value of "O&M intervention" is received on Abis
interface on either the old or the new channel during the internal intra-cell handover procedure and leads to a
transaction failure.
5) Whenever an 48.058 ERROR REPORT message on SAPI 0 with a cause value of "message sequence error"
is
received on Abis interface from the serving cell between the sending of the 48.058 CHANNEL ACTIVATION
message and the reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGMENT during the internal
inter-cell
TCH handover and leads to a transaction failure.
6) Whenever an 48.058 ERROR REPORT message on SAPI 0 with a cause value of "message sequence error"
is
received on Abis interface on the old channel between the sending of the 48.058 CHANNEL ACTIVATION
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
problems which are internal to the BSS.
However, due to the current implementation which does not allow to be aware of the origin of the failure, O&M
operator actions will also be counted.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 14
Evolium
unit:
External comment: :
mechanism: --
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Established Phase
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
Counter definition:
2. It may happen that the counter can not be incremented since it is implemented within the faulty entity. Number
of TCH (in HR or FR usage) drops in TCH established phase due to BSS problem.
It may happen that several causes of failures mentioned below are detected consecutively. In that case, the
counter will only be incremented once, as soon as the call is released.
Trigger condition:
1) Whenever an 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 an 48.058 ERROR REPORT message on SAPI 0 with a cause value of "message sequence error"
is
received on Abis interface after TCH seizure and leads to a loss of call.
3) Whenever a LAPD failure is reported to the Layer 3 of the BSC (for an RSL supporting a TCH transaction after
successful TCH seizure) and leads to a loss of call.
4) Whenever a TCH call release is initiated by the BSS O&M FAULT MANAGEMENT application part or by the
BSS
TELECOM application part as the result of a system defense action which may be due to BSS equipment failures
external to the BSC (e.g. RSL failure or CU recovery failure), or due to BSC internal hardware problems (e.g. TCU
failure or DTC failure) or due to BSC internal software problems (e.g. inconsistencies detected between software
modules or lack of software resources (memory, timer reference, file reference...) or communication problems
between different processor boards).
Notes :
1. TCH call releases which are due to O&M operator actions on BTS or BSC should not be counted. Indeed, in
case
of numerous failures due to O&M commands, this counter will overestimate failures which are due to problems
which are internal to the BSS.
However, due to the current implementation which does not allow to be aware of the origin of the failure, O&M
operator actions will also be counted.
2. It may happen that the counter can not be incremented since it is implemented within the faulty entity.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Handover
Domain: Traffic Load Sub domain-3: TCH
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:
The counter is incremented on the target cell whenever the 48.058 CHANNEL ACTIVATION message of a TCH
channel is about to be sent during any handover procedure.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: DTAP Assignment
Domain: Quality of Service Sub domain-3: Success
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: DTAP Assignment
Domain: Quality of Service Sub domain-3: Success
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Established Phase
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
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:
1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "radio link failure" is
received on Abis interface for a TCH channel (after successful DTAP establishment).
2) Whenever an 48.058 ERROR INDICATION message is received on Abis interface and leads to a loss of call.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Established Phase
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
Counter definition:
Number of TCH (in HR or FR usage) drops in TCH DTAP established phase due to BSS problem.
It may happen that several causes of failures mentioned below are detected consecutively. In that case, the
counter
will only be incremented once, as soon as the call is released.
After an external handover, the target BSC considers that the CONNECT ACK has not already been received.
Trigger condition:
1) Whenever an 48.058 ERROR REPORT message with a cause value of "O&M intervention" is received on Abis
interface after TCH seizure and leads to a loss of call.
2) Whenever an 48.058 ERROR REPORT message on SAPI 0 with a cause value of "message sequence error"
is
received on Abis interface after TCHDTAP establishment and leads to a loss of call.
3) Whenever a LAPD failure is reported to the Layer 3 of the BSC (for an RSL supporting a TCH transaction after
successful TCH seizure) and leads to a loss of call.
4) Whenever a TCH call release is initiated by the BSS O&M FAULT MANAGEMENT application part or by the
BSS TELECOM application part as the result of a system defense action which may be due to BSS equipment
failures external to the BSC (e.g. RSL failure or CU recovery failure), or due to BSC internal hardware problems
(e.g. TCU failure or DTC failure) or due to BSC internal software problems (e.g. inconsistencies detected between
software modules or lack of software resources (memory, timer reference, file reference...) or communication
problems between different processor boards).
Notes :
1. TCH call releases which are due to O&M operator actions on BTS or BSC should not be counted. Indeed, in
case of numerous failures due to O&M commands, this counter will overestimate failures which are due to
problems which are internal to the BSS.
However, due to the current implementation which does not allow to be aware of the origin of the failure, O&M
operator actions will also be counted.
2. It may happen that the counter can not be incremented since it is implemented within the faulty entity.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Established Phase
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
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:
--
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.
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 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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Normal Assignment
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.
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2:
Domain: Resource Availability & Usage Sub domain-3:
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.
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3: Failure
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.008ASSIGNMENT FAILURE (cause: "no radio resource
available") for a TCH channel because no TCH is available and either the queing is disabled in the BSC (T11=0
and
QUEUE_ANYWAY=0, or T11_forced=0 and QUEUE_ANYWAY=1), or the queing is enabled,
QUEUE_ANYWAY=0,
and the MSC does not request a queuing.
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3: Failure
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:
The counter is incremented upon the sending of 48.008ASSIGNMENT FAILURE (cause: "no radio resource
available") for a TCH channel because the queue is full and no request of lower priority can be dequeued.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3: Failure
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.
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3: Failure
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 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.008ASSIGMENT FAILURE (cause: "no radio resource
available") for a dequeued TCH request (i.e. normal assignment) due to the receipt of a higher priority request.
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
Counter definition:
Number of TCH drops during the execution of any TCH outgoing handover, per TRX.
MC621 = C621
Trigger condition:
1) Inter-cell TCH handover: whenever the timer supervising the handover procedure (T3103) expires.
2) External TCH handover: whenever the timer supervising the handover procedure on the serving cell (T8)
expires.
3) Intra-cell TCH handover: whenever the timer supervising the handover procedure (T3107) expires.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
Counter definition:
Number of TCH normal assignments requests from FR only mobiles.
Trigger condition:
Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call with only GSM speech coding
algorithm
version 1 full rate allowed.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
Counter definition:
Number of TCH normal assignments requests from dual rate mobiles.
Trigger condition:
Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call with only GSM speech coding
algorithm
version 1 full rate and GSM speech coding algorithm version 1 half rate allowed.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
Counter definition:
Number of TCH normal assignment requests from AMR mobiles.
Trigger condition:
Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call with GSM speech coding algorithm
version 3 full rate or half rate allowed.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
Counter definition:
number of TCH normal assignment/mode modify in FR 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 FR channel with GSM
speech coding algorithm version 1, not related to handover.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
Counter definition:
number of TCH normal assignment/mode modify in EFR 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 FR channel with GSM
speech coding algorithm version 2, not related to handover.
External comment:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Traffic Load Sub domain-3:
Counter definition:
Number of TCH (in HR or FR usage) normal assignment -whose RTCH channel is allocated in the BSC, per TRX.
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.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
Counter definition:
number of TCH normal assignment/mode modify in FR 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 FR channel with GSM
speech coding algorithm version 3, not related to handover.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
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
speech coding algorithm version 3, not related to handover.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
Counter definition:
number of TCH normal assignment/mode modify for data - whose channel is allocated in the BSC.
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: E-GSM
Domain: Resource Availability & Usage Sub domain-3:
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:
--
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.
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 for a
TCH
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
Counter definition:
Nb of outgoing TCH handover -preparation failures due to congestion, per TRX. Intracell, internal intercell and
external handovers are counted together.
MC711 = C711
Trigger condition:
1) Intracell HO : Whenever an intra-cell TCH handover cannot be performed, because there is no free TCH
channel
to allocate the handover to.
2) Internal inter-cell HO : Whenever a internal inter-cell TCH handover cannot be performed, because there is no
free TCH channel to allocate the handover to.
3) External HO : Whenever a 48.008 HANDOVER REQUIRED REJECT with cause "no radio resource available"
is
received from the MSC by the serving BSC for an outgoing external TCH HO.
Note : the counter will be incremented for external TCH HO if and only if the parameter RESP_REQ is set to 1.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Success
Counter definition:
Nb of outgoing TCH handover successes, per TRX. Intracell, internal intercell and external handovers are counted
together.
MC712 = C712
Trigger condition:
1) External HO: whenever 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
3) Internal intra-cell HO: whenever 44.018ASSIGNMENT COMPLETE is received from the MS via the cell on the
TCH
channel
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
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.
MC713 = C713
Trigger condition:
1) External HO : Whenever a 44.018 HANDOVER FAILURE message is received on Abis interface from the
serving
cell , during an external TCH handover.
2) Internal inter-cell HO : Whenever a 44.018 HANDOVER FAILURE message is received on Abis interface from
the serving cell, during an internal inter-cell TCH handover.
3) Intracell HO : Whenever a 44.018 ASSIGNMENT FAILURE message is received on Abis interface on the
serving
channel, during an internal intra-cell TCH handover.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
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.
MC714 = C714
Trigger condition:
1) External TCH HO : Whenever the timer supervising the handover procedure on the serving cell (T8), expires
during an external TCH handover.
2) Internal intercell TCH HO : Whenever the timer supervising the handover procedure (T3103) expires during an
internal inter-cell TCH handover.
3) Intracell TCH HO : Whenever the timer supervising the handover procedure (T3107) expires during an internal
intra-cell
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Quality of Service Sub domain-3: Success
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:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Success
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,
the external directed retries are counted by this counter.
MC717b = C717b
Trigger condition:
1) Internal inter-cell or external TCH handover: whenever a 44.018 HANDOVER COMPLETE message is
received
on Abis interface from the target cell for a TCH channel.
2) Intra-cell handover: whenever an 44.018 ASSIGNMENT COMPLETE message is received on Abis interface on
the target channel.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3: Success
Counter definition:
Number of TCH (in HR or FR usage) normal assignment successes, per TRX.
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.
External comment:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Established Phase
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
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.
MC736 = C736
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 a TCH channel (after successful seizure).
2) Whenever an 48.058 ERROR INDICATION message is received on Abis interface and leads to a loss of call.
External comment:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Established Phase
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
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.
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3: Failure
Counter definition:
Number of TCH (in HR or FR usage) normal assignment -execution failures due to MS access problem, per TRX.
MC746b = C746b
Trigger condition:
1) The timer T3107 in the BSS supervising the TCH channel seizure by the mobile expires.
2) The BSC receives a 44.018 ASSIGNMENT FAILURE on the old (SDCCH) channel during the normal
assignment
procedure except in case of multiband cell, when the normal assignment procedure is performed in the inner zone
and the ASSIGNMENT FAILURE is received with the cause "protocol error unspecified".
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3: Failure
Counter definition:
C812 = C612a + C612b + C612c + C612d
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Multiband
Domain: Traffic Load Sub domain-3:
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,
- the GSM850 and the DCS1900 bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850 and
DCS1900 bands", or,
- the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if the PLMN_FREQUENCY_BANDS parameter is
set to
"GSM900 and DCS1900 bands".
Trigger condition:
Whenever a 44.018 Classmark Change message in the context of any establishment cause different from location
update is received on Abis interface from the MS with a "Mobile Station Classmark 3" Information Element
specifying that the MS supports:
- the P-GSM (or E-GSM or R-GSM) and the DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is
set to
"GSM900 and DCS1800 bands", or,
- the GSM850 and the DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850 and
DCS1800 bands", or,
- the GSM850 and the DCS1900 bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850 and
DCS1900 bands", or,
- the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if the PLMN_FREQUENCY_BANDS parameter is
set to
"GSM900 and DCS1900 bands".
The counter is incremented only once per SCCP connection in the serving cell, i.e. on receipt of the first 44.018
CLASSMARK CHANGE message.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 44
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Number of suspend requests.
A request could lead to a success, a failure or a stop.
Trigger condition:
Emission of Suspend request 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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Number of suspensions successes.
Trigger condition:
Reception of Resume ack message from MFS.
External comment:
--
Type definition:
Set of counters related to the availability of the CCCH, SDCCH or TCH channels
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
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:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The averaged value (real) is rounded up or down to the
nearest integer value.
External comment:
--
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: Availability
Counter definition:
Average number of available TCH/PDCH timeslots for traffic usage (i.e. TCH (for HR or FR usage) or PDCH).
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The averaged value is rounded up or down to the nearest
integer value.
Note 1: "Available" has here to be understood as the operational state of a timeslot. The timeslot is available if it is
not "blocked" or "out of service".
Note 2: The dynamic SDCCH timeslots are not taken into account in this counter.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: SDCCH
Domain: Resource Availability & Usage Sub domain-3: Availability
Counter definition:
Average number of available static SDCCH sub-channels (i.e. on static SDCCH timeslots).
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The averaged value (real) is rounded up or down to the
nearest integer value.
Note: "Available" has here to be understood as the operational state of a timeslot. The timeslot is available if it is
not
"blocked" or "out of service".
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: CCCH
Domain: Resource Availability & Usage Sub domain-3: Availability
Counter definition:
Average number of available CCCH channels.
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The averaged value (real) is rounded up or down to the
nearest integer value.
External comment:
--
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 busy TCH radio timeslot (in FR or HR usage) 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:
--
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:
Maximum number of simultaneously busy TCH radio timeslots (in HR or FR usage) 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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: SDCCH
Domain: Resource Availability & Usage Sub domain-3: Usage
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:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. In order to provide one decimal place, the average value
(real)
is multiplied by ten and then rounded up or down to the nearest integer value.
Note that the counter value that is indicated in the ASCII file, which can be obtained via the OBSYNT interface,
still
has to be divided by 10, whereas the value that is provided at the user interface is the correct one.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: SDCCH
Domain: Resource Availability & Usage Sub domain-3: Usage
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:
--
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 free TCH and free dynamic SDCCH/8 radio timeslots belonging to the interference band 1.
This
number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The averaged value (real) is rounded up or down to the
nearest integer value.
External comment:
--
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 free TCH and free dynamic SDCCH/8 radio timeslots belonging to the interference band 2.
This
number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The average value (real) is rounded up or down to the
nearest integer value.
External comment:
--
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 free TCH and free dynamic SDCCH/8 radio timeslots belonging to the interference band 3.
This
number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The averaged value (real) is rounded up or down to the
nearest integer value.
External comment:
--
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 free TCH and free dynamic SDCCH/8 radio timeslots in FR or HR usage belonging to the
interference band 4. This number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The averaged value (real) is rounded up or down to the
nearest integer value.
External comment:
--
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 free TCH and free dynamic SDCCH/8 radio timeslots belonging to the interference band 5.
This
number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The average value (real) is rounded up or down to the
nearest integer value.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TRX_TS
Domain: Resource Availability & Usage Sub domain-3: Usage
Counter definition:
Cumulated time (in seconds) during which 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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: SDCCH
Domain: Resource Availability & Usage Sub domain-3:
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:
--
Type definition:
Set of counters related to the usage of the CCCH channel (PCH load, AGCH load, RACH load)
B8 TRX_TS 0
B9 TRX_TS 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: CCCH
Domain: Traffic Load Sub domain-3:
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:
--
B8 TRX_TS 0
B9 TRX_TS 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: CCCH
Domain: Traffic Load Sub domain-3:
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:
--
B8 TRX_TS 0
B9 TRX_TS 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: CCCH
Domain: Traffic Load Sub domain-3:
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:
--
B8 TRX_TS 0
B9 TRX_TS 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: CCCH
Domain: Traffic Load Sub domain-3:
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.
Type definition:
Set of counters related to the usage of the SDCCH channel
B8 TRX_TS 0
B9 TRX_TS 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: SDCCH
Domain: Resource Availability & Usage Sub domain-3: Usage
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:
--
B8 TRX_TS 0
B9 TRX_TS 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: SDCCH
Domain: Traffic Load Sub domain-3:
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.
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:
--
Type definition:
Set of counters releated to the usage of the TCH channel (in HR or FR usage)
B8 TRX_TS 0
B9 TRX_TS 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TCH
Domain: Resource Availability & Usage Sub domain-3: Usage
Counter definition:
Number of times a TCH radio timeslot or a dynamic SDCCH/8 timeslot is allocated in FR usage, for normal
assignment or handover.
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 or handover.
External comment:
--
B8 TRX_TS 0
B9 TRX_TS 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TCH
Domain: Resource Availability & Usage Sub domain-3: Usage
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:
--
B8 TRX_TS 0
B9 TRX_TS 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TCH
Domain: Traffic Load Sub domain-3:
Counter definition:
Time (in seconds) during which a TCH radio timeslot or a dynamic SDCCH/8 timeslot in FR usage 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 for the related TRX timeslot.
2) The counter stops being incremented after the reception of a 48.058 RF CHANNEL RELEASE
ACKNOWLEDGE
message or the expiry of timer T_RCR_ACK twice (after the sending of the 48.058 RF CHANNEL RELEASE
message) concerning the TCH channel previously activated on the related TRX timeslot.
External comment:
--
B8 TRX_TS 0
B9 TRX_TS 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TCH
Domain: Traffic Load Sub domain-3:
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.
For each channel allocation:
1) The counter starts being incremented after the sending of the 48.058 CHANNEL ACTIVATION message
concerning a dynamic SDCCH/8 timeslot or an half rate TCH sub-channel mapped either on the upper half or the
lower half of the related TRX timeslot.
2) The counter stops being incremented when no HR sub-channel is active anymore on the related TRX channel.
This is after the reception of a 48.058 RF CHANNEL RELEASE ACKNOWLEDGE message or the expiry of timer
T_RCR_ACK twice (after the sending of the 48.058 RF CHANNEL RELEASE message) or the BSC internal radio
resource release due to any BSS problem concerning the last HR TCH channel (or the dynamic SDCCH/8
timeslot)
which was active on the related TRX timeslot.
External comment:
--
B8 TRX_TS 0
B9 TRX_TS 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TCH
Domain: Traffic Load Sub domain-3:
Counter definition:
Time (in seconds) during which the TCH radio timeslot or the dynamic SDCCH/8 timeslot in FR usage is busy by
a
multiband mobile station.
2) The counter stops being incremented after the reception of a 48.058 RF CHANNEL RELEASE
ACKNOWLEDGE
message or the expiry of timer T_RCR_ACK twice (after the sending of the 48.058 RF CHANNEL RELEASE
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 65
Evolium
B8 TRX_TS 0
B9 TRX_TS 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TCH
Domain: Traffic Load Sub domain-3:
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.
A MS is considered as multiband if it supports:
- the P-GSM (or E-GSM or R-GSM) and the DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is
set to
"GSM900 and DCS1800 bands", or,
- the GSM850 and the DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850 and
DCS1800 bands", or,
- the GSM850 and the DCS1900 bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850 and
DCS1900 bands", or,
- the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if the PLMN_FREQUENCY_BANDS parameter is
set to
"GSM900 and DCS1900 bands".
Trigger condition:
The counter cumulates, over the Accumulation Period, per radio timeslot, all unit times during which the TCH HR
channel (or the dynamic SDCCH/8 timeslot) is busy.
For each channel allocation:
1) The counter starts being incremented after the sending of the 48.058 CHANNEL ACTIVATION message
concerning :
- an half rate TCH channel (or a dynamic SDCC/8 timeslot) mapped either on the upper half or the lower half of
the
related TRX timeslot.
- a mobile which has sent a 44.018 CLASSMARK CHANGE message with a "Mobile Station Classmark 3"
Information Element field specifying that it is a multiband MS. the MS supports:
- the P-GSM (or E-GSM or R-GSM) and the DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is
set to
"GSM900 and DCS1800 bands", or,
- the GSM850 and the DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850 and
DCS1800 bands", or,
- the GSM850 and the DCS1900 bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850 and
DCS1900 bands", or,
- the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if the PLMN_FREQUENCY_BANDS parameter is
set to
"GSM900 and DCS1900 bands".
2) The counter stops being incremented when no HR sub-channel (or the dynamic SDCCH/8 timeslot) concerning
a
multiband mobile is active anymore on the related TRX channel.
This is after the reception of a 48.058 RF CHANNEL RELEASE ACKNOWLEDGE message or the expiry of timer
T_RCR_ACK twice (after the sending of the 48.058 RF CHANNEL RELEASE message) or the BSC internal radio
resource release due to any BSS problem, concerning the last HR TCH channel (or the dynamic SDCCH/8
timeslot)
related to a multiband mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 66
Evolium
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.
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming Internal
Domain: Handover Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming Internal
Domain: Handover Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
Counter definition:
Number of intra cell TCH (in HR or FR usage) handover requests
Trigger condition:
Whenever the BSC process responsible for the handover procedure starts an intra cell TCH handover procedure.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
Counter definition:
Number of intra cell TCH (in HR or FR usage) handover attempts.nts,
Trigger condition:
44.018 ASSIGNMENT COMMAND is sent to the BTS for intra cell handover on TCH.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Outgoing Internal
Domain: Handover Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Outgoing Internal
Domain: Handover Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Traffic Load Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
Counter definition:
Number of incoming external TCH (in HR or FR usage) handover successes.
Trigger condition:
Whenever a 44.018 HANDOVER COMPLETE message is received on Abis interface from the target cell for a
TCH
channel that is involved in an external TCH handover.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
Counter definition:
MC43=C43, Number of incoming external TCH (in HR or FR usage) handover -execution failures due to MS
access
problem.
Trigger condition:
1) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "handover access
failure" is received on Abis interface from the target cell for a TCH channel during an external TCH handover.
2) Whenever the timer supervising the handover procedure on the target cell (T9113), expires during an external
TCH handover.
3) Whenever a 48.008 CLEAR COMMAND with a cause value of "radio interface failure - reversion to old
channel"
is received on A interface on the target BSC from the MSC during an external TCH handover.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 24. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 27 on TCH.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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
counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
Counter definition:
Number of outgoing external TCH (in HR or FR usage) handover requests.
Trigger condition:
Whenever a 48.008 HANDOVER REQUIRED message is sent on A interface to the MSC for a TCH 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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
Counter definition:
MC46=C46, Number of outgoing external TCH (in HR or FR usage) handover successes.
Trigger condition:
Whenever 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 for a TCH handover.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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).
Note 1: This counter counts both inter-PLMN and intra-PLMN handover events.
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
Number of intra-cell handover - attempts, with the cause 29 (TFO mismatch resolution, TFO optimisation).
MC461 = C461
Trigger condition:
Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 29 on TCH.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
Counter definition:
MC47=C47, 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.
Trigger condition:
Whenever a 44.018 HANDOVER FAILURE message is received on Abis interface from the serving cell , during
an
external TCH handover.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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).
Trigger condition:
Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 2. This counter is
incremented in the serving cell,
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
Number of inter-cell internal or external handovers attempts, with cause 3: "uplink level too low" 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 3. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
Number of inter-cell internal or external handover attempts, with cause 4: "downlink quality too low" on a TCH
channel (in HR or FR usage).
Trigger condition:
Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTS because of cause 4. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
Number of inter-cell internal or external handover attempts, with cause 5: "downlink level too low" on a TCH
channel (in HR or FR usage).
Trigger condition:
Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 5. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
Number of inter-cell internal or external handover attempts, with cause 6: "MS-BTS distance too long" on a TCH
channel (in HR or FR usage).
Trigger condition:
Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTS because of cause 6. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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).
Trigger condition:
Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 15.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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).
Trigger condition:
Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 16.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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).
Trigger condition:
Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTS because of cause 12. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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
counter
is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
Counter definition:
MC48=C48, 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).
Trigger condition:
Whenever the timer supervising the handover procedure on the serving cell (T8), expires during an external TCH
handover.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
Counter definition:
MC50=C50, Number of outgoing external TCH (in HR or FR usage) handover attempts.
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: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming Internal
Domain: Handover Sub domain-3:
Counter definition:
MC52=C52, Number of incoming internal inter-cell TCH (in HR or FR usage) handover successes.
Trigger condition:
Whenever a 44.018 HANDOVER COMPLETE message is received on Abis interface from the target cell for a
TCH
channel that is involved in an internal inter-cell TCH handover.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming Internal
Domain: Handover Sub domain-3:
Counter definition:
MC53=C53, 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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
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:
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
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: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming Internal
Domain: Handover Sub domain-3:
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).
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Outgoing Internal
Domain: Handover Sub domain-3:
Counter definition:
MC55a=C55a, Number of outgoing 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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Outgoing Internal
Domain: Handover Sub domain-3:
Counter definition:
MC56=C56, Number of outgoing internal inter-cell TCH (in HR or FR usage) handover successes.
Trigger condition:
Whenever a 44.018 HANDOVER COMPLETE message is received on Abis interface from the target cell , during
an
internal inter-cell TCH handover.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
Counter definition:
Number of intra-cell TCH (in HR or FR usage) handover -preparation failures due to congestion.
Trigger condition:
Whenever a internal intra-cell TCH handover cannot be performed, because there is no free TCH channel to
serve
the handover.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Outgoing Internal
Domain: Handover Sub domain-3:
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.
Trigger condition:
Whenever a 44.018 HANDOVER FAILURE message is received on Abis interface from the serving cell, during an
internal inter-cell TCH handover.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Outgoing Internal
Domain: Handover Sub domain-3:
Counter definition:
MC58=C58, 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).
Trigger condition:
Whenever the timer supervising the handover procedure (T3103) expires during an internal inter-cell TCH
handover.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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 is related to micro cell environment.
Trigger condition:
Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 7. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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 is related to micro cell environment.
Trigger condition:
Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTS because of cause 17. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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 is related to micro cell environment.
Trigger condition:
Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 18. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 14. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 10.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 11.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 13.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Outgoing Internal
Domain: Handover Sub domain-3:
Counter definition:
MC60=C60, Number of outgoing internal inter-cell TCH (in HR or FR usage) handover attempts.
Trigger condition:
Whenever the 44.018 HANDOVER COMMAND message is sent on Abis interface on the serving channel, during
an
internal inter-cell TCH handover procedure.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
Counter definition:
MC62=C62, Number of intra-cell TCH (in HR or FR usage) handover successes.
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
Counter definition:
MC63=C63, Number of intra-cell TCH (in HR or FR usage) handover execution failures due MS access problem;
the
mobile is lost.
Trigger condition:
Whenever the timer supervising the handover procedure (T3107) expires during an internal intra-cell.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
Counter definition:
MC67=C67, 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.
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC75=C75, Number of external handovers triggered by the MSC but not required by the BSS.
Trigger condition:
Whenever a 48.008 HANDOVER COMMAND message is received on A interface from the MSC and timer
T_HO_REQ_LOST is not running.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
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:
--
B8 LapD 0
B9 LapD 1
Technology: GSM Sub domain-1: Interface
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.
External comment:
--
B8 LapD 0
B9 LapD 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: Abis
Domain: Quality of Service Sub domain-3: LapD
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:
--
B8 LapD 0
B9 LapD 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: Abis
Domain: Resource Availability & Usage Sub domain-3: Availability
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:
--
B8 LapD 0
B9 LapD 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: Abis
Domain: Quality of Service Sub domain-3: LapD
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:
--
B8 LapD 0
B9 LapD 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: Abis
Domain: Quality of Service Sub domain-3: LapD
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:
--
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 received on the LapD link, excluding the re-transmissions.
Trigger condition:
Whenever an Information Frame is received on a logical LAPD link.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 100
Evolium
B8 LapD 0
B9 LapD 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: Abis
Domain: Quality of Service Sub domain-3: LapD
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:
--
B8 LapD 0
B9 LapD 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: Abis
Domain: Quality of Service Sub domain-3: LapD
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 101
Evolium
B8 X25 0
B9 X25 1
Technology: GSM Sub domain-1: Interface
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 102
Evolium
B8 X25 0
B9 X25 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: OMC-BSC
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:
--
B8 X25 0
B9 X25 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: OMC-BSC
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 103
Evolium
B8 X25 0
B9 X25 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: OMC-BSC
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 104
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Resource Availability & Usage Sub domain-3: Availability
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 105
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
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:
--
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: Layers1-2-3
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 106
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: Layers1-2-3
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:
--
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: Layers1-2-3
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 107
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: Layers1-2-3
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:
--
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: Layers1-2-3
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 108
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: Layers1-2-3
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:
--
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: Layers1-2-3
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 109
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: Layers1-2-3
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:
--
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: Layers1-2-3
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 110
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: Layers1-2-3
Counter definition:
Number of Negative Acknowledgment receieved on the N7 SL.
Trigger condition:
Whenever a Negative Acknowledgement (NACK) is received.
External comment:
--
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Resource Availability & Usage Sub domain-3: Availability
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 111
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Resource Availability & Usage Sub domain-3: Availability
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:
--
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
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:
1) Whenever an octet of the Signalling Information Field (SIF) is transmitted.
2) Whenever a Service Information Octet is transmitted.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 112
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: Layers1-2-3
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:
--
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: Layers1-2-3
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 113
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Traffic Load Sub domain-3: Layers1-2-3
Counter definition:
Number of octets re-transmitted on the N7 SL.
Trigger condition:
Whenever an octet has to be re-transmitted.
External comment:
--
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Traffic Load Sub domain-3: Layers1-2-3
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 114
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Traffic Load Sub domain-3: Layers1-2-3
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:
--
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Traffic Load Sub domain-3: Layers1-2-3
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 115
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Resource Availability & Usage Sub domain-3: Availability
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:
--
B8 N7 Link Set 0
B9 N7 Link Set 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Resource Availability & Usage Sub domain-3: Availability
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 116
Evolium
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
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).
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 117
Evolium
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).
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 or T8 expiry during external SDCCH handover
-48.008 CLEAR COMMAND message received with a cause value of "radio interface failure - reversion to old
channel" during external SDCCH handover.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 118
Evolium
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 |
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 |
|
: :
definition:
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)
External comment:
--
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
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 120
Evolium
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
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
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
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 121
Evolium
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
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
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
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 122
Evolium
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
Indicates whether or not a Radio Link Failure was detected or not.
This counter corresponds to the RL_FAILURE_INDICATOR field of the 48.058 PHYSICAL CONTEXT CONFIRM
message.
External comment:
--
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 123
Evolium
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
Indicates the sample rate value at the time the observation is collected.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 124
Evolium
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:
--
Observation
The RTCH channel type to which the Observation relates :
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 125
Evolium
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
Indicates the average receive uplink level of the serving cell, as used by the handover algorithm.
External comment:
--
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
Indicates the average receive downlink level of the serving cell, as used by the handover algorithm.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 126
Evolium
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
Indicates the average received Downlink Level of the serving cell, as used by the Power Budget algorithm.
External comment:
--
Observation
Indicates the average receive uplink quality of the serving cell, as used by the handover algorithm.
External comment:
--
Observation
Indicates the average receive downlink quality of the serving cell, as used by the handover algorithm.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 127
Evolium
Observation
Indicates the average distanc between Mobile and Base station, as used by the handover algorithm.
External comment:
--
Observation
Transmit power at the Mobile.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 128
Evolium
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
Transmit power at the BTS.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 129
Evolium
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 130
Evolium
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 131
Evolium
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 132
Evolium
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 133
Evolium
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 134
Evolium
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 135
Evolium
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 136
Evolium
Observation
Indicates the sample rate value at the time the observation is collected.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 137
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 138
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 139
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 140
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 141
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 142
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 143
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 144
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 145
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 146
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 147
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 148
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 149
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 150
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 151
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 152
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 153
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 154
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 155
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 156
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 157
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 158
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 159
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute BCCH Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The average receive level of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 160
Evolium
Observation
The Power Budget evaluation of reception of a neighboring cell related to the serving cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 161
Evolium
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.
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 162
Evolium
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 163
Evolium
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
- 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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 164
Evolium
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
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.
It should be noted that synchronized external handovers only occur when they are Intra-BSS.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 165
Evolium
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 166
Evolium
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 167
Evolium
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 168
Evolium
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 169
Evolium
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
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.
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 170
Evolium
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:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 171
Evolium
Observation
The last average Uplink Level of the serving cell.
External comment:
--
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:
--
Observation
The last average Downlink Level of the serving cell.
External comment:
--
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 172
Evolium
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:
--
Observation
The last average Downlink Power Budget of the serving cell.
External comment:
--
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
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 173
Evolium
Observation
The last average Uplink Quality of the serving cell.
External comment:
--
Observation
The last average Downlink Quality of the serving cell.
External comment:
--
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:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 174
Evolium
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The last average Distance of the serving cell.
External comment:
--
Observation
Transmit power at the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 175
Evolium
Observation
Transmit power at the BTS.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 176
Evolium
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:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 177
Evolium
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:
--
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
sub-channel field which is not significant is set to zero.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 178
Evolium
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 179
Evolium
Observation
Indicates whether the observed external handover is successful or not. Valid coding is provided below, all other
codings are invalid.
0: Successful handover
- 48.008 CLEAR COMMAND message received with a cause value of "handover successful" during external
handover
1: LAPD failure
2: Other BSS problems
- hardware failure (BSC or BTS or transmission equipment)
- software failure (BSC or BTS or transmission equipment)
3: MS access problems where the mobile reverts to the old channel
- 44.018 HANDOVER FAILURE message received during external handover
4: MS access problems where the mobile does not revert to the old channel
- T8 expiry during external handover
External comment:
--
Observation
Indicates the sample rate value at the time the observation is collected.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 180
Evolium
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
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
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 181
Evolium
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 182
Evolium
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 183
Evolium
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.
Observation
Indicates whether or not the observation record relates to an external incoming handover. Valid coding is provided
below, all other codings are invalid.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 184
Evolium
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
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
sub-channel field which is not significant is set to zero.
External comment:
--
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 185
Evolium
Observation
Indicates whether the observed external handover is successful or not. Valid coding is provided below, all other
codings are invalid.
0: Successful handover
- 48.008 CLEAR COMMAND message received with a cause value of "handover successful" during external
handover
1: LAPD failure
2: Other BSS problems
- hardware failure (BSC or BTS or transmission equipment)
- software failure (BSC or BTS or transmission equipment)
3: MS access problems where the mobile reverts to the old channel
- 44.018 HANDOVER FAILURE message received during external handover
4: MS access problems where the mobile does not revert to the old channel
- T8 expiry during external handover
External comment:
--
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.
It should be noted that synchronized external handovers only occur when they are Intra-BSS.
External comment:
--
Observation
Indicates the sample rate value at the time the observation is collected.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 186
Evolium
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 187
Evolium
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
Indicates the sample rate value at the time the observation is collected.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 188
Evolium
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 189
Evolium
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 190
Evolium
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 191
Evolium
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 192
Evolium
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 193
Evolium
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 194
Evolium
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 195
Evolium
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
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.
Observation
Indicates whether or not the observation record relates to an external outgoing handover. Valid coding is provided
below, all other codings are invalid.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 196
Evolium
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
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
Indicates the number of BSS generated 48.008 HANDOVER REQUIRED messages generated during the
handover
procedure.
External comment:
--
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 197
Evolium
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:
--
Observation
Indicates whether the observed external handover is successful or not. Valid coding is provided below, all other
codings are invalid.
0: Successful handover
- 48.008 CLEAR COMMAND message received with a cause value of "handover successful" during external
handover
1: LAPD failure
2: Other BSS problems
- hardware failure (BSC or BTS or transmission equipment)
- software failure (BSC or BTS or transmission equipment)
3: MS access problems where the mobile reverts to the old channel
- 44.018 HANDOVER FAILURE message received during external handover
4: MS access problems where the mobile does not revert to the old channel
- T8 expiry during external handover
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 198
Evolium
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
- 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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 199
Evolium
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 200
Evolium
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
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
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 201
Evolium
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The last average Uplink Level of the serving cell.
External comment:
--
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:
--
Observation
The last average Downlink Level of the serving cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 202
Evolium
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
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:
--
Observation
The last average Downlink Power Budget of the serving cell.
External comment:
--
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 203
Evolium
Observation
The last average Uplink Quality of the serving cell.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Observation
The last average Downlink Quality of the serving cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 204
Evolium
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:
--
Observation
The last 4 a Receive Levels of a neighboring cell as seen by the Mobile.
External comment:
--
Observation
The last average Distance of the serving cell.
External comment:
--
Observation
Transmit power at the Mobile.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 205
Evolium
Observation
Transmit power at the BTS.
External comment:
--
Observation
The Base Station Identity Code (BSIC) of a neighboring cell.
External comment:
--
Observation
The Absolute Radio Frequency Number of a neighboring cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 206
Evolium
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:
--
Observation
The RTCH channel type to which the Observation relates :
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 207
Evolium
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).
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).
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 208
Evolium
Observation
Describes how the RTCH channel is released. Viz. :
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 209
Evolium
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)
External comment:
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 210
Evolium
--
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
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
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 211
Evolium
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
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
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 212
Evolium
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
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
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
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 213
Evolium
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
Indicates whether or not a Radio Link Failure was detected or not.
This counter corresponds to the RL_FAILURE_INDICATOR field of the 48.058 PHYSICAL CONTEXT CONFIRM
message.
External comment:
--
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 214
Evolium
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
Indicates the sample rate value at the time the observation is collected.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 215
Evolium
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 216
Evolium
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
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:
--
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 217
Evolium
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
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:
--
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
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
interface to the MSC.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 218
Evolium
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
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:
--
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
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
interface to the MSC.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 219
Evolium
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
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
interface to the MSC.
External comment:
--
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 220
Evolium
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
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:
--
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 221
Evolium
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
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:
--
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
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
interface to the MSC.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 222
Evolium
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
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:
--
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
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
interface to the MSC.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 223
Evolium
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
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:
--
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 224
Evolium
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: BSSAP
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.
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
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.
External comment:
--
B8 A interface channel 0
B9 A interface channel 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Traffic Load Sub domain-3:
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.
For each channel allocation:
1) The counter starts being incremented when the A channel is activated (see C751)
2) The counter stops being incremented when the A channel is deallocated after the reception of a 48.058 RF
CHANNEL RELEASE ACKNOWLEDGE message or the expiry of timer T_RCR_ACK twice (after the sending of
the
48.058 RF CHANNEL RELEASE message).
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 225
Evolium
B8 A interface channel 0
B9 A interface channel 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Traffic Load Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 226
Evolium
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.
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Short Message Service
Sub domain-2: Point to Point
Domain: Quality of Service Sub domain-3: Success
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 227
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Short Message Service
Sub domain-2: Point to Point
Domain: Quality of Service Sub domain-3: Success
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Short Message Service
Sub domain-2: Point to Point
Domain: Quality of Service Sub domain-3: Success
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 228
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Short Message Service
Sub domain-2: Point to Point
Domain: Quality of Service Sub domain-3: Success
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Short Message Service
Sub domain-2: Point to Point
Domain: Quality of Service Sub domain-3: Failure
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 229
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Short Message Service
Sub domain-2: Point to Point
Domain: Quality of Service Sub domain-3: Failure
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Short Message Service
Sub domain-2: Point to Point
Domain: Quality of Service Sub domain-3: Failure
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 230
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Short Message Service
Sub domain-2: Point to Point
Domain: Quality of Service Sub domain-3: Failure
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 :
-"timer T200 expired (N200+1) times"
-"unsolicited DM response, multiple frame established state"
-"sequence error".
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 231
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 232
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: SCCP
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:
--
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 233
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Traffic Load Sub domain-3: SCCP
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:
--
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Traffic Load Sub domain-3: SCCP
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 234
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Traffic Load Sub domain-3: SCCP
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:
--
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Traffic Load Sub domain-3: SCCP
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 235
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Traffic Load Sub domain-3: SCCP
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:
--
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: SCCP
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 236
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Quality of Service Sub domain-3: SCCP
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 237
Evolium
Type definition:
Set of counters related to outgoing TCH handover provided per adjacency.
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.
Trigger condition:
Whenever 44.018HANDOVER COMMAND is sent to the MS via the fixed serving cell for an external or internal
inter-cell TCH handover towards the variable target cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 238
Evolium
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 successes.
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 : whenever 48.008 CLEAR COMMAND (cause= "handover successful") is received at the
serving BSC from the MSC during an external handover from the fixed serving cell to the target cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
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 -execution failures 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 fixed serving cell
during
an external or internal inter-cell TCH handover attempted towards the variable target cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 239
Evolium
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 -execution failures due to
MS
access problem, without reversion of the mobile to the old channel.
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
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 with emergency
cause.
Trigger condition:
Inter-cell HO, External HO : Whenever a 44.018 HANDOVER COMMAND is sent to the MS via the serving cell,
for an
outgoing handover cause 2, 3, 4, 5, 6, 7, 17, 18, 22 on a TCH channel, from the fixed serving cell to the variable
target cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 240
Evolium
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 with better cell
cause.
Trigger condition:
Inter-cell HO, External HO : Whenever a 44.018 HANDOVER COMMAND is sent to the MS via the serving cell,
for an
outgoing handover cause 12, 14, 21 on a TCH channel, from the fixed serving cell to the variable target cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
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 with traffic cause.
Trigger condition:
Inter-cell HO, External HO : Whenever a 44.018 HANDOVER COMMAND is sent to the MS via the serving cell,
for an
outgoing handover cause 23,24, 28 on a TCH channel, from the fixed serving cell to the variable target cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 241
Evolium
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 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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 242
Evolium
B8 Adjacency 0
B9 Adjacency-CGI 1
Technology: GSM Sub domain-1: Fixed target Cell
Sub domain-2:
Domain: Adjacency Sub domain-3:
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’).
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 243
Evolium
B8 Adjacency 0
B9 Adjacency-CGI 1
Technology: GSM Sub domain-1: Fixed target Cell
Sub domain-2:
Domain: Adjacency Sub domain-3:
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’).
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 244
Evolium
B8 Adjacency 0
B9 Adjacency-CGI 1
Technology: GSM Sub domain-1: Fixed target Cell
Sub domain-2:
Domain: Adjacency Sub domain-3:
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’).
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 245
Evolium
B8 Adjacency 0
B9 Adjacency-CGI 1
Technology: GSM Sub domain-1: Fixed target Cell
Sub domain-2:
Domain: Adjacency Sub domain-3:
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
2) External handover : whenever 48.008HANDOVER REQUEST ACK is sent to the MSC from the target BSC for
an
external TCH handover from the variable serving cell towards the fixed target cell. The Cell-identity of the serving
and target cells is provided in the 48.008HANDOVER REQUEST with 48.008 cause 2, 3, 4, 5, 6
Only handovers from a 2G cell shall be taken into account (if the field Cell Identifier discriminator in the I.E. Cell
Identifier (serving) of the 48.008 HANDOVER REQUEST is set to ‘0000’ or ‘0001’).
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 246
Evolium
B8 Adjacency 0
B9 Adjacency-CGI 1
Technology: GSM Sub domain-1: Fixed target Cell
Sub domain-2:
Domain: Adjacency Sub domain-3:
Counter definition:
Number of incoming 2G to 2G external and internal inter-cell TCH (in HR or FR usage) handover attempts, with
better cell cause.
Trigger condition:
1) Internal intercell handover : whenever 44.018HANDOVER COMMAND is sent to the MS via the variable
serving
cell for an internal inter-cell TCH handover towards the fixed target cell, with cause 12, 14, 21
2) External handover : whenever 48.008HANDOVER REQUEST ACK is sent to the MSC from the target BSC for
an
external TCH handover from the variable serving cell towards the fixed target cell. The Cell-identity of the serving
and target cells is provided in the 48.008HANDOVER REQUEST with 48.008 cause 12
Only handovers from a 2G cell shall be taken into account (if the field Cell Identifier discriminator in the I.E. Cell
Identifier (serving) of the 48.008 HANDOVER REQUEST is set to ‘0000’ or ‘0001’).
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 247
Evolium
B8 Adjacency 0
B9 Adjacency-CGI 1
Technology: GSM Sub domain-1: Fixed target Cell
Sub domain-2:
Domain: Adjacency Sub domain-3:
Counter definition:
Number of incoming 2G to 2G external and internal inter-cell TCH (in HR or FR usage) handover attempts, with
traffic cause.
Trigger condition:
1) Internal handover : whenever 44.018HANDOVER COMMAND is sent to the MS via the variable serving cell for
an internal inter-cell TCH handover towards the fixed target cell, with cause 23, 24, 28
2) External handover : whenever 48.008HANDOVER REQUEST ACK is sent to the MSC from the target BSC for
an
external TCH handover from the variable serving cell towards the fixed target cell. The Cell-identity of the serving
and target cells is provided in the 48.008HANDOVER REQUEST with 48.008 cause 15.
Only handovers from a 2G cell shall be taken into account (if the field Cell Identifier discriminator in the I.E. Cell
Identifier (serving) of the 48.008 HANDOVER REQUEST is set to ‘0000’ or ‘0001’).
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 248
Evolium
B8 Adjacency 0
B9 Adjacency-CGI 1
Technology: GSM Sub domain-1: Fixed target Cell
Sub domain-2:
Domain: Adjacency Sub domain-3:
Counter definition:
Number of incoming 2G to 2G external and internal inter-cell directed retries attempts, with Forced directed retry
cause.
Trigger condition:
1) Internal handover : whenever 44.018HANDOVER COMMAND is sent to the MS via the variable serving cell for
an internal inter-cell TCH handover towards the fixed target cell, with cause 20
2) External handover : whenever 48.008HANDOVER REQUEST ACK is sent to the MSC from the target BSC for
an
external TCH handover from the variable serving cell towards the fixed target cell. The Cell-identity of the serving
and target cells is provided in the 48.008HANDOVER REQUEST with 48.008 cause 13.
Only handovers from a 2G cell shall be taken into account (if the field Cell Identifier discriminator in the I.E. Cell
Identifier (serving) of the 48.008 HANDOVER REQUEST is set to ‘0000’ or ‘0001’).
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 249
Evolium
B8 Adjacency 0
B9 Adjacency-CGI 1
Technology: GSM Sub domain-1: Fixed target Cell
Sub domain-2:
Domain: Adjacency Sub domain-3:
Counter definition:
Number of incoming 2G to 2G external and internal inter-cell TCH (in HR or FR usage) handover attempts, with
unknown or missing cause.
Trigger condition:
1) Internal handover : whenever 44.018HANDOVER COMMAND is sent to the MS via the variable serving cell for
an internal inter-cell TCH handover towards the fixed target cell, with unknown or missing cause.
2) External handover : whenever 48.008HANDOVER REQUEST ACK is sent to the MSC from the target BSC for
an
external TCH handover from the variable serving cell towards the fixed target cell. The Cell-identity of the serving
and target cells is provided in the 48.008HANDOVER REQUEST with unknown or missing 48.008 cause, or
48.008
cause different from 2, 3, 4, 5, 6, 12, 13, 15.
Only handovers from a 2G cell shall be taken into account (if the field Cell Identifier discriminator in the I.E. Cell
Identifier (serving) of the 48.008 HANDOVER REQUEST is set to ‘0000’ or ‘0001’).
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 250
Evolium
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.
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Outgoing Internal
Domain: Handover Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 251
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 252
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 253
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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 counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 254
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Incoming Internal
Domain: Handover Sub domain-3:
Counter definition:
Number of incoming internal inter-cell SDCCH handover requests.
Trigger condition:
Whenever the BSC process responsible for the handover procedure selects a target cell (among a list of target
cells) for internal inter cell SDCCH handover.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 255
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Incoming Internal
Domain: Handover Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 256
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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
counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 257
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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
counter is incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 258
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
Number of SDCCH inter-cell internal or external handover attempts triggered with cause 2: "uplink quality too
low".
Trigger condition:
Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 2. This counter is
incremented in the serving cell.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
Number of SDCCH inter-cell internal or external handover attempts with cause 3: "uplink level too low".
Trigger condition:
Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 3. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 259
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
Number of SDCCH inter-cell internal or external handover attempts with cause 4: "downlink quality too low".
Trigger condition:
Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 4. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
Number of SDCCH inter-cell internal or external handover attempts triggered with cause 5: "downlink level too
low".
Trigger condition:
Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 5. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 260
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
Number of SDCCH inter-cell internal or external handover attempts with cause 6: "MS-BTS distance too long".
Trigger condition:
Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 6. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
Number of SDCCH intra-cell handover attempts with cause 15: "too high level interference on uplink".
Trigger condition:
Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 15.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 261
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
Number of SDCCH intra-cell handover attempts with cause 16: "too high level interference on downlink".
Trigger condition:
Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 16.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
Number of SDCCH inter-cell internal or external handover attempts with cause 12: "too low power budget".
Trigger condition:
Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTS because of cause 12. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 262
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 21. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 7. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 263
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 17. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
Whenever 44.018HANDOVER COMMAND is sent to the MS via the BTS because of cause 18. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 264
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTS because of cause 14. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
Whenever 44.018 HANDOVER COMMAND is sent to the MS via the BTS because of cause 20. This counter is
incremented in the serving cell.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 265
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
Counter definition:
MC81=C81, Number of incoming external SDCCH handover -preparation failures due to congestion.
Trigger condition:
Whenever a 48.008 HANDOVER FAILURE message with a cause value of "no radio resource available" is sent
on
A interface from the target BSC to the MSC during an external SDCCH handover.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 266
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 267
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
Counter definition:
Number of outgoing external SDCCH handover successes.
Trigger condition:
Whenever a 48.008 CLEAR COMMAND message with a cause of "handover successful" is received on A
interface on the serving BSC from the MSC for an external SDCCH handover.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 268
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 269
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
Counter definition:
Number of outgoing external SDCCH handover attempts.
Trigger condition:
Whenever the 44.018 HANDOVER COMMAND message is sent on Abis interface on the serving channel, during
an
external SDCCH handover procedure.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Incoming Internal
Domain: Handover Sub domain-3:
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
Sub-channel to allocate the handover to.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 270
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Incoming Internal
Domain: Handover Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Incoming Internal
Domain: Handover Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 271
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Outgoing Internal
Domain: Handover Sub domain-3:
Counter definition:
Number of outgoing internal inter-cell SDCCH handover requests.
Trigger condition:
Whenever the BSC process responsible for the handover procedure selects a target cell (among a list of target
cells) for internal inter cell SDCCH handover.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Outgoing Internal
Domain: Handover Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 272
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Outgoing Internal
Domain: Handover Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Outgoing Internal
Domain: Handover Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 273
Evolium
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.
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 274
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: External
Domain: Handover Sub domain-3: Outgoing
Counter definition:
Number of outgoing forced external directed retry (towards a TCH channel in HR or FR usage) successes.
Trigger condition:
Whenever 48.008CLEAR COMMAND (cause="handover successful") is received on the serving BSC for an
external forced directed retry.
Note: This counter counts both inter-PLMN and intra-PLMN directed retry events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Handover Sub domain-3: Outgoing
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 275
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: External
Domain: Handover Sub domain-3: Outgoing
Counter definition:
Number of outgoing normal external directed retry (towards a TCH channel in HR or FR usage) successes.
Trigger condition:
Whenever 48.008 CLEAR COMMAND (cause="handover successful") is received on the serving BSC for an
external normal directed retry.
Note: This counter counts both inter-PLMN and intra-PLMN directed retry events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Handover Sub domain-3: Outgoing
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 276
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Handover Sub domain-3: Outgoing
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: External
Domain: Handover Sub domain-3: Outgoing
Counter definition:
Number of outgoing forced external directed retry -execution failures due to MS access problem with reversion to
the old channel. The target TCH channel can be in HR or FR usage.
Trigger condition:
Whenever 44.018 HANDOVER FAILURE is received from the MS via the serving cell on the old channel
(SDCCH).
Note: This counter counts both inter-PLMN and intra-PLMN directed retry events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 277
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: External
Domain: Handover Sub domain-3: Outgoing
Counter definition:
Number of outgoing forced external directed retry -execution failures due to MS access problem without reversion
to the old channel. The target TCH channel can be in HR or FR usage.
Trigger condition:
Whenever the timer supervising the handover procedure (T8), expires.
Note: This counter counts both inter-PLMN and intra-PLMN directed retry events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Handover Sub domain-3: Outgoing
Counter definition:
Number of outgoing normal internal directed retry -execution failures due to MS access problem with reversion to
the old channel. The target TCH channel can be in HR or FR usage.
Trigger condition:
44.018HANDOVER FAILURE on SDCCH received from the MS via the serving cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 278
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Handover Sub domain-3: Outgoing
Counter definition:
Number of outgoing normal internal directed retry -execution failures due to MS access problem without reversion
to the old channel. The target TCH channel can be in HR or FR usage.
Trigger condition:
Timer T3103 expiry (this timer supervizes the 44.018HANDOVER COMMAND).
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: External
Domain: Handover Sub domain-3: Outgoing
Counter definition:
Number of outgoing normal external directed retry -execution failures due to MS access problem with reversion to
the old channel. The target TCH channel can be in HR or FR usage.
Trigger condition:
Whenever 44.018 HANDOVER FAILURE is received from the MS via the serving cell on the old channel
(SDCCH).
Note: This counter counts both inter-PLMN and intra-PLMN directed retry events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 279
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: External
Domain: Handover Sub domain-3: Outgoing
Counter definition:
Number of outgoing normal external directed retry -execution failures due to MS access problem without reversion
to the old channel. The target TCH channel can be in HR or FR usage.
Trigger condition:
Whenever the timer supervising the handover procedure (T8) expires.
Note: This counter counts both inter-PLMN and intra-PLMN directed retry events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Handover Sub domain-3: Outgoing
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 280
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: External
Domain: Handover Sub domain-3: Outgoing
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.
Note: This counter counts both inter-PLMN and intra-PLMN directed retry events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Handover Sub domain-3: Outgoing
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 281
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: External
Domain: Handover Sub domain-3: Outgoing
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.
Note: This counter counts both inter-PLMN and intra-PLMN directed retry events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Handover Sub domain-3: Outgoing
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 282
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: External
Domain: Handover Sub domain-3: Outgoing
Counter definition:
Number of outgoing forced external directed retry attempts. The target TCH channel can be in HR or FR usage.
Trigger condition:
Whenever a 44.018HANDOVER COMMAND is sent to the MS via the serving cell on the SDCCH channel for a
forced external directed retry.
Note: This counter counts both inter-PLMN and intra-PLMN directed retry events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Handover Sub domain-3: Outgoing
Counter definition:
Number of outgoing normal internal directed retry attempts. The target TCH channel can be in HR or FR usage.
Trigger condition:
Whenever a 44.018HANDOVER COMMAND is sent to the MS via the serving cell on the SDCCH channel for a
normal internal directed retry.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 283
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: External
Domain: Handover Sub domain-3: Outgoing
Counter definition:
Number of outgoing normal external directed retry attempts. The target TCH channel can be in HR or FR usage.
Trigger condition:
Whenever a 44.018HANDOVER COMMAND is sent to the MS via the serving cell on the SDCCH channel for a
normal external directed retry.
Note: This counter counts both inter-PLMN and intra-PLMN directed retry events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 284
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Handover Sub domain-3: Incoming
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Handover Sub domain-3: Incoming
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 285
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Handover Sub domain-3: Incoming
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Handover Sub domain-3: Incoming
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)
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 286
Evolium
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Telecom Procedure
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 287
Evolium
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Telecom Procedure
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 :
- entirely (i.e. for all cells of the list) : the BSC sends a REPORT SUCCESS to the CBC
- partially (i.e. for a part of the list) : the BSC returns a REPORT SUCCESS to the CBC
- not at all (i.e. for no cell) : the BSC returns a REPORT FAILURE to the CBC if the cause of the reject is the same
for all cells, otherwise a REPORT SUCCESS is returned.
When a REPORT SUCCESS is returned, the No-of-Broadcasts-completed-list optional Information Element
specifies
the number of cells successfully served by the request. This IE is not provided when no cells can be served.
Trigger condition:
Whenever a REPORT SUCCESS to a KILL MESSAGE is sent to the CBC, the counter is incremented by the
No-of-Broadcasts-completed-list optional IE (if not provided, the counter is not incremented, since it means that no
cells are served).
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 288
Evolium
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Short Message Service
Sub domain-2: Cell Broadcast
Domain: Quality of Service Sub domain-3: Failure
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 289
Evolium
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Short Message Service
Sub domain-2: Cell Broadcast
Domain: Quality of Service Sub domain-3: Failure
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 :
- entirely (i.e. for all cells of the list) : the BSC sends a REPORT SUCCESS to the CBC
- partially (i.e. for a part of the list) : the BSC returns a REPORT SUCCESS to the CBC
- not at all (i.e. for no cell) : the BSC returns a REPORT FAILURE to the CBC if the cause of the reject is the same
for all cells, otherwise a REPORT SUCCESS is returned.
When a REPORT SUCCESS is returned, the Failure-List optional Information Element specifies for each cell
whose
request has not been completed, the cause and diagnostic of the failure.
Trigger condition:
1) Whenever a WRITE REPLACE or a KILL MESSAGE request is totally rejected by REPORT FAILURE (then, for
all
cells with the same cause), the counter is incremented by the Cell-List IE value provided within the request
message.
2) Whenever a REPORT SUCCESS to a WRITE REPLACE or a KILL MESSAGE request is returned to the CBC,
the
counter is incremented by the number of cells provided within the Failure-List IE of the REPORT SUCCESS.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 290
Evolium
Type definition:
Set of counters describing result of radio measurements for a given cell / TRX.
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 291
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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
This calculation is done when 48.058 RF CHANNEL RELEASE is received for the observed call.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 292
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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
This calculation is done when 48.058 RF CHANNEL RELEASE is received for the observed call.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 293
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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
This calculation is done when 48.058 RF CHANNEL RELEASE is received for the observed call.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 294
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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
This calculation is done when 48.058 RF CHANNEL RELEASE is received for the observed call.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 295
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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:
Whenever a call verifies :
100*(BAD_COVERAGE_DL_SAMPLES / NUM_DL_SAMPLES) <= VQ_INTF_THRESHOLD
and
100*(INTERFERED_DL_SAMPLES / NUM_DL_SAMPLES) <= VQ_INTF_THRESHOLD
and
100*(BAD_QUALITY_DL_SAMPLES / NUM_DL_SAMPLES) > VQ_INTF_THRESHOLD
This calculation is done when 48.058 RF CHANNEL RELEASE is received for the observed call.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 296
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Number of calls with bad quality measurements and with bad FER measurements on the uplink path.
Trigger condition:
Whenever a call verifies :
100*(BAD_QUALITY_UL_SAMPLES / NUM_UL_SAMPLES) > VQ_INTF_THRESHOLD
and
100*(BAD_QUAL_BAD_FER_UL_SAMPLES / BAD_QUALITY_UL_SAMPLES) > VQ_FER_THRESHOLD
This calculation is done when 48.058 RF CHANNEL RELEASE is received for the observed call.
* NUM_UL_SAMPLES : total number of averages calculated on UL measurements during the call on the
considered
TRX
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 297
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Number of calls with bad quality measurements but with good FER measurements on the uplink path.
Trigger condition:
Whenever a call verifies :
100*(BAD_QUALITY_UL_SAMPLES / NUM_UL_SAMPLES) > VQ_INTF_THRESHOLD
and
100*(BAD_QUAL_GOOD_FER_UL_SAMPLES / BAD_QUALITY_UL_SAMPLES) > VQ_FER_THRESHOLD
This calculation is done when 48.058 RF CHANNEL RELEASE is received for the observed call.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 298
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Number of calls with fair quality measurements but with bad FER measurements on the uplink path.
Trigger condition:
Whenever a call verifies :
100*(FAIR_QUAL_BAD_FER_UL_SAMPLES / FAIR_QUALITY_UL_SAMPLES) > VQ_FER_THRESHOLD
This calculation is done when 48.058 RF CHANNEL RELEASE is received for the observed call.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 299
Evolium
Observation
Frequency band of the TRX.
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
Indicator whether a TRX overload occurred.
External comment:
--
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 300
Evolium
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.
External comment:
--
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:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TCH
Domain: Resource Availability & Usage Sub domain-3: Usage
Counter definition:
Number of successful TCH seizures for the concerned cell.
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 301
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 302
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 303
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Percentage of reported Timing Advance with a value above TA_STAT.
Trigger condition:
Whenever a 48.058 MEASUREMENT RESULT is sent by the BTS with Timing Advance > TA_STAT.
Observation
Greatest value of Timing Advance reported to the BSC for the concerned cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 304
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Total number of Extended Measurement Results.
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 305
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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.
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 306
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 307
Evolium
B9 TRX 1
B9 TRX 1
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 308
Evolium
B9 TRX 1
B9 TRX 1
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 309
Evolium
B9 TRX 1
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 310
Evolium
B9 TRX 1
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 311
Evolium
B9 TRX 1
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 312
Evolium
B9 TRX 1
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 313
Evolium
B9 TRX 1
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 314
Evolium
B9 TRX 1
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 315
Evolium
B9 TRX 1
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 316
Evolium
B9 TRX 1
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 317
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Table of 3x 8x10 results.
Each cell (i,j) of the table contains :
1) number of reports in which DL RXQUAL is equal to j and DL RXLEV is reported in level band I (Cij)
2) corresponding averaged value of BS power level :
For G2 BTS : corresponding averaged value of [BTS_MAX_OUTPUT_POWER - abs(BS_TXPWR)]
For Evolium BTS : corresponding averaged value of [ MAX_POWER_PER_TRX- abs(BS_TXPWR)].
BS_TXPWR is the BTS transmitted power defined relatively to the maximum absolute output power of the BTS.
BS_TXPWR is expressed in dB, whereas BTS_MAX_OUTPUT_POWER is expressed in dBm. Note that the
formula
is written independently of the coding used for the variables. The function abs() gives the absolute value of its
argument.
3) corresponding averaged value of Timing Advance
For Cij, the result is given as follows :
Cij=Vij x 254 / Max_i, where Vij represents the real number of measurements, and Max_i the greatest value of Vij,
for i given (see RMS4b).
Cij=0 indicates 'number of measurements = 0'
Cij=254 indicates 'number of measurements = Max_i'
Cij=255 is reserved to indicate overflow.
The values of the average BS power level (2) and the average Timing Advance (3) are directly given, both with a
precision of 0.25. 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.
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 318
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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 RMS4a.
Trigger condition:
External comment:
--
B9 TRX 1
External comment:
This counter is only reported for cells mapped on Evolium BTS.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 319
Evolium
B9 TRX 1
B9 TRX 1
i = 1...10
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 320
Evolium
B9 TRX 1
i = 1...10
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 321
Evolium
B9 TRX 1
i = 1...10
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 322
Evolium
B9 TRX 1
i = 1...10
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 323
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Table of 10x10 results
Each cell (i,j) of the table contains :
1) number of reports in which consecutive BFI counter is in BFI band j and UL RXLEV is reported in level band I
(Cij)
The result is given as follows :
Cij=Vij x 254 / Max_i, where Vij represents the real number of measurements, and Max_i the greatest value of Vij,
for i given (see RMS5b).
Cij=0 indicates 'number of measurements = 0'
Cij=254 indicates 'number of measurements = Max_i'
Cij=255 is reserved to indicate overflow.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 324
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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 RMS5a.
Trigger condition:
External comment:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Table of 10 results
Each cell (i) of the table contains :
1) number of reports in which Radio linkI counter is in S band i
The result is given as follows :
Ci=Vi x 254 / Max_i, where Vi represents the real number of measurements, and Max_i the greatest value of Vi
(see RMS6b).
Ci=0 indicates 'number of measurements = 0'
Ci=254 indicates 'number of measurements = Max_i'
Ci=255 is reserved to indicate overflow.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 325
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Greatest value of the Vi in RMS6a.
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 326
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Table of 10 results
Each cell (i) of the table contains :
1) number of reports in which Path Balance is in Path Balance band i
The result is given as follows :
Ci=Vi x 254 / Max_i, where Vi represents the real number of measurements, and Max_i the greatest value of Vi,
(see RMS7b).
Ci=0 indicates 'number of measurements = 0'
Ci=254 indicates 'number of measurements = Max_i'
Ci=255 is reserved to indicate overflow.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 327
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Greatest value of the Vi in RMS7a.
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 328
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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.
The result is given as follows :
Ci=Vi x 254 / RMS8b, where Vi represents the real number of measurements
Ci=0 indicates 'number of measurements = 0'
Ci=254 indicates 'number of measurements = Max_i'
Ci=255 is reserved to indicate overflow.
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 329
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Greatest value of the Vi in RMS8a.
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 330
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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.
The result is given as follows :
Ci=Vi x 254 / RMS9b, where Vi represents the real number of measurements
Ci=0 indicates 'number of measurements = 0'
Ci=254 indicates 'number of measurements = Max_i'
Ci=255 is reserved to indicate overflow.
Trigger condition:
Whenever a measurement report indicates that C/I value for the extended measurement frequency is included in
the corresponding interval.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 331
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: RMS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Greatest value of the Vi in RMS9a.
Trigger condition:
External comment:
--
RMSp80
Parameter Name : NEIGB_CELL_ID Type 31 : Radio Measurement Statistics
RMSp90
Parameter Name : Frequency ARFCN Type 31 : Radio Measurement Statistics
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 332
Evolium
RMSpa
Parameter Name : PAR_EN_BALANCED_CI Type 31 : Radio Measurement Statistics
RMSpb
Parameter Name : PAR_TA_STAT Type 31 : Radio Measurement Statistics
External comment:
--
RMSpc
Parameter Name : PAR_VQ_AVERAGE Type 31 : Radio Measurement Statistics
External comment:
--
RMSpd
Parameter Name : PAR_VQ_RXLEV Type 31 : Radio Measurement Statistics
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 333
Evolium
RMSpe
Parameter Name : PAR_VQ_RXQUAL Type 31 : Radio Measurement Statistics
External comment:
--
RMSpf
Parameter Name : PAR_VQ_RXQUAL_VS_RXFER Type 31 : Radio Measurement Statistics
External comment:
--
RMSpg
Parameter Name : PAR_VQ_GOOD_RXFER Type 31 : Radio Measurement Statistics
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 334
Evolium
RMSph
Parameter Name : PAR_VQ_BAD_RXFER Type 31 : Radio Measurement Statistics
External comment:
--
RMSpi
Parameter Name : PAR_VQ_INTF_THRESHOLD Type 31 : Radio Measurement Statistics
SFD reference : 3BK 10204 0470 DTZZA ("B7 counters improvements") Length 1
Measured unit: %
Parameter
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
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 335
Evolium
RMSpt1
Parameter Name : TAB_PAR_MEAS_C/I Type 31 : Radio Measurement Statistics
External comment:
--
RMSpt2
Parameter Name : TAB_PAR_MEAS_STAT_BFI Type 31 : Radio Measurement Statistics
External comment:
--
RMSpt3
Parameter Name : TAB_PAR_MEAS_STAT_S Type 31 : Radio Measurement Statistics
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 336
Evolium
RMSpt4
Parameter Name : TAB_PAR_MEAS_PATH_BALANCE Type 31 : Radio Measurement Statistics
External comment:
--
RMSpt5
Parameter Name : TAB_PAR_MEAS_LEVEL Type 31 : Radio Measurement Statistics
External comment:
--
RMSpt6
Parameter Name : TAB_PAR_MEAS_STAT_TA Type 31 : Radio Measurement Statistics
External comment:
This counter is only reported for cells mapped on Evolium BTS.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 337
Evolium
RMSpw1
Parameter Name : BS_TX_PWRMAX Type 31 : Radio Measurement Statistics
RMSpw2
Parameter Name : MS_TX_PWRMAX Type 31 : Radio Measurement Statistics
B9 TRX 1
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 338
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3:
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 339
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3:
Counter definition:
Number of incoming external TCH (in HR or FR usage) handover successes including a change of the (TCH)
frequency band.
Trigger condition:
Whenever a 44.018 HANDOVER COMPLETE message is received on Abis interface from the target cell for a
TCH
channel that is involved in an external TCH handover with a change of the frequency band.
Remark: The change of the (TCH) frequency band for an incoming external handover can only be detected and
taken into account if the adjacency link is defined in both directions. In case of multiband cells, the BCCH
frequency
band of the serving cell will be taken as reference.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 340
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3:
Counter definition:
Number of outgoing external TCH (in HR or FR usage) handover attempts including a change of the (TCH)
frequency band.
Trigger condition:
Whenever the 44.018 HANDOVER COMMAND message is sent on Abis interface on the serving channel, during
an
external TCH handover procedure including a change of the (TCH) frequency band.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
In case of multiband cells, the BCCH frequency band of the target cell will be taken as reference.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 341
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3:
Counter definition:
Number of outgoing external TCH (in HR or FR usage) handover successes including a change of the (TCH)
frequency band.
Trigger condition:
Whenever 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 for a TCH handover including a change of the (TCH) frequency band.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
In case of multiband cells, the BCCH frequency band of the target cell will be taken as reference.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3:
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.
In case of multiband cells, the BCCH frequency band of the target cell will be taken as reference.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 342
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3:
Counter definition:
Number of incoming internal TCH (in HR or FR usage) handover successes including a change of the (TCH)
frequency band.
Trigger condition:
Whenever a 44.018 HANDOVER COMPLETE message is received on Abis interface from the target cell for a
TCH
channel that is involved in an internal inter-cell TCH handover including a change of the (TCH) frequency band.
In case of multiband cells, the BCCH frequency band of the target cell will be taken as reference.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3:
Counter definition:
Number of outgoing internal TCH (in HR or FR usage) handover attempts including a change of the (TCH)
frequency
band.
Trigger condition:
Whenever the 44.018 HANDOVER COMMAND message is sent on Abis interface on the serving channel, during
an
internal inter-cell TCH handover procedure including a change of the (TCH) frequency band.
In case of multiband cells, the BCCH frequency band of the target cell will be taken as reference.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 343
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3:
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.
In case of multiband cells, the BCCH frequency band of the target cell will be taken as reference.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 344
Evolium
B9 Common cell 1
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.
This counter is only reported for cells mapped on Evolium BTS.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 345
Evolium
B9 Common cell 1
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:
This counter is only reported for cells mapped on Evolium BTS.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 346
Evolium
Type definition:
Set of counters related to Voice Group Call Services (VGCS).
B9 Common cell 2
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 347
Evolium
B9 Common cell 2
External comment:
--
B9 Common cell 2
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 348
Evolium
B9 Common cell 2
B9 Common cell 2
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 349
Evolium
B9 Common cell 2
B9 Common cell 2
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 350
Evolium
B9 Common cell 2
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:
--
B9 Common cell 2
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 351
Evolium
B9 Common cell 2
B9 Common cell 2
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 352
Evolium
B9 BSC 2
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 353
Evolium
B9 Common cell 2
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 354
Evolium
B9 Common cell 2
B9 Common cell 2
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 355
Evolium
B9 Common cell 2
B9 Common cell 2
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 356
Evolium
B9 BSC 2
B9 Common cell 2
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 357
Evolium
B9 Common cell 2
B9 Common cell 2
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 358
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
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: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 359
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
Counter definition:
Number of immediate assignment successes for Mobile Originating procedure.
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 360
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
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".
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
Counter definition:
case: Supplementary Service
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION message is received from a CELL, with the L3 INFORMATION
field
containing a 44.018 L3 message with an MIE message type set to CM SERVICE REQUEST and with an MIE CM
service type set to "Supplementary Service".
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 361
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
Counter definition:
case: Location Update request ("follow on" procedure)
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION message is received from a CELL, with the L3 INFORMATION
field
containing a 44.018 L3 message with an MIE message type set to LOCATION UPDATING REQUEST and with
an MIE
Location updating type not set to a RESERVED value and a bit FOR set to 1.
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
Counter definition:
case: CM Re-establishment procedure
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION message is received from a CELL, with the L3 INFORMATION
field
containing a 44.018 L3 message with an MIE message type set to CM RE-ESTABLISHMENT REQUEST
message.
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 362
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 363
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
Counter definition:
case: normal or emergency call establishment
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION message is received from a CELL, with the L3 INFORMATION
field
containg a 44.018 L3 message with an MIE message type set to CM SERVICE REQUEST and an MIE CM
service
type set to either :
- "emergency call establishment",
- or "mobile originating call establishment"
This counter is incremented only if the L3 info message received has to be forwarded to the MSC.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Success
Counter definition:
case: Mobile originated LCS procedure on SDCCH
Trigger condition:
Whenever an 48.058 ESTABLISH INDICATION message is received from a cell, with the L3 INFORMATION field
containing a 44.018 L3 message with an MIE message type set to CM SERVICE REQUEST and with an MIE CM
service type set to "Location Services" (LCS).
This counter is incremented only if the L3 info message received has to be forwarded to the MSC
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 364
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: SDCCH
Domain: Quality of Service Sub domain-3: Success
Counter definition:
MC03=C03, Number of outgoing SDCCH handover (any kind) successes.
Trigger condition:
External SDCCH handover: whenever 48.008 CLEAR COMMAND (cause= "handover successful") is received on
the serving BSC on the SDCCH channel.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 365
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: SDCCH
Domain: Quality of Service Sub domain-3: Failure
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: SDCCH
Domain: Quality of Service Sub domain-3: Success
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 366
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC1040=C440+C445
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 367
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC1044=C444+C446
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC1050=C450+C454
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 368
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Established Phase
Sub domain-2: SDCCH
Domain: Quality of Service Sub domain-3: Failure
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Established Phase
Sub domain-2: SDCCH
Domain: Quality of Service Sub domain-3: Failure
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 369
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
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').
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 370
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
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:
i) upon the sending of a 48.008 QUEUING INDICATION message if the queuing is authorised by the MSC, or,
ii) when the handover request is queued in the cell if the queuing is not authorised by the MSC and the request
has
its pre-emption indicator set (provided that the flag EN_TCH_PREEMPT is set to 'Enable').
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3:
Counter definition:
Number of normal assignment requests for TCH establishment (in HR or FR usage).
Trigger condition:
Whenever an 48.008 ASSIGNMENT REQUEST message for a normal TCH assignment is received from the MSC
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 371
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3:
Counter definition:
Number of normal assignment commands for TCH establishment (in HR or FR usage).
Trigger condition:
Whenever an 44.018 ASSIGNMENT
COMMANDmessage for a normal TCH assignment is sent
to the MS.
External comment:
--
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 372
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Quality of Service Sub domain-3: Success
Counter definition:
MC142e=C142a+C142c
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Quality of Service Sub domain-3: Failure
Counter definition:
MC142f=C142b+C142d
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 373
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Directed Retry
Domain: Traffic Load Sub domain-3: Internal
Counter definition:
MC144e=C144a+C144c
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Directed Retry
Domain: Traffic Load Sub domain-3: External
Counter definition:
MC144f=C144b+C144d
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 374
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Handover
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Traffic Load Sub domain-3:
Counter definition:
Number of immediate assignment plus SDCCH normal assignments -whose SDCCH channel is allocated by the
BSC.
Trigger condition:
Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent on Abis Interface to activate an
SDCCH
channel for any purpose other than handover.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 375
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Immediate Assignment
Domain: Quality of Service Sub domain-3: Failure
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 376
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
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.
Trigger condition:
1) Whenever the BSC receives on Abis interface from the target cell negative acknowledgment to the TCH
channel
activation involved in the handover procedure.
2) Whenever the timer supervising the Channel Activation procedure (T9103) expires on the target cell during
activation of a TCH channel involved in the handover procedure.
3) Whenever an 48.058 ERROR REPORT message with a cause value of "O&M intervention" is received on Abis
interface from either the serving or the target cell during the external or internal inter-cell handover procedure and
leads to a transaction failure.
4) Whenever an 48.058 ERROR REPORT message with a cause value of "O&M intervention" is received on Abis
interface on either the old or the new channel during the internal intra-cell handover procedure and leads to a
transaction failure.
5) Whenever an 48.058 ERROR REPORT message on SAPI 0 with a cause value of "message sequence error"
is
received on Abis interface from the serving cell between the sending of the 48.058 CHANNEL ACTIVATION
message and the reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGMENT during the internal
inter-cell
TCH handover and leads to a transaction failure.
6) Whenever an 48.058 ERROR REPORT message on SAPI 0 with a cause value of "message sequence error"
is
received on Abis interface on the old channel between the sending of the 48.058 CHANNEL ACTIVATION
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
problems which are internal to the BSS.
However, due to the current implementation which does not allow to be aware of the origin of the failure, O&M
operator actions will also be counted.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 377
Evolium
unit:
External comment: :
mechanism: --
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Established Phase
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
Counter definition:
2. It may happen that the counter can not be incremented since it is implemented within the faulty entity. Number
of TCH (in HR or FR usage) drops in TCH established phase due to BSS problem.
It may happen that several causes of failures mentioned below are detected consecutively. In that case, the
counter will only be incremented once, as soon as the call is released.
Trigger condition:
1) Whenever an 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 an 48.058 ERROR REPORT message on SAPI 0 with a cause value of "message sequence error"
is
received on Abis interface after TCH seizure and leads to a loss of call.
3) Whenever a LAPD failure is reported to the Layer 3 of the BSC (for an RSL supporting a TCH transaction after
successful TCH seizure) and leads to a loss of call.
4) Whenever a TCH call release is initiated by the BSS O&M FAULT MANAGEMENT application part or by the
BSS
TELECOM application part as the result of a system defense action which may be due to BSS equipment failures
external to the BSC (e.g. RSL failure or CU recovery failure), or due to BSC internal hardware problems (e.g. TCU
failure or DTC failure) or due to BSC internal software problems (e.g. inconsistencies detected between software
modules or lack of software resources (memory, timer reference, file reference...) or communication problems
between different processor boards).
Notes :
1. TCH call releases which are due to O&M operator actions on BTS or BSC should not be counted. Indeed, in
case
of numerous failures due to O&M commands, this counter will overestimate failures which are due to problems
which are internal to the BSS.
However, due to the current implementation which does not allow to be aware of the origin of the failure, O&M
operator actions will also be counted.
2. It may happen that the counter can not be incremented since it is implemented within the faulty entity.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 378
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Handover Sub domain-3: Incoming
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 379
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Handover
Domain: Traffic Load Sub domain-3: TCH
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:
The counter is incremented on the target cell whenever the 48.058 CHANNEL ACTIVATION message of a TCH
channel is about to be sent during any handover procedure.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 380
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: DTAP Assignment
Domain: Quality of Service Sub domain-3: Success
Counter definition:
MC161 = C161a + C161b
Trigger condition:
Whenever a 44.018 CONNECT ACK is received on Abis interface.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Established Phase
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
Counter definition:
MC162 = C162a + C162b + C162c
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 381
Evolium
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.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 382
Evolium
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3: Failure
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).
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Short Message Service
Sub domain-2: Point to Point
Domain: Quality of Service Sub domain-3: Success
Counter definition:
MC196=C190+C191+C192+C193
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 383
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Short Message Service
Sub domain-2: Point to Point
Domain: Quality of Service Sub domain-3: Failure
Counter definition:
MC197=C194a+C194b+C194c+C195
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
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:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The averaged value (real) is rounded up or down to the
nearest integer value.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 384
Evolium
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: Availability
Counter definition:
Average number of available TCH/PDCH timeslots for traffic usage (i.e. TCH (for HR or FR usage) or PDCH).
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The averaged value is rounded up or down to the nearest
integer value.
Note 1: "Available" has here to be understood as the operational state of a timeslot. The timeslot is available if it is
not "blocked" or "out of service".
Note 2: The dynamic SDCCH timeslots are not taken into account in this counter.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: SDCCH
Domain: Resource Availability & Usage Sub domain-3: Availability
Counter definition:
Average number of available static SDCCH sub-channels (i.e. on static SDCCH timeslots).
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The averaged value (real) is rounded up or down to the
nearest integer value.
Note: "Available" has here to be understood as the operational state of a timeslot. The timeslot is available if it is
not
"blocked" or "out of service".
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 385
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: CCCH
Domain: Resource Availability & Usage Sub domain-3: Availability
Counter definition:
Average number of available CCCH channels.
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The averaged value (real) is rounded up or down to the
nearest integer value.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 386
Evolium
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 busy TCH radio timeslot (in FR or HR usage) 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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 387
Evolium
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:
Maximum number of simultaneously busy TCH radio timeslots (in HR or FR usage) 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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: SDCCH
Domain: Resource Availability & Usage Sub domain-3: Usage
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 388
Evolium
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 free TCH and free dynamic SDCCH/8 radio timeslots belonging to the interference band 1.
This
number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The averaged value (real) is rounded up or down to the
nearest integer value.
External comment:
--
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 free TCH and free dynamic SDCCH/8 radio timeslots belonging to the interference band 2.
This
number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The average value (real) is rounded up or down to the
nearest integer value.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 389
Evolium
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 free TCH and free dynamic SDCCH/8 radio timeslots belonging to the interference band 3.
This
number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The averaged value (real) is rounded up or down to the
nearest integer value.
External comment:
--
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 free TCH and free dynamic SDCCH/8 radio timeslots in FR or HR usage belonging to the
interference band 4. This number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The averaged value (real) is rounded up or down to the
nearest integer value.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 390
Evolium
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 free TCH and free dynamic SDCCH/8 radio timeslots belonging to the interference band 5.
This
number is updated upon the receipt of 48.058 RF RESOURCE INDICATION.
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The average value (real) is rounded up or down to the
nearest integer value.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TRX_TS
Domain: Resource Availability & Usage Sub domain-3: Usage
Counter definition:
Cumulated time (in seconds) during which 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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 391
Evolium
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: A channel
Domain: Resource Availability & Usage Sub domain-3: Availability
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:
--
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Traffic Load Sub domain-3: SCCP
Counter definition:
MC350=C253+C254
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 392
Evolium
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Traffic Load Sub domain-3: SCCP
Counter definition:
MC351=C255+C256
Trigger condition:
External comment:
--
B8 BSC 0
B9 BSC 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: A channel
Domain: Resource Availability & Usage Sub domain-3: Availability
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 393
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TCH
Domain: Resource Availability & Usage Sub domain-3: Usage
Counter definition:
MC370A= SUM(all TRX_TS of the TRX) (C370A)
Trigger condition:
External comment:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TCH
Domain: Resource Availability & Usage Sub domain-3: Usage
Counter definition:
MC370B= SUM(all TRX_TS of the TRX) (C370B)
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 394
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TCH
Domain: Traffic Load Sub domain-3:
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:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TCH
Domain: Traffic Load Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 395
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TCH
Domain: Traffic Load Sub domain-3:
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.
Trigger condition:
The counter cumulates over the Accumulation Period, per radio timeslot, all unit times during which the TCH FR
channel in the GSM frequency band is busy. For each channel allocation: The counter starts being incremented
after the sending of the 48.058 CHANNEL ACTIVATION message to the cell concerning a full rate TCH channel
for
the related TRX timeslot. The counter stops being incremented after the reception of a 48.058 RF CHANNEL
RELEASE ACKNOWLEDGE message or the expiry of timer T_RCR_ACK twice (after the sending of the 48.058
RF
CHANNEL RELEASE message) concerning the TCH channel previously activated on the related TRX timeslot.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 396
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TCH
Domain: Traffic Load Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 397
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TCH
Domain: Traffic Load Sub domain-3:
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.
Trigger condition:
The counter cumulates over the Accumulation Period, per radio timeslot, all unit times during which the TCH FR
channel in the DCS/PCS frequency band is busy. For each channel allocation: The counter starts being
incremented after the sending of the 48.058 CHANNEL ACTIVATION message to the cell concerning a full rate
TCH
channel for the related TRX timeslot. The counter stops being incremented after the reception of a 48.058 RF
CHANNEL RELEASE ACKNOWLEDGE message or the expiry of timer T_RCR_ACK twice (after the sending of
the
48.058 RF CHANNEL RELEASE message) concerning the TCH channel previously activated on the related TRX
timeslot.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 398
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TCH
Domain: Traffic Load Sub domain-3:
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
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:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: TCH
Domain: Traffic Load Sub domain-3:
Counter definition:
MC381= SUM (over all TRX_TS of the TRX) (C381A+C381B)
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 399
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: SDCCH
Domain: Resource Availability & Usage Sub domain-3: Usage
Counter definition:
MC390=SUM (all TRX_TS of the TRX) C39, C39 is NB_TIMES_SDCCH_BUSY in type 4.
Trigger condition:
External comment:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: SDCCH
Domain: Traffic Load Sub domain-3:
Counter definition:
MC400= SUM (all TRX_TS of the TRX) C40
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 400
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 401
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 27 on TCH.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 402
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
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 1: This counter counts both inter-PLMN and intra-PLMN handover events.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 403
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
Number of intra-cell handover - attempts, with the cause 29 (TFO mismatch resolution, TFO optimisation).
MC461 = C461
Trigger condition:
Whenever 44.018 ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 29 on TCH.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
Counter definition:
Number of inter-PLMN TCH outgoing handover or directed retry requests.
Trigger condition:
Whenever a 48.008 HANDOVER REQUIRED message is sent to the MSC on A interface for an external TCH
handover or an external directed retry triggered towards a cell belonging to a PLMN different from the PLMN of
the
serving cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 404
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
Counter definition:
Number of inter-PLMN TCH outgoing handover or directed retry attempts.
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 cell belonging to a PLMN different from the PLMN of
the
serving cell.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
Counter definition:
Number of inter-PLMN TCH outgoing handover or directed retry successes.
Trigger condition:
Whenever a 48.008 CLEAR COMMAND message with Cause "Handover successful" is received from the MSC
on
the A interface for an external TCH handover or an external directed retry triggered towards a cell belonging to a
PLMN different from the PLMN of the serving cell.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 405
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 406
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
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:
--
B9 Common cell 1
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 407
Evolium
B9 Common cell 1
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
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:
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 408
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
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: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Incoming Internal
Domain: Handover Sub domain-3:
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).
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 409
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Handover Sub domain-3: Incoming
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)
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
Counter definition:
Number of intra-cell TCH (in HR or FR usage) handover -preparation failures due to congestion.
Trigger condition:
Whenever a internal intra-cell TCH handover cannot be performed, because there is no free TCH channel to
serve
the handover.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 410
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 10.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 11.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 411
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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:
Whenever 44.018ASSIGNMENT COMMAND is sent to the MS via the BTS because of cause 13.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 412
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3: Failure
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.008ASSIGNMENT FAILURE (cause: "no radio resource
available") for a TCH channel because no TCH is available and either the queing is disabled in the BSC (T11=0
and
QUEUE_ANYWAY=0, or T11_forced=0 and QUEUE_ANYWAY=1), or the queing is enabled,
QUEUE_ANYWAY=0,
and the MSC does not request a queuing.
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3: Failure
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:
The counter is incremented upon the sending of 48.008ASSIGNMENT FAILURE (cause: "no radio resource
available") for a TCH channel because the queue is full and no request of lower priority can be dequeued.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 414
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3: Failure
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.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 415
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3: Failure
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 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.008ASSIGMENT FAILURE (cause: "no radio resource
available") for a dequeued TCH request (i.e. normal assignment) due to the receipt of a higher priority request.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 416
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
Counter definition:
Number of TCH drops during the execution of any TCH outgoing handover, per TRX.
MC621 = C621
Trigger condition:
1) Inter-cell TCH handover: whenever the timer supervising the handover procedure (T3103) expires.
2) External TCH handover: whenever the timer supervising the handover procedure on the serving cell (T8)
expires.
3) Intra-cell TCH handover: whenever the timer supervising the handover procedure (T3107) expires.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
Counter definition:
MC642=C42+C82
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 417
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
Counter definition:
MC643=C43+C83
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
Counter definition:
MC645a = C45a + C85a
Trigger condition:
Whenever a 48.008 HANDOVER REQUIRED message is sent on A interface from the serving cell to the MSC for
a
TCH handover (C45a) or an SDCCH handover (C85a). 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.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 418
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
Counter definition:
MC646=C46+C86
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
Counter definition:
MC647=C47+C87
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 419
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
Counter definition:
MC648=C48+C88
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Outgoing External
Domain: Handover Sub domain-3:
Counter definition:
MC650=C50+C90
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 420
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Incoming Internal
Domain: Handover Sub domain-3:
Counter definition:
MC652=C52+C92
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Incoming Internal
Domain: Handover Sub domain-3:
Counter definition:
MC653=C53+C93
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 421
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Outgoing Internal
Domain: Handover Sub domain-3:
Counter definition:
MC655a=C55a+C95a
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Outgoing Internal
Domain: Handover Sub domain-3:
Counter definition:
MC656=C56+C96
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 422
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Outgoing Internal
Domain: Handover Sub domain-3:
Counter definition:
MC657=C57+C97
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Outgoing Internal
Domain: Handover Sub domain-3:
Counter definition:
MC658=C58+C98
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 423
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Outgoing Internal
Domain: Handover Sub domain-3:
Counter definition:
MC660=C60+C100
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
Counter definition:
MC662=C62+C102
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 424
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
Counter definition:
MC663=C63+C103
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
Counter definition:
MC667=C67+C107
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 425
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC670=C470+C510
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC671=C471+C511
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 426
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC672=C472+C512
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC673=C473+C513
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 427
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC674=C474+C514
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC675=C75+C115
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 428
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC676=C476+C516
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC677=C477+C517
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 429
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC678=C478+C518
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC679=C479+C519
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 430
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
Counter definition:
Number of TCH normal assignments requests from FR only mobiles.
Trigger condition:
Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call with only GSM speech coding
algorithm
version 1 full rate allowed.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
Counter definition:
Number of TCH normal assignments requests from dual rate mobiles.
Trigger condition:
Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call with only GSM speech coding
algorithm
version 1 full rate and GSM speech coding algorithm version 1 half rate allowed.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 431
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
Counter definition:
Number of TCH normal assignment requests from AMR mobiles.
Trigger condition:
Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call with GSM speech coding algorithm
version 3 full rate or half rate allowed.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 432
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
Counter definition:
number of TCH normal assignment/mode modify in FR 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 FR channel with GSM
speech coding algorithm version 1, not related to handover.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 433
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
Counter definition:
number of TCH normal assignment/mode modify in EFR 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 FR channel with GSM
speech coding algorithm version 2, not related to handover.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 434
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Traffic Load Sub domain-3:
Counter definition:
Number of TCH (in HR or FR usage) normal assignment -whose RTCH channel is allocated in the BSC, per TRX.
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.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
Counter definition:
number of TCH normal assignment/mode modify in FR 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 FR channel with GSM
speech coding algorithm version 3, not related to handover.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 435
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
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
speech coding algorithm version 3, not related to handover.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: Service
Domain: Resource Availability & Usage Sub domain-3:
Counter definition:
number of TCH normal assignment/mode modify for data - whose channel is allocated in the BSC.
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 436
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Resource Allocation & Management
Sub domain-2: E-GSM
Domain: Resource Availability & Usage Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 437
Evolium
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.
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 for a
TCH
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.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 438
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
Counter definition:
Nb of outgoing TCH handover -preparation failures due to congestion, per TRX. Intracell, internal intercell and
external handovers are counted together.
MC711 = C711
Trigger condition:
1) Intracell HO : Whenever an intra-cell TCH handover cannot be performed, because there is no free TCH
channel
to allocate the handover to.
2) Internal inter-cell HO : Whenever a internal inter-cell TCH handover cannot be performed, because there is no
free TCH channel to allocate the handover to.
3) External HO : Whenever a 48.008 HANDOVER REQUIRED REJECT with cause "no radio resource available"
is
received from the MSC by the serving BSC for an outgoing external TCH HO.
Note : the counter will be incremented for external TCH HO if and only if the parameter RESP_REQ is set to 1.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 439
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Success
Counter definition:
Nb of outgoing TCH handover successes, per TRX. Intracell, internal intercell and external handovers are counted
together.
MC712 = C712
Trigger condition:
1) External HO: whenever 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
3) Internal intra-cell HO: whenever 44.018ASSIGNMENT COMPLETE is received from the MS via the cell on the
TCH
channel
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 440
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
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.
MC713 = C713
Trigger condition:
1) External HO : Whenever a 44.018 HANDOVER FAILURE message is received on Abis interface from the
serving
cell , during an external TCH handover.
2) Internal inter-cell HO : Whenever a 44.018 HANDOVER FAILURE message is received on Abis interface from
the serving cell, during an internal inter-cell TCH handover.
3) Intracell HO : Whenever a 44.018 ASSIGNMENT FAILURE message is received on Abis interface on the
serving
channel, during an internal intra-cell TCH handover.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 441
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
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.
MC714 = C714
Trigger condition:
1) External TCH HO : Whenever the timer supervising the handover procedure on the serving cell (T8), expires
during an external TCH handover.
2) Internal intercell TCH HO : Whenever the timer supervising the handover procedure (T3103) expires during an
internal inter-cell TCH handover.
3) Intracell TCH HO : Whenever the timer supervising the handover procedure (T3107) expires during an internal
intra-cell
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Directed Retry
Sub domain-2: Internal
Domain: Quality of Service Sub domain-3: Success
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 442
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Handover
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Success
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,
the external directed retries are counted by this counter.
MC717b = C717b
Trigger condition:
1) Internal inter-cell or external TCH handover: whenever a 44.018 HANDOVER COMPLETE message is
received
on Abis interface from the target cell for a TCH channel.
2) Intra-cell handover: whenever an 44.018 ASSIGNMENT COMPLETE message is received on Abis interface on
the target channel.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3: Success
Counter definition:
Number of TCH (in HR or FR usage) normal assignment successes, per TRX.
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.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 443
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Established Phase
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
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.
MC736 = C736
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 a TCH channel (after successful seizure).
2) Whenever an 48.058 ERROR INDICATION message is received on Abis interface and leads to a loss of call.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 444
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Established Phase
Sub domain-2: TCH
Domain: Quality of Service Sub domain-3: Failure
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.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 445
Evolium
B8 TRX 0
B9 TRX 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3: Failure
Counter definition:
Number of TCH (in HR or FR usage) normal assignment -execution failures due to MS access problem, per TRX.
MC746b = C746b
Trigger condition:
1) The timer T3107 in the BSS supervising the TCH channel seizure by the mobile expires.
2) The BSC receives a 44.018 ASSIGNMENT FAILURE on the old (SDCCH) channel during the normal
assignment
procedure except in case of multiband cell, when the normal assignment procedure is performed in the inner zone
and the ASSIGNMENT FAILURE is received with the cause "protocol error unspecified".
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC785a=C585a+C605a
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 446
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC785d=C585d+C605d
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC785e=C585e+C605e
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 447
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Cause
Domain: Handover Sub domain-3:
Counter definition:
MC785f=C585f+C605f
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: SDCCH
Domain: Resource Availability & Usage Sub domain-3: Availability
Counter definition:
Average number of available dynamic SDCCH/8 timeslots.
Trigger condition:
At Accumulation Period expiry, all observations of this counter done at each polling period are averaged, i.e.
summed and divided by the number of observations. The averaged value is rounded up or down to the nearest
integer value.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 448
Evolium
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 busy dynamic SDCCH/8 timeslots allocated as TCH (in FR or HR usage).
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:
--
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:
Maximum number of busy dynamic SDCCH/8 timeslots allocated as TCH (in FR or HR usage).
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 449
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: SDCCH
Domain: Resource Availability & Usage Sub domain-3: Usage
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: SDCCH
Domain: Resource Availability & Usage Sub domain-3: Usage
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 450
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: SDCCH
Domain: Resource Availability & Usage Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: CCCH
Domain: Traffic Load Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 451
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: CCCH
Domain: Traffic Load Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: CCCH
Domain: Traffic Load Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 452
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: CCCH
Domain: Traffic Load Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
Counter definition:
MC81=C81, Number of incoming external SDCCH handover -preparation failures due to congestion.
Trigger condition:
Whenever a 48.008 HANDOVER FAILURE message with a cause value of "no radio resource available" is sent
on
A interface from the target BSC to the MSC during an external SDCCH handover.
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 453
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3: Failure
Counter definition:
C812 = C612a + C612b + C612c + C612d
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
Counter definition:
MC820=C220+C310
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 454
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Incoming External
Domain: Handover Sub domain-3:
Counter definition:
MC821=C221+C311
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Incoming Internal
Domain: Handover Sub domain-3:
Counter definition:
MC830=C230+C330
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 455
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Incoming Internal
Domain: Handover Sub domain-3:
Counter definition:
MC831=C231+C331
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 456
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Multiband
Domain: Traffic Load Sub domain-3:
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,
- the GSM850 and the DCS1900 bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850 and
DCS1900 bands", or,
- the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if the PLMN_FREQUENCY_BANDS parameter is
set to
"GSM900 and DCS1900 bands".
Trigger condition:
Whenever a 44.018 Classmark Change message in the context of any establishment cause different from location
update is received on Abis interface from the MS with a "Mobile Station Classmark 3" Information Element
specifying that the MS supports:
- the P-GSM (or E-GSM or R-GSM) and the DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is
set to
"GSM900 and DCS1800 bands", or,
- the GSM850 and the DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850 and
DCS1800 bands", or,
- the GSM850 and the DCS1900 bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850 and
DCS1900 bands", or,
- the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if the PLMN_FREQUENCY_BANDS parameter is
set to
"GSM900 and DCS1900 bands".
The counter is incremented only once per SCCP connection in the serving cell, i.e. on receipt of the first 44.018
CLASSMARK CHANGE message.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 457
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
Counter definition:
MC870=C270+C360
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2: Intra
Domain: Handover Sub domain-3:
Counter definition:
MC871=C271+C361
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 458
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: CCCH
Domain: Traffic Load Sub domain-3:
Counter definition:
MC8A= SUM (all TRX_TS of the Cell) C8A
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: CCCH
Domain: Traffic Load Sub domain-3:
Counter definition:
MC8B= SUM (all TRX_TS of the Cell) C8B
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 459
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: CCCH
Domain: Traffic Load Sub domain-3:
Counter definition:
MC8C= SUM (all TRX_TS of the cell) C8C
Trigger condition:
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Channel
Sub domain-2: CCCH
Domain: Traffic Load Sub domain-3:
Counter definition:
MC8D= SUM (all TRX_TS of the cell) C8D
Trigger condition:
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 460
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Number of suspend requests.
A request could lead to a success, a failure or a stop.
Trigger condition:
Emission of Suspend request 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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 461
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Number of suspensions successes.
Trigger condition:
Reception of Resume ack message from MFS.
External comment:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH
Sub domain-2: Incoming Internal
Domain: Handover Sub domain-3:
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
Sub-channel to allocate the handover to.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 462
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3:
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).
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 463
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 464
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: Telecom Procedure
Sub domain-2: Normal Assignment
Domain: Quality of Service Sub domain-3:
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).
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 465
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2:
Domain: Handover Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2:
Domain: Handover Sub domain-3:
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 466
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2:
Domain: Handover Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: GSM Sub domain-1: SDCCH+TCH
Sub domain-2:
Domain: Handover Sub domain-3:
Counter definition:
Number of incoming external SDCCH and TCH HO attempts from a UMTS system.
Trigger condition:
Whenever 48.008HANDOVER REQUEST ACK is sent by the target BSC containing the 44.018HANDOVER
COMMAND towards the target cell.
Only handovers from a UMTS system shall be taken into account (if the field Cell Identifier discriminator in the I.E.
Cell Identifier (serving) of the corresponding 48.008 HANDOVER REQUEST is set to ‘1011’)
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 467
Evolium
B9 Common cell 1
B9 Common cell 1
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 468
Evolium
B9 Common cell 1
B9 Common cell 1
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 469
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: LCS Sub domain-1: LCS
Sub domain-2:
Domain: Quality of Service Sub domain-3: SCCP
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: LCS Sub domain-1: LCS
Sub domain-2:
Domain: Quality of Service Sub domain-3: SCCP
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 470
Evolium
B8 Common cell 0
B9 Common cell 1
Technology: LCS Sub domain-1: LCS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
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:
--
B8 Common cell 0
B9 Common cell 1
Technology: LCS Sub domain-1: LCS
Sub domain-2:
Domain: Quality of Service Sub domain-3:
Counter definition:
Number of LCS abort requests received from the MSC in CS domain.
Trigger condition:
Whenever a 48.008 PERFORM LOCATION ABORT message is received by the BSC from the MSC.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 471
Evolium
B9 Common cell 2
B9 Common cell 2
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 472
Evolium
B9 Common cell 2
B9 Common cell 2
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 473
Evolium
B9 Common cell 2
B9 Common cell 2
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 474
Evolium
B9 Common cell 2
B9 Common cell 2
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 475
Evolium
B9 Common cell 2
B9 Common cell 2
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 476
Evolium
B9 Common cell 2
B8 N7 Signalling Link 0
B9 N7 Signalling Link 1
Technology: GSM Sub domain-1: Interface
Sub domain-2: A
Domain: Resource Availability & Usage Sub domain-3: Availability
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:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 477
Evolium
B8 Adjacency 0
B9 Adjacency-CGI 1
Technology: GSM Sub domain-1: BSC
Sub domain-2:
Domain: Adjacency Sub domain-3:
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.
Only handovers from a 2G cell shall be taken into account (if the field Cell Identifier discriminator in the I.E. Cell
Identifier (serving) of the 48.008 HANDOVER REQUEST is set to ‘0000’ or ‘0001’).
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 478
Evolium
B8 Adjacency 0
B9 Adjacency-CGI 1
Technology: GSM Sub domain-1: BSC
Sub domain-2:
Domain: Adjacency Sub domain-3:
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.
Only handovers from a 2G cell shall be taken into account (if the field Cell Identifier discriminator in the I.E. Cell
Identifier (serving) of the 48.008 HANDOVER REQUEST is set to ‘0000’ or ‘0001’).
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 479
Evolium
B8 Adjacency 0
B9 Adjacency-CGI 1
Technology: GSM Sub domain-1: BSC
Sub domain-2:
Domain: Adjacency Sub domain-3:
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.
Only handovers from a 2G cell shall be taken into account (if the field Cell Identifier discriminator in the I.E. Cell
Identifier (serving) of the 48.008 HANDOVER REQUEST is set to ‘0000’ or ‘0001’).
Note: This counter counts both inter-PLMN and intra-PLMN handover events.
External comment:
--
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 480
Evolium
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.
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 481
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 482
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 483
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 484
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 485
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 486
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 487
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 488
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 489
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 490
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 491
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 493
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 494
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 495
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 496
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 497
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 498
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 499
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 500
Evolium
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
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 501
Evolium
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
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 502
Evolium
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
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 503
Evolium
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
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
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 504
Evolium
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
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 505
Evolium
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
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 506
Evolium
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
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
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 507
Evolium
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_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
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 508
Evolium
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
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
HO149 RXLEV 12
HO1498 BSIC 14
HO1499 FREQ 14
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 509
Evolium
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
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
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
HO32 AV_RXQUAL_UL_HO (12) 12
HO347 BSIC 12
HO348 FREQ 12
HO349 RXLEV 12
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 510
Evolium
HO38 BS_TXPWR 12
HO398 BSIC 14
HO399 FREQ 14
HO40 SIGNALLING_TRAFFIC_IND 13
HO41 INCOMING_HO_IND 13
HO4100 RXLEV 14
HO42 HO_REQUEST_TIME_STAMP 13
HO43 NEW_CHANNEL_ID 13
HO43a NEW_RTCH_TYPE 13
HO44 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
HO547 BSIC 12
HO548 FREQ 12
HO549 RXLEV 12
HO598 BSIC 14
HO599 FREQ 14
HO5a OLD_RTCH_TYPE 12
HO6 NEW_CHANNEL_ID 12
HO60 SIGNALLING_TRAFFIC_IND 14
HO61 OUTGOING_HO_IND 14
HO6100 RXLEV 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
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 511
Evolium
HO65 SUCCESS_FAILURE_IND 14
HO68 HO_CAUSE 14
HO698 BSIC 14
HO699 FREQ 14
HO6a NEW_RTCH_TYPE 12
HO7 SUCCESS_FAILURE_IND 12
HO7100 RXLEV 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
HO80a A_LEV_MCHO 14
HO8100 RXLEV 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
HO898 BSIC 14
HO899 FREQ 14
HO90 AV_RXQUAL_DL_HO (12) 14
HO91 A_RANGE_HO 14
HO9100 RXLEV 14
HO94 MS_TXPWR 14
HO947 BSIC 12
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 512
Evolium
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
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 513
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 514
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 515
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 516
Evolium
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 517
Evolium
N1.1 TIME_N7_ALIGNED 9
N1.10 NB_N7_CHANGEOVER 9
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 518
Evolium
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
R01a RTCH_TYPE 11
R03 RECEIVED_TIMESTAMP 11
R04 AV_RXLEV_UL_HO (11) 11
R1013 BSIC 11
R1014 BCCH_FREQ 11
R1015 AV_RXLEV_NCELL 11
R1016 PBGT 11
R11 BS_TXPWR 11
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 519
Evolium
R1113 BSIC 11
R1114 BCCH_FREQ 11
R1115 AV_RXLEV_NCELL 11
R1116 PBGT 11
R113 BSIC 11
R114 BCCH_FREQ 11
R115 AV_RXLEV_NCELL 11
R116 PBGT 11
R12 BTSNUM 11
R1213 BSIC 11
R1214 BCCH_FREQ 11
R1215 AV_RXLEV_NCELL 11
R1216 PBGT 11
R1313 BSIC 11
R1314 BCCH_FREQ 11
R1315 AV_RXLEV_NCELL 11
R1316 PBGT 11
R1413 BSIC 11
R1414 BCCH_FREQ 11
R1415 AV_RXLEV_NCELL 11
R1416 PBGT 11
R1513 BSIC 11
R1514 BCCH_FREQ 11
R1515 AV_RXLEV_NCELL 11
R1516 PBGT 11
R1613 BSIC 11
R1614 BCCH_FREQ 11
R1615 AV_RXLEV_NCELL 11
R1616 PBGT 11
R17 SAMPLE_RATE 11
R1713 BSIC 11
R1714 BCCH_FREQ 11
R1715 AV_RXLEV_NCELL 11
R1716 PBGT 11
R1813 BSIC 11
R1814 BCCH_FREQ 11
R1815 AV_RXLEV_NCELL 11
R1816 PBGT 11
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 520
Evolium
R1913 BSIC 11
R1914 BCCH_FREQ 11
R1915 AV_RXLEV_NCELL 11
R1916 PBGT 11
R2013 BSIC 11
R2014 BCCH_FREQ 11
R2015 AV_RXLEV_NCELL 11
R2016 PBGT 11
R2113 BSIC 11
R2114 BCCH_FREQ 11
R2115 AV_RXLEV_NCELL 11
R2116 PBGT 11
R213 BSIC 11
R214 BCCH_FREQ 11
R215 AV_RXLEV_NCELL 11
R216 PBGT 11
R2213 BSIC 11
R2214 BCCH_FREQ 11
R2215 AV_RXLEV_NCELL 11
R2216 PBGT 11
R2313 BSIC 11
R2314 BCCH_FREQ 11
R2315 AV_RXLEV_NCELL 11
R2316 PBGT 11
R2413 BSIC 11
R2414 BCCH_FREQ 11
R2415 AV_RXLEV_NCELL 11
R2416 PBGT 11
R2513 BSIC 11
R2514 BCCH_FREQ 11
R2515 AV_RXLEV_NCELL 11
R2516 PBGT 11
R2613 BSIC 11
R2614 BCCH_FREQ 11
R2615 AV_RXLEV_NCELL 11
R2616 PBGT 11
R2713 BSIC 11
R2714 BCCH_FREQ 11
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 521
Evolium
R2715 AV_RXLEV_NCELL 11
R2716 PBGT 11
R2813 BSIC 11
R2814 BCCH_FREQ 11
R2815 AV_RXLEV_NCELL 11
R2816 PBGT 11
R2913 BSIC 11
R2914 BCCH_FREQ 11
R2915 AV_RXLEV_NCELL 11
R2916 PBGT 11
R3013 BSIC 11
R3014 BCCH_FREQ 11
R3015 AV_RXLEV_NCELL 11
R3016 PBGT 11
R3113 BSIC 11
R3114 BCCH_FREQ 11
R3115 AV_RXLEV_NCELL 11
R3116 PBGT 11
R313 BSIC 11
R314 BCCH_FREQ 11
R315 AV_RXLEV_NCELL 11
R316 PBGT 11
R3213 BSIC 11
R3214 BCCH_FREQ 11
R3215 AV_RXLEV_NCELL 11
R3216 PBGT 11
R413 BSIC 11
R414 BCCH_FREQ 11
R415 AV_RXLEV_NCELL 11
R416 PBGT 11
R513 BSIC 11
R514 BCCH_FREQ 11
R515 AV_RXLEV_NCELL 11
R516 PBGT 11
R613 BSIC 11
R614 BCCH_FREQ 11
R615 AV_RXLEV_NCELL 11
R616 PBGT 11
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 522
Evolium
R713 BSIC 11
R714 BCCH_FREQ 11
R715 AV_RXLEV_NCELL 11
R716 PBGT 11
R813 BSIC 11
R814 BCCH_FREQ 11
R815 AV_RXLEV_NCELL 11
R816 PBGT 11
R913 BSIC 11
R914 BCCH_FREQ 11
R915 AV_RXLEV_NCELL 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
RMS44a AMR_FR_UL_BAD 31
RMS44b MAX_AMR_FR_UL_BAD 31
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 523
Evolium
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
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
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 524
Evolium
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
S02 CHAN_SEIZ_TIME 10
S03 CHAN_RELEASE_TIME 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
S26 SAMPLE_RATE 10
T02 CHANNEL_SEIZURE_TIME 15
T03 CHANNEL_RELEASE_TIME 15
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 525
Evolium
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
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
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 526
Evolium
X3.23 NB_X25_OUT_CALL_ABNORM_CLOSED 8
Edition: 7 Released BSC Counters 3BK 11203 0102 DSZZA Page 527