SUMMARY

1.1 RR_ERR_RNCAP_RLC_FAILURE_SRB_RST

1.2 RR_ERR_RNCAP_RLC_ FAILURE_TRB_RST

1.3 RR_ERR_IUB_INTERFACE_PERMANENT_RL_FAILURE

1.4 RR_ERR_RNCAP_RB_WAIT_UE_RB_CFG_TIMEOUT

1.5 RR_ERR_RNCAP_CU_WAIT_UE_RSP_TIMEOUT

1.6 RR_ERR_RNCAP_ALCFG_IUB_AAL2_FAILURE

1.7 RR_ERR_RNCAP_RC_REL_MACD_STATUS_ERR

1.8 RR_ERR_RNCAP_DEL_OLD_CCB

1.9 RR_ERR_RNCAP_RRC_UE_RSP_TIMEOUT

1.10 RR_ERR_IU_INTERFACE_RELOC_CANCELLED

1.11 RR_ERR_IU_INTERFACE_FAIL_IN_RADIO_INTERF_PROC

1.12 RR_ERR_RNCAP_RELOC_PHY_CH_RECFG_CMP_TIMEOUT

1.13 RR_ERR_IU_INTERFACE_UNSPECIFIED_FAIL

1.14 RR_ERR_IU_INTERFACE_TIMER_RELOC_CMP_EXPIRY

1.15 RR_ERR_RNCAP_RL_CAUSE_NODEB_TIMEOUT

1.16 RR_ERR_IUB_INTERFACE_CAUSE_RADIO_NW_UNSPECIFIED

1.17 RR_ERR_UU_INTERFACE_INVALID_CFG_ERR_NULL_TYPE

1.18 NBM_CRA_CELL_RR_CRM_FAIL

1.19 RR_ERR_RNCAP_RB_CU_OVERLAP_BACK

1.20 RR_ERR_RNCAP_RRC_MAIN_ABNORMAL_ERR

1.21 RR_ERR_IUB_INTERFACE_REQUESTED_CONFIGURATION_NOT_SUPPORTED

1.22 RR_ERR_RNCAP_HHO_PHYCH_RECFG_TIMEOUT

1.23 RR_ERR_UU_INTERFACE_PH_CH_FAIL_ERR_NULL_TYPE

1.24 RR_ERR_IU_INTERFACE_NO_RSRC_AVAIL

1.25 RR_ERR_RNCAP_ALCFG_IU_AAL2_FAILURE

1.26 RR_ERR_RNCAP_ALCFG_IUB_AAL2_FAILURE

1.27 RR_ERR_IUB_INTERFACE_TRANSP_RESOURCE_UNVAILABLE

1.28 L2ERR_FPMDC_TR_SYN_NO_RESPONSE_AFTER_MAX_RETRY

1.29 RR_ERR_UU_IRCFC_PROTCL_ERROR_ERR_BEGIN

1.30 RR_ERR_UU_IRHFC_PROTCL_ERR_BEGIN

1.31 RR_ERR_IU_INTERFACE_REL_DUE_TO_UE_GEN_SIG_CONN_REL

1.32 RR_ERR_IU_INTERFACE_OM_INTERVENTION

1.33 RR_ERR_IU_INTERFACE_REQUESTED_INFO_NOT_AVAIL

1.34 RR_ERR_IU_INTERFACE_UNKNOWN_TARGET_RNC

1.35 RR_ERR_IU_INTERFACE_RELOC_FAIL_IN_TARGET_CN_RNC_OR_TARGET_SYS

1.36 NBM_CRA_CELL_RR_FAIL

1.37 NBM_IUB_RESET

1.38 RR_ERR_RNCAP_CU_CELLFACH_NOT_FIND_PROC

1.1 RR_ERR_RNCAP_RLC_FAILURE_SRB_RST

Failure error

code

RR_ERR_RNCAP_RLC_FAILURE_SRB_RST

436799455

Failure reasons

Release the bearer signaling the RLC Reset occurs, usually

