You are on page 1of 15

TRAINING DRIVE TEST ENGINEER

Trainer : Khanra LENG


Date: 09-April-2017
Location: Future Telecom Company
Content
1.1 - Route on Main lobe (in front of sector)
1.2 Call set up failure or dropped nearby site
1.3 Check site cross feeder
1.4 Swap log file
1.5 In case stop script
1.6 Abnormal Throughput (Bad Throughput PSDL)
1.7 Abnormal Throughput (Missing Throughput PSUL)
1.8 KPI Target of UMTS (U850 & U2100)
1.9 Sample KPI PAC EVO
1.10 Sample KPI FAC E1800
1.11 Sample KPI FAC L2100
1.1 - Route on Main lobe (in front of sector)

For route on main lobe should drive test, if can


not go can take picture with location also.
Specially the route that DTA was sent should
follow all route to drive test because easy
DTA to clear about Azimuth.
1.2 Call set up failure or dropped nearby site

On this case the DTE should delete the log file


and Re-drive again. If it also failure or
dropped in the poor coverage or far from
serving cell is ok.
1.3 Check site cross feeder

1- Update all information from EP and CME to


file bts when all guys test the site target,
specially PSC or PCI from CME in Google drive
to update file #BTS in Nemo.
2- If all guys see some site abnormal or site
have problem should confirm to DTA to note
about problem.
1.4 Swap log file

1- On this case the DTE should swap log file


in case poor coverage (Low signal)
because easy DTA optimize or the log file
have problem can use those file to re-drive
mean that it not far or effect long route.
Note: If the DTE guys think it also far from
site should be swap the log file depend on
Antenna High.
1.5 In case stop script

1- Before stop script all DTE should wait until


call completed avoid call dropped or call
failure event happen in the log file.
1.6 Abnormal Throughput (Bad Throughput PSDL) Result before

1- Normally the Throughput PSDL pass KPI, 50%


of samples 9 Mbps. But on this area the RSRP
& SINR normal but the throughput it so poor
(>= 1Mbps to < 5Mbps) why is we need to
double check, issue from the network, DTE or
Tools.

PSDL-App_Throughput_DL (kbps)

>= 0.00 to < 1.00 (0) 0.0%
>= 1.00 to < 1000.00 (183) 1.7%

>= 1000.00 to < 5000.00 (4138) 37.6%
>= 5000.00 to < 10000.00 (3607) 32.8%
>= 10000.00 to < 15000.00 (2033) 18.5%

>= 15000.00 to < 20000.00 (772) 7.0%
>= 20000.00 to < 25000.00 (173) 1.6%

>= 25000.00 to < 1000000.00 (85) 0.8%
Result after
1.7 Abnormal Throughput (Missing Throughput PSUL) Result before

1- Normally the Throughput PSUL pass KPI that


mean 50% of samples 7 Mbps. On this case
the issue throughput not detected nearby site
like the missing PSUL so we need to monitoring
all the UE because sometime the UE have
Hang or not working so if DTE still moving car
will have the missing throughput or event fail
& drop PS.

PSUL-App_Throughput_UL (kbps)
>= 0.00 to < 1.00 (0) 0.0%

>= 1.00 to < 1000.00 (148) 1.2%

>= 1000.00 to < 2000.00 (214) 1.7%
>= 2000.00 to < 5000.00 (1159) 9.5%

>= 5000.00 to < 10000.00 (9781) 79.9%

>= 10000.00 to < 15000.00 (944) 7.7%
>= 15000.00 to < 1000000.00 (0) 0.0%
Result after
KPI

1.8 KPI Target of UMTS (U850 & U2100)

For Non-EVO PAC have 2 parts for calculate KPI,


1- calculate with the result all routes, 2- calculate in the prediction area
1.9 Sample KPI PAC EVO
1.9 Sample KPI PAC EVO
1.10 Sample KPI FAC E18
1.11 Sample KPI FAC L2100
Thanks you!

You might also like