Clot V6.0

Cluster Optimization
Prepared by:
Samsung
Course Name : CLOT Procedure

Who should attend
Course Objective
Field Engineers/DT Engineers

This module will enable participants
(SOLPAR)
to understand and conduct or Project Manager (SOLPAR)
Samsung Optimizer(Samsung)
Manage Cluster Optimization.
Area Manager (Samsung)
Circle Head (Samsung)
RF Head(Samsung)
Afternoon Session (2:30pm to 6pm)
CLOT Introduction
Day 1
Test procedure
Lunch break
Morning Session (10:30am to 1:30pm)
WAS
XCAL Demonstration
Hands on exercises
Document History
Edition
Date of Issue
V1.0
-----
V1.3
14August2014
Author
Remarks
Samsung
Initial Version
Training Team
Samsung
Updated with 5 tests and screen shots for test
Training Team procedures
Samsung
Training Team Updated with WAS Procedure
V2.0
5fth Nov2014
V4.0
10th Oct 2015
Samsung
Totally revamped and updated with APK 524
Training Team
V5.0
27th
Samsung
Updated with APK 529 and 850 MHz Clot scenarios
Training Team
and KPIs.
Oct 2015
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
CHAPTER 1: CLOT Introduction
LTE System Introduction

Definition and purpose of CLOT
CLOT Terminologies
Factors that affect CLOT
Cluster Optimization Criteria
CLOT process
Tools and equipment for DT
Optimization System
Tools for Post processing analysis
CLOT objective , an introduction to KPIs
CHAPTER 2: Activity before CLOT DRIVE
DT Cluster selection
What is Front why it is necessary
Installing XCAL apk
Features of APK 529
Pre-Checks
Pre-Check for Rigger

Pre-Check with LSM-R Engineer ( NW Availability , Alarm check)
Pre-check for DT Engineer ( Antenna validation, UE configuration, Network
configuration, Key parameters , Alarm check before DT starts)
CHAPTER 3: Activity during DT
Drive Route guidelines

Call Scenarios
Drive setup
CLOT Test scenario GUI description
Test scenario for 850MHz
Additional GUI information
Agenda
CHAPTER 4: Activity after DT
Log file upload to FMS

Optimization process
Optimization process by NHQ
Apply recommendation by NHQ in field
DRIVE-2
CLOT Report
CHAPTER 5 : CLOT failure reasons
Missing Route
Recommendation not applied
Site SWAP not noticed
Site down / Alarm
CHAPTER 6 : Prohibited actions
Manipulation of Log files

Unclear justification
Not applying Optimizer recommendations
Missing parameter update in SF
CHAPTER 7 : CLOT process via SiteForge
CLOT Work flow

Optimization results on site forge for field application
Project closure
CHAPTER 1: CLOT Introduction
LTE System Introduction - Evolution of Cellular Networks

Packet core
Packet switched
data
Peak data
rates
Circuit switched
voice support
1G
1980s
1990s
Late 90s
2000
2003
2008
2010 onwards
LTE System Introduction : Network Comparison

IP
PSTN
IP
GGSN
GMSC
Core
Network
MSC
BSC / RNC
Access
Network
BTS / NodeB
GSM / WCDMA
SGSN
Single-node access
network
Completely PS network
Separate USER and
CONTROL planes
Controller node in access

network
Separate CS and PS cores
Combined user and
control planes
eNodeB
LTE
LTE System Introduction : LTE Network Architecture

External 3GPP Core
Network
EPC
E-UTRAN
S3
S6a
eNodeB
S4
X2
S1-C
Uu
Gx
S11
eNodeB
S1-U
S5 / S8
SGi
Combined into
SAE - GW
PDN
Definition of a cluster
Wireless system utilize number of low-power
transmitted to create many cells and then form a
cluster.
The Cluster consist the group os several eNBs. The
purpose is to check interworking between each eNB
and overall network quality, service environment
and each signal coverage as well as Up/Download
data throughput and Handover function on the
move can be checked.
Clusters Definition
Cluster can be small (2 sites ) or large up to 30 sites.
Cluster may have EARFCN , TA as well as LSM
boundary.
Sites can be located in different morphology area
but still cab be art of cluster occasionally, in rural
area cluster may not have contiguous coverage.
BSP boundary is the main boundary for any
clusters not based on cluster boundary
Purpose of CLOT
SCFT Aims to ensure the following
Site is properly installed.
Site parameters are properly configured.
Services are available.
CLOT aims to provide the following
Optimize signal coverage
Ensure normal distribution of RF Signals
Control PCI pollution
Meet all agreed KPIs
CLOT Terminologies What is BSP

BSP stands for Best Server Plot which is nothing but predicated signal strength of
each cell.
It is generated by RF planning software such as Atoll tool to give reasonable
approximation as to how many sites required to
provide LTE services in City, Town or rural areas and how far LTE coverage footprint
would go.
It takes many factors in to consideration to generate BSP.
Factors such as Frequency Band, Antenna (Type, Beawidth, Height, Orientation)
Morphology, UL/DL Path loss model.
It aids to guesstimate drive route and Actix use as reference to draw exclusion
boundary line in order to calcuate KPIs.
CLOT Terminologies M-tilt and E-tilt

