Drive Test KPI definition and Measurement Methodology

Long Term Evolution LTE

LTE
Key Performance
Indicators

RRC SR
e-RAB SR
Authentication SR
Service request time
Latency (RTT)
Accessibility

Attach SR
VoLTE DCR
Detach SR
EMM release SR
Maximum Throughput
Average DL Throughput

Bringing the Network into good performance

in a fast and structured manner

This presentation is handling:

DT Data Collection and Conditions
E2E Field Network Performance LTE
Perform. Measurement Counters KPI LTE
Measurement Scenarios and How to Test
Server and Laptop Settings
Used Tooling

Data Collection Background/ Why not using PMC for

acceptance Reporting
Performance Measurement COUNTERS
is the recommended way of collecting performance data in a live network

Why?

But

1.
2.
3.

No additional load
Permanent Source of Information
Can be monitored all the time
PM counters does not exist for all categories and for all
individual KPIs
For this reason, terminal, server and network
traces might be also collected.

On the other hand

traces include very detailed information on call level,

which allows performance analyses of individual mobiles
and operations,

where with traces

It is possible to go further in monitoring and

optimization operations

To prove the performance

of an operating network
to reach the targeted
Quality

Field Acceptance Tests

are carried out

Performance Introduction
Performance of an operational network may be influenced by
multiple factors, detailed conditions, under which network KPIs
are valid, must be specified and agreed upon. These include
system performance, network planning and dimensioning,
measurement campaign planning and parameterization.
LTE system architecture was designed to meet the following
major goals
1.
2.
3.
4.
5.
6.

Improved system capacity & coverage

High user data rates (peak upload and
download rates)
Reduced latency (one-way delay and RTT)
Simplified architecture, IP based transport
infrastructure
Superior user experience
Seamless connection to legacy networks (GSM,
UMTS, 3GPP2/CDMA and LTE)

The selected methods and conditions of field

