Best Effort Optimisation Process Doc v2.1

PROCESS DEFINITION 1 (47)
Version 2.1
Nokia Network Planning
Project Spinoza: Best Effort Optimisation Process 18/07/2005
Project Spinoza: Best Effort RF & In Call

Optimisation/Analysis Process
Version 2.1
Version 2.1
1. DOCUMENT HISTORY
Date Version Editor(s) Changes /Notes

27/05/2005 1.0 Robert Joyce First Draft
01/06/2005 1.1 Justin Clayden Addition of sections 4.5.1 & 4.5.2 & 5.2
Updates to multiple sections.
09/06/2005 1.2 Justin Clayden Update of embedded report formats.
09/06/2005 1.3 Justin Clayden Updates to most sections.
Pat Charoenpanichkit Created Actix Settings section.
James Wall Update of section 5.4
09/06/2005 1.5 Justin Clayden Updates to most sections.
02/07/2005 2.0 Justin Clayden Structure overview
02/07/2005 2.1 Justin Clayden Additions to multiple sections
Version 2.1
TABLE OF CONTENTS
1. DOCUMENT HISTORY ................................................................................................................. 2
2. INTRODUCTION............................................................................................................................ 4
3. OVERVIEW OF BEST EFFORT OPTIMISATION PRINCIPLES & METHODOLOGY .................. 4
4. PREFERENCES IN ACTIX ............................................................................................................ 5
4.1 Cellrefs File.............................................................................................................................. 5
4.2 WCMDA Neighbour List .......................................................................................................... 6
4.3 General Settings...................................................................................................................... 6
4.4 Threshold Settings................................................................................................................... 9
4.5 Storing Actix Settings to File.................................................................................................... 9
4.6 Actix Colour Settings ............................................................................................................... 9
4.7 UMTS Event Definition File ..................................................................................................... 9
5. DRIVE TEST SETUP ................................................................................................................... 10
RF OPTIMISATION – RF HOUSEKEEPING ....................................................................................... 11
5.1 Analysing the Drive for Sites Off-Air and Crossed Feeders .................................................. 11
5.2 Running the RF Coverage KPI Report .................................................................................. 14
6. RF OPTIMISATION – DETAILED RF OPTIMISATION ............................................................... 22
7. RF OPTIMISATION – 3G TO 3G NEIGHBOUR ANALYSIS........................................................ 27
8. RF OPTIMISATION – 3G TO 2G NEIGHBOUR ANALYSIS........................................................ 30
9. IN-CALL ANALYSIS – HOUSEKEEPING .................................................................................... 35
9.1 Analysing the Drive for Sites Carrying Traffic ........................................................................ 35
9.2 Running the Voice Cluster KPI Report .................................................................................. 37
9.3 Running the PS Cluster KPI Report ...................................................................................... 39
9.4 Looking for Obvious Patterns ................................................................................................ 40
10. IN-CALL ANALYSIS – DETAILED ANAYSIS ........................................................................ 42
10.1 Protocol Stack Browser...................................................................................................... 43
10.2 State Forms ....................................................................................................................... 44
11. REPORTING ......................................................................................................................... 45
11.1 Completion of RF Analysis Workbook ............................................................................... 45
11.2 Completion of In Call Analysis Workbook .......................................................................... 45
11.3 Completion of Presentation................................................................................................ 46
12. ISSUING CHANGE REQUESTS & FAULT INVESTIGATIONS............................................ 47
13. SUMMARY ............................................................................................................................ 47
Version 2.1
2. INTRODUCTION
This document describes the Best Effort optimisation process applied on Project Spinoza. The term
Best Effort in this document is used to describe the process of optimising clusters as much as
possible prior to complete cluster optimisation.
Since the methodology described in this document is following a best effort basis, the analysis
detailed in this document concentrates mainly on RF optimisation and analysis of voice & PS call
drives. Since the process will be constantly updated during the project the reader should ensure that
they have the latest version of this document and associated documents and templates.
3. OVERVIEW OF BEST EFFORT OPTIMISATION PRINCIPLES & METHODOLOGY
The Best Effort optimisation methodology to be employed by Nokia can be split into the following
sub-processes:
• RF Optimisation
o RF house keeping (cells on-air check, crossed feeder checks)
o Detailed RF optimisation (confirming correct coverage of individual cells)
o neighbour analysis (3G-3G)
o neighbour analysis (3G-2G)
• Voice & PS Call Performance Optimisation
o In-Call analysis - house keeping (all SC’s carrying traffic)
o Detailed In-Call analysis (pilot pollution analysis, SHO Area Analysis).
Ideally the first step should always precede the second step as there is little point performing
detailed in call drives if the RF environment is not sufficiently optimised to support the calls in the
first place or if cells are not radiating for any reason.
The first step of RF Optimisation is the analysis of the radio conditions against a set of RF targets
(Ec, Ec/Io etc.) In order to do this, extensive RF scanner measurements will be taken for the cluster.
These measurements will then be used to identify RF problem areas within each cluster such as bad
Ec, bad Ec/Io or missing neighbours. During this stage other basic house keeping checks will be
made to make sure that all the sites expected on-air are indeed on-air, that there are no crossed
feeders etc.
Once Best Effort RF Optimisation has been performed, best effort voice & PS call performance
optimisation can begin. Call performance optimisation involves carrying out a series of voice & PS
call tests within the cluster. Again, this step includes basic house keeping checks to confirm cells are
carrying traffic, etc. For each of the call tests performed the End-to-End Engineer analyses the call
performance KPI statistics and if necessary drills down to the individual L3 messages for further
analysis.
From the analysis the Engineer will determine the reason for the problem (further RF optimisation,
system problem, 3G/2G HO problem etc.) and recommend the appropriate changes to the network
through the Change Request process.
Version 2.1
4. PREFERENCES IN ACTIX
4.1 Cellrefs File
There are different CellRefs files for Optus and Vodafone. These files are updated daily and can be
found on the network drive at:
\Common_Data\Actix\CellRefFiles\
Is it critical that you use the correct operators CellRef file when doing any form of analysis.
Below are the details for loading the CellRef file.
Step 1: From the main menu, select Tools Æ Preferences
Step 2: In the Change Preferences dialog, on the File Location line, double-click on the name of the
current cellrefs file.
Step 3: In the Open dialog, navigate to the cellrefs file you would like to use and select Open. The
files must be copied from the Network Drive and place in the following directory for local access:
C:\Program_Files\Actix\Bin\Cellrefs\
Step 4: Click OK to close the Preferences dialog.
Step 5: A message box will be displayed saying that the new cellrefs file takes effect when Actix is
restarted. Click OK to close the message box. Restart Actix by clicking FileÆExit and then restart
Actix in the normal way.
Step 6: Click View Æ Display New Map
By default the cell sites are now visible (if this is not the case then right click, zoom Æ go to layer Æ
wcdma site-Site_Name)
It is suggested that you use the most up to date cellrefs file every time you do any analysis. It is
important to use the cellrefs file specific to the operator you are analyzing.
Version 2.1
4.2 WCMDA Neighbour List
Below are the details of the parameters for the WCDMA Neighbour List.
Tool Æ preferences Æ WCDMA Neighbour List
4.3 General Settings
Step 1: Time Offsets
Tools Æ Preferences Æ Time Offsets

