UEH Exception Description

1.4.2007

IMPORTANT: This list is intended to give a description of the causes and known fixes for
network problems that are made evident by the UEH exception traces in RNC modules
MPs.

Please keep in mind that these exceptions are not always an indication of a fault - they
merely report that something in the call handling has not behaved as expected. A
substantial portion of the exceptions dealing with message timeouts and lower layer
retransmissions will be expected in normal operation due to imperfect RF conditions. If
this aspect is acknowledged and used along with the information on this page, the
statistics obtained through analysis of the exception occurrences can be a useful tool to
identify network faults and configuration problems.

In the end you will find a list for the cause codes.

UehBehaviourBaseProcedure code 51: RadioLinkReconfiguration : Cell Admission rejected

UehChSwitchDchToDchC code 5: Message Reject received, Cell Admission

UehDrncDedChRlSyncReconfC Code 5: admission Rej received

UehSoftHoC Code 16: Message Reject received, Cell Admission

Descriptio The UtranCell is not able to handle the new resource because of admission control
n: considerations.
Cause RnhIfCellAdmissionRejReasonD
code:
Action: Check the cause code for the given CIDs, which will indicate why admission failed there.
Note that this exception will be expected when admission control is working normally to
cope with excessive traffic on a cell. If there is evidence that accesses are being rejected
before the expected limit, then the UtranCell details in the RNC can be checked to
indicate if there are configuration/software issues.
Known RnhIfCellAdmissionRejReasonD Cause 13 (UniSaalCongestion) is occurring during soft
Issues: handover to a RBS that has hanging IMA.

UehBehaviourBaseProcedure code 56: RadioLinkReconfiguration: NBAP Radio Link

Reconfiguration Failure received

UehBehaviourBaseProcedure code 58: RadioLinkReconfiguration: RNSAP Radio Link

Reconfiguration Failure received
Action: Check the RBS/RNC if exceptions are repeated on a particular CID.

UehDrncDedChMeasInitC code 33: Measurement already started

Known An RNC software problem can lead to this exception (reported in WRNad08038, solved in
Issues: CXP9012014 R4AB). This does not have an impact on call success.

UehDrncDedChMeasInitC code 38: Nbap DedMeasInitFail received

Known Seen often in P4/P5ED. Problem has been reported in HG94164.
Issues:
 UehDrncDedChRlAdditionC Code 9: nbapMessage Rej received

UehDrncDedChRlSyncReconfC Code 5: nbapMessage Rej received

Cause RlibInsTerminatorRejectCauseD
code:
 UehIratHoUtranGsmC code 6: Received Ranap RelocationPreparationFailure for Ranap
Relocation Required, failing
Description An IRAT relocation procedure has received a failure message from the core network. The
: breakdown shows the target GSM CGI if available, otherwise the CID of the originating
UTRAN cell.
Cause DcsIfEventIratFailureCause
code:
Action: Repeated failures towards particular CGIs should be checked for data consistency in the
CN nodes.

UehRabEstDedDedC code 29: Timer T_RAB_EST_1 expiry, RRC Radio Bearer Setup
Complete not received
Known This was seen to be occurring for PS calls when the T_RAB timer in SGSN was set to 5
Issues: seconds. It should be 10 seconds to let the RNC and UE have time to establish the RAB.

UehRabHandlingC code 2: DcSp configuration failure

Cause DcsSpConfigRejD
code:

UehRabHandlingC code 4: Timer T_RABEST_1 expiry (RabHandling:UeConfiguration)

Description The timer T_RABEST is normally set to 5 seconds in the RNC. The timer Iu_TRABAssgt in
: the SGSN should be set to 10 seconds. The timer RABEST is started after
RABAssignmentRequest is received from the CN. If the RadioBearerSetup times out or
AAL2 setup times out, then the timer T_RABEST will expire, resulting in this cause code.

UehRrcConnSetupC Code 15: T_RRC_Est_1 expiry, Neither RRC Connection Setup

Complete or NBAP Radio Link Restore Indication received
Description The RNC has not received RrcConnectionSetupComplete from the UE nor
: RadioLinkRestoreIndication from the RBS in order to finalise an RRC Connection Setup
procedure. Possible reasons include:
Inadequate RF conditions
UE fault
RBS fault (check if occurences of this exception are concentrated on particular CIDs)

