Overall Process for SCVT_SV120.1.docx

0SAMSUNG ELECTRONICS

Overall Process for SCVT Document Number : SV120.1

This document is proprietary and confidential. No part of this document may be disclosed in any manner to a third party without the prior written consent.

Overall Process for SV 120.1 COPYRIGHT This manual is proprietary to Samsung Electronics Co., Ltd. and is protected by copyright. No information contained herein may be copied, translated, transcribed or duplicated for any commercial purposes or disclosed to the third party in any form without the prior written consent of SAMSUNG ELECTRONICS Co., Ltd. TRADEMARKS Product names mentioned in this manual may be trademarks and/or registered trademarks of their respective companies. This manual should be read and used as a guideline for properly conducting the field activity. This manual may be changed for the system improvement, standardization and other technical reasons without prior notice. ©2014 SAMSUNG ELECTRONICS Co., Ltd. All rights reserved.

Revision History: Document Number SV 120.1

Date of Remark Issue 14-01-2016 First version

Revision control: Document Number SV 120.1

What’s new First version

Suggestions and queries to be forwarded to: [email protected] This document is proprietary and confidential. No part of this document may be disclosed in any manner to a third party without the prior written consent Page |2

Overall Process for SV 120.1

Executive Summary SCVT (Single Cell Validation Test) is required for the sites which got Installed/Integrated after CLOT completion of the original cluster. SCVT Process is majorly divided in 3 categories. A. B. C. D.

Preparation for SCVT Execution of SCVT on Field Post processing Field Results Validating & Approving New SCVT report

During preparation for SCVT, Planning team will provide Samsung RF lead/ Area Manger should provide correct updated data to SOLPAR Field Engineer via SOLPAR Manager. Task assignment and closer should be done using Site forge Tool. SOLPAR Team must be ready with proper tools, vehicle & skilled man power. When Site forge will trigger newly integrated / 11 B completed site for SCVT, it will create new / sub cluster ID against that site. Circle team should provide Drive route for the new/sub cluster. On field SOLPAR team need to do physical verification with provided data & need to perform drive test activity with Accuver DM tool. After performing drive test activity field engineer should upload collected data. After completing field activity, post processing tool will process the uploaded data. Post processing tool used for this project is ActixOne. Major inputs for KPI calculation during post processing are defined formulae, Drive Log files, Cell data and Best server Plots. After processing log file Post processing tool will generate the report & upload it to Siteforge. From siteforge respective team will download the report to validate. If require then they will optimize the site parameters else accept the report. Tools used during SCVT are SiteForge( To Assign / closure of Task , share post processing results and update the data base ), Accuver DM( To perform field drive test),FMS server ( To download field test related data in handset and upload collected log files) and ActixOne( To post process collected Logs) If site could not able to clear defined criteria then reiterate the complete exercise after doing necessary optimization.

This document is proprietary and confidential. No part of this document may be disclosed in any manner to a third party without the prior written consent Page |3


Cell ref file

Preperation Best Server Plot

Site Survey

Excecution PCI & ET correction with LSM-R Engineer

Post Processing Post processing uploaded LOGS

Samsung Circle RF Lead Validation & RJILCircle RF Lead Approval RJIL CTO

Solpar Team Report Generation Drive Route

Samsung National Optimisation

Drive Test & Upload Log

RJIL central RF Team Rancore Team

STEP 1: Preparation of SCVT Sites gets installed/integrated in the cluster after CLOT activity completion, are eligible for SCVT. Such sites gets trigger by SiteForge or Area manger assigns the SCVT task to Solpar Manager via SiteForge. Prerequisite for the SCVT process is updated database need to upload in Drive test tool & post processing tool. Site database should be uploaded in ACCUVER DM tool & ActixOne Post processing tool in a specific format which is known as “Cellref” file. Along with Cellref there are two other important inputs require which are Cluster File in KML format & Best server Plots of all sites in TAB format.

