Nokia DX Clear Codes

Call Related DX Causes in BSC

dn9814277Issue 11-1 en

# Nokia CorporationNokia Proprietary and Confidential

1 (135)

2003353Nokia BSC/TCSM S11.5 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 Nokia's 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.

Nokia's 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 2005. All rights reserved.

2 (135) # Nokia CorporationNokia Proprietary and Confidential



Contents

Contents 3

List of tables 4

List of figures 5

Summary of changes 7

1 Overview of Call Related DX Causes in BSC 9

2 Functionality of Call Related DX Causes in BSC 11

3 DX Causes in BSC Statistics 153.1 BSC clear code measurement counters for Call Related DX Causes 153.2 Cause values included in observation report 16

4 Functional phases of Call Related DX Causes in BSC 19

5 Cause codes of Call Related DX Causes in BSC 375.1 Success causes 375.2 Failure causes 46

6 DX cause code mapping 656.1 DX causes mapped to BSSMAP causes 656.2 BSSMAP causes mapped to DX causes 766.3 Traffic measurement counters mapped to DX causes 87



3 (135)

Contents

List of tables




List of figures

Figure 1. Phase 1 of DX causes 21


















5 (135)

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 11�1 and 11

Editorial changes.

Changes made between issues 11 and 10

Added two new success causes: ext_out_ibho_to_gsm_c (192) andext_out_ibho_to_utran_c (193).

Deleted two failure causes set by the Abis Interface Program Block:cs_paging_refus_due_load_c (371) and ps_paging_refus_due_load_c (372), andadded one new failure cause: bsc_bsc_conflict_c (373).

The BSSMAP cause of ext_out_inter_system_da_c (191) has changed to directedretry.

Made the above changes also to Section 6.1 DX causes mapped to BSSMAPcauses. and Section 6.2 BSSMAP causes mapped to DX causes.

Added the following causes to the following counters of Section 6.3 Trafficmeasurement counters mapped to DX causes:

Counter 1079: m_call_control_c (909).




Added new counters: 1205, 1206, 1207, 1217 and 1218.

The document has been revised throughout to comply with the latestdocumentation standards.

Changes made between issues 10 and 9�1

New and removed DX Causes

Following causes added:



7 (135)

Summary of changes

ext_out_inter_system_da_c (191), cs_paging_refus_due_load_c (371) andps_paging_refus_due_load_c (372).

Following cause removed: restore_old_c (502).

Chapter Functional phases of Call Related DX Causes in BSC

Figure 16 updated.

Chapter DX cause code mapping

The document DX Cause Code Mapping has ceased to exist and its contents areincluded as a part of this document.

Added the hexadecimal values of the DX causes to the table in DX Causesmapped to BSSMAP Causes.

Additional changes:

The document has been revised throughout to comply with the latestdocumentation standards.




1 Overview of Call Related DX Causes inBSC

All events that occur during a call have a cause. The causes can be coded in orderto observe the transactions in the network, solve possible error situtations andimprove the quality of the network.

Similarly, DX causes are cause codes that describe how the network transactionshave succeeded: they provide information on the causes of events such as callestablishment, handovers, internal faults, timer expiry cases, rejected messagessent to mobile stations or channel releases. The DX causes are conveyed withininternal signalling messages.

Call Related DX Causes give more detailed information on the conditions insidethe BSC than GSM-defined cause values. The DX causes also include GSMcauses when a network element other than the BSC initiates the clearing of atransaction. Cases that are not observed in the MSC can also be examinedthrough the use of DX causes.

The information in the DX causes can be examined using five different methods:

1. using BSC counters on BSC basis

2. using BSC counters on cell basis

3. using clear code counters on BSC basis, divided into different phases

4. using an observation or tracing report on subscriber or channel basis

5. using an observation report on clear code basis.

The counters are grouped into the following measurements, respectively:

1. BSC level clear code PM measurement

2. BSC level clear code SERLEV measurement

3. BSC level clear code measurement.



9 (135)

Overview of Call Related DX Causes in BSC

The measurements have different counters for failures and successful signallingof the basic call and handover cases.

For more information on measurements and observations and how to run them,see Performance measurements and BSC Statistics Administration.

Related topics

. Functionality of Call Related DX Causes in BSC

. DX Causes in BSC Statistics

. Functional phases of Call Related DX Causes in BSC

. Cause codes of Call Related DX Causes in BSC

. DX cause code mapping




2 Functionality of Call Related DX Causesin BSC

A DX cause consists of a cause value and a functional phase:

. a cause value describes the actual event

. a functional phase corresponds with a phase in the signalling scenario orprocedure; it defines when the event has occurred.

DX causes can be divided further into two different cause classes on the basis ofthe cause element:

. success causes

. failure causes.

A success cause is set when an MS receives access to the network with a relevantestablishment cause, or when a handover starts with a relevant handover set-upcause. Correspondingly, a failure cause is set when a failure occurs during a callor a handover. It describes the error that caused the channel release.

Failure causes can be divided further into two different failure classes:

1. Service-level failure. Service for MS terminates unsuccessfully. Service-level failures always lead to call clearing.

2. Informative failure. These types of failures may occur, for example, duringa handover, but they do not result in call clearing, or the MS cannot detectthis kind of failure. In such a case, the call continues on the old channel.Failures that may occur during the call release are also included in thisfailure class.

All failures which have occurred as service-level or informative failures areincluded in the observation or tracing report. The reports also include thesuccessful cases.



11 (135)

Functionality of Call Related DX Causes in BSC

Detection of failures

The handling of a DX cause is located on the GSM layer 3 and the failuredetection can be done in the A interface, Abis interface and inside the BSC.

The BSC is responsible for the following functional parts on layer 3:

. base transceiver station management (BTSM)

. radio resource management (RR)

. base station system application part (BSSAP) .

BTSM and RR are parts of the Abis interface and BSSAP is a part of the Ainterface.

Signalling on the mobility management (MM) layer is transparent to the BSC.The BSC cannot detect all failures that have occurred on the MM layer. Some ofthese failures can be detected, for example, a timer expiry on the lower layer,corrupted messages or other protocol errors. The rest of these failures can be seenas the release of the MSC. The BSC cannot observe these failures if the phase isMM signalling (2) or conversation (15), because the BSC interprets this as asuccessful call. If the failure occurs on layer 1 or 2, the failure can be detected onlayer 3 as a timer expiry or as different kinds of block cause.

Related topics:

. For more information on BTSM, see ETS 300 596 Digital cellulartelecommunications system (Phase 2); Base Station Controller - BaseTransceiver Station (BSC - BTS) interface Layer 3 specification.

. For more information on RR, see ETS 300 557 Digital cellulartelecommunications system (Phase 2); Mobile radio interface layer 3specification.

. For more information on BSSAP, see ETS 300 590 Digital cellulartelecommunications system (Phase 2); Mobile-services Switching Centre -Base Station System (MSC - BSS) interface Layer 3 specification.

Handling of DX Causes

DX causes are handled, as follows:




1. When the program block A detects a failure, it sets the cause and sends theappropriate message to another program block. This internal messageincludes the DX cause element.

2. Program block B, which is responsible for the phase during which the erroroccurred, receives the DX cause. Program block B sets the phase value inthe DX cause element.

3. When the appropriate program block has updated the failure counter, it alsosets a flag in the DX cause element which indicates that the counter hasalready been updated. The counter is updated only once during callsignalling, such as a location update, an SMS or a call.

Note

The DX cause is set by the program block that initiates the channel release. Whenanother network element sends a clearing to the BSC, it is transformed into a DXcause by the program block that receives the clearing.

Priorisation of conflicting failures

Since only one DX cause can be set for one transaction, only the first failure isgenerally set as the DX cause. In a conflict situation, the program block that hasthe highest priority defines the appropriate failure cause.

When two different failures are in conflict, the list of priorities is, as follows:

1. AIVPRB (because it also sets the cause of failure for the MSC)

2. HASPRB

3. other program blocks

The priority handling is implemented in the ABIPRB and the HASPRB and the Ainterface is only responsible for setting the appropriate cause values.

The following program blocks are involved in the handling of DX causes:

ABIPRB The ABIPRB (Abis Interface Program Block) is responsiblefor the normal call phases including basic call, SMS,ciphering and FACCH call set-up. It also updates thesuccessful establishment counters, the Call Successful counter(051015) and sets the failures that have occurred mainly inAbis signalling.



13 (135)

Functionality of Call Related DX Causes in BSC

AIVPRB The AIVPRB (A interface Signalling Program Block in BSC)sets the failures that have occurred mainly in A interfacesignalling.

HASPRB The HASPRB (Handover Attempt Supervisor ProgramBlock) is responsible for the handover phases includingexternal, internal intra and internal inter HO signalling. Italso updates the successful handover counters and sets thefailures which have occurred mainly in HO signalling.

RC0PRB The main purpose of the RC0PRB (Resource ControlProgram Block in BSC) is to implement the interface betweenthe marker and the call control program blocks of the BSC.

RCSPRB The RCSPRB (Radio Connection Supervision ProgramBlock) takes care of the preprocessing of the measurementsamples, determines the RF output power of the MS andBTS, indicates whether a handover is required and performssupervision of the LAPD link by supervising the flow ofmeasurement results coming from the BTS.

RRMPRB The RRMPRB (Radio Resource Management ProgramBlock) controls the use of the radio channels. The programblock also sets the failures that have occurred in RC0PRBsignalling.

SC7PRB The SC7PRB (Speech Circuit Control in GSM BSC AInterface) takes care of the administration of the A interfacespeech circuits. The program block also sets the failures thathave occurred in SC7PRB signalling.

For an overview, see Overview of Call Related DX Causes in BSC.




3 DX Causes in BSC Statistics

The information in the DX causes can be examined using the measurements andobservations of BSC Statistics. The sections below describe this in more detail.


3.1 BSC clear code measurement counters for CallRelated DX Causes

The BSC clear code measurement counters record failures that have occurredduring a call (signalling or conversation). This measurement contains clear codecounters for each of the 15 different phases. All of these counters are failurecounters: their total number is determined by the total number of failure DXcauses. The values of all counters are given on BSC basis.

The counters are updated after a service-level or an informative failure hasoccurred. For a description of the two failure classes, see Functionality of CallRelated DX Causes in BSC.

The counter numbers are determined as follows:

. the first two digits describe the measurement type, which in the BSC clearcode measurement is 50

. the next four digits describe the failure cause.

YYXXXX= counter number

YY= measurement type

XXXX= failure cause value

Each failure cause has its own exact number, which are listed and described inCause codes of Call Related DX Causes in BSC.



15 (135)

DX Causes in BSC Statistics

Example of a clear code counter

If, for example, the clear code counter 500315 (conn_fail_c) has been updated inphase 02, it means that a connection failure has occurred during the MMsignalling phase (phase=02). By using the counters it is possible to see, forexample, how many connection failures have occurred in the MM signallingphase during the measurement period on BSC basis.

Related topics

. 51 BSC Level Clear Code (PM) Measurement

. 57 BSC Level Clear Code (SERLEV) Measurement

3.2 Cause values included in observation report

The observation report includes variables for recording the starting and endingcause/phase. These fields together offer detailed information on callestablishment and call clearing during handovers and basic calls:

. In channel observation, the Phase in and the Cause in fields include theestablishment cause. The Phase out and the Cause out fields are for thechannel release cause.

. In handover observation, the Phase in and the Cause in fields are for thehandover starting cause. The Phase out and the Cause out fields are forthe handover ending cause.

. In clear code observation, the DX cause structure includes the Phase outand the Cause out fields.

When the starting cause (Cause in ) is the same as the ending cause (Cause out ),the event has ended successfully. Correspondingly, when these two variableshave different cause values, the signalling in question was not successful.

The DX cause variables that receive values after the observation are describedbelow:

Phase in This variable contains the phase for a channel seizure.

Cause in This variable contains the cause that indicates the reason for achannel seizure. This can only be a success cause.




Phase out This variable contains the phase when a channel release isstarted.

Cause out This variable contains the cause that indicates the reason for achannel release. This can be a success or a failure cause.



17 (135)

DX Causes in BSC Statistics

4 Functional phases of Call Related DXCauses in BSC

The call transactions are divided into 15 different functional phases, where thenumbers from 1 to 15 represent the phase numbers in the observation report:

1. Paging/initial MS on CCCH

2. MM signalling

3. Basic assignment

4. Release

5. FACCH assignment

6. SMS establishment on TCH

7. SMS establishment on SDCCH

8. Ciphering

9. External handover for source side

10. Internal handover intra for source side

11. Internal handover inter for source side

12. External handover for target side

13. Internal handover intra for target side

14. Internal handover inter for target side

15. Conversation



19 (135)

Functional phases of Call Related DX Causes in BSC

A phase is a stage of the GSM layer 3 call or handover signalling in the BSC. Allthe telecom signalling scenarios can be present as described in the list above andtheir purpose is to identify a failure when it occurs.


Paging/initial MS on CCCH (phase 1)

This phase covers the starting signalling of the mobile originating and the mobileterminating call establishment. The dedicated channel can be a stand-alonededicated control channel SDCCH or a traffic channel TCH.

The ABIPRB is responsible for this phase. When the MS gains access to thenetwork, the ABIPRB sets the establishment cause to the cause field of a DXcause. The success cause is conveyed to the next phase if the signalling isfinished successfully in this phase.

If a failure occurs, the success cause is overwritten with the failure cause and thesignalling continues as call clearing. The failure counter is updated by theRRMPRB (Radio Resource Management Program Block) or, in some cases, bythe ABIPRB.




