dual band application note network

7/28/2019 Dual Band Application Note network

1/21

Alcatel File Reference Date Edition Pagedb_ap_no.doc 21/12/98 01 1

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization.

Appendix B to the

A955 V5.01 User Manual

Dual Band

Application Note


2/21



CONTENTS

1. SCOPE ..................................................................................................................................32. PLANNING ENVIRONMENT.................................................................................................42.1 Defining the System Technology...........................................................................................42.2 Defining the Mobile Class......................................................................................................42.3 Defining the Calculation Models ............................................................................................42.3.1 Propagation Model (CS) ........................................................................................................42.3.2 Fieldstrength Prediction Model (NW).....................................................................................52.3.3 Assignment Model (NW)........................................................................................................52.3.4 Coverage Model (CS and NW)..............................................................................................52.3.5 Models for the Maximum/Strongest/1. Best Server, Max. Interferer at Max. Server,

Max. Interferer at No Best Server; C/I at 1. Best Server (NW)..............................................62.3.6 Traffic Model (CS)..................................................................................................................62.3.7 Interference Model (CS) ........................................................................................................6

2.3.8 Interference Model (NW) .......................................................................................................62.3.9 Channel Separation Model (NW)...........................................................................................72.3.10 Frequency Assignment Model(s) (NW) .................................................................................72.3.11 System Parameter Model (NW).............................................................................................72.4 Defining the Network .............................................................................................................72.5 Defining the Project ...............................................................................................................72.6 Defining the Project Status....................................................................................................82.7 Site/Sector Definition .............................................................................................................92.7.1 Site Definition.........................................................................................................................92.7.2 Sector Definition ....................................................................................................................93. PLANNING TASKS..............................................................................................................123.1 General Tasks .....................................................................................................................123.1.1 Site/Sector Selection............................................................................................................12

3.1.2 Calculation Model Selection.................................................................................................123.2 Pathloss and LOS Tools ......................................................................................................123.3 Fieldstrength Prediction .......................................................................................................133.4 Assignment..........................................................................................................................143.5 Maximum/Strongest/1. Best Server; Max. Interferer at Max. Server;

Max. Interferer at No Best Server; C/I at 1. Best Server......................................................143.6 Coverage Plan.....................................................................................................................143.7 Traffic Load and Traffic Capacity.........................................................................................153.8 Mutual Interference..............................................................................................................163.9 Channel Separation .............................................................................................................163.10 Frequency Plan....................................................................................................................163.11 Interference and Outage......................................................................................................173.12 Tool Calibration....................................................................................................................18

3.13 System Parameter (CAE Data) Generation.........................................................................194. CONCLUSION.....................................................................................................................215. ABBREVIATIONS................................................................................................................21


3/21



1. SCOPE

The scope of this appendix is to outline the extent to which the current version of A955 RNP V5.01

tool can be used to plan dual band radio networks. Although the tool provides the theoretical

possibility to plan 900/1900 MHz networks, this document will solely focus on the 900/1800 MHz

combination in one network.

Only specific dual band topics relative to the planning of conventional networks are outlined. For

general tool handling please refer to specific sections of the user manual.

Also, the document supports only the multiband BSS approach (dual BCCH, as defined in BSS

software release B5).

In the course of this appendix, the original operation band, providing coverage continuity all over the

service area, will be called the main band (classical band), and the additional operation band,

intended for capacity enhancement in selected areas, will be called the second band (preferred

band). If not stated otherwise, it will be assumed that the 900 band will be the classical band and the

1800 band the preferred band.

A next assumption is that the dual band network contains only macrocells. Since all cells operating in

the same frequency band form a network layer; this dual band network will contain 2 layers: one 900

macro layer and one 1800 macro layer.

The structure of this appendix is as follows: first, the necessary inputs/settings/definitions will be

mentioned and the calculation models will be defined in a sensible way.

In a second part the specific planning tasks and their outputs will be assessed.

Finally a summary will be presented as a conclusion.


4/21



2. PLANNING ENVIRONMENT

The goal of chapter 2 is to depict the dual band network structure (macro 900, macro 1800) on the

planning environment of A955.

The approach is to define the two network layers within the same project status. As it will be later

shown in more detail, dual band cells are defined in a similar way as in a classical network by

specifying for each layer/band the cell attributes. Co-site location doesnt cause problems; it can be

handled with an additional parameter in the data model which defines the operation frequency on a

per cell basis.

In consequence, all calculations can be handled consecutively within the same project status.