performance tests for LTE system to deliver the
KPI have to ensure that typical conditions in
operational networks are covered. Additionally,
the measurement conditions also include
relevant impairment factors of the radio link,
because the radio link has the most influence on
E2E performance. Especially, those
characteristics of the (OFDM) encoding
technique, which have side effects for radio
network performance are considered in the
selection of conditions, for example:
1. Sensitivity to Doppler shift
2. Sensitivity to frequency synchronization
problems
3. Sensitivity to multipath effects and cell area
(urban, sub-urban, rural)
4. Dependency on used bandwidth and
frequency range
5. Dependency on used multiple antenna
techniques - Multiple Inputs Multiple Outputs
(MIMO) (transmit diversity, spatial
multiplexing

The combination of all different options for reference conditions and measurement scenarios would result in a
very large number of test cases, which is simply not feasible. It will be the task of test specifications to select
options and scenarios out of the outlined possibilities for a given LTE performance verification campaign.

Pre-Conditions and Assumptions

Page1/2

Distinguished cell positions

KPI figures are measured on three characteristic positions of the cell
1.
2.
3.

Very Good radio conditions (line of sight close to cell center within 50m, low path loss)
Medium radio conditions (BTS distance of ~1/2 cell radius, channel with medium noise conditions, medium path losses)
Cell Edge conditions (cell overlapping area, receive power from neighbor cells at about the same level)

Channel Models
Several factors of the radio link have influence on the LTE- E2E performance of application and services.
1.
2.
3.
4.
5.
6.

UE category
Antenna systems on UE and eNB
Position and distribution of terminals in the cell, terminal movement
Load conditions in the measured cell (UL/DL, data volume)
Receive power level, interference and noise conditions, diversity and fading
Cell area, or clutter type (urban, sub-urban, rural)
Radio Conditions are formulated in terms of SINR and RSRP

In order to reduce the number of possible combinations, mobile terminal speed and radio propagation conditions for
different environments and distances were combined in "Channel Models".
The relevant channel models for LTE are defined in the following three channel models:
1.
2.
3.

EPA - Extended Pedestrian A

EVA - Extended Vehicular A
ETU - Extended Typical Urban

Page2/2

Template for the description of reference conditions includes the channel model together with other parameters
to summarize the essential conditions for measurement scenarios. The column "Reference condition" gives textual
descriptions and possible settings as abstract values only.
Parameter

Reference Condition

Terminal (UE)
Type
Category
Antenna
Position
Distribution

Mobile or smart phone, laptop with LTE card, or w/ modem

UE categories 1-5 according to [3GPP36.306];
Type: SISO, MIMO1*2, MIMO2*2, MIMO4*2, etc. Modulation: QPSK, 16QAM, 64QAM
Good, medium and cell edge (for each terminal)
Equal, or non-equal distribution of "1 to n" UEs

Network Environment
Channel Model
Backhaul Capacity
QoS Configuration
Concurrent Load
Application
Traces
Setup
Route

EPA, EVA, ETU with different Doppler frequencies

Capacities of X2, S1-U, S1-MME transport links.
Link weight and priority assigned to the flow(s)
Unloaded, or concurrent UL/DL data volumes
Application service or traffic generation for LTE E2E, EPS, E-UTRAN, EPC bearers.
Trace points & data to be collected
Trial Lab, Reference Cluster, or Simulation
In reference cluster, drive test route description.

Radio Conditions are formulated in terms of SINR and RSRP

Measurement Setup
Field network cluster
For field performance verification tests of KPIs to be executed in live network environments, the following LTE
Reference Cluster is recommended.
1.
2.
3.
4.

Sufficient number and positioning of UEs as specified by the measurement scenario. All UEs are inside of the cells
of the reference cluster.
e-UTRAN including at least three eNBs, one MME, and an integrated S-GW/ P-GW.
Each eNB supporting three LTE cells, each with predefined minimum radio conditions at cell borders.
Provisioning of network equipment and setting of configuration parameters according to the guidelines of the LTE
network operator and agreed with the vendor.

In addition to the above

1.
2.
3.

4.
5.
6.

At least three eNBs with three cells each

Trace points on all NE interfaces
Monitoring station or test equipment with adequate
protocol stack (e.g. K12xx) to decode IP and radio
network layer protocol messages
Test workstations (WS) to generate background load
WS for post-processing of traces
Operations, Administrations and Maintenance
Performance Management (OAM PM) for
monitoring counters, displaying of statistics

Field measurements # of required Samples

Statistical calculations Confidence Interval for KPI Measurement
The calculation of KPI based on the samples will take into consideration the uncertainty
due to statistics.
The below formula will then be used.
p is the quantity to be estimate (characterize the KPI)
f is the measured value of this quantity
n is the number of samples ( for instance : calls for quality and measurement points for
field level)
the measurement uncertainty is then calculated as follow :

(1)

1- = 0.95

1- = 0.98

1- = 0.99

96
171
267
384
600
1067
2401

136
241
377
543
848
1508
3393

166
296
462
666
1040
1849
4160

W/2 [in %]
10.0
7.5
6.0
5.0
4.0
3.0
2.0

(2)

In this case, the confidence interval (CI) at a 95% statistical level of the studied quantity p is :
Rules for Acceptance :
x = committed value for the KPI
y = measured value for the KPI
z = uncertainty of measurement
in case if x is a maximum (e.g. Call success rate), if y>x-z, the commitment is reached
In case if x is a minimum (e.g. Drop Call rate), if y<x+z, the commitment is reached

and

then the required number of test samples is obtained by

1.96 denotes the quintile of standard normal distribution and W denotes the width of confidence level
The table above shows the necessary number of test runs for given uncertainty ranges W/2 and given error probabilities.

Measurement Scenarios
Measurement Scenarios describes the measurement methods and recommended scenarios according
to KPI categories.

Terminology Used

Meaning for LTE Field Network Performance

Accessibility

Service accessibility, e.g. Attach, or EPS Bearer

Setup Request success rates.

Reliability

Once established, the reliability of the service, e.g.

VoIP call, or EPS bearer drop rates.

Throughput,
Latency

Certain quality, level of conformance. E.g. cell

throughput, or user data rates, packet delay.

Availability

Relationship between service up and down times,

e.g. cell, or LTE network availability

Mobility

Different mobility related metrics, e.g. hand-over

success or drop rates, latencies.

This presentation is handling:

DT Data Collection and Conditions
E2E Field Network Performance LTE
Perform. Measurement Counters KPI LTE
Measurement Scenarios and How to Test
Server and Laptop Settings
Used Tooling

E2E Field Network Performance LTE

LTE Bearer Service Architecture Overview
Data Download /
Upload
Web Browsing
Audio Video
Streaming
Conversational
Voice
LTE E2E Network
Service
Radio Bearer
Services
IP Transport
Services
LTE Network
Elements

Bearer Concept

E-UTRAN

EPC

Internet

Quality of Experience
Layers 4 7 :
Layer 3:

eNB

IP

Layer 2: NAS
PDCP
RLC
MAC
Layer 1:

UE
TE

PHY

S-GW,
MME

P-GW

Peer
Entity

LTE End-to-end Network Service

EPS Bearer

External Bearer

MT
E-RAB
Radio Bearer

S5/S8 Bearer
S1 Bearer

Quality of Service
LTE Uu

S1

Performance Measurements Counters

RU30 KPI formulas

S5/S8

LTE_RL30_counter_
based_KPIs.zip

SGi

Service Accessibility Measurements

Accessibility KPIs characterize the accessibility of a service, or service element to its users. They are
expressed as a ratio of successful service requests to the total number of attempts. (This group of KPIs
corresponds to the category of "service accessibility KPIs).
# successful service requests
Success Rate =
*100[%]
# total attempts
The KPI value is calculated as
number_of (RRC_CONN_RECONFIGURATION_COMPLETE)
EPSSR =

number_of (RRC_CONNECTION_REQUEST)

Parameter

Reference Condition

Terminal (UE)
Type
Category
Antenna
Position
Distribution

Laptop with LTE card, or modem.

UE category according to [3GPP36.306];
One antenna: e.g. SISO
Good, medium and cell edge area.
n.a. (one terminal only)

Network Environment
Channel Model
Backhaul Capacity
QoS Configuration
Concurrent Load
Application
Traces
Setup
Route

EVA0, EVA70: stationary, mobile w/ ~50 km/h

Capacities of X2, S1-U, S1-MME transport links.
n.a.
Unloaded or concurrent UL/DL data volumes of low and medium levels.
Procedure dependent test script for automated execution of different applications.
Data collected by test script. Monitoring of online statistic counters.
Field Network Cluster and Trial Lab.
Real drive test routes (in Cluster), or simulated with varying
channel models (in Lab).

*100%

Reliability Measurements (Service Drop Rates)

Attach, Service Request, Register, etc. are examples of service requests on different Service levels; service
requests establish a relationship between the UE and the network or application. The relationship is normally
terminated with a "Release Request" by the UE. In case of network errors (e.g. handover failures), or
insufficient radio resources the relationship can be terminated unexpectedly. The ratio of such "abnormal"
terminations to the number of all established relationships is given by "drop rate" KPIs.
The Service drop rates 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

EPSBearerD R =

number_of (dropped_c alls)

100%
number_of (successfu ll_calls)

Throughput Measurement (1/3)

Distinguished cell positions
Throughput is the primary metric for the characterization of the LTE radio technology (OFDMA) in DL, Single-Carrier
Frequency Division Multiple Access (SC-FDMA) in UL). The throughput the LTE system can offer depends on many factors:
a)
b)
c)
d)