Version 2.1
Step 2: Binning Mode
Tools Æ Preferences Æ Binning Mode
Select the Binning mode here
Determine the value for each of the

binning mode here
For the physical layer (RF) analysis, it is suggested to use ‘Location’ Binning with the value of
X=0.000001 and Y=0.000001
For In-Call analysis, it is suggested to use ‘Message’ Binning Mode with the value of Message = 1.
Step 3: Decode Settings
Tools Æ Preferences Æ Decode Settings
NOTE: Scanner Ec/Io Threshold should be set to -20dB. Otherwise Actix ignores all values below -
15dB.
Version 2.1
Step 4: GSM Bands Used
Tools Æ Preferences Æ GSM Bands Used
Step 5: WCDMA
Tool Æ Preferences Æ WCDMA

Version 2.1
4.4 Threshold Settings
Step 1: From the main menu, select Tools Æ Display Thresholds
Step 2: Below are the threshold settings used for Actix Event Definitions
Actix Event
Definitions.pdf
4.5 Storing Actix Settings to File
All of the above settings (Sections 4.2 to 4.4) are stored in the actix settings file called
AppSettings.dat that is stored in the following directory:
C:\Program_Files\Actix\Bin\
A back-up version can be found on the network drive at:
\Common_Data\Actix\Actix_Settings\
4.6 Actix Colour Settings
Colour settings for Actix are stored in the xml files stored in the following directory:
C:\Program_Files\Actix\Bin\FormatGroups\UserSettings\
Back-up versions can be found on the network drive at:
\Common_Data\Actix\ColourScheme\
4.7 UMTS Event Definition File
The Actix UMTS Event Definition File need to put in the following location
C:\ProgramFiles\Actix\Analyzer\Bin\Events\
A back-up version can be found on the network drive at:
\Common_Data\Actix\Actix_Patches\
Version 2.1
5. DRIVE TEST SETUP
For further details on the setup of the Nemo drive test equipment please see the Nemo Setup
document which can be found on the network drive at:
\Common_Data\ Procedures_&_Guidelines\Nemo\
For CAL optimisation the following drive test setup will be used:
Voda - 3G only voice call - 90sec Active / 15sec Idle (NOKIA UE)
(File name: YYMMDD_S01_VF_XXX_LONG3G)
Voda - 2G ISHO enabled voice call - 90sec Active / 45sec Idle (SAMSUNG UE)
(File name: YYMMDD_S01_VF_XXX_LONG2G)
Optus - 3G only voice call - 90sec Active / 15sec Idle (NOKIA UE)
(File name: YYMMDD_S01_OP_XXX_LONG3G)
Optus - 2G ISHO enabled voice call - 90sec Active / 45sec Idle (SAMSUNG UE)
(File name: YYMMDD_S01_OP_XXX_LONG2G)
PS384 - 2G handover enabled (NOKIA UE) - Operator will change from drive to drive
PS call will download a 2MB file, disconnect, upload 500kB file, disconnect, then repeat).
(File name: YYMMDD_S01_VF_XXX_PS384 (for Vodafone))
(File name: YYMMDD_S01_OP_XXX_PS384 (for Optus))
2G Scanner - all GSM900 band.

