Call Trace & Network

Parameter Collection
Procedures

July 2015
 Call Trace & Network Parameter Collection Procedures

Collection Procedures

Contents

1 Physical Site Information (XIF)............................................................................................................................4

2 Network Configuration Dump ............................................................................................................................5
2.1 Huawei BSC .................................................................................................................................................5
2.2 Huawei RNC ................................................................................................................................................6
2.3 Huawei NodeB ............................................................................................................................................8
2.4 Huawei eNodeB ....................................................................................................................................... 11
2.4.1 Backing Up M2000 Periodically ....................................................................................................... 11
2.4.2 eNodeB Network Dumps Location .................................................................................................. 13
2.5 Ericsson BSC ............................................................................................................................................. 15
2.6 Ericsson RNC ............................................................................................................................................ 17
2.7 Ericsson NodeB ........................................................................................................................................ 18
2.7.1 Collecting Bulk CM ........................................................................................................................... 19
2.8 Ericsson eNodeB ...................................................................................................................................... 22
2.9 Motorola BSC ........................................................................................................................................... 23
2.10 Nokia BSC................................................................................................................................................. 24
2.11 Nokia RNC ................................................................................................................................................ 25
2.12 ZTE RNC ................................................................................................................................................... 26
3 Traffic Measurement Recording ...................................................................................................................... 27
3.1 Huawei WCDMA (PCHR) .......................................................................................................................... 27
3.1.1 Huawei PCHR File Path .................................................................................................................... 27
3.1.2 Huawei PCHR Field .......................................................................................................................... 27
3.2 Huawei LTE (SIG Log) ............................................................................................................................... 28
3.3 Huawei LTE (TMF) .................................................................................................................................... 29
3.4 Ericsson WCDMA (GPEH) ......................................................................................................................... 32
3.4.1 Ericsson GPEH Recording Scenarios ................................................................................................ 46
3.5 Ericsson LTE (Cell Trace) .......................................................................................................................... 51
3.5.1 Ericsson LTE MME EBM Trace ......................................................................................................... 56
3.6 Nokia WCDMA (Megamon) ..................................................................................................................... 57

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 2

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

3.7 ZTE WCDMA (CTS) ................................................................................................................................... 59

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 3

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

1 Physical Site Information (XIF)

The Physical information of each cell that contain CellID, Latitude,Longitude, Antenna Orientation etc, that were
not available inside network dump. The supported format will be in Text Delimited or in our XIF format.

The following header fields are mandatory for parsing xif dump files.
• CellId
• Latitute
• Longitute
• AntDir

Parsing will fail, if one of these mandatory header fields is not found in the dump file.

Sample information as below :

This file need to be parsed daily to ensure the information drawn on the map and data that will be snyc to Xeus
are accurate.
Sample :

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 4

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

2 Network Configuration Dump

2.1 Huawei BSC

Supported file format is an XML file exported from CM Export feature of iManager M2000.

Follow these steps to collect the dump:

1. Start iManager M2000

2. Click Maintenance…Task Management at the menu
3. Create a new task Configuration Data Export. Select the BSC in the Extended Properties. Choose XML
format and set the destination path.
4. Once the task completed, FTP the file from the destination path.

Supported MO class are as below:

BSC6000NE
BSC6000CellChannel
BSC60002GExtCell
BSC60003GExtCell
BSC6000Cell
BSC6000CellBaseAttr
BSC6000CellCallCtrl
BSC6000CellChMng
BSC6000CellHOCtrl
BSC6000CellPwrCtrl
BSC6000CellSoftPara
BSC6000CellSysMsg
BSC6000CellTimer
BSC60002GAdjRel
BSC60003GAdjRel
BSC6000CellHopData
BSC6000Site
BSC6000TRX

Following is the sample snapshot of the CM Export file:

<?xml version="1.0" encoding="iso-8859-1"?>

<MOTree>
<MO className="BSC6000NE" fdn=".3221229568.3221233664.3221282818">
<attr name="fdn">.3221229568.3221233664.3221282818</attr>
<attr name="IP">10.4.137.21</attr>
<attr name="MOIndex">2</attr>
<attr name="className">BSC6000NE</attr>
<attr name="latitude">255.0</attr>

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 5

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

<attr name="locationName">Arena</attr>
<attr name="longitude">194.0</attr>
<attr name="matchVersion">iManagerM2000_BSC6000_MATCH_ENG_V200R006C01B624</attr>
<attr name="name">BSCNTB31</attr>
<attr name="neID">2</attr>
<attr name="neType">BSC6000</attr>
<attr name="neVersion">BSC6000V900R008C12</attr>
<attr name="realLatitude">0DN</attr>
<attr name="realLongitude">0DE</attr>
<attr name="vendorName">Huawei</attr>
<MO className="BSC6000BCGrp" fdn=".3221229568.3221233664.3221282818.3221417986">
<attr name="fdn">.3221229568.3221233664.3221282818.3221417986</attr>
<attr name="BSCIndex">0</attr>
<attr name="GrpIndex">0</attr>
<attr name="MOIndex">2_0_0</attr>
<attr name="className">BSC6000BCGrp</attr>
<attr name="name">CBCGrp</attr>
<attr name="neID">2</attr>
</MO>……

2.2 Huawei RNC

Supported file format is the export file from Huawei OSS EXP CFGMML command.

By default, this file is saved in the ftp/export_cfgmml directory of the main area of the OMU and named
CFGMML-RNCX-IP-YYYYMMDDHHMMSS.zip("X" indicates RNC ID).

The folder in located within the RNC. To avoid Xeda having to access the folder, it is best that these Data in the
folder be copied out into a server.

Following is sample snapshot of the file :

//****************MML script file****************

//Export start time: 2009-02-23 13:16:19
//Export end time: 2009-02-23 13:18:15
//Export Workstation IP address: 10.232.2.100
//System RNCID: 1
//For BAM version: BSC6800V100R008C01B060
//***********************************************
SET SYS:SYSDESC="HUAWEI WCDMA RNC", SYSOBJECTID="RNC 1", SYSCONTACT="0012 123 28560000",
SYSLOCATION="ABCDE", SYSSERVICES="WCDMA RNC";
ADD RNCBASIC:RNCID=123, MCC="123", MNC="11";
SET WMPUIP:WMPUIPADDR="10.121.139.100", MASK="255.255.255.0", BAMIPADDR="10.121.139.200";
SET SUBNET:SUBNET=80;
ADD OPC:NI=NAT, SPCBITS=BIT14, SPC=H'000C44, NSAP=H'45000060192040139F0000000000000000000000,
NAME="SYRNC";
……

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 6

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

Following are the supported commands :

ADD GSMCELL
ADD GSMNCELL
ADD NRNC
ADD NRNCCELL
ADD CCP
ADD NCP
ADD NODEB
ADD NODEBALGOPARA
ADD NODEBIP
ADD NODEBLDR
ADD CNOPERATOR
ADD RNCBASIC
SET ADMCTRL
SET AMRC
SET CERRMTIMER
SET CMCF
SET CONNMODETIMER
SET DCCC
SET DPB
SET DRD
SET FACHSCHEPRIO
SET FRMHANDPRIO
SET HCSHO
SET HOCOMM
SET HSDPCC
SET HSDSCHSCHEPRIO
SET HSSCCH
SET IDLEMODETIMER
SET INTERFREQHOCOV
SET INTERFREQHONCOV
SET INTERRATHOCOV
SET INTERRATHONCOV
SET INTRAFREQHO
SET LDCALGOPARA
SET LDM
SET LOCHPRIO
SET OLPC
SET SATLDCPERIOD
SET SRNSR
SET STATETIMER
SET SYS
SET UESTATETRANS
SET WFMRCFGDATA
ACT CELL
ACT CELLHSDPA
ADD CELLACCESSSTRICT
ADD CELLALGOSWITCH
ADD CELLCAC
ADD CELLFRC
ADD CELLHCS
ADD CELLHOCOMM
ADD CELLHSDPA
ADD CELLINTERRATHOCOV
ADD CELLLDB
ADD CELLLDM
ADD CELLLDR

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 7

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

