Ultima Fort

Required Data Inputs

for

Ericsson 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

Ultima Fort Required Data Inputs for Ericsson Infrastructure

Table of Contents
1
2

Introduction.......................................................................................................... 3
Required Information and Data............................................................................. 4
2.1
Optimization Goals Area and Zones.....................................................................4
2.2
Network Data ..................................................................................................4
2.2.1
Ericsson BSS Network Configuration .............................................................4
2.2.2
Sector Coordinates File ...............................................................................5
2.3
Mobile Measurements Data Collection..................................................................5
2.3.1
Binary Format Files ....................................................................................6
2.3.1.1
BAR Recordings ..................................................................................6
2.3.1.2
MRR Recordings ..................................................................................8
2.3.1.3
RIR Recordings ...................................................................................9
2.3.2
Text Format Files ..................................................................................... 10
2.3.2.1
NCS Recordings ................................................................................ 10
2.3.2.2
MRR Recordings ................................................................................ 10
2.3.2.3
FAS Recordings................................................................................. 10
2.3.3
Handover Statistics .................................................................................. 11
2.4
Network Performance Statistics ........................................................................ 11
2.4.1
Network Performance Evaluation................................................................ 12
2.4.2
Radio Network Performance KPIs Calculation............................................... 12
2.4.3
Additional KPIs for Network Performance Evaluation..................................... 13
3
Data Collection Checklist..................................................................................... 15

Schema Confidential & Proprietary

page 2 of 15

Ultima Fort Required Data Inputs for Ericsson Infrastructure

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

Optimization area and optimization goals

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

Schema Confidential & Proprietary

page 3 of 15

Ultima Fort Required Data Inputs for Ericsson Infrastructure

2 Required Information and Data

2.1 Optimization Goals Area and Zones
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 and surrounding areas

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, )

List of cells in the guard zone (if any)

2.2 Network Data

2.2.1

Ericsson BSS Network Configuration

The required BSS network configuration file can be retrieved from the Ericsson OSS from the CNA
(Cellular Network Administrator) by using the following commands:
cna_export NW=all, MSC=all, MSC_REF=none, BSC=all, BSC_REF=all, SITE=all,
SITE_REF=none,CELL=all,CELL_REF=all, OUTPUT=AllParameters_YYYYMMDD.txt
cna_export NW = all, FCELL = all, FCELL_REF = all, OUTPUT = foreign_HO_YYYYMMDD.txt
(where: YYYY year, MM month, DD day)
Note:
o

The export of foreign cells data is required only in the case where BSS network configuration
data for surrounding networks has been provided.

The BSS network configuration file should be retrieved per each day of mobile measurements
recordings.

The BSS network configuration file should be generated just before initiating the BAR and
MRR recording session.

The BSS network configuration should be retrieved for each OMCR relevant to the
optimization and surrounding areas in the network.

Schema Confidential & Proprietary

page 4 of 15

Ultima Fort Required Data Inputs for Ericsson Infrastructure

At the beginning and the end of the data collection process the following data should be retrieved
for all BSCs to be included in the network environment creation for Ultima Fort:
RLCRP:CELL=ALL,DETAIL

Cell Resources Details

RXMOP:MOTY=RXOTG

Managed Object Data

RAEPP:ID=ALL

BSC Exchange Properties

Data retrieval should be performed via the BSC command line interface.
The output of the commands printout should be stored in text files. For each output type, the
command name (RLCRP, RXMOP, RAEPP) should be at the beginning of the file name, for
instance RLCRP_BSC1.txt.

2.2.2

Sector Coordinates File

The sector coordinates file should be in tab delimited text file format with geographical
information for all the sectors in the network.
The file should contain the following columns:
o
o
o
o

Sector
Latitude
Longitude
Azimuth

The latitude and longitude values should be in decimal format.

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
o
o
o
o
o
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
o

TRX additions
Frequency changes (TCH)

All other parameters should not be changed.

Schema Confidential & Proprietary

page 5 of 15

