owt dt vs tt presentation

8/11/2019 OWT DT vs TT Presentation

1/34

Aug, 2014

Driver Testing andTECHTRACE comparison


2/34

AGENDA

DRIVE TESTING

TOOLS USED FOR DT

MODES OF DRIVE TESTING

USE OF DRIVE TESTING

KPIs OF DRIVE TETING


3/34

DRIVE TESTING

Drive testing is the most common way to analyse Cellular

Network performance by means of

coverage evaluation

system availability

network capacity

network retainabilitycall quality


4/34

AGENDA

DRIVE TESTING

TOOLS USED FOR DT





5/34

TOOLS USED FOR DT

Drive Testing requires the following tools

Power supply usually using inverter in the

GPS with external antenna

TEMS MS

TEMS Software

Laptop

Laptop

TEMSHandset


6/34


7/34


Drive testing is done with following modes:

Dedicated / Continuous / Long Call Mode

Idle Mode

Sequential / QOS / Short Call Mode

SCAN


8/34


9/34

Idle Mode

The MS is ON but no call occur.

MS receives information from the base station on the Broadcast

Control Channel (BCCH)

Checks if its able to register its current location to the network


10/34

Sequential / QOS / Short Call Mode

Creating the sequence of call along the drive test activity

Before starting the route create call sequence,

for example: Create call for 70 s and idle for 10 s.

Along the drive test, play this sequence until the route is finished

To see the real network

performance run, whenpeople call


11/34

Scan Mode

One of TEMS feature

scan all or selected frequencies on the selected spot or route

To find the clearest frequency

Application of frequency plan

to find the best frequency to

be use in the site

to identify interference adjacent

channel and co channel

Clean Frequency


12/34


13/34


In Planning :Drive Test Before Installation

Perform drive test before our network implemented.This data later will be compared with drive test afterimplementation, to justify.

Drive Test Before SWAPBefore swap (change operator network), drive testing needed to compare thecurrent network with the network after swap. To justify the new network isbetter than before.

Drive Test BenchmarkingDrive test the whole area for the whole active networks, before our networkimplemented. So when our network implemented, can be competed well.


14/34


In Implementation :Drive Test New Site/ Initial Drive TestInitiate the drive test after a site on-air.Make sure that site perform well after on-air.

Test Call New Site

Conducting tests call at a new On - Air site, to justify the performance of asite just after On - Air.

Drive Test Upgrade/Expand TRX After implement new TRX or expand TRX, a drive test performed to justify

that site working well with the new TRX .

Drive Test SFH/Hopping implementation After implement SFH/hopping in the network, a drive test performed to justify that this hopping solution working well with the whole network.


15/34


In Optimization :Drive Test Handover/ Add & Delete neighbors

Drive test conducted after theres changing in neighbours database .Make sure the add really added and the delete really deleted.

Drive Test before & after DowntiltDowntilt conducting, to get better coverage from each antenna. Drive test performed to make sure

the better coverage from each angle changed.

Drive Test Network AuditPerforming drive test activity to maintain the whole network. Could be an annual work.

Drive Test Benchmarkperforming drive test to get justification about our network. Can compete or not. With comparing

the whole network including 'us in drive test.

Drive Test troubleshootingDrive test for special troubleshooting case. Such as, a site that cannot handover from sitessurround it, a site that cannot transmit good signal and cannot achieve its coverage.


16/34

AGENDA

DRIVE TESTING

TOOLS USED FOR DT





17/34

KPIs OF DRIVE TESTING

Undecoded BCCHBSIC Undecode in OtherSiteNo HandoverDelay HandoverPing Pong HandoverNegative HandoverCell OvershootingHigh OverlappingNo Dominant Server

Poor CoverageUnreasonable ServingAreaInterferenceHandover FailureHandover LossUL DropDrop CallSudden Power DropMS Power RapidIncreaseSQI (Speech QualityIndex)


18/34

KPIs OF DRIVE TESTING

Non working sites/sectorsInactive features like freqhoppingDisabled GPRSMissing neighboursOne way neighboursC/A, C/I analysisCapacity problemsCoverage HolesFaulty Installations