2.1 Defining the System Technology

The definition of the system technologies can be performed in the form Network WDB|System

Technology or alternatively in the form Project Status , section Frequency Bands.

note, that for GSM900 the ARFCN range is [1...124] and for GSM1800 it is [512...885] for UL

and DL

the MS_RX_PWR_Thresholdhas to be set in dependency of the Mobile Class (see 2.2)

set No. of BCCH/Cell=1

the other values have to be entered according to the GSM recommendations for

GSM900/1800 respectively

Remark: for the CAE data generation it is important to strictly obey the CMA offsite specification (B5).

In the form for System Technology, the System Technologyhas to be one of the following: P-

GSM/DCS1800/DCS1900. The Name of the Datasetcan be freely defined by the user.

2.2 Defining the Mobile Class

The definition can be achieved in the form Network WDB|Mobile Classes.

for GSM900 phase 2 the MS sensitivity is -102 dBm and the maximum power according to

the mobile class are: class 2 (8 W), 3 (5 W), 4 (2 W), 5 (0.8 W).

for GSM1800 phase 2 the MS sensitivity is -100 dBm and the maximum power according tothe mobile class are: class 1 (1 W), 2 (0.25 W); for GSM1800 and GSM phase 2 there is

additionally class 3 defined (4W), but it is treated as an class 1 MS from PC point of view

2.3 Defining the Calculation Models

2.3.1 Propagation Model (CS)

menu: Database|Model|Cell Specific|Power|Extended Hata

the relevant parameters are mentioned in the table below; the remaining parameters which

are initialized with default parameters can be left unchanged;


5/21



remark: the same MS Ant. Heighthas to be used for GSM900/1800

Parameter

Calc. Model Calc. Frequency a1 a2 a3 b1 b2GSM900 925 MHz 69.55 26.16 -13.82 44.9 -6.55

GSM1800 1795 MHz 46.3 33.9 -13.82 44.9 -6.55

2.3.2 Fieldstrength Prediction Model (NW)

use the L&S GSM model; (the Networkwide|Power model is not implemented in version

5.01)

menu :Database|Model|Networkwide|L&S GSM

the same model is used for calculating the NW Fieldstrength Prediction for theGSM900/1800 layers

the max. time delay must correspond to an maximum range for 35 km (i.e. max. 232 s) and

the Minimum Access Levelmust be set to -98 dBm (GSM900) and -96 dBm (GSM1800)

for the protection values the default values as defined in GSM recommendations can be

adapted

2.3.3 Assignment Model (NW)

menu: Database|Model|Cell Specific|Assignment; set the AssignmentPower Threshold

(below which the assignment probability is set to zero) to -98 dBm (GSM900) and to -96 dBm(GSM1800)

consider HOis recommended to be set to yes in order to calculate the neighbour

relationships

2.3.4 Coverage Model (CS and NW)

CS:

menu: Database|Model|Cell Specific|Coverage

the same model is used for calculating the CS Coverage Probability for the GSM900/1800

layers;

set the CoveragePower Thresholdto -98 dBm (GSM900) and to -96 dBm (GSM1800)

set Consider Sigma of Morpho= yes; set Consider Traffic= yes in order to consider the

traffic weighting (provided there is a traffic database) for average coverage calculation

NW:

a specific Networkwide|Coverage model is not implemented in version 5.01;

nevertheless, the calculation is performed by using the cell specific calculation results and by

determining the maximum value for each pixel and each layer


6/21



2.3.5 Models for the Maximum/Strongest/1. Best Server, Max. Interferer at Max. Server, Max.

Interferer at No Best Server; C/I at 1. Best Server (NW)

Strongest Server calculation

menu Database|Model|Networkwide|Strongest Server; set the Power Thresholdto -98 dBm

(GSM900) and to -96 dBm (GSM1800)

Maximum Server,1. Best Server, Max. Interferer at Max. Server, Max. Interferer at No

Best Server, C/I at 1. Best Server calculation

menu :Database|Model|Networkwide|L&S GSM, for details see 2.3.2;

2.3.6 Traffic Model (CS)

The simple traffic model is implemented in version 5.01, the GSM model is not implemented. The

same maximum blockingcan be used for GSM900/1800, though one model will fit both system

technologies. It must be consistent however to the goal as defined in the project status, see 2.6.

2.3.7 Interference Model (CS)

The models are utilized both for the mutual interference as well as for the final interference

calculations (interference on specific frequency). One model is required for each system technology.

menu: Database|Model|Cell Specific|Interference

