2G Drive Testing

6. 2G Drive Testing and KPI 2 days

Topics:
Drive Test Process
Customer Experience KPI
Setup System Test
Drive Testing
Drive Testing Analysis
 Drive Test Process
Data Preparation and
Collection
Data Analysis
Services to test
Levels of Reporting

Drive
Trouble Shooting
Cluster Preparation KPI definitions
Failure Type Breakdown Root Cause Analysis
Define Cluster Equipment
Post Processing Corrective Action
Define Drive Route Exclusions
functionality Further data logging
Call Patterns
KPI Gap Analysis
OSS Alarms
Network Stats

Why Drive the Network ?

New Site Integration
RF Tuning
Network Optimisation
Network Benchmarking (Golden clusters)
Release Testing
Drive test Performance

There could be many reason for poor Performance, for example

Radio Conditions
UE Category & Performance
Measurement tools & Settings
Server location and settings
HLR QoS Profile
Network Configuration and Parameters
Radio Conditions and Coverage

In general, KPI values are valid in regions with sufficient coverage and under good radio conditions.
Test is to be done inside the coverage area
In case coverage requirements is met but call fails due the coverage, these samples are to be excluded
from the analysis
RSCP
Example of Call Success Criteria Ec/No
Signal Call
above OK
Signal above
Call Call - (B) Ec/No
RSCP Call
- 80dBm OK
NOK - 5dB threshold
threshold

- -95dBm - 12dB
Signal Signal
below below
RSCP Call Ec/No
threshold -110dBm
Threshold
OK
Call
- 20dB threshold
Call - (A) NOK Discard sample

Time
 Drive Test Equipment
Drive Test tool with Scanner and UE is required (for example Nemo Outdoor)
The Scanner measures all used carriers/cells and their corresponding DL scrambling codes,
UE only measures SC signals from the cells that the system has informed/ordered the UE through the BCH
(neighbour list) or via the measurement control message
UE: Scanner:
RSCP Active/Monitored Set For low coverage areas
Carrier RSSI
For Antenna Installation problems
Ec/No Active/Monitored Set
For Missing neighbours
UL/DL Data Throughput
The BLER downlink For Coverage optimisation (e.g. Overshooting)
Pilot BER External interferer detection
Random Access Initial Tx Power With Scanner you can get following info from the
Random Access Preamble Count & Step surrounding cells:
SIR target (UE dependent) Different SC / BCCH
UE Tx Power CPICH RSCP / RxLev value (dBm)
Call Statistic: AMR, CS and PS data calls CPICH EcNo / RxQual value (dBm)
Signalling, QoS profile
Important to drive with call logging equipment and LTE/3G/2G scanner in the same car
 Drive test KPIs for CS

Drive test KPIs for CS domain All Mobility measurements

PI # FPI Name Triggering Maximum Results Normal Results Test Setup

MOC setup time is the interval between the submission of the "RRC
Call Setup Time - Voice MOC @
FPI_6a CONNECTION REQUEST" message and the reception of the L3 2.1 sec 3.5 sec 1 UE MOC to test number:
95%
msg "CC ALERTING" at a UE.

Ratio between successfully established CS voice calls compared to

Call Setup Success Rate - Voice
FPI_7 the overall number of voice call establishment attempts - DL direct 99% 1 UE MOC to test number:
(%)
transfer (CC: alerting) message is received by UE

Ratio between abnormally released voice calls and the overall

FPI_9 Drop Call Rate - Voice (%) number of established voice calls (e.g. RRC Connection Release 1% 1 UE MOC to test number:
message is received before UL/DL CC: disconnect )

Call Setup Time - Voice MMC RRC Connection request message to DL direct transfer (CC: 2 UE (MOC+ MTC) from
FPI_6b 3.8 sec* 6.5 sec
(sec) alerting) msg. moving UE to stationary
Drive test KPIs for CS Test Setup
Typically a few different type of call scenarios is used to measure CS KPIs.
Call length have impact for the drop call rate, at least 90 sec call should be used to measure drop call rate. Shorter
call can be used to measure CSSR.
Call length has no impact for the call setup times.
ISHO measurement require dual mode UE, but for KPIs UE is typically locked.
Below some possible call scenarios that can be used to measure CS KPIs
90 sec call with 15 sec idle from UE to PSTN UE locked
Drop call rate
MOC call setup time
SHO success and overhead
30 sec call with 15 sec idle from 3G to 3G UE locked (B-party stationary)
CSSR (voice)
MMC call setup time
30 min long call UE in dual mode
ISHO success
Drive test KPIs for CS Call setup success and Setup time
Call setup success & time is measured between RRC Connection request and Alerting
UE Node B RNC CN

RRC Connection Request (RACH)

RRC Connection Setup (FACH)

RRC Connection Setup Complete (DCH)
Initial Direct Transfer (CM Service Request)
RANAP: Initial UE msg.

DIRECT TRANSFER (CM service Accept)

