RRC REJECTION AND

RAB FAILURE
Suly, Dec 9, 2015
RRC Rejection/Failure
RRC Setup Call Flow
RRC Rejection during Admission Control Procedure
Counters :
VS.RRC.Rej.ULIUBBand.Cong
VS.RRC.Rej.ULPower.Cong
VS.RRC.Rej.DLPower.Cong
VS.RRC.Rej.DLIUBBand.Cong
VS.RRC.Rej.ULCE.Cong
VS.RRC.Rej.DLCE.Cong
VS.RRC.Rej.Code.Cong
The measurement is triggered at point A.
After receiving RRC CONNECTION REQUEST from UE, RNC
initiates admission procedures for resources of code, power, CE,
and Iub bandwidth.
If admission fails, RNC sends a RRC CONNECTION REJECT
message to UE. The corresponding counter is measured
according to the reject reason in the cell where the UE is located.
If congestion occurs on both the uplink and downlink, only the
related downlink counter is measured.
RRC Rejection during Radio Link Setup
Counter : VS.RRC.Rej.NodeBResUnavail
It is the number of RRC Connection Rejects Due to NodeB
Resource Unavailable
The measurement is triggered at point B.
When RNC receives a RRC CONNECTION REQUEST from
UE, RNC starts a radio link setup procedure.
After receiving a RADIO LINK SETUP FAIL with the cause of NodeB
Resources Unavailable, RNC sends a RRC CONNECTION REJECT to
UE with cause value is congestion.
RRC Rejection during Radio Link Setup
Counter : VS.RRC.Rej.RL.Fail
Meaning : number of RRC Connection Rejects Due to Radio
Link Setup Failure for Cell.
Case 1 :
The measurement triggered at point B.
When RNC receives a RRC CONNECTION REQUEST message from the
UE, the RNC starts a radio link setup procedure. After receiving a RADIO
LINK SETUP FAIL from NodeB, RNC sends a RRC CONNECTION
REJECT message to the UE (with the cause is not CE resource
insufficiency)
Case 2
The measurement triggered at point B.
In this case, the RNC fails to receive a RADIO LINK SETUP RESPONSE
message from NodeB before the timer expires. Then RNC sends RRC
CONNECTION REJECT to UE.
Note : Timer set using SET UIDLEMODETIMER
T300 = 2000ms
N300 = 3
RRC Rejection during Transport Setup
Counter : VS.RRC.Rej.TNL.Fail
This counter is only for ATM Transport
RRC Rejection during RRC Connection Setup
Counter : VS.RRC.FailConnEstab.NoReply
The measurement is triggered at point A.
If the RNC fails to receive a RRC CONNECT SETUP
COMPLETE from UE before the timer expires after the
RNC sends RRC CONNECT SETUP.
Note : Timer set using SET UCONNMODETIMER
RRC Connection Setup can be resend 1x (N381=2)
Timer T381 (600ms)
RAB Setup Failure
 The CN initiates the radio access
bearer setup procedure by sending
RAB ASSIGNMENT REQUEST
message to the RNC.
After receiving RAB ASSIGNMENT
REQUEST message, the RNC
allocates resources, and performs
admission control.
If admission of the RAB succeeds,
the next steps are :
Iu transport connection setup procedure,
Iub radio bearer setup procedure
Uu radio bearer setup procedure.

At last, RNC sends RAB ASSNMENT

