basic ueh exception

Title A UEH Exception Decriptions for Troubleshooting in Live Network

Doc. Nr.

Revision PA1

Date 4/8/2010

Abstract

Revision History

PA1 ETCHLUO

Open Issues

References Ref[1] UEH Exception for NTC Purpose_PA3

Ref[2] UEH_EXCEPTION Introduction

This workbook contains the description of UEH_EXCEPTION Codes for troubleshooting purpose in the live network. It opens a way to investigate the root cause of the problem in depth step by step.

C:\elxmm\2009Feb21\ueh_

A UEH Exception Decriptions for Troubleshooting in Live Network

PA1

First draft

This workbook contains the description of UEH_EXCEPTION Codes for troubleshooting purpose in the live network. It opens a way to investigate the root cause of the problem in depth step by step.



Codes rbId

171 -

529 -

223 -

521 -

54 2

222 -

141 -

552 -

220 -

221 -

12 -

200 -

500 -

533 -

142 -

327 -

318 -

54 -

276 -

545 -

409 -

201 -

351 -

311 -

523 -

407 -

54 3

225 -

800 -

563 -

80 -

54 16

350 -

331 -

283 -

940 -

607 -

509 -

6 -

310 -

110 -

400 -

554 -

501 -

557 -

352 -

921 -

757 -

120 -

140 -

504 -

850 -

711 - 359 -

210 -

54 4

512 -

365 -

10 -

122 -

601 3

660 - 312 - 281 - 404 -

650 -

405 -

11 -

57 -

451 - 180/181/182/183/184 - 310/311/312/327 - 54 - 521/523/552 - 58 - 800 - 54 -

181 - 350/351 - 220/221/222 - 171 - 529 -

EC_String

Received signal admissionRej on rnhIfCellControlP

TIMER inactivityDchTimerId has expired

Received signal decreaseResourceReq on RnhIfCellEventP

TIMER rrcSetuptimerId has expired

Received signal spProcessingFailure on DcsIfEventP

Received signal cellLockedInd on RnhIfCellEventP

Received signal ranapDisconnectInd on UehRanapProcP

TIMER T_CH_SWITCH_1 has expired (DCH<->FACH)

Received signal eulLockedInd on RnhIfCellEventP

Received signal hsDschLockedInd on RnhIfCellEventP

Received signal faultyTrBrInd on DrhIfTrBrP

Received signal cellParamsRC2CharRej on RnhIfCellInfoP

TIMER T_RABEST_1 has expired waiting for RRC Radio Bearer Setup Response

TIMER rcsHsRlLostTimerId has expired

Received signal ranapInitialUeRej on UehRanapProcP

Received signal NBAP RADIO LINK FAILURE INDICATION

Received signal NBAP COMMON MEASUREMENT INITIATION FAILURE


Security Check failed for Cell or Ura update message

TIMER esvRrcTimerId has expired

Received signal RRC Physical Channel Reconfiguration Failure

Received signal cellParamsRej on RnhIfCellInfoP

Received signal RNSAP RADIO LINK ADDITION FAILURE

Received signal NBAP RADIO LINK ADDITION FAILURE

TIMER timer_RRC_ASU has expired

Received signal RRC CellUpdate with Failure Cause


Received signal capabilityChangeInd on RnhIfCellEventP

LOGICAL ERROR IN RANAP RAB ASSIGNMENT REQUEST

TIMER rcsAllRlLostTimerId has expired

Received signal rrcConnRejectInd on RnhIfRrcP


Received signal RNSAP RADIO LINK SETUP FAILURE

Received an NBAP Message Reject

Failed to build Ranap Relocation Required

INTERNAL STATE INCOMPATIBLE WITH REQUESTED OPERATION

Internal Subsystem Communication barred (Uu)

TIMER tcpmPcr has expired

Received signal connNotOk on DrhIfDcRhDcP

Received signal NBAP RADIO LINK SETUP FAILURE

Received signal messageReject on UehNbapDedicatedP

Received signal RRC Radio Bearer Setup Failure

TIMER T_CH_SWITCH_3 has expired (DCH->DCH)

TIMER T_RABEST_1 has expired waiting for RRC Radio Bearer Reconfiguration Complet

TIMER UehRrcCellChangeHsTimer

Received signal RNSAP RADIO LINK RECONFIGURATION FAILURE

UNEXPECTED UL RRC DCCH MESSAGE TYPE

