You are on page 1of 11

Check, de la performance des IRATs HO CS et PS

1. KPI Assessment of the GSM and UMTS Cooperation

Factors that affect inter-system handover KPIs are as follows: radio environment, basic network configuration,
handover policies, and CR support by UEs. According to the commercial verification results, radio environment
is the major factor that affects the handover performance. Basic network configuration and handover policies
take the second place. The CR support by UEs is the third factor that affects the handover performance.

The inter-system handover performance can be improved in the following ways.

 Improve radio environment.


o Properly configure network parameters: The following error configurations may result in
inter-system handover failures:
o The neighboring cell parameters are incorrect: The configuration of the neighboring cells on
the UMTS network is different from that on the GSM network.
o The core network parameters are incorrect or not supported.
 Select proper handover policies: In the same radio environment, different handover policies cause
different handover performance.
o When the RSCP is used for a measurement, measurement results are reported in 3A events.
o When the Ec/Io is used for a measurement, measurement results are reported in 3A events.
o When the RSCP is used for a measurement, measurement results are reported periodically.
o When the Ec/Io is used for a measurement, measurement results are reported periodically.
 Use UEs that support the specific CR to avoid ping-pong reselection or PS ping-pong handover: If a
system supports the bidirectional handover and cell reselection between the WCDMA network and
the GSM network, ping-pong handover and cell reselection may be introduced. UEs that support
FDD_Qmin CR-032221 and FDD_RSCP_threshold CR can properly suppress ping-pong reselections and
decrease the PS service handover frequency. During the cell reselection, you can configure parameters
on the UEs that support the FDD_Qmin CR-032221 CR to avoid frequent cell reselections between the
WCDMA network and the GSM network and avoid unnecessary signal interaction. If UEs support the
FDD_Qmin CR-032221 and FDD_RSCP_threshold CR, you can configure certain handover algorithms to
avoid ping-pong handovers during the PS inter-system handover.

Common KPIs involved in the GSM and UMTS cooperation include:

 CS inter-system handover preparation success rate


 CS inter-system handover execution success rate
 CS HO Ratio Inter-system
 PS HO Success Rate Inter-system
 PS inter-frequency handover rate

You can analyze the network coverage, network traffic, and cooperation parameter settings based on the
handover rate and handover success rate. You must comprehensively consider the cell coverage in various
scenarios by balancing the entire performance and performance in special scenarios. In this manner, you can
avoid deterioration of the entire network performance due to the optimization for special scenarios.

In the table below are presented the related KPIs and normal/optimal lowest values for each of them:

KPI Baseline

CS Inter-RAT HO Prepare Success Rate 95%


KPI Baseline

CS Inter-RAT HO Execute Success Rate 95%


CS Inter-RAT HO Proportion Lower than or equal to 10%
PS Inter-RAT HO Success Rate 95%
PS IRAT HO Proportion Lower than or equal to 1%
RRC.AttConnEstab.Reg Rate HO Proportion Lower than or equal to 30%
For CS inter-system handover preparation success rate, identify the top N cells for the following Counters:

VS.SRELOC.SuccPrep.IRHOCS.Rate
IRATHO.AttRelocPrepOutCS
IRATHO.SuccRelocPrepOutCS
IRATHO.FailRelocPrepOutCS
IRATHO.FailRelocPrepOutCS.NoResAvail
IRATHO.FailRelocPrepOutCS.TAlExp
IRATHO.FailRelocPrepOutCS.TgtFail
IRATHO.FailRelocPrepOutCS.ReloNoSup
IRATHO.FailRelocPrepOutCS.UKnowRNC
VS.IRATHO.FailRelocPrepOutCS.Abort
VS.IRATHO.FailRelocPrepOutCS.CNNoReply
VS.IRATHO.FailRelocPrepOutCS.Cancel
VS.IRATHO.FailRelocPrepOutCS.ReqInfoNotAvail
For CS inter-system handover success rate, identify the top N cells for the following Counters:

VS.IRATHO.SuccCSOut.RNC.Rate
IRATHO.AttOutCS
IRATHO.SuccOutCS
VS.IRATHO.FailOutCS
IRATHO.FailOutCS.CfgUnsupp
IRATHO.FailOutCS.PhyChFail
VS.IRATHO.FailOutCS.Abort
VS.IRATHO.FailOutCS.Other
VS.IRATHO.FailOutCS.NoReply
CS HO Ratio Inter-system

