SOLUSI UNTUK KEMACETAN KODE

A. Ringkasan
Kode akan menyebabkan kemacetan CSSR rendah baik CS dan PS layanan.
Kita dapat memeriksa counter seperti di bawah ini untuk menemukan kemacetan
kode:
- Solusi :
Kode kemacetan akan terjadi di dalam sel pembawa tunggal atau sel F1. Jika sel
pembawa tunggal mengalami kemacetan kode yang sangat serius, memperluas 2
operator dianjurkan. Untuk mengatasi kemacetan kode, kami sarankan untuk
menggunakan algoritma LDR juga. Konfigurasi MML adalah sebagai berikut:
1. Aktifkan switch LDR:
MOD CELLALGOSWITCH: CellId = xxx, NBMLdcAlgoSwitch
CELL_CODE_LDR -1;
2. Menetapkan tindakan LDR:
MOD CELLLDR: CellId = xxx, DLLDRFIRSTACTION = CodeAdj,
DLLDRSECONDACTION= BERateRed, DlLdrBERateReductionRabNum =
3;
3. Kemudian kita bisa memantau counter sebagai berikut untuk memeriksa efek
dari LDR tindakan:
VS.LCC.LDR.BERateDL
VS.LCC.LDR.CodeAdj
VS.LCC.LDR.CodeAdj.Succ

SOLUSI UNTUK KEMACETAN POWER

A. Summary
Power congestion will cause low CSSR of both CS and PS service. We can
check counters as below to find power congestion:

VS.RRC.Rej.Power.Cong+VS.RAB.FailEstPs.Power.Cong+VS.RAB.FailEstCs.P
ower.Cong

In current version, our counter can’t differentiate whether UL or DL power

congestion. To check whether UL or DL congestion, we can first check the MeanTCP
and MeanRTWP:
1. Check the Max Tx power of the congested cell Add cellsetup:cellid=1111,
maxtxpower=430
2. Check counter VS.MeanTCP and VS.MeanTCP.NonHS and calculate the utility
ratio to check whether the utility ratio is very high.
3. Monitor the RTWP to check whether RTWP is very high. By this check then we
can know the uplink and downlink power status.
 Currently for uplink we use Equivalent Number of User to do CAC; for downlink
we use TCP to do CAC. According to our CAC strategy, first make sure some basic
parameters should be configured as follows:
ADD CELLALGOSWITCH: CellId=0,
NBMUlCacAlgoSelSwitch=ALGORITHM_SECOND,
NBMDlCacAlgoSelSwitch=ALGORITHM_FIRST;
ADD CELLCAC: CellId=0, UlTotalEqUserNum=180;

B. Solution
If the configuration is correct and power congestion still happen, we
recommend solutions as follows:
1. Uplink power congestion:
If RTWP is always very high (more than -90dBm), most probability it was
caused by uplink interference. Then first check whether interference problem,
if uplink interference problem, then solving interference is the recommended
method.
If not interference problem. We can:
For single carrier cells or F1 cells, use LDR algorithm:
Switch on the LDR switch:
MOD CELLALGOSWITCH: CellId=0, NBMLdcAlgoSwitch=UL_UU_LDR-
1;
Setting LDR action:
MOD CELLLDR: CellId=0, UlLdrFirstAction=BERateRed,
UlLdrBERateReductionRabNum=1; GoldUserLoadControlSwitch=ON;
2. Downlink power congestion:
If TCP ratio is very high, it means downlink power congestion. Then we can:
a. For single carrier cells, we can use downlink LDR:
MOD CELLALGOSWITCH: CellId=0,
NBMLdcAlgoSwitch=DL_UU_LDR-1;
MOD CELLLDR: CellId=0, DlLdrFirstAction=BERateRed,
DlLdrBERateReductionRabNum=1; GoldUserLoadControlSwitch=ON;
b. For F1 cell, Setting LDR as follows:
MOD CELLALGOSWITCH: CellId=0,
NBMLdcAlgoSwitch=DL_UU_LDR-1;
MOD CELLLDR: CellId=0, DlLdrFirstAction=BERateRed,
DlLdrSecondAction=InterFreqLDHO, DlLdrBERateReductionRabNum=1,
GoldUserLoadControlSwitch=ON;

