GENEX U-Net Wireless Network Planning Software User Manual-Volume II PDF

HUAWEI
GENEX U-Net Wireless Network Planning Software

User Manual - Volume II
V100R001
Huawei Technologies Proprietary

User Manual
Volume
Volume II
Manual Version
T2-030161-20050205-C-1.10
Product Version
V100R001
BOM
31015161
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, P. R. China
Postal Code: 518129
Website: http://www.huawei.com
Email: support@huawei.com
Copyright 2005 Huawei Technologies Co., Ltd.
All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any
means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks
, HUAWEI, C&C08, EAST8000, HONET,
, ViewPoint, INtess, ETS, DMC,
TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium,

M900/M1800,
TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN,
HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye,
Lansway, SmartAX, infoX, and TopEng are trademarks of Huawei Technologies
Co., Ltd.
All other trademarks and trade names mentioned in this manual are the property of
their respective holders.
Notice
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents, but
all statements, information, and recommendations in this manual do not constitute
the warranty of any kind, express or implied.
Summary of Updates
This section provides the update history of this manual and introduces the contents of
subsequent updates.
Update History
Manual Version
T2-030183-20050205-C-1.10
Notes
Initial commercial release
Updates of Contents
None.
About This Manual

Release Notes
The product version of this manual is GENEX U-Net Wireless Network Planning
Software V100R001.
Organization
The manual introduces the functions and features of the U-Net. It also introduces how
to manage the radio data and the geographical data, and how to use U-Net to plan the
network between different technologies, including the early network dimension.
The manual comprises two volumes (totally 15 chapters and one appendix). The
contents of each part are approximately as follows:
Chapter 1 Getting Started introduces the main functions and features of U-Net,
including the install and running environment.
Chapter 2 The Working Environment introduces the operations of the U-Net
interface, including: menu, window, map and browser. At the time, it also introduces the
management of the data list, such as, filter, group and sort.
Chapter 3 Managing Geographic Data introduces the U-Net supported map types
and the operations on the map, such as, create, import, export, delete and so on.
Chapter 4 Managing Radio Network Data introduces the management of the
network data, including the data of site, TRX, antenna and other equipment.
Chapter 5 Managing Computations in U-Net introduces the calculation of regular
analysis and guides the reader how to implement regular analysis, such as coverage
analysis and point analysis. It also introduces the seven propagation models and their
usage.
Chapter 6 GSM/GPRS/EDGE/TDMA Project Management introduces the use of
U-Net in the GSM and GPRS project, including managing and distributing the radio
network resource, managing the traffic data, network dimension and prediction
analysis.
Chapter 7 GSM/TDMA AFP Module introduces the frequency planning function of
U-Net. It introduces the user interface of frequency planning, including automatic
frequency planning and manual frequency planning.
Chapter 8 UMTS/WCDMA Project Management introduces the use of U-Net in the

UMTS/WCDMA project, including the radio network data management, the predication
study, the system simulation and network resource distribution.
Chapter 9 CDMA/CDMA2000 Project Management introduces the use of U-Net in
the CDMA/CDMA2000 project, including the radio network data management, the
predication study, the system simulation and network resource distribution.
Chapter 10 Managing Measurements introduces the two measurement functions of
U-Net: CW measurements and test mobile measurement.
Chapter 11 Co-planning Features introduces the co-planning function of U-Net.
Chapter 12 Import MSI PlaNET Data introduces how to import the data of the MSI
PlaNET project.
Chapter 13 Multi-user Features introduces the multi-user function of U-Net.
Chapter 14 Microwave Links introduces the functions of the microwave link module.
Chapter 15 Radio Network Dimensioning introduces the network functions and
features of U-Net, the setting and operation of each parameter.
Appendix Acronyms and Abbreviations lists all the abbreviations and acronyms in
the manual.
Intended Audience
The manual is intended for the following readers:
z
Technical marketing specialists
Operation & maintenance personnel
Telecommunication administration staff
Conventions
The manual uses the following conventions:
I. General conventions
Convention
Description
Arial
Normal paragraphs are in Arial.
Arial Narrow
Warnings, cautions, notes, table text and tips are in Arial

Narrow.
II. Command conventions

Convention
Description
Boldface
The keywords of a command line are in Boldface.
[]
Items (keywords or arguments) in square brackets [ ] are

optional.
A line starting with the # sign is comments.
III. GUI conventions

Convention
Description
<>
Button names are inside angle brackets. For example, click

the <OK> button.
[]
Window names, menu items, data table and field names

are inside square brackets. For example, pop up the [New
User] window.
Multi-level menus are separated by forward slashes. For

example, [File/Create/Folder].
IV. Mouse operation

Action
Description
Click
Press the left button or right button quickly (left button by

default).
Double-Click
Press the primary mouse button twice continuously and

quickly without moving the pointer.
V. Symbols
Eye-catching symbols are also used in the manual to highlight the points worthy of
special attention during the operation. They are defined as follows:
Caution, Warning, Danger: Means reader be extremely careful during the

operation.
Note, Comment, Tip, Knowhow, Thought: Means a complementary description.

Table of Contents
Table of Contents
Chapter 8 WCDMA/UMTS Project Management ......................................................................... 8-1
8.1 Overview ............................................................................................................................ 8-1
8.2 UMTS Specific Concepts................................................................................................... 8-2
8.3 UMTS Projects Protocol .................................................................................................... 8-3
8.4 Managing UMTS Radio Data............................................................................................. 8-4
8.4.1 UMTS Site Equipment............................................................................................. 8-4
8.4.2 Transmitter UMTS Specific Parameters ................................................................. 8-7
8.4.3 UMTS Cells ............................................................................................................. 8-8
8.5 WCDMA/UMTS Multi-Service Traffic Data ...................................................................... 8-12
8.5.1 Umts Services ....................................................................................................... 8-12
8.5.2 UMTS Mobility Types ............................................................................................ 8-15
8.5.3 UMTS Terminal Equipment................................................................................... 8-17
8.5.4 UMTS User Profiles .............................................................................................. 8-19
8.5.5 UMTS Environments ............................................................................................. 8-22
8.6 WCDMA/UMTS Multi-Service Traffic Cartography.......................................................... 8-26
8.6.1 WCDMA/UMTS Environment Traffic Maps........................................................... 8-27
8.6.2 WCDMA/UMTS User Profile Traffic Maps ............................................................ 8-31
8.6.3 WCDMA/UMTS Live Traffic Maps......................................................................... 8-36
8.7 UMTS Simulations ........................................................................................................... 8-39
8.7.1 Overview ............................................................................................................... 8-39
8.7.2 Managing UMTS Simulations................................................................................ 8-41
8.7.3 UMTS Simulation Process .................................................................................... 8-47
8.7.4 UMTS Simulation Results Summary..................................................................... 8-57
8.7.5 UMTS Simulation Outputs..................................................................................... 8-71
8.8 Specific WCDMA/UMTS Prediction Studies.................................................................... 8-76
8.8.1 Overview ............................................................................................................... 8-76
8.8.2 UMTS Prediction Process ..................................................................................... 8-78
8.8.3 Managing UMTS Predictions ................................................................................ 8-79
8.8.4 UMTS Prediction Studies ...................................................................................... 8-82
8.9 WCDMA/UMTS Resources Allocation............................................................................. 8-98
8.9.1 Overview ............................................................................................................... 8-98
8.9.2 UMTS Neighbours................................................................................................. 8-99
8.9.3 Scrambling Codes ............................................................................................... 8-107
Chapter 9 CDMA/CDMA2000 Project Management.................................................................... 9-1
9.1 Overview ............................................................................................................................ 9-1
9.2 CDMA/CDMA2000 Specific Concepts............................................................................... 9-2
9.3 CDMA/CDMA2000 Projects Protocol ................................................................................ 9-3
i

Table of Contents
9.4 Managing CDMA/CDMA2000 Radio Data......................................................................... 9-4

9.4.1 CDMA/CDMA2000 Site Equipment......................................................................... 9-4
9.4.2 Transmitter CDMA/CDMA2000 Specific Parameters ............................................. 9-7
9.4.3 CDMA/CDMA2000 Cells ......................................................................................... 9-7
9.5 CDMA/CDMA2000 Multi-Service Traffic Data Management........................................... 9-11
9.5.1 CDMA/CDMA2000 Services ................................................................................. 9-11
9.5.2 CDMA/CDMA2000 Radio Configurations ............................................................. 9-15
9.5.3 CDMA/CDMA2000 User Profiles .......................................................................... 9-19
9.5.4 CDMA/CDMA2000 Environments ......................................................................... 9-21
9.6 CDMA/CDMA2000 Multi-Service Traffic Cartography..................................................... 9-25
9.6.1 CDMA/CDMA2000 Environment Traffic Maps...................................................... 9-26
9.6.2 CDMA/CDMA2000 User Profile Traffic Maps ....................................................... 9-30
9.6.3 CDMA/CDMA2000 Live Traffic Maps.................................................................... 9-35
9.7 CDMA/CDMA2000 Simulations ....................................................................................... 9-38
9.7.1 Overview ............................................................................................................... 9-38
9.7.2 Managing CDMA/CDMA2000 Simulations ........................................................... 9-39
9.7.3 CDMA/CDMA2000 Simulation Process ................................................................ 9-46
9.7.4 CDMA/CDMA2000 Simulation Results Summary................................................. 9-56
9.7.5 CDMA/CDMA2000 Simulation Outputs ................................................................ 9-70
9.8 Specific CDMA/CDMA2000 Prediction Studies............................................................... 9-75
9.8.1 Overview ............................................................................................................... 9-75
9.8.2 CDMA/CDMA2000 Prediction Process................................................................. 9-77
9.8.3 Managing CDMA/CDMA2000 Predictions ............................................................ 9-78
9.8.4 CDMA/CDMA2000 Prediction Studies.................................................................. 9-81
9.9 Specific 1xEV-DO Features............................................................................................. 9-98
9.9.1 Defining a (Eb/Nt <-> Max rate) Look-Up Table ................................................... 9-98
9.9.2 Creating 1xEV-DO Specific Predictions.............................................................. 9-100
9.10 CDMA/CDMA2000 Resources Allocation.................................................................... 9-102
9.10.1 Overview ........................................................................................................... 9-102
9.10.2 CDMA/CDMA2000 Neighbours......................................................................... 9-103
9.10.3 PN Offsets ......................................................................................................... 9-110
Chapter 10 Managing Measurements........................................................................................ 10-1
10.1 Managing Measurements Overview .............................................................................. 10-1
10.2 CW Measurement Data Paths ....................................................................................... 10-2
10.2.1 Creation of a CW Measurement Path ................................................................. 10-2
10.2.2 Management of a CW Measurement Path........................................................ 10-12
10.2.3 Using the CW Measurement Window ............................................................... 10-19
10.3 Test Mobile Data Paths ............................................................................................... 10-23
10.3.1 Creation of a Test Mobile Data Path ................................................................. 10-23
10.3.2 Management of a Test Mobile Data Path ......................................................... 10-29
10.3.3 Using the Test Mobile Data Window................................................................. 10-35

ii

Table of Contents
Chapter 11 Co-planning Features.............................................................................................. 11-1

11.1 Overview ........................................................................................................................ 11-1
11.2 Co-Planning Using U-Net .............................................................................................. 11-1
11.2.1 Displaying External Objects in a Current U-Net Project ..................................... 11-1
11.2.2 Allocating Inter-technology Neighbours Manually (Co-Planning) ....................... 11-2
11.2.3 Defining Exceptional Pairs of Inter-technology Neighbours................................ 11-7
11.2.4 Allocating CDMA Neighbours to GSM Transmitters ......................................... 11-11
11.2.5 Allocating GSM Neighbours to CDMA Transmitters ......................................... 11-15
11.3 Co-Planning Using Databases..................................................................................... 11-18
11.3.1 Working in Co-planning with a MS Access Database....................................... 11-18
11.3.2 Working in Co-planning with a SQL Server Database ...................................... 11-19
11.3.3 Working in Co-planning with an Oracle Database ............................................ 11-19
11.3.4 Working in Co-planning with a Sybase Database............................................. 11-20
Chapter 12 Import MSI PlaNET Data ....................................................................................... 12-1
12.1 Overview ........................................................................................................................ 12-1
12.2 PlaNET Geo Data Files............................................................................................... 12-1
12.2.1 PlaNET Geo Data Format ................................................................................ 12-1
12.2.2 Importing MSI PlaNET Geographic Data ......................................................... 12-7
12.2.3 Importing MSI PlaNET Text Data Files ............................................................ 12-8
12.3 Importing a MSI PlaNET Database............................................................................. 12-9
12.3.1 Importing a MSI PlaNET Antenna Database.................................................... 12-9
12.3.2 Importing a MSI PlaNET Network .................................................................. 12-10
12.3.3 Importing a MSI PlaNET Carrier Database .................................................... 12-11
12.3.4 Importing a MSI PlaNET Neighbour Database............................................... 12-12
12.3.5 Importing MSI PlaNET Propagation Model Parameters................................. 12-13
12.3.6 Importing MSI PlaNET Path Loss Matrices .................................................... 12-14
12.4 Importing MSI PlaNET CW Measurement Data........................................................ 12-15
12.4.1 Importing MSI PlaNET CW Measurement...................................................... 12-15
Chapter 13 Multi-user Features.................................................................................................. 13-1
13.1 Overview ........................................................................................................................ 13-1
13.2 Creating/Starting Database Projects ............................................................................. 13-1
13.2.1 Operating Principles............................................................................................ 13-1
13.2.2 Creating a New Database from a Document ...................................................... 13-3
13.2.3 Creating a New Document from a Database ...................................................... 13-4
13.2.4 Starting U-Net from the Command Line.............................................................. 13-5
13.2.5 Exporting User Configuration to an External File................................................ 13-6
13.2.6 Importing User Configuration from an External File............................................ 13-8
13.3 Supported Databases .................................................................................................... 13-9
13.3.1 Overview ............................................................................................................. 13-9
13.3.2 Exporting a Project in a MS Access Database ................................................... 13-9
13.3.3 Exporting a Project in a MS SQL Server Database .......................................... 13-10
iii

Table of Contents
13.3.4 Exporting a Project in an Oracle Database....................................................... 13-12

13.3.5 Exporting a Project in a Sybase Database ....................................................... 13-13
13.4 Data Exchange ............................................................................................................ 13-14
13.4.1 Checking Database Connection Properties ...................................................... 13-14
13.4.2 Loading Data from a Database ......................................................................... 13-14
13.4.3 Archiving Data in a Database............................................................................ 13-15
13.5 Database Conflicts and Consistency ........................................................................... 13-16
13.5.1 Solving a Conflict on a Modified Record ........................................................... 13-16
13.5.2 Solving a Conflict on a Deleted Record ............................................................ 13-18
13.5.3 Running an Audit on a Database ...................................................................... 13-19
13.6 Management of Multi-users Matrices........................................................................... 13-20
13.6.1 Sharing Path Loss Matrices between Users ..................................................... 13-20
13.6.2 Computing Path Loss Matrices Only................................................................. 13-22
Chapter 14 Microwave Links ...................................................................................................... 14-1
14.1 Microwave Links Overview ............................................................................................ 14-1
14.2 Creating and Managing a Microwave Link .................................................................... 14-1
14.2.1 Creating a Microwave Link Overview.................................................................. 14-1
14.2.2 Creating a Link Using the Mouse ........................................................................ 14-1
14.2.3 Creating a Link Using the Wizard........................................................................ 14-2
14.2.4 Listing All Microwave Links of a Network............................................................ 14-2
14.2.5 Setting Microwave Link Properties...................................................................... 14-3
14.2.6 Managing Radio Equipment in Microwave Links ................................................ 14-5
14.3 Analysis of a Microwave Link......................................................................................... 14-7
14.3.1 Path Profile and Link Reliability Analysis ............................................................ 14-7
14.3.2 Interference Analysis......................................................................................... 14-11
14.4 ITU maps ..................................................................................................................... 14-16
14.4.1 ITU Vapour Density on Earth ............................................................................ 14-16
14.4.2 ITU Atmospheric Refraction (February) ............................................................ 14-17
14.4.3 ITU Atmospheric Refraction (May).................................................................... 14-17
14.4.4 ITU Atmospheric Refraction (August) ............................................................... 14-18
14.4.5 ITU Atmospheric Refraction (November).......................................................... 14-19
14.4.6 ITU Rain Zones (America) ................................................................................ 14-19
14.4.7 ITU Rain Zones (Europe and Africa)................................................................. 14-20
14.4.8 ITU Rain Zones (Asia)....................................................................................... 14-21
Chapter 15 Radio Network Dimensioning................................................................................. 15-1
15.1 Radio Network Dimensioning Overview ........................................................................ 15-1
15.1.1 System Overview ................................................................................................ 15-1
15.1.2 Main Functions .................................................................................................... 15-1
15.2 User Interface ................................................................................................................ 15-3
15.2.1 Overview ............................................................................................................. 15-3
15.2.2 Main Interface...................................................................................................... 15-3
iv

Table of Contents
15.2.3 Menu Bar............................................................................................................. 15-4

15.2.4 Shortcut Menu ..................................................................................................... 15-9
15.2.5 Tool Bar............................................................................................................. 15-14
15.2.6 Input Interface ................................................................................................... 15-15
15.2.7 Output Interface ................................................................................................ 15-18
15.2.8 [Project view] Pane ........................................................................................... 15-30
15.2.9 Calculation Tool ................................................................................................ 15-32
15.3 RND Operations........................................................................................................... 15-37
15.3.1 Collecting and Processing Data ........................................................................ 15-37
15.3.2 Parameters Input............................................................................................... 15-41
15.3.3 Basic Operation Flow ........................................................................................ 15-48
15.3.4 Output Results................................................................................................... 15-64
15.3.5 Assistant Tool Operations ................................................................................. 15-67
15.4 RND Parameters.......................................................................................................... 15-72
15.4.1 Input Parameters............................................................................................... 15-72
15.4.2 Output Parameters............................................................................................ 15-86
Appendix Acronyms and Abbreviations ..................................................................................... F-1

v

Chapter 8
WCDMA/UMTS Project Management
Chapter 8 WCDMA/UMTS Project Management

8.1 Overview
UMTS (Universal Mobile Telecommunication System) is a radio technology using
WCDMA (Wideband Code Division Multiple Access) principles. UMTS is based on
Wideband CDMA air interface whereas CDMA/CDMA2000 (1xRTT and IS95) on
Narrowband CDMA. WCDMA/UMTS is available in U-Net with the optional UMTS
module.
In UMTS, everybody works at the same frequency; signals are spread over a band of
3.84 MHz (on each carrier) and distinguished by the use of OVSF codes on them.
Nevertheless, this induces potentially high levels of noise which can be defeated by
sophisticated power controls on uplink (from terminals) and on downlink (from
transmitters) traffic channels.
Because of power control, there is not a single solution to model a UMTS network, and
results depend totally on network parameters such as traffic and user behaviours.
Hence, these parameters have to be modelled before starting calculations via user
distributions. Simulation results provide a snapshot of the UMTS network at a certain
time.
In order to simulate user distributions and associated behaviours, some parameters
have to be set. These are services, mobility types, terminal, user profiles and
environment types. Each of these is easy to manage like any other folder-like object
within U-Net. All these parameters go together with traffic maps, based on
environments, on user profiles (with no required definition for environment parameters)
or on Transmitters and Services (in term of rates or number of users - with no required
definition for environment and user profile parameters).
UMTS power control simulations and UMTS specific coverage predictions need the
definition of the previous parameters. Classical coverage predictions are also available
to study cell pilots. The point analysis tool allows a specific analysis of any active set at
any given point on the map, for a particular scenario (service, terminal, and speed of a
probe mobile which current status is provided by network simulation results).
Geo data are easily manageable like for other projects. You may either create or import
geographic objects. Sites, antennas, station templates, transmitters, measurements,
and propagation models work in the same way for UMTS and the other technology
projects. Nevertheless, due to an enhanced resource management to consider at site
level, site equipment and resource management per service have been introduced.
8-1

Chapter 8
Furthermore, since UMTS support several carrier networks, a new item characterising
each carrier per transmitter has been introduced: UMTS cells. Hence, many properties
are defined at the cell level (e.g. powers).
Like for the other types of technologies, neighbours may be manually defined by the
user or with the help of the neighbour automatic allocation tool, but at the cell level.
UMTS Downlink primary scrambling codes enable the user to distinctly identify cells
(transmitters and carriers). They can also be defined manually or automatically
imposing a large number of constraints.
The What's this context tool allows the user to understand the specific UMTS fields
and features available in dialog boxes.
8.2 UMTS Specific Concepts

In a WCDMA (Wideband Code Division Multiple Access) network, a code is allocated
to each link transmitter-terminal. This code allows the terminal to identify the useful
signal spread over the whole bandwidth as mobiles use the same frequency band
simultaneously. Consequently, each mobile is indirectly interfered by all the others. It is
thus essential for UMTS to perform reliable power control especially on the uplink, in
order to limit network interference level.
To achieve power control simulation and coverage calculation, UMTS planning
requires traffic snapshots unlike GSM planning, which only needs traffic data when
dimensioning a network for a certain grade of service.
UMTS coverage directly depends on offered traffic: the more the traffic is, the smaller
the coverage zones are. This phenomenon is called cell breathing. As Traffic is
dynamic, coverage calculation is necessarily statistical.
U-Net achieves coverage predictions in two steps:
1)
First, it simulates power control) for realistic user distributions to obtain network
parameters and interference level (simulation part).
2)
Then, it generates bin-based coverage probability predictions (prediction part).
See UMTS projects protocol.

8-2

Chapter 8
Note:
z
U-Net enables WCDMA/UMTS network planning, 3G network based on Wideband

Code Division Multiple Access technique (WCDMA) and multi-service management.
These major concepts and new technologies require new network and data
modelling, with appropriate needs for traffic modelling. A wide range of different
UMTS services (speech, web, video-conferencing...), available to consumers,
generates a more complex traffic than standard voice transmissions. Appropriate
traffic data model and relevant localization on a map, i.e. traffic cartography
represents a major input for UMTS planning.
Specific UMTS objects are available when creating a new project with U-Net. The
UMTS project is designed to provide specific UMTS radio and traffic data structures,
UMTS simulations and predictions folders.
8.3 UMTS Projects Protocol

A classical UMTS project protocol, within U-Net, is described below Table 8-1:
Table 8-1 UMTS project protocol
content
explain
Network design
Setting radio data
Pilot studies based only on signal reception
Traffic input
Traffic description
activity probabilities
Traffic map design
number of
subscribers or users
(depending on the
type of map)
Realistic user distribution

generation
Power control simulation
UMTS oriented
prediction studies
Point predictions
Coverage predictions
Network optimization
Neighbour allocation
Primary scrambling code

allocation
Simulations (Evaluation
of interference level)

8-3

Chapter 8
8.4 Managing UMTS Radio Data

8.4.1 UMTS Site Equipment
I. Creating umts site equipment
In UMTS, site equipment allows the user to define some equipment related to channel
elements and some other specific UMTS parameters and calculation options (MUD
factor, Rake efficiency factor, and Carrier selection, Overhead CEs, AS restricted to
neighbours).
To create a UMTS site equipment, proceed as follows:
1)
Click the [Data] tab in the [Explorer] window.
2)
Right click on the Sites folder to open the context menu.
3)
Left click the [Equipment/Open] command from the open scrolling menu.
4)
In the Equipment window, describe a piece of equipment per line. Type its name,
the manufacturer name and define (as Table 8-2).
5)
Click on
to close the table.
Table 8-2 Equipment parameters

parameter
explain
MUD factor
Multi-User Detection is a technology used to

decrease intra-cellular interference on uplink. MUD
is modelled by a coefficient between 0 and 1; this
factor is considered in the UL interference
calculation. In case MUD is not supported by
equipment, enter 0 as value.
Rake receiver efficiency

factor
This factor enables U-Net to model macro-diversity

on uplink. U-Net uses it to calculate the uplink SHO
gain and uplink signal quality in simulations, point
analysis and coverage studies. This parameter is
considered on uplink for softer and softer-softer
handovers; it is applied to the sum of signals
received on the same site. The factor value can be
between 0 and 1. It models losses due to the signal
recombination imperfection.
Carrier selection
It refers to carrier selection mode used during the

transmitter admission control in mobile active set.
Three methods are available:
z
UL min noise: The least loaded carrier (carrier

with the lowest UL load factor) is selected.
DL min power: The carrier with lowest used total
DL power is selected.
Random: The carrier is randomly chosen.

8-4

Chapter 8
parameter
explain
Overhead CEs uplink and

downlink
Number of channel elements that a cell uses for

common channels on uplink and downlink.
AS restricted to neighbours
This option is used to manage mobile active set. If

you select this option, the other transmitters in
active set must belong to the neighbour list of the
best server.
Note:
Rake efficiency factor for computation of recombination in downlink has to be set in
terminals.
II. Managing umts site equipment

Site equipment is listed in a table in U-Net. So, as many other objects, they are easy to
manage both in term of contents or handy tools.
To access to the UMTS site equipment table, proceed as follows:
1)
2)
3)
4)
The table displays each piece of equipment in each line.
5)
Click on
to close the table.
Note:
z
Standard features for managing table content (Copy/Paste, Fill up/down, Delete,
Display columns, Filter, Sort, and Table Fields) are available in context menu (when
right clicking on column(s) or record(s)) and in the Format, Edit and Records menus.

terminals.
III. Managing channel element consumption per umts site equipment

UL and DL channel elements are independently dealt with in power control simulation.
Furthermore, the number of channel element required by a site depends on site

equipment, user service and link direction (up or down).
8-5

Chapter 8
To describe channel element consumption during UMTS simulation, proceed as

follows:
1)
2)
3)
Left click the [Equipment/Channel Element consumption] command from the open
scrolling menu.
4)
In the CE consumption window, enter for each equipment-service pair the number
of UL and DL channel elements that U-Net will consume during power control
simulation.
5)
Click on
to close the table.
IV. Assigning umts site equipment to sites

Once equipment related to channel element are defined, it is possible to assign a piece
of equipment to each site.
To assign a piece of equipment to a site, procedure as follows Table 8-3:
Table 8-3 Assign a piece of equipment to a site
Method
Method 1
Method 2
step
1)
Left click on the [Data] tab of the [Explorer] window.
2)
Expand the Sites folder by clicking on the

of it
button in front
3)
Right click on the site you want to manage.
4)
Choose the Properties option from the context menu.
5)
Click the [Equipment] tab.
6)
Enter the maximum number of uplink and downlink channel

elements available for the site; then. Click on the Equipment
scrolling menu and choose a piece of equipment in the list.
7)
Click on <OK> to validate.
1)
Select on the map the site you want to manage by right

clicking on it (
).
2)
3)
Click the [Equipment] tab.
4)

elements available for the site; then. Click on the Equipment
5)

8-6

Chapter 8
Note:
z
In case you have defined neither equipment nor channel element consumption,
U-Net considers the following default values, Rake efficiency factor = 1, MUD factor
= 0, Carrier selection = UL minimum noise, Overhead CEs downlink and uplink = 0,
AS restricted to neighbours option not selected, and uses one channel element per
link (up or down) for any service, during power control simulation.
Equipment can be also assigned by accessing site table.
8.4.2 Transmitter UMTS Specific Parameters

I. Defining the transmitter umts global parameters
In U-Net, some parameters which are globally related to the UMTS technology can be
accessed easily and applied to all the items of a network; these are called global
parameters.
Some of them are used as global values, other as default values. All of these are
essential in UMTS power control simulations.
To access the global parameters of a UMTS network, proceed as follows:
1)
2)
Right click on the transmitters folder.
3)
4)
Click the Global [parameters] tab.
5)
Click <OK> to close the dialog.
Note:
users may choose the way to calculate the total noise Nt taken into account in downlink
and uplink Eb/Nt. Select in the Nt scrolling menu, either the option Without useful
signal to deduct the signal of the studied cell from the total noise, or the option Total
noise to take into account the noise generated by all the cells.

8-7

Chapter 8
8.4.3 UMTS Cells

I. Definition
Because U-Net supports multi-carriers networks, and also since it is possible to define
some rules about carrier selection for a mobile when defining its active set, a new level
has been introduced, the cell level. A cell defines a carrier on a transmitter. Data of
interest like transmission powers (Pilot, Synchronization, Other common channels,
Maximum power), total power, UL load percentage, primary scrambling codes and
active set thresholds are defined at the cell level. Hence, neighbours are also defined at
the cell level.
The number of cells per transmitter is limited by the number of carriers available for a
network as defined in the global parameter dialog. Cells can be listed either by
transmitter, in a specific dialog, or in a table form, as other radio data (sites and
transmitters). So, here again, the management of cells stays easy and comfortable.
II. Creating a umts cell

The cell concept is fully supported in U-Net. Cell is characterized by the
transmitter-carrier couple. Therefore, you can define several cells per transmitter (as
many cells as carriers associated to transmitter).
To define UMTS transmitter cells, proceed as follows:
1)
2)
Right click on the transmitters folder to open the context menu.
3)
Left click the [Cells/Open] command from the open scrolling menu.
4)
Click on
to close the table.
The Cells table contains all the identifiers of a cell, its name, transmitter and carrier
which the cell refers to, cell primary scrambling code, scrambling code domain to
which the allocated scrambling code belongs, all the values defining transmitted signal
level, pilot power, synchronization power, other common channels power,
maximum power, total power used, information about the cell uplink load and an
active set management parameter, AS threshold.
5)
Click on
to close the table.

8-8

Chapter 8
Note:
Cells are automatically created and described in the table when you drag and drop a
station. On the other hand, you must define them manually after adding a new
transmitter (New... command when right clicking on the transmitters folder) or
copying a list of transmitters in the Transmitters table.
Cell default name is: Transmitter name (carrier). If you change transmitter name or
carrier, U-Net does not update the cell name.

You cannot create two cells related to the same transmitter-carrier couple.
III. Managing umts Cell properties

In UMTS, cells are defined per transmitter. Nevertheless, their associated properties
can be reached by several ways. Like many other objects (Sites, Transmitters,
Antennas, Predictions, Simulations, measurements, etc...) within U-Net, cells can be
managed either individually (per transmitter or in a single dialog) or globally.
Global properties management
In U-Net, you may manage globally the cell properties of your network by accessing
the cell table.
To do so, proceed as follows:
1)
2)
Right click on the transmitters folder to open the context menu.
3)
4)
Click on
to close the table.
Individual property management

There are two ways to edit cell properties of each transmitter in the current network,
as Table 8-4 followed:
Table 8-4 Edit cell properties of each transmitter
Destination
method
Open cell properties

table
step
1)
Left click on the [Data] tab of the [Explorer]

window.
2)
Expand the transmitters folder by clicking

on the button in front of it.
3)
Right click on the transmitter which cell

properties you want to access.
4)
Choose the [Properties] option from the

context menu.
5)
Click the Cell tab from the open dialog.

8-9

Destination
Chapter 8
method
2

dialog
step
1)
Select on the map the transmitter which cell

properties you want to access by left clicking
on the appropriate Tx symbol (arrow).
2)
Choose the [Properties] option from the

context menu.
3)
Click the Cell tab from the open dialog.
1)
Open the cell table.
2)
Double click the record which property

dialog you want to open.
1)
2)
Right click on the record which property

dialog you want to open to get its associated
context menu.
3)
Select the <Record Properties> command

from the open scrolling menu (or the Record
Properties command from the Records
menu).
Note:
z
Cell Properties dialog consists of three tabs: cell characteristics entered in the cells
table are grouped in the General and Transmission/Reception tabs, Intra and
Inter-technology neighbours may be allocated to the cell in the Neighbours tabs.
It is possible to define additional fields in the cell table by using the Fields command
in its related context menu (or from the Records menu). If it is the case, this new field
will then be available in the Other properties tab of any cell property dialog.
IV. Power parameters in umts

Because powers can be defined differently within a same transmitter depending on
carriers, these are defined at the cell level in U-Net.
To define the different powers related to UMTS technology, access the cell
properties (either from the table or from dialogs) and fill the following fields
(Transmission/Reception tab):
z
Max power
Pilot power
SCH power
Other CCH power

8-10

Chapter 8
The total power used and UL load used in specific UMTS coverages are also defined in
the cell properties. The active set threshold (default value: 5dB) used for active set
determination has also to be set there.
V. Active set parameters in umts

For a given terminal allowed to perform handover, the active set contains the
transmitters with which it is connected. The main parameter to be measured for
transmitters in the active set is the pilot quality (Ec/Io). Once the best server, in term of
pilot quality, is defined, other transmitters are selected using an active set threshold.
This threshold is defined at the cell level, considering the cell which pilot quality is the
best for a given active set.
To define the active set threshold of any cell, access the cell properties (either from
the table or from dialogs) and fill the field AS threshold (Transmission/Reception tab).
VI. Displaying umts cell properties on the map

In UMTS, only site and transmitter objects are displayed on the map. Cells are not
represented but it is possible to colour transmitters depending on any of cell attributes.
For example, transmitters may be coloured depending on scrambling codes assigned
to their cells.
To colour transmitters depending on any cell attribute, proceed as follows:
1)
2)
Left click the <Properties> command from the open context menu.
3)
Click on the [Display] tab from the open window.
4)
Choose Discrete values or Values interval as display type and then. select in the
Field scrolling menu a cell attribute (they are the last ones in the scrolling menu).
5)
Click <OK> to validate.
In addition, cell properties can be displayed as tips or labels on the map. To do this,
proceed as follows:
1)
2)
3)
4)
Select cell attributes to be displayed in the Label and Tips text scrolling menus
(they are the last ones in the scrolling menus).
5)

8-11

Chapter 8
Note:
z
These features are fully available if there is one cell per transmitter only. When a
transmitter has more than one cell, U-Net does not know the carrier to be
considered. In this case, no value is collected (#).
It is also possible to group transmitters by any cell attribute. As explained above, this
feature is fully available if there is one cell per transmitter only
8.5 WCDMA/UMTS Multi-Service Traffic Data

8.5.1 Umts Services
I. Creating umts services
UMTS allows the user to carry not only voice but also data for web, or video
conferencing for example.
In UMTS, Services are divided into two categories: circuit switched and packet
switched. Usually, circuit switched services support soft handover unlike packet
switched services.
U-Net provides a function to enable or disable soft handover for a given service.
To create a service, proceed as follows:
1)
Click the [Data] tab from the [Explorer] window.
2)
Expand the UMTS Parameters folder by left clicking on the
3)
Right click on the Services folder to open the associated context menu.
4)
Left click in the scrolling menu on New.
5)
Click the available tabs to set the parameters of the created service.
6)
Validate by clicking on <OK>.
button.
Note:
In the Eb/Nt tab window, (Eb/Nt) DL and (Eb/Nt) UL targets are the thresholds (in dB)
that must be achieved to provide users with the service. These parameters depend on
user speed and must be defined for all mobility types.

8-12

Chapter 8
II. Setting umts service parameters

Similar to the other U-Net object folders, UMTS services are easily manageable.
Creation steps and display management are standard.
To manage the UMTS services parameters, procedure as follows Table 8-5:
Table 8-5 manage the services parameters
Method
Method 1
Method 2
step
1)
2)

button.
3)
Expand the Services folder by left clicking on the
4)
Right click on the service of which you want to manage the

properties to open the associated context menu.
5)
Left click in the scrolling menu on Properties.
6)
Click the available tabs to adjust the parameters of the

current service.
7)
1)

button.
button.
2)
3)
Double click on the service of which you want to manage the

properties.
4)

current service.
5)
button.
Note:
z
When the Services table is displayed and active, it is possible to open the property
dialog window of any service by simply double clicking on any cell in the associated
line, or on the associated arrow at left.
The activity factor and efficiency factors are taken into account in order to determine
user activity status during simulations. Inactive circuit users produce noise whereas
inactive packet ones are not considered.
The coding factors, which penalize UL and DL service rates, may be supplied in two
ways. For each service, you may:
z
Either enter high UL and DL coding factors and then, set a low enough UL and DL
Eb/Nt threshold so that the advantage of high coding can be simulated (higher

8-13

Chapter 8
error correction rate means smaller bit error rate and thus a smaller required
Eb/Nt).
z
Or enter low UL and DL coding factors value and take into account the coding to
define the required UL and DL Eb/Nt values, i.e. a high enough Eb/Nt threshold to
simulate the disadvantage of little coding.
III. Managing globally umts services

In U-Net, UMTS objects are organized in folders. For this reason, U-Net allows the user
to simultaneously display all topics of one type (services, mobility, terminal, user
profiles, and environment) in a table window.
To open the services table, proceed as follows:
1)
2)
3)
4)
Left click in the scrolling menu on Open.
5)
The services table opens.
6)
Click on
button.
to close the table.
or
1)
2)
3)
Double click on the Services folder.
4)
5)
Click on
button.
to close the table.
The services table works exactly like the other tables. Its cells are editable, sorting and
filtering tools, and copy/paste functions are available.
Note:
z
The advanced grouping/filtering/sorting feature may be used on the services from

the context menu associated with the Services folder. From the properties dialog
box, you may also manage the contents of the services table. Use the What's this
help to get description about the fields available in the different windows.

8-14

Chapter 8
8.5.2 UMTS Mobility Types

I. Creating a umts mobility type
In UMTS, receiver mobility knowledge is important for efficient active set management:
a mobile used by a speed driver or a pedestrian will not necessarily be connected to the
same transmitters. Ec/Io requirements and Eb/Nt targets per service and per link (up
and down) are largely dependent on mobile speed.
To create a UMTS mobility type, proceed as follows:
1)
2)
3)
Right click on the Mobility type folder to open the associated context menu.
4)
5)
Set the parameters of the currently created mobility.
6)
button.
Mobility parameters are pilot quality (Ec/Io) thresholds (in dB). For a given mobility type:
Ec/Io threshold is the minimum Ec/Io required from a transmitter to enter the active set.
In U-Net, this value is verified for the best server.
II. Umts active set conditions

The transmitters taking part in the active set have to check the following
conditions:
z
They must be using the same carrier (at the cell level).
The pilot quality (Ec/Io) of the best server has to exceed the Ec/Io threshold
(defined for each mobility type).
The pilot quality difference between other cells and the best server must not
exceed the AS-threshold value set per cell.
Other cells have to belong to the neighbour list of the best server if you have
selected the restricted to neighbours option (in the definition of the Site
equipment).
III. Setting a umts mobility type

Like for the other U-Net object folders, UMTS mobility types are easily manageable.
Creation steps and the display management are standard.
To manage the mobility types parameters, proceed as follows:
1)
2)
3)
Expand the Mobility type folder by left clicking on the

8-15
button.
button.

4)
Chapter 8
Right click on the mobility of which you want to manage the properties to open the
associated context menu.
5)
6)
Set the parameters of the current mobility.
7)
Or,
1)
2)
3)
4)
Double click on the mobility of which you want to manage the properties.
5)
6)
button.
button.
Note:
When the Mobility type table is displayed and active, it is possible to open the property
dialog window of any mobility by simply double clicking on any cell in the associated
IV. Managing globally umts mobility types

To open the mobility types table, proceed as follows:
1)
2)
3)
Right click on the Mobility types folder to open the associated context menu.
4)
5)
The mobility types table opens.
6)
Click on
button.
to close the table.
Or,
1)
2)
3)
Double click on the Mobility types folder.
4)
The mobility types table opens.
5)
Click on
to close the table.

8-16
button.

Chapter 8
The mobility types table works exactly like the other tables. Its cells are editable,
sorting and filtering tools, and copy/paste functions are available.
Note:
z
The advanced grouping/filtering/sorting feature may be used on the services from

the context menu associated with the mobility types folder. From the properties
dialog box, you may also manage the contents of the mobility types table. Use the
What's this help to get description about the fields available in the different windows.
When the Mobility type table is displayed and active, it is possible to open the
property dialog window of any mobility by simply double clicking on any cell in the
associated line, or on the associated arrow at left.
8.5.3 UMTS Terminal Equipment

I. Creating a umts terminal
In UMTS, terminals describe the terminal equipment that can be used in the network
(cellular phone, multi-media terminal, in-car navigation device, and so on). Each
terminal is modelled by a minimum and maximum transmission power (dynamic range
for uplink power control), its antenna gain and reception loss, and an internal thermal
noise. Active set size is the maximum allowable number of transmitters in connection
with the terminal (macro-diversity). Finally, you may enter a Rake receiver efficiency
factor. This factor enables U-Net to model soft handover efficiency on downlink. U-Net
uses it to calculate the downlink SHO gain and downlink signal quality in simulations,
point analysis and coverage studies. This parameter is considered on downlink for any
handover type; it is applied to the sum of signal levels. The factor value can be between
0 and 1. It models losses due to the signal recombination imperfection.
To create a UMTS terminal, proceed as follows:
1)
2)
3)
Right click on the Terminals folder to open the associated context menu.
4)
Left click in the scrolling menu on [New].
5)
Set the parameters of the currently created terminal.
6)

8-17
button.

Chapter 8
Note:
Rake efficiency factor for computation of recombination in uplink has to be set in site
equipment.
II. Setting umts terminal parameters

Like for the other U-Net object folders, UMTS terminals are easily manageable.
To manage the terminal parameters, proceed as follows:
1)
2)
3)
Expand the Terminals folder by left clicking on the
4)
Right click on the terminal of which you want to manage the properties to open the
button.
button.

5)
6)
Set the parameters of the current terminal.
7)
Or,
1)
2)
3)
4)
Double click on the terminal of which you want to manage the properties.
5)
6)
button.
button.
Note:
When the Terminal table is displayed and active, it is possible to open the property
dialog window of any terminal by simply double clicking on any cell in the associated
III. Managing globally umts terminals

To open the terminals table, proceed as follows:
8-18

Chapter 8
1)
2)
3)
4)
5)
The terminals table opens.
6)
Click on
button.
to close the table.
Or,
1)
2)
3)
Double click on the Terminals folder.
4)
5)
Click on
button.
to close the table.
The terminals table works exactly like the other tables. Its cells are editable, sorting
and filtering tools, and copy/paste functions are available.
Note:
z
The grouping/filtering/sorting advanced feature may be used on the services from

the context menu associated with the Terminals folder. From the properties dialog
box, you may also manage the contents of the terminals table. Use the What's this
When the Terminal table is displayed and active, it is possible to open the property
dialog window of any terminal by simply double clicking on any cell in the associated
8.5.4 UMTS User Profiles

I. Creating a umts user profile
In UMTS, user profiles model the behaviour of the different subscriber categories. Each
user profile is constituted by a list of services and their associated usage parameters
such as used terminal, call or session frequency (calls/hour) and duration or data
volume to be transferred.
Parameters for circuit switched services are:
z
Average number of calls per hour
Average duration of a call in seconds
Used terminal (equipment used for the service (from the Terminals table))
Parameters for packet switched services are:

8-19

Chapter 8
Average number of sessions per hour
Volume in Kbytes which is transferred on the downlink during a session
Volume in Kbytes which is transferred on the uplink during a session
Example:
z
For a web-browsing service, a session starts when the user opens his browsing
application and ends when he quits the browsing application. Between these two
events, sometimes the user may be downloading web pages and other times he
may not be using the application, or be browsing local files. A session is described
by the volume transferred both on the downlink and the uplink.
Those parameters are used in simulation to determine the probability (activity status)
that a user is transmitting or receiving communication for the given service and
terminal when the snapshot is taken.
Note:
z
For circuit switched services, entering a one-hour call during 1000s corresponds to
define 2 calls per hour during 500s...the activity probability is the same in both
cases.
For all the services defined for a user profile, in order to be taken into account during
traffic scenario elaboration, the sum of activity probabilities must be lower than 1.
You can model temporal variations of user behaviour by creating different profiles
for different hours (busy hour, and so on).
To create a UMTS user profile, proceed as follows:

1)
2)
3)
Right click on the User profiles folder to open the associated context menu.
4)
5)
Set the parameters of the currently created user profile.
6)
button.
II. Adjusting umts user profile properties

Like for the other U-Net object folders, UMTS user profiles are easily manageable.
To manage the user profile parameters, procedure as follows Table 8-6:
8-20

Chapter 8
Table 8-6 manage the user profile parameters

Method
Method 1
Method 2
step
1)
2)

button.
3)
Expand the User profiles folder by left clicking on the

button.
4)
Right click on the user profile of which you want to manage

the properties to open the associated context menu.
5)
6)
Set the parameters of the current user profile.
7)
1)
2)

button.
3)

button.
4)
Double click on the user profile of which you want to manage

the properties.
5)
6)
Note:
When the User profiles table is displayed and active, it is possible to open the property
dialog window of any user type by simply double clicking on any cell in the associated
III. Managing globally umts user profiles

to display simultaneously all topics of one type (services, mobility, terminal, user
To open the user profiles table, procedure as follows Table 8-7:
Table 8-7 open the user profiles table
Method
Method 1
step
1)
2)

button.
8-21

Chapter 8
Method
Method 2
step
3)
Right click on the User profiles folder to open the

4)
1)
2)

button.
3)
Double click on the User profiles folder.
The user profiles table works exactly like the other tables. Its cells are editable, sorting
Note:
z

the context menu associated with the User profiles folder. From the properties
dialog box, you may also manage the contents of the user profiles table. Use the
When the User profiles table is displayed and active, it is possible to open the
property dialog window of any user type by simply double clicking on any cell in the
8.5.5 UMTS Environments

I. Creating a type of umts environment
Environment classes may be used to describe subscriber spatial distribution on a map;
they are the available classes for traffic cartography design. Environment class
represents an economic and social concept, which defines the characteristics of user
profiles. Each environment class contains a set of three data (user profile, mobility,
density) where density is a number of subscribers with the same profile per km. There
is no restriction on the number of data sets constituting an environment.
To get an appropriate user distribution, you may assign weights per clutter classes, for
each environment class.
To create a UMTS environment type, proceed as follows:
1)
2)

8-22
button.

Chapter 8
3)
Right click on the Environments folder to open the associated context menu.
4)
Left click in the scrolling menu on <New>.
5)
Click the available tabs to set the parameters of the currently created environment.
6)
Note:
When no multi-service geo-marketing data are available, you may supply U-Net with
usual traffic data like user densities per service (for example, values coming from
adapted GSM Erlang maps). In this case, user profile definition and calculation of
deduced activity probability are not necessary to create traffic scenario; traffic
distribution will only depend on densities per service.
In UMTS, for instance, if you know user densities per service, just avoid handling user
profile step by defining one-hour full communication profile per service.
For circuit services:
z
In service properties: set UL and DL activity factors to 1.
In user profile properties, define 1 call/hour with 3600s duration. Therefore, each
user will be connected.
For packet services:

z
In service properties: set efficiency factor to 1 in UL and DL.
In user profile properties: define 1 session/hour and set volume to transmit during
3600s. Therefore, each user will be connected.
Therefore, the activity probabilities calculated during simulation will be equal to 1 and
density values defined in Environments will be user densities (no more subscriber
densities). Elaborated traffic scenario will fully respect the user profile proportion (i.e.
service) given in environments. You will fully master the number of users in simulation
as well as the service proportion which will drive random trials. Moreover, each user will
be connected.
This method is not the usual nominal working mode for U-Net.
II. Setting umts environment parameters

Like for the other U-Net object folders, UMTS environments are easily manageable.
To manage the environments parameters, procedure as follows Table 8-8:

8-23

Chapter 8
Table 8-8 manage the environments parameters

Method
Method 1
Method 2
step
1)
2)

button.
3)
Expand the Environments folder by left clicking on the

button.
4)
Right click on the environment type of which you want to

manage the properties to open the associated context
menu.
5)
6)

current environment.
7)
1)
2)

button.
3)

button.
4)
Double click on the environment type of which you want to

manage the properties.
5)

6)
Note:
z
To get an appropriate user distribution, you may assign weights per clutter classes,
for each environment class in the Clutter weighting tab.
When the Environments table is displayed and active, it is possible to open the
property dialog window of any environment type by simply double clicking on any
cell in the associated line, or on the associated arrow at left.
III. Managing globally umts environment types

to simultaneously display all topics of one type (services, mobility, terminal, user profile,
and environment) in a table window.
To open the environment types table, described as follows Table 8-9:

8-24

Chapter 8
Table 8-9 open the environment types table

Method
Method 1
Method 2
step
1)
Click the [Data] tab from the [Explorer] window,
2)

button.
3)
Right click on the Environments folder to open the

4)
5)
The Environment type table opens.
1)
2)

button.
3)
Double click on the Environments folder.
4)
The environment types table works exactly like the other tables. Its cells are editable,
Note:
z

the context menu associated with the Environments folder. From the properties
dialog box, you may also manage the contents of the environment types table. Use
the What's this help to get description about the fields available in the different
windows.
IV. Displaying statistics per umts environment type

U-Net allows the user to perform a statistic study on each environment class.
These statistics provide the number of mobiles to be created in the traffic scenario for
the given environment (based on a raster traffic map, respecting the layer order). This
number is given displayed per clutter class.
To display a statistic study on any environment type, proceed as follows:
1)
2)

8-25
button.

Chapter 8
3)
4)
Right click on the environment type you want to display a statistical study to open
button.
the associated context menu.

5)
Left click in the scrolling menu on Statistics....
Note:
The statistic study is limited to the focus zone, only the clutter and environment areas
inside the focus zone are taken into account in calculations.
V. Subscriber clutter weighting in umts environments

Enter a weight for each clutter class in order to get an appropriate user distribution
The following formula is used for calculations:
Nk = Nclass
w k Sk
w j Sj
j
where:
Nk
Number of users in the k clutter
Nclass
Number of users in an environment class
wk
k clutter weight at fixed surface
Sk
k clutter surface (stated in km)
This weighting method is used when displaying statistics per UMTS environment type.
8.6 WCDMA/UMTS Multi-Service Traffic Cartography

U-Net provides 3 types of traffic maps for WCDMA/UMTS projects:
z
Traffic raster maps based on environments: each pixel of the map is assigned an
environment class.
Traffic vector maps based on user profiles: each polygon or line contains a density
of subscribers with given user profile and mobility type.
Traffic maps per transmitter and per service: live traffic is spread over a best pilot
coverage plot. To each computed area is assigned either rates or amount of users
per service (uplink or downlink).
8-26

z
Chapter 8
Whatever the type of map is, this one can be either created or modified manually,
imported from an external file and exported to an external file.
8.6.1 WCDMA/UMTS Environment Traffic Maps

I. Creating a umts environment traffic map
There are two solutions to define an environment traffic map, either by creating
environment polygons or by directly importing a raster map in your project as an
environment traffic map.
To create a WCDMA/UMTS environment traffic map by drawing, proceed as follows:
1)
Click the [Geo] tab in the [Explorer] window.
2)
Right click on the Traffic folder to open the associated context menu.
3)
Select the New map command from the scrolling menu.
4)
Choose the map based on environments (raster) option in the Create a traffic map
open window.
button to validate.
5)
Press the
6)
Use the cartography editor (selecting one of the available environment classes as
defined in the environment folder) to draw environment polygons.
7)
Click the
button to close the editor.
Note:
z
Like other raster maps, it is easily possible to save the generated traffic map.
You can only choose among existing environment classes in the cartography editor.
To make available additional classes, do it in the UMTS parameters.
II. Importing a umts environment traffic map

environment polygons or by directly importing a raster map (with the appropriate format)
in your project as an environment traffic map.
To import a WCDMA/UMTS environment traffic map from an external file, proceed as
follows:
1)
2)
3)

8-27

4)
Chapter 8
Choose the map based on environments (raster) option in the Create a traffic map
open window.
5)
Press the
6)
Locate the file to be imported and click the
7)
Choose the Traffic option from the scrolling menu in the open File import window.
8)
Press the
9)
In the name column. left click cells in order to replace class (codes or clutter)
button to validate.
button to validate.
button to validate.
names by existing environment classes.

10) Press <OK> or <Apply> to validate.
Note:
z
Importing a file as a traffic map can be also made through the generic import
(selection of the environment traffic type in the appropriate scrolling menu).
Clutter files can be imported as traffic files.
In order to manage traffic on the entire map. this operation must be carried out for all
classes.
The description table can be fully copied and pasted (using Ctrl+V and Ctrl+C) in a
new U-Net project after importing the raster file. To select globally the environment
class table. just left click on the top left angle of the environment table.
Like other raster maps. it is easily possible to save the generated traffic map.
III. Managing umts environment traffic maps

On an existing environment traffic map, you can access properties and it is possible to
modify the class association and its display settings.
To access the properties of an existing environment traffic map, proceed as follows:
1)
2)
Expand the Traffic folder by clicking on the
3)
Right click on the related environment map folder to open the associated context
button in front of it.
menu.
4)
5)
Click the description tab to re-associate environment classes.
6)
Click the display tab to set the transparency level. the visibility scale and to add the
map information to the legend.
7)
Press <OK> or <Apply> to validate.

8-28

Chapter 8
Or
1)
2)
3)
Double click on the related environment map folder.
4)
5)
Click the display tab to set the transparency level. the visibility scale and to add the
map information to the legend.

6)
It is also possible to access the properties of a single file composing the resulting map
(properties command in the related context menu) to embed it into the atl project or to
check the map geocoding.
Note:
Absolute and relative statistics can be provided for this type of map.
IV. Exporting a umts environment traffic map

Like the other WCDMA/UMTS traffic map types (user profile or live traffic), it is possible
to export a environment traffic map in either a 8 bits/pixel raster tiff, bil or bmp format. It
is possible to export a part or the complete environment traffic map.
To export a part or the complete environment traffic map in WCDMA/UMTS projects,
proceed as follows:
1)

2)
3)
Right click on the Environment map folder in order to get the related context
menu.
4)
Left click on the [Save as...] option from the open scrolling menu.
5)
Define the format, the directory path and the name to give to the file to be
exported.
6)
Click the <Save> button when this is made.
7)
In the Export dialog box. select one of the options and define the resolution (in
metres) of file as follow Table 8-10.
8)
Table 8-10 Export dialog box, select one of the options

options
whole covered
explain
Allows you to save the whole traffic map in another file. As soon
as the file is saved, the properties (such as name) of the traffic
8-29

Chapter 8
options
explain
region
maps listed in the Environment Traffic subfolder are updated.
only pending
changes
Allows save in the file the created traffic polygonal area. As soon as the
modifications are saved, an additional traffic item is created and listed
in the Environment Traffic subfolder.
computation
zone
Allows you to save only traffic map region inside the computation zone
in another file. As soon as the file is saved, an additional traffic object is
created and listed in the Environment Traffic subfolder. To enable this
option, you must have drawn a computation zone beforehand.
resolution
it is defined for raster traffic from the following criteria :

z
If one traffic object is clipped, the displayed resolution will be

the object resolution.
If several objects are modified, the suggested resolution will
be the smallest resolution of the altered items.
If there is no initial traffic item, the resolution will equal the
resolution of DTM object which the modifications are made
on or the smallest resolution of the merged DTM objects if
the modifications are performed on several DTM objects.
If you draw your own traffic data without initial DTM, clutter
or traffic object, a 100 m default resolution will be suggested.
The resolution value must be an integer.
The minimum resolution is set to 1 metre.
Comment:
When you save files using BIL and TIF formats, .hdr and .tfw files are automatically
created in the same folder. The .hdr and .tfw files are respectively associated with .bil
and .tif files; they contain geocoding information and resolution.
V. Displaying statistics on umts environment traffic maps

It is possible to display statistics on an existing WCDMA/UMTS environment traffic map.
Statistics are given globally and relatively as functions of environment traffic classes.
Traffic density statistics indicates the proportion of each traffic class. Traffic statistics
refer to the focus zone is existing.
To display traffic statistics of the map in WCDMA/UMTS projects, proceed as follows:
1)
2)
3)
Right click on the Environment Traffic folder to open the associated context
menu.
4)
Choose the [Statistics] option from the scrolling menu.

8-30

5)
Chapter 8
The surface (Si in km) of imported or edited traffic class (i) included in the focus (if
existing) zone and its percentage (% of i) are specified:
% of i =
Si
100
Sk
k
Note:
z
If no focus zone is defined, statistics are given over the computation zone.
Current statistics are printable by clicking the
button.
8.6.2 WCDMA/UMTS User Profile Traffic Maps

I. Creating a umts user profile traffic map
In U-Net, user profile traffic maps can be defined in any type of project
(GSM/GPRS/EDGE, UMTS or CDMA/CDMA2000). The vector data (points, lines,
polygonal shapes) are expected to directly link a dedicated user profile, mobility and
traffic density. The way to get user profile traffic maps consists in either importing vector
files (MapInfo (MIF, MID), Arcview (SHP), AutoCAD (DXF)) and using them as traffic
maps or creating vectors with the vector editor and assign them some traffic
information.
To create a WCDMA/UMTS user profile traffic map by drawing, proceed as follows:
1)
2)
3)
4)
Choose the map based on user profiles (vector) option in the Create a traffic map
open window.
button to validate.
5)
Press the
6)
Potentially define traffic information (user profile. mobility type. density) in the
Table tab. assign them to U-Net internal traffic fields in the Traffic tab. Use the
vector editor to draw environment polygons, lines or points.
7)
Click the

8-31

Chapter 8
Note:
z
Like other vector layers, it is easily possible to save the generated traffic map.
Points can be seen as traffic hotspots
See Examples of vector traffic data.
II. Importing a umts user profile traffic map

files (MapInfo (MIF, MID), Arcview (SHP), AutoCAD (DXF)) and using them as traffic
maps or creating vectors with the vector editor and assign them some traffic
information.
To import a WCDMA/UMTS user profile traffic map by drawing, proceed as follows:
1)
2)
3)
4)
open window.
button to validate.
5)
Press the
6)
7)
8)
Press the
9)
A dialog box is displayed in order to configure traffic vector data.
button to validate.
button to validate.
10) Click the Traffic tab.

Note:
In the Traffic field part, specify the user profiles to be considered on the traffic vector
map, their mobility types (km/h) and their densities (number of users/km2 for polygons
and number of user/km for lines). You can decide the type of information that you want
to use to define the traffic characteristics, either a field described in the file (by field
option in the Defined column) or a value directly user-definable in U-Net (by value
option in the Defined column).

8-32

z
Chapter 8
The first method can be used only if the file you are importing contains attributes
providing information about the user profile, mobility or density. In this case, select
in the Choice column a suitable field for each data (user profile, mobility and
density); U-Net lists all the attributes described in the file. The attributes of the
source file cannot be modified. Using this method, each traffic polygon or linear is
assigned specific characteristics (user profile, mobility or density).
Note:
Take care to define in U-Net user profiles and mobility types described in traffic file with
exact spelling.
The second way is useful when traffic files contain no attribute. Therefore, you
may assign manually user profiles, mobility types and densities created in U-Net.
Select in the Choice column user profile and mobility listed in UMTS Parameters
folder and specify manually a global density for all the polygons. Beforehand, just
make sure to define in UMTS Parameters the internal data like user profile and
mobility you want to allocate. Here, all the polygons are described by global
characteristics (user profile, mobility or density).
11) In the Clutter weighting part, assign a weight to each clutter class. Thus, U-Net
allows you to spread traffic inside the polygons according to the clutter weighting
defined for the whole subfolder. The spreading operation (using a raster step) will
be carried out during the simulation process.
12) Then, press <OK> to validate the properties setting.
Note:
z
(selection of the Traffic type in the appropriate scrolling menu),
During the import procedure, if the imported user profiles or mobility types are not
currently part of the existing user profiles or mobility types, U-Net warns you about
the fact that these may not be correctly taken into account as traffic data.
Path and description are stored in the external user configuration file.
III. Managing umts user profile traffic maps

To access the properties of an existing user profile traffic map, proceed as follows:
1)
2)

8-33

3)
Chapter 8
Right click on the related user profile traffic map folder to open the associated
context menu.
4)
5)
Click on the [General] tab to either embed the file into the atl project. to relocate
the map by the definition of the appropriate coordinate system. By imposing sorts
on the vector organization or filters on the vector display.
6)
Click on the Table tab to manage the content of the vector.
7)
Click on the Traffic tab to re-associate vector fields and U-Net internal traffic fields.
and to impose subscriber clutter weighting using this map for the subscriber
distribution during the Monte Carlo simulation.
8)
Click on the Display tab to open the U-Net generic display dialog.
9)
Or
1)
2)
3)
Double click on the related user profile traffic map folder.
4)
the map by the definition of the appropriate coordinate system. by imposing sorts
on the vector organization or filters on the vector display.
5)
6)

Click on the Traffic tab to re-associate vector fields and U-Net internal traffic fields.
and to impose subscriber clutter weighting using this map for the subscriber
distribution during the Monte Carlo simulation.
7)
8)
IV. Examples of umts user profile traffic data

Structure of two vector traffic files is described hereafter. Niceregion.mif consists of
eleven polygons representing the Nice region. Each polygon is characterised by a user
profile, the services offered to subscribers, their mobility types and densities. Densities
are stated in number of subscribers per km2. Highway.mif represents a highway (linear)
where density corresponds to a number of subscribers per km.
Niceregion.mif is shown in following Table 8-11.
Table 8-11 Niceregion.mif FILE
Name
User profile
Services used
MobilityA
DensityA
MobilityB
DensityB
Hinterlan
d
rural user
Speech
90 km/h
pedestrian
Village
rural user
Speech
50 km/h
10
pedestrian
Corniche
rural user
Speech
50 km/h
10
pedestrian
20

8-34

Name
Chapter 8
User profile
Services used
MobilityA
DensityA
MobilityB
DensityB
Rural
rural user
Speech
90 km/h
pedestrian
Villages
rural user
Speech
50 km/h
10
pedestrian
10
Nice
urban user
Speech, Web,
Simple
messaging,
Video
conferencing
pedestrian
700
50 km/h
100
Nice
airport
urban user
Speech, Web,
Simple
messaging,
Video
conferencing
pedestrian
700
50 km/h
100
Nice
surroundi
ngs
rural user
Speech
50 km/h
100
90 km/h
100
Rural
rural user
Speech
90 km/h
pedestrian
Villages
rural user
Speech
50 km/h
10
pedestrian
Nice
center
urban user
Speech, Web,
Simple
messaging,
Video
conferencing
pedestrian
4000
pedestrian
Using the user profile traffic import procedure, it is possible to associate (Traffic tab of
the properties dialog):
z
To user profile: either a global value (by value) for all the polygons or the
Userprofile field of the vector (by field) with a different definition for each polygon.
To mobility: either a global value (by value) for all the polygons or the MobilityA
(resp. MobilityB) field of the vector (by field).with a different definition for each
polygon.
To density: either a global value (by value) for all the polygons or the DensityA
(resp. Density B) field of the vector (by field) with a different definition for each
polygon.
Highway.mif is shown in Table 8-12.

Table 8-12 Highway.mif FILE
ID
highway
User_profile
Service used
Density
Mobility
driver
Speech
400
120 km/h

8-35

Chapter 8
Using the user profile traffic import procedure, it is possible to associate (Traffic tab of
the properties dialog):
z
To user profile: either a global value (by value) for all the polygons or the
User_profile field of the vector (by field) with a different definition for each polygon.
To mobility: either a global value (by value) for all the polygons or the Mobility field
of the vector (by field) with a different definition for each polygon.
To density: either a global value (by value) for all the polygons or the Density field
of the vector (by field) with a different definition for each polygon.
V. Exporting a umts user profile traffic map

Like the other WCDMA/UMTS traffic map types (environment, live traffic), it is possible
to export user profile traffic maps.
To export a WCDMA/UMTS user profile traffic map, proceed as follows:
1)
2)
Expand the Traffic folder by left clicking on the
3)
Right click on the user profile traffic map folder to open the associated context
button.
menu.
4)
5)
Define the format. the directory path and the name to give to the file to be exported.
Possible formats are Arcview (.shp). MapInfo (.mif) and the U-Net internal format
(.agd).
6)
Click the <Save> button to complete the export procedure.
8.6.3 WCDMA/UMTS Live Traffic Maps

I. Creating a umts live traffic map
This kind of traffic map requires coverage by transmitter prediction study. Then, U-Net
expects rate values (kbit/s) or number of active users for each service and each
transmitter.
Note:
It is possible to define either one map per service or one map with all services.
Then, the traffic cartography is built without connection with the initial coverage
prediction. This map consists of polygons provided with the same features as the user
profile traffic polygons.

8-36

Chapter 8
The definition of WCDMA/UMTS live traffic maps can be made either from a direct
creation on the basis of coverage by transmitter study previously calculated or by
importing a file.
To create a WCDMA/UMTS live traffic map, proceed as follows:
1)
2)
3)
4)
Choose the map based on transmitter and service (Throughput or Number of

users) option in the Create a traffic map open window.
button to validate.
5)
Press the
6)
Select the prediction study to be considered for traffic distribution. Only coverage
per transmitter studies can be used. A table where you can indicate the live traffic
spread over the transmitter service areas is available. It consists of a column
dedicated to transmitters and several columns for the different services previously
defined in the UMTS parameters folder. In the TX_ID column. Select each line.
Click on the arrow and choose a transmitter in the list. You may also use the copy
and paste commands (respectively Ctrl+C and Ctrl+V) from an Excel file already
containing the expected columns.
7)
Enter rate values (kbits/s) (or Number of active users) on uplink and on downlink
relating to different services for each transmitter.
8)
Press <OK> to continue the map creation.
9)
U-Net displays the property dialog of the map. Click the Traffic tab of the opened
property dialog and define terminal and mobility ratios by entering percentage
values for each terminal and each mobility type (they will be used in the traffic
scenario). You may also specify a weight per clutter class to spread traffic over
each coverage area. The spreading operation will be performed during the traffic
distribution.
10) Click <OK> to validate.

U-Net creates an object called Traffic map per transmitter in the Traffic folder of the
[Geo] tab.
Note:
z
The map only contains the service areas of transmitters listed in the table. Then, the
traffic map shape is fixed and cannot be modified; it is not possible to add new
transmitters.
On the other hand, it is possible to modify traffic values (throughputs or number of

users) afterwards in the Table related to the map.

8-37

Chapter 8
II. Importing a umts live traffic map

The definition of WCDMA/UMTS live traffic maps can be made either from a direct
creation on the basis of a coverage by transmitter study previously calculated or by
importing a file.
You may import files with AGD format. This is the U-Net geographic data internal format.
This kind of file must be created from U-Net (export of coverage by transmitter study in
the AGD format).
To import a WCDMA/UMTS live traffic map by drawing, proceed as follows:
1)
2)
3)
4)
Choose the map based on transmitter and service (Throughput or number of users
per transmitter) option in the Create a traffic map open window.
button to validate.
5)
Press the
6)
7)
8)
Select the option embed in the document to include the file in the .atl document.
button to validate.
When this option is not selected. U-Net just memorizes the file directory path.
9)
In the coordinate systems part. U-Net summarises the projection coordinate

system you have defined in the .atl project. In the box just below. Specify the
coordinate system of the file you are importing (click on Change... to choose
another coordinate system).
button to validate.
10) Press the
11) U-Net displays the property dialog of the map. Click the Traffic tab of the opened
distribution.
Note:
It is also possible to import a traffic map per transmitter using the standard import
procedure (Import command in the File menu). In this case, you must specify in the
import dialog that you want to import the file in the Traffic folder.

8-38

Chapter 8
III. Managing umts live traffic maps

Management features of vector maps are available for traffic maps per transmitter:
standard graphical features are available in the Display tab of the map property dialog
and each map has a corresponding table. This table contains the transmitters used to
build the map and traffic information for each of them.
To access the properties of an existing live traffic map, proceed as follows:
1)
2)
3)
Right click on the related live traffic map folder to open the associated context
menu.
4)
5)
the map by the definition of the appropriate coordinate system by imposing sorts
on the vector organisation or filters on the vector display.
6)
7)
Click on the Traffic tab to re-define terminal and mobility ratios and to impose
subscriber clutter weighting using this map for the subscriber distribution during
the Monte Carlo simulation.
8)
9)
Press <OK> or< Apply> to validate.
IV. Exporting a umts live traffic map

Like the other WCDMA/UMTS traffic map types (environment or user profile), it is
possible to export live traffic maps.
To export a WCDMA/UMTS live traffic map, proceed as follows:
1)
2)
3)
Right click on the live traffic map folder to open the associated context menu.
4)
5)
Define the format, the directory path and the name to give to the file to be exported.
button.
Possible format is the U-Net internal format (.agd).

6)
Click the <Save> button to complete the export procedure.
8.7 UMTS Simulations

8.7.1 Overview
Power control simulation is a necessary step to obtain instantaneous network noise
level and perform service area prediction based on it. Furthermore, it is a first, quick
8-39

Chapter 8
and easy analysis tool to get information about network dimensioning. Traffic data is a
critical parameter for UMTS studies. Indeed, power control simulation is performed
from user distributions, which are obtained by random trials driven by traffic data. Its
significance rests on traffic data relevance.
z
U-Net provides a random user distribution generation, based on a Monte-Carlo

algorithm complying with traffic description and cartography.
Once realistic user distributions are available, power control simulation is

automatically achieved to determine network parameters (such as cells and
terminal powers) and estimate interference level.
U-Net provides either actual network audit (taking into account your network
constraints) or new dimensioning information about how to handle available traffic.
On the same traffic snapshot, you can check how your network works and can be
improved.
U-Net offers a wide range of tuneable parameters involved in UMTS simulations.

Even from existing simulations, it is possible to modify these parameters with the
replay simulations features offered by U-Net. You may also add simulations to a
group of existing simulations. Averaging a group of simulations is also possible.
Once achieved, simulations are available for specific UMTS coverage predictions.
Indeed, for UMTS projects, U-Net provides four different groups of studies, listed in a
natural planning order, from the indispensable pilot study to the study of downlink
total noise, with respect to the propagation model as defined :
z
Pilot-oriented studies to determine pilot coverage by transmitter. the pilot

coverage by signal level. overlapping area (like standard coverage studies). pilot
quality (Ec/Io) and pilot pollution.
Service-oriented studies to determine service availability in uplink and downlink

and effective service areas.
Handover Status Study to analyse macro-diversity performance.
Downlink total noise study.
With the point analysis tool, it is also possible to build a UMTS scenario defining
a probe mobile with a type of terminal, mobility and service) and predict, on
each point of the current map, its results. Except pilot coverage, coverage by
signal level and overlapping studies, which are similar to classical coverage
studies, all other studies are specific to UMTS network planning and closely
related to a particular simulation.
U-Net provides powerful simulation outputs. Firstly, you can display requirements,
results and initial conditions. Then, you may choose to display the simulation
results either per site, per transmitter, or per mobile for the currently studied
simulation. Finally, you may optionally display the computed shadowing errors.
The results can also be displayed on the map as function of any topics dealt with
the UMTS simulations (service, terminal, user, mobility, activity, factors,

8-40

Chapter 8
connection and HO status, best server, active set parameters, geographic

coordinates, rates, carriers, powers, noise rise, path loss).
8.7.2 Managing UMTS Simulations

I. Creating umts power control simulations
UMTS networks automatically regulate themselves by using traffic driven uplink and
downlink power control in order to minimize interference and maximize capacity.
U-Net simulates this network regulation mechanism with an iterative algorithm and
calculates, for each user distribution, network parameters such as base station power,
mobile terminal power, active set and handover status for each terminal.
To create a (group of) UMTS power control simulation(s), proceed as follows:
1)
2)
Right click on the [UMTS simulations] folder to open the associated context menu.
3)
Left click in the scrolling menu on New....
4)
The creation of simulations dialog window opens.
5)
Set the parameters for the current simulation study (ies).
6)
Note:
z
If you check the Execute later box, computations will be started when using the
Calculate command (F7 shortcut or
button).
When starting computations, a group of simulations (with the input number of

simulations) is automatically created under the UMTS simulation folder.
Once achieved, simulations are available for specific UMTS coverage predictions or for
an AS analysis with the point analysis tool.
II. Managing umts simulation properties

Like many other objects (Sites, Transmitters, Cells, Antennas, Predictions,
measurements, etc...) within U-Net, simulations can be managed either individually or
globally. Nevertheless, due to the fact that some of them have already been started,
you can only display their input parameters. Regarding the global properties of
simulations, they are related to the way simulation results are displayed on the map.
8-41

Chapter 8
In U-Net, you may manage globally the display properties of the existing simulations.
1)
2)
Right click on the UMTS Simulations folder to open the context menu.
3)
Left click the Properties command from the open scrolling menu.
Note:
To manage the display of simulation results, the U-Net generic dialog window is used.
So, it is possible to display simulation results related to, for example, their connection
status, handover status, any UMTS parameter, pilot quality, etc... Furthermore, all
simulation folders are then organized in threshold items that you can display or not in
the workspace.

If computations have already been started, the properties you can display on groups of
simulations are related to the input parameters.
To open the properties related to a group of UMTS simulations, proceed as follows:
1)
2)
Expand the UMTS Simulations folder by clicking on the
3)
Right click on the group of UMTS Simulations you want to manage.
4)
Choose the [Properties] option from the context menu.
Note:
z
If computations have not been started (using the Execute later command), you can
access to the group properties in order to modify them for coming computations.
You can access to the Properties of any single simulation. The open dialog is
related to simulations requirements and results, specific results per site, per mobile,
per cell and simulation initial conditions.
III. Umts power control simulation inputs

Before running simulations, you must have a radio network with a satisfying pilot
coverage. Then, it is necessary to define traffic description and cartography.

8-42

Chapter 8
Power control simulation needs propagation path loss for cells and mobiles. If these
results are not available, U-Net achieves propagation calculation using the propagation
model as defined from either the transmitter or the prediction folders.
In U-Net, the dialog allowing you to create simulations is made of three tabs: General,
Traffic and Advanced described below.
z
General tab
In this tab, you can enter a name to the group of simulations that U-Net is going to
compute. Then, you may decide the number of scenarios on which you want to
simulate power control. It is possible to create several simulations at the same time or
just one by one if you prefer. Selecting the Detailed results option enables you to get
additional simulation outputs relating to mobiles (results available in the Mobiles and
Mobiles (Shadowing values) tabs of the simulation Properties window). Finally, the
Execute later option can be used if you want to predefine simulation calculation settings
and start the computation subsequently. In case the option is selected, simulation
calculation is not carried out when closing the dialog; simulation will be worked out
when clicking on the Calculate command (F7 shortcut or
button).
Note:
The Execute later feature enables you to automatically calculate UMTS coverage
studies after simulations without intermediary step.
In the Cell load constraint part, you must select constraints you want U-Net to respect
during power control simulation. If you wish to check your network, just select the
constraints about maximum cell power, maximum number of channel elements,
maximum uplink cell load (the default value is set to 75%) and OVSF codes availability.
The simulation proceeds without exceeding these limits. Mobiles with the lowest
service priority (user-defined in each service properties dialog window) are first
rejected. In order for the simulation to proceed freely, uncheck all the calculation
options.
z
Traffic tab
The global scaling factor for traffic option enables you to increase subscriber density
without changing traffic parameters or cartography. For example, setting the global
scaling factor for traffic to 2 means doubling the initial number of subscribers (for traffic
raster or user profile traffic maps) or the rates/users (for traffic maps per transmitter and
per service).

8-43

Chapter 8
Then, you can perform simulations using several traffic cartographies. To do this, select
them in the Traffic part. In this case, U-Net takes into account the traffic information
provided in all the selected maps. This feature must be carefully used to avoid
inconsistencies. Thus, make sure you do not mix several kinds of traffic maps (for
example, raster traffic map and transmitter coverage area traffic map) in a simulation
study; rather, make several simulation studies, each one based on a same sort of traffic
map. On the other hand, you can fully carry out a simulation study using several traffic
maps belonging to the same kind.
z
Advanced tab
Generator initialization enables you to obtain the same random distribution in two
simulations just by giving the same non-zero integer in this field. For example, you
create a simulation with generator initialization value of 1 (or whichever integer different
from 0). When you create another simulation, giving 1 as generator initialization, you
obtain the same random distribution. To avoid getting similar distributions, just enter
zero value in this field. A group of several distributions created at the same time may be
repeated with the same principle. This can be useful when one wants to compare two
simulations with just one parameter value difference; so to make a just comparison, it is
better to have the same user locations (same path loss values for users).
You can then specify the maximum number of iterations allowed during a simulation, UL
and DL convergence thresholds.
The power control simulation is based on an iterative algorithm. In the Convergence
part, you can define how many iterations you want the simulation to run (maximum
number of iterations) and specify your own uplink and downlink convergence criteria
(percentage power difference for downlink and percentage noise difference for uplink
between two successive iterations).
When clicking OK, simulation starts running and stops when the convergence criteria
are met in two successive iterations (when there is no network parameter evolution).
Therefore, the simulation can finish before reaching the maximum number of defined
iterations.
When calculation is finished, U-Net has created the required number of simulations in
the newly created group of simulations.
U-Net makes easy the consistency management between radio data, simulations and
predictions.
Average simulations and replays are reachable from each of these subfolders. Display
properties are reachable form the Simulations folder.

8-44

Chapter 8
IV. Replaying a umts simulation

U-Net allows the user to replay existing simulations in order to keep the same radio
configuration (including reference maps, initialization number) and to modify the
convergence parameters and the constraints on the cell loads. The new group of
simulations is based on the same random user distribution (number of users who try to
be connected, allocated service, mobility and activity status, geographic position), just
the power control is recalculated and the outputs updated.
To replay a group of UMTS simulations (one of several ones), proceed as follows:
1)
2)
Expand the UMTS simulations folder by left clicking on the
3)
button.
Right click on the UMTS simulation group subfolder you want to replay the
simulations to open the associated context menu.
4)
Left click in the scrolling menu on Replay.
5)
The replay simulation(s) dialog window opens.
6)
Set the parameters on the convergence parameters and the constraints on the cell
loads for the current group of simulations to replay.
7)
Once achieved, simulations are available for specific CDMA coverage predictions or for
Note:
Giving several times the same integer number (different from 0) as initialization number
in the simulation creation dialog box leads to replay simulations with identical user
random distribution.
Comment:
As the generator initialization function, this feature enables you to obtain the same user
distribution in two simulations. Nevertheless, the generator initialization option is more
powerful since it can be used to create several simulations with the same distribution at
the same time and several sets of different simulations with the same set of
distributions.

8-45

Chapter 8
V. Generator initialisation - replay differences (umts)

The main differences between two features are the inputs taken into account in
simulations. Comparison is detailed below.
z
Replay: U-Net reuses the same user distribution (user with a service, a mobility
and an activity status) and traffic parameters (such as maximum and minimum
traffic channel powers allowed, Eb/Nt targets...) as in the initial simulation. Just
radio data (new transmitter, azimuth...) modifications are taken into account during
power control simulation.
Generator initialization: If generator initialization entered when creating both

simulations is an integer different from 0, U-Net finds the same user distribution
(user with a service, a mobility and an activity status) in both simulations. On the
other hand, in this case, both traffic parameter (such as maximum and minimum
traffic channel powers allowed, Eb/Nt targets...) and radio data (new transmitter,
azimuth...) modifications are taken into account during power control simulation.
VI. Averaging umts simulations

With U-Net, it is possible to average some available groups of simulations. This feature
also allows the user to calculate standard deviations on the averaged simulations.
Results are automatically displayed per cell, identically than in a single simulation.
To display average results per cell over a group of UMTS simulations, proceed as
follows:
1)
2)
3)
Right click on the UMTS simulation group subfolder you want to average the
button.
simulations to open the associated context menu.

4)
Left click in the scrolling menu on [Average simulations...].
5)
The average simulation dialog window opens.
6)
Use the What's this help to get description about the fields available in the open
window.
7)
Click on the [available] tabs to display either the Statistics. Means or Standard
deviation window.
8)
Click <OK> to close the window.
Average simulations may be used in specific UMTS coverage predictions or in an AS

analysis with the point analysis tool.
VII. Adding a simulation to an existing group of umts simulations

In U-Net, It is possible to add a new simulation to an existing group of simulations. When
creating the new simulation, U-Net takes into account the same inputs (radio and traffic data,

8-46

Chapter 8
simulation parameters) as used for generating the group of simulations and replays user
distribution and power control simulation.
To add a simulation to an existing group of simulations, proceed as follows:

1)
2)
Expand the UMTS Simulations folder by left clicking on the
3)
Right click on the simulation group on which you want to add a simulation.
4)
Choose the< New...> command from the open context menu.
5)
A new simulation is being computed using the parameters of the current group.
6)
After calculation. a new simulation is added to the group.
button.
Note:
The added simulation is then considered if you calculate an average simulation.
8.7.3 UMTS Simulation Process

I. Power control umts simulation concepts
Power control consists of two steps in U-Net:
1)
Obtaining realistic user distribution.
To get user distribution, you need to have traffic cartography at your disposal.
Each user is assigned a service, a mobility type and an activity status by random trial,
according to a probability law that complies with the traffic database (and packet
switched services as well as circuit switched services).
User activity status is an important output of random distribution, which will have direct
consequences on simulation and network noise level.
In UMTS, a circuit switched service user is either active or inactive:
z
Active means: a radio resource has been allocated to the user, and the user is
speaking (i.e. he creates interference both on the downlink and the uplink).
Inactive means: a radio resource has been allocated to the user, but he is not
speaking (i.e. he does not create interference).
A packet switched service user can be either inactive or active on the downlink or active
on the uplink:
z
Inactive means: the user is currently not transmitting or receiving packets, so he

does not use any radio resource and does not create interference: he is neither
taken into account in simulation, nor represented on map.
8-47

z
Chapter 8
Active on the downlink: the user is receiving data, he has been assigned a radio
resource and he creates interference on the downlink.
Active on the uplink: the user is transmitting data, he has been assigned a radio
resource and he creates interference on the uplink
A second random trial determines user positions in their respective traffic zone.
2)
Based on CDMA air interface, network automatically regulates itself by using traffic
driven uplink and downlink power control in order to minimize interference and
maximize capacity. U-Net simulates this network regulation mechanism with an
iterative algorithm and calculates, for each user distribution, network parameters such
as base station power, mobile terminal power, active set and handover status for each
terminal.
The power control simulation is based on an iterative algorithm. Each iteration, all the
mobiles selected during the user distribution generation (1st step) try to be connected
one by one to network transmitters. The process is repeated from iteration to iteration
until convergence. The algorithm steps are detailed below Figure 8-1.

8-48

Chapter 8
I n itia lis a tio n
1 s t s t e p : M i b e s t s e rv e r d e te r m in a tio n
2 n d s te p : M i a c tiv e s e t d e te r m in a tio n
3 r d s t e p : U p lin k p o w e r c o n tro l
+
r a d io r e s o u r c e c o n tro l
F o r e a c h m o b ile M i
4 th s te p : D o w n lin k p o w e r c o n tr o l
+
r a d io re s o u r c e c o n tro l
5 th s te p : U p lin k a n d d o w n lin k in te rf e re n c e u p d a te
C o n g e s t io n a n d r a d io r e s o u r c e c o n t r o l
C o n v e r g e n c e s tu d y
Figure 8-1 Schematic view of power control simulation algorithm

During simulation, mobiles penalizing too much the others are ejected. Different causes
of ejection can be distinguished:
z
The signal quality is not sufficient:

- On the downlink, not enough pilot signal quality: Ec/I0 pilot < Ec/I0 min pilot
- On the downlink, not enough reception on traffic channel: Ptch > Ptch max
- On the uplink, not enough power to transmit: Pmob > Pmob max
When constraints above are respected, the network may be saturated:

- The maximum load factor is exceeded (at admission or congestion).
- Not enough channel elements on site: channel element saturation
8-49

Chapter 8
- Not enough power for cells: Cell power saturation

- OVSF code saturation
z
When the network is saturated; mobile ejection may be due to different reasons
described above: multiple causes.
II. Umts simulation convergence method

The convergence criterion is evaluated as follows:
Each iteration k, U-Net evaluates:

DL
DL
max P (ic ) P (ic )
max Nuser
(ic )k Nuser
(ic )k 1
tx
k
tx
k 1

DL = max int Stations

100 , int Stations
100
DL
ic
ic

P tx ( )k
N user ( )k

UL
UL

UL
(ic )k Nuser
(ic )k 1
max Nuser
(ic )k 1 100 , int Stations

I UL (ic )k I tot
UL = max int max tot

100
UL
UL
Stations
(
)
I
ic
ic
(
)
N
user

tot
k
Where,
parameter
meanings
the UL convergence threshold
the DL convergence threshold
the cell total transmitted power on the carrier ic
the total interference received by cell on the carrier ic

the number of users connected on UL on the carrier ic
the number of users connected on DL on the carrier ic
U-Net stops the algorithm if:
1)
1st case: Between two successive iterations, UL and DL are lower ( ) than their
respective thresholds (defined when creating a simulation).
The simulation has reached convergence.

8-50

Chapter 8
Example:
Let us assume that the maximum number of iterations is 100, UL and DL
convergence thresholds are 5. If
UL 5
and
DL 5
between the 4th and the 5th
iteration, U-Net stops the algorithm after the 5th iteration. Convergence is
reached.
2)
2nd case: After 30 iterations, UL or/and DL are still higher than their respective
thresholds and from the 30th iteration, UL or/and DL do not decrease during 15
successive iterations.
The simulation has not reached convergence (specific divergence symbol).
Example:
Let us assume that the maximum number of iterations is 100, UL and DL
convergence thresholds are 5.
After the 30th iteration, UL or/and DL equal 100 and do not decrease during 15
successive iterations: U-Net stops the algorithm at the 46th iteration.
Convergence is not reached.
After the 30th iteration, UL or/and DL equal 80, they start decreasing slowly until
the 40th iteration (without going under the thresholds) and then, do not change
during 15 successive iterations: U-Net stops the algorithm at the 56th iteration
without reaching convergence.
3)
3rd case: After the last iteration.
If UL or/and DL are still strictly higher than their respective thresholds, the
simulation has not reached convergence (specific divergence symbol).
If UL and DL are lower than their respective thresholds, the simulation has
reached convergence.

8-51

Chapter 8
III. Admission control in umts simulations

U-Net checks cell UL load during admission control (1st step: mobile best server
determination) and congestion control (after considering all the mobiles during an
iteration). Therefore, a mobile can be rejected due to a higher UL load either during
admission control, or during congestion control. It is possible to distinguish both
rejection causes.
A bit more information concerning the admission control is provided. During admission
control, U-Net calculates the uplink load factor of a considered cell assuming the
handled mobile is connected to it. Here, activity status assigned to users is not taken
into account. So even if the mobile is not active on UL, it can be rejected due to cell load
saturation. To calculate the cell UL load factor, either U-Net takes into account mobile
power determined during power control if mobile was connected in previous iteration,
or it estimates a load rise due to mobile and adds it to the current load. The load rise
( X UL ) is calculated as follows:
X UL =
1
W
1 + UL
Q req RUL
b
Where,
parameter
W
meanings
The chip rate (bit/s)
The Eb/Nt target on uplink (defined in service properties for a
given mobility),
The service uplink effective bit rate (bit/s).
IV. Channel element management in umts simulations

In U-Net, the number of channel elements needed for a user with given service and link
direction depends on site equipment and channel element consumption defined for the
equipment-service couple.
V. Ovsf codes management

OVSF codes are now managed on the downlink during the simulation. U-Net performs
OVSF code allocation during the resource control step.
OVSF codes form a binary tree; codes with a longer length are generated from codes
with a shorter length. Indeed, length-k OVSF codes are generated from length-k/2

8-52

Chapter 8
OVSF codes. Therefore, if one channel needs 1 length-k/2 OVSF code; it is equivalent
to use 2 length-k OVSF codes, or 4 length-2k OVSF codes, as shown in Figure 8-2.
Figure 8-2 OVSF codes

512 codes per cell are available in UMTS projects.
During the resource control, U-Net determines, for each cell, the number of codes,
which will be consumed. It allocates:
A 256 bits-length code per common channel, for each cell. The number of
common channels corresponds to the number of overhead DL channel elements

per cell defined for the site equipment.
A code per cell-receiver link, for traffic channels. The length of code to be allocated,
Code-Length, is determined as follows:

Code _ Length =
W
DL
Rb
Where,
parameter
meanings
Rb
the downlink service effective bit rate (bit/s)
the spreading bandwidth (Hz)
DL
Note:
The factor 2 is taken into account to model usage of a QPSK modulation (2 bit/symbol)
on downlink.

8-53

Chapter 8
When the calculated code length does not correspond to the code lengths available
into the tree, U-Net takes the code with the shorter length. For instance, U-Net will use
a 128 bit OVSF code in case the calculated code length is 240.
The OVSF code allocation follows the Buddy algorithm, which guarantees that:
z
If a k-length OVSF code is used, all of its children with lengths 2k, 4k... cannot be
used because they are no longer orthogonal.
If a k-length OVSF code is used, all of its ancestors with lengths k/2, k/4... cannot
be used because they are no longer orthogonal.
Example:
Let a 16 kbit/s service user active on DL be connected to a cell. We assume that site
equipment requires four overhead downlink channel elements per cell. Therefore,
U-Net will consume four 512 bit-length OVSF codes for common channels and a 128
bit-length OVSF code for traffic channels, that is to say four additional 512 bit-length
OVSF codes.
Note:
z
1. The OVSF code allocation follows the mobile connection order (mobile order in
the Mobiles tab).
2. The OVSF code and channel element management is differently dealt with in
case of softer handover. U-Net allocates OVSF codes for each cell-receiver link
while it globally assigns channel elements to a site.
Constraint on the OVSF codes is available when creating simulation. Therefore, when
selecting it, U-Net checks the OVSF code availability and then:
z
Ejects the mobile if there is no OVSF code available (without considering the
service priority).
When this constraint respect is not required, U-Net just checks the OVSF code
availability without rejecting mobiles in case of OVSF code unavailability.
VI. Ovsf codes availability

An additional constraint on the OVSF codes, Number of codes, is available when
creating simulation. Therefore, when selecting the Number of codes option, U-Net
checks the OVSF code availability and then ejects the mobile if there is no OVSF code
available (without considering the service priority).

8-54

Chapter 8
VII. Modelling shadowing in umts simulations

In order to take into account prediction errors along paths in UMTS simulations, U-Net
keeps a neutral predicted path loss for mobiles; a random shadowing value is
computed and added to the average predicted path loss. Cell edge coverage
probability and shadowing margin are then introduced in prediction studies and point
analysis only.
From a user-defined model standard deviation (value associated to the receiver
position or default value), a random shadowing error is computed and added to the
model path loss ( L path ). This random vale is drawn during Monte-Carlo simulation;
each user is assigned a service, a mobility type, an activity status, a geographic
position and a random shadowing value.
For each link, path loss (L) can be broken down:
L = Lpath +
is a zero mean Gaussian random variable G(0, dB ) representing variation due to
shadowing. It can be expressed as the sum of two uncorrelated zero mean Gaussian
random variables,
and
models error related to the receiver local
environment; it is the same whichever the link.
models error related to the path
between transmitter and receiver.

Therefore, in case of two links, we have:
1 = L + P1
for the link 1
2 = L + P2
for the link 2
From i , the model standard deviation ( ) and the correlation coefficient ( ) between
1
and
Pi
have the same standard deviations).
, we can calculate standard deviations of
We have:

8-55
( L )
and
Pi
( P )
(assuming all

Chapter 8
2 = L2 + P2
L2
2
Therefore,
P2 = 2 (1 )
L2 = 2
There is currently no agreed model for predicting correlation coefficient ( ) between 1
and
. Two key variables influence correlation:
The angle between the two paths. If this angle is small, correlation is high.
The relative values of the two path lengths. If angle is 0 and path lengths are the
same, correlation is zero. Correlation is different from zero when path lengths
differ.
A simple model has been found [1]:
= T

D1
D2
when
is a function of the mean size of obstacles near the receiver and is also linked to
the receiver environment.

In a normal handover state, assuming a hexagonal schema for sites, is close to (+//3) and D1/D2 is close to 1.
We found in literature that = 0.5 when = 0.3 and t = /10.
In U-Net, is set to 0.5. So, we have:
L =
and
P =

8-56

Chapter 8
Therefore, to model shadowing error common with all signals arriving at mobile
Re ceiver
( E Shadowing ), values are randomly drawn for each mobile; they follows a zero-mean
Gaussian distribution with a standard deviation (either value associated to the mobile

2
where ( ) is the standard deviation associated
clutter class, or a default value)
to the mobile clutter class. Then, for each mobile-transmitter couple, U-Net draws
another value representing shadowing part uncorrelated with the position of the mobile
Path
( E Shadowing ); this value follows a zero-mean gaussian distribution with a standard

2
.
deviation
Random shadowing error means are centred on zero. Hence, this shadowing
modelling method has no impact on the simulated network load. On the other hand, as
shadowing errors on the receiver-transmitter links are uncorrelated, the method will
influence the evaluated macro-diversity gain.
Random shadowing values used for each mobile and mobile-transmitter pair are
detailed in simulation results.
8.7.4 UMTS Simulation Results Summary

I. Displaying umts simulation requirements and results
When a simulation study has been created, U-Net creates a statistical report on
simulation results. A part is dedicated to traffic request determined from the 1st step of
simulation (traffic scenario elaboration) and another one refers to network performance
(results coming from 2nd step of simulation: power control).
If a focus zone has been defined in your project, only sites, transmitters and mobiles
located inside the focus zone are considered when accessing simulation results. The
global output statistics are based on these mobiles.
Traffic request:
z
U-Net calculates the total number of users who try to be connected. It is a result of
the first random trial; the power control has not yet been achieved. This result
depends on the traffic description and cartography.
During the first random trial, each user is assigned a service. Therefore, UL and
DL rates that all the users could theoretically generate are provided.
Breakdown (number of users, UL and DL rates) per service is given.

8-57

Chapter 8
Results:
z
The number and the percentage of rejected users are calculated and detailed per
rejection cause. These results are determined after the power control and depend
on network design.
U-Net supplies the total number and the percentage of connected users; UL and
DL total rates that they generate. These data are also detailed per service.
To display requirements and results on any simulation, procedure as follows Table

8-13:
Table 8-13 display requirements and results
Method
Method 1
Method 2
step
1)
2)

button.
3)
Expand the simulation group subfolder containing the

simulation you want to display the requests and results by left
clicking on the button.
4)
Right click on the UMTS simulations you want to display the

requests and results to open the associated context menu.
5)
6)
Click on the [Statistics] tab from the open window.
7)
1)
2)

button.
3)

simulation you want to display the requests and results by left
4)
Double click on the UMTS simulations simulation you want to

display the requests and results.
5)
Click on the [Statistics] tab from the open window.
6)
Click<OK> to close the window.
Note:
The traffic rates are calculated at the user level without taking into account handover.
Once achieved, simulations are available for specific UMTS coverage predictions or for

8-58

Chapter 8
II. Displaying input parameters of an existing umts simulation

After a UMTS simulation, U-Net can display the associated transmitter global parameters and
the inputs defined during the simulation creation.
To display the input parameters of an existing simulation, proceed as following Table

8-14:
Table 8-14 display the input parameters of an existing simulation
Method
Method 1
Method 2
step
1)
2)

button.
3)

simulation you want to display the initial conditions by left
4)

initial conditions to open the associated context menu.
5)
6)
Click on the Initial conditions tab from the open window.
7)
1)
2)

button.
3)

4)
Double click on the UMTS simulations you want to display the

initial conditions.
5)
6)
The initial condition tab window contains parameters shown in Table 8-15:
Table 8-15 Parameters in condition tab window
parameter
The transmitter global
parameters
In detail
z
The spreading width.
The orthogonality factor.
The default uplink soft handover gain.
The inputs available when
The MRC in softer/soft option: if it is defined

or not.
The method used to calculate Io
The maximum number of iterations.

8-59

Chapter 8
parameter
In detail
creating simulation
orthogonality factor and

standard deviation as defined
per clutter type.
The uplink
thresholds.
and
downlink
convergence
The simulation constraints such as the

maximum power. the maximum number of
channel elements. the uplink load factor and
the maximum load.
The name of used traffic maps.
Then, if available, are displayed the values of orthogonality factor and standard
deviation as defined per clutter type.
Note:
When the simulation does not converge (UL and DL convergence criteria not reached
at the end of the simulation), U-Net displays a special warning icon
in front of
Simulation object.
III. Summarising results per site (umts projects)

After a UMTS simulation, U-Net can display the associated results per site.
To display the results on any simulation per site, proceed as following Table 8-16:
Table 8-16 display the results on any simulation per site
Method
Method 1
Method 2
step
1)
2)

button.
3)

simulation you want to display the requests and results by
left clicking on the button.
4)

results per site to open the associated context menu.
5)
6)
Click on the Sites tab from the open window.
7)
1)

8-60

Chapter 8
Method
step
2)

button.
3)

4)
Double click on the UMTS simulations you want to display the

results per site.
5)
6)
In this window, U-Net displays the maximum number of channel elements previously
defined for each site, the number of required channel elements in uplink and downlink
at the end of simulation, the number of extra channel elements due to soft handover,
the properties related to each site equipment (MUD factor, Rake receiver efficiency
factor, carrier selection mode, AS restricted to neighbours option and overhead
channel elements on uplink and downlink), the uplink and downlink throughputs (kbits/s)
per service supported by site. The UL and DL throughputs are the number of kbits per
second supported by the site on uplink and downlink to supply (mobiles connected with
the transmitters located on the site) one kind of services. The throughput calculation
takes into account the handover connections.
If the maximum channel element number is exceeded, sites are displayed with red
colour.
Note:
The
allows the user to choose the data to be displayed in the
current table. Once achieved, simulations are available for specific CDMA coverage
predictions or for an AS analysis with the point analysis tool.
IV. Summarising results per cell (umts projects)

After a UMTS simulation, U-Net can display the associated results per cell.
To display the results on any simulation per site, proceed as following Table 8-17:

8-61

Chapter 8

Method
Method 1
Method 2
step
1)
2)
Expand the UMTS simulation folder by left clicking on the

button.
3)

simulation you want to display the results per cell by left
4)
Right click on the UMTS simulation you want to display the

results per cell to open the associated context menu.
5)
6)
Click on the [Transmitters] tab from the open window.
7)
1)
2)
Expand the UMTS simulation folder by left clicking on the

button.
3)

4)
Double click on the UMTS simulation you want to display the

results per cell.
5)
6)
In this window, U-Net provides the simulation input data like the maximum power, the
pilot power, the SCH power, the other CCH power, the AS threshold, the gain, the
reception and transmission losses, the noise figure, and simulation output data
regarding cells such as the total DL power used, the UL total noise, the UL and DL load
factors, the UL and DL noise rises, the percentage of used power, the UL reuse factor,
the UL reuse efficiency, the number of UL and DL links, the number of used OVSF
codes, the percentage of handover types, the UL and DL throughputs, the minimum,
maximum and average traffic channel powers, the number of users rejected for each
cause, for each cell.
Note:
The
current table. The "Commit loads" button permits to copy UL loads and total powers DL
(or their average in the case of several carriers) in the cell table in order to be taken
potentially as reference for specific CDMA predictions (by selecting the None option
from the simulation scrolling box).

8-62

Chapter 8
Average simulations are ordered by cells. Once achieved, simulations are available for
specific CDMA coverage predictions or for an AS analysis with the point analysis tool.
V. Committing simulated loads to cells (umts projects)

In U-Net, to enable simulation result sharing, two fields, the UL load (UL load factor)
and total power (total DL power used), are available in cell properties. Both parameters
can be results coming from a single or an average simulation or inputs manually
specified in the Cell table or in the Transmission/Reception tab of each cell Property
window.
To assign any simulated UL load factor and total DL power to cells from a network,
proceed as following Table 8-18:
Table 8-18 The step of assign any simulated UL load factor and total DL power
Method
Method 1
Method 2
step
1)
2)

button.
3)

simulation you want to use the simulated results by left
4)
Right click on the UMTS simulations you want to use the

simulated results to open the associated context menu.
5)
6)
Click on the Cells tab from the open window.
7)
Click the
total powers to cells.
8)
Values are automatically copied in each cell properties

window.
9)
1)
2)

button.
3)

4)
Double click on the UMTS simulations you want to use the

simulated results.
5)
6)
Click the
7)

window.
8-63
to assign calculated loads and

Chapter 8
Method
step
8)
Note:
z
When assigned to cells, these values can be used for coverages based on no
simulation.
This feature is also available from the mean tab window of any average simulation.
Reminder: the Commit load button is inactive as long as both fields, UL load and
total power, do not exist.
VI. Summarising results per mobile (umts projects)

After a UMTS simulation, U-Net can display the associated results per mobile.
To display the results on any simulation per site, proceed as following Table 8-19 :
Method
Method 1
Method 2
step
1)
2)

button.
3)

4)

results per mobile to open the associated context menu.
5)
6)
Click on the [Mobiles] tab from the open window.
7)
1)
2)

button.
3)

4)

results per mobile.
5)
Click on the [Mobiles tab] from the open window.
6)

8-64

Chapter 8
In this window, U-Net gives information about calculated terminal parameters. First,
U-Net mentions simulation input data: X, Y, service, terminal, user profile, user mobility
and activity obtained from random trial. U-Net displays simulation output data for these
users: carrier, DL and UL requested and obtained rates, mobile power, best server,
connection status, handover status, transmitters in active set and Ec/Io from cells in
active set.
U-Net displays which carrier is used for connection and calculates the power
transmitted by the terminal. U-Net identifies the best server among the cells taking part
in mobile active set.
Connection status refers to mobile ejection causes previously defined. It gives the
reasons why the mobile, even active, is not connected to any transmitter at the end of
the simulation.
U-Net allows analysing what type of handover is possible for a mobile; providing the
HO status information. HO status represents the real number of sites compared to the
number of cells in active set.
Example:
When a mobile is in connection with three cells and among them two co-site cells (soft
- softer handover), its HO status is 2/3. When the mobile is connected with only one
transmitter (no handover) its HO status is 1/1. When the mobile is connected with three
co-site transmitters (softer - softer handover), its HO status is 1/3.
Active set is the list of transmitters (or cells since on unique carrier) in connection with
the mobile. The maximum number of transmitters in active set is defined by the user in
Terminal Properties and besides limited to 4 in U-Net. Soft handover can be
enabled/disabled for every service. For each transmitter in active set, Ec/Io values are
calculated and may be compared to Ec/Io thresholds previously defined in Mobility
Type Properties. Transmitters, which provide an Ec/Io pilot quality that is lower than
[Best server Ec/Io - AS-threshold], are rejected from the active set.

8-65

Chapter 8
Note:
z
The
current table. Once achieved, simulations are available for specific UMTS coverage
z
Checking the Detailed results box during the simulation creation enables you to get
additional simulation outputs relating to mobiles and shadowing values computed
along paths between transmitters and mobiles.
VII. Displaying shadowing values of a umts simulation

This feature is available only when selecting the Detailed results option in the
simulation creation dialog. Here, U-Net details for each mobile:
z
Its number Id
The clutter class where the receiver is located
The model standard deviation (value associated to the clutter class or default
value)
Re ceiver
The random shadowing error ( E Shadowing ) related to the receiver local
environment (Value at receiver); this one is the same whichever the link.
z
Path
The random shadowing errors ( E Shadowing ) due to the transmitter-receiver path
(Value). U-Net gives this error for a maximum of ten paths; it considers the ten
transmitters, which have the mobile in their calculation areas and the lowest path
losses (Lpath). Transmitters are sorted in an ascending path loss order.
To display shadowing values for each mobile in any simulation, proceed as following
Table 8-20:
Table 8-20 The step of display shadowing values for each mobile
Method
Method 1
step
1)
2)

button.
3)

simulation you want to display by left clicking on the button.
4)

clutter data to open the associated context menu.
5)
6)
Click on the Mobile (Shadowing values) tab from the open

window.
8-66

Chapter 8
Method
Method 2
step
7)
1)
2)

button.
3)

simulation you want to display by left clicking on the button.
4)

clutter data.
5)

window.
6)
Note:
z
The values
ceiver
ERe
Shadowing
computed for all the mobiles follow a zero-mean gaussian
distribution with a standard deviation 2 .
The values
Path
E Shadowing
computed for a given mobile follow a zero-mean gaussian
2
.
distribution with a standard deviation
VIII. Managing umts simulation results on the map

From any simulation, U-Net can, globally or individually, display the associated results
on the map in several ways. These can be managed globally for all the simulations.
To make available the display dialog window on all the simulations of the current
project, proceed as following Table 8-21:
Table 8-21 make available the display dialog window
Method
Method 1
step
1)
2)

button.
3)
Right click on the UMTS simulations folder to open the

8-67

Chapter 8
Method
step
Method 2
4)
5)
Set the display parameters for all the simulations of the

current project.
6)
1)
2)

button.
3)
Double click on the UMTS simulations folder.
4)

current project.
5)
Like for most of the other display dialog windows in U-Net, you can choose the
display type associated with the values (unique, discrete, values interval) and some
corresponding fields. Due to the complexity of UMTS technology simulations, these
fields are numerous and can be obtained as indicated in the following Table 8-22.
Table 8-22 display type and fields
Display type
Field
Unique
All the simulations
Discrete Values
Service
Terminal
User
Mobility
Activity
Carrier
Connection status
Best server
HO status
Asi
Clutter
Value intervals
X
Y
DL requested rate (kbits/s)
UL requested rate (kbits/s)
8-68

Display type
Chapter 8
Field
DL obtained rate (kbits/s)
UL obtained rate (kbits/s)
Mobile Total power
Ec/Io Asi
Cell power TCH Asi (DL)
Ntot DL ASi
Load factor Asi
Noise rise Asi
Reuse factor Asi
Iintra Asi
Iextra Asi
Total path loss Asi
Nb UL CEs
Nb DL CEs
Name
Orthogonality factor
UL SHO gain UL
UL SHO gain DL
Note:
Existing simulations, in the [Explorer] window contain sub-items which depend on
results are displayed on the map. The simulation display is managed with the standard
display dialog in use under U-Net. Once achieved, simulations are available for specific
UMTS coverage predictions or for an AS analysis with the point analysis tool.
IX. Exporting UMTS simulation statistics

U-Net can export statistics from the results tables of any simulation and average
statistics from group of simulations. U-Net can manage globally for all the simulations.
To export the statistics from a results table, proceed as follows:
1)
2)

8-69
button.

Chapter 8
3)
Right click on the simulation group folder to open the associated context menu.
4)
Left click in the scrolling menu on [Average simulation...] to open the average
simulation results.
5)
On any results table tab (e.g. Sites. Cells. Mobiles. ...). left click on the Actions
button.
6)
Select the <Export> command.
Note:
This will open the generic table export window. It is the same export interface as the
export function for the tables in U-Net. You can export the statistics from simulations in
delimited ASCII text files.
To export a results table, proceed as follows:

1)
Select Export from the Actions button menu.
2)
Select the separator and the decimal symbol.
3)
Specify if you want to save the table header in the file.
4)
Use the buttons
and
to be exported. Finally, use the buttons
in order to define the list of fields

and
in order to change the order of
fields to be exported.
5)
Click <OK> to export.
6)
In the open dialog box, select the directory where you want to save the exported file. enter
the file name and click on open to complete export.
Or
1)
2)
Click on the <Load> button.
3)
Specify the directory where the configuration file is located.
4)
Click on Open to open the dialog.
5)
6)
In the open dialog box, select the directory where you want to save the exported
file. enter the file name and click on open to complete export.
Note:
Export settings may be saved in a configuration file. Click on Save. In the open dialog
box, specify the directory where you want to save the configuration file, type the file
name and click on Open to close the dialog.

8-70

Chapter 8
8.7.5 UMTS Simulation Outputs

I. Umts simulation outputs on sites
Each site is characterised by its maximum number of channel elements previously
defined in the site properties.
Results are detailed for:
z
The number of channel elements required on uplink and downlink at the end of
simulation.
The number of channel elements due to soft handover overhead. for UL and DL
(Nb CEs due to SHO overhead UL and DL).
The properties related to the equipment associated to each site (parameters used
during simulation): MUD factor. Rake receiver efficiency factor. carrier selection
mode. AS restricted to neighbours option and overhead channel elements on
uplink and downlink
The uplink and downlink throughputs (kbits/s) per service supported by site. UL
and DL throughputs are the number of kbits per second supported by the site on
uplink and downlink to supply (mobiles connected with the transmitters located on
the site) one kind of services. The throughput calculation takes into account the
handover connections.
II. Umts simulation outputs on cells

Each cell is defined by its carrier, its maximum power, the pilot power, the SCH power,
other CCH power, the AS threshold, the gain, reception and transmission losses, the
noise figure. Results are detailed for the total power used on a carrier, the UL total noise,
UL and DL load factors, UL and DL noise rises, the percentage of used power, the UL
reuse factor, the UL reuse efficiency, the number of UL and DL radio links, the number
of OVSF codes, the percentage of each handover type, the UL and DL throughputs,
minimum, average and maximum traffic channel powers, the number of users rejected
for each reason.
III. Umts average simulation outputs on cells

Each cell is detailed by its carrier, by the UL total noise, UL and DL load factors, UL and
DL noise rises, the total power used, the UL reuse factor, the UL reuse efficiency, the
number of UL and DL radio links, the number of OVSF codes, the percentage of each
handover type, the UL and DL throughputs, minimum, average and maximum traffic
channel powers, the number of users rejected for each reason.

8-71

Chapter 8
IV. Umts standard deviation of simulation outputs on cells

Each cell is detailed by standard deviation on the UL total noise, UL and DL load factors,
the total power used, the UL reuse factor, the UL reuse efficiency, the number of UL and
DL radio links, the number of OVSF codes, the percentage of each handover type, the
UL and DL throughputs, minimum, average and maximum traffic channel powers, the
number of users rejected for each reason.
V. Umts simulation outputs on cell components

z
The total DL power used is the total power transmitted by the transmitter on a
carrier. When constraints are settled, the calculated power cannot exceed the
maximum power value previously defined in Transmitter Properties.
The uplink total noise takes into account the total signal received at the transmitter
on a carrier (from intracell and extracell terminals) and the thermal noise.
From uplink total noise and uplink interference, U-Net calculates uplink load factor
of transmitter on a carrier. If this constraint has been selected, UL cell load factor is
not allowed to exceed the user-defined value.
The uplink reuse factor is determined from uplink intra and extra-cellular
interference (signals received by transmitter respectively from intracell and
extracell terminals).
The uplink reuse efficiency is the reciprocal of the uplink reuse factor.
The DL load factor of the cell i corresponds to the (DL average interference [due to
transmitter signals on the same carrier] for terminals in the transmitter i area) / (DL
average total noise [due to transmitter signals and to thermal noise of terminals]
for terminals in the transmitter i area) ratio.
The uplink and downlink noise rises are respectively calculated from uplink and
downlink load factors. These data point out the signal degradation due to cell load
(interference margin in the link budget).
The percentage of used power is determined from the total DL power-maximum

power ratio (power stated in W). This value also represents the cell load, as a
percentage of the total capacity reached.
Note:
The maximum power is an input data user-definable for each cell in the Properties
window. On the other hand, the power is a simulation output data calculated for each
transmitter, carrier by carrier.
The number of radio links corresponds to the number of users-transmitters links

on the same carrier. This data is calculated on uplink and on downlink. A single
user can use several radio links (handover).
8-72

z
Chapter 8
U-Net estimates the percentages of handover types in which the transmitter takes
part.
Note:
U-Net only details the results for the following handover status, no handover (1/1),
softer (1/2), soft (2/2), softer-soft (2/3) and soft-soft (3/3) handovers; the other
handover status (other HO) are globally analysed.
The uplink and downlink throughputs represent respectively the numbers of kbits
per second delivered by the transmitter on uplink and on downlink.
Minimum traffic channel power is the lowest of the powers allocated to traffic
channels for supplying services to mobiles connected to the transmitter.
Maximum traffic channel power is the greatest of the powers allocated to traffic
Average traffic channel power is the average of the powers allocated to traffic
VI. Umts simulation outputs on mobiles

Each user is defined by his location, the service and the terminal used his profile, his
mobility and his potential activity. Results are given on carriers, UL and DL requested
and obtained rates, mobile powers, connection status, best servers, HO status, active
set transmitters and associated Ec/Io.
If the detailed results box has been checked for the current simulation, results are also
given, for each (mobile - transmitters in active set) link, on the Cell power used on the
TCH (Traffic Channel), the downlink total noise, the downlink load factor, the downlink
noise rise, the downlink reuse factor, the total noise received at the terminal from the
transmitter area (Iintra (DL) and the total noise received at the terminal from other
transmitter areas (Iextra (DL), the total path loss on the link(s) and the number of uplink
and downlink channel elements. Moreover, U-Net provides the name of the clutter class
where the probe receiver is located, the orthogonality factor, and the UL and DL SHO
gains.
VII. Umts simulation outputs on mobile components

U-Net gathers power control simulation inputs and outputs, for all the users who try to be
connected.
z
X and Y are the coordinates of users who try to be connected (geographic position
determined by the 2nd random trial). The power control is based on this order.

8-73

Chapter 8
Note:
Ejected users at the end of the power control are included in this list.
Service, user mobility and status activity are the 1st random trial results (user
distribution generation).
Terminal and user profile are based on traffic description. According to the service
and activity status assigned to a user, U-Net determines his terminal and the
corresponding user profile.
The carrier used for the mobile-transmitter connection.
DL and UL requested rates: they respectively correspond to the DL and UL effective bit
rates of service.
DL and UL obtained rates: after power control simulation, the obtained rate equals the
requested rate if the mobile is connected. Else, the obtained rate is zero.
The total power transmitted by the terminal.
The best server among the transmitters entering mobile active set.
The Connection status refers to mobile ejection causes previously defined. It gives
the reasons why the mobile, even active, is not connected to any transmitter at the
end of the simulation.
The HO status is represented by the number of sites compared to the number of

transmitters in active set.
Example:
When a mobile is in connection with three transmitters and among them two co-site
transmitters (soft - softer handover), its HO status is 2/3 (two sites and three
transmitters). When the mobile is connected with only one transmitter (no handover) its
HO status is 1/1. When the mobile is connected with three co-site transmitters (softer softer handover), its HO status is 1/3.
The list of transmitters in connection with the mobile (Active set). The maximum
number of transmitters in active set is defined by the user in Terminal Properties
and limited to 4 in U-Net. Soft handover can be enabled/disabled for every service.
Ec/Io values are calculated for each transmitter in active set and may be
compared to Ec/Io thresholds defined in Mobility Type Properties.

8-74

Chapter 8
Note:
Transmitters, which Ec/Io value is AS-threshold (handover margin) lower than the best
one (Active Set link 1), are rejected from the active set.
The cell power transmitted on traffic channel. This parameter is determined for
each (mobile transmitters in active set) link.
The DL total noise is calculated for each (mobile transmitters in active set) link.
This parameter is calculated from the transmitter thermal noise and the DL total
interference at the terminal.
The DL load factor (determined for each (mobile transmitters in active set) link)
corresponds to the downlink total interference total noise at the terminal ratio.
The DL noise rise (evaluated for each (mobile transmitters in active set) link) is
deduced from the DL load factor.
The DL reuse factor (calculated for each (mobile transmitters in active set) link)
is evaluated from the interference received at the terminal from the intra
transmitter area and the total interference received at the terminal from all the
transmitters (intra and extra areas).
DL intra-cellular interference for each cell (i) of the mobile active set:
DL
(ic ) Fortho P DL
(ic ) PSCH
I int ra = P DL
tot
tot
LT
i
i
DL extra-cellular interference for each cell (i) of the mobile active set:
I extra =
DL
(ic ) Fortho P DL
(ic ) PSCH
P DL
tot
tot
LT
Tx ,iTx
The total path loss (determined for each (mobile transmitters in active set) link) is
calculated from transmitter and terminal losses, path loss (propagation result),
transmitter and terminal gains.
The number of uplink and downlink channel elements respectively refers to the
number of channel elements consumed by the user on UL and DL.
The orthogonality factor is user-defined in the clutter class Properties window.
The UL SHO gain is determined for mobile receivers connected either on UL or on

UL and DL.
UL Macrodiver sity Gain =
( ) ( )
Eb
Nt
UL
Eb
Nt
UL
tch BS
The DL SHO gain is evaluated in case mobile receivers are connected either on
DL or on UL and DL.
DL Macrodiver sity Gain =
( ) ( )
Eb
Nt
DL
Eb
Nt
DL
tch BS

8-75

Chapter 8
8.8 Specific WCDMA/UMTS Prediction Studies

8.8.1 Overview
For UMTS projects, U-Net provides two kinds of predictions.
I. Point analysis
Point analysis AS analysis is a radio reception diagnosis provided for:
UL and DL load conditions. Analysis is based on the UL load percentage and the DL
total power of cells. These parameters can be either outputs of a given simulation, or
average values calculated from a group of simulations, or user-defined cell inputs.
It's a user-definable probe receiver with associated terminal, mobility and service. This
receiver does not create any interference.
II. Coverage studies

Coverage studies where each map bin is considered as a probe user with associated
terminal, mobility and service. These are ordered in four different groups of studies,
listed in a natural planning order, from the indispensable pilot study to the study of
downlink total noise, with respect to the propagation model as defined:
z
Pilot-oriented studies to determine pilot coverage by transmitter, the pilot coverage

by signal level, overlapping area, pilot quality (Ec/Io) and pilot pollution.
Service-oriented studies to determine service availability in uplink and downlink

and effective service areas.
Handover Status study to analyse macro-diversity performance.
Except pilot coverage, coverage by signal level and overlapping studies, which are
similar to classical coverage studies, all other studies are specific to UMTS network
planning and closely related to a particular UMTS simulation.
Power control is achieved once only during simulation but never during prediction
studies. Simulation outputs such as uplink and downlink noise levels generated by the
users may be used to evaluate the radio reception. Therefore, prediction studies may
be based on:
z
UL load and DL total power modelled during power control simulation for point
analysis,
UL load and DL total power modelled during power control simulation for coverage
studies,
User-definable UL load and DL total power for coverage studies :

8-76

Chapter 8
Specific predictions can be based on either user defined load estimations (when filling
manually the UL_load and Total power cells from the cell table) or by using the "Commit
loads" button (assigning to these columns the calculated uplink loads and total powers
from the current simulation) in the Cells tab window of a simulation result window. To
use these reported values, just select the None option from the Simulation scrolling
box.
Specific UMTS coverage studies may be performed with three different purposes:
z
Analyse in detail one particular simulation.
Globally analyse all simulations and evaluate network stability with regard to traffic
fluctuations.
Analyse an average simulation.
Analyse user-definable parameters such as UL load and DL total power without

simulation.
For these coverage studies, since study GUI is generic, the general rule is to choose:
z
Either a single simulation, or a group of simulations and a user-definable

probability, or a group of simulations and average option, or, finally, no simulation.
A terminal, a mobility (or All), a service (or All).
A specific carrier or all the carriers.
And to display the results as function of the attribute you want.

In this study, each bin may be seen as a probe mobile, which does not create any
interference
Note:
z
If you modify radio parameters, before recalculating predictions, do not forget to

replay UMTS simulations first in order to base predictions on up-to-date simulations.
Ensure consistency between predictions, point analysis and simulation displayed on
map before further analysis. To help on that, U-Net provides a feature to
automatically calculate CDMA predictions after simulations without any
intermediary step.
Important: Any of these specific UMTS studies requires propagation path loss on
each bin.

8-77

Chapter 8
8.8.2 UMTS Prediction Process

I. Predicting on given umts carriers
In U-Net, specific UMTS studies can be based on given carriers.
To base your prediction on given carriers, proceed as follows:
1)
Create a new prediction or access the properties of an existing coverage study

you want to calculate again.
2)
Click the [Simulation] tab.
3)
Choose the carrier selection mode you want to consider in the Carrier scrolling
menu.
4)
Click <OK> or <Apply> to validate.
Note:
When choosing a carrier, only cells using this carrier are taken into account in
calculations. U-Net will display a coverage by carrier. To get a coverage based on all
the carriers, select the All option. In this case, U-Net displays a multi-carrier coverage. It
selects on each bin the best carrier according to the selection mode specified in the
properties of the transmitters from the current network.
II. Modelling shadowing in umts predictions

Transmitted powers on downlink and uplink interference determined during simulation
are used. On each analysed bin, a probe mobile is placed. The path loss of the probe
mobile is the computed path loss (Lpath) plus a margin (MShadowing). This one
depends on the required cell edge coverage probability and model standard deviation
at the probe mobile (either associated to the clutter class where the probe mobile is, or
a default value). In case of macro-diversity, a gain is calculated on uplink and downlink
depending on the number of used links.
You can enter a cell edge coverage probability (x %) when defining prediction
properties (point analysis: Profile, Reception and AS analysis tab and coverage
studies). Therefore, the evaluated pilot quality, uplink and downlink traffic channel
qualities are reliable x% of time.
Formulas used to compute shadowing margin, macro-diversity gains (2 and 3 links) are
detailed in the Technical reference guide.

8-78

Chapter 8
8.8.3 Managing UMTS Predictions

I. Creating predictions from modified umts simulations
This feature is provided to automatically calculate UMTS predictions after simulations
without intermediary step. In fact, you just need to define the UMTS prediction studies
you want to perform and then, press the Calculate command: first, U-Net calculates the
simulations and then, the predictions based on simulations. Therefore, it is no more
necessary to wait for the simulations to be finished to create the UMTS prediction
studies and start the calculations.
1)
Create the UMTS prediction studies you want to perform and define their
properties (colour, terminal, mobility, service). As no simulation has been
previously performed, you cannot base prediction studies on a specific simulation.
2)
Thus, choose either an average analysis (Average) or a statistical analysis based

on a probability (All) on all the future simulations.
Calculate button (or F7).
3)
Left click on the
4)
The Creation of simulations window opens.
5)
Specify the simulation inputs number of simulations to be created, convergence

criteria,
6)
Press <OK> to start the calculations.
U-Net performs the simulations and lists them in the UMTS simulation folder. Then,
U-Net carries out the prediction calculations based on the created simulations.
II. Managing umts prediction display

UMTS prediction dialogs include the U-Net generic display tab. It enables to display
covered areas with graphic settings depending on any attribute (from transmitter, site,
etc...) and to easily manage legends, tips, thresholds, etc... Since prediction study user
interface is generic, many associations between selected items in the Simulation tab (a
terminal, a mobility - or all -, a service - or all -, a specific carrier - or all) and in the
Display tab are available. So, several calculation and display settings are possible.

8-79

Chapter 8
Note:
You can analyse different mobility and several services in a same study. For any UMTS
study, in the Simulation tab, you can choose All in the Service or/and Mobility scrolling
menus. In this case, U-Net works out the coverage criterion for each service or/and
mobility type; a bin of the map will be covered if the studied coverage criterion is met for
any service or/and mobility. In addition, receiver definition and coverage display are not
linked. Parameters set in the Simulation tab are used in order to predetermine the
coverage area (area where U-Net will display coverage) while graphical settings
(available in the Display tab) enable you to choose how to represent the coverage area.
For example, it is possible to perform multi-service or/and multi-mobility pilot reception
analysis and to choose a coverage display per transmitter or depending on any
transmitter attribute.
The available display types (depending on the study to be carried out) are listed below:
z
Single colour: Coverage is mono colour; it displays areas where radio conditions
are satisfied.
Colour per transmitter: Coverage displays areas where radio conditions are
satisfied. Moreover, the bin colour corresponds to the colour of the first transmitter
in active set (best server).
Colour per service: The receiver is not totally defined. Its service can take all
existing service types. There are as many graphical coverage layers as
user-defined services. For each service, coverage layer displays areas where
radio conditions are satisfied.
Colour per mobility: The receiver is not totally defined. Its mobility can take all
existing mobility types. There are as many graphical coverage layers as
user-defined mobility types. For each mobility, coverage layer displays areas
where radio conditions are satisfied.
Colour per probability: Coverage displays areas where radio conditions are
satisfied with different levels of probability. There are as many graphical coverage
layers as user-defined probability thresholds (by default 0.5 and 0.9).
Colour per quality margin: Each coverage layer displays area where the quality
margin is greater than the user-defined threshold value. There are as many
graphical coverage layers as user-defined quality margins. The quality margin is
the difference between the quality level and the target quality level. There is
intersection between layers.
Colour per maximum quality level: Each coverage layer displays area where
the maximum signal quality (even if not reaching the quality target) exceeds the
user-defined quality level. There are as many graphical coverage layers as
user-defined quality margins. There is intersection between layers.

8-80

z
Chapter 8
Colour per effective quality level: Each coverage layer displays area where the
effective signal quality (min between the maximum and the quality target) exceeds
the user-defined quality level. There are as many graphical coverage layers as
Colour per handover status: Coverage displays areas where radio conditions
are satisfied for at least one transmitter pilot quality. There are as many graphical
coverage layers as user-defined handover status. Each layer represents a
handover status. There is no intersection between layers.
Colour per potential active transmitter number: Each coverage layer displays
area where the number of potential active transmitters is greater than the
user-defined threshold value. There are as many graphical coverage layers as
user-defined potential active transmitters. The potential active transmitter number
corresponds to transmitters checking all conditions to enter the active set. There is
Colour per required power level: Each coverage layer displays area where the
required terminal power (in order for transmitter to get a service) is greater than
the user-defined required power thresholds. There are as many graphical
coverage layers as user-defined required power level. There is intersection
between layers.
Colour per required power margin: Each coverage layer displays area where
the required power margin exceeds the user-defined threshold value. There are as
many graphical coverage layers as user-defined power margin. The required
power margin corresponds to the difference between the required terminal power
and the maximum terminal power. There is intersection between layers.
Colour per minimum noise level: The displayed noise level is the lowest of the
values calculated on all carriers.
Colour per average noise level: The displayed noise level is the average of
calculated values on all carriers.
Colour per maximum noise level: The displayed noise level is the greatest of the
Colour per minimum noise rise: The displayed noise rise is the lowest of the
values calculated from the downlink total noise, on all carriers.
Colour per average noise rise: The displayed noise rise is the average of the
Colour per maximum noise rise: The displayed noise rise is the greatest of the
Colour per polluter number: The coverage displays areas where user is
interfered by pilot signal from polluter transmitters. A polluter transmitter is a
transmitter that meets all the criteria to enter the active set but which is not
admitted due to the active set limit size.

8-81

Chapter 8
8.8.4 UMTS Prediction Studies

I. Analysing pilot reception (umts)
This study displays areas where there is at least one transmitter which pilot quality at
receiver (Ec/Io) is sufficient to be admitted in the probe mobile active set [using the
propagation model as defined before (with priority order respect)]. Only the pilot quality
from best server is displayed.
To prepare this prediction study, in the prediction creation steps, select the Pilot
reception analysis (Ec/Io) option from the study type window. The open window is
made of three tab windows: General, Simulation, and Display. An additional Statistics
tab is created after computation. For all of these, use the What's this help to get
description about the fields available in the windows.
The General tab works exactly like in common studies (coverage by transmitter,
coverage by signal level and overlapping), i.e. you may rename the study, add some
comments, define group, sort and filter criteria.
In the Simulation tab window, you may decide which simulation to study or choose a
group of simulations and prefer either an average analysis of all the simulations
included in the group or a statistical analysis of all simulations based on a
user-definable probability (probability must be a value between 0 and 1).
Finally, you can perform prediction studies without simulation. In this case, U-Net takes
into account UL load and DL total power defined in the Cells properties.
The general rule is to choose:
z
Either a single simulation. or a group of simulations and a user-definable

probability. or a group of simulations and average option. or. finally. no
simulation.
A cell edge coverage probability (in %).
A terminal. A mobility (or all). A service (or all).
Note:
When calculating a study based on no simulation, U-Net takes into account UL load
percentage and DL total transmitted power defined for each cell. In case these fields
are not filled, U-Net considers default values, 50% for UL load percentage and 40 dam
for DL total transmitted power.

8-82

Chapter 8
The Display tab is the U-Net generic display dialog allowing you to display your
resulting coverage as function of any compatible attribute.
Comment:
for each study, there are as many layers as user-defined thresholds (quality level,
quality margin...). Each layer may be displayed independently by selecting visibility flag
in folder.
Once computations have been achieved, the Statistics tab is available and contains
the detailed results of displayed layers. For each threshold value (corresponding to
a specific layer), the surface ((Si) covered stated in km2) where the prediction criterion is
met and its percentage (% of i) are specified. These data are calculated in relation to
the whole computation zone and each environment class, when environments are used
to describe the traffic cartography.
For an environment class i,
% of i = (Si) covered*100 / (Si) total
z
(Si) covered is the surface where the prediction criterion is met.
(Si) total is the total surface of the computation zone (or an environment class).
Note:
z
It is not recommended to modify radio parameters and recalculate only predictions.

Simulation(s) must have been replayed first.
Like point prediction, coverage prediction does not take into account possible
network saturation. Thus, there is no guarantee that a simulated mobile in the
prediction service area is connected, simply because simulated network may be
saturated.

map before further analysis.
It also possible to run a single unlocked study by selecting the Calculate command
from its context menu. Even if the other studies are unlocked, only this prediction will
be computed.

8-83

Chapter 8
II. Studying service area (Eb/Nt) downlink (umts)

This study displays areas where there is one transmitter (or several transmitters in
macro-diversity) which traffic channel quality at the receiver (Eb/Nt or combined Eb/Nt)
is sufficient for the probe mobile to obtain a service [using the propagation model as
defined before (with priority order respect)]. Downlink service area is limited by
maximum allowable traffic channel power.
Comment:
Actually, for a circuit switched service, when there are several transmitters in active set,
Eb/Nt from different transmitters are combined in terminal and improve reception with a
macro-diversity gain.
To prepare this prediction study, in the prediction creation steps, select the Service area
(Eb/Nt) downlink option from the study type window. The open window is made of three
tab windows: General, Simulation, and Display. An additional Statistics tab is created
after computation. For all of these, use the What's this help to get description about the
fields available in the windows.
z
Either a single simulation. or a group of simulations and a user-definable

probability. or a group of simulations and average option. or. finally. no simulation.

8-84

Chapter 8
Note:
are not filled, U-Net considers default values, 50% for UL load percentage and 40 dam
When choosing Max Eb/Nt, U-Net calculates the maximum downlink traffic channel
quality you can get at terminal or transmitter; it displays the areas where the downlink
traffic channel quality calculated by considering the maximum allowed traffic channel
power of each transmitter in receiver active set, is higher than the user-defined
thresholds.
The Effective Eb/Nt display is also offered. Here, U-Net considers required traffic
channel quality instead of maximum traffic channel quality; it colours bins of the map
where the required DL traffic channel quality is higher than the user-defined thresholds.
Comment:
For each study, there are as many layers as user-defined thresholds (quality level,
in folder.
Once computations have been achieved, the Statistics tab is available and contains the
detailed results of displayed layers. For each threshold value (corresponding to a
specific layer), the surface ((Si) covered stated in km2) where the prediction criterion is met
and its percentage (% of i) are specified. These data are calculated in relation to the
whole computation zone and each environment class, when environments are used to
describe the traffic cartography.
z

8-85

Chapter 8
Note:
z

saturated.

be computed.
III. Studying service area (eb/nt) uplink (umts)

This study displays areas where the traffic channel quality of probe mobile at
transmitter (Eb/Nt) is sufficient for the transmitter to get a service [using the propagation
model as defined before (with priority order respect)]. Uplink service area is limited by
maximum terminal power.
Comment:
The macro diversity concept is also dealt with on the uplink. Its value depends on the
handover status.
(Eb/Nt) uplink option from the study type window. The open window is made of three
tab windows: General, Simulation, and Display. An additional Statistics tab is created
after computation. For all of these, use the What's this help to get description about the
fields available in the windows.
8-86

Chapter 8
z
Either a single simulation. Or a group of simulations and a user-definable

probability. Or a group of simulations and average option. Or finally. No simulation.
A cell edge coverage probability (in %)
Note:
are not filled, U-Net considers default values, 50% for UL load percentage and 40 dBm
When choosing Max Eb/Nt, U-Net calculates the maximum uplink traffic channel quality
you can get at terminal or transmitter; it displays the areas where the uplink traffic
channel quality calculated by considering the maximum terminal power, is higher than
the user-defined thresholds.
The Effective Eb/Nt display is offered. Here, U-Net considers required traffic channel
quality instead of maximum traffic channel quality; it colours bins of the map where the
required UL traffic channel quality is higher than the user-defined thresholds.
Comment:
in folder.

8-87

Chapter 8
z
Note:
z

saturated.

be computed.
IV. Studying effective service area (umts)

Effective service area is the intersection zone between uplink and downlink service
areas [using the propagation model as defined before (with priority order respect)]. It is
the area where a service is really available for the probe mobile.
To prepare this prediction study, in the prediction creation steps, select the Effective
service area option from the study type window. The open window is made of three tab
windows: General, Simulation, and Display. An additional Statistics tab is created after
computation. For all of these, use the What's this help to get description about the fields
available in the windows.

8-88

Chapter 8

z

Note:
Comment:
in folder.
z

8-89

z
Chapter 8
(Si)total is the total surface of the computation zone (or an environment class).
Note:
z

saturated.

be computed.
V. Defining handoff status (umts)

This study displays areas [using the propagation model as defined before (with priority
order respect)] where the selected service is available and where probe mobile has in
its active set:
z
Only one transmitter : no handover (1/1)
Two non co-site transmitters : soft handover (2/2)
Two co-site transmitters : softer handover (1/2)
Three non co-site transmitters : soft-soft handover (3/3)
Three transmitters among them two co-site : softer-soft handover (merged with
soft-softer handover) (2/3)
Three co-site transmitters : softer-softer handover (1/3)
Comment:
In parenthesis is given equivalence between usual handover name and HO status
notation sometimes used in U-Net, referring to number of sites/number of transmitters
in the active set (See UMTS Simulations : Overview).

8-90

Chapter 8
Note:
z
network.
In this study, handover is allowed on areas where the service chosen by the user is
For each study, a simulation tab enables to connect to one or all simulations.
available.
Furthermore, you can choose different ways of displaying the same coverage to get
a better analysis and dimensioning information on the network.
To prepare this prediction study, in the prediction creation steps, s

elect the handover status option from the study type window. The open window is made
of three tab windows: General, Simulation, and Display. An additional Statistics tab is
created after computation. For all of these, use the What's this help to get description
about the fields available in the windows.
comments, define group, sort and filter criteria
z

Note:

8-91

Chapter 8
Comment:
in folder.
specific layer), the surface ((Si)covered stated in km2) where the prediction criterion is met
% of i = (Si)covered*100 / (Si)total
z
(Si)covered is the surface where the prediction criterion is met.
Note:
z

saturated.

be computed.

8-92

Chapter 8
VI. Studying downlink total noise (umts)

This study enables you to display areas where the total noise (Nt as it is defined in
formulas) exceeds user-defined levels [using the propagation model as defined before
(with priority order respect)].
To prepare this prediction study, in the prediction creation steps, select the Downlink
total noise option from the study type window. The open window is made of three tab
comments, define group, sort and filter criteria
z

A cell edge coverage probability (in %)
A terminal. a mobility (or all). a service (or all).
Note:

8-93

Chapter 8
Note:
In case of given service and carrier, the calculated and displayed coverage is the same
for any selected display per noise level (average, minimum or maximum) or any display
per noise rise (average, minimum or maximum).
Comment:
in folder.
z
Note:
z

saturated.

be computed.

8-94

Chapter 8
VII. Calculating pilot pollution (umts)

This study displays the areas where user is interfered by pilot signal from polluter
transmitters [using the propagation model as defined before (with priority order
respect)]. A polluter transmitter is a transmitter that meets all the criteria to enter the
active set but which is not admitted due to the active set limit size.
pollution option from the study type window. The open window is made of three tab
z

Note:

8-95

Chapter 8
Representation on map may are given regarding to the number of polluters. Each layer
may be displayed independently by selecting visibility flag in folder.
Comment:
in folder.
z
Note:
z

saturated.

be computed.

8-96

Chapter 8
VIII. Analysing a scenario at a point in umts projects

To get reception information for a given point on the map, you may use U-Net point
analysis window. Even in UMTS projects, you may use the Profile, Reception and
Results tab windows as for the other projects, on the signal received from the cell pilot.
Concerning pilot quality given by (Ec/Io) (which is the main parameter to enter an active
set) and connection status, with the point analysis tool, U-Net is able to get information
about the active set analysis of a UMTS scenario (for given mobile, mobility and service)
at the receiver location on the map by using the propagation model as defined before
(with priority order respect).
To make active the AS analysis window:
1)
From the menupoint defined by the receiver on the map bar, check the Point
analysis command in the View menu.
2)
The point analysis window opens in the lower right corner of your current
environment.
3)
Left click on the AS analysis tab.
4)
Click the
5)
Move over the current map to the places where you want to make your analysis.
from the toolbar.
Note:
The Point analysis window is automatically displayed when clicking on the
button
from the toolbar.
Point analysis is a radio reception diagnosis provided for:

z
UL and DL load conditions. Analysis is based on the UL load percentage and the
DL total power of cells. These parameters can be either outputs of a given
simulation, or average values calculated from a group of simulations, or
user-defined cell inputs.
A user-definable probe receiver terminal, a mobility and a service.
Pilot quality and connection status (Pilot, Uplink, and Downlink) are displayed for
previous conditions and without taking into account possible network saturation. Thus,
there is no guarantee that a simulated mobile in the receiver conditions can check the
point analysis diagnosis, simply because simulated network may be saturated.
A description of the AS analysis window is given in Figure 8-3.

8-97

Chapter 8
Figure 8-3 AS analysis window

Bar graph shows pilot reception from all transmitters on the same carrier (with same
colours as defined for each transmitter), displaying limit values required to be in active
set (Ec/Io threshold, (Ec/Io) best server-A-S threshold). Grey background displays
transmitters in active set.
You may modify receiver characteristics. U-Net will automatically check pilot quality
and channel availability:
z
If you change terminal, it will modify maximum available transmitting power in

uplink and the active set size.
If you change mobility, it will modify pilot quality thresholds and Eb/Nt target per
service in downlink.
If you change service, it will modify the active set size and Eb/Nt target in downlink.
8.9 WCDMA/UMTS Resources Allocation

8.9.1 Overview
Once your UMTS network is built, U-Net provides you with some additional features in
order to complete your network planning by the allocation of neighbour cells and
primary scrambling codes.
Like in GSM/GPRS/EDGE or CDMA/CDMA2000, it is possible to easily allocate
neighbours within U-Net. This can be made either manually, or automatically, imposing
several constraints on the potential cells that could be part of a neighbourhood. Then,
once be allocated, neighbours can be easily managed (modification or deletion). Finally,
U-Net makes easy the visualisation of neighborhoods on the active map.
8-98

Chapter 8
Downlink scrambling codes permit to separate cells from others. It is strongly

recommended to assign different codes to a given cell and to cells belonging to its
neighbour list. Some additional separation constraints can be also defined. In U-Net,
you can either allocate it manually for each cell or automatically for all cells or a group of
cells in the network. Depending on the allocation strategy, several constraints can be
imposed on scrambling code groups and domains, exceptional pairs, distance and
neighbours. At any moment, it is possible to check the consistency of the current
scrambling code allocation in the studied network.
8.9.2 UMTS Neighbours

I. Allocating umts cell neighbours manually
Cell neighbours list represents a way to optimize the search for possible cells aimed to
perform handover from the current coverage area. Allocating neighbours in a network
is optional but makes the handover process easier. Defining neighbours helps in the
determination of appropriate scrambling codes.
Note:
z
Neighbours have no impact on interference calculations : all cells in a network

interfere with the others.
Neighbours of any linked project in co-planning can also be displayed and chosen
manually.
Manual allocation of UMTS neighbours must be performed for each cell, one at a time.
To do this, proceed as following Table 8-23:
Table 8-23 Manual allocation of CDMA/CDMA2000 neighbours
Method
Method 1
step
1)
2)
Right click on the transmitters folder to get the related

context menu.
3)
Choose the [Cells\Open Table] command from the open

menu.
4)
Once the [cells] table is open.
5)
Double click on the cell from which you want to define the
neighbourhood.
6)
Click the Intra-technology Neighbours tab from the current

window.
8-99

Chapter 8
Method
Method 2
Method 3
step
7)
In the displayed window. use the top table. Select the row
with symbol
. Then in the Neighbours column. click on
cell to choose from the scrolling box the desired neighbour.
In the scrolling box. U-Net lists all the transmitters located
within a radius of 30 km around the reference transmitter
(cell).
8)
Click either another cell of the table. or the

button to validate and add a new row to the table.
9)
When you have completed your entry. click on OK to close

the dialog box.
1)
2)

context menu.
3)
Right click on the cell from which you want to define the
neighbourhood.
4)
Choose the record properties option from the context menu

(or from the Records menu from the menu bar).
5)
neighbourhood.
6)

window.
7)
In the displayed window. use the top table. Select the row
with symbol
. Then in the Neighbours column. click on
In the scrolling box. U-Net lists all the transmitters located
(cell).
8)
Click either another cell of the table. or the

9)

the dialog box.
1)
2)

context menu.
3)
neighbourhood.
4)
Choose the [Cells/Neighbours/Intra-technology Neighbours]

command from the Transmitters folder context menu.
5)
In the displayed table. Use the row with symbol

. Click
the cell of the Transmitters column to select a reference cell
and then. Click the cell of the Neighbours column to choose
a neighbour.
6)
Click another cell of the table to validate and add a new row
to the table.
7)

the dialog box.
8-100

Chapter 8
Note:
It is possible to add/remove symmetric neighbourhood links at once. To do this, use
the commands [Symmetries] and [Delete link and symmetric] available in a context
menu. This one can be open by right clicking on the neighbour you have added or
you want to delete.
Due to the organisation of neighbourhoods in tables, the copy-paste feature can be
used in order to generate the neighbour table of a global network (or per cell).
Standard features for managing table contents (Copy/Paste, Delete, and Display
columns, Filter, Sort, and Table Fields) are available in a context menu (when right
clicking on column(s)) or record(s) and in the Format, Edit and Records menus.
This feature only deals with GSM/GPRS/EDGE, CDMA/CDMA2000 and UMTS
technologies.
An automatic allocation tool is also available.
II. Allocating umts cell neighbours automatically

Allocation algorithm allocating automatically permits to automatically allocate
neighbours globally to active transmitters in the current network by imposing
constraints on active transmitters that must be satisfied. Force neighbour reciprocity,
adjacency and within co-site is possible.
To allocate automatically UMTS neighbours in a network, proceed as follows:
1)
2)
Right click on the transmitters folder to get the related context menu.
3)
Choose the [Cells/Neighbours/Automatic allocation...] command from the open

menu.
4)
Set the parameters for the current Auto Neighbours allocation study.
Automatic neighbour allocation is based on the following parameters shown in Table

8-24.
Table 8-24 Neighbour allocation parameters
parameters
In detail
Max number of neighbours
This is the maximum number of neighbours to be

allocated to a cell. This value may be either globally
set for all the cells (in the automatic allocation
algorithm), or specified for each cell (in the Cells
table).
U-Net uses the value defined at the cell level if
available, otherwise it considers the global value.

8-101

Chapter 8
parameters
In detail
Max Inter-Site distance
This is the maximum distance you can have between

the reference cell and a candidate neighbour. If the
distance between the reference cell and a candidate
neighbour is higher than this value, then the candidate
neighbour is discarded.
Coverage conditions
between the reference cell
(A) and a candidate
neighbour (B)
U-Net determines the overlapping area between SA

and SB ( S A SB ) as defined below:
SA is the area where:
z
The pilot signal received from the cell A is greater

than minimum pilot signal level.
The pilot quality from A exceeds a user-definable
minimum value (minimum Ec/I0).
The pilot quality from A is the best.
SB is the area where:

z
Power contributing to Io:

Two ways enable you to
determine the I0 value.
The pilot signal received from the cell B is greater

than minimum pilot signal level.
The pilot quality from B is greater than the pilot
quality from A minus the Ec/I0 margin. The Ec/I0
margin has the same meaning as the AS-threshold
defined in the Cell properties. So, it should logically
have the same value.
% Max Power: A reduction factor (% of maximum
powers contributing to I0) is applied to the cell
maximum powers (defined in Cell properties).
Total Power Used: U-Net takes into account the
total downlink power used defined for each cell.
% min Covered Area: This is
percentage of covered area to be
order not to discard the candidate
The percentage of covered area
using this formula
Calculation options
S A SB
SA
a minimum
exceeded in
neighbour B.
is calculated
Force co-site cells as neighbours: This option

enables you to force the co-site cells in the
neighbour list of a reference cell. The co-site cells
are listed just after the forced exceptional pairs.
Force adjacent cells as neighbours: When
selecting this option, adjacent cells are ordered in
the neighbour list just after co-site cells.
Force neighbour symmetry: This option enables
user to consider the reciprocity of a neighbourhood
link.
Force exceptional pairs: Exceptional pairs have
the highest priority. Forced neighbours are
top-ranked in the neighbour list. Forbidden
neighbours must not be listed as neighbours.

8-102

Chapter 8
5)
Click the
button to start calculations.
6)
In the Results part, U-Net provides a list of neighbours and the number of
neighbours for each cell. In addition, it indicates allocation reason for each
neighbour. We can have result shown in Table 8-25:
Table 8-25 Results

Reason
Description
When
Rank in
the list
Forced
Neighbourhood relationship defined

as exceptional pair
Only if the Force exceptional

pairs option is selected
Co-site
The neighbour is located on the

reference cell site
Only if the Force co-site cells

as neighbours option is
selected
Adjacent
The neighbour is adjacent to the

reference cell
Only if the Force adjacent

cells as neighbours option is
selected
% of covered
area
Neighbourhood relationship that

fulfils coverage conditions
Any time
Symmetric
Neighbourhood relationship forced

in order to fulfil symmetry conditions
Only if the Force neighbour

symmetry option is selected
Existing
Existing neighbourhood
relationship
Only if the Reset option is

not selected and in case of a
new allocation
and overlap
area (km2) in
brackets
7)
Once calculations are achieved, click the
button to assign
neighbours to cells. Neighbours are listed in the Intra-technology Neighbours tab

of each cell Properties window.
8)
Click the <Close> button to achieve the procedure.

8-103

Chapter 8
Note:
z

technologies.
No prediction study is needed to perform the automatic neighbour allocation. When

starting an automatic neighbour allocation, U-Net automatically calculates the path
loss matrices if it does not find them.
You can carry out neighbour allocation globally on all the cells or only on a group of
cells. In this case, U-Net will consider all the cells contained in the group of
transmitters, the symmetric neighbours of these cells and all the other ones, which
have an intersection area with the cells of the group.
If the Reset button is unchecked and no new neighbour is found after a new
allocation calculation, the Results part stays empty. Nevertheless, existing
neighbours (from a previous allocation) are kept as before. U-Net only displays the
cells for which it finds new neighbours. Therefore, if a cell has already reached its
maximum number of neighbours before starting the new allocation, it will not appear
in the Results table.
III. Displaying current umts neighbour list

U-Net provides the possibility to open an editable table referencing all the UMTS
neighbours of the current network.
To access the UMTS neighbour table, proceed as follows:
1)
2)
3)
Choose the [Cells/Neighbours/intra-technology Neighbours] command from the

open menu.
4)
In the displayed table. U-Net lists reference cells and their related neighbours. In
addition. it indicates the number of neighbours assigned to each reference cell.
and for each neighbour:
The distance between the neighbour and the reference cell.
If the neighbourhood relationship is symmetric or not.
The type of allocation. Three values are available, manual (copy/paste of a

neighbour list, manual edition of neighbours), automatic (automatic allocation), or
imported (Planet import, generic import, import using an add-in).
The neighbour rank in the list of neighbours of the reference cell. This information
is given only in case of an automatic allocation.
The allocation reason. This information is given only in case of an automatic

allocation.

8-104

Chapter 8
This table can be used to allocate neighbours manually. Standard features for
managing table contents (Copy/Paste, Delete, and Display columns, Filter, Sort, and
Table Fields) are available in a context menu (when right clicking on column(s)) or
record(s) and in the Format, Edit and Records menus.
IV. Deleting the allocated umts neighbours

You may add new neighbours or remove allocated neighbours.
To delete allocated neighbours, proceed as following Table 8-26:

Table 8-26 delete allocated neighbours
Method
Method 1
step
1)
2)

context menu.
3)
Choose the [Cells/Open Table] command from the open

menu.
4)
Once the cells table is open.
5)
neighbourhood.
6)

7)
Click the Intra-technology [Neighbours] tab from the current

window.
8)
In the displayed table. Select the desired neighbour row.
9)
Press the keyboard <Del (or Suppr.)> key
10) Click on <OK> to validate and close the dialog box.

Method 2
Method 3
1)
2)

context menu.
3)
neighbourhood.
4)
Click the Intra-technology [Neighbours] tab from the current

window.
5)
6)
Press the <Del (or Suppr.)> key.
7)
Click on <OK> to validate and close the dialog box.
1)
2)

context menu.
3)

command from the open menu.
4)
5)
Press the keyboard <Del (or Suppr.)> key.

8-105

Chapter 8
Method
step
6)
Note:
It is possible to remove symmetric neighbourhood links at once. To do this, use the
command [Delete link and symmetric] available in a context menu. This one can be
open by right clicking on the neighbour you want to delete.
V. Displaying umts neighbours on the map

Once the UMTS cell neighbours have been allocated, you can display a given
neighbourhood (at the transmitter level) on the map.
To display the neighbours of any transmitter (whatever the carrier is), proceed as
follows:
icon from the toolbar.
1)
Click on the Neighbour graphic management
2)
Left click on the desired transmitter to select it on the map.
3)
U-Net displays on the map shown in Figure 8-4:
The symmetric neighbourhood links with the selected transmitter (reference

transmitter). A single black line represents these links.
The outwards neighbourhood links (which are not symmetric); they are coloured
as the reference transmitter. They show the neighbours of the selected transmitter
(however, the selected transmitter is not one of their neighbours).
The inwards neighbourhood links (which are not symmetric). They show the
transmitters, which have the selected transmitter as neighbour (however, these
transmitters are not in the neighbour list of the selected transmitter). Each link has
the transmitter colour.

8-106

Chapter 8
Figure 8-4 for the transmitter Site0_2 located on Site 0
Note:
z
It is possible to configure the neighbourhood links you wish to display on the map
and to display neighbourhood relationships on a given carrier you may select. To do
this, right click on the transmitters folder and choose the [Neighbours/Display
options...] command from the open menu.
Finally, when you select a transmitter on the map, U-Net is able to show the
coverage areas of its neighbours. You must just display on the map a Coverage by
transmitter study (with a colour display by transmitter) preliminary calculated.
8.9.3 Scrambling Codes

I. Overview
512 scrambling codes are available. They are distributed in 64 clusters of 8 scrambling
codes. Clusters are numbered from 0 to 63. Scrambling codes are numbered from 0 to
511.
Available scrambling codes depend on the country and on the area; it is necessary to
distinguish borders from other zones. To model this, domain and group tables have
been created.
z
A domain corresponds to a border or a zone of the country.
A group is a set of clusters.

8-107

z
Chapter 8
Each group must be associated to one or several domains. Therefore, a domain

consists of several groups.
Firstly, scrambling codes can be manually assigned to any cell of a UMTS network.
Then, using the definition of groups and domains, and imposing some constraints on
them and on neighbours, second neighbours, minimum distance and exceptional pairs,
we can choose a strategy (clustered or distributed) in order to start the automatic tool.
Once allocation is completed, a Audit tool is available.
II. Creating scrambling code domains and groups

512 scrambling codes are available. They are distributed in 64 clusters of 8 scrambling
codes. Clusters are numbered from 0 to 63. Scrambling codes are now numbered from
0 to 511.
To define domains and groups of scrambling codes, proceed as following Table
8-27:
Table 8-27 Define domains and groups of PN Offsets
Method
Method 1
Method 2
step
1)
2)

context menu.
3)
Choose the [Cells/Primary scrambling codes /Domains...]

4)
In the Domains dialog. you can enter a domain per line. To

validate a domain creation. select another line.
5)
Select a domain in the table and click on the Properties...

button.
1)
2)

context menu.
3)
Choose the [Cells/Primary scrambling codes /Domains...]

4)
In the Domains dialog. you can enter a domain per line. To

validate a domain creation. select another line.
5)
Select the line relating to a domain and double click on it.
In the domain properties dialog, specify the name of group(s) that you want to
associate to this domain and define for each of them:
z
The lowest available primary scrambling code (Min).
The highest available primary scrambling code (Max).
The value interval between the primary scrambling codes (Step).

8-108

z
Chapter 8
The scrambling code(s) you do not want to use (Excluded). You can paste a list of
codes; separator must be a blank character.
Additional scrambling code(s) you want to consider during allocation (Extra). You
can paste a list of codes; separator must be a blank character.
You can also define the domain-group pairs in the Group of primary scrambling codes
window.
1)
After defining all the domains. Close the Domains dialog.
2)
3)
Choose the [Cells/Primary scrambling codes/Groups...] command from the

open menu.
4)
In the Group of primary scrambling codes window. Select a domain and

associate one or several groups of scrambling codes to each of them. Define
the groups as explained above.
The defined domains can be now assigned to cells in order then to be used as
constraints in the automatic allocation of scrambling codes.
III. Assigning a scrambling code domain to a cell

After having defined domains and groups, you can assign a domain to each cell.
Therefore, U-Net will choose primary scrambling codes of the associated domain
during allocation.
To assign a domain to cells, you must access cell properties and fill the appropriate field.
This can be made either from:
z
The transmitter property dialog (Cells tab).
The cell property dialog.
The cell table.
The domain association will then be used by the automatic allocation tool.
IV. Allocating scrambling codes to umts cells manually

U-Net allows you to manually force scrambling codes for cells of your network. Hence,
these can be locked in order to be kept unchanged by the automatic tool.
To give a primary scrambling code to a cell, you must access cell properties. This can
be made either from :
z
The cell table.
After allocation is completed (manually or automatically), constraints can be also

checked by an automatic tool.
8-109

Chapter 8
V. Defining exceptional pairs for scrambling code allocation

In addition to standard constraints (reuse distance, neighbours and domains), it is possible
to specify pairs of cells, which cannot have the same primary scrambling code. You can
enter these forbidden pairs in the Exceptional separation constraints table.
To access the Exceptional pairs table, proceed as follows:

1)
2)
3)
Choose the [Cells/Primary scrambling codes/Exceptional pairs...] command from

the open menu.
4)
In the Exceptional separation constraints dialog. Indicate the pairs of cells.
VI. Allocating scrambling codes to umts cells automatically

You can carry out scrambling code allocation on all the cells or only on a group of cells.
In this case, U-Net will consider all the cells defined in the group of transmitters.
Scrambling code allocation is based on:
z
Neighbourhood and secondary neighbourhood if neighbour allocation has been

performed beforehand.
Reuse distance.
Domains of scrambling codes.
Forbidden pairs.
Scrambling code automatic allocation can also be made on a specific carrier or on all.
U-Net assigns scrambling codes to transmitters using the selected carrier.
To automatically allocate primary scrambling codes to all the cells, proceed as follows:
1)
2)
3)
Choose the [Cells/Primary scrambling codes/Automatic allocation...] command

from the open menu.
In this dialog, you can impose to the algorithm to take into account:
z
The existing neighbours listed in the Neighbours table (option Existing

neighbours) : A cell and its neighbours cannot have the same scrambling code.
The neighbours of the cell cannot have the same scrambling code.
The neighbours of listed neighbours (option Second neighbours) : A cell and

the neighbours of its neighbours cannot have the same scrambling code. In

8-110

Chapter 8
addition, all the neighbours (first neighbours and second neighbours) cannot have
the same scrambling code.
Note:
U-Net automatically selects the option Existing neighbours when choosing the option
Second neighbours.
A criterion on Ec/Io (option Additional Ec/Io conditions) : All the cells fulfilling Ec/Io
condition will not have the same scrambling code.
When this option is selected, you must specify a minimum threshold (minimum Ec/Io), a
margin (Ec/Io margin) and a cell edge coverage probability. In this case, for a reference
cell A, U-Net considers all the cells B that can enter active-set on the area where the
reference cell is the best server (area where (Ec/Io)A exceeds the minimum Ec/Io and
is the highest one and (Ec/Io)B is within a Ec/Io margin of (Ec/Io)A).
Note:
U-Net takes into account the total downlink power used by the cell in order to evaluate
Io. Io equals the sum of total transmitted powers. In case this parameter is not specified
in the cell properties, U-Net uses 50% of the maximum power.
A reuse distance: radius within which two cells on the same carrier cannot have the
same primary scrambling code
An allocation strategy. Two allocation strategies are now offered:
z
Clustered allocation: The purpose of this strategy is to choose scrambling codes

among a minimum number of clusters. U-Net will preferentially allocate all the
codes from same cluster.
Distributed allocation: This strategy consists in using as many clusters as

possible. U-Net will preferentially allocate codes from different clusters.
4)
Select one carrier or all on which you want to run the allocation.
5)
Select the Reset all codes option to delete the existing codes and carry out a new
scrambling code allocation. If not selected, existing codes are kept.
6)
Click on Run to start the automatic allocation; U-Net displays the automatic
allocation results in the Results part.
7)
Then, click on Commit to assign primary scrambling codes to cells.

8-111

Chapter 8
To automatically allocate primary scrambling codes to a group of cells, proceed as

follows:
1)
2)
Right click on the group of transmitters folder to get the related context menu.
3)
Choose the [Cells/Primary scrambling codes/Automatic allocation...] command

from the open menu.
4)
window,
5)
Select calculation options (as defined above) in the dialog.
6)
Click on <Run> to start the automatic allocation; U-Net displays the automatic
allocation results in the Results par.
7)
Then, click on <Commit> to assign primary scrambling codes to the group of cells.
Note:
U-Net will take into account both real distance and the azimuths of antennas to
calculate the inter-transmitter distance to be compared with the reuse distance.
VII. Scrambling code allocation process

Algorithm works as follows:
z
U-Net assigns different primary scrambling codes to a given cell i and to its
neighbours,
For a cell j which is not neighbour of the cell i, U-Net gives it a different code:
- If the distance between both cells is lower than the reuse distance.
- If the cell i -cell j pair is forbidden.
When the Second neighbours option is checked, a cell and the neighbours of its
neighbours cannot have the same scrambling code. In addition, all the neighbours
(first neighbours and second neighbours) cannot have the same scrambling code.
U-Net allocates scrambling codes starting with the most constrained cell and ending
with the lowest constrained one. The cell constraint level depends on its number of
neighbours and whether the cell is neighbour of other cells. Here, the neighbour term
includes both manually specified or automatically allocated neighbours and cells, which
are within the reuse distance of a studied cell. When cells have the same constraint
level, cell processing is based on order of transmitters in the transmitters folder.

8-112

Chapter 8
Note:
In order to calculate the effective inter-transmitter distance (which will be compared to
the reuse distance), U-Net takes into account both real distance and azimuths of
antennas. For further information, please, refer to Technical reference guide.
The scrambling code choice depends on domains associated to cells and on the
selected allocation strategy. When no domain is assigned to cells, U-Net uses the 512
primary scrambling codes. Several scenarios are detailed hereafter:
Let us consider 10 scrambling codes to be allocated.
1)
1st case: We assume that any domain is assigned to cells. Here, U-Net will be able
to use the 512 primary scrambling codes.
If selected the Clustered option, U-Net will choose eight codes in the cluster 0 and
two codes in the cluster 1. Therefore, the allocated scrambling codes will be 0, 1, 2,
3, 4, 5, 6, 7, 8, and 9.
If you check the Distributed option, U-Net will take the first code of clusters 0, 1, 2,
3, 4, 5, 6, 7, 8, 9. So, it will assign the codes 0, 8, 16, 24, 32, 40, 48, 56, 64 and 72.
2)
2nd case: We assume that the domain 1 is associated to cells. Domain 1 contains
two groups, the group 1 consisted of cluster 0 (available codes: 0 to 7) and the
group 2 including clusters 2 and 3 (available codes: 16 to 31).
If selected the Clustered option, U-Net will choose eight codes in the group 1 and
two other ones in the group 2 (the first two codes of the cluster 2). So, allocation
result will be 0, 1, 2, 3, 4, 5, 6, 7, 16, and 17.
If you check the Distributed option, U-Net will select the first code of the group 1
(cluster 0), the first code of the cluster 2 (group 2), the first code of the cluster 3
(group 2), the second code of the group 1 (cluster 0), the second code of the
cluster 2 (group 2), the second code of the cluster 3 (group 2) and so on.... Result
of allocation will be 0, 16, 24, 1, 17, 25, 2, 18, 26, and 3.
3)
3rd case: We assume that the domain 1 is associated to cells. Domain 1 contains
one group, the group 1 consisted of cluster 1 (available codes: 8 to 15). As there
are not enough scrambling codes available in the group 1, U-Net does not allocate
any scrambling code and displays an error message Primary scrambling code
allocation failed.
VIII. Checking the consistency of the scrambling code assignments

A checking algorithm is available. It enables you to examine if there are some
inconsistencies after having manually performed some changes.

To use the checking algorithm, proceed as follows:
1)

8-113

Chapter 8
2)
3)
Choose the [Cells/Primary scrambling codes/Audit...] command from the open

menu.
4)
window.
5)
In the Scrambling code checking window. select the allocation criteria that you
want to check as following Table 8-28:
Table 8-28 PN Offset checking window

criteria
step
Neighbourhood
Checking is carried out on the neighbour cells (listed

in the Neighbour tab); they must not have the same
scrambling codes.
Second order
neighbours
A cell and the neighbours of its neighbours do not

have the scrambling code.
All the neighbours (first neighbours and second
neighbours) do not have the same scrambling
code.
Exceptional pairs
Checking is performed on the forbidden pairs of cells;

they must not have the same scrambling code.
Reuse distance
Checking concerns cells which inter-transmitter

distance is lower than the reuse distance you can
define; they must not have the same scrambling code.
Domains
U-Net checks if the allocated PN Offsets belong to the

domain assigned to the cells.
6)
Click on <OK> to start the checking algorithm.
U-Net details the checking results in a report. This report is a text file called
CodeCheck.txt; it is stored in the temporary folder on your workstation. For each
selected criterion, U-Net gives the number of detected inconsistencies and details each
of them.
For criteria 1, 2, 3 and 4, it displays the name of cells and the common scrambling code.
In case of criterion 5, it lists the name of cells, which do not satisfy the criterion, the
associated domains and the allocated scrambling codes.
IX. Displaying the reuse of scrambling codes on the map

Standard display features available at the transmitter and prediction study levels may
be used in order to know the distribution of PN offsets on the map. In addition, grouping
features of transmitters are available; they enable you to regroup in explorer the
transmitters which cells have the same PN Offset. Therefore, it is possible:
z
To give a colour to transmitters depending on the assigned scrambling codes.
To display the assigned scrambling codes in labels or tip balloons.

8-114

z
Chapter 8
To colour the service area of transmitters depending on the assigned scrambling

codes.
To group transmitters by scrambling code.
Note:
transmitter has more than one cell, U-Net does not know the carrier to be considered.
In this case, no value is collected (#).

8-115

Chapter 9
CDMA/CDMA2000 Project Management
Chapter 9 CDMA/CDMA2000 Project Management

9.1 Overview
1xRTT (1st eXpansion Radio Telephone Technology) and IS95 (Interim Standard 95)
are radio technologies using CDMA (Code Division Multiple Access) principles. UMTS
is based on Wideband CDMA air interface whereas CDMA/CDMA2000, like IS95, on
Narrowband CDMA. CDMA/CDMA2000 is available in U-Net with the optional UMTS
module.
In CDMA/CDMA2000, everybody works at the same frequency; signals are spread
over a band of 1.2288 MHz (on each carrier) and distinguished by the use of Walsh
codes. Nevertheless, this induces potentially high levels of noise which can be
defeated by sophisticated power controls on uplink (from terminals) and on downlink
(from transmitters) traffic channels.
Because of power control, there is not a single solution to model a CDMA network, and
results totally depend totally on network parameters such as traffic and user behaviours.
Hence, these parameters have to be modelled before starting calculations via user
distributions. Simulation results provide a snapshot of the CDMA network at a certain
time.
In order to simulate user distributions and associated behaviours, some parameters
have to be tuned. These are services, radio configurations, user profiles and
environment types. Each of these is easy to manage like any other folder-like objects
within U-Net. All these parameters go together with traffic maps, based on
environments, on user profiles (with no required definition for environment parameters)
or on Transmitters and Services (in term of rates or number of users - with required of
definition for environment and user profile parameters).
CDMA/CDMA2000 simulations power control and specific CDMA coverage predictions
need the definition of the previous parameters. Classical coverage predictions are also
available to study cell pilots. The point analysis tool allows a specific analysis of any
active set at a given point on the map, for a particular scenario (service and radio
configuration of a probe user which the current status is provided by network simulation
results).
Geo data are easily manageable like for other projects. You may either create or import
geographic objects. Sites, antennas, station templates, transmitters, measurements,
and propagation models work in the same way for CDMA/CDMA2000 and the other
technology projects. Nevertheless, due to an enhanced resource management to
9-1

Chapter 9
consider at site level, site equipment and resource management per service have been
introduced. Furthermore, since CDMA support several carrier networks, a new item
characterising each carrier per transmitter has been introduced: CDMA cells. Hence,
many properties are defined at the cell level (e.g. powers).
Like for the other types of technology, neighbours may be manually defined by the user
or with the help of the neighbour automatic allocation tool, but at the cell level.
The What's this context tool allows the user to understand the specific CDMA fields
and features available in dialog boxes.
9.2 CDMA/CDMA2000 Specific Concepts

In a CDMA (Code Division Multiple Access) network, a code is allocated to each link
transmitter-terminal. This code allows the terminal to identify the useful signal spread
over the whole bandwidth as mobiles use the same frequency band simultaneously.
Consequently, each mobile is indirectly interfered by all the others. It is thus essential
for IS95 or CDMA/CDMA2000 to perform reliable power control especially on the uplink,
in order to limit network interference level.
To achieve power control simulation and coverage calculation, CDMA planning
requires traffic snapshots unlike GSM planning, which only needs traffic data when
dimensioning a network for a certain grade of service.
CDMA coverage directly depends on offered traffic: the more the traffic is, the smaller
the coverage zones are. This phenomenon is called cell breathing. As Traffic is
dynamic, coverage calculation is necessarily statistical.
U-Net achieves coverage predictions in two steps:
1)
First, it simulates power control for realistic user distributions to obtain network
parameters and interference level (simulation part).
2)
Then, it generates bin-based coverage probability predictions (prediction part).
See CDMA projects protocol.

9-2

Chapter 9
Note:
z
U-Net enables or CDMA/CDMA2000 network planning, 2 (2,5G) network based on

Narrowband Code Division Multiple Access technique (N-CDMA) and multi-service
management. These major CDMA concepts and new technologies require new
network and data modelling, with appropriate needs for traffic modelling. A wide
range of different CDMA/CDMA2000 services available to consumers, generates a
more complex traffic than standard voice transmissions. Appropriate traffic data
model and relevant localization on a map, i.e. traffic cartography represents a major
input for CDMA/CDMA2000 planning. Specific CDMA objects are available when
creating a new project with U-Net. The CDMA projects are designed to provide
specific CDMA radio and traffic data structures, CDMA simulations and predictions
folders.
CDMA and CDMA2000 technologies are available in U-Net only if the optional
UMTS module is installed.
9.3 CDMA/CDMA2000 Projects Protocol

A classical CDMA/CDMA2000 project protocol, within U-Net, is described below as
Table 9-1.
Table 9-1 CDMA/CDMA2000 project protocol
content
explain
Network design
Setting radio data
Pilot studies based only on signal reception
Traffic input
Traffic description
activity probabilities
Traffic map design
number of
subscribers or users
(depending on the
type of map)
Realistic user distribution

generation
CDMA/CDMA2000
oriented prediction
studies
Point predictions
Coverage predictions
Network optimization
Neighbour allocation
Allocating_PN_offsets_to_CDMA_
CDMA2000_c
Simulations (Evaluation
of interference level)

9-3

Chapter 9
9.4 Managing CDMA/CDMA2000 Radio Data

9.4.1 CDMA/CDMA2000 Site Equipment
I. Creating CDMA/CDMA2000 site equipment
In CDMA/CDMA2000, site equipment allows the user to define some equipment
related to channel elements and some other specific CDMA parameters and calculation
options (MUD factor, Rake efficiency factor, and Carrier selection, Overhead CEs, AS
restricted to neighbours).
To create a CDMA/CDMA2000 site equipment, proceed as follows:
1)
2)
3)
4)
In the Equipment window, describe a piece of equipment per line. Type its name,
the manufacturer name and define. (See Table 9-2 ).
5)
Click on
to close the table.
Table 9-2 Equipment parameters

parameter
explain
MUD factor
Multi-User Detection is a technology used to

decrease intra-cellular interference on uplink. MUD
is modelled by a coefficient between 0 and 1; this
factor is considered in the UL interference
calculation. In case MUD is not supported by
equipment, enter 0 as value.
Rake receiver efficiency

factor
This factor enables U-Net to model macro-diversity

on uplink. U-Net uses it to calculate the uplink SHO
gain and uplink signal quality in simulations, point
analysis and coverage studies. This parameter is
considered on uplink for softer and softer-softer
handovers; it is applied to the sum of signals
received on the same site. The factor value can be
between 0 and 1. It models losses due to the signal
recombination imperfection.
Carrier selection
It refers to carrier selection mode used during the

transmitter admission control in mobile active set.
Three methods are available:
z
UL min noise: The least loaded carrier (carrier

with the lowest UL load factor) is selected.
DL min power: The carrier with lowest used total
DL power is selected.
Random: The carrier is randomly chosen.

9-4

Chapter 9
parameter
explain
Overhead CEs uplink and

downlink
number of channel elements that a cell uses for

common channels on uplink and downlink.
AS restricted to neighbours
This option is used to manage mobile active set. If

you select this option, the other transmitters in
active set must belong to the neighbour list of the
best server.
Note:
terminal radio configurations.
II. Managing CDMA/CDMA2000 site equipment

Site equipment is listed in a table in U-Net. So, as many other objects, they are easy to
manage both in term of contents or handy tools.
To access to the CDMA/CDMA2000 site equipment table, proceed as follows:
1)
2)
3)
4)
The table displays each piece of equipment in each line.
5)
Click on
to close the table.
Note:
z

terminal radio configurations.

9-5

Chapter 9
III. Managing channel element consumption per CDMA/CDMA2000 site

equipment
UL and DL channel elements are independently dealt with in power control simulation.
Furthermore, the number of channel element required by a site depends on site
equipment, user service and link direction (up or down).
To describe channel element consumption during CDMA/CDMA2000 simulation,
proceed as follows:
1)
2)
3)
Left click the [Equipment/Channel Element consumption] command from the open
scrolling menu.
4)
In the CE consumption window, enter for each equipment-terminal (RC) pair the
number of UL and DL channel elements that U-Net will consume during power
control simulation.
5)
Click on
to close the table.
IV. Assigning CDMA/CDMA2000 site equipment to sites

Once equipment related to channel element are defined, it is possible to assign a piece
of equipment to each site.
To assign a piece of equipment to a site proceed as follows Table 9-3.
Table 9-3 Assign a piece of equipment to a site
Method
Method 1
Method 2
step
1)
2)
Expand the Sites folder by clicking on the

it
3)
Right click on the site you want to manage.
4)
5)
Click the Equipment tab.
6)
Use the What's this help to get description about the open
dialog window.
7)

elements available for the site; then, click on the Equipment
8)
1)
Select on the map the site you want to manage by right

clicking on it (
button in front of
).
2)
3)
Click the Equipment tab.
4)
Use the What's this help to get description about the open
9-6

Chapter 9
Method
step
dialog window.
5)

elements available for the site; then, click on the Equipment
6)
Note:
z
In case you have defined neither equipment nor channel element consumption,
U-Net considers the following default values, Rake efficiency factor = 1, MUD factor
= 0, Carrier selection = UL minimum noise, Overhead CEs downlink and uplink = 0,
AS restricted to neighbours option not selected, and uses one channel element per
link (up or down) for any service, during power control simulation.
Equipment can be also assigned by accessing site table.
9.4.2 Transmitter CDMA/CDMA2000 Specific Parameters

I. Defining the transmitter CDMA/CDMA2000 global parameters
In U-Net, some parameters which are globally related to the CDMA technology can be
accessed easily and applied to all the items of a network; these are called global
parameters.
Some of them are used as global values, other as default values. All of these are
essential in CDMA/CDMA2000 power control simulations.
To access the global parameters of a CDMA/CDMA2000 network, proceed as follows:
1)
2)
3)
4)
Click the [Global parameters] tab.
5)
Click< OK> to close the dialog.
9.4.3 CDMA/CDMA2000 Cells

I. Definition
Because U-Net supports multi-carriers networks, and also since it is possible to define
some rules about carrier selection for a mobile when creating its active set, a new level
has been introduced, the cell level. A cell defines a carrier on a transmitter. Data of
9-7

Chapter 9
interest like transmission powers (Pilot, Synchronization, Paging, and Maximum

power), total power, UL load percentage, PN Offsets, or active set thresholds are
defined at the cell level. Hence, neighbours are also defined at the cell level.
The number of cells per transmitter is limited by the number of carriers available for a
network as defined in the global parameter dialog. Cells can be listed either by
transmitter, in a specific dialog, or in a table, as other radio data (sites and transmitters).
So, here again, the management of cells remains easy and comfortable.
II. Creating a CDMA/CDMA2000 cell

The cell concept is fully supported in U-Net. Cell is characterised by the
transmitter-carrier couple. Therefore, you can define several cells per transmitter (as
many cells as carriers associated to transmitter).
To define CDMA/CDMA2000 transmitter cells, proceed as follows:
1)
2)
Right click on the Transmitters folder to open the context menu.
3)
Left click the [Cells: Open] command from the open scrolling menu.
4)
Click on
to close the table.
The Cells table contains all the identifiers of a cell, its name, transmitter and carrier
which the cell refers to, cell PN Offset, PN Offset domain to which the allocated PN
Offset belongs, all the values defining transmitted signal level, pilot power,
synchronization power, paging power, maximum power, total power used,
information about the cell uplink load and an active set management parameter, AS
threshold.
Note:
z
Cells are automatically created and described in the table when you drag and drop a
station. On the other hand, you must define them manually after adding a new
transmitter (New... command when right clicking on the Transmitters folder) or
copying a list of transmitters in the Transmitters table.
Cell default name is: Transmitter name (carrier). If you change transmitter name or
carrier, U-Net does not update the cell name.
You cannot create two cells related to the same transmitter-carrier couple.
III. Managing CDMA/CDMA2000 cell properties

In CDMA/CDMA2000, cells are defined per transmitter. Nevertheless, their associated
properties can be reached by several ways. Like many other objects (Sites,
9-8

Chapter 9
Transmitters, Antennas, Predictions, Simulations, measurements, etc...) within U-Net,

cells can be managed either individually (per transmitter or in a single dialog) or
globally.
In U-Net, you may manage globally the cell properties your network by accessing the
cell table:
1)
2)
Right click on the Transmitters folder to open the context menu.
3)
4)
Click on
to close the table.

There are two ways to edit cell properties of each transmitter in the current network,
as Table 9-4 followed.
Table 9-4 Edit cell properties of each transmitter
Object
method

table

dialog
step
1)
Left click on the [Data] tab of the [Explorer]

window.
2)
Expand the transmitters folder by clicking

on the button in front of it.
3)
Right click on the transmitter which cell

properties you want to access.
4)
Choose the Properties option from the

context menu.
5)
Click the Cell tab from the open dialog,
1)
Select on the map the transmitter which cell

properties you want to access by left
clicking on the appropriate Tx symbol
(arrow).
2)
Choose the Properties option from the

context menu.
3)
Click the Cell tab from the open dialog,
1)
2)
Double click the record which property

dialog you want to open,
1)
2)
Right click on the record which property

dialog you want to open to get its
3)
Select the Record Properties command

from the open scrolling menu (or the

9-9

Object
Chapter 9
method
step
Record Properties command from the
Records menu),
Note:
z
Cell Properties dialog consists of three tabs: cell characteristics entered in the cells
table are grouped in the General and Transmission/Reception tabs, Intra and
Inter-technology neighbours may be allocated to the cell in the Neighbours tabs.
It is possible to define additional fields in the cell table by using the Fields command
in its related context menu (or from the Records menu). If it is the case, this new field
will then be available in the Other properties tab of any cell property dialog.
IV. Power parameters in CDMA/CDMA2000

Because powers can be defined differently within a same transmitter depending on
carriers, these are defined at the cell level in U-Net.
To define the different powers related to CDMA/CDMA2000 technologies, access
the cell properties (either from the table or from dialogs) and fill the following fields
(Transmission/Reception tab):
z
Max power
Pilot power
Synchronization power
Paging power
The total power used and UL load used in specific CDMA coverages are also defined in
the cell properties. The active set threshold (default value: 5dB) used for active set
determination has also to be set there.
V. Active set parameters in CDMA/CDMA2000

For a given terminal allowed to perform handover, the active set contains, the
transmitters with which it is connected. The main parameter to measure for transmitters
potentially in the active set is the pilot quality (Ec/Io). Once the best server in term of
pilot quality is defined, other transmitters are selected such as their pilot quality has to
be greater than a T-Drop value defined in the mobility (radio configuration) part.
To define the T-Drop, access the properties of each mobility type (either from the table
or from dialogs) and fill the field T-Drop.

9-10

Chapter 9
VI. Displaying CDMA/CDMA2000 cell properties on the map

Only site and transmitter objects are displayed on the map. Cells are not represented
but it is possible to colour transmitters depending on any of cell attributes. For example,
transmitters may be coloured depending on PN offsets assigned to their cells.
To colour transmitters depending on any cell attribute, proceed as follows :
1)
2)
3)
4)
Choose Discrete values or Values interval as display type and then, select in the
Field scrolling menu a cell attribute (they are the last ones in the scrolling menu).
5)
In addition, cell properties can be displayed as tips or labels on the map. To do this,
proceed as follows :
6)
7)
8)
9)
Select cell attributes to be displayed in the Label and Tips text scrolling menus
(they are the last ones in the scrolling menus).
Note:
z
transmitter has more than one cell, U-Net does not know the carrier to be
considered. In this case, no value is collected (#).
It is also possible to group transmitters by any cell attribute. As explained above, this
feature is fully available if there is one cell per transmitter only.
9.5 CDMA/CDMA2000 Multi-Service Traffic Data Management

9.5.1 CDMA/CDMA2000 Services
I. Creating CDMA/CDMA2000 services
CDMA/CDMA2000 allows the user to carry not only voice but also data for web, or
video conferencing for example. Services are divided into two categories (type field):
speech and data.
9-11

Chapter 9
U-Net provides a function to enable or disable soft handover for a given service.
To create a service, proceed as follows :
1)
2)
Expand the CDMA/CDMA2000 Parameters folder by left clicking on the

button.
3)
4)
5)
window.
6)
Click the available tabs to set the parameters of the created service.
7)
Validate by clicking on<OK >.
Note:
z
In the Eb/Nt tab window, (Eb/Nt)DL and (Eb/Nt)UL targets are the thresholds (in dB)
that must be achieved to provide users with the service. These parameters are
linked with radio configurations, and must be defined with some potentially different
multiples of nominal rate (defined in the terminal properties in RC) for the SCH rate.
Service nominal rates are defined within the services for UMTS. In
CDMA/CDMA2000 projects, nominal rates for FCH are defined within the terminal
(RC) properties and the SCH rates are given as multiple of this in the Eb/Nt tab.
Maximum and minimum allowed powers allowable for any type of service are
defined in General tab in UMTS whereas they are defined on FCH and SCH in the
Eb/Nt tab in CDMA/CDMA2000 , for each type of radio configuration linked with the
considered service (See Data service creation for CDMA/CDMA2000).
II. Data service creation CDMA/CDMA2000

The fundamental channel is a continuous nominal rate channel used for voice services.
For data services, the fundamental channel and an additional temporary channel, the
supplemental channel, are required. The supplemental channel is a short duration
channel with a rate equal to two, four, eight, or sixteen times the nominal data rate. The
rate of high speed data services is variable and depends on the amount of data to be
sent.
The user should enter 9.6kbps or 14.4kbps (according to the RC) in the nominal rate of
the service. Plus, the user needs to define the probability that an SCH will be required
or requested with a multiple of the nominal rate. The user will enter probabilities for
each possible multiple (2, 4, 8 and 16). In a real system, the sum of probabilities should
be less than 1 since the SCH is needed for only a fraction of the total connection time
9-12

Chapter 9
(the probability reflects the percentage of time that the service will need an SCH with
the given multiple of nominal rate).
III. Setting CDMA/CDMA2000 services parameters

Similar to the other U-Net object folders, CDMA/CDMA2000 services are easily
manageable. Creation steps and the display management are standard.
To manage the services parameters, proceed as follows Table 9-5.
Table 9-5 manage the services parameters
Method
Method 1
Method 2
step
1)
2)
Expand the CDMA/CDMA2000 Parameters folder by left

3)
4)
Right click on the service of which you want to manage the

5)
6)

current service.
7)
1)

2)
3)
Double click on the service of which you want to manage the

properties.
4)

current service.
5)
button.
button.
Note:
dialog window of any service by simply double clicking on any cell in the associated line,
or on the associated arrow at left.
The coding factors, which penalize UL and DL service rates, may be supplied in two
ways. For each service, you may :
z
Either enter high UL and DL coding factors and then, set a low enough UL and DL
Eb/Nt threshold so that the advantage of high coding can be simulated (higher

9-13

Chapter 9
error correction rate means smaller bit error rate and thus a smaller required
Eb/Nt).
z
Or enter low UL and DL coding factors value and take into account the coding to
define the required UL and DL Eb/Nt values, i.e. a high enough Eb/Nt threshold to
simulate the disadvantage of little coding.
IV. Managing globally CDMA/CDMA2000 services

In U-Net, CDMA/CDMA2000 objects are organized in folders. For this reason, U-Net
allows the user to simultaneously display all topics of one type (services, mobility,
terminal, user profiles, and environment) in a table window.
To open the services table, proceed as follows.
Method 1
1)
2)

button.
3)
4)
5)
Method 2
1)
2)

button.
3)
Double click on the Services folder.
4)
The services table works exactly like the other tables. Its cells are editable, sorting and
filtering tools, and copy/paste functions are available.
Note:
z

the context menu associated with the Services folder. From the properties dialog
box, you may also manage the contents of the services table. Use the What's this

9-14

Chapter 9
9.5.2 CDMA/CDMA2000 Radio Configurations

I. Creating a CDMA/CDMA2000 radio configuration
In CDMA/CDMA2000, Ec/I0 requirements and Eb/Nt targets per service and per link
(up and down) knowledge, contrary to UMTS, are not dependant on mobility. In order to
keep the UMTS structure, mobility type and terminals folders are used but deal with
only one concept : Radio Configurations. Due to the fact that mobility type and
terminals folders deal with same topics, consistency has to be respected by setting the
same RC in both folders.
To create a CDMA/CDMA2000 Radio Configuration, proceed as follows :
1)
2)

button.
3)
Right click on the Mobility type folder to open the associated context menu.
4)
5)
window.
6)
Set the parameters of the currently created mobility.
7)
Validate the RC mobility folder part by clicking on OK.
8)
9)
10) Use the What's this help to get description about the fields available in the open
window.
11) Set the parameters of the currently created terminal.
12) Validate the RC terminal folder part by clicking on <OK>.
Parameters which are located into the mobility type folder are pilot quality (Ec/Io)
thresholds (in dB). For a given mobility type :
z
Ec/Io (Tad in CDMA/CDMA2000 projects) threshold is the minimum Ec/Io required

from a transmitter to enter the active set. In U-Net, this value is verified for the best
server.
T-Drop is the minimum Ec/Io required from a transmitter not to be ejected from the
active set. This data is important for CDMA/CDMA2000 . In U-Net, this value is
verified for transmitters other than the best server.
Terminals summarise the different radio configurations that can be used in the network.
Each radio configuration is described by a minimum and maximum transmission power
(dynamic range for downlink power control), its antenna gain and reception losses, and
an internal thermal noise (calculated from the noise figure). Active set size is the
maximum allowable number of transmitters in connection with the terminal
(macro-diversity). This parameter is settable for FCH as well as for SCH. The maximum
9-15

Chapter 9
active set size can reach 6. The number of fingers represents the maximum number of
active set links the terminal (rake) can combine. This criterion is considered in
simulations, point analysis and coverage prediction. The number of fingers is the same
for FCH and SCH. You can also define UL and DL nominal rates i.e. the fundamental
channel (FCH) rate. Finally, you may enter a percentage of the mobile total power
dedicated to the UL pilot channel.
The UL pilot power is than taken into account to calculate the total UL interference.
II. CDMA/CDMA2000 active set conditions

The transmitters taking part in the active set have to check the following conditions:
z
They must be using the same carrier (at the cell level).
The pilot quality (Ec/Io) from the best server has to exceed the Ec/Io threshold
(defined for each mobility type - radio configuration).
The pilot quality from other transmitters has to be greater than the T-Drop value
(defined for each mobility type - radio configuration).
Other cells have to belong to the neighbour list of the best server if you have
selected the restricted to neighbours option (in the definition of the Site
equipment).
III. Setting a CDMA/CDMA2000 radio configuration

Like for the other U-Net object folders, CDMA/CDMA2000 mobility types and terminals
(composing Radio Configuration) are easily manageable. Creation steps and the
display management are standard.
To manage the Radio Configuration parameters dealing with Ec/I0 requirements,
proceed as follows Table 9-6.
Table 9-6 manage the Radio Configuration parameters
Method
Method 1
Method 2
step
1)
2)

3)

button.
4)
Right click on the mobility of which you want to manage the

5)
6)
7)
1)
2)

9-16

Chapter 9
Method
step
clicking on the
button.
3)

button.
4)
Double click on the mobility of which you want to manage

the properties.
5)
6)
To manage the Radio Configuration parameters dealing with terminals, proceed as

follows in Table 9-7.
Table 9-7 manage the Radio Configuration parameters
Method
Method 1
Method 2
step
1)
2)

3)
4)
Right click on the terminal of which you want to manage the

5)
6)
7)
1)
2)

3)
4)
Double click on the terminal of which you want to manage

the properties.
5)
6)
Validate by clicking on <OK.>
button.
button.
IV. Managing globally CDMA/CDMA2000 radio configurations

Because Radio Configurations are made of mobility type and terminal folders, Radio
Configuration parameters are spread within the two related tables.

9-17

Chapter 9
To open the Radio Configuration table dealing with Ec/I0 requirements, proceed as
follows Table 9-8.
Table 9-8 open the Radio Configuration table
Method
Method 1
Method 2
step
1)
2)

3)
Right click on the Mobility types folder to open the

4)
1)
2)

3)
Double click on the Mobility types folder.
To open the Radio Configuration table dealing with terminals, proceed as follows
Table 9-9.
Table 9-9 open the Radio Configuration table
Method
Method 1
Method 2
step
1)
2)

3)
Right click on the Terminals folder to open the associated

context menu.
4)
5)
1)
2)

3)
Double click on the Terminals folder.
4)
The mobility types and terminal tables work exactly like the other tables. Their cells
are editable, sorting and filtering tools, and copy/paste functions are available.

9-18

Chapter 9
Note:
z

the context menu associated with the mobility types or terminals folder. From the
properties dialog box, you may also manage the contents of the mobility types or
terminals table. Use the What's this help to get description about the fields available
in the different windows.
When the Mobility type or terminals table are displayed and active, it is possible to
open the property dialog window of any mobility or terminal by simply double
clicking on any cell in the associated line, or on the associated arrow at left.
9.5.3 CDMA/CDMA2000 User Profiles

I. Creating a CDMA/CDMA2000 user profile
In CDMA/CDMA2000, user profiles describe the behaviour of different user categories.
Each user profile is assigned a service and its associated usage parameters such as
used terminal, session frequency (calls/hour) and duration.
Parameters for speech services are:
z
Parameters for data services are:

z
Used Radio Configuration
Those parameters are used in simulation to determine the probability (activity status)
that a user is transmitting or receiving communication for the given service and terminal
when the snapshot is taken.
Example:
z
For speech services, entering a one-hour call during 1000s corresponds to define 2
calls per hour during 500s...the activity probabilities will be the same in both cases.
In order for all the services defined for a user profile to be taken into account during
traffic scenario elaboration, the sum of activity probabilities must be lower than 1
You can model temporal variations of user behaviour by creating different profiles
for different hours (busy hour, ...).

9-19

Chapter 9
To create a CDMA/CDMA2000 user profile, proceed as follows :

1)
2)

button.
3)
Right click on the User profiles folder to open the associated context menu.
4)
5)
Set the parameters of the currently created user profile.
6)
II. Adjusting CDMA/CDMA2000 user profile properties

Like for the other U-Net object folders, CDMA/CDMA2000 user profiles are easily
To manage the user profile parameters, proceed as follows Table 9-10.
Table 9-10 manage the user profile parameters
Method
Method 1
Method 2
step
1)
2)

3)

button.
4)
Right click on the user profile of which you want to manage

the properties to open the associated context menu.
5)
6)
7)
1)
2)

3)

button.
4)
Double click on the user profile of which you want to manage

the properties.
5)
6)
III. Managing globally CDMA/CDMA2000 user profiles

In U-Net,CDMA/CDMA2000 objects are organized in folders. For this reason, U-Net
9-20

Chapter 9
To open the user profiles table, proceed as follows Table 9-11 :

Table 9-11 open the user profiles table
Method
Method 1
Method 2
step
1)
2)

3)
Right click on the User profiles folder to open the associated

context menu.
4)
1)
2)

3)
Double click on the User profiles folder.
The user profiles table works exactly like the other tables. Its cells are editable, sorting
Note:
z

the context menu associated with the User profiles folder. From the properties
dialog box, you may also manage the contents of the user profiles table. Use the
When the User profiles table is displayed and active, it is possible to open the
property dialog window of any user type by simply double clicking on any cell in the
9.5.4 CDMA/CDMA2000 Environments

I. Creating a type of CDMA/CDMA2000 environment
Environment classes may be used to describe subscriber spatial distribution on a map;
they are the available classes for traffic cartography design. Environment class
represents an economic and social concept, which defines the characteristics of user
profiles. Each environment class contains a set of three data (user profile, mobility,
density) where density is a number of subscribers with the same profile per km, and
where the mobility corresponds to the radio configuration defined in the user profile
folder. There is no restriction on the number of data sets constituting an environment.
9-21

Chapter 9
Note:
To get an appropriate user distribution, you may assign weights per clutter classes, for
each environment class.
To create a CDMA/CDMA2000 environment type, proceed as follows:

1)
2)

button.
3)
Right click on the Environments folder to open the associated context menu.
4)
5)
window.
6)
Click the available tabs to set the parameters of the currently created
environment.
7)
Note:
z
Particular case: When no multi-service geo-marketing data are available, you may
supply U-Net with usual traffic data like user densities per service (for example,
values coming from adapted GSM Erlang maps). In this case, user profile definition
and calculation of deduced activity probability are not necessary to create traffic
scenario ; traffic distribution will only depend on densities per service.
Therefore, the activity probabilities calculated during simulation will be equal to 1

and density values defined in Environments will be user densities (no more
subscriber densities). Elaborated traffic scenario will fully respect the user profile
proportion (i.e. service) given in environments. You will fully master the number of
users in simulation as well as the service proportion which will drive random trials.
Moreover, each user will be connected.
This method is not the usual nominal working mode for U-Net.
II. Setting CDMA/CDMA2000 environment parameters

Like for the other U-Net object folders, CDMA/CDMA2000 environments are easily
To manage the environments parameters, proceed as follows Table 9-12.

9-22

Chapter 9
Table 9-12 manage the environments parameters

Method
Method 1
Method 2
step
1)
2)

3)

button.
4)
Right click on the environment type of which you want to

manage the properties to open the associated context
menu.
5)
6)

7)
1)
2)

3)

button.
4)
Double click on the environment type of which you want to

manage the properties.
5)

6)
Note:
To get an appropriate user distribution, you may assign weights to clutter classes, for
each environment class in the Clutter weighting tab.
III. Managing globally CDMA/CDMA2000 environment types

terminal, user profile, and environment) in a table window.
To open the environment types table, proceed as follows Table 9-13.
Table 9-13 open the environment types table
Method
Method 1
step
1)
2)

9-23

Chapter 9
Method
step
clicking on the
3)
Method 2
button.
Right click on the Environments folder to open the

4)
5)
1)
2)

3)
Double click on the Environments folder.
4)
The environment types table works exactly like the other tables. Its cells are editable,
Note:
z

the context menu associated with the Environments folder. From the properties
dialog box, you may also manage the contents of the environment types table. Use
the What's this help to get description about the fields available in the different
windows.
IV. Displaying statistics per CDMA/CDMA2000 environment type

U-Net allows the user to perform a statistic study on each environment class.
These statistics provide the number of mobiles to be created in the traffic scenario for
the given environment (based on a raster traffic map, respecting the layer order). This
number is given displayed per clutter class.
To display a statistic study on any environment type, proceed as follows :
1)
2)

button.
3)

9-24
button.

4)
Chapter 9
Right click on the environment type you want to display a statistical study to
open the associated context menu.
5)
Left click in the scrolling menu on Statistics....
Note:
The statistic study is limited to the focus zone, only the clutter and environment areas
inside the focus zone are taken into account in calculations.
V. Subscriber clutter weighting in CDMA/CDMA2000 environment

Enter a weight for each clutter class in order to get an appropriate user distribution
The following formula is used for calculations:
Nk = Nclass
w k Sk
w j Sj
j
where :
Nk
Number of users in the k clutter
Nclass
Number of users in an environment class
wk
k clutter weight at fixed surface
Sk
k clutter surface (stated in km)
This weighting method is used when displaying statistics per CDMA/CDMA2000

environment type.
9.6 CDMA/CDMA2000 Multi-Service Traffic Cartography

U-Net provides 3 types of traffic maps for CDMA/CDMA2000 projects :
z
Traffic raster maps based on environments: each pixel of the map is assigned an
environment class.
Traffic vector maps based on user profiles: each polygon or line contains a density
of subscribers with given user profile and mobility type.
Traffic maps per transmitter and per service: live traffic is spread over a best pilot
coverage plot. To each computed area is assigned either rates or amount of users
per service (uplink or downlink).
9-25

z
Chapter 9
Whatever the type of map is, this one can be either created or modified manually,
imported from an external file and exported to an external file.
9.6.1 CDMA/CDMA2000 Environment Traffic Maps

I. Creating a CDMA/CDMA2000 environment traffic map
environment polygons or by directly importing a raster map in your project as an
environment traffic map.
To create a CDMA/CDMA2000 environment traffic map by drawing, proceed as
follows :
1)
2)
3)
4)
Choose the map based on environments (raster) option in the Create a traffic
map open window.
button to validate.
5)
Press the
6)
Use the cartography editor (selecting one of the available environment classes as
defined in the environment folder) to draw environment polygons.
7)
Click the
Note:
z
You can only choose among existing environment classes in the cartography editor.
To make available additional classes, do it in the CDMA/CDMA2000 parameters.
II. Importing a CDMA/CDMA2000 environment traffic map

environment polygons or by directly importing a raster map (with the appropriate format)
in your project as an environment traffic map.
To import a CDMA/CDMA2000 environment traffic map from an external file, proceed
as follows :
1)
2)
9-26

Chapter 9
3)
4)
Choose the map based on environments (raster) option in the Create a traffic
map open window.
button to validate.
5)
Press the
6)
7)
8)
Press the
9)
button to validate.
button to validate.
In the name column, left click cells in order to replace class (codes or clutter)
names by existing environment classes.
10) Press <OK> or <Apply> to validate.
Note:
z
(selection of the environment traffic type in the appropriate scrolling menu).
Clutter files can be imported as traffic files.
In order to manage traffic on the entire map, this operation must be carried out for all
classes.
The description table can be fully copied and pasted (using <Curl> and <Curl>) in a
new U-Net project after importing the raster file. To select globally the environment
class table, just left click on the top left angle of the environment table.
III. Managing CDMA/CDMA2000 environment traffic maps

On an existing environment traffic map, you can access properties and it is possible to
modify the class association and its display settings.
To access the properties of an existing environment traffic map, proceed as follows :
1)
2)
3)
Right click on the related environment map folder to open the associated
context menu.
4)
5)
6)
Click the display tab to set the transparency level, the visibility scale and to
add the map information to the legend.
7)

9-27

Chapter 9
It is also possible to access the properties of a single file composing the resulting map
(properties command in the related context menu) to embed it into the atl project or to
check the map geocoding.
Note:
Absolute and relative statistics can be provided for this type of map.
IV. Exporting a CDMA/CDMA2000 environment traffic map

Like the other CDMA/CDMA2000 traffic map types (user profile or live traffic), it is
possible to export a environment traffic map in either a 8 bits/pixel raster tiff, bil or bmp
format. It is possible to export a part or the complete environment traffic map.
To export a part or the complete environment traffic map in CDMA/CDMA2000 projects,
1)
2)
3)
Right click on the Environment map folder in order to get the related context menu.
4)
Left click on the Save as... option from the open scrolling menu.
5)
Define the format. the directory path and the name to give to the file to be
exported.
6)
Click the Save button when this is made.
7)
In the Export dialog box. select one of the options and define the resolution (in
metres) of file , which described in Table 9-14.
8)
Click <OK>to validate.
Table 9-14 Export dialog box, select one of the options

options
explain
whole covered
region
allows you to save the whole traffic map in another file. As soon
as the file is saved, the properties (name,...) of the traffic maps
listed in the Environment Traffic subfolder are updated.
only pending
changes
allows save in the file the created traffic polygonal area. As soon as the
modifications are saved, an additional traffic item is created and listed
in the Environment Traffic subfolder.
computation
zone
allows you to save only traffic map region inside the computation zone
in another file. As soon as the file is saved, an additional traffic object is
created and listed in the Environment Traffic subfolder. To enable this
option, you must have drawn a computation zone beforehand.
resolution
it is defined for raster traffic from the following criteria :

z
If one traffic object is clipped, the displayed resolution will be

9-28

Chapter 9
options
explain
the object resolution.
z
If several objects are modified, the suggested resolution will

be the smallest resolution of the altered items.
If there is no initial traffic item, the resolution will equal the
resolution of DTM object which the modifications are made
on or the smallest resolution of the merged DTM objects if
the modifications are performed on several DTM objects.
If you draw your own traffic data without initial DTM, clutter
or traffic object, a 100 m default resolution will be suggested.
The resolution value must be an integer.
The minimum resolution is set to 1 metre.
Note:
When you save files using BIL and TIF formats, .hdr and .tfw files are automatically
created in the
same folder. The .hdr and .tfw files are respectively associated with .bil and .tif files;
they contain
geocoding information and resolution.
V. Displaying statistics on CDMA/CDMA2000 environment traffic maps

It is possible to display statistics on an existing CDMA/CDMA2000 environment traffic
map. Statistics are given globally and relatively as functions of environment traffic
classes. Traffic density statistics indicates the proportion of each traffic class. Traffic
statistics refer to the focus zone is existing.
To display traffic statistics of the map in CDMA/CDMA2000 projects, proceed as
follows :
1)
2)
3)
Right click on the Environment Traffic folder to open the associated context
menu.
4)
Choose the Statistics option from the scrolling menu.
5)
The surface (Si in km) of imported or edited traffic class (i) included in the
focus (if existing) zone and its percentage (% of i) are specified:
% of i =
Si
100
Sk
k

9-29

Chapter 9
Note:
z
If no focus zone is defined, statistics are given over the computation zone.
Current statistics are printable by clicking the
button.
9.6.2 CDMA/CDMA2000 User Profile Traffic Maps

I. Creating a CDMA/CDMA2000 user profile traffic map
files (MapInfo(MIF,MID), Arcview (SHP), Autocad(DXF)) and using them as traffic maps
or creating vectors with the vector editor and assign them some traffic information.
To create a CDMA/CDMA2000 user profile traffic map by drawing, proceed as follows :
1)
2)
3)
4)
open window.
button to validate.
5)
Press the
6)
Potentially define traffic information (user profile. mobility type. density) in the
Table tab. assign them to U-Net internal traffic fields in the Traffic tab. and use the
vector editor to draw environment polygons. lines or points.
7)
Click the
Note:
z
Like other vector layers, it is easily possible to save the generated traffic map.
Points can be seen as traffic hotspots

9-30

Chapter 9
II. Importing a CDMA/CDMA2000 user profile traffic map

files (MapInfo(MIF,MID), Arcview (SHP), Autocad(DXF)) and using them as traffic maps
or creating vectors with the vector editor and assign them some traffic information.
To import a CDMA/CDMA2000 user profile traffic map by drawing, proceed as follows :
1)
2)
3)
4)
Choose the map based on user profiles (vector) option in the Create a traffic
map open window.
button to validate.
5)
Press the
6)
7)
8)
Press the
9)
A dialog box is displayed in order to configure traffic vector data.
button to validate.
button to validate.
10) Click the Traffic tab.
Note:
In the Traffic fields part, specify the user profiles to be considered on the traffic vector
map, their mobility types (km/h) and their densities (number of users/km2 for polygons
and number of user/km for lines). You can decide the type of information that you want
to use to define the traffic characteristics, either a field described in the file (by field
option in the Defined column) or a value directly user-definable in U-Net (by value
option in the Defined column).
The first method can be used only if the file you are importing contains attributes
providing information about the user profile, mobility or density. In this case, select
in the Choice column a suitable field for each data (user profile, mobility and
density); U-Net lists all the attributes described in the file. The attributes of the
source file cannot be modified. Using this method, each traffic polygon or linear is
assigned specific characteristics (user profile, mobility or density).

9-31

Chapter 9
Note:
Take care to define in U-Net user profiles and mobility types described in traffic file with
exact spelling.
The second way is useful when traffic files contain no attribute. Therefore, you
may assign manually user profiles, mobility types and densities created in U-Net.
Select in the Choice column user profile and mobility listed in UMTS Parameters
folder and specify manually a global density for all the polygons. Beforehand, just
make sure to define in UMTS Parameters the internal data like user profile and
mobility you want to allocate. Here, all the polygons are described by global
characteristics (user profile, mobility or density).
11) In the Clutter weighting part, assign a weight to each clutter class. Thus, U-Net
allows you to spread traffic inside the polygons according to the clutter weighting
defined for the whole subfolder. The spreading operation (using a raster step) will
be carried out during the simulation process.
12) Then, press OK to validate the properties setting.
Note:
z
(selection of the Traffic type in the appropriate scrolling menu).
During the import proceed , if the imported user profiles or mobility types are not
currently part of the existing user profiles or mobility types, U-Net warns you about
the fact that these may not be correctly taken into account as traffic data.
Path and description are stored in the external user configuration file.
III. Managing CDMA/CDMA2000 user profile traffic maps

To access the properties of an existing user profile traffic map, proceed as follows :
1)
2)
3)
Right click on the related user profile traffic map folder to open the associated
context menu.
4)
5)
Click on the General tab to either embed the file into the atl project, to relocate
the map by the definition of the appropriate coordinate system, by imposing
sorts on the vector organisation or filters on the vector display.
6)

9-32

7)
Chapter 9
Click on the Traffic tab to re-associate vector fields and U-Net internal traffic
fields, and to impose subscriber clutter weighting using this map for the subscriber
distribution during the monte-carlo simulation.
8)
9)
Press OK or Apply to validate.
IV. Examples of CDMA/CDMA2000 user profile traffic data

Structure of two vector traffic files is described hereafter. Niceregion.mif consists of
eleven polygons representing the Nice region. Each polygon is characterised by a user
profile, the services offered to subscribers, their mobility types and densities. Densities
are stated in number of subscribers per km2. Highway.mif represents a highway (linear)
where density corresponds to a number of subscribers per km.
Niceregion.mif is shown in Table 9-15.
Table 9-15 Niceregion.mif FILE
Name
Userprofile
Services used
MobilityA
DensityA
MobilityB
DensityB
Hinterland
rural user
Speech
90 km/h
pedestrian
Village
rural user
Speech
50 km/h
10
pedestrian
Corniche
rural user
Speech
50 km/h
10
pedestrian
20
Rural
rural user
Speech
90 km/h
pedestrian
Villages
rural user
Speech
50 km/h
10
pedestrian
10
Nice
urban user
Speech, Web,
Simple
messaging,
Video
conferencing
pedestrian
700
50 km/h
100
Nice airport
urban user
Speech, Web,
Simple
messaging,
Video
conferencing
pedestrian
700
50 km/h
100
Nice
surroundings
rural user
Speech
50 km/h
100
90 km/h
100
Rural
rural user
Speech
90 km/h
pedestrian
Villages
rural user
Speech
50 km/h
10
pedestrian
Nice center
urban user
Speech, Web,
Simple
messaging,
Video
conferencing
pedestrian
4000
pedestrian

9-33

Chapter 9
Using the user profile traffic import proceed , it is possible to associate (Traffic tab of the
properties dialog) :
To user profile : either a global value (by value) for all the polygons or the
Userprofile field of the vector (by field), with a different definition for each polygon.
To mobility : either a global value (by value) for all the polygons or the MobilityA
(resp. MobilityB) field of the vector (by field), with a different definition for each
polygon.
To density : either a global value (by value) for all the polygons or the DensityA
(resp. Density B) field of the vector (by field), with a different definition for each
polygon.
Highway.mif is shown in Table 9-16.
Table 9-16 Highway.mif FILE
ID
highway
User_profile
Service used
Density
driver
Speech
400
Mobility
120 km/h
Using the user profile traffic import proceed , it is possible to associate (Traffic tab of the
properties dialog) :
z
To user profile : either a global value (by value) for all the polygons or the
User_profile field of the vector (by field), with a different definition for each
polygon.
To mobility : either a global value (by value) for all the polygons or the Mobility field
of the vector (by field), with a different definition for each polygon.
To density : either a global value (by value) for all the polygons or the Density field
of the vector (by field), with a different definition for each polygon.
V. Exporting a CDMA/CDMA2000 user profile traffic map

Like the other CDMA/CDMA2000 traffic map types (environment or live traffic), it is
possible to export user profile traffic maps.
To export a CDMA/CDMA2000 user profile traffic map, proceed as follows :
1)
2)
3)
Right click on the user profile traffic map folder to open the associated context
button.
menu.
4)
5)
Left click on the [Save as... ]option from the open scrolling menu.
Define the format. the directory path and the name to give to the file to be exported.
Possible formats are Arcview (.shp). MapInfo (.mif) and the U-Net internal format
(.agd).
6)
Click the <Save> button to complete the export proceed .

9-34

Chapter 9
9.6.3 CDMA/CDMA2000 Live Traffic Maps

I. Creating a CDMA/CDMA2000 live traffic map
This kind of traffic map requires a coverage by transmitter prediction study. Then,
U-Net expects rate values (kbits/s) or number of active users for each service and each
transmitter.
Note:
It is possible to define either one map per service or one map with all services.
Then, the traffic cartography is built without connection with the initial coverage
prediction. This map consists of polygons provided with the same features as the user
profile traffic polygons.
The definition of CDMA/CDMA2000 live traffic maps can be made either from a direct
importing a file.
To create a CDMA/CDMA2000 live traffic map, proceed as follows:
1)
2)
3)
4)
Choose the map based on transmitter and service (Throughput or Number of

users) option in the Create a traffic map open window.
button to validate.
5)
Press the
6)
Select the prediction study to be considered for traffic distribution. Only coverage
per transmitter studies can be used. A table where you can indicate the live traffic
spread over the transmitter service areas is available. It consists of a column
dedicated to transmitters and several columns for the different services previously
defined in the UMTS parameters folder. In the TX_ID column. select each line.
click on the arrow and choose a transmitter in the list. You may also use the copy
and paste commands (respectively Ctrl+C and Ctrl+V) from an Excel file already
containing the expected columns.
7)
Enter rate values (kbits/s) (or Number of active users) on uplink and on downlink
relating to different services for each transmitter.
8)
Press <OK> to continue the map creation.
9)
U-Net displays the property dialog of the map. Click the Traffic tab of the opened
9-35

Chapter 9
distribution.
U-Net creates an object called Traffic map per transmitter in the Traffic folder of the
[Geo] tab.
Note:
z
The map only contains the service areas of transmitters listed in the table. Then, the
traffic map shape is fixed and cannot be modified; it is not possible to add new
transmitters.
On the other hand, it is possible to modify traffic values (throughputs or number of

users) afterwards in the Table related to the map.
In CDMA/CDMA2000 projects, it is necessary to define one map per radio

configuration. Thus, enter a percentage value different from 0 for a given radio
configuration (choose the same radio configuration, for terminal and mobility), and 0
for the other ones.
II. Importing a CDMA/CDMA2000 live traffic map

The definition of CDMA/CDMA2000 live traffic maps can be made either from a direct
importing a file.
You may import files with AGD format. This is the U-Net geographic data internal format.
This kind of file must be created from U-Net (export of a coverage by transmitter study
in the AGD format).
To import a CDMA/CDMA2000 live traffic map by drawing, proceed as follows:
1)
2)
3)
4)
Choose the map based on transmitter and service (Throughput or number of users
per transmitter) option in the Create a traffic map open window.
button to validate.
5)
Press the
6)

9-36
button to validate.

Chapter 9
7)
8)
Select the option embed in the document to include the file in the .atl document.
When this option is not selected. U-Net just memorizes the file directory path.
9)
In the coordinate systems part. U-Net summarises the projection coordinate

system you have defined in the .atl project. In the box just below. specify the
coordinate system of the file you are importing (click on Change... to choose
another coordinate system).
button to validate.
10) Press the
11) U-Net displays the property dialog of the map. Click the Traffic tab of the opened
distribution.
Note:
It is also possible to import a traffic map per transmitter using the standard import
proceed (Import command in the File menu). In this case, you must specify in the
import dialog that you want to import the file in the Traffic folder.
III. Managing CDMA/CDMA2000 live traffic maps

Management features of vector maps are available for traffic maps per transmitter:
standard graphical features are available in the Display tab of the map property dialog
and each map has a corresponding table. This table contains the transmitters used to
build the map and traffic information for each of them.
To access the properties of an existing live traffic map, proceed as follows :
1)
2)
3)
Right click on the related live traffic map folder to open the associated context
menu.
4)
5)
Click on the General tab to either embed the file into the atl project. to relocate the
map by the definition of the appropriate coordinate system. by imposing sorts on
the vector organisation or filters on the vector display.
6)

9-37

7)
Chapter 9
Click on the Traffic tab to re-define terminal and mobility ratios and to impose
subscriber clutter weighting using this map for the subscriber distribution during
the monte-carlo simulation.
8)
9)
IV. Exporting a CDMA/CDMA2000 live traffic map

Like the other CDMA/CDMA2000 traffic map types (environment or user profile), it is
possible to export live traffic maps.
To export a CDMA/CDMA2000 live traffic map, proceed as follows :
1)
2)
3)
Right click on the live traffic map folder to open the associated context menu.
4)
Left click on the [Save as... ]option from the open scrolling menu.
5)
Define the format, the directory path and the name to give to the file to be exported.
button.
Possible format is the U-Net internal format (.agd).

6)
Click the <Save> button to complete the export proceed .
9.7 CDMA/CDMA2000 Simulations

9.7.1 Overview
Power control simulation is a necessary step to obtain instantaneous network noise
level and perform service area prediction based on it. Furthermore, it is a first, quick
and easy analysis tool to get information about network dimensioning. Traffic data is a
critical parameter for CDMA studies. Indeed, power control simulation is performed
from user distributions, which are obtained by random trials driven by traffic data. Its
significance rests on traffic data relevance.
z
U-Net provides a random user distribution generation, based on a Monte-Carlo

algorithm complying with traffic description and cartography.
Once realistic user distributions are available, power control simulation is

automatically achieved to determine network parameters (such as cells and
terminal - radio configuration - powers) and estimate interference level.
U-Net provides either actual network audit (taking into account your network
constraints) or new dimensioning information about how to handle available traffic.
On the same traffic snapshot, you can check how your network works and can be
improved.
U-Net offers a wide range of tuneable parameters involved in CDMA/CDMA2000

simulations. Even from existing simulations, it is possible to modify these
parameters with the replay simulations features offered by U-Net. You may also
9-38

Chapter 9
add simulations to a group of existing simulations. Averaging a group of

simulations is also possible. Once achieved, simulations are available for specific
CDMA/CDMA2000 coverage predictions.
Indeed, for CDMA/CDMA2000 projects, U-Net provides four different groups of
studies, listed in a natural planning order, from the indispensable pilot study to the
study of downlink total noise, with respect to the propagation model as defined:
z
Pilot-oriented studies to determine pilot coverage by transmitter, the pilot

coverage by signal level, overlapping area (like standard coverage studies), pilot
quality (Ec/Io) and pilot pollution.
Service-oriented studies to determine service availability in uplink and

downlink and effective service areas.
handover status study to analyse macro-diversity performance.
A specific 1xEV-DO coverage is also available for CDMA/CDMA2000 projects, but this
is not relative to any simulation.
z
With the point analysis tool, it is also possible to build a CDMA scenario defining
a probe mobile with a type of terminal, SCH multiple rate and service and
predict, on each point of the current map, its results. Except pilot coverage,
coverage by signal level and overlapping studies, which are similar to classical
coverage studies, all other studies are specific to CDMA/CDMA2000 network
planning and closely related to a particular simulation.
U-Net provides powerful simulation outputs. Firstly, you can display requirements,
results and initial conditions. Then, you may choose to display the simulation
results either per site, per transmitter, or per mobile for the currently studied
simulation. Finally, you may optionally display the computed shadowing errors.
The results can also be displayed on the map as function of any topics dealt with
the CDMA/CDMA2000 simulations (service, terminal, user, mobility, activity,
factors, connection and HO status, best server, active set parameters, geographic
coordinates, rates, carriers, powers, noise rise, path loss).
9.7.2 Managing CDMA/CDMA2000 Simulations

I. Creating CDMA/CDMA2000 power control simulations
CDMA/CDMA2000 networks automatically regulate themselves by using traffic driven
uplink and downlink power control in order to minimize interference and maximize
capacity.
U-Net simulates this network regulation mechanism with an iterative algorithm and
calculates, for each user distribution, network parameters such as base station power,
mobile terminal (RC) power, active set and handover status for each terminal.
9-39

Chapter 9
To create a (group of) CDMA/CDMA2000 power control simulation(s), proceed as

follows :
1)
2)
Right click on the CDMA/CDMA2000 simulations folder to open the associated

context menu.
3)
4)
The creation of simulations dialog window opens.
5)
window.
6)
Set the parameters for the current simulation study(ies).
7)
Note:
z
If you check the execute later box, computations will be started when using the
Calculate command (F7 shortcut or
button).
When starting computations, a group of simulations (with the input number of

simulations) is automatically created under the CDMA/CDMA2000 simulation
folder.
Once achieved, simulations are available for specific CDMA/CDMA2000 coverage

II. Managing CDMA/CDMA2000 simulation properties

Like many other objects (Sites, Transmitters, Cells, Antennas, Predictions,
measurements, etc...) within U-Net, simulations can be managed either individually or
globally. Nevertheless, due to the fact that some of them have already been started,
you can only display their input parameters. Regarding the global properties of
simulations, they are related to the way simulation results are displayed on the map.
In U-Net, you may manage globally the display properties of the existing simulations.
To do so, proceed as follows :
1)
2)
Right click on the CDMA/CDMA2000 Simulations folder to open the context menu.
3)
Left click the Properties command from the open scrolling menu.

9-40

Chapter 9
Note:
To manage the display of simulation results, the U-Net generic dialog window is used.
So, it is possible to display simulation results related to, for example, their connection
status, handover status, any CDMA/CDMA2000 parameter, pilot quality, etc...
Furthermore, all simulation folders are then organised in threshold items that you can
display or not in the workspace.

If computations have already been started, the properties you can display on groups of
simulations are related to the input parameters.
To open the properties related to a group of CDMA/CDMA2000 simulations, proceed as
follows :
1)
2)
Expand the CDMA/CDMA2000 Simulations folder by clicking on the
button in
front of it.
3)
Right click on the group of CDMA/CDMA2000 Simulations you want to manage.
4)
Note:
z
If computations have not been started (using the execute later command), you can
access to the group properties in order to modify them for coming computations.
You can access to the Properties of any single simulation. The open dialog is
related to simulations requirements and results, specific results per site, per mobile,
per cell and simulation initial conditions.
III. CDMA/CDMA2000 power control simulation inputs

Before running simulations, you must have a radio network with a satisfying pilot
coverage. Then, it is necessary to define traffic description and cartography.
In U-Net, the dialog allowing you to create simulations is made of three tabs : General,
Traffic and Advanced described below.
General tab
9-41

Chapter 9
In this tab, you can enter a name to the group of simulations that U-Net is going to
compute. Then, you may decide the number of scenarios on which you want to
simulate power control. It is possible to create several simulations at the same time or
just one by one if you prefer. Selecting the Detailed results option enables you to get
additional simulation outputs relating to mobiles (results available in the Mobiles and
Mobiles (Shadowing values) tabs of the simulation Properties window). Finally, the
Execute later option can be used if you want to predefine simulation calculation settings
and start the computation subsequently. In case the option is selected, simulation
calculation is not carried out when closing the dialog; simulation will be worked out
when clicking on the Calculate command (F7 shortcut or
button).
Note:
The Execute later feature enables you to automatically calculate CDMA/CDMA2000
coverage studies after simulations without intermediary step.
In the Cell load constraint part, you must select constraints you want U-Net to respect
during power control simulation. If you wish to check your network, just select the
constraints about maximum cell power, maximum number of channel elements,
maximum uplink cell load (the default value is set to 75%) and Walsh codes availability.
The simulation proceeds without exceeding these limits. Mobiles with the lowest
service priority (user-defined in each service properties dialog window) are first
rejected. In order for the simulation to proceed freely, uncheck all the calculation
options.
Traffic tab
The global scaling factor for traffic option enables you to increase subscriber density
without changing traffic parameters or cartography. For example, setting the global
scaling factor for traffic to 2 means doubling the initial number of subscribers (for traffic
raster or user profile traffic maps) or the rates/users (for traffic maps per transmitter and
per service).
Then, you can perform simulations using several traffic cartographies. To do this, select
them in the Traffic part. In this case, U-Net takes into account the traffic information
provided in all the selected maps. This feature must be carefully used to avoid
inconsistencies. Thus, make sure you do not mix several kinds of traffic maps (for
example, raster traffic map and transmitter coverage area traffic map) in a simulation
study; rather, make several simulation studies, each one based on a same sort of traffic
map. On the other hand, you can fully carry out a simulation study using several traffic
maps belonging to the same kind.
9-42

Chapter 9
Advanced tab
Generator initialization enables you to obtain the same random distribution in two
simulations just by giving the same non-zero integer in this field. For example, you
create a simulation with generator initialization value of 1 (or whichever integer different
from 0). When you create another simulation, giving 1 as generator initialization, you
obtain the same random distribution. To avoid getting similar distributions, just enter
zero value in this field. A group of several distributions created at the same time may be
repeated with the same principle. This can be useful when one wants to compare two
simulations with just one parameter value difference; so to make a just comparison, it is
better to have the same user locations (same path loss values for users).
You can then specify the maximum number of iterations allowed during a simulation, UL
and DL convergence thresholds.
The power control simulation is based on an iterative algorithm. In the Convergence
part, you can define how many iterations you want the simulation to run (maximum
number of iterations) and specify your own uplink and downlink convergence criteria
(percentage power difference for downlink and percentage noise difference for uplink
between two successive iterations).
When clicking OK, simulation starts running and stops when the convergence criteria
are met in two successive iterations (when there is no network parameter evolution).
Therefore, the simulation can finish before reaching the maximum number of defined
iterations.
When calculation is finished, U-Net has created the required number of simulations in
the newly created group of simulations.
U-Net makes easy the consistency management between radio data, simulations and
predictions.
Average simulations and replays are reachable from each of these subfolders. Display
properties are reachable form the Simulations folder.
IV. Replaying a CDMA/CDMA2000 simulation

U-Net allows the user to replay existing simulations in order to keep the same radio
configuration (including reference maps, initialization number) and to modify the
convergence parameters and the constraints on the cell loads. The new group of
simulations is based on the same random user distribution (number of users who try to
be connected, allocated service, mobility and activity status, geographic position), just
the power control is recalculated and the outputs updated.
To replay a group of CDMA/CDMA2000 simulations (one of several ones), proceed
as follows :
9-43

Chapter 9
1)
2)
Expand the CDMA/CDMA2000 simulations folder by left clicking on the
3)
Right click on the CDMA/CDMA2000 simulation group subfolder you want to
button.
replay the simulations to open the associated context menu.

4)
Left click in the scrolling menu on Replay....
5)
The replay simulation(s) dialog window opens.
6)
Set the parameters on the convergence parameters and the constraints on the cell
loads for the current group of simulations to replay.
7)
Once achieved, simulations are available for specific CDMA coverage predictions or for
Note:
Giving several times the same integer number (different from 0) as initialization number
in the simulation creation dialog box leads to replay simulations with identical user
random distribution.
Comment:
As the generator initialization function, this feature enables you to obtain the same user
distribution in two simulations. Nevertheless, the generator initialization option is more
powerful since it can be used to create several simulations with the same distribution at
the same time and several sets of different simulations with the same set of
distributions.
V. Generator initialisation - replay differences (CDMA/CDMA2000)

The main differences between two features are the inputs taken into account in
simulations. Comparison is detailed below.
z
Replay: U-Net reuses the same user distribution (user with a service, a mobility
and an activity status) and traffic parameters (such as maximum and minimum
traffic channel powers allowed, Eb/Nt targets...) as in the initial simulation. Just
radio data (new transmitter, azimuth...) modifications are taken into account during
power control simulation.
Generator initialization: If generator initialization entered when creating both

simulations is an integer different from 0, U-Net finds the same user distribution
(user with a service, a mobility and an activity status) in both simulations. On the
other hand, in this case, both traffic parameter (such as maximum and minimum
9-44

Chapter 9
traffic channel powers allowed, Eb/Nt targets...) and radio data (new transmitter,
azimuth...) modifications are taken into account during power control simulation.
VI. Averaging CDMA/CDMA2000 simulations

With U-Net, it is possible to average some available groups of simulations. This feature
also allows the user to calculate standard deviations on the averaged simulations.
Results are automatically displayed per cell, as in a single simulation.
To display average results per cell over a group of CDMA/CDMA2000 simulations,
1)
2)
3)
button.
Right click on the CDMA/CDMA2000 simulation group subfolder you want to

average the simulations to open the associated context menu.
4)
Left click in the scrolling menu on [Average simulations....].
5)
The average simulation dialog window opens.
6)
Click on the [available] tabs to display either the Statistics. Means or Standard
deviation window.
7)
Average simulations may be used in specific CDMA coverage predictions or in an AS

analysis with the point analysis tool.
VII. Adding a simulation to an existing group of CDMA/CDMA2000 simulations

In U-Net, It is possible to add a new simulation to an existing group of simulations.
When creating the new simulation, U-Net takes into account the same inputs (radio and
traffic data, simulation parameters) as used for generating the group of simulations and
replays user distribution and power control simulation.
To add a simulation to an existing group of simulations, proceed as follows:
1)
2)
Expand the CDMA/CDMA2000 Simulations folder by left clicking on the
3)
Right click on the simulation group on which you want to add a simulation.
4)
Choose the <New...> command from the open context menu.
5)
A new simulation is being computed using the parameters of the current group.
6)
After calculation, a new simulation is added to the group.
button.
Note:
The added simulation is then considered if you calculate an average simulation.

9-45

Chapter 9
9.7.3 CDMA/CDMA2000 Simulation Process

I. Power control CDMA/CDMA2000 simulation concepts
Power control consists of two steps in U-Net:
1st step : obtaining realistic user distribution
2nd step : Power control simulation
1)
1st step: obtaining realistic user distribution
To get user distribution, you need to have traffic cartography at your disposal.
Each user is assigned a service, a mobility type (RC) and an activity status by random
trial, according to a probability law that complies with the traffic database.
User activity status is an important output of random distribution, which will have direct
consequences on simulation and network noise level.
A user is either active or inactive:
z
Active means: a radio resource has been allocated to the user, and the user is
speaking (i.e. he creates interference both on the downlink and the uplink).
Inactive means: a radio resource has been allocated to the user, but he is not
speaking (i.e. he does not create any interference).
A second random trial determines user positions in their respective traffic zone.
2)
2nd step : Power control simulation
Power control simulation needs propagation path loss for transmitters and mobiles. If
these results are not available, U-Net achieves propagation calculation using the
propagation model as defined from either the transmitter or the prediction folders.
Based on CDMA air interface, network automatically regulates itself by using traffic
driven uplink and downlink power control in order to minimize interference and
maximize capacity. U-Net simulates this network regulation mechanism with an
iterative algorithm and calculates, for each user distribution, network parameters such
as base station power, mobile terminal power, active set and handover status for each
terminal.
The power control simulation is based on an iterative algorithm. Each iteration, all the
mobiles selected during the user distribution generation (1st step) try to be connected
one by one to network transmitters. The process is repeated from iteration to iteration
until convergence. The algorithm steps are detailed below Figure 9-1.

9-46

Chapter 9
Initialisation
1st step : Mi best server determination
2nd step : Mi active set determination
3rd step : Uplink power control

+
radio resource control
For each mobile Mi
4th step : Downlink power control

+
radio resource control
5th step : Uplink and downlink interference update
Congestion and radio resource control
Convergence study
Figure 9-1 Schematic view of power control simulation algorithm

In CDMA/CDMA2000 , downlink power control simulation is independently carried out
on fundamental channel and on supplemental channel. Point analysis (Downlink
availability) and prediction study (Service area Downlink) are based on the same
principle.
9-47

Chapter 9
During power control simulation, the DL rate on SCH is downgraded until the DL quality
level on SCH is reached. SCH is not used when the downgraded rate is twice lower
than the rate on FCH. Practically, the DL rate on SCH is multiplied by a downgrading
factor which is 2(-k) multiple. Therefore, the number of rejections due to an insufficient
reception on traffic channel (Ptch > PtchMax) should decrease.
Moreover, during power control simulation, the UL rate on SCH is downgraded until the
required power on UL is lower than the mobile maximum power. SCH is not used when
the downgraded rate is lower than twice the FCH rate. Practically, the UL rate on SCH is
multiplied by a downgrading factor, which is a multiple of 2(-k) (every downgrading step
is halving). Therefore, the number of rejections due to an insufficient power to transmit
(Pmob > PmobMax) should decrease.
SCH downgrading is also modelled during power control simulation when there is not
enough channel elements on UL and DL to enable the link. Therefore, mobile will be
rejected only if site lacks of channel elements to support FCH. As in case of DL
downgrading due to an insufficient reception on traffic channel, the downgrading is
driven by the best server of active set. Therefore, no downgrading occurs if there is not
enough channel elements on sites where other transmitters of active set are located;
mobile is directly rejected.
Note:
Power control on SCH will be carried out just for data service users.
During simulation, mobiles penalizing too much the others are ejected. Different causes
of ejection can be distinguished:
z
The signal quality is not sufficient:

- On the downlink, not enough pilot signal quality: Ec/I0 pilot < Ec/I0 min pilot
- On the downlink, not enough reception on traffic channel: Ptch > Ptch max (FCH
or SCH)
- On the uplink, not enough power to transmit: Pmob > Pmob max
When constraints above are respected, the network may be saturated:

- The maximum load factor is exceeded (at admission or congestion).
- Not enough channel elements on site: channel element saturation
- Not enough power for cells: Cell power saturation
- OVSF code saturation
9-48

z
Chapter 9
When the network is saturated; mobile ejection may be due to different reasons
described above: multiple causes.
II. CDMA/CDMA2000 simulation convergence method

The convergence criteria is evaluated as follows:
Each iteration k, U-Net evaluates:

DL
DL
max P (ic ) P (ic )
max Nuser
(ic )k Nuser
(ic )k 1
tx
k
tx
k 1

100
DL = max int Stations
100 , int Stations
DL

P tx ( ic )k
N user ( ic )k

UL
UL

UL
(ic )k Nuser
(ic )k 1
max Nuser
(ic )k 1 100 , int Stations

I UL (ic )k I tot
UL = max int max tot

100
UL
UL
Stations
(
)
I
ic
ic
N user ( )k

tot
k
Where:
parameter
meanings
the UL convergence threshold
the DL convergence threshold
the cell total transmitted power on the carrier ic
the total interference received by cell on the carrier ic

the number of users connected on UL on the carrier ic
the number of users connected on DL on the carrier ic
U-Net stops the algorithm if:

1)
1st case: Between two successive iterations, UL and DL are lower ( ) than their
respective thresholds (defined when creating a simulation).
The simulation has reached convergence.

Example:
Let us assume that the maximum number of iterations is 100, UL and DL convergence
thresholds are 5. If UL 5 and DL 5 between the 4th and the 5th iteration, U-Net
stops the algorithm after the 5th iteration. Convergence is reached.

9-49

2)
Chapter 9
2nd case: After 30 iterations, UL or/and DL are still higher than their respective
thresholds and from the 30th iteration, UL or/and DL do not decrease during 15
successive iterations.
The simulation has not reached convergence (specific divergence symbol).
Example:
Let us assume that the maximum number of iterations is 100, UL and DL convergence
thresholds are 5.
After the 30th iteration, UL or/and DL equal 100 and do not decrease during 15
successive iterations: U-Net stops the algorithm at the 46th iteration.
Convergence is not reached.
After the 30th iteration, UL or/and DL equal 80, they start decreasing slowly
until the 40th iteration (without going under the thresholds) and then, do not
change during 15 successive iterations: U-Net stops the algorithm at the 56th
iteration without reaching convergence.
3)
3rd case: After the last iteration.
If UL or/and DL are still strictly higher than their respective thresholds, the
simulation has not reached convergence (specific divergence symbol).
If UL and DL are lower than their respective thresholds, the simulation has
reached convergence.
III. Admission control in CDMA/CDMA2000 simulations

U-Net checks cell UL load during admission control (1st step: mobile best server
determination) and congestion control (after considering all the mobiles during an
iteration). Therefore, a mobile can be rejected due to a higher UL load either during
admission control, or during congestion control. It is possible to distinguish both
rejection causes.
A bit more information concerning the admission control is provided. During admission
control, U-Net calculates the uplink load factor of a considered cell assuming the
handled mobile is connected to it. Here, activity status assigned to users is not taken
into account. So even if the mobile is not active on UL, it can be rejected due to cell load
9-50

Chapter 9
saturation. To calculate the cell UL load factor, either U-Net takes into account mobile
power determined during power control if mobile was connected in previous iteration,
or it estimates a load rise due to mobile and adds it to the current load. The load rise
( X UL ) is calculated as follows:
X UL =
1
W
1 + UL
Q req RUL
b
Where
parameter
W
meanings
the chip rate (bit/s)
the Eb/Nt target on uplink (defined in service properties for a
given mobility),
the service uplink effective bit rate (bit/s).
IV. Channel element management in CDMA/CDMA2000 simulations

In U-Net, the number of channel elements needed for a user with given service and link
direction depends on site equipment and channel element consumption defined for the
equipment-service couple.
V. Walsh codes management

Walsh codes can be managed on the downlink during the simulation. U-Net performs
Walsh code allocation during the resource control step.
Walsh codes form a binary tree; codes with a longer length are generated from codes
with a shorter length. Indeed, length-k Walsh codes are generated from length-k/2
Walsh codes. Therefore, if one channel needs 1 length-k/2 Walsh code; it is equivalent
to use 2 length-k Walsh codes, or 4 length-2k Walsh codes,....as in Figure 9-2.

9-51

Chapter 9
Figure 9-2 Walsh codes

128 Walsh codes per transmitter and per carrier are available in CDMA/CDMA2000
projects while 512 codes are available in UMTS projects.
During the resource control, U-Net determines, for each transmitter and each carrier,
the number of codes, which will be consumed. Therefore, it allocates:
z
A 512 bits-length code per common channel, for each transmitter and each carrier.
A code per transmitter-receiver link, for FCH. The length of code to be allocated,
Code-Length, is determined as follows:
FCH
Code Length R DL
=W
b
A code per transmitter-receiver link, for SCH, in case SCH is supported by the user
radio configuration. The length of code to be allocated, Code-Length, is

determined as follows:
SCH
Code Length R DL
=W
b
where,
parameter
meanings
DL FCH
the service downlink bit rate on FCH
Rb
DL SCH
the service downlink bit rate on SCH
the spreading bandwidth
Rb
The Walsh code allocation follows the Buddy algorithm, which guarantees that:
z
If a k-length Walsh code is used, all of its children with lengths 2k, 4k... cannot be
used because they are no longer orthogonal.
If a k-length Walsh code is used, all of its ancestors with lengths k/2, k/4... cannot
be used because they are no longer orthogonal.

9-52

Chapter 9
Note:
z
The Walsh code allocation follows the mobile connection order (mobile order in the
Mobiles tab).
The Walsh code and channel element management is differently dealt with in case
of softer handover. U-Net allocates Walsh codes for each transmitter-receiver link
while it globally assigns channel elements to a site.
Example:
In CDMA/CDMA2000 , let a voice user with a RC1 be in softer handover. Therefore,
U-Net will allocate two Walsh codes (one for each transmitter-receiver link) and only
one channel element to the site.
VI. Walsh codes availability

An additional constraint on the Walsh codes, Number of codes, is available when
creating simulation. Therefore, when selecting the Number of codes option, U-Net
checks the Walsh code availability and then:
z
Ejects the mobile if there is no Walsh code to support FCH rate.
Downgrades the DL SCH rate if there is no Walsh code free to support the
requested SCH rate and enable the link.
Therefore, a mobile will be rejected for code saturation cause only if there is no Walsh
code to support FCH rate. The unavailability of Walsh code to support SCH rate leads
to a DL SCH rate downgrading.
Note:
When the Number of codes option is not selected, U-Net just checks the Walsh code
availability. No DL SCH rate downgrading is performed in case of Walsh code
unavailability.
VII. Modelling shadowing in CDMA/CDMA2000 simulations

In order to take into account prediction errors along paths in CDMA/CDMA2000
simulations, U-Net keeps a neutral predicted path loss for mobiles; a random
shadowing value is computed and added to the average predicted path loss. Cell edge

9-53

Chapter 9
coverage probability and shadowing margin are then introduced in prediction studies
and point analysis only.
From a user-defined model standard deviation (value associated to the receiver
position or default value) associated to the receiver position, a random shadowing error
is computed and added to the model path loss ( L path ). This random vale is drawn
during Monte-Carlo simulation; each user is assigned a service, a mobility type (RC),
an activity status, a geographic position and a random shadowing value.
For each link, path loss (L) can be broken down:
L = Lpath +
is a zero mean gaussian random variable G(0, dB ) representing variation due to
shadowing. It can be expressed as the sum of two uncorrelated zero mean gaussian
random variables,
and
models error related to the receiver local
environment; it is the same whichever the link.
models error related to the path
between transmitter and receiver.

Therefore, in case of two links, we have:
1 = L + P1
for the link 1
2 = L + P2
for the link 2
From
, the model standard deviation ( ) and the correlation coefficient ( ) between
and
Pi
have the same standard deviations).
, we can calculate standard deviations of
We have:
2 = L2 + P2
L2
2
Therefore.
9-54
( L )
and
Pi
( P )
(assuming all

Chapter 9
P2 = 2 (1 )
L2 = 2
There is currently no agreed model for predicting correlation coefficient ( ) between 1

2
and
. Two key variables influence correlation.
The angle between the two paths. If this angle is small, correlation is high.
The relative values of the two path lengths. If angle is 0 and path lengths are the same,
correlation is zero. Correlation is different from zero when path lengths differ.
A simple model has been found [1]:
= T

D1
D2
when
is a function of the mean size of obstacles near the receiver and is also linked to
the receiver environment.

In a normal handover state, assuming a hexagonal schema for sites, is close to (+//3) and D1/D2 is close to 1.
We found in literature that = 0.5 when = 0.3 and t = /10.
In U-Net, is set to 0.5. So, we have:
L =
and
P =
Therefore, to model shadowing error common with all signals arriving at mobile
Re ceiver
( E Shadowing ), values are randomly drawn for each mobile; they follows a zero-mean
gaussian distribution with a standard deviation (either value associated to the mobile

clutter class, or a default value) 2 where ( ) is the standard deviation associated
to the mobile clutter class. Then, for each mobile-transmitter couple, U-Net draws
9-55

Chapter 9
another value representing shadowing part uncorrelated with the position of the mobile
Path
( E Shadowing ); this value follows a zero-mean gaussian distribution with a standard

2
.
deviation
Random shadowing error means are centred on zero. Hence, this shadowing
modelling method has no impact on the simulated network load. On the other hand, as
shadowing errors on the receiver-transmitter links are uncorrelated, the method will
influence the evaluated macro-diversity gain.
Random shadowing values used for each mobile and mobile-transmitter pair are
detailed in simulation results.
9.7.4 CDMA/CDMA2000 Simulation Results Summary

I. Displaying CDMA/CDMA2000 simulation requirements and results
When a simulation study has been created, U-Net creates a statistical report on
simulation results. A part is dedicated to traffic request determined from the 1st step of
simulation (traffic scenario elaboration) and another one refers to network performance
(results coming from 2nd step of simulation: power control).
If a focus zone has been defined in your project, only sites, transmitters and mobiles
located inside the focus zone are considered when accessing simulation results. The
global output statistics are based on these mobiles.
Traffic request:
z
U-Net calculates the total number of users who try to be connected. It is a result of
the first random trial, the power control has not yet been achieved. This result
depends on the traffic description and cartography.
During the first random trial, each user is assigned a service. Therefore, UL and
DL rates that all the users could theoretically generate are provided.
Breakdown (number of users, UL and DL rates) per service is given.
Results:
z
The number and the percentage of rejected users are calculated and detailed per
rejection cause. These results are determined after the power control and depend
on network design.
U-Net supplies the total number and the percentage of connected users, UL and
DL total rates that they generate. These data are also detailed per service.
To display requirements and results on any simulation, proceed as follows Table 9-17 :

9-56

Chapter 9
Table 9-17 display requirements and results

Method
Method 1
Method 2
step
1)
2)
Expand the CDMA/CDMA2000 simulations folder by left

3)

4)
Right click on the CDMA/CDMA2000 simulation you want to

display the requests and results to open the associated
context menu.
5)
6)
Click on the Statistics tab from the open window.
7)
1)
2)

3)

4)
Double click on the CDMA/CDMA2000 simulation you want

to display the requests and results.
5)
Click on the Statistics tab from the open window.
6)
Click<OK> to close the window.
Note:
The traffic rates are calculated at the user level without taking into account handover.
Once achieved, simulations are available for specific CDMA/CDMA2000 coverage
II. Displaying input parameters of an existing CDMA/CDMA2000 simulation

After a CDMA/CDMA2000 simulation, U-Net can display the associated transmitter
global parameters and the inputs defined during the simulation creation
To display the input parameters of an existing simulation, proceed as follows Table
9-18.

9-57

Chapter 9
Table 9-18 display the input parameters of an existing simulation

Method
Method 1
Method 2
step
1)
2)

3)

4)

display the initial conditions to open the associated context
menu.
5)
6)
7)
1)
2)

3)

4)

to display the initial conditions.
5)
6)
The initial condition tab window contains as follows Table 9-19.

Table 9-19 Parameters in condition tab window
parameter
The transmitter global
parameters
In detail
z
The spreading width.
The orthogonality factor.
The default uplink soft handover gain.
The inputs available when

creating simulation
The MRC in softer/soft option: if it is defined

or not.
The method used to calculate Io
The maximum number of iterations.
The uplink
thresholds.
and
downlink
convergence
The simulation constraints such as the

maximum power, the maximum number of
channel elements, and the uplink load factor
and the maximum load.
The name of used traffic maps.

9-58

Chapter 9
parameter
In detail
orthogonality factor and

standard deviation as defined
per clutter type.
Note:
When the simulation does not converge (UL and DL convergence criteria not reached
at the end of the simulation), U-Net displays a special warning icon
in front of
Simulation object.
III. Summarising results per site (CDMA/CDMA2000 projects)

After a CDMA/CDMA2000 simulation, U-Net can display the associated results per
site.
To display the results on any simulation per site, proceed as follows Table 9-20.
Table 9-20 display the results on any simulation per sit
Method
Method 1
Method 2
step
1)
2)

3)

simulation you want to display the requests and results
by left clicking on the button.
4)
Right click on the CDMA/CDMA2000 simulation you

want to display the results per site to open the
5)
6)
7)
Click OK to close the window.
1)
2)

3)

simulation you want to display the requests and results
by left clicking on the button.
4)

to display the results per site.
5)
6)
Click OK to close the window.

9-59

Chapter 9
In this window, U-Net displays the maximum number of channel elements previously
defined for each site, the number of required channel elements in uplink and downlink
at the end of simulation, the number of extra channel elements due to soft handover,
the properties related to each site equipment (MUD factor, Rake receiver efficiency
factor, carrier selection mode, AS restricted to neighbours option and overhead
channel elements on uplink and downlink), the uplink and downlink throughputs (kbits/s)
per service supported by site. The UL and DL throughputs are the number of kbits per
second supported by the site on uplink and downlink to supply (mobiles connected with
the transmitters located on the site) one kind of services. The throughput calculation
takes into account the handover connections.
If the maximum channel element number is exceeded, sites are displayed with red
colour.
Note:
The
IV. Summarising results per cell (CDMA/CDMA2000 projects)

After a CDMA/CDMA2000 simulation, U-Net can display the associated results per cell.
Method
Method 1
step
1)
2)

3)

4)

display the results per cell to open the associated context
menu.
5)
6)
7)

9-60

Chapter 9
Method
Method 2
step
1)
2)

3)

4)

to display the results per cell.
5)
6)
In this window, U-Net provides the simulation input data like the maximum power, the
pilot power, the synchro power, the paging power, the AS threshold, the gain, the
reception and transmission losses, the noise figure, and simulation output data
regarding cells such as the total DL power used (on the fundamental and on the
supplemental channel), the UL total noise, the UL and DL load factors, the UL and DL
noise rises, the percentage of used power, the UL reuse factor, the UL reuse efficiency,
the number of UL and DL links, the number of used Walsh codes, the percentage of
handover types (on FCH and SCH), the UL and DL throughputs (on FCH and SCH), the
minimum, maximum and average traffic channel powers, the number of users rejected
for each cause for each cell.
See Simulation outputs on cell components.
Note:
The
current table. The "Commit loads" button permits to copy UL loads and total powers DL
(or their average in the case of several carriers) in the cell table in order to be taken
potentially as reference for specific CDMA predictions (by selecting the None option
from the simulation scrolling box).
Average simulations are ordered by cells. Once achieved, simulations are available for
specific CDMA coverage predictions or for an AS analysis with the point analysis tool.
V. Committing simulated loads to cells (CDMA/CDMA2000 projects)

In U-Net, to enable simulation result sharing, two fields, the UL load (UL load factor)
and total power (total DL power used), are available in cell properties. Both parameters
9-61

Chapter 9
can be results coming from a single or an average simulation or inputs manually

specified in the Cell table or in the Transmission/Reception tab of each cell Property
window.
To assign any simulated UL load factor and total DL power to cells from a network,
proceed as follows Table 9-22.
Table 9-22 The step of assign any simulated UL load factor and total DL power
Method
Method 1
Method 2
step
1)
2)

3)

4)

use the simulated results to open the associated context
menu.
5)
6)
7)
Click the
8)

window.
9)
1)
2)

3)

4)

to use the simulated results.
5)
6)
Click the
7)

window.
8)

9-62

Chapter 9
Note:
z
When assigned to cells, these values can be used for coverages based on no
simulation.
This feature is also available from the mean tab window of any average simulation.
Reminder : the Commit load button is inactive as long as both fields, UL load and
total power, do not exist.
VI. Summarising results per mobile (CDMA/CDMA2000 projects)

After a CDMA/CDMA2000 simulation, U-Net can display the associated results per
mobile.
Method
Method 1
Method 2
step
1)
2)

3)

4)

display the results per mobile to open the associated context
menu.
5)
6)
Click on the Mobiles tab from the open window.
7)
1)
2)

3)

4)

to display the results per mobile.
5)
Click on the Mobiles tab from the open window.
6)
In this window, U-Net gives information about calculated terminal parameters. First,
U-Net mentions simulation input data: X, Y, service, terminal, user profile, user mobility
and activity obtained from random trial. U-Net displays simulation output data for these
9-63

Chapter 9
users: carrier, DL and UL requested and obtained rates, mobile power (on the
fundamental channel and on the supplemental channel), best server, connection status,
handover status, transmitters in active set and Ec/Io from cells in active set.
U-Net displays which carrier is used for connection and calculates the power
transmitted by the terminal (on FCH and SCH) . U-Net identifies the best server among
the cells taking part in mobile active set.
Note:
z
Connection status refers to mobile ejection causes previously defined. It gives the
reasons why the mobile, even active, is not connected to any transmitter at the end
of the simulation.
U-Net allows to analyse what type of handover is possible for a mobile; providing the
HO status information. HO status represents the real number of sites compared to
the number of cells in active set.
Active set is the list of transmitters (or cells since on unique carrier) in connection
with the mobile. The maximum number of transmitters in active set is defined by the
user in Terminal Properties and besides limited to 4 in U-Net. Soft handover can be
enabled/disabled for every service. For each transmitter in active set, Ec/Io values
are calculated and may be compared to Ec/Io thresholds and T-Drop previously
defined in Mobility Type Properties. Transmitters, which provide an Ec/Io pilot
quality that is lower than [ Best server Ec/Io - AS-threshold ], are rejected from the
active set.
Example:
z
when a mobile is in connection with three cells and among them two co-site cells
(soft - softer handover), its HO status is 2/3. When the mobile is connected with only
one transmitter (no handover) its HO status is 1/1. When the mobile is connected
with three co-site transmitters (softer - softer handover), its HO status is 1/3.

9-64

Chapter 9
Note:
z
The
z
Checking the Detailed results box during the simulation creation enables you to get
additional simulation outputs relating to mobiles and shadowing values computed
along paths between transmitters and mobiles.
VII. Displaying shadowing values of a CDMA/CDMA2000 simulation

This feature is available only when selecting the Detailed results option in the
simulation creation dialog. Here, U-Net details for each mobile:
z
Its number Id.
The clutter class where the receiver is located.
The model standard deviation (value associated to the clutter class or default
value).
The random shadowing error (
ceiver
ERe
Shadowing
) related to the receiver local
environment (Value at receiver); this one is the same whichever the link.
z
The random shadowing errors (
Path
E Shadowing
) due to the transmitter-receiver path
(Value). U-Net gives this error for a maximum of ten paths; it considers the ten
transmitters, which have the mobile in their calculation areas and the lowest path
losses (Lpath). Transmitters are sorted in an ascending path loss order.
To display shadowing values for each mobile in any simulation, proceed as follows
Table 9-24.
Table 9-24 The step of display shadowing values for each mobile
Method
Method 1
step
1)
2)

3)

simulation you want to display by left clicking on the
button.
4)

display the clutter data to open the associated context
menu.
5)

9-65

Chapter 9
Method
Method 2
step
6)

window.
7)
1)
2)

3)

simulation you want to display by left clicking on the
button.
4)

to display the clutter data.
5)

window.
6)
Note:
z
The values
ceiver
ERe
Shadowing
computed for all the mobiles follow a zero-mean gaussian
2
.
distribution with a standard deviation
The values
Path
E Shadowing
computed for a given mobile follow a zero-mean gaussian
distribution with a standard deviation 2 .
VIII. Managing CDMA/CDMA2000 simulation results on the map

From any simulation, U-Net can, globally or individually, display the associated results
on the map in several ways. These can be managed globally for all the simulations.
To make available the display dialog window on all the simulations of the current
project, proceed as follows Table 9-25.
Table 9-25 make available the display dialog window
Method
Method 1
step
1)
2)

9-66

Chapter 9
Method
step
clicking on the
3)
Method 2
button.
Right click on the CDMA/CDMA2000 simulations folder to

4)
5)

current project.
6)
1)
2)

3)
Double click on the CDMA/CDMA2000 simulations folder.
4)

current project.
5)
Like for most of the other display dialog windows in U-Net, you can choose the display
type associated with the values (unique, discrete, values interval) and some
corresponding fields. Due to the complexity of CDMA/CDMA2000 technology
simulations, these fields are numerous and can be obtained as indicated in the
following Table 9-26.
Table 9-26 display type and fields
Display type
Field
Unique
All the simulations
Discrete Values
Service
Terminal
User
Mobility
Discrete Values
Activity
Carrier
Connection status
Best server
HO status
Asi
Clutter
Value intervals

9-67

Chapter 9
Display type
Value intervals
Field
Y
DL requested rate (kbits/s)
UL requested rate (kbits/s)
DL obtained rate (kbits/s)
UL obtained rate (kbits/s)
Mobile FCH power
Mobile SCH power
Ec/Io Asi
Cell power FCH Asi (DL)
Cell power SCH Asi (DL)
Ntot DL ASi
Load factor Asi
Noise rise Asi
Reuse factor Asi
Iintra Asi
Iextra Asi
Total path loss Asi
Nb UL CEs
Nb DL CEs
Name
Orthogonality factor
UL SHO gain UL
UL SHO gain DL
Note:
Existing simulations, in the [Explorer] window contain sub-items which depend on
results are displayed on the map. The simulation display is managed with the standard
display dialog in use under U-Net. Once achieved, simulations are available for specific
CDMA coverage predictions or for an AS analysis with the point analysis tool.

9-68

Chapter 9
IX. Exporting CDMA/CDMA2000 simulation statistics

U-Net can export statistics from the results tables of any simulation and average
statistics from group of simulations. U-Net can These can be managed globally for all
the simulations.
To export the statistics from a results table, proceed as follows:
1)
2)
3)
Right click on the simulation group folder to open the associated context menu.
4)
Left click in the scrolling menu on [Average simulation... ]to open the average
button.
simulation results; Or.Right click on a simulation to open the associated context

menu.Left click in the scrolling menu on Properties... to open the statistics for the
current simulation results
5)
On any results table tab (e.g. Sites. Cells. Mobiles. ...). left click on the Actions
button.
6)
Select the <Export> command.
Note:
This will open the generic table export window. It is the same export interface as the
export function for the tables in U-Net. You can export the statistics from simulations in
delimited ASCII text files.
To export a results table, proceed as follows :

1)
2)
Select the separator and the decimal symbol.
3)
Specify if you want to save the table header in the file.
4)
Use the buttons
and
to be exported. Finally. use the buttons
in order to define the list of fields

and
in order to change the order of
fields to be exported.
5)
6)
In the open dialog box, select the directory where you want to save the exported file, enter
Or
1)
2)
Click on the <Load> button.
3)
Specify the directory where the configuration file is located.

9-69

Chapter 9
4)
Click on Open to open the dialog.
5)
6)
In the open dialog box, select the directory where you want to save the exported file, enter
Note:
Export settings may be saved in a configuration file. Click on Save. In the open dialog
box, specify the directory where you want to save the configuration file, type the file
name and click on Open to close the dialog.
9.7.5 CDMA/CDMA2000 Simulation Outputs

I. CDMA/CDMA2000 simulation outputs on sites
Each site is characterised by its maximum number of channel elements previously
defined.
Results are detailed for:
z
The number of channel elements required on uplink and downlink on FCH and
SCH channels at the end of simulation.
The number of channel elements due to soft handover overhead, for UL and DL
(Nb CEs due to SHO overhead UL and DL).
The properties related to the equipment associated to each site (parameters used
during simulation): MUD factor, Rake receiver efficiency factor, carrier selection
mode, AS restricted to neighbours option and overhead channel elements on
uplink and downlink.
The uplink and downlink throughputs (kbits/s) per service supported by site on
FCH and SCH channels. UL and DL throughputs are the number of kbits per
second supported by the site on uplink and downlink to supply (mobiles connected
with the transmitters located on the site) a particular service. The throughput
calculation takes into account the handover connections.
II. CDMA/CDMA2000 simulation outputs on cells

Each cell is defined by its carrier, its maximum power, the pilot power, the sync power,
the paging power, the AS threshold, the gain, reception and transmission losses, the
noise figure. Results are detailed for the total power used on a carrier (DL), DL FCH and
SCH powers, the UL total noise, UL and DL load factors, UL and DL noise rises, the
percentage of used power, the UL reuse factor, the UL reuse efficiency, the number of
UL and DL radio links, the number of Walsh codes allocated to a transmitter, the
9-70

Chapter 9
number of Walsh codes dedicated to FCH, then to SCH, the percentage of each
handover type, the UL and DL number of channel elements used on FCH and on SCH,
the UL and DL throughputs on FCH and SCH, minimum, average and maximum traffic
III. CDMA/CDMA2000 average simulation outputs on cells

Each cell is detailed by its carrier and the average on the UL total noise, UL and DL load
factors, UL and DL noise rises, the total power used, the UL reuse factor, the UL reuse
efficiency, the number of UL and DL radio links, the number of Walsh codes, the
percentage of each handover type, the UL and DL throughputs, minimum, average and
maximum traffic channel powers, the number of users rejected for each reason.
IV. CDMA/CDMA2000 standard deviation of simulation outputs on cells

Each cell is detailed by its cell and the standard deviation of the UL total noise, UL and
DL load factors, the total power used, the UL reuse factor, the UL reuse efficiency, the
number of UL and DL radio links, the number of Walsh codes, the percentage of each
handover type, the UL and DL throughputs, minimum, average and maximum traffic
V. CDMA/CDMA2000 simulation outputs on cell components

z
The total power used is the total power that the transmitter transmits on a carrier.
When constraints are settled, the calculated power cannot exceed the maximum power
value previously defined in Transmitter Properties.
The total FCH Power used is the power transmitted on FCH.
The total SCH Power used is the power transmitted on SCH.
The uplink total noise takes into account the total signal received at the transmitter
on a carrier (from intracell and extracell terminals) and the thermal noise.
From uplink total noise and uplink interference, U-Net calculates uplink transmitter
load factor on a carrier. If this constraint has been selected, UL cell load factor is
not allowed to exceed the user-defined value.
The uplink reuse factor is determined from uplink intra and extra-cellular
interference (signals received by the transmitter respectively from intracell and
extracell terminals).
The uplink reuse efficiency is the reciprocal of the uplink reuse factor.
The DL load factor of the cell i corresponds to the (DL average interference [due to
transmitter signals on the same carrier] for terminals in the transmitter i area) / (DL
average total noise [due to transmitter signals and to thermal noise of terminals]
for terminals in the transmitter i area) ratio.
The uplink and downlink noise rises are respectively calculated from uplink and
downlink load factors. These data point out the signal degradation due to cell load
(interference margin in the link budget).
9-71

z
Chapter 9
The percentage of used power is determined from the total DL power-maximum

power ratio (power stated in W). This value also represents of the cell DL loading
(percentage of DL capacity reached).
Note:
the maximum power is an input data user-definable for each cell in the Properties
window. On the other hand, the power is a simulation output data calculated for each
transmitter, carrier by carrier.
U-Net estimates the percentages of handover status which the transmitter takes part in.
HO status represents the number of sites compared to the number of transmitters in
active set size. Active set is the list of transmitters in connection with mobiles. The
maximum number of transmitters in the active set is defined by the user in Terminal
Properties and limited to 6 for CDMA/CDMA2000 projects. For example, when a mobile
is in connection with three transmitters and among them two co-site transmitters (soft softer handover), its HO status is 2/3. When the mobile is connected with only one
transmitter (no handover), its HO status is 1/1. When the mobile is connected with three
co-site transmitters (softer-softer handover), its HO status is 1/3.
Note:
U-Net details only the results for the following handover status, no handover (1/1),
softer (1/2), soft (2/2), softer-soft (2/3) and soft-soft (3/3) handovers; the other
handover status (other HO) are globally analysed.
The number of radio links corresponds to the number of users-transmitters links

on the same carrier. This data is calculated on uplink and on downlink. A single
user can use several radio links (handover).
The number of channel elements required by FCH and SCH to provide connected
mobiles with the service is estimated on UL and DL. These data are given without
taking into account handover status. Therefore, the sum of channel elements
requested by transmitters on the same site may exceed the number of channel
element required by the site (result provided in the Sites tab).
The uplink and downlink throughputs represent respectively the numbers of Kbits
per second delivered by the transmitter on FCH and on SCH. These data are
calculated on uplink and on downlink.
Minimum traffic channel power is the lowest one of the powers allocated to traffic
Maximum traffic channel power is the greatest of the powers allocated to traffic
9-72

z
Chapter 9
Average traffic channel power is the average of the powers allocated to traffic
VI. CDMA/CDMA2000 simulation outputs on mobiles

Each user is defined by his location, the service and the terminal used, his profile, his
mobility and his potential activity. Results are given on carriers, UL and DL requested
and obtained rates, mobile total, FCH and SCH powers, connection status, best
servers, HO status, active set transmitters and associated Ec/Io.
If the detailed results box has been checked for the current simulation, results are also
given, for each (mobile - transmitters in active set) link, on the UL and DL downgrading
factors applied on the SCH, the downlink total noise, Cell powers transmitted on the
FCH and the SCH, the downlink load factor, the downlink noise rise, the downlink reuse
factor, the total noise received at the terminal from the transmitter area (Iintra (DL) and
the total noise received at the terminal from other transmitter areas (Iextra (DL), and the
total loss on the link(s). Moreover, U-Net provides the name of the clutter class where
the probe receiver is located, the orthogonality factor, the UL and DL SHO gains (on
FCH and SCH).
VII. CDMA/CDMA2000 simulation outputs on mobile components

U-Net sums up power control simulation inputs and outputs, for all the users who try to
be connected.
z
X and Y are the coordinates of users who try to be connected (geographic position
determined by the 2nd random trial). The power control is based on this order.
Note:
Ejected users at the end of the power control are included in this list.
Service, user mobility and status activity are the 1st random trial results (user
distribution generation).
Terminal and user profile are based on traffic description. According to the service
and activity status assigned to a user, U-Net determines his terminal and the
corresponding user profile.
The carrier used for the mobile-transmitter connection.
DL and UL requested rates: they respectively correspond to the DL and UL

effective bit rates of service.
DL and UL obtained rates: after power control simulation, the obtained rate equals
the requested rate if the mobile is connected. Else, the obtained rate is zero.
The total power transmitted by the terminal.

9-73

Chapter 9
The best server among the transmitters entering mobile active set.
The Connection status refers to mobile ejection causes previously defined. It gives
the reasons why the mobile, even active, is not connected to any transmitter at the
end of the simulation.
The HO status HO status represents the real number of sites used compared to
the number of fingers.
For example, if the terminal active set size is 6 and if its number of fingers is 3, the
mobile will be able to be connected with none, one, two or three transmitters.
U-Net will consider in simulations and in predictions (HO status study) the
following handover status, no handover (1/1), softer (1/2), soft (2/2), softer-soft
(2/3), soft-soft (3/3), or softer-softer (1/3) handovers.
The list of transmitters in connection with the mobile (Active set). The maximum
number of transmitters in active set is defined by the user in Terminal Properties
and limited to 6 in U-Net. Soft handover can be enabled/disabled for every service.
Ec/Io values are calculated for each transmitter in active set and may be
compared to Ec/Io thresholds and T-Drop previously defined in Mobility Type
Properties.
Note:
Transmitters, which the Ec/Io value is AS-threshold value lower than the best one
(Active Set 1), are rejected from the active set.
The Downgrading factor for SCH: means the rate on the SCH was halved to
remain within the maximum SCH power, and the maximum cell power. It results in
better signal quality because reducing the SCH rate increases the processing gain,
thus reduces the required C/I ratio for successful decoding.
The cell power transmitted on traffic channel. This parameter is determined for
each (mobile transmitters in active set) link.
The DL total noise is calculated for each (mobile transmitters in active set) link
(FCH and SCH). This parameter is calculated from the transmitter thermal noise
and the DL total interference at the terminal.
The DL load factor (determined for each (mobile transmitters in active set) link)
corresponds to the downlink total interference total noise at the terminal ratio.
The DL noise rise (evaluated for each (mobile transmitters in active set) link) is
deduced from the DL load factor.
The DL reuse factor (calculated for each (mobile transmitters in active set) link)
is evaluated from the interference received at the terminal from the intra
transmitter area and the total interference received at the terminal from all the
transmitters (intra and extra cells).
DL intra-cellular interference for each cell (i) of the mobile active set:
9-74

Chapter 9
DL
(ic ) Fortho P DL
(ic ) PSCH
I int ra = P DL
tot
tot
LT
i
i
DL extra-cellular interference for each cell (i) of the mobile active set:
I extra =
DL
(ic ) Fortho P DL
(ic ) PSCH
P DL
tot
tot
LT
Tx ,iTx
The total path loss (determined for each (mobile transmitters in active set) link) is
calculated from transmitter and terminal losses, path loss (propagation result),
transmitter and terminal gains.
The number of uplink and downlink channel elements respectively refer to the
number of channel elements consumed by the user on UL and DL.
The orthogonality factor is user-defined in the clutter Properties window.
The UL SHO gain is determined for mobile receivers connected either on UL or on UL and
DL.:
UL Macrodiver sity Gain =
( ) ( )
Eb
Nt
UL
Eb
Nt
UL
tch BS
The DL SHO gain is evaluated in case mobile receivers are connected either on DL or on
UL and DL.:
DL Macrodiver sity Gain =
( ) ( )
Eb
Nt
DL
Eb
Nt
DL
tch BS
9.8 Specific CDMA/CDMA2000 Prediction Studies

9.8.1 Overview
For CDMA (Code Division Multiple Access) projects, U-Net provides two kinds of
predictions.
I. Point analysis
Point analysis which enables you to get prediction at a specific location within your
network:
z
Standard studies on pilot reception (Profile, Reception and Results tab),
Active set analysis of a real time probe user in order to determine CDMA pilot
quality and connection status at the receiver by using the AS analysis tab.

9-75

Chapter 9
Note:
AS analysis is a radio reception diagnosis provided for:
z
UL and DL load conditions. Analysis is based on the UL load percentage and the DL
total power of cells. These parameters can be either outputs of a given simulation,
or average values calculated from a group of simulations, or user-defined cell inputs
a user-definable probe receiver with associated terminal, mobility and service. This
receiver does not create any interference.
II. Coverage studies

Coverage studies where each map bin is considered as a probe user with associated
terminal, mobility and service. These are ordered in four different groups of studies,
listed in a natural planning order, from the indispensable pilot study to the study of
downlink total noise, with respect to the propagation model as defined :
z
Pilot-oriented studies to determine pilot coverage by transmitter, the pilot

coverage by signal level, overlapping area, pilot quality (Ec/Io) and pilot pollution.
Service-oriented studies to determine service availability in uplink and

downlink and effective service areas.
handover status study to analyse macro-diversity performance.
Except pilot coverage, coverage by signal level and overlapping studies, which are
similar to classical coverage studies, all other studies are specific to CDMA/CDMA2000
network planning and closely related to a particular CDMA/CDMA2000 simulation.
Power control is achieved once only during simulation but never during prediction
studies. Simulation outputs such as uplink and downlink noise levels generated by the
users may be used to evaluate the radio reception. Therefore, prediction studies may
be based on:
z
UL load and DL total power modelled during power control simulation for point
analysis.
UL load and DL total power modelled during power control simulation for coverage
studies.
User-definable UL load and DL total power for coverage studies :
Specific predictions can be based on either user defined load estimations (when filling
manually the UL_load and Total power cells from the cell table) or by using the "Commit
loads" button (assigning to these columns the calculated uplink loads and total powers
from the current simulation) in the Cells tab window of a simulation result window. To
use these reported values, just select the None option from the Simulation scrolling
box.
9-76

Chapter 9
Specific CDMA coverage studies may be performed with four different purposes:
z
Analyse in detail one particular simulation.
Globally analyse all simulations and evaluate network stability with regard to traffic
fluctuations.
Analyse an average simulation..
Analyse user-definable parameters such as UL load and DL total power without

simulation.
For these coverage studies, since study GUI is generic, the general rule is to choose :
z
either a single simulation, or a group of simulations and a user-definable

a terminal, a mobility (or All), a service (or All).
a specific carrier or all the carriers.
and to display the results as function of the attribute you want.

In this studies, each bin may be seen as a probe mobile, which does not create any
interference
Note:
z
If you modify radio parameters, before recalculating predictions, do not forget to

replay CDMA simulations first in order to base predictions on up-to-date simulations.
map before further analysis. To help on that, U-Net provides a feature to
automatically calculate CDMA predictions after simulations without any
intermediary step.
Important : Any of these specific CDMA studies requires propagation path loss on
each bin.
9.8.2 CDMA/CDMA2000 Prediction Process

I. Predicting on given CDMA/CDMA2000 carriers
In U-Net, specific CDMA studies can be based on given carriers.
To base your prediction on given carriers, proceed as follows:
1)
Create a new prediction or access the properties of an existing coverage study

you want to calculate again.
2)
Click the [Simulation] tab.

9-77

3)
Chapter 9
Choose the carrier selection mode you want to consider in the Carrier scrolling
menu.
4)
Click <OK> or <Apply> to validate.
Note:
When choosing a carrier, only cells using this carrier are taken into account in
calculations. U-Net will display a coverage by carrier. To get a coverage based on all
the carriers, select the All option. In this case, U-Net displays a multi-carrier coverage. It
selects on each bin the best carrier according to the selection mode specified in the
properties of the transmitters from the current network.
II. Modelling shadowing in CDMA/CDMA2000 predictions

Transmitted powers on downlink and uplink interference determined during simulation
are used. On each analysed bin, a probe mobile is placed. The path loss of the probe
mobile is the computed path loss (Lpath) plus a margin (MShadowing). This one
depends on the required cell edge coverage probability and model standard deviation
at the probe mobile (either associated to the clutter class where the probe mobile is, or
a default value). In case of macro-diversity, a gain is calculated on uplink and downlink
depending on the number of used links.
You can enter a cell edge coverage probability (x%) when defining prediction properties
(point analysis: Profile, Reception and AS analysis tab and coverage studies).
Therefore, the evaluated pilot quality, uplink and downlink traffic channel qualities are
reliable x% of time.
Formulas used to compute shadowing margin, macro-diversity gains (2 and 3 links) are
detailed in the Technical reference guide.
9.8.3 Managing CDMA/CDMA2000 Predictions

I. Creating predictions from modified CDMA/CDMA2000 simulations
This feature is provided to automatically calculate CDMA/CDMA2000 predictions after
simulations without intermediary step. In fact, you just need to define the
CDMA/CDMA2000 prediction studies you want to perform and then, press the
Calculate command: first, U-Net calculates the simulations and then, the predictions
based on simulations. Therefore, it is no more necessary to wait for the simulations to
be finished to create the CDMA/CDMA2000 prediction studies and start the
calculations.
9-78

Chapter 9

1)
Create the CDMA prediction studies you want to perform and define their
properties (colour, terminal, mobility, service). As no simulation has been
previously performed, you cannot base prediction studies on a specific simulation.
2)
Thus, choose either an average analysis (Average) or a statistical analysis based

on a probability (All) on all the future simulations.
Calculate button (or F7).
3)
Left click on the
4)
The Creation of simulations window opens.
5)
Specify the simulation inputs (number of simulations to be created, convergence

criteria.
6)
Press <OK> to start the calculations.
U-Net performs the simulations and lists them in the CDMA/CDMA2000 simulation
folder. Then, U-Net carries out the prediction calculations based on the created
simulations.
II. Managing CDMA/CDMA2000 prediction display

CDMA/CDMA2000 prediction dialogs include the U-Net generic display tab. It enables
to display covered areas with graphic settings depending on any attribute (from
transmitter, site, etc...) and to easily manage legends, tips, thresholds, etc... Since
prediction study user interface is generic, many associations between selected items in
the Simulation tab (a terminal, a mobility type - or all -, a service - or all -, a specific
carrier - or all) and in the Display tab are available. So several calculation and display
settings are possible.
Note:
You can analyse different mobility and several services in a same study. For any
CDMA/CDMA2000 study, in the Simulation tab, you can choose All in the Service
or/and SCH scrolling menus. In this case, U-Net works out the coverage criterion for
each service or/and SCH rates; a bin of the map will be covered if the studied coverage
criterion is met for any service or/and SCH rate. In addition, receiver definition and
coverage display are not linked. Parameters set in the Simulation tab are used in order
to predetermine the coverage area (area where U-Net will display coverage) while
graphical settings (available in the Display tab) enable you to choose how to represent
the coverage area. For example, it is possible to perform multi-service or/and
multi-SCH rate pilot reception analysis and to choose a coverage display per
transmitter or depending on any transmitter attribute.

9-79

Chapter 9
The available display types (depending on the study to be carried out) are listed below:
z
Single colour : Coverage is mono colour; it displays areas where radio conditions
are satisfied.
Colour per transmitter : Coverage displays areas where radio conditions are
satisfied. Moreover, the bin colour corresponds to the colour of the first transmitter
in active set (best server).
Colour per service : The receiver is not totally defined. Its service can take all
existing service types. There are as many graphical coverage layers as
user-defined services. For each service, coverage layer displays areas where
radio conditions are satisfied.
Colour per mobility : The receiver is not totally defined. Its mobility can take all
existing mobility types. There are as many graphical coverage layers as
user-defined mobility types. For each mobility, coverage layer displays areas
where radio conditions are satisfied.
Colour per probability : Coverage displays areas where radio conditions are
satisfied with different levels of probability. There are as many graphical coverage
layers as user-defined probability thresholds (by default 0.5 and 0.9).
Colour per quality margin : Each coverage layer displays area where the quality
margin is greater than the user-defined threshold value. There are as many
graphical coverage layers as user-defined quality margins. The quality margin is
the difference between the quality level and the target quality level. There is
Colour per maximum quality level : Each coverage layer displays area where
the maximum signal quality (even if not reaching the quality target) exceeds the
user-defined quality level. There are as many graphical coverage layers as
Colour per effective quality level : Each coverage layer displays area where the
effective signal quality (min between the maximum and the quality target) exceeds
the user-defined quality level. There are as many graphical coverage layers as
Colour per handover status : Coverage displays areas where radio conditions
are satisfied for at least one transmitter pilot quality. There are as many graphical
coverage layers as user-defined handover status. Each layer represents a
handover status. There is no intersection between layers.
Colour per potential active transmitter number : Each coverage layer displays
area where the number of potential active transmitters is greater than the
user-defined threshold value. There are as many graphical coverage layers as
user-defined potential active transmitters. The potential active transmitter number
corresponds to transmitters checking all conditions to enter the active set. There is
Colour per required power level : Each coverage layer displays area where the
required terminal power (in order for transmitter to get a service) is greater than
9-80

Chapter 9
the user-defined required power thresholds. There are as many graphical

coverage layers as user-defined required power level. There is intersection
between layers.
z
Colour per required power margin : Each coverage layer displays area where
the required power margin exceeds the user-defined threshold value. There are as
many graphical coverage layers as user-defined power margin. The required
power margin corresponds to the difference between the required terminal power
and the maximum terminal power. There is intersection between layers.
Colour per minimum noise level: The displayed noise level is the lowest of the
Colour per average noise level: The displayed noise level is the average of
calculated values on all carriers.
Colour per maximum noise level: The displayed noise level is the greatest of the
Colour per minimum noise rise : The displayed noise rise is the lowest of the
Colour per average noise rise : The displayed noise rise is the average of the
Colour per maximum noise rise : The displayed noise rise is the greatest of the
Colour per polluter number : The coverage displays areas where user is
interfered by pilot signal from polluter transmitters. A polluter transmitter is a
transmitter that meets all the criteria to enter the active set but which is not
admitted due to the active set limit size
9.8.4 CDMA/CDMA2000 Prediction Studies

I. Analysing pilot reception (CDMA/CDMA2000)
This study displays areas where there is at least one transmitter which pilot quality at
receiver (Ec/Io) is sufficient to be admitted in the probe mobile active set [using the
propagation model as defined before (with priority order respect)]. Only the pilot quality
from best server is displayed.
reception analysis (Ec/Io) option from the study types window. The open window is
made of three tab windows : General, Simulation, and Display. An additional
Statistics tab is created after computation. For all of these, use the What's this help to
get description about the fields available in the windows.
9-81

Chapter 9
Finally, you can perform prediction studies without simulation. In this case, U-Net
takes into account UL load and DL total power defined in the Cells properties.
z

probability, or a group of simulations and average option, or, finally, no
simulation.
a cell edge coverage probability (in %).
Note:
z
In the SCH scrolling list, the choice none refers to a null SCH rate.
You must keep consistency between the chosen radio configuration and the
selected SCH rate. For example, take care not to associate a RC1 or RC2 terminal
with a SCH rate different from 0 (2, 4, 8 or 16 in the scrolling list).
are not filled, U-Net considers default values, 50% for UL load percentage and 40
dBm for DL total transmitted power.
Comment:
in folder.
9-82

Chapter 9
z
Note:
z

saturated.

be computed.
II. Studying service area (Eb/Nt) downlink (CDMA/CDMA2000)

This study displays areas where there is one transmitter (or several transmitters in
macro-diversity) which traffic channel quality at the receiver (Eb/Nt or combined Eb/Nt)
is sufficient for the probe mobile to obtain a service [using the propagation model as
defined before (with priority order respect)]. Downlink service area is limited by
maximum allowable traffic channel power.
Comment:
Actually, for a circuit switched service, when there are several transmitters in active set,
Eb/Nt from different transmitters are combined in terminal and improve reception with a
macro-diversity gain.

9-83

Chapter 9
(Eb/Nt) downlink option from the study types window. The open window is made of
three tab windows : General, Simulation, and Display. An additional Statistics tab is
z

Note:
z

9-84

Chapter 9
Comment:
in folder.
specific layer), the surface ((Si)covered stated in km2) where the prediction criterion is
For an environment class i.
z
Note:
z

saturated.

be computed.
III. Studying service area (Eb/Nt) uplink (CDMA/CDMA2000)

This study displays areas where the traffic channel quality of probe mobile at
transmitter (Eb/Nt) is sufficient for the transmitter to get a service [using the propagation
model as defined before (with priority order respect)]. Uplink service area is limited by
maximum terminal power.

9-85

Chapter 9
Comment:
The macro diversity concept is also dealt with on the uplink. Its value depends on the
handover status.
(Eb/Nt) downlink option from the study types window. The open window is made of
three tab windows : General, Simulation, and Display. An additional Statistics tab is
z

simulation.
Note:
z

9-86

Chapter 9
Comment:
in folder.
z
Note:
z

saturated.

be computed.

9-87

Chapter 9
IV. Studying effective service area (CDMA/CDMA2000)

Effective service area is the intersection zone between uplink and downlink service
areas [using the propagation model as defined before (with priority order respect)]. It is
the area where a service is really available for the probe mobile.
To prepare this prediction study, in the prediction creation steps, select the Effective
service area option from the study types window. The open window is made of three tab
windows : General, Simulation, and Display. An additional Statistics tab is created after
z
either a single simulation. or a group of simulations and a user-definable

probability. or a group of simulations and average option. or. finally. no simulation.
a terminal. a mobility (or All). a service (or All).
Note:
z

9-88

Chapter 9
Comment:
in folder.
z
Note:
z

saturated.

be computed.

9-89

Chapter 9
V. Defining handoff status (CDMA/CDMA2000)

This study displays areas [using the propagation model as defined before (with priority
order respect)] where the selected service is available and where probe mobile has in
its active set:
z
Only one transmitter : no handover (1/1)
Two non co-site transmitters : soft handover (2/2)
Two co-site transmitters : softer handover (1/2)
Three non co-site transmitters : soft-soft handover (3/3)
Three transmitters among them two co-site : softer-soft handover (merged with
soft-softer handover) (2/3)
Three co-site transmitters : softer-softer handover (1/3)
Comment:
In parenthesis is given equivalence between usual handover name and HO status
notation sometimes used in U-Net, referring to number of sites/number of transmitters
in the active set (See CDMA/CDMA2000 Simulations Overview).
Note:
z
network.
In this study, handover is allowed on areas where the service chosen by the user is
available.
For each study, a simulation tab enables to connect to one or all simulations.
Furthermore, you can choose different ways of displaying the same coverage to get
a better analysis and dimensioning information on the network.
To prepare this prediction study, in the prediction creation steps, select the handover
status option from the study types window. The open window is made of three tab

9-90

Chapter 9
z

probability, or a group of simulations and average option, or, finally, no simulation
a cell edge coverage probability (in %)
a specific carrier or all the carriers
Note:
z
Comment : for each study, there are as many layers as user-defined thresholds (quality
level, quality margin...). Each layer may be displayed independently by selecting
visibility flag in folder.
Once computations have been achieved, the Statistics tab is available and contains
the detailed results of displayed layers. For each threshold value (corresponding to
a specific layer), the surface ((Si)covered stated in km2) where the prediction criterion is
9-91

Chapter 9
Note:
z

saturated.

be computed.
VI. Studying downlink total noise (CDMA/CDMA2000)

This study enables you to display areas where the total noise (Nt as it is defined in
formulas) exceeds user-defined levels [using the propagation model as defined before
(with priority order respect)].
To prepare this prediction study, in the prediction creation steps, select the Downlink
total noise option from the study types window. The open window is made of three tab

9-92

z
Chapter 9

simulation.
a cell edge coverage probability (in %)
Note:
z
Note:
In case of given service and carrier, the calculated and displayed coverage is the same
for any selected display per noise level (average, minimum or maximum) or any display
per noise rise (average, minimum or maximum).
Comment:
in folder.
9-93

Chapter 9
z
Note:
z

saturated.

be computed.
VII. Calculating pilot pollution (CDMA/CDMA2000)

This study displays the areas where user is interfered by pilot signal from polluter
transmitters [using the propagation model as defined before (with priority order
respect)]. A polluter transmitter is a transmitter that meets all the criteria to enter the
active set but which is not admitted due to the active set limit size.
pollution option from the study types window. The open window is made of three tab
9-94

Chapter 9

z

Note:
z
Representation on map may are given regarding to the number of polluters. Each layer
may be displayed independently by selecting visibility flag in folder.
Comment:
in folder.
9-95

Chapter 9
z
Note:
z

saturated.

be computed.
VIII. Analysing a scenario at a point in CDMA/CDMA2000 projects

To get reception information for a given point on the map, you may use U-Net point
analysis window. Even in CDMA projects, you may use the Profile, Reception and
Results tab windows as for the other projects, on the signal received from the cell pilot.
Concerning pilot quality given by (Ec/Io) (which is the main parameter to enter an active
set) and connection status, with the point analysis tool, U-Net is able to get information
about the active set analysis of a CDMA scenario (for given mobile, mobility and service)
at the receiver location on the map by using the propagation model as defined before
(with priority order respect).
To make active the AS analysis window:
1)
From the menu bar, check the Point analysis command in the View menu.
2)
The point analysis window opens in the lower right corner of your current
environment.
3)
Left click on the AS analysis tab.
4)
Click the
from the toolbar.

9-96

5)
Chapter 9
Move over the current map to the places where you want to make your analysis.
Note:
The Point analysis window is automatically displayed when clicking on the
button
from the toolbar.
Point analysis is a radio reception diagnosis provided for:

z
UL and DL load conditions. Analysis is based on the UL load percentage and the
DL total power of cells. These parameters can be either outputs of a given
simulation, or average values calculated from a group of simulations, or
user-defined cell inputs.
a user-definable probe receiver terminal, a SCH rate and a service.
Pilot quality and connection status (Pilot, Uplink, and Downlink) are displayed for
previous conditions and without taking into account possible network saturation. Thus,
there is no guarantee that a simulated mobile in the receiver conditions can check the
point analysis diagnosis, simply because simulated network may be saturated.
A description of the AS analysis window is given below Figure 9-3.
Figure 9-3 AS analysis window

Bar graph shows pilot reception from all transmitters on the same carrier (with the same
colours as the one defined for each transmitter), displaying limit values required to be in
active set (Ec/Io threshold, T-drop). Grey background displays transmitters in active set.

9-97

Chapter 9
A third vertical bar indicating T-Drop defined in the mobility properties boxes may be
displayed on the AS analysis window.
Reminder: The transmitters taking part in the active set have to check the following
conditions:
They must be using the same carrier.
z
The pilot quality (Ec/Io) from the best server has to exceed the Ec/Io threshold
(defined for each mobility type).
The pilot quality from other transmitters has to be greater than the T-Drop
value (defined for each mobility type).
Other transmitters have to belong to the neighbour list of the best server if you
have selected the restricted to neighbours option (in Global parameters tab).
You may modify receiver characteristics, U-Net will automatically check pilot quality
and channel availability:
z
If you change terminal, it will modify maximum available transmitting power in

uplink and the active set size.
If you change mobility, it will modify pilot quality thresholds and Eb/Nt target per
service in downlink.
If you change service, it will modify the active set size and Eb/Nt target in downlink.
Note:
z
9.9 Specific 1xEV-DO Features

9.9.1 Defining a (Eb/Nt <-> Max rate) Look-Up Table
A default (Eb/Nt Max rate) look-up table is implemented in the tool. Nevertheless, if
there is an U-Net.ini file stored in the U-Net installation directory, U-Net considers
values contained in the file; else, it takes into account default values. So, it is possible to
define a user-defined look-up table giving the relationship between rate and Eb/Nt in an
U-Net.ini file. These values will be used in order to predict 1xEV-DO coverages. You
must create this file and place it in the U-Net installation directory.
The file must have the following syntax:
9-98

Chapter 9
[RatesEbNt]
Values="Rate1 value EbNt1 value Rate2 value EbNt2 value....
Example: Information described below
[RatesEbNt]
Values="38.4 4.5 76.8 4.5 102.6 4.3 153.6 4.5 204.8 4.1 307.2 4 614 4 921.6 4.7
1228.8 5 1843 7.4 2457 8.5"
Corresponds to this look-up table
Rate
Eb/Nt
38.4
4.5
76.8
4.5
102.6
4.3
153.6
4.5
204.8
4.1
307.2
614
921.6
4.7
1228
8.5
1843
7.4
2457
8.5
Note:
This file is read only when U-Net is started. Therefore, it is necessary to close the U-Net
session and to restart it in order to take into account any modification performed in
U-Net.ini.
From rate and Eb/Nt, it is easy to calculate the corresponding C/I using the following
relation:
Eb C W
=
Nt
I
R (in W)
Hence, we get:

9-99

Rate
Chapter 9
Eb/Nt
Corresponding C/I
38.4
4.5
-10.6
76.8
4.5
-7.5
102.6
4.3
-6.5
153.6
4.5
-4.5
204.8
4.1
-3.7
307.2
-2.0
614
921.6
4.7
3.5
1228
8.5
1843
7.4
9.2
2457
8.5
11.5
9.9.2 Creating 1xEV-DO Specific Predictions

This study displays areas according to the C/I level (C/I) or the maximum downlink rate
that can be supported. This study is linked with the definition of a look-up table linking
required (Eb/Nt)and defined rates.
To prepare this prediction study, in the prediction creation steps, select the 1xEV-DO
coverage option from the study types window. The open window is made of three tab
windows : General, Receiver, and Display. For all of these, use the What's this help to
get description about the fields available in the windows.
In this study, each bin of the map corresponds to a probe user with associated terminal
and service. Hence, in the receiver tab, you have to define choose a cell edge coverage
probability (in %), a Radio configuration, a service (or all) and a carrier (or all).
On each bin, U-Net calculates the C/I level. If you have selected a colour per C/I
threshold, it just compares the calculated value to the defined thresholds. In case of a
colour per maximum data rate, U-Net uses the look-up table to determine the
supported maximum data rate. It considers the C/I interval around the calculated C/I
and takes the rate associated to the lower C/I limit. Finally, when choosing a display per
9-100

Chapter 9
Ec/Io, it works out Ec/Io value on each bin and compares it to the defined thresholds.
Different display types are detailed hereafter.
I. Display per C/I level

In the Receiver tab, choose one terminal, the service and one carrier or all of them.
Then, in the Display tab, select Value intervals as display type and C/I as field.
On each bin inside the computation zone, U-Net calculates the C/I level.
Txi
C
PM
=
Txj
I
P M + N term
0
Txj , j i
where,
Tx
M
P max is the transmitter maximum power.
LT is the transmitter-terminal total loss.
is the maximum signal level received from Tx (
Tx
PM =
Tx
P max
Tx
LT ).
Tx
Tx
A bin of the map is coloured if the C/I level exceeds (=) entered thresholds (the bin
colour depends on the C/I level). Coverage consists of several independent layers
which you may manage visibility in the workspace. There are as many layers as defined
thresholds. Each layer corresponds to an area where the C/I level exceeds a defined
minimum threshold.
II. Display per Ec/Io level

Then, in the Display tab, select Value intervals as display type and Ec/Io as field.
On each bin inside the computation zone, U-Net calculates the Ec/Io level.
Ec
C
=
=
Io C + I
Txi
M
Txj
M
+ N term
0
Txj ,i j
A bin of the map is coloured if the Ec/Io level exceeds (=) entered thresholds (the bin
colour depends on the Ec/Io level). Coverage consists of several independent layers
which you may manage visibility in the workspace. There are as many layers as defined
thresholds. Each layer corresponds to an area where the Ec/Io level exceeds a defined
minimum threshold.

9-101

Chapter 9
III. Display per maximum rate

Then, in the Display tab, select Value intervals as display type and Max rate as field.
On each bin inside the computation zone, U-Net calculates the C/I level. To determine
the supported maximum data rate, U-Net uses the look-up table defined in the U-Net.ini
file if it exists or the default table. It considers the C/I interval around the calculated C/I
and takes the rate associated to the lower C/I limit.
A bin of the map is coloured if the rate equals or exceeds entered thresholds (the bin
colour depends on the rate). Coverage consists of several independent layers which
you may manage visibility in the workspace. There are as many layers as defined
thresholds. Each layer corresponds to an area where a maximum rate (threshold value)
is supported.
IV. Other displays

On each bin inside the computation zone, U-Net calculates the C/I level and
determines the corresponding data rate as explained above.
A bin of the map is coloured if the calculated rate equals or exceeds the lowest rate
defined in the U-Net.ini file or the default look-up table (38.4 kbps). Coverage consists
of several independent layers which you may manage visibility in the workspace.
9.10 CDMA/CDMA2000 Resources Allocation

9.10.1 Overview
Once your CDMA/CDMA2000 network is built, U-Net provides you some additional
features in order to complete your network planning by the allocation of neighbour cells
and PN Offsets.
Like in GSM/GPRS/EDGE or UMTS, it is possible to easily allocate neighbours within
U-Net. This can be made either manually, or automatically, imposing several
constraints on the potential cells that could be part of a neighbourhood. Then, once
allocated, neighbours can be easily managed (modification or deletion). Finally, U-Net
makes easy the visualisation of neighbourhoods on the active map.
PN Offsets permit to separate cells from others. It is strongly recommended to assign
different codes to a given cell and to cells belonging to its neighbour list. Some
additional separation constraints can be also defined. In U-Net, you can either allocate
it manually for each cell or automatically for all cells or a group of cells in the network.
Depending on the allocation strategy, several constraints can be imposed on PN
9-102

Chapter 9
Offsets groups and domains, exceptional pairs, distance and neighbours. At any
moment, it is possible to check the consistency of the current PN Offset allocation in the
studied network.
9.10.2 CDMA/CDMA2000 Neighbours

I. Allocating CDMA/CDMA2000 cell neighbours manually
Cell neighbours list represents a way to optimize the search for possible cells aimed to
perform handover from the current coverage area. Allocating neighbours in a network
is optional but makes the handover process easier. Defining neighbours helps in the
determination of appropriate PN Offsets.
Note:
z
Neighbours have impact on interference calculation : all cells in a network interfere

with the others.
Neighbours of any linked project in co-planning can also be displayed and chosen
manually.
Manual allocation of CDMA/CDMA2000 neighbours must be performed for each cell,

one at a time. To do this, proceed as follows in Table 9-27.
Table 9-27 Manual allocation of CDMA/CDMA2000 neighbours
Method
Method 1
step
1)
2)

context menu.
3)
Choose the [Cells\Open Table] command from the open

menu
4)
Once the [cells] table is open,
5)
neighbourhood.
6)

window.
7)
In the displayed window, use the top table. Select the row
with symbol
, then in the Neighbours column, click on
In the scrolling box, U-Net lists all the transmitters located
(cell).

9-103

Chapter 9
Method
Method 2
Method 3
step
8)
Click either another cell of the table, or the

9)
When you have completed your entry, click on OK to close

the dialog box.
1)
2)

context menu.
3)
neighbourhood.
4)

5)
neighbourhood.
6)

window.
7)
with symbol
, then in the Neighbours column, click on
In the scrolling box, U-Net lists all the transmitters located
(cell).
8)

9)

the dialog box.
1)
2)

context menu.
3)
neighbourhood.
4)

command from the Transmitters folder context menu.
5)
In the displayed table, use the row with symbol

. Click
the cell of the Transmitters column to select a reference cell
and then, click the cell of the Neighbours column to choose
a neighbour.
6)
Click another cell of the table to validate and add a new row
to the table.
7)

the dialog box.

9-104

Chapter 9
Note:
z
It is possible to add/remove symmetric neighbourhood links at once. To do this, use

the commands [Symmetries] and [Delete link and symmetric] available in a context
menu. This one can be open by right clicking on the neighbour you have added or
you want to delete.
Due to the organisation of neighbourhoods in tables, the copy-paste feature can be

used in order to generate the neighbour table of a global network (or per cell).
Standard features for managing table contents (Copy/Paste, Delete, Display


technologies.
An automatic allocation tool is also available.
II. Allocating CDMA/CDMA2000 cell neighbours automatically

Allocation algorithm allocating automatically permits to automatically allocate
neighbours globally to active transmitters in the current network by imposing
constraints on active transmitters that must be satisfied. Force neighbour reciprocity,
adjacency and within co-site is possible.
To allocate automatically CDMA/CDMA2000 neighbours in a network, proceed as
follows :
1)
2)
3)
Choose the [Cells/Neighbours/Automatic allocation...] command from the open

menu.
4)
Set the parameters for the current Auto Neighbours allocation study.
5)
Click the
6)
In the Results part. U-Net provides a list of neighbours and the number of
neighbours for each cell. In addition. it indicates allocation reason for each
neighbour. We can have Table 9-28.
Table 9-28 Results
Reason
Description
When
Rank in the list
Forced
Neighbourhood
relationship defined as
exceptional pair
Only if the Force

exceptional pairs option
is selected
Co-site
The neighbour is located
Only if the Force co-site

9-105

Reason
Chapter 9
Description
When
Rank in the list
on the reference cell site
cells as neighbours
option is selected
Adjacent
The neighbour is adjacent

to the reference cell
Only if the Force

adjacent cells as
neighbours option is
selected
% of covered
area
Neighbourhood
relationship that fulfils
coverage conditions
Any time
Symmetric
Neighbourhood
relationship forced in order
to fulfil symmetry
conditions
Only if the Force

neighbour symmetry
option is selected
Existing
relationship
Only if the Reset option

is not selected and in
case of a new allocation
and overlap
area (km2) in
brackets
7)
button to assign
neighbours to cells. Neighbours are listed in the Intra-technology Neighbours tab

of each cell Properties window.
8)
Click the <Close> button to achieve the proceed .

9-106

Chapter 9
Note:
z

technologies.
No prediction study is needed to perform the automatic neighbour allocation. When

starting an automatic neighbour allocation, U-Net automatically calculates the path
loss matrices if it does not find them.
You can carry out neighbour allocation globally on all the cells or only on a group of
cells. In this case, U-Net will consider all the cells contained in the group of
transmitters, the symmetric neighbours of these cells and all the other ones, which
have an intersection area with the cells of the group.
If the Reset button is unchecked and no new neighbour is found after a new
allocation calculation, the Results part stays empty. Nevertheless, existing
neighbours (from a previous allocation) are kept as before. U-Net only displays the
cells for which it finds new neighbours. Therefore, if a cell has already reached its
maximum number of neighbours before starting the new allocation, it will not appear
in the Results table.
III. Displaying current CDMA/CDMA2000 neighbour list

U-Net provides the possibility to open an editable table referencing all the
CDMA/CDMA2000 neighbours of the current network.
To access the CDMA/CDMA2000 neighbour table, proceed as follows:
1)
2)
3)
Choose the [Cells/Neighbours/Intra-technology Neighbours] command from the

open menu.
4)
In the displayed table. U-Net lists reference cells and their related neighbours. In
addition. it indicates the number of neighbours assigned to each reference cell.
and for each neighbour:
The distance between the neighbour and the reference cell.

imported (Planet import, generic import, import using an add-in).
The neighbour rank in the list of neighbours of the reference cell. This information
is given only in case of an automatic allocation.

allocation.

9-107

Chapter 9
This table can be used to allocate neighbours manually. Standard features for
managing table contents (Copy/Paste, Delete, Display columns, Filter, Sort, Table
Fields) are available in a context menu (when right clicking on column(s)) or record(s)
and in the Format, Edit and Records menus.
IV. Deleting the allocated CDMA/CDMA2000 neighbours

You may add new neighbours or remove allocated neighbours.
To delete allocated neighbours, proceed as follows Table 9-29.
Table 9-29 delete allocated neighbours
Method
Method 1
step
1)
2)

context menu.
3)
Choose the [Cells/Open Table] command from the open

menu
4)
Once the cells table is open,
5)
neighbourhood.
6)

7)
Click the Intra-technology [Neighbours] tab from the

current window.
8)
In the displayed table, select the desired neighbour row.
9)
10) Click on <OK> to validate and close the dialog box.

Method 2
Method 3
1)
2)

context menu.
3)
neighbourhood.
4)
Click the Intra-technology [Neighbours] tab from the

current window.
5)
6)
7)
1)
2)

context menu.
3)
Choose
the
[Cells/Neighbours/Intra-technology
Neighbours] command from the open menu.
4)
5)

9-108

Chapter 9
Method
step
6)
Note:
It is possible to remove symmetric neighbourhood links at once. To do this, use the
command [Delete link and symmetric] available in a context menu. This one can be
open by right clicking on the neighbour you want to delete.
V. Displaying CDMA/CDMA2000 neighbours on the map

Once the CDMA/CDMA2000 cell neighbours have been allocated, you can display a
given neighbourhood (at the transmitter level) on the map.
To display the neighbours of any transmitter (whatever the carrier is), proceed as
follows :
icon from the toolbar.
1)
Click on the Neighbour graphic management
2)
Left click on the desired transmitter to select it on the map.
3)
U-Net displays on the map Figure 9-4).
The symmetric neighbourhood links with the selected transmitter (reference

transmitter). A single black line represents these links.
The outwards neighbourhood links (which are not symmetric); they are
coloured as the reference transmitter. They show the neighbours of the selected
transmitter (however, the selected transmitter is not one of their neighbours).
The inwards neighbourhood links (which are not symmetric). They show the
transmitters, which have the selected transmitter as neighbour (however, these
transmitters are not in the neighbour list of the selected transmitter). Each link has
the transmitter colour.

9-109

Chapter 9
Figure 9-4 for the transmitter Site0_2 located on Site 0
Note:
z
It is possible to configure the neighbourhood links you wish to display on the map
and to display neighbourhood relationships on a given carrier you may select. To do
this, right click on the transmitters folder and choose the [Neighbours/Display
options...] command from the open menu.
Finally, when you select a transmitter on the map, U-Net is able to show the
coverage areas of its neighbours. You must just display on the map a Coverage by
transmitter study (with a colour display by transmitter) preliminary calculated.
9.10.3 PN Offsets
I. Overview
512 PN Offsets are available. They are distributed in 64 clusters of 8 PN Offsets.
Clusters are numbered from 0 to 63. PN Offsets are numbered from 0 to 511.
Available PN Offsets depend on the country and on the area; it is necessary to
distinguish borders from other zones. To model this, domain and group tables have
been created.
z
A domain corresponds to a border or a zone of the country.
A group is a set of clusters.

9-110

z
Chapter 9
Each group must be associated to one or several domains. Therefore, a domain

consists of several groups.
Firstly, PN Offsets can be manually assigned to any cell of a CDMA/CDMA2000

network. Then, using the definition of groups and domains, it is possible to impose
some constraints on them and on neighbours, second neighbours, minimum distance
and exceptional pairs to start the automatic tool.
Once allocation is completed, a Audit tool is available.
II. Creating pn offsets domains and groups

512 PN Offsets are available. They are distributed in 64 clusters of 8 PN Offsets.
Clusters are numbered from 0 to 63. PN Offsets are now numbered from 0 to 511.
To define domains and groups of PN Offsets, proceed as follows Table 9-30.
Table 9-30 define domains and groups of PN Offsets
Method
Method 1
Method 2
step
1)
2)

context menu.
3)
Choose the [Cells/PN Offsets codes/Domains...] command

from the open menu.
4)
In the Domains dialog, you can enter a domain per line. To

validate a domain creation, select another line.
5)
Select a domain in the table and click on the Properties...

button.
1)
2)

context menu.
3)
Choose the [Cells/PN Offsets codes/Domains...] command

from the open menu.
4)
In the Domains dialog, you can enter a domain per line. To

validate a domain creation, select another line.
5)
Select the line relating to a domain and double click on it.
In the domain properties dialog, specify the name of group(s) that you want to
associate to this domain and define for each of them:
z
The lowest available PN Offsets (Min).
The highest available PN Offsets (Max).
The value interval between the PN Offsets (Step).
The PN Offset(s) you do not want to use (Excluded). You can paste a list of PN
Offsets; separator must be a blank character.
9-111

z
Chapter 9
Additional PN Offset(s) you want to consider during allocation (Extra). You can
paste a list of PN Offsets; separator must be a blank character.
You can also define the domain-group pairs in the Group of PN Offsets window.
To do so, proceed as follows :
1)
After defining all the domains, close the Domains dialog.
2)
3)
Choose the [Cells/PN Offsets/Groups...] command from the open menu.
4)
In the Group of PN Offsets window, select a domain and associate one or several
groups of PN Offsets to each of them. Define the groups as explained above.
The defined domains can be now assigned to cells in order then to be used as
constraints in the automatic allocation of PN Offsets.
III. Assigning a pn offset domain to a cell

After having defined domains and groups, you can assign a domain to each cell.
Therefore, U-Net will choose PN Offsets of the associated domain during allocation.
To assign a domain to cells, you must access cell properties and fill the appropriate field.
This can be made either from :
z
The cell table.
The domain association will then be used by the automatic allocation tool.
IV. Allocating pn offsets to CDMA/CDMA2000 cells manually

U-Net allows you to manually force PN Offsets for cells of your network. Hence, these
can be locked in order to be kept unchanged by the automatic tool.
To give a PN Offset to a cell, you must access cell properties. This can be made either
from :
z
The cell table.
After allocation is completed (manually or automatically), constraints can be also

checked also by an automatic tool.
V. Defining exceptional pairs for pn offset allocation

In addition to standard constraints (reuse distance, neighbours and domains), it is
possible to specify pairs of cells, which cannot have the same PN Offset. You can enter
these forbidden pairs in the Exceptional separation constraints table.
9-112

Chapter 9
To access the Exceptional pairs table, proceed as follows:

1)
2)
3)
Choose the [Cells/PN Offsets/Exceptional pairs...] command from the open menu.
4)
In the Exceptional separation constraints dialog, indicate the pairs of cells.
Display columns, Filter, Sort, Table Fields) are available in context menu (when right
clicking on column(s) or record(s)) and in the Format, Edit and Records menus.
VI. Allocating pn offsets to CDMA/CDMA2000 cells automatically

You can carry out PN Offsets allocation on all the cells or only on a group of cells. In this
case, U-Net will consider all the cells defined in the group of transmitters.
PN Offset allocation is based on:
z
Neighbourhood and secondary neighbourhood if neighbour allocation has been

performed beforehand.
Reuse distance.
Domains of PN Offsets.
Forbidden pairs.
PN Offset automatic allocation can also be made on a specific carrier or on all. U-Net
assigns PN Offsets to transmitters using the selected carrier.
To automatically allocate PN Offsets to all the cells, proceed as follows :
1)
2)
3)
Choose the [Cells/PN Offsets/ Automatic allocation...] command from the open
menu.
In this dialog, you can impose to the algorithm to take into account :
z
The existing neighbours listed in the Neighbours table (option Existing

neighbours) : A cell and its neighbours cannot have the same PN Offset. The
neighbours of the cell cannot have the same PN Offset.
The neighbours of listed neighbours (option Second neighbours): A cell and the
neighbours of its neighbours cannot have the same PN Offset. In addition, all the
neighbours (first neighbours and second neighbours) cannot have the same PN
Offset.
Note:
U-Net automatically selects the option Existing neighbours when choosing the option
Second neighbours.

9-113

Chapter 9
A criterion on Ec/Io (option Additional Ec/Io conditions) : All the cells fulfilling Ec/Io
condition will not have the same PN Offset.
When this option is selected, you must specify a minimum threshold (minimum Ec/Io), a
margin (Ec/Io margin) and a cell edge coverage probability. In this case, for a reference
cell A, U-Net considers all the cells B that can enter active-set on the area where the
reference cell is the best server (area where (Ec/Io)A exceeds the minimum Ec/Io and
is the highest one and (Ec/Io)B is within a Ec/Io margin of (Ec/Io)A).
Note:
U-Net takes into account the total downlink power used by the cell in order to evaluate
Io. Io equals the sum of total transmitted powers. In case this parameter is not specified
in the cell properties, U-Net uses 50% of the maximum power.
A reuse distance : radius within which two cells on the same carrier cannot have the
same PN Offset.
1)
Select one carrier or all on which you want to run the allocation.
2)
Select the Reset all PN Offsets option to delete the existing PN Offsets and carry
out a new PN Offset allocation. If not selected, existing PN Offsets are kept.
3)
4)
Then, <click> on <Commit> to assign PN Offsets to cells.
To automatically allocate PN Offsets to a group of cells, proceed as follows :

1)
2)
Right click on the group of transmitters folder to get the related context menu.
3)
Choose the [Cells/PN Offsets/Automatic allocation...] command from the open

menu.
4)
Select calculation options (as defined above) in the dialog.
5)
6)
Then, click on <Commit> to assign PN Offsets to the group of cells.
Note:
U-Net will take into account both real distance and the azimuths of antennas to
calculate the inter-transmitter distance to be compared with the reuse distance.

9-114

Chapter 9
VII. Pn offset allocation process

Algorithm works as follows:
z
U-Net assigns different PN Offsets to a given cell i and to its neighbours.
For a cell j which is not neighbour of the cell i, U-Net gives it a different PN Offset.
If the distance between both cells is lower than the reuse distance.
If the cell i -cell j pair is forbidden.
When the Second neighbours option is checked, a cell and the neighbours of its
neighbours cannot have the same PN Offset. In addition, all the neighbours (first
neighbours and second neighbours) cannot have the same PN Offset.
U-Net allocates PN Offsets starting with the most constrained cell and ending with
the lowest constrained one. The cell constraint level depends on its number of
neighbours and whether the cell is neighbour of other cells. Here, the neighbour
term includes both manually specified or automatically allocated neighbours and
cells, which are within the reuse distance of a studied cell. When cells have the
same constraint level, cell processing is based on order of transmitters in the
Transmitters folder.
Note:
In order to calculate the effective inter-transmitter distance (which will be compared to
the reuse distance), U-Net takes into account both real distance and azimuths of
antennas. For further information, please, refer to Technical reference guide.
The PN Offset choice depends on domains associated to cells and on the selected
allocation strategy. When no domain is assigned to cells, U-Net uses the 512 PN
Offsets. Several scenarios are detailed hereafter:
Let us consider 10 PN Offsets to be allocated.
z
1st case: We assume that any domain is assigned to cells. Here, U-Net will be able
to use the 512 PN Offsets.
U-Net will choose eight codes in the cluster 0 and two PN Offsets in the cluster 1.
Therefore, the allocated PN Offsets will be 0, 1, 2, 3, 4, 5, 6, 7, 8, 9.
2nd case: We assume that the domain 1 is associated to cells. Domain 1 contains
two groups, the group 1 consisted of cluster 0 (available PN Offsets: 0 to 7) and
the group 2 including clusters 2 and 3 (available PN Offsets: 16 to 31).
U-Net will choose eight PN Offsets in the group 1 and two other ones in the group 2
(the first two PN Offsets of the cluster 2). So, allocation result will be 0, 1, 2, 3, 4, 5, 6,
7, 16, 17.
9-115

Chapter 9
3rd case: We assume that the domain 1 is associated to cells. Domain 1 contains
one group, the group 1 consisted of cluster 1 (available PN Offsets: 8 to 15). As

there are not enough PN Offsets available in the group 1, U-Net does not allocate
any PN Offsets and displays an error message PN Offsets allocation failed.
VIII. Checking the consistency of the pn offset assignments

A checking algorithm is available. It enables you to examine if there are some
inconsistencies after having manually performed some changes.
To use the checking algorithm, proceed as follows:
1)
2)
3)
Choose the [Cells/PN Offsets/Audit...] command from the open menu.
4)
In the PN Offset checking window, select the allocation criteria that you want to
check as follow Table 9-31.
Table 9-31 PN Offset checking window

criteria
step
Neighbourhood
checking is carried out on the neighbour cells (listed

in the Neighbour tab); they must not have the same
PN Offset,
Second order
neighbours
A cell and the neighbours of its neighbours do not

have the same PN Offset.
All the neighbours (first neighbours and second
neighbours) do not have the same PN Offset.
Exceptional pairs
checking is performed on the forbidden pairs of cells;

they must not have the same PN Offset.
Reuse distance
checking concerns cells which inter-transmitter

distance is lower than the reuse distance you can
define; they must not have the same PN Offset.
Domains
U-Net checks if the allocated PN Offsets belong to

the domain assigned to the cells.
5)
Click on <OK> to <start> the checking algorithm.
U-Net details the checking results in a report. This report is a text file called
CodeCheck.txt; it is stored in the temporary folder on your workstation. For each
selected criterion, U-Net gives the number of detected inconsistencies and details each
of them.
For criteria 1, 2, 3 and 4, it displays the name of cells and the common PN Offset. In
case of criterion 5, it lists the name of cells, which do not satisfy the criterion, the
associated domains and the allocated PN Offsets.

9-116

Chapter 9
IX. Displaying the reuse of pn offsets on the map

Standard display features available at the transmitter and prediction study levels may
be used in order to know the distribution of PN offsets on the map. In addition, grouping
features of transmitters are available; they enable you to regroup in explorer the
transmitters which cells have the same scrambling code. Therefore, It is possible:
z
To give a colour to transmitters depending on the assigned PN offsets.
To display the assigned PN offsets in labels or tip balloons.
To colour the service area of transmitters depending on the assigned PN offsets.
To group transmitters by PN offset.
Note:
transmitter has more than one cell, U-Net does not know the carrier to be considered.
In this case, no value is collected (#).

9-117

Chapter 10 Managing Measurements

10.1 Managing Measurements Overview
In U-Net, the measurement module provides two types of drive tests: CW
measurements and Test mobile data.
The aim of CW measurements is to analyse measurements made on the real field
referring to only one transmitter (at a given frequency - Continuous Wave) in order to
calibrate propagation models. Test mobile data refer to measurements related to
several servers, each point referring to a serving cell and to a list of neighbours. The
goal of test mobile data is to check and to improve the quality of an existing network.
The creation of CW measurements in U-Net is very easy and can be made either by
importing measurements or general data samples (even from PlaNET data) or by
pasting measurement results. The way CW measurements are imported can be
managed in configurations which permits the user to make easier import procedures. In
addition, the multiple imports of CW measurement files are supported. It is also
possible to create paths to define a set of points where a prediction calculation can be
performed.
The management of any CW measurement path is very complete and provides several
features concerning, for example, the update of geo data, user-defined additional fields,
and the display of any path in a generic way.
By using the features which compares imported measurements values and U-Net
prediction calculation results, you can apply measurements import either to select the
best suited model or, more accurately, to refine the parameters of the selected model.
Furthermore, it is possible to add predictions from other transmitters on any CW
measurement path.
The CW Measurements window allows you to analyse both measurement and
prediction fields very precisely using the point analysis tool. It is also possible to
synchronise the analysis of a CW measurement path both in the table, on the map and
on the specific CW measurement window.
It is possible the export path and measurement results in order to make them
available in other application.
The creation of Test mobile data path is possible by importing ASCII text or TEMS files
for any type of technology. All the information contained along the considered path can
be listed in a manageable table and be used for analysis in a specific test mobile data
window.

10-1

Like for the CW measurements, import configuration and multiple imports is supported
on test mobile data files. In addition, all other classical features concerning the
properties of any test mobile data path have been implemented (filters, display, export
in a vector file, management at the folder level, synchronisation between the specific
test mobile data window, the map and the related data table).
10.2 CW Measurement Data Paths

10.2.1 Creation of a CW Measurement Path
I. Creating a CW measurement session
In U-Net, CW measurements sessions are sorted as sites or transmitters, i.e., in folders
in the Data tab explorer window. Because a CW measurement session refers to a main
transmitter, U-Net groups the imported or created CW measurement paths by
transmitter. Like other objects organized in folders in U-Net, these are easily
manageable. So, to reach a specific CW measurement session, expand both CW
measurements and reference transmitter folders by clicking the
with the
buttons (or contract
buttons).
CW Measurements folder global properties are reachable from the associated context
menu (right click on the CW measurements folder).
To create a CW measurement session, proceed as follows:
1)
Click the Data tab in the Explorer window.
2)
Right click on the CW Measurements folder to open the associated context menu.
3)
4)
A CW measurement session properties box is open.
5)
window.
6)
Give a name to the CW measurement path.
7)
Specify the transmitter name which the CW measurements have been performed
around.
8)
Indicate the transmitter frequency, the receiver height and the gain of receiver
antenna.
9)
Define the reception unit compatible with CW measurements.
When this is made, you may edit the open CW measurement table, paste values in it, or
create a CW measurement path.

10-2

Note:
z
To establish the CW measurement session, you must link it with a transmitter for the
measures to be based on.
Features available in the CW Measurement folder context menu are also offered in
each group context menu. Therefore, you can add a new CW measurement path in
a group using New and Import commands and define unique prediction, statistics
and display settings for all the paths available in a group thanks to the Properties
command.
II. Pasting a CW measurement path

During a CW measurement session creation, you may paste the coordinates of a path
and, eventually, its associated CW measurement values. This procedure is useful if
your CW measurements are stored in a spreadsheet (Excel, Word). Coordinates to be
pasted refer to the display coordinate system currently defined.
To do this, proceed as follows:
1)
Make displayed the New CW measurement session window.
2)
Use the What's this help to get description about available fields in the open
dialog window.
3)
Open the spreadsheet where your CW measurement file is stored.
4)
Select X and Y coordinates and CW measurements to be imported and copy

them with either the Ctrl+V command or the Copy command from the Edit menu.
5)
Switch to the open New CW measurement session window.
6)
Precise the paste data reception unit.
7)
Click on the
8)
Click OK to validate.
button.
Note:
If you paste only the X and Y coordinates, CW measurement values are set to 0 along
the associated path. If CW measurements are not included at this time, you will not be
able to do it next.
III. Drawing a CW measurement path

When a CW measurement session has been defined, you can create a CW
measurement path on the current map by simply using the mouse. You can either put

10-3

CW measurement points one by one, or draw a path with equal distance separating
each CW measurement point.
To add points in a CW measurement session, proceed as follows:
1)
2)
Expand the CW Measurements folder by left clicking on the
3)
Expand the Reference transmitter folder by left clicking on the
4)
Right click on the CW measurement session you want to add CW measurement
button.
button.
points.
5)
Choose the add points... option from the context menu.
6)
Left click on the map with the
pointer where to put the appropriate location for
the CW measurement points.

7)
Press the 'Esc' button on your keyboard or double click to finish the current points
adding.
To add a path in a CW measurement session, proceed as follows:

1)
2)
3)
4)
Right click on the CW measurement session you want to add CW measurement
button.
button.
points.
5)
Choose the add path... option from the context menu.
6)
Precise the length step separating two consecutive CW measurement points.
7)
Left click on the map with the
8)
Press the 'Esc' button on your keyboard or double click to finish the current path
pointer for each CW measurement path corner.
building.
Note:
Adding points or adding a path is available only when no measures values have been
imported in the current CW measurement session. Nevertheless, you may add points
to any other CW measurement session.
Caution:
These functions cannot be used to modify the imported CW measurement.

10-4

IV. Importing a CW measurement path

In U-Net, you may import CW measurement text files with .dat, .txt and .csv extensions.
To do this, proceed as follows (see Table 10-1):
Table 10-1 Importing a CW measurement path
No.
Step
Detail
1)
2)
Open CW measurement
import window
3)
4)
5)
Click
1)
Check that you have chosen the right

configuration. You may change it: click on
the Configuration scrolling menu and select
another one.
Check also the import setting automatically
provided by the configuration.
You can change some parameters in the
File part such as the number of the first CW
measurement line, the list separator ( ,
tab, ;) and decimal symbol (, or .)
used in the file to be imported.
Give a correlation between the displayed
columns
and
U-Net
internal
CW
measurement fields by either clicking on
each cell in the Field line and then,
selecting a field in the list or by clicking on
the Setup button. In the last case, the CW
Measurement setup window, where three
U-Net internal fields, X, Y and CW
measurements, are listed, is displayed. The
X and Y fields have to be assigned unlike
the CW Measurements field which is
optional.
2)
3)
Click on the Setup tab
4)
1)
2)
3
Open the General tab
3)
4)
Click on the
button to achieve the
import CW measurement
procedure.

Right click on the CW Measurements folder
to open the associated context menu.
Left click in the scrolling menu on Import....
Specify the path, name and the format of
the file to be imported in the open window.
Indicate the CW measurement name.

Specify the name of transmitter on which
the CW measurements refer to
Enter the transmitter frequency, the
receiver height, the gain and losses of the
receiver antenna.
Define the unit of CW measurement and
the coordinate system of CW measurement
points,

10-5
to validate your choice,

Using this procedure, you may also import general data (location names, field
characteristics, etc...) along the imported CW measurement path, if the extra data has
the same format as the imported coordinates and CW measurement data. To achieve
this, you just have to select the appropriate format in the cell type in each column.
When this is done, data are available to be displayed on the map with the CW
measurement points.
Note:
z
To establish the CW measurement session, you must link it with a transmitter for the
measures to be based on.
When the CW measurement file to be imported contains fields, which the name
corresponds to name of a U-Net internal field (e.g. field Distance), U-Net imports
the field but changes its name to differentiate it. In fact, U-Net ends the imported
field name with (file) (e.g. field Distance (File)).
When the imported file contains fewer lines than the defined number of the first CW
measurement line, U-Net warns you the current configuration will be applied with a
reinitialisation of the first CW measurement line number to 1.
With configuration, it is possible to import several CW measurements at the same

time.
You can optionally import a CW measurement path to existing reference transmitter

folders. To do that, follow the procedure above, but reach the reference transmitter
folder (instead of the CW Measurement folder only) by expand the CW
Measurements folder by left clicking on the
button.
V. Importing several CW measurement paths

There are two solutions in order to import several CW measurement files at once.
The first way is the file multi-selection. To do this, proceed as follows:

1)
Follow the standard steps of the import CW measurements procedure, select

several files in the Open window.
Either,
2)
In the Open window, optionally specify an import configuration in the "Files of

type" scrolling box" in order to filter only files respecting the format defined in the
considered configuration.
3)
Select the files you want to import simultaneously (multi-selection is possible by

using the 'Shift' key.
4)
Click the
button.
Or,
10-6

2)

3)
Click the
4)
The import CW measurements window opens.
5)
Optionally specify an import configuration (Configuration part) that will be
button.
consistent with the format of the files being imported.

Then
1)
In that case, you may import several CW measurement files based on the same
transmitter and with the same associated configuration. In this case, you just need
to indicate the transmitter and the configuration once.
2)
Click on the
all button: all the paths will be imported at the same
time.
Note:
z
If the selected CW measurement files are based on several transmitters and/or

have different configurations, you cannot use the
button. For each
file, indicate a transmitter and/or a configuration and then, click the

button.
z
When using the Import all button, U-Net does not import files for which the
configuration does not correspond to the selected one. It displays an error message
and goes on the import with next file.
It is also possible to import in one shot surveys related to different transmitters and/or
different configurations by the mean of an index file containing information usually
entered through the GUI (see Table 10-2):
Table 10-2 U-Net Measurement Index File Format
Column name
Description
File
File name
Transmitter
Transmitter name (must be in the Transmitters folder of

the .atl document)
Freq (MHz)
Transmitter frequency (default is the central frequency of the

main frequency band associated to the transmitter, if not
found it is 1000 MHz)

10-7

Column name
Description
Units
Reception unit (default is the global reception unit available

in the Option dialog (dBm, dBV, dBV/m)
Coordinates
Coordinate system code (default is the code of the

coordinate system selected as the Display system in the
Options dialog, the code is available in the system
properties)
Height(m)
Receiver height (m) (default is the receiver height defined in

the Predictions folder properties).
Gain(dB)
Receiver gain (dB) (default is 1 dB)
Losses(dB)
Receiver losses (dB) (default is 0 dB)
Configuration
Configuration name (must already exist in the U-Net

document)
Important:
z
The index file must be named xxx.ami (U-Net Measurement Index).
The first line must contain the titles of the columns, with the exact column names
listed above. Information in bold is mandatory.
Both examples show the content of an AMI file.

z
Example 1 shown in Table 10-3.
Table 10-3 Example 1

File
Transmitter
Configuration
Railways.txt
Site0_0
conf_1
Highway1.txt
Site1_1
conf_2
Highway2.txt
Site2_0
conf_3
Example 2 shown in Table 10-4 and Table 10-5.
Table 10-4 Example 2 (1)

File
Transmitter
Freq(MHz)
Units
Coordinates
Railways.txt
Site0_0
935
dBm
27595
Highay1.txt
Site1_1
935
dBm
27595
Highway2.txt
Site2_0
935
dBm
27595

10-8

Table 10-5 Example 2 (2)

File
Height(m)
Gain(dB)
Losses(dB)
Configuration
Railways.txt
conf_1
Highay1.txt
conf_2
Highway2.txt
1.5
conf_3
When importing the AMI file, U-Net displays its content and highlights errors (file not
found, transmitter not found, configuration not found) (see Figure 10-1). Yellow lines
contain erroneous information; wrong information is displayed in red. It is possible to
correct the errors and apply in the import dialog, to take into account new information
without modifying the AMI file.
Figure 10-1 Import parameters errors

Import of an AMI file: the transmitter Site6_3 is not available in the U-Net document. By
clicking in the red cell, the user can correct the error. When the import is successful,
U-Net automatically creates one CW Measurement subfolder for each imported
transmitter.
VI. Adding predictions on existing CW measurement paths

Since a CW measurement path is mainly related to a given transmitter, only the signal
measured from this transmitter can be studied and compared with predictions along the
path. Nevertheless, it is possible, in U-Net to get predictions of signal received from
other transmitters along the path.
To add a prediction from another transmitter, proceed as follows:
1)
Access the CW measurement path you want to add a transmitter.
2)
Right click on the CW measurement path in order to open the associated

context menu.
3)
Select the Properties command from the open menu.
4)
Use the What's this help to get description about the fields available in the current
dialog.

10-9

5)
In the Properties dialog, open the Parameters tab, Click the

button and choose the Add a prediction... command from the open menu.
6)
In the New prediction dialog, click on the Transmitter scrolling menu and
choose a new transmitter, which the prediction will refer to.
7)
Click OK to achieve the transmitter addition.
The new transmitter becomes available in the CW measurement session table as a

new column. Computations using this transmitter are made in the same way as
computations on classical reference transmitter for a CW measurement path.
Note:
z
Like for classical single transmitter CW measurement sessions, computations along

the CW measurement paths are possible with several transmitters.
To delete columns related to additional transmitters, delete the related field in the
table management dialog (Table tab) of the considered CW measurement session.
VII. Creating an import CW measurement configuration

In U-Net, import CW measurement configurations can be defined in order to make
easier some future import procedures based on the same model as a reference one.
Moreover, configurations may be useful to import several CW measurement data set at
once.
To create an import CW measurement configuration, you must use the generic
import feature. When the import CW measurements windows are open, proceed as
follows (see Table 10-6):
Table 10-6 Creating an import CW measurement configuration
Step
Detail
Define configuration
characteristics in the Setup tab
You can change some parameters in the File part

such as the number of the first CW measurement
line, the list separator ( , tab, ;) and decimal
symbol (, or .) used in the file to be imported,
Give a correlation between the displayed columns
and U-Net internal CW measurement fields by
either clicking on each cell in the Field line and
then, selecting a field in the list or by clicking on
the Setup button. In the last case, the CW
Measurement setup window, where three U-Net
internal fields, X, Y and CW measurements, are
listed, is displayed. The X and Y fields have to be
assigned unlike the CW Measurements field which
is optional.

10-10

Step
Detail
In the Configuration part, enter the extension (e.g.
*.txt) for the files that will be considered (and
filtered) with this configuration.
button and enter a name
Click the
for the current configuration. Click OK to save the
import configuration.
Indicate the CW measurement path name.
Specify the name of transmitter on which the CW
measurements refer to.
Open the General tab
Enter the transmitter frequency, the receiver

height, the gain and losses of the receiver
antenna.
Define the unit of CW measurement and the
coordinate system of CW measurement point.
Click on the
button to achieve the
import CW measurement procedure.
Note:
z
Configuration is saved as soon as you click on the Save button. It is not necessary
to complete the import procedure (by pressing the Import button).
When importing a CW measurement file, the existing configurations are available in

the Files of type scrolling menu (Open window). They are sorted according to their
creation order. During import, if U-Net recognises the extension, it automatically
proposes the corresponding configuration. In case several configurations are
associated with an extension, U-Net chooses the first configuration in the list.
When importing a CW measurement file, of course, the existing configurations are

also available in the Configuration scrolling box of the Setup tab of the import CW
measurement data file dialog. When selecting the appropriate configuration,
correspondences are automatically set.
The defined configurations are stored in the file MeasImport.ini. This file is located
in the directory where U-Net is installed. You can copy it on other workstations (in
the directory where U-Net is installed) in order to make available the configurations.

10-11

Caution:
z
It is no longer necessary to define a projection coordinate system to be able to

import a CW measurement path. However, in order to avoid some inconsistencies,
you must specify it in case the CW measurement points are stated in a geographic
coordinate system.
In order to avoid some inconsistencies, do not assign the *.* extension to a

configuration.
VIII. Deleting an import CW measurement configuration

In U-Net, Import CW measurements configurations can be defined in order to make
easier some future import procedures based on the same model as a reference one.
Moreover, configurations may be useful to import several CW measurement data set at
once.
To delete an import CW measurement configuration, you must use the generic
import feature. When the import CW measurements window is open, proceed as
follows:
1)
Click on the Setup tab.
2)
In the Configuration part, click on the Configuration scrolling list.
3)
Choose the configuration you want to remove.
4)
Click on the
button.
Another solution is to open the file MeasImport.ini (located in the directory where
U-Net is installed), select and erase the configurations that you want to remove.
10.2.2 Management of a CW Measurement Path

I. Defining CW measurement path properties
In U-Net, CW measurements sessions are organized in items located in reference
transmitter folders.
CW Measurements folder global properties are reachable from the associated context
menu (left click on the CW measurements folder).
Measure sessions properties are reachable from CW measurements folders
associated context menus (left click on the CW measurements folders).
To manage the properties of an existing CW measurement path, proceed as follows:
1)
2)

10-12
button.

3)
4)
Right click on the CW measurement session you want to manage properties.
button.
5)
6)
window.
The dialog is made of 4 tabs (General, Parameters, Table, and Display) in which you
can respectively manage:
z
The CW measurement conditions.
The General tab contains information on the receiver and the header of the imported
file.
z
Predictions and related filters over the CW measurement path.
Predictions are used for comparison between real CW measurement and prediction
using the propagation model to be calibrated. Filter features enable you to limit the CW
measurement data points listed in the table and displayed on the map.
z
The CW measurement table content,
The table tab works like all the other ones, with the standard features on how to
manage the contents of any table. It is possible to add new attribute in the table.
z
The display of the CW measurement points composing the path.
Note:
In the parameters tab, when clicking the
button, the Refresh geo data
command enables you to update heights (Alt DTM, Clutter height, DTM+Clutter) and
the clutter class of CW measurement points after adding new geographic maps or
modifying existing ones.
II. Opening a CW measurement table

All the CW measurement points of a path, attributes, predictions and the error are listed
in related table.
To open this table, proceed as follows:
1)
2)
3)
button.
button.
Either,
4)
Right click on the CW measurement session you want to open the related table.
5)
Choose the Open Table command from the context menu.

10-13

Or,
4)
Double click on the CW measurement session you want to open the related
table.
Standard features for managing table contents (Copy/Paste, Fill up/down, Delete,
Display columns, Filter, Sort, and Table Fields) are available in a context menu (when
You can also access the table content management from the Table tab of the CW
measurement session property dialog.
III. Predicting signal levels on a CW measurement path

In U-Net, it is possible to make predictions along a CW measurement path, using the
reference transmitter for the current CW measurement session, and potentially added
one. This feature is possible using any prediction model along an existing CW
measurement path, either created from a spreadsheet, from a drawing of points or
paths, or from a data import. The goal of this feature will be to play on the propagation
model parameters with a view to calibrate it.
To open the prediction window associated with the current CW measurement
session, proceed as follows:
1)
2)
3)
4)
button.
button.
Right click on the CW measurement session you want to predict coverage on CW

measurement path.
5)
6)
Click on the Parameters tab.
7)
window.
8)
When prediction parameters are set (filter + selection of a propagation model),

button and choose the Calculate predictions command
Click the
from the open menu to start calculation.

9)
Statistics between CW measurement and predictions are automatically displayed

in a new window.
10) Results are then available in the CW measurement session table.

10-14

Note:
z
This feature allows you also to predict signal level of added transmitters in an
existing CW measurement path.
It is also possible to use the path loss stored in the path loss matrices if they have
been previously calculated for prediction studies (select Path loss matrices instead
of a propagation model). In this case, the prediction values on the CW measurement
path are just extracted from path loss matrices.
When a transmitter is made of several elements for which it is possible to define

several powers (TRX types in GSM/GPRS/EDGE, cells in UMTS or
CDMA/CDMA2000), U-Net computes using the highest power level (e.g. BCCH in
GSM/GPRS/EDGE)
When using the
button, The Refresh geo data command update
heights (Alt DTM, Clutter height, Clutter+DTM) and clutter class of CW

measurement points after adding new geographic maps or modifying existing ones,
and recalculates predictions to take into account modifications (Calculate
predictions command).
IV. Filtering points along CW measurement paths

When predicting along CW measurement paths, it is possible to impose some filter.
This can be made in the Filter part of the Parameters tab of any CW measurement
session property dialog; you may specify filter criteria on (see Table 10-7):
Table 10-7 Filtering points
Parameter
Operation
Description
Distance between
CW measurement
point and reference
transmitter
Enter minimum and maximum

distances (Min distance and
Max distance) in respective
boxes.
U-Net will keep only CW

measurement points which
distance from reference
transmitter is between
minimum and maximum
distances.
Measured signal
(CW measurement
value)
Enter low and high limits for CW

measurement values in
respective boxes (Min meas.
and Max meas.).

measurement points which
CW measurement value is
between low and high
limits.
Azimuth between the

filtered points and the
reference transmitter
It is possible to keep CW
measurement points, which
angle with the reference
transmitter azimuth is between
user-defined negative and
positive angle values.

10-15

Parameter
Clutter class where

CW measurement
point is located
Operation
Check boxes of clutter classes
you want to keep in table and
map. It is possible to select
several values at once. To do
this, click one or several clutter
classes using shift and/or Ctrl
button at the same time and
then, check/uncheck one of
boxes.
Description

measurement points
located on the selected
clutter classes.
Example: If you enter 90 as negative angle and +90 as positive angle, U-Net will only
keep CW measurement points which have an angle between 90 and +90 with the
reference transmitter azimuth.
Filters are applied to CW measurement points in the table and on the map; only these
points are taken into account for statistics calculations.
Selecting the Delete points outside from the filter option enables you to definitively
remove CW measurement points, which do not fulfill filter criteria, from table and map.
It is possible to define advanced filters on other fields by clicking the More... button.
U-Net opens the classical Filter dialog available for any table.
Note:
z
Error corresponds to difference between CW measurement value and predicted

signal level from reference transmitter.
U-Net calculates signal level predictions for all the CW measurement points even
the filtered ones.
V. Displaying statistics between CW measurements and predictions

Since U-Net allows users to make predictions along a CW measurement path, it is
possible to compare field results in order either to calibrate the currently used
propagation model, or to determine the best suited one for the current project.
To display comparative results on CW measurements and prediction along a path,
proceed as follows:
1)
2)
3)
4)
Right click on the CW measurement session you already realized some

comparative predictions.
10-16
button.
button.

5)
Click the
button and choose the Display statistics command from the
open menu.
6)
Results are displayed on the in a Statistics window (per clutter class).
The Display tab window allows you to manage comparative results directly on the map.
Note:
z
Even it is possible to add other transmitters in an existing CW measurement path,

and start predictions on them, comparison is possible only with the reference
transmitter.
We remind you that model calibration and its result (standard deviation) strongly
depend on the CW measurement samples you use. A calibrated model must restore
the behaviour of CW measurements depending on their configuration on a large
scale, not totally check to a few number of CW measurements. The calibrated
model has to give correct results for every new CW measurement point performed
in the same geographical zone, without having been calibrated on these CW
measurements.
VI. Managing display on a CW measurement path

In U-Net, since CW measurement sessions are organized in item folders, these are
managed in the same way than in other folder items, i.e. sites, transmitters, etc...
Hence, the generic U-Net display dialog is available in order to manage each CW
measurement path, and works exactly as in the other cases.
To access the display dialog of any CW measurement session, proceed as follows:
1)
2)
3)
4)
Right click on the CW measurement session you want to manage the data display.
5)
6)
Click on the Display tab.
7)
button.
button.
window.
Thresholds, legend, tips and other handy display tools are available as classically.

10-17

Note:
z
When selecting Discrete values, you can choose Best server. U-Net will give the
measurement points the colour of transmitter, from which the predicted signal level
is the best one.
When using Value intervals, you can choose Best prediction. U-Net will colour the
measurement points depending on the best predicted signal level.
VII. Exporting CW measurement paths

in U-Net, CW measurement path may be exported in ArcView (.shp) and MapInfo
(*.mif) file formats as well as U-Net internal format (*.agd).
If the first case, when exporting, two other files with .dbf and .shx are created. The .dbf
file may be read with a spreadsheet word processor and contains all fields available in
the table associated with the CW measurement session that data are currently being
exported.
In the second case, in addition to the Mif file, a text file is created and contains
necessary text information in order to define path attributes.
To export data from a CW measurement sessions (path included):
1)
2)
3)
4)
Right click on the CW measurement session you want to export data.
5)
Choose the Export... option from the context menu.
button.
button.
6)
Enter name and path for the files to export (for both .shp, .dbf and .shx files).
7)
Click Save when this is made.
8)
A dialog window opens in which you must precise the coordinate system to use in
the exported file
9)
window.
10) Click
to confirm the export.
Note:
Under U-Net, shp filenames are not limited in number of characters when exporting or
importing, even if the file name is made of more than 8 characters.

10-18

10.2.3 Using the CW Measurement Window

I. CW Measurement window: activation
In U-Net, the CW Measurements window allows users to display curves for CW
measurements, predictions and any other parameters on each point of an existing CW
measurement path.
To open the CW Measurements window, proceed as follows:
Either,
1)
Left click on the View menu from the menu bar.
2)
Check the CW Measurements option from the scrolled menu.
Or,
1)
Access the CW measurement path you want to study.
2)
Right click on it in order to open the related context menu.
3)
Select the Analyse... command from the open menu.
The CW Measurements window is manageable by right clicking on it. From the open
scrolling menu, you may either zoom, copy the displayed window (in order to use it in
another application), print it, manage display parameters, and add a second ordinary
axis in order to study in parallel several parameters.
To use efficiently the CW measurement window, move the mouse pointer inside it, and
you will be able to follow the analysis along a complete selected CW measurement
path.
II. Defining the display properties of the CW measurement window

U-Net provides several tools to manage the display of the CW measurement window, in
order to make complete and easy a complete analysis of CW measurement paths.
To access the CW measurement window display dialog, proceed as follows:
1)
Make active the CW measurement window.
2)
Right click in it in order to get the related context menu.
3)
Choose the Display command from the open menu.
4)
Use the What's this help to get description about available fields in the open
dialog.
5)
In this dialog, you can specify Y-axis scale by entering minimum and maximum
values, choose style and colour of CW measurement, prediction (from transmitter
which the CW measurement path is related to) and attribute curves and select a
unique style for prediction (from other transmitters) curves. Colours of prediction
(from other transmitters) curves correspond to transmitter colours.
6)
Click OK to close the dialog.

10-19

Note:
The X-axis represents the distance (in m) between the point CW measurement and the
transmitter, according to the CW measurement path refers to. The X-axis scale can be
changed. The Y-axis (left vertical axis) is dedicated to CW measurement and prediction
values; its scale is user-definable. When using a second ordinary axis, the Y-axis (right
vertical axis) is related to attribute values; its scale is fixed.
III. Synchronising display in table/map/CW measurement window

It is possible to simultaneously visualise information and predictions about a CW
measurement point in the table, on the map and in the CW measurement window
thanks to display synchronisation. This synchronisation is also possible on vector data.
1)
Open the table related to the studied CW measurement data path, check the
CW measurement path displayed on the map and select the test mobile data
path in the CW measurement window.
2)
Arrange the table, the map and the CW measurement window on the screen so
as to display everything and click on the map window to make it active.
3)
Set the display options of the CW measurement window.
4)
Then, in the CW measurement window, click to display a cursor and move it

along the path; U-Net simultaneously selects both in the table and on the map the
corresponding CW measurement point.
IV. Analysing additional fields along CW measurement paths

In U-Net, It is possible to compare one CW measurement path with predictions from
different transmitters. In the CW Measurements window, you can visualise variations of
CW measurements, predictions from different transmitters and any CW measurement
path attribute (distance, clutter class, altitude...) along the path using a second ordinary
axis.
Attributes and their definitions are listed in the table below (see Table 10-8).
Table 10-8 CW measurement path attributes
Attribute
Description
CW Measurement point abscissa (stated in the display coordinate

system)
CW Measurement point ordinate (stated in the display coordinate

system)
CW Measurement point altitude above sea level (m)
CW Measurement values (if available)

10-20

Attribute
Description
Prediction values (if completed)
(M - P)
Difference between measured and predicted values
Distance between transmitter and CW measurement point (m)
CLUTTER
Clutter class at the CW measurement point
Clutter height at the CW measurement point (m)
P (Tx)
Signal level received from Tx (dBm)
DTM +
CLUTTER
Clutter height + ground altitude at the CW measurement point (m)
When the CW Measurements window is displayed, all of these data are available in the
Field scrolling list (CW measurement and prediction values always stay visible). Once a
field is selected, a second ordinary axis opens at extreme right and associated value is
given just right to it.
To analyse data at along a path in the CW measurement window, proceed as follows:
1)
Make the CW Measurements window active.
2)
Left click in the CW Measurements window.
3)
A cursor (vertical line) appears in the CW Measurement window positioned on the

closest CW measurement point. This cursor can be moved over the curves
from one point to another.
4)
Simultaneously, a receiver-like
cursor appears on the map on the
associated CW measurement point. As for point analysis and interference, this

cursor symbolizes a receiver placed on the CW measurement point to be
studied. This receiver will be synchronized such as two pointing modes on the
CW measurement points are available: on the map and on the curves.
5)
Choose from the Field scrolling box the value to display on each point, and the
curve to display in parallel with the ones referring to the main ordinary axis.
Note:
To come back to the initial state (no second ordinary axis), select the blank field from
the field scrolling box.
V. Zooming in the CW measurement window

U-Net provides some zoom tools in order to be able to analyse with precision data
contained in the CW measurement window.
10-21

To access a zoom command in the CW measurement window, proceed as follows:

1)
2)
3)
Choose either the Zoom in, Zoom out, 1st zoom point or last zoom point
4)
The CW measurement window adapts itself according to your choice.
By using the 1st zoom point or last zoom point commands, it is possible to define a
zoom range for the current CW measurement window. In the CW Measurement window,
place the cursor where you want to start the zoom, right click and select the 1st zoom
point command. Then, place the cursor where you want to end the zoom, right click and
select the last zoom point command. U-Net will display the path between the first and
the last selected CW measurement points.
Clicking on Zoom out enables you to undo the zoom area and to display the whole path.
VI. Exporting the CW measurement window

In U-Net, like for many other objects displayed in a window form (point analysis,
antenna patterns, etc...), it is possible to export the contents of the CW measurement
window to another application.
To export the CW measurement window to another application, proceed as follows:
1)
2)
3)
Choose the Copy command from the open menu.
4)
Switch to another application (e.g. Word), then paste the content of the clipboard.
Note:
Additional data related to the second ordinary axis are kept during export.
VII. Printing the CW measurement window

antenna patterns, etc...), it is possible to print the contents of the CW measurement
To export the CW measurement window to another application, proceed as follows:
1)
2)
3)
Choose the Print command from the open menu.
4)
The print dialog opens.

10-22

Note:
Additional data related to the second ordinary axis are kept during print.
VIII. Combining CW measurement and point analysis windows

The combined use of the CW measurements window and the point analysis window
may help the user to interpret some results that could be difficult to understand.
Nevertheless, some prediction differences may happen between the two windows.
Differences can be explained as follows:
1)
In the point analysis window, prediction results are given for each bin from the
calculation grid (defined in the prediction properties). There is uniqueness in
prediction results for each picture element from the calculation grid in the point
analysis window.
2)
In the CW Measurements window, prediction results are given for the exact
geographic location where have been taken CW measurements. No computation
(or prediction) resolution is taken in account in this part.
10.3 Test Mobile Data Paths

10.3.1 Creation of a Test Mobile Data Path
I. Importing a test mobile data path
In U-Net, you may import any ASCII text file (with tab, semi-colon or blank character as
separator) as well as TEMS FICS-Planet export (*.pln) and TEMS text export (*fmt) to
create a test mobile data path.
1)
2)
Right click on the Test mobile data folder to open the associated context menu.
3)
4)
Specify the path, name and the format of the file to be imported in the open
window.
The Test mobile data import dialog is open. It is similar to the one available when
importing CW measurement data:
1)
In the General tab, give a name and indicate the receiver height, gain and
losses of the receiver antenna, the units and the coordinate system used in the
file.
2)
In the Setup tab, select an import configuration if defined or specify import

settings such as the first test mobile data line, the separator and the decimal
symbol.
10-23

3)
Click on the Setup button to set correspondence between the file columns and
the U-Net internal fields.
Mandatory information that U-Net needs to succeed in importing a file is:

z
The position of test mobile data points: indicate abscissa and ordinate columns in
the file.
ID of serving cells and their neighbours. For each point, U-Net is capable of
importing the measurements from a serving cell and six neighbour cells.
In UMTS networks, a cell is identified thanks to its scrambling code. Therefore, you
must indicate the columns relating to the scrambling code of cells, the scrambling code
format (decimal or hexadecimal) used in the file and the scrambling code group if
needed. As a scrambling code can belong to several groups, it is useful to know the
group, from which it has been selected. If the scrambling code group information is not
contained in the file, do not specify anything.
In CDMA/CDMA2000 networks, a cell is identified thanks to its PN Offset. Therefore,
you must indicate the columns relating to the PN Offset of cells, the PN Offset format
(decimal or hexadecimal) used in the file and the PN Offset group if needed. As a PN
Offset can belong to several groups, it is useful to know the group, from which it has
been selected. If the PN Offset group information is not contained in the file, do not
specify anything.
In case of GSM/GPRS/EDGE networks, a cell is identified thanks to its pair
BCCH-BSIC. Thus, you must specify the fields corresponding to BCCH and BSIC of
cells, and the BSIC format (decimal or octal) used in the file.
For scrambling code, scrambling code group, PN Offset code, PN Offset code group,
BCCH and BSIC information, it is not required to associate a column of the file for the
serving cell and each neighbour cell; this operation was considered too long. Here, you
must enter a unique character string for the serving and neighbour cells; this character
string is a substring that must be contained in the column names relating to the serving
and neighbour cells.
Important: U-Net is case sensitive. So, be careful when defining column titles.
Example: If you enter the character string SC for the scrambling code information,
U-Net will search for the scrambling codes of serving and neighbour cells in the
columns which name contains SC.
4)
In the Setup tab, specify the data type of columns to be imported. The default
type of columns is <Ignore>. If you do not change it, columns will not be recovered
in U-Net.
5)
In order to go on the import, click on

10-24

Note:
z
Some files like *.pln and some *.fnt files (created with previous TEMS versions)
have a well-known fixed structure. In this case, import is automatic and direct.
Multiple imports are supported.
In the Import dialog, it is important to specify the right data type (Integer, Real,
Text...) of each column in order for data to be correctly displayed (only numerical
fields will be able to be displayed in the Test mobile data window). Columns with
<Ignore> type will not recover.
The import settings may be saved in a configuration (test mobile data import
configuration) that you will be able to reuse for next file imports.
II. Importing several test mobile data paths

It is possible to import several test mobile data files at once.
1)
Follow the standard steps of the import test mobile data procedure, select
several files in the Open window.
Either,
2)
In the Open window, optionally specify an import configuration in the "Files of

type" scrolling box" in order to filter only files respecting the format defined in the
considered configuration.
3)

4)
button.
Click the
Or,
2)

3)
Click the
4)
The import CW measurements window opens.
5)
Optionally specify an import configuration (Configuration part) that will be
button.
consistent with the format of the files being imported.

Then,
1)
In that case, you may import several test mobile data files based on the same
transmitter and with the same associated configuration. In this case, you just need
to indicate the configuration once.

10-25

2)
Click on the
all button: all the paths will be imported at the same
time.
Note:
z
If the selected test mobile data files are based on different configurations, you
button. For each file, indicate a configuration and then,
cannot use the

click the
z
button.
When using the Import all button, U-Net does not import files for which the
configuration does not correspond to the selected one. It displays an error message
and goes on the import with next file.
III. Creating an import test mobile data path configuration

In U-Net, import test mobile data configurations can be defined in order to make easier
some future import procedures based on the same model as a reference one.
Moreover, configurations may be useful to import several test mobile data set at once.
To create an import test mobile data configuration, you must use the generic import
feature. When the import test mobile data window is open, proceed as follows:
1)
Define configuration characteristics in the Setup tab:
You can change some parameters in the File part such as the number of the first
CW measurement line, the list separator ( , tab, ;) and decimal symbol (,
or .) used in the file to be imported.
Click on the Setup button to set correspondence between the file columns and
the U-Net internal fields.
Mandatory information that U-Net needs to succeed in importing a file is:

z
The position of test mobile data points: indicate abscissa and ordinate columns in
the file.
ID of serving cells and their neighbours. For each point, U-Net is capable of
importing the measurements from a serving cell and six neighbour cells.
In UMTS networks, a cell is identified thanks to its scrambling code. Therefore, you
must indicate the columns relating to the scrambling code of cells, the scrambling code
format (decimal or hexadecimal) used in the file and the scrambling code group if
needed. As a scrambling code can belong to several groups, it is useful to know the
group, from which it has been selected. If the scrambling code group information is not
contained in the file, do not specify anything.
10-26

In case of GSM/GPRS/EDGE networks, a cell is identified thanks to its pair

BCCH-BSIC. Thus, you must specify the fields corresponding to BCCH and BSIC of
cells, and the BSIC format (decimal or octal) used in the file.
For scrambling code, scrambling code group, BCCH and BSIC information, it is not
required to associate a column of the file for the serving cell and each neighbour cell;
this operation was considered too long. Here, you must enter a unique character string
for the serving and neighbour cells; this character string is a substring that must be
contained in the column names relating to the serving and neighbour cells.
Important: U-Net is case sensitive. So, be careful when defining column titles.
Example: If you enter the character string SC for the scrambling code information,
U-Net will search for the scrambling codes of serving and neighbour cells in the
columns which name contains SC.
2)
Click the OK button when the correspondence is complete.
3)
In the Setup tab, specify the data type of columns to be imported. The default
type of columns is <Ignore>. If you do not change it, columns will not be recovered
in U-Net.
4)
In the Configuration part, enter the extension (e.g. *.txt) for the files that will be
considered (and filtered) with this configuration
5)
button and enter a name for the current configuration.
Click the
Click OK to save the import configuration.

6)
In order to go on the import, open the General tab:
Indicate the test mobile path name.
Enter the transmitter frequency, the receiver height, the gain and losses of the
receiver antenna.
Define the unit and the coordinate system of the current test mobile data.
Click on the
button to achieve the import test mobile data procedure.

10-27

Note:
z
Configuration is saved as soon as you click on the Save button. It is not necessary
to complete the import procedure (by pressing the Import button).
When importing a test mobile data file, the existing configurations are available in
the Files of type scrolling menu (Open window). They are sorted according to their
creation order. During import, if U-Net recognises the extension, it automatically
proposes the corresponding configuration. In case several configurations are
associated with an extension, U-Net chooses the first configuration in the list.
When importing a test mobile data file, of course, the existing configurations are
also available in the Configuration scrolling box of the Setup tab of the import test
mobile data file dialog. When selecting the appropriate configuration,
correspondences are automatically set.
The defined configurations are stored in the file MeasImport.ini. This file is located
in the directory where U-Net is installed. You can copy it on other workstations (in
the directory where U-Net is installed) in order to make available the configurations.
Caution:
z
It is not necessary to define a projection coordinate system to be able to import a

test mobile data path. However, in order to avoid some inconsistencies, you must
specify it in case the test mobile data points are stated in a geographic coordinate
system.
In order to avoid some inconsistencies, do not assign the *.* extension to a

configuration.
IV. Deleting an import test mobile data path configuration

In U-Net, Import test mobile data configurations can be defined in order to make easier
some future import procedures based on the same model as a reference one.
Moreover, configurations may be useful to import several test mobile data set at once.
To delete an import test mobile data configuration, you must use the generic import
feature. When the import test mobile data window is open, proceed as follows:
1)
Click on the Setup tab.
2)
In the Configuration part, click on the Configuration scrolling list.
3)
Choose the configuration you want to remove.
4)
Click on the
button.

10-28

Another solution is to open the file MeasImport.ini (located in the directory where
U-Net is installed), select and erase the configurations that you want to remove.
10.3.2 Management of a Test Mobile Data Path

I. Defining test mobile data path properties
In U-Net, test mobile data sessions are organized in items located under the Test
mobile data folder.
Test mobile data folder global properties are reachable from the associated context
menu (left click on the Test mobile data folder).
Measure sessions properties are reachable from Test mobile data subfolders
associated context menus (left click on the Test mobile data subfolders).
To manage the properties of an existing Test mobile data path, proceed as follows:
1)
2)
Expand the Test mobile data folder by left clicking on the
3)
Right click on the Test mobile data session you want to manage properties.
4)
5)
button.
window.
The dialog is made of 4 tabs (General, Parameters, Table and Display) in which you
can respectively manage:
z
The Test mobile data conditions.
The General tab contains information on the receiver and the header of the imported
file.
z
Filters over the Test mobile data path.
Filter features enable you to limit the test mobile data points listed in the table and
displayed on the map.
z
Predictions along the test mobile data path for each involved server or neighbour.
The analysis of a specific field (e.g. RXLEV of a specific transmitter when this one
is neighbour #3) along the path.
The Test mobile data table content.
The table tab works like all the other ones, with the standard features on how to
manage the contents of any table. It is possible to add new attribute in the table.
z
The display of the Test mobile data points composing the path.

10-29

Note:
In the parameters tab, when clicking the
button, the Refresh geo data
command enables you to update heights (Alt DTM, Clutter height, DTM+Clutter) and
the clutter class of test mobile data points after adding new geographic maps or
modifying existing ones.
II. Opening a test mobile data table

All the test mobile data points of a path, serving cells, neighbours and related attributes
are listed in a table.
To open this table, proceed as follows:
1)
2)
Expand the test mobile data folder by left clicking on the
button.
Either,
3)
Right click on the test mobile data session you want to open the related table.
4)
Choose the Open Table command from the context menu.
Or,
3)
Double click on the test mobile data session you want to open the related table.
Standard features for managing table contents (Copy/Paste, Fill up/down, Delete,
Display columns, Filter, Sort, and Table Fields) are available in a context menu (when
You can also access the table content management from the Table tab of the test
mobile data session property dialog.
All the test mobile data points from the imported file are listed in a related table. For
each test mobile data point, U-Net provides the file attributes and other information
such as the ground altitude above the sea level (Alt. DTM), the distance from its serving
cell (Dist), the clutter class (Clutter), the clutter height (Clutter Height) and the total
height including the clutter height and the ground altitude (DTM+Clutter).

10-30

Note:
It is possible to display either the BCCH-BSIC pair, the scrambling code
group-scrambling code pair or the PN Offset group-PN Offset pair, in the columns of
the serving and neighbour cells. To display this information in the table when importing
a file, add these lines in the U-Net.ini file.
[TestMobileData]
ShowCoupleInfo=1
To be taken into account, the file must be located in the U-Net installation directory.
This file is read only when U-Net is started. Therefore, it is necessary to close the U-Net
U-Net.ini.
III. Predicting signal levels on a test mobile data path

For any existing test mobile data, it is possible to predict the signal level of any involved
transmitter, on each point of the path.
1)
2)
3)
4)
5)
Click the Parameters tab.
6)
Click the
button.
button and choose the Calculate predictions command
from the open menu to start calculation.

Calculate Predictions adds in the table, for each transmitter (serving and neighbours), a
column ("Pred serving cell", "Pred neighbour1", and so on) which contains the
predicted field (in dBm) received from the transmitter. The propagation model used is
the one assigned to the transmitter (in the Propagation tab of the Transmitter properties
for the main matrix calculation). Standard graphic display is available for these new
columns. For example, you can obtain charts with predicted signal(s) in the Test mobile
data window.
IV. Filtering points along test mobile data paths

When working on a test mobile data path, it is possible to impose some filter in order to
exclude inappropriate points from the study. This can be made in the Filter part of the
Parameters tab of any test mobile data session property dialog, you may specify filter
criteria on:

10-31

z
Clutter class where test mobile data point is located: check boxes of clutter
classes you want to keep in table and map. It is possible to select several values at
once. To do this, click one or several clutter classes using shift and/or Ctrl button at
the same time and then, check/uncheck one of boxes. U-Net will keep only test
mobile data points located on the selected clutter classes.
It is possible to define advanced filters on other fields by clicking the More... button.
U-Net opens the standard Filter dialog available for any table.
The Refresh geo data feature, available when clicking on the Actions button, enables
you to update heights (Alt DTM, Clutter height, DTM+Clutter) and the clutter class of
test mobile data points after adding new geographic maps or modifying existing ones.
Selecting the Delete points outside from the filter option enables you to definitively
remove test mobile data points, which do not fulfill filter criteria, from table and map.
Filters are applied to test mobile data points in the table and on the map.
V. Focusing on a specific field along a test mobile data path

For any existing test mobile data, it is possible to focus on a specific field linked of any
involved transmitter, on each point of the path.
This feature allows the user to choose a transmitter and a field and to generate a new
column in the table, containing the value of the given field for the selected transmitter
when it is either the serving cell or one of the neighbours. For example, the column can
contain the RXLEV for the selected transmitter whether it is the serving cell or a
neighbour.
1)
2)
3)
4)
5)
6)
Click the
button.
button and choose the Focus on a transmitter command
from the open menu.

7)
In the Focus on specific fields of a given transmitter dialog, select a transmitter in

the first scrolling menu.
8)
Then, open the second scrolling menu and select for the serving cell and each
neighbour the fields, which you want to collect values. Only one field per serving
cell and neighbour may be chosen.
9)
Click OK to confirm the selection.
10) A display with colour shading is automatically proposed on the created field in the
table.
11) Click OK to close the dialog.
10-32

VI. Managing display on a test mobile data path

In U-Net, since test mobile data sessions are organized in item folders, these are
managed in the same way than in other folder items, i.e. sites, transmitters, etc...
Hence, the generic U-Net display dialog is available in order to manage each test
mobile data path, and works exactly as in the other cases.
To access the display dialog of any test mobile data session, proceed as follows:
1)
2)
3)
4)
button.
5)
Click on the Display tab.
6)
window.
Thresholds, legend, tips and other handy display tools are available as classically.
Important:
When the number of test mobile data points is very high, it is possible to improve the
speed of test mobile data display by checking the 'Quick display' box in the Display tab
of the dialog box. In this case, the symbol of test mobile data points is fixed; it is just
possible to change size and colour. In this case, the symbol of test mobile data points is
fixed; it is just possible to change size and colour.
To be taken into account, the file must be located in the U-Net installation directory. This
file is read only when U-Net is started. Therefore, it is necessary to close the U-Net
U-Net.ini.
Note:
Display of test mobile data paths can be globally managed from the property dialog of
the Test mobile data folder.
It is possible to display on the map the serving and neighbour cells of a test mobile data
point.
To visualise the serving and neighbour cells of a test mobile data point, proceed as
follows:

10-33

1)
On the map, click on a point.
2)
U-Net displays the link(s).
U-Net graphically displays link(s) from the test mobile data point to its serving cell (solid
line - S as symbol) and neighbours (dotted line and N as symbol). The link colour
corresponds to the transmitter colour.
VII. Exporting test mobile data paths

In U-Net, Each test mobile data path may be exported in ArcView (.shp) and MapInfo
(*.mif) file formats as well as U-Net internal format (*.agd).
If the first case, when exporting, two other files with .dbf and .shx are created. The .dbf
file may be read with a spreadsheet word processor and contains all fields available in
the table associated with the test mobile data session that data are currently being
exported.
In the second case, in addition to the Mif file, a text file is created and contains
necessary text information in order to define path attributes.
To export data from a test mobile data session (path included):
1)
2)
3)
Right click on the Test mobile data session you want to export data.
4)
Choose the Export... option from the context menu.
5)
Enter name and path for the files to export.
6)
Click Save when this is made.
7)
A dialog window opens in which you must precise the coordinate system to use in
button.
the exported file.

8)
window.
9)
Click
to confirm the export.
Note:
Under U-Net, shp filenames are not limited in number of characters when exporting or
importing, even if the file name is made of more than 8 characters.

10-34

10.3.3 Using the Test Mobile Data Window

I. Test mobile data window: activation
In U-Net, the Test mobile data window allows users to display the variation of any
selected numeric field along the path.
To open the Test mobile data window, proceed as follows:
Either,
1)
Left click on the View menu from the menu bar.
2)
Check the Test mobile data option from the scrolled menu.
Or,
1)
Access the test mobile data path you want to study.
2)
Right click on it in order to open the related context menu.
3)
Select the Analyse... command from the open menu.
The Test mobile data window is manageable by right clicking on it. From the open
scrolling menu, you may either zoom, copy the displayed window (in order to use it in
another application), print it, manage display parameters to make easy the analysis of
the several parameters.
To use efficiently the CW measurement window, move the mouse pointer inside it, and
you will be able to follow the analysis along a complete selected CW measurement
path.
II. Defining the display properties of the test mobile data window
U-Net provides several tools to manage the display of the Test mobile data window, in
order to make complete and easy a complete analysis of Test mobile data paths.
To access the CW measurement window display dialog, proceed as follows:
1)
Make active the Test mobile data window.
Either,
2)
Click the
button to choose information you want to visualise. In the
Display dialog, U-Net lists all the test mobile data path attributes. Only values from
numerical fields can be displayed in the Test mobile data window; discrete fields
are made grey.
Or,
2)
3)
Choose the Display command from the open menu.
4)
Check the boxes of fields which you want to visualise variation and choose a
colour for each of them. A context menu is available when right clicking anywhere
in the table. It contains following commands (see Table 10-9).
10-35

Table 10-9 Test mobile data window context menu

Command
Description
Select all
Selects all the attributes listed in the table
Display
Checks boxes of all the selected attributes
Hide
Uncheck boxes of all the selected attributes
Colour
Assigns the chosen colour to all the selected

attributes
It is possible to select several attributes at once. To do this, click one or several

attributes using shift and/or Ctrl button at the same time, and then use the Display, Hide
and Colour commands of the context menu.
Then
1)
Click on OK to validate the display settings.
III. Synchronising display in table/map/Test mobile data window

It is possible to simultaneously visualize information about a test mobile data point in
the table, on the map and in the Test mobile data window thanks to display
synchronization. This synchronization is also possible on vector data.
1)
Open the table related to the studied test mobile data path, check the test
mobile data path is displayed on the map and select the test mobile data path in
the Test mobile data window.
2)
Arrange the table, the map and the Test mobile data window on the screen so
as to display everything and click on the map window to make it active.
3)
Set the display options of the Test mobile data window. After selecting and
validating attributes you want to visualise in the Test mobile data window, U-Net
regroups and colours columns relating to the displayed attributes in the table. The
column colour corresponds to the colour associated to the attribute in the Display
dialog of the Test mobile data window.
4)
Then, in the Test mobile data window, click to display a cursor and move it
along the path ; U-Net simultaneously displays in the table and on the map the
corresponding test mobile data point and its links to serving and neighbour cells
(only on the map).
Note:
To remove the colour of columns in the table and to display all of them again, use the
Column format and the Display columns commands available in the Format menu.

10-36

IV. Zooming in the test mobile data window

U-Net provides some zoom tools in order to be able to analyse with precision data
contained in the Test mobile data window.
To access a zoom command in the Test mobile data window, proceed as follows:
1)
2)
3)
Choose either the Zoom in, Zoom out, 1st zoom point or last zoom point
4)
The Test mobile data window adapts itself according to your choice.
By using the 1st zoom point or last zoom point commands, it is possible to define a
zoom range for the current Test mobile data window. In the Test mobile data window,
place the cursor where you want to start the zoom, right click and select the 1st zoom
point command. Then, place the cursor where you want to end the zoom, right click and
select the last zoom point command. U-Net will display the path between the first and
the last selected CW measurement points.
Clicking on Zoom out enables you to undo the zoom area and to display the whole path.
V. Exporting the test mobile data window

antenna patterns, etc...), it is possible to export the contents of the Test mobile data
To export the Test mobile data window to another application, proceed as follows:
1)
2)
3)
Choose the Copy command from the open menu.
4)
Switch to another application (e.g. Word), then paste the content of the clipboard.
VI. Printing the test mobile data window

antenna patterns, etc...), it is possible to print the contents of the Test mobile data
To export the Test mobile data window to another application, proceed as follows:
1)
2)
3)
Choose the Print command from the open menu.
4)
The print dialog opens.

10-37

Chapter 11 Co-planning Features

11.1 Overview
Since U-Net is a complete multi-technology planning tool, the possibility to work on
several networks on the same environment has been developed. Hence, it is possible
to display in parallel any object (sites, transmitters, geo data, etc...) of a project in
another external project. You can choose, for example, to display simultaneously
transmitter
coverages
from
both
GSM/GPRS/EDGE
and
WCDMA/UMTS
technologies.
Moreover, it is also possible to study inter-technology handover by allocating
Inter-technology neighbours, either manually or automatically (from CDMA to GSM or
from GSM to CDMA) using methods based on distance and coverage overlapping
(optionally).
Because U-Net is able to work connected to a database, working in co-planning in
such a context is also possible, and whatever is the database in use (MS Access, SQL
server, Oracle, and Sybase).
11.2 Co-Planning Using U-Net

11.2.1 Displaying External Objects in a Current U-Net Project
In U-Net, the co-planning feature enables you to compare networks based on different
technologies in the same document .atl. Therefore, you can visualise sites,
transmitters, prediction studies, measurement paths and geographic maps (DTM,
clutter, traffic...) (see Table 11-1).
Table 11-1 Displaying external objects in a current U-Net project
Function
Operation
1)
visualise any object

from a project A in a
project B
2)
Result
Open both projects A.atl and
The selected
B.atl.
objects are
In the document A.atl, right
displayed in the
click on the folder(s) (Sites,
document B
Transmitters,
workspace
Predictions,
Measurements, Clutter classes,

11-1
window

Function
Operation
Result
Traffic, DTM...) you want to
Set up link of the projects A

and B
3)
visualise in the project B in
Additional folders
order to display the associated
relating to project
context menu.
A data are created
Choose the Creating a link in:
in the document B
document
Explorer window.
B.atl
command
from the open scrolling menu

The
modifications
will be taken into
account both in
the project A
change project A object

properties in document A
(source
document) and
or B.
in the project B
(in the
workspace and
Explorer
windows).
Define neighbours
between linked projects
(from CDMA to GSM or
from GSM to CDMA)
using methods based on

distance and coverage
overlapping (optionally).
Note:
When closing the project A, U-Net displays a special warning icon in the document B
Explorer window and objects relating to the document A disappear in the project B
workspace window.
11.2.2 Allocating Inter-technology Neighbours Manually (Co-Planning)

In U-Net, the co-planning feature allows you to display networks based on different
technologies in a same document .atl. You can visualise GSM/GPRS/EDGE sites,
transmitters, coverage studies in a UMTS project.
11-2

In addition, a feature allowing the inter-technology neighbours management has been

integrated; you may choose manually, for any transmitter, neighbours from a linked
project (for example GSM neighbours of UMTS cells). An automatic tool (from CDMA
to GSM or from GSM to CDMA) using a method based on distance and coverage
overlapping (optionally) is also available.
To define the inter-technology neighbours (from a CDMA document, B.atl) for any
transmitter (of a GSM document, A.atl), proceed as shown in Table 11-2.
Table 11-2 Define the inter-technology neighbours
Method
Operation
1)
Create a link on the Transmitters folder of B.atl into A.atl.
2)
In the document A.atl, left click on the Data tab of the

Explorer window.
3)
Expand the transmitters folder by clicking on the

4)
Either Right click on the transmitter for which you want

to define the inter-technology neighbourhoods, Choose
the properties option from the context menu, Or Double
click on the transmitter for which you want to define the
inter-technology neighbourhoods.
5)
Method 1
Click the Inter-technology Neighbours tab from the

current window.
6)
In the displayed window, use the top table. Select the

, then in the Neighbours column,
row with symbol
click on cell to choose from the scrolling box the desired
neighbour. In the scrolling box, U-Net lists all the cells
from B.atl located within a radius of 30 km around the
reference transmitter.
7)
Click on the
button to validate and add a
new row to the table.

8)
When you have completed your entry, click on OK to

close the dialog box.

11-3

Method
Operation
1)
2)

Explorer window.
3)
Right click on the Transmitters folder to open the associated

context menu.
4)
Choose the [Neighbours: Inter-technology Neighbours]

command from the scrolling list.
Method 2
5)
6)
Edit or choose from the scrolling menu the reference

transmitter name (in the network A) and then, the external
neighbour name (in the network B). Only inter-technology
cells located within 30 km from the reference transmitter are
listed in the scrolling list of the Neighbours column.
7)
Click on the
button to validate and add a new
row to the table.

8)

the dialog box.
To define the inter-technology neighbours (from a GSM document, B.atl) for any
cell (of a CDMA document, A.atl), proceed as shown in Table 11-3.

11-4

Table 11-3 Define the inter-technology neighbours

Method
Operation
1)
Create a link on the Transmitters folder of B.atl into

A.atl.
2)

Explorer window.
3)

context menu.
4)
Choose the [Cells:Open Table] command from the

open menu.
5)
Once the cells table is open, Either Right click on the

cell for which you want to define the inter-technology
neighbourhood, Choose the record properties option
from the context menu (or from the Records menu from
the menu bar), or Double click on the cell from which
you
Method 1
want
to
define
the
inter-technology
neighbourhood.
6)
Click the Inter-technology Neighbours tab from the

current window.
7)
In the displayed window, use the top table. Select the

, then in the Neighbours column,
row with symbol
click on cell to choose from the scrolling box the
desired neighbour. In the scrolling box, U-Net lists all
the transmitters from B.atl located within a radius of 30
km around the reference cell.
8)
Click either on the
button to validate
and add a new row to the table.

9)


11-5

Method
Operation
1)
Create a link on the Transmitters folder of B.atl into

A.atl.
2)

Explorer window.
3)

context menu.
4)
Right click on the Transmitters folder to open the

5)
Choose
the
[Cells:
Neighbours:
Inter-technology
Neighbours] command from the scrolling list.

Method 2
6)
7)
Edit or choose from the scrolling menu the reference

cell name (in the network A) and then, the external
neighbour
name
(in
the
network
B).
Only
inter-technology transmitters located within 30 km from

the reference cell are listed in the scrolling list of the
Neighbours column.
8)
Click on the
button to validate and add
a new row to the table.

9)

For each neighbour, U-Net indicates:

z
The distance between the neighbour and the reference transmitter (cell).

imported (Planet import, generic import, import using an add-in). After a manual
allocation, the value is set to manual.
The neighbour rank in the list of neighbours of the reference transmitter (cell).
This information is given only in case of an automatic allocation.

allocation.
In the table listing all the neighbourhood relationships of cells, U-Net indicates the
number of neighbours assigned to each reference transmitter (cell).

11-6

Note:
Standard features for managing table contents (Copy/Paste, Delete, and Display
11.2.3 Defining Exceptional Pairs of Inter-technology Neighbours

U-Net enables you to define neighbourhood constraints that may be then considered
by algorithm during the automatic allocation of inter-technology neighbours.
To define Inter-technology exceptional pairs of neighbours between transmitters
(from a GSM document, B.atl) and cells (of a CDMA document, A.atl), proceed as
shown in Table 11-4.

11-7

Table 11-4 Define Inter-technology exceptional pairs of neighbours between

transmitters
Method
Operation
1)
2)
In the document A.atl, left click on the Data tab of the Explorer
window.
3)
Right click on the transmitters folder to get the related context

menu.
4)
Choose the [Cells:Open Table] command from the open menu.
5)
Once the cells table is open, Right click on the cell from which
you
want
to
define
the
inter-technology
neighbourhood
constraints, then choose the record properties option from the

context menu (or from the Records menu from the menu bar). Or
neighbourhood constraints.
Method 1
6)
Click the Inter-technology Neighbours tab from the current

window.
7)
In the displayed window, use the top table. Select the row with
. In the Neighbours column, click the cell of the
symbol
Neighbours column to choose from the scrolling box a neighbour
(U-Net lists all the transmitters from B.atl located within a radius
of 30 km around the reference cell) and then, click the cell of the
Status column and choose from the scrolling menu if you want to
forbid or force this neighbourhood relationship.
8)
button
to validate and add a new row to the table.

9)
When you have completed your entry, click on OK to close the

dialog box.

11-8

Method
Operation
1)
2)

In the document A.atl, left click on the Data tab of the Explorer
window.
3)
Right click on the transmitters folder to get the related context

menu.
4)
Choose the [Cells:Neighbours:Inter-technology exceptional pairs]

Method 2
5)
. Click the cell

of the Cells column to select a reference cell and then, click the
cell of the Neighbours column to choose a neighbour. Finally,
click the cell of the Status column and specify if you want to forbid
or force this neighbourhood relationship.
6)
Click another cell of the table to validate and add a new row to the
table.
7)
When you have completed your entry, click on OK to close the

dialog box.
To define Inter-technology exceptional pairs of neighbours between cells (from a

CDMA document, B.atl) and transmitters (of a GSM document, A.atl), proceed as
shown in Table 11-5.

11-9

Table 11-5 Define Inter-technology exceptional pairs of neighbours between cells

Method
Operation
1)
2)

Explorer window.
3)
Expand the transmitters folder by clicking on the
button
in front of it.
4)
Right click on the transmitter for which you want to define

the inter-technology neighbourhood constraints, then
choose the properties option from the context menu. Or
Double click on the transmitter for which you want to
define the inter-technology neighbourhood constraints.
Method 1
5)
Click the Inter-technology Neighbours tab.
6)
. In the Neighbours column, click the cell
with symbol
of the Neighbours column to choose from the scrolling box
a neighbour (U-Net lists all the cells of B.atl located within
a radius of 30 km around the reference transmitter) and
then, click the cell of the Status column and choose from
the scrolling menu if you want to forbid or force this
neighbourhood relationship.
7)

8)


11-10

Method
Operation
1)
2)

Explorer window.
3)
Choose the [Neighbours:Inter-technology exceptional

pairs] command from the Transmitters folder context
menu.
4)
Method 2
. Click
the cell of the Transmitters column to select a reference
transmitter and then, click the cell of the Neighbours
column to choose a neighbour. Finally, click the cell of the
Status column and specify if you want to forbid or force
this neighbourhood relationship.
5)
Click another cell of the table to validate and add a new

row to the table.
6)

Note:
Exceptional pairs are not taken into account during manual neighbour allocation.
11.2.4 Allocating CDMA Neighbours to GSM Transmitters

It is possible to automatically define handover relationships between a GSM network
and a CDMA one (CDMA2000 1xRTT 1xEV-DO, IS-95 cdmaOne and UMTS). This
feature enables you to establish a list of inter-technology neighbours in an .atl
document; inter-technology neighbours are stored in database.
If you want to allocate neighbours from UMTS document to transmitters in GSM
document, you have to create a link from transmitters in UMTS into GSM document
(using the context menu of Transmitters folder in UMTS document).
To automatically allocate UMTS neighbours (from UMTS.atl) to GSM transmitters
(of GSM.atl), proceed as follows:
1)
Create a link on the Transmitters folder of UMTS.atl into GSM.atl.
2)
In the document GSM.atl, right click on the transmitters folder to get the
related context menu.
3)
Choose the [Neighbours:Automatic allocation...] command from the open

menu.
11-11

4)
Click on the Inter-technology Neighbours tab. Table 11-6 shows the

parameters which automatic neighbour allocation is based on.
5)
Click the
6)
neighbours for each transmitter. In addition, it indicates allocation reason for each
neighbour. (see Table 11-7)
7)
button to assign
inter-technology neighbours to cells.

8)
Click the Close button to achieve the procedure.
Table 11-6 UMTS-GSM automatic neighbour allocation parameters

Parameter
Definition
Description
z
This value may be either globally

set for all the transmitters (in the
The maximum number of
automatic allocation algorithm), or
Max
inter-technology
specified for each transmitter (in
number of
neighbours (from the UMTS
the Transmitters table).
neighbours
document) to be allocated
to a transmitter.
U-Net uses the value defined at the

transmitter
level
if
available,
otherwise it considers the global

value.
Max
Inter-Site
distance
SA
The maximum distance you
If the distance between the reference
can have between the
transmitter and a candidate neighbour
reference transmitter and a
is higher than this value, then the
candidate neighbour.
candidate neighbour is discarded.
The area where the signal
Coverage conditions between the
level received from A on the
reference transmitter (A) and a
BCCH TRX type exceeds
candidate neighbour (B) if the option
the user-defined minimum
Use Coverage Overlapping is
threshold.
selected. U-Net determines the

11-12

Parameter
Definition
Description
overlapping area between SA and SB
The area where:

z
The pilot signal received
( S A SB ).
from the cell B is greater

than
SB
minimum
pilot
signal level.
z
The pilot quality from B

exceeds
user-definable minimum
value (minimum Ec/Io).
z
Max
Power:
reduction factor (% of
maximum
powers
contributing to I0) is
applied
to
Power
maximum
contributing
(defined
to Io
properties).
z
Total
the
cell
powers
in
Cell
Power
Used:
No
U-Net takes into account

the total downlink power
used defined for each
cell.
a minimum percentage of
% min
covered area to be
Covered
exceeded in order not to
Area
discard the candidate

neighbour B.
The percentage of covered area is

calculated using this formula
S A SB
SA
.
This option enables you to force the

Calculation
options
co-site cells in the neighbour list of a

Force co-site as neighbours
reference transmitter. The co-site cells

are listed just after the forced
exceptional pairs.
Exceptional pairs have the highest
priority. Forced neighbours are
Force exceptional pairs
top-ranked in the neighbour list.

Forbidden neighbours must not be
listed as neighbours.

11-13

Parameter
Definition
Description
When selecting the Reset option,
U-Net deletes all the current
neighbours and carries out a new
Reset neighbours
neighbour allocation. If not selected,

the existing neighbours are kept.
Table 11-7 Reason of UMTS-GSM automatic neighbour allocation

Reason
Description
Neighbourhood relationship
Forced
defined as exceptional pair
The neighbour is located on
Co-site
the reference transmitter site
Distance
(km)
When
Rank in
the list
Only if the Force

exceptional pairs option
is selected
Only if the Force co-site
as neighbours option is
selected
The neighbour is within the
Only if the Use
maximum distance from the
Coverage Overlapping
reference transmitter
option is not selected
Neighbourhood relationship
Only if the Use
that fulfils coverage
Coverage Overlapping
conditions
option is selected
% of
covered
area
and overlap
2
area (km )
in brackets
Only if the Reset option
Existing
is not selected and in
relationship
case of a new
allocation
Note:
If the Reset button is unchecked and no new neighbour is found after a new allocation,
the Results part stays empty. U-Net only displays the transmitters for which it finds
new neighbours. Therefore, if a transmitter has already reached its maximum number
of neighbours before starting the new allocation, it will not appear in the Results table.
11-14

11.2.5 Allocating GSM Neighbours to CDMA Transmitters

It is possible to automatically define handover relationships between a GSM network
and a CDMA one (CDMA2000 1xRTT 1xEV-DO, IS-95 cdmaOne and UMTS). This
feature enables you to establish a list of inter-technology neighbours in an .atl
document; inter-technology neighbours are stored in database.
If you want to allocate neighbours from GSM document to cells in UMTS document,
you have to create a link from transmitters in GSM into UMTS document (using the
context menu of Transmitters folder in GSM document).
To automatically allocate GSM neighbours (from GSM.atl) to UMTS cells (of
UMTS.atl), proceed as follows:
1)
Create a link on the Transmitters folder of GSM.atl into UMTS.atl.
2)
In the document UMTS.atl, right click on the transmitters folder to get the
related context menu.
3)
Choose the [Cells:Neighbours:Automatic allocation...] command from the

open menu.
4)
Click on the Inter-technology Neighbours tab. Table 11-8 shows the

parameters which automatic neighbour allocation is based on.
button to start calculations
5)
Click the
6)
neighbours for each cell. In addition, it indicates allocation reason for each
neighbour. (see Table 11-9)
7)
button to assign
inter-technology neighbours to cells.

8)
Click the Close button to achieve the procedure.
Table 11-8 UMTS-GSM automatic neighbour allocation parameters

Parameter
Definition
Description
z
This value may be either globally

set for all the transmitters (in the
The maximum number of
automatic allocation algorithm), or
Max
inter-technology
specified for each transmitter (in
number of
neighbours (from the UMTS
the Transmitters table).
neighbours
document) to be allocated
to a transmitter.
U-Net uses the value defined at the

transmitter
level
if
available,
otherwise it considers the global

value.

11-15

Parameter
Max
Inter-Site
distance
Definition
Description
The maximum distance you
If the distance between the reference
can have between the
transmitter and a candidate neighbour
reference transmitter and a
is higher than this value, then the
candidate neighbour.
candidate neighbour is discarded.
The area where the signal

level received from A on the
SA
BCCH TRX type exceeds

the user-defined minimum
Coverage conditions between the
threshold.
reference transmitter (A) and a

candidate neighbour (B) if the option
The area where:

z
The pilot signal received

from the cell B is greater
than
SB
minimum
pilot
signal level.
z
Use Coverage Overlapping is

selected. U-Net determines the
overlapping area between SA and SB
( S A SB ).
The pilot quality from B

exceeds
user-definable minimum
value (minimum Ec/Io).
z
Max
Power :
reduction factor (% of
maximum
powers
contributing to I0) is
applied
to
Power
maximum
contributing
(defined
to Io
properties).
z
Total
the
cell
powers
in
Cell
Power
Used:
No
U-Net takes into account

the total downlink power
used defined for each
cell.
A minimum percentage of
% min
covered area to be
Covered
exceeded in order not to
Area
discard the candidate

neighbour B.
The percentage of covered area is

calculated using this formula
S A SB
SA
.

11-16

Parameter
Definition
Description
This option enables you to force the
co-site cells in the neighbour list of a
Force co-site as neighbours
reference transmitter. The co-site cells

are listed just after the forced
exceptional pairs.
Exceptional pairs have the highest
Calculation
options
priority. Forced neighbours are

Force exceptional pairs
top-ranked in the neighbour list.

Forbidden neighbours must not be
listed as neighbours.
When selecting the Reset option,
U-Net deletes all the current
Reset neighbours
neighbours and carries out a new

neighbour allocation. If not selected,
the existing neighbours are kept.
Table 11-9 Reason of UMTS-GSM automatic neighbour allocation

Reason
Forced
Co-site
Distance (km)
Description
Neighbourhood
Only if the Force
relationship defined as
exceptional pairs
exceptional pair
option is selected
The neighbour is located
Only if the Force
on the reference
co-site as neighbours
transmitter site
option is selected
The neighbour is within
Only if the Use
the maximum distance
Coverage
from the reference
Overlapping option is
transmitter
not selected
% of covered
area
Neighbourhood
and overlap
relationship that fulfils
area (km ) in
coverage conditions
brackets
the list
Only if the Use

Coverage
Overlapping option is
selected

11-17
Rank in
When

Reason
Description
When
Rank in
the list
Only if the Reset

Existing
option is not selected
relationship
and in case of a new
allocation
Note:
If the Reset button is unchecked and no new neighbour is found after a new allocation,
the Results part stays empty. U-Net only displays the cells for which it finds new
neighbours. Therefore, if a cell has already reached its maximum number of
neighbours before starting the new allocation, it will not appear in the Results table.
11.3 Co-Planning Using Databases

11.3.1 Working in Co-planning with a MS Access Database
MS Access users can store only one .atl project in the same database. Nevertheless,
you can create a link between the databases and manage simultaneously tables which
have the same structure as Sites, Antennas, Links or Link equipment tables.
To manage a single table (e.g., Sites table) in an MS Access database, proceed as
follows:
1)
Open the project B.atl in U-Net.
2)
Remove the transmitters from the Transmitters table and sites from the Sites
table.
3)
Export the project B.atl in the database B.mdb.
4)
In the database, open the document B.mdb and delete the Sites table.
5)
In U-Net, open the project A.atl and export it in the database A.mdb.
6)
In the Access database, open the document B.mdb.
7)
Select the Get External Data: Link Tables... command from the File menu.
8)
Select A.mdb from the Link window.
9)
Click on the Link button.
10) Choose the Sites table in the Link tables window,.

11) Press OK to create a Sites table linked to the A.mdb Sites table in B.mdb. Both
tables contain the same objects.

11-18

11.3.2 Working in Co-planning with a SQL Server Database

SQL server users can store several projects .atl in the same database. When
connecting U-Net to the database (exporting a document .atl in the database or
opening a document .atl from the database), you can visualize all the environments .atl
stored in the database in the Choosing a project window and select one of them. Then,
by creating synonyms, you can share tables which have the same structure as Sites,
Antennas, Links or Link equipment tables. This procedure can be carried out only by
the database administrator.
To manage a single table (e.g., Sites table) in an SQL server database, proceed as
follows:
1)
Let the sites of both projects A.atl and B.atl be identical.
2)
Lets assume two users, user A and user B, have been created in the
database.
3)
Open the project B.atl in U-Net, remove the transmitters from the
Transmitters table and sites from the Sites table.
4)
Export the project B.atl in the database by logging on to user B.
5)
In the database, log on to user B and delete the Sites table.
6)
In U-Net, open the project A.atl and export it in the database by logging on to
user A.
7)
In the database, log on to user A.
8)
Click on the Sites table and select the Create a synonym on command from the
associated context menu. The Create synonym window is displayed.
9)
Specify the synonym name (Sites), the name of the schema containing the
synonym (User B), the object type (table), the name of the schema you want to
use (User A), the object which will be the synonym model (Sites).
10) Click on Create to validate the synonym creation in the schema B (user B).
11) Therefore, the user B Sites table is the same than the user A Sites table. Both
tables are linked.
11.3.3 Working in Co-planning with an Oracle Database

Oracle users can store several projects .atl in the same database. When connecting
U-Net to the database (exporting a document .atl in the database or opening a
document .atl from the database), you can visualize all the environments .atl stored in
the database in the Choosing a project window and select one of them. Then, by
creating synonyms, you can share tables which have the same structure as Sites,
To manage a single table (e.g., Sites table) in an Oracle database, proceed as
follows:
1)

11-19

2)
database.
3)
4)
5)
6)
user A.
7)
8)
9)
tables are linked.
11.3.4 Working in Co-planning with a Sybase Database

Sybase users can store several projects .atl in the same database. When connecting
U-Net to the database (exporting a document .atl in the database or opening a
document .atl from the database), you can visualize all the environments .atl stored in
the database in the Choosing a project window and select one of them. Then, by
creating synonyms, you can share tables which have the same structure as Sites,
To manage a single table (e.g., Sites table) in a Sybase database, proceed as
follows:
1)
2)
database.
3)
4)
5)
6)
user A.
7)
8)

11-20

9)
tables are linked.

11-21

Chapter 12 Import MSI PlaNET Data

12.1 Overview
U-Net can import the following data previously created with PlaNET project (version
2.8).
z
Geographic data
Radio data (antennas, network data - sites and transmitters -, carriers)
Neighbours
Propagation Models (possibly path loss matrices)
Text Data Files
CW measurement
This feature is available in any type of project.

U-Net imports PlaNET database even if there are errors or inconsistencies in files to
be imported. Indeed, U-Net imports all the objects, except these which description
syntax is incorrect and data which depend on nonexistent objects (ex: station located
on a site which does not exist). Errors occurred during import are listed and described
in the Events tab of the Event viewer window.
Note:
Each import deletes and recreates all the objects to be imported.
12.2 PlaNET Geo Data Files

12.2.1 PlaNET Geo Data Format
The PlaNET geographic data are described by a set of files regrouped in a PlaNET
directory. The directory structure depends on the geographic data type. U-Net
supports the following objects in PlaNET format:
z
Digital Terrain Model (16 bits)
Clutter classes maps (16 bits)
Raster images (1, 4, 8 and 24 bits)
Vector data
Text data

12-1

I. DTM
The DTM directory consists on three files, the height file and two others:
Index file
The index file structure is simple; it is an ASCII text file which holds positional
information about file. It contains five columns. You can open an index file using any
ASCII text editor. Table 12-1 shows the format of the index file.
Table 12-1 The format of the index file
Field
Acceptable
values
File name
East min
Float
File name: name

Description
of file referenced
by the index file
Field
Acceptable
values
Description
East max
Float
Float
x-axis map coordinate
x-axis map coordinate
of the centre of the
upper-left pixel in
upper-right pixel in
metres
metres
North min
North max
Square size
Float
Float
Float
y-axis map coordinate
y-axis map coordinate of
the centre of the
dimension of a
upper-left pixel in
upper-right pixel in
pixel in metres
metres
metres
Example:
Index file associated with height file (DTM data).

sydney1
303900 343900 6227900 6267900 50
Projection file
The projection file provides information about used projection system. This file is
optional, and it is an ASCII text file with up to four lines. (See Table 12-2)

12-2

Table 12-2 The format of the projection file

Line
Description
Spheroid
No
Zone
No
Projection
No
Central
Latitude and longitude of projection central meridian and
meridian
equivalent x and y coordinates in metres (optional)
Example:
Projection file associated with height file (DTM data).

Australian-1965
56
UTM
0 153 500000 10000000
II. Clutter classes

The Clutter classes directory consists on three files, the clutter file and two others:
Menu file
The menu file, an ASCII text file, defines the feature codes for each type of clutter. It
consists of as many lines (with the following format) as there are clutter codes in the
clutter data files. (See Table 12-3)
Table 12-3 The format of the menu file
Field
Clutter-code
Feature-name
Type
Integer
(>1)
String
Description
Identification code for clutter class
Name associated with the clutter-code. It may contain
spaces
Example:
Menu file associated with the clutter file. (See Table 12-4)

12-3

Table 12-4 Menu file associated with the clutter file

1 open
7 buildings
13 denseurbanhigh
2 sea
8 village
14 blockbuildings
3 inlandwater
9 industrial
15 denseblockbuild
4 residential
10 openinurban
16 rural
5 meanurban
11 forest
17 mixedsuburban
6 denseurban
12 parks
Index file
The index file gives clutter spatial references. The structure of clutter index file is the
same as the structure of the DTM index file.
III. Vector
Vector data contains features such as coastlines, road, etc. Each of these features is
stored in a separate vector file. Four types of file are used, the vector files, where x
and y coordinates of vector paths are stored, and three other files:
Menu file
The menu file, an ASCII text file, lists the vector types stored in the database. The
menu file is composed of one or more records with the following structure (See Table
12-5).
Table 12-5 The format of the menu file
Field
Vector type
code
Type
Identification code for the vector
Integer > 0
type
Vector type
String (up to 32 characters in
name
length)
Note:
The fields are separated by space characters.
Description
Index file

12-4
Name of the vector type

The index file, an ASCII text file, lists the vector files and associates each vector file
with one vector type and optionally, one attribute file. The index file consists of one or
more records with the following structure (See Table 12-6).
Field
Vector file
name
Attribute file
name
Type
Description
String (up to 32
characters in
Filename of the vector file
length)
String (up to 32
characters in
length)
Filename of attribute file associated with the

vector file (optional)
Consist of four fields as follows:
z
Vector
file
eastmin:
minimum
x-axis
coordinate of all vector path points in the

vector file.
z
Vector
file
eastmax:
maximum
x-axis

Dimensions
Real
vector file
z
Vector
file
northmin:
minimum
y-axis

vector file.
z
Vector
file
northmax:
maximum
y-axis

vector file.
Vector type
name
String (up to 32
Name of the vector type which the vector file is
characters in
associated with. This one must match exactly a
length)
vector type name field in the menu file.
Note:
The fields are separated by space characters.
Example:
Index file associated with the vector files (See Table 12-7).

12-5

Table 12-7 Index file associated with the vector files
sydney1.airport
313440 333021 6239426 6244784 airport
sydney1.riverlake
303900 342704 6227900 6267900 riverlake
sydney1.coastline
322837 343900 6227900 6267900 coastline
sydney1.railways
303900 336113 6227900 6267900 railways
sydney1.highways
303900 325155 6240936 6267900 highways
sydney1.majstreets
303900 342770 6227900 6267900 majstreets
sydney1.majorroads
303900 342615 6227900 6267900 majorroads
Attribute file
The attribute file stores the height and description properties of vector paths. This file
is optional.
IV. Image
The Image directory consists of two files, the image file with .tif extension and an index
file with the same structure as the DTM index file structure.
V. Text file
The text data directory consists of:
z
Text data files
The text data files, ASCII text files with the following format:
Airport
637111.188 3094774.00
Airport
628642.688 3081806.25
Each file contains a line of text followed by easting and northing of that text, etc....
z
Index file
The index file, an ASCII text file, stores the position of each text file. It consists of one
or more records with the following structure (See Table 12-8).
Field
File name
Type
Description
Text (up to 32
characters in length)
Filename of the text data file

12-6

Field
Type
East Min
Real
East Max
Real
North Min
Real
North Max
Real
Text feature
Description
Minimum x-axis coordinate of all points
listed in the text data file
Maximum x-axis coordinate of all points
Minimum y-axis coordinate of all points
Maximum y-axis coordinate of all points
Text (up to 32
This field is omitted in case no menu file is
characters in length)
available
Note:
Separator is a blank character.
Example:
railwayp.txt -260079 693937 2709348 3528665 Railway_Station

airport.txt -307727 771663 2547275 3554675 Airport
ferryport.txt 303922 493521 2667405 3241297 Ferryport
Menu file
The menu file, an ASCII text file, which contains the text features. This file is optional.
1 Airport
2 Ferryport
3 Railway_Station
12.2.2 Importing MSI PlaNET Geographic Data

Several types of geographic data coming from PlaNET (version 2.8) can be imported
into U-Net: clutter, DTM, vectors or image. Whatever data, the procedure always
consists in importing an index file either from the File menu, or with drag and drop from
any file explorer application to U-Net.
To import any PlaNET geographic database, proceed as follows:
1)
Select the Import command in the File menu from the menu bar.
12-7

2)
Choose from the File of types scrolling box (See Table 12-9).
Table 12-9 File of types Setting

Option
Operation
1)
Give the path of the index file.
2)
Click the Open button.
3)
Choose from the open window the type of geo
PlaNET Geo data (index)
data to be imported and if you want to embed it

or not in the current .atl U-Net project.
4)
Press
<OK>
to
achieve
the
geographic
database procedure import.

1)
A specific PlaNET data import dialog window

opens.
2)
Check the box(es) associated with the data to

be imported and locate the index file(s) with the
PlaNET database
browser.
3)
Check or modify the projection coordinate

system attached to the geographic data to be
imported.
4)
Press
<OK>
to
achieve
the
geographic
database procedure import.
Notes:
The
button helps you to locate any file by accessing an Open file dialog
window.
z
Selecting the PlaNET Geo data (index) option from the File of types scrolling box
is not compulsory. This option is taken by default when importing an index file.
U-Net also supports as index file all the files which name begins with the string of
character index . U-Net is not case sensitive. Examples: index, Index2,
INDEX.new...
12.2.3 Importing MSI PlaNET Text Data Files

In U-Net, you can import text data coming from PlaNET (version 2.8). The procedure
consists in locating an index file.
To import any PlaNET text data files, proceed as follows:

12-8

1)
2)
Choose from the File of types scrolling box the PlaNET Geo data (index)
option.
3)
Give the path of the index file.
4)
Click the Open button.
5)
In the Data type dialog, select Text data.
6)
Press <OK> to achieve the text data procedure import.
U-Net creates a folder called Text data in the Geo tab; this folder contains all the
objects listed in the index file.
Notes:
Selecting the PlaNET Geo data (index) option from the File of types scrolling box
is not compulsory. This option is taken by default when importing an index file.
U-Net also supports as index file all the files which name begins with the string of
character index . U-Net is not case sensitive. Examples: index, Index2,
INDEX.new...
12.3 Importing a MSI PlaNET Database

12.3.1 Importing a MSI PlaNET Antenna Database
In U-Net, you can import antennas coming from PlaNET (version 2.8). The
procedure consists in locating an index file containing the name of the antennas to
import from the current folder. Standard fields defined in U-Net data structure are
directly imported. Depending on the type of data, other PlaNET fields are imported
and considered as information fields (Other properties tab of the imported data).
Note:
If the database system does not allow the creation of fields by program (e.g. Oracle), it
is necessary to create the new fields in database before importing.
For antennas, the information fields to be created are:

z
FREQUENCY: The design frequency of the antenna
H_WIDTH:The azimuth beamwidth
V_WIDTH:The elevation beamwidth
FRONT_TO_BACK: The ratio of forward antenna gain at 0 and 180 degree

elevation
12-9

z
TILT: Indicates whether the antenna is to be electrically or mechanically tilted
To import a PlaNET antenna database, proceed as follows:

1)
2)
Choose from the File of types scrolling box the PlaNET database option.
3)
A specific PlaNET data import dialog window opens.
4)
Check the box associated with the data to import and locate the linked index
file in the appropriate box.
5)
Press <OK> to achieve the antenna database procedure import.
Note:
The
button helps you to locate any object in directories by accessing to a
classical Open file dialog window.
12.3.2 Importing a MSI PlaNET Network

Network data (only sites or sites and transmitters) from PlaNET (version 2.8) can be
imported into a U-Net document. The procedure consists in selecting an ASCII site
database file and a Flag type file (optional). PlaNET Site database contains 5 flags.
Selecting the Flag type file imports flag names instead of flag values. Take car to
ensure consistency between the imported database and data from the Flag type file.
Standard fields defined in U-Net data structure are directly imported. Depending on
the type of data, other PlaNET fields are imported and considered as information
fields (Other properties tab of the imported data).
Note:
For sites, the information fields to be created are:

z
FLAG_1 to FLAG5: Site status flags (number or flag name if flag types file also
imported)
LAYER: MACRO for macrocell or MICRO for microcell (or empty)
To import a PlaNET network database, proceed as follows:

1)
2)
12-10

3)
4)
Check the box(es) associated with the data to import and locate the linked
file(s) in the appropriate boxes.
5)
Press <OK> to achieve the network database procedure import.
Note:
The
Caution:
z
Transmitters cannot be created without antenna data. When importing a network,

you must make sure that antenna types referenced by sites already exist in the
current project. If not, you must import the appropriate antennas database.
Therefore, select antenna import and ensure a suitable directory path for antennas.
In PlaNET projects, transmitters are characterized by the EIRP (2G). In U-Net 3G

projects, this field is not available, instead of the pilot power has to be defined.
Thus, when importing PlaNET network data, the pilot power is calculated from the
EIRP value as follows: Pilot power = EIRP - antenna gain + emission losses.
12.3.3 Importing a MSI PlaNET Carrier Database

Carrier data from PlaNET (version 2.8) can be imported in GSM/GPRS/EDGE
projects. Standard fields defined in U-Net data structure are directly imported.
Depending on the type of data, other PlaNET fields are imported and considered as
information fields (Other properties tab of the imported data).
Note:
For the carrier import, the information fields to be created are:

z
LAC: Location area code
CELLID: Alphanumeric cell identity

12-11

MOB_COUNTRY_CODE: Mobile Country Code
BSC: Base Station Controller
MSC: Mobile services Switching Centre
Note:
The transmitters are supposed either to exist in the U-Net document or to be imported
first.
To import a PlaNET carrier database, proceed as follows:

1)
2)
3)
4)
5)
Press <OK> to achieve the carrier database procedure import.
Note:
The
12.3.4 Importing a MSI PlaNET Neighbour Database

Neighbour data coming from PlaNET (version 2.8), related to a consistent transmitter
network, can be imported in GSM/GPRS/EDGE or UMTS/CDMA projects.
To import a PlaNET neighbour database, proceed as follows:
1)
2)
3)
4)
5)
Press <OK> to achieve the neighbour database procedure import.

12-12

Note:

The
12.3.5 Importing MSI PlaNET Propagation Model Parameters

U-Net provides an automatic import of PlaNET models. Standard propagation K1 to
K6 values as well as calculation methods and clutter management parameters are
imported. The procedure consists in selecting an index file containing the name of the
models to be imported.
To import a PlaNET propagation model database, proceed as follows:
1)
2)
3)
4)
Check the box associated with the data to import and locate the linked index
file in the appropriate box.
5)
Press <OK> to achieve the propagation models database procedure import.
Note:
The
Caution:
z
It is necessary to know that PlaNET deals with gains contrary to U-Net which
deals with losses. Indeed, for PlaNET a loss is a negative value. Hence, clutter
parameters are the opposite between PlaNET and U-Net. In the same way and
for the same reason, K1 to K6 values are the opposite between PlaNET and
U-Net, except K4 (diffraction parameter) which is considered as a loss.
The automatic import of PlaNET models is supposed to avoid that the user have
to manage any conversion.

12-13

Examples:
Let's imagine a clutter class in a PlaNET project for which is assigned a -10 dB gain.
It is assigned a 10 dB loss (positive value) within the U-Net document.
If a clutter class generates an increase of signal (i.e. 5dB in a PlaNET project), then
U-Net considers a negative loss (-5dB).
12.3.6 Importing MSI PlaNET Path Loss Matrices

Imported path loss matrices are listed in the Result storage window from the context menu
of the Predictions folder. They are locked; thus, new prediction studies performed in U-Net
will just be based on the imported results without recalculating path loss matrices. When
importing PlaNET predictions, U-Net uses signal level and EIRP available in each binary .sig
file to calculate the path loss (EIRP-signal level). This path loss is then used by U-Net as any
path loss result coming from a propagation model.
To import PlaNET path loss matrices, proceed as follows:

1)
2)
3)
4)
Check the box associated with the data to import and locate the linked .sig
directory in the appropriate box.
5)
Press <OK> to achieve the path loss matrices database procedure import.
Note:
The
Caution:
If you change some parameters like grid resolution..., a dialog will warn you about the
fact that calculations will be unlocked. In this case, to perform prediction studies,
U-Net will recalculate the path loss matrices using the default model.

12-14

12.4 Importing MSI PlaNET CW Measurement Data

12.4.1 Importing MSI PlaNET CW Measurement
CW Measurement from PlaNET (version 2.8) may be imported into U-Net. This
feature is available in any type of project. To make the PlaNET survey import easier,
the drag and drop feature is available from any file explorer application to U-Net.
To import a PlaNET CW measurement file in U-Net, proceed as follows:
1)
2)
Right click on the CW Measurements folder to open the associated context

menu.
3)
4)
In the open window, in the type of file box, specify the survey files PlaNET
(*.hd) format.
5)
Precise the path and the name of the file to be imported.
6)
Click
7)
The CW measurement is directly imported in the U-Net environment. PlaNET
to validate your choice.
data are included in U-Net internal fields of the properties window.

8)
Press <OK> to validate.
Note:
Importing PlaNET CW measurement in a UMTS project requires that the measured
transmitter already exists in the project (site + antenna + transmitter - cell). Ensure the
consistency between the cell pilot power in U-Net UMTS project and the EIRP value
defined in the PlaNET document (Pilot power = EIRP transmitter antenna gain +
emission losses).

12-15

Chapter 13 Multi-user Features

13.1 Overview
U-Net is able to store and to exchange (load or refresh) project data in a standard
database.
z
Working with a database allows several users to share the same data without
risking hidden data consistency loss.
To create user configuration files (containing geo file paths and description
(including vector or raster traffic data), computation zone definition, prediction
definitions, folder configurations, macro file paths) that can be exchanged
between users working on the same project.
Once the database is created, it is easily possible for each user to make
modifications and either reloads modified data from the database or refresh
database with pending changes.
Potential data conflicts (e.g. on modified or deleted records), due to other users
actions are detected and the user is assisted in resolving them.
A U-Net document, once connected to a database, keeps memory of the

connection and allows the user to manage data consistency in deferred
processing.
To open a U-Net session from a command line, including several management

options.
Share externalized path loss matrices between users.
13.2 Creating/Starting Database Projects

13.2.1 Operating Principles
At the beginning of a session, you can connect (either creating a new database or a
new atl document from a database) to an existing database and load its data in your
own U-Net new file. At any time during the session, you are able to archive your work
into the connected database, or refresh your document with radio data coming from
the database.
You can perform the following operations:
z
Connection between an existing base and an U-Net new document(see Figure

13-1)

13-1

Figure 13-1 Connection between an existing base and an U-Net new document
z
Export of a current U-Net document data to a database(see Figure 13-2)
Figure 13-2 Export of a current U-Net document data to a database

z
Archive in the database(see Figure 13-3)
Figure 13-3 Archive in the database

z
Refresh from the database(see Figure 13-4)
Figure 13-4 Refresh from the database

13-2

13.2.2 Creating a New Database from a Document

This procedure permits the user to create the reference database that can either be
used by several users or handled easily.
To create a new database from the currently open .atl U-Net document, proceed as
follows:
1)
From the menu bar, select the Database command in the File menu.
2)
Then click on the Export... option from the open menu.
3)
Click on the
button after giving the appropriate name and format
(MS Access, SQL Server, Oracle, and Sybase) to the exported file.
Table 13-1 shows the exported data.
Table 13-1 Exported U-Net data
Class
Sub Class
radio data
Data
sites
Transmitters
Antennas
station templates
microwave links
propagation models
radio parameters
frequency bands
The data which are stored

in database
UMTS or
CDMA/CDMA2000
parameters
Neighbours (internal and
external)
custom fields
units
coordinate systems
The data which are not
Geo data files (or paths)
folder configurations
saved in database
related parameters
study definitions

13-3

Class
Sub Class
Data
computation and focus
zones
traffic maps
The data which are not
Geo data files (or paths)
saved in database
related parameters
Measurements
path loss results
(matrices) and coverage
areas
The user configuration feature allows the user to save Geo data paths and related
parameters, folder configurations, study definitions, and the computation zone. Traffic
maps, measurements and coverage areas can be easily exported. Path loss results
can be shared between users using a central matrix private folder. Matrices can be
also exported in external files to be used in other applications.
13.2.3 Creating a New Document from a Database

This connection must be established when creating a new document. Once connected,
U-Net loads the entire base in your new document. Then connection is interrupted. A
new connection with reference database will be activated only when necessary in
order to enable other user access.
To create a new U-Net document based on data from an existing database, proceed
as follows:
1)
From the menu bar, right click on the File menu, then choose the open from a
database... option from the current menu (if no project is already open) or select
the Database option, then Choose the open from a database... option (if a
project is already open).
2)
Select the database file format (including databases via a Microsoft Data link file
(.UDL)) and name.
3)
button to open the selected database.
Left click on the
Connection procedure is specific to each database type.

Note:
You will have to check the accuracy of the geo data paths (clutter, traffic, etc...) that
may not be valid on your computer.

13-4

13.2.4 Starting U-Net from the Command Line

I. Starting U-Net from the link of U-Net document and database
It is possible to start U-Net from the command line and open a project stored in an
Access or Oracle database by entering the database connection parameters
(user/password/server).
In the command dialog, type the following instruction (see Table 13-2).
Table 13-2 Starting U-Net from the link of U-Net document and database
Database
Instruction
Oracle
C:\Program Files\Huawei GENEX

\U-Net1.0\U-Net.exe -Provider <Provider
name> -Password <User password >
-UserId <User account > -DataSource
<server> -Project <Project account>
Access

\U-Net1.0\U-Net.exe -Provider <Provider
name> -DataSource C:\...\database.mdb
Note:
To identify the provider name, check the connection properties command from the
Database menu in U-Net when the associated database is currently opens (the
Access and Oracle provider names are respectively Microsoft.Jet.OLEDB.4.0 and
MSDAORA.1).
Caution:
Note that Provider, Password, UserId, DataSource and Project parameters are case
sensitive in the instructions above.
II. Starting U-Net from configuration file

The methods for starting U-Net from configuration file are shown in Table 13-3.

13-5

Table 13-3 Starting U-Net from configuration file

Method
Instruction
Command line

\U-Net1.0\U-Net.exe -Provider
<provider_name> -UserId <login_account>
-Password <password> -DataSource
<server> -Project <project_account> -Cfg
C:\....\configuration.cfg
Command line with options

\U-Net1.0\U-Net.exe -Cfg
C:\....\configuration.cfg
Note:
These options can be configured in the U-Net desktop shortcut.
In this case, U-Net is automatically started and the configuration file is loaded when
creating a new project.
13.2.5 Exporting User Configuration to an External File

In U-Net, user configurations can be saved and shared between users. Hence, you
can define some settings in an .atl project and store them in an external file. This file
has a XML (eXtensible Markup Language) international format and .cfg or .geo
extension.
A user configuration file may contain the following information:
z
Geographic data set: Paths of imported geographic maps, map display settings
(visibility scale, transparency, tips text...), clutter description (code, name, height,
model standard deviation and orthogonality factor of each clutter class, default
model standard deviation) and raster or user profile traffic map description.
Computation zone.
Folder configurations: Sort/group/filter configurations and display settings of radio

data folders.
Definition of prediction studies: general information (name, comments, group, sort

and filters), study conditions and display settings.
AFP configuration (this option is available in GSM documents only): Calculation

options selected when starting an AFP session as well as calculation parameters
used for interference histograms.
The paths of macros.

13-6

All these parameters are not stored in a relational database. Therefore, the only way to
share these settings is to create a user configuration file. Then, by importing it, users
are able to work on the same geographic data, have the same data organization and
representation and work out the same prediction studies on a common computation
zone. Moreover, they are able to carry out any modification in their .atl documents
without changing reference for the others.
To export a user configuration in an external file, proceed as follows:
1)
In the Tools menu, select the [User configuration: Save as...] command.
2)
In the User configuration window, select the options you want to export in the file
and then.
3)
Click OK.
4)
In the Save as dialog, browse to find the directory where you want to save the file
and specify its name.
5)
Press OK to validate.
Notes:
z
U-Net can store path of any imported geographic data with any of the supported
formats. Be careful, vectors must be in the same coordinate system as the raster
maps.
Projection and display coordinate systems are not stored (they are stored in the
database).
The different settings (geographic data set, computation zone, folder configurations
and prediction study definition) can be stored independently. The default extension
of user configuration file is .geo when saving either geographic data set, or
computation zone, or both of them.
The different settings (geographic data set, computation zone, folder configurations
and prediction study definition) can be stored independently. The default extension
of user configuration file is .geo when saving either geographic data set, or
computation zone, or both of them.
Since a macro is linked to a U-Net session (and not to an .atl project), the export in
user configurations can be made when an .atl project is open or not.
User configuration files have an international format; they can be used on

workstations with different regional parameters.
U-Net does not store any simulation settings such as parameters entered when
creating simulation or simulation display properties.
Since user configuration files are in standard XML format, they can be open by
XML viewers (and modified and/or improved).

13-7

User configuration files can be created by U-Net, imported into an existing .atl
document (into an U-Net session for macros) and easily exchanged between users.
13.2.6 Importing User Configuration from an External File

User configuration files are one of the tools in U-Net to share data between users.
To import a user configuration from an external file, proceed as follows:
1)
In the Tools menu, select the [User configuration: Import...] command.
2)
In the Open window, click on the Files of type scrolling menu and select
Configuration files (*.cfg).
3)
Specify the directory where the file to be imported is located and its name.
4)
5)
In the User configuration window, check the items you want to import in
your .atl document.
6)
Click OK to validate the import procedure.
When importing a user configuration file including a geographic data set or a study list,
U-Net checks if geographic maps or prediction studies are available in the .atl
document. If it finds a map or a study in the .atl document, it offers new options in the
import dialog, Reset existing geo data and Reset existing studies. Select these
options in order to remove existing geographic maps or studies from the .atl document
before loading the geographic data set or study list described in the user configuration
file.
Notes:
z
If you choose to import a user configuration file, the syntax of the U-Net desktop
shortcut must not contain -Cfg <configuration_file>.
If a configuration file called U-Net.cfg is located in the U-Net installation directory,

this configuration file is automatically loaded when creating a new project (from
template or database).

13-8

Notes:
Since a macro is linked to a U-Net session (and not to an .atl project), the macros
contained in the files referenced by user configurations can be imported only when
no .atl project is open.
If the user tries to import a user configuration containing a macro in an open .atl
project, only the other items will be imported (geo data set, study list, computation
zone, folder configurations, and AFP configuration in GSM documents).
If the user tries to import a user configuration containing only macro information in
an open .atl project, configuration data will not be taken into account.
13.3 Supported Databases

13.3.1 Overview
Four standard databases are presently supported: MS SQL Server, MS Access, and
Oracle via the OLE-DB interface and Sybase using the ODBC interface.
Note:
In addition to the above databases, all the databases that accept .udl files and
support ODBC interface can be accessed (see below).
When possible, U-Net allows you to interactively create your database. Some
databases, MS SQL Server for example, cannot be created by application and need
administrator intervention. It is why U-Net just suggests creating a new MS Access
database. Each database carries its own connection dialog.
13.3.2 Exporting a Project in a MS Access Database

To export a currently open U-Net project in a MS Access database, proceed as
follows:
1)
Choose the Database command from the File menu.
2)
Click Export... from the open menu.
3)
An export dialog box is open.
4)
Choose name and path associated with the database to export.
5)
Select the database format, as shown in Figure 13-5.

13-9

Figure 13-5 Select the database format

6)
Click Save to validate your choice.
Note:
Opening a project from a database use the same syntax.
13.3.3 Exporting a Project in a MS SQL Server Database

To export a currently open U-Net project in a MS SQL server database, proceed as
follows:
1)
2)
3)
An export dialog box opens.
4)
Select the SQL Server Database file format in the appropriate scrolling box, see
Figure 13-6.

13-10

Figure 13-6 Select the SQL Server Database file format

5)
In the open dialog, enter information about with the base to connect to as system
account, server, user name, password.(see Figure 13-7)
Figure 13-7 SQL Server Login

6)
Click OK to complete the export procedure.
Note:
To open a project from a database, use the same syntax.

13-11

13.3.4 Exporting a Project in an Oracle Database

To export a currently open U-Net project in an Oracle database, proceed as follows:
1)
2)
3)
4)
Select the Oracle Database file format in the appropriate scrolling box, see
Figure 13-8.
Figure 13-8 Select the Oracle Database file format

5)
In the open dialog, enter the name, password and server name (as defined in
the tnsnames.ora file) relative to the system account.(see Figure 13-9).
Figure 13-9 Oracle Login

6)
Note:
To open a project from a database, use the same syntax.

13-12

13.3.5 Exporting a Project in a Sybase Database

To export a currently open U-Net project in a Sybase database, proceed as follows:
1)
2)
3)
4)
Select the ODBC data source type in the appropriate scrolling box, see Figure
13-10.
Figure 13-10 Select the Sybase Database file format

5)
In the open dialog, enter information related to the base to connect with as
system account. (see Figure 13-11)
Figure 13-11 Select Data Source of Sybase

6)

13-13

Notes:
By selecting the previous format, all the databases that support OD-BC interface
can be accessed.
Opening a project from a database use the same syntax.
13.4 Data Exchange

13.4.1 Checking Database Connection Properties
To check the connection between the currently open project and the reference
database, proceed as follows:
1)
Left click on the File tool from the toolbar.
2)
Choose the Database command.
3)
Click Connection properties... from the open menu.
4)
A dialog informing you about the current connection is then open.
A specific message box warns you if you are not currently connected to a database.
Note:
You can use this feature to switch from a user/project account to another. When this
made, do not forget to use the refresh command to update your project regarding to
privileges and rules related to the current connection.
13.4.2 Loading Data from a Database

When a database connection is already established, U-Net offers you the possibility to
refresh data in several ways.
To refresh data, proceed as follows:
1)
2)
3)
Click the Refresh option from the open menu.
4)
In the open dialog window, you may modify U-Net pending changes in your linked
database, then refresh only data you did not modify. Or cancel your changes and
reload database as it is.

13-14

13.4.3 Archiving Data in a Database

When a database connection is already established, U-Net offers you to check
precisely the data you want to transfer into the database.
I. Open the Archive dialog window

To open the Archive dialog window, proceed as follows:
1)
2)
3)
Click the Archive... option from the open menu.
II. Methods to display the modified records

z
For each table, U-Net groups changes by type(a field may be updated; a record
may be either deleted or inserted) and displays for each group, the number of
changes in brackets. Furthermore, for the type updated, U-Net details all the
modified fields.
Modified records can be displayed either in table or by group.
To detail differences, just select the modified record or the updated field you want
to check and ask U-Net to show differences. U-Net lists all the fields describing
the record; the modified fields are grey. For each of them, U-Net provides current
and initial values. The initial value is the value of field in the .atl document at the
time of the last exchange with the linked database (this is either the last value you
have archived in the database or the value after the last refresh from the
database).
III. Methods to modify records

z
You can request a global archive of pending changes to the database using Run
all or prefer to run through differences between previous and current data values.
If you prefer to archive step by step, you can select the desired record and
archive it with the Run command.
U-Net also allows you to cancel any of the changes that have been made to your
document by using the Undo command. Therefore, thanks to these features, it is
possible not to archive all the updated fields of a record in database. For example,
if you have modified two fields of a transmitter, you may archive in database one
change only and not the other one. To do this, you must undo the modified field
you do not want to archive and then, select the record and click on Run.
When your changes have been archived, you get either a dialog window indicating
that all modifications have been successfully archived, or a warning dialog about data
conflict. U-Net helps you to manage it (either when modifying or deleting records).

13-15

Note:
The Archive dialog window is available only when some changes have been made
and not already archived.
13.5 Database Conflicts and Consistency

13.5.1 Solving a Conflict on a Modified Record
The record field you modified and you try to archive has already been modified in
the linked database by another user.
For example, you are connected to a MS Access database whose transmitters table
has been modified since your initial load. Indeed, the altitude of transmitter Tx34 has
been increased from 30 to 35 metres (See Figure 13-12).
Figure 13-12 MS Access database modified by another user

In your current project, you have also increased this altitude, but from 30 to 33
metres only (See Figure 13-13).
Figure 13-13 Transmitters table you modified in U-Net

Ignoring that someone already modified this value, you try to archive. Trying to
archive, U-Net detects the conflict and warns you about it with Figure 13-14.
13-16

Figure 13-14 Conflict and Warns

In the open Archive dialog window, if you select the conflicting data, U-Net offers you
to see differences between current and initial values in the document. The initial
values correspond to values of fields in the .atl document at the time of the last
exchange with the linked database (this is either the last values you have archived in
the database or the values after the last refresh from the database) (Show Differences
command) (see Figure 13-15).
Figure 13-15 Show Differences of U-Net document and database

In the Archive dialog window, select the conflicting data and click on the Resolve
command (see Figure 13-16).
Figure 13-16 Archive dialog window

A dialog box summarizing the associated conflict opens. Line(s) in grey represent(s)
the conflict location(s). By checking the box on the left, database will be updated
13-17

with current U-Net data. If you let the box unchecked, U-Net data are loaded from
the linked database (see Figure 13-17).
Figure 13-17 Show the associated conflict

You can then check the database. You check that Tx34 altitude is 33 metres, like in the
current U-Net project (see Figure 13-18).
Figure 13-18 Updated MS Access database after conflict resolving
Note:
Only differences between database and current project on the same field of the same
record can cause a conflict.
13.5.2 Solving a Conflict on a Deleted Record

The record you modified and you try to archive has been deleted from the linked
database by another user.
Somebody deleted the transmitter Tx34 on Site 29. You have modified its altitude on
the current U-Net project and you try to archive.
13-18

When trying to archive, U-Net detects the conflict and warns you about. When using
the Resolve command, U-Net will display the following message, as shown in Figure
13-19.
Figure 13-19 conflict and warns when delete a record

If you choose <Yes>, you recreate the deleted record in the database. Choosing No,
you delete the record in your document as well as in the linked database.
13.5.3 Running an Audit on a Database

In U-Net, a tool allows users to check consistency between the different U-Net tables
(Sites, Transmitters, and so on). This tool is useful if you work either in .atl documents
linked to a central database, or in .atl documents created from a central database that
have been disconnected. In these cases, the .atl documents may contain some
inconsistencies coming from the central database (e.g. some transmitters located on a
site that does not exist in the Sites table...).
To run this audit, in the Tools menu, select Database Audit and choose (see Table
13-4).
Table 13-4 Database Audit Items
Purpose
Item
Result Description
All the objects with foreign keys
may have a problem; integrity
problem actually occurs for
records that have non existing
references (e.g. transmitters
located on a non existing site,
find all the objects with

problems
[Integrity Checking]
transmitters with an antenna that

does not exist in the Antennas
table ...). If integrity problems are
found, U-Net displays a warning
message and proposes you to
delete them. Integrity problems
are solved in the .atl document
but not in the database.

13-19

Purpose
Item
Result Description
Find sites without

transmitters,
transmitters without
subcells, TRXs and
neighbours in
GSM/TDMA
documents, and sites
[Undefined Record
without transmitters,
Checking]
No
transmitters without
cells and cells without
neighbours in UMTS,
IS95-CDMA,
CDMA2000
documents.
Show a list or all the
duplicated records
[Event]
No
Find objects that have

the same identifier
(e.g. sites with the
[Duplicate Record
same name,
Checking]
No
transmitters with the

same name...)
13.6 Management of Multi-users Matrices

13.6.1 Sharing Path Loss Matrices between Users
I. Methods of sharing path loss matrices
In U-Net, some path loss results can be shared by several users. This feature enables
the users both to optimize calculation times and to minimize disk occupation on their
computer by limiting the .atl environment and the externalized calculation matrix sizes.
To use shared calculation matrices, proceed as follows:
1)
In the File menu, select the Database: Refresh command to update your .atl
environment or the Database: Open from a database command to create
your .atl environment. Then, save your environment.
2)

13-20

3)
Right click on the Predictions folder to open the associated context menu, and
then choose the Properties option from the scrolling menu. Or double click on
the Predictions folder.
4)
In order to specify the shared directory to be used, you may either directly edit
the path to access the shared directory, or click on the
button and choose
in the Save as dialog the file Pathloss.dbf included in the shared directory to be
used.
5)
Note:
It is not mandatory to store private path loss matrices in an external folder in order to
access public path loss matrices. Therefore, you may specify a shared directory to be
used even if private path loss matrices are embedded in your .atl document.
II. Fetures of sharing path loss matrices

z
Requires a specific work configuration. Indeed, all the users must be connected
with a central database and the project must be managed by a calculation
administrator (somebody centralizing the calculation result database) also
connected with the database which will provide the calculation matrices by
externalizing its results. The private external path loss matrix folder of the
calculation administrator will be the shared folder which will be used by the other
users.
U-Net performs prediction studies using the shared path loss matrices only when
it does not find the matrices in the user private external folder (or embedded in
the atl project). Therefore, to base the prediction studies exclusively on the
shared matrices, you need to delete the matrices stored in the private external
folder (or embedded in the .atl document) using the Delete command in the
Results window.
U-Net accesses the shared path loss matrices using a read only mode. It
directly reads matrices it needs in the shared directory (these matrices cannot be
locked due to consistency with read only mode).
If a user modifies in its environment some parameters, U-Net detects which

matrices are invalid and recalculates them.
After saving and closing the .atl environment, U-Net keeps only the recalculated
matrices either embedded or in the user private external folder. Therefore, if you
change the height of a transmitter and if you carry out predictions, U-Net will
recalculate only the path loss matrix related to this transmitter and will save it in
the private external folder associated with the .atl environment. The prediction
13-21

studies will be based on the recalculated matrix and on the other matrices coming
from shared directory.
This feature is very useful when several users working on a same project want to
perform predictions on different areas. They can plan the network on their area
and store in their private folder the associated path loss matrices.
Note:
Only the calculation administrator is able to update the shared matrices by refreshing
its .atl environment and then, restarting calculations. The calculation administrator
must feed the calculation matrices only when they are no longer used by the users.
13.6.2 Computing Path Loss Matrices Only

Path loss matrices can be calculated independently of prediction studies. It is
mandatory to have defined a study to obtain path loss matrices calculation (see Table
13-5).
Table 13-5 Computing path loss matrices
Operation
Function
Work out path loss matrices calculation
of all the active transmitters in the group;
From any group of transmitters in the

Transmitters folder, you may select
Calculations and then Calculate path
loss matrices in the context menu.
only invalid matrices or nonexistent

matrices are computed. The
computation zone does not influence the
calculated transmitters and path loss
matrices size; computation is performed
on the whole transmitter calculation
radius.
It is possible to recalculate all the
This feature can be used by a
matrices of the group by choosing the
calculation administrator in order to fill
option "Force path loss matrix
the directory containing the shared path
calculation".
loss matrices.
These features are also available in context menus of a transmitter and the
Transmitters folder.

13-22

Chapter 14 Microwave Links

14.1 Microwave Links Overview
The optional Microwave Links module allows you to define microwave link network, to
display these links on the map, to perform engineering calculations (margin,
availability) and analyze interference globally on the network or for a particular link.
Since several links can share their extremities (either start or end), the description of a
network in U-Net is divided into two folders located in the explorer window.
A Sites folder which contains the set of points that can be used as link extremities. This
folder can also contain sites for 2G/3G networks.
A Links folder which contains the description of the links. Each link refers to two items
in the Sites folder.
Each folder works as the other objects from the explorer window as far as data visibility,
data priority or data display are concerned. Furthermore, each item in the Stations
folder can also be used as a link extremity.
14.2 Creating and Managing a Microwave Link

14.2.1 Creating a Microwave Link Overview
In U-Net, a microwave link can be managed in the same way as sites and transmitters
for example. There are two ways to create a link, either using the mouse or using the
creation wizard. These can also been made directly from the microwave link table.
Microwave links are easy to manage, for display as well as for parameter setup. The
settings are available either in the link itself or in the radio equipment.
14.2.2 Creating a Link Using the Mouse

To create a new microwave link using the mouse, proceed as follows:
button from the tool bar, the pointer shape changes to
1)
Click on the
2)
Left click a first time on the map to locate the start of the new link, the pointer
shape changes to
3)
Left click a second time on the map where to define the link end.

14-1

Note:
You can create a new link directly on the map, either on existing sites or on new
sites automatically created. During the link creation, when placing the pointer near
to an existing site highlights it, indicating that it is a potential extremity for the link.
Otherwise, a new site will be created.
When the link is created, its parameters can be defined in its properties dialog box.
14.2.3 Creating a Link Using the Wizard

To create a new microwave link with creation wizard, proceed as follows:
1)
2)
Right click on the Microwave links folder to open the context menu.
3)
Left click in the scrolling menu on New to start the link creation wizard.
4)
Click the
Note:
button to validate the new microwave link.
Radio equipment must be defined before creating links.
The step 3 of the creation wizard does not allow creating a new equipment.
14.2.4 Listing All Microwave Links of a Network

Like other objects listed in folders (sites, transmitters, coverage studies, etc...), it is
possible to list all the existing microwave links of a network (and its associate
properties) in a table form.
To open the microwave link table, proceed as follows:
1)
2)
Left click on the Data tab of the Explorer window.

Double click on the Microwave links folder or Right click on the Microwave links
folder to open the associated context menu, choose the Open command in the
scrolling menu.
Due to this organization, microwave links table benefits from all the features
usually available in tables (content management, filtering, sorting, etc...).

14-2

14.2.5 Setting Microwave Link Properties

Like for all objects organized in folders (Sites, Transmitters, Antennas, Predictions,
Simulations, measurements, etc...) within U-Net, microwave links can be managed
either individually or globally.
I. Global properties management

In U-Net, you may manage globally the properties associated with all existing
microwave links of your network:
1)
2)
Right click on the Microwave links folder.
3)
4)
Set global properties in the Properties dialog. The properties dialog has 3
standard tab windows are: General, Table, Display (see Table 14-1).
Table 14-1 Global properties dialog

Tab
Description
[General]
Deals with folder organisation and list of

configurations.
[Table]
Helps you to manage contents in the

Microwave links table.
[Display]
Allows you to manage the display of links

depending on their attributes, to manage
the legend, labels on the map, and the
contents of help popups using the tip tool
.
Notes:
The microwave links folder benefits from the generic U-Net display dialog in order
to make its display management easier through, for example, labels, legends,
threshold definition and the tip tool.
If you create a new microwave link, the apply current configuration (or F5: Refresh icon) command gives the colour to new links according to the display
properties of the microwave links folder.

14-3

II. Individual property management

There are two ways to edit properties of each microwave link in the current network.
Method 1:
1)
2)
Expand the Microwave links folder by clicking on the
3)
Right click on the microwave link you want to manage.
4)
5)
Set property in the Properties dialog. The displayed window contains at least 4
tabs (General, Link, Parameters, Display). The Other Properties tab is available if
some user defined fields have been added to the Microwave links table (see
Table 14-2).
Table 14-2 Individual property dialog
Tab
Description
[General]
Deals with the name, the length, and the cluster name of the
current link.
[Link]
Contains the names of antennas, equipment, power and losses

related to each extremity of the current link.
[Parameters]
Assign to the link an environment type, a rain zone and a climate

type.
[Display]
Allows you to manage the colour and the style of the current link.
Method 2:
1)
Select on the map the microwave link you want to manage by left clicking on
the appropriate link.
2)
Right Click the context menu.
3)
4)
Set property in the Properties dialog. The displayed window contains at least 4
tabs (General, Link, Parameters, and Display). The Other Properties tab is
available if some user defined fields have been added to the Microwave links
table (see Table 14-3).
Table 14-3 Individual property dialog

Tab
[General]
Description
Deals with the name, the length, and the cluster name
of the current link.

14-4

Tab
Description
[Link]
Contains the names of antennas, equipment, power

and losses related to each extremity of the current link,
[Parameters]
Assign to the link an environment type, a rain zone and

a climate type,
[Display]
Allows you to manage the color and the style of the

current link.
Note:
You can open the property dialog of the Antennas used at extremities by clicking
the
buttons on the right of the antenna selection boxes in the Link tab.
Some parameters are linked with environmental behaviours. In the Parameters tab,
rain zones (America, Europe and Africa, Asia), Vapour density and atmospheric
refraction (February, May, August, November) are based on map following ITU
recommendations.
14.2.6 Managing Radio Equipment in Microwave Links

The radio equipment is a device with specific power, reception threshold and FKTB
(equipment noise power).
To manage the radio equipment available in the current network, proceed as follows:
1)
2)
Right click on the microwave links folder to open the associated context menu.
3)
Left click in the scrolling menu on Radio equipment....
4)
Precise the names of each piece of equipment and the associated power,
reception threshold, FKTB, and other parameters related to interference
studies and total and fading outage probabilities computations.
5)
Press the Close button to validate.
In addition to power, reception threshold and thermal noise (FKTB), you may specify
the following parameters in the Equipment window, is described below Table 14-4.
Table 14-4 radio equipment parameters
Parameter
Spectrum width
Description
Function
It corresponds to the signal
taken into account to
spreading around the central
determine interferer and

14-5

Parameter
(MHz)
Description
Function
frequency. Spectrum width
interfered sites in interference
depends on the type of
study
modulation supported by
equipment.
Saturation
This parameter enables U-Net
calculate total and fading
(dBm)
to predict signal level
outage probabilities in link
enhancement (paragraph 2.3.3
analysis
in ITUR 530-8
recommendation). Saturation =
E + Received signal. Where E
is the enhancement (dB) not
exceeded for p% of the time.
Signature width
They are used to model signal
(MHz) and depth
distortion due to frequency
(dB)
selective fading and delay

during multipath propagation
(paragraph 5.1 in ITUR 530-8
recommendation).
Correction factor
This term is considered to
discrimination
predict reduction of cross-polar

polarization (XPD) in multipath
or precipitation conditions
(paragraph 4 in ITUR 530-8
recommendation).
Corr. Fact. Discrimination = (Co/I) without XPIC (Cross-polar interference

canceller).
Corr. Fact. Discrimination = (Co/I) - XPIF with XPIC (Cross-polar interference

canceller).
Where (Co/I) is the carrier-to-interference ratio for a reference BER and XPIF is a
laboratory-measured cross-polarization improvement factor.
Caution:
These parameters are taken into account only when the analysis is based on the
ITUR 530-8 recommendation.

14-6

Note:
The XPDg parameter is used during the first step of the prediction. XPDg is the
minimum of the transmitting and receiving antenna bore sight XPDs. U-Net
determines XPDg from cross-polar antenna pattern in case of az = 0 and el = 0 (az
and el are respectively the calculated azimuth and tilt angles).
From this dialog, you can access the IRF dialog by clicking the
button.
Transmission powers and reception thresholds of a link are automatically initialized

with the equipment values when choosing equipment in the Link tab of the link
Properties window.
When no equipment is specified in the link properties, U-Net considers the

following default values: Spectrum width = 100MHz, Saturation = 0 dBm, Signature
width = 0 MHz, Signature depth = 0 dB and Corr. Fact. Discrimination = 0.
You can add customized fields in the equipment table by clicking on the Fields
button.
14.3 Analysis of a Microwave Link

14.3.1 Path Profile and Link Reliability Analysis
I. Adjusting computation parameters in link analysis
Once a microwave link has been correctly build, U-Net can interactively analyze the
signal
level
profile
along
it.
Path
loss
attenuations
are
calculated
from
recommendations:
z
ITU-R PN 525-6 for the losses due to diffraction (with or without corrective term
on Deygout method),
ITU-R PN 525-2 for the free space propagation loss,
ITU-R PN 676-3 for the atmospheric Path losses.
Link analysis, considering the application of these recommendations, is made using

either ITUR 530-3 recommendation (P.530-3) or the ITUR 530-8 one (P.530-8) in
order to calculate total and fading outage probabilities of the link.
To choose parameters used in computations of link analysis, proceed as follows:
1)
Select a link in the Explorer or in the workspace.
2)
Right click on it to open the associate context menu.
3)
Choose the Analysis... command from the context menu.
4)

14-7

5)
Specify longitude and latitude, choose the recommendation and the diffraction
evaluation method you want to use in analysis.
6)
Click OK to close the dialog.
Notes:
U-Net automatically updates analysis report when changing any parameter.
New properties of equipment (signature width and depth, saturation, correction

factor discrimination) are considered in the link analysis only if it is based on ITUR
530-8 recommendation. In this case, U-Net takes into account these parameters to
calculate total and fading outage probabilities of the link.
Computations are related to environmental behaviors. In the Parameters tab of any

link property dialog, rain zones (America, Europe and Africa, Asia), Vapour density
and atmospheric refraction (February, May, August, November) are based on
maps following ITU recommendations.
II. Displaying profile along a microwave link

In U-Net, it is possible to carry out a link analysis in a specific window which displays
the Fresnel ellipsoid along the profile and allows adjusting corrective terms.
To display the propagation analysis window, proceed as follows:
1)
2)
Expand the Microwave links folder by left clicking on the
3)
Right click on the microwave link you want to display the signal level profile to
button.

4)
Left click in the scrolling menu on Analysis....
5)
Click on the Profile tab from the open window.
6)
Set the current microwave link radio parameters.
7)
Note:
z
Antenna heights are generally set up using one or several Fresnel zone clearance
criteria. For example, the ITU recommends a clearance of 60% of the first Fresnel
zone for standard refractivity conditions, and LOS (line of sight) for the worst
conditions.
The Profile tab of the analysis window allows interactive settings of antennas
heights, with real time display of the two different clearance criteria.

14-8

Additional information is available in the Profile tab. A vertical red line indicates the
position of the main edge along the link,
U-Net displays, above the main edge, the diffraction loss (dB) due to this obstacle
( J ( p ) ) in case of the first k value and the distance (m) between the obstacle and the
starting of the link extremity.
Furthermore, you may move cursor along the link and visualize its position on the map.
To do this,
z
click anywhere on the profile to display the cursor;
click on it without releasing the mouse and shift it along the link.
U-Net indicates the following information at the top of the dialog, is described below
Table 14-5.
Table 14-5 Information of profile along a microwave link
Information
Description
The distance (m) between cursor and the
No
starting site of the link

The penetration (h in m) of the Fresnel
Penetration = h(axis) - h(obstacle)
ellipsoid for the first entered k values
h(axis) and h(obstacle) are
(1.33 by default)
respectively height of the Fresnel

ellipsoid axis and the height of the
obstacle.
The ellipsoid radius at the cursor position
No
(F1 in m)
III. Displaying analysis results on a microwave link

U-Net provides a report for the analysis of each link. The report window contains the
radio parameters used as well as the signal profile along, for the worth month and
mean year, the percentage of time during which link is not interrupted by fading
(Quality), and the percentage of time during which the link is not interrupted by rain
(Availability).
To open the statistical report window for any microwave link, proceed as follows:
1)
Click the Data tab in the Explorer window,
2)
3)
Right click on the microwave link for which you want to display the statistical
report,
4)
Left click in the scrolling menu on Analysis...,

14-9
button,

5)
Click on the Report tab from the open window,
6)
Press OK to close the window.
Note:
z
Parameters cannot be edited in the Report tab window. You can set only them in
the Parameters tab window
When using receiver antenna diversity, U-Net takes into account an improvement
coefficient to work out link outage probabilities. This coefficient value is provided in
the Report tab.
IV. Managing the display of a microwave link profile

U-Net allows the user to adjust several parameters in order to manage path profile
display along a microwave link.
To open the signal level propagation display dialog window, proceed as follows:
1)
Click the Data tab in the Explorer window,
2)
Make active the signal profile window,
3)
Right click on signal display zone to open the associated context menu,
4)
Left click in the scrolling menu on Display...,
5)
Adjust the current display parameters on graduations, Fresnel

representation and earth curvature,
6)
Press OK or Apply to validate.
V. Editing profile values (microwave links)

This feature provides a table of values containing the points of the current profile. The
values are displayed over a grid with the best resolution of the current geo data. Each
point is defined with:
z
Distance, in metres, from the link start
Altitude
Clutter class
Clutter height
To open the parameter settings window for any microwave link, proceed as follows:
1)
2)
3)
Right click on the microwave link you want to edit the profile values.
button.
4)
Left click in the scrolling menu on Analysis....
5)
Click on the Profile values tab from the open window.
6)
Displayed data can be accessed and modified (values, clutter class, etc...).
14-10

7)
Note:
In the table, it is possible to create an entire profile either by entering data manually
in the cells, or by using the copy and paste tool with values taken from other
applications (SIG)
button. Moreover, it is also possible to copy
values defining the profile into other applications (SIG) by selecting line(s), and
using the
z
button.
To select the whole table, left click in the top left-hand corner of the table.
14.3.2 Interference Analysis

I. Interference analysis in microwave links: definitions
This function allows you to measure the level of interference generated by the
network on a receiver, or the level of interference generated by a transmitter on all
the receivers in the network. With or without IRF, U-Net checks if there are overlapping
between frequency spectra of links. To do this, U-Net takes into account spectrum
width around each link central frequency.
Note:
If no equipment is defined in the link properties, U-Net considers a 100 MHz spectrum
width.
When studying interference or when preparing a budget, U-Net offers you to compute
diffraction losses with Deygout model, with or without diffraction correction method.
When calculating interference level and the propagation fading, the path loss due to
the directivity of both antennas is taken into account, as well as the path loss due to
the equipment (polarization discrimination, frequency filtering, etc.). The results can be
copied and pasted into a spread sheet to allow you to make further analysis.

14-11

Note:
In order to carry out an interference analysis the radio equipment must be
associated to the links (equipment for which IRF curves have been defined).
Interference analysis can be carried out either on a particular link or on all the links.
II. Finding interferers of a given receiver (microwave links)

To identify the transmitters causing interferences on a given receiver, proceed as
follows:
1)
2)
3)
Right click on the microwave link you want to identify interferers of one of its
button.
extremities.
4)
Left click in the scrolling menu on Interferences....
5)
Check the Find interferers of option from the open window.
6)
Select from the scrolling list the transmitter with which you want to create your
study.
7)
Enter the maximum distance at which the potential interferers must be located
in order to be taken into account.
8)
Select the diffraction computation method (Deygout or modified Deygout

method).
9)
button to run calculations.
Click the
10) If some interferers meet the criteria above, they are displayed in the Results list.
11) Total interference and margin reduction are displayed at the bottom,
12) Press CLOSE to finish.
III. Finding receivers interfered by a transmitter (microwave links)

To identify the receivers interfered by a given transmitter, proceed as follows:
1)
2)
3)
Right click on the microwave link you want to identify interferers of one of its
button.
extremities.
4)
Left click in the scrolling menu on Interferences....
5)
Check the Find interferences victims of option from the open window.
6)
Select from the scrolling list the transmitter you want to study.
7)
Enter the maximum distance at which the potential interfered transmitters must
be located in order to be taken into account.
8)

method).
14-12

9)
Click the
button to run calculations.
10) If some transmitters meet the criteria above, they are displayed in the Results
list.
11) Total interference and margin reduction are displayed at the bottom.
12) Press CLOSE to finish.
IV. Calculating interferences in a global microwave network

U-Net provides a tool allowing the user to find out all the interferences in a network.
To perform a global interference analysis in the current network, proceed as
follows:
1)
2)
Right click on the Microwave links folder in order to open the associated
context menu.
3)
Left click on the Interferences... command from the open scrolling menu.
4)
Enter the maximum distance for potentially interfering sites.
5)

method).
6)
7)
A summary table on interferences opens.
The results obtained in this case correspond to the interference analysis on each link.
Following data are displayed:
z
Link name
Receiver site name
Signal received
Flat margin
Accumulated interferences (Interferences column)
Accumulated margin reduction (Margin reduction column)
Effective margin
V. Interference analysis on microwave links

This function allows you to measure the level of interference generated by all the
network transmitters on a receiver, or the level of interference generated by a
transmitter on all the receivers in the network.
Definitions are described below Table 14-6.
Table 14-6 Definitions about Interference analysis on microwave links
Definition
Description
Interferences of B (interfering link
No
transmitter) on A (interfered link

14-13

Definition
Description
receiver) = Signal received from B

at A - IRF
Signal received from B at A =
No
Transmitted power(B) + Weighted

gain(B) - Losses(B)
Weighted Gain(A), (resp. B)
value of A gain (resp. B) weighted by the

fading values given in the radiation pattern of
A (resp. B) according to the direction of
station B (resp. A). The polarization
difference of the two signals is taken into
account: if the polarizations are different, the
Weighted Gain(A) depends on A cross polar
radiation pattern.
Losses(B)
Free Space Fading

Atmospheric Fading
Diffraction Fading + Weighted Gain(A)
Losses(A)
IRF
IRF (Interference Reduction Factor) =

Receiver filtering protection as a function of
the difference that exists between the central
frequencies of the disturbed signal and of the
disturbing signal (which is user-definable).
FKTB
F: noise figure
K: Boltzmann constant=1.38 10e(-23) J / K
T: noise temperature ~ 290 K
B: passband width (Hz)
Margin reduction and
Margin reduction = 10 log(1+10e
accumulated margin reduction
FKTB)/10
(interferences -
Accumulated margin reduction = 10

log(1+10e
Effective margin
(Total interferences - FKTB)/10
Effective margin = Flat margin

Accumulated margin reduction
Flat margin
Flat margin = Signal received Reception

threshold
14-14

VI. Using IRF in microwave links

IRF (Interference Reduction Factor) is a receiver filtering protection as a function of
the difference that exists between the central frequencies of the disturbed signal and
of the disturbing signal (which is user-definable).
To access the IRF dialog, proceed as follows Table 14-7:
Table 14-7 Access the IRF dialog
Step
Method 1
Method 2
1)
2)
Open the Radio equipment table.
3)
Click the
1)
2)
Right click on the Microwave links folder in order to get the
button.

3)
Choose the IRF option from the context menu.
The open window offers a list of all the possible equipment pairs. Each piece of
equipment paired with other pieces of equipment can be either interfered with or
interferer.
For each pair, you will have to enter, in table form, the values for the deltaF(MHz) and
for the Protection(dB).

z
Notes:
When clicking on the IRF button, U-Net now opens IRF dialog associated to the
selected interfered equipment.
Transmission powers and reception thresholds of a link are automatically initialized

with the equipment values when choosing equipment in the Link tab of the link
Properties window.
When no equipment is specified in the link properties, U-Net considers the

following default values: Spectrum width = 100MHz, Saturation = 0dBm, Signature
width = 0 MHz, Signature depth = 0 dB and Corr. Fact. Discrimination = 0.
You can add customized fields in the equipment table by clicking on the Fields
button.
When no IRF value has been defined for interfering-interferer equipment pairs,
there is no protection and interference are higher.

14-15

VII. Displaying microwave link budgets

This function provides a report on the analysis results for all the links in the current
project.
To obtain the link budgets table, proceed as follows:
1)
2)
Right click on the Microwave links folder in order to open the associated
context menu.
3)
Left click on the Budgets... command from the open scrolling menu.
4)
Choose the diffraction method to use for link budget computation.
For each link, the following data is displayed:

z
Name of the link
Length
Transmitter site name
Azimuth of the transmitter
Downtilt of the transmitter
Receiver site name
Azimuth of the receiver
Downtilt of the receiver
Signal received
Margin value
14.4 ITU maps

14.4.1 ITU Vapour Density on Earth
ITU vapour density on earth is shown in Figure 14-1.

14-16

Figure 14-1 Annual vapour density on Earth (g/m3)
14.4.2 ITU Atmospheric Refraction (February)

ITU atmospheric refraction (February) is shown in Figure 14-2.
Figure 14-2 ITU Percentage of time during which the gradient <=-100 units N/km: February
14.4.3 ITU Atmospheric Refraction (May)

ITU atmospheric refraction (May) is shown in Figure 14-3.
14-17

Figure 14-3 ITU Percentage of time during which the gradient <=-100 units N/km: May
14.4.4 ITU Atmospheric Refraction (August)

ITU atmospheric refraction (August) is shown in Figure 14-4.
Figure 14-4 ITU Percentage of time during which the gradient <=-100 units N/km: August

14-18

14.4.5 ITU Atmospheric Refraction (November)

ITU atmospheric refraction (November) is shown in Figure 14-5.
Figure 14-5 ITU Percentage of time during which the gradient <=-100 units N/km: November
14.4.6 ITU Rain Zones (America)

ITU rain zones (America) are shown in Figure 14-6.

14-19

Figure 14-6 Rain Zones: America
14.4.7 ITU Rain Zones (Europe and Africa)

ITU rain zones (Europe and Africa) are shown in Figure 14-7.

14-20

Figure 14-7 Rain Zones: Europe and Africa
14.4.8 ITU Rain Zones (Asia)

ITU rain zones (Asia) are shown in Figure 14-8.

14-21

Figure 14-8 Rain Zones: Asia

14-22

Chapter 15 Radio Network Dimensioning

15.1 Radio Network Dimensioning Overview
15.1.1 System Overview
The RND (Radio Network Dimensioning) is a tool to assist the 3G network planning,
which is developed based on the 2G and 3G network, the acknowledged advanced
algorithm in the industry and the Huaweis abundant experiences in the radio network
planning.
The RND can implement the dimension tasks of the early network planning, such as
link budget, coverage dimension, capacity dimension, CE number & Iub throughput
dimension and so forth.
15.1.2 Main Functions

The main dimension functions of the RND are as follows.
I. Link budget
The functions are shown in Table 15-1.
Table 15-1 Link budget functions
Sub Functions
Description
Calculate and output the
UL (uplink) Link budget
UL coverage radius of the
Output
z
UE EIRP
Minimum
strength of NodeB
cell
Calculate and output the

DL (downlink) Link budget
DL coverage radius of the
signal
UL path loss
NodeB EIRP (DL)
Minimum
signal
strength of UE
cell
z
DL path loss
II. Network dimension

The purpose of the network dimension is to predict the required NodeB number of an
area under certain adjustment and the required CE number, Iub throughput and so
forth of each NodeB. The functions are shown in Table 15-2.

15-1

Table 15-2 Network dimension functions

Sub Functions
Description
Output
Perform the network dimension

only take the coverage target
Coverage
Dimension
into consideration. This type of

dimension is only used in the
situation that the traffic
information is unknown or the
traffic volume is small.
This method takes the target of
the network building into
consideration, including
coverage and capacity
NodeB area
requirements.
NodeB
needed
In the actual project, this

method is commonly used to
and the capacity are difficult to

be balanced, you can adjust
building.
Real DL load of the

cell
the cell parameters to meet the

requirements of the network
Real UL load of the

cell
predict the required site

number. When the coverage
number
Covered
user
number of the cell

z
Actual user number

of the cell
Iteration
The cell parameters available
Dimension
for adjustment are as follows:
of the network and
cell radius, carrier number,
the actual capacity
target load.
There are three adjustment
ways:
z
Adjust cell radius only
Adjust cell load ->carrier

number ->cell radius
Adjust carrier number->cell

load ->cell radius
The first way is the default one.

Refer to section 15.4 RND
Parameters about the details of
the three dimension methods.

15-2
Target load capacity
CE number
Iub throughput

III. Nodeb ce number dimension

z
Calculate the UL CE number
Calculate the DL CE number
Calculate NULP
Calculate NDLP
IV. Nodeb Iub interface traffic dimension

z
Iub throughput (UL) (common channel)
Iub throughput (DL) (dedicated channel)
Required E1 number (common channel)
Required E1 number (dedicated channel)
15.2 User Interface

15.2.1 Overview
The main interface consists of menu bar, toolbar, [project view] pane, output display
area and status bar.
The [Project view] pane displays the tasks, scene information of the projects in tree
structure and provides the function to switch the contents of the output display area.
The output display area displays the calculation results of the dimension tasks in the
form of table and provides the functions to switch the display mode and export the
result table and so forth.
In the following, we introduce the detailed functions of each interface.
15.2.2 Main Interface

The main interface includes menu bar, project view and output display area. After the
program initializes, the main interface is displayed. If no project is opened or created,
the project view and the output display area contain no content.
Figure 15-1 shows the main interface. In the figure 15-1, there are three projects
opened and displayed cascading in the output display area.

15-3

Figure 15-1 Main interface - three projects opened
15.2.3 Menu Bar

I. Initial menus
Figure 15-2 shows the menus when there is no project opened or created.
Figure 15-2 Initial menus
II. Menus when open or create a project

Figure 15-3 shows the menus when there is project opened or created.
Figure 15-3 Menus when a project opened or created
III. [File] menu

The [File] menu includes the following menu items as shown in Figure 15-4.
The sub menu items are shown in Table 15-3.
Table 15-3 Sub Menus of [File]
Sub Menu
[New]
Description
create a new dimension project
15-4

Sub Menu
Description
[Open]
open a saved project
[Close]
close the current dimension project
[Close All]
close all the opened projects
[Save]
save the current project
[Save As]
save the current project as another file
[Export HTML
export the calculation results of the current project as HTML
File]
format
[Export
export the calculation results of the current project as XML
EXCEL File]
format
[Print Setup]
set the current printer
[Print Preview]
preview the contents to be printed
[Print]
print the current project
Figure 15-4 File menu
IV. [Edit] menu

The [Edit] menu includes the following menu items as shown in Figure 15-5.
15-5


Table 15-4 Sub Menus of [Edit]
Sub Menu
Description
[Undo]
undo the current copied contents
[Copy]
copy the selected contents
[Select All]
select all the content of the current table
Figure 15-5 Edit menu
V. [View] menu
The [View] menu includes the following menu items as shown in Figure 15-6.
Table 15-5 Sub Menus of [View]
Sub Menu
[Tool Bar]
Description
display/hide the standard tool bar and document tool
bar
[Status Bar]
display/hide the status bar
[Tree Bar]
display/hide the [project view] pane
Figure 15-6 View menu
VI. [Tool] menu

The [Tool] menu includes the following menu items as shown in Figure 15-7.
15-6

The sub menu items show in Table 15-6.

Table 15-6 Sub Menus of [Tool]
Sub Menu
[Common
Parameter]
[Advanced
Parameter]
[CE, Iub Common
Parameter]
Description
input the common parameters
input the advanced parameters
calculate the CE number and the Iub traffic
[CE, Iub Advanced
set the advanced parameters related to the CE number
Parameter]
and the Iub traffic
[Calculation Tool]
calculate the feeder loss and the area coverage probability
[Link Balance]
calculate the link balance
[Chart\Link Budget
display the budget cell radius calculated by the link
Cell Radius]
dimension
[Chart\Network
Coverage Budget
NodeB]
[Chart\ Network
Coverage Budget
CE]
[Chart\ Network
Coverage Budget
E1]
[Chart\Network
Iteration Budget
NodeB]
[Chart\Network
Iteration Budget
CE]
[Chart\Network
Iteration Budget
E1]
display the budget NodeB calculated by the network

coverage dimension
display the budget CE calculated by the network coverage

dimension
display the budget E1 calculated by the network coverage

dimension
display the budget NodeB calculated by the network

iteration dimension
display the budget CE calculated by the network iteration

dimension
display the budget E1 calculated by the network iteration

dimension

15-7

Figure 15-7 [Tool] menu
VII. [Window] menu

The [Window] menu includes the following menu items as shown in Figure 15-8.
Table 15-7 Sub Menus of [Window]
Sub Menu
Description
[Cascade]
cascade all the output windows
[Tile]
tile all the output windows
Figure 15-8 [Window] Menu
VIII. [Help] menu

The sub menus are shown in Figure 15-9.

15-8

Figure 15-9 [Help] menu
15.2.4 Shortcut Menu

I. Shortcut menu of the output display area
Right click in the output display area, and then the following shortcut menus appear as
shown in Figure 15-10.
Table 15-8 Shortcut Menu of the Output Display Area
Sub Menu
[Copy]
Description
copy the currently selected contents,
the same as that in the [Edit] menu
Shortcut Key
Ctrl+C
copy all the contents of the output

[Select All]
table, the same as that in the [Edit]
Ctrl+A
menu
[Recalculate]
refresh the output table
[Switch Output
switch the output table from displayed
Mode]
by Year to displayed by Scene
[Export HTML
File]
export the current project as HTML file
[Export Excel
export the current project as EXCEL
File]
file
Ctrl+W
-
F7
F8
Note:
If the input parameters change, click [Recalculate] to run a new calculation. Otherwise,
it only refreshes the output table.
The same below.

15-9

Figure 15-10 Shortcut menu of the output display area
II. Shortcut menu of project (as shown in Figure 15-11)

Table 15-9 Shortcut menu of project
Sub Menu
Description
Shortcut Key
[Copy]
copy the selected project
[Paste]
paste the copied project
[Make
make a duplication of the selected
duplication]
project
[Delete]
[Rename]
delete the selected project or its

duplication
rename the selected project or its
duplication
--
[Common
open a dialog to input the common
Parameter]
parameters
[Advanced
open a dialog to input the advanced
Parameter]
parameters
[Recalculate]
recalculate the current project
Ctrl +W
run the link balance tool
[Link
Balance]

15-10
F3
F4

Figure 15-11 Shortcut menu of project
III. Shortcut menu of project output (as shown in Figure 15-12)

Table 15-10 Shortcut menu of project output
Sub Menu
Description
[Recalculate]
[Switch Output
Mode]
[Export HTML
export the calculation results of the
File]
current project as HTML file
[Export Excel
File]
current projects Excel file
[Delete Link
delete link budget result of the current
Budget]
project
[Delete
Network
Dimension]
delete network dimension results of

the current project

15-11
Shortcut Key
Ctrl+ W
-
F7
F8

Figure 15-12 Shortcut menu of project output

If not all the tasks are created when create a new project, or the link budget or the
network dimension is deleted, you can also add the relevant tasks through the [add]
menu in the shortcut menu. Add dimension task menu is shown in below Figure 15-13.
Figure 15-13 Add dimension tasks
IV. Shortcut menu of project statistics (as shown in Figure 15-14)

Table 15-11 Shortcut menu of project statistics
Sub Menu
Description
[Recalculate]
[Switch Output
Mode]
[Export HTML File]
[Export Excel File]

current project as HTML file
current projects Excel file
[Chart\Link Budget
display the budget cell radius
Cell Radius]
calculated by the link dimension

15-12
Shortcut Key
Ctrl+ W
-
F7
F8

Sub Menu
[Chart\Network
Coverage Budget
NodeB]
[Chart\ Network
Coverage Budget
CE]
[Chart\ Network
Coverage Budget
E1]
[Chart\Network
Iteration Budget
NodeB]
[Chart\Network
Iteration Budget
CE]
[Chart\Network
Iteration Budget
E1]
Description
display the budget NodeB calculated
by the network coverage dimension
display the budget CE calculated by

the network coverage dimension
display the budget E1 calculated by

the network coverage dimension
display the budget NodeB calculated

by the network iteration dimension
display the budget CE calculated by

the network iteration dimension
display the budget E1 calculated by

the network iteration dimension
Figure 15-14 Shortcut menu of project statistics

15-13
Shortcut Key

15.2.5 Tool Bar

I. Standard tool bar(as shown in Figure 15-15)
Figure 15-15 Standard tool bar

Table 15-12 shows the signification of every button.
Table 15-12 Standard tool bar
Button
Description
Create a new dimension project
Open a saved project
Save the current project
Print the current project
Preview the contents to be printed
Copy the current selected contents
Undo the current copied contents
Display/hide the [project view] pane
Calculate the coverage probability
Calculate the CE number and the Iub traffic
II. Document tool bar(as shown in Figure 15-16)
Figure 15-16 Document tool bar

Table 15-13 shows the signification of every button.

15-14

Table 15-13 Document tool bar

Button
Description
Switch the output display from indexed by year to indexed by scene
Export the calculation results of the current project as HTML file
Export the calculation results of the current project as EXCEL file
Open a dialog to input the common parameters
Open a dialog to input the advanced parameters
Open the chart statistics window
15.2.6 Input Interface

I. Selecting task and scene
Setting the scene and task is setting the properties of the project. You can specify the
scene and task when create a new project, or modify the scene and task of an existing
project as shown in Figure 15-17.

15-15

Figure 15-17 Setting the properties of project
II. Input parameters

Input parameters refer to the parameters of the project that need to be input manually,
including common parameter and advanced parameter
1)
Common parameter
[Common Parameter] are the parameters that need to be adjusted constantly. The
common parameters are indexed by YEAR and classified as different scenes. Refer to
15.3.2 Parameters Input for details. Figure 15-18 shows the interface.

15-16

Figure 15-18 Setting common parameters

2)
Advanced parameter
[Advanced Parameter] are the service configuration and default values that seldom
need to be adjusted, including noise and scene, power and sector, CE number and Iub
throughput, dimension method and other input parameters as shown in Figure 15-19.
Refer to section 15.3.2
for details.

15-17

Figure 15-19 Setting the advanced parameters
15.2.7 Output Interface

The output interface includes common output, statistics output and chart output.
I. Common output
Common output includes the link budget output (see Figure 15-20), the network
dimension output (see Figure 15-23) and CE&Iub budget output (see Figure 15-26).
1)
Link budget output
Link budget calculates the UL and DL cell radius of each scene based on the given
propagation model and relevant parameters.
Among which, the input parameters and the calculation results (including intermediate
results) have different background colors.
The back ground color of input parameters is light yellow, the intermediate results is
light blue and the final calculation results and the important intermediate results are
dark blue (the same below).
In Figure 15-20, the Max power of TCH and the Antenna gain are the input
parameters. The Cable loss Tx and the EIRP are the intermediate results. The
Minimum signal required is the important intermediate results.
15-18

Figure 15-20 Link budget output

You can switch the output display mode of the current project to compare the output
results(See Figure 15-21 and Figure 15-22).
Figure 15-21 Indexed by year
Figure 15-22 Indexed by scene

2)
Network dimension output
Network dimension includes coverage dimension and iteration dimension. The

difference of the two dimension methods are shown in Table 15-14.
15-19

Table 15-14 Two types of network dimension

Dimension
Type
Signification
Carries out the dimension based on

Network
the network coverage requirements of
coverage
the target load without considering the
dimension
current traffic requirements. The

current cell radius is fixed.
Interface
As shown in Figure
15-23. Refer to
15.4 RND
Parameters for the
details about the
parameters.
As shown in Figure
Considers both the coverage and the

Network iteration
traffic. The cell radius is flexible. It is
dimension
most commonly used method to carry

out the network dimension.
15-24 and Figure

15-25. Refer to
15.4 RND
Parameters for the
details about the
parameters.
Figure 15-23 Output of the network coverage dimension
Note:
You can switch the output display mode of the current project to compare the output
results.
15-20

Figure 15-24 Network iteration dimension (indexed by year)
Figure 15-25 Indexed by scene

15-21

3)
Ce&Iub dimension output
As a part of the network dimension output, the CE number and Iub traffic budget
output are also classified as network coverage output and network iteration output.
Figure 15-26 shows the CE&Iub results calculated by the network iteration method.
Figure 15-26 CE&Iub budget
II. Statistics output

The statistics output includes list by scene (see Figure 15-27) and by year (see Figure
15-28).
Figure 15-27 List by scene

15-22

Figure 15-28 Statistic by year
III. Chart output

The chart output displays the following statistics results in 2D or 3D chart:
z
Link budget Cell Radius(see Figure 15-29)
Network coverage dimension NodeB number(see Figure 15-30)
Network coverage dimension CE number (see Figure 15-31)
Network coverage dimension E1 number(see Figure 15-32)
Network iteration dimension NodeB number(see Figure 15-33)
Network iteration dimension CE number(see Figure 15-34)
Network iteration dimension E1 number(see Figure 15-35)

15-23

Figure 15-29 Chart statistics cell radius

15-24

Figure 15-30 Chart statistics - network coverage dimension NodeB number (2D)

15-25

Figure 15-31 Chart statistics - network coverage dimension CE number (2D)

15-26

Figure 15-32 Chart statistics - network coverage dimension E1number (3D)

15-27

Figure 15-33 Chart statistics - network iteration dimension NodeB number (2D)

15-28

Figure 15-34 Chart statistics - network iteration dimension CE number (2D)

15-29

Figure 15-35 Chart statistics - network iteration dimension E1 number (3D)
15.2.8 [Project view] Pane

The [Project view] pane displays the index information of the current project in tree
structure, including input and output. You can switch the output display mode through
the menu or button to compare the output results.
I. The [project view] tree structure before switch output mode

By default, the project information is indexed by year, as shown in Figure 15-36.

15-30

Figure 15-36 Project tree structure before switch the output mode
II. The [project view] tree structure after switch output mode
You can switch the output mode to display the output indexed by scene, as shown in
Figure 15-37.
Figure 15-37 Project tree structure after switch the output mode

15-31

15.2.9 Calculation Tool

I. Area coverage probability calculation tool
This tool can calculate the edge coverage probability and the needed slow fading
margin. Enter the area coverage probability, the path loss slope and the standard
deviation of slow fading, and the tool can automatically calculate and output the edge
coverage probability and the needed slow fading margin (see Figure 15-38).
Figure 15-38 Area coverage probability calculation tool
II. Ce number and Iub interface throughput calculation tool

This tool can calculate the required CE number and the Iub interface throughput of
single NodeB. The common parameters and the calculation results are displayed in
the same table (see Figure 15-39). The advanced parameters are consistent with
parameters set in the [CE, Iub] tab in Figure 15-40.

15-32

Figure 15-39 CE&Iub calculation

15-33

Figure 15-40 CE&Iub advance parameter

The [advanced parameters] dialog here is different from the [advance parameter]
dialog of the whole project. When calculate the CE number and Iub throughput of the
NodeB, you can only adjust all the parameters in the [CE, Iub] tab and the Common
channel power ratio (DL) and the NodeB max power (dBm) in the [Scene] tab.
Figure 15-41 shows the [CE, Iub] tab. Figure 15-42 shows the [scene] tab.

15-34

Figure 15-41 CE&Iub calculate- adjustable parameters

15-35

Figure 15-42 CE&Iub Calculate- Un-adjustable parameters
III. Link balance tool

Link balance tool can calculate the Max DL power according to the set conditions
when the UL and DL are balanced.
Figure 15-43 is the condition setting dialog.
Figure 15-43 Link balance input

Figure 15-44 shows the link balance output.
15-36

Figure 15-44 Link balance output

Refer to section 15.3.5 III. Link Balance Tool for details.
15.3 RND Operations

15.3.1 Collecting and Processing Data
You shall input the network parameters before carry out the network dimension,
including radio propagation model, equipment, antenna, channel assignment, sector
parameters, power ratio, target load and service parameters.
The following are the required data to carry out the dimension. These data can be
obtained from the operators and the equipment providers.

15-37

I. Data from the operators(as shown in Table 15-15)

Table 15-15 Data from the operators
Class
Data
Description
the scenes can be divided into dense
urban, urban, suburb, country and
scene
highway
Scene Data
Radio Data
Related to
the scene
coverage area
user number of each
can be calculated from the total user
scene
number to each scenes user number ratio
channel type
penetration loss (dB)
standard deviation of
shadow fading
(indoor/outdoor) (dB)
Sector type
Sector
Parameter
Max carrier number of

each sector
II. Data from equipment providers (as shown in Table 15-16)

Table 15-16 Data from equipment providers
Class
Basic Data
Data
Description
The default value is YES (except for
whether support
highway). The indoor coverage is
indoor coverage
measured by the macro-cell model.
whether use TMA

NodeB receive
The default value is YES

by default, it uses two antenna diversities
diversity
NodeB transmit
by default, it does not use diversity
diversity

15-38

Class
Data
Description
Use the radio propagation model that is
consistent with the network planning tool.
The parameters of the propagation model
propagation model
adopt the calibrated ones. If has not

carried out the model calibration, and then
take the experience value provided by the
equipment providers.
Add a margin when carry out the
dimension margin
dimension considering the difference with

the actual environment.
Max power of TCH

(dBm)
Cell
Max power of TCH
Parameter
traffic channel (dBm)

DL common channel
power ratio
Sector
Neighbor interference
Parameter
factors
obtain this value from the operators
antenna height (m)
antenna gain (dBi)
noise figure (dB)
Antenna
Noise
background noise
level (dBm)
7/8 or 5/4. You can also define the cable
cable type
type
average unit cable

Cable
TMA
loss
the loss of every 100m cable (dB/m)
cable length (m)
cable loss (dB)
cable connector loss
total loss of all the connectors (dB)
TMA filter figure (dB)

15-39

Class
Data
Description
total jumper loss (dB)
CEs per NULP/NDLP
FACH (signaling and

data)
CE, Iub
Margin of burst
service
NodeB O&M
throughput (Kbps)
Active factor
Equivalent CE
number
BLER
Service
Parameters
SupSoftHandover
determine whether support the soft

handover
RBSpeed
the speed of the radio bearer
Bodyloss
the loss caused by body
SHO ratio
III. Data obtained from the current network/protocols/planning target

(generally provided by operators) (as shown in Table 15-17)
Table 15-17 Data obtained from the current network/protocols/planning target
Class
Data
Description
SHO gain (fast

fading)
Radio Data
The parameters can be obtained based
UL frequency (MHz)
Non-orthogonality
on the reference protocols or the

current network data.
factor (DL)
Target
continuous coverage
Service Data
service

15-40

Class
Data
Description
The require Eb/No of the continuous
coverage service. This value can refer
required Eb/No
to the data provided by the equipment

providers
average busy-hour
traffic volume of
CS (Erlang) and PS (kbit)
single user borne by

each service
If the operators do not define it, you can

Gos
adopt the experience value provided by

the equipment provider
cell target load

Other Target
Data
access target
threshold (UL)
area coverage
probability
15.3.2 Parameters Input

I. Common parameters
There are two types of common parameters
z
Only Calculating the Link Budget(see Table 15-18)
Carrying out the Network Dimension only or both the Network Dimension and
Link Budget(see Table 15-19)
Table 15-18 Common parameters when only calculating the link budget
Dense Urban
UL
Continuous
coverage service
NodeB diversity
Sector type
DL
PS64
PS64
No
Antenna
Diversity
3 Sector
15-41

Channel type
TU3
Required Eb/No
2.64
5.39
Max power of TCH
24
31
Indoor coverage
TRUE
TMA used
TRUE
Propagation model
SPM
Note:
After input the service type, channel type, NodeB diversity, the tool automatically
generates the Eb/No value (if use the equipment from other providers, and then obtain
this value from them).
Table 15-19 Common parameters when carrying out the network dimension only or
both the network dimension and link budget
Dense Urban
UL
DL
Continuous coverage service
PS64
PS64
NodeB diversity
2 Antenna
No Diversity
Sector type
3 Sector
Channel type
TU3
Eb/No
2.64
5.39
Max power of TCH(dBm)
24
31
Indoor coverage
TRUE
TMA used
TRUE
propagation model
SPM
Cell load
0.50
area coverage probability
0.95
User number
360,000
15-42
0.75

Coverage area(km2)
20
Max carrier number per sector
Dimension margin
0.15
Gos
0.02
AMR12.2(Erl)
0.0200
0.0200
CS64(Erl)
0.0010
0.0010
PS64(kbit)
560
PS128 (kbit)
PS384 (kbit)
II. Advanced parameters

The advanced parameters include:
z
Global Parameters(see Table 15-20)
Scene Parameters(see Table 15-21)
Dimension method (see Table 15-22)
Sector parameters(see Table 15-23)
CE Number and Iub Throughput(see Table 15-24)
Service Parameters(see Table 15-25)
Standard Propagation Model (SPM)(see Table 15-26)
Asset Propagation Model(see Table 15-27)
NodeB(see Table 15-28)
UE(see Table 15-29)
Table 15-20 Global parameters

NodeB max power
43
(dBm)
Common channel power
ratio
0.25
UL frequency (MHz)
1950
DL frequency (MHz)
2140
SHO gain (fast fading)
1.5
Non-orthogonality factor
0.4

15-43

(DL)
Table 15-21 Scene parameters

Dense
Urban
Urban
Penetration loss
Suburb
Country
Highway
19
13
StdDevIndoor(dB)
11.7
9.4
7.2
6.2
6.2
StdDevOutdoor(dB)
10
30%
30%
30%
30%
30%
(indoor)(dB)
Penetration loss
(outdoor)(dB)
SHO ratio
Table 15-22 Dimension method

Access
threshold (UL)
Access
threshold (DL)
0.50
0.75
Dimension
Adjust cell
method
radius only
Note:
There are three dimension methods: adjust cell radius only, Adjust cell load->carrier
number-> cell radius and Adjust carrier number->cell load->cell radius. Refer to
section 15.4 RND Parameters for details.
Table 15-23 Sector parameters

Omni
2 Sec.
3 Sec.
6 Sec.
InterferenceFactor
0.55
0.55
0.65
0.65
GainofAntenna
11
17
17
20

15-44

Table 15-24 CE number and Iub throughput

CEs per NULP
128
CEs per NDLP
384.00
FACH(singling)
FACH(data)
SHO ratio
0.3
Margin of the burst service
0.25
NodeB O&M Throughput
64.0
(kbps)
Table 15-25 Service parameters

AMR12.2k
CS64k
PS64k
PS128k
PS384k
Active Factor (UL)
0.67
1.00
0.70
0.70
0.70
Active Factor (DL)
0.67
1.00
0.70
0.70
0.70
NodeB CE for UL
1.00
3.00
2.50
5.00
10.00
NodeB CE for DL
1.00
3.00
2.50
5.00
10.00
SupSoftHandover
RBSpeed(kbps)
12.20
64.00
64.00
128.00
384.00
BodyLoss(dB)
3.00
0.00
0.00
0.00
0.00
BLER
0.010
0.001
0.050
0.050
0.050
GOS
0.020
0.050
N/A
N/A
N/A
Table 15-26 Standard propagation model (SPM)

Dense Urban
Urban
Suburb
Country
Highway
k1
27.425
23.455
11.955
23.065
-3.455
k2
44.9
44.9
44.9
44.9
44.9

15-45

k3
5.83
5.83
5.83
5.83
5.83
k4
k5
-6.55
-6.55
-6.55
-6.55
-6.55
k6
Clutter Loss
-20
Suburb
Country
Highway
Table 15-27 Asset propagation model

Dense Urban
Urban

k1
166.52
162.55
151.05
130.64
135.64
k2
N
44.9
44.9
44.9
44.9
44.9
ok3
-2.96
-2.96
-2.96
-2.96
-2.96
e k4
: k5
-13.82
-13.82
-13.82
-13.82
-13.82
k6
-6.55
-6.55
-6.55
-6.55
-6.55
k7
Clutter Loss
-20
Tuning Freq
2130.00
The above SPM and Asset parameter values are the calibrated ones.
Table 15-28 NodeB

NodeB antenna height
(M)
NodeB background
noise (dBm)
30
-200.00
TMA filter figure
0.40
total jumper loss
2.10
cable type
7/8"

15-46

cable loss(dB/100m)
6.11
cable length (m)
30.00
NodeB noise figure(No

TMA, dB)
NodeB noise figure
4.033
2.30
(TMA, dB)
Note:
The total jumper loss includes the loss of all the connectors of the cable and the
loss of the connectors between TMA and cable (if TMA used).
If select typical cable, such as 7/8 or 5/4, the loss of every 100m cable is
automatically calculated. Otherwise, it needs to input the value manually.

z
cable loss = loss of every 100m cable x cable length/100
NodeB noise figure can be automatically calculated based on the cable loss, and
can also be defined manually.
Table 15-29 UE
UE antenna height (M)
1.5
UE antenna gain (dBi)
0.00
UE Noise figure(dB)
1.50
UE background
-200.00
noise(dBm)
cable loss (dB)
0.00
15.3.3 Basic Operation Flow

I. Creating new project
Procedures to create a new project:
1)
Click [File/New] or the [New] button in the toolbar.
2)
In the [Task and Scene] dialog (see Figure 15-45), select the task and scene,
specify the year.
3)
Click <OK>, a new project is created.

15-47

Figure 15-45 Selecting task and scene
Note:
The year span cannot be more than 30 years
II. Opening an existing project

Select [File/Open] or the
button in the toolbar to open an existing dimension
project. Figure 15-46 shows the open dialog.
Figure 15-46 Opening a dimension project

15-48

Note:
RND can only open the project saved by RND while cannot open the XML file
generated by other software.
III. Common parameter input

The input of common parameter includes:
z
Common parameter input when create a new project
Common parameter adjust when open an existing project
They are to be introduced in the following in details.

1)
Common parameter input when create a new project
After selecting the scenes and tasks, the [common parameter] dialog pops up (as
shown in Figure 15-47). You can configure the parameters of different scenes of each
year. For the value of each parameter, refer to 15.3.2 I. for reference. For the
meaning of each parameter, refer to 15.4 RND Parameters.

15-49

Figure 15-47 Setting common parameters

The service type of the PS128k and the PS144k is similar. Therefore they are placed
in the same dropdown list box.
In the [Common parameter] dialog, click the [PS128 (kbit)] item, and you can select
PS144k in the opened dropdown list box (as shown in Figure 15-48). The default one
is PS128k.

15-50

Figure 15-48 PS128k and PS144k

2)
Common parameter adjust when open an existing project
Method 1: use shortcut key (F3) or select [Tool\Common parameter] to open the
[Common parameter] dialog to modify the parameters.
Method 2: right click a year in the [Project view] pane, and then select [Common
parameter] in the opened menu. This is suitable for the situation that there is
more than one year in the current project (see Figure 15-49).

15-51

Figure 15-49 Shortcut menu of the year in the [Project view] pane
Note:
The functions of the shortcut menu of each item in the [project view] pane take effect
for both the item itself and all its sub-items. For example, the [Common parameter] of
the shortcut menu of year 2006 effects all the scenes of year 2006.
IV. Advanced parameter input

The advance parameters are the parameters that do not change constantly. The
methods to modify the advanced parameters are as follows:
z
Method 1: use shortcut key (F4)
Method 2: select [Tool\Advanced Parameter] (see Figure 15-50).
For the value of each parameter, refer to 15.3.2
II. . For the meaning of each
parameter, refer to 15.4 RND Parameters.
Note:
The [advanced parameter] function of the shortcut menu of each item in the [project
view] pane take effect for both the item itself and all its sub-items. When carry out the
calculation, system takes the modified advanced parameter value to calculate the
current item and all its sub-items while takes the former value to calculate other items.

15-52

Figure 15-50 Setting the advanced parameters
V. Calculate the current project

Click <Calculate> button after adjust the common parameters to implement the
calculation.
The <Calculate> button also has the function of saving the parameter settings besides
implementing the calculation.
The calculation progress is shown in the status bar during the calculation. The
calculation results are displayed in the output table after the calculation finishes (see
Figure 15-51).

15-53

Figure 15-51 Calculation results
VI. Recalculate
After adjusting part of or all of the common parameter and advanced parameters, the
current project needs to be recalculated based on the adjusted parameters.
The recalculate methods are as follows:
z
Right click on the project output area and select [Recalculate](see Figure 15-52)
Click the <Calculate> button in the [Common parameter] dialog.
Right click the shortcut menu of a year or a scene in the project view, and then
select [Recalculate]. It is suitable for recalculating a year or a scene.(see Figure
15-53)

15-54

Figure 15-52 [Recalculate] in the project output area
Figure 15-53 [Recalculate] in the [Project view] pane
Note:
After adjusting the parameters, all the adjusted common parameters and advanced
parameters are saved while the calculation results are not refreshed. You must
recalculate to refresh the calculation results.

15-55

VII. Exporting the dimension results

The calculation results can be saved as HTML file or EXCEL file.
z
Method 1: select [File\Export HTML File] or [File\Export Excel File].
Method 2: Press shortcut key F7 or F8.(see Figure 15-54)
Figure 15-54 Export HTML file
Method 3: select button
or
in the toolbar.
Method 4: right click on the output display area and then select [Export HTML File]
or [File\Export Excel File].(see Figure 15-55)
Figure 15-55 The [Export HTML File] in the shortcut menu of output display area
z
Method 5: right click the items in the [project view] pane and then select [Export
HTML File] or [File\Export Excel File].(see Figure 15-56)

15-56

Figure 15-56 The [Export HTML File] in the shortcut menu of [Project view] pane
After select the [Export HTML File], system opens the [Save as] dialog as shown in
Figure 15-57. Click <Save> to save the dimension results as HTML file.
Figure 15-57 Save as HTML file

Figure 15-58 shows the exported HTML file.

15-57

Figure 15-58 The exported HTML file

Figure 15-59 shows the exported Excel file.

15-58

Figure 15-59 The exported excel file
VIII. Copying the dimension results

You can copy part of or all of the output display area (see Figure 15-60) and then paste
them to the editor supporting text format (see Figure 15-61).
Figure 15-60 Copying dimension results

15-59

Figure 15-61 The pasted dimension results
IX. Save the dimension project

The current dimension project can be saved as XML file. The saved file can be opened
by RND.
The save methods are as follows:
1)
Save project. There are three methods (as shown in Table 15-30).
Table 15-30 Save project methods

Method
Shortcut Key
Description
select [File\Save]
CTRL+S
See Figure 15-62.
click the
See Figure 15-63.
button in the
toolbar
Quit the project, system
gives the save prompt
dialog.

15-60

Figure 15-62 Saving a dimension project
Figure 15-63 Save prompt

2)
After select the [Save] menu, system opens the [Save] dialog as shown in Figure
15-64. Specify the saving directory and then click <Save> to save the dimension
project.
Figure 15-64 Saving a project

15-61

X. Managing the dimension project

You can manage the dimension project through the shortcut menu of the items in the
[Project view] pane.
z
Managing the input data
You can implement the following operations on the input year data: copy, paste, make
duplication, delete and rename as shown in Figure 15-65.
Figure 15-65 Managing input data

Table 15-31 Shortcut menu of input data in project view
Sub Menu
[Copy]
[Paste]
[Make
duplication]
Description
Copy all the input parameter value of the current item and its
sub-items to the clipboard
Paste the contents in the clipboard to the current item
(including its sub-items)as its input parameter
Make a duplication of the current item
[Delete]
Delete the current item and all its sub-items
[Rename]
Rename the current item

15-62

Note:
You can only copy and paste the contents to the items of the same level.
If you make a duplication of a scene, system also makes a duplication of the scene
in other year.
If you rename a scene, the scene of the same name in other years is also
renamed.
Managing the link budget and network dimension output data
You can implement the following operation through the shortcut menu of the link
budget and the network dimension (including their sub-items): recalculate, switch
output mode, output dimension results, and delete dimension tasks as shown in Figure
15-66.
Figure 15-66 Managing output data

Table 15-32 Shortcut menu of Link Budget and Network Dimension Output Data
Sub Menu
[Recalculate]
[Switch output
mode]
Description
See section 15.2.4 III.
See section Figure 15-12 and Figure 15-13.
[Export
dimension
See VII. .
results]
[Delete
dimension tasks]
delete the selected task

15-63

z
Output statistics
You can implement the following operation through the shortcut menu of the statistical
(including their sub-items): copy, select all, export HTML file, export excel file and
make a statistical chart, as shown in Figure 15-67.
Figure 15-67 Managing statistics results

Table 15-33 Shortcut menu of statistics output
Sub Menu
Description
[Select all]
select all the statistics output results of the current item
[Copy]
copy the selected contents
[Export
dimension
See VII. .
results]
[Chart]
Display the statistical results as chart, see 15.2.7 III. Chart

Output
15.3.4 Output Results

I. Link budget output
Table 15-34 lists the important intermediate results and cell radius of the link budget.
Refer to section Figure 15-20 for the details about the output interface of link budget.
Refer to 15.4 RND Parameters for the meaning of each parameter.
15-64

Table 15-34 Link budget output parameters

Dense Urban
UL
DL
EIRP(dBm)
18.00
44.47
Noise figure(dB)
2.30
7.00
Receiver sensitivity(dBm)
-125.25
-117.49
Interference margin (dB)
3.01
2.31
Fast fading margin (dB)
2.31
0.96
-138.33
-112.71
Minimum receive signal

strength (dBm)
Slow fading margin(dB)
14.25
SHO gain (fast fading) (dB)
5.94
5.94
Path loss (dB)
129.01
129.87
Cell Radius (km)
0.43
0.45
II. Network dimension output

Network dimension includes network coverage dimension and network iteration
dimension. The output parameters of the two network dimension methods are the
same.
Table 15-35 lists the output results of the network iteration dimension. See section
Figure 15-23 for the details about the interface. See 15.4 RND Parameters for the
meaning of each parameter.
Table 15-35 Network dimension output parameters
Dense
Urban
User density
18000.00

15-65

Dense
Urban
Actual carriers per sector
Cell radius (km)
0.27
NodeB area(km2)
0.14
Real load (UL)
0.41
Real load (DL)
0.75
User number of coverage
832
User number of UL target

load (cell)
User number of DL target
load (cell)
Current real user number
(cell)
User number of target
load (network)
Current real user number
(network)
Real cell area coverage
probability
Real cell edge coverage
probability
NodeB needed
1081
834
832
362790
361920
0.99
0.97
145
III. CE Number and Iub throughput dimension output

Table 15-36 lists the required CE number and the Iub throughput of dense urban.
Refer to section Figure 15-26 for the interface. Refer to 15.4 RND Parameters for the
meaning of each parameter.

15-66

Table 15-36 CE Number and Iub throughput dimension output parameters

Dense
Urban
CEs(UL)
90.00
CEs(DL)
127
NULP
NDLP
Iub throughput
3251.244
(common channel)
E1 number(common
channel)
Iub throughput
3338.33
(dedicated channel)
E1 number(dedicated
channel)
Note:
The above listed CE number and the Iub throughput are the whole network required
ones. While in the next section, what the CE, Iub calculation tool lists is the NodeB
required CE number and Iub throughput.
IV. Statistics output

Calculate the required NodeB number, E1 number and CE number based on year and
scene.
15.3.5 Assistant Tool Operations

I. Ce, Iub calculation tool
This tool can calculate the NodeB required CE number and Iub throughput to help you
evaluate the performance of individual device.
z
Input parameters
Common parameter refers to Table 15-37.

15-67

Table 15-37 Common parameters of CE, Iub calculation tool

User number/NodeB
500
AMR12.2(Erl)
0.0200
0.0200
CS64 (Erl)
0.0010
0.0010
PS64 (kbit)
560
PS128(kbit)
PS384(kbit)
Beside the CE, Iub parameter and the service parameters, the following two parameter
(as shown in Table 15-38) also affect the calculation results:
Table 15-38 Power parameters of CE, Iub calculation tool
NodeB max power
43
(dBm)
common channel
0.25
power ratio (DL)
Output results(see Table 15-39)
Table 15-39 Output results

CEs(UL)
25
CEs(DL)
34
NULP
NDLP
Iub
throughput(common
958.8876
channel)
E1 number(common
channel)
Iub
throughput(dedicated
981.7885
channel)

15-68

E1 number(dedicated
channel)
II. Area edge coverage probability calculation

See section 15.2.9 I. Area Coverage Probability Calculation Tool.
III. Link Balance Tool

Link balance refers to the status in which the UL and DL cell radius are the same. The
link balance tool can calculate the maximum DL power in this status.
z
Setting conditions(see Figure 15-68)
Figure 15-68 Setting link balance conditions

Table 15-40 shows the conditions.
Table 15-40 Link Balance conditions
Condition
Description
No limit of max power
directly display the calculated maximum DL power
(Down)
in the link balance status

Check whether the calculated maximum DL
power is within the specified range. If YES,
Limit of max power (Down)
directly display it. If NO, display the maximum

value of the range as the maximum DL power and
then recalculate the DL cell radius within this
power.

15-69

Note:
If limit the maximum DL power, the maximum value cannot be greater than the
maximum cell power (set in the advanced parameter dialog).
Generally, the gap between minimum value and maximum value is 25dB
To use the link balance function, you must select the link budget when configure
the tasks.
Results Output(see Figure 15-69)
Figure 15-69 Link balance results output
Note:
If you accept the maximum DL power under the balanced status, the value is
considered as the input parameter when implement link budget calculation next time.

15-70

IV. Real-time Calculation

Real-time calculation enables you to check the results of the link budget in real time. If
you modify the parameters of the link budget, the cell UL and DL radius are displayed
in the status bar in real time as shown in Figure 15-70.
Figure 15-70 Real-time calculation
Note:
You must select the link budget when configure the tasks to use the real-time
calculation function.

15-71

15.4 RND Parameters

15.4.1 Input Parameters
I. Scene and task parameters(see Table 15-41)
Table 15-41 Scene and Task Parameters
Parameter
Description
Default
Value
Value
Range
Effect on the
dimension
results
The year
Year
The begin/end years
The next
span cannot
of the dimension
year of the
be more
project.
current year.
than 30
years.
The value of
the following
parameters is
different of
z
Dense
different
Urban(Dense
scene:
Urban)
Scenes
Urban(Urban)
Suburb(Suburban)
Country(Rural
the [Select
All] box is
penetration
-
loss, standard
deviation of
checked.
Area)
z
building
By default,
shadow
fading,
Highway(High
parameters
way)
and SHO gain

of propagation
model and so
forth.
Tasks
Link budget
Network
By default,
the [Select
All] box is
dimension
checked.
II. Common parameters

z
Continuous Coverage Service(see Table 15-42)

15-72

Table 15-42 Continuous Coverage Service parameter

Effect on the
Value
Description
Default value
dimension
results
AMR12.2k voice
AMR12.2
service
64k PS service
CS64
(including VideoPhone
service)
AMR12.2
PS64
128k PS service
(UL, DL)
PS128
144k PS service
PS144
384k PS service
PS384
64k PS service
UL and DL
demodulation
performance
NodeB Diversity(see Table 15-43)
Table 15-43 NodeB Diversity parameter
Value
Default
Description
value
Effect on the
dimension
results
2 antenna
2 Antennas
receive
diversities
UL
link
4 antenna
4 Antennas
receive
UL
2 Antennas
performance
diversities
No Diversity
DL
link
Closeloop-Mode1
Closeloop-Mode2
No Diversity
demodulation
Do not adopt
receive diversity
Close loop
mode 1
No Diversity
Close loop
mode2
Do not adopt
receive diversity

15-73
DL
demodulation
performance

Value
Default
Description
value
Effect on the
dimension
results
Space time
transmit
STTD
diversity
Note:
UL link refers to the NodeB receive diversity methods. Different diversity method
has different Eb/No, which affect the UL path loss.
DL link refers to the NodeB transmit diversity methods. Different transmit diversity
method has different demodulation performance, which affect the DL path loss.
Sector Type(see Table 15-44)
Table 15-44 Sector Type parameter

Value
Omni
2 sectors
3 sectors
6 sectors
Description
Default
Effect on the
Value
dimension results
NodeB has one

sector
NodeB has two
sectors
NodeB has three
sectors
Three
Sectors
NodeB antenna
gain , Interference
factor, NodeB area
NodeB has six

sectors
Channel Type(see Table 15-45)
Table 15-45 Channel Type parameter

Value
Static
Description
-
Default Value
Dense UrbanTU3,

15-74
Effect on the
dimension results

Value
TU3
Description
Default Value
dimension results
Urban walking
UrbanTU30,
Demodulation
speed 3km/hour
Suburb,CountryTU50,
performance,
HighwayHT120
Fast power control
Urban vehicle
TU30
Effect on the
margin, SHO gain
speed
30km/hour
Urban vehicle
TU50
speed
50km/hour
Urban vehicle
TU120
speed
120km/hour
Country vehicle
RA120
speed
120km/hour
Country vehicle
RA250
speed
250km/hour
Highway vehicle
HT120
speed
120km/hour
Required Eb/No
Eb/No refers to the unit bit energy to the total noise density ratio. The value of this
parameter directly affects the receiver sensitivity of the NodeB and UE. This parameter
is also related to the NodeB diversity, power control, channel type, move speed and
BLER and so forth. After set this parameter, the RND can calculate the UL and Dl
Eb/No value.
You can also define the Eb/No value.
z
Indoor Coverage(see Table 15-46)

15-75

Table 15-46 Indoor Coverage parameter

Value
TRUE
Description
Effect on the dimension
value
results
There is indoor coverage.

Consider penetration loss
No indoor coverage, do
FALSE
Default
not consider the
TRUE
Penetration loss, standard
(Highway
deviation of shadow fading
FALSE)
margin
Default
value
results
penetration loss
TMA Used(see Table 15-47)
Table 15-47 TMA Used parameter

Value
Description
TRUE
TMA used
FALSE
TMA not used
NodeB cable loss, NodeB

TRUE
noise figure, UE interference

margin at the receive end
Propagation Model(see Table 15-48)
Table 15-48 Propagation Model parameter

Value
ASSET
COST231
SPM
Description
Default
value
results
ASSET macro-cell
propagation model
COST231-HATApropagation
SPM
model
Coverage radius
Standard propagation model
Different propagation model has different methods to calculate the cell radius. ASSET
and SPM propagation model are semi-experience models, the parameters of which
can be calibrated based on the C/W measurement results. Thus the cell radius is more
precise.
COST231 is experience model, which needs no detailed geographical information. It is
mainly used to implement sketchy dimension.
15-76

Cell Load(see Table 15-49)
Table 15-49 Cell Load parameter

Default
Description
value
UL
0.50(50%)
UL target load
DL
0.75(75%)
DL target load
Effect on the dimension results

UL cell capacity
DL cell capacity, DL cell coverage
radius
Area Coverage Probability(see Table 15-50)
Table 15-50 Area Coverage Probability parameter

Default
value
Dense
Urban
0.95(95%)
Urban
0.92(92%)
Suburb
0.90(90%)
Country
0.90(90%)
Highway
0.90(90%)
Edge coverage probability, slow fading margin
Coverage Area (km2)(see Table 15-51)
Table 15-51 Coverage Area parameter

Default
value
Dense
Urban
20
Urban
80
Suburb
500
Country
1000
Highway
500
User density, cell capacity, required NodeB

15-77

User Number(see Table 15-52)
Table 15-52 User Number parameter

Default
value
Dense
360000
Urban
Urban
240000
Suburb
80000
Country
80000
Highway
40000
User density, cell capacity, required NodeB
Max Carrier Number Per Sector
This parameter is valid only when use the network iteration dimension and the
dimension method contains the adjust carrier number item. The added carrier cannot
surpass this parameter value. The default value is one.
Dimension Margin
Because the planning tool cannot completely simulate the actual radio propagation
environment, therefore, it is necessary to add a margin to the dimension results. The
default value is 0 (0%).
Max Power of TCH (dBm)(see Table 15-53)
Table 15-53 Max Power of TCH parameter

AMR12.2
CS64
PS64
PS128
PS384
UL
21
24
24
24
24
DL
30
36
31
33
37
The required max power of TCH of each bearer affects the EIRP.
z
Gos
Gos (Grade of Service) is the criteria to measure the network congestion. For CS
service, Gos is congestion probability. For PS service, Gos is the probability
requirements under a certain queue delay.
Different scene has different Gos. The default value is 0.02(2%). Refer to
Advanced Parameter for the details about the Gos of each bearer.

15-78

Traffic Volume Information(see Table 15-54)
Table 15-54 Traffic Volume parameter

AMR12.2(Erl
)
CS64(Erl)
PS64(kbit)
PS128(kbit)
PS384(kbit)
UL
DL
UL
UL
UL
UL
DL
0.02
0.02
0.001
0.001
560
Urban
0.02
0.02
0.001
0.001
240
480
560
Suburb
0.02
0.02
0.001
0.001
213
307
209
78
Country
0.02
0.02
0.001
0.001
190
264
195
27
Highway
0.02
0.02
0.001
0.001
190
264
195
27
Dense
Urban
DL
DL
DL
Define traffic volume for the bearer of each scene. The CS service is average
busy-hour traffic, the unit is Erlang. The PS service is average busy-hour throughput,
the unit is kbit.
Note:
The above parameters are all displayed in decimal fraction. For example: 95% is
displayed as 0.95.
III. Advanced parameters

z
Global parameter(see Table 15-55)
Table 15-55 Global parameter

Parameter name
Default
Value
value
range
results
UL frequency(MHz)
1950
Cell radius
DL frequency (MHz)
2140
Cell radius
1.5
Cell radius
SHO gain (fast

fading)

15-79

Parameter name
Non-orthogonality
Default
Value
value
range
results
0.5
factor (DL)
NodeB max power
0-1
43
(dBm)
Common channel
Cell DL capacity
Cell DL capacity
0.25
power ratio (DL)
0-1
Cell DL capacity
Scene parameters
The following parameters of each scene are different and thus affect the calculation of
UL and DL cell radius: building penetration loss, standard deviation of shadow fading
and SHO gain. For the details about the default value of these parameters, refer to
Table 15-23
z
Dimension method(see Table 15-56)
Table 15-56 Dimension Method

Dimension method
Description
The capacity of the whole network is limited.
Adjust cell radius only
Therefore, reduce the cell radius to increase

network capacity
Adjust according to the sequence of increasing
Adjust cell load ->carrier
target load, adding carrier number and reducing cell
number ->cell radius
radius. When the coverage and the capacity are

balanced, stop the adjustment.
Adjust according to the sequence of adding carrier
Adjust carrier number ->cell
number, increasing target load and reducing cell
load->cell radius
radius. When the coverage and the capacity are

balanced, stop the adjustment.
The above three methods are valid only when use network iteration dimension. By
default, the Adjust cell radius only is selected. The access threshold parameters of
the last two methods refer to Table 15-57.

15-80

Table 15-57 Access threshold parameter

Threshold
Default
parameter
value
Access
threshold (UL)
Access
threshold (DL)
Value range
0.5
0-1
UL target load ->UL cell capacity
0.75
0-1
UL target load ->DL cell capacity
The UL and DL access threshold limits the maximum value of the target load. That is,
the target load access threshold.
z
Sector parameters
The sector type determines the antenna gain and interference factor.
z
CE Number and Iub Throughput(see Table 15-58)
Table 15-58 CE Number and Iub Throughput parameter
Parameter name
CEs per NULP
CEs per NDLP
FACH(signaling)
FACH(data)
Description
CE number of
each NULP
CE number of
each NDLP
FACH(signaling)
channel number
FACH(data)
channel number
Default
Value
value
range
Effect on the CE,

Iub dimension
results
128.00
NULP number
384
NDLP number
2.00
Traffic in the DL
common channel
Traffic in the DL
common channel
Channel number,
SHO ratio
0.3
01
total Iub
throughput
Margin of burst
PS service burst
service
probability
NodeB O&M
Throughput (Kbps)
z
0.25
01
The O&M
throughput of
64
Iub
Service parameters
15-81
Total Iub
throughput
Total Iub
throughput

Service parameters contains various types of bearer, the corresponding UL/DL active
factors of each bearer type, UL/DL equivalent CE number, transmit speed, body loss,
BLER and Gos and so forth.
For the default value of these parameters, refer to Table 15-25.
The currently defined bearer types are: AMR12.2, CS64K, PS64K, PS128K, PS144K
and PS384K.
Parameters of Standard Propagation Model
Standard propagation model is based on the following formula:
Table 15-59 shows the parameters.

Table 15-59 Parameters of Standard Propagation Model
Parameter
Description
PR
receive power (dBm)
PTx
transmit power (EIRP) (dBm)
K1
offset constant (dB)
K2
multiplier of log (d)
distance between receiver and transmitter (m)
K3
multiplier of log (HTxeff)
HTxeff
effective height of the transmitter antenna (m)
K4
multiplier of diffraction, K4 must be positive number
Diffraction loss
loss of diffraction (dB)
K5
multiplier of log (HTxeff) log (d)
K6
multiplier of HRxeff
HRxeff
effective height of MS antenna (m)
Kclutter
multiplier of f (clutter)
F (clutter)
average weighted loss of clutter

15-82

You can obtain the value of K1K6 and Kclutter through the propagation model
calibration.
Parameters of Asset Propagation Model
Asset propagation model is based on the following formula:

Lp= K1 + K2log (d) + K3Hms + K4log (Hms) + K5 log (HTxeff)
+ K6 log (HTxeff) log (d) + K7Diffraction + Kclutte
Table 15-60 shows the parameters.
Table 15-60 Parameters of Asset Propagation Model
Parameter
Description
K1
offset constant, which is related with frequency (dB)
K2
multiplier of log (d)
distance between receiver and transmitter (km)
K3
multiplier of Hms
Hms
effective height of MS antenna (m)
K4
multiplier of log (Hms)
K5
multiplier of log (HTxeff)
HTxeff
effective height of transmitter antenna (m)
K6
multiplier of log (HTxeff) log (d)
K7
correction factor of diffraction
Diffraction loss
loss of diffraction (dB)
Kclutter
correction factor of clutter fading
You can obtain the value of K1K7 and Kclutter through the propagation model
calibration.

15-83

Note:
In addition, when you use the Asset propagation model, you need to set the tuning
frequency to calibrate the K1,
For the default value of the tuning frequency, refer to Table 15-27.
Equipment(see Table 15-61)
Table 15-61 Equipment parameter
Parameter name
NodeBantenna
height (M)
NodeBbackground
noise(dBm)
Description
Effect on the
Default
Value range
value
dimension
results
30
-200
Cell radius
Background
noise margin
Transmitter cable
TMA filter figure(dB)
0.4
loss (only affect

DL)
The total jumper

loss of the whole
antenna cable
system, including
the loss of all the
Jumper loss dB)
connectors of the
cable and the
0.3
Transmitter cable
loss
loss of the
connectors
between TMA
and cable (if TMA
used)
Cable type
7/8"
7/8" or5/4". You can
Transmitter cable
also define it.
loss

15-84

Parameter name
Description
Effect on the
Default
Value range
value
dimension
results
If you select a cable

type, RND
automatically
display the cable
Cable loss
Cable loss of
(dB/100m)
every 100m cable
6.11
loss, which can be
Transmitter cable
modified. If you
loss
define a special
type of cable, you
need to specify the
cable loss for it
Cable length (m)
30
0100
Transmitter cable
loss
When you specify

the cable type,
cable length and
unit cable loss, the
NodeB noise
Noise figure when
figure(No TMA )
TMA is not used
4.033
noise figure is
automatically
calculated. You can

also modify the
calculated noise
figure result.
NodeB noise
Noise figure when
figure(TMA used)
TMA is used
UEantenna height
2.3
The same as above
1.5
UENoise figure(dB)
UE cable loss (dB)
-200
(M)
UEantenna gain
(dBi)
UE background
noise(dBm)

15-85
Cell radius
Background
noise margin

If you need to define the NodeB noise figure, you can check the [NodeB noise figure
(No TMA, dB)] box or the [NodeB noise figure (TMA, dB)] box, and then input the noise
figure value, as shown in Figure 15-71.
Figure 15-71 Setting NodeB noise figure
15.4.2 Output Parameters

I. Link budget output
z
EIRP (dBm)
EIRP (Equivalent Isotropic Radiated Power) refers to the product of the power
supplied to the antenna and the antenna gain in a direction relative to an isotropic
antenna.
You can calculate the EIRP through the following formula:
EIRP = max power of TCH (dBm)cable loss at the transit end (dB)body loss (dB) +
transmitter antenna gain (dBi)
z
Noise figure (dB)
Noise figure is an index to evaluate the noise performance of the amplifier.

Noise figure is usually represented by NF. Its definition is the input SNR (signal to
noise ration) to the output SNR ratio of the amplifier.
15-86

NodeB noise figure differs whether the TMA is used or not.(see Table 15-62)
Table 15-62 NodeB noise figure calculation
TMA
Description
Used
The NodeB noise figure = NodeB cable loss + noise figure of the
FALSE
antenna connector when no TMA is used.

The noise figure of the antenna connector when no TMA is used is
2.2dB.
The NodeB noise figure = TMA connector noise figure+ loss of the
cable between TMA and antenna.
TRUE
loss of the cable between TMA and antenna is set as 0.7 dB
The relationship between the TMA connector noise figure and

the cable loss is shown in Table 15-63.
Table 15-63 The relationship between the TMA connector noise figure and the cable
loss
Cable Loss (dB)
Gain of NDDL
NF at TMA
(dB)
connector (dB)
6.00
32
2.60
5.00
31
2.40
4.00
30
2.20
3.00
29
2.10
2.00
28
2.00
1.00
27
1.90
UE noise figure is generally set as 7dB.

z
Receive Sensitivity (dBm)
The receive sensitivity refers to the required signal level at the receiver to meet the
required Eb/ (No+Io).
The receive sensitivity is closely related to the noise figure, channel rate and its
demodulation threshold. You can calculate the receive sensitivity through the following
formula:

15-87

Receive sensitivity = 174 (dBm/Hz) + NF (dB) +10log [1000Rb (kHz)] + required

Eb/No (dB)
Note:
-174(dBm/Hz) is heat noise.
For the UL link, the NF is the noise figure of the antenna connector. For the DL link,
the NF is the UE noise figure.
Rb (KHz) is the bearing rater.
Eb/No can be obtained by checking relevant table.
Interference Margin (dB)
Interference margin refers to the noise rise margin. The bigger the interference margin
is, the higher the load that the network can hold is.
NodeB receive interference margin is only related to the cell UL load threshold. Its
calculation formula is as follows:
NodeB receive interference margin = 10log (1cell UL load threshold).
DL
interference
margin
is
related
(Non-orthogonality factor (DL)),
to
the
following
parameters:
alpha
iRatio (interference from other cell to the
interference from local cell ratio when the UE locates in the edge of the cell),
P max_ NodeB (NodeB maximum power), Load max_ DL (DL load upper
threshold), CL max_ DL (maximum DL coupling loss) and NF _ UE (UE noise
figure).
z
Fast Fading Margin (dB)
It reflects the close loop fast power controls compensation for the fast fading. You can
check its value from relevant table.
z
Minimum Signal Receive Strength (dBm)
It refers to the required minimum signal strength to implement correct demodulation.

Its calculation formula is as follows:
Minimum signal strength requirements (dBm)=receiver sensitivity +cable loss +body
lossreceive
antenna
gain
(dBi)+
interference
margin
+background
noise
marginSHO gain (fast fading) +fast fading margin

z
Slow Fading Margin (dB)
You first calculate the cell edge coverage probability based on the cell area coverage
probability, and then calculate the slow fading margin based on the cell area coverage
probability and slow fading standard deviation.

15-88

z
SHO Gain (Slow Fading) (dB)
The existence of multiple irrespective tributaries of SHO reduces the shadow fading
margin requirements. The gain obtained in this way is called Multi-Cell gain. You can
calculate the SHO gain (slow fading) based on the slow fading standard deviation and
cell edge coverage probability.
z
Path Loss (dB)
The calculation formula of path loss is as follows:

Path loss (dB) = EIRP (dBm)minimum receive signal strength (dBm)building
penetration loss (dB)slow fading margin (dB) +SHO gain (slow fading) (dB)
z
Cell Radius (km)
You can calculate the cell radius based on the path loss (dB), frequency (MHz), UE
antenna height (m), NodeB antenna height (m) and the propagation model.
II. Network dimension output

z
User Density
User density = total user number/coverage area (km2)

z
Real Carrier Number per Sector
It refers to the real carrier number of each sector after adjust the carrier number when
implement the network iteration dimension and select the adjust cell load ->carrier
number ->cell radius or the Adjust carrier number ->cell load ->cell radius dimension
method.
Note:
It is only valid when implement network iteration dimension. In the network coverage
dimension, the real carrier number of each sector is the same with the max carrier
number per sector
Cell Radius
For the network coverage dimension, the output cell radius and the coverage radius
obtained from link budget are the same. For the network iteration dimension, the
output is the cell radius after adjustment.
z
NodeB Area
The NodeB area is calculated based on the sector type and the cell radius.(See Table
15-64)

15-89

Table 15-64 Relationship of NodeB area and the sector type

Sector
type
NodeB area
calculation
formula
Omni
3/ 2 3 R2
2 sectors
3/ 2 3 R2
3 sectors
9 /8 3 R2
6 sectors
3/ 2 3 R2
Note:
For the scene highway, the NodeB area calculation formula is 1.9*R.
Real Load
It refers to the cell load calculated based on the current radius (need to consider DL)
and current cell user number.
z
User Number of Coverage (Cell)
User Number of Coverage (Cell) =cell area User density
Note:
For the network iteration dimension, the user number refers to the cell coverage user
number after the iteration finishes. That is, it is calculated based on the adjusted cell
radius.
User Number of Target Load (Cell)
It refers to the user number calculated based on the target load (the target load is input
manually).
z
Current Real User Number (Cell)
It refers to the actual user number that the current cell can support. The calculation
formula is as follows:
15-90

Current Real User Number (Cell) = MIN (user number of cell UL target load, user
number of cell DL target load, user number of cell coverage)
z
User Number of Target Load (Network)
It refers to the user number of the whole network calculated based on the target load.
The calculation formula is as follows:
Max user number of target load = dimensioned NodeB number sectors of each
NodeB carrier number of each sector MIN (user number of cell UL target load, user
number of cell DL target load)
z
Current Real User Number (Network)
It refers to the actual user number that the current network can support. The
calculation formula is as follows:
Current Real User Number (Network) = dimensioned NodeB number sectors of each
NodeB carrier number of each sector current real user number (cell)
z
Real Cell Area Coverage Probability
It is calculated based on the real load and the cell radius after the iteration finishes.
z
Real Cell Edge Coverage Probability
It is calculated based on the real load, the cell radius after the iteration finishes and the
real cell area coverage probability.
z
NodeB Number Needed
NodeB number needed = coverage area / NodeB area (1+ dimension margin)
III. Ce number and Iub throughput

z
CE Number (UL and DL)
It refers to the CE number that the network needs.

z
NULP and NDLP
The calculation formula is as follows:
NodeB UL / DL CE number
NULP / NDLP =
CEs per NULP / NDLP

Where,
means round up.

NodeB Iub Throughput (Common Channel)
It refers to the NodeB Iub throughput when implement the IMSI-attach or location
update using the common channel.
z
E1 Number (Common Channel)

15-91

It refers to the NodeB required E1 number when implement the IMSI-attach or location
update using the common channel.
z
NodeB Iub Throughput (Dedicated Channel)
It refers to the NodeB Iub throughput when implement the IMSI-attach or location
update using the dedicated channel.
z
E1 Number (Dedicated Channel)
It refers to the NodeB required E1 number when implement the IMSI-attach or location
update using the dedicated channel.

15-92

Appendix Acronyms and Abbreviations

A
AFP
Auto frequence planning
AMR
Adaptive MultiRate
API
Application Program Interface
AS
Active Set
ASCII
American Standard Code for Information Interchange
ASi
Asynchronous Serial Interface
B
BCC
Base station Colour Code
BCCH
Broadcast channel (logical channel)
BCCH-BSIC
Base Station Identity Code
BER
Bit Error Rate
BLER
Block Error Rate
BMP
bitmap
BSC
Base Station Controlle
BSIC
Base Station Identity Code
C
CC
Country Code
CCCH
Common Control Channel
CCH
Common transport channel
CD
Compact Disk
CDMA
Code Division Multiple Access
CD-ROM
Compact Disc-Read Only Memory
CE
Channel Element
CPU
Center Processing Unit
CS
Circuit Switched (CS) domain
CW
Continuous Wave
D
DCS1800
Digital Distribution System at 1800MHz
DEM
Digital Elevation Model

F-1

DL
Downink
DTM
Digital Elevation Model
DTX
Discontinuous Transmission
E
EGPRS
Enhanced GPRS
EIRP
Equivalent Isotropically Radiated Power
F
FACH
Forward Access Channel
FCH
Fundamental Channel
G
GOS
Grade of Service
GPRS
General Packet Radio Service
GPRS-EDGE
Enhanced Data rates for GSM Evolution
GRPS
General Packet Radio Service
GSM
Global System for Mobile communications
GSM-TDMA
Time Division Multiple Access
GUI
graphical user interface (gui)
H
HCS
Hierarchical Cell Structure
HDR
High-availability Data Replication
HR
Half Rate
HSN
Hopping Sequence Number
I
IMSI
International Mobile Station Identity
IS-95
Interim Standards 95
IST
Immediate Service Termination (IST)
ITU
International Telecommunications Union
ITU-R
International Telecommunication Union -Radiocommunication Sector
K
KPI
Key Performance Index
L
LAC
Location Area Code
LOS
Line of sight

F-2

M
MAIO
Mobile Allocation Index Offset
MAP
Mobile Application Part
MSC
Mobile Switching Center
MUD
Multiuser detection
N
NCC
Network Color Code
BCC
Base station Colour Code
N-CDMA
Narrowband CDMA
NF
Noise Figure
O
ODBC
Open Database Connectivity
OVSF
Orthogonal Variable Spreading Factor
P
PER
Packed encoding rules
PN
Pseudo Number
PS
Packet Switched
Q
QoS
Quality of Service
R
RA
Rural Area
RC
Rate Configuration
RND
Radio Network Dimensioning
RTT
Radio Transmission Technology
S
SCH
Synchronization CHannel
SFH
Synthesizer Frequency Hopping
SHO
Soft Handover
SPM
Standard Propagation Model
STTD
Space Time Transmit Diversity
T
TCH
Traffic Channel
TDMA
Time Division Multiple Access

F-3

TMA
Tower Mounted Amplifier
TRX
Transceiver
TU
Typical Urban
U
UE
User Equipment
UMTS
Universal Mobile Telecommunication System
UTM
Universal Transverse Mercator
W
WCDMA
Wideband CDMA
WGS
World Geodetic System
WLL
Wireless Local Loop
X
XML
Extensible Mark-up Language
XPIC
Cross-polar interference canceller
XPIF
cross-polarisation improvement factor

F-4

GENEX U-Net Wireless Network Planning Software User Manual-Volume II PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

GENEX U-Net Wireless Network Planning Software User Manual-Volume II PDF

Caricato da

Copyright:

Formati disponibili

HUAWEI

GENEX U-Net Wireless Network Planning Software

Huawei Technologies Proprietary

GENEX U-Net Wireless Network Planning Software

Huawei Technologies Co., Ltd.

Huawei Technologies Proprietary

Copyright 2005 Huawei Technologies Co., Ltd.

All Rights Reserved

, HUAWEI, C&C08, EAST8000, HONET,

, ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium,

Huawei Technologies Proprietary

Huawei Technologies Proprietary

About This Manual

Chapter 8 UMTS/WCDMA Project Management introduces the use of U-Net in the

Technical marketing specialists

Operation & maintenance personnel

Telecommunication administration staff

Normal paragraphs are in Arial.

Warnings, cautions, notes, table text and tips are in Arial

Huawei Technologies Proprietary

II. Command conventions

The keywords of a command line are in Boldface.

Items (keywords or arguments) in square brackets [ ] are

A line starting with the # sign is comments.

III. GUI conventions

Button names are inside angle brackets. For example, click

Window names, menu items, data table and field names

Multi-level menus are separated by forward slashes. For

IV. Mouse operation

Press the left button or right button quickly (left button by

Press the primary mouse button twice continuously and

Caution, Warning, Danger: Means reader be extremely careful during the

Huawei Technologies Proprietary

User Manual - Volume II

User Manual - Volume II

9.4 Managing CDMA/CDMA2000 Radio Data......................................................................... 9-4

Huawei Technologies Proprietary

User Manual - Volume II

Chapter 11 Co-planning Features.............................................................................................. 11-1

User Manual - Volume II

13.3.4 Exporting a Project in an Oracle Database....................................................... 13-12

User Manual - Volume II

15.2.3 Menu Bar............................................................................................................. 15-4

Huawei Technologies Proprietary

User Manual - Volume II

Chapter 8 WCDMA/UMTS Project Management

User Manual - Volume II

8.2 UMTS Specific Concepts

Then, it generates bin-based coverage probability predictions (prediction part).

See UMTS projects protocol.

Huawei Technologies Proprietary

User Manual - Volume II

U-Net enables WCDMA/UMTS network planning, 3G network based on Wideband

8.3 UMTS Projects Protocol

Setting radio data

Pilot studies based only on signal reception

Traffic map design

Realistic user distribution

Power control simulation

Primary scrambling code

Huawei Technologies Proprietary

User Manual - Volume II