No Site ID Status Name Validation Date Type

1 111629 Failed Birku 30/4/2020 2T2R

2 111649 Failed Birku 1/5/2020 2T2R

3 117118 Failed Birku 2/5/2020 2T2R

4 111059 Pass Birku 2/5/2020 2T2R

5 111061 Pass Birku 2/5/2020 2T2R

6 111097 Failed Birku 3/5/2020 2T2R

7 111409 Failed Birku 3/5/2020 2T2R

8 111163 Failed Birku 3/5/2020 2T2R

9 111162 pending Birku 3/5/2020 2T2R

10 111846 Failed Birku 4/5/2020 2T2R

11 111679 Failed Birku 4/5/2020 2T2R

12 111207 Failed Birku 5/5/2020 2T2R

13 111426 Failed Birku 5/5/2020 2T2R

14 111865 Failed Birku 6/5/2020 2T2R

15 112147 pending Birku 6/5/2020 2T2R

16 117109 Failed Birku 6/5/2020 2T2R

17 111742 Pass Birku 6/5/2020 2T2R

18 111701 pending Birku 7/5/2020 2T2R

19 111710 Failed Birku 7/5/2020 2T2R

20 111696 pending Birku 7/5/2020 2T2R

21 111680 Failed Birku 7/5/2020 2T2R

22 112179 pending Birku 7/5/2020 2T2R

23 111876 Failed Birku 9/5/2020 2T2R

24 117112 Failed Birku 9/5/2020 2T2R

25 112225 Failed Birku 9/5/2020 2T2R

26 111551 Failed Birku 9/5/2020 2T2R

27 112160 Failed Birku 10/5/2020 2T2R

28 112205 Birku 10/5/2020 2T2R

Pass
29 111547 Failed Birku 10/5/2020 2T2R
30 111410 Failed Birku 10/5/2020 2T2R
31 111067 Failed Birku 11/5/2020 2T2R

32 111562 Failed Birku 11/5/2020 2T2R

33 111867 Failed Birku 11/5/2020 2T2R

34 111635 Failed Birku 11/5/2020 2T2R

35 112143 Failed Birku 14/5/2020 2T2R

36 Failed Birku 16/16/2020 4T4R

111139
37 111154 Failed Birku 16/5/2020 4T4R

38 Failed Birku 16/16/2020 4T4R

111396
39 112072 Failed Birku 16/5/2020 4T4R

40 112099 Failed Birku 17/5/2020 4T4R

41 112138 Failed Birku 17/5/2020 4T4R

42 112139 Failed Birku 17/5/2020 4T4R

43 112248 Failed Birku 17/5/2020 4T4R

44 111052 Failed Birku 30/5/2020 4T4R

45 111161 Pass Birku 30/5/2020 2T2R
 Remark
1. INTRA Site Handover Success Rate is NOK.
2. Mobility Avg. FTP DL throughput and,
3. Stationary Max. & Avg. FTP DL throughput for sector 1,as well as Avg. FTP DL & Max. FTP UL for sector
3 are below targets.

1. Mobility Avg. FTP DL throughput and,

2. Stationary Max. & Avg. FTP DL throughput for sectors 1 & 2 are below targets

1.PS Session Termination Success Rate,

2. Successful FTP DL transfer and,
3. Max. FTP DL throughput for sectors 2 & 3 are below targets.
4. Sectors are crossed.
correct "Avg. Latency for Ping 1460bytes " for sector 1 on the report
correct "Fast Return duration after CS call is finished" status on the report
1. no lat & long info to check cross from idle mobility logfile.
2. correct " Max. & Avg. FTP UL throughput" results unit on the report.

1. Fast Return duration after CS call is finished has no value for sector 1.
2. Max FTP DL througput for sectors 2 &3, and Avg. FTP DL throghput for sectos 2 are below targets.

1. Fast Return duration after CS call is finished has no value for sector 1.
2. only one test for Avg. Latency for both Ping 32 & 1460 bytes.
3. only one test for successful FTP UL & DL transfer, and PS session termination.
4. both Max. & Avg. FTP DL throughput below target for all sectors.
5. Sectors are crossed

corrupted logfile
1. FTP DL plan is only twice for 1GB file
2. PS call success rate has no value for sector 3.
FTP DL plan is only twice for 1GB file