recommended settings:

interf. margin= 0 dB (this value is considered as an offset to threshold C/I co-channel); threshold C/I (co-ch) = 9 dB;

max. int. prob. for constraint in the interf. matrix= 10 % (accept the default);

standard deviation for interf. calc= 6 dB;

min. Netw. access level = -98 dBm (GSM900) and -96dBm (GSM1800);

consider final interference= yes;

interference projection(considered channel) = least interfered or average over all

channels;

consider traffic weighting for mean calculation= yes (provided that there are traffic

databases available);

the parameter calculation= BCCH or others, enters only the outage calculation for the other parameters, default values can be adapted

2.3.8 Interference Model (NW)

One model will fit both system technologies.

menu: Database|Model|Networkwide|Interference

the following parameter settings are recommended in a first approach:

interference margin = 0 dB;

max. interference allowed for average over all frequencies= 5 %;

max. interference allowed after frequency assignment= 5 %;


7/21



weighting mode= by traffic (only those areas in the network will be considered where a

traffic exists); this will give a more realistic result than by area;

user interference: weighted average (will perform a weighting by assignment); the

option best case will yield more optimistic results

2.3.9 Channel Separation Model (NW)


menu :Database|Model|Networkwide|Channel Separation; the different thresholds for

BCCH/TCH/STCH interference can be set here

2.3.10 Frequency Assignment Model(s) (NW)


menu: Database|Model|Cell Specific|Frequency Assignment|Box or SA

2.3.11 System Parameter Model (NW)

menu :Database|Model|General|System Parameters

in a first approach the default parameter settings are recommended

2.4 Defining the Network

Settings in Section Description the parameters NCC, MNC,PLMNare defined for the dual band network: one single value

respectively

Settings in Section Models

the user may choose if he wants to select the GSM900 calculation models as default models

at network, project or project status level; for the purpose of this description it is assumed,

that settings are done at project status level (selection marked by green colour), see chapter

2.6

2.5 Defining the Project

Settings in Section Models

see chapter 2.6

Settings in Section Coordinate System

the coordinate systems defined at project level are valid for all subsequent project stati


8/21



2.6 Defining the Project Status

Settings in the Section Project Status

the user entries in this section are informal

the statistical results given in this section refer to all cells comprised in the project status, i.e

those for GSM900/1800

for the results given in this section see chapter 3.7 (max. blocking), 3.6 (min. coverage), 3.11

(network interference, network outage); 3.10 (arcs frequency, denials and error frequency)

Settings in the Section Models

in the current version of A955 it is possible to define only one default calculation model for

each calculation; since one default model is required for each system technology, one can

define the models for the classical band as default models and if a calculation in the

preferred band has to be done, the respective calculation model has to be selected manually

example: 900 band is classical band; 1800 band is preferred band

all GSM900 models (CS and NW) can be selected on project status level as a default

cell specific calculation models for GSM1800 technology have to be selected at sector

level

networkwide calculation models for GSM1800 technology can be selected only at project

status level and above, but not at sector level; so it is mandatory to check the selected

NW model before launching a NW calculation for 900 and for 1800

Settings in the Section Frequency Band enter the available frequency bands for GSM900/1800 allocating the channel and zone type;

the system technologies can also be defined within this section with the help of the System

button

Settings in the Section Raster Files

the files for topography, morphostructure, building and road maps are valid for both

GSM900/1800

it is necessary to include separate traffic density files for GSM900/1800, since the traffic

distribution may be different in the two frequency bands

Settings in the Section Frequency Group

a frequency allocation in groups can be done within this menu separately for GSM900/1800;

if this is not desired, there are no settings to do


9/21



2.7 Site/Sector Definition

2.7.1 Site Definition

There are two ways to define sites: directly on the map and in the sector editor.

In case of no co-location of GSM900/1800 sites: normal handling as described in previous chapters

of the users manual.

In case of site co-location for GSM900/1800, it is recommended to obey the following:

if all antennas for GSM900/1800 will have the same height, it is sufficient to define one site

which will host sectors of both system technologies

site creation: it is recommended to work in the spreadsheet by duplicating records/creating

new ones/copy & paste and making modifications on them

section Management: it might be useful to point out the system technology in the site name

for clear distinction

section Location : take care on a proper description to avoid later confusions

section Coordinates: the entries for the site coordinates x and y must be identical and

consistent in all of the defined coordinate systems (for the time being this check still has to

be performed, but as soon as copy & paste functionalities will be available the condition will

normally be fulfilled )

