ultima forte required data inputs for ericsson markets 2g-3g infrastructure.pdf

8/9/2019 Ultima forte required data inputs for ericsson markets 2g-3g infrastructure.pdf

1/28

Ultima Fort Required Data Inputs for Ericsson Markets 2G-3G Infrastructure

May 08 Proprietary and Confidential Page 1 of 28

Schema

Ultima Fort

Required Data Inputs for EricssonMarkets 2G-3G Infrastructure(for Version 4.0 and above)

Copyright Notice

Due to a policy of continuous product development and refinement, Schema reserves the right to alter thespecifications and descriptions outlined in this publication without giving prior notice of any kind. In addition,

no part of this publication, taken as a whole or separately, shall be deemed to be part of any contract forequipment or services.

Schema retains the sole proprietary rights to all information contained in this document. No part of thispublication may be reproduced, stored in a retrieval system, transmitted in any form or by any means,

including but not limited to: electronic, mechanical, magnetic, photocopy, recording, or otherwise, in use now

or in the future, without prior written consent from Schema.

Copyright 2008 Schema


2/28



Schema

Table of Contents

1 Introduction.............................................................................................. 4

2 Required Information and Data................................................................. 5

2.1 Optimization Area...........................................................................................5

Network Data........................................................................................................6

2.1.1 GSM Network Configuration....................................................................6

2.1.2 UMTS Network Configuration (XML Format) ..............................................7

2.1.3 Sector Coordinates File..........................................................................9

2.1.4 UMTS Antenna File.............................................................................. 10

2.1.5 *.mpr File.......................................................................................... 11

2.1.6 Generic Loss File................................................................................. 11

2.1.7 Mobile Measurement Data Recordings.................................................... 122.1.8 Activation of Recordings ...................................................................... 13

2.1.9 Retrieval of Recordings........................................................................19

2.2 Handover Statistics....................................................................................... 21

2.3 Network Performance Statistics ...................................................................... 22

2.3.1 Network Performance Evaluation........................................................... 24

2.3.2 Radio Network Performance KPI Calculation............................................ 24

3 Data Collection Checklist......................................................................... 26

4 Appendix: Troubleshooting ..................................................................... 27

4.1.1 The removeFile Parameter for BARFIL and MRR File Deletion..................... 27

4.1.2 Additional Ericsson Information............................................................. 284.1.3 Parameter Database (PDB) Maps .......................................................... 28


3/28


4/28



Schema

1 Introduct ion

This document contains a list of all the required information and data that must be collected on

Ericsson GSM infrastructures for execution of the optional GSMUMTS Neighbor List

Optimization feature in Ultima Fort v4.0, for systems with the Ericsson GSM infrastructure.

The following data is required:

Optimization area

Ericsson BSS network configuration data (XML format)

UMTS system network configuration (vendor XML format or Schema Format)

GSM Sector coordinates data

UMTS antenna file

UMTS-to-GSM handover statistics

UTRAN neighboring cell quality measurements

Generic Loss File (optional)

Performance reports

The following data and information is required:

Optimization area

Nokia BSS network configuration data (XML format)

UMTS system network configuration (vendor XML format or Schema Format)

GSM Sector coordinates data

UMTS antenna file

UMTS-to-GSM handover statistics AKA Counter 93 (Section 2.3)

UTRAN neighboring cell quality measurements AKA Counter 94 (Section 2.3)

Generic Loss File (optional)

Performance reports

The following sections provide a more in-depth description of the required data sources and

how to obtain them.


5/28



Schema

2 Requi red Information and Data

2.1 Optim izat ion Ar eaThe definition of the network area to be optimized is:

List of cells (from both networks) in the optimization area

Extended list of cells, including a guard zone (in which only GSM cells required)

Both lists are .txt files with one column, the first item being the word Sector, followed by a list

of sector names (both GSM and UMTS).

These lists can be generated by using the Ultima Fort selection tool, and saving the

selection.


6/28



Schema

Netw or k Data

2.1.1 GSM Netwo rk Conf ig urat io n

2.1.1.1 CNA Export in Text Format

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)

Notes:

Foreign cell data must be exported in order to import the IRAT Handover with any UMTS

network (Ericsson, as well as Nokia).

Daily CNA adjustment jobs should be scheduled for each BSC to ensure that the network

configuration is updated in the OSS.