ADD CELLMEAS
ADD CELLOLC
ADD CELLPUC
ADD CELLRLACTTIME
ADD CELLSELRESEL
ADD CELLSETUP
ADD CELLSIBSWITCH
ADD CHPWROFFSET
ADD PSINACTTIMER
ADD SMLCCELL
SET PSINACTTIMER
ADD INTERFREQNCELL
ADD INTRAFREQNCELL

Below are the instruction to generate this file in case it is not available in the server :

1. Running the following command to export the MML script file from the configuration data of the OMU
by the default setting.
The script file is exported to "the main area directory of the OMU/ftp/export_cfgmml/CFGMML-RNCX-
IP-YYYYMMDDHHMMSS.zip("X" indicates RNC ID)".
EXP CFGMML:;

2. Running the following command to export the MML script of configuration data on the OMU by the
default export file path.
The script file is exported to /ftp/export_cfgmml on the active workspace of the active OMU and named
"the main area directory of the OMU/ftp/export_cfgmml/cfgmml.zip".
EXP CFGMML: FN="cfgmml.txt";

3. If the OMU runs the WINDOWS system, to export the MML script of configuration data on the OMU
(Export file path = D:\mbsc\bam\version_a\ftp; Export file name = cfgmml.zip), run the following
command(Please affirm that "D:\mbsc\bam\version_a\ftp" is a valid path on the OMU server):
EXP CFGMML: FILEPATH="D:\mbsc\bam\version_a\ftp", FN="cfgmml.txt";

4. If the OMU runs the LINUX system, to export the MML script file from the configuration data of the
OMU (Export file path = /mbsc/bam/version_a/ftp; Export file name = cfgmml.zip), run the following
command (Please affirm that "/mbsc/bam/version_a/ftp" is a valid path on the OMU server):
EXP CFGMML: FILEPATH="/mbsc/bam/version_a/ftp", FN="cfgmml.txt";

2.3 Huawei NodeB

Supported file format is an XML configuration file located in the NodeB itself. There is one file per NodeB.

<?xml version="1.0" encoding="GB2312" standalone="yes"?>

<NODEB xmlns = "x-schema:NodeBCfgBiz.xml" ID = "0x0">

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 8

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

<NODEBSOM ID = "0x14000000">
<NODEBTYPE ID = "0x24000001">15</NODEBTYPE>
<NULPFPGA ID = "0x24000002">
<NULPRXDELAYTIME ID = "0x34000003">
<NULPRDT ID = "0x44000004" STATIC = "0" DESC = "Rx time
delay">184</NULPRDT>
</NULPRXDELAYTIME>
</NULPFPGA>
<NULPCDMDDMDSP ID = "0x24000005">
<DEMDSPMODE ID = "0x34000006">
<NBWM ID = "0x44000007" STATIC = "1" DESC = "NodeB work mode(0-
TWOANTENNA 1-FOURANTENNA 3-ECONOMIZED)">0</NBWM>
</DEMDSPMODE>
</NULPCDMDDMDSP>
<NDLPFPGA ID = "0x24000008">
<NDLPUPGBUSMODE ID = "0x34000009">
<UGWM ID = "0x4400000a" STATIC = "0" DESC = "Rx G_Bus work mode(0-
BACKUP 1-STANDALONE)">0</UGWM>
</NDLPUPGBUSMODE>
</NDLPFPGA>
<NDLPENCODEDSP ID = "0x2400000b">
<TXDELAYTIME ID = "0x3400000c">
<TDT ID = "0x4400000d" STATIC = "0" DESC = "Tx time
delay">248</TDT>
</TXDELAYTIME>
</NDLPENCODEDSP>
<BBUCM ID = "0x2400000e" STATIC = "0" DESC = "BBU cascade mode">0</BBUCM>….

The network dump files is inside M2000 server in the following path:
M2000 server : /export/home/sysm/ftproot/NE type (for example: DBS3900)/Data
Example : /export/home/sysm/ftproot/DBS3900/Data

The data generated for automatic backup is located in the AUTOBAKDATA****** directory.

Sample output location will be like this:

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 9

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

Each eNodeB will be having the same file named : NodeBCfg.xml as per screenshot below :

Supported file format is an XML configuration file located in the NodeB itself. There is one file per NodeB.

<?xml version="1.0" encoding="GB2312" standalone="yes"?>

<NODEB xmlns = "x-schema:NodeBCfgBiz.xml" ID = "0x0">
<NODEBSOM ID = "0x14000000">
<NODEBTYPE ID = "0x24000001">15</NODEBTYPE>
<NULPFPGA ID = "0x24000002">
<NULPRXDELAYTIME ID = "0x34000003">
<NULPRDT ID = "0x44000004" STATIC = "0" DESC = "Rx time
delay">184</NULPRDT>
</NULPRXDELAYTIME>
</NULPFPGA>
<NULPCDMDDMDSP ID = "0x24000005">
<DEMDSPMODE ID = "0x34000006">
<NBWM ID = "0x44000007" STATIC = "1" DESC = "NodeB work mode(0-
TWOANTENNA 1-FOURANTENNA 3-ECONOMIZED)">0</NBWM>
</DEMDSPMODE>
</NULPCDMDDMDSP>
<NDLPFPGA ID = "0x24000008">
<NDLPUPGBUSMODE ID = "0x34000009">

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 10

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

<UGWM ID = "0x4400000a" STATIC = "0" DESC = "Rx G_Bus work mode(0-

BACKUP 1-STANDALONE)">0</UGWM>
</NDLPUPGBUSMODE>
</NDLPFPGA>
<NDLPENCODEDSP ID = "0x2400000b">
<TXDELAYTIME ID = "0x3400000c">
<TDT ID = "0x4400000d" STATIC = "0" DESC = "Tx time
delay">248</TDT>
</TXDELAYTIME>
</NDLPENCODEDSP>
<BBUCM ID = "0x2400000e" STATIC = "0" DESC = "BBU cascade mode">0</BBUCM>….

2.4 Huawei eNodeB

In order to produce the network dump, data need to be backup automatically (periodically).

2.4.1 Backing Up M2000 Periodically

This describes how to periodically back up the M2000 dynamic data.

2.4.1.1 Prerequisites

 You have logged in to the M2000 client.

 You have the relevant operation privileges.
 The tape drive is connected properly. It holds a tape if you plan to back up data on the tape.
 A hard disk has sufficient free space if you plan to back up data on the hard disk.

2.4.1.2 Context

Generally, M2000 dynamic data is backed up periodically. The periodic backup of the dynamic data is performed
in full backup mode.

Dynamic data backup has no restriction on backup time. The backup can be performed during the system
operation.

Note : Backing up dynamic data consumes system resources. Thus, the time set for backup should be at night
when the system traffic is light.

2.4.1.3 Procedure

1. On the main window, choose Maintenance > Task Management.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 11

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

The Task Management dialog box is displayed.

2. Choose Task Type > Backup > Server Backup in the navigation tree and double-click the node. The
Attribute dialog box of server periodic backup is displayed as below.

 Click Common Parameters, and set Task Name and Start Time.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 12

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

 Click Extended Parameters, and set Server Full Backup Date.

