Ultima Forte Required Data Inputs For Ericsson Markets 2g-3g Infrastructure PDF

Ultima Fort Required Data Inputs for Ericsson Markets 2G-3G Infrastructure
Ultima Fort
Required Data Inputs for Ericsson
Markets 2G-3G 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
Proprietary and Confidential
Schema
Page 1 of 28
Table of Contents
1
Introduction.............................................................................................. 4
Required Information and Data................................................................. 5

2.1
Optimization Area ...........................................................................................5
Network Data ........................................................................................................6

2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
2.1.7
2.1.8
2.1.9
GSM Network Configuration....................................................................6

UMTS Network Configuration (XML Format) ..............................................7
Sector Coordinates File ..........................................................................9
UMTS Antenna File.............................................................................. 10
*.mpr File.......................................................................................... 11
Generic Loss File................................................................................. 11
Mobile Measurement Data Recordings .................................................... 12
Activation of Recordings ...................................................................... 13
Retrieval of Recordings ........................................................................ 19
2.2
Handover Statistics ....................................................................................... 21
2.3
Network Performance Statistics ...................................................................... 22

2.3.1 Network Performance Evaluation........................................................... 24
2.3.2 Radio Network Performance KPI Calculation............................................ 24
Data Collection Checklist......................................................................... 26
Appendix: Troubleshooting ..................................................................... 27

4.1.1 The removeFile Parameter for BARFIL and MRR File Deletion..................... 27
4.1.2 Additional Ericsson Information............................................................. 28
4.1.3 Parameter Database (PDB) Maps .......................................................... 28
May 08
Schema
Page 2 of 28
Table of Figures
Figure 1: Retrieve the Required BSS Network Configuration Files .........................................8
Figure 2: Export the Required BSS Network Configuration Files ............................................8
Figure 3: Save the Required BSS Network Configuration Files ..............................................9
Figure 4: RNO NCS New Recording ................................................................................ 14
Figure 5: RNO NCS UMTS Settings ................................................................................. 16
Figure 6: RNO NCS New UMFI Set ................................................................................. 16
Figure 7: RNO NCS Select Cell Set ................................................................................. 17
May 08
Schema
Page 3 of 28
Introduction
This document contains a list of all the required information and data that must be collected on
Ericsson GSM infrastructures for execution of the optional GSM<->UMTS Neighbor List
Optimization feature in Ultima Fort v4.0, for systems with the Ericsson GSM infrastructure.
The following data is required:
Optimization area
Ericsson BSS network configuration data (XML format)
UMTS system network configuration (vendor XML format or Schema Format)
GSM Sector coordinates data
UMTS antenna file
UMTS-to-GSM handover statistics
UTRAN neighboring cell quality measurements
Generic Loss File (optional)
Performance reports
The following data and information is required:
Optimization area
Nokia BSS network configuration data (XML format)
UMTS system network configuration (vendor XML format or Schema Format)
GSM Sector coordinates data
UMTS antenna file
UMTS-to-GSM handover statistics AKA Counter 93 (Section 2.3)
UTRAN neighboring cell quality measurements AKA Counter 94 (Section 2.3)
Generic Loss File (optional)
Performance reports
The following sections provide a more in-depth description of the required data sources and
how to obtain them.
May 08
Schema
Page 4 of 28
Required Information and Data
2.1
Optimization Area
The definition of the network area to be optimized is:
List of cells (from both networks) in the optimization area
Extended list of cells, including a guard zone (in which only GSM cells required)
Both lists are .txt files with one column, the first item being the word Sector, followed by a list
of sector names (both GSM and UMTS).
These lists can be generated by using the Ultima Fort selection tool, and saving the
selection.
May 08
Schema
Page 5 of 28
Network Data
2.1.1
GSM Network Configuration
2.1.1.1 CNA Export in Text Format

