Sei sulla pagina 1di 2

Acessibility VS.RRC.Rej.ULCE.

Cong (67190404)
VS.RRC.Rej.DLCE.Cong (67190405)
Worst cells:
VS.RRC.Rej.Code.Cong (67179524)
There are two categories of KPIs:
Trial:
-which cells/RBSs having accessibility problems (RRC connection successful rate and RAB establishment
less than 98% RRC Registration success rate with LAC borders:
successful rate) 10 cells
-Change FACH Power LAC border cells from 1 to 1.8dB
-imply the reasons of failures
-Change IDLEQHYST2S from 2 to 4dBm
With the weight factor (total number of RRC attempts of that cell / total number of RRC attempts in
Parameters:
whole RNC) in a certain time period, for example consequent 7 days
LST URRCESTCAUSE
Low CSSR CS:
----------------------------------------------------------------------------------------
-RRC Failure
RAB Voice Failure:
-RAB Voice Failure
Parameters:
-Check alarm for serving NodeB and neighbouring sites
-SET UFRCCHLTYPEPARA
RRC Failure :
-Check CS VS PS, CN VS RNC Security mode:
if VS.RRC.AttConnEstab.R eg very high
(MSC SET MapConfig,SGSN SET PMM ,RNC SET UEA) if matched
- ADD CNDOMAIN:CNDOMAINID=PS_DOMAIN, DRXCYCLELENCOEF=6, NMO=MODE1 (change to MODE2)
Reasons:
Reasons:
VS.RAB.FailEstabCS.UuFail (73393836): Uu Interface Configuration Failure “count at best cell”
VS.RRC.Rej.Redir.IntraRat (67189473): (whenever DRD Fails and Admission Fails then Redirection
VS.RAB.FailEstabCS.RBIncCfg (ID: 67193536) “Invalid Configuration of UE”
Happens “by sending in RRC Reject Message redirection info.”, this don’t count if redirection is due to
VS.RAB.FailEstabCS.RBCfgUnsup (ID: 67193537) “Configuration unsupported by UE as UE don’t have VP”
service-based redirection)
VS.RAB.FailEstabCS.PhyChFail (ID: 67193538) “physical channel failure from UE side, not related to RF”
VS.RRC.Rej.Redir.InterRat (67189474): inter-RAT cells (whenever DRD Fails and Admission Fails then
VS.RAB.FailEstabCS.UuNoReply (ID: 67193539) “RF problem”
Redirection Happens “by sending in RRC Reject Message redirection info.”, this don’t count if redirection
-Check Missing Neighbor
is due to service-based redirection)
-NodeB Alarm
VS.RRC.Rej.Redir.Service (67196031): Service-based RRC Redirection (by sending in RRC Reject Message
-Interference
redirection info.)
-Check the Pilot Pollution
VS.RRC.Rej.RL.Fail (67179525):(maybe from Iub or Node-B hardware as power amplifier overheating
-Check invalid parameters
“check alarms”)
-Check inter-RAT HO and if the failure point is in RNC border
VS.RRC.Rej.TNL.Fail (ID: 67179527):Transmission Setup Failure on Iub Interface (its problem with AAL2
-RbSetup RspTmr(SET USTATETIMER:RbSetupRspTmr=8000)
transmission, happens in ATM connections)
VS.RAB.FailEstabCS.Cong (67189494): Congestion “count at best cell”
-Transmission alarm
VS.RAB.FailEstabCS.ULPower.Cong (ID: 67193611) VS.RAB.FailEstabCS.DLPower.Cong (ID: 67193612)
-Check IuB packet loss
VS.RAB.FailEstabCS.ULIUBBand.Cong (ID: 67192611) VS.RAB.FailEstabCS.DLIUBBand.Cong (ID:
-Check IUB AAL2PATH or IPPATH configruation
67192610) VS.RAB.FailEstabCS.ULCE.Cong (ID: 67190406) VS.RAB.FailEstabCS.DLCE.Cong (ID:
VS.RRC.FailConnEstab.NoReply (67190401):Timeout of RRC CONNECT SETUP COMPLETE (normally timer
67190407) VS.RAB.FailEstabCS.Code.Cong (ID: 67199864)
waits for 5000msec) Radio
if VS.RAB.FailEstabCS.Unsp>10%
-Check missing neighbor
-if (VS.RAB.FailEstabCS.Unsp –VS.RAB.FailEstabCS.Cong)>5%,
-NodeB Alarm
Check AAL2 CID Congestion
-SPU/PIU Load Check
-if(IRATHO.AttIncCS/ VS.RAB.AttEstabCS.Conv)>10%
if Subsystem VS.SPU.CPULOAD.MEAN >60%
Disable 2G->3G handover
-Reselection: if (RRC.AttConnEstab.IRATCelRes/VS.RRC.AttConnEstab.Cell) too high
-capacity check
-HO: if (IRATHO.AttIncCS/VS.RAB.AttEstabCS.Conv) too high,
VS.RAB.FailEstabCS.IubFail (73393835): Radio Link Configuration Failure “Iub or hardware problem +
-FACH channel congestion & power :
count at best cell”
-Check coverage in the failure points.
VS.RAB.FailEstabCS.TNL (67189496): Transport Network Layer Cause “Iu problem + count at best cell”
-Check DL interference
Check Iu interface Alarm
-pilot pollution
Check Iu-CS AAL2PATH or IPPATH configuration
-Check UL interference in the cell
Check Iu-CS if have packet Loss
VS.RRC.FailConnEstab.Cong (67179521): Congestion VS.RRC.Rej.ULIUBBand.Cong (67192608)
Top cell Alarm Check ,transmission alarm
VS.RRC.Rej.DLIUBBand.Cong (67192609) VS.RRC.Rej.ULPower.Cong (67193609)
Check Iub AAL2PATH or IPPATH configuration
VS.RRC.Rej.DLPower.Cong (67193610)
Check IuB if have packet Loss
Low CSSR PS:
-RRC Failure
-RAB PS Failure
-Check alarm for serving NodeB and neighbouring sites
RAB PS Failure:
Reasons:
VS.RAB.FailEstabPS.UuFail (73393836): Number of Failed PS RAB Establishments Due to Uu Interface
Configuration Failure “count at best cell”
VS.RAB.FailEstabPS.RBIncCfg (ID: 67193536) “Invalid Configuration of UE”
VS.RAB.FailEstabPS.RBCfgUnsup (ID: 67193537) “Configuration unsupported by UE as UE don’t have VP”
VS.RAB.FailEstabPS.PhyChFail (ID: 67193538) “physical channel failure from UE side, not related to RF”
-Blind HO Flag if 2 carrier
VS.RAB.FailEstabPS.UuNoReply (ID: 67193539) “RF problem”
-Blind HO Flag if 2 carrier
VS.RAB.FailEstabPS.Cong (67189494): Number of Failed PS RAB Establishments due to Congestion
“count at best cell” VS.RAB.FailEstabPS.ULPower.Cong (ID: 67193611)
VS.RAB.FailEstabPS.DLPower.Cong (ID: 67193612) VS.RAB.FailEstabPS.ULIUBBand.Cong (ID: 67192611)
VS.RAB.FailEstabPS.DLIUBBand.Cong (ID: 67192610) VS.RAB.FailEstabPS.ULCE.Cong (ID: 67190406)
VS.RAB.FailEstabPS.DLCE.Cong (ID: 67190407) VS.RAB.FailEstabPS.Code.Cong (ID: 67199864)
VS.RAB.FailEstabPS.IubFail (73393835): Number of Failed PS RAB Establishments Due to Radio Link
Configuration Failure “Iub or hardware problem + count at best cell”
VS.RAB.FailEstabPS.TNL (67189496): Number of Failed PS RABs Establishments Due to Transport
Network Layer Cause “Iu problem + count at best cell”

Congestion:
-check Traffic
-Check if overshooting
-instant or long time

Parameters:
D2F2PTVMTHD from 64B to 128B (DCH to Fach or DCH to PCH)

Potrebbero piacerti anche