ultima forte required data inputs for huawei infrastructure.pdf

Ultima Forte

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 ©2011 Schema

Ultima Forte – Required Data Inputs for Huawei Infrastructure

Schema Confidential & Proprietary February 2011 of 142

Table of Contents

1 Introduction .............................................................................................. 7

2 Required Information and Data ................................................................. 8

2.1 Optimization Area ............................................................................................ 8

2.2 Network Data .................................................................................................. 8

2.2.1 Huawei BSS Network Configuration .......................................................... 8

2.2.1.1 Huawei BSS Naming Convention ............................................................... 8 2.2.1.2 BSC Hardware Release 32 ........................................................................ 9 2.2.1.3 BSC Hardware Release S6000 ................................................................. 10 2.2.1.4 BSC Hardware Release S6900 ................................................................. 20

2.2.2 Sector Coordinates File ......................................................................... 23

2.3 Mobile Statistics Data Recordings .................................................................... 24

2.3.1 Addition and Deletion of New Neighbors ................................................. 25

2.3.1.1 Versions R002 and R007 ........................................................................ 25 2.3.1.2 Process for S6000: ................................................................................ 29 2.3.1.3 Process for S6900: ................................................................................ 37

2.3.2 Activation of Recordings (R002 and R007) .............................................. 41

2.3.3 Activation of Recordings (S6000) ........................................................... 46

2.3.4 Activation of Recordings (S6900) ........................................................... 48

2.3.5 Activation of Recordings in M2000 version R8C01B060SPC003 and above .. 49

2.3.5.1 New Added Function .............................................................................. 49 2.3.5.2 Query The Status Of Importing The Neighboring Cell Data .......................... 50 2.3.5.3 Import the Neighboring Cell Data ............................................................ 52

2.4 Retrieving Mobile Statistics Results .................................................................. 54

2.4.1 iManager Retrieval for Versions R002 and R007 ....................................... 54

2.4.2 MS Retrieval for S6000 ......................................................................... 56

2.4.3 MS Retrieval for S6900 ......................................................................... 77

2.4.3.1 Neighbor Cell Level Measurement per Cell retrieval: .................................. 78 2.4.3.2 TCHF/H Receive Level Measurement per TRX (RLMF FR/RLMF HR) retrieval: . 82

2.5 Traffic File .................................................................................................... 84

2.6 GPRS/EDGE Traffic File ................................................................................... 85

2.7 Handover Statistics ........................................................................................ 85

2.8 Retrieving TA data ......................................................................................... 85

2.9 Traffic Balance KPI file ................................................................................... 86

2.10 UL Interference ............................................................................................. 86

3 Network Performance Statistics .............................................................. 91

3.1 Network Performance Evaluation ..................................................................... 92

3.2 Radio Network Performance KPIs Calculation .................................................... 92

3.3 Additional KPIs for Network Performance Evaluation .......................................... 93

4 Data Collection Checklist ......................................................................... 95



Appendix A .................................................................................................... 96

Appendix B .................................................................................................. 102

Appendix C: ................................................................................................. 110

Appendix D .................................................................................................. 118

Appendix E: Step-by-Step 3G Update Implementation ............................... 123

3G Update for Huawei Networks ............................................................................ 123

3G Update for Ericsson Networks ........................................................................... 131

3G Update for NSN Networks ................................................................................. 138



Table of Figures

Figure 1: BSC6000 Local Maintenance Terminal ................................................................ 10

Figure 2: Login Dialog Box ............................................................................................. 11

Figure 3: Configuration-Browse Configuration Data ........................................................... 11

Figure 4: Select Dialog Box ............................................................................................ 12

Figure 5: Browse Cell Data ............................................................................................ 13

Figure 6: Browse TRX and Channel Data .......................................................................... 14

Figure 7: Browse Other Data .......................................................................................... 15

Figure 8: Launch all Tables ............................................................................................ 16

Figure 9: Cell Channel Management Data Table ................................................................ 17

Figure 10: Save As Dialog Box ....................................................................................... 18

Figure 11: Other Cell Attributes Table ............................................................................. 19

Figure 12: M2000 Main Topology Window ........................................................................ 20

Figure 13: BSC6900 Local Maintenance Terminal .............................................................. 21

Figure 14: Export Configuration Data .............................................................................. 22

Figure 15: Data Auto Configuration System ..................................................................... 25

Figure 16: Data Auto Configuration ................................................................................. 25

