EFO (xAFP) – Ericsson Interaction

Data collection
 1. Introduction
EFO (xAFP) PROCESS 8. Handover
Stats*

6. QoS Data
(Rxqual, rxlev, pc)

5. DAILY BCCH-
BSIC MAPPINGS

4. DAILY MOBILE
MEASUREMENTS
(MMR)

7. Traffic and %HR

Stats

3. Frequency
Constraints

2. BSS Configuration * Handover Stats may also be required at “MMR preparation”

1. Physical Data stage if BA list reduction by neighbor deletion IS PERFORMED

EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 2

 1. INTRODUCTION
Required Input Data Summary
1. Physical Data
– All sites to be retuned (core) as well as all relevant outer tiers (buffer) must be
included and flagged as core or buffer. Mandatory data:
› Sector ID
› Site Name
› Latitude
› Longitude
› Azimuth
› ERP (dBm)
› Antenna Name/Pattern
› Ground Elevation – Does not impact EFO (xAFP)
› Antenna Height Above Ground Level (>0)
› Total TILT – Does not impact EFO (xAFP)
2. Network Data (BSS configuration) – See multivendor support and interfaces
3. Frequency planning constraints (OPTIONAL):
– Combiner constraints, repeaters, forbidden parameters, local knowledge information.
4. Mobile Measurements Recordings (MMR)
– At least 2 weeks including weekends, collected daily, should cover at least the 4
busiest hours (may cover longer period if possible, i.e: 7am-10pm)an overview of
problems in the network!!
EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 3
 1. INTRODUCTION
Required Input Data Summary (II)
5. Daily BCCH – BSIC mappings
– Needed to match MMR
6. RxQual & RxLev and Power Control Stats per Sector Basis
– RxQual/RxLev/PC data recommended daily window covering the 3-4 busiest hours
7. Traffic and Half Rate penetration per sector
– Voice Traffic & Half Rate %
– Data Traffic: Recommended in networks with significant data traffic on TCH
layer (creates additional interference on voice) or if Data Traffic wants to be used
as driver for frequency plan.
• Data Erlangs-> PDCH Used Timeslots, split BCCH/TCH layer needed.
• Data Volume (optional) (Mbits)-> Only needed if frequency plan with
target cost including DATA traffic, split BCCH/TCH layer needed.
– Aggregation Method for voice & data traffic
– Averaged: Recommended 3-4 busiest hours (same as Rxqual/Rxlev/PowerControl) of
the network averaged (hourly and daily). It is used for Interference Matrix validation.
– Busy Hour: ISBH * per sector is averaged (hourly and daily). Used in the optimization
phase.
8. HO Stats
– Use the most recent neighbor DAILY HO attempts (Last 3-4 weeks )
EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 4 *ISBH = Individual Sector Busy Hour (peak traffic per sector)
EFO (xAFP) – Ericsson Interaction

2. Data collection
2.1 collection of cm data
› The network configuration to be used by EFO (xAFP) can
be obtained in 3 ways
1. Exported from Ericsson OSS via “old CNAI” dump
2. Exported from Ericsson OSS via “new CNAI” dump
3. Exported using MML commands dumps in each BSC

EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 6

2.1 collection of cm data
OLD CNAI DUMP
1. Export from Ericsson OSS via “old CNAI” dumps
Execute the following commands in OSS’ Shell
cna_export NW=all, MSC=all, MSC_REF=none, BSC=all, BSC_REF=none, CELL=all,
CELL_REF=all, OUTPUT=singleCNAI.txt
cna_export NW = all, FCELL = all, FCELL_REF = all, OUTPUT = fcell.txt
–singleCNAI.txt and fcell.txt(foreign cells) files will be exported to the default cnai export
folder /var/opt/ericsson/cnai/data/export/
–An log file of the export will also be created in /var/opt/ericsson/cnai/log/reports
–NW=all may also be substituted by NW=AXE or the network ID used by operator
–Export just for selected BSCs could also be obtained using BSC=bsclist.txt instead of BSC=all
› bsclist.txt is a text file list of BSC names separated by spaces by default needs to be
stored in /etc/opt/ericsson/cnai/data/ directory.
–Default directories used by cna_export can be changed for example to /home/[user]/[myfolder]
with these commands:
setenv CNA_EXPORT_DATA_DIR ~/[myfolder]-> Output file path
setenv CNA_DATA_DIR ~/[myfolder]-> Input file bsclist.txt path
setenv CNAI_REPORT_FILE_DIR ~/[myfolder]-> Log file path

EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 7

2.1 collection of cm data
NEW CNAI DUMP
2. Export from Ericsson OSS via “new CNAI” dumps
› This command exports all parameters for MOs in all domains of valid area to
singleCNAI_new.txt.
cnai export valid -i --output singleCNAI_new.txt
› This command exports all parameters for MSCs and selected BSCs and also
recursively all MOs in domains under BSC
cnai export valid -i MSC, -ir BSC=BSC01,BSC02,… --output singleCNAI_new.txt
›By default if no path specified file is stored in user’s home /home/[user]/

EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 8

2.1 collection of cm data
MML DUMP
3. Export using MML commands in each BSC
The following commands must be run on each BSC using the Command
Handler
RLDEP:cell=all; (Cell description Data)
RLCFP:cell=all; (Cell frequency data)
RLCHP:cell=all; (Cell hopping data)
RLNRP:cell=all; or RLNRP:cell=all,nodata; (Cell neighbor data)
RLSTP:cell=all; (Cell status data)
RLBDP:cell=all; (Cell Configuration BPC data)
›The result of each MML must be stored in separated files per
command and folders per BSC
Using Operation Procedure Support and Activity Manager
modules of OSS Network Explorer application, the MML
Automate MML
commands can be scheduled to be executed for all BSCs at export

specific intervals (attached file provides step-by-step details).

EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 9

2.1 collection of cm data
ADDITIONAL MML FILES
› Specially if using CNAI old or new formats, it is recommended to export
per BSC the following command dumps (both together in a file, per BSC)
1.RXMOP:MOTY=RXOTX; To obtain the number of TRXs by counting the
number of RXOTX objects per cell name
2.RXMOP:MOTY=RXOTG; To obtain the combiner type and TRX status
active hopping type.
3.RXMSP:MOTY=RXOTX; To obtain the TX status
› These additional dumps (1,2) can be used later by EFO to build a
mapping file “sector, chgr, #trx count, hop type” . (3) can tell which of
those TX are actually operative.
› This is useful because in some cases the CNAI information is not enough
to obtain this information and EFO needs to make assumptions.

EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 10

ho attempts, mMr & mRr

› HO attempts per neighbor relationship

HO Attempts
– 2-3 weeks of collection Sample

– 24 hours aggregation per relationship

› 1 value per relationship and day
› Mobile Measurements Reports (MMR) & Mobile Recording
Results (MRR)
– 2 weeks of collection
– 24 hours collection if possible
› At least system busy hour periods (~8 hours)
– Binary files
› BARFIL files for MMR
- Result of NCS or FAS collection through RNO or by MML commands in each BSC
› MRRFIL files for MRR

EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 11

Mmr activation & collection
activation ways

› MMR are gathered through Ericsson BAR binary files (raw data)
› Three possible ways are suggested to activate BAR files creation in
Ericsson infra (in order of preference):
1. Scheduling FAS measurements recordings through RNO
2. Scheduling NCS measurements recordings through RNO
3. Per BSC, using MML commands
- Just if RNO is not available

EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 12

2.2 Activation and Collection of MMR
A. Scheduling FAS recordings

- In dual band networks it is recommended to create 2 simultaneous FAS recording

tasks (typically duration of 2 weeks):
• One recoding task just for 850/900 Cells, to scan 850/900 BCCHs
• One recoding task just for 1900/850 Cells, to scan 1900/1800 BCCHs
- If having time for further collection, after finishing the previous, another FAS
recording can be launched for all cells together scanning all joint BCCHs from both
bands. Crossed band relations may be used in EFO (xAFP) to complete the
Interference Matrix (estimate co-bcch relations and other missing relations)
- Next slides describe the process to create a single FAS recording for 1900 Band,
the process is to be repeated for 850 Band in case of dual band network.
EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 13
 2.2 Activation and Collection of MMR
A. Scheduling FAS recordings (II)

• In the Time section the days of collection and

up to 4 periods per day can be defined.
• Typically all day except night included
(i.e:7am 11pm)
• Select Cells or Cell Set that includes all cells
in Core and Buffer areas of EFO (xAFP)
• “Create of FAS Result” check is not needed as
project.
EFO (xAFP) will just use the raw BAR binary
• If selecting complete BSCs, new cells will be
files
dynamically added to the recording.
• Recommended settings :
•
• Additionally, during MMR collection, multiband
Relative SS Threshold C/I = -12 dB
• Relative SS Threshold C/A= 3 dB reporting parameters are recommended to be
• BA List Change Interval = 10-15 min set MBCR=0 or 1, FDDMRR=0 or 1,
• No. Test Freqs. to Add at Each Interval = 5 TDDMRR = 0 or 1.
EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 14
2.2 Activation and Collection of MMR
A. Scheduling FAS recordings (III)

