Ultima Fort Required Data Inputs for Alcatel

Infrastructure

Ultima Fort
Required Data Inputs
for

Alcatel Infrastructure
(appropriate for Ultima Fort v 3.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 19

Ultima Fort Required Data Inputs for Alcatel 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
Alcatel BSS Network Configuration .......................................................... 4
2.2.2
Sector Coordinates File.......................................................................... 8
2.2.3
Traffic File ........................................................................................... 8
2.3
Mobile Measurements Data Collection............................................................. 9
2.3.1
BA List Creation for RMS Data Collection .................................................. 9
2.3.2
RMS Data Collection............................................................................ 11
2.3.3
Retrieving the RMS Results .................................................................. 14
2.3.4
Retrieving Handover Statistics .............................................................. 15
2.4
Network Performance Statistics ................................................................... 15
2.4.1
Network Performance Evaluation........................................................... 16
2.4.2
Radio Network Performance KPIs Calculation ......................................... 16
2.4.3
Additional KPIs for Network Performance Evaluation ............................... 17
3
Data Collection Checklist....................................................................................18
4
Appendix ...........................................................................................................19

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

1: Start RNUSM .............................................................................................. 5

2: Select RNUSM Configuration ......................................................................... 5
3: Selected Directory Number........................................................................... 6
4: Click on Export ........................................................................................... 6
5: Click on Free .............................................................................................. 7
6: Export Process ........................................................................................... 7
7: Activating RNUSM ..................................................................................... 10
8: Selecting Population / Import ..................................................................... 10
9: Supervised Configuration ........................................................................... 11
10: Defining the Template (1) ........................................................................ 11
11: Defining the Template (2) ........................................................................ 12
12: Consistency Check Report ........................................................................ 12
13: Selecting Cell Parameters ......................................................................... 13
14: Login to UFM .......................................................................................... 13
15: Provide Period for RMS Aggregation ........................................................... 14
16: Selecting Alignment Status ....................................................................... 19
17: Misaligned Cell........................................................................................ 19

Schema Confidential & Proprietary

page 2 of 19

Ultima Fort Required Data Inputs for Alcatel Infrastructure

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

Optimization area and optimization goals

Alcatel BSS network configuration data

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 (if any)

Schema Confidential & Proprietary

page 3 of 19

Ultima Fort Required Data Inputs for Alcatel Infrastructure

2.2 Network Data

2.2.1

Alcatel BSS Network Configuration

The required BSS network configuration data can be retrieved from each of the Alcatel
OMCRs. The created file set contains the following files:
o

Adjacency.csv

Cell.csv

ExernalOmcCell.csv

HoControl.csv

RnlAlcatelBSC.csv

RnlAlcatelMFS.csv

RnlAlcatelSector.csv

RnlAlcatelSiteManager.csv

RnlBasebandTranceiver.csv

RnlFrequencyHoppingSystem.csv

RnlPowerControl.csv

SubNetwork.csv

There is an automatic process at the Alcatel OMCR, which provides for the retrieval of the
required file set at the time defined by the customer.
Prior to retrieving data, the BSS network configuration audit should be performed. Any
discovered data inconsistencies should be solved according to the procedure in Appendix A.
The procedure for manually retrieving the required file set is shown below:
1. Login to OMCR.
2. Click on Network.
3. Start RNUSM. See figure 1 below.

Schema Confidential & Proprietary

page 4 of 19

Ultima Fort Required Data Inputs for Alcatel Infrastructure

Network

RNUSM

Figure 1: Start RNUSM

4. Select Configuration/Export in the RNUSM window:

:
Figure 2: Select RNUSM Configuration

5. The Alcatel OMCR has 10 predefined directories for Export. The required file set will be
stored under the selected Directory Number (see figure 3 below). This directory should
be defined when the OMC is configured.

Schema Confidential & Proprietary

page 5 of 19

Ultima Fort Required Data Inputs for Alcatel Infrastructure

Figure 3: Selected Directory Number

6. Select a Supervised Configuration Item with Directory Status defined as Idle.

7. Click on Export.

Figure 4: Click on Export

8. If there are no Idle items, select a Supervised Configuration Item with Directory Status
defined as Ready. Click on Free when it appears (see figure 5 below). This will remove
the old data from the specified directory.

Schema Confidential & Proprietary

page 6 of 19

Ultima Fort Required Data Inputs for Alcatel Infrastructure

Figure 5: Click on Free

9. When the directory status has changed to Ready, click on Export. The window in figure
6 below will appear, presenting the Export process.

Figure 6: Export Process

The required file set will be placed in the specified directory:

For release B7 and B8:

/Alcatel/var/share/AFTR/ACIE/ACIE_NLExport_Dir1 (up to _Dir10)

For release R9:

/ACIE/ACIE_NLExport_Dir1 (up to _Dir10)

Schema Confidential & Proprietary

page 7 of 19

Ultima Fort Required Data Inputs for Alcatel Infrastructure

2.2.2

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

LAC (optional)

CI (optional)

The sector name is supposed to be unique per network.

LAC and CI values are optional in the case when the Sector field values match the User
Label field values in the Cell table in the BSS network configuration dump.
When Sector values do not match the BSS network configuration dump values, then LAC
and CI values should be provided in order to be able to match geographical locations with
network elements.

2.2.3

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 RMS recordings.
The processing of this data should be performed in order to comply with specific network
optimization requirements. The processed data should comply with the Schema-defined
format.

Schema Confidential & Proprietary

page 8 of 19

Ultima Fort Required Data Inputs for Alcatel Infrastructure

2.3 Mobile Measurements Data Collection

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

BSC split

Site rehoming (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 B7.2 or later.

2.3.1

BA List Creation for RMS Data Collection

The Ultima Fort functionality Measurement Plan should be used for the collection of
reliable data for network modeling. The Measurement Plan functionality provides
frequency allocation for each sector BA list. The following procedure should be implemented
in order to upload the required network definitions for BA lists creation:
1. The Measurement Plan functionality will create the command set for BA list updates:
o

ExternalOmcCell_Create.csv

Adjacency_Add.csv

SubNetwork.csv

2. Copy these command files to specified directories on OMCR by using FTP (make sure the
transfer is in ASCII mode):

For R7,R8:
o

/Alcatel/var/share/AFTR/ACIE/ACIE_NLImport_Dir1(_Dir10) - use relevant

directory

For R9:
o

/ACIE/ACIE_NLImport_Dir1(_Dir10) ) - use relevant directory

3. Activate RNUSM. See figure 7 below.

Schema Confidential & Proprietary

page 9 of 19

Ultima Fort Required Data Inputs for Alcatel Infrastructure

Figure 7: Activating RNUSM

4. Select Configuration/Create PRC - a new PRC will open. Provide a name for the PRC.
5. Select Population/Import.

Figure 8: Selecting Population / Import

6. Select the relevant folder with recently created command files.

7. Check the uploaded configuration by selecting Activation/Check. If you get any
warnings or errors do NOT proceed with Activation, before you either solve the
problems or you are sure you understand what the warnings or errors mean. In case you
dont understand them please contact Customer Support for further help.

Schema Confidential & Proprietary

page 10 of 19

Ultima Fort Required Data Inputs for Alcatel Infrastructure

Figure 9: Supervised Configuration

8. For implementation in the live network select Activation -> Activate PRC.
9. The same procedure should be performed for all other recording days with relevant
configuration data for upload. The upload should be performed prior to starting the RMS
recording.

2.3.2

RMS Data Collection

In order to collect the required data for network modeling the RMS statistics should be
activated in the network. The RMS template should be created for RMS data collection
process activation. The template contains the set of tables with different parameters that
can be changed. For template definition perform the following actions:
1. Login to the OMCR.
2. Activate RNUSM.
3. Open PRC.

Figure 10: Defining the Template (1)

Schema Confidential & Proprietary

page 11 of 19

Ultima Fort Required Data Inputs for Alcatel Infrastructure

4. Select the required BSCs by using a filter and then define a Template -> Show RMS
Template.
5. Define the parameters for the template according to figures 11 & 12 below. The most
important parameters for Ultima Fort are: C/I and RxLevel thresholds.

Figure 11: Defining the Template (2)

6. The recently created template should be checked for consistency and be error-free prior
to activation. A consistency check is performed by selecting Activation/Check without
forcing the administrative state. A report will be displayed upon consistency check
completion (see figure 12 below). If errors appear in this report the template should be
corrected. In case of no errors, select Activation/Activate without forcing.

Figure 12: Consistency Check Report

Schema Confidential & Proprietary

page 12 of 19

Ultima Fort Required Data Inputs for Alcatel Infrastructure

7. For all sectors under the selected BSC apply the appropriate template by selecting Cell
Parameters/ RMS&MAFA/ RMS_Template (see figure 13 below).

Figure 13: Selecting Cell Parameters

8. Click on Activation -> Activate PRC.

The RMS Data Aggregation Period should be defined after the RMS Template creation.
To define this period the following procedure should be followed:
1. Login to the OMCR.
2. Activate UFM and provide Login to UFM.

Figure 14: Login to UFM

Schema Confidential & Proprietary

page 13 of 19

Ultima Fort Required Data Inputs for Alcatel Infrastructure

3. Click on PMC.
4. In the following dialog define the required period for RMS aggregation:

Existing RMS period

Click on PMC

Apply

RMS period definition

Figure 15: Provide Period for RMS Aggregation

5. Define the appropriate time frame for RMS aggregation (the recommended period is
between 3 to 6 hours around a network busy hour).
6. Apply definitions.

2.3.3

Retrieving the RMS Results

The required RMS results can be retrieved from the Alcatel directory. The RMS files are
located in a predefined directory.
Binary PRMS files in releases R7 and R8 are located at the OMCR in the following directory:
o

/alcatel/var/share/AFTR/APME/BSC

Note:
When PRMS files are transferred from Unix to Windows by using FTP, the transfer method
should be defined as Binary.
All PRMS files recorded on the same day should be stored in the same directory.
The name file convention for RMS files is as follows:
o
o
o
o

Statistics type PMRES-31

BSC name - BSC_11
Recording date 2005-09-13
Binary file name example:
PMRES-31.82A.3.1BSC_11.2005-09-13.20:06:26.5277.103

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

Schema Confidential & Proprietary

page 14 of 19

Ultima Fort Required Data Inputs for Alcatel Infrastructure

2.3.4

Retrieving Handover Statistics

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

Serving Sector

Target Sector

Handover Attempts

The following statistical counter should be used:

C720 NB_ADJ_SCELL_OUT_TCH_HO_ATPT

This counter aggregates the number of outgoing handover attempts per adjacency.

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

MC703, MC812, MC718, MC717a, MC717b, MC662

TCH Traffic:

MC138, MC07, MC137

TCH Assignments (TCH assignment attempts and failures):

MC400, MC390

SDCCH Performance (drop, drop reason):

MC148, MC04, MC147, MC81, MC91, MC101, MC01, MC02, MC10

MC380a, MC380b

TCH Performance (drop, drop reason):

MC736, MC621, MC14c, MC739

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

Handover Performance (cell relation):

C720, C721, C722, C723

Handover Performance (cell):

MC670, MC671, MC672, MC673, MC674, MC676, MC677, MC678, MC646,

MC656, MC650, MC660

Schema Confidential & Proprietary

page 15 of 19

Ultima Fort Required Data Inputs for Alcatel Infrastructure

2.4.1

Network Performance Evaluation

Each KPI improvement rate will be calculated as:

KPI _ improvement _ rate =

KPI before KPI new

KPI before

100%

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

KPI _ Success _ improvement _ rate =

KPI before KPI new

1 KPI before

100%

Each KPI will be calculated for improvement rate 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 =

( MC138 + MC 07)
( MC 01 + MC 02)

( MC 736 + MC 621)

TCH _ Drop _ Rate _ Radio =

(MC 718 + MC 717a + MC 717b MC 662)

(MC 736 + MC 621)
Call _ Drop _ Rate _ Radio =
(MC 718 + MC 717a)

TCH _ Erlang _ to _ Drop _ Radio =

(MC380a + MC380b)
(MC 736 + MC 621)

TCH _ Bad _ Quality _ DL =

RMS 4a
x =5
7

RMS 4a
x =0

TCH _ Bad _ Quality _ UL =

RMS 3a
x =5
7

RMS 3a
x =0

Outgoing _ HO _ Success _ Rate =

(MC 646 + MC 656)

(MC 650 + MC 660)

Notes:
The calculations mentioned above do not include drops that occur due to BSS problems such
as: transmission, BSC, TRAU, MSC.
The Bad_Quality statistics will be retrieved from RMS data directly.

Schema Confidential & Proprietary

page 16 of 19

Ultima Fort Required Data Inputs for Alcatel Infrastructure

2.4.3

Additional KPIs for Network Performance Evaluation

The following calculations provide additional KPIs for network performance evaluation:

SDCCH _ Assignment _ Success =

(MC 01 + MC 02 + MC10)

( MC148 + MC 04 + MC147 + MC81 + MC 91 + MC101)

( MC138 + MC 07 + MC137)
( MC 01 + MC 02)
(MC 718)
TCH _ Assignment _ Success =
(
MC
703 + MC812)
(MC 736 + MC 621 + MC14c + MC 739)
TCH _ Drop _ Rate =
(MC 718 + MC 717a + MC 717b MC 662)
(MC 736 + MC 621 + MC14c + MC 739)
Call _ Drop _ Rate =
(MC 718 + MC 717a)
(MC380a + MC380b)
TCH _ Erlang _ to _ Drop =
(MC 736 + MC 621 + MC14c + MC 739)
(MC 400)
SDCCH _ Traffic =
SDCCH _ Drop _ Rate =

3600

TCH _ Traffic =

(MC380a + MC380b)
3600

TCH _ Traffic _ FR =

(MC 380a)

TCH _ Traffic _ HR =

(MC 380b)

HO _ Cause =

3600

3600

(MC 67 x)

( MC 670 + MC 671 + MC 672 + MC 673 + MC 674 + MC 676 + MC 677 + MC 678)

Schema Confidential & Proprietary

page 17 of 19

Ultima Fort Required Data Inputs for Alcatel 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

PRMS Files
BSS Network Configuration
Network Performance Statistics
SDCCH Assignments
SDCCH Traffic
SDCCH Performance
TCH Assignments
TCH Traffic
TCH Performance
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
HO attempts
HO success
HO reversion
HO drop
HO reasons
HO attempts
HO success

page 18 of 19

Ultima Fort Required Data Inputs for Alcatel Infrastructure

4 Appendix
This Appendix contains the procedure for configuration database alignment (Force Config)
in the case where data inconsistencies have been discovered.
The procedure for performing the following file set is shown below:
1. Start RNUSM.
2. Select Cell Filter.
3. Select Alignment Status Misaligned.

Figure 16: Selecting Alignment Status

4. For a misaligned cell activate Force Config:

Figure 17: Misaligned Cell

Schema Confidential & Proprietary

page 19 of 19