Ultima Fort Required Data Inputs for Nokia Infrastructure

Ultima Fort
Required Data Inputs
for

Nokia Infrastructure
(appropriate for Ultima Fort v3.9)
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 2007, Schema

Schema Confidential & Proprietary

page 1 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

Table of Contents
1
2

Introduction.......................................................................................................... 3
Required Information and Data............................................................................. 3
2.1
Optimization Goals and Areas.............................................................................3
2.2
Network Data ..................................................................................................4
2.2.1
Nokia BSS Network Configuration (Option A XML Format) .............................4
2.2.2
Nokia BSS Network Configuration (Option B Queries Format) ........................6
2.2.3
Sector Coordinates File ...............................................................................7
2.2.4
Traffic File ................................................................................................7
2.3
Mobile Measurements Data Recordings ................................................................8
2.3.1
BA List Creation for Data Collection ..............................................................8
2.3.1.1
Importing MP Export Files in XML Format................................................9
2.3.1.2
Activation of the XML CM Provisioner ................................................. 10
2.3.2
CF and DAC Recordings ............................................................................ 13
2.3.3
Retrieving Mobile Measurements Results ..................................................... 14
2.3.4
Retrieving Handover Statistics ................................................................... 15
2.4
Network Performance Statistics ........................................................................ 16
2.4.1
Network Performance Evaluation................................................................ 17
2.4.2
Radio Network Performance KPIs Calculation............................................... 17
2.4.3
Additional KPIs for Network Performance Evaluation..................................... 18
3
Data Collection Checklist..................................................................................... 20
4
Appendix............................................................................................................. 21
4.1
Initial Activation of the CF feature..................................................................... 21
4.2
Initial Activation of the DAC feature .................................................................. 22

List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure

1: Retrieve the Required BSS Network Configuration Files........................................................ 4

2: Choosing the BSCs ........................................................................................................ 5
3: Object Classes for Export ................................................................................................ 5
4: Export Target File........................................................................................................... 6
5: Open the CM Plan Manager and Change Current View to Import............................................ 9
6: Import Target File .......................................................................................................... 9
7: Import Data to New Plan ............................................................................................... 10
8: Activating the CM Provisioner......................................................................................... 10
9: Selecting Task for Activation .......................................................................................... 11
10: Select GSM Locking Allowed Feature ............................................................................. 11
11: Prompt to Activate the Operation .................................................................................. 11
12: Subplan Log .............................................................................................................. 12
13: Test Backup Feature ................................................................................................... 13
14: CF Recording ............................................................................................................. 13
15: DAC Recording ........................................................................................................... 14
16: CF Feature Activated................................................................................................... 21
17: DAC Feature Activated ................................................................................................ 22

Schema Confidential & Proprietary

page 2 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

1 Introduction
This document contains a list of all the required information and data that must be collected on
Nokia GSM infrastructures in preparation for installation of Ultima Fort.
Required information and data include the following:
o

Optimization area and optimization goals

Nokia BSS network configuration data (XML format or SQL queries format)

Sector coordinates data

Mobile measurements recordings

Performance reports

The following sections provide a more in-depth description of the required data sources and the
manner in which they can be obtained.

2 Required Information and Data

2.1 Optimization Goals and Areas
1. Optimization goal/s - a general description of the optimization goals for the intended area is
required.
2. Network area:
o

List of cells in the optimization area

List of frequencies to be used as BCCH channels

List of frequencies to be used as TCH channels

Current frequency planning strategy (1:1, 1:2, , per site, per cell, ad-hoc, )

Desired optimization strategy (1:1, 1:2, , per site, per cell, ad-hoc, )

List of cells in the guard zone

Schema Confidential & Proprietary

page 3 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

2.2 Network Data

There are two possible methods for BSS network configuration data retrieval:
1. CM Plan Manager interface (depends on availability) to XML format.
2. Predefined set of SQL queries to CM database to text tab delimited tables.
BSS network configuration should be retrieved from each OMCR relevant to the optimization
area.

2.2.1

Nokia BSS Network Configuration (Option A XML Format)

To retrieve the required BSS network configuration files from the Nokia OSS
1. Go to the CM Plan Manager (usually via Citirix, X-Terminal or OSS workstation)

2. Go to ViewExport Actuals or Ctrl+E (see figure 1 below)

Figure 1: Retrieve the Required BSS Network Configuration Files

Schema Confidential & Proprietary

page 4 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

3. Choose the BSCs in Available Objects for all cells in the optimization and guard-zone
areas. See figure 2 below.

Figure 2: Choosing the BSCs

4. In the Object Classes for Export section, click the Select All icon to select all parameters.