2.4.2 eNodeB Network Dumps Location

The network dump files is inside M2000 server in the following path:
M2000 server : /export/home/sysm/ftproot/NE type (for example: DBS3900 LTE)/Data
Example : /export/home/sysm/ftproot/DBS3900 LTE/Data

The data generated for automatic backup is located in the AUTOBAKDATA****** directory.

Sample output location will be like this:

Sample Output Location :

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 13

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

Each eNodeB will be having the same file named : M2000.xml as per screenshot below :

Following is a sample snapshot of the file :

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 14

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

<?xml version="1.0" encoding="GB2312"?>

<spec:BACKUPCFG
xmlns:spec="http://www.huawei.com/specs/huawei_wl_bulkcm_xml_baseline_syn_1.0.0"
xmlns="http://www.huawei.com/specs/bsc6000_nrm_forSyn_collapse_1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.huawei.com/specs/huawei_wl_bulkcm_xml_baseline_syn_1.0.0
CfgSynData_collapse_spec.xsd">
<spec:fileHeader fileFormatVersion="1.1.0" NRMversion="LTEDATAV100R005C00SPC373"
NEversion="DBS3900 LTE V100R005C00SPC373" synType="synall"/>
<spec:synData>
<class synlabel="00000000011209476647">
<TBLANGNO id="0">
<attributes>
<LangNo>0</LangNo>
</attributes>
</TBLANGNO>

2.5 Ericsson BSC

Supported file format is the command printout from Command Handling in Ericsson OSS. Here is a list of
supported command printout:

Note: Some commands may be applicable for certain version of the BSC only.

RLADP:SET=ALL;
DBTSP:TAB=AXEPARS;
RLGRP:CELL=ALL;
IOEXP;
RAEPP:ID=ALL;
RLCAP;
RLCDP:CELL=ALL;
RLDCP;
RLLSP;
RLOMP;
RLTYP;
RLHBP;
RLBDP:CELL=ALL;
RLCFP:CELL=ALL;
RLCHP:CELL=ALL;
RLDTP:CELL=ALL;
RLGAP:CELL=ALL;
RLSTP:CELL=ALL;
DTSTP:DIP=ALL;
RLACP:CELL=ALL;
RLCRP:CELL=ALL;
RLCXP:CELL=ALL;
RLDEP:CELL=ALL;
RLDHP:CELL=ALL;
RLDMP:CELL=ALL;

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 15

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

RLDRP:CELL=ALL;
RLGSP:CELL=ALL;
RLHPP:CELL=ALL;
RLIMP:CELL=ALL;
RLLCP:CELL=ALL;
RLLDP:CELL=ALL;
RLLFP:CELL=ALL;
RLLHP:CELL=ALL;
RLLLP:CELL=ALL;
RLLPP:CELL=ALL;
RLMFP:CELL=ALL;
RLPBP:CELL=ALL;
RLPDP:CELL=ALL;
RLSBP:CELL=ALL;
RLSMP:CELL=ALL;
RLSSP:CELL=ALL;
RLSUP:CELL=ALL;
RLUMP:CELL=ALL;
RRGBP;
RLBCP:CELL=ALL;
RLCPP:CELL=ALL;
RLLOP:CELL=ALL;
RLPCP:CELL=ALL;
RLCPP:CELL=ALL,EXT;
RLDEP:CELL=ALL,EXT;
RLLHP:CELL=ALL,EXT;
RLLOP:CELL=ALL,EXT;
RLDEP:CELL=ALL,EXT,UTRAN;
RLNRP:CELL=ALL,UTRAN;
RLGNP:CELL=ALL;
RLNRP:CELL=ALL;
RLLBP;
SAOSP;
SAAEP:SAE=ALL;
SAAEP:SAE=1153;
SAAEP:SAE=298;
SAAEP:SAE=299;
SAAEP:BLOCK=RQCD,SAE=522;
SAAEP:BLOCK=RQCD,SAE=523;
RLAPP:CELL=ALL;
RLIHP:CELL=ALL;
RLLUP:CELL=ALL;
RLOLP:CELL=ALL;
RLSLP:CELL=ALL;
RLTDP:MSC=ALL
RRTPP:TRAPOOL=ALL;
RLLPP:CELL=ALL;
RXMOP:MOTY=RXOTG;
RXTCP:MOTY=RXOTG;
RXMOP:MOTY=RXOTRX;
CACLP;

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 16

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

2.6 Ericsson RNC

KGET dump collection

Supported file format is MO Shell from the Ericsson OSS. Following are the supported command printout:

Note: For new release of Ericsson RNC the supported file format is extracted from MO Shell (kget). The command
is ‘lt all; kget all’

RncFunction
UeRc
UeRcTrCh
UeRcRab
UeRcEdchFlow
UeRcPhyChEdch
WcdmaCarrier
UtranCell
Pch
UtranRelation
GsmRelation
Fach
Hsdsch
Eul
Rach
IubLink
NbapCommon
NodeSynch
NbapDedicated
IubEdch
Handover
DchFrameSynch
Ura
RncModule
Rcs
SecurityHandling
IurLink
WcdmaCarrier
ExternalUtranCell
CchFrameSynch
UeRrcType
UePositioning
PositioningServiceClass
AgpsPositioning
RttPositioning
ExternalGsmNetwork
ExternalGsmCell
LocationArea
ServiceArea
RoutingArea

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 17

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

Panging
UtranNetwork
PowerControl
PlmnIdentityGroup
Sid
SasPositioning
ChannelSwitching
UeMeasControl

2.7 Ericsson NodeB

Supported file format is the BulkCM Export from the Ericsson OSS. By default Ericsson OSS will automatically
export the Bulk CM for whole network daily. In order to reduce the output file, user can exclude the Transport
Network information which is not required.

Snapshot of Ericsson BulkCM Export file

Following are the elements supported by Xeda :

NodeBFunction
vsDataNodeBFunction\
vsDataSector
vsDataCarrier
vsDataRbsLocalCell
vsDataSectorAntenna
vsDataAntennaBranch
vsDataAntFeederCable

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 18

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

vsDataAuxPlugInUnit
RNCFunction
attributes
VsDataContainer
UtranCell
IubLink

2.7.1 Collecting Bulk CM

1. Start OSS Common Explorer.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 19

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

2. OSS Common Explorer will appear on the screen as shown in the figure below. At Topology Tab, select the
Root node from the network tree. Then, right click and select ‘Export.’ option from the context menu.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 20

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

3. After clicking on ‘Export.’ option, Bulk CM Export dialog box will appear as shown in the figure below.
Tick to select Radio Network only as a filter details option and click Export button.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 21

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

4. Click on Bulk CM Progress tab to view on the export progress.

5. FTP to the OSS and set the export to /var/opt/ericsson/nms_umts_wran_bcg/files/export.

2.8 Ericsson eNodeB

For the BulkCm Network Dump:

1. In the Common Explorer, select the Top Network Element, then right-click and select ExportNE
The Bulk CM Export dialog will appear.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 22

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

2. Set the output location

3. At the Filter select Radio and Transport Network
4. Click Export

2.9 Motorola BSC

Supported file format is the exported Comma Delimited file at the OMC. There are separate files for Cell and
Neighbor parameter. For the neighbor parameters file the GSM Neighbors Export and Utran Relation Export are
in one single file.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 23

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

2.10 Nokia BSC

Supported file format is the RAML Export in XML format.