Ultima Fort Required Data Inputs for Ericsson Infrastructure

Note (1): Version of BSC and OSS must be R8 or later.

Note (2):There are 3 types of Mobile Measurements files. Each of these can be extracted and
then used by Ultima Fort either in binary format or text format.

2.3.1
2.3.1.1

Binary Format Files

BAR Recordings

These files contain the C/I measurements. BAR recordings should be performed over 5
consecutive working days.
There are 2 possible ways to activate BAR recording:
1. RNO interface (depends on availability)
2. BSC command interface
To perform BAR recordings using the RNO interface, follow the instructions below:
1. Login to OSS
2. Start RNO
3. Go to File -> New Recording -> NCS
4. Provide the recording session with a name
5. Set Relative SS Threshold to -12db
6. Set Absolute SS Threshold to -80dbm
7. Set BA List Change interval to 15 minutes
8. Set number of test frequencies to add to each interval to 10
9. Enter Start date
10. Enter repeat value (set to daily) and number of times to repeat (set to 5)
11. Enter date type, working days only (5 consecutive working days - Monday to Friday)
12. Enter hour range (recommended to define 4 hours around network busy hour)
13. Select the cell set or BSC (should include all cells of the entire network)
14. Set Cell Filter to desired (available) frequency band (limits recorded cell set to
specified frequency band)
15. Select Frequencies - Create a Frequency Set for BAR recordings including all
frequencies used for BCCH in the desired band for the entire network
16. Save and schedule the recording
Note:
In dual band network the recording should be performed separately according to cell band. In
order to provide full functionality of handover optimization, the inter band recordings suppose to
be performed as well, i.e. the each band cell set should record frequency set, which is contain the
BCCH frequencies for both bands.

Schema Confidential & Proprietary

page 6 of 15

Ultima Fort Required Data Inputs for Ericsson Infrastructure

When the RNO application is not available, BAR recordings can be activated by using the BSC
command line interface. Follow the instructions below:
1. RABRE:RID=RARID00; terminate an NCS recording
2. RABIE:RID=BARID00; delete a recording
3. RABII; initialize a new recording
4. RABRP:RID=BARID00; print BAR recording status (optional)
5. RABDC:RID=BARID00, CELL=ALL; all cells of a BSC will be recorded
6. RABDC:RID=BARID00,TMBCCHNO=50&&124; frequencies to measure 50 to 124*
7. RABDC:RID=BARID00,NUMFREQ=10; number of test frequencies at each interval
8. RABDC:RID=BARID00,SEGTIME=15; recording segment time in minutes
9. RABDC:RID=BARID00,RELSSN=12; negative signal strength thresholds
10. RABDC:RID=BARID00,RELSS2P=0; positive signal strength thresholds
11. RABDC:RID=BARID00, ABSS=80; absolute signal strength (means negative dBm)
12. RABDP:RID=BARID00; view recording properties
13. RABRI:RID=BARID00,DTIME=120; recording period time in minutes - the recording
starts as soon as this command is entered!
14. RABTI:RID=BARID00,IO=FILE; after recording is complete, this command should be
run in order to create the output binary file at the OSS
15. RABTI:RID=BARID00, IO=AT-##; substitute at-## with the number of the AT device
from that which you see when you connect to this BSC. The text output will be
produced at AT-## device**.
* - the relevant frequency set should be used for each specific case.
** - in some cases when a binary file cannot be created, the BAR text output can be
generated at the BSC command terminal. Store the generated printout as a text file.
Once recording is complete, store the BARFILs files for each BSC on FTP no later than 48 hours
after the recording (otherwise it will be deleted from the system).
Binary BARFILs files are located at the OSS in the following directories:

R8:
o

Note:

/var/opt/ehpt/eac/data/fs/BSC_NAME/

R9/R10 with IOG20:

o /root/var/opt/ericsson/nms_eam_eas/data/fs/BSC_NAME/

R9/R10 with APG40:

o /root/var/opt/ericsson/brf/data/db/tmpfileStore/BSC_NAME/