Figure 1. Phase 1 of DX causes

MM signalling (phase 2)

This phase covers the MM signalling between the mobile subscriber and theMSC. The MM signalling occurring on an SDCCH or a TCH is transparent forthe BSC.

The ABIPRB is responsible for this phase.

The successful cause is received from the previous phase and conveyed further tothe following phase.

If a failure occurs, the successful cause is overwritten with the failure cause andthe signalling continues as call clearing. The RRMPRB updates the failurecounter.

MS BTS BSC MSC

PAGING

PAGING_COMMAND

PAGING_REQUEST

CHANNEL_REQUEST

CHANNEL_REQUIRED

CHANNEL_ACTIVATION_ACKNOWLEDGE

IMMEDIATE_ASSIGNMENT_COMMAND

IMMEDIATE_ASSIGNMENT

SABM>

ESTABLISH_INDICATION

UA

PAGING_RESPONSE

AUTHENTICATION_REQUEST

CHANNEL_ACTIVATION



21 (135)




Basic assignment (phase 3)

This phase covers the mobile subscriber assignment signalling from the SDCCHto the TCH by means of the Basic Call set-up.

MS BTS BSC MSC


AUTHENTICATION_RESPONSE

AUTHENTICATION_RESPONSE

IDENTIFICATION_REQUEST

IDENTIFICATION_REQUEST

IDENTIFICATION_RESPONSE

IDENTIFICATION_RESPONSE

DATA_INDICATION

CALL_PROCEEDING CALL_PROCEEDING

ASSIGNMENT_REQUEST


DT1(set up)

MS BTS BSC MSC

ALERT ALERT

CONNECT CONNECT

CONNECT_ACK CONNECT_ACK








Release (phase 4)

This phase covers the release on an SDCCH or a TCH.


MS BTS BSC MSC

ASSIGNMENT_REQUEST

ASSIGNMENT_COMMAND

SABM ESTABLISH_INDICATION> >

UA

ASSIGNMENT_COMPLETE

ASSIGNMENT_COMPLETE

ALERT ALERT

PHYSICAL_CONTEXT_REQUEST

PHYSICAL_CONTEXT_CONFIRM

CHANNEL_ACTIVATION

CHANNEL_ACTIVATION_ACK

ASSIGNMENT_COMMAND

RF_CHANNEL_RELEASE

RF_CHANNEL_RELEASE_ACK



23 (135)


When a CLEAR COMMAND is received from the MSC, the AIVPRB knowsthat the release is either normal or abnormal. The release is a normal one whenthe MSC releases the channel, for example, at the end of a location update or atthe end of a call.

In a normal release, the AIVPRB sets the cause to normal_rel_c and sends theappropriate message to the ABIPRB including the DX cause. The ABIPRBchecks the DX cause of the message and decides whether to update the counters.When ABIPRB receives the normal_rel_c cause, it updates the counter 051015Call Successful and a successful establishment counter according to the successDX cause for establishment, which was received from the previous phase.

If a failure occurs during this phase, only one of the BSC clear code counters isupdated. The service level counters are not updated, because failures in this phasedo not affect the service of the MS.


FACCH assignment (phase 5)

This phase covers the FACCH Call Set-up assignment signalling. The dedicatedchannel can only be a TCH.



MS BTS BSC MSC

CHANNEL_RELEASE CLEAR_COMMAND

CLEAR_COMPLETE

DISC

UA

RELEASE_INDICATION

RF_CHANNEL_REL_ACK

DEACTIVATE_SACCH

RF_CHANNEL_RELEASE






SMS establishment on TCH (phase 6)

This phase covers the SMS establishment signalling on a TCH. The dedicatedchannel can only be a TCH.




MS BTS BSC MSC

ASSIGNMENT_REQUEST

MODE_MODIFY_ACK

CH_MODE_MODIFICATION

CH_MODE_MODIFY_ACK

CH_MODE_MODIFY_ACK_S

ASSIGNMENT_COMPLETE

ALERT ALERT

MODE_MODIFY_REQ

CH_MODE_MODIFICATION



25 (135)



SMS establishment on SDCCH (phase 7)

This phase covers SDCCH SMS establishment. The dedicated channel can onlybe an SDCCH.




MS BTS BSC MSC

UA(SAPI=3)

ESTABLISH_CONFIRM

DATA_REQUEST(CP_DATA)

DATA_INDICATION(CP_ACK)

DATA_INDICATION(CP_DATA)

DATA_REQUEST(CP_ACK)

DT1(CP_ACK)

DT1(CP_DATA)

DT1(CP_ACK)

SABM(SAPI=3)

DT1(CP_DATA)

ESTABLISH_REQUEST





Ciphering (phase 8)

This phase covers ciphering signalling. The dedicated channel can be an SDCCHor a TCH.




MS BTS BSC MSC

UA(SAPI=3)

ESTABLISH_CONFIRM

DATA_INDICATION(CP_ACK)

DT1(CP_DATA)

ESTABLISH_REQUEST

SABM(SAPI=3)

DATA_REQUEST(CP_DATA)

DT1(CP_ACK)

DATA_INDICATION(CP_DATA)

DT1(CP_DATA)

DT1(CP_ACK)

DATA_REQUEST(CP_ACK)



27 (135)



External handover for source side (phase 9)

This phase covers the external handover signalling of the source side on anSDCCH and a TCH.

The HASPRB is responsible for this phase.

The MS and the BTS send the measurement results to the BSC. The RCSPRBdecides on the basis of the results whether the handover is performed. If thehandover conditions are met, the RCSPRB sets the cause for the handover andsends the appropriate signalling message forward, including the DX cause.

The HASPRB checks the cause of the handover and decides that an externalhandover is to be made. Next, the HASPRB converts the cause for the appropriatetype of handover. The MSC indicates with a CLEAR COMMAND message thatthe signalling has finished successfully. When the BSC receives the CLEARCOMMAND, the AIVPRB knows if the clearing is normal and successful. It setsthe cause to normal_rel_c and sends the appropriate signalling message forward.The HASPRB updates the successful handover counter and the ABIPRB updatesthe successful establishment counter as well as the Call Successful counter(051015) with the success DX cause for establishment, which was received fromthe previous phase.

If a failure occurs before the CLEAR COMMAND is received from the MSC,the success cause is overwritten. The signalling continues as handover clearingand the failure counter is updated by the RRMPRB or, in some cases, theHASPRB.

MS BTS BSC MSC

CIPHERING_MODE_COMMAND

CIPHERING_MODE_COMMAND

CIPHERING_MODE_COMPLETE

CIPHERING_MODE_COMPLETE

ENCRYPTION_COMMAND




If a failure occurs after the CLEAR COMMAND is received from the MSC, nofailure counters are updated because the MS does not observe this kind of failure;the success DX cause counter has been updated because the MS has been releasedimmediately after the clear command.

When the MSC sends a CLEAR COMMAND with the relevant failure cause, thecause is converted into a DX cause and the RRMPRB updates the failure counter.


Internal handover intra for source side (phase 10)

This phase covers the internal intra-cell handover signalling of the source side onan SDCCH and a TCH.


The MS and the BTS send the measurement results to the BSC. The RCSPRBdecides on the basis of the results whether the handover is performed. When thehandover conditions are met, the RCSPRB sets the cause for the handover andsends the appropriate signalling message forward, including the DX cause.

MS BTS BSC MSC

MEAS_REPORT MEAS_RESULT

HO_REQUIRED

HO_COMMAND

HO_CMD HANDOVER_COMMAND

CLEAR_COMMAND

CLEAR_COMPLETE

RF_CHANNEL_RELEASE




29 (135)


The HASPRB checks the cause for the handover and decides that an internalhandover should be made. Next, the HASPRB converts the DX cause for theappropriate handover.

On the source side, the ABIPRB sends the original DX cause (success DX causefor establishment) via the HASPRB to the target ABIPRB. It is taken into use onthe target side after the handover signalling has finished successfully.

The HASPRB updates the successful handover counter and the call continues as anormal call on the target side.

If a failure occurs on the source side before the assignment command is received,the success cause is overwritten and the signalling continues as call clearing. Thefailure counter is updated by the RRMPRB.

On the target side, the HASPRB sets the cause to source_fail_c. No failurecounters are updated because only one counter is updated for each failure; theRRMPRB has updated the failure counter on the source side.


MS BTS BSC MSC


PHYSICAL_CONTEXT_REQUEST_S

PHYSICAL_CONTEXT_CONFIRM_S

ASSIGNMENT_COMMAND

ASSIGNMENT_COMMAND

RF_CHANNEL_RELEASE





Internal handover inter for source side (phase 11)

This phase covers the internal inter-cell handover signalling for the source side onan SDCCH or a TCH.


The success and failure cases are handled as described in Internal handover intrafor source side.


External handover for target side (phase 12)

This phase covers the external handover signalling for the target side on anSDCCH and a TCH.


The BSC receives the HO REQUEST message with the relevant handover cause.The AIVPRB sends the appropriate signalling message to the HASPRB,including the DX cause. The HASPRB converts the cause into the relevant DXcause for the external handover. If the signalling finishes successfully, theHASPRB updates the handover success counter, and the DX cause is conveyed tothe following phase.

If a failure occurs, the successful DX cause is overwritten and the signallingcontinues as handover clearing. The failure counter is updated by the RRMPRBor, in some cases, by the HASPRB.

MS BTS BSC MSC


HO_CMD HANDOVER_COMMAND

HO_PERFORMED

RF_CHANNEL_RELEASE




31 (135)



Internal handover intra for target side (phase 13)

This phase covers the internal intra-cell handover signalling for the target side onan SDCCH and a TCH.


MS BTS BSC MSC

HO_REQUEST1

2

3

4

HANDOVER_ACCESS5 >

HO_DETECTION6

7

8

SABM ESTABLISH_INDICATION9 > 10

UA11

HANDOVER_COMPLETE12

RR13

HANDOVER_COMPLETE14

15

CHANNEL_ACTIVATION


HO_REQUEST_ACK

HO_DETECTION

PHYSICAL_INFO

HO_COMPLETED




See Internal handover intra for source side for a successful case.

If a failure occurs before the assignment has been completed on the target side,the appropriate failure counter is updated. The MS is able to return to the oldchannel. If it returns to the old channel, it sends an assignment failure. This kindof situation only affects the informative counters.

The HASPRB sets the flag restore_old as TRUE and includes it in the DX causethat is sent to the ABIPRB to indicate that the MS returns to the old channel. Thesource side ABIPRB receives the DX cause and the original establishment causeis restored. The signalling continues on the old channel.

If the MS does not return to the old channel (the MS is lost), the HASPRB setsthe source_fail_c as the cause and sends it to the target side ABIPRB. Callclearing is started with the real failure cause on the source side and the failurecounter is updated by the RRMPRB.

If the failure occurs after the assignment has been completed on the target side,the success cause is overwritten and the signalling continues as call clearing.


MS BTS BSC MSC

SABM ESTABLISH_INDICATION

UA

ASSIGNMENT_COMPLETE

RR

CHANNEL_ACTIVATION


HO_PERFORMED



33 (135)


Internal handover inter for target side (phase 14)

This phase covers the internal inter-cell handover signalling for the target side onan SDCCH or a TCH.


The success and failure cases are handled as described in Internal handover intrafor target side .


Conversation (phase 15)

This phase covers MM signalling between the MS and the MSC duringconversation on a TCH.

MS BTS BSC MSC

HANDOVER_ACCESS

HO_DETECTION

SABM ESTABLISH_INDICATION

UA

PHYSICAL_INFO

HANDOVER_COMPLETE

RR

HANDOVER_COMPLETE

CHANNEL_ACTIVATION


HO_PERFORMED





The phase starts when the BSC receives the CONNECT ACK message. Thesuccessful DX cause is received from the previous phase and conveyed further tothe following phase.

If a failure occurs, the successful DX cause is overwritten with the failure causeand the signalling continues as call clearing. The RRMPRB updates the failurecounter.


MS BTS BSC MSC

CONNECT ACK CONNECT ACK

CHANNEL RELEASE CLEAR COMMAND



35 (135)


5 Cause codes of Call Related DX Causesin BSC

Each success and failure cause has its own number that is used to identify it. Thecause codes, their numbers and the cause descriptions can be found in thefollowing sections. The cause number is given inside parentheses, after the causename.

For more information on the relations of DX causes, BSSMAP causes and BSCtraffic measurement counters, see DX Cause Code Mapping. For an overview,see Overview of Call Related DX Causes in BSC.

5.1 Success causes

The success causes are described below:

1. location_update_c (10)

The location update.

2. facch_emergency_call_c (20)

FACCH calls for which the establishment cause is emergency call.

3. facch_reestablishment_c (21)

FACCH calls for which the establishment cause is re-establishment.

4. facch_answer_to_pagin_c (22)

FACCH calls for which the establishment cause is answering to paging.

5. facch_mo_speech_call_c (23)

FACCH calls for which the establishment cause is mobile originatingspeech call.

6. facch_mo_data_call_c (24)



37 (135)

Cause codes of Call Related DX Causes in BSC

FACCH calls for which the establishment cause is mobile originating datacall.

7. facch_other_procedure_c (25)

FACCH calls for which the establishment cause is another procedure.

8. facch_mt_data_call_c (26)

FACCH calls for which the establishment cause is mobile terminating datacall.

9. facch_imsi_detach_c (27)