Figure 17: Export Network Parameters ............................................................................ 26

Figure 18: Export Network Parameter ............................................................................. 26

Figure 19: Save Export File as Text File ........................................................................... 27

Figure 20: Import Network Parameters ........................................................................... 27

Figure 21: Upload Recently Generated File ....................................................................... 28

Figure 22: Confirmation Dialog Box ................................................................................. 28

Figure 23: Export Network Plan Parameter ...................................................................... 29

Figure 24: Choose the Export Type ................................................................................. 30

Figure 25: Choose the Export Object ............................................................................... 31

Figure 26: Save As Dialog Box ....................................................................................... 32

Figure 27: Import Network Plan Parameter Menu.............................................................. 33

Figure 28: Import Network Plan Parameter Dialog Box ...................................................... 34

Figure 29: Selection of HandoversTable.txt File ................................................................ 35

Figure 30: Select a File to be Imported............................................................................ 36

Figure 31: Task Management Window ............................................................................ 37

Figure 32: Task Dialog Box ........................................................................................... 38



Figure 33: Task Type Setting ........................................................................................ 39

Figure 34: Task Time Setting ........................................................................................ 40

Figure 35: Script Loading.............................................................................................. 41

Figure 36: Select Traffic Measurement ............................................................................ 42

Figure 37: Select New Task............................................................................................ 43

Figure 38: New Task Registration ................................................................................... 43

Figure 39: Definition of Data Set to Handle Task .............................................................. 44

Figure 40: BSC Cell Selection ......................................................................................... 44

Figure 41: Registration of All Statistical Items .................................................................. 45

Figure 42: Performance Measure Measurement Selection ................................................... 46

Figure 43: Performance Measure Measurement Window .................................................... 47

Figure 44: Performance Measure Measurement Selection ................................................... 48

Figure 45: Performance Measure Measurement Window .................................................... 49

Figure 46: iManager Service Menu .................................................................................. 55

Figure 47: Performance Query Result .............................................................................. 56

Figure 48: Query Result Display ..................................................................................... 57

Figure 49: Network Object Settings ................................................................................ 58

Figure 50: Object Selections .......................................................................................... 59

Figure 51: Available Counters ........................................................................................ 60

Figure 52: Selected Counters ......................................................................................... 60

Figure 53: Neighbor Cell Measurement Per Cell ................................................................ 61

Figure 54: Export Query Results ..................................................................................... 62

Figure 55: Saving Files .................................................................................................. 63

Figure 56: Saving Files in *.csv Format ........................................................................... 64

Figure 57: Query Result Object Settings .......................................................................... 65

Figure 58: Filter By Status ............................................................................................. 66

Figure 59: Available Counters to Selected Counters .......................................................... 67

Figure 60: Setting Start Time and End Time ..................................................................... 68

Figure 61: Query Export ................................................................................................ 69

Figure 62: Saving *.csv Files.......................................................................................... 70

Figure 63: Condition Button ........................................................................................... 71

Figure 64: Available Counters to Selected Counters .......................................................... 72

Figure 65: Setting Start Time and End Time ..................................................................... 73



Figure 66: Query Export ................................................................................................ 74

Figure 67: *.csv File Selection ........................................................................................ 75

Figure 68: Performance Query Result .............................................................................. 77

Figure 69: Query Result Display ..................................................................................... 78

Figure 70: Network Object Settings ................................................................................ 79

Figure 71: Object Selections .......................................................................................... 80

Figure 72: Available Counters ........................................................................................ 81

Figure 73: Selected Counters ......................................................................................... 81

Figure 74: Neighbor Cell Measurement Per Cell ................................................................ 82

Figure 75: Query Result Window .................................................................................... 96

Figure 76: Object Settings - All BSCs .............................................................................. 97

Figure 77: BSC - Filter by Status .................................................................................... 97

Figure 78: Addition of Counters to Selected Counters Area ................................................ 98

Figure 79: Query for K3003 Successful SDCCH Seizures .................................................... 99

Figure 80: Query Export ............................................................................................... 100

Figure 81: Selection of *.csv Files .................................................................................. 101

Figure 82: Export Network Plan Parameter Menu ............................................................. 102

Figure 83: Choose Export Type...................................................................................... 103

Figure 84: Choose Export Object ................................................................................... 104

Figure 85: Save As Dialog Box ...................................................................................... 105