LOGICAL ERROR IN RRC RADIO BEARER RECONF COMPLETE

Received signal messageReject on UehRnsapDedicatedSrncP

Received signal messageReject on UehRanapProcP

TIMER T_RABREL_1 has expired waiting for RRC Radio Bearer Release Response

LOGICAL ERROR FAILED TO DECODE RRC MESSAGE

LOGICAL ERROR IN RNSAP RADIO LINK READY INDReceived signal RNSAP RADIO LINK FAILURE INDICATION

Received signal asynch_forcedReleaseInd on UehUeCtxtAsynchIndicP


TIMER cellChangeTimerId has expired

Received a RNSAP Message Reject

Received signal setupLocalIpUdpTrBrRej on DrhIfTrBrP

Received signal sccpConnectionDisconnectionInd on UehRnsapDedicatedSrncP

Internal Subsystem Communication barred (UEH)

LOGICAL ERROR IN NBAP RL FAILURE INDReceived signal NBAP RADIO LINK RECONFIGURATION FAILUREUnhandled GPEH Service Class in call to incrementGpehCounterReceived signal RRC Measurement Control Failure

LOGICAL ERROR IN NBAP RADIO LINK SETUP RESPONSE

Received signal RRC Radio Bearer Reconfiguration Failure

Received signal setupTrBrRej on DrhIfTrBrP

Received signal interRATHandoverExInd on DcsIfEventP with invalid targetId

Received signal RANAP Relocation Preparation Failure

Causes Impact

Performance degrade

No impact

Call drop

Performance degrade

Call drop

Locking cell caused many affected UeContexts release. Call drop

Admisson rejected due to following limitation: 1 Congestion2 AseUl - Admission limit for UL ASE exceeded3 AseDl - Admission limit for DL ASE exceeded4 DlPwr5 DlCode6 SF87 SF168 SF329 CompModeLimit10 CellDeactivated11 RoutingFailure12 LoadSharing13 UniSaalCongestion14 RbsUlHwResources15 RbsDlHwResources16 PhysHsChanLimit17 SF4UL18 SF8UL19 SF16UL20 SF8gUL21 SF16g22 EdchLimitServingCell23 EdchLimitNonServingCell,24 SctpCongestion25 EdchLimitServingCellTti2

The inactivityDchTimer defines the maximum time of inactivity on the DCH allowed after the establishment of a RRC connection in CELL_DCH. It is restarted at the reception of the following messages:Downlink Direct TransferUplink Direct TransferInitial Direct Transfer After timeout, releasing the signaling connection is a normal behaviour for an UE in state CELL_DCH with Stand-alone SRB only to save system resources.

Congestion Control in RNC requested to decrease the resources usage on the existing connections of cell in congestion to admit a new connection or service with higher QoS priority by pre-emption or channel switching, system resources released.

Timeout waiting neither RRC Connection Setup Complete or NBAP Radio Link Restore Indication, caused by coverage or RF environmental related issues, like power, interference, shadowing, and so on...

RLC data transport failure on SRB2, caused by coverage or RF environmental related issues, like power, interference, shadowing, and so on...

Call drop

Call drop

Locking Eul channel caused many affected UeContexts release.Call drop

Locking hsDsch channel caused many affected UeContexts release.Call drop

Call drop

Performance degrade

Call drop

Call drop

Depends

See NBAP REJECT CAUSE Depends

See NBAP REJECT CAUSE Performance degrade

Call drop

The SRNC might receive an unexpected SCCP release indication for an established Iu connection. This could be initiated by either of the following:a) A SCCP RLSD message sent from the CN is received by the SRNC.b) A local detection in SRNC on that the SCCP connection is lost. After reception of the SCCP release indication for one CN if the UE had signalling connections towards two CNs, all resources associatedwith the CN for which the SCCP release indication comes is released. The signalling connection towards the other CN remains.

Timeout waiting RRC Radio Bear Reconfiguration Complete for ChannelSwitching in between Cell_DCH and Cell_FACH, caused by coverage or RF environmental related issues, like power, interference, shadowing, and so on...

Resource calculation(Mapping parameters) for Radio Connection was not passed for a new RRC connection establishment or radio link setup, caused by capability limitation of the cell in current snapshot.