because of the poor quality of empty, RLC kept retransmission

resulting reset.。

Failure flowchart

Root due to the

Find method

First, you can determine the upstream or downstream

problems. May lead to downstream signaling downstream quality

problems can not be issued. May also lead to signaling

the RLC packets of ACK can not reported due to uplink quality

problems. Can by PCHR field BLER to determine whether the

uplink BLER higher. Can also check the total number of packets

dropped call signaling transport channel receiver and wrong to judge

by the number of packets the uplink that you have received the

wrong package. Also can refer to the same time period in the plot

log ISCPmeasurement value (ISCP higher system outside

interference over large lead RLC can not receive the the

uplink ACKpacket). If the UE reported downlink BLER, you can also

look at the the downlink BLER is too high then the UE is unable to

close the whole downstream signaling packets.

PCHR concern I

E

Plot log corresponding slot UL ISCP value, path: district Logs -

> cell -> carrier -> timeslot -> UL ISCP

RRC release information block dropped calls before signaling

transport channel in the wrong package number, UL / DL BLER. The

path to: user log -> RRC release -> exception information -> UL / DL

BLER + the total number of packets dropped call signaling transport

channel receiver + dropped call signaling transport channel received

the wrong number of blocks.

1.2 RR_ERR_RNCAP_RLC_FAILURE_TRB_RST

Failure error

code

RR_ERR_RNCAP_RLC_FAILURE_TRB_RST

436799456

Failure reasons

Lead to the release of the bearer service RLC reset occurs, usually

because of the poor quality of empty, RLC kept retransmission

resulting reset.

Failure flowchart

Root due to the

Find method

The similar reasons same

RR_ERR_RNCAP_RLC_FAILURE_SRB_RST difference in that the

object is a business of the RLC, the need to check the total number

of blocks and the wrong block number as well as uplink service

the BLER RAB information block the link release uplink received.

PCHR

CONCERN IE

The RAB information block link release uplink reception before the

total number of blocks / wrong number of blocks,

the UL business the BLER. The path to: user log ->

RABinformation -> exception information -> UL BLER the link before

release in the number of each grade range + RAB block upstream

receiving total number of blocks / wrong number of blocks.

1.3 RR_ERR_IUB_INTERFACE_PERMANENT_RL_FAILURE

Failure error

code

RR_ERR_IUB_INTERFACE_PERMANENT_RL_FAILURE

436996134

Failure reasonsReceived the the NODE B reported the RL FAILURE IND, uplink

radio link synchronization fails

Failure flowchart

Root due to the

Find method

The cause is usually due to the decline in the quality of the air

interface link uplink radio link synchronization failure generally

occurs this error appears BLER elevated.Dropped calls can be

checked before the the PCHR plot logISCP. ISCP higher system

interference may lead; otherwise might cover problem

PCHR

CONCERN IE

Plot log corresponding slot UL ISCP value, path: district Logs -

> cell -> carrier -> timeslot -> UL ISCP

User downlink transmission code link release power T

CPvalues, the path to: user log -> RRC release -> exception

information -> DL TCP number of reports -> TCP.

1.4 RR_ERR_RNCAP_RB_WAIT_UE_RB_CFG_TIMEOUT

Failure error

code

RR_ERR_RNCAP_RB_WAIT_UE_RB_CFG_TIMEOUT

437127146

Failure reasonsDCCC, business release / build process release Ue not

returnRB Reconfiguration Complete message

Failure flowchart

Root due to the

Find method

This situation generally, there are two possibilities, one is a

configuration message in the UE in the old link is not received

full RB Another situation is that the UE back to theRB configuration

response message, but due to the problem of the quality or the

transmission of the uplink, the RNC in the new The link did not

receive a response message.

(Or DCCC failed before failure) signaling transport channel to

the wrong number of packets to determine whether the uplink

problem created by the the uplink BLER well RAB of PCHR

RAB establishment

failure (, or DCCC failure) RLCretransmission rate can also check to

determine whether theUE not readily receive

