Documente Academic
Documente Profesional
Documente Cultură
Your feedback is important to us: The TEOCO Documentation team takes many measures in order
to ensure that our work is of the highest quality.
If you found errors or feel that information is missing, please send your Documentation-related
feedback to Documentation@teoco.com
Thank you,
The TEOCO Documentation team
Date
Author
Change Description
iv
Table of Contents
Table of Contents
1
Introduction .............................................................................................. 1
1.1
4.2
Installation ................................................................................................... 14
6.2
Configuration ................................................................................................ 14
6.3
6.4
6.5
iii
Introduction
1 Introduction
The following document contains a list of all the required information and data to be collected
on NSN UMTS infrastructures in preparation for the installation of the Mentor optimization tool.
The information and data required includes the following:
Schema Format
Network Preferences
MegaMon logs
XML counters
HO handoff
NL neighbor list
Description
Data Source
Reference
NSN RNC
Section 3.1.1
Antenna file
Planning tool,
internal
database
Section 3.1.3.1
Terrain file
TAB, GRD,
GeoTiff
Section 3.1.3.2
Antenna profiles
Planet format
and others
Section 3.1.3.3
MegaMon tool
Section 4.1
NetAct
Section 4.2
Check
Schema Format files, including complete information required for physical sites and soft
parameter configuration (depending on availability) in text format.
3.1.1
The UMTS network configuration data is contained in an XML file in standard 3GPP format.
The other option, which is also applicable for server deployments, is to use the ready-made
OSS script:
The highlighted part is the DistName of the RNC to be exported (for example: PLMNPLMN/RNC-40)
3.1.2
Note: This is an optional input used for IRAT optimization and for displaying the GSM topology.
A special retrieval procedure can be used on the OSS for each of the underlying GSM vendors.
Moreover, a physical topology file, coordinates.txt, similar to the one needed for UMTS, is
required.
TEOCO can provide detailed documentation on how to perform this operation, if necessary.
3.1.3
The physical parameters of the network, such as the sector and antenna location, and the
antenna profiles, may not be available through the configuration dump.
Most of the required physical configuration of the network can be derived from network
planning tools or from customer-self-maintained databases with the most updated network
configuration.
Mentor defines a set of textual files that should be available. These files are:
Antenna file - includes the physical configuration of each sector. See section 3.1.3.1 below
for the file format.
In contrast to planning tools or other configuration sources, Mentor requires only active sector
carriers. Sectors that are inactive during an analyzed period should be marked as inactive in
the antenna files.
All soft parameters may be defined in this file, but will be overridden by the Network Topology
files. It is recommended that the latest Network Topology files be used to update the Schema
Format file and to identify any inconsistencies, such as missing or unnecessary sectors.
Physical constraints
Network topology
The antenna file must include all sectors selected for optimization and all sectors in the guardzone area, where optimization is not performed. It is recommended that all sectors within two
tiers of the selected sectors be included.
Mandatory?
Description
Default
Value
RNC Name
TRUE
RNC ID
TRUE
Vendor
TRUE
NodeB Name
TRUE
NodeB Id
TRUE
NodeB Longitude
TRUE
NodeB Latitude
TRUE
Sector Name
TRUE
Active
TRUE
TRUE
Missing Data
TRUE
FALSE
Noise Figure
TRUE
AntennaID
TRUE
Antenna Model
TRUE
Sector Keywords
FALSE
Antenna Longitude
TRUE
Antenna Latitude
TRUE
Height
TRUE
Mechanical DownTilt
TRUE
Mechanical tilt
Azimuth
TRUE
Downlink Loss
TRUE
Uplink Loss
TRUE
TRUE
TRUE
RET ID
FALSE
In Building
TRUE
In Use
Parent of cell
FALSE
Sector
Latitude
Longitude
Azimuth
LAC (optional)
CI (optional)
The latitude and longitude values should be expressed in decimal-degree format, with up to six
digits following the decimal point.
Retrieval Procedure
The OMS configuration should be changed in order to store XML measurement files in the
following folder: /var/opt/OMSftproot/xmlfilesBU
1. Go to the Parameter Tool GUI in the RNC Element Manager.
2. Open LDAP path: ClusterRoot/OMS/OMSPlatform/SS_GenericPM/OMSNMSFWriter/
3. Double-click BackupEnabled and set it to 1.
After these steps, the XML measurement files will be stored in to the
var/opt/OMSftproot/xmlfilesBU directory. The files will be deleted automatically 7 days
after creation.
10
4.2.2
4.2.3
Counters
Mandatory counters
M1000
M1001
M1002
M1008
M1010
M1022
M5000
M5101
11
12
Monitoring
Logging / If Logging
Emil
Filter Basic_RU20_geo
LOG_DIRECTORY=D:\\LOGS
#Dallas Market
HOST[1]=5.209.4.160
PORT[1]=12345
OUTPUT_DIRECTORY[1]=\\\\RFNSNQ04\\geo\\Model\\Logs\\all\\DARNC001
2. It is important to note that for all the RNCs the Host number must be in the correct order,
or it will cause the service to stop.
3. Once this is set, start the NSN collector service from the services.
13
The first 2 executables will create on their first run a .properties file with a name matching their
name. For the NSNCollectorApplication, this file is used to keep the last configuration used
between runs. For the NSNCollectorService, the file is used to employ changes in the service
configuration and the service should be restarted if the file is updated.
6.2 Configuration
The configuration of the NSNCollectorService is controlled through the
NSNCollectorService.properties file created in the installation folder. On the first run of the
service, if the file does not exist a template file will be created with instructions on how to edit
and modify the file. Once the file is modified and saved, the service should be restarted in order
for the changes to take effect.
14
.log files in the directory of the installation or in any other directory configured through
the .properties file if you are running it as a service.
Files containing the data transmitted from the NSN MegaMon. These files are created in
the directory specified to the collector either in the GUI or in the .properties file.
Make sure that the .log files dont contain any error or warning messages
Make sure that files are created and accumulated in the dump folder of the collector
Occasionally connect to the MegaMon machine and make sure that no errors or warnings
appear on the MegaMon software
15