Ul tim ti m a™ Me Mentor nt or Requir qu ire ed Da Data Inp Input uts s for f or NSN Infrastructure
Confidentiality, Copyright Notic e & Discl Discl aimer Due to a policy of continuous product development and refinement, TEOCO Ltd. (and its affiliates, together “TEOCO”) reserves the right to alter the specifications, representation, descriptions and all other matters outlined in this publication without prior notice. No part of this document, taken as a whole or separately, shall be deemed to be part of any contract for a product or commitment of any kind. Furthermore, this document is provided “As Is” and without any warranty. This document is the property of T EOCO, which owns the sole and full r ights including copyright. TEOCO retains the sole property rights to all information contained in this document, and without the written consent of TEOCO given by contract or otherwise in writing, the document must not be copied, reprinted or reproduced in any manner or form, nor transmitted in any form or by any means: electronic, mechanical, magnetic or otherwise, either wholly or in part. The information herein is designated highly confidential and is subject to all restrictions in any law regarding such matters and the relevant confidentiality and non- disclosure clauses or agreements issued with TEOCO prior to or after the disclosure. All the information in this document is to be safeguarded and all steps must be taken to prevent it from being disclosed to any person or entity other than the direct entity that received it directly from TEOCO. TEOCO and Netrac® are trademarks of TEOCO. All other company, brand or product names are trademarks or service marks of their respective holders. This is a legal notice and may not be removed or altered in any way. COPYRIGHT © 2013 TEOCO LTD. ALL AL L RIGHTS RESERVED. RESERVED.
Your feedback feedback is import ant 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 m issing, please send your Documentation-related feedback to
[email protected] Thank you, The TEOCO Documentation team
Document Revision History Ver
Date
Author
Change Description
iv
Table of Contents
Table of Contents 1
Introduction .............................................................................................. 1 1.1
Definitions, Acronyms, and Abbreviations ........................................................... 1
2
Mentor Preliminary Setup Checklist .......................................................... 2
3
Detailed Description of Required Information and Data ............................ 3 3.1
Network Configuration Data .............................................................................. 3 3.1.1 NSN Switch Dump – XML Configuration .................................................... 3 3.1.2 GSM Network Topology .......................................................................... 5 3.1.3 Antenna and Sectors Physical Location, Profiles, and Parameters in Delimited Format x ........................................................................................................ 5
4
NSN Logs and Stats ................................................................................... 9 4.1
Log Files (MegaMon Logs) ................................................................................. 9
4.2
Stats (PMs) File ............................................................................................. 10 4.2.1 Retrieval Procedure .............................................................................. 10 4.2.2 Activating Key Counter Measurements.................................................... 11 4.2.3 Counters ............................................................................................ 11
5
Appendix A: Step-by-Step Guide for Collecting Data from MegaMon ....... 12
6
Appendix B: NSN Collector Service .......................................................... 14 6.1
Installation ................................................................................................... 14
6.2
Configuration ................................................................................................ 14
6.3
Monitoring the NSN Collector........................................................................... 15
6.4
Stopping the NSN Collector Service .................................................................. 15
6.5
Scheduling Collection Periods for the NSN Collector Service ................................ 15
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 M entor optimization tool. The information and data required includes the following: •
•
Network configuration (described in detail in section 3) o
Schema Format
o
Network Topology file (XML)
o
Network Preferences
NSN logs and stats (described in detail in section 4) o
MegaMon logs
o
XML counters
When preparing to set up Mentor in a network, it is usually recommended to start by creating the network configuration, followed by a sample data collection. Section 2 outlines a “setup checklist”, which should be used as a first step to facilitate efficient installation and configuration. The following sections of this document provide a more i n-depth description of the required data sources, and the manner in which they can be obtained.
1 .1 D ef i n i t i o n s , A c r o n y m s , an d A b b r e v i at i o n s The following definitions, acronyms, and abbreviations are used throughout this document: •
HO – handoff
•
HHO – hard handoff
•
NL – neighbor list
•
RNC - Radio Network Controller
•
RAB – Radio Access Bearer
1
Ultima™ Mentor Required Data Inputs for NSN Infrastructure
2 Mentor Prelimi nary Setu p Checkli st The following table summarizes the minimal data required for the kickoff of a Mentor installation. This table should be used as a reference to expedite the installation process. These files can be collected by TEOCO professional services on site, or by the customer point of contact. Mandatory files and definitions:
2
Descrip tio n
Data Source
Reference
1
NSN Switch Dump
NSN RNC
Section 3.1.1
2
Antenna file
Planning tool, internal database
Section 3.1.3.1
3
Terrain file
TAB, GRD, GeoTiff
Section 3.1.3.2
4
Antenna profiles
Planet format and others
Section 3.1.3.3
5
MegaMon log files
MegaMon tool
Section 4.1
6
NSN XML Counters
NetAct
Section 4.2
Check
Detailed Description of Required Information and Data
3 Detailed Descr ip tio n of Requi red Infor mation and Data 3.1 Netw ork Confi gur ation Data The sources for network configuration data are: •
•
Schema Format files, including complete information required for physical sites and soft parameter configuration (depending on availability) in text format. Network configuration file exported from the NetAct.
3 .1 .1
N SN S w i t c h D u m p – X ML C o n f i g u r a t i o n
The UMTS network configuration data is contained in an XML fi le in standard 3GPP format.
3.1.1.1 Retrieval Procedure In order to retrieve the required RNC network configuration data from the Nokia OSS, the most convenient option is to use the export of the actual configuration from the CM Operational Manager. 1. Go to the CM Operations Manager (via Citrix, X-Terminal, or the OSS workstation).
Figure 1: CM Operation Manager in the main window 2. Go to File
Export Actual Configuration.
3
Ultima™ Mentor Required Data Inputs for NSN Infrastructure
3. Choose the RNCs in the ActualConfiguration pane for all cells in the optimization and guard-zone areas.
Figure 2: Export of Actual Configuration 4. Set the output parameters values to Internal Values (mandatory action for OSS 5.2 and above) 5. Click Start.
The other option, which is also applicable for server deployments, is to use the ready-made OSS script:
racclimx.sh -op Import_Export -fileFormat RAML2 -importExportOperation actualExport -DN PLMN-PLMN/RNC-XX -fileName
The highlighted part is the DistName of the RNC to be exported (for example: PLMNPLMN/RNC-40)
4
Detailed Description of Required Information and Data
3 .1 .2
G SM N et w o r k T o p o l o g y
Note: This is an optional input used for IRAT optimization and for di splaying 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 n eeded for UMTS, is required. TEOCO can provide detailed documentation on how to perform this ope ration, if necessary.
3 .1 .3
A n t e n n a a n d S ec t o r s P h y s i c a l L o c a t i o n , P r o f i l e s , a n d P ar a m e t e r s i n D e l i m i t e d F o r m a t x
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.
•
Antenna profiles – antenna-pattern data files
•
Mentor also requires an updated Terrain file
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 i nconsistencies, such as missing or unnecessary sectors.
5
Ultima™ Mentor Required Data Inputs for NSN Infrastructure
3.1.3.1 Antenna File The antenna file (in tab-delimited text format) includes the physical configuration of each sector, including: •
Location data (i.e., coordinates, height, and so forth)
•
Antenna characteristics (i.e., height, azimuth, and so forth)
•
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 i s recommended that all sectors within two tiers of the selected sectors be included.
6
Detailed Description of Required Information and Data
The Antenna file fields are described below. Field
Mandatory?
Description
Default Value
RNC Name
TRUE
Unique in the network - RNC display name
RNC ID
TRUE
Unique in the network
Vendor
TRUE
The vendor of the RNC
NodeB Name
TRUE
Site display name
NodeB Id
TRUE
Unique under the same RNC
NodeB Longitude
TRUE
NodeB Latitude
TRUE
Sector Name
TRUE
Active
TRUE
TRUE
Missing Data
TRUE
FALSE
Noise Figure
TRUE
AntennaID
TRUE
Unique under the same cell
Antenna Model
TRUE
Lookup from antenna DB
Sector Keywords
FALSE
Comma-separated list of keywords, if any
Antenna Longitude
TRUE
Antenna Latitude
TRUE
Height
TRUE
Height of the antenna above ground
Mechanical DownTilt
TRUE
Mechanical tilt
Azimuth
TRUE
Downlink Loss
TRUE
0
Uplink Loss
TRUE
0
RTT fix A Coefficient
TRUE
1
RTT fix B Coefficient
TRUE
0
RET ID
FALSE
In Building
TRUE
In Use
Parent of cell
FALSE
Table 1: Antenna File Parameters Note: If UTM coordinates are used, the relevant column headers should be different: NodeB X, NodeB Y, Antenna X, and Antenna Y.
7
Ultima™ Mentor Required Data Inputs for NSN Infrastructure
3.1.3.2 Terrain File The terrain map should be in GeoTif data format. It is recommended that the map resolution be at least 50m. Mentor can support additional terrain file formats, such as TAB, GRD, etc.
3.1.3.3 Antenna Profiles Antenna-pattern data files are in Planet format.
3.1.3.4 Coordi nates File for GSM Network The sector coordinates file should be in tab-delimited text file format, and should i nclude geographical information for all of the network sectors, including the following columns: •
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.
8
NSN Logs and Stats
4 NSN Lo gs and Stats 4.1 Log Files (MegaMon Log s) Log files can be collected using the NSN and TEOCO integrated solution. The following features are mandatory: 1. RNC3372 L3 Data Collector or TSS3101 (3G) L3 Data Coll ector (MegaMon) 2. RNC3393 GEO Interface or TSS3104 (3G) GEO Interface The following filter string should be set in the MegaMon collection application: SR:((OFAM=4FD,508,509,9B6,9B7,997)AND(NOT(NUM=8037,8038,0D7A6,0D5BA,9904,9835,9836,0AB2E,0D5 B8,02AB)))OR(NUM=0C5DF,0E47B,0CDA9)
For more information on the MegaMon configuration, see Appendix A. Notes: 1. In order to collect data from all cells in the RNC, all ICSUs should be defined in the Megamon collection application. 2. If Megamon is used for purposes other than the TEOCO Mentor tool, and data is written to its own disk space, it should be configured to delete old data when free disk space is below a certain threshold. This threshold should be large enough to al low it to function properly. 3. TEOCO uses a data-collector application in order to integrate its server to Megamon in the GEO interface. The GEO interface is a streaming TCP/IP message interface. The TEOCO collector installation instructions are described in Appendix B. Contact TEOCO support in order to receive the installation files. 4. Network bandwidth of the Geo interface between the TEOCO Coll ector and the Megamon machine should be minimal as a result of one of the following calculations: •
Erlangs - Every Erlang on the RNC requires 0.5Kbps.
•
Cell count - Every cell on the RNC requires 15Kbps.
9
Ultima™ Mentor Required Data Inputs for NSN Infrastructure
The following figure summarizes the TEOCO-NSN MegaMon solution architecture:
4.2 Stats (PMs) Fil e 4 .2 .1
R et r i e v a l P r o c e d u r e
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
NSN Logs and Stats
4 .2 .2
A c t i v a t i n g K e y C o u n t e r M ea s u r e m e n t s
1. Go to the RNW Measurement Management application. 2. Check that all measurements presented in the picture below are activated (green triangle means that measurements are active):
Figure 3: RNW Measurement Management
4.2.3
Counters
Mandatory counters
M1013 – Intra-frequency neighbor
M1015 – IRAT neighbor list optimization
M1014 - Inter-frequency neighbor
M1028 – Detected Cell EC/NO measurements
M1000
M1001
M1002
M1008
M1010
M1022
M5000 M5101
11
Ultima™ Mentor Required Data Inputs for NSN Infrastructure
5 App endi x A: Step-by-Step Guid e fo r Coll ecting Data fr om MegaMon This appendix describes the required settings for MegaMon and the Emil Collector on the MegaMon and Emil Client Collector. For sample output directories, please contact TEOCO support. MegaMon Server (connected to RNC) 1. Open the MegaMon program, shown below.
Figure 4: MegaMon Setup 2. Set options. Note: These must be set before you start the program.
12
•
Monitoring
•
Logging / If Logging
•
Emil
Appendix A: Step-by-Step Guide for Collecting Data from MegaMon
3. Get Units. 4. Set Filters (only for ICSUs that show an address). •
Filter – Basic_RU20_geo
•
Logs – Get All
5. Start the Emil client on MegaMon. •
Set to auto reconnect
6. Start the Emil Collector service. 7. Start the MegaMon program. 8. The collections should create a temporary file in your output location. 10 files are generated every 15min into a folder separated by date. Collection Server 1. Set the properties file in the Emil folder, where the setup foll ows the following format: •
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.
Figure 5: Emil GEO Server Setup
13
Ultima™ Mentor Required Data Inputs for NSN Infrastructure
6 App endi x B: NSN Coll ector Service 6.1 Ins tallati on The NSN Collector Service arrives as a single executable installer. To install, it double-click the executable file and follow the instructions on screen. The installation directory will then include 3 executables when the NSNCollectorService.exe is up and running: •
•
•
NSNCollectorApplication.exe – a collector supporting a single RNC, which is controlled through the GUI. Should be used for debugging purposes. NSNCollectorService.exe – a collector supporting multiple RNCs, which is run as a Windows Service and configured through the .properties file NSNCollectorServiceShutdown.exe – a utility executable for a smooth shutdown of the Collector Service
The first 2 executables will create on their fi rst 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 fil e is updated.
6 .2 C o n f i g u r a t i o n 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
Appendix B: NSN Collector Service
6.3 Monit ori ng th e NSN Collect or The NSN Collector in both modes (GUI or Service) creates two artifacts: •
•
.log files in the directory of the installation or in any other di rectory configured through the .properties file if you are running it as a service. Files containing the data transmitted from the NSN MegaMon. These fil es are created in the directory specified to the collector either in the GUI or in the .properties file.
To monitor the collector you should: •
Make sure that the .log files don’t 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
6.4 Stoppi ng the NSN Collect or Serv ic e For smooth operation of the collector service, it i s recommended to stop it using the provided executable NSNCollectorServiceShutdown.exe and not by using Windows facilities for stopping running services.
6 .5 Sc h e d u l i n g C o l l e c t i o n P er i o d s f o r t h e N SN C o l l e c t o r Service Currently NSN RNCs emit larger amounts of data than we are able to process overnight. Therefore, our present solution for NSN markets will be based on collecting data during part of the day only. In order to configure the collector to work only at specified times, you should use the Windows Task Scheduler to start and stop the NSN Collector Service periodically. Please note that for stopping the service it is recommended to use the executable mentioned above. Please also notice that there might be a time zone difference between the coll ecting machine running the service and the market/RNC. This should be taken into account when creating the scheduler tasks. In addition, since a single collector service collects from mul tiple RNCs, it is possible that they do not all share the same time zone. In t his case, the collection period should be extended and calculated so that meaningful data is collected from all RNCs monitored by that collector.
15