messages RB configuration RLCretransmission rate is too high

PCHR

CONCERN IE

RRC release block UL BLER, the SRB2 RLC retransmission rate,

the wrong number of packets received by the transmission

channel / total number of packets. Path: user log-> RRC release -

> Exceptions -> UL / DL BLER + the total number of packets

dropped call signaling transport channel receiver+ signaling

transport channel dropped calls before receiving the wrong number

of blocks + SRB2 RLC retransmission rate.

1.5 RR_ERR_RNCAP_CU_WAIT_UE_RSP_TIMEOUT

Failure error

code

RR_ERR_RNCAP_CU_WAIT_UE_RSP_TIMEOUT

437127131

Failure reasonsConfigured response timeout waiting for empty cell update

procedure RNC issued CELL UPDATE CONFIRM

Failure flowchart

Root due to the

Find method

This situation is similar to the error 1.4. The different is that

the CELL UPDATE CONFIRM is in the common channel through

the UM mode hair. It can only check the uplink. The cell update

failed general will cause RRC release RRCrelease signaling

transport channel, you can check the wrong number of packages

and the total number of packets. If the total number of packets

to 0, then the UE no response message on the hair, is likely to be

the downlink UE does not receive configuration information leading

to.

PCHR

CONCERN IE

RRC release the block UL BLER, the total number of packets

dropped call signaling transport channel receiver / wrong number of

packages. The path to: user log -> RRC release ->exception

information -> UL / DL BLER + the total number of packets dropped

call signaling transport channel receiver +dropped call signaling

transport channel received the wrong number of blocks.

1.6 RR_ERR_RNCAP_ALCFG_IUB_AAL2_FAILURE

Failure error

code

RR_ERR_RNCAP_ALCFG_IUB_AAL2_FAILURE

436603622

Failure reasonsN ODE B initiated the IUB mouth AAL 2 release, trigger business

release

Failure flowchart

Root due to the

Find method

The cause is usually due to the decline in the quality of the air

interface link uplink radio link synchronization failure generally

occurs this error appears BLER elevated.Dropped calls can be

checked before the the PCHR plot logISCP. ISCP higher system

interference may lead; otherwise might cover problem

PCHR

CONCERN IE

Corresponding slot UL ISCP value plot log path: the plot log-

> Cell -> carrier -> -> UL ISCP slot;

User downlink transmission code link release power

the TCPvalue, path: users log -> RRC release -> Exceptions -> DL

TCPnumber of reports -> TCP.

1.7 RR_ERR_RNCAP_RC_REL_MACD_STATUS_ERR

Failure error

code

RR_ERR_RNCAP_RC_REL_MACD_STATUS_ERR

436799446

Failure reasons L2 MACD reported abnormal status report led business release

Failure flowchartNo

Root due to the

Find method

The error code L2 MACD reported exception error collectively,

for specific error root causes need to see the the

original MACD returned error code to determine the specific cause.

If this type of error occurs, submitted in

the PR platform(w ww.support.td-tech.com) the RNC Technology

Consulting single details refer to Overview section.

PCHR

CONCERN IE

L2 abnormalities cause value coding. Path: user log -> RAB,

RRC release information -> exception information -> L2Abnormal

values encoded

1.8 RR_ERR_RNCAP_DEL_OLD_CCB

Failure error

code

RR_ERR_RNCAP_DEL_OLD_CCB

437127121

Failure reasons

User actually has dropped calls, but the network side resources has

not been completely emptied, the the UE again initiates a

connection leading to the user once the connection is released.

Failure flowchart

Root due to the

Find method

Usually situation may be due to the lost contact, the UE and the

network side initiates a service, or the user to re-enable the UE to

re-initiate the RRC connection, and the RNCside is not the user

resource release. Also a small part of the reason is lead by

the DSCR, in LCR 5.0 advised to turn off the DSCR function.

23G switch (or RNC switch between) failed in the RNC the

border or 3G coverage boundary cell, RNC to the UE initiateDSCR