Retrieve the required BSS network configuration file from the Ericsson OSS, using the Cellular
Network Administrator (CNA), by running the following commands:
Overall Network Configuration:
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
Foreign Cells:
cna_export NW = all, FCELL = all, FCELL_REF = all, OUTPUT=foreign_HO_YYYYMMDD.txt
(where: YYYY year, MM month, DD day)
Notes:
Foreign cell data must be exported in order to import the IRAT Handover with any UMTS
network (Ericsson, as well as Nokia).
Daily CNA adjustment jobs should be scheduled for each BSC to ensure that the network
configuration is updated in the OSS.
It is recommended that the BSS network configuration file be retrieved for each day of
mobile measurement recordings. However, it is mandatory that this file be retrieved if any
BCCH/BSIC changes were made between two days of recordings.
The BSS network configuration file should be generated just before initiating the BAR and
MRR recording sessions.
The BSS network configuration should be retrieved for each OSS that is relevant to the
optimization and surrounding areas in the network.
BSC data is optional beginning from Release R12.
At the beginning and end of the data collection process, the following optional data should be
retrieved for all BSCs, and included in the Ultima Fort network environment:
May 08
Schema
Page 6 of 28
Data
Description
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 command printout should be stored in text files. The command name (RLCRP,
RXMOP, RAEPP) of each output type should be at the beginning of the file name, e.g.,
RLCRP_BSC1.txt.
2.1.1.2 New CNAI Export Format - R12:

Release R12 supports the New CNAI (CNA Import) alternative format for network configuration
files.
The required BSS network configuration file can be retrieved from the Cellular Network
Administrator (CNA) of the Ericsson OSS, using the following command: CNAI export valid i >
AllParameters_YYYYMMDD.txt.
2.1.2
UMTS Network Configuration (XML Format)
The UMTS Network configuration is an XML file in standard 3GPP format. Each UMTS OSS
vendor has its own method of retrieving this file.
May 08
Schema
Page 7 of 28
To retrieve the required BSS network configuration files from the Ericsson OSS:
1. Go to ConfigurationWCDMA Radio access NetworkWCDMA RAN Explorer (usually via
Citrix or OSS workstation).
2. Right click on the root of the network and select Export Network Configuration.
Figure 1: Retrieve the Required BSS Network Configuration Files
Figure 2: Export the Required BSS Network Configuration Files
May 08
Schema
Page 8 of 28
Choose the File Name and Radio topology.
Figure 3: Save the Required BSS Network Configuration Files
2.1.3
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 (optional)
CI (optional)
Keywords (optional)
The latitude and longitude values should be expressed in decimal-degree format, with up to six
digits following the decimal point.
May 08
Schema
Page 9 of 28
2.1.4
UMTS Antenna File
The UMTS Antenna file must be in tab-delimited text file format with full information for all the
sectors in the optimization and guard-zone areas.
Note: This file contains many fields (intended for future use), whose values are not currently
used for the GSM<->UMTS Neighbor List Optimization feature.
The required fields are in bold letters. Non-required fields should have real values for
database integrity (but the feature can run with dummy values).
RNC Name
RNC Id
Vendor
NodeB Name
NodeB Id
NodeB Longitude
NodeB Latitude
Sector Name
Active (boolean)
Noise Figure
AntennaID
Antenna Model
Sector Keywords
Antenna Longitude
Antenna Latitude
Height
Electrical DownTilt
Mechanical DownTilt
Azimuth
Downlink Loss
Uplink Loss
RTT fix A Coefficient
RTT fix B Coefficient
In Building
May 08
Schema
Page 10 of 28
The following file has a sample entry that corresponds to one antenna.
Antennas.txt
2.1.5
*.mpr File
The .mpr file is a text file (with the *.mpr extension) that points to the UTRAN topology file with
the following pointer:
ERICSSON_XML_FILE_NAME=path\topology_file_name.xml
2.1.6
Generic Loss File
The Generic Loss File is of a generic horizontal antenna pattern, used to determine the order of
potential neighbors in a measurement plan.
If a user-defined file (optional) is not provided, Ultima Fort uses a one-column text file, with
default values for each relative angle between the source and target sectors, in the following
structure:
Relative angle[degrees]= Loss[dB]
For example:
0=0
1=0
2=0.01
3=0.03
4=0.05
5=0.08
6=0.12
7=0.15
8=0.2
9=0.25
..
359=0
May 08
Schema
Page 11 of 28
The following is a full example of the file:
GenericLossFile.txt
2.1.7
Mobile Measurement Data Recordings
The following activities should stop during data recording:
BSC or RNC split
Site re-parenting (e.g., BSC/site relation changes in the GSM network)
LAC and CI changes in the GSM network, scrambling codes in the UMTS network, BCCH and
BSIC in the GSM network
Site and carrier additions
Sector mechanical changes, such as tilt, azimuth, and antenna
Manual UMTS <-> GSM Neighbor additions or deletions
The following changes should be performed only during maintenance (not during recording):
TRX/Carrier additions
Frequency changes (TCH)
Frequency changes (BCCH and BSIC)
Scrambling codes changes
Manual UMTS <-> GSM Neighbor additions or deletions
Site additions
No other parameters should be changed.

