Professional Documents
Culture Documents
Revision History
EDITION
DATE OF ISSUE
1.3
AUTHOR
REMARKS
JH Kim
JW Park
1.4
JH Kim
CONTENTS
Revision History
CONTENTS
Overview 4
CHAPTER 1. Cell Edge Test
12
1.2
1.3
1.1.1
DL Throughput ........................................................................................................................... 12
1.1.2
UL Throughput ........................................................................................................................... 14
1.2.2
Stationary Test...........................................................................................................................20
1.3.1
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
34
RSRP ......................................................................................................................................... 34
2.1.2
SINR ........................................................................................................................................... 36
2.2.2
2.2.5
2.2.7
2.2.8
2.2.9
2.2.10
2.2.12
2.2.13
2.2.14
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.8
2.3.9
2.3.10
2.3.11
Packet Loss................................................................................................................................ 66
2.4.4
71
CHAPTER 4. Appendix
73
Overview
These tests cover a broad range of network performance characteristics
including latency, handoff, throughput, capacity, VoLTE with MOS and
reliability.
This YTLC-SAMSUNG BTS cluster test procedure provides a detail
description of each test and a brief summary of the test results.
The BTS cluster tests were conducted at drive route and fixed Point that
YTLC and SAMSUNG agreed upon mutually. All test results were extracted
from the field data comparing with the coverage on the basis of cell plan
simulation.
Test Name
Stationary Test
Test Items
Bound
Acceptance Criteria
1.1
DL Throughput Test
>=
1.1.2
UL Throughput Test
1.2
1.2.1
>=
>=
=<
Success Rate
1.2.2
1.3
Stationary Test
1.3.1
DL MCS
>=
>= 0dB
1.3.2
DL MCS
>=
>= 5dB
1.3.3
DL MCS
DL MCS
>=
DL MCS
>=
UL MCS
>=
>= 30dB
1.3.6
>= 25dB
1.3.5
>= 15dB
1.3.4
>=
1.3.7
UL MCS
>=
1.3.8
UL MCS
>=
1.3.9
UL MCS
>=
Mobility Test
Mobility Test
2.1
2.1.1
RSRP
>=
2.1.2
SINR
>=
2.2
2.2.1
>=
99
=<
800
=<
Success Rate
2.2.2
2.2.5
2.2.7
2.2.8
=<
2.2.9
HOSR (Intra-
>=
99
=<
40
TBD
Frequency+Inter Frequency)
2.2.11
2.2.12
Throughput
2.2.13
Throughput
2.2.14
Report only.
1 sample per cluster
2.3
2.3.1
>=
99
Rate (GBR)
2.3.2
=<
2.3.3
=<
2.3.4
TBD
2.3.5
TBD
2.3.6
>=
99
+Intra-Frequency)
2.3.8
TBD
2.3.9
(GBR)
2.3.10
Report Only.
2.3.11
Packet Loss
Report Only
A mutual understanding and
agreements as report only test item.
2.4
2.4.2
2.4.4
=<
45
Packet Loss
=<
=<
75
Packet Loss
=<
MOS Mobility
Acceptance Criteria
Test
3.1
3.1.1
>=
Upload
>= 256Kbps
>= 256Kbps
>= 256Kbps
>= 256Kbps
Morphology
Dense Urban
Urban
Suburban
Rural
Dense Urban
Urban
Suburban
Rural
Test
UE Band
Turn
Setting
DL Data/UL
Data
1st
Fixed(2.3)
VoLTE/Ping
2nd
Auto
DL Data/UL
Data
1st
Fixed(2.3/2.6)
VoLTE/Ping
2nd
Auto
DL Data/UL
Data
1st
Fixed(2.6)
VoLTE/Ping
2nd
Auto
DL Data/UL
Data
1st
Fixed(2.3/2.6)
VoLTE/Ping
2nd
Auto
DL Data/UL
Data
1st
Fixed(2.3/2.6)
VoLTE/Ping
2nd
Auto
DL Data/UL
Data
1st
Fixed(2.3/2.6)
VoLTE/Ping
2nd
Auto
DL Data/UL
Data
1st
Fixed(2.3/2.6)
VoLTE/Ping
2nd
Auto
Case
Cluster Configuration
Test Item
Interleave (2.3G)
Overlay(2.6G)
Interleave(2.3G)/Interleave(2.3G) +
Overlay(2.6G)
Interleave(2.3G)/Overlay(2.6G)
Interleave(2.3G)/Interleave(2.3G)
+ Overlay(2.6G)/Overlay(2.6G)
Interleave(2.3G) +
Overlay(2.6G)/Overlay(2.6G)
Number of UE
UE
Source
Test Item
Test Method
RSRP/SINR
Call Drop Rate (nGBR)
Block Error Rate (BLER)
HOSR (Intra-Frequency)
HOSR (Inter-Frequency)
UE1
Data(DL)
Long Call
Throughput
Data(UL)
Long Call
VoLTE
Traffic Time/60Sec
10
Ping 32Bytes/1500Byte
Ping 32Bytes/1500Byte
Ping
Ping 32Bytes
Traffic Time/20 Sec
Ping 1500Bytes
(Including header)
In car loss
Loss
RSRP
8dB
(Use the In car loss for the GAP of outdoor RSRP and in car tested environment)
11
1.1.1 DL Throughput
1.1.1.1 Purpose
1) To verify cell edge single user download throughput according to each morphology
2) Cell edge tests only for pilot cluster
7) System Environment
A.
Test Environment
12
Criteria
2) Result Conditions
13
1.1.2 UL Throughput
1.1.2.1 Purpose
1) To verify cell edge single user upload throughput each morphology
2) Cell edge tests only for pilot cluster
7) System Environment
B.
Test Environment
14
than 3 Gbytes.)
4) Save the upload throughput logs with RF condition and GPS information per location by
DM tool.
5) Summarize test result.
Criteria
>=256kbps
4) Result Conditions
15
7) System Environment
A.
Test Environment
B.
16
17
Criteria
>=99%
Test Environment
C.
Signaling Message :
18
19
KPI
Criteria
=<1000ms
4) Result Conditions
1.3.1.1 Purpose
1) To verify single user downlink throughput according to RF condition(0dB=< SINR =< 5dB)
2) This test is to be performed at Pilot Cluster only
Test Environment
20
Criteria
2 Mbps (FC1)
3 Mbps (FC2)
2) Result Conditions
21
Auto
4) 1 GPS
5) The test point should be RF conditions (5=<SINR=<10dB)
6) System Environment
A.
Test Environment
22
Criteria
4.8Mbps (FC1)
9 Mbps (FC2)
2) Result Conditions
23
Criteria
12Mbps (FC1)
24Mbps (FC2)
2) Result Conditions
24
Criteria
24Mbps (FC1)
47Mbps (FC2)
25
2) Result Conditions
26
Criteria
28Mbps (FC1)
60Mbps (FC2)
2) Result Conditions
27
Criteria
88 kbps (FC1)
128 kbps (FC2)
2) Result Conditions
28
29
3) Connect FTP server and start uploading predefined file of bigger than 1Gbytes size for 2
minutes
4) Summarize test result.
Criteria
2) Result Conditions
Test Environment
30
Criteria
5 Mbps (FC1)
12 Mbps (FC2))
2) Result Conditions
31
32
Criteria
6 Mbps (FC1)
17 Mbps (FC2)
2) Result Conditions
33
2.1.1 RSRP
2.1.1.1 Purpose
1) To Verify radio coverage at predefined drive route which is service coverage of the cluster
Test Environment
34
Value
RSRP
Must be higher than 90% of RSRP which meet the UL Throughput 256K
(90 % >= UL Throughput 256K)
2) Result Conditions
II.
Out of coverage
35
2.1.2 SINR
2.1.2.1 Purpose
1) To Verify radio coverage at predefined drive route which is service coverage of the cluster
Test Environment
36
Value
SINR
Overshooting
10%, SINR <= 2dB@RSRP is more than (outdoor RSRP +3dB in car loss)
3) Result Conditions
II.
Out of coverage
RSRP : Measure coverage area where RSRP>=(outdoor RSRP +3dB- in car loss)
37
2.2.
2.2.1.1 Purpose
1) To verify network accessibility Success Rate until predefined route is fully covered
7) Signaling Message :
38
39
KPI
Value
>=99%
3) Result Conditions
2.2.2.1 Purpose
1) To verify network accessibility entry time until predefined route is fully covered
Test Environment
40
3) Start drive test around the pre-defined drive route at 30-40 Kmph continuing the
Attach the UE to the network and detach according to call scenario with UE3, UE5
4) Result Conditions
41
KPI
Value
=<800ms
2.2.5.1 Purpose
1) To verify that dropped sessions are kept to a minimum until predefined route is fully covered
Test Environment
42
i.
2) Formula : Calculate the Call drop Rate = The number of Abnormal Release for DL DATA,
UL DATA) / (Summation of the number of Calls Attempts for DL DATA, UL DATA) x100
3) No. of call drops/ No. call attempts %,
A.
B.
Value
=< 1%
4) Result Conditions
43
2.2.8.1 Purpose
1) To verify that BLER is kept to a minimum until predefined route is fully covered
Test Environment
44
3) Start drive test around the pre-defined drive route at 30-40 Kmph continuing the
generate continuous DL traffic from UE 1 according to call scenario
4) Measure the downlink BLER which is an error rate of data transmission of PDSCH after
all HARQ procedures from UE1(DL DATA)
5) At the end of the drive route stop the logging and ensure that the log files are
saved
6) Summarize test result.
Value
Residual BLER
=< 1 %
3) Result Conditions
2.2.9.1 Purpose
1) To verify that is to measure the handover success rate within the covered area
45
Test Environment
Iperf/FTP
servers
EPC
eNB monitoring
tool
Test
UEs
`
Pre-determined route
Intra eNB
HO point
B.
eNB
Iperf/ftp
clients
eNB
Inter eNB
HO point
`
Intra eNB
HO point
Intra eNB
HO point
Test equipment
in vehicle
Call Flow
3) Start drive test around the pre-defined drive route at 30-40 Kmph continuing the
generate continuous DL traffic, Ping from UE 1 , UE2, UE5 according to call scenario
4) At the end of the drive route stop the logging and ensure that the log files are
save
46
Value
>= 99 %
HOSR
4) Result Conditions
2.2.10.1
Purpose
1) To verify that is to measure the handover Latency within the covered area
2.2.10.2
Test Environment
47
Iperf/FTP
servers
EPC
eNB monitoring
tool
Test
UEs
`
Pre-determined route
Intra eNB
HO point
B.
2.2.10.3
eNB
Iperf/ftp
clients
eNB
Inter eNB
HO point
`
Intra eNB
HO point
Intra eNB
HO point
Test equipment
in vehicle
Call Flow
Test Procedure
save
5) Summarize test result.
2.2.10.4
Pass/Fail Criteria
1) LatencyDefinition:rrcConnectionReconfiguration(HOCommand)torrcConnectionReconfig
48
KPI
Value
Handover Latency
=< 40 ms
3) Result Conditions
2.2.12.1 Purpose
1) Verify user throughput at predefined drive route
Test Environment
49
Value
>= 10.5Mbps
2) Result Conditions
50
2.2.13.1 Purpose
1) Verify user throughput at predefined drive route
Test Environment
51
Value
>= 2.0Mbps
3) Result Conditions
52
2.3.
Mobility Test(VoLTE)
2.3.1.1
Purpose
1) To verify that is to measure VoLTE Call Setup Success Rate within the covered area
Test Environment
Test Environment
53
B.
Signal Flow
54
save
5) Summarize test result.
Attempts
A.
B.
Value
>=99 %
3) Result Conditions
II.
Out of coverage
55
Test Environment
56
4) At the end of the drive route stop the logging and ensure that the log files are save
5) Summarize test result.
2.6.13.3
1)
Pass/Fail Criteria
VoLTE Call Setup Time Definition: From "SIP INVITE" message transmission (by
Value
>=99 %
3) Result Conditions
57
Test Environment
save
5) Summarize test result.
58
Drop
rate
Definition
Abnormal
Release
UE
is
released
without
rrcConnectionReleasemsg.
A.
ii.
2) Formula : Calculate the Call drop Rate = The number of Abnormal Release for VoLTE) /
(Summation of the number of Calls Attempts for VoLTE Call) x100
3) No. of call drops/ No. call attempts %,
A.
The number of Call Attempts for UE3(VoLTE) : The number of Call Attempts for : VoS
Call Count
KPI
Value
=<1 %
4) Result Conditions
59
A. Test Environment
Iperf/FTP
servers
EPC
eNB monitoring
tool
Test
UEs
`
Pre-determined route
eNB
Intra eNB
HO point
B.
Iperf/ftp
clients
eNB
Inter eNB
HO point
`
Intra eNB
HO point
Intra eNB
HO point
Test equipment
in vehicle
Call Flow
60
4) Start drive test around the pre-defined drive route at 30-40 Kmph continuing the
generate VoLTE Call between Mobile Originated(MO) and Mobile Termination(MT)
according to call scenario
4) At the end of the drive route stop the logging and ensure that the log files are
save
5) Summarize test result.
Value
>= 99 %
2) Result Conditions
61
C. Test Environment
Iperf/FTP
servers
EPC
eNB monitoring
tool
Test
UEs
`
Pre-determined route
Intra eNB
HO point
eNB
Iperf/ftp
clients
eNB
Inter eNB
HO point
`
Intra eNB
HO point
Intra eNB
HO point
Test equipment
in vehicle
62
D.
Call Flow
3) Start drive test around the pre-defined drive route at 30-40 Kmph continuing the
generate VoLTE Call between Mobile Originated(MO) and Mobile Termination(MT)
according to call scenario
4) At the end of the drive route stop the logging and ensure that the log files are
save
5) Summarize test result.
Value
Handover Latency
=< 40 ms
3) Result Conditions
63
Purpose
1) To verify that is to measure the Packet delay variation(Jitter_GBR) within the covered
area
2.3.10.2
Test Environment
64
4) Start drive test around the pre-defined drive route at 30-40 Kmph continuing the
generate VoLTE Call between Mobile Originated(MO) and Mobile Termination(MT)
according to call scenario
5) At the end of the drive route stop the logging and ensure that the log files are
save
6) Using the VoLTE Call scenario, Calculate the Average jitter value
7) Summarize test result.
KPI
Report Only
65
2.3.11.1
Purpose
1) To verify that is to measure the Packet loss(GBR) within the covered area
2.3.11.2
2.4.11.3
Test Environment
Test Procedure
66
4) At the end of the drive route stop the logging and ensure that the log files are save
5) Using the VoLTE Call scenario, Calculate the Average Packet Loss
6) Summarize test result.
2.4.11.4
Pass/Fail Criteria
Value
Packet Loss
Report Only
2) Result Conditions
2.4.
67
Value
=<45 ms
Packet Loss
=<1 %
68
Test Environment
4) At the end of the drive route stop the logging and ensure that the log files are
save
5) Summarize test result.
RTT : "PING REQ" message transmission (by UE) to "PING RSP" message reception (by
UE).
69
2) Packet Loss : The number of Lost Packets / The number of Transmitted Packets
KPI
Value
=<75 ms
Packet Loss
=<1 %
3) Result Conditions
II.
70
MobilityTest(VoLTE MOS)
Test Environment
71
3) Start drive test around the pre-defined drive route at 30-40 Kmph continuing the
generate VoLTE Call between Mobile Originated(MO) and Mobile Termination(MT)
according to call scenario
4) At the end of the drive route stop the logging and ensure that the log files are save
5) Calculate the MOS results for MO and MT separately based on M2M test.
KPI
POLQA WB MOS
AMR-WB, 12.65 kbps
POLQA WB MOS
AMR-WB, 6.6 kbps
>= 3.6
>= 3.0
4) Result Conditions
72
CHAPTER 4. Appendix
4.1.
Legend Setting
4.4.1.1 RSRP
4.4.1.2 RSRQ
4.4.1.3 SINR
4.4.1.4 Tx Power UL
73
74