NO Site ID status Validation team Date

63 112220 Fail Yirgalem 5/28/2020

64 111758 Fail Yirgalem 6/1/2020

65 111647 Fail Yirgalem 6/1/2020

66 112201 Fail Yirgalem 5/28/2020

67 112131 Fail Yirgalem 6/1/2020

68 111719 Fail Yirgalem 6/17/2020

69 111681 Fail Yirgalem 5/28/2020

70 111759 Fail Yirgalem 6/1/2020

71 111416 Yirgalem

72 113002 Fail Yirgalem 5/30/2020

73 111050 Fail Yirgalem 6/2/2020

74 111128 Fail Yirgalem 6/2/2020

75 111194 Fail Yirgalem 6/2/2020

76 111268 Fail Yirgalem 6/2/2020

77 111413 Fail Yirgalem 6/2/2020

78 111436 Fail Yirgalem 6/2/2020

79 111553 Fail Yirgalem 6/11/2020

80 111559 Fail Yirgalem 6/11/2020

81 111583 Fail Yirgalem 6/11/2020

82 111617 Fail Yirgalem 6/11/2020

83 111631 Fail Yirgalem 6/12/2020

84 111643 Fail Yirgalem 6/12/2020

85 111682 Fail Yirgalem 6/12/2020

86 111683 Fail Yirgalem 6/12/2020

87 111698 Fail Yirgalem 6/13/2020

88 111699 Fail Yirgalem 6/13/2020

89 111722 Fail Yirgalem 6/13/2020

90 111750 Fail Yirgalem 6/13/2020

91 111806 Fail Yirgalem 6/13/2020

92 111819 Fail Yirgalem 6/13/2020

93 111821 Fail Yirgalem 6/13/2020

94 111832 Fail Yirgalem 6/14/2020

95 111833 Fail Yirgalem 6/14/2020

96 111837 Fail Yirgalem 6/14/2020

97 111838 Fail Yirgalem 6/14/2020

98 111841 Fail Yirgalem 6/2/2020

99 111843 Fail Yirgalem 6/14/2020

100 111848 Yirgalem

101 111849 Fail Yirgalem 6/23/2020

102 111861 Fail Yirgalem 6/15/2020

103 111870 Fail Yirgalem 6/15/2020

104 111874 Fail Yirgalem 6/15/2020

105 111881 Fail Yirgalem 6/15/2020

106 111999 Fail Yirgalem 6/17/2020

108 112132 Fail Yirgalem 6/15/2020

109 112144 Fail Yirgalem 6/15/2020

110 112157 Fail Yirgalem 6/15/2020

111 112192 Yirgalem

112 112227 Fail Yirgalem 6/15/2020

113 112229 Fail Yirgalem 6/15/2020

114 112236 Fail Yirgalem 6/15/2020

115 112243 Fail Yirgalem 6/15/2020

116 112244 Fail Yirgalem 6/15/2020

117 112251 Yirgalem

118 112252 Fail Yirgalem 6/16/2020

119 112261 Fail Yirgalem 6/16/2020

120 113000 Fail Yirgalem 6/23/2020

121 117101 Fail Yirgalem 6/16/2020

122 117111 Fail Yirgalem 6/16/2020

123 117113 Fail Yirgalem 6/16/2020

124 117120 Yirgalem

125 117134 Fail Yirgalem 6/16/2020

126 117141 Fail Yirgalem 6/16/2020

127 117144 Yirgalem

Site Solution Remark
Scenario

2T2R
C2_only 4 CSFB successful

2T2R All DL&UL throughput below thr. Ping32_C2 RTT above thr.

2T2R C2_moc log is locked with wrong PSC-=C1, Throughput below

thr. For all DL,

2T2R Allmost all KPI's fail

C1_UL and ALL DL throughput below thr. C1&2 MOC test wrong
2T2R methodlogy.

2T2R C3_MOC done 3 times. C1_UL throughput below thr,ping test

done 20 times,DL kPI's fail,

2T2R C2_DL throughput and C3_Dl transfer below thr.

2T2R C1_DL file transfer 3 times, ERAB set up time not cheked

C3_Dl wrong test methdology, KPI's formula for PS Session

2T2R termination success rate, Detach time,ERAB set up time cannt
be identified
DL_App throughput&& data transfer below thr, Ul_mobility
2T2R file size,MOC_C2 for PCI_408 not done.Ping wrong
testmethod, PCI0 has more sample
DL_App throughput&& data transfer below thr, DL&&Ul_mobility file
2T2R size,.Ping wrong testmethod, RRC success rate for C1&2 below thr.
PCI0 has more sample
2T2R Logfiles missed

DL, Mobility and UL testlogfiles missed, PS attach time

2T2R
above thr. 1

2T2R C3_dl throughput below thr,high Serving PCI 0, Wrong EP.