Note: BSC Version R06A (R12) (or later versions) should be used.
OSS Version RC3, RC5.3 (or later versions) should be used.
The following features should be activated to collect mobile measurements on the
Ericsson GSM OSS:
NCS-G, (NCS-GSM)
NCS-GW, (NCS-GSM/WCDMA)
In addition to the optional OSS NCS GSM-WCDMA feature, the following features are required
for IRAT modeling:
May 08
Schema
Page 12 of 28
Optional OSS features:

o
FAJ 122 477, Neighboring Cell Support - GSM RAN (NCS-G)
Optional BSS features:

o
FAJ 121 815, GSM-WCDMA Active BA-list Recording
FAJ 121 57, GSM-UMTS Cell Reselection and Handover
Mobile measurements files can be extracted from the Ericsson OSS, and used by Ultima Fort
either in binary format (Section 2.3.1) or in text format (Section 2.3.2).
2.1.8
Activation of Recordings
2.1.8.1
BA List Recordings (BAR) Recordings
BAR recordings should be performed during three to five consecutive working days.
BAR recording is activated by:
RNO interface (if available): FAJ 122 477 Neighboring Cell Support - GSM RAN (NCS-G)
BSC command interface
To perform BAR recordings, using the RNO interface:

1. Log in to OSS.
2. Start RNO.
3. Go to FileNew RecordingNCS.
4. Name the recording session.
5. Select the Measure GSM and Measure WCDMA check boxes.
6. Set the Relative SS Threshold to -12db.
7. Set the Absolute SS Threshold to -80dbm.
8. Set the BA List Change interval to 15 minutes.
9. Set the number of test frequencies to add to each interval to 10.
10. Enter a start date.
11. Enter a repeat value (set to daily) and a number of repetitions (set to 5).
12. Enter a date type with working days only (e.g., Monday to Friday five consecutive
working days).
13. Enter an hour range (four hours that include the network busy hour).
14. Select the cell set or BSC (including every cell in the entire network).
May 08
Schema
Page 13 of 28
15. Set the Cell Filter to a desired (available) frequency band (with the recorded cell set
limited to a specified frequency band.)
16. Select Frequencies. Create a Frequency Set for BAR recordings, including all frequencies
used for the BCCH in the desired band for the entire network.
17. Save and schedule the recording.
Figure 4: RNO NCS New Recording

