You are on page 1of 16

Ultima Fort Required Data Inputs for Siemens Infrastructure

Ultima Fort
Required Data Inputs for Siemens
Infrastructure
(for Version 4.0 and above)
Copyright Notice
Due to a policy of continuous product development and refinement, Schema reserves the right to alter the
specifications and descriptions outlined in this publication without giving prior notice of any kind. In addition,
no part of this publication, taken as a whole or separately, shall be deemed to be part of any contract for
equipment or services.
Schema retains the sole proprietary rights to all information contained in this document. No part of this
publication may be reproduced, stored in a retrieval system, transmitted in any form or by any means,
including but not limited to: electronic, mechanical, magnetic, photocopy, recording, or otherwise, in use now
or in the future, without prior written consent from Schema.

Copyright 2008 Schema

May 08
Schema

Proprietary and Confidential

1 of 16

Ultima Fort Required Data Inputs for Siemens Infrastructure

Table of Contents
1

Introduction.............................................................................................. 4

Required Information and Data................................................................. 5


2.1

Optimization Area ...........................................................................................5

2.2

Network Configuration.....................................................................................5
2.2.1 Siemens BSS Network Configuration Data Retrieval ...................................5
2.2.2 Sector Coordinates File ..........................................................................6

2.3

Mobile Measurements Data Recordings ..............................................................6


2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7

2.4

BA List Creation for SCA Data Collection...................................................7


SCA Data Collection ..............................................................................7
SCA Data Collection Cleanup ..................................................................7
Running Command Files ........................................................................8
Retrieving SCA Results ........................................................................ 10
Traffic File ......................................................................................... 10
Handover Statistics ............................................................................. 11

Network Performance Statistics ...................................................................... 11


2.4.1 Network Performance Evaluation........................................................... 12
2.4.2 Radio Network Performance KPI Calculation............................................ 12
2.4.3 Additional KPIs for Network Performance Evaluation ................................ 13

Data Collection Checklist......................................................................... 15

May 08
Schema

Proprietary and Confidential

2 of 16

Ultima Fort Required Data Inputs for Siemens Infrastructure

Table of Figures
Figure 1: Radio Commander Application ...........................................................................8
Figure 2: Command Line Interface ...................................................................................8
Figure 3: Command History Tool .....................................................................................9

May 08
Schema

Proprietary and Confidential

3 of 16

Ultima Fort Required Data Inputs for Siemens Infrastructure

Introduction

This document contains a list of the information and data to be collected for Siemens GSM
infrastructures in order to perform an optimization cycle using Ultima Fort.
The following information is required:

Optimization area and optimization goals

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

May 08
Schema

Proprietary and Confidential

4 of 16

Ultima Fort Required Data Inputs for Siemens Infrastructure

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
2.2.1

Network Configuration
Siemens BSS Network Configuration Data Retrieval

The required BSS network configuration data should be retrieved from every Siemens OMCR.
Each created file set should contain configuration files for all BSCs in ASCII format with the
*.asc extension.
Notes:

The BSS network configuration data upload is performed automatically (e.g., every 6 hours
or once a day, depending on local definitions).

The most updated BSS network configuration data must be obtained before the
Measurement Plan (for modeling data collection) is created.

Network activities should stop before the upload process begins.

May 08
Schema

Proprietary and Confidential

5 of 16

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

CI

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 Measurements Data Recordings

The following network activities should stop while data is being recorded:

BSC split

Site re-homing (BSC/site relations change)

Changes in LAC and CI

Sector mechanical changes, such as tilt, azimuth, and antenna

Frequency changes (BCCH and BSIC)

Neighbor additions or deletions

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

TRX additions

Frequency changes (TCH)

Site additions

No other parameters should be changed.

May 08
Schema

Proprietary and Confidential

6 of 16

Ultima Fort Required Data Inputs for Siemens Infrastructure

Notes:

The BSC must be Version BR6 or a later version.

Since a BAL rotation is required, due to Siemens SCA limitations, and only part of the BCCH
spectrum is measured daily, only partial data will be collected for sites added during the
measurement period.

2.3.1

BA List Creation for SCA Data Collection

The Fort Measurement Plan functionality helps collect reliable data for network modeling, as it
provides frequency allocation for each sector BA list and creates the prepare.cli command file
for BA list updates. This file is located in the Day 0 directory, as specified in the Measurement
Plan.
To implement scripts in the network:
1. Open an FTP session (ASCII).
2. Upload the files to a work folder.
3. If needed, convert special characters from the DOS/WIN platform to UNIX, using the
command:

dos2unix </folder/filename.cli> </folder/filename.cli>

2.3.2

SCA Data Collection