3
feeder cross,DL test did not follow testmethod,c3_Ul not
2T2R
locked,C2_attach/detach locked with wrong PCI,high serving PCI0
DL test did not follow test methodology, ping done 20 times,High serving
2T2R
PCI0 for all tests,
C1&3_UL App throughput below thr.ping all_20times, C2_high attach
2T2R
time,High serving PCI0 for all tests,
Both DL&UL , ping tests did not follow testmethodlogy, CS fallback time
2T2R is above thr. C2_3 detach success rate below thr. So it needs retest for all
KPI 1
Ping test 20 times,C1_RRC success rate and C2_ detach success rate
2T2R belwo thr. All mobility test fail. AL Dl test did not follow test
methodlogy,
 C2&3 RRC and detach success rate below thr. Sites cover less in IDLE,
2T2R
all mobility KPI fail, PCI 0 has more serving for all test

2T2R PCI0 has high serving, C3_RRC success rate below thr. All Dl KPI's fail,
feeder cross,C1_Ping 32 done 21 times, other ping test 20 times,all call
2T2R test done 3 times, C1_RRC and attach success rate below thr, PCI 0 has
more serving for all test

2T2R C1 all KPI's missed, all KPI's results below thr.

C2_CSFB success rate below thr, all ping and DL test did not follow
2T2R
testmethodology. PCI0 serves more percentage.
feeder cross, C1&2_ping 32 done 21 time and other 20 times, PCI0 is
2T2R
detected
C3_UL PS transfer one time, ping 20 times,Dl wrong test methodology,
2T2R
feedercross.

2T2R MOC_didn't follow test methodology,ping test 20 times, wrong EPT

MOC_C2 locked with other PCI,attach/detach did not follow

2T2R
testmethodlogy, UL/DL logfiles missed PCI0 serving high.
C1_attach/detach fail, ALL_ping RTT time above thr. DL dinot follow the
2T2R
test methodology.DL mobility below thr. PCI0 serves.
All Ping test 20 times,PCI0 serves more, DL test did not follow test
2T2R
methodlogy.
C2&3 RRC and detach success rate below thr. All DL test fail, PCI0 has
2T2R
high serving
All UL transfer one time, C2_ping done 21 times, all mobility KPI's
2T2R
missed, DL test did not follow test methodology.PCI0 has high serving
C2(PCI469)_ping and attach/detach log file missed, all ping 20times,All
2T2R
DL test missed,PCI0 has high serving

2T2R half of test missed and others fail.PCI0 has high serving

C1_dl 3 times ps transfer, C2_DL throughput below thr.DL and UL

2T2R
_mobility file size 2GB, high serving PCI0, MOC_c2
feeder cross,PCI145_ping not done,MOC_test did not follow test
2T2R
methodology,PCI0 has high serving

2T2R Ping C1_1460 fail,DL KPIS fail

2T2R all kpi's fail

C1_RRC success rate belwo thr. Ping test is done 20 times, DL &&
2T2R
C1_moc did not follow test methodlogy,
MOC_C2&3 done twice,C3_attach/detach fail, DL didn’t follow test
2T2R
methodlogy, PCI0 serves high for all test. All ping test done 20 times
 All test for PCI 482 (redunndancy of 481 done)& UL mobility didn't
2T2R done. PCI0 and DL KPIS didn't meet the test procedue.All ping test done
20 times
C2&3 CSFB time is above thr. Ping_RTT/attach/UL fail,totally
2T2R
all KPI's fail
MOC_C1&3 done three times,C2_ul below thr. DL test methodology and
2T2R
PCI0 is obsered .
CSFB calls and PING test did not follow test procedure, C2&3_UL
2T2R
below thr. Dl log ifles missed, PCI0 serves for all test
MOC_C2&3(PCI 3&4 )did not follow test procedure, C1&2_ping 20
2T2R times but C_3 18 times. DL test did not follow test procedure. PCI 0
serves high.

No mobility log files,ping test done 20 times, C2_UL below thr. PCI0
2T2R
serves high sample, DL test is done with wrong procedure
PING test fail,App throughput C1&2_UL belwo thr. DL test did not
2T2R follow test procedure. DL mobility throughput below thr.PCI0 serves also
high
Ps attach time is below thr for all sectors, Ping test has been done 20
2T2R times, Moc didn’t follow test procedure.NO log file for all mobility and
DL, UL .
2T2R Incomplete logfile

2T2R ping test done 20 times, No log file for C1_ul and All DL.

C1&3_MOC test is done 4 times, DL,UL & C1&2_ping test methodology

2T2R
is wrong. No logfile for UL and DL mobility
Ping test is done 20 times, C2_moc twice, All DL KPI's faill. PCI0 serves
2T2R
high
CSFB calls and PING test did not follow test procedure, C3_UL below
2T2R
thr. DL KPI's fail. PCI0 serves for all test

