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

HUAWEI
GENEX U-Net Wireless Network Planning Software

User Manual - Volume I
V100R001
Huawei Technologies Proprietary

GENEX U-Net Wireless Network Planning Software
User Manual
Volume Volume I
Manual Version T2-030183-20050205-C-1.10
Product Version V100R001
BOM 31014583
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 Notes

T2-030183-20050205-C-1.10 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
z Operation & maintenance personnel
z Telecommunication administration staff
Conventions
The manual uses the following conventions:
I. General conventions
Convention Description
Arial Normal paragraphs are in Arial.
Warnings, cautions, notes, table text and tips are in Arial
Arial Narrow
Narrow.

II. Command conventions
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
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
Press the left button or right button quickly (left button by

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

Double-Click
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.

GENEX U-Net Wireless Network Planning Software Table of Contents
Table of Contents
Chapter 1 Getting Started............................................................................................................. 1-1

1.1 Summary............................................................................................................................ 1-1
1.2 Features in U-Net 1.0 ........................................................................................................ 1-2
1.2.1 General Features .................................................................................................... 1-2
1.2.2 Features for GSM/GPRS/EDGE Projects ............................................................. 1-10
1.2.3 Features for WCDMA/UMTS Projects................................................................... 1-13
1.2.4 Features for CDMA/CDMA2000 Projects ............................................................. 1-15
1.3 Installing and Removing U-Net ........................................................................................ 1-17
1.3.1 System Requirements........................................................................................... 1-17
1.3.2 What's Installed with U-Net ................................................................................... 1-17
1.3.3 Installing U-Net...................................................................................................... 1-17
1.3.4 Removing U-Net.................................................................................................... 1-19
1.3.5 Installing Distributed Computing Server................................................................ 1-20
1.3.6 Removing Distributed Computing Server.............................................................. 1-20
1.3.7 Troubleshooting after Installation .......................................................................... 1-21
1.4 Getting Help ..................................................................................................................... 1-22
1.4.1 Ways to Get Assistance ........................................................................................ 1-22
1.4.2 Technical Support ................................................................................................. 1-24
1.5 Running Project Templates ............................................................................................. 1-24
1.5.1 Starting a New Project .......................................................................................... 1-24
1.5.2 Templates Provided .............................................................................................. 1-24
1.5.3 Creating Your Own Template................................................................................ 1-26
1.5.4 Building a Project Step by Step............................................................................. 1-28
Chapter 2 The Working Environment .......................................................................................... 2-1

2.1 Overview ............................................................................................................................ 2-1
2.2 Working with Menus and Windows.................................................................................... 2-2
2.2.1 Working with Document Window ............................................................................ 2-2
2.2.2 Working with Docking or Floating Window.............................................................. 2-2
2.2.3 Printing the Active Window ..................................................................................... 2-3
2.3 Working with Maps............................................................................................................. 2-3
2.3.1 Zooming and Panning ............................................................................................. 2-3
2.3.2 Using the Panoramic Window ................................................................................. 2-4
2.3.3 Centering the Map................................................................................................... 2-5
2.3.4 Choosing a Scale .................................................................................................... 2-5
2.3.5 Defining Visibility Ranges on Objects ..................................................................... 2-6
2.3.6 Displaying Rulers around the Map .......................................................................... 2-6
2.3.7 Point-to-Point Analysis ............................................................................................ 2-7
i
2.3.8 Getting Distances on the Map................................................................................. 2-8

2.3.9 Displayed Cursors ................................................................................................... 2-9
2.3.10 Printing a Map ..................................................................................................... 2-12
2.3.11 Exporting Maps to External Files ........................................................................ 2-13
2.3.12 Exporting Maps to Other Applications................................................................. 2-13
2.4 Working with the Explorer................................................................................................ 2-15
2.4.1 Overview ............................................................................................................... 2-15
2.4.2 Renaming an Object ............................................................................................. 2-16
2.4.3 Displaying the Object Properties........................................................................... 2-16
2.4.4 Deleting an Object................................................................................................. 2-16
2.4.5 Managing Object Visibility ..................................................................................... 2-17
2.5 Working with Data Tables................................................................................................ 2-18
2.5.1 Accessing Data Table ........................................................................................... 2-18
2.5.2 Managing Contents in Tables ............................................................................... 2-18
2.5.3 Editing Contents in Tables .................................................................................... 2-19
2.5.4 Opening Dialogs from Tables................................................................................ 2-20
2.5.5 Managing Table Display........................................................................................ 2-21
2.5.6 Copying and Pasting in Tables ............................................................................. 2-24
2.5.7 Exporting Tables in External Files......................................................................... 2-25
2.5.8 Importing Tables from External Files .................................................................... 2-26
2.5.9 Printing Data Tables.............................................................................................. 2-27
2.6 Filtering/Grouping/Sorting Data ....................................................................................... 2-27
2.6.1 Sorting and Filtering in Tables .............................................................................. 2-27
2.6.2 Examples of Filter in Tables.................................................................................. 2-29
2.6.3 Filtering Radio Data .............................................................................................. 2-31
2.6.4 Advanced Filtering Example ................................................................................. 2-33
2.6.5 Advanced Filtering Counter Example 1 ................................................................ 2-34
2.6.6 Advanced Filtering Counter Example 2 ................................................................ 2-35
2.6.7 Sorting a Folder..................................................................................................... 2-36
2.6.8 Arranging Items in Groups .................................................................................... 2-37
2.6.9 Examples of Grouping by...................................................................................... 2-38
2.6.10 Using a Group by/Sort/Filter Configuration ......................................................... 2-39
2.6.11 Creating Subfolders ............................................................................................ 2-40
2.6.12 Reorganizing Data after Modifications ................................................................ 2-41
2.6.13 Filtering Data in a Polygon .................................................................................. 2-41
2.6.14 Removing the Polygon Filter ............................................................................... 2-42
2.7 Managing Display in U-Net .............................................................................................. 2-42
2.7.1 Defining the Display Properties of Any Item Folder .............................................. 2-42
2.7.2 Managing and Displaying Legends ....................................................................... 2-43
2.7.3 Thresholds, Colours and Legends ........................................................................ 2-44
2.7.4 Displaying Object Labels on the Map.................................................................... 2-45
2.7.5 Using the Tips Tool to Get Information ................................................................. 2-46
ii
2.8 Using Handy Tools........................................................................................................... 2-47

2.8.1 Using the Undo/Redo Command .......................................................................... 2-47
2.8.2 Refreshing Maps and Folders ............................................................................... 2-47
2.8.3 Setting Document Prints ....................................................................................... 2-48
2.8.4 Locating Any Point on the Map ............................................................................. 2-48
2.8.5 Locating any Site on the Map................................................................................ 2-49
2.8.6 Locating any Vector on the Map ........................................................................... 2-50
2.8.7 Synchronizing Vector Selection and Data Table................................................... 2-51
2.8.8 Using the Status Bar to Get Information ............................................................... 2-52
2.8.9 Using Icons from the Tool Bar............................................................................... 2-52
2.8.10 Using Shortcuts in U-Net..................................................................................... 2-55
2.9 Tips and Tricks................................................................................................................. 2-57
2.9.1 How to Import Geo Data Easily............................................................................. 2-57
2.9.2 How to Change Globally a Value for All the Transmitter ...................................... 2-57
2.9.3 How to Find Easily a Site on the Map ................................................................... 2-57
2.9.4 How to be Automatically Placed in the Find Site Box ........................................... 2-57
2.9.5 How to Delete All Sites and Their Transmitters in One Shot ................................ 2-57
2.9.6 How to Access the Properties of Any Object or Group of Objects........................ 2-58
2.9.7 How to Filter Data Rapidly .................................................................................... 2-58
2.9.8 How to Work Only on Live Sites............................................................................ 2-58
2.9.9 How to Use Wildcard Characters to Filter Text-format Fields............................... 2-58
2.9.10 How to Change Globally the Names of All the Sites........................................... 2-59
2.9.11 How to Find Easily an Object by Its Name in a Folder ....................................... 2-59
2.9.12 How to Open or Close Rapidly a Folder ............................................................. 2-59
2.9.13 How to Find Easily an Object in a Table ............................................................. 2-60
2.9.14 How to Find Easily an Object on the Map........................................................... 2-60
2.9.15 How to Customise the Columns Displayed in a Table ........................................ 2-60
2.9.16 How to Customise the Table Style ...................................................................... 2-60
2.9.17 How to Change Globally Display Properties of Objects...................................... 2-60
2.9.18 How to Predict Signal Level on a Road .............................................................. 2-60
2.9.19 How to Work on a Set of Sites Selected by a Polygon ....................................... 2-61
2.9.20 How to Obtain a Link Budget .............................................................................. 2-61
2.9.21 How to Display City Points and Their Names on the Map .................................. 2-61
2.9.22 How to Display Scrambling Codes on the Map................................................... 2-61
2.9.23 How to Define the Default Server for Distributed Computing ............................. 2-62
Chapter 3 Managing Geographic Data ........................................................................................ 3-1

3.1 Overview ............................................................................................................................ 3-1
3.2 Geo Data Type Supported................................................................................................. 3-1
3.2.1 The DTM (Digital Terrain Model)............................................................................. 3-2
3.2.2 Clutter Classes (or Land Use)................................................................................. 3-2
3.2.3 Clutter Heights......................................................................................................... 3-2
3.2.4 Vector Layers .......................................................................................................... 3-3
iii
3.2.5 Scanned Images ..................................................................................................... 3-4

3.2.6 Population Maps...................................................................................................... 3-4
3.2.7 Generic Maps .......................................................................................................... 3-4
3.2.8 The Traffic Data....................................................................................................... 3-4
3.3 Length/height/offset units and coordinate systems ........................................................... 3-5
3.3.1 Setting Default length/Height/Offset Units .............................................................. 3-5
3.3.2 Basic Concepts ....................................................................................................... 3-6
3.3.3 Defining the Projection Coordinate System ............................................................ 3-7
3.3.4 Defining the Display Coordinate System ................................................................ 3-8
3.3.5 Selecting Degrees Display Format.......................................................................... 3-9
3.3.6 Creating Your Own Coordinate System................................................................ 3-10
3.4 Geo Data Format Supported ........................................................................................... 3-12
3.4.1 Overview ............................................................................................................... 3-12
3.4.2 BIL Data Format .................................................................................................... 3-13
3.4.3 TIFF Data Format.................................................................................................. 3-15
3.4.4 DXF Data Format .................................................................................................. 3-17
3.4.5 SHP Data Format.................................................................................................. 3-17
3.4.6 MIF Data Format ................................................................................................... 3-18
3.4.7 Erdas Imagine Data Format .................................................................................. 3-18
3.4.8 Other Supported Formats ..................................................................................... 3-19
3.5 Managing Clutter Classes................................................................................................ 3-20
3.5.1 Importing a Clutter Class File................................................................................ 3-20
3.5.2 Optimizing the Loading of Clutter Class Files ....................................................... 3-20
3.5.3 Description of MNU Files ...................................................................................... 3-21
3.5.4 Managing the Clutter Classes ............................................................................... 3-21
3.5.5 Adding a Clutter Class .......................................................................................... 3-24
3.5.6 Displaying Statistics on Clutter Classes................................................................ 3-24
3.6 Managing Clutter Heights ................................................................................................ 3-25
3.6.1 Importing a Clutter Height File .............................................................................. 3-25
3.6.2 Managing Clutter Height Maps.............................................................................. 3-25
3.7 Managing DTM Maps ...................................................................................................... 3-26
3.7.1 Importing a DTM Map ........................................................................................... 3-26
3.7.2 Managing DTM Maps............................................................................................ 3-27
3.8 Managing Vector Maps.................................................................................................... 3-28
3.8.1 Importing a Vector File .......................................................................................... 3-28
3.8.2 Managing Vector Objects...................................................................................... 3-29
3.8.3 Displaying Vector Layers over Predictions ........................................................... 3-30
3.9 Managing Scanned Images ............................................................................................. 3-30
3.9.1 Importing Scanned Images ................................................................................... 3-30
3.9.2 Managing Scanned Images .................................................................................. 3-31
3.10 Managing Population Maps ........................................................................................... 3-32
3.10.1 Importing a Population Map ................................................................................ 3-32
iv
3.10.2 Managing Population Maps................................................................................. 3-33

3.10.3 Displaying Statistics on Population ..................................................................... 3-34
3.10.4 Using Population Data in Prediction Reports...................................................... 3-35
3.11 Managing Generic Maps................................................................................................ 3-35
3.11.1 Overview ............................................................................................................. 3-35
3.11.2 Create an Advanced Geo Data Folder................................................................ 3-36
3.11.3 Managing Generic Maps ..................................................................................... 3-37
3.11.4 Displaying Statistics on Generic Data................................................................. 3-38
3.11.5 Using Generic Map Data in Prediction Reports .................................................. 3-38
3.12 Managing Geo Data Files and Folders.......................................................................... 3-39
3.12.1 Embedding - Linking Comparison ....................................................................... 3-39
3.12.2 Embedding Geographic Data.............................................................................. 3-40
3.12.3 Repairing a Broken Link...................................................................................... 3-40
3.12.4 Grouping Geo Data Files in Display Folder ........................................................ 3-42
3.12.5 Checking the Map Geocoding............................................................................. 3-43
3.12.6 Setting Geo Data Priority .................................................................................... 3-43
3.13 Editing Geographic Data................................................................................................ 3-45
3.13.1 Raster Objects..................................................................................................... 3-45
3.13.2 Vector Objects..................................................................................................... 3-48
3.14 Managing Geographic Data Export ............................................................................... 3-54
3.14.1 Exporting a Clutter Class Map ............................................................................ 3-54
3.14.2 Saving the Edited Raster Polygons..................................................................... 3-55
3.14.3 Exporting a Clutter Height Map ........................................................................... 3-57
3.14.4 Exporting a DTM Map ......................................................................................... 3-58
3.14.5 Exporting a Vector Object ................................................................................... 3-59
Chapter 4 Managing Radio Network Data................................................................................... 4-1

4.1 Managing Radio Network Data Overview.......................................................................... 4-1
4.2 Setting Default Radio Units................................................................................................ 4-1
4.3 Sites ................................................................................................................................... 4-2
4.3.1 Site Properties......................................................................................................... 4-2
4.3.2 Site Lists................................................................................................................ 4-10
4.4 Antennas.......................................................................................................................... 4-13
4.4.1 Creating an Antenna ............................................................................................. 4-13
4.4.2 Managing the Antenna Properties......................................................................... 4-14
4.4.3 Modifying Antenna Parameters in Tables ............................................................. 4-16
4.4.4 Copying Antenna Patterns to the Clipboard.......................................................... 4-17
4.4.5 Importing Antenna Patterns .................................................................................. 4-17
4.4.6 Printing Antenna Patterns ..................................................................................... 4-18
4.5 Transmitters ..................................................................................................................... 4-19
4.5.1 Transmitters Overview .......................................................................................... 4-19
4.5.2 Transmitters Properties......................................................................................... 4-19
4.5.3 Station Templates ................................................................................................. 4-27
v
4.6 Repeaters ........................................................................................................................ 4-32

4.6.1 Repeaters Overview.............................................................................................. 4-32
4.6.2 Creating a Repeater.............................................................................................. 4-32
4.6.3 Managing Repeater Properties ............................................................................. 4-33
4.6.4 Setting Donor Properties of a Repeater................................................................ 4-34
4.6.5 Setting Coverage Properties of a Repeater .......................................................... 4-34
4.6.6 Updating Repeater Parameters ............................................................................ 4-36
4.6.7 Using Repeaters in Calculations ........................................................................... 4-36
4.7 Radio Equipment ............................................................................................................. 4-37
4.7.1 Radio Equipment Overview................................................................................... 4-37
4.7.2 Managing TMA Equipment.................................................................................... 4-38
4.7.3 Managing Feeder Equipment................................................................................ 4-39
4.7.4 Managing BTS Equipment .................................................................................... 4-39
4.7.5 Assigning Radio Equipment to Transmitter........................................................... 4-40
4.7.6 Using Equipment to Compute Transmitter Losses ............................................... 4-41
4.7.7 Managing Radio Equipment in a Database Structure........................................... 4-42
Chapter 5 Managing Computations in U-Net.............................................................................. 5-1

5.1 Computations in U-Net Overview ...................................................................................... 5-1
5.2 Computing in Polygonal Areas .......................................................................................... 5-2
5.2.1 Computation and Focus Zones Overview............................................................... 5-2
5.2.2 Computation and Focus Zones Effects................................................................... 5-3
5.2.3 Drawing a Computation/Focus Zone....................................................................... 5-5
5.2.4 Creating a Computation/Focus Zone from Polygons .............................................. 5-6
5.2.5 Importing the Computation/Focus Zone from a File................................................ 5-6
5.2.6 Exporting the Computation/Focus Zone to a File.................................................... 5-7
5.2.7 Deleting the Computation/Focus Zone ................................................................... 5-7
5.2.8 Resizing the Computation/Focus Zone................................................................... 5-8
5.2.9 Moving a Point of the Computation/Focus Zone..................................................... 5-8
5.2.10 Adding a Point in the Computation/Focus Zone ................................................... 5-8
5.2.11 Removing a Point in the Computation/Focus Zone .............................................. 5-8
5.2.12 Displaying the Computation/Focus Zone Size ...................................................... 5-9
5.2.13 Displaying the Computation/Focus Zone Coordinates ......................................... 5-9
5.3 Propagation Models......................................................................................................... 5-10
5.3.1 Propagation Models Overview .............................................................................. 5-10
5.3.2 Propagation Model General Information ............................................................... 5-11
5.3.3 Working with Longley-Rice Model......................................................................... 5-16
5.3.4 Working with ITU 526-5 Model.............................................................................. 5-17
5.3.5 Working with ITU 370-7 Model (Vienna 93) .......................................................... 5-18
5.3.6 Working with WLL (Wireless Local Loop) Model .................................................. 5-18
5.3.7 Working with Okumura-Hata Model ...................................................................... 5-20
5.3.8 Working with Cost-Hata Model.............................................................................. 5-22
5.3.9 Working with Standard Propagation Model........................................................... 5-25
vi
5.3.10 Working with Standard Propagation Model Recommendations ......................... 5-27

5.3.11 SPM Clutter Tab Window.................................................................................... 5-42
5.3.12 SPM Calibration Tab Window ............................................................................. 5-44
5.4 Tuning Reception Parameters ......................................................................................... 5-50
5.4.1 Setting the Receiver Properties ............................................................................ 5-50
5.4.2 Computing Shadowing Margins ............................................................................ 5-51
5.4.3 Using Cell Edge Coverage Probability in Predictions ........................................... 5-53
5.5 Coverage Studies ............................................................................................................ 5-54
5.5.1 Coverage Studies Overview.................................................................................. 5-54
5.5.2 Coverage Prediction General Settings.................................................................. 5-55
5.5.3 Prediction Study Templates .................................................................................. 5-70
5.5.4 Path Loss Management ........................................................................................ 5-73
5.5.5 Prediction Coverage Outputs ................................................................................ 5-79
5.6 Point Analysis Predictions ............................................................................................... 5-84
5.6.1 Point Analysis Predictions Overview..................................................................... 5-84
5.6.2 Displaying Point Analysis Results ......................................................................... 5-85
5.6.3 Managing Point Analysis....................................................................................... 5-88
5.7 Calculation Tools in U-Net ............................................................................................... 5-93
5.7.1 U-Net Features for Computing .............................................................................. 5-93
5.7.2 Distributing Calculations on Several PCs ............................................................. 5-93
5.7.3 Improving Calculation Performances .................................................................... 5-95
5.7.4 Displaying Calculation Events in a Log Window ................................................... 5-95
5.7.5 Exporting Calculation Events in a Log File ........................................................... 5-96
Chapter 6 GSM/GPRS/EDGE/TDMA Project Management ........................................................ 6-1

6.1 Overview ............................................................................................................................ 6-1
6.2 GSM/GPRS/EDGE Projects Protocol ................................................................................ 6-2
6.3 Defining GSM/GPRS/EDGE Resources............................................................................ 6-4
6.3.1 Overview ................................................................................................................. 6-4
6.3.2 Frequencies............................................................................................................. 6-5
6.3.3 HSNs ....................................................................................................................... 6-8
6.3.4 BSICs ...................................................................................................................... 6-9
6.4 Managing GSM/GPRS/EDGE Radio Data ...................................................................... 6-12
6.4.1 Overview ............................................................................................................... 6-12
6.4.2 HCS Layers ........................................................................................................... 6-13
6.4.3 Timeslot Configurations ........................................................................................ 6-14
6.4.4 Cell Types ............................................................................................................. 6-15
6.4.5 Subcells................................................................................................................. 6-27
6.4.6 GPRS/EDGE Equipment....................................................................................... 6-33
6.5 GSM/GPRS/EDGE Traffic Management ......................................................................... 6-38
6.5.1 Overview ............................................................................................................... 6-38
6.5.2 GSM/GPRS/EDGE Multi-service Traffic Data....................................................... 6-39
6.5.3 GSM/GPRS/EDGE Multi-service Traffic Cartography .......................................... 6-51
vii
6.5.4 GSM/GPRS/EDGE Traffic Analysis ...................................................................... 6-71

6.6 GSM/GPRS/EDGE Network Dimensioning ..................................................................... 6-73
6.6.1 Setting GSM/GPRS/EDGE Dimensioning Models................................................ 6-73
6.6.2 Dimensioning GSM/GPRS/EDGE Transmitters.................................................... 6-75
6.6.3 Committing Dimensioning Outputs in GSM/GPRS/EDGE .................................... 6-76
6.7 GSM/GPRS/EDGE Resources Allocation ....................................................................... 6-78
6.7.1 Overview ............................................................................................................... 6-78
6.7.2 GSM/GPRS/EDGE Neighbours ............................................................................ 6-79
6.7.3 Allocating GSM/GPRS/EGPRS Resources Manually in U-Net ............................ 6-91
6.7.4 Using an AFP to Allocate Resources in U-Net...................................................... 6-96
6.7.5 Frequency Plan Analysis..................................................................................... 6-109
6.8 Specific GSM/GPRS/EDGE Prediction Studies ............................................................ 6-115
6.8.1 Setting Specific Coverage Conditions in GSM/GPRS/EDGE Studies ................ 6-115
6.8.2 Studying Interfered Zone Predictions.................................................................. 6-118
6.8.3 Computing a Coverage Study by C/I Level......................................................... 6-120
6.8.4 Studying Interferences with the Point Analysis ................................................... 6-121
6.8.5 Creating a Coverage by GPRS/EDGE Coding Schemes ................................... 6-125
6.8.6 Computing a Coverage by GPRS/EDGE Rate per Timeslot .............................. 6-125
Chapter 7 GSM/TDMA AFP Module ............................................................................................. 7-1

7.1 Overview ............................................................................................................................ 7-1
7.2 Managing the U-Net AFP Module...................................................................................... 7-1
7.2.1 Overview ................................................................................................................. 7-1
7.2.2 Accessing the U-Net AFP Properties ...................................................................... 7-2
7.2.3 Defining the AFP Parameters ................................................................................. 7-3
7.2.4 Defining the AFP Allocation Strategies ................................................................... 7-8
7.3 U-Net AFP module GUI ................................................................................................... 7-13
7.3.1 U-Net AFP Cost Tab ............................................................................................. 7-13
7.3.2 U-Net AFP HSN Tab ............................................................................................. 7-14
7.3.3 U-Net AFP MAL Tab ............................................................................................. 7-15
7.3.4 U-Net AFP MAIO Tab ........................................................................................... 7-16
7.3.5 U-Net AFP BSIC Tab ............................................................................................ 7-17
7.3.6 U-Net AFP Advanced Tab..................................................................................... 7-18
viii
GENEX U-Net Wireless Network Planning Software Chapter 1 Getting Started
Chapter 1 Getting Started
1.1 Summary
U-Net is a comprehensive Window-based multi-technology and user-friendly
radio-planning environment that supports wireless telecom operators during the whole
network lifetime, from initial design to densification and optimization.
More than an engineering tool, U-Net is an open, scalable and flexible technical
information system that integrates easily with other IT systems, increases productivity
and shortens lead times.
U-Net supports a full range of implementation scenarios, from stand-alone to
enterprise-wide server-based configurations using distributed and parallel computing.
The highlights of U-Net are definitely as follows Table 1-1:
Table 1-1 The highlights of U-Net
Highlights Description
Advanced network design features High-performance propagation

calculation engine, multi-layered and
hierarchical networks supported, traffic
modeling, automatic frequency/code
planning and network optimization. Full
support of GSM/GPRS/EDGE, CDMA
IS-95, WCDMA / UMTS, CDMA2000
technologies. Planning of integrated
multi-technology network (GSM/UMTS,
GSM/GPRS, CDMA/CDMA2000...).
Open and flexible architecture Support of multi-user environments

through an innovative database
architecture that provides data sharing,
data integrity management and easy
integration with other IT systems.
rd
Integration of 3 party or proprietary
modules (propagation models and AFP)
through a set of programming interfaces
(API). The integration of add-ins and
macros is also available.
1-1
Highlights Description
Distributed and parallel computing U-Net allows for the distribution of

calculations over multiple workstations
and supports parallel computing on
multi-processor servers, thus
dramatically reducing prediction and
simulation times and getting the most out
of your hardware.
State-of-the-art GIS features U-Net supports both multi-format and

multi-resolution geographic data and
integration with GIS tools. Large, dense
urban and countrywide databases are
supported and displayed interactively
with multiple layers including engineering
and prediction studies. It features an
integrated raster and vector editor.
U-Net is made of a main module to which you can add optional modules such as:
z The UMTS module (allowing CDMA/CDMA2000 projects) dedicated to
WCDMA/UMTS network analysis and planning.
z The Measurements module which allows the importation and management of
concrete CW measurement or test mobile data paths.
z The Automatic Frequency Planning module for the optimization of
GSM/GPRS/EDGE frequency plans.
z The Microwave planning module. This module allows the user to plan and
analysis microwave links.
1.2 Features in U-Net 1.0

These features are divided into several parts: some general features which are
available on the U-Net platform for any project, those dedicated to GSM/GPRS/EDGE,
WCDMA/UMTS, and CDMA/CDMA2000 (IS95, 1xRTT) studies. Improvements have
also been performed on microwave links and measurements.
1.2.1 General Features
General features are shown in Table 1-2.
1-2
Table 1-2 General Features
Feature Description
Developer toolkit It is possible to run path loss calculation

through an add-in/macro.
API has been updated in order to give
access to the low resolution path loss
matrices.
Sector rotation You may modify the azimuth of the first

antenna of all the transmitters situated
on a site using your mouse.
U-Net displays the integer value of
azimuth in the Status bar.
Status bar It is possible not to display altitude,

clutter class and clutter height
information in the Status bar. This can
be configured through the U-Net.ini file.
Geographic information system U-Net is capable of displaying

longitudes and latitudes in decimal
degrees. Four different formats are
available.
Zoom features have been improved. It
is possible to restore the previous zoom
level and the working of zoom-in and
out tool has been simplified.
You may insert a logo in your prints.
MapInfo format files containing points
with text are now supported.
Generic display features are available
for the clutter classes maps.
The management of clutter heights has
been improved in case your .atl
document contains both clutter classes
map(s) with an average height per
clutter class and clutter height map(s).
1-3
Feature Description
Transmitter and cell renaming It is possible to block the automatic

renaming of transmitters and cells
according to site name. This can be
configured through the U-Net.ini file.
Station templates You can add custom fields in station

templates.
Remote electrical tilt antenna It is possible to model remote electrical

tilt antenna. To do this, the user must
add an additional field in the database.
Filtering polygons U-Net displays the last drawn filtering

polygon on the map characterised by a
thick blue border.
Management features available for the
computation and focus zones (Add a
point, Remove the polygon ...) are
available in the filtering polygon context
menu as well.
Computation/Focus zones The computation (resp. focus) zone

area is provided in the computation
(resp. focus) zone properties window.
Import/export U-Net is capable of importing tabulated

data from (exporting to) ASCII text files
to (from) tables.
Prediction studies U-Net is capable of comparing the

coverage plots resulting from two
different prediction studies and
generating a comparative plot from the
two. This type of comparative coverage
plot is called a “Delta plot”.
It is also possible to create a duplicate
of any prediction study and to run a
single prediction study through the
context menu.
1-4
Feature Description
Reports on prediction studies U-Net provides a new output in reports

generated from prediction plots. It
calculates the percentage of covered
area inside the focus zone if available
and else, the percentage of covered
area inside the computation zone.
Export of prediction plots It is possible to specify a resolution

when exporting prediction plots in
ArcView format. This resolution can be
different from the path loss matrices
resolution and the one used for
calculating the prediction plot.
Database Each modification performed on

records (creation/deletion) and fields is
listed and may be independently
managed. For example, let us assume
we have a transmitter whose antenna
and height have been modified. It is
now possible to not globally archive all
the changes in the database. Meaning
that you may archive the modification of
antenna only and not the new height.
Point-to-point analysis Real point-to-point analysis is possible.

U-Net can display the terrain and clutter
profile between two points even if none
of them is a transmitter.
Calculation performance It is possible to specify a cut-off value

on the received signal level; this one is
used by U-Net limit contribution of
some interferers. Thanks to this
feature, some calculation performances
may be improved.
1-5
Feature Description
GUI Many improvements have been made

on the dialogs, menus and commands
in order to make them even more
logical and easy to use
Context menus have been
standardized in order to give more
weight to the main commands
Generic geographic layers In addition to the standard raster layers

(DEM, clutter classes, images...) U-Net
allows users to import and display
additional raster layers (e.g. population
files, income density maps...), which
are then taken into account in reports.
Geographic display folder It is now possible to group any type of

geo data within a unique group in order
to make them used for display only.
Clutter heights files A new "Clutter heights" folder has been

created. The clutter height can be now
defined at the pixel level and taken into
account in calculations (Propagation
models, measurements).
Tiff Geo files For Tiff files, an option has been added
to modify the color palette convention
used by U-Net.
Import of PlaNET text data files It is now possible to import PlaNET text
data in .atl documents.
User configurations A new option is available during the

import of a cfg file with a view to delete
all existing maps.
It is now possible to include macro file
paths in user configurations
Unit systems New units are available for lengths,

heights and offsets.
1-6
Feature Description
Site lists In addition to the dynamic filtering

features, U-Net allows users to define
static lists of sites names, either
graphically or by using analytic criteria.
Site lists are stored in the database and
can be imported and exported as ASCII
files.
Repeaters Repeaters are modeled and considered

in the prediction studies and
interference analysis.
Site and transmitter naming When changing the name of a site,

U-Net automatically renames
transmitters and cells related to the site
which names contain the site name.
The sector numbering has changed. It
starts from 1 instead of 0 and can be
set by the user.
Object search tool A new dialog is available in order to

locate on the map any vector from its
attribute, any point or any site.
Enhancement of the neighbour allocation An additional option enables the user to

algorithm force adjacent cells as neighbours
(GSM / GPRS / EDGE, WCDMA /
UMTS, CDMA / CDMA2000)
Multi-resolution in predictions It is now possible to define a main and

an extended resolution (for low
resolution) linked with main and
extended matrices, main and extended
calculation radii.
Definition of the resolution at the The resolution of the prediction studies

prediction level are independent from the pathloss
calculation resolution
1-7
Feature Description
Prediction studies It is now possible to select the 2nd best

server for the service zone definition in
prediction studies
A new display type is available in
coverage predictions. You can now
color the service zones depending on
the best cell edge coverage probability
and on the cell edge coverage
probability.
It is now possible to calculate path loss
matrices independently from any
coverage study
Point analysis U-Net now provides the angle between

the profile and the north in the status
bar, at the bottom left of the window.
In the Profile window, a green line
shows the line of sight (LOS) from the
studied transmitter.
In the Profile window, U-Net also
displays the angle of the LOS read in
the antenna vertical pattern. U-Net now
provides the angle between the profile
and the north in the status bar, at the
bottom left of the window.
In the Profile window, a green line
shows the line of sight (LOS) from the
studied transmitter.
In the Profile window, U-Net also
displays the angle of the LOS read in
the antenna vertical pattern.
CW Measurement A new filter related to the angle

between the reference transmitter and
CW measurement points has been
introduced for the statistical
comparisons between CW
measurements and predictions.
1-8
Feature Description
Test mobile analysis (measurement In addition to the CW measurement

module) layer, a new layer allows to import,
display and analysis test mobile data.
Measurements points can now be
colored by best server or best signal
level
Additional generic and proprietary test
mobile/CW survey file formats are
supported, including TEMS
FICS-Planet export (.pln) and TEMS
Text export (.fmt). •Decoding and
display of the serving cell ID and
neighbour IDs from the BSIC/BCCH
fields (GSM), scrambling codes
(UMTS) or PN Offsets
(CDMA/CDMA2000).
It is possible to create a specific field
related to a fixed attribute all along a
single test mobile data path.
Co-Planning A new algorithm based on coverage

overlapping allows automatically
calculating and allocating neighbours
between GSM and CDMA (including
UMTS) networks. The simple algorithm,
based on distance, provided in the
previous versions is still available.
Batch mode Calculations can be launched in batch

mode.
1-9
Feature Description
New 'general interface' in the developer's A new programming interface provides

toolkit a generic access to network data and
pathloss matrices in U-Net projects,
and allows developers to add their own
functions into U-Net user interface.
It enables the integration of a wide
range of applications such as
optimization tools, interface with other
applications and configuration tools.
Customization is performed using
external VBA scripting tools or the
U-Net Visual C++ Software
Development Kit.
It is now possible to access antenna
patterns through the propagation model
API.
The toolkit enables to run macros from
an U-Net session.
Database management All reserved keywords have been

removed from database structure
1.2.2 Features for GSM/GPRS/EDGE Projects
I. Default values
New default values have been implemented in GSM GPRS EGPRS documents.
II. Shadowing modelling
It is now possible to define a default model standard deviation value. You may force
U-Net to use this value even if a clutter class map with model standard deviations per
clutter class is available. Otherwise, this value is used if no clutter class map is
available in your .atl document or if no model standard deviation value per clutter class
is specified.
Use of clutter weighting in the cumulated traffic and traffic analysis
A new command “Clutter weighting calculation” is available in the traffic folder context
menu in order for the clutter weighting to be correctly considered in the cumulated
traffic and the traffic analysis.
1-10
III. Interference tab
Multi-options are available in the Interference tab of the Point analysis window. It is
now possible to consider either all the interferers, or only co-channel interferers, or
only adjacent channel interferers, in order to calculate interference received.
IV. AFP tool
U-Net now considers the focus zone (instead of the computation zone) to determine
transmitters for which it will allocate resources.
The option “Best signal level of the highest priority HCS layer” is now available when
calculating interference histograms. In addition, you may specify a Cell Edge
Coverage Probability in the dialog that enables you to model shadowing.
Interference histograms (.clc files) with a simplified format can be imported.
It is possible to export AFP results thanks to the generic export feature.
An Erlang based cost function replaces the pair-wise sum-up of interferences with a
more precise modeling of the interfered traffic.
When the constraints are too important for the planning algorithm, it is possible to
access to information giving the list of cells for which the constraints are not fulfilled.
Predefined MAL are supported (SFH TRX)
Multiple reuse pattern constraints
Grouping constraints may be taken into account in non-hopping TRX
Minimal change optimization (cost of changing already assigned TRX higher than new
assignments)
Staggered MAIO allocation (MAIO equally spaced for one sector)
Local quality target (ability to improve plan only where minimal quality is not achieved)
V. User configuration
It is now possible to save in user configuration files all the settings specified when
starting an AFP session as well as calculation parameters used for interference
histograms.
VI. Neighbours
Internal (intra-technology) and external (inter-technology) neighbours are now listed in

dedicated tables. Standard features for managing table contents (Copy/Paste, Delete,
Display columns, Filter, Sort, Fields ...) are available in a context menu (when right
clicking on column(s)) or record(s) and in the Format, Edit and Records menus.
Parameters used to define the overlapping area between reference cell and candidate
cells are now grouped in a dialog, this one can be opened by clicking the Define
button.
1-11
Display of neighbours:
Additional information such as symmetry of a neighborhood link, outwards and
inwards handover relationships, is now available on the map.
Information to be displayed may be configured.
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 color display by transmitter) preliminary calculated.
It is possible to directly add/remove neighborhood links at once:
On the map thanks to CTRL and SHIFT shortcuts,
In the table listing neighbour relationships thanks to commands Delete link and
symmetric and Symmetries available in a context menu.
You may now define the maximum number of neighbours you want to allocate to a
transmitter at the transmitter level (Transmitters table). If specified, this parameter is
used in the automatic allocation. Otherwise, U-Net uses the default value still available
in the automatic neighbour allocation dialog.
New tables available for internal (intra-technology) and external (inter-technology)
neighbours allow you to define allocation constraints (list of neighborhood
relationships to be forced or forbidden). Then, these constraints may be taken into
account during the automatic neighbour allocation.
Finally, in tables listing neighbours, U-Net provides additional information such as the
distance between the neighbour and the transmitter/cell, if the neighborhood
relationship is symmetric or not, the type of allocation (manual, automatic, or allocation
coming from an import), the neighbour rank in the list (only in case of an automatic
allocation) and the allocation cause (only in case of an automatic allocation).
VII. Data model
All the TRX type parameters have been introduced in the subcells
It is now possible to exclude channels from the allocation at the subcell level
The separations are now imposed between subcells
VIII. BSIC notation
It is now possible to manage the BSIC (NCC-BCC) in octal or decimal (as before)
format.
IX. Improvements in traffic modelling
New ‘data’ traffic layer allowing the modelling of the GPRS traffic demand, in addition
to the existing voice traffic layer.
Combined GPRS/voice traffic dimensioning and analysis.
1-12
X. New GPRS features
Enhanced time slot dimensioning.

Calculation of Quality of Service indicators
XI. Consistency checking tool
The audit (former name: consistency checking) tool has been enhanced. Additional
tests are automatically provided.
1.2.3 Features for WCDMA/UMTS Projects
I. Default values
New default values are available in UMTS WCDMA documents.
II. Display of cell properties
It is now possible to assign a colour to transmitters depending on their cell attributes,

to display cell attributes in labels or tip balloons and to color the service area of
transmitters depending on any cell attribute. In addition, you may group transmitters by
any cell attribute.
III. Simulations
U-Net can export the results tables (Sites, Cells, Mobiles tabs) of any simulation. You
may also export results of an average simulation based on a group of simulations.
An additional output, the UL reuse efficiency, is available in simulation results. This is
the reciprocal of the uplink reuse factor.
IV. AS analysis tab
You may now base analysis on a group of simulations (U-Net uses average UL load
and DL total power), or no simulation (U-Net uses UL load and DL total power
user-defined for each cell).
V. Processing gain
Formulas used to calculate uplink and downlink processing gains have been modified.
The coding factor is no longer taken into account. Therefore, the processing gain is the
ratio between bandwidth and the nominal rate.
VI. Shadowing modelling
is specified.
1-13
Calculations of UL and DL macro-diversity gains based on shadowing margins have

been enhanced.
VII. OVSF codes
U-Net now allocates 256-bit-length OVSF codes to common channels. In addition, a

new formula is used to evaluate the length of OVSF codes allocated to traffic
channels.
VIII. Neighbours

In the automatic neighbour allocation GUI, parameters used to define the overlapping
area between reference cell and candidate cells are now grouped in a dialog, which
can be opened by clicking the Define button.
inwards handover relationships, is now available on the map. In addition, it is possible
to display neighborhood relationships on a given carrier you may select.
The maximum number of neighbours you want to allocate to a cell is no longer a global
value; you may now define this parameter at the cell level (Cells table). If specified,
this parameter is used in the automatic allocation. Otherwise, U-Net uses the default
value still available in the automatic neighbour allocation dialog.
1-14
IX. Global parameters
Two methods are available in order to calculate the total noise NT.
X. Scrambling code allocation
It is possible to define neighborhood constraints during the scrambling code allocation.

Neighborhood constraints can be imposed not only on the current defined neighbours.
The scrambling code allocation is compatible with the bi-thread computation process.
1.2.4 Features for CDMA/CDMA2000 Projects
I. Default values
Default values of CDMA2000 1xRTT 1xEV-DO documents have been modified.

Default values of IS-95 cdmaOne documents have been modified.
II. Display of cell properties
It is now possible to assign a colour to transmitters depending on their cell attributes,

to display cell attributes in labels or tip balloons and to color the service area of
transmitters depending on any cell attribute. In addition, you may group transmitters by
any cell attribute.
III. AS analysis tab
You may now base analysis on a group of simulations (U-Net uses average UL load
and DL total power), or no simulation (U-Net uses UL load and DL total power
user-defined for each cell).
IV. Processing gain
Formulas used to calculate FCH and SCH (uplink and downlink) processing gains
have been modified. The coding factor is no longer taken into account. Therefore, the
processing gain is the ratio between bandwidth and the (FCH or SCH) nominal rate.
V. Shadowing modelling
is specified.
Calculations of UL and DL macro-diversity gains based on shadowing margins have
been enhanced.
1-15
VI. Neighbours

The automatic neighbour allocation GUI has been modified. Parameters used to
define the overlapping area between reference cell and candidate cells are now
grouped in a dialog, which can be opened by clicking the Define button.
inwards handover relationships, is now available on the map. In addition, it is possible
to display neighborhood relationships on a given carrier you may select.
The maximum number of neighbours you want to allocate to a cell is no longer a global
value; you may now define this parameter at the cell level (Cells table). If specified,
this parameter is used in the automatic allocation. Otherwise, U-Net uses the default
value still available in the automatic neighbour allocation dialog.
VII. Coverage predictions
Two new display types are available for the service area (Eb/Nt) study: Required
Power and Required Power margin
1-16
VIII. Simulations
A comment has been added for simulations (as for prediction studies)
IX. PN Offset allocation
PN offsets are now supported by U-Net. An automatic PN Offset allocation tool is

available. The PN Offset allocation is compatible with the bi-thread computation
process.
1.3 Installing and Removing U-Net

1.3.1 System Requirements
U-Net application runs on PC work stations under Windows NT 4.0, 2000 or XP. The
recommended configuration for the workstation is as following:
z CPU Pentium III (800 MHz at least)
z Memory 256 Mb recommended
z Disk 2 GB free on disk recommended (or more according to the
used geographic database)
z Operating system Windows NT 4.0, 2000 or XP
z Graphics card 1280*1024 64000 colors
z Application environment Microsoft Office >95 advised (Excel, Word, Access)
1.3.2 What's Installed with U-Net
During U-Net installation, other components may also have been added from the
executable files com32upd and dcom95 (both designed for Windows 95 - not
recommended). Furthermore, U-Net must be installed with an appropriate version of
Microsoft Data Access Components (MDAC - in order to work with databases). The
recommended version is 2.7. This one can be downloaded from the support site.
If you choose to install the calculation server, it is installed as a service on your local
machine. To make it unavailable, you will need to stop it in the Services (Administrative
tools) dialog of your operating system.
1.3.3 Installing U-Net
To install U-Net, proceed as follows:

1) Quit all programs.
2) Insert the CD-ROM in the appropriate drive and follow the instructions on the
screen, or Double-click the Setup application.
By default, the U-Net installation directory path is C:\Program Files\Huawei
GENEX\U-Net 1.0\ (or the last directory in which you installed the U-Net application).
1-17
To define another directory path, edit directly the appropriate box during the installation,
which is shown in Figure 1-1.
Figure 1-1 Select Path
3) Select the type of installation you want to make, which is shown in Figure 1-2.
1-18
Figure 1-2 Select features
Features description:
z U-Net tools: Install U-Net RND tools
z Support components: Install U-Net Tee Chart ActiveX Control
z Tutorial documents: Install U-Net documents
4) Click the button to run the installation process.
Note:
z Help files are automatically installed during Setup,
z The User manual (in PDF format) is on the CD-ROM, and can be downloaded
from the support site,
z Install the dongle driver only if necessary (not available or old version). It the option
is checked, it will be necessary to reboot after installation.
1.3.4 Removing U-Net
To remove U-Net, proceed as follows:
1-19
1) Quit all programs.

2) Click the Windows Start button, point to Settings, and then click Control Panel.
3) Double click the Add/Remove Programs icon.
4) In the Install/Uninstall tab, select U-Net in the list, and then click Add/Remove.
5) Follow the instructions on the screen.
1.3.5 Installing Distributed Computing Server
U-Net provides a feature on distributed computations of propagation calculations and

CDMA/WCDMA simulations. The U-Net package provides a computing server
application (AtollSvr) which can be installed either on workstations or servers and
which can be used by U-Net sessions installed on other stations.
This computing server application (used only for path loss computations) supports
dual-processor configuration (2 processors are used on multi-processor stations).
To install the distributed computing server, check the U-Net calculation server option in
the Select components box during the setup process. The application will then be
installed as a service on the local machine, i.e. will run as far as the local pc is on,
even with no user connected.
Service management like the distributed computing server application can be
accessed from the Administrative tools icon in the Control Panel. Then choose the
Services application.
Note:
Like for U-Net installation, you must be connected with administrative rights when
installing the application.
In order to be able to access some potential centralized geo data for computation,
check that the account on which is "installed" the service has enough rights (which is
not always the case by default). If not, access the properties of the Service and assign
it to an appropriate account (e.g. in the Log on window for Windows 2000 OS).
1.3.6 Removing Distributed Computing Server
The distributed computing server application is installed as a service on stations, i.e.

runs as far as the local PC is on, even with no user connected.
The first step of uninstalling is to stop the corresponding service. To do that, proceed
as follows:
1) Check that you are connected on an account with rights allowing you to stop
Services, proceed as follows Table 1-3.
1-20
Table 1-3 Stop service
System Step Operation
1 Access the Control Panel
2 Click on the Services Icon,

Under Windows NT4
3 Select the U-Net server item,
4 Click the STOP button.
1 Access the Control Panel,
Under Windows 2000 or 2 Open the Administrative Tools,

XP 3 Click on the Services Icon,
4 Select the U-Net server item,
5 Right click on the item to open the

context menu and Click the STOP
Under Windows 2000 or command; or open “Service”
XP property dialog box and click the
STOP button in the Service status
part.
Once the service is stopped, to uninstall, proceed as follows:
1) Left click the button of your operating system.
2) Choose the command in the open menu.
3) Enter the syntax "< U-Net installation path>\ AtollSvr.exe" /UnregServer in the
open box.
4) The computing server application is then removed from the station.
1.3.7 Troubleshooting after Installation
After having installed U-Net, you may encounter some running problems that are easy
to fix.
Firstly, please be sure to have installed U-Net on an administrator account, to have
rebooted your computer and logged in again on an account with administrator rights in
order to complete installation with libraries that were in use during the first installation
step (including mdac - optionally - and the sentinel driver).
1-21
Please also check the validity of the folder in which you installed U-Net. Because
U-Net is installed by default in an U-Net folder, be sure that you didn't put yours in that
way, for example: C:\Program Files\Huawei GENEX\XXX\ U-Net 1.0\..., where XXX
was the name of the main folder in which you wanted to install U-Net.
If the MDAC version of your PC is too old, you might install a newer version of mdac
(downloadable from the support site) in order to allow communications with databases.
The recommended MDAC version is 2.7.
In case of the message "Protection key error", please check your connection and the
key validity. If you use a hardware Superpro dongle, try first to reboot your computer
after installation on an administrator account. Then, install again the sentinel driver (by
using the setupx86.exe file in the setup folder from your current U-Net main folder).
Caution:
It is advised to switch off your computer before unplugging or plugging hardware key
into it.
Do not change the PC date.
When the Superpro dongle is temporary:
- Do not reprogram it even if you plug it into another computer.
- Do not put the time bomb off without the Huawei support help.
Nethasp key (Multi-user licence) is supported under Windows 2000 Server only using
from License manager 8.09.
1.4 Getting Help

1.4.1 Ways to Get Assistance
To get help from the Help menu:

z Just select the Help Topic command in the Help menu. The Help window is then
open on the screen.
z Several approaches are available to search information, is described below Table
1-4.
1-22
Table 1-4 Search information
Method Description
Click on the Content tab Click on the Content tab to scroll through a
table of content. When you have found in the
list the topic you are interested in, simply
double click on it. A window containing the
information about the subject will then be
open on your screen. You will notice in the
text some words or sentences in green,
these are links to other topics relating to the
word or sentence.
Click on the Index tab Click on the Index tab to refer to the index
inputs. Choose in the list the input you are
interested in, double click on it. A window
containing the information about the subject
will be displayed.
Click on the Find tab Click on the Find tab to search for specific
words or sentences that might be in a help
topic. Type the word or the sentence you
search, choose in the list a subject and then
press Display to open the window containing
information.
Note:
For any external modules like propagation models, automatic planning tool or any
other one developed with the API, the online help can be reached by clicking the
button of each tab. A related topic will be open.
z To get an explanation about dialog box options: Just click the What's this
button located at the top right corner of teach dialog window and then, click on the
field you want to be informed of. A help window will be displayed.
z To see the name of a toolbar button, Rest the pointer on the button until the name
appears.
z To get a short explanation about a menu command or a toolbar button, Position
the pointer on the command or the button. A short explanation is displayed in the
status bar located at the bottom left of the U-Net window.
1-23
z To get information about the U-Net application (version number, copyrights)
Click the about tool on the toolbar, or select the About U-Net... command in the
Help menu.
1.4.2 Technical Support
You can consult the support section of the Huawei web site: www.huawei.com.
Also, you can contact us by EMAIL: GENEX@huawei.com.
1.5 Running Project Templates

1.5.1 Starting a New Project
Several project types based on different technologies are available in: GSM 900, GSM
dual band 900-1800, GPRS, and, by use of an optional module UMTS, CDMA-IS95
and CDMA2000 (1xRTT). Each project has its own data and folder structure. For
example, tabs in the transmitter properties dialog box and radio parameters change
according to the project. In the same way, availability of some specific objects depends
on the chosen project, such as, for example, UMTS cells (UMTS projects) or TRX
(GSM-TDMA projects). Moreover, U-Net modular and scalable architecture enables
the user to match the configuration to customer needs.
To choose a project type:
1) Select in the File menu the New command, or click on the new tool in the
toolbar.
2) In the project type dialog box, choose a project and then, click on OK to validate.
Note:
U-Net allows you to define a personal template from any existing project.
1.5.2 Templates Provided
U-Net supports, in its standard version, project types is described below Table 1-5.
1-24
Table 1-5 Supported project type
Project type Description
GSM900(850) (Global System for Mobile 2nd generation of numeric telephony

communications) norm working around the 900 (850)
MHz band, using the TDMA (Time
Division Multiple Access) technology.
This technology is supported using the
GSM GPRS EGPRS project template.
DCS1800/1900 (Digital Communications 2nd generation of numeric telephony

System) norm working around the 1800/1900
MHz band, using the TDMA (Time
GSM dual-band 900-1800 (GSM900 2nd generation of numeric telephony

and DCS1800) norm working both around the 900 MHz
and 1800 MHz bands, using the TDMA
technology. This technology is
supported using the GSM GPRS
EGPRS project template.
GPRS (Global Packet Radio Service) 2.5th generation of numeric telephony

and EDGE (Enhanced Data-rates for norms working around the 900-1800
GSM - or Global - Evolution) MHz bands, using the TDMA (Time
The optional UMTS module (which is shown in Table 1-6) permits to build projects for:
Table 1-6 UMTS projects
UMTS (Universal Mobile 3rd generation of numeric telephony

Telecommunication System) norm working around the 2 GHz band,
using the WCDMA (Wideband Code
UMTS WCDMA project template.
1-25
1xRTT (1st eXpansion Radio Telephone 2.5th generation of numeric telephony

Technology) norm working around the 900 MHz
band, using the CDMA (Code Division
Multiple Access) technology. This
technology is supported using the
CDMA2000 1xRTT 1xEV-DO project
template.
IS95-CDMA (Interim Standard 95) 2nd generation of numeric telephony

norm working around the 800 MHz
band, using the CDMA (Code Division
Multiple Access) technology, also
known as CDMAOne 95 refers to an
accepted industry protocol. This
technology is supported using the IS-95
cdmaOne project template.
Note:
Moreover, microwave link technology is available in any project type.
1.5.3 Creating Your Own Template
By using the database structure provided by U-Net by default, it is possible to create

your personal template with a view to start each new project with your own tables,
parameters, user-defined flags...
There are 2 ways to do so, proceed as follows:
I. Method 1
1) In an open U-Net project, select Database: Export... command in the File menu,
2) Export the project as a template in the U-Net templates directory (by default
C:\Program Files\Huawei GENEX\ U-Net 1.0\Templates), which is shown in
Figure 1-3.
1-26
Figure 1-3 Export database
When this is done, your personal template is available in the Project type dialog box,
which is shown in Figure 1-4.
Figure 1-4 Project type
II. Method 2
1) Open a U-Net project template (located in C:\Program Files\Huawei GENEX \

U-Net1.0\Templates by default) in MS Access as a model.
2) You can modify the databases as you want in order to obtain your customized
template. For example, you can import your own table of antennas.
3) Use the Save as... command in the File menu, to save this template in the U-Net
template subfolder.
4) When this is done, your personal template is available in the Project type dialog
box.
1-27
1.5.4 Building a Project Step by Step
I. U-Net basic project
To build a U-Net basic project, follow the basic steps described below:
1) Choose a project template.
2) Define the projection and display coordinate systems, the length, reception, and
transmission units.
3) Import geographic data files (clutter classes and heights, DTM, vector data,
population data, generic data...).
4) Create the network by using station templates or by retrieving the data of an
existing one. Adjust the parameters of sites, transmitters, repeaters, and specific
GSM/GPRS or UMTS/CDMA/CDMA2000 radio data.
5) Calibrate propagation models by the use of CW measurements.
6) Define the computation zone and the calculation settings (resolutions, calculation
radius, propagation models, and reception properties).
7) Create and calculate standard coverage studies (per transmitter, by signal level,
overlapping zones).
II. GSM/GPRS projects
1) Define multi-service traffic parameters (services, mobility types, terminals, user

profiles, environments).
2) Define the traffic through the import or the creation of maps (Traffic maps per
environment, Traffic maps per user profile, Live traffic maps, User density traffic
maps, Capture the traffic to analyse the demand, Set the dimensioning models).
3) Dimension the network (required number of shared, circuit and packet timeslots,
traffic loads).
4) Define the neighbours manually or automatically.
5) Allocate frequencies, BSIC and frequency hopping parameters, to match the
demand (user-defined of coming from dimensioning part).
6) Check the allocations through interference studies, the audit tool, KPI calculation
7) Compute specific GPRS/EDGE studies.
8) Check and validate of the network by the import of test mobile data.
III. UMTS projects
1) Define multi-service traffic parameters (services, mobility types, terminals, user

profiles, environments).
2) Define the traffic through the import or the creation of maps
tTraffic maps per environment
tTraffic maps per user profile
tLive traffic maps
1-28
3) Define neighbours manually or automatically.

4) Make instant pictures of the network by the use of monte-carlo simulations. This
also provides dimensioning results.
5) Calculate specific UMTS studies based on network load (user-defined of coming
from simulations).
6) Allocate primary scrambling codes to cells and check the allocation with the audit
tool.
7) Check and validate the network by the import of test mobile data.
IV. CDMA/CDMA2000 projects
1) Define multi-service traffic parameters (services, mobility types, radio

configurations, environments).
2) Define the traffic through the import or the creation of maps
tTraffic maps per environment
tTraffic maps per user profile
tLive traffic maps
3) Define neighbours manually or automatically.
4) Make instant pictures of the network by the use of monte-carlo simulations. This
provides also dimensioning results.
5) Calculate specific CDMA/CDMA2000 studies based on network load
(user-defined of coming from simulations).
6) Allocate PN Offsets to cells and check the allocation with the audit tool.
7) Check and validate the network by the import of test mobile data.
1-29
GENEX U-Net Wireless Network Planning Software Chapter 2 The Working Environment
Chapter 2 The Working Environment
2.1 Overview
The U-Net user interface consists of an integrated set of cursors, windows, tools,
menus, toolbars and other elements that allow you to create, and define your project in
one place.
The user interface uses standard Windows interface functionalities along with a few
additional features to make your environment easy to use. Moreover, the drag and
drop feature can be commonly used between any folder explorer and U-Net in order to
import or open any objects with a compatible format.
The two common window types are document windows and docking windows. The
position and size of document windows can be changed within the U-Net window.
They can be maximized and minimized. Docking windows, however, can be attached
to the borders of the application window, or float anywhere on your screen.
You can have more than one document file open in U-Net. Document windows are
attached to a single document. You can have many document windows attached to a
single document. Examples of document windows are maps, datasheets or studies
reports. When you close the last document window attached to a document, this
document is closed.
Docking windows are shared among open documents. They reflect the content of the
active document. The active document is the one attached to the active window.
Examples of docking windows are the Explorer window, the Panoramic window, the
Legend window, or the Event viewer window.
U-Net provides many features dealing with the use of the map. Hence, you can easily
move, zoom in and out, changing scales, and choosing visibility range for objects
displayable on the map. Several ways of exporting the current environment are also
possible.
In U-Net, most of the items are organized in folders in the Explorer window. Those
folders can be displayed in tables in order to make easy the management of large data
in the same time. Hence, filters, groups and sorts are easily made either in folders,
tables and on the map (filtering only), and can be saved in configurations.
This generic organization method is also applied to the display of objects in U-Net. A
generic display dialog is available when working on the properties of radio data (sites,
transmitters, and microwave links), prediction studies, measurements, simulations and
some geo data objects (DTM map or vector objects).
2-1
U-Net provides several handy tools, like an Undo/Redo function, Windows classical
and specific shortcuts, the use of icons and several types of cursors related to working
processes. Furthermore, U-Net provides different search tools in order to easily locate
either a site, a point, or a vector (even from its attributes only). It is also possible to
synchronize a selected vector and the related displayed data (or any CW
measurement or Test mobile data) in the corresponding data table.
2.2 Working with Menus and Windows

2.2.1 Working with Document Window
I. To tile the document windows
Select in the Window menu the Tile command.
II. To cascade the document windows
Select in the Window menu the Cascade command.
2.2.2 Working with Docking or Floating Window
I. To show or hide a docking window
z To show a docking window, click the name of the window on the View menu.
z To hide the window, click the Hide button in the corner of the window. This
button may be at the top-left or top-right corner, depending on the position of the
window.
II. To expand or contract a docking window in its docking area
Click the Expand or Contract button near the corner of the window. This
button may be near the top-left or top-right corner, depending on the position of the
window. This is a dual-purpose button. When the window is fully expanded, the
function of this button is Contract; otherwise, the function is Expand.
III. To change a docked window to a floating window
Double click in the window border.
IV. To dock a floating window
Double click the window title bar to return the window to its previous docked location,
or point to the title bar and drag the window to a different dock area.
V. To position a floating window over a dock (without docking it)
1) Point to the title bar of the window.

2) Hold down the CTRL key and drag the window over any dock area of the
application window.
2-2
Note:
The window positions for docking windows are not associated with the current project;
they remain the same no matter which project you open.
2.2.3 Printing the Active Window
U-Net provides powerful features in order to import/export any data. On this

consideration, U-Net provides also the possibility to print any type of active window
(table, legend, map, antenna pattern, point analysis window...).
In order to print the active window, once the print is set, select the Print command in
the File menu (or use the Ctrl+P shortcut) in the case of maps or tables.
For other objects like antenna patterns, legend or point analysis windows (for
example), just select the Print... command from the related context menu (right click in
the window).
2.3 Working with Maps

2.3.1 Zooming and Panning
U-Net provides powerful tools in order to zoom and to move the currently displayed
map
I. To zoom in
1) Click the zoom tool on the zoom toolbar, or Press Ctrl+Q Then left-click
on the map;
2) Press Ctrl+A or Select the Zoom in command from the View menu.
The map is displayed with the previous scale in the scale list box.
II. To zoom out
1) Click the zoom tool on the zoom toolbar or Press Ctrl+Q Then right-click
on the map;
2) Press Ctrl+R or Select the Zoom out command from the View menu.
The map is displayed with the next scale in the scale list box.
Note:
Zoom in and out actions are made depending on the cursor map location. The cursor
stays in the workspace.
2-3
III. To zoom on a specific area of the map
1) Click the zoom area tool on the zoom toolbar or On the View menu select
the Zoom Area command.

2) On the map press and hold the left mouse button at the north-west corner of the
area.
3) Drag the pointer to the south-east corner.
4) Release the mouse button.
IV. To switch between the last five (4 previous + 1 current) zoom levels in
history
use the Previous zoom and Next zoom buttons on the zoom toolbar.
V. To move the map area
1) Click the Hand tool on the zoom toolbar.
2) Hold down the left mouse button on the map area and drag the pointer.
Note:
In case of refresh problems on the map, use the icon from the zoom toolbar (or
the F5 shortcut).
2.3.2 Using the Panoramic Window
The Panoramic window offers a whole view of the imported geographic data and
allows locating the map area you want to display in the workspace. A darker rectangle
characterizes the map area selected in the Panoramic window and displayed in the
workspace.
Several operations may be performed from the Panoramic window; they are detailed
below.
I. To zoom on a specific area of the map
1) Position the pointer on the map. The pointer becomes a dotted rectangle.
2) Press and hold the left mouse button at the north-west corner of the area.
3) Drag the pointer to the south-east corner.
2-4
II. To move the map area
1) Position the pointer on the zoom area (darker rectangle). The pointer becomes
a cross.
2) Press the left mouse button.
3) Slide the pointer.
III. To resize the map area
1) Position the pointer at the corner (or any border) of the zoom area (darker
rectangle). The pointer becomes a double arrow.
2) Press the left mouse button.
3) Slide the pointer.
2.3.3 Centering the Map
The centre map function enables you to display the selected objects like transmitters,
sites, hexagonal design... at the centre of the workspace and the central area of
imported geographical data like clutter, DTM, vector data or scanned images. In both
cases, the displayed area is moved conserving the current scale.
I. To centre an object in the displayed workspace
1) Right click the object.

2) Select the Locate on Map command in the context menu.
II. To put a map in the centre of the displayed workspace
1) Right click the geo data layer.

2) Select the Centre Map command in the context menu.
2.3.4 Choosing a Scale
To choose a scale, proceed as follows:

1) Click the arrow next to the scale box on the zoom toolbar.
2) In the list click the scale value you want.
If the scale value you want is not in the list:
1) Click in the scale box.
2) Type the scale value you want.
3) Press Enter. The value you entered is added to the scale list.
2-5
Note:
z If you drag the icon band containing the scale scrolling box from the toolbar to a
side of your environment, you may find it again by clicking on the zoom area
button.
z Use the What's this help to get further description about the fields available.
2.3.5 Defining Visibility Ranges on Objects

For any object with settable display (sites, transmitters, coverage studies, CW
measurement, maps...), it is possible to specify a visibility range. The object will be
visible only if the zoom level defined in the workspace (in the scale box) is within the
object visibility range.
This feature enables you to display in the workspace an object depending on the zoom
level.
To define an object visibility range, proceed as follows:
1) Right click the folder related to the considered object to open the associated
context menu.
2) Choose the Properties command from the open scrolling menu.
3) In the Display tab, enter minimum and maximum zoom levels.
Note:
z In case of sites and transmitters, the visibility range is globally specified in the
folder Properties window.
z This feature is an add-on, like visibility boxes or layer order, to manage object
visibility in the workspace; the defined visibility ranges have no influence on the
objects taken into account in calculations.
z Visibility scales defined for objects are taken into account during printings or print
previews. Objects will appear only if the printing scale is within their respective
visibility range.
2.3.6 Displaying Rulers around the Map
It is possible to make visible rulers along the displayed map. A distance measurement
tool is also available.
To display rulers in the current environment, proceed as follows:
2-6
1) Select in the Tools menu, the Options... command.

2) In the Options dialog box, click on the Coordinates tab.
3) In the Display rulers part, check the rulers you want to display in the
workspace.
4) Click OK to validate.
Note:
Use the What's this help to get further description about the fields available in the
window.
2.3.7 Point-to-Point Analysis
Thanks to the button , U-Net allows the user to study the geographic profile
between two points on the map.

To display the profile between two points, proceed as follows:
1) Make displayed the map of your current project.
2) Left click on the Height profile button from the toolbar.
3) Left click once on the map to place the first point.

4) Move the pointer and left click on the map to place the second point.
U-Net automatically opens the Point analysis window and displays the height and
clutter profile between both points in the Terrain sections tab, which replaces the
Profile tab. In addition, it creates a folder called Terrain sections in the Data tab and
lists all the created terrain sections in a related table.
Click anywhere on the map or on an object in the explorer in order to replace the
Terrain section tab by the Profile tab.
2-7
Note:
z All the created terrain sections are displayed on the map.
z All the terrain sections are listed in a manageable table. Standard features for
managing table contents (Fields, Delete, Filter, Sort, Locate on the map, Display
columns, Copy/Paste, Fill up/down, ...) are available in a context menu (when right
clicking on column(s) or record(s)) and in the Format, Edit and Records menus.
You can also access the table content management from the Table tab of the
terrain section property dialog.
z When selecting a terrain section in the table (on the map), this one is
simultaneously selected on the map (in the table) and displayed in the Terrain
section tab.
z The generic U-Net display dialog is available in order to manage the display of
each terrain section. Open the terrain section property dialog and select the
Display tab.
z A terrain section can be modified. On the map, right click on it and check that the
Edit command is selected. On the map, left click on a point and drag it (the left
button pressed) where you want. The terrain section cannot be changed if the Edit
command is not selected.
z A context menu including the Copy and Print commands is available when right
clicking anywhere in the Terrain section tab.
z Standard features (Delete, Rename, and so on) are available in the context menu
of the terrain section folder.
2.3.8 Getting Distances on the Map
U-Net allows the user to get distances on the map easily by the use of the
Distance measurement button. This tool allows you also to determine the azimuth of
the current measurement segment.
To display distances on the map, proceed as follows:
2) Left click on the Distance measurement button from the toolbar.
3) Left click once in the map to put the start point.

4) Click on the map at each point you want to know the distance from the
previous point.
5) The distance from the first point, the distance from the previous point and the
azimuth angle of the current measurement segment are displayed in the extreme
lower left corner of your current environment.
2-8
6) Double click on the map to finish the current distance measurement session.
Note:
z Selected points are linked to each other by straight lines,
z U-Net reads azimuth in a clockwise direction.
2.3.9 Displayed Cursors
In U-Net, cursors will appear in different forms according to the current position or
command. The meaning of each possible shape is described in Table 2-1:
Table 2-1 Displayed cursors
Appearance Meaning
Wait The hourglass tells you to wait. When it

disappears, you can enter another command.
Arrow Use the arrow mainly to select objects or

commands. It will remain as long as a new
command has not been activated
Selection arrow Use the zone selection arrow to define a

selection region. You can use it inside a map to
define a zone to print or copy and in the
panoramic view to define the zone to be
displayed on the map. You must define a
«window» on the active map or panoramic view
by left clicking (1st corner of the «window» top
left) and «Sliding».
Polygonal Use the polygonal zone selection arrow to define

selection arrow a non-rectangular selection region. You can use
it inside a map to define a zone to filter either
sites or transmitters, to define computation and
focus zones, to draw vector or raster polygons.
You must define a "closed polygonal zone" on
the active map by left clicking several times.
Close the polygon by clicking twice.
Hand Only active on maps, use the hand to move the

visible part of the displayed map.
2-9
Appearance Meaning
Zoom tool Right click and left click with the mouse on the
map window to respectively zoom out and zoom
in on the map at the location of the mouse
pointer
Zoom area The magnifying glass tells you that U-Net is

waiting for a zoom «window» to be defined on
the active map by left clicking (1st corner of the
«window» top left) and «Sliding».
The transmitter symbol tells you that U-Net is

New transmitter waiting for you to place a transmitter on the
active map by left clicking. You can place as
many transmitters as you want by holding down
the button while you move the mouse and
pressing down the Ctrl key at the same time.
Sights The sight symbol will appear as soon as you

have activated the point analysis tool. This
informs you that U-Net is waiting for you to left
click on a point of the active map.
Sights placed The sight «placed» symbolizes the Receiver and

(Receiver) indicate the point on the map used for
calculations displayed in the Measurements or
Point analysis window (Profile / Reception /
Interference/Results/AS analysis). You can
access menu by right clicking on the point
analysis window.
Pencil The pencil indicates that you can define

polygonal zones without the clutter. U-Net is
waiting for you to left click on various points on
the active map. Double clicking will close the
polygon.
Deletion U-Net is waiting for you to select by left clicking

a newly created polygonal zone.
2-10
Appearance Meaning
Position U-Net is waiting for you to select an edge of the

indicator newly created polygon by left clicking. When you
click, the cursor changes into the Select/create
points on polygons cursor (below). Right clicking
will open a context-sensitive dialog box allowing
you to add a point, delete the polygon and
centre the map on the polygon.
Select/create Left clicking followed by dragging one of the

points on polygon edges, will add a new point to the
polygons polygon and modify its contour. Left clicking on a
point that already exists on the polygon, followed
by dragging allows you to move the point. Right
clicking opens a context-sensitive dialog box
allowing you to delete a point, delete the polygon
and centre the map on the polygon.
Placing a CW U-Net is waiting for you to left click on a point on

measurement the active map so it can place a CW
point measurement point there.
Placing points U-Net is waiting for you to left click on a point on

in a CW the active map so it can start a CW
measurement measurement path. Once you have made your
path first click, the cursor will change shape and
U-Net will wait for you to left click on various
points on the active map. Double clicking will
end the path.
Microwave link U-Net is waiting for you to left click on a point on

st
start the active map (1 point in the microwave link).
End Once you have made your first click, the cursor
will change shape and U-Net will wait for you to
left click on a second point on the active map to
nd
end the link (2 point in the microwave link)
Measurements Use the measurement tool to display projected

on the map distances and azimuths in the status bar.
Terrain section Drop two points with the mouse in order to

analyse the within terrain section (Point analysis
window)
2-11
2.3.10 Printing a Map
I. To print a map area
1) Click on the select an area tool in the zoom toolbar.
2) Define the area to be printed: Position the pointer on the map. Press and hold
the left mouse button at the north-west corner of the area, drag the pointer to
the south-east corner and then release the mouse button.
3) Select the Print area: Set command in the File menu. The selected area is
lighter.
4) Select the Page setup command in the File menu to configure your print layout.
The Page setup dialog box is displayed.
5) Use the What's this help to get description about the fields available in the
open window.
6) Select the appropriate options on the available fields you want for your print.
7) When your configuration is achieved, press OK to validate.
Note:
It is possible to insert,
z a logo on the top left corner
z a title on the top center
z and comments centered at the bottom
z of your prints through the Page setup dialog
II. To visualize your print sheet
Select the Print preview command in the File menu to visualize your print sheet.
III. To remove the selected area
Select the Print area: Remove command in the File menu.
Note:
z Visibility scales defined for objects are taken into account during printings or print
previews. Objects will appear only if the printing scale is within their respective
visibility range.
z Use the What's this help to get further description about the fields available in
windows.
2-12
Caution:
When using the Fit to page option, it is not possible to know the printing scale in
advance.
2.3.11 Exporting Maps to External Files
To export a map as an external file, proceed as follows:
1) Click on the Select an area tool in the zoom toolbar.
2) Define the area to be exported: Position the pointer on the map. Press and
hold the left mouse button at the north-west corner of the area, drag the
pointer to the south-east corner and then, release the mouse button.
3) Select the Export image... command in the File menu. In the Save as dialog box,
define the directory where you want to locate your file, the file name and the file
format. Press OK.
4) In the Size of created file dialog box, specify either the scale or the resolution
(dot/inch) to display the image with this resolution or the pixel size (m) to use
image as a georeferenced raster file. The minimum resolution is set to 1 meter.
5) Press OK to validate.
Note:
z Three file formats, *.tif, *.bil and *.bmp are supported. The *.bmp format is rather
dedicated to images and the *.tif and *.bil format to georeferenced images. Thus, to
use the exported map as an image, choose *.bmp format and define a scale and a
resolution; this last one will be written in the file. On the other hand, if you want to
use the exported map as geographic data, prefer the *.tif or *.bil format and specify
the pixel size. A geo-referencement file will be created. For additional information
see Supported data formats.
z Use the What's this help to get further description about the fields available in the
dialog box.
2.3.12 Exporting Maps to Other Applications
I. To copy an image to another application as a linked object
2-13
2) Define the area to be exported: Position the pointer on the map. Press and hold
the left mouse button at the north-west corner of the area, drag the pointer to the
south-east corner and then release the mouse button.
3) Select the Copy command in the Edit menu.
4) Open another application.
5) Select the Paste special... command in the Edit menu. In the Paste special dialog
box, choose the Paste link option and select U-Net document object in the
scrolling list box. Press OK to validate. A shortcut to the source file is created and
thus, the image may be updated by left clicking on it and selecting the U-Net
linked object: Convert... command.
Note:
if the U-Net file is modified and saved, the linked image is automatically updated.
II. To copy an image to another application as a screen shot
3) Select the Copy Image... command in the Edit menu. In the Copy image dialog
box, choose the screen resolution option or define the pixel size (m) and then,
press OK to validate.
5) Select the Paste special... command in the Edit menu. In the Paste special
dialog box, choose the Paste option and select Bitmap in the scrolling list box.
Press OK to validate.
III. To copy the north-west and south-east point coordinates of the image to
another application

3) Select the Copy Image... command in the Edit menu. In the Copy image dialog
box, choose the screen resolution option or define the pixel size (m) and then,
press OK to validate.
2-14
5) Select the Paste command in the Edit menu (or the Unformatted text option
when choosing the Paste Special... command).
Note:
The point coordinates vary according to the chosen option (screen resolution or pixel
size).
2.4 Working with the Explorer

2.4.1 Overview
The Explorer window has three tabs:
I. The Data tab
The Data tab allows the radio data and calculation management; it consists of diverse
folders depending on the modules included in the U-Net application:
z Sites
z Antennas
z Transmitters
z Predictions
z UMTS Parameters, CDMA/CDMA2000 Parameters, or GSM/GPRS Parameters
z UMTS Simulations or CDMA/CDMA2000 Simulations
z Traffic analysis (GSM/GPRS/EDGE projects only)
z Hexagonal design
z Microwave links
z CW Measurements and Test mobile data
II. The Geo tab
The Geo tab allows handling geographical data; it initially contains three folders and
more when you import other geographical data types (vector data, scanned images)
such as:
z Clutter classes
z Clutter heights
z Digital Terrain Model
z Population data
z Any generic geo data map
z Traffic (GSM/GPRS/EDGE/TDMA, WCDMA/UMTS, CDMA/CDMA2000)
z Terrain sections
2-15
III. The Modules tab
The Modules tab offers the propagation model management. It contains:

z A Propagation models folder where the following propagation models are listed:
1) Longley-Rice
2) Okumura-Hata
3) Costa-Hata
4) Standard Propagation Model
5) ITU 526-5
6) ITU 370-7 (Vienna 93)
7) WLL
z The list of the different AFP models available in your current U-Net version.
z Any additional module created via the API
In each tab, the created or imported objects are listed in corresponding folders using a
tree-structure presentation. Each object and folder offers a context menu available by
left clicking on it.
2.4.2 Renaming an Object
To rename an object, proceed as follows:

z Left click the object. Press the F2 key.
z Or Right click the object, and Select the Rename command in the context
menu.
2.4.3 Displaying the Object Properties

To open the property dialog of any object, proceed as follows:
1) Right click the object to open the associated context menu.
2) Select the Properties command in the context menu.
Note:
Depending on the object type, properties can be accessed by just double clicking on it.
Double clicking as the same function than the one in bold in the associated context
menu (left click on the object).
2.4.4 Deleting an Object
To delete an object, proceed as follows:

z Right click the object either in the explorer window or on the map (radio data),
Select the Delete command in the context menu.
2-16
z Or Click on the object in the explorer window, Press the Suppr key.
2.4.5 Managing Object Visibility
The and buttons are located in front of folders containing at least one object.
I. To open or close a folder, proceed as follows:
Click respectively on the or buttons. In the example (shown in Figure 2-1), the
Antennas folder is open, and the Sites folder is closed. A check box is displayed
next to each object visible in the workspace.
Figure 2-1 Antennas
II. To show or hide an object in the workspace, proceed as follows:
When a check box is checked, the corresponding object is visible in the workspace.
If you want to make the object invisible, simply uncheck the check box by clicking on
it.
The folders with grey check box contain both visible and invisible objects.
In the example, the sites are not displayed in the workspace unlike the transmitters.
Moreover, some prediction studies listed in the Prediction folder are not visible.
The different folders composing any environment can be ordered in layers with a view
to manage their display priority on the map. For example, in the example above, the
layer associated with the predictions is displayed over the layer associated with the
UMTS simulations. Indeed, in the tree above, the Predictions folder is located higher
than the UMTS simulations one. This feature is particularly useful for the display
managing of geo data objects.
To manage several objects display priority, proceed as follows:
2-17
1) Select the object you want to change the display priority on the map.
2) Drag it through the Explorer window.
3) Put it at the location that gives him the display priority order you want to
assign to it.
Note:
Putting over layers may get invisible under layers. To avoid that, do not forget to adjust
the transparency level of objects located over the others.
2.5 Working with Data Tables
2.5.1 Accessing Data Table

In U-Net, many radio data objects (sites, transmitters, repeaters, antennas, UMTS or
CDMA/CDMA2000 Cells, UMTS or CDMA/CDMA2000 parameters, microwave links...)
can be stored in a table, summarizing all their characteristics, and allowing you to use
filters, groups and sorts on contained data. Table can also be used to display
prediction reports and be exported ( imported) to (from) external files.
To access a Data table, proceed as follows:
1) Click on the appropriate tab from the explorer window.
2) Double click on the data folder (not available for prediction reports), or Right
click on the data folder to open the associated context menu.
3) Choose Open Table in the scrolling menu.
2.5.2 Managing Contents in Tables
To check displayed table data, proceed as follows:

1) Click the Data tab from the explorer window.
2) Right click on the data folder in order to display the associated context menu.
3) Select the data folder properties.
4) Choose the table tab from the window.
Another method:
1) Open the table you want to manage the contents.
2) Right click in any cell of the table, Choose the Table Fields command from the
open context menu.
3) Or Choose the Table Fields command from the Records menu in the main menu
bar.
2-18
It is possible to check and to manage (addition and deletion of new types) the data
stored in the table. In this window, are displayed the names, types, allocated lengths,
and default value (if existing) of the data available. Some objects are custom objects
of U-Net and cannot be removed and others are user-definable.
Use the What's this help to get further description about the fields available in the
window.
Note:
z When creating a new column (Add... button from any table tab window), you can fill
a choice list associated with the new variable (only with text format). Hence, when
assigning a value to this variable in the associated cell, you will be able to choose
one of the items from the scrolling choice list. Moreover, the cell can be also edited,
and any value can be assigned to it.
z It is possible to define a default value to any user-defined field. This default value is
automatically reported to the choice list box (only in text format).
z Even if tables summarize the characteristics of each item, it is possible to edit,
individually, most of them by two ways (See Editing contents in tables)
z Even if U-Net is case-sensitive, be aware that this could lead to some troubles
when connected to some database formats (e.g. Access)
2.5.3 Editing Contents in Tables
Two ways are available in order to edit Data table cells:
I. By choosing in a scrolling box
If a choice list has been defined in the field definition, you can edit contents in tables by
choosing in a scrolling box, as shown in Figure 2-2:
2-19
Figure 2-2 Data/Table of transmitters
II. By editing and changing the value or the text directly in the box
By editing and changing the value or the text directly in the box to edit contents in
tables is shown in Figure 2-3:
Figure 2-3 Data/Table of transmitters
2.5.4 Opening Dialogs from Tables
Since most of the tunable objects can be listed in tables, it is also possible to open the
properties dialog box of any site, antenna, transmitter or cell from the corresponding
table.
To do this, proceed as follows:
1) Open the considered table.
2) Select the record you want to open the property dialog box.
3) Double click on it, Or Right click on the record you want to open the property
dialog box.
2-20
4) Select the Record properties... command from the open context menu (or from
the Records menu).
Note:
Sometimes, clicking on narrow cells drives to just editing it. To avoid such behaviour,
and to open the property dialog for sure, double click on the extreme left part of the
table in the appropriate row.
2.5.5 Managing Table Display
The table formats can be personalized in order to retain pertinent data, or for a clearer
visualization. In that way, it is possible to manage the titles, styles or fonts, to adjust
the dimensions of the cells, and to hide or freeze columns.
I. Manage table titles
1) Activate the Table window.

2) Select the Format Title command from the Format menu in the menu bar.
3) A 4 tabs (Font, Colour, Borders, and Alignment) font dialog box opens.
4) Select the title format parameters from the available tabs in the open window.
5) Click either the OK or Apply button to validate.
II. Manage table columns

2) Select the Format Columns command from the Format menu in the menu bar.
3) A 4 tabs (Font, Colour, Borders, Alignment) font dialog box opens,
4) Select the table content format parameters from the available tabs in the open
window.
5) Click either the OK or Apply button to validate.
III. Change width or height

2) Set your cursor on the separation between lines or columns to be modified (in the
title bar for widths and in the 1st shaded column for heights)
3) Left Click and slide the cursor, and proceed as following Figure 2-4 and Figure
2-5.
2-21
Figure 2-4 Changing cells widths
Figure 2-5 Changing cells height
2-22
Note:
You can define a different width for each column. The height of the cells will be defined
for the entire table.
IV. Display the columns
1) Activate the Table window,

2) Select the Display columns command from the Format menu. The dialog box
allows to select the various columns which are displayed in the corresponding
table,
3) Or Right click into the table in order to get the related context menu, Choose
the Display columns command from the opened menu.
V. Freeze/Unfreeze a column
In large tables where the use of scroll bars is necessary, it may be useful to keep some
columns visible, by freezing them on the screen. This feature is always possible
except for tables containing reports.
To do so, proceed as follows:
2) Select the column to be frozen by left clicking on the corresponding title (to freeze
several columns, slide on the associated titles after the 1st click - you can only
select several columns if they are adjacent to each other - ).
3) Select the Freeze columns command from the Format menu.
To unfreeze frozen columns, select the Unfreeze columns command from the
Format menu
VI. Hide columns
There are three ways to hide columns:

Method 1:
2) Left click on the title of the column to hide (to hide several columns, hold the
Ctrl key when selecting the other columns to hide).
3) Select the Hide columns command on the Format menu.
Method 2:
2) Do as the same way as in the resize columns method seen above, and slide
the pointer on the title bar in order to obtain a zero width column.
Method 3:
2-23
Unselect the concerned column in the Display columns command from the Format
menu.
To display again the hidden columns, use the Display columns command from the
Format menu.
VII. Moving columns
In large tables it can be practical to group columns of interest, or to read data in a

special order. In U-Net, the column order can be managed easily.
2) Select the column to be moved by left clicking on the corresponding title (to
move several columns, slide on the associated titles after the 1st click - you can
only move several columns if they are adjacent to each other - ).
3) Click again on the selected columns zone and drag it until the required target.
When this zone is dragged, the place where the columns will be displayed is
referenced by a red line.
2.5.6 Copying and Pasting in Tables
U-Net provides some powerful tools in order to use the copy and paste functions in
tables. You may either copy any cell with the copy (Ctrl+C or Copy command from the
Edit menu) or cut (Ctrl+X or Cut command from the Edit menu) functions and paste it
in any available cell from any table (Ctrl+V or Paste command from the Edit menu).
Moreover, it is possible to paste several times the same cell in a table. To do so,
proceed as follows:
1) Activate the table window.
2) Select the cell zone where you want to copy the data, which is shown in Figure
2-6.
Figure 2-6 Paste Example

2-24
3) If you want to copy the top cell in the selected cells, either use the Fill down
(Ctrl+D) shortcut or the Fill down command from the Edit menu, which is
shown in Figure 2-7.
Figure 2-7 Copy and paste example
4) If you want to copy the bottom cell in the selected cells, either use the Fill up
(Ctrl+U) shortcut or the Fill up command from the Edit menu, which is shown
in Figure 2-8.
Figure 2-8 Copy and paste example
2.5.7 Exporting Tables in External Files
Tables, table columns or fields can be imported and exported to and from U-Net.
U-Net is capable of importing from and exporting to tabulate ASCII text files and
provides different possible configurations for import and export.
To export a table, proceed as follows:
2-25
2) Right click on the table window to open the context menu.

3) Select Export from the menu.
4) Use the What's this help to get description about the fields available in the open
window.
5) Either specify export settings.
z Select the separator and the decimal symbol.
z Specify if you want to save the table header in the file.
z Use the buttons and in order to define the list of
fields to be exported. Finally, use the buttons and in order to change the
order of fields to be exported.
6) Or select an export configuration if defined.
z Click on the Load button.
z Specify the directory where the configuration file is located.
z Click on Open to close the dialog.
7) Click OK to export.
8) 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.
2.5.8 Importing Tables from External Files
Tables, table columns or fields can be imported and exported to and from U-Net.
U-Net is capable of importing from and exporting to tabulate ASCII text files and
provides different possible configurations for import and export.
To import a table, proceed as follows:
2) Right-click on the table window to open the context menu.
3) Select Import from the menu.
4) In the open dialog box, define the directory where the file to be imported is
located, select the file and click on open.
window.
6) Either specify import settings.
2-26
z Select the separator and the decimal symbol.

z Specify the number of the first line containing data to be imported.
z In the preview table, define correspondence between the fields to be imported
(available in your file) and the U-Net internal fields. All the columns found in the
file to be imported are listed in the first row (Source). The second row (Destination)
enables you to specify name of the corresponding field in the U-Net table. In the
Destination row, click on each cell and choose the corresponding field (in which
you want to recover the source column content) in the scrolling menu. An
additional option “Ignore” is available in the scrolling menu. Select it if you do not
want to import the source column content in the U-Net table.
7) Or select an import configuration if defined.
z Click on the Load button.
z Specify the directory where the configuration file is located.
z Click on Open to close the dialog.
8) Click OK to import.
Note:
z Import 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.
z An option “Update records” is available in the dialog. It enables you to refresh
properties of records already existing in the table.
2.5.9 Printing Data Tables
In U-Net, it is as easy to print Data table as maps. To do this, make active your table,
and choose the Print... command from the File menu in the general menu bar.
Like for maps and reports, it is also possible to preview the print to be made on tables.
2.6 Filtering/Grouping/Sorting Data

2.6.1 Sorting and Filtering in Tables
In U-Net, data may be sorted and/or filtered in particular in tables (this is also possible
in data folder or on the map). After filtering, excluded data are not taken into account in
calculations. There are many ways to use this feature.
I. Sorting in Tables
Data may be sorted in ascending (A to Z, 1 to 10) or descending (Z to A, 10 to 1) order.

Any field except the antenna patterns field may be sorted.
2-27
To sort data in a table, proceed as follows:

2) Select a title of a column. This column will be the sort reference.
3) When selected, right click or select the Records menu. Then select the Sort
Ascending or Sort Descending option from the scrolling menu.
II. Sorting in several columns
U-Net offers to sort several table columns at the same time.

2) Select the columns to be sorted by selecting them in the title bar.
3) When selected, right click or select the Records menu. Then select the Sort
Ascending or Sort Descending option from the scrolling menu.
4) Sorts are successively applied to each selected column, if only these are
adjacent to each other.
III. Filtering in Tables
To filter a type of data in a table, proceed as follows:

2) Select an item, a type of antenna in the transmitters table, for example, when
selected, right click or select the Records menu. Then select the Filter by
selection (resp. Filter excluding selection) option from the scrolling menu to keep
only (resp. to reject) data which have the antenna (for example) as the selected
item.
See Examples of filter in tables
Filtering data in several columns is possible in the same way not only if selected items
are adjacent to each other. To select different cells, hold the Ctrl key pressed when left
clicking.
IV. Advanced data Filtering in Tables
U-Net enables to make complex filters, by combining several criteria on fields. This
can be managed by using criteria either in the Advanced filter option from the Records
menu, or by choosing the general tab from the item properties which is in
consideration.
The authorized filtering criteria are shown in Table 2-2.
Table 2-2 Formula
Formula Data are kept in the table only if
=X value equal to X (X may be a number or characters)
2-28
Formula Data are kept in the table only if
<> X value not equal to X (X may be a number or characters)
<5 numerical value is less than 5
>7 numerical value is greater than 7
<=10 numerical value is less than or equal to 10
>=20 numerical value is greater than or equal to 20
Combinations of filters are made firstly horizontally, then vertically.

See Advanced filtering Example and counter-examples (1 2).
V. Adding/modifying a data in any filtered/sorted table
When a new item is added to the project (base station, site, transmitter ...) or when a
data is modified, it is possible to reapply a previous filter/sort configuration.
2) Right click on the item in the data window or select the Records menu.
3) Select the Apply filter/sort option from the scrolling menu.
VI. Restoring data in Tables
To restore filtered data in tables, select the Show all records option from the
Records menu.
Filtering, by any way, applies automatically to maps and data folders. As in tables,
U-Net permits to manage easily data from folders.
2.6.2 Examples of Filter in Tables
Examples of filter in tables are shown in Figure 2-9 and Figure 2-10.
2-29
Figure 2-9 Filter by selection (Antenna AO9209)
2-30
Figure 2-10 Filter excluding selection (Antenna AO9209)
2.6.3 Filtering Radio Data

In U-Net, filters may be applied to items with results displayed simultaneously in tables,
in the map and in the data folders. All data not checking the filters are not taken into
account in calculations.
Filter tools are available:
z In the Advanced Filter option from the Records menu (when the Data table
window is on) or from the general tab window from the item properties (see
features in Sorting and filtering in tables).
z By using the Filter by selection or Filter excluding selection options from
either the Records menu or by right clicking directly on the object in the table to
be used as reference for the filtering (see features in Sorting and filtering in
tables).
z From the Properties dialog box associated with the current folder.
To filter any folder from its associated Properties dialog box, proceed as follows:
1) Click on the Data tab in the Explorer window.
2) Right click on the folder you want to sort to open the associated context menu.
3) Left click in the scrolling menu on Properties.
4) Select the General tab from the open window.
2-31
5) Click on the button.

filtering dialog window.
7) Click the Filter tab and choose the filtering reference variable(s) and the
associated filtering way(s).
8) Select a field you want to use for filtering among the discrete fields. U-Net lists the
choice list if the selected field is a text field with a choice list, or all the values of
the selected field in table.
9) Check/uncheck boxes to keep/exclude values from tables, map and explorer.
U-Net displays the defined filter at the bottom of the dialog.
10) Click OK to apply filter.
Note:
z The way the data contained in the current folder are filtered can be saved in a
configuration template in order to be used later.
z It is also possible to use wildcard characters when defining advanced filter criteria
on fields with the text format, which is shown in Table 2-3.
Table 2-3 Filter
Filter criteria Function
Filters objects which the chosen field

*string*
contains the string of characters
Filters objects which the chosen field begins

string*
with the string of characters
Note:
Sites may belong to several groups. In this case, let us assume that each site has an
associated field such as a list of groups (for example “gr1 gr3 gr5”). Therefore, by
entering *gr5* as criterion, you can filter all the sites included in gr5.
z It is possible to select several values at once. To do this, click one or several
values using shift and/or Ctrl button at the same time and then, check/uncheck one
of boxes.
z Advanced site filters are available using the site list feature.
2-32
2.6.4 Advanced Filtering Example
Let's consider an U-Net project which contains only antenna of two types:
GSMA090-12-6 and AO9209. All transmitters using A09209 antenna have only 0°
azimuth instead of 0°, 120° and 240° of azimuth for transmitters using GSMA090-12-6
antenna, which is shown in Figure 2-11.
Figure 2-11 Transmitters
Example: initial table

A goal could be, for example, to extract GSMA090-12-6 antennas whose azimuths are
0° and 240°. This can be done by using the following syntax in the window described
just below Figure 2-12:
2-33
Figure 2-12 An example of filtering/sorting
z The type of columns to be filtered is chosen from a scrolling menu.

z The second line point out that will be kept GSMA090-12-6 antennas whose
azimuth is lower than 120°.
z Or any type of antenna whose azimuth is greater than 120° (4th line). For this
constraint, no AO9209 antenna is concerned.
2.6.5 Advanced Filtering Counter Example 1
Here are a typical example which could drive an U-Net user to mistakes in filter and
sort syntax. The goal stays the same than in the example just before. The examples
are shown through an advanced filter window and the corresponding filtered and
sorted Data table described just below Figure 2-13.
2-34
Figure 2-13 Advanced filtering

z The second line point out that will be kept GSMA090-12-6 antennas whose
azimuth is greater than 120°.
z Or any type of antenna whose azimuth is less than 120° (4th line), i.e. both
GSMA090-12-6 and AO9209 antennas.
2.6.6 Advanced Filtering Counter Example 2
Here is a typical example which could drive an U-Net user to mistakes in filter and sort
syntax. The goal stays the same than in the example just before. The examples are
shown through an advanced filter window and the corresponding filtered and sorted
Data table described just below Figure 2-14.
2-35
Figure 2-14 Advanced filtering

z The second line point out that will be kept any type of antenna whose azimuth is
greater than 120°.
z Or any type of antenna whose azimuth is less than 120° (4th line).
z GSMA090-12-6 antennas will be kept without any constraint.
The result indicates there have been no filtering. The final table is identical with the
initial table.
2.6.7 Sorting a Folder
In the data window, items (transmitters, sites, simulations, etc...) are classified in
folders. You can unfold them by left clicking on the button associated with an item.
You can fold them by left clicking on the button.
In U-Net, every item folder can be sorted in the same way as in tables. Whenever a
Data table is sorted, the display of the corresponding item is automatically modified in
the associated folder.
2-36
Moreover, you can sort any folder from its associated properties dialog box. To do
so, proceed as follows:
1) Click the Data tab in the Explorer window.

sorting dialog window.
7) Choose the sorting reference variable(s) and the associated sorting way(s),
Note:
The way the current folder is sorted can be saved in a configuration template in order
to be used later.
2.6.8 Arranging Items in Groups
In U-Net, it may be very practical to group data by characteristics. This can be done on
the data folder or subfolder of any item. The group corresponds to the Contents in
tables. Several levels (limited by the memory of your computer) of grouping are
available.
To arrange any folder or subfolder in group(s) of variables, proceed as follows:
2) Right click on the folder or subfolder you want to arrange in groups to open the
associated context menu.
z Left click in the scrolling menu on Properties.
z Select the General tab from the open window.
z Click on the button.

z Use the What's this help to get description about the fields available in the open
grouping dialog window.
z Choose the grouping reference variable(s) and the associated grouping
order.
z Click OK to validate.
2-37
To come back to a standard display, either chooses the Group by none option in the
scrolling menu or use the grouping dialog window and put back the grouping reference
variables in the Available fields box.
Note:
The way the data contained in the current folder are grouped can be saved in a
configuration template in order to be used later.
2.6.9 Examples of Grouping by
In the following transmitters folder, sites in red are active, sites in white are inactive
described just below Figure 2-15:
Figure 2-15 Data/Transmitters/Group by active sites
The obtained transmitters folder is classified in two groups, one for the active sites,
one for the inactive sites, which is shown in Figure 2-16:
2-38
Figure 2-16 Data/Transmitters - Transmitters grouped by activity
Note:
In U-Net, activity is a Boolean. Active has the true value, whereas inactive has the
false value.
2.6.10 Using a Group by/Sort/Filter Configuration
In U-Net, the way data contained in any folder are grouped, filtered and sorted can be
saved in a configuration template in order to be used later. Configuration templates are
directly embedded to save .atl projects. Any configuration is erasable.
To create a configuration template (from an existing data organization), proceed as
follows:
2-39
6) Type the configuration name in the open saving configuration dialog window. The
configuration created is listed in the configuration scrolling list in the General tab
and is available for any data organization in the current folder only.
Note:
For transmitters, a default configuration called As Sites folder is available. Using this
configuration enables you to arrange transmitters in the Transmitters folder according
to the organization criteria defined for sites.
You can define several configurations and use them when needed. The configurations
you’ve created are available from the context menu associated with any folder by
using the Configuration command and one of the listed objects in the scrolling menu.
To apply the configuration used to newly created objects, select the Apply current
configuration command in context menus.
Existing configurations are not saved in database. Nevertheless, in order to keep
these, and potentially share them between users, U-Net provides a feature allowing
you to save user configurations (including also geo data set and computation zone) in
an external file.
See Exporting user configuration to an external file.
2.6.11 Creating Subfolders
In U-Net, you can manage your data folders in subfolders in order to display them in
different ways. You can, for example, create a subfolder for each sorting or filtering
and compare it with each other.
1) In the data folder window, right click on the item you want to create a subfolder.
2) Choose the Create a folder option from the scrolling menu.
3) A subfolder containing a copy of the original folder content is created.
You can manage your data in subfolders as in the original folder. Every subfolder is
associated with a Data table window. You can display each subfolder on the map, by
checking ( ) or not ( ) the check box associated with each subfolder. You can
manage the visibility of the data as described in the Object visibility topic.
If you delete a subfolder, of course, data are not deleted. If you delete the last
remaining subfolder, its data go directly to the initial folder. due to refresh consideration,
it may happen that data disappear. To come back to the display of all objects of the
folder, use the group by none function related to the considered folder.
2-40
2.6.12 Reorganizing Data after Modifications
When some data are either added or modified, their properties may not be consistent
with the current folder configuration. To make this configuration respected, just choose
the apply current configuration from either the Records menu (in case of displayed
table) or from its associated context menu.
Note:
The configuration is automatically applied to radio data dropped on the map. For
example, let's assume that the current configuration filters transmitters which azimuth
is 240°. We build a tri-sector station whose azimuth is 0,120 and 240°. Once dropped,
0 and 120° azimuth transmitters are automatically filtered. Only the 240° azimuth
transmitter is kept.
2.6.13 Filtering Data in a Polygon
In large projects, it may be useful to work only on a certain number of sites and
transmitters, in order to reduce the computation cost or to make visualization clearer
either on the map, table or in the data folder.
To filter data inside a polygon, proceed as follows:
1) Click the Data tab from the Explorer window.
2) Right click on the Sites folder to open the associated context menu.
3) Choose the Filter inside a polygon command from the open menu.
4) Select the Draw option, Draw the filtering polygon on the map with the mouse,
each left click corresponding to an angle, Close the zone by double clicking (not
displayed when closed ), Or Select the computation zone option, Only data
(Sites and transmitters) contained in the considered polygon filter are kept.
The remaining objects in the polygon are displayed both in the data folders, in the Data
tables and on the map. The filtering polygon is distinguished from others by its
characteristic thick blue border. This facilitates recognizing the filtering polygon on the
map.
In this zone, you may use current sorts, filters or groups or create new ones.
2-41
Note:
z You may filter sites inside a polygon even if they are grouped. The filter is applied
to subfolders.
z The polygon filtering can be saved in a Site folder configuration.
z This filter is automatically applied to transmitters.
z The filter is saved in the .atl document.
z The filter is taken into account when defining a configuration.
z The current computation or focus zone can also be taken as polygon filter (see
their associated context menu).
2.6.14 Removing the Polygon Filter
In U-Net, radio data can be filtered in a polygon. As other filters, this can be saved in
folder configuration.
To cancel the polygon filter, proceed as follows:
2) Right click on the Sites folder to open the associated context menu.
3) Choose the Remove polygon filter command from the open menu.
4) All existing data from the current project are then displayed.
2.7 Managing Display in U-Net

2.7.1 Defining the Display Properties of Any Item Folder
In U-Net, most of the item groups (sites, transmitters, microwave links, predictions,
simulations, measurements, DTM maps,..) are managed in the same way concerning
their display. For each of them, a homogenized dialog window is available allowing you
to define the type of field(s) to display, and how. Moreover, from this standard window,
it is possible to display labels related to the displayed object, and to manage the
information available using the tip tool when pointing the object on the workspace.
Finally, you will be able to choose or not to display the related legend in the Legend
window.
To access the display property window of any object, proceed as follows:
1) Click the appropriate tab in the Explorer window.
2) Right click on the folder related to the objects from which you want to manage
the display properties.
3) Left click the Properties command from the open context menu,
4) Click on the Display tab from the open window.
2-42
window.
6) Set the display parameters of the current object.
When working on the display of an item folder (e.g. Site or Transmitter folder), it is
possible to choose among several display types:
z Single: same representation for any object of the folder.
z Discrete values: representation according to the value of a discrete field available
in the table related to the current object(s).
z Values interval: representation according to the value of a numerical field
available in the table related to the current object(s).
Note:
z Whatever is the display type chosen, it is possible to change the displayed colours.
To do that, select the threshold to modify and use the commands contained in the
scrolling menu when clicking the button.

z You can modify globally thresholds and associated parameters using the values
interval display type and the Shading... command (Actions button).
z Each individual display property (e.g. of just one site) is reachable by selecting the
display tab from the item Properties dialog.
2.7.2 Managing and Displaying Legends
Any displayed U-Net object may have its associated legend in the Legend window.
To make displayable legend associated with any object, proceed as follows:
2) Right click on the folder related to the objects from which you want to manage
the legend properties.
window.
6) Check the Add to legend box.
8) The associated legend is now displayed in the Legend window.
To open the Legend window, just check the Legend command from the View menu in
the menu bar. A new window is then displayed in the current environment.
2-43
Note:
z Only displayed objects can have their legend in the Legend window.
z The contents of the legend are given in the threshold window definition and is
editable.
z The legend window can be printed as any other active window. To do this, right
click in it and select the Print.. command in the open context menu.
2.7.3 Thresholds, Colours and Legends
The thresholds associated with colours are so many criteria making up a range of
criteria (e.g. below threshold from -45dBm to -70dBm).
You can use this association to provide a colorimetric representation of received signal
levels, path losses, or any other field displayed in values interval in U-Net.
The definition of thresholds can be performed by using the button of

U-Net generic display windows. The several commands are available are listed below:
z Select all: U-Net automatically selects all the representations available in the
table.
z Delete: U-Net removes representations selected in the table.
z Insert before: This command is available only if a representation is selected in the
table. U-Net adds a new threshold in the table and places it before the selected
one.
z Insert after: This command is available only if a representation is selected in the
table. U-Net adds a new threshold in the table and places it after the selected
one.
z Properties: This command is available only after selecting one or several
representations of the table. U-Net opens the Display window where you may
change color and style.
z Shading: U-Net opens the Shading window. You can define the number of value
intervals and configure their displays. Enter the highest (First break) and lowest
(Last break) thresholds and an interval between thresholds. Define the color
shading by choosing beginning and colours. Finally, you can select a coverage
interior and a style of line for coverage contour.
You can set coverage transparency by moving the cursor on the transparency scale
and specify a visibility scale.
If available, the legend associated with each threshold allows you to display a text
instead of the threshold in the legend. If no text has been entered, thresholds are
displayed with associated colours, which described just below Figure 2-17.
2-44
Figure 2-17 Defining thresholds
In the example above, in the case of the signal level option, the defined thresholds
mean:
z Signal level >= -65 red (1st color from top),
z -65 > Signal level >= -105 shading from red to blue (9 thresholds),
z Signal level < -105 not drawn on coverage.
Note:
z Shading, Insert before and Insert after features are only available in case of a value
intervals display type.
z When double-clicking on any representation in the table, U-Net opens the
associated Display window.
2.7.4 Displaying Object Labels on the Map
Two solutions are generally available in order to display information related to

displayed objects (e.g. sites or transmitters) on the map within U-Net. This information
can be either permanently displayed or temporary reachable in an help popup related
to any pointed object on the map.
To make displayed permanently labels related to any object on the map, proceed as
follows:
2) Right click on the folder related to the objects you want to display related labels
on the map.
window.
6) Check the items to be displayed in the Label scrolling menu.
2-45
8) The associated labels are now displayed on the map close to the referring
objects.
Note:
You can display more many labels than parameters related to the considered object.
E.g., even if you add a new field in the transmitter table, this field will be available to be
displayed as a label for all the transmitters.
2.7.5 Using the Tips Tool to Get Information
Two solutions are generally available in order to display information related to

displayed objects (e.g. sites or transmitters) on the map within U-Net. This information
can be either permanently displayed or temporary reachable in a help popup related to
any pointed object on the map.
To make available information related to any pointed object on the map, proceed as
follows:
2) Right click on the folder related to the objects you want to display related tables
on the map.
3) Left click the Properties command from the open context menu.
window.
6) Check the items to be displayed in the Tips text scrolling menu.
8) The associated information can be now given in help popups when pointing
any item on the map with mouse.
To make active the tips information, click the from the toolbar. To inactive this
function, click it again ( ).
Note:
You can display as many information in popup as parameters related to the
considered object. E.g., even if you add a new field in the transmitter table, this field
will be potentially available to be displayed in tip balloons.
2-46
2.8 Using Handy Tools

2.8.1 Using the Undo/Redo Command
Undo/Redo commands are available in U-Net. It is a first step to enable users to undo
and redo:
z Most of modifications performed in workspace as: creating, deleting and
moving a site (even moving a site to a high point), a station or a group of stations,
modifying antenna azimuth, moving a transmitter or deleting a transmitter.
z Management tasks performed in Explorer window as creating and deleting any
object (site, transmitter, repeater, antenna, link, group of hexagons, measurement
path, prediction study, map, propagation model...) except simulations in UMTS
projects.
z Management tasks performed in tables (add or delete records, paste in tables,
fill down or fill up commands).
The Undo/Redo is reachable from the Edit menu when available.
Note:
The last 10 actions can be undone, unless you perform an action which is not
supported by the undo feature. In that case, the undo memory is cancelled.
2.8.2 Refreshing Maps and Folders
A refresh function is available in U-Net. This feature allows you to reload currently
displayed maps and apply the current configurations to folders (e.g. after an addition of
inconsistent data not respecting a filter).
To do this, use the button from the tool bar or the shortcut key F5.
Note:
This feature allows you to cancel some potential refresh problems of the map.
2-47
2.8.3 Setting Document Prints
In U-Net, many windows can be easily printed: maps, tables, legend window, CW
measurement window, Test mobile data window, point analysis window. Concerning
maps and tables, a preview feature is available.
To open the print preview of any table or map, proceed as follows:
1) Make active the window you want to print.
2) Select the Print Preview command from the File menu in the general menu
bar.
3) A preview window (in which you can zoom in or zoom out) opens.
4) Use the Print... or the Close command.
The way tables and maps are printed can also be managed easily in order to provide
well-organized and customized printed outputs.
To setup any table or map print, proceed as follows:
1) Make active the window you want to parameter the print.
2) Select the Page Setup... command from the File menu in the general menu bar.
window.
4) A fit representation of the print document is displayed and some options dealing
with customization are available.
5) Click OK to close the dialog.
Note:
The selected options (e.g.: erase outside of focus zone) are taken into account in print
preview.
2.8.4 Locating Any Point on the Map
U-Net provides a tool which enables you to quickly find existing sites and vectors on
the map and to locate any point on the map. It is possible to search for a site or a
vector according to any of its text type attributes.
The first step consists in opening the Map locating dialog. To open it, in the tool bar,
click on the map locating icon . The Map locating dialog consists of three parts
dedicated to:
z The search for site
z The search for vector
z The location of any point
2-48
The three find options cannot be used at once. Therefore, select one of them.
To search for any point on the map, proceed as follows:
1) Select the Point option.
2) In respective boxes, enter x-coordinate and y-coordinate of the point you want to
find on the map.
3) Keep the Draw point option selected.
4) Click on OK. U-Net displays a target on the map and centres the map on it.
Note:
To hide the target, right click on it and select the Delete command from the context
menu.
2.8.5 Locating any Site on the Map
In order to locate any site on the map, U-Net provides two different tools.
I. Search Bar
1 - A search bar is available to find the location of sites on the map. The Search bar
can be open or closed by selecting the Search bar command in the View menu.
This bar becomes a floating window by double clicking on it. In this case, it is possible
to resize it.
To search an existing site in a network using the search site tool, proceed as
follows:
1) In the Search bar, type the first characters of the site name in the Find site box.
U-Net displays a scrolling list containing all the sites, which the name begins with
this string of characters.
2) Either Select the site in the list, or Go on typing the site name to reduce the
number of sites in the list.
3) After choosing the site in the list, U-Net automatically centers the map on the
selected site.
Note:
z As in advanced filters, it is possible to use the “contains” (*string*) and “begins with”
(string*) criteria to search for sites which name contains or begins with the given
string. Be careful, *string is unknown.
z Use the F3 shortcut to be automatically placed in the Find site box.
2-49
II. Dialog
dedicated to:
Then, this tool works like the "Find site" tool (See above). To search for any site on
the map, proceed as follows:
1) Select the Site option.
2) Open the Field scrolling menu and choose in the list one text field (among the
text type attributes of sites).
3) In the box below, type the first characters for the selected attribute (name or a
comment for example). U-Net displays a scrolling list containing all the values,
which begins with this string of characters, and gives into brackets the name of
corresponding sites/vectors.
4) Either Select a value in the list or Go on typing to reduce the number of
values.
5) After choosing the value in the list, click on OK. U-Net automatically centres the
map on the site with the selected value.
Note:
(string*) criteria to search for sites, which selected field contains or begins with the
given string.
z Be careful, *string is unknown.
2.8.6 Locating any Vector on the Map
2-50
dedicated to:
To search for any site on the map, proceed as follows:
1) Select the Vector option.
2) Open the Field scrolling menu and choose in the list one text field (among the
text type attributes of vectors).
3) In the box below, type the first characters for the selected attribute. U-Net
displays a scrolling list containing all the values, which begins with this string of
characters, and gives into brackets the name of corresponding sites/vectors.
4) Select a value in the list, Or Go on typing to reduce the number of values.
5) After choosing the value in the list, click on OK. U-Net automatically centers the
map on the vector with the selected value.
Note:
(string*) criteria to search for sites, which selected field contains or begins with the
given string.
z Be careful, *string is unknown.
2.8.7 Synchronizing Vector Selection and Data Table
Vectors are made of points containing some attributes/properties. They can be geo
data vectors, CW measurement paths, or test mobile data paths and related to a table
in which is displayed the properties of each point. When selecting a point composing a
vector, if the data table is displayed in the same time, U-Net synchronizes
automatically both. Indeed, the tool selects in the table the records related to the
selected point on the map.
Note:
When working on a measurement path, you can use the specific CW measurement
window with this feature. When moving with the pointer along the path, the selection in
the table is automatically made.
2-51
2.8.8 Using the Status Bar to Get Information
The status bar is one of the different objects that can be displayed or not using the
View menu. Once checked, the status bar is located at the measurement tool (
button in the toolbar), i.e. distances between successive points and azimuths. The
right part displays information about the location where points the mouse on the map:
X and Y coordinates (respecting the defined display coordinate system), the altitude
(extracted from the imported DTM file) the clutter class (as defined in the clutter
classes property dialog) and the clutter height (extracted from clutter height file(s) if
available in your .atl document, or otherwise read in the clutter classes folder
description).
Note:
It is possible not to display altitude, clutter class and clutter height information in the
status bar. To do this, add the syntax described below in an U-Net.ini file.
[StatusBar]
DisplayZ=0
DisplayClutterClass=0
DisplayClutterHeight=0
You must create this file and place it in the U-Net installation directory. It 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.
2.8.9 Using Icons from the Tool Bar
U-Net provides a large number of commands that can be accessible using icons
located in the tool bar. Some of them are also linked to shortcut keys.
The different icons located in the toolbar are listed below:
I. In the Standard toolbar
: Open the new project dialog (like the Ctrl+N shortcut)
: Access the Open file dialog (like the Ctrl+O shortcut)
: Save the current active project (like the Ctrl+S shortcut)
2-52
: Cuts the selected data (like the Ctrl+X shortcut)
: Copy the selected data (like the Ctrl+C shortcut)
: Paste the content of the clipboard (like the Ctrl+V shortcut)
: Print the current active window (table or map) (like the Ctrl+P shortcut)
: Open the About U-Net dialog
II. In the Radio toolbar
: Create a new station based on the currently selected model
: Create a new group of hexagons based on the currently selected station
template ( no hexagon radius defined)
: Station model currently selected
: Create a new repeater related to the currently selected transmitter
: Neighbour graphic management for the selected transmitter
: Activate the point analysis window
: Calculate only invalid matrices, or calculate all unlocked coverage and pending
simulations (like the F7 shortcut)
: Force the calculation of all the matrices from scratch, calculate all unlocked
coverage and pending simulations (like the Ctrl+F7 shortcut)
III. In the Map toolbar
: Activate the area selection tool
: Reload map and folders (like the F5 shortcut)
2-53
: Move the map window (like the Ctrl+D shortcut)
: Map scale currently used
: Previous/Next view (zoom and location)
: Zoom in on the map and centre on the cursor location (like the Ctrl+A
shortcut)/Zoom out on the map and centre on the cursor location (like the Ctrl+R
shortcut)
: Define a zoom area on the map (like the Ctrl+W shortcut)
: Activate the tip tool feature (inactivated:
: Get distances on the map
: Activates the map locating tool in order to locate any point, site or vector
: Displays point-to-point profile analysis
IV. In the Microwave link toolbar
: Create a new microwave link.
V. In the Search toolbar
: Centre map around the selected site.
VI. In the Vector edition toolbar
: Create a new vector layer (either in the Geo or in the Data tab)
: Select the vector layer being currently edited
: Draw a new vector polygon
: Draw a new vector line
2-54
: Draw points
: Allows the user to merge several vector polygons
: Allows the user to make holes in polygons
: Permits to keep only overlapping areas in order to create the resulting

polygon
: Allows the user to cut a polygon in several parts
Note:
The description of each icon is given in a tip balloon when pointing the mouse on it.
2.8.10 Using Shortcuts in U-Net
Like many other applications working under Windows environment, U-Net provides a
complete set of shortcuts in order to make easier and quicker the way to use it.
The different available shortcuts are listed below (some of them are linked with icons
of the toolbar):
I. Using the Ctrl key
Ctrl+A: Select all records in tables (table active) or Zoom in on the map (like left click
on the map when the tool is active)
Ctrl+C: Copy the selected data (like icon from the toolbar)
Ctrl+D: Fill down selected data in tables (table active) or Move the map window (map
active - like icon from the toolbar)
Ctrl+F: Open the find in tables dialog
Ctrl+N: Open the new project dialog (like icon from the toolbar)
Ctrl+O: Access the Open file dialog (like icon from the toolbar)
2-55
Ctrl+P: Print the current active window (table or map) (like icon from the toolbar)
Ctrl+Q: Activate the Zoom In/Out tool
Ctrl+R: Zoom out on the map (like right click on the map when the tool is active)
Ctrl+S: Save the current active project (like icon from the toolbar)
Ctrl+U: Fill down selected data in tables (table active)
Ctrl+V: Paste the content of the clipboard (like icon from the toolbar)
Ctrl+W: Define a zoom area on the map (map active) (like icon from the toolbar)
Ctrl+X: Cut the selected data (like icon from the toolbar)
Ctrl+Y: Redo the previous undone function

Ctrl+Z: Undo the last function
II. Using the F keys
F3: Locate the cursor directly within the search site tool
F5: Reload map and folders (like icon from the toolbar)
F7: Calculate only invalid matrices, calculate all unlocked coverages and pending
simulations (like icon from the toolbar)
Ctrl+F7: Force the calculation of all matrices from scratch, calculate all unlocked
coverages and pending simulations (like icon from the toolbar)
Note:
When a letter is underlined in a command (Use the Alt button to make underlines
active in Windows 2000), press Alt+letter to run it.
2-56
2.9 Tips and Tricks

2.9.1 How to Import Geo Data Easily
Drag and drop feature is available for any geo data object to import in U-Net. To do this,
just select the accurate geo data file in your file explorer and drag it to U-Net. The
format will be automatically detected by the tool.
This can also be made on PlaNET® index data file.
2.9.2 How to Change Globally a Value for All the Transmitter
The right way to make global changes is to open the Transmitter table, modify the
contents in the first cell, select all the columns and then use the fill-down feature,
available in the Edit menu or with the shortcut Ctrl+D.
To select all the cells of the column, the easiest way is to select the first one, then
select the last one holding the Shift button.
2.9.3 How to Find Easily a Site on the Map
A search bar is available to find the location of sites on the map. The Search bar can
be open or closed by selecting the Search bar command in the View menu.
In the Search bar, type the first characters of the site name in the Find site box. U-Net
displays a scrolling list containing all the sites, which the name begins with this string
of characters. Then, either select the site in the list, or go on typing the site name to
reduce the number of sites in the list. After choosing the site in the list, U-Net
automatically centres the map on the selected site. As in advanced filters, it is possible
to use the “contains” (*string*) and “begins with” (string*) criteria to search for sites
which name contains or begins with the given string.
A map locating dialog is also available and provides the location of any site or vector
(as function on its attributes) or any point. To open it, select the icon in the
toolbar.
2.9.4 How to Be Automatically Placed in the Find Site Box
Use the F3 shortcut to be automatically placed in the Find site box of the Search bar.
2.9.5 How to Delete All Sites and Their Transmitters in One Shot
The right way to delete all sites and their transmitters is to open the Sites table, select
the first one and the last one holding the Shift button and use Suppr keyboard button.
2-57
It is recommended to close the Sites and Transmitters folders before deleting a large
number of sites and transmitters, otherwise the refresh of the explorer could take a
long time.
2.9.6 How to Access the Properties of Any Object or Group of Objects
In U-Net, the properties of any object (geo data, sites, transmitters, measurements,
etc...) can be accessed from the associated context menu. This is reachable by
right-clicking on the considered object/group and choosing the properties command.
2.9.7 How to Filter Data Rapidly
The easiest way is to perform directly filters within the tables (popup menu available by
right-clicking in the table). OR and AND criteria can be easily handled:
I. AND filtering criterion
Selecting cells in several columns and the option "Filtering by selection" in the popup
menu performs a AND filtering criterion
Example: keeping transmitters with azimuth 120° and pilot power equal to 33 dBm
II. OR filtering criterion
Selecting cells in several rows and the option "Filtering by selection" in the popup
menu performs a OR filtering criterion
Example: keeping transmitters with pilot power equal to 33 dBm or 35 dBm
To check which kind of dynamic criterion has been used by U-Net, you can open
Transmitters/Properties/General tab and look at the advanced filter.
2.9.8 How to Work Only on "Live" Sites
Let's assume there is a flag (user field) in Site table dedicated to the status of the site
("live", "on-built", "planned", and so on).
Filtering sites directly in the table with the popup menu ("Filtering by selection") allows
keeping just "live" sites.
Filters on site are automatically performed on transmitters ("As site folder" is the
default configuration for Transmitter folder). Further simulations or predictions will be
achieved only on "live" sites.
2.9.9 How to Use Wildcard Characters to Filter Text-format Fields
Wildcard characters such as “*” can be used when defining advanced filter criteria on
fields with text format.
2-58
Entering *string* enables you to filter objects which the chosen field contains the
string of characters.
Entering string* enables you filter objects which the chosen field begins with the
string of characters.
Example: How to display transmitters which are allocated a channel XX?
In the Transmitter table structure, there is a field "Channels" which contains a flat list of
the channels allocated to the transmitter. It is possible to define an advanced filter as
follows:
Use the Advanced filter tab of the Filter dialog (Transmitters / Properties / General /
Filter / Advanced filter):
z Columns: select "Channels" in the list
z Criteria: =* XX * (which means CONTAINS)
Only the transmitters with the channel XX are displayed.
Note:
The same filter can be managed at the level of any study by transmitter.
2.9.10 How to Change Globally the Names of All the Sites
There is a Find/Replace feature in the Edit menu available when a table is open. To
prefix all the sites with your name for example, select the first cell of the "name"
column in the Site table and use the Edit/Replace feature.
2.9.11 How to Find Easily an Object by Its Name in a Folder
Open the folder and type the first letters of the object name.
2.9.12 How to Open or Close Rapidly a Folder
z Shortcuts, available in standard Windows applications are available within U-Net

to open or close the selected folder with shortcuts.
z "Right arrow" and "Left arrow" respectively open and close the selected folder just
like "+" and "-" on the numeric keyboard.
z "*" on the numeric keyboard opens all the subfolders of the selected folder.
z [Alt F4] may be used to quit U-Net rapidly when no modifications were made. If
there are modifications, you will be asked to save them anyway.
2-59
2.9.13 How to Find Easily an Object in a Table
A Find feature is available in the Edit menu when a table is open. To find an object in a
table, open the table and use the Find feature.
2.9.14 How to Find Easily an Object on the Map
The “Centre Map or Locate on Map ” feature allows the user to find on the map any
object located into a folder (site, transmitter, etc...). When choosing this command in
the associated context menu, the considered object is automatically displayed in the
centre of the current workspace.
2.9.15 How to Customise the Columns Displayed in a Table
When a table is open, you may use the "Display columns..." feature available in the
Format menu to choose which columns you want to keep within the table. This is
useful to customise reports on transmitters or import Excel-format data by matching
columns on both sides and copying-pasting into the table.
2.9.16 How to Customise the Table Style
When a table is open, you may use features available in the Format menu in order to
customise the table style.
z To change the title style, choose the Format title feature.
z To modify the column style, select a column and use the Format columns feature.
You may also use the Align Left, Centre, Align Right, Bold and Italic features.
2.9.17 How to Change Globally Display Properties of Objects
In the Display tab, select the whole table describing the display configuration and click
on the Modify button. In the Display window, you can choose a unique symbol for all
the objects.
2.9.18 How to Predict Signal Level on a Road
The easiest way consists in using CW measurement features. Let’s assume you have
previously imported a vector file. The procedure is divided into three steps:
1) Right click on a linear object and select the Element properties command. In
the Geometry tab, copy the list of coordinates (Ctrl+C).
2) Right click on the CW Measurement folder and select the New command. Give
a name to the path, specify CW measurement unit, transmitter and receiver
properties and finally click on the Paste button. Then, click on OK to validate the
path creation.
2-60
3) Open the path properties window. Choose a propagation model, click on

Actions and choose Calculate predictions. The signal level calculated on the path
is displayed in a related table (P(dBm) column).
You may use the CW Measurement window to visualize the signal level received from
the selected transmitter on the path.
2.9.19 How to Work on a Set of Sites Selected by a Polygon
Let's assume polygons are available within U-Net. Right-clicking on the polygon, you
can use it as the computation or focus zone or as a filtering polygon. Sites,
transmitters and future calculations are filtered with this polygon.
You can save the polygon filter as a configuration of the Site folder, and repeat this
operation with as many polygons as you wish.
Then, directly right-clicking on the Site folder, you will get all the available
configurations for the folder and be able to rapidly switch from one to another.
Configurations are saved in the ATL file but possibly also in an external user
configuration file.
2.9.20 How to Obtain a Link Budget
Right-click anywhere in the Profile window to open a context menu. This menu allows
you to change receiver properties, gives the choice between signal level, pathloss or
total losses display, and offers a link budget.
If the propagation model used by the selected transmitter is a Standard Propagation
Model, there is an additional feature, useful for validation, called "Model details"
providing detailed results along the profile.
2.9.21 How to Display City Points and Their Names on the Map
With a vector format providing for each point an attribute containing the name (e.g.
"name").
Import the vector file within U-Net and choose the field "name" as label (you can use
any field or list of fields in the same way).
2.9.22 How to Display Scrambling Codes on the Map
Scrambling codes are managed at the cell level, e.g. for a given transmitter and a
given carrier.
Coverage can be displayed using a color code based on any cell property (scrambling
code, UL load, and so on) on condition that:
z A UMTS study is created with the choice of a single carrier
2-61
z The study Display tab is set with the required field (scrambling code, UL load, and
so on)
Note:
PN offsets can be displayed in the same way in CDMA/CDMA2000 projects
2.9.23 How to Define the Default Server for Distributed Computing
In the U-Net.ini file:

[RemoteCalculation]
Servers=Workstation_1;Workstation_2
If the list is empty, computations are run locally.
2-62
GENEX U-Net Wireless Network Planning Software Chapter 3 Managing Geographic Data
Chapter 3 Managing Geographic Data
3.1 Overview
U-Net manages several geographic data types: DTM (Digital Terrain Model), clutter
classes (land use), clutter heights (over the DTM), scanned images, vector data,
population data, generic data and supports several file formats in relation to data type.
The first step is to define geographic coordinate systems then import geographic data
(DTM, clutter classes and heights, scanned images, vector data, population data) using
an easy and fast procedure. Furthermore, U-Net allows you to create your own clutter
class (and traffic raster - in GSM/GPRS/EDGE, UMTS or CDMA/CDMA2000 projects)
maps thanks to the cartography editor. U-Net lists the imported DTM, clutter class and
height or traffic objects in their respective folder and creates a separate folder for each
imported vector data and scanned image.
Once theses folder are created (Traffic description is linked with radio data - depending
on the project type - even if present in the [Geo] tab of the U-Net environment), you may
manage them (display, data location managing, clutter class description...) easily. It is
also possible to display vector objects over coverages by importing/transferring these
objects directly in the Data tab.
U-Net also provides some features dealing with data priority like multi-layer
management and multi-resolution management.
Some edition tools for raster or vector objects are also available. Moreover, most of the
geo data objects can be exported in external files (DTM, clutter classes, clutter heights,
raster polygons, and vector layers). Finally, maps can be exported as an image in
external files, or in other applications.
3.2 Geo Data Type Supported

Several geographic data types:
z DTM (Digital Terrain Model)
z clutter classes (land use)
z clutter heights (over the DTM)
z scanned images
z vector data
z population data
z generic data maps
For all of these, different file formats are supported.
3-1
3.2.1 The DTM (Digital Terrain Model)
The DTM (Digital Terrain Model) files describe the ground elevation. The DTM
geographic data is a 16 bits/pixel relief map. U-Net is able to display this raster map in
different ways: single value, discrete values, values interval.
DTM/DEM is systematically taken into account in computation by propagation model.
Note:
In most documents, Digital elevation model (DEM) and digital terrain model (DTM) are
differentiated and do not have the same meaning. By definition, DEM refers to altitude
above sea level including both ground and clutter while DTM just corresponds to the
ground height above sea level.
3.2.2 Clutter Classes (or Land Use)
The clutter class files describe the land cover (dense urban, buildings, residential,
forest, open, villages....); the ground is represented by a grid map where each bin
corresponds to a code allocated to a main type of cover (a clutter class). According to
the classification, the clutter is either statistical if the number of clutter classes depends
on the housing density or determinist if the number of clutter classes depends on the
cover altitude.
The altitude per class can be defined in the clutter class property dialog. In that case,
only one altitude refers to each clutter class. It is also possible to use a clutter height
map (see below).
The clutter class maps are 8 bits/pixel (256 classes-raster maps). They define an image
with a color assigned to each clutter class (by default, grey shading).
Note:
Clutter heights are taken into account only using the Standard Propagation Model and
WLL model.
3.2.3 Clutter Heights
Clutter height maps are complementary to clutter classes, in a way that they can inform
more precisely on the clutter altitudes, since it is possible to have different heights for a
3-2
same class of clutter. Like in clutter classes, clutter heights indicate, on each bin, the
clutter altitude over the DTM.
When clutter altitude is defined both in clutter class and clutter height folders, the
information is taken in the second one. Clutter heights are taken first if they exist (in
measurements, computations, display).
The clutter height maps are 16 bits/pixel. They give one altitude per pixel and can be
managed like DTM/DEM maps. U-Net is able to display the clutter height map in
different ways: single value, discrete values, values interval.
Note:
Clutter heights are taken into account only using the Standard Propagation Model and
WLL model.
3.2.4 Vector Layers
This type of data represents either polygon (regions...), or lines (roads, coastlines...) or
points (important locations...). They are used in display only and have not any effect on
computations.
Polygons can be used for filtering purpose or for the creation of computation and focus
zones. Whatever their shape is, it is possible to create a vector layer by using the vector
editor.
Any formation/attribute contained in the vector can be used as a display parameter
(name, zip code, user profile, etc...)
Vectors can be used to generate CDMA/CDMA2000 or WCDMA/UMTS traffic maps
(see below).
Note:
Since vector maps (like scanned images) have no effect on computation, it is possible
to group all maps working like this within a unique display folder, and to make their
management easier.
3-3
3.2.5 Scanned Images
This type of data (1-24 bits/pixel) regroups the road maps and the satellite images.
Scanned images are only used for display (no effect on computations), and help the
user lo locate precisely objects in the real field.
Note:
Since scanned images (like vector maps) have no effect on computation, it is possible
to group all maps working like this within a unique display folder, and to make their
management easier.
3.2.6 Population Maps
Population maps are built using 8-32 bits/pixel files for which some density or value (in
number of inhabitants) information is given. It is possible to mix several types of files (8
or 16 bits raster, vectors,) in order to extract from them the needed information.
The interest of these maps is to use them in prediction reports with a view to display, for
example, the absolute and relative covered population.
Population maps have no effect on prediction and simulation results.
3.2.7 Generic Maps
The generic map feature has been developed in order to import any type of geo data in
term of any advanced map. For example, it is now possible to import any raster/vector
file and to use it as a revenue, rainfall or socio-demographics map.
Like for the population map, it is possible to mix several types of files (8 or 16 bits raster,
vectors...) in order to extract from them the needed information.
It is also potentially possible to use this information in prediction reports. For example,
in a revenue map, it is possible to display the revenue value for coverage.
Generic maps have no effect on prediction and simulation results.
3.2.8 The Traffic Data
According to the project type you start, U-Net proposes different kinds of traffic data.
In any project, you can import or create traffic 8 bits/pixel (256 classes-raster maps).
For each bin of the map, a code linked with a particular environment class is assigned
(density of user profiles with associated mobility) for UMTS, CDMA and CDMA2000
projects or a traffic density (Erlang/km2) in GSM/GPRS/EDGE projects. The raster
maps are macroscopic traffic estimation.
3-4
In the UMTS, CDMA/CDMA2000 projects, you can additionally use traffic vector maps
and traffic maps per transmitter and per service.
z Vector maps detail traffic estimations (lines or polygons may have a specific traffic).
Each polygon or line is related to a specific user profile with associated mobility
and density. They can be built from population density vector maps.
z When traffic is actual information on connections (and no longer subscriber
estimation), coming from the network and dealing with rates per transmitter and
service, it is possible to create and use traffic maps based on this network
feedback. They are built from coverage by transmitter prediction.
3.3 Length/Height/Offset Units and Coordinate Systems

3.3.1 Setting Default length/Height/Offset Units
In U-Net, it is possible to define a default length/height/offset units, like default radio

units, that will be used in some dialog box fields (not in tables).
For example:
z Lengths are used for calculation radius in transmitter and station template
properties or hexagon radius in station template properties, and when using the
Distance measurement button.

z Heights are used when reading the altitudes of sites, transmitters, DTM, etc...
z Offset units are used to define transmitter Dx and Dy from the related site location.
To define a default length/height/offset units in an already open project, proceed as
follows:
1) Click on the Tools menu from the toolbar.
2) Choose the Options... command from the open scrolling menu.
3) Click on the Units tab.
4) Choose in the scrolling list the default units for the current .atl U-Net project.
Note:
We can distinguish the display unit as described above from the internal unit. The
internal unit cannot be changed by the user. In any case (.atl project connected to a
database or not), the internal length unit is the “metre”. When environments are
connected to a database, display and internal unit systems are stored in the database:
z The internal unit is used as the length (height or offset) unit in the database.
z The display unit is memorized and taken into account when opening a project from
the database.
3-5
3.3.2 Basic Concepts
I. Concepts
A map or a geospatial database is a flat representation of data located on a curved

surface. A projection is a device for producing all or part of a round body on a flat sheet.
This projection cannot be done without distortion, thus the cartographer must choose
the characteristic (distance, direction, scale, area or shape) which is to be shown
appropriately at the expense of the other characteristics, or compromise on several
characteristics [1]. The projected zones are referenced using cartographic coordinates
(meter, yard...).
II. projection systems
Two projection systems are widely used:

z The Lambert Conformal-Conic projection: a portion of the earth is
mathematically projected on a cone conceptually secant at one or two standard
parallels. This projection type is useful for representing countries or regions that
have a predominant east-west expanse.
z The Universal Transverse Mercator projection (UTM): a portion of the earth is
mathematically projected on a cylinder tangent to a meridian (which is transverse
or crosswise to the equator). This projection type is useful for mapping large areas
that are oriented north-south.
III. geographic system
The geographic system is not a projection, but a representation of a location on the

earth's surface from geographic coordinates (degree-minute-second or grade) giving
the latitude and longitude in relation to the origin meridian (Paris for NTF system and
Greenwich for ED50 system). The locations in the geographic system can be converted
into other projections.
[1] Snyder, John. P., Map Projections Used by the US Geological Survey, 2nd Edition,
United States Government Printing Office, Washington, D.C., 313 pages, 1982.
IV. U-Net coordinate system references
U-Net integrates two databases including more than 980 international coordinate
system references, a database based on the European Petroleum Survey Group and
another one regrouping only France's coordinate systems.
U-Net distinguishes the cartographic coordinate systems for projection and either
cartographic or geographic coordinate systems for display.
The maps displayed in the workspace are referenced in a particular projection system
intrinsic to the imported geographic data files; thus, the projection system depends on
the imported geographic file. By choosing a specific display system, you may see
(using the rulers or status bars) the location of sites on the map in a coordinate system
3-6
different from the projection coordinate system. You may also position on the map sites
referenced in the display system: the coordinates are automatically converted in the
projection system and the site is displayed on the map.
In the example shown in Figure 3-1, the French Riviera geographic data file has been
imported. The map shows the French Riviera projected using the cartographic NTF
(Paris) / France II étendue system (coordinates in metres). On the other hand, site
coordinates are stated in the geographic WGS 72 system (coordinates in
degrees-minutes-seconds).
Figure 3-1 NTF System
Note:
If all the imported geographic files are referenced in the same projection system and if
you do not need to convert coordinates in another system; it is not necessary to define
projection and display systems. By default, the two systems are the same.
3.3.3 Defining the Projection Coordinate System
To define the projection coordinate system, proceed as follows:

1) Select in the [Tools/ Options...] command.
2) Click on the [Coordinates] tab from the open window.
3) Click on the browse button right to the [Projection] field.

4) Use the “What's this” help to get further description about the fields available in
the window.
3-7
5) Select a catalogue and choose a coordinate system in the related table.

Characteristics of the selected system are described by clicking the <Properties>
button.
6) Click <OK> to validate the projection system.
Note:
z You can add the selected coordinate system to a catalogue of favourite systems by
using the button.

z When exporting a U-Net project in a database, the currently chosen display
coordinate system becomes the internal one.
z Default systems cannot be modified.
3.3.4 Defining the Display Coordinate System
To define the display coordinate system, proceed as follows:

2) Click on the Coordinates tab from the open window.
3) Click on the browse button right to the Display field.

4) Use the What's this help to get further description about the fields available in the
window.
5) Select a catalogue and choose a coordinate system in the related table.
Characteristics of the selected system are described by clicking the Properties
button.
6) Click <OK> to validate the display system.
3-8
Note:
z If the display coordinate system is cartographic, X and Y respectively correspond to
abscissa and ordinate.
z If the display coordinate system is geographic, X and Y respectively refer to
longitude and latitude.
z Cartographic systems are identified by the symbol to the left of the systems,
whereas geographic ones are symbolized by .
z You can add the selected coordinate system to a catalogue of favourite systems by
using the button.

z Default systems cannot be modified.
3.3.5 Selecting Degrees Display Format
To facilitate the comprehension, use and functioning with other software tools, U-Net is
capable of displaying the longitudes and latitudes in four different formats. This is
helpful when exchanging data with other tools and enables U-Net to adapt itself to
different working environments.
Examples of the different longitude/latitude display methods available are shown in
Table 3-1:
Table 3-1 longitude/latitude display methods
Method Example
1 26°56’29.9’’N
2 26d56m29.9sN
3 26.93914N
4 +26.93914
To select the desired degrees display format, proceed as follows:

1) Click on the [Tools] menu.
2) Open the Options... window.
3) Select the degrees format from the dropdown menu on the Coordinates tab.
4) Click <OK> to accept.
3-9
Note:
Different degrees display formats are available only for the geographic coordinate
systems as there is no concept of longitudes and latitudes in the cartographic
coordinate systems.
3.3.6 Creating Your Own Coordinate System
I. Create a new coordinate system
U-Net provides a large catalogue of default coordinate systems. Nevertheless, it is

possible to add the description of geographic and cartographic coordinate systems.
The new coordinate system can be created from scratch or initialized on the basis of an
existing one.
To create a new coordinate system, proceed as follows:
2) Click on the Coordinates tab from the open window.
3) Click on the browse button right to the Projection or Display field.

4) Click on the New button, or select a catalogue and choose a coordinate system in
the related table, Click on the New button.
window.
6) Choose the catalogue where you want to store the new coordinate system.
II. Geographic coordinate system
z Geographic coordinate system (symbolised ) is a latitude and longitude

coordinate system.
z The latitude and longitude are related to an ellipsoid, a geodetic datum and a
prime meridian.
z The geodetic datum provides the position and orientation of the ellipsoid relative to
the earth.
III. cartographic coordinate system
A cartographic coordinate system (symbolised ) is obtained thanks to a

transformation method which converts a (latitude, longitude) into an (easting, northing).
To define a projection system, you must specify the geographic coordinate system
supplying longitude and latitude and the transformation method characterised by a set
of parameters.
3-10
Different methods may require different sets of parameters. For example, the
parameters required to define the projected Transverse Mercator coordinate system
are listed below:
z The longitude of the natural origin (Central meridian),
z The latitude of the natural origin,
z The False Easting value,
z The False Northing value,
z A scale factor at the natural origin (on the central meridian),
Procedure:
1) In the General part, type a name, choose a unit in the scrolling menu (to open it,
select the cell and left click on the arrow), and define the usage.
2) In the Category part, choose in the Type scrolling menu (to open it, select the cell
and left click on the arrow) either Long/Lat in order to create a geographic
coordinate system, or a type of projection and its set of associated parameters for
cartographic coordinate systems.
3) In the Geo part, specify the meridian and choose an existing datum in the Datum
scrolling menu (to open it, select the cell and left click on the arrow). The
associated ellipsoid is automatically selected. You can also describe a geodetic
datum by selecting ... in the Datum scrolling menu. In this case, you must provide
parameters (Dx, Dy, Dz, Rx, Ry, Rz and s) needed for the transformation of datum
into WGS84 and an ellipsoid.
4) Click <OK> to validate the display system.
Note:
z An identification code enables U-Net to differentiate the existing coordinate systems.
In case of new created coordinate systems, assigned codes are integer values
strictly higher than 32767.
z Management in the coordinate system folder is possible. Use the Technical guide
for the process description.
Caution:
For an easier management and to avoid any confusion, take care to give a unique
name to the created coordinate systems.
3-11
3.4 Geo Data Format Supported

3.4.1 Overview
U-Net offers import filters for the most commonly used geographic data formats. You
can use these filters to import DTM, clutter class, traffic, vector files or scanned images.
The different filters are shown in Table 3-2:
Table 3-2 File formats
File format Can contain Georeferenced

BIL DTM (16 bits), clutter heights Yes via .hdr files
(16 bits), clutter classes (8
bits), traffic (8 bits), image
(1-24 bits), population (8-32
bits), Generic (8-32 bits)
TIFF DTM, clutter height and Yes via associated .tfw

classes, traffic, Image, files if they exist
population, generic
PlaNET© DTM, clutter height and Yes via index files
classes, traffic, Image, text
and vector data
BMP DTM, clutter height and Yes after manually

classes, traffic, Image, entering northwest and
population, generic southwest point
coordinates of the image
DXF® Vector data, vector traffic, Yes
population, generic
SHP Vector data, Vector traffic, Yes
population, generic
MIF/MID Vector data, Vector traffic, Yes
population, generic
IST DTM, clutter height and Yes via .hdr files
classes, traffic, Image,
population, generic
Erdas Imagine DTM, clutter height and Yes automatically

classes, traffic, Image, embedded in the data file
population, generic
Thus, you can import:

z DTM files with TIFF (16 bit), BIL (16 bit), IST (16 bit), PlaNET©, BMP (16 bit) and
Erdas Imagine (16 bit) formats.
z Clutter heights with TIFF (16 bit), BIL (16 bit), IST (16 bit), PlaNET©, BMP (16 bit)
and Erdas Imagine (16 bit) formats.
3-12
z Clutter classes and traffic files with TIFF (8 bit), BIL (8 bit), IST (8 bit), BMP (8 bit),
PlaNET©, and Erdas Imagine (8 bit) formats.
z Vector data files with DXF®, PlaNET©, SHP and MIF formats.
z Vector traffic files with DXF®, PlaNET©, SHP and MIF formats.
z Scanned image files with TIFF (1-24 bit), BIL (1-24 bit), IST (1-24 bit), BMP (1-24
bit), PlaNET© and Erdas Imagine (1-24 bit) formats.
z Population with TIFF (16 bit), BIL (16 bit), IST (16 bit), PlaNET©, BMP (16 bit),
Erdas Imagine (16 bit), DXF®, SHP and MIF formats.
z Generic data with TIFF (16 bit), BIL (16 bit), IST (16 bit), PlaNET©, BMP (16 bit),
Erdas Imagine (16 bit), DXF®, SHP and MIF formats.
Note:
The use of compressed formats (tiff compressed or Erdas Imagine) on geo data (e.g.
DTM or Clutter) can lead to slow processes because of the decompression in real time.
To avoid this effect, it is strongly recommended:
z Either to inactive the status bar which provides geo data information in real time. To
do this, unpick the status bar option in the View menu.
z Or not to display some information such as altitude, clutter class and clutter height in
the status bar. To do this, add the syntax described below in an U-Net.ini file.
[StatusBar]
DisplayZ=0
It is also possible to save the produced map in a not compressed format.
3.4.2 BIL Data Format
Band Interleaved by Line is a method of organizing image data for multiband images. it
is a schema for storing the actual pixel values of an image in a file. The pixel data is
typically preceded by a file header that contains ancillary data about image, such as the
number of rows and columns in the image, a colourmap... BIL data stores pixel
information band by band for each line, or row, of the image. Although BIL is a data
organization schema, it is treated as an image format. An image description (number of
rows and columns, number of bands, number of bits per pixel, byte order...) has to be
provided to be able to display the BIL file. This information is included in the header
HDR file associated with the BIL file. A HDR file has the same name as the BIL file it
3-13
references, and should be located in the same directory as the source file. The HDR
structure is simple, it is an ASCII text file that contains eleven lines. You can open a
HDR file using any ASCII text editor. The parameters defined in .hdr files are detailed
below Table 3-3:
Table 3-3 Defined parameters
Acceptable
Keywords Default Description
values
number of rows in the
nrows any integer > 0 none
image
number of columns in
ncols any integer > 0 none
the image
number of spectral
nbands any integer > 0 none
bands in the image
number of bits per pixel

nbits* 1, 4, 8, 16, 32 8
per band
byte order in which

same as host
byteorder I = Intel image pixel values are
machine
stored
M = Motorola
organization of the
layout bil bil
bands in the image file
number of bytes of data
in the image file to be
skipbytes any integer > 0 0 skipped in order to reach
the start of the image
data
x-axis map coordinate of

ulxmap any real number 0 the centre of the
upper-left pixel
y-axis map coordinate of
any real number
ulymap nrows - 1 the centre of the
upper-left pixel
x dimension of a pixel in
xdim any real number 1
map units
y dimension of a pixel in
ydim any real number 1
map units
*The nbits value depends on the geographic data type. Indeed, nbits are respectively
16 (16 bits) for DTM and 8 (8 bits) for clutter or traffic.
Example: clutter.hdr file associated with clutter.bil file.
“nrows 1500
3-14
ncols 1500
nbands 1
nbits 8
byteorder M
layout bil
skipbytes 0
ulxmap 975000
ulymap 1891000
xdim 20.00
ydim 20.00”
3.4.3 TIFF Data Format
I. General
The Tagged Image File Format graphics filter supports all image types (monochrome,
grayscale, palette color, and RGB full color images) and pack bit or fax group 3-4
compressions. The TIFF files are not systematically georeferenced.
In this case, you will have to enter spatial references of the image manually during the
import procedure (x and y-axis map coordinates of the centre of the upper-left pixel,
pixel size); an associated file with TFW extension will be simultaneously created with
the same name and in the same directory as the TIFF file it references. U-Net will then
use the .tfw file during the import procedure for an automatic georeferencement.
TFW file contains the spatial reference data of an associated TIFF file. The TFW file
structure is simple; it is an ASCII text file that contains six lines. You can open a TFW
file using any ASCII text editor. The contents of a TFW file are described below Table
3-4.
Table 3-4 TFW File
Line Description
1 x dimension of a pixel in map units
2 amount of translation
3 amount of rotation
negative of the y dimension of a pixel in map
4
units
x-axis map coordinate of the centre of the

5
upper-left pixel
y-axis map coordinate of the centre of the

6
upper-left pixel
3-15
II. Example
clutter.tfw file associated with clutter.tif file.

100.00
0.00
0.00
-100.00
60000.00
2679900.00
It is possible to import a group of tiff images as geo data.
Note:
U-Net supports also TIFF files using the Packbit, FAX-CCITT3 and LZW compression
modes.
III. Operation
For customers working out the TIFF coverage prediction files exported by U-Net with
GIS tools, an option is available in order to modify the colour palette convention used by
U-Net.
In the default palette, the first colour indexes represent the useful information and the
remaining colour indexes represent the background.
It is possible to export a TIFF file with a palette containing at the colour index 0, the
background colour, and following, the colour indexes necessary to represent useful
information.
To set up the new palette convention, add these lines in the U-Net.ini file:
[TiffExport]
PaletteConvention=Gis
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
session and to restart it in order to take into account any modification performed in
U-Net.ini.
3-16
Note:
[StatusBar]
DisplayZ=0
z It is also possible to save the produced map in a not compressed format.
3.4.4 DXF Data Format
The Drawing Interchange Format (DXF) enables the interchange of drawings between
AutoCAD® and U-Net. DXF files can be either ASCII or binary formats, but only the first
type is used in U-Net.
Essentially a DXF file is composed of pairs of codes and associated values. The codes,
known as group codes, indicate the type of value that follows. Using these group code
and value pairs, a DXF file is organized into sections, which are composed of records,
which in turn are composed of a group code and a data item. Each group code and
value is on their own line in the DXF file.
Each section starts with a group code 0 followed by the string, SECTION. This is
followed by a group code 2 and a string indicating the name of the section (for example,
HEADER). Each section is composed of group codes and values that define its
elements. A section ends with a 0 followed by the string ENDSEC.
3.4.5 SHP Data Format
ESRI (Environmental Systems Research Institute, Inc.) Arcview® GIS (Geographic

Information System) Shapefiles are a simple, non-topological format for storing the
geometric location and attribute information of geographic features. A shape file is one
of the spatial data formats that you can work with in ArcExplorer. shp data file are
commonly associated with two other files with .shx and .dbf extensions.
3-17
A quick description of the 3 files is given below:

z shp - the file that stores the feature geometry.
z shx - the file that stores the index of the feature geometry.
z dbf - the dBASE file that stores the attribute information of features. When a
shapefile is added as a theme to a view, this file is displayed as a feature table.
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.
3.4.6 MIF Data Format
MIF (MapInfo Interchange Format) is a format allowing generic data to be attached to a

variety of graphical items. These ASCII files are editable, relatively easy to generate,
and work on all platforms supported by MapInfo. Vector objects may be imported in
U-Net with a MIF extension.
MapInfo data are contained in two files with .MIF and MID. extensions. Graphics reside
in a .MIF file and textual data is contained in a .MID file. The textual data is delimited
data, with one row per record and either Carriage Return, Carriage Return plus Line
Feed, or Line Feed between lines. The MIF file has two areas -- the file header area
and the data section. The MID file is an optional file. When there is no MID file, all fields
are blank.
More info: http://www.mapinfo.com/community/free/library/interchange_file.pdf
3.4.7 Erdas Imagine Data Format
U-Net is able to support Erdas Imagine data files in order to import DTM (16 bit/pixel),
clutter (8 bit/pixel), and traffic (8 bit /pixel) and image (1-24 bit/pixel) files with the .img
format. These files use the Erdas Imagine Hierarchical File Format (HFA) structure. For
any type of file, if there are pyramids (storage of different resolution layers), they are
used to enhance performance when decreasing the resolution of the display.
z U-Net supports uncompressed as well as compressed (or partially compressed)
DTM .img files,
z You can create a .mnu file to improve the clutter class map loading,
z The association colour-code (raster maps) may be automatically imported from
the .img file,
z These files are auto-georeferenced, i.e. they do not need any extra file for
georeferencement,
3-18
z For image files, the number of supported bands is either 1 (colour palette is
defined separately) or 3 (no colour palette but direct RGB information for each
pixel). In case of 3 bands, only 8 bit per pixel format is supported. Therefore, 8-bit
images, containing RGB information (three bands are provided: the first band is for
Blue, the second one is for Green and the third for Red), can be considered as 24
bit per pixel files. 32 bit per pixel files are not supported.
Note:
[StatusBar]
DisplayZ=0
It is also possible to save the produced map in a not compressed format.
3.4.8 Other Supported Formats
U-Net supports 3 other formats than the BIL, TIFF, PlaNET, DXF, SHP, MIF, and IMG
ones.
The .ist and .dis formats are ASCII files used for Digital Terrain Model only. Ist images
come from Istar, whereas dis images come from IGN (Institut Géographique National).
Ist format works exactly like bil format, except for DTM images, for which ist format
uses a decimetric coding for altitudes, whereas bil images uses only a metric coding.
The .bmp format is the standard Windows image format on DOS and
Windows-compatible computers. The bmp format supports RGB, colour-indexed,
greyscale, and bitmap colour modes, and does not support alpha channels.
3-19
3.5 Managing Clutter Classes

3.5.1 Importing a Clutter Class File
Considering the appropriate format, clutter class type files can be imported as follows:
1) Select the [File/ Import] command from the menu bar.
2) Specify the path, the name and the format (optional) of the related file in the
open dialog box.
3) Press <OK> to validate.
4) Select the [Clutter classes] option in the Data type scrolling box.
5) Click the <Import> button to complete the file import.
The imported clutter class files are listed in their appropriate folder in the [Geo] tab
and can be managed easily (description, modification, visibility, layer order
management, etc...). Geographic data are displayed in the workspace.
Note:
z The drag and drop feature is available from any file explorer application to U-Net.
z .geo or .cfg (user configuration files) can be used (import-export) to share paths of
the imported clutter class file paths between users.
z Imported files can be embedded during the import or afterwards.
3.5.2 Optimizing the Loading of Clutter Class Files
The loading performance of clutter classes (and raster traffic) with .bil, .tif and .img
formats are highly improved when U-Net does not have to find by itself the list of the
classes contained in the file. To benefit from this optimization, the user must create a
text file named as the clutter classes (or GSM/GPRS/EDGE, UMTS or
CDMA/CDMA2000 raster traffic maps) file with .mnu extension, at the same location.
This MNU file gives the correspondence between the code and the class name. This
optimization is already included in the PlaNET® format thanks to the menu file.
To do so, check the validity of an associated .mnu file in the map folder before
achieving the import geo data procedure.
Practical advice: U-Net can be used to easily create the MNU file. Just import the
clutter classes (or traffic) file (slow loading) in U-Net and paste the class description
([Description] tab in the Properties window) in a text file.
3-20
3.5.3 Description of MNU Files
I. General
MNU file is useful when importing clutter class or raster traffic files with .tif, .bil
and .img formats. It gives the correspondence between the clutter (or traffic) code and
the class name. It is a text file named as the clutter class (or traffic) files with .mnu
extension, which must be stored at the same location .
MNU file is shown in following Table 3-5.
Table 3-5 MNU Files
Field Type Description

Identification code for the
Class code Integer > 0
clutter (or traffic) class
String (up to 32 characters in Name of the clutter (or
Class name
length) traffic) class
Separator is either a blank or a tab.
II. Sample
Mnu file associated to a clutter file.

z 0 none
z 1 open
z 2 sea
z 3 inland_water
z 4 residential
z 5 meanurban
3.5.4 Managing the Clutter Classes
Clutter classes represent the land cover of a network. They can be used by propagation
models in three ways:
z Some of them use their "nature" to associate adapted formulas (Okumura-Hata,
Cost-Hata).
z Others use these clutter classes to associate some specific parameters such as
specific losses or clearances (Standard Propagation model, WLL).
z The definition of clutter heights (either in clutter classes or clutter heights) to
compute diffraction both over the DTM and the clutter (Standard Propagation
model, WLL).
3-21
It is also possible to define, per clutter class, a model standard deviation (in order to
compute shadowing margins) and orthogonality factor (for CDMA/CDMA2000 and
WCDMA/UMTS projects).
To manage the clutter classes properties, proceed as follows:
1) Click the [Geo] tab in the Explorer window.
2) Right click on the clutter classes folder to open the associated context menu, Left
click in the scrolling menu on Properties, or double click the clutter classes folder.
different tabs.
4) Click on the [Description] tab from the open window.
5) Assign name and average height (m) to each code.
6) Optionally enter, for each clutter class, a model standard deviation per clutter
class (in dB) that will be used to calculate the shadowing margins.
7) For CDMA/CDMA2000 and WCDMA/UMTS projects only, an orthogonality
factor per clutter class (Orthogonality factor can be modeled by a value between
0 and 1. A 0 value indicates no orthogonality at all, instead a 1 value in the case of
perfect orthogonality at mobiles).
8) Click on the Default Values tab.
9) Set (or not) the default model standard deviation. This value is used if no clutter
map is available in the .atl document of if no model standard deviation is specified.
10) Select (or not) the option "Use default values only" in order to force U-Net to use
default values specified in this tab instead of the values defined per clutter class.
11) Click on the [Display] tab to manage the appearance of the map.
12) Press <OK> to validate the settings.
The Clutter classes map uses the generic U-Net display dialog and its standard tools:
z Display types: Discrete or Value intervals
z Shading command on value intervals
z Legend management
z Visibility scale
z Transparency level management
Other common features related to either a geo data folder (Save as, Centre the map on
the object) or an imported geo data file (Embedding the file in the project afterwards)
can be accessed from their related context menu.
Like in other geo data folders, you can also work on the layer order. This will have an
effect on the computations taking into account that “What is seen is what is used”.
Layers to be considered will have to be located on the top of the other layers.
3-22
Note:
z The description table can be fully copied and pasted (using Ctrl+C and Ctrl+V) in a
new U-Net project after importing the clutter file. To select globally the clutter class
table, just left click on the top left angle of the clutter table.
z If the height column is not filled in, the models using this information (WLL model for
example) will consider a zero clutter height.
z The heights defined in the clutter classes are taken into account only if the Clutter
height folder is not filled.
z The white colour is associated with the transparent colour. Thus, the geographic
layer below the clutter class map will be visible in the area where the transparent
colour is assigned.
z Before importing the clutter file, it is important to define a reference class
corresponding to zero code, white colour and no data. Thus, the code "0" is
allocated to areas without clutter.
z The class names cannot exceed a length of 50 characters.
z Clutter classes description (and clutter file path) is part of the contents of
exported .geo or .cfg files.
z It is possible to define a default model standard deviation value. You may force
U-Net to use this value even if a clutter class map with model standard deviation per
available in your .atl document or if no model standard deviation value per clutter
class is specified.
z In CDMA/CDMA2000 and WCDMA/UMTS projects, the default orthogonality factor
(transmitter global parameters) is taken into account only if the related values in the
clutter class properties are not filled.
z New clutter classes can be created manually.
The button updates the resulting clutter class map by deleting all unused
classes.
Advice: Use this function to keep consistency between the clutter classes described in
the table and in the imported file.
Example: U-Net automatically memorizes the different clutter classes of imported file.
Even after deleting the file, the clutter classes are stored in the description table.
Pressing the button will remove them.
See importing a geographic data file.
3-23
3.5.5 Adding a Clutter Class
To add a clutter class to the current geo environment, proceed as follows:

2) Right click on the Clutter classes folder to open the associated context menu,
Left click in the scrolling menu on Properties, Or Double click on the Clutter
classes folder.
3) Click the [Description] tab.
window.
5) Describe each new clutter class in the appropriate cells of the bottom line.
6) Press <OK> or <Apply> to validate.
The added clutter class is then available to be used to create new clutter class
polygons using the clutter editor.
3.5.6 Displaying Statistics on Clutter Classes
To display the relative occupancy of each clutter type in the current project
computation zone (or focus zone if existing), proceed as follows:
2) Right click on the Clutter classes folder to open the associated context menu.
3) Choose the Statistics option from the scrolling menu.
4) The surface (Si in km²) of each clutter class (i) included in the computation zone
(or focus zone if existing) and its percentage (% of i) are specified:
Si
% of i = × 100
∑ Sk
k .
Note:
z Since the statistic study is limited to the computation zone (or focus zone if existing),
only the clutter area inside the computation zone is taken into account,
z Current statistical results are printable by clicking the button,

z Data contained in the statistics window can be copied by selecting them (Ctrl+A)
then copying them to the clipboard (Ctrl+C).
3-24
3.6 Managing Clutter Heights

3.6.1 Importing a Clutter Height File
Considering the appropriate format, clutter height type files can be imported as
follows:
1) Select the Import command in the File menu from the menu bar.
open dialog box.
4) Select the Clutter heights option in the Data type scrolling box.
The imported clutter class files are listed in their appropriate folder in the [Geo] tab
and can be managed easily (properties, visibility, layer order management, etc...).
Geographic data are displayed in the workspace.
Note:
the imported clutter height file paths between users.
3.6.2 Managing Clutter Height Maps
In U-Net, there are two places to define clutter heights. This can be done either via the
clutter classes maps properties (in this case, clutter height is an average value
associated to a clutter class) or via clutter height files (this type of file provides a clutter
height value on each point of the map).
Therefore, clutter height file(s) are supposed to be more accurate since it is possible to
have several heights per clutter class. For display, calculations using propagation
models and determination of clutter height along CW measurement and test mobile
data paths, U-Net takes clutter height information in clutter heights file if available in
the .atl document. Else, it considers average clutter height specified for each clutter
class in the clutter classes file description.
Clutter height maps can be managed in the same way as the DTM map. To access the
properties of the resulting clutter height map, proceed as follows:
3-25
2) Right click on the clutter heights folder to open the associated context menu, Left
click in the scrolling menu on Properties, Or Double click the clutter heights folder.
different tabs.
4) Click the [Display] tab to manage the appearance of the map.
5) Press <OK> to validate the settings.
The Clutter height map uses the generic U-Net display dialog and its standard tools:
z Display types: Discrete or Value intervals
z Shading command on value intervals
z Legend management
z Visibility scale
Other common features related to either a geo data folder (Save as, Centre the
map on the object) or an imported geo data file (Embedding the file in the project
afterwards) can be accessed from their related context menu.
Like in other geo data folders, you can also work on the layer order. This will have
an effect on the computations taking into account that “What is seen is what is
used”. Layers to be considered will have to be located on the top of the other
layers.
Note:
z If available in the Clutter heights folder, this information is displayed in the status bar
relatively to the location of the pointer.
z Clutter height properties (and clutter height path) is part of the contents of
3.7 Managing DTM Maps

3.7.1 Importing a DTM Map
Considering the appropriate format, Digital Terrain Model (or DEM) files can be
imported as follows:
open dialog box.
4) Select the Altitude (DTM) option in the Data type scrolling box.
3-26
The imported DTM files are listed in their appropriate folder in the [Geo] tab and can be
managed easily (properties, visibility, layer order management, etc...). Geographic data
are displayed in the workspace.
Note:
the imported DTM file paths between users.
3.7.2 Managing DTM Maps
The Digital Terrain Model is a geographic data file representing ground surface
elevation. DTM maps can be managed in the same way than the Clutter height map.
To manage the DTM display, proceed as follows:
2) Right click on the DTM folder to open the associated context menu, Left click in
the scrolling menu on Properties, Or Double click the DTM folder.
3) Click on the [Display] tab from the open window.
window.
5) Set the display parameters of the current DTM.
6) Click <OK> to validate.
The DTM display uses the generic U-Net display dialog and lets you choose, in the
display type scrolling menu:
z single: same representation for any bin
z discrete values: bin representation according to the value of a discrete field (sea
level) describing the DTM object.
z values interval: bin representation according to the value of a numerical field
(altitude) describing the DTM object.
Whatever the display type you have chosen, you can customize the graphical
representation of bins. In the table, for each line, click on each row.
You can manage the contour line visualisation by using the relief slider.
3-27
Note:
Other common features related to either a geo data folder (Save as, Centre the map on
the object) or an imported geo data file (Embedding the file in the project afterwards)
can be accessed from their related context menu.
Like in other geo data folders, you can also work on the layer order. This will have an
effect on the computations taking into account that “What is seen is what is used”.
Layers to be considered will have to be located on the top of the other layers.
Path and description are stored in the external user configuration file.
3.8 Managing Vector Maps

3.8.1 Importing a Vector File
In U-Net, it is possible to create (using the vector editor) or to import vectors as geo
data. In that case, vectors are only used for display purposes, and polygons can be
taken as filters, computation or focus zones. Vector files can also be used for
CDMA/CDMA2000 or WCDMA/UMTS traffic maps, population or any generic map.
In addition, it is possible to group any geo data type under a single folder that will be
used for display purposes only.
The vector import process does not use the same dialog as the other geo data (clutter
classes and heights, DTM, images)
Considering the appropriate format, vector files can be imported as follows:
open dialog box.
4) In the Vector Import dialog, select the Geo or Data option in the ‘Import to’
scrolling list.
5) Select the appropriate coordinate system (if needed).
The imported vector files are automatically listed at the explorer root level in the Geo (or
Data) tab and can be managed easily (properties, visibility, layer order management,
etc...). Geographic data are displayed in the workspace.
3-28
Note:
z The drag and drop feature is available from any file explorer application to U-Net,
z Under U-Net, shp filenames are not limited in the number of characters when
exporting or importing, even if the file name is made up of more than 8 characters.
imported file paths between users.
z Contrary to other data types, it is possible to choose a geographic coordinate
system at the import.
z Vectors can be shifted from one tab to another afterwards for display
considerations.
3.8.2 Managing Vector Objects
Vector geographic objects contain additional characteristics. Their number and their
type depend on the file format. Indeed, when dealing with .dxf or PlaNET® files, a
single attribute, the height, is available unlike .mif or .shp files which can include
several attributes (name, length, height...). Thus, third dimension vector data can be
read and additional information relating to vectors can be used as a display parameter.
To manage the vector objects display, proceed as follows:
1) Click the tab (Data or Geo) in which the vector layer is currently located in the
Explorer window.
2) Right click on the vector folder to open the associated context menu, Left click
in the scrolling menu on Properties, Or Double click the vector folder.
different tabs.
4) Click on the [Display] tab.
5) Set the vector display parameters.
3-29
Note:
z You may manage the display of each vector individually. To do so, after having
expanded the vector folder, choose the properties option from the considered vector
context menu (left click), then set the display parameters. Use the What's this help
to get description of the fields available in the open window.
z Path and description are stored in the external user configuration file.
z Attributes used in the vector display can be modified thanks to the vector edition
features.
z Vectors can be shifted from one tab to another afterwards for display
considerations.
3.8.3 Displaying Vector Layers over Predictions
It is possible to put vector layers either in the Data tab so as to display them on the top
of coverage studies or in the [Geo] tab to keep them in the background, thanks to layer
order.
To do so, when importing a vector file, you may select Data tab as the import
destination in the Vector import dialog.
In addition, a Transfer command (either in Geo, or in Data) is available in each vector
layer context menu (right click on vector layer to open context menu); it enables you to
switch vector layers from Geo to Data tabs or vice versa.
3.9 Managing Scanned Images

3.9.1 Importing Scanned Images
Considering the appropriate format, scanned image files can be imported as follows:
open dialog box.
4) Select the Image or scan option in the Data type scrolling box.
The imported scanned image files are automatically listed at the explorer root level in
the [Geo] tab and can be managed easily (properties, visibility, layer order
management, etc...). Geographic data are displayed in the workspace.
3-30
Note:
the imported scanned image file paths between users.
It is possible to import scanned image files by groups by using an index file. Once
the procedure performed, U-Net creates a folder per imported index file.
The import procedure is the same as for the other geo data images (Import command
from the File menu). When obtaining the classic Open dialog box, select the All
supported file or PlaNET® geo data (index) format and locate the appropriate file.
When clicking the Open button, a dialog box opens in which you must indicate the
image data type.
Note:
The drag and drop tool is available to import such a group of Tiff/Bmp files.
Its format is:

One line per Tiff/Bmp file: Relative name of tiff/bmp file with regard to the index file path
XMIN XMAX YMIN YMAX 0 (the separator is a blank)
Where:
z XMAX = XMIN + (number of horizontal bins x bin width)
z YMAX = YMIN + (number of vertical bins x bin height)
Example of a two images index file located in the folder C:\TEMP. These two files are
located in the same directory.
nice1.tif 984660 995380 1860900 1872280 0
nice2.tif 996240 1004900 1860980 1870700 0
3.9.2 Managing Scanned Images
Scanned images are geographic data files which represent the real field (road maps,
satellite images) and which are used in order to precisely locate surrounding items or
other less precise maps (like statistical raster maps for example).
To manage the display of any scanned image, proceed as follows:
3-31
2) Right click on the scanned image folder to open the associated context menu, Left
click in the scrolling menu on Properties, Or Double click the scanned image
folder.
different tabs.
4) Click on the [Display] tab.
5) Set the scanned image display parameters.
Note:
Path and description are stored in the external user configuration file.
3.10 Managing Population Maps

3.10.1 Importing a Population Map
It is possible to use population maps, in terms of density or value information. Several

forms of files can be mixed in order to compose a resulting population map. This type of
map, like other geo data folders (clutter, DTM) works on the principle “What is seen is
what is used”. Data retained in the folder will be used in clutter statistics and prediction
reports.
Several file formats (raster or vector) are supported in order to make their content
available for population data.
Depending on the file type (vector or raster), the way to import a file as a population
map component can be different.
To import a population map, proceed as follows
In the File menu, select the Import command,
I. Vector format (Mif, shp)”;
1) In the Vector Import dialog, select the Population item in the ‘Import to’ scrolling
list.
2) Select the appropriate coordinate system (if needed).
3) Associate a numeric field/attribute of the vector to the U-Net internal field that
will be used. Proceed as following Figure 3-2 and Figure 3-3:
3-32
Figure 3-2 Population density (number of inhabitants/km²)
Figure 3-3 Population values (number of inhabitants per item – polygon/road, etc...)
II. Raster/Morpho format
1) In the File menu, select the Import command.

2) In the File Import dialog, select the Population density data type.
3) Click the <Import> button.
U-Net fills the Population folder of the [Geo] tab with the imported files. Some tabs are
added to the Population property dialog:
z Correspondence tab to manage vector items
z Description and Table tabs to manage raster items
In addition, the [Display] tab is available for any data type item and uses the generic
U-Net display dialog.
Note:
z Population values can only be imported with vector files.
z The drag and drop feature is possible to import such a type of map.
the imported population file paths between users.
z It is possible to create a population vector map using the vector edition tool. To do
this, right click on the Population folder and select the ‘Add vector layer’ command.
3.10.2 Managing Population Maps
To access the properties of the resulting population map, proceed as follows

1) In the [Geo] tab, right click the Population folder.
3-33
2) Choose the Properties command in the context menu.

3) Depending on the imported file type, different tabs are available (see above):
z Description: all identified classes of the raster files are listed here. You can
associate here a different population density for each class.
z Table: this tab is dedicated to manage the contents of the class table contained in
the [Description] tab.
z Correspondence: an imported vector file is listed in each line. In the column
‘Field’, the vector field which has to be chosen as population data has to be
selected, always with the density check box (when the relevant data is of type
density). The current selection is the one made during the import. The association
can be modified afterwards.
z Display: U-Net generic display dialog with the possibility to tune the threshold
shading. The displayed information is the number of inhabitants/km².
Note:
z The resulting population map is not the addition of all the maps, but the result of
what is seen. Maps of interest have to be put on the top layer. For raster maps, the
‘no data’ class makes the population information operational which is below the
zones of this type.
z The display by value is not permitted is the following cases:
different raster maps with different resolutions
vectors mixing lines and polygons
mix of raster and vector maps
z The display by density is not permitted on vectors made of points.
3.10.3 Displaying Statistics on Population
It is possible to display the relative and absolute distributions of people depending on

the thresholds defined in the [Display] tab of the Population folder property dialog. To do
this, select the Statistics command from the Population folder context menu. Like other
statistics windows, what is used for the results is provided by what is seen.
Note:
Statistics are provided on the focus zone if it exists. Otherwise, the computation zone is
considered. With neither of them, statistics are given for the total geographic zone.
3-34
3.10.4 Using Population Data in Prediction Reports
In prediction reports, it is possible to make displayed columns related to covered

population densities (as defined in the [Display] tab of the Population folder property
dialog), the number of covered people, and the percentage of covered population.
To display information about the covered population by a prediction, proceed as
follows:
1) Right click on the Prediction of interest.
2) Select the Generate Report command from the context menu.
3) In the [Format: Display columns] menu, check the boxes related to the
information you want to display with the prediction report.
Note:
Reports are possible only on displayed studies or sub-items of the studies (transmitters,
thresholds, etc...).
3.11 Managing Generic Maps

3.11.1 Overview
This feature has been developed in order to import any type of geo data in term of any
advanced map. For example, it is possible to import any raster/vector file and to use it
as a revenue, rainfall or socio-demographics map.
Several forms of files can be mixed in order to compose a resulting generic map. This
type of map, like other geo data folders (clutter, DTM) works on the principle “What is
seen is what is used”. Data retained in the folder will be potentially used in prediction
reports.
Several file formats (raster or vector) are supported in order to make their contents
available for generic maps
All types of coding may be mixed in any generic geo data folder: vector files, raster files
(8, 16, 32 bits per pixel). Vector layers can be created using the vector edition tool.
The imported data can then be interpreted in order to produce resulting maps of type:
z Morpho file: map of value classes (like clutter) (8 bits – integer [0...255])
z Raster file: map of value densities (16 bits with scaling factor – integer [0....65535]
or float simple precision, 32 bits – [0....16777216] or float double precision)
The creation of a new map type is made during the import of a geo data file that will be
part of the resulting map. Then, once created, and depending on the supported formats,
it will be possible to import/add other data files in order to complete the new map.
3-35
Depending on the file type (vector or raster) that will be used for the initialization of the
new map, the way to import it can be slightly different.
3.11.2 Create an Advanced Geo Data Folder
The creation of a generic map is made via the import of a geo data file.
I. Vector format (Mif, shp)

2) In the Vector Import dialog, select the ‘Advanced...’ button,
II. Raster/Morpho format:
1) In the File Import dialog, select the ‘Advanced...’ button,

2) The definition of the new map type is made in the current window (New type),
3) Enter the name of the new map (e.g. Revenue)
4) Check the boxes related to the formats that you want this map to be able to
support (Vector, Raster 8, 16 and 32 bits),
5) Indicate the type of map you want to be produced by interpreting the file data
(See above)
z Morpho file: map of value classes (like clutter) (8 bits – integer [0...255])
z Raster file: map of value densities (16 bits with scaling factor – integer [0....65535]
or float simple precision, 32 bits – [0....16777216] or float double precision).
6) Check the ‘Integrable’ box if you want the relevant data (contained in the files
composing the resulting map) to be potentially used in prediction reports. This
data (of type surface density only) will be integrated on each considered item
(threshold, transmitter) in predictions to provide statistics.
7) Click <OK> to validate the creation of the advanced geo data map,
III. Vector format (Mif, shp):
1) Select the appropriate coordinate system (if needed),

2) In the Vector Import dialog, associate a numeric field/attribute of the vector to
the U-Net internal field that will be used as a:
z Value density (number of items/km²)
z Absolute values (number of items per polygon/road, etc...)
IV. Raster/Morpho format:
1) Select to use the content as a value or as a density. Density is not consistent with
a data which is not integrable.
A new geo data folder is created, filled with the imported file(s). Some tabs are added to
the property dialog:
3-36
z Correspondence tab to manage vector items,

z Description and Table tabs to manage raster items.
In addition, the [Display] tab is available for any data type item.
Once the folder is created, it is possible to easily import any other supported file as a
part of the generic map. This is done as a standard geo data import by selecting the
appropriate target map in the import dialog.
Note:
z Value maps can be imported using vector files.
z The drag and drop feature is possible to import such kinds of maps.
the imported population file paths between users.
z It is possible to add a vector map to an existing generic map using the vector edition
tool. To do this, right click on the related folder and select the ‘Add vector layer’
command.
Important: 8 bits maps are only code maps. So, when importing any geo data type file
as a 8 bits map, bear in mind that the values that you are importing are codes and not
values like densities, for example. The values related to each pixel will be defined for
each code, each pixel referring to a code.
3.11.3 Managing Generic Maps
To access the properties of the resulting generic map, proceed as follows:

1) In the [Geo] tab, right click the folder of the considered generic map.
2) Choose the Properties command in the context menu.
3) Depending on the imported file type, different tabs are available (see above):
z Description: all identified classes of the raster files are listed here. You must
associate here a different value density for each class.
z Table: this tab is dedicated to manage the contents of the class table contained in
the [Description] tab.
z Correspondence: an imported vector file is listed in each line. In the column
‘Field’, the vector field which has to be chosen as relevant data has to be selected,
always with the density check box (when the relevant data is of type density). The
current selection is the one made during the import. The association can be
modified afterwards.
z Display: U-Net generic display dialog with the possibility to tune the threshold
shading. Both discrete value and value interval display types are available.
3-37
Note:
The resulting population map is not the addition of all the maps, but the result of what is
seen. Maps of interest have to be put on the top layer. For raster maps, the ‘no data’
class makes the population information operational which is below the zones of this
type.
The Integrable/not Integrable aspect is chosen at the creation and cannot be changed
afterwards.
The display by value is not permitted are the following cases:
z different raster maps with different resolutions
z vectors mixing lines and polygons
z mix of raster and vector maps
z The display by density is not permitted on vectors made of points.
3.11.4 Displaying Statistics on Generic Data
It is possible to display the relative and absolute distributions of each item class (class
defined by thresholds in the [Display] tab of the Generic geo data folder property dialog).
To do this, select the Statistics command from the appropriate folder context menu.
Like other statistics windows, what is used for the results is provided by what is seen.
Note:
Statistics are provided on the focus zone if it exists. Otherwise, the computation zone is
considered. With neither of them, statistics are given for the total geographic zone.
3.11.5 Using Generic Map Data in Prediction Reports
In prediction reports, it is possible to make displayed columns related to data contained

in any generic map. This can be made for any data, and is even more advanced when
the relevant data is of type ‘Integrable’.
To display information about the covered classes of any generic data by a
prediction, proceed as follows:
1) Right click on the Prediction of interest.
2) Select the Generate Report command from the context menu.
3) In the [Format: Display columns] menu, check the boxes related to the
information you want to display with the prediction report.
3-38
Note:
Reports are possible only on displayed studies or sub-items of the studies (transmitters,
thresholds, etc...).
Integrable/Not Integrable, Density/Value: examples

Integrable data will be used in prediction reports so they can be summed over the cells
characterised by the item of interest (transmitter, threshold, etc...). They can be of type
value (Revenue, number of customers ...) or density (Revenue/km², number of
customer/km² ...).
For example, in the case of the revenue map, a prediction report will indicate:
z The percentage on how is covered each revenue class, globally, and for each
single coverage cell (transmitter, threshold, ...).
z The revenue of the global coverage and of each single coverage cell.
z The percentage of the covered revenue map, globally, and for each single
coverage cell.
Non Integrable data means that they are an information for each pixel (or polygon e.g.)
which cannot be integrated over a coverage cell, like socio-demographic classes, rain
zones, etc....
In that case, considering the example of a rain zone map, a prediction report would
indicate:
z The relative coverage of each rain zone class, by the global study, and for each
single coverage cell (transmitter, threshold, ...).
Being non Integrable, no other information is given.
3.12 Managing Geo Data Files and Folders

3.12.1 Embedding - Linking Comparison
U-Net offers the user the possibility to link or embed any imported geo data file. The
main differences between linked and embedded objects are the location where data
are stored and how the imported data are updated after placing them in the U-Net
document.
When you import geographic data without selecting the embed in document option,
U-Net just memorizes the location where the source files are stored (directory path)
and creates a link to source files: the objects are linked. If you modify the source file,
information will be automatically taken into account in the document .atl. On the other
hand, some applications as deleting or moving the source file in another directory
involve the link break. In this case, U-Net offers you solutions to repair it.
3-39
The embedded geographic files are totally included in the document .atl, they become a
part of the document: There is no longer a link between the document .atl and the
source files. Therefore, the U-Net document is not updated if you modify the source file.
Practical advice: Prefer the linked objects in order to limit the U-Net document size.
Note:
The distributed calculations do not work in case of embedded geographic data.
3.12.2 Embedding Geographic Data
You may embed DTM, clutter class or height, traffic, vector, population, generic and
scanned image objects you have imported in your U-Net document. This can be done
either when importing the geo data, or from the properties of an available object.
To embed geographic data in the current .atl project during the import procedure, just
check the 'Embed in document' box in the object import dialog box.
To embed geographic data in the current .atl project from an existing data item,
proceed as follows:
2) For a raster, clutter height or DTM file: Expand the related folder by left clicking
on the button, Right click on the file you want to embed in the current project,
Left click in the scrolling menu on Properties, Or Double click the file you want
to embed in the current project.
3) For a scanned map or a vector file: Right click on the scanned map/vector file
you want to embed in the current project, Left click in the scrolling menu on
Properties, Or Double click the scanned map/vector file you want to embed in
the current project.
4) Click on the General tab from the open window.
5) Click the button from the open window.

6) Click <OK> or <Apply> to validate.
3.12.3 Repairing a Broken Link
It may happen that some source files (.atl or geo data files) have moved since the last
time the current project was open. In this case, U-Net cannot find them automatically
and will display the following error message (See Figure 3-4):
3-40
Figure 3-4 Missing Shortcut
I. Method 1:
Click the button if you want to locate the geo data file by yourself. At the same time,
U-Net automatically searches for the file with the nearest match based on size, date
and type. When it has found it, it displays the error message shown in Figure 3-5.
Figure 3-5 Problem with Shortcut
If the file corresponds to the source file, press <OK>.
II. Method 2:
If the localization is not successful, you have to link again the geo data file to the
project by yourself from the geo item properties. To do so, proceed as follows:
2) For a clutter class, traffic or DTM file: Expand the Clutter classes, traffic raster or
DTM folder by left clicking on the button, Right click on the Clutter classes, traffic
raster or DTM file you want to fix the link problem, Left click in the scrolling menu
on Properties, Or Double click the Clutter classes, traffic raster or DTM file
you want to fix the link problem.
3) For a scanned map or a vector file: Right click on the scanned map/vector file
you want to fix the link problem, Left click in the scrolling menu on Properties, Or
Double click the scanned map/vector file you want to fix the link problem.
4) Click on the General tab from the open window.
5) Click the button from the open window.

6) Locate the appropriate data file.
3-41
3.12.4 Grouping Geo Data Files in Display Folder
In the standard case, when importing geo data files dedicated only to display (1-24 bits
images, vectors), they are listed at the root of the [Geo] tab only (or possibly in the Data
tab for vectors), contrary to other data files, like clutter ones, for example, which are
listed all together and within a single ‘Clutter class’ folder. Listed all together, files can
be displayed/hidden or moved.
In U-Net, you can also, within a single additional folder, import different types of geo
data files and use them for display only. This folder does not produce a map, like it is the
case for the generic import of geo data files in order to produce, for example, revenue
or socio-demographics maps. This folder (which can be called geo display folder) just
groups geo data files and cannot be managed globally. The management (display only)
of each single item is made at the item level.
It is possible to import several file formats (raster or vector) in a single folder to make
them available for display only. All types of files may be mixed in a geo display folder:
vector or raster files (8, 16, 32 bits per pixel). Their information is used only for display,
i.e. that any raster file will be interpreted as an image (and also set as an image).
The creation of a geo display folder is made during the import of a first geo data file that
will be located in it. Then, once created, it will be possible to import other files within this
folder.
I. Vector format (Mif, shp)
1) In the File menu, select the Import command,

2) In the Vector Import dialog, select the ‘New folder in Geo – or Data’ item in the
‘Import to’ scrolling list.
3) Select the appropriate coordinate system (if needed),).
4) Give a name for the newly created folder.
II. Raster/Morpho format

2) In the File Import dialog, select the ‘New folder in Geo – or Data’ item in the
‘Data type’ scrolling list,.
3) Give a name for the newly created folder,.
A new geo data folder is created, filled with the imported file(s). Once the folder is
created, it is easily possible to import any other geo data file as a member of the
created folder. This is made as a standard geo data import by selecting the appropriate
target item in the import dialog.
3-42
Note:
z The drag and drop feature is possible to import such a type of map.
z Since it is possible to create the geo display folder either in the Geo or in the Data
tab, it is as easy to transfer it from one to another. To do this, right click on the
considered folder and select the ‘Transfer to Data/Geo’
z It is possible to import Packbit, FAX-CCITT3 and LZW compressed TIFF files.
3.12.5 Checking the Map Geocoding
You can check the file map geocoding (coordinates of north-west point, pixel size and
additional coordinates of south east point for .bmp files).
To check the geocoding of any data object (see above), proceed as follows:
I. For a clutter class, population, generic, traffic or DTM file
1) Click the [Geo] tab in the Explorer window,

2) Expand the folder by left clicking on the button.
3) Right click on the file whose geocoding you want to check, Left click in the
scrolling menu on Properties, Or Double click the file you want to check its
geocoding.
4) Click on the Geocoding tab from the open window,
5) Check or modify the extreme northwest and southeast points,
II. For a scanned map
1) Click the [Geo] tab in the Explorer window,

2) Right click on the file whose geocoding you want to check, Left click in the
scrolling menu on Properties, Or Double click the file you want to check its
geocoding,
3) Click on the Geocoding tab from the open window,
4) Check or modify the extreme northwest and southeast points,
3.12.6 Setting Geo Data Priority
U-Net lists the imported DTM, clutter class or traffic objects in their respective folder
and creates a separate folder for each imported vector data and each imported
scanned image. Each object corresponds to a layer with a specific size. Thus, there are
as many layers as imported objects. The layers are on top of each other in the order of
listed objects.
3-43
I. At the display level
Only the layer on top and the layers beneath area where there is no data will be visible
in the workspace.
In the example below, vector data (including highways, coastline, riverlake, majorroads,
majorstreets, railways and airport), clutter classes, DTM and scanned image have been
imported and a UMTS environment traffic map has been edited inside the computation
zone. In the workspace, we can see the linear objects (roads, riverlake,...) inside and
beyond the computation zone and the traffic layer (green colour) inside the computation
zone. The clutter class layer is visible in the area where no traffic data has been edited
(outside the computation zone).
On the other hand, the DTM layer which is underneath the clutter class layer and the
scanned map which is underneath the DTM layer are not visible, which is shown in
Figure 3-6.
Figure 3-6 U-Net Geo-Data
To make a layer visible in the workspace, either uncheck the check box of the other
layers (see object visibility), move the layer on the top of the list, or adjust the
transparency level of objects (clutter class, traffic and scanned image) when available.
To move an object in the [Geo] tab, proceed as follows:
1) Click and hold on the layer you want to move.
2) Drag the layer in the list.
3) Release the layer.
II. At the calculation level
DTM, Clutter classes, clutter heights, and Traffic density folders can contain several
objects representing different areas of the map or common parts of the map with
identical or different resolutions. U-Net takes into account in calculations, for each
3-44
folder, only the data it sees (that is to say the object on top and the objects beneath area
where there is no data). What is used is what is seen. Thus, for each folder, you must
locate on top the objects with the smallest size and the best resolution.
Note:
Population and generic data maps work in the same way. Their data can be used in
prediction reports.
3.13 Editing Geographic Data

3.13.1 Raster Objects
I. Creating a clutter or traffic raster polygon
A cartography editor is available either to modify imported clutter class (or traffic raster)
map or to produce your own clutter (or traffic) raster maps without initial clutter (or traffic)
object. In the same way, it is easy to delete clutter or raster traffic polygons. All created
polygons can be easily saved in external files. These modifications are taken into
account in calculations by propagation models.
To display the editor tool bar, proceed as follows:
2) Right click the Clutter classes folder (or environment traffic object) to open
the associated context menu.
3) Select the Edit command from the available scrolling menu.
4) The clutter (or traffic) editor window opens.
The editor tool bar consists of a selection box to choose the clutter (or traffic) class you
want to edit, a polygon drawing tool , a polygon deletion tool and a close save
button (See Figure 3-7).
Figure 3-7 Clutter edition
3-45
Note:
The clutter (or traffic) class you want to edit must be previously defined in the
[Description] tab of Clutter classes properties (or in the environment folder in
GSM/GPRS/EDGE, UMTS or CDMA/CDMA2000) dialog box.
Like for the computation and focus zones, you can copy and paste exact coordinates
(consistent with the defined display coordinate system) of a closed polygon. To do this,
select the properties command from the context menu (right click) related to the
selected polygon.
II. Editing clutter or traffic raster polygons
To edit clutter or traffic (raster map) polygons, proceed as follows:

2) Use either the clutter editor to add clutter data or traffic editor to produce traffic
data.
3) Select the clutter (or traffic - raster map) class you want to edit from the
selection box.
Note:
To make clutter (or traffic) classes available in the selection box, these have to be
previously defined:
z In the [Description] tab of the Clutter classes properties for the clutter editor.
z In the Environment subfolder of the GSM/GPRS/EDGE, UMTS or
CDMA/CDMA2000 parameters folder.
4) Select the polygonal drawing tool.

5) Position the pointer on the map area where you want to edit your own data.
6) Press the mouse left button (a first point is created).
7) Slide the pointer on the map and press the mouse left button to create another
point.
8) Carry out the two last steps until you draw the polygonal area you want.
9) Double click to close off the polygonal area.
10) Press the close button.
The created polygon is displayed with the same colour as the edited clutter class (or
traffic class). As long as the cartography editor is open, the polygonal area is delimited
by a thin black line rewiring the created points.
3-46
Note:
The clutter or traffic layer must be visible (see multi-layer management in Setting geo
data priority) if you want the modifications to appear on the map.
III. Modifying clutter or traffic raster polygons
To resize clutter or traffic polygons (raster map), proceed as follows:

2) Leave the cartography editor open.
3) Left click on the black line (limits of the polygonal area). The pointer becomes
the position indicator ( ).
4) Press and hold the mouse left button.
5) Drag the pointer in the area where you want to locate the point.
7) Press the close button to validate.
To add a point, proceed as follows:
4) Right click to open the associated context menu.
5) Select the Insert point command from the open scrolling menu.
To delete a point, proceed as follows:
3) Left click on the point you want to delete. The pointer becomes the position
indicator ( ).
5) Select the Delete point command from the open scrolling menu.
IV. Deleting clutter or traffic raster polygons
To delete clutter or traffic (raster map) polygons, proceed as follows:

the position indicator ( ), Right click to open the associated context menu,
3-47
Select the Delete polygon command from the open scrolling menu, Or Select the
Polygon deletion tool, Click on the polygonal area you want to delete.
4) Press the Close button to validate.
V. Displaying information about raster polygons
By using the tips button , U-Net allows the user to read information about any
polygonal area.
To know the surface and the type of edited data, proceed as follows:
Hold the pointer on the polygonal area until the associated information (code, name,
etc...) appears. The surface is given only in the case of closed polygonal areas.
Note:
z Information will appear only if the tips button is on.
To display the coordinates or points composing a polygonal area, proceed as follows:

3) Select the Properties command from the open scrolling menu,
The coordinates (in the display system) of the point composing the polygon are then
displayed in a table window.
Note:
Like for the focus or computation zone, the Copy-Paste feature is available in the
polygon coordinates table.
3.13.2 Vector Objects
I. Creating a vector layer
A toolbar enables you to edit new vector layers and modify the imported ones. This bar
can be open or closed by selecting the Vector edition command in the View menu.
It is possible to create new vector layers containing polygons, lines and points.
3-48
To create a new vector layer, proceed as follows:
1) Click on the New vector layer icon .
U-Net creates a folder called Vectors in explorer, either in the [Geo] tab, or in the Data
tab. In fact, the folder location depends on the open tab of explorer. So, the folder will be
placed in the [Geo] tab if this one is displayed when creating the new layer.
2) The new vector layer is listed in the Vector layer scrolling menu
Any vector object can be easily edited and modified. It is also very easy to define and
modify its fields.
Note:
Since vectors can be used to produce GSM/GPRS/EDGE, CDMA/CDMA2000 or
WCDMA/UMTS traffic maps, it is possible to create a vector layer during the creation of
the traffic map itself following the same procedure.
II. Editing a vector object
Once the vector layer is created, it can be easily edited and managed.
To edit vector objects of the layer, procedure as follows Table 3-6.
3-49
Table 3-6 Editing a vector object
Object procedure
1) In the Vector edition bar, click on the arrow to open
the Vector layer scrolling menu.
2) Select the layer to be edited in the list, Or In the
Explorer, right click on the vector layer to be edited in
order to get the context menu, Select the Edit command
from the open scrolling list, Click on the New polygon
icon to create polygons, or on the New line icon
to create lines, or on the New point icon to create
points.
For polygons or lines
3) Position the pointer on the map.
4) Press the mouse left button to create the first point of
polygon or line.
5) Move the pointer on the map and press the mouse
left button to create another point.
6) Carry out the two last steps until you draw the
polygonal area or the line you want.
7) Double click to close off polygonal area or to stop the
line drawing.
1) In the Vector edition bar, click on the arrow to open

the Vector layer scrolling menu.
2) Select the layer to be edited in the list, Or In the
Explorer, right click on the vector layer to be edited in
order to get the context menu, Select the Edit command
from the open scrolling list, Click on the New polygon
For points
icon to create polygons, or on the New line icon
to create lines, or on the New point icon to create
points.
3) Position the pointer on the map.
4) Press the mouse left button to create a point.
To clear the current icon selection, press the Esc button on your keyboard or click on
the selected icon.
Note:
The vector edition can be made on any vector, even working as a CDMA/CDMA2000,
WCDMA/UMTS traffic, population or generic map. The procedure is identical to the one
above.
3-50
III. Managing vector object shapes
Some tools available in the Vector edition bar enable you to modify the polygon shape
of a vector layer.
Indeed, it is possible:
z To merge several polygons thanks to the Combine icon
z To make a hole in a polygon by using the Erase icon

z To keep only the overlapping area of two polygons thanks to the Intersection icon
z To cut a polygon in two or more by using the Split icon
The vector layer must be in edition mode in order to be able to modify the shape of its
polygons.
To put a vector layer in edition mode, proceed as follows:
1) In the Vector edition bar, click on the arrow to open the Vector layer scrolling
menu, Select the layer to be edited in the list.
2) Or In the Explorer, right click on the vector layer to be edited in order to get the
context menu, Select the Edit command from the open scrolling list.
To combine several polygons, proceed as follows:
3) Choose the vector layer to be edited.
4) On the map, select a polygon.
5) In the Vector edition bar, click the Combine icon .
6) Draw one or several polygons on the map.

U-Net considers all the polygons as a group of polygons. If there is overlapping areas
between some polygons, U-Net merges them to make a single one.
z To clear the current icon selection, press the Esc button on your keyboard or
click on the selected icon.
z To erase areas within polygons, proceed as follows:
2) On the map, select a polygon or a group of polygons.
3) In the Vector edition bar, click the Erase icon .

U-Net removes all the overlapping areas between polygons.
3-51
z To keep intersection areas between polygons, proceed as follows:

3) In the Vector edition bar, click the Intersection icon .

U-Net only keeps the intersection areas between polygons and erases all the areas
outside.
z To split polygons, proceed as follows:
7) In the Vector edition bar, click the Split icon .

U-Net uses each polygon side intersecting the existing polygon(s) to cut them.
To clear the current icon selection, press the Esc button on your keyboard or click on
the selected icon.
Additional management features are available when right clicking on any vector object
on the map (polygons, lines or points).
When a vector layer is in Edition mode, you may select in the vector object context
menu:
z Delete: To remove vector objects on the map.
z Convert to line: To convert a polygon into a closed line.
z Convert to polygon: To convert a closed line into a polygon.
z Open line: To open a closed line; U-Net removes segment between the last and
the first point.
z Close line: To close line; U-Net adds a segment between the last and the first
point of the line.
z Insert point: To add a point into the polygon contour or line; the point is created at
the pointer location.
z Move: To shift vector objects on the map (place the pointer where you want to
locate vector object and left click to release it).
z Quit edition: In order for a vector layer to no longer be editable.
z Properties: To access the vector object property dialog. The General tab sums up
the vector layer name, the vector object identification number and vector object
attributes. The Geometry tab lists coordinates of points composing the selected
vector object. Coordinates are stated in the coordinate system specified in the
vector layer property dialog (General tab).
3-52
IV. Managing vector object properties
Vectors properties can be managed in two ways, either from a table containing all
vectors and their attributes or from the related standard property dialog. The procedure
is described following Table 3-7.
Table 3-7 Vectors properties management
Procedure
All the vectors (polygons, lines, points and groups of polygons) of a
vector layer and their attributes are listed in the corresponding
table. To open this table, proceed as follows:
1) Click the tab (Data or Geo) where the vector layer is currently
located in the Explorer window.
2) Right click on the vector folder to open the associated context
Vector table
menu.
3) Left click in the scrolling menu on Open.
Standard features for managing table contents (Copy/Paste, Fill
up/down, Delete, Display columns, Filter, Sort, Fields...) are
available in a context menu (when right clicking on column(s) or
record(s)) and in the Format, Edit and Records menus.
As a classical property dialog in U-Net, the vector layer property

dialog consists of a General tab, a Table tab and a [Display] tab.
To open the property dialog related to a vector object, proceed as
follows:
1) Click the tab (Data or Geo) where the vector layer is currently
Property located in the Explorer window.
dialog
2) Right click on the vector folder to open the associated context
menu.
3) Left click in the scrolling menu on the Properties command.
4) Use the What's this help to get description about the fields
available in the different tabs.
In the General tab, U-Net indicates:

z The vector layer name.
z If the vector layer is embedded in the .atl document or just linked. In this case,
U-Net displays the directory path used to access the file.
The Embed button can be used to embed the vector layer in the .atl document when
this one is just linked.
The Find button enables you to redefine a new path when the file's location has
changed.
z The coordinate system of the vector layer.
3-53
When the vector layer is linked, the coordinate system used is the one of the file
(system specified when importing the file). It corresponds to the projection coordinate
system when the vector layer is embedded.
The coordinate system can be changed (click on the Convert button to change it). In
this case, coordinates of points composing vector objects of the layer will be converted
in the selected coordinate system.
In addition, you can define, in this tab, sort and filter criteria that will be applied to vector
objects of the layer contained in the table.
The Table tab enables you to manage the vector layer table content. Therefore, you
may add custom fields in the table in order to describe vector attributes.
The [Display] tab enables you to manage the vector layer display; it is possible to
display vectors with colour depending on any attribute.
3.14 Managing Geographic Data Export

3.14.1 Exporting a Clutter Class Map
Like for DTM, clutter height and traffic raster maps, it is possible to export the current
clutter class description in either a tiff, a bil or a bmp format. You may choose to keep
the squared part of the current clutter class map that contains the defined computation
zone.
To export a part or the complete clutter class map, proceed as follows:
2) Right click on the Clutter classes folder to open the associated context menu,
3) Left click on the Save as... option from the open scrolling menu.
4) Define the format, the directory path and the name to give to the file to be
exported.
5) Click the Save button when done.
6) In the Export dialog box, select one of the options and define the resolution (in
metres) of the file:
z The whole covered region option allows you to save the whole clutter class map in
another file. As soon as the file is saved, the properties (name,...) of the clutters
listed in the Clutter classes folder are updated.
z The computation zone option allows you to save the clutter region inside the
computation zone in another file. As soon as the file is saved, an additional clutter
object is created and listed in the Clutter classes folder. To enable this option, you
must have drawn a computation zone beforehand.
z A resolution value is suggested; it is defined for clutter from the following criteria:
z If one clutter object is clipped, the displayed resolution will be the object resolution.
z If several objects are extracted, the suggested resolution will be the smallest
resolution of the objects.
3-54
z The resolution value must be an integer.

z The minimum resolution is set to 1 metre.
Note:
z 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.
z Clutter classes file path (and clutter description) is part of the contents of
3.14.2 Saving the Edited Raster Polygons
Saving the edited polygons consists either in creating a new clutter class (or traffic -
raster map) file including your modifications, or in storing your modifications in the
existing clutter class (or traffic) files.
I. To store modifications in a new file, proceed as follows:

2) Right click on the Clutter classes folder (or Traffic raster object) to open the
3) Select the Save as command from the open scrolling menu.
4) Indicate the path, the name and the format( *.tif, *.bil and *.bmp) for the file to be
exported.
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. Saving a file with the
BMP format doesn't involve the automatic creation of georeferencement file. Thus, it is
advised to associate with .bmp files a text document including the same information as
the .hdr or .tfw files.
6) Select one of the options and define the resolution (in metres) of file in the open
Export dialog box.
3-55
dialog box (See Figure 3-8).
Figure 3-8 Export region
z The whole covered region option allows you to save in the file the whole clutter
class map (or traffic map) including the clutter class (or traffic) modifications made
by the user. As soon as the modifications are saved, the properties of the clutter
(or traffic) object listed in the Clutter classes (or Traffic) folder are updated.
z The only pending changes option allows you just to save in the file the created
clutter class (or traffic) polygonal area. As soon as the modifications are saved, an
additional clutter class (or traffic) object is created and listed in the Clutter classes
(or Traffic) folder.
z The computation zone option allows you to save in the file the rectangular clutter
region (or traffic region) containing the computation zone encompassing the clutter
class (or traffic) modifications made by the user. As soon as the modifications are
saved, an additional clutter class (or traffic) object is created and listed in the
Clutter classes (or Traffic) folder.
z A resolution value is suggested; it is defined for clutter from the following criteria:
z If one clutter object is modified, the displayed resolution will be the object
resolution.
z If several objects are modified, the suggested resolution will be the smallest
resolution of the altered clutter class objects.
z If there is no initial clutter class object, 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.
z If you draw your own clutter data without initial DTM, clutter class or traffic object, a
100 m default resolution will be suggested.
z For any raster object, the resolution value must be an integer.
The same criteria are used to define the resolution of traffic objects: firstly, U-Net looks
for resolution in the modified traffic objects, secondly in the clutter class objects if there
3-56
is no imported traffic objects, then in DTM objects in case neither traffic nor clutter class
data is available and finally give the 100 m default resolution if there is no traffic, no
clutter class and no DTM data.
Caution:
Once the modifications are saved, the polygon dimensions are fixed and cannot be
modified.
II. To store modifications in an existing file, proceed as follows:

2) Right click on the Clutter classes folder (or Traffic folder - raster map) to open
the associated context menu
3) Select the Save command from the open scrolling menu.
4) A message is displayed warning the user that some current clutter class (or traffic)
files will be updated.
Note:
The existing file is made of a fixed size matrix. Hence, changes made outside this
matrix will not be taken into account.
3.14.3 Exporting a Clutter Height Map
Like for DTM, clutter class and traffic raster maps, it is possible to export the current
clutter height map in either a tif or a bil format. You may choose to keep the squared
part of the current clutter height map that contains the defined computation zone.
To export a part or the complete clutter height map, proceed as follows:
2) Right click on the Clutter height folder to open the associated context menu,
exported.
3-57
The whole covered region option allows you to save the whole clutter height map in
another file. As soon as the file is saved, the properties (name,...) of clutter height
object listed in the Clutter height folder are updated.
The computation zone option allows you to save the clutter height region inside the
computation zone in another file. As soon as the file is saved, an additional clutter
height object is created and listed in the Clutter height folder. To enable this option,
you must have drawn a computation zone beforehand.
A resolution value is suggested; it is defined for clutter height from the following criteria:
z If one clutter height object is clipped, the displayed resolution will be the object
resolution.
Note:
z Clutter height file path is part of the contents of exported .geo or .cfg files.
3.14.4 Exporting a DTM Map
Like for clutter class, clutter height and traffic raster maps, it is possible to export the
current DTM map in either a tif or a bil format. You may choose to keep the squared part
of the current DTM that contains the defined computation zone.
To export a part or the complete DTM map, proceed as follows:
2) Right click on the DTM folder to open the associated context menu.
exported.
3-58
The whole covered region option allows you to save the whole DTM map in another file.
As soon as the file is saved, the properties (name,...) of DTM object listed in the DTM
folder are updated.
The computation zone option allows you to save the DTM region inside the
computation zone in another file. As soon as the file is saved, an additional DTM object
is created and listed in the DTM folder. To enable this option, you must have drawn a
computation zone beforehand.
A resolution value is suggested; it is defined for DTM from the following criteria:
z If one DTM object is clipped, the displayed resolution will be the object resolution.
Note:
z DTM file path is part of the contents of exported .geo or .cfg files.
3.14.5 Exporting a Vector Object
You can save any edited vector layer in a vector format file. In this case, the vector layer
is no longer embedded in the .atl document; it is a linked file. It can be embedded
afterwards.
To export a vector layer, proceed as follows:
1) Click the tab (Data or Geo) where the vector layer is currently located in the
Explorer window.
2) Right click on the Vector layer to be exported in order to open the associated
context menu.
3) Select the Save as command from the open scrolling menu.
4) Indicate the path, the name and the format for the file to be exported. Possible
formats are Arcview (.shp), MapInfo (.mif) and an U-Net internal format (.agd).
3-59
Note:
z Only polygons can be saved in the Arcview (.shp) format. Therefore, a vector layer
mixing polygons and lines, polygons and points, or containing just points or lines
can only be saved in MapInfo (.mif) or U-Net internal format (.agd).
z The U-Net internal format (.agd) is a new format only supported by U-Net. Reading
of .agd files is faster than other vector files with classical supported formats
(MapInfo, Arcview, and AutoCAD).
In addition, in case of a linked file, it is possible to save modifications performed on the

vector layer.
To save modifications on a vector layer, proceed as follows:
1) Click the tab (Data or Geo) where the vector layer is currently located in the
Explorer window,
2) Right click on the Vector layer to be saved in order to open the associated
context menu,
3) Select the Save command from the open scrolling menu, U-Net displays a
warning to inform you that the source file will be modified,
4) Click <OK> to update the source file.
Note:
The Save command is available only if there are some pending changes on the vector
layer.
3-60
GENEX U-Net Wireless Network Planning Software Chapter 4 Managing Radio Network Data
Chapter 4 Managing Radio Network Data
4.1 Managing Radio Network Data Overview

As a reference radio planning tool, U-Net is able to work on several technologies. This
feature indicates that there may be a large amount of data in any project. Nevertheless,
U-Net has been developed in order to maximize the number of common features for
any type of project, either dealing with geo data management or radio data
management. Of course, several specific items dealing with the management of radio
data are introduced depending on the considered technology (e.g. TRXs and Subcells
in GSM/GPRS/EDGE, Cell level in UMTS or CDMA/CDMA2000 projects, etc...).
All the organisation tools (filters, sorts, groups, etc...) described in the user interface
basics can be applied on the radio data, working in the explorer, tables or on the map.
That way, working on sites, antennas, transmitters (including multi-sectored stations
and multi-antennas transmitters) and repeaters always remains easy. Moreover, it is
also possible to easily define, and in the same way in any technology, radio equipment,
that will be assigned to each transmitter of any network.
Specific parts dealing with radio data on GSM/GPRS/EDGE, WCDMA/UMTS and
CDMA/CDMA2000 will be seen next. Optimizations on networks will also be described
on specific parts dealing with each of these project templates.
4.2 Setting Default Radio Units

To build your network, like the projection or display coordinate systems or default
length unit used in any U-Net project, you must define reception and transmission
units as they have to be taken into account in the working environment.
U-Net allows you to define the units of measurement for transmission and reception of
signal levels, in your working environment. The options for units are as follows:
z Signal transmission units: dBmilliwatts (dBm), Watts or kiloWatts;
z Signal reception units: dBmilliwatts (dBm), dBmicroVolts (dBµV) or
dBmicroVolts/meter (dBµV/m).
To define reception and transmission units in the current project, proceed as
follows:
1) From the menu bar, select the options... command in the Tools menu.
2) Left click on the Units tab from the open window.
3) Use the What's this help to get description about the fields available and the
way to use them.
4-1
4) Choose in the scrolling lists the default reception/transmission units for the
current .atl U-Net project.
The default unit length can be defined in the same dialog box.
4.3 Sites
4.3.1 Site Properties
I. Creating a site
In U-Net, a site is a geographical point where one or several transmitters (multi-sector

site or station) equipped with antennas with particular characteristics are located.
Proceed as follows to create a site:
2) Right click on the Sites folder to open the context menu.
3) Left click the New command from the open scrolling menu.
4) Use the What's this help to get description about the fields available in the new
site dialog window.
Note:
z If the new site seems to not appear on the map, expand the Site folder by left
clicking on the associated button. Right click on the site you want to see in order
to open a menu from which you select the centre map option.
z Site is automatically created when dropping a base station on the map.
From the Display tab window, you can display sites with colours depending on their
attributes. The attributes of the sites can be displayed as labels in the workspace or in
help popups using the tip tool.
In UMTS and CDMA/CDMA2000 projects, in addition to the geographic information,
the definition of site equipment and their use has to be tuned.
II. Naming automatically sites
U-Net integrates, by default, a prefix to site names: "Site". In addition to this prefix, a
number is added and is incremented automatically. Nevertheless, you can force U-Net
not to use this default prefix and to prefer user-defined prefixes. You can customise it
by adding the syntax described below in a U-Net.ini file. You must create this file and
place it in the U-Net installation directory.
4-2
The syntax in order to define a new prefix to site names in the U-Net.ini file is the
following:
[Site]
Prefix=”newprefix”
Each new site will be named “newprefixN” instead of “SiteN”.
Note:
z 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.
z Naming automatically transmitters is also possible, either from a fixed prefix or
based on the site name.
z When changing the name of a site, U-Net automatically renames transmitters and
cells related to the site which names contain the site name. In the same way, if you
rename a transmitter, the corresponding cells are automatically renamed. The
automatic renaming according to site name is by default available. However, it may
be blocked if you add the following lines in the U-Net.ini file.
[AutoRename]
Transmitters = 0
3GCells = 0
Transmitters refer to transmitter renaming when the site name is changed.
3GCells refers to cell renaming when the transmitter name is changed.
III. Managing site properties
Like for all objects organised in folders (Sites, transmitters, Antennas, Predictions,
Simulations, measurements, etc...) within U-Net, sites can be managed either
individually or globally. Global setting is applied to all the filtered sites.
IV. Global properties management
In U-Net, you may manage globally the properties associated with existing sites of
your network:
1) Left click on the Data tab of the Explorer window.
2) Right click on the Sites folder.
3) Choose the Properties option from the context menu.
4) Use the What's this help to get description about the open dialog window.
4-3
The displayed window contains 3 tabs (General, Table, and Display). The General tab
allows you to use the advanced filter/sort/group by features. The Table tab manages
the contents of the Site table. The Display tab is designed to assign colours, labels and
tips to sites. An additional Other Properties tab is possible if some user defined fields
are added to the Site table.
V. Individual property management
There are two ways to edit properties of each existing site in the current network.
To do so,
1) Left click on the Data tab of the Explorer window, Expand the Sites folder by
clicking on the button in front of it, and Right click on the site you want to
manage.
2) Or Select on the map the site you want to manage by right clicking on it ( ).

The displayed window contains at least 2 tabs (General and Display). An additional
Other Properties tab is possible if some user-defined fields are added to the Site table.
In UMTS or CDMA/CDMA2000 projects, an additional tab dealing with Site equipment
is available.
Managing site properties is also possible from the Site table.
VI. Changing a site position
U-Net permits easy management of the site positions. You can proceed in two ways,
either by using geographic coordinates, by integrating the field topology, or by moving
sites manually (using the mouse).
A context menu is associated with each created site. This can be obtained identically
by right clicking on the site on the map or in the Sites folder from the Explorer window.
VII. Using the geographic coordinates

1) Double click on the site (on the map, or in the Sites folder from the Explorer
window) you want to move, in order to obtain the site properties window. You
can do the same by selecting the Properties option from the context menu
associated with this site (see above).
2) Choose the General tab.
3) Use the What's this help to get description about the open dialog window
4) Give the site coordinates (X, Y) in the display system you have chosen. The
position of the site by default (just at the creation) corresponds to the centre of
your active map.
4-4
Note:
In the General tab of the site properties window, you can also change the name of the
site, add comments for each site, and lock its position on the map. Locking the site
position allows "safety" for manual movements (using the mouse) for sites on the map.
When you move the site, a message will ask you to confirm your action.
VIII. Moving sites to a high point
When creating a network, it may be very useful to get sites high enough to propagate
signals easily. U-Net enables you to put sites on the highest point (based on the DTM)
around a site on a certain range.
1) Activate the site context menu (see above).
2) Select the Move to a high point... option.
3) Display the radius of highest point test around the current site.
Note:
U-Net can use either the DTM or a user-defined height for sites in computations.
IX. Moving sites using the mouse
You can move sites manually on the map, by selecting (left click) one and then by
dragging it on the map, left button pressed, wherever you want. A moving
confirmation is asked if the site has a locked position (see above).
X. Managing site altitudes
U-Net computes automatically the altitude from the imported DTM map. Nevertheless,
it is possible to define "real" altitudes that will be the ones taken into account for
computations. It is possible to have both altitudes per site, one altitude read from the
DTM map (non editable value) and another one that the user may define in the Real
box. Only the real altitude defined by the user is stored in database (Sites table).
To manually define a site altitude, proceed as follows:
clicking on the button in front of it. Right click on the site you want to manage
the altitude.
4-5
2) or Select on the map the site whose altitude you want to manage by left clicking
on it ( ).

4) Click the General tab of the open dialog.
6) Enter the real altitude in the appropriate field.
7) Click OK or Apply to validate your choice.
Note:
z In the Sites table, U-Net displays the real altitude of the site if defined or the DTM
altitude in brackets in case the site has no real altitude.
z In calculations, U-Net takes into account the site's real altitudes and the DTM value
in case it does not find any real altitude. You may force U-Net to consider only site
altitudes determined from the DTM map by selecting the Compute with the DTM
altitudes option in the Properties window (General tab) of the site folder. In this
case, U-Net ignores the entered real altitudes.
z Altitude is global height compared with sea level (Sea is 0 altitude) and depends on
the data of the imported DTM file (which could be DEM, i.e. including clutter height)
XI. Getting distances around sites
The radial grid is a graduated grid on the map around the site, with site text colour.
This grid enables the user to have better distances around site visualisation. You can
set its parameters by using the button.

clicking on the button in front of it, Right click on the site you want to get
distances around.
2) Or Select on the map the site you want to get distances around by left clicking
on it ( ).

4) Click the Display tab of the open dialog.
6) Left click the button to open the site grid parameter setting dialog
box.
4-6
7) Set the maximum radius, the distance between each graduation and the
deviation between angular graduations.
Note:
You can access directly to the grid parameters from the Grid option from the site
context menu. Clicking ok is equal to checking the Show radial grid box.
Example is shown in Table 4-1 and Figure 4-1.
Table 4-1 Distance example
Maximum radius of grid 5,000 m
Concentric distance between graduations 500 m
Distance between angular graduations 30°
Figure 4-1 Grid display with above parameters
XII. Displaying terrain section around sites
Thanks to the button , you may study the terrain section around a site.
To display the terrain section around a site, proceed as follows:

2) Left click on the Height profile button from the toolbar.
3) On the map, left click once on the site you want to study. U-Net creates a point.
4) Move the pointer anywhere around the site.
4-7
U-Net automatically opens the Point analysis window and dynamically displays
the height and clutter profile between the site and the pointer in the Terrain
sections tab, which replaces the Profile tab.
5) Left click on the map to put a second point. U-Net displays on the map the path
between both points.
U-Net creates a folder called Terrain sections in the Data tab and lists all the
created terrain sections in a related table.
6) Click anywhere on the map or on an object in the explorer in order to replace
the Terrain section tab by the Profile tab.
Note:
z All the created terrain sections are displayed on the map.
z All the terrain sections are listed in a manageable table. Standard features for
managing table contents (Fields, Delete, Filter, Sort, Locate on the map, Display
columns, Copy/Paste, Fill up/down, ...) are available in a context menu (when right
clicking on column(s) or record(s)) and in the Format, Edit and Records menus.
You can also access the table content management from the Table tab of the
terrain section property dialog.
z When selecting a terrain section in the table (on the map), this one is
simultaneously selected on the map (in the table) and displayed in the Terrain
section tab.
z The generic U-Net display dialog is available in order to manage the display of
each terrain section. Open the terrain section property dialog and select the
Display tab.
z A terrain section can be modified. On the map, right click on it and check that the
Edit command is selected. On the map, left click on a point and drag it (the left
button pressed) where you want. The terrain section cannot be changed if the Edit
command is not selected.
z A context menu including the Copy and Print commands is available when right
clicking anywhere in the Terrain section tab.
z Standard features (Delete, Rename...) are available in the context menu of the
terrain section folder.
XIII. Displaying the line of sight area
The line of sight represents an area within which visible contact can be made, i.e. the
visible zone from a site, choosing either to work on a simple radius or on a more
constraining Fresno ellipsoid.
To display the line of sight area associated with a site, proceed as follows:
4-8
1) Left click on the desired site in the Sites folder (Explorer window) or on the
map.
2) Left click to select the Line of sight area option from the context menu.
4) Enter the desired parameters and left click.
5) Click on OK to validate. U-Net then displays the line of sight area.
XIV. Setting the display properties of a site
U-Net always permits the user to manage object displays easily. For the sites, this can
be done by selecting the display tab of the site properties window. The properties
window is reached from the site context menu (right click on the site on the map or in
the Sites folder from the Explorer window).
On the site display window, you may:
1) Define the site display colours (text and symbol). You can display sites with
colours depending on their attributes. The attributes of the sites can be displayed
as labels in the workspace.
By left clicking on the symbol button, you may change the symbol
font, colour, type, style (bold, italic, underline) and background (colour and
type). Concerning the background, you may choose described below Table 4-2:
Table 4-2 Select background
none
halo
opaque
2) Display of the site name, or not and define the related font style.
3) Display of a radial grid around the site, or not.
4-9
Note:
If you use the Display tab in the Site folder properties dialog box in the Explorer
window, you may define globally the symbol and text sites display, depending
potentially on their attributes.
XV. Deleting built sites
In U-Net, sites (like transmitters) are organized in folders. Even if these two tables are
linked, it is possible to delete easily, in one shot, sites and transmitters referred to.
1) Open the Sites table.
2) Select the Sites you want to delete.
3) Press the Del button of your keyboard, or choose the Delete record command
from the Edit menu.
Note:
z When deleting a site where transmitters are positioned, U-Net automatically
removes the site and the transmitters without displaying a warning. Hence, to
cancel a deletion, use the undo feature available in the Edit menu.
z Sites can be deleted directly on the map, using their context menu.
4.3.2 Site Lists
I. Creating a site list
In addition to the dynamic filtering features, U-Net also enables users to define static
lists of sites. Unlike filter/sort/group criteria that may be only saved in user
configuration files, site lists are stored in the database. Therefore, when creating
an .atl document from the database, it is possible to recover only the sites of a list you
can choose. These site lists may be also used as filter so as to study in predictions
only sites of the list(s). In addition, site lists can be imported and exported as ASCII
files.
To create lists of sites, proceed as follows:
3) Choose the [Site list: Open Table] command from the open scrolling menu.
4-10
4) In the Site lists dialog, you may define one list per row. To validate a list creation,
select another row.
5) Select a list in the table and click on the Properties... button. Or Select a row and
double click on it.
6) In the List properties dialog, enter the sites belonging to the list (copy/paste is
supported).
II. Managing a site list
It is possible to add a site, a group of sites or all the sites in an existing list
subsequently.
To add a site in a list, proceed as follows:
1) Right click on a site in the explorer or on the map.
2) Choose the Add a site to a list... commands in the context menu.
3) In the Addition of sites in a list dialog, open the scrolling menu and select a list.
To add a group of sites in a list, proceed as follows:
1) Right click on a group of sites in the explorer.
2) Choose the Add sites to a list... command in the context menu.
3) In the Addition of sites in a list dialog.
4) Enter the name of a new list, Or Open the scrolling menu and select an existing
list.
To add all the sites in a list, proceed as follows:
1) Right click on the Sites folder in the explorer.
2) In the context menu, choose Site lists and then the Add sites to a list... command.
3) In the Addition of sites in a list dialog.
4) Enter the name of a new list, Or Open the scrolling menu and select an existing
list.
III. Exporting a site list
Site lists can be exported in ASCII text files

To export a site list, proceed as follows:
3) Choose the [Site list: Open Table] command from the open scrolling menu,
4) In the Site lists dialog, either Select an existing list in the table, Or Type the name
of a new list. Then, click on the Properties... button (or double click on it).
5) Click on Export.
6) In the Save as dialog, choose a directory to save the file, give a name to the file
and click on OK.
The ASCII text file has the following syntax:
4-11
Site name 1
Site name 2
...
It contains only a list of site names; the coordinates and other attributes of sites are not
saved. Thus, this file can be imported only if the sites have been previously created in
the .atl document.
IV. Importing a site list
Site lists can be created within U-Net. They can also be imported from an external
ASCII file.
To import a site list, proceed as follows:
3) Choose the [Site list: Open Table] command from the open scrolling menu.
4) In the Site lists dialog, either Select an existing list in the table, Or Type the name
of a new list. Then, click on the Properties... button (or double click on it).
5) Click on Import.
6) In the Open dialog, specify the path to access the file and click on Open to import
the file.
U-Net fills in the selected list with sites from the imported file. Sites listed before
importing the file are kept. U-Net displays a warning if a site in the list does not
exist in the .atl document.
V. Displaying site lists
Site lists created in the .atl document can be stored in the database. Therefore, when
a user opens an .atl document from a database that contains site lists, he has the
possibility to choose the list(s) of sites he wants to recover in his .atl document.
To choose the site list to be displayed from a database, proceed as follows:
1) After selecting the database to be open, U-Net displays the Options dialog.
2) In this window, either Select the value <ALL> to load all the sites in the .atl
document, Or Check only the box(es) of site lists you want to recover.
3) Click on OK to validate.
Only the sites from the selected list(s) will be available in the .atl document.
Note:
It is possible to select several lists at once. To do this, click one or several lists using
shift and/or Ctrl button at the same time and then, check/uncheck one of the boxes.
4-12
VI. Filtering site lists
To use site lists as filters, proceed as follows:

1) Right click on the Sites folder and select Properties.
2) In the General tab, click on the Filter button.
3) In the filter dialog, open the Site lists tab and check/uncheck box (es) of site lists
you want to keep/exclude in the .atl document.
4) Click on OK to validate.
U-Net only keeps sites belonging to site lists you have selected. In this case, sites
are not definitively removed from the .atl document. This is only a filter you can
cancel (by opening the Sites table and select Show all records in the Records
menu).
Note:
z It is possible to select several lists at once. To do this, click one or several lists
using shift and/or Ctrl button at the same time and then, check/uncheck one of the
boxes.
z All the boxes can be unchecked at once by clicking the Clear all button.
z By default, the value <ALL> is selected; it means there is no filter.
4.4 Antennas
4.4.1 Creating an Antenna
An antenna is a device used for radiating or receiving electromagnetic energy.

Depending on the type of project (GSM, UMTS, etc.), U-Net provides antennas
well-suited to the studied projects.
Furthermore, U-Net allows you to create antennas and set the parameters for the
characteristics of each of them (Name, manufacturer, gain, horizontal pattern, vertical
pattern, and comments).
Note:
Creating and setting parameters for different antennas on the basis of manufacturers
data is a long and meticulous operation. To make it easier for you U-Net allows the use
of copy and paste functions as easily as in all office automation tools. You may thus
create an antenna from a blank sheet or from an existing one; the U-Net display is
compatible with most spreadsheets or word processors.
4-13
To create an antenna, proceed as follows:

2) Right click on the Antennas folder to open the context menu.
3) Left click in the scrolling menu on New to create a new antenna.
windows.
5) Fill out the appropriate fields either manually, or by importing existing values.
6) Click either OK or Apply to validate.
Note:
z When performing a calculation along an angle on which no data is available, U-Net
computes a linear interpolation from existing pattern values.
z In the other properties tab, there are 3 U-Net custom properties like the Antenna
beamwidth, minimum and maximum frequencies corresponding to the antenna
utilization range. The Beamwidth is, in a plane containing the direction of the
maximum lobe of the antenna pattern, the angle between the two directions in
which the radiated power is one-half the maximum value of the lobe. Translated in
terms of dB, half power corresponds to -3 dB. In this window, you may enter this
angle in degrees.
z An Electrical tilt field is available in the General tab, but is not taken into account for
computations. Patterns must already integrate this parameter in their shape.
z It is possible to model remote electrical tilt antennas. This feature is not available
by default. In order to make it available, you must add a field in the Transmitters
table (either in the database if you work with .atl documents linked to a database or
in the .mdb template or your .atl document if you work in disconnected .atl
documents). This field must be named REDT; it is a float field with a length of 4.
4.4.2 Managing the Antenna Properties
In U-Net, you may edit and even modify the current parameters of an antenna. You
may do this action either individually for each antenna, or globally.
I. Single radiation pattern editing
You may edit horizontal or vertical patterns of each antenna by doing nearly the
same as creating an antenna. To do so, proceed as follows:
2) Expand the Antennas folder by left clicking on the sign left to the directory.
3) Select the antenna from which you want to edit the radiation pattern by left
clicking on it.
4-14
4) Activate the antenna properties window either by double clicking or by choosing

the properties option from the scrolling menu.
5) Choose the pattern tab associated with the pattern you want to edit.
You may change the values by filling new ones directly on the tables. Patterns can be
copied to clipboard or printed.
Note:
It is possible to display antenna patterns with either linear or logarithmic axes. To
choose your display system, right click in the pattern window and choose the
appropriate option from the open scrolling menu. The new shape is automatically
displayed in the pattern window.
II. Multiple radiation pattern editing
Like for the other parameters (sites, transmitters, etc...), U-Net enables you to manage
antennas in table form. To activate the antenna table, double click on the antenna
folder or choose the Open Table option from the antenna context menu (right click on
the antenna folder). By resizing cell heights and widths, you may obtain all the antenna
patterns on a view in order to make a comparative choice, which is shown in Figure
4-2.
Figure 4-2 Data Tab/Antenna/Open Table - Antenna Data table
4-15
Note:
z By using the copy (Ctrl+C) and paste (Ctrl+V) functions, you may even attribute
patterns from one antenna to another one by working directly on the pattern cells of
the antenna table,
z The way patterns are displayed (linear or logarithmic) is reported in the antenna
table as chosen in any single antenna properties dialog box.
4.4.3 Modifying Antenna Parameters in Tables
U-Net can easily manage antenna data with its table form availability. Like for the other
items, you may change data directly in the table (left click on the cell you want to
modify), or use the copy and paste (Ctrl+C and Ctrl+V) functions. This last feature is
very useful in that way you may reuse patterns of an antenna to others.
Example:
In the following table, a new antenna called Antenna1, from Martin SA, has been built,
with a 12 dBi Gain, and some patterns. The goal, here, is to export the patterns of a
certain antenna to the one of Antenna1.
To do so:
1) Activate the antenna table.
2) Select the pattern cell from the antenna whose pattern you want to export.
3) Copy the cell by using the Ctrl+C function. (See Figure 4-3).
Figure 4-3 Data Tab/Antenna/Open/Pattern copying - Antenna Data table
4) Select the pattern cell from the antenna you want to change the pattern.
5) Paste the patterns by using the Ctrl+V option (See Figure 4-4).
4-16
Figure 4-4 Data Tab/Antenna/Open/Pattern Pasting - Antenna Data table
U-Net replaces the old pattern by the new one both in the antenna table and properties
window. You can check that data have also been adapted in the patterns table of the
modified antenna properties window.
4.4.4 Copying Antenna Patterns to the Clipboard
To copy the horizontal/vertical pattern of an existing antenna to the clipboard,

proceed as follows:
3) Select the antenna from which you want to copy the radiation pattern by left
clicking on it.
5) Choose the pattern tab associated with the pattern you want to edit
(horizontal/vertical).
6) Right click on the pattern window in order to open the associated context menu.
7) Choose the Copy command from the open menu.
This can be made either on a linear or a logarithmic display.
4.4.5 Importing Antenna Patterns
I. Using existing values
If you already have table formatted values for antenna patterns in a file (spreadsheet
or word processor), you can “import” them directly into the cells of the patterns table by
copying and pasting from your application (a spreadsheet in the following example).
4-17
1) Select from your spreadsheet the columns containing angles and values you
want to import.
2) Copy your selection (See Figure 4-5).
Figure 4-5 Horizontal pattern values copying
3) Switch to U-Net.
4) Click the first top left cell of the corresponding pattern table in the antenna
properties window.
5) Paste the data by using the Ctrl+V shortcut.
6) Left click on the Apply button.
II. Missing values in selection
If there are some missing values (blank lines) in your data sheet, U-Net is able to
interpolate the values in order to obtain a complete and realistic pattern all around the
antenna. To do so, just follow exactly the steps as above. When pasted, blank lines are
compacted in the pattern table when the apply button is pressed.
4.4.6 Printing Antenna Patterns
To print the horizontal/vertical pattern of an existing antenna, proceed as follows:

3) Select the antenna from which you want to print the radiation pattern by left
clicking on it.
5) Choose the pattern tab associated with the pattern you want to edit
(horizontal/vertical).
6) Right click on the pattern window in order to open the associated context menu.
7) Choose the Print... command from the open menu.
4-18
This can be made either on a linear or a logarithmic display.
4.5 Transmitters
4.5.1 Transmitters Overview
A transmitter is the source or generator of any signal on a transmission medium. A

transmitter is a piece of equipment composed of some antennas located on a site.
Depending on the type of project, U-Net manages differently the transmitter’s
parameters. Whatever the project, you may manage globally or individually the
transmitter parameters and their single activity/inactivity. A base station is a group of
transmitters on the same site. With U-Net, you may work on several types, from single
to multi-sectored stations, by creating new ones from nothing or templates.
Then depending on the project type, transmitters are managed differently. Hence,
additional levels are introduced like subcells and TRXs in TDMA/GSM projects, cells
(one carrier on a transmitter) for WCDMA/UMTS and CDMA/CDMA2000 projects.
So, the items referenced in this part deal with common management of transmitters
and station templates. All specific parts depending on the technology are described in
their respective parts. In the coming sections, steps will describe the creation, deletion,
moving and setting of the global properties of the transmitters and station templates.
4.5.2 Transmitters Properties
I. Creating a transmitter
In U-Net, several antennas can be installed on the same transmitter. The creative
steps for one antenna and more antennas transmitters are identical. The second
antenna used is automatically placed at the same height than the first one.
To create a transmitter, proceed as follows:
2) Right click on the transmitters folder.
3) Choose the New option from the context menu.
windows.
5) Fill out the appropriate fields in the several tab windows.
6) Click OK or Apply to validate the new transmitter.
U-Net opens the "Transmitter new element properties" window containing the main
characteristics describing the transmitter you are building. This window contains at
least 2 tabs, additional tabs being linked with the type of project template you are
working on.
The standard tabs are General and Transmitter, and deal with the definition of the
transmitter, its location, the assignment to some specific radio equipment (leading to
4-19
losses computation), and the antenna(s) used on this transmitter. The power definition
is located in the Transmitter part in GSM/GPRS/EDGE projects, whereas its definition
is made at the cell level in WCDMA/UMTS or CDMA/CDMA2000 projects.
Note:
The Other Properties tab window is available for any project if a user-defined field has
been added to the transmitter table.
II. Naming automatically transmitters
U-Net integrates, by default, a prefix to transmitter names which is the name of the
related site. In addition to this prefix, the sector number corresponding to the
considered transmitter is added. Nevertheless, you can force U-Net not to use this
default prefix and to prefer user-defined prefixes. You can customise it by adding the
syntax described below in a U-Net.ini file. You must create this file and place it in the
U-Net installation directory.
The syntax in order to define a new prefix to transmitter names in the U-Net.ini file is
the following:
[Transmitter]
Prefix=”newprefix”
Each new transmitter will be named “newprefixN” instead of “TxN”.
Another solution is to use an automatic prefix by writing these lines:
[Transmitter]
Prefix=”<AUTO>”
In this case, each new transmitter is called “Site name_n”. Site name is the name of
the site where the transmitter is located and n is the transmitter number on this site.
4-20
Note:
z 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.
z When changing the name of a site, U-Net automatically renames transmitters and
cells related to the site which names contain the site name. In the same way, if you
rename a transmitter, the corresponding cells are automatically renamed. The
automatic renaming according to site name is by default available. However, it may
be blocked if you add the following lines in the U-Net.ini file:
[AutoRename]
Transmitters = 0
3GCells = 0
Transmitters refer to transmitter renaming when the site name is changed.
3GCells refers to cell renaming when the transmitter name is changed.
z Automatically naming sites is also possible.
The default sector numbering can be set. By default, when creating a tri-sectors
station, the numbering of the first sector starts from 1. Therefore, we will have 3
transmitters named Site_1, Site_2 and Site_3.
To differently initialize the numbering of the first sector, add these lines in the U-Net.ini
file:
[Transmitter]
First=x (x must be an integer)
III. Managing transmitter properties
Like for all objects organised in folders (Sites, Transmitters, Antennas, Predictions,
Simulations, measurements, etc...) within U-Net, transmitters can be managed either
individually or globally. A global setting is applied to all the filtered transmitters.
IV. Global properties management
In U-Net, you may manage globally the properties associated with transmitters of
your network:
The 4 standard tab windows are: General, Table, Propagation and Display.
4-21
- The General tab deals with folder organisation and associate configurations.
- The Table tab helps you to manage contents in the Transmitter table.
- The Propagation tab makes it possible to assign the same propagation model(s),
calculation radius (or radii), path loss resolution(s) to all filtered transmitters of the
folder, and to manage the path loss result storage,
- The Station templates tab allows you to manage (creation, modification, deletion)
models of stations.
- The Display tab allows you to manage the display of transmitters depending on their
attributes, to manage the legend, labels on the map, and the contents of help popups
using the tip tool .
Note:
z To attribute different colours to the transmitters (used in coverage prediction for
example) in the network easily, use the automatic command from the Display type
scrolling box in the Display tab window (and validate by pressing the Apply button).
z In GSM/GPRS/EDGE projects, a BSIC format tab is available. In this one, you can
define whether BSICs are in octal or decimal notations.
V. Individual property management
There are two ways to edit properties of each transmitter in the current network.
To do so,
1) Left click on the Data tab of the Explorer window, Expand the transmitters
folder by clicking on the button in front of it, and Right click on the
transmitter you want to manage.
2) or Select on the map the transmitter you want to manage by left clicking on the
appropriate Tx symbol (arrow).
The displayed window contains at least 4 tabs (General, Transmitter, Propagation, and
Display). The Other Properties tab is available if some user defined fields have been
added to the Transmitter table:
- The General tab deals with the referring site and the location of the current
transmitter
- The Transmitter tab is linked with the definition of power (in GSM/GPRS/EDGE
projects), assigned losses and antennas built on this transmitter,
4-22
- The Propagation tab makes it possible to assign propagation model(s), calculation

radius (or radii), path loss resolution(s) to the current transmitter, and to manage the
path loss result storage,
- The display tab allows you to manage the colour assigned to the current transmitter.
Note:
z You can open the property dialog of the Site on which the transmitter is built by
clicking the button on the right of the scrolling site selection box in the
General tab.
z You can open the property dialog of the Antenna used as main antenna on the
transmitter by clicking the button on the right of the scrolling antenna

selection box in the Transmitter tab.
VI. Moving a transmitter on the map
Even if transmitters are linked with sites, it is possible to shift them from their reference
site by adjusting Dx and Dy contained in each transmitter property dialog box. Dx (resp.
Dy) is the distance (in metres) between the considered transmitter and the basis site
X-positive (Y-positive) directed.
Nevertheless, it is possible to move a transmitter by using your mouse. To do so,
proceed as follows:
1) Select the transmitter you want to move on the map by left clicking on it and
maintaining it, a specific second pointer appears close to the mouse pointer.
2) Drag the transmitter to the desired location.
3) Release the mouse button when reached.
Dx and Dy values are automatically modified in the transmitter properties.
4-23
VII. Adjusting transmitter azimuths
In U-Net, it is possible to modify the azimuth of the antenna(s) of any transmitter by

accessing its property dialog box. Azimuth values are defined in degrees, 0° indicating
north, and are ordered in a clockwise direction.
It is also possible to modify the azimuth of the first antenna of any transmitter by
using your mouse. To do so, proceed as follows:
1) Select the transmitter you want to move on the map by left clicking on it and
release the mouse button.
2) Move the pointer to the arrow extremity of the selected transmitter, a
specific rotation pointer appears close to the mouse pointer.
3) Left click on the green dot and maintain the mouse button pressed.
4) Drag the pointer in order to execute a rotation around the original location.
5) The current value of the azimuth is displayed in real time in the extreme left
part of the status bar .
6) Release the mouse button when the desired angle is reached.
The azimuth value for the first antenna of the considered transmitter is automatically
modified in the transmitter properties.
It is also possible to modify the azimuth of the first antenna of all the transmitters
situated on a site by using your mouse. To do so, proceed as follows:
1) Select any transmitter of the site you want to rotate on the map by left clicking
on it and release the mouse button.
2) Move the pointer to the arrow extremity of the selected transmitter, a
specific rotation pointer appears close to the mouse pointer.
3) Left click on the green dot and maintain the mouse button pressed.
4) Hold down the CTRL button on your keyboard.
5) Drag the pointer in order to execute a rotation around the original location.
4-24
6) The current value of the azimuth is displayed in real time in the extreme left
part of the status bar .
7) Release the mouse button and the CTRL button when the desired angle is
reached.
Azimuth values for the first antenna of all the transmitters concerned are automatically
modified in the transmitter properties.
Note:
The precision of the azimuth angle depends on the distance of the cursor from the
transmitter symbol. Azimuth angles change by:
z 1 degree when the cursor is moved within a distance of 10 times the size of the
transmitter symbol.
z 0.1 degree when the cursor is moved outside this region.
VIII. Installing several antennas on a transmitter
In U-Net, it is possible to assign several antennas on the same transmitter in order to

compose the several associated patterns of each of them.
To build several antennas on the same transmitter, proceed as follows:
transmitter you want to manage.
2) Or Select on the map the transmitter you want to manage by left clicking on the
4) Click the Transmitter tab of the open window.
5) Use the What's this help to get description about the open dialog.
6) In the Other antennas part, define additional antennas. Click on the first cell in
the Antenna column, open the scrolling menu (by clicking on the arrow) and
choose an antenna in the scrolling menu. Then, enter its characteristics: azimuth
(Azimuth column), down tilt (Tilt column) and the percentage of power dedicated
to this antenna (Percent_power column). Select another row to validate the new
antenna installation.
7) Click OK or Apply to validate the antenna building.
4-25
Note:
z Entering 0% in the Percent_power column means that only the first antenna will be
considered.
z The other antennas used are automatically placed at the same height as the first
one.
z The characteristics of additional antennas are no longer described in the
Transmitters table.
IX. Setting transmitter activity
When transmitters are built in a network, you may decide to activate them or not.
Predictions, simulations and associated reports/statistics take into account only active
transmitters (and not filtered transmitters). In the Explorer window, active transmitters
are displayed in red ( symbol) in the transmitter folder, unlike inactive ones which
are displayed in white ( symbol).
To set the activity of a transmitter,
1) Select the Transmitter tab from the transmitter properties.
2) Or Activate the transmitter table window.
3) (Un)check the active box in order to make the transmitter (un)active in the
network.
4) You may also manage the transmitters activity from the context menu associated
with each transmitter individually (right click on the transmitter subfolder in the
geo tab from the explorer window) or globally (right click on the transmitters folder
in the geo tab from the explorer window).
X. Deleting a transmitter
To delete an existing transmitter, proceed as follows:

transmitter you want to delete.
2) Or Select on the map the transmitter ( )you want to delete by left clicking
on the appropriate Tx symbol (arrow).
3) Choose the Delete option from the context menu.
Another alternative is to delete the line associated with the transmitter you want to
delete in the Transmitters table.
4-26
Note:
When selecting a transmitter, be careful to reach the selection. is
different. In that case, that is the site which is selected. Since the deletion action is
possible on sites on which transmitters are built, be sure of your selection.
4.5.3 Station Templates
I. Creating a station template
A station is one transmitter or a group of transmitters on a same site sharing the same
properties. With U-Net, you may create, modify or delete station templates and build
your network from stations instead of single transmitters.
To create a new station template, proceed as follows:
Either
1) From the toolbar, left click on the template scrolling box
2) Select the Manage Templates... tool
Or
4) Click the Station templates tab.
Then
1) Click the button to create a new station template.

window.
3) Enter the parameters of the station being currently built.
The new station template is then available in the station scrolling menu.
4-27
Note:
In UMTS or CDMA/CDMA2000, the station template must integrate the site equipment
properties related to the site on which it will be dropped.
II. Defining station template properties
To manage a station template, proceed as follows:
Either,
2) Select the Manage Template... tool
Or
Then
1) Select the template you want to manage in the Available templates box.
2) Click the button to open the station template properties dialog

box.
window.
4) Set the parameters of the current station.
You can also add user-defined fields to station templates through the station templates
management window. These additional fields appear in a new tab in the station
template properties window, named Other properties, if there are corresponding
4-28
user-defined fields available in the sites table. This feature has been designed to allow
users to introduce user-defined fields in the sites table to the station templates. So that
the sites then created with this template contain these user-defined fields by default.
To add, modify or delete a field in the station templates, proceed as follows:
Either,
.
Or
Then
1) Click the button on the station template management window to

open the station template fields dialog box.
2) Click to add, to modify properties or

to delete a user-defined field.
Note:
z The properties you can adjust are similar to the transmitter properties ones.
z The user-defined fields added in the station templates must be the same as the
user-defined fields in the sites table to be taken into account.
III. Deleting a station template
4-29
To delete a station template, proceed as follows:

Either
Or
Then
1) Select the template you want to delete in the Available templates box.
2) Click the button.

3) Click either OK or Cancel to close the dialog box.
IV. Dropping a station from a template
In U-Net, as for (site, transmitter) pairs, you can easily build station from available
templates.
Proceed as follows to create a station:
1) Select in the station template scrolling box (located in the toolbar) the template
to use.
2) Left click on the New station button, left to the scrolling box.
3) Put the station on the appropriate location on your map.

You may also build several identical stations from a template in U-Net. To do so, you
must have previously defined a hexagonal cell radius for the corresponding
template in its properties dialog window. Once this is done, proceed as follows to
create groups of stations:
to use.
2) Left click on the Hexagonal design button, left of the scrolling box.
4-30
3) Draw the zone in which you want to build the stations on the map as a
computation or focus zone.
4) Stations with associated hexagonal shapes around are built as best possible in
the drawn zone.
Once built, stations objects (sites and transmitters) are put in the corresponding
folders, and you may work on them as if they were sites and transmitters. Hence, you
may add additional antennas on each created transmitter.
Note:
z When you select a specific template, if the Hexagonal design button is not available
( ), please define a hexagonal cell radius for this template in its properties dialog
window, used as the hexagonal shape radius.
z In UMTS or CDMA/CDMA2000, the site on which is dropped the station has UMTS
equipment properties which are defined in the station template dialog.
z It is also possible to drop a station on an existing site.
V. Dropping a station on an existing site
In U-Net, the standard way in dropping stations is at the same time the creation of
related site and corresponding properties (e.g. site equipment in UMTS or
CDMA/CDMA2000). Nevertheless, it is easily possible to drop a station from a
template on existing site.
Once the reference site is available, to drop a station from a template on it,
proceed as follows:
to use.
2) Uncheck the visibility flag in front of the hexagonal design folder.
3) Left click on the New station button, left of the scrolling box.
4) Move your pointer to the reference site on your map.

5) When the pointer sticks on it, put the station on the site by left clicking.
VI. Managing a multi-sectored station
Even if you can select only one transmitter at a time, it is possible to group together all
the transmitters composing a same base station (defined in the station templates
properties).
4-31

2) Right click on the transmitter folder to open the context menu.
3) Choose the group by sites option.
4) Transmitters are then displayed under sites subfolders in the transmitters folder.
VII. Merging hexagonal groups of base stations
When you build several hexagonal groups of different station templates, some
hexagons may overlap. These overlapping zones can overestimate the number of
needed sites regarding the number of transmitters. To avoid that, U-Net provides a
tool that helps you to merge sites of different hexagon groups.
To merge sites of different hexagonal groups located within a certain distance,
proceed as follows:
2) Display the several hexagon groups by checking the box ( ) in front of the
Hexagonal design folder.
3) Right click on the Hexagonal design folder to open the context menu.
4) Choose the Merge sites... command from the open menu.
5) Enter the distance within which you want to merge sites.
6) Click OK to start the merging process.
Example: let's imagine that two base bi-sector stations of different hexagon groups are
located within a radius of 200 metres, and their respective hexagon cell radius is 500
m and 1000m. With this feature, you can merge sites located within a distance of e.g.
300 metres. At the end of the process, there will be only one site on which 4
transmitters will be built.
4.6 Repeaters
4.6.1 Repeaters Overview
A simple modeling of repeaters is available. The modeling focuses on the impact of

repeaters and the additional coverage they provide to transmitters.
Broad-band repeaters are not modeled. A repeater is similarly modeled for 2G and 3G
networks, except that on the 2G side, U-Net deals with EIRP and on the 3G side with a
global amplification gain. We assume that all the TRXs from the 2G donor transmitter,
as well as all the carriers from the 3G donor transmitter are amplified.
4.6.2 Creating a Repeater
It is possible to model a repeater for which there is a donor transmitter.

To create a repeater, proceed as follows:
4-32
1) Select a transmitter on the map or in the Transmitters folder of explorer ; it will

be the donor transmitter.
2) In the toolbar, click on the icon (active only if a transmitter has been
previously selected).
3) Place the repeater on the map.
A repeater can be added on an existing site or can itself generate a new site. U-Net
creates a repeater linked to the selected donor transmitter. In the explorer, the new site
is listed in the Sites folder and the repeater under its donor transmitter.
The repeater is represented on the map by the symbol . The repeater has the
colour of the donor transmitter and by default, the same azimuth. When clicking on it,
U-Net displays a link to the donor transmitter.
4.6.3 Managing Repeater Properties
The repeater property dialog can be open either by double-clicking on the repeater on
the map or in the explorer, or by selecting Properties... in the repeater context menu. It
consists of four parts, the General part, the Donor part, the Coverage part and the
Propagation part.
Standard properties are available in the General tab. This tab contains general
information on the repeater:
z The name of the repeater. By default, repeaters are called RepeaterN.
z The donor transmitter name that cannot be changed after the repeater creation.
z The site which it is located on.
z The distance offset on x (Dx) and y (Dy) axis.
z The amplifier gain (amplification gain).
z It will be used in the link budget to evaluate the repeater total gain.
z The delay offset (Internal delay) of the repeater.
z Delay offset is an informative field in this version.
z Comments.
All the created repeaters and donor side properties are listed in the Repeaters table.
To open this table, right click on the Transmitters folder and then, select Repeaters and
Open Table.
4-33
Note:
The table cannot be used to create repeaters since only properties of the donor side
may be specified. On the other hand, it allows you to delete repeaters or modify their
characteristics ; standard features for managing table content (Fill down/up, 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 menu.
4.6.4 Setting Donor Properties of a Repeater
Donor properties can be accessed from the donor tab of any repeater property dialog.
Parameters of this tab model the repeater donor side facing the donor transmitter.
The different settings are listed below:
z The repeater donor side antenna has to be selected in the model scrolling menu.
By default, if no antenna is installed on the repeater, U-Net takes into account an
omni antenna with 0 dBi gain.
z Enter the repeater antenna height. U-Net evaluates the repeater azimuth and
downtilt considering that the donor side antenna of the repeater is pointed to the
antenna of the donor transmitter.
z Azimuth and downtilt can also be user-defined.
z The Calculate button enables you to update azimuth and downtilt values after
changing the repeater donor side antenna height or the repeater location. If you
choose another site or change site coordinates in the General tab, click on Apply
before using the Calculate button.
z Finally, you may model the feeder equipment used. Choose a type of feeder in
the Feeders scrolling menu and enter its length.
4.6.5 Setting Coverage Properties of a Repeater
Coverage properties can be accessed from the Coverage side tab of any repeater
property dialog. This tab enables you to model the repeater coverage side.
The different settings are listed below:
z The repeater activity status has to be chosen. Only active repeaters (displayed
with red colour in the explorer) are calculated.
z Choose the repeater coverage side antenna in the model scrolling menu. By
default, if no antenna is installed on the repeater, U-Net takes into account an
omni antenna with 0 dBi gain.
z Enter the height, azimuth and downtilt of the repeater coverage side antenna.
z Additional antennas can be specified.
4-34
Note:
By default, characteristics (antenna, azimuth, height,...) of the repeater coverage side
correspond to the donor transmitter characteristics.
z Finally, you may model the feeder equipment used. Choose a type of feeder in
the Feeders scrolling menu and enter its length.
z You may define EIRP in case of GSM/GPRS/EDGE networks or total gain in
UMTS/CDMA/CDMA2000 networks. U-Net will use this value (EIRP or total gain)
to calculate the signal level received from the repeater. Either directly enter a
value, or click on the Calculate button in order for U-Net to deduce the value from
the link budget. The Calculate button enables you to update the value after
changing any characteristic in the Coverage tab. If you modify other
characteristics in the General and Donor side tabs, click on Apply before using
the Calculate button.
Note:
Default EIRP takes into account donor transmitter EIRP, propagation loss between the
donor transmitter and the repeater, donor part characteristics (donor antenna gain,
feeder losses), amplifier gain and coverage part characteristics (coverage antenna
gain and feeder losses). The default gain is applied to each power (pilot power, SCH
power...) and takes into account the same information about donor transmitter, donor
and coverage parts of the repeater.
Assumptions:
z The link between the donor transmitter and the repeater has the same frequency
as the network.
z Propagation loss between donor transmitter and repeater is calculated using the
ITU 526-5 propagation model.
Since repeaters will be involved in computations, propagation parameters have to be
set like in transmitters. They can be accessed from the Propagation side tab of any
repeater property dialog.
As for the transmitter, you may specify:
z A propagation model, a calculation radius and a resolution used to compute the
main path loss matrix.
z A propagation model, a calculation radius and a resolution taken into account to
calculate the extended path loss matrix.
4-35
Note:
z By default, U-Net assigns to the repeater calculation settings (propagation model,
calculation radius, grid resolution,...) defined for the donor transmitter.
z The definition of the calculation radius in the repeater property dialog has an effect
on the related transmitters that will be taken into account or not because of the use
of a computation zone.
4.6.6 Updating Repeater Parameters
As for transmitters, it is possible to select a repeater on the map, to change its azimuth
and its position relating to its site.
Angle calculation
In addition, it is possible to globally update calculated azimuths and downtilts of
repeater donor side antennas by selecting Repeaters and Calculate Angles in the
Transmitters context menu.
Finally, it is possible to globally update calculated total gains (or calculated EIRP) of all
the repeaters by selecting Repeaters and Calculate Gain (or Calculate EIRP) in the
Transmitters context menu.
4.6.7 Using Repeaters in Calculations
Repeaters have an impact on the donor transmitter coverage.
I. Path loss matrices
U-Net calculates a main path loss matrix and potentially an extended one for each
active repeater:
z Which satisfies the filter criteria defined.
z Which has a calculation area (intersection between the calculation radius and
rectangle including the computation zone).
Computations are performed with the standard validity management carried out for
any transmitter.
Features such as export of repeater path loss matrices, the possibility to evaluate the
number of transmitters/repeaters to recalculate, the list of transmitters/repeaters
calculated and their invalidity reasons, ... are available in the Result storage dialog and
in the Propagation tab of the Transmitters property dialog.
II. Coverage predictions
The calculation area is the union between calculation areas of the donor transmitter
and the repeater. U-Net displays a composite coverage ; on each pixel, it takes the
4-36
sum of both signals, the signal level received from the donor transmitter and the signal
level from the repeater.
The desynchronisation, which would lead to constructive or destructive operation on
signals, is not modeled.
III. Point analysis
In the Profile tab, it is possible to study the profile between a repeater and a target
receiver. In this case, U-Net gives the signal level from the repeater.
In the Reception and Results tabs, it provides the composite signal, the signal level
received from the donor transmitter plus the signal level from the repeater.
IV. GSM/GPRS/EDGE specific calculations
Repeaters have no direct impact on:

z TRX dimensioning.
z The donor transmitter (which has an extended coverage) is supposed to deal with
more traffic and so naturally needs more TRXs.
z Neighbour allocation.
z The donor transmitter would naturally have more neighbours as its coverage is
extended.
z Frequency allocation.
z The donor transmitter (which has an extended coverage) is supposed to create
more interference so allocation will naturally be more constrained.
V. UMTS, CDMA2000 and CDMA/ IS 95 specific calculations
Repeaters have no direct impact on:

z Power control simulation.
z Neighbour allocation.
z The donor transmitter would naturally have more neighbours as its coverage is
extended.
z Scrambling code allocation.
4.7 Radio Equipment

4.7.1 Radio Equipment Overview
Radio equipment is related to several devices producing losses on transmitters. In

U-Net, it is possible to calculate such losses for each type of equipment regarding their
specific characteristics. The calculated values may then be used to either determine
total loss on transmitters or indicate their order of magnitude for each of them.
Furthermore, for UMTS or CDMA/CDMA2000 projects, assigning equipment to
transmitter helps in the determination of the Total noise figure using the Friis equation.
4-37
U-Net enables you to model transmitter equipment in any project. Radio equipment
consists of three main parts:
z Tower Mounted Amplifier (also called Mast Head Amplifier): it is used to reduce
the composite noise figure of the base station. TMAs are connected between the
antenna and the feeder cable.
z Feeders.
z BTS.
All the components, tower mounted amplifiers, feeders and BTS, are described in
three associated tables. In addition, some characteristics, which may be different for
transmitters using the same equipment, are specified in each transmitter properties.
Equipment can also be managed in a database structure.
4.7.2 Managing TMA Equipment
TMA (Tower Mounted Amplifier) are used in the equipment specifications linked with
each transmitter. When defined, TMA are available and can be assigned individually to
each transmitter of the network.
To create/manage tower mounted amplifiers equipment, proceed as follows:
2) Right click on the Transmitters folder to open the associated context menu.
3) Choose the Equipment: TMA equipment... option from the open menu.
dialog window.
5) Click on the Records tab to open the TMA definition table.
6) Create TMA equipment (give an equipment name to each newly created one),
and, for each of them, specify noise figure (noise figure TMA, dB), uplink gain
(reception gain TMA, dB) and downlink loss (transmission losses TMA, dB).
7) Click the Close button to validate.
Note:
z Losses and gains must be positive values.
z The Table tab window allows you to manage user-defined variables in the Records
tab window.
z Only transmission values are used in TDMA/GSM projects.
4-38
4.7.3 Managing Feeder Equipment
Feeders are used in the equipment specifications linked with each transmitter. When
defined, feeder types are available and can be assigned individually to each
transmitter of the network.
To create/manage feeder equipment, proceed as follows:
3) Choose the Equipment: Feeder equipment... option from the open menu.
dialog window.
5) Click on the Records tab to open the Feeder definition table.
6) Create Feeder equipment (give an equipment name to each newly created one),
and, for each of them, specify losses per metre (feeder losses per metre, dB/m)
and the connector transmission and reception losses (dB).
Note:
z Losses must be positive values.
tab window.
z In CDMA/CDMA2000 or WCDMA/UMTS projects, feeder and connector losses are
not included in the transmitter uplink total losses since they are already taken into
account in the noise figure evaluation.
4.7.4 Managing BTS Equipment
BTS equipment is used in the equipment specifications linked with each transmitter.
When defined, BTS types are available and can be assigned individually to each
transmitter of the network.
To create/manage BTS equipment, proceed as follows:
3) Choose the Equipment: BTS equipment... option from the context menu.
dialog window.
5) Click on the Records tab to open the BTS definition table.
4-39
6) Create BTS equipment (give an equipment name to each newly created one),
and, for each of them, specify noise figure (BTS noise figure, dB).
Note:
z Noise figures must be positive values.
tab window.
4.7.5 Assigning Radio Equipment to Transmitter
Once defined, TMA, feeder and BTS equipment can be assigned to transmitters taking
part of a network in order to determine corresponding total losses. For example, in
GSM/GPRS/EDGE projects, losses due to equipment will be available only when the
Power and Losses option is chosen to define the efficient power of transmitters instead
of EIRP.
To define transmitter radio equipment, proceed as follows:
2) Expand the transmitters folder by clicking on the button in front of it.
Either,
1) Right click on the transmitter you want to parameter radio equipment to open
2) Choose the Properties command from the open menu.
Or
1) Double click on the transmitter you want to parameter radio equipment.
Then
1) Click on the Transmitter tab from the open window.
2) Click the button to open the associated dialog box.

window.
4-40
Note:
z Losses and gains must be positive values.
4.7.6 Using Equipment to Compute Transmitter Losses
TMA, feeder and BTS equipment allows you to calculate losses on transmitters. Once
their characteristics defined for each transmitter, U-Net calculates downlink losses for
GSM/GPRS/EDGE projects, and downlink and uplink losses for CDMA projects,
including the total noise figure, using the Friis equation.
To display calculated loss regarding to equipment specifications for each transmitters,
open the properties dialog associated with the considered transmitter, and choose the
Transmitter tab window. Calculated values are indicated in brackets on the right of the
boxes linked with the different types of losses. This fields are editable and can be user
modified.
Note:
z When loss information is missing, the following default values are considered:
Gain=0dB and Noise figure=0dB.
z Since they are already taken into account in the noise figure evaluation, feeder and
connector losses are not included in the transmitter uplink total losses
(CDMA/CDMA2000 or WCDMA/UMTS projects).
z Whatever the value in the Real field(s) is (even = 0) and wherever it comes from
(computed or user-defined), this is the one which is taken into account for the
loss(es) or noise figure evaluation.
U-Net does not automatically recalculate total losses and total noise figure when
modifying equipment characteristics in their respective tables, in each transmitter
Equipment specifications window or in the Transmitters table. It keeps initial values
and displays updated values in parentheses.
For automatic total losses and total noise figure update from equipment
characteristics, proceed as follows:
Either,
1) Right click on the Transmitters folder, choose Equipment: Apply to transmitters.
Or
4-41
1) Open the Transmitters table.

Then
1) Select the whole column(s) you want to calculate.
2) Empty it (them) using the Delete key on your keyboard.
Note:
The first way enables you to update total losses and total noise figure of all the
transmitters while the second one can be used on a group of transmitters.
4.7.7 Managing Radio Equipment in a Database Structure
In U-Net, TMA, feeder and BTS equipment are related to some objects from a
database. These are available when creating a new environment .atl or when opening
an existing one not connected to a database.
To enable the equipment modeling in existing projects connected to a central
database, a specific procedure must be achieved. This is given below:
1) Let several users be connected with a central database. The database
administrator is one of them.
2) In the database, the administrator must create three tables, called
‘TMAEquipments’, ‘FeederEquipments’, and ‘BTSEquipments’ ( see Table 4-3,
Table 4-4 and Table 4-5), respectively dedicated to TMA, feeder and BTS
equipment. Tables are described hereafter. In each table, assign a primary key
to the field ‘NAME’.
Table 4-3 TMAEquipments table
Field Label Length Description
NAME Text 255 Name of Tower Mounted Amplifier
DL_LOSSES Float 4 Downlink losses of Tower Mounted

Amplifier
NOISE_FIGURE Float 4 Noise figure of Tower Mounted Amplifier
UL_GAIN Float 4 Uplink gain of Tower Mounted Amplifier
4-42
Table 4-4 FeederEquipments table
NAME Text 255 Name of Feeder
LOSS_PER_METER Float 4 Feeder loss per meter
Table 4-5 BTSEquipments table
NAME Text 255 Name of base station
NOISE_FIGURE Float 4 Noise figure of base station
3) The administrator must also define fields, listed below, in the existing
Transmitters and TplTransmitters tables, described below Table 4-6.
Table 4-6 Fields to add in the Transmitters and TplTransmitters tables
TMA_NAME Text 255 Name of the TMA equipment
FEEDER_NAME Text 255 Name of the feeder equipment
BTS_NAME Text 255 Name of the BTS equipment
FEEDERLENGTH_DL Float 4 Length of DL feeder
FEEDERLENGTH_UL Float 4 Length of UL feeder
ANTDIVGAIN Float 4 Antenna gain diversity
MISCDLL Float 4 Miscellaneous DL loss
MISCULL Float 4 Miscellaneous UL loss
Users may then refresh their documents .atl or open a new one from the database
from projects created under U-Net.
4-43
GENEX U-Net Wireless Network Planning Software Chapter 5 Managing Computations in U-Net
Chapter 5 Managing Computations in U-Net
5.1 Computations in U-Net Overview

Once the network has been built, U-Net allows you to create some general studies. To
make this easier, U-Net provides calculation tools like multithread and distributed
computing features. Moreover, the several processes can be either displayed in an
event viewer window or inside a log file.
U-Net provides also the possibility to limit the calculation loading and time by
introducing polygonal zones. These help you to restrict the computation to a certain set
of transmitters, and to clip related computations, coverages and other outputs. This is
made by using two types of polygonal zones: the computation zone and the focus zone.
The first one is the one on which are made the computations, the second one on which
are made the statistical outputs.
Depending on the project type on which you are working on, you may choose between
the different propagation models available in U-Net. Selecting the most appropriate one,
you may even decide to attribute different ones to the different transmitters composing
the network.
Predictions may be featured in two ways:
z By using the point analysis tool in order to predict, at any point of the current map,
the reception profile between a reference transmitter (in real time) and the value of
the several signal levels of the surrounding transmitters at a given point (using
existing path loss matrices).
z By computing different types of standard coverage predictions: coverage by
transmitter, coverage by signal level and overlapping zones. Many customisation
features on coverage studies are available in order to make their analysis easier.
All of these are easily manageable. Furthermore, U-Net allows you to export coverage
and path loss results with a view to use them elsewhere in another application.
Note:
z For CDMA technology projects (UMTS and CDMA/CDMA2000), U-Net provides
also an active set analysis based on a particular scenario (given terminal, mobility
and terminal) for an existing simulation at a given point.
z Other specific studies like interference studies (GSM/GPRS/EDGE projects) or
handover, service availability, etc... (UMTS and CDMA/CDMA2000) are also
possible.
5-1
5.2 Computing in Polygonal Areas

5.2.1 Computation and Focus Zones Overview
The computation and focus zones are user-definable polygonal areas based on the
map cutting. Drawing such polygonal zones allows the user to reduce calculation area
and calculation times, and to permit a more precise analysis on computation results.
The computation zone had several functions:
z Determining transmitters geographically involved in computations. The
transmitters that will be taken into account are the ones which have at least one
calculation radius (main and/or secondary, at the transmitter or repeater level)
intersecting the rectangle around the computation zone.
z Determining the validity of path loss matrices (i.e. Increasing the computation zone
size invalidates path loss results).
z Clipping traffic maps (during Monte-Carlo simulations, mobiles are dropped within
the computation zone).
z Clipping all the coverage areas.
In other words, path loss matrices are computed within the rectangle around the
computation zone and coverages are displayed within the computation zone itself.
The [focus zone] help you in:
z Clipping all reports and statistics,
z Clipping the graphic display with lighter colours around the polygon (and optionally
when printing).
To sum up, computation zone is the area where U-Net works out path loss matrices,
coverage studies, Monte-Carlo and power control simulations while focus zone is the
area where you want the results. These features provide a practical way of analysing
sub-areas once the main area is fully calculated. Furthermore, they enable you to
analyse simulation results and coverage without border effect.
Like other polygonal objects (e.g. clutter or traffic), computation and focus zone are
easy to manage in U-Net. Hence, this zones can created either by drawing, or
importing from an external file. Several drawing tools are available, e.g. resizing,
adding points to the zones, removing a point. Moreover, these can be saved in external
files. Information on these zones is also very easy to reach (size and coordinates).
Note:
You may perform propagation calculations without geographic data (free space
propagation). Nevertheless, it is necessary to define a computation zone.
5-2
5.2.2 Computation and Focus Zones Effects
Computation and focus zones help you to reduce calculation area and calculation times.
They are applied on several items listed below.
I. Clutter classes or traffic statistics
Clutter classes, traffic, UMTS, CDMA/CDMA2000 environment statistics refer to the

focus zone if there is one. Only areas inside the focus zone are taken into account.
Note:
If not defined, the focus zone is the computation zone.
z Clutter classes
U-Net calculates the surface of each clutter class contained in the focus zone and its
percentage.
z Traffic
In UMTS or CDMA/CDMA2000 projects, statistics are available only in case of traffic
raster maps (traffic maps based on environments). U-Net works out surface of each
traffic class (environment) contained in the focus zone. For each of them, it provides
surface of each clutter class covered by the traffic class and its percentage.
In GSM/GPRS/EDGE projects, U-Net evaluates the surface of each traffic class
contained in the working zone and its percentage.
z UMTS and CDMA/CDMA2000 environments statistics
For each user profile described in the environment, U-Net calculates density of users
and the number of users on a clutter class. The density of users remains the same. On
the other hand, the number of users is related to the focus zone.
II. Path loss matrices
U-Net works out a path loss matrix for each active and filtered transmitter (or related
repeater) which at least a calculation radius intersects a rectangle containing the
computation zone. Only contents of the matrices inside the rectangle around the
computation zone are calculated.
III. Coverage studies
z Calculation and display

Coverage calculations are achieved by taking into account the computation zone.
U-Net checks coverage conditions on the areas inside the computation zone.
Therefore only bins contained in the computation zone will be covered.
5-3
Tip information on coverage is related to the computation zone. The focus zone has no
effect on tip contents.
z Statistics on UMTS and CDMA/CDMA2000 studies
To be taken into account, the focus zone must be defined before accessing study
statistics. It is not necessary to define it before computing coverage. When accessing
the Statistics tab (in the study Properties window), U-Net considers only covered areas
inside the focus zone. For each threshold value defined in the Display tab, it works out
the covered surface and its percentage. These data are evaluated for each
environment class, when using maps based environments as traffic cartography.
Note:
z Study reports
To be taken into account, the focus zone must be defined before accessing reports.
Reports are dynamically updated to take into account the focus zone without requiring
a coverage re-calculation. U-Net considers only covered surfaces inside the focus
zone. Therefore, in case of coverage by transmitter, only transmitters which coverage
intersects the focus zone can be considered in the report.
Note:
IV. UMTS and CDMA/CDMA2000 simulations
z Calculation
U-Net drops mobiles on the traffic area contained in the computation zone. During
power control, U-Net considers all the active and filtered transmitters which the
calculation radius intersects rectangle containing the computation zone.
z Simulation reports
To be taken into account, the focus zone must be defined before checking simulation
results (UMTS, CDMA/CDMA2000). It is not necessary to define it before calculating
simulation. When accessing the results of the simulation, only sites, transmitters and
mobiles located inside the focus zone are considered. The global output statistics are
based on these mobiles.
5-4
Note:
If not defined, the focus zone is the computation zone. The computation zone is not
used as filter. Therefore, all the transmitters with a calculation area, even those located
outside the computation zone, and all the created mobiles are analyzed in the
simulation results.
If the focus and computation zones are the same, only sites and transmitters located
inside the focus zone are dealt with in the simulation results.
z Display
All the mobiles even those outside the focus zone are represented on the map. U-Net
provides information for any of them, in tips and by left clicking on them.
V. Other calculation algorithms
Other calculation algorithms for allocating primary scrambling codes or PN Offsets,

neighbours, frequencies, BSIC or working out the number of requested TRXs take into
account all the active and filtered transmitters which the calculation radius intersects
rectangle containing the computation zone.
VI. Printing
You may print either the whole selected area or only the area inside the focus zone
when selecting the Erase outside of the focus zone option [File: Page setup command].
Note:
If the focus zone is not defined, U-Net will consider the computation zone instead of
focus zone.
5.2.3 Drawing a Computation/Focus Zone
To draw a computation or a focus zone, proceed as follows:
1) Select the Draw command from the Tools: computation (resp. focus) zone
menu in the menu bar.
2) Position the pointer (polygonal selection arrow) on the map.
3) Press the mouse left button (a first point is created).
4) Slide the pointer on the map and press the mouse left button to create another
point.
5) Carry out the two last steps until you draw the polygonal area you want.
6) Double click to close off the polygonal area.
5-5
The selected computation zone is delimited by a red line. The focus zone is delimited
by a green line and the background is lighter.
Note:
5.2.4 Creating a Computation/Focus Zone from Polygons
You can create a computation (resp. focus) zone from any polygon contained in a
vector object (created or imported). To do so, proceed as follows:
1) Right click on the polygon you want to become the computation (resp. focus)
zone to open the associated context menu.
2) Select the Use as computation (resp. focus) zone command from the available
scrolling menu.
5.2.5 Importing the Computation/Focus Zone from a File
As many other geo data objects, U-Net allows you to import the computation (resp.
focus) zone from a file with either an Autocad (.dxf), Arcview (.shp), MapInfo (.Mif), Agd
or PlaNET® format. The imported computation (resp. focus) zone takes the place of an
already existing one.
To import a computation (resp. focus) zone file, proceed as follows:
Either,
1) Select the Import... command from the Tools: computation (resp. focus) zone
Or,
1) Select the Import... command from the File menu in the menu bar.
Then,
1) Specify the directory where the file to be imported is located, the file name and
the file type in the open dialog box.
2) Press the OPEN button to validate.
window,
4) Select the computation (resp. focus) zone option from the Import to scrolling
menu.
5) If necessary, precise the coordinate system associated with the file being
currently imported.
6) Click the Import button to achieve the procedure.
5-6
Note:
z The drag and drop feature is available from any file explorer application to U-Net to
import the computation (resp. focus) zone,
z Any computation (resp. focus) zone must be a polygon,
z The Tools: computation (resp. focus) zone menu is available only if the map of the
project is currently displayed.
z 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.
5.2.6 Exporting the Computation/Focus Zone to a File
In U-Net, it is possible to export the computation (resp. focus) zone in order to make it
available in other applications/projects. This can be made in the Arcview (.shp),
MapInfo (.Mif) or Agd formats.
To export the current computation (resp. focus) zone to a file, proceed as follows:
1) Select the Save as... command from the Tools: computation (resp. focus) zone
2) Specify the path, the name and the format of the file to be exported.
3) Press the SAVE button to validate.
window.
5) If necessary, precise the coordinate system associated with the file being
currently exported.
6) Click the Export button to achieve the procedure.
Note:
z The Tools: computation (resp. focus) zone menu is available only if the map of the
project is currently displayed.
5.2.7 Deleting the Computation/Focus Zone
To delete the computation (resp. focus) zone, proceed as follows:

Either,
5-7
1) Left click on the red (resp. green) line (limit of the computation/focus zone). The
pointer becomes position indicator ( ).
2) Right click on this limit to open the associated context menu.
3) Select the Delete zone command from the open scrolling menu.
Or,
1) Choose the computation (resp. focus) zone: Delete command from the Tools
menu when the workspace is displayed on top.
5.2.8 Resizing the Computation/Focus Zone
To resize the computation (resp. focus) zone, proceed as follows:

3) Drag the pointer until its target location.
5.2.9 Moving a Point of the Computation/Focus Zone
To move an existing point of the computation (resp. focus) zone, proceed as follows:
1) Left click on the point of the computation zone limit (red line) you want to move.
The pointer becomes position indicator ( ).
3) Drag the pointer until the target location.
5.2.10 Adding a Point in the Computation/Focus Zone
To add a point to the computation (resp. focus) zone, proceed as follows:

1) Left click on the location on the computation zone limit (red line) you want to add
a point. The pointer becomes position indicator ( ).
3) Select the Insert point command from the open scrolling menu.
5.2.11 Removing a Point in the Computation/Focus Zone
To remove a point from the computation (resp. focus) zone, proceed as follows:
1) Left click on the point from the computation zone limit (red line) you want to
delete. The pointer becomes position indicator ( ).
3) Select the Delete point command from the open scrolling menu.
5-8
5.2.12 Displaying the Computation/Focus Zone Size
U-Net allows the user to read various information about any object through the tips.
Thus, it is possible to display information (here: area size) on the current
computation (resp. focus) zone. This can be made by the use the tips button , or
the properties window of the computation (resp. focus) zone.

Either
1) Rest the pointer on the red (resp. green) line (limit of the computation/focus
zone) except on the main points making up the computation zone until the
information appears.
Note:
Information about surface will appear only if the tips button is on.
Or,
1) Right-click on the computation (resp. focus) zone border.
2) Click on the properties... menu.
The properties window displays the size of the computation (resp. focus) zone.
5.2.13 Displaying the Computation/Focus Zone Coordinates
To display the coordinates of points composing the computation (resp. focus) zone,
proceed as follows:
Either,
3) Select the Properties command from the open scrolling menu.
4) The coordinates (in the defined display system) of the point composing the
computation (resp. focus) zone are then displayed in a table window.
Or,
1) Choose the computation (resp. focus) zone: Properties command from the
Tools menu when the workspace is displayed on top.
5-9
Advice:
To draw an appropriate computation/focus zone, you can copy a list of point
coordinates from a spreadsheet and paste it in the computation zone properties
window. The format of the data contained in the table is the following: X_coordinate
TAB Y_coordinate on each line. Inside this interface, TAB and Return commands are
available by using simultaneously the Ctrl key and the appropriate key. Coordinates are
displayed as defined previously.
5.3 Propagation Models

5.3.1 Propagation Models Overview
By computing losses along transmitter-receiver paths, propagation models permit to

predict the received signal level at a given point and take into account:
z The Radio data.
z The Geo data like DTM and/or clutter classes, according to the model.
The mechanisms involved in electromagnetic propagation are:
z Free space propagation
z Reflections
z Diffraction
z Scattering
All these mechanisms can be more or less taken into account by propagation models
depending on their complexity. U-Net provides, by default, some model based on
empirical approaches. For any type of project, you must find the best suited one.
Nevertheless, U-Net allows you to manage any project with several propagation
models. These can be assigned either globally or at the transmitter level. Each
transmitter may have a main propagation model (high resolution and short calculation
radius) and a secondary one, with a lower resolution, and an extended calculation
radius.
Some propagation models (Okumura-Hata and Cost-Hata) are based on a “model
type” principle. On the base of the formulae they offer, you can use these models to
develop customized models by duplicating the existing base model (Okumura-Hata
and Cost-Hata).
The Okumura-Hata, Cost-Hata, Longley-Rice, Standard propagation model and WLL
models available in U-Net are based on formulae whose parameters can be set.
Okumura-Hata and Cost-Hata in particular are based on one formula for each clutter
class.
5-10
The ITU 526-5 and ITU 370-7 (Vienna 93) models are deterministic and therefore their
parameters cannot be set.
Like other U-Net objects, propagation models can be easily managed.
Note:
When performing consecutive calculations with different thresholds:
z If no calculation radius has been defined, U-Net recalculates the complete coverage
for each prediction.
z If a relatively large calculation radius has been defined, U-Net "stores in memory"
the calculations for the defined area and only calculates the difference between the
two predictions.
5.3.2 Propagation Model General Information
I. Selecting propagation models
In U-Net, propagation models can be chosen at different levels. For this reason, you
must be very careful with the propagation models priority order given to the different
places where these models are defined.
U-Net is able to calculate two path loss matrices per transmitter, a first matrix over a
near radius computed with a high resolution and a propagation model, and a second
matrix over a far radius computed with a low resolution and another propagation model.
Note:
In addition, it is possible to differentiate resolution of path loss matrices from plot
resolution.
To define propagation model(s) simultaneously to all transmitters, proceed as

follows:
4) Click on the Propagation tab from the open window.
5) In the main matrix part, choose from the scrolling list a propagation model (with a
calculation radius and a resolution used to compute the main path loss matrix).
5-11
6) Optionally, in the extended matrix part, choose from the scrolling list a propagation
model (with a calculation radius and a resolution taken into account to calculate
the extended path loss matrix).
To define propagation model(s) to one transmitter at a time, proceed as follows:
2) Expand the Transmitters folder by left clicking on the button.
Either,
3) Right click on the transmitter to which you want to assign a specific propagation
model.
Or,
3) Double click on the transmitter to which you want to assign a specific propagation
model.
5) In the main matrix part, choose from the scrolling list a propagation model (with
a calculation radius and a resolution used to compute the main path loss matrix).
6) Optionally, in the extended matrix part, choose from the scrolling list a
propagation model (with a calculation radius and a resolution taken into account
to calculate the extended path loss matrix).
You can also define these parameters in the Transmitters table.
5-12
Note:
z The calculation radius limits the scope of the calculations to the radius that has been
defined. The calculation radius prevents the system from calculating over too long
distances (e.g. in an urban area). In the case of very large environments, the
calculation radius allows you to improve the calculation time. If no main calculation
radius has been defined (and no secondary propagation model), U-Net takes into
account automatically the prediction minimum threshold to define the calculation
radius for each transmitter. Nevertheless, this could drive to long calculation times
z Since it is a matrix (or 2 in case of extended calculation radius) which is computed
for each transmitter, the calculation radius represents the half side length of the
potential matrix located around the considered transmitter.
z U-Net computes an extended matrix only if the three parameters, propagation
model, calculation radius and resolution, are specified. Therefore, an extended
matrix will not be worked out if its resolution is null.
z U-Net computes at the same time the main and extended matrices of a transmitter
with a global management. Therefore, it will recalculate both matrices even if only
one is invalid.
To select a default propagation model on predictions, proceed as follows:

2) Right click on the Predictions folder to open the associated context menu.
5) Choose from the scrolling list a propagation model.
6) Enter the grid resolution.
current dialog window.
Note:
This selected model is taken into account only if the value of the main propagation
model (transmitter property) is (Default model).
II. Setting propagation model priority
Even if it is possible to choose a propagation model in the Predictions folder, priority

is given firstly to model(s) defined at the transmitter level (in any case, for either
coverage studies or point analysis predictions). In that next case, you can choose a
5-13
propagation model (and potentially a secondary one) for each transmitter. What is
then displayed as propagation model in the Transmitters folder properties is the
summary of what has been chosen for each independent transmitter.
For example, if you chose the same main propagation model X for each single
transmitter, X will be displayed as main propagation model in the Transmitters folder
properties. If you assign a main propagation model X to some transmitters and Y to
others, no main propagation model will be displayed in the Transmitters folder
properties (see Table 5-1).
Table 5-1 Propagation models
Model Frequency Take into Required Recommended

band account settings use
Longley-Rice ~ 40 MHz - Terrain - Calibration - Flat areas
(theoretical) profile - Very low
- Reflection frequencies
ITU 370-7 100 - 400 - Terrain - Percentage - Long distances

Vienna 93 MHz profile time while (d>10km)
real field > - Low frequencies
calculated
field
ITU 526-5 30 - 10.000 - Terrain Fixed receivers

(theoretical) MHz profile
- Diffraction
(3
knife-edge
Deygout
method)
WLL 30 - 10.000 - Terrain - Free space Fixed receivers

MHz profile loss > Microwave links
- - Receiver
Deterministi height and
c clutter clearance per
- Diffraction clutter
(3
knife-edge
Deygout
method)
Okumura-Hat 150 - 1.000 - Terrain - With 1 < d < 20 km

a MHz profile diffraction or > GSM 900
- Statistical not
>
clutter (at the - Urban loss + CDMA/CDMA200
receiver) correction 0
- 1 formula a(Hr)
per clutter
- Reflection
5-14
Model Frequency Take into Required Recommended

band account settings use
Cost-Hata 1.500 - - Terrain - With 1 < d < 20 km
2.000 MHz profile diffraction or > GSM 1800
- Statistical not
> UMTS
clutter (at the - Urban loss +
receiver) correction
- 1 formula a(Hr)
per clutter
- Reflection
Standard 150 - 2.000 - Terrain - With 1 < d < 20 km

Propagation MHz profile diffraction > GSM 900
Model - Statistical weight
> GSM 1800
clutter - K1, ..., K6
(single > UMTS
- Effective
antenna formula) >
height - LOS or CDMA/CDMA200
NLOS 0
differentiation (Automatic
- Loss per calibration
clutter with available)
clutter
weighting
- Receiver
clearance
Because of the priority given to the transmitters in term of propagation models, the one
displayed in the Predictions folder will be kept as reference for the complete project if
the (default model) value has been selected for all the transmitters in the network.
III. Displaying general information on propagation model
Under U-Net, the user interface is homogeneous for the different available propagation
models. Indeed, for all of them, a common General tab window is available. In this tab,
you may enter the model name, add some descriptions and check the model signature.
The model signature is used for validity purpose. A unique model signature is assigned
to each propagation model and its settings. When modifying model parameters, the
associated model signature is changed. This enables U-Net to detect potential path
loss matrix invalidity. In the same way, two identical propagation models in different
projects do not have the same model signature.
5-15
Note:
Model signature corresponds to the MODEL_ID field you can find in .par files when
externalising path loss matrices. Nevertheless, the real name of the used propagation
model is also explicitly written in .par files (TX_MODEL_NAME field).
IV. Choosing the appropriate propagation model
The different propagation models are more or less suited depending on the type of
project, radio and geographic data in use in the .atl current project. A summarized
description is given in the following table.
V. Managing propagation model folders
In the Modules tab, propagation models are organized in folders. That way, these items
are easy to manage like other objects. Hence it is easily possible to delete, duplicate,
copy and rename each of them.
To access the different managing properties of any propagation model, right click on the
model you want to manage to open the related context menu. Then choose among the
several available commands: delete, duplicate, copy, rename.
All newly created propagation models will then be available in the propagation model
selection boxes (Prediction or Transmitter properties).
The copy function can be useful to copy and paste a specifically tuned model in an atl
project to another one (considering the name does not already exist).
5.3.3 Working with Longley-Rice Model
The Longley-Rice is a theoretical model particularly suitable for predictions in the 40

MHz band in flat areas. This model uses the terrain profile to calculate propagation.
However, the Longley-Rice model parameters can be set in the form of a calibration
involving the distance and an additional loss value.
To manage the Longley-Rice model, proceed as follows:
1) Click the Modules tab in the Explorer window.
2) Expand the Propagation models by left clicking on the button.
Either,
3) Right click on the Longley-Rice subfolder to open the associated context menu.
Or,
3) Double click on the Longley-Rice subfolder.
4) Click on the Parameters tab.
5-16
5) Use the button to get a context-sensitive help on the displayed

window.
6) Define the loss parameters to be added to the model (in constant terrain, 0 values
means a signal linear decreasing as function of distance).”.dkm” is the distance (in
kilometres) from the transmitter.
7) Validate by clicking on Apply or OK.
5.3.4 Working with ITU 526-5 Model
The ITU 526-5 model is particularly suitable for predictions in the 30-10000 MHz band
at fixed receivers. It uses the terrain profile and the diffraction mechanism (3 knife-edge
Deygout method) to calculate path loss.
The ITU 526-5 recommendation considers that:
z If there are no obstacles, propagation will take place in free space ;
z If there is an obstacle, attenuation will be taken into account.
If there is an obstacle, attenuation will be caused on contact with the relief with
diffraction on the main peak (represented by a red line in the Profile tab of the point
analysis window). The main peak taken into account is the one that intersects the most
with the Fresnel ellipsoid. Any attenuation that occurs is then calculated between the
station and the main peak and between the main peak and the receiver. The result may
then show up to two new attenuation peaks in addition to the main peak. The various
peaks are identified by red lines. The attenuation generated by all the peaks is
displayed above the main peak.
To access the ITU 526-5 model properties box, proceed as follows:
Either,
3) Right click on the ITU526 subfolder to open the associated context menu.
Or,
3) Double click on the ITU526 subfolder.

window.
6) A dialog window opens in which you may choose or not to apply an empirical
tuneable corrective formula on the Deygout method.
5-17
5.3.5 Working with ITU 370-7 Model (Vienna 93)
The ITU 370-7 model follows the recommendations of the Vienna 1993 international
conference on telecommunications network coordination. This model is particularly
suitable for predictions in the 100-400 MHz band over long distances (d>10 km), such
as in Broadcast studies. It uses the terrain profile to calculate propagation.
Vienna 93 model parameter setting is limited to defining the percentage of time during
which the real field is higher than the signal level calculated by the model (1%, 10% or
50% of the time). The 50% value is usually used for coverage predictions, and 1% is
usually used for interference studies.
To access the ITU 370-7 model properties box, proceed as follows:
Either,
3) Right click on the ITU370 subfolder to open the associated context menu.
Or,
3) Double click on the ITU370 subfolder.

window.
6) Choose the appropriate time percentage for the current study.
Note:
When using this model, take care not to define cell edge coverage probability different
from 50%, or will be considered twice.
5.3.6 Working with WLL (Wireless Local Loop) Model
The WLL model is specially intended for "Radio Local Loop" applications in the
30-10000 MHz band. It is derived from the ITU 526-5 model from which it takes the
prediction algorithms while applying specific changes:
z The possibility of setting loss parameters dealing with free space propagation and
loss within the line of sight area only or not.
5-18
If the option ‘Line of sight only’ is not selected, U-Net computes the path loss on each
calculation bin, using formula defined in the dialog box.
If the option ‘Line of sight only’ is used, U-Net checks for each calculation bin if the
receiver is in the transmitter line of sight. Receiver is in the transmitter line of sight if
100% of the Fresnel half ellipsoid is cleared (no obstacle along the transmitter-receiver
profile).
If the receiver is in the transmitter line of sight, U-Net computes the path loss on each
calculation bin, using formula defined in the dialog.
When the receiver is not in the transmitter line of sight, U-Net considers that the path
loss tends towards infinite.
z The use of an “altimeter” clutter whose heights for different items (trees, buildings,
etc.) will be added to those for DTM.
z The possibility of defining a height and a receiver clearance associated with each
clutter class; (e.g. receiver on a building, etc.). These heights will be added to the
heights of the clutter.
z Adding notions of transmitter clearance.
Along the Tx-Rx profile, both ground altitude and clutter height are considered to
calculate diffraction losses. U-Net takes clutter height information in clutter heights file if
available in the .atl document. Otherwise, it considers average clutter height specified
for each clutter class in the clutter classes file description. If the .atl document does not
contain any clutter height file and no average height per clutter class is specified, U-Net
will consider ground altitude only.
You can define a clearance space around transmitters and receivers (20 metres by
default). This feature permits in particular to model streets in clutter areas.
Example: the clearance can be used to simulate streets in an area of buildings where
the clutter class file used does not show street detail.
To access the WLL model properties box, proceed as follows:
Either,
3) Right click on the WLL subfolder to open the associated context menu.
Or,
3) Double click on the WLL subfolder.

window.
6) Set the free space path loss prediction parameters.
5-19
7) Define an overall clearance for all the transmitters.

8) Define a default clearance for each receiver.
9) Define a height and clearance specific to the receiver for each clutter class. If, for a
given class, you have not defined any value, the default height will be used. This
land use part will be available only if the document contains a Land use folder.
5.3.7 Working with Okumura-Hata Model
I. Working with Okumura-Hata model overview
The Okumura-Hata is a model particularly suitable for predictions in the 150-1000 MHz
band over long distances (1 < d < 20km) and is very adapted to GSM 900, IS95 and
1xRTT technologies. This model uses the terrain profile, diffraction and reflection
mechanisms in order to calculate propagation.
Hata models are well adapted to urban environment. Nevertheless, in order to make
them available in a wide range of environments, it is possible to define several
corrective formulas, and to associate each one to each clutter class available in the
project. Furthermore, it is also possible to define a default formula used when no land
use data is available.
II. Considering losses due to diffraction (Okumura-Hata)
Okumura-Hata is able to take into account or not diffraction mechanisms by using a 1-knife edge
Deygout method.
To compute losses due to diffraction in the total path loss, proceed as follows:
Either
3) Right click on the Okumura-Hata subfolder to open the associated context
menu.
Or
3) Double click on the Okumura-Hata subfolder.
4) Click on the Configuration tab.

window.
6) Choose from the dedicated scrolling menu to take into account (1) or not (0) losses
due to diffraction.
5-20
III. Defining an environment default formula (Okumura-Hata)
U-Net takes into account that even if you do not have a clutter file or clutter data
missing, it is possible to use the Okumura-Hata model. To achieve this, you may define
a default type formula to be assigned to the undefined zones.
To select the environment default formula, proceed as follows:
Either
menu.
Or

window.
6) Choose from the dedicated scrolling menu one of the available formulas (tuneable
by accessing the Formulas dialog box) to assign to undefined zones.
IV. Assigning environment formulas to clutter types (Okumura-Hata)
When environment formulae and clutter data are available for the current project, you
need to assign to each detected clutter class a type of formula, in order to make this
model valid for a wide range of media.
To configure clutter types with available formulae, proceed as follows:
Either
menu.
Or

window.
5-21
6) Select in the scrolling lists cells from the Formula column the clutter-formula
associations.
Note:
Without this association, the Okumura-Hata model, which uses the clutter classes, will
be unable to correctly perform prediction calculations. The default formula will be used
on all clutter classes.
V. Creating/Modifying environment formulas (Okumura-Hata)
To create/modify an environment formula:

Either
menu.
Or
Then
2) Click on the button to open the associated dialog box.

window.
4) Adjust formula types and coefficients depending on the considered environment
type.
5) Validate by clicking on OK.
5.3.8 Working with Cost-Hata Model
I. Working with Cost-Hata model overview
The Cost-Hata is a model particularly suitable for predictions in the 1500-2000 MHz
band over long distances (1 < d < 20km) and is very adapted to DCS 1800 and UMTS
technologies. This model uses the terrain profile, diffraction and reflection
mechanisms in order to calculate propagation.
5-22
Hata models are well adapted to urban environment. Nevertheless, in order to make
them available in a wide range of environments, it is possible to define several
corrective formulas, and to associate each one to each clutter class available in the
open project. Furthermore, it is also possible to define a default formula used when no
land use data will be available.
II. Considering losses due to diffraction (Cost-Hata)
Cost-Hata is able to take into account or not diffraction mechanisms by using a 1-knife edge
Deygout method.
To compute losses due to diffraction in the total path loss, proceed as follows:
Either
3) Right click on the Cost-Hata subfolder to open the associated context menu.
Or
3) Double click on the Cost-Hata subfolder.
Then

window.
3) Choose from the dedicated scrolling menu to take into account (1) or not (0) losses
due to diffraction.
III. Defining an environment default formula (Cost-Hata)
U-Net takes into account that even if you do not have a clutter file or clutter data
missing, it is possible to use the Cost-Hata model. To achieve this, you may define a
default type formula to be assigned to the undefined zones.
To select the environment default formula, proceed as follows:
Either
Or
5-23
Then

window.
3) Choose from the dedicated scrolling menu one of the available formulas (tuneable
by accessing the Formulas dialog box) to assign to undefined zones.
IV. Assigning environment formulas to clutter types (Cost-Hata)
When environment formulae and clutter data are available for the current project, you
need to assign to each detected clutter class a type of formula, in order to make this
model valid for a wide range of media.
To configure clutter types with available formulae, proceed as follows:
Either
Or
Then

window.
3) Select in the scrolling lists cells from the Formula column the clutter-formula
associations.
Note:
Without this association, the Cost-Hata model, which uses the clutter classes, will be
unable to correctly perform prediction calculations. The default formula will be used on
all clutter classes.
5-24
V. Creating/Modifying environment formulas (Cost-Hata)
To create/modify an environment formula:

Either
Or
Then
2) Click on the button to open the associated dialog box.

window.
4) Adjust formula types and coefficients depending on the considered environment
type.
5.3.9 Working with Standard Propagation Model
I. Working with Standard Propagation model overview
The Standard Propagation Model is a model (deduced from the Hata formulae)
particularly suitable for predictions in the 150-2000 MHz band over long distances (1 <
d < 20km) and is very adapted to GSM 900/1800, UMTS and CDMA/CDMA2000
technologies. This model uses the terrain profile, diffraction mechanisms (calculated in
several ways) and takes into account clutter classes and effective antenna heights in
order to calculate path loss. An automatic calibration tool is available.
The model may be used for any technology. It is based on the following formula:
( )
 K1 + K 2 log(d ) + K 3 log HTxeff + K 4 × Diffraction + 
PR = PTx −  
 ( eff
)
 K 5 log(d ) × log H Rx + K clutter f (clutter ) + K hill ,LOS 

With (see Table 5-2):
Table 5-2 Parameters
Parameters Description
PR received power (dBm)
5-25
Parameters Description
PTx transmitted power (EIRP) (dBm)
K1 constant offset (dB)
K2 multiplying factor for log(d)
d distance between the receiver and the
transmitter (m)
K3 multiplying factor for log(HTxeff)
HTxeff effective height of the transmitter antenna

(m)
K4 Multiplying factor for diffraction calculation.
K4 has to be a positive number
Diffraction losses due to diffraction over an obstructed

path (dB)
K5 multiplying factor for log(HTxeff)log(d)

K6 multiplying factor for HRxeff
H Rxeff mobile antenna height (m)
Kclutter multiplying factor for f(clutter)

f(clutter) average of weighted losses due to clutter
K(hill,los) corrective factor for hilly regions (=0 in case
of NLOS)
All of these parameters are user-definable in the Standard Propagation Model

Properties window consisting in 4 tabs (General, Parameters, Clutter, and Calibration).
See typical values for SPM formula parameters and SPM recommendations
II. Accessing Standard Propagation Model properties
Users cannot access the internal formula of the Standard Propagation Model.
Nevertheless, you may set all its parameters in the Parameters and Clutter tab
windows from the SPM properties dialog box.
To access the Standard Propagation Model properties box, proceed as follows:
Either
3) Right click on the SPM subfolder to open the associated context menu.
Or
5-26
3) Double click on the SPM subfolder.

Then
1) A dialog window opens.
2) Select the tab according the way you want to adjust model parameters.
See typical values for SPM formula parameters and SPM recommendations.
III. Adjusting Standard Propagation Model parameters
You may adjust the parameters contained in the SPM base formula by using both the
General and the Clutter tab windows from the SPM properties box.
Excepting for the loss and clearance per clutter class (defined in the Clutter tab
window), all parameters (including the Diffraction terms) are user-definable in the
Parameters tab window.
Moreover, in 5 cases, user has to select his choice in scrolling menus:
z Effective antenna height determination method.
z Diffraction calculation method (Deygout, Epstein-Peterson, Deygout with
correction, Millington).
z The Profiles cell: if you select the radial option, U-Net establishes a profile
between each transmitter and each point located on its calculation perimeter
(user-defined by the calculation radius) and then, uses the nearest profile to make
a prediction on a point inside the calculation perimeter (radial optimisation).
When choosing the systematic option, U-Net systematically determines a profile
between each transmitter and any points in its calculation area. To avoid longer
calculation times, it is recommended to choose the radial option.
z Corrective term for hilly regions.
z The Grid calculation method. You can perform the calculations either at the
centre (centred option) or in the bottom left corner (bottom left option) of each grid.
For all the other parameters, user may enter directly the appropriate values directly in
the associated boxes.
See typical values for SPM formula parameters and SPM recommendations.
5.3.10 Working with Standard Propagation Model Recommendations
Beware that the clutter influence may be taken into account in two terms, Diffraction
loss and f(clutter) at the same time. To avoid this, we advise:
z Not to consider clutter heights to evaluate diffraction loss over the
transmitter-receiver profile if you specify losses per clutter class.
This approach is recommended if the clutter height information is statistical.
Or
5-27
z Not to define any loss per clutter class if you take clutter heights into account in the
diffraction loss.
In this case, f(clutter)=0. Losses due to clutter are only taken into account in the
computed Diffraction loss term.
This approach is recommended if the clutter height information is either
semi-deterministic or deterministic.
In case of semi-deterministic clutter information, specify receiver clearance (m) per
clutter class. Both ground altitude and clutter height are considered along the whole
transmitter-receiver profile except over a specific distance around the receiver
(clearance), where U-Net proceeds as if there was only the DTM map. The clearance
information is used to model streets.
Clearance definition is not necessary in case of deterministic clutter height information.
Clutter height information is accurate enough to be used directly without additional
information such as clearance. Here, losses due to clutter are taken into account in the
computed Diffraction loss term.
I. SPM General tab window
The SPM General tab window is shown in following Figure 5-1.
Figure 5-1 SPM General tab window
When open, use the button to get a context-sensitive help on the

available fields.
5-28
II. SPM Parameters tab window
The SPM General tab window is shown in following Figure 5-2.
Figure 5-2 SPM Parameters tab window
When open, use the button to get a context-sensitive help on the

available fields.
This tab manages parameters from the Standard Propagation model base formula.
In the Near transmitter and Far from transmitter parts, specify the maximum
distance, max distance, and four (K1, K2) sets (two sets per part).
Max distance is a maximum distance from transmitter. When d (distance between
receiver and transmitter) is inferior to this distance, the receiver is considered near
transmitter. On the other hand, if d is greater than the maximum distance, the receiver
is considered far from transmitter.
Two (K1, K2) sets, (K1, K2)los and (K1, K2)nlos, are defined in each part. They enable to
differentiate the case where the receiver is in the transmitter line of sight path (los index)
or is not (nlos index).
Therefore, the (K1, K2) sets taken into account in prediction calculations will depend on
d and visibility.
5-29
In the Effective antenna height part, define the HTxeff calculation method, the
minimum and maximum distances (distance min and distance max) and K3 factor.
HTxeff may be calculated with six different methods.
Note:
Distance min and distance max are set to 3000 and 15000 m according to ITU
recommendations and to 0 and 15000 m according Okumura recommendations.
These values are only used in two methods of effective antenna height calculation and
have different meanings according to the method.
In the Diffraction part, specify which method you want to use for calculating the
Diffraction term and K4 factor.
Four different methods (Deygout, Epstein-Peterson, Deygout with correction and
Millington) are available.
z These diffraction calculation methods are based on the General method for one
or more obstacles described in ITU 526-5 recommendations.
z Along the transmitter-receiver profile, both ground altitude and clutter height are
considered. U-Net takes clutter height information in clutter heights file if available
in the .atl document. Else, it considers average clutter height specified for each
clutter class in the clutter classes file description. If the .atl document does not
contain any clutter height file and no average height per clutter class is specified,
U-Net will consider ground altitude only.
z Finally, the calculations take earth curvature into account via the effective Earth
radius concept.
In the Other parameters part, specify the values for K5, K6, Kclutter and hilly terrain
corrective factor. Enter 1 or 0 to respectively take it into account or not. In the
calculation profile, if you select the radial option, U-Net establishes a profile between
each transmitter and each point located on its calculation perimeter (user-defined by
the calculation radius) and then, uses the nearest profile to make a prediction on a point
inside the calculation perimeter (radial optimisation). On the other hand, when
choosing the systematic option, U-Net systematically determines a profile between
each transmitter and any points in its calculation area.
5-30
Note:
To avoid longer calculation times, choose the radial option.
Finally, you can perform the calculations at the centre (centred option) or in the bottom
left corner (bottom left option) of each grid.
To select a method (in Effective antenna height and Diffraction parts)
z Right click on the method line and then, on the arrow on the extreme right side.
z Choose a method in the list.
Note:
Default values have been assigned to multiplying factors. The default values
correspond to the quasi-open Okumura-Hata formula valid for a 935 MHz frequency.
(See Sample values for SPM formula parameters).
III. Transmitter effective antenna height SPM
HTxeff may be calculated with five different methods (see Table 5-3).
Table 5-3 HTxeff Calculated Methods
Method Description
Transmitter antenna height above the ground (HTx in m).
Height above ground
HTxeff = HTx
The transmitter antenna height is determined in relation to

an average ground height calculated along a profile
between transmitter and receiver. The profile length
depends on distance min and distance max values and is
limited by the transmitter and receiver locations. Distance
min and distance max are respectively minimum and
maximum distances from transmitter.
HTxeff = HTx + (H 0Tx − H 0 )
Height above average where,
profile
H0Tx is the ground height (ground elevation) above sea
level at transmitter (m).
H 0 is the average ground height above sea level along
the profile (m).
Note:
z If the profile is not located between the transmitter and
the receiver, HTxeff equals HTx.
5-31
Method Description
The transmitter antenna height is calculated using the
ground slope at receiver.
HTxeff = (HTx + H 0Tx ) − (H Rx + H 0Rx ) + K × d
where,
H Rx is the receiver height above the ground (m).
H 0Rx is the ground height (ground elevation) above sea

Slope at receiver
level at receiver (m).
between 0 and distance
min K is the ground slope calculated over a user-defined
distance (Distance min). In this case, Distance min is a
distance from receiver.
Furthermore, this method gets computed height values
only between 20 and 200m.
If the original computed HTxeff is less than 20m, then the
output HTxeff becomes 20m.
If the original computed HTxeff is greater than 200m, then
the output HTxeff becomes 200m.
If Hotx > Horx then

HTxeff = HTx + (H 0Tx − H 0Rx )
Spot Ht
If Hotx <= Horx then
HTxeff = HTx
Abs Spot Ht: HTxeff = HTx + H 0Tx − H 0Rx
Note:
Distance min and distance max are set to 3000 and 15000 m according to ITU
recommendations and to 0 and 15000 m according Okumura recommendations.
These values are only used in the two last methods and have different meanings
according to the method.
Enhanced slope at receiver is shown in following Figure 5-3.
5-32
Figure 5-3 Enhanced slope at receiver:
Let x-axis and y-axis respectively represent positions and heights. We assume that
x-axis is oriented from transmitter (origin) to receiver.
This calculation is achieved in several steps:
1) U-Net determines line of sight between transmitter and receiver.
The LOS line equation is:
(( +
LOS (i ) = (H 0Tx + H Tx ) − H 0Tx H Tx
) − (H 0Rx + H Rx )) ⋅ Re s ⋅ i
d
where,
H0Tx is the ground height above sea level at transmitter (m).
HTx is the transmitter antenna height above the ground (m).
HoRx is the ground height above sea level at receiver (m).
HRx is the receiver antenna height above the ground (m).
d is the distance between transmitter and receiver (m).
i is the point index.
Res is the profile resolution (distance between two points).
2) U-Net extracts the transmitter-receiver terrain profile.
3) Hills and mountains are already taken into account in diffraction calculations.
Therefore, in order for them not to unfavourably influence the regression line
calculation, U-Net filters the terrain profile.
U-Net calculates two filtered terrain profiles, one established from transmitter and
another from receiver. It determines filtered height of every profile point. Profile points
are evenly spaced on the basis of profile resolution. To determine filtered terrain height
at a point, U-Net evaluates ground slope between two points and compares it with a
threshold set to 0.05; three cases are possible.
Some notations defined hereafter are used in next part.
Hfilt is the filtered height.
5-33
Horig is the corrected original height. Original terrain height is determined from extracted
ground profile and corrected by considering Earth curvature.
- Filter starting from transmitter
Let us assume that Hfilt-Tx(Tx) = Horig(Tx)
For each point, we have three different cases:
1st case: If
(H orig (i ) − H orig (i − 1)) ≤ 0.05

H orig (i ) > H orig (i − 1) and Re s ,
Then,
( )
H filt −Tx (i ) = H filt −Tx (i − 1) + H orig (i ) − H orig (i − 1)
2nd case: If
(H orig (i ) − H orig (i − 1)) > 0.05

H orig (i ) > H orig (i − 1) and Re s
Then,
H filt −Tx (i ) = H filt −Tx (i − 1)
3rd case: If
H orig (i ) ≤ H orig (i − 1)
Then,
H filt −Tx (i ) = H filt −Tx (i − 1)
If
H filt (i ) > H orig (i ) additionally
Then,
H filt −Tx (i ) = H orig (i )
- Filter starting from receiver

Let us assume that Hfilt(Rx)=Horig(Rx)
For each point, we have three different cases:
1st case: If
5-34
(H orig (i ) − H orig (i + 1)) ≤ 0.05

H orig (i ) > H orig (i + 1) and Re s ,
Then,
(
H filt − Rx (i ) = H filt − Rx (i + 1) + H orig (i ) − H orig (i + 1))
2nd case: If
(H orig (i ) − H orig (i + 1)) > 0.05

H orig (i ) > H orig (i + 1) and Re s
Then,
H filt − Rx (i ) = H filt − Rx (i + 1)
3rd case: If
H orig (i ) ≤ H orig (i + 1)
Then,
H filt − Rx (i ) = H filt − Rx (i + 1)
If
H filt (i ) > H orig (i ) additionally
Then,
H filt − Rx (i ) = H orig (i )
Then, for every point of profile, U-Net compares the two filtered heights and chooses
the greatest one.
H filt (i ) = max (H filt −Tx (i ), H filt − Rx (i ))
4) U-Net determines the influence area, R. It corresponds to the distance from

receiver at which the original terrain profile plus 30 metres intersects LOS line for
the first time (when beginning from transmitter).
The influence area must satisfy additional conditions:
R = 3000 m,
R ≥ 0.01 ⋅ d ,
R must contain at least three bins.

5-35
Note:
z 1. When several influence areas are possible, U-Net chooses the highest one.
z 2. If d < 3000m, R = d.
5) U-Net performs a linear regression on the filtered profile within R in order to

determine a regression line.
The regression line equation is:
y = a⋅x +b
∑ (d (i ) − d
i
m ) ⋅ (H filt (i ) − H m )
a=
∑ (d( i ) − d )
2
m
i and b = H m − a ⋅ d m
where,
∑H
1
Hm = ⋅ filt (i )
n
i
i is the point index. Only points within R are taken into account.
R
dm = d −
2
d(i) is the distance between i and transmitter (m).
Then, U-Net extends the regression line to transmitter location. Therefore, its equation
is:
regr (i ) = a ⋅ (i ⋅ Re s ) + b
6) Then, U-Net calculates effective transmitter antenna height, H Txeff (m).
H 0Tx + H Tx − b
H Txeff =
1+ a 2
If HTxeff is lower than 20m, U-Net recalculates it with a new influence area, which begins
at transmitter.
5-36
Note:
z In case H Txeff > 1000m , 1000m will be used in calculations.

z If HTxeff is still lower than 20m, an additional correction is taken into account (7th
step).
7) If HTxeff is still lower than 20m (even negative), U-Net evaluates path loss using
HTxeff = 20m and applies a correction factor.
Therefore, if
H Txeff < 20m ,
L path = L path (H Txeff = 20m, d , f ) + K lowant
where,
d 20 ⋅ (1 − (H Txeff − 20 ))
K lowant = − 0.3 ⋅ (H Txeff − 20 ) −
5  d   d 
10  9.63 +  ⋅  6.93 + 
 1000   1000 
f is the frequency (MHz).
IV. Diffraction computation in SPM
This feature is available in the General tab window from the SPM properties box.
In the Diffraction part, user has to define calculations method for the Diffraction term
and K4 factor. These diffraction calculation methods are based on the General method
for one or more obstacles described in ITU 526-5 recommendations. The calculations
take earth curvature into account via the effective Earth radius concept.
Four different methods (Deygout, Epstein-Peterson, Deygout with correction and
Millington) are available.
In order to define precisely the diffraction profile, a clearance per clutter class must be
defined. To do so, enter the appropriate values in the Clutter tab window from the SPM
properties box in cells just left to the clutter classes ones.
V. Deygout
The Deygout construction (as shown in Figure 5-4), limited to a maximum of three
edges, is applied to the entire profile from transmitter to receiver. A straight line
between transmitter and receiver is drawn and the heights of obstacles above this line,
hi, are calculated. The obstruction positions, di, are also recorded. From these data, νi
are evaluated. The point with the highest ν value is termed the principal edge, p, and
5-37
the corresponding loss is J(νp). Then, the construction is applied twice, from transmitter
to point p to obtain νt and J(νt) and from point p to receiver to obtain νr and J(νr).
Point p
Point t
ht Point r
hp
hr
Ht+H0t
Sea level
Hr+H0r
T R
Figure 5-4 Deygout construction
Note:
The calculation formulas are detailed in ITU 526-5 recommendations.
The Deygout with correction (ITU 526-5) method is based on the Deygout construction
plus an empirical correction, C.
Therefore,
If ν p > 0 , we have Diffraction loss = J (ν p ) + J (ν t ) + J (ν r ) +C
Else
Diffraction loss = J (ν p ) + C
Note:
In case of ITU 526-5 propagation model, Diffraction loss term is determined as follows:
If ν p > −0.78 , we have Diffraction loss = J (ν P ) + t ⋅ (J (ν t ) + J (ν r ) + C )
Where,
 J (ν p ) 
t = min ,1
 6 
C = 8.0 + 0.04d
(d, the distance between transmitter and receiver, stated in km)
5-38
Else
Diffraction loss = 0
VI. Epstein-Peterson
The Epstein-Peterson construction (as shown in Figure 5-5) is limited to a maximum

of three edges. First, the Deygout construction is applied to determine the three main
edges over the whole profile. Then, the main edge height, hp, is recalculated;
according to the Epstein-Peterson construction, hp is the height above a straight
line between t and r points. The main edge position dp is recorded and hence, from
these data, νp and J(νp) are evaluated.
Point p
Point t
hp
ht Point r
hr
Ht+H0t
Sea level
Hr+H0r
T R
Figure 5-5 Epstein-Peterson construction
In this method, same calculation formulas are used to define h, ν and J(ν).
VII. Millington
The Millington construction (as shown in Figure 5-6), limited to a single edge, is
applied over the whole profile. Two horizon lines are drawn at transmitter and at
receiver. A straight line between transmitter and receiver is defined and the height
of intersection point between the two horizon lines above the straight line, hh, is
calculated. The position dh is recorded and then, from these values, νh and J(νh) are
evaluated using same formulas than previously.
Point h
hh
Ht+H0t
Sea level
Hr+H0r
T R
Figure 5-6 Millington construction

5-39
Note:
If you select no diffraction, the Diffraction term equals zero and is not taken into account
in calculations.
VIII. Receiver effective antenna height
In the Standard Propagation Model, the receiver effective antenna height is estimated
as following:
H Rxeff = (H Rx + H 0Rx ) − H 0Tx
where,
HRx is the receiver antenna height above the ground (m).
H 0 Rx is the ground height (ground elevation) above sea level at the receiver (m).
H 0Tx is the ground height (ground elevation) above sea level at the transmitter (m).
Note:
The calculation of effective antenna heights ( HRxeff and HTxeff ) is based on extracted
DTM profiles. They are not properly performed if you have not imported heights (DTM
file) beforehand.
IX. Sample values for SPM formula parameters
Here are some orders of magnitudes for the different parameters composing the
Standard Propagation Model formula (see Table 5-4)
Table 5-4 K Parameters
Min Typical Max

K1 Variable Variable Variable
K2 20 44.9 70
K3 -20 5.83 20
K4 0 0.5 0.8
5-40
Min Typical Max

K5 -10 -6.55 0
K6 -1 0 0
Concerning the parameter K1, this really depends on the frequency, and so, on the
technology type. Here are some examples (see Table 5-5):
Table 5-5 K1 Value
Project type Frequency (MHz) K1

GSM 900 935 12.5
GSM 1800 1805 22
GSM 1900 1930 23
UMTS 2110 23.8
1xRTT 900 12
Since K1 is a constant, its value is strongly dependant on the values given to losses per
clutter class (if needed)
X. Correction for hilly regions
An optional corrective term Khill,LOS is proposed in the SPM Parameters tab to correct
path loss for hilly regions when transmitter and receiver are in LOS. Khill,LOS is
determined in three steps. Steps to achieve are related to the previous ones: influence
area, R, and regression line are supposed available.
1) For every profile point within influence area, U-Net calculates height deviation
between the original terrain profile (with Earth curvature correction) and
regression line. Then, it sorts points according to the deviation and draws two lines
(parallel to the regression line), one which is exceeded by 10% of the profile points
and the other one by 90%.
2) U-Net evaluates the terrain roughness, h; it is the distance between the two lines.
3) U-Net calculates Khill,LOS.
We have
K hill,LOS = K h + K hf
If
0 < ∆h ≤ 20 m , K h = 0
Else
5-41
K h = 7.73 log (∆h ) − 15.29 log(∆h ) + 6.746

2
If
0 < ∆h ≤ 10 m , K hf = −2 ⋅ 0.1924 ⋅ (H 0Rx + H Rx − regr (i Rx ))
Else
(
K hf = −2 ⋅ − 1.616 log (∆h ) + 14.75 log(∆h ) − 11.21 ⋅
2
)H 0Rx + H Rx − regr (i Rx )
∆h
iRx is the point index at receiver.
5.3.11 SPM Clutter Tab Window
Figure 5-7 SPM Clutter tab window
When open (as shown in Figure 5-7), use the button to get a
context-sensitive help on the available fields.
In this tab, you may define the average of weighted losses due to clutter, f(clutter).
n
f (clutter ) = ∑ Li w i
i =1
where
L: loss due to clutter.
5-42
w: weight.
n: number of points taken into account over the profile.
The losses due to clutter are evaluated over a maximum distance from receiver,
Max distance. Each clutter class is assigned specific loss, Loss per clutter class. The
losses are calculated from ground and clutter heights. The weighting function
enables to give a weight to each point (see Table 5-6).
Table 5-6 Weighting function
Uniform weighting function: Logarithmic weighting function:

1 d 
wi = log i + 1
n D 
wi =
n dj 
∑ log + 1
j =1 D 
Exponential weighting Triangular weighting function:
function: di
di
wi = n
wi =
e D
−1 ∑d
j =1
j
n dj
∑e
j =1
D
−1 d i = D − d i' where d’i is the distance between the
receiver and the i point.
To select the weighting function

1) Right click on the weighting function line and then, on the arrow.
2) Choose a function type in the list.
See SPM Recommendations.
I. Typical values or losses per clutter class (SPM)
Table 5-7 Losses per clutter class
Losses per clutter class

Dense urban from 4 to 5
Woodland from 2 to 3
Urban 0
Suburban from -5 to -3
Industrial from -5 to -3
Open in urban from -6 to -4
Open from -12 to -10
Water from -14 to -12
5-43
These values (see Table 5-7) have to be entered only when considering statistical
clutter class maps only.
Note:
The Standard Propagation Model is deduced from the Hata formulae, valid in the case
of an urban environment. The values above are consistent since 0 dB is indicated from
an urban clutter class, positive values for more dense clutter classes, and negative
values for less dense clutter classes.
5.3.12 SPM Calibration Tab Window
Figure 5-8 SPM Calibration tab window
When open (as shown in Figure 5-8), use the button to get a
context-sensitive help on the available fields.
In this tab, you may statistically analyse difference between predictions and CW
measurements (Click on the Statistics.... button) and perform an automatic model
calibration (Click on the Calibrate... button) from CW measurement survey.
Choose in the list the CW measurement paths you want to use. In the Filter part, you
may select the CW measurement points to be taken into account in statistics and for
the model calibration by specifying distance and CW measurement intervals, los
5-44
(CW measurement points in the transmitter line of sight) and nlos (CW measurement
points which are not in the transmitter line of sight) options.
Note:
Statistical analysis and calibration cannot be performed without CW measurement
survey.
I. Displaying statistics before calibration (SPM)
This feature is available in the Calibration tab window from the SPM properties box.
With this, you may statistically analyse difference between predictions and an existing
CW measurement survey.
To statistically compare CW measurements with prediction results, left click on the
Statistics... button. The study is carried out on the CW measurement points which
check filter criteria. The report window is displayed:
All parameters defined in General and Clutter tabs are summarized in the Model
parameter part: the formulas used for calculations depending on visibility and distance
from transmitter, the algorithms for evaluating Diffraction and HTxeff terms and the
losses per clutter classes.
In the Global statistics part, the number of CW measurement points which check filter
criteria (Num points), the average value (Mean), the standard deviation (Std deviation),
minimum (Min) and maximum (Max) values are evaluated for data like error, error
(LOS), error (NLOS), log(d), log(HTxeff), Diff, log(d)log(HTxeff) and HRxeff.
The difference between experimental (CW measurement) and theoretical (prediction)
values (named Error), is calculated on the whole path. On the other hand, Error (LOS)
is only calculated from points in transmitter line of sight path and Error (NLOS) takes
into account points which are not in transmitter line of sight path. Other data (log(d),
log(HTxeff), Diff, log(d)log(HTxeff) and HRxeff) are calculated on the whole path.
In the Statistics per clutter classes part, Num points, Mean and Std deviation on error
are detailed per clutter classes.
Finally, the correlation matrix is specified.
II. Calibrating the Standard Propagation Model
This feature is available in the Calibration tab window from the SPM properties box.
With this, you may perform an automatic model calibration from an existing CW
measurement survey.
5-45
Choose in the list the CW measurement paths you want to use. In the Filter part, you
may select the CW measurement points to be taken into account in statistics and for the
model calibration by specifying distance and CW measurement intervals, los (CW
measurement points in the transmitter line of sight) and nlos (CW measurement points
which are not in the transmitter line of sight) options.
Note:
Statistical analysis and calibration cannot be performed without CW measurement
survey.
From a selected CW measurement session, you may either display statistics on

comparison with the current propagation model or choose to calibrate this model in
order to check its results to the CW measurements.
To calibrate the model, press the Calibrate... button. The Calibration window is open.
The calibration is carried out on the CW measurement points which check filter criteria
using the linear regression method.
The variables (cste, clutter, log(d), log(HTxeff), Diff, log(d)log(HTxeff), HRxeff) to be
calibrated, the corresponding correlation coefficients (except for cste and clutter which
are constant) and the corrections to be made on Ki initial factors to take into account the
calibration are listed in a table.
You may compare the average error (Mean) and the error standard deviation (Std
deviation) before (initial statistics) and after (current statistics) calibrating the model.
To achieve the model calibration, right click one or several variables (using shift and/or
Ctrl button at the same time) and then, press Identify button. The calibration will be
achieved when the current Mean and Std deviation values and hence, all correlation
coefficients are as close to zero as possible.
When selecting a specific variable, you may see, in the right small window, the
correlation between error and this variable.
Note:
The abscissa of the regression line is not the prediction level, but the value of the
variable you select in the left part of the window (e.g. Log(D)). The abscissa begins
from the min value found in the measurement path until the max value found in the
measurement path. The ordinate is the error corresponding to the related
measurement point.
5-46
Hence, the regression line represents the correlation between the error and the
selected variable. Moreover, the regression line is calculated by using all the points, so
there is no average point.
When the correlation coefficient is close to one, a straight line can be drawn from the
points: the error is strongly dependent on the variable. On the other hand, when the
correlation coefficient is close to zero, the points are scattered around the straight line:
there is no correlation between the error and the variable. It means that if the variable if
modified, this will not improve the error. In that case, there will be no use calibrating this
variable.
When all the variables are selected, identification is processed for each variable from
the most correlated to the less correlated to error. In that case, no regression line is
displayed (U-Net cannot show variation of 2 variables at the same time).
To recover the initial data before calibration, press Reinitialise button.
To validate the calibration, press OK. The corrections will be added to Ki factor values.
Note:
K1 and K2 factors are the same for near and far options.
Important comment:
z Model automatic calibration solution is a mathematical solution. Before committing
results, ensure of their relevance towards a physical and realistic solution. See
Typical values for Standard Propagation Model formula parameters
z 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.
See also (to calibrate 1 variable - to calibrate several variables).
III. To calibrate one variable
Let us consider the scatter of CW measurement points depending on their calculation

values for a given variable (Figure 5-9).
5-47
ERROR (measurement – prediction)
Regression line
calculated
values for the
variable
Figure 5-9 Calibrate one variable
If the regression line (where the sum of square differences is minimised) is:
y = ax + b
It is easy to prove that:
a=
∑ XY
∑X 2
where
X = xi − x
and
Y = yi − y
with b = −ax + y
When a variable is calibrated, the new value of the coefficient Ki is equal to a and the
constant value is equal to b. The coefficients are effectively affected to the model by
clicking on OK. b is generally not null, that is why Cste is often set when
identifying a variable.
Caution:
The Correction column means the difference between the new value and the current
value of the model for each coefficient.
The correlation equals to:
r =
∑ XY
∑ X ∑Y
A correlation is considered satisfying when its absolute value is closed to 1. When it is
not the case, the resulting correction may be unstable and so not reliable.
Once the variable has been calibrated (after pushing the Identify button), a correction is
suggested and the correlation is then set to zero because the differences between CW
measurements and predictions are no longer dependent on the calculated values.
Once the identification is processed, the correlation graphic becomes (Figure 5-10):
5-48
ERROR (measurement – prediction)
Regression line
calculated values
for the variable
Figure 5-10 Correlation
IV. To calibrate several variables
We can generalise the regression line for a set of N coefficients:
 x0 
 
y = [a0 Κ aN ] ×  Μ
 x N 
We can prove by the same mean:
 ∑ X 02 ∑X X 0 1 Κ ∑X X N   a0   ∑ X 0Y 
0
     
 ∑ X 0 X1 ∑X  ×  a1  =  ∑ X 1Y 
2
1
 Μ Ο   Μ  Μ 
     
∑ 0 X N
X Λ Κ ∑ N  aN  ∑ X NY 
X 2
with
X 0 = (x 0 )i − x 0 , X 1 = (x1 )i − x1 … and (Y ) = (y i ) − (y )
By inverting the matrix, we can get the coefficients ai.

CONCLUSION:
It is important to notice that the matrix may be not inverted (or nearly not) in some
cases.
z When the correlation is wrong (When ( X N )i is nearly a constant (for example
log(HTxeff) when HTxeff is unique) and more generally variables whose

correlation is wrong (its absolute value near to zero). When the variable is actually
a constant, the correlation is 0 and no calibration is offered (in this case the chart is
empty).
z When two variables depend on each other (2 lines are proportional in the
matrix: for example log(d) and log(d)*log(HTxeff) when HTxeff is nearly a
constant), the process works wrongly and may diverge.
5-49
So, it is advised to process identification for several variables at a time but only for
those which are well correlated and do not depend on another one already involved.
5.4 Tuning Reception Parameters

5.4.1 Setting the Receiver Properties
In U-Net, the calculation of signal levels at any point, for point analysis or coverage
purpose, is linked with the definition of a receiver. Depending on the considered project
type, different properties might be set.
To set receiver properties, proceed as follows:
Either,
2) Right click on the Predictions folder to open the context menu.
Or
2) Double click on the Predictions folder.
Then
1) Left click on the Receiver tab from the open window.
2) Use the What's this help to get description about receiver fields.
3) Enter its height and, for GSM/GPRS/EDGE studies, associated antenna, losses,
and the adjacent channel protection level.
Note:
z By default, the antenna is set to an omni one with a 0 dB gain,
z In GSM/GPRS/EDGE projects, it is possible to set the adjacent channel protection
level. This parameter is used in interference computations in order to simulate the
signal level offset due to an adjacent channel contribution on the considered
channel. For example, if the value is set to 18 dB (default value), this means that the
signal level coming from an adjacent channel will be decreased by 18 dB on the total
noise computation on the considered channel.
For UMTS or CDMA/CDMA2000 studies, the point analysis tool is used for a particular
scenario. Depending on the type of mobility, service or terminal (or Radio configuration
in CDMA/CDMA2000) chosen, radio parameters are not the same for the receiver.
Consequently, to manage receiver parameters used in the point analysis, you must set
the characteristics of each used UMTS parameters (type of service, mobility, terminal)
5-50
or CDMA/CDMA2000 (type of service, Radio Configurations) in the corresponding

properties dialog window.
In GSM/GPRS/EDGE projects, U-Net has also an option which limits the
representation for coverages around stations, in order to consider synchronisation
problems. This feature is a graphic representation for coverages and is not taken into
account in calculations.
To define the maximum range value limiting the coverage display
(GSM/GPRS/EDGE studies only) around stations, proceed as follows:
Either,
2) Right click on the Predictions folder to open the context menu.
Or
Then
1) Left click on the System tab (if available) from the open window.
2) Use the What's this help to get description about the fields available in the current
window.
3) Set maximum range value.
4) Click OK or Apply to validate.
5.4.2 Computing Shadowing Margins
Propagation models are mathematical tools used for the prediction of losses along a
path with the better accuracy possible. In reality, if we were to stay on a same location
or a same clutter class measuring a signal level, we would observe some variations of
results due to slow fading/shadowing, i.e. surrounding environment. We would observe
that real results are spread on a Gaussian curve, around an average value, and with a
specific standard deviation. If we consider the model correctly calibrated, its result
should check to this average value. So, in that case, we assume that the model gives a
result which is at least correct in an average case, that is to say, in 50% of the
measured cases. 50% means that 50% of the measurements will be better that the
predicted value, the other values, being worst.
This can be taken into account by considering a model standard deviation at the
receiver (where you compute a signal level). Either the model standard deviation is
clutter class dependent (one value specified for each clutter class) if a clutter class map
is available, or U-Net considers a default value (no clutter class map available, no value
per clutter class specified or default value forced). The model standard deviation, linked
to a required cell edge coverage probability on results (point analysis or coverages)
lead to additional losses called shadowing margin. This is a margin from a result given
5-51
by propagation model (in dB) for which the probability of error is 50%. It indicates that,
on the real field, results will have at least the value computed by U-Net with the defined
cell edge coverage probability (this means maybe better but not worst).
For example, let's consider the model (correctly calibrated) gives a loss that should
lead to a signal level of -70 dBm. The user wants a reliability level of 85 %. Let's
imagine U-Net provides a shadowing margin of 7 dB for the considered location. All of
this leads to the fact that the real signal will be equal or better than -77 dBm in 85% of
cases.
Of course, if you have defined a model standard deviation per clutter class, the same
reliability level provides the same shadowing margin to all the receivers located on the
same clutter type. On the other hand, different reliability levels will impose different
values of shadowing margins even if considering the same clutter type.
To display the computed shadowing margins as a function of reliability level, proceed
as follows:
To display the computed shadowing margins per clutter class as a function of cell
edge coverage probability, proceed as follows:
3) Choose the Shadowing margins... option from the scrolling menu.
4) Use the What's this help to get description about other fields available in the
current window.
5) Set the cell edge coverage probability.
6) Click the button to start computation.

5-52
Note:
z U-Net provides a shadowing margin for each clutter class when a clutter class map
is available in the .atl document. Otherwise, it displays one default shadowing
margin computed from the default model standard deviation.
z When the cell edge coverage probability is greater than 50%, shadowing margin
values are different from zero.
z In UMTS or CDMA/CDMA2000 projects, uplink and downlink macro-diversity gains
(2 links and 3 links) are also indicated in this window. Downlink macro-diversity
gains are calculated by considering the fixed cell edge coverage probability, the
model standard deviation at the receiver, the Ec/Io difference between the best
server and the second one and the Ec/Io difference between the second best server
and the third one (these two values may be specified in the dialog). Uplink
macro-diversity gains are calculated by considering the fixed cell edge coverage
probability, the model standard deviation at the receiver, the uplink Eb/Nt difference
between the best server and the second one and the uplink Eb/Nt difference
between the second best server and the third one (these two values may be
specified in the dialog).
z If no clutter data is available, shadowing margin will be set to 0dB, and UL soft
handover gain will be set to the default global value (defined in the Transmitter
global parameters in UMTS or CDMA/CDMA2000).
z When the cell edge coverage probability is 50%, even if macro-diversity gains (2
and 3 links) may be computed in this window, the value taken into account is the
default global value (defined in the Transmitter global parameters) for coverage
studies and point analysis.
z In UMTS and CDMA/CDMA2000 simulations, these losses are evaluated by
computing random shadowing errors and are added to the model path loss.
5.4.3 Using Cell Edge Coverage Probability in Predictions
U-Net models the probability of error on the predicted path loss; errors on calculations
depend on the transmitter-receiver path and the receiver position. They are due to
some obstacles, which are not taken into account by the propagation model (in case
geographic data are not up-to-date or appropriate enough, or when there are point
obstacles). This phenomenon is called shadowing or slow fading; variation occurs over
distances comparable to the width of obstacles (buildings, hills ...) along the path.
From a user-defined model standard deviation (either depending on the clutter class
where the receiver is located, or a default value) and a reliability level, U-Net evaluates
a shadowing margin and adds it to the path loss predicted by the model. All coverage
studies integrate the possibility to enter a reliability level (in their property dialog box).
5-53
Note:
z In case of a correctly calibrated propagation model, typical standard deviations
should be around 6 dB to 9 dB.
z 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.
z In Interference computation (GSM/GPRS/EDGE, UMTS, CDMA/CDMA2000),
Shadowing margins (depending on the entered reliability level and the standard
deviation at the receiver) are applied only to signal level values. These are not taken
into account in noise determinations.
When calculating coverage with an x% reliability level, U-Net displays the areas where
the measured field exceeds the predicted signal during x% of time. When increasing
the reliability level, the predicted signal deviates from average and hence, the
shadowing margin rises.
Note:
When using the ITU 370 model, take care not to define reliability level, the reliability
level being already included as a parameter.
5.5 Coverage Studies

5.5.1 Coverage Studies Overview
A coverage is a set of covered pixels. The coverage is a result of path loss matrix
computations depending on the choice of propagation models, calculation areas and
computation and coverage resolutions. Coverage areas defined by coverage
conditions in order to select the transmitters that must be taken into account for the
study. Then, according to this selection, any pixel will be covered as depending on the
display type chosen, either by transmitter, by signal level, by overlapping zones in the
standard case (for all projects). So, a coverage is a graphic representation of points
for which a coverage condition is satisfied.
5-54
Depending on the type of project considered, some specific studies (treated in their
specific parts) are also available:
- Interference studies in GSM/GPRS/EDGE projects.
- Specific GPRS/EDGE studies dealing with coding schemes or rates colouring.
- Specific UMTS or CDMA/CDMA2000 studies based either on simulations or
user-defined traffic loads.
Like for many other U-Net objects, the management of coverage studies is both easy
and powerful. The generic U-Net display dialog (including legend, label et tip
management) is used and allows you to display your study on several attributes related
to transmitters. Furthermore, some organization features (filter, sort and groups) are
also available on the displayed result.
Many features help in the management of coverage in U-Net. Indeed, it is possible to
lock/unlock either complete studies or individual matrices, to display, print or export
exhaustive coverage reports, to export matrices or coverage zones, to check the
validity of current results regarding to the current radio configurations, and other tools
always with a view to make handy coverage studies in U-Net.
It is also possible to calculate path loss matrices independently from any coverage
study.
5.5.2 Coverage Prediction General Settings
I. Setting calculation areas
In U-Net, calculation areas are defined at the transmitter level. U-Net is able to
calculate two path loss matrices per transmitter, a first matrix over a near radius
computed with a high resolution and a propagation model, and a second matrix over a
far radius computed with a low resolution and another propagation model.
In addition, the calculation areas of each transmitter occur only within the computation
zone.
To define calculation area(s) simultaneously to all transmitters, proceed as follows:
5) In the main matrix part, enter a calculation radius (with a propagation model and a
resolution used to compute the main path loss matrix).
6) Optionally, in the extended matrix part, enter a calculation radius (with a
propagation model and a resolution used to compute the extended path loss
matrix).
5-55
To define calculation area(s) to one transmitter at a time, proceed as follows:

Either:
3) Right click on the transmitter to which you want to define a specific calculation
area.
Or
3) Double click on the transmitter to which you want to assign a specific calculation
area.
Then
2) In the main matrix part, enter a calculation radius (with a propagation model
and a resolution used to compute the main path loss matrix).
3) Optionally, in the extended matrix part, enter a calculation radius (with a
matrix).
5-56
Note:
z Since it is a matrix (or 2 in case of extended calculation radius) which is computed
for each transmitter, the calculation radius represents the half side length of the
potential matrix located around the considered transmitter.
one is invalid.
z The main calculation radius (and the related propagation model) can be also set at
the station template level.
z When modifying a computation zone (e.g. reduction of the area) in which some
predictions studies have already been made, it is strongly recommended to run
again predictions in order to ensure validity of results with current computation zone.
II. Setting calculation resolutions
In U-Net, it is possible to calculate two path loss matrices per transmitter, a first matrix
over a near radius computed with a high resolution and a propagation model, and a
second matrix over a far radius computed with a low resolution and another
propagation model. The resolution of matrices is not a global parameter since it can be
managed for each transmitter depending on its location.
In addition, it is possible to differentiate resolution of path loss matrices from plot
resolution. Prediction plot resolution can be actually defined on a per study basis. Thus,
you can calculate several coverage studies with different resolutions without
invalidating and recalculating path loss matrices.
To define calculation resolution(s) simultaneously to all transmitters, proceed as
follows:
5-57
5) In the main matrix part, enter a calculation resolution (with a propagation model
and a calculation radius used to compute the main path loss matrix).
6) Optionally, in the extended matrix part, enter a calculation resolution (with a
matrix).
To define calculation resolution(s) to one transmitter at a time, proceed as follows:
Either:
3) Right click on the transmitter to which you want to define a specific calculation
resolution.
Or
3) Double click on the transmitter to which you want to assign a specific calculation
resolution,
Then
2) In the main matrix part, enter a calculation resolution (with a propagation
model and a calculation radius used to compute the main path loss matrix).
3) Optionally, in the extended matrix part, enter a calculation resolution (with a
propagation model and a calculation radius used to compute the extended path
loss matrix).
5-58
Note:
one is invalid.
In addition to the default propagation model, a default grid resolution can be specified in
the property dialog of the Predictions folder.
U-Net takes into account the default grid resolution when no value or zero is defined for
the main resolution in the transmitter properties. In this case, the main path loss matrix
of the transmitter will be worked out with the default grid resolution.
To define a default calculation resolution, proceed as follows:
5) Enter the default calculation resolution.
current dialog window.
III. Creating coverage calculations
Whatever the project type is, all existing predictions are listed in the Predictions folder
(Data tab). When starting a new project, no prediction is available.
To create any prediction, proceed as follows:
3) Left click in the scrolling menu on New....
4) Choose from the list a prediction template in the open window.
5-59
associated prediction window.
6) Set prediction parameters.
7) Click OK to validate your choice.
At this step, no calculation is made. The prediction with the parameters is just ready to
b run.
Note:
User interface of each prediction study Properties is standardised. For any common
study, the Properties window consists of three tabs:
z The General tab where you may rename the study, define the coverage resolution,
add some comments, define group, sort and filter criteria, on the coverage display
only (not on the results),
z The Condition tab where you can specify the study parameters,
z The Display tab to define coverage display settings.
Like propagation models, any existing coverage study can be duplicated using the
Duplicate command of its related context menu (right click). The new prediction study
keeps the same coverage and display settings than the original ones.
IV. Creating coverage studies per group of transmitter
In U-Net, it is possible to automatically create prediction studies restricted to a given

transmitter or group of transmitters.
To create a coverage study by transmitter or by group of transmitters:
Either,
3) Right click on the transmitter/transmitter subfolder you want to manage.
Or,
1) Select on the map the transmitter you want to manage by left clicking on the
Then
1) Choose the Predictions... option from the context menu.
2) Choose a prediction study in the open window and press OK.
3) Click on the Calculate button to run calculations. The created study is listed in the
Predictions folder.
5-60
Note:
z The general tab of the prediction dialog can be also used to restrict the results
display identically,
z Coverages per transmitter or group of transmitters work like when filtering
transmitters in coverage studies, i.e., the filter is made on display only, and not on
computations.
V. Accessing coverage prediction properties
Coverage predictions are manageable identically as point analysis prediction. Firstly,

because propagation models may be specified either in the Predictions folder or in the
Transmitters folder, you must be very careful to its priority order. The main propagation
model defined with transmitters is taken first before the one defined with Predictions
(See Selecting and managing propagation models). Then take care about the fact that
reception is modelled as if it was made using a specific receiver and its associated
parameters.
Predictions are organised as the other U-Net objects, i.e. in a folder form. The
Predictions folder is the parent item for all the performed coverage predictions. So, it is
possible to access the properties either of the Predictions folder or of any prediction.
To access predictions global properties, proceed as follows:
either
or
Then
1) Click the Predictions, Receiver or the System tab (if available).
2) Use the What's this help to get description about the fields available in each
dialog.
3) Set predictions global parameters.
To access the properties of any single existing prediction, proceed as follows:
2) Expand the Predictions folder by left clicking on the button.
Either
3) Right click on the prediction study of which you want to access properties.
5-61

Or
3) Double click on the prediction study of which you want to access properties.
Then
1) Click on the available tabs to display the different windows.
2) Use the What's this help to get description about the fields available in each
window.
3) Check or adjust prediction parameters.
VI. Setting coverage resolutions
In the property dialog of each prediction study (General tab), it is possible to specify the
plot resolution. Prediction plots are generated from multi-resolution path loss matrices.
Nevertheless, the plot resolution is independent from matrix resolutions and can be
defined on a per study basis.
Therefore, in U-Net, you can:
z Change the plot resolution without making multi-resolution path loss matrices
invalid. This enables you to save calculation and recalculation times.
z Display prediction plots with a resolution different from path loss matrix
resolutions.
VII. Organising result outputs of a coverage study
In U-Net, it is possible to filter the results of a coverage study by excluding some zones
involved in the initial result. These filters only deal with display. Of course, during
calculation, U-Net takes into account all the active and filtered transmitters (at the
transmitter folder level) to calculate the prediction and displays only coverage related to
this transmitter.
Practical example: the network consists of 4 stations (Tx0, Tx1, Tx2 and Tx3).
z Coverage by transmitter study: with best server, no margin and filter on Tx0.
U-Net displays the areas where the signal level from Tx0 is higher than the specified
threshold and Tx0 is the best server.
z Interfered areas study: any calculation option and filter on Tx0.
Tx1, Tx2 and Tx3 are possible interferers; they are taken into account in calculations.
The covered areas are the areas where Tx0 is interfered by one of these items.
To make a filter on any study, open its associated properties, and use the standard filter
tools by clicking the button.
5-62
Note:
z Filters defined in the Transmitters folder and filters inside a polygon have priority
over the prediction filters. Transmitters, which do not check these filter criteria, are
considered as inactive in predictions.
z In the General tab, Group and Sort features enable you to organise study result in
the Explorer. You can group or sort a study according to any transmitter attribute.
These commands are always available except when selecting display of best signal
level, best server path loss, best server total losses or number of servers.
z It is also possible to set the plot resolution in the General tab of any coverage study.
VIII. Defining the coverage conditions
In U-Net, all the common coverage studies use the same dialog made of 3 tabs
(General, Condition, and Display). The condition tab of any coverage study property
dialog allows you to filter the active transmitters (with calculation area) that will be part
of the computation.
So, in this tab, you must specify (using the What's this help to get information about
available fields in the condition tab window):
z The study criterion you want U-Net to calculate: you can choose to evaluate the
signal level at the receiver (Signal level), the path loss (Path loss) or the total
losses (Total losses), as in point analysis,
z Minimum and maximum thresholds: a bin of the map will be covered only if the
calculated criterion for each considered transmitter on the bin is between minimum
and maximum thresholds.
z Servers you want to study from the evaluation of their service area. You may
choose to keep, on each pixel All the servers, the one with the Highest signal
level or the one with the Second highest signal level, as far as they check the
other conditions (e.g. minimum reception threshold).
z A margin in case of a best signal study.
- In case of all the servers are considered (All), the coverage area of Txi is the zone
where:
Minimum threshold < PTxi ( Txi

rec or Ltot or Total − Losses )
Txi ≤ Maximum threshold
- In case of best signal level (Best signal level) and a margin, the service area of Txi
corresponds to the bins where:
rec (ic ) (or Ltot or Total − Losses

Minimum threshold ≤ PTxi ) < Maximum threshold
Txi Txi
and
5-63
Txi
Prec
j ≠i
( )
(ic ) ≥ Best PrecTxj (ic ) − M
where
M is the specified margin (dB).
Best function: considers the highest value.
Note:
z If the margin equals 0 dB (best signal level and no margin), U-Net will consider bins
where the signal level received from Txi is the highest one.
z If the margin is set to 2 dB, U-Net will consider bins where the signal level received
from Txi is either the highest one or 2dB lower than the highest one.
z If the margin is set to -2 dB, U-Net will consider bins where the signal level received
from Txi is 2dB higher than the signal levels from transmitters, which are 2nd best
servers.
- In case of second best signal level and a margin, the service area of Txi
corresponds to the bins where:
rec (ic ) (or Ltot or Total − Losses

Txi Txi
and
Txi
Prec
j ≠i
( )
(ic ) ≥ 2nd Best PrecTxj (ic ) − M
where
2nd Best function: considers the second highest value.
Note:
z If the margin equals 0 dB, U-Net will consider bins where the signal level received
from Txi is the second highest one.
from Txi is either the second highest one or 2dB lower than the second highest one.
from Txi is 2dB higher than the signal levels from transmitters, which are 3rd best
servers.
5-64
In GSM/GPRS/EDGE projects, some specific server conditions related with the

potential use of HCS layers are available for the service area determination.
The last parameters to define in the Condition tab, whatever the project type is, are:
z The study cell edge coverage probability. Entering 60% as cell edge coverage
probability means that the measured criterion exceeds the predicted one, 60% of
the time.
z The selection of an item defining power in transmitters (TRX types in
GSM/GPRS/EDGE projects, carrier in UMTS or CDMA/CDMA2000).
Note:
This tab deals with the determination of covering transmitter only. The way they cover
the bin is managed in the Display tab.
IX. Managing prediction display
Like for the other U-Net objects classified under folders, prediction results can be either
displayed (by checking the box just left to each prediction) or not (by unchecking the
box just left to each prediction) on the map. You may even display all the calculated
predictions by checking the box just left to the Predictions folder (See Managing object
visibility). Coverages are organised as layers. The layer order can be modified in order
to make some of them displayed on the top.
Concerning the coverage itself, U-Net uses the generic display dialog in order to make
easy and complete its management. So, when creating a prediction study, once the
filter on the transmitters to take into account in computations and coverage (and
interference) condition are set (condition tab), the display tab allows you to colour the
defined zones depending on selected attributes (using the What's this help to get
information about available fields in the display tab window). Attributes can be chosen
in order to realize either common studies (coverage by transmitter, by signal level,
overlapping zones), or specific studies (e.g. interference studies in GSM/GPRS/EDGE
projects, handover status, pilot pollution, etc.., in UMTS or CDMA/CDMA2000 projects),
or studies depending on any other attribute (attributes of sites, antennas, transmitters
and cells in UMTS or CDMA/CDMA2000 projects).
These attributes can be, for example:
z Signal level (in dBm, dBµV, dBµV/m)
On each bin of each transmitter coverage area, U-Net calculates signal level received
from the transmitter. A bin of a coverage area is coloured if signal level exceeds (=)
entered minimum thresholds (bin colour depends on signal level). Coverage consists of
several independent layers for which you may manage visibility in the workspace.
5-65
There are as many layers as transmitter coverage areas. Each layer shows the
different signal levels available in the transmitter coverage area.
z Best signal level (in dBm, dBµV, dBµV/m)
On each bin of each transmitter coverage area, U-Net calculates signal levels received
from transmitters, which coverage areas overlap the studied one, and chooses the
highest value. A bin of a coverage area is coloured if the signal level exceeds (=)
entered thresholds (the bin colour depends on the signal level). Coverage consists of
several independent layers for which you may manage visibility in the workspace.
There are as many layers as defined thresholds. Each layer corresponds to an area
where the signal level from the best server exceeds a defined minimum threshold.
z Path loss (dB)
On each bin of each transmitter coverage area, U-Net calculates path loss from the
transmitter. A bin of a coverage area is coloured if path loss exceeds (=) entered
minimum thresholds (bin colour depends on path loss). Coverage consists of several
independent layers for which you may manage visibility in the workspace. There are as
many layers as coverage areas. Each layer shows the different path loss levels in the
transmitter coverage area.
z Total losses (dB)
On each bin of each transmitter coverage area, U-Net calculates total losses from the
transmitter. A bin of a coverage area is coloured if total losses exceed (=) entered
minimum thresholds (bin colour depends on total losses). Coverage consists of several
independent layers for which you may manage visibility in the workspace. There are as
many layers as coverage areas. Each layer shows the different total losses levels in the
coverage area.
z Best server path loss (dB)
from transmitters, which coverage areas overlap the studied one, determines the best
transmitter and evaluates path loss from the best transmitter. A bin of a coverage area
is coloured if the path loss exceeds (=) entered thresholds (bin colour depends on path
loss). Coverage consists of several independent layers for which you may manage
visibility in the workspace. There are as many layers as defined thresholds. Each layer
corresponds to an area where the path loss from the best server exceeds a defined
minimum threshold.
z Best server total losses (dB)
from transmitters, which coverage areas overlap the studied one, determines the best
transmitter and evaluates total losses from the best transmitter. A bin of a coverage
area is coloured if the total losses exceed (=) entered thresholds (bin colour depends
on total losses). Coverage consists of several independent layers for which you may
5-66
manage visibility in the workspace. There are as many layers as defined thresholds.
Each layer corresponds to an area where the total losses from the best server exceed a
defined minimum threshold.
z Number of servers
U-Net evaluates how many coverage areas cover a bin in order to determine the
number of servers. The bin colour depends on the number of servers. Coverage
consists of several independent layers for which you may manage visibility in the
workspace. There are as many layers as defined thresholds. Each layer corresponds to
an area where the number of servers exceeds (=) a defined minimum threshold.
z Cell edge coverage probability (%)
On each bin of each transmitter service area, the coverage corresponds to the pixels
where the signal level from this transmitter fulfils signal conditions (defined in
Conditions tab) with different cell edge coverage probabilities. In the explorer, there is
one coverage area per transmitter.
z Best cell edge coverage probability (%)
On each bin of each transmitter service area, the coverage corresponds to the pixels
where the best signal level received fulfils signal conditions (defined in Conditions tab).
In the explorer, there is one coverage area per cell edge coverage probability.
Caution:
In case of a signal level, path loss or total losses display, the lowest defined threshold
must be equal to the minimum threshold entered in the Condition tab.
5-67
Note:
z U-Net provides default calculation and display parameters when creating common
prediction studies (coverage by signal level, coverage by transmitter and
overlapping), but it is possible to cover by signal level even if choosing a coverage
by transmitter study.
z The definition of a study (coverage condition and display parameters) can be
chosen for a study template.
z Choosing another display type can make invalid coverage study. In this case, it is
necessary to recalculate prediction study in order to update coverage.
z In UMTS or CDMA/CDMA2000 projects, transmitter coverage areas may be
displayed according to any cell attribute. If you study a given carrier, U-Net only
displays the coverage areas of transmitters using the selected carrier. If the study is
based on all the carriers, all the transmitter coverage areas will be displayed. On the
other hand, the colour of each coverage area will depend on the number of carriers
used by the transmitter. If there is only one cell per transmitter, the colour of the
transmitter coverage area depends on the value of the cell attribute. When
transmitters have more than one cell, U-Net does not know the carrier to be
considered. In this case, no value is collected (#) and these coverage areas are
displayed with the same colour.
X. Running coverage calculations
In U-Net, coverage studies can be firstly created and tuned, and then calculated. So, it
is possible to prepare a complete set of coverage studies, and let them work all
together only when necessary.
To run calculations on created predictions, proceed as follows:
2) Calculations will be made only on unlocked predictions (symbolized ).
Either,
3) From the menu bar, click either the Calculate button or the Force
calculation button
Or,
4) Choose either the Calculate or Force calculation command from the open
scrolling menu.
Then
5-68
1) The event viewer opens showing the calculations progress in the Tasks tab (you
may stop calculations even by clicking the Stop button or pressing the Esc key).
2) When finished, results are then displayed on the current map (if the visibility flag
is checked).
Note:
The calculate and Force calculation features can be also accessed either:
z by using respectively the F7 and Ctrl+F7 keys,
z from the Tools menu in the menu bar,
z from the Predictions folder context menu.
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.
After having been calculated, coverage predictions are automatically locked.
XI. Locking coverage studies
U-Net allows you to lock some coverage predictions (and to freeze their result display)
whereas you desire to commit calculations on other studies. So, this feature enables
the user to easily compare prediction results made with different parameters
individually. This can be made either globally or for each single prediction.
To lock/unlock any single prediction study:
3) Right click on the prediction study you want to lock/unlock the calculations.
4) Select/Unselect the Study Locked option from the open scrolling menu.
To lock/unlock all the existing prediction studies:
3) Select either the Lock studies or Unlock studies from the open scrolling menu.
Locked predictions are displayed with the icon, whereas unlocked predictions are
given by the icon.
5-69
Note:
z After having been calculated, coverage predictions are automatically locked.
z Be careful not to mix up locking predictions with locking path loss results from the
Result storage. Even if some predictions are locked and other unlocked, path loss
matrices may stay unchanged if either they are locked in the Result storage window
or if the user does not use the Force calculation button.
Caution:
When calculations have to be completed, be sure to have already defined the

coordinate system used in the current project.
5.5.3 Prediction Study Templates
I. Calculating a coverage by transmitter
In U-Net, all studies are classified in a study types box, referencing standard and
customized studies. Standard studies are divided into two parts, common studies and
studies which are specific to the current project (GSM/GPRS/EDGE, UMTS, and
CDMA/CDMA2000). Common studies for any projects are: coverage by transmitter,
coverage by signal level and overlapping zones.
The coverage by transmitter study enables the user to predict coverage zones by
transmitter depending either on their signal level, their path loss or total losses defined
within a user-defined range.
To prepare this prediction study, in the prediction creation steps, select the coverage by
transmitter option from the study types window. The open window is made of three tab
windows: General, Condition, and Display. For all of these, use the What's this help to
get description about the fields available in the windows (See also Defining the
coverage condition and Manage prediction display).
The coverage by transmitter study is a template for which the field 'Transmitter' is
selected by default in the display tab. In that case, coverage zones will be displayed
with the same colours than the ones defined for each transmitter.
5-70
Note:
z U-Net offers default calculation and display parameters when creating common
prediction studies but it is possible to cover by signal level even if choosing a
coverage by transmitter study just by setting this in the display tab.
II. Calculating a coverage by signal level
The coverage by signal level study enables the user to predict coverage zones by field
strength from transmitter depending either on their signal level, their path loss or total
losses defined within a user-defined range.
To prepare this prediction study, in the prediction creation steps, select the coverage by
signal level option from the study types window. The open window is made of three tab
get description about the fields available in the windows (See also Defining the
coverage condition and Manage prediction display).
The coverage by signal level study is a template for which the field 'Best signal level' is
selected by default in the display tab. In that case, each layer corresponds to an area
where the signal level from the best server exceeds a defined minimum threshold.
Numerous options related to signal level coverage are available in the Display tab.
Note:
prediction studies but it is possible to cover by transmitter even if choosing a
coverage by signal level study just by setting this in the display tab.
z Choosing a display per best signal level creates a study item made of threshold
items whereas choosing a display per signal level let the folder be made of
transmitter items. On each of these items, it is possible to check/uncheck the
visibility flag.
5-71
III. Calculating overlapping areas
Overlapping is a coverage whose points correspond, for a defined condition, to the
common points of areas covered by the signal of, at least, two transmitters. Therefore,
U-Net displays the areas where the signal level from at least two transmitters (signal
level option), the path loss of the signal received from at least two transmitters (path
loss option), or total losses along two paths between the considered point and
transmitters (total losses option), is between minimum and maximum user-defined
thresholds.
To prepare this prediction study, in the prediction creation steps, select the Overlapping
option from the study types window. The open window is made of three tab windows:
General, Condition, and Display. For all of these, use the What's this help to get
description about the fields available in the windows (See also Defining the coverage
condition and Manage prediction display).
The coverage by overlapping area study is a template for which the field 'Number of
servers' is selected by default in the display tab. In that case, each layer corresponds to
an area where the number of servers exceeds a defined minimum threshold.
Note:
prediction studies but it is possible to cover by transmitter even if choosing an
overlapping study just by adjusting display.
IV. Creating a coverage study template
U-Net provides a feature allowing you to save the definition of a coverage study
(General, condition and display tab properties) in a study template.
To save the settings of any study in a template, proceed as follows:
1) Right click the coverage study you want to save as a template.
2) Choose the "Save as a template" command from the open context menu.
3) U-Net saves the study parameters in a “Studies.xml” file stored in the U-Net
installation directory.
5-72
All the study templates saved in this file are available when creating new prediction
studies. In the Study types window, U-Net lists all the classical studies available for a
type of project in the standard studies part and the study templates you have created in
the customised studies part.
Note:
The name given to the reference study is kept as template name.
It is possible to remove a study template from the file. In the Study types window, select
a customised study and click on the Delete button.
V. Deleting a coverage study template
In U-Net, coverage study templates are saved in a “Studies.xml” file stored in the U-Net
installation directory. These templates contain settings of reference studies set in their
General, condition and display tab properties.
To delete an existing study template proceed as follows:
3) Left click in the scrolling menu on New....
4) Select from the list the study template (customized studies) you want to delete.
5) Click the button.

Note:
You can also delete globally all the customized studies by deleting the Studies.xml file
in the U-Net directory.
5.5.4 Path Loss Management
I. Storage of path loss matrices
The first step of coverage predictions consist in the determination of the path loss
matrices associated with each active and filtered transmitter in the network. This is
automatically made for the first coverage prediction. Results (path loss matrices) may
be stored either directly in the current atl project or can be externalised either in the
same directory than the .atl project or in any directory you can specify.
5-73
To set the location of the path loss matrices of an .atl U-Net project, proceed as
follows:
3) Choose the Properties option from the scrolling menu.
4) In the Predictions tab, click on the button and choose a location to store
multi-resolution path loss matrices:
z Embedded: matrices are included in the .atl document.
z \<ATL_name>.losses: Multi-resolution matrices are stored in an external folder
located in the same directory as the .atl document. U-Net memorises a relative
path to access path loss matrices. By default, this folder is called
<ATL_name>.losses (<ATL_name> is the name of the .atl document).
Nevertheless, it is possible to change the folder name afterwards; all the names
are supported. When using the Save as command, U-Net creates a new folder
associated to the new .atl document in the same directory; this folder contains path
loss matrices and has the same name as the .atl document. No recalculation
occurs if you move the .atl document and its related path loss matrix folder in
another directory.
z Browse: In this case, specify the directory where you want to save path loss
matrices and click on OK. U-Net memorises the whole path to access path loss
matrices. The path can be manually typed or modified. In that case, U-Net works
differently than in the previous option when using the Save as command. It only
creates the new .atl document.
current window,
When externalising path loss results, U-Net creates an external folder containing:
z One .los file per transmitter ; it corresponds to its main path loss matrix.
z A .dbf file giving validity information for all the main matrices.
z A folder called LowRes dedicated to extended path loss matrices.
This folder contains one .los file per transmitter, which has an extended path loss matrix,
and a .dbf file giving validity information for all the extended matrices.
Using this option, calculations are no longer stored in the .atl file. This feature enables
the user to store bigger calculations in external files without storage size limitation (2
Gbytes for a file).
5-74
Caution:
The external files are updated without saving the U-Net environment as soon as
calculations are performed. To keep consistency with the stored calculations, the
corresponding U-Net environment must be saved before closing.
Note:
z Since the dbf file has a standard format, its contents can be checked by opening it in
Access.
z This feature allows you to create matrices that will sharable between several users.
z In the case of a project in which some matrices were initially embedded, U-Net
provides a feature that compresses .atl files when getting out
II. Locking path loss results
This feature enables you to let freeze any path loss matrix, even if invalid when using
the Calculate button. Nevertheless, all existing (even locked) matrices are
recalculated if you use the Force calculation button during calculations.
There are two ways to lock path loss matrices, either from the Predictions global
properties in a table form, or from any transmitter properties.
To lock/unlock propagation results (one transmitter at a time), proceed as follows:
Either
3) Right click on the transmitter you want to lock the associated path loss matrix.
4) Choose the Properties option from the open scrolling menu.
Or
3) Double click on the transmitter you want to lock the associated path loss matrix.
Then
1) Click on the Propagation tab.
2) Check/Uncheck the Locked box.
3) Use the What's this get description about other fields available in the current
window.
5-75
To lock/unlock propagation results (possibly on several transmitters), proceed as

follows:
3) Choose the Result storage... option from the open scrolling menu.
Either
4) Check/Uncheck the Locked box associated with the transmitters you want to
lock/unlock the associated path loss matrix.
Or
4) Select the transmitters you want to lock path loss matrix.
Then
1) Choose the Lock/Unlock option from the Action button.
2) Use the What's this get description about other fields available in the current
window.
Note:
z Be careful not to mix up locking matrices with locking calculations.
z It is possible to lock/unlock matrices from the context menu of the Propagation tab of
the Transmitter global properties.
III. Checking path loss results validity
This feature enables you to check if current path loss results are consistent with the
current radio parameters. There are two ways to check path loss matrices validity,
either from the Predictions global properties in a table form, or from any transmitter
properties. If validity is not ok, you may calculate path loss matrices again in order to
keep consistency. Reasons of invalidity are displayed for each transmitter.
To check propagation results validity (one transmitter at a time), proceed as follows:
Either
3) Right click on the transmitter you want to check the associated path loss matrix
validity.
Or
5-76
3) Double click on the transmitter you want to check the associated path loss
matrices validity.
Then
2) Check the label displayed in the Validity line. If the label is "No", the invalidity
reason is given just below.
current window.
To check propagation results validity (possibly on several transmitters), proceed as
follows:
5) Check the label displayed in the Validity column. If the label is "No", the invalidity
reason is given on the same line.
current window.
From this dialog box, it is possible to know how many transmitter path loss data
must be recalculated in order to be consistent with the current radio configuration
before starting calculations. Only matrices dealing with active transmitters are taken
into account in that case. To do so, click on the button. The number is
automatically given in the dialog. The number of transmitters available in the current
network is also indicated.
Note:
z It is possible to check the validity of existing path loss matrices from the [Predictions:
Result storage...] command.
z U-Net manages path loss matrix validity, transmitter by transmitter, even in case
transmitters have main and extended path loss matrices. Therefore, even if only one
path loss matrix of the transmitter is invalid, U-Net will recalculate both of them.
z In the Results storage dialog and in the Propagation tab of the Transmitters property
dialog, U-Net lists calculated transmitters (transmitters with main and extended
matrices) without distinguishing main path loss matrices from extended ones.
5-77
IV. Exporting main path loss matrices
Existing main path loss matrices may be exported in external files in order to be used in
external applications. For the export, the user must select the type of value to export
(Path loss or Signal levels). If “Signal level“ is selected, units have to be chosen.
Furthermore, U-Net enables the user to select the storage file format (binary, text or
table).
To export one or several path loss matrices, proceed as follows:
3) Choose the Result storage... option from the open scrolling menu.
4) Select the transmitter(s) from which you want to export the existing main matrix.
current window.
6) Choose the Export... option from the Action button.
7) Choose the directory, the format, and the field to export.
Two files are created by exported matrix. One is the exported field, the other, the
georeferencement file related to the involved transmitter and its related calculation
area.
Possible exports are:
z Attenuations in dB
z Signal levels in dBm, dBµV or dBµV/m
Possible file formats to export values are:
z Binary format: .bil
z Text: .txt with tab as separating character
z Table: .csv with semicolon as separating character
Caution:
Take care not to mix-up with externalising path loss matrices (where each matrix is
"made" of a .par and .los file)
Note:
Secondary matrices, linked with extended calculation radius, cannot be exported.
5-78
5.5.5 Prediction Coverage Outputs
I. Managing prediction results Overview
U-Net contains several features in order to manage prediction results. Prediction

results concern both coverages and matrices.
From available results, it is possible to display associated statistical reports on the
coverage zones associated with each prediction study, and to easily export or print
them.
When a coverage display is satisfactory, it is possible to lock it in order to create
further comparative coverage with different parameters. A comparison tool between
two different predictions is even available.
Depending on their type, coverage results may be exported in vector or raster formats.
Exported data are covered areas and related threshold definition.
Another U-Net feature allows you a complete management of path loss matrices
related to transmitters. Firstly, it is possible to lock only some path loss matrices (even if
invalid), while calculating path loss matrices from other transmitters of the network.
Then, it is possible to check the validity of current matrices regarding the current radio
parameters. Then, these path loss matrices my also be exported in order to be used
in external applications.
Results (path loss matrix for each transmitter) may be either directly embedded to
any current project, or outsourced to an external folder, in order to let them available
from other users. Indeed, U-Net permits to share propagation results stored in an
external folder between several users. Therefore, this special results storage
permits to use in the same project, both external results for some transmitters and
private results for others. This part is treated in the specific multi-users chapter.
Note:
Even if several cells can be defined per transmitter in UMTS or CDMA/CDMA2000,
only one path loss matrix is computed per transmitter, powers not being parameters of
interest for matrix computation.
II. Displaying prediction reports
U-Net provides a report editing feature on all available prediction for any project type.
These can be done either for each single prediction or for all displayed prediction (
box checked for predictions in the Predictions folder from which you want a report).
Reports are displayed in a table form and their content can be managed like in any
other table.
5-79
When a report table is active, columns can be managed by using the columns to display
option from the Format menu. On first opening, the report will only display the name
and coverage areas columns.
To edit a report about any displayed coverage, proceed as follows:
3) Right click on the Prediction from which you want a report to open the associated
context menu.
4) Choose the Generate Report option from the scrolling menu.
5) The associated report is then displayed as a new window.
6) Choose the Display columns... option from the Format menu.
7) Check the boxes associated with the related information to display as columns are
the current report.
Note:
z You may display simultaneously report on all displayed coverages by using the
Generate Report option from the Predictions folder context menu. The obtained
report concerns all displayed predictions, and is organised in the same order than
the one defined in the Explorer window Data tab.
z Columns to display are either related to the global coverage or to each transmitter
taking part into the coverage.
z In GSM/GPRS projects, reports dealing with traffic data are base on the default
traffic analysis
III. Exporting prediction reports
The report on any coverage prediction can be exported to any other Office-like
application. To do so, like for any other table in U-Net, perform a copy and paste
action for the entire report, then reformat the text if required (change into a table,
modify, etc...).
You may also export the displayed map (including currently displayed results) and the
results from the point analysis window to any other application program supporting
image data format.
IV. Printing prediction reports
You can use U-Net to print characteristics tables and reports as well as maps with their
coverage.
To print a prediction report, proceed as follows:
5-80
1) Make active a report window.

2) Choose the Print... option from the File menu in the menu bar.
window.
4) Adjust the printing parameters (We assume that your printer is correctly
configured for your Windows applications. If this is not the case, first use the Print
configuration... option).
5) Click OK to validate and activate the printing.
Print reports can be centred on the sheet and possibly spread over a number of sheets
for large-scale tables. Cell sizes are then displayed on the screen.
Note:
When printing a report, a footnote is created automatically in order to indicate the date
(in month/day/year format) and the time of printing as well as the page numbering.
V. Comparing two prediction studies
U-Net is capable of comparing the coverage plots resulting from two different prediction
studies and generating a comparative plot from the two. This type of comparative
coverage plot is called a Delta plot in U-Net. A comparative prediction study can be
created from the following prediction studies:
z All common prediction studies with display set so as to display the extreme values
(maximum / minimum / best / highest etc.).
z All UMTS or CDMA/CDMA2000 prediction studies based on simulation averages
or actual results.
The user should keep in mind that two studies that are displayed according to a certain
transmitter property cannot be compared. The coverage plots should not depend on the
transmitters in order to be comparable.
Furthermore, delta plots are always locked studies and cannot be unlocked.
Comparative studies have the following properties:
z A name convention has been adopted for delta plots: Comparison (Prediction
Study 1 - Prediction Study 2).
z The comments field contains the comments from the two prediction studies
compared.
z The names and bin resolutions for the two studies compared are also stored.
z The bin resolution used for the delta plot calculation is the higher one of the two.
Three display formats are possible for delta plots:
5-81
z Intersection: Shows the area where both prediction study plots overlap (i.e. the
pixels covered by both).
z Union: Shows all the pixels covered by both or at least one of the two prediction
studies with different colours.
z Difference: Shows all the pixels covered by both or either one of the prediction
studies with different colours.
Like all other prediction studies, it is also possible to export the delta plots in agd, mif, tif,
shp and bmp formats.
To create a new delta plot, proceed as follows:
3) Right click on one of the two prediction studies to compare to open the associated
context menu.
4) Choose the second prediction study from the submenu Compare with.
5) The Comparison (Prediction Study 1 – Prediction Study 2) properties dialog
opens.
6) Set the display properties on the Display tab.
7) Click OK to compute the delta plot.
Delta plots are automatically calculated and are locked. If you modify the display
properties, the delta plot will be automatically recalculated when the properties window
is closed by pressing OK.
VI. Exporting prediction coverages
With U-Net, it is possible to export the coverage areas resulting from any coverage
prediction in Bmp or Tiff raster formats or in ArcView©, MapInfo© or Agd vector formats.
Of course, it is possible to only export predictions that have been calculated
beforehand. Exporting coverage predictions allows the user to generate data file easy
to import as vector or raster objects within U-Net or within other applications. For each
exported prediction (total or for a transmitter), the exported zone is delimited by the
rectangle encompassing the coverage. All coverage type can be exported.
To export any prediction coverage zone, proceed as follows:
3) Right click on the Prediction from which you want to export the coverage zones.
4) Choose the Export... option from the scrolling menu.
5) Choose the name, the format and the path for the file to be exported.
6) Click on the Save button to validate.
7) Check or change the export resolution (only in case of ArcView© vector format).
The default one is the resolution of the prediction plot (set in the prediction study
property dialog).
5-82
8) Check or modify the reference coordinate system for the file to be exported (if
needed - vector format).
9) Click the Export button to achieve the prediction export.
Note:
z Be very careful about the accuracy of the coordinate system format to export.
Indeed, when selecting a different coordinate system than the one initially defined
within U-Net, the file is converted thanks to this other coordinate system.
z Raster format export is not possible when the coverage is made per transmitter
(coverage studies with display type per transmitter, per any transmitter attribute, per
signal level, per path loss, per total losses). In this case, only coverage area of a
single transmitter can be exported in BMP or TIFF raster format.
See Coverage prediction available exports.
VII. Coverage prediction available exports
Depending on the type of prediction, the following exports are possible (see Table 5-8).
Table 5-8 Available exports
Prediction Possible export

Overlapping The total coverage
Coverage by signal level
Coverage by C/I level
Pilot pollution
Downlink total noise
handover status
GPRS/EDGE max rate per
timeslot
GPRS/EDGE coding scheme
Coverage by transmitter The total coverage
Interfered zones Coverage of each transmitter
Service area (Eb/Nt) uplink

Service area (Eb/Nt) downlink
Effective service area
5-83
Prediction Possible export

Pilot reception analysis Ec/Io
For each exported prediction (global or for a single transmitter), the exported zone is
delimited by the rectangle encompassing the coverage
Note:
Exporting coverage zones by transmitter is possible only when the coverage study item
is made of transmitter sub-items.
5.6 Point Analysis Predictions

5.6.1 Point Analysis Predictions Overview
U-Net contains several propagation models for specific needs. Once the choice has
been made, the associated parameters have been set and the receiver has been tuned,
you are able to make radiowave propagation predictions. Moreover, U-Net provides a
point analysis tool allowing you, in the standard case (for all types of projects),
z to study reception along a profile between from a reference transmitter in real time
(no matrix needed).
z to evaluate the signal levels coming from the surrounding transmitters at a given
point (using existing path loss matrices).
Furthermore, this tool is very helpful in the analysis of cases related to specific
technologies. With this, you can:
z evaluate interferences on a selected transmitter at a given point, and determine
the interferers and associated noise levels in GSM/GPRS/EDGE projects.
z make a complete active set analysis at a given point for a probe UMTS or
CDMA/CDMA2000 user moving in the network with a particular behaviour. This
tool will help you to study also, at a point, the pilot reception and the connection
status.
These specific studies are available in their specific parts.
Of course due to the fact that several powers can be defined on an identical transmitter
(at the subcell level in GSM/GPRS/EDGE or at the cell level in UMTS or
CDMA/CDMA2000), point analysis window provides the possibility to select either the
TRX type or the carrier of the study.
5-84
Using the Standard Propagation Model, it is possible to obtain further data along a
terrain profile with the point analysis. Other tools like export ease, link budget, the
possibility to adjust in real time cell edge coverage probability, etc...are also available
Note:
Like for coverage predictions, and because propagation models may be defined either
in the Predictions folder or in the Transmitters folder, you must be very careful to its
priority order. The propagation model defined with transmitters is taken first
compared to the one defined with Predictions (See Selecting and managing
propagation models).
5.6.2 Displaying Point Analysis Results
I. Using the receiver
To make the point analysis active, just click on the icon (or check the Point
analysis in the View menu). When this is made, you can move on the active map, and
have displayed in Point analysis window the profile analysis between a given
transmitter and the current location, the predictions from all the surrounding
transmitters, and specific GSM/GPRS/EDGE or CDMA/UMTS studies.
If you click on the map, the receiver is fixed on a particular point. To move it again,
just click the icon, and drag it over the map.
II. Studying the profile from a transmitter
With the point analysis tool, U-Net is able to display a view of the terrain profile between
a given station and the point defined by the receiver on the map using the propagation
model as defined before (with priority order respect). Results are given in real time (no
need for path loss matrices).
To make active the reception profile 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 Profile tab.
4) Select the transmitter on which you want to base the prediction from the
associated scrolling list.
Either
5-85
5) Click the button in the Point analysis window,
Or
5) Click the button from the toolbar,
Then
1) The data appearing on the profiles (ellipses, clutter, etc.) will be function of the
considered model (See below).
In this profile tab window, U-Net indicates the propagation model associated with the
selected transmitter; this model is used for analysis. You may choose to display either
the signal or several losses at any point. You can also choose the item level at which
the power(s) of each transmitter are defined (TRX type or carrier).
The altitude (expressed in metres) is reported on the vertical scale. A green line shows
the line of sight (LOS) from the studied transmitter and U-Net displays the angle of the
LOS read in the antenna vertical pattern. Along the profile, if the signal meets an
obstacle, this causes an attenuation with diffraction symbolized by a red vertical line (if
the model used takes into account diffraction mechanisms). The main peak taken into
account is the one that intersects the most the Fresnel ellipsoid. Any attenuation that
occurs is then calculated in one hand, between the station and the main peak, in the
other hand, between the main peak and the receiver. With some propagation models
using a 3 knife-edge Deygout diffraction method, the result may then show up two new
attenuations peaks in addition to the main peak. The various peaks are identified by red
lines. The attenuation generated by all the peaks is displayed above the main peak.
III. Profile with ITU 526-5, Okumura-Hata or Cost-Hata model
When you use the ITU 526-5, Okumura-Hata or Cost-Hata models, Fresnel ellipsoids
(blue) will appear on the profile and possible diffraction peaks will be represented by a
red line. The attenuation generated by these peaks will be displayed above the main
peak.
z Profile with WLL model
When you use the WLL model, clutters will also appear on the profile in addition to
DTM.
As for the previous models, the Fresnel ellipsoids (in blue) and possible diffraction
peaks due to the DTM and/or clutters symbolized by red lines with attenuation
calculated for all these peaks are displayed above the main peak.
z Profile with the Longley-Rice and Vienna 93 models
Only the first Fresnel ellipsoid and the terrain profile appear for these two models.
z Profile with the Standard Propagation model
5-86
Peaks of diffraction are displayed regarding to the selected method (Deygout,

Epstein-Peterson, Deygout with correction and Millington). Both the terrain profile and
the clutter (and its height, if defined) appear using this model. A report containing
information on transmitter-receiver profile can be displayed.
IV. Displaying predicted signal levels at a point
With the point analysis tool, U-Net is able to display the signal from active transmitters
in a network at the point defined by the receiver on the map by using the propagation
model as defined before (with priority order respect).
To make active the reception window:
environment.
3) Left click on the Reception tab.
4) Click the button from the toolbar.
5) Move over the current map to the places where you want to make your analysis.
The value of the different signal levels coming from different transmitters is reported in
the Reception window in bar form, from top to bottom from the highest predicted signal
level to the lowest one. Displayed bars have the same colours as defined for each
transmitter.
Note:
z Displaying the predicted signal level at a point is possible only if path loss matrices
have been already determined. To do this, you must have previously executed any
coverage prediction or simulations (CDMA/CDMA2000, UMTS) before using the
point analysis tool.
z You can choose the item level at which the power(s) of each transmitter are defined
(TRX type or Carrier),
z IN GSM/GPRS/EDGE projects, it is possible to select the HCS layer on which you
want to study signal levels.
z For UMTS or CDMA/CDMA2000 studies, that is the pilot power which is displayed in
this window whereas it is the Ec/Io which is given in the AS analysis window.
V. Listing all signal and C/I levels at a point
In addition to the studies with point analysis of the profile from a transmitter, predicted
signals from surrounding transmitters, and, potentially interferences in case of
GSM/GPRS/EDGE projects, U-Net provides an additional tab in the point analysis
5-87
window allowing you to display, in the same window, general information at the
receiver.
So, U-Net provides in the Results tab of the Point analysis window:
z General information on the receiver: its coordinates (stated in the Display
coordinate system) and the clutter class which it is located on.
z The signal level received from each transmitter containing the receiver in its
calculation area, (Transmitters are sorted in a descending signal level order).
z C/I levels due to surrounding transmitters, first both in co-channel and adjacent
cases, then in adjacent channel case only (studying always the most interfered
TRX) in GSM/GPRS/EDGE projects.
Note:
z Displaying interference levels at a point is possible only if path loss matrices have
been already determined. To do this, you must have previously executed any
coverage prediction or simulations (CDMA/CDMA2000, UMTS) before using the
point analysis tool.
z Interferences are possible only if some channels have been allocated to TRXs.
z You can choose the item level at which the power(s) of each transmitter are defined
(TRX type or Carrier).
z IN GSM/GPRS/EDGE projects, it is possible to select the HCS layer on which you
want to study signal levels.
z For UMTS or CDMA/CDMA2000 studies, that is the pilot power which is displayed in
this window whereas it is the Ec/Io which is given in the AS analysis window.
5.6.3 Managing Point Analysis
I. Selecting a transmitter in point analysis
When studying reception profile and interferences using the point analysis tool, it is
possible to display results at an identical point for several transmitters.
To do so, when using the point analysis icon over the map as a moving receiver,
click on the map at the location you want to study different transmitters. Then, the
receiver is fixed on the map. In the Point analysis window (Profile or Interference
tab), select the transmitter to study then. Results are automatically displayed in the
Point analysis window.
5-88
II. Selecting the power definition item in point analysis
Depending on the considered technology, power can be defined with different values
within the same transmitters. The point analysis window allows you to select the level at
which several powers can be defined for the same transmitter. Hence, you can select:
z In GSM/GPRS/EDGE, the TRX type (BCCH, TCH or TCH_INNER) over which to
study the profile. Choosing the (All) option takes the TRX type with the highest
signal level.
z In UMTS or CDMA/CDMA2000, the carrier, assuming that several cells can be
assigned to a transmitter, each cell characterising a carrier on a transmitter.
Choosing the (All) option takes the carrier where the related cell has the highest
signal level.
This feature is available both when working in the Profile, Reception, Interference,
Results and AS Analysis tabs in UMTS/CDMA. Nevertheless, concerning the last one,
the (all) option (for cells) works regarding the carrier selection mode as defined in the
site equipment (UMTS, CDMA/CDMA2000).
III. Adjusting cell edge coverage probability in a point analysis
U-Net allows the user to display the properties of a probe receiver used in a point analysis
window. Depending on the tab in use (reception profile, predicted signal, interference analysis,
Results, and AS Analysis tabs in UMTS/CDMA, it is possible to display different pieces of
information.
The cell edge coverage probability can be set at the receiver level, in order to calculate
shadowing margins (using model standard deviation defined per clutter class or the
default one) to be applied to computed path loss (made by the model).
In any tab window of the point analysis window, to access the reliability setting box,
proceed as follows:
1) Right click in the current Point analysis window.
window.
4) Set the value of the cell edge coverage probability.
5) The related shadowing margin value is automatically displayed.
5-89
Note:
z When the cell edge coverage probability is greater than 50%, shadowing margin
values are different from zero.
z When the reliability level is 50%, U-Net takes into account the default UL
macro-diversity gain defined in the Transmitter global parameters for coverage
studies and point analysis.
z In UMTS and CDMA/CDMA2000 simulations, these losses are evaluated by
computing random shadowing errors and are added to the model path loss.
IV. Displaying signal levels or losses in point analysis
U-Net allows the user to display the properties of a probe receiver used in a point
analysis window. Depending on the tab in use (reception profile, predicted signal,
interference analysis, Results, and AS Analysis tabs in UMTS/CDMA, it is possible to
display different pieces of information.
Hence, you can choose to display results at a given point in term of path loss, total
losses or signal level in the Profile tab of the point analysis window. This can also be
made as a coverage condition.
In the Profile tab window, to access the result type box, proceed as follows:
window.
4) Choose to display the signal level, path loss or total losses in the Result type
scrolling box.
5) Click OK to close the dialog and validate your choice.
The available study criteria are detailed in the table below (see Table 5-9).
Table 5-9 criteria
Study criteria Formulas
Signal level ( Prec ) (

Prec = EIRP − Lpath − MShadowing + G ant Rx − LRx )
Path loss ( L path ) Lpath = Lmodel + Lant Tx
Total losses ( ) (
Total − Losses = Lpath + M Shadowing + LTx + LRx − Gant Tx + Gant Rx )
(Total-Losses)
5-90
Note:
In case of coverage studies, it is possible to calculate the signal level at the receiver in
dBm, dBµV or dBµV/m.
V. Displaying link budget at a receiver
U-Net allows the user to display the link budget at a receiver along a path profile. The
link budget is made of powers, gains and losses composing the resulting signal level.
To display the link budget box at any point, proceed as follows:
2) Left click on the Profile tab.
4) Choose the Link budget... option from the context menu.
VI. Using a site as a target for point analysis
U-Net provides a feature in order to drop the receiver used for point analysis on the
exact location of an existing site, using any tab (reception profile, predicted signal,
interference analysis, Results, or AS Analysis tabs in UMTS/CDMA of the point
analysis window.
To put the point analysis tool on an existing site, proceed as follows:
1) Make active the point analysis.
2) Right click on the receiver to open the associated context menu.
3) Select the Target site command from the open scrolling menu.
4) In the Target site dialog, choose one existing site from the scrolling list.
VII. Displaying SPM parameters over a profile analysis
When using Standard Propagation model, you may display a report containing
information on transmitter-receiver profile.
To get it, proceed as follows:
1) Right click on the profile part of the current window in order to open the
2) Choose the Model details command from the displayed menu.
The default text editor. In this report, U-Net gives the number of points taken into
account along the transmitter-receiver path and details for every point:
z The distance between the point and the transmitter (Dist) in m.
z The ground height (Alt) in m.
z The ground height with earth curvature consideration (Gr H) in m.
5-91
z The total height (Tot H) in m: Tot H = Gr H + clutter height.
Note:
At the transmitter (first point in the list) or at the receiver (last point in the list), we
respectively have: Tot H = Gr H + Clutter height + HTx and Tot H = Gr H + Clutter height
+ HRx, where, HTx and HRx are respectively transmitter and receiver antenna heights
above the ground (m).
z The clutter class.

z The filtered total height (Flt H) in m. U-Net determines this parameter only when
the Enhanced slope at receiver method is selected.
Then, it recapitulates the effective transmitter antenna height (Tx effective height), K1
and K2 parameters used in calculations (Far or Near, LOS or NLOS), the diffraction
loss, the antenna loss, the clutter loss and the correction for low Tx effective height. In
addition, U-Net informs you that the free space loss is considered when the loss
calculated by the model is lower.
VIII. Exporting a point analysis study
Whatever the point analysis on which you are working (reception profile, predicted
signal level, interference analysis, and AS Analysis - UMTS/CDMA - tabs) is, U-Net
allows the user to export a result as displayed in the Point analysis window as in image
in any application.
environment.
3) Choose the tab associated with your current study.
4) Make your results displayed.
5) Right click in the Point analysis window.
6) Choose the Copy option from the context menu.
7) Switch to another application supporting any format image.
8) Paste the current content of your clipboard:
z Either by using the Ctrl+V shortcut,
z Or by choosing the Paste command from the Edit menu.
IX. Printing a point analysis study
Whatever the point analysis on which you are working (reception profile, predicted
signal level, interference analysis, and AS Analysis - UMTS/CDMA - tabs) is, U-Net
allows the user to print a result as displayed in the Point analysis window:
5-92

environment.
3) Choose the tab associated with your current study.
4) Make your results displayed.
5) Right click on the Point analysis window.
6) Choose the Print... option from the context menu.
7) The Print dialog window opens.
8) Choose the appropriate printing parameters.
9) Click OK to start printing.
5.7 Calculation Tools in U-Net

5.7.1 U-Net Features for Computing
U-Net provides a multi-thread feature allowing you to spread some computations on

several processors. Hence, U-Net can use two processors of the local machine for
propagation computations, neighbour allocations (internal and Inter-technology
neighbours), UMTS and CDMA/CDMA2000 simulations and coverage studies
(standard or specific GSM/GPRS/EDGE, UMTS or CDMA/CDMA2000), automatic
scrambling code allocation and automatic PN Offset allocation.
This feature is automatic. That means that, on a dual-processor pc, each processor
works out one path loss matrix, one prediction study or one simulation. Therefore,
calculation times are divided in two.
It is also possible to distribute path loss calculation using several Pcs on the same time.
5.7.2 Distributing Calculations on Several PCs
U-Net provides you the possibility to share computations using two processors of a
multi-processors PC. Moreover, another feature enables you to distribute path loss
calculations on several workstations. The U-Net package provides a computing server
application; it can be installed either on workstations or servers and used by U-Net
sessions installed on other stations. Once the computing server application is installed
on a workstation, this one is considered as a potential calculation server for other
workstations with computing server application. Therefore, a user can distribute
calculations of path loss matrices on another workstation if the computing server
application is installed on his workstation and the other one.
This application (working only on path loss matrix computations) supports
dual-processor configurations. Once the computing server application is installed on
some computation servers, the distributed computation feature is possible for other
computers of the network.
5-93
To activate the distributed calculation on a local workstation, proceed as follows:

1) From the menu bar, select the Distributed calculation... command in the Tools
menu.
3) Check the Activate the distributed calculation option.
z Either, Type the name of calculation servers, which you want to distribute
computations on (use semicolon as separator). U-Net automatically saves the list
of calculation servers to be used in a U-Net.ini file located in the U-Net installation
directory. The file has the following syntax:
[RemoteCalculation]
Servers=Workstation_1;Workstation_2
If the list is empty, U-Net considers that the distributed calculation option is inactive.
Then, computations are run on the local workstation.
z Or, When clicking on the Detect button, U-Net searches and displays all the
potential calculation servers you can use. Or When clicking on the All button,
U-Net displays the symbol * in the Use servers dialog. In this case, it will scan all
the potential calculation servers when starting calculations. U-Net will use all the
found calculation servers. Then click OK to validate your choice.
Note:
z When starting propagation computations, U-Net searches the calculation servers of
the list and distributes calculations on the found servers. It displays in the Events tab
the found calculation servers.
z If calculation servers entered in the list are not available (workstation is off),
computations are run on the local workstation.
z The distributed calculations do not work in case of embedded geographic data and
ISTAR format maps (*.ist).
z Several users can distribute their computations on the same calculation server.
Path loss matrices are not simultaneously calculated but one at a time (e.g. 1st
matrix from user1, 1st matrix from user2 and so on)
z A U-Net.ini file can be prepared by an administrator in order to specify the
computing servers, and marked as read only.
z This calculation server(s) uses 1 U-Net licence per pair of processors. Of course,
each pair of processors of each client uses also a licence.
z Floating licence is not mandatory using the U-Net calculation server feature.
5-94
5.7.3 Improving Calculation Performances
It is possible to specify a cut-off value on the received signal level; this one is used by
U-Net to limit contribution of some interferers. Thanks to this feature, some calculation
performances may be improved:
z All the calculations based on the C/I criterion study in GSM/GPRS/EDGE/TDMA
documents: the coverage predictions (coverage by C/I level, interfered zones or
GPRS/EDGE studies), the interference tab of the point analysis window, the traffic
analysis and interference histograms,
z All the calculations based on the total noise in UMTS/WCDMA and
CDMA/CDMA2000 documents: the UMTS (CDMA) specific coverage predictions,
the AS analysis tab of the point analysis window, power control simulations and
neighbour automatic allocation.
To set the cut-off value, proceed as follows:
Either,
2) Right click on the Predictions folder to open the context menu,
Or
2) Double click on the Predictions folder,
Then
1) Left click on the Predictions tab from the open window,
2) In the Calculation limitation part of the dialog, enter the cut-off value.
This value is used as a filter criterion on interferers. Therefore, U-Net will discard all the
interferers, which the signal level is lower than this value.
5.7.4 Displaying Calculation Events in a Log Window
An event viewer window is available in U-Net. To make it open, use the View menu.
This window consists of two tabs, the Events and Tasks tabs.
I. Events tab
U-Net lists some events and provides for each of them, the type, the hour the event
occurred and a description. Events detailed in the Events tab concern PlaNET imports
and calculations (path loss matrices and coverage studies). You may encounter three
types of events, displayed with a specific symbol:
z Errors occurred during PlaNET import or calculations: U-Net does not stop the
import or calculation process; it automatically opens the Events tab to warn you.
z Warnings about minor problems happened during calculations. Be careful,
U-Net does not open the Events tab to inform you.
5-95
z Information on time a calculation or PlaNET import process is started and

ended.
Some features in order to manage events are available. To access them, right click on
the window in order to open the related context menu. Then you will be able to:
z Delete the selected event(s) (Clear command),
z Delete all the events (Clear all command),
z Copy the event description in the clipboard (Copy command),
z Display the entire event description (Properties command).
II. Tasks tab
The Tasks tab enables you to visualise progress of path loss matrix, prediction study,
UMTS, CDMA/CDMA2000 simulation calculations and neighbour allocation.
As calculation progress is managed in the Tasks tab, it is possible to work with U-Net
while calculations start.
The Tasks tab is automatically open as soon as calculations are started.
To interrupt calculations, click on the button, available in the Tasks tab.
Note:
z Messages listed in the events tab can be saved in a log file.
z The log window is automatically magnetised within the other set of U-Net windows.
To break this magnetism, and freely move this window, use the CTRL key when
dragging it.
5.7.5 Exporting Calculation Events in a Log File
The Event viewer window contains two tabs: Events and Tasks. The events tab displays
details about processes and potential errors, information and warnings.
Messages listed in this tab can be saved in a .log file. To do that, add an option when
starting U-Net from a command line, with the syntax above:
“C:\Program Files\Huawei GENEX\ U-Net 1.0\U-Net.exe” -log “C:\....\events.log”
5-96
Chapter 6
User Manual - Volume I GSM/GPRS/EDGE/TDMA Project
GENEX U-Net Wireless Network Planning Software Management
Chapter 6 GSM/GPRS/EDGE/TDMA Project

Management
6.1 Overview
GSM (Global System for Mobile communications) and DCS (Digital Communications
System) are radio technologies using TDMA (Time Division Multiple Access) principles,
each on a different frequency band.
In TDMA technologies, users are spread over frequency bands made of physical
channels. Each of these physical channels is divided into a certain number of logical
channels called timeslots. The norm in standard TDMA is 8 timeslots per channel. This
means that a channel can carry simultaneously 8 speaking users.
Even if users on a same physical channel do not interferer each other (spread on time),
every data carried on a physical channel can be potentially interfered by other
communications occurring on co-channel or on adjacent channel. The goal of planning
such a GSM/GPRS/EDGE network will be to provide a sufficient coverage to cover a
maximum area, to assign to transmitters enough channels in order to absorb the traffic
demand by limiting interferences in the network.
GPRS (Global Packet Radio Service) and EDGE (Enhanced Data-rates for GSM - or
Global - Evolution) are 2.5th numeric telephony norms working around the 900-1800
MHz band, using the also TDMA (Time Division Multiple Access) technology as
classical GSM norm. Contrary to GSM working in circuit switched mode, EDGE and
GPRS use timeslot working on packet switched mode, but can be mixed with GSM
timeslots on transmitters.
GSM and GPRS/EDGE projects share the same template. A station will be able to
allow both GSM and GPRS services depending on its properties. This will be set at the
subcell level with timeslot either dedicated to circuit, packet or composite services.
Each transmitter dealing with GPRS/EDGE must have a piece of GPRS/EDGE
equipment. U-Net allows the user to either create or modify easily this equipment.
These are linked with so-called coding schemes functions of C or C/I thresholds.
GPRS technology provides 4 coding schemes whereas EDGE can offer 9. With U-Net,
you can set these coding schemes and display their effects in graphs.
Since GPRS/EDGE technology is based on GSM norm, it is possible to define or not,
in the same network, transmitters as GPRS/EDGE stations.
Compared to GSM norm, GPRS/EDGE provides the support of larger amounts of data
services. Moreover, this technology permits to carry more data per timeslot.
6-1
Chapter 6
Depending on the radio data and the number of timeslots dedicated to packet service
transmissions for the transmitters part of the current network, U-Net can determine the
average capacity per timeslot per transmitter.
Geo data are easily manageable as in the other projects. You may either create or
import any of these data. Sites, antennas, station templates, transmitters,
measurements, and propagation models work in the same way for GSM/GPRS/EDGE
projects than for the other technology types. Nevertheless, the complexity of such a
modelling has led to the introduction of several specific radio data for
GSM/GPRS/EDGE in order to optimise the management of radio resources. As many
objects in U-Net, these data are easy to manage and use generic dialogs.
Multi-service traffic can be fully managed in U-Net through the settings of
GSM/GPRS/EDGE parameters (services, mobility types, terminals, user profiles,
environments), multi-service cartography (maps per environment, per user profile, live
traffic, user density). Mixing the network and all these multi-service data, traffic is
spread using the traffic capture feature.
Thanks to it, and by the use of a dimensioning model, it is possible to determine the
requested number of TRXs to absorb the traffic with regard to quality requirements.
The resource allocation can be made either manually or by using an Automatic
Frequency Planning.
Even if all common studies are available (coverage by transmitter, coverage by signal
level, overlapping) with some specific conditions due to GSM/GPRS/EDGE, U-Net
provides also some other specific coverage studies dealing with interferences:
interfered zones and coverage by C/I level and specific GPRS/EDGE coverages:
coding schemes and throughput per timeslot.
The resulting network can be analysed thanks to the availability of different tools
dealing with frequency plan check, channel location search and KPI calculation.
The What's this context tool allows the user to understand the specific
GSM/GPRS/EDGE fields and features available in the several dialog boxes.
6.2 GSM/GPRS/EDGE Projects Protocol

A classical GSM/GPRS/EDGE project protocol, within U-Net, is described below (see
Table 6-1):
6-2
Chapter 6
Table 6-1 Projects protocol
Project Description
z Choice of a project template

z Definition projection and display coordinate
Project initialisation systems
z Definition of length, reception and transmission
units
z Clutter classes
z Clutter heights
Definition of geographic
z DTM
data through the import or
z Vector data
the creation of maps
z Population data
z Generic data
Common coverage studies

(by transmitter, by signal None.
level, HCS layers, etc...)
z Determination of domains and groups

(frequencies, BSICs, HSNs)
z Setup of cell types
Network design: Setting
z Definition and tuning of transmitters and
radio data
subcells
z Coding scheme definitions
z Setup of GPRS/EDGE equipment
z Services
z Mobility types
Definition of multi-service
z Terminals
traffic parameters
z User profiles
z Environments
z Traffic maps per environment

Definition of the traffic
z Traffic maps per user profile
through the import or the
z Live traffic maps
creation of maps
z User density traffic maps
Capture of the traffic to

None.
analyse the demand
6-3
Chapter 6
Project Description
z Dimensioning model settings

Dimensioning of the z Required number of TRXs per transmitter to
network absorb the input traffic
z Determination of the traffic load per transmitter
Definition of the
neighbours manually or None.
automatically
z Manual allocation of frequencies

z Manual allocation of BCCH
Resource manual
z Manual allocation of BSICs
allocation
z GSM/GPRS/EDGE Automatic Frequency
Planning
z Frequency plan checking

Checking of the network
z Channel search tool
allocations
z KPI calculation
z Interference areas
GSM/GPRS/EDGE z Coverage by C/I level
oriented prediction studies z Coverage by coding schemes
z Coverage by rates per timeslot
6.3 Defining GSM/GPRS/EDGE Resources

6.3.1 Overview
In U-Net, radio network modelling needs the management of specific radio resources
data in GSM/GPRS/EDGE projects:
z Frequencies
z HSNs (Hopping Sequence Number)
z BSICs (NCC-BCC pairs)
As many other objects in U-Net, these parameters have been integrated to the tool
with a will to make their management and their use easy. These parameters are used
as inputs for cell types, subcells and TRXs in stations.
The resources are organised in domains, each domain being potentially made of
several groups. During the resource allocation, only items belonging to the defined
domains will be allowed to be chosen.
6-4
Chapter 6
Note:
For frequencies, the top layer is the frequency band. A frequency domain (made of
several groups) will be a part of a frequency band.
6.3.2 Frequencies
I. Overview
In U-Net, for a complete exploitation of frequencies, it is possible to define frequency

domains and groups based on standard frequency bands.
z A domain is a set of groups; it consists of one or several groups. A frequency
domain belongs to a frequency band; it is a subset of the frequency band.
z A group is a set of channels. A frequency group belongs to one or several
frequency domains; it is a subset of frequency domains.
Manual and automatic frequency planning is based on frequency domains assigned to
the TRX types in cell types.
The creation and the management of frequency domains and groups, like for many
other objects in U-Net is always easy and clear.
II. Managing frequency bands
Frequency bands represent the reference frequency set that frequency groups and
domains (which include specific rules, steps and exclusions) refer to. Frequency
bands can be seen as a fixed item, whereas groups and domains are the frequency
subsets that can be managed in order to check to available frequency lists.
Frequency band properties can be accessed in two ways, either from a frequency
band table, either from a frequency band dialog.
To open the frequency band dialog, proceed as follows:
2) Right click on the transmitters folder in order to get the related context menu.
3) Choose the Properties option from the open menu.
4) Click on the Frequencies tab.
5) Use the What's this help to get description about available fields in the open
window.
6) Select the frequency band you want to manage, then click the modify button to
open the associated dialog, or Double click the frequency band you want to
manage.
7) Click the General tab.
8) Define the frequency band parameters.
6-5
Chapter 6

10) Click again OK to close the transmitters properties dialog box.
Note:
z The Frequency domains tab lists the domains related to the current frequency
band.
z Addition, deletion of frequency bands are made using respectively the
and buttons.
z The button helps you to manage the content of the frequency band
table (See below).
To open the frequency band table, proceed as follows:

3) Choose the [Network settings: Frequency bands...] command from the open
menu.
4) Define the parameters of each frequency band.
Note:
z The dialog of each frequency band (see above) is reachable by either double
clicking the related record in the table, or by using the button once a
record is selected.
z The button helps you to manage the content of the frequency band
table.
z An Other Properties tab is available when some user defined fields have been
added to the Frequency band table.
III. Managing frequency domains and groups
For an easier resource management, frequency domain and group tables are
available. Frequency domains are linked to types of TRXs. When defining a cell type,
you must assign a frequency domain to each TRX type.
6-6
Chapter 6
To define domains and groups of frequencies, proceed as follows:

2) Right click on the transmitters folder to get the related context menu.
3) Choose the [Network settings: Domains: Frequencies...] command from the open
menu.
window.
5) In the Domains dialog, enter a domain per line and specify the related frequency
band. To validate a domain creation, select another line.
6) Select a domain in the table and click on the Properties... button, or select the
line relating to a domain and double click on it.
7) 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 frequency (Min channel number).
z The highest available frequency (Max channel number).
z The value interval between the frequencies (Step between channels).
z Frequency (frequencies) you do not want to use (Excluded channel numbers).
You can paste a list of channels; separator must be a blank character.
z Additional frequency (frequencies) you want to consider during allocation (Extra
channel numbers). You can paste a list of channels; separator must be a blank
character.
You can also define the domain-group pairs in the Group of frequencies window.
1) After defining all the domains, close the Domains dialog.
3) Choose the [Network settings: Groups: Frequencies...] command from the open
menu.
window.
5) In the Group of frequencies window, select a domain and associate one or
several groups of frequencies to each of them. Define the groups as explained
above.
The defined domains can be now assigned to TRX types of each cell type in order
then to be used as constraints in the automatic allocation of frequencies.
6-7
Chapter 6
6.3.3 HSNs
I. Overview
In U-Net, modelling of base frequency hopping and synthesised frequency hopping is

supported. So, some parameters such as MAL (Mobile Allocation List), HSN (Hopping
Sequence Number), and MAIO (Mobile Allocation Index Offset) are managed.
HSN (Hopping Sequence Number) parameter is used to describe frequency hopping
sequence; this is one of 4 input parameters for GSM hopping sequence generator
algorithm. HSN may take 64 different values; they are numbered from 0 to 63.
Frequency sequences are pseudo-random, except for the special case of HSN = 0,
where frequencies are used one after the other (cyclic hopping).
In U-Net, for a complete exploitation of HSNs, it is possible to define HSN domains
and groups.
z A domain is a set of groups; it consists of one or several groups.
z A group is a set of HSNs. A HSN group belongs to one or several HSN domains; it
is a subset of HSN domains.
Manual and automatic HSN planning is based on the HSN domains assigned to TRX
types in cell types.
Creation and management of HSN domains and groups, like for many other objects in
U-Net always stay easy and clear.
II. Managing HSN domains and groups
For an easier resource management, HSN domain and group tables are available.
HSN domains are linked to types of TRXs. When defining a cell type, you must assign
a HSN domain to each TRX type.
To define domains and groups of HSNs, proceed as follows:
3) Choose the [Network settings: Domains: HSNs...] command from the open menu.
window.
5) In the Domains dialog, you can enter a domain per line. To validate a domain
creation, select another line.
7) In the domain properties dialog, specify the name of group(s) included in this
domain and define for each of them:
z The lowest available HSN (Min).
z The highest available HSN (Max).
6-8
Chapter 6
z The value interval between the HSNs (Step).

z HSN(s) you do not want to use (Excluded). You can paste a list of HSNs;
separator must be a blank character.
z Additional HSN(s) you want to consider during allocation (Extra). You can paste a
list of HSNs; separator must be a blank character.
Note:
A default domain called “ALL HSNs” exists; it contains the 64 HSNs.
You can also define the domain-group pairs in the Group of HSNs window.
3) Choose the [Network settings: Groups: HSNs...] command from the open menu.
window.
5) In the Group of HSNs window, select a domain and associate one or several
groups of HSNs to each of them. Define the groups as explained above.
The defined domains can be now assigned to TRX types of each cell type in order
then to be used as constraints in the automatic allocation of HSNs.
6.3.4 BSICs
I. BSICs: Overview
In GSM/GPRS/EDGE, the BSIC (Base Station Identity Code) colour code is

associated with a BCCH in order for a mobile to distinguish the base station to which
both are assigned from the other surrounding ones. The BSIC is composed of a NCC
(Network Colour Code) and BCC (BTS Colour Code). NCC and BCC are integers
between 0 and 7.
Hence, the BSIC is a result of a (NCC-BCC) couple and can be noted using two types
of notation: octal or decimal. U-Net supports both syntaxes and will make its allocation
depending on the chosen format.
As available BSICs depend on the country and on the area; it is sometimes necessary
to distinguish borders from other zones. To model this, domain and group tables have
been created.
z A domain is a set of groups; it consists of one or several groups.
z A group is a set of BSICs. A BSIC group belongs to one or several BSIC domains.
6-9
Chapter 6
Therefore, a BSIC domain can contain more or less than 8 BSICs.

Manual or automatic BSIC planning is based on the BSIC domain assigned to
transmitter.
Creation and management of BSIC domains and groups, like for many other objects in
U-Net always stay easy and clear.
II. Defining BSIC format
The BSIC colour code is the result of two digits: NCC (Network Colour Code) and BCC
(BTS Colour Code). NCC and BCC are integers between 0 and 7. 64 BSICs are
available. They are distributed in 8 groups (one group per possible NCC) of 8 BSICs.
For each pair, it is possible to define a BSIC number, following either the octal or the
decimal notation (see Table 6-2).
Table 6-2 BSIC Format
Format Description
By considering NCC (Network Colour Code [0..7]) and BCC

(Base station Colour Code [0..7]), it is possible to build a
Decimal format
BSIC number with the rule: NCCx8 + BCC. For example, the
(3-2) pair leads to a BSIC value of 26.
The octal rule is identical to the decimal rule, except the fact
Octal format that 8 is replaced by 10 (NCCx10 + BCC). For the case
above, the (3-2) pair drives to a value of 32 in octal format.
To choose the BSIC format globally for a project, proceed as follows:

4) Click the BSIC format tab.
5) Select either the Octal or Decimal option in the Display format scrolling box
6-10
Chapter 6
Note:
z When defined, the selected BSIC format will be taken into account by the BSIC
manual allocation (i.e. only values consistent when the selected choice are
available in the BSIC scrolling box – TRX tab of transmitter property dialog), the
AFP and Audit tool.
z Take care about the definition of the BSIC domain, in order to be consistent with
the chosen BSIC notation.
z It is still possible to enter the BSIC in NCC-BCC format in the TRX tab of the
transmitter dialog. Depending on the BSIC format, U-Net will translate the
NCC-BCC pair in BSIC number.
z The BSIC format has to be defined correctly prior to the Test mobile data imports.
III. Managing BSIC domains and groups
For an easier resource management, BSIC domain and group tables are available.
You must assign a BSIC domain to each transmitter.
To define domains and groups of BSICs, proceed as follows:
3) Choose the [Network settings: Domains: BSICs...] command from the open
menu.
window.
5) In the Domains dialog, you can enter a domain per line. To validate a domain
creation, select another line.
7) 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 BSIC (Min).
z The highest available BSIC (Max).
z The value interval between the BSICs (Step).
z The BSIC(s) you do not want to use (Excluded). You can paste a list of BSICs;
separator must be a blank character.
z Additional BSIC (s) you want to consider during allocation (Extra). You can paste
a list of BSICs; separator must be a blank character.
6-11
Chapter 6
Note:
A default domain called “ALL BSICs” exists; it contains the 64 BSICs in 8 groups (NCC
= 0, ..., 7).
You can also define the domain-group pairs in the Group of BSICs window.
3) Choose the [Network settings: Groups: BSICs...] command from the open menu.
window.
5) In the Group of BSICs window, select a domain and associate one or several
groups of BSICs to each of them. Define the groups as explained above.
The defined domains can be now assigned to each transmitter in order then to be
used as constraints in the automatic allocation of BSICs.
6.4 Managing GSM/GPRS/EDGE Radio Data

6.4.1 Overview
In U-Net, radio network modelling and radio resource management has lead to the
introduction of specific radio data for GSM/GPRS/EDGE projects:
z HCS layers
z Timeslot configurations
z TRX types and Cell types
z Subcells
z GPRS/EDGE Equipment
As many other objects in U-Net, these parameters have been integrated to the tool
with a will to make their management and their use easy. By their use, it is possible to
define subcells and TRXs of stations.
Thanks to this advanced description level, concentric cells are supported. In addition,
modelling of several hopping modes is supported: no hopping, Base Band Hopping
and Synthesised Frequency Hopping. Some parameters such as MAL (Mobile
Allocation List), HSN (Hopping Sequence Number), and MAIO (Mobile Allocation
Index Offset) are managed.
6-12
Chapter 6
6.4.2 HCS Layers
I. Overview
In U-Net, It is possible to model hierarchical networks. Indeed, you may define several
types of layers, a given priority and a threshold speed on each of them, and then,
assign one of them to transmitters.
Hierarchical cells are taken into account (including priority) in any prediction study (e.g.
coverage by transmitter, interfered zones and coverage by C/I levels) based on search
for best server for coverage conditions. The threshold speed is used for the traffic
distribution as a filter criterion on the mobility. Only mobiles with a mobility lower than
the maximum speed will be considered eligible to reside on the layer.
II. Managing HCS layers
In U-Net, HCS layers are listed in a table form. Hence, their management (creation,
deletion or modification) is identical to standard management of data in tables.
To manage HCS layers that will be available to assign to transmitters, proceed as
follows:
3) Choose the [Network settings: HCS Layers...] command from the open menu.
4) Define and modify each HCS layer with its name, and its related priority, by
editing cells.
The priority of each HCS layer is taken into account in coverage predictions, when
considering, on each pixel, the server which has the highest signal level on the highest
priority layer.
You can also assign a threshold speed to each HCS layer. This speed threshold is
used to distribute traffic over different network layers using the mobility criterion.
Mobiles with a mobility of less than the threshold speed for a layer can reside on that
layer.
Note:
Priority is organised in ascending order, i.e. 1 has higher priority than 0 (lowest
priority).
III. Assigning HCS layers to transmitters
To assign a HCS layer among existing ones to a transmitter, proceed as follows:
6-13
Chapter 6
Either:
3) Right click on the transmitter which you want to assign a HCS layer to.
or
1) Select on the map the transmitter which you want to assign a HCS layer to by
left clicking on the appropriate Tx symbol (arrow).
Then
window.
3) Click on the General tab.
4) Choose the HCS layer to assign to the current transmitter in the associated
scrolling menu.
Note:
z Layer priority is automatically assigned to transmitter. This parameter maybe taken
into account in GSM/GPRS/EDGE coverage conditions in prediction studies.
z The threshold speed is used for the traffic distribution as a filter criterion on the
mobility. Only mobiles with a mobility lower than the maximum speed will be
considered eligible to reside on the layer.
z Assigning HCS layers to transmitters is optional.
6.4.3 Timeslot Configurations
I. Overview
It is possible to define timeslot configurations that can be used in allocating different

timeslot types to TRXs. A timeslot configuration defines the distribution method for
circuit, packet and shared timeslots on a TRX. Timeslot configurations influence the
network dimensioning results (evaluation of the number of TRXs required to fulfill the
traffic demand) and calculation of Key Performance Indicators (KPIs).
6-14
Chapter 6
Note:
Shared timeslots are used for both, circuit-switched and packet-switched calls,
circuit-switched timeslots for circuit-switched / GSM calls and packet-switched
timeslots in case of packet-switched / EGPRS calls.
II. Managing timeslot configurations
To create and describe a timeslot configuration, proceed as follows:

1) Right click on the Transmitters folder.
2) In the context menu, choose Network settings and Timeslot configurations
command.
3) In the List of timeslot configurations dialog, type the name of a new configuration
in the table.
4) In the table, select the row including the configuration and then, either click on
Properties or double click.
5) In the configuration property dialog, indicate the distribution of circuit, packet and
shared timeslots for each TRX.
6) A TRX per row is described in the table: enter the TRX number and specify the
corresponding number of circuit, packet and shared timeslots. When there is not
enough number of TRXs, U-Net uses the timeslot distribution assigned to the last
TRX.
7) Click OK to validate the timeslot configuration description.
8) Click on Close.
Note:
z Three default timeslot configurations (one per TRX type: BCCH, TCH and
TCH_INNER) are available.
z The fields defined at the subcell level "Number of packet (circuit or shared)
timeslots" are used when no timeslot configuration is defined.
6.4.4 Cell Types
I. Overview
In U-Net, a cell type describes the types of TRXs that a cell can use and their
parameters, which can be different.
Examples: Default cell types are available in the tool:
6-15
Chapter 6
z The cell type GSM900_N_NORMAL (a non concentric GSM900 normal cell)

contains BCCH and TCH TRXs.
z The cell type DUALBAND_CC_MINI (a concentric dual band cell) contains BCCH,
TCH and TCH_INNER TRXs.
Cell types are linked to station templates or transmitters. Indeed, when defining a
station template or transmitter properties, you must specify the cell type which the
station or transmitter refers to.
Creation and management of cell types, like for many other objects in U-Net always
stays easy and clear.
II. TRX types: definition
By default, three types of TRXs are modelled in U-Net:

z The BCCH TRX type: this TRX type is the BCCH carrier.
z The TCH TRX type which is the default traffic carrier.
z The TCH_INNER TRX type: this TRX type is the inner traffic carrier.
Note:
You can define additional TRX types directly from the GSM_EGPRS.mdb document
template.
The cell type definition must include a TRX type, which is the BCCH carrier (BCCH
TRX type), and a TRX type, which is the default traffic carrier (TCH TRX type). Only
one TRX type carrying the broadcast and only one TRX type carrying the default TCH
are supported.
TRX types are the standard elements which compose cell types.
III. Managing cell types
Cell types are linked to station templates or transmitters. Indeed, when defining a
station template or transmitter properties, you must specify the cell type which the
station or transmitter refers to.
Cell type properties can be accessed in two ways, either from a Cell type table, either
from a Cell type dialog.
To open the cell type dialog, proceed as follows:
3) Choose the Properties option from the open menu.
4) Click on the Cell types tab.
6-16
Chapter 6
5) Use the What's this help to get description about available fields in the open
window.
Either
6) Select the cell type you want to manage,
7) Click the modify button to open the associated dialog.
Or,
6) Double click the cell type you want to manage.
Then
1) Click the General tab.
2) Define the cell type parameters.
4) Click again OK to close the transmitters properties dialog box.
Note:
z Addition, deletion of cell types are made using respectively the and
buttons.
z The button helps you to manage the content of the cell type table
(See below).
To open the cell type table, proceed as follows:

3) Choose the [Network settings: Cell types...] command from the open menu.
Either
4) Select the cell type you want to manage.
5) Click the modify button to open the associated dialog.
Or,
4) Double click the cell type you want to manage.
5) Define the parameters of each cell type.
6-17
Chapter 6
Note:
z The dialog of each cell type (see above) is reachable by either double clicking the
related record in the table, or by using the button once a record is

selected.
z The button helps you to manage the content of the cell type table.
z An Other Properties tab is available when some user defined fields have been
added to the Cell type table.
IV. Cell type parameters
In the cell type properties window, you can rename it, enter the types of TRXs (BCCH,
TCH, and TCH_INNER) used by this cell type and specify for each of them:
z The assigned frequency domain
Only channels belonging to this frequency domain will be allocated to TRXs during
automatic or manual frequency planning.
z Maximum MAL (Mobile Allocation List) length
This is the maximum size of the MAL. In other words, it corresponds to the maximum
number of channels allocated to TRXs of a subcell during automatic frequency
planning in case SFH (Synthesized Frequency Hopping) or BBH (Base Band Hopping)
is supported and allocation mode is free.
z Allocation mode
It refers to the allocation strategy used during manual or automatic frequency planning.
Two allocation strategies are offered (see Table 6-3):
Table 6-3 Allocation mode
Allocation mode Description
all the channels of the frequency domain can be assigned

Free allocation
to TRXs.
Only channels belonging to a same group of the frequency

Grouped allocation
domain can be chosen.
z Min C/I
This is a quality condition; you can enter specific quality requirements for each TRX
type. It can be used as reference value in interference studies and in AFP.
6-18
Chapter 6
z % max interference
This is the maximum percentage of interfered area or interfered traffic that U-Net must
not exceed during automatic frequency planning.
z Default DL power offset
This is a reduction of power relative to the transmitter power. It enables you to model
power control of TCH TRXs and concentric cells (TCH_INNER TRXs that transmit a
power lower than BCCH TRX and TCH TRXs).
z Default hopping mode
Here, you can specify if frequency hopping technology is supported for this TRX type.
If frequency hopping is supported, choose either the Base Band Hopping mode (BBH),
or the Synthesized Hopping mode (SFH). Else, select Non Hopping.
z Default reception threshold
This is the reception condition for this TRX type. You can enter a specific reception
condition for each TRX type.
z AFP weight
This is a cost factor used to increase or decrease the importance of a TRX type during
automatic frequency planning. The cost factor must be a positive real. The higher the
AFP weight is, the higher the constraint on the TRX type is.
z HSN domain
Only HSNs belonging to this HSN domain will be allocated to subcells during
automatic or manual frequency planning. Allocation of HSN is performed in case of
BBH or SFH.
z Freeze HSN
Selecting this option enables you to keep the current HSN allocation of subcells
related to this TRX type when starting a new AFP session.
z DTX support (default)
Here, you can specify if DTX (Discontinuous Transmission) technology is supported
for this TRX type.
z Number of circuit TS (default)
circuit
This is the number of time slots per TRX dedicated to circuit traffic (voice) ( NTS ).
z Number of packet TS (default)
packet
This is the number of time slots per TRX supporting packet traffic ( NTS ).
z Number of composite TS (default)
6-19
Chapter 6
This is the number of time slots per TRX supporting both voice and packet traffic
composite
( NTS ).
Note:
These time slots are exclusively dedicated to traffic channels; they are not used for
BCCH and CCCH (Control Common Channels).
In case of BCCH TRX type, at least one time slot is used for BCCH. So, we have:
NTS
circuit
+ NTS
packet
+ NTS
composite
≤ F multiplexing − 1
In case of TCH or TCH_INNER TRX types, we have:
NTS
circuit
+ NTS
packet
+ NTS
composite
= F multiplexing
F multiplexi ng is the multiplexing factor of the frequency band, which the frequency domain
assigned to this TRX type belongs to.
The number of requested TRXs for voice traffic depends on these values. In case of
GPRS/EDGE stations, U-Net considers only time slots available for voice traffic
( NTS
circuit
+ NTS
composite
). If the GPRS/EDGE option is not selected (GSM station), U-Net
considers all the time slots ( NTS

circuit
+ NTS
packet
+ NTS
composite
).
Important:
The fields “Number of shared timeslots per TRX”, “Number of circuit timeslots per
TRX” and “Number of packet timeslots per TRX” are available in the cell type
description but are used in calculations only if no timeslot configuration is defined
(described below).
z Default hysteresis
This parameter is not used in this U-Net version.
This is a default value of a subcell specific parameter. It denotes the handover
hysteresis margin (when going below min reception level). It concerns intra-cell
handovers only.
z Priority
If a probe mobile can be served by more than one subcell of a transmitter, the subcell
that has a higher service priority will serve it.
z Half-rate traffic ratio
6-20
Chapter 6
It is the percentage of Half-Rate voice traffic in the subcell. This parameter is taken
into account to calculate the required number of timeslots to satisfy the voice traffic
demand.
z Traffic overflow target
This parameter is used during the traffic analysis to distribute the traffic between
subcells and layers. For a given subcell, this parameter is the percentage of candidate
traffic considered to overflow to another subcell with a lower priority. It impacts the
traffic capture between Inner and Outer subcells, as well as between micro and macro
layers. In other words, it is a kind of anticipation of the percentage of traffic rejected
from higher priority subcells/layers to lower ones.
Note:
If the traffic overflow target is set to a value lower than the Grade of Service, it implies
that the traffic rejected (according to the dimensioning model, Erlang B or Erlang C)
will be considered lost and will not overflow to other subcells.
z Timeslot configuration name

Name of the timeslot configuration describing the distribution of circuit, packet and
shared timeslots on TRXs of a subcell.
When a cell type is assigned to a transmitter, its parameters are used to initialise the
properties of the transmitter subcells. If you modify the values in the TRX types of the
cell types afterwards, these are not updated automatically in the subcells which were
already set with the previous values.
V. Examples of cell types
Two examples of cell types provided by default in U-Net are explained below:
1) Normal cell type
A normal cell type consists of two TRX types:
z BCCH TRX type
z TCH TRX type
The table below (see Table 6-4) described parameters to be specified for any selected
hopping mode.
6-21
Chapter 6
Table 6-4 Hopping mode
Characteristics Used in U-Net Hopping mode
Non BBH SFH

hopping
Frequency domain Automatic or x x x

manual frequency
planning
Maximum MAL Automatic Not used x x

(Mobile Allocation frequency
List) length planning
Allocation mode Automatic or x x x

manual frequency
planning
Min C/I Interference x x x

studies,
Automatic
frequency
planning
% max interference Automatic x x x

frequency
planning
Default DL power Signal level = 0 for = 0 for = 0 for

offset studies BCCH BCCH BCCH
= 0 for TCH = 0 for = 0 for TCH
TCH
Default hopping Interference Non Base Synthesized

mode studies Hopping Band Hopping
Hopping
Default reception Signal level x x x

threshold studies
AFP weight Automatic x x x

frequency
planning
6-22
Chapter 6
Non BBH SFH

hopping
HSN domain Automatic Not used x x

frequency
planning
Freeze HSN Automatic x x x

frequency
planning
DTX support Automatic x x x

(default) frequency
planning,
Interference
studies
Number of Number of x x x
composite TS requested TRXs,
(default) GPRS-like studies
Number of packet Number of x x x

TS (default) requested TRXs,
GPRS-like studies
Number of circuit Number of x x x

TS (default) requested TRXs,
GPRS-like studies
Default hysteresis Not used Not used Not used Not used
Priority Not used Not used Not used Not used
Half-rate traffic ratio Traffic analysis x x x
Target rate of traffic Traffic analysis x x x

overflow
Timeslot Dimensioning x x x
configuration
6-23
Chapter 6
Non BBH SFH

hopping
Frequency domain Automatic or x x x

manual frequency
planning
Maximum MAL Automatic Not used x x

(Mobile Allocation frequency
List) length planning
2) Concentric cell type

A concentric cell type consists of three TRX types:
z BCCH TRX type
z TCH TRX type
z TCH_INNER
The table below (see Table 6-5) described parameters to be specified for any selected
hopping mode.
Table 6-5 Hopping mode
Non BBH SFH

hopping
Frequency Automatic or manual x x x

domain frequency planning
Maximum MAL Automatic frequency Not used x x

(Mobile planning
Allocation List)
length
Allocation mode Automatic or manual x x x

frequency planning
Min C/I Interference studies, x x x

Automatic frequency
planning
6-24
Chapter 6
Non BBH SFH

hopping
% max Automatic frequency x x x

interference planning
Default DL = 0 for = 0 for = 0 for

power offset Signal level studies BCCH BCCH BCCH
=> 0 for => 0 for => 0 for
TCH TCH TCH
<> 0 for <> 0 for <> 0 for
TCH_INNE TCH_IN TCH_INNE
R NER R
Default hopping Interference studies Non Base Synthesized

mode Hopping Band Hopping
Hopping
Default Signal level studies x x x

reception
threshold
AFP weight Automatic frequency x x x

planning
HSN domain Automatic frequency Not used x x

planning
Freeze HSN Automatic frequency x x x

planning
DTX support Automatic frequency x x x

(default) planning,
Interference studies
Number of Number of requested x x x

composite TS TRXs,

packet TS TRXs,
6-25
Chapter 6
Non BBH SFH

hopping

circuit TS TRXs,
Default Not used Not used Not used Not used

hysteresis
Priority Not used Not used Not used Not used
Half-rate traffic Traffic analysis x x x

ratio
Target rate of Traffic analysis x x x

traffic overflow
Timeslot Dimensioning x x x
configuration
Frequency Automatic or manual x x x

domain frequency planning
Maximum MAL Automatic frequency Not used x x

(Mobile planning
Allocation List)
length
VI. Assigning cell types to transmitters
A cell type consists in TRX types (BCCH, TCH or TCH inner). Assigning a cell type to a
transmitter enables you to define its subcells (TRX type properties become subcell
properties). A subcell corresponds to the transmitter-TRX type pair.
To assign a cell type to a transmitter, proceed as follows:
Either:
3) Right click on the transmitter you want to manage.
or
6-26
Chapter 6
Then
2) Click on the TRXs tab of the current dialog.
4) Click on the scrolling menu and choose a cell type in the list.
Note:
z If you modify the settings of a Cell type which is already assigned to a transmitter,
U-Net does not update transmitter subcell characteristics automatically.
z Once selected, cell type property dialog can be open by clicking on the
button.
z U-Net indicates the main frequency band of the transmitter. This is the frequency
band, which the frequency domain assigned to BCCH TRX type belongs to. U-Net
takes into account this frequency band in path loss matrix evaluation.
6.4.5 Subcells
I. Managing subcells in transmitters
The subcells of transmitter and their settings are defined in this part. A subcell is a
group of TRXs sharing the same radio characteristics, the same quality (C/I)
requirements, and common settings. A subcell is defined by the transmitter-TRX type
pair.
Subcells of transmitter and their settings depend on the cell type selected for the
transmitter. The cell type predefines the TRX type of each subcell since the properties
of each TRX type initialise the ones of each subcell. The default values reported for
subcells can be modified without changing reference for the cell type. On the other
hand, U-Net updates subcell characteristics when selecting another cell type.
Except their TRX type (coming from the selected cell type), all subcell properties are
editable and can be modified in the subcell part of any transmitter property.
To access the subcell table from the transmitter properties, proceed as follows:
Either:
6-27
Chapter 6

or
Then
4) Define the Subcell settings in the subcell part.
II. Displaying the subcell list
Even if subcells are linked to transmitters, it is possible to display all existing subcells
of a network in an editable form.
To open the subcell general table, proceed as follows:
3) Choose the [Subcells: Open Table] command from the open menu.
4) Define the Subcell settings.
The button helps you to manage the content of the subcell table.
III. Subcell property details
Whatever is the way to reach subcell properties (from transmitter properties or from
the subcell table), for any of them, U-Net details:
z Requested TRXs
This is the number of TRXs requested for a subcell. In case of BCCH TRX type, the
number of requested TRXs is 1 by default. In case of TCH or TCH_INNER TRX type,
this is a network dimensioning result, which depends on the traffic density in the
subcell and on the blocked call percentage.
z Traffic load
It indicates the usage rate of TRXs; its value is between 0 and 1. This parameter may
be, either user-defined, or automatically reported after calculating the number of
requested TRXs. In this case, traffic load ( Ltraffic ) is a dimensioning result; this is a
global traffic load for all the subcells of each transmitter. We have:
6-28
Chapter 6
Traffic
Ltraffic =
NTRX
Traffic is the traffic request (Erlang) on the transmitter coverage area,
NTRX is the total number of TRXs requested by a transmitter.
It is taken into account in interference calculation and automatic frequency planning.

z HSN
This is the hopping sequence number of subcell. All the TRXs of the subcell have the
same HSN. HSN can be manually entered or automatically allocated. Only HSN
belonging to the HSN domain assigned to this TRX type (in the selected cell type
property dialog) can be allocated. This parameter is taken into account in interference
calculation in case of SFH or BBH.
z Synchronisation
Type the same string of character in order for the TRXs of several subcells is
synchronized during frequency hopping. By default, synchronization is performed at
the site level; TRXs of subcells on a same site are synchronized. You may also define
synchronization at the subcell level (different values for each subcell) or group of
transmitters level (unique value for subcells of this group).
Note:
z Any string of character can be entered.
z This field is case sensitive.
This parameter is taken into account in interference calculation in case of frequency

hopping (BBH or SFH).
z DL power offset
This is a reduction of power relative to the transmitter power. Entering 3 dB means that
the subcell power will be 3 dB lower than the transmitter power defined in the
Transmitter tab.
z Hopping mode
If frequency hopping is supported, choose either the Base Band Hopping mode (BBH),
or the Synthesized Hopping mode (SFH). Else, select Non Hopping.
z Reception threshold
This is the reception condition for the subcell. This value can be used as reference
value in signal level coverage predictions (lowest received signal level in order for
receiver to be covered by the subcell).
6-29
Chapter 6
z Hysteresis
z DTX supported
Select this option if DTX (Discontinuous Transmission) technology is supported for the
subcell.
z Number of circuit TS (default)
circuit
This is the number of time slots per TRX dedicated to circuit traffic (voice) ( NTS ).
z Number of packet TS (default)
packet
This is the number of time slots per TRX supporting packet traffic ( NTS ).
z Number of composite TS (default)

This is the number of time slots per TRX supporting both voice and packet traffic
composite
( NTS ).
Note:
These time slots are exclusively dedicated to traffic channels; they are not used for
BCCH and CCCH (Control Common Channels).
In case of BCCH TRX type, at least one time slot is used for BCCH. So, we have:
NTS
circuit
+ NTS
packet
+ NTS
composite
≤ F multiplexing − 1
In case of TCH or TCH_INNER TRX types, we have:
NTS
circuit
+ NTS
packet
+ NTS
composite
= F multiplexing
F multiplexi ng is the multiplexing factor of the frequency band, which the frequency domain
assigned to this TRX type belongs to.
The number of requested TRXs for voice traffic depends on these values. In case of
GPRS/EDGE stations, U-Net considers only time slots available for voice traffic
( NTS
circuit
+ NTS
composite
). If the GPRS/EDGE option is not selected (GSM station), U-Net
considers all the time slots ( NTS

circuit
+ NTS
packet
+ NTS
composite
).
6-30
Chapter 6
Important:
The fields “Number of shared timeslots per TRX”, “Number of circuit timeslots per
TRX” and “Number of packet timeslots per TRX” are available in the cell type
description but are used in calculations only if no timeslot configuration is defined
(described below).
z Excluded
When defining frequency domains, you have to choose the range of channels, the
step, exceptional and excluded channels. Excluded channels are channels that are in
the defined range that you do not want to make allocatable. Excluded channels can be
set first in the frequency domain definition. In addition, you can also define less
constraining domains (with less excluded channels) and define excluded channels at
the subcell level. All subcells related to this domain must not have access to these
excluded channels for the allocation.
Note:
z 1. Channels must be separated by a blank character.
z 2. When defined, the excluded channels (per subcell) will be taken into account by
the frequency manual allocation (i.e. only consistent values are available in the
TRX channel scrolling box – TRX tab of transmitter property dialog), the AFP and
Audit tool.
z 3a. In Non Hopping mode or Base Band Hopping, in Free or Group Constrained
strategy, excluded channels are not visible in their related domains. So, subcells
are allocated with consistency within their defined domain.
z 3b. In Synthesized Frequency Hopping, in Free strategy, excluded channels are
not visible any more in their related domains.
z 3c. In Synthesized Frequency Hopping, in Group Constrained strategy, since the
allocation is made per exact group, as soon as a group has a defined excluded
channel, the complete group is excluded from the domain. The allocation (and what
is visible in frequencies scrolling boxes) is then possible only over groups with
initially no excluded channel.
These 3 rules are checked by the Audit tool.

z Assigned frequency domain
Only channels belonging to this frequency domain will be allocated to TRXs during
automatic or manual frequency planning.
6-31
Chapter 6
z Maximum MAL (Mobile Allocation List) length,

This is the maximum size of the MAL. In other words, it corresponds to the maximum
number of channels allocated to TRXs of a subcell during automatic frequency
planning in case SFH (Synthesized Frequency Hopping) or BBH (Base Band Hopping)
is supported and allocation mode is free.
z Allocation mode
It refers to the allocation strategy used during manual or automatic frequency planning.
Two allocation strategies are offered:
- Free allocation: all the channels of the frequency domain can be assigned to TRXs.
- Grouped allocation: Only channels belonging to a same group of the frequency
domain can be chosen.
z Min C/I
This is a quality condition; you can enter specific quality requirements for each subcell.
It can be used as reference value in interference studies.
z % max interference
This is the maximum percentage of interfered area or traffic (defined during the
interference histogram determination) that U-Net must not exceed during automatic
frequency planning.
z AFP weight
This is a cost factor used to increase or decrease the importance of a subcell during
automatic frequency planning. The cost factor must be a positive real. The higher the
AFP weight the greater the constraint on the subcell.
z HSN domain
Only HSNs belonging to this HSN domain can be allocated to subcells during manual
frequency planning. Allocation of HSN must be performed in case of SFH or BBH.
z Freeze HSN
Selecting this option enables you to keep the current HSN allocation of subcells
related to this TRX type when running a new AFP.
z Half-rate traffic ratio
It is the percentage of Half-Rate voice traffic in the subcell. This parameter is taken
into account in the traffic analysis and to calculate the required number of timeslots to
match the voice traffic demand.
z Traffic overflow target
This parameter is used during the traffic analysis to distribute the traffic between
subcells and layers. For a given subcell, it is the percentage of candidate traffic
considered to overflow to another subcell with a lower priority. It impacts the traffic
6-32
Chapter 6
capture between Inner and Outer subcells, as well as between micro and macro layers.
In other words, it is a kind of anticipation of the percentage of traffic rejected by higher
priority subcells/layers to lower ones.
Important:
The traffic overflow target and the Half-Rate traffic ratio must be the same for BCCH
and TCH subcells. If you enter different values for BCCH and TCH subcells, U-Net will
take the BCCH subcell values.
z Timeslot configuration name
Name of the timeslot configuration describing the distribution of circuit, packet and
shared timeslots on TRXs of a subcell.
z Required number of shared timeslots
This is the number of shared timeslots required for all the TRXs of a subcell.
z Required number of circuit timeslots
This is the number of circuit switched timeslots required for all the TRXs of a subcell.
z Required number of packet timeslots
This is the number of packet switched timeslots required for all the TRXs of a subcell.
z Effective rate of traffic overflow
This is the percentage of traffic overflowing from a subcell.
Note:
The last four fields contain results from the dimensioning process.
With this data model, all data contained in cell types become default ones, i.e. they are
used to initialise subcell properties when creating a transmitter; they can be modified
in the transmitter property dialog without modifying the default values defined for the
cell type, which the transmitter refers to. If you modify one of these data in cell types,
transmitters already dealing with these cell types will not have their default parameters
modified.
6.4.6 GPRS/EDGE Equipment
I. Creating a GPRS/EDGE equipment
A folder called GPRS/EDGE equipment is available in the Explorer window Data tab. It
enables you to manage specific equipment for GPRS and EDGE networks.
Thresholds associated with coding schemes are defined in these equipment. Any
6-33
Chapter 6
transmitter dealing with GPRS or EDGE technology has to be assigned an existing

piece of equipment.
To create a new GPRS/EDGE equipment, proceed as follows:
3) Choose the [Equipment: GPRS/EDGE Equipment...] command from the open
menu.
4) Fill the empty table line in order to create the new piece of equipment.
5) Click the button to open the related complete dialog.

window.
7) Set the GPRS/EDGE equipment settings.
8) Click OK or Apply to achieve the creation.
Note:
z The button helps you to manage content of the GPRS/EDGE

Equipment table.
z An Other Properties tab is available if some user defined fields have been added to
the GPRS/EDGE Equipment table.
II. Managing GPRS/EDGE equipment properties
In U-Net, it is possible to modify properties (name, number of coding schemes,

thresholds and associated graphs) of any existing equipment. These equipment have
to be defined for each transmitter taking part in specific GPRS/EDGE coverage
predictions (Coding schemes and Max rate per timeslot). The user can define the
technology supported by this equipment (whether GPRS or EGPRS).
To manage an GPRS/EDGE equipment, proceed as follows:
3) Choose the [Equipment: GPRS/EDGE Equipment...] command from the open
menu.
4) The associated Data table opens.
5) Define the parameters of each GPRS/EDGE Equipment.
6-34
Chapter 6
Note:
z The dialog of each GPRS/EDGE Equipment is reachable either by double clicking
the related record in the table, or by using the button once a record is
selected.
z The button helps you to manage content of the GPRS/EDGE

Equipment table.
z An Other Properties tab is available if some user defined fields have been added to
the GPRS/EDGE Equipment table.
III. Setting coding schemes parameters
In GPRS or EDGE technology, the coding scheme is a coding algorithm used to

introduce more or less redundancy (rate multiplier) and improve packet transmission.
Four and nine coding schemes are respectively available for GPRS and EDGE
networks. The more important the coding scheme is, the less redundancy there is.
Therefore, in GPRS networks, using a coding scheme 4 means that there will be no
redundancy.
To adjust the parameters associated with coding schemes from any equipment,
proceed as follow:
1) Access the property dialog of the equipment you want to adjust the associated
coding schemes.
window.
3) Click on the General tab to check or modify, for the current equipment:
z The name and/or the maximum number of coding schemes available for the
current equipment.
z If the equipment supports only GPRS or both GPRS and EDGE.
4) Click on the Thresholds tab to define, for each coding scheme:
z Power threshold and Signal noise ratio threshold: They are respectively the
minimum power (C) and the minimum signal noise ratio (C/I) required at the
receiver in order for the coding scheme to be used.
z Max rate (kbps): It is the maximum rate (kbps) obtained when there is no data
transmission error.
z Rates depending on C (kbps) and rates depending on C/I (kbps): These
columns contain values used to represent Rate=f(C ) and Rate=f(C/I) graphs.
z 8PSK modulation used or not (EDGE only).
6-35
Chapter 6
The and buttons allows to display graphs associated with

the currently selected coding scheme.
Note:
In the case of GPRS/EDGE, two sets of charts (C and C/I) can be given: one is related
to the GPRS mode and another one related to the EDGE mode. If the option Edge is
not checked, U-Net considers that the charts (C and C/I) are related to the GPRS
mode, else it uses them as charts related to the EDGE mode.
IV. Displaying rate graphs
In GPRS/EDGE technology, coding schemes are linked with data transmission

redundancy level. The least redundancy deals with riskier data transmissions with
potentially higher transmission rates. The most redundancy deals with safer data
transmissions but with lower rates. Coding schemes are hence defined in order to
obtain the best compromise between enough transmission speed and safety of data
packet transmission. That is why each coding scheme has an optimum working range
depending on either C or C/I values. This can be pointed out through graphs attached
with the definition of each coding scheme linked to GPRS/EDGE equipment.
To display the rate graph as function of C or C/I values for a given coding scheme,
proceed as follows:
1) Access properties dialog box of the equipment you want to adjust the
associated coding schemes.
window.
3) Click on the Thresholds tab.
Either,
4) Click on the C or C/I cell you want to display the associated rate graph,
Or,
4) Select the line of the coding scheme you want to display a rate graph,
Then
1) Click either the or button to open the graph (as

function respectively of C or C/I) dialog window.
6-36
Chapter 6
2) The Rate graph window opens. It consists of a table where you can define C
(or C/I) and rate values (copying and pasting a set of values, adding and deleting
values is possible) and a part where the graph is displayed.
3) Click OK or close the window.
Note:
These graphs show the rate evolution depending on radio conditions (C and C/I) by
considering block error rates. Therefore, from these graphs, you can choose a coding
scheme suitable to radio conditions.
V. Setting GPRS/EDGE transmitters
In U-Net, transmitters part of network dealing either with GPRS or EDGE can be or not
considered as GPRS/EDGE sectors by default. If not, they are taken as classical GSM
stations.
To assign GPRS/EDGE properties to any transmitter, proceed as follows:
Either,
2) Double click the Transmitters folder to open the associated table.
3) Check the boxes associated with such transmitters in the GPRS/EDGE column.
4) Assign the associated GPRS/EDGE to cells.
Or
2) Access the properties dialog box of the transmitter you want to define as an
GPRS/EDGE station.
Then
1) Click on the GPRS/EDGE tab.
2) Use the What's this help to get description about the fields available in the current
window.
3) Check the GPRS/EDGE Station box and complete the GPRS/EDGE equipment
field.
6-37
Chapter 6
Note:
z When choosing the equipment, all pieces of equipment previously described in the
GPRS/EDGE equipment folder are available in the GPRS/EDGE equipment
scrolling menu. If none is chosen, U-Net does not consider the associated
transmitter in the GPRS/EDGE specific studies.
z The number of coding schemes limits the number of coding schemes of the
associated equipment that the E/GPRS station can use.
z Example: Let a GPRS station use an equipment with four coding schemes. The
number of supported coding schemes has been set to 2. It means that the station
will use only the first two coding schemes (1 and 2).
z The average 8PSK Power Backoff is the average power reduction for E/GPRS
transmitters due to 8PSK modulation in EDGE.
z All these inputs are also available in the station template description.
6.5 GSM/GPRS/EDGE Traffic Management

6.5.1 Overview
The U-Net GSM/GPRS/EDGE traffic model is flexible, versatile and comprehensive.

This traffic model introduces the notion of service in the GSM/GPRS/EDGE
documents allowing the user to completely model the multi-service 2G/2.5G network
traffic. The salient parameters in this regard are the settings of a GSM/GPRS/EDGE
parameters folder containing:
z Services
z Terminal types
z Mobility types
z User profiles
z Environment classes
All of these items are classified into subfolders. In addition to these, the folder also
contains a GPRS dimensioning model subfolder.
Finally, U-Net provides the possibility to create various types of traffic maps: per
environment, per user profile (vector), per user density, or by using live traffic data.
Furthermore, the traffic analysis feature allows the user to manipulate the created
traffic maps in order to use them in prediction studies and in the dimensioning
procedure.
A user profile can be considered to be the principal data for the traffic maps. It
describes the behaviour of a certain type of users in terms of terminal type, service
and mobility. This data can then be used to generate traffic environments that contain
6-38
Chapter 6
a certain type of users with a certain density. Traffic maps can then be based on
environments, user profiles, throughput per sector (Live traffic) and densities.
6.5.2 GSM/GPRS/EDGE Multi-service Traffic Data
I. Creating GSM/GPRS/EDGE services
The traffic model allows the user to define not only voice but also data services in
GSM/GPRS/EDGE documents. Services are divided into two categories: circuit
switched and packet switched. Currently, the circuit switched service includes only
GSM voice services that use a single timeslot.
To create a service, proceed as follows:
2) Expand the GSM/GPRS/EDGE Parameters folder by left clicking on the
button.
3) Right click on the Services folder to open the associated context menu,
4) Left click in the scrolling menu on New.
window.
6) Click the available tabs to set the parameters of the created service.
II. Setting GSM/GPRS/EDGE service parameters
Similar to the other U-Net object folders, GSM/GPRS/EDGE services are easily
manageable. Creation steps and display management are standard.
To manage the GSM/EGPRS services parameters, proceed as follows:
button.
3) Expand the Services folder by left clicking on the button.
Either,
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,
Or,
4) Double click on the service of which you want to manage the properties,
Then
window,
2) Click the available tabs to adjust the parameters of the current service,
6-39
Chapter 6
Note:
z For a circuit switched service the user can specify the maximum blocking rate
(stated in term of Erlang B or C).
z For each packet switched service the user can enter, apart from a maximum
permissible blocking rate, a maximum permissible delay, a minimum required
throughput with a percentage of coverage that should at least be provided with this
throughput, and minimum/maximum number of timeslots allowed to be multiplexed
per user for that particular service.
z The maximum blocking rate defines the call blocking or call queuing rate for the
GSM voice services and the probability of delayed packet arrivals for EGPRS
data services.
z The field minimum throughput per user defines the lower threshold on the user
throughput and is one of the inputs for the dimensioning process for EGPRS
networks. The dimensioning takes into account the availability percentage of this
minimum throughput as well. These two criteria tell U-Net dimensioning engine
that the defined minimum user throughput should be available for at least that
percentage of cell coverage.
z Maximum allowable delay for a certain type of service is another input to the
dimensioning process. This is the user level delay perceived accessing a given
service, i.e. web, ftp, e-mail, etc.
z The user can also define the minimum number of timeslots reserved for packet
communication to ensure a minimum quality level. The maximum can be
specified to limit the allocation at the dimensioning within a practical/feasible
range for the network operator.
III. Managing globally GSM/GPRS/EDGE services
U-Net allows the user to simultaneously display all topics of one type (services,
mobility, terminal type, user profiles, and environment) in a table window.
To open the services table, proceed as follows:
button.
Either,
3) Right click on the Services folder to open the associated context menu.
6-40
Chapter 6
Or,
3) Double click on the Services folder.
Then
1) The services table opens.
2) Click on 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.
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.
IV. Creating a GSM/GPRS/EDGE mobility type
With the knowledge of user mobility, i.e. speed, U-Net can analyse multi-layer traffic.
In a multi-layer GSM/GPRS/EDGE network, a user speed is one of the main criteria
that is taken into account at the moment of connection establishment when there are
more than 1 possible servers available. A fast moving mobile is usually allocated a
channel from the macro/umbrella layer rather than from the micro layer to minimize
signalling and hence computational load on the system.
To create a GSM/GPRS/EDGE mobility type, proceed as follows:
button.
3) Right click on the Mobility type folder to open the associated context menu.
window.
6) Set the parameters of the currently created mobility.
6-41
Chapter 6
Note:
A maximum speed for each HCS (Hierarchical Cell Structure) layer is defined in the
Network settings that allows each HCS layer to capture a certain type of traffic within
defined mobility limitations.
V. Setting a GSM/GPRS/EDGE mobility type
Like for the other U-Net object folders, GSM/GPRS/EDGE mobility types are easily
manageable. Creation steps and the display management are standard.
To manage the mobility types parameters, proceed as follows:
button.
3) Expand the Mobility type folder by left clicking on the button,
Either,
4) Right click on the mobility of which you want to manage the properties to open
Or,
4) Double click on the mobility of which you want to manage the properties,
Then
window.
2) Set the parameters of the current mobility.
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
VI. Managing globally GSM/GPRS/EDGE mobility types
mobility, terminal type, user profiles, and environment) in a table window.
6-42
Chapter 6
To open the mobility types table, proceed as follows:

button.
Either,
3) Right click on the Mobility types folder to open the associated context menu.
Or,
3) Double click on the Mobility types folder.
Then
1) The mobility types table opens.
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.
z 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.
VII. Creating a GSM/GPRS/EDGE terminal
A terminal defines the capabilities of a mobile terminal in terms of the number of

timeslots it can multiplex in downlink (if it is defined as GPRS/EDGE compatible), the
frequency bands, and the technology it is compatible with.
During traffic analysis (capture), packet switched service can only work with GPRS or
GPRS/EDGE technology compatible mobile terminals. On the other hand, circuit
switched service can be associated to GSM technology compatible mobile terminals
as well as GPRS and GPRS/EDGE technology compatible mobile terminals.
Therefore, U-Net will distribute:
z Circuit switched service users in the service areas of GSM and GPRS/EDGE
stations.
6-43
Chapter 6
z Packet switched service users with GPRS technology compatible mobile

terminals in the service areas of GPRS/EDGE stations with GPRS/EDGE
equipments supporting either only GPRS, or both GPRS and EDGE technologies.
z Packet switched service users with GPRS/EDGE technology compatible mobile
terminals in the service areas of GPRS/EDGE stations with GPRS/EDGE
equipments supporting both GPRS and EDGE technologies.
To create a GSM/GPRS/EDGE terminal, proceed as follows:
button.
3) Right click on the Terminals folder to open the associated context menu,
window.
6) Set the parameters of the currently created terminal.
z Specify the compliant technology type(s) with the current terminal
z Since a GPRS or GPRS/EDGE technology compatible mobile terminal can
consume/communicate over multiple timeslots simultaneously, in that case
indicate the number of downlink timeslots.
z Specify the frequency band(s) the mobile terminal is compatible with. The
definition of compatible frequency bands again allows the software to allocate the
mobile to a certain network layer in the multilayer scenario with multiple bands
(GSM900 and DCS1800 layers, for example).
VIII. Setting GSM/GPRS/EDGE terminal parameters
Like for the other U-Net object folders, GSM/GPRS/EDGE terminals are easily
To manage the terminal parameters, proceed as follows:
button.
3) Expand the Terminals folder by left clicking on the button.
Either,
4) Right click on the terminal of which you want to manage the properties to open
Or,
4) Double click on the terminal of which you want to manage the properties.
6-44
Chapter 6
Then
window.
2) Set the parameters of the current terminal.
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
IX. Managing globally GSM/GPRS/EDGE terminals
mobility, terminal, user profiles, and environment) in a table window.
To open the terminals table, proceed as follows:
button.
Either,
3) Right click on the Terminals folder to open the associated context menu,
Or,
3) Double click on the Terminals folder.
Then
1) The terminals table opens.
The terminals table works exactly like the other tables. Its cells are editable, sorting
and filtering tools, and copy/paste functions are available.
6-45
Chapter 6
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 help to get description about the fields available in the different windows.
z 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
X. Creating a GSM/GPRS/EDGE user profile
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
z Average duration of a call in seconds
z Used terminal (equipment used for the service (from the Terminals table))
Parameters for packet switched services are:
z Average number of sessions per hour
z Volume in Kbytes which is transferred on the downlink during a session
z Used terminal (equipment used for the service (from the Terminals table))
These parameters are used in traffic distribution to assign a certain traffic type to a
certain layer and station that can manage the said traffic.
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.
z You can model temporal variations of user behaviour by creating different profiles
for different hours (busy hour ...).
To create a GSM/GPRS/EDGE user profile, proceed as follows:

6-46
Chapter 6

button.
3) Right click on the User profiles folder to open the associated context menu.
window.
6) Set the parameters of the currently created user profile.
XI. Adjusting GSM/GPRS/EDGE user profile properties
Like for the other U-Net object folders, GSM/GPRS/EDGE user profiles are easily
To manage the user profile parameters, proceed as follows:
button.
3) Expand the User profiles folder by left clicking on the button.
Either,
4) Right click on the user profile of which you want to manage the properties to
open the associated context menu.
Or,
4) Double click on the user profile of which you want to manage the properties.
Then
window.
2) Set the parameters of the current user profile.
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
6-47
Chapter 6
XII. Managing globally GSM/GPRS/EDGE user profiles
U-Net allows the user to display simultaneously all topics of one type (services,
mobility, terminal, user profiles, and environment) in a table window.
To open the user profiles table, proceed as follows:
button.
Either,
3) Right click on the User profiles folder to open the associated context menu.
Or,
3) Double click on the User profiles folder.
Then
1) The user profiles table opens.
The user profiles table works exactly like the other tables. Its cells are editable,
Note:
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
What's this help to get description about the fields available in the different
windows.
z 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
XIII. Creating a type of GSM/GPRS/EDGE environment
Environment classes may be used to describe subscriber spatial distribution on a map;

they are the available classes for traffic cartography design. An 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.
6-48
Chapter 6
To get an appropriate user distribution, you may assign weights per clutter classes, for
each environment class.
To create a GSM/GPRS/EDGE environment type, proceed as follows:
button.
3) Right click on the Environments folder to open the associated context menu.
window.
6) Click the available tabs to set the parameters of the currently created
environment.
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).Traffic distribution will only depend on
densities per service.
XIV. Setting GSM/GPRS/EDGE environment parameters
Like for the other U-Net object folders, GSM/GPRS/EDGE environments are easily
To manage the environments parameters, proceed as follows:
button.
3) Expand the Environments folder by left clicking on the button.
Either,
4) Right click on the environment type of which you want to manage the
properties to open the associated context menu.
Or,
4) Double click on the environment type of which you want to manage the
properties.
Then
window.
2) Click the available tabs to adjust the parameters of the current environment.
6-49
Chapter 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.
z 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.
XV. Managing globally GSM/GPRS/EDGE environment types
mobility, terminal, user profile, and environment) in a table window.
To open the environment types table, proceed as follows:
button.
Either,
3) Right click on the Environments folder to open the associated context menu.
Or,
3) Double click on the Environments folder.
Then
1) The Environment type table opens.
The environment types table works exactly like the other tables. Its cells are editable,
Note:
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.
z 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.
6-50
Chapter 6
XVI. Subscriber clutter weighting in GSM/GPRS/EDGE environments
Enter a weight for each clutter class in order to get an appropriate user
distribution
The following formula is used for calculations:
w k × Sk
Nk = Nclass ×
∑w j × Sj
j
where (see Table 6-6):
Table 6-6 Formula parameters
Number of users in the k clutter

Nk
Number of users in an environment class

Nclass
k clutter weight at fixed surface

wk
k clutter surface (stated in km²)

Sk
6.5.3 GSM/GPRS/EDGE Multi-service Traffic Cartography
I. Overview
U-Net provides 4 types of traffic maps for GSM/GPRS/EDGE projects:

z Traffic raster maps based on environments: each pixel of the map is assigned an
environment class.
z Traffic vector maps based on user profiles: each polygon or line contains a
density of subscribers with given user profile and mobility type.
z Traffic maps per transmitter and per service: live traffic is spread over a best
server coverage plot.
z Traffic raster maps based on user densities: actual user density per pixel can be
used to create a map of this type.
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.
6-51
Chapter 6
II. Creating a GSM/GPRS/EDGE 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 GSM/GPRS/EDGE 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.
5) Press the button to validate.

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.
z You can only choose among existing environment classes in the cartography editor.
To make available additional classes, do it in the GSM/GPRS/EDGE parameters.
III. Importing a GSM/GPRS/EDGE 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 (with the appropriate
format) in your project as an environment traffic map.
To import a GSM/GPRS/EDGE environment traffic map from an external file, proceed
as follows:
2) Right click on the Traffic folder to open the associated context menu,
4) Choose the map based on environments (raster) option in the Create a traffic
map open window.
6-52
Chapter 6
6) Locate the file to be imported and click the button to validate.

7) Choose the Traffic option from the scrolling menu in the open File import window.

window.
10) In the name column, left click cells in order to replace class (codes or clutter)
names by existing environment classes.
11) 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),
z Clutter files can be imported as traffic files.
z In order to manage traffic on the entire map, this operation must be carried out for
all classes.
z 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.
z Like other raster maps, it is easily possible to save the generated traffic map.
IV. Managing GSM/GPRS/EDGE 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:
2) Expand the Traffic folder by clicking on the button in front of it.
Either
3) Right click on the related environment map folder to open the associated
context menu.
Or
3) Double click on the related environment map folder.
Then
6-53
Chapter 6
window.
2) Click the description tab to re-associate environment classes.
3) Click the display tab to set the transparency level, the visibility scale and to
add the map information to the legend.
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:
z Absolute and relative statistics can be provided for this type of map.
z U-Net provides the possibility to display the cumulated traffic when working on
several traffic map(s), whatever there types are.
V. Exporting a GSM/GPRS/EDGE environment traffic map
Like the other GSM/GPRS/EDGE traffic map types (user profile, live traffic or user
density), 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 GSM/GPRS/EDGE
projects, proceed as follows:
3) Right click on the Environment map folder in order to get the related context
menu.
exported.
6) Click the Save button when this is made.
metres) of file:
The whole covered region option 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.
6-54
Chapter 6
The only pending changes option allows just to 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.
The computation zone option 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.
A resolution value is suggested; 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.
z If several objects are modified, the suggested resolution will be the smallest
resolution of the altered items.
z 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.
z If you draw your own traffic data without initial DTM, clutter or traffic object, a 100
m default resolution will be suggested.
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.
VI. Displaying statistics on GSM/GPRS/EDGE environment traffic maps
It is possible to display statistics on an existing GSM/GPRS/EDGE 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 GSM/GPRS/EDGE projects, proceed as
follows:
3) Right click on the Environment Traffic folder to open the associated context
menu.
6-55
Chapter 6
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:
Si
% of i = × 100
∑ Sk
k
Note:
z If no focus zone is defined, statistics are given over the computation zone.
z Current statistics are printable by clicking the button.
VII. Creating a GSM/GPRS/EDGE 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 GSM/GPRS/EDGE user profile traffic map by drawing, proceed as follows:
4) Choose the map based on user profiles (vector) option in the Create a traffic
map open window.

dialogs.
7) 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.
8) Click the button to close the editor.
6-56
Chapter 6
Note:
z Like other vector layers, it is easily possible to save the generated traffic map.
z Points can be seen as traffic hotspots.
See Examples of vector traffic data
VIII. Importing a GSM/GPRS/EDGE 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 import a GSM/GPRS/EDGE user profile traffic map by drawing, proceed as follows:
4) Choose the map based on user profiles (vector) option in the Create a traffic
map open window.


9) A dialog box is displayed in order to configure traffic vector data.
10) Click the Traffic tab.
11) 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).
z 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
6-57
Chapter 6
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.
z 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 GSM/GPRS/EDGE
Parameters folder and specifies manually a global density for all the polygons.
Beforehand, just make sure to define in GSM/GPRS/EDGE 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).
12) 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.
13) Then, press OK to validate the properties setting.
Note:
(selection of the Traffic type in the appropriate scrolling menu).
z 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.
z Path and description are stored in the external user configuration file.
See Examples of vector traffic data
IX. Managing GSM/GPRS/EDGE user profile traffic maps
To access the properties of an existing user profile traffic map, proceed as follows:
Either
6-58
Chapter 6
3) Right click on the related user profile traffic map folder to open the associated
context menu.
Or
3) Double click on the related user profile traffic map folder.
Then
window.
2) 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.
3) Click on the Table tab to manage the content of the vector.
4) 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 traffic
analysis.
5) Click on the Display tab to open the U-Net generic display dialog.
Note:
U-Net provides the possibility to display the cumulated traffic when working on several
traffic map(s), whatever there types are.
X. Examples of GSM/GPRS/EDGE user profile traffic data
Structure of two vector traffic files is described hereafter. Niceregion.mif (see Table 6-7)
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.
Table 6-7 Niceregion.mif
Name User Services MobilityA DensityA MobilityB DensityB

profile used
Hinterland rural Speech 90 km/h 8 pedestria 2

user n
Village rural Speech 50 km/h 10 pedestria 5
6-59
Chapter 6
Name User Services MobilityA DensityA MobilityB DensityB

profile used
user n
Corniche rural Speech 50 km/h 10 pedestria 20

user n
Rural rural Speech 90 km/h 8 pedestria 2

user n
Villages rural Speech 50 km/h 10 pedestria 10

user n
Nice urban Speech, pedestria 700 50 km/h 100

user Web, Simple n
messaging,
Video
conferencing
Nice urban Speech, pedestria 700 50 km/h 100

airport user Web, Simple n
messaging,
Video
conferencing
Nice rural Speech 50 km/h 100 90 km/h 100

surroundi user
ngs
Rural rural Speech 90 km/h 5 pedestria 5

user n
Villages rural Speech 50 km/h 10 pedestria 5

user n
Nice urban Speech, pedestria 4000 pedestria 0

center user Web, Simple n n
messaging,
Video
conferencing
Using the user profile traffic import procedure, it is possible to associate (Traffic tab of
the properties dialog):
6-60
Chapter 6
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.
z 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.
z 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 (see Table 6-8).
Table 6-8 Highway.mif
ID User_profile Service used Density Mobility
highway driver Speech 400 120 km/h
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.
z 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.
z 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.
XI. Exporting a GSM/GPRS/EDGE user profile traffic map
Like the other GSM/GPRS/EDGE traffic map types (environment, live traffic or user
density), it is possible to export user profile traffic maps.
To export a GSM/GPRS/EDGE user profile traffic map, proceed as follows:
2) Expand the Traffic folder by left clicking on the button.
3) Right click on the user profile traffic map folder to open the associated context
menu.
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.
6-61
Chapter 6
XII. Creating a GSM/GPRS/EDGE live traffic map
This kind of traffic map requires a coverage by transmitter prediction study. Then,
U-Net expects on each transmitter service area, a number of Erlangs in case of
speech service and rate values (kbps) for packet-switched services.
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 GSM/GPRS/EDGE 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.
To create a GSM/GPRS/EDGE live traffic map, proceed as follows:
4) Choose the map based on transmitters and services option in the Create a
traffic map open window.

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 GSM/EGPRS 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 Erlangs for speech service and rate values (kbits/s) for packet-switched
services for each transmitter.
8) Press OK to continue the map creation.
dialogs.
10) 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
6-62
Chapter 6
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.
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.
z On the other hand, it is possible to modify traffic values (Erlangs, throughputs)
afterwards in the Table related to the map.
XIII. Importing a GSM/GPRS/EDGE live traffic map
The definition of GSM/GPRS/EDGE 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 a coverage by
transmitter study in the AGD format).
To import a GSM/GPRS/EDGE live traffic map by drawing, proceed as follows:
4) Choose the map based on transmitters and services option in the Create a
traffic map open window.

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
6-63
Chapter 6
coordinate system of the file you are importing (click on Change... to choose
another coordinate system).

11) 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.
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.
XIV. Managing GSM/GPRS/EDGE 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:
Either
3) Right click on the related live traffic map folder to open the associated context
menu.
Or
3) Double click on the related live traffic map folder.
Then
window.
6-64
Chapter 6
2) 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.
3) Click on the Table tab to manage the content of the vector.
4) Click on the Traffic tab to re-define terminal and mobility ratios and to impose
subscriber clutter weighting using this map for the traffic analysis.
To open the table related to an existing live traffic map, proceed as follows:
3) Right click on the related live traffic map folder to open the associated context
menu.
The management of the table is generic and can be accessed from the Table tab of the
properties dialog or from the Table context menu (Fields command). Sorts and Filters
features on the display are also available.
Note:
XV. Exporting a GSM/GPRS/EDGE live traffic map
Like the other GSM/GPRS/EDGE traffic map types (environment, user profile or user
density), it is possible to export live traffic maps.
To export a GSM/GPRS/EDGE live traffic map, proceed as follows:
3) Right click on the live traffic map folder to open the associated context menu.
exported. Possible format is the U-Net internal format (.agd).
XVI. Creating a GSM/GPRS/EDGE user density traffic map
This type of traffic maps allows the user to express the traffic density directly in the
form of a map using graphical vector layers. The user can add vector layers and draw
6-65
Chapter 6
the regions with different traffic densities. The user can also specify the distribution of
Terminal types, Mobility types, and Services for the map based on traffic density.
Note:
It is possible to create multiple maps based on traffic density with different distribution
of Terminal types, Mobility types and Services.
The definition of GSM/GPRS/EDGE user density traffic maps can be made either from
a direct creation by drawing or by importing a raster (32-bit format) file.
To create a GSM/GPRS/EDGE user density traffic map, proceed as follows:
4) Choose the map based on densities option in the Create a traffic map open
window.
After clicking on Create map, U-Net adds a subfolder in the Traffic folder.
dialogs.
7) U-Net displays the property dialog of the map. In the Traffic tab, you can describe
the distribution of different types of traffic. Specify the percentages of the
distribution of different Terminal types, Mobility types and Services in the
map (they will be used in the traffic scenario). You can also manage the Display
properties of the map from the Display tab.
Note:
z The map contains traffic density per pixel directly entered by the user. So, if the
user has entered a traffic density of 100 users per km2, U-Net will allocate x users
per pixel (depending on the pixel size) and these x users will be distributed
according to the percentages given in the Traffic tab of the map’s properties
window.
z It is possible to modify traffic distribution (Terminal types, Mobility types and
Services) afterwards in the properties of the map.
6-66
Chapter 6
8) U-Net creates an object called “Traffic density map” in the Traffic folder of the Geo
tab. A vector layer is automatically created in this subfolder.
9) Edit this vector layer to define geographical areas with a certain traffic
density. To change the traffic density, you have to open the vector layer table and
enter values in the Traffic density(Density) column.
10) Close the table to validate.
Note:
z You can turn the vector editor ON and OFF either through the Edit... menu in the
Traffic density Map’s context menu or through the Edit menu in the vector layer’s
context menu.
z In this type of traffic maps, you are not asked to specify a clutter weighting as it is
already the traffic density per pixel that is stored in the map.
XVII. Importing a GSM/GPRS/EDGE user density traffic map
The definition of GSM/GPRS/EDGE user density traffic maps can be made either from
a direct creation by drawing or by importing a raster (32-bit format) file. The supported
formats are BIL (only 32 bit), BMP, PlaNET, TIFF, ISTAR, Erdas Imagine formats
To import a GSM/GPRS/EDGE user density traffic map, proceed as follows:
4) Choose the map based on densities option in the Create a traffic map open
window.
6) Locate the file to be imported and click the button to validate,

7) Choose the Traffic density option from the scrolling menu in the open File import
window.

dialogs.
10) U-Net displays the property dialog of the map. In the Traffic tab, you can describe
the distribution of different types of traffic. Specify the percentages of the
distribution of different Terminal types, Mobility types and Services in the
6-67
Chapter 6
map (they will be used in the traffic scenario). You can also manage the Display
properties of the map from the Display tab.
Note:
(selection of the Traffic density type in the appropriate scrolling menu).
z The map contains traffic density per pixel directly entered by the user. So, if the
user has entered a traffic density of 100 users per km2, U-Net will allocate x users
per pixel (depending on the pixel size) and these x users will be distributed
according to the percentages given in the Traffic tab of the map’s properties
window.
z It is possible to modify traffic distribution (Terminal types, Mobility types and
Services) afterwards in the properties of the map.
z In this type of traffic maps, you are not asked to specify a clutter weighting as it is
already the traffic density per pixel that is stored in the map.
XVIII. Managing GSM/GPRS/EDGE user density traffic maps
Management features of vector maps are available for traffic density maps: limited set
of graphical features are available in the Display tab of the map property dialog and
each map has a corresponding table. This table contains the traffic density values
used.
To access the properties of an existing user density traffic map, proceed as follows:
Either
3) Right click on the related user density traffic map folder to open the
Or
3) Double click on the related live traffic map folder.
Then
window.
2) Click on the Traffic tab to re-define Terminal, Mobility and Services ratios using
this map for the traffic analysis.
6-68
Chapter 6
To open the table related to an existing user density traffic map, proceed as
follows:
3) Expand the User density Traffic subfolder by clicking on the button in front
of it.
4) Right click on the vector layer to open the associated context menu.
The management of the table is generic and can be accessed from the Table tab of the
vector properties dialog or from the Table context menu (Fields command). Sorts and
Filters features on the display are also available.
Note:
XIX. Exporting a GSM/GPRS/EDGE user density traffic map
Like the other GSM/GPRS/EDGE traffic map types (environment, user profile or live
traffic), it is possible to export user density traffic maps.
To export a GSM/GPRS/EDGE user density traffic map, proceed as follows:
3) Right click on the user density traffic map folder to open the associated
context menu.
exported. Possible format are BIL (only 32 bit) and BMP formats.
XX. Displaying the GSM/GPRS/EDGE cumulated traffic
In U-Net, there are different possibilities for displaying the traffic maps in a
GSM/EGPRS document:
z Either the user can display all the traffic maps in form of different items. In this
case, U-Net displays the maps in layers laid one over the other. This is the default
method of displaying traffic maps.
6-69
Chapter 6
z Or the user can choose to display the cumulated traffic.

Traffic from all the map layers is cumulated over the map display window and the
resulting traffic is displayed and coloured according to the traffic density per pixel.
To display the GSM/GPRS/EDGE cumulated traffic, proceed as follows:
2) If the symbol before the traffic folder is , refresh the clutter weighting values
5) Click the Display tab. The U-Net generic display dialog opens.
6) Select the Value intervals display and the appropriate field.
U-Net can display the cumulated circuit-switched and the cumulated packet-switched
traffic densities in Erlangs/km2 and kbps/km2 respectively. The cumulated traffic takes
into account the clutter weighting if used for traffic maps other than traffic density maps.
This type of display is useful to view the different traffic density areas as a result of all
the different traffic maps. Different colour shades are used to depict different values of
cumulated traffic density per pixel resulting from the initial traffic maps.
Note:
To come back to the standard display, select the 'None' display type.
XXI. Exporting the GSM/GPRS/EDGE cumulated traffic
U-Net allows the user to export the cumulated traffic generated with all the traffic maps
in the environment. The cumulated traffic can be exported in BIL (only 32 bit) and BMP
formats. These exported files can later be imported and used as traffic density maps in
U-Net.
To export a raster file containing the cumulated traffic density, proceed as follows:
2) If the symbol before the traffic folder is , refresh the clutter weighting values.
4) Left click in the scrolling menu on the Export cumulated traffic command.
5) Specify the directory where you want to save the exported file, the file name
and the file type in the opened dialog box.
6) Press OK to validate.
6-70
Chapter 6
Note:
Clutter weightings specified for the different traffic maps are not systematically taken
into account in the cumulated traffic map and traffic analysis. In order to warn the user,
U-Net displays the Traffic folder with a special symbol . In this case, in order to
correctly consider the clutter weighting, it is mandatory to refresh it before
displaying/exporting cumulated traffic and calculating a traffic analysis.
To refresh clutter weighting, proceed as follows:

3) Left click in the scrolling menu on Clutter weighting calculation.
6.5.4 GSM/GPRS/EDGE Traffic Analysis
I. Overview
Traffic analysis allows the user to analyse the traffic from maps at the transmitter level.
This feature, in general, distributes the traffic from the maps to all the transmitters in
each layer according to the compatibility criteria defined in the transmitter, services,
mobility, terminal items. More specifically, this feature allows U-Net to allocate the
traffic to each transmitter of each layer (micro/macro, multiband, ...) taking into
account the criteria defined in the user profiles and the transmitters.
For example, an EGPRS enabled transmitter will be allocated the data user traffic
while a transmitter not having the EGPRS functionality will only carry the GSM voice
traffic.
Similarly, a user using a GSM900 band mobile phone will not be allocated to a
transmitter that only functions on the DCS1800 band, and so on and so forth.
This feature allows the user to create multiple traffic distributions with different criteria
and to later analyse the network according to any of them.
Important: the traffic analysis is a mandatory step before dimensioning. The outputs of
a traffic analysis can be used for dimensioning and KPI calculation, and the
determination of coverage study reports and neighbour allocation is based on a default
capture.
II. Creating a GSM/GPRS/EDGE traffic capture
To perform a traffic analysis, proceed as follows:

2) If the symbol before the traffic folder is , refresh the clutter weighting values.
6-71
Chapter 6
3) Right click on the Traffic analysis folder and choose New in the associated
context menu.
4) The property dialog opens. Click the available tabs to set the parameters of the
currently created traffic distribution.
z The General tab: Here, you may type the name of the traffic analysis, add some
comments and filter the transmitters which you want to spread the traffic over.
z The Source traffic tab: U-Net lists in this tab all the traffic maps available in
the .atl document. Select this (or these) to be considered in the traffic analysis. It
is possible to globally scale the traffic maps with a certain multiplying factor; this
factor enables you to increase the traffic request of the map without changing the
traffic map description.
z The Condition tab: Parameters available in the Condition part are used to
determine each transmitter service area which U-Net will distribute traffic and
then, the traffic demand. Service areas of subcells are determined using the
option « Best signal level per HCS layer », a 0dB margin and the subcell
reception threshold as lower threshold.
z In case of data traffic, you may base analysis on C/I. In this case, U-Net uses the
charts rate=f(C) and rate=f(C/I) to evaluate the number of timeslots used for the
traffic demand and the minimum rate reduction factor.
5) Then, either confirm by clicking on Calculate in the Condition tab, or click on
OK to close the dialog and choose OK in the U-Net dialog in order to calculate
the traffic capture.
After completing calculations, U-Net adds two new tabs named “Results per
transmitter” and “Results per subcell” in the property dialog producing the outputs of
the traffic analysis.
III. GSM/GPRS/EDGE traffic capture outputs
After completing calculations, U-Net adds two new tabs named “Results per
transmitter” and “Results per subcell” in the property dialog.
In the Results per transmitter tab, U-Net indicates the traffic distributed to each
transmitter. It provides, for each transmitter:
z The circuit traffic demand (in Erlangs) and the average demand of circuit
timeslots.
The number of timeslots to be used to match the circuit traffic demand depends
whether the transmitter subcells support full or half rate.
z The packet traffic demand (in kbps) and the average demand of packet timeslots.
The number of timeslots to be used to match the packet traffic demand depends on
the maximum throughput that a packet timeslot can support. This parameter is
predefined by radio conditions at the mobile terminal (C and optionally C/I).
6-72
Chapter 6
z The average packet timeslot capacity (in kbps).

In the Results per subcell tab, U-Net details the distributed traffic per subcell, service,
terminal and mobility. For each subcell of each transmitter (except BCCH subcell,
which is supposed to capture the same traffic than TCH subcell), U-Net indicates the
type(s) of traffic assigned to it (service, mobility, terminal). Then, for each set (subcell,
service, and mobility, terminal), it displays:
z The traffic demand: circuit traffic demand is stated in Erlangs and packet traffic
demand in kbits/s.
z The number of timeslots to be used to match the traffic demand.
In case of voice service, it depends whether the subcell supports full or half rate. If the
% of half rate traffic ratio of the subcell is set to 0, the subcell needs as many timeslots
as Erlangs and the number of used timeslots equals the traffic demand. In case of half
rate, the number of used timeslots depends on the % of traffic using half rate.
In case of a packet switched service, the demand in packet timeslots depends on the
maximum throughput that a timeslot can support. This parameter is predefined by
radio conditions at the mobile terminal (C and optionally C/I).
Formulas and calculation details of results are available in the technical reference
guide.
IV. Using a GSM/GPRS/EDGE traffic analysis
Different tools are available on an existing GSM/GPRS/EDGE traffic analysis. From its
context menu (right click), you may:
z Use standard management features (Delete, Rename).
z Open the property dialog of the traffic analysis to check analysis parameters and
results (Properties).
z Recalculate the traffic analysis (Recalculate).
z Select the traffic analysis as the default traffic distribution to be taken into account
in coverage study reports and neighbour allocation (Default). This particular
captured traffic is assigned a little icon describing it as the default distribution
for studies (not default: ).
z Perform dimensioning of network based on a traffic analysis (Dimensioning).
z Calculate KPIs of a real network based on the traffic analysis (KPI calculation...).
6.6 GSM/GPRS/EDGE Network Dimensioning

6.6.1 Setting GSM/GPRS/EDGE Dimensioning Models
Dimensioning models are provided at the GSM/GPRS/EDGE parameters level. This

item is the basis of GSM/GPRS/EDGE dimensioning and quality analysis process. A
6-73
Chapter 6
user can define a dimensioning model by providing the simple parameters in the
properties window.
To set parameters of a dimensioning model, proceed as follows:
1) Expand the GSM/GPRS/EDGE parameters folder by clicking on the button.
2) Expand the Dimensioning models subfolder by left clicking on the button.
3) Right click on a dimensioning model and select Properties in the context
menu.
Notably, these parameters define the system level conditions to be taken into account
when dimensioning the system or when analysing the quality of service (QoS) of the
system.
4) Open the General tab and indicate dimensioning directives:
z The upper limit on the number of TRXs that can be placed in a transmitter.
z The queuing model for GSM voice calls (Erlang B or Erlang C).
z The lower limit on the number of dedicated packet switched timeslots that can be
used by the transmitter, the upper limit on the number of TRXs that can be added
in order for the subcell to fulfill the packet traffic demand and the Key
Performance Indicators (KPIs) to be taken into account when performing the
dimensioning process.
5) Open the Quality charts tab including the curves of throughput reduction factor,
delay, and blocking probability used for the dimensioning process of packet
switching traffic. All these three curves are against the system load, which is
defined as the ratio of used packet timeslots to the number of timeslots available
to perform data communication (packet calls). U-Net provides a basic set of
curves by default for these parameters, but a user can always use his own quality
curves generated through some other software package using simulations.
Note:
z The quality model curves should not be modified haphazardly, as it may cause the
dimensioning and quality analysis feature to malfunction.
z The curve for delay against network load is left to be entered by the user for the
moment.
z The curve of blocking probability against network load is for a user multiplexing
factor of 8 (default value). The user multiplexing factor corresponds to the number
of GPRS/EDGE users that can be multiplexed on a timeslot. This field has been
added in the database structure of the document template “GSM_EGPRS”
(EGPRSDimensioningModel table) but it is not used for the moment. This feature
will be completely implemented in a later release.
6-74
Chapter 6
6) Click OK to close the property dialog.

KPIs are the minimal throughput, the blocking probability and the delay. They are
described below.
Throughput for a EGPRS user is the average maximum throughput perceived at the
mobile terminal during a data call. If there are more than one user multiplexed on the
same timeslot, which occurs as the system starts being loaded with many users, each
multiplexed user perceives a reduction in his throughput per timeslot due to this
multiplexing. This reduction in throughput is depicted by the Reduction Factor.
A Reduction Factor of 1, or nearly 1, means that each user is communicating at the
maximum throughput that a timeslot can offer in a given environment (the maximum
throughput per timeslot depends, in its turn, on the C/I ratio at a given location). As the
system starts being loaded with users, the reduction factor starts decreasing depicting
the lessening of throughput per user.
Each user communicating over a packet switching protocol experiences a delay that is
due to the buffering of packets, the resource allocation, and transmission delay. This
delay can be restricted to a maximum allowable limit within the properties of a service.
This delay and the blocking probability in the EGPRS system are closely related,
meaning that a user starts to experience more delay in service when the system is
near saturation and the incoming packets are placed in a waiting queue as there are
no resources available for immediate transfer. This buffering of packets is related to
the load of the system.
Note:
The term system load refers to the ratio of the number of used packet timeslots to the
number of packet switching (shared + dedicated) timeslots available in the system.
Hence, it has roughly the same concept as traffic load in the GSM.
6.6.2 Dimensioning GSM/GPRS/EDGE Transmitters
U-Net allows the user to dimension a GSM/EGPRS network fully and thoroughly. The
user can work with multiple traffic maps, whose traffic has been distributed over the
transmitters and network layers, to dimension the transmitters according to GSM voice
and EGPRS data traffic carried. Only one traffic capture can be used for dimensioning
computations at a time.
To run a dimensioning calculation, proceed as follows:
2) Expand the Traffic analysis folder by left clicking on the button.
6-75
Chapter 6
3) Right click on a Traffic capture item, according to which you want to dimension
the network, to open the context menu.
4) Select the Dimensioning command in the opened scrolling menu.
5) In the Dimensioning dialog, choose the dimensioning model to be used for
computations.
You can select the columns you want to display in the table. To do this, click on the
Displayed columns button and select information you wish to display.
6) Click on Calculate button to perform the dimensioning.
U-Net sums up dimensioning inputs and outputs in the table. U-Net displays rows of
the table in red when the number of required TRXs for a transmitter exceeds the
maximum number of TRXs per transmitter.
Note:
Dimensioning is based on a traffic capture. Modifications of traffic map(s), traffic
parameters and transmitter properties (e.g. calculation area, GPRS/EDGE
equipment...) have an influence on the traffic capture. Therefore, if you modify some of
these data, you must recalculate the traffic capture before performing dimensioning.
6.6.3 Committing Dimensioning Outputs in GSM/GPRS/EDGE
After a dimensioning procedure, for each subcell of each transmitter, U-Net gives:
I. Main dimensioning results
such as the number of required TRXs, the number of required packet, shared and
circuit timeslots and the traffic load (circuit and packet).
We assume we have a subcell with circuit and packet traffic. U-Net evaluates a
number of TRXs so as to have enough circuit timeslots (shared and dedicated) to
match the circuit traffic demand with the effective blocking rate. Then, it calculates how
many TRXs it must add to match the packet traffic demand. This value is determined
for a given packet load from quality charts used by the dimensioning model. If the
dimensioning model takes into account the three KPIs (minimum throughput reduction
factor, maximum delay and maximum blocking rate), the number of TRXs to add for
packet service is calculated so as to comply with the following conditions: the
throughput reduction factor must exceed the minimum throughput reduction factor, the
delay and the blocking rate must be respectively lower than the maximum delay and
maximum blocking rate.
6-76
Chapter 6
II. Network settings
such as the maximum number of TRXs that can be placed in the transmitter (this value
is indicated in the dimensioning model properties), the maximum rate of traffic
overflow (%) (specified in the subcell properties) and the half rate traffic ratio (%)
(defined in the subcell properties).
Note:
When the maximum rate of traffic overflow and the Half-Rate traffic ratio values are
different for BCCH and TCH subcells, U-Net takes the BCCH subcell values.
III. Traffic capture results
such as the packet traffic demand (kbps), the average demand in packet timeslots, the
average number of timeslots per connection (packet) and the circuit traffic demand
(Erlangs), the average demand in circuit timeslots and the average number of
timeslots per connection (circuit),
Note:
In case of concentric cells, the traffic demand on TCH subcells is different from the
one evaluated during the traffic capture. It is calculated from the traffic demand of the
capture and the effective rate of traffic overflow (instead of the maximum rate used in
traffic analysis).
For packet services, the average number of timeslots per connection corresponds to
the average number of downlink timeslots, which mobile terminals can simultaneously
communicate over. For circuit switched services, the number of timeslots per
connection is 1 in case of full rate; else it depends on the half rate ratio.
IV. Additional dimensioning results,
1) For a circuit switched service, you will find the served circuit traffic (Erlangs), the
effective rate of traffic overflow and the effective blocking rate.
The served circuit traffic corresponds to the circuit traffic demand less the effective
overflowed circuit traffic.
In case of Erlang B, the effective rate of traffic overflow corresponds to the effective
blocking rate; this value is deduced from the required number of circuit timeslots
(shared + dedicated) and the circuit traffic demand in Erlang B tables.
6-77
Chapter 6
In case of Erlang C, the effective rate of traffic overflow is zero except if the maximum
number of TRXs is exceeded; the effective blocking rate is inferred from the required
number of circuit timeslots (shared + dedicated) and the circuit traffic demand in
Erlang C tables.
2) For a packet switched service, results are the served packet traffic (kbps), the
effective rate of traffic overflow, the minimum throughput reduction factor and
KPIs such as the throughput reduction factor, the delay and the blocking rate.
The served packet traffic corresponds to the packet traffic demand less the effective
overflowed packet traffic.
The effective rate of traffic overflow corresponds to the rejected packet traffic due to
missing packet timeslots.
The minimum throughput reduction factor is stated in percentage; it corresponds to the
highest reduction (lowest percentage) that can be applied to the maximum rate in
order to supply service with the minimum permissible rate (defined for the service).
After a computation, click on Commit to assign the results to transmitters (the
required number of TRXs) and subcells (the required number of TRXs, the load, the
required number of shared, circuit and packet timeslots and the effective rate of traffic
overflow).
U-Net displays rows of the table in red when the number of required TRXs for a
transmitter exceeds the maximum number of TRXs per transmitter.
Note:
z Dimensioning is based on a traffic capture. Modifications of traffic map(s), traffic
parameters and transmitter properties (e.g. calculation area, E/GPRS equipment...)
have an influence on the traffic capture. Therefore, if you modify some of these
data, you must recalculate the traffic capture before performing dimensioning.
z Formulas and calculation details of parameters listed in the table are available in
the technical reference guide.
6.7 GSM/GPRS/EDGE Resources Allocation

6.7.1 Overview
At this step, GSM/GPRS/EDGE parameters, traffic maps have been defined. A traffic
analysis has been performed with a view to dimension the network. The number of
needed resources (TRXs) is known.
6-78
Chapter 6
The next step is to define transmitters neighbours. This can be made manually, but
U-Net proposes an algorithm which allows you to perform it automatically. Allocating
transmitter neighbours manually can also be made for external transmitters from a
linked network in co-planning. Neighbour definition helps in the Automatic Frequency
Planning (AFP) in order to impose frequency separation constraints on neighbours.
Once the neighbours are known, the resource allocation can be made either manually
or by using an automatic allocation tool. The constraints on it come from the data
model itself, from the user which can impose separation constraints on:
z Neighbours
z Within transmitters
z On transmitters located on unique sites
z Defined exceptional pairs of subcells
and from the different dialogs composing the procedure of the AFP.
Concerning the AFP features, U-Net provides a generic AFP interface which is
compliant for the use of a specific AFP model. General constraints are imposed in the
generic parts and the strategy directives can be set in the specific model itself.
This automatic tool will try to reach a best solution respecting also the number of
requested resources. Furthermore, this tool can help you for the determination of
HSNs, MAIOs, BSICs, and SFHs.
After the resource allocation, the network can be analysed thanks to the use of the
following tools:
z A tool to check the frequency plan consistency
z A tool to check the consistency between transmitters and subcells
z A channel search tool working on channels, BCCHs and BSICs
z The possibility to compute Key Performance Indicators (KPI) on the basis of a
traffic capture and a resource allocation.
The network is the ready for the study of interfered zones, C/I predictions, and specific
E/GPRS studies (coding schemes and throughputs).
6.7.2 GSM/GPRS/EDGE Neighbours
I. Allocating GSM/GPRS/EDGE transmitter neighbours manually
When defined, cell neighbours are a way to optimise the search of possible cells
aiming to perform handover from the current coverage area. Allocating neighbours in a
network is optional. Defining neighbours helps in imposing constraints for frequency
automatic allocation.
6-79
Chapter 6
Note:
Neighbours are not a filter for transmitters being part of interferers. All transmitters in a
network take part in interferences on each transmitter. Neighbours of any linked
project in co-planning can also be listed and chosen manually.
Manual allocation of GSM/GPRS/EDGE neighbours must be performed for each

transmitter, one at a time. To do this, proceed as follows:
Either,
3) Right click on the transmitter from which you want to define the neighbourhood,
Choose the properties option from the context menu, Or Double click on the
transmitter from which you want to define the neighbourhood,
4) Click the Intra-technology Neighbours tab from the current window,
5) Use the What's this help to get information about fields available in the current
window,
6) In the displayed window, use the top table. Select the row with symbol , then
in the Neighbours column, click on the 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,
7) Click either another cell of the table, or 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.
Or
2) Choose the [Neighbours: Intra-technology Neighbours] command from the
Transmitters folder context menu,
3) In the displayed table, use the row with symbol . 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,
4) Click another cell of the table to validate and add a new row to the table,
In the table, U-Net provides additional information
6-80
Chapter 6
Note:
z It is possible to add/remove symmetric neighbourhood links at once. To do this, use
the commands [Symmetrise] 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.
z 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
transmitter).
z 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
z This feature deals with GSM/GPRS/EDGE, CDMA/CDMA2000 and UMTS
technologies.
An automatic allocation tool is also available.
II. Defining GSM/GPRS/EDGE exceptional pairs of neighbours
U-Net enables you to define neighbourhood constraints that may be then considered
by algorithm during the automatic allocation of neighbours.
To define GSM/GPRS/EDGE exceptional pairs of neighbours, proceed as follows:
Either,
3) Right click on the transmitter for which you want to define the neighbourhood
constraints, Choose the properties option from the context menu, Or Double
click on the transmitter for which you want to define the neighbourhood
constraints.
4) Click the Intra-technology Neighbours tab.
5) Use the What's this help to get information about fields available in the current
window.
6) In the displayed window, use the bottom table. Select the row with symbol .
In the Neighbours column, click the cell of the Neighbours column to choose
from the scrolling box a neighbour (U-Net lists all the transmitters 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.
6-81
Chapter 6
7) Click either another cell of the table, or the button to validate and
add a new row to the table.
Or
2) Choose the [Neighbours:Intra-technology exceptional pairs] command from
the Transmitters folder context menu.
3) In the displayed table, use the row with symbol . 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.
4) Click another cell of the table to validate and add a new row to the table.
Note:
Exceptional pairs are not taken into account during manual neighbour allocation.
III. Allocating GSM/GPRS/EDGE transmitter neighbours automatically
Allocation algorithm permits to automatically allocate neighbours in the current

network.
To automatically allocate GSM/GPRS/EDGE neighbours in a network, proceed as
follows:
3) Choose the [Neighbours:Automatic allocation...] command from the open menu.
window.
5) Set the parameters for the current Auto Neighbours allocation study.
Automatic neighbour allocation is based on the following parameters:
z Max number of neighbours
This is the maximum number of neighbours to be allocated to a transmitter. This value
may be either globally set for all the transmitters (in the automatic allocation algorithm),
or specified for each transmitter (in the Transmitters table).
U-Net uses the value defined at the transmitter level if available, otherwise it considers
the global value.
6-82
Chapter 6
z Max Inter-Site distance

This is the maximum distance you can have between the reference transmitter and a
candidate neighbour. If the distance between the reference transmitter and a
candidate neighbour is higher than this value, then the candidate neighbour is
discarded.
Coverage conditions between the reference transmitter (A) and a candidate neighbour
(B)
U-Net determines the overlapping area between SA and SB ( S A ∩ SB ) as defined
below (see Figure 6-1):

SA is the reference transmitter A coverage area restricted between two boundaries.
The first boundary represents the start of the handover area (best server area of A
more the handover margin named “handover start”) and the second boundary shows
the end of the handover area (best server area of A more the margin called “handover
end”).
SB is coverage area where the candidate transmitter B is the best server.
Minimum signal level
Handover end
Handover start
canB
refA Best server area of canB
Best server area of refA
SA∩SB
Figure 6-1 Coverage conditions
6-83
Chapter 6
Note:
z The margin “handover end” must exceed the margin “handover start”.
z The higher the margin “handover end” is, the bigger the list of candidate
neighbours is.
Take into account Covered Area: U-Net calculates the percentage of covered area
S A ∩ SB
( SA ).
Take into account Covered Traffic: U-Net calculates the traffic covered on the
overlapping area ( S A ∩ SB ).
% min Covered Area: This is a minimum percentage to be exceeded in order not to

discard the candidate neighbour B. If the option “Take into account Covered Area” is
selected, it will correspond to the minimum percentage of covered area. If the option
“Take into account Covered Traffic” is selected, it will refer to the minimum percentage
of covered traffic.
z Calculation options
Force co-site transmitters as neighbours: This option enables you to force the co-site
transmitters in the neighbour list of a reference transmitter. The co-site transmitters are
listed just after the forced exceptional pairs.
Force adjacent transmitters as neighbours: When selecting this option, adjacent
transmitters are ordered in the neighbour list just after co-site transmitters.
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.
Reset neighbours: When selecting the Reset option, U-Net deletes all the current
neighbours and carries out a new neighbour allocation. If not selected, the existing
neighbours are kept.
6) Click the button to start calculations.
In the Results part, U-Net provides a list of neighbours and the number of neighbours
for each transmitter. In addition, it indicates allocation reason for each neighbour. We
can have (see Table 6-9):
6-84
Chapter 6
Table 6-9 Allocation reasons
Reason Description When Rank in the

list
Forced Neighbourhood Only if the Force 1

relationship defined exceptional pairs option is
as exceptional pair selected
Co-site The neighbour is Only if the Force co-site 2

located on the transmitters as neighbours
reference transmitter option is selected
site
Adjacent The neighbour is Only if the Force adjacent 3

adjacent to the transmitters as neighbours
reference transmitter option is selected
% of covered Neighbourhood Any time 4

area or relationship that
% of covered fulfils coverage
traffic conditions
Symmetric Neighbourhood Only if the Force 5

relationship forced in neighbour symmetry
order to fulfill option is selected
symmetry conditions
Existing Existing Only if the Reset option is 6

neighbourhood not selected and in case of
relationship a new allocation
Note:
U-Net displays either the percentage of covered area and the overlap area (km2) in
brackets (Covered Area option), or the percentage of covered traffic and the covered
traffic (Erlang) in brackets (Covered Traffic option).
7) Once calculations are achieved, click the button to assign

neighbours to transmitters as displayed in the current table. Neighbours are then
listed in the Intra-technology Neighbours tab of each transmitter properties
window.
6-85
Chapter 6
8) Click the Close button to achieve the procedure.
Note:
z This feature deals with GSM/GPRS/EDGE, CDMA/CDMA2000 and UMTS
technologies.
z 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.
z U-Net does not take into account the specified margin “handover start” when using
the adjacency option. It considers a fixed value of 0 dB.
z In case of HCS layers, neighbours between macros and micros in HCS are not
currently allocated even if the macro and micro are physically adjacent.
z You can carry out neighbour allocation globally on all the transmitters or only on a
group of transmitters. In this case, U-Net will consider all the transmitters contained
in the group of transmitters, the symmetric neighbours of these transmitters and all
the other ones, which have an intersection area with the transmitters of the group.
z Neighbours are not a filter for transmitters being part of interferers. All transmitters
in a network take part in interferences on each transmitter.
z 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.
IV. Displaying current GSM/GPRS/EDGE neighbour list
U-Net provides the possibility to open an editable table referencing all the
GSM/GPRS/EDGE neighbours of the current network.
To access the GSM/GPRS/EDGE neighbour table, proceed as follows:
3) Choose the [Intra-technology Neighbours] command from the open menu.
4) In the displayed table, U-Net lists reference transmitters and their related
neighbours. In addition, it indicates the number of neighbours assigned to each
reference transmitter, and for each neighbour:
z The distance between the neighbour and the reference transmitter.
z If the neighbourhood relationship is symmetric or not.
z The type of allocation. Three values are available, manual (copy/paste of a
neighbour list, manual edition of neighbours), automatic (automatic allocation), or
6-86
Chapter 6
imported (Planet import, generic import, import using an add-in). This output will
be able to be considered by AFP; it is currently unused.
z The neighbour rank in the list of neighbours of the reference transmitter. This
information is given only in case of an automatic allocation.
z The allocation reason. This information is given only in case of an automatic
allocation.
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.
V. Modifying the allocated GSM/GPRS/EDGE neighbours
You may add new neighbours or remove allocated neighbours.

To delete allocated neighbours, proceed as follows:
Either
3) Right click on the transmitter from which you want to exclude some neighbours.
4) Choose the properties option from the context menu.
5) Click the Intra-technology Neighbours tab from the current window.
6) Click on OK to validate and close the dialog box.
Or
3) Choose the [Neighbours:Intra-technology Neighbours] option from the context
menu.
4) In the displayed table, select the target neighbour row.
5) Press the keyboard Del (or Suppr.) key.
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.
To add new neighbours, proceed as follows:

Either
6-87
Chapter 6

3) Right click on the transmitter from which you want to exclude some
neighbours.
4) Choose the properties option from the context menu.
5) Click the Intra-technology Neighbours tab from the current window.
6) In the displayed table, use the last row with symbol . Click the cell of the
Neighbours column to choose a neighbour or edit the neighbour name.
7) Edit the neighbour name.
Or
3) Choose the [Neighbours: Intra-technology Neighbours] option from the
context menu.
4) In the displayed table, use the last row with symbol . 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 or edit the neighbour name.
Note:
z Adding/Removing neighbours can be also made thanks to the Neighbour
graphic management icon.

z It is possible to add symmetric neighbourhood links at once. To do this, use the
command [Symmetrise] available in a context menu. This one can be open by right
clicking on the neighbour you have added.
VI. Displaying GSM/GPRS/EDGE neighbours on the map
Once the GSM/GPRS/EDGE neighbours have been allocated, you can display a given
neighbourhood on the map.
To display the neighbours of any transmitter, proceed as follows:
1) Click on the Neighbour graphic management icon from the toolbar.
2) Left click on the desired transmitter to select it on the map.

3) U-Net displays on the map (see Figure 6-2):
z The symmetric neighbourhood links with the selected transmitter (reference
transmitter). A single black line represents these links.
6-88
Chapter 6
z 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).
z 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.
Figure 6-2 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.
To do this, right click on the transmitters folder and choose the
[Neighbours:Display...] command from the open menu.
z 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.
VII. Adding/Removing GSM/GPRS/EDGE neighbours on the map
You may directly add and remove neighbourhood links on the map thanks to CTRL
and SHIFT shortcuts.
To add a symmetric neighbourhood link, proceed as follows:
6-89
Chapter 6
2) Left click on the reference transmitter on the map. U-Net displays its
neighbourhood links.
3) In order to define a new symmetric link between the reference transmitter and a
transmitter A (transmitter A is neighbour of the reference transmitter and vice
versa), hold down SHIFT on your keyboard and left click on the transmitter A.
U-Net displays a single black line between both transmitters.
To remove a symmetric neighbourhood link, proceed as follows:
3) In order to remove an existing symmetric link between the reference transmitter
and a transmitter A, hold down SHIFT on your keyboard and left click on the
transmitter A.
To add an outwards neighbourhood link, proceed as follows:
3) In order to define a new outwards link between the reference transmitter and a
transmitter A (transmitter A is neighbour of the reference transmitter but reference
transmitter is not neighbour of transmitter A), hold down CTRL on your keyboard
and left click on the transmitter A. U-Net displays an arrow directed to transmitter
A; it is coloured as the reference transmitter.
To remove an outwards neighbourhood link, proceed as follows:
3) In order to remove an existing outwards link between the reference transmitter
and a transmitter A, hold down CTRL on your keyboard and left click on the
transmitter A.
To add an inwards neighbourhood link, proceed as follows:
6-90
Chapter 6
3) In order to define an outwards link between the reference transmitter and a

transmitter A (the reference transmitter is neighbour of transmitter A but
transmitter A is not neighbour of reference transmitter), proceed as follows:
z If there is an existing symmetric link between both transmitters: hold down CTRL
on your keyboard and left click on the transmitter A.
z If no neighbourhood link exist between both transmitters: first, create a symmetric
neighbourhood link as explained above and then, hold down CTRL on your
keyboard and left click on the transmitter A.
4) U-Net displays an arrow directed to the reference transmitter; it is coloured as
transmitter A.
To remove an inwards neighbourhood link, proceed as follows:
3) In order to remove an existing outwards link between the reference transmitter
and a transmitter A, hold down SHIFT on your keyboard and left click on the
transmitter A.
Note:
Neighbourhood relationships are automatically updated in the intra-technology
neighbours table.
6.7.3 Allocating GSM/GPRS/EGPRS Resources Manually in U-Net
I. Assigning BSIC domains to transmitters
Once defined, a BSIC domain has to be assigned to a transmitter. Only BSICs

included in the assigned BSIC domain can be manually or automatically allocated to a
transmitter.
To assign a BSIC domain to a transmitter, proceed as follows:
Either:
or
6-91
Chapter 6
Then
1) Choose the Properties option from the context menu,
2) Click on the TRXs tab of the current dialog,
3) Use the What's this help to get description about the open dialog window,
4) In the Identification part, click on the scrolling menu and choose a BSIC domain
in the list,
5) Click OK to close the dialog
Note:
z The BSIC domain must be consistent with the defined BSIC format. When
choosing a format, U-Net adapts automatically the related domain in order not to
consider inconsistent values.
z BSIC domain associated to the transmitter can be changed afterwards.
z Once selected, BSIC domain dialog can be open by clicking on the button.
z The BSIC domain is an input required for manual or automatic BSIC allocation.
z When running the AFP, you can also select the BSIC allocation.
II. Assigning manually BSICs to transmitters
The colour code BSIC (Base Station Identity Code) for a transmitter is made up of the
NCC (Network Colour Code) and the BCC (BTS Colour Code). The NCC code is, for
example, 0 or 4 for France. The BCC code (respectively NCC) is a digit between 0 and
7.
The BCCH-BSIC pair permits, on a given territory, to identify precisely a cell. At a
higher level, it may exist identical BCCH-BSIC pairs characterising very distant zones.
In U-Net, you can either allocate it manually to each transmitter or automatically to all
transmitters in the network.
Once a BSIC domain has been allocated to a transmitter, it is possible either to
manually or automatically choose a BSIC among available ones for any transmitter.
To manually allocate a BSIC to a transmitter, proceed as follows:
Either:
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 you want to manage,
6-92
Chapter 6
or
appropriate Tx symbol (arrow),
Then
1) Choose the Properties option from the context menu,
2) Click on the TRXs tab of the current dialog,
3) Use the What's this help to get description about the open dialog window,
4) Click on the scrolling menu and choose a BSIC in the list,
5) Click OK to close the dialog
Note:
z The BSIC value must be consistent with the defined BSIC format. Only consistent
values are available in the BSIC scrolling menu.
z BSIC associated to the transmitter can be changed afterwards.
z The selected BSIC must be part of the chosen BSIC domain.
z Once chosen in single digit format, the related NCC-BCC format is automatically
displayed above the scrolling box.
z It is possible to edit the BSIC scrolling box. Furthermore, you can enter the BSIC
value with a NCC-BCC format in the scrolling box, and click the Apply button.
U-Net will convert it in the single digit format consistent with the related BSIC
domain.
III. Allocating manually a BCCH to transmitters
BCCH (Broadcast Control CHannel) permits the diffusion of the cell characteristic data,
including the steady diffusion of several types data systems. This channel must be part
both of the main frequency band (coming from the selected cell type) and allocated
channels in TRXs. The BCCH is defined on the timeslot 0 of a selected frequency.
To allocate manually a BCCH to a transmitter, proceed as follows:
Either:
or
6-93
Chapter 6

Then
1) In Non Hopping or Base Band Hopping, Create a new TRX of type BCCH and
enter the related channel, Or In Synthesised Frequency Hopping, Create a
new TRX of type BCCH, fill the related MAL in the TRX part, and enter the
channel on which will be located the timeslot 0 dedicated to the steady diffusion
of BCCH information.
Note:
You can also automatically a TRX of type BCCH by entering the related frequency in
the BCCH columns from the transmitter global table.
IV. Creating TRXs in transmitters
In U-Net, for GSM/GPRS/EDGE projects, channels are defined at the TRX level. The
manual allocation of frequencies is made by the management of TRXs in transmitters.
The allocation can be also made by filling the Channels column from the transmitter
table. When entering channel values in the table, TRXs of type TCH are automatically
created in the related transmitters.
BCCH can be assigned identically.
Automatic frequency allocation can also be made using the optional AFP module.
By using the advanced filter feature on transmitters, it is possible, for example, to
display only transmitters linked to a frequency and their adjacent ones. Using the filter
feature in the study display tab, it is also possible to display all cells with a specific
frequency (f), and also all cells with frequencies (f+1) and (f-1) in different colours.
V. Managing TRXs in transmitters
From transmitter properties, it is possible to list TRXs of transmitter and channels

allocated to TRXs. This TRX table can be automatically filled after an automatic
frequency planning. You may also fill it manually. It contains a TRX per line.
TRX is the transmitter level at which channels are defined.
To access the TRX table from the transmitter properties, proceed as follows:
Either:
6-94
Chapter 6

or
Then
4) Define the TRX settings in the TRXs part.
VI. Displaying the TRX list
Even if TRXs are linked to transmitters, it is possible to display all existing TRXs of a
network in an editable form.
To open the TRX general table, proceed as follows:
3) Choose the [Subcells: TRXs] command from the open menu.
4) Define the TRX settings.
5) The button helps you to manage the content of the TRX table.
VII. TRX property details
Whatever is the way to reach TRX properties (from transmitter properties or from the
TRX table), for any of them, U-Net details:
z Index
This is identification number of TRX. This number (integer) may be user-defined or
automatically given by U-Net (after closing the dialog).
z TRX type
z Channels
Specify channel(s) allocated to TRX: 1 channel per TRX if the hopping mode for the
TRX type is “Non Hopping” or “Base Band Hopping”, several channels per TRX if the
hopping mode for the TRX type is “Synthesized Hopping”.
Channel(s) can be either copied, or manually selected one by one in the scrolling
menu (select the box and click on the arrow to open the scrolling menu). The scrolling
menu offers you channels of the frequency domain assigned to this TRX type (Cell
type property dialog).
6-95
Chapter 6
Note:
When pasting a list of channels, separator must be a blank character.
z MAIO (Mobile Allocation Index Offset)

The MAIO is selectable for each TRX separately. It is used in case of frequency
hopping (BBH or SFH) to avoid intra-site collisions due to co or adjacent channel
consumption. This is an integer; its range of value is between 0 and N-1 (N is the
number of channels used in the hopping sequence). MAIO can be manually entered or
automatically allocated.
z Freeze Channels
Select this option to keep the current channel allocation at the TRX level when starting
a new AFP.
Note:
The Freeze channels option can be also imposed at the transmitter level only.
6.7.4 Using an AFP to Allocate Resources in U-Net

I. Adjusting AFP parameters from the data model
In U-Net, it is possible to adjust AFP parameters per transmitter and not only as global
constraints.
In the TRXs tab of the transmitter property dialog, it is possible to force:
Subcell part:
z The main frequency band used by propagation model when assigning cell types
to transmitters.
z The frequency domains (including the excluded channels) for each subcell in
which the automatic tool chooses frequencies as defined.
z The allocation mode (Free or Group constrained) for the AFP to allocate
frequencies to TRX.
z The allowed C/I and max percentage of interference per subcell.
z The minimum reception threshold for each subcell.
z The max MAL length allowed per subcell.
z The hopping mode, for each subcell of each transmitter.
z The site synchronisation at the subcell level.
z The support of DTX per subcell (or not).
6-96
Chapter 6
z The timeslot configurations.

Furthermore, U-Net is able to compute automatically the requested number of TRXs
(at the subcell level) for all transmitters of the network. When computed, values are
automatically reported in the subcell part of the transmitter property dialog boxes.
TRX part:
In the transmitter property dialog (TRXs tab), you can choose manually the
frequencies related to each TRX. The MAIO can also be manually specified.
Concerning the AFP itself, it is possible to freeze channels of each TRX at this level.
This way, existing channels will not be overwritten by any new automatic allocation.
In the AFP tab of the transmitter property dialog, it is possible to impose:
z A weight on cost function used for convergence on this specific transmitter. For
example, entering a value of 2 for a specific transmitter whereas the value for
other transmitters is 1 means that we will consider convergence when the
reached cost function on this transmitter will be half the one of the other
transmitters.
z To avoid recalculation by AFP of parameters as frequencies, HSNs and BSICs at
the transmitter level, it is possible to freeze them. Frequencies can be also frozen
at the subcell level (see above).
z Exceptional channel separations with other (transmitter, subcell) pairs that are
neither co-site nor neighbours of the currently considered (transmitter, subcell)
pair.
II. Defining exceptional separations for frequency allocation
In U-Net, the Separation table, in GSM/GPRS/EDGE projects, allows you to

impose/relax some channel separations between items which are neither co-cell, nor
co-site, nor part of neighbour transmitters during an automatic allocation of
frequencies. Standard separations are defined in the generic AFP dialog.
For example, if we take Tx1 and Tx2, which are neither neighbours nor co-site, we can
impose in the separation table a value of 3. This will mean that if we assign f1 to Tx1
and f2 to Tx2, the AFP has to respect: f1 − f2 ≥ 3 . This constraint is also checked by
the Audit tool.
The separations are defined per couple of (Transmitter, TRX type) pairs, and they deal
with imposing or relaxing constraints. Relaxing constraints means that the defined
separation in the Separation table has priority on the imposed separation between
co-site, co-cell or neighbour items. It is even possible to define intra-cell separations,
e.g. between BCCH and TCH subcells of a same transmitter.
Examples:
6-97
Chapter 6
z Tx1 and Tx2 are neither neighbours or co-site. We impose in the separation table
the following rules:
Separation of 3 channels between (Tx1, BCCH) and (Tx2, BCCH)
Separation of 2 channels between (Tx1, TCH) and (Tx2, TCH)
If we assign respectively f11 and f12 to the BCCH and the TCH of Tx1, and
respectively f21 and f22 to the BCCH and the TCH of Tx2, we must have:
f11 − f21 ≥ 3 f11 − f22 ≥ 2

, . Nevertheless, we could have f21 = f11 and f21 = f12 .
z We impose a co-cell minimum separation of 3. We defined also in the transmitter

table a separation of 2 for the (Tx1, BCCH) and (Tx1, TCH) pairs. So, if we assign
f11 to the BCCH and f12 to the TCH, it may be possible to have f11 − f12 = 2 , even
if there is a co-cell configuration.
For any transmitter, to define channel separations with any other transmitter, proceed
as follows:
Either:
or
Then
2) Click on the AFP tab of the current dialog.
4) In the displayed table window, enter the (Transmitter, TRX type) couples and
their related imposed separation.
5) Click either another table cell, or the button to validate and add a
new line to the table.
To access the exceptional pair table, proceed as follows:
3) Choose the [Frequency plan: Exceptional pairs...] command from the open menu.
6-98
Chapter 6
5) In the displayed table, enter the (Transmitter, TRX type) couples and their related
imposed separation.
6) Click another table cell to validate and add a new line to the table.
z The button helps you to manage the content of the Exceptional

separation table.
z Other constraints are imposed in transmitter properties.
z The separation table can also be completed from the AFP generic dialog.
z The Audit tool takes into account the defined separation table with priority
compared to co-cell, co-site or neighbour separation constraints.
z It is possible to Copy and Paste (Ctrl-C – Ctrl-V) the separation list in the tables.
z In the TRX type column, it is possible to select the ‘All’ value in order to force the
separation for all the subcells of the considered transmitter
III. Using the generic AFP interface
The role of an Automatic Frequency Planning tool (AFP) is the assignment of

frequencies within a GSM network, in order to match the traffic demand (number of
requested TRXs) with respect to the quality (e.g. limitation of interferences).
A certain number of inputs are defined in the data model (transmitter properties and
exceptional pairs of subcells) of from the generic AFP Graphic User Interface. In
addition, depending on the selected AFP model, specific parameters may be set.
The Automatic Frequency Planning (AFP) module of U-Net is an option that allows
users to automatically generate frequency plans for GSM and TDMA networks. The
following parameters may be allocated:
z Frequencies
z Frequency hopping groups (MAL)
z HSN, MAIO
z BSIC
The AFP aims to generate optimal allocations, i.e. allocations that minimise
interference over the network and comply with a set of constraints defined by the user.
The two main types of constraints are the separation constraints and the spectrum
limitations. The AFP uses a ‘cost function’ to evaluate frequency plans, and the aim of
the algorithm is to find frequency plans with minimal costs.
In U-Net, the GSM/GPRS/EDGE data model has been adapted to be consistent with
any AFP model. U-Net provides generic options and parameters, which can be taken
into account during the automatic frequency plan.
U-Net provides a set of generic dialogs available for any AFP model implemented by
various vendors. The different AFP models are activated in the same way.
6-99
Chapter 6
For any AFP model, the convergence criterion is based on a cost function taking into
account all the requirements given by the network inputs. The goal of the model is to
try to minimize the value of the cost function involved in the process. The cost function
mainly consists of two components. The first component is related to interferences, the
second one considers separation constraint violations. Both components are
normally added in order to get global cost. Nevertheless, the user will be able to
consider only the separation cost component.
Before starting an AFP session, you have to insure that the number of required TRXs
per transmitter has been already defined. The related traffic loads have an effect on
the cost function used in the AFP.
As separation constraints may be set on neighbours, this allocation should also be
performed before starting an AFP session.
Starting AFP
You may perform an automatic frequency planning on all the transmitters or only on a
group of transmitters.
To start an AFP session, proceed as follows:
2) Right click on the transmitters folder or on a group of transmitters.
3) Choose the [Frequency plan: Automatic allocation...] option from the context
menu.
The first step consists in setting AFP inputs such as the resources to allocate, the
choice of the subcells to be considered, and the separation requirements. During the
second step, U-Net loads and checks the network. The third step consists in optionally
computing the theoretical level of interference that the AFP model will have to
minimize. If you choose not to make this calculation, the mathematical model will work
with respect to separation constraints only. This dialog will allow you also to set the
AFP model and to run it. Finally, U-Net provides AFP results in the last step.
Note:
z An audit on the computed frequency plan is available.
z A channel search tool working on channels, BCCHs and BSICs allows you, for
example, to display the transmitters cells with a specific frequency (f) the ones with
frequencies (f+1) and (f-1) in different colours.
6-100
Chapter 6
IV. AFP Step 1: generic inputs
After having started an AFP session, the 1st step consists in the AFP generic inputs.
In this first dialog, you can:
1) In the General tab, check the boxes related to the resources you wish to
allocate during this AFP session. If the AFP model you are using supports this, it
is possible to allocate several resource types: channels (for NH or BBH subcells),
MAL and MAIO (for SFH subcells), HSN (for BBH and SFH subcells) and BSIC.
Note:
U-Net avoids creating TRXs without channels. Therefore, if the user does not ask for
MAL-MAIO assignment, all the SFH subcells are considered as “frozen”, and no TRXs
will be created for them. The same happens in case only a MAL-MAIO assignment is
selected. In this case, all NH and BBH subcells will be seen as frozen and no TRXs
will be created.
2) Then, indicate if you want all the potential interferers to be taken into account
by the AFP model. Check/uncheck the ‘Load all the potential interferers’ box. If
this box is unchecked, the cost function will only consist of the separation
violation cost.
3) In the Separations tab, click on the Exceptional pairs... button in order to
check/add separations within exceptional pairs of transmitters and subcells.
These separation constraints have priority on other separations (co-cell and
co-site separations as well as separations between neighbours) you may specify.
4) Then, define the channel separations within subcells of a same cell, within
subcells of co-site transmitters and between subcells of neighbours. You
may specify separations between BCCH subcells, traffic subcells and between
BCCH and traffic subcells.
5) Click Validate to run the loading of the selected network and its checking.
V. AFP Step 2: loading and checking the network
After the AFP generic inputs, U-Net loads and check the involved items in the 2nd step
U-Net loads:
z The transmitters to be allocated (we will call them “TBA transmitters”): Among all
the active and filtered transmitters, they are the ones that belong to the
transmitters folder for which the AFP was launched and to the focus zone as well.
6-101
Chapter 6
z The potential interferers with TBA transmitters if the option “Load all the potential
interferers” is selected. They are all the transmitters whose calculation radii
intersect the calculation radius of any TBA transmitter.
z The transmitters involved in the specified separation conditions with the TBA
transmitters: the neighbours, co-site transmitters, transmitters or subcells of
exceptional pairs and neighbours of neighbours in case of BSIC allocation.
Note:
z In case of the BSIC allocation, neighbours of neighbours are systematically loaded.
z If no focus zone exists in the .atl document, U-Net takes into account the
computation zone.
The calculated cost takes into account all the loaded transmitters. On the other hand,
only TBA transmitters may be assigned the resources selected in the previous dialog.
Other loaded transmitters are considered as “frozen” for all the types of assignments:
BSIC, HSN, MAL, MAIO and channels.
The calculated cost takes into account all the loaded transmitters. On the other hand,
resources are not assigned to all the TBC transmitters. Therefore, it is important to
know the transmitters to be allocated (we will call them “TBA transmitters”): they are
the active and filtered transmitters located inside the computation zone, which belong
to the folder from which the AFP has been started. Only TBA transmitters may be
assigned the resources selected in the previous dialog. Other loaded transmitters are
considered as “frozen” for all the types of assignments: BSIC, HSN, MAL, MAIO and
channels.
Once loaded, U-Net checks the network consistency. It reports mainly non-blocking
warnings in an additional event viewer. These warnings deal with, for example, values
out of their range or inconsistencies of the existing allocation.
For example, U-Net can report the fact that a list of frequencies is assigned to a TRX
supporting a non-hopping or base band hopping mode. In this case, AFP will fix it if
frequencies are not frozen.
In case of inconsistent values (e.g. a value of 100 for the traffic load), these will be
replaced by U-Net in order to avoid blocking the AFP process. Nevertheless, in some
cases, like an empty HSN (resp. BSIC) domain when the HSN allocation is requested,
the AFP process is stopped and an error message is reported to the user in order to fill
the domains.
6-102
Chapter 6
Caution:
Information given by the event viewer has to be read carefully before going further.
After having checked the messages in the event viewer, click the Close button to go
on.
U-Net then opens a new dialog dealing with other AFP settings.
VI. AFP Step 3: generic AFP settings
After having loaded and checked the involved network, U-Net opens a dialog made of
three parts.
The first part reports the validated network conditions:
z Resources to be allocated
z Separation constraints
z Type of the loading
Full: both potential interferers (interferences taken into account) and
transmitters/subcells considered in separation requirements have been loaded and
checked.
Partial: only transmitters/subcells involved in separation requirements have been
loaded and checked.
z State of the network loading: number of loaded subcells, number of subcells
selected for the AFP process, warnings during the consistency checking, etc...
At this step, the status box in the part “Step 3” indicates that the allocation will be
based on separation constraints only.
The second part of the dialog enables user to calculate/import interference histograms
interferences are taken into account in AFP (not only separation requirements).
Interference histograms can be computed only if the user has previously selected the
option “Take into account interferences” (leading to the loading of all the potential
interferers) in the previous dialog. Else, buttons are greyed.
In the first case, for each pair (interfered subcell, interferer subcell), U-Net calculates a
C/I value on each bin of the interfered subcell service area (determined by the min
reception threshold defined at the subcell level for a fixed cell edge coverage
probability); all the subcells are supposed to share the same channel. Then, U-Net
integrates C/I values calculated over the service area of the interfered subcell and
determines an interference histogram. Histogram shows the different interference
probabilities. Interference probability is the probability that users of the interfered
6-103
Chapter 6
subcell receive a C/I higher than a C/I value; interference probability is stated either in
percentage of interfered area or in percentage of interfered traffic.
Example: Let (Tx1, BCCH) and (Tx2, BCCH) be the victim and interferer subcells. The
service areas have been defined using best server with 0 dB margin. The interference
probability is stated in percentage of interfered area (see Figure 6-3).
Figure 6-3 Representation of the probability
In that case, we observe that the probability for C/I (BCCH of Tx2 on the BCCH of Tx1)
to be greater than 0 is 100% (which is normal because Tx1 is best server). The
probability to have a C/I value at least equal to 31 is 31.1%. If we introduce the fact
that the required C/I level on the BCCH of Tx1 is 12, we consider in that case that,
since the probability that C/I is at least equal to 12 is 93.5%, the percentage of
interfered areas in the service area of the BCCH of Tx1 caused by the BCCH of TX2 is
6.5%.
To calculate interference histograms, proceed as follows:
1) Click on Calculate... to compute interference histogram for each pair of subcells.
2) In the Interference calculation dialog, specify the servers to study (All, best signal
level per HCS layer, best signal level of the highest priority HCS layer), a margin
in case of a best signal level study, the cell edge coverage probability and select
the calculation option on how to define the interference probability:
z Traffic spreading based on default capture maps: the probability is expressed in
percentage of interfered traffic and takes into account both traffic maps and the
traffic load coming from dimensioning (or user-defined).
z Uniform traffic spreading: the probability is expressed in percentage of interfered
area and integrates the traffic load coming from dimensioning (or user-defined).
This method cannot consider precisely traffic hotspots but is much more faster
than the previous one.
3) Then, click on OK to run the interference histogram calculations.
6-104
Chapter 6
Caution:
Changing some transmitter or subcell properties such as power offset, reception

threshold and transmitter power or EIRP makes invalid interference histograms. In this
case, you must recalculate them.
Note:
z U-Net only takes into account the subcells of loaded transmitters to calculate
interference histograms.
z The resolution used to calculate interference histograms is the default resolution
defined in the Predictions property dialog.
z When calculating C/I, U-Net applies shadowing margins (depending on the entered
cell edge coverage probability and the model standard deviation on the pixel) to the
C values only.
z It is possible to export the computed interference histograms (by clicking the Export
button). When exporting interference histograms, U-Net creates two ASCII text
files in the specified directory: xxx.dct and xxx.clc (xxx is the user specified name).
The .dct file contains the name of transmitters taken into account in AFP and their
associated identification numbers; the .clc file details interference histogram of
each pair (interfered subcell, interferer subcell). For further information about the
storage format, please refer to the Technical Reference Guide.
To import an existing interference histogram, proceed as follows:

1) Click on Import... and specify the .clc file to be imported. U-Net looks for the
associated .dct file in the same directory and uses it to decode transmitter
identifiers. When this file is unavailable, U-Net assumes that the transmitter
identifiers are the transmitter names.
6-105
Chapter 6
Note:
z When you successively import several .clc files containing the same relationship,
U-Net considers the first imported relation only (relation found in the first imported
file). The ones found in the other files are ignored.
z File multi-selection is supported. Therefore, it is possible to import several .clc files
at once.
z U-Net supports a simplified import format as well (format of a line: Interfered
subcell, Interfering subcell, co-channel interference probability, adjacent channel
probability). For further information, please refer to the Technical Reference Guide.
z No validity control is performed when importing an interference histogram file. Be
sure that imported histograms are consistent with the current configuration.
z U-Net only imports interference histograms related to loaded transmitters.
z The histogram interference computation needs path loss results. If matrices are
invalid, they will be updated during the computation process.
After computing or importing interference histograms, the status box in the part “Step
3” indicates that the allocation will be based on separation constraints and
interferences.
Caution:
If the interferences were supposed to be taken into account, but no histogram has
been determined, the AFP process will be based on separation constraints only.
Finally, the third part of the dialog enables you to:

1) Choose the AFP model.
2) Adjust its parameters by clicking the properties button.
Note:
All the AFP models listed in the Modules tab will be available in the scrolling list.
3) Indicate a target time (in minutes) on which the AFP will base its method in order
to lower its cost function and converge to a solution.
6-106
Chapter 6
Note:
This target time is used only by the model to select the best suited method. This
means that you will not be able to consider the result reliable as far as the target time
is not reached. The model will be able to stop by itself before this target time, but if
after this elapsed time the model considers that the result is not satisfying enough, it
will go on improving the frequency plan.
4) In case interferences are taken into account, you may select the DTX option and
enter an activity factor to consider discontinuous transmission mode on
subcells, which support DTX.
5) Once these parameters are set, click on Run to start the automatic frequency
planning.
VII. AFP Step 4: generic outputs
After starting AFP, U-Net displays a new dialog providing information about the AFP
progress. It indicates:
z The cost of the best solution (best cost).
z The elapsed time since the session has been started.
z The value of the cost component related to separations only.
In addition, in the general AFP display space, some general information about the
current solution is given in real time (depending on the selected AFP model).
As said in step 3, the target computation time provides to the model an indication
about the method to take in order to find a suitable solution. Nevertheless,
computations can be stopped any time by clicking the Stop button and confirming it.
Best results (related to the best solution – lower cost value) will be then displayed as
they are.
When calculations are completed or stopped, U-Net displays the frequency plan
proposed by the AFP tool. All the results/violations are listed in a dialog (see Figure
6-4). The first tab (Frequency plan) shows a table listing the assigned resources.
Resources can be coloured in different ways in the table for different reasons such as:
z Artic blue: frozen resource.
z Red: resource modified since the previous allocation but with separation
constraint violation.
z Green: resource modified since the previous allocation with respect to separation
constraints.
z Black: resource not modified.
z Blue: resource assigned with separation constraints respected.
z Purple: resource assigned but with separation violation.
6-107
Chapter 6
z Brown: resource not modified with separation violation.

z Grey: transmitters and subcells involved in computations.
Figure 6-4 Results
You may choose the results you want to display. It is actually possible to list the results
related only to:
z Cells (BSICs)
z Subcells (HSNs)
z TRXs (Channels/MAL, MAIO and related separation violations)
Use the boxes “Cells”, “Subcells” and “TRXs” to do this. Of course, all of them can be
displayed at the same time.
You may choose to display the resources assigned during the current AFP session to
the TBA transmitters (option “Studied transmitters only”) and in addition, the existing
frequency plan of potential interferers and transmitters involved in separation
requirements (option “Transmitters involved in computations”).
In the table, when pointing the resources, a tip balloon gives the meaning of the
colouring. In case of separation violations, a button is available at the right side of the
6-108
Chapter 6
table. Its name indicates the type of violation. When clicking on it, U-Net opens a
message box (see Figure 6-5) detailing the reason.
Figure 6-5 Message box
Finally, you may export the table content to tabulated ASCII text files. Click on the
export button. Then, in the Export dialog, proceed as explained.
When there are separation violations, it is interesting to open the Separation constraint
violations tab. Click on the “Compute and Display” button in order for U-Net to
summarise all the separation violations of the current AFP session.
Note:
The bottom part of the Frequency plan tab displays the messages related to the last
solution (maybe not the best one) and potential related allocation problems.
Before closing this dialog, use the Commit button to assign the allocated resources.
Note:
An audit on the computed frequency plan is available.
6.7.5 Frequency Plan Analysis
I. Checking the frequency plan consistency
Once frequencies have been assigned to TRXs (manually, automatically), U-Net

provides a tool in order to check the consistency of the current frequency plan.
This tool enables you to check the consistency and the validity of several parameters
involved in a GSM/GPRS/EDGE network. U-Net performs the consistency checking
on:
z The transmitters to be allocated (we will call them “TBA transmitters”): Among all
the active and filtered transmitters, they are the ones that belong to the
transmitters folder for which the AFP was launched and to the focus zone as well.
6-109
Chapter 6
z The potential interferers with TBA transmitters if the option “Load all the potential
interferers” is selected. They are all the transmitters whose calculation radii
intersect the calculation radius of any TBA transmitter.
z The transmitters involved in the specified separation conditions with the TBA
transmitters: the neighbours, co-site transmitters, transmitters or subcells of
exceptional pairs and neighbours of neighbours in case of BSIC allocation.
Some audits are automatic; other ones are user-defined.
First, this tool automatically checks the following points:
z Definition of a unique BCCH TRX per transmitter
z Consistency between TRXs and related cell types
z No empty domain
z Frequency domains included in reference frequency bands (if Frequencies box is
ticked)
z In case of Non Hopping or Base Band Hopping: definition of one unique
frequency per TRX
z In case of Synthesized Frequency Hopping: definition of a frequency list per TRX
z In case of Synthesized Frequency Hopping: respect of max MAL lengths
z In case of Synthesized Frequency Hopping: MAIO less than the number of MAL
frequencies
z Optionally, it was also checking the consistency of the current frequency plan,
HSN and BSIC allocation (compliance with assigned domains, the allocation
strategy and separation constraints)
z The number of timeslots per subcell must be lower than or equal to the
multiplexing factor (-1 for the BCCH subcell)
z The number of timeslots per subcell cannot be null
Furthermore, you can parameter some additional checking on Frequencies, HSN
and/or BSIC elements:
z Check of the compliance of the current frequency plan with the allocation strategy
(Free or Group constrained) at the TRX type level (subcells in transmitters)
z Check of the respect of domains for allocated resources of type frequency, HSN
or BSIC. These domains are tested in order to check that they are not empty.
Concerning frequencies, the tool is able to check compliance of frequency
domains within related frequency bands
z Consistency between the defined BSIC format and the assigned BSICs (BSIC
domain option checked)
z Consistency between the excluded channels (at the subcell level) and the
assigned ones (Frequency domain option checked)
z In case of Synthesized Frequency Hopping and Group constrained strategy,
respect of exactly a group of a domain for the allocated TRXs (Frequencies and
Allocation strategy options checked)
6-110
Chapter 6
z Respect of the exceptional separation constraints (between subcells) prior to

co-cell, co-site or neighbour separations (relaxation)
z A transmitter and its neighbours must not have the same (BSIC-BCCH) pair
((BSIC, BCCH) pair option checked)
z Two neighbours must not have the same (BSIC-BCCH) pair ((BSIC, BCCH) pair
option checked)
To run the checking algorithm, proceed as follows:
1) In the General tab of the dialog, select the parameters you want to check.
2) In the Separations tab, click on the Exceptional pairs... button in order to
check/add separations within exceptional pairs of transmitters and subcells.
Then, define the channel separations within subcells of a same cell, within
subcells of co-site transmitters and between subcells of neighbours. You
may specify separations between BCCH subcells, traffic subcells and between
BCCH and traffic subcells.
3) In the Detailed results tab, specify the detail level you wish to display in the
Event viewer. When no option is selected, U-Net displays global warnings or/and
error messages according to the problems. It will display an error message per
transmitter/subcell/TRX/pair of transmitters if you choose “Error messages”.
When selecting “Warning related to separations”, it displays a warning for each
separation constraint violation. If “Additional warnings” is checked, it will give a
detailed list of all the warnings.
4) Click on OK to start the consistency checking.
Checking results about consistency are displayed in the tasks tab of the event viewer.
This can be also stored in an external log file.
II. Checking consistency between transmitters and subcells
An additional tool is available to check consistency of some subcell and TRX

characteristics which can be duplicated at the transmitter level which can occurs after
incorrect use of the archive function in database connection.
U-Net checks for each transmitter that:
z The number of TRXs indicated in the Transmitters table corresponds to the
number of TRXs listed for this transmitter in the TRXs table.
z The list of channels used by the transmitter consists of all the channels assigned
to TRXs of the transmitter.
z The BCCH of the transmitter is the same than the channel assigned to BCCH
TRX of the transmitter.
z The number of required TRXs indicated in the Transmitters table is equal to the
sum of required TRXs of the transmitter subcells.
z The hopping mode of the transmitter corresponds to the one of its TCH subcell.
To start the Audit tool, proceed as follows:
6-111
Chapter 6
1) Right click on the Transmitters folder and select the Subcells: Audit... command.
2) In the Subcell consistency dialog, two options are available: you may display a
report in the events viewer (U-Net provides a list of problems grouped by
transmitters) and solve the detected problems (U-Net updates characteristics of
transmitters inconsistent with their subcells and TRXS).
3) Click on OK to start the checking tool.
III. Using the channel search tool in GSM/GPRS/EDGE
U-Net provides a tool which allows you to search for BCCH and/or non BCCH
channels and BSIC. This is an additional tool to analyse a frequency plan; you may
use it in order to quickly visualise channel and BSIC reuse on the map.
To display the Search window, select the "Channel search window" in the View
general menu. U-Net opens a floating window that you can keep at any location on
your screen, or dock at the bottom of the map, like the Point analysis window.
The user defines a channel or a BSIC, U-Net finds and highlights (by allocating
significant colours) the transmitters which are assigned that channel or BSIC.
Three tabs are available to help the user find transmitters which are assigned a given
channel, BSIC or BCCH-BSIC. U-Net changes the colours of the transmitter arrows on
the map. To obtain a 2D graphic display, it is necessary to have preliminary defined
and calculated a study "Coverage by transmitter" (with a colour display by transmitter).
The colours of the coverage cells will then follow the colours of the transmitters.
z Search for channels
The user defines a channel, which can be searched within the control channels
("BCCH"), within the other channels ("non BCCH"), or indifferently within all the
channels ("All") of the network, without differentiating subcells. U-Net runs through the
channel list of each transmitter and gives the colour RED to co-channel transmitters,
ORANGE to multi-adjacent channel transmitters (+1 and -1), BLUE (+1) and GREEN
(-1) to adjacent channel transmitters and GREY to the others. If it happens that a
transmitter meets several criteria, the co-channel criterion has priority meaning that
RED colour always overrides the others.
z Search for BSIC
The user defines a BSIC value. U-Net runs through all the BSIC within the network
and gives the colour RED to transmitters with that BSIC and GREY to the others.
z Search for BCCH-BSIC
The user defines a pair of BCCH-BSIC values. U-Net runs through all the BCCH-BSIC
pairs within the network and gives the colour RED to transmitters with that
BCCH-BSIC and GREY to the others.
6-112
Chapter 6
Note:
z To restore the initial transmitter colours, click the button in the

bottom of the map.
z A useful feature is to display as label on the map the BCCH, BSIC and channel list
of each transmitter, using the Display tab of the Transmitters folder properties.
IV. Computing KPIs in GSM/GPRS/EDGE
U-Net allows the user to calculate and analyse the Key Performance Indicators, such
as the reduction factor, the blocking probability, and delay that are currently set in the
network. This can be thought of as an analysis tool that enables the user to observe
how much the network satisfies basic criteria of performance.
To run a KPI calculation, proceed as follows:
1) Left click the Data tab from the Explorer window.
2) Expand the Traffic analysis folder by left clicking on the button.
3) Right click on a Traffic capture item, according to which you want to dimension
the network, to open the context menu.
4) Select KPI calculation....
5) In the KPI calculation dialog, choose the dimensioning model to be used for
computations.
You can select the columns you want to display in the table. To do this, click on the
Displayed columns button and select information you wish to display.
6) Click on Calculate.
For each subcell of each transmitter, U-Net gives:
z Network settings such as the number of TRXs, the number of packet, shared and
circuit timeslots and the traffic load, the maximum number of TRXs that can be
placed in the transmitter (this value is indicated in the dimensioning model
properties), the maximum rate of traffic overflow (%) (specified in the subcell
properties) and the half rate traffic ratio (%) (defined in the subcell properties).
Note:
When the maximum rate of traffic overflow and the Half-Rate traffic ratio values are
different for BCCH and TCH subcells, U-Net takes the BCCH subcell values.
6-113
Chapter 6
z Traffic capture results such as the packet traffic demand (kbps), the average
demand in packet timeslots, the average number of timeslots per connection
(packet) and the circuit traffic demand (Erlangs), the average demand in circuit
timeslots and the average number of timeslots per connection (circuit).
Note:
In case of concentric cells, the traffic demand on TCH subcells is different from the
one evaluated during the traffic capture. It is calculated from the traffic demand of the
capture and the effective rate of traffic overflow (instead of the maximum rate used in
traffic analysis).
For packet services, the average number of timeslots per connection corresponds to
the average number of downlink timeslots, which mobile terminals can simultaneously
communicate over. For circuit switched services, the number of timeslots per
connection is 1 in case of full rate; else it depends on the half rate ratio.
z For a circuit switched service, you will find the served circuit traffic (Erlangs), the
effective rate of traffic overflow and the effective blocking rate.
The served circuit traffic corresponds to the circuit traffic demand less the effective
overflowed circuit traffic.
In case of Erlang B, the effective rate of traffic overflow corresponds to the effective
blocking rate; this value is deduced from the required number of circuit timeslots
(shared + dedicated) and the circuit traffic demand in Erlang B tables.
In case of Erlang C, the effective rate of traffic overflow is zero except if the maximum
number of TRXs is exceeded; the effective blocking rate is inferred from the number of
circuit timeslots (shared + dedicated) and the circuit traffic demand in Erlang C tables.
z For a packet switched service, results are the served packet traffic (kbps), the
effective rate of traffic overflow, the minimum throughput reduction factor and
KPIs such as the throughput reduction factor, the delay and the blocking rate.
The served packet traffic corresponds to the packet traffic demand less the effective
overflowed packet traffic.
The effective rate of traffic overflow corresponds to the rejected packet traffic due to
missing packet timeslots.
The minimum throughput reduction factor is stated in percentage; it corresponds to the
highest reduction (lowest percentage) that can be applied to the maximum rate in
order to supply service with the minimum permissible rate (defined for the service).
KPIs are deduced from the packet load and the number of available connections by
using quality charts defined in the dimensioning model properties.
6-114
Chapter 6
7) After a computation, click on Commit to assign the results to subcells (the load
and the effective rate of traffic overflow).
Note:
KPI calculation is based on a traffic capture. Modifications of traffic map(s), traffic
parameters and transmitter properties (e.g. calculation area, E/GPRS equipment,...)
have an influence on the traffic capture. Therefore, if you modify some of these data,
you must recalculate the traffic capture before calculating KPIs.
6.8 Specific GSM/GPRS/EDGE Prediction Studies
6.8.1 Setting Specific Coverage Conditions in GSM/GPRS/EDGE Studies

Whatever the project type is, the way to create, manage and run coverage studies is
identical. Only study parameters are different.
Hence, in GSM/GPRS/EDGE projects, even if coverage study dialogs are composed
of the three classical tabs:
z The General tab where you may rename the study, define the coverage resolution,
add some comments, define group, sort and filter criteria, on the coverage display
only (not on the results).
z The Condition tab where you can specify the study parameters.
z The Display tab to define coverage display settings.
Coverage conditions are managed with some specifics related to GSM/GPRS/EDGE
technology.
GSM/GPRS/EDGE specific settings in predictions are described below:
1) Indeed, coverage conditions include the possibility to choose between two
options for the definition of reception thresholds. You can either manually enter a
lower threshold for the transmitters to be part of a coverage, or you can choose
the lower threshold defined in subcells (taking into account the power offset) for
this. To do this, select the button next to the threshold boxes. In each pixel,
U-Net will then take into account all subcells respecting its minimum signal level
at that point for the coverage. The best server notion (+ margin) and the cell edge
coverage probability options are then considered.
2) Concerning the best (or second best) server option, U-Net provides the possibility
to consider or not HCS layers and associated priorities.
Let us assume that:
6-115
Chapter 6
z Each transmitter, Txi, belongs to a Hierarchical Cell Structure (HCS) layer, k, with
a defined priority.
z The maximum range option (available in the System tab of the Predictions
property dialog) is inactive.
In case of all the servers are considered (All), for each HCS layer, k, the service area
of Txi corresponds to the bins where:
rec (tt ) (or Ltot or Total − Losses

Txi Txi
In case of the best signal level per HCS layer and a margin, for each HCS layer, k,
the service area of Txi corresponds to the bins where:

Txi Txi
and
Txi
Prec
j ≠i
( )
(BCCH ) ≥ Best PrecTxj (BCCH ) − M
where
Note:
from Txi is the highest one.
servers.
In case of the best signal level on the highest priority layer and a margin, the
service area of Txi corresponds to the bins where:

Txi Txi
and
Txi
Prec
j ≠i
( )
(BCCH ) ≥ Best PrecTxj (BCCH ) − M
and
Txi belongs to the HCS layer with the highest priority
where
6-116
Chapter 6

Note:
from Txi is the highest one.
servers.
In case of the second best signal level per HCS layer and a margin, for each HCS
layer, k, the service area of Txi corresponds to the bins where:

Txi Txi
and
Txi
Prec
j ≠i
( )
(BCCH ) ≥ 2nd Best PrecTxj (BCCH ) − M
where
2nd Best function: considers the second highest value.
Note:
from Txi is the second highest one.
from Txi is either the second highest one or 2dB lower than the second highest
one.
from Txi is 2dB higher than the signal levels from transmitters, which are 3rd best
servers.
6-117
Chapter 6
Note:
Choosing the Best signal level per HCS layer makes U-Net consider the best server of
each HCS layer on the considered pixel. Overlapping best server zones are enabling.
3) Furthermore, it is possible to restrict the reception on certain TRX types using the
appropriate scrolling box. It is possible to select the All option in interference
studies.
4) In interference studies, it is possible also to use the button in order to
consider the min C/I threshold defined per subcell as lower or upper ratio signal to
noise for interference definition.
5) As for the TRX type filter at reception on a pixel (See above 3 - ), you can also
restrict the study to potentially interfered TRX type using the appropriate scrolling
box. Selecting the (All) option makes U-Net study C/I over each TRX type.
6) Other specific options are relative to interference studies or GPRS/EDGE studies
and are described in the corresponding context sensitive help.
Note:
Since each pixel can be seen as a receiver, its related properties have to be set (e.g.:
adjacent channel protection level).
6.8.2 Studying Interfered Zone Predictions
The determination of interference zones is possible as soon as channels have been

allocated to the transmitters composing the current network, exactly like for
interferences study using the point analysis tool. This study is closely based on the
principle of common prediction studies from which it takes the definition mode and to
which it adds an interference condition. Nevertheless, specific coverage
GSM/GPRS/EDGE conditions are available. Prediction parameters are also standard.
The interfered zones study enables the user to predict areas where transmitters are
interfered (taken into account depending on signal level) by other transmitters sharing
either an identical channel or an adjacent channel as function of signal to noise ratio.
U-Net computes C/I level on each calculation bin where conditions on signal reception
are satisfied. Then, it considers in coverage the bins where the calculated C/I is lower
than an upper threshold and colours the bin depending on an interfered transmitter
attribute. The interference definition is proper to each study.
6-118
Chapter 6
To prepare this prediction study, in the prediction creation steps, select the interfered
zone option from the study types window. The open window is made of three tab
get description about the fields available in the windows.
The interfered zone study is a template for which the field 'Transmitter' is selected by
default in the display tab. In that case, interfered zones will be displayed with the same
colours than the ones defined for each transmitter.
Note:
z Shadowing margins (depending on the entered cell edge coverage probability and
the model standard deviation at the receiver) are applied only on the C values.
These are not taken into account in I determinations.
z U-Net offers default calculation and display parameters when creating interference
area prediction studies but it is possible to colour by any other consistent attribute
just by adjusting display.
z The study depends on the hopping mode, and the study will be made on:
z The most interfered channel (this one with the lowest C/I) of TRXs belonging to the
selected TRX type (BCCH, TCH, TCH_INNER) or the most interfered channel of all
the TRX types (All), in case of a non hopping mode,
z The MAL of the selected subcell (BCCH, TCH, TCH_INNER) or the most interfered
MAL of all the subcells (All), in case of base band hopping,
z The most interfered MAL-MAIO of the selected subcell (BCCH, TCH, TCH_INNER)
or all the subcells (All), in case of synthesised frequency hopping.
z on each pixel Check the detailed results option if you want to display details on
interference:
z per TRX (one channel) in Non Hopping mode,
z per MAL (indicating the related TRX type) in Base Band Hopping mode,
z per MAL-MAIO (indicating the related TRX type) in Synthesised Frequency
Hopping mode,
z per transmitter in the current prediction folder.
z Since each pixel can be seen as a receiver, its related properties have to be set
(e.g.: adjacent channel protection level).
6-119
Chapter 6
6.8.3 Computing a Coverage Study by C/I Level
The determination of zones by C/I level is possible as soon as channels have been
allocated to the transmitters composing the current network, exactly like for
interferences study using the point analysis tool. This study is closely based on the
principle of common prediction studies from which it takes the definition mode and to
which it adds an interference condition. Nevertheless, specific coverage
GSM/GPRS/EDGE conditions are available. Prediction parameters are also standard.
The coverage by C/I level study enables the user to predict C/I levels involving
transmitters (taken into account depending on signal level) sharing either an identical
channel or an adjacent channel with other transmitters as function of signal to noise
ratio. The interference definition is proper to each study.
To prepare this prediction study, in the prediction creation steps, select the Coverage
by C/I level option from the study types window. The open window is made of three tab
get description about the fields available in the windows.
The coverage by C/I level study is a template for which the field 'C/I level' is selected
by default in the display tab. In that case, each layer corresponds to an area where the
C/I level exceeds a defined minimum threshold. Numerous options related to signal
level coverage are available in the Display tab.
6-120
Chapter 6
Note:
z Shadowing margins (depending on the entered cell edge coverage probability and
the standard deviation per clutter class) are applied only to the C values. These are
not taken into account in I determinations.
z U-Net offers default calculation and display parameters when creating coverage by
interference level but it is possible to colour by any other consistent attribute just by
adjusting display.
z When selecting a "highest signal level" option with a margin or the "All" option, you
may have areas where several transmitters are interfered. On these bins, several
C/I values are calculated. Therefore, you may choose to display either the lowest
one of these values (Min C/I option) or the highest one (Max C/I option) in the Field
scrolling box of the display tab.
z The study depends on the hopping mode, and the study will be made on:
z The most interfered channel (this one with the lowest C/I) of TRXs belonging to the
selected TRX type (BCCH, TCH, TCH_INNER) or the most interfered channel of all
the TRX types (All), in case of a non hopping mode,
z The MAL of the selected subcell (BCCH, TCH, TCH_INNER) or the most interfered
MAL of all the subcells (All), in case of base band hopping,
z The most interfered MAL-MAIO of the selected subcell (BCCH, TCH, TCH_INNER)
or all the subcells (All), in case of synthesised frequency hopping.
z on each pixel Check the detailed results option if you want to display details on
interference:
z per TRX (one channel) in Non Hopping mode,
z per MAL (indicating the related TRX type) in Base Band Hopping mode,
z per MAL-MAIO (indicating the related TRX type) in Synthesised Frequency
Hopping mode,
z per transmitter in the current prediction folder.
6.8.4 Studying Interferences with the Point Analysis
I. Point analysis
With the point analysis tool, U-Net is able to display interferers for a given transmitter,
at the receiver location on the map using the propagation model as defined before
(with priority order respect). To analyse interferences, user must assign frequencies to
6-121
Chapter 6
transmitters beforehand. Furthermore, since each pixel can be seen as a receiver, its
related properties have to be set.
To make active the Interference analysis window (GSM/GPRS/EDGE projects only):
environment.
3) Left click on the Interference tab.
4) Select the transmitter you want the receiver to be currently connected from the
associated scrolling list.
5) Click the button from the toolbar.
6) Move over the map to display the transmitter interferers at any point.
7) The data appearing in the Point analysis window on receiver interference at
the point clicked on will be as follows:
You can study a TRX type or all the TRX types. U-Net displays the signal level and
interference received on:
z The most interfered channel of the selected transmitter subcell (BCCH, TCH,
TCH_INNER) or the most interfered of all the transmitter subcells (All), in case of
a non hopping mode.
z The MAL of the selected transmitter subcell (BCCH, TCH, TCH_INNER) or the
most interfered MAL of all the transmitter subcells (All), in case of base band
hopping.
z The most interfered MAL-MAIO of the selected transmitter subcell (BCCH, TCH,
TCH_INNER) or the most interfered MAL-MAIO of all the transmitter subcells (All),
in case of synthesised frequency hopping.
Finally, you may take into account either contribution of all the interferers, or
co-channel interferers only, or adjacent channel interferers only, in the interference
level evaluation.
II. Results
In this tab, U-Net provides for a given receiver:

z The signal level received from the interfered subcell.
z Either the overall interference received from all the interferer transmitters (both
co-channel and adjacent channel interferers are considered), or the co-channel
interference received from all the co-channel interferers, or the adjacent channel
interference received from all the adjacent channel interferers.
z The interference level received from each interferer. Interferers are sorted in a
descending signal level order.
6-122
Chapter 6
U-Net informs you when reduction factors of signal level and interference level are
applied; reception bars consist of two parts, a full part, which shows the received
signal or interference level, and an empty part corresponding to signal or interference
level reduction. In case of the interfered subcell reception bar, signal level reduction
can be due to the subcell power offset. For each interferer transmitter reception bar,
interference level reduction can be due to power offsets of subcells, adjacent channel
protection and fractional load.
In addition, U-Net indicates the most interfered channel in case of non hopping (the
most interfered MAL in case of base band hopping and the most interfered MAL-MAIO
in case of base band hopping) and the signal to noise ratio at the receiver.
III. Scenario
The studied transmitter is Site14_2; we analyse potential interferences from all the
interferers (both co-channel and adjacent channel interferers) received on all its TRXs
( i.e. we study the worst case). The requested cell edge coverage probability is 75 %.
Like for the interfered zones and coverage by C/I levels studies, U-Net analyses the
most interfered channel of the studied transmitter in case of non hopping mode (see
Figure 6-6).
Figure 6-6 Point analysis
z Site 14_2 consists of two subcells, one is TRX type BCCH (no power offset); the
other is TRX type TCH (no power offset). The channel 4 is assigned to one TRX
TCH.
z Site 9_2 consists of two subcells, one is TRX type BCCH (no power offset); the
other is TRX type TCH (no power offset). The channel 4 is assigned to TRX
BCCH.
z Site 2_2 is a transmitter made of two subcells, one is TRX type BCCH (no power
offset); the other is TRX type TCH (power offset 3dB). The channel 4 is assigned
to one TRX TCH.
z Site 12_3 is a transmitter made of two subcells, one is TRX type BCCH (no power
offset); the other is TRX type TCH (no power offset). The channel 3 is assigned to
one TRX TCH.
z The Non hopping mode is assigned to TRX types of these transmitters.
6-123
Chapter 6
Point analysis leads to the following results:

z The 1st bar in brown shows the signal level from the transmitter Site14_2 at the
receiver (-77.5 dBm). Initially, this value would have been -71.4 dBm, but signal
level value is decreased by 6.1 dB due to the shadowing margin.
z The 2nd bar indicates the overall interference for interfering stations (-87.7 dBm).
z The following bars show, respectively, in descending order, signal levels of each
interferer subcell on the studied station (Site9_2: -89.2 dBm, Site2_2: -93.5 dBm
and Site12_3: - 106.94 dBm).
You can see that the most interfered channel of Site14_2 is the channel 4 and the C/I
received is 10.2 dB. Analysis of interferers leads to the following comments:
z The reception bar of Site9_2 is full. The channel 4 is assigned to TRX BCCH of
this transmitter; it is a co-channel interferer. On the other hand, no power offset is
defined.
z The reception bar of Site2_2 is partly filled. The channel 4 is assigned to one TRX
TCH of this transmitter; it is a co-channel interferer. The empty part of the
reception bar is due to power offset (3 dB) specified for the TCH subcell.
z Finally, the reception bar of Site 12_3 is partly filled. The channel 3 is assigned to
one TRX TCH of this transmitter; this is an adjacent channel interferer. Here, the
empty part of the reception bar is due to the adjacent channel protection level is
set to 18 dB. No power offset is defined for TCH subcell. Nevertheless, if a
supplementary power offset had been defined for this subcell, the related bar
would have been cleared from 3dB more.
If the bar representing interference of the station is full, this means that this station
interference on the interfered station is not attenuated by one of the factors described
above.
Note:
z Only signal level (C) is downgraded by the shadowing margin (depending on the
entered cell edge coverage probability and the standard deviation per clutter class).
The interference level (I) is not altered by the shadowing margin.
z Neither DTX, nor traffic load of TRXs are taken into account to evaluate the
interference levels (U-Net calculates interference level by considering 100% as
voice activity factor and traffic load).
z If a MAL is defined on the most interfered subcell, you can obtain, for example, the
following result: Interference on: TCH M.A.L. 512 513 514 515 516 517 518 519
520 521 522 523 524 525
6-124
Chapter 6
6.8.5 Creating a Coverage by GPRS/EDGE Coding Schemes
This study displays areas according to the used coding schemes. The coverage colour
depends on the assigned coding scheme. The coding scheme choice is determined
from radio conditions (C or/and C/I). Therefore, the strongest C and C/I values are, the
higher the coding scheme will be. When both graphs are used, U-Net uses the lowest
one.
As this study can be based on C/I, some parameters are similar to the ones found in
interference predictions.
To prepare this prediction study, in the prediction creation steps, select the
GPRS/EDGE option from the study types window. The open window is made of three
tab windows: General, Condition, and Display. For all of these, use the What's this
help to get description about the fields available in the windows.
In the condition tab, specific coverage GSM/GPRS/EDGE conditions are available.
Moreover, if you check the 'Calculations based on C/I option, both conditions on signal
(C ) and signal noise ratio (C/I) must be satisfied to be able to use a given coding
scheme.
The coverage by coding scheme is a template for which the field 'Coding Schemes' is
selected by default in the display tab. In that case, each layer shows the coding
schemes to be used in the transmitter coverage area. You can also choose to display
your coverage in term of Best coding schemes. The resulting coverage shows the best
coding scheme that can be used on each pixel. Other options related to GPRS/EDGE
coverage are available in the Display tab.
Note:
z U-Net offers default calculation and display parameters when creating
GPRS/EDGE prediction studies.
6.8.6 Computing a Coverage by GPRS/EDGE Rate per Timeslot
This study displays the areas where the rate carried by transmitter on one packet
timeslot exceeds the user-defined thresholds. The rate is determined from rate=f(C)
or/and rate=f(C/I) graphs defined for each coding scheme. When both graphs are
used, U-Net chooses the less favourable rate.
6-125
Chapter 6
As this study can be based on C/I, some parameters are similar to the ones found in
interference predictions.
To prepare this prediction study, in the prediction creation steps, select the
GPRS/EDGE option from the study types window. The open window is made of three
tab windows: General, Condition, and Display. For all of these, use the What's this
help to get description about the fields available in the windows.
In the condition tab, specific coverage GSM/GPRS/EDGE conditions are available.
Moreover, if you check the 'Calculations based on C/I option, both conditions on signal
(C) and signal noise ratio (C/I) must be satisfied to be able to use a given coding
scheme.
To calculate the coverage per rate/timeslot, two coverage display options are available.
Firstly, you can choose the Rate/timeslot. In that case, each layer shows the rates that
a transmitter can carry one timeslot. You can also choose to display your coverage in
term of Best rate/timeslot. The resulting coverage gives the best rate/timeslot per pixel
from the previous display. Other options related to GPRS/EDGE coverage are
available in the Display tab.
Note:
z U-Net offers default calculation and display parameters when creating
GPRS/EDGE prediction studies.
6-126
GENEX U-Net Wireless Network Planning Software Chapter 7 GSM/TDMA AFP Module
Chapter 7 GSM/TDMA AFP Module
7.1 Overview
The U-Net AFP model supports Base Band Hopping (BBH) and Synthesized
Frequency Hopping (SFH) modes. It enables you to automatically plan:
z Channels and HSN (Hopping sequence numbers) in case of BBH.
z MAL (Mobile Allocation List), MAIO (Mobile Allocation Index Offset) and HSN in
case of SFH.
z Only channels in case of non hopping.
z BSICs.
The U-Net AFP model is implemented using simulated annealing, taboo search, graph
heuristics and machine learning. It manages its time resources to match the user time
directives. If given a lot of time, the model will use a major part of this time to “learn” the
network. During the learning phase, the model adjusts its internal parameters. At the
end of the user-defined time period, the AFP switches to a randomised combinatorial
search phase. If the user-defined time period is extremely short, the AFP may carry on
only deterministic heuristics that converge quickly. In all the cases where randomness
is used, the random seed is initialised by the machine time.
The network learning is performed by executing many fast and deterministic instances
of the AFP. The one, which gains the best performance, is memorized in the document
and is therefore the most adapted to the specific network. The next time that an AFP
will be executed it will start where the learning process ended – it will use the parameter
profile of the best solution stored in the .atl document.
The convergence criterion studied by the U-Net AFP model is based on a cost function
taking into account all the requirements given by the network inputs. The goal of the
model is to try to minimize the value of the cost function.
7.2 Managing the U-Net AFP Module

7.2.1 Overview
The cost function is stated in interfered Erlangs (i.e. in number of interfered timeslots); it
corresponds to the cost of the entire loaded network. It is based on four components,
the cost component due to interferences, the cost component due to separation
violations, the cost component due to missing requested TRXs and the cost component
due to assigned frequencies out of the domain. Each cost component is described
hereafter. Nevertheless, for further information about the cost function calculation,
please refer to the Technical Reference Guide.
7-1
Parameters considered in the cost function components can be fully controlled by the
user. Some of these parameters are part of the general data model (quality
requirements, allowed percentage of interference per subcell); others can be managed
inside the property dialog of the U-Net AFP model such as separation costs and
diversity gains.
Note:
z At the end of an allocation, the final result in term of reached total cost does not
depend on the network initial state (initial cost) on condition that state is correct from
a consistency checking point of view. From this, we can say that the AFP starts from
scratch every time the user starts the allocation.
z In addition, the AFP cost will always start from the previously reached cost. Let's
imagine that the results of an AFP have been committed. If we start a new AFP with
the same settings, the initial cost will have the value of the final cost of the previous
AFP session.
7.2.2 Accessing the U-Net AFP Properties
In the property dialog of the U-Net AFP model, you may manage some parameters to
be considered in the cost function and in addition, give some directives to the AFP
model.
To open the U-Net AFP model property dialog, proceed as follows:
Either
1) In the Modules tab, open the Frequency allocation modules list.
2) Right click on the U-Net AFP Module subfolder.
3) Select the Properties command in the context menu.
Or
1) Right click on the Transmitters folder.
2) Select the [Frequency plan: Automatic allocation…] command from the opened
scrolling menu.
3) In the second dialog (after the loading of the network), select the model in the
scrolling box.
4) Click the Properties button.
7-2
Note:
Like for the propagation models, it is possible to duplicate the AFP model in several
ones with different sets of parameters. They will be available in AFP sessions (once
duplicated, the model is then available in the AFP scrolling list of the generic AFP
dialog).
The AFP property dialog consists of 7 tabs: the General, Cost, HSN, MAL, MAIO, BSIC,
and Advanced. The Cost and Advanced tabs include parameters to take into account in
the cost function estimation. The other tabs refer to the allocation strategies on HSN,
MAL, MAIO and BSICs required to the AFP.
7.2.3 Defining the AFP Parameters
I. Defining interference cost in the AFP
The interference cost component is evaluated for each TRX. Estimation is based on
interference histograms calculated for pairs of subcells and takes into account
frequency and interferer diversity gains modelling frequency hopping and gain due to
DTX.
For each single TRX, U-Net estimates the probability for the TRX to be interfered. A
TRX v is interfered by a TRX i when the C/I level on TRX v is lower than an “evaluated
threshold”. This one is calculated by adding the different gains listed above to the
minimum C/I threshold specified in the subcell properties. U-Net reads the interference
probability (probability to have a C/I lower than the “evaluated threshold”) in the
corresponding interference histogram. Then, for each TRX v, it adds the interference
probabilities from all the TRX i; the sum is limited to 100% of the TRX traffic.
The interference component can be weighted in the global cost value.
For further details, please refer to the Technical Reference Guide.
II. Defining separation violation cost in the AFP
The separation violation cost component is evaluated for each TRX.
Estimation is based on costs specified for the required separations. Let S12 denote the
required separation between two transmitters Tx1 and Tx2 in the network. If we assign f1
at Tx1 and f2 at Tx2, and if f1 − f2 < S12 , then we can consider that the separation
requirement is not respected. A separation can be strongly or weakly broken: for
example, the pair of frequencies 1 and 2 breaks a separation requirement of 3. The pair
of frequencies 1 and 3 breaks this requirement as well, but is closer to answer it, since
7-3
the reached separation is 2. Therefore, this second pair should provide a lower cost
than the first one.
In addition, frequencies that are part of a MAL with a low fractional load and that break
a separation should not be weighted the same as in a non-hopping separation breaking
case. Therefore, the cost is weighted by the burst collision probability (which is the
multiplication of the victim and interferer fractional loads) and the interferer diversity
gain.
For each single TRX, separation violations are summed up. This sum is limited to 100%
of the TRX traffic. The same limitation stands for the interference cost component: it
can complete the amount of “ruined” traffic to 100% but not more. This means that a
TRX with many separation violations is considered as 100% ruined and has a cost
component due to interference equal to 0.
Note:
The TRX traffic depends on the number of circuit and composite timeslots available
and the TRX traffic load. These parameters are given in the subcell properties.
For further details, please refer to the Technical Reference Guide.

To set the cost of separation violations, proceed as follows:
1) Access the U-Net AFP property dialog.
2) Click the Cost tab.
3) In the Separations part, scroll in the list until displaying the requested
separation “s”.
4) Click on the reached separation “k” and enter the desired cost value.
Note:
z The higher the violation is, the greater the cost value should be.
z If the same TRX is involved several times in separation violations, its cost value will
be limited to 100% (100% of its traffic is interfered).
z The separation component can be weighted in the global cost value.
III. Miscellaneous costs involved in AFP cost function
In addition to the standard interference and separation violation cost, U-Net provides
two other components in the global cost value. These cannot be set.
1) Missing TRX cost component
7-4
By default, U-Net considers for each missing TRX that 100% of the TRX traffic is ruined.
The tax per missing TRX can be modified in the AFP model property dialog (Cost tab).
Let us imagine a transmitter involved in AFP session for which the number of requested
TRXs is 5; this transmitter is not a TBA transmitter. It has currently 3 assigned TRXs. In
that case, the two missing and undefined TRXs have to be considered for this
allocation because they would have an effect on the current frequency plan if allocated.
In the Missing TRX component part, you may indicate the cost value to be considered
when a TRX is missing. The default cost for a missing TRX is 1. In order not to take into
account this component in the global cost, uncheck the Active box.
2) Corrupted TRX cost component
U-Net considers a TRX as corrupted when:
z An allocated frequency does not respect the frequency domain constraints.
z More than one frequency is assigned to a NH TRX.
z No channel is assigned to a TRX.
The MAL assigned to a group constrained SFH TRX is not strictly a group of its domain.
By default, U-Net considers 1000% of the TRX traffic as cost. Value of this parameter
can be modified in the AFP model property dialog.
In the Corrupted TRX component part, you may indicate the cost value to be
considered when a TRX is corrupted. The default cost for a corrupted TRX is 10. In
order not to take into account this component in the global cost, uncheck the Active
box.
IV. Weighting cost components in the AFP
In the global value of the U-Net AFP cost function, it is possible to impose a weight on
the cost components of the global cost.
To introduce a weight on the different components (separation, interference) in the
global cost, proceed as follows:
2) Click the Cost tab.
3) In the Separation of Interferences part, you can enter a value between 0 and 1 as
a multiplicative factor on the component.
V. Setting interferer diversity gain in the AFP
Values specified in the second table of the Cost tab are only used in case of frequency
hopping. When a frequency hopping mode is used, a mobile is linked to a list a
frequencies (MAL) and the frequency collision probability is spread over the several
frequencies.
The use of frequency hopping drives to two types of gains, the interferer diversity gain
and the frequency diversity gain. This last one is described in the Interferences tab. The
7-5
interferer diversity gain (in dB) models the geographic diversity of interferers and is
applied both to the interference and separation cost components of the cost function.
This gain depends on the MAL length of the victim TRX. A long MAL leads to average
the negative effects over users with different geographic locations. In the interference
cost component, the gain is applied to lower the defined minimum C/I threshold per
subcell, i.e. to shift the entrance point in the interference histograms. In the separation
violation cost component, the gain is translated in a linear value and applied directly to
the separation cost by division.
To set the values of the interferer diversity gains, proceed as follows:
2) Click the Advanced tab.
3) In the top table, select the MAL length and specify a gain value.
Example:
Let us consider the following simple case of a network consisted of two TRXs. The first
one TRXi carries the (MAL)i and is interfered by TRXj carrying the (MAL)j. TRXi and
TRXj have a separation requirement of 2. Their lengths are respectively 5 and 4.
Unfortunately, they share a same frequency (separation = 0). In this case, the cost of
the separation violation is 90 for each TRX. The interferer diversity gain is 1.4 for a MAL
of 5 and 1.2 for a MAL of 4.
In the interference histograms of the interfered TRXi (resp. TRXj), the entrance point is
shifted by 1.4 dB (resp. 1.2 dB).
For TRXi, with a gain of 1.4 dB, the effect on the separation cost is given by the linear
(1.4 10 )
value 10 ≈ 1 .38 . The contribution of the MAL length of 5 divides the separation cost
for this interfered MAL by 1.38. Considering the initial separation cost and the interferer
diversity gain, we reach a separation cost of (90 1.38 ) = 65 .21 . If we now consider the
fractional load (considering the fact that only one channel of each TRX causes
interferences, with (MAL length)I=4 and (MAL length)j=4, the collision probability is
1 20 . The separation violation cost to consider for TRXi is therefore 3.25%.
In the same way, the separation violation cost to consider for TRXj is:
 
1  90 
= 3.41%
20   110.2  
 10   
.
Now, in order to compute the separation violation cost on each TRX, the current values
have to be multiplied by the number of timeslots dedicated to traffic (by default, 7 in
BCCH and 8 for TCH) and by its related traffic load (given in units of Erlang/timeslot).
7-6
VI. Setting the frequency diversity gain in the AFP
The frequency diversity gain is taken into account in case of frequency hopping. When
a frequency hopping mode is used, a mobile is linked to a list a frequencies (MAL) and
the frequency collision probability is spread over the several frequencies.
The use of frequency hopping drives to two types of gains, the interferer diversity gain
and the frequency diversity gain. This first one is described in the Cost tab. The
frequency diversity gain (dB) models the gain due to diversity of multi-path effects and
is applied to the interference cost component only. Depending on the victim MAL length,
the gain is applied to lower the defined minimum C/I threshold per subcell.
To set the values of the frequency diversity gains, proceed as follows:
3) In the middle table, select the MAL length and specify a gain value.
VII. Tuning the gain due to low time slot use ratio in the AFP
The gain due to low time slot use ratio is taken into account in case of interferers
supporting DTX. When considering an interferer, the use of DTX reduces its amount of
interference. This is modelled by a gain (in dB) associated to the voice activity factor ; it
is applied to the minimum C/I threshold of the interfered subcell.
To tune the gains due to low time slot use ratio, proceed as follows:
3) In the bottom table, select a gain in the list and specify an activity factor. For
each voice activity factor, a certain gain value will be estimated.
Note:
z DTX is only applied over subcells for which the “DTX supported” box has been
flagged (Subcell property).
z Take care not to mix up voice activity factor in DTX and traffic load. Traffic load
represents the average occupancy of TRXs and is always applied to the value of
cost function (as defined per subcell during dimensioning).
7-7
7.2.4 Defining the AFP Allocation Strategies
I. Overview
The U-Net AFP model is currently capable of doing free MAL assignment or
pre-defined MAL assignment. The instruction indicating the assignment mode to be
used is given at the subcell level.
When using a free assignment mode, the AFP model may assign any MAL that
satisfies the needs of TRXs. Then, the size of MAL, the HSNs and the MAIOs can be
assigned either according to user directives, or completely freely. In the last case, the
AFP model takes all the decisions during allocation; the HSN and MAIO assignments
and the MAL size determination are carried out so as to obtain a user defined frequency
reuse and fractional load.
When using a group constrained assignment model, the AFP model may only assign a
pre-defined group in the domain. The success of the assignment depends on the
definition of groups. Each MAL length represented in the domain should fulfil the
following conditions: there must be many MALs having the same length and all together
should cover the domain.
Examples:
z An example of a badly planned domain is a domain containing many 3-length
groups, a single 5-length group and many 8-length groups. If restricted to such a
domain, the AFP will not produce an optimal plan. On the other hand, by adding
only a few more 5-length groups, the quality can be improved.
z An example of a good group definition is a domain of 40 frequencies where at least
60 groups are defined, 15 3-length groups, 12 4-length groups, 10 5-length
groups…
Note:
z The AFP model will always assign the same MAL to all the TRXs within a same
subcell.
z The assignment mode “Group constrained” is considered for SFH only. In NH and
BBH the assignment mode is always free.
z When many groups are defined, the quality is almost as good as with free
assignment.
In order to get correct results, the user must keep in mind some of the possible
trade-offs, for example:
7-8
z When assigning the same HSN and MAL to synchronized subcells, the lowest
bound of the MAL length is increased, since it must be at least equal to the total
number of TRXs sharing the same HSN.
z When assigning the same HSN and MAL to synchronized subcells, we limit the
choice of the MAL frequencies.
z When assigning the same HSN and MAL to synchronized subcells, we may gain
more on interference and frequency diversity.
In order to understand how to work the AFP model, some notions are detailed below.
An atom is a set of synchronized subcells sharing the same HSN, the same frequency
domain, and the same MAL. The MAIO assignment of an atom manages the frequency
collisions between the MALs in it. If an atom contains more than one subcell, the AFP
may assign partially different MALs to it.
Working at the atom level, and with the definition of a user-defined synchronisation
reference (subcell table), the AFP model is able to fully support the benefits of
synchronization in a GSM network.
II. Setting HSN strategy in frequency hopping (AFP)
In U-Net, the HSN (Hopping Sequence Number) is defined at the subcell level. So, for
interfering and non-synchronized subcells, the AFP model tries to allocate different
HSNs. When the subcells are synchronized (usually within a same site), it tries to
assign the same HSN and different MAIOs.
To access the HSN strategy parameters, proceed as follows:
2) Click the HSN tab.
In this tab of the U-Net AFP dialog, the user can manage the HSN allocation in order to
respect one of the following options:
z Assignment of the same HSN to all the subcells of a site.
z Assignment of the same HSN to all the subcells of a transmitter.
z Assignment of different HSNs to a pair of subcells which mutually interfere.
z Optimised assignment (free HSN) so as to obtain the best frequency assignment.
7-9
Note:
The following constraints do not allow the AFP model to comply with some directives:
z If two synchronised subcells on the same site have different "Max MAL lengths" they
cannot be assigned with the same HSN.
z If two synchronised subcells on the same site have different frequency domains
(maybe due to forbidden channels), they cannot be assigned with the same HSN.
z If two synchronised subcells on the same site have different assignment mode (free,
grouped), they cannot be assigned with the same HSN.
III. Defining MAL targets in SFH (AFP)
Settings available in the MAL tab are taken into account for SFH only. The AFP model
uses these directives in order to determine the MAL and MAL length to be assigned to
each subcell.
You may choose either to assign the same MAL to all the TRXs of an atom or to allow
allocation of different ones. Then, in order to determine the MAL length to be assigned,
the AFP proceeds in this order:
When using a group constrained assignment model, the AFP model may only assign a
pre-defined group in the domain. Only the length of groups available in the domain may
be selected.
For any assignment model (group constrained or free), the AFP model may either
assign the MAL with the maximum length allowed (user-defined in subcell properties)
or freely choose the MAL length according to the following directives:
To access the MAL targets parameters, proceed as follows:
2) Click the MAL tab.
z Target frequency reuse
Both the MAL size determination and the HSN assignment are carried out so as to
obtain a user defined frequency reuse. This value can be edited.
The frequency reuse ratio represents the ratio between the MAL length and the total
number of frequencies in the domain. The reuse ratio is not directly linked to the reuse
pattern. Nevertheless, we can assume that a 1x1 reuse pattern has a frequency reuse
ratio of 1. A 4x12 reuse pattern can have a reuse ratio between 1/4 and 1/12,
depending on whether all TRXs sharing the same sites have the same MAL (and HSN)
or not (considering synchronisation at the site level).
7-10
Note:
z This directive has a meaning in SFH only.
z This directive is used only if the option “Adjust MAL length” is checked. Else, the
specified value is not taken into account.
z MAL size strategy

It is possible to choose a MAL size strategy when allocating different MALs to the TRXs
of an atom. You may decide to use either a short MAL strategy or a long MAL strategy.
A long MAL strategy enables the AFP model to profit from the hopping gains. On the
other hand, it may be harder to find frequencies for these MALs.
Note:
z This directive has a meaning in SFH only.
z This directive is considered only if the option “Adjust MAL length” is checked.
z Target fractional load

Both the MAL size determination and the HSN assignment are performed so as to
obtain a user defined fractional load. The value of the target fractional load parameter
can be edited.
A fractional load of is obtained if the number of TRXs using a certain MAL is only times
the size of this MAL (Our notion of fractional load does not require taking into account
the traffic load. It is always smaller or equal to 1.). It equals 1 in NH or BBH modes.
The target fractional load cannot be always obtained; we will consider this parameter as
a guideline rather than a constraint. When it can be reached, the AFP model will choose
a MAL length 1/ times higher than the number of TRXs in the biggest subcell of the
atom.
7-11
Note:
z This directive has a meaning only in case of SFH.
z The target frequency reuse directive has a higher priority than the target fractional
load directive.
z This directive is used only if the option “Adjust MAL length” is checked. Else, the
specified value is not taken into account.
z The value of this parameter can be auto calibrated by the AFP model if you check
the box “Automatic adjustment”.
IV. Managing MAIO preferences in SFH (AFP)
When working in Synthesized Frequency Hopping, it is possible to fix some targets to

the AFP.
To access the MAIO preferences parameters, proceed as follows:
2) Click the MAIO tab.
Two allocation options are available:
z Staggered: The MAIOs assigned to TRXs of a subcell are evenly spaced.
z Free: The AFP model freely assigns MAIOs (without constraint on the MAIO
spacing).
The AFP assigns MAIOs to TRXs so as to reuse the same MAL within a subcell, within
a transmitter, or even within a site. The MAL-MAIO allocation is carried out at the same
time in order to respect the separation requirements between frequencies on air.
V. Setting BSIC usage diversity in the AFP
The U-Net AFP provides the possibility to define a strategy on the BSIC usage.
To access the BSIC usage strategy parameters, proceed as follows:

2) Click the BSIC tab.
3) Choose the BSIC allocation strategy:
z Minimal: The AFP model uses a minimum number of BSICs; it will reuse the same
BSICs.
z Maximal and homogeneous: This strategy consists in using as many BSICs as
possible. In addition, the AFP model will choose BSICs evenly distributed in the
whole domain.
BSIC allocation is based on neighbourhood links between cells defined in the
Neighbours table.
Example: we assume that we have three transmitters, A, B and C.
7-12
z 1st case: A has two neighbours, B and C. The AFP model assigns different BSICs
to A, B and C if they have the same BCCH.
z 2nd case: A is neighbour of B and C. The AFP model assigns different BSICs to A,
B and C if they have the same BCCH.
A A
N N N N
B C B C
1st case: B and C neighbours of A 2nd case: A neighbour of B and C

It is possible to consider an additional constraint on interferences. If you select the
option “Load all the potential interferers” when starting AFP (and then, import/calculate
interference histograms), the AFP model assigns different BSICs to potential interferers,
which have the same BCCH.
Finally, the BSIC allocation is compliant with the strategy selected in the BSIC tab of the
AFP model property dialog.
7.3 U-Net AFP module GUI

7.3.1 U-Net AFP Cost Tab
Figure 7-1 AFP Cost tab
7-13
This tab (Figure 7-1) allows you to set the different components composing the global
cost value. Each component mat be or not considered (weight or tax =0).
It is useful to differently handle small and big amounts of interference. For example, it is
better to have 10 transmitters with up to 2% of interfered traffic rather than only two
transmitters with up to 10% of interfered traffic.
A quality target, the % max of interference, is specified for each subcell (subcell
properties). This one enables AFP to differentiate small and big amounts of
interference.
If you select the option “Do not include the cost of TRXs having reached their quality
target”, U-Net will only take into account the cost of TRXs, which exceeds this quality
target. If the cost of a TRX is less than the quality target, then AFP dismisses it.
On the other hand, this quality target is not considered when selecting the other option
“Take into account the cost of all the TRXs”. In this case, AFP includes the cost of all the
TRXs in the global cost.
7.3.2 U-Net AFP HSN Tab
Figure 7-2 AFP HSN tab
This tab (Figure 7-2) enables you to give an allocation strategy in case of frequency
hopping. You may specify HSN directives (in case of SFH or BBH).
7-14
7.3.3 U-Net AFP MAL Tab
Figure 7-3 AFP MAL tab
hopping. You may specify MAL size directives (in case of SFH).
7-15
7.3.4 U-Net AFP MAIO Tab
Figure 7-4 AFP MAIO tab
hopping. You may specify MAIO preferences (in case of SFH).
7-16
7.3.5 U-Net AFP BSIC Tab
Figure 7-5 AFP BSIC tab
hopping. You may set the BSIC usage diversity.
7-17
7.3.6 U-Net AFP Advanced Tab
Figure 7-6 AFP advanced tab
hopping. You may set:
z The interferer diversity gain.
z The frequency diversity gain.
z The gain depending on the time slot use ratio.
The interferer diversity and the frequency diversity gains are defined for different MAL
lengths. All of these parameters available in the dialog are used to evaluate the
interference cost component. Only the interferer diversity gain has an influence on the
separation cost component.
7-18

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

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

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

Încărcat de

Drepturi de autor:

Formate disponibile

HUAWEI

GENEX U-Net Wireless Network Planning Software

Huawei Technologies Proprietary

Manual Version T2-030183-20050205-C-1.10

Product Version V100R001

Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,

Bantian, Longgang District, Shenzhen, P. R. China

Postal Code: 518129

Huawei Technologies Proprietary

All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any

, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,

Huawei Technologies Proprietary

Manual Version Notes

Huawei Technologies Proprietary

Chapter 2 The Working Environment introduces the operations of the U-Net

Chapter 4 Managing Radio Network Data introduces the management of the

Chapter 5 Managing Computations in U-Net introduces the calculation of regular

Chapter 6 GSM/GPRS/EDGE/TDMA Project Management introduces the use of

Chapter 7 GSM/TDMA AFP Module introduces the frequency planning function of

Huawei Technologies Proprietary

Chapter 9 CDMA/CDMA2000 Project Management introduces the use of U-Net in

Chapter 10 Managing Measurements introduces the two measurement functions of

Chapter 11 Co-planning Features introduces the co-planning function of U-Net.

Chapter 13 Multi-user Features introduces the multi-user function of U-Net.

Chapter 15 Radio Network Dimensioning introduces the network functions and

The manual is intended for the following readers:

The manual uses the following conventions:

Huawei Technologies Proprietary

III. GUI conventions

Button names are inside angle brackets. For example, click

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

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

Huawei Technologies Proprietary

Chapter 1 Getting Started............................................................................................................. 1-1

Chapter 2 The Working Environment .......................................................................................... 2-1

Huawei Technologies Proprietary

2.3.8 Getting Distances on the Map................................................................................. 2-8

Huawei Technologies Proprietary

2.8 Using Handy Tools........................................................................................................... 2-47

Chapter 3 Managing Geographic Data ........................................................................................ 3-1

Huawei Technologies Proprietary

3.2.5 Scanned Images ..................................................................................................... 3-4

Huawei Technologies Proprietary

3.10.2 Managing Population Maps................................................................................. 3-33

Chapter 4 Managing Radio Network Data................................................................................... 4-1

Huawei Technologies Proprietary

4.6 Repeaters ........................................................................................................................ 4-32

Chapter 5 Managing Computations in U-Net.............................................................................. 5-1

Huawei Technologies Proprietary

5.3.10 Working with Standard Propagation Model Recommendations ......................... 5-27

Chapter 6 GSM/GPRS/EDGE/TDMA Project Management ........................................................ 6-1

Huawei Technologies Proprietary

6.5.4 GSM/GPRS/EDGE Traffic Analysis ...................................................................... 6-71

Chapter 7 GSM/TDMA AFP Module ............................................................................................. 7-1

Huawei Technologies Proprietary

Chapter 1 Getting Started

Table 1-1 The highlights of U-Net

Advanced network design features High-performance propagation