When BARFILs are transferred from Unix to Windows by using FTP, the transfer method should
be defined as Binary. All BARFILs recorded on the same day should be stored in the same
directory.

Schema Confidential & Proprietary

page 7 of 15

Ultima Fort Required Data Inputs for Ericsson Infrastructure

2.3.1.2

MRR Recordings

These files contain RxLevel and traffic data.

MRR recordings should be generated in parallel to the BAR recordings and for the same cell set.
No filtering or thresholds should be applied to the MRR recordings.
There are 2 possible ways to activate an MRR recording:
1. RNO interface (depends on availability)
2. BSC command interface
To perform MRR recordings using the RNO interface, follow the instructions below:
1. Login to OSS
2. Start RNO
3. Go to File -> New Recording -> MRR
4. Provide the recording session with a name
5. Enter Start date
6. Enter repeat value (set to daily) and number of times to repeat (set to 5)
7. Enter date type, working days only (5 consecutive working days - Monday to Friday)
8. Enter hour range (suggested to define 3 hours around network busy hour)
9. Select the cell set or BSC (should include all cells of the network)
10. Set Cell Filter to desired (available) frequency band (limits recorded cell set to
specified frequency band)
11. Save and schedule the recording

When the RNO application is not available, MRR recordings can be activated by using the BSC
command line interface. Follow the instructions below:
1. RAMRE: RID=MRRID00; terminate an MRR recording
2. RAMIE: RID=MRRID00; delete a recording
3. RAMII; initialize a new recording
4. RAMRP: RID=MRRID00; print status (optional)
5. RAMDC: RID=MRRID00, CELL=ALL; all cells of a BSC will be recorded
6. RAMDC: RID=MRRID00, MEASTYPE=NOTYPE; all measurement types will be collected
7. RAMRI: RID=MRRID00, DTIME=120; recording period time - the recording starts as
soon as this command is entered!
8. RAMRP: RID=MRRID00; print status (optional)
9. RAMTI: RID=MRRID00; after recording is complete, this command should be run in
order to create the output file

Schema Confidential & Proprietary

page 8 of 15

Ultima Fort Required Data Inputs for Ericsson Infrastructure

Once recording is complete, store the MRRFILs files for each BSC on FTP no later than 48 hours
after the recording (otherwise it will be deleted from the system).
Binary MRRFILs files are located at the OSS in the following directories:

R8:
o

/var/opt/ehpt/eac/data/fs/BSC_NAME/

R9/R10 with IOG20:

o /root/var/opt/ericsson/nms_eam_eas/data/fs/BSC_NAME/

R9/R10 with APG40:

o /root/var/opt/ericsson/brf/data/db/tmpfileStore/BSC_NAME/

Note:
When MRRFILs are transferred from Unix to Windows by using FTP, the transfer method should
be defined as Binary. All MRRFILs recorded on the same day should be stored in the same
directory.
MRR recordings may also be exported to ASCII files using the RNO GUI. In this case both export
files (.msmt and .conf) should be transferred. This data can be used to back up the MRRFILs files.

2.3.1.3

RIR Recordings

These files contain uplink interference data.

RIR recordings should be generated only in case of some external interference observed in the
network on uplink. This type of recording mainly relates to the GSM900 band.
RIR recordings can be activated by using the BSC command line interface. Follow the instructions
below:
1. RARRE: RID=RIRID00; terminate an RIR recording
2. RARIE: RID=RIRID00; end of recording
3. RARII; initialize a new recording
4. RARRP: RID=RIRID00; print status (optional)
5. RARDC: RID=RIRID00, CELL=ALL, CSYSTYPE=GSM900; all cells in the GSM900 band
in a BSC will be recorded
6. RARDC: RID=RIRID00, ARFCN=60&&124; frequencies from 60 to 124 will be recorded
7. RARRI: RID=RIRID00, DTIME=300; recording period in minutes - the recording
starts as soon as this command is entered!
8. RARRP: RID=RIRID00; print status (optional)
9. RARTI: RID=RIRID00; after recording is complete, this command should be run in
order to create the output file
Once recording is complete, store the RIRFILs files for each BSC on FTP no later than 48 hours
after the recording (otherwise it will be deleted from the system).