It is recommended that the BSS network configuration file be retrieved for each day of

mobile measurement recordings. However, it is mandatory that this file be retrieved if any

BCCH/BSIC changes were made between two days of recordings.

The BSS network configuration file should be generated just before initiating the BAR and

MRR recording sessions.

The BSS network configuration should be retrieved for each OSS that is relevant to the

optimization and surrounding areas in the network.

BSC data is optional beginning from Release R12.

At the beginning and end of the data collection process, the following optional data should be

retrieved for all BSCs, and included in the Ultima Fort network environment:


7/28



Schema

Data Description

RLCRP:CELL=ALL,DETAIL;Cell ResourcesDetails

RXMOP:MOTY=RXOTG;Managed ObjectData

RAEPP:ID=ALL;BSC ExchangeProperties

Data retrieval should be performed via the BSC command line interface.

The output of the command printout should be stored in text files. The command name (RLCRP,

RXMOP, RAEPP) of each output type should be at the beginning of the file name, e.g.,

RLCRP_BSC1.txt.

2.1.1.2 New CNAI Export Format - R12:

Release R12 supports the New CNAI (CNA Import) alternative format for network configuration

files.

The required BSS network configuration file can be retrieved from the Cellular Network

Administrator (CNA) of the Ericsson OSS, using the following command: CNAI export valid i >

AllParameters_YYYYMMDD.txt.

2.1.2 UMTS Networ k Conf ig ur at io n (XML Form at)The UMTS Network configuration is an XML file in standard 3GPP format. Each UMTS OSS

vendor has its own method of retrieving this file.


8/28



Schema

To retrieve the required BSS network configuration files from the Ericsson OSS:

1. Go to ConfigurationWCDMA Radio access NetworkWCDMA RAN Explorer (usually via

Citrix or OSS workstation).

2.

Right click on the root of the network and select Export Network Configuration.

Figure 1: Retrieve the Required BSS Network Configuration Files

Figure 2: Export the Required BSS Network Configuration Files


9/28



Schema

Choose the File Name and Radio topology.

Figure 3: Save the Required BSS Network Configuration Files

2.1.3 Secto r Coord inates Fi le

The sector coordinates file should be in tab-delimited text file format, and should include

geographical information for all of the network sectors, including the following columns:

Sector

Latitude

Longitude

Azimuth

LAC (optional)

CI (optional)

Keywords (optional)

The latitude and longitude values should be expressed in decimal-degree format, with up to six

digits following the decimal point.


10/28



Schema

2.1.4 UMTS An ten na Fil e

The UMTS Antenna file must be in tab-delimited text file format with full information for all the

sectors in the optimization and guard-zone areas.

Note: This file contains many fields (intended for future use), whose values are not currently

used for the GSMUMTS Neighbor List Optimization feature.

The required fields are in boldletters. Non-required fields should have real values for

database integrity (but the feature can run with dummy values).

RNC Name

RNC Id

Vendor

NodeB Name

NodeB Id

NodeB Longitude

NodeB Latitude

Sector Name

Active (boolean)

Noise Figure

AntennaID

Antenna Model

Sector Keywords

Antenna Longitude

Antenna Latitude

Height

Electrical DownTilt

Mechanical DownTilt

Azimuth

Downlink Loss

Uplink Loss RTT fix A Coefficient

RTT fix B Coefficient

In Building


11/28



Schema

The following file has a sample entry that corresponds to one antenna.

Antennas.txt

2.1.5 *.mpr Fi le

The .mpr file is a text file (with the *.mpr extension) that points to the UTRAN topology file with

the following pointer:

ERICSSON_XML_FILE_NAME=path\topology_file_name.xml

2.1.6 Generic Lo ss Fi le

The Generic Loss File is of a generic horizontal antenna pattern, used to determine the order of

potential neighbors in a measurement plan.

If a user-defined file (optional) is not provided, Ultima Fort uses a one-column text file, with

default values for each relative angle between the source and target sectors, in the following

structure:

Relative angle[degrees]= Loss[dB]

For example:

0=0

1=0

2=0.01

3=0.03

4=0.05

5=0.08

6=0.12

7=0.15

8=0.2

9=0.25

..

359=0


12/28



Schema

The following is a full example of the file:

GenericLossFile.txt

2.1.7 Mobi le Measurement Data Recor din gs

The following activities should stop during data recording:

BSC or RNC split

Site re-parenting (e.g., BSC/site relation changes in the GSM network)

LAC and CI changes in the GSM network, scrambling codes in the UMTS network, BCCH and

BSIC in the GSM network

Site and carrier additions

Sector mechanical changes, such as tilt, azimuth, and antenna

Manual UMTS GSM Neighbor additions or deletions

The following changes should be performed only during maintenance (not during recording):

TRX/Carrier additions

Frequency changes (TCH)

Frequency changes (BCCH and BSIC)

Scrambling codes changes

Manual UMTS GSM Neighbor additions or deletions

Site additions

No other parameters should be changed.

Note: BSC Version R06A (R12) (or later versions) should be used.

OSS Version RC3, RC5.3 (or later versions) should be used.

The following features should be activated to collect mobile measurements on the

Ericsson GSM OSS:

NCS-G, (NCS-GSM)

NCS-GW, (NCS-GSM/WCDMA)

In addition to the optional OSS NCS GSM-WCDMA feature, the following features are required

for IRAT modeling:


13/28



Schema

Optional OSS features:

o FAJ 122 477, Neighboring Cell Support - GSM RAN (NCS-G)

Optional BSS features:

o

FAJ 121 815, GSM-WCDMA Active BA-list Recording

o FAJ 121 57, GSM-UMTS Cell Reselection and Handover

Mobile measurements files can be extracted from the Ericsson OSS, and used by Ultima Fort

either in binary format (Section 2.3.1) or in text format (Section 2.3.2).

2.1.8 Act i vat ion of Recor din gs

2.1.8.1 BA List Recordings (BAR) Recordings

BAR recordings should be performed during three to five consecutive working days.BAR recording is activated by:

RNO interface (if available): FAJ 122 477 Neighboring Cell Support - GSM RAN (NCS-G)

BSC command interface

To perform BAR recordings, using the RNO interface:

1. Log in to OSS.

2. Start RNO.

3.

Go to File

New Recording

NCS.4. Name the recording session.

5. Select the Measure GSMand Measure WCDMAcheck boxes.

6. Set the Relative SS Threshold to -12db.

7. Set the Absolute SS Threshold to -80dbm.

8. Set the BA List Change interval to 15 minutes.

9. Set the number of test frequencies to add to each interval to 10.

10.Enter a start date.

11.Enter a repeat value (set to daily) and a number of repetitions (set to 5).

12.Enter a date type with working days only (e.g., Monday to Friday five consecutive

working days).

13.Enter an hour range (four hours that include the network busy hour).

14.Select the cell set or BSC (including every cell in the entire network).


14/28



Schema

15.Set the Cell Filter to a desired (available) frequency band (with the recorded cell set

limited to a specified frequency band.)

16.Select Frequencies. Create a Frequency Set for BAR recordings, including all frequencies

used for the BCCH in the desired band for the entire network.

17.Save and schedule the recording.

Figure 4: RNO NCS New Recording

Noteon WCDMA Settings:

The recording configuration consists of the following:

Number of WCDMA cells in each Measurement report.

An Absolute Ec/No threshold.

The maximum number of test UMFIs that may be added to the 3G active mode BA lists

at one time.

A set of test-UMFIs to be used in recording.

The number of WCDMA cells in each measurement report is a recording parameter that can be

set to either Network Settingsor to a numerical value between 1 and 3. The Network

Settings value uses the current FDDMRRnetwork setting for the recording, which will remain


15/28



Schema

the same. The numerical values will activate a temporary value of the FDDMRRparameter to

be used during recording. When active, this temporary value, called TFDDMRR,blocks any

FDDMRR value update for the cells included in the recording.

The temporary value is used to increase the amount of measurement data during the recording,and affects how the Multi-RAT mobiles report data in the measurement report. This, in turn,

may affect the locating performance.

The absolute Ec/No threshold is related to a counter, which is incremented whenever the

Ec/NoUMFI> absequation is fulfilled absis the Ec/No absolute threshold and Ec/NoUMFIis the

Ec/No value for a specific UMFI, reported by the Multi-Rat mobile. The ratio between Ec/NoUMFI

and the number of measurement reports that include at least one reported UMFI during the

period when the specific UMFI has been included in the 3G Active BA-list for the cell is a value

that is used to determine whether or not the undefined WCDMA neighboring cell is included as a

