Alcatel BSC Counters Catalogue _B10

8/11/2019 Alcatel BSC Counters Catalogue _B10

1/630

Alcatel-Lucent

15/01/2009

BSC COUNTERSCATALOGUE B10

Edition: 13 Released BSC Counters Catalogue 3BK 11203 0135 DSZZA


2/630

Alcatel-Lucent

Type number: Counter - 1

Type name: Traffic measurementsType scope (per BSS): One or several cells

Candidate for Standard No

Type limitations (per BSS):1) The union of all observed cells per BSS for the detailed measurement types 1, 2, 3, 4, 5, 6, 19 (ifused as Detailed), 26, 28 (if used as Detailed), 29 (if used as Detailed), 31 (if used as detailed), 34 (ifused as Detailed) must not exceed 40 cells.

Type definition:Set of counters related to the traffic evaluation per telecom procedures

C01 Type 1 : Traffic measurements

Counter Name : NB_IMM_ASS_SUCC_MT Counter Integer

SFD reference :

No reference.

Length:

4Data collection Cumulative Measured number

Release Measured object Package

B10 Common cell 1B8 Common cell 0B9 Common cell 1

Technology: GSM Sub domain-1: Telecom Procedure (QoS)Sub domain-2: Immediate Assignment

Domain: Quality of Service Sub domain-3: Success

Counter definition:Number of immediate assignment plus SDCCH normal assignment successes for Mobile Terminating procedure.

Trigger condition:Whenever an 48.058 ESTABLISH INDICATION message is received from a CELL, with the L3_INFORMATION

field including a 44.018 PAGING RESPONSE message.

External comment:--

Edition: 13 Released BSC Counters Catalogue 3BK 11203 0135 DSZZA Page 2


3/630

Alcatel-Lucent


Counter Name : NB_IMM_ASS_SUCC_MO Counter Integer

SFD reference : No reference. Length: 4Data collection Cumulative Measured number

Release

Measured object Package




Counter definition:Number of immediate assignment successes for Mobile Originating procedure.

MC02 = C02 = C02a+C02b+C02c+C02d+C02e+C02f+C02g+C02h+C02i.The following counters C02a/b/c/d/e/f/g/h/i provide the distribution of the MO telecom procedures on SDCCH.

Trigger condition:

External comment:--

C02a Type 1 : Traffic measurements

Counter Name : NB_IMM_ASS_SUCC_MO_LOC_UPD Counter IntegerSFD reference : No reference. Length: 4Data collection Cumulative Measured number


B10

Common cell

1B8

Common cell

0B9 Common cell 1



Counter definition:case: Location Update request (except the "follow on" procedure)Trigger condition:Whenever an 48.058 ESTABLISH INDICATION message is received from a cell, with the L3 INFORMATION fieldcontaining a 44.018 L3 message with an MIE message type set to LOCATION UPDATING REQUEST and with

anMIE 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:

--



4/630

Alcatel-Lucent

C02b Type 1 : Traffic measurements

Counter Name : NB_IMM_ASS_SUCC_MO_SMS Counter Integer


Release





Counter definition:case: SMS procedure on SDCCHTrigger 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 MIECM 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:--

C02c Type 1 : Traffic measurements

Counter Name : NB_IMM_ASS_SUCC_MO_SUP_SERV Counter IntegerSFD reference : No reference. Length: 4Data collection Cumulative Measured number

Release





Counter definition:case: Supplementary ServiceTrigger 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 MIECM 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:--



5/630

Alcatel-Lucent

C02d Type 1 : Traffic measurements

Counter Name : NB_IMM_ASS_SUCC_MO_FOLLOW_ON Counter Integer


Release





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 withan 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:--

C02e Type 1 : Traffic measurements

Counter Name : NB_IMM_ASS_SUCC_MO_CM_REEST Counter IntegerSFD reference : No reference. Length: 4

Data collection Cumulative

Measured number





Counter definition:case: CM Re-establishment procedureTrigger 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 REQUESTmessage.This counter is incremented only if the L3 info message received has to be forwarded to the MSC.

External comment:--



6/630

Alcatel-Lucent

C02f Type 1 : Traffic measurements

Counter Name : NB_IMM_ASS_SUCC_MO_L3INFO_UNKNOW Counter Integer


Release





Counter definition:MC02f=C02f, number of immediate assignment successes for Mobile Originationg procedure, in case of L3 Info(within 48.058 ESTABLISH INDICATION) unknown by the BSC but transferred to the MSC.

Trigger condition:

External comment:--

C02g Type 1 : Traffic measurements

Counter Name : NB_IMM_ASS_SUCC_MO_IMSI_DETACH Counter IntegerSFD reference : No reference. Length: 4Data collection Cumulative Measured number



Technology:

GSM

Sub domain-1:

Telecom Procedure (QoS)Sub domain-2: Immediate Assignment


Counter definition:MC02g=C02g, number of immediate assignment successes for Mobile Originationg procedure, in case of IMSIDetach Indication.

Trigger condition:Whenever an 48.058 ESTABLISH INDICATION message is received from a CELL, with L3_INFORMATION fieldcontaining a 44.018 L3 message with an MIE message type set to IMSI DETACH INDICATION. This counter isincremented only if the L3 info message received has to be forwarded to the MSC.

External comment:--



7/630

Alcatel-Lucent

C02h Type 1 : Traffic measurements

Counter Name : NB_IMM_ASS_SUCC_MO_CALL_EST Counter Integer


Release





Counter definition:case: normal or emergency call establishmentTrigger 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 CMservice 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:--

C02i Type 1 : Traffic measurements

Counter Name : NB_IMM_ASS_SUCC_MO_LCS Counter Integer