The Fort Measurement Plan functionality creates the following command files for SCA data
collection, activation, and termination, with BA list updates for each day of SCA data collection:

setup.cli

reset.cli

The command set in the setup.cli file should be implemented before beginning SCA data
collection. The command set in the reset.cli file should be implemented after completing SCA
data collection.

2.3.3

SCA Data Collection Cleanup

The Fort Measurement Plan functionality creates a prepare.cli command set to clean up BA
list updates when the SCA data collection process is over.
This file, located in the Day X (last day) directory, should be used to clean up network
configuration.

May 08
Schema

Proprietary and Confidential

7 of 16

Ultima Fort Required Data Inputs for Siemens Infrastructure

2.3.4

Running Command Files

After preparing command files, required changes/activation should be implemented as follows:


1. Move the command file to the OMCR, using FTP.
2. Open the Radio Commander application, shown in Figure 1.

Figure 1: Radio Commander Application


3. Activate the Command Line Interface (CLI - part of the Radio-Commander), shown in
Figure 2.

Figure 2: Command Line Interface

May 08
Schema

Proprietary and Confidential

8 of 16

Ultima Fort Required Data Inputs for Siemens Infrastructure

4. Change to the directory containing the required .cli files.


5. For each command file:
a. Change the file mode to:
chmod +x </folder/filename.cli>
b. Execute the commands using:
</folder/filename.cli> | tee </folder/responseFileName>
Note: The CLIINOUTLOOP.LUC command can also be used:
cliinoutloop.luc -X prepare.cli > prepare.txt
The following example illustrates how to run all commands from prepare.cli and how to create
the prepare.txt log file.
A log of the command responses is in the log file. The response file should be used to check
whether commands have succeeded or failed. Any failed commands should be rerun. The
Command History tool helps track command statuses, as shown in Figure 3.

Figure 3: Command History Tool

May 08
Schema

Proprietary and Confidential

9 of 16

Ultima Fort Required Data Inputs for Siemens Infrastructure

Command files created by a Measurement Plan should be run in the following order:

Day 0:
o

prepare.cli

setSymbolicNames.cli (optional)

setup.cli (before SCA recordings start)

reset.cli (after SCA recordings are over)

Day 1:

Day N-1:
o

setup.cli (before SCA recordings start)

reset.cli (after SCA recordings are over)

deleteSymbolicNames.cli (optional, only if implemented on Day0)

clear.cli

Day N:

2.3.5

Retrieving SCA Results

Uploaded SCA measurements are organized by recording days.


Log files should be organized by date. Each sector should have a log file in binary format.
Note: When log files are transferred from the OMCR via FTP, set the transfer method to Binary.
Siemens uploads log files in szip format. Commands to unzip files (reset.cli) have both a
folder and a filename.
If these commands remain as szip files, either:

the command folder names are incorrect, or

the user does not have permission to run commands.

2.3.6

Traffic File

The traffic file should be in tab-delimited text file format with traffic information for all sectors
in the optimization and simulation areas (the guard-zone area), and should include the
following columns:

Sector

Traffic (carried traffic in Erlangs)

AMR penetration (optional)

May 08
Schema

Proprietary and Confidential

10 of 16

Ultima Fort Required Data Inputs for Siemens Infrastructure

Since the Traffic file should be in Schema format, these columns can be in any order.
The Traffic file should contain information for five consecutive working days in a three to fourhour period that includes the network peak hour, and should be generated on the last recording
day.

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

The AOUINIRH(144), ATINBHDO(110) statistical counters should be used and aggregated


for the total number of outgoing handover attempts per adjacency.

2.4

Network Performance Statistics

The following network performance statistics should be collected (for each cell, every hour, for
seven consecutive days) for network traffic modeling and post-optimization network
performance benchmarking.

SDCCH Assignments (immediate assignment attempts and failures):

ATIMASCA(1...6), NSUCCHPC(16), ATSDCMBS

SDCCH Traffic:

MBUSYSDC

SDCCH Performance (drop and drop reason):

NRFLSDCC(19)

TCH Assignments (TCH assignment attempts, failures, and successes):

TASSATT(23), TASSUCC(23), TASSFAIL(615), SUCTCHSE(12)

TCH Traffic:

MEBUSTCH(14), ATTCHSEI(12), ATTCHSMBS(14)

TCH Performance (drop and drop reason):

NRFLTCH (136), UNIHIALC, UNIHIRLC, NRCLRREQ (118), NRCLRCMD (112)

TCH RxQuality:

CRXLVQUU(164),
May 08
Schema

CRXLVQUD(164)
Proprietary and Confidential

11 of 16

Ultima Fort Required Data Inputs for Siemens Infrastructure

The following performance statistics should be collected and calculated daily, for seven
consecutive days, for each cell relation:

Intracell HO:

SINTHITA(112), UNINHOIA(112), ATINHIAC(112).

HO Performance (cell):

ATINHIRC(111), SINTHINT(111)

HO Performance (cell relation):

AOUINIRH(144), SOUINIRH(144), UNINHOIE(111),


ATINBHDO(110), SUINBHDO(1..10), NRUNINHD(110)

2.4.1

Network Performance Evaluation

The formula for calculating the KPI improvement rate is:

KPI _ improvement _ rate =

KPI before KPI new


KPI before

100%

The formula for calculating the handover success rate improvement is:

HO _ Success _ improvement _ rate =

KPI before KPI new


1 KPI before

100%

Each KPI improvement ratio may be calculated separately over a period of five working days
(during each days network busy hour), before and after the optimization cycle.
Network performance KPIs that are not related to the BSS subsystem should be excluded from
the calculation.

2.4.2

Radio Network Performance KPI Calculation

The formula for calculating Radio Network Performance evaluation KPI is:

SDCCH _ Drop _ Rate =

TCH _ Drop _ Rate =

NRFLTCH(1...36) + UNIHIALC + UNIHIRLC


SUCTCHSE (1,2)

Call _ Drop _ Rate (1) =

May 08
Schema

NRFLSDCC (1...9 )
NSUCCHPC (1...6 )

NRCLRREQ (1...3,5... 12,14...18 )


TASSUCC (2,3)
Proprietary and Confidential

12 of 16

Ultima Fort Required Data Inputs for Siemens Infrastructure

Call _ Drop _ Rate(2) =

NRCLRREQ(1...3,5...12,14...18)
NRCLRCMD(1...2,4...8,10...12) NRCLRREQ(4,13) TASSFAIL(6...8,11...13)

MEBUSTCH(1...4)
NRFLTCH(1...36) + UNIHIALC+ UNIHIRLC

TCH _ Erlang _ to _ Drop(1) =

TCH _ Erlang _ to _ Drop(2) =

MEBUSTCH(1...4)

NRCLRREQ(1...3,5...12,14...18)

TCH _ Bad _ Quality _ DL =

CRXLVQUD_x

Rxlev = 0 RxQual =5
64

CRXLVQUD_x
x =1

TCH _ Bad _ Quality _ UL =

CRXLVQUU_x

Rxlev = 0 RxQual =5
64

CRXLVQUU_x
x =1

Outgoing _ HO _ Success _ Rate =

2.4.3

SOUINIRH(1...44) + SUINBHDO(1...10)
AOUINIRH(1...44) + ATINBHDO(1...10)

Additional KPIs for Network Performance Evaluation

The formulae for calculating additional KPIs for network performance evaluation are:

SDCCH _ Assignment _ Success =

SDCCH _ Congestion =

NSUCCHPC(1...6) ATSDCMBS
ATIMASCA(1...6) ATSDCMBS

ATSDCMBS
ATIMASCA(1...6)

TCH _ Assign _ Success(1) = 1

TASSFAIL(6,7,9...12,14,15)
TASSATT(2,3)

TCH _ Assign _ Success(2) = 1

TASSFAIL(6...15)
TASSATT (2,3)

Call _ Congestion =

May 08
Schema

TASSFAIL(8,13)
TASSATT (2,3)
Proprietary and Confidential

13 of 16

Ultima Fort Required Data Inputs for Siemens Infrastructure

TCH _ Congestion =

ATTCHSMBS(1...4)
ATTCHSEI(1,2)

SDCCH _ Traffic = MBUSYSDC


TCH _ Traffic = MEBUSTCH(1...4)

TCH _ Traffic _ FR = MEBUSTCH (1,3)


TCH _ Traffic _ HR = MEBUSTCH(2,4)

May 08
Schema

Proprietary and Confidential

14 of 16

Ultima Fort Required Data Inputs for Siemens Infrastructure

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

SCA Files
BSS Network
Configuration
Network Performance Statistics
SDCCH Assignments

Immediate assignments attemptsImmediate


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 EFR/HR/AMR/AMRHR
TCH Congestion

TCH Performance

Drops
Drops per reason

Rx Quality

Rx Quality DL
Rx Quality UL

Intracell HO Performance

IHO attempts
IHO success
IHO fail

Handover (HO)
Performance per Cell
Relation

HO
HO
HO
HO
HO

HO Performance per Cell

HO reasons

May 08
Schema

attempts
success
reversion
drop
reasons

Proprietary and Confidential

15 of 16

Ultima Fort Required Data Inputs for Siemens Infrastructure

SOURCE

COMMENTS

CHECK

HO attempts
HO success

May 08
Schema

Proprietary and Confidential

16 of 16