Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 21

NSN KPIs, overview

Soc Classification level


1 Nokia Siemens Networks /
Outline

NSN counter-based KPIs


NSN field test KPIs

Soc Classification level


2 Nokia Siemens Networks Presentation / Author / Date
RL40/RL35 counters and KPIs
RL40/RL35 counters and KPIs attached
Latest counter and KPI info available in JUMP:
http://nop-i.nokiasiemensnetworks.com/pl_login.php
NPO KPI documentation folder
https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/383538045
Official benchmark KPIs are in CuDo: Specifications of LTE RAN Key
Performance Indicators
This is a link to latest (Product Finder Search)

LTE RAN Key


worksheet
Performance Indicators RL40
Worksheet in worksheet 09_KPI_Overview FDD_RL40.xls
09_KPI_Overview TDD_RL35.xls
09_KPI_overview_RL40.xls

Soc Classification level


3 Nokia Siemens Networks /
RL40/RL35 measurements
RL40/RL35 measurements summarized
http://nop-i.nokiasiemensnetworks.com/pl_login.php

Soc Classification level


4 Nokia Siemens Networks Presentation / Author / Date
Accessibility
E-UTRAN E-RAB Setup Success Ratio
The KPI describes the setup success ratio of the elementary E-RAB setup
procedure used to setup the E-RAB between MME and UE.
It indicates the E-UTRAN contribution to network accessibility for the end-
user, not the whole end-to-end service accessibility.

Summarisation
Logical formula formula (PI ID) Summarisation formula (Abbreviation)
E-RAB SSR=(E-RAB 100*sum([M8006C1]) / 100*sum([EPS_BEARER_SETUP_COMPLETIONS])
setup successes / E- sum([M8006C0]) / sum([EPS_BEARER_SETUP_ATTEMPTS])
RAB setup
attempts)*100%

Soc Classification level


5 Nokia Siemens Networks /
Retainability
E-RAB Normal Release Ratio, User perspective
This KPI describes the ratio of normally released E-RABs from user
perspective. This KPI is corresponding to a Connection Completion Ratio.

Summarisation
Logical formula formula (PI ID) Summarisation formula (Abbreviation)
E-RAB NRR 100*sum([EPC_EPS_BEARER_REL_REQ_NORM]+
UP=(normal E-RAB EPC_EPS_BEARER_REL_REQ_DETACH]+
releases user [ENB_EPSBEAR_REL_REQ_RNL_REDIR]+
perspective / all E-RAB
[ENB_EPS_BEARER_REL_REQ_RNL_INA]) /
releases)*100% sum([EPC_EPS_BEARER_REL_REQ_NORM]+
[EPC_EPS_BEARER_REL_REQ_DETACH]+
[EPC_EPS_BEARER_REL_REQ_RNL]+
[EPC_EPS_BEARER_REL_REQ_OTH] +
[ENB_EPSBEAR_REL_REQ_RNL_REDIR]+
[ENB_EPS_BEARER_REL_REQ_RNL_INA] +
[ENB_EPS_BEARER_REL_REQ_RNL_RLF]+
[ENB_EPS_BEARER_REL_REQ_TNL]+
[ENB_EPS_BEARER_REL_REQ_OTH])

Soc Classification level


6 Nokia Siemens Networks /
Mobility
E-UTRAN HO Success Ratio, intra eNB
This KPI describes the success ratio for the handover execution phase,
when the source eNB receives information that the UE successfully is
connected to the target cell within own eNB.

Summarisation Summarisation formula


Logical formula formula (PI ID) (Abbreviation)

Intra HO SR =(number of successful 100*sum([SUCC_INTRA_ENB_HO]) /


intra eNB HOs) / sum([ATT_INTRA_ENB_HO])
(number of intra eNB HO
attempts)*100%

Soc Classification level


7 Nokia Siemens Networks /
Mobility
E-UTRAN HO Success Ratio, inter eNB X2 based
This KPI describes the success ratio for the inter eNB X2 based handover
execution phase, when the source eNB receives information that the UE
successfully is connected to the target cell within target eNB.

Summarisation Summarisation formula


Logical formula formula (PI ID) (Abbreviation)

Inter X2 based HO SR =(number of 100*sum([SUCC_INTER_ENB_HO]) /


successful inter eNB X2 based HOs) / sum ([ATT_INTER_ENB_HO])
(number of inter eNB X2 based HO
attempts)*100%

Soc Classification level


8 Nokia Siemens Networks /
KPIs followed and reported from live LTE networks
(by Technical Support)
current current NSN
current
NW KPI week week
week
trend Bench- Comments
2 1 mark