1. voice call duration is ony 5 seconds per sectors.

2. Avg. latency for ping 32 & 1460 bytes is only 5 tests per sectors.
3. FTP DL & UL plan is only once for 2GB & 500MB files respectively.
4. Max. FTP DL throughput for all sectors, and Avg. FTP UL throughput for sectors 1 & 2 are below
targets.

No FTP UL log file for sector 2

1. sector 3's voice call duration for the second test is 3 seconds.
2. FTP DL plan is only twice for 1GB file per sector.
corrupted logfile

1. correct "Fast Return duration after CS call is finished" and "PS Service access time ( ERAB Setup
time )" resuts on the report as the validation and report results are different.
2. Location of the cell and its log track are different; lat & log variation.

correct "Fast Return duration after CS call is finished" and "PS Service access time ( ERAB Setup time )"
resuts on the report as the validation and report results are different.
corrupted logfile
Fast Return duration… has no value for sectors 1 & 3, Max. & Avg. FTP DL throughput are below targets
for sectors 1 & 2, Sectors are crossed
corrupted logfile

Fast Return duration… has no value for all sectors, location of cell and its log track are slightly different
corrupted logfile
No DL log for sector1, Max FTP DL for sector 2 is below target,FTP DL plan is only twice for 1GB file for
sector 3.
FTP DL for sector 2 is cancelled, (mobility) Avg. FTP below target, lat & long variation for idle mobility
analysis
(mobiliy) Avg. FTP DL throughput below target
FTP DL test plan for sector 1 is only once which is cancelled, & for setor 3 are only twice of which the
second attempt is cancelled, Max. & Avg. FTP DL throughput are below targets.
lat & long variation for idle mobility analysis

correct "PS service access time", "Avg. attach and detach time" and other units' results on the report.
No FTP DL log file for sector 2, correct "PS service access time" result on the report
lat & long variation for idle mobility analysis
FTP DL fourth attempt cancelled for sector 2, Max. & Avg. FTP DL throughput below target.
incomplete log files; only FTP DL & UL, ping 32 & 1460, Detach&attach for sctor 2, and MOC for scrtors 1
&2
lat & long variation for idle mobility analysis

PS attach & detach success rate & time have no values for sector 1, Max. FTP DL throughput below
target for sector 2, correct "Fast Return duration after CS call is finished" and "PS Service access time
( ERAB Setup time )" resuts on the report
No FTP DL and ping1460Bytes log files within the ValidationFeedBack directory
No DL logs for sectors 1 & 3, Max. & Avg. FTP DL for sector 2 is below target, lat & long variation for idle
mobility analysis
256 QAM activated, all sectors' Max. FTP DL throughput below targets

CA & 256 QAM activated, FTP DL test plan is only twice for sctor 1 of which th second attempt is
cancelled, Max. FTP DL throughput for sectors 1& 3 are below targets, second attempt of FTP UL for
sector 3 failed.
CA & 256 QAM activated; affects FTP throughputs
CA & 256 QAM activated,Max. FTP DL for sector 1 is below target, no FTP DL log files for sectors 2 & 3,
sectors are crossed
CA & 256 QAM activated, Max. FTP DL for all sectors & Avg. FTP DL for sectors 2 & 3 are below targets,
FTP DL test plan for sector 3 is 1GB file only twice (the second attempt is cancelled)
CA & 256 QAM activated, no FTP DL log file for sector 1, sectors crossed
FTP DL plan is only once & twice for 1GB file with failed attempts, lat & long variation for idle mobility
analysis
corrupted logfile
No Site ID Status Name Validation Date Type

51 111649 Pass Birku 27/6/2020 2T2R

 Remark

cleared with the updated retest log file

 Scenario 3 sites justification and action taken when retesting

High PRB Utilization during test, Poor SINR, and Testing

method not good
No Site ID Status Name Validation Date Type

35 111649 Pass Birku 27/6/2020 2T2R

 Remark

cleared with the updated retest log file

 Scenario 3 sites justification and action taken when
retesting

High PRB Utilization during test, Poor SINR, and

Testing method not good
SSV Validation Summary_Birku
Tool Failed Passed Retest Signed Total
Nemo 0 0 0 0 0
PHU 10 35 31 35 45

NB: 112069 not validated so far!