Note on WCDMA Settings:
The recording configuration consists of the following:
Number of WCDMA cells in each Measurement report.
An Absolute Ec/No threshold.
The maximum number of test UMFIs that may be added to the 3G active mode BA lists
at one time.
A set of test-UMFIs to be used in recording.
The number of WCDMA cells in each measurement report is a recording parameter that can be
set to either Network Settings or to a numerical value between 1 and 3. The Network
Settings value uses the current FDDMRR network setting for the recording, which will remain
May 08
Schema
Page 14 of 28
the same. The numerical values will activate a temporary value of the FDDMRR parameter to
be used during recording. When active, this temporary value, called TFDDMRR, blocks any
FDDMRR value update for the cells included in the recording.
The temporary value is used to increase the amount of measurement data during the recording,
and affects how the Multi-RAT mobiles report data in the measurement report. This, in turn,
may affect the locating performance.
The absolute Ec/No threshold is related to a counter, which is incremented whenever the
Ec/NoUMFI > abs equation is fulfilled abs is the Ec/No absolute threshold and Ec/NoUMFI is the
Ec/No value for a specific UMFI, reported by the Multi-Rat mobile. The ratio between Ec/NoUMFI
and the number of measurement reports that include at least one reported UMFI during the
period when the specific UMFI has been included in the 3G Active BA-list for the cell is a value
that is used to determine whether or not the undefined WCDMA neighboring cell is included as a
defined neighbor.
A function calculates an appropriate set of test-UMFIs, based on a set of GSM cells. The WCDMA
cell coordinates determine which of those cells, located in the same area as the GSM cells, are
included in the recording. The user defines at which distance from the GSM cells the search is
performed. A list of test-UMFIs is then generated, based on the WCDMA cells that are found.
Since a maximum of 128 test-UMFIs may be included in a set, four recordings are needed to
measure all 512 Scrambling Codes for a single WCDMA-frequency.
May 08
Schema
Page 15 of 28
Figure 5: RNO NCS UMTS Settings
Figure 6: RNO NCS New UMFI Set
May 08
Schema
Page 16 of 28
Figure 7: RNO NCS Select Cell Set

Additional Notes:
Recordings in a dual band network should be made separately, based on the cell band.
However, to provide full functionality of handover optimization, inter-band recordings
should be made. Each band cell set should record a frequency set with the BCCH
frequencies for both bands. Multi Band Cells Reported (MBCR), is a cell parameter that
indicates how many neighbors from each frequency band are reported in the
measurement report. The recommended setting is either 2 or 3 in multi-band network,
in order for mobiles to report measurements from the opposite band.
While BAR files can also be generated with the Frequency Allocation Support (FAS), the
Neighboring Cell Support (NCS) should be used if possible.
The NCCPERM defines the allowed NCCs on the BCCH carriers for which MSs are
permitted to send measurement reports. Hence, if all NCCs are used, NCCPERM should
be set accordingly (i.e., all NCCs included in NCCPERM parameter) so that all NCCs are
reported. NCCPERM has no impact on idle mode behavior, since idle mode cell
reselection is based on CGI, and not on ARFCN/BSIC).
The Active BA list Recording may sometimes contain measurement results with
unexpected, disallowed BSICs, (e.g., 00 or 77). This occurs when some MSs report
irrelevant BSICs initially, before decoding actual BSIC information and is not related to a
fault in the BA List recordings feature.
If an operator has not purchased the RNO application to activate BAR recordings through NCS,
the BAR recordings can be activated, using the following BSC command line interface:
May 08
Schema
Page 17 of 28
1. RABRE:RID=RARID00; Terminate an NCS recording.