Figure 3: Object Classes for Export

Schema Confidential & Proprietary

page 5 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

5. Click Select (figure 3 above) to select the location to save the XML file.

Figure 4: Export Target File

6. Use the Export button to start the export process.

2.2.2

Nokia BSS Network Configuration (Option B Queries Format)

The required BSS network configuration files can be retrieved from the Nokia CM database
through running Perl script provided by Schema. This generated output will contain set text
files with the BSS network configuration. The script automatically generates SQL queries for
retrieval of the required data from Nokias Oracle database as follows:
1. Open a binary FTP session to the Nokia OSS machine.
2. Upload the script file NokiaNetConfig.pl to a directory with R/W permissions.
3. Activate the script by using the following command in Unix:
> perl NokiaNetConfig.pl
4. FTP (in binary mode) the 10 newly created text files.
Note: the Perl script uses a direct connection to the Oracle database. The user will be asked to
login and provide a password on starting the process.

Schema Confidential & Proprietary

page 6 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

2.2.3

Sector Coordinates File

The sector coordinates file must be in tab delimited text file format with geographical
information for all the sectors in the optimization area and the guard-zone area.
The file should contain the following columns:
o

Sector

Latitude

Longitude

Azimuth

The sector name is supposed to be unique per network.

2.2.4

Traffic File

The traffic file should be in the format of a tab delimited text file with traffic information for all
the sectors in the optimization area and the guard-zone area.
The file should contain the following columns:
o

Date (in ddmmyyy format)

Hour (in hh format)

Sector

Traffic (carried traffic in Erlang)

The file should contain traffic information for 5 consecutive working days and should preferably
be produced on the last day of the DAC and CF recordings.
The traffic file can be retrieved from the Nokia PM database by using an SQL query. The
required SQL query can be provided by Schema Customer Support. In order to retrieve the
traffic data from the Nokia Oracle database, use the following procedure:
1. Open a binary FTP session to the Nokia OSS machine.
2. Upload the traffic.sql file to a directory with R/W permissions.
3. Activate the SQL query by using the following command:
sqlplus username/password @filename (e.g. sqlplus omc/omc @traffic.sql)
4. FTP (in binary mode) the newly created text file (traffic.txt).

Schema Confidential & Proprietary

page 7 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

2.3 Mobile Measurements Data Recordings

A network freeze is strongly recommended during the recording time frame.
The following activities should be halted during data recordings:
o

BSC split

Site reparenting (BSC/site relations change)

Changes of LAC and CI

Site additions

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 the maintenance window (not while
recording is taking place):
o

TRX additions

Frequency changes (TCH)

All other parameters should not be changed.

Note: Version of BSC must be S10.5 or later.

2.3.1

BA List Creation for Data Collection

The Defined Adjacent Cell and Channel Finder measurements collect signal strength and
C/I data that are reported by the mobiles in the MAHO report.
In order to collect information on BCCH channels that are not in the adjacent cell list, it is
necessary to define a new BCCH allocation list, which contains all BCCHs that should be
measured, and assign this BA list for each BTS.
This makes use of the Double BCCH Allocation List feature. This feature provides the mobile
the user-defined frequency list for measurements. This user-defined list should contain all
BCCH frequencies that belong to the defined neighbors and additional frequencies that should
be measured. This will have no impact on handover performance.
The Ultima Fort Measurement Plan functionality should be used for the collection of
reliable data for network modeling. The Measurement Plan functionality provides frequency
allocation for each sector BA list.

Schema Confidential & Proprietary

page 8 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

2.3.1.1

Importing MP Export Files in XML Format

Browse to the MP export directory of UltimaFortNokia Measurement Plan\Day_X and

import (using the CM Plan Manager) one after another all 4 files. Each file should be imported
into its own plan (01_Disassociate_BAL.xml, 02_Delete_BAL.xml, 03_Create_BAL.xml,
04_Associate_BAL.xml).

1. Open the CM Plan Manager and change Current View to Import as shown in figure 5
below.

Figure 5: Open the CM Plan Manager and Change Current View to Import
2. Browse to the proper directory and select the .xml files to import.

Figure 6: Import Target File

Schema Confidential & Proprietary

page 9 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

3. Name your plan and click on Start.

Figure 7: Import Data to New Plan

2.3.1.2

Activation of the XML CM Provisioner

In order to activate the plan you have imported (the BA list rotation) access the Provisioner
and activate it.
1. Activate CM Provisioner.

Figure 8: Activating the CM Provisioner

Schema Confidential & Proprietary

page 10 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

2. Select the proper task which you want to activate.

