ultima fortי required data inputs for siemens infrastructure.pdf

8/9/2019 Ultima Fort Required Data Inputs for Siemens Infrastructure.pdf

1/16

Ultima Fort Required Data Inputs for Siemens Infrastructure

May 08 Proprietary and Confidential 1 of 16Schema

Ultima Fort

Required Data Inputs for SiemensInfrastructure

(for Version 4.0 and above)

Copyright Notice

Due to a policy of continuous product development and refinement, Schema reserves the right to alter thespecifications 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 forequipment or services.

Schema retains the sole proprietary rights to all information contained in this document. No part of thispublication 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


2/16



Table of Contents

1 Introduction.............................................................................................. 4

2 Required Information and Data................................................................. 52.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 BA List Creation for SCA Data Collection...................................................7

2.3.2 SCA Data Collection ..............................................................................7

2.3.3 SCA Data Collection Cleanup ..................................................................7

2.3.4 Running Command Files ........................................................................8

2.3.5 Retrieving SCA Results ........................................................................10

2.3.6 Traffic File .........................................................................................10

2.3.7 Handover Statistics ............................................................................. 11

2.4 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

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


3/16



Table of Figures

Figure 1: Radio Commander Application ...........................................................................8

Figure 2: Command Line Interface...................................................................................8

Figure 3: Command History Tool .....................................................................................9


4/16



1 Introduct ion

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.


5/16



2 Requi red Information and Data

2.1 Optim izat ion Ar eaThe 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 Networ k Conf igur at ion

2.2.1 Siemens BSS Networ k Conf ig urat io n Data Retr i eval

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.


6/16



2.2.2 Secto r Coord inates Fi le

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 Mobil e Measurements Data Reco rdi ngs

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.


7/16



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 themeasurement period.

2.3.1 BA Lis t Creat io n for SCA Data Col lect io n

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

2.3.2 SCA Data Col l ect i on

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

setup.cli

reset.cli

The command set in the setup.clifile should be implemented before beginning SCA data

collection. The command set in the reset.clifile should be implemented after completing SCA

data collection.

2.3.3 SCA Data Col l ect i on 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.


8/16



2.3.4 Runnin g Command Fi les

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


9/16



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

5. For each command file:

a. Change the file mode to:

chmod +x

b. Execute the commands using:

| tee

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.cliand how to create

the prepare.txtlog 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


10/16



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

Day 0:

o prepare.cli

o setSymbolicNames.cli (optional)

Day 1:

o setup.cli (before SCA recordings start)

o reset.cli (after SCA recordings are over)

Day N-1:

o setup.cli (before SCA recordings start)

o reset.cli (after SCA recordings are over)

Day N:

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

o clear.cli

2.3.5 Retr ievi ng SCA Result s

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 szipformat. Commands to unzip files (reset.cli) have both a

folder and a filename.

If these commands remain as szipfiles, either:

the command folder names are incorrect, or

the user does not have permission to run commands.

2.3.6 Traf f i c Fi le

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)


11/16


12/16



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 Netwo rk Perfo rmanc e Evaluat ion

The formula for calculating the KPI improvement rate is:

%100__

=before

newbefore

KPI

KPIKPIratetimprovemenKPI

The formula for calculating the handover success rate improvement is:

%1001

___

=

before

newbefore

KPI

KPIKPIratetimprovemenSuccessHO

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 Netwo rk Perfo rmanc e KPI Calcu lat ion

The formula for calculating Radio Network Performance evaluation KPI is:

( )

( )

=

6...1NSUCCHPC

9...1NRFLSDCC__ RateDropSDCCH

( )

( ) ++

=1,2SUCTCHSE

UNIHIRLCUNIHIALC1...36NRFLTCH__ RateDropTCH

( )

( )

=2,3TASSUCC

12,14...181...3,5...NRCLRREQ)1(__ RateDropCall


13/16



( )

( ) ( ) ( )

=

.136...8,11..TASSFAIL4,13NRCLRREQ8,10...121...2,4...NRCLRCMD

12,14...181...3,5...NRCLRREQ)2(__ RateDropCall

( )

( )

++= UNIHIRLCUNIHIALC1...36NRFLTCH

1...4MEBUSTCH

)1(___ DroptoErlangTCH

( )

( )

=12,14...181...3,5...NRCLRREQ

1...4MEBUSTCH)2(___ DroptoErlangTCH

=

= ==

64

1

7

0

7

5

CRXLVQUD_x

CRXLVQUD_x

___

x

Rxlev RxQualDLQualityBadTCH

=

= ==

64

1

7

0

7

5

CRXLVQUU_x

CRXLVQUU_x

___

x

Rxlev RxQualULQualityBadTCH

( ) ( )

( ) ( )

+

+=

1...10ATINBHDO1...44AOUINIRH

1...10SUINBHDO1...44SOUINIRH___ RateSuccessHOOutgoing

2.4.3 Add i t i onal KPIs for Networ k Perfo rmanc e Evaluat ion

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

( )

( )

=

ATSDCMBS1...6ATIMASCA

ATSDCMBS1...6NSUCCHPC__ SuccessAssignmentSDCCH

( )

=1...6ATIMASCA

ATSDCMBS_CongestionSDCCH

( )

=

)3,2(TASSATT

,14,156,7,9...12TASSFAIL1)1(__ SuccessAssignTCH

( )

=)2,3(TASSATT

6...15TASSFAIL1)2(__ SuccessAssignTCH

( )

=)2,3(TASSATT

8,13TASSFAIL_CongestionCall


14/16



( )

=,2)ATTCHSEI(1

1...4ATTCHSMBS_CongestionTCH

= MBUSYSDC_TrafficSDCCH

( )= 1...4MEBUSTCH_TrafficTCH

( )= 1,3MEBUSTCH__ FRTrafficTCH

( )= 2,4MEBUSTCH__ HRTrafficTCH


15/16



3 Data Col lect ion Checkl ist

SOURCE COMMENTS CHECKNetwork Data

BSS NetworkConfiguration

Sector Coordinates File

Traffic File

Mobile Measurements Recordings

Day 1 Day 2 Day 3 Day 4 Day 5

SCA Files

BSS Network

ConfigurationNetwork Performance Statistics

SDCCH Assignments Immediate assignments attemptsImmediateassignments 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 cellTraffic 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 CellRelation

HO attemptsHO success

HO reversion

HO drop

HO reasons

HO Performance per Cell HO reasons


16/16



SOURCE COMMENTS CHECK

HO attempts

HO success

ultima fortי required data inputs for siemens infrastructure.pdf

Documents