2. RABIE:RID=BARID00; Delete a recording.
3. RABII; Initiate a new recording.
4. RABRP:RID=BARID00; Print a BAR recording status (optional).
5. RABDC:RID=BARID00, CELL=ALL; Record all BSC cells.
6. RABDC:RID=BARID00,TMBCCHNO=50&&124; Frequencies to measure 50 to 124.*
7. RABDC:RID=BARID00,NUMFREQ=10; The number of test frequencies at each interval.
8. RABDC:RID=BARID00,SEGTIME=15; The 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, beginning as soon
as this command is entered!
14. RABTI:RID=BARID00,IO=FILE; After recording is complete, this command creates the
output binary file in the OSS.
15. RABTI:RID=BARID00, IO=AT-##; Substitute at-## with the number of the AT device
seen when connecting to this BSC. The text output iproduced on the AT-## device**.
* - The relevant frequency set should be used for each specific case.
** - If, for some reason, a binary file cannot be created, the BAR text output can be
generated at the BSC command terminal, with the generated printout being stored as a
text file.
MRR Recordings
2.1.8.2
Measurement Results Recordings (MRR) are files that contain RxLevel, RxQual, and traffic data.
MRR recordings should be generated with, and for the same cell set as, BAR recordings, and
without filtering or thresholds.
An MRR recording may be activated via:
RNO interface (if available): FAJ 122 522, Measurement Result Recording (MRR)
BSC command interface
To make MRR recordings using the RNO interface:
May 08
Schema
Page 18 of 28
1. Log in to OSS.
2. Start RNO.
3. Go to FileNew RecordingMRR.
4. Name the recording session.
5. Enter a Start date.
6. Enter a repeat value (set to daily) and a number of repetitions (set to 5).
7. Enter a date type with working days only (Monday to Friday five consecutive working
days).
8. Enter an hour range (three hours defined to include the network busy hour).
9. Select the cell set or BSC (including every cell in the entire network).
10. Set Cell Filter to a desired (available) frequency band. (The recorded cell set is limited to
a specified frequency band.)
11. Save and schedule the recording.
In the absence of an RNO application, MRR recordings may be activated using the BSC
command line interface, as follows:
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 are recorded.
6. RAMDC: RID=MRRID00, MEASTYPE=NOTYPE; All measurement types are collected.
7. RAMRI: RID=MRRID00, DTIME=120; Recording period time, which starts as soon as this
command is entered!
8. RAMRP: RID=MRRID00; Print status (optional).
9. RAMTI: RID=MRRID00; After the recording is finished, this command should be run to
create the output file.
2.1.9
2.1.9.1.1
Retrieval of Recordings
BA list recordings (BAR) Recordings: Binary mode
Binary format files contain C/I measurements.
May 08
Schema
Page 19 of 28
Once recording is finished, the BARFILs files should be stored for each BSC on FTP. If they are
not stored within 48 hours after recording, they will be deleted from the system.
Binary BARFILs files are located in the following OSS directories:
R8:
o
R9/R10 and later with IOG20:

o
/var/opt/ehpt/eac/data/fs/BSC_NAME/
/root/var/opt/ericsson/nms_eam_eac/data/fs/BSC_NAME/
R9/R10 and later with APG40:

o
/root/var/opt/ericsson/brf/data/db/tmpfileStore/BSC_NAME/
Note:
The binary transfer method should be used to transfer BARFILs from UNIX to Windows via FTP.
All BARFILs recorded on the same day should be stored in the same directory.
The Appendix provides information on troubleshooting situations in which BAR files are not
created.
2.1.9.2
Measurement Results Recordings (MRR) - Binary Mode
When the recording is finished, store the MRRFILs files for each BSC on an FTP. If they are not
stored within 48 hours after recording, they will be deleted from the system.
Binary MRRFILs files are located in the following OSS directories:
R8:
o
R9/R10 and later with IOG20:

o
/var/opt/ehpt/eac/data/fs/BSC_NAME/
/root/var/opt/ericsson/nms_eam_eac/data/fs/BSC_NAME/
R9/R10 and later with APG40:

o
May 08
/root/var/opt/ericsson/brf/data/db/tmpfileStore/BSC_NAME/
Schema
Page 20 of 28
Notes:
Use the binary transfer method to transfer MRRFILs from UNIX to Windows via FTP.
All MRRFILs recorded on the same day should be stored in the same directory.
The Appendix provides information on troubleshooting situations in which MRR files are not
created.
2.1.9.3
NCS Recordings - Text Format Files
NCS Recording files, available in the RNO application window, contain C/I measurements, which
are similar to the information available in the raw binary BAR recordings.
NCS files can be exported from the RNO application window in pairs, one with an *.msmt
extension (data) and one with a *.conf extension (file configurations and recordings
information).
2.1.9.4
MRR Recordings - Text Format Files
MRR Recording files contain RxLevel, RxQual, and traffic data, which can be extracted in either
binary or text formats. Text format can be exported directly form the RNO application window.
Text MRR files are extracted in pairs: one with an *.msmt extension (data) and one with a
*.conf extension (file configurations and recordings).
MRR recordings are exported to ASCII files via the RNO GUI. Both export files (*.msmt and
*.conf) should be transferred. The data from these files may be used to back up MRRFIL files.
2.2
Handover Statistics
Handover statistics for each cell-to-cell relation should be collected for handover optimization.
These statistics should be aggregated for an entire 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
May 08
Schema
Page 21 of 28
Notes:
The following counter can be extracted from 3G OSS for IRAT Handovers from 3G to 2G
cells: pmnoattoutirathospeech
It is not necessary to import 3G to 3G handover attempts, since they are not optimized in
Fort.
2.3
Network Performance Statistics
Network performance statistics should be collected for network traffic modeling and postoptimization network performance benchmarking.
The following network performance statistics should be collected per cell, and calculated hourly
over seven consecutive days:
Overall GSM HO Performance (Cell to Cell Relation, HO Attempts, HO Reversions, HO Lost,).

These statistics should include the following counters: HOVERCNT, HOVERSUC, HORTTOCH,
HOASBCL, HOASWCL, HOUPLQA, HODWNQA, HOATTLSS, HOATTHSS.
Specific IRAT HO performance should be calculated from a 2G network using the following:
The number of handover commands sent to mobile station, with the neighboring UTRAN
cell as target cell (HOVERCNTUTRAN).
The number of successful handovers to the neighboring UTRAN cell (HOVERSUCUTRAN).
The number of handover attempts to the neighboring UTRAN cell when the MS returned
to the old channel (HORTTOCHUTRAN).
The number of handover commands sent to mobile station due to urgency in the GSM
cell, with the neighboring UTRAN cell as target cell (URGHOVERUTRAN).
The number of successful handover attempts, due to urgency in the GSM cell, to the
neighboring UTRAN cell (SUCURGHOUTRAN).
Specific IRAT HO performance should be calculated from a 3G network using the following:
KPI
Voice 3G-2G IRAT HO

Failure Rate (%)
May 08
DESC
Equation
IRAT failure rate for

voice calls when the
trigger is based on an RF
condition. When the
voice call is not
successfully handed over
to GSM network, the call
is returned to the UMTS
network and continues in
UMTS until it attempts
100*[1(pmnosuccessoutirathospeech/pmnoattoutirat
hospeech)]
Schema
Page 22 of 28
another IRAT HO. This

counter will only be
incremented in the
SRNC.
Voice 3G-2G IRAT HO
failures
Total number of voice

IRAT 3G-2G failures.
(pmnoattoutirathospeech pmnosuccessoutirathospeech)
Total Voice 3G-2G IRAT HO

(incl SBHO) Failure Rate
(%)
The IRAT failure rate for

voice calls when the
trigger is based on an RF
condition and a servicebased handover. When
the voice call is not
successfully handed over
to the GSM network, the
call is returned to the
UMTS network and
continues in UMTS until it
attempts another IRAT
HO. This counter will
only be incremented in
the SRNC.
100*[1{pmNoSuccessOutIratHoSpeech+pmNoSucce
ssSbHoSpeech}/{pmNoAttOutIratHoSpeech+
pmNoAttOutSbHoSpeech}]
Total number of IRAT

failures, including
Service based HOs.
[(pmNoAttOutIratHoSpeech+pmNoAttOutSbH
oSpeech)(pmNoSuccessOutIratHoSpeech+pmNoSucce
ssSbHoSpeech)]
The inter-RAT CC from

UTRAN to GPRS when UE
is on DCH. The counter is
increased when the Cell
Change Order From
UTRAN Failure (RRC)
message is received from
the UE.
100*(pmnooutiratccreturnoldch/pmnooutiratc
catt)
PS interactive IRAT HO
failures
Total number of PS
interactive IRAT failures
(pmnooutiratccatt - pmNoOutIratCcSuccess)
Multi-RAB IRAT Failure Rate

(%)
The outgoing (to GSM)