UE still from 3G original cell access (or the surrounding adjacent

cell access), when the RNC found access a repeat

user IMSI number, old user initiated release.

If 23G switch (or RNC switch between) success, UE and rapid

source cell from the switch will occur the IMSI conflict, initiated by

the release.

Whether in the then system dropped calls, you need to see

whether IU REL REQ message, if not is not counted as dropped

calls; IU REL REQ message, but the carrying value of the reason is

the normal release, does not count as a dropped call .

PCHR

CONCERN IE

SRB RLC Reset times. The path to: user log -> RRC release ->

RRC release head -> UL / DL the SRB RLC the Reset Views.

1.9 RR_ERR_RNCAP_RRC_UE_RSP_TIMEOUT

Failure error

code

RR_ERR_RNCAP_RRC_UE_RSP_TIMEOUT

437127122

Failure reasonsTimeout waiting for RRC CONN CMP news, RRC connection

establishment failure

Failure flowchart

Root due to the

Find method

CELL UPDATE similar UE has not received the RRC CONN SETUP message, also possible that the UE back to the RRC CONN CMP message, the RNC side is not received.

The signaling transport access failure by examining the

signaling channel to receive the total number of packets and the

wrong number of packages to determine the upstream, or

downstream problems.

PCHR

CONCERN IE

The uplink SIR TARGET, the total number of packets received

signaling transport channel signaling access failure / wrong number

of packages. The path to: user log -> RRC release ->exception

information -> UL SIR + signaling transport channel receiver

dropped calls, total number of packets + dropped calls before

signaling transmission channel received the wrong block number.

1.10 RR_ERR_IU_INTERFACE_RELOC_CANCELLED

Failure error

code

RR_ERR_IU_INTERFACE_RELOC_CANCELLED

437127122

Failure reasons

In the TRNC side, the core network IU REL CMD message received

in the process of waiting for Ue response, including reasons for

value CANCELL this case most SRNCBecause some exceptions

sent to the CN the RELOC CANCELLmessage

Failure flowchartno

Root due to the

Find method

　

Since the actual cause of the error occurred in the SRNC,the need

to by IMSI match view the log corresponding SRNC to confirm the

specific reasons.

PCHR

CONCERN IE　

1.11 RR_ERR_IU_INTERFACE_FAIL_IN_RADIO_INTERF_PROC

Failure error

code

RR_ERR_IU_INTERFACE_FAIL_IN_RADIO_INTERF_PROC

436930539

Failure reasonsUsually during the migration process, DRNC side response timeout

waiting empty core network notification SRNC side migration failed.

Failure flowchartno

Root due to the

Find method

SRNC side check whether the air interface signaling successfully

issued. The quality of the the DRNC side check the uplink, whether

received uplink Reconfiguration Complete message. Check method

reference 1.4 Error code processing method.

PCHR

CONCERN IE

The DRNC side UL wrong package, SRNC side RLCretransmission

rate. The path to: user log -> RRC release ->exception information -

> dropped calls SRB2 RLC downlink retransmission rate + total

number of packets dropped call signaling transport channel

receiver + dropped call signaling transport channel received the

wrong number of blocks.

1.12 RR_ERR_RNCAP_RELOC_PHY_CH_RECFG_CMP_TIMEOUT

Failure error

code

　RR_ERR_RNCAP_RELOC_PHY_CH_RECFG_CMP_TIMEOUT

437127139

Failure reasonsThe DRNC side of the waiting empty response timeout, notice the

release of the core network IU link

Failure flowchart no

Root due to the

Find method

SRNC side check whether the air interface signaling successfully

issued. The quality of the the DRNC side check the uplink, whether

received uplink Reconfiguration Complete message. Check method

reference 1.4 Error code processing method.

PCHR

CONCERN IE

The DRNC side UL wrong package, SRNC side RLCretransmission

rate. Path: user log -> RRC release ->Exceptions -> SRB2

RLC downlink retransmission rate + dropped calls dropped calls

before signaling transport channel receives the total number of

packets + dropped calls before signaling transmission channel

