Ultima Forté Required Data Inputs For Huawei Infrastructure

Ultima - Fort Required Data Inputs for Huawei Infrastructure
Ultima Fort
Required Data Inputs for Huawei Infrastructure (for Version 4.0 and above)
Copyright Notice
Due to a policy of continuous product development and refinement, Schema reserves the right to alter the specifications and descriptions outlined in this publication without giving prior notice of any kind. In addition, no part of this publication, taken as a whole or separately, shall be deemed to be part of any contract for equipment or services. Schema retains the sole proprietary rights to all information contained in this document. No part of this publication may be reproduced, stored in a retrieval system, transmitted in any form or by any means, including but not limited to: electronic, mechanical, magnetic, photocopy, recording, or otherwise, in use now or in the future, without prior written consent from Schema.
Copyright 2008 Schema
Schema Confidential & Proprietary
June 2008
Page 1 of 87
Table of Contents
1 2 Introduction.............................................................................................. 6 Required Information and Data................................................................. 7
2.1 2.2 Optimization Area ...........................................................................................7 Network Data.................................................................................................7 2.2.1 Huawei BSS Network Configuration .........................................................7 2.2.2 Sector Coordinates File ........................................................................ 19 2.3 Mobile Statistics Data Recordings.................................................................... 20 2.3.1 Addition and Deletion of New Neighbors ................................................. 20 2.3.2 Activation of Recordings (R002 and R007).............................................. 33 2.4 Retrieving Mobile Statistics Results ................................................................. 37 2.4.1 iManager Retrieval for Versions R002 and R007 ...................................... 37 2.4.2 MS Retrieval for S6000 ........................................................................ 39 2.5 2.6 2.7 Traffic File ................................................................................................... 59 Handover Statistics ....................................................................................... 59 Network Performance Statistics ...................................................................... 59 2.7.1 Network Performance Evaluation........................................................... 60 2.7.2 Radio Network Performance KPIs Calculation .......................................... 61 2.7.3 Additional KPIs for Network Performance Evaluation ................................ 62
Data Collection Checklist......................................................................... 64
Appendix A.................................................................................................... 65 Appendix B .................................................................................................... 72 Appendix C: ................................................................................................... 80
June 2008
Page 2 of 87
Table of Figures
Figure 1: BSC6000 Local Maintenance Terminal .................................................................9 Figure 2: Login Dialog Box............................................................................................ 10 Figure 3: Configuration-Browse Configuration Data .......................................................... 10 Figure 4: Select Dialog Box........................................................................................... 11 Figure 5: Browse Cell Data ........................................................................................... 12 Figure 6: Browse TRX and Channel Data ......................................................................... 13 Figure 7: Browse Other Data......................................................................................... 14 Figure 8: Launch all Tables ........................................................................................... 15 Figure 9: Cell Channel Management Data Table ............................................................... 16 Figure 10: Save As Dialog Box ...................................................................................... 17 Figure 11: Other Cell Attributes Table ............................................................................ 18 Figure 12: Data Auto Configuration System..................................................................... 21 Figure 13: Data Auto Configuration ................................................................................ 21 Figure 14: Export Network Parameters ........................................................................... 22 Figure 15: Export Network Parameter ............................................................................ 22 Figure 16: Save Export File as Text File .......................................................................... 23 Figure 17: Import Network Parameters........................................................................... 23 Figure 18: Upload Recently Generated File ...................................................................... 24 Figure 19: Confirmation Dialog Box................................................................................ 24 Figure 20: Export Network Plan Parameter...................................................................... 25 Figure 21: Choose the Export Type ................................................................................ 26 Figure 22: Choose the Export Object .............................................................................. 27 Figure 23: Save As Dialog Box ...................................................................................... 28 Figure 24: Import Network Plan Parameter Menu ............................................................. 29 Figure 25: Import Network Plan Parameter Dialog Box...................................................... 30 Figure 26: Selection of HandoversTable.txt File................................................................ 31 Figure 27: Select a File to be Imported........................................................................... 32 Figure 28: Select Traffic Measurement............................................................................ 33 Figure 29: Select New Task .......................................................................................... 34 Figure 30: New Task Registration .................................................................................. 34 Figure 31: Definition of Data Set to Handle Task .............................................................. 35 Figure 32: BSC Cell Selection ........................................................................................ 36
June 2008
Page 3 of 87
Figure 33: Registration of All Statistical Items ................................................................. 36 Figure 34: iManager Service Menu ................................................................................. 37 Figure 35: Performance Query Result ............................................................................. 39 Figure 36: Query Result Display .................................................................................... 40 Figure 37: Network Object Settings ............................................................................... 41 Figure 38: Object Selections ......................................................................................... 42 Figure 39: Available Counters ....................................................................................... 43 Figure 40: Selected Counters ........................................................................................ 43 Figure 41: Neighbor Cell Measurement Per Cell................................................................ 44 Figure 42: Export Query Results .................................................................................... 45 Figure 43: Saving Files................................................................................................. 46 Figure 44: Saving Files in *.csv Format .......................................................................... 47 Figure 45: Query Result Object Settings ......................................................................... 48 Figure 46: Filter By Status ............................................................................................ 49 Figure 47: Available Counters to Selected Counters.......................................................... 50 Figure 48: Setting Start Time and End Time .................................................................... 51 Figure 49: Query Export ............................................................................................... 52 Figure 50: Saving *.csv Files ........................................................................................ 53 Figure 51: Condition Button .......................................................................................... 54 Figure 52: Available Counters to Selected Counters.......................................................... 56 Figure 53: Setting Start Time and End Time .................................................................... 56 Figure 54: Query Export ............................................................................................... 57 Figure 55: *.csv File Selection....................................................................................... 58 Figure 56: Query Result Window.................................................................................... 65 Figure 57: Object Settings - All BSCs ............................................................................. 66 Figure 58: BSC - Filter by Status ................................................................................... 66 Figure 59: Addition of Counters to Selected Counters Area ................................................ 68 Figure 60: Query for K3003 Successful SDCCH Seizures ................................................... 69 Figure 61: Query Export ............................................................................................... 70 Figure 62: Selection of *.csv Files.................................................................................. 71 Figure 63: Export Network Plan Parameter Menu ............................................................. 72 Figure 64: Choose Export Type...................................................................................... 73 Figure 65: Choose Export Object ................................................................................... 74
June 2008
Page 4 of 87
Figure 66: Save As Dialog Box ...................................................................................... 75 Figure 67: Import Network Plan Parameter Menu ............................................................. 76 Figure 68: Import Network Plan Parameter Dialog Box...................................................... 77 Figure 69: Open FrequencyTable.txt File ......................................................................... 78 Figure 70: Selection of File to Import ............................................................................. 79 Figure 71: Export Network Plan Parameter Menu ............................................................. 80 Figure 72: Choose Export Type...................................................................................... 81 Figure 73: Choose Export Object ................................................................................... 82 Figure 74: Save As Dialog Box ...................................................................................... 83 Figure 75: Import Network Plan Parameter Menu ............................................................. 84 Figure 76: Import Network Plan Parameter Dialog Box...................................................... 85 Figure 77: Opening 2G External Cell.txt File .................................................................... 86 Figure 78: Selection of File to Import ............................................................................. 87
June 2008
Page 5 of 87
Introduction
This document lists the information and data to be collected in order to optimize Huawei GSM infrastructures, using Ultima Fort. In general, the following information is required: Optimization area and optimization goals Huawei BSS network configuration data Sector coordinate data Mobile measurement recordings Performance reports
This document not only identifies the required data sources, but also explains how to obtain that data.
June 2008
Page 6 of 87
Ultima Fort Required Data Inputs for Huawei Infrastructure
2
2.1

