FREQUENCY PLANNING PROCEDURE

Revision 2 - March 2001

1 INTRODUCTION
1.1

Objective
This procedure is intended to provide the frequency planner with a set of guidelines and checklists
when doing a frequency plan. It encompasses the planning process using the following frequency
planning tools:
Asset
Optimisation Tool Box (O:\PlanOpt\Apps\FPlanWizard\OTB.exe)
CellOpt 2.1 or CellOpt 2.2
Planning Toolbar (O:\PlanOpt\Apps\PlanningToolbar\PlanningToolbar.exe) for

Asset Import (Frequency Planning Tab)

Asset Utilities (Frequency Planning Tab)

Accept BCCH carriers(Planning and Configuration Tab)

NetCfg 3.0

1.2

Scope
This document describes the procedure for preparing and implementing a frequency plan, which
entails the generation of an interference matrix, the generation of a carriers required file, the running
of the AFP and the implementation of the plan.

1.3

Definitions
CTR - Cell Traffic Recording
FER - Frame Erasure Rate
NetCfg - Network Configuration Workbench
NCC - Network Control Centre

1.4

Responsibility
The overall responsibility of preparing, implementing a frequency plan is that of the Planning and
Optimisation Team Leader(s) for the area(s) where the plan is implemented. All members of the team
are required to assist.

1.5

References Documents

1)
2)
3)
4)
5)
6)

CellOpt 2.1 Users Manual, and online manual.

Asset Users Reference Guide.
Use of TMOS procedure.
Generating and changing Radio Cell Data procedure.
RBS2000 - Synthesised Frequency Hopping (SythHopCHGR.doc)
A simplified frequency planning procedure (SimpleFplanProc.doc)

2 PROCEDURE
2.1

Document Structure
A quick overview of the OTB, that helps one to prepare the files required for CellOpt is given in
Section 3 - this will give a contexts in which the rest of the preparation needs to take place.
The pre-planning process is described in Section 4. This pre-planning process is critical for a
conventional prediction based plan but also applies to a measurement-based plan.
Site lists need to be prepared for each plan the Plan-list is a list of site for which you would like to
find new frequencies. For a prediction based plan an Affected-list which should include all sites that

will affect or be affected by the frequency changes also needs to be generated. Tips on how to
prepare these are described in Section 5.
Section 6 provides methods to obtain traffic information traffic file. This will be used in many steps of
the planning process.
Section 7 describes how to obtain an interference matrix. 1) In the conventional way: using
predictions and traffic distribution in Asset. This is well suited in cases where a large number of new
cells need to be brought up. Or 2) Measurement based using CTRs. This will require that no major
sites were brought up in the last 2 weeks or so. For radio network quality reasons, a measurementbased plan is strongly recommended. A Combined measurement and prediction based plan is
recommended for rural areas.
How to prepare a carrier file and determine the number of required carriers per cell is described in
Section 8.
Section 9 gives two methods to obtain exception files from two possible sources: drive test and handover statistics. For a measurement-based plan it is recommended that one do not use exceptions as
this will only skew the interference matrix and provide less than optimum results.
A step by step procedure for generating a plan in CellOpt 2.1 follows in Section 10.
In Section 11 it is suggested to prepare backup data to recover if something went wrong during the
implementation of the plan.
Section 12 informs one how to update the Asset database and validate the sanity of the plan.
Section 13 describes how to implement the plan into the network using NetCfg.
Drive tests need to be performed after the implementation of the frequency plan to give final
validation and to allow for optimisation. Section 14 describes this process.
For future reference it is necessary and interesting to keep a record of the all the data pertaining to
the frequency plan. Section 15 stipulates what need to be recorded.

3 OVERVIEW OF OPTIMISATION TOOLBOX