received the wrong number of blocks .

1.13 RR_ERR_IU_INTERFACE_UNSPECIFIED_FAIL

Failure error

code

RR_ERR_IU_INTERFACE_UNSPECIFIED_FAIL

436930640

Failure reasons

The under hair IU REL CMD message 1.CN release cause

valueUNSPECIFIED_FAIL

The migration process, DRNC to the SRNC back migration

failed because the value UNSPECIFIED_FAIL

UNSPECIFIED_FAIL

Failure flowchart no

Root due to the 1, View forward pass the message carries the release cause;

Find method

2, the DRNC migration ready error occurred, but the cause of

the error is not classified, by IMSI match the specific reason for the

failure in the view the DRNC side of thePCHR.

PCHR

CONCERN IE　

1.14 RR_ERR_IU_INTERFACE_TIMER_RELOC_CMP_EXPIRY

Failure error

code

RR_ERR_IU_INTERFACE_TIMER_RELOC_CMP_EXPIRY

436930529

Failure reasons

CS disparate systems switch received the news of the IU RELEASE

CMD of the core network, because the value

IU_TRELOCCOMPLETE_EXPIRY

Failure flowchartno

Root due to the

Find method

The possible core network does not receive disparate systems side

the RELOC COMPELETE message timeout after the release

of IU links. Need to see CN log, DRNC side log / BSCside of the log.

PCHR

CONCERN IE　

1.15 RR_ERR_RNCAP_RL_CAUSE_NODEB_TIMEOUT

Failure error

code

RR_ERR_RNCAP_RL_CAUSE_NODEB_TIMEOUT

436996049

Failure reasonsThe IUB mouth waiting the RL to establish

or RLRECONFIGURATION response timeout

Failure flowchartno

Root due to the

Find method

NODE B greater probability of failure, the need to view theNODE B

the ROSA log / CHR log for further analysis.

PCHR

CONCERN IE　

1.16 RR_ERR_IUB_INTERFACE_CAUSE_RADIO_NW_UNSPECIFIED

Failure error

code

　RR_ERR_IUB_INTERFACE_CAUSE_RADIO_NW_UNSPECIFIED

436996065

Failure

reasons

RL establish or re-equipped, NODE B back to RL SETUP /

RECFG FAIL, because the value IUB_UNSPEC_CAUSE_RADIO_NW

Failure

flowchart

no

Root due to

the Find

method

NODE B greater probability of failure, the need to view theNODE B

the ROSA log / CHR log for further analysis.

PCHR

CONCERN IE　

1.17 RR_ERR_UU_INTERFACE_INVALID_CFG_ERR_NULL_TYPE

Failure error

code

　RR_ERR_UU_INTERFACE_INVALID_CFG_ERR_NULL_TYPE

437127179

Failure reasonsUE returns UU mouth configuration failure message, the reason

is INVALID CONFIGURATION

Failure flowchart

Root due to the

Find method

　

View the signaling process configuration empty message UEdoes

not support, may be related to the configuration state of

the UE, version information and business types. Can view

the UE and the core network of the NAS message interaction, but

also to find the terminal type of IMEI

PCHR

CONCERN IEThe IMEI terminal type

1.18 NBM_CRA_CELL_RR_CRM_FAIL

Failure error

code

NBM_CRA_CELL_RR_CRM_FAIL

420349909

Failure reasonsDistrict resource access failure or failure of IUB bandwidth

application

Failure flowchart no

Root due to the

Find method

Check the cell log (time slot and code resources) to confirm whether

the code was lack of resources

PCHR

CONCERN IE

The carrier idle RU cell log information, paths: district Logs -> cell -

> Carrier -> R4/HSPA users. And

1.19 RR_ERR_RNCAP_RB_CU_OVERLAP_BACK

Failure error

code

RR_ERR_RNCAP_RB_CU_OVERLAP_BACK

437127148

Failure reasonsThe RB setup or reconfigurable cell update message is received

when the wait for a response

Failure flowchart

Root due to the