Schema Confidential & Proprietary

page 9 of 15

Ultima Fort Required Data Inputs for Ericsson Infrastructure

Binary RIRFILs files are located at OSS in the following directories:

R8:
o

R9/R10 with IOG20:

o

/var/opt/ehpt/eac/data/fs/BSC_NAME/
/root/var/opt/ericsson/nms_eam_eas/data/fs/BSC_NAME/

R9/R10 with APG40:

o

/root/var/opt/ericsson/brf/data/db/tmpfileStore/BSC_NAME/

Note:
When RIRFILs are transferred from Unix to Windows by using FTP, the transfer method should be
defined as Binary. All RIRFILs recorded on the same day should be stored in the same directory.
FAS recordings may also be exported to ASCII files using the RNO GUI. In this case both export
files (.msmt and .conf) should be transferred. This data can be used to back up the RIRFILs
files.

2.3.2
2.3.2.1

Text Format Files

NCS Recordings

These files contain C/I measurements (parallel format to the BAR recordings as in para. 2.3.1.1).
NCS files are extracted in pairs: one with an .msmt extension (which contains the data) and one
with a .conf extension (which contains the file configuration and recordings).

2.3.2.2

MRR Recordings

These files contain the RxLevel and traffic data and can be extracted either in binary format (as
in para. 2.3.1.2) or in text format.
Text MRR files are extracted in pairs: one with an .msmt extension (which contains the data)
and one with a .conf extension (which contains the file configuration and recordings).

2.3.2.3

FAS Recordings

These files contain uplink interference (the parallel of RIR files, as in para. 2.3.1.3).
FAS recordings should be generated only in case of some external interference observed in the
network on uplink. This type of recording mainly relates to the GSM900 band.
Text FAS files are extracted in pairs: one with an .msmt extension (which contains the data) and
one with a .conf extension (which contains the file configuration and recordings).

Schema Confidential & Proprietary

page 10 of 15

Ultima Fort Required Data Inputs for Ericsson Infrastructure

2.3.3

Handover Statistics

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

Serving Sector

Target Sector

Handover Attempts

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 network performance statistics should be collected on a per cell basis with hourly
resolution over 7 consecutive days:
o

SDCCH Assignments
CCALLS, CCALLSSUB, CMESTAB, CMESTABSUB, CCONGS, CCONGSSUB, CNRELCONG

SDCCH Traffic
CTRALACC, CTRALSUB

SDCCH Performance
CNDROP

TCH Assignments. These statistics should include the following counters:

TASSALL, TFCASSALL, THCASSALL, TFNCASSALLSUB, THNCASSALLSUB, TMSESTB,
TFMSESTB, THMSESTB, TFMSESTBSUB, THMSESTBSUB, TFCONGSAS, THCONGSASSUB,
TFNRELCONG, THNRELCONG, TFNRELCONGSUB, THNRELCONGSUB

TCH Traffic (Traffic per Cell, Traffic per OL/UL, Traffic HR/EFR and per OL/UL, Traffic AMR
FR/AMR HR and per OL/UL). These statistics should include the following counters:
TFTRALACC, THTRALACC, TFTRALSUB, THTRALSUB, TSCAN, TFNSCAN, THNSCAN,
TFNSCANSUB,
THNSCANSUB,
TTCONGS,
TFTCONGS,
THTCONGS,
TFTCONSUB,
THTCONSUB