Figure 86: Import Network Plan Parameter Menu............................................................. 106

Figure 87: Import Network Plan Parameter Dialog Box ..................................................... 107

Figure 88: Open FrequencyTable.txt File ......................................................................... 108

Figure 89: Selection of File to Import ............................................................................. 109

Figure 90: Export Network Plan Parameter Menu ............................................................. 110

Figure 91: Choose Export Type...................................................................................... 111

Figure 92: Choose Export Object ................................................................................... 112

Figure 93: Save As Dialog Box ...................................................................................... 113

Figure 94: Import Network Plan Parameter Menu............................................................. 114

Figure 95: Import Network Plan Parameter Dialog Box ..................................................... 115

Figure 96: Opening 2G External Cell.txt File .................................................................... 116

Figure 97: Selection of File to Import ............................................................................. 117



1 Introduction

This document lists the information and data to be collected in order to optimize Huawei GSM

infrastructures, using Ultima Forte.

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.



2 Required Information and Data

2.1 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 Network Data

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

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 BSC Hardware Release 32

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.

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.

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



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.



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.



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


13. Click OK.



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


16. Click OK.



All of the tables are launched.

Figure 8: Launch all Tables



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.



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



20. Repeat this procedure for all other launched tables (Steps 15 – 17) (e.g., Other Cell

Attributes).

Figure 11: Other Cell Attributes Table

21. HandoverTable.txt (see 2.3.1.2.1) and FrequencyTable.txt (see appendix B) are

required.

22. Repeat Steps 1-21 for each BSC, required to create the environment.



2.2.1.4 BSC Hardware Release S6900

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 BSC6900 Local Maintenance

Terminal shown in Figure 12

2.

Figure 12: M2000 Main Topology Window



Figure 13: BSC6900 Local Maintenance Terminal

3. From the BSC6900 Local Maintenance Terminal, select MML Commands System

Management Configuration Management Configuration Data Management

Backup Data Management Export Configuration Data MML Script (EXP

CFGMML), as shown in Figure 3. You can run EXP CFGMML command directly in

Command Input as well.



Figure 14: Export Configuration Data

4. Use the File Manager to retrieve the data. The path is visible when you run EXP

CFGMML.



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.



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.

Figure 15: Data Auto Configuration System

Figure 16: Data Auto Configuration



3. Select Export Network Parameters.

Figure 17: Export Network Parameters

4. Select Export Adjacent Relationship of Cells.

5. Select All cells.

6. Select Export Parameter.

Figure 18: Export Network Parameter



7. Save the export file as a text file.

Figure 19: Save Export File as Text File

Based on the provided export data file, Forte 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:

8. Select Import Network Parameters.

Figure 20: Import Network Parameters



9. Select and load the recently generated file (with updated neighbor relations).

Figure 21: Upload Recently Generated File

10. Confirm the single adjacent relationship of all BSC cells after the upload.

Figure 22: Confirmation Dialog Box



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 BSC‟s BSC6000 Local Maintenance Terminal.

2. Select ConfigurationImport or Export DataExport Network Plan Parameter.

Figure 23: Export Network Plan Parameter



The Export Network Plan Parameter dialog box, with Choose the export type

displayed.

Figure 24: Choose the Export Type



3. Click on Export adjacent cells, and then click Next>> to launch the Choose the

export object step.

Figure 25: 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.



The Save As dialog box is displayed.


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 and External2GTable

To import HandoversTable.txt to S6000:

1. Choose ConfigurationImport or Export DataImport Network Plan Parameter.

Figure 27: Import Network Plan Parameter Menu



The Import Network Plan Parameter dialog box is displayed.

Figure 28: Import Network Plan Parameter Dialog Box

2. Click the … button and select the folder containing the HandoversTable.txt file.



3. Click Open.

Figure 29: Selection of HandoversTable.txt File



Figure 30: Select a File to be Imported

4. Click Finish.

5. The above steps are similar for importing 2G External Cell file (see appendix C).

6. Repeat Steps 1-5 for each BSC (optimization set and buffer zone sectors) required to

generate the MP script.

7. The 2G External, created for the measurement plan, should be removed after the last

day of collecting mobile measurements (see appendix D).

Note: The HandoversTable.txt file should only contain sectors with fake neighbors

added by Ultima Forte; 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 computer‟s 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.



2.3.1.3 Process for S6900:

2.3.1.3.1 Create Task to Add 2G External Cells and Handovers