RESPONSE, indicating whether the
RAB setup is successful.
RABs Unsuccessfully Established due to Congestion
Counters :
VS.RAB.FailEstabCS.Cong
VS.RAB.FailEstabCS.DLIUBBand.Cong
VS.RAB.FailEstabCS.ULIUBBand.Cong
VS.RAB.FailEstabCS.ULCE.Cong
VS.RAB.FailEstabCS.DLCE.Cong
VS.RAB.FailEstabCS.Code.Cong
VS.RAB.FailEstabCS.ULPower.Cong
VS.RAB.FailEstabCS.DLPower.Cong
VS.RAB.FailEstabCS.DLIUCSBand.Cong
VS.RAB.FailEstabCS.ULIUCSBand.Cong
If congestion occurs both in uplink and downlink, these
counters are measured only in the downlink.
The measurement is triggered at point B.
The RNC measures this counter in the best cell for the
UE.
RABs Unsuccessfully Established During Iu Transport Bearer Setup
Counter : VS.RAB.FailEstabCS.TNL
This counter is only used for ATM transport
RABs Unsuccessfully Established During Radio Link Setup
Counter : VS.RAB.FailEstabCS.IubFail
This counter is measured in the best cell that UE camps on.
In all cases, the counter is triggered at point B.
Case 1 :
The RNC receives RADIO LINK RECONFIGURATION FAILURE.
Note if the radio link configuration fails due to CE resource insufficiency, this
counter is not measured.
Case 2 :
The timer is expired while RNC waiting for RADIO LINK RECONFIGURATION
READY. (Set UESTATETIMER:RlRecfgReadyTmr=5000ms)
Case 3 :
After RNC sends RADIO LINK RECONFIGURATION COMMIT and then
receives RADIO LINK FAILURE INDICATION from NodeB, the RNC starts a
timer to wait for a RADIO LINK RESTORE INDICATION.
(Set UESTATETIMER:RlRstrTmr=11000ms)
RABs Unsuccessfully Established During Radio Link Setup
Counter :
VS.RAB.FailEstabCS.NodeBULCE.Cong
VS.RAB.FailEstabCS.NodeBDLCE.Cong
The measurement is triggered at point B.
If RNC receives an RL reconfiguration failure message
(or RL establishment failure message) with cause value
indicating uplink or downlink CE congestion, the RNC
sends a RAB ASSIGNMENT RESPONSE and the RAB
setup fails.
RABs Unsuccessfully Established During Iub Transport Bearer Setup
Counter : VS.RAB.FailEstabCS.IubAAL2Fail
This counter is only for ATM transport
RABs Unsuccessfully Established During Radio Bearer Setup
Counter :
VS.RAB.FailEstabCS.UuFail : due to UE configuration failures (no
response received from UE or UE sends a RADIO BEARER SETUP
FAILURE message) on Uu interface during RB setup procedure.
Subcounter of VS.RAB.FailEstabCS.UuFail
VS.RAB.FailEstabCS.RBIncCfg: due to invalid configuration of UE during
the RB Setup Procedure (first call flow)
VS.RAB.FailEstabCS.RBCfgUnsup: due to configuration unsupported of
UE During the RB Setup Procedure (first call flow)
VS.RAB.FailEstabCS.PhyChFail: due to physical channel failure of UE
during the RB Setup Procedure (first call flow)
VS.RAB.FailEstabCS.UuNoReply (second call flow): due to no reply
during the RB Setup Procedure. RAB setup fails because the timer for
the RNC to wait for the RADIO BEARER SETUP COMPLETE message
from the UE expires during the RB setup procedure.
(USTATETIMER:RbSetupRspTmr=15000ms)
RABs Unsuccessfully Established During Radio Bearer Setup
Counter : VS.RAB.FailEstabCS.SRBReset
The measurement is triggered at point B.
When a signaling RLC resets during the RB setup
procedure, the RNC sends the CN a RAB ASSIGNMENT
RESPONSE message, indicating that the RAB setup fails.
This counter is measured in the best cell where the UE
camps.
RABs Unsuccessfully Established During Radio Bearer Setup
Counter : VS.RAB.FailEstabCS.CellUpd
The measurement is triggered at point B.
When the RAB setup fails due to the overlap of the RB setup
and cell update procedures, the RNC sends the CN a RAB
ASSIGNMENT RESPONSE message with a cause value of
"Failure in the Radio Interface Procedure".
This counter is measured in the best cell where UE camps.
Optimization
General
The following can cause all kind of failure and kpi degradation (RRC Setup Failure, RAB Setup
failure, Drop Call, Handover Failure, Low throughput, Poor voice quality) :
Network Alarms
Transmission problem : IP Ping Mean Lost Statistics, IP Clock Alarms, Reference Clock Alarms, SCTP Alarms, etc,
are indication of transmission alarms
Problem on antenna : Antenna device broken, Imperfect connection, high VSWR, Passive Intermodulation, high
RTWP
Availability problem : cells or surrounding cells are down
External interference : usually causing high RTWP at several cells at one area.
Cell coverage overshoot (based on drive test or TP statistics) : Cell overshoot may cause poor quality and pilot
pollution
Missing Neighbor
Poor coverage
Pilot pollution / low EcNo
Code Congestions
Check whether code triggered LDR is activated (LST UCELLALGOSWITCH)
(Look for CELL_CODE_LDR::ON or CELL_CODE_LDR-1)
(As an example, please see on below embedded file dsp_ucellcac.txt)
Consider downtilt or reduce PCPICH Power if overshooting
Consider downtilt the congested cells, and uptilt the nearest cell to take over the load
Check whether U2100 and U900 are balance. If not balance, check the downtilt or set easier reselection to lighter cell :
MOD UINTERFREQNCELL:RncId=301, CellId=34341, Ncellrncid=301, Ncellid=34344, IdleQoffset2sn=-3; (34344 has lighter load)
MOD UINTERFREQNCELL:RncId=301, CellId=34344, Ncellrncid=301, Ncellid=34341, IdleQoffset2sn=3; (34344 has lighter load)
MOD UCELLSELRESEL:CellId=34341, IdleSintersearch=6; (when UE camp on 34341, easier reselection to 34344/U2100)