Call Setup Success &
DIRECT TRANSFER (Setup) Time

DIRECT TRANSFER (Call Proceeding)

RANAP: RAB Assignment Request

RRC: Radio Bearer Setup

RRC: Radio Bearer Setup Complete

RANAP: RAB Assignment Response

DIRECT TRANSFER (Alerting)

DIRECT TRANSFER (connect)
DIRECT TRANSFER (connect Acknowledge)
 Drive Test KPIs for PS Success and Drop ratios
Drive test KPIs for PS Domain
Maximum Normal
PI # FPI Name Triggering Test Setup
Results Results

FPI_20 Average GPRS Attach Time (sec) RRC Connection request message to Attach Accept message 1 PS MOC UE
1.5 sec 2 sec
Between the "RRC CONNECTION REQUEST" msg. and the
reception of the L3 message "ACTIVATE PDP CONTEXT
FPI_21a Average PDP Context Activation time 1 PS MOC UE
ACCEPT" at a UE.
Time for Attach not included 1.4 sec 2 sec
RRC Connection request message to Activate PDP context
FPI_22 Activate PDP Context Success Rate (%) 99% 1 PS MOC UE
Accept message
Number of successful PS setups - number of lost PS
FPI_27 PS Retainability ratio (%) 99% 1 PS MOC UE
sessions/Number of established PS sessions.
Drive Test KPIs for PS GPRS Attach Time
GPRS Attach Time is measured between RRC Connection Request and Attach Accept
UE Node B RNC CN

RRC Connection Request (RACH)

RRC Connection Setup (FACH)

RRC Connection Setup Complete (DCH)

Initial Direct Transfer GPRS Attach Request (DCH)
RANAP: Initial UE msg.
DIRECT TRANSFER (Authentication and ciphering request)
DIRECT TRANSFER (authentication and ciphering response) PS attach time

Security mode command

Security mode complete

Downlink direct transfer: common id

Uplink Direct transfer: identity response

Downlink direct transfer: Attach Accept

Uplink Direct transfer: Attach Complete

Drive Test KPIs for PS PDP context activation time and success
PDP Context Activation Time is measured between RRC Connection Request and Activate PDP
context Accept
UE Node B RNC CN

GPRS Attach

RRC Connection Request (RACH)

RRC Connection Setup (FACH)

PDP context activation time
RRC Connection Setup Complete (DCH) and success
Service Request
Security mode command
Security mode complete
Activate PDP context request (DCH)

RANAP: RAB Assignment Request

RRC: Radio Bearer Setup

RRC: Radio Bearer Setup Complete

RANAP: RAB Assignment Response

Measurement Control
Activate PDP Context Accept (DCH)

Call Established
Introduction 2G Dive Test

2G Drive Test is testing and measuring performance of 2G

network.
Tool :
1. Sofware Nemo Outdoor
2. PC Laptop
3. GPS
4. Scanner
Introduction 2G Dive Test (Contnd)

Continuous Drive Test

Drive Test (Outdoor) using GPS
Walk Test (Indoor) using Pin point / way point
Analyze Data Collection
Analyze data that was collected before (from log files)
To know some problem in current area
Reporting
To answer analyze data collection (Objective Answer)
Optimization consideration
Recommendation
Introduction 2G Dive Test (Contnd)

Parameter Drive Test GSM

Rx Lev
Rx Qual
SQI
Cell Id, BSIC
TA (Timing Advance)
ARFCN (Absolute Radio Frequency Channel Number)
etc
Step by Step Nemo Setting

Open Device Manager

Step 1: Step 2:
Start > Settings > Control Panel > System Choose Hardware Tab in System
Properties > click Device Manager

Or My Computer > Manage > Device Manager

Step by Step Nemo Setting (Contd)

1. Open Device Manager (Contd)

Step 3:
Lock port to connect hardware (modem)
Scanner / GPS & Check COM Port
Step by Step Nemo Setting (Contd)

Connect UE & Check COM Port

Double click Modem to check Trace port number > Check under Modem
Tab

For UE Modem:
In device manger view:
Step by Step Nemo Setting (Contd)

Start Nemo Outdoor and Load Workspace

Make sure the nemo dongle is connected to the laptop
Launch Nemo Outdoor Software
Load the desire workspace
Workspace should contains adequate information for the user to monitor
Difference workspace should be created for difference setup configuration
Nemo workspace area store proper folder for easy to access, eg:
C:\Nemo Tools\Nemo Outdoor\Workspaces
Step by Step Nemo Setting (Contd)

Running Program
Start > Program Files > Nemo Tools > Nemo Outdoor
Workspace
Detail
Device Configuration
Load of measurement
Step by Step Nemo Setting (Contd)

User Interface Nemo Outdoor

Step by Step Nemo Setting (Contd)

Load Workspace
Browse to Nemo Workspace Folder > Select Workspace > Click Open
Step by Step Nemo Setting (Contd)