SFD reference :

3BK 10204 0540 DTZZA ("Location services (LCS)")

Length:

4


Measured number

Release





Counter definition:case: Mobile originated LCS procedure on SDCCHTrigger condition:

Whenever an 48.058 ESTABLISH INDICATION message is received from a cell, with the L3 INFORMATION fieldcontaining 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:--



8/630

Alcatel-Lucent


Counter Name : NB_OUT_SDCCH_HO_SUCC Counter Integer

SFD reference : 3BK 10204 0413 DSZZA ("PM Counters Improvements in B6") Length: 4


Measured number

Release



Technology: GSM Sub domain-1: HandoverSub domain-2: SDCCH


Counter definition:MC03=C03, Number of outgoing SDCCH handover (any kind) successes.Trigger condition:External SDCCH handover in the following cases:

1/ 48.008 CLEAR COMMAND (cause= "handover successful") is received on the serving BSC.

2/ 48.008 CLEAR COMMAND (cause= "normal event/call control") received while T8 is running.

Note: This counter counts both inter-PLMN and intra-PLMN handover events.

External comment:--


Counter Name : NB_IMM_ASS_PREP_FAIL_CONG Counter IntegerSFD reference : No reference. Length: 4


Measured number




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:

--



9/630

Alcatel-Lucent


Counter Name : NB_SDCCH_DROP_OUT_HO Counter Integer


Release



Technology: GSM Sub domain-1: HandoverSub domain-2: SDCCH


Counter definition:MC07=C07, Number of SDCCH drops during any outgoing SDCCH handover.Trigger condition:Internal inter-cell SDCCH handover: whenever the timer supervising the handover procedure (T3103) expires.

External comment:

--


Counter Name : NB_INC_SDCCH_HO_SUCC Counter Integer




Technology:

GSM

Sub domain-1:

HandoverSub domain-2: SDCCH


Counter definition:MC10=C10, Number of incoming SDCCH handover (any kind) successes.Trigger condition:Internal inter-cell or external SDCCH handover: whenever a 44.018 HANDOVER COMPLETE message is

receivedon Abis interface from the target cell for an SDCCH Sub-channel.


External comment:

--



10/630

Alcatel-Lucent


Counter Name : NB_SDCCH_DROP_EST_PHAS_BSS_PB Counter Integer


Release



Technology: GSM Sub domain-1: Established PhaseSub domain-2: SDCCH


Counter definition:MC137=C137, Number of SDCCH drops in SDCCH established phase due to BSS problem.It may happen thatseveral causes of failures mentioned below are detected consecutively. In that case, the counter will only beincremented 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 stablephase 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 phaseof an SDCCH transaction : O&M has disabled the DTC

External comment:--

Edition:

13

Released

BSC Counters Catalogue

3BK 11203 0135 DSZZA

Page 10


11/630

Alcatel-Lucent


Counter Name : NB_SDCCH_DROP_EST_PHAS_RLF Counter Integer


Release



Technology: GSM Sub domain-1: Established PhaseSub domain-2: SDCCH


Counter definition:Number of SDCCH drops on SDCCH established phase due to radio link failure (radio link timeout or Lapdm timerexpiry).

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

External comment:--

Edition:

13

Released


3BK 11203 0135 DSZZA

Page 11


12/630

Alcatel-Lucent


Counter Name : NB_TCH_NOR_ASS_QUEUED Counter Integer



Measured number

Release



Technology: GSM Sub domain-1: Telecom Procedure (Traffic Load)Sub domain-2: Normal Assignment

Domain: Traffic Load Sub domain-3:

Counter definition:Number of TCH (in HR or FR usage) normal assignment requests that are put in BSC queue. Trigger condition:Further to the receipt of a 48.008 ASSIGNMENT REQUEST message for TCH, the counter is incremented:

i) upon the sending of a 48.008 QUEUING INDICATION message if the queuing is authorised by the MSC, or,

ii) when the assignment request is queued in the cell if the queuing is not authorised by the MSC and theparameter QUEUE_ANYWAY is set, or,iii) when the assignment request is queued in the cell if the queuing is not authorised by the MSC and the request has its pre-emption indicator set (provided that the flag EN_TCH_PREEMPT is set to 'Enable').

Note 1: MC13a = C13aNote 2: The HMI name of the parameter QUEUE_ANYWAY is "FORCED_QUEUING".

External comment:--

Edition:

13

Released


3BK 11203 0135 DSZZA

Page 12


13/630

Alcatel-Lucent


Counter Name : NB_INC_EXT_TCH_HO_QUEUED Counter Integer



Measured number

Release



Technology: GSM Sub domain-1: Telecom Procedure (Traffic Load)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 requesthas its pre-emption indicator set (provided that the flag EN_TCH_PREEMPT is set to 'Enable').

Note: MC13b = C13b


External comment:--

Edition:

13

Released


3BK 11203 0135 DSZZA

Page 13


14/630

Alcatel-Lucent


Counter Name : NB_INC_SDCCH_HO_ALLOC Counter Integer


Release




Domain: Traffic Load Sub domain-3: SDCCH

Counter definition:MC147=C147, Number of incoming internal or external SDCCH handovers -whose target SDCCH channel isallocated by the BSC.

Trigger condition:Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent on Abis Interface to activate an

SDCCH

channel for any handover purposes.


External comment:--


Counter Name : NB_IMM_ASS_ALLOC Counter Integer

SFD reference : No reference. Length: 4


Measured numberRelease Measured object Package


Technology: GSM Sub domain-1: Telecom Procedure (Traffic Load)Sub domain-2: Immediate Assignment


