bsc counters bsc level clear code measurement

BSC Counters: BSC Level ClearCode Measurement

dn9813515Issue 5a-0 en

# Nokia CorporationNokia Proprietary and Confidential

1 (74)

2003330Nokia BSC S10.5 ED, Vers. 2, ProductDocumentation

The information in this documentation is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokias customers only for the purposes of the agreement under which the documentationis submitted, and no part of it may be reproduced or transmitted in any form or means without theprior written permission of Nokia. The documentation has been prepared to be used byprofessional and properly trained personnel, and the customer assumes full responsibility whenusing it. Nokia welcomes customer comments as part of the process of continuous developmentand improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products cannot be considered binding butshall be defined in the agreement made between Nokia and the customer. However, Nokia hasmade all reasonable efforts to ensure that the instructions contained in the documentation areadequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the documentation.

Nokias liability for any errors in the documentation is limited to the documentary correction oferrors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL(INCLUDING MONETARY LOSSES), that might arise from the use of this documentation or theinformation in it.

This documentation and the product it describes are considered protected by copyrightaccording to the applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

Other product names mentioned in this documentation may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright ' Nokia Corporation 2003. All rights reserved.

2 (74) # Nokia CorporationNokia Proprietary and Confidential


BSC Counters: BSC Level Clear Code Measurement

Contents

Contents 3

List of tables 4

List of figures 5

Summary of changes 7

1 BSC Counters: BSC Level Clear Code Measurement 9

2 Counters of Clear Code Measurement 11

Appendix A BSC Clear Codes and Phases 73



3 (74)

Contents

List of tables




List of figures



5 (74)

List of figures

Summary of changes

Summary of changes

Changes between document issues are cumulative. Therefore, the latest documentissue contains all changes made to previous issues.

Changes made between issues 5 and 4

1. Introduction

The following new counters added: 500370, 500628-500629, 500710-500720

2. Counters

The following new counters added: 500370, 500628-500629, 500710-500720

The information updated for the following counters: 500321, 500341


New counter added: 500627 (previously spare)


1. Counters

The following new counters added: 500405, 500936, 500937

Information on counter explanation corrected in the following counter: 500342

Information on counter updating corrected in the following counter: 500924



7 (74)

Summary of changes

1 BSC Counters: BSC Level Clear CodeMeasurement

The BSC clear code measurement registers statistics about clear codes for theBSC during calls.

The call-related DX causes give more detailed information on the conditionsinside the BSC than the GSM-defined cause values. Internal faults and timerexpiry cases can be observed with the help of DX causes. The DX causes showalso cases that are not observed in the MSC. They also include GSM causes whena network element other than the BSC initiates the clearing of the transaction.

BSC clear codes and phases are presented in Appendix BSC Clear Codes andPhases .

See also Call Related DX Causes in BSC .

For more information on the documentation of the counters, with an exampletable and an explanation of the table fields, see BSC Counters: GeneralInformation on Measurements and Observations .

Related topics

Counters of Clear Code Measurement



9 (74)


2 Counters of Clear Code MeasurementNo

COUNTER NAME

RELEASE/CHANGED

500300

USER ACT BLOCK

S4

EXPLANATION Number of channels blocked by the user.

No

COUNTER NAME

RELEASE/CHANGED

500301

NETW ACT BLOCK

S4

EXPLANATION Number of channels blocked by the network.

No

COUNTER NAME

RELEASE/CHANGED

500302

BTS FAIL BLOCK

S4

EXPLANATION Number of channels blocked due to a BTS failure.

No

COUNTER NAME

RELEASE/CHANGED

500303

LAPD FAIL BLOCK

S4

EXPLANATION Number of channels blocked due to an LAPD failure.



11 (74)


No

COUNTER NAME

RELEASE/CHANGED

500304

ABIS FAIL BLOCK

S4

EXPLANATION Number of channels blocked due to a failure in the Abis interface.

No

COUNTER NAME

RELEASE/CHANGED

500305

ABIS MSG CORRUP TO BTS

S4

EXPLANATION Number of packages of the Abis interface message failures.

No

COUNTER NAME

RELEASE/CHANGED

500306

ASSIGN FAIL MSG

S4

EXPLANATION Number of ASSIGNMENT_ FAILURE messages which the Abisinterface receives from the MS during a basic call.

No

COUNTER NAME

RELEASE/CHANGED

500307

BLOCK SLAVE

S4

EXPLANATION Number of channels blocked due to a reason other than in counters500300-500304.

No

COUNTER NAME

RELEASE/CHANGED

500308

CH ACT NACK

S4

EXPLANATION Number of times the Abis interface receives aCHANNEL_ACTIVATION_ NACK message or the content of themessage has been corrupted.

UPDATED - When the Abis interface receives a CHANNEL_ACTIVATION_NACK message- When the content of the received message is corrupted




No

COUNTER NAME

RELEASE/CHANGED

500309

CH ACT NACK OM INTER

S4

EXPLANATION Number of CHANNEL_ ACTIVATION_NACK messages which theAbis interface receives due to O & M intervention.

No

COUNTER NAME

RELEASE/CHANGED

500310

CH ACT NACK EQUIP FAIL

S4

EXPLANATION Number of CHANNEL_ ACTIVATION_NACK messages which theAbis interface receives due to equipment failure.

No

COUNTER NAME

RELEASE/CHANGED

500311

CH ACT NACK ENCRYP ALG

S4

EXPLANATION Number of CHANNEL_ ACTIVATION_NACK messages which theAbis interface receives because the encryption algorithm is notsupported.

No

COUNTER NAME

RELEASE/CHANGED

500312

CH ACT NACK CH RAD ALR A

S4

EXPLANATION Number of CHANNEL_ ACTIVATION_NACK messages which theAbis interface receives because the radio channel has already beenallocated.

No

COUNTER NAME

RELEASE/CHANGED

500313

CH ACT NACK SERV NOT AVA

S4

EXPLANATION Number of CHANNEL_ ACTIVATION_NACK messages which theAbis interface receives because the service is not available.



13 (74)


No

COUNTER NAME

RELEASE/CHANGED

500314

CH ACT FAIL

S4

EXPLANATION Number of CHANNEL_ ACTIVATION_ACK messages received bythe Abis interface. The contents of the message are corrupted or atimer expires while waiting for the message.

No

COUNTER NAME

RELEASE/CHANGED

500315

CONN FAIL

S4

EXPLANATION Total number of CONNECTION_FAILURE messages.

UPDATED When the Abis interface receives a CONNECTION_FAILUREmessage.

No

COUNTER NAME

RELEASE/CHANGED

500316

CONN FAIL RAD INF FAIL

S4

EXPLANATION Number of CONNECTION_ FAILURE messages which the Abisinterface receives as a result of a failure in the radio interface.

UPDATED When the Abis interface receives a CONNECTION_FAILUREmessage and its cause is radio_interface_failure .

No

COUNTER NAME

RELEASE/CHANGED

500317

CONN FAIL RAD LINK FAIL

S4

EXPLANATION Number of CONNECTION_ FAILURE messages which the Abisinterface receives as a result of a radio link failure.