inter-RAT handover
failure rate for multi-RAB
for the best cell in the
active set. The counter is
only incremented in
SRNC.
100*[1{pmNoSuccessOutIratHoMulti/pmNoAttOutIra
tHoMulti}]
Multi RAB IRAT HO failures
Total number of MultiRAB IRAT failures.
(pmNoAttOutIratHoMulti pmNoSuccessOutIratHoMulti)
Total Voice 3G-2G IRAT HO

(incl SBHO) failures
PS Interactive IRAT Failure

Rate (%)
May 08
Schema
Page 23 of 28
Hs Cell Change Failure Rate

(%)
HS Cell Change Failures
2.3.1
The HS Cell Change

failure rate. The counter
stops after a RRC
Physical Channel
Reconfiguration
Complete has been
received from the UE
during the HS-DSCH Cell
Change, or after a RRC
Radio Bearer
Reconfiguration when
there is a PDU size
change during a HSDSCH Cell Change.
100*[1{pmNoHsCcSuccess/pmNoHsCcAttempt}]
Total number of HS Cell

Change failures,
(pmNoHsCcAttempt - pmNoHsCcSuccess)
Network Performance Evaluation
Each KPI improvement rate will be calculated as:
KPI _ improvement _ rate =
KPI before KPI after

KPI before
100%
The improvement in the handover success rate will be calculated as:
Success _ improvement _ rate =
KPI after KPI before

1 KPI before
100%
Each KPI improvement ratio can be calculated separately over a period of five working days
(during each days network busy hour) before and after the optimization cycle.
Any network performance KPIs that are not related to the BSS subsystem should be excluded
from the calculation.
2.3.2
Radio Network Performance KPI Calculation
The following formulae calculate the KPIs that evaluate radio network performance:
Outgoing _ HO _ Success _ Rate =
May 08
(HOVERSUC)
(HOVERCNT)
Schema
Page 24 of 28
Outgoing 3G-2G IRAT HO Failure Rate (%) = (pmnosuccessoutirathospeech /

pmnoattoutirathospeech)
Outgoing 2G-3G IRAT HO Failure Rate (%) = HOVERSUCUTRAN/ HOVERCNTUTRAN
May 08
Schema
Page 25 of 28
Data Collection Checklist

SOURCE
COMMENTS
CHECK
Network Data
GSMS Network Configuration
UMTS Network Topology
(XML)
GSM Sector Coordinates File
UMTS Antennas file
UMTS .mpr file
Generic Loss File
optional
Mobile Measurements & IRAT HO statistics Recordings

Day 1
Day 2
Day 3
Day 4
Day 5
Prior to the measurement

plan
During the measurement
plan
After the measurement plan
Network Performance Statistics (before and after the plan)
IRAT HO failure rate
May 08
UMTS-to-GSM HO attempts
UMTS-to-GSM HO Success
Schema
Page 26 of 28
4 Appendix: Troubleshooting
BARFIL and MRRFIL files are transferred from the BSC to the OSS, once the recording has
finished.
4.1.1
The removeFile Parameter for BARFIL and MRR File Deletion
To check the setting of the removeFile parameter:

1. Connect to the OSS via an external application, such as Citrix ICA Client.
2. Check the file removing option in OSS, which automatically deletes MS files (perhaps to
avoid hard disk space problems). The possible values for this parameter are:
removeFile Value
Result
MS files will not be

removed
MS files will be
removed
Parameters in OSS are stored in Parameter Database (PDB) maps. The removeFile parameter
belongs to the BRF map.
To determine the value of the OSS parameters, use the cap_pdb_get_para command:
cap_pdb_get_para n brf removeFile
The Ericsson Alex Library has additional details.
3. Change the value of the file removing option from 1 to 0, using the cap_pdb_mu
command (with the correct user privileges). (If the file removing option is set to 1, files
will be deleted.) If the BRF map is edited with an editor such as VI, it may lock the
database, and the cap_pdb_mu command may not work with BRF. A user with Super
User access (and perhaps additional knowledge) may be able to resolve this problem.
4. Activate the NCS recording using the RNO.
5. Look for BARFIL and MRRFIL files after completing the collection process, since these
files must be located in their corresponding directories.
6. Return the file removing option to its original value (1) after completing the MS
collection. If this parameter is not changed back to the original value, the result may be
a reduction in hard disk space, in addition to other collateral problems.
May 08
Schema
Page 27 of 28
4.1.2
Additional Ericsson Information
(This material originally appears in official documentation, entitled Operations Support

System (Oss) Rc 1.1, Cp4).
Files retrieved from APG40 are stored in the <dbPath>/tmpFileStore/<bsc> directory.
File
Description
<dbPath>
The path is stated by