Required Information and Data

Optimization Area
The following information is required to analyze a network: List of cells in the optimization and surrounding areas (optimization set and guard zone) Available spectrum for all bands List of frequencies to be used as BCCH channels List of frequencies to be used as TCH channels Current frequency planning strategy (BB,1:1, 1:2, , per site, per cell, ad-hoc, ) Desired optimization strategy (BB, 1:1, 1:2, , per site, per cell, ad-hoc, )
2.2
2.2.1
Network Data
Huawei BSS Network Configuration
2.2.1.1 Huawei BSS Naming Convention

Huawei currently uses G3BSC32 and S6000 BSC hardware, each with several associated software versions. Each BSS software release also includes several versions and releases (ranging from R001 to R007 for G3BSC32 BSC). For example, G3BSC32 with software Version V300 and Release R007 is associated with: G3BSC32V300R007ENGC01 (English Correction package 01) G3BSC32V300R007CHNC01 (Chinese Correction package 01)
BSC S6000 software version (V900) and release (R001, R003, and so on) has the following corrections and patches:
June 2008
Page 7 of 87
BSC6000V900R001C01: BSC hardware Version 6000 with BSS software Version V900, Release R001. BSC6000V900R001C03B104SP10: BSC hardware Version 6000 with BSS software Version V900, Release R001, correction C03B104 and patch SP10. Upgraded to BSC6000V900R001C03B104SP12: BSC hardware Version 6000 with BSS software Version V900, Release R001, correction C03B104 and patch SP12.
The above packages are referred to as R002, R007, and S6000.
2.2.1.2 Release R002 and Release R007

The BSS network configuration dump can be retrieved via a supported remote program (e.g., Remote Administrator) to each relevant BSC, with a copy of the DBF directory. The full path is C:/OMC/BSC/BAM/dbf. All available DBF files should be retrieved per BSC.
2.2.1.3 BSC Hardware Release S6000

