cluster procedure

1. Cluster Optimization
Prepared by:
Samsung

2. Course Name: SCFT Procedure
Course Objective
This module will enable participants
to understand how to conduct
Cluster Optimization Drive
Who should attend
RF / DT engineers, Riggers
Morning Session (10:30am to 1:30pm)
Lunchbreak
Afternoon Session (2:30pm to 6pm)
Day 1
•XCAL Demonstration
• Hands on exercises

3. Good to know
Keep your mobile phone in the silent mode during the session
Need to sign attendance sheet at the start and end of each day
At the end of each training post test will be conducted
Stick to break timings
Your valuable feedback will be taken at the end to enhance training experience
For logistics support contact the co-ordinator

4. Agenda
Introduction
 Cluster Optimization Test Entrance Criteria
 High level process
 Drive Route Selection
Test Procedure
 Types of tests
 Checklist for cluster optimization
Cluster System Acceptance Test
 RF Design Validation
 Handover Test
 Retainability Test
 Accessibility Test
 VoLTE Quality

5. Introduction to Cluster Optimization

6. Cluster Optimization Test Entrance Criteria
Cluster Definition
 Minimum of 20 to 30 eNB’s
 Contiguous coverage
 Can cross TA boundaries
Test entrance criteria
 At least 80% of the eNB’s in the
test cluster shall have passed
SCFT and shall have compliance
with EMF norms
 SCFT and EMF compliance
report for each eNB for the test
cluster has to be verified
 Any changes to the eNB physical