Channel environment (e.g. stationary or mobile, speed) and fading conditions

Reception conditions impaired by traffic load levels, and by interference between the cells, in short by the
user's SINR
Network layout, type of antenna
Position of users in the cell (implies e.g. path loss and fading)

Thats why the location of the mobile terminal in the cell will strongly influences the data rate that can be experienced by the
user. For this reason, the capacity of an LTE cell is characterized by two distinguished metrics, one viewing capacity from the
operator's point of view (How many users can be supported by the cell?), the other from the end-user perspective:
a)
b)

Cell Throughput, and

Peak User Data Rate-loss and fading

Tests to be made at
locations within the cell's
main beam

Cell Throughput (2/3)

The metric "Cell Throughput" shows the sustainable
aggregate cell capacity available to a number of "n" users.

R4
R3

Distribution of Users for Cell Throughput measurements

shows how users are arranged for cell throughput

measurements. Each user position is characterized by
different combinations of path loss, receive signal, and
neighbor cell interference strengths.

R2
R1

The measurement is done with stationary terminals to avoid

the impact of movement and Hand-Over (HO). The latter
implies that for those mobiles that are located at the cell
edge, HO must be prevented on the UE or by the network.
The default backhaul capacity of S1-U transport links are to be controlled and modified if necessary to
prevent this link becoming a bottleneck during the measurement. The modified value should become
default for subsequent measurements. Cell throughput measurements should be executed with an
increasing number of UEs starting with 1. While the first test case corresponds to the peak user data rate
measurement, the subsequent ones illustrate the dependency of this KPI on the number of active users.