UehRrcConnSetupC Code 18: DcSp processing failure at RRC Connection Setup

Description An attempted RRC connection has not been established due to a problem reported by
: DCS.
Cause DcsProcessingFailureIndD
code:
Known This exception has been seen with causecode=101 (not listed in 32/1551-CRA 403 38/1
Issues: Rev.B) for IubLinks which have problems with the internal node synchronisation
connectivity within the RNC. This has been linked to Main MP switchovers, and the
allocation and linkages of AAL0 resources after the standby MP becomes active. A quick
way to check this for sites which are reporting bad RRC connection success statistics is
by observing the last reported phase measurement within the NodeSynch MOs for the
IubLinks:
get NodeSynch timeStamp
These timestamps should have values within the supervision interval from the current
node time (attribute supervisionIntervalT). If this is not the case, a module MP restart for
the affected module(s) has been seen to reconnect the ROs as required.
(Note that the command eg "lhsh 000400 aal0statcep -l" can also be used to observe the
AAL0 CEP ROs on the TUBs. A state of (3) is normal, (1) indicates that there is not a
proper connection to the fRO).
(Reported in HG66365)
 UehSignConnSetupC code 2: RANAP Initial UeMessage Reject received
Known Seen to occur at SGSN restarts.
Issues:

UehSoftHoC Code 11: Timer timer_RRC_ASU expiry, RRC Active Set Update Complete not
received at radio link deletion
UehSoftHoC Code 30: Timer timer_RRC_ASU expiry, RRC Active Set Update Complete not
received
Description An ASUC message has not been received within the expected period. This will normally
: be a symptom of a fault in RLC transmission.
 UehSoftHoC Code 15: RNH cell information request failure
Description This exception has been seen when an attempt is made to retrieve configuration
: information from RNH for an unavailable cell, initiated for example when a UE sends a
measurement report for a given PSC, and the RNC tries to get data for the target cell.
Note that the CID reported in the exception is the current serving cell, not the cell for
which the information request has failed.
Known This is seen to happen regularly when sites are affected by transmission faults.
Issues: Another analysis has shown that this can happen in a case where a neighbour cell is
radiating, but is locked in the RNC (or where two identical scrambling codes can be
received in a location, and one of them is locked). Neighbour cells causing problems in
this way can be identified by inspecting the values of the pmNoTimesCellFailAddToActSet
counter.

UehSoftHoC Code 26: Message Reject received, NBAP Radio Link Setup Request
Known In one case, this exception was seen regularly for an RBS which had a loopback on one of
Issues: the transmission links.

UehSoftHoC Code 28: AAL2 network connection setup failure on Iub interface
Description An AAL2 connection setup problem has occured on the Iub interface towards a particular
: RBS during soft HO. This normally does not directly cause a drop, but the new cell will be
removed again from the active set, and there may be repeated attempts to add this cell
depending on RF conditions, which will increase the signalling overhead. If the RF
environment degrades to the point where the call cannot be maintained without the new
cell, then the call will drop. These faults are typically a result of:
Congested transport connectivity for available Iub AAL2 VCs
AAL2 routing data misconfiguration
Transport/Node faults
Cause CpxAal2NciConnectRejCauseD
code:
Action: Use the reject type and reject cause codes to determine more specific details of the
particular problem on the node, and then check nodes/connectivity/traces as appropriate.

UehUeCtxtC Code 5: Logical Error in Protocol message

Description This exception indicates that an unexpected message (in terms of the normal call
: progression) has been received for this UeRef. These exceptions can include both Rel and
NoRel cases, depending on the message received.
Known A fault has been detected where HS drops can occur at a physical channel
Issues: reconfiguration when the RNC sends the CFN for the reconfiguration to take effect. A
check is performed in the RBS to see if the requested change is to occur within the guard
period and, if so, it should be rejected. However the check is not performed correctly, and
an unnecessary RadioLinkFailureIndication can be sent to the RNC (problem described in
HG60622, reported solved in CXP9010809 R27D - P4.0.6). This can account for cases seen
reported with "NBAP RL Failure message (6)" closely following a
RadioLinkReconfigurationCommit.

