Cluster Optimization

Prepared by:
Samsung

Course Name: SCFT Procedure

Morning Session (10:30am to 1:30pm)

Day 1

Lunch break

Course Objective
Who should attend
This module will enable participants
RF / DT engineers, Riggers
to understand how to conduct
Cluster Optimization Drive

Afternoon Session (2:30pm to 6pm)

XCAL Demonstration
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 eNBs
Contiguous coverage
Can cross TA boundaries

Test entrance criteria

(((

(((

(((

(((

(((

(((

At least 80% of the eNBs 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
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

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

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 UEs : 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

Test Call
Ping Google server
OCNS Loading
Site Coverage

Sector Overshooting

Coverage overlapping

Accessibility

Quality check

Mobility/Retainability
Worst Area

Parameter

Action

FTP Test Call Upload & Download

Ping from command prompt
Loading effect 76% in the downlink
Analysis of RSRP,SINR plot, PCI plot

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

1. Analysis based on each sector

coverage area and handover till
adjacent cluster boundary 2.SCFT
report should be considered for
reference
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

Attach success rate, RACH success

rate, Tracking area update success
rate
Analysis for weak DL & UL
throughput areas. Analysis based on
interference, overlapping, Handoff
issues, SINR, hardware issues etc

KPI analysis w.r.t benchmark and

optimization after 1st drive test

Handoff, call drop

Specific issues for Handoff, call drops should

be analyzed and optimized accordingly
Optimization suggestion should be given to
improve worst areas

Analysis for the worst area for

Throughput, SINR, Low coverage etc

Optimization suggestion should be given to

improve weak throughput 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

Target Value

No. of UE's

RSRP
Coverage
Morphology

Downlink data long

>95%

No. of Overlapping Server

Downlink data long
within 5dB, < 3 Servers

> 90%

No. of Overlapping Server

Downlink data long
within 5dB, < 2 Servers

> 60%

DL Throughput > 2Mbps

Downlink data long

> 95%

Average DL Throughput

Downlink data long

> 14.5M

UL Throughput > 256kbps

Uplink data long

> 95%

Average
(Mbps)

Uplink data long

> 2.5M

UL

per

Type of Call

Throughput

RSRP by Morphology

Parameter

Morphology

Criteria

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

RSRP

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

Index

11

KPI

Type of Call

Target Value

No. of UE's

Downlink
data
long + Uplink data
long + VoLTE long

> 98%

Interruption
Downlink
data
Time
long + Uplink data
< 50ms + UE Switching
long + VoLTE long
Time

> 95%

Handover Success Rate

Handover
12

Retainability Test
Following test cases shall be conducted & will be mandatory for pass/fail criteria
c

Index

13

KPI

Call Drop Rate*

Type of Call

Target Value

No. of UE's

Downlink
data
long + Uplink data
long + VoLTE long

TBD

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

15

Attach Success Rate

VoLTE Short*

TBD

16

Detach Success Rate

VoLTE Short*

TBD

17

VoLTE Attach Time < 3.5

sec

VoLTE Short*

TBD

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

19

RTP Packet Loss and

Discard Rate

VoLTE Long*

TBD

20

e2e one way delay <

100ms

VoLTE Long*

TBD

21

Packet Delay Variation

(Jitter) < 40ms

VoLTE Long*

TBD