Ultima Forte

Required Data Inputs for ZTE

Infrastructure
(For Version 5.2 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 Ericsson Infrastructure

Schema Confidential & Proprietary February 2011 Page 2 of 15

Ultima Forte – Required Data Inputs for Ericsson Infrastructure

Table of
Contents
1 Introduction.............................................................................................3
2 Required Information and Data.................................................................4
2.1 Optimization Area.............................................................................................4
2.2 Network Data..................................................................................................4
2.2.1 ZTE BSS Network Configuration...............................................................4
2.2.2 Sector Coordinates File...........................................................................6
2.3 BA List Creation for Mobile Measurements Collection.............................................6
2.4 Mobile Measurements Data Collection.................................................................7
2.4.1 C/I Measurements Collection..................................................................10
2.4.2 RxLevel and RxQuality Measurements Collection.......................................10
2.4.3 TA Measurements.................................................................................10
2.4.4 GPRS/EDGE Traffic file..........................................................................10
2.4.5 Handover Statistics...............................................................................11
2.4.6 Traffic File...........................................................................................11
2.4.7 Traffic Balance KPI file..........................................................................11
2.5 Network Performance Statistics........................................................................12
2.5.1 Network Performance Evaluation............................................................12
2.5.2 Radio Network Performance KPI Calculation.............................................13
2.5.3 Additional KPI’s for Network Performance Evaluation.................................13
3 Data Collection Checklist.........................................................................14
4 Appendix...................................................................................................15

Schema Confidential & Proprietary February 2011 Page 3 of 15

Ultima Forte – Required Data Inputs for Ericsson Infrastructure

1 Introduction
This document contains a list of the information and data to be collected for ZTE GSM
infrastructures in order to perform an optimization cycle using Ultima Forte.

The following information is required:

 Optimization area and optimization goals

 ZTE BSS network configuration data
 Sector coordinate data
 Mobile measurement recordings
 Performance reports

This document not only identifies the required sources of data, but also explains how to obtain
the data.

Schema Confidential & Proprietary February 2011 Page 4 of 15

Ultima Forte – Required Data Inputs for Ericsson Infrastructure

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 ZTE BSS Network Confi guration

Retrieve the required BSS network configuration file from the ZTE OSS, using NetNumen(TM)
M31, according to the following steps:

1. Open Configuration Management Window.

Schema Confidential & Proprietary February 2011 Page 5 of 15

Ultima Forte – Required Data Inputs for Ericsson Infrastructure

2. In the tree in the left side of the window, select “Export Configuration Data” for the
required BSC and Config set.

3. Select the “Export Network Plan Data” option and then select Excel format.

Schema Confidential & Proprietary February 2011 Page 6 of 15

Ultima Forte – Required Data Inputs for Ericsson Infrastructure

2.2.2 Sector Coordinates File

The sector coordinates file should be in tab-delimited text file format, and should 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 BA List Creation for Mobile Measurements

Collection
In order to import BA List provisioning scripts into ZTE OSS, use the following procedure:

1. Open Configuration Management Window.

Schema Confidential & Proprietary February 2011 Page 7 of 15

Ultima Forte – Required Data Inputs for Ericsson Infrastructure

2. In the tree in the left side of the window, select “Batch Apply Network Plan Data” for the
required BSC and Config set.

2.4 Mobile Measurements Data Collection

The following network activities should stop during the time that data is 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

The following changes should be performed only during maintenance (not during recording):

 TRX additions
 Frequency changes (TCH)
 Frequency changes (BCCH and BSIC)
 Neighbor additions or deletions
 Site additions

No other parameters should be changed.

Schema Confidential & Proprietary February 2011 Page 8 of 15

Ultima Forte – Required Data Inputs for Ericsson Infrastructure

Retrieve the required BSS Mobile Statistics files from the ZTE OSS, using NetNumen(TM) M31, for
C/I, RxLevel, RxQuality, TA and GPRS/EDGE Traffic according to the following steps:

1. Open Performance Management window and select “Performance Data Query”.

2. Select the required counters (described in next section) in “Query Index” tab.

3. Select the required time of recording and granularity in “Query Time” tab.

Schema Confidential & Proprietary February 2011 Page 9 of 15

Ultima Forte – Required Data Inputs for Ericsson Infrastructure

4. Select the BSCs on which statistical data will be quried in “Query Object” tab and click o.k.

5. Export the results into XLS or CSV format and select all columns for the exported and click
o.k.

Schema Confidential & Proprietary February 2011 Page 10 of 15

Ultima Forte – Required Data Inputs for Ericsson Infrastructure

Note:

Network configuration files MUST be collected on a daily basis for each day that
mobile measurement files are collected.

2.4.1 C/I Measurements Collection

C/I measurements should be collected by querying all the counters belong to “MR Adjacent Cell
Measurement” group as described in section 2.4.

2.4.2 RxLevel and RxQuality Measurements

Collection
RxLevel and RxQuality measurements should be collected by querying all the counters belong to
“MR Serving Cell Measurement” group as described in section 2.4.

2.4.3 TA Measurements
TA measurements should be collected by querying all the counters belong to “MS TA
Measurement” group as described in section 2.4.

Schema Confidential & Proprietary February 2011 Page 11 of 15

Ultima Forte – Required Data Inputs for Ericsson Infrastructure

2.4.4 GPRS/EDGE Traffi c fi le

GPRS/EDGE Traffic should be collected by querying all the counters belong to “PS basic
Measurement” group as described in section 2.4.

2.4.5 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

2.4.6 Traffi c 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 should comply with Schema’s 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.4.7 Traffi c Balance KPI fi le

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:

Schema Confidential & Proprietary February 2011 Page 12 of 15

Ultima Forte – Required Data Inputs for Ericsson Infrastructure

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 Double Carried traffic, in Erlangs
Traffic Note: This does not include the AMR
HR traffic
Blockage Percent 0 to 100 Optional
LAC Optional
String
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.5 Network Performance Statistics

TBD

2.5.1 Network Performance Evaluation

Each KPI improvement rate will be calculated as:

KPI before  KPI after

KPI _ improvement _ rate   100%
KPI before

For the handover success rate the improvement will be calculated as:

Schema Confidential & Proprietary February 2011 Page 13 of 15

Ultima Forte – Required Data Inputs for Ericsson Infrastructure

KPI after  KPI before

Success _ improvement _ rate   100%
1  KPI before

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.

2.5.2 Radio Network Performance KPI Calculation

The following calculations provide KPIs to evaluate radio network performance:

TBD

2.5.3 Additional KPI’s for Network Performance

Evaluation

The following calculations provide additional KPIs to evaluate network performance:

TBD

Schema Confidential & Proprietary February 2011 Page 14 of 15

Ultima Forte – Required Data Inputs for Ericsson Infrastructure

3 Data Collection Checklist

Source Comments Check
Network Data
BSS Network
Configuration
Sector Coordinates File
Traffic File
Mobile Measurements Recordings
Day 1 Day 2 Day 3 Day 4 Day 5
BAR Files
MRR Files
RIR Files
BSS Network
Configuration
Network Performance Statistics
SDCCH Assignments  Immediate assignments attempts
 Immediate assignments failures
SDCCH Traffic  SDCCH traffic per cell
 SDCCH congestion
SDCCH Performance  SDCCH drop
 SDCCH drop reason
TCH Assignments  TCH assignment attempts
 TCH assignment failures
TCH Traffic  Traffic per cell
 Traffic FR/HR
TCH Performance  Drops
 Drops per reason
Handover (HO)  HO attempts
Performance per Cell  HO success
Relation  HO reversion
 HO drop
Intra-Cell Handover  HO reasons
Performance  HO attempts
 HO success

4 Appendix

Schema Confidential & Proprietary February 2011 Page 15 of 15