Counter definition:Number of immediate assignment plus SDCCH normal assignments -whose SDCCH channel is allocated by theBSC.

Trigger condition:

Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent on Abis Interface to activate anSDCCH

channel for any purpose other than handover.

External comment:--



15/630

Alcatel-Lucent


Counter Name : NB_IMM_ASS_EXEC_FAIL_RADIO Counter Integer


Release





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:

13

Released


3BK 11203 0135 DSZZA

Page 15


16/630

Alcatel-Lucent


Counter Name : NB_TCH_DROP_HO_PREP_EXEC_FAIL_BSS_PB Counter Integer


Release



Technology: GSM Sub domain-1: HandoverSub domain-2: TCH


Counter definition:Number of TCH (in HR or FR usage) drops due to BSS problem during any TCH handover preparation andexecution phases.This counter is incremented on the cell on which the problem occurs(In the case of internal inter-cell handovers, itis not incremented on both serving and target cell). For problems that are not related to a specific cell, the counter

related to the serving cell will be incremented.It may happen that several causes of failures mentioned below are detected consecutively. In that case, the

counter will only be incremented once, as soon as the handover procedure fails.This counter takes into account handovers from TCH in traffic or in signaling mode.

Trigger condition:1) Whenever the BSC receives on Abis interface from the target cell negative acknowledgment to the TCH

channelactivation involved in the handover procedure.2) Whenever the timer supervising the Channel Activation procedure (T9103) expires on the target cell duringactivation 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 Abisinterface from either the serving or the target cell during the external or internal inter-cell handover procedure andleads to a transaction failure.4) Whenever an 48.058 ERROR REPORT message with a cause value of "O&M intervention" is received on Abisinterface on either the old or the new channel during the internal intra-cell handover procedure and leads to atransaction failure.5) Whenever an 48.058 ERROR REPORT message on SAPI 0 with a cause value of "message sequence error"

isreceived on Abis interface from the serving cell between the sending of the 48.058 CHANNEL ACTIVATIONmessage and the reception of the 48.058 CHANNEL ACTIVATION ACKNOWLEDGMENT during the internalinter-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 ACTIVATIONmessage 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 anRSL 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 orby the BSS TELECOM application part as the result of a system defense action which may be due to BSSequipment failures external to the BSC (e.g. RSL failure or CU recovery failure), or due to BSC internal hardwareproblems (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...) orcommunication problems between different processor boards).9) Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "remote transcoderfailure" is received on Abis interface from the old channel between the sending of the 48.058 CHANNELACTIVATION 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


17/630



18/630

Alcatel-Lucent

unit:

mechanism: unit:External comment:

--


Counter Name : NB_TCH_DROP_EST_PHAS_BSS_PB Counter IntegerSFD reference : No reference. Length: 4Data collection Cumulative Measured number


B10 Common cell 1B8 Common cell 0

B9

Common cell

1Technology: GSM Sub domain-1: Established Phase

Sub domain-2: TCHDomain: Quality of Service Sub domain-3: Failure

problems which are internal to the BSS. Counter definition:

However, due to the current implementation which does not allow to be aware of the origin of the failure, O&MNumber of TCH (in HR or FR usage) drops in TCH established phase due to BSS problem.

operator actions will also be counted. It may happen that several causes of failures mentioned below aredetected consecutively. In that case, the2. It may happen that the counter can not be incremented since it is implemented within the faulty entity.counter

will only be incremented once, as soon as the call is released.This counter takes into account TCH in traffic or in signaling mode. It is not incremented in case of TCH dropduring a normal assignment, a handover or a DTM assignment.

Trigger condition:

1) Whenever a 48.058 ERROR REPORT message with a cause value of "O&M intervention" is received on Abisinterface after TCH seizure and leads to a loss of call.2) Whenever a 48.058 ERROR REPORT message on SAPI 0 with a cause value of "message sequence error" isreceived 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 aftersuccessful 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 theBSS TELECOM application part as the result of a system defense action which may be due to BSS equipmentfailures 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 betweensoftware 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, incase of numerous failures due to O&M commands, this counter will overestimate failures which are due toproblems 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&Moperator 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:--



19/630

Alcatel-Lucent


Counter Name : NB_INC_IDR_ALLOC Counter Integer



Measured number

Release



Technology: GSM Sub domain-1: Telecom Procedure (Traffic Load)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) whosetarget 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 TCHchannel is about to be sent during an internal directed retry.

External comment:--


Counter Name : NB_INC_TCH_HO_ALLOC Counter Integer


Data collection Cumulative Measured number

Release




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

bythe 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 TCHchannel is about to be sent during any handover procedure.


External comment:--



20/630

Alcatel-Lucent


Counter Name : NB_DTAP_MO_NOR_ASS_SUCC Counter Integer

SFD reference : RFD 3BKA55CBR035191 Length: 4Data collection Cumulative Measured number

Release



Technology: GSM Sub domain-1: Telecom Procedure (QoS)Sub domain-2: DTAP Assignment


Counter definition:Number of mobile originating normal assignment - DTAP successes.Trigger condition:Whenever a 44.018 CONNECT ACK is received on Abis interface.

External comment:

--


Counter Name : NB_DTAP_MT_NOR_ASS_SUCC Counter Integer




Technology:

GSM

Sub domain-1:

Telecom Procedure (QoS)Sub domain-2: DTAP Assignment


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:--



21/630


22/630

Alcatel-Lucent


Counter Name : NB_TCH_DROP_DTAP_EST_PHAS_BSS_PB Counter Integer


Release



Technology: GSM Sub domain-1: Established PhaseSub domain-2: TCH


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, thecounterwill 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 communicationproblems 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, incase of numerous failures due to O&M commands, this counter will overestimate failures which are due toproblems 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&Moperator 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:--