1. Select Maintenance > Task Management from M2000. The Task Management

window is displayed.

Figure 31: Task Management Window

2. Click New. The New Task dialog box is displayed.



Figure 32: Task Dialog Box

3. Type the name of a timing task in Task Name. Select MML Script in Task Type. Select

Once in Run Type and click Next.



Figure 33: Task Type Setting

4. Select Start Time for performing the task in Time Setting. If you select Run At Once,

the Start Time parameter is invalid, and the task is performed immediately after the

related settings are complete. Click Next.



Figure 34: Task Time Setting

5. Browse Script File to load the script. Check the Select NE box and select the relevant

BSC. Execution Mode is not important if you select only one NE. Select Ignore in

Error-Execution Mode to continue running the script when you receive an error. In

Execution Result, specify the location to Save As for either the Failed Result or All

Result. Click Finish to run the script.



Figure 35: Script Loading

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 36: Select Traffic Measurement



3. Select Task > New.

Figure 37: Select New Task

4. Register the new task with all available parameters.

Figure 38: New Task Registration



5. Define the data set required to handle the task.

Figure 39: Definition of Data Set to Handle Task

6. Select all the cells of the measured BSC.

Figure 40: BSC Cell Selection



7. Follow the above steps to register the Defined Adjacent Cell statistics.

Figure 41: Registration of All Statistical Items

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.3.3 Activation of Recordings (S6000)

1. From the iManager 2000 window, click the Performance drop down menu and select

Measure Management to launch the Measure Management window as shown below:

Figure 42: Performance Measure Measurement Selection



Figure 43: Performance Measure Measurement Window

2. Click on MR Measurement and then select Neighbor Cell Level Measurement per Cell

from the list.

3. From the BSC list – select the relevant BSCs.

4. Make sure all sectors are checked on the window to the right of the BSC list.

5. On the upper window, select 60 minutes.

6. Make sure all of the counters are checked.

7. Repeat steps 3-6 for all relevant BSCs.

8. Click Apply.



2.3.4 Activation of Recordings (S6900)

1. From the M2000 window, click the Performance drop down menu and select Measure

Management to launch the Measure Management window as shown below:

Figure 44: Performance Measure Measurement Selection

2. Click on MR Measurement and then select Neighbor Cell Level Measurement per Cell

from the list.

3. Select the relevant BSCs from the BSC list.

4. Make sure all sectors are checked on the window on the bottom right of the BSC list.

5. On the upper window, select 60 minutes.

6. Make sure all of the counters are checked.

7. Repeat steps 3-6 for all relevant BSCs.



8. Click Apply.

Figure 45: Performance Measure Measurement Window

NOTE: The above process should be implemented for TCHH Receive Level Measurement

per TRX and TCHH Receive Level Measurement per TRX.

2.3.5 Activation of Recordings in M2000 version

R8C01B060SPC003 and above

2.3.5.1 New Added Function

Neighboring Cell Data Import

The neighbor cell data for RNC, BSC6000 and BSC NEs are not saved in the database directly,

while saved in the file in M2000; when the user needs to query the neighbor cell data in M2000,

it is necessary to import the file got from the NEs before querying the results.

1、 The menu (Performance) -> (Neighboring Cell Data Import)



Figure 46: Neighboring Cell Data Import menu bar

2、 Main Interface for Neighboring Cell Data Import

Figure 47: Main Interface for Neighboring Cell Data Import

Included in the function: Query the status of Importing the Neighboring Cell Data, Import

the Neighboring Cell Data.

2.3.5.2 Query The Status Of Importing The Neighboring Cell Data

By clicking the button “Query”, the window for querying the status of importing process,

appears as follows:



Figure 48: Query Window Status

Step for querying the importing data:

1. Select the function subset, NE on the left, and select the period and time range

2. Click the button “OK” for querying

3. The status of importing NE is displayed as follows:



Figure 49: Importing Data Status

2.3.5.3 Import the Neighboring Cell Data

By clicking the button “Import”, the windows for importing the neighboring cell data,

appears as follows:



Figure 50: Neighboring Cell Data Import

Step for importing the Neighboring Cell Data: 1. Select the function subset, NE on the left, and select the period and time range

2. Click the button “OK” for importing

3. Cue for sending success

Figure 51: The Command Execute Success

4. The operation results for importing the Neighboring Cell Data are displayed as follows:



Figure 52: Import Status Results

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 53: iManager Service Menu

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.



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 54: Performance Query Result



Figure 55: Query Result Display



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 56: Network Object Settings

3. Select the BSCs that are scheduled for retrieval of mobile statistics measurements.



4. Click the > button to add the BSC to the Selected Objects area.

Figure 57: 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. The counters should be selected for one BSC at a time, for few hours

around the busy hour.



Figure 58: Available Counters

Figure 59: Selected Counters



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 60: Neighbor Cell Measurement Per Cell

The Neighbor Cell Level Measurement per Cell query result is displayed.



9. Right click on the query result and select Export All…

Figure 61: Export Query Results



10. When the Save window appears, click on the File Type drop down menu, and select

CSV Files (*.csv)

Figure 62: Saving Files

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 63: 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).



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 64: Query Result Object Settings

3. Select the BSC that is scheduled to retrieve the mobile statistics measurements. (This

step should be done separately for each BSC.)




Figure 65: Filter By Status

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. The counters should be selected for one BSC at a time, for

few hours around the busy hour.

Figure 66: Available Counters to Selected Counters





8. Click Query to start the query for TCHH Receive Level Measurement per TRX

(RLMF_HR(0-4)).

Figure 67: Setting Start Time and End Time

The result of the TCHH Receive Level Measurement per TRX query is posted.




Figure 68: Query Export



10. When the Save window appears, click on the File Type drop down menu, and select

CSV Files (*.csv).

Figure 69: Saving *.csv Files

11. Navigate to the selected folders and type RLMF_HR(0-4) in the File Name field.




13. Click on the Condition button to re-launch the Query Result window.

Figure 70: Condition Button

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.

Figure 71: Available Counters to Selected Counters





17. Click Query to start the query for TCHH Receive Level Measurement per TRX

(RLMF_HR(5-7)).

Figure 72: Setting Start Time and End Time

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…




20. When the Save window appears, click on the File Type drop down menu and select CSV

Files (*.csv).

Figure 74: *.csv File Selection

21. Navigate to the selected folders and type RLMF_HR(5-7) on the File Name field.


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

RLMF_FR(0-4) - S4100A - S4147B

RLMF_FR(5-7) - S4150A - S4177B

RLMF_HR(0-4) - S4100C - S4147D

RLMF_HR(5-7) - S4150C - S4177D



25. Locate all of the collected data in „Model‟ folder, with the following structure:



2.4.3 MS Retrieval for S6900

From the Main Topology window, right click on the BSC and select Query Performance Result

to launch the Query Result window as shown below:

Figure 75: Performance Query Result



Figure 76: Query Result Display

2.4.3.1 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 77: Network Object Settings

3. Select the BSCs that are scheduled for retrieval of mobile statistics measurements.




Figure 78: Object Selections

5. Click on Counter Settings > All Counter to show all counters.

6. Select All counters and click the > button to add the selected counters to the

Selected Counters area. The counters should be selected for one BSC at a time, for a

few hours close to the busy hour.



Figure 79: Available Counters

Figure 80: Selected Counters





8. Click the Export button to start the query and save the result in *.csv format for

Neighbor Cell Level Measurement per Cell.

Figure 81: Neighbor Cell Measurement Per Cell

9. 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).

2.4.3.2 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 the Object Settings tab > Network to show all of the BSCs.

3. Select the BSC that is scheduled to retrieve the mobile statistics measurements. (This

step should be done separately for each BSC.)


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 the > button to add the counters

to the Selected Counters area. The counters should be selected for one BSC at a time,

for a few hours close to the busy hour.



8. Click the Export button to start the query and save the result in *.csv format (type

RLMF_HR(0-4) in the File Name field) for TCHH Receive Level Measurement per

TRX (RLMF_HR(0-4)).



9. Repeat Steps 1-5.

10. Select S4150C counter - S4177D counter and click the > button to add the counters

to the Selected Counters area.



12. Click the Export button to start the query and save the result (type RLMF_HR(5-7) in

the File Name field) in *.csv format for TCHH Receive Level Measurement per TRX

(RLMF_HR(5-7)).

13. Repeat Steps 1-12 for the TCHF Receive Level Measurement per TRX report.

14. 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).

RLMF_FR(0-4) - S4100A - S4147B

RLMF_FR(5-7) - S4150A - S4177B

RLMF_HR(0-4) - S4100C - S4147D