User Data Rate (3/3)

The "Peak User Data Rate" metric describes the data capacity
that is available to one user in a cell. Data rate is the most
important single factor which influences the end-user
experience of non-real-time application services, like web
browsing, email, File Transfer Protocol (FTP) up/ downloads,
and interactive gaming, due to its impact on (signaling and data)
transfer delays.
Parameter
Terminal (UE)
Type
Category
Antenna
Position
Distribution
Network Environment
Channel Model
Backhaul Capacity
QoS Configuration
Concurrent Load
Application
Traces
Setup
Route

R4
R3
R2
R1

Reference Condition
Smart phone and laptop with LTE card
Corresponding UE categories
Types: SISO, MIMO 1*2, 2*2, etc.
Good, medium, and cell edge (Distinguished
One single terminal

Cell Position)

EPA, EVA stationary and mobile w/ 3, 50 km/h

Capacities of X2, S1-U, S1-MME transport links.
Non-real-time QoS, equal weights and priorities
Unloaded
FTP upload, download; separate
UE, eNB, FTP Server; Uu, S1-U, S1-MME, X1, ...
Reference cluster in live network
Drive test route passing good and medium cell positions, and crossing cell borders.

Latency measurement
The benchmark measurement for finding the E2E latency of LTE access networks for data applications is the
Round Trip Time (RTT) measurement. RTT is measured with the Ping application of the UEs operating
system or with a comparable measurement tool. It records the time difference between sending an Internet
Control Message Protocol (ICMP) Echo Request to an IP host, and the reception of the corresponding ICMP
Echo Reply message.
The measurement can be executed between a mobile terminal and an IP host, which is configured to respond
to ICMP Echo Requests. This way, round trip delays can be measured between UE - eNB (LTE Uu), UE - S/PGW (E-UTRAN Radio Access Bearer (E-RAB), EPS) and UE - AS (LTE E2E), respectively. The measurement
can (and should) be executed in both directions.
The Ping application sends successive ICMP Echo Requests
1. either upon reception of the ICMP Echo Reply to the previous request,
2. or after a predefined period of time (in the range of ~100ms to 1s)
The total number of measurements per cycle should be chosen so that results have the required statistical
confidence level. The recommended number of measurements per IP host is 100.

Mobility (handover) measurements