Find method

The reasons this happens with empty response timeout

similar.The Find Reference 1.4.

PCHR

CONCERN IE

1.20 RR_ERR_RNCAP_RRC_MAIN_ABNORMAL_ERR

Failure error

code

RR_ERR_RNCAP_RRC_MAIN_ABNORMAL_ERR

436602845

Failure reasonsReceive process exception error message usually wait for

theAL establishing, leading the AL creation failed

Failure flowchart

no

Root due to the

Find method

　

This usually is the the L2 error code L2 instances of failure to

establish cause, you can check the record. If this type of error

occurs, submitted in the PR platform (www.support.td-tech.com) the

RNC Technology Consulting single details refer to Overview section.

PCHR

CONCERN IE

L2 causes values encoded path to: user log -> RAB or RRCrelease

information -> exception information -> L2 Abnormal values

encoded.

1.21 RR_ERR_IUB_INTERFACE_REQUESTED_CONFIGURATION_NOT_SUPPORTED

Failure error

code

RR_ERR_IUB_INTERFACE_REQUESTED_CONFIGURATION_NO

T_SUPPORTED

436996060

Failure reasonsRL establish or re-configuration process, NODE B returns the

requested configuration is not supported.

Failure flowchart

Root due to the

Find method

　

NODE B fault and configuration errors likely View NODE

B related ROSAlog / CHR log for further analysis.

PCHR

CONCERN IE　

1.22 RR_ERR_RNCAP_HHO_PHYCH_RECFG_TIMEOUT

Failure error

code

RR_ERR_RNCAP_HHO_PHYCH_RECFG_TIMEOUT

437127127

Failure reasonsSwitching process hollow mouth physical channel reconfiguration

message response timeout waiting for empty

Failure flowchart

Root due to the

Find method

This situation is typical RB reconfiguration response Timeout

similar. Check the switch fails before the RLC retransmission rate, to

determine whether the downstream problems.

Check the switch failed before the target cell signaling transport

channel of the total number of packets received and the number of

error packets, judgment whether uplink.

According to the type of switch (the same frequency /different

frequency), and reported a measurement report, it is judged whether

it is due to the same frequency interference or override causes

PCHR

CONCERN IE

Switch fails before the RLC retransmission rate, the total number of

packets received before the target cell signaling transport channel

switching failure and the wrong number of

packages. Path: PCHR users log -> system and system switch -

>exception information -> the wrong number of packets received

before the failure of the SRB RLC retransmission rate and switching

signaling transport channel and the total number of packets.

1.23 RR_ERR_UU_INTERFACE_PH_CH_FAIL_ERR_NULL_TYPE

Failure error

code

RR_ERR_UU_INTERFACE_PH_CH_FAIL_ERR_NULL_TYPE

437127156

Failure reasonsSwitching process hollow mouth to receive the physical channel

failure message message due to PHY_CH_FAIL.

Failure flowchart

Root due to the

Find method

This case Usually for UE new configuration activation in the

new cell synchronization failure, poor quality of the new cell

empty, the UE can not do uplink synchronization also likely is the

cell synchronization channel configuration problems, cell

synchronization letter Road (UpPCH can be checked / FPACH) is

configured properly. Or the ISCPinterference checking UpPTS.

Is also possible that the dedicated channel is a downlink

synchronization problems.

PCHR

CONCERN IE

The cell log UPPCHR ISCP values path is: plot log -> cell ->

UPPCH ISCP.

1.24 RR_ERR_IU_INTERFACE_NO_RSRC_AVAIL

Failure error

code

RR_ERR_IU_INTERFACE_NO_RSRC_AVAIL

436930639

Failure reasons

SRNC initiated migration prepare failure message is received after

the migration of the core network ready, because the the DRNC side

does not have the resources.Possible reasons: no

available license; unable to obtain theCCB table.

Failure flowchartno

Root due to the

Find method

Check the the DRNC side PCHR log, see if the user is denied due to

the code resource issues or the number of users limit migration into.

PCHR