RLMF_HR(5-7) - S4150C - S4177D

15. Locate all of the collected data in the Model folder:

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 Erlang)

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 four-

hour period that includes the network peak hour, and should be generated on the last recording

day.



2.6 GPRS/EDGE Traffic File

The GPRS/EDGE traffic file should be in tab-delimited text file format with information for all

sectors in the optimization and simulation areas (the guard-zone area), and should include the

following columns:

Sector

GPRS Traffic (in Erlang)

EDGE Traffic (in Erlang)

The required traffic file can be prepared with raw traffic data from the Performance

Management system. This file can be retrieved from the M2000 performance manager by

querying counters L9101, L9001, L9302- L9310 and L9202- L9210 using the same method

used to query mobile measurement statistics.

2.7 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.8 Retrieving TA data

The required TA (Time Advance) data file can be prepared with raw traffic data from the

Performance Management system. This file can be retrieved from the M2000 performance

manager by querying counters S4400A- S4463A using the same method used to query mobile

measurement statistics.



2.9 Traffic Balance KPI file The KPI files contain data about blockages, utilization, and traffic. Each file should have the

following name format: KPIyyyyddmm_<BSC name>.txt

The files should contain the following information:

Field Type Range Comments

Sector String Sector name

Date String DD/MM/YYYY or MM/DD/YYYY

Hour Time 00:00, 01:00, 02:00, …, 23:00

FR

Traffic

Double Carried traffic, in Erlangs

Note: This does not include the AMR

FR traffic

HR

Traffic

Double Carried traffic, in Erlangs

Note: This does not include the AMR

HR traffic

Blockage Percent 0 to 100 Optional

LAC

String

Optional

CI String Optional

The following are the minimal and maximal input data required for the load balancing

optimization:

Minimal data is traffic per network busy hour, for seven days

Maximal data is traffic, AMR traffic, and blockage, per hour, for one month

You can also use any data in between the minimal and maximal data listed above.

2.10 UL Interference Steps to Uplink interference data preparation:

1. Log on to the local BSC‟s BSC6000 Local Maintenance Terminal.



2. Choose the required cell and then click on Configuration Frequency Scan option (right

click on the cell).

3) Choose the frequency list and the start time of the scan in Configure Frequency Scan

window.



4) Press start to apply the configuration, success message should appear.

Success message



5) Save the output as a text file.



3 Network Performance Statistics

Network performance statistics should be collected for network traffic modeling and post-

optimization network performance benchmarking.

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.

SDCCH Traffic:

o Sum of SDCCH measurement reports in the cell.

SDCCH Performance (drop, drop reason):

o SDCCH Call Drop, SDCCH lost radio connections (connection failure), SDCCH lost radio

connections (error indicator).

TCH Assignments (TCH assignment attempts and failures):

o Attempted TCH seizures (all), attempted TCH seizures for call, successful TCH seizures

(all), successful TCH seizures for call, attempted TCH seizures meeting TCH overflow.

TCH Traffic:

o 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 Performance (drop, drop reason):

o TCH Call Drop, TCH lost radio connections (connection failure), TCH lost radio

connections (error indicator).

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.

HO Performance (cell):

o Attempted outgoing internal inter cell handovers, attempted outgoing inter BSC inter-

cell handovers, attempted handovers for uplink quality, attempted handovers for

downlink quality, successful outgoing internal inter cell handovers, successful outgoing

inter BSC inter cell handovers.



3.1 Network Performance Evaluation

Each KPI improvement rate will be calculated as follows:

%100__

before

newbefore

KPI

KPIKPIratetimprovemenKPI

The Success Rate KPIs (SDCCH/TCH Setup, HO) improvement will be calculated as follows:

%100100

___

before

beforenew

KPI

KPIKPIratetimprovemenSuccessKPI

%100____

before

beforenew

KPI

KPIKPIratetimprovemenDroptoErlang

Each KPI improvement ratio can be calculated separately over a period of five working days