TCH Performance (Drops, Drops per OL/UL, Drops Reason, Drops Reason per OL/UL, Normal
Disconnection Bad Quality). These statistics should include the following counters:
TFNDROP, THNDROP, TFNDROPSUB, THNDROPSUB, TFDISTA, THDISTA, TFDISTASUB,
THDISTASUB, TFDISSUL, TFDISSSDL, TFDISSSBL, TFDISSSULSUB, TFDISSSDLSUB,
TFDISSSBLSUB, THDISSSUL, THDISSSDL, THDISSSBL, THDISSSULSUB, THDISSSDLSUB,
THDISSSBLSUB, TFDISQAUL, TFDISQADL, TFDISQABL, TFDISQAULSUB, TFDISQADLSUB,
TFDISQABLSUB,
THDISQAUL,
THDISQADL,
THDISQABL,
THDISQAULSUB,
THDISQADLSUB,
THDISQABLSUB,
TFSUDLOS,
THSUDLOS,
TFSUDLOSSUB,
THSUDLOSSUB

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

Schema Confidential & Proprietary

page 11 of 15

Ultima Fort Required Data Inputs for Ericsson Infrastructure

HO Performance (Cell to Cell Relation, HO Attempts, HO Reversions, HO Lost, Assignment to

Best/Worst due to BQ Uplink & due to BQ Downlink). These statistics should include the
following counters:
HOVERCNT, HOVERSUC, HORTTOCH, HOASBCL, HOASWCL, HOUPLQA, HODWNQA,
HOATTLSS, HOATTHSS

Intra-Cell Performance (Attempts, Reversion, Lost, Reason Uplink/Downlink). These statistics

should include the following counters:
HOINSUC, HOINBOCH, HOINUQA, HOINDQA, HOINBQA

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 the handover success rate the improvement will be calculated as:

HO _ 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 =

TCH _ Drop _ Rate =

(CNDROP)

(CMESTAB + CMESTABSUB)

(TFNDROP + THNDROP + TFNDROPSUB + THNDROPSUB)

TCH _ Erlang _ to _ Drop =

TFCASSALL + THCASSALL +

+ TFNCASSALLSUB + THNCASSALLSUB

(TFTRALACC + THTRALACC) / 360

(TFNDROP + THNDROP + TFNDROPSUB + THNDROPSUB)

Schema Confidential & Proprietary

page 12 of 15

Ultima Fort Required Data Inputs for Ericsson Infrastructure

TCH _ Bad _ Quality _ DL =

RxQual _ DL

RxQual _ DL

x =5
7

x =0

TCH _ Bad _ Quality _ UL =

RxQual _ UL

RxQual _ UL

x =5
7

x =0

Outgoing _ HO _ Success _ Rate =

(HOVERSUC)
(HOVERCNT)

Notes:
The Bad_Quality statistics will be retrieved from the MRR data directly.

2.4.3

Additional KPIs for Network Performance Evaluation

The following calculations providing additional KPIs for network performance evaluation:

(CMESTAB + CMESTABSUB)
(CCALLS + CCALLSSUB)
(CNDROP)
SDCCH _ Drop _ Rate _ Total =
(CMESTAB + CMESTABSUB)
SDCCH _ Assignment _ Success =

SDCCH _ Congestion =

(CCONGS)
(CCALLS)
TFCASSALL + THCASSALL +

TCH _ Assign _ Success =

TCH _ Congestion =

SDCCH _ Traffic =
TCH _ Traffic =

+ TFNCASSALLSUB + THNCASSALLSUB

(TASSALL)

CNRELCONG + TFNRELCONG + THNRELCONG +

TFNRELCONGSUB + THNRELCONGSUB

(TASSALL)

(CTRALACC + CTRALSUB)
3600

(TFTRALACC + THTRALACC)

TCH _ Traffic _ FR =

360

(TFTRALACC)
360

Schema Confidential & Proprietary

page 13 of 15

Ultima Fort Required Data Inputs for Ericsson Infrastructure

TCH _ Traffic _ HR =

(THTRALACC)
360

(HODWNQA)
(HOVERCNT)
(HOUPLQA)
HO _ BQ _ UL =
(HOVERCNT)
HO _ BQ _ DL =

Schema Confidential & Proprietary

page 14 of 15

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

BAR Files
MRR 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
Intra-Cell Handover
Performance

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 15 of 15