CONCERN IE

The DRNC side corresponding to user error. The path to: user log ->

the RAB information / RRC release -> exception error code.

1.25 RR_ERR_RNCAP_ALCFG_IU_AAL2_FAILURE

Failure error

codeRR_ERR_RNCAP_ALCFG_IU_AAL2_FAILURE

Failure reasonsIu interface ATM configuration, the Iu interface board

instructions AL carrying abnormal release since Rab release

Failure flowchartno

Root due to the

Find method

Check the the RNC alarm information, to see if abnormal

alarm Iu interface board.

PCHR

CONCERN IE　

1.26 RR_ERR_RNCAP_ALCFG_IUB_AAL2_FAILURE

Failure error

codeRR_ERR_RNCAP_ALCFG_IUB_AAL2_FAILURE

Failure reasonsIub mouth ATM configuration, As the Iub interface board

instructions AL carrying abnormal cause Rab release

Failure flowchartno

Root due to the

Find method

Check the RNC alarm information, to see if there are abnormal

alarm Iub interface board

PCHR

CONCERN IE　

1.27 RR_ERR_IUB_INTERFACE_TRANSP_RESOURCE_UNVAILABLE

Failure error

code

　RR_ERR_IUB_INTERFACE_TRANSP_RESOURCE_UNVAILABLE

436996111

Failure

reasons

Business establishment process, the establishment of the Iubmouth

the AL bearing failure, because Iub transport resources available

Failure

flowchart

no

Root due to

the Find

method

The users check specify Iub mouth, carrying configuration(AAL2PATH

(ATM configuration) IPPATH (IP configuration)), see if available

PCHR

CONCERN IE　

1.28 L2ERR_FPMDC_TR_SYN_NO_RESPONSE_AFTER_MAX_RETRY

Failure error

code

　L2ERR_FPMDC_TR_SYN_NO_RESPONSE_AFTER_MAX_RETRY

Failure

reasons

Failed the Iub port synchronous transmission channel, why is not

received NodeB response

Failure

flowchart

no

Root due to

the Find

method

NODE B received transmission synchronization request will back the

response, such failures are out in the transmission itself. RNC and

NodeB transmission channel on both sides need to check the

synchronization-related settings.

PCHR

CONCERN

IE

　

1.29 RR_ERR_UU_IRCFC_PROTCL_ERROR_ERR_BEGIN

Failure error

code

RR_ERR_UU_IRCFC_PROTCL_ERROR_ERR_BEGIN~RR_ERR_UU_IR

CFC_PROTCL_ERROR_ERR_END

Failure

reasons

PS domain inter-system handover failure because the UE sends

HANDOVER FROM UTRAN FAILURE, the reasons value is one of the

following:

Configuration unacceptable,

physical channel failure,

protocol error,

unspecified

Failure

flowchart

无

Root due to

the Find

method

If the reason the majority of the "physical channel failure", are generally

in 23G edge, empty of poor quality, or 2G cell congestion and other

reasons;

For other reasons, you can view the protocol version supported by the UE,

UE whether to support inter-system handover. Contact terminal

manufacturers to solve.

PCHR

CONCERN IE　

1.30 RR_ERR_UU_IRHFC_PROTCL_ERR_BEGIN

Failure error

code

RR_ERR_UU_IRCFC_PROTCL_ERROR_ERR_BEGIN　

~RR_ERR_UU_IRCFC_PROTCL_ERROR_ERR_END

Failure reasons

PS domain inter-system handover failure because the UE sends

HANDOVER FROM UTRAN FAILURE, the reasons value is one of

the following:

Configuration unacceptable,

physical channel failure,

protocol error,

unspecified

Failure flowchartno

Root due to the

Find method

If the reason the majority of the "physical channel failure", are

generally in 23G edge, empty of poor quality, or 2G cell congestion

and other reasons;

For other reasons, you can view the protocol version supported by

the UE, UE whether to support inter-system handover. Contact

terminal manufacturers to solve.

PCHR

CONCERN IE　