Figure 9: Selecting Task for Activation

3. Select GSM Locking Allowed with 10sec limit and click on Start Operation.

Figure 10: Select GSM Locking Allowed Feature

4. Click on Continue.

Figure 11: Prompt to Activate the Operation

Schema Confidential & Proprietary

page 11 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

5. The Subplan Log will appear.

Figure 12: Subplan Log

6. XML successful implementation will be terminated when the State: Finished message
appears.
7. IMPORTANT NOTE: In order to roll back, an automatic back up is created and can be
activated if necessary. See figure 13 below.

Schema Confidential & Proprietary

page 12 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

Figure 13: Test Backup Feature

2.3.2

CF and DAC Recordings

CF and DAC recordings should be performed over consecutive working days for the same time
frame. The validation of DAC and CF features status is mentioned in the Appendix.
Use the following MML commands to view the criteria currently defined in the BSC for DAC and
CF recordings:

For CF: ZTPI:MEASUR,CHAN_FIN

Figure 14: CF Recording

Schema Confidential & Proprietary

page 13 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

For DAC: ZTPI:MEASUR,DAC

Figure 15: DAC Recording

Use the following MML commands to start/modify the CF and DAC recordings:
1. ZTPM:MEASUR,CHAN_FIN:ALL,09002100,4:DB1=-12,DB2=0; - defines CF
measurements to start at 09:00 and finish at 21:00 daily with 4 hours resolution.
2. ZTPS:MEASUR,CHAN_FIN; - starts the CF measurement.
3. ZTPM:MEASUR,DAC:ALL,09002100,4:DB1=-12,DB2=0; - defines the DAC measurement
to start at 09:00 and finish at 21:00 daily with 4 hours resolution.
4. ZTPS:MEASUR,DAC; - starts the measurement.
Note: The thresholds used for recordings (between class 1, class 2 and class 3 measurements)
should be the same thresholds to all sectors and BSCs in the DAC and CF files!

2.3.3

Retrieving Mobile Measurements Results

The required mobile measurements results can be retrieved from the Nokia PM database by
running Perl script provided by Schema. This generated output will contain set text files with
required data. The script automatically generates SQL queries for the data retrieval from the
Nokias Oracle database:
1. Open a binary FTP session to the Nokia OSS machine.
2. Upload the script file NokiaMS.pl to a directory with R/W permissions.
3. Activate the script by using the following command in Unix: >perl NokiaMS.pl
4. FTP (in binary mode) the 3 newly created text files.

Schema Confidential & Proprietary

page 14 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

Note: the Perl script uses a direct connection to the Oracle database. The user will be asked to
login and provide a password on starting the process.
The script will generate 3 files for each recording day:
o

CF (Channel Finder measurements)

DAC (Defined Adjacent Cell measurements)

Rx Statistics (Rxlevel and RxQuality measurements)

The BSS network configuration files must be retrieved per each day of the mobile
measurements recordings as described in section 2.2 above.

2.3.4

Retrieving Handover Statistics

For handover optimization purposes the handover statistics per cell-to-cell relation should be
collected. The data should be aggregated over one week and provided in a tab delimited text
file with the following fields:
o

Serving Sector

Target Sector

Handover (HO) Attempts

The required handover statistics file can be retrieved from the Nokia PM database by using an
SQL query. The required SQL query will be provided by Schema Customer Support. In order to
retrieve handover data from the Nokia Oracle database, use the following procedure:
8. Open a binary FTP session to the Nokia OSS machine.
9. Upload the ho_adj.sql file to a directory with R/W permissions.
10. Activate the SQL files by using the following command:
sqlplus username/password @filename (e.g. sqlplus omc/omc @ho_adj.sql)
11. FTP (in binary mode) the newly created text file (ho.txt).
The created ho_adj.txt file can be imported directly to Ultima Fort.

Schema Confidential & Proprietary

page 15 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

2.4 Network Performance Statistics

Network performance statistics should be collected for the purpose of network traffic modeling
and post-optimization network performance benchmarking.
The following performance statistics should be collected on a per cell basis with hourly
resolution over 7 consecutive days:
o

SDCCH Assignments (immediate assignment attempts and failures):

sdcch_assign, t3101_expired, sdcch_req, sdcch_seiz_att, sdcch_ho_seiz, setup_succ,
call_setup_failure, succ_seiz_term, succ_seiz_orig, sdcch_loc_upd, succ_emerg_call,
sdcch_call_re_est, imsi_detach_sdcch, msc_i_sdcch, bsc_i_sdcch

MSDCCH Traffic:
ave_busy_sdcch, res_av_denom15

SDCCH Performance (drop, drop reason):