23/630

Alcatel-Lucent


Counter Name : NB_TCH_DROP_DTAP_EST_PHAS_REM_TRANS_FAIL Counter Integer


Release





Counter definition:Number of TCH (in HR or FR usage) drops in TCH DTAP established phase due to remote transcoder failure.

Thiscounter is not concerned by the channel change procedure.

Trigger condition:

Whenever a 48.058 CONNECTION FAILURE INDICATION message with a cause value of "remote transcoderfailure" is received on Abis interface for a TCH channel (for an established call).

External comment:--

Edition:

13

Released


3BK 11203 0135 DSZZA

Page 22


24/630

Alcatel-Lucent


Counter Name : NB_CALL_TFO Counter Integer

SFD reference : 3BK 10204 0478 DTZZA ("Tandem Free Operation") Length: 4Data collection Cumulative Measured number

Release



Technology: GSM Sub domain-1: SpeechSub 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 bythe 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 theassigned TCH).

Note 2: A TCH is seen as assigned in the serving cell between the sending of 48.058 CHANNEL ACTIVATIONmessage and the receipt of the 48.058 RF CHANNEL RELEASE message. This means that the counter can beincremented either if the TCH is assigned to serve a normal assignment or if the TCH is assigned to serve anincoming internal (inter-cell or intra-cell) or external handover.

Note 3: MC170 = C170

External comment:--

Edition:

13

Released


3BK 11203 0135 DSZZA

Page 23


25/630

Alcatel-Lucent


Counter Name : NB_TFO_CODEC_REQ Counter Integer

SFD reference : 3BK 10204 0478 DTZZA ("Tandem Free Operation") Length: 4Data collection Cumulative Measured number

Release



Technology: GSM Sub domain-1: SpeechSub domain-2: TFO


Counter definition:Number of codec mismatch resolutions or codec optimisations requested to the BSC.Trigger condition:Whenever a 48.058 REMOTE CODEC CONFIGURATION REPORT is received by the BSC.

External comment:

--


Counter Name : NB_TIMES_TRAF_DETECTED_HIGH Counter Integer

SFD reference : 3BK 10204 0326 DSZZA ("Traffic Management in HO Length: 4Algorithms")



B10 Common cell 1B8 Common cell 0

B9

Common cell

1Technology: GSM Sub domain-1: Resource Allocation & Management

Sub domain-2: Normal AssignmentDomain: 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 eachA_TRAFFIC_LOAD period.

This counter permits to tune the following parameters: A_TRAFFIC_LOAD, N_TRAFFIC_LOAD andHIGH_THRESHOLD.

This counter relates to the number of free TCH timeslots.

Trigger condition:At each A_TRAFFIC_LOAD period, whenever the BSC decision process detects a "high" traffic_load.

External comment:--



26/630

Alcatel-Lucent


Counter Name : NB_TIMES_TRAF_DETECTED_LOW Counter Integer

SFD reference : 3BK 10204 0326 DSZZA ("Traffic Management in HO Length: 4Algorithms")


Measured number



Technology: GSM Sub domain-1: Resource Allocation & ManagementSub 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 eachA_TRAFFIC_LOAD period.

This counter permits to tune the following parameters: A_TRAFFIC_LOAD, N_TRAFFIC_LOAD andLOW_THRESHOLD.

This counter relates to the number of free TCH timeslots.

Trigger condition:At each A_TRAFFIC_LOAD period, whenever the BSC decision process detects a "low" traffic_load.

Remark : the number of "indefinite" traffic load can be deduced from the counters NB_LOW_TRAFFIC_LOAD andNB_HIGH_TRAFFIC_LOAD over the Accumulation Period.

External comment:--

Edition:

13

Released


3BK 11203 0135 DSZZA

Page 25


27/630

Alcatel-Lucent


Counter Name : NB_TCH_NOR_ASS_PREP_FAIL_NO_QUEUE Counter Integer



Measured number

Release



Technology: GSM Sub domain-1: Telecom Procedure (QoS)Sub domain-2: Normal Assignment


Counter definition:Number of TCH (in HR or FR usage) normal assignment preparation failures because of the non-queuing of theASSIGNMENT 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"), becausethe queuing procedure is either:1) disabled within the BSC (i.e. (T11=0 and QUEUE_ANYWAY=0), OR (T11_forced=0 andQUEUE_ANYWAY=1)), or2) enabled within the BSC, i.e. T11 0, but not requested by the MSC when QUEUE_ANYWAY=0.

Trigger condition:The counter is incremented upon the sending of 48.008 ASSIGNMENT FAILURE (cause: "no radio resourceavailable") for a TCH channel because no TCH is available and either the queuing is disabled in the BSC (T11=0and QUEUE_ANYWAY=0, or T11_forced=0 and QUEUE_ANYWAY=1), or the queuing is enabled,QUEUE_ANYWAY=0, and the MSC does not request a queuing.

Note 1: The HMI name of the parameter QUEUE_ANYWAY is "FORCED_QUEUING".

Note 2: In case of Mx BSC, "no TCH available" could happen when the TCH processing capacity of CCP reachesthe limit defined by the MAX_TCH_PER_CCP parameter. In this case, this counter and MC926 are incrementedby one.

Note 3: In IP mode, this counter is increased by 1 if:- the cell mapped on a BTS is in IP congestion status;

- or the TCH processing capacity of AbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_TCH_TSparameter

External comment:--

Edition:

13

Released


3BK 11203 0135 DSZZA

Page 26


28/630

Alcatel-Lucent


Counter Name : NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_FULL Counter Integer



Measured number

Release