(File name: YYMMDD_S01_XXX_SCAN2G)
3G Scanner - both Voda and Optus channels - Top15 SC's on each channel.
(File name: YYMMDD_S01_XXX_SCAN3G)
This 3G scanner files is then split into separate files for each operator using the “Scanner
Conversion” tool (available on the network drive:
\\Common_Files\Tools\
(File name: YYMMDD_S01_VF_XXX_SCAN3G (for Vodafone))

(File name: YYMMDD_S01_OP_XXX_SCAN3G (for Optus))
For file naming convention the following is assumed:
YY - year
MM - month
DD - day
XXX - team name eg TIN - Tin Team

COP - Copper Team
BRO - Bronze Team
IRO - Iron Team
S01 - cluster eg S01 - Sydney 01

C01 - Canberra cluster 01
Version 2.1
RF OPTIMISATION – RF HOUSEKEEPING
5.1 Analysing the Drive for Sites Off-Air and Crossed Feeders
NOTES:
1. The Binning method in Actix should be set to “Location”. See section 4.3.
2. Ensure you always plot layers like streets, RNC borders and cluster borders.
3. Cells should be displayed and JSid’s also shown.
This section must be completed for each operator.
Step 1: Open Actix and load all Scanner log files that you need to analyse (make sure that you
know exactly which files are associated with the cluster you need to analyse and for which date).
(File>Open Log File)
Version 2.1
Step 2: Create a superstream of all scanner log files (if you’re going to analyse multiple scanner
drives). Tools->Create Superstream
Step 3: Plot the best server SC on a map and perform a visual inspection that each and every cell
that should be on air- is on air. With the cell layer turned on and with the colour of the cells set to
match the SC you can also easily see and sites with swapped feeders.
Version 2.1
Step 4: Display the detected SCs on an Excel worksheet.
Step 5: Sort by Scrambling Code and use Autofilter to run a quick check of sites SCs detected
during the drives.
Version 2.1
5.2 Running the RF Coverage KPI Report
NOTES:
Step 1: Open the RF KPI Report (Tools->Open Workbook)
Step 2: Make sure that you select the Superstream you have just created as the source data for the
KPI Report.
Version 2.1
Step 3: You will then be presented with a completed Spreadsheet. The statistics page will look like
the picture below.
NOTE: The “Scanner File” name shown in the box will be just one of the scanner files used to create
the superstream.
Step 4: These RF statistics need to be loaded into the drive data sheet in the RF Database as
shown below.
Step 4.1: After you open Database, select Drive Test Stat page as shown.
Version 2.1
Step 4.2: Select Operator Name and City. Then click on “Add New DT” button.
Step 4.3: First, select the Cluster Number. Then you will get site list on the right hand and select
only the On-Air sites on this drive test. After that click update button.
2. Cluster Site
3. Update Site
Version 2.1
Step 4.4: All shown below will be update on the highlighted area but you have to fill in the number of
Alarm sites manually.
Step 4.5: Fill in all the necessary information with Fault Investigation. Fault investigation is the
problem that you found on this drive test. You can fill in later after finish analyzing by using the Edit
Button.
1. Fill in additional
2. Add Fault investigation in the

Version 2.1
Step 4.6: From Actix Worksheet, you go to the bottom of Statistic Page. It has the summary of Drive
Test result that you can copy and paste to the KPI (You have to select only the data, don’t select
whole column in row). In this example, I’ll show you the AMR KPI result.
Step 4.7: Paste in the KPI Statistic Box. Repeat it 1 by 1 until complete all RF, AMR, PS and VDO
calls.
Select whole column and paste the
NOTE: The program will automatically fill the missing information in the above picture.
Version 2.1
Step 4.8: Then click “Add Button” on the upper right hand.
NOTE: For more information, please find out in the Optimize Database Manual.
Version 2.1
Step 5: The remaining sheets in the RF Coverage KPI Report contain statistics and graphs.
Step 6: From the RF Coverage KPI Report several pages need to be cut and paste into the Best
Effort RF Analysis spreadsheet.
Version 2.1
OUTCOMES FROM THIS SECTION:
If swapped feeders are detected:

- This issue needs to be raised immediately as a Fault Investigation in the RF Database. Once it
has been logged, then a “Optimisation Notification for Fault_TT” form must be filled in and
emailed as soon as possible to the following people:
Steve.Joyce@nokia.com for Vodafone Lead Sites

nokiaric@vodafone.com for Vodafone Lead Sites
ext-steve.langton@nokia.com for Optus Lead Sites.

nokiaric@vodafone.com for Optus Lead Sites.
If antenna tilts or pans are needed:

- You should begin to compile a list of physical antenna changes (tilt changes, azimuth changes)
they you believe are necessary to improve RF coverage in the area. Further additions to these
physical changes may be necessary after the In Call analysis is completed. These physical
changes will eventually be raised in a Change Request through the RF Database tool.
- All these changes need to be carefully considered and each and every change must go through
the following steps:
They must be simulated in NetAct planner.
They must be approved by the RF Engineer who planned the site.
If the planning engineer is not available then the TSS and site photos should be
used.
If the antenna is DualBand then 2G must confirm the change also.
NetAct must be updated with the new configuration.
Add RF Statistics to the RF Database:

- As described in detail previously, the statistics need to the added to the RF Database for both
operators.
“RF Healthcheck complete” the RF Database:

- In the RF Database, the “RF Healthcheck complete” button much be tick for both operators..
Start compiling the Best Effort RF Analysis template (one for each operator):
- Now that the RF Coverage KPI Analysis macro has been run, the first 3 sheets of the Best Effort
RF Analysis Template can be completed. These sheets are “Scanner Files Loaded”, “RF KPI
Summary”, “EcNo vs RSCP”.

Version 2.1
6. RF OPTIMISATION – DETAILED RF OPTIMISATION
NOTES:
This section to be completed for the operator with most radiating sites in the cluster.
Step 1: Poor Coverage Analysis: Display the best server Ec (RSCP) coverage for the superstream
on a map and locate the areas of poor coverage. These will be analysed in more depth later. (This
RSCP plot is also an input into the final powerpoint presentation so now is a good time to complete
this task.)
Version 2.1
Step 2: Poor Quality Analysis: Display the best server Ec/Io for the superstream on a map and
locate the areas of poor Ec/Io. Remember that areas of poor Ec/Io can be due to poor coverage as
well as pilot pollution. Therefore there’s nothing you can do about the areas of bad Ec/Io where the
coverage is also bad. You can only improve the Ec/Io if there’s sufficient Ec. This will be analysed in
further in the next step.
(This Ec/Io plot is also an input into the final powerpoint presentation so now is a good time to
complete this task.)
Version 2.1
Step 3: Pilot Pollution Analysis: Using Actix, display the pilot pollution for the superstream on a map.
This gives an easier visualisation of problem areas in the network.
In Actix, the Pilot Pollution event occurs when four or more pilots are above a user defined level (in
our case -15dB). It is important to note that it does not consider the RSCP values of these pilots (as
can be seen in the screenshot). It is important to always consider three factors- RSCP levels, Ec/Io
levels and the number of pilots (i.e.- pilot pollution) in a given area.
Step 4: Now that the problem areas have been identified, then detailed analysis can begin. In actix
look at the individual RSCP and Ec/Io of cells to determine their service areas.
Version 2.1
To improve the RSCP and Ec/Io situation in these areas you should use Actix to identify the best
servers and worst interferers in the area and possibly suggest new azimuths or down tilts for these
sites to improve dominance of the best servers or reduce interference from the worst interferers.
It is also important to consider the other possible reasons for these problem areas, such as:
1. Missing Site. If there is a missing site in the plan, then nothing should be done into
improve coverage/dominance until the missing site is on air.
2. Coverage Degradation Request. There may be a Coverage Degradation Request
active in this area. To confirm, display the MapInfo layer that contains all active CDR’s
and discuss with the RF Planner of this area.
3. Cell /Site not radiating. Low RSCP could be due to a cell or site not radiating at the time
of the drive. This should have been confirmed in the RF Housekeeping stage.
Step 5: Details of RF problems should be added to the Best Effort RF Analysis template. Example
below.
Version 2.1
If antenna tilts or pans are needed:

- Continue to compile a list of physical antenna changes (tilt changes, azimuth changes) they you
believe are necessary to improve RF coverage in the area. Further additions to these physical
changes may be necessary after the In Call analysis is completed. These physical changes will
eventually be raised in a Change Request through the RF Database tool.
- All these changes need to be carefully considered and each and every change must go through
the following steps:
They must be simulated in NetAct planner.
They must be approved by the RF Engineer who planned the site.
If the antenna is DualBand then 2G must confirm the change also.
NetAct must be updated with the new configuration.
Start compiling the final powerpoint presentation:

- The RSCP and Ec/Io plots for each operator can be pasted into the final power point
presentation.
Complete the Problem Areas documentation:

- The “Problem Area” sections of the Best Effort RF Analysis template should be completed.
This section to be completed for the operator with most radiating sites in the cluster.
Version 2.1
7. RF OPTIMISATION – 3G TO 3G NEIGHBOUR ANALYSIS
This section is to be completed for each operator separately. 3G to 3G neighbour cell list will
be separate for each operator.
Step 1: Select from the menu Analysis -> UMTS Accelerated Network Rollout (This should give you
something similar to the screen below. Make sure that the Superstream is selected in the file
selection box.
Step 2: Now double click on the Neighbour List Recommendation icon and after a short time
(depends on the size of your superstream) you should be presented with a screen similar to that
below. Click “Show Excel Report” button on the lower right corner.
Version 2.1
Step 3: Open the latest version of the Spinoza 3G3G Neighbour List Creator macro. Enable Macros.
Step 4: Go back to the Actix sheet and click on the grey square between the A and the 1 grey
squares to select the whole Actix Sheet.
Step 5: Copy this sheet to the 3G Neighbour List Creator work book. (Click on the blue square and
select paste).
Step 6: Go back to the Summary Sheet, update the date, Engineer and Cluster details and click on
the Create Neighbour List button. After a short time you should be presented with a summarised
missing neighbour sheet similar to the one below. Do not forget to save your new sheet with a
different name to retain the blank 3G Neighbour List Creator sheet for next time.
Version 2.1
Step 7: You will then have a list of suggested neighbour additions. (NOTE: The Excel macro ignores
any missing neighbours with less than 10 samples.)
NOTE: If there are any sites with swapped feeders that all “missing” ncells for these sites should be
ignored in this process.
These potential missing neighbours should be checked for validity using the mapinfo neighbours tool
that can be found on the common drive:
\Common_Data\MapInfo\UMTS_Tool\
All valid neighbours can then be created into a Change Request using the RF Database. All that is
required to produce a CR is the source and target cellid’s.
There are limitations to the number of 3G to 3G neighbour relations that can be defined per cell. At
present this is limited to 28 relations. If the CR that is created has ADJS_id’s that are greater than
28, then you must reconsider this relationship and all other relationships defined in that cell. It may
be necessary to delete a relationship to make space.
Change Request generation:

- Once a list of valid new 3G – 3G neighbour relationships is created this must be implemented
into the RF database by creating the relationships (both directions) and for both operators
separately.
- A copy of the final CR’s are the be included in the “CR -3g-3g Neighbours” sheet of the Best
Effort RF Analysis spreadsheet.
This section is to be completed for each operator separately. 3G to 3G neighbour cell list will
be separate for each operator.
Version 2.1
8. RF OPTIMISATION – 3G TO 2G NEIGHBOUR ANALYSIS
This section to be completed for both operators separately.
Actix is not able to do the 3G/2G neighbour analysis. The process for finding missing 3G to 2G
ncells is detailed below.
All programs and macros mentioned in this section can be found on the network drive at:
\Common_Data\Procedures_&_Guidelines\3G_to_2G_ncell_process\
A DOS based program has been written to process the scan files. An excel worksheet with
associated macros (which processes the output of the above program) is then used to present the
scanned 3G/2G ncells in terms of SC/BCCH-BSIC. A second excel worksheet with associated
macros is then used to present scanned and undefined SC/BCCH-BSIC combinations.
The RF engineer must decide which scanned SC/BCCH-BSIC combinations should be added as
neighbours. The Cell id of 3G and 2G cells to be added is noted.
The new 3G to 2G relationships are added to the RF Database in order to generate a Change
Request.
Step 1: To process the log files copy all 3G and 2G scanner files, from one and only one drive test
team, taken on the same day, into the same directory. 3G and 2G scanner files will most often have
a .fs3 and .fs2 extension respectively.
NOTE: Concatenating the files may not end up saving time. If after concatenating the 2G and 3G
scan files, the output file, to be created in step 6, may contain over 65536 lines (the maximum
allowed in excel). If this is the case the output file will have to be broken into separate files of length
less than 65536 lines.
It is best to check whether the file is for 3G or 2G by opening the scanner files in notepad. Following
is an excerpt from a 2G scanner file. This information is found near the top of the file. Note that the
current version is 1.73 or 1.74. The remaining messages clearly indicate that this is a scan of the 2G
GSM system.
*** NEMO PRIME 4.13.23 ff ver 1.73 11.5.2005 10:25:31

#NT Network type : GSM 900/GSM 1800
#ST Scanner type : DTI LX GSM 900/1800
Similarly here is an excerpt from a 3G scanner file.
*** NEMO PRIME 4.13.23 ff ver 1.73 11.5.2005 10:25:31

#NT Network type : UMTS 2100 FDD
#ST Scanner type : DTI LX UMTS 2100
Make certain that all 3G scanner files have the same extension, this does not have to be .fs3, but it
must be consistent. Also, remove all spaces from the file names.
Step 2: Copy the executable DOS code, get3g2g_spin_1.5.exe to the directory created in step1.
Step 3: Open a DOS window (Start->Run->”cmd”)

Version 2.1
Step 4: Change to the directory that the scanner files are located in and combine the files:
Combine all 2G files into a single input file using the following command; Copy *.fs2 input2G.fs2
Combine all 3G files into a single input file using the following command; Copy *.fs3 input3G.fs3
NOTE: All scan files are from the same day and all 2G drives have *.fs2 and all 3G scan files have
*.fs3 extension. If data from different drive test teams taken on the same day is copied into the same
file, the output file will contain erroneous information.
Step 5: Run the executable file get3g2g on the combined 3G and 2G scanner files. Below is an
example of a successful run of the executable file. It may be helpful to indicate the date on input and
output files as you may be analysing drives from a number of days.
Version 2.1
Step 6: Open the 3G2G Neighbour List Creator Excel workbook that is available on the network
drive.
NOTE: Opening this workbook using XL from Microsoft office 2000 has resulted in the macro not
working correctly in a number of cases. Use XL 2002 or later.
Step 7: Using XL, open the 3G2G output file (created previously) as tab and space delimited.
NOTE: If the file has more than 65536 lines then the output file will have to be broken into separate
files of length less than 65536 lines. This can be done using the “Split File” tool that can be found on
the network drive.
Step 8: Select the entire sheet from step 8 (by clicking in top left grey box) and paste this sheet on
the “3g2g Output File” worksheet of the Spinoza 3G2G Neighbour List Creator workbook.
Step 9: Fill your details in the front sheet of the Spinoza 3G2G Neighbour List Creator workbook.
Now click the “Get 3G/2G Neighbour List” button. Separate lists will be created for Optus (ARFCN
43-83) and Vodafone (ARFCN 85-124). The list contains only 4 columns, SC (3G primary
scrambling code), ARFCN (GSM900), BSIC, and Count. Below is an example of the list for
Vodafone.
SC ARFCN(GSM900) BSIC Count

52 111 5 67
52 115 17 58
52 107 59 32
52 91 37 15
52 87 57 10
127 109 9 126
127 115 16 74
127 99 7 56
130 107 18 116
130 105 51 7
130 111 5 7
131 87 9 561
131 111 5 208
131 95 29 140
Step 10: Create a Scan Data file by pasting successive outputs (like that above) one after the other.
An example is shown below with many lines cut out.
Version 2.1
Step 11: Open the most recent A_WCEL and A_ADJG files for Optus or Vodafone (you will need to
repeat the following step for each operator to produce separate lists).
Step 12: Open the Spinoza 3G2G Undefined Ncells worksheet. Enable macros and use Excel 2002
or later. Follow the instructions.
An example segment of the output of this macro is shown below. We now have a list of scanned and
undefined SC/BCCH-BSIC combinations.
SC ARFCN (GSM900) BSIC COUNT defined or scanned Evaluate Undefined Ncell

146 81 2 1563 scanned Undefined ncell
Version 2.1
These potential missing neighbours should be checked for validity using the mapinfo neighbours tool
that can be found on the common drive:
\Common_Data\MapInfo\UMTS_Tool\
Using the SC and the BCCH-BSIC combinations, the local topography, cell height/azimuth, scan
data count and local knowledge the RF engineer will decide which 3G to 2G neighbour relationships
should be added. While investigating neighbour relationships from the maps, note the 3G and 2G
cellid’s.
All valid neighbours can then be created into a Change Request using the RF Database. All that is
required to produce a CR is the source and target cellid’s.
There are limitations to the number of 3G to 2G neighbour relations that can be defined per cell. At
present this is limited to 13 relationships for both Vodafone and Optus. If the CR that is created has
ADJG_id’s that are greater than 13, then you must reconsider this relationship and all other
relationships defined in that cell. It may be necessary to delete a relationship to make space.
NOTE: 2G to 3G neighbouring cell relationships will be audited by a separate process.
Change Request generation:

- Once a list of valid new 3G - 2G neighbour relationships is created this must be implemented
into the RF database by creating the relationships.
- A copy of the final 3G -2G CR’s for each operator must then be included in the “CR -3g-2g
Neighbours” sheet of the Best Effort RF Analysis spreadsheet.
- A copy of the final 2G - 3G CR’s for each operator must then be included in the “CR - 2g-3g
Neighbours” sheet of the Best Effort RF Analysis spreadsheet.
Version 2.1
9. IN-CALL ANALYSIS – HOUSEKEEPING
9.1 Analysing the Drive for Sites Carrying Traffic
NOTES:
7. The Binning method in Actix should be set to “Message”. See section 4.3.
This section must be completed for each operator separately by each end-to-end engineer.
This task is an extension of the RF Housekeeping section where the scanner data was checked to
confirm that the cells were radiating and point in the correct direction. Now we are checking the UE
data to confirm that each and every cell in the area driven is able to carry a call (i.e.- it is in the
Active Set at some time).
NOTE: In this step we are not checking if a call is setup on each cell- we are just confirming that the
cell is in the Active Set at some time.
Step 1: Open Actix and load all Voice log files that you need to analyse.
Version 2.1
Step 2: Create a superstream of all the log files.
Step 3: Plot the Active Set SC on a map and perform a visual inspection that each and every cell
that should be on air- is on air and is the strongest SC in the Active Set in the areas expected.
Ensure you have the cell layer turned on and with the colour of the cells set to match the SC.
Version 2.1
9.2 Running the Voice Cluster KPI Report
Step 1: Load the mobile drive test log files to be analysed.
Step 2: Create a superstream of all the mobile drive test log files.
Version 2.1
Step 3: Run the latest Voice/Video or PS KPI Report on the Superstream of the mobile drive test log
Step 4: Make sure that the supersteam that has been created is used as the input for the KPI report.
Version 2.1
Step 5: You should then be presented with something similar to the following (this is a Voice KPI
Report- PS or Video report are slightly different).
This spreadsheet is the basis of the Best Effort In-Call Analysis template. This should be cut and
past into the template now.
9.3 Running the PS Cluster KPI Report
For the PS384 calls a different report must be run. Follow the same steps as above on the PS384
log files and run the “Spinoza General FTP DL KPI Report” spreadsheet instead. The output will be
similar to what is shown below.
Version 2.1
9.4 Looking for Obvious Patterns
The next stage of in call analysis is to try to see if there are any obvious reasons for the call
performance. This can be easily done by displaying the setup fails/call drops on a map and on a
workbook to see if they’re mainly located in one area.
This will highlight if the issues are related to just one cell or site. It can also show you if the problems
are consistently around RNC borders for example.
Version 2.1
From the map and this workbook it is possible to quickly see if one of two sites are consistently
failing due to setup calls or dropping calls. If a situation like this is found then this must be
progressed to the detailed In-Call analysis and the reason for the failures/drops pinpointed. This
issue needs to the raised immediately through a Fault Investigation in the RF Database. Details
should also be included in the Detailed In-Call Analysis template as well as the summary section of
the final powerpoint presentation. It is important to identify the number of failures/drops that are
related to this particular issue.
From this sheet is it also possible to see if the failures are due to low coverage or bad Ec/Io. Areas
of bad coverage and bad Ec/Io should have already been detected from the scanner drives. It may
be that the site in a particular area is not yet built, in which case there is little that can be done to
improve coverage in such areas.
“Cells Carrying Traffic” the RF Database:

- In the RF Database, the “Cells carrying Traffic” button much be tick for both operators to confirm
that each and every cell has been detected in the Active Set during the drive.
If a serious site issue is detected:

- Any serious site issue needs to be raised immediately as a Fault Investigation in the RF
Database. Once it has been logged, then it must be followed up with the RIC.
Start compiling the Best Effort In-Call Analysis template (one for each operator):
- Now that the Voice Cluster KPI Report macro has been run, most of the output sheets need to
be included in the Best Effort In-Call Analysis template. The detailed call analysis will be
completed in the following section.
Version 2.1
10. IN-CALL ANALYSIS – DETAILED ANAYSIS
This section much be completed for each operator separately by each end-to-end engineer.
Detailed In-Call analysis must now be performed to investigate the reasons for all failed call setups
and dropped calls. The output of the Voice Cluster KPI Report macro will now have been put into the
Best Effort In-Call Analysis template. This will contain in depth details of each and every dropped
call / failed setup. Many obvious reasons for the failures/drops can be pinpointed immediately. For
example if there is poor RSCP levels for all SC’s seen at a particular point, then it is a simple case of
lack of coverage. Once it is confirmed that this is due to a missing site, then no further analysis is
needed.
The latest version of this macro gives possible reasons for a dropped call or call setup failure. These
are:
Due to Bad Coverage

Due to Missing Neighbour
Due to Network Problem
These are indicators only. They should be used as a starting point for anaylsis. After detailed
analysis is completed the “Setup/Drop Failure Reason” column can be filled in with one of the
following reasons:
Bad Coverage
Pilot Pollution
SHO Failure
Missing Neighbour
RRC Failure
DL RRC Connection Release
INVALID Call Setup Failure
Other
Version 2.1
Failures/drops due to bad Ec/Io but with good RSCP generally indicate that the UE has not selected
the best SC and is usually a sign of missing neighbours. Investigate the best serving SC before and
after the drop and if they are different investigate if a neighbour relationship exists between these
cells.
Once all obvious reasons for failures have been investigated, more detailed analysis must be
performed. The features in actix that can be used in this section are the Protocol Stack Browser and
State Forms.
10.1 Protocol Stack Browser
The Actix Protocol Stack Browser should be used to look at the Layer 3 messages for a closer look
at the reason for call failures and drops. Occasionally, Actix may misrepresent some of the data as
failures and therefore we should check all failures to make sure they are real failures and if not
amend the In-Call KPI report accordingly.
L3 Message flows for CS and PS calls are given in the embedded documents below.
AMR MOC Call Flow PS MOC Call Flow
AMR MOC Call PS MOC Call

Flow.pdf Flow.pdf
You can access the Protocol Stack Browser through the View / Protocol Stack menu. Ensure that
you choose the current Superstream.
NOTE: This picture also shows an Active & Monitored Set State Form which is discussed in the next
section.
Version 2.1
10.2 State Forms
State Forms are user defined windows that can show any combination of data that is superstream.
Actix has several predefined State Forms that have cover the major functions.
NOTE: To get the most out the State Forms functionality it is best to superstream the in-call and
scanner files together to allow viewing of both data at the same time. This is ideal for detecting
missing neighbour relations etc.
You can access State Forms through the View / Forms menu. Ensure that you choose the current
Superstream.
The picture below shows an example of the UMTS Scanner CPICH Chart and the UMTS Active +
Monitored Set state forms.
The picture below shows the UMTS Missing Neighbours state form that pulls data from both the
scanner and the UE.
Version 2.1
Completion of the Best Effort In-Call Analysis template (one for each operator):
- Now that the Voice Cluster KPI Report macro has been run, and detailed analysis completed,
then the Best Effort In-Call Analysis template can be finalised.
11. REPORTING
11.1 Completion of RF Analysis Workbook
For the RF Analysis the engineer should complete a Best Effort RF Analysis workbook for each
operator. This report includes all the problems seen during the RF analysis (sites off air, crossed
feeders etc.) as well as a list of any physical changes and missing neighbours to be added (for both
operators).
The template is stored on the network drive in the following directory:
\Common_Data\Procedures_&_Guidelines\
A copy of completed workbook should be saved in the following directory:
\Cluster_Data\Cluster_XX\Analysis\
NOTE: These spreadsheets are then embedded in the final powerpoint presentation (see the
section below).
11.2 Completion of In Call Analysis Workbook
For the In Call Analysis each end-to-end engineer should complete a Best Effort In Call Analysis
workbook for their operator. This report will record all the problems seen during the In Call analysis.
NOTE: These spreadsheets are then embedded in the final powerpoint presentation (see the
section below).
Version 2.1
11.3 Completion of Presentation
After the completion of the Best Effort RF Analysis and Best Effort In-Call Analysis workbooks, then
these two technical reports must be embedded into the Best Effort Optimisation Report (powerpoint
presentation). This is passed on to management for review.
File naming convention is as follows:
Best_Effort_XXX_OO_WWWDrive_YYMMDD.ppt
Where: XXX - cluster eg S01 - Sydney 01

C01 - Canberra cluster 01
OO - operator eg VF - Vodafone
OP - Optus
WWW – drive no. eg 1st – First Drive

2nd – Second Drive
YY - year
MM - month
DD - day
NOTE: Two separate reports need to be produced- 1 Optus and 1 Vodafone. The RF portion is the
same- but the In Call analysis must be operator specific.
This report is to be sent to the following people for review (in Sydney):
- benjamin.goh@nokia.com
- Catalina.Fontan@nokia.com
- Arnaud.Pieters@nokia.com
This report is to be sent to the following people for review (in Mebourne):
- rittavee.chantarakul@nokia.com
Version 2.1
12. ISSUING CHANGE REQUESTS & FAULT INVESTIGATIONS
The following Fault Investigations need to be raised immediately once they are found during
analysis:
• Swapped Feeders
• Site Issues resulting is serious dropped calls or call setup failure on a cell or site.
The following Change Requests are to be raised upon completion of the final report:
• Physical antenna changes – Vodafone (tilts and pans)
• Physical antenna changes – Optus (tilts and pans)
• 3G – 3G neighbouring cells additions / deletions – Optus
• 3G – 3G neighbouring cells additions / deletions – Vodafone
• 3G – 2G neighbouring cells additions / deletions – Optus (BSC and RNC data)
• 3G – 2G neighbouring cells additions / deletions – Vodafone RNC data.
• 3G – 2G neighbouring cells additions / deletions – Vodafone BSC data.
These Fault Investigations and Change Request must always be raised through the RF Database
system to allow for easy tracking of implementation. The parameter CR’s are sent daily to the
appropriate RIC by a single point of contact within the RF group.
The antenna changes for Optus lead sites are send to the following people.
NSW VIC
jbruggen@alandick.com.au jbruggen@alandick.com.au
tyoungnickel@alandick.com.au tyoungnickel@alandick.com.au
ext-steve.langton@nokia.com ext-steve.langton@nokia.com
13. SUMMARY
This document has summarised the Spinoza Best Effort RF and In-Call optimisation/analysis
process. Since the process will be constantly updated during the project the reader should ensure
that they have the latest version of this document and the latest version of the imbedded
spreadsheets.

Best Effort Optimisation Process Doc v2.1

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Best Effort Optimisation Process Doc v2.1

Transféré par

Droits d'auteur :

Formats disponibles

PROCESS DEFINITION 1 (47)

Project Spinoza: Best Effort RF & In Call

Date Version Editor(s) Changes /Notes

3. OVERVIEW OF BEST EFFORT OPTIMISATION PRINCIPLES & METHODOLOGY

o RF house keeping (cells on-air check, crossed feeder checks)

o Detailed RF optimisation (confirming correct coverage of individual cells)

o neighbour analysis (3G-3G)

o neighbour analysis (3G-2G)

• Voice & PS Call Performance Optimisation

o In-Call analysis - house keeping (all SC’s carrying traffic)

o Detailed In-Call analysis (pilot pollution analysis, SHO Area Analysis).

4.1 Cellrefs File

Step 1: From the main menu, select Tools Æ Preferences

Step 4: Click OK to close the Preferences dialog.

Step 6: Click View Æ Display New Map

4.2 WCMDA Neighbour List

Tool Æ preferences Æ WCDMA Neighbour List

4.3 General Settings

Step 1: Time Offsets

Tools Æ Preferences Æ Time Offsets

Step 2: Binning Mode

Tools Æ Preferences Æ Binning Mode

Select the Binning mode here

Determine the value for each of the

X=0.000001 and Y=0.000001

Step 3: Decode Settings

Tools Æ Preferences Æ Decode Settings

Step 4: GSM Bands Used

Tools Æ Preferences Æ GSM Bands Used

Tool Æ Preferences Æ WCDMA

4.4 Threshold Settings

Step 1: From the main menu, select Tools Æ Display Thresholds

4.5 Storing Actix Settings to File

A back-up version can be found on the network drive at:

4.6 Actix Colour Settings

Back-up versions can be found on the network drive at:

4.7 UMTS Event Definition File

A back-up version can be found on the network drive at:

5. DRIVE TEST SETUP

2G Scanner - all GSM900 band.

(File name: YYMMDD_S01_VF_XXX_SCAN3G (for Vodafone))

For file naming convention the following is assumed:

XXX - team name eg TIN - Tin Team

S01 - cluster eg S01 - Sydney 01

This section must be completed for each operator.

Step 4: Display the detected SCs on an Excel worksheet.

5.2 Running the RF Coverage KPI Report

This section must be completed for each operator.

Step 1: Open the RF KPI Report (Tools->Open Workbook)

2. Add Fault investigation in the

Select whole column and paste the

OUTCOMES FROM THIS SECTION:

If swapped feeders are detected:

Steve.Joyce@nokia.com for Vodafone Lead Sites

ext-steve.langton@nokia.com for Optus Lead Sites.

If antenna tilts or pans are needed:

Add RF Statistics to the RF Database:

“RF Healthcheck complete” the RF Database:

This section must be completed for each operator.

6. RF OPTIMISATION – DETAILED RF OPTIMISATION

OUTCOMES FROM THIS SECTION:

If antenna tilts or pans are needed:

Start compiling the final powerpoint presentation:

Complete the Problem Areas documentation:

Due to Bad Coverage