UPDATED When the Abis interface receives a CONNECTION_FAILUREmessage and its cause is radio_link_failure .




No

COUNTER NAME

RELEASE/CHANGED

500318

CONN FAIL REM TRANS FAIL

S4

EXPLANATION Number of CONNECTION_ FAILURE messages which the Abisinterface receives due to a remote transcoder failure.

UPDATED When the Abis interface receives a CONNECTION_FAILUREmessage and its cause is remote_transcoder_failure .

No

COUNTER NAME

RELEASE/CHANGED

500319

DATA IND CORRUP

S4

EXPLANATION Number of DATA_INDICATION messages received by the Abisinterface. The contents of the message are corrupted.

No

COUNTER NAME

RELEASE/CHANGED

500320

ERR IND

S4

EXPLANATION Number of ERROR_ INDICATION messages received by the Abisinterface.

UPDATED When the Abis interface receives an ERROR_INDICATION message.

IMPACT Call cleared

No

COUNTER NAME

RELEASE/CHANGED

500321

ESTAB IND FAIL

S4

EXPLANATION Number of failed ESTABLISH_INDICATION message receptions. TheESTABLISH_INDICATION message is missing or comes too late,causing the timer to expire. (This refers to ghosts that are notrecognised in the counter 003030.)

UPDATED When the timer expires while waiting for theESTABLISH_INDICATION message



15 (74)


No

COUNTER NAME

RELEASE/CHANGED

500322

ESTAB CONF FAIL

S4

EXPLANATION Number of ESTABLISH_ CONFIRM messages received by the Abisinterface. The content of the message is corrupted or a timer expireswhile waiting for the message.

No

COUNTER NAME

RELEASE/CHANGED

500323

HO FAIL

S4

EXPLANATION Number of handover failures when the MS returns to the sourcechannel.

UPDATED When a handover fails and the MS returns to the source channel andsends an ASSIGNMENT_ FAILURE or a HANDOVER_FAILUREmessage to the network during the handover.

IMPACT HO failure

No

COUNTER NAME

RELEASE/CHANGED

500324

HO DETECT FAIL

S4

EXPLANATION Number of HO_DETECT messages the Abis interface receives. Thecontent of the message is corrupted or a timer expires while waitingfor the message.

UPDATED - When the content of the HO_DETECT message is corrupted.- When a timer expires while waiting for the HO_DETECT message.

No

COUNTER NAME

RELEASE/CHANGED

500325

MODE MOD NACK

S4

EXPLANATION Number of MODE_MODIFY_ NACK messages received by the Abisinterface.




No

COUNTER NAME

RELEASE/CHANGED

500326

MODE MOD ACK FAIL

S4

EXPLANATION Number of MODE_MODIFY_ ACK messages the Abis interfacereceives. The content of the message is corrupted or a timer expireswhile waiting for the message.

UPDATED - When the content of the MODE_MODIFY_ACK message iscorrupted.- When a timer expires while waiting for the MODE_ MODIFY_ACKmessage.

No

COUNTER NAME

RELEASE/CHANGED

500327

NO MEAS RESULT

S4

EXPLANATION Number of missing MEASUREMENT_RESULT messages from theBTS.

No

COUNTER NAME

RELEASE/CHANGED

500328

NO RESP FROM COPRO

S4

EXPLANATION Number of times a timer expires because a co-process does notrespond. A BSC-internal failure.

REASON BSC-internal failure

No

COUNTER NAME

RELEASE/CHANGED

500329

PHY CONT CONF FAIL

S4

EXPLANATION Number of PHYSICAL_ CONTEXT_CONFIRM messages receivedby the Abis interface. The contents of the message are corrupted or atimer expires while waiting for the message.



17 (74)


No

COUNTER NAME

RELEASE/CHANGED

500330

RCS ALG START ACK FAIL

S4

EXPLANATION Number of RCS_ALGORITHM_ START_ACK messages received bythe Abis interface. The content of the message is corrupted or a timerexpires while waiting for the message.

UPDATED When the timer expires while waiting for theRCS_ALGORITHM_START_ACK message.

REASON Signalling within the BSC.

No

COUNTER NAME

RELEASE/CHANGED

500331

RCS ALG CL ACK FAIL

S4

EXPLANATION Number of RCS_ALGORITHM_ CLEAR_ACK messages received bythe Abis interface. The content of the message is corrupted or a timerexpires while waiting for the message.

UPDATED When the timer expires while waiting for theRCS_ALGORITHM_CLEAR_ACK message.


No

COUNTER NAME

RELEASE/CHANGED

500332

RC0 DISCO IND

S4

EXPLANATION Number of RC0_ DISCONNECT_IND messages received by the Abisinterface from the RC0.





No

COUNTER NAME

RELEASE/CHANGED

500333

RF CH REL ACK FAIL

S4

EXPLANATION Number of RF_CH_REL_ACK messages received by the Abisinterface. The content of the message is corrupted or a timer expireswhile waiting for the message.

No

COUNTER NAME

RELEASE/CHANGED

500334

REL IND

S4

EXPLANATION Number of RELEASE_ INDICATION messages received by the Abisinterface.

No

COUNTER NAME

RELEASE/CHANGED

500335

REL IND FAIL

S4

EXPLANATION Number of received RELEASE_ INDICATION messages. The contentof the message is corrupted or a timer expires while waiting for themessage.

No

COUNTER NAME

RELEASE/CHANGED

500336

SIGNALLING ERROR

S4

EXPLANATION Number of DTAP signalling failures.

No

COUNTER NAME

RELEASE/CHANGED

500337

STATE CONFLICT

S4

EXPLANATION Number of attempts to activate a blocked channel in the Abisinterface.



19 (74)


No

COUNTER NAME

RELEASE/CHANGED

500338

TYPE CONFLICT

S4

EXPLANATION Number of attempts to activate a channel in the Abis interface with thewrong information.

No

COUNTER NAME

RELEASE/CHANGED

500339

FORCED REL

S4

EXPLANATION Number of forced releases of TCHs.

No

COUNTER NAME

RELEASE/CHANGED

500340

REJ GHOST RES

S4

EXPLANATION Number of rejected phantom reservations caused by the wrongestablishment cause in the CHANNEL_REQUIRED message fromthe MS, or a too long distance between the MS and the BTS.

No

COUNTER NAME

RELEASE/CHANGED

500341

OVERLOAD

S4

EXPLANATION Number of OVERLOAD messages from the BTS. BTS has sent aDELETE_INDICATION message to the BSC as a result of AG bufferoverflow. The SDCCH has been released by the BSC.

No

COUNTER NAME

RELEASE/CHANGED

500342

ABI SWITCHOVER

S4/S8

EXPLANATION Number of unsuccessful call setups during the BCSU switchover.

IMPACT Call setup failures




No

COUNTER NAME

RELEASE/CHANGED

500343

SAPI 3 FAIL

S4

EXPLANATION Number of RELEASE_ INDICATION messages or corruptedESTABLISH_INDICATION messages which the Abis interfacereceives during the establishment of an SMS.

No

COUNTER NAME

RELEASE/CHANGED

500344

PAGING MSG FAIL

S4