2T2R No mobilityand DL log files,ping test done 20 times, PCI0 serves high
Ping test wrong test methodlogy, C2_UL app throughput below thr., No
2T2R logfile for C1 attach/detach and MOC and Mobility UL, All DL KPI's fail
and
2T2R Ping_1460 fail,no logfile for DL tests.

2T2R ping test is done 20 times,Dl test didn’t follow test method.

2T2R feeder cross, DL KPI's fail, PCI 0 serves more.

Test Tool

NEMO

NEMO

NEMO

NEMO

NEMO

NEMO

Nemo

Nemo

Nemo

Nemo

NEMO

NEMO

Nemo

Nemo

Nemo

NEMO

NEMO

Nemo

Nemo

NEMO
NEMO

Nemo

Nemo

Nemo

Nemo

NEMO

NEMO

Nemo

Nemo

Nemo

Nemo

NEMO

NEMO

NEMO

NEMO

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo
Nemo

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo

Nemo
No Site ID Status Validation Signature Date Site Solution

1 5/21/2020 2T2R
111305 signed Yirgalem
2 5/21/2020 2T2R
111676 signed Yirgalem
3 5/21/2020 2T2R
111301 signed Yirgalem
4 5/25/2020 2T2R
112212 signed Yirgalem
5 5/23/2020 2T2R
112194 signed Yirgalem
6 5/25/2020 2T2R
111569 signed Yirgalem
7 5/21/2020 2T2R
111856 signed Yirgalem
8 5/23/2020 2T2R
111684 signed Yirgalem
9 5/23/2020 2T2R
111665 signed Yirgalem
10 5/23/2020 2T2R
111678 signed Yirgalem
11 5/21/2020 2T2R
112257 signed Yirgalem
12 5/23/2020 2T2R
111697 signed Yirgalem
13 5/21/2020 2T2R
112155 signed Yirgalem
14 5/21/2020 2T2R
111765 signed Yirgalem
15 5/21/2020 2T2R
112169 signed Yirgalem
16 5/25/2020 2T2R
111736 signed Yirgalem
17 5/25/2020 2T2R
111550 signed Yirgalem
18 5/25/2020 2T2R
112048 signed Yirgalem
19 5/25/2020 2T2R
111744 signed Yirgalem
20 5/25/2020 2T2R
117102 signed yirgalem
21 5/25/2020 2T2R
112178 signed yirgalem
22 5/25/2020 2T2R
111613 signed yirgalem
23 5/25/2020 2T2R
111662 signed yirgalem
24 5/25/2020 2T2R
112170 signed yirgalem
25 5/25/2020 2T2R
111648 signed yirgalem
26 6/4/2020 2T2R
112165 signed Yirgalem
27 6/4/2020 2T2R
112228 signed Yirgalem
28 6/4/2020 2T2R
111586 signed Yirgalem
29 6/4/2020 2T2R
111745 signed Yirgalem
30 6/4/2020 2T2R
111604 signed Yirgalem
31 6/4/2020 2T2R
111708 signed Yirgalem
32 6/4/2020 2T2R
117106 signed Yirgalem
33 6/4/2020 2T2R
111242 signed Yirgalem
34 6/4/2020 2T2R
111732 signed Yirgalem
35 6/4/2020 2T2R
114001 signed Yirgalem
36 6/12/2020 2T2R
112215 signed Yirgalem
37 6/12/2020 2T2R
112200 signed Yirgalem
38 6/12/2020 2T2R
111667 signed Yirgalem
39 6/12/2020 2T2R
111652 signed Yirgalem
40 6/12/2020 2T2R
111746 signed Yirgalem
41 6/17/2020 2T2R
111579 signed Yirgalem
42 6/17/2020 2T2R
112171 signed Yirgalem
43 6/26/2020 2T2R
111258 signed Yirgalem
44 6/26/2020 2T2R
112161 signed Yirgalem
45 6/26/2020 2T2R
112181 signed Yirgalem
46 6/26/2020 2T2R
112213 signed Yirgalem
47 6/26/2020 2T2R
112164 signed Yirgalem
48 6/26/2020 2T2R
111627 signed Yirgalem
49 6/26/2020 2T2R
117105 signed Yirgalem
50 111763 signed Yirgalem 6/26/2020 2T2R
51 111669 signed Yirgalem 6/26/2020 2T2R
No Site ID status Validation team Date Site Solution
4 112166 pass Yirgalem 6/26/2020 2T2R
21 111685 pass Yirgalem 6/26/2020 2T2R
23 111669 pass Yirgalem 6/26/2020 2T2R
30 112168 pass Yirgalem 6/26/2020 2T2R
Remark
SSV Validation Summary_Yirgalem
Tool Failed Passed Retest Signed Total
Nemo 59 0 0 0 59
PHU 8 54 48 51 62