The Optimisation Toolbox assist in the preparation of files to be used in CellOpt for both a measurement
and prediction based frequency plan.
The first screen enables the input of the Plan-CellList. This could be done by
selecting one or more BSC and or on and more Regions for which the a frequency plan need to
be generated or
providing a Site-list of all the sites for which the frequency plan need to be prepared
The next screen gives options for the source of your interference matrix.
This could be either a prepared prediction based interference matrix file that needs to be imported
or an interference matrix that is calculated by the OTB based on the CTR recordings.
The same screen provide possible sources for the traffic data:
The traffic can be extracted from the STS database or
be provided in various file formats.
The next screen allows the user to enter the rules for calculating the number carriers required. Only
one source of carrier information can be used, namely directly from the Planned Database.
After this a screen that allows for the entering of the Equipment types are allowed. A site-list of
RBS2000, a cell-list of Cell-extenders and a cell-list of CDU-D's are used to determine which cells can
do synthesized hopping.
The last screen allows you to select the output directory where the files that will be used for CellOpt
can be written to. All the files will be with the right filenames and the right formats for CellOpt. (The
OTB does all the required conversions)

4 PRE-PLANNING PROCESS

Get a Remedy Reference number by logging it yourself in Remedy or contact the NCC (083-182) for
implementing the plan on the scheduled date. Note that in most practical situations it is wise to start a
months before the time with the preparation of a frequency plan, at the rate that you would have if the
plan was due the next week - this is required due to the ever changing environment that we work in.

4.1

4.2

4.3

4.4

Asset Database
A list of all sites (Plan-list) to be included in the plan must be maintained at least one month before
the plan. This includes all new sites and all new sectorisations. Co-ordinate with the implementation
and transmission division and finalise a list of sites that will definitely be included in plan, i.e., sites
without any transmission, lease or equipment shortage problems. Note that for a measurement
based plan all the sites included in the plan must be up for at least a month before the plan .
Used the MoreFreq.exe tool to find frequencies to bring it up with.
All new sites and sectorisations that will be activated in the frequency plan must be entered into
Asset. Ensure that all the sites involved in the frequency plan have the correct data (this includes all
existing sites that can affect the planning area):

Antenna Height.

Azimuth.

EIRP.

Mechanical Tilt.

Antenna Type.

Correct Flags, e.g., the incorrect BSC and location area will affect the cell data generated after
the frequency plan.

Ensure that sites that have recently become operational are marked as operational in Asset, and
that the necessary change has also taken place in the WA system.
Once the site database has been updated, changes to this database and the sites should be limited
to sites well outside the planning area.

Predictions
Ensure that the correct prediction models and appropriate prediction radii are applied to all cells:

All major metropolitan sites must be predicted to a minimum of 40 km. The Suburban model is
recommended

Small town/road sites must be predicted to a minimum of 80 km. The General200 model is
recommended for towns and the Rural model can be used for the rural sites

Extended-range cells need to be predicted up to 150km, the rural is recommended

Generate before plan Interference Plots

Calculate the Best Server and Worst Interference arrays for
1. Co-channel interference on the BCCH layer
2. Adjacent channel interference on the BCCH layer
3. Co-channel interference on the TCH layer
4. Adjacent channel interference on the TCH layer
The layers for which the interference is calculated can be set up on in Tools/Array settings....

Neighbours
Enter the neighbours for all new cells in NetCfg (the Cell relation tap) Neighbours could be identified
by inspection of the service area plot in Asset. Generate command files to run in new sites / sectors
with their neighbour relations.
Undefined neighbours can be identified using the Optimisation Toolbox - Neighbour Relation
Identification option. The previously undefined neighbours should be run into the switch and be active
for a while before the plan.
This is a good time to have a look at existing sites with too many (> 15 typically) neighbours and
delete unnecessary neighbours. Unnecessary neighbours can be removed, using the OTB or the
handover counts. Neither method should be used blindly. The OTB also enable one to identify
unnecessary neighbours that might be defined and have a high handover count, but where the
handovers are mostly ping-pong handovers.
Files must be generated remove excessive neighbours from existing sites.
This neighbour information may be retrieved from the BSC at a later stage for the purpose of a
neighbour exception file. In the future the neighbour relation file will also be used for BCC planning.

4.5

4.6

4.7

New Site/Sector Commissioning