EXPLANATION Number of MS_PAGING messages which the Abis interface receiveswhile the channel is blocked.

No

COUNTER NAME

RELEASE/CHANGED

500345

CH REQUIRED FAIL

S4

EXPLANATION Number of CHANNEL_REQUIRED messages received by the Abisinterface. The content of the message is corrupted.

No

COUNTER NAME

RELEASE/CHANGED

500346

MODE MOD NACK EQUIP FAIL

S4

EXPLANATION Number of MODE_MODIFY_ NACK messages which the Abisinterface receives due to equipment failure.

UPDATED The Abis interface receives a MODE_ MODIFY_NACK message withcause equipment_ failure .



21 (74)


No

COUNTER NAME

RELEASE/CHANGED

500347

MODE MOD NACK TRC RAT UN

S4

EXPLANATION Number of MODE_MODIFY_ NACK messages which the Abisinterface receives because the requested transcoding or rateadaptation is not available.

UPDATED The Abis interface receives a MODE_ MODIFY_NACK message withthe cause requested_ transcoding/rate_adaption_not_available .

No

COUNTER NAME

RELEASE/CHANGED

500348

RRM SERV REQ NACK

S4

EXPLANATION Number of RRM_CH_SERV_ REQ_NACK messages received by theAbis interface.


No

COUNTER NAME

RELEASE/CHANGED

500349

CH MODE MOD FAIL

S4

EXPLANATION Number of CH_MODE_ MODIFY_ACK messages received by theAbis interface. The mode of the message is not the same as therequested mode.

No

COUNTER NAME

RELEASE/CHANGED

500350

ASSIGNMENT FAIL

S4

EXPLANATION Number of timer expiries due to late or missingASSIGNMENT_COMPLETE message.

UPDATED When the timer expires while waiting for theASSIGNMENT_COMPLETE message.




No

COUNTER NAME

RELEASE/CHANGED

500351

DR FAIL

S4

EXPLANATION Number of failed directed retry procedures.

No

COUNTER NAME

RELEASE/CHANGED

500352

COPROCESS FAIL

S4

EXPLANATION Number of failures that have occurred in the co-process.

No

COUNTER NAME

RELEASE/CHANGED

500353

ERR REP ENC ALG NOT IMP

S4

EXPLANATION Number of ERROR_REPORT messages received from the BTSbecause the encryption algorithm is not implemented.

UPDATED When an ERROR_REPORT message is received from the BTS andthe cause is encryption_ algorithm_not_implemented .

No

COUNTER NAME

RELEASE/CHANGED

500354

ERROR REPORT

S4

EXPLANATION Number of ERROR_REPORT messages received from the BTS.

No

COUNTER NAME

RELEASE/CHANGED

500355

CH ACT NACK CH MODE ERR

S5

EXPLANATION Number of CHANNEL_ ACTIVATION_NACK messages received bythe Abis interface.

UPDATED When the cause for the failure is either not_implemented_unspecifiedor mandatory_ie_ error .



23 (74)


No

COUNTER NAME

RELEASE/CHANGED

500355

CH ACT NACK CH MODE ERR

S5

IMPACT The call may possibly be cleared

No

COUNTER NAME

RELEASE/CHANGED

500356

CH ACT NACK GEN IE ERR

S5

EXPLANATION Number of CHANNEL_ ACTIVATION_NACK messages received bythe Abis interface with cause general_ie_error .


No

COUNTER NAME

RELEASE/CHANGED

500357

SPEECH VERSION UNAVAIL

S5

UPDATED When the Abis interface receives an ASSIGNMENT_FAILURE orHANDOVER_FAILURE messages from the MS with the radioresource cause channel_mode_unacceptable .

IMPACT The call may possibly be clearedHO failure

No

COUNTER NAME

RELEASE/CHANGED

500358

IGNORED DOUBLE RAND ACC

S6

EXPLANATION Number of ignored double random accesses in the extended cell.

UPDATED When two incoming random accesses have the same frame numberand, as a result, the latter one is ignored.

RELATED TO A FEATURE BSS6037 Improved Solution for Extended Cell




No

COUNTER NAME

RELEASE/CHANGED

500359

RTSL_RECONF

S7

EXPLANATION Number of failed reconfigurations of a dynamic SDCCH.

UPDATED When the reconfiguration of a dynamic SDCCH resource is failed atthe time of an immediate assignment because all of the SDCCHresources under the control of the BCSU are already in use.

RELATED TO A FEATURE BSS7036 Dynamic SDCCH allocation

IMPACT Call cleared

No

COUNTER NAME

RELEASE/CHANGED

500360

HO INTERRUPTED

S7

EXPLANATION Number of interrupted HOs.

UPDATED When an assignment procedure is started before the MS is assignedto move to a new channel and the HO attempt is terminated withcause ho_interrupted .

IMPACT IMPACT: HO interrupted

No

COUNTER NAME

RELEASE/CHANGED

500361

DOWNGRADE WITH HSCSD

S7

EXPLANATION Number of channel releases caused by a downgrade.

UPDATED When the downgrade procedure is completed successfully.

RELATED TO A FEATURE BSS7003, BSS7037 HSCSD and 14.4 kbit/s data services

IMPACT Channel release



25 (74)


No

COUNTER NAME

RELEASE/CHANGED

500362

HO NOT STARTED

S7

EXPLANATION Number of rejected handover starts due to other ongoing procedures.

UPDATED When the handover start is rejected due to another ongoingprocedure.


IMPACT HO not allowed

No

COUNTER NAME

RELEASE/CHANGED

500363

CONF CHANGE NOT ALLOWED

S7

EXPLANATION Number of rejected upgrades, downgrades, subsequent assignmentsand ALAs due to other ongoing procedures.

UPDATED When the upgrade, downgrade or ALA is rejected due to anotherongoing procedure.



No

COUNTER NAME

RELEASE/CHANGED

500364

CONF CHANGE BTS FAIL

S7

EXPLANATION Number of failed configuration changes because the BTS sends aMODE_MODIFY_NACK message or the BTS does not answer at all.

UPDATED When the configuration change fails because the BTS sends aMODE_MODIFY_NACK message or the BTS does not answer at all.


IMPACT The call may possibly be cleared.




No

COUNTER NAME

RELEASE/CHANGED

500365

CONF CHANGE MS FAIL

S7

EXPLANATION Number of failed configuration changes because the MS sends aCONFIGURATION_CHANGE_REJECT message or the MS does notanswer at all.

UPDATED When the configuration change fails because the MS rejects theconfiguration change or the MS does not answer at all.



No

COUNTER NAME

RELEASE/CHANGED

500366

HSCSD COPRO FAIL

S7

EXPLANATION Number of channel releases caused by a failure in another channel inan HSCSD configuration.

UPDATED When a channel is released due to failure in another channel in anHSCSD configuration.



No

COUNTER NAME

RELEASE/CHANGED

500367

SUB TIMER

S7

EXPLANATION Number of timer expiries because the subchannel is not responding tothe main channel in an HSCSD connection.

UPDATED When a timer expires because the subchannel does not respond tothe main channel in an HSCSD connection.


IMPACT Call cleared



27 (74)


No