Following is the snapshot of the file:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE raml SYSTEM 'raml20.dtd'>
<raml version="2.0" xmlns="raml20.xsd">
<cmData type="actual">
<header>
<log dateTime="2009-06-01T15:31:08" action="created" appInfo="ActualExporter"/>
</header>
<managedObject class="BSC" version="S13" distName="PLMN-PLMN/BSC-1234" id="1567005">
<p name="dcsMacrocellThreshold">2</p>
<p name="dcsMicrocellThreshold">3</p>
<p name="name">SYBSC1</p>
<p name="neSwRelease">S11.5</p>
<p name="adjCellFreqsInMeasBAInfo">10</p>
<p name="alrmChFail">40</p>
<p name="alrmNoOfSei">4</p>
<p name="alrmSchFail">80</p>
<p name="alrmSdcch">20</p>
<p name="alrmSeizReq">100</p>
<p name="alrmTch">20</p>
<p name="amhLowerLoadThreshold">20</p>
<p name="amhMaxLoadOfTgtCell">70</p>
<p name="amhTrhoGuardTime">30</p>
<p name="amhUpperLoadThreshold">80</p>
<p name="amrConfInHandovers">1</p>…..

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 24

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

2.11 Nokia RNC

Supported file format is the RAML Export in XML format.

Following is the snapshot of the file:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE raml SYSTEM 'raml20.dtd'>
<raml version="2.0" xmlns="raml20.xsd">
<cmData type="actual">
<header>
<log dateTime="2006-11-07T12:04:02" action="created" appInfo="ActualExporter"/>
</header>
<managedObject class="RNC" version="RN2.1" distName="PLMN-PLMN/RNC-102" id="87001">
<defaults name="System"/>
<p name="A2EA">4960192040131000000000000000000000000000</p>
<p name="ActivationTimeOffset">600</p>
<p name="BTSfrozenMaxTimer">30</p>
<p name="BitRateSetPSNRT">0</p>
<p name="CCCHforCUCallowed">1</p>
<p name="CMmasterSwitch">0</p>
<p name="CVUserInactInSignConnRel">1</p>
<p name="CellDCHtestTmr">0</p>
<p name="CellReselectionObservingTime">30</p>
<p name="CrHandlingPolicyDL">2</p>
<p name="CrHandlingPolicyUL">2</p>
<p name="CrQueuingTimeDL">4</p>
<p name="CrQueuingTimeUL">4</p>
<p name="DCHUtilRelThrDL">8</p>
<p name="DCHUtilRelThrUL">8</p>
<p name="DLBLERConfInterval">23</p>…

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 25

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

2.12 ZTE RNC

Supported file format is Excel datasheet from the RNC.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 26

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

3 Traffic Measurement Recording

3.1 Huawei WCDMA (PCHR)

1. RNC Network Dump

Use “EXP CFGMML” command to export the MML scripts of the configuration data into the BAM folder

2. CHR Log

The CHRs are generated automatically and stored under the BAM in the following path:
- RNC R10  /bam/versiona/loaddata/famlogfmt for R10
- RAN R11  /bam/common/fam/famlogfmt
- RAN R12 & R13  /bam/common/fam/famlogfmt/pchr

The PCHR log will have either UCHR or PCHR word in the filenames e.g.
- RNC R10  RNC0101_02Log20110404000002_20110404010109.log.zip
- RAN R11  BSC0121_[UCHR]02Log20111010231746(DST)_20111010232743(DST).log.zip
- RAN R12 & R13  BSC0121_[PCHR]02Log20111010231746(DST)_20111010232743(DST).log.zip

Important: For R11 and above, please ensure that the file name has ‘UCHR’ or ‘PCHR’. File with
‘CHR’ string alone does contain the performance call log and not supported in Xeus Pro.

3.1.1 Huawei PCHR File Path

The CHRs are generated automatically and stored under the BAM in the following path:
 RAN R12 & R13 /bam/common/fam/famlogfmt/pchr

The PCHR log will have either UCHR or PCHR word in the filenames e.g.
 RAN R12 & R13 BSC0121_[PCHR]02Log20111010231746(DST)_20111010232743(DST).log.zip

3.1.2 Huawei PCHR Field

If one of the fields is not enabled in the CHRs, use the following command to enable it:
1. In the LMT tool, execute the command SET CHRRNCCTRL (R10) or SET UCHRCTRL (R11) in the Command Input
field.
2. Click the “SELECT ALL” check box in the Type option drop down lists.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 27

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

3. Run the command through a batch file only:

Huawei R10
SET CHRRNCCTRL:STATETYPE=ABNORMAL_ONLY-1&NORMAL_ONLY-1, DOMAINTYPE=CS_ONLY-1&PS_ONLY-1, FLOWTYPE=CONN_SETUP-1&RAB-1&DCCC-
1&SHO-1&HHO-1&SYS_HO_OUT-1&RRC_RELEASE-1&STAT-1&NET_OPT-1, RRCCAUSE=ORIGINATING_CONVERSATIONAL_CALL-
1&ORIGINATING_STREAMING_CALL-1&ORIGINATING_INTERACTIVE_CALL-1&ORIGINATING_BACKGROUND_CALL-
1&ORIGINATING_SUBSCRIBED_TRAFFIC_CALL-1&TERMNT_CONVERSATIONAL_CALL-1&TERMNT_STREAMING_CALL-1&TERMNT_INTERACTIVE_CALL-
1&TERMNT_BACKGROUND_CALL-1&EMERGENCY_CALL-1&INTER_RAT_CELL_RESELECTION-1&INTER_RAT_CELL_CHG_ORDER-1&REGISTRATION-
1&DETACH-1&ORIGINATING_HIGH_PRIOR_SIG-1&ORIGINATING_LOW_PRIOR_SIG-1&CALL_RE_ESTAB-1&TERMNT_HIGH_PRIOR_SIG-
1&TERMNT_LOW_PRIOR_SIG-1&TERMNT_CAUSE_UNKNOWN-1&MBMS_RECEPTION-1&MBMS_PTP_RB_REQ-1;

Huawei R11 & above

SET UCHRCTRL:STATETYPE=ABNORMAL_ONLY-1&NORMAL_ONLY-1, DOMAINTYPE=CS_ONLY-1&PS_ONLY-1, FLOWTYPE=CONN_SETUP-1&RAB-1&DCCC-
1&SHO-1&HHO-1&SYS_HO_OUT-1&RRC_RELEASE-1&STAT-1&NET_OPT-1, RRCCAUSE=ORIGINATING_CONVERSATIONAL_CALL-
1&ORIGINATING_STREAMING_CALL-1&ORIGINATING_INTERACTIVE_CALL-1&ORIGINATING_BACKGROUND_CALL-
1&ORIGINATING_SUBSCRIBED_TRAFFIC_CALL-1&TERMNT_CONVERSATIONAL_CALL-1&TERMNT_STREAMING_CALL-1&TERMNT_INTERACTIVE_CALL-
1&TERMNT_BACKGROUND_CALL-1&EMERGENCY_CALL-1&INTER_RAT_CELL_RESELECTION-1&INTER_RAT_CELL_CHG_ORDER-1&REGISTRATION-
1&DETACH-1&ORIGINATING_HIGH_PRIOR_SIG-1&ORIGINATING_LOW_PRIOR_SIG-1&CALL_RE_ESTAB-1&TERMNT_HIGH_PRIOR_SIG-
1&TERMNT_LOW_PRIOR_SIG-1&TERMNT_CAUSE_UNKNOWN-1&MBMS_RECEPTION-1&MBMS_PTP_RB_REQ-1;

3.2 Huawei LTE (SIG Log)

Instructions to Collect Huawei LTE SIG Log :

1) First, create a “LTE Cell Trace” task in M2000 before capturing the call trace. The output file format is SIGLOG.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 28

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