sdcch_radio_fail, sdcch_rf_old_ho, sdcch_abis_fail_call, sdcch_abis_fail_old,
sdcch_a_if_fail_call, sdcch_a_if_fail_old, sdcch_lapd_fail, sdcch_bts_fail, sdcch_bcsu_reset,
sdcch_user_act, sdcch_netw_act

TCH Assignments (TCH assignment attempts and failures):

tch_norm_seiz, ms_tch_succ_seiz_assign_cmplt, tch_req_rej_lack

TCH Traffic:
ave_busy_tch, res_av_denom14, ave_tch_busy_full, ave_tch_busy_half

TCH Performance (drop, drop reason):

tch_radio_fail, tch_rf_old_ho, tch_abis_fail_call, tch_abis_fail_old, tch_a_if_fail_call,
tch_a_if_fail_old, tch_tr_fail, tch_tr_fail_old, tch_lapd_fail, tch_bts_fail, tch_user_act,
tch_bcsu_reset, tch_netw_act, tch_act_fail_call

TCH Rx Quality Performance:

freq_dl_qual0 freq_dl_qual0, freq_ul_qual0 freq_ul_qual0

The following performance statistics should be collected on a per cell (cell relation) basis with
daily resolution over 7 consecutive days.
o

HO Performance (cell relation):

ho_att_to_adj, ho_succ_to_adj, ho_fail_res_to_adj, ho_att_from_adj, ho_succ_from_adj,
ho_fail_res_from_adj

Schema Confidential & Proprietary

page 16 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

HO Performance (cell):
cell_tch_tch, bsc_o_tch_tch, msc_o_sdcch_tch
cause_up_qual, cause_up_level, cause_down_qual, cause_down_lev, cause_distance,
cause_msc_invoc, cause_intfer_up, cause_intfer_dwn, cause_umbr, cause_pbdgt,
cause_omc, cause_ch_adm, cause_traffic, cause_dir_retry, cause_pre_emption,
cause_field_drop, cause_low_distance, cause_bad_ci, cause_good_ci

2.4.1

Network Performance Evaluation

Each KPI improvement rate will be calculated as:

KPI _ improvemen t _ rate =

KPI before KPI new

KPI before

100%

For success rate KPIs (SDCCH/TCH Setup, HO) the improvement will be calculated as:

KPI _ Success _ improvemen t _ rate =

KPI before KPI new

1 KPI before

100%

Each KPI will be calculated for improvement rates separately over working 5 days (24 hours or
a selected hours range) before and after optimization. Network performance KPIs that are not
related to the BSS subsystem will be excluded from the calculation.

2.4.2

Radio Network Performance KPIs Calculation

The following calculations will be used for KPIs proposed for radio network performance
evaluation:

SDCCH _ Drop _ Rate _ Radio =

TCH _ Drop _ Rate _ Radio =

(sdcch_radio_fail + sdcch_rf_old_ho)

succ_seiz_term + succ_seiz_orig + sdcch_call_re_est +

+ sdcch_emerg_call + sdcch_loc_upd + sdcch_imsi_detach +

+ msc_i_sdcch + bsc_i_sdcch

(tch_radio_fail + tch_rf_old_ho )

ms_tch_succ_seiz_assign_cmplt -

- cell_tch_tch - bsc_o_tch_tch - msc_o_sdcch_tch

Schema Confidential & Proprietary

page 17 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

ave_busy_tch

TCH _ Erlang _ to _ Drop _ Radio =

res_av_denom14

(
tch_radio_
fail
tch_rf_old
_ho)
+

TCH _ Bad _ Quality _ DL =

freq_dl_qualX
x =5
7

freq_dl_qualX
x =0

TCH _ Bad _ Quality _ UL =

freq_ul_qualX
x =5
7

freq_ul_qualX
x =0

Outgoing _ HO _ Success _ Rate =

(ho_succ_to_adj)

(ho_att_to_adj - ho_fail_res_to_adj)

Notes:
The calculations mentioned above do not include drops that occur due to BSS problems such as
transmission, BSC, TRAU, MSC.

2.4.3

Additional KPIs for Network Performance Evaluation

The following calculations provide additional KPIs for network performance evaluation:

SDCCH _ Assignment _ Success =

Schema Confidential & Proprietary

(sdcch_assign )
(sdcch_seiz_att )

page 18 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

SDCCH _ Drop _ Rate =

TCH _ Drop _ Rate =

sdcch_radio_fail + sdcch_rf_old_ho + sdcch_abis_fail_call +

+ sdcch_abis_fail_old + sdcch_a_if_fail_call + sdcch_a_if_fail_old +