(during each day‟s 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.

3.2 Radio Network Performance KPIs Calculation

The following calculations will be used for KPIs proposed for Radio Network performance

evaluation:

(all) seizures SDCCH Successful

)indicator(error sconnection radiolost SDCCH

failure)n (connectio sconnection radiolost SDCCH

___ RadioRateDropSDCCH

(all) seizures TCH Successful

)indicator(error sconnection radiolost TCH

failure)n (connectio sconnection radiolost TCH

___ RadioRateDropTCH

callfor seizures TCH Successful


failure)n (connectio sconnection radiolost TCH

___ RadioRateDropCall




failure)n (connectio sconnection radiolost TCH7500

)assignmentearly very (excl. cell in the reportst measuremen TCH of Sum

)assignmentearly very (excl. cell 1800in reportst measuremen TCH of Sum

___ RadioDroptoErlang

7

0

7

5___

x

DL

x

DL

RLMF

RLMF

DLQualityBadTCH

7

0

7

5___

x

UL

x

UL

RLMF

RLMF

ULQualityBadTCH

handovers cellinter BSCinter outgoing Attempted

handovers cellinter internal outgoing Attempted

handovers cellinter BSCinter outgoing Successful

handovers cellinter internal outgoing Successful

___ RateSuccessHOOutgoing

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.

3.3 Additional KPIs for Network Performance Evaluation

The following calculations provide additional KPIs for network performance evaluation:

(all) Seizures SDCCH Attempted

(all) seizures SDCCH Successful__ SuccessAssignmentSDCCH


Drop Call SDCCH__ RateDropSDCCH


overflow SDCCH meeting seizures SDCCH Attempted__ RateBlockSDCCH



(all) seizures TCH Attempted

(all) seizures TCH Successful__ SuccessAssignmentTCH

(all) seizures TCH Successful

drop call TCH__ RateDropTCH

(all) seizures TCH Attempted

overflow TCH meeting seizures TCH Attempted__ RateBlockTCH

callfor seizures TCH Successful

drop call TCH__ RateDropCall

drop call TCH7500



__

DroptoErlang

7660

cell in the reportst measuremen SDCCH of Sum_

TrafficSDCCH

7500



_

TrafficTCH

7500

FR_RLMF__

DLFRTrafficTCH

7500

HR_RLMF__

DLHRTrafficTCH



qualitydownlink for handovers Attempted___ CauseQualDLHO



qualityuplink for handovers Attempted___ CauseQualULHO



4 Data Collection Checklist Source Check Comments

Network Data

BSS Network configuration

Sector coordinates

Traffic

HO Attempts per cell relation

Modeling Data

Day 1 Day 2 Day 3 Day 4 Day 5

For R002, R007

RLMF FR

RLMF HR

DAC

UAC


For S6000

Neighbor Measurements (C/I data)

RLMF FR 0-4

RLMF HR 0-4

RLMF FR 5-7

RLMF HR 5-7


Network Performance Statistics

SDCCH assignments

SDCCH Traffic

SDCCH Performance

TCH assignments

TCH Traffic

TCH performance

HO performance per cell relation

HO performance per cell



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 82: 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.



Figure 83: 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 84: BSC - Filter by Status



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.

Figure 85: 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.

9. Click Query to start the query for K3003 Successful SDCCH Seizures.

Figure 86: Query for K3003 Successful SDCCH Seizures

The result of the K3003 Successful SDCCH Seizures query is displayed.



11. When the Save window appears, click on the File Type drop down menu and select CSV

Files (*.csv).

Figure 88: Selection of *.csv Files

12. Navigate to the selected folders and type Successful SDCCH Seizures on the File

Name field.


14. Repeat Steps 1–13 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.



Appendix B

Steps to Export and Import Frequency Table in preparation for retuning:

To export a sample FrequencyTable.txt from S6000:


16. Choose Configuration > Import or Export Data > Export Network Plan

Parameter.

Figure 89: Export Network Plan Parameter Menu



The Export Network Plan Parameter dialog box, with Choose the export type

displayed.

Figure 90: Choose Export Type



17. Click on Export frequency data of cells, and then click Next>> to launch the Choose

the export object step.

Figure 91: Choose Export Object

18. 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.

19. Click Export.



20. The Save As dialog box is displayed.


21. Navigate to the selected folder, and type “FrequencyTable” in the File Name field.

22. Click Save to save the FrequencyTable (in *.txt format).



To import FrequencyTable.txt to S6000:

1. Choose Configuration > Import or Export Data > Import Network Plan

Parameter.




2. The Import Network Plan Parameter dialog box is displayed.


3. Click the … button and select the folder with the FrequencyTable.txt file.



4. Click Open.

Figure 95: Open FrequencyTable.txt File



Figure 96: Selection of File to Import

5. Click Finish.

Note: The FrequencyTable.txt file should only contain sectors with frequencies that were

changed by Ultima Forte (only sectors in the optimization set). Try to export the

FrequencyTable.txt file with the HandoversTable.txt file. When Ultima Forte supports Export

FP for Huawei S6000, this FrequencyTable.txt will be mandatory.



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:


2. Choose Configuration > Import or Export Data > Export Network Plan

Parameter.

Figure 97: Export Network Plan Parameter Menu



The Export Network Plan Parameter dialog box, with Choose the export type is

displayed.

Figure 98: Choose Export Type



3. Click on Export 2G external cells, and then click Next>> to launch the Choose the

export object step.

Figure 99: 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.



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



To import 2G External Cells.txt to S6000:

1. Choose Configuration > Import or Export Data > Import Network Plan

Parameter.




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.

Figure 103: Opening 2G External Cell.txt File



Figure 104: Selection of File to Import

5. Click Finish.

6. Repeat Steps 1–5 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 Forte (sectors with neighbors in

the optimization set).



Appendix D

External sectors, created by Forte, can be removed in one of two ways:

1. Automatic MML script (MML interface available from R003)

Login to the local BSC LMT



Go to System Batch Command (or use the hot key Ctrl+E)

The following window will appear:



Select Open and select the Script (*.txt)



2. Manual Removal:

Login to the local BSC LMT

Right click on the BSC6000 to expand the sector list and at the bottom of the list you will see

the 2G External Cells as shown below:



Right click on the External sectors that you want to delete and select “Delete 2G External Cell”

as shown below:



Appendix E: Step-by-Step 3G Update

Implementation

3G Update for Huawei Networks

1. Connect to the Local Management Terminal (LMT).



2. Execute “FOC CMCTRL” to obtain the Configuration Control Right.



3. Open the Batch Commands to execute Forte‟s update file.



4. Open the Forte update file



5. Choose where you will save the output file.



6. Execute Forte‟s update file.



7. Close the LMT and release the Configuration Control.



3G Update for Ericsson Networks

1. Copy Forte‟s .xml export on the Ericsson UMTS import directory.

2. Go to OSS WCDMA Common Explorer.



3. Create a New Planned Configuration.

The New Planned Configuration dialog box is displayed.



4. Import Forte‟s UMTS update file (.xml)

A dialog box is displayed enabling you to select the update file to import.



The progress of the import is displayed.



5. Activate the planned configuration.



A dialog box is displayed.



Planned Configuration Activation complete.

6. UMTS Network Update successful



3G Update for NSN Networks

1. The update will require Netact CM Operations Manager and CM Editor.

IMPORTANT: Modifications to different Network Elements should be implemented

depending on which OSS the 2G cells are located in.

a) If the ADJGs are from one OSS to another (Nokia or another vendor), the modifications