Number of IMSI detaches on the TCH channel due to SDCCH congestion.

10. basic_emergency_call_c (40)

Basic calls for which the establishment cause is emergency call.

11. basic_reestablishment_c (41)

Basic calls for which the establishment cause is re-establishment.

12. basic_answer_to_pagin_c (42)

Basic calls for which the establishment cause is answering to paging.

13. basic_mo_speech_call_c (43)

Basic calls for which the establishment cause is mobile originating speechcall.

14. basic_mo_data_call_c (44)

Basic calls for which the establishment cause is mobile originating datacall.

15. basic_other_procedure_c (45)

Basic calls for which the establishment cause is another procedure.

16. basic_mt_data_call_c (46)

Basic calls for which the establishment cause is mobile terminating datacall.

17. basic_imsi_detach_c (47)

Number of IMSI detaches on the SDCCH channel.

18. ext_in_ul_quality_c (80)

An incoming external handover. The handover setup cause is uplinkquality.




19. ext_in_ul_strength_c (81)

An incoming external handover. The handover setup cause is uplinkstrength.

20. ext_in_dl_quality_c (82)

An incoming external handover. The handover setup cause is downlinkquality.

21. ext_in_dl_strength_c (83)

An incoming external handover. The handover setup cause is downlinkstrength.

22. ext_in_distance_c (84)

An incoming external handover. The handover setup cause is distance.

23. ext_in_o_and_m_inter_c (85)

An incoming external handover. The handover setup cause is O and Mintervention.

24. ext_in_resp_to_msc_invoc_c (86)

An incoming external handover. The handover setup cause isresp_to_msc_invoc.

25. ext_in_better_cell_c (87)

An incoming external handover. The handover setup cause is better cell.

26. ext_in_directed_retry_c (88)

An incoming external handover. The handover setup cause is directed retry.

27. ext_in_unexpected_c (89)

An incoming external handover. The handover setup cause is unexpected.

28. ext_in_switch_crc_pool_c (90)

An incoming external handover attempt for changing the A interfacecircuit pool.

29. ext_in_pre_empt_c (91)

An incoming external handover. The handover setup cause is preemption.

30. ext_in_bsc_trho_c (92)

An incoming external handover. The handover setup cause is BSC trafficreason handover.

31. ext_in_isho_c (93)



39 (135)


An incoming external inter-system handover.

32. ext_out_dl_rxlev_c (100)

An outgoing external handover. The handover setup cause is downlink rxlevel.

33. ext_out_ul_rxlev_c (101)

An outgoing external handover. The handover setup cause is uplink rxlevel.

34. ext_out_dl_rxqual_c (102)

An outgoing external handover. The handover setup cause is downlink rxquality.

35. ext_out_ul_rxqual_c (103)

An outgoing external handover. The handover setup cause is uplink rxquality.

36. ext_out_dl_interf_c (104)

An outgoing external handover. The handover setup cause is downlinkinterference.

37. ext_out_ul_interf_c (105)

An outgoing external handover. The handover setup cause is uplinkinterference.

38. ext_out_distance_c (106)

An outgoing external handover. The handover setup cause is distance.

39. ext_out_pbgt_ho_c (107)

An outgoing external handover. The handover setup cause is PBGThandover.

40. ext_out_umbrella_ho_c (108)

An outgoing external handover. The handover setup cause is umbrellahandover.

41. ext_out_forced_ho_c (109)

An outgoing external handover. The handover setup cause is forcedhandover.

42. ext_out_dr_ho_c (110)

An outgoing external handover. The handover setup cause is DR (directedretry) handover.




43. ext_out_tr_ho_c (111)

An outgoing external handover. The handover setup cause is TR (trafficreason) handover.

44. ext_out_idr_ho_c (112)

An outgoing external handover. The handover setup cause is IDRhandover.

45. ext_out_pre_empt_ho_c (113)

An outgoing external handover. The handover setup cause is pre-emptionhandover.

46. ext_out_rap_fld_drop_c (114)

An outgoing external handover. The handover setup cause is rapid fielddrop.

47. ext_out_low_distance_c (115)

An outgoing external handover. The handover setup cause is low distance(extended cell radius functionality).

48. ext_out_switch_crc_pool_c (116)

An outgoing external handover attempt to change the A interface circuitpool.

49. ext_out_slow_moving_ms_c (117)

An outgoing external handover. The handover setup cause is Slow MovingMS in the Macro Cell. The slow moving detection is based on the receivedmeasurement of adjacent micro cells and on the umbrella-like handovercriterias.

50. ext_out_det_slow_mov_ms_c (118)

An outgoing external handover. The handover setup cause is low speed ofMS. The slow moving detection is based on the MS speed indications sentby the BTS.

51. ext_out_det_fast_mov_ms_c (119)

An outgoing external handover. The handover setup cause is high speed ofMS. The fast moving detection is based on the MS speed indications sentby the BTS.

52. ext_out_erfd_ho_c (163)

Handover cause Enhanced Field Drop handover.

53. ext_out_bsc_trho_c (164)



41 (135)


An outgoing external handover whose setup cause is BSC traffic reasonhandover.

54. ext_out_isho_c (190)

An outgoing external inter-system handover. The handover setup cause isBSC traffic load.

55. ext_out_inter_system_da_c (191)

An outgoing external inter-system direct access handover. The handoversetup cause is DR (directed retry) handover.

56. ext_out_ibho_to_gsm_c (192)

An outgoing external IMSI based handover from the source GSM networkto the GSM authorized networks. The handover setup cause is BSC trafficload.

57. ext_out_ibho_to_utran_c (193)

An outgoing external IMSI based handover from the source GSM networkto the UTRAN authorized networks. The handover setup cause is BSCtraffic load.

58. inter_dl_rxlev_c (120)

An internal inter handover. The handover setup cause is downlink rx level.

59. inter_ul_rxlev_c (121)

An internal inter handover. The handover setup cause is uplink rx level.

60. inter_dl_rxqual_c (122)

An internal inter handover. The handover setup cause is downlink rxquality.

61. inter_ul_rxqual_c (123)

An internal inter handover. The handover setup cause is uplink rx quality.

62. inter_dl_interf_c (124)

An internal inter handover. The handover setup cause is downlinkinterference.

63. inter_ul_interf_c (125)

An internal inter handover. The handover setup cause is uplinkinterference.

64. inter_distance_c (126)

An internal inter handover. The handover setup cause is distance.




65. inter_pbgt_ho_c (127)

An internal inter handover. The handover setup cause is PBGT handover.

66. inter_umbrella_ho_c (128)

An internal inter handover. The handover setup cause is umbrellahandover.

67. inter_forced_ho_c (129)

An internal inter handover. The handover setup cause is forced handover.

68. inter_dr_ho_c (130)

An internal inter handover. The handover setup cause is DR handover.

69. inter_tr_ho_c (131)

An internal inter handover. The handover setup cause is TR (traffic reason)handover.

70. inter_idr_ho_c (132)

An internal inter handover. The handover setup cause is IDR handover.

71. inter_pre_empt_ho_c (133)

An internal inter handover. The handover setup cause is pre-emptionhandover.

72. inter_rap_fld_drop_c (134)

An internal inter handover. The handover setup cause is rapid field drop.

73. inter_low_distance_c (135)

An internal inter handover. The handover setup cause is low distance(extended cell radius functionality).

74. inter_ok_ci_ratio_c (136)

An internal inter handover. The handover setup cause is ok C/I ratio(Underlay-overlay handover).

75. inter_bad_ci_ratio_c (137)

An internal inter handover. The handover setup cause is bad C/I ratio(Underlay-overlay handover).

76. inter_slow_moving_ms_c (138)



43 (135)


An internal inter handover. The handover setup cause is Slow Moving MSin the Macro Cell. The slow moving detection is based on the receivedmeasurement of adjacent micro cells and on the umbrella-like handovercriterias.

77. inter_det_slow_mov_ms_c (139)

An internal inter handover. The handover setup cause is low speed of theMS . The slow moving detection is based on the MS speed indications sentby the BTS.

78. inter_det_fast_mov_ms_c (156)

An internal inter handover. The handover setup cause is high speed of theMS . The fast moving detection is based on the MS speed indications sentby the BTS.

79. inter_erfd_ho_c (157)

Handover cause Enhanced Field Drop handover.

80. Inter_direct_access_c (158)

The counter indicates the number of successful internal inter-cellhandovers from a dedicated control channel to a super-reuse TRX.Handover setup cause is direct access procedure.

81. inter_bsc_trho_c (159)

An internal inter handover whose setup cause is BSC traffic reasonhandover.

82. inter_dadlb_c (160)

An internal inter handover whose setup cause is Direct Access to DesiredLayer/Band.

83. intra_dl_interf_c (140)

An internal intra handover. The handover setup cause is downlinkinterference.

84. intra_ul_interf_c (141)

An internal intra handover. The handover setup cause is uplinkinterference.

85. intra_forced_ho_c (142)

An internal intra handover. The handover setup cause is forced handover.

86. intra_dl_rxqual_c (143)




An internal intra handover. The handover setup cause is downlink rxquality.

87. intra_ok_ci_ratio_c (144)

An internal intra handover. The handover setup cause is ok C/I ratio(Underlay-overlay handover).

88. intra_bad_ci_ratio_c (145)

An internal intra handover. The handover setup cause is bad C/I ratio(Underlay-overlay handover).

89. intra_pre_empt_ho_c (146)

An internal intra handover. The handover setup cause is pre-emptionhandover.

90. intra_distance_c (147)

Intra cell handover from a normal area to an extended area. Intra cellhandover from a normal area to an extended area is performed when thetiming advance (TA) of the MS equals or is greater than that defined by theparameter maxMSDistanceHOThreshold.

91. intra_low_distance_c (148)

Intra cell handover from an extended area to a normal area. Intra cellhandover from an extended area to a normal area is performed when thetiming advance (TA) of the MS equals or is greater than that defined by theparameter minMSDistanceHOThreshold.

92. intra_dr_ho_c (149)

Assignment attempt from an SDCCH to a super-reuse frequency.

93. intra_direct_access_c (150)

The counter indicates the number of successful internal intra-cellhandovers from a dedicated control channel to a super-reuse TRX .Handover setup cause is direct access procedure.

94. intra_gprs_ho_c (151)

An internal intra handover. The handover is performed in order to get moreresources for GPRS .

95. intra_ho_to_amr_hr_c (152)

An intra cell handover from AMR FR to AMR HR.

96. intra_ho_to_amr_fr_c (153)

An intra cell handover from AMR HR to AMR FR.



45 (135)


97. intra_inter_band_tch_c (154)

A TCH-TCH handover that has been made due to load reasons betweenBTSs on different frequency bands of a segment.

98. intra_inter_band_sdc_c (155)

An SDCCH-SDCCH handover, based on SDCCH reservation duration in aBTS on the BCCH frequency band, to a BTS on another frequency band.

99. intra_inter_bts_type_tch_c (166)

A TCH-TCH handover from an UltraSite or a ConnectSite 100 BTS to aTalk Family BTS due to load reasons within a segment.

100. intra_inter_bts_type_sdc_c (167)

An SDCCH-SDCCH handover, based on SDCCH reservation durationfrom an UltraSite or ConnectSite 100 BTS to a Talk Family BTS within asegment.

101. intra_ho_due_to_hscsd_c (168)

An intra cell handover made to enable an HSCSD upgrade.

102. intra_inter_band_due_lev_c (169)

A TCH-TCH handover from a non-BCCH frequency layer between BTSson different frequency bands of a segment, performed due to weakdownlink signal level.

5.2 Failure causes

The failure causes are divided into the following groups according to the programblock that sets the cause in question:

. causes set by the Abis Interface Program Block (ABIPRB)

. causes set by the Radio Connection Supervision Program Block (RCSPRB)

. causes set by the A interface Signalling Program Block in BSC (AIVPRB)

. causes set by the Speech Circuit Control in GSM BSC A interface(SC7PRB)

. causes set by the Resource Control Program Block in BSC (RC0PRB)

. causes set by the Handover Attempt Supervisor Program Block (HASPRB)

. causes set by the Mobile Services Switching Centre (MSC).




Causes set by the Abis Interface Program Block (ABIPRB)

1. user_act_block_c (300)

Channel blocking caused by the user.

2. netw_act_block_c (301)

Channel blocking caused by the network.

3. bts_fail_block_c (302)

Channel blocking caused by a BTS failure.

4. lapd_fail_block_c (303)

Channel blocking caused by an LAPD failure.

5. abis_fail_block_c (304)

Channel blocking caused by an Abis failure.

6. abis_msg_corrup_to_bts_c (305)

The packing of the Abis interface message fails.

7. ass_fail_msg_c (306)

The Abis interface receives an ASSIGNMENT FAILURE message fromthe MS during a Basic Call.

8. block_slave_c (307)

Channel blocking caused by some other reason than the ones given above.

9. ch_act_nack_c (308)

The Abis interface receives a CHANNEL ACTIVATION NACK messageor its contents have been corrupted.

10. ch_act_nack_om_inter_c (309)

The Abis interface receives a CHANNEL ACTIVATION NACK message,and the cause is O and M intervention .

11. ch_act_nack_equip_fail_c (310)

The Abis interface receives a CHANNEL ACTIVATION NACK message,and the cause is equipment failure .

12. ch_act_nack_encryp_alg_c (311)

The Abis interface receives a CHANNEL ACTIVATION NACK messageand the cause is encryption algorithm not supported .