For a connection that includes HSDPA, the PS part of the connection is considered lost by the RCS when the RLS that contains the Serving HS-DSCH cell, has been out-of-sync for a time given by the parameter hsDschRcLostT. This means that when the hsDschRcLostT timer expires, an Iu Release will be requested to the PS CN and when the dchRcLostT timer expires, an Iu Release will be requested to all involved CNs. It caused by coverage or RF environmental related issues, like power, interference, shadowing, and so on...

Case 1: Establishing a signaling connection to CN but the Ue reference has already have an iuSigConnId, the ranapInitialUeMessage was rejected, but sent over RANAP Direct Transfer to CN instead.Case 2: In other case could be RANAP failure causing the commuication to CN lost completely.

RLC data transport failure on RB, caused by coverage or RF environmental related issues, like power, interference, shadowing, and so on...

Call drop

Call drop

Performance degrade

Performance degrade

Security algorithm syncing failure in state CellUpdate or UraUpdate, see details on following ErrorCode 545

Timeout waiting for RRC Security Mode Complete, caused by RLC_RESET PDU received at pending RX activation of Ciphering configuration in SecurityControl, UL message(SecurityMode Command Complete) in SRB was discared. It's often a clash between different RNC and/or CN procedures.

1 Configuration Unsupported2 Physical Channel Failure3 Incompatible Simultaneous Reconfiguration4 Compressed mode runtime error5 Protocol Error6 Cell Update Occurred7 Invalid Configuration8 Configuration Incomplete9 Unsupported Measurement10 MBMS Session Already Received Correctly11 Lower Priority MBMS Service12 Spare513 Spare414 Spare315 Spare216 Spare1In the case of ChannelSwitching from Cell_FACH to Cell_DCH, it often the UE failed to establish the physical channel(s) indicated in the received CELL UPDATE CONFIRM message. When a physical dedicated channel establishment is initiated by the UE, the UE shall start a timer T312 and wait for layer 1 to indicate N312 "in sync" indications. On receiving N312 "in sync" indications, the physical channel is considered established and the timer T312 is stopped and reset. If the timer T312 expires before the physical channel is established, the UE shall consider this as a "physical channel failure". In such a situation, coverage or RF environmental issues are always the contributor.

Cell specific info is fetched from TopCell (doff, measurementId, nodePhasediff, nodePhaseDiffAcc, primaryCPICHPower, ulInterference, lac, rac, sac, individualoffset).

Call drop, or Performance degrade, depends

IUB FrameSynch DL: TimingAdj CtrlFrame received with ToA > ToAE, i.e. "crazy off"

Processing hardware unavailable in RBS was received. Performance degrade

Call drop

Call drop

Call drop

IE in RANAP RAB ASSIGNMENT REQUEST was not supportedPerformance degrade

Call drop

Call drop

See NBAP REJECT CAUSE Performance degrade

Call drop

Performance degrade

Connection to Ue lost, RRC communication failure Performance degrade

Timeout waiting for RRC Active Set Update Complete, caused by coverage or RF environmental related issues, like power, interference, shadowing, and so on...

1 Configuration Unsupported2 Physical Channel Failure3 Incompatible Simultaneous Reconfiguration4 Compressed mode runtime error5 Protocol Error6 Cell Update Occurred7 Invalid Configuration8 Configuration Incomplete9 Unsupported Measurement10 MBMS Session Already Received Correctly11 Lower Priority MBMS Service12 Spare513 Spare414 Spare315 Spare216 Spare1

RLC data transport failure on SRB3,caused by coverage related issues like out of coverage, poor coverage, or environmental related issues like interference, shadowing

Radio Connection Supervision function was timeout, all Radio links lost, caused by coverage related issues like out of coverage, poor coverage, or environmental related issues like interference, shadowing

RLC data transport failure for RB16(PS Interactive),caused by coverage or RF environmental related issues, like power, interference, shadowing, and so on...

1 Encode failed2 Timeout3 Transaction removed

CN Hard Handover for PS rab + CS signalling connection was not supported

Call drop

Performance degrade

See NBAP REJECT CAUSE

Call drop

Call drop

Call drop

Performance degrade

Call drop

A Cell program restarted causing internal communication broken to DcRh.


