How to identify the IuB congestion

Step 1:
We should check 10 counters, get the total times of RRC/ RAB setup failure due to IuB
congestion.
If they are "0", it means no IuB congestion.
If they are not "0", it means maybe there is IuB congestion, go to step 2.
VS.RRC.Rej.ULIUBBandCong
VS.RRC.Rej.DLIUBBandCong
VS.RAB.FailEstab.CS.DLIUBBand.Cong
VS.RAB.FailEstab.CS.ULIUBBand.Cong
VS.RAB.FailEstab.PS.DLIUBBand.Cong
VS.RAB.FailEstab.PS.ULIUBBand.Cong
VS.RAC.SHO.Fail.ULIub.Cong
VS.RAC.SHO.Fail.DLIub.Cong
VS.RAC.HHO.Fail.ULIub.Cong
VS.RAC.HHO.Fail.DLIub.Cong

Step 2:
Check the alarm.
Sometimes the IuB congestion due to E1 down or E1 with problem (the available IuB
resource less then nominal IuB resource).
If there is alarm for IuB/ E1, let RAN engineer clean the alarm and identify whether the alarm
impact the available IuB resource or not.
If there is not alarm for IuB/ E1 or the alarm does not impact the available IuB resource, go to
step 3.

Step 3:
Check the IuB Utilizing Ratio and configuration of IuB between RNC and NodeB.
If IuB Utilizing Ratio is low and total times of RRC/ RAB setup failure due to IuB congestion is
high, we need check the configuration of IuB between RNC and NodeB.
Sometimes RAN engineer set the wrong configuration of IuB between RNC and NodeB.
For example:
PATHID/ VPI/ VCI/ TXTRFX/ RXTRFX and other parameter is wrong or missing, then path
is not available or the available IuB resource less then nominal IuB resource.
In different project, we met the wrong configuration of IuB between RNC and NodeB
many times.
You need check the configuration of IuB between RNC and NodeB if IuB Utilizing Ratio
less then 50%.
If IuB Utilizing Ratio is high and total times of RRC/ RAB setup failure due to IuB congestion is
high, the configuration of IuB between RNC and NodeB is right, it is IuB congestion.
Formula of IuB Utilizing Ratio:
 [(VS.ATMUlAvgUsed.1+VS.ATMUlAvgUsed.2+
VS.ATMUlAvgUsed.3+VS.ATMUlAvgUsed.4+
IUB
VS.IPUlAvgUsed.1+VS.IPUlAvgUsed.2+
Bandwidth
VS.IPUlAvgUsed.3+
Utilizing
VS.IPUlAvgUsed.4)/
Ratio (UL)
(VS.ATMUlTotal.1+
VS.ATMUlTotal.2+VS.ATMUlTotal.3+VS.ATMUlTotal.4+VS.IPUlTotal.1+VS.IPUlTotal.2+VS.IPUlTotal.3+VS.I
IUB
Bandwidth
[(VS.ATMDLAvgUsed.1+VS.ATMDLAvgUsed.2+VS.ATMDLAvgUsed.3+VS.ATMDLAvgUsed.4+VS.IPDLAvgU
Utilizing
Ratio (DL)

How to reduce the IuB congestion by changing factor

The risk:
It impacts the throughput rate of single user, impacts the feeling of user, so we need fall
back it after IuB expand is finished.

I use BSC6810V200R011C00SPC100SPC130 as sample, the parameter maybe is different in

other RNC version:

Step 1:
Add a new FTI, the new FTI with lower factor. You can add different FTI for different factor:
For example :
ADD TRMFACTOR: FTI=26, REMARK="60% factor", PSINTERDL=60, PSINTERUL=60,
PSBKGDL=60, PSBKGUL=60, HDINTERDL=60, HDBKGDL=60;
ADD TRMFACTOR: FTI=27, REMARK="50% HSDPA factor", HDINTERDL=50,
HDBKGDL=50;
ADD TRMFACTOR: FTI=28, REMARK="40% UL factor and 50% DL factor", PSINTERDL=50,
PSINTERUL=40, PSBKGDL=50, PSBKGUL=40, HDINTERDL=50, HDBKGDL=50;
ADD TRMFACTOR: FTI=29, REMARK="30% DL factor", PSINTERDL=30, PSBKGDL=30,
HDINTERDL=30, HDBKGDL=30;
ADD TRMFACTOR: FTI=30, REMARK="50% R99 factor and 30% HSDPA factor",
PSINTERDL=50, PSINTERUL=50, PSBKGDL=50, PSBKGUL=50, HDINTERDL=30,
HDBKGDL=30;
and so on.
Remark:
1.The new FTI should different with the current FTI, you can execute the command "LST
TRMFACTOR" or query the CFGMML to get the current FTI.
For example, the current FTI
FTI REMARK
1 "FOR IUCS ATM"
2 "FOR IUCS IP"
3 "IUPS_IP"
4 "FOR IUB ATM"
6 "FOR IUR"
23 "IUB Cong DLUL"
24 "IUB Cong DLUL_1"
25 "IuB_Cong_Modify_TRM"
2.In the command, you can set different factor for different service.
For example
If DL IuB congestion is high but UL IuB congestion is very low or "0", you can modify factor for
DL only
If HSDPA user much more than R99 user, you can only change the factor for HSDPA.

Step 2:
Check the ANI for high IuB congestion NodeB
You can execute the command "LST ADJNODE" or query the CFGMML to get it.
For example, you can find ANI ID for target NodeB as below:
ANI NAME NODET
105 "NEWARMADARLKMW" IUB

Step 3:
Modify the FTI for the target NodeB which with high IuB congestion, use the new FTI which
with lower factor, execute the command
MOD ADJMAP: ANI=105, ITFT=IUB, TRANST=ATM_IP, CNMNGMODE=SHARE, FTI=27;
Remark:
1. "ITFT", "TRANST", "CNMNGMODE" should as same as before, only modify the FTI
2. If you want to modify the factor for some NodeBs, add a new FTI with new factor, do not
modify the existing FTI (Do not impact to other sites)
3. Modify the factor step by step. For example, the initial factor is 70%, you can modify it to
60% then monitor.
If can not solve the problem, modify it to 50%, then 40%, and so on.

Fallback

After IuB expand is finished, fallback the initial FTI which with initial factor for the target
NodeB.