The HO KPIs are measured under the following variations of conditions:
1.
2.
3.

Unloaded versus loaded cell conditions for Intra RAT, ideal conditions in target cell for Inter Radio Access
Technology (RAT) (GSM, UMTS) hand-over scenarios
Mobile terminals with vehicular speed
Drive routes from good reception condition (in the originating cell) over hand-over area to a good position
on the destination cell
Parameter
Terminal (UE)
Type
Category
Antenna
Position
Distribution
Network Environment
Channel Model
Backhaul Capacity
QoS Configuration
Concurrent Load
Application
Traces
Setup
Route

Reference Condition
Smart phone, laptop with LTE card
UE category tbd. according to [3GPP36.306];
One antenna: e.g. SISO
Good/medium in originating cell directly across hand-over area to good/medium position in new cell.
n.a.
EVA0, EVA70: stationary, mobile w/ ~50 km/h
n.a.
n.a.
Unloaded and loaded destination cell in UL/DL.
UDP data stream in DL with hand-offs acc. to reference traffic model.
MT, Source and Target eNBs, mobility events
Reference Cluster, Trial Lab
In reference cluster, drive test route description.

The drive test has to be repeated at least 20 times to get the required level of statistical confidence. All reasons for
handover failures (no resources in target cell, service not supported, etc.) should be excluded.

Intra eNodeB

eNodeB1

eNodeB1

Handover between cells (having different coverage

areas) within one eNB
Smart phone, laptop with LTE card
Datacard status: active, subscriber attached, Data call established
Trigger subsequent Intra eNodeB HoV procedures by moving to the next
cell (Same eNodeB).
Drive clock wise and anticlockwise to Intra eNB Handover Functionality
One log will be generated for clockwise and one log file for anticlockwise

Intra eNB handover

functionality will be
tested along with
coverage check

Clockwise
eNodeB1

Anti- Clockwise
eNodeB1

Handover Procedure
Before handover

Handover
preparation

SAE GW

SAE GW

MME

Source
eNB

MME

Radio handover
SAE GW
MME

Target
eNB

= Data in radio
= Signalling in radio
= GTP tunnel
= GTP signalling

= S1 signalling
= X2 signalling

Late path
switching
SAE GW
MME

Inter eNodeB Handover

Smart phone, laptop with LTE card
SAE GW

Data card status: active, subscriber attached, Data call

established
Trigger subsequent Intra eNodeB HoV procedures by
moving to the next cell (other eNodeB).

MME

Execute the test bidirectional

One log will be generated for clockwise
and one log file for anticlockwise

Inter eNB handover

functionality will be
tested along with
coverage check

Source
eNB

Target
eNB

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
Target KPI values (ms)

Initial Attach
Re-Attach (w/o
Authentication)

Min
Unloaded
241

Mean Load 95%-ile Load

A
A
110
271

125

362

145

Field KPI
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)
Detach Time

Min Unloaded Mean Load A 95%-ile Load A

46
66
88

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:

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
LTENwAttSR

number
number

_ of _ successful
_ of _ successful

l _ attachment
l _ attachment

s
100 %
s

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].

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
Target KPI values (ms):

Min Unloaded Mean Load A 95%-ile 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

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

Target KPI values (ms):

Min Unloaded Mean Load A 95%-ile 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

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.

Field KPIs
Service Request Success Rate Continued

Formula:
EPSSR

number_of

(RRC_CONN_
RECONFIGUR
ATION_COMP
number_of
(RRC_CONNE
CTION_REQU
EST)

LETE)

100 %

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

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_c
alls)
EPSBearerD

Target KPI values: < 2%

R =

number_of

(successfu

ll_calls)

100 %

This presentation is handling:

DT Data Collection and Conditions
E2E Field Network Performance LTE
Perform. Measurement Counters KPI LTE
Measurement Scenarios and How to Test
Server and Laptop Settings
Used Tooling