section Buildings: enter the max. antenna height above ground separately for

GSM900/1800

section Topology: the GSM900/1800 sectors have to be assigned to the same BSC since

they are managed via the same Abis link

2.7.2 Sector Definition

The tool offers the possibility to colour the sectors individually for better distinction on the map

window. So, the user can use different colours for GSM900 and GSM1800 respectively, see menu

Configuration|Preferences|Site/Sector Display:

in section Site, choose parameter Default Site Colourand make settings

in section Sector, tick Sector Colouring , choose the parameter System Technologyand

make settings

There are two ways to define sectors: directly on the map and in the sector editor.

In case of no co-location of GSM900/1800 sectors: normal handling . It might be helpful to point out

the system technology in the site name for clear distinction of 900/1800 sectors.

In case of site co-location for GSM900/1800, it is recommended to obey some particularities which

will be mentioned in the enumeration below:

sector creation: it is recommended to work in the spreadsheet by duplicating records/creating

new ones/copy & paste and making modifications on them

Section Description: the settings have an direct impact on the CMA data generation


10/21



the CIhas to be set manually in the site/sector table, section Description; however,

the results have to be compliant with:

BSS release B5: two CIs are assigned (one for the GSM900 cell, one for the

GSM1800 cell);

BSS release B6: one CI is assigned for a dual band cell

LAC: for the calculation see chapter 3.13

Cell Type:

the cell type is defined by 4 parameters: coverage, dimension, partition, range

e.g. for a regular macrocell the attributes are: coverage= single; dimension=

macrocell; partition= normal cell; range= normal cell

Remark: the coverage, dimension, partition, rangecan also be viewed via the

ARFCN sheet

system technology: set the system technology on a per cell basis

the cell class(range :[urban......rural]; mandatory for the CMA data generation) defines

the geographical environment of the cell;

For the time being this parameter has to be set manually; in a future version of A955 it

will be determined automatically with the help of the assignment probability and the

morpho structure database.

Since the definition of cell class is left to the user, the same cell class should be

defined in case of site co-location.

Hint: use the Statistics on Cell feature to easily determine the predominant morpho

structure in the assignment area of a cell.

Section Manager: for the sector name it might be helpful to point out the system technologyin the sector name for clear distinction of 900/1800 sectors

Section Topology: see 2.7.1, section Topology

Section Calculation Results: see chapter 3; for B5: the results given here refer always to the

selected sector

Section Transceiver: the BTS hardware type can be specified as defined in

Database|Network|Hardware Type

Section Antenna:

in case of dual band (resp. monoband) antenna usage:

orientation, height above ground, mechanical downtilt: identical (resp. individual)

setting for GSM900/1800 sectors antenna patterns practically dont differ considerably for 900 MHz and 1800 MHz; only

one pattern has to be generated and can be used for both system technologies

Remark: if electrical downtilt is used, different antenna patterns might have to be

considered, since electrical downtilt is adjustable independently for both frequency

ranges.

Section Power:

the parameters of this section enter the pathloss and the power budget computation

the parameters EIRP, BTS power, cable length, cable attenuationmay differ for

GSM900/1800 and have to be entered individually, also the parameter Mobile Classwhich

depends on system technology


11/21



Section CAE Data and section Neighbour Cells: see chapter 3.13

Section Forbidden ARFCN: independent setting for GSM900/1800

section Mutual Interference: for the results, see chapter 3.8

Section Models: the default cell specific models for the classical band which were defined

on network/project/project status level will be considered unless no other model is chosen;

therefore it is mandatory to select all cell specific calculation models for the preferred band at

sector level

the model selection at sector level is marked by the red colour


12/21



3. PLANNING TASKS

In chapter 2 the calculation models were determined and the planning structure was defined.

Guidelines for the site/sector handling were given.

Chapter 3 shows for each planning task how to use A955 and in which form the result is generated

(output file or numeric results); the storage location of numeric results is mentioned.

Remark: since inputs and results are stored in a common database, a distinction is not always

possible in the tool handling. So, inputs and results may appear in the same sheet/form; results are

often editable.

3.1 General Tasks

3.1.1 Site/Sector Selection

best way: in the site/sector table; each cell of a layer is characterized by its rnp_bts_id

on the map via the selection area and/or via right mouse click: it is not possible to select all

sites/sectors on the map in case of co-site location

3.1.2 Calculation Model Selection

Generally speaking, the networkwide calculation models can be selected at network, project and

