Call Setup Success Rate=BSS Call Establishment Success Rate = [([Success Rate of Call

Setup (Immediate Assignment)/{100}) x ([Success Rate of TCH Assignment]/{100}) x (1 ([Call Drop Rate on SDCCH]/{100})) x {100}.
In this formula,it is recommended to replace [Success Rate of Call Setup (Immediate
Assignment)] by "Immediate assignment commands/Immediate Assignment requests".
Br\\
Bijoy

Huawei - Man - 13th July 2010

(10:13 GMT)

As well
Call Setup Indications Timed Out: 162
for this hour.
No SD blocking

Huawei - Man - 13th July 2010

(10:10 GMT)

You mean I should use following formula for CSSR?

Immediate assignment commands/Immediate Assignment requests*100
Or what is useful formula for CSSR in Huawei system?

Bijoy - 13th July 2010

(09:41 GMT)

From this data,what I can conclude is:

1.This cell is either at LA boundary or overshooting at LA boundary beacuse LU request is
high.
2.Call setup Indication is Low,which means there is either Imm. assignment reject(SDCCH
Blk) or call setup indication timed out(T3101 expiry).
3.Your immediate aasignment success is poor for Non-call type.

Suggestions

1.Give tilt to the cell if overshooting

2.Check Co-BSIC-BCCH cells,if nearby
3.Increase Cell reselection hysteresis if on LA boundary.
4.Check for SDCCH Blocking(remote possibility)
This formula is actually too gross,you should use CSSR for CS services only.
P.S:
You can increase the "RACH Min. Access level","RACH Busy threshold",& "RACH error
threshold" to reduce this,but you cant eliminate the effect totally.
It is better if you use "Immediate assignment commands/Immediate Assignment requests"
in place of RA303I.
Br\\
Bijoy

Huawei - Man - 13th July 2010

(09:25 GMT)

Bijoy, please have a look stat for one hour of the mention cell. Its CSSR is very low. I can't
find the cause.
Maybe you can give some ideas to find the reason, PLEASE. Thanks a lot.

Start Time 13/07/2010 06:00:00

Object Name CellA
CA300J:Channel Requests (Circuit Service) : 208
CA303J:Call Setup Indications (Circuit Service) : 45
Call Setup Success Rate : 21.635
CA3030J:Call Setup Indications (SDCCH) (Circuit Service) : 45
CA3039J:Call Setup Indications (TCH) (Circuit Service) : 0
CA303A:Call Setup Indications (Call Type) : 3
CA303B:Call Setup Indications (Non-Call Type) : 42
A300A:Channel Requests (MOC) : 4
A300C:Channel Requests (MTC) : 4
A300D:Channel Requests (Emergency Call) : 0
A300E:Channel Requests (Call Re-establishment) : 0
A300F:Channel Requests (Location Updating) : 200
A300H:Channel Requests (Packet Call) : 100
A300I:Channel Requests (LMU+Reserved) : 0
A300K:Channel Requests (Protocol Incompatible) : 0
CA300A:Channel Requests (Call Type) : 8
CA300B:Channel Requests (Non-Call Type) : 300
CA303H:Call Setup Indications (Packet Service) : 0

K3000:SDCCH Seizure Requests : 208

K3003:Successful SDCCH Seizures : 208
K3003A:Successful SDCCH Seizures (Call Type) : 7
RCA313:Success Rate of TCH Assignment : 100
RA303I:Success Rate of Call Setup (Immediate Assignment) : 21.635

Huawei - Man - 13th July 2010

(09:23 GMT)

Bijoy, please have a look stat for one hour of the mention cell. Its CSSR is very low. I can't
find the cause.
Maybe you can give some ideas to find the reason, PLEASE. Thanks a lot.
Start Time 13/07/2010 06:00:00
Object Name CellA
CA300J:Channel Requests (Circuit Service) 208
CA303J:Call Setup Indications (Circuit Service) 45
Call Setup Success Rate 21.635
CA3030J:Call Setup Indications (SDCCH) (Circuit Service) 45
CA3039J:Call Setup Indications (TCH) (Circuit Service) 0
CA303A:Call Setup Indications (Call Type) 3
CA303B:Call Setup Indications (Non-Call Type) 42
A300A:Channel Requests (MOC) 4
A300C:Channel Requests (MTC) 4
A300D:Channel Requests (Emergency Call) 0
A300E:Channel Requests (Call Re-establishment) 0
A300F:Channel Requests (Location Updating) 200
A300H:Channel Requests (Packet Call) 100
A300I:Channel Requests (LMU+Reserved) 0
A300K:Channel Requests (Protocol Incompatible) 0
CA300A:Channel Requests (Call Type) 8
CA300B:Channel Requests (Non-Call Type) 300
CA303H:Call Setup Indications (Packet Service) 0
K3000:SDCCH Seizure Requests 208
K3003:Successful SDCCH Seizures 208
K3003A:Successful SDCCH Seizures (Call Type) 7
RCA313:Success Rate of TCH Assignment 100
RA303I:Success Rate of Call Setup (Immediate Assignment) 21.635

Bijoy - 13th July 2010

(09:03 GMT)

Channel Request for Packet Call means the MS is sending a RACH to access the PS services.
Br\\
Bijoy

Huawei - Man - 13th July 2010

(08:11 GMT)

Hi Bijoy
I have defined "Channel Request (Packet Call)" is 500-800-1800
times on this cell.

500-800-1800

Actually what does it mean, what is Packet Call?

Bijoy - 13th July 2010

(05:31 GMT)

Hi
Ideally,LU shouldn't be considered for calculating CSSR,but the formula you are using
considers SDCCH drop during LU.So,yes,your CSSR will get impacted.
P.S:There is a way out & you will find that in that very post.
Br\\
Bijoy

Huawei - Man - 12th July 2010

(12:26 GMT)

Yes yes, I found. Thanks.

Can location update failure affect to CSSR even no SD congestion?
Syed Fahad

2012-08-01, 10:10 AM

Dears,
We also faced the same issue in all Huawei BSC's in our Network. We enabled the traces at Um Interface,
and from these traces filtered the LU Requests and IMSI's requesting the LU's. When these IMSI's were
shared with NSN Core, they were all found out to be International Roaming IMSI's, with LU Reject Messages
mostly as " Roaming Not allowed in the LAC" and " PLMN not allowed". From here we initially got the idea
that this problem is only faced and created by Roamers, and no LU Reject Message is returned from Our
Subscriber IMSI. Even the Drive Test Results during this degradation Time on the effected cells showed no
abnormality.
Having said that one trial was done during the degradation time on the degraded cells, and that was to
restrict the 2G-3G IRAT Reselection Criteria, and problem was vanished.!!!!!!
If the issue is being faced in 2G-3G Co located cells, or 3G Cells in the area, try to restrict the 2G -3G IRAT
Reselection Criteria by setting the FDD Repquant = RSCP, RSCPMinThreshold = 15 / -84dBm and FDD Q
Offset = 8.

@Khurram The Reason why this problem resolves at its own might be the fact that after sending the
continuous Channel Requests for LU, the MS battery dries off.