configuration required for EMF
compliance shall be updated in
the cluster database
(((
(((
(((
(((
(((
(((
(((
((( (((
(((

7. Cluster Optimization High-level Process
Drive 1
• First cluster drive
after 80 % of the
sites pass SCFT &
EMF
Optimization
• Post-analysis
changes to
network
Drive 2
• Second Drive
Test result will be
compared with
the first Drive
Test for worst
areas by
measuring entire
signal
environment
after change in
System
Parameters and
adjustments of
Antenna

8. Drive Route Selection
UE should be served by all sectors of every eNB in the cluster
Include highways, major and minor roads in the cluster
Route should represent potential subscriber usage locations
Should not leave the designed coverage area for the cluster
First and second drive routes should remain identical
Conditions (e.g. UE position) should be identical between drives
Do not cross 40 kmph

9. SCFT + Cluster Drive Case
Suppose an eNB comes on-air after the rest of the cluster
For that site, SCFT & Cluster optimization drive test should be done till first tier
neighbors for the site

10. Drive Route for late on-air site
B B
1. Drive route for Cluster when Site B is not on Air 2. Drive route for Sub Cluster after Site B is on Air

11. Test Procedure

12. Tests to be conducted
FTP Downlink Long Call
FTP Uplink Long Call
VoLTE Long Call
VoLTE Short Call4 UE’s : 1 Master, 3 Slaves

13. FTP Downlink Long Call
Ensure that OCNS is enabled for all eNBs in the
cluster with 76% downlink load
Ensure that the UE is successfully attached to
the LTE network
Select the appropriate UE and download the
FTP DL Scenario from FMS
Start the Autocall test. FTP download uses a
single file with the highest possible
compression and file size of 8GB. (Attach to
detach - 60 min & 10 Sec Idle time)
Ensure that the log files are being captured
Start traversing around the pre-defined drive
route at 30-40 Kmph, continuing the
FTP download and reinitiating in case of call
drop
At the end of the drive route stop the logging
and ensure that the log files are uploaded

14. FTP Uplink Long Call
Ensure that OCNS is enabled for all eNBs in the
cluster with 76% downlink load
Ensure that the UE is successfully attached to
the LTE network
Select the appropriate UE and download the
FTP UL Scenario from FMS
Start the Autocall test. FTP UL uses a single file
of highest possible compression and file size of
1GB. ( Attach to detach - 60 min & 10 Sec Idle
time)
Ensure that the log files are being captured
Start traversing around the pre-defined drive
route at 30-40 Kmph, continuing the
FTP upload and reinitiating in case of call drop
At the end of the drive route stop the logging
and ensure that the log files are uploaded

15. VoLTE Long Call
Ensure that OCNS is enabled for all eNBs in the
cluster with 76% downlink load
Ensure that the UE is successfully attached to
the LTE network and successfully registered for
VoLTE service
Select the appropriate UE and download the
VoLTE Long call Scenario from FMS
Start the Autocall test. Ensure that the log files
are being captured
Start traversing around the pre-defined drive
route at 30-40 Kmph, continuing the long call
and reinitiating in case of call drop
At the end of the drive route stop the logging
and ensure that the log files are uploaded

16. VoLTE Short Call
Ensure that OCNS is enabled for all eNBs in
the cluster with 76% downlink load
Ensure that the UE is successfully attached
to the LTE network and successfully
registered for VoLTE service
Select the appropriate UE and download
the VoLTE Short call Scenario from FMS
Start the Autocall test. Ensure that the log
files are being captured
Start traversing around the pre-defined
drive route at 30-40 Kmph, continuing the
short calls
At the end of the drive route stop the
logging and ensure that the log files are
uploaded

17. Checklist for Cluster Optimization
Items Parameter Action
Test Call FTP Test Call Upload & Download Before starting drive test make a test call
Ping Google server Ping from command prompt Before starting drive test try ping test
OCNS Loading Loading effect 76% in the downlink Before starting drive test
Site Coverage
Analysis of RSRP,SINR plot, PCI plot Optimization suggestions will be given after
post processing of 1st drive test
Sector Overshooting
1. Analysis based on each sector
coverage area and handover till
adjacent cluster boundary 2.SCFT
report should be considered for
reference
Optimization suggestions should be given
and which will be implemented after 1st
drive test in Cluster optimization
Coverage overlapping
Analysis based on each sector
coverage area using PCI plot of
serving cell
Optimization suggestions should be given to
reduce coverage overlapping and which will
be implemented in after 1st drive test in
Cluster optimization
Accessibility
Attach success rate, RACH success
rate, Tracking area update success
rate
KPI analysis w.r.t benchmark and
optimization after 1st drive test
Quality check
Analysis for weak DL & UL
throughput areas. Analysis based on
interference, overlapping, Handoff
issues, SINR, hardware issues etc
Optimization suggestion should be given to
improve weak throughput areas
Mobility/Retainability
Handoff, call drop Specific issues for Handoff, call drops should
be analyzed and optimized accordingly
Worst Area
Analysis for the worst area for
Throughput, SINR, Low coverage etc
Optimization suggestion should be given to
improve worst areas

18. Cluster System Acceptance Tests

19. Cluster System Acceptance Tests
RF Design Validation
Handover
Retainability
Accessibility
VoLTE Quality

20. Index KPI Type of Call Target Value No. of UE's
1
RSRP Coverage per
Morphology
Downlink data long >95% 1
2
No. of Overlapping Server
within 5dB, < 3 Servers
Downlink data long > 90% 1
3
No. of Overlapping Server
within 5dB, < 2 Servers
Downlink data long > 60% 1
4 DL Throughput > 2Mbps Downlink data long > 95% 1
5 Average DL Throughput Downlink data long > 14.5M 1
6 UL Throughput > 256kbps Uplink data long > 95% 1
7
Average UL Throughput
(Mbps)
Uplink data long > 2.5M 1
[JR1]Samsung modified table as per test case agreement between RJIL & Samsung
RF Design Validation Tests
Following test cases shall be conducted & will be mandatory for pass/fail criteria

21. RSRP by Morphology
Parameter Morphology Criteria
RSRP
Dense Urban
> -107dBm for 95% of
samples
Medium Urban
> -110dBm for 95% of
samples
SubUrban
> -113dBm for 95% of
samples
Rural
> -116dBm for 95% of
samples

22. Handover Test
Index KPI Type of Call Target Value No. of UE's
11 Handover Success Rate
Downlink data
long + Uplink data
long + VoLTE long
> 98% 3
12
Handover Interruption
Time
< 50ms + UE Switching
Time
Downlink data
long + Uplink data
long + VoLTE long
> 95% 3
Following test cases shall be conducted & will be mandatory for pass/fail criteria

23. Retainability Test
Index KPI Type of Call Target Value No. of UE's
13 Call Drop Rate*
Downlink data
long + Uplink data
long + VoLTE long
TBD 3
Following test cases shall be conducted & will be mandatory for pass/fail criteria
c

24. Accessibility Test
Index KPI Type of Call Target Value No. of UE's
14 RACH Success Rate VoLTE Short* TBD 1
15 Attach Success Rate VoLTE Short* TBD 1
16 Detach Success Rate VoLTE Short* TBD 1
17
VoLTE Attach Time < 3.5
sec
VoLTE Short* TBD 1
Following test cases shall be conducted & will be mandatory for pass/fail criteria

25. VoLTE Quality Test
Index KPI Type of Call Target Value No. of UE's
19
RTP Packet Loss and
Discard Rate
VoLTE Long* TBD 1
20
e2e one way delay <
100ms
VoLTE Long* TBD 1
21
Packet Delay Variation
(Jitter) < 40ms
VoLTE Long* TBD 1
Following test cases shall be conducted & will be mandatory for pass/fail criteria