2) After capturing the log, you can export the log from eNodeB by executing the MML commands as the
following:

3) The output file will have ".dat" or ".sig" extension.

3.3 Huawei LTE (TMF)

• Open Signaling Trace Management on M2000

• Click on Cell Trace
• Click on New

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 29

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

• Enter “Trace Name”

• Select desired cell in “Select Cells”

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 30

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

• Set the desired trace duration

• Trace Depth
o Set to High
• Message Type
o Select ALL messages

• Right click on the completed trace and select Export

• In the export file view, set the desired path

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 31

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

3.4 Ericsson WCDMA (GPEH)

Site Data
It is advisable for the users to import the site data by XIF/TEMS Cel-file/ MCOM file format first before the
importing of the Ericsson WCDMA OSS Bulk CM XML file or Ericsson RNC MOSHELL KGET log.

The table below shows some of the mandatory fields in creating a XIF format site data:

XIF Parameter Description

CellId The unique Cell Identity/Name of the cell e.g. G1001A.

Note: Xeus Pro does not accept two records with SAME Cell Id. Any duplicate
cell Id will be renamed with additional suffix e.g. G1001A_1.

Mandatory field

SiteId The Site Id of the cell e.g. D1001.

Note: Site Id will be displayed as label for cell in the map

Longitude Longitude of the cell in Float format e.g. -121.23328.

Mandatory field

Latitude Latitude of the cell in Float format e.g. 30.12312.

Mandatory field

AntDir Direction of the cell in Degree unit

Mandatory field

RncId RNC Identity

Note: RncId-Cid pair allows matching of WCDMA Cell network data to the site
data in Xeus Pro database

CId WCDMA Cell Identity

Note: RncId-Cid pair allows matching of WCDMA Cell network data to the site
data in Xeus Pro database

XIF parameter format

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 32

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

Sample of XIF format

RNC Network Dump

You can import the WCDMA site configuration and neighbor data by the following options:
1. Ericsson WCDMA OSS Bulk CM XML file
2. Ericson RNC MOSHELL KGET log file

GPEH Recording Collection

The following are the steps to obtain the GPEH recording set. Refer to Appendix 1(b): Ericsson GPEH
Recording Steps for a more detail information.

GPEH collection parameter settings:

1. Start OSS Common Explorer
2. Select the required RNC Node
3. Change the ‘gpehDataLevel’ to ‘ALL_DATA’
4. Increase the value for ‘gpehFileSize’ parameter to 50,000 (50,000kB)

Initiate GPEH Collection

1. Select Performance > Initiate data Collection > WCDMA/LTE RAN Measurements
2. Select Administration > Add profile
3. Select GPEH as the subscription profile type
4. Enter profile name

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 33

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

5. Select “RNC network elements should be observed”

6. Select the required RNC for recording
7. Select the required Utran Cells for recording
8. Select the required GPEH recording events. Please refer to Section 3.4.1 for GPEH Recording Scenarios
for the required events on different analysis scenarios. Following table show the recommended GPEH
events to be collected for a standard Xeus Pro 5 analysis.

GPEH • INTERNAL_ADMISSION_CONTROL_RESPONSE Identify Admission Control

Internal • INTERNAL_CALL_REESTABLISHMENT Identify Call Re-establishment after abnormal release
Event • INTERNAL_CALL_SETUP_FAIL Identify Call Setup Failure
• INTERNAL_CHANNEL_SWITCHING Identify Channel Switching
• INTERNAL_CMODE_ACTIVATE Identify Compressed Mode Activation
• INTERNAL_CMODE_DEACTIVATE Identify Compressed Mode Deactivation
• INTERNAL_CNHHO_EXECUTION_ACTIVE Identify Core Network Hard Handover
• INTERNAL_FAILED_HSDSCH_CELL_CHANGE Identify failed HS-DSCH cell change
• INTERNAL_FAILED_TRANSITION_TO_DCH Identify Failed transition to DCH in HS mode
• INTERNAL_HSDSCH_CELL_SELECTION_NO_CELL_SELECTED Identify HS cell selection involving no new cell
• INTERNAL_IFHO_EXECUTION_ACTIVE Identify inter-frequency handovers
• INTERNAL_IMSI Identify the UE IMSI
• INTERNAL_IRAT_HO_CC_EVALUATION Identify IRAT handover decision
• INTERNAL_IRAT_HO_CC_EXECUTION Identify IRAT handovers
• INTERNAL_MEASUREMENT_HANDLING_EXECUTION Identify Compressed Mode type
• INTERNAL_OUT_HARD_HANDOVER_FAILURE Identify failed hard handovers
• INTERNAL_OUT_HARD_HANDOVER_SUCCESS Identify successful hard handovers
• INTERNAL_PACKET_DEDICATED_ THROUGHPUT Capture RLC and application throughput for PS Interactive data
• INTERNAL_PACKET_DEDICATED_THROUGHPUT_STREAMING Capture RLC and application throughput for PS streaming data
• INTERNAL_PS_RELEASE_DUE_TO_CNHHO Identify Packet Switched RAB release due to a Core Network Hard Handover
• INTERNAL_RAB_ESTABLISHMENT Identify RAB establishments
• INTERNAL_RAB_RELEASE Identify RAB releases
• INTERNAL_RADIO_QUALITY_MEASUREMENTS_UEH Capture UL SIR Errors and DL TX Code Power information
• INTERNAL_SOFT_HANDOVER_EXECUTION Identify Soft Handovers
• INTERNAL_SOHO_DS_MISSING_NEIGHBOUR Identify missing neighbors
• INTERNAL_SOHO_DS_UNMONITORED_NEIGHBOUR Identify unmonitored neighbors
• INTERNAL_SUCCESSFUL_HSDSCH_CELL_CHANGE Identify HS-DSCH cell change
• INTERNAL_SUCCESSFUL_HSDSCH_CELL_SELECTION_NEW_ACTIVE_SET Identify HS-DSCH cell selection with new cell selected after hard handover
• INTERNAL_SUCCESSFUL_HSDSCH_CELL_SELECTION_OLD_ACTIVE_SET Identify HS-DSCH cell selection that selects a new cell in the old active set
• INTERNAL_SUCCESSFUL_TRANSITION_TO_DCH Identify successful transition to DCH in HS mode
• INTERNAL_SYSTEM_BLOCK Identify blocked call
• INTERNAL_SYSTEM_RELEASE Identify dropped call
• INTERNAL_SYSTEM_UTILIZATION Capture Resource Usage
• INTERNAL_UE_POSITIONING_QOS Capture UE Position from Location Services

RRC • RRC_CELL_CHANGE_ORDER_FROM_UTRAN Identify IRAT Cell Change Order

Event • RRC_CELL_CHANGE_ORDER_FROM_UTRAN_FAILURE Identify IRAT Cell Change failure
• RRC_CONNECTION_REJECT Identify RRC Connection Reject
• RRC_CONNECTION_RELEASE Identify RRC connection release
• RRC_CONNECTION_REQUEST Identify Call Attempt
• RRC_CONNECTION_SETUP_COMPLETE Identify UE category
• RRC_DOWNLINK_DIRECT_TRANSFER Capture NAS messages
• RRC_HANDOVER_FROM_UTRAN_COMMAND Identify Successful relocation preparation for IRAT handover
• RRC_HANDOVER_FROM_UTRAN_FAILURE Identify Failed relocation preparation for IRAT handover
• RRC_INITIAL_DIRECT_TRANSFER Capture NAS messages

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 34

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

• RRC_MEASUREMENT_CONTROL Capture GSM Neighbor Information