project status level as described in sections 2.4, 2.5, 2.6; cell specific calculation models can also be

selected at network, project, project status level and additionally at sector level as described insection 2.7.2.

Remark: make sure to select the proper networkwide calculation model each time you switch

between system technologies.

For exceptional cases where none of the above mentioned procedures applies, the selection

procedure will be mentioned in the respective calculation description.

3.2 Pathloss and LOS Tools

LOS calculation on an area or along a vector the calculation algorithm has to be selected after calculation launch; 2 algorithms are

possible: min. rec. height and LOS-yes/no

selection of sites/sectors in the site/sector table

calculation can be started from the menu

for every selected sector there will be an output file

due to the frequency independency of the LOS calculation, in case of co-location and

identical antenna heights the LOS results for the GSM900/1800 sectors of a site will be

identical


13/21



Remark: the LOS calculation along a vector (L&S algorithm) is analog, but there is no output file

created.

LOS calculation and Pathloss calculation along a path defined on the map:

the parameters which enter the calculations can be edited in the table InfoDB|UserAdmin|

User Roles Preferences

for the LOS calculation along a path these are: group: PathLossCursor(!), name:

GetHeightTx, GetHeightRx

for the pathloss calculation along a path these are: group PathLossCursor, name:

GetFrequency, GetHeightTx, GetHeightRx, GetPower

these calculations are not site/sector dependant

for every new computation the result will be displayed as a 2D plot

3.3 Fieldstrength Prediction

A955 offers accurate propagation models suitable for hierarchical dual band network and capable of

diffraction, scattering, reflection, ray tracing.

The power calculation is handled independently in the different network layers.

Fieldstrength Prediction (CS)

all sectors GSM900/1800 for which the calculation has to be done can be selected at once

(starting with version 5.1);workarround for version 5.01: perform separate calculations, first for all GSM900 cells and

than for the GSM1800 cells; make sure, the correct propagation models are used (hint: this

can be checked by selecting the single step mode and by displaying the propagation model

parameters with the Show button)

in the fieldstrength dialog the standard selections can be performed for modes, prediction

type, area selection, raster data; the selection for propagation modelhas to be sector

specific;also the same diffraction model has to be selected (e.g. Deygout ITU)

for every selected sector there will be an output file

Remark: in a next version of A955, power statistics will be available within the calculation

Statistics on Area, section Pixel Results

Fieldstrength Prediction (NW)

it is possible to create networkwide predictions for GSM900 and GSM1800 respectively;

therefore it is necessary to select all sectors for which the calculation has to be done having

the same system technology (e.g. with the help of filtering) and to start the GSM processor

with the calculation MaxFieldStrength (Network)

there will be an output file for each system technology

the GSM processor calculation Received Isotropic Power (Network) yields similar results

with MaxFieldStrength (Network) except that there are no distance restrictions considered


14/21



3.4 Assignment

For the version 5.01 of A955, assignment has to be done separately for both layers. HO between the

bands (preferred band, FDR) cannot be considered yet. A special algorithm taking account of all

these problems is under preparation.

it is possible to perform assignment calculations for the GSM900 and GSM1800 layers

respectively; therefore it is necessary to select all sectors for which the calculation has to be

done having the same system technology and to start the GSM processor with the

calculation Assignment Probability (Cell)

there will be an output file for every selected sector

the cell area[km2] is stored in the site/sector table in the column br_area_outer, the power

receive level at the cell border is stored in the column br_border_level;these results can be

alternatively viewed in the sector editor, section Calc. Results

Remark: in a next version of A955, a statistic on cell area will be available within the

calculation Statistics on Cells, section General Averaging

3.5 Maximum/Strongest/1. Best Server; Max. Interferer at Max. Server;

Max. Interferer at No Best Server; C/I at 1. Best Server

The calculations belong to the same family of calculations and can be applied independently for each

network layer. The Maximum Server takes into account distance restrictions and a threshold for the

minimum received level, whereas the Strongest Server considers only the latter. The 1. Best Server

filters those areas of the Maximum Server result where no interferences occur. Therefore thefrequency assignment has to be completed before.

it is possible to perform Maximum/Strongest/1. Best Server calculations for the GSM900 and

GSM1800 layers respectively; it is necessary to select all sectors for which the calculation has

to be done having the same system technology and to launch the GSM processor with the

respective calculations

there will be an output file for each system technology

3.6 Coverage Plan

Independent handling in the different frequency bands is mandatory. select all sectors for which the calculation has to be done having the same system technology