the dbPath
parameter in BRF
map.
<bsc>
The BSC.
The removeFile parameter in the BRF map can be set up to delete files automatically, as
explained in the previous section.
4.1.3
Parameter Database (PDB) Maps
Each application has its own parameter database map, with parameters relating to the current
installation.
When the appropriate command is entered in the command shell window (man -s7 <map
name>), additional map information is displayed on the main page.
Application
Map Name
BRF
Brf
FAS
Fas
FOX
Fox
NCS
Ncs
NOX
Nox
TET
Tet
MRR
Mrr
Use cap_pdb_mu to edit the map.

Note:
To edit system parameters, select RNO System Parameters from the Options menu in the
RNO main window.
May 08
Schema
Page 28 of 28

Ultima Forte Required Data Inputs For Ericsson Markets 2g-3g Infrastructure PDF

Uploaded by

Copyright:

Available Formats

Ultima Forte Required Data Inputs For Ericsson Markets 2g-3g Infrastructure PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ultima Forte Required Data Inputs For Ericsson Markets 2g-3g Infrastructure PDF

Uploaded by

Copyright:

Available Formats

Ultima Fort Required Data Inputs for Ericsson Markets 2G-3G Infrastructure

Copyright 2008 Schema

Proprietary and Confidential

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

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

Network Data ........................................................................................................6

GSM Network Configuration....................................................................6

Handover Statistics ....................................................................................... 21

Network Performance Statistics ...................................................................... 22

Data Collection Checklist......................................................................... 26

Appendix: Troubleshooting ..................................................................... 27

Proprietary and Confidential

Proprietary and Confidential

Ericsson BSS network configuration data (XML format)

UMTS system network configuration (vendor XML format or Schema Format)

GSM Sector coordinates data

UMTS antenna file

UMTS-to-GSM handover statistics

UTRAN neighboring cell quality measurements

Generic Loss File (optional)

Nokia BSS network configuration data (XML format)

UMTS system network configuration (vendor XML format or Schema Format)

GSM Sector coordinates data

UMTS antenna file

UMTS-to-GSM handover statistics AKA Counter 93 (Section 2.3)

UTRAN neighboring cell quality measurements AKA Counter 94 (Section 2.3)

Generic Loss File (optional)

Proprietary and Confidential

Required Information and Data

The definition of the network area to be optimized is:

List of cells (from both networks) in the optimization area

Proprietary and Confidential

GSM Network Configuration

2.1.1.1 CNA Export in Text Format

BSC data is optional beginning from Release R12.

Proprietary and Confidential

2.1.1.2 New CNAI Export Format - R12:

UMTS Network Configuration (XML Format)

Proprietary and Confidential

Figure 1: Retrieve the Required BSS Network Configuration Files

Figure 2: Export the Required BSS Network Configuration Files

Proprietary and Confidential

Choose the File Name and Radio topology.

Figure 3: Save the Required BSS Network Configuration Files

Sector Coordinates File

Proprietary and Confidential

UMTS Antenna File

RTT fix A Coefficient

RTT fix B Coefficient

Proprietary and Confidential

Generic Loss File

Proprietary and Confidential

The following is a full example of the file:

Mobile Measurement Data Recordings

The following activities should stop during data recording:

BSC or RNC split

Site re-parenting (e.g., BSC/site relation changes in the GSM network)

Site and carrier additions