• In the FAS ICDM Settings window, under BCCH

Frequencies, select ”Frequency Set, All
Frequencies” and later select or create a frequency
• Once Cell Set has been selected it is
set that includes just the ARFCNs that are in use as
needed to configure the BCCH
BCCH in the network core and buffer areas (not the
frequencies to be scanned by accessing
“theoretical” BCCH frequency range, there are
the ICDM Settings window.
usually exceptions to the “official” rules)
• CNA analysis or EFO (xAFP) OLAPs can provide
such list of used ARFCNs on BCCH
EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 15
2.2 Activation and Collection of MMR
B. Scheduling NCS recordings

- If FAS license is not available then the MMR collection can be launched using NCS
recordings
- In dual band networks it is recommended to create 2 simultaneous NCS recording
tasks (typically duration of 2 weeks):
- One recoding task just for 850/900 Cells, to scan 850/900 BCCHs
- One recoding task just for 1900/850 Cells, to scan 1900/1800 BCCHs
- If having time for further collection, after finishing the previous, another NCS
recording can be launched for all cells together scanning all joint BCCHs from both
bands. Crossed band relations may be used in EFO (xAFP) to complete the
Interference Matrix (estimate co-bcch relations and other missing relations)
- Next slides describe the process to create a single NCS recording for 1900 Band
EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 16
 2.2 Activation and Collection of MMR
B. Scheduling NCS recordings (II)

• Select Cells or Cell Set that includes all cells in

Core and Buffer areas of EFO (xAFP) project. If
• Recommended GSM settings :
• Relative SS = -5 dB These will result in
selecting complete BSCs, new cells or will be
• Absolute SS = -95 dBm equivalent BAR thresholds - dynamically added to the recording.
12 and 2, closest to
• Multi Band Cell Offset= 7dB recommendation -12/3 • GSM Frequencies:
• BA List Change Interval = 10 min • Recommended to chose option 1st Order
• No. Test Freqs. to Add at Each Interval = 5 Neighbors + Free Selection
• Time settings, analogue to FAS • This enables the selection of Frequency set,
recommendation proceed analogously as recommended for
EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 17
FAS
2.2 Activation and Collection of MMR
C. mmL Commands per BSC
• In case Ericsson RNO is not available, BAR measurements may be scheduled per BSC.
• Launch Command Handling tool and connect to each BSC of the area where BAR is to
be collected and execute the MML commands:
1. RABII;
RABII (ii- for identity-initiate) is the command to initiate a
recording identity, will return and RID
• RID = (BARID0…BARID63)
2. RABDC:RID=BARID00,TMBCCHNO=613&
&636, CELL=ALL, RELSSN=12, RELSS2P
= 3, NUMFREQ=5, SEGTIME =10;
RABDC (c- for change) is used to change the default
settings of the initiated recording ID.
• CELL= ALL means all cells in BSC included in
the recording
• RELSSN =-12 (Relative SS Threshold C/I)
• RELSS2P = 3 (Relative SS Threshold C/A)
• SEGTIME = 10 min (BA List Change Interval)
• NUMFREQ = 5 (No. Test Freqs. to Add at Each
Interval)
• TNBCCHNO=613&&656 -> BCCHs with Other BA related commands:
ARFCN 613…636 -RABDP:RID=BARID00;displays information on the
measurement task
2. RABRI:RID=BARID00,DTIME=480; -RABIE:RID=BARID00; can be used to end the recording
RABRI (i- for initiate) is used to start the recording before the DTIME has finished
• DTIME (duration time) used to indicate the -RABRP:RID=BARID00; Print a BAR recording status
duration in minutes from the time it is entered -RABTI:RAD=BARID00; Print the BAR recording result (only if
on RID RID status is COMPLETE)
EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 18
2.2 Activation and Collection of MMR
COLLECTION OF BAR FIles
› Depending on Ericsson OSS configuration, BAR files (filename starting with BARFIL) may be
stored in a different folder. In former experiences files have been found in one of the following
folders:
– /var/opt/ehpt/eac/data/fs/[BSC Name] (R8)

– /var/opt/ericsson/nms_eam_eac/data/fs (R9/R10 with IOG20)