UehUeCtxtC Code 17: Aal2 Disconnect Ind

Description An unexpected Q.2630 REL message has been received from an external source. This can
: happen for Iub connections in the case of RBS faults or restarts - the RXI will send REL
for each seized AAL2 connection if it detects that the connection to the RBS has been
lost.
Cause CpxAal2NciDisconnectCauseD
code:
Action: Repeated occurences will flag network configuration problems or other faults.

UehUeCtxtC Code 18: HandoverEvaluation function on SP has failed

Cause DcsIfEventHandoverEvalConnReleaseIndD
code:
Action: A cause code of 1 (CELL_NOT_IN_NEIGHBOURSET) indicates a call drop due to a missing
neighbour. The UE has reported that the strength/quality of a measured scrambling code
is high compared to that of the best cell in the active set (threshold determined by
releaseConnOffset), yet is not listed as a potential neighbour. If available,
GPEH/CTR/UETR events can be used to get details on this problem - the measured
scrambling code is not available from the exception printout.
 UehUeCtxtC Code 23: Release of packet due to SP processing failure

UehUeCtxtC Code 24: Connection release due to SP processing failure on Rrc Rb

UehUeCtxtC Code 25: Connection release due to SP processing failure on Unknown Rb

Description: Cause=1 (RLC_RESET) indicates that the maximum number of retransmission
of packets on the RLC layer was reached. Possible reasons for this include:
Inadequate RF conditions
UE faults have been found in Qualcomm UE firmware which can lead to the
RLC UL transmission hanging in RbId=16 (HS) after physical channel
reconfigurations. If the UE software is upgraded to at least 304456E, drops
due to these faults are seen far less often. This is normally associated with
exceptions due to radio link failure on NBAP. The RNC will typically send an
IuReleaseRequest to the CN with cause "radioNetwork/radio-connection-with-
UE-lost" after these exceptions are seen.
Cause code: DcsProcessingFailureIndD
Known Issues: This can be seen occasionally in association with IRAT handovers (described
in WRNac80939). If the IRAT Cell Change takes longer than usual to execute,
then it is possible that DCS may be still trying to communicate with the UE
after the UE has moved U->G. In this case, spProcessingFail will be sent to
UEH, but this should not affect the success of the IRAT handover.
Action: If these exceptions are seen consistently with Cause=1 in measured good RF
conditions, then this warrants further investigation. However these faults
generally require end-to-end tracing between RNC and UE, because they are
related to the RLC dialogues between these entities. Tracing on RETRANSM
and DISCARD in the RNC DC device handling the call can give more
information on the failure. This data is more useful in conjunction with
simultaneous RLC tracing on the UE.

UehUeCtxtC Code 57: Timeout on RCS All RL Lost timer, releasing Iu Connection, non
running state
Description: When the RBS detects loss of UL synchronization for a RL Set in a Radio
Connection it will send the Radio Link failure Indication message to the RNC.
If all RLs have failed, the timer dchRcsLost is started (about 5 sec). When the
timer expires, the Radio Connection is considered lost and the RNC proceeds
to tear down the call.
Known Issues: This could happen when there is an Iu-ReleaseRequest with cause
"radioNetwork/user-inactivity" or "radioNetwork/radio-connection-with-UE-
Lost".

UehUeCtxtC Code 58: Timeout on RCS Hs RL Lost timer, releasing Iu Connection, non
running state
Description: When the RBS detects loss of UL synchronization for a RL Set in a Radio
Connection it will send the Radio Link failure Indication message to the RNC.
If all RLs have failed, the timer HsdchRcsLost is started (about 5 sec). When
the timer expires the Radio Connection is considered lost and the RNC
proceeds to tear down the call.
Known Issues: This could happen when there is an Iu-ReleaseRequest with cause
"radioNetwork/user-inactivity" or "radioNetwork/radio-connection-with-UE-
Lost".
UE suspected faults: UEs stop UL transmission, which cause RLC AM
retransmissions, and L1 NACK rate reaches 100%.
Old QC software LLRQ 3.0.34.88, UE stops UL transmission causing the call
to drop.
Sierra Wireless cards with 1.0.1 level firmware have this problem, it has
been fixed in R1.1.29.
 UehUeCtxtC Code 62: Ranap InitialUeRej received