47 (135)


13. ch_act_nack_rad_ch_alr_a_c (312)

The Abis interface receives a CHANNEL ACTIVATION NACK messageand the cause is radio channel already allocated .

14. ch_act_nack_serv_not_ava_c (313)

The Abis interface receives a CHANNEL ACTIVATION NACK messageand the cause is service is not available .

15. ch_act_fail_c (314)

The Abis interface receives a CHANNEL ACTIVATION ACK messageand its contents have been corrupted or a timer expires while waiting forthe message.

16. conn_fail_c (315)

The Abis interface receives a CONNECTION FAILURE message.

17. conn_fail_rad_inf_fail_c (316)

The Abis interface receives a CONNECTION FAILURE message and itscause is radio interface failure .

18. conn_fail_rad_link_fail_c (317)

The Abis interface receives a CONNECTION FAILURE message and itscause is radio link failure .

19. conn_fail_rem_trans_fail_c (318)

The Abis interface receives a CONNECTION FAILURE message and itscause is remote transcoder failure .

20. data_ind_corrup_c (319)

The Abis interface receives a DATA INDICATION message whosecontents have been corrupted.

21. err_ind_c (320)

The Abis interface receives an ERROR INDICATION message.

22. estab_ind_fail_c (321)

A timer expires while waiting for an ESTABLISH INDICATIONmessage.

23. estab_conf_fail_c (322)

The Abis interface receives an ESTABLISH CONFIRM message. Thecontents of the message have been corrupted or a timer expires whilewaiting for the message.




24. ho_fail_c (323)

The handover has failed and the MS returns to the source channel. The MShas sent an ASSIGNMENT FAILURE or a HANDOVER FAILUREmessage to the network during the handover.

25. ho_detect_fail_c (324)

The Abis interface receives an HO DETECT message. The contents of themessage have been corrupted or a timer expires while waiting for themessage.

26. mode_mod_nack_c (325)

The Abis interface receives a MODE MODIFY NACK message.

27. mode_mod_ack_fail_c (326)

The Abis interface receives a MODE MODIFY ACK message whosecontents have been corrupted or a timer expires while waiting for themessage.

28. no_meas_result_c (327)

No measurement result messages from the BTS.

29. no_resp_from_copro_c (328)

Timer expires because the co-process does not respond. A BSC-internalfailure.

30. phy_cont_conf_fail_c (329)

The Abis interface receives a PHYSICAL CONTEXT CONFIRMmessage. The contents have been corrupted or a timer expires whilewaiting for the message.

31. rcs_alg_start_ack_fail_c (330)

The Abis interface receives an rcs_algorithm_start_ack message whosecontents have been corrupted or a timer expires while waiting for themessage. BSC-internal signalling.

32. rcs_alg_cl_ack_fail_c (331)

The Abis interface receives an rcs_algorithm_clear_ack message whosecontents have been corrupted or a timer expires while waiting for themessage. BSC-internal signalling.

33. rc0_disco_ind_c (332)

The Abis interface receives an rco_disconnect_ind message from RC0.

34. rf_ch_rel_ack_fail_c (333)



49 (135)


The Abis interface receives an RF CH REL ACK message whose contentshave been corrupted or a timer expires while waiting for the message.

35. rel_ind_c (334)

The Abis interface receives a RELEASE INDICATION message.

36. rel_ind_fail_c (335)

The Abis interface receives a RELEASE INDICATION message. Thecontents of the message have been corrupted or a timer expires whilewaiting for the message.

37. signalling_error_c (336)

DTAP signalling fails.

38. state_conflict_c (337)

An attempt to activate a blocked channel in the Abis interface.

39. type_conflict_c (338)

An attempt to activate a channel with the wrong information in the Abisinterface.

40. forced_rel_c (339)

Forced TCH release.

41. rej_phantom_res_c (340)

Rejected phantom reservations caused by the wrong establishment cause inthe channel required message from the MS or a too long distance betweenthe MS and the BTS.

42. overload_c (341)

Overload message from the BTS.

43. abi_switchover_c (342)

The BCSU switchover has been started.

44. sapi_3_fail_c (343)

During SMS establishment, the Abis interface receives a RELEASEINDICATION message or the ESTABLISH_INDICATION messagereceived has been corrupted.

45. paging_msg_fail_c (344)

The Abis interface receives an MS PAGING message and the channel hasbeen blocked.




46. ch_required_fail_c (345)

The Abis interface receives a CHANNEL REQUIRED message whosecontents have been corrupted.

47. mode_mod_nack_equip_fail_c (346)

The Abis interface receives a MODE MODIFY NACK message with thecause equipment failure .

48. mode_mod_nack_trc_rat_un_c (347)

The Abis interface receives a MODE MODIFY NACK message with thecause requested transcoding/rate adaption not available .

49. rrm_serv_req_nack_c (348)

The Abis interface receives an RRM CH SER REQ NACK message.

50. ch_mode_mod_fail_c (349)

The Abis interface receives a CH MODE MODIFYACK message and themode does not correspond to the requested mode.

51. ass_fail_c (350)

Timer expires while waiting for the ASSIGNMENT COMPLETEmessage.

52. dr_fail_c (351)

Directed retry procedure fails.

53. coprocess_fail_c (352)

A failure has occurred in co-process.

54. err_rep_enc_alg_not_imp_c (353)

An ERROR REPORT message is received from the BTS and the cause isencryption algorithm not implemented .

55. error_report_c (354)

An ERROR REPORT message is received from the BTS.

56. ch_act_nack_ch_mode_err_c (355)

The Abis interface receives a CHANNEL ACTIVATION NACK messageand the failure cause is either not implemented unspecified or mandatoryIE error .

57. ch_act_nack_gen_ie_err_c (356)



51 (135)


The Abis interface receives a CHANNEL ACTIVATION NACK messageand the failure cause is general IE error .

58. speech_version_unavail_c (357)

The Abis interface receives an ASSIGNMENT FAILURE message or aHANDOVER FAILURE message from the MS during an assignment or ahandover and the RR cause is channel mode unacceptable .

59. ignored_double_rand_acc_c (358)

If two incoming random accesses have the same frame number, the latterone is ignored when random access buffering is used in an extended rangecell.

60. rtsl_reconf_fail_c (359)

Reconfiguration of a dynamic SDCCH resource has failed duringimmediate assignment. All SDCCH resources controlled by the BCSU arealready in use.

61. ho_interrupted_c (360)

If an assignment procedure is started before the MS is assigned to move toa new channel, the handover attempt is terminated with DX causeho_interrupted_c.

62. downgrade_c (361)

Number of channel releases caused by a downgrade.

63. ho_not_started_c (362)

Number of rejected HO starts due to other ongoing procedures.

64. conf_change_not_allowed_c (363)

Number of rejected upgrades, downgrades and ALAs due to other ongoingprocedures.

65. conf_change_bts_fail_c (364)

Number of failed configuration changes due to a MODE MODIFY NACKmessage or no answer from the BTS.

66. conf_change_ms_fail_c (365)

Number of failed configuration changes due to a configuration changereject or no answer from the MS.

67. hscsd_copro_fail_c (366)

Number of channel releases caused by a failure in another channel in theHSCSD configuration.




68. sub_timer_c (367)

Number of timer expiries due to sub-channel not responding to the mainchannel in the HSCSD connection.

69. pre_emption_c (368)

Number of TCH pre-emption releases.

70. upgrade_fail_c (369)

Number of upgrade procedure failures.

71. estab_ind_corrupted_c (370)

Number of ESTABLISH INDICATION messages which the Abisinterface receives because of the corrupted contents of the message.

72. bsc_bsc_conflict_c (373)

Number of unsuccessful channel setups when BSC-BSC conflict control isused.

Causes set by the Radio Connection Supervision Program Block (RCSPRB)

1. timing_advance_c (400)

The call is released after the distance between the MS and the BTS hasreached the maximum value allowed, that is, after the MS has exceeded theplanned cell boundaries.

2. rrm_switch_crc_pool_c (401)

The Radio Resource Management Program Block (RRMPRB) sets thiscause in the TCH RESOURCE REQUEST NEGATIVEACKNOWLEDGEMENT message in order to indicate the A interfacecircuit pool change request.

3. rrm_speech_ver_unavail_c (402)

The requested speech version is not supported by the target BTS.

4. bts_not_supporting_c (403)

A resource that is not supported by the BTS has been requested.

5. ms_not_supporting_c (404)

A resource that is not supported by the MS has been requested.

6. rrm_invalid_cell_c (405)



53 (135)


The traffic channel allocation in the external handover has failed. TheHANDOVER REQUEST message received by the BSS indicates a targetcell that is not controlled by the BSS.

Causes set by the A interface Signalling Program Block in BSC (AIVPRB)

1. aiv_hand_act_fail_c (600)

Activation of a hand process fails in the AIVPRB master.

2. aiv_ssp_c (601)

SCCP connection establishment is not possible because the subsystem is inthe prohibited status. The situation is detected by the AIVPRB master.

3. sccp_conn_fail_c (602)

SCCP connection establishment fails. A CREF message is received fromthe MSC.

4. sccp_conn_timeout_c (603)

No response from the MSC to the SCCP connection establishment.

5. sccp_release_c (604)

Abnormal release of the SCCP connection (RLSD received).

6. global_reset_c (606)

State change of an SCCP subsystem or a RESET message from the MSC.

7. no_dtap_from_msc_c (608)

No DTAP message from the MSC after a successful SCCP connectionestablishment.

8. ho_denied_assign_c (609)

Starting of the handover is not allowed because an assignment procedure isin progress.

9. ho_denied_ciphering_c (610)

Starting of the handover is not allowed because the ciphering procedure isin progress.

10. ho_denied_clear_c (611)

Starting of the handover is not allowed because the call clearing procedureis in progress.

11. ho_denied_no_sccp_conn_c (612)




Starting of an external SDCCH handover is not allowed because the SCCPconnection establishment is not complete.

12. T7_expiry_c (613)

Expiry of GSM timer T7.

13. T10_expiry_c (614)

Expiry of GSM timer T10.

14. aiv_crct_res_timeout_c (615)

Timeout in the AIVPRB while allocating an A interface speech circuit.

15. aiv_crct_conn_timeout_c (616)

Timeout in the AIVPRB while connecting an A interface speech circuit.

16. aiv_crct_disconn_timeout_c (617)

Timeout in the AIVPRB while disconnecting an A interface speech circuit.

17. aiv_crct_rel_timeout_c (618)

Timeout in the AIVPRB while releasing an A interface speech circuit.

18. aiv_timeout_c (619)

Timeout in the AIVPRB in BSC internal communication.

19. act_ctrl_timeout_c (620)

The BSC internal supervision timer, which supervises the communicationbetween the Abis and the A interface, has expired.

20. invalid_bssmap_msg_c (621)

An erroneous message, which leads to the clearing of the call, is receivedfrom the MSC.

21. unknown_a_pcm_c (622)

Message received concerning an unknown A interface circuit.

22. ho_denied_no_proper_crc_c (623)

Handover is denied when the AIVPRB receives the handover inquirymessage from the Handover Attempt Supervisor Program Block(HASPRB) with the cause switch circuit pool and there is no proper Ainterface circuit fitting in with the pool list of the inquiry message.

23. ch_type_mismatch_c (624)



55 (135)


The radio interface data rate requirement is totally contradictory with theTCH channel rate request of the channel type IE included in the normalAssignment Request or Handover Request. In the Assignment Requestrelated to the In Call Modification or the FACCH call setup, the TCHchannel rate request or the data rate request are totally contradictory withthe type of TCH where the call is to be maintained.

24. aiv_transc_or_rate_unava_c (625)

The TCH type requested by the MSC is not supported.

25. aiv_speech_version_unava_c (626)

The speech coder version requested by the MSC is not supported.

26. aiv_pagin_refus_big_load_c (627)

A PAGING message is received from the MSC when the BCSU unit loadis too high. The load is observed by the number of unhandled messages inthe unit.

27. aiv_conn_refresh_timeout_c (628)

Timeout in the connection refreshing procedure.

28. aiv_conn_refresh_failed_c (629)

The connection refreshing procedure has failed.

Causes set by the Speech Circuit Control in GSM BSC A interface (SC7PRB)

1. a_tsl_user_mismatch_c (800)

A request to connect, disconnect or release a speech circuit is receivedfrom a process which is not recorded as a user of the circuit in the internalcontrol tables of SC7PRB.

2. sc7_crct_res_timeout_c (801)

Timeout in the SC7PRB while allocating an A interface speech circuit.

3. sc7_crct_conn_timeout_c (802)

Timeout in the SC7PRB while connecting an A interface speech circuit.

4. sc7_crct_disconn_timeout_c (803)

Timeout in the SC7PRB while disconnecting an A interface speech circuit.

5. sc7_crct_rel_timeout_c (804)

Timeout in the SC7PRB while releasing an A interface speech circuit.

6. a_tsl_blocked_c (805)




Assignment of a circuit that is blocked.

7. a_tsl_status_unknown_c (806)

Assignment of a circuit whose status is unknown.

8. lsi_access_fail_c (807)

Access to the Line Signalling File (LSIGNL) failed.

9. scc_access_fail_c (808)

Access to the System-controlled Circuit State File (SCCTST) failed.

10. undef_tsl_in_lsi_c (809)

The circuit concerned is not defined in the LSIGNL file.

11. crct_equipment_fail_c (810)

The SC7PRB has detected a situation which has been caused by hardwareproblems.