– /var/opt/ericsson/brf/data/db/tmpFileStore/[BSC Name] (R9/R10 & later with APG40)

– /ossrc/ericsson/brf/data/db/tmpFileStore/
– /var/opt/ericsson/sgw/SGw1.0.11.0/apg40files/sts/
– /var/opt/ericsson/ncs

– /var/opt/ericsson/fas

› In case BAR files cannot be found in any of this folder. Ensure to search all directories
(find/grep unix commands will help)
› It may also happen that BAR files are not transferred to the OSS but kept in BSCs or have a
short life time at the hard disk or there is no hard disk space. Sort out this problems with the
help of OSS administrators.
– For example: Files may be removed right after transfer to OSS, check the parameter “removeFile” with
command cap_pdb_get_para –n brf removeFile (this command displays the value, should be 0), use
cap_pdb_mu to set it to 0 if needed.cursor to removeFile p: i , 1-> type r then 0 :w! then :q
› When BARFILs are transferred from UNIX to Windows via FTP, the binary transfer method
should be used.

EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 19

2.3 Collection of PM DATA
QOS
› QoS data is gathered through Ericsson MRR binary files
(raw data)
› Two possible ways are suggested to enable MRR file
creation in Ericsson (in order of preference)
A. Scheduling MRR measurements recordings through RNO
(preferred)
B. Per BSC, using MML commands (just if RNO not available)

EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 20

2.3 Collection of PM DATA
A. QOS.SCHEDULING MRR THROUGH RNO (I)

› Create a New GSM MRR Recording

› All cells in core+buffer EFO (xAFP) area can be included

EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 21

2.3 Collection of PM DATA
A. QOS.SCHEDULING MRR THROUGH RNO (II)

• Give a name to the recording

• Time settings: Periods and repeat settings (up to 4 periods per day can be defined)
• Typically busiest period of the network during working days (in the example 18:00 to 21:00)
• Save Result Separately: If enabling several periods, one file per period will be created for this
• Select Cells or Cell Set that includes all cells in Core and Buffer areas of EFO (xAFP) project. If
selecting complete BSCs, new cells will be dynamically added to the recording.

EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 22

 2.3 Collection of PM DATA
B. QOS.SCHEDULING MRR THROUGH MML
• In case Ericsson RNO MRR feature is not available, BAR measurements may be
scheduled per BSC.
• Launch Command Handling tool and connect to each BSC of the area where MRR is to
be collected and execute the MML commands:

1. RAMII;
RAMII (ii- for identity-initiate) is the command to initiate a
recording identity, will return and RID
• MRRID = (MRRID0…MRRID9)
2. RAMDC:RID=MRRID00,CELL=ALL;
RAMDC (c- for change) is used to change the default
settings of the initiated recording ID.
• CELL= ALL means all cells in BSC included in
the recording
3. RAMRI:RID=MRRID00,DTIME=240,RES
ET;
RAMRI (i- for initiate) is used to start the recording
• DTIME (duration time) used to indicate the Other MRR related commands:
-RAMDP:RID=MRRID00;displays information on the
duration in minutes from the time it is entered measurement task
on RID -RAMIE:RID=MRRID00; can be used to end the recording
• RESET the recording data is reset when a before the DTIME has finished
recording is resumed. The counters then start -RAMRP:RID=MRRID00; Print a BAR recording status
from zero. If the parameter RESET is left out, -RAMTI:RAD=MRRID00; Print the BAR recording result (only
the counters start from the values they if RID status is COMPLETE). The command is used to initiate
processing and file output of measurement result recording data.
previously had.

EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 23

2.3 Collection of PM DATA
QoS. COLLECTION OF MRR Files
› Depending on Ericsson OSS configuration, MRR files (filename starting with MRRFIL) may be
stored in a different folder. In former experiences files have been found in one of the following
folders:
– /var/opt/ehpt/eac/data/fs/[BSC Name] (R8)

– /var/opt/ericsson/nms_eam_eac/data/fs (R9/R10 with IOG20)

– /var/opt/ericsson/sgw/SGw1.0.11.0/apg40files/sts/

– /var/opt/ericsson/brf/data/db/tmpFileStore/[BSC Name] (R9/R10 & later with APG40)

– /ossrc/ericsson/brf/data/db/tmpFileStore/