Then we can monitor the counters as follows to check the effect of LDR
action:
VS.LCC.LDR.InterFreq
VS.LCC.LDR.BERateDL
VS.LCC.LDR.BERateUL

Note: usually
Note: usuallypower congestion
power willwill
congestion not not
happen in dual
happen carrier
in dual cell.cell.
carrier ForFor
single
single
carrier site, ifsite,
carrier power congestion
if power is serious,
congestion expand
is serious, carrier
expand is recommended.
carrier is recommended
 SOLUTION FOR IUB CONGESTION

A. Summary
IUB congestion will cause low CSSR of both CS and PS service. We can use
NodeB counters to calculate IUB utility ratio. If average utility ratio is more than 70%,
IUB expansion is recommended for this site.
B. Related counter
We can find IUB congestion by counters as below:
UL IUB congestion:
VS.RRC.Rej.ULIUBBandCong+VS.RAB.FailEstab.CS.ULIUBBand.Cong+
VS.RAB.FailEstab.PS.ULIUBBand.Cong+VS.RAC.SHO.Fail.ULIub.Cong+
VS.RAC.HHO.Fail.ULIub.Cong
DL IUB congestion:
VS.RRC.Rej.DLIUBBandCong+VS.RAB.FailEstab.CS.DLIUBBand.Cong+
VS.RAB.FailEstab.PS.DLIUBBand.Cong+VS.RAC.SHO.Fail.DLIub.Cong+
VS.RAC.HHO.Fail.DLIub.Cong
C. Solution
The best solution is to expand the IUB band. Other solutions are just temporary
methods to remain the KPI.
When IUB congestion is detected, first we need check the IUB utility ratio, if utility
ratio is very small but still congestion, it may caused by wrong transmission
configuration.
Usually we can modify the FTI of the congested NodeB. MML is as follow:
1. Find the FTI of the NodeB.
ADD ADJNODE: ANI=33, NAME="nodeB", NODET=IUB, NODEBID=1111,
TRANST=ATM;
ADD ADJMAP: ANI=33, ITFT=IUB, TRANST=ATM, CNMNGMODE=SHARE,
TMIGLD=1, TMISLV=2, TMIBRZ=1, FTI=101;
2. Change the FTI of the NodeB to 20.
MOD ADJMAP: ANI=33, ITFT=IUB, TRANST=ATM, CNMNGMODE=SHARE,
TMIGLD=1, TMISLV=2, TMIBRZ=1, FTI=20;
Note: We configured FTI=20 dedicated for relieving the IUB congestion. If after
modification still congestion, we can also new a specific FTI.
 RTWP Problem Analysis and Solution

A. Summary
High RTWP will cause low performance in CSSR and CCSR. Currently the
background noise is -106dBm, if the RTWP is higher than -95dBm then the load
factor will more than 90%, CAC will be overload congestion status. To
troubleshooting a high RTWP issue, please refer the procedure as below.
B. Analysis Procedure
1. Check Alarm
- Check the hardware alarm. Like RF Module Rx Branch RTWP Difference Too
High Alarm etc.
- Check whether VSWR alarm exists.
Command: DSP VSWR
If have alarm or high VSWR (more then 11), first escalate to BSS team, then
assistant them to check whether it is hardware problem or interference.
2. Check NodeB configuration in NodeB LMT
- Check uplink RF sensitivity
Command: DSP RFDESPARAM and DSP DESENS
Usually the value of these two parameters should be 0, if it is not 0, fallback
to 0 to check whether RTWP can restore normal.
- Check Uplink Attenuation Value
Command: LST RXATTEN
This configuration will affect the RX gain. If TMA is not used, then no need to
configure it; and if TMA is used then we should configure it as per TMA gain.
The default value is 0. (Without TMA)
- Check the intermodulation interference
If primary RTWP is very high but secondary RTWP is normal, it may be caused
by this case.
Method: suggest to shut off the transmit power then monitor the RTWP. If
RTWP become normal after transmit power is switched off and RTWP become
high when transmit power is switched on, we can suspect that it may caused by
feeder joint problem, need BSS team check the feeder connection (primary feeder).
Command to shut off the transmit power:
SET TXSW
3. Check the interference feature
- Check the RTWP trend
Check the RTWP counter VS.MeanRTWP, VS.MaxRTWP, VS.MinRTWP. Make
a chart to show the interference trend in one day.
Trace the RTWP in NodeB LMT; trace 24hours in one day and save the result to
txt format and make chart to show the primary and secondary RTWP trend in one
day.
 Through the chart, we can know the interference feature:
What time the interference happens, in day or night; in busy hour or always….
How about the consistency between primary and secondary RTWP trend?
Through the trend we can analyze whether heavy traffic causes the high RTWP;
whether external or internal interference?
- Check the site information
Check it is indoor site or outdoor site.
For indoor site, need collect the information as below:
Whether 2nd carrier is implemented or not?
Whether the combiner is used? Combiner frequency is match or not?
For outdoor site, need collect the information as below:
How many sectors experience high RTWP?
How about RTWP status of nearby sites?
Is repeater located near the site?
4. Find the interference source
- Judge external or internal interference
Disconnect the jumper (jumper at the cabinet side) from the NodeB, and then trace
the RTWP. If RTWP is still very high after disconnection, that means NodeB have
problem. Need BSS team check the RF module. If RTWP become normal after
disconnection, that means NodeB have no problem. We can conclude that the
problem may exist in Feeder system or external interference. BSS team can help to
do the VSWR test for the feeder and jumper to check the feeder system ok or not.
Or we can change jumper to verify.
- Troubleshoot the interference
Do the frequency scanning in NodeB LMT.
From the result we can check whether there is strong interference from some special
frequency band. If from the result we find the interference, we need visit the site to
find the interference source. We can:
If frequency scanning tool available (like frequency analyzer), we can use tool
to scan the interference. The method to check the interference by scanning tool:
Switch off the transmit power of the interference sector. Make the test antenna
of the tool toward the direction of the antenna of the NodeB (follow the same
orientation, same down tilt, also the same attitude) and scan the interference.
By this method we can check whether external interference exists or not.
If frequency scanning tool unavailable, we can adjust the azimuth of the
interference to check from which direction the external interference comes
from.
- Common methods
NodeB have two sets of RTWP, primary and secondary RTWP; if only one set
of RTWP is abnormal but the other set is OK. We can swap the primary feeder
with the secondary feeder to check whether high RTWP swap or not.
 If two sectors are very near but only one sector experience high RTWP and the
other sector is OK. We can swap the feeder of these two sectors at the antenna
side to check whether high RTWP will swap from one sector to the other.
By these swap actions, we can analyze the interference feature and find
the interference source.
Check List, SN, Check Items, Check Method, Check Result, Remark OMC
Information Collection
1. Uplink RF sensitivity MML command:
DSP RFDESPARAM / DSP DESENS
2. Uplink Attenuation Value MML command:
LST RXATTEN
3. Check the TMA gain(if TMA used) MM command:
LST TMAGAIN
4. whether nearby sites also have the same high RTWP feature check the RTWP
counter or realtime RTWP monitor
5. Describe the RTWP feature (like it is always high or some times high ). What
is the RTWP range MML command: STR RTWPRTTST (NodeB LMT)
real time RTWP monitor (both primary and secondary RTWP)
6. analyze the interference feature compare the traffic load with the RTWP.
Check whether high traffic or interferece cause the high RTWP.
7. LMT uplink frequecny scanning do the scanning in NodeB LMT (need block
the sector)
8. Check the intermodulation MML command: SET TXSW switch off the
downlink tansmit power and monitor whether interference disapper or not
Site visit and information collection
9. Visit the site Whether 3G system shared antenna with 2G or not? Whether
TMA used or not? Whether repeater is located nearby?
10. whether primary and secondary RTWP are both have high swap the primary
feeder with the secondary feeder to check whether high RTWP swap or not

12. differentiate internal or external interference. Disconnect the jumper from

the cabinet and then monitor the RTWP.