defined neighbor.

A function calculates an appropriate set of test-UMFIs, based on a set of GSM cells. The WCDMA

cell coordinates determine which of those cells, located in the same area as the GSM cells, are

included in the recording. The user defines at which distance from the GSM cells the search is

performed. A list of test-UMFIs is then generated, based on the WCDMA cells that are found.

Since a maximum of 128 test-UMFIs may be included in a set, four recordings are needed to

measure all 512 Scrambling Codes for a single WCDMA-frequency.


16/28



Schema

Figure 5: RNO NCS UMTS Settings

Figure 6: RNO NCS New UMFI Set


17/28



Schema

Figure 7: RNO NCS Select Cell Set

Additional Notes:

Recordings in a dual band network should be made separately, based on the cell band.

However, to provide full functionality of handover optimization, inter-band recordings

should be made. Each band cell set should record a frequency set with the BCCH

frequencies for both bands. Multi Band Cells Reported (MBCR), is a cell parameter that

indicates how many neighbors from each frequency band are reported in the

measurement report. The recommended setting is either 2 or 3 in multi-band network,

in order for mobiles to report measurements from the opposite band.

While BAR files can also be generated with the Frequency Allocation Support (FAS), the

Neighboring Cell Support (NCS) should be used if possible.

The NCCPERM defines the allowed NCCs on the BCCH carriers for which MSs are

permitted to send measurement reports. Hence, if all NCCs are used, NCCPERM should

be set accordingly (i.e., all NCCs included in NCCPERM parameter) so that all NCCs are

reported. NCCPERM has no impact on idle mode behavior, since idle mode cell

reselection is based on CGI, and not on ARFCN/BSIC).

The Active BA list Recording may sometimes contain measurement results with

unexpected, disallowed BSICs, (e.g., 00 or 77). This occurs when some MSs report

irrelevant BSICs initially, before decoding actual BSIC information and is not related to a

fault in the BA List recordings feature.

If an operator has not purchased the RNO application to activate BAR recordings through NCS,

the BAR recordings can be activated, using the following BSC command line interface:


18/28



Schema

1. RABRE:RID=RARID00; Terminate an NCS recording.

2. RABIE:RID=BARID00; Delete a recording.

3. RABII; Initiate a new recording.

4.

RABRP:RID=BARID00; Print a BAR recording status (optional).

5. RABDC:RID=BARID00, CELL=ALL; Record all BSC cells.

6. RABDC:RID=BARID00,TMBCCHNO=50&&124; Frequencies to measure 50 to 124.*

7. RABDC:RID=BARID00,NUMFREQ=10; The number of test frequencies at each interval.

8. RABDC:RID=BARID00,SEGTIME=15; The recording segment time in minutes.

9. RABDC:RID=BARID00,RELSSN=12; Negative signal strength thresholds.

10.RABDC:RID=BARID00,RELSS2P=0; Positive signal strength thresholds.

11.

RABDC:RID=BARID00, ABSS=80; Absolute signal strength (means negative dBm).12.RABDP:RID=BARID00; View recording properties.

13.RABRI:RID=BARID00,DTIME=120; Recording period time in minutes, beginning as soon

as this command is entered!

14.RABTI:RID=BARID00,IO=FILE; After recording is complete, this command creates the

output binary file in the OSS.

15.RABTI:RID=BARID00, IO=AT-##; Substitute at-## with the number of the AT device

seen when connecting to this BSC. The text output iproduced on the AT-## device**.

* - The relevant frequency set should be used for each specific case.

** - If, for some reason, a binary file cannot be created, the BAR text output can be

generated at the BSC command terminal, with the generated printout being stored as a

text file.

2.1.8.2 MRR Recordings

Measurement Results Recordings (MRR) are files that contain RxLevel, RxQual, and traffic data.

MRR recordings should be generated with, and for the same cell set as, BAR recordings, and

without filtering or thresholds.

An MRR recording may be activated via:

RNO interface (if available): FAJ 122 522, Measurement Result Recording (MRR)

BSC command interface

To make MRR recordings using the RNO interface:


19/28



Schema

1. Log in to OSS.

2. Start RNO.

3. Go to File

New Recording

MRR.

4.

Name the recording session.

5. Enter a Start date.

6. Enter a repeat value (set to daily) and a number of repetitions (set to 5).

7. Enter a date type with working days only (Monday to Friday five consecutive working

days).