Case 1: If the Ue roams to a different cell during the Radio Bearer Setup Procedure the Radio Bearer Setup attempt will fail because the UE will not be able toswitch to DCH in the original cell while handling a Cell Update to the new cell. The Ue will send a Radio Bearer Failure in this situation on the CCH in thenew cell. (The Radio Bearer Setup Failure transaction Id will be different to the Radio Bearer Setup Transaction Id). The Failure can thus be ignored andthe use case continues normally (The Cell Update (new cell) is handled and the RAB Establishment continues from the propagation delay request. In the case where it is a Cell Update Same Cell,).Case 2: If the RADIO BEARER SETUP FAILURE is received on the CCH of the same cell (The transaction Ids are the same), it indicates that the RAB Establishment has failed in that cell. In this situation, the resources (dedicated and common) seized for the connection are released as described in the T_RABEST_1 timeout case.

Timeout waiting for RRC Radio Bearer Reconfiguration Complete, caused by coverage or RF environmental related issues, like power, interference, shadowing, and so on…

Timeout waiting for RRC Cell Change Complete, caused by coverage or RF environmental related issues, like power, interference, shadowing, and so on…

The RRC message received was not the one expected, Ue was not in sync with RNC

Uplink Counter Synchronisation IE not present in RRC RADIO BEARER RECONF COMPLETE message


Call drop

Performance degrade

Call dropSee NBAP REJECT CAUSE Call drop

Call drop

Call drop

Call drop

Call drop


Timeout waiting RRC Radio Bearer Release Response, caused by coverage or RF environmental related issues, like power, interference, shadowing, and so on…

InvalidConfiguration in RRC MESSAGE or error decoding UL DCCH message

The function is initiated by RANAP unavailable (a Core Networks is down), a cell unavailable, cell program restart, PDR SP unavailable, Cello unavailable,congestion, Pool congestion or RNSAP unavailable.

RLC data transport failure on SRB4, caused by coverage or RF environmental related issues, like power, interference, shadowing, and so on…

Timeout waiting for RRC Cell Change, caused by coverage or RF environmental related issues, like power, interference, shadowing, and so on…


400 drhTrBr_failedUnspecified401 drhTrBr_rncModuleDown402 drhTrBr_trBrNotFound403 "drhTrBr_failedToInsertTrBr"404 drhTrBr_cppNciRestartOnMp405 drhTrBr_cppNciNetConnRej406 drhTrBr_cppNciNodeConnRej407 drhTrBr_cppNciDiscInd408 drhTrBr_cepNotFound409 drhTrBr_failedToInsertCep410 drhTrBr_eriServerNotReadyForCepComm411 drhTrBr_cppEriCepReject412 drhTrBr_cppEriRestartOnMp413 drhTrBr_auditOngoing414 drhTrBr_spRestart415 drhTrBr_ipHostNotFound416 drhTrBr_failedToInsertIpTp417 drhTrBr_cppSciSessionSetupRej418 drhTrBr_ipTpNotFound419 drhTrBr_cppSciSessionModifyRej420 drhTrBr_auditInconsistency421 drhTrBr_cppSciTrafficIndSessionReleased422 drhTrBr_ipSessionReleasedIt's often caused by the underlying TNL resource unavailable temporarily.

Depends

Call drop

Call drop

Performance degrade

CN or BSC failed to prepare the resources for IRATHO Performance degradeSee Ref[1]See Ref[1]See Ref[1] and Ref[2]See Ref[1] See Ref[1] and Ref[2]See Ref[1] and Ref[2]See Ref[1] and Ref[2]

The SRNC might receive an unexpected SCCP release indication for an established Iu connection. This could be initiated by either of the following:a) A SCCP RLSD message sent from the CN is received by the SRNC.b) A local detection in SRNC on that the SCCP connection is lost. After reception of the SCCP release indication for one CN if the UE had signalling connections towards two CNs, all resources associatedwith the CN for which the SCCP release indication comes is released. The signalling connection towards the other CN remains.

The communication in between UEH and DCS was broken, caused by the release of SRB due to spProcessing failure.

Logical error in IE RL_InformationResponseList_RL_SetupRspFDD_PDU

1 Configuration Unsupported2 Physical Channel Failure3 Incompatible Simultaneous Reconfiguration4 Compressed mode runtime error5 Protocol Error6 Cell Update Occurred7 Invalid Configuration8 Configuration Incomplete9 Unsupported Measurement10 MBMS Session Already Received Correctly11 Lower Priority MBMS Service12 Spare513 Spare414 Spare315 Spare216 Spare1

Setting up AAL2 connection got remote reject due to resource temporary failure.

