Professional Documents
Culture Documents
Ultima Forté: Required Data Inputs For Ericsson Markets 2G-3G Infrastructure (For Version 4.0 and Above)
Ultima Forté: Required Data Inputs For Ericsson Markets 2G-3G Infrastructure (For Version 4.0 and Above)
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.
Table of Contents
1 Introduction.............................................................................................. 4
2 Required Information and Data................................................................. 5
2.1 Optimization Area ...........................................................................................5
Network Data ........................................................................................................6
2.1.1 GSM Network Configuration....................................................................6
2.1.2 UMTS Network Configuration (XML Format) ..............................................7
2.1.3 Sector Coordinates File ..........................................................................9
2.1.4 UMTS Antenna File.............................................................................. 10
2.1.5 *.mpr File.......................................................................................... 11
2.1.6 Generic Loss File................................................................................. 11
2.1.7 Mobile Measurement Data Recordings .................................................... 12
2.1.8 Activation of Recordings ...................................................................... 13
2.1.9 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
3 Data Collection Checklist......................................................................... 26
4 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
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
1 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.
• 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.
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.
Network Data
Retrieve the required BSS network configuration file from the Ericsson OSS, using the Cellular
Network Administrator (CNA), by running the following commands:
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:
Data Description
Cell Resources
RLCRP:CELL=ALL,DETAIL;
Details
Managed Object
RXMOP:MOTY=RXOTG;
Data
BSC Exchange
RAEPP:ID=ALL;
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.
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.
To retrieve the required BSS network configuration files from the Ericsson OSS:
2. Right click on the root of the network and select Export Network Configuration.
• 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.
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
The following file has a sample entry that corresponds to one antenna.
Antennas.txt
ERICSSON_XML_FILE_NAME=path\topology_file_name.xml
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:
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
GenericLossFile.txt
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
Note: BSC Version R06A (R12) (or later versions) should be used.
• 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:
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).
• RNO interface (if available): FAJ 122 477 Neighboring Cell Support - GSM RAN (NCS-G)
1. Log in to OSS.
2. Start RNO.
3. Go to FileÆNew RecordingÆNCS.
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).
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.
• The maximum number of test UMFIs that may be added to the 3G active mode BA lists
at one time.
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
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.
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:
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 should be generated with, and for the same cell set as, BAR recordings, and
without filtering or thresholds.
• RNO interface (if available): FAJ 122 522, Measurement Result Recording (MRR)
1. Log in to OSS.
2. Start RNO.
3. Go to FileÆNew RecordingÆMRR.
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.)
In the absence of an RNO application, MRR recordings may be activated using the BSC
command line interface, as follows:
7. RAMRI: RID=MRRID00, DTIME=120; Recording period time, which starts as soon as this
command is entered!
9. RAMTI: RID=MRRID00; After the recording is finished, this command should be run to
create the output file.
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.
• R8:
o /var/opt/ehpt/eac/data/fs/”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.
• R8:
o /var/opt/ehpt/eac/data/fs/”BSC_NAME”/
• R9/R10 and later with IOG20:
o /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”/
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.
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).
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.
• Serving Sector
• Target Sector
• Handover Attempts
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é.
The following network performance statistics should be collected per cell, and calculated hourly
over seven consecutive days:
Each KPI improvement ratio can be calculated separately over a period of five working days
(during each day’s 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.
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
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:
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
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.
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.
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.
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.
Note:
To edit system parameters, select RNO System Parameters from the Options menu in the
RNO main window.