Known Issues: Has been seen in cases when MTP3 links towards core network are unstable.
Check link states in RNC, and resources in MSC and SGSN as appropriate.

UehRrcConnSetupC Code 21: DcSp processing failure at Handover Evaluation

UehUeSecurityCtrlC code 10: DcSp communication failure

UehUeSecurityCtrlC code 13: DcSp communication failure while waiting for

spRbWaitCipheringRsp
 UehSoftHoC Code 51: DcSp Processing Failure Received
Descriptio Miscellaneous DCS failures
n:
Cause DcsProcessingFailureIndD
code:

Cause Codes: (From 32/1551-CRA 403 38/1 Rev B)

CellUpdateCause
0 CellReselection
1 periodicalCellUpdate
2 uplinkDataTransmission
3 utran_pagingResponse
4 re_enteredServiceArea
5 radiolinkFailure
6 rlc_unrecoverableError
7 CellUpdateCause_spare1

CellUpdateFailure
1 configurationUnsupported_chosen
2 FailureCauseWithProtErr_physicalChannelFailure_chosen
3 incompatibleSimultaneousReconfiguration_chosen
4 compressedModeRuntimeError_chosen
5 FailureCauseWithProtErr_protocolError_chosen
6 cellUpdateOccurred_chosen
7 invalidConfiguration_chosen
8 configurationIncomplete_chosen
9 unsupportedMeasurement_chosen
10 FailureCauseWithProtErr_spare7_chosen
11 FailureCauseWithProtErr_spare6_chosen
12 FailureCauseWithProtErr_spare5_chosen
13 FailureCauseWithProtErr_spare4_chosen
14 FailureCauseWithProtErr_spare3_chosen
15 FailureCauseWithProtErr_spare2_chosen
16 FailureCauseWithProtErr_spare1_chosen

CpxAal2NciConnectRejCauseD, CpxAal2NciDiscIndD, CpxAal2NciDisconnectCauseD

rejectType
1 Local reject
2 Remote reject
rejectCause - Local reject
1 CELLO_AAL2NCI_NO_ROUTE_TO_DEST
2 CELLO_AAL2NCI_SWI_EQUIP_CONG
3 CELLO_AAL2NCI_NO_RESOURCES_AVAILABLE
4 CELLO_AAL2NCI_OTHER_REJ_CAUSE
rejectCause - Remote reject
3 CAUSE_NO_ROUTE
31 CAUSE_NORMAL
34 CAUSE_NO_CHANNEL
38 CAUSE_NETWORK_OUT_OF_ORDER
41 CAUSE_TEMP_FAILURE
42 CAUSE_SWITCHING_CONGESTION
44 CAUSE_CHANNEL_UNAVAILABLE
47 CAUSE_RESOURCE_UNAVAILABLE
93 CAUSE_CANNOT_HANDLE_PARAMETER
95 CAUSE_INVALID_MESSAGE
96 CAUSE_MANDANTORY_IE_MISSING
97 CAUSE_MESSAGE_NOT_IMPLEMENTED
99 CAUSE_PARAMETER_NOT_IMPLEMENTED
100 CAUSE_INVALID_IE_CONTENTS
102 CAUSE_RECOVERY_ON_TIMER_EXPIRY
110 CAUSE_MESSAGE_DISCARDED_UNRPAR

DcsProcessingFailureIndD
0 OUT_OF_MEMORY
1 RLC_RESET
100 OTHER_FAILURE
200 INCORRECT_TIMING
201 ERR_MAC_CONFIG
202 ERR_MAC_CONFIG_TX
203 ERR_MAC_CONFIG_RX

DcsIfEventHandoverEvalConnReleaseIndD
0 UNSPECIFIED_RELEASE_CAUSE
1 CELL_NOT_IN_NEIGHBOURSET
2 EVENT_BUFFER_EXCEEDED
3 BUFFER_TIME_EXCEEDED
4 CELL_SYNCH_INFO_NOT_AVAILABLE

