Ultima™ Mentor
Required Data Inputs for
Ericsson Infrastructure
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 TEOCO, which owns the sole and full rights 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 © 2014 TEOCO LTD. ALL RIGHTS RESERVED.
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 [email protected]
Thank you,
iii
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 Ericsson 3G Network Topology (XML format) ... 3
3.1.2 GSM Network Topology ... 8
3.1.3 Antenna and Sectors Physical Location, Profiles, and Parameters in Delimited Format 8 4 Ericsson Logs and Stats ... 11
4.1 GPEH Log Collection and Setup ... 11
4.1.1 GPEH Profile ... 11
4.1.2 Retrieval Procedure ... 17
4.1.3 Events to Record ... 17
4.2 Stats File (XML) ... 18
4.2.1 Configuring Counters in OSSRC ... 18
4.2.2 RBS Counters Required for Proper HSPA Analysis ... 18
4.2.3 Retrieval Procedure ... 19
4.3 Templates ... 19
4.4 RES Activation and Properties (WMRR) ... 19
4.4.1 Setting up a WMRR Recording ... 20
4.4.2 RES Results ... 23
4.5 Folder Structure for GPEH and Counter Files ... 23
4.6 RPMO Recordings ... 24
4.6.1 Logs Collection and Setup ... 24
1 Introduction
This document contains a list of all the required information and data to be collected on Ericsson UMTS infrastructures in preparation for the installation of the Mentor optimization tool. The information and data required includes the following:
• Network configuration (detailed in section 3)
o Ericsson Network Topology file (XML format)
o Antenna and sectors physical location, profiles, and parameters in delimited format (internally known as Schema format)
o GSM Network Topology (Optional, for running an IRAT optimization and displaying the GSM layer)
• UMTS logs and counter data (detailed in section 4)
o GPEH logs
o Counters file (XML format) o RBS logs
When preparing to set up Mentor in a network, we usually recommend starting 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 in-depth description of the required data sources, and the manner in which they can be obtained.
1.1 Definitions, Acronyms, and Abbreviations
The following definitions, acronyms, and abbreviations are used throughout this document: • HO – Handoff
• HHO – Hard Handoff • NL – Neighbor List
• RNC - Radio Network Controller
• GPEH – General Performance Event Handler • RAB – Radio Access Bearer
2
2 Mentor Preliminary Setup Checklist
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
Description Data source Reference Check
Ericsson XML configuration dump Ericsson OSSRC 5.x/6.x/12 See section 3.1.1 Antenna File
Please also specify UTM Zone, Projection used.
Planning tool (Mentum Planet, Forsk Atoll etc.), internal DB
See section
3.1.3.1
Terrain file TAB, GRD, GeoTiff See section
3.1.3.2
Antenna Profiles Planet formats and others
See section
3.1.3.3
GPEH LOG files (sample 1 hour) Important: • GPEHfileSize: 60000 per RNC • UEfraction: 1000 Ericsson P5/P6/P7/W10/W12 See section 4.1
Ericsson Counter files Ericsson
P5/P6/P7/W10/W12
See section 4.2
RBS counter files See section 4.2.3
Optional files and definitions
Description Data source Reference Check
Optional files for special cases only
Description Data source Reference Check
1 RES periodic reporting (WMRR)
Reports should include:
Ec, EcIo, UeTxPower
Ericsson
P5/P6/P7/W10/W12
See section 4.4
Note: TEOCO recommends using RES recordings for a limited time only, and mainly for creating
the UeTxPower maps.
3 Detailed Description of Required Information
and Data
3.1 Network Configuration Data
The sources for network configuration data are:
o A predefined set of Network Topology files exported from the Ericsson OSS in XML format.
o Textual files, including complete information required for physical sites and soft parameter configuration, depending on availability (“Schema Format”).
IMPORTANT – Mentor includes an automatic wizard that generates most of the textual files
required for its operation, based on the data commonly available in the service provider environment.
3.1.1
Ericsson 3G Netw ork Topology (XML format)
There are several options to generate the Ericsson XML configuration files. Many variants exist, which will generate different content within the XML files.
The Mentor product makes use of an elaborated configuration file, which contains all of the RNC and NodeB parameters. Using this type of file enables Mentor to identify and warn about configuration problems, use the RBS counters as well as create an accurate model of the network.
The network topology dump might already be activated in the network. Follow the procedure in section 3.1.1.1 to verify whether the dumps have already been created, or run them directly from
4
3.1.1.1 Generating the XML Configuration Using Scripts
First check if the configuration files are already available in the following directory:
/var/opt/ericsson/nms_umts_wran_bcg/files/export
You can use the UNIX scripts in the OSS that periodically generates the XML configuration file. The shells script is called start_rah_export.sh, and is located in the following directory:
opt/ericsson/nms_umts_wran_bcg/bin/
Further information can be found in the ALEX system through:
“Bulk Configuration System Administrator Guide 1/1543-APR 901 550/2 Uen E “ “Bulk Configuration General and Transport User Guide”
“Bulk Configuration System Administrator Guide”
3.1.1.2 Generating the XML Configuration File Using the OSSRC
IMPORTANT: Because of an internal Ericsson issue, we recommend exporting the entire
network configuration and not only a specific RNC. See chapter 3.1.1.3 for an explanation as to how to analyze the results.
1. Launch>>Applications>>Ericsson>>OSS Common Explorer.
2. Ensure that the combo box under WCDMA menu has the value RNC/RBS.
3. Right-click Root (red icon) -> Export configuration. Can be performed up to RBS level. 4. Change the file name (optional).
5. Select the Both radio and transport topology option (3rd radio button). 6. Click Next and then Finish.
6
3.1.1.3 Working with Ericsson XML files and checking their validity
Ericsson OSS will not export the NodeB information when only exporting a single RNC.
TEOCO recommends verifying the data using an external XML reader, such as “XML Marker”. (http://symbolclick.com/download.htm)
When loading a single RNC xml dump without the NodeB information, you will see a picture similar to the one listed below. Under the main “SubNetwork” folder, there is an individual “SubNetwork” for each RNC.
An XML dump that contains NodeB data will include additional information under the RNC “SubNetwork” such as “ExternalGsmCell”, etc.
Sometimes, it is not possible to open a large XML file with an XML editor (usually over 750MB). In this case, use TEOCO’s scripts to divide the file into the different RNCs, or manually cut-out RNCs between the two XML directives:
<xn:SubNetwork id="RNC01">
And
8
3.1.2
GSM Network Topology
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 underlying GSM vendor. Moreover, a physical topology file is required, similar to the one needed for UMTS.
TEOCO can provide detailed documentation on how to perform this operation, if required.
For example, for Ericsson GSM networks the following “standard” procedure should be
followed (additional variants are available, depending on the specific versions). This is only an excerpt from the full document.
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)
3.1.3
Antenna and Sectors Physical Location, Profiles, and
Parameters in Delimited Format
The physical parameters of the network, such as the sector and antenna location, and the antenna profiles, might not be available through the OSS 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 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. We recommend 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.
3.1.3.1 Antenna File
The antenna file (in tab-delimited text format) includes the physical configuration of each sector, including:
o Location data (i.e., coordinates, height, and so forth) o Antenna characteristics (i.e., height, azimuth, and so forth) o Physical constraints
o Network topology
The antenna file must include all sectors selected for optimization and all sectors in the
guard-zone area – where optimization is not performed. We recommend that all sectors
within two tiers of the selected sectors be included. The Antenna file fields are described in Table 1:
Field Value Range Description Default
RNC Name String Unique in the network RNC display name
RNC ID String Unique in the network
RNC Vendor String The vendor of the RNC NodeB Name String Site display name
NodeB ID String Unique under the same RNC NodeB Longitude Double
NodeB Latitude Double
Sector Name String Parent of cell
Antenna ID String 50ch max Unique under the same cell Antenna Model String Lookup from antenna DB
Sector Keywords String 1000ch max Comma-Separated list of keywords, if any Antenna Longitude Double
Antenna Latitude Double
Antenna Height Integer 0…200 Height of the antenna above ground Antenna Electrical
DownTilt Integer -20 …+20 Electrical tilt Antenna Mechanical
DownTilt Integer -20 …+20 Mechanical tilt Antenna Azimuth Integer 0…359 Azimuth UL Cable Loss Double 0…20 With step 0.1
10
Note: If UTM coordinates are used, the relevant column headers should be different:
NodeB X, NodeB Y, Antenna X, and Antenna Y.
3.1.3.2 Terrain File
The terrain map should be in GeoTif data format. We recommend 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
4 Ericsson Logs and Stats
The General Performance Event Handler (GPEH) files contain periodic and event-triggered mobile and NodeB reports, which enable Mentor to model the network.
The following procedure should be used to define GPEH and Stats profiles, generate them, and collect them for use in Mentor.
4.1 GPEH Log Collection and Setup
4.1.1
GPEH Profile
For the GPEH files to have the necessary information required for Mentor to operate, the correct profile must be defined in the OSSRC. The following procedure can be used to set the profile:
INPORTANT - The following parameters must be defined correctly:
• UeFraction=1,000 • GPEHfileSize=60,000
• Mentor can operate with reduced values for these parameters. To define a different set of values, please consult TEOCO support.
To add the GPEH profile:
1. Launch>>Applications>>Ericsson>>Performance>>Initiate data Collection>>WCDMA/LTE RAN Measurements
12
2. Administration -> Add profile.
3. General performance event handling profile (fourth radio button). Next.
5. Choose entity type - RNC / RBS (usually RNC). Next.
6. Choose RNC from left to right (only one can be chosen). Next. 7. Choose Cells from left to right. Next.
14
8. Choose which events to record from left to right. NOTE: Detailed event list is listed in section
16
10. Recording activation by using "Resume profile" option or Scheduler information - see Using scheduler. Finish.
To view and change the profiles go to the General performance profile tab.
Changing the GPEH recording profile from “Headers data only” to “All data”:
1. [Read / Edit] GPEH data level (Edit - only in admin user type).
2. Change GPEH data level from Headers data only to All data (Admin users only). 3. Close the window.
4.1.2
Retrieval Procedure
The GPEH files are generated through the Ericsson OSS.
In OSS P5 the GPEH files are located in:
/var/opt/ericsson/nms_umts_pms_seg/segment1/red/downloaded/gpeh
In OSS 5.x/6.x/12 the GPEH files are located in:
/var/opt/ericsson/nms_umts_pms_seg/segment1/GPEH/SubNetwork=<RNC Name>/MeContext=<RNC NAME>
Where <RNC NAME> is the name of the RNC you have to complete
For example.
/var/opt/ericsson/nms_umts_pms_seg/segment1/GPEH/SubNetwork=EVO1/MeContext=EVO 1
4.1.3
Events to Record
The following GPEH events are required:
Event Protocol Description
8 RRC RRC_MEASUREMENT_REPORT 19 RRC RRC_RRC_CONNECTION_RELEASE 34 RRC RRC_RRC_CONNECTION_REQUEST 128 NBAP NBAP_RADIO_LINK_SETUP_REQUEST 258 RANAP RANAP_IU_RELEASE_REQUEST 259 RANAP RANAP_IU_RELEASE_COMMAND 265 RANAP RANAP_DIRECT_TRANSFER 268 RANAP RANAP_COMMON_ID 384 Internal INTERNAL_IMSI 385 Internal INTERNAL_RADIO_QUALITY_MEASUREMENTS_UEH 386 Internal INTERNAL_RADIO_QUALITY_MEASUREMENTS_RNH 398 Internal INTERNAL_IRAT_HO_CC_EVALUATION 399 Internal INTERNAL_IRAT_HO_CC_EXECUTION 415 Internal INTERNAL_RAB_ESTABLISHMENT 438 Internal INTERNAL_SYSTEM_RELEASE 441 Internal INTERNAL_PACKET_DEDICATED_THROUGHPUT 451 Internal INTERNAL_SYSTEM_UTILIZATION 456 Internal INTERNAL_CALL_SETUP_FAIL
18
4.2 Stats File (XML)
This 15-minute interval file contains the RNC counters for all the network elements. Usually the counters are already correctly defined and enabled in the OSSRC.
If for any reason the RBS counters are not configured for collection, please refer to the list in section 4.2.2 for the list of counters. It is important to add them for proper HSPA analysis.
4.2.1
Configuring Counters in OSSRC
Adding Counters profile:
1. Launch>>Applications>>Ericsson>>Performance>>Initiate data Collection>>WCDMA/LTE RAN Measurements
2. Administration -> Add profile.
3. User defined statistical subscription profile (first radio button). Next. 4. Profile name (required) & Description (optional). Next.
5. Standard statistics. Next.
6. Choose entity type - RNC / RBS / RXI (usually RNC). Next.
7. Choose RNC from left to right (more than one can be chosen). Next.
8. Choose which counters to record. There is a limit for the amount of counters to be recorded per RNC, depending on the OSS version. The counters are sorted in alphabetical order. The groups marked in blue are system defined and are a part of the system’s profiles, where the markings ‘Pr’ means primary, ‘S’ secondary. The profiles are an integral part of the OSSRC program, and are usually active; hence there is no need to recollect them. Next.
4.2.2
RBS Counters Required for Proper HSPA Analysis
pmCapAlloclubHsLimitingRatio pmHsDataFramesLost pmHsDataFramesReceived pmAckReceived pmNackReceived pmAverageUserRate [0..17] pmNoInactiveRequiredSubFrames pmNoActiveSubFrames pmNoOfHsUsersPerTti [0..4] pmReportedCqi [0..31] pmSumNumHspdschCodesAdded pmSampleNumHspdschCodesAdded pmSumOfHsScchUsedPwr [0..102] pmSumAckedBits
pmSumTransmittedBits PmTransmittedCarrierPower [0..51] PmTransmittedCarrierPowerNonHs [0..51] PmAverageRssi [0..64] pmTransmittedCarrierPowerHs PmRemainingResourceCheck [0..2]
4.2.3
Retrieval Procedure
The Counter files are generated through the Ericsson OSS.
In OSS 5 the Counter files are located in:
var/opt/ericsson/nms_umts_pms_seg/segment1
In OSS 5.x/6.x/12 the Counter files are located in:
/var/opt/ericsson/nms_umts_pms_seg/segment1/XML/SubNetwork=<RNC Name>/MeContext=<RNC NAME>
Where <RNC NAME> is the name of the RNC to complete, separated into RBS and RNC XML files.
4.3 Templates
The template files are located in:
var/opt/ericsson/nms_umts_pms_reg/templates
The Template files include the GPEH events to record, counters to record, and network areas for both.
If the template files are used, they must be activated in the “Data collection subscription profiles” in the OSS.
4.4 RES Activation and Properties (WMRR)
Note: This is an optional data input, which is rearly used with current customers.
Mentor can utilize the additional information provided as periodic messages in the GPEH logs.
Activating the periodic messages will increase the GPEH data file size.
If the messages are activated, TEOCO recommends defining EcIo, RSCP, and UeTxPower as parameters to be reported in the periodic measurements.
20
4.4.1
Setting up a WMRR Recording
1. Open the configuration application and select New Recording->WMRR->WCDMA.
2. Define the recording time period and recurring schedule.
3. For the RNC measurements, under Service1, define the required RABs for recording. We recommend including both voice and data RABs.
4. Under Measurement Quantity define Ec/No, RSCP and UeTxPower (UeTxPower is optional and can be removed if there is no place)
5. Select Sample & Fraction Settings. Make sure that UE Fraction is set to Full and that the periodic samples for each service are maximum 16 seconds. (If required, you can choose a higher sampling rate, for example, 12 or 8.)
22
6. In the Cell Set dialogue box, select the relevant RNCs for recording.
4.4.2
RES Results
Activating RES in the network will result in additional periodic-measurement reports in the GPEH files.
For example, the following sample of a GPEH file includes RES data. As can be seen by the time stamp, each report is provided in 16-second time intervals.
In the following case, it can also be seen that two sectors were serving the terminal.
4.5 Folder Structure for GPEH and Counter Files
For OSS data – GPEH and counter files – to be processed most efficiently by Mentor, the folder structure should be maintained as follows:
• Under the parent folder, create two folders. One should be named “logs”, for the GPEH files, and the other “KPIs” for the counter files (including the RBS counters). It is VITAL that these folder names are used, as Mentor looks for these names when processing the files. • Under each of the two folders, create a folder for each day of recordings, named according
to the date, in YYYYMMDD format. Diverting from this format will increase Mentor’s file processing time.
• Under each date folder, place the appropriate recording files for that day. The files can be placed directly under the date folder, but we recommend opening a subfolder for each RNC/RBS, as shown in the following example.
24
4.6 RPMO Recordings
4.6.1
Logs Collection and Setup
1. Start Event Based Applications (EBA) for GSM from the OSS–RC Workspace Menu: Applications Ericsson Performance Event Based Applications for GSM
2. Define recording cell sets using the Set Handler which is available from the RPMO main window.
3. Define RPMO events to be recorded.
The following events are mandatory for proper Mentor operation.
Index Event Number Event Name
1 1 Assignment Failed 2 2 ClearRequest 3 3 Clear Command 4 5 HandoverCommand 5 6 HandoverComplete 6 7 ChannelBusy
7 14 Cipher Mode Complete
8 20 MS Context Established
9 23 TBF Changes
10 34 Cs Call Release
11 36 Measurement Result Large
12 38 TBFEnds
13 41 VGCS Notification Response
Raw Event Data Export (REDE) makes it possible to store any events and
monitors that can be provided by the R-PMO server software in a file. The format of the file can be tab delimited or BIN. (In Mentor 9.1 the only supported format is tab delimited). Tab delimited format is limited by OSS-SC to a maximum 100 sectors even though more than one recording could be scheduled simultaneously.
26
4.6.2
Log Storage
The files are stored in the following OSS directories:
• var/opt/ericsson/eba_rede/data/USER NAME/RawEventExport/
• var/opt/ericsson/eba_rede/data/USER NAME/scheduledRawEventExport/ (if scheduling is used)