and start the GSM processor with the calculation Coverage Probability (Cell) (one output file

for every selected sector) respectively Coverage Probability (Network) (one output file for

each network layer)

the average coverage probability for each sector will be stored in the site/sector table, column

br_prob_av_cov;there can be an optional weighting by traffic, see 2.3.4

the average coverage probability for each network layer will be stored in the project status

table, section project status, parameter minimum coverage;the result is overwritten at switch

of system technologies


15/21



Remarks:

A combination of individual band coverages yielding a composite coverage plan of the complete

dual band network is forseen for a next version of A955. The planner can investigate within one

single plot areas which are covered by both bands, areas just being covered by GSM900 or

GSM1800 and areas having no coverage at all.

Also, in a next version of A955, the average coverage probability will be available within the

calculation Statistics on Cells, section General Averaging yielding the values min, max,

averageand within the section Pixel Results yielding the area percentage with a certain

coverage probability. A coverage statistic will be available within the calculation Statistics on

Area, section Pixel Results.

3.7 Traffic Load and Traffic Capacity

By independent handling of traffic loads in both bands most influencing factors are not considered

adequately. However, in order to split the traffic load between the layers or to limit the traffic load in

the main layer, two separate traffic density databases are necessary. For further considerations it is

assumed that a given traffic distribution is already split up into the two bands yielding two databases.

The traffic density database selection is achieved by a ranking within the project status form, section

Raster Files. The database with the highest ranking is considered. So, each time the system

technology is switched it is mandatory to priorize the desired database via ranking. the traffic calculation is launched via the GSM processor Required. It determines for each

cell: the traffic load of the cell br_off_cell_traf_out, the number of required traffic channels

br_rq_nr_traf_ch_out, the number of required signaling channels br_rq_nr_sig_ch_out.

Out of these, the number of required TRXs per cell br_rq_nr_trx_out, the traffic capacityper

cell br_traf_capand the blocking probability per cell br_block_probare determined. These

figures are stored in the site/sector table or can be alternatively viewed in the sector editor,

section Calc. Results.

the maximum blockingprobability for the layer will be stored in the project status table,

section project status

with the help of Tools|Statistics on Area it is possible to calculate: the total traffic load for an area, summed from the traffic database (no assignment

weighting considered):

define a selection area (!, blue rectangle) on the map

section Input Data; the result is given in section Traffic , parameter Total

the total traffic load summed for all cell areas in the selection area (i.e. assignment

weighting considered):

define a selection area (!, blue rectangle) on the map

section Numerical Result; the result is given in parameter Total Traffc


16/21



Remark: statistics on a cell basis can be performed in terms of number of carriers, traffic density,

traffic distribution, traffic loadand traffic capacity: select the cell; select Tools|Statistics|Cell; select

section Input Data and General Averaging (not implemented in version 5.01).

3.8 Mutual Interference

One mutual interference calculation is required per frequency band. The calculation is launched via

the GSM processor.

the mutual interference calculation can be performed for all cells of one layer at a time;

1st. step: select all cells of one layer in the site/sector editor (e.g. via filtering); all cells =

servers + interferers;

2nd. step: in the following dialog box Select Items, select the server cells; by default, all

cells are selected; if the box Show results is ticked, for each cell pair 3 result windows are

opened (C/I, co-channel and adjacent channel interference) and 3 result files are written; the

option Show results can be time consuming and should be used only if few results are to

be displayed; if Show results is not ticked, no result windows are opened

in any case, the calculation results for each cell pair are saved in the interferer matrix

(Database|Network|Interference Relation): prob_int_ms_co_int, prob_int_ms_adj_int; for

each cell the interferer cells and the victims are determined and can be viewed in the form

Cell Relations (access via the Interference Relation table), section Mutual Interference.

3.9 Channel Separation

The determined channel separation can be viewed in the form Cell Relations (access via the

Interference Relation table), section Channel Separation.

3.10 Frequency Plan

Preparatory steps are the determination of the service area (assignment calculation), traffic demand

and mutual interference.

Different thresholds are used for planning the BCCH, TCH and STCH frequencies. For BSS software

release B5 (dual BCCH), the planning is done separately for each band.

The frequency plan is stored in the sheet ARFN, columns ARFN; BCCH is indicated in BCCH

usage column.

The results of the frequency assignment algorithm are printed in a listing window; key figures are also

stored in the Project Status form, section Project Status.

All frequencies can be assigned manually and the results of the automatic frequency assignment can

be edited.


17/21