DcsIfEventIratFailureCause
0 UNSPECIFIED_FAILURE_CAUSE
1 RELOCATION_FAILURE
2 HO_FROM_UTRAN_FAILURE

DcsSpConfigRejD
Common cause values DCS and CCS
1 dcsArgValueOutOfRange (Argument value too little or too big)
2 DcsCepAttachMissing (CEP attachment for AALxEDI not made)
3 dcsCepAttachUnsuccessful (CEP attachment for AALxEDI did not succeed)
4 DcsNoFreeMemory (No free memory for new definition)
5 DcsNoIdleInstance (No idle instance available. The resource handler has allocated too
many connections to this SP.)
6 dcsProtocolEntityNotCreated (Protocol entity not created (no arg. change possible))
7 dcsServiceTypeMismatch (Service type does not match (e.g. with logical channel type))
8 DcsIdNotDefined (A needed identity does not exist. This is a possible code from every
primitive if any needed id is missing)
9 DcsIdCollision (The id is already d. Used in add primitives)
10 DcsArgMismatch (The primitives in the bag do not make a sensible configuration)
11 DcsSpOverload (The SP CPU is too loaded)
12 DcsGeneralError (Error in the bag not related to a certain argument or primitive)
20 dcsUeRefOrModIdOutOfRange (Not valid ueRef and/or moduleId)
21 spInternalBagTimedout (Not all bag clients responding within a limited time)
99 DcsOtherCauseCode (Other cause code)
DCS specific cause values
100 dcsReconfigurationOngoing (There is already a configuration ongoing i.e. commit has not
been received before new prepare or the previous configuration is still waiting for the
correct CFN)
101 dcsWrongActiveSetSize (The size of the active set is bigger than what HoEval can handle)
102 DcsBagSearchFailed (Fail to found the primitive in the bag)
103 dcsNoInstanceAllocatedForUE (For the requested UE there is not an allocated instance of
HoEval)
104 dcsAlreadyAllocated (The UE already has been allocated to)
105 dcsSecKeyNotActivated (The new security keys cannot be activated)
106 dcsGapSequenceAlreadyActivated (ransmission Gap Sequence already activated)

DrhDcSpCtrl.h, DrhDcRhInitialResourceRejD, DrhDcRhReserveAal2CepRejD,

DrhIfDcRhResourceChangeRejD, drhDcResultE
300 failedUnspecified
301 noResources
302 missingCepRef
303 faultySignalOrder
304 noCepsAvailable
305 celloEriCepReject
306 celloNciConnReject
307 spRestarting
308 spBlocked
309 celloNciRestartOnMp
310 celloEriRestartOnMp
311 unknownDrhRcRef
312 clearResourceReqSent
313 rncModuleDown
314 wrongOldUeRate

drhDcRhCepRejCauseE
400 Aal5ResourcesNotAvailable
401 Aal5ManagementInduced
402 Aal5OtherRejectCause
403 Aal5EriDown
404 WrongSpState
405 NoFreeCepData
406 SpPointerZero
407 CepDataNotInitialized
408 FaultyCepState

drhIfIurCcControl
300 FailedUnspecified
301 NoResources
302 MissingCepRef
303 NoCepsAvailable
304 CelloEriCepReject
305 CelloNciConnReject
306 SpRestarting
307 SpBlocked
308 CelloNciRestartOnMp
309 CelloEriRestartOnMp
310 DcRhReject
311 DcSpEdiAttachFailure
312 CcSpEdiAttachFailure
313 IurSpEdiAttachFailure
314 UnknownIurCcRhRef