COUNTER NAME

RELEASE/CHANGED

500368

FORCED HO BLOCK

S7

EXPLANATION Number of blocked TCHs after a forced HO attempt. This counter ismapped to BSSMAP cause O_and_M_intervention (0x07).


IMPACT Call cleared

No

COUNTER NAME

RELEASE/CHANGED

500369

UPGRADE FAIL

S7

EXPLANATION Number of upgrade procedure failures. This counter is mapped toBSSMAP cause equipment_failure (0x20).

UPDATED When the upgrade procedure fails.


IMPACT Channel release

No

COUNTER NAME

RELEASE/CHANGED

500370

ESTAB IND CORRUPTED

S10

EXPLANATION Number of corrupted ESTABLISH_INDICATION messages receivedby the Abis interface.

UPDATED When the Abis interface receives an ESTABLISH_INDICATIONmessage with corrupted content.

No

COUNTER NAME

RELEASE/CHANGED

500371

SPARE

EXPLANATION Spare




No

COUNTER NAME

RELEASE/CHANGED

500372

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500373

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500374

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500400

TIMING ADVANCE

S4

EXPLANATION Number of times the MS exceeds the cell boundaries.

UPDATED When the call is released after the distance between the MS and theBTS has reached the allowed maximum value, in other words, whenthe MS has exceeded the planned cell boundaries.

No

COUNTER NAME

RELEASE/CHANGED

500401

RRM SWITCH CRC POOL

S5

EXPLANATION Number of requests for changing the circuit pools in the A interface.

UPDATED When the RRM sets cause rrm_switch_ crc_pool in a messagerejecting a request for a TCH.

RELATED TO A FEATURE BSS5010 Half Rate



29 (74)


No

COUNTER NAME

RELEASE/CHANGED

500401

RRM SWITCH CRC POOL

S5

IMPACT - HO attempt fails- An external HO for changing the circuit pools in the A interface ispossibly started.

REASON A interface

No

COUNTER NAME

RELEASE/CHANGED

500402

RRM SPEECH VER UNAVAIL

S6

EXPLANATION Number of requests for radio channel allocation that are rejectedbecause the requested speech coder versions are not supported bythe target BTS.

UPDATED When an Assignment or Handover Resource Allocation proceduresfails.

DEPENDENCIES 001011

RELATED TO A FEATURE BSS6071 Enhanced Full Rate Codec (ETSI)

IMPACT - Call attempt fails- HO attempt fails

REASON BTS

No

COUNTER NAME

RELEASE/CHANGED

500403

RRM BTS NOT SUPPORTING

S7

EXPLANATION Number of requests for resources that are not supported by the BTS.This counter is mapped to BSSMAP cause requested_transcoding/rate_adaption_unavailable (0x30).

UPDATED When the BTS does not support the requested resources.





No

COUNTER NAME

RELEASE/CHANGED

500404

RRM MS NOT SUPPORTING

S7

EXPLANATION Number of requests for resources that are not supported by the MS.This counter is mapped to BSSMAP cause MS_not_equipped (0x26).

UPDATED When the MS does not support the requested resources.


No

COUNTER NAME

RELEASE/CHANGED

500405

RRM INVALID CELL

S8

EXPLANATION Number of failed traffic channel allocations in an external handover.

UPDATED When a target cell is not controlled by the BSS.

DEPENDENCIES Two counters of the Handover measurement are incremented alongwith this DX cause:

- Number of unsuccessful handovers due to a lack of resources (newcell side) (004001).- Number of unsuccessful handovers due to a lack of resources (oldcell side) (004055).

IMPACT HO failed

No

COUNTER NAME

RELEASE/CHANGED

500406

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500407

SPARE

EXPLANATION Spare



31 (74)


No

COUNTER NAME

RELEASE/CHANGED

500408

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500500

HO NOT ALLOWED

S4

EXPLANATION Number of external HOs that are not allowed.

UPDATED - When the HO is not allowed during a FACCH call setup- When the external DR HO attempt fails because the external DRHOs are disabled.- When all candidate cells for an inter-BSC HO are normal areas ofextended cells.

IMPACT The HO attempt fails

REASON BSC internal

No

COUNTER NAME

RELEASE/CHANGED

500501

NO RADIO RES AVAIL

S4

EXPLANATION Number of occurrences when there are no radio resources in the BTSfor channel reservation during HO signalling.

IMPACT HO attempt fails

REASON Congestion

No

COUNTER NAME

RELEASE/CHANGED

500502

RESTORE SOURCE

S4

EXPLANATION Not relevant.

UPDATED




No

COUNTER NAME

RELEASE/CHANGED

500502

RESTORE SOURCE

S4

DEPENDENCIES See counter 500323.

No

COUNTER NAME

RELEASE/CHANGED

500503

NO RESP FROM COPROCESS

S4

EXPLANATION Number of signalling failures in the internal processes during HOsignalling.

UPDATED When the internal timer of the HASPRB expires.External HO source phase (0x09):- waiting for internal message 9349 from the AIVPRB- waiting for internal message 9368 from the AIVPRBInternal BSC intra-cell target phase (0x0D):- waiting for internal message 9354 from the ABIPRBInternal BSC inter-cell (0x0E) and intra-cell (0x0D) target phases:- waiting for internal message 2300 from the AIVPRB- waiting for internal message 2336 from the AIVPRB

IMPACT - HO attempt fails- Possible RF release (new BTS)

REASON BSC internal signalling.

No

COUNTER NAME

RELEASE/CHANGED

500504

NO RESP TO RADIO RES REQ

S4

EXPLANATION Number of failures in reserving a target channel during HO signalling.

UPDATED When the internal timer of the HASPRB expires. Target channelreservation has failed during HO signalling. No answer to the radioresource request.

IMPACT HO attempt fails




33 (74)


No

COUNTER NAME

RELEASE/CHANGED

500505

HAS STATE CONFLICT C

S4


UPDATED When the internal timer of the HASPRB expires: waiting for internalmessage 9408 from the ABIPRB

IMPACT - HO attempt fails- Channel release (new channel)


No

COUNTER NAME

RELEASE/CHANGED

500506

CLEAR CMD NOT RECEIVED

S4

EXPLANATION Number of times when no CLEAR_COMMAND message is receivedfrom the A interface during external source HO signalling.

UPDATED When the GSM timer T8 expires in the source BSC during an externalHO.

IMPACT - HO attempt fails- Call is cleared

REASON MS, new BSS, MSC

No

COUNTER NAME

RELEASE/CHANGED

500507

MS IS LOST

S4

EXPLANATION Number of lost MSs after a HANDOVER/ASSIGNMENT commandduring handovers.

UPDATED - When one of the GSM timers T3107, T3103 or T9113 expires- When an internal message 9472 is not received from the AIVPRBand the timer of the HASPRB expires




No

COUNTER NAME

RELEASE/CHANGED

500507

MS IS LOST

S4

DEPENDENCIES - In BSC-internal HOs the new channel is cleared- With cause 500511.

- In external HOs the old channel is cleared with cause value set bythe MSC.

IMPACT - HO attempt fails.- Call is cleared.

REASON MS, BSS

No