8. Enter an hour range (three hours defined to include the network busy hour).

9. Select the cell set or BSC (including every cell in the entire network).

10.Set Cell Filter to a desired (available) frequency band. (The recorded cell set is limited to

a specified frequency band.)

11.Save and schedule the recording.

In the absence of an RNO application, MRR recordings may be activated using the BSC

command line interface, as follows:

1. RAMRE: RID=MRRID00; Terminate an MRR recording.

2. RAMIE: RID=MRRID00; Delete a recording.

3. RAMII; Initialize a new recording.

4.

RAMRP: RID=MRRID00; Print status (optional).5. RAMDC: RID=MRRID00, CELL=ALL; All cells of a BSC are recorded.

6. RAMDC: RID=MRRID00, MEASTYPE=NOTYPE; All measurement types are collected.

7. RAMRI: RID=MRRID00, DTIME=120; Recording period time, which starts as soon as this

command is entered!

8. RAMRP: RID=MRRID00; Print status (optional).

9. RAMTI: RID=MRRID00; After the recording is finished, this command should be run to

create the output file.

2.1.9 Retr i eval of Recor din gs

2.1.9.1.1 BA list recordings (BAR) Record ings : Binary mode

Binary format files contain C/I measurements.


20/28



Schema

Once recording is finished, the BARFILs files should be stored for each BSC on FTP. If they are

not stored within 48 hours after recording, they will be deleted from the system.

Binary BARFILs files are located in the following OSS directories:

R8:

o /var/opt/ehpt/eac/data/fs/BSC_NAME/

R9/R10 and later with IOG20:

o /root/var/opt/ericsson/nms_eam_eac/data/fs/BSC_NAME/

R9/R10 and later with APG40:

o /root/var/opt/ericsson/brf/data/db/tmpfileStore/BSC_NAME/

Note:

The binary transfer method should be used to transfer BARFILs from UNIX to Windows via FTP.

All BARFILs recorded on the same day should be stored in the same directory.

The Appendix provides information on troubleshooting situations in which BAR files are not

created.

2.1.9.2 Measurement Resul ts Recordings (MRR) - Binary Mode

When the recording is finished, store the MRRFILs files for each BSC on an FTP. If they are not

stored within 48 hours after recording, they will be deleted from the system.

Binary MRRFILs files are located in the following OSS directories:

R8:

o /var/opt/ehpt/eac/data/fs/BSC_NAME/

R9/R10 and later with IOG20:

o /root/var/opt/ericsson/nms_eam_eac/data/fs/BSC_NAME/

R9/R10 and later with APG40:

o /root/var/opt/ericsson/brf/data/db/tmpfileStore/BSC_NAME/


21/28



Schema

Notes:

Use the binary transfer method to transfer MRRFILs from UNIX to Windows via FTP.

All MRRFILs recorded on the same day should be stored in the same directory.

The Appendix provides information on troubleshooting situations in which MRR files are not

created.

2.1.9.3 NCS Recordings - Text Format Files

NCS Recording files, available in the RNO application window, contain C/I measurements, which

are similar to the information available in the raw binary BAR recordings.

NCS files can be exported from the RNO application window in pairs, one with an *.msmt

extension (data) and one with a *.conf extension (file configurations and recordings

information).

2.1.9.4 MRR Recordings - Text Format Files

MRR Recording files contain RxLevel, RxQual, and traffic data, which can be extracted in either

binary or text formats. Text format can be exported directly form the RNO application window.

Text MRR files are extracted in pairs: one with an *.msmt extension (data) and one with a

*.conf extension (file configurations and recordings).

MRR recordings are exported to ASCII files via the RNO GUI. Both export files (*.msmt and

*.conf) should be transferred. The data from these files may be used to back up MRRFIL files.

2.2 Hando ver Stat i st ic s

Handover statistics for each cell-to-cell relation should be collected for handover optimization.

These statistics should be aggregated for an entire week for each cell-to-cell relation, and

provided in a tab-delimited text file with the following fields:

Serving Sector

Target Sector

Handover Attempts


22/28



Schema

Notes:

The following counter can be extracted from 3G OSS for IRAT Handovers from 3G to 2G

cells: pmnoattoutirathospeech

It is not necessary to import 3G to 3G handover attempts, since they are not optimized inFort.