drhIfPdrRh.h
300 failedUnspecified
301 noResources
302 celloEriCepReject
303 celloNciConnReject
304 rcSpCepReject
305 rcSpEdiAttachFailure
306 hardwareFailure
307 spBlocked
308 spReconfigured
309 spDeleted
310 celloNciRestartOnMp
311 celloEriRestartOnMp
312 rcSpBlocked
313 rcSpRestart
314 rcAal2EriRestart
315 rcAal2NciRestart
316 rcAal5Restart
317 noPdrSpAndNoCentral
318 noPdrSp
319 ueAlreadyInUseOnThisPort
320 centralRhReject
321 noSpIpAddress
322 dcMuxIdError
323 pdrSpFailedUnknownSpIpAddress
324 pdrSpFailedEdiAttach
325 pdrSpFailedUnspecified
326 spRestorationFailure
327 spIpAddressDown
328 gtpPathDown
329 centralRhDown
330 serverPdrRhDown
331 noPidForSp
332 celloEriServiceNotConnected
333 maxResult

drhPdrRhSpStateE
0 InUse
1 NotConfigured
2 Restarted
3 Blocked
4 Deleted
5 Aal5NciDown
6 Aal5EriDown
7 NoActiveIpAddresses
InterRAT_ChangeFailureCause
1 configurationUnacceptable_chosen
2 physicalChannelFailure_chosen
3 protocolError_chosen
4 unspecified_chosen
5 spare4_chosen
6 spare3_chosen
7 spare2_chosen
8 spare1_chosen

procType
1 rrcConnSetup
2 signConnSetup
3 signConnRelease
4 rabEstablishDedCom
5 rabEstablishComDed
6 rabEstablishDedDed
7 rabReleaseDedDed
8 rabReleaseDedCom
9 rabReleaseComDed
10 ueConnRelease
11 softHandover
12 ueSecurityCtrl
13 cellUpdate
14 measure
15 chSwitchToFach
16 chSwitchOnDch
17 chSwitchToDch
18 startCompMode
19 stopCompMode
20 iratHoUtranGsm
21 iratHoGsmUtran
22 iratCcUtranGsm
23 forcedSignConnRelease
24 forcedUeConnRelease
25 forcedRabReleaseDedDed
26 forcedRabReleaseComDed
27 forcedRabReleaseDedCom

procType_Drift
1 rlSetup
2 rlAddition
3 rlDeletion
4 rlSyncReconf
5 cellUpdate
6 measInit
7 measFail
8 measTerm
9 comTrChRelease
10 comTrChSetup
11 dlPowerCtrl
12 compressedMode
13 forcedRlDeletion
14 forcedComTrChRelease

result
1 getRcSpCtrlBarredRef
2 getRnhCellBarredRef
4 getUuRrcBarredRef
8 getIubNbapBarredRef
64 getIurRnsapBarredRef

resultFlag
98 ranap_semantic_error
99 ranap_message_not_compatible_with_receiver_state

RoamCptDrncRbsData
1 RoamCptRbs: Aal2 Connection RRC INVALID
2 Found X configured TrCh for RRC! Expected 1 and only 1
3 RoamCptRbs: dchIdDrncRrc INVALID (no RRC connection)
4 RoamCptRbs: Aal2 Connection Speech INVALID
5 Found X configured TrCh for Speech! Expected no more than 3!
6 RoamCptRbs: Aal2 Connection UDI INVALID
7 Found X configured TrCh for CsFixRate ! Expected 1
8 Found X configured TrCh for CsVarRate ! Expected 1
9 RoamCptRbs: dchIdDrncUdi INVALID (no UDI connection)
10 RoamCptDrncRbs: Aal2 Connection Packet INVALID
11 Found X configured TrCh for Packet ! Expected 1
12 RoamCptRbs: dchIdDrncPacketRab INVALID (no Packet connection)

RoamCptData
1 RoamCpt: ulScramblingCode INVALID (not state DCH)
2 RoamCpt: RabSpeech INVALID (no Speech rab)
3 RoamCpt: RabUDI INVALID (no UDI rab)
4 RoamCpt: RabPacket INVALID (no packet rab)
5 RoamCpt: Common Channel INVALID (not state RachFach)
6 Can't handle X rbs's!! Maximum number allowed = 5