12. reset_crct_c (811)

The RESET CIRCUIT message has been received from the MSC.

13. sc7_ssp_c (813)

An error caused by the SCCP prohibited status. The situation has beendetected by the SC7PRB.

14. a_pcm_fault_c (815)

A fault has been detected in the 2-Mbit PCM connection.

15. a_crct_removed_c (817)

A speech circuit has been removed from use.

16. a_et_state_change_c (819)

State change of the ET has occurred.

Causes set by the Resource Control Program Block in BSC (RC0PRB)

1. rc0_hand_act_fail_c (700)

The RC0PRB master fails to activate a hand process.

2. a_crct_alr_res_c (701)

Assignment of a speech circuit which has already been allocated.

3. a_crct_conn_err_c (702)



57 (135)


Connection error in marker while connecting an A interface speech circuit.

4. rc0_crct_conn_timeout_c (703)

Timeout in the RC0PRB while connecting an A interface speech circuit.

5. access_out_of_crct_tbl_c (704)

Requested speech circuit not found in the circuit control table.

6. a_crct_rel_err_c (705)

Circuit release error in marker while releasing an A interface speechcircuit.

7. rc0_transc_or_rate_unava_c (706)

The requested channel rate corresponding to the A interface circuit poolhas not been defined on the A interface.

8. rc0_cip_type_mismatch_c (707)

The circuit type A is totally contradictory with the TCH channel raterequirement or the data rate requirement implies the circuit pool change.

9. rc0_inv_msg_contents_c (708)

The radio interface data rate requirement is totally contradictory with the Ainterface pool configuration.

10. rc0_req_speech_ver_unava_c (709)

BSC has received either an ASSIGNMENT REQUEST or a HANDOVERREQUEST message containing speech codec versions, none of which aresupported by the BSC.

11. rc0_hunting_queue_full_c (710)

The hunting queue is full.

12. rc0_a_crct_congestion_c (711)

There is no free circuit for the call.

13. rc0_a_search_error_c (712)

The content of the hunting request message is invalid.

14. rc0_crct_pool_mismatch_c (713)

The hunted circuit is from the wrong circuit pool.

15. rc0_rej_due_eme_call_c (714)

The hunting queue is full. An emergency call has taken priority over theordinary call.




16. rc0_ilc_file_error_c (715)

A interface circuit reservation fails because no pool is available on thehunting list.

Causes set by the Handover Attempt Supervisor Program Block (HASPRB)

1. ho_not_allowed_c (500)

External handover was not allowed during a FACCH call setup, externalDR handover was disabled, or all candidate cells for an external handoverwere n-areas of the extended cells.

2. no_radio_res_avail_c (501)

No radio resources in the BTS for channel reservation during handoversignalling.

3. no_resp_from_coprocess_c (503)

Signalling with the internal processes has failed during handoversignalling.

4. no_resp_to_radio_res_req_c (504)

Target channel reservation has failed during handover signalling. Noanswer to the radio resource request.

5. has_state_conflict_c (505)

Target channel reservation has failed. CHANNEL ACTIVATION ACKmessage not been received and the timer for it has expired.

6. clear_cmd_not_received_c (506)

No CLEAR COMMAND has been received from the A interface duringexternal source handover signalling.

7. ms_is_lost_c (507)

The timer t3107, t3103 or t9113 has expired. An ASSIGNMENTCOMPLETE or HANDOVER COMPLETE message has not beenreceived. The MS has not established a channel to the target side.

8. no_resp_to_ho_cpl_msg_c (508)

Problems in sending the HANDOVER PERFORMED message by theBSC.

9. has_switchover_c (509)

Switchover has been started and the handover has failed.

10. target_fail_c (510)



59 (135)


Failure in the target channel.

11. source_fail_c (511)

Failure in the source channel.

12. has_call_control_c (512)

The master has failed to create a hand.

13. adj_cell_id_err_c (513)

The handover attempt was interrupted when the BSC noticed that the targetcell information (BCCH frequency and/or BSIC) received from the MSCin the HANDOVER COMMAND message is incorrect. This counterindicates that information in the source BSS Radio Network ConfigurationDatabase concerning adjacent cells is incorrect.

Causes set by the Mobile Services Switching Centre (MSC)

These causes are only possible during signalling. The BSC cannot observe thesecauses if the phase is MM signalling (2) or conversation (15).

1. m_radio_if_mess_fail_c (900)

Cause value 0x00 radio interface message failure received from the MSC.

2. m_radio_if_fail_c (901)

Cause value 0x01 radio interface failure received from the MSC.

3. m_uplink_quality_c (902)

Cause value 0x02 uplink quality received from the MSC.

4. m_uplink_strength_c (903)

Cause value 0x03 uplink strength received from the MSC.

5. m_downlink_quality_c (904)

Cause value 0x04 downlink quality received from the MSC.

6. m_downlink_strength_c (905)

Cause value 0x05 downlink strength received from the MSC.

7. m_distance (906)

Cause value 0x06 distance received from the MSC.

8. m_o_and_m_inter_c (907)

Cause value 0x07 O and M intervention received from the MSC.




9. m_resp_to_msc_invoc_c (908)

Cause value 0x08 response to MSC invocation received from the MSC.

10. m_call_control_c (909)

Cause value 0x09 call control received from the MSC.

11. m_r_if_f_rev_to_old_c (910)

Cause value 0x0A radio interface failure, reversion to old channelreceived from the MSC.

12. m_handover_succ_c (911)

Cause value 0x0B handover successful received from the MSC.

13. m_better_cell_c (912)

Cause value 0x0C better cell received from the MSC.

14. m_directed_retry_c (913)

Cause value 0x0D directed retry received from the MSC.

15. m_equipment_fail_c (914)

Cause value 0x20 equipment failure received from the MSC.

16. m_no_radio_res_avail_c (915)

Cause value 0x21 no radio resource available received from the MSC.

17. m_req_terr_res_unava_c (916)

Cause value 0x22 requested terrestrial resource unavailable received fromthe MSC.

18. m_ccch_overload_c (917)

Cause value 0x23 ccch overload received from the MSC.

19. m_processor_overload_c (918)

Cause value 0x24 processor overload received from the MSC.

20. m_bss_not_equipped_c (919)

Cause value 0x25 bss not equipped received from the MSC.

21. m_ms_not_equipped_c (920)

Cause value 0x26 ms not equipped received from the MSC.

22. m_tr_cod_rat_ad_unav_c (921)



61 (135)


Cause value 0x30 requested transcoding/rate adaption unavailablereceived from the MSC.

23. m_ciph_alg_not_supp_c (922)

Cause value 0x40 ciphering algorithm not supported received from theMSC.

24. m_terr_chan_alr_allc_c (923)

Cause value 0x50 terrestrial circuit already allocated received from theMSC.

25. m_prot_err_b_bsc_msc_c (924)

Cause value 0x60 protocol error between BSC and MSC received from theMSC.

26. m_unexpected_c (925)

Unexpected failure from the MSC.

27. m_invalid_cell_c (926)

Cause value 0x27 invalid cell received from the MSC.

28. m_invalid_msg_cont_c (927)

Cause value 0x51 invalid message contents received from the MSC.

29. m_ie_or_field_missing_c (928)

Cause value 0x52 information element or field missing received from theMSC.

30. m_incorrect_value_c (929)

Cause value 0x53 incorrect value received from the MSC.

31. m_unknown_msg_type_c (930)

Cause value 0x54 unknown message type received from the MSC.

32. m_unknown_ie_c (931)

Cause value 0x55 unknown information element received from the MSC.

33. m_transc_or_rate_unavail_c (932)

Cause value 0x30 requested transcoding/rate adaption unavailablereceived from the MSC.

34. m_cip_type_mismatch_c (933)

Cause value 0x31 circuit pool mismatch received from the MSC.




35. m_switch_crc_pool_c (934)

Cause value 0x32 switch circuit pool received from the MSC.

36. m_speech_version_unavail_c (935)

Cause value 0x31 requested speech version unavailable received from theMSC.

37. m_pre_empt_c (936)

Cause value 0x29 preemption received from the MSC.

38. m_traffic_c (937)

Cause value 0x0F traffic received from the MSC.



63 (135)


6 DX cause code mapping

The purpose of the following tables is to help the user to determine the relationsbetween DX causes, BSSMAP causes and BSC traffic measurement counters.

The first table maps DX causes to BSSMAP causes, the second BSSMAP causesto DX causes and the third traffic measurement to the DX causes which cause thecounters to increment.


6.1 DX causes mapped to BSSMAP causes

The following table lists the BSC-internal DX causes and the correspondingBSSMAP causes that are used on the A interface.

HEX Dec DX cause BSSMAP cause HEX DEC

50 80 ext_in_ul_quality_c Uplink quality 2 2

51 81 ext_in_ul_strength_c Uplink strength 3 3

52 82 ext_in_dl_quality_c Downlink quality 4 4

53 83 ext_in_dl_strength_c Downlink strength 5 5

54 84 ext_in_distance_c Distance 6 6

55 85 ext_in_o_and_m_inter_c O and M intervention 7 7

56 86 ext_in_resp_to_msc_invoc_c Response to MSC invocation 8 8

57 87 ext_in_better_cell_c Better cell C 12

58 88 ext_in_directed_retry_c Directed retry D 13



65 (135)

DX cause code mapping


59 89 ext_in_unexpected_c Used if the cause of incomingexternal handover is notrecognised or not mentioned atall

5A 90 ext_in_switch_crc_pool_c Switch circuit pool 32 50

5B 91 ext_in_pre_empt_c Preemption 29 41

5C 92 ext_in_bsc_trho_c Traffic F 15

5D 93 ext_in_isho_c Used if the incoming externalhandover is an inter�systemhandover

64 100 ext_out_dl_rxlev_c Downlink strength 5 5

65 101 ext_out_ul_rxlev_c Uplink strength 3 3

66 102 ext_out_dl_rxqual_c Downlink quality 4 4

67 103 ext_out_ul_rxqual_c Uplink quality 2 2

68 104 ext_out_dl_interf_c Downlink quality 4 4

69 105 ext_out_ul_interf_c Uplink quality 2 2

64 106 ext_out_distance_c Distance 6 6

6B 107 ext_out_pbgt_ho_c Better cell C 12

6C 108 ext_out_umbrella_ho_c Better cell C 12

6D 109 ext_out_forced_ho_c O and M intervention 7 7

6E 110 ext_out_dr_ho_c Directed retry D 13

6F 111 ext_out_tr_ho_c Response to MSC invocation 8 8

70 112 ext_out_idr_ho_c Directed retry D 13

71 113 ext_out_pre_empt_ho_c Response to MSC invocation 8 8

72 114 ext_out_rap_fld_drop_c Uplink strength 3 3

73 115 ext_out_low_distance_c Distance 6 6

74 116 ext_out_switch_crc_pool_c Switch circuit pool 32 50

75 117 ext_out_slow_moving_ms_c Better cell C 12





76 118 ext_out_det_slow_mov_ms_c Better cell C 12

77 119 ext_out_det_fast_mov_ms_c Better cell C 12

78 120 inter_dl_rxlev_c Downlink strength 5 5

79 121 inter_ul_rxlev_c Uplink strength 3 3

7A 122 inter_dl_rxqual_c Downlink quality 4 4

7B 123 inter_ul_rxqual_c Uplink quality 2 2

7C 124 inter_dl_interf_c Downlink quality 4 4

7D 125 inter_ul_interf_c Uplink quality 2 2

7E 126 inter_distance_c Distance 6 6

7F 127 inter_pbgt_ho_c Better cell C 12

80 128 inter_umbrella_ho_c Better cell C 12

81 129 inter_forced_ho_c O and M intervention 7 7

82 130 inter_dr_ho_c Directed retry D 13

83 131 inter_tr_ho_c Response to MSC invocation 8 8

84 132 inter_idr_ho_c Directed retry D 13

85 133 inter_pre_empt_ho_c Response to MSC invocation 8 8

86 134 inter_rap_fld_drop_c Uplink strength 3 3

87 135 inter_low_distance_c Distance 6 6

88 136 inter_ok_ci_ratio_c Downlink quality 4 4

89 137 inter_bad_ci_ratio_c Downlink quality 4 4

8A 138 inter_slow_moving_ms_c Better cell C 12

8B 139 inter_det_slow_mov_ms_c Better cell C 12

8C 140 intra_dl_interf_c Downlink quality 4 4

8D 141 intra_ul_interf_c Uplink quality 2 2

8E 142 intra_forced_ho_c O and M intervention 7 7

8F 143 intra_dl_rxqual_c Downlink quality 4 4



67 (135)



90 144 intra_ok_ci_ratio_c Downlink quality 4 4

91 145 intra_bad_ci_ratio_c Downlink quality 4 4

92 146 intra_pre_empt_ho_c Response to MSC invocation 8 8

93 147 intra_distance_c Distance 6 6

94 148 intra_low_distance_c Distance 6 6

95 149 intra_dr_ho_c Directed retry D 13

96 150 intra_direct_access Downlink strength 5 5

97 151 intra_gprs_ho_c Traffic F 15

98 152 intra_ho_to_amr_hr_c Better cell C 12

99 153 intra_ho_to_amr_fr_c Better cell C 12

9A 154 intra_inter_band_tch_c Traffic F 15

9B 155 intra_inter_band_sdc_c Traffic F 15

9C 156 inter_det_fast_mov_ms_c Better cell C 12

9D 157 inter_erfd_ho_c Better cell C 12