To export the configuration data table for each BSC, log on to the BSC Local Maintenance Terminal (LMT) from the Main Topology window as follows: 1. From the Management Tree tab on the left window, right click on the BSC (e.g., BSC248) and select Maintenance Client to launch the BSC6000 Local Maintenance Terminal shown in Figure 1.
June 2008
Page 8 of 87
Figure 1: BSC6000 Local Maintenance Terminal 2. Fill in a login Name, Password, and BSC Name/IP in the appropriate places in the Login dialog box shown in Figure 2.
June 2008
Page 9 of 87
Figure 2: Login Dialog Box 3. From the BSC6000 Local Maintenance Terminal, select ConfigurationBrowse Configuration Data, as shown in Figure 3.
Figure 3: Configuration-Browse Configuration Data
June 2008
Page 10 of 87
4. Select a specific configuration from the Select dialog box, shown in Figure 4.
Figure 4: Select Dialog Box
5. In the All Data area of the Select dialog box, select the Browse Site Common Data sub-entry from the Browse Site Data entry. 6. Click the > button to add Browse Site Common Data to the Data to be shown area of the Select dialog box. 7. Click OK.
June 2008
Page 11 of 87
8. In the All Data area, click on Browse Cell Data and select the following sub-entries.
Figure 5: Browse Cell Data Browse Cell Common Data Browse Cell Handover Data Browse Cell Power Control Data Browse Cell Channel Management Data Browse Other Cell Attributes Browse Cell FH Data Browse 2G Adjacent Relations Data Browse 3G Adjacent Relations Data (only if there are 3G sites) Browse 2G External Cell Data Browse 3G External Cell Data (only if there are 3G sites)
9. Click the > button to add these sub-entries to the Data to be shown area. 10. Click OK.
June 2008
Page 12 of 87
11. In the All Data area, click on Browse TRX & Channel Data, and select the Browse TRX Data and Browse Channel Data sub-entries.
Figure 6: Browse TRX and Channel Data 12. Click the > button to add these sub-entries to the Data to be shown area. 13. Click OK.
June 2008
Page 13 of 87
14. In the All Data area, select Browse Other Data, then select the Browse Cell Frequency Data and Browse TRX Frequency Data sub-entries.
Figure 7: Browse Other Data 15. Click the > button to add these sub-entries to the Data to be shown area. 16. Click OK.
June 2008
Page 14 of 87
All of the tables are launched.
Figure 8: Launch all Tables
June 2008
Page 15 of 87
17. Click on one of the tables (e.g., Cell Channel Management Data) to open it.
Figure 9: Cell Channel Management Data Table 18. Right click on the table, and then click on Export to save the table.
June 2008
Page 16 of 87
A Save As dialog box is displayed.
Figure 10: Save As Dialog Box 19. Navigate to the selected folders and click Save to save the file name as the same name of the open table (e.g., Site Common Data, which can only be saved in *.xls format).
June 2008
Page 17 of 87
20. Repeat this procedure for all other launched tables (Steps 15 17) (e.g., Other Cell Attributes).
Figure 11: Other Cell Attributes Table
21. Manually convert all of the configuration table files to *.csv format for use in Fort. 22. Repeat Steps 1-21 for each BSC, required to create the environment.
June 2008
Page 18 of 87
2.2.2
Sector Coordinates File
The sector coordinates file should be in tab-delimited text file format, and include geographical information for all of the network sectors, including the following columns: Sector Latitude Longitude Azimuth LAC (optional) CI (optional) Keywords (optional)
The latitude and longitude values should be expressed in decimal-degree format, with up to six digits following the decimal point.
June 2008
Page 19 of 87
2.3

Mobile Statistics Data Recordings
The following network activities should stop while data is being recorded: BSC split Site re-homing (BSC/site relations change) Changes of LAC and CI Sector mechanical changes, such as tilt, azimuth, and antenna changes Frequency changes (BCCH and BSIC) Neighbor additions or deletions
The following changes should be performed only during maintenance (not during recording): TRX additions Frequency changes (TCH) Site additions
No other parameters should be changed. The Defined Adjacent Cell and Undefined Adjacent Cell measurements collect signal strength information of potential interferers, reported by the mobiles in the Mobile Measurement Reports (MMR), for Versions R002 and R007. Neighbor Measurements contains a full C/I data report for Version S6000. To collect information for BCCH channels that do not belong to the adjacent cell list (BCCHs not used by existing neighbors), a new BCCH allocation list (BA2 active BA list) should be defined to contain all BCCHs to be measured. This BA list should be assigned to each sector by creating fake neighbors for each cell with missing BCCH channels. The Ultima Forte Measurement Plan functionality should be used to collect reliable data for network modeling. This functionality allocates BCCH frequencies to the active BA list for each sector. Missing BCCH frequencies will be defined by adding new neighbor relations for each sector.
2.3.1
Addition and Deletion of New Neighbors
2.3.1.1 Versions R002 and R007

1. Select the BSC in the Network Management System (NMS) network tree. 2. Select System Dynamic Configuration.
June 2008
Page 20 of 87
Figure 12: Data Auto Configuration System
Figure 13: Data Auto Configuration
3.
Select Export Network Parameters.
June 2008
Page 21 of 87
Figure 14: Export Network Parameters
4. Select Export Adjacent Relationship of Cells. 5. Select All cells. 6. Select Export Parameter.
Figure 15: Export Network Parameter
June 2008
Page 22 of 87
7. Save the export file as a text file.
Figure 16: Save Export File as Text File
Based on the provided export data file, Fort generates a file with a new neighbor list (including newly added neighbor relations) for measurement purposes. The handoversTable.txt should be named and placed in the network configuration directory with the other *.dbf files. This file (one for each measured BSC) should be uploaded to the BSC every day during maintenance as follows: 1. Select Import Network Parameters.
Figure 17: Import Network Parameters
June 2008
Page 23 of 87
2. Select and load the recently generated file (with updated neighbor relations).
Figure 18: Upload Recently Generated File
3. Confirm the single adjacent relationship of all BSC cells after the upload.
Figure 19: Confirmation Dialog Box
June 2008
Page 24 of 87
2.3.1.2 Process for S6000:
2.3.1.2.1 Export HandoversTable