VS.RAB.SuccEstabCS.AMR.12.2
IRATHO.AttOutCS
Ratio = IRATHO.AttOutCS:VS.RAB.SuccEstabCS.AMR.12.2
PS HO Success Rate Inter-system of top N cells

IRATHO.SuccOutPSUTRAN.Rate
IRATHO.AttOutPSUTRAN
IRATHO.SuccOutPSUTRAN
VS.IRATHO.FailOutPSUTRAN.Cell
IRATHO.FailOutPSUTRAN.CfgUnsupp
IRATHO.FailOutPSUTRAN.PhyChFail
VS.IRATHO.FailOutPS.Abort
VS.IRATHO.FailOutPSUTRAN.Other
PS HO Ratio Inter-system

VS.RAB.SuccEstPS.Cell
IRATHO.AttOutPSUTRAN
IRATHO.AttOutPSUTRAN:VS.RAB.SuccEstPS.Cell
Inter-RAT cell re-selection rate

RRC.AttConnEstab.IRATCelRes
VS.RRC.AttConnEstab.Sum
Inter-RAT cell re-selection rate=RRC.AttConnEstab.IRATCelRes/VS.RRC.AttConnEstab.Sum.

2. 3G to 2G IRAT Parameters and strategy

In this section, we will describe parameters and strategy related to interRAT HO definition.

Please note that if CoexistMeasThdChoice is set to COEXIST_MEAS_THD_CHOICE_INTERFREQ, then


interfrequency parameters for HO will be considered. In case CoexistMeasThdChoice is set to
COEXIST_MEAS_THD_CHOICE_INTERRAT, then interRAT parameters for HO will be considered.

Note also that periodical reporting is preferred and recommended by Orange group and provide. Test have
been done for this parameter showing better performance for IRAT HO Success Rate and reduction of IRAT HO
number.

Interfreq configuration InterRAT configuration

Parameter name Strategy Parameter name Strategy


Periodical Periodical
INTERRATREPORTMODE reporting INTERFREQREPORTMODE reporting
FilterCoefOf2D2F D3 InterFreqFilterCoef D3
MeasQuantityOf3A <NULL> PrdReportInterval D500
InterRATFilterCoef D3 HystFor2B <NULL>
WeightForUsedFreq 0 HYSTFOR2D 0
InterRATPeriodReportInterva
l D1000 HYSTFOR2F 0
HYSTFOR2D 0 HystForPrdInterFreq 0
HYSTFOR2F 0 WeightForUsedFreq 0
Hystfor3A <NULL> TimeToTrig2B <NULL>
HystforInterRAT 0 TimeToTrig2D D320
TrigTime2D D320 TimeToTrig2F D1280

TrigTime2F D1280 TimeToTrigForPrdInterFreq 0

TrigTime3A <NULL> INTERFREQCSTHD2DECN0 -14

TimeToTrigForNonVerify 0 INTERFREQCSTHD2FECN0 -12

TimeToTrigForVerify 0 INTERFREQR99PSTHD2DECN0 -16

BSICVerify Verify mode INTERFREQHTHD2DECN0 -16

INTERRATCSTHD2DECN0 -14 INTERFREQR99PSTHD2FECN0 -14

INTERRATCSTHD2FECN0 -12 INTERFREQHTHD2FECN0 -14

INTERRATR99PSTHD2DECN0 -16 INTERFREQCSTHD2DRSCP -104

INTERRATHTHD2DECN0 -16 INTERFREQCSTHD2FRSCP -101

INTERRATR99PSTHD2FECN0 -14 INTERFREQR99PSTHD2DRSCP -112

INTERRATHTHD2FECN0 -14 INTERFREQHTHD2DRSCP -112


INTERRATCSTHD2DRSCP -104 INTERFREQR99PSTHD2FRSCP -109
INTERRATCSTHD2FRSCP -101 INTERFREQHTHD2FRSCP -109
INTERRATR99PSTHD2DRSCP -112 TARGETFREQCSTHDECN0 -12
INTERRATHTHD2DRSCP -112 TARGETFREQR99PSTHDECN0 -14
InterRATR99PsThd2FRSCP -109 TARGETFREQHTHDECN0 -14
InterRATHThd2FRSCP -109 TARGETFREQCSTHDRSCP -101
TargetRatCsThd 12 TARGETFREQR99PSTHDRSCP -104
TargetRatR99PsThd 16 TARGETFREQHTHDRSCP -104
TargetRatHThd 16 USEDFREQCSTHDECN0 -14
UsedFreqCsThdEcN0 <NULL> USEDFREQR99PSTHDECN0 -16
UsedFreqR99PsThdEcN0 <NULL> USEDFREQHTHDECN0 -16
UsedFreqHThdEcN0 <NULL> USEDFREQCSTHDRSCP -104
UsedFreqCsThdRscp <NULL> USEDFREQR99PSTHDRSCP -112
UsedFreqR99PsThdRscp <NULL> USEDFREQHTHDRSCP -112
UsedFreqHThdRscp <NULL> HHOECNOMIN -16
InterRATMeasTime 60 HHORSCPMIN -115