• RRC_MEASUREMENT_REPORT Capture neighbor Ec/No and RSCP
• RRC_SIGNALLING_CONNECTION_RELEASE_INDICATION Identify Fast Dormancy
• RRC_UPLINK_DIRECT_TRANSFER Capture NAS messages

RANAP • RANAP_COMMON_ID Capture the IMSI for the call

Event • RANAP_IU_RELEASE_COMMAND Identify UMTS to GSM relocation
• RANAP_IU_RELEASE_COMPLETE Identify Call Release for UETR/CTR
• RANAP_IU_RELEASE_REQUEST Identify call release or dropped call
• RANAP_RELOCATION_COMMAND Identify direct retry to GSM
• RANAP_RELOCATION_PREPARATION_FAILURE Identify IRAT relocation preparation failure

NBAP • NBAP_RADIO_LINK_SETUP_REQUEST Identify propagation delay for GeoAnalysis

Event • NBAP_CELL_SETUP_REQUEST Identify propagation delay for GeoAnalysis

GPEH events to be collected

9. Select the UE Fraction for the percentage of mobile that will be recorded.
10. Input the schedule for the profile recording. It is advisable to make sure there is no others running
recording on the planned schedule.
11. Once complete, the collected GPEH files will be located in
“/var/opt/ericsson/nms_umts_pms_seg/segment1/GPEH/” folder.

Configure the GPEH collection parameter at the RNC

1. Start OSS Common Explorer.

2. Select the required RNC Node to perform GPEH recording.

3. Change the ‘GPEH Data Level’ parameter value according to the value in your recording scenario. The
recommend value for all data is 1.
4. Increase the value for ‘GPEH File Size’ parameter to 50,000 (50,000 KB).

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 35

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

Initiate GPEH collection

1. Select Performance > Initiate data Collection > WCDMA/LTE RAN Measurements to start the
WCDMA/LTE RAN Measurement tool.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 36

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

2. Select Administration >Add profile… to add a new profile.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 37

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

3. Add GPEH subscription profile wizard will appear on the screen as shown in the figure below. Select the
required recording type. (GPEH, CTR or UETR) Click Next button to proceed to the next step.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 38

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

4. Type in the Profile name and click Next button to proceed to the next step.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 39

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

5. Select RNC network elements should be observed and click Next button to proceed to the next step.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 40

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

6. Select the required RNC you would like to collect and click Next button to proceed to the next step.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 41

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

7. Select the required Utran Cells for recording and click Next button to proceed to the next step.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 42

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

8. Select the events for the GPEH recording and click Next button to proceed to the next step. Please refer
to section 3.4.1 for GPEH Recording Scenarios for the required events on different analysis scenarios.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 43

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

9. Select the UE Fraction (Percentage of mobile that will be recorded) and click Next button to proceed to
the next step.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 44

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

10. Select the schedule for the subscription profile.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 45

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

11. Monitor the progress at Profile display tab > General performance even handling profiles.

12. Once complete, the collected GPEH files will be located in

“/var/opt/ericsson/nms_umts_pms_seg/segment1/GPEH/” folder.

3.4.1 Ericsson GPEH Recording Scenarios

Following table shows the different analysis scenarios in Xeus Pro 5 and the recommended data collection
configuration.
Analysis Type Recommended GPEH Event to be collected Cell Set Recording
Setting
Problem Cells detail GPEH Internal Event Problem cells only. gpehDataLevel =
analysis such as  INTERNAL_ADMISSION_CONTROL_RESPONSE Not more than 1 (ALL DATA)
troubleshooting of  INTERNAL_CALL_REESTABLISHMENT 10% of total RNC
dropped call,  INTERNAL_CALL_SETUP_FAIL limit Ue_Fraction =
blocked call and  INTERNAL_CHANNEL_SWITCHING 500
Throughput. User  INTERNAL_CMODE_ACTIVATE
needs to analyze  INTERNAL_CMODE_DEACTIVATE
call messages with  INTERNAL_CNHHO_EXECUTION_ACTIVE
message details.  INTERNAL_FAILED_HSDSCH_CELL_CHANGE
 INTERNAL_FAILED_TRANSITION_TO_DCH
 INTERNAL_HSDSCH_CELL_SELECTION_NO_CELL_SELE
CTED
 INTERNAL_IFHO_EXECUTION_ACTIVE
 INTERNAL_IMSI
 INTERNAL_IRAT_HO_CC_EVALUATION

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 46

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

 INTERNAL_IRAT_HO_CC_EXECUTION
 INTERNAL_MEASUREMENT_HANDLING_EXECUTION
 INTERNAL_PACKET_DEDICATED_ THROUGHPUT
 INTERNAL_RAB_ESTABLISHMENT
 INTERNAL_RAB_RELEASE
 INTERNAL_RADIO_QUALITY_MEASUREMENTS_UEH
 INTERNAL_SOFT_HANDOVER_EXECUTION
 INTERNAL_SOHO_DS_MISSING_NEIGHBOUR
 INTERNAL_SOHO_DS_UNMONITORED_NEIGHBOUR
 INTERNAL_SUCCESSFUL_HSDSCH_CELL_CHANGE
 INTERNAL_SUCCESSFUL_HSDSCH_CELL_SELECTION_
NEW_ACTIVE_SET
 INTERNAL_SUCCESSFUL_HSDSCH_CELL_SELECTION_
OLD_ACTIVE_SET
 INTERNAL_SUCCESSFUL_TRANSITION_TO_DCH
 INTERNAL_SYSTEM_BLOCK
 INTERNAL_SYSTEM_RELEASE
 INTERNAL_SYSTEM_UTILIZATION
 INTERNAL_OUT_HARD_HANDOVER_FAILURE
 INTERNAL_OUT_HARD_HANDOVER_SUCCESS

RRC Event
 RRC_CELL_CHANGE_ORDER_FROM_UTRAN
 RRC_CELL_CHANGE_ORDER_FROM_UTRAN_FAILURE
 RRC_CONNECTION_REJECT
 RRC_CONNECTION_RELEASE
 RRC_CONNECTION_REQUEST
 RRC_CONNECTION_SETUP_COMPLETE
 RRC_DOWNLINK_DIRECT_TRANSFER
 RRC_HANDOVER_FROM_UTRAN_COMMAND
 RRC_HANDOVER_FROM_UTRAN_FAILURE
 RRC_INITIAL_DIRECT_TRANSFER
 RRC_MEASUREMENT_CONTROL
 RRC_MEASUREMENT_REPORT
 RRC_UPLINK_DIRECT_TRANSFER

RANAP Event
 RANAP_COMMON_ID
 RANAP_IU_RELEASE_COMMAND
 RANAP_IU_RELEASE_REQUEST
 RANAP_RELOCATION_COMMAND
 RANAP_RELOCATION_PREPARATION_FAILURE

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 47

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

NBAP Event
 NBAP_RADIO_LINK_SETUP_REQUEST

Cell Analysis, GPEH Internal Event Whole RNC gpehDataLevel =

Scatter and  INTERNAL_CALL_REESTABLISHMENT 0 (HEADER
Distribution Chart  INTERNAL_CHANNEL_SWITCHING ONLY)*
 INTERNAL_CNHHO_EXECUTION_ACTIVE
 INTERNAL_FAILED_HSDSCH_CELL_CHANGE Ue_Fraction =
 INTERNAL_FAILED_TRANSITION_TO_DCH 500
 INTERNAL_HSDSCH_CELL_SELECTION_NO_CELL_SELE