1.31 RR_ERR_IU_INTERFACE_REL_DUE_TO_UE_GEN_SIG_CONN_REL

Failure error

code

RR_ERR_IU_INTERFACE_REL_DUE_TO_UE_GEN_SIG_CONN_

REL

436930565

Failure reasonsDue to the small amount of data of the UE in a period of time

caused by the IU port release

Failure flowchartno

Root due to the

Find method

View UE whether there is still pass.

PCHR

CONCERN IE　

1.32 RR_ERR_IU_INTERFACE_OM_INTERVENTION

Failure error

code

RR_ERR_IU_INTERFACE_OM_INTERVENTION

436930638

Failure reasons OM干预造成的 IU口释放

Failure flowchart no

Root due to the

Find method

OM intervention caused the IU mouth release

PCHR

CONCERN IE　

1.33 RR_ERR_IU_INTERFACE_REQUESTED_INFO_NOT_AVAIL

Failure error RR_ERR_IU_INTERFACE_REQUESTED_INFO_NOT_AVAIL

code 436930567

Failure reasons

Migrated out ready to fail, the reason for the failure occurred when

applying for district resources: NBM_CRA_CELL_RR_FAIL/

NBM_CRA_CELL_CONGEST/ NBM_CRA_CELL_UNAVAIL

Failure flowchartno

Root due to the

Find method

The specific reason for the failure of the target RNC / target system

side

PCHR

CONCERN IE　

1.34 RR_ERR_IU_INTERFACE_UNKNOWN_TARGET_RNC

Failure error

code

RR_ERR_IU_INTERFACE_UNKNOWN_TARGET_RNC

436930534

Failure reasons

RNC RELOCATION REQUIRED message is sent to the CN, CN

returned RELOCATION PREPARATION FAILURE message, the

message with the cause value: unknown target RNC

Failure flowchartno

Root due to the

Find method

See RNC RELOCATION REQUIRED message with information of

the target RNC is sent to the CN is correct

PCHR

CONCERN IE　

1.35 RR_ERR_IU_INTERFACE_RELOC_FAIL_IN_TARGET_CN_RNC_OR_TARGET_SYS

Failure error

code

RR_ERR_IU_INTERFACE_RELOC_FAIL_IN_TARGET_CN_RNC_

OR_TARGET_SYS

436930554

Failure reasons Side of the target RNC or target system UNSPECIFIED causes of

migration failures, IU mouth because the value of fill for

RR_ERR_IU_INTERFACE_RELOC_FAIL_IN_TARGET_CN_RNC_

OR_TARGET_SYS

Failure flowchartno

Root due to the

Find method

View the specific cause of the target RNC or target system side

PCHR

CONCERN IE　

1.36 NBM_CRA_CELL_RR_FAIL

Failure error

code

NBM_CRA_CELL_RR_FAIL

420382676

Failure reasonsUE requests access code resource allocation module returns a

failure, the RNC internal might again try to access.

Failure flowchartno

Root due to the

Find method

Appear this error code may have the following reasons: 1

parameter error, null pointer process anomalies; 2 carrier frequency

code division failed.

PCHR

CONCERN IE　

1.37 NBM_IUB_RESET

Failure error

code

NBM_IUB_RESET

420579281

Failure reasons The IUB interface reset occurred.

Failure flowchartno

Root due to the If NBM_IUB_RESET, then the reasons: 1 Delete port; 2 NODE B

Find method has reset release users; the IUB link may flash.

PCHR

CONCERN IE　

1.38 RR_ERR_RNCAP_CU_CELLFACH_NOT_FIND_PROC

Failure error

codeRR_ERR_RNCAP_CU_CELLFACH_NOT_FIND_PROC

Failure reasonsFACH state received cell update can not handle cell update is

discarded waiting for UE redo cell update.

Failure flowchartno

Root due to the

Find method

Need to troubleshoot access cell status is normal, the the access

cell load condition is serious and may cause serious lack of code

resources to the reasons for the failure.

PCHR

CONCERN IE