All new sites and sectors should be pre-tested before activation. This will involve loading test
frequencies into the site and drive testing with TEMS. Checks should be made for sector swaps,
antenna faults and cabling faults. These checks will eliminate any doubt when drive testing after the
new frequency plan has been implemented. Use as far as possible reasonable clean frequencies to
bring these sites up with. If this is not possible and a prediction based plan is implemented, these
sites should be halted again, but for a measurement based plan they should really be active for as
long as possible before the plan.
For a measurement based plan these sites need to be brought up on temporary frequencies (use the
MoreFreq.exe tool) at least a month before the scheduled date of the plan, to allow measurement s to
take place on these cells and their neighbours.

Identify Donor Cells of Cell Extenders

Make a cell-list (preferable Planet format) of cells that have cell-extenders linked to them. This will be
used to identify RBS2000 cells that will not be allowed to do synthesized hopping. A query Donors
cells of Cell-Extendersis available in the CTR-Admin database (O:\PlanOpt\Data\MTN Network
Information\Frequency Planning.mdb) is available to ease this. Note that manual checking is required.
Make a list of the cell-extenders, their locations and the cells that they are linked to. This will be used
to inform the Installation Technicians of the new frequencies for the cell-extenders.

Define second channel groups.

Second channel groups need to be defined for all cells that do not yet have a second channel group
defined. This can be done in NetCfg (Utilities/ Node Edit). A complete description of the commands
that need to be run in can be found in Reference 5. Note that two channel groups are
recommended even for cell that will do base band hopping.

PREPARING THE PLAN-LIST AND THE AFFECTED-LIST

The decision on the Plan-Sitelist needs to be made well in advance.
The Optimisation Toolbox can automatically generate a plan-List based on queries on the BSCs and
Regions. The Affected Cell-list automatically based on the interference matrix.
A Plan-Sitelist can be generated in Asset: an option to define a site filter is available on the site
database form - use the frequency planning boundaries to filter the list. The plan site list would need
to be exported (Files/Export/Planet) to be used in the OTB later.
For a prediction based plan it is required that an Affected Site-list is defined before hand to limit the
size of the interference matrix. To generate an affected site list in Asset, a user-defined polygon is
useful. In the Enterprise tool set under the Tools tap select Editors/Vectors. Use the polygon option
to draw an affected area around the plan area. This polygon can then be used in generating an
affected site list in Asset
Queries are also available to generate a Plan-Sitelist in Frequency Planning database
(O:\PlanOpt\Data\MTN Network Information\Frequency Planning.mdb) GetPlanSiteList*.

PREPARING A TRAFFIC FILE

One of the three methods below can be used to determine the traffic per cell - the first is the preferred
method, because of the simplicity and accuracy. It is always recommended that the traffic be checked.

6.1

6.2

Using the Optimisation Toolbox

An option is available in the OTB to get the data from the database automatically. The traffic that is
currently (03/2000) used is the third highest traffic value reported in the previous month. The tool
provides a growth factor to grow the traffic.
Also available is the option to import the traffic for some cells (typically the Planned Cell list) and
request the tool to query the database for the traffic on the rest of the cells.

Getting Live Traffic from the Database:

Two Access queries are available in Frequency Planning database (O:\PlanOpt\Data\MTN Network
Information\Frequency Planning.mdb) to get a good estimation of the peak traffic that a cell will carry:

6.3

6.4

Traffic (Asset Format) and Traffic per Site Sector running this query would create tables in the
Frequency Planning Access database, which can be exported and used with other tools.
The queries provide the third highest traffic level recorded in any hour over the previous month a
scale factor is entered as parameter to allow for future growth.

Predicting traffic using the Forecast tool:

A traffic forecast tool is available on STS on MTNsn03 (the drive where CellQ&A runs from). Run the
executable Forecast.exe.
The results appear as c:/ forecast.trf on the PC that you are working from this file is in Planet
format.
A conversion utility can be installed from O:\PlanOpt\Apps\TrafficConverter\Setup to convert it to
Asset format. (This is required for a prediction based plan; the traffic would need to be imported)
Currently (2000/05) this tool is not considered accurate enough to be trusted blindly and planner
should double check all the values - especially the sites that came up in the last three month and
ones that were off during the last three months.