COUNTER NAME

RELEASE/CHANGED

500508

NO RESP TO HO CPL MSG

S4


UPDATED - Internal timer of the HASPRB expires.- Waiting for internal message 9472 from the AIVPRB.

DEPENDENCIES - In BSC-internal HOs the new channel is cleared with cause 500511.- In external HOs the old channel is cleared with cause value set bythe MSC.

IMPACT - HO attempt fails- Call is cleared.


No

COUNTER NAME

RELEASE/CHANGED

500509

HAS SWITCHOVER

S4

EXPLANATION Number of HOs that have failed after the switchover has started.

UPDATED When the unit switchover has started during a HO before the BSC hassent the HANDOVER/ASSIGNMENT command to the MS.



35 (74)


No

COUNTER NAME

RELEASE/CHANGED

500509

HAS SWITCHOVER

S4

IMPACT - HO attempt fails.- Possible channel release (new channel).- Possible RF release (new BTS).

REASON BSC-internal.

No

COUNTER NAME

RELEASE/CHANGED

500510

TARGET FAIL

S4

EXPLANATION Not relevant.

No

COUNTER NAME

RELEASE/CHANGED

500511

SOURCE FAIL

S4

EXPLANATION Number of failures on the source channel during HOs.

UPDATED - When there is a failure in the source channel before the BSC hassent a HANDOVER/ ASSIGNMENT command to the MS.- When one of the GSM timers T3107 or T3103 expires.- When the internal message 9472 is not received from the AIVPRBand the internal timer of the HASPRB expires.- When the HO is not completed (for example, the switching of the bi-directional speech path fails in the A interface).

IMPACT - HO attempt fails- Call is cleared.

REASON MS, BSS

No

COUNTER NAME

RELEASE/CHANGED

500512

HAS CALL CONTROL

S4

EXPLANATION Number of failures for the master to create a hand.




No

COUNTER NAME

RELEASE/CHANGED

500512

HAS CALL CONTROL

S4

UPDATED When the master of the HASPRB fails to reserve a new hand for theHO attempt.

IMPACT HO attempt fails.

REASON BSC internal.

No

COUNTER NAME

RELEASE/CHANGED

500513

ADJ CELL ID ERR

S4

EXPLANATION Number of interrupted HO attempts.

UPDATED When the BSC notices that the target cell information on the BCCHfrequency or/and BSIC, received in the HANDOVER_COMMANDmessage from the MSC, is not correct.NOTE! This counter indicates that the information on the adjacentcells is incorrect in the BSDATA (BSS Radio Network ConfigurationDatabase).

IMPACT HO attempt fails.

REASON BSS Radio Network Configuration Database.

No

COUNTER NAME

RELEASE/CHANGED

500514

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500515

SPARE

EXPLANATION Spare



37 (74)


No

COUNTER NAME

RELEASE/CHANGED

500516

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500517

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500518

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500519

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500520

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500521

SPARE

EXPLANATION Spare




No

COUNTER NAME

RELEASE/CHANGED

500522

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500523

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500524

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500600

AIV HAND ACT FAIL

S4

EXPLANATION Number of failures to activate a hand process in the AIVPRB master.

UPDATED When the AIVPRB master fails to create a hand process for the call.

IMPACT Call attempt fails

No

COUNTER NAME

RELEASE/CHANGED

500601

AIV SSP

S4

EXPLANATION Number of failures to establish an SCCP connection because thesubsystem is in the prohibited status.

UPDATED When the AIVPRB rejects the call attempt because the MSC is notreachable.



39 (74)


No

COUNTER NAME

RELEASE/CHANGED

500601

AIV SSP

S4


No

COUNTER NAME

RELEASE/CHANGED

500602

SCCP CONN FAIL

S4

EXPLANATION Number of failures to establish an SCCP connection.

UPDATED When a CREF message is received from the MSC.


No

COUNTER NAME

RELEASE/CHANGED

500603

SCCP CONN TIMEOUT

S4

EXPLANATION Number of failures to receive an acknowledgement from the MSC tothe request for establishing an SCCP connection.

UPDATED When the GSM timer T9105 expires.


No

COUNTER NAME

RELEASE/CHANGED

500604

SCCP RELEASE

S4

EXPLANATION Number of abnormal releases of the SCCP connection.

UPDATED Whenever the MSC clears a call by releasing the SCCP connectionwithout first clearing the upper layers (BSSMAP).

IMPACT Call dropped




No

COUNTER NAME

RELEASE/CHANGED

500605

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500606

GLOBAL RESET

S4

EXPLANATION Number of calls cleared due to global resets.

UPDATED - When the state of a SCCP subsystem changes so that the MSCbecomes unattainable

- When a reset message is received from the MSC

IMPACT Call dropped

No

COUNTER NAME

RELEASE/CHANGED

500607

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500608

NO DTAP FROM MSC

S4

EXPLANATION Number of times when no DTAP message is received from the MSCafter a successful establishment of the SCCP.

UPDATED When the SCCP connection is established without user data in theCR and CC messages and a timer that supervises the reception offurther messages from the MSC expires.




41 (74)


No

COUNTER NAME

RELEASE/CHANGED

500609

HO DENIED ASSIGN

S4

EXPLANATION Number of times when the HO is not allowed to be started because anassignment procedure is in progress.

UPDATED When the HO attempt is interrupted.

IMPACT HO attempt interrupted

No

COUNTER NAME

RELEASE/CHANGED

500610

HO DENIED CIPHERING

S4

EXPLANATION Number of times when the HO is not allowed to be started becausethe ciphering procedure is in progress.



No

COUNTER NAME

RELEASE/CHANGED

500611

HO DENIED CLEAR

S4

EXPLANATION Number of times when the HO is not allowed to be started becausethe call clearing procedure is in progress.



No

COUNTER NAME

RELEASE/CHANGED

500612

HO DENIED NO SCCP CONN

S4

EXPLANATION Number of times when the external SDCCH HO is not allowed to bestarted because the establishment of the SCCP connection is inprogress.




No

COUNTER NAME

RELEASE/CHANGED

500612

HO DENIED NO SCCP CONN

S4



No

COUNTER NAME

RELEASE/CHANGED

500613

T7 EXPIRE

S4

EXPLANATION Number of expiries of the GSM timer T7.



No

COUNTER NAME

RELEASE/CHANGED

500614

T10 EXPIRE

S4

EXPLANATION Number of expiries of the GSM timer T10 that causes the call to becleared by the MSC.

UPDATED When the call is cleared.

IMPACT The assignment procedure fails on the A interface. The call / callattempt is likely to be cleared by the MSC.

No

COUNTER NAME

RELEASE/CHANGED

500615

AIV CRCT RES TIMEOUT

S4

EXPLANATION Number of timeouts in the AIVPRB that are related to allocating an Ainterface speech circuit.

UPDATED When the call is cleared or the HO attempt fails.

IMPACT Call / HO attempt fails.



43 (74)


No

COUNTER NAME

RELEASE/CHANGED

500616

AIV CRCT CONN TIMEOUT

S4

EXPLANATION Number of timeouts in the AIVPRB that are related to connecting an Ainterface speech circuit.