InterRATPingPongTimer 0 INTERFREQMEASTIME 60

InterRATPingPongHyst 0 PeriodFor2B <NULL>


PeriodFor3A <NULL> AmntOfRpt2B <NULL>
AmntOfRpt3A <NULL> TimeToInterfreqHO 0

InterRatPhyChFailNum 3 UsedFreqLowerThdEcNo -18


PenaltyTimeForPhyChFail 30 UsedFreqUpperThdEcNo 0

3. KPI Assessment of the GSM and UMTS Cooperation

Collect the number of handovers from the WCDMA network to the E-UTRAN network of each cell during the
specific period and the number of successful handovers from the WCDMA network to the E-UTRAN network.
For example:

CellId Time(As day) VS.U2LTEHO. VS.U2LTEHO.SuccOut VS.U2LTEHO.RRCRelea


AttOutPS.Serv PS.Service se.Service
ice

XX YYYY-DD-MM
XX YYYY-DD-MM
Add the number of all the handovers and the number of successful handovers from the LTE network to the
WCDMA network of all the cells. For example:

Handover success rate from the WCDMA network to the LTE network:

= Number of successful handovers from the WCDMA network to the LTE network/Number of all the handovers
from the WCDMA network to the LTE network x 100%

= VS.U2LTEHO.SuccOutPS.Service /VS.U2LTEHO.AttOutPS.Service x 100%

If the W2E is low, check the configuration of external LTE cells in RNC, then check 3G to LTE handover strategy
and conformity to the planned strategy and finally check LTE KPIs in order to confirm that no problem of
coverage or congestion is going in LTE network. Finally, if none of those is a problem check if caused by
mismatched configuration between EPC, EnodeB and RNC.

LTE KPIs to check are given in the attached file:

CellId Time(As day) L.RRC.ConnReq.Succrate L.RRC.ConnReq.Att L.RRC.ConnReq.Succ

XX YYYY-DD-MM XX% NNN NNN


eRAB Setup Success Rate
CellId Time(As day) L.E-RAB.Est succrate L.E-RAB.AttEst L.E-RAB.SuccEst

XX YYYY-DD-MM XX% NNN NNN

Call drop rate


CellId Time(As day) Drop rate(ALL) L.E-RAB.AbnormRel L.E-RAB.Rel

XX YYYY-DD-MM XX% NNN NNN


RRC Setup Success Rate
CellId Time(As day) L.RRC.Conn.succrate L.RRC.ConnReq.Att L.RRC.ConnReq.Succ

XX YYYY-DD-MM XX% NNN NNN

4. Diagrams

CS Inter-RAT HO Prepare
Success Rate<=95%

Cause Cause Cause Cause


IRATHO.FailR IRATHO.FailR VS.IRATHO.F IRATHO.FailR
elocPrepOutC elocPrepOutC ailRelocPrep elocPrepOutC
S.NoResAvail S.UKnowRNC OutCS.ReqInf S.ReloNoSup
oNotAvail
True True True

Find from Ucell-Ncell Make 2G externalCS Inter-RAT HO Exec Check consistency of cell Verify parameters &
Success Rate<=95% configuration between radio
worst 2G cells for prep check on the RNC and CN. license for reloc in CN.

Relief cong
Cause
and/or Cause Cause Cause Cause Cause
interf for 2G cell
IRATHO.Fail IRATHO.Fail VS.IRATHO.F VS.IRATHO.F VS.IRATHO.F VS.IRATHO.F
OutCS.PhyC OutCS.CfgUn ailRelocPrep ailOutCS.Abo ailRelocPrep ailOutCS.No
hFail supp OutCS.Cancel rt OutCS.Abort Reply

2G cell True
True Vrai Vrai
problem
solved Check if Iu-cs interface
Find from Ucell-Ncell Make 2G external
No specific solution.
shows quality or cong Verify parameters &
Check if Iu-cs interface
shows quality or cong
worst 2G cells check on the RNC
Signaling trace needed
problem. If not change license for reloc in CN.
problem. If not change
RelocIuRelCmdTmr timers
RelocIuRelCmdTmr timers
False