should be made to the Virtual Cells located in the OSS where 3G is (The VCs are under the

BSC-0/BCF-0).

The notation of the VCs is BTS-(LAC+CI) . Where LAC takes 5 spaces, for example:

BTS-91 _ _ _ 2081. The maximum allowed is 10 spaces, 5 for LAC and 5 for the CI.



b) If the ADJGs are from one OSS (3G Network) to the same OSS (2G Network also), the

modifications should be to the 3G Cells.

XML Examples for both cases:

Scenario A:



Scenario B:

The XML Script of option “b” is the FP generated by Forte (Set_FP.xml).

2. Prepare the XML script with CM Operations Manager.

Important: Do NOT Provision yet! (Uncheck the “Provision” option), and click “Start”.

The Prepare Plan Option checks the plan and whether all the ADJx defined for the site are

actualized in the XML plan (if our plan will modify a parameter related to the ADJxs, the CM

will automatically add the XML code in the plan to update the ADJxs)



3. When the plan preparations are finished, open the plan with CM Editor to check if the ADJGs

are correct.

In the above example, the planned and actual values are identical because the plan was

already successfully provisioned. Repeat this step after the Plan Provision finalization to

check if the ADJGs were actualized correctly



4. Open the Plan with CM Editor to check if the ADJGs are ready to actualize.

Now you have the MO ADJGs in your plan.

5. For Scenario A, start the Provision. For Scenario B, if the FP has already been executed in

MML, uncheck the “Entire Plan” scope and check only the RNCs of your ADJGs. For both

Scenarios, there is no need to prepare the plans again.

ultima forte required data inputs for huawei infrastructure.pdf

Documents