IRAT Neighbor List Optimization Procedure
Copyright 2016 TEOCO Corporation - All rights reserved. No part of this work, which is protected by copyright, may be reproduced in any form or by any means - graphic, electronic or mechanical, including photocopying, recording, recording, taping or storage in an information retrieval system - without the written permission of the copyright owner.
Mobifone – IRAT NL Optimization
Contents 1
IRAT Neighbor List Plan Procedure ..................................................................................................3
Page 2 of 9
Mobifone – IRAT NL Optimization
1
IRAT Neighbor List Plan Procedure
Objective: To optimize UMTS-GSM neighbors in the network
Technology Vendor Specific Recommendation/s
UMTS
Pre-requisite
Include GSM in Network Import, Fix UMTS-GSM discrepancy, UMTS/GSM Measurement Plan
Output Pre-Optimization Assessment Post-Optimization Assessment
NL Plan Report,
No IRAT Neighbor List Optimization
7 days 7 days
Include GSM during Network Import
In the toolbar, click on Network Open Network Reports. Then open UMTS-GSM discrepancy report
Page 3 of 9
Mobifone – IRAT NL Optimization
To Fix UMTS-GSM Discrepancies, click on Tools Resolve UMTS/GSM Discrepancies
Sample Huawei UMTS/GSM correction by Ultima Mentor
Recollect CM file and repeat Step 1
Page 4 of 9
Mobifone – IRAT NL Optimization
Create UMTS/GSM Measurement Plan. Click Tools UMTS/GSM Measurement Plan
Set desired Parameters such as Max Neighbors, Number of Days, GSM Band, Output Directory
Daily Implementation of UMTS/GSM Measurement Plan scripts in OSS
Sample UMTS/GSM Measurement Plan files/scripts
Data collection (CM, Logs and KPIs) and model creation for measurement plan days
Page 5 of 9
Mobifone – IRAT NL Optimization
Import Network with latest model
Ensure that you have a model for the environment.
Select Sectors to Optimize
From an excel file, Ctrl+Alt+C on sectors to optimize. Then Ctrl+Alt+V in Mentor
Run Optimization Neighbor List Plan.
Page 6 of 9
Mobifone – IRAT NL Optimization
In the wizard window, select: Sector Type Network sectors = Active Neighbor List Type = UMTS/GSM
Click Next and then Finish. In the Calculations pane, right-click the IRAT NL Plan and open report
Open Neighbor List Report
In the Calculations pane, right-click the IRAT NL Plan and click Export Plan to create implementation scripts
Page 7 of 9
Mobifone – IRAT NL Optimization
Define output directory for implementation scripts
Page 8 of 9
Mobifone – IRAT NL Optimization
Additional Notes:
1.
UMTS/GSM Inconsistencies
When building a 2G/3G network in Mentor, a UMTS-GSM discrepancy report will be created. This report should be analyzed carefully for: BCCH/BSIC inconsistencies between GSM and UMTS OSS. As GSM sector are defined as external on the UMTS OSS, their BCCH/BSIC may not have been updated during GSM retune. Those warnings should be corrected immediately.
LAC/CI inconsistencies between GSM and UMTS OSS. A few possibilities: As GSM sector are defined as external on the UMTS OSS, their LAC/CI ma y not have been updated during GSM BSC re-homes. Verify if that LAC/CI combination actually exist in GSM network o
You may not have included the entire GSM SD for the area. A GSM BSS/OSS/Other vendor SD may be missing in your network. Recover that information and rebuild env. This happens at border between vendors o
A GSM sector may exist in GSM OSS but was not included in your environment. It was missing from your GSM coordinates file. o
Build the GSM environment in Forte and look for sectors missing coordinates. Add them to your coordinate file and rebuild env in Mentor (submit to server if server is used)
If not, use the GSM Import detail report (when building env from Configuration file, not from server) to find those sector missing coordinates. Add them to your coordinate file and rebuild env in Mentor (submit to server if server is used)
Those inconsistencies will reduce your ability to optimize the NL as unknown neighbors will not be touched. They will also prevent those handover to occur. It is recommended to fix them if possible, but it is not a show-stopper and Mentor will optimize the network around them.
2.
Reasons for UMTS/GSM Measurement Plan a. b. c. d. e.
Missing neighbors will not be reported by the Ue The Ue will only measure (during compressed mode) the existing BCCH of GSM neighbors and report only the existing BCCH/BSIC of GSM neighbors Any other BCCH will not be scanned and therefore not reported Any other BCCH/BSIC will be discarded and not reported even when measured Only way to find a missing neighbor is to create it and measure of it actually has any HO count (Trial and error process)
Page 9 of 9