Makeconfiguration
Check harder HO toof
problem cell: Ciooffset Cause Cause
the 2G cells in RNC
for Cell or layer priority IRATHO.FailR IRATHO.FailR
(CGI-BCCH/BSIC
or GSM RSSI thdmapor
elocPrepOutC elocPrepOutC
S.TAlExp S.TgtFail
HOtrigger time

Problem True
solved
True Target CN or BSC failure. Check
Check if RelocCmdTmr value is
Problem alarms, path consistency an
solved reasonable
congestion and quality.

False
False
Check and improve 2G Cause
cell RF status: VS.IRATHO.F
ailOutCS.Oth
Cause
interference, er
VS.IRATHO.F
overshooting, low ailRelocPrep
OutCS.CNNo
Reply

True Change RelocIuRelCmdTmr to


2G cell higher value
problem No specific solution. Signaling
solved trace and CN parameters audit
needed

False

Change GSM RSSI


target Thd

End
False Problem
solved

True

End
PS Inter-RAT HO Success
Rate <= 95% and CS IRAT HO
Success Rate >= 95%

Cause Cause Cause Cause


IRATHO.FailO IRATHO.FailO VS.IRATHO.F VS.IRATHO.F
utPSUTRAN. utPSUTRAN. ailOutPS.Abo ailOutPSUTR
PhyChFail CfgUnsupp rt AN.Other

True True True

Find from Ucell-Ncell Find from Ucell-Ncell Increase T309 timer Change
worst 2G cells worst 2G cells value. RelocIuRelCmdTmr to
higher value

Check configuration of Check and improve


the 2G cells in RNC PDCH/TBF availability
(CGI-BCCH/BSIC map in 2G side

2G cell
problem
Problem True solved
solved

True
False

Check and improve 2G IRAT problem


solved True
cell RF status:
interference,
overshooting, low

Check CN
True 2G cell
problem configuration problem
solved

False

Change GSM RSSI


target Thd

False Problem
solved

True

End
CS IRAT Ratio>=10% or PS
IRAT Ratio >=1%

VS.IRATHO.AttOu VS.IRATHO.AttOut
tCS.TrigEcNo or CS.TrigRscpor
VS.IRATHO.AttOu VS.IRATHO.AttOut
tPS.TrigEcNo are PS.TrigEcNo are
important. important.

True True
Check if InterRAT
Check if InterRAT parameter strategy are
parameter strategy are respected
respected

True True

Change interRAT
Strategy OK False parameters and/or strategy False Strategy OK

True True

EcNo improvement RSCP improvement


solution and coverage solution and coverage
check OSS and/or DT check OSS and/or DT

False
Problem
solved

True

End
Start

RRC.AttConnEst
ab.IRATCelRes/
Faux VS.RRC.AttConn
Estab.Sum >=
30%

Vrai

Check neighboring configuration Check IRAT reselection Check overshooting (check


(check relative document) parameters relative document)

Is OK ? Faux
Make needed corrections.

Vrai

Is DT possible Faux
Check IRAT HO counters

Vrai

Is RSCP main cause


Make DT in the area in order to for CS/PS IRAT HO?
Faux
check cause of reselection

Vrai

Has coverage Vrai Make coverage improvement


problems(RSCP)
? actions for RSCP (go to relative
document)

Make coverage improvement


Faux actions for EcNo (go to relative
document)

Change Qrxlevmin for GSM to a


higher value to reduce
probability of reselecting 2G.

Change idleQhyst1s / Qoffset1sn


value in order to make harder
reselection to 2G.

Change Treselection to larger


value in order to make harder
reselection to 2G.
End
Start

HO SR from LTE cell


WCDMA to neighborin Add and/or correct LTE
True False
LTE low? g check
OK? neighboring configuration

WCDMA to Correct WCDMA to LTE


LTE HO
parameters
False handover / reselection
correctly parameter (relate to document)
configured
?

Make LTE capacity relief actions


False LTE True
LTE Kpis capacity (check related document).
OK? problem?

True

LTE Make LTE parameters / strategy


configurati True
on actions (check related
problem? document).

Check alarms and


LTE True
Hardware troubleshooting guide
problem?

LTE RF
Make RF improvement /
True
problem? correction actions (check
related document).

LTE Make transmission improvement /


False
transmissio correction actions (relate to service
n OK? drop document)

True

EPC – Correct configuration and


False
EnodeB- interconnection parameters and
RNC config algorithms
OK?

False Problem
solved?

True

Start

You might also like