CTED *The plot will be
 INTERNAL_IFHO_EXECUTION_ACTIVE limited to the
 INTERNAL_IRAT_HO_CC_EVALUATION Active Set from
 INTERNAL_IRAT_HO_CC_EXECUTION the internal
message.
 INTERNAL_MEASUREMENT_HANDLING_EXECUTION
Monitored Set
 INTERNAL_PACKET_DEDICATED_THROUGHPUT
measurement
 INTERNAL_RAB_ESTABLISHMENT
will not be
 INTERNAL_RAB_RELEASE
available
 INTERNAL_RADIO_QUALITY_MEASUREMENTS_UEH
 INTERNAL_SOFT_HANDOVER_EXECUTION
 INTERNAL_SOHO_DS_MISSING_NEIGHBOUR
 INTERNAL_SOHO_DS_UNMONITORED_NEIGHBOUR
 INTERNAL_SUCCESSFUL_HSDSCH_CELL_CHANGE
 INTERNAL_SUCCESSFUL_HSDSCH_CELL_SELECTION_
NEW_ACTIVE_SET
 INTERNAL_SUCCESSFUL_HSDSCH_CELL_SELECTION_
OLD_ACTIVE_SET
 INTERNAL_SUCCESSFUL_TRANSITION_TO_DCH
 INTERNAL_SYSTEM_BLOCK
 INTERNAL_SYSTEM_RELEASE
 INTERNAL_SYSTEM_UTILIZATION
 INTERNAL_OUT_HARD_HANDOVER_FAILURE
 INTERNAL_OUT_HARD_HANDOVER_SUCCESS

NBAP Event
 NBAP_RADIO_LINK_SETUP_REQUEST

RANAP Event
 RANAP_COMMON_ID

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 48

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

Neighbor GPEH Internal Event Whole RNC gpehDataLevel =

Optimization  INTERNAL_CALL_REESTABLISHMENT 0 (HEADER
including missing  INTERNAL_SOFT_HANDOVER_EXECUTION ONLY)
neighbor and Pilot  INTERNAL_SOHO_DS_MISSING_NEIGHBOUR
Pollution Analysis  INTERNAL_SOHO_DS_UNMONITORED_NEIGHBOUR Ue_Fraction =
 INTERNAL_OUT_HARD_HANDOVER_FAILURE 800
 INTERNAL_OUT_HARD_HANDOVER_SUCCESS

RRC Event
 RRC_CONNECTION_RELEASE
 RRC_CONNECTION_REQUEST

NBAP Event
 NBAP_RADIO_LINK_SETUP_REQUEST

RANAP Event
 RANAP_COMMON_ID
Phone Profiling GPEH Internal Event Whole RNC gpehDataLevel =
 INTERNAL_ADMISSION_CONTROL_RESPONSE 1 (ALL DATA)
 INTERNAL_CALL_REESTABLISHMENT
 INTERNAL_CALL_SETUP_FAIL Ue_Fraction =
 INTERNAL_CNHHO_EXECUTION_ACTIVE 500
 INTERNAL_FAILED_HSDSCH_CELL_CHANGE
 INTERNAL_FAILED_TRANSITION_TO_DCH
 INTERNAL_IFHO_EXECUTION_ACTIVE
 INTERNAL_IRAT_HO_CC_EXECUTION
 INTERNAL_MEASUREMENT_HANDLING_EXECUTION
 INTERNAL_RAB_ESTABLISHMENT
 INTERNAL_RADIO_QUALITY_MEASUREMENTS_UEH
 INTERNAL_SOFT_HANDOVER_EXECUTION
 INTERNAL_SOHO_DS_MISSING_NEIGHBOUR
 INTERNAL_SOHO_DS_UNMONITORED_NEIGHBOUR
 INTERNAL_SYSTEM_BLOCK
 INTERNAL_SYSTEM_RELEASE

RRC Event
 RRC_CONNECTION_RELEASE
 RRC_CONNECTION_REQUEST
 RRC_DOWNLINK_DIRECT_TRANSFER
 RRC_INITIAL_DIRECT_TRANSFER (Mandatory)
 RRC_UPLINK_DIRECT_TRANSFER (Mandatory)

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 49

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

RANAP Event
 RANAP_COMMON_ID
 RANAP_IU_RELEASE_COMMAND
 RANAP_IU_RELEASE_REQUEST

NBAP Event
 NBAP_RADIO_LINK_SETUP_REQUEST

Smartphone RRC Event Whole RNC gpehDataLevel =

Analysis  RRC_CONNECTION_RELEASE 1 (ALL DATA)
 RRC_CONNECTION_REQUEST
 RRC_DOWNLINK_DIRECT_TRANSFER Ue_Fraction =
 RRC_INITIAL_DIRECT_TRANSFER (Mandatory) 500
 RRC_UPLINK_DIRECT_TRANSFER (Mandatory)

NBAP Event
 NBAP_CELL_SETUP_REQUEST

RANAP Event
 RANAP_COMMON_ID
 RANAP_IU_RELEASE_COMMAND
 RANAP_IU_RELEASE_REQUEST

GPEH Internal Event

 INTERNAL_CALL_REESTABLISHMENT
 INTERNAL_CALL_SETUP_FAIL
 INTERNAL_CHANNEL_SWITCHING
 INTERNAL_IMSI
 INTERNAL_OUT_HARD_HANDOVER_FAILURE
 INTERNAL_OUT_HAND_HANDOVER_SUCCESS
 INTERNAL_PACKET_DEDICATED_THROUGHPUT
 INTERNAL_PACKET_DEDICATED_THROUGHPUT_CON
V_SPEECH
 INTERNAL_PACKET_DEDICATED_THROUGHPUT_CON
V_UNKNOWN
 INTERNAL_PACKET_DEDICATED_THROUGHPUT_STRE
AMING
 INTERNAL_RAB_ESTABLISHMENT
 INTERNAL_RAB_RELEASE
 INTERNAL_SYSTEM_BLOCK

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 50

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

GPEH Plots RRC Event Whole RNC gpehDataLevel =

 RRC_CONNECTION_RELEASE 1 (ALL DATA)
 RRC_CONNECTION_REQUEST
 RRC_MEASUREMENT_REPORT Ue_Fraction =
500
NBAP Event
 NBAP_RADIO_LINK_SETUP_REQUEST

GPEH Internal Event

 INTERNAL_SYSTEM_RELEASE

GPEH Recording Scenarios

Analysis Type Recommended UETR/CTR Event to be collected

Call Trace (UETR) or RRC Event
Cell Trace (CTR)  All RRC events
RANAP Event
 All RANAP events
NBAP Event
 All NBAP events

Appendix: Recommended Events for UETR/CTR Analysis

3.5 Ericsson LTE (Cell Trace)

Data Collection Instructions

Here is a table of events and the protocol required to be collected. The events that are available for CTR and
UETR respectively are marked by a tick:

Event Name Protocol CTR UETR

INTERNAL_EVENT_UE_MOBILITY_EVAL INTERNAL  
INTERNAL_PER_CELL_TRAFFIC_REPORT INTERNAL 
INTERNAL_PER_RADIO_CELL_MEASUREMENT INTERNAL 
INTERNAL_PER_RADIO_UE_MEASUREMENT INTERNAL 
INTERNAL_PER_RADIO_UE_MEASUREMENT_TA INTERNAL  
INTERNAL_PER_RADIO_UTILIZATION INTERNAL 
INTERNAL_PER_UE_RB_TRAFFIC_REP INTERNAL 
INTERNAL_PER_UE_TRAFFIC_REP INTERNAL 

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 51

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