2.3 Netw or k Perf orm ance Stat ist ic s

Network performance statistics should be collected for network traffic modeling and post-

optimization network performance benchmarking.

The following network performance statistics should be collected per cell, and calculated hourly

over seven consecutive days:

Overall GSM HO Performance (Cell to Cell Relation, HO Attempts, HO Reversions, HO Lost,).

These statistics should include the following counters: HOVERCNT, HOVERSUC, HORTTOCH,

HOASBCL, HOASWCL, HOUPLQA, HODWNQA, HOATTLSS, HOATTHSS.

Specific IRAT HO performance should be calculated from a 2G network using the following:

o The number of handover commands sent to mobile station, with the neighboring UTRAN

cell as target cell (HOVERCNTUTRAN).

o The number of successful handovers to the neighboring UTRAN cell (HOVERSUCUTRAN).

o The number of handover attempts to the neighboring UTRAN cell when the MS returned

to the old channel (HORTTOCHUTRAN).

o

The number of handover commands sent to mobile station due to urgency in the GSMcell, with the neighboring UTRAN cell as target cell (URGHOVERUTRAN).

o The number of successful handover attempts, due to urgency in the GSM cell, to the

neighboring UTRAN cell (SUCURGHOUTRAN).

Specific IRAT HO performance should be calculated from a 3G network using the following:

KPI DESC Equation

Voice 3G-2G IRAT HOFailure Rate (%)

IRAT failure rate forvoice calls when thetrigger is based on an RFcondition. When thevoice call is notsuccessfully handed overto GSM network, the callis returned to the UMTSnetwork and continues inUMTS until it attempts

100*[1-(pmnosuccessoutirathospeech/pmnoattouthospeech)]


23/28



Schema

another IRAT HO. Thiscounter will only beincremented in theSRNC.

Voice 3G-2G IRAT HOfailures

Total number of voiceIRAT 3G-2G failures.

(pmnoattoutirathospeech -pmnosuccessoutirathospeech)

Total Voice 3G-2G IRAT HO(incl SBHO) Failure Rate(%)

The IRAT failure rate forvoice calls when thetrigger is based on an RFcondition and a service-based handover. Whenthe voice call is notsuccessfully handed overto the GSM network, thecall is returned to theUMTS network and

continues in UMTS until itattempts another IRATHO. This counter willonly be incremented inthe SRNC.

100*[1-{pmNoSuccessOutIratHoSpeech+pmNoSucssSbHoSpeech}/{pmNoAttOutIratHoSpeecpmNoAttOutSbHoSpeech}]

Total Voice 3G-2G IRAT HO(incl SBHO) failures

Total number of IRATfailures, includingService based HOs.

[(pmNoAttOutIratHoSpeech+pmNoAttOutSoSpeech)-(pmNoSuccessOutIratHoSpeech+pmNoSucssSbHoSpeech)]

PS Interactive IRAT FailureRate (%)

The inter-RAT CC fromUTRAN to GPRS when UEis on DCH. The counter isincreased when the CellChange Order FromUTRAN Failure (RRC)message is received fromthe UE.

100*(pmnooutiratccreturnoldch/pmnooutircatt)

PS interactive IRAT HOfailures