19/34

AGENDA

INTRODUCTION TO TECHTRACE

HOW IT WORKS

ARCHITECTURE

CONCEPT

REPORTING

TT-PRO AND TT-RANKPIs MEASURED BY TECHTRACE


20/34


21/34

HOW IT WORKS

TECHtrace PRO works stand alone at OSS

Measurements taken from OSS to investigate troubleshooting use

cases:

coverage

capacity

service

VIP performance

Information and measurements about the user group

experience are collected without tracers and DT equipment


22/34

ARCHITECTURE

Detection of low Performance areasQuality of end user service; Areas with high blocking, call drop

and low experienced speed

Traffic analysis; Areas with high service usage, cell throughputand number of users

Coverage Performance ; Areas with poor signal level and/ or high

interference


23/34

CONCEPT


24/34

REPORTING

TECHtrace provide powerful reporting functionality:Table/Diagram

GIS Reporting

These include but are not limited to :

Coverage

Drops

Handover

Interference

Load

Neighbours

Parameter settings

Pre-drops

Quality

Service performance

Stability

Soft-drops

Swaps

User performance


25/34

TECHTRACE PRO

TECHtrace PRO is able to investigate deeply within all

NW entities; (BTS, RNC NE level Cell cluster)

TECHTRACE PRO detects at OSS level use case

Performance monitoring trigger

The solution only requires SQL/NetAct/Nastar/excel/CSV-

import files


26/34

TECHTRACE RAN

This tool and technology will be able to investigate

deeply the air interface and user view/experiences in

addition to TT PRO

TECHtrace RAN investigates at RNC/e-node B level air

interface/RRM RANPAR/, Cell cluster/Iub monitoring

Solution based on tracer or log file

Solution detects single users view, and substitutes mainly

Drive Test efforts

KPIs meas red b


27/34

KPIs measured byTECHTRACE

TECHTrace is able to measure following KPIsAir Interface performance

Propagation Delay ,

RSCP,

CQI,TCP(total, R99, HSDPA),

Littlei (DL),

RTWP

RSSI

Fragmented cells,

Permanent distant access,

unstable/permament bad cells,

Root causes for high adj. cell interference,

Root causes for adjacent cell interference


28/34

KPIs measured by


29/34


QoS Analysis

Blocking probability

Access failure rate

Service drop rate

Physical speed of a connection

Coverage probability

KPIs measured by


30/34


User Activity Analysis

Throughput

Number of users

Number of service requests


31/34

BENEFITS of TECHtrace

Multi technology / multi vendor networkBased on open architecture which has nearly no limits for the storage

of the performance data

Can be distributed in a form of packagesE.g. WCDMA-RAN, LTE-RAN, CORE

Delivers innovative GEO maps for traffic

performance indicators.

Includes an open script engine component

based on JavaScript

ADVANTAGES OVER DRIVE


32/34

ADVANTAGES OVER DRIVETESTING

With TT-PRO; NW investigations will be solved by 70% - 90%Done w/o air interface investigation

For further investigations TT-RAN will perform air interface investigationsLess labor intensive and time consumingMore comprehensive, based on large number of usersNot limited to time of test driveUplink and Downlink analysis possibleMakes NW optimization very efficient and reduces CAPEX/OPEXNo need of call flow monitoring, w/o tracer HW/SWIncludes E2E, field, RAN, NE plus auto analysis

Increasing data volumes and NW capacity, interferencewill grow and therefore DT will not indicate reliable cell loadmeasurements to give NPO results of NW improvementsTECHtrace PRO/ E2E-NE & user group investigationTECHtrace RAN/ reduced Drive-Tests/single user view

ADVANTAGES OVER DRIVE


33/34

ADVANTAGES OVER DRIVETESTING

Daily briefing (E2E report)Drill down by auto-investigations/(fault) reportingContinuously data investigations to

perform Q2E by Geo-map & usingSmartTECH tools


34/34

Q & A

owt dt vs tt presentation

Documents