1.

Low CSSR Voice (4)

• RNL related problem: following counters indicate that the failure is due to a RNL (Radio Network Layer) procedure
problem; includes congestion counters.
- VS.RAB.FailEstCS.Relo: CS RAB establishment failures due to relocation; check inter-RAT HO and if the failure point is
in RNC border.
- VS.RAB.FailEstCS.RIPFail: CS RAB establishment failures due to failure in a radio interface procedure; check the
relative RB Setup failure counters to get more details on the failure cause:
- VS.FailRBSetup.CfgUnsup: unsupported configuration (e.g.: UE receives an RB setup request for Video Call
while is doing a PS downlink data service. Many terminals do not support simultaneous Video Call and high-
speed PS service on the downlink)
- VS.FailRBSetup.PhyChFail: physical channel failure; indicates poor coverage
- VS.FailRBSetup.CellUpd: cell update occurs (never happens in commercial networks)
- VS.FailRBSetup.IncCfg: invalid configuration; some UEs, mainly Sony Ericsson, may cause this
- VS.FailRBSetup.NoReply: mainly RF related issue
 1. Low CSSR Voice (5)
• Congestion problem: following counters indicate lack of radio recourses or Iub bandwidth. Check the Admission
Control thresholds. Take appropriate measures to relieve congestion, e.g. activate LDR, OLC algorithms, and to
increase capacity. Refer to Huawei 3G Capacity Optimisation document in IMS [1] for more details on how to battle
congestion and improve capacity.
- VS.RAB.FailEstCs.Code.Cong: CS RAB establishment failures due to code congestion
- VS.RAB.FailEstCs.Power.Cong: CS RAB establishment failures due to power congestion
- VS.RAB.FailEstCs.ULCE.Cong: CS RAB establishment failures due to UL CE congestion
- VS.RAB.FailEstCs.DLCE.Cong: CS RAB establishment failures due to DL CE congestion
- VS.RAB.FailEstab.CS.DLIUBBand.Cong: CS RAB establishment failures due to UL Iub bandwidth congestion
- VS.RAB.FailEstab.CS.ULIUBBand.Cong: CS RAB establishment failures due to DL Iub bandwidth congestion
- VS.RAB.FailEstabCS.Unsp.Other: CS RAB establishment failures due to congestion in other resources than the
previous 6 cases
- VS.RAB.FailEstabCS.RNL.Other: CS RAB establishment failures due to any RNL related reason other than the previous
9 cases

• Any other reason: following counter indicate failure due to any other reason apart from the previous ones
- VS.RAB.FailEstabCS.Other.Cell: CS RAB establishment failures due to any other reason except the previous 11 cases

Note: All previous RAB failure counters include all CS services: AMR and Video Call.

[1] https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D420188465
 2. Low CSSR PS (1)
- RNC level formula:
PS Call Setup Success Rate (RNC) =
(([VS.RRC.SuccConnEstab.OrgInt]+[VS.RRC.SuccConnEstab.OrgBkg]+[VS.RRC.SuccConnEstab.TrmInt]+[VS.RRC.SuccCon
nEstab.TrmBkg])/([VS.RRC.AttConnEstab.OrgInt]+[VS.RRC.AttConnEstab.OrgBkg]+[VS.RRC.AttConnEstab.TrmInt]+[VS.R
RC.AttConnEstab.TrmBkg]))*(([RAB.SuccEstabPSNoQueuing.Intact]+[RAB.SuccEstabPSNoQueuing.Bgrd]+[RAB.SuccEsta
bPSQueuing.Intact]+[RAB.SuccEstabPSQueuing.Bgrd])/([RAB.AttEstabPS.Intact]+[RAB.AttEstabPS.Bgrd]))*{100}

- Cell level formula:

PS Call Setup Success Rate (Cell) =
(([RRC.SuccConnEstab.OrgItrCall]+[RRC.SuccConnEstab.OrgBkgCall]+[RRC.SuccConnEstab.TmItrCall]+[RRC.SuccConnEst
ab.TmBkgCall])/([RRC.AttConnEstab.OrgInterCall]+[RRC.AttConnEstab.OrgBkgCall]+[RRC.AttConnEstab.TmInterCall]+[R
RC.AttConnEstab.TmBkgCall]))*(([VS.RAB.SuccEstabPS.Inter]+[VS.RAB.SuccEstabPS.Bkg])/([VS.RAB.AttEstabPS.Inter]+[
VS.RAB.AttEstabPS.Bkg]))*{100}

Analysis process:
1. Check which part of the CSSR KPI causes the low value: RRC setup, RAB setup or both. The 2 distinct parts RRC
Setup Success Rate and RAB Setup Success Rate that are composing the CSSR can be used for this purpose.
2. To check the above, check the corresponding KPIs for RRC Setup Success Rate and AMR RAB Setup Success Rate.
3. Check the alarms for the serving NodeB and neighbouring sites in order to identify any hardware faults.
 2. Low CSSR PS (2)
4. In case that RRC Setup is causing the low value, identify the root cause of high RRC Setup failures by following
counters:
• Transmission problem: following counters indicate transmission issue on Iub interface; check relative alarms
- VS.RRC.Rej.RL.Fail: RRC establishment failures due to RL setup failure
- VS.RRC.Rej.TNL.Fail: RRC establishment failures due to TNL setup failure

• Radio resource congestion: following counters indicate lack of radio resources or Iub bandwidth. Check the
Admission Control thresholds. Take appropriate measures to increase capacity.
- VS.RRC.Rej.Power.Cong: RRC establishment failures due to power load congestion
- VS.RRC.Rej.UL.CE.Cong: RRC establishment failures due to UL CE congestion
- VS.RRC.Rej.DL.CE.Cong: RRC establishment failures due to DL CE congestion
- VS.RRC.Rej.Code.Cong: RRC establishment failures due to code congestion
- VS.RRC.Rej.ULIUBBandCong: RRC establishment failures due to UL Iub bandwidth congestion
- VS.RRC.Rej.DLIUBBandCong: RRC establishment failures due to DL Iub bandwidth congestion
- VS.RRC.Rej.Other.Cong: RRC establishment failures due to other congestion except from the previous 6 reasons

• RF problem: following counter indicate failure due to RF issue. Check coverage in the failure points. Check if it is in
cell border (most probably it is).
- RRC.FailConnEstab.NoReply: RRC establishment failures due to no reply from the UE during the RRC setup flow