To export a sample HandoversTable.txt from S6000: 1. Login to the local BSCs BSC6000 Local Maintenance Terminal. 2. Select ConfigurationImport or Export DataExport Network Plan Parameter.
Figure 20: Export Network Plan Parameter
June 2008
Page 25 of 87
The Export Network Plan Parameter dialog box, with Choose the export type displayed.
Figure 21: Choose the Export Type 3. Click on Export adjacent cells, and then click Next>> to launch the Choose the export object step.
June 2008
Page 26 of 87
Figure 22: Choose the Export Object 4. Select the cells from the Object Tree area on the left, and then click > to add them to the Selected Object List area on the right. 5. Click the Export button.
June 2008
Page 27 of 87
The Save As dialog box is displayed.
Figure 23: Save As Dialog Box
6. Navigate to the selected folder and type HandoversTable in the File name field. 7. Click Save to save the adjacent cells table (only in *.txt format). 8. Repeat Steps 1-8 for each BSC (optimization set and buffer zone sectors) required to generate the MP script.
2.3.1.2.2 Import HandoversTable

To import HandoversTable.txt to S6000:
June 2008
Page 28 of 87
1. Choose ConfigurationImport or Export DataImport Network Plan Parameter.
Figure 24: Import Network Plan Parameter Menu
June 2008
Page 29 of 87
The Import Network Plan Parameter dialog box is displayed.
Figure 25: Import Network Plan Parameter Dialog Box
June 2008
Page 30 of 87
2. Click the button and select the folder containing the HandoversTable.txt file. 3. Click Open.
Figure 26: Selection of HandoversTable.txt File
June 2008
Page 31 of 87
Figure 27: Select a File to be Imported
4. Click Finish. 5. Repeat Steps 1-5 for each BSC (optimization set and buffer zone sectors) required to generate the MP script.
Note: The HandoversTable.txt file should only contain sectors with fake neighbors added by Ultima Fort; the original neighbors need not be in this file. Also, if the HandoversTable.txt file is longer than 5000 lines it can be split into multiple files (preferably 3000 lines per file). This largely depends on the computers memory capacity. The file must be split if the BSC6000 LMT fails to import, and sends File too large error messages. However, if the file is split into multiple files, fake neighbors belonging to the same sectors of the same site must remain within the same file.
June 2008
Page 32 of 87
2.3.2
Activation of Recordings (R002 and R007)
Note: While no specific recording activation is required for S6000, the operator should confirm that the MR measurements (Neighbor Cell Level Measurement per Cell and TCHF/H Receive Level Measurement per TRX) are available for query. In order to collect required data for network modeling, the Defined Adjacent Cell (DAC), Undefined Adjacent Cell (UAC) and Receiving Level Measurement Function (RLMF) network statistics should be activated for all sectors (Neighbor Measurements and RLMF for S6000). The Rate and Level limits for DAC and UAC statistics should be defined as 0 in order to avoid data filtering based either on the number of samples (Rate) or on the Signal Strength (Level). To activate required BSC level statistical functionalities: 1. Select the BSC. 2. Select Traffic Measurement.
Figure 28: Select Traffic Measurement
3. Select Task > New.
June 2008
Page 33 of 87
Figure 29: Select New Task
4. Register the new task with all available parameters.
Figure 30: New Task Registration
June 2008
Page 34 of 87
5. Define the data set required to handle the task.
Figure 31: Definition of Data Set to Handle Task 6. Select all the cells of the measured BSC.
June 2008
Page 35 of 87
Figure 32: BSC Cell Selection
7. Follow the above steps to register the Defined Adjacent Cell statistics.
Figure 33: Registration of All Statistical Items
June 2008
Page 36 of 87
8. Follow the above steps to register the RLMF, FR, and HR statistics. 9. Retrieve network configuration files for each day of Mobile Statistics recording.
2.4
Retrieving Mobile Statistics Results
Use the Huawei generic format for all relevant sectors to retrieve all statistics for every day at the same time. RLMF statistics should be provided for both FR and HR traffic. For versions R002 and R007, four daily files should be generated for data required for every statistical type (DAC, UAC, RLMF, FR, RLMF, and HR). For version S6000, five daily files should be generated for data required for every statistical type (Neighbors Measurements, RLMF FR (0-4), RLMF FR (5-7), RLMF HR (0-4), and RLMF HR (5-7)). Currently, Versions R002 and R007 of iManager correctly generate only RLMF data. DAC and UAC data should be retrieved separately. After Huawei updates these versions, iManager will also be able to retrieve DAC and UAC statistics.
2.4.1
iManager Retrieval for Versions R002 and R007
1. Log on to iManager. 2. Select the relevant BSC. 3. Click on ServicePerformance.
Figure 34: iManager Service Menu
June 2008
Page 37 of 87
4. Select a measurement task to export the results of RLMF (DAC, UAC). 5. Click F7 or right click on an item, and then select Query Result. 6. All boxes under the Basic Settings tab should be marked for both RLMF and DAC recordings. 7. Select the Specified Time Segment radio button under Time Range > Filter Settings. 8. Set the appropriate values, and then click OK. 9. When a table is displayed with all task results, right click on one of the fields, and then click on Save AsExcel File. 10. Specify the desired location and file name. To retrieve data via BAM: 1. Select the appropriate task, and click on Statistic Result. 2. Define the results time period. 3. Right click the table, and then click on Save to file or click the Save To button.
June 2008
Page 38 of 87
2.4.2
MS Retrieval for S6000
1. From the iManager M2000 window, click on the Performance drop down menu and select the Query Result to launch the Query Result window as shown below:
Figure 35: Performance Query Result
June 2008
Page 39 of 87
Figure 36: Query Result Display
June 2008
Page 40 of 87
Neighbor Cell Level Measurement per Cell retrieval:

1. Click on MR Measurement and then select the Neighbor Cell Level Measurement per Cell on the left side of the window. 2. On the Object Settings tab, click on Network to show all BSCs.
Figure 37: Network Object Settings
June 2008
Page 41 of 87
3. Select the BSCs that are scheduled for retrieval of mobile statistics measurements. 4. Click the > button to add the measurements to the Selected Objects area.
Figure 38: Object Selections 5. Click on Counter Settings > System Counter to show all counters. 6. Select all counters and click the > button to add the selected counters to the Selected Counters area.
June 2008
Page 42 of 87
Figure 39: Available Counters
Figure 40: Selected Counters
June 2008
Page 43 of 87
7. On the Other Settings tab, select the appropriate settings, and then set the Start Time and End Time for queries. 8. Click the Query button to start the query for Neighbor Cell Level Measurement per Cell.
Figure 41: Neighbor Cell Measurement Per Cell
June 2008
Page 44 of 87
The Neighbor Cell Level Measurement per Cell query result is displayed. 9. Right click on the query result and select Export All
Figure 42: Export Query Results
June 2008
Page 45 of 87
10. When the Save window appears, click on the File Type drop down menu, and select CSV Files (*.csv)
Figure 43: Saving Files
June 2008
Page 46 of 87
11. Navigate to the selected folders, and type Neighbor Cell Measurement per Cell on the File Name field. 12. Click Save to save the file in *.csv format.
Figure 44: Saving Files in *.csv Format
13. Repeat the Neighbor Cell Level Measurement per Cell retrieval process for each BSC (optimization set and buffer zone sectors) within the MP script scheduled to collect mobile statistics (MS).
June 2008
Page 47 of 87
TCHF/H Receive Level Measurement per TRX (RLMF FR/RLMF HR) retrieval:
1. Click on MR Measurement > TCHH Receive Level Measurement per TRX on the left side of the window. 2. Click on Object Settings tab > Network to show all of the BSCs.
Figure 45: Query Result Object Settings
June 2008
Page 48 of 87
3. Select the BSCs that are scheduled to retrieve mobile statistics measurements. 4. Click the > button to add the measurements to the Selected Objects area.
Figure 46: Filter By Status
June 2008
Page 49 of 87
5. From the Counter Settings tab, click on System Counters to show all of the available counters. 6. Select S4100C counter - S4147D counter and click > button to add the counters to the Selected Counters area.
Figure 47: Available Counters to Selected Counters
June 2008
Page 50 of 87
7. On the Other Settings tab, select the appropriate settings, and then set the Start Time and End Time for queries. 8. Click Query to start the query for TCHH Receive Level Measurement per TRX (RLMF_HR(0-4)).
Figure 48: Setting Start Time and End Time
June 2008
Page 51 of 87
The result of the TCHH Receive Level Measurement per TRX query is posted. 9. Right click on the query result and select Export All
Figure 49: Query Export
June 2008
Page 52 of 87
10. When the Save window appears, click on the File Type drop down menu, and select CSV Files (*.csv).
Figure 50: Saving *.csv Files
11. Navigate to the selected folders and type RLMF_HR(0-4) in the File Name field. 12. Click Save to save the file in *.csv format.
June 2008
Page 53 of 87
13. Click on the Condition button to re-launch the Query Result window.
Figure 51: Condition Button
June 2008
Page 54 of 87
14. Click on Counter Settings > System Counters to show all available counters. 15. Select S4150C counter - S4177D counter and click the > button to add the counters to the Selected Counters area.
June 2008
Page 55 of 87
Figure 52: Available Counters to Selected Counters 16. On the Other Settings tab, select the appropriate settings, and then set the Start Time and End Time for queries. 17. Click Query to start the query for TCHH Receive Level Measurement per TRX (RLMF_HR(5-7)).
Figure 53: Setting Start Time and End Time
June 2008
Page 56 of 87
18. The result of the TCHH Receive Level Measurement per TRX query is displayed. 19. Right click on the query result, and select Export All
June 2008
Page 57 of 87
20. When the Save window appears, click on the File Type drop down menu and select CSV Files (*.csv).
Figure 55: *.csv File Selection 21. Navigate to the selected folders and type RLMF_HR(5-7) on the File Name field. 22. Click Save to save the file in *.csv format. 23. Repeat Steps 1-22 for the TCHF Receive Level Measurement per TRX report. 24. Repeat the TCHF/H Receive Level Measurement per TRX (RLMF_FR/RLMF_HR) retrieval process for each BSC (optimization set and buffer zone sectors) in the MP script scheduled for collection of mobile statistics (MS).
June 2008
Page 58 of 87
RLMF_FR(0-4) - S4100A - S4147B RLMF_FR(5-7) - S4150A - S4177B RLMF_HR(0-4) - S4100C - S4147D RLMF_HR(5-7) - S4150C - S4177D
2.5
Traffic File
The traffic file should be in tab-delimited text file format, with traffic information for all sectors in the optimization and simulation areas (the guard-zone area), and should include the following columns: Sector Traffic (carried traffic in Erlangs) AMR penetration (optional)
Since the Traffic file complies with Schema format, these columns can be in any order. The Traffic file should contain information for five consecutive working days in a three- to fourhour period that includes the network peak hour, and should be generated on the last recording day.
2.6
Handover Statistics
Handover statistics for each cell-to-cell relation should be collected for handover optimization. This data should be aggregated over one week for each cell-to-cell relation, and provided in a tab-delimited text file with the following fields: Serving Sector Target Sector Handover Attempts
Counter H371: Cell Outgoing Handover Commands should be used, as it aggregates the number of outgoing HO attempts per adjacency. Appendix A describes how to query this H371 counter for Handover Attempts statistics retrieval.
2.7
Network Performance Statistics
Network performance statistics should be collected for network traffic modeling and postoptimization network performance benchmarking.
June 2008
Page 59 of 87
The following network performance statistics should be collected per cell, and calculated hourly over seven consecutive days: SDCCH Assignments (immediate assignment attempts, successes, and failures): o Attempted SDCCH Seizures (all), successful SDCCH seizures (all), SDCCH Seizures failures, attempted SDCCH seizures meeting SDCCH overflow. Sum of SDCCH measurement reports in the cell. SDCCH Call Drop, SDCCH lost radio connections (connection failure), SDCCH lost radio connections (error indicator). Attempted TCH seizures (all), attempted TCH seizures for call, successful TCH seizures (all), successful TCH seizures for call, attempted TCH seizures meeting TCH overflow. Sum of TCH measurement reports in 1800 cell (excl. very early assignment), sum of TCH measurement reports in the cell (excl. very early assignment) TCH Call Drop, TCH lost radio connections (connection failure), TCH lost radio connections (error indicator).
SDCCH Traffic: o SDCCH Performance (drop, drop reason): o
TCH Assignments (TCH assignment attempts and failures): o
TCH Traffic: o
TCH Performance (drop, drop reason): o
The following performance statistics should be collected and calculated daily for each cell relation, for seven consecutive days,: HO Performance (cell relation): o Attempted outgoing inter cell handover, successful outgoing inter cell handover, unsuccessful outgoing cell handover with successful reversion, unsuccessful outgoing cell handover with unsuccessful reversion. Attempted outgoing internal inter cell handovers, attempted outgoing inter BSC intercell handovers, attempted handovers for uplink quality, attempted handovers for downlink quality, successful outgoing internal inter cell handovers, successful outgoing inter BSC inter cell handovers.
HO Performance (cell): o
2.7.1
Network Performance Evaluation
Each KPI improvement rate will be calculated as follows:
June 2008
Page 60 of 87
KPI _ improvement _ rate =
KPI before KPI new KPI before
100%
The Success Rate KPIs (SDCCH/TCH Setup, HO) improvement will be calculated as follows:
KPI _ Success _ improvement _ rate =
KPI new KPI before 100 KPI before
100% 100%
Erlang _ to _ Drop _ improvement _ rate =
KPI new KPI before KPI before
Each KPI improvement ratio can be calculated separately over a period of five working days (during each days network busy hour), before and after the optimization cycle. Any network performance KPIs that are not related to the BSS subsystem should be excluded from the calculation.
2.7.2
Radio Network Performance KPIs Calculation
The following calculations will be used for KPIs proposed for Radio Network performance evaluation:
SDCCH _ Drop _ Rate _ Radio =
SDCCH lost radio connections (connection failure) + SDCCH lost radio connections (error indicator )
(Successful SDCCH seizures (all)) Successful TCH seizures (all)
TCH _ Drop _ Rate _ Radio =
TCH lost radio connections (connection failure) + TCH lost radio connections (error indicator )
Call _ Drop _ Rate _ Radio =
TCH lost radio connections (connection failure) + TCH lost radio connections (error indicator )
Successful TCH seizures for call
June 2008
Page 61 of 87
Erlang _ to _ Drop _ Radio =
Sum of TCH measurement reports in the cell (excl. very early assignment)
Sum of TCH measurement reports in 1800 cell (excl. very early assignment) + TCH lost radio connections (connection failure) + 7500 TCH lost radio connections (error indicator )
TCH _ Bad _ Quality _ DL =
RLMF RLMF
x =0 7 x =5 7
DL
DL
TCH _ Bad _ Quality _ UL =
RLMF RLMF
x =0 x =5 7
UL
UL
Outgoing _ HO _ Success _ Rate =
Successful outgoing inter BSC inter cell handovers