RL30/RL25 Measurements
Measurements summarized
MEAS ID
M51120
M51121
M51122
M51123
M51125
M51126
M51127
M51128
M51129
M51130
M51131
M51132
M51136
M8000
M8001
M8004
M8005
M8006

Measurement
LTE_IP_Stats
LTE_PHB_Stats
LTE_TOP_Stats
LTE_Ethernet_Link
LTE_IPSec
LTE_IP_Filtering
LTE_VLAN_IP_Stats
LTE_VLAN_PHB_Stats
VLAN_stats
LTE_ETHIF_stats
LTE_L2SWI_Stats
LTE_TWAMP_Stats
LTE_TAC_Stats
LTE_S1AP
LTE_Cell_Load
LTE_Transport_Load
LTE_Pwr_and_Qual_UL
LTE_EPS_Bearer

MEAS ID
M8007
M8008
M8009
M8010
M8011
M8012
M8013
M8014
M8015
M8016
M8017
M8018
M8019
M8020
M8021
M8022
M8023

Measurement
LTE_Radio_Bearer
LTE_RRC
LTE_Intra_eNB_HO
LTE_Pwr_and_Qual_DL
LTE_Cell_Resource
LTE_Cell_Throughput
LTE_UE_State
LTE_Inter_eNB_HO
LTE_Neighb_Cell_HO
LTE_Inter_Sys_HO
LTE_ISYS_HO_UTRAN_NB
LTE_eNB_Load
LTE_ISYS_HO_GSM_NB
LTE_Cell_Avail
LTE_Handover
LTE_X2AP
LTE_UE_and_ServDiff

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.

Logical formula
E-RAB SSR=(E-RAB setup
successes / E-RAB setup
attempts)*100%

Summarisation
formula (PI ID)

Summarisation formula (Abbreviation)

100*sum([M8006C1]) /
sum([M8006C0])

100*sum([EPS_BEARER_SETUP_COMPLETIONS]) /
sum([EPS_BEARER_SETUP_ATTEMPTS])

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.
Logical formula
E-RAB NRR UP=(normal ERAB releases user
perspective / all E-RAB
releases)*100%

Summarisation
formula (PI ID)

Summarisation formula (Abbreviation)

100*sum([EPC_EPS_BEARER_REL_REQ_NORM]+
EPC_EPS_BEARER_REL_REQ_DETACH]+
[ENB_EPSBEAR_REL_REQ_RNL_REDIR]+
[ENB_EPS_BEARER_REL_REQ_RNL_INA]) /
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])

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.
Logical formula

Summarisation
formula (PI ID)

Summarisation formula (Abbreviation)

100*sum([SUCC_INTRA_ENB_HO]) /
sum([ATT_INTRA_ENB_HO])

Intra HO SR =(number of successful intra eNB

HOs) /
(number of intra eNB HO attempts)*100%

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.
Logical formula

Summarisation
formula (PI ID)

Summarisation formula (Abbreviation)

100*sum([SUCC_INTER_ENB_HO]) / sum
([ATT_INTER_ENB_HO])

Inter X2 based HO SR =(number of successful

inter eNB X2 based HOs) /
(number of inter eNB X2 based HO
attempts)*100%

KPIs followed and reported from live LTE networks

(by Technical Support)
current
week2

current
week1

current
week

trend

NSN
Benchmark

Comments

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 Rate

[%] (LTE_5218c)

99,05

98,79

99,42

98,099,5%

eRAB Setup Success Ratio

[%] (LTE_5017a)

99,80

99,78

99,92

99,099,5%

6,1

5,86

2,60

1,0-5,0%

4,51

4,87

2,73

tbd

99,63

99,75

99,48

99,099,5%

NW KPI

eRAB Drop Ratio [%]

(LTE_5025b)

eRAB Drops per PDCP Vol.