Create Workspace
Parameter
Step by Step Nemo Setting (Contd)
Add devices
Step 1 : Go to Measurement
workspace > Add New Device

Step 2: Click the Configuration part

> Trace port and Modem port
Step by Step Nemo Setting (Contd)

Nemo Interface
Map Interface
Open Map (.tab)

Nemo log files and other files are stored proper folder for easy to access, eg:
C:\Nemo Tools\Results (.nmf)
Nemo Reporting

Map Info
Exporting from Nemo Outdoor
Select Parameter
Reporting KPI with Map Info
Layer Control
Create Thematic Map
Define Network Performance
Open Table
Nemo Reporting (Contd)

Export to Map Info

Nemo Reporting (Contd)

Select Parameter
Nemo Reporting (Contd)

Report KPI with MapInfo

KPI (Key Performance Indicator) :
key to determine network
performance. Like Rx Lev, Rx Qual,
etc

MapInfo is software for loading

and mapping geoghrapic analysis
File > Open file (chose file extension
.tab)
Ex: bandung.tab
Used Layer control
Nemo Reporting (Contd)

Open Tab Files Layer Control

View
Edit
Nemo Reporting (Contd)

Create Symbol
Nemo Reporting (Contd)

Create Thematic Map

Nemo Reporting (Contd)

Create Thematic Map (Contd)

Nemo Reporting (Contd)

Reporting with Map Info & Table

Drive Testing Analysis

Drive test analysis with many sample cases :

1. Ping pong Handover
2. Missing Neighbor
3. Cross Feeder
4. Blocked Call
5. Dropped Call
6. Handover Failure
Drive Testing Analysis (Contd)

Ping pong Handover

Analysis:
Ping pong handover was happened due to no
dominant cells which cover area problem
difference RxLev between each cells less than
5 dB.

Solution:
Make 1 cell to be dominant which cover the
area problem with down tilt or re-azimuth
antenna and or setting handover parameter
setting.
Drive Testing Analysis (Contd)

Missing Neighbor
Analysis:
UE cannot handover to near site although the
source site has low RxLev already.

Solution:
Create adjacent cell between source cell
with near cell.
Drive Testing Analysis (Contd)
Cross Feeder

Analysis:
Based on plot was finding sector 1 cover area sector 2 and sector 2
cover area sector 1.

Solution:
To fix cross feeder or jumper configuration for each sector.
Drive Testing Analysis (Contd)
Cross Feeder (Contd)

Usually 1 sector have 2 feeders connection, Tx/Rx & RxDiv and should have inline between Antenna to Radio
Module for each sector. If 2 feeder installation was wrong to difference sector, we said Fully Cross Feeder
and if only 1 feeder to connect to difference sector, we can said Partial Cross Feeder.
Drive Testing Analysis (Contd)

Blocked Call
Analysis:
In this case, blocked call was happened due to
low Rx Lev (-104 dBm) and distance site
serving too far (> 7km).

Solution:
Many solution can do it to solve this problem:
- Make near site to dominant in this area
with antenna re-azimuth or re-tilting
- Increase RxLev Min, for good RxLev can
give call service.

Usually blocked call was happened due to

capacity issue as congestion or hardware
problem (TRX module). Upgrade or replace
TRX Module can solve this problem.
Drive Testing Analysis (Contd)

Dropped Call
Analysis:
Dropped call was happened due to low
RxLev, RxQual and too far Timing Advance
(TA=21). Signal level issue has root cause
dropped call in this area.

Solution:
Propose additional site to solve this problem.

If finding dropped call although signal level

(RxLev) still good, example >= -90dBm. You
need to check RxQual or C/I cause usually
this problem due to Interference (Co-
channel, Adjacent channel or External).
Drive Testing Analysis (Contd)

Dropped Call (Contd)

Solution:
Some solution to solve dropped call due to
interference:
- Down tilt antenna for overshooting site
- Re-azimuth antenna
- Change frequency BCCH
- Finding source external interference
Co-channel Interference (usually repeater or jammer)
- Sometime feeder & jumper installation
was not proper can generate
interference (check alarm VSWR).

Adjacent channel Interference

Drive Testing Analysis (Contd)

Handover Failure Analysis:

Handover failure was happened due to
congestion in target cell although handover
threshold already fulfill to start handover.

Handover failure can be happened with many

causes:
- Congestion in target cell
- TRX module is broken in target site
- Useless neighbor relation with too far site
neighbor
- Still not created yet neighbor relation in
surrounding cell

Solution:
Setting handover parameter to important
neighbor relation.
Drive Testing Analysis (Contd)

Drive Test Parameter Information (standard value)

RxLevel Value
-10 to -80 dBm (good)
-80 to -95 dBm (fair)
-95 to -110 dBm (bad)
RxQual Value
0 to 3 (good)
4 to 5 (fair)
6 to 7 (bad)
C/I Value
> 10 (good)
< 10 (bad)
SQI Value
> 18 (good)
< 18 (bad)