Consider change the Minimum Code Reserved for HSDPA from 5 to 3 or to 1 (LST/MOD UCELLHSDPA)
This is very effective, as reducing 1 HSPDSCH code mean adding 16 code SF256
Impact : low throughput during busy hours)
Consider for more aggressive LDR Actions (LST UCELLLDR to see current setting on RNC)
Change DLLDRBERATEREDUCTIONRABNUM and MAXUSERNUMCODEADJ from 1 to 3, using MOD UCELLLDR command
Consider to trigger the LDR state earlier by changing the threshold CellLdrSfResThd from SF8 to SF4 (MOD
UCELLLDR)
UL/DL CE Congestions
Check cell credit triggered LDR is activated (LST UCELLALGOSWITCH)
(Look for CELL_CREDIT_LDR::ON or CELL_CREDIT_LDR-1)
Check for WBBP board alarms or license missing
Check the license (Node B Command DSP License, or from M2000 Software Management/NE License/Node B)
Consider downtilt or reduce PCPICH Power if overshooting
Consider downtilt the congested cells, and uptilt the nearest cell to take the loda
Propose license upgrade if node B license is too few, or at area with busy traffic
Enable Node-B LDR algorithm :
MOD UNODEBALGOPARA: NodeBName="nodeb1", NodeBLdcAlgoSwitch=NODEB_CREDIT_LDR-1;
Consider for more aggressive LDR Actions (Change DLLDRBERATEREDUCTIONRABNUM or
ULLDRBERATEREDUCTIONRABNUM from 1 to 3)
For UL : Consider to trigger the LDR state earlier by changing the threshold ULLDRCREDITSFRESTHD from SF8 to
SF4 (MOD:UCELLLDR)
For DL : Consider to trigger the LDR state earlier by changing the threshold DLLDRCREDITSFRESTHD from SF8 to
SF4 (MOD:UCELLLDR)
For UL : Change ULTTICREDITSFRESTHD from SF8 to 4SF4
(MOD UCELLLDR and MOD UNODEBLDR)
HSDPA User Congestions
Consider downtilt or reduce PCPICH Power if overshooting
Consider downtilt the congested cells, and uptilt the nearest cell to take over the load
Check whether U2100 and U900 are balance. If not balance, check the downtilt or set easier reselection
to lighter cell :
MOD UINTERFREQNCELL:RncId=301, CellId=34341, Ncellrncid=301, Ncellid=34344, IdleQoffset2sn=-3; (34344 has lighter load)
MOD UINTERFREQNCELL:RncId=301, CellId=34344, Ncellrncid=301, Ncellid=34341, IdleQoffset2sn=3; (34344 has lighter load)
MOD UCELLSELRESEL:CellId=34341, IdleSintersearch=6; (when UE camp on 34341, easier reselection to 34344/U2100)
Check for user number counters : VS.HSDPA.UE.Mean.Cell, VS.HSDPA.UE.Max.Cell
Check parameter using LST UCELLCAC for MAXHSDPAUSERNUM
If the counters number is high, change the MAXHSDPAUSERNUM from 64 to 96 (MOD UCELLCAC)
HSUPA User Congestions
Consider downtilt or reduce PCPICH Power if overshooting
Consider downtilt the congested cells, and uptilt the nearest cell to take over the load
Check whether U2100 and U900 are balance. If not balance, check the downtilt or set easier reselection
to lighter cell :
MOD UINTERFREQNCELL:RncId=301, CellId=34341, Ncellrncid=301, Ncellid=34344, IdleQoffset2sn=-3; (34344 has lighter load)
MOD UINTERFREQNCELL:RncId=301, CellId=34344, Ncellrncid=301, Ncellid=34341, IdleQoffset2sn=3; (34344 has lighter load)
MOD UCELLSELRESEL:CellId=34341, IdleSintersearch=6; (when UE camp on 34341, easier reselection to 34344/U2100)
Check for user number counters : VS.HSUPA.UE.Mean.Cell and VS.HSUPA.UE.Max.Cell
Check parameter MAXHSUPAUSERNUM using LST UCELLCAC
(Look for Maximum HSUPA user number or MAXHSUPAUSERNUM)
If the counters number is high, change the MAXHSUPAUSERNUM from 20 to 40
(MOD UCELLCAC)
Following are steps to change MaxHSUPAUserNum from 20 to 40 (1 ERGCH/EHICH for every 20 HSUPA user):
1. DEA UCELLHSUPA: LOGICRNCID=xxx, CELLID=xxxx;
2. MOD UCELLHSUPA:LOGICRNCID=xxx, CELLID=xxxx, ERGCHEHICHCODENUM=2;
3. ACT UCELLHSUPA:LOGICRNCID=xxx, CELLID=xxxx;
4. MOD UCELLCAC: LogicRNCId=xxx, CellId=xxxxx, MaxHSUPAUserNum=40;
VS.RRC.Rej.RL.Fail / VS.RAB.FailEstabCS.IubFail
If occurred at all cell, check with transmissions related alarms and ping statistics
VS.IPPOOL.ADJNODE.PING.MeanLOST and escalate to Transmission.
If occurred only in U900, reset WBBP on slot 2
If occurred only in U2100, reset WBBP on slot 1 and slot 3
VS.RRC.FailConnEstab.NoReply
VS.RAB.FailEstabCS.UuFail / .SRBReset / .CellUpd
Mostly caused by poor coverage, pilot pollution or the high RTWP.
Two possibility :
Users could not receive message from RNC
Caused by poor coverage / pilot pollution
UE already reply with RRC CONNECTION SETUP COMPLETED (on UL DCH) but not received by Node B
High RTWP/ external interference / signal from UE too weak
Therefore, the solution can be listed as follow :
Perform drive test to find poor coverage or pilot pollution
Consider increase the PCPICH Power or uptilt RET to improve coverage
In case of High RTWP, trigger easier reselection to another frequency :
MOD UINTERFREQNCELL:RncId=301, CellId=34342, Ncellrncid=301, Ncellid=34345, IdleQoffset2sn=-10; (34342 high RTWP)
MOD UINTERFREQNCELL:RncId=301, CellId=34345, Ncellrncid=301, Ncellid=34342, IdleQoffset2sn=10; (34345 RTWP is ok)
MOD UCELLSELRESEL:CellId=34342, IdleSintersearch=6; (when UE camp on 34342, easier reselection to 34345/U2100)
Only for VS.RRC.FailConnEstab.NoReply :
Increase the MaxFACHPower from 10 to 30 (MOD UFACH:CELLID=36641,TRCHID=5,MAXFACHPOWER=30;)
Appendix
Relation between CellId and WBBP