Counter definition:MC612b=C612b, Case: 48.008ASSIGNMENT REQUEST on TCH (in FR or HR usage) is received when no TCH

isavailable 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 bedequeued from the BSC queue.

Trigger condition:The counter is incremented upon the sending of 48.008 ASSIGNMENT FAILURE (cause: "no radio resourceavailable") for a TCH channel because the queue is full and no request of lower priority can be de-queued.

Note 1: In case of Mx BSC, "no TCH available" could happen when the TCH processing capacity of CCP reachesthe limit defined by the MAX_TCH_PER_CCP parameter. In this case, this counter and MC926 are incrementedby one.



External comment:--



29/630

Alcatel-Lucent


Counter Name : NB_TCH_NOR_ASS_PREP_FAIL_T11_EXP Counter Integer



Measured number

Release



Technology: GSM Sub domain-1: Telecom Procedure (QoS)Sub domain-2:


Counter definition:Case: 48.008ASSIGNMENT REQUEST is queued because no TCH (in HR or FR usage) is available in the cell,timer T11 (case MSC requests for queuing whatever QUEUE_ANYWAY value may be) or timer T11_forced (caseQUEUE_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 resourceavailable").Remark: If an internal directed retry is attempted and failed while T11/T11_forced is running, the request isun-holded and the BSC waits for the expiry of the relevant timer. Consequently, this counter must not beincremented upon the failure of an internal directed retry.

Trigger condition:The counter is incremented upon the sending of 48.008 CLEAR REQUEST (cause : "no radio resource available")-following the expiry of T11 or T11 forced for a queued TCH normal assignment.


Note 2: In case of Mx BSC, "no TCH available" could happen when the TCH processing capacity of CCP reaches

the limit defined by the MAX_TCH_PER_CCP parameter. In this case, this counter and MC926 are incrementedby one.

Note 3: In IP mode, this counter is increased by 1 if:- the cell mapped on a BTS is in IP congestion status;- or the TCH processing capacity of AbisBTSGroup reaches the limit defined by the NB_MAX_ACTIVE_TCH_TSparameter

External comment:--

Edition:

13

Released


3BK 11203 0135 DSZZA

Page 28


30/630

Alcatel-Lucent


Counter Name : NB_TCH_NOR_ASS_PREP_FAIL_QUEUE_REJ Counter Integer



Measured number

Release





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 (caseQUEUE_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) : theBSC 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 bedequeued by a higher priority request.

Trigger condition:The counter is incremented upon the sending of the 48.008 ASSIGMENT FAILURE (cause: "no radio resourceavailable") for a de-queued TCH request (i.e. normal assignment) due to the receipt of a higher priority request.


Note 2: In case of Mx BSC, "no TCH available" could happen when the TCH processing capacity of CCP reaches

the limit defined by the MAX_TCH_PER_CCP parameter. In this case, this counter and MC926 are incrementedby one.



External comment:--

Edition:

13

Released


3BK 11203 0135 DSZZA

Page 29


31/630

Alcatel-Lucent


Counter Name : NB_TCH_DROP_OUT_HO_EXEC_TRX Counter Integer

SFD reference : 3BK 10204 0470 DTZZA ("B7 counters improvements") Length: 2Data collection Cumulative Measured number

Release


B10 TRX 0B8 TRX 0B9 TRX 1



Counter definition:Number of TCH drops during the execution of any TCH outgoing handover, per TRX. This counter takes intoaccount handovers from TCH in traffic or in signaling mode.MC621 = C621

Trigger condition:

1) Inter-cell TCH handover: whenever the timer supervising the handover procedure (T3103) expires.

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

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

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

External comment:--

Edition:

13

Released


3BK 11203 0135 DSZZA

Page 30


32/630

Alcatel-Lucent


Counter Name : NB_TCH_FR_REQ Counter Integer


Release



Technology: GSM Sub domain-1: Resource Allocation & ManagementSub domain-2: Service


Counter definition:Number of TCH normal assignments requests from FR only mobiles (after possible filtering from the MSC). Trigger condition:Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for speech call with only GSM speech codingalgorithm version 1 full rate allowed.

External comment:

--


Counter Name : NB_TCH_DR_REQ Counter IntegerSFD reference : 3BK 10204 0470 DTZZA ("B7 counters improvements") Length: 4Data collection Cumulative Measured number


B10 Common cell 1B8 Common cell 0B9

Common cell


Sub domain-2: ServiceDomain: 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 codingalgorithm version 1 full rate and GSM speech coding algorithm version 1 half rate allowed.

External comment:--



33/630

Alcatel-Lucent


Counter Name : NB_TCH_DR_EFR_REQ Counter Integer


Release





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 algorithmversion 1 full rate, GSM speech coding algorithm version 1 half rate and GSM speech coding algorithm version 2

full rate allowed.

External comment:--


Counter Name : NB_TCH_AMR_REQ Counter Integer



B10 Common cell 1B8

Common cell

0B9 Common cell 1



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 algorithmversion 3 full rate or half rate allowed.

External comment:--



34/630

Alcatel-Lucent

C701e Type 1 : Traffic measurements

Counter Name : NB_TCH_DATA_REQ Counter Integer


Release





Counter definition:Number of TCH normal assignment requests for data calls.Trigger condition:Receipt of 48.008 ASSIGNMENT REQUEST from the MSC for data call.

External comment:

--


Counter Name : NB_TCH_NOR_FR_ALLOC Counter Integer




Technology:

GSM

Sub domain-1:

Resource Allocation & ManagementSub domain-2: Service


Counter definition:Number of TCH normal assignment/mode modify in FR usage - whose channel is allocated in the BSC. Thiscounter takes into account mode modify from TCH signaling to TCH traffic (following a DTM assignment with aTCH in signaling mode).