About Cell Ref File: Cellref files are one of the most important and necessary pre-requisites data. There is specific name format for file “cellref_4g_.csv”. Site configuration details are given Cellref file. Most of the parameters gets define by RF planning team which they need to regularly update with respect to RFI/ TSSR data. Cluster, TAC information is depending upon the site location. To define Cluster & TAC details in Cellref file, we need to refer existing cluster boundaries which have been already defined for PAN India. Sometimes it requires redefining the boundaries of cluster so that all sites fit within cluster boundaries. ECGI details are on basis inputs given by eNodeB team against each eNodeB SAP data. Currently PCI are getting planned manually against each site, Similarly Electric tilt data need to update if planned tilt data mismatched with executed during implementation. These parameters field engineer need to confirm with LSMR engineer before performing drive test, if cellref data mismatch with LSM-R data then LSM-R details need to update. Cellref data should be considered as final data.

About Drive test Route: There is no defined drive route for SCVT. During moving test DT engineer should cover all motor able roads till 1st tire neighbors

Neighbor site Test site Drive route This document is proprietary and confidential. No part of this document may be disclosed in any manner to a third party without the prior written consent Page |4

Overall Process for SV 120.1 Figure 1 Drive test route sample

About Best Server Plot: Best server plots prepared by planning team. Physical data of sites consider during preparing best server must be same as data given cell ref file. If updated Cellref and Best server plots do not upload in post processing tool and Drive test tool prior to field test then field engineer can find difficulty to perform SCVT test as well as test results will not be accurate. SOLPAR Field Engineer should check all physical parameters on field. LSM-R engineer should support Field engineer to unlock the site and to update PCI, Electric Tilt and TAC details in LSM-R if require. If there is any alarm then LSM-R engineer should update field engineer. During Cluster Optimization LSMR engineer should apply following setting to all sites in cluster and sub cluster 1. 2. 3.

76% OCNS Loading Smart Scheduler Of eMBMS service of

For doing changes in HOTO sites, circle Samsung team need to raise PE. About PE : Pre-Requisites: • Login to Planned Event Portal • Updated List of HOTO Sites Process Applicable for HOTO Sites: • Raise blanket PE for week • Close the PE at the end of week with brief details. Escalation Process • Any issues with PE approval needs to be raised to Samsung Ops team (To be discussed with Samsung Ops team)

Area Manager should support Field engineer to access the site

STEP 2: Execution of SCVT on Field There are two major steps involved in SCVT. Site survey /auditing are first step and drive test is the second step.


Overall Process for SV 120.1 Site Survey/ Auditing: After completing requisite task mentioned in previous step, field engineer will start doing site survey once he reach to the site. Field engineer role in Site survey: Field engineer should cross verify site location and all other antenna parameters with details given in cell ref .If Cellref data and field data is mismatch then he should inform Samsung engineer as well as he should rectify antenna parameters on field with help or rigger. Similarly field engineer should coordinate with respective LSM-R engineer for LSM-R related activities like update LSM-R data, checking alarm and locking unlocking the site. Rigger role in Site survey: Rigger will support field engineer to measure field parameters by climbing on pole/ tower if require. If field engineer suggest doing any changes in antenna parameters like tilt, azimuth or height then he should execute it. For all such activities Rigger should carry required tools and consider safety measures. LSM-R engineer role in Site Survey: LSM-R engineer should support field engineer to check/update site parameters/alarms in LSM-R. LSM-R engineer is also responsible to lock /unlock the site & apply following setting to all sites in cluster 1. 2. 3. 4.

76% OCNS Loading Smart Scheduler Of eMBMS service of Collocated 1800 MHz Sites of( If available)

Field Drive Test: Field engineer will start performing field drive test after completing site survey successfully. Field engineer will do Drive test for the site with 3 devices as against 5 devices used in current CLOT process using Accuver DM tool installed in mobile handset, within the area which will cover 1tier neighboring sites location if possible.

In SCVT drive test activity there are two tests. a b

Stationary test with one mobile Moving test with 2 mobiles

 Stationary Test: 1 2

Drive test engineer will start the drive test activity with stationary test. Drive test engineer will move over to “Alpha sector” and perform following activities during the stationary test (to be performed under main lobe of the sector). a Latch on Alpha sector PCI and check RSRP, it should have a stable dominant RSRP level from serving cell, and neighbor cells should not be dominant. This is very important when the cluster has started to radiate in that case dominance has to be correctly observed before starting the test. b Check GPS status and select destination value of co-ordinates from map window. c Assign “Stationary-1” call setting with Cycle information & site details, (CYCLE should remain the same until the complete SCVT test (STATIONARY & MOVING) ends), if you have to restart the test cause of any issue then issue new and diferent cycle number, but it should be same for stationary and moving test (ideally it should be incremented by 1, every time you repeat the test on same site), cycle is a reference for naming the log files. d Perform under mentioned test by pressing “AUTO CALL” over the CORE PRIME phone.


