Professional Documents
Culture Documents
Change History
This table shows the change history of this guide:
Edition
Date
Reason
11 June 2013
First edition.
Explanation of Symbols
Throughout this guide, where appropriate, some symbols are used to highlight
particular pieces of text. Three different symbols are in use, and are explained as
follows:
Symbol
Brief Description
Full Description
Note
Tip
Warning or Important
Contents
Help and Support
11
Chapter 1 Introduction
17
23
37
Page 7
101
Page 8
121
163
Page 9
175
187
205
Index
Page 10
213
From the Help menu, click Help Contents. Scroll through the table of contents and
choose a relevant topic to display.
To search for something particular, from the Help menu, click Help Contents and
using the Index tab or Search tab, type in a letter or word to start searching for
relevant topics.
Press F1 in a dialog box to view context-sensitive help (available for most dialog
boxes).
If the product is installed (not web-based), click Start on the taskbar, point to
Programs, then AIRCOM International, then <Product Name>, then Docs.
You can also navigate to the Docs folder in the location where you installed the
product.
- or If you want to view the PDF file through a web browser and you have a customer
web support account you can download the latest User Reference Guide (PDFs)
from our website. If you do this, please check for additions or corrections in the
'Change History' section near the start of the guide.
Page 11
Description
What's New
Describes the new features and enhancements that have been added to the latest release of the
ENTERPRISE suite.
How to use the AIRCOM OPTIMA Installation Tool, which configures the operation of AIRCOM
OPTIMA, including the Oracle table partitions and tablespaces. Includes information on how to
set up data definitions for incoming vendor data files and runtime parameter (INI) files for a
number of components such as the combiner, loader and summary modules.
Describes the operation and maintenance (O&M) procedures for the extraction, transforming and
loading processes of the AIRCOM OPTIMA backend programs.
Provides a brief 'look-up' reference for AIRCOM OPTIMA, the network performance management
and monitoring software tool.
How to use AIRCOM OPTIMA to view performance data and statistics both with ENTERPRISE
and standalone.
How to perform the I-VIEW SON application server installation, and how to manage users and
cluster allocation.
Describes the operation of I-VIEW SON, AIRCOM's hybrid SON optimisation application.
I-VIEW Live Plan User Reference How to install, configure and use I-VIEW Live Plan, a configuration management tool which can
update live and planned network changes.
Page 12
Description
What's New
Describes the new features and enhancements that have been added to the latest release of the
ENTERPRISE suite.
How to use ADVANTAGE to plan and optimise networks automatically, consider measured data,
and analyse network performance.
ARRAYWIZARD User Reference How to use ARRAYWIZARD to automatically generate pathloss predictions and best server
arrays, which gives you instantaneous display of coverage and interference information for preselected filters when loaded into ASSET.
ASSET Technical Reference
Provides array descriptions and information on some of the algorithms used in ASSET.
How to use ASSET, the network planning and analysis tool, to design a range of cellular
networks. Includes network planning, propagation modelling, service and bearer definition,
coverage analysis, traffic planning, neighbour planning, measurement data analysis, reporting,
arrays and simulation of network performance.
How to use ADVANTAGE to plan and optimise networks automatically, designed as an aid for
day-to-day planning.
How to use COMMANDER to execute individual commands or run batch processes on the
ENTERPRISE database without having to run ENTERPRISE itself.
How to use CONNECT, the network transmission and microwave link planning software for full
network physical link design and logical link design. Also contains CONNECT-specific reference
information, for example compatible file formats and performance calculations.
Describes the ENTERPRISE Data Service (EDS) capabilities, system architecture, hardware and
software requirements and Schemas required, and provides a guide for planning or interfacing
requirements to the Web Service.
Also contains information on supported data types and their read/write capabilities.
ENTERPRISE Database
Reference
Describes the relationships between tables in the database and the contents of each table.
How to install and configure ENTERPRISE, your network, and Oracle databases. Describes how
to use Administrator to create users and groups, and set permissions. Also contains information
on software licensing.
ENTERPRISE Notification
Service Technical Reference
Describes the ENTERPRISE Notification Service (ENS) capabilities and provides a guide for
planning or interfacing requirements to the Web Service. An example is also included to
demonstrate how to integrate ENS with MS BizTalk.
ENTERPRISE Technical
Reference
Provides information on file formats used across a number of ENTERPRISE products, as well as
antenna and diffraction calculations.
Describes the functionality that is common to most of the products in the ENTERPRISE suite, for
example the Map View, vectors, equipment and filters.
How to use the ENTERPRISE Data Service and ENTERPRISE Notification Service web
application. Also contains information about system administration and using power tools.
How to use the Financial Analysis module to evaluate and plan the revenue potential of your
network.
How to install I-VIEW Dimension and how to operate the user interface. Also contains
instructions on how to build the network model and use the software for mobile and transmission
planning.
How to locate Traffic Arrays using network measurement files topology files.
Page 13
Guide
Description
How to use the MYRIAD propagation model, which is a sophisticated model that can
automatically adapt to all engineering domains, radio environments and systems. (Separately
licensed model for use with ASSET.)
Obtaining Support
If you have a difficulty you cannot resolve yourself using the online Help or
Reference Guides, or you have found a possible fault in the software, you can log a
support request. You may also wish to contact us if you want to:
Register for a customer web account to access the Support area (send requests to
uk-support@aircominternational.com).
Go to www.aircomassist.com.
Log in, using your customer web account username and password.
Page 14
Give us as much information as possible about the problem and the context in
which it occurred
Can send extracts of your data sets if we need them to reproduce your problem
Page 15
Page 16
CHAPTER 1
Introduction
ADVANTAGE is an automatic network planning and optimisation tool. It provides
an advanced, integrated framework that is composed of:
Problem identification
GSM
UMTS FDD
Fixed WiMAX
Mobile WiMAX
CDMA2000
EV-DO
LTE
Occasionally in this guide, for brevity, the term WiMAX is used to represent Fixed
or Mobile WiMAX, and the term CDMA/EV-DO is used to represent CDMA2000 or
EV-DO.
To optimise any of these networks, you need to have the appropriate licence.
If required, multiple technologies can be used within the same project.
Page 17
About ADVANTAGE
ADVANTAGE is an automatic planning/optimisation platform that:
The number of sites required to meet the coverage and service objectives
during regional network rollout
The physical network configuration to maximise capacity for the desired range
of services and traffic demands
Utilises a wide range of survey measurement and network statistics data to tune
the modelled network and facilitate area performance optimisation
Page 18
Based on the same user interface as the rest of the ENTERPRISE products
Page 19
Antenna
Power
Grid
A choice of two cost mechanisms, each with its own set of metrics:
Array-based
Service-based
For more information on these two sets of mechanisms, see About Network
Optimisation on page 24.
The changes considered in the optimisation can be evaluated in terms of various
metric categories:
Metric Category
Represents
Budget
Financial
The financial value of the network plan, such as revenue or net income.
(Licence-dependent.)
RF
The network plan performance in terms of the targets specified by the user.
An overall optimisation cost value can be generated from all these components, based
on scenario-specific relative degrees of importance.
In summary, the optimisation depends on:
A set of radio parameters and targets that characterise the expected performance
for the metrics that can be affected by the optimisation.
A set of financial parameters and associated targets that characterise the financial
value of a plan and can be affected by the optimisation.
(This is licence-dependent. For more information see the Financial Analysis User
Reference Guide.)
Page 20
An analysis engine that estimates the cost values for the metrics used in the
optimisation every time a network plan is evaluated.
Page 21
Page 22
CHAPTER 2
Overview of ADVANTAGE
Before you begin to use ADVANTAGE, you should ensure that you understand the
basic concepts described in this section.
You must have the appropriate user permissions (these are specified in
ENTERPRISE Administrator) in order to use ADVANTAGE-specific functionality or
to change ADVANTAGE settings. For more information, see the Installation and
Administration User Reference Guide.
Measurement Data Usage - you can use area and/or cell-specific (measured or
experimental) data
The ADVANTAGE User Reference Guide describes all the steps and processes in
the tool. However, some of these steps, in particular the ones related to the radio
environment setup, will not be relevant to the general user, provided the
administrator (or super-user) has already completed them. This is also true for
optimisation scenarios that have been set up by one user that can be shared with other
users who access the same project.
You should always make sure that the ENTERPRISE project setup is up-to-date and
complete before proceeding. For more information, see the ENTERPRISE and ASSET
User Reference Guides.
Page 23
Antenna
Power
Grid
For example, you might want to run an optimisation that considers the following
network changes:
Array-based
Service-based
Analysis
The analysis functionality in ADVANTAGE enables you to analyse your network
plan against your chosen optimisation strategy, including the metrics and targets that
you have specified.
More specifically, it enables you to:
Access the rollout planning functionality, in order to assess and sequence the
potential network changes
You can evaluate a single plan, or compare two plans, in terms of their performance.
The performance achieved for each configuration is compared with the user-specified
performance targets and presented (in terms of absolute and/or relative values) on a
traffic and area basis. Depending on your licences, the performance can be based on
RF thresholds, and/or on financial or budgetary considerations.
The Analysis report generated can include:
Actions
Statistics
Costs
You can use the produced reports and/or graphical information to determine how
good a plan is, or the number/cost of the required optimisation actions.
Within the Analysis functionality, you can perform ranking on the potential network
changes, and create partial plans.
For more information, see Analysing and Evaluating Plans on page 163.
Problem Area and Problem Cell Identification
ADVANTAGE also enables you to quickly identify the areas and cells of poor
performance, based on user-specified targets. You can use the produced reports
and/or graphical information to determine which areas or cells should be optimised.
You can also use problem cell weighting to prioritise actions (changes) to cells that
have shown poor performance, based on the analysis output and/or network
measurements.
For more information, see Identifying Problems in a Network on page 175.
Page 25
Import and spread network data, for example performance engineering data or
traffic data. This cell-specific information is imported into ADVANTAGE and
spread intelligently in the area of interest. The created arrays can describe the
network performance and may highlight problematic areas/cells. They can also be
used directly (in the case of traffic arrays) or indirectly in the analysis or
optimisation.
ADVANTAGE also enables you to use the standard ENTERPRISE traffic
functionality to create/load/modify a traffic array, using either live traffic or
specified traffic.
Load and use area-specific and/or cell-specific data (for example, drive test
measurements) to check the network modelling/performance; tune a propagation
model; generate measurement-based pathloss files in order to influence the
pathloss predictions (and predicted network performance); run a focused analysis
or optimisation (based, for example, on drive test routes).
Optimiser
For more information about the common user interface, see either the ENTERPRISE
User Reference Guide, or the ASSET User Reference Guide.
Page 26
For more information on importing and exporting XML data, see the ENTERPRISE
User Reference Guide.
Page 27
Enables You To
Propagation Models
Terminal Types
Specify the different terminal types and properties needed for subscribers of your network.
Assign the terminal types to different network layers or to multiple layers, and describe their
geographical distribution in relation to the mapping data.
Carriers
Define carriers.
Most radio network systems divide up spectrum into pairs for uplink and downlink communication.
For most technologies, it is convenient to refer to a carrier number which abstracts the absolute
frequency from the description of the carriers. For LTE, the absolute frequencies in terms of MHz
need to be specified.
Carrier Layers:
Define GSM carrier layers, which are sub-sets of the total list of carriers, grouped together under a
common name.
Cell Layers:
Define GSM cell layers, which are logical groups of transceivers on a cell. By using cell layers, you
can distinguish between micro cells and macro cells or between carriers of different frequency
bands.
Bearers
Define bearers that transport voice and data between cells and terminal types.
Services
Define services, and then allocate the services to terminal types, to account for the different
services offered to the subscriber.
For example, services might have different data rates and other requirements such as quality of
service.
Clutter Parameters
Set up clutter parameters, such as different shadow fading standard deviations and indoor losses
for each clutter type. These fades and losses are considered when you run a simulation of network
performance. For some technologies, you can set additional clutter-specific adjustments that
influence, for example, AAS Support.
For more information on any of these menu items, see the ASSET User Reference
Guide.
Enables You To
Array Manager
Traffic
Page 28
Enables You To
Network Data
Coverage/Interference
Define, generate, and analyse customised compound arrays based on the existing available
arrays.
Array Settings
For more information on the four items listed under Network Data, see Using
Measurement Data on page 187.
For more information on the other items, see the ASSET User Reference Guide.
Enables You To
Measurements
Import drive test measurements, perform propagation model analysis, auto-tune the model
parameters and create measurement-based pathloss files (based on the imported data).
Enables You To
Configure technology-specific thresholds for problematic areas. These define the minimum clutterspecific values that are acceptable for the purpose of the analysis.
Identify area problems (such as low coverage, low quality) and/or cell problems (such as large
number of dropped calls, large number of handovers).
Assign problem cell weights, in order to prioritise actions (changes) to cells that have shown poor
performance.
The items on the Problem Identification sub-menu are only available for GSM and
UMTS.
Page 29
Enables You To
Site/Node report
Generate a report that includes any selected contents of the Site Database, based on any filter.
Generate a report containing all cells which use a certain carrier, or range of carriers, according to
the criteria.
Determine which report format you want to use for the associated report type. For more
information, see Selecting Report Formats on page 99.
Enables You To
Optimiser Workflow
The Optimiser Workflow enables you to perform the vast majority of tasks within ADVANTAGE
from a single dialog box. This incorporates the setting up of parameters, costs, constraints and
targets, and generation of optimisation plans.
Plan Manager
RF Array Thresholds
RF Metric Targets
Costs/Limits
Strategy
Traffic
Settings
For more information, see About the Optimiser Workflow on page 33.
ADVANTAGE Wastebasket
Page 30
Setup
During this phase, you need to follow these steps (where applicable):
Choose which status field you want to use to differentiate between new
network elements and existing network elements, if applicable.
Define the Strategy for the optimisation, which includes the selection of which
Metrics are to be used.
Define the Settings, that is, key additional parameters and options.
Define the Action/Unit Costs and other cost-associated options (for example,
Budget).
Page 31
Analysis
During this phase, you can optionally perform these steps:
Review the configuration of any plan or delta plan, by checking the plan
reports (Initial, Delta, Final) and the Action-Constraints.
Apply a plan to the Site Database, using either the Temp Apply/UnApply or
the Apply to Database options.
Optimisation
During this phase, you can use the Plan Manager in the Optimiser Workflow to
perform a number of plan-related operations, including the starting/running of
the Optimiser. You can check the feedback from the Optimiser in terms of:
Cost Details and Graphs - information about the costs related to the
optimisation.
Analysis
During this phase, you can repeat the appropriate steps as described in the
previous Analysis section.
Action
During this phase, you can optionally perform these steps:
Page 32
Apply a plan to the Site Database, using either the Temp Apply/UnApply or
the Apply to Database options.
Start a (secondary) optimisation from a delta plan, by using the Create a New
Plan from a Delta Plan option.
The following table briefly describes the options in the Optimiser Workflow dialog
box:
Option
Enables You To
Plan Manager
RF Array Thresholds
Specify the required RF performance thresholds that will be used for your optimisations
and analyses.
RF Metric Targets
Define the RF performance targets for your optimisations, based on the appropriate
metrics.
Costs/Limits
Set maximum limits, combinations, and costs in terms of budget. This is for actionrelated costs and unit costs.
Strategy
Define major factors that will influence optimisations, such as which metrics will be
optimised, and how those metrics are weighted.
Traffic
Select the list of terminal types to be used in an optimisation, and/or to load cached
traffic arrays.
Page 33
Option
Enables You To
Settings
Set additional parameters and options related to optimisations, analysis and spreading
network data. Also enables you to set the array-based settings, and the settings for
Auto Plan Setup.
Financial Analysis
Assess and plan for the revenue potential of your network. This licensed module can
help you make informed network planning decisions, particularly if integrating new sites
into an existing network.
See the Financial Analysis User Reference Guide.
The tab names and options within the Optimiser Workflow vary slightly
according to the technology that you are using.
For more detailed information about the options in this dialog box, see:
Prediction Resolutions
For performance reasons, prediction resolutions for individual cells should be set
so that they match the resolution at which the analysis or optimisation is being
performed. Ideally, the predictions should already be available at the specified
map data resolution, before performing an analysis or optimisation.
Page 34
You can use the following list of guidelines in order to maximise the ability of the
optimisation algorithm to find an optimised network configuration quickly:
Concentrate on the region and cells of interest. Use the Plan Wizard to specify the
region and cells of interest, and ignore areas or cells that should not be part of the
optimisation.
Restrict the optimisation calculations to vectors and/or drive test routes (if possible). Use
the option in the Plan Wizard (or the Edit Vectors right-click option) to restrict the
optimisation array and cost calculations to specific vectors and/or drive test
routes.
Do not use a higher array resolution than required. If you can get realistic network
performance results by specifying a low resolution for the optimisation, there is no
point in using a higher resolution.
Restrict the number of servers/cells considered for array generation. If you can get
realistic results (for example, with respect to interference) by specifying fewer
servers/cells for the optimisation, there is no need to use more.
Limit the optimisation cost calculations to a lower number of servers/cells (if appropriate).
Use the Servers/Cells per Pixel option on the Strategy page of the Optimiser
Workflow to do this.
Focus on problematic cells/areas. Use read-only filters (for network objects that
should be considered, but not modified) and/or the Problem Cells options to
ensure that the Optimiser concentrates on cells that are performing badly.
Do not under- or over-constrain the optimisation problem. Make sure that the specified
actions/constraints are reasonable, so that inappropriate configurations are not
evaluated, but also flexible enough to allow the Optimiser to produce the best
possible plan.
Fine-tune the algorithm. The nature of the algorithm is general enough to apply to a
wide range of optimisation problems. Although the algorithm can be fine-tuned
per specific scenario to further maximise its efficiency (the algorithmic fine-tuning
depends on the setup and user permissions), it is not an easy task and must be
approached with caution.
Page 35
To do this:
1
In the dialog box that appears, select the (Property-based) filter that you want to
use.
Select the site or node template that you want to apply to the filter.
Click OK.
Remember to click back on the ADVANTAGE or ASSET tab afterwards.
You have now applied an instance of the template (that is, a new site or node) to
every Property in the filter.
The new sites/nodes will be added in the Site Database under the newly created
separate PLMN.
Page 36
CHAPTER 3
About Action-Constraints
The purpose of action-constraints in ADVANTAGE is to allow certain network
parameter changes to be considered in a network optimisation, but at the same time
impose meaningful limitations and restrictions on those changes, in order to
accurately represent the real-world environment.
An example of an 'action' may be that you want to allow the antenna azimuths for a
group of cells to be changed, but, at the same time, you might want to specify a
'constraint' for one of those cells, which could be a forbidden azimuth range because of
a nearby school.
The ADVANTAGE tool focuses on automatic optimisation of plans, and the
Action-Constraints dialog box plays a crucial part in this process. This chapter focuses
on the Action-Constraints within the Site Database. For more detailed information
about the plan-specific Action-Constraints dialog box within the Optimiser Workflow,
it is important that you read the chapter Setting Action-Constraints for Plans on page
121.
Action-constraints that you can set up and edit within the Optimiser Workflow
Action-constraints that you can set for specific network elements directly within
the Site Database
Page 37
Set specific action-constraints in the Site Database, and then edit these actionconstraints (if required) and set up further action-constraints (if required) in the
Action-Constraints dialog box.
- or -
Object
Action-Constraint
Grid Constraints
Property
Grid Constraints
Property
Grid Constraints
Site or Node
If you do set any of the above action-constraints in the Site Database, when you next
create a plan, you will be able to view them in the Action-Constraints dialog box, in a
read-only state. Whether they are used in an optimisation depends on whether you
choose to use the Grid planning mechanism.
Page 38
Network Element
Constraints
Equipment
Property
Antenna, Grid
GSM Site
Installation, Grid
GSM Cell
Antenna
GSM Subcell
Power
UMTS Node
UMTS Cell
CDMA2000/EV-DO Site
Antenna, Grid
WiMAX Node
Antenna, Grid
Network Element
Constraints
WiMAX Cell
Power
LTE Node
Antenna, Grid
LTE Cell
Power
You can also edit a number of constraints in the Site Database simultaneously, as
described in Configuring Constraints in the Site Database Global Editor on page 54.
In the dialog box that appears, select the mast that you want to constrain.
Select the required mount option - if you select Rooftop, the building height of
the Property will be added to the mast height to give the antenna height
Click the Constraints tab, and specify the mast heights that you want to make
available:
In the Available Masts Height pane, type in a height value and click Add
To change a value, select it and enter a new value in the box and click Update
Page 39
BTS Types
To configure equipment-specific constraints for BTS types:
1
In the dialog box that appears, select the BTS type that you want to constrain.
Click the Parameters tab, and in the PA Output Power pane, select a cell layer and
enter the minimum and maximum PA Output power values that the BTS can
provide. This picture shows an example:
These constraints are only used if these equipment types are assigned to the
relevant network elements in the Site Database. For example, masts are assigned to
Properties (all technologies), and BTS equipment types are assigned to GSM sites.
Page 40
Select a Property, and click the Physical Antennas tab. This picture shows an
example:
Ensure that you select the appropriate antenna from the list (if there is more than
one).
Use the scroll bar to scroll to the right, to reveal the antenna constraints (Height
Fixed, Azimuth Fixed, and so on). This picture shows an example:
You can activate the following constraints per antenna, if you want to prevent
such changes during optimisation:
Height Fixed
Azimuth Fixed
Device Fixed
You can, if required, define a Forbidden Azimuth Range for the cell's antenna.
This enables you to define an orientation range which the automatic optimisation
cannot consider for azimuth changes.
To set the range, specify a clockwise bearing (the start azimuth for the forbidden
range) and an anti-clockwise bearing (the end azimuth for the forbidden range).
For a fuller description of these settings, see About the Forbidden Azimuth
Range on page 130.
You can activate and set the following constraints per antenna, if you want to
enable such changes during optimisation:
Page 41
Select a Property, and click the Antenna Constraints tab. This picture shows an
example:
In the Antenna Height Rules pane, enter the minimum and maximum height
values that you wish to use as a basis for the antenna constraints defined on this
tab.
To manually define a series of allowable antenna height values within the
minimum-maximum range:
Page 42
Select the Manual option, and then select the Constrain checkbox.
In the value box above the Add button, type the first value in metres.
Click Add.
Add further values as required - to delete a value, select it and click Remove.
To edit a value, select it, change the value and then click Update.
To define a series of allowable antenna height values within the minimummaximum range based on the mast associated with the Property (which is defined
on the General tab of a Property in the Site Database):
Select the Mast option, and then select the Constrain checkbox.
The constraint values that you have defined for this mast appear. For more
information on this, see Configuring Equipment Constraints on page 39.
To define a series of allowable antenna height values within the minimummaximum range based on a particular step size:
Select the Step option, and then type a value in metres for the step.
A series of allowable antenna height values appears, starting with the defined
minimum height, then moving upwards in steps (according to the size you
defined) to the defined maximum height.
For example, the allowable height values for a minimum height of 20m and a
maximum of 30m with a step size of 2m would be 20, 22, 24, 26, 28, and 30m.
4
In the Height Variation pane, you can determine whether the heights for
individual antennas may differ at a specific Property (this option is cell layerspecific for GSM). To do this, select the Allowed checkbox.
If this is not selected, all antennas on the same cell layer (GSM) or on all
carriers (UMTS) at this Property must be at the same height. However, GSM cells
for different cell layers, or cells of different technologies (for example, GSM and
UMTS) can still have antennas with heights different from each other.
In the Antennas at Same Height pane, you can specify a minimum azimuth
difference. This is the minimum separation (in degrees) that you are willing to
accept between antennas of the same height on this Property. To do this, select the
Constrain checkbox and type a value.
In the Antenna Co-location pane, select the Enable Co-location checkbox if you
want to enable antenna devices to be able to share co-location parameters
(identical location co-ordinates, height and azimuth, and on the same Property).
If Antenna Co-location is not enabled for a Property, no antenna sharing or
co-location configuration can be accepted as a valid starting configuration or
examined as a potential optimisation solution by the Optimiser. For more
information, see How the Optimiser Considers Shared Antennas on page 142.
Page 43
Select
To
Nominal
Candidate
Click in the Name field and type the ID of another Property already defined in
the Site Database:
(The co-ordinate values are auto-populated after you press the Enter key.)
- or
Click in the appropriate column and type co-ordinate values (in GRID, DLL, or
LL as appropriate).
Page 44
If required, you can constrain the Optimiser to consider only the current position
of the Property (whether candidate locations are available or not), by selecting
'Location Fixed'.
This picture shows an example, where three possible candidate locations have been
defined:
If you need to delete a candidate location, select the location and click Delete.
If you have specified any Property IDs, the Optimisation Status on the Grid
Constraints tab of the specified candidate Property is auto-updated to 'candidate'.
Page 45
In the ACP Constraint pane, select the Fix Site Equipment checkbox if you want
the specified BTS equipment type to stay unchanged during a GSM power
optimisation.
If You Want To
Ensure that this site is always used in every solution the Optimiser generates. This means that the
site will never be completely 'switched off' during optimisations.
Prevent the sector configuration for a site from changing during optimisations.
Page 46
In the Min. Sectors and Max. Sectors fields, type the required number of sectors.
Click Generate.
If you need to delete a configuration, select it and click Remove. To delete all
configurations, click Remove All.
Page 47
Ensure that you select the appropriate antenna by selecting the required slot from
the Antenna Configuration pane:
These slot numbers correspond to the antennas listed on the Antennas tab. The
constraints are always antenna-specific.
4
In the Misc Constraints pane, you can activate the following constraint per
antenna slot, if you want to prevent such changes during optimisation:
You can also activate and set the following constraints per antenna slot, if you
want to enable such changes during optimisation:
Page 48
In the ACP Constraint pane, select the Fixed PA Output checkbox if you want to
prevent changes to the PA output by the Optimiser during optimisation.
Ensure that you select the appropriate antenna by selecting the required antenna
number from the Antenna Configuration pane:
These numbers correspond to the antennas listed on the Antennas tab. The
constraints are always antenna-specific.
4
In the Misc Constraints pane, you can activate the following constraint per
antenna, if you want to prevent such changes during optimisation:
You can also activate and set the following constraints per antenna, if you want to
enable such changes during optimisation:
Page 49
If You Want To
Ensure that this site is always used in every solution the Optimiser generates. This means that
the site will never be completely 'switched off' during optimisations.
Prevent the sector configuration for a site from changing during optimisations.
Page 50
In the Min. Sectors and Max. Sectors fields, type the required number of sectors.
Click Generate.
To delete a configuration, select it and click Remove. To delete all configurations, click
Remove All.
Page 51
In the ACP Constraint pane, select the Fix Node Type checkbox if you want the
specified Node type to stay unchanged during a power optimisation.
Page 52
The power that is dedicated to the Pilot, Control, Synchronisation and Indicator
channels
HSDPA power
In the TX Power Limits pane, under ACP Constraint, select the Fixed checkbox.
Page 53
Select the items that you want to change for the network elements in this filter. For
a list of the ADVANTAGE-specific constraints, see ADVANTAGE-specific
Constraints in the Global Editor on page 55.
Here is an example of the constraints in the Global Editor:
Where a parameter has two checkboxes, ensure you select both if you want to
set the relevant constraint. However, if you want to disable (previously set)
constraints, you can select the first checkbox, and clear the second checkbox. In
simple terms, the first checkbox determines whether the change is to be made, and
the second checkbox determines what is to be changed. For example:
To set the constraint
Page 54
Properties
Cell Constraints
Property Constraints
Antennas:
Allow Co-location
Min Height
Max Height
Grid Constraints:
Optimisation Status
Location Fixed
Heights Used
Site Constraints
Grid Constraints:
Min Sectors
Max Sectors
Generate Configurations
Fixed PA Output
Fixed TX Power
Fixed TX Power
Page 55
Page 56
CHAPTER 4
Setting Up Thresholds,
Targets and Parameters
The Optimiser Workflow enables you to perform the vast majority of tasks within
ADVANTAGE from a single dialog box. This incorporates the setting up of
parameters, costs, constraints and targets, and generation of optimisation Plans.
It comprises a number of main options in the left hand pane, and each of these enables
you to access a range of specific options that are displayed in the right-hand pane.
This chapter focuses on the thresholds, parameters and settings, which are crucial to
the optimisation engine. In addition to setting the thresholds and metric targets, it is
here that you specify which strategy you will use for your optimisations and analyses.
These steps, in particular the ones related to the radio environment setup, are
probably not relevant to the general user, assuming that the administrator (or superuser) has already completed them. This is also true for optimisation scenarios that
have been set up by one user that can be shared with other users who access the same
project.
To start the Optimiser Workflow:
From the Optimiser menu, click Workflow
- or Click the
Page 57
The RF (radio frequency) array thresholds in the Optimiser Workflow enable you to
specify:
These thresholds determine the required RF performance for your optimisations and
analyses.
These thresholds are used by the array-based optimisation cost mechanism (they
are not used by the service-based cost mechanism).
In the RF Array Thresholds, you can configure clutter-specific thresholds that define
the current or required performance of your network. This enables you to specify and
use minimum signal strength, signal quality, and dominance thresholds for chosen
clutter types.
These thresholds are evaluated when running optimisations and performing an
analysis.
This picture shows an example of the Clutter Thresholds:
Page 58
If you have multiple cell layers (GSM) or multiple carriers (all other
technologies), you can evaluate your network at a 'per layer' or 'per carrier' level
(rather than 'per technology'). There is a Per Layer Calculation option in the Settings
(Options tab) which enables you to activate the 'per layer/carrier' tabs in the RF
Thresholds. See About the Options Tab on page 87.
This picture shows an example of 'Per Layer' Clutter Thresholds:
on the main
Specify the threshold values as required in the columns for the appropriate clutter
types. The following table describes them:
Technology
Parameter
Description
GSM
RSS
UMTS
RSCP
CDMA/EV-DO
RSCP
Fixed WiMAX
DL RSS
Mobile WiMAX
Preamble RSS
LTE
RSRP
GSM
CINR
UMTS
Pilot Ec/Io
CDMA/EV-DO
Pilot Ec/Io
Fixed WiMAX
DL CINR
Mobile WiMAX
Preamble CINR
LTE
RSRQ
Page 59
Technology
Parameter
Description
GSM
Polluters
UMTS
Pilot Polluters
CDMA/EV-DO
Pilot Polluters
LTE
Dominance Interferers
Copying and Pasting single or multiple values within the dialog box
All changes that you make on this page are automatically saved to the database in
the Applied state, and the changes will persist when you close the Workflow
dialog box.
However, if appropriate, you can carry out one of the following actions:
If you want to restore the options on this page to the previous committed state
(if such a state exists), click Restore
If you want to share the changes on this page with all other users, click
Commit
on the main
On the General Clutter Parameters tab, specify the parameters as required in the
columns for the appropriate clutter types. The following table describes the
parameters:
Parameter
Description
Sample
Determines whether cost function sampling is applied to the clutter type. This
sampling is a calculation process using only a subset of the total pixels during
optimisation. The process 'removes' neighbouring pixels of the same clutter type,
and therefore makes the optimisation faster.
Sampling is only recommended if your mapping resolution is high (under 50m) and
you want to optimise a large area.
You can display the subset of pixels on the map View. See About the
Sampling Option on page 116.
Page 60
Parameter
Description
Importance
The importance of the corresponding clutter in terms of traffic density. The higher
the importance of the clutter, the higher the traffic density levels for this clutter type,
and vice versa.
If required, you can change all values in a column by editing one row and then
double-clicking on the column heading.
In the RF Array Thresholds, you can configure vector-specific thresholds that define
the current or required performance of your network. This enables you to specify and
use minimum signal strength, signal quality, and dominance thresholds for chosen
vectors.
These thresholds are evaluated when running optimisations and when performing an
analysis.
The Override checkbox not only enables you to edit the values, but also activates
the vector thresholds. Conversely, if unselected, the vector thresholds are not active.
Therefore, you should always bear this in mind before you run an optimisation or
perform an analysis.
When selected, vector thresholds will always have a higher priority than clutter
thresholds (in the pixels that are intersected by your chosen vectors).
This picture shows an example of the Vector Thresholds:
Page 61
If you have multiple cell layers (GSM) or multiple carriers (all other
technologies), you can evaluate your network at a 'per cell layer' or 'per carrier' level
(rather than 'per technology'). To activate the per layer/carrier tabs in the RF Array
Thresholds, on the Options tab in the Settings page, select the Per Layer Calculation
option. See About the Options Tab on page 87.
This picture shows an example of 'Per Cell Layer' Vector Thresholds:
Page 62
Click the Select Vectors button, and in the dialog box that appears, choose the
vectors for which you would like to configure parameters, then click OK.
Specify the values as required in the columns for the appropriate vectors. The
following tables describe the thresholds:
Technology
Parameter
Description
All
Priority
You can specify the relative priority of the chosen vectors. This
will determine which parameters are to be used at locations with
intersecting vectors. To raise the priority of a vector, select it,
then drag and drop it to the required priority position.
GSM
RSS
UMTS
RSCP
CDMA/EV-DO
RSCP
Fixed WiMAX
DL RSS
Mobile WiMAX
Preamble RSS
LTE
RSRP
Technology
Parameter
Description
GSM
CINR
UMTS
Pilot Ec/Io
CDMA/EV-DO
Pilot Ec/Io
Fixed WiMAX
DL CINR
Mobile WiMAX
Preamble CINR
LTE
RSRQ
GSM
Polluters
UMTS
Pilot Polluters
CDMA/EV-DO
Pilot Polluters
LTE
Dominance Interferers
Copying and Pasting single or multiple values within the dialog box
Leave the Override checkbox selected if you want these thresholds to be active for
your optimisations. You can deactivate them at any time, by deselecting the
checkbox.
All changes that you make on this page are automatically saved to the database in
the Applied state, and the changes will persist when you close the Workflow
dialog box.
However, if appropriate, you can carry out one of the following actions:
If you want to restore the options on this page to the previous committed state
(if such a state exists), click Restore
If you want to share the changes on this page with all other users, click
Commit
Page 63
These parameters enable you to define targets for optimisations and analyses. These
targets correspond to metrics that can be defined separately for each cost mechanism
(array-based and service-based).
The metric targets may vary according to the technology that you are using.
Coverage:
The required array-based coverage (target, minimum and multiplier) for the
clutter type.
Coverage target calculations are based on signal strength level alone (such as
RSS).
Quality
The required array-based quality (target, minimum and multiplier) for the
clutter type.
Quality target calculations are based on either the quality level alone (such as
CINR) or on both quality level AND signal strength (for example, CINR and
RSS together), depending on your preferred basis for this metric. For more
information, see Specifying the Settings on page 86.
Page 64
Dominance
The number of servers (target, minimum and multiplier) for the clutter type.
Dominance target calculations are based on the appropriate dominance or
pilot polluters array.
This metric is not available for all technologies.
The following table describes the targets that can be defined for each technology.
They can be separately defined for traffic and area:
Technology
Target Metrics
Coverage
Quality
Dominance
GSM
RSS
CINR
Polluters
UMTS
RSCP
Pilot Ec/Io
Pilot Polluters
CDMA2000/EV-DO
RSCP
Pilot Ec/Io
Pilot Polluters
LTE
RSRP
RSRQ
Dominance Interferers
Fixed WiMAX
DL RSS
DL CINR
- not applicable -
Mobile WiMAX
Preamble RSS
Preamble CINR
- not applicable -
Multiplier - multiplier factor (cost penalty) if the minimum is not achieved (default
is 1)
Specify the required values in the appropriate columns for each of your clutter
types.
on the main
Page 65
Copying and Pasting single or multiple values within the dialog box
All changes that you make on this page are automatically saved to the database in
the Applied state, and the changes will persist when you close the Workflow
dialog box.
However, if appropriate, you can carry out one of the following actions:
If you want to restore the options on this page to the previous committed state
(if such a state exists), click Restore
If you want to share the changes on this page with all other users, click
Commit
Page 66
Served Terminals
Uplink Throughput
Downlink Throughput
The available metric targets may vary according to the technology that you are
using. For example, for GSM or WiMAX, the Handover metrics are not applicable.
For each metric target, you can use:
Averaged Cost Calculation - This averages the sum of calculated costs (considered
in the optimisation) for all the groups for the appropriate metric, based on the total
number of groups assigned to it.
Weighted Cost Calculation - This weights the calculated cost (considered in the
optimisation) for each group for the appropriate metric, based on the groupspecific terminal attempts or served terminals or targeted throughput (as
applicable).
In terms of the optimisation, the only time the Averaged/Weighted options will
make a difference to the results is when you have multiple groups assigned to a
metric. If that is not the case, they can be considered to be exactly the same.
There are three stages to configuring the service-based metric targets:
If you want to set the same target values for all your services (per metric), it is a
simple process to place them in the same group, and specify a common set of
target values.
If you want to specify target values independently for each service (per metric),
you should ensure you place each service in a separate group.
Page 67
Ensure that you have already defined all your services and associated parameters.
For information on defining services, carriers, cell layers, terminals and bearers,
see the ASSET User Reference Guide.
In the Group Edit dialog box, name the group, and select the appropriate service,
as in this example:
Click the right-arrow button. The service (and its associated carriers or cell layers)
is shown in the right pane. In this example only one service has been selected, but
you can select more if required:
on the main
Target values are specified per group. Therefore, if you want to specify target
values independently for each service, you should keep them in separate groups.
8
When you have finished editing the group, you can continue adding or editing
any other groups according to your requirements.
If you want to share specific group changes with all other users of the project, click
Commit, or to share all group changes, Commit All.
Page 68
In the right-hand pane of the Optimiser Workflow, highlight the required metric for example, Served Terminals (Averaged).
From the Groups available pane, select a group and click the right-arrow button.
The group appears in the Groups in-use pane, and will be associated with the
respective target.
If appropriate, you can assign more than one group to a metric. If you do this, you
should check whether you want to use the Averaged or Weighted metric, as
explained in About the Targets for Service-based Metrics on page 66.
Click OK.
If a group has already been assigned to one of the metrics, you can quickly copy
that same group to another metric by selecting it, and then dragging and dropping it
onto another metric.
Page 69
If the target group is assigned to more than one metric, ensure you select the
correct one, because the target values are independent between the metrics.
The target group values appear:
Depending on the target group, you can edit some or all of the following values:
Value
Description
Min
Target
Target value
Max
Multiplier
All changes that you make on this page are automatically saved to the database in
the Applied state, and the changes will persist when you close the Workflow
dialog box.
However, if appropriate, you can carry out one of the following actions:
If you want to restore the options on this page to the previous committed state
(if such a state exists), click Restore
If you want to share the changes on this page with all other users, click
Commit
The Commit All and Restore All buttons are useful if you have edited a large
number of targets.
Page 70
Specifying Costs/Limits
The Costs/Limits in the Optimiser Workflow enable you to:
If you select the option to reject plans based on these limits, the optimiser will not
accept any optimisation states (apart from the starting plan state) that exceed these
limits.
This picture shows an example where limits have been set on the number of Antenna
Units and the number of Property Units. Any optimisation state that exceeds either of
these limits would be rejected.
Page 71
on the main
All changes that you make on this tab are automatically saved to the database in
the Applied state, and the changes will persist when you close the Workflow
dialog box.
However, if appropriate, you can carry out one of the following actions:
If you want to restore the options on this tab to the previous committed state
(if such a state exists), click Restore
If you want to share the changes on this tab with all other users, click Commit
You can turn this plan rejection method On/Off by using the 'Reject Plans Based
On Max Actions/Units' checkbox (the individual selections and limits are still stored).
Location
Property
Site
Cell
All actions
Only remote actions (actions not requiring a visit to the site, such as changes to
remote adjustable antennas)
You may then specify whether power actions are to be considered as remote actions
or as visit actions (however, BTS and Node Type actions are always considered as
visit actions).
Page 72
on the main
All changes that you make on this tab are automatically saved to the database in
the Applied state, and the changes will persist when you close the Workflow
dialog box.
However, if appropriate, you can carry out one of the following actions:
If you want to restore the options on this tab to the previous committed state
(if such a state exists), click Restore
If you want to share the changes on this tab with all other users, click Commit
The example below specifies that all Visit Actions per Location (including power
actions in this case) will be combined:
Page 73
Properties
Sites
Cells
Antenna devices
And, for example, Action-related costs for the number of changes involving:
Antenna azimuth
Mechanical downtilt
GSM PA Output
WiMAX TX Power
If you also have the Financial Analysis module installed, when you run an
analysis or optimisation, these costs are included in the 'Expenditure' metric, in
addition to any specified financial (CAPEX/OPEX) costs. For more information, see
the Financial Analysis User Reference Guide.
To define costs for units and actions:
1
on the main
Expand the required category (Combined, Antenna, Power or Grid), then expand
the appropriate action or unit, and then expand Budget.
For more information about the combined category, see Defining Combinations of
Actions on page 72.
To expand or shrink any of the trees, select an object and press the * or - key, or
if you are using a laptop computer, press the Fn and * or - keys.
Page 74
In the appropriate Values column, double-click a value and edit the Cost, as
required.
This picture shows an example:
All changes that you make on this tab are automatically saved to the database in
the Applied state, and the changes will persist when you close the Workflow
dialog box.
However, if appropriate, you can carry out one of the following actions:
If you want to restore the options on this tab to the previous committed state
(if such a state exists), click Restore
If you want to share the changes on this tab with all other users, click Commit
Azimuth
Mechanical Downtilt
Height
Pattern (remote adjustable electrical Changes to the electrical downtilt of the antenna, where the adjustment can be
downtilt)
performed remotely.
In the Cellular Antennas dialog box, on the Info tab, you can specify how the
pattern can be adjusted. If an antenna used on a cell is set to 'Remote', the
Optimiser considers this action as a remote adjustment.
Pattern (site adjustable electrical
downtilt)
Changes to the electrical downtilt of the antenna, where the adjustment requires a
site visit.
In the Cellular Antennas dialog box, on the Info tab, you can specify how the
pattern can be adjusted. If an antenna used on a cell is set to 'Swap' or 'Switch', the
Optimiser considers this action as an onsite adjustment.
Device
Page 75
This Parameter
Antenna Unit
For Power
This Parameter
PA Output
BTS Type
HSDPA Power
Changes to all of the UMTS cell power settings described above (including
HSDPA).
Node Type
For Grid
This Parameter
Property Unit
Property
Site Unit
Site
Cell Unit
Cell
For Property Unit, Site Unit and Cell Unit, this represents the (generic) financial
burden that may be imposed by changes to the respective total numbers of
Properties/sites/cells in an optimised plan.
Page 76
For Combined
This Parameter
Location
Combined changes (such as the antenna device or azimuth) to the network objects
in a location.
Property
Combined changes (such as the antenna device or azimuth) to the network objects
on a Property.
Site
Combined changes (such as the antenna device or azimuth) to the network objects
on a site.
Cell
Combined changes (such as the antenna device or azimuth) to the network objects
on a cell.
Multiplier value
on the main
All changes that you make on this tab are automatically saved to the database in
the Applied state, and the changes will persist when you close the Workflow
dialog box.
However, if appropriate, you can carry out one of the following actions:
If you want to restore the options on this tab to the previous committed state
(if such a state exists), click Restore
If you want to share the changes on this tab with all other users, click Commit
Page 77
Select the Metrics to be used in the optimisation and set their weightings
These parameters enable you to define the factors that will influence optimisations.
The strategy options may vary according to the technology that you are using.
If you have multiple cell layers (GSM) or multiple carriers (all other technologies)
in your network, you can select and weight the Performance components at a 'per
layer' or 'per carrier' level. The Per Layer Calculation option in the Settings (Options
tab) enables you to activate these levels. See About the Options Tab on page 87.
Page 78
on the main
In the case of the RF category, expand the cost mechanism, metric, technologies,
and layers (if enabled), as appropriate.
5
For each selected item, double-click the Weight value, and edit it as required (the
corresponding % columns update automatically).
The weightings always total 100% for items that share the same hierarchical
level, are parented to the same item, and are selected.
10 In the Pixel Weighting pane, specify whether the calculation of the optimisation
costs should consider area only, traffic only or both combined. To do this, type a
value in the % Traffic box to define the weighted importance of traffic-specific
calculations for the optimisation; the % Area value is then automatically updated.
The pixel weightings affect the array-based cost mechanism only (in other
words, the service-based cost mechanism is always only traffic-based).
11 In the Mechanism Technologies pane, select the technologies for which you want
the metrics/weightings to be used. You can also specify, as appropriate:
Maximum number of servers (GSM only) - the number of cells that are
considered as covering cells and interferers.
Number of covering cells (all other technologies) - the number of cells that are
considered as primary covering cells, handover cells (if appropriate) and
interferers.
All changes that you make on this tab are automatically saved to the database in
the Applied state, and the changes will persist when you close the Workflow
dialog box.
ADVANTAGE 8.1 User Reference Guide
Setting Up Thresholds, Targets and Parameters
Page 79
However, if appropriate, you can carry out one of the following actions:
If you want to restore the options on this tab to the previous committed state
(if such a state exists), click Restore
If you want to share the changes on this tab with all other users, click Commit
If you have multiple cell layers (GSM) or multiple carriers (all other technologies)
in your network, you can specify the Performance degradation thresholds at a 'per
layer' or 'per carrier' level. The Per Layer Calculation option in the Settings (Options
tab) enables you to activate these levels. See About the Options Tab on page 87.
All the options are independent. For example, you could choose to select 'Arraybased' without also selecting 'RF', and you could select 'Coverage' without also having
to select 'Array-based'. Alternatively, you could choose to prevent the 'Array-based'
category degrading too much without specifying thresholds on any individual subcategories (such as Coverage or Quality). Each selected option would have an
influence on the optimisation process.
To set a threshold:
Page 80
on the main
For each item, you can choose to set the threshold as an ABSOLUTE degradation
of the starting cost value, or as a RELATIVE (%) degradation of the starting cost
value.
You can change from one to the other by clicking the appropriate row in the Max
Degradation column, and using the drop-down box.
For example, if you have a starting cost value of 20:
A relative (%) threshold of 10 would mean that configurations with costs =< 22
(for that metric) would be considered
If you want to restore the options on this tab to the previous committed state
(if such a state exists), click Restore
If you want to share the changes on this tab with all other users, click Commit
You can turn this plan rejection method On/Off by using the 'Reject Plans Based
On Metric Degradation' checkbox (the individual selections and thresholds are still
stored).
Page 81
Metric Multipliers
These enable you to normalise the units used for the different metric categories, so
that the respective units can be considered in the optimisation on a common basis (the
RF cost category does not really refer to a specific measurable unit; it is an abstract
number or percentage).
The multiplier values indicate the scale used to represent the following parameters:
The way that you define the multipliers will have a significant impact on the
optimisation. You should ensure that all of the values are correct before proceeding.
For example, suppose you are using the Budget and RF metrics in an optimisation,
and the budget represents Euros. If you know or assume that 10,000 Euros of
expenditure is equivalent to an RF cost of 1 unit, then the multiplier values should be
1 for Budget, and 10,000 for RF.
Page 82
Metrics Prioritisation
This enables you to determine how the metrics and multipliers are considered in the
optimisation.
You can select one of these options:
Option
Description
All the metrics selected and weighted on the Metrics Selection/Weights tab will
be considered in each optimisation iteration.
Only the worst performing overall metric (Budget, Financial or RF) will be
considered in each optimisation iteration.
on the main
Double-click the multiplier value(s) that you want to edit, and type the new
value(s).
If you want to restore the options on this tab to the previous committed state
(if such a state exists), click Restore
If you want to share the changes on this tab with all other users, click Commit
Page 83
These options are relevant if you want to consider traffic in your optimisations.
Even if you do not consider traffic, you still need to specify a Reference Terminal
type. You can do this on the Metrics Selection/Weights tab of the Strategy page.
on the main
Select (or view) the required terminal type(s) from the list displayed.
All changes that you make on this tab are automatically saved to the database in
the Applied state, and the changes will persist when you close the Workflow
dialog box.
However, if appropriate, you can carry out one of the following actions:
Page 84
If you want to restore the options on this tab to the previous committed state
(if such a state exists), click Restore
If you want to share the changes on this tab with all other users, click Commit
on the main
In the dialog box that appears, select the Use Advantage Traffic checkbox to
enable the use of the arrays that are selected in the Cached Traffic Arrays pane.
Select the Use Cell Traffic Offset Values checkbox if you want to use these
values in optimisations, analyses and problem cell identification.
5
Right-click the required traffic array and select Load Ticked Traffic Arrays.
The selected arrays are loaded into memory.
From the Arrays menu, click Array Manager, and select the required arrays.
For more information on using the Array Manager, see the ASSET User Reference
Guide.
Page 85
Specify the parameters and options that relate to the Auto Plan Setup method of
creating an optimisation plan
Choose which network element status field you want to use to represent new cells
in your project
The settings options may vary according to the technology that you are using.
Page 86
on the main
Set the required options for the appropriate technology, as described in the
following section.
All changes that you make on this tab are automatically saved to the database in
the Applied state, and the changes will persist when you close the Workflow
dialog box.
However, if appropriate, you can carry out one of the following actions:
If you want to restore the options on this tab to the previous committed state
(if such a state exists), click Restore
If you want to share the changes on this tab with all other users, click Commit
If You Want To
Only consider:
CINR (GSM)
RSRQ (LTE)
Shared Antenna
Device/Pattern ID Variation
Modification Strategy
Page 87
If You Want To
Grid Planning
Workflow Display
The settings options vary according to the technology that you are using.
Page 88
on the main
Set the required options for the appropriate technology, as described in the
following section.
All changes that you make on this tab are automatically saved to the database in
the Applied state, and the changes will persist when you close the Workflow
dialog box.
However, if appropriate, you can carry out one of the following actions:
If you want to restore the options on this tab to the previous committed state
(if such a state exists), click Restore
If you want to share the changes on this tab with all other users, click Commit
Description
Number of Snapshots
A snapshot represents an individual component within the simulation process. For each
snapshot, specified densities of user terminals are positioned in statistically determined
locations. The ability of each terminal to make its connection to the network is calculated
through an iterative process. The performance of the network is then analysed from the
averaged results.
Set the Max. Power Change (%) convergence parameter to set the 'stabilisation' target for
each snapshot. This limits the number of iterations per snapshot.
If the percentage change in total uplink and total downlink interference (summed over all
cells) changes by an amount smaller than this target value for 15 consecutive iterations, then
the iterations are deemed to have converged.
If you want to only scan pixels where traffic exists (a valid traffic raster must be in memory),
select YES.
The simulation can calculate the average number of 'polluting cells' at any location, as
determined by the threshold that you set here (x dB).
This threshold determines the relative margin below the best server within which a cell
qualifies as a polluter.
The exact definition of polluting cells for GSM in ASSET is:
The number of cells (from any cell layer) providing an RSS level within x dB of the best RSS.
The threshold is relative. The default value is 40 dB.
Page 89
Parameter
Description
Best Server:
Use Priorities and Offsets
If you want to consider any priorities that have been set in the Cell Layers dialog box, and the
signal offsets, when determining the better serving sub-cells, select YES.
If this is set to NO, the best server results are based on signal strength alone.
Best Server:
Override Sub-Cell specific
values
If you want to use generic values for Signal Threshold and TA Threshold, select YES, and
then specify the two generic values.
Select 'Snapshots' if you want the traffic-loading of the cells to be calculated by the Simulator
by running snapshots.
If this is set to NO, the best server results are based on the Signal Threshold and TA
Threshold set specifically for each sub-cell on the General tab of the Site Database.
Select '100% Load' if you want to model a fully loaded network (without running snapshots).
Per Carrier Analysis:
Carrier Number
If you want to restrict the serving sub-cells to those that have been assigned a specific
carrier, select YES in the Per Carrier Analysis parameter, and then specify a number in the
Carrier Number.
You can select what type of interference you want to be considered for the interference
arrays, in terms of Co- and/or Adjacent channels.
You can set the value for adjacent channel offset which is used to calculate interference.
If you want to scale the interference levels by the Fractional Load of the interferer when
generating interference arrays, select YES.
If you want to add a gain to the serving cell signal to simulate the diversity improvement in
C/I (related to the number of hopping frequencies), select YES.
Use DTX
If you want to use DTX factors when creating interference arrays, select YES.
If you want to scale the interference levels by the Antenna Hopping gain, (where enabled on
the cells), select YES.
Description
Number of Snapshots
A snapshot represents an individual component within the simulation process. For each
snapshot, specified densities of user terminals are positioned in statistically determined
locations. The ability of each terminal to make its connection to the network is calculated
through an iterative process. The performance of the network is then analysed from the
averaged results.
Intra-Site Correlation Coefficient The correlation between fades (for a terminal) to cells on the same node.
Inter-Site Correlation Coefficient The correlation between fades (for a terminal) to cells on different nodes.
Max Power Change (%)
Set the Max. Power Change (%) convergence parameter to set the 'stabilisation' target for
each snapshot. This limits the number of iterations per snapshot.
If the percentage change in total uplink and total downlink interference (summed over all cells)
changes by an amount smaller than this target value for 15 consecutive iterations, then the
iterations are deemed to have converged.
Page 90
If you want to only scan pixels where traffic exists (a valid traffic raster must be in memory),
select YES.
Parameter
Description
The simulation can output an array that shows the average number of pilot polluters at any
location, as determined by the threshold that you set here (x dB).
This threshold determines the relative margin below the best Ec/Io within which a cell qualifies
as a pilot polluter.
The exact definition of pilot polluters for UMTS in ASSET is:
The number of cells not in the active set, but providing an Ec/Io level within xdB of the best
Ec/Io in the active set. The threshold is relative. The default value is 6 dB.
The error due to imperfect power control in dB, which can be used to influence the simulation
results. It is recommended that this parameter is set to zero.
In a real network, imperfect power control produces a (log-normal) distribution of achieved
Eb/No values for successfully served terminals. One consequence might be a higher uplink
noise rise. If a non-zero value is entered here, the simulation models this effect by including
uncorrelated log-normal errors on the UL and DL transmit powers. Errors are applied only after
all other handover gains and margins have been considered.
Chip Rate
The chip rate of the system to be simulated. This value is used in combination with the service
bit rate to calculate the processing gain for a service.
If you have specified values for orthogonality per clutter type in the Clutter Parameters dialog
box, you have the option here to enable them to be used in the simulation. To do this, select
YES.
If this is set to NO, the orthogonality factor used by the Simulator is the generic value on the
Cell Params tab in the Site Database.
HSDPA Scheduling
You can select one of the scheduling strategies: Round Robin, Max Ec/Io, or Proportionally
Fair.
Only the terminals that support HSDPA will be sorted, even if they do not end up using an
HSDPA bearer.
If you use Non-Dynamic, an HSDPA user (or a number of users if code multiplexing is
enabled) will be served with the HSDPA Power value, regardless of their location relative
to the cell.
If you use Dynamic, HSDPA users will be served either with the HSDPA power value, or
(if it is lower) the available power on the cell. Therefore, with this method, you should
ensure that the HSDPA power value is set accurately.
Page 91
Description
Number of Snapshots
A snapshot represents an individual component within the simulation process. For each
snapshot, specified densities of user terminals are positioned in statistically determined
locations. The ability of each terminal to make its connection to the network is calculated
through an iterative process. The performance of the network is then analysed from the
averaged results.
Intra-Site Correlation Coefficient The correlation between fades (for a terminal) to sectors on the same site.
Inter-Site Correlation Coefficient The correlation between fades (for a terminal) to sectors on different sites.
Max Power Change (%)
Set the Max. Power Change (%) convergence parameter to set the 'stabilisation' target for
each snapshot. This limits the number of iterations per snapshot.
If the percentage change in total uplink and total downlink interference (summed over all
sectors) changes by an amount smaller than this target value for 15 consecutive iterations,
then the iterations are deemed to have converged.
If you want to only scan pixels where traffic exists (a valid traffic raster must be in memory),
select YES.
The simulation can output an array that shows the average number of pilot polluters at any
location, as determined by the threshold that you set here (x dB).
This threshold determines the relative margin below the best Ec/Io within which a cell qualifies
as a pilot polluter.
The exact definition of pilot polluters for CDMA2000 or EV-DO in ASSET is:
The number of sectors not in the active set, but providing an Ec/Io level higher than x dB. The
threshold is absolute. The default value is -15 dB.
The error due to imperfect power control in dB, which can be used to influence the simulation
results. It is recommended that this parameter is set to zero.
In a real network, imperfect power control produces a (log-normal) distribution of achieved
Eb/Nt values for successfully served terminals. One consequence might be a higher uplink
noise rise. If a non-zero value is entered here, the simulation models this effect by including
uncorrelated log-normal errors on the UL and DL transmit powers. Errors are applied only after
all other handover gains and margins have been considered.
If you have specified values for orthogonality per clutter type in the Clutter Parameters dialog
box, you have the option here to enable them to be used in the simulation. To do this, select
YES.
EV-DO Scheduling
Page 92
You can select one of the two scheduling strategies: Round Robin or Max Ior/Ioc.
Description
Number of Snapshots
A snapshot represents an individual component within the simulation process. For each
snapshot, specified densities of user terminals are positioned in statistically determined
locations. The ability of each terminal to make its connection to the network is calculated
through an iterative process. The performance of the network is then analysed from the
averaged results.
Intra-Site Correlation Coefficient The correlation between fades (for a terminal) to cells on the same node.
Inter-Site Correlation Coefficient The correlation between fades (for a terminal) to cells on different nodes.
Max Power Change (%)
Set the Max. Power Change (%) convergence parameter to set the 'stabilisation' target for
each snapshot. This limits the number of iterations per snapshot.
If the percentage change in total uplink and total downlink interference (summed over all
cells) changes by an amount smaller than this target value for 15 consecutive iterations, then
the iterations are deemed to have converged.
If you want to only scan pixels where traffic exists (a valid traffic raster must be in memory),
select YES.
Description
Number of Snapshots
A snapshot represents an individual component within the simulation process. For each
snapshot, specified densities of user terminals are positioned in statistically determined
locations. The ability of each terminal to make its connection to the network is calculated
through an iterative process. The performance of the network is then analysed from the
averaged results.
Intra-Site Correlation Coefficient The correlation between fades (for a terminal) to cells on the same node.
Inter-Site Correlation Coefficient The correlation between fades (for a terminal) to cells on different nodes.
Max Power Change (%)
Set the Max. Power Change (%) convergence parameter to set the 'stabilisation' target for
each snapshot. This limits the number of iterations per snapshot.
If the percentage change in total uplink and total downlink interference (summed over all cells)
changes by an amount smaller than this target value for 15 consecutive iterations, then the
iterations are deemed to have converged.
If you want to only scan pixels where traffic exists (a valid traffic raster must be in memory),
select YES.
Dominance Interference
Threshold
The simulation outputs an array that shows the average number of cell interferers at any
location, as determined by the threshold that you set here (x dB).
This threshold determines the relative margin below the best RSRP within which a cell
qualifies as a cell interferer.
The exact definition of cell interferers for LTE in ASSET is:
The number of cells providing an RSRP value within x dB of the best RSRP value. The
threshold is relative. The default value is 6 dB.
Page 93
Parameter
Description
SU-MIMO Diversity
You can selectively activate or deactivate the MIMO modes in areas that have LOS to the
serving cell. This is only applicable to predictions generated by the Enhanced Macrocell
model, the MYRIAD model, or the Volcano model, which can distinguish LOS and NLOS at
each predicted location.
SU-MIMO Multiplexing
MU-MIMO
(MIMO schemes rely on a low correlation between the signal paths to the transmit elements of
an antenna; locations that have LOS to an antenna are more likely to have a high correlation.)
On the Auto Plan Setup tab, set the required options for the appropriate
technology, as described in the following section.
All changes that you make on this tab are automatically saved to the database in
the Applied state, and the changes will persist when you close the Workflow
dialog box.
However, if appropriate, you can carry out one of the following actions:
Page 94
If you want to restore the options on this tab to the previous committed state
(if such a state exists), click Restore
If you want to share the changes on this tab with all other users, click Commit
Description
This margin is used to determine which cells interact with other cells in each pixel.
For example, if the margin is set to 3dB, an interacting cell can be defined as 'a cell
whose signal strength is within 3dB of the Best Serving signal at that pixel'.
For each pixel, the threshold parameter/s (in next row) must also be satisfied.
Within the search area, on a pixel-by-pixel basis, the wizard finds potential target
cells. The difference between the power of the source cell and target cell is
calculated. This value is then compared to the margin, and the difference is
converted into an interaction probability factor (based on a normal distribution
formula). These factors are summed to find the net interaction probability for each
target cell on the whole search area. Based on the qualifying criteria (in the next
rows), the wizard creates a list of valid target cells for each source cell.
The maximum number of target cells that are considered at each pixel during the
calculations. On a pixel-by-pixel basis, this parameter determines how many 'sets'
of covering cell data is to be evaluated for potential interacting cells.
Maximum distance
In order to qualify as a valid target cell, a target cell must be within this specified
distance.
The maximum number of target cells that can qualify as valid interacting cells for
the source cell. (The overlapping percentage ranking determines which cells
qualify).
In the case of LTE, this value comes from the cell-specific values defined on
the Neighbours tab in the Site Database.
Minimum number of neighbouring cells This option can be used to ensure a minimum number of interacting cells for each
source cell, even if the percentage (in next row) is not attained. This parameter is
activated by the associated checkbox.
All the supporting criteria must also be satisfied.
Minimum overlapping (%)
A target cell must attain at least this percentage of the overlapping area to qualify
as a valid interacting cell.
If you also select the 'Minimum number of interacting cells' option, this means that if
the number of valid interacting cells (>n%) is less than the specified minimum
number, other target cells (<n%) will be added as valid interacting cells, until the
minimum is satisfied.
All the supporting criteria must also be satisfied.
Enables you to set a specific standard deviation for the signal strength/quality (as
appropriate). This parameter is activated by the associated checkbox, otherwise
the propagation model value is used.
If you select this option, cells that exist on sites belonging to the same Property will
automatically qualify as valid interacting cells.
Page 95
New elements
Existing elements
The network element types that can be associated with your chosen status field
are: Cell, Site, or Property. The field type to be used can be Pick-list or Boolean.
2
Improved Selection Planning: The Optimiser can start from a realistic snapshot of
the existing network, because new elements will not be initially switched 'ON'.
Improved Cost Modelling: The Optimiser can discriminate between new and
existing elements when it considers action costs (for actions such as azimuth
changes) - only existing elements can incur such costs.
Improved Cost Comparisons: You can compare the cost/benefits of turning 'ON'
new cells, and/or switching 'OFF' existing cells.
If you have a licence for the Financial Analysis module, there are additional
benefits. For more information, see the Financial Analysis User Reference Guide.
If you do not use this differentiation, all your network elements will be
considered as existing.
Status fields represent a very crucial part of ENTERPRISE, and can be used for a
variety of reasons, for example to track the network deployment phase of network
elements. It is probable that your project administrator has already set up most of the
fields for your project.
If you want to use the Element Status functionality, you should request that your
administrator sets up a special field dedicated for this purpose (unless your
organisation has already decided to use one of the existing fields for this).
A simple example would be a field named 'State (Existing or New)' with Pick-list
options of 'Existing' and 'New'.
For information on how to set up fields, see the ENTERPRISE Installation and
Administration Guide.
Page 96
Assuming your administrator has set up or designated a field for this purpose, this is
how you activate it to differentiate between new and existing elements:
1
on the main
The drop-down list displays all the Pick-list or Boolean fields that have been
created for the project by your administrator.
4
From this list, select the field that you want to represent the element status. This
picture shows an example:
In the State pane, select the field state(s) that you want to indicate a new element.
Here is an example:
Select the respective checkbox(es) if you want your new and/or existing network
elements to be initially considered as OFF when creating a new plan.
A plan can include both new and existing network elements; the purpose of these
options is to enable you to specify one or both categories as OFF.
If you do not select either option, the created plan will initially consider all
elements as ON (in effect, it makes no distinction between new and existing
elements).
Page 97
Here are some examples of when you might find these options useful:
If You Want to Achieve an
Optimised Network Plan
Page 98
If you want to restore the options on this tab to the previous committed state
(if such a state exists), click Restore
If you want to share the changes on this tab with all other users, click Commit
If other people are logged into the same database as you, it is possible that they have
Committed changes to network element(s) that you are now trying to Commit. If this
happens, you are prompted either to cancel the Commit or to continue, overriding
their Committed data with your own changes.
Analysis report
Optimiser report
This can be done using report formats that can be configured and managed by your
administrator. For information on this, see the ENTERPRISE Installation and
Administration Guide.
Page 99
If such formats have been configured, an individual user can determine the 'mapping'
of the required report format to each ADVANTAGE report type.
A default set of formats already exists in any new project. These formats are
already mapped to each report type, so if you are satisfied with the default reports,
you do not need to do anything (neither in ENTERPRISE Administrator nor in
ADVANTAGE).
If you need to view or modify the mapping relationships, you can use the ACP &
Financial Analysis Reports Assignment dialog box.
To open this dialog box:
From the Reports menu, click ACP & Financial Analysis Reports Assignment.
The ACP & Financial Analysis Reports Assignment dialog box appears:
For the appropriate report type, click in the Report Name column.
In the drop-down list, select the required report name (this is only meaningful if
multiple formats have been made available for the report type).
Repeat the above steps if you want to modify any other mapping relationships.
Click Close.
The reports will automatically be output in the chosen format when they are next
generated.
You can check the basic details of the currently mapped report formats by selecting
the report type and clicking the 'Info' button.
Page 100
CHAPTER 5
Start/Run Optimisations
Delete plans
Temp Apply/UnApply
Apply to Database
There is also a context menu, which you can access by right-clicking on the
icon of the appropriate plan. This provides quick access to the same options as most
of the main buttons, but also provides extra options. For more information, see Using
the Context Menu on page 112.
Page 101
When you are using the Optimiser Workflow for the first time, you need to set up
the general parameters, strategy, settings, and so on, before you run any
optimisations. These may include:
RF Array Thresholds
RF Metric Targets
Costs/Limits
Strategy
Traffic
Settings
However, this depends whether you have the appropriate user permissions. Parts of
this process may not be relevant to the general user, and it is possible that the above
options and parameters are centrally specified within the user's organisation.
Plan
Delta plan
A delta plan is the result of an optimisation run from an original plan. However, in
essence, the two types of plan, once created, can be considered to be the same. This is
because, in general terms, you can perform similar operations using a plan of either
category, and you can choose to Apply any of these plans to the database.
Here are some basic principles:
Page 102
Before you can start an optimisation, you must have at least one plan created. For
more information, see Creating Plans for Optimisation or Analysis on page 104.
Plans are created by way of a 'snapshot' from the current Site Database (this is the
only way a 'new' plan can be created). During that process, you can choose to
restrict the scope of the plan in terms of (i) region, (ii) sites/nodes/cells, and (iii)
vectors/drive test routes, by using the options in the Plan Wizard. At the end of
that process, the plan appears within the Plan Manager list.
Plans and delta plans are listed in the Plan Manager section of the Workflow
dialog box.
Delta plans can only emanate from a plan, and they must always be 'parented' to a
plan, since they represent changes to the starting plan.
When you run an optimisation for the plan, the delta plans appear as 'children' of
the parent plan.
icon.
This picture shows an example of how plans and delta plans are listed in the Plan
Manager:
These options are visual 'filters' that help you to distinguish which plan(s) you are
working with.
The 'Created By Me' option always lists the plans that you (the logged in User ID)
have created.
The 'All Plans' option always lists all existing plans, regardless of who created them.
The 'Used' option requires a more detailed description:
The concept behind the 'Used' option is that, generally speaking, only one individual
would be working with a particular plan at any one time. This would avoid 'multiuser' problems if you are intending to work iteratively with a plan, making
progressive changes toward a new plan which has the potential to improve the
quality of your network.
However, it is possible, if required, for a plan to be 'used' by more than one person.
When this is the situation, the Action-Constraints are viewable but not editable, and
the plan cannot be deleted.
When you create a plan, it automatically becomes 'used' by you. However, it is
possible to turn this status on/off, using the Toggle option in the context menu. In a
similar way, any user who did not create the plan, can use the Toggle option to
activate his/her 'used' status for that plan. The option can therefore be used to hand
over the 'use' of the plan to a different single user, or (if explicitly required) it can be
used to share the 'use' of the plan amongst multiple users.
In situations where you may want multiple users to work on the same plan, but have
the freedom to edit the Action-Constraints for that plan, you can utilise the Duplicate
option. This enables different users to 'branch off' from the same original plan into
potentially different proposed network plans. It also enables you to work on a copy of
an existing plan, so that you can experiment with different Action-Constraints, while
still retaining the original plan.
Only plans marked as 'Used' will be exported to XML. See About the File Menu on
page 27.
Page 103
The Plan Setup method enables you to specify the region and the filters (cells) for
the plan, and then manually assign the appropriate Action-Constraints templates.
It can be launched either from the Workflow, or directly from the Map View. The
latter is quicker and easier if the Map View is already displaying the correct region
and filters.
This method is recommended for users who wish to create plans without any
recommendations from the tool.
The Auto Plan Setup method can automatically recommend the grouping of cells
into filters, and consequently facilitates the assigning of the appropriate ActionConstraints template to those filters. It can also automatically determine the
geographic area for the resultant plan, by creating a vector. The concept behind
this method is that it can automate some of the pre-optimisation tasks (which
would be done manually when using the Plan Setup method).
This method is recommended for users who wish to create plans helped by
recommendations from the tool.
It can be launched either from the Workflow, or directly from the Map View. The
latter is quicker and easier if the Map View is already displaying the correct region
and cell filters.
A fuller description of this method is included in Using the Auto Plan Setup
Method to Create a Plan on page 108.
If you launch either method directly from the Map View, you should ensure that the
display includes the region and the cells that you want to choose from when creating
the plan.
If you launch either method from the Workflow (Plan Manager), you should ensure
that the display includes the region that you want to use when creating the plan. In
this case, it is possible to choose cells that are not displayed on the Map View, but
they must be located within the region.
Page 104
Important :
When creating a plan, two of the steps are crucial in determining which cells will
be included: (i) specifying the region and (ii) selecting the site/cell filter(s).
A further (optional) step enables you to select specific vectors and/or drive test
routes, which can be useful if you want to precisely define the pixels that will be
included in the metrics evaluation. This is an important way of focusing the
optimisation calculations, but it does not (for example, in the case of a polygon)
determine which cells are included.
Check that you have a Map View window open that displays the region and cells
that you want to include. (However, if you prefer to enter precise co-ordinates, an
open Map View is not essential.)
Click the Plan Setup button, then click the Plan Setup option.
In the Plan Wizard that appears, type a name for the plan.
on the main
If required, you can select an existing plan as a template. For information on this,
see the following section.
Click Next.
6
Check that the region for the plan is correct. If necessary, you can modify the
region by entering precise co-ordinates.
Click Next.
ADVANTAGE 8.1 User Reference Guide
Using and Managing Plans
Page 105
Select one or more filters to determine which sites/nodes and cells are to be
considered in the plan.
Click Next.
8
The next step of the wizard enables you to select the appropriate ActionConstraints templates on a filter basis.
Anything you edit here can be modified after creating the plan, using the
Action-Constraints dialog box. In fact, if preferred, you can skip this step now, and
do it later, as described in Using the Action-Constraints Dialog Box on page 125.
Use the Add button to specify each filter-template combination. (You can delete a
row by clicking .) Here is an example:
You can edit any of the filter selections and/or template assignments by
clicking in any of the columns. You can also edit any of the Action-Constraints
Templates (in the normal way) by clicking the Manage Templates button.
Click Next.
Page 106
If you want to restrict the optimisation to particular vectors, select the Use Vectors
checkbox and then specify the vectors under the System or User folders, as
appropriate.
- and/or If you want to restrict the optimisation and/or analysis to a drive test route, select
the appropriate vectors from the Measurements folder.
You can subsequently modify the restriction selections at any time, by rightclicking on the plan in the Plan Manager of the Workflow, and selecting Edit
Vectors.
10 Click the Finish button.
There is also a button on the main ADVANTAGE toolbar which enables you to
create a 'Quick Plan' based on an open Map View, enabling you to do this in fewer
steps. For more information on this, see Creating a Quick Plan from a Map View on
page 108.
Page 107
Any cells that were in the original 'template' plan, but not captured by the region
and filters for the new plan, are always excluded from the new plan. Conversely, if
there are cells in the new plan that did not exist in the original 'template' plan, they
would need their action-constraints to be edited in the Action-Constraints dialog box
(in the usual way).
Ensure you have the appropriate Map View open, so that it is displaying:
In the horizontal toolbar of the Map View, click the 'Plan Setup' button
(alternatively, click on the View and press Ctrl-U).
The Action-Constraints dialog box appears, so that you can edit the actions and
constraints for the new plan. For more information, see About the ActionConstraints Dialog Box on page 122.
In the Workflow dialog box, the new plan appears in the Plan Manager list. The
plan name is automatically set, but you can right-click on it and rename it, if
required.
When using this 'Quick Plan' method, any vectors that are visible within the
relevant Map View will automatically be added to the resulting plan definition, but
these vector selections can then be amended.
At the stage where the Auto Plan Setup is aware of the 'main focus' cells, it can
recommend the grouping of other cells into 'tiered' filters (using an algorithm based
on user-defined settings). It is then simple to make the appropriate Action-Constraints
template assignments. For example:
Filter
Main focus
Recommended (tier 1)
Recommended (tier 2)
Read-Only
Furthermore, the Auto Plan Setup can then automatically determine the geographic
area that should be taken into consideration during analysis and optimisation of the
resultant plan. The algorithm builds a list of all cells contained within the plan that
have any 'non-Read-Only' Action-Constraints Templates associated with them. It then
finds all pixels where any of these cells provides a signal strength above the relevant
signal threshold defined on the Auto Plan Setup tab of the Settings page in the
Workflow. An enclosed vector (polygon) is then created around all these pixels.
In summary, the main benefits of this method are:
The 'tiered' filters are recommended automatically (and they are independent of
currently existing filters). These tiered filters can be considered as a form of cell
'hierarchy' in terms of what can happen in the optimisation.
This is based on a cell identification algorithm that uses the settings under the
Auto Plan Setup tab in the Settings page of the Workflow. For more information,
see Configuring the Settings for Auto Plan Setup on page 94.
The templates in the Action-Constraints dialog box are assigned based on the
previous sequence of assignments in this dialog box, which creates consistency for
iterative use of the Auto Plan Setup.
You can manually override these recommendations (if you have the relevant
permissions).
The geographic area for the eventual evaluation of the plan can be automatically
determined.
Depending on the planning region size, cell volumes, and map data
resolution, the running of the algorithms for the filters and the geographic area
can take some time.
If you intend to use the 'Create Restriction Polygon' option, a valid Reference
Terminal Type must have been specified on the Strategy page of the Optimiser
Workflow.
Ensure that you have a Map View window open that displays the region and cells
that you want to include.
In the top-right corner of the Map View window, click the Auto Plan Setup button
(alternatively, click on the View and press Ctrl-V).
The Auto Plan Setup Wizard appears. Name the plan, and insert any comments.
Click Next.
Page 109
Select one or more filters to define which cells should represent the 'main focus'.
Click Next.
The 'Review Recommendations' step of the wizard shows the Focus filter and the
recommended 'Tier 1' and 'Tier 2' filters, each associated with their appropriate
Action-Constraints templates. Here is an example:
You can edit any of the filter selections and/or template assignments by clicking
in the Filter column or in any of the planning mechanism columns. You can also
edit any of the Action-Constraints Templates (in the normal way) by clicking the
Manage Templates button.
You can use the
button if you need to specify more filter-template
combination rows, and you can delete rows by clicking .
Where appropriate, you can use the up and down arrows
to set the filter
priorities. Only one template (per mechanism) can be assigned to a filter.
Therefore, in cases where an object might exist in more than one filter in this
dialog box, the filter priority order is important in determining which template is
assigned.
You can check the contents of the relevant filter by clicking
7
If you want the Auto Plan Setup to automatically determine the geographic
area that should be taken into consideration during evaluation of the resultant
plan, select the 'Create Restriction Polygon' option.
You can only do this if a valid Reference Terminal Type has been specified on
the Strategy page of the Optimiser Workflow.
If you select this option, the Auto Plan Setup will run the restriction polygon
algorithm and store the associated vector.
The new vector subsequently appears in the ACP folder in the Vector Manager
and in the Map View data types list (where it can be visualised).
Click Next.
Page 110
If you want to restrict the optimisation to particular vectors, select the Use Vectors
checkbox and then specify the vectors under the System or User folders, as
appropriate.
- and/or If you selected the 'Create Restriction Polygon' in the previous step, the 'Use
Restriction Polygon' checkbox will be already selected, but you have the option to
deselect it.
- and/or If you want to restrict the optimisation and/or analysis to a drive test route, select
the appropriate vectors from the Measurements folder.
You can subsequently modify any of the restriction selections at any time, by
right-clicking on the plan in the Plan Manager of the Workflow, and selecting Edit
Vectors.
9
There is also an option to launch the Auto Plan Setup by clicking the Plan Setup
button (and then the Auto Plan Setup option) on the Workflow dialog box. If you do
this, you need to confirm (or specify) the region and select the site/cell filters. The key
difference is that you can select filters not currently displayed on the Map View.
Page 111
Improved Selection Planning: The Optimiser can start from a realistic snapshot of
the existing network, because new elements will not be initially switched 'ON'.
Improved Cost Modelling: The Optimiser only considers action costs (for actions
such as azimuth changes) for elements that already exist.
If you do not use this differentiation, all your network elements will be considered
as existing.
For more information, see Specifying a Field to Differentiate New/Existing Elements
on page 96.
Page 112
This not only provides quick access to the same options as most of the main buttons,
but also provides extra options:
Option
Available for
Description/Comments
Action-Constraints
Plans
Edit Vectors
Summary
Plans
Initial Report
Plans
Delta Report
Delta plans
Final Report
Delta plans
Analysis
Financial Analysis
Optimise
Duplicate
Plans
For more information, see Viewing and Using Plans in the Plan
Manager on page 103.
Duplicate
Delta plans
For more information, see Viewing and Using Plans in the Plan
Manager on page 103.
Page 113
Option
Available for
Description/Comments
Rename
Delete
When you delete a plan, its 'child' delta plans are also removed.
However, a delta plan can be deleted individually.
Bookmark
Toggle Use
You can use this option to toggle the 'Used' status of a plan.
The option can be used, for example, to 'release your usage' of a
plan. This may, for example, enable another user to 'obtain the
usage' of that plan.
For more information, see Viewing and Using Plans in the Plan
Manager on page 103.
Refresh
Page 114
Ensure you have a Map View window open that will include the planning region
for the plan.
Open the Map Information and Control, and select the required plan under the
Plans heading in the Data Types:
If required, you can double-click the plan name in the Map Information and
Control, and select a different display colour.
The other items displayed (including the nodes or sites) depend on which other
items are selected in the Data Types (this may also depend whether a Favourite View
has been initially displayed). This plan viewing option does not discriminate in terms
of nodes/sites; it simply visualises the planning region.
Page 115
Description
Plan Summary
A summary which lists the included cells, and the planning region (size,
location, resolution).
The summary also includes an Update 2D View button, which can be
very useful.
Enables you to quickly update (overwrite) the contents of the Selection Filter
with the cells that are in the selected plan.
For more information about the Selection Filter, see the ENTERPRISE User
Reference Guide.
In the same way as for other items in the Data Types, these options enable
you to manage the display properties of each item.
The Properties option can also be accessed by double-clicking the plan
name.
If you have modified one of the visual options (Apply Sampling, Properties), you
need to click the Redraw button to refresh the Map View.
In the Map Information and Control, right-click the required plan (under the Plans
heading in the Data Types).
Page 116
Any previously Applied changes in the Site Database being lost (in the normal
way)
A configuration in the Site Database that is different from the plan that you
created to start with (because the plan, once created in the Plan Manager, is
independent of subsequent database changes)
To apply a plan:
1
Page 117
The database is now reverted to its previous configuration, and the Site Database
window is active again.
Page 118
You cannot make any manual changes to the Site Database while it is in this
'temporary' restrictive state.
The operation does not affect other users who are sharing the project.
You cannot close a session (that is, close the project) while the Site Database is in
the 'temporary' state. It is obligatory to revert it by clicking Temp UnApply before
you close your session.
You can make further manual changes to the Site Database, in the normal way,
after this operation.
You will be able to use the Restore option in the Site Database, if necessary, to
restore to the previous committed state (assuming the network elements had at
some stage been previously committed).
The operation may subsequently affect other users who are sharing the project, in
the normal way, if you choose to Commit the changes.
You can close a session (that is, close the project) in the normal way, if required,
with some changes in the Applied state.
Deleting a Plan
To delete an optimisation plan:
1
Page 119
Page 120
CHAPTER 6
Setting Action-Constraints
for Plans
The purpose of action-constraints in ADVANTAGE is to allow certain network
parameter changes to be considered in a network optimisation, but at the same time
impose meaningful limitations and restrictions on those changes, in order to
accurately represent the real-world environment.
In ADVANTAGE, there are two separate 'sources' of action-constraints:
Action-constraints that you can set up and edit within the Optimiser Workflow
Action-constraints that you can set for specific network elements directly within
the Site Database
Action-constraints that are set in the Site Database are always auto-populated
into the Action-Constraints dialog box when you create a plan. You then have the
freedom to modify those action-constraints at that stage, if required. When you run an
optimisation, the Optimiser reads the action-constraints exclusively from the ActionConstraints dialog box, regardless of their original 'source'.
This flexibility enables you to:
Set specific action-constraints in the Site Database, and then edit these actionconstraints (if required) and set up further action-constraints (if required) in the
Action-Constraints dialog box.
- or -
This chapter focuses on the plan-specific Action-Constraints dialog box within the
Optimiser Workflow. For more detailed information about the action-constraints
within the Site Database, see About Action-Constraints on page 37.
Page 121
The Action-Constraints dialog box not only sets the constraints for the network
optimisation, but, crucially, it also sets the possible actions (namely, the network
parameter changes) that can take place.
In the majority of cases, when you have created a new plan you must set possible
changes in the Action-Constraints dialog box, otherwise an optimisation will not
run. The only exception to this is when you are performing an Antenna or Grid
optimisation where particular action-constraints have been set in the Site Database
before the plan was created, as shown in this table:
Action-Constraints
Antenna
Electrical or Mechanical Downtilts, with Antenna Constraints tab for a cell (GSM)
accompanying Total Downtilts
Antenna Constraints tab for a node (other technologies)
Grid
Property Locations
Sector Configurations
The user interface of the Action-Constraints dialog box is designed to help you. The
two main guiding factors are the colour distinctions and the checking facility:
Page 122
Colour Backgrounds
There are two colour backgrounds for columns in the dialog box:
The columns that cannot be edited (for example, those that show the current
values of the plan) are presented on a blue background.
The columns that can be edited (for example, those for which action-constraints
can be set for the plan optimisation) are presented on a green background.
Checking Facility
The Check button is extremely useful for automatically verifying that the plan's
action-constraints are valid, and ready for the optimisation to run.
For example, it can show you:
How many 'Degrees of Freedom' are in the plan, according to the current state of
the Action-Constraints. This value emanates from the amount of variables in the
plan. This picture represents a plan where fifteen of the antennas can each
undergo a possible azimuth change:
If there are no Degrees of Freedom, then the optimisation will not be allowed to
run.
Errors will not allow the optimisation to run; warnings will allow it to run, but the
message is aimed at making you aware of the situation.
It is recommended that you make full use of all these guiding factors in this
section to ensure everything is set up correctly before optimising any plan.
Page 123
The existing values - although inactive - remain in place just in case you want
to reuse them later, by removing the Fixed setting. Unless that happens, they
stay inactive.
Here is an example:
In one of the rows, the Fixed checkbox for the Azimuth action-constraint is
selected. Therefore, when the optimisation is run, no azimuth changes will be
considered for that particular antenna in that row.
The above principles are true whether the Action-Constraints dialog box is edited
manually or by using Template Assignments. With specific regard to changes
made to the Action-Constraints values by assignment from templates, you should
note the following:
When you create a template, it is likely that you will not have selected all the
potential action-constraints in that template. When you assign that template to
a filter, the 'Fixed' checkboxes for the action-constraints that were unselected in
the template become automatically selected in the Action-Constraints dialog
box (for the objects in the associated filter and independently for each planning
mechanism).
For example, if a template has only Azimuth (Antenna mechanism) selected,
the other action-constraints (Tilts, Heights, Device/Pattern) would all be set to
'Fixed' in the Action-Constraints dialog box, after the template assignment.
For more information, see Assigning Action-Constraints Templates to Objects
on page 150.
Page 124
Antenna
Power
The constraints, that is, the restrictions on what can be changed, in terms of
objects, ranges, limits and so on
The actions, that is, all the possible network parameter changes that may be
considered in the optimisation
The action-constraints of any plans which already have delta plans are always in
Read-Only format.
If you are only intending to analyse a plan, you may not need to edit the actionconstraints.
You can edit the Action-Constraints for an optimisation Plan within the Plan
Manager. To do this:
1
on the main
Page 125
For the selected Plan, you can edit the constraints and/or the possible changes. You
can do this:
Individually for each object, on a manual basis. You can employ functionality
similar to that in Microsoft Excel to do this, such as copying and pasting.
- or -
Using Action-Constraints Templates that you have created, which you can then
either:
When you have finished making changes in the Action-Constraints dialog box,
you must always click 'Apply', in order to save the changes.
The section headings (ID, Current Values, Azimuth, Pilot Power, Candidate
Planning and so on)
The column headings (Property, Cell, Min, Max, Step, Fixed and so on)
Page 126
Show/hide column
Sort ascending
Sort descending
Filter (gives option to show only the rows containing a chosen value in column)
In addition, if you prefer, you can perform similar viewing operations using the
Show/Hide button:
Show/Hide button
In very simplified terms, here is some general advice on how you might use each
method:
Manually Editing the Action-Constraints Values
If you only want to set up or edit a single parameter, for example an Azimuth Change
Step, it is probably easier and quicker to edit the value directly in the ActionConstraints dialog box:
Page 127
If you want to set up different values for different groups of cells, make full use of
the filters when you edit the values.
Important :
These filters only display the cells included in the plan when it was created.
Therefore, they are intrinsically 'subsets' of the corresponding filters that you
would view in the Site Database.
Each time you open a project, the filters in this dialog box will always default
to the filter specified on the Filters tab of the Preferences dialog box, under the
File menu.
You can employ functionality similar to that in Microsoft Excel, such as:
Page 128
The constraints, that is, the restrictions on what can be changed, in terms of
objects, ranges, limits and so on
The actions, that is, all the possible network parameter changes that may be
considered in the optimisation
The Action-Constraints Templates provide you with a quick and easy way of setting
up action-constraints so that they can be reused across all or some of your plans. You
should make full use of these templates so that you avoid duplication of constraints
that may be generic to all plans. In other words, you should avoid spending time
setting many constraints directly in the Action-Constraints dialog box, if there is a
high chance that you will be using those action-constraints for other plans. See About
Action-Constraints Templates on page 137.
Columns in the ID section of the Antenna tab in the Action-Constraints dialog box
Description
These are object identities relating to the network elements included in the plan.
Template
If applicable, this is the assigned template that determines the possible changes in the
row. If the changes are independent of a template, this field will display 'Custom'. If the
Read Only template is assigned, all the 'Fixed' checkboxes in the row are selected.
Columns in the Current Values section of the Antenna tab in the Action-Constraints dialog box
Page 129
Description
Columns in the Antenna Constraints section of the Antenna tab in the Action-Constraints dialog box
Description
Height Variation
If you want to use height variation, select the checkbox. This defines whether the heights for
individual antennas may differ at a specific Property.
If height variation is not selected, all antennas on the same cell layer (GSM) or all carriers at
this Property (all other technologies) must be at the same height. However, GSM cells for different
cell layers, or cells of different technologies (for example, GSM and UMTS) can still have antennas
with heights different from each other.
Minimum Azimuth
Difference
This enables you to set a minimum separation (in degrees) that you are willing to accept between
antennas of the same height on a specific Property.
Co-Location Enabled
This enables you to allow antenna devices to share co-location parameters (identical location coordinates, height and azimuth, and existing on the same Property).
If Antenna Co-location is not enabled for a Property, no antenna sharing or co-location
configuration can be accepted as a valid starting configuration or examined as a potential
optimisation solution by the Optimiser. For more information, see How the Optimiser Considers
Shared Antennas on page 142.
This enables you to define, for a specific antenna, an orientation range that the automatic
optimisation cannot consider for azimuth changes. For this, the minimum represents a clockwise
bearing (the start azimuth of the forbidden range) and the maximum represents an anti-clockwise
bearing (the end azimuth of the forbidden range).
For descriptive detail on this, see About the Forbidden Azimuth Range on page 130.
Page 130
This description of the Forbidden Azimuth Range also corresponds to the similar
option on the Antenna Constraints tab in the Site Database. (Action-constraints that
are set in the Site Database are always auto-populated into the Action-Constraints
dialog box when you create a plan, but they can be modified at that stage, if required.)
The way that you set the forbidden azimuth parameters depends on your exact
requirements. This illustration shows the importance of setting up the minimum and
maximum settings correctly:
Examples of forbidden azimuth ranges with corresponding parameters in the Action-Constraints dialog box
This next picture illustrates a more specific example of how the forbidden azimuth
might be used within an antenna optimisation.
The example represents an antenna currently set to 60 with an optimisation azimuth
range between 0 and 120, but with a forbidden range between 90 and 105:
Specific example of how the forbidden azimuth might be used within an antenna optimisation
Page 131
This picture shows how the corresponding parameters would be set in the ActionConstraints dialog box:
Columns in the Electrical Tilt / Patterns section of the Antenna tab in the Action-Constraints dialog box
Description
Use Min/Max/Step
Serves as a 'switch'. Select this if you want Min/Max/Step values to be used in the optimisation, but
do not select it if you want Specified Device/Patterns to be used instead.
Min/Max/Step
You can enable the electrical downtilt of the antenna to be changed, by specifying Minimum and
Maximum downtilts, and the allowed Step of change (all in degrees).
Fixed
Select this if you want nothing to be changed for Electrical Tilt/Patterns. If this is selected, the 'Use
Min/Max/Step' checkbox will have no effect.
Specified Device/Patterns
Device Fixed
Select this if you want the pattern to be allowed to change, but not the device.
Notes:
Page 132
Total downtilt must also be set, in order to allow the required changes to the
electrical downtilt during optimisation. See Antenna Tab - Total Downtilt Heading
on page 133.
If any of the three antenna constraints for electrical tilt (Min; Max; Step) are
enabled for an antenna in the Site Database, the Use Min/Max/Step checkbox for
that antenna is automatically selected in the Action-Constraints dialog box, but
this is editable.
Columns in the Mechanical Downtilt section of the Antenna tab in the Action-Constraints dialog box
Description
Min/Max/Step
You can enable the mechanical downtilt of the antenna to be changed, by specifying Minimum and
Maximum downtilts, and the allowed Step of change (all in degrees).
Fixed
Total downtilt must also be set, in order to allow the required changes to the
electrical downtilt during optimisation. See Antenna Tab - Total Downtilt Heading on
page 133.
Columns in the Total Downtilt section of the Antenna tab in the Action-Constraints dialog box
Description
Min/Max
You can specify limits for the total downtilt. Any changes made to the electrical and/or mechanical
downtilt during optimisation would not be allowed to exceed these limits.
Fixed
Select this if you want nothing to be changed for the total downtilt.
Page 133
Columns in the Azimuth section of the Antenna tab in the Action-Constraints dialog box
Description
Min/Max/Step
You can enable the azimuth of the antenna to be changed, by specifying Minimum and Maximum
azimuths, and the allowed Step of change (all in degrees).
Fixed
If you want to set up a forbidden azimuth range, see About the Forbidden
Azimuth Range on page 130.
Columns in the Height section of the Antenna tab in the Action-Constraints dialog box
Description
Use Min/Max/Step
Serves as a 'switch'. Select this if you want Min/Max/Step values to be used in the optimisation, but
do not select it if you want Values to be used instead.
Min/Max/Step
You can enable the height of the antenna to be changed, by specifying Minimum and Maximum
heights, and the allowed Step of change (all in degrees).
Values
If applicable, this initially shows a list of values specified in the Site Database (see Configuring
Property Antenna Constraints on page 42). Alternatively, you can manually edit the list of values in
the column.
If you want to enable these values to be used during optimisation, ensure that the Min/Max/Step
checkbox is not selected.
Fixed
Page 134
Select this if you want nothing to be changed for the antenna height. If this is selected, the 'Use
Min/Max/Step' checkbox will have no effect.
The constraints, that is, the restrictions on what can be changed, in terms of
objects, ranges, limits and so on
The actions, that is, all the possible network parameter changes that may be
considered in the optimisation
The columns contain all the power-related parameters that correspond to the
technology of the network element.
For some of these parameters, there is an option to set a 'uniform group' constraint.
This enables you to specify groups of cells that you want to be adjusted uniformly by
the Optimiser.
To do this:
In the appropriate 'Uniform Group Id' column, specify a number (0 or greater) for
the cells that you want to be grouped by the Uniform Power constraint. It is
possible, if required, to use different numbers to make separate groups.
If this option is inactive for a cell, the value shows as -1.
If this is enabled, the respective initial power values for the associated cells must
be the same in order for changes to be considered by the Optimiser. If the initial
power values are not the same, then this constraint will not be applicable and will be
ignored.
The Action-Constraints Templates provide you with a quick and easy way of setting
up action-constraints so that they can be reused across all or some of your plans. You
should make full use of these templates so that you avoid duplication of constraints
that may be generic to all plans. In other words, you should avoid spending time
setting many constraints directly in the Action-Constraints dialog box, if there is a
high chance that you will be using those action-constraints for other plans. See About
Action-Constraints Templates on page 137.
The Action-Constraints Templates provide you with a quick and easy way of setting
up action-constraints so that they can be reused across all or some of your plans. You
should make full use of these templates so that you avoid duplication of constraints
that may be generic to all plans. In other words, you should avoid spending time
setting many constraints directly in the Action-Constraints dialog box, if there is a
high chance that you will be using those action-constraints for other plans. See About
Action-Constraints Templates on page 137.
ADVANTAGE 8.1 User Reference Guide
Setting Action-Constraints for Plans
Page 135
None
No effect.
n/a.
Site
Sector
The selection planning options can also be set up using the Grid Planning ActionConstraints Template, as described in Configuring Action-Constraints Templates for
Grid Planning on page 147.
Page 136
During an Optimisation:
None
No effect.
List
Sites can be moved to specified locations (corresponding to the Candidate Properties and/or 'coordinate only' locations defined in the Site Database).
Search Step
Sites can be moved to locations determined by globally generated grid co-ordinates, as defined in the
Grid Planning Action-Constraints Template.
Both
These options can also be set up using the Grid Planning Action-Constraints
Template, as described in Configuring Action-Constraints Templates for Grid
Planning on page 147.
Antenna
Power
Page 137
You should make full use of these templates so that you avoid duplication of
constraints that may be generic to all plans. In other words, you should avoid
spending time setting many constraints directly in the Action-Constraints dialog box,
if there is a high chance that you will be using those action-constraints for other plans.
Example of the options available within the Actions Constraints Template Editor
Page 138
on the main
If you are adding a template, click Add, name the template, click OK, and then
click Edit.
- or If you are editing an existing template, select it and click Edit.
In the dialog box that appears, click the first action or constraint that you wish to
configure, for example Antenna Planning - Electrical Downtilt.
For details on the different planning actions and constraints that you can
configure, see one of the following sections:
In the right hand pane, edit the values for this action or constraint. For example:
Click the next action or constraint that you want to configure, and in the right
hand pane edit the values as appropriate.
You can configure any combination of actions or constraints in the same template.
For example, a template can contain both Antenna Planning and Power Planning
actions or constraints.
Page 139
When you have configured all of the actions and constraints that you require, click
OK, and then, in the Action-Constraints dialog box, click Close.
You can now assign this (or any other) template to objects on a 'filter-specific' basis
in the Action-Constraints dialog box, as described in Assigning Action-Constraints
Templates to Objects on page 150.
This table describes the antenna planning action-constraints that you can configure:
Select
To
Device/Pattern
Page 140
Select
To
Electrical Downtilt
Max Change defines the maximum permitted change from the respective original value in the
Site Database (in degrees).
Total Downtilt must also be selected, unless Mechanical Downtilt is considered and the Total
Downtilt is to remain unchanged.
For an optimisation to consider electrical downtilt changes, the appropriate antenna patterns
(for each antenna device) need to be set up in the Cellular Antennas dialog box.
Mechanical Downtilt
Min Value sets the minimum mechanical downtilt that is permitted (in degrees). Any downtilts
below the minimum will not be modified in the optimisation.
Max Value sets the maximum mechanical downtilt that is permitted (in degrees). Any
downtilts above the maximum will not be modified in the optimisation.
Max Change defines the maximum permitted change from the respective original value in the
Site Database.
Total Downtilt must also be selected, unless Electrical Downtilt is considered and the Total
Downtilt is to remain unchanged.
Total Downtilt
Azimuth
Height
Enable the total downtilt (electrical plus mechanical) of the antenna to be changed:
Min Value sets the minimum total downtilt that is permitted (in degrees). Any downtilts below
the minimum will not be modified in the optimisation.
Max Value sets the maximum total downtilt that is permitted (in degrees). Any downtilts
above the maximum will not be modified in the optimisation.
Min Diff at Same Height specifies the minimum permitted angular distance (in degrees) that
has to be maintained if antennas for the same technology and cell layer (if applicable) are
positioned at the same height.
Min Value sets the minimum antenna height that is permitted (in m). Any antennas below the
minimum will not be modified in the optimisation.
Max Value sets the maximum antenna height that is permitted (in m). Any antennas above
the maximum will not be modified in the optimisation.
Max Change defines the maximum permitted change from the respective original value in the
Site Database (in m).
The original parameter settings (for example, antenna types) are always included
in the optimisation.
Any antenna parameters with values outside the {min, max} range set in the
respective constraints will not be changed during the optimisation.
Page 141
The antenna type, electrical downtilt, mechanical downtilt and total downtilt
actions/constraints are interdependent. For example, you cannot consider changes
to the mechanical downtilt without enabling changes to the electrical and/or total
downtilt as well.
If you want the Optimiser to consider a network configuration that allows antenna
sharing (implicit or explicit), you must ensure the
option is enabled
on the Antenna Constraints tab for the relevant Properties in the Site Database. For
more information, see Configuring Property Antenna Constraints on page 42. There
are also options related to antenna sharing within the Settings. For more information,
see Specifying the Settings on page 86.
Depending on the antenna planning actions and constraints that you have specified
for the considered cells:
Page 142
In the case of any considered antennas that are 'explicitly' shared, their
configuration (for example, mechanical tilt) can be modified (jointly) during the
optimisation, but the respective antennas will remain explicitly shared.
In the case of any considered antennas that are 'implicitly' shared, their sharing
status may change during the optimisation. For example, antennas that were
initially shared may each end up having different configurations, and become
non-shared.
In the case of all other considered antennas, their sharing status may change
during the optimisation. For example, antennas that were not initially shared may
each end up having the same configuration, and become implicitly shared.
Whenever antennas are shared, the number of actions and respective action costs
are considered appropriately, and are only counted once for the same physical
antenna object. For example, a mechanical tilt change to an antenna shared between
two cells would only be counted once.
To
PA Output Power
BTS Type
If you have selected PA Output Power, the constraints described in this table become
active:
This Constraint
Enables You To
Page 143
This Constraint
Enables You To
Set the maximum permitted change from the current value in the cell (in dB).
Changes Allowed
Define how the current value will be allowed to change within the set ranges:
'Any' allows both higher and lower values to be examined during the optimisation.
ff
When defining GSM power planning actions and constraints, you should
remember the following:
The original parameter settings (for example, BTS equipment types) are always
included in the optimisation.
Any power parameters with values outside the {min, max} range set in the
respective constraints will not be changed during the optimisation.
To
Max TX Power
Pilot Power
HSDPA Power
Max DL Power Per Connection Enable the maximum power per connection to be changed.
Node Types
If you have selected any of the above power options, the constraints described in this
table become active:
This Constraint
Enables You To
Set the maximum permitted change from the current value in the cell (in dB).
Specify that the pilot power (for all the cells associated with the template) is always
adjusted in proportion with the Max TX Power. This maintains the same ratio that exists in
the starting plan.
When this is selected, the Change Step and the Changes Allowed become read-only,
and the values that you set for the Max TX Power are used instead.
Changes Allowed
Page 144
Define how the current value will be allowed to change within the set ranges:
'Any' allows both higher and lower values to be examined during the optimisation.
When configuring UMTS power planning actions and constraints, you should
remember the following:
The original parameter settings (for example, Node equipment types) are always
included in the optimisation.
Any power parameters with values outside the {min, max} range set in the
respective constraints will not be changed during the optimisation.
When you are using the Fixed % of Max TX Power checkbox (for Pilot Power,
HSDPA Power or Max Power Per User):
You should ensure that all the values you set for the Max TX Power planning
action are compatible with your overall objectives
If the Fixed Ratio and/or Uniform Power constraint has been enabled, the
Optimiser will not change the Node Type from one that supports HSDPA to one
that does not, and vice versa.
If a cell considered by the Optimiser cannot support HSDPA (in other words, none
of its available Node Types support HSDPA or it is not supported on the cell), the
Optimiser will not allow any changes to the HSDPA Power and will not consider
the HSDPA-specific Fixed Ratio and Uniform Power constraints for this cell.
To
If you have selected any of the above power planning actions, the constraints
described in this table become active:
This Constraint
Enables You To
Set the maximum permitted change from the current value in the cell (in dB).
Page 145
This Constraint
Enables You To
Changes Allowed
Define how the current value will be allowed to change within the set ranges:
'Any' allows both higher and lower values to be examined during the optimisation.
Any power parameters with values outside the {min, max} range set in the
respective constraints will not be changed during the optimisation.
To
TX Power
(Fixed and Mobile)
If you have selected the above power planning action, the constraints described in this
table become active:
This Constraint
Enables You To
Set the maximum permitted change from the current value in the cell (in dB).
Changes Allowed
Define how the current value will be allowed to change within the set ranges:
'Any' allows both higher and lower values to be examined during the optimisation.
When defining WiMAX power planning actions and constraints, you should
remember the following:
Page 146
Any power parameters with values outside the {min, max} range set in the
respective constraints will not be changed during the optimisation.
If you have selected any of the above options, the constraints described in this table
become active:
This Constraint
Enables You To
Min Value
Max Value
Set the maximum permitted change from the current value in the cell.
Changes Allowed
Define how the current value will be allowed to change within the set ranges:
'Any' allows both higher and lower values to be examined during the optimisation.
When configuring LTE power planning actions and constraints, you should
remember the following:
Any power parameters with values outside the {min, max} range set in the
respective constraints will not be changed during the optimisation.
Page 147
Page 148
This table describes the action-constraints that you can configure for candidate
planning:
Select
To
Specify the minimum and maximum acceptable distance (in m) between any PropertyProperty pairs that are first-order neighbour pairs (in other words, nominal-nominal,
nominal-candidate or candidate-candidate) considered in a plan.
You can then choose to modify the way that nominal-nominal first-order neighbour pairs
are considered, by selecting to:
Candidate Locations
Ignore the minimum and maximum distances during the first optimisation iteration
only
Specified in the Site Database Grid Constraints tab for each considered nominal
Property
If the number of globally generated locations exceeds 100 per Property, a warning
message is produced so that the step value is then adjusted (either automatically or
manually).
Forbidden Areas
Define areas that should not be considered as potential site locations, including the
original (Site Database) nominal Properties.
This picture shows an example of the actions and constraints for selection planning:
Page 149
This table describes the action-constraints that you can configure for selection
planning:
Option
Description
Site
Site can be switched ON or OFF (= all its sectors ON, or all its sectors OFF).
If required, the option to set a site as 'Site Always Active' can be used in Site Planning, but it means
that the site would, in effect, be 'read-only'.
Sector
Sector can be switched ON or OFF individually, according to the sector configurations on the Grid
Constraints tab for the site in the Site Database.
Sector planning cannot be used unless allowable configurations have been generated on the Grid
Constraints tab.
The option to set a site as 'Site Always Active' can be used to ensure that at least one sector of that
site always remains active.
Property
All sites of a Property can be switched ON or OFF (= all its sites and their cells ON, or all its sites and their
cells OFF).
This option only has an effect where there are two or more sites co-located on the same Property
(otherwise site selection should be used).
Whenever you select or de-select this option, all the sites co-located on that Property are always updated
consistently. This is so that the Property option can never be inconsistently selected for co-located sites.
All the other network level options behave independently between co-located sites.
Any site set as 'Site Always Active' can be used in Property planning. However, if all of a Property's
sites are set as always active, the Optimiser would have no flexibility for that Property.
Sites that are assigned with this option are always used in every solution the Optimiser generates. This
means that the site will never be 'switched off' during optimisations.
The way that this option may affect Selection Planning (Site, Sector, Property) is described in each of the
rows above.
Within the left-hand pane of the Optimiser Workflow, select Plan Manager.
5
Page 150
Continue with the Add button until you have specified all the required filtertemplate combinations. (You can delete a row by clicking .) Here is an example:
Click OK. The assignments you have made now appear in the Action-Constraints
dialog box.
When you have finished, you can close the Action-Constraints dialog box.
There are three points you should note regarding template assignments. Two of
these points relate to default templates that are always available to you (these are in
addition to the templates that are user-defined):
Read Only template - when this is assigned to a filter, all the 'Fixed' checkboxes (for
the objects in the associated filter) become automatically selected in the ActionConstraints dialog box.
Unchanged template - when this is assigned to a filter, nothing is changed (for the
objects in the associated filter) in the Action-Constraints dialog box. This option is
necessary because you may want, for example, to assign a template for just one or
two planning mechanisms, and leave the other(s) unchanged.
When you create a template, it is likely that you will not have selected all the
potential action-constraints in that template. When you assign that template to a
filter, the 'Fixed' checkboxes for the action-constraints that were unselected in the
template become automatically selected in the Action-Constraints dialog box, for
the objects in the associated filter.
Page 151
For example, if a template has only Azimuth (Antenna mechanism) selected, the
other action-constraints (Tilts, Heights, Device/Pattern) would all be set to 'Fixed'
in the Action-Constraints dialog box, after the template assignment.
All templates (read only, leave unchanged and user-defined) are assigned
separately to each individual planning mechanism. Therefore, the above points are
valid independently for each mechanism.
For more specific information about the 'Fixed' columns, see About the Fixed
Columns for the Action-Constraints on page 124.
If you want to reassign some of your currently assigned templates, but not all, you
can change the template selection in the Action-Constraints dialog box to 'Custom' on
the objects that you don't want to modify, before pressing the Re-assign All Templates
button.
Page 152
CHAPTER 7
Optimising a Network
The Optimiser Workflow enables you to perform the vast majority of tasks within
ADVANTAGE from a single dialog box. This incorporates the setting up of
parameters, costs, constraints and targets, and generation of optimisation Plans.
It comprises a number of main options in the left hand pane, and each of these enables
you to access a range of specific options that are displayed in the right-hand pane.
This chapter focuses on how to run an optimisation, and how to interpret the
feedback.
To start the Optimiser Workflow:
From the Optimiser menu, click Workflow
- or Click the
Set up a project with the necessary planning data, including traffic (if applicable).
Defined the action and/or unit-related costs, if you want the optimisation to
consider such costs (for example, costs for antenna azimuth changes).
The above step is optional.
Created a plan (defining the area, cell filters, and, optionally, vectors), using the
Plan Manager. For more information, see Using and Managing Plans on page 101.
Page 153
For a problem cell related optimisation, you must run Problem Cell Identification
and/or define cell-specific weights.
This then enables you to start an optimisation.
Running an Optimisation
Before you can run an optimisation, you must have created at least one plan.
(If appropriate, you can also choose to optimise a delta plan.)
For a full list of the prerequisites, see Prerequisites for an Optimisation on page 153.
To start an optimisation:
Page 154
on the main
Select the appropriate plan, and click the Optimise button. The Optimiser dialog
box appears:
Set the minimum time interval for the 'best cost value' plan to be saved (at each
time interval, a new delta plan is saved only if the best cost value is less than the
previous saved value). To do this, in the Delta Plan Writing Interval edit box, type
the number of minutes and click Set.
At the point where you stop the optimisation, an additional delta plan is saved
(according to the same criteria above), as if the next time interval had been
reached.
5
If you want to view statistics information using the Statistics Graph, Statistics
Details or Report buttons, ensure that the Calculate Statistics checkbox is selected.
Monitoring an Optimisation
When you have started an optimisation, the Optimiser runs. This picture shows an
example of a running scenario:
Description
Starting configuration
Modification strategy
The cost for the best configuration that the Optimiser has found so far.
The absolute gain value represented by the difference between the starting
and best cost values; this gain expressed as a relative percentage.
The total number of iterations that have taken place up to this point in the
optimisation. This includes the iteration required for optimisation initialisation
and (if applicable) any iterations rejected based on the Max Objects/Actions or
Max Degradation criteria.
Page 155
Value
Description
Accepted: The number of states that have been accepted by the Optimiser as
valid (that is, a state that has broken no hard constraints such as Max
Degradation, Max Objects/Actions, Min/Max Inter-Site Distance).
Generated: The number of performed states.
A/G: The 'Accepted to Generated' ratio.
The time the Optimiser was started, the time it was stopped, and the elapsed
time.
While the optimisation is running, you can view a variety of useful feedback
information, by clicking any of the following buttons:
Cost Graph - for a graphical representation of the best, current and generated cost
values for each iteration
Statistics Graph(s) - for the initial and best plan values for the selected series
Cost Details - for a variety of information about the costs related to the
optimisation
Statistics Details - for the statistics for the initial iteration and the most recent best
plan
Page 156
You can use this feedback to assess whether a satisfactory cost value has been
achieved, and also to see the pattern of values generated by the Optimiser.
To zoom in on a particular section of the graph:
1
Click and hold down the left mouse button on the graph where one corner of the
required section will be and drag the mouse to create a box.
Page 157
To select what information is shown on the graph, click Series, and in the dialog box
that appears, select the required categories of information. Then click OK.
To zoom in on a particular section of the graph:
1
Click and hold down the left mouse button on the graph where one corner of the
required section will be and drag the mouse to create a box.
Page 158
The number of pixels in the area that will be considered by the Optimiser
The contribution of each considered cost category (and its components) to the
starting, best, current and generated optimisation cost (the relevant metric
selection/weights and multiplier coefficients are also displayed)
The examined optimisation states (or iterations) and the respectively generated
optimisation cost (the best and current cost values are also displayed)
To get details of different cost values besides the current ones, ensure that the Log
states option is selected.
This picture shows an example:
You can also use this information to check the entire optimisation setup after an
optimisation has started. For example, you can ensure that the weights and multiplier
coefficients are correctly configured and that the optimisation targets are realistic and
can be met.
Page 159
GSM
UMTS
CDMA2000
EV-DO
Fixed WiMAX
Mobile WiMAX
LTE
You can view these details in terms of overall coverage, per clutter threshold and/or
per vector threshold. You can also view action information, and cost information.
Page 160
If appropriate, you can choose to optimise a delta plan. If you begin a new
optimisation, the statistics information for the previous one will be deleted. However,
if you continue optimisation from the last generated delta plan, the statistics
information for the last optimisation will still be available.
The optimisation report provides details of the actions, statistics and costs for the
starting plan and each subsequent best plan. This picture shows an example:
You can produce a similar report (for a specific delta plan) after you have stopped
the Optimiser, by selecting the appropriate plan in the Plan Manager section of the
Workflow, and clicking the Analysis button.
You may be able to choose which customised report format you want to use for
this report type. For more information, see Selecting Report Formats on page 99.
Page 161
Examining different types of actions and/or the impact of limiting the number of
actions further
Modifying the optimisation targets and/or approach through the Strategy and
Settings and (depending on the setup and user permissions) the algorithmic setup
34.
Page 162
CHAPTER 8
Access the rollout planning functionality, in order to assess and sequence the
potential network changes
You can evaluate a single plan, or compare two plans, in terms of their performance
(with respect to measurements and optimisation metrics).
As part of the network evaluation, statistics similar to those available in ASSET can
also be generated. The statistics include array-based metrics such as coverage and
interference (presented per clutter type and/or per vector) and, if applicable, servicebased metrics. In addition, feedback based on the specified optimisation metrics can
be provided.
The performance achieved for each configuration is compared with the user-specified
targets and presented (in terms of absolute and/or relative values) on a traffic and
area basis.
Page 163
For optimised (delta plan) network configurations, the considered actions and action
costs are also included in the analysis. If this is the case, the analysis will generate a
report with separate information on:
Actions
Statistics
Costs
You can use the produced reports and/or graphical information to determine how
good a plan is, or the number/cost of the required optimisation actions (if applicable).
You can also use the Analysis dialog box to access the rollout planning functionality,
in order to assess and sequence the potential network changes for either a Plan or
Delta Plan. For more information, see About Rollout Planning and Partial Plans on
page 169.
As an ADVANTAGE user, you can use parts of the related ENTERPRISE analysis
functionality in addition to the ADVANTAGE-specific options. With specific regard
to measurements, please see Using Measurement Data on page 187.
Description
Type
Actions
Statistics
Optimisation Costs
If you have a Financial Analysis licence, you can also analyse financial metrics
such as Revenue, Expenditure, Net Income and Return On Investment (ROI). For
more information see the Financial Analysis User Reference Guide.
Page 164
Set up a project with the necessary planning data, including traffic (if applicable).
For more information, see the ENTERPRISE and ASSET User Reference Guides.
Created (or have access to) a plan. For more information, see Using and Managing
Plans on page 101.
Ensure that you have performed the required preparation steps, as described in
Prerequisites for Running an Analysis on page 165.
Page 165
In the Analysis dialog box, the selected plan appears as the Base Plan.
(If you want to select a different plan, you can do this by clicking the browse
button
.)
5
To generate the report, click the Report button, then select the format for your
report, and click OK.
This report is similar to the Optimisation report (available from the Optimiser).
The difference is that this report focuses on a specific plan or delta plan.
Here is an example:
Page 166
When you have finished, in the Analysis dialog box, you can either click Reset to
analyse or compare other plans, or you can click Close.
You may be able to choose which customised report format you want to use for
this report type. For more information, see Selecting Report Formats on page 99.
Ensure that you have performed the required preparation steps, as described in
Prerequisites for Running an Analysis on page 165.
Select one of the two plans you want to compare, and click the Analysis button.
In the Analysis dialog box, the selected plan appears as the Base Plan.
(If you want to select a different plan, you can do this by clicking the browse
button
.)
In the Analysis dialog box, for the Compare Plan, click the browse
and select the other required plan.
button,
If required, click the Compare Options button if you want to set default values for
comparing array pixels where one has a server and one does not.
Click Analyse to perform the comparison analysis. When the analysis has finished
running, the Report button will become active.
To generate the reports, click the Report button, then select the format for your
reports, and click OK.
10 When you have finished, in the Analysis dialog box, you can either click Reset to
analyse or compare other plans, or you can click Close.
Page 167
You can also view the comparison analysis results in the Map View window. For
information on how to do this, see Displaying Plan Comparison Results in the Map
View on page 168.
Ensure that you have a Map View window showing the considered network
configuration(s). If not, you can select the region(s) for the plans using the Plans
heading in the Data Types list:
On the Map View toolbar, click the Show Data Types button
Information & Control button
Page 168
From the list that appears, select the array type that you want to view and click
Redraw to view the related analysis results:
To define how the array is displayed, double-click the required array and edit the
display properties in the dialog box that appears. You can set the following
display options:
Page 169
For ADVANTAGE users, this functionality can be used with plans or delta plans.
Here are two examples:
The Rollout Planning functionality is accessible from the Analysis dialog box. The
Analysis dialog box, in its normal usage, provides the ability to analyse your network
configurations based on any user-selected metric, and then generate analysis reports
that contain single columns per metric. However, the added benefit of the Rollout
Planning functionality is that it enables you to sort, re-analyse and produce a
cumulative report with multiple columns per metric.
In summary, after performing an analysis, you can use this functionality to:
1
Re-analyse.
Page 170
All new network elements of a plan (plan, delta plan or partial plan) always appear
in the Ranking list.
The existing network elements of a delta plan (or partial plan from a delta plan)
appear in the Ranking list only if they have been changed by the Optimiser.
The existing network elements of a plan (or partial plan from a plan) all appear in
the Ranking list if there are not any new elements in the plan.
Page 171
You can:
Show the columns for Absolute Values and/or Additional Improvement in the
dialog box (this has no impact on the report, which always includes both types
of information).
To generate a fresh analysis of your changes (taking the new sequence into
account), click Analyse.
When the analysis has finished running, the Report button will become active.
Click the Report button, then select the format for your report, and click OK.
This report enables you to view and assess the cumulative statistics (relating to the
chosen metrics) for each cell, site or Property. Here is an example of a report, after
ranking the above results by coverage:
This example report has been simplified (rows have been removed) for clarity.
In this example, the 'partial plan' values in the columns (when read left to right)
illustrate how the overall coverage value increases as each additional site/node in
the sequence is considered for inclusion in the plan. Obviously, at the same time as
the summed value increases, the individual coverage value for each site/node
tends to diminish.
A separate report will be generated for each of the metrics that you specified
when setting up the analysis. For example, if you selected Coverage and Quality,
two separate reports would be presented.
7
Page 172
In the Rollout Planning dialog box, if you want to change the element sequence
and re-analyse, you can now click the Reset button.
Check that you have finished re-sequencing and analysing your changes in the
Rollout Planning dialog box.
Decide which items you want to include in the partial plan (sequence 1 to n).
Click on the row that relates to Sequence n (that is, the lowest ranked item in your
proposed partial plan).
In the example shown here, clicking the row relating to Sequence 6 would create a
plan that includes the items in the top six rows (1 to 6 inclusive):
A new partial plan is automatically created, and listed in the Workflow dialog box,
under the plan from which it was created. Here is an example:
Page 173
Page 174
CHAPTER 9
Identifying Problems in a
Network
ADVANTAGE enables you to focus the optimisation process, either automatically or
manually, on the areas or cells of the network that are underperforming. The focus is
on the identification of:
The problem area and/or cell identification analysis allows you to define the expected
performance both in terms of design targets for offered services, and also in terms of
area served or traffic captured, or both. This identifies the areas of poor performance
that are critical to network efficiency. By correlating the performance achieved and
the area and/or traffic served, ADVANTAGE can quickly improve the achieved
revenue from the network.
This functionality is only available for GSM and UMTS.
Low Coverage
Low Quality
Low Dominance
For information on defining problem criteria for areas, see Configuring Problem Area
Thresholds on page 176.
Problems with cells may include those that:
Are associated with coverage problems within their best server area
Are associated with quality problems within their best server area
Page 175
For information on defining problem criteria for cells, see Configuring Problem Cell
Thresholds on page 178.
After you have set the necessary area/cell problem criteria, you can identify
problematic areas or cells by using Problem Area and Cell Identification. For
information, see Identifying Problem Areas and Cells on page 180.
You can also specify (or produce automatically) cell-specific weights that can be
considered during optimisation. The problem cells can subsequently be targeted by
the automatic optimisation algorithm. This ensures that increased priority is given to
these cells, enabling more efficient automatic optimisation. For information, see
Configuring Problem Cell Weights on page 185.
Low Coverage
Low Quality
Low Dominance
The array used during the identification process for Low Coverage and Low
Dominance is the Best Server array (GSM) or Best Pilot Server array (UMTS).
The array used during the identification process for Low Quality is the Average
Connection (C/I) array (GSM) or Best Ec/Io array (UMTS).
Page 176
From the Tools menu, point to Problem Identification, then point to Problem Area
Thresholds, and then click the required technology (GSM or UMTS).
Threshold
Low Coverage
Low Quality
Low Dominance
Max Servers
The above criteria also depend on whether at least one of the associated
traffic/area thresholds is also exceeded, as described below.
3
On each of the three tabs, you can also set associated threshold values as follows:
Category
Threshold
Low Coverage
Low Quality
Low Dominance
Low Coverage
Low Quality
Low Dominance
If either of the above values is exceeded, the area may qualify as problematic,
depending on the associated value for Low Coverage, Low Quality or Low
Dominance.
4
When you have completed your changes, click Apply, and then click Close.
Example
Here is an example, valid for either GSM or UMTS:
In this example, on the Low Coverage problem area category, the criteria for a
contiguous low coverage (that is, problematic) area have been set to any urban area:
Page 177
From the Tools menu, point to Problem Identification, then click Problem Cell
Thresholds.
In the dialog box that appears, expand either GSM or UMTS, as appropriate.
Expand the required category, and select the threshold you want to configure. The
following table describes these thresholds:
Category
Threshold
Description
Large # of Dropped
Calls
Max
Max
Large # of
Handovers
Low Coverage
Low Quality
Page 178
As above.
Min Traffic
Min Area
As above.
As above.
Min Traffic
Min Area
As above.
Category
Threshold
Description
Low Traffic
As above.
Min (km)
As above.
Max (km)
Small Area
High Traffic
Large Area
Notes :
Within the Problem Cell categories that contain a pair of thresholds, the two
thresholds operate on an OR basis. Within the Low Coverage and Low Quality
categories, the first pair of thresholds operate on an OR basis, but each one also
operates on an AND basis with its respective Min Traffic OR Min Area
threshold.
Dropped Call and Handover problem cells will only be identified if you have
corresponding network data. Furthermore, if you have more than one type of
data for these (for example, DroppedCallsLev and DroppedCallsQual),
ADVANTAGE combines the respective data into a single value per cell for
problem cell identification purposes.
In the Values column, double-click a value and type the new one.
When you have completed your changes, click Apply, and then click Close.
Page 179
Set up a project with the necessary planning data, including traffic (if applicable).
For more information, see the ENTERPRISE and ASSET User Reference Guides.
Created a plan (defining the area, cell filters, and, optionally, vectors), using the
Plan Manager. For more information, see Using and Managing Plans on page 101.
Defined the Problem Area and/or Cell Thresholds, as appropriate. For more
information, see:
From the Tools menu, point to Problem Identification, then click Problem Area
and Cell Identification.
Select the appropriate plan, and click OK. This is necessary to focus on the
relevant area and cells.
In the dialog box that appears, on the Problem Area Cell Identification tab, select
the checkboxes next to the parameters that you wish to be considered when
identifying problem areas and cells.
If you select one of the problem cell types that relate to a similar problem area
type (Low Coverage, Low Quality, Low Dominance), then the corresponding
problem area type is also selected. In these cases, you cannot identify problem
cells independent of the area they are associated with.
Click Start.
Problem areas and cells are identified.
Page 180
When you have run the identification, you can generate one or both of these
reports:
Click the appropriate button, and then select the type of report you want to
generate, and click OK.
You can also specify (or produce automatically) cell-specific weights that can be
considered during optimisation. The problem cells can subsequently be targeted by
the automatic optimisation algorithm. This ensures that increased priority is given to
these cells, enabling more efficient automatic optimisation. For more information, see
Configuring Problem Cell Weights on page 185.
The report details the number of problem areas, the amount of affected traffic (given
in E, but this can represent any unit) and the size of the affected area (in km).
To quickly identify the most or least problematic area, use the Sort
Ascending/Descending function in Excel.
As well as generating a report, you can also view problem area data in the Map View
window. For information on how do this, see Displaying Problem Area Data in the
Map View on page 182.
ADVANTAGE 8.1 User Reference Guide
Identifying Problems in a Network
Page 181
Ensure you have a Map View window showing the considered network
configuration(s). If not, you can select the region for the plan using the Plans
heading in the Data Types list:
On the Map View toolbar, click the Show Data Types button
Information & Control button
Select the appropriate problem areas from the Problem Areas folder.
Click Redraw.
The problem area data will be displayed.
This picture shows UMTS Coverage Problem Areas in the Map View window:
Page 182
If you want to display several problem areas at once, and view information on each as
you hover over the Map View:
1
In the Map Information Field Selector, select the required problem areas, and then
click Add.
Click OK.
If you want to define colour profiles for different problem areas, double-click on
the problem area in the Map Information and Control dialog box. In the dialog box
that appears, on the Problem Area tab select a colour to represent the starting value,
and on the Selected Areas tab choose which problem areas to show on the Map View
window.
Page 183
As well as the summary, each report has a separate page for each problem type
ADVANTAGE has identified. In the example above, the problem of Low Coverage is
identified. This picture shows the Low Coverage tab:
Notes :
Page 184
The report also shows the problem areas related to the respective problem cells,
since these are considered when identifying problematic cells.
Traffic values in the summary and separate problem type reports are given in E,
but this can represent any unit.
Identify the problem cells in your network. For more information on how to do
this, see Identifying Problem Areas and Cells on page 180.
From the Tools menu, point to Problem Identification, then click Problem Area
and Cell Identification.
Select the appropriate plan, and click OK. This is necessary to focus on the
relevant area and cells.
In the Problem Area and Cell Identification dialog box, click the Problem Cell
Weights tab.
Based on the problem cells identified:
Cell weights are produced (if applicable), and displayed in the cost multiplier
column. The default weight is 1.0000 (no priority) and higher values indicate a
more problematic cell and therefore a greater priority for the optimisation.
This picture shows an example, where 3 problem cells have been identified:
You can choose to manually edit the automatically produced weight values, and
also select/deselect any of the cells.
Page 185
From the Tools menu, point to Problem Identification, then click Problem Area
and Cell Identification.
Select the appropriate plan, and click OK. This is necessary to focus on the
relevant area and cells.
In the In the Problem Area and Cell Identification dialog box, on the Problem Cell
Weights tab, double-click the required cell's Cost Multiplier value and type the
new value. The default weight is 1.0000 (no priority) and higher values indicate a
more problematic cell and therefore a greater priority for the optimisation.
For example, a cost multiplier of 2.0000 would give that cell a weight twice that of
the other cells. You can also use lower values if you require. You can even use 0, in
which case the cell will be included in the optimisation but will not contribute to
the cost calculations.
If you edit the weight of a problem cell, it is automatically selected.
To remove the manual problem cell weights and use the default unitary weights:
Page 186
Select the appropriate technology level checkbox, and then deselect it, so that all of
the cell-specific checkboxes are automatically unselected.
CHAPTER 10
Network data
This data (such as performance engineering data), can provide information that is
crucial to understanding the performance of your network.
You can import cell (and cell pair)-specific information into ADVANTAGE, which
is spread intelligently in the area of interest and used in the analysis/optimisation.
In a similar way to ASSET, you can also use the standard ENTERPRISE traffic
functionality in ADVANTAGE to create/load/modify a traffic array, whether live
traffic is considered or not. For more information on this, see the ASSET User
Reference Guide.
Using measured data, ADVANTAGE can model the network more accurately, basing
its results on measured performance, and consider the measurements in the analysis
and optimisation.
Network data spreading is available for GSM and UMTS only. However, the use
of measurement data functionality is available for all technologies.
Page 187
Page 188
In the first example, the areas of green represent low traffic density. In the second
example, the areas of red represent a high number of dropped calls due to reasons
other than signal strength or interference.
Page 189
The way that traffic is spread by ADVANTAGE alleviates the above problems,
because the traffic spreading process acknowledges the likelihood that a pixel may be
covered by any of the predicted servers/cells. The calculated coverage probability
and the traffic per cell (from the imported network data) are used to generate a
system of equations, which are solved so that the predicted and measured data are
consistent. The two end products of traffic spreading are a technology-specific traffic
array and a set of cell-specific traffic modifiers.
Page 190
The respective minimum signal strength value specified in the Data Array
Wizard
Use This
Mechanism
To
Example of Network
Data spread this way
Default Naming
Convention in
ADVANTAGE
Traffic
Traffic
Traffic
Weighted Average
Congestion probability
Congestion
Even
DroppedCallsOther
Signal Strength
Spread data based on the traffic, clutter Dropped calls due to signal
and coverage probability for each cell;
strength
this spreading process is actually an
optimisation that will identify the
minimum signal strength threshold
below which calls are dropped, based
on the imported data and the considered
network configuration and RF
Thresholds in the Optimiser Workflow.
DroppedCallsLev
Interference
DroppedCallsQual
Relative Signal
Strength (1)
HandoverLinkBudget
Relative Signal
Strength (2)
HandoverLev
Relative Interference
and (absolute) Signal
Strength
Page 191
Use This
Mechanism
To
Example of Network
Data spread this way
Default Naming
Convention in
ADVANTAGE
Relative Signal
Spread data based on the traffic,
Handovers due to interference N/A
Strength and
coverage probability and interference
(absolute) interference probability for each cell pair, taking into
account the relative signal strength and
absolute interference thresholds defined
in the Site Database and, if not, the RF
Thresholds in the Optimiser Workflow.
For more information on the RF Thresholds and Settings, see About the Optimiser
Workflow on page 33.
For more information on configuring networks, see the ASSET User Reference Guide.
Description
The first row must contain a description of the data, for example, Network Data Per Cell.
COMPULSORY
Page 192
Table sheet
Description
The first row must contain a description of the data, for example, Network Data Handovers.
OPTIONAL
If you are using AIRCOM OPTIMA, the import file format could match the
(optional) report generated by the Data Array Wizard. This enables you to import
from an OPTIMA database, generate a report, and import the data from the report
whenever the database is not accessible.
Ensure you have a column with the required counter name, containing the data of
interest, in the Network Data Excel file.
If an OPTIMA database is used, only the table and view for the consideration of
network data should be appropriately defined. If you require assistance in setting this
up, please contact Product Support (see Obtaining Support on page 14).
Page 193
Example of the first sheet (Per Cell) of an Excel spreadsheet used to import network data
Example of the second sheet (Handovers) of an Excel spreadsheet used to import network data
Using the ADVANTAGE-specific spreading mechanisms, you can import and spread
on a pixel basis any Key Performance Indicator (KPI) data. The default types of
network data that you can import in ADVANTAGE are:
Traffic levels
Congestion percentage
Handover statistics
For details about how other data types can be imported, see Configuring the
Format for Importing Network Data on page 192.
Prerequisites
Before spreading network data, you (or your administrator) need to have:
Set up a project with the necessary planning data. For more information, see the
ENTERPRISE and ASSET User Reference Guides.
Created a plan (defining the area, cell filters, and, optionally, vectors), using the
Plan Manager. For more information, see Using and Managing Plans on page 101.
From the Arrays menu, point to Network Data and click Data Array Wizard.
In the dialog box that appears, select the appropriate plan. This contains the
required information in terms of cells and region, and, if appropriate, vectors (in
which case the data spreading will be restricted accordingly).
To specify the folder where the cached traffic arrays will be saved, click the
button in the Cached Array Path pane, browse to the folder where you want to
save the arrays, and click OK.
Specify the minimum signal strength for GSM and/or UMTS as appropriate.
Network data will only spread to areas where the signal strength is above this
threshold.
Page 195
Click Next.
To import from a file, select Import from file and click the Browse button.
Locate the file, click Open and then click Next.
Select the checkboxes for the specific network data types you want to spread, and
(if you wish to change the default mechanism for that type) click in the Spreading
Mechanism column and choose from the resulting list. Each list is dependent on
the specific network data type (for example, only the handover-related spreading
mechanisms are available for data described as HandoverLinkBudget). If required,
you can also enter or modify the unit for each network data type.
If you are importing from an OPTIMA database, you can choose to filter the
data, by selecting a start date and an end date and a time. (Currently, the most
recent data matching these conditions is loaded).
Click Next.
In the dialog box that appears, select the format for your report. If you choose
a text file, select a program to open it with.
Click OK.
The results are displayed in your chosen format. You can save the report if
required.
10 Click Finish. The network data is spread, and a summary list is displayed:
11 Click Done.
Page 196
After you have spread network data, you can then display it, in either:
Open a Map View window displaying the area you want to view.
On the Map View toolbar, click the Show Data Types button
Information & Control button
From the list of Data Types, expand Processed Performance Data, then the
required technology (GSM or UMTS), and then select the data you want to
display.
Click Redraw.
The chosen network data array is displayed.
If you want to change how the data is displayed, double-click on the data you
want to display in the list of Data Types. Select the start colour, the Start value
(this is the minimum value to be displayed), the Interval value (this is the step
value), as well as the Units (for example, Erlangs). Click OK and then click OK and
Redraw.
If you want to view the value per pixel for this array, ensure Show Map View
Gadgets is selected from the View menu on the Map View window.
In the dialog box that appears, in the Available Items pane, select Processed
Performance Data, and click the
button.
Click OK.
Double-click the 'Please select Data Array' text at the bottom of the Map View
window:
Page 197
10 In the dialog box that appears, select the array for which you want to display
information, and click OK.
11 As you move the mouse cursor over the map, the pane at the bottom of the Map
View window displays the network data value for the specific pixel under the
cursor:
Page 198
Ensure you have opened the Map View window, and displayed the area of
interest.
From the Arrays menu, point to Network Data and click Data Pixel Analyser. The
Data Values dialog box appears.
Hover the mouse pointer over the pixel where you wish to view the data values.
The corresponding values for this location are displayed:
The types of data you can view correspond to the four tabs on the Data Values dialog
box. The following table describes these tabs:
Click this tab
To view
Spread Data
The estimated values per pixel for the data imported through spreading.
If handover data has been considered, information on the estimated traffic in handover
(denoted as Traffic Affected) is also displayed.
Clutter Thresholds
The estimated threshold values per clutter type for the used Spreading Mechanisms that involve
an optimisation; these thresholds are the traffic density for Traffic and the minimum signal
strength and interference thresholds for Signal Strength and Interference (if applicable) spread
data.
You need to have displayed clutter data on the Map View for this to be applicable.
Cell Modifiers
The estimated modifier values per best server cell (pilot for UMTS) for the used Spreading
Mechanisms that involve an optimisation. These modifiers may be required for all the considered
cells and traffic, signal strength and interference (if applicable) spread data to ensure that the
respectively imported (measured) and estimated network data information is identical.
Probabilities
From the Arrays menu, point to Network Data, and click Re-Spread Data.
In the dialog box that appears, select the appropriate plan. This contains the
required information in terms of cells and region.
Click OK.
Once the network data is re-spread, you can view the estimated network data in the
Map View window in the same way as you view spread network data. For more
information, see Displaying Spread Data on the Map View on page 197.
Page 199
You can also re-spread network data, which enables you to view estimated network
data after an optimisation plan has been considered. For more information, see ReSpreading Network Data on page 199.
From the Arrays menu, point to Network Data and click Data Array Operations.
On the Manipulate Data Array tab, select the array you wish to scale.
Type the required scaling (between 0 and 10) into the box, or drag the bar
horizontally to the required scaling value.
Click Close.
From the Arrays menu, point to Network Data and click Data Array Operations.
On the Manipulate Data Array tab, select the first array you wish to combine.
Select the second array, and in the Array Combining pane, click the lower
The two arrays must be of the same resolution and same area.
Page 200
To add, subtract, or multiply the two arrays, select the appropriate button. A new
combined array is created.
If you want to change the name of the new combined array, type the new name.
Click
Click Close.
In the Array Management pane, type in a new name for the array and then click
Rename.
You array is renamed.
In the dialog box that appears, browse to a saved array and click Open.
The array appears in the list.
The array can only be used for editing and visualisation purposes.
On the Manage Data Array tab, select an array and click Save.
In the dialog box that appears, browse to a suitable location in which to save your
file and click Save.
Your array is saved. You can now load the array in the future, rather than re-create
the array.
Page 201
Model Analysis
Neighbour Planning
TMR (*.tmr)
TEMS (*.fmt)
DingLi (*.txt)
Page 202
After they have been generated, measurement-based pathloss files contain the coordinates of the measurement-based pathloss data, and the measurement-based
pathloss values. They are automatically saved into the directories already designated
for the project's normal pathloss prediction files.
If you use them to influence the normal pathloss predictions, the amount of influence
they have depends on the percentage weightings that you specify in the Array
Settings dialog box. You can also use interpolation to influence surrounding pixels
that do not contain measurement-based data. These weightings and interpolation
(and any changes to them) will be automatically invoked whenever you create a
coverage/interference array, or when you run the Simulator, or when you use the
Pathloss Prediction Generator.
ADVANTAGE 8.1 User Reference Guide
Using Measurement Data
Page 203
For full information on loading the original measurement data, and generating
measurement-based pathloss files, please see the Using Measurement Data chapter in
the ASSET User Reference Guide.
Page 204
APPENDIX A
Technical Reference
This appendix provides more in-depth technical information about how
ADVANTAGE works.
Traffic spreading.
The cost function takes the following shape:
Where
( , , ) ( , )
3 5
3 5
6 . These
parameters to be upheld, for example 1 2
relationships are uniquely defined using the Importance (priority) settings on the
General Clutter Parameters tab of the Optimiser Workflow dialog box.
Page 205
Action costs.
These are understood as the budgetary/financial costs of actions (in other words,
changes) performed on the network, such as costs of changing an antenna. Action
costs are calculated as aggregates of user-defined unitary cost values. They are not
normalised in any way, and therefore are proportional to the magnitude of
changes in a given network.
Antenna planning also considers antenna unit costs, while Grid Planning also
considers Property, site and cell unit costs. Strictly speaking, these differ from the
rest of action costs and are only budget-related. Furthermore, it is possible to
consider a number of actions and their respective costs as a single combined action
and cost on a location, Property, site or cell basis.
Performance costs.
These are understood as costs generated for a network based on various
performance metrics such as coverage probability. Contrary to action costs,
performance costs depend on the state of the network, not on the changes
themselves. However, the considered actions influence network performance
indirectly. Performance costs are calculated in percentages based on various
normalisation schemes that ensure their objectivity with respect to networks of
arbitrary sizes.
These costs are broken down into various sub-components so that every subcomponent can be modelled individually and then added to the other subcomponents to produce the overall cost. The synthesis bias is controlled through a set
of multi-stage weights.
Page 206
The cost function f for automatic network optimisation is defined over a constrained
n-dimensional parameter space (as described in About the Network Optimisation
Domain on page 206):
f ACTION ( 0 , ) W 2A
f ACTION
( 0 , )
i
f PERFORMANCE ( ) W i f PERFORMANC
E ( )
i
f Pi ERFORMANCE ( )
k
Wki f Pi ,ERFORMANC
E ( ), ( typeI)
k
k
i
i ,k
f PkERFORMANCE ( ); W i f Pi ,ERFORMANC
E ( ) max{Wk f P ERFORMANCE ( )}, ( typeII)
k
k
f : R
f ACTION, f ACTION
: [0, )
i
i ,k
f PERFORMANCE , f PERFORMANC
E , f PERFORMANCE : [0, )
R PERFORMANCE : [0,100%]
Where:
f ACTION (0 , ) is the total action cost due to changing the network configuration
0
from state
to state
f ACTION
(0 , ) is the action cost generated by one of the action cost components (for
f PERFORMANCE ( )
i
f PERFORMANC
E ( )
(i).
i ,k
f PERFORMANC
E ( )
mechanism (i).
R PERFORMANCE (0 , )
Page 207
2A
, P2A are cost conversion coefficients expressing the number of budgetary cost
Wki are normalised weights combining costs generated by the performance cost
components of the optimisation cost mechanism (i).
Page 208
Concentrate on the region and cells of interest. Use the Plan Wizard to specify the
region and cells of interest, and ignore areas or cells that should not be part of the
optimisation.
Restrict the optimisation calculations to vectors and/or drive test routes (if possible). Use
the option in the Plan Wizard (or the Edit Vectors right-click option) to restrict the
optimisation array and cost calculations to specific vectors and/or drive test
routes.
Do not use a higher array resolution than required. If you can get realistic network
performance results by specifying a low resolution for the optimisation, there is no
point in using a higher resolution.
Restrict the number of servers/cells considered for array generation. If you can get
realistic results (for example, with respect to interference) by specifying fewer
servers/cells for the optimisation, there is no need to use more.
Limit the optimisation cost calculations to a lower number of servers/cells (if appropriate).
Use the Servers/Cells per Pixel option on the Strategy page of the Optimiser
Workflow to do this.
Focus on problematic cells/areas. Use read-only filters (for network objects that
should be considered, but not modified) and/or the Problem Cells options to
ensure that the Optimiser concentrates on cells that are performing badly.
Do not under- or over-constrain the optimisation problem. Make sure that the specified
actions/constraints are reasonable, so that inappropriate configurations are not
evaluated, but also flexible enough to allow the Optimiser to produce the best
possible plan.
Fine-tune the algorithm. The nature of the algorithm is general enough to apply to a
wide range of optimisation problems. Although the algorithm can be fine-tuned
per specific scenario to further maximise its efficiency (the algorithmic fine-tuning
depends on the setup and user permissions), it is not an easy task and must be
approached with caution.
This picture shows a three-dimensional convex hull, whose projection constitutes the
two-dimensional Voronoi diagram for the displayed set of points on the plane:
Page 209
Here are a few remarks on possible optimisation scenarios, which highlight some key
aspects of an optimisation problem:
An optimisation problem may have many local minima, and this can produce
problems for optimisation algorithms that are not capable of escaping them.
Adaptive Simulated Annealing (ASA) is designed to overcome local minima
trapping.
These are different from the global minimum of the cost function, and should
not be confused.
An optimisation problem may not have a global minimum at all. If this is the case,
any sufficiently small cost function value will be appropriate for a parameter
configuration to be regarded as optimum.
With most network optimisation problems involving a large number of variables (as
many as 500), the algorithm that can identify the best possible solution within a
reasonable amount of time must be very sophisticated. The current ADVANTAGE
optimisation algorithm is based on a proprietary adaptation of ASA, specifically
tuned to mobile communications problems. The algorithm combines the reliability of
ASA in identifying the best solution with a sophisticated 'greedy' algorithm designed
to rapidly target the largest immediate gains. A comprehensive research program has
identified major speed benefits (as much as 300% difference in some cases) over the
standard ASA implementation.
Page 210
Page 211
Page 212
Index
A
Action costs
available 75
combining 72
configuring 71
Action-Constraints
about 37
antenna planning 125, 140
dialog box 122, 125
grid planning 135, 147
power planning 125, 143
setting 37
templates 137
Actions
combining 72
setting a maximum number of 71
ADVANTAGE
benefits 21
process flow 31
workflow 33
Algorithms
spreading 205
Analysing and evaluating plans 163
Analysis
for a single plan 165
network improvement 167
network performance 165
to compare plans 167
Antennas
sharing 86, 142
Application environment 19
Arrays
combining 200
deleting 201
loading 201
loading cached traffic 85
renaming 201
saving 201
scaling 200
Assistance, obtaining 11
Auto Plan Setup, using 94, 95, 108
Azimuths, forbidden ranges 40, 130
D
Delta Plans 102
E
Editing
data arrays 201
Element status 96
F
Forbidden Azimuth ranges 40, 130
G
Global Editor
setting constraints in site database 54
L
Loading
cached traffic arrays 85
M
C
Cached traffic arrays
editing 201
loading and deleting 85
Clutter
thresholds 58
Clutter/Vector parameters 58
Combining, action costs 72
Configuring
Page 213
service-based 66
Metrics
array-based 64
degradation 80
service-based targets 66
optimisation settings 86
Spreading, network data 188
Statistics
graphs 158
reports 158, 160
Support
obtaining 14
O
Operational environment, ADVANTAGE 19
Optimisation
Action-Constraints templates 137
antenna 125, 140
grid planning 135, 147
parameters 33
power planning 143
prerequisites 153
reports 155, 160
running the optimiser 155
starting the optimiser 154
strategy 78
thresholds 58
Optimiser Workflow
about 33
using 33
P
Partial plans 169
Per Layer calculations 58, 61, 87
Plan Manager, using 101
Plans
concept 102
creating 104
rejecting 71, 80
Traffic Options 84
using the Plan Manager 101
viewing and using 103
Problem areas, identifying 180
Problem cell weights, configuring 185
Problem cells, identifying 180
R
Reference Guides
summary 12, 13
Rejecting plans
based on max units/actions 71
based on metric degradation 80
Reports
problem area 181
problem cell 184
Re-spreading, network data 199
RF Thresholds 58
Rollout planning 169
S
Sampling, for clutter 58
Shared antennas
about 86, 142
how considered 142
Page 214