Embed Size (px)
Citation preview
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
UE RNC CN
IU RELEASE REQ
(Radio Connection With UE Lost)
RRC CELL UPDATE
(signalling rlc unrecovrable err)
IU RELEASE COMMAND
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
UE RNC CN
IU RELEASE REQ
(Radio Connection With UE Lost)
RRC CELL UPDATE
(Traffic rlc unrecovrable err)
IU RELEASE COMMAND
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 reasons Received the the NODE B reported the RL FAILURE IND, uplink
radio link synchronization fails
Failure flowchart
NODEB RNC CN
IU RELEASE REQ
NBAP_RL_FAILURE_IND
IU RELEASE COMMAND
Wat RL restore
tmeout
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 reasons DCCC, business release / build process release Ue not
returnRB Reconfiguration Complete message
Failure flowchart
RNC CN
IU RELEASE REQ
(Failure in the Radio Interface)
Radio bear reconfig/
Phy channel reconfig
UE
Uu Interface
Timeout
IU RELEASE COMMAND
IU RELEASE COMPLETE
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 reasons Configured response timeout waiting for empty cell update
procedure RNC issued CELL UPDATE CONFIRM
Failure flowchart
RNC CN
IU RELEASE REQ
(Failure in the Radio Interface)
Cell Update Confirm(Rb
Recfg/Ph Recfg)
UE
Uu Interface
Timeout
IU RELEASE COMMAND
Cell Update
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 reasons N ODE B initiated the IUB mouth AAL 2 release, trigger business
release
Failure flowchart
NODEB RNC CN
IU RELEASE REQ
NBAP_RL_FAILURE_IND
IU RELEASE COMMAND
QAAL2_RELEASE_REQ
AAL2
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 flowchart No
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
UE RNC CN
Rrc Conn Req(Same IMSI
Relocation Required
Relocation Prepare failure
Rrc Conn Rel
(Redirect signal conn req)
Common ID(Same IMSI
Iu Release Req
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 reasons Timeout waiting for RRC CONN CMP news, RRC connection
establishment failure
Failure flowchart
RNC CN
RRC CONN SETUP
UE
Uu Interface
Timeout
RRC CONN REQ
Rel Rrc Resource
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.