9E 158 inter_direct_access_c Downlink strength 5 5

9F 159 inter_bsc_trho_c Traffic F 15

A0 160 inter_dadlb_c Traffic F 15

A3 163 ext_out_erfd_ho_c Better cell C 12

A4 164 ext_out_bsc_trho_c Traffic F 15

A6 166 intra_inter_bts_type_tch_c Traffic F 15

A7 167 intra_inter_bts_type_sdc_c Traffic F 15

A8 168 intra_ho_due_to_hscsd_c Traffic F 15

A9 169 intra_inter_band_due_lev_c Downlink strength 5 5

BE 190 ext_out_isho_c Traffic load 28 40

BF 191 ext_out_inter_system_da_c Directed retry D 13

C0 192 ext_out_ibho_to_gsm_c Traffic load 28 40





C1 193 ext_out_ibho_to_utran_c Traffic load 28 40

12C 300 user_act_block_c O and M intervention 7 7

12D 301 netw_act_block_c O and M intervention 7 7

12E 302 bts_fail_block_c Equipment failure 20 32

12F 303 lapd_fail_block_c Equipment failure 20 32

130 304 abis_fail_block_c Equipment failure 20 32

131 305 abis_msg_corrup_to_bts_ c Equipment failure 20 32

132 306 ass_fail_msg_c Radio interface failure, rev to oldch

A 10

133 307 block_slave_c Equipment failure 20 32

134 308 ch_act_nack_c Radio interface failure 1 1

135 309 ch_act_nack_om_inter_c O and M intervention 7 7

136 310 ch_act_nack_equip_fail_c Equipment failure 20 32

137 311 ch_act_nack_encryp_alg_c Ciphering algorithm notsupported

40 64

138 312 ch_act_nack_rad_ch_alr_a_c No radio resource available 21 33

139 313 ch_act_nack_serv_not_ava_c Req transc/rate adaption unavail 30 48

13A 314 ch_act_fail_c Equipment failure 20 32

13B 315 conn_fail_c Radio interface failure 1 1

13C 316 conn_fail_rad_inf_fail_c Radio interface failure 1 1

13D 317 conn_fail_rad_link_fail_c Radio interface failure 1 1

13E 318 conn_fail_rem_trans_fail_c Equipment failure 20 32

13F 319 data_ind_corrup_c Radio interface message failure 0 0

140 320 err_ind_c Radio interface failure 1 1

141 321 estab_ind_fail_c Radio interface message failure 0 0

142 322 estab_conf_fail_c Radio interface message failure 0 0



69 (135)



143 323 ho_fail_c Radio interface failure, rev to oldch

A 10

144 324 ho_detect_fail_c Radio interface message failure 0 0

145 325 mode_mod_nack_c BSS not equipped 25 37

146 326 mode_mod_ack_fail_c Radio interface message failure 0 0

147 327 no_meas_result_c Radio interface failure 1 1

148 328 no_resp_from_copro_c Equipment failure 20 32

149 329 phy_cont_conf_fail_c Radio interface message failure 0 0

14A 330 rcs_alg_start_ack_fail_c Equipment failure 20 32

14B 331 rcs_alg_cl_ack_fail_c Equipment failure 20 32

14C 332 rc0_disco_ind_c Equipment failure 20 32

14D 333 rf_ch_rel_ack_fail_c Radio interface failure 1 1

14E 334 rel_ind_c Radio interface failure 1 1

14F 335 rel_ind_fail_c Radio interface message failure 0 0

150 336 signalling_error_c Radio interface failure 1 1

151 337 state_confligt_c Equipment failure 20 32

152 338 type_confligt_c Equipment failure 20 32

153 339 forced_rel_c Preemption 29 41

154 340 rej_phantom_res_c Radio interface message failure 0 0

155 341 overload_c CCCH overload 23 35

156 342 abi_switchover_c O and M intervention 7 7

157 343 sapi_3_fail_c Radio interface failure 1 1

158 344 paging_msg_fail_c Radio interface message failure 0 0

159 345 ch_required_fail_c Radio interface message failure 0 0

15A 346 mode_mod_nack_equip_fail_c Equipment failure 20 32

15B 347 mode_mod_nack_trc_rat_un_c Req transc/rate adaption unavail 30 48





15C 348 rrm_serv_req_nack_c No radio resource available 21 33

15D 349 ch_mode_mod_fail_c Radio interface failure 1 1

15E 350 ass_fail_c Radio interface message failure 0 0

15F 351 dr_fail_c No radio resource available 21 33

160 352 coprocess_fail_c Radio interface failure 1 1

161 353 err_rep_enc_alg_not_imp_c Ciphering algorithm notsupported

40 64

162 354 error_report_c Radio interface failure 1 1

163 355 ch_act_nack_ch_mode_err_c Req transc/rate adaption unavail 30 48

164 356 ch_act_nack_gen_ie_err_c Radio interface message failure 0 0

165 357 speech_version_unavail_c Radio interface failure, rev to oldch

A 10

166 358 ignored_double_rand_acc_c Radio interface message failure 0 0

167 359 rtsl_reconf_fail_c No radio resource available 21 33

168 360 ho_interrupted_c Equipment failure 20 32

169 361 downgrade_c Equipment failure 20 32

16A 362 ho_not_started_c Equipment failure 20 32

16B 363 conf_change_not_allowed_c Equipment failure 20 32

16C 364 conf_change_bts_fail_c BSS not equipped 25 37

16D 365 conf_change_ms_fail_c Radio interface failure 1 1

16E 366 hscsd_copro_fail_c Equipment failure 20 32

16F 367 sub_timer_c Equipment failure 20 32

170 368 forced_ho_block_c O and M intervention 7 7

171 369 upgrade_fail_c Equipment failure 20 32

172 370 estab_ind_corrupted_c Radio interface message failure 0 0

175 373 bsc_bsc_conflict_c Call control 9 9

190 400 timing_advance_c Distance 6 6



71 (135)



191 401 rrm_switch_crc_pool_c Switch circuit pool 32 50

192 402 rrm_speech_ver_unavail_c Requested speech versionunavailable

33 51

193 403 rrm_bts_not_supporting_c Req transc/rate adaption unavail 30 48

194 404 rrm_ms_not_supporting_c MS not equipped 26 38

195 405 rrm_invalid_cell_c Invalid cell 27 39

1F4 500 ho_not_allowed_c Call control 9 9

1F5 501 no_radio_res_avail_c No radio resource available 21 33

1F7 503 no_resp_from_coprocess_c Equipment failure 20 32

1F8 504 no_resp_to_radio_res_req_c Equipment failure 20 32

1F9 505 has_state_confligt_c Equipment failure 20 32

1FA 506 clear_cmd_not_received_c Radio interface message failure 0 0

1FB 507 ms_is_lost_c Radio interface message failure 0 0

1FC 508 no_resp_to_ho_cpl_msg_c Equipment failure 20 32

1FD 509 has_switchover_c O and M intervention 7 7

1FE 510 target_fail_c Call control 9 9

1FF 511 source_fail_c Call control 9 9

200 512 has_call_control_c Call control 9 9

201 513 adj_cell_id_err_c Invalid cell 27 39

258 600 aiv_hand_act_fail_c Equipment failure 20 32

259 601 aiv_ssp_c Call control 9 9

25A 602 sccp_conn_fail_c Call control 9 9

25B 603 sccp_conn_timeout_c Call control 9 9

25C 604 sccp_release_c Call control 9 9

25E 606 global_reset_c Call control 9 9

260 608 no_dtap_from_msc_c Call control 9 9





261 609 ho_denied_assign_c Call control 9 9

262 610 ho_denied_ciphering_c Call control 9 9

263 611 ho_denied_clear_c Call control 9 9

264 612 ho_denied_no_sccp_conn_c Call control 9 9

265 613 T7_expiry_c Call control 9 9

266 614 T10_expiry_c Equipment failure 20 32

267 615 aiv_crct_res_timeout_c Equipment failure 20 32

268 616 aiv_crct_conn_timeout_c Equipment failure 20 32

269 617 aiv_crct_disconn_timeout_c Equipment failure 20 32

26A 618 aiv_crct_rel_timeout_c Equipment failure 20 32

26B 619 aiv_timeout_c Equipment failure 20 32

26C 620 act_ctrl_timeout_c Equipment failure 20 32

26D 621 invalid_bssmap_msg_c Protocol error betw BSC andMSC

60 96

26E 622 unknown_a_pcm_c Req terrestrial resource unavail 22 34

26F 623 ho_denied_no_proper_crc_c Call control 9 9

270 624 ch_type_mismatch_c Invalid message contents 51 81

271 625 aiv_transc_or_rate_unava_c Req transc/rate adaption unavail 30 48

272 626 aiv_speech_version_unava_c Invalid message contents 51 81

273 627 aiv_pagin_refus_big_load_c Call control 9 9

274 628 aiv_conn_refresh_timeout_c Equipment failure 20 32

275 629 aiv_conn_refresh_failed_c Equipment failure 20 32

2BC 700 rc0_hand_act_fail_c Equipment failure 20 32

2BD 701 a_crct_alr_res_c Terr circuit already allocated 50 80

2BE 702 a_crct_conn_err_c Equipment failure 20 32

2BF 703 rc0_crct_conn_timeout_c Equipment failure 20 32



73 (135)



2C0 704 access_out_of_crct_tbl_c Equipment failure 20 32

2C1 705 a_crct_rel_err_c Equipment failure 20 32

2C2 706 rc0_transc_or_rate unava_c Req transc/rate adaption unavail 30 48

2C3 707 rc0_cip_type_mismatch_c Switch circuit pool 32 50

2C4 708 rc0_inv_msg_contents_c Invalid message contents 51 81

2C5 709 rc0_req_speech_ver_unava_c Requested speech versionunavailable

33 51

2C6 710 rc0_hunting_queue_full_c Traffic load 28 40

2C7 711 rc0_a_crct_congestion_c Equipment failure 20 32

2C8 712 rc0_a_search_error_c Traffic load 28 40

2C9 713 rc0_crct_pool_mismatch_c Equipment failure 20 32

2CA 714 rc0_rej_due_eme_call_c Traffic load 28 40

2CB 715 rc0_ilc_file_error_c Equipment failure 20 32

320 800 a_tsl_user_mismatch_c Equipment failure 20 32

321 801 sc7_crct_res_timeout_c Equipment failure 20 32

322 802 sc7_crct_conn_timeout_c Equipment failure 20 32

323 803 sc7_crct_disconn_timeout_c Equipment failure 20 32

324 804 sc7_crct_rel_timeout_c Equipment failure 20 32

325 805 a_tsl_blocked_c Req terrestrial resource unavail 22 34

326 806 a_tsl_status_unknown_c Req terrestrial resource unavail 22 34

327 807 lsi_access_fail_c Equipment failure 20 32

328 808 scc_access_fail_c Equipment failure 20 32

329 809 undef_tsl_in_lsi_c Req terrestrial resource unavail 22 34

32A 810 crct_equipment_fail_c Equipment failure 20 32

32B 811 reset_crct_c Response to MSC invocation 8 8

32D 813 sc7_ssp_c Call control 9 9





32F 815 a_pcm_fault_c Equipment failure 20 32

331 817 a_crct_removed_c O and M intervention 7 7

333 819 a_et_state_change_c O and M intervention 7 7

384 900 m_radio_if_mess_fail_c Radio interface message failure 0 0

385 901 m_radio_if_fail_c Radio interface failure 1 1

386 902 m_uplink_quality_c Uplink quality 2 2

387 903 m_uplink_strength_c Uplink strength 3 3

388 904 m_downlink_quality_c Downlink quality 4 4

389 905 m_downlink_strength_c Downlink strength 5 5

38A 906 m_distance_c Distance 6 6

38B 907 m_o_and_m_inter_c O and M intervention 7 7

38C 908 m_resp_to_msc_invoc_c Response to MSC invocation 8 8

38D 909 m_call_control_c Call control 9 9

38E 910 m_r_if_f_rev_to_old_c Radio interface failure, rev to oldch

A 10

38F 911 m_handover_succ_c Handover successful B 11

390 912 m_better_cell_c Better cell C 12

391 913 m_directed_retry_c Directed retry D 13

392 914 m_equipment_fail_c Equipment failure 20 32

393 915 m_no_radio_res_avail_c No radio resource available 21 33

394 916 m_req_terr_res_unava_c Req terrestrial resource unavail 22 34

395 917 m_cch_overload_c CCCH overload 23 35

396 918 m_processor_overload_c Processor overload 24 36

397 919 m_bss_not_equipped_c BSS not equipped 25 37

398 920 m_ms_not_eqipped_c MS not equipped 26 38

399 921 m_tr_cod_rat_ad_unav_c Req transc/rate adaption unavail 30 48



75 (135)



39A 922 m_ciph_alg_not_supp_c Ciphering algorithm notsupported

40 64

39B 923 m_terr_chan_alr_allc_c Terr circuit already allocated 50 80

39C 924 m_prot_err_b_bsc_msc_c Protocol error betw BSC andMSC

60 96

39E 926 m_invalid_cell_c Invalid cell 27 39

39F 927 m_invalid_msg_cont_c Invalid message contents 51 81

3A0 928 m_ie_or_field_missing_c Information elem or field missing 52 82

3A1 929 m_incorrect_value_c Incorrect value 53 83

3A2 930 m_unknown_msg_type_c Unknown message type 54 84

3A3 931 m_unknown_ie_c Unknown information element 55 85