Preparing Traffic files using Asset:

When many new cells are to be integrated in the frequency plan, the traffic utilities in Asset can be
used. For more complete information consult The Asset Users Reference Guide under Traffic
Analysis and Terminal Type.
First confirm that the necessary Terminal Types are defined (use GSM 900). To define the Terminal
Type or to define or change the way the traffic is spread between different clutter types go to Options/
Terminal Types
If the new cells are placed amongst existing sites the live data need to be imported. Go to
Tools/Traffic/Load Live Traffic and load the live or forecasted traffic data (as generated in 6.2 or 6.3) in
Asset Format.
To determine the traffic distribution in the area, run the Traffic Wizard (Tools/Traffic).
The traffic can be forecasted or grown using the Scale Traffic option.
To determine the traffic that would be absorbed by all the new cells (and the old cells) run Analyse
(Tools/Traffic). The captured traffic is stored in a temporary file. This could be renamed and imported
into a spreadsheet or into Access where it can be translated into a normal traffic file.

7 GENERATING AN INTERFERENCE MATRIX.

For completeness and for trouble shooting it is recommended that both interference matrices are
prepared for any frequency plan, particularly so for a combined plan.

7.1

7.2

For a Prediction based or "combined" plan

In Asset open up a window that would display all the affected sites. Use the Interference Table Wizard
(Tools/Interference Table) to generate the interference matrix. To have this interference matrix to
reflect the traffic distribution it is necessary to follow the procedure under 6.4.The OTB will translate
this interference matrix to Planet format.

Using Cell Traffic Recordings (CTRs)

Verify that sufficient measurements are available to implement a measurement based frequency plan.
At least 120 Mobile Measurement Records for macro-cells and at least 50 for micro and pico cells are
required. Use the query Sufficient CTR recordings? in the Frequency Planning database to establish
the completeness of the measurements.
To give priority in the CTR-Scheduler to cells that does not have sufficient measurements use the
query Order CTR-recording or Order Cells insufficient CTRs to place the cells in the CTRCMDBUF
table.
To generate an interference-matrix simply use the option in the Optimisation Tool Box. Note that this
might take up to a day to generate, so consider this in your planning

8 PREPARING A CARRIERS FILE