+ sdcch_lapd_fail + sdcch_bts_fail + sdcch_bcsu_reset +

+ sdcch_user_act + sdcch_netw_act

succ_seiz_term + succ_seiz_orig + sdcch_call_re_est +

+ sdcch_emerg_call + sdcch_loc_upd + sdcch_imsi_detach +

+ msc_i_sdcch + bsc_i_sdcch

tch_radio_fail + tch_rf_old_ho + tch_abis_fail_call + tch_abis_fail_old +

+ tch_a_if_fail_call + tch_a_if_fail_old + tch_tr_fail + tch_tr_fail_old +

+ tch_lapd_fail + tch_bts_fail + tch_user_act + tch_bcsu_reset +

+ tch_netw_act + tch_act_fail_call

ms_tch_succ_seiz_assign_cmplt -

- cell_tch_tch - bsc_o_tch_tch - msc_o_sdcch_tch

ave_busy_tch

TCH _ Erlang _ to _ Drop =

res_av_denom14

tch_radio_fail + tch_rf_old_ho + tch_abis_fail_call +

tch_abis_fail_old + tch_a_if_fail_call + tch_a_if_fail_old +

tch_tr_fail + tch_tr_fail_old + tch_lapd_fail + tch_bts_fail +

tch_user_act + tch_bcsu_reset + tch_netw_act + tch_act_fail_call

ave_busy_sdcch

SDCCH _ Traffic =
res_av_denom15
ave_busy_tch

TCH _ Traffic =
res_av_denom14

TCH _ Traffic _ FR = (ave_tch_busy_full)

TCH _ Traffic _ HR = (ave_tch_bu sy_half )

HO _ Cause =

(cause_X)

cause_up_qual + cause_up_level + cause_down_qual + cause_down_lev +

+ cause_distance + +cause_msc_invoc + cause_intfer_up + cause_intfer_dwn +

+ cause_umbr + cause_pbdgt + cause_omc + cause_ch_adm + cause_traffic +
+ cause_dir_retry + cause_pre_emption + cause_field_drop +

+ cause_low_distance + cause_bad_CI + cause_good_CI

Schema Confidential & Proprietary

page 19 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

3 Data Collection Checklist

SOURCE

COMMENTS

CHECK

Network Data
BSS Network Configuration
(XML)
BSS Network Configuration
(SQL)
Sector Coordinates File
Traffic File
Mobile Measurements Recordings
Day 1

Day 2

Day 3

Day 4

Day 5

CF Files
DAC Files
RxStatistics Files
BSS Network Configuration
(XML)
BSS Network Configuration
(SQL)
Network Performance Statistics
SDCCH Assignments
SDCCH Traffic
SDCCH Performance
TCH Assignments
TCH Traffic
TCH Performance
TCH Rx Quality
Handover (HO) Performance
per Cell Relation
HO Performance per Cell

Schema Confidential & Proprietary

Immediate assignments attempts

Immediate assignments failures
SDCCH traffic per cell
SDCCH congestion
SDCCH drop
SDCCH drop reason
TCH assignment attempts
TCH assignment failures
Traffic per cell
Traffic FR/HR
Drops
Drops per reason
Rx Quality DL
Rx Quality UL
HO attempts
HO success

HO types
HO reasons

page 20 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

4 Appendix
4.1 Initial Activation of the CF feature
The first step is to log into the BSC. The CF feature should be activated on each BSC to be
measured.
Use the following command from the OSS/NMS to login to a BSC:
C7xtermx n bsc_name
In order to verify that the CF feature is activated on the BSC perform the following MML
command:
ZWOI:10,65
The printout will show whether the CF feature is activated or not. 00FF means the feature is
activated (as displayed in figure 16 below), while 0000 means it is disabled.

Figure 16: CF Feature Activated

Use the following command for CF activation in case it is not active:

ZWOC:10,65,FF

Schema Confidential & Proprietary

page 21 of 22

Ultima Fort Required Data Inputs for Nokia Infrastructure

4.2 Initial Activation of the DAC feature

The first step is to log into the BSC. The DAC feature should be activated on each BSC to be
measured.
Use the following command from the OSS/NMS to login to a BSC:
C7xtermx n bsc_name
In order to verify that the DAC feature is activated on BSC, perform the following MML
command:
ZWOS:2,626
The printout will show whether the DAC feature is activated or not.
When the Activation Status equals to Activated, the DAC feature is activated as in figure 17
below.

Figure 17: DAC Feature Activated

Use the following command for DAC activation in case it is not active:

ZWOA:2,626,A

Schema Confidential & Proprietary

page 22 of 22