Attempted outgoing internal inter cell handovers + Attempted outgoing inter BSC inter cell handovers
Successful outgoing internal inter cell handovers +
Note: The calculations mentioned above do not include drops that may occur due to BSS problems, such as transmission, BSC, TRAU, or MSC. Bad Quality statistics will be retrieved from RMS data directly.
2.7.3
Additional KPIs for Network Performance Evaluation
The following calculations provide additional KPIs for network performance evaluation:
SDCCH _ Assignment _ Success =
Successful SDCCH seizures (all) Attempted SDCCH Seizures (all) SDCCH Call Drop
SDCCH _ Drop _ Rate =
Successful SDCCH seizures (all)
SDCCH _ Block _ Rate =
Attempted SDCCH seizures meeting SDCCH overflow Successful SDCCH seizures (all)
June 2008
Page 62 of 87
TCH _ Assignment _ Success =
Successful TCH seizures (all) Attempted TCH seizures (all) TCH call drop
TCH _ Drop _ Rate =
Successful TCH seizures (all)
TCH _ Block _ Rate =
Attempted TCH seizures meeting TCH overflow Attempted TCH seizures (all) TCH call drop Call _ Drop _ Rate = Successful TCH seizures for call
Erlang _ to _ Drop =
Sum of TCH measurement reports in 1800 cell (excl. very early assignment) + 7500 TCH call drop
SDCCH _ Traffic =
Sum of SDCCH measurement reports in the cell

