7/28/2019 SSV DT

1/18

SSV DT REPORT PROCESS

6th Sept 2012

Network statistics

SSV DT Handling and Plots

SSV KPI Handling

7/28/2019 SSV DT

2/18

To understand and maintain uniformity of SSV Reports

Facilitate smooth approval of Reports by Customer

Easy handling of SSV reports

Objectives

7/28/2019 SSV DT

3/18

3

SSV DT Tools and software

Tools and Software

SoftwareProbe version(V200R003C01SPC300)

Assistant version 3.3 soft dongle type

Auxiliary softs(Franson Gpsgate etc.)

Tools

Laptop(P/A software installed)

E270 Data card

Phones + USB cables(U120E, U6100 or U8800)

GPS

Inverter

Compass

Audit tools(tape measure, inclinometer, camera etc)

7/28/2019 SSV DT

4/18

Initial Optimization both RF and KPI optimization should be performed on new sites

before, during and after SSV DT. Improve coverage and quality if bad

If changes are done, do show previous data and the data after impact of change. If forexample there was a swap on site, DT plot should be generated for before and after theswap correction as evidence.

Before SSV, DT engineer should predict possible routes on Google earth to test all three

sectors as best as possible. If all three sectors are not driven due to certain issues itshould be stated and backed by evidence such as pictures in report.

Audit & site changes must be done and well noted before DT. All changes(azimuth , swap,tilt, coordinates) done on site which are different from planned data should be logged inthe SSV Audit Tracker

Lock Band before SSV DT is done

Drive should continue until handover or coverage becomes poor , DT should be in limit of1.5Km

Throughput Data information should be displayed using strictly Probe.

Things to note

7/28/2019 SSV DT

5/18

Live Site

Perform

SSV DT

Victor

Review

BSC owner

Review

VDF

Review

NPO Planning NPO Server

PAC

Parameter/KPI

monitoring

SSV Audit Tracker Log files

SSV Report

SSV Report approved

SSV Report approved

SSV General Flow

SSV Report rejected

SSV Report rejected

SSV Report approved

7/28/2019 SSV DT

6/18

SSV Process

Market VF Project

Site name,Site ID/Cluster ID EKUASI, WEB7311 /WE_TAK_BSC01

Latitude/Longitude 4.930167/ -1.725833

General location

Western Region

Date 12-22-2011

BTS Type DBS3900

Site Config S2/2/2

Cell ID Antenna type Mech tilt Elect Tilt Azimuth RF Height

17311 80010122 0 4 80 23.4

27311 80010122 0 4 220 23.4

37311 80010122 0 4 330 23.4

Cell ID BCCH TCH MAIO HSN

17311 48 61;62;63;64;65;66;67;68;69;70;71;72;73;74;75;76;77;78;79;80;81;82;83 0 0

27311 53 61;62;63;64;65;66;67;68;69;70;71;72;73;74;75;76;77;78;79;80;81;82;83 2 0

37311 57 61;62;63;64;65;66;67;68;69;70;71;72;73;74;75;76;77;78;79;80;81;82;83 4 0

These tables should be filled carefully to conform with planned parameters(Asset/ITI DB). Audit should

be done on site and if there is any variation on site especially with coordinates, azimuth, Mech tilt,

antenna type and height it should be well noted and corrected. Issues concerning coordinates should be

feedback to planning.

SITE INFORMATION

ANTENNA INFORMATION

CELL PARAMETER

7/28/2019 SSV DT

7/18

DT Plots

1. CELL ID DISTRIBUTION

The cell ID distribution plot should be generated as above taking note of scale, legend and

grid lines, before DT is performed DT engineer should first check for sector swap and take

audit on site and compare with Asset/ITI DB. DT should be done to test all three sectors as

best as possible. If all three sectors are not all tested due to unavailability of access route it

should be commented and backed with snapshots from Google earth or pictures taken fromsite. Note that DT should begin from the site.

Display cell ID

along routes

served by

respective

sectors

Synchronize sector

colour with plots in

assistant and note to

resolve sector swap.

Display Cell ID for

sectors

Display site name

7/28/2019 SSV DT

8/18

2. C/I ON BCCH CARRIER

The C/I on BCCH Carrier plot should be generated as above taking note of scale and grid lines.