Overall Process for SV 120.1 I VoLTE Short Call II FTP-DL III FTP-UL e f 3

Drive test engineer now moves over towards “Beta sector” and performs the following activities during stationary test: a Check PCI b. Assign “Stationary-2” call setting with cycle information & site details c . Perform under mentioned test by pressing “AUTO CALL” over CORE PRIME handset.

e f 4

At the end of “Auto call” press status as “In Progress”. Press “Upload to server” button which is popped up & wait for upload to finish.

i VoLTE Short Call ii FTP-DL iii FTP-UL At the end of Auto call press status as “In Progress”. Press “Auto DRM/DRX Upload” button which is popped up & wait for upload to finish.

Drive test engineer shall move over towards “Gamma sector” and perform the following activities during the stationary test a Check PCI and latch to it. b Assign “Stationary-3” call setting with cycle information & site details c Perform under mentioned test by pressing “AUTO CALL” over CORE PRIME handset.

d e

i VoLTE Short Call ii FTP-DL iii FTP-UL At the end of “Auto call” presses status as “Completed”. Press “Auto DRM/DRX Upload “button which is popped up & wait for upload to finish



 Moving Test: 1

After completion of “Stationary” test now the drive test engineer has to go for the “Moving test”, drive test engineer will use two CORE PRIME/ K-Touch handsets.


Overall Process for SV 120.1 2

There will be two diferent tests (DL,UL) that shall be performed over these handsets. a One handset for DTDL b One handset for DTUL

3

“Moving test” call logging should start by performing a walk test around the site in clockwise and anticlockwise direction for checking the inter-sector handover within the SCVT site and checking the correct PCI as seen in cell reference file.

4

Drive test engineer will carry out the remaining part of moving test while in car in a continuous log. Keep checking the PCI of serving cell so as to confirm handover between neighbors of same site. a Move from Alpha sector to Beta sector to check handover between them. b Move from Beta sector to Gamma sector to check handover between them. c Move from Gamma sector to Alpha sector to check handover between them. d Move from Alpha sector to Gamma sector to check handover between them. e Move from Gamma sector to Beta sector to check handover between them. f Move from Beta sector to Alpha sector to check handover between them. g Make “Coverage footprint” of each sector within the “Best server plot” of the site on all possible drive routes.

5

6 7

Press “Stop” after completion of drive on both handset( based on steps a to g as above) and press status as "Complete” . Press “Auto DRM/DRX Upload” button which gets popped up in both handset & wait for upload to finish. Ask the LSMR engineer to switch of the site. Inform the SOLPAR PM and Samsung area manager about the completion of the drive and move for the next drive if time permits for the day.



This document is proprietary and confidential. No part of this document may be disclosed in any manner to a third party without the prior written consent P a g e | 10


Field engineer will upload the collected log files and close the CLOT task in SiteForge after updating SOLPAR Manager.



For detail process please refer SCVT Pocket Guide.docx.

SCVT Pocket Guide.docx

STEP 3: Post Processing and Report Generation ActixOne Tool is used for generating report after post processing of uploaded log files. After completing drive test field engineer upload log files in Accuver FMS server using DT tools. Accuver FMS server sends log files to Landing zone of ActixOne server. ActixOne Collects log files from landing zone & process the log files. After processing log files ActixOne generate the report. Calculation of KPI is depending upon defined formulae, Cellref file (site data base) and Best server plots.

Accuver DM tool used in UE for DT

Accuver FMS Server

ActixOne Server

ActixOne Client in Web Browser



Snap shots KPI page of SCVT report are shown below.