UPDATED When the call is cleared or the HO attempt fails.

IMPACT Call / HO attempt fails

No

COUNTER NAME

RELEASE/CHANGED

500617

AIV CRCT DISCONN TIMEOUT

S4

EXPLANATION Number of timeouts in the AIVPRB that are related to disconnectingan A interface speech circuit.

No

COUNTER NAME

RELEASE/CHANGED

500618

AIV CRCT REL TIMEOUT

S4

EXPLANATION Number of timeouts in the AIVPRB that are related to releasing an Ainterface speech circuit.

No

COUNTER NAME

RELEASE/CHANGED

500619

AIV TIMEOUT

S4

EXPLANATION Number of timeouts in the AIVPRB that are related to the internalcommunication of the BSC.

No

COUNTER NAME

RELEASE/CHANGED

500620

ACT CTRL TIMEOUT

S4

EXPLANATION Number of expiries of the BSC-internal supervision timer whichsupervises the communication between the Abis and the A interfaces.




No

COUNTER NAME

RELEASE/CHANGED

500620

ACT CTRL TIMEOUT

S4

UPDATED When the call is cleared.

IMPACT Call dropped

No

COUNTER NAME

RELEASE/CHANGED

500621

INVALID BSSMAP MSG

S4

EXPLANATION Number of the times when a corrupted message received from theMSC results to a clearing of the call.

IMPACT Call dropped

No

COUNTER NAME

RELEASE/CHANGED

500622

UNKNOWN A PCM

S4

EXPLANATION Number of messages received that concern an unknown PCMmultiplex in the A interface.

No

COUNTER NAME

RELEASE/CHANGED

500623

HO DENIED NO PROPER CRC

S4

EXPLANATION Number of HO enquiries that are rejected because there are nocircuits available.

UPDATED When the AIVPRB receives a handover request from the HASPRBwith cause switch_ circuit_pool and no A interface circuit matchesthose in the pool list of the enquiry.




45 (74)


No

COUNTER NAME

RELEASE/CHANGED

500624

CH TYPE MISMATCH

S5

EXPLANATION The radio interface data rate requirement, included in the normalASSIGNMENT_REQUESTor the HANDOVER_REQUEST message,is totally contradictory with the TCH channel rate request of thechannel type IE.The TCH channel rate request, or the data rate requirement, includedin the ASSIGNMENT_REQUEST message related to theIN_CALL_MODIFICATION message or the FACCH call setup, istotally contradictory with the type of the TCH on which the call ismaintained.

UPDATED When the above mentioned conditions are fulfilled during theassignment or the HO resource allocation procedures.

IMPACT The assignment procedure fails on A interface, or in case of ahandover the handover attempt fails.

No

COUNTER NAME

RELEASE/CHANGED

500625

AIV TRANSC OR RATE UNAVA

S5

EXPLANATION Number of assignment or HO requests that have failed because therequested TCH type is not supported by the A interface pools.

No

COUNTER NAME

RELEASE/CHANGED

500626

AIV SPEECH VERSION UNAVA

S5

EXPLANATION Number of assignment or HO requests that are rejected because therequested speech coder versions are not supported.

IMPACT The assignment procedure or HO attempt fails.




No

COUNTER NAME

RELEASE/CHANGED

500627

AIV PAGING REFUSED BIG LOAD

S9

EXPLANATION This counter is updated when a PAGING message is received fromthe MSC and there is a too heavy load in the same BCSU unit. Theheavy load is observed using the amount of unhandled messages inthe unit.

UPDATED When bsc_dx_cause 627 is set because of too many unhandledmessages in the BCSU unit.

No

COUNTER NAME

RELEASE/CHANGED

500628

AIV CONN REFRESH TIMEOUT

S10

EXPLANATION The A interface connection is refreshed from time to time during a call.This counter indicates that the timer for the connection refreshprocedure has expired.

RELATED TO A FEATURE BSS10005 Reversed Hunting

DEPENDENCIES Counters 001078, 001079, 001080, 001087, 001088 and 001089 areupdated with this counter.

IMPACT Call cleared.

No

COUNTER NAME

RELEASE/CHANGED

500629

AIV CONN REFRESH FAILED

S10

EXPLANATION The A interface connection is refreshed from time to time. Thiscounter indicates that the connection refresh procedure has failed.



IMPACT Call cleared.



47 (74)


No

COUNTER NAME

RELEASE/CHANGED

500630

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500631

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500632

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500633

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500634

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500635

SPARE

EXPLANATION Spare




No

COUNTER NAME

RELEASE/CHANGED

500636

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500637

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500638

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500639

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500700

RC0 HAND ACT FAIL

S4

EXPLANATION Number of failures of the RC0PRB master to activate a hand process.



49 (74)


No

COUNTER NAME

RELEASE/CHANGED

500701

A CRCT ALR RES

S4

EXPLANATION Number of assignments of a speech circuit which has already beenallocated.

No

COUNTER NAME

RELEASE/CHANGED

500702

A CRCT CONN ERR

S4

EXPLANATION Number of connection errors in the Marker and Cellular ManagementUnit (MCMU) while a speech circuit in the A interface is beingconnected.

No

COUNTER NAME

RELEASE/CHANGED

500703

RC0 CRCT CONN TIMEOUT

S4

EXPLANATION Number of timeouts in the RC0PRB during connections of an Ainterface speech circuit.

No

COUNTER NAME

RELEASE/CHANGED

500704

ACCESS OUT OF CRCT TBL

S4

EXPLANATION Number of failures in finding the requested speech circuit in the circuitcontrol table.

No

COUNTER NAME

RELEASE/CHANGED

500705

A CRCT REL ERR

S4

EXPLANATION Number of circuit release errors in the Marker when an A interfacespeech circuit is released.




No

COUNTER NAME

RELEASE/CHANGED

500706

RC0 TRANSC OR RATE UNAVA

S5

EXPLANATION Number of requests for a channel rate that are rejected because thecircuit pool defined in the request has not been defined in the Ainterface.

No

COUNTER NAME

RELEASE/CHANGED

500707

RC0 CIP TYPE MISMATCH

S5

UPDATED - When the circuit type in the A interface is contradictory with the TCHchannel rate requirement.- When the data rate requirement implies the circuit pool change.

No

COUNTER NAME

RELEASE/CHANGED

500708

RC0 INV MSG CONTENTS

S5

UPDATED When the radio interface data rate requirement is contradictory withthe circuit pool configuration in the A interface.

No

COUNTER NAME

RELEASE/CHANGED

500709

RC0 REQ SPEECH VER UNAVA

S6

EXPLANATION Number of times the BSC has received either anASSIGNMENT_REQUEST or a HANDOVER_REQUEST messagecontaining speech codec versions, none of which are supported bythe BSC.

RELATED TO A FEATURE BSS6071 Enhanced Full Rate Codec (ETSI)




51 (74)


No

COUNTER NAME

RELEASE/CHANGED

500710

RC0 HUNTING QUEUE FULL

S10

EXPLANATION Number of times when there is no free place for the call in the huntingqueue.



IMPACT Call attempt fails.

No

COUNTER NAME

RELEASE/CHANGED

