In this paper I would like to share how to improve Call set up Success Rate in WCDMA system.
In WCDMA CSSR is split per services such as: CSSR CS(Voice services), CSSR PS(Data services), CSSR
Video(Video services) but the idea is same when we would like to improve Call set up success rate.
As we know in 3G WCDMA there are some resources like Code,Power,CE(Channel Element) and
IUB. You have to make sure no blocking resources first to improve your CSSR. If you found some
blocking based on your counter then you have to optimize. Here are some suggestion step to
optimize blocking resources:
1st action step: Physical Audit (involving TP analysis) : Make sure no overlap/overshooting
coverage
- Remove Locell for 2nd carrier in nodeb with script : RMV LOCELL:LOCELL=x;
ADD
LOCELL:LOCELL=x,STN=x,SECN=x,SECT=LOCAL_SECTOR,ULGROUPNO=0,DLGROUPNO=0,TTW=FALS
E,CN1=1,SRN1=4,SN1=x,ANT1N=ANTB,ULFREQ=9638,DLFREQ=10588,MXPWR=460,HISPM=FALSE,
RMTCM=FALSE,VAM=FALSE;
3rd Action: Modify DL CAC parameters set to higher value. Parameters involved :
DLCONVAMRTHD, DLCONVNONAMRTHD, DLOTHERTHD, DLHOTHD, DLCELLTOTALTHD
1st action: Verify CE license and CE board capability. Commands involved : DSP LICENSE, DSP
BBPTC(Huawei LMT)
1st Action: Verify Iub BW setting in Node-B and in RNC. Sets involved : IPPATH, IPLOGICPORT
4th action: Modify FTI to reduce Active Factor. Sets involved : TRMFACTOR, ADJMAP, ADJNODE
Hardware issue or wrong installation can be impacted to low CSSR such as WRFU problem or bad
connector installation. You have to make sure no such hardware problem to make your CSSR
good.
As stated on resources optimization, you need to make sure no overshooting or coverage overlap
to make your CSSR is good and no handle unnecessary traffic and make nodeB handle traffic
heavily.
When fast dormancy, enhanced fast dormancy, or standard fast dormancy is applied, the UE can
request the RNC to release the PS signaling connection if no more PS data is being transmitted.
Upon receiving such a request, the RNC can either release the signaling connection and put the UE
into idle mode, or maintain the signaling connection and put the UE through Cell_FACH to
CELL/URA_PCH state to reduce battery consumption. The descriptions about fast dormancy,
enhanced fast dormancy, and standard fast dormancy are as follows:
- With fast dormancy, after receiving a Signaling Connection Release Indication (SCRI) message
from a UE, the RNC releases the UE RRC connection regardless of whether the message contains
the cause value "UE Requested PS Data session end."
- With enhanced fast dormancy, UEs send SCRI messages that do not contain the cause value "UE
Requested PS Data session end" to the RNC. After receiving such an SCRI message, the RNC moves
- Standard fast dormancy is applicable to fast dormancy UEs that comply with 3GPP Release 8 (R8
for short). With standard fast dormancy, UEs send SCRI messages that contain the cause value "UE
Requested PS Data session end" to the RNC. After receiving such an SCRI message, the RNC moves
the UE through Cell_FACH to CELL/URA_PCH state. Standard fast dormancy is valid only when
theRNC has enabled the timer T323 in system information block type 1 (SIB1). You can refer to the
document on your vendor to activate EFD feature.
You can adjust CPICH Power setting to reduce coverage and improve your CSSR Ex:
Change PCPICHPOWER from 330 to 300.
You can adjust QQUALMIN to improve CSSR and avoid congestion on blocking resources especially
during event with potential to increasing traffic. Example: Change Qqualmin from -18 to -15 to avoid
congestion.