Professional Documents
Culture Documents
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.
May 08
Schema
1 of 16
Table of Contents
1
Introduction.............................................................................................. 4
2.2
Network Configuration.....................................................................................5
2.2.1 Siemens BSS Network Configuration Data Retrieval ...................................5
2.2.2 Sector Coordinates File ..........................................................................6
2.3
2.4
May 08
Schema
2 of 16
Table of Figures
Figure 1: Radio Commander Application ...........................................................................8
Figure 2: Command Line Interface ...................................................................................8
Figure 3: Command History Tool .....................................................................................9
May 08
Schema
3 of 16
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:
Performance reports
This document not only identifies the required sources of data, but also explains how to obtain
the data.
May 08
Schema
4 of 16
2.1
Optimization Area
List of cells in the optimization and surrounding areas (optimization set and guard zone)
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.
May 08
Schema
5 of 16
2.2.2
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
The following network activities should stop while data is being recorded:
BSC split
The following changes should be performed only during maintenance (but not while recording):
TRX additions
Site additions
May 08
Schema
6 of 16
Notes:
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
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:
2.3.2
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
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
7 of 16
2.3.4
May 08
Schema
8 of 16
May 08
Schema
9 of 16
Command files created by a Measurement Plan should be run in the following order:
Day 0:
o
prepare.cli
setSymbolicNames.cli (optional)
Day 1:
Day N-1:
o
clear.cli
Day N:
2.3.5
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
May 08
Schema
10 of 16
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
2.4
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 Traffic:
MBUSYSDC
NRFLSDCC(19)
TCH Traffic:
TCH RxQuality:
CRXLVQUU(164),
May 08
Schema
CRXLVQUD(164)
Proprietary and Confidential
11 of 16
The following performance statistics should be collected and calculated daily, for seven
consecutive days, for each cell relation:
Intracell HO:
HO Performance (cell):
ATINHIRC(111), SINTHINT(111)
2.4.1
100%
The formula for calculating the handover success rate improvement is:
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
The formula for calculating Radio Network Performance evaluation KPI is:
May 08
Schema
NRFLSDCC (1...9 )
NSUCCHPC (1...6 )
12 of 16
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
MEBUSTCH(1...4)
NRCLRREQ(1...3,5...12,14...18)
CRXLVQUD_x
Rxlev = 0 RxQual =5
64
CRXLVQUD_x
x =1
CRXLVQUU_x
Rxlev = 0 RxQual =5
64
CRXLVQUU_x
x =1
2.4.3
SOUINIRH(1...44) + SUINBHDO(1...10)
AOUINIRH(1...44) + ATINBHDO(1...10)
The formulae for calculating additional KPIs for network performance evaluation are:
SDCCH _ Congestion =
NSUCCHPC(1...6) ATSDCMBS
ATIMASCA(1...6) ATSDCMBS
ATSDCMBS
ATIMASCA(1...6)
TASSFAIL(6,7,9...12,14,15)
TASSATT(2,3)
TASSFAIL(6...15)
TASSATT (2,3)
Call _ Congestion =
May 08
Schema
TASSFAIL(8,13)
TASSATT (2,3)
Proprietary and Confidential
13 of 16
TCH _ Congestion =
ATTCHSMBS(1...4)
ATTCHSEI(1,2)
May 08
Schema
14 of 16
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
SDCCH Traffic
SDCCH Performance
SDCCH drop
SDCCH drop reason
TCH Assignments
TCH Traffic
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 reasons
May 08
Schema
attempts
success
reversion
drop
reasons
15 of 16
SOURCE
COMMENTS
CHECK
HO attempts
HO success
May 08
Schema
16 of 16