Cluster Optimization

Prepared by:
Samsung
 Course Name: SCFT Procedure
Course Objective Who should attend
This module will enable participants RF / DT engineers, Riggers
to understand how to conduct
Cluster Optimization Drive

Morning Session (10:30am to 1:30pm) Afternoon Session (2:30pm to 6pm)

Lunch break
•XCAL Demonstration

Day 1 • Hands on exercises

 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

 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
Introduction to Cluster Optimization
 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
 Cluster Optimization High-level Process

Drive 1 Optimization Drive 2

• First cluster drive • Post-analysis • Second Drive
after 80 % of the changes to Test result will be
sites pass SCFT & network compared with
EMF the first Drive
Test for worst
areas by
measuring entire
signal
environment
after change in
System
Parameters and
adjustments of
Antenna
 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

 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
 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
Test Procedure
 Tests to be conducted

FTP Downlink Long Call

FTP Uplink Long Call

VoLTE Long Call

4 UE’s : 1 Master, 3 Slaves VoLTE Short Call

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

Handover

Retainability

Accessibility

VoLTE Quality
[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

Index KPI Type of Call Target Value No. of UE's

RSRP Coverage per
1 Downlink data long >95% 1
Morphology

No. of Overlapping Server

2 Downlink data long > 90% 1
within 5dB, < 3 Servers

No. of Overlapping Server

3 Downlink data long > 60% 1
within 5dB, < 2 Servers

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
Average UL Throughput
7 Uplink data long > 2.5M 1
(Mbps)
 RSRP by Morphology

Parameter Morphology Criteria

> -107dBm for 95% of

Dense Urban
samples

> -110dBm for 95% of

Medium Urban
samples
RSRP
> -113dBm for 95% of
SubUrban
samples

> -116dBm for 95% of

Rural
samples
 Handover Test
Following test cases shall be conducted & will be mandatory for pass/fail criteria

Index KPI Type of Call Target Value No. of UE's

Downlink data
11 Handover Success Rate long + Uplink data > 98% 3
long + VoLTE long

Handover Interruption
Downlink data
Time
12 long + Uplink data > 95% 3
< 50ms + UE Switching
long + VoLTE long
Time
 Retainability Test
Following test cases shall be conducted & will be mandatory for pass/fail criteria
c

Index KPI Type of Call Target Value No. of UE's

Downlink data
13 Call Drop Rate* long + Uplink data TBD 3
long + VoLTE long
 Accessibility Test
Following test cases shall be conducted & will be mandatory for pass/fail criteria

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

VoLTE Attach Time < 3.5

17 VoLTE Short* TBD 1
sec
 VoLTE Quality Test
Following test cases shall be conducted & will be mandatory for pass/fail criteria

Index KPI Type of Call Target Value No. of UE's

RTP Packet Loss and

19 VoLTE Long* TBD 1
Discard Rate

e2e one way delay <

20 VoLTE Long* TBD 1
100ms

Packet Delay Variation

21 VoLTE Long* TBD 1
(Jitter) < 40ms