end should be in this

at.

7/28/2019 SSV DT

9/18

The Rxlev_Sub plot should be generated as above taking note of scale, legend and grid lines.

Before DT is performed DT engineer should confirm azimuth with Asset/ITI DB. DT should be

done to test all three sectors as best as possible. Coverage is of the highest priority in SSV DT

and so should be noted well, if coverage is poor DT engineer should try to improve or comment

to explain issue in report and make recommendations as like the example shown in the nextslide

3. RXLEV_SUB

Legend should be in this

format. It is very important

7/28/2019 SSV DT

10/18

The rxlev(coverage) was poor within that area and report could have been rejected but with

comments indicating an undulating terrain backed by snapshots from Google Earth which was

added to the report as remarks rectified the problem and report was finally approved. And so

when DT engineer encounters such problems it should be well noted

7/28/2019 SSV DT

11/18

RX LEVEL_SUB TABLE AND GRAPH

Legend Count Percentage(%)

-64dBm ~ -10dBm 497 23.20

-68dBm ~ -64dBm 140 6.54

-73dBm ~ -68dBm 375 17.51

-78dBm ~ -73dBm 220 10.27

-85dBm ~ -78dBm 470 21.94

-100dBm ~ -85dBm 440 20.54

Total2142 100.00

Rx_Level(Sub)

0

500

1000

1500

2000

-64dBm ~ -

10dBm

-68dBm ~ -

64dBm

-73dBm ~ -

68dBm

-78dBm ~ -

73dBm

-85dBm ~ -

78dBm

-100dBm ~

-85dBm

Counts

0.00

20.00

40.00

60.00

80.00

100.00

Percentage(%)

Discrete Cummulative

The Rxlev_Sub Table and Graph samples should be generated exactly as shown above with the

correct Legend as displayed on the rxlev_sub plot.

7/28/2019 SSV DT

12/18

4. RXQUAL_SUB

The RxQual_Sub plot should be generated as above taking note of scale, legend and grid lines.

Legend should be

in thisformat. It is very

important

7/28/2019 SSV DT

13/18

Legend Count Percentage(%)

0 ~ 4 2098 88.9

4 ~ 6 181 7.67

6 ~ 7 81 3.43

Total 2360 100

RXQUAL_SUB TABLE AND GRAPH

The RxQual_Sub Table and Graph samples should be generated exactly as shown above with

the correct Legend as displayed on the rxqual_sub plot. Use graph template sheet to aid to

generate samples as same as in the rxlev_sub samples.

7/28/2019 SSV DT

14/18

The HANDOVER EVENT plot sholud be generated as shown above taking note of legend, scale

and grid lines. Intercell Handover sholud be shown as best as possible. If there are pingpong

handovers due to overshooting or between intercells DT engineer sholud take note to correct

the problem or add remarks to explain the issue.

4. HANDOVER EVENT PLOT

Legend should be

in this

format. It is very

important

Legend showing

count of successful

Handovers should

be in this

format as well. It is

very important

The handover

pictogram should

be displayed clearly

with a visible font

size

7/28/2019 SSV DT

15/18

PS Data should be done using strictly Probe and data graphs should be displayed as shown in

sample below:

EDGE Throughput (DL) Data

7/28/2019 SSV DT

16/18

Data Download Thresholds

Type of Download

Data Transfer EDGE GPRS

Total Download Size >= 2MB >=1MB

Maximum Transfer Rate

7/28/2019 SSV DT

17/18

SSV KPI

KPI statistics should be queried for 5 days

If KPI statistics for a site dont meet threshold it should

be escalated to BSC owner to rectify problem.

At the last section of the SSV report, the summaryheading DT engineer should change site ID to that of therespective site.

Sample ssv report

KPI Target

CS

Call Setup Success

Rate98%

Handover Success

Rate95%

Call Drop Rate 2%

SDCCH Drop Rate 2%

TCH Congestion Rate 2%

SDCCH Congestion

Rate2%

TCH Traffic N/A

PS

DL TBF Estab

Success98%

DL TBF Drop 6%

UL TBF Estab

Success98%

HW_UL TBF Drop 6%

7/28/2019 SSV DT

18/18

THANK YOU