Cell Availability
excl. BLU [%]
(LTE_5239a)
99,5 99,53 94,16 >99,5%
NA05096336 250 eNBs down after Plan
Operation failure

RRC Setup Success


99,05 98,79 99,42 98,0-

EXA
Rate [%] (LTE_5218c) 99,5%

MPL
eRAB Setup Success
Ratio [%] (LTE_5017a) 99,80 99,78 E
99,92 99,0-
99,5%

eRAB Drop Ratio [%]


(LTE_5025b)
6,1 5,86 2,60 1,0-
5,0% Improved after completion of the SW
upgrade to RL20 5.0.2 on 29.02.2012.
eRAB Drops per inactivityTimer has also been changed
PDCP Vol. [#/GB]
(LTE_5812a)
4,51 4,87 2,73 tbd from 30 to 20 seconds.

Intra LTE Handover


Success Rate [%]
Avg(LTE_5035a;LTE_5048b)
99,63 99,75 99,48 99,0-
99,5%

Soc Classification level


9 Nokia Siemens Networks /
And so on counters and network KPIs

Once again the main links:

Please see JUMP for latest counter-based KPIs


http://nop-i.nokiasiemensnetworks.com/pl_login.php

NPO KPI documentation folder


https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/3835
38045

Official customer counter-based KPIs are in CuDo:


Specifications of LTE RAN Key Performance Indicators
This is a link to latest customer KPI CuDo (Product Finder Search)

Soc Classification level


10 Nokia Siemens Networks /
Outline

NSN counter-based KPIs


NSN field test KPIs

Soc Classification level


11 Nokia Siemens Networks Presentation / Author / Date
Field KPIs important links

Definitions and performance targets


https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/437652090

Field KPI References:


LTE E2E Field Network Performance - KPI Targets for RL30, Internal Version
LTE E2E Field Network Performance - KPI Targets for RL25TD, Internal Version
NPO project/trial reports
NPO KPI material (FDD)
TD-LTE KPI Optimization Guidelines for RL15TD

In the following slides some examples to follow

No NSN customer specific field KPI templates/workbooks


available for Actix or Nemo Analyze yet.
If your project needs these, please collect example drive
test logs and contact tommi.mecklin@nsn.com
Soc Classification level
12 Nokia Siemens Networks /
Field KPI
Attach Time
With Attach, the mobile terminal registers at the LTE network. At the end of
the procedure the UE is authenticated, and a default (nGBR) bearer is
established.
The Attach Time is the interval between the connection request and the
acknowledgement of the positive response by the UE.

Mean value and 95% from all measured samples


Formula : Attach Time [ms] = tAttach Complete tAttach Request

Related E-UTRAN Counters & KPIs


None
Min
Target KPI values (ms) Unload Mean 95%-ile
ed Load A Load A
Initial Attach241 110 271
Re-Attach (w/o
Authentication
) 125 362 145
Soc Classification level
13 Nokia Siemens Networks Presentation / Author / Date
Field KPIs
Detach Time
With an explicit Detach request the UE informs the LTE network that it does
not want to access the EPS any longer. At the end of the procedure all EPS
bearers of the UE are released.
The Detach Time is the interval between the Detach Request and the
reception of a Detach Accept message by the UE. No Detach Accept is sent
by the network if the cause for Detach is switching the UE off.

Formula : Detach Time [ms] = tDetachRequest tDetachAccept

Related E-UTRAN Counters & KPIs


None
Target KPI values (ms)
Min
Unload Mean 95%-ile
ed Load A Load A
Detach Time 46 66 88

Soc Classification level


14 Nokia Siemens Networks Presentation / Author / Date
Field KPIs
Attach Success Rate
The Attach Success Rate is defined as the ratio between the number of
successful registrations and the number of all requests. This is the
probability that a user can attach to the LTE network at any moment of time.
The calculated success ratio figure excludes attach requests, which are
rejected by authentication failures. On the other hand, network attach
requests which are terminated by timer expiry (due to the unavailability of
some LTE resource) are considered as unsuccessful registrations.
If the success rate is calculated on the eNB by counting incoming RRC
requests, RRC CONNECTION REQUEST retries are to be excluded, since
they would increase the overall number of establishment attempts, and thus
reduce the success ratio.
Formula: number _ of _ successfull _ attachments
LTENwAttSR 100%
number _ of _ attempts

Target KPI values: 95%


Related E-UTRAN Counters & KPIs
PM counters: LTE EPS Bearer - M8006;
KPIs: Initial E-RAB Setup Success Ratio (ISSR) - LTE_5112a
Soc Classification level
15 Nokia Siemens Networks Presentation / Author / Date
Field KPIs
Service Request Time: UE Initiated
It is the time taken by the LTE network to setup an EPS bearer on
request by the UE. The EPS bearer can be new (dedicated), or an
existing one (e.g. the default EPS bearer). The latter is needed to reassign
Uu radio and S1 bearer resources to the existing EPS bearer of
a previously Idle UE.
The EPS bearer has to be created or activated before IP packets can
be exchanged, i.e. the Service Request creates the IP link dynamically
over the mobile access (LTE) network.
The UE Initiated EPS Bearer Setup Time is the interval between the
submission of the message RRC CONNECTION REQUEST (see References
26. [3GPP36.331]) carrying a NAS: Service Request message
in its body, and the reception of the RRC CONNECTION RECONFIGURATION
response by the UE. The Bearer Setup procedure is based
on the Service Request procedure, see References 3. [3GPP23.401]
and 20. [3GPP36.300].

Soc Classification level


16 Nokia Siemens Networks Presentation / Author / Date
Field KPIs
Service Request Time: UE Initiated Continued
Mean value and 95% from all measured samples
Formula:
Service Request Time [ms] = tRRC_Reconfig tRRC_Request

TargetMinKPI values (ms):


Unload Mean 95%-ile
ed Load A Load A
UE
initiated 95 122 110

Related E-UTRAN Counters


Mean EPS Setup Time: SAEB.EstabTimeMean.QCI
Max EPS Setup Time: SAEB.EstabTimeMax.QCI

Soc Classification level


17 Nokia Siemens Networks Presentation / Author / Date
Field KPIs
Service Request Time: Network Initiated
It is the time taken by the LTE network to set up an EPS bearer on
request by the P-GW. The EPS bearer has to be created before IP
packets can be sent (DL) to the UE if the UE has no proper EPS bearer
for the given IP packet flow. The network initiated Service Request
Time includes a Paging Time (ref. to Paging Time) if the UE is idle. The
EPS Bearer Setup procedure is based on the Paging and Service
Request procedures according to References 26. [3GPP36.331] and 3.
[3GPP23.401].
Mean value and 95% from all measured samples
Formula: Service Request Time [s] = tRRC_Reconfig tRRC_Request
Min

Target
KPI values (ms): Unload Mean 95%-ile
ed Load A Load A
NW initiated (w/o
Paging) 172 145 212

Related E-UTRAN Counters (same as UE Initiated)


Mean EPS Setup Time: SAEB.EstabTimeMean.QCI
Max EPS Setup Time: SAEB.EstabTimeMax.QCI
Soc Classification level
18 Nokia Siemens Networks Presentation / Author / Date
Field KPIs
Service Request Success Rate
This KPI is defined as the ratio between successfully established EPS
bearers compared to the overall number of EPS bearer establishment
attempts. It corresponds to the probability that a user or the LTE network
can establish an EPS bearer at any moment in time.
Requests that are terminated by timer expiry (due to the non-
accessibility of some LTE resource) are considered as unsuccessful
attempts. Authentication errors (requests rejected by the MME) are
included in the total number of failures.
Only the first RRC CONNECTION REQUEST is to be considered, since
counting retries of the same message would increase the overall number
of bearer establishment attempts, and thus reduce the success ratio.

Soc Classification level


19 Nokia Siemens Networks Presentation / Author / Date
Field KPIs
Service Request Success Rate Continued
Formula:
number_of (RRC_CONN_RECONFIGURATION_COMP LETE)
EPSSR 100%
number_of (RRC_CONNECTION_REQUEST)

Target KPI values: 98%


Related E-UTRAN Counters & KPIs
Group of related PM counters: LTE EPS Bearer - M8006
KPI: Additional E-RAB Setup Success Ratio (ASSR) -
LTE_5113a

Soc Classification level


20 Nokia Siemens Networks Presentation / Author / Date
Field KPIs
Service Drop Rate
It is the ratio between abnormally released bearers and the overall number
of established EPS bearers. An abnormal release is defined as any EPS
bearer termination that was not triggered by the mobile user (from UE side).
Thus, it reflects the probability that an established bearer is aborted due to
insufficient network resources.
Dropping the bearer becomes visible to the end-user if an application
service is actively using it. If the application automatically re-establishes the
bearer, it remains unnoticed by the user.
Formula: number_of (dropped_calls)
EPSBearerD R 100%
number_of (successfu ll_calls)

Target KPI values: < 2%

Soc Classification level


21 Nokia Siemens Networks Presentation / Author / Date

You might also like