GSM Cell target Id could not be mapped to a GSM cell reference in UehUeCtxt data, wrong data in GSM relation.

See Ref[1]See Ref[1] See Ref[1] and Ref[2]See Ref[2]See Ref[2]

Trace Object

uehUeCtxtC* 1,3,6,7,enter,return

uehUeCtxtC* 1,3,7,enter,return

uehUeCtxtC* 6,7,enter,return RANAP_ASN bus_send, bus_receive

uehUeCtxtC* 1,3,6,7,enter,returnUE_TRBR_HANDL 3UE_GENERAL 3

RRC_ASN bus_send, bus_receive RANAP_ASN bus_send, bus_receive CON_HANDL 1,6,7

NBAP_ASN bus_send, bus_receiveDRIFT_DED 6,7

RRC_ASN bus_send, bus_receiveuehUeCtxtC* 1,3, enter, return

CHAN_SWITCH 6,7CELL_UPDATE 5,6,7DRIFT_DED 6,7IRAT_HANDOVER 6,7RAB_EST 6,7RAB_REL 3,5,6,7CON_HANDL 6,7

NBAP_ASN bus_send, bus_receiveRNSAP_ASN bus_send, bus_receiveCON_HANDL 6,7HANDOVER 1,3,6,7,state_change,enter,return

NBAP_ASN bus_send, bus_receiveRNSAP_ASN bus_send, bus_receiveCON_HANDL 6,7HANDOVER 1,3,6,7,state_change,enter,return

RRC_ASN bus_send, bus_receiveHANDOVER 6,7

RRC_ASN bus_send, bus_receiveCELL_UPDATE 6,7

GENRAB_EVAL 1,3GRC_SERV 1,3

RANAP_ASN bus_send, bus_receiveCN_HARD_HANDOVER 6,7IRAT_HANDOVER 1,6,7

RRC_ASN bus_send, bus_receiveCOMPRESSED_MODE 2,6,7HS_CELL_CHANGE 6,7POWER_CTRL 6,7IF_HANDOVER 2,3,6,7HANDOVER 6,7

RRC_ASN bus_send, bus_receiveIRAT_HANDOVER 2,6,7RAB_EST 3,6,7

UE_TRBR_HANDL 6,7

Radio Network Layer Cause0 Unkown C-ID,1 Cell not available,2 Power level not supported,3 DL radio resources not available,4 UL radio resources not available,5 RL Already Activated/allocated,6 Node B Resources Unavailable,7 Measurement not supported for the object,8 Combining Resources not available,9 Requested configuration not supported,10 Synchronization failure,11 Priority transport channel established,12 SIB Origination in Node B not Supported,13 Requested Tx Diversity Mode not supported,14 Unspecified,15 BCCH scheduling error,16 Measurement Temporarily not Available,17 Invalid CM Setting,18 Reconfiguration CFN not elapsed,19 Number of DL codes not supported,20 S-CPICH not supported,21 Combining not supported,22 UL SF not supported,23 DL SF not supported,24 Common Transport Channel Type not supported,25 Dedicated Transport Channel Type not supported,26 Downlink Shared Channel Type not supported,27 Uplink Shared Channel Type not supported,28 CM not supported,29 Tx diversity no longer supported,30 Unknown Local Cell ID,31 Number of UL codes not supported,32 Information temporarily not available,33 Information Provision not supported for the object,34 Cell Synchronisation not supported,35 Cell Synchronisation Adjustment not supported,36 DPC Mode Change not Supported,37 IPDL already activated,38 IPDL not supported,39 IPDL parameters not available,40 Frequency Acquisition not supported,41 Power Balancing status not compatible,42 Requested type of Bearer Rearrangement not supported,43 Signalling Bearer Rearrangement not supported,44 Bearer Re-arrangement needed,45 Delayed Activation not Supported,46 RL Timing Adjustment not supported,

47 MICH not supported,48 F-DPCH Not Supported

Transport Layer CauseTransport resource unavailable,Unspecified,

Protocol CauseTransfer syntax error,Abstract syntax error (reject),Abstract syntax error (ignore and notify),Message not compatible with receiver state,Semantic error, Unspecified,Abstract syntax error (falsely constructed message),

Miscellaneous CauseControl processing overloadHardware failure,O&M intervention,Not enough user plane processing resources,Unspecified,

basic ueh exception

Documents