[#/GB]
(LTE_5812a)

Intra LTE Handover

Success Rate [%]
Avg(LTE_5035a;LTE_5048b)

Improved after completion of the SW upgrade to RL20

5.0.2 on 29.02.2012. inactivityTimer has also been
changed from 30 to 20 seconds.

This presentation is handling:

DT Data Collection and Conditions
E2E Field Network Performance LTE
Perform. Measurement Counters KPI LTE
Measurement Scenarios and How to Test
Server and Laptop Settings
Used Tooling

Overview of settings to be deactivated

Security tasks and settings to be deactivated
Firewalls should be deactivated (External and Windows-Internal)
Virus scanner have to be deactivated
Special security scripts/tasks of company PCs have to be deactivated.

Automatic updates to be deactivated

Automatic Windows update feature
Automatic Error-Reports to Microsoft
MS Internet Explorer
MS Media Player
Automatic updates of Virus Scanner
Windows Time Update
Automatic Update of any other installed application

Network requests to be deactivated for each modem connection

NetBIOS over TCP/IP
LMHOSTS-requests

Example of throughput degradation (ethereal trace)

Automatic Microsoft
Windows-Update
causes FTP
download
interruption for
about 6 sec.
This causes an
drastic degradation
of the throughput
average

How to deactivate Windows XP Firewall

Deactivate Windows XP
Firewall
START Settings Control
Panel Security Center
Windows Firewall

Detailed_View

Deactivate
Windows XP
Firewall

How to deactivate Windows XP Automatic Updates

Deactivate Windows
XP Automatic
Updates

Detailed_View

Deactivate
Windows XP
Automatic
Updates

START Settings
Control Panel
Security Center
Automatic Updates

How to modify Windows XP Internet Explorer

Modify Windows XP internet options for Internet Explorer
START Settings Control Panel Internet Options Advanced
Deactivate
Automatically check
for Internet Explorer
updates
Deactivate Enable
Install On Demand
(Internet Explorer)

Detailed_View

Deactivate Enable
offline items to be
synchronized on a
schedule

How to deactivate WinXP Automatic Error-Reports to

Microsoft (1/2)
Deactivate WinXP
Automatic ErrorReports to
Microsoft

Activate
Disable error
reporting

START Settings
Control Panel
System Advanced
Error Reporting
Detailed_View

How to deactivate WinXP Automatic Error-Reports to

Microsoft (2/2)
Activate Startup
Type to Disabled

Detailed_View

How to modify WinXP Media Player

Modify Windows XP
Media Player
description depends
on used MP version
Open MS Media
Player Tools
Options Privacy

Deactivate Privacy
settings of MS Mediaplayer, not to connect the
internet

How to deactivate Windows XP Time Update

Deactivate Windows XP Windows Time Update
Open Date and Time properties by double-click on clock display at the windows task bar
Deactivate Automatically synchronize with an Internet time server

Deactivate
Detailed_View

Automatically
synchronize with an
Internet time server

How to deactivate NetBIOS over TCP/IP and

LMHOSTS-req
Deactivate Enable
LMHOSTS lockup

Deactivate Windows
XP NetBIOS over
TCP/IP and
LMHOSTSrequests

Open Dialup Con.

Properties
IP Protocol
Advanced
WINS

Detailed_View

NOTE:
Activate Disable
NetBIOS over TCP/IP

This modifications
have to be done for
each configured dialup
connection specially !!!

This presentation is handling:

DT Data Collection and Conditions
E2E Field Network Performance LTE
Perform. Measurement Counters KPI LTE
Measurement Scenarios and How to Test
Server and Laptop Settings
Used Tooling

Used Drive Test Solution

Scanners, NEMO FSR1
1. Multi-band multi-RAT, up to 8 bands
simultaneously
2. FDD bands
3. TDD bands 36 and 38

Qualcomm chips:
MDM9200, MDM9600
Huawei E398 dongle
LTE Classic Analyzer

Questions? Comments?
We are happy to help you!

ZORO Group