500711

RC0 CRCT CONGESTION

S10

EXPLANATION Number of times when there is no free circuit for the call.




No

COUNTER NAME

RELEASE/CHANGED

500712

RC0 A SEARCH ERROR

S10

EXPLANATION Number of times when the content of the hunting request message isinvalid.







No

COUNTER NAME

RELEASE/CHANGED

500713

RC0 CRCT POOL MISMATCH

S10

EXPLANATION Number of times when the hunted circuit is from the wrong circuit pool.




No

COUNTER NAME

RELEASE/CHANGED

500714

RC0 REJ DUE EME CALL

S10

EXPLANATION Number of times when the hunting queue is full and an emergencycall has taken priority over an ordinary call.




No

COUNTER NAME

RELEASE/CHANGED

500715

RC0 ILC FILE ERROR

S10

EXPLANATION Number of times when there is no pool available on the hunting list.






53 (74)


No

COUNTER NAME

RELEASE/CHANGED

500716

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500717

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500718

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500719

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500720

SPARE

EXPLANATION Spare




No

COUNTER NAME

RELEASE/CHANGED

500800

A TSL USER MISMATCH

S4

EXPLANATION Number of requests to connect, disconnect, or release a speechcircuit that are received from a process which is not recorded as auser of the circuit in the SC7PRBs internal control tables.

No

COUNTER NAME

RELEASE/CHANGED

500801

SC7 CRCT RES TIMEOUT

S4

EXPLANATION Number of timeouts in the SC7PRB while allocating a speech circuit inthe A interface.

No

COUNTER NAME

RELEASE/CHANGED

500802

SC7 CRCT CONN TIMEOUT

S4

EXPLANATION Number of timeouts in the SC7PRB while connecting a speech circuitin the A interface.

No

COUNTER NAME

RELEASE/CHANGED

500803

SC7 CRCT DISCONN TIMEOUT

S4

EXPLANATION Number of timeouts in the SC7PRB while disconnecting a speechcircuit in the A interface.

No

COUNTER NAME

RELEASE/CHANGED

500804

SC7 CRCT REL TIMEOUT

S4

EXPLANATION Number of timeouts in the SC7PRB while releasing a speech circuit inthe A interface.



55 (74)


No

COUNTER NAME

RELEASE/CHANGED

500805

A TSL BLOCKED

S4

EXPLANATION Number of assignments of a circuit that is blocked.

No

COUNTER NAME

RELEASE/CHANGED

500806

A TSL STATUS UNKNOWN

S4

EXPLANATION Number of assignments of a circuit with unknown status.

No

COUNTER NAME

RELEASE/CHANGED

500807

LSI ACCESS FAIL

S4

EXPLANATION Number of failures to access the LSINGL file.

No

COUNTER NAME

RELEASE/CHANGED

500808

SCC ACCESS FAIL

S4

EXPLANATION Number of failures to access the SCCTST file.

No

COUNTER NAME

RELEASE/CHANGED

500809

UNDEF TSL IN LSI

S4

EXPLANATION Number of failures to find the circuit concerned because it is notdefined in the LSIGNL file.




No

COUNTER NAME

RELEASE/CHANGED

500810

CRCT EQUIPMENT FAIL

S4

EXPLANATION Number of failures which the SC7PRB has tracked down to hardwareproblems.

No

COUNTER NAME

RELEASE/CHANGED

500811

RESET CRCT

S4

EXPLANATION Number of RESET_CIRCUIT messages received from the MSC.

No

COUNTER NAME

RELEASE/CHANGED

500812

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500813

SC7 SSP

S4

EXPLANATION Number of the errors due to status SCCP prohibited .

UPDATED When the status has been detected by the SC7PRB.

No

COUNTER NAME

RELEASE/CHANGED

500814

SPARE

EXPLANATION Spare



57 (74)


No

COUNTER NAME

RELEASE/CHANGED

500815

A PCM FAULT

S4

EXPLANATION Number of faults detected in the 2 Mbit PCM connection.

No

COUNTER NAME

RELEASE/CHANGED

500816

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500817

A CRCT REMOVED

S4

EXPLANATION Number of speech circuits that have been removed from use.

No

COUNTER NAME

RELEASE/CHANGED

500818

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500819

A ET STATE CHANGE

S4

EXPLANATION Number of state changes in the ET.

No

COUNTER NAME

RELEASE/CHANGED

500820

SPARE

EXPLANATION Spare




No

COUNTER NAME

RELEASE/CHANGED

500821

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500822

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500823

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500824

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500825

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500826

SPARE

EXPLANATION Spare



59 (74)


No

COUNTER NAME

RELEASE/CHANGED

500827

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500828

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500829

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500900

M RADIO IF MESS FAIL

S4

EXPLANATION Number of messages received from the MSC that indicate failures ofthe radio interface.

UPDATED When the cause value is 0x00

No

COUNTER NAME

RELEASE/CHANGED

500901

M RADIO IF FAIL

S4

EXPLANATION Number of messages received from the MSC that indicate failures ofthe radio interface.





No

COUNTER NAME

RELEASE/CHANGED

500902

M UPLINK QUALITY

S4

EXPLANATION Number of messages received from the MSC that concern the uplinkquality .

UPDATED When the cause value is 0x02.

No

COUNTER NAME

RELEASE/CHANGED

500903

M UPLINK STRENGTH

S4

EXPLANATION Number of messages received from the MSC that concern thestrength of the uplink signal.


No

COUNTER NAME

RELEASE/CHANGED

500904

M DOWNLINK QUALITY

S4

EXPLANATION Number of messages received from the MSC that concern thedownlink quality.


No

COUNTER NAME

RELEASE/CHANGED

500905

M DOWNLINK STRENGTH

S4

EXPLANATION Number of messages received from the MSC that concern thestrength of the downlink signal.




61 (74)


No

COUNTER NAME

RELEASE/CHANGED

500906

M DISTANCE

S4

EXPLANATION Number of messages received from the MSC that concern thedistance between the MS and the BTS.


No

COUNTER NAME

RELEASE/CHANGED

500907

M O AND M INTER

S4

EXPLANATION Number of messages received from the MSC that concern O&Mintervention.


No

COUNTER NAME

RELEASE/CHANGED

500908

M RESP TO MSC INVOC

S4

EXPLANATION Number of messages received from the MSC that concern theresponses to invocations from the MSC.


No

COUNTER NAME

RELEASE/CHANGED

500909

M CALL CONTROL

S4

EXPLANATION Number of messages received from the MSC that concern callcontrol.





No

COUNTER NAME

RELEASE/CHANGED

500910

M R IF F REV TO SOURCE

S4

EXPLANATION Number of messages received from the MSC that concern the returnto the source channel due to a radio interface failure.

UPDATED When the cause value is 0x0A.

No

COUNTER NAME

RELEASE/CHANGED

500911

M HANDOVER SUCC

S4

EXPLANATION Number of messages received from the MSC that concern successfulHOs.

UPDATED When the cause value is 0x0B.

No

COUNTER NAME

RELEASE/CHANGED

500912

M BETTER CELL

S4

EXPLANATION Number of messages received from the MSC that concern a bettercell.