Optimisation Toolbox provide the facility to extract carrier data from the Planned Database (MTNIS)
The number of carriers are then calculated based on the amount of traffic, whether the site is
synthesised hopping or not. The number of Carriers will always be equal or bigger than the number of
TRX's. The tool requires the following inputs, which can be provided through cell and or site lists or
from queries off the database.
The synthesised hopping site list is a list of all sites with RBS2000s (Site T number). It can be
obtained using the query RBS2000 Sites from the database (O:\PlanOpt\Data\MTN Network
Information\Frequency Planning.mdb database. A table called List of 2000 will be created. This
can then be exported. If you choose to have the number of carriers equal to the number of TRX's
this is not required.
A list of cells with CDU-D on in Planet format. (SiteTnumber <tab> sectorNumber). (A query is
available on the Frequency Planning database, but the results need to be double checked)
A list of donor cells to cell-extenders (SiteTnumber <tab> sectorNumber). A query is also
available to determine these in the Frequency Planning database. Note that this table is only as
accurate as the database and must be double-checked.
The recommended settings for a measurement based plan are

Assume 4.5 Erlang is not carried in the Hopping Set, but on the BCCH (BCCH preferred)

Use 100% Frequency load on the Hopping Set

Traffic growth of 20%

Minimum Hopping Carriers 1

Maximum Hopping Carriers 1

Minimum Carriers 2

Allow carrier reduction.

The recommended settings for a prediction based plan are

Assume 4.5 Erlang is not carried in the Hopping Set, but on the BCCH (BCCH preferred)

Use 100% Frequency load on the Hopping Set

Traffic growth of 20%

Minimum Hopping Carriers 4

Maximum Hopping Carriers 4

Minimum Carriers 2

Allow carrier reduction.

9 GENERATING AN EXCEPTION FILE

9.1

9.2

Both exception files can be used, but is not advisable when doing a measurement based plan. It is
still advisable to prepare both exception files when doing a frequency plan - they come in handy as
emergency measures.

Getting exceptions from hand-over statistics

In NetCfg there is a utility that generates exception files from the hand-over statistics:
Utilities/Handover Filters; use the Handover Filter tab.
A query HandOverExceptions in the Frequency Planning database is a quick way of getting exception
in CellOpt format.

Getting exceptions from TEMS drive test.

An application is available on O:\PlanOpt\Apps\TEMS Exceptions to generate exceptions from TEMS
drive test. It is strongly recommended that the all the cells BA-list be changed to include the entire
BCCH block when the drive tests are being performed.

10 OPTIMISING THE FREQUENCIES IN CELLOPT

10.1 Setting up CellOpt

If CellOpt is not already installed follow the installation instruction in O:\PlanOpt\Apps\CellOpt\Install\.

In the Models directory, three sub-directories exists - one (NCS_and_Preditions) contains a

recommended/sample model set-up for a prediction based plan, one contains (FER_from_CTRs) the
set-up best suited for a CTR measurement based plan, and then there is Combined for a combined
measurement and prediction based plan. Chose the model that you would like to implement. Confirm
that the files are tab delimited data, and ensure that there are no spurious tabs or spaces in the file.
Copy the following files to your chosen model directory ( the filenames are important):
The plan site list as was prepared in Section 5 in Planet format as sitelist.txt
The carriers files as was prepared in Section 7 in Planet format as carriers.txt
If you intend doing a synthesised hopping plan prepare a Planet format site list of all the RBS2000
sites. It can be obtained using the query RBS2000 Sites from the database (O:\PlanOpt\Data\MTN
Network Information\Frequency Planning.mdb database. A table called List of 2000 will be created.
This can then be exported. Store this in your model file directory as RBS2000S.txt. The OTB also
exports this file.
Prepare a list of all cells that have CDU-D's installed. The query CDU-D list for CellOpt could help
to identify these cells - it is important to verify the results of this query (List of CDU-D's table) as it
is based on some assumptions, and the database currently (01/2000) does not accurately reflect
all CDU-D cells. Store this as CDU-D.txt in the appropriate model directory as a Planet format file
(T#### Secno).
Also prepare a list of cell-extenders. The query Donors cells of Cell-Extenders generates a table
Donors of Cell-Extenders, that can be exported. Store this in Planet format as CellExtenders.txt
Copy the interference matrix to the directory as intmatrix.txt (and in the case of a Combined plan
the Prediction based interference matrix should be named intmatpred.txt).
Copy the hand-over exception file as Exceptions.txt into your model directory.
Please make sure that CTR_FER.Plan file and the reference to it in the CTR_FER.txt file are
deleted. The file contains information from the previous plan, and will corrupt the carrier
changes.

10.2 Running the Optimiser

Run CellOpt.
Load the model file (Prediction.txt or CTR_FER.txt).
Carefully note in the General Application log at the bottom of the CellOpt Screen that everything
loaded successfully.
Start the Optimiser, and log the CQI (CellOpt Quality Index) in a log file.
From time to time, without stopping the optimiser export a carriers file in Planet format.
Let the optimiser run for at least 12 hours. (A good time to generate backup data.)
From time to time Export the carrier file without stopping the optimiser, these file can be used as a
backup.
Stop the optimiser after it is clear that it has converged and that no further improvements could be
made. Export the carriers in Planet format.
In future the BCC (Base Station Colour Code) must be planned in CellOpt. Choose the exception list
as neighbours and the NonHopFER or Traffic Interference as penalties. Export the carriers in Planet
format. Import this back into the OTB where the NCC will be planned. One will use the OTB to import
the carriers into the Asset database.
Currently (2000/03) the BSICs are planned when the BCCH carriers are accepted. So the carrier file
exported from need to be imported into the Asset database using the tool Asset Import from the
Planningtoolbar.

11 GENERATING BACKUP DATA FOR THE SWITCH

Generate command files using NetCfg that can be used in the case of an emergency to restore the
network to its original state before the plan.

12 VERIFYING THE FREQUENCY PLAN

Before starting with this process ensure that any changes that you want to make in Asset has been
committed and those that you don't want to make restored.
Import the carriers file that has been exported from CellOpt using the import tool Asset Import from
the Planningtoolbar.

Open Asset and do not commit any changes now.

Calculate the Best Server and Worst Interference arrays for
1. Co-channel interference on the BCCH layer
2. Adjacent channel interference on the BCCH layer
3. Co-channel interference on the TCH layer
4. Adjacent channel interference on the TCH layer
The layers for which the interference is calculated can be set up on in Tools/Array settings.... Identify
any serious interference problems that might be customer affecting. Take the necessary action, e.g.
change a frequency, alter the settings in CellOpt or add additional exception or interference arrays
into CellOpt - change the settings if required.
Store these interference plots and make printouts as part of the documentation process.

13 IMPLEMENTING THE FREQUENCY PLAN INTO THE NETWORK

Before the new plan is run in, a frequency dump must be taken from all relevant BSCs (i.e., RLCFP:
CELL=ALL). This information is read into the Oracle database and will allow the RLCFE command to
end the current frequencies. This should happen automatically, but you can ask Daniel to force a
dump.
Once you are satisfied with a particular plan, commit the changes in Asset (Asset Utilities (Commit All
button) in the Planningtoolbar). Note that only the sites allocated to you will be changed - if you are
combining a plan with a neighbouring region, they must also apply and commit the frequency
changes. After it is committed in Asset it the data is downloaded in the planned database.
Queries are available to group approve the changes - ask Daniel. The BCCH approval currently
(2000/03) triggers the calculation of the BSIC
Command files can now be generated to implement the new plan on the various switching centres.
Essential commands for celldata are:
RLSTC ! Halt the cell/site.
RLDEC ! Change BCCH and BSIC.
RLCFE ! End old traffic channels.
RLCFI ! Enter new traffic channels.
RLMFE ! End old measurement frequency list.
RLMFC ! Enter new measurement frequency list.
RLCHC ! To change hopping sequence numbers.
External_cell BSC definition must also be changed to update BCCH and BSIC changes.
After the plan has been successfully run, another frequency dump must be taken from all relevant
BSCs. This will be used as a consistency check to confirm that the new active frequencies are the
same as the planned frequencies.

14 VALIDATING AND OPTIMISING THE FREQUENCY PLAN WITH

DRIVE TEST

Generate a new TEMS cell list from the Oracle database and drive test the network.
Verify all the inter BSC handovers
Note any interference or drops due to interference.
Note any missing neighbours or missing measurement frequencies

15 KEEPING RECORDS

The following data need to be stored in O:\PlanOpt\Data\Records\FreqPlan\<Frequency Planning

Area> and on a stiffy:
A completed Frequency Planning Form; make a printout too to store with the interference plot.
(for the form O:\PlanOpt\Data\ISO9000\Documents\FreqPlanForm.xls);
A log of all the settings used in the OTB.
All the files used in the OTB.
All the files exported from the OTB.
All the files in the CellOpt/Model directory.
The carrier file imported into Asset.

The backup files.

The command files that were generated.
The TEMS log files.
The TEMS cell lists.
The stiffy, along with all before and after interference plots need to be stored in a common cabinet.

DEFINITIONS
N/A
RECORDS
Frequency Planning form, stiffy and interference plots as specified under 15 Keeping Records.
PROCEDURE DETAILS
Originator/Author Name:
Location:
Position:
Originators Manager:
Location:
Position:
National Quality Manager:
Distribution List:

Magdaleen Snyman
Head Office
Assistant Manager Optimisation
Hendi van der Merwe
Head Office
Optimisation Manager
Andrew Portokallis
Network Group

AUTHORIZATION
Designation:
Name:
Signature:
Date:

Group Executive

Originators
Manager

Document
Originator/Author

DCS Administrator