Low value (e.g.

<95%) indicates problems to establish a PS call between UEs and PS

domain CORE.Similar formulas can be used for each specific RAB CSSR, i.e., PS
Streaming CSSR (%) or PS Interactive CSSR (%).Refer to the internal Claro doc.
Optimization Guidelines: Capacity in Ericsson (DEO.OTM.IOP3041) for further
detailsregarding the Ericsson features Load Sharing and Directed Retry.From P7.1
(P7 FP), current release in Claro, new counters are available for monitoring the
performance of the
NASSignalling phase
(i.e. after IU Signalling Connection establishment and before RAB Assignment
Request).New formulas will also cover the
Iu Signalling Connection

phase
performance through counters already availablebefore P7.1 in MO RNCFunction;
therefore, the same Iu Sig. Conn. Success Rate value is to be applied to all
UtranCellsunder the same RNC. As the new formulas below will compute failures in
these 2 additional phases (see next figure), a slight degradation inthese KPIs might
be observed after their introduction when comparing to old formulas above.
3.1.1.3CS CSSR (%) from P7.1where (RAB) = Speech, Cs64, Cs57Note that 2 important additions have been made
to this KPI:
1.
By adding pmNoDirRetrySuccess in the RAB term numerator, this KPI does take into
account the success rate of thespeech calls redirected to gsm by the Directed Retry
mechanism.2.By adding pmNoInCsIratHoSuccess/Att counters in the RAB term, this
KPI now also takes into account the successrate of the Speech Calls entering the 3G
network via Incoming CS IRAT HO.
3.1.1.4PS CSSR (%) from P7.1(RAB)atHoAttpmNoInCsIrmpt(RAB)]ablishAttepmNoRabEst[ satHoSuccespmNoInCsIrr
ySuccesspmNoDirRet]
(RAB)ess(RAB)ablishSuccpmNoRabEst[ *CsSuccConnectReqpmTotNoRrceaseCsNasSi
gnRelpmNoSystem1*temptCsstablishAtpmNoIuSigEccessCsstablishSupmNoIuSigE*n

nCs)aringRrcCopmNoLoadSh-qCscConnectRe(pmTotNoRr
CsSuccConnectReqpmTotNoRrc *100

+++
(RAB)mpt(RAB)ablishAttepmNoRabEst(RAB)ess(RAB)ablishSuccpmNoRabEst*PsSucc
ConnectReqpmTotNoRrceasePsNasSignRelpmNoSystem1*temptPsstablishAtpmNoIu
SigEccessPsstablishSupmNoIuSigE*rIratCcOrdeConnectAttpmTotNoRrcselIratCellReC
onnectAttpmTotNoRrcnnPs)aringRrcCopmNoLoadSh-qPscConnectRe(pmTotNoRr
OrdercessIratCcConnectSucpmTotNoRrcllReselcessIratCeConnectSucpmTotNoRrcPsS
uccConnectReqpmTotNoRrc *100

++++

where (RAB) = PacketStream, PacketStream128, PacketInteractiveNote that one

important addition has been made to this KPI:1.By adding
pmTotNoRrcConnectSuccess(Att)IratCellResel(CcOrder) counters in the RRC term,
this KPI now also takesinto account the success rate of the PS Calls entering the 3G
network via Incoming IRAT Cell Change Order or IRAT CellReselection.[Pending
Confirmation from Ericsson]
3.1.2Overall Service Accessibility - OSAC (%)
Since there are many different services defined in UMTS and each one can have a
different accessibility at any time,an overall service accessibility can be defined to
obtain an overall measure of network accessibility averaged over allservices. This
metric can be used in case one single measurement is to be applied to sort out the
worst overallinaccessible cells.The OSAC criterion will be based on a weighted
averaging of the accessibility for the CS and PS services supported bythe cell. The
weighting factors will be chosen to be the demand for the service given by the
number of RAB Establishattempt for that service.
OSAC
= 100 * [(
CS CSSR
* CS RAB Assignment Request) + (
PS CSSR

* PS RAB Assignment Request)] /Sum(# CS & PS RAB Assignment Request)where:

CS/PS CSSR
=
Call Setup Success Rate,
as described in the previous section
.
Or simplifying:100 * [(
CS_RRC_SSR
* CS RAB Assignment Complete) + (
PS_RRC_SSR
* PS RAB Assignment Complete)]
/
Sum(# CS & PS RAB Assignment Request)where:
CS/PS_RRC_SSR
=
RRC Setup Success Rate
(with CS/PS Establishment Causes) =(# CS/PS RRC Connection Setup Complete / #
CS/PS RRC Connection Request)The KPI can be built for Ericsson in the following
way(load sharing, directed retry, Iub Sign. & NAS connection establishments have
been omitted for simplicity):Simplifying:
[]

nteractivemptPacketIablishAttepmNoRabEst+mptCs64ablishAttepmNoRabEst
+mptlishEcAttepmRabEstab+mptSpeechablishAttepmNoRabEst
nteractivemptPacketIablishAttepmNoRabEst*
nteractivemptPacketIablishAttepmNoRabEst
nteractiveessPacketIablishSuccpmNoRabEst *PsConnectReqpmTotNoRrc

PsSuccConnectReqpmTotNoRrc mptCs64ablishAttepmNoRabEst+
mptlishEcAttepmRabEstab+ mptSpeechablishAttepmNoRabEst
*mptCs64ablishAttepmNoRabEst+ mptlishEcAttepmRabEstab+
mptSpeechablishAttepmNoRabEst essCs64ablishSuccpmNoRabEst+
esslishEcSuccpmRabEstab+ essSpeechablishSuccpmNoRabEst
*CsConnectReqpmTotNoRrcCsSuccConnectReqpmTotNoRrc*100
[]

nteractivemptPacketIablishAttepmNoRabEst+mptCs64ablishAttepmNoRabEst
+mptlishEcAttepmRabEstab+mptSpeechablishAttepmNoRabEst
nteractiveessPacketIablishSuccpmNoRabEst* PsConnectReqpmTotNoRrc
PsSuccConnectReqpmTotNoRrc essCs64ablishSuccpmNoRabEst+
esslishEcSuccpmRabEstab+ essSpeechablishSuccpmNoRabEst
*CsConnectReqpmTotNoRrcCsSuccConnectReqpmTotNoRrc *100

3.2Medium Level KPIs

3.2.1RRC Connection Success Rate (%)
(For all connection requests)Low value (e.g.<95%) indicates problems to establish a
generic radio connection between UEs and RNC starting fromidle mode state.Notes:

pmNoOfReturningRrcConn (number of Load Sharing diversions when establishing an

RRC connection that returns tothe first frequency) is not available per domain (CS,
PS), so next two metrics are missing this correction.

RRC connection attempts are not corrected for emergency calls redirections.
CounterspmNoOfRedirectedEmergencyCalls and pmNoOfReturningEmergencyCalls
(MO RNCFunction) could be used to estmate theircontribution at RNC level.

Due to the fact that the UE may perform cell re-selection during the RRC Connection
establishment (it may repeatRRC Connection Request message N300 times which
may arrive at different cell) and the fact that WCDMA RAN (the RNC)does not double

count the duplicated RRC Connection Request messages received, there is a chance
that the RRC accesssuccess rate for some cells may show values above 100%. The
access success rate better than 100% happens when theattempt is registered in a
cell different to the cell where the success is registered. The end result is a slightly
better successrate for the cell that completes the access and a slightly worst
success rate for the cell where the access wasattempted/started.
3.2.1.1RRC Connection Success Rate CS (%)
(For CS connection requests)Low value (e.g.<95%) indicates problems to establish a
radio connection between UEs and RNC starting from idlemode state
in particular affecting CS services (speech and video calls).
3.2.1.2RRC Connection Success Rate PS (%)
(For PS connection requests)Low value (e.g.<95%) indicates problems to establish a
radio connection between UEs and RNC starting from idlemode state
in particular affecting PS services.
3.2.2Iu Signalling Establishment Success Rate (%)
(For all connection requests)Low value (e.g.<95%) indicates problems to establish
the Iu part of the Control Plane between the RNC and CORE.Note these counters are
in MO RNCFunction (hence, only available at RNC level)