7660
TCH _ Traffic =
Sum of TCH measurement reports in 1800 cell (excl. very early assignment) + 7500
TCH _ Traffic _ FR = TCH _ Traffic _ HR = HO _ DL _ Qual _ Cause =
RLMF
DL
_ FR
7500
RLMF
DL
_ HR
7500
Attempted outgoing inter BSC inter cell handovers

Attempted outgoing internal inter cell handovers +
Attempted handovers for downlink quality Attempted handovers for uplink quality
HO _ UL _ Qual _ Cause =
Attempted outgoing inter BSC inter cell handovers

Attempted outgoing internal inter cell handovers +
June 2008
Page 63 of 87
Data Collection Checklist

Source Network Data BSS Network configuration Sector coordinates Traffic HO Attempts per cell relation Modeling Data Day 1 For R002, R007 RLMF FR RLMF HR DAC UAC BSS Network configuration For S6000
Neighbor Measurements (C/I data)
Check
Comments
Day 2
Day 3
Day 4
Day 5
RLMF FR 0-4 RLMF HR 0-4 RLMF FR 5-7 RLMF HR 5-7 BSS Network configuration Network Performance Statistics SDCCH assignments SDCCH Traffic SDCCH Performance TCH assignments TCH Traffic TCH performance HO performance per cell relation HO performance per cell
June 2008
Page 64 of 87
Appendix A
Steps to Query Statistics Counters (Example: K3003 Successful SDCCH Seizures): 1. From the iManager M2000 window, click on the Performance drop down menu and select the Query Result to launch the Query Result window as shown below:
Figure 56: Query Result Window 2. Click on Call Measurement > KPI Measurement per Cell on the left of the window. 3. Click on Object Settings > Network to show all BSCs.
June 2008
Page 65 of 87
Figure 57: Object Settings - All BSCs 4. Select the BSC (single or multiple BSCs) for which KPI statistics are queried. 5. Click the > button to add the BSCs to the Selected Objects area.
Figure 58: BSC - Filter by Status
June 2008
Page 66 of 87
6. Click on Counter Settings > System Counter to show all KPI counters. 7. Select the K3003 Successful SDCCH Seizures counter and click the> button to add the counters to the Selected Counters area.
June 2008
Page 67 of 87
Figure 59: Addition of Counters to Selected Counters Area 8. On the Other Settings tab, select the appropriate settings as shown below and set the Start Time and End Time for querying.
June 2008
Page 68 of 87
9. Click Query to start the query for K3003 Successful SDCCH Seizures.
Figure 60: Query for K3003 Successful SDCCH Seizures
June 2008
Page 69 of 87
The result of the K3003 Successful SDCCH Seizures query is displayed. 10. Right click on the query result and select Export All
June 2008
Page 70 of 87
11. When the Save window appears, click on the File Type drop down menu and select CSV Files (*.csv).
Figure 62: Selection of *.csv Files 12. Navigate to the selected folders and type Successful SDCCH Seizures on the File Name field. 13. Click Save to save the file in *.csv format. 14. Repeat Steps 113 for all of the Call Measurement counters. Note: The system returns results faster if one BSC at a time (rather than multiple BSCs) is queried.
June 2008
Page 71 of 87
Appendix B
Steps to Export and Import Frequency Table in preparation for retuning: To export a sample FrequencyTable.txt from S6000: 1. Log on to the local BSCs BSC6000 Local Maintenance Terminal. 2. Choose Configuration > Import or Export Data > Export Network Plan Parameter.
Figure 63: Export Network Plan Parameter Menu
June 2008
Page 72 of 87
The Export Network Plan Parameter dialog box, with Choose the export type displayed.
Figure 64: Choose Export Type 3. Click on Export frequency data of cells, and then click Next>> to launch the Choose the export object step.
June 2008
Page 73 of 87
Figure 65: Choose Export Object 4. Select the cells from the Object Tree area on the left, and then click the > button to add them to the Selected Object List area on the right. 5. Click Export.
June 2008
Page 74 of 87
6. The Save As dialog box is displayed.
7. Navigate to the selected folder, and type FrequencyTable in the File Name field. 8. Click Save to save the FrequencyTable (in *.txt format).
June 2008
Page 75 of 87
To import FrequencyTable.txt to S6000: 9. Choose Configuration > Import or Export Data > Import Network Plan Parameter.
June 2008
Page 76 of 87
10. The Import Network Plan Parameter dialog box is displayed.
June 2008
Page 77 of 87
11. Click the button and select the folder with the FrequencyTable.txt file. 12. Click Open.
Figure 69: Open FrequencyTable.txt File
June 2008
Page 78 of 87
Figure 70: Selection of File to Import
13. Click Finish. Note: The FrequencyTable.txt file should only contain sectors with frequencies that were changed by Ultima Fort (only sectors in the optimization set). Try to export the FrequencyTable.txt file with the HandoversTable.txt file. When Ultima Fort supports Export FP for Huawei S6000, this FrequencyTable.txt will be mandatory.
June 2008
Page 79 of 87
Appendix C:
To Export and Import 2G External Cells Table after importing the FrequencyTable.txt to update the neighbors of external cells (sectors belonging to a different BSC): To export a sample 2G External Cells.txt from S6000: 1. Log on to the local BSCs BSC6000 Local Maintenance Terminal. 2. Choose Configuration > Import or Export Data > Export Network Plan Parameter.
Figure 71: Export Network Plan Parameter Menu
June 2008
Page 80 of 87
The Export Network Plan Parameter dialog box, with Choose the export type is displayed.
Figure 72: Choose Export Type 3. Click on Export 2G external cells, and then click Next>> to launch the Choose the export object step.
June 2008
Page 81 of 87
Figure 73: Choose Export Object 4. Select the cells from the Object Tree area on the left, and then click the > button to add the cells to the Selected Object List area on the right. 5. Click Export.
June 2008
Page 82 of 87
6. The Save As dialog box is displayed.
7. Navigate to the selected folders, and name the file in the File name box. 8. Click Save to save the 2G External Cells (in *.txt format).
June 2008
Page 83 of 87
To import 2G External Cells.txt to S6000: 1. Choose Configuration > Import or Export Data > Import Network Plan Parameter.
June 2008
Page 84 of 87
2. The Import Network Plan Parameter dialog box is displayed.
3. Click the button and select the folder containing the 2G External Cells.txt file. 4. Click Open.
June 2008
Page 85 of 87
Figure 77: Opening 2G External Cell.txt File
June 2008
Page 86 of 87
Figure 78: Selection of File to Import
5. Click Finish. 6. Repeat Steps 15 for all sectors in other BSCs with neighbors for the BSC optimization set. Note: The 2G External Cells.txt file should only contain sectors with neighbors for the optimization set whose frequencies were changed by Ultima Fort (sectors with neighbors in the optimization set).
June 2008
Page 87 of 87

