Beruflich Dokumente
Kultur Dokumente
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
Table of Contents
Table of Contents
1
Introduction .............................................................................................. 1
1.1
4.2
4.3
Templates ..................................................................................................... 19
4.4
4.5
4.6
RPMO Recordings........................................................................................... 24
4.6.1 Logs Collection and Setup ..................................................................... 24
4.6.2 Log Storage ........................................................................................ 26
iii
Introduction
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:
Antenna and sectors physical location, profiles, and parameters in delimited format
(internally known as Schema format)
GSM Network Topology (Optional, for running an IRAT optimization and displaying the
GSM layer)
GPEH logs
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.
HO Handoff
NL Neighbor List
Data source
Ericsson XML
configuration dump
Ericsson
5.x/6.x/12
Antenna File
See
3.1.3.1
section
Projection used.
Terrain file
See
3.1.3.2
section
Antenna Profiles
Planet
others
See
3.1.3.3
section
GPEH
LOG
(sample 1 hour)
files
Reference
OSSRC
formats
and
Check
Ericsson
P5/P6/P7/W10/W12
Ericsson
P5/P6/P7/W10/W12
Important:
GPEHfileSize: 60000 per RNC
UEfraction: 1000
Description
Data source
Reference
GSM configuration
Customer DB
Check
Description
Data source
Reference
RES periodic
reporting (WMRR)
Ericsson
P5/P6/P7/W10/W12
Check
Note: TEOCO recommends using RES recordings for a limited time only, and mainly for creating
the UeTxPower maps.
A predefined set of Network Topology files exported from the Ericsson OSS in XML
format.
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
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
the UNIX machine. The procedure described in 3.1.1.2 uses the OSSRC to generate the
configuration files.
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.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 TEOCOs scripts to divide the file into the different RNCs, or manually cut-out
RNCs between the two XML directives:
<xn:SubNetwork id="RNC01">
And
</xn:SubNetwork>
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 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
3.1.3
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.
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.
Value
Range
Description
RNC Name
String
RNC ID
String
RNC Vendor
String
NodeB Name
String
NodeB ID
String
NodeB Longitude
NodeB Latitude
Sector Name
Double
Default
Double
String
Parent of cell
Antenna ID
String
Antenna Model
String
50ch max
Sector Keywords
String
Antenna Longitude
Double
Antenna Latitude
Double
Antenna Height
Antenna Electrical
DownTilt
Antenna Mechanical
DownTilt
Antenna Azimuth
Integer
0200
Integer
-20 +20
Electrical tilt
Integer
-20 +20
Mechanical tilt
Integer
0359
UL Cable Loss
Double
020
Azimuth
With step 0.1
DL Cable Loss
Double
020
Active
String
50ch max
In building
String
50ch max
Note: If UTM coordinates are used, the relevant column headers should be different:
NodeB X, NodeB Y, Antenna X, and Antenna Y.
10
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.
1.
11
2.
3.
4.
12
5.
6.
Choose RNC from left to right (only one can be chosen). Next.
7.
13
8.
14
Choose which events to record from left to right. NOTE: Detailed event list is listed in section
4.1.3
9.
Choose UE fraction (1000 is recommended but a lower value can be used as well). Next.
15
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.
16
4.1.2
Retrieval Procedure
4.1.3
Events to Record
Protocol
RRC
RRC
RRC
NBAP
RANAP
RANAP
RANAP
RANAP
Internal
Internal
Internal
Internal
Internal
Internal
Internal
Internal
Internal
Internal
Description
RRC_MEASUREMENT_REPORT
RRC_RRC_CONNECTION_RELEASE
RRC_RRC_CONNECTION_REQUEST
NBAP_RADIO_LINK_SETUP_REQUEST
RANAP_IU_RELEASE_REQUEST
RANAP_IU_RELEASE_COMMAND
RANAP_DIRECT_TRANSFER
RANAP_COMMON_ID
INTERNAL_IMSI
INTERNAL_RADIO_QUALITY_MEASUREMENTS_UEH
INTERNAL_RADIO_QUALITY_MEASUREMENTS_RNH
INTERNAL_IRAT_HO_CC_EVALUATION
INTERNAL_IRAT_HO_CC_EXECUTION
INTERNAL_RAB_ESTABLISHMENT
INTERNAL_SYSTEM_RELEASE
INTERNAL_PACKET_DEDICATED_THROUGHPUT
INTERNAL_SYSTEM_UTILIZATION
INTERNAL_CALL_SETUP_FAIL
Table 2: Events to Record as part of the GPEH Profile
17
4.2.1
2.
3.
4.
5.
6.
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 systems 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
pmCapAlloclubHsLimitingRatio
pmHsDataFramesLost
pmHsDataFramesReceived
pmAckReceived
pmNackReceived
pmAverageUserRate [0..17]
pmNoInactiveRequiredSubFrames
pmNoActiveSubFrames
pmNoOfHsUsersPerTti [0..4]
pmReportedCqi [0..31]
pmSumNumHspdschCodesAdded
pmSampleNumHspdschCodesAdded
pmSumOfHsScchUsedPwr [0..102]
pmSumAckedBits
18
pmSumTransmittedBits
PmTransmittedCarrierPower [0..51]
PmTransmittedCarrierPowerNonHs [0..51]
PmAverageRssi [0..64]
pmTransmittedCarrierPowerHs
PmRemainingResourceCheck [0..2]
4.2.3
Retrieval Procedure
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.
19
4.4.1
20
1.
2.
3.
For the RNC measurements, under Service1, define the required RABs for recording.
We recommend including both voice and data RABs.
4.
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.)
21
22
6.
In the Cell Set dialogue box, select the relevant RNCs for recording.
7.
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.
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 Mentors 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.
23
2.
24
Define recording cell sets using the Set Handler which is available from the RPMO main
window.
3.
Event Number
1
2
3
5
6
7
14
20
23
34
36
38
41
Event Name
Assignment Failed
ClearRequest
Clear Command
HandoverCommand
HandoverComplete
ChannelBusy
Cipher Mode Complete
MS Context Established
TBF Changes
Cs Call Release
Measurement Result Large
TBFEnds
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.
25
4.6.2
Log Storage
26
var/opt/ericsson/eba_rede/data/USER NAME/RawEventExport/