STEP 4: Validating and Approving SCVT After generating CLOT report ActixOne send report to SiteForge. There are predefined stakeholders to validate and approve SCVT report in SiteForge. Stage 1 of Report Validation and Approval: SAMSUNG National Optimization Team National Optimization Engineer will download the report from SiteForge to validate it. If all KPI are passed and clear all the defined criteria then Optimization Engineer will accept the report and forward it to next step. If report gets fail optimization engineer will reject the report .He/She will try to optimize the site and ask to field team to do re-drive with given suggestion via Samsung RF Lead-Samsung Area Manager-SOLPAR Manager. If all KPI are passed and clear all the defined criteria after re-drive then Optimization Engineer will accept the report and forward it to next step. After re-drive if report fails again then National Optimization engineer will again reject the report and forward the particular case to NEO RF performance team. After receiving suggestions from NEO-RF performance team National Optimization engineer will try to implement the suggestions on the field to optimize the site and ask to field team to do re-drive via Samsung RF Lead-Samsung Area ManagerSOLPAR Manager. SOLPAR Team needs to re-drive till the Site report clear all the defined criteria. For any physical parameter change during optimization SiteForge data should get updated by SOLPAR after implementation at field Types of Changes for SCVT during Optimization: 1) Parameter Changes in LSMR 2) Physical Changes in Field This document is proprietary and confidential. No part of this document may be disclosed in any manner to a third party without the prior written consent P a g e | 14


• • •

 Change Initiators Deployment Optimization Team NEO RF & Performance Team NEO eNB Team

• •

 Change Executor: For LSMR Related Changes: Deployment Integration Team For Physical Attribute Changes: Field Solpar Team. 

LSMR Related Changes: • Initiator should raise “Change Request” to the “Integration Team” as a Jira Ticket • CR must have site list, parameter values & MOP for implementation • Integration team must update the status at least once in 2 days & close the ticket when activity complete



Physical Attribute Changes • Field Solpar team should make changes as per the instruction from circle RF Lead • Revised details to be sent to Siteforge team from RF Optimization Team.

Stage 2 of Report Validation and Approval: SAMSUNG RF Lead As mentioned in above Stage 1 ,If National optimization team accept the SCVT report then this report will get forwarded to RJIL Circle RF lead using Site Forge Tool. If RJIL RF Circle lead reject the SCVT report then Samsung RF lead will forward it to National optimization team to repeat Stage 1. Similarly if National optimization team reject the CLOT report then RF lead will forward the optimization suggestions given by optimization team to Area manager, So that Area manager will ask SOLPAR manager to implement the suggestions on field & repeat step 1. Stage 3 of Report Validation and Approval: RJIL Circle RF Lead As mentioned in Stage2, after SCVT report accepted by National optimization team, Samsung Circle RF lead will forward the report to RJIL Circle RF lead by accepting it in SiteForge. Once RJIL circle RF lead will receive the report, He/She will download the report and review/validate it. If RJIL circle RF lead finds report clear all the necessary criteria then he /She will accept the Report for further validation, else he/she will reject the report for further optimization of site. If RJIL RF lead rejects the report then rejected report gets trigger to Samsung RF lead to repeat the stage 2. If RJIL Circle CTO/ RJIL central RF team rejects the report then also it is RJIL circle RF Lead duty to revalidate the report. Stage 4 of Report Validation and Approval: RJIL Circle CTO As mentioned in stage 3, after SCVT report accepted by RJIL Circle RF lead, SiteForge will forward the report to RJIL Circle CTO. This document is proprietary and confidential. No part of this document may be disclosed in any manner to a third party without the prior written consent P a g e | 15

Overall Process for SV 120.1 If RJIL circle CTO finds report clear all the necessary criteria then he /She will accept the Report for further validation, else reject the report which will get trigger to RJIL Circle RF lead to repeat stage 3.

Stage 5 of Report Validation and Approval: RJIL central RF Team If RJIL Central RF Team find report clear all the necessary criteria then they will accept the Report for task closure, else reject the report which will get trigger to RJIL Circle RF lead to repeat stage 3.

Stage 6 of Report Validation and Approval: RJIL RANCORE Team If RANCORE RF Team find report clear all the necessary criteria then they will accept the Report for task closure, else reject the report which will get trigger to RJIL Circle RF lead to repeat stage 3. After Completing all the approval Samsung Area manager will close SCVT task in SiteForge to declare completion of CLOT.

--------------------------------------------------------------------END OF DOCUMENT--------------------------------------------------------------------------------


Overall Process for SCVT_SV120.1.docx

Recommend Documents