3.11 Interference and Outage

Although there is no interband interference potential, the Pout and Pint calculations must be done

separately for each band. In version V5.01 the outage probability is not implemented.

The interference and outage calculation family comprises the following calculations: cell specific,

networkwide and average calculations for interference and outage.

The Critical Frequency calculation result might be necessary for the cell specific calculation for

interference and outage, its result being stored in the site/sector sheet column br_crit_fx.

Cell specific calculation for interference and outage

Launch the the GSM processor calculation Interference on spec. frequency. The following options

are available: Specific Frequency, Critical Frequency, BCCH.

1st. step: select all cells of one layer in the site/sector editor (e.g. via filtering); all cells =

servers + interferers;

2nd. step: in the following dialog box Select Items, select the server cells; by default, all cells

are selected; if the box Show results is ticked for each server cell 2 result windows are

opened (C/I and interference probability) and 2 result files are written;

for each pixel of the plot, C stands for server, meanwhile 'I' represents the summed

contribution of all interferer cells operating an co and adjacent frequency

the option Show results can be time consuming and should be used only if few results are tobe displayed; if Show results is not ticked, no result windows are opened

in any case, the calculation results for each cell are saved in the Result directory on

harddisk and in the site/sector sheet in the columns:

cons_fx(frequency considered for interference and outage calculation)

br_int_fx (interference probability on considered frequency)

br_int_fx_ul (uplink interference probability on considered frequency)

br_int_fx_adj (adjacent channelinterference probability)

br_int_fx_adj_ul (uplink adjacent channel interference probability)

br_int_fx_co (co-channelinterference probability)

br_int_fx_co_ul (uplink co-channelinterference probability) For the outage results, the columns are named analog.

Remark: a statistic on interference (forseen statistic on outage) is available within the calculation

Statistics on Cells, section Pixel Results yielding the values min, max

also, an interference (outage) statistic will be available within the calculation Statistics on Area,

section Pixel Results


18/21



Networkwide calculation

The networkwide calculation is based on the cell specific calculation results (for the considered

frequencies).

select all cells of one layer

launch the GSM processor calculation Overall Interference

although the same model is used for calculation, it is necessary to perform the calculation for

each band separately to obtain interference plots for each network layer

the networkwide C/I and the networkwide interference probability result plots are pointed in

the Result database

Average over Frequencies

An interference and outage average over all frequencies of a cell can be computed.

select all cells of the network

launch the calculation Cell Calculation|Average over Frequencies

the calculation results for each cell are saved in the site/sector sheet in the columns:

br_int_av (interference probability, average over frequencies)

br_int_av_ul (uplinkinterference probability, average over frequencies)

Remark: in a next version of A955, the average over frequencies will be available within the

calculation Statistics on Cells, section General Averaging yielding the values min, max, average

Interference Averaging

An average over the computed cell interferences can be calculated for each network layer.

select all cells of one layer

launch the calculation Network Planning|Interference Averaging

the result (a numeric value) for the layer will be stored in the Project Status form, section

Project Status, parameter network interference (resp.network outage)

when switching between the system technologies, the result will be overwritten; it cannot be

saved

3.12 Tool Calibration

A separate tool calibration for each system technology is necessary. However, the calibration

procedure is identical. The result of each calibration is given on the screen and corresponds to the

minimum of the RMS curve in the plot. It is possible to calibrate the parameters of the propagation

model, the morpho structure gains and the morpho heights.

Hint to the numbering of the morpho structure gains: e.g. morpho structure gain 6corresponds to the

6th entry in the morphostructure table.


19/21



Case one: Analogue measurements are available.

Load the analogue measurements for each system technology, select the

measurement points and perform the calibrations with Measurement|Calibration.

Case two: Digital measurements are available.

Load the digital measurements and select according to the (BCCH, BSIC) couples

those cells which operate in the same frequency band. Then perform the calibrations.

The network planner has to know which cells belong to each frequency band.

3.13 System Parameter (CAE Data) Generation

According to the CMA offsite specification for BSS software release B5, four data files describing the

network have to be supllied by network planning. In the current version of A955, the CEL (main cell

description file), ADJ (neighbourhood relationship file) , FRQ (frequency list) are created.

The FHS (frequency hopping file) file will be implemeted in a next tool version.

For the time being only one default value (the GSM900 one) per parameter is possible, i.e manual

postprocessing is necessary for the GSM1800 default values.

All default and calculated parameters can be modified manually.

The generation of CAE data is taking place in the following mode:

during site/sector creation, the CAE parameters (their name starts with cae) are initialized inthe site/sector table with default values for GSM900. These parameters are needed for the

CEL file. The default values for the cell specific parameters LAC, BCC (=TSC) are

overwritten during the calculations Location Areas, BCC/TSC.

the parameter cell classis set according to see chapter 2.7.2;

according to the cell classparameter, the CMA offsite tool selects templates for the

rest of the parameters

CI: in the current version the CI is set to 1 for every cell in the network, manual

modification necessary, see chapter 2.7.2

LAC: calculation according to the LAC planning strategy, e.g.

a.) usage of the same LAC for the GSM900/1800 cells served by the same BSCb.) one LAC for the GSM900 cells belonging to the same BSC and another LAC for the

GSM1800 cells;

launch Calculator|Network Planning|Location Areas;

the results can be viewed in the site/sector table;

BCC(=TSC): in release B5 two BCCs are assigned (one for the GSM900 cell, one for

the GSM1800 cell); in release B6 one BCC is assigned for a dual band cell

launch Calculator|Network Planning|BCC/TSC

the results can be viewed in the site/sector table


20/21



the CAE parameters MS_TXPWR_MAX, MS_TXPWR_MAX_INNERwhich are

frequency dependent have to be adapted manually for the GSM1800 cells according to

the CMA offsite specification for B5, i.e the default GSM900 values have to be

overwritten

the simplest way to achieve this, is to operate in the spreadsheets and to set the

values using filtering and the Edit|Set Columns feature

the neighbourship table is filled with neighbourship information, which is needed for the ADJ

file:

during the assignment calculation, if the considered HO parameter has been set in the

cell specific assignment calculation model

or during the neighbour cells calculation (Voronoi method)

Note, that already existing results are overwritten.

select all sectors GSM900/1800 in the site/sector table

launch Calculator|Network Planning|Neighbour Cells;

In each case, the results can be analyzed via the form Cell Relations (access via the

Interference Relation table), section Neighbour Cell. Possibly delete all relationships

before starting a new calculation.

the ARFCN table is filled with information needed for the FRQ file during the frequency

assignment

the following CAE parameters are set automatically:

RNP_CELL_ID: combination of site and cell name

Frequency Range(new in B5): set according to the system technology

NCC, MNC: defined in the sheet Network WDB|Network (see 2.4)MCC: defined in the sheet Network WDB|Country

DTX_INDICATOR_SACCH(new in B5): will be set to default value 0

the data files CEL, ADJ, FRQ, are created via the menu Database|Export|RNP=>CMA

select the option RNP=>CMA;

than select the export format B5 Ed02

the results are written in the Export subdirectory on the disk;

the subdirectory for CMA data which is created by A955 is named according to the

project name

the filenames contain the project status ID

Remarks:

a statistic on the number of neighbour cells is available within the calculation Statistics on Cells,

section Numerical Results yielding the numbers of outgoing and incoming HO

if the system technology of a cell is not defined according to the CMA offsite specification for B5,

A955 urges to specify the system technology

all cells of a project status are considered for the CMA data generation; a possible workarround

is to set the parameter External Cellin the BTS form, section Description to yes.


21/21

Alcatel File Reference Date Edition Page

4. CONCLUSION

The following table summarizes the planning tasks as described in chapter 3 pointing the modality

they have to be realized in the current tool version. All tasks mentioned with an * need to get an

improved (i.e common) handling in future releases of A955.

Planning task commonhandling for 900

and 1800

separate handling for 900 and1800

Pathloss XLOS (area, vector) X

Fieldstrength (CS, NW) XAssignment * X

Max. Server Family XCoverage * X

Traffic Demand, Capacity * XMutual Interference X

Frequency Assignment XInterference, Outage (CS, NW) X

Tool Calibration XCAE Data Generation X

5. ABBREVIATIONS

A955 Alcatel RNP-ToolBCCH Broadcast Control ChannelBSS Base Station SubsystemBTS Base Transceiver StationCI Cell IdentityCS Cell Specific CalculationEIRP Equivalent Isotropic Radiated Power(F)DR (Forced) Directed RetryGSM 900 Global System for Mobile Communication (900 MHz)GSM 1800 Global System for Mobile Communication (1800 MHz)HO Handover

LA(C) Location Area (Code)MS Mobile StationNW Networkwide CalculationPC Power ControlRNP Radio Network PlanningTCH Traffic ChannelTRX Transceiver

End of Document

dual band application note network

Documents