LST ULOCELL:MODE-ALLLOCALCELL will showed relationship between CellID and Baseband Equipment ID. Here U2100 using Baseband ID 0, and U900 using Baseband ID 1
LST ULOCELL:MODE=ALLLOCALCELL;
Local Cell ID Cell ID UL Baseband Equipment ID DL Baseband Equipment ID
30251 30251 1 1
30252 30252 1 1
30253 30253 1 1
30254 30254 0 0
30255 30255 0 0
30256 30256 0 0

From Command LST BASEBANDEQM, it is known that BasebandEqm-0 using WBBP in slot 1 and 3, while BasebandEqm-1 is using WBBP slot 2
LST BASEBANDEQM:BASEBANDEQMID=0,BASEBANDEQMTYPE=UL;
Cabinet No. Subrack No. Slot No.
0 0 1
0 0 3

LST BASEBANDEQM:BASEBANDEQMID=0,BASEBANDEQMTYPE=DL;
Cabinet No. Subrack No. Slot No.
0 0 1
0 0 3

LST BASEBANDEQM:BASEBANDEQMID=1,BASEBANDEQMTYPE=UL;
Cabinet No. = 0
Subrack No. = 0
Slot No. = 2

LST BASEBANDEQM:BASEBANDEQMID=1,BASEBANDEQMTYPE=DL;
Cabinet No. = 0
Subrack No. = 0
Slot No. = 2
Thank You