Trigger condition:48.058 CHANNEL ACTIVATION/ MODE MODIFY about to be sent to the BTS, indicating a FR channel with GSMspeech coding algorithm version 1, not related to handover.

External comment:--



35/630

Alcatel-Lucent


Counter Name : NB_TCH_NOR_HR_ALLOC Counter Integer


Release





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 withGSM speech coding algorithm version 1, not related to handover.

External comment:

--


Counter Name : NB_TCH_NOR_EFR_ALLOC Counter IntegerSFD reference : 3BK 10204 0470 DTZZA ("B7 counters improvements") Length: 4Data collection Cumulative Measured number


B10 Common cell 1B8 Common cell 0B9

Common cell


Sub domain-2: ServiceDomain: 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. Thiscounter takes into account mode modify from TCH signaling to TCH traffic (following a DTM assignment with aTCH in signaling mode).

Trigger condition:48.058 CHANNEL ACTIVATION/ MODE MODIFY about to be sent to the BTS, indicating a FR channel with GSMspeech coding algorithm version 2, not related to handover.

External comment:

--



36/630

Alcatel-Lucent


Counter Name : NB_TCH_NOR_ASS_ALLOC_TRX Counter Integer


Release



Technology: GSM Sub domain-1: Telecom Procedure (Traffic Load)Sub domain-2: Normal Assignment


Counter definition:Number of TCH (in HR or FR usage) normal assignment whose RTCH channel is allocated in the BSC, per TRX.This counter also takes into account normal assignment whose RTCH channel is allocated in the BSC insignaling mode (FR usage only), for DTM.

MC703 = C703

Trigger condition:

Whenever a 48.058 CHANNEL ACTIVATION message is about to be sent on Abis Interface to activate a TCHchannel for normal assignment, or for DTM assignment with a TCH in signaling mode.

External comment:--


Counter Name : NB_TCH_NOR_AMR_FR_ALLOC Counter IntegerSFD reference : 3BK 10204 0470 DTZZA ("B7 counters improvements") Length: 4Data collection Cumulative Measured number

Release





Counter definition:Number of TCH normal assignment/mode modify in FR AMR usage - whose channel is allocated in the BSC. Thiscounter takes into account mode modify from TCH signaling to TCH traffic (following a DTM assignment with aTCH in signaling mode).

Trigger condition:

48.058 CHANNEL ACTIVATION/ MODE MODIFY about to be sent to the BTS, indicating a FR channel with GSMspeech coding algorithm version 3, not related to handover.

External comment:--



37/630


38/630

Alcatel-Lucent


Counter Name : NB_EGSM_MS_ACCESS_EXCEPT_LU Counter Integer

SFD reference : 3BK 10204 0519 DTZZA ("E-GSM support") Length: 4Data collection Cumulative Measured number

Release



Technology: GSM Sub domain-1: Resource Allocation & ManagementSub domain-2: E-GSM


Counter definition:Number of initial accesses for call establishments (except location update) of MS supporting the E-GSM band, ona CELL basis.MC706 = C706

Trigger condition:

Whenever a 44.018 CLASSMARK CHANGE message in the context of any establishment causes different fromlocation update is received on Abis interface with a "Mobile Station Classmark 3" or a "Mobile Station Classmark2" 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.018CLASSMARK CHANGE message.

External comment:--

Edition:

13

Released


3BK 11203 0135 DSZZA

Page 37


39/630

Alcatel-Lucent


Counter Name : NB_TCH_OUT_HO_REQ_TRX Counter Integer


Release



Technology: GSM Sub domain-1: TCHSub 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 countedtogether. This counter takes into account handovers from TCH in traffic or in signaling mode. It does not take intoaccount DTM Assignments.

MC710 = C710

Trigger condition:

1) Intracell HO: Whenever the BSC process responsible for the handover procedure starts an intra cell TCHhandover procedure.2) Internal intercell HO: Whenever the BSC process responsible for the handover procedure selects a target cell(among a list of target cells) for internal inter cell TCH handover.3) External HO: Whenever a 48.008 HANDOVER REQUIRED message is sent on A interface to the MSC. If more

than one 48.008 HANDOVER REQUIRED is sent in the frame of the same Handover procedure, the counter isincremented only once.

48.008 HANDOVER REQUIRED is sent in following situations:

1) An external handover alarm has been raised, with corresponding list of candidate cells. 2) The list of candidate cells for the current alarm has been updated.


External comment:--

Edition:

13

Released


3BK 11203 0135 DSZZA

Page 38


40/630


41/630

Alcatel-Lucent


Counter Name : NB_TCH_OUT_HO_SUCC_TRX Counter Integer


Release





Counter definition:Nb of outgoing TCH handover successes, per TRX. Intracell, internal intercell and external handovers are countedtogether. This counter takes into account handovers from TCH in traffic or in signaling mode. It does not take intoaccount DTM Assignments.

MC712 = C712

Trigger condition:

1) External HO in the following cases:1a) 48.008CLEAR COMMAND (cause = "handover successful") is received on the serving BSC on the TCHchannel.1b) 48.008 CLEAR COMMAND (cause = "normal event/call control") is received while T8 is running.2) Internal inter-cell HO: whenever 44.018HANDOVER COMPLETE is received from the MS via the target cell onthe TCH channel.

3) Internal intra-cell HO: whenever 44.018 ASSIGNMENT COMPLETE is received from the MS via the cell on theTCH channel.

Note 1: This counter counts both inter-PLMN and intra-PLMN handover events. Note 2: This counter counts handover to UMTS.

External comment:--

Edition:

13

Released


3BK 11203 0135 DSZZA

Page 40


42/630

Alcatel-Lucent


Counter Name : NB_TCH_OUT_HO_FAIL_REV_TRX Counter Integer


Release





Counter definition:Nb of outgoing TCH handover -execution failures due to MS access problem with reversion of the mobile to the

oldchannel. Intracell, internal intercell and external handovers are counted together. This counter takes into accounthandovers from TCH in traffic or in signaling mode. It does not take into account DTM Assignments.

MC713 = C713

Trigger condition:1) External HO: Whenever a 44.018 HANDOVER FAILURE message is received on Abis interface from theserving cell, during an external TCH handover.2) Internal inter-cell HO: Whenever a 44.018 HANDOVER FAILURE message is received on Abis interface fromthe 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

servingchannel, during an internal intra-cell TCH handover.

Note: This counter counts both inter-PLMN and intra-PLMN handover events.Note: This counter counts handover to UMTS.

External comment:--



43/630

Alcatel-Lucent


Counter Name : NB_TCH_OUT_HO_FAIL_NO_REV_TRX Counter Integer


Release





Counter definition:Nb of outgoing TCH handover -execution failures due to MS access problem without reversion of the mobile to theold channel (call drop). Intracell, internal intercell and external handovers are counted together. This counter takesinto account handovers from TCH in traffic or in signaling mode. It does not take into account DTM Assignments.

MC714 = C714

Trigger condition:1) External TCH HO: Whenever the timer supervising the handover procedure on the serving cell (T8) expires,except if a 48.008 CLEAR COMMAND with "normal event/call control" cause was received from the MSC, leadingto a normal call release. In such a case, the handover is considered as successful.

2) Internal intercell TCH HO: Whenever the timer supervising the handover procedure (T3103) expires during aninternal inter-cell TCH handover.3) Intracell TCH HO: Whenever the timer supervising the handover procedure (T3107) expires during an internalintra-cell

Note: This counter counts both inter-PLMN and intra-PLMN handover events.Note: This counter counts hantover to UMTS

External comment:--

Edition:

13

Released


3BK 11203 0135 DSZZA

Page 42


44/630

Alcatel-Lucent


Counter Name : NB_INC_IDR_SUCC_TRX Counter Integer


Release



Technology: GSM Sub domain-1: Directed RetrySub domain-2: Internal


Counter definition:Number of incoming directed retry (towards a TCH channel in HR or FR usage) successes, per TRX.MC717a = C717a

Trigger condition:Whenever a 44.018 HANDOVER COMPLETE message is received on Abis interface from the target cell for a

TCH

channel involved in an internal directed retry procedure.

External comment:--


Counter Name : NB_INC_TCH_HO_SUCC_TRX Counter IntegerSFD reference : 3BK 10204 0470 DTZZA ("B7 counters improvements") Length: 2Data collection Cumulative Measured number


B10

TRX

0B8 TRX 0B9 TRX 1



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 isreceivedon 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 onthe target channel.


External comment:--



45/630

Alcatel-Lucent


Counter Name : NB_TCH_NOR_ASS_SUCC_TRX Counter Integer


Release





Counter definition:Number of TCH (in HR or FR usage) normal assignment successes, per TRX. This counter also takes intoaccount normal assignment successes for TCH establishment in signaling mode (FR usage only), for DTM. MC718 = C718

Trigger condition:

Whenever a 44.018 ASSIGNMENT COMPLETE message is received on Abis interface for a TCH channel that isnot involved in a handover procedure, in traffic or in signaling mode.

External comment:--


Counter Name : NB_TCH_DROP_EST_PHAS_RLF_TRX Counter IntegerSFD reference : 3BK 10204 0470 DTZZA ("B7 counters improvements") Length: 2Data collection Cumulative Measured number

Release


B10

TRX

0B8 TRX 0B9 TRX 1



Counter definition:Number of TCH (in HR or FR usage) drops in TCH established phase due to radio link failure (radio link timeout orLapdm timer expiry), per TRX. This counter takes into account TCH in traffic or in signaling mode.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:--



46/630

Alcatel-Lucent


Counter Name : NB_TCH_DROP_EST_PHAS_REM_TRANS_FAIL_TRX Counter Integer


Release





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 normalassignments or an internal intra-cell handovers) or a 44.018 HANDOVER COMPLETE message (in case of aninternal inter-cell incoming HO or an external inter-cell incomingHO) has been received for the TCH connection.

Note 1: MC739 = C739.Note 2: The counter is incremented only once per established TCH connection. Thus, even if the BTS sendsseveral 48.058 CONNECTION FAILURE INDICATION messages with cause "Remote Transcoder Failure" for aparticular established TCH connection, BSC will increment the counter only once for that connection.

External comment:

--



47/630

Alcatel-Lucent


Counter Name : NB_TCH_NOR_ASS_EXEC_FAIL_RADIO_TRX Counter Integer


Release





Counter definition:Number of TCH (in HR or FR usage) normal assignment -execution failures due to MS access problem, per TRX.This counter also takes into account DTM assignment -execution failures due to MS access problem for TCHestablishment in signaling mode (FR usage only).

MC746b = C746b

Trigger condition:

1) The timer T3107 in the BSS supervising the TCH channel seizure by the mobile expires (following the sendingof 44.018 ASSIGNMENT COMMAND for a TCH channel that is not involved in a handover procedure).2) The timer T3107 in the BSS supervising the TCH channel seizure by the mobile expires, following the sendingof 44.018 DTM ASSIGNMENT COMMAND for a TCH channel in signaling mode.3) The BSC receives a 44.018 ASSIGNMENT FAILURE on the old (SDCCH) channel during the normalassignment procedure except in case of multiband cell, when the normal assignment procedure is performed inthe inner zone and the ASSIGNMENT FAILURE is received with the cause "protocol error unspecified".4) The BSC receives a 44.018 DTM ASSIGNMENT FAILURE on the old (SDCCH) channel during the DTMassignment procedure, for a TCH in signaling mode.