INTERNAL_PER_UETR_CELL_TRAFFIC_REPORT INTERNAL 
INTERNAL_PER_UETR_RADIO_CELL_MEASUREMENT INTERNAL 
INTERNAL_PER_UETR_RADIO_UE_MEASUREMENT INTERNAL 
INTERNAL_PER_UETR_RADIO_UTILIZATION INTERNAL 
INTERNAL_PER_UETR_UE_RB_TRAFFIC_REP INTERNAL 
INTERNAL_PER_UETR_UE_TRAFFIC_REP INTERNAL 
INTERNAL_PROC_ERAB_RELEASE INTERNAL  
INTERNAL_PROC_ERAB_SETUP INTERNAL  
INTERNAL_PROC_HO_EXEC_S1_IN INTERNAL  
INTERNAL_PROC_HO_EXEC_S1_OUT INTERNAL  
INTERNAL_PROC_HO_EXEC_X2_IN INTERNAL  
INTERNAL_PROC_HO_EXEC_X2_OUT INTERNAL  
INTERNAL_PROC_INITIAL_CTXT_SETUP INTERNAL  
INTERNAL_PROC_RRC_CONN_SETUP INTERNAL  
INTERNAL_PROC_S1_SETUP INTERNAL  
INTERNAL_PROC_S1_SIG_CONN_SETUP INTERNAL  
INTERNAL_PROC_UE_CTXT_RELEASE INTERNAL  
RRC_MEASUREMENT_REPORT RRC  
RRC_RRC_CONNECTION_RECONFIGURATION RRC  
RRC_RRC_CONNECTION_RECONFIGURATION_COMPLETE RRC  
RRC_RRC_CONNECTION_RELEASE RRC  
RRC_RRC_CONNECTION_REQUEST RRC  
RRC_RRC_CONNECTION_SETUP RRC  
RRC_RRC_CONNECTION_SETUP_COMPLETE RRC  
S1_DOWNLINK_NAS_TRANSPORT S1  
S1_ERAB_RELEASE_COMMAND S1  
S1_ERAB_RELEASE_REQUEST S1  
S1_ERAB_SETUP_REQUEST S1  
S1_ERAB_SETUP_RESPONSE S1  
S1_ERAB_RELEASE_INDICATION S1  
S1_HANDOVER_COMMAND S1  
S1_HANDOVER_REQUEST S1  
S1_HANDOVER_REQUIRED S1  
S1_INITIAL_CONTEXT_SETUP_REQUEST S1  
S1_INITIAL_CONTEXT_SETUP_RESPONSE S1  
S1_INITIAL_UE_MESSAGE S1  
S1_UE_CONTEXT_RELEASE_COMMAND S1  
S1_UE_CONTEXT_RELEASE_REQUEST S1  

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 52

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

S1_UPLINK_NAS_TRANSPORT S1  
X2_HANDOVER_REQUEST X2  
X2_HANDOVER_REQUEST_ACKNOWLEDGE X2  

The following is the data collection steps :

1. On the Performance menu of the OSS Network Explorer window, click Initiate data Collection then click
RAN Measurements.

2. To create a new Subscription Profile select Add profile from the Administration menu, then the Add
subscription profile wizard will appear. There follows a series of steps at the end of which a new
Subscription Profile will be created. Move between the steps using the Next and Previous buttons.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 53

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

3. Choose LTE Cell Trace Profile

4. At the select eRBS, select at least 10 eRBS that are in the same cluster.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 54

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

5. Click next, and select the Output Format as File

6. Click next, select all Cells
7. Click next, select All Events
8. Click next, leave the UE Fraction at 1000
9. Click Next, Select “Enable ASN.1”
10. Click Next to set up Schedule. Choose immediate and run the trace for 3 hours.
11. Follow through to start the recording.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 55

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

12. At the LTE Cell Trace Profiles tab, select the newly created profile, Right click on the UE ID Mapping label
and select “Enable UE ID mapping”

13. Get the output at the OSS directory

14. The output files will have name like below
“A20120201.2145+0100-
2200+0100_SubNetwork=ONAN_ROOT_MO_R,SubNetwork=Demo,MeContext=RBS123_celltracefile_1.bin.gz “

There would be one file per RBS for every 15 minutes.

3.5.1 Ericsson LTE MME EBM Trace

The Ericsson LTE MME EBM Trace file correlates with Ericsson LTE Call Trace. The aim is to provide IMSI
information to the calls logged in the LTE Call Trace. Its format is *_ebs.* where the extension is a sequence
number.

Example:
A20110207.1115-0600-20110207.1130-0600_1_ebs.235
A20110207.1130-0600-20110207.1145-0600_1_ebs.236

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 56

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

Here are a list of events required to be collected :

Event Name
L_TAU
L_SERVICE_REQUEST
L_ATTACH
L_DETACH

3.6 Nokia WCDMA (Megamon)

Site Data
Users need to import the site data by XIF/TEMS Cel-file/ MCOM file format first before the importing of the Nokia
WCDMA RAML XML file.

The table below shows some of the mandatory fields in creating a XIF format site data:

XIF Parameter Description

CellId The unique Cell Identity/Name of the cell e.g. G1001A.

Note: Xeus Pro does not accept two records with SAME Cell Id. Any duplicate
cells Id will be renamed with additional suffix e.g. G1001A_1.

Mandatory field

SiteId The Site Id of the cell e.g. D1001.

Note: Site Id will be displayed as label for cell in the map

Longitude Longitude of the cell in Float format e.g. -121.23328.

Mandatory field

Latitude Latitude of the cell in Float format e.g. 30.12312.

Mandatory field

AntDir Direction of the cell in Degree unit

Mandatory field

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 57

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

RncId RNC Identity

Note: RncId-Cid pair allows matching of WCDMA Cell network data to the site
data in Xeus Pro database

CId WCDMA Cell Identity

Note: RncId-Cid pair allows matching of WCDMA Cell network data to the site
data in Xeus Pro database

XIF parameter format

Sample of XIF format

RNC Network Dump

You can import the WCDMA site configuration and neighbor data by importing the Nokia WCDMA RAML XML file.

Megamon .MGA Log File

Initial Megamon log files collection :
1. Start Megamon -> Setup -> Select “Connections”
Check with equipment vendors and make sure the control connections settings are set correctly.

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 58

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

2. Setup -> Select “Output files”

a. Set the output file directory
b. Do not check on the “output type” as the output file extension will be in *.MGA binary format.
c. Set the time based to 10 min
d. Check the PC HD space and apply conditional items removal accordingly
e. Do not check on any options settings
f. Set the format of the output filename as your preference. Advisable filename to include
network element with year, month, date, hour, minute and seconds.

3. Setup -> Select “Filter condition”

Check if there is Telecom filter with condition of
SR:(OFAM=4FD,507,508,509)AND(NOT(NUM=0001,0002,8037,8038,0D5BA,0A340,0A339,0D9DA,0D
5B8,0AB2B)), if no, create a new filter with condition.

4. Action -> Select “Get Units”

a. Only check on the ICSU units
b. Set all ICSU with “Telecoms” filter & leave “Via” column settings as “N/A”
c. After click “Set Filters” then confirm “Status=OK”-> Click “Start mon”
d. Check output directory and find the log files
e. Click “Stop” once the Megamon log collection is done.

5. Mandatory message – > rak_modify_rnc_param_s

3.7 ZTE WCDMA (CTS)

1. Login to NetNumen with the details

2. Subscriber Trace > Create Subscriber Trace Task (repeat step for each IMSI)

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 59

 Call Trace & Network Parameter Collection Procedures

Collection Procedures

InfoVista Confidential - Copyright © 2015 InfoVista S.A. All rights reserved. 60