3A5 933 m_cip_type_mismatch_c Circuit pool mismatch 31 49

3A6 934 m_switch_circuit_pool_c Switch circuit pool 32 50

3A7 935 m_speech_version_unavail_c Requested speech versionunavail

33 51

3A8 936 m_pre_empt_c Preemption 29 41

3A9 937 m_traffic_c Traffic F 15

6.2 BSSMAP causes mapped to DX causes

The following table shows which DX causes trigger a particular BSSMAP cause.The BSSMAP causes and their hexadecimal values are listed in the first twocolumns. The third column lists the cause fields of the DX causes which bringabout a BSSMAP cause on the A interface.

BSSMAP cause HEX DX cause DEC

RADIO INTERFACE MESSAGEFAILURE

0x00 data_ind_corrup_c 319

estab_ind_fail_c 321

estab_conf_fail_c 322





ho_detect_fail_c 324

mode_mod_ack_fail_c 326

phy_cont_conf_fail_c 329

rel_ind_fail_c 335

rej_phanton_res_c 340

paging_msg_fail_c 344

ch_required_fail_c 345

ass_fail_c 350

ch_act_nack_gen_err_c 356

ignored_double_rand_acc_c 358

estab_ind_corrupted_c 370

clear_cmd_not_received_c 506

ms_is_lost_c 507

m_radio_if_mess_fail_c 900

RADIO INTERFACE FAILURE 0x01 ch_act_nack_c 308

conn_fail_c 315

conn_fail_rad_inf_fail_c 316

conn_fail_rad_link_fail_c 317

err_ind_c 320

no_meas_result_c 327

rf_ch_rel_ack_fail_c 333

rel_ind_c 334

signalling_error_c 336

sapi_3_fail_c 343

ch_mode_mod_fail_c 349

coprocess_fail_c 352



77 (135)



error_report_c 354

conf_change_ms_fail_c 365

m_radio_if_fail_c 901

UPLINK QUALITY 0x02 ext_out_ul_quality_c 80

ext_out_ul_rxqual_c 103

ext_out_ul_interf_c 105

inter_ul_rxqual_c 123

inter_ul_interf_c 125

intra_ul_interf_c 141

m_uplink_quality_c 902

UPLINK STRENGTH 0x03 ext_in_ul_strength_c 81

ext_out_ul_rxlev_c 101

ext_out_rap_fld_drop_c 114

inter_ul_rxlev_c 121

inter_rap_fld_drop_c 134

m_uplink_strength_c 903

DOWNLINK QUALITY 0x04 ext_in_dl_quality_c 82

ext_out_dl_rxqual_c 102

ext_out_dl_interf_c 104

inter_dl_rxqual_c 122

inter_dl_interf_c 124

inter_ok_ci_ratio_c 136

inter_bad_ci_ratio_c 137

intra_dl_interf_c 140

intra_dl_rxqual_c 143

intra_ok_ci_ratio_c 144





intra_bad_ci_ratio_c 145

m_downlink_quality_c 904

DOWNLINK STRENGTH 0x05 ext_in_dl_strength_c 83

ext_out_dl_rxlev_c 100

inter_dl_rxlev_c 120

intra_direct_access_c 150

inter_direct_access_c 158

intra_inter_band_due_lev_c 169

m_downlink_strength_c 905

DISTANCE 0x06 ext_in_distance_c 84

ext_out_distance_c 106

ext_out_low_distance_c 115

inter_distance_c 126

inter_low_distance_c 135

intra_distance_c 147

intra_low_distance_c 148

timing_advance_c 400

m_distance_c 906

O AND M INTERVENTION 0x07 ext_in_o_and_m_inter_c 85

ext_out_forced_ho_c 109

inter_forced_ho_c 129

intra_forced_ho_c 142

user_act_block_c 300

netw_acct_block_c 301

ch_act_nack_om_inter_c 309

abi_switchover_c 342



79 (135)



forced_ho_block_c 368

has_switchover_c 509

a_crct_removed_c 817

a_et_state_change_c 819

m_o_and_m_inter_c 907

RESPONSE TO MSC INVOCATION 0x08 ext_in_resp_to_msc_invoc_c 86

ext_out_tr_ho_c 111

ext_out_pre_empt_ho_c 113

inter_tr_ho_c 131

inter_pre_empt_ho_c 133

intra_pre_empt_ho_c 146

reset_crct_c 811

m_resp_to_msc_invoc_c 908

CALL CONTROL 0x09 bsc_bsc_conflict_c 373

ho_not_allowed_c 500

target_fail_c 510

source_fail_c 511

has_call_control_c 512

aiv_ssp_c 601

sccp_conn_fail_c 602

sccp_conn_timeout_c 603

sccp_release_c 604

global_reset_c 606

no_dtap_from_msc_c 608

ho_denied_assign_c 609

ho_denied_ciphering_c 610





ho_denied_clear_c 611

ho_denied_no_sccp_conn_c 612

T7_expiry_c 613

ho_denied_no_proper_crc_c 623

aiv_pagin_refus_big_load_c 627

sc7_ssp_c 813

m_call_control_c 909

RADIO INTERFACE FAILURE,REVERSION TO OLD CHANNEL

0x0A ass_fail_msg_c 306

ho_fail_c 323

m_r_if_f_rev_to_old_c 910

HANDOVER SUCCESSFULL 0x0B m_handover_succ_c 911

BETTER CELL 0x0C ext_in_better_cell_c 87

ext_out_pbgt_ho_c 107

ext_out_umbrella_ho_c 108

ext_out_slow_moving_ms_c 117

ext_out_det_slow_mov_ms_c 118

ext_out_det_fast_mov_ms_c 119

inter_pbgt_ho_c 127

inter_umbrella_ho_c 128

inter_slow_moving_ms_c 138

inter_det_slow_mov_ms_c 139

intra_ho_to_amr_hr_c 152

intra_ho_to_amr_fr_c 153

inter_erfd_ho_c 157

ext_out_erfd_ho_c 163



81 (135)



m_better_cell_c 912

DIRECTED RETRY 0x0D ext_in_directed_retry_c 88

ext_out_dr_ho_c 110

ext_out_idr_ho_c 112

inter_dr_ho_c 130

inter_idr_ho_c 132

intra_dr_ho_c 149

ext_out_inter_system_da_c 191

m_directed_retry_c 913

TRAFFIC 0x0F ext_in_bsc_trho_c 92

intra_gprs_ho_c 151

intra_inter_band_tch_c 154

intra_inter_band_sdc_c 155

inter_bsc_trho_c 159

inter_dadlb_c 160

ext_out_bsc_trho_c 164

intra_inter_bts_type_tch_c 166

intra_inter_bts_type_sdc_c 167

intra_ho_due_to_hscsd_c 168

m_traffic_c 937

EQUIPMENT FAILURE 0x20 bts_fail_block_c 302

lapd_fail_block_c 303

abis_fail_block_c 304

abis_msg_corrup_to_bts_c 305

block_slave_c 307

ch_act_nack_equip_fail_c 310





ch_act_fail_c 314

conn_fail_rem_trans_fail_c 318

no_resp_from_copro_c 328

rcs_alg_start_ack_fail_c 330

rcs_alg_cl_ack_fail_c 331

rc0_disco_ind_c 332

state_confligt_c 337

type_confligt_c 338

mode_mod_nack_equip_fail_c 346

ho_interrupted_c 360

downgrade_c 361

ho_no_started_c 362

conf_change_not_allowed_c 363

hscsd_copro_fail_c 366

sub_timer_c 367

upgrade_fail_c 369

no_resp_from_coprocess_c 503

no_resp_to_radio_res_req_c 504

has_state_confligt_c 505

no_resp_to_ho_cpl_msg_c 508

aiv_hand_act_fail_c 600

T10_expiry_c 614

aiv_crct_res_timeout_c 615

aiv_crct_conn_timeout_c 616

aiv_crct_disconn_timeout_c 617

aiv_crct_rel_timeout_c 618



83 (135)



aiv_timeout_c 619

act_ctrl_timeout_c 620

aiv_conn_refresh_timeout_c 628

aiv_conn_refresh_failed_c 629

rc0_hand_act_fail_c 700

a_crct_conn_err_c 702

rc0_crct_conn_timeout_c 703

access_out_of_crct_tbl_c 704

a_crct_rel_err_c 705

rc0_a_crct_congestion_c 711

rc0_crct_pool_mismatch_c 713

rc0_ilc_file_error_c 715

a_tsl_user_mismatch_c 800

sc7_crct_res_timeout_c 801

sc7_crct_conn_timeout_c 802

sc7_crct_disconn_timeout_c 803

sc7_crct_rel_timeout_c 804

lsi_access_fail_c 807

scc_access_fail_c 808

crct_equipment_fail_c 810

a_pcm_fault_c 815

m_equipment_fail_c 914

NO RADIO RESOURCE AVAILABLE 0x21 ch_act_nack_rad_ch_alr_a_c 312

rrm_serv_req_nack_c 348

dr_fail_c 351

rtsl_reconf_fail_c 359





no_radio_res_avail_c 501

m_no_radio_res_avail_c 915

REQUESTED TERRESTRIALRESOURCE UNAVAILABLE

0x22 unknown_a_pcm_c 622

a_tsl_blocked_c 805

a_tsl_status_unknown_c 806

undef_tsl_in_lsi_c 809

m_req_terr_res_unava_c 916

CCCH OVERLOAD 0x23 overload_c 341

m_cch_overload_c 917

PROCESSOR OVERLOAD 0x24 m_processor_overload_c 918

BSS NOT EQUIPPED 0x25 mode_mod_nack_c 325

conf_change_bts_fail_c 364

m_bss_not_equipped_c 919

MS NOT EQUIPPED 0x26 rrm_ms_not_supporting_c 404

m_ms_not_equipped_c 920

INVALID CELL 0x27 rrm_invalid_cell_c 405

m_invalid_cell_c 926

TRAFFIC LOAD 0x28 ext_out_isho_c 190

ext_out_ibho_to_gsm_c 192

ext_out_ibho_to_utran_c 193

rc0_hunting_queue_full_c 710

rc0_a_search_error_c 712

rc0_rej_due_eme_call_c 714

PREEMPTION 0x29 ext_in_pre_empt_c 91

forced_rel_c 339



85 (135)



m_pre_empt_c 936

REQUESTED TRANSCODING/RATEADAPTION UNAVAILABLE

0x30 ch_act_nack_serv_not_ava_c 313

mode_mod_nack_trc_rat_un_c 347

ch_act_nack_ch_mode_err_c 355

rrm_bts_not_supporting_c 403

aiv_transc_or_rate_unava_c 625

rc0_transc_or_rate_unava_c 706

m_tr_cod_rat_ad_unav_c 921

CIRCUIT POOL MISMATCH 0x31 m_cip_type_mismatch_c 933

SWITCH CIRCUIT POOL 0x32 ext_in_switch_crc_pool_c 90

ext_out_switch_crc_pool_c 116

rrm_switch_src_pool_c 401

rc0_cip_type_mismatch_c 707

m_switch_crc_pool_c 934

REQUESTED SPEECH VERSIONUNAVAILABLE

0x33 rrm_speech_ver_unavail_c 402

rc0_req_speech_ver_unava_c 709

m_speech_version_unavail_c 935

CIPHERING ALGORITHM NOTSUPPORTED

0x40 ch_act_nack_encryp_alg_c 311

err_rep_enc_alg_not_imp_c 353

m_ciph_alg_not_supp_c 922

TERRESTRIAL CIRCUIT ALREADYALLOCATED

0x50 a_crct_alr_res_c 701

m_terr_chan_alr_allc_c 923

INVALID MESSAGE CONTENTS 0x51 ch_type_mismatch_c 624

aiv_speech_version_unava_c 626





rc0_inv_msg_contents_c 708

m_invalid_msg_cont_c 927

INFORMATION ELEMENT OF FIELDMISSING

0x52 m_ie_or_field_missing_c 928

INCORRECT VALUE 0x53 m_incorrect_value_c 929

UNKNOWN MESSAGE TYPE 0x54 m_unkown_msg_type_c 930

UNKNOWN INFORMATION ELEMENT 0x55 m_unknown_ie_c 931

PROTOCOL ERROR BETWEEN BSCAND MSC

0x60 invalid_bssmap_msg_c 621

m_prot_err_b_bsc_msc_c 924

6.3 Traffic measurement counters mapped to DXcauses

The following table lists the traffic measurement counters that are incrementeddue to DX causes. The first two columns list the counter name and number. Thelast two columns indicate the cause fields of the DX causes and their decimalvalues.

Counter description Counter DX cause DEC

Number of SDCCH transaction failures dueto BSS failure

1002 This is a sum of the counters 1033, 1034,1035, 1036

Number of SDCCH transaction failures dueto a radio failure (incremented only inphases 1-8)

1003 ass_fail_msg_c 306

1003 conn_fail_c 315

1003 conn_fail_rad_inf_fail_c 316

1003 conn_fail_rad_link_fail_c 317

1003 err_ind_c 320

1003 ho_fail_c 323



87 (135)



1003 ho_detect_fail_c 324

1003 ch_mode_mod_fail_c 349

1003 ass_fail_c 350

1003 error_report_c 354

1003 conf_change_ms_fail_c 365

1003 timing_advance_c 400

1003 no_resp_from_coprocess_c 503

1003 ms_is_lost_c 507

1003 target_fail_c 510

1003 source_fail_c 511