Ultima Forté Required Data Inputs For Huawei Infrastructure

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Ultima Forté Required Data Inputs For Huawei Infrastructure

Hochgeladen von

Copyright:

Verfügbare Formate

Ultima - Fort Required Data Inputs for Huawei Infrastructure

Copyright 2008 Schema

Schema Confidential & Proprietary

Ultima - Fort Required Data Inputs for Huawei Infrastructure

Data Collection Checklist......................................................................... 64

Schema Confidential & Proprietary

Ultima - Fort Required Data Inputs for Huawei Infrastructure

Schema Confidential & Proprietary

Ultima - Fort Required Data Inputs for Huawei Infrastructure

Schema Confidential & Proprietary

Ultima - Fort Required Data Inputs for Huawei Infrastructure

Schema Confidential & Proprietary

Ultima - Fort Required Data Inputs for Huawei Infrastructure

Schema Confidential & Proprietary

Ultima Fort Required Data Inputs for Huawei Infrastructure

Required Information and Data

2.2.1.1 Huawei BSS Naming Convention

Schema Confidential & Proprietary

Ultima Fort Required Data Inputs for Huawei Infrastructure

The above packages are referred to as R002, R007, and S6000.

2.2.1.2 Release R002 and Release R007

2.2.1.3 BSC Hardware Release S6000

Schema Confidential & Proprietary

Ultima Fort Required Data Inputs for Huawei Infrastructure

Schema Confidential & Proprietary

Ultima Fort Required Data Inputs for Huawei Infrastructure

Figure 3: Configuration-Browse Configuration Data

Schema Confidential & Proprietary

Ultima Fort Required Data Inputs for Huawei Infrastructure

Figure 4: Select Dialog Box

Schema Confidential & Proprietary

Ultima Fort Required Data Inputs for Huawei Infrastructure

Schema Confidential & Proprietary

Ultima Fort Required Data Inputs for Huawei Infrastructure

Schema Confidential & Proprietary

Ultima Fort Required Data Inputs for Huawei Infrastructure

Schema Confidential & Proprietary

Ultima Fort Required Data Inputs for Huawei Infrastructure

All of the tables are launched.

Figure 8: Launch all Tables

Schema Confidential & Proprietary

Ultima Fort Required Data Inputs for Huawei Infrastructure

Schema Confidential & Proprietary

Ultima Fort Required Data Inputs for Huawei Infrastructure

A Save As dialog box is displayed.

Schema Confidential & Proprietary

Ultima Fort Required Data Inputs for Huawei Infrastructure

Figure 11: Other Cell Attributes Table

Schema Confidential & Proprietary

Ultima Fort Required Data Inputs for Huawei Infrastructure

Sector Coordinates File

Schema Confidential & Proprietary

Ultima Fort Required Data Inputs for Huawei Infrastructure

Mobile Statistics Data Recordings

Addition and Deletion of New Neighbors

2.3.1.1 Versions R002 and R007

Schema Confidential & Proprietary

Ultima Fort Required Data Inputs for Huawei Infrastructure

Figure 12: Data Auto Configuration System

Figure 13: Data Auto Configuration

Select Export Network Parameters.

Schema Confidential & Proprietary