Tilts : Following E&M tilts guidelines are used prior to cluster
drive
M-tilt=0, E-tilt=4/2 urban/rural or hwy morphologies.
M-TILT
The pattern in front goes down and behind goes up.
The guideline recommended that mechanical down tilt
of an antenna should not exceed more than one-half of
its vertical beam width.
E-TILT
The pattern droops all around like an inverted saucer.
Depending upon scenarios cells can be E-down tilted or Eup tilted.
EDT applied to contain over propagating signal.
EUT applied to increase cell foot print.
CLOT Terminologies What is RSRP and SINR

RSRP
Reference Signal Received Power
Coverage footprint
Aids handover
Ranges -44dBm - -140dBm
SINR
Signal to Interference & Noise ratio
Measure network strength
SINR gives the idea about channel conditions.
Major contributor for throughput KPI
SINR=(S/I+N)
RF Conditions
RSRP(dBm)
SINR(dB)
Excellent
>=-80
>=20
Good
(-80 to -90)
(13 to 20)
Mid Cell
(-90 to -100)
(0 to 13)
Cell Edge
<=-100
<=0
LTE Network Factors that affect CLOT

1.
2.
3.
4.
Antenna Type
Antenna Azimuth
Antenna Height
Antenna Tilt
Cluster Optimization Test Criteria