Total number of PSinteractive IRAT failures (pmnooutiratccatt - pmNoOutIratCcSuccess

Multi-RAB IRAT Failure Rate(%)

The outgoing (to GSM)inter-RAT handoverfailure rate for multi-RABfor the best cell in the

active set. The counter isonly incremented inSRNC.

100*[1-{pmNoSuccessOutIratHoMulti/pmNoAttOuttHoMulti}]

Multi RAB IRAT HO failuresTotal number of Multi-RAB IRAT failures.

(pmNoAttOutIratHoMulti -pmNoSuccessOutIratHoMulti)


24/28



Schema

Hs Cell Change Failure Rate(%)

The HS Cell Changefailure rate. The counterstops after a RRCPhysical ChannelReconfigurationComplete has beenreceived from the UEduring the HS-DSCH CellChange, or after a RRCRadio BearerReconfiguration whenthere is a PDU sizechange during a HS-DSCH Cell Change.

100*[1-{pmNoHsCcSuccess/pmNoHsCcAttempt}]

HS Cell Change FailuresTotal number of HS CellChange failures, (pmNoHsCcAttempt - pmNoHsCcSuccess)

2.3.1 Netwo rk Perfo rmanc e Evaluat ion

Each KPI improvement rate will be calculated as:

%100__

=before

afterbefore

KPI

KPIKPIratetimprovemenKPI

The improvement in the handover success rate will be calculated as:

%1001

__

=

before

beforeafter

KPI

KPIKPIratetimprovemenSuccess

Each KPI improvement ratio can be calculated separately over a period of five working days

(during each days network busy hour) before and after the optimization cycle.

Any network performance KPIs that are not related to the BSS subsystem should be excluded

from the calculation.

2.3.2 Radio Netwo rk Perfo rmanc e KPI Calcu lat ion

The following formulae calculate the KPIs that evaluate radio network performance:

=)HOVERCNT(

)HOVERSUC(___ RateSuccessHOOutgoing


25/28



Schema

Outgoing 3G-2G IRAT HO Failure Rate (%) = (pmnosuccessoutirathospeech /

pmnoattoutirathospeech)

Outgoing 2G-3G IRAT HO Failure Rate (%) = HOVERSUCUTRAN/ HOVERCNTUTRAN


26/28



Schema

3 Data Col lect ion Checkl istSOURCE COMMENTS CHECK

Network Data

GSMS Network Configuration

UMTS Network Topology(XML)

GSM Sector Coordinates File

UMTS Antennas file

UMTS .mpr file

Generic Loss File optional

Mobile Measurements & IRAT HO statistics Recordings

Day 1 Day 2 Day 3 Day 4 Day 5

Prior to the measurementplan

During the measurementplan

After the measurement plan

Network Performance Statistics (before and after the plan)

IRAT HO failure rate UMTS-to-GSM HO attempts

UMTS-to-GSM HO Success


27/28



Schema

4 Appendix: Troub leshoot in g

BARFIL and MRRFIL files are transferred from the BSC to the OSS, once the recording has

finished.

4.1.1 The removeFi le Parameter for BARFIL and MRR Fi le Delet i on

To check the setting of the removeFile parameter:

1. Connect to the OSS via an external application, such as Citrix ICA Client.

2. Check the file removing option in OSS, which automatically deletes MS files (perhaps to

avoid hard disk space problems). The possible values for this parameter are:

removeFile Value Result

0MS files will not beremoved

1MS files will beremoved

Parameters in OSS are stored in Parameter Database (PDB) maps. The removeFile parameter

belongs to the BRF map.

To determine the value of the OSS parameters, use the cap_pdb_get_para command:

cap_pdb_get_para n brf removeFile

The Ericsson Alex Library has additional details.

3. Change the value of the file removing option from 1 to 0, using the cap_pdb_mu

command (with the correct user privileges). (If the file removing option is set to 1, files

will be deleted.) If the BRF map is edited with an editor such as VI, it may lock the

database, and the cap_pdb_mu command may not work with BRF. A user with Super

User access (and perhaps additional knowledge) may be able to resolve this problem.

4. Activate the NCS recording using the RNO.

5. Look for BARFIL and MRRFIL files after completing the collection process, since these

files must be located in their corresponding directories.

6. Return the file removing option to its original value (1) after completing the MS

collection. If this parameter is not changed back to the original value, the result may be

a reduction in hard disk space, in addition to other collateral problems.


28/28


4.1.2 Addi t i ona l Er icsso n In format ion

(This material originally appears in official documentation, entitled Op e r a t i o n s Su p p o r t

S y s t em ( O s s ) R c 1 . 1 , Cp 4 ).

Files retrieved from APG40 are stored in the /tmpFileStore/ directory.

File Description

The path is stated bythe dbPathparameter in BRFmap.

The BSC.

The removeFile parameter in the BRF map can be set up to delete files automatically, as

explained in the previous section.

4.1.3 Paramet er Databas e (PDB) Maps

Each application has its own parameter database map, with parameters relating to the current

installation.

When the appropriate command is entered in the command shell window (man -s7 ), additional map information is displayed on the main page.

Application Map Name

BRF Brf

FAS Fas

FOX Fox

NCS Ncs

NOX Nox

TET Tet

MRR Mrr

Use cap_pdb_mu to edit the map.

Note:

To edit system parameters, select RNO System Parametersfrom the Optionsmenu in the

RNO main window.

ultima forte required data inputs for ericsson markets 2g-3g infrastructure.pdf

Documents