UPDATED When the cause value is 0x0C.

No

COUNTER NAME

RELEASE/CHANGED

500913

M DIRECTED RETRY

S4

EXPLANATION Number of messages received from the MSC that concern directedretry.

UPDATED When the cause value is 0x0D.



63 (74)


No

COUNTER NAME

RELEASE/CHANGED

500914

M EQUIPMENT FAIL

S4

EXPLANATION Number of messages received from the MSC that concern equipmentfailures.


No

COUNTER NAME

RELEASE/CHANGED

500915

M NO RADIO RES AVAIL

S4

EXPLANATION Number of messages received from the MSC which report that thereare no radio resources available.


No

COUNTER NAME

RELEASE/CHANGED

500916

M REQ TERR RES UNAVA

S4

EXPLANATION Number of messages received from the MSC which report that therequested terrestrial channel is not available.


No

COUNTER NAME

RELEASE/CHANGED

500917

M CCH OVERLOAD

S4

EXPLANATION Number of messages received from the MSC that concern CCCHoverload.





No

COUNTER NAME

RELEASE/CHANGED

500918

M PROCESSOR OVERLOAD

S4

EXPLANATION Number of messages received from the MSC that concern processoroverload.


No

COUNTER NAME

RELEASE/CHANGED

500919

M BSS NOT EQUIPPED

S4

EXPLANATION Number of messages received from the MSC which report that theBSS is not equipped.


No

COUNTER NAME

RELEASE/CHANGED

500920

M MS NOT EQUIPPED

S4

EXPLANATION Number of messages received from the MSC which report that the MSis not equipped.


No

COUNTER NAME

RELEASE/CHANGED

500921

M TR COD RAT AD UNAV

S4

EXPLANATION Number of messages received from the MSC which report that therequested transcoding or rate adaptation is not available.




65 (74)


No

COUNTER NAME

RELEASE/CHANGED

500922

M CIPH ALG NOT SUPP

S4

EXPLANATION Number of messages received from the MSC which report that theciphering algorithm is not supported.


No

COUNTER NAME

RELEASE/CHANGED

500923

M TERR CHAN ALR ALLC

S4

EXPLANATION Number of messages received from the MSC which report thefollowing events:

UPDATED - When the requested terrestrial circuit is already allocated (causevalue 0x50)- When the contents of the message are invalid (cause value 0x51)- When there is an information element or field missing (cause value0x52)- When there is an incorrect value in the message (cause value 0x53)- When the message is unknown(cause value 0x54)- When there is an unknown information element in the message(cause value 0x55)

No

COUNTER NAME

RELEASE/CHANGED

500924

M PROT ERR B BSC MSC

S4

EXPLANATION Number of messages received from the MSC which report protocolerror between the BSC and the MSC.

UPDATED If the BSC detects a failure which causes the call to be cleared or if theMSC sends a clear command during a non-transparent procedure.




No

COUNTER NAME

RELEASE/CHANGED

500925

M UNEXPECTED

S4

EXPLANATION Number of messages received from the MSC which reportunexpected failures.

No

COUNTER NAME

RELEASE/CHANGED

500926

M INVALID CELL

S4

EXPLANATION Number of messages received from the MSC which report an invalidcell.


No

COUNTER NAME

RELEASE/CHANGED

500927

M INVALID MSG CONT

S4

EXPLANATION Number of messages received from the MSC which report invalidcontents of the message.


No

COUNTER NAME

RELEASE/CHANGED

500928

M IE OR FIELD MISSING

S4

EXPLANATION Number of messages received from the MSC which report that thereis an information element or field missing.




67 (74)


No

COUNTER NAME

RELEASE/CHANGED

500929

INCORRECT VALUE

S4

EXPLANATION Number of messages received from the MSC which report anincorrect value.


No

COUNTER NAME

RELEASE/CHANGED

500930

UNKNOWN MSG TYPE

S4

EXPLANATION Number of messages received from the MSC which report anunknown message type.


No

COUNTER NAME

RELEASE/CHANGED

500931

UNKNOWN IE

S4

EXPLANATION Number of messages received from the MSC which report anunknown information element.


No

COUNTER NAME

RELEASE/CHANGED

500932

M TRANSC OR RATE UNAVAIL

S5

EXPLANATION Number of messages received from the MSC which report that therequested transcoding or rate adaptation is not available.





No

COUNTER NAME

RELEASE/CHANGED

500933

M CIP TYPE MISMATCH

S5

EXPLANATION Number of messages received from the MSC which report that thereis a circuit pool mismatch.


No

COUNTER NAME

RELEASE/CHANGED

500934

M SWITCH CRC POOL

S5

EXPLANATION Number of messages received from the MSC which report circuit poolswitch.


No

COUNTER NAME

RELEASE/CHANGED

500935

M SPEECH VERSION UNAVAIL

S5

EXPLANATION Number of messages received from the MSC which report that therequested speech version is unavailable.


No

COUNTER NAME

RELEASE/CHANGED

500936

M PRE EMPTION

S8

EXPLANATION Number of messages received from the MSC which report pre-emption




69 (74)


No

COUNTER NAME

RELEASE/CHANGED

500937

M TRAFFIC

S8

EXPLANATION Number of messages received from the MSC which report causetraffic

UPDATED When the cause value is 0x0F

No

COUNTER NAME

RELEASE/CHANGED

500938

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500939

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500940

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500941

SPARE

EXPLANATION Spare




No

COUNTER NAME

RELEASE/CHANGED

500942

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500943

SPARE

EXPLANATION Spare

No

COUNTER NAME

RELEASE/CHANGED

500944

SPARE

EXPLANATION Spare

Related topics


Appendix: BSC Clear Codes and Phases



71 (74)


Appendix A BSC Clear Codes and Phases

DEC HEX PHASE

1 0x1 Paging/Initial MS(CCCH and SDCCH or TCH)

2 0x2 MM signalling(SDCCH or TCH)

3 0x3 Basic assignment(SDCCH or TCH)

4 0x4 Release

(SDCCH or TCH)

5 0x5 FACCH assignment(TCH)

6 0x6 SMS establishment(TCH)

7 0x7 SMS establishment(SDCCH)

8 0x8 Ciphering(SDCCH or TCH)

9 0x9 External HO(SDCCH or TCH, source)

10 0xA Internal HO Intra(SDCCH or TCH, source)

11 0xB Internal HO Inter(SDCCH or TCH, source)



73 (74)

BSC Clear Codes and Phases

12 0xC External HO(SDCCH or TCH, target)

13 0xD Internal HO Intra(SDCCH or TCH, target)

14 0xE Internal HO Inter(SDCCH or TCH, target)

15 0xF Conversation.

Related topics






BSC Counters: BSC Level Clear Code MeasurementContentsList of tablesList of figuresSummary of changes1 BSC Counters: BSC Level Clear Code Measurement2 Counters of Clear Code MeasurementAppendix A BSC Clear Codes and Phases

bsc counters bsc level clear code measurement

Documents

nokia bsc s10

nokia logo

permission of nokia

nokia hasmade

documentation areadequate

copyright nokia corporation

bsc clear codes

enbsc counters