External comment:

--

Edition:

13

Released


3BK 11203 0135 DSZZA

Page 46


48/630

Alcatel-Lucent


Counter Name : NB_TCH_NOR_ASS_PREP_FAIL_CONG_R_ABIS Counter Integer


Release





Counter definition:MC812 = C812 = C612a + C612b + C612c + C612dTrigger condition:

External comment:--

Edition:

13

Released


3BK 11203 0135 DSZZA

Page 47


49/630

Alcatel-Lucent


Counter Name : NB_MULTIBAND_MS_ACCESS_EXCEPT_LU_CELL Counter Integer


Release



Technology: GSM Sub domain-1: Telecom Procedure (Traffic Load)Sub domain-2: Multiband


Counter definition:Number of initial accesses for call establishments (location update apart) initiated by multiband mobile stations.The counter is defined on a per cell basis.A MS is considered as multiband if it supports:

- the P-GSM (or E-GSM or R-GSM) and the DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is

set to "GSM900 and DCS1800 bands", or,- the GSM850 and the DCS1800 bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850 and

DCS1800 bands", or,

- the GSM850 and the DCS1900 bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850 andDCS1900 bands", or,

- the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if the PLMN_FREQUENCY_BANDS parameter isset to "GSM900 and DCS1900 bands".

Trigger condition:Whenever a 44.018 Classmark Change message in the context of any establishment cause different from locationupdate is received on Abis interface from the MS with a "Mobile Station Classmark 3" Information Elementspecifying 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 andDCS1800 bands", or,- the GSM850 and the DCS1900 bands if the PLMN_FREQUENCY_BANDS parameter is set to "GSM850 andDCS1900 bands", or,- the P-GSM (or E-GSM or R-GSM) and the DCS1900 bands if the PLMN_FREQUENCY_BANDS parameter isset 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.018CLASSMARK CHANGE message.

External comment:--

Edition:

13

Released


3BK 11203 0135 DSZZA

Page 48


50/630

Alcatel-Lucent


Counter Name : NB_Suspend_Resume_req Counter Integer

SFD reference : 3BK 10204 0503 DTZZA ("GPRS suspend / resume for class Length: 4B mobiles")


Measured number





Counter definition:Number of suspend / Resume requests.A request could lead to a success, a failure or a stop.

Trigger condition:Emission of MS Suspend message by the BSC to the MFS

Emission of MS Resume message by the BSC to the MFSA suspend message received from MS with a "suspend cause" filtered by BSC will not be counted. Stop causescould be:

1) External handover2) MS channel failure.

External comment:--


Counter Name :

Nb_Suspend_fail

Counter Integer







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:--



51/630

Alcatel-Lucent


Counter Name : Nb_Suspend_succ Counter Integer



Measured number





Counter definition:Number of suspensions successes.Trigger condition:Reception of Resume ack message from MFS.

External comment:

--



52/630

Alcatel-Lucent

Type number: Counter - 2

Type name: Resource availability measurementsType scope (per BSS): One or several cells

Candidate for Standard No

Type limitations (per BSS):1) The union of all observed cells per BSS for the detailed measurement types 1, 2, 3, 4, 5, 6, 19 (ifused as Detailed), 26, 28 (if used as Detailed), 29 (if used as Detailed), 31 (if used as detailed), 34 (ifused as Detailed) must not exceed 40 cells.

Type definition:Set of counters related to the availability of the CCCH, SDCCH or TCH channels

C141 Type 2 : Resource availability measurements

Counter Name : AV_NB_TCH_QUEUED Counter Round (10

SFD reference :

No reference.

Length:

2Data collection Status Inspection (polling=10s) Measured number



Technology: GSM Sub domain-1: ChannelSub 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:--



53/630

Alcatel-Lucent


Counter Name : AV_NB_NOT_AVAIL_TRX_TS Counter Round (x)

SFD reference : No reference. Length: 2Data collection Status Inspection (polling=20s) Measured number

Release



Technology: GSM Sub domain-1: ChannelSub 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:--


Counter Name : AV_NB_AVAIL_TCH Counter Round (x)



B10 Common cell 1B8

Common cell

0B9 Common cell 1

Technology: GSM Sub domain-1: ChannelSub domain-2: TCH


Counter definition:Average number of available TCH/PDCH timeslots for traffic usage (i.e. TCH (for HR or FR usage) or PDCH).Trigger condition: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 nearestinteger value.

Note 1: "Available" has here to be understood as the operational state of a timeslot. The timeslot is available if itis not "blocked" or "out of service".

Note 2: The dynamic SDCCH timeslots are not taken into account in this counter.

External comment:--



54/630

Alcatel-Lucent


Counter Name : AV_NB_AVAIL_SDCCH Counter Round (x)


Release



Technology: GSM Sub domain-1: ChannelSub domain-2: SDCCH


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 isnot "blocked" or "out of service".

External comment:--


Counter Name : AV_NB_AVAIL_CCCH Counter Round (x)SFD reference : No reference. Length: 2

Data collection Status Inspection (polling=20s)

Measured number



Technology: GSM Sub domain-1: ChannelSub domain-2: CCCH


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

Date post:	02-Jun-2018
Category:	Documents
Upload:	sami
View:	218 times
Download:	0 times

Alcatel BSC Counters Catalogue _B10

Documents