RoamCptRbsData
1 Can't handle X RLs!! Maximum number allowed = 5
2 RoamCptRbs: Aal2 Connection RRC INVALID
3 Found X configured TrCh for RRC! Expected 1 and only 1
4 RoamCptRbs: dchIdRrc INVALID (no RRC connection)
5 RoamCptRbs: Aal2 Connection Speech INVALID
6 RoamCptRbs: Aal2 Connection UDI INVALID
7 Found X configured TrCh for CsFixRate ! Expected 1
8 Found X configured TrCh for CsVarRate ! Expected 1
9 RoamCptRbs: dchIdUdi INVALID (no UDI connection)
10 RoamCptRbs: Aal2 Connection Packet INVALID
11 Found X configured TrCh for Packet ! Expected 1
12 RoamCptRbs: dchIdPacketRab INVALID (no Packet connection)

RlibInsTerminatorRejectCauseD
1 EncodeFailed
2 Timeout
3 TransactionRemoved

RnhIfCellAdmissionRejReasonD
1 Congestion
2 AseUl
3 AseDl
4 DlPwr
5 DlCode
6 SF8
7 SF16
8 SF32
9 CompModeLimit
10 CellDeactivated
11 RoutingFailure
12 LoadSharing
13 UniSaalCongestion
14 RbsUlHwResources
15 RbsDlHwResources
16 PhysHsChanLimit
17 SF4UL

RnhIfCellAddUeCcRejD
300 drhCcRh_failedUnspecified
301 drhCcRh_noResources
302 drhCcRh_missingCepRef
303 drhCcRh_faultySignalOrder
304 drhCcRh_noCepsAvailable
305 drhCcRh_celloEriCepReject
306 drhCcRh_celloNciConnReject
307 drhCcRh_spRestarting
308 drhCcRh_spBlocked
309 drhCcRh_celloNciRestartOnMp
310 drhCcRh_celloEriRetartOnMp
311 drhCcRh_rcRhReject=
312 drhCcRh_rcSpEdiAttachFailure
313 drhCcRh_ccSpEdiAttachFailure
314 drhCcRh_unknownDrhCcRef
315 drhCcRh_clearResourceReqSent
316 drhCcRh_rncModuleDown
1 ccsArgValueOutOfRange
2 ccsCepAttachMissing
3 ccsCepAttachUnsuccessfull
4 ccsNoFreeMemory
5 ccsNoIdleId
6 ccsProtocolEntityNotCreated
7 ccsServiceTypeMismatch
8 ccsIdNotDefined
9 ccsIdCollision
10 ccsArgMismatch
11 ccsPrimMismatch
12 ccsSpOverload
99 ccsOtherCauseCode
301 ccsDrhArgValueOutOfRange
302 ccsDrhSpare1
303 ccsDrhSpare2
304 ccsDrhNoFreeMemory
305 ccsDrhNoIdleId
306 ccsDrhProtocolEntityNotCreated
307 ccsDrhServiceTypeMismatch
308 ccsDrhIdNotDefined
309 ccsDrhIdCollision
379 ccsDrhOtherCauseCode

RnhIfUeRegistrationRegisterServingUeCtxtRejReasonD
1 other
2 rejectDueToMpOverload
3 rejectDueToEcRedirectRequired
4 rejectDueToUeIdentityCollision

status
2 fail
3 errorIndication
4 messageReject cause is Timeout
5 messageReject cause not Timeout

UehMeasureRunReqD->measChoice
1 UECC_MEAS_ACTIVATE_REC
2 UECC_MEAS_DEACTIVATE_REC
3 UECC_MEAS_ACTIVATE_REC_SOFTHO
4 UECC_MEAS_ACTIVATE_REC_CCH_TO_DCH
5 UECC_MEAS_UE_POSITIONING

UehRadioConnType
0 uehNotValid
1 uehRrcConn
2 uehSpeech
3 uehUdiFixed64
4 uehPacketCch
5 uehPacket64
6 uehPacket128
7 uehPacket384
8 uehCs57
9 uehSp0
10 uehSp64
11 uehPreconfRrcOnly
12 uehPreconfSpeech
13 uehPsStreamInt8
14 uehUdiFixed65Int8
15 uehPacket64Hs
16 uehPacket384Hs
17 uehPsStream128Int8
18 uehRadioConnTypeEMaxVal

UehCNIdE
0 uehCNidCircuit
1 uehCNidPacket
2 uehCNidUndef