(((
(((
Test entrance criteria

At least 90% of the eNBs in the test
cluster shall have passed SCFT and
shall have compliance with EMF
norms
(((
(((
(((
(((
Cluster Definition
Minimum of 25 to 30 eNBs
Contiguous coverage
Can cross TA boundaries
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
DT Front should be 98%(discussed
later)
CLOT Work Flow

Before CLOT
Additional process
Main process
SELECT NEW
CLUSTER TO BE
DRIVEN
1. CLOT Triggered
for CLOT Test
Site On-air
2. DTR Preparation
SCFT & EMF

Cluster
Ready
>=90%
4a. Hold, If JIRA not

cleared
3. NAV >=98%
NOK
NOK
OK
NOK
5a. Hold if Site Down
6a. Hold if Site Down
NOK
4. CLOT PreCheck
Request via
JRA OK
Additional process
9a. Recommendation
for Improvement like
Change Parameter
Request
Parameter Implement
Update in SiteForge
Go for DT+
5.
Online
Surveilla
nce
RequestOK
6. Go
for DT1
OK
7a. Justification
submission to NOPT
(Pics of Block road)
7. 100%
Route
Covered
8.
Analysis
(NOPT)
9. Are
KPIs
met
10. Report
Submission
Tools and Equipment for DT

Check list for RIGGER
Weather proofing kit.

Complete Tool Kit (Spanners/Knife/Hammer/Cable Tie etc.)
Connector making tools.
Safety belts
Safety shoes
Helmet
Rope with board and extra riggers (with full protective gear) in case of
wall mount sites.
First aid box
Annexure - 3 to be filled up and handed over to SOLPAR PM, who sends
it over to Samsung RF manager.
Tools and equipment for DT

Checklist for Rigger Contd
LTE Network Optimization System
Tools for Post processing
XCAP
Post processing
tool
Log file analysis
AnyPlan Optimizer
Simulation tool
Physical
optimization
recommendations
Actix One
Post processing
tool
KPI report
generation
Tools for Post processing contd
Atoll
RF Planning
tool
BSP Plot
generation
MapInfo
XCAL
Geo mapping
tool
Drive route
creation
Drive test tool

Field
Measurement
Clot Objective : Introduction to KPIs

Field Drive Test:
Field engineer will start performing field drive test after completing site survey successfully. Field engineer
will use 5 handsets to perform five tests using Accuver DM tool installed in mobile handset.
Each handset will perform one of the test given below
1. LDL 1
2. LDL 2
3. LUL
4. VoLTE Long
5. VoLTE Short
All test scenarios are already predefined in Accuver DM tool. Drive test engineer will select different test
scenarios per handset.
Introduction
About Exclusion & Non Exclusion
Zone
to KPIs
Cluster A
PCI capture
during
drive
Cluster B
BSP of Site
222222222222222222233333333333333333444444444444455555
Drive Route
Zone
PCI belongs
to target
Cluster Site
Drive within Best

server Plot of
Target Cluster Site
Drive within Best server

plot of Active Site
Exclusion / Non
Exclusion ZONE of
Cluster A
Non Exclusion Zone
Exclusion Zone
Exclusion Zone
Non Exclusion Zone
Remark
In this case Site 1 of Cluster A is not active
In this case another cluster site is over shooting

In this case drive has been done out of Cluster coverage
Non Active Site = If PCI of site not found during drive

5 mtr
5 mtr
All Drive Samples
5x5 Area Bin samples

( Bin Sample is avg value of all samples in 5x5 grid )
01. Cluster Acceptance Checklist
CLOT ACCEPTANCE REPORT
KPIs
Call Model
Category
Target
Value
Non-Exclusion
Exclusion
Status
RSRP
LDL, LUL
KPI
>= 95 %
97.70% (28835 /29514)
97.72% (27691 /28336)
PASS
RSRP 2300
Ping 2300
Info
Report Only
RSRP 1800
Ping 1800
Info
Report Only
SINR >= -2 dB
LDL, LUL
Info
96.81% (26252/27116)
96.87% (25481/26304)
Report Only
Overlapping Servers within 5 dB <= 1
LDL, LUL
KPI
>= 60 %
75.08% (20207 /26915)
75.25% (19493 /25904)
PASS
Overlapping Servers within 5 dB <= 2
LDL, LUL
KPI
>= 90 %
94.97% (25560 /26915)
94.90% (24583 /25904)
PASS
PCI for all Sectors Observed
LDL, LUL
Info
60 / 63
Report Only
MAC Throughput DL >= 1024 Kbps
LDL
KPI
93.40% (30422/32573)
93.55% (29588/31628)
PASS
MAC Throughput UL >= 256 kbps
LUL
KPI
>= 95 %
99.88% (16797/16818)
99.87% (16300/16322)
PASS
Average MAC Throughput DL (kbps)
LDL
KPI
>= 5,120
8,553.35
8,617.83
PASS
Average MAC Throughput UL (kbps)
LUL
KPI
>= 3,200
4,670.68
4,704.32
PASS
Call Drop Rate
LDL, LUL
KPI
<= 1 %
0.07% (2/2908.90)
0.07% (2/2837.61)
PASS
TAU Success Rate
LDL, LUL
Info
95.00% (19/20)
94.74% (18/19)
Report Only
Handover Success Rate
LDL, LUL
KPI
>= 98 %
98.27% (2220/2259)
98.22% (2098/2136)
PASS
Handover Success Rate of 2300
Ping 2300
Info
Report Only
Handover Success Rate of 1800
Ping 1800
Info
Report Only
Handover Interruption Time < 100ms
LDL, LUL
KPI
>= 95 %
99.64% (2212/2220)
99.62% (2090/2098)
PASS
RACH Success Rate
VoS
KPI
>= 99 %
100.00% (819/819)
100.00% (799/799)
PASS
Attach Success Rate
VoS
Info
99.87% (774/775)
100.00% (752/752)
Report Only
VoLTE Setup Success Rate
VoS
Info
100.00% (771/771)
100.00% (749/749)
Report Only
Attach Setup Time < 1.5 s
VoS
Info
100.00% (0.70)
100.00% (0.70)
Report Only
IMS Registration Setup Time < 1.5 s
VoS
Info
0.00% (2.62)
0.00% (2.62)
Report Only
VoLTE Setup Time < 1.5 s
VoS
Info
99.09% (0.78)
99.20% (0.78)
Report Only
VoLTE Jitter < 40 ms
VoS
KPI
>= 95 %
100.00% (01.47)
100.00% (01.50)
PASS
VoLTE Latency < 100 ms
VoS
KPI
>= 95 %
100.00% (10.47)
100.00% (10.12)
PASS
VoLTE RTP Packet Loss Rate
VoS
KPI
<= 1 %
0.15%
0.18%
PASS
CHAPTER 2 : Activity before CLOT DRIVE
Selection of cluster
> 90% sites

SCFT & EMF
done
No Alarm on
any ENB in the
cluster
CLUSTER SELECTED
Past 3 days
network
availability >=
98%
What is front
>= 90% SCFT & EMF

compliant sites
Past 3 days NAV of All
ready for drive sites >=98%
All sites in cluster are alarm
free
Installing new 529 XCAL APK in handset
New XCAL APK version 529 is released
850 MHz BAND support
New GUI introduced
5 handsets for CLOT remain unchanged
Installing new XCAL
Remove
Install
Work
Remove existing XCAL app

from mobile
Installing new XCAL APK
Making XCAL work- some tips
to remember
1. Remove existing XCAL app

1. From Mobile front screen select Settings go to Application
Manager
1.Remove existing XCAL app ..continued

1. Select XCAL and UNINSTALL

1. Select XCAL Router and UNINSTALL

1. Select XCAL Service and UNINSTALL

1. Go back to Mobile home page and select My Files Select
Device storage

Device storage
2. Install new XCAL 524 app

Device storage - Download (if APK 529 is copied in download)
2. Install new XCAL 529 app

Select new apk 529 from folder and install.
Installing XCAL
Next..Next until installation complete.
Pre-requirements to make XCAL work

Following are required to make X-CAL work
1. WiFi should be OFF
2. Mobile network should be in LTE only mode
3. SIM card selected for Data should be RJIL
4. Mobile data should be ON
5. Location mode ON
6. Data roaming ON
Making XCAL work

Launch X-CAL from Mobile app page for license select IMEI and download license
( If LTE connection is not successful license update will fail)
Making XCAL work

Select the band for testing. If it is tri band cluster we can select 2300
Making XCAL work

Making XCAL work

Select the band for testing. If it is tri band cluster we can select 2300 to start the test
Select the 3 dots to

go to FMS mode
Pre-Checks
Pre-Check
Pre-check for RIGGER
Weather proofing kit.

Tool Kit (Spanners/Knife/Hammer/Cable Tie etc.)
Connector making tools.
Safety belts
Safety shoes
Helmet
Rope with board and extra riggers (with full protective gear) in case of
wall mount sites.
First aid box
Annexure - 3 to be filled up and handed over to SOLPAR PM, who sends
it over to Samsung RF manager.
Pre-Check
Checklist for Rigger Contd
Pre-Check for LSMR Engineer

Pre-Check with LSM-R
Enable 76% OCNS loading on all eNBs of target cluster & disable Smart scheduler
function.
The LSMR engineer should confirm the PE details to the SOLPAR engineer
If site has service impacting alarm (like VSWR, backhaul issue, card failure etc.) that
need site visit by deployment team
Sites in targeted cluster should be operational
If a neighboring cluster is already launched, in that case the neighbor cluster should
also be alarm free, and so as to avoid any handover related issues during CLOT
Pre-Check for LSMR Engineer

Pre-Check with LSM-R contd
Below site parameters needs to be checked with given site database (cell ref).
In case of discrepancy he needs to get it rectified via LSMR engineer, in same PE.
Pre-checks for DT Engineer

DT Engineer should be fully aware of Cluster he is going to drive
Network configuration
Key parameters
Antenna Validation
Alarm check with LSMR before DT starts
Hard copy of drive route based on best server plot
5 handset FULLY CHARGED with XCAL loaded and sufficient storage space
Magnetic Compass, Tilt Meter & Laser meter.
Obtaining door key & site access via respective authority. Authorization letter from
RJIL, to conduct drive test.
DT Vehicle with inverter, extension box, Mobile holders
Planned Event co-ordination with LSMR engineer
Pre-checks for DT Engineer

Check License information of XCAL
CHAPTER-3 : Activity during DT
Drive Route guidelines

UE should be served by all sectors of every eNB in the cluster ( all PCIs)
Justification/approval needed if any PCIs cannot be covered
Include highways, major and minor roads in the cluster
Should cover all drivable roads, proof required for any blocked roads
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
UE position should be identical during drive tests
Do not cross 40 kmph
Drive route guidelines

Drive Route Guidelines
Check, whether the drive route along with site database is visible in map
window of XCAL Auto mobile. ( Handset with LDL2 test scenario for 2.3GHz
and 1.8GHz and 1800 ping handset for 850MHz) If he is not able to view the
map after said procedure, he should immediately inform the optimization
engineer via Samsung RF lead & withhold the drive until the map route is
uploaded.
The drive route is assumed to be covering, all motor-able roads not
accessible or cant be driven due to any blockage should be captured with a
snapshot for proof.
Drive route guidelines cont

Drive route sample
DT Engineer will instruct the car driver for the direction to be followed
based on pre-defined drive route based on GPS location in drive test
tool. Engineer will also carry the drive route handmade copy, during
the CLOT test.
Drive setup
1. Spike Guard, mobile charger & Handset
2. Cigarette lighter input inverter
3. Mobile holder
(1)
(2)
(3)
Drive setup guidelines

Setup & guidelines Arrange all five handsets in following configuration
Drive setup guidelines cont

Setup
& guidelines Arrange all five handsets in following configuration
Samsung LTE Core

Prime handset
Drive setup guidelines cont

Setup & guidelines cont
Check whether the GPS in all the mobiles, have got latched & stable GPS icon
appears
Check whether the mobiles are getting charged via car inverter
Start LDL1, LDL2, LUL, VoL & VoS calls simultaneously

Check whether the logs are getting generated
Start moving on the defined drive route, as seen on the map window of the XCAL
mobile.
Phone which is used to check the drive route, the map window should be
configured in such a way that, it should reflect the main KPI as the legend
Check the file size limit (50MB with DRX format) indication displayed on each
handset
Call Scenarios
Perform the 1st CLOT automation drive using XCAL- Auto Mobile
Total 5 call scenarios, should be running in parallel, over 5 different Samsung
Prime handsets.
2300Hz and 1800 MHz
850MHz
LDL1 (Long FTP download call 1).
Ping 1800
LUL (Long FTP Upload call).
LUL (Long FTP Upload call).
VoL (Long VoLTE call).
Ping 2300
VoS (Short VoLTE call).
VoS (Short VoLTE call).
Test Scenario for Clot 2300/1800MHz

LDL1
LUL
LDL2
VoL
VoS
FTP Downlink Long Call - LDL1 and LDL2

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.
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 (LUL)

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 Short Call (VoS)

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
VoLTE Long Call (VoL)

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
Step 1: Band Lock

After launching in XCAL in all 5 handset lock the band
For testing 2300 all 5 handset must be locked to 2300
For testing 1800 all 5 handset must be locked to 1800
For testing 850 MHz 3 handset should be locked to 850MHz and one to 2300 ( for
Ping 2300 test scenario) and another to 1800 ( for Ping 1800 test scenario)
Restart handset
Step 2: Select FMS Mode

Select the band for testing. If it is tri band cluster we can select 2300 to start the test
Select the 3 dots to

go to FMS mode
Step 3: Check the current band
Step 4: GPS Value

Select GPS Value and keep the icon pressed
Step 5: Select cluster

Select the cluster. The cluster DTR get downloaded
Step 6 : Select Setting Select Type

Select Setting and then click on Select Type
Step 7: Select Cycle

Select Cluster and Cycle C1
Step 8: Downloading DTR
Step 9: Select Scenario

Test Scenario for 2300 and 1800 band are LDL1,LDL2, LUL, VoS, VoL
Step 10 : Select FTP Server
Start Autocall
Press Start Button
Clot test Scenario-LDL1

Additional Requirements:
1.
2.
3.
SINR
PCI X/Y/Z(x=No of PCI found, Y=No of scft done , Z= total no of PCI in clot
MAP with DT route covered % bin
Note: Clot scenario is same for Band 2300/1800. So GUI is also same for both bands
Selected band
GPS Status window

Lock/Unlock
Latitude,longitude
RSRP Window
RSRP measured
No. of PCI for Cluster
No.of PCI found
During the drive
for selected cluster
Call Scenario
Traffic/Idle
FTP Connection window

Success/Fail
Server IP Address
Throughput window
MAC UL Throughput
PCI details
% of PCI found during

Drive
File Name
Clot test Scenario-LDL2

1.
2.
3.
4.
RSRP Window
SINR window
Serving PCI window.
GPS Status window

Lock/Unlock
Latitude,longitude
Note: Clot scenario is same for Band 2300/1800. So

GUI is also same for both bands
Selected band
UL Thoughput
Drive test route

completed
FTP Connection
window success/Fail
server IP address
Call Scenario
Traffic/Idle
File Name
Clot test Scenario-LUL

1.
2.
3.
SINR window
Selected band
GPS Status
window
Lock/Unlock
Lat/long
FTP Connection window

Success/Fail
Server IP Address
RSRP Window
RSRP measured
Throughput window
MAC UL Throughput
No. of PCI for

Cluster
No.of PCI found
During the drive
for selected
cluster
Serving PCI
PCI Details
File Name
Call Scenario
Traffic/Idle
Clot test Scenario-VoL

1.
2.
3.
4.
5.
6.
SINR window
Serving PCI
RSRP window
SIP message window
Selected band
GPS Status window
Lock/Unlock
Latitude,longitude
RTP Loss Window

Measured RTP Loss
RTP Loss % for KPI
Volte Call Result
Window
Success/fail
Call Scenario
Traffic/Idle
Note: Clot scenario is same for Band 2300/1800. So

GUI is also same for both bands
Clot test Scenario-VoS

1.
2.
3.
4.
RSRP window
SIP message window
Selected band
GPS Status
window
Lock/Unlock
Lat/long
SINR Window
Measured SINR
Min. SINR for Cluster
Attach Window
Success/Fail
Call Scenario
Traffic/Idle
RACH Window
RACH Attempt
RACH Success
RACH Fail
Volte Window
Success/Fail
Success/fail/total no of call
Test Scenario for Clot 850MHz

LDL1
LUL
P1800
P2300
VoS
Test Scenario for Band 850 MHz Clot
Clot test Scenario-Ping 1800

1.
2.
GPS Status
window
GPS
lock/unlock
status
Current
lat/long of UE
Selected Band
RSRP Window
Serving cell RSRP
SINR Window
Serving Cell SINR
Data Activity
window
Traffic/Idle
status
Test scenario
Name
Traffic/idle
time
SINR Threshold
Success/fail/total no of
ping
Clot test Scenario-Ping 2300

1.
2.
3.
RSRP window
Serving PCI
GPS Status
window
Lock/Unlock
Lat/long
Selected Band
Data Activity window
Traffic/Idle status
Drive route completed Bin %
count
RSRP Window
Serving cell
RSRP
Traffic/Idle time
Map window with PCI info

of cells
Success/fail/total no of ping
Important checks during DT

Check Alarms if any During DT with LSMR Engineer
Check for missing route. 100% route should be driven for CLOT to be successful
Check Sector SWAP : Most CLOT failure happens since DT engineer fail to
notice sector swap.
CHAPTER 4: Activity after DT
Log file upload to FMS

After stopping Autocall mode, one additional option added as cancel. So if you
select option cancel then logfile will save as cancel in place of in progress or
complete
Cancelled logfile will not be consider for report generation through Actix-One
2014 Samsung Electronics
90
Activity after DT
Inform SOLPAR Manager, Samsung RF lead & LSM-R engineer after task
completion drive1
Log files should be uploaded to FMS server. SOLPAR engineer should wait till all
the drive log files get uploaded.
Solpar DT engineer should complete approval process for cluster driven less than
pre-defined route
Once uploading is done, SOLPAR engineer will call LSM-R engineer to remove 76%
OCNS loading on the site & to start the smart scheduler function.
SOLPAR engineer needs to wait, till he gets confirmation from LSM-R engineer
regarding normal functioning of services.
SOLPAR engineer should inform Samsung RF lead via SOLPAR manager regarding
completion of drive test
CLOSE THE TASK THROUGH SITEFORGE
Optimization Process
Samsung Optimization engineer suggestion to SOLPAR Manager via RF lead.
SOLPAR engineer is not directly involved in this process.
Once the drive logs are uploaded into the server, the optimization engineer
will download the log files to be imported into AnyPlan optimizer software.
The software is used to give physical optimization suggestion, prior to CLOT2 drive by SOLPAR engineer.
The optimization engineer will verify these results and also analyze any bad
KPI results based on report of CLOT-1 drive.
Optimization engineer will provide his optimization inputs to the SOLPAR
manager through circle RF lead. He might give parametric optimization
suggestion to LSM-R engineer separately.
These inputs will be in mutual agreement with RJIL team.
Optimization Process
Maximize
Performance
Antenna
Parameters
OPTIMIZATION
Optimization Process contd..

Analyze Problem Areas and Find Solutions
Noise & Interference
Poor RF Area
System Parameters
1. Antenna Parameter
1. Cell planning parameters (PCID,

1. UL/DL RSRP
Preamble root sequence number)
2. SINR
2. Neighbor lists ( Remove blacklists
cells / Add omitted cells
3. Verify Interference
2. eNB Tx Power
3. HO Parameters ( A3-Event-Offset,
Hysteresis, Time-to-Trigger, etc)
Acceptance / Exit Criteria

Purpose
KPIs
Call Model
Category
3MHz
5MHz
10MHz
Exclusion/N
on
Exclusion
Remark
Exclusion
RSRP Criteria for 3MHz =

RSRP of 2300 + 13dB
RSRP of 2300 + 11dB
RSRP of 2300 + 8dB
RF Design
Validation
RSRP <= RSRP

Criteria
LDL, LUL
KPI
>=95%
>=95%
>=95%
RF Design
Validation
SINR >= -2 dB
LDL, LUL
Info
Info
Info
Info
Exclusion
Exclusion
RF Design
Validation
Overlapping Servers
within 5 dB <= 1
LDL, LUL
KPI
>=60%
>=60%
>=60%
Exclusion
Exclusion
RF Design
Validation
Overlapping Servers
within 5 dB <= 2
LDL, LUL
KPI
>=90%
>=90%
>=90%
Exclusion
Exclusion
RF Design
Validation
MAC Throughput DL
>= DL Edge TP
LDL
KPI
>=95%
>=95%
>=95%
Exclusion
DL Edge Throughput for 3MHz

= 500kbps
DL Edge Throughput for 5MHz
= 800kbps
DL Edge Throughput for
10MHz = 1,600kbps
RF Design
Validation
MAC Throughput UL
>= 256 kbps
LUL
KPI
>=95%
>=95%
>=95%
Exclusion
Exclusion
RF Design
Validation
Average MAC
Throughput DL (kbps)
LDL
KPI
>=3.0Mb
ps
>=5.0Mb
ps
>=10.0M
bps
Exclusion
Exclusion
RF Design
Validation
Average MAC
Throughput UL (kbps)
LUL
KPI
>=1.875
Mbps
>=3.125
Mbps
>=6.25M
bps
Exclusion
Exclusion
Handover Test
Handover Success
Rate
LDL, LUL
KPI
>=98%
>=98%
>=98%
Exclusion
Exclusion
Handover Test
Handover Interruption
Time < 100ms
LDL, LUL
KPI
>=95%
>=95%
>=95%
Exclusion
Exclusion
Acceptance / Exit Criteria

Accessibility
RACH Success Rate
VoS
KPI
>=99%
>=99%
>=99%
Exclusion
Non Exclusion
Retainability
Call Drop Rate
LDL, LUL
KPI
<=1%
<=1%
<=1%
Exclusion
Non Exclusion
VoLTE Quality
VoLTE Jitter < 40 ms
VoS
Info
Info
Info
Info
Exclusion
Non Exclusion
VoLTE Quality
VoLTE Latency < 100

ms
VoS
Info
Info
Info
Info
Exclusion
Non Exclusion
VoLTE Quality
VoLTE RTP Packet

Loss Rate
VoS
Info
Info
Info
Info
Exclusion
Non Exclusion
Additional
Information
PCI for all Sectors

Observed
LDL, LUL
Info
Info
Info
Info
Exclusion
Non Exclusion
Additional
Information
TAU Success Rate
LDL, LUL
Info
Info
Info
Info
Exclusion
Non Exclusion
RF Design
Validation of
1800 Mhz
RSRP of 1800
1800 Ping
Info
Info
Info
Info
Exclusion
Non Exclusion
Handover Test
1800
Handover Success
Rate of 1800
1800 Ping
Info
Info
Info
Info
Exclusion
Non Exclusion
RF Design
Validation of
2300 Mhz
RSRP of 2300
2300 Ping
Info
Info
Info
Info
Exclusion
Non Exclusion
Handover Test
1800
Handover Success
Rate of 2300
2300 Ping
Info
Info
Info
Info
Exclusion
Non Exclusion
Apply recommendation by NHQ
( Example only )
Site
ID
Drive-2
SOLPAR manager informs SOLPAR engineer to perform 2nd drive with
necessary optimization /Changes suggestion.
SOLPAR engineer gets the optimization task to be performed on affected
areas within the Cluster through SOLPAR manager.
Post this, SOLPAR engineer will continue with 2nd Cluster Optimization drive
preparations.
Preparation for CLOT process drive 2

Pre checks with LSM-R engineer prior to cluster drive 2
Perform the 2nd CLOT automation drive using XCAL- Auto Mobile
SOLPAR engineer, along with help of rigger, should perform necessary
optimization suggestion given by optimization engineer, as mentioned in
previous section.
Rest process as given in section 4 for CLOT needs to be re-performed by the
SOLPAR engineer.
Drive-2 Closure
Inform SOLPAR Manager, Samsung RF lead & LSM-R engineer after task
completion 2
CLOT task closure through SiteForge (At SOLPAR engineer end)

Note : Sites Radiating in Already Accepted Cluster
Once Fill in eNodeBs start radiating in a cluster (Cluster acceptance drive has
been completed with sites <100% & >90% in targeted cluster) then the drive
test for the fill in site should encompass the eNodeBs designed coverage area
as per RF design and up to 2 tier of neighbor eNodeB cells for that site
acceptance. The report for the site will be only Cluster acceptance report with
the drive test till the 2nd tier neighbor and no need to do separate SCFT for the
site
CHAPTER 5: CLOT failure reasons
CLOT Failure reasons

Main reason for CLOT failures are the following
Missing route : Occurs when all routes as per DTR are not covered
Antenna Recommendation not applied : If SOLPAR does not carry out
implementation of recommendations provided by optimization team before second
drive CLOT fails
Sector SWAP not noticed : Solpar need to identify the Sector Swap.
Site down / Alarm : If the Site goes down or Alarms are generated during DT and the
same is not noticed or rectified CLOT fails
Missing PCI found
UE Configuration issue: IPSEC not disabled
Cell ref Antenna parameter mismatch, discuss with RF lead
Details of Failure Categories:

Issue Category
DT Process Deviation
Check List
Missing Route
Not Apply Antenna
Parameter
Site Down
UE Issue
Detailed Description
- PCI not detected,
- Re-used logfile,
- Stationary Test,
- DT Plot mismatch between test scenarios
- Logfile corrupted / DTR changed (Solpar)
- DT Route Changed,
- Wrong DTR prepared (with not integrated sites),
- DT done on not triggered CLOT,
- Parameter mismatch in cellref,
- Cluster boundary issue,
- Missing logs in report
- Missing Route without justification and supporting photographs.
- Main Roads/Main Area not covered
- Recommendation not implemented on field/LSMR and not updated on Site forge.
- 1.8G/850M Antenna Parameters are not same as of 2.3G Passed Cluster or vice versa.
- Service affecting Alarm on Site during drive
- GTP Loss / Backhaul fluctuation during drive
- High RSSI during drive resulting in poor UL throughput/RACH Fail
- UE config issue (IPSec/IPv4 setting)
- GPS unlock during drive
- UE malfunctioning (Huge difference in RSRP level between different UEs)
102
Apply Antenna recommendation by NHQ
( Example only )
Make sure that default Antenna parameters are implemented on field

If it is a drive on a frequency for which the same cluster has already passed on
other frequency then the same antenna parameter needs to be applied on this
cluster as well
Make sure new antenna parameters are updated in site forge and Cell ref
Drive Route mismatch between Different UEs
As can be seen in the above snap, the drive route is different in all 3 scenarios, it
Could be because of UE issue, Human unforced error, Knowingly done.
At all times keep checking if your UE is still connected and GPS is not lost
Stationary
test done
Stationary
Test Done
As can be seen in above snap that Stationary drive has been done to improve samples
and KPI as a result.
Analysis team has macros that automatically identify if Stationary test has been done,
Doing the same will make you re-drive the cluster
LDL1: PCI Count check
LDL2: Drive Progress status
LDL2 v/s FMS: DT Progress % for RF Lead in FMS

DT Progress %
LUL Throughput
VOS: SINR & (RACH/Attach/VOLTE Setup) Success rate
VoL: RTP Loss
Action Items: Circle RF Lead

Circle RF Lead to ensure to train new Solpar engineer before deploying on field and ensure that they follow the proper process
during the drive and log upload.
Circle RF Lead to ensure to prepare the DTR for CLOT Triggered Sites and within the BSP strictly.
Circle RF Lead to ensure the planned CLOT given for alarm surveillance and timely information reaches to respective DT engineer in
case of any service affecting alarms.
Circle RF Lead to check and ensure that 1.8G & 850M antenna parameters matches with 2.3G passed cluster before giving go ahead
for 1.8G & 850M drive test.
Circle RF Lead to ensure all recommendations (Antenna parameters/Sector Swap removal) to be implemented on field/LSMR and
siteforge before starting the next level of drive test.
Circle RF Lead need to ensure that solpar engineer monitors the main KPIs i.e. DL/UL Throughput, VOLTE setup, Attach Success,
RACH Success during DT and should hold the drive if he finds any abnormality and contact to Help Desk for issue resolution. He
should resume the drive test once issue resolved.
Circle RF Lead need to ensure that solpar engineer monitors that all 5 test scenarios are continuously running during the drive test.
No stationary test to be conducted for any test scenario and old logfiles not to be reused in any circumstances.
Circle RF Lead to instruct Solpar engineer to prepare the less drive justification PPT during the upload of logfiles in to FMS and send
to respective circle & NHQ SPOCs so that it reaches to NHQ analyzers on time.
Circle RF Lead to ensure not to give blind approval for less drive cases until unless it is genuinely justified by solpar engineer. You can
ask photos & non driven area on whatsapp or on mail for necessary verification for approval.
112
CHAPTER 6: Prohibited actions
Prohibited actions during CLOT

Following actions are taken by SOLPAR which resulted in failure of CLOT
Manipulate of log files : Do not attempt to modify log files at any stage
Providing unclear justifications ( NEED CLEAR JUSTIFICATIONS)
Not implementing Optimizer recommendations
Missing parameter update in SF
Renaming should be correct.
Old logfiles should not be used.
Drive tester should stick to the guidelines provided by
QUIZ
Q 1) How many scenarios are there in 2300 MHz CLOT ?
Ans a) 3
b) 2
c) 5
d)4
Q 2) In 850 Mhz Clot, How many mobiles will be locked to 850 Mhz
band?
Ans a) 3
b) 2
c) 5
d)4
Q 3) In a cluster of 20 sites, atleast how many sites should have got

SCFT done ?
Ans a) 16
b) 18
c)19
b) 20
CHAPTER 7 : CLOT process through Siteforge
CLOT Process Flow Chart

Work assignment
through SiteForge
Preparation for CLOT

process - drive1
Pre checks with

LSM-R engineer
Perform the 1st CLOT

automation drive test
Inform SOLPAR
Manager,
Samsg. RF lead & LSM-R
CLOT task closure

(in Site Forge)
Samsung. Opt. Eng.

suggestion to
SOLPAR Mgr. via RF
lead
SOLPAR mgr. informs

SOLPAR engr. to
perform 2nd drive with
Changes on site.
Preparation for
CLOT process drive2
CLOT Process Flow Chart cont

Pre checks with
LSM-R engineer
prior to drive - 2
CLOT task closure

through SITE
FORGE
Perform the 2nd

CLOT drive
Repeat process,
to meet cluster
KPI
Infm. SOLPAR Mangr.,

Samsg. RF lead,LSM-R
eng. on completion
CLOT WORK FLOW

START
Reject
Auto trigger if
90% SCFT done Samsung RF
Lead
Samsung
OPT team
Accept
RJIL RF
Engineer
Reject
Accept
Samsung AM
RJIL RF
Lead
Solpar PM
Reject
RJIL CLOTAccept
QA
Auditor
Solpar Field Eng

for drive test -1
Accept
RJIL CLOT QA
Manager
Close
WAS workflow cont..

Cluster Task trigger
Drive route preparation and upload at FMS
AM assignment
SOLPAR Assignment
Field engineer assignment
Cluster task performed by field engineer
Report trigger to optimization engineer
Validation by optimization engineer
Report submission to RJIL central RF team for approval
RJIL central RF team accept the report.
Task closer
SiteForge log in window
Samsung RF Head window
Assignment for Cluster Task to AM
RF Head assign Task to AM
Assignment for Cluster Task to AM
RF Head assign Task to AM
Cluster Task assignment to AM
Work order assigned to AM
Cluster Task Assignment to SOLPAR PM
AM assign Cluster task to SOLPAR PM
Cluster task assigned to SOLPAR PM
Cluster Task assignment to Field engineer
Cluster task assign to field engineer
Cluster task assigned to field engineer
Cluster task activity by Field engineer
First time field engineer will perform the drive , upload log file and complete the task at Site Forge
Cluster task activity by Field engineer
Field engineer complete the Task
Optimization Engineer Task
Optimization engineer will download the Cluster report, Analyze and upload the suggestions at Site
forge when reject the TASK
Uploading Suggestions to SiteForge Site by site
Uploading Suggestions to SiteForge Site by site and Save.
Suggested parameter updated successfully
Suggested parameter updated successfully
Suggested parameter need to be update site wise for cluster all sites
After putting all suggested parameters , Optimizer will reject the task
After putting all suggested parameters , Optimizer will reject the task
Task rejected by Optimizer, rejected TASK will go to AM
Area Manager Task
Area Manager Task
AM re-assign the TASK to SOLPAR PM
Area Manager Task
Area Manager Task
Area Manager Task
Area Manager Task
Task re-assigned to SOLPAR PM
SOLPAR PM Task
SOLPAR PM assign TASK to Field engineer
SOLPAR PM Task
SOLPAR PM assign TASK to Field engineer
SOLPAR PM Task
TASK assigned to Field engineer
Field engineer Task
Field engineer will check suggested parameter and implement the changes
Field engineer Task
Field Engineer Task
Field Engineer Task
Field Engineer Task
Field Engineer Task
Field engineer will check suggested parameter and implement the changes and update at Siteforge
Field Engineer Task
Field Engineer Task
and verify .
Field Engineer Task
Field engineer will Perform the drive test and upload the log post all suggested changes .
After successful log upload he will complete the TASK.
Field Engineer Task
Task Completed by field engineer
Optimizer will download the report and analyze, if pass then will accept and send for RJIL Central RF
Team
Optimizer can check that suggested parameter has been implemented or not.
Optimizer accept the report with remark(if any) and send it to approval for RJIL Central RF Team
Optimizer accept the report with remark(if any) and send it to approval for RJIL Central RF Team
Reliance central RF
RJIL Central RF team accept the report
Reliance central RF
RJIL Central RF team accept the report and Task Closed.
Thanks

Clot V6.0

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Clot V6.0

Uploaded by

Copyright:

Available Formats

Cluster Optimization

Course Name : CLOT Procedure

Field Engineers/DT Engineers

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

10th Oct 2015

LTE System Introduction

CHAPTER 2: Activity before CLOT DRIVE

Pre-Check for Rigger

CHAPTER 3: Activity during DT

Drive Route guidelines

Log file upload to FMS

CHAPTER 5 : CLOT failure reasons

CHAPTER 6 : Prohibited actions

Manipulation of Log files

CHAPTER 7 : CLOT process via SiteForge

CLOT Work flow

CHAPTER 1: CLOT Introduction

LTE System Introduction - Evolution of Cellular Networks

LTE System Introduction : Network Comparison

Controller node in access

LTE System Introduction : LTE Network Architecture

Site is properly installed.

Site parameters are properly configured.

Services are available.

CLOT aims to provide the following

Optimize signal coverage

Ensure normal distribution of RF Signals

Control PCI pollution

Meet all agreed KPIs

CLOT Terminologies What is BSP

CLOT Terminologies M-tilt and E-tilt

CLOT Terminologies What is RSRP and SINR

LTE Network Factors that affect CLOT

Cluster Optimization Test Criteria

Test entrance criteria

SCFT and EMF compliance report for

Any changes to the eNB physical

CLOT Work Flow

SCFT & EMF

4a. Hold, If JIRA not

5a. Hold if Site Down

6a. Hold if Site Down

Tools and Equipment for DT

Weather proofing kit.

Tools and equipment for DT

LTE Network Optimization System

Tools for Post processing

Tools for Post processing contd

Drive test tool

Clot Objective : Introduction to KPIs

Drive within Best

Drive within Best server

Non Exclusion Zone

Non Exclusion Zone

In this case Site 1 of Cluster A is not active

In this case another cluster site is over shooting

Non Active Site = If PCI of site not found during drive

All Drive Samples

5x5 Area Bin samples

01. Cluster Acceptance Checklist

CLOT ACCEPTANCE REPORT

97.70% (28835 /29514)