› In case MRR files cannot be found in any of this folder. Ensure to search all directories
(find/grep unix commands will help)
› It may also happen that MRR files are not transferred to the OSS but kept in BSCs or have a
short life time at the hard disk or there is no hard disk space. Sort out this problems with the
help of OSS administrators.
– For example: Files may be removed right after transfer to OSS, check the parameter “removeFile” with
command cap_pdb_get_para –n brf removeFile (this command displays the value, should be 0), use
cap_pdb_mu to set it to 0 if needed.

› When MRRFILs are transferred from UNIX to Windows via FTP, the binary transfer method
should be used.
› MRR can also be obtained in ASCII files, exporting directly the recordings from RNO
(.msmt & .conf files) – NOT RECOMMENDED

EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 24

2.3 Collection of PM DATA
VOICE TRAFFIC
› Voice carried traffic per cell in the project during the collection period is needed in any text
format which contains this info:
– Sector
– Voice erlangs= sum(TFTRALACC)/sum(TFNSCAN) +sum(THTRALACC)/sum(THNSCAN)
› If Subcell, also Voice Erlangs OL
=sum(TFTRALSUB)/sum(TFNSCAN)+sum(THTRALSUB)/sum(THNSCAN)
– HR % = 100*(sum(THTRALACC)/sum(THNSCAN))/(sum(TFTRALACC)/sum(TFNSCAN)
+sum(THTRALACC)/sum(THNSCAN))
› If Subcell, also % HR OL =
100*(sum(THTRALSUB)/sum(THNSCAN))/(sum(TFTRALSUB)/sum(TFNSCAN)+sum(THTRALSUB)/
sum(THNSCAN))
– Optionally # of TSL available for voice on BCCH TRX
– Optionally VAMOS traffic and VAMOS %HR can be considered (from as EFO 13.1)
› TFTRALACCV,TFTRALVSUB,TFNSCANV,THTRALACCV,THTRALVSUB,THNSCANV
› Aggregation: Average Erlang and HR % for the same days/hours as the QoS (MRR)
recordings (in a single or several files).
– I.e: If MRR collected to capture BH from 18 to 20 then traffic and HR% average of those hours

EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 25

2.3 Collection of PM DATA
Data Traffic
› Data traffic information per sector can be also used as a source of interference and if
wished also for Data traffic optimization purposes.
› Data Erlangs carried on the TCH layer produces interference and should be loaded in EFO.
This formula gives overall cell Data Erlangs:
› Average Cell DL Used PDCHs=Sum(DLBPDCH+DLGPDCH+DLEPDCH)/Sum(TRAFFDLGPRSSCAN)

› Data volume (Mbits) is optional and it is only used if freq. plan optimization uses data traffic
performance as driver.
› Data Volume DL (Mbits) = Sum(DLSTRVOL+DLINTBGVOL)/1000 or
sum(DLBGGDATA+DLTHP1GDATA+DLTHP2GDATA+DLTHP3GDATA+DLBGEGDATA+DLTHP1EGDATA+DLTHP2EGDATA+DLTHP3EGD
ATA+DLTHP1E2ADATA+DLTHP2E2ADATA+DLTHP3E2ADATA+DLBGE2ADATA)/1024

› Data Erlangs/volume need to be split between BCCH/TCH layers before importation by

means of EFO native importer (see 3.4). One approximated way to perform the split is to do
it based on allocated PDCH counters for CHGR0 (when CHGR0 just contains BCCH TRX)
› BCCH Data Erlangs (DL) = Average Cell DL Used PDCHs * Sum(ALLPDCHACC0)/Sum(ALLPDCHACC)
› TCH Data Erlangs (DL) = Average Cell DL Used PDCHs - BCCH Data Erlangs (DL)
› BCCH Data Volume DL(Mbits)= Data Volume DL (Mbits) * Sum(ALLPDCHACC0)/Sum(ALLPDCHACC)
› TCH Data Volume DL(Mbits)= Data Volume DL (Mbits) - BCCH Data Volume DL(Mbits)
› Aggregation: Average data Erlangs/Volume for the same days/hours as the QoS (MRR)
recordings.

EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 26

2.3 Collection of PM DATA
HANDOVER
› Daily sum of handover attempts (HOVERCNT) between each
pair of neighbors for a period of 2-4 weeks is required.
› Comma separated values (CSV) format
› Handover data can be imported in a single or several files using
the generic or native importers in EFO which just requires
columns for Source, Target, HO
› Aggregation method can be chosen in those imported (peak,
peak average, Sum, Average…)

EFO - Ericsson Interaction | Ericsson Internal | 2013-08-14 | Page 27