Number of SDCCH transaction failures dueto a radio failure of the old channel duringand SDCCH-SDCCH or SDCCH-TCHhandover (incremented only in phases 9�11)





1004 err_ind_c 320

1004 ho_fail_c 323


1004 ass_fail_c 350










Number of SDCCH transaction failures dueto a radio failure of the new channel duringa SDCCH handover (incremented only inphases 12-14)





1005 err_ind_c 320

1005 ho_fail_c 323



1005 ass_fail_c 350







Number of radio TCH transactions endeddue to BSS problems

1012 This is a sum of the counters 1045, 1046,1047, 1051

Number of radio TCH transactions endeddue to a radio failure (incremented only inphases 1-8, 15)





1013 err_ind_c 320

1013 ho_fail_c 323




89 (135)




1013 ass_fail_c 350








Number of radio TCH transactions endeddue to a radio failure of the old channelduring a HO on a TCH (incremented only inphases 9-11)





1014 err_ind_c 320

1014 ho_fail_c 323


1014 ass_fail_c 350






Number of radio TCH transactions endeddue to a radio failure of the new channelduring a HO on a TCH (incremented only inphases 12-14)









1015 err_ind_c 320

1015 ho_fail_c 323



1015 ass_fail_c 350







Number of SDCCH transaction failures dueto an activation failure

1027 This is a sum of the counters 1072, 1074

Number of radio TCH transactions endeddue to an activation failure

1028 This is a sum of the counters 1081, 1083

Number of radio TCH transactions endeddue to a transcoder failure (incrementedonly in phases 1-8, 15)

1029 conn_fail_rem_trans_fail_c 318

Number of radio TCH transactions endeddue to a transcoder failure of the oldchannel during a HO on a TCH(incremented only in phases 9-11)


Number of radio TCH transactions endeddue to a transcoder failure of the newchannel during a HO on a TCH(incremented only in phases 12-14)


Number of SDCCH transaction failures dueto Abis interface failure

1033 This is a sum of the counters 1075, 1076,1077



91 (135)



Number of SDCCH transaction failures dueto A interface failure


Number of SDCCH transaction failures dueto a LAPD failure

1035 lapd_fail_block_c 303

Number of SDCCH transaction failures dueto a BTS failure

1036 bts_fail_block_c 302

Number of SDCCH transaction failures dueto user actions

1037 user_act_block_c 300

Number of SDCCH transaction failures dueto radio network reconfiguration actions

1039 netw_act_block_c 301

Number of TCH transaction failures due toan Abis interface failure


Number of TCH transaction failures due toa LAPD failure


Number of TCH transaction failures due toa BTS failure


Number of TCH transaction failures due touser actions

1048 user_act_block_c 300

Number of TCH transaction failures due toradio network reconfiguration actions

1050 netw_act_block_c 301

Number of TCH transaction failures due toan A interface failure


Number of SDCCH transaction failures dueto an activation failure during call(incremented only in phases 1-8)

1072 ch_act_nack_c 308

1072 ch_act_nack_om_inter_c 309

1072 ch_act_nack_equip_fail_c 310

1072 ch_act_nack_encryp_alg_c 311

1072 ch_act_nack_rad_ch_alr_a_c 312

1072 ch_act_nack_serv_not_ava_c 313

1072 mode_mod_nack_c 325

1072 mode_mod_nack_equip_fail_c 346





1072 mode_mod_nack_trc_rat_un_c 347

1072 err_rep_enc_alg_not_imp_c 353

1072 ch_act_nack_ch_mode_err_c 355

1072 ch_act_nack_gen_ie_err_c 356

1072 speech_version_unavail_c 357

1072 conf_change_bts_fail_c 364

1072 rrm_speech_ver_unavail_c 402

Number of SDCCH transaction failures dueto an activation failure of the new channelduring an SDCCH handover (incrementedonly in phases 12-14)
















Number of SDCCH transaction failures dueto an Abis interface failure during call(incremented only in phases 1-8)

1075 abis_fail_block_c 304



93 (135)



1075 abis_msg_corrup_to_bts_c 305

1075 block_slave_c 307

1075 ch_act_fail_c 314

1075 data_ind_corrup_c 319

1075 estab_ind_fail_c 321

1075 estab_conf_fail_c 322

1075 mode_mod_ack_fail_c 326

1075 no_meas_result_c 327

1075 no_resp_from_copro_c 328

1075 phy_cont_conf_fail_c 329

1075 rcs_alg_start_ack_fail_c 330

1075 rcs_alg_cl_ack_fail_c 331

1075 rf_ch_rel_ack_fail_c 333

1075 rel_ind_fail_c 335

1075 signalling_error_c 336

1075 sapi_3_fail_c 343

1075 sub_timer_c 367

1075 estab_ind_corrupted_c 370

1075 has_state_confligt_c 505

Number of SDCCH transaction failures dueto an Abis interface failure on the oldchannel during SDCCH-SDCCH orSDCCH-TCH handover (incremented onlyin phases 9-11)
























Number of SDCCH transaction failures dueto an Abis interface failure on the newchannel during SDCCH-SDCCH orSDCCH-TCH handover (incremented onlyin phases 12-14)













95 (135)













Number of SDCCH transaction failures dueto an A interface failure during call attempt(incremented only in phases 1-8)

1078 rc0_disco_ind_c 332

1078 rrm_switch_crc_pool_c 401

1078 clear_cmd_not_received_c 506

1078 no_resp_to_ho_cpl_msg_c 508

1078 aiv_hand_act_fail_c 600

1078 aiv_ssp_c 601

1078 sccp_conn_fail_c 602

1078 sccp_conn_timeout_c 603

1078 sccp_release_c 604

1078 global_reset_c 606

1078 no_dtap_from_msc_c 608

1078 ho_denied_assign_c 609

1078 ho_denied_ciphering_c 610

1078 ho_denied_clear_c 611

1078 ho_denied_no_sccp_conn_c 612





1078 T7_expiry_c 613

1078 T10_expiry_c 614

1078 aiv_crct_res_timeout_c 615

1078 aiv_crct_conn_timeout_c 616

1078 aiv_crct_disconn_timeout_c 617

1078 aiv_crct_rel_timeout_c 618

1078 aiv_timeout_c 619

1078 act_ctrl_timeout_c 620

1078 invalid_bssmap_msg_c 621

1078 unknown_a_pcm_c 622

1078 ho_denied_no_proper_crc_c 623

1078 ch_type_mismatch_c 624

1078 aiv_transc_or_rate_unava_c 625

1078 aiv_speech_version_unava_c 626

1078 aiv_conn_refresh_timeout_c 628

1078 aiv_conn_refresh_failed_c 629

1078 rc0_hand_act_fail_c 700

1078 a_crct_alr_res_c 701

1078 a_crct_conn_err_c 702

1078 rc0_crct_conn_timeout_c 703

1078 access_out_of_crct_tbl_c 704

1078 a_crct_rel_err_c 705

1078 rc0_transc_or_rate_unava_c 706

1078 rc0_cip_type_mismatch_c 707

1078 rc0_inv_msg_contents_c 708

1078 rc0_req_speech_ver_unava_c 709



97 (135)



1078 rc0_hunting_queue_full_c 710

1078 rc0_a_crct_congestion_c 711

1078 rc0_a_search_error_c 712

1078 rc0_crct_pool_mismatch_c 713

1078 rc0_rej_due_eme_call_c 714

1078 rc0_ilc_file_error_c 715

1078 a_tsl_user_mismatch_c 800

1078 sc7_crct_res_timeout_c 801

1078 sc7_crct_conn_timeout_c 802

1078 sc7_crct_disconn_timeout_c 803

1078 sc7_crct_rel_timeout_c 804

1078 a_tsl_blocked_c 805

1078 a_tsl_status_unknown_c 806

1078 lsi_access_fail_c 807

1078 scc_access_fail_c 808

1078 undef_tsl_in_lsi_c 809

1078 crct_equipment_fail_c 810

1078 reset_crct_c 811

1078 sc7_ssp_c 813

1078 a_pcm_fault_c 815

1078 a_crct_removed_c 817

1078 a_et_state_change_c 819

1078 m_radio_if_mess_fail_c 900

1078 m_radio_if_fail_c 901

1078 m_uplink_quality_c 902

1078 m_uplink_strength_c 903





1078 m_downlink_quality_c 904

1078 m_downlink_strength_c 905

1078 m_distance_c 906

1078 m_o_and_m_inter_c 907

1078 m_resp_to_msc_invoc_c 908

1078 m_r_if_f_rev_to_old_c 910

1078 m_handover_succ_c 911

1078 m_better_cell_c 912

1078 m_directed_retry_c 913

1078 m_equpment_fail_c 914

1078 m_no_radio_res_avail_c 915

1078 m_req_terr_res_unava_c 916

1078 m_cch_overload_c 917

1078 m_processor_overload_c 918

1078 m_bss_not_equipped_c 919

1078 m_ms_not_equipped_c 920

1078 m_tr_cod_rat_ad_unav_c 921

1078 m_ciph_alg_not_supp_c 922

1078 m_terr_chan_alr_allc_c 923

1078 m_prot_err_b_bsc_msc_c 924

1078 m_unexpected_c 925

1078 m_invalid_cell_c 926

1078 m_invalid_msg_cont_c 927

1078 m_ie_or_field_missing_c 928

1078 m_incorrect_value_c 929

1078 m_unknown_msg_type_c 930



99 (135)



1078 m_unknown_ie 931

1078 m_transc_or_rate_unavail_c 932

1078 m_cip_type_mismatch_c 933

1078 m_switch_crc_pool_c 934

1078 m_speech_version_unavail_c 935

1078 m_pre_empt_c 936

1078 m_traffic_c 937

Number of SDCCH transaction failures dueto an A interface failure on the old channelduring SDCCH-SDCCH or SDCCH-TCHhandover (incremented only in phases 9-11)






1079 aiv_ssp_c 601











1079 T10_expiry_c 614

































101 (135)



















1079 sc7_ssp_c 813

















1079 m_call_control_c 909



















1079 m_ie_or_field_missing 928

1079 m_incorrect_value 929

1079 m_unknown_msg_type 930

1079 m_unknown_ie 931



103 (135)









Number of SDCCH transaction failures dueto an A interface failure on the new channelduring and SDCCH handover (incrementedonly in phases 12-14)






1080 aiv_ssp_c 601











1080 T10_expiry_c 614


































105 (135)


















1080 sc7_ssp_c 813







































1080 m_unknown_ie_c 931




107 (135)








Number of radio TCH transactions endeddue to an activation failure during callattempt (incremented only in phases 1-8)
















Number of radio TCH transactions endeddue to an activation failure on the newchannel during an SDCCH-TCH or TCH-TCH handover (incremented only in phases12-14)




















Number of TCH transaction failures due toan Abis interface failure during call(incremented only in phases 1-8, 15)
















109 (135)










Number of TCH transaction failures due toan Abis interface failure on the old channelduring a TCH handover (incremented onlyin phases 9-11)
























Number of TCH transaction failures due toan Abis interface failure on the new channelduring a TCH handover (incremented onlyin phases 12-14)





















Number of TCH transaction failures due toan A interface failure during call(incremented only in phases 1-8, 15)




111 (135)







1087 aiv_ssp_c 601











1087 T10_expiry_c 614











































113 (135)









1087 sc7_ssp_c 813













































Number of TCH transaction failures on theold channel due to an A interface failureduring handover attempt (incremented onlyin phases 9-11)






115 (135)





1088 aiv_ssp_c 601











1088 T10_expiry_c 614













































117 (135)







1088 sc7_ssp_c 813














































Number of TCH transaction failures on thenew channel due to an A interface failureduring handover attempt (incremented onlyin phases 12-14)







119 (135)




1089 aiv_ssp_c 601











1089 T10_expiry_c 614














































121 (135)






1089 sc7_ssp_c 813














































Number of TCH releases due to radiofailures in call set-up phase before connectacknowledgement (incremented only inphases 2, 3, 5, 8�14)





1139 err_ind_c 320



123 (135)



1139 ho_fail_c 323



1139 ass_fail_c 350








Number of the TCH releases due to BSSfailures in call set-up phase before connectacknowledgement (incremented only inphases 2, 3, 5, 8�14)
































1140 aiv_ssp_c 601











1140 T10_expiry_c 614



125 (135)



















1140 sc7_ssp_c 813












127 (135)










1140 m_equipment_fail_c 914






1140 m_ms_not_eqipped_c 920






















Number of TCH releases due to radiofailures in call set-up phase (incrementedonly in phases 2, 3)





1205 err_ind_c 320

1205 ho_fail_c 323



1205 ass_fail_c 350








Number of TCH releases due to radiofailures (incremented only in phases 12-14)






129 (135)




1206 err_ind_c 320

1206 ho_fail_c 323



1206 ass_fail_c 350








Number of the TCH releases due to BSSfailures (incremented only in phases 12-14)
































1207 aiv_ssp_c 601













131 (135)



1207 T10_expiry_c 614















































1207 sc7_ssp_c 813











133 (135)











1207 m_equipment_fail_c 914






1207 m_ms_not_eqipped_c 920






















Number of TCHs releases due to BSC-BSCconflict (incremented only in phases 1-8 or15)

1217 bsc_bsc_conflict_c 373

Number of TCHs releases due to BSC-BSCconflict (incremented only in phases 12 �14)

1218 bsc_bsc_conflict_c 373



135 (135)


Nokia DX Clear Codes

Documents

Transcript of Nokia DX Clear Codes