technical reference guide

AT230_TRG_E1

Technical Reference Guide 2.3.0

Table of contents

T

Table of contents

4 Unauthorized reproduction or distribution of this document is prohibited © Forsk 2004

Table of contents

© Forsk 2004 Unauthorized reproduction or distribution of this document is prohibited 5

TABLE OF CONTENTS

I INSTALLATION ....................................................................................17 I.1 ATOLL INSTALLATION...................................................................................................17

I.1.1 WORKSTATION REQUIREMENTS ....................................................................................................................... 17 I.1.2 INSTALLATION PROCEDURE ............................................................................................................................. 17 I.1.3 TROUBLESHOOTING ....................................................................................................................................... 18

I.2 FLOATING LICENSE INSTALLATION.................................................................................18 I.2.1 REQUIREMENTS............................................................................................................................................. 18

I.2.1.a License Server requirements................................................................................................................ 18 I.2.1.b Firewall network requirements.............................................................................................................. 19

I.2.2 INSTALLATION PROCEDURE ............................................................................................................................. 19 I.2.2.a Overview............................................................................................................................................... 19 I.2.2.b Installation on the server....................................................................................................................... 19 I.2.2.c Installation on the server or clients ....................................................................................................... 19 I.2.2.d Installation on clients ............................................................................................................................ 19

II MULTI-USER ENVIRONMENTS...........................................................23 II.1 ORACLE DATABASE .................................................................................................23

II.1.1 CREATING THE PROJECT ACCOUNT .................................................................................................................. 23 II.1.2 CREATING TABLES ......................................................................................................................................... 23 II.1.3 CREATING OTHER USERS................................................................................................................................ 24 II.1.4 ADVANCED CUSTOMISATION............................................................................................................................ 24

II.1.4.a Example 1: Managing site sharing........................................................................................................ 24 II.1.4.b Example 2: Managing users by postcode............................................................................................. 25

III MEMORY REQUIREMENTS.................................................................29 III.1 INTRODUCTION ........................................................................................................29 III.2 DISK SPACE REQUIREMENTS....................................................................................29

III.2.1 NETWORK-WIDE INPUT ................................................................................................................................... 29 III.2.2 CELL-SPECIFIC RESULTS................................................................................................................................ 29 III.2.3 NETWORK-WIDE OUTPUT................................................................................................................................ 29 III.2.4 TEMPORARY DISK SPACE ............................................................................................................................... 30 III.2.5 OTHERS ....................................................................................................................................................... 30

III.3 RAM REQUIREMENTS..............................................................................................30 III.3.1 GENERAL...................................................................................................................................................... 30 III.3.2 UMTS SIMULATIONS ..................................................................................................................................... 30 III.3.3 PREDICTIONS ................................................................................................................................................ 31

IV ATOLL ADMINISTRATION FILES........................................................35 IV.1 USER CONFIGURATION FILE (.CFG) ............................................................................35

IV.1.1 DESCRIPTION ................................................................................................................................................ 35 IV.1.2 CREATION..................................................................................................................................................... 35

IV.1.2.a Examples.............................................................................................................................................. 35 IV.1.2.a.i Example 1: Geographic data set.......................................................................................................................35 IV.1.2.a.ii Example 2: Folder configuration.......................................................................................................................36 IV.1.2.a.iii Example 3: Computation zone and study list ...................................................................................................36 IV.1.2.a.iv Example 4: AFP Configuration........................................................................................................................36 IV.1.2.a.v Example 5: Macros..........................................................................................................................................36

IV.1.3 AUTOMATIC LOADING ..................................................................................................................................... 37 IV.2 ATOLL.INI FILES.......................................................................................................37

IV.2.1 DESCRIPTION ................................................................................................................................................ 37

Table of contents


IV.2.1.a Site and transmitter names................................................................................................................... 37 IV.2.1.b Automatic renaming of transmitters and cells ....................................................................................... 38 IV.2.1.c Modelling method of antenna patterns.................................................................................................. 38 IV.2.1.d Computation options............................................................................................................................. 38 IV.2.1.e Information displayed in the status bar ................................................................................................. 38 IV.2.1.f Consideration of shadowing in Ec/Io calculation................................................................................... 39 IV.2.1.g Licence expiry date............................................................................................................................... 39 IV.2.1.h Displaying milliseconds in the event viewer.......................................................................................... 39 IV.2.1.i BSIC format .......................................................................................................................................... 39 IV.2.1.j Tiff colour convention............................................................................................................................ 39

IV.3 STUDIES.XML ..........................................................................................................40 IV.3.1 DESCRIPTION ................................................................................................................................................ 40 IV.3.2 CREATION..................................................................................................................................................... 40

IV.3.2.a Example................................................................................................................................................ 40

V ATOLL DATABASE STRUCTURE.......................................................43 V.1 OVERVIEW ..............................................................................................................43 V.2 TABLES ..................................................................................................................43

V.2.1 COMMON TABLES........................................................................................................................................... 43 V.2.1.a Antennas table...................................................................................................................................... 43 V.2.1.b Sites table............................................................................................................................................. 44 V.2.1.c Transmitters table................................................................................................................................. 44 V.2.1.d TplTransmitters table ............................................................................................................................ 46 V.2.1.e FrequencyBands table.......................................................................................................................... 48 V.2.1.f PropagationModels table ...................................................................................................................... 48 V.2.1.g Coordsys table...................................................................................................................................... 48 V.2.1.h Units table............................................................................................................................................. 49 V.2.1.i Receivers table..................................................................................................................................... 49 V.2.1.j Customfields table ................................................................................................................................ 49 V.2.1.k Networks table...................................................................................................................................... 49 V.2.1.l Secondaryantennas table..................................................................................................................... 50 V.2.1.m Repeaters table .................................................................................................................................... 50 V.2.1.n Tables dedicated to site list management............................................................................................. 50

V.2.1.n.i SitesListsNames table .......................................................................................................................................50 V.2.1.n.ii SitesLists table..................................................................................................................................................50

V.2.1.o Tables dedicated to equipment management....................................................................................... 51 V.2.1.o.i TMAEquipments table .......................................................................................................................................51 V.2.1.o.ii FeederEquipments table...................................................................................................................................51 V.2.1.o.iii BTSEquipments table ......................................................................................................................................51

V.2.1.p Tables dedicated to microwave links management .............................................................................. 51 V.2.1.p.i Links..................................................................................................................................................................51 V.2.1.p.ii LinkEquipments table........................................................................................................................................52 V.2.1.p.iii LinkEquipmentsIRF table .................................................................................................................................52

V.2.1.q Tables dedicated to neighbour management........................................................................................ 52 V.2.1.q.i Neighbours table ...............................................................................................................................................52 V.2.1.q.ii NeighboursExt table..........................................................................................................................................53 V.2.1.q.iii NeighboursConstraints table ............................................................................................................................53 V.2.1.q.iv NeighboursConstraintsExt table.......................................................................................................................53

V.2.2 CDMA2000 1XRTT 1XEV-DO, IS-95 CDMAONE, UMTS WCDMA TABLES.................................................... 54 V.2.2.a CDMACells table .................................................................................................................................. 54 V.2.2.b CDMAEquipments table ....................................................................................................................... 55 V.2.2.c CDMAEquipmentsCEsUse table .......................................................................................................... 55 V.2.2.d CarriersType (only for CDMA2000 1XRTT 1xEV-DO, IS-95 cdmaOne)............................................... 55 V.2.2.e Tables dedicated to scrambling code management (only for UMTS) ................................................... 55

V.2.2.e.i ScramblingCodesDomains table........................................................................................................................55 V.2.2.e.ii ScramblingCodesGroups table .........................................................................................................................55 V.2.2.e.iii Separations table .............................................................................................................................................56

V.2.2.f Tables dedicated to PN Offset management (IS95, cdmaOne and CDMA2000) ................................. 56 V.2.2.f.i PnCodesDomains table ......................................................................................................................................56 V.2.2.f.ii PnCodesGroups table........................................................................................................................................56 V.2.2.f.iii Separations table ..............................................................................................................................................56

V.2.2.g Multi-service traffic management.......................................................................................................... 57 V.2.2.g.i UMTSEnvironmentDefs table ............................................................................................................................57 V.2.2.g.ii UMTSMobility table...........................................................................................................................................57 V.2.2.g.iii UMTSServicesQuality table .............................................................................................................................57 V.2.2.g.iv UMTSServicesUsage table ..............................................................................................................................57

Table of contents


V.2.2.g.v UMTSServices table.........................................................................................................................................58 V.2.2.g.vi UMTSTerminals table ......................................................................................................................................58 V.2.2.g.vii UMTSTraficEnvironments table.......................................................................................................................59 V.2.2.g.viii UMTSUserProfiles table.................................................................................................................................59

V.2.3 GSM AND E-GPRS-ORIENTED TABLES ........................................................................................................... 59 V.2.3.a Layers table .......................................................................................................................................... 59 V.2.3.b TRXTypes table.................................................................................................................................... 59 V.2.3.c Resource management ........................................................................................................................ 59

V.2.3.c.i FrequencyDomains table ...................................................................................................................................59 V.2.3.c.ii FrequencyGroups table.....................................................................................................................................59 V.2.3.c.iii BSICDomains table..........................................................................................................................................60 V.2.3.c.iv BSICGroups table ............................................................................................................................................60 V.2.3.c.v HSNDomains table ...........................................................................................................................................60 V.2.3.c.vi HSNGroups table.............................................................................................................................................60

V.2.3.d CellTypes table..................................................................................................................................... 61 V.2.3.e TRGConfigurations table ...................................................................................................................... 61 V.2.3.f TRGs table ........................................................................................................................................... 61 V.2.3.g TRXs table............................................................................................................................................ 63 V.2.3.h Separations table.................................................................................................................................. 63 V.2.3.i TSConfigurationNames table................................................................................................................ 63 V.2.3.j TSConfigurations table ......................................................................................................................... 63 V.2.3.k EGPRSEquipments table ..................................................................................................................... 64 V.2.3.l EGPRSQuality table ............................................................................................................................. 64 V.2.3.m EGPRSDimensioningModel table......................................................................................................... 64 V.2.3.n EGPRSServiceQuality table ................................................................................................................. 64 V.2.3.o Multi-service traffic management.......................................................................................................... 65

V.2.3.o.i EGPRSEnvironmentDefs table ..........................................................................................................................65 V.2.3.o.ii EGPRSMobility table ........................................................................................................................................65 V.2.3.o.iii EGPRSServices table ......................................................................................................................................65 V.2.3.o.iv EGPRSServicesusage table ............................................................................................................................65 V.2.3.o.v EGPRSTerminals table.....................................................................................................................................65 V.2.3.o.vi EGPRSTrafficEnvironments table ....................................................................................................................65 V.2.3.o.vii EGPRSUserProfiles table ...............................................................................................................................66

VI COORDINATE SYSTEMS ....................................................................69 VI.1 BASIC CONCEPTS ....................................................................................................69 VI.2 COORDINATE SYSTEM MANAGEMENT.........................................................................69

VI.2.1 THE PROJECTION SYSTEM............................................................................................................................... 69 VI.2.2 THE DISPLAY SYSTEM..................................................................................................................................... 69 VI.2.3 THE INTERNAL SYSTEM................................................................................................................................... 70

VI.3 COORDINATE SYSTEM DESCRIPTION..........................................................................70 VI.3.1 OVERVIEW .................................................................................................................................................... 70

VI.3.1.a Geographic coordinate system ............................................................................................................. 70 VI.3.1.b Projection.............................................................................................................................................. 70 VI.3.1.c Projected coordinate system ................................................................................................................ 70 VI.3.1.d Ellipsoid ................................................................................................................................................ 70 VI.3.1.e Datum................................................................................................................................................... 70 VI.3.1.f Meridian................................................................................................................................................ 71

VI.3.2 FORMAT OF COORDINATE SYSTEM FILES........................................................................................................... 71 VI.3.2.a Codes of units....................................................................................................................................... 71 VI.3.2.b Codes of datums .................................................................................................................................. 71 VI.3.2.c Codes of projection methods ................................................................................................................ 73 VI.3.2.d Indices of projection parameters........................................................................................................... 73

VII UNITS AND BSIC FORMAT .................................................................77 VII.1 TRANSMISSION POWER UNIT .....................................................................................77

VII.1.1 THE DISPLAY UNIT.......................................................................................................................................... 77 VII.1.2 THE INTERNAL UNIT........................................................................................................................................ 77

VII.2 RECEPTION POWER UNIT ..........................................................................................77 VII.2.1 THE DISPLAY UNIT.......................................................................................................................................... 77 VII.2.2 THE INTERNAL UNIT........................................................................................................................................ 77

VII.3 DISTANCE, HEIGHT AND OFFSET UNITS ......................................................................77

Table of contents


VII.3.1 THE DISPLAY UNIT.......................................................................................................................................... 77 VII.3.2 THE INTERNAL UNIT........................................................................................................................................ 77

VII.4 BSIC FORMAT ........................................................................................................78 VII.4.1 THE DISPLAY FORMAT..................................................................................................................................... 78 VII.4.2 THE INTERNAL FORMAT................................................................................................................................... 78

VIII GEOGRAPHIC DATA ...........................................................................81 VIII.1 DATA TYPE .............................................................................................................81

VIII.1.1 DIGITAL TERRAIN MODEL (DTM)..................................................................................................................... 81 VIII.1.2 CLUTTER (OR LAND-USE)................................................................................................................................ 82

VIII.1.2.a Clutter classes ...................................................................................................................................... 82 VIII.1.2.b Clutter heights ...................................................................................................................................... 82

VIII.1.3 TRAFFIC DATA ............................................................................................................................................... 82 VIII.1.4 VECTOR DATA ............................................................................................................................................... 83 VIII.1.5 SCANNED IMAGES.......................................................................................................................................... 83 VIII.1.6 POPULATION ................................................................................................................................................. 83 VIII.1.7 OTHER GEOGRAPHIC DATA ............................................................................................................................. 83

VIII.2 SUPPORTED GEOGRAPHIC DATA FORMATS ................................................................83

IX RADIO DATA........................................................................................87 IX.1 DATA TYPES............................................................................................................87

IX.1.1 ANY DOCUMENT............................................................................................................................................. 87 IX.1.1.a Site ....................................................................................................................................................... 87 IX.1.1.b Antenna ................................................................................................................................................ 87 IX.1.1.c Transmitter ........................................................................................................................................... 87 IX.1.1.d Repeater............................................................................................................................................... 87 IX.1.1.e Station .................................................................................................................................................. 87 IX.1.1.f Hexagonal design................................................................................................................................. 87

IX.1.2 GSM_EGPRS DOCUMENTS .......................................................................................................................... 87 IX.1.2.a TRX ...................................................................................................................................................... 87 IX.1.2.b Subcell.................................................................................................................................................. 87 IX.1.2.c Cell type................................................................................................................................................ 87

IX.1.3 UMTS, CDMA2000 AND IS95-CDMA DOCUMENTS ....................................................................................... 88 IX.1.3.a Cell ....................................................................................................................................................... 88

X FILE FORMATS....................................................................................91 X.1 BIL FORMAT ............................................................................................................91

X.1.1 HEADER FILE (.HDR)....................................................................................................................................... 91 X.1.1.a Description............................................................................................................................................ 91 X.1.1.b Samples................................................................................................................................................ 92

X.1.1.b.i Digital Terrain Model..........................................................................................................................................92 X.1.1.b.ii Clutter classes file.............................................................................................................................................92

X.1.2 .BIL FILE........................................................................................................................................................ 92 X.2 TIFF FORMAT...........................................................................................................92

X.2.1 HEADER FILE DESCRIPTION (.TFW) ................................................................................................................. 93 X.2.2 SAMPLE........................................................................................................................................................ 93

X.2.2.a Clutter classes file ................................................................................................................................ 93 X.3 PLANET FORMAT .....................................................................................................93

X.3.1 DTM FILE ..................................................................................................................................................... 93 X.3.1.a description ............................................................................................................................................ 93 X.3.1.b Sample ................................................................................................................................................. 94

X.3.2 CLUTTER CLASS FILES.................................................................................................................................... 94 X.3.2.a Description............................................................................................................................................ 94 X.3.2.b Sample ................................................................................................................................................. 94

X.3.3 VECTOR FILES ............................................................................................................................................... 95 X.3.3.a Description............................................................................................................................................ 95 X.3.3.b Sample ................................................................................................................................................. 95

X.3.4 IMAGE FILES .................................................................................................................................................. 95

Table of contents


X.3.5 TEXT DATA FILES ........................................................................................................................................... 95 X.4 MNU FORMAT...........................................................................................................96

X.4.1 DESCRIPTION ................................................................................................................................................ 96 X.4.2 SAMPLE........................................................................................................................................................ 96

X.5 EXTERNALISED PROPAGATION RESULTS FORMAT .......................................................96 X.5.1 DBF FILE ....................................................................................................................................................... 97

X.5.1.a DBF file format...................................................................................................................................... 97 X.5.1.a.i dbf Structure......................................................................................................................................................97 X.5.1.a.ii dbf Header (variable size depending on field count)..........................................................................................97 X.5.1.a.iii Each dbf record (fix length) ..............................................................................................................................98

X.5.1.b dbf file content ...................................................................................................................................... 98 X.5.2 LOS FILE ....................................................................................................................................................... 99

X.6 INTERFERENCE HISTOGRAMS FORMAT .......................................................................99 X.6.1 EXPORT FORMAT ........................................................................................................................................... 99

X.6.1.a dct file ................................................................................................................................................... 99 X.6.1.a.i Description ........................................................................................................................................................99 X.6.1.a.ii Sample ...........................................................................................................................................................100

X.6.1.b clc file.................................................................................................................................................. 100 X.6.1.b.i Description ......................................................................................................................................................100 X.6.1.b.ii Samples .........................................................................................................................................................101

X.6.2 IMPORT FORMAT .......................................................................................................................................... 101 X.6.2.a Samples.............................................................................................................................................. 102

XI CALCULATIONS ................................................................................105 XI.1 OVERVIEW ............................................................................................................105 XI.2 PATH LOSS MATRICES............................................................................................106

XI.2.1 CALCULATION AREA DETERMINATION ............................................................................................................. 107 XI.2.2 CALCULATE – FORCE CALCULATION COMPARISON........................................................................................... 107

XI.2.2.a Calculate............................................................................................................................................. 107 XI.2.2.b Force calculation ................................................................................................................................ 107

XI.2.3 MATRIX VALIDITY ......................................................................................................................................... 108 XI.3 PATH LOSS CALCULATIONS ....................................................................................109

XI.3.1 GROUND ALTITUDE DETERMINATION............................................................................................................... 109 XI.3.2 CLUTTER DETERMINATION ............................................................................................................................ 109

XI.3.2.a Clutter class........................................................................................................................................ 109 XI.3.2.b Clutter height ...................................................................................................................................... 109

XI.3.3 MULTI–LAYER MANAGEMENT......................................................................................................................... 110 XI.3.3.a Example 1: Two DTM maps representing different areas................................................................... 110 XI.3.3.b Example 2: Clutter classes and DTM maps representing the same area ........................................... 111 XI.3.3.c Example 3: Two clutter class maps representing a common area...................................................... 111

XI.3.4 GEOGRAPHIC PROFILE EXTRACTION............................................................................................................... 112 XI.3.4.a Extraction methods............................................................................................................................. 112

XI.3.4.a.i Radial extraction.............................................................................................................................................112 XI.3.4.a.ii Systematic extraction.....................................................................................................................................113

XI.3.4.b Profile resolution: multi-resolution management................................................................................. 113 XI.4 PROPAGATION MODELS..........................................................................................114

XI.4.1 OVERVIEW .................................................................................................................................................. 114 XI.4.2 OKUMURA-HATA AND COST-HATA................................................................................................................. 116

XI.4.2.a Hata formula ....................................................................................................................................... 116 XI.4.2.b Corrections to the Hata formula.......................................................................................................... 116 XI.4.2.c Calculations in Atoll ............................................................................................................................ 116

XI.4.3 STANDARD PROPAGATION MODEL (SPM) ...................................................................................................... 117 XI.4.3.a SPM formula....................................................................................................................................... 117 XI.4.3.b Calculations in Atoll ............................................................................................................................ 117

XI.4.3.b.i Visibility and distance between the transmitter and the receiver......................................................................117 XI.4.3.b.ii Effective transmitter antenna height ...............................................................................................................117

XI.4.3.b.ii.i Height above ground..............................................................................................................................117 XI.4.3.b.ii.ii Height above average profile.................................................................................................................117 XI.4.3.b.ii.iii Slope at receiver between 0 and distance min......................................................................................118 XI.4.3.b.ii.iv Spot Ht .................................................................................................................................................118 XI.4.3.b.ii.v Abs Spot Ht...........................................................................................................................................118 XI.4.3.b.ii.vi Enhanced slope at receiver..................................................................................................................118

XI.4.3.b.iii Receiver effective antenna height .................................................................................................................121 XI.4.3.b.iv Correction for hilly regions in case of LOS ....................................................................................................121 XI.4.3.b.v Diffraction ......................................................................................................................................................121

Table of contents


XI.4.3.b.vi Losses due to clutter.....................................................................................................................................122 XI.4.3.b.vii Recommendations .......................................................................................................................................123

XI.4.4 WLL .......................................................................................................................................................... 123 XI.4.4.a WLL formula ....................................................................................................................................... 123 XI.4.4.b Calculations in Atoll ............................................................................................................................ 123

XI.4.4.b.i Free space loss ..............................................................................................................................................123 XI.4.4.b.ii Diffraction ......................................................................................................................................................124

XI.4.4.b.ii.i Receiver clearance ................................................................................................................................124 XI.4.4.b.ii.ii Receiver height .....................................................................................................................................124 XI.4.4.b.ii.iii Visibility ................................................................................................................................................124

XI.4.5 ITU-R P.526-5 MODEL................................................................................................................................ 124 XI.4.5.a ITU 526-5 formula............................................................................................................................... 124 XI.4.5.b Calculations in Atoll ............................................................................................................................ 124

XI.4.5.b.i Free space loss ..............................................................................................................................................124 XI.4.5.b.ii Diffraction ......................................................................................................................................................124

XI.4.6 ITU-R P.370-7........................................................................................................................................... 124 XI.4.6.a ITU 370-7 formula............................................................................................................................... 124 XI.4.6.b Calculations in Atoll ............................................................................................................................ 125

XI.4.6.b.i Free space loss ..............................................................................................................................................125 XI.4.6.b.ii Corrected standard loss.................................................................................................................................125

XI.4.6.b.ii.i Cn calculation.........................................................................................................................................125 XI.4.6.b.ii.ii AHRxeff calculation...................................................................................................................................125 XI.4.6.b.ii.iii Acl calculation .......................................................................................................................................126

XI.4.7 APPENDICES ............................................................................................................................................... 126 XI.4.7.a Free space loss .................................................................................................................................. 126 XI.4.7.B Diffraction loss.................................................................................................................................... 126

XI.4.7.b.i Knife-edge diffraction......................................................................................................................................126 XI.4.7.b.ii Deygout method ............................................................................................................................................127

XI.4.7.b.ii.i 1 obstacle ..............................................................................................................................................127 XI.4.7.b.ii.ii 3 obstacles............................................................................................................................................127

XI.4.7.b.iii Epstein-Peterson method..............................................................................................................................128 XI.4.7.b.iv Deygout method with correction....................................................................................................................128 XI.4.7.b.v Millington method ..........................................................................................................................................129

XI.5 ANTENNA ATTENUATION CALCULATION ...................................................................129 XI.5.1.a Calculation of azimuth and tilt angles ................................................................................................. 129 XI.5.1.b Antenna pattern 3D interpolation ........................................................................................................ 131

XI.6 SHADOWING MODEL...............................................................................................132 XI.6.1 OVERVIEW .................................................................................................................................................. 132 XI.6.2 MODELLING IN PREDICTIONS ......................................................................................................................... 133

XI.6.2.a Shadowing margin evaluation............................................................................................................. 133 XI.6.2.a.i Shadowing error pdf (one signal) ....................................................................................................................133

XI.6.2.b Uplink macro-diversity gain evaluation ............................................................................................... 134 XI.6.2.b.i Shadowing error pdf (n signals) ......................................................................................................................134

XI.6.2.b.i.i 2 signals without recombination..............................................................................................................135 XI.6.2.b.i.ii n signals without recombination .............................................................................................................136 XI.6.2.b.i.iii Correlation coefficient determination .....................................................................................................136

XI.6.2.b.ii Uplink macro-diversity gain ............................................................................................................................136 XI.6.2.c Downlink macro-diversity gain evaluation........................................................................................... 136

XI.6.2.c.i Shadowing error pdf (n signals) ......................................................................................................................137 XI.6.2.c.i.i 2 available signals ..................................................................................................................................137 XI.6.2.c.i.ii n available signals..................................................................................................................................138 XI.6.2.c.i.iii Correlation coefficient determination .....................................................................................................139

XI.6.2.c.ii Downlink macro-diversity gain........................................................................................................................139 XI.6.3 MODELLING IN SIMULATIONS ......................................................................................................................... 139 XI.6.4 REFERENCES .............................................................................................................................................. 140

XI.7 APPENDICES .........................................................................................................140 XI.7.1 TRANSMITTER RADIO EQUIPMENTS................................................................................................................. 140

XI.7.1.a UMTS, CDMA2000 and IS95-CDMA documents ............................................................................... 141 XI.7.1.b GSM-EGPRS documents ................................................................................................................... 142

XI.7.2 SECONDARY ANTENNAS................................................................................................................................ 142

XII GSM GPRS EGPRS DOCUMENTS....................................................147 XII.1 GENERAL PREDICTION STUDIES ..............................................................................147

XII.1.1 CALCULATION CRITERIA................................................................................................................................ 147 XII.1.2 POINT ANALYSIS .......................................................................................................................................... 147

XII.1.2.a Profile tab ........................................................................................................................................... 147 XII.1.2.b Reception tab ..................................................................................................................................... 147

Table of contents


XII.1.3 COVERAGE STUDIES .................................................................................................................................... 148 XII.1.3.a Service area determination................................................................................................................. 148

XII.1.3.a.i All the servers................................................................................................................................................148 XII.1.3.a.ii Best signal level per HCS layer and a margin ...............................................................................................148 XII.1.3.a.iii Best signal level of the highest priority layer and a margin ...........................................................................148 XII.1.3.a.iv Second best signal level per HCS layer and a margin..................................................................................149

XII.1.3.b Coverage display................................................................................................................................ 149 XII.1.3.b.i Plot resolution................................................................................................................................................149 XII.1.3.b.ii Display types ................................................................................................................................................149

XII.2 TRAFFIC ANALYSIS ................................................................................................150 XII.2.1 TRAFFIC DISTRIBUTION ................................................................................................................................. 150

XII.2.1.a Normal cells (nonconcentric, no HCS layer) ....................................................................................... 150 XII.2.1.a.i Circuit switched services................................................................................................................................150 XII.2.1.a.ii Packet switched services ..............................................................................................................................150

XII.2.1.b Concentric cells .................................................................................................................................. 150 XII.2.1.b.i Circuit switched services................................................................................................................................150 XII.2.1.b.ii Packet switched services ..............................................................................................................................151

XII.2.1.c HCS layers ......................................................................................................................................... 151 XII.2.1.c.i Circuit switched services................................................................................................................................151 XII.2.1.c.ii Packet switched services ..............................................................................................................................151

XII.2.2 CALCULATION OF THE TRAFFIC DEMAND PER SUBCELL ..................................................................................... 151 XII.2.2.a Traffic maps based on environments and user profiles ...................................................................... 151

XII.2.2.a.i Normal cells (nonconcentric, no HCS layer)...................................................................................................151 XII.2.2.a.i.i Circuit switched services........................................................................................................................151 XII.2.2.a.i.ii Packet switched services ......................................................................................................................152

XII.2.2.a.ii Concentric cells ............................................................................................................................................152 XII.2.2.a.ii.i Circuit switched services.......................................................................................................................152 XII.2.2.a.ii.ii Packet switched services .....................................................................................................................153

XII.2.2.a.iii HCS layers...................................................................................................................................................153 XII.2.2.a.iii.i Normal cells .........................................................................................................................................153 XII.2.2.a.iii.ii Concentric cells...................................................................................................................................154

XII.2.2.b Traffic maps based on transmitters and services ............................................................................... 156 XII.2.2.b.i Normal cells (nonconcentric, no HCS layer)...................................................................................................157 XII.2.2.b.ii Concentric cells ............................................................................................................................................157 XII.2.2.b.iii HCS layers...................................................................................................................................................157

XII.2.2.b.iii.i Normal cells .........................................................................................................................................157 XII.2.2.b.iii.ii Concentric cells...................................................................................................................................158

XII.3 NEIGHBOUR ALLOCATION.......................................................................................161 XII.3.1 GLOBAL ALLOCATION FOR ALL TRANSMITTERS................................................................................................. 161 XII.3.2 ALLOCATION FOR A GROUP OF TRANSMITTERS ................................................................................................ 163

XII.4 INTERFERENCE PREDICTION STUDIES.......................................................................163 XII.4.1 COVERAGE STUDIES .................................................................................................................................... 163

XII.4.1.a Service area determination................................................................................................................. 164 XII.4.1.a.i All the servers................................................................................................................................................164 XII.4.1.a.ii Best signal level per HCS layer and a margin ...............................................................................................164 XII.4.1.a.iii Best signal level of the highest priority HCS layer and a margin ...................................................................164 XII.4.1.a.iv Second best signal level per HCS layer and a margin..................................................................................164

XII.4.1.b Carrier to interference ratio calculation............................................................................................... 164 XII.4.1.b.i Carrier power level.........................................................................................................................................165 XII.4.1.b.ii Interference calculation.................................................................................................................................165 XII.4.1.b.iii Collision probability for non hopping mode ...................................................................................................166 XII.4.1.b.iv Collision probability in case of BBH or SFH..................................................................................................166

XII.4.1.c Coverage area determination ............................................................................................................. 167 XII.4.1.d Coverage area display........................................................................................................................ 167

XII.4.2 POINT ANALYSIS .......................................................................................................................................... 167 XII.5 GPRS EGPRS COVERAGE STUDIES ......................................................................168

XII.5.1 COVERAGE AREA DETERMINATION ................................................................................................................. 168 XII.5.1.a All the servers..................................................................................................................................... 168 XII.5.1.b Best signal level per HCS layer and a margin .................................................................................... 168 XII.5.1.c Second best signal level per HCS layer and a margin........................................................................ 168 XII.5.1.d Best signal level of the highest priority layer and a margin................................................................. 168

XII.5.2 CALCULATION OPTIONS ................................................................................................................................ 169 XII.5.2.a Calculations based on C..................................................................................................................... 169 XII.5.2.b Calculations based on C and C/I ........................................................................................................ 169

XII.5.3 COVERAGE DISPLAY..................................................................................................................................... 169 XII.5.3.a Coding schemes................................................................................................................................. 169

XII.5.3.a.i Calculations based on C................................................................................................................................169 XII.5.3.a.ii Calculations based on C and C/I ...................................................................................................................169

XII.5.3.b Best coding schemes.......................................................................................................................... 170 XII.5.3.b.i Calculations based on C................................................................................................................................170

Table of contents


XII.5.3.b.ii Calculations based on C and C/I ...................................................................................................................170 XII.5.3.c Rate/timeslot....................................................................................................................................... 170

XII.5.3.c.i Calculations based on C ................................................................................................................................170 XII.5.3.c.ii Calculations based on C and C/I ...................................................................................................................170

XII.5.3.d Best rate/timeslot................................................................................................................................ 171 XII.5.3.d.i Calculations based on C................................................................................................................................171 XII.5.3.d.ii Calculations based on C and C/I ...................................................................................................................171

XIII AFP .....................................................................................................175 XIII.1 OVERVIEW ............................................................................................................175 XIII.2 DESCRIPTION OF THE COST FUNCTION .....................................................................175

XIII.2.1 NOTATIONS................................................................................................................................................. 176 XIII.2.2 COST FUNCTION .......................................................................................................................................... 176 XIII.2.3 COST COMPONENTS..................................................................................................................................... 177

XIII.2.3.a Separation violation cost component.................................................................................................. 177 XIII.2.3.b Interference cost component .............................................................................................................. 178

XIII.3 BSIC ALLOCATION ................................................................................................180

XIV UMTS DOCUMENTS ..........................................................................183 XIV.1 GENERAL PREDICTION STUDIES ..............................................................................183

XIV.1.1 CALCULATION CRITERIA................................................................................................................................ 183 XIV.1.2 POINT ANALYSIS .......................................................................................................................................... 183

XIV.1.2.a Profile tab ........................................................................................................................................... 183 XIV.1.2.b Reception tab ..................................................................................................................................... 183

XIV.1.3 COVERAGE STUDIES .................................................................................................................................... 184 XIV.1.3.a Service area determination................................................................................................................. 184

XIV.1.3.a.i All the servers ..............................................................................................................................................184 XIV.1.3.a.ii Best signal level and a margin .....................................................................................................................184 XIV.1.3.a.iii Second best signal level and a margin .........................................................................................................184

XIV.1.3.b Coverage display................................................................................................................................ 184 XIV.1.3.b.i Plot resolution ..............................................................................................................................................184 XIV.1.3.b.ii Display types...............................................................................................................................................185

XIV.2 DEFINITIONS AND FORMULAS..................................................................................186 XIV.3 ACTIVE SET MANAGEMENT .....................................................................................189 XIV.4 TRAFFIC DATA.......................................................................................................189

XIV.4.1 USER DENSITY ............................................................................................................................................ 189 XIV.5 SIMULATIONS ........................................................................................................190

XIV.5.1 RANDOM TRIAL STRATEGIES.......................................................................................................................... 190 XIV.5.1.a Simulations based on raster traffic and vector traffic maps ................................................................ 190 XIV.5.1.b Simulations based on traffic map per service and per transmitter ...................................................... 192

XIV.5.2 POWER CONTROL SIMULATION ...................................................................................................................... 193 XIV.5.2.a Algorithm initialization......................................................................................................................... 193 XIV.5.2.b Presentation of the algorithm.............................................................................................................. 194

XIV.5.2.b.i Determination of Mi’s Best server (SBS(Mi))...................................................................................................194 XIV.5.2.b.ii Determination of the active set ....................................................................................................................194 XIV.5.2.b.iii Uplink power control ....................................................................................................................................195 XIV.5.2.b.iv Downlink power control ................................................................................................................................195 XIV.5.2.b.v Uplink and downlink interference update......................................................................................................196 XIV.5.2.b.vi Control of radio resource limits (OVSF codes, cell power, channel elements) ..............................................196 XIV.5.2.b.vii Uplink load factor control..............................................................................................................................197

XIV.5.2.c Convergence criteria........................................................................................................................... 197 XIV.5.3 APPENDICES ............................................................................................................................................... 197

XIV.5.3.a Admission control ............................................................................................................................... 197 XIV.5.3.b OVSF code management ................................................................................................................... 198 XIV.5.3.c Downlink load factor calculation ......................................................................................................... 199

XIV.6 UMTS W-CDMA PREDICTION STUDIES..................................................................200 XIV.6.1 POINT ANALYSIS .......................................................................................................................................... 200

XIV.6.1.a AS analysis tab................................................................................................................................... 200 XIV.6.1.a.i Bar graph and pilot sub-menu ......................................................................................................................200 XIV.6.1.a.ii Downlink sub-menu.....................................................................................................................................202 XIV.6.1.a.iii Uplink sub-menu..........................................................................................................................................203

Table of contents


XIV.6.2 COVERAGE STUDIES .................................................................................................................................... 204 XIV.6.2.a Pilot reception analysis ....................................................................................................................... 204

XIV.6.2.a.i 1st case: analysis based on all the carriers ...................................................................................................204 XIV.6.2.a.ii 2nd case: analysis based on a specific carrier ..............................................................................................205

XIV.6.2.b Downlink service area analysis........................................................................................................... 205 XIV.6.2.c Uplink service area analysis ............................................................................................................... 207 XIV.6.2.d Downlink total noise analysis.............................................................................................................. 209

XIV.6.2.d.i Analysis on all the carriers............................................................................................................................209 XIV.6.2.d.ii Analysis on a given carrier...........................................................................................................................210

XIV.7 AUTOMATIC NEIGHBOUR ALLOCATION .....................................................................210 XIV.7.1 GLOBAL ALLOCATION FOR ALL CELLS.............................................................................................................. 210 XIV.7.2 ALLOCATION FOR A GROUP OF CELLS ............................................................................................................. 212

XIV.8 PRIMARY SCRAMBLING CODE ALLOCATION ..............................................................212 XIV.8.1 AUTOMATIC ALLOCATION DESCRIPTION........................................................................................................... 212 XIV.8.2 ALLOCATION EXAMPLES................................................................................................................................ 213

XIV.9 AUTOMATIC GSM-UMTS NEIGHBOUR ALLOCATION.................................................214 XIV.9.1 OVERVIEW .................................................................................................................................................. 214 XIV.9.2 AUTOMATIC ALLOCATION DESCRIPTION........................................................................................................... 214

XIV.9.2.a Algorithm based on distance .............................................................................................................. 214 XIV.9.2.b Algorithm based on coverage overlapping.......................................................................................... 215 XIV.9.2.c The Reset option ................................................................................................................................ 216

XIV.9.3 CALCULATION OF THE INTER-TRANSMITTER DISTANCE...................................................................................... 216

XV CDMA2000 AND IS95-CDMA DOCUMENTS .....................................221 XV.1 GENERAL PREDICTION STUDIES ..............................................................................221

XV.1.1 CALCULATION CRITERIA................................................................................................................................ 221 XV.1.2 POINT ANALYSIS .......................................................................................................................................... 221

XV.1.2.a Profile tab ........................................................................................................................................... 221 XV.1.2.b Reception tab ..................................................................................................................................... 221

XV.1.3 COVERAGE STUDIES .................................................................................................................................... 222 XV.1.3.a Service area determination................................................................................................................. 222

XV.1.3.a.i All the servers ...............................................................................................................................................222 XV.1.3.a.ii Best signal level and a margin ......................................................................................................................222 XV.1.3.a.iii Second best signal level and a margin.........................................................................................................222

XV.1.3.b Coverage display................................................................................................................................ 222 XV.1.3.b.i Plot resolution ...............................................................................................................................................222 XV.1.3.b.ii Display types................................................................................................................................................223

XV.2 DEFINITIONS AND FORMULAS..................................................................................224 XV.3 ACTIVE SET MANAGEMENT .....................................................................................228 XV.4 TRAFFIC DATA.......................................................................................................229

XV.4.1 USER DENSITY ............................................................................................................................................ 229 XV.5 SIMULATIONS ........................................................................................................229

XV.5.1 RANDOM TRIAL STRATEGIES.......................................................................................................................... 229 XV.5.1.a Simulations based on raster traffic and vector traffic maps ................................................................ 230 XV.5.1.b Simulations based on traffic map per service and per transmitter ...................................................... 230

XV.5.2 POWER CONTROL SIMULATION ...................................................................................................................... 232 XV.5.2.a Algorithm initialization......................................................................................................................... 233 XV.5.2.b Presentation of the algorithm.............................................................................................................. 233

XV.5.2.b.i Determination of Mi’s Best server (SBS(Mi))....................................................................................................233 XV.5.2.b.ii Determination of the active set .....................................................................................................................233 XV.5.2.b.iii Uplink power control ....................................................................................................................................234 XV.5.2.b.iv Downlink power control................................................................................................................................235 XV.5.2.b.v Uplink and downlink interference updates ....................................................................................................237 XV.5.2.b.vi Control of radio resource limits (Walsh codes, cell power and site channel elements) .................................237 XV.5.2.b.vii Uplink load factor control..............................................................................................................................237

XV.5.2.c Convergence criterion......................................................................................................................... 238 XV.5.3 APPENDICES ............................................................................................................................................... 238

XV.5.3.a Admission control ............................................................................................................................... 238 XV.5.3.b Walsh code management ................................................................................................................... 238 XV.5.3.c Downlink load factor calculation ......................................................................................................... 239

XV.6 AUTOMATIC NEIGHBOUR ALLOCATION .....................................................................240 XV.6.1 GLOBAL ALLOCATION FOR ALL CELLS.............................................................................................................. 241 XV.6.2 ALLOCATION FOR A GROUP OF CELLS ............................................................................................................. 242

Table of contents


XV.7 PN OFFSET ALLOCATION........................................................................................242 XV.8 AUTOMATIC GSM/TDMA-CDMA NEIGHBOUR ALLOCATION.....................................244

XV.8.1 OVERVIEW .................................................................................................................................................. 244 XV.8.2 AUTOMATIC ALLOCATION DESCRIPTION........................................................................................................... 244

XV.8.2.a Algorithm based on distance .............................................................................................................. 244 XV.8.2.b Algorithm based on coverage overlapping.......................................................................................... 245 XV.8.2.c The Reset option ................................................................................................................................ 246

XV.9 AUTOMATIC CDMA-CDMA2000 NEIGHBOUR ALLOCATION......................................246 XV.9.1 OVERVIEW .................................................................................................................................................. 246 XV.9.2 AUTOMATIC ALLOCATION DESCRIPTION........................................................................................................... 247

XV.9.2.a The Reset option ................................................................................................................................ 247

XVI REPEATERS ......................................................................................251 XVI.1 OVERVIEW ............................................................................................................251 XVI.2 AUTOMATIC CALCULATION .....................................................................................251

XVI.2.1 GLOBAL AMPLIFICATION GAIN ........................................................................................................................ 251 XVI.2.2 EIRP ......................................................................................................................................................... 252

XVI.3 STANDARD PREDICTION STUDIES ............................................................................252 XVI.3.1 POINT ANALYSIS .......................................................................................................................................... 252

XVI.3.1.a Profile tab ........................................................................................................................................... 252 XVI.3.1.b Reception and results tabs ................................................................................................................. 252

XVI.3.2 COVERAGE STUDIES .................................................................................................................................... 252 XVI.4 UMTS SPECIFIC PREDICTION STUDIES.....................................................................253

C H A P T E R 1

Installation This chapter describes requirements and main steps to install Atoll and the floating license manager.

1

Technical Reference Guide


Installation


I INSTALLATION Atoll can be installed in two different ways:

1. Atoll is installed on all the workstations with one hardware key (called Superpro) per workstation. 2. Atoll is installed on all the workstations and a server PC, equipped with a floating license system and a

specific hardware key (called NetHASP), manages the number of possible Atoll users. This system provides more flexibility.

Atoll and floating license manager installation procedures and requirements are detailed below.

I.1 ATOLL INSTALLATION This part describes the requirements to install Atoll on workstations and its installation procedure.

I.1.1 WORKSTATION REQUIREMENTS Atoll runs on workstation PCs with Windows NT4, 2000 or XP. The recommended configuration for the workstation is as follows:

• CPU: Pentium III (minimum) • Memory: 64 MB (minimum), 128 MB (recommended) • Disk space: 2 GB free harddisk space (or more according to the used geographic database) • Operating system: Windows NT 4.0. SP5, Windows 2000 SP4 or Windows XP SP1. • Graphics card: 1280*1024 with 64000 colours • Additional software: Microsoft Office • Parallel port (25 pins) or USB port (Windows 2000/XP) is required to plug in the Superpro hardware key.

Note: CPU usage is optimised when running Atoll using an application server with Citrix metaframe. Nevertheless, the

RAM required per user remains the same. So, in case of an application server dedicated to n users, each user will require 128 MB of RAM meaning a total of 128×n MB.

I.1.2 INSTALLATION PROCEDURE To install Atoll,

• Quit all programs. • Insert the CD ROM in the workstation CD drive. • Follow the instructions on screen.

Note: Administrator rights are required for the first installation. The default installation directory for Atoll is C:\Program Files\Forsk\Atoll. You can define another directory path during the installation.

Destination directory selection



Options can be modified during the installation to install: - Help files, - Atoll development kit, - User manual (in pdf format), - The distributed computation tool*.

Notes: 1. Some other components may also have been installed during Atoll installation. These include the executable files

com32upd and dcom95 (both designed for Windows 95 - not recommended) and some Microsoft Data Access Components (MDAC enables working with databases).

2. The installation CD contains Microsoft Data Access Components MDAC version 2.7 that can be installed if needed.

3. You may find several versions of Adobe Acrobat® Reader (German, English, French, Italian and Spanish) and the User Manual pdf file on the installation CD as well.

I.1.3 TROUBLESHOOTING First of all, make sure you have installed Atoll using an administrator account, restarted your computer and logged in again with an account with administrator priviliges in order to complete the installation of the libraries that were in use during the first installation step (including MDAC and the sentinel driver). Verify that the folder in which you have installed Atoll is valid. By default Atoll is intalled in an Atoll folder, be sure not to have modified it like this example: C:\Program Files\Forsk\XYZ\Atoll\..., where XYZ is the name of the main folder in which you wanted to install Atoll. If the MDAC version of your PC is too old, you may install a newer version available on the Atoll installation CD. The recommended MDAC version is 2.7. Note: MDAC is provided with the Atoll installation program on the CD. In case the message "Protection key error" appears, please verify that the hardware key is correctly plugged in and is valid. If you use a Superpro hardware key, first try restarting your computer after the installation on an administrator account. Then install the sentinel driver again using the setupx86.exe file in the setup folder in your current Atoll folder. Precautions: 1. It is recommended to switch off your computer before unplugging or plugging the hardware key. 2. Do not change the PC date. 3. With a temporary Superpro hardware key: - Do not reprogram it even if you plug it into another computer. - Do not put off the time bomb without help from Forsk Support Team.

I.2 FLOATING LICENSE INSTALLATION To work in a networked environment with a floating license, a floating license manager is installed on a server.

I.2.1 REQUIREMENTS

I.2.1.a LICENSE SERVER REQUIREMENTS • Operating system: Windows NT4 or Windows 2000. • A parallel or a USB port (only with Windows 2000) must be available to plug-in the floating hardware key.

* To install the distributed computing server, check the distributed computing server option in the Select components box during the setup. The application is installed as a service on the local machine and it will run as long as the workstation is ON (even if no user is logged in). Service management, like the distributed computing server application, is accessed from the Administrative tools icon in the Control Panel. Check that the service “Atoll server” is started before using it. Notes: 1. You must have administrator rights when installing Atoll. 2. In order to be able to use centralised geographic data for computations, check that the account on which the

service is installed has enough rights (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-in window for Windows 2000).

Installation


I.2.1.b FIREWALL NETWORK REQUIREMENTS • If the license server is behind a firewall, port 475 must be open when using UDP or TCP protocol.

I.2.2 INSTALLATION PROCEDURE

I.2.2.a OVERVIEW The floating license management system called NetHASP is manufactured by Aladdin. This system includes:

A NetHASP key. Depending on the number of potential users, keys may be programmed with a variable number of tokens. One workstation consumes one token even if more than one Atoll sessions are running.

The NetHASP license manager. This application communicates with Atoll and NetHASP. The HASP device driver. It is an interface between the NetHASP license manager and the NetHASP key. The NetHASP monitor. It enables you to check the number of consumed tokens. The nethasp.ini and nhsrv.ini files. The first of these two configuration files may be installed on each client to

facilitate access to the license server and the second one on the server in order to authorise workstations to consume tokens. The client and the NetHASP license manager reads and uses the information in these files if found. Default values are used otherwise.

I.2.2.b INSTALLATION ON THE SERVER On the server, you have to install the NetHASP license manager, the HASP device driver and the NetHASP key. You may optionally copy the nhsrv.ini file and later modify this file to tune the settings for the NetHASP license manager.

1. Insert the CD ROM in the server CD drive. 2. Search for the file named LMsetup.exe and execute it. 3. When asking “Please select a type of setup”, choose Service. The license server will run even if no user is

logged on to the server. 4. Specify a destination directory. By default “C:\Program Files\Aladdin\NETHASP LM” is proposed. 5. Accept the following dialogs until NetHASP License manager is installed. 6. Accept automatic driver installation. The driver enables the license manager to communicate with the hardware

key. 7. In the end, as proposed by the installation program, start the license manager. The license manager is started

in Service mode. A small icon is available in the task bar at the bottom right of the screen. You can access the network communication protocols by double-clicking this icon. Load and Remove commands in the menu bar enable you to modify protocols. To close the window without stopping the license manager, select Exit in the menu bar.

8. Plug the NetHASP dongle in the server’s parallel or USB port. 9. Search for file named nhsrv.ini on the CD and copy it in the directory where the NetHASP license manager is

located. Then, customise the file as needed. Notes: 1. The NetHASP key must always be plugged in the PC where the NetHASP license manager is installed. 2. NetHASP key is supported by Windows 2000 Server only using Licence manager 8.09.

I.2.2.c INSTALLATION ON THE SERVER OR CLIENTS You can install the NetHASP monitor to check the number of tokens consumed. It can be installed on the server or on one or several workstations.

1. Insert the CD ROM in the server’s (or client’s) CD drive. 2. According to the computer’s operating system (Windows NT 4.0 or Windows 2000), either open the monitorNT

folder and execute the setup.exe program file (MasterHasp\monitorNT\setup\cd) or open the monitor2000 folder and start the askmon32.exe program file (MasterHasp\monitor2000\install).

3. Specify a destination directory. “C:\Program Files\Aladdin\monitor” is proposed by default. 4. Accept the following dialogs until the NetHASP monitor is installed.

I.2.2.d INSTALLATION ON CLIENTS It is recommended to copy the nethasp.ini file on each client PC. In the file, you can configure how the workstation searches for the license manager.



1. Insert the CD Rom in the client’s CD drive. 2. Search for nethasp.ini file and copy it in the directory where the atoll.exe program file is installed. 3. Customise the file as needed.

Precautions: 1. It is recommended to specify the server name in the domain (NetBios name) in the nethasp.ini configuration file. Example: If the global server name is Server1.company.com, enter Server1 (Do not type Server1.company.com). 2. Only one server name is supported in the nethasp.ini configuration file. 3. It is recommended to switch off your computer before unplugging or plugging the hardware key. 4. Do not change the PC’s date. Notes: 1. In case a workstation is connected to a server with a license manager and a NetHASP hardware key, and is

also equipped with a Superpro hardware key at the same time, the Superpro hardware key has priority over the NetHASP hardware key.

2. In case a Superpro hardware key is plugged into a PC where the license manager is installed (here, the server), the Superpro hardware key is ignored.

C H A P T E R 2

Multi-user environments This chapter describes how to manage databases.

2

Multi-user environments


II MULTI-USER ENVIRONMENTS In a multi-user configuration, all the users are connected to a database. Location where the database must be installed differs with the database type.

Database Server Workstations (client PC’s) Access No Yes*

SQL server Yes No Oracle Yes Yes (“Oracle client”) Sybase Yes Yes

Locations (server or workstation) where database must be installed *It is possible to connect Atoll to an Access database even if Access is not installed on workstations.

II.1 ORACLE DATABASE Oracle version 8.1.7 and above are supported by Atoll. A Server is a machine where the database will be stored and where you will perform all administration operations. We assume that:

1. Oracle is installed on the server and clients. 2. An empty database where data will be stored has been created. Its name is AtollDB and a specific SID is AtollDB. 3. An entry in the tnsnames.ora file (definition of the service name AtollDB) enabling communication with the Atoll database has been added. 4. A tablespace called Atoll has been created.

Note: The service name, AtollDB, must be specified,

- When exporting an Atoll project in an Oracle database (Server = Service name), - When opening an Atoll project from an AtollDB project (Server = Service name), - When using Oracle tools to manage the AtollDB database (Host name = Service name).

II.1.1 CREATING THE PROJECT ACCOUNT You must be connected to the server and must use the DBA studio tool (available in the Database administration menu). DBA studio may be started from the server or any client on which administration tools have been installed.

1. Start DBA Studio. 2. In the File menu, select Add Database to Tree to view the different databases you can access. 3. In the Add Databases to tree window, select the ‘Add selected databases from your local tnsnames.ora file’

option and choose the AtollDB service name. Close the window. 4. In the explorer, double-click on AtollDB, enter “system” as username and “manager” as password. Press OK. 5. To create a new user, open the Security subfolder, right click on User and select Create in the context menu. 6. Define an account with all the administrator rights. This account will be used to store Atoll project tables; it will

be the table owner. Give it a name related to the type of project that you want to store (for instance, GSM in case of GSM project or UMTS in case of UMTS WCDMA project). Specify Atoll as default tablespace and choose DBA for its privileges.

II.1.2 CREATING TABLES Atoll creates the tables automatically.

1. Start Atoll. 2. Create a new project (GSM, for example), define the unit systems, the projection and display coordinate

systems to use. 3. Choose the Database: Export command in the File menu. 4. Select Oracle database as the type of database you use. 5. Enter the user name and the password of the owner of the tables (user name and password defined when

creating the project account) and the service name defined in the tnsnames.ora file (AtollDB).



II.1.3 CREATING OTHER USERS You must be connected to the server and must use the DBA studio tool (available in the Database administration menu). DBA studio may be started from the server or any client on which administration tools have been installed.

2. Start DBA Studio. 3. In the File menu, select Add Database to Tree to view the different databases you can access. In the Add

Databases to tree window, select the ‘Add selected databases from your local tnsnames.ora file’ option and choose the AtollDB service name. Close the window.

4. In the explorer, double-click on AtollDB. You must be connected as the owner of the tables to grant privileges. 5. To create new users, open the Security subfolder, right click on User and select Create in the context menu. 6. Define user accounts with specific rights. For example, you may create an account for an Atoll project

administrator with all the rights on the tables and other user accounts having restricted rights on the tables of the project. These accounts do not contain any table; they contain the rights of using the tables included in the project account. For each user account, enter a name and a password, specify Atoll as default tablespace and customise its privileges.

Hence, any user can connect to the project account by providing his user name and password. At this point, your installation is sufficient to use Oracle from any client PC using one of the declared user accounts and the service created on this machine.

II.1.4 ADVANCED CUSTOMISATION You may use the SQL in order to share the site table (example 1) or to limit the connection to a set of transmitters for some users (example 2). Two examples are detailed hereafter. Use SQL plus 8 as program and log on as the owner of the tables.

II.1.4.a EXAMPLE 1: MANAGING SITE SHARING Let us assume that:

- Connection string = AtollDB - GSM Project account = AtollADMINGSM, password = ADMINGSM - UMTS Project account = AtollADMINUMTS, password = ADMINUMTS - Common Project account = AtollADMIN, password = ADMIN

1. Create the AtollADMIN.SITES table and copy all sites from AtollADMINGSM.SITES to AtollADMIN.SITES

SQL > connect AtollADMIN/ADMIN@AtollDB; SQL > create table AtollADMIN.SITES as select * from AtollADMINGSM.SITES; SQL > create unique index AtollADMIN_SITES on AtollADMIN.SITES(NAME);

2. Replace the AtollADMINGSM.SITES table by an AtollADMINGSM.SITES view

SQL > connect AtollADMINGSM/ADMINGSM@AtollDB; SQL > drop table AtollADMINGSM.SITES; SQL > connect AtollADMIN/ADMIN@AtollDB; SQL > grant delete on AtollADMIN.SITES to AtollADMINGSM with grant option; SQL > grant insert on AtollADMIN.SITES to AtollADMINGSM with grant option; SQL > grant select on AtollADMIN.SITES to AtollADMINGSM with grant option; SQL > grant update on AtollADMIN.SITES to AtollADMINGSM with grant option; SQL > create view AtollADMINGSM.SITES as select * from AtollADMIN.SITES;

3. Follow the same procedure for UMTS (atolladmin.sites already created)

SQL > connect AtollADMINUMTS/ADMINUMTS@AtollDB; SQL > drop table AtollADMINUMTS.SITES; SQL > connect AtollADMIN/ADMIN@AtollDB; SQL > grant delete on AtollADMIN.SITES to AtollADMINUMTS with grant option; SQL > grant insert on AtollADMIN.SITES to AtollADMINUMTS with grant option; SQL > grant select on AtollADMIN.SITES to AtollADMINUMTS with grant option; SQL > grant update on AtollADMIN.SITES to AtollADMINUMTS with grant option; SQL > create view AtollADMINUMTS.SITES as select * from AtollADMIN.SITES;

4. Commit this transaction

SQL > commit;

Multi-user environments


II.1.4.b EXAMPLE 2: MANAGING USERS BY POSTCODE 1. Add a field ‘POSTCODE’ to the SITES table:

SQL > alter table SITES add (POSTCODE number);

2. Rename the SITES table to be able to hide it by a view:

SQL > rename SITES to PRIVATE_SITES;

3. Create a POSTCODETABLE table to link users and postcodes (one user may be linked to several postcodes):

SQL > create table POSTCODETABLE (USERNAME varchar2(30), POSTCODE number);

You can fill this table using this instruction: SQL > insert into POSTCODETABLE values (‘USER1’, 75);

5. Create a view owned by this user hiding the actual table SITES through these commands:

SQL > create view SITES as select * from PRIVATE_SITES where POSTCODE in (select POSTCODE from POSTCODETABLE where USERNAME =USER) with check option;

Note: "With check option" is very important because it specifies that insert and update operations performed through the view must result in rows that the view query can select.

6. Hide the TRANSMITTERS table

SQL > rename TRANSMITTERS to PRIVATE_TRANSMITTERS; SQL> create view TRANSMITTERS as

select * from PRIVATE_TRANSMITTERS where SITE_NAME in (select NAME from SITES);

Note: It is also important to hide the TRANSMITTERS table because Atoll must not select transmitters whose associated sites are not present in the SITES view.

7. Do not forget to commit this transaction

SQL > commit;

CAUTION: The error message triggered if you try to archive a record which does not match the project is not very explicit: “ORA-01402: view WITH CHECK OPTION - clause violation”

C H A P T E R 3

Memory Requirements This chapter gives some aspects of memory requirements for Atoll processes.

3

Memory Requirements


III MEMORY REQUIREMENTS

III.1 INTRODUCTION This document gives some aspects of memory requirement (both RAM and hard disk space) for Atoll depending on the network to be planned. Please note that the figures are approximative and correspond to the version 2.2.1. Due to simplifications in the formulas (not all input parameters are listed), the actual values may vary. Also note that Atoll is able to perform computations in pixel sizes that are different from those of the raster maps. So it is possible to do detailed planning with smaller pixels and nation-wide coverage plot calculations with larger pixels. This will decrease disk space requirements, RAM allocation and calculation time.

III.2 DISK SPACE REQUIREMENTS The amount of disk space required for data obviously depends on the project, mostly on planning area, pixel size and number of cells. In networks with just a few cells, the planning area controls the required amount of disk space. In networks with a large number of sites, the number of transmitters is more important. Pixel size stays a main factor in any case.

III.2.1 NETWORK-WIDE INPUT The file size for raster maps (DTM, clutter heights, clutter classes, traffic density/environments, images) does not depend on the number of cells, only on the size of the planning area in pixels. Please note the following: • Clutter class maps take 1 (or 2 for Planet format) bytes per pixel • Background images take from 1 to 3 bytes per pixels • Traffic maps take 1 (or 2 for Planet format) bytes per pixel • DTM or clutter height maps take 2 bytes per pixel • Population maps or other generic maps can take from 1 to 4 bytes per pixel For one clutter map, one DTM map, one traffic map and one background image, you may estimate 6 bytes per pixel of input area. This data can be shared between different planning alternatives of the same network. Note: If a geo data file initially embedded into the project is deleted, Atoll compress the ATL project automatically and

avoid file fragmentation.

III.2.2 CELL-SPECIFIC RESULTS The more cells there are in the network, the more important it is to consider the disk space required by the cell-specific propagation predictions. Cell area and pixel size are important here as well. Cell-specific results take 2 bytes per pixel. If you consider a calculation area for a transmitter of 1000 x 1000 pixels, you obtain a file size of 2 MB per sector. This value has to be considered for each planning alternative separately, so a new ATL file will require the same disk space again. Notes: 1. The rule is the same when considering an extended matrix (linked with extended resolution and calculation

radius), since 2 bytes per pixel are also stored. 2. If matrices, which were initially embedded into the project, are externalised, Atoll compresses the ATL project

automatically to avoid file fragmentation.

III.2.3 NETWORK-WIDE OUTPUT Similar to network-wide input, the network-wide output (raster results) mainly depends on the size of the planning area and pixel. The size of the result also depends on number of layers (one layer for the network or one layer per involved transmitter/attribute), and the number of colours and thresholds. So Atoll predictions take between 1 bit and 2 bytes per pixel of the calculation area. Atoll provides a feature that compresses resulting studies when saving the ATL projects to avoid file fragmentation. Note: As a result, the required disk space depends on the number and type of the defined predictions. As a rough estimation you can have 14 bytes per pixel. This space is required for each ATL file individually.



III.2.4 TEMPORARY DISK SPACE Atoll will need some disk space to store intermediate results during calculations. A file will be created in the temporary directory of Windows whose size depends on the calculation and will be detailed in the later section on RAM requirements. Likewise, a temporary file is created when using the "Save As..." function. The file will be erased after the calculation or the storage has been terminated. This disk space is required only once per installation.

III.2.5 OTHERS Other objects that require disk space can safely be neglected in realistic scenarios as the required disk space depending on planning area and number of transmitters is far bigger. The ATL file stores the database tables as well as numerical results. An empty ATL file will have less than 100 KB. Each additional site will need between 1 and 2 KB more space in the ATL file (negligible compared to the size of the propagation results). Furthermore, vector files as part of the geo data can be neglected, as their file size usually is much smaller than the height and clutter maps. Note: During a classical ‘save’ of an ATL project, Atoll estimates the size of unused spaces in the file due to

fragmentation. If the amount of unused space is more than 50% than the useful space, Atoll offers the user to compress the file.

III.3 RAM REQUIREMENTS

III.3.1 GENERAL Usually, a PC with 256 MB RAM is sufficient for all operations with Atoll, provided, of course, that no memory-hungry applications are used in parallel. Starting Atoll without loading a project will require around 13 MB RAM (monitored with the Task Manager of Windows). Loading a Paris project with 500 sites, some predictions and some simulations will increase the memory required to 83 MB.

III.3.2 UMTS SIMULATIONS The calculations that require the most memory are the UMTS simulations. The memory requirement of this calculation is a function of the following: • Number of sites involved • Number of transmitters involved • Number of cells involved • Number of mobiles generated by the UMTS simulation (Monte Carlo approach) • Number of transmitters covering a pixel • Number of services simulated • Number of neighbours per cell • "Detailed Results" and "Limit Active Set to Neighbours" flags • Number of links per mobile • Number of channel elements per site Most of these parameters have minor influences and the actual requirements are mostly governed by the number of cells and number of mobiles. Assuming that there are three carriers used and the number of transmitters and mobiles is sufficiently high, so that the other inputs can be neglected, the required memory can be approximated conservatively by mtR ×+×= 25.30.14 for normal simulations mtR ×+×= 3.40.14 for option "detailed results" with R: peak RAM requirement in KBytes t: number of transmitters affecting the computation zone m: number of mobiles generated by UMTS simulation Example: For a calculation of 500 sites (or 1500 transmitters) and 2400 mobiles, this will result in a RAM requirement of around 28 MB for a normal simulation and 30 MB if detailed results are to be stored as well.

Memory Requirements


Notes: 1. Please note that this is the peak requirement. Once the calculations are terminated, lesser memory will be

required. 2. This approximation also considers effects based in the operating system, like memory over-allocation due to

fragmentation. It is a conservative approximation and in most cases the actual RAM requirement will be below these calculated figures.

III.3.3 PREDICTIONS During the calculation of a prediction (networkwide raster result), RAM required is the same as the additionally required disk space, i.e. between 1 bit and 2 bytes per pixel of the calculation zone. Apart from this, temporary memory is required for calculations like "Coverage by transmitter" and "Coverage by signal level". Here, Atoll temporarily allocates an average of 4 more bytes per pixel (8 bytes if the best server margin is not zero) of the calculation area. Example: The Paris region has a size of around 10 x 13 km and a pixel resolution of 5m. This equals around 5 MPixels. For a prediction that calculates the signal strength of the UMTS pilot in less than 16 colours, we need a permanent memory of 4 bits per pixel, so a total of around 2.5 Mbytes. During the calculation, we need 4 more bytes per pixel, so around 20 Mbytes more apart from the 2.5 Mbytes. Note: For large networks, in order not to load the entire computation zone in memory, Atoll splits the prediction

computations in bands and works on them successively. This decomposition is not visible to the user.

C H A P T E R 4

Atoll administration files This chapter describes the different files used for Atoll administration.

4

Atoll administration files


IV ATOLL ADMINISTRATION FILES Three files can be used for Atoll administration:

- The user configuration file (.cfg) may contain paths and description of geographic data, computation zone definition, filter/sort/group criteria applied to folders, display settings of objects, prediction study list, path to access macros and AFP settings.

- The atoll.ini file can contain site and transmitter naming conventions, calculation settings (modelling method of antenna patterns) and many other options (list of calculation servers,…).

- The studies.xml file can describe prediction studies with customised settings. Several users can share a common working environment using these files.

IV.1 USER CONFIGURATION FILE (.CFG)

IV.1.1 DESCRIPTION The user configuration file has an XML format with either .cfg or .geo extension. This file may contain the following information:

- Geographic data set: Paths of imported geographic maps (vector, traffic maps, clutter, DEM, image, …), map display settings (display type, visibility scale, transparency, tips text, …), clutter description (code, name, colour, height, model standard deviation and orthogonality factor of each clutter class), the description of traffic maps (raster and vector maps, map per sector and service), new types and formats of geographic data (customer density, …),

- The computation zone definition, - Folder configurations: Sort/group/filter criteria and display settings of sites, antennas, transmitters, microwave

links and propagation models, - Study definition: List of prediction studies available in the Predictions folder and their settings such as general

information (name, comments, group, sort and filters), study conditions and display settings (display type, visibility scale, add to legend option, tips text, transparency level, …),

- AFP Configuration: Settings specified when starting an AFP session as well as calculation parameters, - Paths of files containing macros.

IV.1.2 CREATION This is an upgradable file format. It is necessary to create it from Atoll so that it can be read again. Several examples are provided hereafter. User configuration files can be opened by classical XML viewers (Internet Explorer, XMLSpy, ...). So, it is possible to make selective changes such as the path of geographic data.

IV.1.2.a EXAMPLES

IV.1.2.a.i Example 1: Geographic data set <Atoll> <Geodataset version="2"> <Vectors> <Name>rte1</Name> <Display>

… </Display> <File> <Format>SHP</Format> <Path>\\Bigdisk\BIGDISK\DonneesGeo\France\Routes\rte1.shp</Path> </File> </Vectors>

… </Geodataset> </Atoll>



IV.1.2.a.ii Example 2: Folder configuration <Atoll> <FoldersConfigurations> <Sites>

… </Sites>

… </FoldersConfigurations> </Atoll>

IV.1.2.a.iii Example 3: Computation zone and study list <Atoll> <CalculationZone> <Point>526097 1841220</Point>

… </CalculationZone> <Studies> <CoverageCarrierStudy> <Name>Coverage by signal level</Name> <Display>

… </Display> <Conditions>

… </Conditions> </CoverageCarrierStudy> </Studies> </Atoll>

IV.1.2.a.iv Example 4: AFP Configuration <Atoll> <AFP_options> <defSeparations__CONF_CO_SITE_BB>2</defSeparations__CONF_CO_SITE_BB> … <allocType>59</allocType> <numMinutes>60</numMinutes> <useDTX>1</useDTX> <dtxVocalFactor>70</dtxVocalFactor> <AfpBasedOnInterference>1</AfpBasedOnInterference> <AfpBasedOnSeparations>1</AfpBasedOnSeparations> <IM_calculate__WithTraffic>0</IM_calculate__WithTraffic> … </AFP_options> </Atoll>

IV.1.2.a.v Example 5: Macros <Atoll> <Macros> <File> <Path>C:\TestsAddin\testEvents.vbs</Path> <Language>VBScript</Language> <Timeout>60</Timeout> </File> </Macros> </Atoll>



IV.1.3 AUTOMATIC LOADING Three methods can be used to automatically load the configuration file when users create a new ATL document (by selecting either New or Open from a database in the File menu):

1. Use the following syntax “C:\Program Files\Forsk\Atoll\Atoll.exe -Cfg <configuration_file>” as Atoll desktop shortcut.

Note: We assume that C:\Program Files\Forsk\Atoll\Atoll.exe corresponds to the location of the application file of Atoll.

2. The configuration file must be called atoll.cfg and placed in the Atoll installation directory. Note: This method works only if syntax of the Atoll desktop shortcut does not contain the string “-Cfg

<configuration_file>”.

3. Use the Atoll Management Console to specify the user configuration file to be loaded for each user. This one depends on the user logon properties. For further information, please refer to the Atoll Management Console documentation.

IV.2 ATOLL.INI FILES

IV.2.1 DESCRIPTION The atoll.ini file is a text file. In order for the file to be used by Atoll, you may:

1. Either place the file in the Atoll installation directory. 2. Or use the Atoll Management Console to specify the atoll.ini file to be loaded for each user. This one depends

on the user logon properties. For further information, please refer to the Atoll Management Console documentation.

The atoll.ini file may contain the following settings:

- Prefixes to be used for naming sites and transmitters, - The possibility to deny automatic renaming of transmitters and cells when site names are modified, - The modelling method and display option of antenna patterns, - Computation options as the list of calculation servers (among which path loss computations will be

distributed), the number of threads used for computations and the priority between calculations and user interface,

- Information to be displayed in the Status bar, - How shadowing is to be considered in Ec/Io calculation, - A request to inform user about the expiry date of the Atoll temporary license, - The possibility to display milliseconds in the Event viewer, - The BSIC format used in new ATL documents and the ones created in version 2.1, - The colour convention of Tiff files.

Note: This file is read only when Atoll is started.

IV.2.1.a SITE AND TRANSMITTER NAMES It is possible to specify prefixes to be used for naming sites and transmitters. In case of site, you must add these lines:

[Site] Prefix=”newprefix”

Each new site will be named “newprefixN” instead of “SiteN”. For transmitters, you can define a prefix by adding these lines:

[Transmitter] Prefix=”newprefix”



Each new transmitter will be named “newprefixN” instead of Sitename_n (Sitename is the name of the site where the transmitter is located and n is the transmitter sector number on this site).

IV.2.1.b AUTOMATIC RENAMING OF TRANSMITTERS AND CELLS When the name of any site is modified, Atoll automatically renames the transmitters and cells related to the site according to the new site name. Similarily, renaming a transmitter renames the corresponding cells automatically. Automatic renaming according to site names is enabled by default. However, it may be disabled by adding the following lines in the Atoll.ini file:

[AutoRename] Transmitters= 0 3GCells= 0

‘Transmitters’ refers to transmitter renaming when the site name is changed. ‘3Gcells’ refers to cell renaming when the transmitter name is changed.

IV.2.1.c MODELLING METHOD OF ANTENNA PATTERNS The file should contain following information:

[Antenna] PatternInterpolation=0 or 1 AngleCalculation=0 or 1 Catalog Vertical Diagram Orientation=0 or angle value

For PatternInterpolation and AngleCalculation, 0 or 1 has the following meaning:

0: Method used in Atoll versions prior to 2.1, 1: New method available from the Atoll 2.1 version (included).

PatternInterpolation and AngleCalculation respectively refer to the methods used to determine losses and calculate azimuth and tilt angles. Catalog Vertical Diagram Orientation is only a display option. It enables representing the antenna’s vertical diagram with a certain orientation. Adjusting Catalog Vertical Diagram Orientation = 90, for example, will rotate the vertical diagram by 90° in clock-wise direction. 0 corresponds to the default display.

IV.2.1.d COMPUTATION OPTIONS The file should contain the following instructions:

[RemoteCalculation] Servers=List of servers with semicolon as separator or * in order to use all the available servers NumberOfThreads=1 or 2 Priority=0, 1, 2

NumberOfThreads enables you to limit the number of processors of the server used for computations.

1: Only one processor will work out, 2: Both processors of server will be used.

Priority enables you to set the priority between calculations and user interface.

0: highest priority of user interface 1: higher priority of user interface 2: same priority

By default, when no information is given in the atoll.ini file, priority is set to 1.

IV.2.1.e INFORMATION DISPLAYED IN THE STATUS BAR It is possible to hide altitude, clutter class and/or clutter height information in the status bar. The atoll.ini file should contain the following corresponding lines in the respective case:

[StatusBar] DisplayZ=0 DisplayClutterClass=0 DisplayClutterHeight=0

DisplayZ, DisplayClutterClass and DisplayClutterHeight respectively refer to the display of altitude, clutter class and



clutter height.

IV.2.1.f CONSIDERATION OF SHADOWING IN EC/IO CALCULATION In order to take the DL SHO gain into account in the Ec/Io calculation, the file should contain the following lines:

[CDMA] AddPilotSHOGain=0 or 1

0 means that the DL SHO gain is neither calculated nor taken into account. Specifying it equal to 1 implies it being taken into account in the Ec/Io calculation. When this parameter is not defined in the atoll.ini file, Atoll considers the DL SHO gain. Finally, you may choose the method used to calculate DL and UL SHO gains by adding these lines:

[CDMA] SHOGainAdvanced=0 or 1

0 refers to the method used in Atoll’s versions prior to 2.2.2 and 1 corresponds to the new method used from Atoll version 2.2.2 (inclusive) and onwards. When this parameter is not defined in the atoll.ini file, Atoll 2.3.0 uses the new method.

IV.2.1.g LICENCE EXPIRY DATE The file should contain the following lines:

[License] TimeBombNotice=x

x is the number of days prior to the temporary license expiry date you want Atoll to warn you. By default, when no information is given in the atoll.ini file, Atoll warns the user 30 days before the expiry.

IV.2.1.h DISPLAYING MILLISECONDS IN THE EVENT VIEWER The file should contain the following lines:

[EventsObserver] milliseconds=0 or 1

Setting it to 1 displays milliseconds in the Event viewer

IV.2.1.i BSIC FORMAT The file should contain these lines: [BsicFormat] DefaultValue=1 for Octal or 0 for Decimal format UndefinedValue=1 for Octal or 0 for Decimal format DefaultValue enables you to change the default BSIC format (Octal by default) when you create a new ATL document. UndefinedValue enables you to specify the BSIC format used in ATL documents created/saved in Atoll 2.1. If no information is specified in the atoll.ini file, Atoll considers that BSIC format is undefined.

IV.2.1.j TIFF COLOUR CONVENTION You may export tifF files with a palette containing the background colour at index 0 and then the colour indexes necessary to represent useful information. The file must contain these lines:

[TiffExport] PaletteConvention=Gis



IV.3 STUDIES.XML

IV.3.1 DESCRIPTION The studies.xml file has an XML format. This file can contain the description of prediction studies including:

- The general parameters: name of study template, comments, group, sort and filter criteria, - The study conditions: study criterion, lower and upper thresholds, servers to be studied, margin, carrier, … - The display settings: display type, visibility scale, add to legend option, tips text, transparency level, …

This file must be placed in the Atoll installation directory. So that all the studies described in the studies.xml file can be used as study templates available for all the users in their ATL documents.

IV.3.2 CREATION This is an upgradable file format. It is necessary to create it from Atoll so that it can be read again.

IV.3.2.a EXAMPLE <CoverageCarrierStudy> <Name>Coverage by transmitter</Name> </CoverageCarrierStudy>

C H A P T E R 5

Atoll database structure This chapter describes the tables contained in document templates and the relationships between these tables.

5

Atoll database structure


V ATOLL DATABASE STRUCTURE

V.1 OVERVIEW All the document types offered in Atoll (CDMA2000 1XRTT 1xEV-DO, IS-95 cdmaOne, UMTS WCDMA, GSM GPRS EGPRS) are based on templates. In order to be used, these templates may be located:

1. Either in the Templates folder in the Atoll installation directory. 2. Or in any directory whose location path is declared using the Atoll Management Console for each group of

users. For further information, please refer to the Atoll Management Console documentation. Each template is organised in a database form in .mdb format and consists of a set of tables where the radio network infrastructure is modelled. In this chapter, we will focus on the structure of tables composing the document templates and the relationship between tables of the same template. Fields typed in bold characters in tables correspond to primary keys.

V.2 TABLES

V.2.1 COMMON TABLES The tables described below are available in all document templates and contain the same information irrespective of the project type.

V.2.1.a ANTENNAS TABLE This table contains the description of antennas.

Field Label Length Description Null column allowed

Default value

BEAMWIDTH Float 4 Antenna beamwidth Yes COMMENT Text 255 Additional information about antenna Yes

CONSTRUCTOR Text 50 Antenna manufacturer name Yes

DIAGRAM Binary Internal binary format containing the description of the antenna horizontal and vertical patterns Yes

ELECTRICAL_TILT Float 4 Antenna electrical tilt (for information) Yes 0

Fmax Double 8 Maximum frequency of created antennas Unit: MHz Yes

Fmin Double 8 Minimum frequency of created antenna Unit: MHz Yes

GAIN Float 4 Antenna isotropic gain Unit: dBi No 0

NAME Text 50 Name of antenna created in the current project No Note: Antenna pattern described in a text format may be converted in a binary format using a converter. The format of

the binary field, DIAGRAM, is detailed below. Each antenna is described by a header and a list of value pairs. The header is defined as follows: int (32 bits) flag = 0 for omni diagrams 1 for non-omni short (16 bits) num = number of diagrams (0,1,2,3,4) short (16 bits) siz0 = size of the first diagram (horizontal copolar section (elevation=0°)) short (16 bits) siz1 = size of second (vertical copolar section (azimuth=0°)) short (16 bits) siz2 = size of third (horizontal contrapolar) short (16 bits) siz3 = size of fourth (vertical contrapolar) short (16 bits) prec = precision of the following angle values (=100) Then follows the content of each of the defined diagrams ("sizx" with a value not equal to zero) One diagram consists of a list of value pairs:



- one unsigned short value, the angle in degrees (multiplied by 100), so 577 means 5 degrees 77 hundredth of degree - one short value representing the loss in dB for the given angle. if siz2 = 5, there will be 5 pairs of values describing the third diagram. All the lists of pairs are concatenated without any separator.

V.2.1.b SITES TABLE This table stores all the sites and their properties.

Field Label Length Database Description Null column allowed

Default value Choice list

ALTITUDE Float 4 All Real altitude Unit: m

Yes

COMMENT Text 255 All Additional information on the site Yes LATITUDE Double 8 All Y coordinate No 0

LONGITUDE Double 8 All X coordinate No 0 NAME Text 50 All Site name No

CDMA_EQUIPMENT Text 50 UMTS/CDMA2000 Equipment associated with the site Yes CDMAEquipments table

CHANNEL_ELEMENTS_DL Integer 4 UMTS/CDMA2000 Number of available channel elements for downlink

No 256

CHANNEL_ELEMENTS_UL Integer 4 UMTS/CDMA2000 Number of available channel elements for uplink

No 256

V.2.1.c TRANSMITTERS TABLE This table stores all the transmitters and their properties.

Field Label Length Database Description Null

column allowed


ACTIVE Boolean 2 All Transmitter activity: 'Yes' means that the transmitter is active No 1

ANTDIVGAIN Float 4 All Antenna diversity gain Yes 0

ANTENNA_NAME Text 50 All Name of the main antenna installed on the transmitter No Antennas table

AZIMUT Float 4 All Azimuth of the main antenna No 0

BTS_NAME Text 50 All Name of the BTS equipment Yes BTSEquipments table

CALC_RADIUS Integer 4 All Calculation radius used to define the calculation area Unit: m

Yes 2000

CALC_RADIUS2 Integer 4 All Extended calculation radius (not used in 2.1.0) Yes 2000

CALC_RESOLUTION Integer 4 All Calculation resolution (not used in 2.1.0) Yes 100

CALC_RESOLUTION2 Integer 4 All Extended calculation resolution (not used in 2.1.0) Yes 100

CELL_SIZE Integer 4 All Hexagon radius Unit: m

Yes 2000

COMMENT Text 255 All Additional information about the transmitter Yes

DX Integer 4 All X coordinate relative to the site location Yes 0 DY Integer 4 All Y coordinate relative to the site location Yes 0

FEEDER_NAME Text 50 All Name of the feeder equipment Yes FeederEquipments table

FEEDERLENGTH_DL Float 4 All Length of feeder in DL Yes 0 FEEDERLENGTH_UL Float 4 All Length of feeder in UL Yes 0

HEIGHT Float 4 All Antenna height above the ground Unit: m No 30

HEXAGON_GROUP Text 50 All Group of hexagons used to create this transmitter Yes

MISCDLL Float 4 All Miscellaneous DL loss Yes 0 MISCULL Float 4 All Miscellaneous UL loss Yes 0

PROPAG_MODEL Text 255 All Name of the propagation model used to calculate prediction Yes Default model

Default model, PropagationModels

table

PROPAG_MODEL2 Text 255 All Name of the propagation model used to calculate extended prediction (not used in Yes




column allowed


2.1.0)

SITE_NAME Text 50 All Name of the site on which the transmitter is located (from the site table of Atoll) No Sites table

TILT Float 4 All Mechanical downtilt of the first antenna No 0

TMA_NAME Text 50 All Name of the TMA equipment Yes TMAEquipments table

TX_ID Text 50 All Transmitter name No

AVERAGE_8PSK_POWER_BACKOFF Float 4 GSM/TDMA

Average power reduction for EGPRS transmitters due to 8PSK modulation in EDGE

Yes 3 dB

BSIC Text 10 GSM/TDMA BSIC colour code (Base Station Colour Code) assigned to the station Yes

BSIC_DOMAIN Text 50 GSM/TDMA A text field pointing at the BSIC domain. Yes BSICDomains tableBSIC_FROZEN Boolean 2 GSM/TDMA AFP not allowed to modify BSIC. No 0

CELL_TYPE Text 50 GSM/TDMA

This field identifies a set of records in the TRGConfigurations tables (all the records that point to this cell-type) each of these records specifies a TRG that should exist in this transmitter.

No DCS1800_N_Normal CellTypes table

CHANNELS Text 255 GSM/TDMA Physical channels allocated to the transmitter Yes

CODING_SCHEME_ NUMBER Integer 4 GSM/TDMA The number of coding schemes supported

by the EGPRS transmitter Yes 4

CONTROL_CHANNEL Integer 4 GSM/TDMA Physical channel used as Broadcast Control Channel (BCCH) Yes

COST_FACTOR Float 4 GSM/TDMA Used by the AFP assign priorities to transmitters Yes 1

EGPRS_EQUIPMENT Text 50 GSM/TDMA Name of the equipment assigned to the E-GPRS station Yes EGPRSEquipments

table

EIRP Float 4 GSM/TDMA Transmitter’s effective isotropic radiated power No 43

ENABLE_EGPRS Boolean 2 GSM/TDMA 'Yes' enables you to consider the transmitter as a E-GPRS station No 0

FBAND Text 20 GSM/TDMA Name of the frequency band FrequencyBands table

FROZEN Boolean 2 GSM/TDMA Only TRXs that are not frozen and belong to non-frozen cells can be assigned frequencies by the AFP.

No 0

HOP_MODE Text 25 GSM/TDMA The hopping mode of the default traffic TRG in this transmitter.

HSN_FROZEN Boolean 2 GSM/TDMA

Only TRGs belonging to non-HSN-frozen cells, and which have non_HSN_frozen configurations, can be assigned HSNs by the AFP.

No 0

LAYER Text 50 GSM/TDMA Name of the Hierarchical Cell Structure layer Yes Layers table

LOSSES Float 4 GSM/TDMA Losses due to transmitter radio equipmentUnit: dB Yes

MAX_NEIGHB_NUMBER Integer 4 GSM/TDMA Maximum number of neighbours for the transmitter Yes

MAX_EXT_NEIGHB_NUMBER Integer 4 GSM/TDMA Maximum number of inter-technology

neighbours for the transmitter Yes

MEAN_CAPACITY_TS Float 4 GSM/TDMA Average data rate supported by the transmitter per time slot Unit: kbps

No 0

NUM_TRX Short 4 GSM/TDMA

The total number of TRXs in this transmitter. In the cases of no or Base band hopping, it must correspond to the number of channels in the CHANNELS field.

Yes 0

PDCH_NUMBER Integer 4 GSM/TDMA Number of time slots dedicated to packet service transmissions Yes 0

POWER Float 4 GSM/TDMA Transmitter power Yes REQ_CHANNELS Integer 4 GSM/TDMA Number of required TRXs No 1

FBAND Text 50 UMTS/CDMA2000 Frequency band No Band1 FrequencyBands

table

NOISE_FIGURE Float 4 UMTS/CDMA2000

Noise figure used to determine the thermal noise at the transmitter No 5

RXLOSSES Float 4 UMTS/CDMA2000

Losses in the uplink due to transmitter radio equipment No 0

TXLOSSES Float 4 UMTS/CDMA2000

Losses in the downlink due to transmitter radio equipment No 0



V.2.1.d TPLTRANSMITTERS TABLE This table is used to store station templates and their properties.


column allowed


ACTIVE Boolean 2 All Transmitter activity: 'Yes' means that the transmitter is active No 0

ANTDIVGAIN Float 4 All Antenna diversity gain Unit: dB Yes

ANTENNA_NAME Text 50 All Name of the main antenna installed on the transmitter No Antennas table

AZIMUT Float 4 All Azimuth of the first antenna No

BTS_NAME Text 50 All Name of the BTS equipment Yes BTSEquipments table

CALC_RADIUS Integer 4 All Calculation radius used to define each transmitter calculation area Unit: m

Yes

CALC_RADIUS2 Integer 4 All Extended calculation radius (not used in 2.1) Unit: m

Yes

CALC_RESOLUTION Integer 4 All Calculation resolution (not used in 2.1) Yes

CALC_RESOLUTION2 Integer 4 All Extended calculation resolution (not used in 2.1) Yes

CELL_SIZE Float 4 All Hexagon radius Unit: m Yes

FEEDER_NAME Text 50 All Name of the feeder equipment Yes FeederEquipments table

FEEDERLENGTH_DL Float 4 All Length of downlink feeder Unit: m Yes

FEEDERLENGTH_UL Float 4 All Length of uplink feeder Unit: m Yes

HEIGHT Float 4 All Antenna height above the ground Unit: m No

MAX_NEIGHB_NUMBER Integer 4 All Maximum number of neighbours for the cell or the transmitter Yes

MAX_EXT_NEIGHB_NUMBER Integer 4 All Maximum number of inter-technology neighbours for the cell or the transmitter

Yes

MISCDLL Float 4 All Miscellaneous downlink loss Yes MISCULL Float 4 All Miscellaneous uplink loss Yes

NAME Text 50 All Template name No NUM_SECOND_ANTENNAS Integer 4 All Number of secondary antennas Yes

NUM_SECTORS Integer 4 All Number of sectors No

PROPAG_MODEL Text 50 All Name of the propagation model used to calculate prediction Yes PropagationModels

table

PROPAG_MODEL2 Text 50 All Name of the propagation model used to calculate extended prediction Yes

TILT Float 4 All Mechanical downtilt of the main antenna No

TMA_NAME Text 50 All Name of the Tower Mounted Amplifier equipment Yes TMAEquipments

table

AVERAGE_8PSK_POWER_BACKOFF Float 4 GSM/TDMA

Average power reduction for EGPRS transmitters due to 8PSK modulation in EDGE

Yes 3 dB

BSIC_DOMAIN Text 50 GSM/TDMA A text field pointing to ResourceGroups.NAME. It limits the BSIC domain of the site.

Yes

CELL_TYPE Text 50 GSM/TDMA

This field marks a set of records in the TRGConfigurations tables (all the records for which TRG_CONFIG has the same value.) Each of these records specifies a TRG that should exist in this transmitter.

No CellTypes table

CODING_SCHEME_ NUMBER Integer 4 GSM/TDMA The number of coding schemes

supported by the EGPRS transmitter Yes 4

EGPRS_EQUIPMENT Text 255 GSM/TDMA Name of the Tower Mounted Amplifier equipment Yes EGPRSEquipments

table

EIRP Float 4 GSM/TDMA Transmitter’s effective isotropic radiated power No 43

ENABLE_EGPRS Boolean 2 GSM/TDMA 'Yes' enables you to consider the No 0




column allowed


transmitter as a E-GPRS station

LAYER Text 50 GSM/TDMA Name of the Hierarchical Cell Structure layer Yes Layers table

LOSSES Float 4 GSM/TDMA Losses due to transmitter radio equipment Unit: dB

Yes

MEAN_CAPACITY_TS Float 4 GSM/TDMA Average data rate supported by the transmitter per time slot Unit: kbps

No 0

PDCH_NUMBER Integer 4 GSM/TDMA Number of time slots dedicated to packet switched service Yes 0

POWER Float 4 GSM/TDMA Transmitter power Yes REQ_CHANNELS Integer 4 GSM/TDMA Number of required physical channels No 1

CARRIERS Text 50 UMTS/CDMA2000 Carriers used by the transmitter No ‘0’ FBAND Text 50 UMTS/CDMA2000 Frequency band No

NOISE_FIGURE Float 4 UMTS/CDMA2000 Noise figure used to determine the thermal noise at the transmitter No

PILOT_POWER Float 4 UMTS/CDMA2000 Power of the pilot channel No

POWER_MAX Float 4 UMTS/CDMA2000 Maximum power supported by the transmitter No

RXLOSSES Float 4 UMTS/CDMA2000Losses in the uplink due to transmitter radio equipment Unit: dB

No

TOTAL_POWER Float 4 UMTS/CDMA2000Total downlink power: manually specified by the user or calculated by the WCDMA simulation algorithm

Yes

TXLOSSES Float 4 UMTS/CDMA2000Losses in the downlink due to transmitter radio equipment Unit: dB

No

UL_LOAD Float 4 UMTS/CDMA2000Uplink transmitter load factor: manually specified by the user or calculated by the WCDMA simulation algorithm

Yes

CHANNEL_ELEMENTS_DL Integer 4 UMTS/CDMA2000 Number of channel elements for downlink No

CHANNEL_ELEMENTS_UL Integer 4 UMTS/CDMA2000 Number of channel elements for uplink No

CDMA_EQUIPMENT Text 50 UMTS/CDMA2000 CDMA equipment Yes CDMAEquipments table

REUSE_DIST Float 4 UMTS/CDMA2000Minimum reuse distance for scrambling codes in UMTS or PN offsets in CDMA2000

Yes

AS_THRESHOLD Float 4 UMTS Max allowed difference with the best-server to enter the Active Set (dB) No

OTHERS_CCH_POWER Float 4 UMTS Power of the other common channels except SCH No

SC_DOMAIN_NAME Text 50 UMTS Scrambling code domain name Yes

SCH_POWER Float 4 UMTS Power of the synchronisation (SCH) channel No

EVDO_CES Integer 4 CDMA2000 Number of EVDO channel elements per carrier Yes

IDLE_POWER_GAIN Float 4 CDMA2000 Gain dedicated to transmitted power in idle state Yes

MUG_TABLE Memo Variable CDMA2000 Set of values used to generate the graph MUG=f(num users) Yes

PAGING POWER Float 4 CDMA2000 Power of the paging channel No PN_DOMAIN_NAME Text 50 CDMA2000 PN Offset code domain name Yes

SYNCHRO_POWER Float 4 CDMA2000 Power of the synchronisation (SCH) channel No



V.2.1.e FREQUENCYBANDS TABLE This table contains the description of frequency band(s).

Field Label Length Database Description Null column allowed Default value

NAME Text 20 GSM/TDMA Name of the frequency band No

CHANNEL_WIDTH Double 8 GSM/TDMA Width of each physical channel composing the frequency band Unit: kHz No 1

EXCLUDED_CHANNELS Text 255 GSM/TDMA Physical channels you do not want to allocate Yes FIRST_CHANNEL Integer 4 GSM/TDMA Number of the first physical channel available on the network No 0

FREQUENCY Double 8 GSM/TDMA Frequency of the downlink carrier Unit: MHz No 1000

LAST_CHANNEL Integer 4 GSM/TDMA Number of the last physical channel available on the network No 0 MULTIPLEX_FACTOR Integer 4 GSM/TDMA Number of logical channels composing a physical channel No 1

NAME Text 50 UMTS/CDMA2000 Unused No Band1 FIRST_CARRIER Integer 4 UMTS/CDMA2000 Number of the first carrier available on the network No 0

FREQUENCY Double 8 UMTS/CDMA2000 Average frequency of the carriers Unit: MHz No 2110

LAST_CARRIER Integer 4 UMTS/CDMA2000 Number of the last carrier available on the network No 0 SPREADING_WIDTH Double 8 UMTS/CDMA2000 Spreading bandwidth definition No 0

V.2.1.f PROPAGATIONMODELS TABLE The table contains the available propagation models and their settings.

Field Label Length Description Null column allowed DATA Binary - Model specific parameters Yes

DESCRIPTION Text 255 User defined Yes NAME Text 50 Name of the propagation model No

SIGNATURE Text 40 Unique Global ID of last model update No TYPE Text 50 ProgID of the model No

V.2.1.g COORDSYS TABLE The Coordsys table enables you to store descriptions of the projection coordinate system and database’s internal coordinate system (display coordinate system when creating database). The Coordsys table contains 23 fields detailed below:

Field Label Length Description Null

column allowed

Default value

CODE Integer 4 Identification number of the coordinate system (the code of user-defined coordinate systems is an integer higher than 32768) No 0

DATUM_CODE Integer 4 Yes 0 DATUM_ROTX Double 8 Arc-seconds Yes 0 DATUM_ROTY Double 8 Arc-seconds Yes 0 DATUM_ROTZ Double 8 Arc-seconds Yes 0 DATUM_SCALE Double 8 Part per million (ppm) Yes 0 DATUM_SHIFTX Double 8 Meters Yes 0 DATUM_SHIFTY Double 8 Meters Yes 0 DATUM_SHIFTZ Double 8 Meters Yes 0 ELLIPS_CODE Integer 4 Yes 0

ELLIPS_RMAJOR Double 8 Meters Yes 0 ELLIPS_RMINOR Double 8 Meters Yes 0

NAME Text 50 Coordinate system name No PROJ_ANGLE Double 8 Decimal degrees Yes 0

PROJ_FALSE_EASTING Double 8 Meters Yes 0 PROJ_FALSE_NORTHING Double 8 Meters Yes 0 PROJ_FIRST_PARALLEL Double 8 Decimal degrees Yes 0 PROJ_LATITUDE_ORIGIN Double 8 Decimal degrees Yes 0

PROJ_LONGITUDE_ORIGIN Double 8 Decimal degrees Yes 0

PROJ_METHOD Byte Undefined, NoProjection, Lambert1SP, Lambert2SP, Mercator, CassiniSoldner, TransMercator, TransMercatorSO, ObliqueStereographic, NewZealandMapGrid, HotineOM, LabordeOM, SwissObliqueCylindical, UTM

Yes 0




column allowed

Default value

PROJ_SCALE_FACTOR Double 8 Yes 0 PROJ_SECOND_PARALLEL Double 8 Decimal degrees Yes 0

PROJ_ZONE_NUMBER Short 2 Used with UTM Yes 0

V.2.1.h UNITS TABLE The Units table contains identification numbers of reception, transmission units, projection coordinate system specified in the ATL document and database internal coordinate system, and internal BSIC format.



COORD_SYSTEM Integer 4 All Display coordinate system when creating database Yes Coordsys table

PROJECTION Integer 4 All Projected coordinate system for geo data Yes Coordsys table

RECEPTION_UNIT Byte All Reception unit when creating database No 0 0=dBm, 1=dbµV, 2=dbµV/m

TRANSMISSION_UNIT Byte All Transmission unit when creating database No 0 0=dBm, 1=Watts,

2=kWatts BSIC_FORMAT Integer 4 GSM/TDMA BSIC format No 1 0=Decimal, 1=Octal

V.2.1.i RECEIVERS TABLE This table contains the receiver parameters.

Field Label Length Description Null column allowed Default value Choice list ADJ_CHANNEL_PROT Float 4 Protection against interfering signals from adjacent channels. No 18

ANTENNA Text 50 Receiver antenna name (if empty an omni antenna is used) Yes Antennas tableHEIGHT Float 4 Height of the receiver No 2 LOSS Float 4 Losses due to receiver radio equipment (up and downlink) No 0 NAME Text 50 Receiver name No

V.2.1.j CUSTOMFIELDS TABLE This table enables you to define default values and choice lists for custom fields added to different tables. For each custom field, you must indicate the table in which it should be available, the default value and a choice list.

Field Label Length Description Null column allowed Choice list CHOICE_LIST Memo Unlimited Choice list for the field Yes

COLUMN_NAME Text 50 Second part of the unique key. Field name No DEFAULT_VALUE Text 50 Default value for the field Yes Atoll table field

TABLE_NAME Text 50 First part of the unique key. Table name No Atoll table

V.2.1.k NETWORKS TABLE The Networks table contains information on the used technology and associated global parameters.


Default value

Choice list

ADD_MRC_SOFTERSOFT Boolean 2 CDMA only: If true, gain due to MRC is taken into account for softer/soft cases No 0

DEFAULT_HOGAIN_UL Float 4 CDMA only: Default soft handoff gain uplink No 0

DEFAULT_MODEL Text 50 Default propagation model No ‘Cost-Hata’ PropagationModels table

DEFAULT_ORTHO_FACTOR Float 4 CDMA only: Default orthogonality factor No 0 DEFAULT_RESOLUTION Integer 4 Default calculation resolution No 100

DMAX Float 4 Maximum radius for a cell No -1 IOISNTOT Boolean 2 CDMA only: Io includes pilot signal or not No -1 NTISNTOT Boolean 2 CDMA only: Nt includes pilot signal or not No 0

NAME Text 50 No SHARED_RESULTS_FOLDER Text 255 Shared results storage folder Yes

SYSTEM Text 50 "WLL", "GSM", "UMTS", "1XRTT", "IS95", "BROADCAST" No

TECHNOLOGY Text 10 "TDMA", "CDMA", “FDMA” No



V.2.1.l SECONDARYANTENNAS TABLE This table contains information about additional antennas installed on transmitters.

Field Label Length Description Null column allowed Default value

ANTENNA Text 50 Name of the antenna installed on the transmitter No Antennas table

AZIMUTH Float 4 Second part of the unique key. Azimuth of the antenna No 0

PERCENT_POWER Float 4 Percentage of power dedicated to the secondary antenna No 0

TILT Float 4 Mechanical downtilt of the secondary antenna No 0

TX_ID Text 50 First part of the unique key. Transmitter name No Transmitters table

V.2.1.m REPEATERS TABLE Atoll is able to manage repeaters as transmitters driven by a donor cell.


column allowed

Default value

Choice list

AMPLIFIER_GAIN Float 4 All Gain of the amplifier Yes 80 AZIMUT Float 4 All Azimuth of the donor side antenna No 0

DONOR_CELLID Text 50 All Name of the donor transmitter No Transmitters tableDOWNTILT Float 4 All Down tilt of the donor side antenna No 0

FEEDER_NAME Text 255 All Name of the donor side feeder Yes FeederEquipments table

FEEDERLENGTH Float 4 All Length of donor side feeder Yes 0 EIRP Float 4 GSM/TDMA EIRP of the repeater No

HEIGHT Float 4 All Height of the donor side antenna No 30 REC_ANTENNA Text 50 All Name of the donor side antenna Yes Antennas table

TX_ID Text 50 All Name of the transmitter (and of the transmitter used for coverage) No Transmitters

table

DELAY_OFFSET Integer 4 All Desynchronisation time between donor cell and repeater

No 0

TOTAL_GAIN Float 4 UMTS/CDMA2000 Total gain to be applied to donor cell pilot power Yes 0 In UMTS or CDMA2000 databases, DONOR_CELLID refers to a cell, while in GSM databases it refers to a transmitter. Notes: 1. Repeater properties are saved in two tables: the donor side parameters are in the Repeaters table and the

coverage side in the Transmitters table. 2. In GSM documents, the repeater EIRP taken into account in calculations is stored in the Repeaters table (the

EIRP column of the Transmitters table is not used).

V.2.1.n TABLES DEDICATED TO SITE LIST MANAGEMENT Atoll is able to manage site lists to filter groups of sites and transmitters easily.

V.2.1.n.i SitesListsNames table Field Label Length Description Null column allowed Choice list

NAME Text 50 Name of the list No

V.2.1.n.ii SitesLists table Field Label Length Description Null column allowed Choice list

LIST_NAME Text 50 First part of the unique key. Name of the list No SitesListsNames table SITE_NAME Text 50 Second part of the unique key. Name of the site No Sites table



V.2.1.o TABLES DEDICATED TO EQUIPMENT MANAGEMENT You may model different pieces of equipment (TMA, feeders and BTS). Three dedicated tables store these descriptions.

V.2.1.o.i TMAEquipments table Field Label Length Description Null column allowed Default value

DL_LOSSES Float 4 Downlink losses of Tower Mounted Amplifier No 0 NAME Text 50 Name of Tower Mounted Amplifier No

NOISE_FIGURE Float 4 Noise figure of Tower Mounted Amplifier No 0 UL_GAIN Float 4 Uplink gain of Tower Mounted Amplifier No 0

V.2.1.o.ii FeederEquipments table Field Label Length Description Null column allowed Default value

CONNECTOR_LOSSES_UL Float 4 Feeder connector losses in uplink No 0 CONNECTOR_LOSSES_DL Float 4 Feeder connector losses in downlink No 0

LOSS_PER_METER Float 4 Feeder loss per meter No 0 NAME Text 50 Name of Feeder No

V.2.1.o.iii BTSEquipments table Field Label Length Description Null column allowed Default value

NAME Text 50 Name of Base Station No NOISE_FIGURE Float 4 Noise figure of Base Station No 0

V.2.1.p TABLES DEDICATED TO MICROWAVE LINKS MANAGEMENT

V.2.1.p.i Links This table stores microwave links and their settings.



ANTENNA1 Text 50 Name of the antenna installed on site1 No Antennas table ANTENNA2 Text 50 Name of the antenna installed on site2 No Antennas table

CLUSTER_ID Text 50 Name of the group of links (if belongs to a tandem links) Yes

COMMENT Text 255 Additional information on the link Yes

DIVERSITY1 Boolean 2 Flag is true if there is a diversity antenna (on site1 receiver) No 0

DIVERSITY2 Boolean 2 Flag is true if there is a diversity antenna (on site2 receiver) No 0

ENVTYPE Short 2 Hydroclimatic parameter: environment (enum for Flat terrain, Mountainous, ...) No 0 Plain zone, Mountain zone, Lake zone,

Link over the water EQP1 Text 50 Name of the equipment installed on site1 Yes LinkEquipments table EQP2 Text 50 Name of the equipment installed on site2 Yes LinkEquipments table

FREQ1 Double 8

Frequency of the descending link 'site1-site2' (site1 and site2 being transmitter and receiver respectively) Unit: MHz

No 1000

FREQ2 Double 8

Frequency of the ascending link 'site1-site2' (site1 and site2 being receiver and transmitter respectivley) Unit: MHz

No 1000

HEIGHT1 Float 4 Height of the antenna installed on site1 Unit: m No 30

HEIGHT2 Float 4 Height of the antenna installed on site2 Unit: m No 30

NAME Text 255 Link name No PL Float 4 Hydroclimatic parameter PL No 10

POLAR1 Text 1 Polarisation of the descending link 'site1 - site2' (site1 and site2 being transmitter and receiver respectively)

No ‘V’

POLAR2 Text 1

Polarisation of the ascending link 'site1-site2' (site1 and site2 being receiver and transmitter respectively)

No ‘V’

PROFILE Binary Link profile (not used in 2.1.0) Yes





R001 Float 4 Hydroclimatic parameter: rain quantity No 22 RAINZONE Short 2 Hydroclimatic parameter: rain zone (A, B, ...) No 4 A,B,C,D,E,F,G,H,I,J,K,L,M,N,P,Q

RXLOSSES1 Float 4 Receiver losses (site2 is the receiver) No 0 RXLOSSES2 Float 4 Receiver losses (site1 is the receiver) No 0

RXTHRESHOLD1 Float 4 Reception threshold at site2 (site2 is the receiver) No -90 RXTHRESHOLD2 Float 4 Reception threshold at site1 (site1 is the receiver) No -90

SEPARATION1 Float 4 Distance between the antenna and the diversity antenna (site1 receiver) Yes 10

SEPARATION2 Float 4 Distance between the antenna and the diversity antenna (site2 receiver) Yes 10

SITE1 Text 50 Name of the site chosen as extremity 1 (site1) for the current link under construction No Sites table

SITE2 Text 50 Name of the site chosen as extremity 2 (site2) for the current link under construction No Sites table

TEMPERATURE Short 2 Hydroclimatic parameter: Temperature No 15 TXLOSSES1 Float 4 Transmitter losses (site1 is the transmitter) No 0 TXLOSSES2 Float 4 Transmitter losses (site2 is the transmitter) No 0 TXPOWER1 Float 4 Transmitter power (site1 is the transmitter) No 20 TXPOWER2 Float 4 Transmitter power (site2 is the transmitter) No 20

VAPOR Short 2 Hydroclimatic parameter: Vapour density No 10

V.2.1.p.ii LinkEquipments table This table enables you to describe link equipment.

Field Label Length Description Null column allowed Default value DISCRIM_CORR Float 4 Correction for the equivalent margin of XPD (dB) No 10

ENHANCEMENT_THR Float 4 Enhancement threshold (overflow) No -35 NAME Text 50 Equipment name No

NOISE_POWER Float 4 Equipment thermal noise No -100 POWER Float 4 Equipment power No 30

SIGN_DEPTH Float 4 Signature Depth (dB) No 30 SIGN_WIDTH Float 4 Signature Width (GHz) No 10

SPECTRUM_WIDTH Float 4 Spectrum mask width No 100 THRESHOLD Float 4 Reception threshold when using this equipment No -90

V.2.1.p.iii LinkEquipmentsIRF table This table contains IRF for interfered equipment-interferer equipment pairs.

Field Label Length Description Null column allowed Choice list INTERFERED Text 50 First part of the unique key. Name of the

interfered equipment No Linkequipments table

INTERFERER Text 50 Second part of the unique key. Name of the interfering equipment No Linkequipments table

IRF Binary Internal binary format containing the description of the interference filtering protections No

Note: The binary field, IRF, represents a list of pairs of values. Each pair consists of: float deltaF: spacing in frequency

float protection: protection applied to this frequency

V.2.1.q TABLES DEDICATED TO NEIGHBOUR MANAGEMENT

V.2.1.q.i Neighbours table This table enables you to store neighbourhood relationships between transmitters (or cells) of a same ATL document (intra-technology neighbours, e.g. neighbourhood between UMTS cells).


column allowed


IMPORTANCE Float 4 Handover importance (for AFP use) Yes

NEIGHBOUR Text 50 Second part of the unique key. List of neighbours No

Transmitters table in GSM/TDMA and CdmaCells table in

UMTS/CDMA2000 RANK Float 4 Order of the neighbourhood (not strict order Yes




column allowed


relation)

REASON Integer 4 Reason of the neighbourhood No Manual Manual, Forced, Co-site, Adjacent, Symmetric, Distance, Coverage

TRANSMITTER Text 50 First part of the unique key. Transmitters or cells No


UMTS/CDMA2000

TYPE Text 50 Type of the neighbourhood (handover, measurement…) Yes

V.2.1.q.ii NeighboursExt table This table enables you to store neighbourhood relationships between transmitters and cells of different ATL documents (inter-technology neighbours, e.g. GSM neighbours of UMTS cells).




NEIGHBOUR Text 50 Second part of the unique key. List of neighbours from another project No


UMTS/CDMA2000

RANK Float 4 Order of the neighbourhood (not strict order relation) Yes

REASON Integer 4 Reason of the neighbourhood No Manual Manual, Forced, Co-site, Adjacent, Symmetric, Distance, Coverage



UMTS/CDMA2000

TYPE Text 50 Type of the neighbourhood (handover,measurement…) Yes

V.2.1.q.iii NeighboursConstraints table This table enables you to force/forbid handover relationships between transmitters (or cells). These constraints are used as inputs to the automatic neighbour allocation.




NEIGHBOUR Text 50 Second part of the unique key. List of neighbours No Transmitters table in

GSM/TDMA and CdmaCells table in UMTS/CDMA2000


REASON Integer 4 Reason of the neighbourhood No Manual

0=Manual, 1=Forced, 2=Co-site, 3=Adjacent,

4=Symmetric, 5=Distance, 6=Coverage

STATUS Integer 4 Type of constraint on the neighbourhood relationship. Constraint is used in automatic allocation. No Forced 0=Forced, 1=Forbidden

TRANSMITTER Text 50 First part of the unique key. Transmitters or cells. No Transmitters table in

GSM/TDMA and CdmaCells table in UMTS/CDMA2000

TYPE Text 50 Type of the neighbourhood (handover, measurement…) (not used in 2.3) Yes

V.2.1.q.iv NeighboursConstraintsExt table This table enables you to force/forbid external handover relationship (with cells of another project). These constraints are used as inputs to the automatic neighbour allocation.




NEIGHBOUR Text 50 Second part of the unique key. List of neighbours from another project. No

Transmitters table in GSM/TDMA and

CdmaCells table in UMTS/CDMA2000


REASON Integer 4 Reason of the neighbourhood No Manual

0=Manual, 1=Forced, 2=Co-site, 3=Adjacent,

4=Symmetric, 5=Distance, 6=Coverage





STATUS Integer 4 Type of constraint on the neighbourhood relationship. Constraint is used in automatic allocation. No Forced 0=Forced, 1=Forbidden


Transmitters table in GSM/TDMA and

CdmaCells table in UMTS/CDMA2000

TYPE Text 50 Type of the neighbourhood (handover, measurement…)(not used in 2.3) Yes

V.2.2 CDMA2000 1XRTT 1XEV-DO, IS-95 CDMAONE, UMTS WCDMA TABLES These tables are available in the CDMA2000 1XRTT 1xEV-DO, IS-95 cdmaOne and UMTS WCDMA project templates. Note: The IS-95 cdmaOne and CDMA2000 1XRTT 1xEV-DO document templates have the same data structure. In the

following part, we will imply that fields available in the CDMA2000 database are also available in the IS-95 cdmaOne document templates.

V.2.2.a CDMACELLS TABLE This table enables you to store cells and their properties.


column allowed


CARRIER Short 2 UMTS/CDMA2000 Carrier number No 0 CELL_ID Text 50 UMTS/CDMA2000 Name of the cell No

COMMENT Text 255 UMTS/CDMA2000 Additional information about the cell Yes

MAX_NEIGHB_NUMBER Integer 4 UMTS/CDMA2000 Maximum number of neighbours for the cell Yes

MAX_EXT_NEIGHB_NUMBER Integer 4 UMTS/CDMA2000 Maximum number of inter-technology neighbours for the cell Yes

PILOT_POWER Float 4 UMTS/CDMA2000 Power of the pilot channel No 33

POWER_MAX Float 4 UMTS/CDMA2000 Maximum power supported by the transmitter No 43

REUSE_DIST Float 4 UMTS/CDMA2000Minimum reuse distance for scrambling codes in UMTS and PN Offsets in CDMA2000.

Yes

TOTAL_POWER Float 4 UMTS/CDMA2000

Total downlink power: manually specified by the user or calculated by the WCDMA simulation algorithm

Yes

TX_ID Text 50 UMTS/CDMA2000 Name of the transmitter No Transmitters table

UL_LOAD Float 4 UMTS/CDMA2000

Uplink transmitter load factor: manually specified by the user or calculated by the WCDMA simulation algorithm

Yes

AS_THRESHOLD Float 4 UMTS Maximum difference with the best-server to enter active Set (dB) No 5

OTHERS_CCH_POWER Float 4 UMTS Power of other common channels except SCH No 30

SC_DOMAIN_NAME Text 50 UMTS Scrambling code domain name. Yes ScramblingCodesDomains table

SCH_POWER Float 4 UMTS Power of the synchronisation (SCH) channel No 21

SCRAMBLING_CODE Short 2 UMTS Scrambling code. Yes

IDLE_POWER_GAIN Float 4 CDMA2000 Gain dedicated to transmitted power in idle state. No -10

MUG_TABLE Memo Variable CDMA2000 Set of values used to generate the graph MUG=f(number of users) Yes

PN_DOMAIN_NAME Text 50 CDMA2000 PN Offset domain name. Yes PnCodesDomains table PN_OFFSET Short 2 CDMA2000 PN Offset. Yes

SYNCHRO_POWER Float 4 CDMA2000 Power of the synchronisation (SCH) channel No 17

PAGING_POWER Float 4 CDMA2000 Power of other common channels except SCH No 27



V.2.2.b CDMAEQUIPMENTS TABLE This table describes equipment that performs radio resource management at site level.



CARRIER_SELECTION Short 2 UMTS/CDMA2000 Carrier selection mode No min UL noise

0="min UL noise" 1= "min DL power" 2="random"

CES_OVERHEAD_DL Integer 4 UMTS/CDMA2000 Number of channel elements used for DL overhead channels (pilot, synchro, ...) No 0

CES_OVERHEAD_UL Integer 4 UMTS/CDMA2000 Number of channel elements used for UL overhead channels (pilot, synchro, ...) No 0

MANUFACTURER Text 50 UMTS/CDMA2000 Name of the manufacturer Yes

MUD_FACTOR Float 4 UMTS/CDMA2000 MUD factor for UL interference cancellation No 0

NAME Text 50 UMTS/CDMA2000 Equipment name No

RAKE_EFFICIENCY Float 4 UMTS/CDMA2000 Efficiency of the rake receiver. Used for combination of AS member contributions No 1

USE_NEIGHBOURS Boolean 2 UMTS/CDMA2000If true, selection of AS members is limited to the neighbours of the selected transmitter

No 0

V.2.2.c CDMAEQUIPMENTSCESUSE TABLE This table contains information about consumption of channel elements.



CHANNEL_ELTS_DL Integer* 4 UMTS/CDMA2000 Number of channel elements used for downlink No 1

CHANNEL_ELTS_UL Integer* 4 UMTS/CDMA2000 Number of channel elements used for uplink No 1

EQUIPMENT Text 50 UMTS/CDMA2000 First part of the unique key. Name of equipment No CDMAEquipments

table

SERVICE Text 50 UMTS/CDMA2000Second part of the unique key. Service name in UMTS or Terminal name in CDMA/CDMA2000

No UMTSServices table

*In CDMA/CDMA2000 projects, these field values have float type.

V.2.2.d CARRIERSTYPE (ONLY FOR CDMA2000 1XRTT 1XEV-DO, IS-95 CDMAONE) This table lists the different carriers and enables you to indicate whether it is a 1xEV-DO carrier or a 1xRTT carrier.



CARRIER Integer 4 CDMA2000 Carrier number No

TYPE Integer 4 CDMA2000 Carrier type No 1xRTT 1xRTT=0 1xEV-DO=1

V.2.2.e TABLES DEDICATED TO SCRAMBLING CODE MANAGEMENT (ONLY FOR UMTS) This table enables you to specify some constraints (range of available scrambling codes, pairs of cells which cannot be assigned the same scrambling codes) that Atoll will use as inputs to the automatic scrambling code allocation.

V.2.2.e.i ScramblingCodesDomains table Field Label Length Database Description Null column allowed

DOMAIN_NAME Text 50 UMTS Resource domain name No

V.2.2.e.ii ScramblingCodesGroups table


column allowed


DOMAIN_NAME Text 50 UMTS Second part of the unique key. Called grouping scheme. Set of scrambling code groups. No Scrambling

CodesDomains table

EXCLUDED Text 225 UMTS List of codes to be excluded from the series defined by FIRST, LAST and STEP (separated by blank charaters) Yes

EXTRA Text 225 UMTS Codes to be added. It is forbidden for EXTRA and EXLUDED to have common numbers. Separator must be a blank character. Yes




column allowed


FIRST Integer 4 UMTS Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, …, FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP ≤ LAST.

No 0

LAST Integer 4 UMTS Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, …, FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP ≤ LAST.

No 0

NAME Text 50 UMTS First part of the unique key. Name of the scrambling code group No

STEP Integer 4 UMTS Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, …, FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP ≤ LAST.

No 1

V.2.2.e.iii Separations table Field Label Length Database Description Null column

allowed Choice list

TX_ID Text 50 UMTS First part of the unique key. First cell name in a symmetric relation No CdmaCells table

TX_ID_OTHER Text 50 UMTS Second part of the unique key. Second cell name in a symmetric relation No CdmaCells table

V.2.2.f TABLES DEDICATED TO PN OFFSET MANAGEMENT (IS95, CDMAONE AND CDMA2000) This table enables you to specify some constraints (range of available PN offsets, pairs of cells which cannot be assigned the same PN offset) that Atoll will use as inputs to the automatic PN offset allocation.

V.2.2.f.i PnCodesDomains table Field Label Length Database Description Null column allowed

DOMAIN_NAME Text 50 CDMA2000 Resource domain name No

V.2.2.f.ii PnCodesGroups table


column allowed


DOMAIN_NAME Text 50 CDMA2000 Second part of the unique key. Domain of the PN code group. No PnCodesDomains

table

EXCLUDED Text 225 CDMA2000 List of codes to be excluded from the series defined by FIRST, LAST and STEP (separated by blank character) Yes

EXTRA Text 225 CDMA2000 Codes to be added. It is forbidden for EXTRA and EXLUDED to have common numbers. Separator must be a blank character. Yes

FIRST Integer 4 CDMA2000 Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, …, FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP ≤ LAST.

No 0

LAST Integer 4 CDMA2000 Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, …, FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP ≤ LAST.

No 0

NAME Text 50 CDMA2000 First part of the unique key. Name of the PN code group No

STEP Integer 4 CDMA2000 Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, …, FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP ≤ LAST.

No 1

V.2.2.f.iii Separations table Field Label Length Database Description Null column

allowed Choice list

TX_ID Text 50 CDMA2000 First part of the unique key. First cell name in a symmetric relation No CdmaCells table

TX_ID_OTHER Text 50 CDMA2000 Second part of the unique key. Second cell name in a symmetric relation No CdmaCells table



V.2.2.g MULTI-SERVICE TRAFFIC MANAGEMENT These tables contain descriptions of multi-service traffic data (services, mobility types, terminals, user profiles and environments).

V.2.2.g.i UMTSEnvironmentDefs table Field Label Length Database Description Null column

allowed Default value Choice list

DENSITY Float 4 UMTS/CDMA2000 Number of subscribers per km2 No 0

ENVIRONMENT Text 50 UMTS/CDMA2000 Environment name No UMTSTraficEnvironments table

MObilITY Text 50 UMTS/CDMA2000 Type of mobility Yes UMTSMobility table USER_PROFILE Text 255 UMTS/CDMA2000 Type of user profile Yes UserUserProfiles table

V.2.2.g.ii UMTSMobility table Field Label Length Database Description Null column allowed

NAME Text 50 UMTS/CDMA2000 Type of mobility No TADD Float 4 UMTS/CDMA2000 Minimum Ec/Io for best server selection No

TDROP Float 4 CDMA2000 Ec/Io threshold for active set rejection No

V.2.2.g.iii UMTSServicesQuality table Field Label Length Database Description Null column


MOBILITY Text 50 UMTS/CDMA2000 Second part of the unique key. Type of mobility No UMTSMobility

table

SERVICE Text 50 UMTS/CDMA2000 First part of the unique key. Name of the service No UMTSServices

table

DL_TARGET_QUAL Float 4 UMTS Eb/Nt target on the downlink for a type of mobility No 0

UL_TARGET_QUAL Float 4 UMTS Eb/Nt target on the uplink for a type of mobility No 0

DL_TARGET_QUAL Float 4 CDMA2000 Eb/Nt target on the downlink for each type of (mobility, SCH rate) pair No 0

PTCH_MIN Float 4 CDMA2000 Minimum transmitter power on fundamental traffic channel for the service No 14

PTCH_MAX Float 4 CDMA2000 Maximum transmitter power on fundamental traffic channel for the service No 34

UL_TARGET_QUAL Float 4 CDMA2000 Eb/Nt target on the uplink for each type of (mobility, SCH rate) pair No 0

SCH_RATE Integer 4 CDMA2000 SCH Rate factor (0 -> 16) No 0

V.2.2.g.iv UMTSServicesUsage table Field Label Length Database Description Null column


CALL_DURATION Float 4 UMTS/CDMA2000 Average duration of a call (for circuit switched services) Unit: s

Yes

CALL_NUMBER Float 4 UMTS/CDMA2000 Average number of calls per hour for circuit switched services or average number of sessions per hour for packet switched services

No 0

SERVICE Text 50 UMTS/CDMA2000 Service that the subscriber may request No UMTSServices table

TERMINAL Text 50 UMTS/CDMA2000 Type of terminal used by the subscriber for the service No UMTSTerminals

table

USER_PROFILE Text 255 UMTS/CDMA2000 User profile name No UMTSUserProfile table

DL_VOLUME Float 4 UMTS Volume transferred on the downlink during a session (for packet switched services) Unit: Kbyte

Yes

UL_VOLUME Float 4 UMTS Volume transferred on the uplink during a session (for packet switched services) Unit: Kbyte

Yes



V.2.2.g.v UMTSServices table Field Label Length Database Description Null column

allowed Default value

BODY_LOSS Float 4 UMTS/CDMA2000 Losses due to the user body No 0 DL_CODING_FACTOR Float 4 UMTS/CDMA2000 Coding factor on the downlink No 1

NAME Text 50 UMTS/CDMA2000 Service name No

PRIORITY Integer 4 UMTS/CDMA2000 Priority level of the service: parameter used in the WCDMA simulation No 0

UL_CODING_FACTOR Float 4 UMTS/CDMA2000 Coding factor on the uplink No 1 USE_HANDOFF Boolean 2 UMTS/CDMA2000 'Yes' if the service supports soft handoff No 0

DL_ACTIVITY Float 4 UMTS Activity factor for circuit switched service on the downlink Yes

DL_NOMINAL_BIT_RATE Float 4 UMTS Service nominal data rate on the downlink Unit: kbps No

DL_PACKET_EFFICIENCY Float 4 UMTS Packet efficiency factor on the downlink Yes

PACKET_SWITCHED Boolean 2 UMTS 'Yes' for packet switched service - 'No' for circuit switched service No No

UL_ACTIVITY Float 4 UMTS Activity factor for circuit switched service on the uplink Yes

UL_NOMINAL_BIT_RATE Float 4 UMTS Service nominal data rate on the uplink Unit: kbps No

PTCH_MAX Float 4 UMTS Maximum transmitter power on traffic channel for the service No 21

PTCH_MIN Float 4 UMTS Minimum transmitter power on traffic channel for the service No -20

UL_PACKET_EFFICIENCY Float 4 UMTS Packet efficiency factor on the uplink Yes

DLFCH_ACTIVITYFACTOR Float 4 CDMA2000 Occupancy time of the fundamental channel on the downlink Yes 1

DLRATE_2 Float 4 CDMA2000 Probability to transmit twice the nominal rate on the supplementary channel (SCH) on the downlink Yes 0

DLRATE_4 Float 4 CDMA2000 Probability to transmit four times the nominal rate on the supplementary channel (SCH) on the downlink Yes 0

DLRATE_8 Float 4 CDMA2000 Probability to transmit eight times the nominal rate on the supplementary channel (SCH) on the downlink Yes 0

DLRATE_16 Float 4 CDMA2000 Probability to transmit sixteen times the nominal rate on the supplementary channel (SCH) on the downlink Yes 0

TYPE Integer 2 CDMA2000 '0'=’Speech’,’1’=’Data 1xRTT’ ‘2’=’EVDO’ No 0

ULFCH_ACTIVITYFACTOR Float 4 CDMA2000

Either occupancy time of the fundamental channel on the uplink for 1xRTT, or probability to transmit the nominal rate on the supplementary channel (SCH) on the uplink in case of 1xEVDO.

No 1

ULRATE_2 Float 4 CDMA2000 Probability to transmit twice the nominal rate on the supplementary channel (SCH) on the uplink No 0

ULRATE_4 Float 4 CDMA2000 Probability to transmit four times the nominal rate on the supplementary channel (SCH) on the uplink No 0

ULRATE_8 Float 4 CDMA2000 Probability to transmit height times the nominal rate on the supplementary channel (SCH) on the uplink No 0

ULRATE_16 Float 4 CDMA2000 Probability to transmit sixteen times the nominal rate on the supplementary channel (SCH) on the uplink No 0

V.2.2.g.vi UMTSTerminals table Field Label Length Database Description Null column


GAIN Float 4 UMTS/CDMA2000 Receiver antenna gain No 0 LOSS Float 4 UMTS/CDMA2000 Receiver antenna loss No 0 NAME Text 50 UMTS/CDMA2000 Terminal name No

NOISE_FACTOR Float 4 UMTS/CDMA2000 Noise figure used to determine the thermal noise at the receiver No 8

PMAX Float 4 UMTS/CDMA2000 Maximum receiver power on traffic channel No 21 (UMTS) 23 (CDMA2000)

PMIN Float 4 UMTS/CDMA2000 Minimum receiver power on traffic channels No -20 (UMTS) -50 (CDMA2000)

RAKE_EFFICIENCY Float 4 UMTS/CDMA2000 Efficiency of the rake receiver. Used for combination of Active Set member contributions No 1

ACTIVE_SET_SIZE Short 2 UMTS Maximum number of transmitters possibly connected to the receiver No 3

ACTIVE_SET_SIZE Short 2 CDMA2000 Maximum number of transmitters possibly connected with the receiver for the fundamental channel (FCH) No 6

SCH_AS_SIZE Short 2 CDMA2000 Maximum number of transmitters possibly connected with the receiver for the supplementary channel (SCH) No 3

FWD_BASEDATARATE Float 4 CDMA2000 Downlink nominal rate supported by the receiver on the No



Field Label Length Database Description Null column allowed Default value

fundamental channel RAKE_NUM_FINGERS Short 2 CDMA2000 Number of links of the active set that will be combined No 3

REV_BASEDATARATE Float 4 CDMA2000 Uplink nominal rate supported by the receiver on the fundamental channel No

PILOT_POWER_PCT Float 4 CDMA2000 Percentage of Maximum power dedicated to the UL pilot channel No 0

V.2.2.g.vii UMTSTraficEnvironments table Field Label Length Database Description Null column allowed

CLUTTER_WEIGHTS Binary UMTS/CDMA2000 Internal binary format describing weights assigned to each clutter class Yes

NAME Text 50 UMTS/CDMA2000 Name of the created environment No

V.2.2.g.viii UMTSUserProfiles table Field Label Length Database Description Null column allowed

NAME Text 50 UMTS/CDMA2000 Name of the created user profile No

V.2.3 GSM AND E-GPRS-ORIENTED TABLES The tables described below are available in the GSM_EGPRS document template.

V.2.3.a LAYERS TABLE This table is used to manage HCS layers.

Field Label Length Description Null column allowed Default value NAME Text 50 Name of the hierarchical cell structure layer No

MAX_SPEED Float 4 Threshold speed for a mobile considered eligible to reside on a layer Yes 0

PRIORITY Integer 4 Priority of the layer (largest value has the highest priority) No 1

V.2.3.b TRXTYPES TABLE This table lists the types of TRXs modelled. It contains three types of TRXs, BCCH, TCH and TCH_INNER, by default.


Default value

IS_BCCH Boolean 2 Indicates that a TRG_TYPE is the Common Broadcast carrier. Tests in the code will verify that only one type carries the broadcast. No 0

IS_TCH_DEF Boolean 2 Indicates that a TRG_TYPE is the default traffic carrier (the OUTER zone). Tests in the code will verify that only one type is the default TCH. No 0

NAME Text 15 Type of TRX No

PRIORITY Float 4 Priority of a certain type of TRX to carry traffic (largest value has the highest priority) No 0

V.2.3.c RESOURCE MANAGEMENT These tables enable you to manage resources such as frequencies, BSICs and HSNs. You may define domains and groups of resources (a domain being a set of groups of resources).

V.2.3.c.i FrequencyDomains table Field Label Length Description Null column

allowed Choice list

FREQUENCY_BAND_NAME Text 50 Name of the frequency band on which domain is based No FrequencyBands table

NAME Text 50 Name of domain No

V.2.3.c.ii FrequencyGroups table Field Label Length Description Null column


DOMAIN_NAME Text 50 Called grouping scheme. Set of resource groups. No FrequencyDomains

table EXCLUDED Text 225 List of frequencies to be excluded from the series Yes





defined by FIRST, LAST and STEP (separated with comas)

EXTRA Text 225 Frequencies to be added. It is forbidden for EXTRA and EXLUDED to have common numbers

Yes

FIRST Short 2

Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, …, FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP ≤ LAST.

No 0

LAST Short 2


No 0

NAME Text 50 Unique key. Name of a Resource Group No

STEP Short 2


No 1

V.2.3.c.iii BSICDomains table Field Label Length Description Null column allowed

NAME Text 50 Name of the domain No

V.2.3.c.iv BSICGroups table Field Label Length Description Null column


DOMAIN_NAME Text 50 Called grouping scheme. Set of resource groups. No BSICDomains table

EXCLUDED Text 225 List of BSICs to be excluded from the series defined by FIRST, LAST and STEP (separated with comas) Yes

EXTRA Text 225 BSIC to be added. It is forbidden for EXTRA and EXLUDED to have common numbers Yes

FIRST Short 2 Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, …, FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP ≤ LAST.

No 0

LAST Short 2 Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, …, FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP ≤ LAST.

No 0

NAME Text 50 Unique key. Name of a resource group No

STEP Short 2 Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, …, FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP ≤ LAST.

No 1

V.2.3.c.v HSNDomains table Field Label Length Description Null column allowed

NAME Text 50 Name of HSN (Hopping Sequence Number) domain. No

V.2.3.c.vi HSNGroups table Field Label Length Description Null column


DOMAIN_NAME Text 50 Called grouping scheme. Set of resource groups. No HSNDomains table

EXCLUDED Text 225 List of HSNs to be excluded from the series defined by FIRST, LAST and STEP (separated with comas) Yes

EXTRA Text 225 HSNs to be added. It is forbidden for EXTRA and EXLUDED to have common numbers Yes

FIRST Short 2 Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, …, FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP ≤ LAST.

No 0

LAST Short 2 Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, …, FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP ≤ LAST.

No 0

NAME Text 50 Unique key. name of a Resource Group No

STEP Short 2 Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, …, FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP ≤ LAST.

No 1



V.2.3.d CELLTYPES TABLE This table lists the cell types.

Field Label Length Description Null column allowed NAME Text 50 Defines the list of TRXs of the station and associated parameters. No

V.2.3.e TRGCONFIGURATIONS TABLE This table enables you to store the cell types parameters.


column allowed


ASSIGN_MODE Text 25 One of the two options: «Free» or «Group constrained». No ‘Free’

BAD_QUAL_UB Float 4 Additional constraints on subcell quality (considered in AFP): maximum probability to have C/I lower than C_OVER_I_MIN.

No 5

C_OVER_I_MIN Float 4 Minimum C/I No 9 CELL_TYPE Text 50 First part of unique key. No Celltypes table

COST_FACTOR Float 4 By default, 1. The cost factor will be used to increase or decrease the importance of subcells of this configuration. No 1

DEF_CIRCUIT_TS Byte Number of time slots that support circuit switched traffic only. No 0

DEF_COMPOSITE_TS Byte Number of time slots that support circuit and packet switched traffic No 8

DEF_DTX Boolean 2 This is a default value of a subcell specific parameter. It is set to true if the TRXs of the subcell use Discontinuous transmission

No 1

DEF_HO_HYST Float 4

This is a default value of a subcell specific parameter. It denotes the handover hysteresis margin (below a minimum reception level). It concerns intra-cell handovers only.

No 4

DEF_HOP_MODE Text 25 This is a default value of a subcell specific parameter. Hopping mode can be “Non Hopping”, “Base Band Hopping”,or “Synthesized Hopping”.

No ‘Non Hopping’

DEF_MIN_RECEPTION Float 4 This is a default value of a subcell specific parameter. It denotes the minimum received power required to be served by this subcell.

No -115

DEF_PACKET_TS Byte Number of time slots that support packet switched traffic. No 0

DEF_POWER_OFFSET Float 4 This is a default value of a subcell specific parameter: the average power offset with respect to the BCCH channel. No 0

FREQUENCY_DOMAIN Text 50 All frequencies assigned to TRXs of this configuration must belong to this domain. Domains contain grouping info as well.

No FrequencyDomains table

HR_RATIO Float 4 Percentage of Half Rate voice traffic in the subcell. Yes 0

HSN_DOMAIN Text 50 All HSNs assigned to subcells of this configuration must belong to this domain. No HSNDomains table

HSN_FROZEN Boolean 2 Only subcells that point to non-hsn_frozen configurations in non-hsn_frozen cells can by be assigned HSNs by the AFP.

No 0

MAXIMAL_MAL Short 2 Limitation on length of the MAL (Mobile allocation list). No 16

SERVICE_PRIORITY Float 4 If a point can be served by more than one subcell of a transmitter, the subcell that has a higher service priority will serve it.

No 0

TRX_TYPE Text 15 Second part of unique key No TRXTypes table TRAFFIC_OVERFLOW_

TARGET Float 4 The percentage of traffic that is considered to overflow from the subcell. Yes 0

TS_CONFIGURATION_NAME Text 50 Timeslot configuration No TSConfigurationNa

mes table

V.2.3.f TRGS TABLE The table enables you to store subcell parameters.


column allowed


ASSIGN_MODE Text 25 One of the two options: «Free» or «Group constrained». No ‘Free’

BAD_QUAL_UB Float 4 Additional constraints on subcell quality No 5




column allowed


(considered in AFP): maximum probability to have C/I lower than C_OVER_I_MIN.

CIRCUIT_TS Byte Number of time slots that support circuit switched traffic only. No 0

COMPOSITE_TS Byte Number of time slots that support circuit and packet switched traffic. No 8

COST_FACTOR Float 4 By default, 1. The cost factor is used to increase or decrease the importance of subcells of this configuration.

No 1

C_OVER_I_MIN Float 4 Minimum C/I No 9

DTX Boolean 2 It is set to true if the TRXs of the subcell use Discontinuous transmission. No 1

EFFECTIVE_TRAFFIC_OVERFLOW Float 4 Effective traffic overflow Yes

FREQUENCY_DOMAIN Text 50 All frequencies assigned to TRXs of this configuration must belong to this domain. Domains contain grouping info as well.

No FrequencyDomains table

EXCLUDED Text 250 List of frequencies which should not be used by TRX of the current subcell. Yes

HO_HYST Float 4 HO_HYST denotes the handover hysteresis margin (below minimum reception level). It concerns intra-cell handovers only.

No 3

HOP_MODE Text 25 The hopping mode of a subcell can be “Non Hopping”, “Base Band Hopping”, or “Synthesized Hopping”.

No ‘Non Hopping’

HR_RATIO Float 4 Percentage of Half Rate voice traffic in the subcell. Yes 0

HSN Short 2 Assigned HSN. Yes

HSN_DOMAIN Text 50 All HSNs assigned to subcells of this configuration must belong to this domain. No HSNDomains table

HSN_FROZEN Boolean 2 Only subcells that point to non-hsn_frozen configurations in non-hsn_frozen cells can be assigned HSNs by the AFP.

No 0

MAXIMAL_MAL Short 2 Limitation on length of the MAL (Mobile allocation list). No 16

MIN_RECEPTION Float 4 MIN_RECEPTION denotes the minimum reception power required to be served by this subcell.

No -75

PACKET_TS Byte Number of time slots that support packet switched traffic. No 0

POWER_OFFSET Float 4 The average power offset with respect to the BCCH channel. No 0

REQ_CHANNELS Integer 4 Number of required channels. No 0

REQ_COMPOSITE_TS Byte 1 Number of composite timeslots required for a subcell. (Output from the dimensioning process)

Yes

REQ_CIRCUIT_TS Byte 1 Number of circuit switched timeslots required for a subcell. (Output from the dimensioning process)

Yes

REQ_PACKET_TS Byte 1 Number of packet switched timeslots required for a subcell. (Output from the dimensioningprocess)

Yes

SYNCHRO_NAME Text 50 Defines synchronization sets. Yes

TRAFFIC_LOAD Float 4 TRAFFIC_LOAD = (Traffic in Erlangs) / (NUM_TRX*Multyplexing_factor ) (In GSM, multiplexing factor is 8).

No 1

TRAFFIC_OVERFLOW_TARGET Float 4 The percentage of traffic that is considered to overflow from one subcell. Yes 0

TRX_TYPE Text 15 Second part of a unique key. Points to the TRX type table. No TRXTypes table

TS_CONFIGURATION_NAME Text 50 Timeslot configuration No TSConfigurationNames table

TX_ID Text 50 First part of a unique key. It is the transmitter to which this subcell belongs. (The cell type can be retrieved by following this link).

No Transmitters table



V.2.3.g TRXS TABLE The table enables you to store TRXs of transmitters.



CN_LIST Text 255 List of all frequencies assigned to this TRX. (separated with spaces) Yes

FROZEN Boolean 2 Allows/disallows changing parameters of this TRX. No 0 MAIO Integer 4 Assigned MAIO (Mobile Allocation Index Offset). Yes

TRX_NUMBER Integer 4 An order on TRXs in the same subcell. It is the second part of a unique key. No

TRX_TYPE Text 15 The couple TX_ID, TRG_TYPE is the key of the TRGs table to which this TRX belongs No TRXTypes table

TX_ID Text 50 First part of a unique key. It points to Transmitters. The value of the field CELL_TYPE in the Transmitters table can therefore be retrieved and can serve in order to access relevant information in the TRGConfigurations table.

No Transmitters table

V.2.3.h SEPARATIONS TABLE This table contains separation requirements for some pairs of subcells or pairs of transmitters. It is used as input by the automatic frequency planning tool.

Field Label Length Description Null column allowed Default value Choice list MIN_SEP Short 2 Minimum separation requirement. No 1

TRX_TYPE Text 15 First transmitter subcell or All No All TRXTypes table TRX_TYPE_OTHER Text 15 Second transmitter subcell or All No All TRXTypes table

TX_ID Text 50 First transmitter name in a symmetric relation. No Transmitters

table

TX_ID_OTHER Text 50 Second transmitter name in a symmetric relation. No Transmitters

table

V.2.3.i TSCONFIGURATIONNAMES TABLE The table lists the timeslots configurations.

Field Label Length Description Null column allowed Default value Choice list NAME Text 50 Name of the configuration No

V.2.3.j TSCONFIGURATIONS TABLE The table enables you to store timeslots configurations parameters.


column allowed


ADDITIONAL_8PSK_PWR_BCKFF Integer 4

Additional power reduction in case of 8PSK modulation (value to add to AVERAGE_8PSK_MODULATION defined in Transmitters table)

No 0

NAME Text 50 Name of the configuration No TSConfigurationName table

TRX_NUMBER Integer 4 Zero based index of TRX

COMPOSITE_TS Byte 1 Number of time slots that support circuit and packet switched traffic No 8

CIRCUIT_TS Byte 1 Number of time slots that support circuit switched traffic No 0

GPRS_MAX_CS_NUMBER Integer 4 Maximum GPRS coding scheme number supported by packet timeslots of this TRX No 4

EDGE_MAX_MCS_NUMBER Integer 4 Maximum EDGE coding scheme number supported by packet timeslots of this TRX No 9

PACKET_TS Byte 1 Number of time slots that support packet switched traffic No 0



V.2.3.k EGPRSEQUIPMENTS TABLE This table enables you to manage GPRS and EGPRS equipment.

Field Label Length Description Null column allowed Default value CODING_SCHEME_NUMBER Integer 4 Maximum number of available coding schemes No 4

NAME Text 50 Equipment name No

TECHNOLOGY Text 15 GSM, GPRS or GPRS/EDGE. To allocate traffic to compatible transmitter mobile pair. No GPRS

V.2.3.l EGPRSQUALITY TABLE This table enables you to store properties of GPRS and EGPRS equipment.

FIELD Label Length Description Null column allowed


C_THRESHOLD Float 4 Minimum power (C) required at the receiver in order for a coding scheme to be used No

C_THROUGHPUTS Memo Variable Set of values used to generate the Rate=f(C) graph No 1 CODING_SCHEME Integer 4 Coding scheme No

COVERI_THRESHOLD Float 4 Minimum carrier to interference ratio (C/I) required at the receiver in order for a coding scheme to be used No

COVERI_THROUGHPUTS Memo Variable Set of values used to generate the Rate=f(C/I) graph No 1

EDGE Boolean 2 If yes: coding scheme and curves related to edge mode No 0

EQUIPMENT Text 50 Type of equipment No EGPRSEquipments table

MAX_THROUGHPUT Float 4 Maximum data rate obtained when there is no data transmission error Unit: kbps

No 1

MODULATION Boolean 2 True if 8PSK modulation is used for a given coding scheme, False otherwise. Considered when taking AVERAGE_8PSK_POWER_BACKOFF into account

No 0

V.2.3.m EGPRSDIMENSIONINGMODEL TABLE This table enables you to store dimensioning models and dimensioning options.

FIELD Label Length Description Null

column allowed


NAME Text 50 Service Name No QUEUING_MODEL Text 50 Queuing model: Erlang B , Erlang C No Erlang B

MAX_CHANNELS Integer 4 Maximum number of time slots than can be allocated No 16

MIN_DEDICATED_PDCH Integer 4 Minimum dedicated time slots number for packet switched traffic No 0

MAX_DEDICATED_PDCH Integer 4 Maximum dedicated time slots number for packet switched traffic No 4

MAX_TRXS_TO_ADD_FOR_PACKET Integer 4 Maximum allowed number of TRXs to add in order to reach required quality for packet switched services

Yes 4

MAX_USER_MULTIPLEXING Integer 4 Maximum number of simultaneous TBF allowed per TSL Yes 100

PDCH_LOCATION_PREF Text 50 Preferred location of packet switched TS: BCCH, TCH or TCH_INNER Yes TRXTypes

table PDCH_THROUGHPUT_MIN_KPI Boolean 2 Minimum KPI throughput No 1 PDCH_BLOCKING_PROBA_KPI Boolean 2 KPI blocking probability No 0

PDCH_DELAY_KPI Boolean 2 KPI service delay No 0

V.2.3.n EGPRSSERVICEQUALITY TABLE This table enables you to store quality charts used for the packet traffic dimensioning.

FIELD Label Length Description Null column allowed


DIMENSIONING_MODEL Text 50 Name of the dimensioning model No EGPRSDimensioning model

AVAIL_CONNECTIONS Float 4 Number of available connections Yes 1

LOAD_RF Memo Variable Set of values used to generate the chart Rate reduction factor=f(Load) Yes

LOAD_DELAY Memo Variable Set of values used to generate the chart Delay=f(Load) Yes

LOAD_BLOCKING_PROBA Memo Variable Set of values used to generate the chart Blocking=f(Load) Yes



V.2.3.o MULTI-SERVICE TRAFFIC MANAGEMENT These tables contain descriptions of multiservice traffic data (services, mobility types, terminals, user profiles and environments).

V.2.3.o.i EGPRSEnvironmentDefs table

FIELD Label Length Description Null

column allowed


ENVIRONMENT Text 50 Environment name No EGPRSTrafficEnvironments table

USER_PROFILE Text 255 User profile No EGPRSUserProfiles table MOBILITY Text 50 Type of mobility Yes EGPRSMobility table DENSITY Float 4 Number of subscribers per km2 Yes 0

V.2.3.o.ii EGPRSMobility table FIELD Label Length Description Null column allowed NAME Text 50 Type of mobility No SPEED Float 4 Average speed (km/h) No

V.2.3.o.iii EGPRSServices table FIELD Label Length Description Null column


NAME Text 50 Service Name No PACKET_SWITCHED Boolean 2 'Yes' if it is a packet switched service No 0 MIN_THROUGHPUT Float 4 Minimum user throughput requested for the service Yes 1

MIN_THROUGHPUT_RATIO Float 4 Dimensioning target of the % of surface where minimum throughput is reached Yes 1

MAX_DELAY Float 4 Maximum delay allowed for the service Yes 1

MAX_BLOCKING_RATE Float 4 Maximum probability that a packet is blocked (delayed), GoS for circuit switched services Yes 2

MAX_TS_SUPPORT Integer 4 Maximum number of timeslots supported by the service Yes 4

MIN_TS_REQUIRED Integer 4 Minimum number of timeslots required to access the service Yes 1

VOICE Boolean 2 'Yes' if it is the voice service No 1

V.2.3.o.iv EGPRSServicesusage table FIELD Label Length Description Null column


USER_PROFILE Text 255 User profile name No EGPRSUserProfiles table

SERVICE Text 50 Service that the subscriber may request No EGPRSServices table

TERMINAL Text 50 Type of terminal used by the subscriber for the service No EGPRSTerminals table

CALL_NUMBER Float 4 Average number of calls per hour for circuit switched services or average number of sessions per hour for packet switched services

Yes 0

CALL_DURATION Float 4 Average duration of a call (for circuit switched services) Yes

DL_VOLUME Float 4 Volume transferred on the downlink during a session (for packet switched services) Yes

V.2.3.o.v EGPRSTerminals table FIELD Label Length Description Null column


NAME Text 50 Terminal name No

DL_AVAIL_TIME_SLOT Float 4 Number of timeslots the mobile terminal can multiplex in downlink

Yes 1

PRIMARY_BAND Text 50 Frequency band the mobile terminal is compatible with No FrequencyBands table

SECONDARY_BAND Text 50 Frequency band the mobile terminal is compatible with (for dual-band mobile terminals)

Yes FrequencyBands table

TECHNOLOGY Text 50 Technology supported by the mobile terminal Yes GSM, GPRS, GPRS/EDGE

V.2.3.o.vi EGPRSTrafficEnvironments table FIELD Label Length Description Null column

allowed NAME Text 50 Name of the created environment No

CLUTTER_WEIGHTS Binary Internal binary format describing weights assigned to each clutter class Yes



V.2.3.o.vii EGPRSUserProfiles table FIELD Label Length Description Null column

allowed NAME Text 50 Name of the created user profile No

C H A P T E R 6

Coordinate systems This chapter describes the coordinate systems you can define in Atoll.

6

Coordinate systems


VI COORDINATE SYSTEMS

VI.1 BASIC CONCEPTS A map or a geo-spatial database is a flat representation of data collected from a curved surface. A projection is a means for producing all or part of a spheroid on a flat sheet. This projection cannot be done without distortion. Thus, the cartographer must choose the characteristic (distance, direction, scale, area or shape) that he wants to be shown accurately at the expense of the other characteristics. Or compromise on several characteristics [1-3]. The projected zones are referenced using cartographic coordinates (meter, yard, ...). Two projection systems are widely used:

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

- The Transverse Mercator projection: 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.

The geographic system is not a projection. It is only a representation of a location on the surface of the earth in geographic coordinates (degree-minute-second, grade) giving the latitude and longitude in relation to the meridian origin (e.g. Paris for NTF system and Greenwich for ED50 system). The locations in the geographic system can be converted into other projections. References: [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. [2] http://www.colorado.edu/geography/gcraft/notes/gps/gps_f.html [3] geps2.ihsenergy.com/products/geodetic.html

VI.2 COORDINATE SYSTEM MANAGEMENT Atoll uses three coordinate systems:

1. The projection system, 2. The display system, 3. The internal system.

VI.2.1 THE PROJECTION SYSTEM The projection system can be set by the user from the Options dialog. This is the coordinate system in which raster geo data are provided. It is only used to retrieve a geographical value in a given display system. Especially, to make sites and geographic data consistent. It is not used during the import processing. When a raster file is imported, Atoll just uses its geo-referencing (West/North point) to know the value for each pixel. None of the different systems is used in the import process. Nevertheless, the West/North point is given in this coordinate system and it is important to use the correct projection system to keep consistency between geographic data and site positions. Note: It is not possible to manage raster geo data provided in different coordinate systems. When a vector file (traffic,

measurements, …) is imported, a translation between two coordinate systems may be asked through a specific dialog.

VI.2.2 THE DISPLAY SYSTEM The display system can be defined by the user in Options dialog. It is used to display the coordinates in any dialog, with the rulers on the map and in the right bottom corner of the status bar (mouse coordinates). When sites are imported, the display system must match imported site coordinate system to enable further translations. 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.

http://www.colorado.edu/geography/gcraft/notes/gps/gps_f.html



VI.2.3 THE INTERNAL SYSTEM It is the internal coordinate system for site positions and it cannot be modified by the user. This system corresponds to:

The display system for an environment not connected to a database, The database coordinate system for an environment connected to a database. The database coordinate system

is the system used for display when creating a database and cannot be changed. So, when you are not connected to a database and you change the display system, all the site positions are translated in this new system. When you are connected to a database, the site positions are translated in your ATL environment but not in the database since the internal unit can never be changed. Projection and internal coordinate systems are stored in the database. The internal coordinate system is used as the database coordinate system. When creating a document from the database, Atoll respectively considers projection and internal systems stored in the database as projection and display coordinate systems of the document.

VI.3 COORDINATE SYSTEM DESCRIPTION

VI.3.1 OVERVIEW Geographic coordinate system is a latitude and longitude coordinate system. The latitude and longitude are related to an ellipsoid, a geodetic datum and a prime meridian. The geodetic datum provides the position and orientation of the ellipsoid relative to the earth. A projected coordinate system is obtained using a transformation method that converts a (latitude, longitude) pair into an (easting, northing) pair. Therefore, 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. Different methods may require different sets of parameters. For example, the parameters required to define the projected Transverse Mercator coordinate system are:

The longitude of the natural origin (Central meridian), The latitude of the natural origin, The False Easting value, The False Northing value, A scaling factor at the natural origin (on the central meridian),

Basic definitions are summed up hereafter.

VI.3.1.a GEOGRAPHIC COORDINATE SYSTEM The geographic coordinate system is the association of a datum and a meridian. Atoll allows the user to choose the most suitable geographic coordinate system for the geographic area.

VI.3.1.b PROJECTION The projection is the transformation applied to project the ellipsoid of the earth on to a plane. There are different projection methods using sets of specific parameters.

VI.3.1.c PROJECTED COORDINATE SYSTEM The projected coordinate system is the result of the application of a projection to a geographic coordinate system. It associates a geographic coordinate system and a projection. Atoll allows the user to choose the projected coordinate system matching the geographic data.

VI.3.1.d ELLIPSOID The ellipsoid is the pattern used to model the earth. It is defined by its geometric parameters.

VI.3.1.e DATUM The datum consists of the ellipsoid and its position relative to the WGS84 ellipsoid. In addition to the ellipsoid, translation, rotation and distortion parameters define the datum.

Coordinate systems


VI.3.1.f MERIDIAN The standard meridian is Greenwich (of course). But some geographic coordinate systems are based on other meridians. These meridians are defined by a longitude from Greenwich origin.

VI.3.2 FORMAT OF COORDINATE SYSTEM FILES The Coordsystems folder located in the Atoll installation directory contains all the coordinate systems, both geographic and cartographic, offered in the tool. Coordinate systems are grouped by region in the world; one catalogue per region and one, called Favourites (initially empty), are available in the folder. Each catalogue is described by one ASCII text file with .cs extension. In a .cs file, each coordinate system is described in one line. The line syntax is: Code=”Name of the system”;Code of unit;Code of datum;Code of projection;Parameters of the projection;”Comments” Notes: 1. The identification code enables Atoll to differentiate existing coordinates systems. In case you create a new

coordinate system, it must be an integer value strictly higher than 32767. 2. When describing a new datum, you must enter the code of ellipsoid and parameters instead of the datum code in

the brackets. You can have from 3 to 7 parameters defined in this order: Dx, Dy, Dz, Rx, Ry, Rz and S. Commas separate these characteristics. In this case, the line format is:

Code=”Name of the system”;Code of unit;code of ellipsoid,Dx,Dy,Dz,Rx,Ry,Rz,S;Code of projection;Parameters of the projection;”Comments” 3. There are up to seven projection parameters. They must be ordered according to the parameter index given in the

paragraph Indices of projection parameters (parameter with index 0 will be the first one). Projection parameters are delimited by comas.

4. For UTM projections, you must define a positive UTM zone number in case of a north zone and a negative number for south UTM zones.

5. You may enter the usage and/or the region as comments. Examples: 4230="ED50";101;230;0;1;"Europe - west" 32045="NAD27 / Vermont ";2;267;0;6,-72.5,42.5,500000,0,0.9999643;"United States - Vermont" Codes of units, data, projections and projection parameter indices are listed in the tables, hereafter.

VI.3.2.a CODES OF UNITS Cartographic units Code Geographic units Code

Metre 0 Radian 100 Kilometre 1 Degree 101

Foot 2 Grad 102 Link 3 ArcMinute 103

Chain 4 ArcSecond 104 Yard 5

Nautical mile 6 Mile 7

Unspecified -1 Unspecified -1 Code-Unit correspondences

VI.3.2.b CODES OF DATUMS Code Datum Code Datum 121 Greek Geodetic Reference System 1987 260 Manoca 125 Samboja 261 Merchich 126 Lithuania 1994 262 Massawa 130 Moznet (ITRF94) 263 Minna 131 Indian 1960 265 Monte Mario 201 Adindan 266 M'poraloko 202 Australian Geodetic Datum 1966 267 North American Datum 1927 203 Australian Geodetic Datum 1984 268 NAD Michigan 204 Ain el Abd 1970 269 North American Datum 1983 205 Afgooye 270 Nahrwan 1967 206 Agadez 271 Naparima 1972



207 Lisbon 272 New Zealand Geodetic Datum 1949 208 Aratu 273 NGO 1948 209 Arc 1950 274 Datum 73 210 Arc 1960 275 Nouvelle Triangulation Française 211 Batavia 276 NSWC 9Z-2 212 Barbados 277 OSGB 1936 213 Beduaram 278 OSGB 1970 (SN) 214 Beijing 1954 279 OS (SN) 1980 215 Reseau National Belge 1950 280 Padang 1884 216 Bermuda 1957 281 Palestine 1923 217 Bern 1898 282 Pointe Noire 218 Bogota 283 Geocentric Datum of Australia 1994 219 Bukit Rimpah 284 Pulkovo 1942 221 Campo Inchauspe 285 Qatar 222 Cape 286 Qatar 1948 223 Carthage 287 Qornoq 224 Chua 288 Loma Quintana 225 Corrego Alegre 289 Amersfoort 226 Cote d'Ivoire 290 RT38 227 Deir ez Zor 291 South American Datum 1969 228 Douala 292 Sapper Hill 1943 229 Egypt 1907 293 Schwarzeck 230 European Datum 1950 294 Segora 231 European Datum 1987 295 Serindung 232 Fahud 296 Sudan 233 Gandajika 1970 297 Tananarive 1925 234 Garoua 298 Timbalai 1948 235 Guyane Francaise 299 TM65 236 Hu Tzu Shan 300 TM75 237 Hungarian Datum 1972 301 Tokyo 238 Indonesian Datum 1974 302 Trinidad 1903 239 Indian 1954 303 Trucial Coast 1948 240 Indian 1975 304 Voirol 1875 241 Jamaica 1875 305 Voirol Unifie 1960 242 Jamaica 1969 306 Bern 1938 243 Kalianpur 307 Nord Sahara 1959 244 Kandawala 308 Stockholm 1938 245 Kertau 309 Yacare 247 La Canoa 310 Yoff 248 Provisional South American Datum 1956 311 Zanderij 249 Lake 312 Militar-Geographische Institut 250 Leigon 313 Reseau National Belge 1972 251 Liberia 1964 314 Deutsche Hauptdreiecksnetz 252 Lome 315 Conakry 1905 253 Luzon 1911 322 WGS 72 254 Hito XVIII 1963 326 WGS 84 255 Herat North 901 Ancienne Triangulation Française 256 Mahe 1971 902 Nord de Guerre 257 Makassar 903 NAD 1927 Guatemala/Honduras/Salvador

(Panama Zone) 258 European Reference System 1989

Code – Data correspondences

Coordinate systems


VI.3.2.c CODES OF PROJECTION METHODS Code Projection Code Projection

0 Undefined 8 Oblique Stereographic 1 No projection Longitude / Latitude 9 New Zealand Map Grid 2 Lambert Conformal Conical 1SP 10 Hotine Oblique Mercator 3 Lambert Conformal Conical 2SP 11 Laborde Oblique Mercator 4 Mercator 12 Swiss Oblique Cylindrical 5 Cassini-Soldner 13 Oblique Mercator 6 Transverse Mercator 14 UTM Projection 7 Transverse Mercator South Oriented

Code – Projection correspondences

VI.3.2.d INDICES OF PROJECTION PARAMETERS Index Projection parameter Index Projection parameter

0 UTM zone number 4 Scale factor at origin 0 Longitude of origin 4 Latitude of 1st parallel 1 Latitude of origin 5 Azimuth of central line 2 False Easting 5 Latitude of 2nd parallel 3 False Northing 6 Angle from rectified to skewed grid

Indice – Projection parameter correspondences

C H A P T E R 7

Units and BSIC format This chapter deals with unit systems and BSIC formats you can define in Atoll.

7

Units and BSIC format


VII UNITS AND BSIC FORMAT

VII.1 TRANSMISSION POWER UNIT It is important to distinguish the display transmission power unit from the internal transmission power unit.

VII.1.1 THE DISPLAY UNIT The display unit can be set by the user from the Options dialog. It is used in the ATL documents to display the transmission powers in all the dialogs and tables.

VII.1.2 THE INTERNAL UNIT The internal unit cannot be changed by the user. The internal unit of the transmission power corresponds to:

The display unit in case of an environment not connected to a database, The database transmission power unit for an environment connected to a database. The database transmission

power unit is the display transmission power unit of the ATL environment when creating a database. It cannot be changed.

So when you are not connected to a database and you change the transmission power units, all the transmission powers are translated in this new system. When you are connected to a database the transmission powers are translated in your ATL document but not in the database since the internal unit is never changed. The internal transmission power unit system is stored in the database. When creating a new document from a database, Atoll takes the internal unit stored in the database as display transmission power unit in the ATL document.

VII.2 RECEPTION POWER UNIT It is important to distinguish the display reception power unit from the internal reception power unit.

VII.2.1 THE DISPLAY UNIT The display unit can be set by the user form the Options dialog. It is used in the ATL documents to display the reception thresholds (Prediction study properties or microwave link properties) and the received signal levels (measurements, point analysis, coverage studies).

VII.2.2 THE INTERNAL UNIT The internal unit cannot be changed by the user. The internal unit of the reception powers corresponds to:

The display unit in case of an environment not connected to a database, The database reception power unit for an environment connected to a database. The database reception power

unit is the display reception power unit of the ATL environment when creating a database. It cannot be changed. The internal reception power unit system is stored in the database. When creating a new document from database, Atoll takes the internal unit stored in the database as display reception power unit in the ATL document.

VII.3 DISTANCE, HEIGHT AND OFFSET UNITS We can distinguish the display unit from the internal unit here as well.

VII.3.1 THE DISPLAY UNIT The display unit can be changed by the user from the Options dialog. It is used to display distances, heights and offsets in some dialogs, tables and Status bar.

VII.3.2 THE INTERNAL UNIT The internal unit cannot be changed by the user. In any case (ATL environment connected to a database or not), the internal unit is the metre. The internal length unit is not saved in the database.



VII.4 BSIC FORMAT It is important to distinguish the display BSIC format from the internal BSIC format.

VII.4.1 THE DISPLAY FORMAT User may choose the display format in the Options dialog. It is used in ATL documents to display BSICs.

VII.4.2 THE INTERNAL FORMAT The internal format corresponds to:

The display format in case of ATL documents not connected to a database, The database BSIC format for an ATL document connected to a database. The database BSIC format is the

display format of the ATL project when creating a database. It cannot be changed. So when, being not connected to a database, you change the display format, all the BSICs are converted from the old format in the new format except if the old format was undefined. In this case, BSICs do not change. When you are connected to a database, BSICs are converted in your ATL document but not in the database since the internal format is never changed. The internal format is stored in the database. When creating a new document from the database, Atoll takes the internal format stored in the database as display format in the ATL document.

C H A P T E R 8

Geographic data This chapter describes the geographic data types supported by Atoll.

8

Geographic data


VIII GEOGRAPHIC DATA

VIII.1 DATA TYPE Atoll manages several geographic data types; DTM (Digital Terrain Model), clutter (Land-Use), scanned images, vector data, traffic data, population, and any other generic data.

VIII.1.1 DIGITAL TERRAIN MODEL (DTM) The DTM (Digital Terrain Model or height) files describe the ground elevation above the sea level. DTM files supported by Atoll are 16 bits/pixel relief maps in tifF, bil, Planet©, Erdas Imagine and bmp formats. DTM maps are taken into account in path loss calculations by Atoll propagation models. DTM file provides altitude value (z stated in metre) on evenly spaced points. Abscissa and ordinate axes are respectively oriented in right and downwards directions. Space between points is defined by pixel size (P stated in metre). Pixel size must be the same in both directions. First point given in the file corresponds to the upper-left corner of the map. This point refers to the northwest point geo-referenced by Atoll. Four points (hence, four altitude values) are necessary to describe a “bin”; these points are bin vertices.

(0,0,z0) (P,0,z1)

(P,P,z2)(0,P,z3)

Therefore, a n*n bin DTM file requires (n+1)2 points (altitude values).

Pixel size

Pixel size

Northwest point

Bin

Altitude values provided on every point

Schematic view of a DTM file

Notes: 1. Altitude values differ within a bin. Method used to calculate altitudes is described in the Path loss calculations:

Altitude determination part. Concerning DTM map display, Atoll takes altitude of the southwest point of each bin to determine its colour.

2. 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. In Atoll, the DEM term may be used instead of DTM term.



VIII.1.2 CLUTTER (OR LAND-USE) You may import two types of clutter files in ATL documents. These files indicate either the clutter class or the clutter height on each bin of the map.

VIII.1.2.a CLUTTER CLASSES Atoll supports 8 bits/pixel (255 classes) raster maps in tifF, bil, bmp, Erdas Imagine formats or 16 bits/pixel raster maps in Planet© format. This kind of clutter file describes the land cover (dense urban, buildings, residential, forest, open, villages, …). A grid map represents ground and each bin of the map is characterised by a code corresponding to a main type of cover (a clutter class). Atoll automatically lists all the clutter classes of the map. It is possible to specify an average clutter height for each clutter class manually during the map description step. Clutter maps are taken into account in path loss calculations by Atoll propagation models. Clutter file provides a clutter code per bin. Bin size is defined by pixel size (P stated in metre). Pixel size must be the same in both directions. Abscissa and ordinate axes are respectively oriented in right and downwards directions. First point given in the file corresponds to the upper-left corner of the image. This point refers to the northwest point geo-referenced by Atoll.

X

Y

(0,0)

Code 1

Code 4

Code 2

Code 1

Therefore, a n*n bin Clutter file requires (n)2 code values. Note: The clutter code is the same inside a bin.

VIII.1.2.b CLUTTER HEIGHTS Files supported by Atoll for clutter heights are 16 bits/pixel raster maps in tifF, bil, Erdas Imagine and bmp formats. The file provides clutter height value on evenly spaced points. Abscissa and ordinate axes are respectively oriented in right and downwards directions. Space between points is defined by pixel size (P in metre). Pixel size must be the same in both directions. First point given in the file corresponds to the upper-left corner of the map. This point refers to the northwest point geo-referenced by Atoll. These maps are taken into account in path loss calculations by Atoll propagation models. Note: Atoll considers the clutter height of the nearest point in calculations (see Path loss calculations: Clutter

determination part). For map display, Atoll takes clutter height of the southwest point of each bin to determine its colour.

VIII.1.3 TRAFFIC DATA Atoll offers different kinds of traffic data:

- Environment traffic maps, Atoll supports 8 bits/pixel (256 class) traffic raster maps in tiff, bil, bmp, Erdas Imagine formats. These maps provide macroscopic traffic estimation. Each pixel is assigned an environment class, which is a list of user profiles with a defined mobility type and a density.

- User profile traffic maps, Atoll supports vector traffic maps with dxf®, Planet©, shp, mif and agd formats. These maps are detailed traffic estimations (lines or polygons corrying a specific traffic). Each polygon or line is assigned a specific user profile with associated mobility type and density. They can be built from population density vector maps.

- Live traffic maps

Geographic data


Atoll supports maps with agd format. This kind of map is based on the network feedback. It provides actual information on connections (and not just subscriber estimation) from the network. It is built from a coverage by transmitter prediction study that defines sector boundaries for the traffic distribution in each sector. In UMTS, CDMA2000 and IS95-CDMA, either data rates or the number of users per service are indicated for each transmitter service area. In GSM/TDMA, Atoll expects a number of Erlangs in case of speech service and data rate values for packet-switched services for each transmitter service area.

- User density traffic maps This kind of map is only available in GSM/TDMA documents. Atoll supports 16 and 32 bits/pixel traffic raster maps in tiff, bil, bmp, Planet© and Erdas Imagine formats. This map is also based on the network feedback as it deals with network users information as well. Each pixel is assigned a number of users with a given service, terminal and mobility type.

In GSM documents, traffic maps are taken into account for traffic analysis and network dimensioning. In UMTS, CDMA2000 and IS95-CDMA documents, they are used by the Monte-Carlo simulator to model user distributions and evaluate related network parameters (cell power, mobile terminal power, …).

VIII.1.4 VECTOR DATA These data represent either polygons (regions, ...), lines (roads, coastlines, ...) or points (towns, ...). Atoll supports vector data files in DXF®, Planet©, SHP, MIF and AGD formats. These maps are only used for display and provide information about the geographic environment.

VIII.1.5 SCANNED IMAGES These geographic data regroup the road maps and the satellite images. They are only used for display and provide information about the geographic environment. Atoll supports scanned image files in tifF (1, 4, 8, 24-bits/pixel), bil (1, 4, 8, 24-bits/pixel), Planet© (1, 4, 8, 24-bits/pixel), bmp (1-24-bits/pixel) and Erdas Imagine (1, 4, 8, 24-bits/pixel) formats.

VIII.1.6 POPULATION Atoll deals with vector population files in MIF, SHP and AGD formats or 8, 16, 32 bits/pixel raster population files in tifF, bil, bmp, Erdas Imagine formats. Population map describes the population distribution. They are considered in clutter statistics and in coverage plot reports.

VIII.1.7 OTHER GEOGRAPHIC DATA It is possible to import generic geographic data types, other than those listed above, (Customer density, revenue density, …) in Atoll. These data can be either vector files in MIF, SHP and AGD formats or 8, 16, 32 bits/pixel raster files in tifF, bil, bmp, Erdas Imagine formats. These maps are taken into account in coverage plot reports. Notes: 1. The minimum resolution supported by Atoll is 1m for any raster maps. 2. DTM and clutter map resolution must be an integer. 3. All the raster maps you want to import in an ATL document must be represented in the same projection system.

VIII.2 SUPPORTED GEOGRAPHIC DATA FORMATS Atoll offers import filters for the most commonly used geographic data formats. The different filters are:

File format Can contain Georeferenced

bil DTM, Clutter classes and heights, Traffic, Image, Population, Other data Yes via .hdr files

tifF DTM, Clutter classes and heights, Traffic, Image, Population, Other data

Yes via associated .tfw files if they exist

Planet© DTM, Clutter classes, Image, Vector data Yes via index files

bmp DTM, Clutter classes and heights, Traffic, Image, Population, Other data

Yes after manually entering northwest and southwest point coordinates of the image

DXF® Vector data, Vector traffic Yes SHP Vector data, Vector traffic, Population, Other data Yes

MIF/MID Vector data, Vector traffic, Population, Other data Yes

ERDAS IMAGINE DTM, Clutter classes and heights, Traffic, Image, Population, Other data Yes

AGD Vector data, Vector traffic, Population, Other data



Thus, to sum up, you can import:

- DTM files in tifF (16-bit), bil (16-bit), Planet© (16-bit), Erdas Imagine (16-bit) and bmp (16-bit) formats. - Clutter heights files in tifF (16-bit), bil (16-bit), Erdas Imagine (16-bit) and bmp (16-bit) formats. - Clutter classes and traffic raster files in tifF (8-bit), bil (8-bit), bmp (8-bit), Erdas Imagine (8-bit). Clutter files in

Planet© format (16-bit) are also supported. - Vector data files in DXF®, Planet©, SHP, MIF and AGD formats. - Vector traffic files in DXF®, Planet©, SHP, MIF and AGD formats. - Scanned image files in tifF (1, 4, 8, 24-bit), bil (1, 4, 8, 24-bit), Planet© (1, 4, 8, 24-bit), bmp (1-24-bit) and Erdas

Imagine (1, 4, 8, 24-bit) formats. - Population files in MIF, SHP, AGD, tifF (8, 16, 32-bits), bil (8, 16, 32-bits), bmp (8, 16, 32-bits) and Erdas Imagine

(8, 16, 32-bits) formats. - Other generic data types in MIF, SHP, AGD, tifF (8, 16, 32-bits), bil (8, 16, 32-bits), bmp (8, 16, 32-bits) and Erdas

Imagine (8, 16, 32-bits) formats Note: It is possible to import Packbit, FAX-CCITT3 and LZW compressed tiff files. However, in case of DTM and clutter,

we recommend not to use compressed files in order to avoid poor performances. If uncompressed files are too big, it is better to split them.

C H A P T E R 9

Radio data This chapter details all the radio data used in Atoll.

9

Radio data


IX RADIO DATA

IX.1 DATA TYPES Atoll manages several radio data types; sites, transmitters, antennas, stations and hexagonal designs. Data definition in Atoll is detailed hereafter.

IX.1.1 ANY DOCUMENT

IX.1.1.a SITE A site is a geographical point where one or several transmitters (multi-sectored site or station) equipped with antennas are located.

IX.1.1.b ANTENNA An antenna is a device used for transmitting or receiving electromagnetic waves.

IX.1.1.c TRANSMITTER A transmitter is a group of radio devices located at a site. Transmitters are equipped with antenna(s) and other equipment such as feeder, tower mounted amplifiers (TMA) and BTS.

IX.1.1.d REPEATER A repeater is a device that amplifies a received signal both in downlink and in uplink. It consists of two parts, a donor side and a coverage side.

IX.1.1.e STATION A station can represent one transmitter on a site or a group of transmitters on a same site sharing the same properties. You can define station templates and build your network from stations instead of single transmitters.

IX.1.1.f HEXAGONAL DESIGN A hexagonal design is a group of stations created from the same station template.

IX.1.2 GSM_EGPRS DOCUMENTS

IX.1.2.a TRX A base station (transmitter) consists of several transceivers or TRXs. One TRX supports as many time slots as the multiplexing factor defined in properties of your frequency band (8 time slots in GSM networks). Three types of TRXs are modelled in Atoll:

- The BCCH TRX type: carries the BCCH, - The TCH TRX type: which is the default traffic carrier, - The TCH_INNER TRX type: this TRX type is an inner traffic carrier.

IX.1.2.b SUBCELL A subcell corresponds to a group of TRXs having the same radio characteristics, the same quality (C/I) requirements, and common settings. A subcell is characterised by the ‘transmitter-TRX type’ pair. Each transmitter may have one or more subcells. The most common configurations are the BCCH, TCH configuration or the BCCH, TCH, TCH_INNER one.

IX.1.2.c CELL TYPE A cell type describes the subcells (types of TRXs) that a cell can use and their parameters, which can be different. In the current Atoll version, the cell type definition must include a TRX type as the BCCH carrier (BCCH TRX type) and another TRX type as 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.



IX.1.3 UMTS, CDMA2000 AND IS95-CDMA DOCUMENTS

IX.1.3.a CELL Cell comprises the carrier characteristics of a transmitter. Cell is characterised by the ‘transmitter-carrier’ pair. The transmitter-carrier pair must be unique.

C H A P T E R 10

File formats This chapter describes the main formats of files you can import in and export from Atoll.

10

File formats


X FILE FORMATS

X.1 BIL FORMAT Band Interleaved by Line is a method of organizing image data for multi-band 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 auxiliary data about the image, such as the number of rows and columns in the image, a colour map, etc. 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 refers to, and should be located in the same directory as the source file. The HDR structure is simple; it is an ASCII text file containing eleven lines. You can open an HDR file using any ASCII text editor. Atoll supports the following objects in bil format;

Digital Terrain Model (16 bits) Clutter heights (16 bits) Clutter classes and traffic density maps (8 bits) Raster images (1, 4, 8, 24 bits) Population maps (8, 16, 32 bits) Other generic geographic data (8, 16, 32 bits) Path loss or field value matrices (16 bits)

X.1.1 HEADER FILE (.HDR)

X.1.1.a DESCRIPTION The header file is a text file that describes how data are organised in the .bil file. The header file is made of rows, each row having the following format: keyword value where ‘keyword’ corresponds to an attribute type, and ‘value’ defines the attribute value. Keywords required by Atoll are described below. Other keywords are ignored. nrows: number of rows in the image. ncols: number of columns in the image. nbands: number of spectral bands in the image, (1 for DTM data and 8 bit pictures). nbits: number of bits per pixel per band; 16 for DTMs (altitude in metres), 8 for clutter classes file (clutter code), 16 for path loss matrices (path loss in dB, field value in dBm, dBµV and DBµV/m). byteorder: byte order in which image pixel values are stored. Accepted values are M (Motorola byte order) or I (Intel byte order). layout: must be ‘bil’. skipbytes: byte to be skipped in the image file in order to reach the beginning of the image data. Default value is 0. ulxmap: x coordinate of the centre of the upper-left pixel. ulymap: y coordinate of the centre of the upper-left pixel. xdim: x size in metre of a pixel. ydim: y size in metre of a pixel. Four additional keywords may be optionally managed. datatype: type of data read (in addition to the length)

It can be: I1 Integer 1 bit I2 Integer 2 bits I4 Integer 4 bits I8 Integer 8 bits I16 Integer 16 bits I32 Integer 32 bits R32 Real 32 bits R64 Real 64 bits RGB24 Integer 3 colour components on 24 bits



By default, integer data types are chosen with respect to the pixel length (nbits). valueoffset: Real value to be added to the read value (Vread) valuescale: scaling factor to be applied to the read value So, we have tvalueoffsevaluescaleVV read +×= nodatavalue: value corresponding to “NO DATA” The value –9999 is used by default.

X.1.1.b SAMPLES Here, the data resolution is 20m.

X.1.1.b.i Digital Terrain Model nrows 1500 ncols 1500 nbands 1 nbits 16 byteorder M layout bil skipbytes 0 ulxmap 975000 ulymap 1891000 xdim 20.00 ydim 20.00

X.1.1.b.ii Clutter classes file nrows 1500 ncols 1500 nbands 1 nbits 8 byteorder M layout bil skipbytes 0 ulxmap 975000 ulymap 1891000 xdim 20.00 ydim 20.00

X.1.2 .BIL FILE bil files are usually binary files without header. Data are stored starting from the Northwest corner of the area. The skipbytes value defined in the header file allows to skip records if the data do not start at the beginning of the file.

X.2 TIFF FORMAT Tagged Image File Format graphics filter supports all image types (monochrome, greyscale, palette colour, and RGB full colour images) and packbit, LZW or fax group 3-4 compressions. The tifF files are not systematically geo-referenced. 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 refers to. Atoll will then use the .tfw file during the import procedure for an automatic geo-referencing. 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 look something like this: Atoll supports the following objects in tifF format:

• Digital Terrain Model (16 bits) • Clutter heights (16 bits) • Clutter classes and traffic density maps (8 bits)

File formats


• Raster images (1, 4, 8, 24 bits) • Population maps (8, 16, 32 bits) • Other generic geographic data (8, 16, 32 bits)

X.2.1 HEADER FILE DESCRIPTION (.TFW) The header file is a text file that describes how data are organised in the .tif file. The header file is made of rows, each row having the following description: Line Description 1 x dimension of a pixel in map units 2 amount of translation 3 amount of rotation 4 negative of the y dimension of a pixel in map units 5 x-axis map coordinate of the centre of the upper-left pixel 6 y-axis map coordinate of the centre of the upper-left pixel

X.2.2 SAMPLE

X.2.2.a CLUTTER CLASSES FILE 100.00 0.00 0.00 -100.00 60000.00 2679900.00

X.3 PLANET FORMAT The Planet geographic data are described by a set of files grouped in a Planet directory. The directory structure depends on the geographic data type: Atoll supports the following objects in Planet format:

• Digital Terrain Model (16 bits) • Clutter class maps (16 bits) • Raster images (1, 4, 8 and 24 bits) • Vector data • Text data

X.3.1 DTM FILE

X.3.1.a DESCRIPTION The DTM directory consists of three files; the height file and two other files detailed below:

- The index file structure is simple; it is an ASCII text file that holds position information about the file. It contains five columns. You can open an index file using any ASCII text editor. The format of the index file is as follows:

Field Acceptable values Description

File name Text Name of file referenced by the index file East min Float x-axis map coordinate of the centre of the upper-left pixel in meters East max Float x-axis map coordinate of the centre of the upper-right pixel in meters North min Float y-axis map coordinate of the centre of the lower-left pixel in meters North max Float y-axis map coordinate of the centre of the upper-left pixel in meters

Square size Float Dimension of a pixel in meters

- The projection file provides information about the projection system used. This file is optional. It is an ASCII text file with four lines maximum.



Line Description Spheroid

Zone Projection

Central meridian Latitude and longitude of projection central meridian and equivalent x and y coordinates in meters (optional)

X.3.1.b SAMPLE Index file associated with height file (DTM data). sydney1 303900 343900 6227900 6267900 50 Projection file associated with height file (DTM data). Australian-1965 56 UTM 0 153 500000 10000000

X.3.2 CLUTTER CLASS FILES

X.3.2.a DESCRIPTION The Clutter directory consists of three files; the clutter file and two other files detailed below:

- The menu file, an ASCII text file, defines the feature codes for each type of clutter. It consists of as many lines (with the following format) as there are clutter codes in the clutter data files. This file is optional.

Field Type Description

Clutter-code Integer (>1) Identification code for clutter class Feature-name Text (up to 32 characters in length) Name associated with the clutter-code. It may contain spaces

- The index file gives clutter spatial references. The structure of clutter index file is the same as the structure of DTM index file.

X.3.2.b SAMPLE Menu file associated with the clutter file: 1 open 2 sea 3 inlandwater 4 residential 5 meanurban 6 denseurban 7 buildings 8 village 9 industrial 10 openinurban 11 forest 12 parks 13 denseurbanhigh 14 blockbuildings 15 denseblockbuild 16 rural 17 mixedsuburban

File formats


X.3.3 VECTOR FILES

X.3.3.a DESCRIPTION Vector data comprises terrain features such as coastlines, roads, etc. Each of these features is stored in a separate vector file. Four types of files are used, the vector file, where x and y coordinates of vector paths are stored, and three other files detailed below:

- The menu file, an ASCII text file, lists the vector types stored in the database. The menu file is composed of one or more records with the following structure:


Vector type code Integer > 0 Identification code for the vector type Vector type name Text (up to 32 characters in length) Name of the vector type

The fields are separated by space character.

- The index file, an ASCII text file, lists the vector files and associates each vector file with one vector type, and optionally with one attribute file. The index file consists of one or more records with the following structure:


Vector file name Text (up to 32 characters in length) Name of the vector file Attribute file name Text (up to 32 characters in length) Name of attribute file associated with the vector file

(optional) Dimensions Real vector file eastmin: minimum x-axis coordinate of all vector

path points in the vector file vector file eastmax: maximum x-axis coordinate of all vector path points in the vector file vector file northmin: minimum y-axis coordinate of all vector path points in the vector file vector file northmax: maximum y-axis coordinate of all vector path points

Vector type name Text (up to 32 characters in length) Name of the vector type with which the vector file is associated. This one must match exactly a vector type name field in the menu file.

The fields are separated by space character.

- The attribute file stores the height and description properties of vector paths. This file is optional.

X.3.3.b SAMPLE Index file associated with the vector files sydney1.airport 313440 333021 6239426 6244784 airport sydney1.riverlake 303900 342704 6227900 6267900 riverlake sydney1.coastline 322837 343900 6227900 6267900 coastline sydney1.railways 303900 336113 6227900 6267900 railways sydney1.highways 303900 325155 6240936 6267900 highways sydney1.majstreets 303900 342770 6227900 6267900 majstreets sydney1.majorroads 303900 342615 6227900 6267900 majorroads

X.3.4 IMAGE FILES The image directory consists of two files, the image file with .tif extension and an index file with the same structure as the DTM index file structure.

X.3.5 TEXT DATA FILES The text data directory consists of:

- The text data files, ASCII text files with the following format:

Airport 637111.188 3094774.00



Airport 628642.688 3081806.25

Each file contains a line of text followed by easting and northing of that text, etc.

- The index file, an ASCII text file, stores the position of each text file. It consists of one or more records with the following structure:


File name Text (up to 32 characters in length) Filename of the text data file East Min Real Minimum x-axis coordinate of all points listed in the text data file East Max Real Maximum x-axis coordinate of all points listed in the text data file North Min Real Minimum y-axis coordinate of all points listed in the text data file North Max Real Maximum y-axis coordinate of all points listed in the text data file

Text feature Text (up to 32 characters in length) This field is omitted in case no menu file is available. Separator used is a blank character.

railwayp.txt -260079 693937 2709348 3528665 Railway_Station airport.txt -307727 771663 2547275 3554675 Airport ferryport.txt 303922 493521 2667405 3241297 Ferryport

- The menu file, an ASCII text file, contains the text features. This file is optional. 1 Airport 2 Ferryport 3 Railway_Station

X.4 MNU FORMAT

X.4.1 DESCRIPTION mnu file is useful when importing clutter classes and traffic files in .tif and .bil formats. It gives the correspondence between the clutter (or traffic) code and the class name. It is a text file named as the clutter (or traffic) file with .mnu extension. It must be stored at the same location as the clutter (or traffic) file. It has the same structure as the menu file used in the Planet format.

Field Type Description Class code Integer > 0 Identification code for the clutter (or traffic) class Class name Text (up to 50 characters in length) Name of the clutter (or traffic) class. It may contain spaces.

Separator used can either be a blank or a tab.

X.4.2 SAMPLE mnu file associated to a clutter classes file. 0 none 1 open 2 sea 3 inland_water 4 residential 5 meanurban

X.5 EXTERNALISED PROPAGATION RESULTS FORMAT Propagation results, i.e. the path loss matrices, may be stored in an external folder. This folder consists of a dBASE III based file named ‘pathloss.dbf’ that contains calculation parameters of all the transmitters considered and one file (or two when calculating main and extended path loss matrices) per transmitter taken into account. This is a binary file with .los extension and contains the path loss values for a transmitter. Note: Each transmitter path loss matrix is calculated on the area where calculation radius intersects the computation

zone (see: Computation zone).

File formats


X.5.1 DBF FILE dBASE III file (pathloss.dbf) has a standard dbf format described below. Its content can be checked by opening it in MS-Access. The format is detailed hereafter.

X.5.1.a DBF FILE FORMAT For general information, the format of .dbf files in any Xbase language is described. Following notations are used in tables:

FS = FlagShip D3 = dBaseIII+ Fb = FoxBase D4 = dBaseIV Fp = FoxPro D5 = dBaseV CL = Clipper

X.5.1.a.i dbf Structure Byte Description 0..n .dbf header (see next part for size, byte 8) n+1

1st record of fixed length (see next parts) 2nd record (see next part for size, byte10) … last record

If dbf is not empty

last optional: 0x1a (eof byte)

X.5.1.a.ii dbf Header (variable size depending on field count) Byte Size Contents Description Applies for (supported by) 00 1 0x03 plain .dbf FS, D3, D4, D5, Fb, Fp, CL 0x04 plain .dbf D4, D5 (FS) 0x05 plain .dbf D5, Fp (FS) 0x43 with .dbv memo var size FS 0xB3 with .dbv and .dbt memo FS 0x83 with .dbt memo FS, D3, D4, D5, Fb, Fp, CL 0x8B with .dbt memo in D4 format D4, D5 0x8E with SQL table D4, D5 0xF5 with .fmp memo Fp 01 3 YYMMDD Last update digits All 04 4 ulong Number of records in file All 08 2 ushort Header size in bytes All 10 2 ushort Record size in bytes All 12 2 0,0 Reserved All 14 1 0x01 Begin transaction D4, D5 0x00 End Transaction D4, D5 0x00 ignored FS, D3, Fb, Fp, CL 15 1 0x01 Encryptpted D4, D5 0x00 normal visible All 16 12 0 (1) multi-user environment use D4,D5 28 1 0x01 production index exists Fp, D4, D5 0x00 index upon demand All 29 1 n language driver ID D4, D5 0x01 codepage437 DOS USA Fp 0x02 codepage850 DOS Multi ling Fp 0x03 codepage1251 Windows ANSI Fp 0xC8 codepage1250 Windows EE Fp 0x00 ignored FS, D3, Fb, Fp, CL 30 2 0,0 reserved All 32 n*32 Field Descriptor, (see next paragraph) all +1 1 0x0D Header Record Terminator all

• Field descriptor array in dbf header (32 bytes for each field)

Byte Size Contents Description Applies for (supported by) 0 11 ASCI field name, 0x00 termin all 11 1 ASCI field type (see next paragraph) all 12 4 n,n,n,n Fld address in memory D3 n,n,0,0 offset from record begin Fp 0,0,0,0 ignored FS, D4, D5, Fb, CL 16 1 byte Field length, bin (see next paragraph) all \ FS,CL: for C field type 17 1 byte decimal count, bin all / both used for fld lng 18 2 0,0 reserved all



20 1 byte Work area ID D4, D5 0x00 unused FS, D3, Fb, Fp, CL 21 2 n,n multi-user dBase D3, D4, D5 0,0 ignored FS, Fb, Fp, CL 23 1 0x01 Set Fields D3, D4, D5 0x00 ignored FS, Fb, Fp, CL 24 7 0..0 reserved all 31 1 0x01 Field is in .mdx index D4, D5 0x00 ignored FS, D3, Fb, Fp, CL

• Field type and size in dbf header, field descriptor (1 byte)

Size Type Description/Storage Applies for (supported by) C 1..n Char ASCII (OEM code page chars)

rest= space, not \0 term. all

n = 1..64kb (using deci count) FS n = 1..32kb (using deci count) Fp, CL n = 1..254 all D 8 Date 8 ASCII digits (0..9) in the YYYYMMDD format all

F 1..n Numeric ASCII digits (-.0123456789) variable pos. of float.point n = 1..20

FS, D4, D5, Fp

N 1..n Numeric ASCII digits (-.0123456789) fix posit/no float.point all

n = 1..20 FS, Fp, CL n = 1..18 D3, D4, D5, Fb L 1 Logical ASCII chars (YyNnTtFf space) FS, D3, Fb, Fp, CL ASCII chars (YyNnTtFf ?) D4, D5 (FS)

M 10 Memo 10 digits repres. the start block posit. in .dbt file, or 10 spaces if no entry in memo all

V 10 Variable

Variable, bin/asc data in .dbv 4bytes bin= start pos in memo 4bytes bin= block size 1byte = subtype 1byte = reserved (0x1a) 10spaces if no entry in .dbv

FS

P 10 Picture binary data in .ftp structure like M Fp

B 10 Binary binary data in .dbt structure like M D5

G 10 General OLE objects structure like M D5, Fp

2 2 short int binary int max +/- 32767 FS 4 4 long int binary int max +/- 2147483647 FS 8 8 double binary signed double IEEE FS

X.5.1.a.iii Each dbf record (fix length) Byte Size Description Applies for (supported by) 0 1 deleted flag "*" or not deleted " " all

1…n 1… x-times contents of fields, fixed length, unterminated. For n, see (2) byte 10…11 All

X.5.1.b DBF FILE CONTENT dbf file provides information that is needed to check validity of each path loss matrix.

Field Type Description FILE_NAME Text Name of .los file

MODEL_NAME Text Name of propagation model used to calculate path loss

MODEL_SIG Text

Signature (identity number) of model used in calculations. You may check it in the propagation model properties (General tab) . The Model_SIG is used for the purpose of validity. A unique Model_SIG is assigned to each propagation model. When model parameters are modified, the associated model ID changes. This enables Atoll to detect path loss matrix invalidity. In the same way, two identical propagation models in different projects do not have the same model ID1.

ULXMAP Float X-coordinate of the top-left corner of the path loss matrix upper-left pixel

1 In order to benefit from the calculation sharing feature, users must retrieve the propagation models from the same central database. This can be done using the Open from database command for a new document or the Refresh command for an existing one. Otherwise, Atoll generates different model_ID (even if same parameters are applied on the same kind of model) and calculation sharing become unavailables due to inconsistency.

File formats


ULYMAP Float Y-coordinate of the top-left corner of the path loss matrix upper-left pixel RESOLUTION Float Resolution of path loss matrix in metre

NROWS Float Number of rows in path loss matrix NCOLS Float Number of columns in path loss matrix

FREQUENCY Float Frequency band TILT Float Transmitter antenna mechanical tilt

AZIMUTH Float Transmitter antenna azimuth TX_HEIGHT Float Transmitter height in metre TX_POSX Float X-coordinate of the transmitter TX_POSY Float Y-coordinate of the transmitter ALTITUDE Float Ground height above sea level at the transmitter in metre

RX_HEIGHT Float Receiver height in metre

ANTENNA_SI Float Logical number referring to antenna pattern. Antennas with the same pattern will have the same number.

MAX_LOS Float Maximum path loss stated in 1/16 dB This information is used, when no calculation radius is set, to check the matrix validity.

CAREA_XMIN Float Lowest x-coordinate of centre pixel located on the calculation radius2 CAREA_XMAX Float Highest x-coordinate of centre pixel located on the calculation radius CAREA_YMIN Float Lowest y-coordinate of centre pixel located on the calculation radius CAREA_YMAX Float Highest y-coordinate of centre pixel located on the calculation radius WAREA_XMIN Float Lowest x-coordinate of centre pixel located in the computation zone3 WAREA_XMAX Float Highest x-coordinate of centre pixel located in the computation zone WAREA_YMIN Float Lowest y-coordinate of centre pixel located in the computation zone WAREA_YMAX Float Highest y-coordinate of centre pixel located in the computation zone

LOCKED Boolean Locking status

0: path loss matrix is not locked 1: path loss matrix is locked.

INC_ANT Boolean Atoll indicates if losses due to the antenna pattern are taken into account in the path loss matrix.

0: antenna losses not taken into account 1: antenna losses included

X.5.2 LOS FILE The data file is a 16 bits binary row file organized in a standard row-column structure. It contains an integer path loss value, with a 1/16 dB unit. Data are stored starting from the southwest to the northeast corner of the area.

X.6 INTERFERENCE HISTOGRAMS FORMAT Interference histograms required by automatic frequency planning tools can be imported and exported.

X.6.1 EXPORT FORMAT When exporting interference histograms, Atoll creates two ASCII text files in a specified directory: xxx.dct and xxx.clc (xxx is the user-specified name).

X.6.1.a DCT FILE

X.6.1.a.i Description The .dct file is divided into two parts:

- The first part is a header used for format identification. It must be:

# Forsk Calculation Results Dictionary File. # Version 1.0, Tab separated format. Commented lines start with # .

- The second part provides information about transmitters taken into account in AFP. The lines after the header are considered as comments if they start with the symbol “#”. If not, they must have the following format: <Column1><tab><Column2><newline>

2 These coordinates enable Atoll to determine the area of calculation for each transmitter. 3 These coordinates enable Atoll to determine the rectangle including the computation zone.



Column name Type Description Column1 Transmitter name Text Name of the transmitter Column2 Transmitter Identifier Integer Identification number of the transmitter

One transmitter per line is described separated with a tab character.

X.6.1.a.ii Sample # Forsk Calculation Results Dictionary File. # Version 1.0, Tab separated format. Commented lines start with # . # Fields are: ##-------------#-------------# #| Transmitter | Transmitter | #| Name | Identifier | ##-------------#-------------# Site0_0 1 Site0_1 2 Site0_2 3 Site1_0 4 Site1_1 5 Site1_2 6 Site2_0 7 Site2_1 8 ….

X.6.1.b CLC FILE

X.6.1.b.i Description The .clc file consists of two parts:

- The first part is a header used for format identification. It must be:

# Forsk Calculation Results Data File. # >Version 1.0, Tab separated format. Commented lines start with # .

- The second part details interference histogram of each interfered subcell-interferer subcell pair. The lines after the header are considered as comments if they start with the symbol “#”. If not, they must have the following format: <Column1><tab><Column2><tab><Column3><tab><Column4><tab><Column5><newline>

The 5 tab-separated columns are defined in the table below:

Column name Description

Column1 Interfered Transmitter Identification number of the interfered transmitter. If the column is empty, its value is identical to the one of the line above.

Column2 Interfering transmitter Identification number of the interferer transmitter. If the column is null, its value is identical to the one of the line above.

Column3 Interfered TRX type Interfered subcell. If the column is null, its value is identical to the one of the line above.

Column4 C/I threshold C/I value. This column cannot be null.

Column5 Probability C/I > Threshold Probability to have C/I ≥ the value specified in column 4 (C/I threshold). This field must not be empty.

Notes: 1. The interferer TRX type is not specified. In fact, the subcells of the interferer transmitter differ by their power

offsets. If the power offset of a subcell is x with respect to the BCCH, then its interference C/I histogram will be shifted by x with respect to the BCCH interference histogram. It contains no further information; therefore, the interferer TRX type is always BCCH.

2. The columns 1, 2, and 3 must be defined only in the first line of each histogram. 3. For each interfered subcell-interferer subcell pair, Atoll saves probabilities for several C/I values (between 6 and

24 values). Five of them are fixed; probabilities are computed for C/I values equal to –9, 1, 8, 14 and 22dB. Then, between each fixed C/I value, you can have up to three additional values (this number depends on the probability variation between the fixed values). The C/I values have 0.5dB accuracy and probability is calculated with an accuracy of 0.004.

File formats


X.6.1.b.ii Samples # Forsk Calculation Results Data File. # Version 1.0, Tab separated format. Commented lines start with # . # Remark: C/I results do not incorporate power offset values. # Fields are: ##------------#------------#------------#-----------#------------------# #| Interfered | Interfering| Interfered | C/I | Probability | #| Transmitter| Transmitter| Trx type | Threshold | C/I >= Threshold | ##------------#------------#------------#-----------#------------------# 1 2 BCCH -9.5 1 -9 1 -6 1 -3 1 0 0.996 1 0.992 2 0.992 5 0.98 6 0.98 8 0.968 9 0.96 11 0.936 12 0.912 14 0.872 15 0.848 16 0.832 17 0.808 22 0.712 23 0.696 25 0.644 26 0.556 1 2 TCH -9.5 1 -9 1 -6 1 -3 1 0 0.996 1 0.992 2 0.992 5 0.98 6 0.98 8 0.968 9 0.96 11 0.936 12 0.912 14 0.872 15 0.848 16 0.832 17 0.808 22 0.712 23 0.696 25 0.644 26 0.556

X.6.2 IMPORT FORMAT Two import formats are supported. You may import interference histograms with:

• Standard format: same as export format. Note: When importing interference histograms with standard format, you must specify the .clc file to be imported. Atoll

looks for the associated .dct file in the same directory and uses it to decode transmitter identifiers. If this file is unavailable, Atoll assumes that the transmitter identifiers are the transmitter names. In this case, the columns 1 and 2 of the .clc file must contain the names of the interfered and interferer transmitters instead of their identification numbers.

• Simplified format



In this case, there is only a .clc file containing co-channel and adjacent channel interference probabilities specified for each interfered transmitter – interferer transmitter pair. There is only one set of values for all the subcells of the interfered transmitter. Each line must have the following format :

<Column1><tab><Column2><tab><Column3><tab><Column4><newline>

The 4 tab-separated columns are defined in the table below:

Column name Description Column1 Interfered transmitter Name of the interfered transmitter. Column2 Interfering transmitter Name of the interferer transmitter.

Column3 Co-channel interference probability

Probability of having ( )reqTCHBCCHICMaxIC

,≤ for BCCH and TCH subcells.

Probability of having INNERTCHreqICIC _≤ for TCH_INNER subcell.

Column4 Adjacent channel interference probability

Probability of having ( ) FICMaxIC reqTCHBCCH−≤

, for BCCH and TCH subcells.

Probability of having FICIC INNERTCHreq −≤ _ for TCH_INNER subcell.

reqIC corresponds to the required C/I threshold. This parameter is defined for each subcell.

F is the adjacent channel protection level. Note: The lines starting with the symbol “#” are considered as comments.

X.6.2.a SAMPLES Site0_1 Site0_2 0.01 0.001 Site0_2 Site0_3 0.98 0.97 Site0_3 Site0_2 0.91 0.21 Site0_3 Site0_1 0.15 0.15 Site0_1 Site0_3 0.9 0.2 Notes: 1. No validity check is carried out when importing an interference histogram file. 2. Atoll only imports interference histograms related to loaded transmitters.

C H A P T E R 11

Calculations This chapter provides information on path loss matrices, propagation models, antenna pattern modelling and shadowing modelling.

11


104 Unauthorized reproduction or distribution of this document is prohibited Forsk 2004

Calculations

Forsk 2004 Unauthorized reproduction or distribution of this document is prohibited 105

XI CALCULATIONS

XI.1 OVERVIEW Three kinds of predictions are available in Atoll:

- Point analysis enables you to visualise transmitter-receiver profile and to get predictions for a user-defined receiver in real time anywhere on a geographic map (Point analysis window: Profile tab).

- Coverage studies consider each bin of calculation areas as a potential receiver you can define. Therefore, covered bins correspond to areas where a criterion on the predicted received signal is fulfilled.

- Point analysis based on path loss matrices enables you to get parameters derived from predicted values in coverage studies (field received, path loss, C/I, UMTS parameters) for a receiver anywhere inside a calculation area (Point analysis window: Reception, Interference, AS analysis tabs).

An overview of different analysis methods is presented in the table below:

Coverage studies Point analysis Point analysis based on path loss matrices

Any study Profile Reception, Results, Interference, AS analysis

Receiver position At the centre of each calculation bin within

calculation areas

Anywhere. Even beyond computation zone Anywhere inside the calculation areas

Calculation Path loss matrix calculation Real time No calculation: result coming from path

loss matrices

Profile extraction Radial except when using SPM Systematic Method used for coverage studies: radial

except when using SPM

Result One value inside a calculation bin

Different values inside a calculation bin One value inside a calculation bin

* When using SPM, you can choose either radial or systematic calculation option. Notes: 1. In coverage studies, Atoll calculates path loss for every bin within calculation areas. However, only results on

calculation bins inside the computation zone are displayed. 2. Profile point analysis is calculated in real time. Therefore, prediction is always consistent with the network. On the

other hand, if you modify any parameter (radio or geo), which may make matrices invalid, consider updating the matrices before using point analysis based on path loss matrices.

3. Due to different calculation methods, you can get different results at a same point when performing a point analysis in profile or reception mode.

In any case, prediction is performed in three steps: 1st step: First of all, Atoll calculates the path loss ( Lpath ), using the selected propagation model.

RXTx antantelpath LLLL ++= mod

elLmod is the loss on the transmitter-receiver path calculated through the propagation model. elLmod value depends on the selected propagation model.

TxantL is the transmitter antenna attenuation (from antenna patterns).

RxantL is the receiver antenna attenuation ( 0=RxantL ) (from antenna patterns).

Notes: 1. In any project, Atoll considers that the receiver antenna is in the transmitter antenna axis. Therefore, the receiver

antenna attenuation is supposed to be zero. 2. Transmitter antenna attenuation may not be considered in this step. It depends on propagation model provider,

who may choose to include this parameter in pathL calculation. However, all the propagation models available in

Atoll calculate pathL by considering transmitter antenna attenuation. 2nd step: Atoll evaluates a shadowing margin, MShadowing , from the user-defined model standard deviation at the receiver and the cell edge coverage probability .



Note: For a cell edge coverage probability of 50%, the shadowing margin is always zero. In this case, Atoll still works as above. 3rd step: Then, Atoll determines the prediction criterion and displays coverage.

For a signal level study, The signal level at the receiver ( cPRe ) is calculated. We have (in dBm):

( )RxantShadowingpathrec LGMLEIRPP Rx

−+−−= Where TxantTx LGPEIRP

Tx−+=

EIRP is the effective isotropic radiated power of the transmitter.

TxP is the transmitter power.

TxantG is the transmitter antenna gain.

TxL are transmitter losses.

ShadowingM is the shadowing margin.

RxL are receiver losses.

RxantG is the receiver antenna gain.

Notes: 1. In UMTS, CDMA2000 and IS95-CDMA documents, PilotTx PP = and DLtotalTx LL −= . 2. In UMTS, CDMA2000 and IS95-CDMA documents, Atoll considers that

RxantG and RxL equal zero when calculating the received signal level (in point analysis, Profile and Reception tabs, and in common coverage studies such as Coverage per transmitter, Coverage by field level, Overlapping).

3. In GSM_EGPRS documents, DLtotalTx LL −= . 4. In GSM_EGPRS documents, receiver is equipped with an antenna with zero gain.

The prediction is performed for a user-defined cell edge coverage probability (x%). This means that the measured criterion exceeds the predicted criterion for x% of time. The prediction is reliable during x% of time. Note: In case of interference studies, only signal from interfered transmitter (C) is downgraded by the shadowing margin.

We consider that interference value (I) is not altered by the shadowing margin.

XI.2 PATH LOSS MATRICES Atoll is able to calculate two path loss matrices per transmitter, a first matrix over a smaller radius computed with a high resolution and a propagation model, and a second matrix over a larger radius computed with a low resolution and another propagation model. To be considered for calculations, a transmitter must fulfil the following conditions:

- It must be active, - It must satisfy filter criteria defined in the Transmitters folder, And - It must have a calculation area.

In the rest of the document, a transmitter fulfilling the conditions detailed above will be called TBC transmitter. The path loss matrix size of a TBC transmitter depends on its calculation area. Atoll determines a path loss value ( Lpath ) on each calculation bin (calculation bin is defined by the resolution) of the calculation area of the TBC transmitter. You may have one or two path loss matrices per TBC transmitter.

Calculations


XI.2.1 CALCULATION AREA DETERMINATION Transmitter calculation area is a rectangle or a square depending on transmitter calculation radius and the computation zone. Calculation radius enables Atoll to define a square around the transmitter. One side of the square equals twice the entered calculation radius. Hence, transmitter calculation area corresponds to the intersection area between its calculation square and the rectangle containing the computation zone.

Calculation area

XI.2.2 CALCULATE – FORCE CALCULATION COMPARISON

XI.2.2.a CALCULATE The Calculate feature (F7) enables you:

1. To calculate prediction studies The first time you click on Calculate (no path loss matrices exist), Atoll computes path loss matrices for each TBC transmitter. Then, it calculates created and unlocked coverage prediction studies inside the computation zone.

2. To check result validity and update calculations If calculations have been performed once and you have changed some parameters such as radio data or calculation area, Atoll automatically detects path loss matrices to be recalculated. These are either one or several path loss matrices that become invalid due to certain modifications. Then Atoll calculates the prediction study, or the just prediction study if matrices are still valid.

XI.2.2.b FORCE CALCULATION With the Force calculation feature (Ctrl+F7), Atoll deletes all the path loss matrices even if they are valid, recalculates them and then updates the results of prediction studies. Note: Geographic data (DTM, clutter) modification makes path loss matrices invalid. However, Atoll does not detect this

invalidity just by using Calculate. Therefore, to update calculations, you must click on the Force calculation command.

____ Computation zone. - - - - Rectangle containing the computation zone. - - - - Calculation area defined (square).

Transmitter

Calculation area: real area for which Atoll calculates path losses.



XI.2.3 MATRIX VALIDITY Atoll manages path loss matrix validity transmitter by transmitter, even in case of transmitters with two path loss matrices (main and extended matrices). Therefore, even if only one path loss matrix of the transmitter is invalid, Atoll will recalculate both of them. All the geographic data modifications and some radio data changes can make matrices invalid. This table lists these modifications and also changes that have an impact only on prediction studies.

Modification Matrix validity Impact on Calculate Force calculation

Frequency Invalid Path loss matrices Sufficient Not necessaryAntenna* coordinates (site coordinate: X

and Y, Dx and Dy) Invalid Path loss matrices Sufficient Not necessary

Antenna* height Invalid Path loss matrices Sufficient Not necessaryAntenna* pattern Invalid Path loss matrices Sufficient Not necessary

Down tilt* Invalid Path loss matrices Sufficient Not necessaryAzimuth* Invalid Path loss matrices Sufficient Not necessary

% Power (when there is other antennas) Invalid Path loss matrices Sufficient Not necessarySite position Invalid Path loss matrices Sufficient Not necessary

Grid resolution (main or/and extended) Invalid Path loss matrices Sufficient Not necessaryPropagation model (main or/and

extended) Invalid Path loss matrices Sufficient Not necessary

Propagation model parameters Invalid Path loss matrices Sufficient Not necessaryCalculation areas

1. Calculation areas are smaller Valid Prediction study Sufficient Not necessary

Calculation areas 2. Calculation areas become higher Invalid Path loss matrices Sufficient Not necessary

Receiver height Invalid Path loss matrices Sufficient Not necessaryReceiver losses Valid Prediction study Sufficient Not necessaryReceiver gain Valid Prediction study Sufficient Not necessary

Receiver antenna Valid because 0=RxantL Prediction study Sufficient Not necessary

Geographic layer order Invalid Path loss matrices Insufficient Necessary Geographic file resolution Invalid Path loss matrices Insufficient Necessary

New DTM map Invalid Path loss matrices Insufficient Necessary New clutter class edition Invalid Path loss matrices Insufficient Necessary

Coverage study resolution Valid Prediction study Sufficient Not necessaryCell edge coverage probability Valid Prediction study Sufficient Not necessary

Coverage study conditions Valid Prediction study Sufficient Not necessaryCoverage study display options Valid Prediction study Sufficient Not necessary

*Modifications of all the parameters relating to main and other antennas make matrix invalid. Practical advice: Calculate or Force calculation? If you modify radio data or calculation areas, use the Calculate button. On the other hand, if you change geographic data, it is necessary to use Force calculation. Practical advice: Calculation area management When performing prediction studies, it is recommended to follow this methodology to minimise recalculations: 1st step: Calculate without computation zone. 2nd step: Draw a computation zone and calculate. 3rd step: Decrease the calculation radius and calculate.

Calculations


XI.3 PATH LOSS CALCULATIONS

XI.3.1 GROUND ALTITUDE DETERMINATION Atoll determines reception and transmission site altitude from Digital Terrain Model map. The method used to evaluate site altitude is based on a bilinear interpolation. It is described below. Let us suppose a site S located inside a bin. Atoll knows the altitudes of four bin vertices, S’1, S’’1, S’2 and S’’2, from the DTM file.

S

S’1

S’2 S ‘’2

S ‘’1

1st step: Atoll draws a vertical line through S. This line respectively intersects (S’1,S’’1) and (S’2, S’’2) lines at S1 and S2.

S

S1

S2S’2 S"2

S’1 S"1

2nd step: Atoll determines the S1 and S2 altitudes using a linear interpolation method.

S"1 S’1

S1

S"2

S’2S2

3rd step: Atoll performs a second linear interpolation to evaluate the S altitude.

S2S1

S

XI.3.2 CLUTTER DETERMINATION Some propagation models need clutter class and clutter height as information at receiver or along a transmitter-receiver profile.

XI.3.2.a CLUTTER CLASS Atoll uses clutter classes file to determine the clutter class.

XI.3.2.b CLUTTER HEIGHT To evaluate the clutter height, Atoll uses clutter heights file if available in the .atl document; clutter height of a site is the height of the nearest point in the file.



Example: Let us suppose a site S. In the clutter heights file, Atoll reads clutter heights of four points around the site, S’1, S’’1, S’2 and S’’2. Here, the nearest point to S is S”2; therefore Atoll takes the S”2 clutter height as clutter height of S.

S

S’1

S’2 S ‘’2

S ‘’1

If you do not have any clutter height file, Atoll takes clutter height information in clutter classes file. In this case, clutter height is an average height related to a clutter class.

XI.3.3 MULTI–LAYER MANAGEMENT DTM, clutter and traffic may be taken into account in calculations (prediction, network optimisation). DTM, Clutter and Traffic folders can contain several objects representing different areas of the map or common parts of the map with identical or different resolutions. Atoll considers only the visible data in calculations, for each folder (DTM, Clutter, Traffic). Inside a folder, What You See Is What Is Used. Thus, in each folder, you must place the objects with the smallest size and the best resolution on top. For example, you import two clutter files and both files have no geographical overlap, then both will be considered in calculation. If there is an overlap, then for the overlapping region, the file placed on top will be taken into account and not the file at the bottom. So, if you have a high-resolution small area on your clutter (two files), it is necessary to put the high-resolution file on top for it to be taken into account for calculation.

XI.3.3.a EXAMPLE 1: TWO DTM MAPS REPRESENTING DIFFERENT AREAS Let us consider two imported DTM files:

- The first one called “DTM 1” represents an area with a 50m resolution. - The second one called “DTM 2” shows another area with a 20m resolution.

Here, the DTM data taken into account in calculations do not depend on their order in the DTM folder (Explorer window). The file order does not really matter because there is no overlap.

Explorer window Work space Case 1 DTM

- DTM 2 (20m) - DTM 1 (50m)

20m 50m

Case 2 DTM

- DTM 1 (50m) - DTM 2 (20m)

20m 50m

Multi-layer management in calculations – two DTM maps representing different areas

Calculations


XI.3.3.b EXAMPLE 2: CLUTTER CLASSES AND DTM MAPS REPRESENTING THE SAME AREA Let us consider two imported maps:

- A clutter classes map called “Clutter”. - A DTM map called “DTM”.

Whatever the chosen order (case 1: clutter classes map on top of the DTM map or case 2: DTM map on top of the clutter classes map), Atoll always uses the clutter and DTM data in calculations.

Explorer window Work space Case 1 Clutter classes

- Clutter DTM

- DTM

clutter

Case 2 DTM

- DTM Clutter classes

- Clutter

DEM

Multi-layer management in calculations – Clutter and DTM maps representing the same area

XI.3.3.c EXAMPLE 3: TWO CLUTTER CLASS MAPS REPRESENTING A COMMON AREA Let us consider two imported clutter classes files:

- The first one called “Clutter 1” represents a large area with a 50m resolution. - The second one called “Clutter 2” shows a smaller area with a 20m resolution already represented on the first map.

According to the map order in the Clutter folder (Explorer window), Atoll does not take into account the same clutter information:

- In the first case, Clutter 2 is on the top of Clutter 1: Atoll sees both maps, it will consider clutter data coming from Clutter 2 in the definition area of clutter 2 and Clutter 1 elsewhere. - In the second case, Clutter 1 is on the top of Clutter 2: Atoll only sees Clutter 1. Therefore, just Clutter 1 information is used.

Explorer window Work space Case 1 Clutter classes

- Clutter 2 (20m) - Clutter 1 (50m)

20m

50m



Case 2 Clutter classes

- Clutter 2 (50m) - Clutter 1 (20m)

50m

Multi-layer management in calculations – two clutter maps representing the same area

XI.3.4 GEOGRAPHIC PROFILE EXTRACTION Geographic profile extraction is needed in order to calculate diffraction losses. Profiles can be based on DTM only or on DTM and clutter both. In fact, it depends on the selected propagation model.

XI.3.4.a EXTRACTION METHODS

XI.3.4.a.i Radial extraction Atoll draws radials from the site (where transmitter is located) to each calculation bin located along the transmitter calculation area border. In other words, Atoll determines a geographic profile between site and each bin centre.

Grid resolution

• Transmitter Radial: Atoll will extract a geographic profile for each radial

Centre of a bin located on the calculation border

Receiver: it may be anywhere in point analysis or at the centre of each calculation bin in coverage studies

Radial calculation method

Calculations


Transmitter Centre of a bin located on the calculation border Profile resolution

Site-bin centre profile The receiver may be located either anywhere within a calculation bin (Point prediction) or at the centre of a calculation bin (Coverage study). Therefore, according to the receiver position, Atoll chooses the nearest profile and uses it (receiver is considered as located on the profile) to perform prediction study at the receiver.

XI.3.4.a.ii Systematic extraction In this case, Atoll systematically extracts a geographic profile between the site (where transmitter resides) and the receiver.

Radial calculation method

• Transmitter Geographic profiles

Receiver: it may be anywhere in point analysis or at the centre of each calculation bin in coverage studies

XI.3.4.b PROFILE RESOLUTION: MULTI-RESOLUTION MANAGEMENT Geographic profile resolution depends on resolution of geographic data used by the propagation model (DTM and/or clutter).

1st case: If the chosen propagation model considers both DTM and clutter heights along the profile, the profile resolution will be the highest of the two.

Example 1: Standard Propagation Model is used to perform predictions. A DTM map with a 40m resolution and a clutter heights map with a 20m resolution are available. Both DTM and clutter maps are considered when using Standard Propagation Model. Therefore, here, the profile



resolution will be 20m. It means that Atoll will extract geographic information, ground altitude and clutter height, every 20m. To get ground altitude every 20m, Atoll uses the bilinear interpolation method described in the Path loss calculations: Altitude determination part. Clutter heights are read from the clutter heights map. Atoll takes the clutter height of the nearest point every 20m (see Path loss calculations: Clutter determination). Example 2: Standard Propagation Model is used to perform predictions. A DTM map with a 40m resolution and a clutter classes map with a 20m resolution are available. No clutter height file has been imported in .atl document. Both DTM and clutter maps are considered when using Standard Propagation Model. Therefore, here, the profile resolution will be 20m. It means that Atoll will extract geographic information, ground altitude and clutter height, every 20m. To get ground altitude every 20m, Atoll uses the bilinear interpolation method described in the Path loss calculations: Altitude determination part. Atoll uses the clutter classes map to determine clutter height. Every 20m, it determines clutter class and takes associated average height.

2nd case: If the chosen propagation model takes into account only DTM map along the profile, profile resolution will be the highest resolution among the DTM files.

Example: Cost-Hata is used to perform predictions. Both DTM maps with 40m and 25m resolutions and a clutter map with a 20m resolution are available.

Explorer window Work space

DTM - DTM 1 (25m) - DTM 2 (40m)

Clutter - Clutter (20m)

25m

40m

Only DTM maps are considered along the whole profile when using Cost-Hata model. Therefore, here, the profile resolution will be 25m. It means that Atoll will extract geographic information, only the ground altitude, every 25m. DTM1 is on the top of DTM2. Thus, Atoll will consider ground elevation read from DTM1 in the definition area of DTM1 and DTM2 elsewhere. To get ground altitude every 25m, Atoll uses the bilinear interpolation method described in the Path loss calculations: Altitude determination part. Note: 1. The selected profile resolution does not depend on the geographic layer order. In the last example, whatever the

DTM file order you choose, profile resolution will always be 25m. On the other hand, the geographic layer order will influence the usage of data to establish the profile.

2. The calculation bin of path loss matrices defined by the grid resolution is independent of geographic file resolution.

XI.4 PROPAGATION MODELS

XI.4.1 OVERVIEW Propagation models available in Atoll are presented below and their main characteristics are listed in the table hereafter. Note: In formulas described below, Lmodel is stated in dB.

Calculations

115 Unauthorized reproduction or distribution of this document is prohibited © FORSK 2003

Propagation model

Frequency band

Physical phenomena Diffraction calculation method

Profile based on

Profile extraction mode

Cell size

Rx location

Receiver Use

Hata models 150-2000 MHz

L(d, f, HRx) per environment Diffraction loss

Deygout - 1 obstacle DTM Radial Macro cell Mini cell

Street

Mobile GSM900 GSM1800 UMTS CDMA2000

SPM 150-2000 MHz L(d, HTxeff, HRxeff, Diffraction loss, clutter)

Deygout - 3 obstacles Epstein-Peterson - 3 obstacles Deygout corrected - 3 obstacles Millington - 1 obstacle

DTM Clutter

Radial Systematic

Macro cell Mini cell

Street

Mobile GSM900 GSM1800 UMTS CDMA2000

WLL 30-10000 MHz Free space loss Diffraction loss

Deygout - 3 obstacles DTM Clutter

Radial - Street Rooftop

Fixed Microwave links WLL

ITU 526-5 30-10000 MHz Free space loss Diffraction loss

Deygout - 3 obstacles Deygout corrected - 3 obstacles

DTM Radial Macro cell

Street

Fixed Microwave links WLL

ITU 370-7 (Vienna 93)

100-400 MHz Free space loss Corrected standard loss

- - - Macro cell

Rooftop Fixed Broadcast

Note: In the Physical phenomena column, bold expressions refer to formulas customisable in Atoll.


FORSK 2003 Unauthorized reproduction or distribution of this document is prohibited 116

XI.4.2 OKUMURA-HATA AND COST-HATA

XI.4.2.a HATA FORMULA Hata formula empirically describes the path loss as a function of frequency, receiver-transmitter distance and antenna heights for an urban environment. This formula is valid for flat, urban environments and 1.5 metre mobile antenna height. Path loss (Lu) is calculated (in dB) as follows:

( ) ( ) ( )( ) dhBBhAfAALu TxTx loglogloglog 21321 ++++= f is the frequency (MHz). hTx is the transmitter antenna height above ground (m) (Hb notation is also used in Atoll). d is the distance between the transmitter and the receiver (km). The parameters A1, A2, A3, B1 and B2 can be user-defined. Default values are proposed in the table below:

Parameters Okumura-Hata f ≤ 1500 MHz

Cost-Hata f > 1500 MHz

A1 69.55 46.30 A2 26.16 33.90 A3 -13.82 -13.82 B1 44.90 44.90 B2 -6.55 -6.55

Default Hata parameters

XI.4.2.b CORRECTIONS TO THE HATA FORMULA As described above, the Hata formula is valid for urban environment and a receiver antenna height of 1.5m. For other environments and mobile antenna heights, corrective formulas must be applied.

( )Rxel haLuL −=1mod for large city and urban environments

( ) 4.528

log2 21mod −

−−= fhaLuL Rxel for suburban area

( ) ( ) ( ) 94.40log33.18log78.4 21mod −+−−= ffhaLuL Rxel for rural area

a(hRx) is a correction for a receiver antenna height different from 1.5m.

Environment a(Hr) Rural/Small city ( )( ) ( )( )8.0log56.17.0log1.1 −−− fhf Rx

Large city ( ) 97.475.11log2.3 2 −rxh Note: When receiver antenna height equals 1.5m, a(hRx) is close to 0 dB regardless of frequency.

XI.4.2.c CALCULATIONS IN ATOLL Hata models take into account topo map (DTM) between transmitter and receiver and morpho map (clutter) at the receiver. 1st step: For each calculation bin, Atoll determines the clutter bin on which the receiver is located. This clutter bin corresponds to a clutter class. Then, it uses the Hata formula assigned to this clutter class to evaluate ( )1modelL . 2nd step: This step depends on whether the ‘Add diffraction loss’ option is checked.

- If the ‘Add diffraction loss’ option is unchecked, Atoll stops calculations. 1modmod elel LL =

- If the ‘Add diffraction loss’ option is selected, Atoll proceeds as follows:

1. It extracts a geographic profile between the transmitter and the receiver based on the radial calculation

Calculations


mode. 2. It determines the largest obstacle along the profile in accordance with the Deygout method and

evaluates losses due to diffraction ( )2modelL . 2mod1modmod elelel LLL +=

Note: elLmod cannot be less than free space loss. Therefore, to avoid inconsistencies, a threshold value at least equal to

free space loss will be considered even if the calculated elLmod is lower than free space loss.

XI.4.3 STANDARD PROPAGATION MODEL (SPM)

XI.4.3.a SPM FORMULA SPM is based on the following formula:

( ) ( ) ( ) ( ) ( ) ( )clutterfKHKHdKlossnDiffractioKHKdKKL clutterRxeffTxeffTxeffel ++×+×+++= 654321mod loglog loglog

with, 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 loss: loss due to diffraction over an obstructed path (dB). K5: multiplying factor for log(HTxeff)log(d). K6: multiplying factor for RxeffH .

RxeffH : effective mobile antenna height (m). Kclutter: multiplying factor for f(clutter). f(clutter): average of weighted losses due to clutter.

XI.4.3.b CALCULATIONS IN ATOLL

XI.4.3.b.i Visibility and distance between the transmitter and the receiver For each calculation bin, Atoll determines:

- The distance between the transmitter and the receiver. If the distance Tx-Rx is lesser than the maximum user-defined distance (break distance), the receiver is considered to be near the transmitter. Atoll will use the set of values marked “Near transmitter”. If the distance Tx-Rx is greater than the maximum distance, receiver is considered far from transmitter. Atoll will use the set of values “Far from transmitter”.

- Whether the receiver is in the transmitter line of sight or not. If the receiver is in the transmitter line of sight, Atoll will take into account the set of values (K1,K2)LOS. If the receiver is not in the transmitter line of sight, Atoll will use the set of values (K1,K2)NLOS.

XI.4.3.b.ii Effective transmitter antenna height Effective transmitter antenna height (HTxeff) may be calculated with six different methods.

XI.4.3.b.ii.i Height above ground The transmitter antenna height is above the ground (HTx in m).

HTxeff = HTx

XI.4.3.b.ii.ii Height above average profile The transmitter antenna height is determined relative to an average ground height calculated along the profile between a transmitter and a 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 minimum and maximum distances from the transmitter respectively.

( )00 HHHH TxTxTxeff −+=



where, TxH0 is the ground height (ground elevation) above sea level at transmitter (m).

0H is the average ground height above sea level along the profile (m).

Note: If the profile is not located between the transmitter and the receiver, HTxeff equals HTx.

XI.4.3.b.ii.iii Slope at receiver between 0 and distance min The transmitter antenna height is calculated using the ground slope at receiver.

( ) ( ) dKHHHHH RxRxTxTxTxeff ×++−+= 00 where,

RxH is the receiver antenna height above the ground (m).

RxH0 is the ground height (ground elevation) above sea level at receiver (m). K is the ground slope calculated over a user-defined distance (Distance min). In this case, Distance min is a distance from receiver. Notes: 1. If mHTxeff 20< then, Atoll uses 20m in calculations.

2. If mHTxeff 200> then, Atoll takes 200m.

XI.4.3.b.ii.iv Spot Ht If RxTx HH 00 > then, ( )RxTxTxTxeff HHHH 00 −+= If RxTx HH 00 ≤ then, TxTxeff HH =

XI.4.3.b.ii.v Abs Spot Ht

RxTxTxTxeff HHHH 00 −+=

XI.4.3.b.ii.vi Enhanced slope at receiver Atoll offers a new method called “Enhanced slope at receiver” to evaluate the effective transmitter antenna height.

•

HRx

HTxeffH0 +

H0Tx

30m

R

d

LOS line

regression line terrain

profile Let x-axis and y-axis respectively represent positions and heights. We assume that x-axis is oriented from the transmitter (origin) towards the receiver. This calculation is achieved in several steps: 1st step: Atoll determines line of sight between transmitter and receiver. The LOS line equation is:

( ) ( ) ( ) ( )( ) ( )isd

HHHHHHiLos RxRxTxTxTxTx Re00

0+−+

−+=

Calculations


where, i is the point index. Res is the profile resolution (distance between two points).

2nd step: Atoll extracts the transmitter-receiver terrain profile. 3rd step: Hills and mountains are already taken into account in diffraction calculations. Therefore, in order for them not to unfavourably influence the regression line calculation, Atoll filters the terrain profile. Atoll calculates two filtered terrain profiles; one established from the transmitter and another from the 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, Atoll evaluates ground slope between two points and compares it with a threshold set to 0.05; where three cases are possible. Some notations defined hereafter are used in next part.

filtH is the filtered height.

origH 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 ( ) ( )TxHTxH origTxfilt =−

For each point, we have three different cases:

1st case: If ( ) ( )1−> iHiH origorig and ( ) ( )

05.0Re

1≤

−−s

iHiH origorig ,

Then, ( ) ( ) ( ) ( )( )11 −−+−= −− iHiHiHiH origorigTxfiltTxfilt

2nd case: If ( ) ( )1−> iHiH origorig and ( ) ( )

05.0Re

1>

−−s

iHiH origorig

Then, ( ) ( )1−= −− iHiH TxfiltTxfilt

3rd case: If ( ) ( )1−≤ iHiH origorig

Then, ( ) ( )1−= −− iHiH TxfiltTxfilt

If ( ) ( )iHiH origfilt > additionally

Then, ( ) ( )iHiH origTxfilt =−

- Filter starting from receiver Let us assume that ( ) ( )RxHRxH origfilt = For each point, we have three different cases:

1st case: If ( ) ( )1+> iHiH origorig and ( ) ( )

05.0Re

1≤

+−s

iHiH origorig ,

Then, ( ) ( ) ( ) ( )( )11 +−++= −− iHiHiHiH origorigRxfiltRxfilt

2nd case: If ( ) ( )1+> iHiH origorig and ( ) ( )

05.0Re

1>

−−s

iHiH origorig

Then, ( ) ( )1+= −− iHiH RxfiltRxfilt

3rd case: If ( ) ( )1+≤ iHiH origorig

Then, ( ) ( )1+= −− iHiH RxfiltRxfilt

If ( ) ( )iHiH origfilt > additionally

Then, ( ) ( )iHiH origRxfilt =− Then, for every point of profile, Atoll compares the two filtered heights and chooses the higher one.

( ) ( ) ( )( )iHiHiH RxfiltTxfiltfilt −−= ,max ( ) ( ) ( )( )iHiHiH RxfiltTxfiltfilt −−= ,max



4th step: Atoll determines the influence area, R. It corresponds to the distance from receiver at which the original terrain profile plus 30 metres intersects the LOS line for the first time (when beginning from transmitter). The influence area must satisfy additional conditions:

mR 3000≥ , dR ⋅≥ 01.0 , R must contain at least three bins.

Notes: 1. When several influence areas are possible, Atoll chooses the highest one. 2. If d < 3000m, R = d. 5th step: Atoll performs a linear regression on the filtered profile within R in order to determine a regression line. The regression line equation is:

baxy +=

( )( ) ( )( )( )( )∑

∑−

−−=

im

imfiltm

did

HiHdida 2 and mm adHb −=

where,

( )∑=i

filtm iHn

H 1

i is the point index. Only points within R are taken into account.

2Rddm −=

d(i) is the distance between i and the transmitter (m). Then, Atoll extends the regression line to the transmitter location. Therefore, its equation is:

( ) ( ) bsiairegr +⋅⋅= Re 6th step: Then, Atoll calculates effective transmitter antenna height, TxeffH (m).

a

bHHH TxTxTxeff

2

0

1+

−+=

If HTxeff is lower than 20m, Atoll recalculates it with a new influence area, which begins at transmitter. Notes: 1. In case mHTxeff 1000> , 1000m will be used in calculations.

2. If TxeffH is still lower than 20m, an additional correction is taken into account (7th step). 7th step: If TxeffH is still lower than 20m (even negative), Atoll evaluates path loss using mHTxeff 20= and applies a correction factor. Therefore, if mHTxeff 20< ,

( ) KfdmHLL lowantTxeffelel +== ,,20modmod where,

( ) ( )( )

+⋅

+

−−⋅−−⋅−=

100093.6

100063.9

20120203.0105 dd

HHd

K TxeffTxefflowant

Calculations


XI.4.3.b.iii Receiver effective antenna height ( ) TxRxRxRxeff HHHH 00 −+=

where, RxH is the receiver antenna height above the ground (m).

RxH0 is the ground height (ground elevation) above sea level at the receiver (m).

TxH0 is the ground height (ground elevation) above sea level at the transmitter (m). Note: The calculation of effective antenna heights ( RxeffH and TxeffH ) is based on extracted DTM profiles. They are not

properly performed if you have not imported heights (DTM file) beforehand.

XI.4.3.b.iv Correction for hilly regions in case of LOS An optional corrective term enables Atoll to correct path loss for hilly regions when the transmitter and the receiver are in Line-of-sight. Therefore, if the receiver is in the transmitter line of sight and the Hilly terrain correction option is active, we have:

( ) ( ) ( ) ( ) ( ) KclutterfKHKdHKHKdKKL LOShillclutterRxTxeffTxeffLOSLOSel ,653,2,1mod loglogloglog ++⋅++++= When the transmitter and the receiver are not in line of sight, the path loss formula is:

( ) ( ) ( ) ( ) ( )clutterfKHKdHKnDiffractioKHKdKKL clutterRxTxeffTxeffNLOSNLOSel +⋅+++++= 6543,2,1mod loglogloglog K LOShill , is determined in three steps. Influence area, R, and regression line are supposed available. 1st step: For every profile point within influence area, Atoll 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%. 2nd step: Atoll evaluates the terrain roughness, ∆h; it is the distance between the two lines. 3rd step: Atoll calculates K LOShill , .

We have KKK hfhLOShill +=, If mh 200 ≤∆< , 0=K h

Else ( ) ( ) 746.6log29.15log73.7 2 +∆−∆= hhK h If mh 100 ≤∆< , ( )( )iregrHHK RxRxRxhf −+⋅⋅−= 01924.02

Else ( ) ( )( ) ( )h

iregrHHhhK RxRxRxhf ∆

−+⋅−∆+∆−⋅−= 02 21.11log75.14log616.12

iRx is the point index at receiver.

XI.4.3.b.v Diffraction Four methods are available to calculate diffraction loss over the transmitter-receiver profile. They are detailed in the Appendices. Along the transmitter-receiver profile, both ground altitudes and clutter heights are considered. Atoll takes clutter height information from clutter heights if available in the .atl document. Otherwise, it considers average clutter height specified for each clutter class in the clutter classes description. If the .atl document does not contain any clutter height data and no average height per clutter class is specified, Atoll will consider ground altitude only.



XI.4.3.b.vi Losses due to clutter Atoll calculates f(clutter) over a maximum distance from receiver.

( ) ∑=

=n

iiiwLclutterf

1

where,

L: loss due to clutter defined in the Clutter tab by the user (in dB). w: weight determined through the weighting function. n: number of points taken into account over the profile. Points are evenly spaced depending on the profile resolution.

Four weighting functions are available:

• Uniform weighting function: n

wi1

=

• Triangular weighting function: ∑

=

= n

jj

ii

d

dw

1

'ii dDd −= , where d’i is the distance between the receiver and the ith point and D is the maximum distance defined.

• Logarithmic weighting function:

∑=

+

+=

n

j

j

i

i

Dd

Dd

w

11log

1log

• Exponential weighting function:

∑=

−

−=n

j

Dd

Dd

i j

i

e

ew

11

1

The chart below shows the weight variation with the distance for each weighting function.

w i=f(d i)

d i

w i

Uniform weighting function

Triangular weighting function

Loragithm ic weighting function

Exponentia l weighting function

Calculations


XI.4.3.b.vii 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:

1. 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 2. 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 Atoll proceeds as if there was only the DTM map. The clearance information is used to model streets.

Tx

Rx

clearance

clutter

DEM

Tx-Rx profile. Ground altitude and clutter height (here, average height specified for each clutter class in the clutter classes map

description) are taken into account along the profile. 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. Note: elLmod cannot be less than free space loss. Therefore, to avoid inconsistencies, a threshold value at least equal to


XI.4.4 WLL

XI.4.4.a WLL FORMULA

lossnDiffractiolossspaceFreeL el mod +=


XI.4.4.b.i Free space loss Please refer to the Appendices for further details about free space loss calculation.



XI.4.4.b.ii Diffraction Atoll calculates diffraction loss along the transmitter-receiver profile built from DTM and clutter maps. Therefore, losses due to clutter are taken into account in diffraction losses. Atoll takes clutter height information from the 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. The Deygout’s construction (considering 3 obstacles) is used. This method is detailed in the Appendices.

XI.4.4.b.ii.i Receiver clearance Define receiver clearance (m) per clutter class when clutter height information is either statistical or semi-deterministic. Both ground altitude and clutter height are considered along the whole profile except over a specific distance around the receiver (clearance), where Atoll proceeds as if there was only the DTM map (see SPM part). Atoll uses the clearance information to model streets. If the clutter is deterministic, do not define any receiver clearance (m) per clutter class. In this case, clutter height information is accurate enough to be used directly without additional information such as clearance (Atoll can locate streets).

XI.4.4.b.ii.ii Receiver height Entering receiver height per clutter class enables Atoll to consider the fact that receivers are fixed and located on the roofs.

XI.4.4.b.ii.iii Visibility If the option ‘Line of sight only’ is not selected, Atoll computes Lmodel on each calculation bin using the formula defined above. When selecting the option ‘Line of sight only’, Atoll checks for each calculation bin if the Diffraction loss (as defined in the Diffraction loss: Deygout part) calculated along profile equals 0.

- In this case, receiver is considered in ‘line of sight’ and Atoll computes Lmodel on each calculation bin using the formula defined above.

- Otherwise, Atoll considers that Lmodel tends to infinity. Note: elLmod cannot be less than free space loss. Therefore, to avoid inconsistencies, a threshold value at least equal to


XI.4.5 ITU-R P.526-5 MODEL

XI.4.5.a ITU 526-5 FORMULA lossnDiffractiolossspaceFreeL el mod +=



XI.4.5.b.ii Diffraction Atoll calculates diffraction loss along the transmitter-receiver profile is built from the DTM map. The Deygout’s construction (considering 3 obstacles), with or without correction, is used. These methods are detailed in the Appendices.

XI.4.6 ITU-R P.370-7

XI.4.6.a ITU 370-7 FORMULA If d<1 km, lossspaceFreeL el mod = If d>1000 km, 1000mod =L el

Calculations


If 1<d<1000 km, ( )loss standard Correctedloss, space FreeL el maxmod = d is the distance between the transmitter and the receiver (km).



XI.4.6.b.ii Corrected standard loss This formula is given for a 60 dBm (1kW) transmitter power.

Corrected standard loss fAAC clHn Rxefflog2054.3175.10860 −+−−−−=

where,

Cn is the field strength received in dBµV/m, AHRxeff

is a correction factor for effective receiver antenna height (dB), Acl is the correction for terrain clearance angle (dB), f is the frequency in MHz.

XI.4.6.b.ii.i Cn calculation The Cn value is determined from charts Cn=f(d, HTxeff). In the following part, let us assume that Cn=En(d,HTxeff) (where En(d,HTxeff) is the field received in dBµV/m) is read from charts for a distance, d (in km), and an effective transmitter antenna height, HTxeff (in m). First of all, Atoll evaluates the effective transmitter antenna height, HTxeff , as follows:

If 0 ≤ d < 3 km, HHHH RxTxTxTxeff 00 −+= If 3 ≤ d < 15 km, ( )dHHHH TxTxTxeff :300 −+= If 15 ≤ d, ( )15:300 HHHH TxTxTxeff −+=

where, TxH is the transmitter antenna height above the ground (m).

TxH0 is the ground height (ground elevation) above sea level at the transmitter (m).

( )dH :30 is the average ground height (m) above sea level for the profile between a point 3 km from transmitter and the receiver (located at d km from transmitter).

( )15:30H is the average ground height (m) above sea level for the profile between a point 3 km and another 15 km from transmitter.

Then, depending on d and HTxeff, Atoll determines Cn using bilinear interpolation as follows. If 37.5 ≤ HTxeff ≤ 1200, Cn= En(d,HTxeff) Otherwise, Atoll considers Hd Txeffhorizon ⋅= 1.4 (d is stated in km) Therefore, If HTxeff < 37.5

If d ≥ dhorizon, we have ( )5.37 ,25 ddEC horizonnn −+= Else Cn=En(d, 37.5) – En(dhorizon, 37.5) + En(25, 37.5)

If HTxeff > 1200

If d ≥ dhorizon, we have ( )2001 ,142 ddEC horizonnn −+= Else Cn=En(d, 1200) – En(dhorizon, 1200) + En(142, 1200)

XI.4.6.b.ii.ii AHRxeff calculation

⋅⋅=10

log206

HcAH

RxRxeff



where, HRx is the user-defined receiver height, c is the height gain factor.

Note: c values are provided in the recommendation 370-7; for example, c=4 in a rural case.

XI.4.6.b.ii.iii Acl calculation

If f ≤ 300 MHz, ( )( ) ( )

−++−+−= 1.011.0log209.61.82 ννAcl

Otherwise, ( ) ( )

−++−+−= 1.011.0log209.69.142 ννAcl

With

⋅⋅−=300

4000 fθν

where, θ is the clearance angle (in radians) determined according to the recommendation 370-7 (figure 19), f is the frequency stated in MHz.

XI.4.7 APPENDICES

XI.4.7.a FREE SPACE LOSS ( ) ( )dflossspaceFree log20log204.32 ++=

where,

f is the frequency in MHz, d is the Tx-Rx distance in km, Free space loss is stated in dB.

XI.4.7.b DIFFRACTION LOSS General method for one or more obstacles (knife-edge diffraction) is used to evaluate diffraction losses (Diffraction loss in dB). Four construction modes are implemented in Atoll. All of them are based on this same physical principle presented hereafter, but differ in the way they consider one or several obstacles. Calculations take the earth curvature into account through the effective Earth radius concept (K factor=1.333). Note: The calculation formulas are based on ITU 526-5 recommendations.

XI.4.7.b.i Knife-edge diffraction The procedure checks whether a knife-edge obstructs the first Fresnel Zone constructed between the transmitter and the receiver. The diffraction loss, J(ν), depends on the obstruction parameter (ν), which corresponds to the ratio of the obstruction height (h) and the radius of the Fresnel zone (r).

( )ddfddncr

21

210

2 +⋅⋅⋅⋅⋅=

where,

n is the Fresnel zone index, c0 is the speed of light (2.99792 x108 ms-1), f is the frequency in Hz d1 is the distance from the transmitter to obstacle in m, d2 is the distance from obstacle to receiver in m.

We have:

rh−= ν

h is the obstruction height (height from the obstacle top to the Tx-Rx axis).

Calculations


Tx Rxh

d1 d2 Knife-edge diffraction

Hence,

If ν ≥ -0.7, ( ) ( ) ( )111log20962

−++−⋅+= ννν .J

Else, ( ) 0=νJ

XI.4.7.b.ii Deygout method The Deygout’s construction, limited to a maximum of three edges, is applied to the entire profile from transmitter to receiver. This method is used to evaluate path loss incurred by multiple knife-edges. Deygout method is based on a hierarchical knife-edge sorting used to distinguish the main edges, which induce the largest losses, and secondary edges, which have a lesser effect. The edge hierarchy depends on the obstruction parameter (ν) value.

XI.4.7.b.ii.i 1 obstacle A straight line between transmitter and receiver is drawn and the height of the obstacle above the Tx-Rx axis, hi, is calculated. The obstruction position, di, is also recorded. νi are evaluated from these data. The point with the highest ν value is termed the principal edge, p, and the corresponding loss is J(νp).

Point p

Rx

Tx hp

Sea level

Deygout construction – 1 obstacle

Therefore, we have ( )ν pJlossnDiffractio =

XI.4.7.b.ii.ii 3 obstacles Then, the main edge (point p) is considered as a secondary transmitter or receiver. Therefore, the profile is divided in two parts: one half profile, between the transmitter and the knife-edge section, another half, constituted by the knife-edge-receiver section. The same procedure is repeated on each half profile to determine the edge with the higher ν. The two obstacles found, (points t and r), are called ‘secondary edges’. Losses induced by the secondary edges, J(νt) and J(νr), are then calculated. Once the edge hierarchy is determined, the total loss is evaluated by adding all the intermediary losses obtained.



Point t

Point r

Point p

Rx

Tx hp

hr

ht

Sea level

Deygout construction – 3 obstacles

Therefore,

If 0>ν p , we have ( ) ( ) ( )ννν rtp JJJlossnDiffractio ++= Otherwise ( )ν pJlossnDiffractio =

Note: In case of ITU 526-5 and WLL propagation models, Diffraction loss term is determined as follows: If 78.0−>ν p , we have ( ) ( ) ( )( )ννν rtp JJtJlossnDiffractio +⋅+=

Where, ( )

= 1,

6min ν pJ

t

Otherwise 0 =lossnDiffractio

XI.4.7.b.iii Epstein-Peterson method The Epstein-Peterson construction is limited to a maximum of three edges. First, Deygout construction is applied to determine the three main edges over the whole profile as described above. Then, the main edge height, hp, is recalculated according to the Epstein-Peterson construction. hp is the height above a straight line connecting t and r points. The main edge position dp is recorded and νp and J(νp) are evaluated from these data.

Point tPoint r

Point p

Rx

Tx

hp

hr

ht

Sea level

Epstein-Peterson construction

Therefore, we have ( ) ( ) ( )ννν rtp JJJlossnDiffractio ++=

XI.4.7.b.iv Deygout method with correction The Deygout method with correction (ITU 526-5) is based on the Deygout construction (3 obstacles) plus an empirical correction, C. Therefore,

If 0>ν p , we have ( ) ( ) ( )ννν rtp JJJlossnDiffractio ++= +C

Otherwise ( ) CJlossnDiffractio p += ν Note: In case of ITU 526-5 propagation model, Diffraction loss term is determined as follows: If 78.0−>ν p , we have ( ) ( ) ( )( )CJJtJlossnDiffractio rtP ++⋅+= ννν Where,

Calculations


( )

= 1,

6min ν pJ

t

dC 04.00.8 += (d: distance stated in km between the transmitter and the receiver). Otherwise 0 =lossnDiffractio

XI.4.7.b.v Millington method The Millington construction, limited to a single edge, is applied over the entire profile. Two horizon lines are drawn at the transmitter and at the receiver. A straight line between the transmitter and the receiver is defined and the height of the intersection point between the two horizon lines above the Tx-Rx axis, hh, is calculated. The position dh is recorded and then, from these values, νh and J(νh) are evaluated using the same previous formulas.

Point h

Rx

Tx hh

Sea level

Millington construction

Therefore, we have ( )ν hJlossnDiffractio =

XI.5 ANTENNA ATTENUATION CALCULATION The modelling method used to evaluate losses due to antenna pattern, antTxL , is desribed below. Furthermore, you will find explanations about the remote electrical downtilt modelling. Atoll calculates the accurate azimuth and tilt angles and then, performs a 3D interpolation of horizontal and vertical patterns to determine the attenuation of antenna.

XI.5.1.a CALCULATION OF AZIMUTH AND TILT ANGLES From the direction of the transmitter antenna and the receiver position relative to the transmitter, Atoll determines the receiver position relative to the direction of the transmitter antenna.



"x

'x

z (Height)

d

eRx

aRx

eTx

aTx

Tx y (North)

x (East)

'y

'z

"y

"z

Rx

aTx and eTx are respectively the transmitter (Tx) antenna azimuth and tilt in the coordinate system ( )zyxS ,,0 .

aRx and eRx are respectively the azimuth and tilt of the receiver (Rx) in the coordinate system ( )zyxS ,,0 . d is the distance between the transmitter (Tx) and the receiver (Rx). In the coordinate system ( )zyxS ,,0 , the receiver coordinates are:

( ) ( )( ) ( )

( )

⋅−⋅⋅⋅⋅

=

dedaedae

zyx

Rx

RxRx

RxRx

Rx

Rx

Rx

sincoscossincos

(1)

Let az and el respectively be the azimuth and tilt of the receiver in the transmitter antenna coordinate system

","," zyxSTx . Therefore, the receiver coordinates in

","," zyxSTx are:

( ) ( )( ) ( )

( )

⋅−⋅⋅⋅⋅

=

deldazeldazel

zyx

Rx

Rx

Rx

sincoscossincos

"""

(2)

According to the figure above, we have the following relations:

( ) ( )( ) ( )

⋅

−=

zyx

aaaa

zyx

TxTx

TxTx

1000cossin0sincos

'''

(3)

and

( ) ( )( ) ( )

⋅

−=

'''

cossin0sincos0

001

"""

zyx

eeee

zyx

TxTx

TxTx (4)

Therefore, the relation between the system ( )zyxS ,,0 and the transmitter antenna system ( )","," zyxSTx is:

Calculations


( ) ( )( ) ( )

( ) ( )( ) ( )

⋅

−⋅

−=

zyx

aaaa

eeee

zyx

TxTx

TxTx

TxTx

TxTx

1000cossin0sincos

cossin0sincos0

001

"""

(5)

We get,

( ) ( )( ) ( ) ( ) ( ) ( )( ) ( ) ( ) ( ) ( )

⋅

⋅−⋅⋅

−=

zyx

eaeaeeaeae

aa

zyx

TxTxTxTxTx

TxTxTxTxTx

TxTx

coscossinsinsinsincoscossincos

0sincos

"""

(6)

Then, substituting the receiver coordinates in the system S0 from Eq. (1) and the receiver coordinates in the system STx from Eq. (2) in Eq. (6) leads to a system where two solutions are possible: 1st solution: If TxRx aa = , then 0=az and TxRx eeel −= 2nd solution: If TxRx aa ≠ , then

( )( )

( ) ( )( )

−⋅+

−

=

TxRx

RxTx

TxRx

Tx

aaee

aaeaz

sintansin

tancos

1arctan

and

( ) ( )( )

( ) ( )( )

−

⋅+−

−⋅=TxRx

RxTx

TxRx

Tx

aaee

aaeazel

sintancos

tansinsinarctan

If ( ) ( ) 0sinsin <−⋅ TxRx aaaz , then π+= azaz Note: Remote electrical downtilt modelling The remote electrical downtilt, REDT, introduces a conical transformation of the 3D antenna pattern in the vertical axis. It is taken into account in the azimuth and tilt angles computation. Therefore, we use the following formulas to calculate az and el: 1st solution: If TxRx aa = , then 0=az and TxRx eREDTeel −−= 2nd solution: If TxRx aa ≠ , then

( )( )

( ) ( )( )

−−⋅+

−

=

TxRx

RxTx

TxRx

Tx

aaREDTee

aae

az

sintansin

tancos

1arctan

and

( ) ( )( )

( ) ( )( )

−

−⋅+

−−

⋅=TxRx

RxTx

TxRx

Tx

aaREDTee

aaeazel

sintancos

tansinsinarctan

If ( ) ( ) 0sinsin <−⋅ TxRx aaaz , then π+= azaz

XI.5.1.b ANTENNA PATTERN 3D INTERPOLATION Atoll determines losses due to horizontal and vertical patterns of transmitter antenna. It reads the losses H(az) in the horizontal pattern for the calculated azimuth angle az and the losses V(el) in the vertical pattern for the calculated tilt angle el. Then, it calculates the global losses due to antenna pattern, ( )elazLantTx , :

( ) ( ) ( ) ( )( ) ( ) ( )( )

−−⋅+−⋅

−−= elVH

azelVH

azazHelazLantTx ππ

πππ

0,



Note: We assume that the horizontal and vertical patterns are two cross-sections of the 3D pattern. In other words, the description of the antenna pattern must satisfy the following:

H(0)=V(0) and H(π)=V(π) In case of an electrical tilt, α, the horizontal pattern is a conical section with a α degrees elevation off the

horizontal plane. Here, horizontal and vertical patterns must satisfy the following: H(0)=V(α) and H(π)=V(π-α) If the constraints listed above are satisfied, this implies that: 1. Interpolated horizontal and vertical patterns respectively fit in with the entered horizontal and vertical patterns,

even in case of electrical tilt, 2. The contribution of both the vertical pattern back and front parts are taken into account.

Otherwise, only the second point is guaranteed. Note: Atoll uses this modelling method from the Atoll 2.1 version (inclusive) and above. In Atoll’s versions prior to the

2.1, another modelling method was available to evaluate angles and losses due to antenna pattern. The user has the option to choose between these two methods through Atoll.ini file (see Atoll administration files). For further information about the old modelling method, please refer to the Technical Reference Guide 2.2.

XI.6 SHADOWING MODEL

XI.6.1 OVERVIEW Propagation models (e.g. Cost-Hata, Standard Propagation Model, …) assume that path loss is only a function of parameters such as antenna heights, environment and distance. The predicted path loss for a system operated in a particular environment will therefore be constant for a given transmitter-receiver distance. In practice, however, the particular clutter environment along a path at a given distance will be different for every path. This causes variations with respect to the nominal values given by the path loss models. Some paths will suffer increased loss, while others will be less obstructed and have an increased signal strength. This phenomenon is called shadowing or slow fading because variations occur over distances comparable to the width of obstacles (buildings, hills, ...) along the path. “Slow” is used in opposition to fast fading or Rayleigh fading, which comes from multipath interference and has very short distance variation. It is crucial to account for this in order to predict the reliability of coverage provided by any mobile cellular system. The shadowing effect can be modelled by a log-normal (also called Gaussian) distribution with a model standard deviation σ depending on the clutter type. The corresponding log-normal density function is represented hereafter.

Shadowing Margin (dB)

Gaussian Probability Density Function

Log-normal Probability Density Function

Different clutter types have different impacts on the shadowing effect. Therefore, each clutter type is characterized by a different model standard deviation. For every clutter class the shape of the Gaussian distribution curve will be the same but the unit scale of the horizontal axis of the graph will be different. The accuracy of this modelling will depend on:

- The suitability of the range of standard deviation used for each clutter class, - The definition (bin size) of the digital map, - How up-to-date the digital map is, - The number of clutter classes, - The accuracy of assignment of clutter classes.

Calculations


Shadowing is taken into account in different ways in predictions (prediction studies and point analysis) and in (UMTS, CDMA2000 or IS95-CDMA) Monte-Carlo simulations:

- In predictions, a shadowing margin ( MShadowing ) is added to the computed path loss ( pathL ) on each bin. The shadowing margin is calculated for a certain cell edge coverage probability and depends on the model standard deviation associated to the receiver clutter class. The cell edge coverage probability corresponds to the percentage of subscribers on the cell edge that the radio planner is aiming to cover. For example, a cell edge coverage probability of 75% means that 75% of the subscribers on the edge of the cell will receive adequate signal level. Therefore, when calculating a prediction study with a cell edge coverage probability of x%, we may conclude that the signal level predicted on each bin is reliable x% of time and the global predicted coverage area is reliable at least x% of time.

In UMTS, CDMA2000 and IS95-CDMA, Atoll calculates uplink and downlink macro-diversity gains ( UL

diversitymacroG −

and DLdiversitymacroG − ) depending on the receiver handover status. These gains are respectively taken into account to

evaluate the uplink Eb/Nt in case of soft handover and the downlink Ec/Io from best server (see paragraph XIV.1).

- For each individual Monte Carlo simulation, Atoll derives a random shadowing margin for each mobile-to-cell link and adds this value to the predicted path loss. The way Atoll estimates the shadowing margin complies with the statistical nature of the Monte Carlo approach. A shadowing margin for each mobile-cell link in each simulation is obtained by taking a random value from the probability density distribution for the appropriate clutter class that describes the shadowing effect. This probability distribution is a log-normal distribution as explained above.

XI.6.2 MODELLING IN PREDICTIONS

XI.6.2.a SHADOWING MARGIN EVALUATION From a user-defined standard deviation at the receiver position and required cell edge coverage probability, a shadowing margin, Mshadowing, is calculated and added to the path loss, Lpath.

XI.6.2.a.i Shadowing error pdf (one signal) The measured path loss in dB can be expressed as a Gaussian Random Variable:

( )10,GLL dBpath ×+= σ

where,

Lpath is the predicted path loss, σdB is the user-defined standard deviation of the error, G(0,1) is a zero-mean unit-variance Gaussian RV.

Thus, the probability density function (pdf) for the random or shadowing part of path loss is:

( ) 2

2

2e2

1dBσ

x

dBL πσ

xp−

×=

Therefore the probability to have a shadowing exceeding z dB is

( ) ( ) dxeπσ

dxxpzxPz

σx

dBz LL

dB∫∫∞+ −∞+

×==>2

2

2

21

If we normalise x by dividing it by σdb:

( )

=×=> ∫

∞+ −

dBσz

x

L σzQdxe

πzxP

dB

2

2

21

where,

Q is the complementary cumulative function. To ensure a required cell edge coverage probability, LR , for the predicted value, we have to add a shadowing margin, MShadowing , to the link budget.



Confidence in the prediction can be expressed as: ( )

MLPPMσ,GPPLPLPCd

ShadowingpathTxrec

ShadowingdBrecTxrecTx

−−=≤×⇔−≤⇔≥−=

'10''

where,

Prec is the field level predicted at the receiver

RxantRxTx LGEIRPP −+=' EIRP is the effective isotropic radiated power of the transmitter. LRx are receiver losses.

Gant Rxis the receiver antenna gain.

The shadowing margin value is such that:

( ) ( ) ( )

−=>−−==≥

dB

ShadowingShadowingLShadowingLrecd

MQMxPMRPCP

σ101

Because Q is a well-known function, we plan to use its tabulation for a set of cell edge coverage probabilitys. Therefore, it will be easy to work out the needed MShadowing for each link. Above, we have considered that a cell has only coverage limitations. Generally, it is also limited by interference. So, the signal to noise ratio has to be more than a signal to noise ratio threshold as well. In the denominator, we also have different random variations for each interferer. It is expedient to consider average interference as valid (for CDMA networks, we can consider that a certain level of interference is maintained by congestion control [3]). Otherwise, we would have to model the probabilities of having different levels of interference. At each bin, we would have a different pdf with a different standard deviation for interference (depending on number of interferers). Therefore, in studies where signal to noise ratio is calculated, only the signal from interfered transmitter (C) is downgraded by the shadowing margin. We consider that interference value (I) is not altered by the shadowing margin.

0.4 0.6 0.80

1

2

3

Probability (one signal)

Margin

(Margin is normalised: MargindB

Shadowing

σM

= )

XI.6.2.b UPLINK MACRO-DIVERSITY GAIN EVALUATION In UMTS, CDMA2000 and IS95-CDMA, mobiles may be in soft handoff (mobile connected to cells located on different sites). In this case, we can consider the shadowing error pdf described below.

XI.6.2.b.i Shadowing error pdf (n signals) For each link, path loss (L) can be broken down as:

ξLL path += ξ is a zero mean gaussian random variable ( )dB,σG 0 representing variation due to shadowing. It can be expressed as the sum of two uncorrelated zero mean gaussian random variables, Lξ and Pξ . Lξ models error related to the receiver local environment; it is the same whichever the link. Pξ models error related to the path between transmitter and receiver. Therefore, in case of two links, we have:

11 PL ξξξ += for the link 1


Knowing iξ , the model standard deviation ( )σ and the correlation coefficient ρ between 1ξ and 2ξ , we can calculate

Calculations


standard deviations of ( )LLξ σ and ( )piPξ σ (assuming all i

Pξ have the same standard deviations). We have:

222PL σσσ +=

2

2

σσρ L=

Therefore, ( )ρσσP −×= 122

ρσσL ×= 22

XI.6.2.b.i.i 2 signals without recombination In technologies supporting soft handoff (UMTS, CDMA2000, IS95-CDMA), cell is interference limited. As for one link, to ensure a required cell edge coverage probability LR for the prediction, we add to each link budget a shadowing margin,

M signalsShadowing2 .

Prediction reliability in order to have Eb/Nt higher or equal to Eb/Nt from the best server can be expressed as:

1111

1111

1

11

'' predpathTxpredTx CINLPξCINLPN

Cd −−−≤⇔≥−−=

or 1

22221

2222

2 '' predpathTxpredTx CINLPξCINLPN

Cd −−−≤⇔≥−−=

where

CIipred is the quality level (signal to noise ratio) predicted at the receiver for link i.

Ni is the noise level for link i. We note:

ipredipathiiShadowing CINM signals −−−= LP'tx

2 and

2121 predpred CICI −=∆

21∆ is the minimum needed margin on each link.

Therefore, the probability of having a quality at least equal to the best predicted one is:

( )

<<−= 1

2

21

1

12,1

Cd,Cd12predpredLLShadowing

noMRCL CI

NCI

NPMR signals

( ) ( )2121,

22

21

2 ,1 ∆−>>−= MMPMR signalssignalssignalsShadowingShadowingShadowing

noMRCL ξξξξ

We can express it using Lξ , 1

Pξ and 2Pξ

( ) ( ) ( )( ) ( ) ( ) ( )

( ) ( ) ( ) ( ) LLShadowingPξLShadowingPξLξShadowingnoMRCL

LShadowingPξLShadowingPξLξLLShadowingShadowing,ξξ

LShadowingpLShadowingp,ξξLξLLShadowingShadowing,ξξ

d∆∆M∆P∆M∆P∆PMR

∆M∆P∆M∆P∆P∆ξM,ξMξP

∆M,ξ∆MξP∆P∆ξM,ξMξP

signals

P

signals

PL

signals

signals

P

signals

PL

signalssignals

signalssignals

ppL

signalssignals

−∆−>×−>×−=

−∆−>×−>×==∆−>>

−∆−>−>×==∆−>>

∫∞+

∞−

21

21

21

212121

21

212121

222

2222

21

2221

22

21

1

( )

∆−==∆−>∆ ∫

∞+

∆−

−

p

Lsignals

Shadowing

M

x

pL

signalsShadowing

iPP

MQdxeMP

Lsignals

Shadowing

p

σπσσ

ξ

222

2

2

2

21

Then, we have:



( ) ( )∫∞+

∞−∆

∆−∆−×

∆−×∆−= L

p

Lsignals

Shadowing

p

Lsignals

ShadowingL

signalsShadowing

noMRCL d

MQ

MQPMR

L σσξ

21

222 1

If we introduce user defined standard deviation ( )σ and correlation coefficient ( )ρ , and consider that

LPξ is a Gaussian

pdf:

( ) LL

signalsShadowingL

signalsShadowing

xsignals

ShadowingnoMRCL dx

xMQ

xMQeMR

L

−

∆−−×

−

−×−= ∫

∞+

∞−

−

ρσρσ

ρσρσ

π 11211

21

2222

2

XI.6.2.b.i.ii n signals without recombination We can generalize the previous expression to n signals:

( ) L

n

i

iL

nsignalsShadowingLShadowing

x

ShadowingnoMRCL dx

xMQ

xMQeMRnsignalsL

nsignals ∏∫=

∞+

∞−

−

−

∆−−×

−

−×−=

2

12

11211

2

ρσ

ρσ

ρσρσ

π

The case where softer handoff occurs (two signals from co-site cells) is equivalent to the one signal case. The Softer/soft case is equivalent to the two signals case. For the path associated with the softer recombination, we will use combined SNR to calculate the availability of the link.

XI.6.2.b.i.iii Correlation coefficient determination There is currently no agreed model for predicting correlation coefficient ( )ρ between 1ξ and 2ξ . Two key variables influence correlation:

- The angle between the two signals. If this angle is small, correlation is high. - The relative values of the two signal lengths. If angle is 0 and lengths are the same, correlation is zero.

Correlation is different from zero when path lengths differ. A simple model has been found [1]:

21

DD

φφρ

γT

= when πφφ ≤≤T

Tφ is a function of the mean size of obstacles near the receiver and γ is also linked to the receiver environment.

In a normal handover status, assuming a hexagonal design for sites, φ is close to π (+/- π/3) and D1/D2 is close to 1.

In [1,5], 5.0=ρ when 30.γ = and 10πφT = .

In Atoll, ρ is set to 0.5.

XI.6.2.b.ii Uplink macro-diversity gain Atoll determines the uplink macro-diversity gain ( UL

diversitymacroG − ) from the shadowing margins calculated in case of one signal and n signals. Therefore, we have :

ShadowingnsignalsShadowing

ULdiversitymacro MMG −=−

Where n is the number of cell-mobile signals.

XI.6.2.c DOWNLINK MACRO-DIVERSITY GAIN EVALUATION In UMTS, CDMA2000 and IS95-CDMA, in case of soft handoff, mobiles are able to switch from one cell to another if the best pilot drastically fades. To model this function, we have to consider the probability of fading over the shadowing margin, both for the best signal and for all the other available signals, in the shadowing margin calculation. Let us consider the shadowing error pdf described below.

Calculations


XI.6.2.c.i Shadowing error pdf (n signals) For each link, path loss (L) can be broken down as:

ξLL path += ξ is a zero mean gaussian random variable ( )dB,σG 0 representing variation due to shadowing. It can be expressed as

the sum of two uncorrelated zero mean gaussian random variables, Lξ and Pξ . Lξ models the error related to the

receiver local environment, which is the same for all links. Pξ models the error related to the path between the transmitter and the receiver. Therefore, in case of two links, we have:



Knowing iξ , the model standard deviation ( )σ and the correlation coefficient ρ between 1ξ and 2ξ , we can calculate

standard deviations of ( )LLξ σ and ( )piPξ σ (assuming all i

Pξ have the same standard deviations). We have:

222PL σσσ +=

2

2

σσρ L=


ρσσL ×= 22

XI.6.2.c.i.i 2 available signals In technologies supporting soft handoff (UMTS, CDMA2000 and IS95-CDMA), cells are interference limited. As for one link, to ensure a required cell edge coverage probability LR for the prediction, we add a shadowing margin, signals

ShadowingM 2 , to each link budget.

Prediction reliability to have predIo

EcIoEc

≥ for the best server can be expressed as:

1

m11

1

11

11LPLP

predpilot

predpilot Io

EcIoIoEcIo

IoEc

−−−≤⇔

≥−−= ξ

Or 1

2m22

1

222 LPLP

predpilot

predpilot Io

EcIoIoEcIo

IoEc

−−−≤⇔

≥−−= ξ

We note:

i

predipiloti

signalsShadowing Io

EcIoM

−−−= m2 LP

2

pred

1

pred

21 Io

EcIoEc

−

=∆

21∆ is the minimum needed margin on each link.

Therefore, probability of having a quality at least equal to the best predicted one is:

( )

<

<−=1

21

12,1

2 ,1predpred

LLsignals

ShadowingnoMRCL Io

EcIo

EcIoEc

IoEcPMR

( ) ( )21

22

21,

2 ,121

∆−>>−= signalsShadowing

signalsShadowing

signalsShadowing

noMRCL MMPMR ξξξξ

We can express it by using Lξ , 1

Pξ and 2Pξ



( ) ( ) ( )( ) ( ) ( ) ( )

( ) ( ) ( ) ( ) LLsignals

ShadowingPLsignals

ShadowingPLsignals

ShadowingnoMRCL

Lsignals

ShadowingPLsignals

ShadowingPLLLsignals

Shadowingsignals

Shadowing

Lsignals

ShadowingpLsignals

ShadowingpLLLsignals

Shadowingsignals

Shadowing

dMPMPPMR

MPMPPMMP

MMPPMMP

PPL

PPL

ppL

∆∆−∆−>∆×∆−>∆×∆−=

∆−∆−>∆×∆−>∆×∆=∆=∆−>>

∆−∆−>∆−>×∆=∆=∆−>>

∫∞+

∞−

21

22212

21

222121

22

21,

21

2221,

21

22

21,

1

,

,,

21

2121

ξξξ

ξξξξξ

ξξξξξ

ξξξ

ξξξξξ

( )

∆−==∆−>∆ ∫

∞+

∆−

−

p

Lsignals

Shadowingx

pL

signalsShadowing

iP

MQdxeMP

LSHO

p

P σπσ γ

σ2

222

2

21

ξ

Then, we have:

( ) ( ) Lp

Lsignals

Shadowing

p

Lsignals

ShadowingL

signalsShadowing

noMRCL d

MQ

MQPMR

L∆

∆−∆−×

∆−×∆−= ∫

∞+

∞− σσ

21

222 1 ξ

If we introduce a user defined standard deviation ( )σ and a correlation coefficient ( )ρ and consider that

LξP is a Gaussian

pdf:

( ) LL

signalsShadowingL

signalsShadowing

xsignals

ShadowingnoMRCL dx

xMQ

xMQeMR

L

−

∆−−×

−

−×−= ∫

∞+

∞−

−

ρσ

ρσ

ρσ

ρσ

π 11211

21

2222

2

XI.6.2.c.i.ii n available signals We can generalize the previous expression for n signals:

( ) L

n

i

iL

nsignalsShadowingL

nsignalsShadowing

xnsignalsShadowing

noMRCL dx

xMQ

xMQeMR

L

∏∫=

∞+

∞−

−

−

∆−−×

−

−×−=

2

12

11211

2

ρσ

ρσ

ρσ

ρσ

π

0.5 0.55 0.6 0.65 0.7 0.75 0.8 0.85 0.9 0.95 10 2 4 6 8

10 12 14 16 18 20 Case of 2 signals

Probability

Margin (in dB)

__ 21∆ =1 dB

__ 21∆ =5 dB

__ 21∆ =10 dB

Calculations


0.5 0.55 0.6 0.65 0.7 0.75 0.8 0.85 0.9 0.95 10 2 4 6 8

10 12 14 16 18 20 Case of 3 signals (sigma=8dB, delta1=1dB)

Probability

Margin (in dB)

0.5 0.55 0.6 0.65 0.7 0.75 0.8 0.85 0.9 0.95 10 2 4 6 8

10 12 14 16 18 20 Case of 3 signals (sigma=8dB, delta1=2dB)

Probability

Margin (in dB)

__ 2 signals __ 3

1∆ =5 dB

__ 31∆ =10 dB

XI.6.2.c.i.iii Correlation coefficient determination For further information about determination of the correlation coefficient, please see paragraph XI.6.2.b.i.iii.

XI.6.2.c.ii Downlink macro-diversity gain Atoll determines the downlink macro-diversity gain ( DL

diversitymacroG − ) from the shadowing margins calculated in case of one signal and n signals. Therefore, we have :

ShadowingnsignalsShadowing

DLdiversitymacro MMG −=−

Where n is the number of available signals. Note: Atoll uses the DL macro-diversity gain to calculate Ec/Io. You can force Atoll not to take it into account through the

Atoll.ini file (see Atoll administration files). You must create this file and place it in the Atoll installation directory.

XI.6.3 MODELLING IN SIMULATIONS From a user-defined model standard deviation associated to the receiver position, a random shadowing error is computed and is added to the model path loss ( Lpath ). This random value is drawn during Monte-Carlo simulation. Each user is assigned a service, a mobility type, an activity status, a geographic position and a random shadowing value. For each link, path loss (L) can be broken down:

ξLL path += ξ is a zero mean gaussian random variable ( )dB,σG 0 representing variation due to shadowing. It can be expressed as

the sum of two uncorrelated zero mean gaussian random variables, Lξ and Pξ . Lξ models error related to the receiver

local environment. It is the same for all links. Pξ models error related to the path between transmitter and receiver. Therefore, in case of two links, we have:



11 PL ξξξ += for link 1

22 PL ξξξ += for link 2

From iξ , the model standard deviation ( )σ , and the correlation coefficient ( )ρ between 1ξ and 2ξ , we can calculate

standard deviations of Lξ ( )Lσ and iPξ ( )Pσ . Assuming all i

Pξ have the same standard deviations, We have:

222PL σσσ +=

2

2

σσρ L=


ρσσL ×= 22 As explained above (paragraph XI.6.2.b.i.iii), ρ is set to 0.5 in Atoll. So, we have:

2σσL =

and

2σσP =

Therefore, to model shadowing error common in all signals arriving at the receiver ( E ceiver

ShadowingRe ), values are randomly

drawn for each receiver. They follow a zero-mean gaussian distribution with a standard deviation

2σ , where ( )σ is

the standard deviation associated with the receiver’s clutter class. Then, for each receiver-transmitter pair, Atoll draws another value representing the shadowing part uncorrelated with the position of the receiver ( EPath

Shadowing ). This value

follows a zero-mean gaussian distribution with a standard deviation

2σ .

So, we have:

EEE PathShadowing

ceiverShadowingShadowing += Re

Random shadowing error has means centred at zero. Hence, this shadowing modelling method has no impact on the simulated network load. On the other hand, as shadowing errors on the receiver-transmitter links are uncorrelated, the method will influence the evaluated SHO gain in case mobile is in SHO.

XI.6.4 REFERENCES [1] Saunders S. “Antennas and propagation for Wireless Communication Systems” pp 180-198 [2] Holma H., Toskala A. “WCDMA for UMTS” [3] Jhong S., Leonard M. “CDMA systems engineering handbook” pp 309-315, 1051-1053” [4] Remy J.G., CUEUGNET J., SIBEN C. “Systèmes de radiocommunications avec les mobiles” pp 309-310 [5] Laiho J., Wacker A., Novosad T. “Radio network planning and optimisation for UMTS” pp 80-81

XI.7 APPENDICES

XI.7.1 TRANSMITTER RADIO EQUIPMENTS Radio equipment such as TMA, feeder and BTS, are taken into account to evaluate:

- Total UL and DL losses ( LL DLtotalULtotal −− , ) and total noise figure ( )totalNF in UMTS, CDMA2000 and IS95-CDMA documents,

- Total losses ( )TotalL in GSM-EGPRS documents. In Atoll, the transmitter-equipment pair is modelled as if there was one item only, i.e. globally. The reference point, which

Calculations


is the location of the transmission/reception parameters, is the entrance point in this set. For example, the TMA entrance point, if exists. Or more generally, the entrance of the first equipment. (See figure below)

XI.7.1.a UMTS, CDMA2000 AND IS95-CDMA DOCUMENTS Atoll calculates total UL and DL losses as follows:

GLL ULdivant

ULMiscULtotal −− −= (in dB)

where, LUL

Misc are the miscellaneous reception losses

GULdivant − is the antenna diversity gain

( )∑ −=− GLL DLDLDLtotal (in dB)

Therefore, we have:

LLLLL DLMisc

DLConnector

DLFeeder

DLTMADLtotal +++=−

where, LDL

TMA is the TMA transmission loss

LDLFeeder is the feeder transmission loss ( lLL DL

FeederFeederDLFeeder ×= , where LFeeder and l DL

Feeder are respectively the feeder loss per metre and the transmission feeder length in metre), LDL

Connector is the connector transmission loss

LDLMisc are the miscellaneous transmission losses

The total noise figure is determined with Friis' equation.

( ) ( )GG

NFG

NFNFNF ULFeeder

ULTMA

BTSULTMA

FeederTMAtotal ⋅

−+−+= 11 (not in dB1)

where, NFFeeder is the feeder noise figure, NFTMA is the TMA noise figure, NFBTS is the BTS noise figure,

GULTMA is the TMA reception gain,

GULFeeder is the feeder UL gain; LG UL

FeederULFeeder −= .

LULFeeder is the feeder reception loss ( lLL UL

FeederFeederULFeeder ×= , where LUL

Feeder and lULFeeder are respectively the feeder

loss per metre and the reception feeder length in metre), Notes: 1. According to the book “Radio network planning and optimisation for UMTS” by Laiho J., Wacker A., Novosad T.,

the noise figure corresponds to the loss in case of passive components. Therefore, feeder noise figure is equal to the sum of cable and connector uplink losses.

LLNF ULConnector

ULFeederFeeder +=

where LULConnector is the connector reception loss,

2. Loss and gain inputs specified in .atl documents must be positive values.

1 Formula cannot be directly calculated from components stated in dB and must be converted in linear values.



XI.7.1.b GSM-EGPRS DOCUMENTS Atoll calculates DL total losses as follows:

( )∑ −=− GLL DLDLDLtotal (in dB) Therefore, we have:

LLLLL DLMisc

DLConnector

DLFeeder

DLTMADLtotal +++=−

where, LDL

TMA is the TMA transmission loss,

LDLFeeder is the feeder transmission loss ( lLL DL

FeederFeederDLFeeder ×= , where LUL

Feeder and l DLFeeder are respectively the feeder

loss per metre and the transmission feeder length in metre), LDL

Connector is the connector transmission loss,

LDLMisc are the miscellaneous transmission losses.

XI.7.2 SECONDARY ANTENNAS When secondary antennas are installed on a transmitter, the signal level received from it is calculated as follows:

( ) ( )

el

i iiiant Tx

Tx

iantiTx

mmmant Tx

Tx

manti

iTx

rec L

elazL

LGxP

elazL

LGxP

P

TxTx

mod

,,

1

⋅⋅

+

⋅∑−⋅

=

∑−

−

−

−

(not in dB2)

Where,

PTx is the transmitter power (Ppilot in UMTS, CDMA2000 and IS95-CDMA documents), i is the secondary antenna index, xi is the percentage of power dedicated to the secondary antenna, i, G mant Tx− is the gain of the main antenna installed on the transmitter, LTx are transmitter losses (LTx=Ltotal-DL), G iant Tx− is the gain of the secondary antenna, i, installed on the transmitter, Lmodel is the path loss calculated by the propagation model,

( )mmmant elazL Tx,− is the attenuation due to main antenna pattern,

( )iiiant elazL Tx,− is the attenuation due to pattern of the secondary antenna, i.

The definition of angles, az and el, depends on the used calculation method.

- Method 1 (must be indicated in an atoll.ini file): azm is the difference between the receiver antenna azimuth and azimuth of the transmitter main antenna, elm is the difference between the receiver antenna tilt and tilt of the transmitter main antenna, azi is the difference between the receiver antenna azimuth and azimuth of the transmitter secondary antenna, i, eli is the difference between the receiver antenna tilt and tilt of the transmitter secondary antenna, i,

- Method 2 (default):

azm is the receiver azimuth in the coordinate system of the transmitter main antenna, elm is the receiver tilt in the coordinate system of the transmitter main antenna, azi is the receiver azimuth in the coordinate system of the transmitter secondary antenna, i, eli is the receiver tilt in the coordinate system of the transmitter secondary antenna, i,

2 Formula cannot be directly calculated from components stated in dB and must be converted in linear values.

C H A P T E R 12

GSM GPRS EGPRS documents This chapter provides information on calculations and optimisation methods available in GSM GPRS EGPRS documents.

12

GSM GPRS EGPRS documents


XII GSM GPRS EGPRS DOCUMENTS

XII.1 GENERAL PREDICTION STUDIES

XII.1.1 CALCULATION CRITERIA Three criteria can be studied in point analysis (Profile tab) and in general coverage studies. Study criteria are detailed in the table below:

Study criteria Formulas

Signal level ( PTxirec )

Signal level received from a transmitter on a TRX type ( ) ( ) ( ) ( )RxantShadowing

Txipath

Txirec LGMLttPttEIRPttP Rx

−+−−∆−=

Path loss ( LTxipath ) LLL ant

Txipath Tx

+= model

Total losses ( LTxitotal ) ( ) ( )GGLLMLL antantRxTxShadowing

Txipath

Txitotal RxTx

+−+++=

where,

EIRP is the effective isotropic radiated power of the transmitter, elLmod is the loss on the transmitter-receiver path (path loss) calculated by the propagation model,

LantTx is the transmitter antenna attenuation (from antenna patterns),

ShadowingM is the shadowing margin,

RxL are the receiver losses, Gant Rx

is the receiver antenna gain, ∆P is the power offset defined for the selected TRX type in the transmitter property dialog, tt is the TRX type (in the GSM GPRS EGPRS.mdb document template, there are three possible TRX types, BCCH, TCH and TCH Inner).

XII.1.2 POINT ANALYSIS

XII.1.2.a PROFILE TAB Atoll displays the signal level received from the selected transmitter on a TRX type ( ( )ttPTxi

rec ). Notes: 1. If power offsets of subcells are identical, field level received from a selected transmitter will be the same for all the

studied TRX types. 2. For a selected transmitter, it is also possible to study the path loss, LTxi

path , or the total losses, LTxitotal . Path loss and

total losses are the same on any TRX type.

XII.1.2.b RECEPTION TAB Analysis provided in the Reception tab is based on path loss matrices. So, you can study reception from TBC transmitters for which path loss matrices have been computed on their calculation areas. For each transmitter, Atoll displays the signal level received on a TRX type, ( ( )ttPTxi

rec ). Reception bars are displayed in a decreaseing signal level order. The maximum number of reception bars depends on the signal level received from the best server. Only reception bars of transmitters whose signal level is within a 30 dB margin of the best server can be displayed. Notes: 1. If power offsets of subcells are identical, field level received from a given transmitter will be the same whichever

the studied TRX type. 2. It is also possible to study the path loss, LTxi

path , or the total losses, LTxitotal of each transmitter. Path loss and total

losses are the same on any TRX type.



XII.1.3 COVERAGE STUDIES For each TBC transmitter, Txi, Atoll determines the selected criterion on each bin inside the Txi calculation area. In fact, each bin within the Txi calculation area is considered as a potential (fixed or mobile) receiver. Coverage study parameters to be set are:

- The study conditions in order to determine the service area of each TBC transmitter, - The display settings to select how to colour service areas.

XII.1.3.a SERVICE AREA DETERMINATION Atoll uses parameters entered in the Condition tab of the coverage study property dialog to predetermine areas where it will display coverage. We can distinguish four cases as below. Let us assume that:

- Each transmitter, Txi, belongs to a Hierarchical Cell Structure (HCS) layer, k, with a defined priority. - The maximum range option (available in the System tab of the Predictions property dialog) is inactive.

XII.1.3.a.i All the servers For each HCS layer, k, the service area of Txi corresponds to the bins where:

( ) ( ) threshold Maximum or or threshold Minimum <−≤ LossesTotalLttP TxiTxitot

Txirec

XII.1.3.a.ii Best signal level per HCS layer and a margin For each HCS layer, k, the service area of Txi corresponds to the bins where:


Txirec

And ( ) ( )( ) MBCCHPBestBCCHP Txj

recij

Txirec −≥

≠

M is the specified margin (dB). Best function: considers the highest value. Notes: 1. If the margin equals 0 dB, Atoll will consider bins where the signal level received from Txi is the highest. 2. If the margin is set to 2 dB, Atoll will consider bins where the signal level received from Txi is either the highest or

2dB lower than the highest. 3. If the margin is set to -2 dB, Atoll will consider bins where the signal level received from Txi is 2dB higher than the

signal levels from transmitters that are the 2nd best servers.

XII.1.3.a.iii Best signal level of the highest priority layer and a margin In this case, the service area of Txi corresponds to the bins where:


Txirec


recij

Txirec −≥

≠

And Txi belongs to the HCS layer with the highest priority



signal levels from transmitters that are the 2nd best servers.



XII.1.3.a.iv 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:


Txirec


recij

ndTxirec −≥

≠2

M is the specified margin (dB). 2nd Best function: considers the second highest value. Notes: 1. If the margin equals 0 dB, Atoll will consider bins where the signal level received from Txi is the second highest. 2. If the margin is set to 2 dB, Atoll will consider bins where the signal level received from Txi is either the second

highest or 2dB lower than the second highest. 3. If the margin is set to -2 dB, Atoll will consider bins where the signal level received from Txi is 2dB higher than the

signal levels from transmitters that are the 3rd best servers.

XII.1.3.b COVERAGE DISPLAY

XII.1.3.b.i Plot resolution Prediction plot resolution is independent of the matrix resolutions and can be defined on a per study basis. Prediction plots are generated from multi-resolution path loss matrices using bilinear interpolation method (similar to the one used to evaluate site altitude).

XII.1.3.b.ii Display types It is possible to display the transmitter service area with colours depending on any transmitter attribute or other criteria such as:

• Signal level (in dBm, dBµV, dBµV/m) Atoll calculates signal level received from the transmitter on each bin of each transmitter service area. A bin of a service area is coloured if the signal level exceeds (≥) the defined minimum thresholds (bin colour depends on signal level). Coverage consists of several independent layers whose visibility in the workspace can be managed. There are as many layers as transmitter service areas. Each layer shows the different signal levels available in the transmitter service area.

• Best signal level (in dBm, dBµV, dBµV/m) Atoll calculates signal levels received from transmitters on each bin of each transmitter service area. Where other service areas overlap the studied one, Atoll chooses the highest value. A bin of a service area is coloured if the signal level exceeds (≥) the defined thresholds (the bin colour depends on the signal level). Coverage consists of several independent layers whose visibility in the workspace can be managed. 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.

• Path loss (dB) Atoll calculates path loss from the transmitter on each bin of each transmitter service area. A bin of a service area is coloured if path loss exceeds (≥) the defined minimum thresholds (bin colour depends on path loss). Coverage consists of several independent layers whose visibility in the workspace can be managed. There are as many layers as service areas. Each layer shows the different path loss levels in the transmitter service area.

• Total losses (dB) Atoll calculates total losses from the transmitter on each bin of each transmitter service area. A bin of a service area is coloured if total losses exceed (≥) the defined minimum thresholds (bin colour depends on total losses). Coverage consists of several independent layers whose visibility in the workspace can be managed. There are as many layers as service areas. Each layer shows the different total losses levels in the transmitter service area.

• Best server path loss (dB) Atoll calculates signal levels received from transmitters on each bin of each transmitter service area. Where other service areas overlap the studied one, Atoll determines the best transmitter and evaluates path loss from the best transmitter. A bin of a service area is coloured if the path loss exceeds (≥) the defined thresholds (bin colour depends on path loss). Coverage consists of several independent layers whose visibility in the workspace can be managed. 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.



• Best server total losses (dB) Atoll calculates signal levels received from transmitters on each bin of each transmitter service area. Where service areas overlap the studied one, Atoll determines the best transmitter and evaluates total losses from the best transmitter. A bin of a service area is coloured if the total losses exceed (≥) the defined thresholds (bin colour depends on total losses). Coverage consists of several independent layers whose visibility in the workspace can be managed. 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.

• Number of servers Atoll evaluates how many service 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 whose visibility in the workspace can be managed. There are as many layers as defined thresholds. Each layer corresponds to an area where the number of servers exceeds (≥) a defined minimum threshold.

• 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. There is one coverage area per transmitter in the explorer.

• 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. There is one coverage area per cell edge coverage probability in the explorer.

XII.2 TRAFFIC ANALYSIS When starting a traffic analysis, Atoll distributes the traffic from maps to transmitters of each layer according to the compatibility criteria defined in the transmitter, services, mobility type, terminal type properties. Transmitters considered in traffic analysis are the active and filtered transmitters that belong to the focus zone. Note: If no focus zone exists in the .atl document, Atoll takes into account the computation zone.

XII.2.1 TRAFFIC DISTRIBUTION

XII.2.1.a NORMAL CELLS (NONCONCENTRIC, NO HCS LAYER)

XII.2.1.a.i Circuit switched services A user with a given circuit switched service, c, a terminal, t, and a mobility type, m, will be distributed to the BCCH and TCH subcells of a transmitter if:

- The terminal, t, works on the frequency band used by the BCCH subcell, - The terminal, t, works on the frequency band used by the TCH subcell.

XII.2.1.a.ii Packet switched services A user with a given packet switched service, p, a terminal, t, and a mobility type, m, will be distributed to the BCCH and TCH subcells of a transmitter if:

- The transmitter is an GPRS/EGPRS station (option specified in the transmitter property dialog), - The terminal, t, is technologically compatible with the transmitter, - The terminal, t, works on the frequency band used by the BCCH subcell, - The terminal, t, works on the frequency band used by the TCH subcell.

XII.2.1.b CONCENTRIC CELLS In case of concentric cells, TCH_INNER TRX type has the highest priority to carry traffic.

XII.2.1.b.i Circuit switched services A user with a given circuit switched service, c, a terminal, t, and a mobility type, m, will be distributed to the TCH_INNER, BCCH and TCH subcells of a transmitter if:

- The terminal, t, works on the frequency band used by the BCCH subcell, - The terminal, t, works on the frequency band(s) used by the TCH_INNER and TCH subcells.



XII.2.1.b.ii Packet switched services A user with a given packet switched service, p, a terminal, t, and a mobility type, m, will be distributed to the TCH_INNER, BCCH and TCH subcells of a transmitter if:

- The transmitter is an GPRS/EGPRS station (option specified in the transmitter property dialog), - The terminal, t, is technologically compatible with the transmitter, - The terminal, t, works on the frequency band used by the BCCH subcell, - The terminal, t, works on the frequency band(s) used by the TCH_INNER and TCH subcells.

XII.2.1.c HCS LAYERS For each HCS layer, k, you may specify the maximum mobile speed supported by the transmitters of the layer.

XII.2.1.c.i Circuit switched services A user with a given circuit switched service, c, a terminal, t, and a mobility type, m, will be distributed to the BCCH and TCH subcells (and TCH_INNER in case of concentric cells) of a transmitter if:

- The terminal, t, works on the frequency band used by the BCCH subcell, - The terminal, t, works on the frequency band(s) used by the TCH_INNER and TCH subcells, - The user’s mobility, m, is lower than the maximum speed supported by the layer, k.

XII.2.1.c.ii Packet switched services A user with a given packet switched service, p, a terminal, t, and a mobility type, m, will be distributed to the BCCH and TCH subcells (and TCH_INNER in case of concentric cells) of a transmitter if:

- The transmitter is an GPRS/EGPRS station (option specified in the transmitter property dialog), - The terminal, t, is technologically compatible with the transmitter, - The terminal, t, works on the frequency band used by the BCCH subcell, - The terminal, t, works on the frequency band(s) used by the TCH_INNER and TCH subcells, - The user mobility, m, is lower than the maximum speed supported by the layer, k.

XII.2.2 CALCULATION OF THE TRAFFIC DEMAND PER SUBCELL Here we assume that:

- Users considered for evaluating the traffic demand fulfil the compatibility criteria defined in the transmitter, services, mobility, terminal properties as explained above.

- Atoll distributes traffic on subcell service areas, which are determined using the option “Best signal level per HCS layer” with a 0dB margin and the subcell reception threshold as lower threshold.

- Same traffic is distributed to the BCCH and TCH subcells.

XII.2.2.a TRAFFIC MAPS BASED ON ENVIRONMENTS AND USER PROFILES

XII.2.2.a.i Normal cells (nonconcentric, no HCS layer) Number of subscribers ( mupX , ) for each TCH subcell (Txi, TCH), per user profile up with a given mobility m, is inferred as:

DTCHTxiSTCHTxiX mupmup ×= ),(),( ,, Where Sup,m is the TCH service area containing the user profile up with the mobility m and D is the user profile density. For each behaviour described in the user profile up, Atoll calculates the probability for the user to be connected with a given service using a terminal t.

XII.2.2.a.i.i Circuit switched services For a circuit switched service c, we have:

3600),(dNp call

tcup×

=

Where Ncall is the number of calls per hour and d is the average call duration (in seconds). Then, Atoll evaluates the traffic demand, mtcupD ),,( , in Erlangs for the subcell (Txi, TCH) service area.



),(,),,( ),(),( tcupmupmtcup pTCHTxiXTCHTxiD ×=

XII.2.2.a.i.ii Packet switched services For a packet switched service p, we have:

36008

),(××

=VNp call

tpup

Where Ncall is the number of calls per hour and V is the transmitted data volume per call (in kBytes). Then, Atoll evaluates the traffic demand, mtpupD ),,( , in kbits/s for the subcell (Txi, TCH) service area.

),(,),,( ),(),( tpupmupmtpup pTCHTxiXTCHTxiD ×=

XII.2.2.a.ii Concentric cells In case of concentric cells, Atoll distributes a part of traffic on the TCH_INNER service area (TCH_INNER is the highest priority traffic carrier) and the remaining traffic on the outer ring served by the TCH subcell. The traffic spread over the TCH_INNER subcell may overflow to the TCH subcell. In this case, the traffic demand is the same on the TCH_INNER subcell but increases on the TCH subcell. Note: Traffic overflowing from the TCH_INNER to the TCH is not uniformly spread over the TCH service area. It is still

located on the TCH_INNER service area. Number of subscribers ( mupX , ) for each TCH_INNER (Txi, TCH_INNER) and TCH (Txi, TCH) subcell, per user profile up with a given mobility m, is inferred as:

DINNERTCHTxiSINNERTCHTxiX mupmup ×= )_,()_,( ,,

( ) ( )[ ] DINNERTCHTxiSTCHTxiSTCHTxiX mupmupmup ×−= _,,),( ,,,

( )INNERTCHTxiS mup _,, and ( )TCHTxiS mup ,, respectively refer to the TCH_INNER and TCH subcell service areas containing the user profile up with the mobility m. D is the user profile density.

TCH

TCH_INNERTraffic overflow

S(Txi,TCH_INNER)

S(Txi,TCH)-S(Txi,TCH_INNER)

Representation of a concentric cell Txi

XII.2.2.a.ii.i Circuit switched services For each user of the user profile up using a circuit switched service c with a terminal t, Atoll calculates the probability ( ),( tcupp ) of the user being connected. Calculations are detailed in part XII.2.2.a.i.i. Then, Atoll evaluates the traffic demand, mtcupD ),,( , in Erlangs in the (Txi, TCH_INNER) and (Txi, TCH) subcell service areas.

( ) ( ) ),(,),,( _,_, tcupmupmtcup pINNERTCHTxiXINNERTCHTxiD ×=

( ) ( )INNERTCHTxiOINNERTCHTxiDpTCHTxiXTCHTxiD mtcuptcupmupmtcup _,_,),(),( max),,(),(,),,( ×+×= Where ( )INNERTCHTxiO _,max is the maximum rate of traffic overflow (in %) specified for the TCH_INNER subcell.



XII.2.2.a.ii.ii Packet switched services For each user of the user profile up using a packet switched service p with a terminal t, probability of the user being connected ( ),( tpupp ) is calculated as explained in part XII.2.2.a.i.ii. Atoll evaluates the traffic demand, mtpupD ),,( , in kbits/s in the (Txi,TCH_INNER) and (Txi, TCH) subcell service areas.

( ) ( ) ),(,),,( _,_, tpupmupmtpup pINNERTCHTxiXINNERTCHTxiD ×=

( ) ( )INNERTCHTxiOINNERTCHTxiDpTCHTxiXTCHTxiD mtpuptpupmupmtpup _,_,),(),( max),,(),(,),,( ×+×=

Where ( )INNERTCHTxiO _,max is the maximum rate of traffic overflow (in %) specified for the TCH_INNER subcell.

XII.2.2.a.iii HCS layers We assume two HCS layers: the micro layer has a higher priority than the macro layer. Txi belongs to the micro layer and Txj to the macro.

XII.2.2.a.iii.i Normal cells Atoll distributes traffic on the TCH service areas. The traffic capture is calculated with the option “Best signal level per HCS layer” meaning that there is an overlap between HCS layers service areas. Let ),( TCHTxjSmacro

goverlappin denote this area (TCH service area of the macro layer overlapped by the TCH service area of the micro layer). Traffic on the overlapping area is distributed to the TCH subcell of the micro layer because it has a higher priority. On this area, traffic of the micro layer may overflow to the macro layer. In this case, the traffic demand is the same on the TCH subcell of the micro layer but increases on the TCH subcell of the macro layer. Note: Traffic overflowing to the macro layer is not uniformly spread over the TCH service area of Txj. It is only located on

the overlapping area.

TC HTC H

M acro layer M ic ro layer

T ra ffic overflow

Representation of micro and macro layers Atoll evaluates the traffic demand on the micro layer (higher priority) as explained above. For further details, please refer to formulas for normal cells. Then, it proceeds with the macro layer (lower priority). Number of subscribers ( macro

mupX , ) for each TCH subcell (Txj, TCH) of the macro layer, per user profile up with the mobility m, is inferred as:

( ) ( ) ( )( ) DTCHTxjSTCHTxjSTCHTxjX macrogoverlappinmup

macromup

macromup ×−= − ,,, ,,,

Where ( )TCHTxjSmacro

mup ,, is the TCH service area of Txj containing the user profile up with the mobility m and D is the profile density. For each user described in the user profile up with the circuit switched service c and the terminal t, the probability for the user being connected ( ),( tcupp ) is calculated as explained in the part XII.2.2.a.i.i. Then, Atoll evaluates the traffic demand, macro

mtcupD ),,( , in Erlangs in the subcell (Txj,TCH) service area.

( ) ( ) ( ) ( )( ) ( )TCHTxiO

TCHTxiSTCHTxjS

TCHTxiDpTCHTxjXTCHTxjD micromup

macrogoverlappinmupmicro

mtcuptcupmacro

mupmacro

mtcup ,,

,,,, max

,

,),,(),(,),,( ××+×= −



For each user described in the user profile up with the packet switched service p and the terminal t, probability for the user to be connected ( ),( tpupp ) is calculated as explained in the part XII.2.2.a.i.ii. Then, Atoll evaluates the traffic demand, macro

mtpupD ),,( , in kbits/s in the subcell (Txj, TCH) service area.

),(),(

),(),(),(),( max

,

,),,(),(,),,( TCHTxiO

TCHTxiSTCHTxjS

TCHTxiDpTCHTxjXTCHTxjD micromup

macrogoverlappinmupmicro

mtpuptpupmacro

mupmacro

mtpup ××+×= −

Where ( )TCHTxiO ,max is the maximum rate of traffic overflow (stated in %) specified for the TCH subcell of Txi (micro

layer) and ( )TCHTxiSmicromup ,, is the TCH service area of Txi containing the user profile up with the mobility m.

XII.2.2.a.iii.ii Concentric cells Atoll evaluates the traffic demand on the micro layer (higher priority HCS layer) as explained above. For further details, please refer to formulas given in case of concentric cells. Then, it proceeds with the macro layer (lower priority HCS layer). The traffic capture is calculated with the option “Best signal level per HCS layer”. It means that there are overlapping areas between HCS layers where traffic is spread according to the layer priority. On these areas, traffic of the higher priority layer may overflow.

S1

S2

S3 S’1

S’3

S’2

The TCH_INNER service area of the macro layer is overlapped by the micro layer. This area consists of two parts: an area overlapped by the TCH service area of the micro layer ( )( )INNERTCHTxjSmacro

TCHTxigoverlappin _,,− and another overlapped

by the TCH_INNER service area of the micro layer ( )( )INNERTCHTxjSmacroINNERTCHTxigoverlappin _,_,− .

Let us consider three areas, S1, S2 and S3.

( ) ( )( )INNERTCHTxjSINNERTCHTxjSS macroTCHTxigoverlappinmup

macromup _,_, ,,,1 −−−=

( ) ( )INNERTCHTxjSS macroINNERTCHTxigoverlappinmup _,_,,2 −−=

( ) ( ) 2,,3 _, SINNERTCHTxjSS macroTCHTxigoverlappinmup −= −−

Where ( )INNERTCHTxjSmacro

mup _,, is the TCH_INNER subcell service area of Txj containing the user profile up with the mobility m. We only consider the overlapping areas containing the user profile up with the mobility m. On S1, the number of subscribers per user profile up with a given mobility m ( macro

mupX , ) is inferred:



( ) DSINNERTCHTxjX macromup ×= 1, _,

Where D is the user profile density. The traffic spread over the TCH_INNER service area of the micro layer may overflow on the TCH subcell. The traffic overflowing to the TCH subcell is located on the TCH_INNER service area. On S2 , the TCH subcell traffic coming from the TCH_INNER subcell traffic overflow may overflow proportional to R2.

( )INNERTCHTxiSSR micro

mup _,,

22 =

The traffic spread over the ring served by the TCH subcell of the micro layer only may overflow on S3 proportional to R3.

( ) ( )INNERTCHTxiSTCHTxiSSR micro

mupmicro

mup _,, ,,

33 −

=

Where ( )TCHTxiSmicro

mup ,, and ( )INNERTCHTxiSmicromup _,, are the TCH and TCH_INNER service areas of Txi respectively

containing the user profile up with the mobility m. For each user described in the user profile up with a circuit switched service c and a terminal t, the probability for the user being connected ( ),( tcupp ) is calculated as explained in the part XII.2.2.a.i.i. Then, Atoll evaluates the traffic demand, macro

mtcupD ),,( , in Erlangs in the subcell (Txj,TCH_INNER) service area.

( )( )

( ) ( ) ( )( ) ( )TCHTxiOpTCHTxiXR

TCHTxiOINNERTCHTxiOINNERTCHTxiDRpINNERTCHTxjX

INNERTCHTxjD

tcupmicro

mup

micromtcup

tcupmacro

mupmacro

mtcup

,,,_,_,

_,_,

max),(,3

maxmax),,(2

),(,

),,(

××××××

+×=

For each user described in the user profile up with a packet switched service p and a terminal t, probability for the user to be connected ( ),( tpupp ) is calculated as explained in the part XII.2.2.a.i.ii. Then, Atoll evaluates the traffic demand, macro

mtpupD ),,( , stated in kbits/s in the subcell (Txj,TCH_INNER) service area.

( )( )

( ) ( ) ( )( ) ( )TCHTxiOpTCHTxiXR

TCHTxiOINNERTCHTxiOINNERTCHTxiDRpINNERTCHTxjX

INNERTCHTxjD

tpupmicro

mup

micromtpup

tpupmacro

mupmacro

mtpup

,,,_,_,

_,_,

max),(,3

maxmax),,(2

),(,

),,(

××××××

+×=

Where ( )TCHTxiO ,max and ( )INNERTCHTxiO _,max are the maximum rates of traffic overflow (stated in %) specified for the TCH and TCH_INNER subcells of Txi respectively. The area of the TCH ring of the macro layer is overlapped by the micro layer. There are two parts: an area overlapped by the TCH service area of the micro layer ( )( )INNERTCHTCHTxjSmacro

TCHTxigoverlappin _,, −− and another one by the TCH_INNER

service area of the micro layer ( )( )INNERTCHTCHTxjSmacroINNERTCHTxigoverlappin _,_, −− .

Let us consider three areas, S’1, S’2 and S’3.

( ) ( ) ( )( )INNERTCHTCHTxjSINNERTCHTxjSTCHTxjSS macroTCHTxigoverlappinmup

macromup

macromup _,_,,' ,,,,1 −−−= −−

( ) ( )INNERTCHTCHTxjSS macroINNERTCHTxigoverlappinmup _,' _,,2 −= −−

( )( ) 2,,3 '_,' SINNERTCHTCHTxjSS macroTCHTxigoverlappinmup −−= −−

Where ( )TCHTxjSmacro

mup ,, and ( )INNERTCHTxjSmacromup _,, are the TCH and TCH_INNER subcell service areas of Txj

respectively. We only consider the overlapping areas containing the user profile up with the mobility m.



On S’1, the number of subscribers per user profile up with a given mobility m ( macro

mupX , ) is inferred:

( ) DSTCHTxjX macromup ×= 1, ',

Where D is the user profile density. The traffic spread over the TCH_INNER service area of the micro layer may overflow on the TCH subcell. The traffic overflowing on the TCH subcell is located on the TCH_INNER service area. On S’2 , the TCH subcell traffic coming from the TCH_INNER subcell traffic overflow may overflow proportionally to R’2.

( )INNERTCHTxiSSR micro

mup _,''

,

22 =

The traffic spread over the ring served by the TCH subcell of the micro layer only may overflow on S’3 proportional to R’3.

( ) ( )INNERTCHTxiSTCHTxiSSR micro

mupmicro

mup _,,''

,,

33 −

=

Where ( )TCHTxiSmicro

mup ,, and ( )INNERTCHTxiSmicromup _,, are the TCH and TCH_INNER service areas of Txi respectively

containing the user profile up with the mobility m. For each user described in the user profile up with a circuit switched service c and a terminal t, the probability for the user being connected ( ),( tcupp ) is calculated as explained in the part XII.2.2.a.i.i. Then, Atoll evaluates the traffic demand, macro

mtcupD ),,( , in Erlangs in the subcell (Txj,TCH) service area.

( )( )

( ) ( )( ) ( ) ( )

( ) ( )TCHTxiOpTCHTxiXRTCHTxiOINNERTCHTxiOINNERTCHTxiDR

INNERTCHTxjOINNERTCHTxjDpTCHTxjX

TCHTxjD

mtcupmicro

mup

micromtcup

macromtcup

tcupmacro

mup

macromtcup

,,',_,_,'

_,_,,

,

max),,(,3

maxmax),,(2

max),,(

),(,

),,(

×××+×××

+×+×

=

For each user described in the user profile up with a packet switched service p and a terminal t, the probability for the user being connected ( ),( tpupp ) is calculated as explained in the part XII.2.2.a.i.ii. Then, Atoll evaluates the traffic demand, macro

mtpupD ),,( , in kbits/s in the subcell (Txj,TCH) service area.

( )( )

( ) ( )( ) ( ) ( )

( ) ( )TCHTxiOpTCHTxiXRTCHTxiOINNERTCHTxiOINNERTCHTxiDR

INNERTCHTxjOINNERTCHTxjDpTCHTxjX

TCHTxjD

mtpupmicro

mup

micromtpup

macromtpup

tpupmacro

mup

macromtpup

,,',_,_,'

_,_,,

,

max),,(,3

maxmax),,(2

max),,(

),(,

),,(

×××+×××

+×+×

=

Where ( )TCHTxiO ,max is the maximum rate of traffic overflow (stated in %) specified for the TCH subcell of Txi (micro layer), ( )INNERTCHTxiO _,max the maximum rate of traffic overflow indicated for the TCH_INNER subcell of Txi (macro layer), ( )INNERTCHTxjO _,max the maximum rate of traffic overflow indicated for the TCH_INNER subcell of Txj (macro

layer) and ( )TCHTxiX micromup ,, the number of subscibers with the user profile up and mobility m on the TCH service area of

Txi (as explained in the part XII.2.2.a.ii).

XII.2.2.b TRAFFIC MAPS BASED ON TRANSMITTERS AND SERVICES We assume that the traffic map is built from a coverage by transmitter prediction study calculated for the TCH subcells with options:

- “Best signal level per HCS layer” and no margin if the network only consists of normal cells and concentric cells, - “Best signal level of the highest priority HCS layer” and no margin in case of HCS layers.

When creating the traffic map, you have to specify the traffic demand per transmitter and per service (throughput for a



packet switched service and erlangs for a circuit switched service) and the global distribution of terminals and mobility types. Let ( )TCHTxiEc , denote the erlangs for the circuit switched service, c, on the TCH subcell of Txi. Let ( )TCHTxiTp , denote the throughput of the packet switched service, p, on the TCH subcell of Txi. We assume that 100% of users have the terminal, t, and the mobility type, m.

XII.2.2.b.i Normal cells (nonconcentric, no HCS layer) For each circuit switched service, c, Atoll evaluates the traffic demand, Dc,t,m, in Erlangs in the subcell (Txi, TCH) service area. ( ) ( )TCHTxiETCHTxiD cmtc ,,,, = For each packet switched service, p, Atoll evaluates the traffic demand, Dp,t,m, in kbits/s in the subcell (Txi, TCH) service area. ( ) ( )TCHTxiTTCHTxiD pmtp ,,,, =

XII.2.2.b.ii Concentric cells In case of concentric cells, Atoll distributes a part of traffic on the TCH_INNER service area (TCH_INNER is the highest priority traffic carrier) and the remaining traffic, on the ring served by the TCH subcell only. The traffic spread over the TCH_INNER subcell may overflow to the TCH subcell. In this case, the traffic demand is the same on the TCH_INNER subcell and rises on the TCH subcell. Note: Traffic overflowing from the TCH_INNER to the TCH is not uniformly spread over the TCH service area. It is only

located on the TCH_INNER service area. For each circuit switched service, c, Atoll evaluates the traffic demand, Dc,t,m, in Erlangs in the subcell, (Txi, TCH_INNER) and (Txi, TCH), service areas.

( ) ( )( ) ( )TCHTxiE

TCHTxiSINNERTCHTxiSINNERTCHTxiD cmtc ,

,_,_,,, ×=

and

( )( ) ( )( )

( ) ( )( ) ( )INNERTCHTxiOINNERTCHTxiD

TCHTxiETCHTxiS

INNERTCHTxiSTCHTxiSTCHTxiD

mtc

cmtc

_,_,

,,

_,,,

max,,

,,

×

+×−=

For each packet switched service, p, Atoll evaluates the traffic demand, Dp,t,m, in kbits/s in the subcell, (Txi, TCH_INNER) and (Txi, TCH), service areas.

( ) ( )( ) ( )TCHTxiT

TCHTxiSINNERTCHTxiSINNERTCHTxiD pmtp ,

,_,_,,, ×=

and

( )( ) ( )( )

( ) ( )( ) ( )INNERTCHTxiOINNERTCHTxiD

TCHTxiTTCHTxiS

INNERTCHTxiSTCHTxiSTCHTxiD

mtp

pmtp

_,_,

,,

_,,,

max,,

,,

×

+×−=

Where ( )INNERTCHTxiO _,max is the maximum rate of traffic overflow (stated in %) specified for the TCH_INNER

subcell, ( )TCHTxiS , and ( )INNERTCHTxiS _, are the TCH and TCH_INNER service areas of Txi respectively.

XII.2.2.b.iii HCS layers We assume we have two HCS layers: the micro layer has a higher priority and the macro layer has a lower one. Txi belongs to the micro layer and Txj to the macro one.

XII.2.2.b.iii.i Normal cells Atoll distributes traffic on the TCH service areas. The traffic capture is calculated with the option “Best signal level per HCS layer”. It means that there is an overlapping area between HCS layers. Let ),( TCHTxjSmacro

goverlappin denote the TCH service area of the macro layer overlapped by the TCH service area of the micro layer. Traffic on the overlapping area is distributed to the TCH subcell of the micro layer (higher priority layer). On this area, traffic of the micro layer may overflow to the macro layer. In this case, the traffic demand is the same on the TCH subcell of the micro layer but rises



on the TCH subcell of the macro layer. Note: Traffic overflowing on the macro layer is not uniformly spread over the TCH service area of Txj. It is only located

on the overlapping area. Atoll starts evaluating the traffic demand on the micro layer (highest priority HCS layer). For each circuit switched service, c, Atoll calculates the traffic demand, micro

mtcD ,, , in Erlangs in the subcell (Txi,TCH) service area.

( ) ( )TCHTxiETCHTxiD cmicro

mtc ,,,, = For each packet switched service, p, Atoll calculates the traffic demand, micro

mtpD ,, , in kbits/s in the subcell (Txi,TCH) service area.

( ) ( )TCHTxiTTCHTxiD pmicro

mtp ,,,, = Then, Atoll proceeds with the macro layer (lower priority HCS layer). For each circuit switched service, c, Atoll calculates the traffic demand, macro

mtcD ,, , in Erlangs in the subcell (Txj,TCH) service area.

( ) ( ) ( ) ( )( ) ( )TCHTxiO

TCHTxiSTCHTxjS

TCHTxiDTCHTxjETCHTxjD micro

macrogoverlappinmicro

mtccmacro

mtc ,,

,,,, max,,,, ××+=

For each packet switched service, p, Atoll calculates the traffic demand, macro

mtpD ,, , in kbits/s in the subcell (Txj,TCH) service area.

( ) ( ) ( ) ( )( ) ( )TCHTxiO

TCHTxiSTCHTxjS

TCHTxiDTCHTxjTTCHTxjD micro

macrogoverlappinmicro

mtppmacro

mtp ,,

,,,, max,,,, ××+=

Where ( )TCHTxiO ,max is the maximum rate of traffic overflow (in %) specified for the TCH subcell of Txi (micro cell) and

( )TCHTxiSmicro , the TCH service area of Txi.

XII.2.2.b.iii.ii Concentric cells Atoll evaluates the traffic demand on the micro layer as explained above in case of concentric cells and then proceeds with the macro layer (lower priority layer). The traffic capture is calculated with the option “Best signal level per HCS layer”. It means that there is overlapping areas between HCS layers where traffic is spread over according to the layer priority. On these areas, traffic of the higher priority layer may overflow.

S1

S2

S3 S’1

S’3

S’2



The TCH_INNER service area of the macro layer is overlapped by the micro layer. This area consists of two parts: an area overlapped by the TCH service area of the micro layer ( )( )INNERTCHTxjSmacro

TCHTxigoverlappin _,,− and another overlapped

by the TCH_INNER service area of the micro layer ( )( )INNERTCHTxjSmacroINNERTCHTxigoverlappin _,_,− .

Let us consider three areas, S1, S2 and S3.

( ) ( )( )INNERTCHTxjSINNERTCHTxjSS macroTCHTxigoverlappin

macro _,_, ,1 −−=

( ) ( )INNERTCHTxjSS macroINNERTCHTxigoverlappin _,_,2 −=

( ) ( ) 2,3 _, SINNERTCHTxjSS macroTCHTxigoverlappin −= −

Where ( )INNERTCHTxjSmacro _, is the TCH_INNER subcell service area of Txj. The traffic specified for Txj in the map description ( ( )TCHTxjEc , ) is spread over S1 proportionally to R1.

( )TCHTxjSSR map ,

11 =

( )TCHTxjSmap , is the TCH service area of Txj in the traffic map with the option “Best signal level of the highest priority

layer”. The traffic spread over the TCH_INNER service area of the micro layer may overflow to the TCH subcell. The traffic overflowing to the TCH subcell is located on the TCH_INNER service area. On S2 , the TCH subcell traffic coming from the TCH_INNER subcell traffic overflow may overflow proportional to R2.

( )INNERTCHTxiSSR micro _,

22 =

The traffic spread over the ring only served by the TCH subcell of the micro layer may overflow on S3 proportional to R3.

( ) ( )INNERTCHTxiSTCHTxiSSR micromicro _,,

33 −

=

For each circuit switched service, c, Atoll calculates the traffic demand, macro

mtcD ,, , in Erlangs in the subcell (Txj,TCH_INNER) service area.

( )( )

( ) ( ) ( )( ) ( )( )

( ) ( ) ( )+

××−×

×××+×

=

TCHTxiOTCHTxiETCHTxiS

INNERTCHTxiSTCHTxiSR

TCHTxiOINNERTCHTxiOINNERTCHTxiDRTCHTxjER

INNERTCHTxjD

cmicro

micromicro

micromtc

cmacro

mtc

,,,

_,,,_,_,

,_,

max3

maxmax,,2

1

,,


mtpD ,, , in kbits/s in the subcell (Txj,TCH_INNER) service area.

( )( )

( ) ( ) ( )( ) ( )( )

( ) ( ) ( )+

××−×

×××+×

=

TCHTxiOTCHTxiTTCHTxiS


TCHTxiOINNERTCHTxiOINNERTCHTxiDRTCHTxjTR

INNERTCHTxjD

pmicro

micromicro

micromtp

pmacro

mtp

,,,

_,,,_,_,

,_,

max3

maxmax,,2

1

,,

Where ( )TCHTxiO ,max is the maximum rate of traffic overflow (stated in %) specified for the TCH subcell of Txi,

( )INNERTCHTxiO _,max is the maximum rate of traffic overflow (stated in %) specified for the TCH_INNER subcell of Txi

and ( )TCHTxiSmicro , is the TCH subcell service area of Txi. The area of the TCH ring of the macro layer is overlapped by the micro layer. There are two parts: an area overlapped by



the TCH service area of the micro layer ( )( )INNERTCHTCHTxjSmacroTCHTxigoverlappin _,, −− and another overlapped by the

TCH_INNER service area of the micro layer ( )( )INNERTCHTCHTxjSmacroINNERTCHTxigoverlappin _,_, −− .

Let us consider three areas, S’1, S’2 and S’3.

( ) ( ) ( ) ( )INNERTCHTCHTxjSINNERTCHTxjSTCHTxjSS macroTCHTxigoverlappin

macromacro _,_,,' ,1 −−−= −

( )( )INNERTCHTCHTxjSS macroINNERTCHTxigoverlappin _,' _,2 −= −

( )( ) 2,3 '_,' SINNERTCHTCHTxjSS macroTCHTxigoverlappin −−= −

Where ( )TCHTxjSmacro , and ( )INNERTCHTxjSmacro _, are the TCH and TCH_INNER subcell service areas of Txj respectively. The traffic specified for Txj in the map description ( ( )TCHTxjEc , ) is spread over S’1 proportional to R’1.

( )TCHTxjSSR map ,

'' 11 =

( )TCHTxjSmap , is the TCH service area of Txj in the traffic map with the option “Best signal level of the highest priority

layer”. The traffic spread over the TCH_INNER service area of the micro layer may overflow to the TCH subcell. The traffic overflowing to the TCH subcell is located on the TCH_INNER service area. On S’2 , the TCH subcell traffic coming from the TCH_INNER subcell traffic overflow may overflow proportional to R’2.

( )INNERTCHTxiSSR micro _,

'' 22 =

The traffic spread over the ring only served by the TCH subcell of the micro layer may overflow on S’3 proportional to R’3.

( ) ( )INNERTCHTxiSTCHTxiSSR micromicro _,,

'' 33 −

=

For each circuit switched service, c, Atoll calculates the traffic demand, macro

mtcD ,, , in Erlangs in the subcell (Txj,TCH) service area.

( )

( )( ) ( )

( ) ( ) ( )( ) ( )( )

( ) ( ) ( )TCHTxiOTCHTxiETCHTxiS


TCHTxiOINNERTCHTxiOINNERTCHTxiDRINNERTCHTxjOINNERTCHTxjD

TCHTxjER

TCHTxjD

cmicro

micromicro

micromtc

macromtc

c

macromtc

,,,

_,,'

,_,_,'_,_,

,'

,

max3

maxmax,,2

max,,

1

,,

××−×

×××+×

+×

=


mtpD ,, , in kbits/s in the subcell (Txj,TCH) service area.

( )

( )( ) ( )

( ) ( ) ( )( ) ( )( )

( ) ( ) ( )TCHTxiOTCHTxiTTCHTxiS


TCHTxiOINNERTCHTxiOINNERTCHTxiDRINNERTCHTxjOINNERTCHTxjD

TCHTxjTR

TCHTxjD

pmicro

micromicro

micromtp

macromtp

p

macromtp

,,,

_,,'

,_,_,'_,_,

,'

,

max3

maxmax,,2

max,,

1

,,

××−×

×××+×

+×

=

Where ( )INNERTCHTxjO _,max is the maximum rate of traffic overflow (stated in %) specified for the TCH_INNER

subcell of Txj, ( )TCHTxiO ,max is the maximum rate of traffic overflow (stated in %) specified for the TCH subcell of Txi,

( )INNERTCHTxiO _,max is the maximum rate of traffic overflow (stated in %) specified for the TCH_INNER subcell of Txi,

( )TCHTxiSmicro , is the TCH subcell service area of Txi and ( )INNERTCHTxiSmicro _, is the TCH_INNER subcell service



area of Txi.

XII.3 NEIGHBOUR ALLOCATION The intra-technology neighbour allocation algorithm takes into account all the TBC transmitters. It means that all the TBC transmitters of the .atl document are potential neighbours. The transmitters to be allocated will be called TBA transmitters. They must fulfil the following conditions:

• They are active, • They satisfy the filter criteria applied to the Transmitters folder, • They are located inside the focus zone, • They belong to the folder for which allocation has been executed. This folder can be either the Transmitters

folder or a group of transmitters. Only TBA transmitters may be assigned neighbours. Note: If no focus zone exists in the .atl document, Atoll takes into account the computation zone.

XII.3.1 GLOBAL ALLOCATION FOR ALL TRANSMITTERS We assume a reference transmitter A and a candidate neighbour, transmitter B. When automatic allocation starts, Atoll checks following conditions:

1. The distance between both transmitters must be lower than the user-definable maximum inter-site distance. If the distance between the reference transmitter and the candidate neighbour is greater than this value, then the candidate neighbour is discarded.

2. The calculation options,

Force co-site transmitters as neighbours: This option enables you to force transmitters located on the reference transmitter site in the candidate neighbour list. Force adjacent transmitters as neighbours: This option enables you to force transmitters geographically adjacent to the reference transmitter in the candidate neighbour list. Force neighbour symmetry: This option enables user to force the reciprocity of a neighbourhood link. Therefore, if the reference transmitter is a candidate neighbour of another transmitter, the later will be considered as candidate neighbour of the reference transmitter. Force exceptional pairs: This option enables you to force/forbid some neighbourhood relationships. Therefore, you may force/forbid a transmitter to be candidate neighbour of the reference transmitter. Reset neighbours: When selecting the Reset option, Atoll deletes all the current neighbours and carries out a new neighbour allocation. If not selected, the existing neighbours are kept.

3. There must be an overlapping zone ( SS BA I ) with a given cell edge coverage probability where:

- SA is the area where the received signal level from the transmitter A is greater than a minimum signal level. SA is the coverage area of reference transmitter A restricted between two boundaries; the first boundary represents the start of the handover area (best server area of A plus the handover margin named “handover start”) and the second boundary shows the end of the handover area (best server area of A plus the margin called “handover end”) - SB is the coverage area where the candidate transmitter B is the best server.



refA

Best server area of refA

SA∩SB

canB

Best server area of canB

Handover endHandover start

Minimum signal level

Atoll calculates either the percentage of covered area ( 100×A

BA

SSS I ) if the option “Take into account Covered Area” is

selected, or the percentage of traffic covered on the overlapping area SS BA I for the option “Take into account Covered Traffic”. Then, it compares this value to the % minimum covered area (minimum percentage of covered area for the option “Take into account Covered Area” or minimum percentage of covered traffic for the option “Take into account Covered Traffic”). If this percentage is not exceeded, the candidate neighbour B is discarded. Candidate neighbours fulfilling coverage conditions are sorted in descending order with respect to percentage of covered area or covered traffic.

4. Atoll lists all neighbours and sorts them by priority so as to eliminate some of them from the neighbour list if the maximum number of neighbours to be allocated to each transmitter is exceeded. The neighbour priority depends on the neighbourhood cause. Priority assigned to each neighbourhood cause is indicated in the table below (1 is a higher priority than 2 and so on).

Neighbourhood cause

When Priority

Existing neighbour Only if the Reset option is not selected and in case of a new allocation 1

Exceptional pair Only if the Force exceptional pairs option is selected 2

Co-site transmitter Only if the Force co-site transmitters as neighbours option is selected 3

Adjacent transmitter Only if the Force adjacent transmitters as neighbours option is selected 4

Neighbourhood relationship that fulfils coverage conditions Only if the % minimum covered area is exceeded 5

Symmetric neighbourhood relationship Only if the Force neighbour symmetry option is selected 6 If there are 15 candidate neighbours and the maximum number of neighbours to be allocated to the reference transmitter is 8. Among these 15 candidate neighbours, only 8 (having the highest priorities) will be allocated to the reference transmitter. In the Results part, Atoll provides the list of neighbours, the number of neighbours and the maximum number of



neighbours allowed for each transmitter. In addition, it indicates the allocation cause for each neighbour. Therefore, a neighbour may be marked as exceptional pair, co-site, adjacent or symmetric. If the neighbour is not forced but fulfils coverage conditions, Atoll displays the percentage of covered area (or the percentage of covered traffic) and the overlap area (km2) (or the traffic covered on the overlap area in Erlangs) in brackets. Finally, if transmitters have previous allocations in the list, neighbours are marked as existing. Notes 1. No prediction study is needed to perform an automatic neighbour allocation. When starting an automatic

neighbour allocation, Atoll automatically calculates the path loss matrices if not found. 2. Atoll uses traffic map(s) selected in the default traffic analysis in order to determine the percentage of traffic

covered on the overlapping area. 3. The percentage of covered area (or the percentage of covered traffic) is calculated with the resolution specified in

the property dialog of the predictions folder (Default resolution parameter). 4. When the option “Force adjacent transmitters as neighbours” is used, the margin “handover start” is not taken into

account. Atoll considers a fixed value of 0 dB. 5. A forbidden neighbour must not be listed as neighbour except if the neighbourhood relationship already exists and

the Reset neighbours option is unchecked when you start the new allocation. In this case, Atoll displays a warning in the Event viewer indicating that the constraint on the forbidden neighbour will be ignored by algorithm because the neighbour already exists.

6. The force neighbour symmetry option enables the users to consider the reciprocity of a neighbourhood link. This reciprocity is allowed only if the neighbour list is not already full. Thus, if transmitter B is a neighbour of the transmitter A while transmitter A is not a neighbour of the transmitter B, two cases are possible:

1st case: There is space in the transmitter B neighbour list: the transmitter A will be added to the list. It will be the last one.

2nd case: The transmitter B neighbour list is full: Atoll will not include transmitter A in the list and will cancel the link by deleting transmitter B from the transmitter A neighbour list.

7. When the options “Force exceptional pairs” and “Force symmetry” are selected, Atoll considers the constraints between exceptional pairs in both directions so as to respect symmetry condition. On the other hand, if neighbourhood relationship is forced in one direction and forbidden in the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the Event viewer.

8. In the Results, Atoll displays only 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.

XII.3.2 ALLOCATION FOR A GROUP OF TRANSMITTERS In this case, Atoll allocates neighbours to:

- TBA transmitters, - Neighbours of TBA transmitters marked as exceptional pair, adjacent and symmetric, - Neighbours of TBA transmitters that satisfy coverage conditions.

XII.4 INTERFERENCE PREDICTION STUDIES

XII.4.1 COVERAGE STUDIES Two interference studies with predefined settings are available:

1. The coverage by C/I level study: This study provides you a global analysis of the network quality, 2. The interfered areas study: This study shows the areas where a transmitter is interfered by other ones.

In both cases, Atoll calculates C/I ratio on each calculation bin where conditions on signal level reception are satisfied. Then, it either considers the bins where the calculated C/I exceeds a lower threshold in the coverage and colours these bins depending on C/I value (coverage by C/I level study), or it considers the bins where the calculated C/I is lower than a upper threshold in the coverage and colours them depending on colour of the interfered transmitter (interfered areas study). All the TBC transmitters are taken into account in these studies. Let us assume that each bin within each TBC transmitter calculation area corresponds to a probe mobile receiver. Coverage study parameters to be set are:

- The study conditions in order to determine the coverage area of each TBC transmitter - The display settings to select how to colour coverage areas.

Note: For information on the common prediction studies (like coverage by transmitter, profile study, …), please, refer to

Common prediction studies part.



XII.4.1.a SERVICE AREA DETERMINATION The areas, where Atoll will calculate C/I, depend on signal level reception conditions. Atoll uses the parameters entered in the Conditions tab in order to determine service area of each TBC transmitter. We can distinguish four cases: Here we presume that:

- Each transmitter, Txi, belongs to a hierarchical cell structure (HCS) layer, k, with a defined priority. - The maximum range option (available in the System tab of the Predictions property dialog) is inactive.

XII.4.1.a.i All the servers For each HCS layer, k, the service area of Txi corresponds to the bins where:

threshold Maximum)(threshold Minimum <≤ ttPTxirec

XII.4.1.a.ii Best signal level per HCS layer and a margin For each HCS layer, k, the service area of Txi corresponds to the bins where:


and ( ) ( )( ) MBCCHPBestBCCHP Txj

recij

Txirec −≥

≠

where, M is the specified margin (dB). Best function: considers the highest value.

XII.4.1.a.iii Best signal level of the highest priority HCS layer and a margin In this case, the service area of Txi corresponds to the bins where:



recij

Txirec −≥

≠

and Txi belongs to the HCS layer with the highest priority

where, M is the specified margin (dB). Best function: considers the highest value.

XII.4.1.a.iv 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:



recij

ndTxirec −≥

≠2

where, M is the specified margin (dB). 2nd Best function: considers the second highest value.

Note: When the maximum range option is selected, Atoll searches for interference on the bins: - Where the respective criteria described above are checked, and - Located within a specified distance from the transmitter (maximum range).

XII.4.1.b CARRIER TO INTERFERENCE RATIO CALCULATION Atoll works out carrier to interference ratio on each bin of transmitter service areas. In order to understand the difference between each frequency hopping mode from the mobile point of view, it is interesting to consider the Mobile Station Allocation (MSA). MSA is characterised by the pair (Channel list, MAIO). When a non hopping (NH) mode is used, channel list is a channel while it corresponds to the mobile allocation list (MAL) in case of base band hopping (BBH) or synthesised frequency hopping (SFH). For BBH, channels of MAL belong to a unique TRX type. Examples:



For each example given below, we assume that. In case of NH, we have:

TRX index Channel list MAIO MSA 1 53 * (53,*) 2 54 * (54,*)

In case of BBH, assuming TRXs belong to the same TRX type, we have:

TRX index Channel list MAIO MSA 1 53 * ([53,54,55],0) 2 54 * ([53,54,55],1) 3 55 * ([53,54,55],2)

In case of SFH, we have:

TRX index Channel list MAIO MSA 1 53 54 55 56 2 ([53,54,55,56],2) 2 53 54 55 56 3 ([53,54,55,56],3)

Therefore, for a mobile station, BBH and SFH work in the same way. Consider the following notations: v is a victim transmitter (TBC transmitter with a service area), MSAS(v) is the set of MSAs associated to v. The number of MSAS(v) depends on TRX type(s) to be analysed (option available in study properties): you may study a given TRX type tt (There are as many MSA(v) as TRXs allocated to the subcell (v,tt)) or all the TRX types (The number of MSA(v) corresponds to the number of TRXs allocated to v), i is a potential interfering transmitter (TBC transmitters which calculation area intersects service area of v), MSAS(i) is the set of MSAs related to potential interferers i, INT(v) is the set of transmitters that interfere v. Several MSAs, m, are related to a transmitter. Therefore, for each victim transmitter v with MSA m (m ∈ MSAS(v)), Atoll

calculates carrier to interference ratio

)()(

mImC

v

v

, received at the mobile; mobile is connected to a victim transmitter, v

with a given m. )(mCv is the carrier power level received from v on m and )(mIv corresponds to the interference received from interfering transmitters i on m. Atoll studies the most interfered MSA. So, it considers:

=

)()(

mImC

MinIC

v

v

kv

except if analysis is detailed (Detailed result option).

XII.4.1.b.i Carrier power level )()( mPmC v

recv =

XII.4.1.b.ii Interference calculation Potential interferers can be transmitters i (i≠v), using co-channels and/or adjacent channels. Therefore, we can write:

)()()( mImImI vadj

vco

v +=

)(mIvco is the interference received at v on m due to co-channels.

)(mIvadj is the interference received at v on m due to adjacent channels.

)()()()(

)( )(

,, nTnPpmI i

irecco

vINTi iMSASn

ivnm

vco ××= ∑ ∑

∈ ∈

and

)()()()()( )(

,, nT

FnPpmI i

irec

adjvINTi iMSASn

ivnm

vadj ××= ∑ ∑

∈ ∈



ivnmp ,, is the probability of having a co- or adjacent channel collision between MSAs n and m (when n and m contain co-

and adjacent channels). It depends on the used frequency hopping mode. )(nP i

rec is the carrier power level received from i on n, Ti(n) is occupancy of the MSA n.

)()()( nfnLnT iact

itraffici ×=

If “Average” is selected in the study properties, )(nLi

traffic is the traffic load defined for the MSA n of i. If “Maximum” option

is selected, 1)( =nLitraffic .

)(nf iact is the activity factor defined for the MSA n of i. If the subcell (i,tt) supports DTX mode, it is a global value specified

in the study properties. Otherwise, the activity factor is 1.

XII.4.1.b.iii Collision probability for non hopping mode We have:

1,, =ivnmp

XII.4.1.b.iv Collision probability in case of BBH or SFH MSA m of v can be defined as the pair ([f1,f2,….fn], MAIO) and MSA n of i as the pair ([f’1,f’2,….f’n], MAIO’) (where f and f’ are channels).

Now, let us consider the occurrence, )',( i

nv

m ffOCCUR , such that a channel f of m can meet a channel f’ of n during hopping sequence. There is a collision if f and f’ are co- or adjacent channels. Then, we can define a collision as follows:

)',( in

vm ffOCCURCollision = such that τ=− i

nv

m ff '

(τ equals 0 if vmf and i

nf ' are co-channels or 1 if adjacent channels) Therefore, we have:

occurence

collisionivnm n

np =,,

ncollision and noccurence respectively correspond to the number of collisions and the number of occurrences. They are closely linked to the correlation between m and n. We can have two cases: 1st case: MSAs m and n are correlated m and n must have identical HSN and synchronisation. The number of occurrences depends on the MAL size, MAIO And MAIO’. Example:

Schematic view of hopping sequences MSA m of v

([34 37 39], MAIO=0) 34 3377 39

MSA n of i ([38 36 34], MAIO’=2) 3388 36 34

Here, the number of occurrences is 3; the number of co-channel collisions is 1 and the number of adjacent channel collisions is 1.

So, we have:

31)( ,

, =coivnmp and

31)( ,

, =adjivnmp

2nd case: MSAs m and n are not correlated Condition specified above is not fulfilled. Probability to have each pair is the same. All the occurrences are possible.



Example: Schematic view of hopping sequences

MSA m of v ([34 37 39], MAIO=0)

34 37 39

MSA n of i ([38 36 34], MAIO’=2)

38 36 34

Here, the number of occurrences is 9; the number of co-channel collisions is 1 and the number of adjacent channel collisions is 3.

So, we have:

91)( ,

, =coivnmp

and 31)( ,

, =adjivnmp

Note: Only the carrier power level is downgraded by the shadowing margin. The interference level is not altered.

XII.4.1.c COVERAGE AREA DETERMINATION

For each victim transmitter v, coverage area corresponds to bins where vI

C

is between lower and upper thresholds

specified in study properties.

XII.4.1.d COVERAGE AREA DISPLAY You can display the transmitter coverage area depending on the C/I level, prefer a display depending on transmitter colour or on any other transmitter attribute .

• C/I level Each bin of the transmitter coverage area is coloured if the calculated C/I level exceeds (≥) the specified minimum thresholds (bin colour depends on C/I level). Coverage consists of several independent layers whose visibility in the workspace can be managed. There are as many layers as transmitter coverage areas. Each layer shows the different C/I levels available in the transmitter coverage area.

• Max C/I level Atoll compares calculated C/I levels received from transmitters on each bin of each transmitter coverage area where coverage areas overlap the studied one and chooses the highest value. A bin of a coverage area is coloured if the C/I level exceeds (≥) the specified thresholds (the bin colour depends on the C/I level). Coverage consists of several independent layers whose visibility in the workspace can be managed. There are as many layers as defined thresholds. Each layer corresponds to an area where the highest received C/I level exceeds a defined minimum threshold.

• Min C/I level Atoll compares C/I levels received from transmitters on each bin of each transmitter coverage area where the coverage areas overlap the studied one and chooses the lowest value. A bin of a coverage area is coloured if the C/I level exceeds (≥) the specified thresholds (the bin colour depends on the C/I level). Coverage consists of several independent layers whose visibility in the workspace can be managed. There are as many layers as defined thresholds. Each layer corresponds to an area where the lowest received C/I level exceeds a defined minimum threshold.

• Transmitter Atoll colours each bin of each transmitter coverage area. The bin colour corresponds to the transmitter colour. Coverage consists of several independent layers whose visibility in the workspace can be managed. There are as many layers as interfered transmitters.

XII.4.2 POINT ANALYSIS Analysis provided in the Interference tab is based on path loss matrices. You can study interference on:

- TBC transmitters for which path loss matrices have been computed, - calculation areas.

Atoll indicates the following at the receiver:

- The carrier power level received from the victim transmitter v on the most interfered MAS m, - Either the overall interference received from interfering transmitters i on MAS m (both co-channel and adjacent

channel interferers are considered), or the co-channel interference received from co-channel interfering transmitters i on MAS m, or the adjacent channel interference received from adjacent channel interfering transmitters i on MAS m (for further information about noise calculation, please refer to Signal to noise



calculation: noise calculation part) - The interference level received from each interfering transmitter i on m. Interferers are sorted in a descending

order w.r.t. carrier power level. Notes: 1. Neither DTX nor traffic load of TRXs are taken into account to evaluate interference levels.

Therefore, we have 1)()()( =×= nfnLnT iact

itraffici .

2. Only carrier power level is downgraded by the shadowing margin. The interference level is not altered.

XII.5 GPRS EGPRS COVERAGE STUDIES Atoll calculates a coverage area for all the TBC EGPRS transmitters. Let us assume that each bin within a TBC EGPRS transmitter calculation area corresponds to a probe mobile receiver. Coverage study parameters to be set are:

- The study conditions in order to determine the coverage area of each TBC transmitter, - The display settings to select how to colour coverage areas.

XII.5.1 COVERAGE AREA DETERMINATION We can have four cases: Let us presume that: - Each transmitter, Txi, belongs to a HCS layer, k, with a defined priority. - Each transmitter, Txi, is a GPRS/EGPRS station (Txi-EGPRS as notation). - GPRS/EGPRS equipment installed on each transmitter, Txi, does not support 8PSK modulation. - The maximum range option (available in the System tab of the Predictions property dialog) is inactive.

XII.5.1.a ALL THE SERVERS For each HCS layer, k, the coverage area of Txi corresponds to Txi calculation area.

XII.5.1.b BEST SIGNAL LEVEL PER HCS LAYER AND A MARGIN For each HCS layer, k, the coverage area of Txi corresponds to the bins where the signal level received from Txi,

)(BCCHP EGPRSTxirec

− , is the highest one (Txi is the best server) or within a defined margin of the highest signal level (within a margin of the best server). Note: If the margin equals 0, the coverage area of Txi corresponds to the bins where )(BCCHP EGPRSTxi

rec− is the highest.

XII.5.1.c SECOND BEST SIGNAL LEVEL PER HCS LAYER AND A MARGIN For each HCS layer, k, the coverage area of Txi corresponds to the bins where the signal level received from Txi,

)(BCCHP EGPRSTxirec

− , is the second highest one (Txi is the second best server) or within a defined margin of the second highest signal level (within a margin of the second best server). Note: If the margin equals 0, the coverage area of Txi corresponds to the bins where )(BCCHP EGPRSTxi

rec− is the second

highest.

XII.5.1.d BEST SIGNAL LEVEL OF THE HIGHEST PRIORITY LAYER AND A MARGIN In this case, the coverage area of Txi corresponds to the bins where:

)(BCCHP EGPRSTxirec

− is the highest one (Txi is the best server) or within a defined margin of the highest signal level (within a margin of the best server),

And Txi belongs to the HCS layer with the highest priority.



XII.5.2 CALCULATION OPTIONS EGPRS studies can be based either on signal level (C) or on the signal (C) and interference levels (C/I) both.

XII.5.2.a CALCULATIONS BASED ON C In this case, only signal level reception is taken into account. Atoll evaluates the signal level received from GPRS/EGPRS transmitters on TRXs (TRX) belonging to the selected TRX type (tt) or on all the TRXs, )(TRXP EGPRSTxi

rec− .

XII.5.2.b CALCULATIONS BASED ON C AND C/I EGPRS studies are based on the received signal and C/I levels. Atoll evaluates:

- The signal level received from EGPRS transmitters on TRXs (TRX) belonging to the selected TRX type (tt) or on all the TRXs, )(TRXP EGPRSTxi

rec− .

And - The carrier to interference ratio received on TRXs (TRX) belonging to the selected TRX type (tt) or on all the

TRXs, I

TRXP EGPRSTxirec )(−

.

For further information about I calculation, please refer to Interference prediction studies: Interference calculation part.

XII.5.3 COVERAGE DISPLAY Coverage area can be displayed with colours depending on:

XII.5.3.a CODING SCHEMES

XII.5.3.a.i Calculations based on C Atoll calculates signal level received from Txi on each bin of Txi coverage area. Atoll selects a coding scheme, cs, such that:

For each TRX type, tt, ( ) ( )sholdPower ThreTRXPEquipment

csEGPRSTxi

rec >−

Only the bins with a coding scheme assigned are coloured (the bin colour depends on the assigned coding scheme). Coverage consists of several independent layers whose visibility in the workspace can be managed. There are as many layers as transmitter coverage areas. Each layer shows the coding schemes to be used in the transmitter coverage area.

XII.5.3.a.ii Calculations based on C and C/I Atoll calculates signal level and C/I level received from the transmitter on each bin of each Txi coverage area, for each TRX. For each TRX, Atoll selects a coding scheme, cs, such that:

( ) ( )sholdPower ThreTRXPEquipment

csEGPRSTxi

rec >−

And

( )hresholdse ratio tSignal noiITRXP Equipment

cs

EGPRSTxirec >

− )(

Then, Atoll considers the lowest coding scheme. Only the bins with a coding scheme assigned are coloured (the bin colour depends on the assigned coding scheme). Coverage consists of several independent layers whose visibility in the workspace can be managed. There are as many layers as transmitter coverage areas. Each layer shows the coding schemes to be used in the transmitter coverage area.



XII.5.3.b BEST CODING SCHEMES

XII.5.3.b.i Calculations based on C Atoll calculates signal levels received from transmitters on each bin of each Txi coverage area, where coverage areas overlap the studied one. For each transmitter, Atoll selects a coding scheme, cs, such that:

For each tt, ( ) ( )sholdPower ThreTRXPEquipment

csEGPRSTxi

rec >−

Then, on each bin, it chooses the best coding scheme (the best possible). Only the bins with a coding scheme assigned are coloured (the bin colour depends on the assigned coding scheme). Coverage consists of several independent layers whose visibility in the workspace can be managed. There are as many layers as possible coding schemes. Each layer shows the areas where a given coding scheme can be used.

XII.5.3.b.ii Calculations based on C and C/I Atoll calculates signal levels and C/I levels received from transmitters on each bin of each Txi coverage area, where coverage areas overlap the studied one, on each TRX. For each TRX of each transmitter, Atoll selects a coding scheme, cs, such that:

( ) ( )sholdPower ThreTRXPEquipment

csEGPRSTxi

rec >−

And

( )hresholdse ratio tSignal noiITRXP Equipment

cs

EGPRSTxirec >

− )(

For each transmitter, Atoll only considers the lowest coding scheme. Then, on each bin, it chooses the best coding scheme (the best possible). Only the bins with a coding scheme assigned are coloured (the bin colour depends on the assigned coding scheme). Coverage consists of several independent layers whose visibility in the workspace can be managed. There are as many layers as possible coding schemes. Each layer shows the areas where a given coding scheme can be used.

XII.5.3.c RATE/TIMESLOT

XII.5.3.c.i Calculations based on C Atoll calculates the signal level received, ( )TRXP EGPRSTxi

rec− , from the transmitter on each bin of each Txi coverage area

and selects a coding scheme, cs, as explained above (Display per coding scheme). Then, from the C=f(rate) graph associated to cs, it evaluates the rate corresponding to ( )TRXP EGPRSTxi

rec− . A bin of a coverage area is coloured if the

calculated rate exceeds the defined minimum thresholds (bin colour depends on rate). Coverage consists of several independent layers whose visibility in the workspace can be managed. There are as many layers as transmitter coverage areas. Each layer shows the rates that a transmitter can provide on one timeslot.

XII.5.3.c.ii Calculations based on C and C/I On each bin of each Txi coverage area, Atoll calculates the signal level and C/I level received from the transmitter on

each TRX (respectively, ( )TRXP EGPRSTxirec

− and I


) and selects a coding scheme, cs, as explained above

(Display per coding scheme). Then, from the C=f(rate) and C/I=f(rate) graphs associated to cs, it evaluates the rates

corresponding to ( )TRXP EGPRSTxirec

− and I


, and chooses the lowest one. A bin of a coverage area is

coloured if the calculated rate exceeds the defined minimum thresholds (bin colour depends on rate). Coverage consists of several independent layers whose visibility in the workspace can be managed. There are as many layers as transmitter coverage areas. Each layer shows the rates that a transmitter can provide on one timeslot.



XII.5.3.d BEST RATE/TIMESLOT

XII.5.3.d.i Calculations based on C Atoll calculates signal levels received from transmitters, ( )TRXP EGPRSTxi

rec− , on each bin of each Txi coverage area, where

coverage areas overlap the studied one. For each transmitter, Atoll selects a coding scheme, cs, as explained above (Display per coding scheme) and evaluates the rate corresponding to ( )TRXP EGPRSTxi

rec− from the C=f(rate) graph

associated to cs. Then, it chooses the best rate (the highest one). A bin of a coverage area is coloured if the best rate exceeds the defined minimum thresholds (bin colour depends on rate). Coverage consists of several independent layers whose visibility in the workspace can be managed. There are as many layers as defined thresholds. Each layer shows the areas where a rate can be provided on one timeslot.

XII.5.3.d.ii Calculations based on C and C/I Atoll calculates signal levels and C/I levels received from transmitters on each bin of each Txi coverage area, where

coverage areas overlap the studied one, on each TRX (respectively, ( )TRXP EGPRSTxirec

− and I


). For each

transmitter, Atoll selects a coding scheme, cs, as explained above (Display per coding scheme) and evaluates the rates

corresponding to ( )TRXP EGPRSTxirec

− and I


from the C=f(rate) and C/I=f(rate) graphs associated to cs, and

takes the lowest one. Then, on each bin, it chooses the best rate (the highest one). A bin of a coverage area is coloured if the best rate exceeds the defined minimum thresholds (bin colour depends on rate). Coverage consists of several independent layers whose visibility in the workspace can be managed. There are as many layers as defined rate thresholds. Each layer shows the areas where a rate can be provided on one timeslot. Note: When selecting the “calculation based on C/I” option in GPRS/EGPRS prediction studies, Atoll calculates the

carrier to interference ratio for all the EGPRS TBC transmitters but takes into account all the TBC transmitters (GSM and GPRS/EGPRS) to evaluate the interference, I.

C H A P T E R 13

AFP This chapter details the cost function used by the Atoll AFP module and its BSIC allocation algorithm.

13

AFP


XIII AFP

XIII.1 OVERVIEW The Atoll Automatic Frequency Planning (AFP) module enables users to automatically generate frequency plans for GSM and TDMA networks. The AFP module can allocate the following parameters:

- Frequencies, - Frequencies hopping groups (MAL), - HSN, MAIO, - BSIC.

The AFP aims at generating optimal allocations, i.e. allocations that minimize interference over the network and comply with a set of constraints defined by the user. The two main constraints are the separation constraints, and the spectrum limitations. Allocation of the first three types of resources (frequencies, MAL, HSN and MAIO) is based on a ‘cost function’. The aim of this algorithm is to find the allocation with the minimum cost. The cost function takes into account all the requirements provided as network inputs, described in the first part of this chapter. The second part focuses on algorithm used for the BSIC allocation. For further information on the generic use of AFP (parameters to set for any AFP model, the different steps of AFP and outputs), refer to user manual (GSM/TDMA project management - GSM/TDMA network optimisation - GSM/TDMA generic AFP management). For further information on the Atoll AFP model (global description of cost function components and parameters available in the model property dialog), please refer to user manual (GSM/TDMA project management). AFP can be carried out either on all the transmitters from the Transmitters folder context menu, or on a group of transmitters from the group’s subfolder context menu. When starting AFP, Atoll loads:

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

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

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

Notes: 1. In case of the BSIC allocation, neighbours of neighbours are systematically loaded. 2. If no focus zone exists in the .atl document, Atoll takes into account the computation zone. The calculated cost takes into account all the loaded transmitters. It is the same for BSIC allocation. On the other hand, resources are assigned to TBA transmitters only. Other loaded transmitters are considered as “frozen” for all types of assignments: BSIC, HSN, MAL, MAIO and channels.

XIII.2 DESCRIPTION OF THE COST FUNCTION The cost function is stated in Erlangs. It corresponds to the cost of the entire loaded network. In fact, each loaded TRX is assigned a status, either valid, corrupted or missing. The Atoll AFP algorithm calculates a cost for each TRX according to its status. Therefore, we can distinguish three types of costs:

- The cost of a valid TRX based on two components, a cost component due to separation violations and a cost component due to interferences,

- The cost of a missing TRX, - The cost of a corrupted TRX.

Then, in order to evaluate the global cost, the Atoll AFP algorithm sums up the cost of each TRX. The cost of a TRX is considered only once. A TRX is considered missing if it is required by a subcell but undefined. Let us imagine a transmitter involved in AFP for which the number of required TRX is 5. This transmitter is not a TBA transmitter having 3 currently assigned TRXs. In which case, the two missing and undefined TRXs have to be considered for the allocation because they would have an effect on the current frequency plan if allocated. A TRX is considered corrupted when:

- It contains out of domain frequencies,



- An allocated frequency does not respect the frequency domain constraints, - More than one frequency is assigned to a NH TRX, - No channel is assigned to a TRX, - The MAL assigned to a group constrained SFH TRX is not strictly a group of its domain, - A SFH TRX has no MAIO or HSN.

XIII.2.1 NOTATIONS We will use notations listed hereafter to describe the cost function: TRG: for the subcell notion. We denote “number of” by #, (For example, # TRXs corresponds to the number of TRXs) The relation “if and only if” by “⇔”, The size of the group g by g , The set of all the frequencies by ARFCN, The set of all the subsets of frequencies by ARFCN2 , The set of all the TRGs by “TRGs”, And the biggest integer x≤ by x (x can be a real number). Let giA , denote the number of times a group ARFCNg 2∈ is assigned to TRGi, in the assignment A. For example:

• When i is NH, 1, =giA ⇔ g is a single member group containing one of the frequencies assigned at TRGi.

If |g| is not 1 or if g does not contain a frequency assigned at i, then 0, =giA .

• When i uses BBH, giA , can be either 0 or # TRXi.

igi TRXA # , = ⇔ g is the set of frequencies assigned toTRXs of TRGi. When we talk about “TRXs of i using g”, and in the case of BBH, then there are |g| such virtual TRXs.

• When i uses SFH, giA , must be iTRX#≤ . nA gi =, ⇔ g is the set of frequencies assigned to n TRXs of TRGi. We assume all the groups assigned to TRGi have the same length.

TSi denotes the number of timeslots available for each TRX in TRGi. TLi is the traffic load of the TRGi. This parameter may either be calculated during dimensioning or specified by user. ( ErlangsTLi # = using a single TRX in TRGi , divided by TSi) TSUi refers to the downlink timeslot use ratio (due to DTX and AMR) at TRGi. CFi is the coast factor of TRGi. QMINi is the minimum required quality (in C/I) at TRGi. PMAXi is the percentage that is permitted to have quality lower than QMINi, at TRGi. REQi corresponds to the required number of TRXs at TRGi. A communication uses the group g in TRGi if its mobile allocation is g. The probability of being interfered is denoted by

( )AP gii ,', (i’ is the TRX index - different TRX indexes may have different MAIOs). ( )AP gii ,', is a function of the whole frequency assignment. We will give a more precise definition of what it is “to be interfered” later. The probability of violating a separation constraint is ( )AP gii

',', . It is a function of the whole frequency assignment as well.

In the description, we will use the term “Atom”. ATOM(i) will be the same as ATOM(k) if and only if the two TRGs (i and k) are synchronized, have the same HSN, the same length of MAL, and the same hopping mode. Non Hopping TRGs or BBH TRGs are always in separate atoms. If two TRGs are not in the same atom but are interfering, then they can be considered as unsynchronised. If not synchronised, their quality is a function of all possible frequency combinations. If synchronised, we know the frequency pairs emitted together and the pairs that are not. GAIN(TSUk) is a user defined table that translates TSUk (TSU = timeslot usage) into a gain in dB.

XIII.2.2 COST FUNCTION The AFP cost function calculated by Atoll is a TRX based cost and not an interference matrix entry based cost. It counts the interfered traffic of a TRX in Erlangs once. The cost function Ψ is defined below:

AFP


( ) iiiTRGsi

TRXsig

giii TSCFTLATRXMISARFCN

×××

+×=Ψ ∑ ∑∈

∈∈

g using i of '2

,',_ δλ

i’ is the TRX index, belonging to 1-A 0,1, gi,… . As said above, in case of BBH, it is a virtual TRX.

iTRXMIS _ is the number of missing TRXs for the subcell i.

−= ∑

∈ ARFCNggiii AREQMAXTRXMIS

2,,0_

λ is the cost value for a missing TRX. This value can be between 0 and 10. The default cost value is 1 and can be modified in the AFP module property dialog.

If i’ is corrupted:

( ) Ω=Agii ,',δ

Ω is the cost value when a TRX is corrupted. This value can be between 0 and 10. The default cost value is 10 and can be modified in the AFP module property dialog.

If i’ is valid, the algorithm evaluates the cost of a valid TRX, ( )AP gii ,'," .

( ) ( ) ( )( )[ ]APAPMAXAP giigiigii'

,',,',,', ,1" ×+×= γα

( )AP gii ,', is the interference cost component (probability of being interfered).

( )AP gii'

,', is the separation violation cost component (probability of being interfered according to the separation constraints). α is the weight of the interference cost component. This value can be between 0 and 1. The default weight is 0.35 and can be modified in the AFP module property dialog. γ is the weight of the separation violation cost component. This value can be between 0 and 1. The default weight is 1 and can be modified in the AFP module property dialog.

If the option “Take into account the cost of all the TRXs” available in the AFP module property dialog is selected:

( ) ( )APA giigii"

,',,', =δ

Else if the option “Do not include the cost of TRXs having reached their quality target” available in the AFP module property dialog is selected, the algorithm compares ( )AP gii ,'," to the quality target specified for i, MAXiP .

If ( ) MAXigii PAP >,'," , then ( ) ( )APA giigii"

,',,', =δ

If ( ) MAXigii PAP ≤,'," , then ( ) 0,', =Agiiδ

XIII.2.3 COST COMPONENTS Separation violation and interference cost components are described hereafter. 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), while others can be managed inside the property dialog of the Atoll AFP model such as separation costs and diversity gains.

XIII.2.3.a SEPARATION VIOLATION COST COMPONENT The separation violation cost component is evaluated for each TRX. Estimation is based on costs specified for the required separations. Let kiCONSTRSEP ,_ denote the required separation constraint between TRGi and TRGk. Let zsCost , denote the user defined cost for a separation constraint violation when the required separation is “s” and the

actual separation is “z”. We will use vkiSEP ,, to represent ZCONSTRSEP kiCost ,_ ,

.



Note: In the AFP model property dialog, the user may enter a percentage, while here we use a probability. We consider ''' kggiiξ to be the separation violation of the i’th TRX in TRGi, assigned to the group g and being violated by the assignment Ak,g’. If ( ) ( )kATOMiATOM ≠

Then '

' ''

',,',

'' gg

SEPA

gfgf

ffkigk

kggii ×

×

=

∑∈∈

−

ξ

If ( ) ( )kATOMiATOM =

Then

∑ ∑∈ −∈

−

=

',,_' 1_,...1,0_',,'' _'

ikiEXSETk NFnfggkikggii FNSEP

τυξ

Let ',,_ ikiEXSET be the set of all the TRXs using g’ in TRGk. If ki = , this set will exclude i’ itself, so as not to consider the interference of a TRX with itself. Let ( )gNF _ be the number of frames in the MAL g. ( ) ggNF =_ .

Since ( ) ( )'__ gNFgNF = , we shortly denote the two as NF _ .

Let nf _ denote the frame number from 0 to NF _ . While ( )

',,_

igiAMAIOnf +=υ modulo NF _ and υg is the thυ frequency in g,

And ( )',',

_kgkAMAIOnf +=τ modulo NF _ and τ'g is the thττ frequency in g’,

Furthermore, frequencies that are part of a MAL with a low fractional load and that break a separation constraint should not be weighted the same as in a non-hopping separation breaking case. Therefore, the cost is weighted by an interferer diversity gain.

( )( )gDIVI

kiG _1.0, 101ˆ ×=

Where

( )gDIVI _ is the interferer diversity gain (dB) user-defined for each MAL length. It is used in the ( )AP gii ,', definition as well.

For each single TRX, separation violations are summed up. This sum is limited to 100% of the TRX traffic. Therefore, we have:

( )

×= ∑∈

≠∈ARFCNg

ikTRGskikggiigii GMinAP

2',

'''

,',ˆ',1 ξ

XIII.2.3.b INTERFERENCE COST COMPONENT The interference cost component is evaluated for each TRX. Estimation is based on interference histograms calculated for pairs of subcells. In addition, it takes into account frequency and interferer diversity gains, and models frequency hopping and gain due to DTX. Note: Interference histograms are described in user manual (GSM/TDMA project management - GSM/TDMA network

optimisation - GSM/TDMA generic AFP management). They can be exported to files. For further description of these files, refer to part X.6 of this document.

When trying to estimate ( )AP gii ,', , we encounter the following problems:

• The QMINi C/I quality indicator corresponds to the accumulated interference level of all interferers while the C/I interference histograms correspond to pair-wise interferences. • Both QMINi and the histograms correspond to a single frequency. In case of a MAL containing more than one frequency, we must combine interferences on several different frequencies of a MAL.

AFP


The estimation we present below is the simplest possible estimation since it solves the first problem by linear sum and truncation at the value of 1. It solves the second problem by averaging and adding two diversity gains: ( )gDIVF _

standing for frequency diversity gain, and ( )gDIVI _ standing for interferer diversity gain. Let ( )gNF _ be the number of frames in the MAL g. ( ) ggNF =_ . Let nf _ denote the frame number from 0 to NF _ . Let

jgkAMAIO',,

be the j’th MAIO of ',gkA , j is one of the 1-A 0,1, g'k,… TRXs.

The value of jgkAMAIO

',, is one of ' 0,1, g…

If the TRGk is NH, then 0,',

=jgkAMAIO .

If the TRGk uses BBH, then jMAIOjgkA =

,',.

As said above, in case of BBH, we consider 'g virtual TRXs, the jth TRX has the MAIO j.

Let ig be the ith frequency in the group g. We consider ''' kggiiξ : If ( ) ( )kATOMiATOM ≠

Then

×

<

×= ∑∈∈ '',

',,,

','' '

_Pr

gfgf

ffkiik

gkkggii gg

UBQICobability

Aξ

Where ( ) ( ) ( ) kiffki TSUGAINgDIVIgDIVFSUPADJffQMINUBQ +++×−−= ___'_ ',,, If ( ) ( )kATOMiATOM = Then: Let ',,_ ikiEXSET be the set of all TRXs using g’ in TRGk. if ki = , this set will exclude i’ itself, so as not to consider the interference of a TRX with itself.

Since ( ) ( )'__ gNFgNF = we shortly denote the two as NF _ .

( )

∑ ∑∈ −∈

<=

',,_' 1_,...,1,0_',,,'' __Pr

ikiEXSETk FNnfffkiikkggii NFUBQICobabilityξ

Where

υgf = ,

τ'' gf = ,

( )',,

_igiAMAIOnf +=υ modulo FN _ ,

( )',',

_kgkAMAIOnf +=τ modulo FN _ ,

( ) ( ) ( ) kiffki TSUGAINgDIVIgDIVFSUPADJffQMINUBQ +++×−−= ___'_ ',,,

Therefore, we have:

( )

= ∑∈∈

ARFCNgTRGsk

kggiigii MinAP

2'

'',', ,1 ξ

The sum is limited to 100% of the TRX traffic.



XIII.3 BSIC ALLOCATION The BSIC allocation algorithm takes into account the following constraints:

- Neighbourhood links between transmitters, It considers:

• The existing neighbours listed in the neighbours list if neighbour allocation has been performed beforehand,

• The neighbours of listed neighbours,

- Interferences between transmitters if the option “Load all the potential interferers” (available when starting AFP) is selected and then, interference histograms are imported/calculated,

In addition, BSIC allocation is compliant with the BSIC domains of transmitters and the strategy indicated in the BSIC tab of the AFP module property dialog. Either the algorithm selects a minimum number of BSICs in the related BSIC domain (Minimal option), or it chooses as many BSICs as possible while keeping them evenly distributed in the related BSIC domain (Maximal and homogeneous option). Algorithm works as follows:

1. For each TBA transmitter i, Atoll searches for all the transmitters having the constraints listed above. These are: a. Its neighbours (neighbours listed in the neighbours list). b. The neighbours of its neighbours, c. The transmitters that interfere it,

Note: Atoll always considers symmetry relationship between a transmitter, its neighbours and the second neighbours.

2. The algorithm assigns different BSICs to the transmitter i and to all transmitters found if they have the same BCCH or an adjacent BCCH.

Examples: We assume that we have three TBA transmitters, A, B and C. 1st case: A has two neighbours, B and C. The AFP module assigns different BSICs to A, B and C if they have the same BCCH or an adjacent BCCH. 2nd case: A is neighbour of B and C. The AFP module assigns different BSICs to A, B and C if they have the same BCCH or an adjacent BCCH.

N N

A

B C

N N

A

B C

1st case: B and C neighbours of A 2nd case: A neighbour of B and C 3rd case: B is neighbour of A and C is neighbour of B. The AFP module assigns different BSICs to A, B and C if they have the same BCCH or an adjacent BCCH. 4th case: X is neither a neighbour of A, nor a neighbour of neighbours of A. Nevertheless, it interferes A. The AFP module assigns different BSICs to A and X if they have the same BCCH or an adjacent BCCH. Atoll assigns a BSIC to all the TBA transmitters even if there are not enough BSICs available in the domain. In the last case, it displays warning messages in the Events viewer.

C H A P T E R 14

UMTS documents This chapter provides details of UMTS formulas, definitions and calculations.

14

UMTS documents


XIV UMTS DOCUMENTS

XIV.1 GENERAL PREDICTION STUDIES

XIV.1.1 CALCULATION CRITERIA Three criteria can be studied in point analysis (Profile tab) and in common coverage studies. Study criteria are detailed in the table below:



Signal level received from a transmitter on a carrier (cell) ( ) ( ) Shadowing

Txipath

Txirec MLicEIRPicP −−=


Txipath Tx

+= model


Txipath

Txitotal RxTx

+−+++=

where,





is the receiver antenna gain, ic is a carrier number,

Notes: 1. It is possible to analyse all the carriers. In this case, Atoll takes the highest pilot power of cells to calculate the

signal level received from a transmitter. 2. TxantTxpilot LGicPicEIRP −+= )()( with LTx=Ltotal-DL.

3. Atoll considers that GantRx and L Rx

equal zero.

XIV.1.2 POINT ANALYSIS

XIV.1.2.a PROFILE TAB Atoll displays either the signal level received from the selected transmitter on a carrier ( ( )icPTxi

rec ), or the highest signal level received from the selected transmitter on all the carriers. Note: For a selected transmitter, it is also possible to study the path loss, LTxi


total losses are the same on any carrier.

XIV.1.2.b RECEPTION TAB Analysis provided in the Reception tab is based on path loss matrices. So, you can study reception from TBC transmitters for which path loss matrices have been computed on their calculation areas. For each transmitter, Atoll displays either the signal level received on a carrier, ( ( )icPTxi

rec ), or the highest signal level received on all the carriers. Reception bars are displayed in a decreasing signal level order. The maximum number of reception bars depends on the signal level received from the best server. Only reception bars of transmitters whose signal level is within a 30 dB margin of the best server can be displayed. Note: For a selected transmitter, it is also possible to study the path loss, LTxi





XIV.1.3 COVERAGE STUDIES For each TBC transmitter, Txi, Atoll determines the selected criterion on each bin inside the Txi calculation area. In fact, each bin within the Txi calculation area is considered as a potential (fixed or mobile) receiver. Coverage study parameters to be set are:


XIV.1.3.a SERVICE AREA DETERMINATION Atoll uses parameters entered in the Condition tab of the coverage study property dialog to predetermine areas where it will display coverage. We can distinguish three cases:

XIV.1.3.a.i All the servers The service area of Txi corresponds to the bins where:

( ) ( ) threshold Maximum or or threshold Minimum <−≤ LossesTotalLicP TxiTxitot

Txirec

XIV.1.3.a.ii Best signal level and a margin The service area of Txi corresponds to the bins where:


Txirec

And ( ) ( )( ) MicPBesticP Txj

recij

Txirec −≥

≠



signal levels from transmitters, which are 2nd best servers.

XIV.1.3.a.iii Second best signal level and a margin The service area of Txi corresponds to the bins where:


Txirec


recij

ndTxirec −≥

≠2



signal levels from transmitters, which are 3rd best servers.

XIV.1.3.b COVERAGE DISPLAY

XIV.1.3.b.i Plot resolution Prediction plot resolution is independent of the matrix resolutions and can be defined on a per study basis. Prediction plots are generated from multi-resolution path loss matrices using bilinear interpolation method (similar to the one used

UMTS documents


to evaluate site altitude).

XIV.1.3.b.ii Display types It is possible to display the transmitter service area with colours depending on any transmitter attribute or other criteria such as:








• 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. There is one coverage area per transmitter in the explorer.




XIV.2 DEFINITIONS AND FORMULAS Name Value Unit Description Fortho Clutter parameter or global parameter (default value) None Orthogonality factor Fmud Equipment parameter None MUD factor

( )icSThAS j ,_ Cell parameter NoneThreshold for macro diversity specified for a station on a given carrier ic

MMG ShadowingnpathsShadowing

ULdiversitymacro −=−

n=2 or 3 UL

diversitymacroG −

Global parameter (default value)

None UL quality gain due to signal diversity in soft handoff4.

DLdiversitymacroG − Shadowing

npathsShadowing


n=2 or 3 None DL gain due to availability of

several pilot signals at the mobile 5.

( )lUL NNumChEltsmax Site parameter None Number of channel elements

available for a site on uplink

( )lDL NNumChEltsmax Site parameter None Number of channel elements

available for a site on downlink

( )lUL NNumChElts Simulation result None Number of channel elements of a

site consumed by users on uplink

( )lDL NNumChElts Simulation result None

Number of channel elements of a site consumed by users on downlink

Fterm Terminal parameter None Terminal Noise Factor Ftx Transmitter parameter None Transmitter Noise Factor K 1.38 10-23 J/K Boltzman constant

T 293 K Ambient temperature

W Spreading bandwidth Hz Spreading Bandwidth Xmax Simulation parameter None Maximum loading factor

TxN0 WTKFTx ××× W Thermal noise at transmitter TermN0 WTKFTerm ××× W Thermal noise at terminal

Rc W Bits/s Chip rate

f efficiencyrakeUL

Equipment parameter None Uplink rake receiver efficiency factor

f efficiencyrakeDL

Terminal parameter None Downlink rake receiver efficiency factor

( )ServiceRDLnominal Service parameter Bits/s Service downlink nominal bit rate

( )ServiceFDLcoding Service parameter None Service coding factor on downlink

( )ServiceDLbR FR DL

codingDLnominal × Bits/s Service downlink effective bit rate

( )ServiceULnominalR Service parameter Bits/s Service uplink nominal bit rate

( )ServiceFULcoding Service parameter None Service coding factor on uplink

( )ServiceULbR FR UL

codingULnominal × Bits/s Service uplink effective bit rate

( )ServiceDLpG DL

alnoRW

min

None Service downlink process gain

( )ServiceULpG UL

alnoRW

min

None Service uplink process gain

)(icPSCH Cell parameter W Cell synchro channel power

)(icPOtherCCH Cell parameter W Cell other common channels (except CPICH and SCH) power

)(icPpilot Cell parameter W Cell pilot power

)(max icP Cell parameter W Max Cell power

( )icPtch Simulation result W Transmitter traffic channel power

4 npaths

ShadowingM corresponds to the shadowing margin evaluated from the shadowing error probability density function (n paths) in case of uplink soft handoff

modelling.

5 npathsShadowingM

corresponds to the shadowing margin evaluated from the shadowing error probability density function (n paths) in case of downlink Ec/Io modelling.

UMTS documents


on carrier ic

( )icPtx ( ) ( ) ( ) ( )∑+++)( ictch

tchotherCCHSCHpilot icPicPicPicP Transmitter total transmitted power on carrier ic

termP Simulation result W Terminal power transmitted GTx Transmitter parameter None Transmitter gain

GTerm Terminal parameter None Terminal gain

LTx Transmitter parameter (user-defined or calculated from

transmitter equipment characteristics) None Transmitter loss6

Lbody Service parameter None Body loss LTerm Terminal parameter None Terminal loss Lpath Propagation model result None Path loss

MShadowing Result calculated from cell edge coverage probability and model standard deviation None Shadowing margin

Only used in prediction studies

EShadowing Simulation result NoneRandom shadowing error drawn during Monte-Carlo simulation Only used in simulations

In prediction studies7

termTx

ShadowingbodytermTxpath

GGMLLLL

×××××

Transmitter-terminal total loss MShadowing=1 in downlink extra-cellular interference calculations

LT In simulations

termTx

ShadowingbodytermTxpath

GGELLLL

×××××

None

Transmitter-terminal total loss

)(icPc T

pilot

LicP )(

W Chip power received at terminal

( )icP DLb

( )T

tch

LicP

W Bit power received at terminal on carrier ic

( )icPULb

T

term

LP

W Bit power received at transmitter on carrier ic used by terminal

( )icP DLtot

( )T

tx

LicP

W Total power received at terminal from a transmitter on carrier ic

( )icP DLtraf

( )∑)( ictch t

tch

LicP

W Total power received at terminal from traffic channels of a transmitter on carrier ic

( )icI DLtot ( ) ( )icIicI DL

extraDL

ra +int W Total effective interference at terminal on carrier ic (after unscrambling)

)(int icIDLra ))(

)(()(T

SCHDLtot

txiortho

DLtot

txi LicP

icPFicP −×− W Downlink intra-cellular interference at terminal on carrier ic8

)(icIDLextra ( )∑

≠ij ,txj

DLtot icP W Downlink extra-cellular interference

at terminal on carrier ic Without

Pilot ( ) ( ) termDLextra

DLra NicIicI 0int ++

( )icI DL0

Total noise ( ) ( ) termDLextraDL

tottxi

NicIicP 0++ W Total received noise at terminal on

carrier ic

( )icN DLtot ( ) termDL

tot NicI 0+ W Total received noise at terminal on carrier ic

Total noise ( )icIicP

DLc

0

)( ( )

⇔

0IE

icQ

c

pilot

Without

Pilot ( ) ( ) corthoDL

c

PFicIicP

×−− 1)(

0

None Quality level at terminal on pilot for

carrier ic

( )icQBSipilot None Pilot quality from the best server

cell at the receiver

6 ULtotalTx LL −= on uplink and DLtotalTx LL −= on downlink. 7 In uplink prediction studies, only carrier power level is downgraded by the shadowing margin (MShadowing). In downlink prediction studies, carrier power level and intra-cellular interference are downgraded by the shadowing margin (MShadowing) while extra-cellular interference level is not. Therefore, MShadowing is set to 1 in downlink extra-cellular interference calculation formulas. 8 In simulation outputs, Atoll evaluates downlink intra-cellular interference at terminal on carrier ic as follows:

)()1())()(()()(int icPFL

icPicPFicPicI DLbortho

T

SCH

txi

DLtotortho

txi

DLtot

DLra ×−−−×−=



( )icQ sultingpilotRe ( )icQG

BSipilotDL

diversitymacro ×− NoneBest pilot quality level received on carrier ic with a fixed cell edge coverage probability

Without useful signal

( )( ) ( ) ( ) ( )

1serviceG

icPFicNicP DL

pDLbortho

DLtot

DLb ×

×−− ( )

DLt

b

DLtch

NE

icQ

⇔

Total noise ( ) )(

)(serviceG

icNicP DL

pDLtot

DLb ×

NoneQuality level at terminal on a traffic channel from one transmitter on carrier ic9

DLSHOG

( )( )rBest serveicQ

icQDL

tch

DL

, None Soft handover gain on downlink

)(icQDL [ ]∑∈

×set Active

efficiency rakeASi

DLtch

DL icQf None

Quality level at terminal using carrier ic due to combination of all transmitters of the active set (Macro-diversity conditions).

( )icI intraULtot

( )∑cell same

termicPUL

b W

Total power received at transmitter from intra-cellular terminals using carrier ic

( )icI extraULtot

( )∑othercells

term

ULb icP

W Total power received at transmitter from extra-cellular terminals using carrier ic

( )icIULtot ( ) ( ) ( )icIFicI raUL

totMUDULextratot

int1 ×−+ W Total received interference at transmitter on carrier ic

( )icNULtot ( ) txUL

tot NicI 0+ W Total noise at transmitter on carrier ic (Uplink interference)

pilotreqQ

threshold

c

IE

0

( mobility) parameter None Ec/Io target on downlink for the best server

DLreqQ

DL

reqt

b

NE

(service, mobility) parameter None Eb/Io target on downlink

CIDLreq

GQ

DLp

DLreq None Required quality on downlink

Without useful signal

( )( ) ( ) ( ) ( )serviceG

icPFicNicP UL

pULbMUD

ULtot

ULb ×

×−− 1 ( )

ULt

b

ULtch

NE

icQ

⇔

Total noise )()()( serviceG

icNicP UL

pULtot

ULb ×

None Quality level at transmitter on a traffic channel for carrier ic4

No handoff [ ]icQUL

tch

Softer HO [ ]∑

∈×

)(Activeset

efficiency rake

samesitei

tchAS

ULUL icQf

Soft HO, softer/soft (without MRC)

[ ]( ) ULdiversitymacro

ULtch GicQMax

ActivesetiAS−×

∈

)(icQUL

Softer/soft (+ MRC)

[ ] [ ]

ULdiversitymacro

UL

tchi

ULtch

UL

G

icQicQfMaxAS

−

∈

×

× ∑site other

site) (sameset Active

efficiency rake ,

None

Quality level at site using carrier ic due to combination of all transmitters of the active set located at the same site and taking into account increasing of the quality due to macro-diversity (macro-diversity gain). In simulations 1=−

ULdiversitymacroG .

ULSHOG

( )( )rBest serveicQ

icQUL

tch

UL

, None Soft handover gain on uplink

ULreqQ

UL

reqt

b

NE

(service, mobility) parameter None Eb/Nt target on uplink

( )icP reqtch ( ) ( )icP

icQQ

tchDL

DLreq × W

Required transmitter traffic channel power to achieve Eb/Nt target at terminal on carrier ic

9 Calculation option may be selected in the Global parameters tab. The chosen option will be taken into account only in simulations. In point analysis and coverage studies, Atoll uses the option “Total noise” to evaluate DL and UL Eb/Nt.

UMTS documents


( )icP reqterm ( ) ( )icP

icQQ

termUL

ULreq × W

Required terminal power to achieve Eb/Nt target at transmitter on carrier ic

Xmax Simulation constraint None Maximum uplink load factor allowed

( )icX UL Simulation result

( )( )icNicI

ULtot

ULtot

Or cell parameter

None Uplink load factor on carrier ic

)(icFUL ( )

( ) ( )mudraUL

tot

ULtot

FicIicI

−× 1int None Uplink reuse factor on carrier ic

( )iDL txicX , ( )

∑−+

−tch

orthoDLreq

orthoDL

FCI

FF

11

None Downlink load factor on carrier ic

)(icFDL

( )( ) ( )

T

SCH

T

SCHDLtotortho

DLtot

DLra

DLtot

LicP

LicPicPF

icIicIicI

)()(1)()(

int +

−×−

= None Downlink reuse factor on a carrier

ic

( )icNRDL ( )( )icX DL−− 1log10 dB Noise rise on downlink

( )icNRUL ( )( )icX UL−− 1log10 dB Noise rise on uplink

( )icPower DL% Simulation result ( )( ) 100)(/ max ×icPicPtx Or cell parameter

None Percentage of maximum transmitter power used.

( )icSNumCodes j ,max Simulation constraint None Maximum number of OVSF codes

available per cell (512)

( )icSNumCodes j , Simulation result None Number of OVSF codes used by the cell

XIV.3 ACTIVE SET MANAGEMENT Active set (AS) management is detailed hereafter. Cells entering a mobile’s active set must fulfil the following conditions:

• The best server (first cell entering active set) - The pilot quality from the best serving cell must exceed the Ec/Io threshold. Best server cell is the one

with the highest pilot quality. • Other cells in the active set

- Must use the same carrier as the best server, - The pilot quality difference between other candidate cells and the best server must be lower than the

AS threshold specified for the best server, - Other candidate cells must belong to the neighbour list of the best server if it is located on a site where

the equipment imposes this restriction (the “restricted to neighbours” option selected in the equipment properties).

XIV.4 TRAFFIC DATA

XIV.4.1 USER DENSITY When multi-service geo-marketing data is not available, you may supply the usual traffic data, like network user densities per service to Atoll (for example, values coming from adapted GSM Erlang maps). In this case, user profile definition and calculation of deduced activity probability are not necessary to create traffic scenario, traffic distribution will only depend on densities per service. If you know network user densities per service (density of users attempting a connection), just shunt User profile step by defining one service per user profile and one full-hour communication profile per service.

1. For circuit switched services: - in service properties: set UL and DL activity factors to 1. - in user profile properties: define 1 call/hour of 3600s duration.

2. for packet switched services: - in service properties: set efficiency factor in UL and DL to 1. - in user profile properties: define 1 session/hour and set volume to transmit during 3600s (for example, if nominal rate is 384 kbps, set UL and DL volumes to 172800 kBytes). So that, all the users will be connected.



Therefore, the activity probabilities calculated during simulations will be equal to 1 and subscriber density values defined in Environments will be network user densities as subscribers have a 100% percent probability to attempt a comunication. Elaborated traffic scenario will fully respect the user profile proportion (i.e. service) given in Environments. You will control the number of users in simulations as well as the service proportion that drives random trial. Moreover, all the users will be connected. Note: This method is not the usual nominal working mode for Atoll. Practical advice: 1. For example, you have Erlang/km2 data for, say, speech service in different environments. First of all, you will

define these environments. This can be translated into the number of traffic channel links using the Erlang B table (with a certain blocking probability), which is the number of users per km2 attempting to make a call. Now that you know the number of potential network user density, you can enter this value in the subscriber density and define the speech user profile as above (1 call/hour and 3600 sec/call).

2. If you have Erlang data per subscriber type and subscriber densities, you can use Atoll’s User Profile properties to enter this information and define environments with these subscriber densities. For the Erlang data, you will enter “number of calls per hour” and “call duration” (for CS services) or “UL and DL volume” (for PS services). For example, if a speech user is characterized by 20mE, this means that the probability that this subscriber will attempt to make a call is 0.02. So we will put a combination of values in the user profile such that the probability of activity = (Number of calls per hour)x(call duration)/3600 = 0.02.

3. If, instead of Erlangs, you have Mbytes per service per environment, you can start by defining these environments. You must convert this total volume per service into the number of attempting network user density. So, if you have 3.84 Mbytes in an environment for a service with 384kbps data rate, this implies that there are 10 users of this service attempting a call. Simply divide the surface of the environment by 10 to get the user density. Since this subscriber density represents attempting network user density, we have to keep the user profile properties (1 call per hour and 3600s per call) such that the probability of activity is 1. So the idea is again the same: if you know how many users will attempt a connection in an environment, you can put network user density value in subscriber density of environment, and give the user a 100% probability of activity (in user profiles).

4. Erlangs represent busy hour traffic. It is an average of the busy hour. But Atoll’s simulations are snapshots, meaning an instance of the busy hour. That instance is not necessarily the average traffic of the busy hour and can deviate. If we use the 20mE to produce 0.02 probability as above, it is a snapshot analysis on an average representation of busy hour. For the extreme cases (upper and lower extremities of the traffic curve), we need to raise or lower one or several values (calls/hr, call duration, subscriber density, or simply the global scaling factor while creating simulations), and run the simulations with different traffic cases: above and below the average.

5. The point to remember is that Atoll obtains, whatever the case, the number of attempting network users (with a certain service, terminal and mobility) to distribute in different areas to run a simulation.

XIV.5 SIMULATIONS

XIV.5.1 RANDOM TRIAL STRATEGIES During the simulation, a first random trial is performed to determine the number of users and their activity status. The determination of the number of users and the activity status allocation depend on the type of traffic cartography used.

XIV.5.1.a SIMULATIONS BASED ON RASTER TRAFFIC AND VECTOR TRAFFIC MAPS From surface calculation (S) and profile density (D), a number of subscribers (X) per profile is inferred.

DSX ×= For each behaviour described in a user profile, according to the service, frequency use and exchange volume, Atoll calculates the probability for the user being connected in uplink and in downlink at an instant t. For circuit switched service (i): Calculation of the service usage duration per hour ( p0 : probability of being connected):

36000dNp call ×=

where Ncall is the number of calls per hour and d is the average call duration.

UMTS documents


Calculation of the number of users trying to access the service i ( ni ):

pXni 0×= Active and inactive users are considered. Activity status determination: Calculation of activity probabilities

Probability of being inactive: ( ) ( )ffp DLact

ULactinactive −×−= 11

Probability of being active on UL: ( )ffp DLact

ULactUL −×= 1

Probability of being active on DL: ( )ffp ULact

DLactDL −×= 1

Probability of being active both on UL and DL: ffp DLact

ULactDLUL ×=+

Where, f UL

act and f DLact are respectively the UL and DL activity factors defined for circuit switched services.

Thus,

Number of inactive users: ( ) pninactiven inactiveii ×= Number of users active on UL: ( ) pnULn ULii ×= Number of users active on DL: ( ) pnDLn DLii ×= Number of users active on UL and DL both: ( ) pnDLULn DLULii +×=+

For packet switched service (j): Calculation of activity probabilities

36008

min ××××=

RfVNf UL

alnoULeff

ULsessUL and

36008

min ××××=

RfVNf DL

alnoDLeff

DLsessDL

where Nsess is the number of sessions per hour, VUL and V DL are respectively the data volumes tranfered in UL and DL (KBytes), f UL

eff and f DLeff are the UL and DL efficiency factors defined for packet switched services, RUL

alnomin and RDLalnomin

are the UL and DL nominal rates (kbps = 1000 bps) of the service j.

Probability of being inactive: ( ) ( )ffp DLULinactive −×−= 11 Probability of being active on UL: ( )ffp DLULUL −×= 1 Probability of being active on DL: ( )ffp ULDLDL −×= 1 Probability of being active both on UL and DL: ffp DLULDLUL ×=+

Thus,

Number of inactive users: ( ) pXinactiven inactivej ×= Number of users active on UL: ( ) pXULn ULj ×= Number of users active on DL: ( ) pXDLn DLj ×= Number of users active on UL and DL both: ( ) pXDLULn DLULj +×=+

Calculation of the number of active users trying to access the service j ( nj ):

( ) ( ) ( )DLULnDLnULnn jjjj +++= Inactive users are not taken into account. Note: The total number of users attempting a connection with a certain service remains constant in all the simulations.

Therefore, if you compute several simulations at once, the total number of users will be the same in any simulation. On the other hand, the activity status distribution between users is an average distribution. Infact, in each simulation, the activity status of each user is randomly drawn. Therefore, if you compute several simulations at once, average numbers of inactive, active on UL, active on DL and active on UL and DL users correspond to the calculated distribution. But if you check each simulation, the activity status distribution between users is different in each of them.

All user characteristics determined, a second random trial is performed to obtain their geographical positions.



XIV.5.1.b SIMULATIONS BASED ON TRAFFIC MAP PER SERVICE AND PER TRANSMITTER For each transmitter Txi and each service j:

- Either Atoll will deduce the number of active users on UL and DL in the Txi cell using the service j if you have selected the map with the Throughput option.

RRN UL

b

ULt

UL = and RRN DL

b

DLt

DL =

RULt is the kbits per second transmitted on UL in the Txi cell to supply the service j, RDL

t is the kbits per second transmitted on DL in the Txi cell to supply the service j, RUL

b and RDLb are the effective rates on UL and DL for

service j respectively.

- Or Atoll will directly use the defined NUL and NDL values (number of active users on UL and DL in the Txi cell using the service j) if you have selected the map with the User option.

For circuit switched service (i): Users active on UL and DL both are included in the NUL and NDL values. Therefore, it is necessary to accurately determine the number of active users on UL (nj(UL)), on DL (nj(DL)) and on UL and DL (nj(UL+DL)) both. As for the other types of cartography, Atoll considers both active and inactive users for circuit switched services. Calculation of activity probabilities

Probability of being active on UL: ( )ffp DLact

ULactUL −×= 1

Probability of being active on DL: ( )ffp ULact

DLactDL −×= 1

Probability of being active both on UL and DL: ffp DLact

ULactDLUL ×=+

Probability of being inactive: ( ) ( )ffp ULact

DLactinactive −×−= 11

Calculation of the number of active users trying to access the circuit switched service i We have:

( ) Nnpp ULjDLULUL =×+ + ( ) Nnpp DLjDLULDL =×+ +

Where, nj is the total number of active users in the Txi cell using the circuit switched service i. Thus,

( )

+×

+×

=++

+

+

+

pppN

pppNDLULn

DLULDL

DLULDL

DLULUL

DLULULj ,min

( ) ( )DLULnNULn jULj +−=

( ) ( )DLULnNDLn jDLj +−= And, ( ) ( ) ( )DLULnDLnULnn jjjj +++= Calculation of the number of inactive users trying to access the circuit switched service i

( ) ppninactiven inactiveinactive

jj ×−= 1

For packet switched service (j): As for the other types of cartography, Atoll considers all the connected users as active. Activity probabilities are not calculated. Calculation of the number of users trying to access the packet switched service j If NN DLUL <

( ) NDLULn ULj =+ ( ) 0=ULn j ( ) NNDLn ULDLj −=

UMTS documents


If NN DLUL > ( ) NDLULn DLj =+ ( ) 0=DLn j ( ) NNULn DLULj −=

nj is the total number of active users in the Txi cell using the packet switched service j. Thus, ( ) ( ) ( )DLULnDLnULnn jjjj +++= Note: The total number of users remains constant in all the simulation. Therefore, if you compute several simulations at

once, the total number of users will be the same in any simulation. On the other hand, the activity status distribution between users is an average distribution. Infact, in each simulation, the activity status of each user is randomly drawn. Therefore, if you compute several simulations at once, average numbers of inactive, active on UL, active on DL and active on UL and DL users correspond to the calculated distribution. But if you check each simulation, the activity status distribution between users is different in each of them.

XIV.5.2 POWER CONTROL SIMULATION Based on W-CDMA air interface, UMTS network automatically regulates itself by using traffic driven uplink and downlink power control in order to minimize interference and maximize capacity. Atoll simulates this network regulation mechanism with an iterative algorithm and calculates, for each user distribution, network parameters such as cell power, mobile terminal power, active set and handoff status for each terminal. The power control simulation is based on an iterative algorithm. In each iteration, all the mobiles selected during the generation of a user distribution (1st step) try to be connected one by one to the network’s TBC transmitters. The process is repeated from iteration to iteration until convergence is achieved. The steps of this algorithm are detailed below.

Initialisation

2nd step : Mi active set determination

3rd step : Uplink power control

1st step : Mi best server determination

For each mobile Mi

4th step : Downlink power control

5th step : Uplink and downlink interference update

Congestion and radio resource control

Convergence study

XIV.5.2.a ALGORITHM INITIALIZATION Total power on a carrier ic ( )icPTx of base station Sj is initialised to )()()( icPicPicP otherCCHSCHpilot

++ .

Uplink received powers on carrier ic, ( )icIULintratot and ( )icIULextra

tot , at base station Sj are initialised to 0 W (i.e. no connected



mobile).

( ) ( )( ) 0

,,

, ==⇔icSNicSI

icSXj

ULtot

jULtot

jk

XIV.5.2.b PRESENTATION OF THE ALGORITHM The algorithm is detailed for any iteration k. Xk is the value of the X (variable) at the iteration k. In the algorithm, all ( )targettb NE and ( )targettb NE thresholds depend on user mobility and are defined in Service and Mobility parameters tables. All variables are described in Definitions and formulas part. For each mobile Mi

XIV.5.2.b.i Determination of Mi’s Best server (SBS(Mi)) For each station Sj containing Mi in its calculation area.

Calculation of ( )ijk MSrBestCarrie , . For each carrier ic used by Sj, we calculate current loading factor:

( ) ( )( )icSN

icSIicSX

jULtot

jULtot

jk ,,

, =

EndFor If carrier selection mode is “UL min noise”

( )ijk MSrBestCarrie , is the carrier with the lowest ( )icSX jk , Else if carrier selection mode is “DL min power”

( )ijk MSrBestCarrie , is the carrier with the lowest ( )kjtx icSP ,

Else if carrier selection mode is “Random” ( )ijk MSrBestCarrie , is randomly selected

Calculation of ( ) ( )( )( )ijk

DLjic

jipilot MSrBestCarrieIrBestcarrieSMP

rBestcarrieSMQk ,

,,,,

0

=

If user selects “without Pilot”

( ) ( )( )( ) ( ) ( )rBestcarrieSMPFMSrBestCarrieI

rBestcarrieSMPrBestcarrieSMQ

jicorthoijkDL

jicjipilotk ,,1,

,,,,

0 ×−−=

Ejection of station Sj if the pilot is not received If ( ) ( )( )i

pilotreqjipilot MMobilityQrBestcarrieSMQ

k<,, then Sj is rejected by Mi

If ( ) ( )( )ipilotjipilot MQrBestcarrieSMQ

kk

max,, > Admission control (If simulation respects a loading factor constraint and Mi was not connected in previous iteration).

If ( )( ) max,, XMSrBestCarrieSX ijkjk > , then Sj is rejected by Mi Else

( ) ( )rBestcarrieSMQMQ jipilotipilot kk,,max =

( ) jiBS SMS = Endif

EndFor If no SBS has been selected, Mi has failed to be connected to the network In the following lines, we will consider ( )( )iiBSk

MMSrBestCarrieic ,=

XIV.5.2.b.ii Determination of the active set For each station Sj containing Mi in its calculation area, using ic , and, if neighbours are used, neighbour of SBS(Mi)

Calculation of ( ) ( )( )icI

icSMPicSMQ DL

jicjipilotk

0

,,,, =

If user selects “without Pilot”

UMTS documents


( ) ( )( ) ( ) ( )icSMPFicI

icSMPicSMQ

jicorthoDL

jicjipilotk ,,1

,,,,

0 ×−−=

Ejection of Sj from the active set if difference with the best server is too great If ( ) ( ) ),( _,,max icSThASicSMQMQ BSjipilotipilot kk

>− then Sj is rejected Else Sj is included in the Mi active set Ejection of a station if the mobile active set is full Station with the lowest

kpilotQ in the active set is rejected EndFor

XIV.5.2.b.iii Uplink power control Calculation of the required power for Mi: ( )ki

reqterm icMP ,

If the mobile accesses a circuit switched service (active or inactive in uplink) or a packet switched service (active in uplink). Note: For inactive mobiles in packet switched mode, this power is calculated for information only.

For each cell (Sj,ic) of the Mi active set Calculation of quality level on Mi traffic channel at (Sj,ic), with the minimum power allowed on traffic channel for the Mi service

( ) ( )( )jiT

kireq

termji

ULb SML

icMPicSMP

,,

,, 1−=

( ) ( )( ) ( ) ( ) ( )serviceG

icSMPFicNicSMP

icSMQ ULp

jiULbMUD

ULtot

jiULb

kjiULtch ×

×−−=

,,1,,

,,

If user selects "Total noise",

( ) ( )( ) ( )serviceGicN

icSMPicSMQ UL

pULtot

jiULb

kjiULtch ×=

,,,,

End For If (Mi is in not in handoff)

( ) ( )icSMQMQ jiUL

tchiUL

k,,

k=

Else if (Mi is in softer handoff) ( ) ( )∑

∈×=

set Active,,

jSkji

ULtch

ULiencyrake effici

ULk icSMQfMQ

Else if (Mi is in soft, or softer/soft without MRC) ( ) ( )( ) ( )UL

diversitymacro linkskjiULtchi

ULk GicSMQMaxMQ

ASi−×=

∈2

,,set Active

Else if (Mi is in soft/soft) ( ) ( )( ) ( )UL

diversitymacro linkskjiULtchi

ULk GicSMQMaxMQ

ASi−×=

∈3

,,set Active

Else if (Mi is in softer/soft with MRC)

( ) ( ) links

ULdiversitymacro

UL

tchothersitei

ULtch

ULencyake efficii

ULk GicQicQfMaxMQ

AS

r 2

)site same(set Active

)(,)( −∈

× ×

= ∑

End If

( ) ( ) ( )( )( ) ( ) 1,

Mobility,Service, −×= ki

reqterm

iULk

iiULreq

kireq

term icMPMQ

MMQicMP

If ( ) ( )itermkireq

term MPicMP min, < then ( ) ( )jitermkireq

term SMPicMP ,, min=

If ( ) )(, max MiPicMP termkireq

term > then Mi cannot select any cell and its active set is cleared Endif

XIV.5.2.b.iv Downlink power control If (mobile does not use a packet switched service that is inactive on the downlink)

For each cell (Sj,ic) in Mi active set Calculation of quality level on (Sj,ic) traffic channel at Mi with the minimum power allowed on traffic channel for



the Mi service

( ) ( )( )( )jiT

itchji

DLb SML

MPicSMP,

Service,,min

=

( ) ( )( ) ( ) ( ) ( )( )i

DLp

jiDL

borthoDLtot

jiDL

bkji

DLtch MServiceG

icSMPFicNicSMP

icSMQ ××−−

=,,1

,,,,

If user selects "Total noise"

( ) ( )( ) ( )( )i

DLpDL

tot

jiDL

bkji

DLtch MServiceG

icNicSMP

icSMQ ×=,,

,,

End For ( ) ( )∑

∈

×=ActivesetSj

kjiDLtch

DLiencyrake effici

DLk icSMQfMQ ,,

Do For each cell (Sj,ic) in Mi active set

Calculation of the required power for DL traffic channel between (Sj,ic) and Mi:

( ) ( ) ( )( )( ) ( )( )itch

iDLk

iiDLreq

kjireq

tch MPMQ

MMQicSMP service

Mobility,Service,, min×=

If ( ) ( )( )itchkjireq

tch MPicSMP Service,, max> then ( )icS j , is tuned at maxtchP

Recalculation of a decreased DLreqQ (a part of the required quality is managed by the cells tuned at max

tchP )

( ) ( )( )( )jiT

ireqtch

jiDLb S,ML

MServicePic,S,MP =

( ) ( )( ) ( ) ( ) ( )( )i

DLp

jiDL

borthoDLtot

jiDL

bkji

DLtch MServiceG

icSMPFicNicSMP

icSMQ ××−−

=,,1

,,,,

EndFor

( ) ( )∑∈

×=set Active

,,jS

kjiDLtch

DLiencyrake effici

DLk icSMQfMQ

While ( ) ( ) ( )( )iiDLreqi

DLk MMQMQ Mobility,Service< and Mi active set is not empty

Endif

XIV.5.2.b.v Uplink and downlink interference update Update of interference on active mobiles only (old contributions of mobiles and stations are replaced by the new ones). For each cell (Sj,ic)

Update of ( )icSN jULtot ,

EndFor For each mobile Mi

Update of ( )icN DLtot

EndFor EndFor

XIV.5.2.b.vi Control of radio resource limits (OVSF codes, cell power, channel elements) For each cell (Sj,ic)

While ( ) ( )icSPicSP jtxkjtx ,, max>

Ejection of mobile with highest ( )kji

reqtch icSMP ,, for the lowest service priority

EndFor For each cell (Sj,ic)

While ( ) ( )icSNumCodesicSNumCodes jkj ,, max> Ejection of last admitted mobile

EndFor For each site (Node B) Nl

While ( ) ( )lDL

klDL NNumChEltsNNumChElts max>



UMTS documents


While ( ) ( )lUL

klUL NNumChEltsNNumChElts max>

Ejection of mobile with highest ( )kireq

term icMP , for the lowest service priority EndFor

XIV.5.2.b.vii Uplink load factor control For each cell (Sj,ic) with XUL(Sj,ic) > Xmax

Ejection of a mobile with the lowest service priority EndFor While at least one cell with XUL(Sj,ic) > Xmax exists

XIV.5.2.c CONVERGENCE CRITERIA The convergence criteria are evaluated for each iteration, and can be written as follow:

( ) ( )( )

( ) ( )( )

( ) ( )( )

( ) ( )( )

×

−

×−=∆

×

−

×

−=∆

−−

−−

100max

int,100maxintmax

100max

int,100max

intmax

11

11

icN

icNicN

icIicIicI

icN

icNicN

icP

icPicP

kULuser

kULuserk

ULuserStations

kULtot

kULtotk

ULtot

StationsUL

kDLuser

kDLuserk

DLuserStations

ktx

ktxktxStationsDL

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

Example: Let us assume that the maximum number of iterations is 100, UL and DL convergence thresholds are set to 5. If 5≤∆UL and 5≤∆DL between the 4th and the 5th iteration, Atoll stops the algorithm after the 5th iteration. Convergence has been reached.

2nd case: After 30 iterations, UL∆ and/or DL∆ are still higher than their respective thresholds and from the 30th iteration,

UL∆ and/or DL∆ do not decrease during the next 15 successive iterations. The simulation has not reached convergence (specific divergence symbol).

Examples: Let us assume that the maximum number of iterations is 100, UL and DL convergence thresholds are set to 5. 1. After the 30th iteration, UL∆ and/or DL∆ equal 100 and do not decrease during the next 15 successive iterations:

Atoll stops the algorithm at the 46th iteration. Convergence has not been reached. 2. After the 30th iteration, UL∆ and/or DL∆ equal 80, they start decreasing slowly until the 40th iteration (without going

under the thresholds) and then, do not change during 15 successive iterations: Atoll stops the algorithm at the 56th iteration without reaching convergence.

3rd case: After the last iteration. If UL∆ and/or DL∆ are still strictly higher than their respective thresholds, the simulation has not reached convergence (specific divergence symbol). If UL∆ and DL∆ are lower than their respective thresholds, the simulation has reached convergence.

XIV.5.3 APPENDICES

XIV.5.3.a ADMISSION CONTROL During admission control, Atoll calculates the uplink load factor of a considered cell assuming the mobile concerned is connected with it. Here, activity status assigned to users is not taken into account. So even if the mobile is not active on UL, it can be rejected due to cell load saturation. To calculate the cell UL load factor, either Atoll takes into account the mobile power determined during power control if mobile was connected in previous iteration, or it estimates a load rise due to the mobile and adds it to the current load. The load rise ( ULX∆ ) is calculated as follows:



RQWX

ULb

ULreq

UL

×+

=∆1

1

XIV.5.3.b OVSF CODE MANAGEMENT OVSF codes are managed on the downlink during the simulation. Atoll performs OVSF code allocation during the radio resource control step. OVSF codes form a binary tree. Codes of longer lengths are generated from codes of a shorter length. Length-k OVSF codes are generated from length-k/2 OVSF codes. Therefore, if one channel needs 1 length-k/2 OVSF code, it is equivalent to use 2 length-k OVSF codes, or 4 length-2k OVSF codes and so on.

Indexes into the OVSF code tree (not OVSF code numbers)

512 512 bit-length codes per cell are available in UMTS projects. During the resource control, Atoll determines the number of codes that will be consumed for each cell. Therefore, it allocates:

• A 256 bit-length code per common channel, for each cell, • A code per cell-receiver link, for TCH (traffic channels). The length of code to be allocated, Code_Length, is

determined as follows:

2_ ×= DLbR

WLengthCode

Note: The factor 2 is taken into account to model the usage of a QPSK modulation (2 bit/symbol) on downlink. When the calculated code length does not correspond to the code lengths available in the tree, Atoll takes the code with a shorter length. For instance, Atoll will use a 128 bit OVSF code in case the calculated code length is 240. The OVSF code allocation follows the “Buddy” algorithm, which guarantees that:

• If a k-length OVSF code is used, all of its children with lengths 2k, 4k, …, cannot be used as they will not be orthogonal.

• If a k-length OVSF code is used, all of its ancestors with lengths k/2, k/4, …, cannot be used as they will not be orthogonal.

Example: Let a “64 kbit/s service” user be active on DL while connected to a cell. We assume that the coding factor is 1 and site equipment requires four overhead downlink channel elements per cell. Atoll will consume four 256 bit-length OVSF codes for common channels (i.e. eight 512 bit-length OVSF codes) and a 64 bit-length OVSF code for traffic channels (i.e. eight additional 512 bit-length OVSF codes). Notes: 1. The OVSF code allocation follows the mobile connection order (mobile order in the Mobiles tab). 2. The OVSF code and channel element management is dealt with differently in case of “softer” handoff. Atoll

allocates OVSF codes for each cell-mobile link while it globally assigns channel elements to a site.

UMTS documents


XIV.5.3.c DOWNLINK LOAD FACTOR CALCULATION Approach for downlink load factor evaluation is highly inspired by the downlink load factor defined in the book “WCDMA for UMTS by Harry Holma and Antti Toskala”.

Let DLp

DLreq

req GQ

CI = be the required quality.

GDLp and QDL

req are the processing gain on downlink and the Eb/Nt target on downlink respectively. In case of soft-handoff, required quality is limited to the effective contribution of the transmitter.

)()()()()()()()( icPicPicPicPicPicPicPicPtch

tchnonOrtho

CCHortho

CCHtch

tchotherCCHSCHpilotDL

tx ∑∑ ++=+++=

where )()()( icPicPicP otherCCHpilot

orthoCCH +=

)()( icPicP SCHnonOrthoCCH =

At mobile level, we have a required power, Ptch:

( ) Tterm

raextrareqtch LNicIicICIicP ×++×= 0int )()()(

( ) ( )T

term

T

nonOrthoCCH

T

tchnonOrtho

CCHDLtx

orthoextrareqtch LNL

icPL

icPicPicPFicICIicP ×

++

−−×−+×= 0

)()()()(1)()(

( )( )

( )orthoreq

TtermnonOrtho

CCHorthoDLtxorthoTextra

tch

FCI

LNicPFicPFLicIicP−+

×+×+×−+×=

11)()(1)(

)( 0

)(int icIDL

ra is the total power received at the receiver from the cell with which it is connected. )(icIDL

extra is the total power received at the receiver from other cells.

( )( )( )

∑−+

×+×+×−+×++=tch

orthoreq

TtermnonOrtho

CCHorthoDL

txorthoTextranonOrthoCCH

orthoCCH

DLtx

FCI

LNicPFicPFLicIicPicPicP11

)()(1)()()()( 0

Let FDL be the downlink reuse factor:

DLtx

Textra

ra

extraDL

PLicI

icIicIF ×==− )(

)()(1

int

We have: ( )

( )∑

−+

×+×+×−+×−++=tch

orthoreq

TtermnonOrtho

CCHorthoDLtxortho

DLtx

DLnonOrthoCCH

orthoCCH

DLtx

FCI

LNicPFicPFicPFicPicPicP11

)()(1)()1()()()( 0

( )

( ) ( )∑

∑

−+

×+×++=

−+

−−

tchortho

req

TtermnonOrtho

CCHorthononOrthoCCH

orthoCCH

DLtx

orthoreq

tchortho

DL

DLtx

FCI

LNicPFicPicPicPF

CI

FFicP

11)()()()(

11)( 0

( )

( )

( )∑

∑

−+

−−

−+

×+×++

=

tchortho

req

orthoDL

tchortho

req

nonOrthoCCHorthoT

termnonOrtho

CCHortho

CCH

DLtx

FCI

FF

FCI

icPFLNicPicP

icP

111

11)()()(

)(

0

Therefore, the downlink load factor can be expressed as:



( )∑

−+

−=tch

orthoreq

orthoDL

DL

FCI

FFX11

The downlink load factor represents the signal degradation in relation to the reference interference (thermal noise plus synchronisation channel power).

XIV.6 UMTS W-CDMA PREDICTION STUDIES

XIV.6.1 POINT ANALYSIS

XIV.6.1.a AS ANALYSIS TAB Let us suppose a receiver with an associated terminal, service and mobility that does not create any interference. The analysis is based on the UL load percentage and the downlink total power of cells. These parameters can be outputs of a given simulation, average values calculated from a group of simulations, or user-defined cell inputs.

XIV.6.1.a.i Bar graph and pilot sub-menu Atoll proceeds as in power control simulation. It determines the best carrier of each transmitter i (its best cell) that contains the receiver in its calculation area. The best carrier selection depends on the option chosen in Equipments (UL minimum noise, DL minimum power, random) and is based on simulation results. Then, Atoll calculates pilot quality at the receiver from these transmitters on their best carriers and defines the best server (on its best carrier).

1. Ec/Io (or ( )icQpilot ) evaluation Let us assume that ic is the best carrier of a transmitter i containing the receiver in its radius calculation. Two ways may be used to calculate Io.

Option Total noise: Atoll considers the noise generated by all the transmitters and the thermal noise. Option Without pilot: Atoll considers the total noise deducting the pilot signal and considering the orthogonality of traffic channels and other common channels.

Calculation option may be selected in Global parameters. Therefore, we have:

For the total noise option, ( ) ( )icI

icPicQ DLo

ci

pilot i

)(= with ( ) NicIicPicI term

oDLo

DLextraDL

toti

++= )()(

For the without pilot option, ( ) ( ) ( ) PFicI

icPicQciortho

DLo

ci

pilot i ×−−=

1)(

with ( ) NicIicIicI termo

DLo

DLra

DLextra ++= )()( int

1st step: )(icPci calculation for each cell (i,ic)

)(icPci is the pilot power of a transmitter i on carrier ic at the receiver.

L

icPicPT i

c i

pilot )()( =

LT i

is the total loss between transmitter i and receiver.

GGMLLLL

LtermTx

T i

ShadowingbodytermpathTx

×××××

=

2nd step: )(icPDL

tot j and )(icPDL

tot icalculations

We have:

)()(,

icPicIijtxj

DLtot

DLextra ∑

≠

=

And

))()(()()(intT

SCHDLtoti

orthoDLtoti

DLra L

icPicPFicPicI −×−=

UMTS documents


For each transmitter of the network, )(icPDLtot is the total power received at the receiver from the transmitter on the

best carrier ic of the transmitter i.

L

icPicPT

TxDLtot

)()( =

( )icPTx is the total power transmitted by transmitter i on the best carrier. Total power transmitted by each cell is provided in the Simulation properties (Transmitter tab). 3rd step: Nterm

o calculation WTKFN term

termo ×××=

4th step: ( )icIDL

o and ( )icQpilot i evaluation using formulas described above

5th step: DL

diversitymacroG − calculation

The macro-diversity gain, DLdiversitymacroG − , models the decrease in shadowing margin due to the fact there are several

available pilot signals at the mobile.

ShadowingnpathsShadowing


npathsShadowingM is the shadowing margin when the mobile receives n pilot signals (not necessarily from transmitter belonging to

the mobile active set). Note: This parameter is determined from cell edge coverage probability and model standard deviation. When the model

standard deviation is set to 0, the macro-diversity gain equals 0.

6th step: Determination of active-set Atoll takes the transmitter i with the highest ( )icQ

ipilot and calculates the best pilot quality received with a fixed cell edge

coverage probability, ( )icQ sultingpilotRe .

( ) ( )( )icQGicQ

ipilotDL

diversitymacrosulting

pilot maxRe ×= −

If QQ req

pilotsulting

pilot ≥Re , it means pilot quality at the receiver exceeds ( )icQ sultingpilotRe x% of time (x is the fixed cell edge coverage

probability). The cell whose ( )icQipilot is the highest one enters the active set as best server ( ( )icQpilotBS

) and the best carrier (icBS) of the best server, iBS, will be the carrier used by other transmitters of the active set (when active set size is greater than 1). Pilot is available. If QQ req

pilotsulting

pilot <Re , no cell (i,ic) can enter the active set. Pilot is unavailable. Then, pilot qualities at the receiver from transmitters i (except the best server) on the best carrier of the best server, icBS, are recalculated to determine the entire receiver active set (when active set size is greater than 1). Same formulas and calculation method are used to update ( )icI BS

DLo value and determine ( )icQ BSpilot i

. We have:

For total noise option, ( ) ( )icI

icPicQBS

DLo

ciBSpilot i

BS )(= with ( ) NicIicPicI term

oDLo BS

DLextraBS

DLtoti

BS ++= )()(

For without pilot option,

( ) ( ) ( ) ( ))1)(

BS

BS

icPFicI

icPicQciorthoBS

DLo

ciBSpilot i ×−−

= with ( ) NicIicIicI termo

DLo BS

DLraBS

DLextraBS ++= )()( int

Other cells (i,icBS) in the active set must satisfy the following criteria:

( ) ( ) ),icld (iAS_threshoicQicQ BSBSBSpilotBSBSpilot i≥−

),()ic(i, BS BSBS icilistneighbour ∈ (optionally)

2. Number of cells in active set

This is a user-specified input in the Terminal properties. It corresponds to the active set size.



3. Thermal noise This parameter is calculated as described above (3rd step).

4. Io (Best server)

Io (Best server) is the total noise received at the receiver on icBS. The notation “Best server” refers to the best server of active set. This is relevant when using the calculation option “Without pilot”. In this case, it informs that the pilot signal of the best server (iBS,icBS) is deducted from the total noise.

5. Downlink macro-diversity gain This parameter is calculated as described above (5th step).

XIV.6.1.a.ii Downlink sub-menu Atoll calculates traffic channel quality from each cell (k,icBS) of the receiver’s active set at the receiver. No power control is performed as in simulations. Here, Atoll determines downlink traffic channel quality at the receiver for the maximum allowed traffic channel power per transmitter. Then, after combination, the global downlink traffic channel quality is evaluated and compared with the specified target quality.

1. Eb/Nt target Eb/Nt target (QDL

req ) is a user-defined parameter for a given service and mobility. This parameter is available in the Services table.

2. Eb/Nt max for each cell of active set Let us assume the following notation: Eb/Nt max corresponds to QDL

max Therefore, for each cell (k,icBS), we have:

( )( ) ( )service_max)(max GicN

icPicQ DLp

BSDLtot

BSDL kb

BSDL k ×=

With ( )L

PicPT k

BSDL kb

tchmax

max_ = and NicIicIicN termBS

DLextraBS

DLraBS

DLtot 0int )()()( ++=

where Ptch

max is the maximum power allowed on traffic channel. This parameter is user-defined in the Services table. ( )icN BS

DLtot is the total noise at the receiver on the best carrier of the best server.

For each transmitter j ( jk ∈ ) in network, ( )icP BSDLtot is the total power received at the receiver from j on icBS.

3. Eb/Nt max

QDL

MAX is the traffic channel quality at the receiver on icBS after signal combination of all the transmitters k of the active set. On downlink, for any handoff status, we have:

( ) ( )

×= ∑

kmax icQficQ BSBSDL kDL

iencyrake efficDLMAX

where f DL

iencyrake effic is the downlink rake efficiency factor defined in Terminal properties.

Therefore, downlink traffic channel is available if QicQ DLreqBS

DLMAX ≥)( .

4. Effective Eb/Nt

QDLeff is the effective traffic channel quality at the receiver on icBS.

),min( QQQ DL

reqDLMAX

DLeff =

UMTS documents


5. Downlink soft handover gain

( )( )( )icQ

icQGBS

BS

DL k

DLMAXDL

SHOmaxmax

=

( )( )icQ BS

DL kmaxmax corresponds to the highest ( )icQ BS

DL kmax value.

XIV.6.1.a.iii Uplink sub-menu For each cell (k,icBS) in the receiver’s active set, Atoll calculates uplink traffic channel quality from receiver. No power control is performed as in simulations. Here, Atoll determines the uplink traffic channel quality at the cell for the maximum traffic channel power of the terminal. The global uplink traffic channel quality is evaluated from formulas depending on the receiver handoff status. Then, from this value, Atoll calculates the required terminal power and compares it to the specified target value.

1. Max terminal power Max terminal power ( Pterm

max ) is a user-defined input for each terminal. It corresponds to the terminal’s maximum traffic channel power.

2. Required terminal power 1st step: ( )icQ BS

UL kmax evaluation for each cell

For each cell (k,icBS) in the receiver’s active set, we have:

( )( ) ( )service_max)(max GicN

icPicQ ULp

BSULtot

BSDL kb

BSULk ×=

With ( )L

PicPT k

BSUL kb

termmax

max_ = and ( ) ( ) ( ) ( ) NicPFicPicN TxBS

same cellterm

ULbMUDBS

sother cellterm

ULbBS

ULtot 0

1 +∑×−+∑=

PULb is the traffic channel power received at the transmitter j (j is a network transmitter, jk ∈ ) from the terminal

on icBS.

( ) ( )L

icPicPT j

BSBS

termUL jb =

( )icP BSterm is the traffic channel power transmitted by the terminal on icBS. This data is a simulation output that can be found in the Simulation properties (Mobile tab). Finally, WTKFN Tx

Txo ×××=

2nd step: Eb/Nt max calculation

)( BSULMAX icQ is the traffic channel quality at the transmitter on icBS after signal combination of all the transmitters k

of the active set. If there is no handoff (1/1): )()(

max BSUL k

BSULMAX icQicQ =

For soft handoff (2/2):

( ) ( ))(max)( max2 BSUL kUL

diversitymacro linksBSULMAX icQGicQ ×= −

( )links

ULdiversitymacroG

2− is the uplink macro-diversity gain. This parameter is determined from cell edge coverage probability and model standard deviation. When the cell edge coverage probability is set to 50%, Atoll considers the uplink macro-diversity gain defined by the user in Global parameters.

( ))(max max BSUL k icQ corresponds to the highest )(

max BSUL k icQ value.

For soft-soft handoffs (3/3):

( ) ( ))(max)( max3 BSUL kUL


( )links

ULdiversitymacroG

3− is the uplink macro-diversity gain. This parameter is determined from cell edge coverage probability and model standard deviation. When the cell edge coverage probability is set to 50%, Atoll



considers the uplink macro-diversity gain defined by the user in Global parameters.

For softer and softer-softer handoffs (1/2 and 1/3): ( )∑×=

kBS

UL kULiencyrake efficBS

ULMAX icQficQ )()(

max

For softer-soft handoffs (2/3), there are two possibilities:

If MRC option is selected (option available in Global parameters): ( ) ( ))(,)(max)(

max

max2 site same the on kBS

other siteUL k on anBS

UL kULiencyrake effic

ULdiversitymacro linksBS

ULMAX icQicQfGicQ ∑××= −

If MRC option is not selected: ( ) ( ))(max)(

max2 BSUL kUL


3rd step: ( )icP BS

reqterm calculation

( )icP BS

reqterm is the required terminal power.

( ) ( )( ) PicQ

QicP termUL

MAX

ULreq

BS

BSreqterm

max×=

QUL

req is a parameter defined by the user for a given service and mobility. This parameter is available in the Services table.

Therefore, uplink traffic channel is available if ( ) PicP termBSreqterm

max≤ . 3. Effective Eb/Nt

QUL

eff is the effective traffic channel quality at the transmitter on icBS.

),min( QQQ ULreq

ULMAX

ULeff =

4. Uplink soft handover gain

The uplink soft handover gain calculation depends on the receiver handoff status.

( ))(max)(

max

BSUL k

BSULMAXUL

SHO icQicQG =

XIV.6.2 COVERAGE STUDIES Let us assume each bin on the map corresponds to a probe receiver with associated terminal, mobility and service. This receiver may be using a specific carrier or all of them. Moreover, it does not create any interference. Coverage studies are based on the UL load percentage and the downlink total power of cells. These parameters can be either simulation outputs, or user-defined cell inputs.

XIV.6.2.a PILOT RECEPTION ANALYSIS For further details of calculation formulas and methods, please refer to Definitions and formulas part, and Point analysis – AS analysis tab – Pilot sub-menu part.

XIV.6.2.a.i 1st case: analysis based on all the carriers Atoll proceeds as in point predictions. It determines the best carrier of each transmitter i containing the receiver in its calculation area. The best carrier selection depends on the option chosen in Equipment (UL minimum noise, DL minimum power, random) and is based on the UL load percentage and the downlink total power of cells (simulation results or cell properties). Atoll calculates pilot quality at the receiver from these transmitters on their best carrier and determines the best serving transmitter iBS on its best carrier icBS ( ( )BSicQpilot BSi

). Then, it deduces the best pilot quality

received with a fixed cell edge coverage probability, ( )BSsulting

pilot icQRe . Atoll displays the best pilot quality received with a fixed cell edge coverage probability.

UMTS documents


XIV.6.2.a.ii 2nd case: analysis based on a specific carrier The carrier that can be used by transmitters is fixed. In this case, for each transmitter i containing the receiver in its calculation area that may use the specified carrier (carrier specified in Cell Properties), Atoll calculates pilot quality at the receiver on this carrier icgiven. Then, it determines the best serving transmitter iBS using the carrier icgiven ( ( )givenicQpilot BSi

)

and deduces the best pilot quality received with a fixed cell edge coverage probability, ( )givensulting

pilot icQRe . Atoll displays the best pilot quality received with a fixed cell edge coverage probability.

1. Single colour Atoll displays a coverage if ( ) QicQ req

pilotsulting

pilot ≥Re . Coverage consists of a single layer with a unique colour.

icicic givenBS or =

Qreq

pilot is a target value defined in the Mobility table by the user.

2. Colour per transmitter Atoll displays a coverage if ( ) QicQ req

pilotsulting

pilot ≥Re ( icicic givenBS or = ). Coverage consists of several layers with associated colours. There is a layer per transmitter with no intersection between layers. Layer colour is the colour assigned to the best serving transmitter iBS in Transmitter properties.

3. Colour per mobility In this case, receiver is not completely defined and no mobility is assigned. Coverage consists of several layers with a layer per user-defined mobility defined in Mobility sub-folder. For each layer, area is covered if ( ) QicQ req

pilotsulting

pilot ≥Re ( icicic givenBS or = ). Each layer is assigned a colour and there are intersections between layers.

4. Colour per probability Coverage consists of several layers with a layer per user-defined probability level defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) QicQ req

pilotsulting

pilot ≥Re ( icicic givenBS or = ) in the required number of simulations. Each layer is assigned a colour and there are intersections between layers.

5. Colour per quality level Coverage consists of several layers with a layer per user-defined quality threshold defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) thresholdQicQ pilot

sultingpilot _Re ≥ ( icicic givenBS or = ). Each layer is assigned a

colour and there are intersections between layers.

6. Colour per quality margin Coverage consists of several layers with a layer per user-defined quality margin defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) QQicQ inm

pilotsulting

pilotreq

pilotargRe ≥− ( icicic givenBS or = ). Each layer is assigned a

colour and there are intersections between layers.

XIV.6.2.b DOWNLINK SERVICE AREA ANALYSIS As in point predictions, Atoll calculates traffic channel quality at the receiver for each cell (k,ic) (with ic=icBS or icgiven) in the receiver’s active set. No power control is performed as in simulations. Here, Atoll determines downlink traffic channel quality at the receiver for a maximum allowed traffic channel power for transmitters. Then, the global downlink traffic channel quality (Eb/Nt max) is evaluated after combination. Note: Active set determination is performed as in point prediction. The only difference is the carrier choice. If analysis is

based on all the carriers, the best carrier of the best server transmitter is used. On the other hand, if analysis is based on a given carrier, the selected carrier is used (in this case, only the transmitters using this carrier are allowed to enter the active set).

Atoll displays traffic channel quality at the receiver for transmitters in active set on the carrier ic ( icBS or icgiven ). For further details of calculation formulas and methods, please refer to Prediction studies: Point analysis – AS analysis



tab – Downlink sub-menu part.

1. Single colour Atoll displays a coverage with a unique colour if ( ) QicQ DL

reqDLMAX ≥ .

QDLreq is a user-defined parameter for a service and mobility in the Services sub-folder.

2. Colour per transmitter

Atoll displays a coverage if ( ) QicQ DL

reqDLMAX ≥ . Coverage consists of several layers with associated colours. There is a layer

per transmitter with no intersection between layers. Layer colour is the colour assigned to best serving transmitter in Transmitter properties.

3. Colour per mobility In this case, receiver is not completely defined and no mobility is assigned. Coverage consists of several layers with a layer per user-defined mobility defined in Mobility sub-folder. For each layer, area is covered if ( ) QicQ DL

reqDLMAX ≥ . Each layer is assigned a colour and there are intersections between layers.

4. Colour per service*

In this case, receiver is not completely defined and no service is assigned. Coverage consists of several layers with a layer per user-defined service defined in Services sub-folder. For each layer, area is covered if ( ) QicQ DL

reqDLMAX ≥ . Each layer is assigned a colour and there are intersections between layers.

5. Colour per probability

Coverage consists of several layers with a layer per user-defined probability level defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) QicQ DL

reqDLMAX ≥ in the required number of simulations. Each layer is

assigned a colour and there are intersections between layers.

6. Colour per maximum quality level Coverage consists of several layers with a layer per user-defined quality threshold defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) QicQ DL

thresholdDLMAX ≥ . Each layer is assigned a colour and there are

intersections between layers.

* Service oriented studies (effective service area, DL or UL service area analysis) with per service display are based on a calculation and display optimisation method. Atoll considers that a calculation bin covered for the upper service of the list is automatically covered for the lower services. Sometimes, this optimisation is not possible. In such a case, the composite coverage is reliable but single service coverage layers might be incorrect. Atoll detects when this optimisation may involve errors. In this case, it advises the user to perform a study for each service to get a reliable service coverage. Different cases where optimisation method does not work correctly are detailed below: 1. Any uplink or downlink quality study must be performed for each service if handover is not available for all the

services and the service order is different from the one found when considering handover for all the services. A bin could be covered by a service requiring a high quality target, due to handover (Eb/Nt combination), while it would not be covered by a service requiring a lower quality target but not allowing handover.

For uplink, services are sorted according to a decreasing quality indicator ( IUL

Q ):

GQ

I ULp

ULreqUL

Q =

For downlink, services are sorted according to a decreasing quality indicator ( IDLQ ):

PGQ

Itch

DLp

DLreqDL

Q max×=

2. Effective service area study must be performed for each service if uplink and downlink orders of services

(explained above) are not the same.

UMTS documents


7. Colour per effective quality level

Coverage consists of several layers with a layer per user-defined quality threshold defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) QicQ DL

thresholdDLeff ≥ . Each layer is assigned a colour and there are


8. Colour per quality margin Coverage consists of several layers with a layer per user-defined quality margin defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) QQicQ DL

inmDLreq

DLMAX arg≥− . Each layer is assigned a colour and there are


9. Colour per required power Atoll calculates the downlink required power, )(icP req

tch , as follows:

max

)()( tchUL

MAX

DLreqreq

tch PicQ

QicP ×=

where DLreqQ is the Eb/Nt target on downlink. This parameter, available in the Services table, is user-defined for given

service and mobility. max

tchP is a user-defined input for each service. It corresponds to the maximum allowable traffic channel power for a transmitter.

Coverage consists of several layers with a layer per user-defined required power threshold defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) PicP threshold

tchreqtch ≥ . Each layer is assigned a colour and there are


10. Colour per required power margin Coverage consists of several layers with a layer per user-defined power margin defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) PPicP inm

tchtchreqtch

argmax ≥− . Each layer is assigned a colour and there are intersections between layers.

XIV.6.2.c UPLINK SERVICE AREA ANALYSIS As in point prediction, Atoll calculates uplink traffic channel quality from receiver for each cell (k,ic) (with ic=icBS or icgiven) in receiver active set. No power control simulation is performed. Atoll determines uplink traffic channel quality at the transmitter for the maximum terminal traffic channel power. Then, the global uplink traffic channel quality (Eb/Nt max) is evaluated according to receiver handoff status.

Note: Active set determination is performed as in point prediction. The only difference is the carrier choice. If analysis is based on all the carriers, the best carrier of the best server will be used. On the other hand, if analysis is based on a given carrier, the carrier used will be the selected one (in this case, only the transmitters using this carrier will be able to enter active set).

Atoll displays traffic channel quality at transmitters in active set on the carrier ic ( icBS or icgiven ) received from the receiver. For further details of calculations formulas and methods, please refer to Point analysis – AS analysis tab – Uplink sub-menu part.

1. Single colour Atoll displays a coverage if ( ) QicQ UL

reqULMAX ≥ . Coverage colour is unique.

QULreq is a user-defined parameter for a service and mobility in the Services sub-folder.

2. Colour per transmitter

Atoll displays a coverage if ( ) QicQ UL

reqULMAX ≥ . Coverage consists of several layers with associated colours. There is a layer

per transmitter with no intersection between layers. Layer colour is the colour assigned to best server transmitter in Transmitter properties.



3. Colour per mobility

In this case, receiver is not completely defined and no mobility is assigned. Coverage consists of several layers with a layer per user-defined mobility defined in Mobility sub-folder. For each layer, area is covered if ( ) QicQ UL

reqULMAX ≥ . Each layer

is assigned a colour and there are intersections between layers.

4. Colour per service* In this case, receiver is not completely defined and no service is assigned. Coverage consists of several layers with a layer per user-defined service defined in Services sub-folder. For each layer, area is covered if ( ) QicQ UL

reqULMAX ≥ . Each

layer is assigned a colour and there are intersections between layers.

5. Colour per probability Coverage consists of several layers with a layer per user-defined probability level defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) QicQ UL

reqULMAX ≥ in the required number of simulations. Each layer is

assigned a colour and there are intersections between layers.

6. Colour per maximum quality level Coverage consists of several layers with a layer per user-defined quality threshold defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) QicQ UL

thresholdULMAX ≥ . Each layer is assigned a colour and there are


7. Colour per effective quality level Coverage consists of several layers with a layer per user-defined quality threshold defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) QicQ UL

thresholdULeffective ≥ . Each layer is assigned a colour and there are

intersections between layers. 8. Colour per quality margin

Coverage consists of several layers with a layer per user-defined quality margin defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) QQicQ UL

inmULreq

ULMAX arg≥− . Each layer is assigned a colour and there are

intersections between layers. * Service oriented studies (effective service area, DL or UL service area analysis) with per service display are based on a calculation and display optimisation method. Atoll considers that a calculation bin covered for the upper service of the list is automatically covered for the lower services. Sometimes, this optimisation is not possible. In such a case, the composite coverage is reliable but single service coverage layers might be incorrect. Atoll detects when this optimisation may involve errors. In this case, it advises the user to perform a study for each service to get a reliable service coverage. Different cases where optimisation method does not work correctly are detailed below: 1. Any uplink or downlink quality study must be performed for each service if handover is not available for all the

services and the service order is different from the one found when considering handover for all the services. A bin could be covered by a service requiring a high quality target, due to handover (Eb/Nt combination), while it would not be covered by a service requiring a lower quality target but not allowing handover.

For uplink, services are sorted according to a decreasing quality indicator ( IUL

Q ):

GQ

I ULp

ULreqUL

Q =

For downlink, services are sorted according to a decreasing quality indicator ( IDLQ ):

PGQ

Itch

DLp

DLreqDL

Q max×=

2. Effective service area study must be performed for each service if uplink and downlink orders of services

(explained above) are not the same.

UMTS documents


9. Colour per required power Coverage consists of several layers with a layer per user-defined power threshold defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) PicP threshold

termreqterm ≥ . Each layer is assigned a colour and there are


10. Colour per required power margin Coverage consists of several layers with a layer per user-defined power margin defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) PPicP inm

termtermreqterm

argmax ≥− . Each layer is assigned a colour and there are intersections between layers.

XIV.6.2.d DOWNLINK TOTAL NOISE ANALYSIS Atoll determines downlink total noise generated by cells.

( ) ( )N

LicPicN term

oj

T j

Tx jDLtot +∑=

Downlink noise rise, ( )icNRDL , is calculated from the downlink total noise, NDLtot , as follows:

( )

⋅−=NNicNR DL

tot

term

DL0log10

XIV.6.2.d.i Analysis on all the carriers If all the carriers are selected, Atoll determines DL total noise for all the carriers. Then, allows the user to choose different colours.

1. Colour per minimum noise level

Coverage consists of several layers with a layer per user-defined noise level defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) NicN DL

thresholdic

DLtot ≥min . Each layer is assigned a colour and there are

intersections between layers. 2. Colour per maximum noise level

Coverage consists of several layers with a layer per user-defined noise level defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) NicN DL

thresholdic

DLtot ≥max . Each layer is assigned a colour and there are


3. Colour per average noise level Coverage consists of several layers with a layer per user-defined noise level defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) NicN DL

thresholdic

DLtot ≥average . Each layer is assigned a colour and there are


4. Colour per minimum noise rise Atoll displays bins where ( ) NRicNR DL

thresholdic

DL ≥min . Coverage consists of several areas with an area per user-defined

noise rise threshold defined in the Display tab. Each area is assigned a colour and there are intersections between areas.

5. Colour per maximum noise rise Atoll displays bins where ( ) NRicNR DL

thresholdic

DL ≥max . Coverage consists of several areas with an area per user-defined


6. Colour per average noise rise Atoll displays bins where ( ) NRicNRaverage DL

thresholdic

DL ≥ . Coverage consists of several areas with an area per user-defined




XIV.6.2.d.ii Analysis on a given carrier When only one carrier is analysed, Atoll determines DL total noise or DL noise rise on this carrier. In this case, the displayed coverage is the same for any selected display per noise level (average, minimum, maximum) or any display per noise rise (average, minimum, maximum).

1. Colour per noise level Coverage consists of several layers with a layer per user-defined noise level defined in the Display tab (Prediction properties). For each layer, area is covered if ( ) NicN DL

thresholdDLtot ≥ . Each layer is assigned a colour and there are


2. Colour per noise rise Atoll displays bins where ( ) NRicNR DL

thresholdDL ≥ . Coverage consists of several areas with an area per user-defined noise rise threshold defined in the Display tab. Each area is assigned a colour and there are intersections between areas.

XIV.7 AUTOMATIC NEIGHBOUR ALLOCATION The intra-technology neighbour allocation algorithm takes into account all the cells of TBC transmitters. It means that all the cells of TBC transmitters of your .atl document are potential neighbours. The cells to be allocated will be called TBA cells. They must fulfil following conditions:


folder or a group of transmitters. Only TBA cells may be assigned neighbours. Note: If no focus zone exists in the .atl document, Atoll takes into account the computation zone.

XIV.7.1 GLOBAL ALLOCATION FOR ALL CELLS We assume a reference cell A and a candidate neighbour, cell B. When automatic allocation starts, Atoll checks the following conditions:

1. The distance between both cells must be lower than the user-definable maximum inter-site distance. If the distance between the reference cell and the candidate neighbour is greater than this value, then the candidate neighbour is discarded.


Force co-site cells as neighbours: This option enables you to force cells located on the reference cell site in the candidate neighbour list. Force adjacent cells as neighbours: This option enables you to force cells geographically adjacent to the reference cell in the candidate neighbour list. Force neighbour symmetry: This option enables user to force the reciprocity of a neighbourhood link. Therefore, if the reference cell is a candidate neighbour of another cell, this one will be considered as candidate neighbour of the reference cell. Force exceptional pairs: This option enables you to force/forbid some neighbourhood relationships. Therefore, you may force/forbid a cell to be candidate neighbour of the reference cell. Reset neighbours: When selecting the Reset option, Atoll deletes all the current neighbours and carries out a new neighbour allocation. If not selected, the existing neighbours are kept.

3. There must be an overlapping zone ( SS BA I ) with a given cell edge coverage probability where:

UMTS documents


SA is the area where:

• The pilot signal received from the cell A is greater than minimum pilot signal level. • The pilot quality from A exceeds a user-definable minimum value (minimum Ec/I0). • The pilot quality from A is the best.

SB is the area where:

• The pilot signal received from the cell B is greater than minimum pilot signal level. • The pilot quality from B is greater than the pilot quality from A minus the Ec/I0 margin. The Ec/I0 margin has the

same meaning as the AS-threshold defined in the Cell properties. So, it should logically have the same value. Notes: 1. SA is the zone where the cell A is the Ec/I0 best serving cell. It means that the cell A is the first in the active set. 2. SB is the zone where the cell B can enter the active set. 3. Two ways enable you to determine the I0 value: A: A reduction factor (% of maximum powers contributing to I0) may be applied to cell maximum powers (defined in Cell properties) to customize their contribution to I0. Thus, I0 represents the sum of effective powers received from the other cells. The entered percentage is a kind of downlink load factor estimation. If the % of maximum powers contributing to I0 is too low, i.e. if PP% pilot<× max , Atoll takes into account the pilot powers to evaluate the I0 value. B: Atoll takes into account load parameters defined per cell (such as the total downlink power used). I0 represents the sum of total transmitted powers.

Atoll calculates the percentage of covered area ( 100×A

BA

SSS I ) and compares this value to the % minimum covered

area. If this percentage is not exceeded, the candidate neighbour B is discarded. Candidate neighbours fulfilling coverage conditions are sorted in descending order with respect to percentage of covered area.

4. Atoll lists all candidate neighbours and sorts them by priority so as to eliminate some of them from the neighbour list if the maximum number of neighbours to be allocated to each cell is exceeded. The candidate neighbour priority depends on the neighbourhood cause. Priority assigned to each neighbourhood cause is listed in the table below (1 is a higher priority than 2 and so on).

Neighbourhood cause

When Priority



Co-site cell Only if the Force co-site cells as neighbours option is selected 3

Adjacent cell Only if the Force adjacent cells as neighbours option is selected 4


Symmetric neighbourhood relationship Only if the Force neighbour symmetry option is selected 6 If there are 15 candidate neighbours and the maximum number of neighbours to be allocated to the reference cell is 8. Among 15 candidate neighbours, only 8 (those with the highest priority) will be allocated to the reference cell. In the Results part, Atoll provides the list of neighbours, the number of neighbours and the maximum number of neighbours allowed for each cell. In addition, it indicates the allocation cause for each neighbour. Therefore, a neighbour may be marked as exceptional pair, co-site, adjacent or symmetric. If the neighbour is not forced but satisfies the coverage conditions, Atoll displays the percentage of covered area and the overlap area (km2) in brackets. Finally, if cells have previous allocations in the list, neighbours are marked as existing. Notes 1. No simulation or prediction study is needed to perform an automatic neighbour allocation. When starting an

automatic neighbour allocation, Atoll automatically calculates the path loss matrices if not found. 2. The neighbour lists may be optionally used in the power control simulations to determine the mobile’s active set. 3. The percentage of covered area is calculated with the resolution specified in the properties dialog of the

predictions folder (default resolution parameter).



4. A forbidden neighbour must not be listed as neighbour except if the neighbourhood relationship already exists and the Reset neighbours option is unchecked when you start the new allocation. In this case, Atoll displays a warning in the Event viewer indicating that the constraint on the forbidden neighbour will be ignored by algorithm because the neighbour already exists.

5. The force neighbour symmetry option enables the users to consider the reciprocity of a neighbourhood link. This reciprocity is allowed only if the neighbour list is not already full. Thus, if the cell B is a neighbour of the cell A while the cell A is not a neighbour of the cell B, two cases are possible:

1st case: There is space in the cell B neighbour list: the cell A will be added to the list. It will be the last one. 2nd case: The cell B neighbour list is full: Atoll will not include cell A in the list and will cancel the link by deleting

cell B from the cell A neighbour list. 6. When the options “Force exceptional pairs” and “Force symmetry” are selected, Atoll considers the constraints

between exceptional pairs in both directions so as to respect symmetry condition. On the other hand, if neighbourhood relationship is forced in one direction and forbidden in the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the Event viewer.

7. In the Results, Atoll displays only the cells for which it finds new neighbours. Therefore, if a TBA cell has already reached its maximum number of neighbours before starting the new allocation, it will not appear in the Results table.

XIV.7.2 ALLOCATION FOR A GROUP OF CELLS In this case, Atoll allocates neighbours to:

- TBA cells, - Neighbours of TBA cells marked as exceptional pair, adjacent and symmetric, - Neighbours of TBA cells that satisfy coverage conditions.

XIV.8 PRIMARY SCRAMBLING CODE ALLOCATION Downlink primary scrambling codes enable you to distinguish cells from one another (cell identification). According to selected allocation options, the primary scrambling code allocation algorithm takes into account either all the cells of TBC transmitters, or only cells of active and filtered transmitters located inside the computation zone. Atoll calculates a scrambling code for all these cells. On the other hand, it allocates primary scrambling codes only to TBA cells (cells to be allocated). TBA cells fulfil following conditions:


folder or a group of transmitters. Note: If no focus zone exists in the .atl document, Atoll takes into account the computation zone.

XIV.8.1 AUTOMATIC ALLOCATION DESCRIPTION The scrambling code allocation algorithm can take into account following constraints:

- Neighbourhood between cells, You may consider:

• The existing neighbours listed in the Intra-technology neighbours table if neighbour allocation has been performed beforehand (option “Existing neighbours”), • The neighbours of listed neighbours (option “Second neighbours”),

Note: With the option “Second neighbours”, Atoll considers both the first neighbours and the second neighbours.

- Cells fulfilling a criterion on Ec/Io (option “Additional Ec/Io conditions”),

For a reference cell “A”, Atoll considers all the cells “B” that can enter the active set on the area where the reference cell is the best server (area where (Ec/Io)A exceeds the minimum Ec/Io and is the highest one and (Ec/Io)B is within a Ec/Io margin of (Ec/Io)A).

Note: Atoll takes the total downlink power used by the cell into account in order to evaluate Io. Io equals the sum of total transmitted powers. In case this parameter is not specified in the cell properties, Atoll uses 50% of the maximum

UMTS documents


power.

- Reuse distance, - Exceptional pairs, - Domains of scrambling codes,

In addition, it depends on the selected allocation strategy:

- Clustered allocation: The purpose of this strategy is to choose scrambling codes among a minimum number of clusters. Atoll will preferentially allocate all the codes within the same cluster.

- Distributed allocation: This strategy consists in using as many clusters as possible. Atoll will preferentially allocate codes from different clusters.

Algorithm works as follows:

1. For each cell i, Atoll establishes a list of “near” cells. For a cell i, its “near” cells may be: a. Its neighbour cells: the neighbours listed in the Intra-technology neighbours table (option “Existing

neighbours”), b. The neighbours of its neighbours (option “Second neighbours”), c. The cells that fulfil Ec/Io condition (option “Additional Ec/Io conditions”), d. The cells with distance from the cell i loss than the reuse distance, e. The cells that make exceptional pairs with cell i.

2. Atoll assigns different primary scrambling codes to a given cell i and to all its “near” cells. The neighbours of

the cell i cannot have the same scrambling code. And if you consider second neighbours, all the neighbours (first neighbours and second neighbours) cannot have the same scrambling code.

Notes: 1. Atoll always considers symmetry relationship between a cell, its neighbours and the second neighbours. 2. When you select the option “Additional Ec/Io conditions”, Atoll calculates a scrambling code for each TBC cell. If

this option is not selected, it determines scrambling codes for cells of active and filtered transmitters located inside the computation zone.

Atoll calculates scrambling codes starting with the highly constrained cell and ending with the lowest constrained one. The constraint level of a cell depends on the number of its “near” cells and how many other cells have this cell as “near”. When cells have the same constraint level, cell processing is based on the order of transmitters in the Transmitters folder. In the Results table, Atoll only displays scrambling codes allocated to TBA cells.

XIV.8.2 ALLOCATION EXAMPLES The scrambling code choice depends on domains associated to cells and on the selected allocation strategy. When no domain is assigned to cells, Atoll uses the 512 primary scrambling codes. Several scenarios are detailed hereafter: Let us consider 10 scrambling codes to be allocated. 1st case: We assume that no domain is assigned to cells. Here, Atoll will be able to use the 512 primary scrambling codes. If you check the “Clustered” option, Atoll will choose eight codes from the cluster 0 and two codes in the cluster 1. Therefore, the allocated scrambling codes will be 0, 1, 2, 3, 4, 5, 6, 7, 8, 9. If you check the “Distributed” option, Atoll will take the first codes of clusters 0, 1, 2, 3, 4, 5, 6, 7, 8, 9. So, it will assign the codes 0, 8, 16, 24, 32, 40, 48, 56, 64 and 72. 2nd case: We assume that domain 1 is associated to cells. Domain 1 contains two groups, group 1 consisting of cluster 0 (available codes: 0 to 7) and group 2 including clusters 2 and 3 (available codes: 16 to 31). If you check the “Clustered” option, Atoll will choose eight codes in group 1 and two other ones in group 2 (the first two codes of cluster 2). So, allocation result will be 0, 1, 2, 3, 4, 5, 6, 7, 16, 17. If you check the “Distributed” option, Atoll will select the first code of group 1 (cluster 0), the first code of the cluster 2 (group 2), the first code of cluster 3 (group 2), the second code of group 1 (cluster 0), the second code of the cluster 2 (group 2), the second code of cluster 3 (group 2) and so on. Result of allocation will be 0, 16, 24, 1, 17, 25, 2, 18, 26, 3. 3rd case: We assume that domain 1 is associated to cells. Domain 1 contains one group, group 1 consisting of cluster 1 (available codes: 8 to 15). As there are not enough scrambling codes available in group 1, scrambling code allocation fails. Atoll displays a warning in the Events viewer indicating the first cell for which domain constraint is not fulfilled and stops the allocation. In the Results table of the Primary scrambling codes allocation dialog, it gives the scrambling codes that were already assigned to cells before stopping the algorithm.



XIV.9 AUTOMATIC GSM-UMTS NEIGHBOUR ALLOCATION

XIV.9.1 OVERVIEW It is possible to automatically calculate and allocate neighbours between GSM and UMTS networks. In Atoll, it is called inter-technology neighbour allocation. In order to be able to use the inter-technology neighbour allocation algorithm, you must have:

• An .atl document containing the GSM network, GSM.atl, and another one describing the UMTS network, UMTS.atl,

• An existing link on the Transmitters folder of GSM.atl into UMTS.atl or vice-versa. The external neighbour allocation algorithm takes into account all the GSM TBC transmitters. It means that all the TBC transmitters of GSM.atl are potential neighbours. The cells to be allocated will be called TBA cells which, being cells of UMTS.atl, fulfil following conditions:

• They are active, • They satisfy the filter criteria applied to Transmitters folder, • They are located inside the focus zone, • They belong to the folder for which allocation has been executed. This folder can be either the Transmitters

folder or a group of transmitters subfolder. Only UMTS TBA cells may be assigned neighbours.

XIV.9.2 AUTOMATIC ALLOCATION DESCRIPTION The allocation algorithm takes into account criteria listed below:

• The inter-transmitter distance, Transmitter azimuths are taken into account to evaluate the inter-transmitter distance (for further information on inter-transmitter distance calculation, please refer to paragraph XIV.9.3),

• The maximum number of neighbours fixed, • Allocation options, • The selected allocation strategy,

Two allocation strategies are available: the first one is based on distance and the second one on coverage overlapping.

We assume we have a UMTS reference cell, A, and a GSM candidate neighbour, transmitter B.

XIV.9.2.a ALGORITHM BASED ON DISTANCE When automatic allocation starts, Atoll checks following conditions:

1. The distance between the UMTS reference cell and the GSM neighbour must be less than the user-definable maximum inter-site distance. If the distance between the UMTS reference cell and the GSM neighbour is greater than this value, then the candidate neighbour is discarded.

Candidate neighbours are sorted in descending order with respect to distance.


Force co-site cells as neighbours: It enables you to automatically include GSM transmitters located on the same site than the reference UMTS cell in the candidate neighbour list. This option is automatically selected. Force exceptional pairs: This option enables you to force/forbid some neighbourhood relationships. Therefore, you may force/forbid a GSM transmitter to be candidate neighbour of the reference UMTS cell. Reset neighbours: When selecting the Reset option, Atoll deletes all the current neighbours and carries out a new neighbour allocation. If not selected, existing neighbours are kept.

UMTS documents


3. Atoll lists all candidate neighbours and sorts them by priority so as to eliminate some of them from the

neighbour list if the maximum number of neighbours to be allocated to each cell is exceeded. The candidate neighbour priority depends on the neighbourhood cause. Priority assigned to each neighbourhood cause is listed in the table below (1 is a higher priority than 2 and so on).

Neighbourhood cause

When Priority




Neighbourhood relationship that fulfils distance conditions Only if the Max inter-site distance is not exceeded 4

If there are 15 candidate neighbours and the maximum number of neighbours to be allocated to the reference cell is 8. Among 15 candidate neighbours, only 8 (those with the highest priority) will be allocated to the reference cell. In the Results part, Atoll provides the list of neighbours, the number of neighbours and the maximum number of neighbours allowed for each cell. In addition, it indicates the allocation cause for each neighbour. Therefore, a neighbour may be marked as exceptional pair or co-site. If the neighbour is not forced but fulfils distance conditions, Atoll displays the distance from the reference cell. Finally, if cells have previous allocations in the list, neighbours are marked as existing.

XIV.9.2.b ALGORITHM BASED ON COVERAGE OVERLAPPING When automatic allocation starts, Atoll checks following conditions:

1. The distance between the UMTS reference cell and the GSM neighbour must be less than the user-definable maximum inter-site distance. If the distance between the UMTS reference cell and the GSM neighbour is greater than this value, then the candidate neighbour is discarded.


Force co-site cells as neighbours: It enables you to automatically include GSM transmitters located on the same site than the reference UMTS cell in the candidate neighbour list. This option is automatically selected. Force exceptional pairs: This option enables you to force/forbid some neighbourhood relationships. Therefore, you may force/forbid a GSM transmitter to be candidate neighbour of the reference UMTS cell. Reset neighbours: When selecting the Reset option, Atoll deletes all the current neighbours and carries out a new neighbour allocation. If not selected, existing neighbours are kept.

3. There must be an overlapping zone ( SS BA I ) with a given cell edge coverage probability where: SA is the area where the pilot signal received from the cell A is greater than the minimum pilot signal level and the pilot quality from A exceeds a user-definable minimum value (minimum Ec/I0). SB is the area where the signal level received from candidate transmitter B on BCCH TRX type exceeds the specified minimum signal level.


BA






neighbour list if the maximum number of neighbours to be allocated to each cell is exceeded. The candidate neighbour priority depends on the neighbourhood cause. Priority assigned to each neighbourhood cause is listed in the table below (1 is a higher priority than 2 and so on…).

Neighbourhood cause

When Priority





If there are 15 candidate neighbours and the maximum number of neighbours to be allocated to the reference cell is 8. Therefore, among 15 candidate neighbours, only 8 (those with the highest priority) will be allocated to the reference cell. In the Results part, Atoll provides the list of neighbours, the number of neighbours and the maximum number of neighbours allowed for each cell. In addition, it indicates the allocation cause for each neighbour. Therefore, a neighbour may be marked as exceptional pair or co-site. If the neighbour is not forced but fulfils coverage conditions, Atoll displays the percentage of covered area and the overlap area (km2) in brackets. Finally, if cells have previous allocations in the list, neighbours are marked as existing. Notes: 1. No prediction study is needed to perform an automatic neighbour allocation. When starting an automatic

neighbour allocation, Atoll automatically calculates the path loss matrices if not found. 2. The percentage of covered area is calculated with the resolution specified in the properties dialog of the

predictions folder (default resolution parameter). 3. A forbidden neighbour must not be listed as neighbour except if the neighbourhood relationship already exists and



XIV.9.2.c THE RESET OPTION As explained above, Atoll keeps the existing inter-technology neighbours when the Reset option is not checked. We assume that we have an existing allocation of inter-technology neighbours. A new TBA cell i is created in UMTS.atl. Therefore, if you start a new allocation without selecting the Reset option, Atoll determines the neighbour list of the cell i, If you change some allocation criteria (e.g. increase the maximum number of neighbours or create a new GSM TBC transmitter) and start a new allocation without selecting the Reset option, it examines the neighbour list of TBA cells and checks allocation criteria if there is space in their neighbour lists. A new GSM TBC transmitter can enter the TBA cell neighbour list if allocation criteria are satisfied. It will be the first one in the neighbour list.

XIV.9.3 CALCULATION OF THE INTER-TRANSMITTER DISTANCE In order to calculate the effective inter-transmitter distance, Atoll takes into account the real distance and azimuths of antennas.

( ) ( ) ( ))coscos1(, αβ ×−×+×= xxDCellBCellADist

where x = 0.5% so that the maximum D variation not to exceed 1%,

D is stated in m.

UMTS documents


β

Cell A

Cell B

D

α

The formula above implies that two cells facing each other will have a smaller effective distance than the real physical distance. It is this effective distance that will be taken into account rather than the real distance.

C H A P T E R 15

CDMA2000 and IS95-CDMA documents This chapter provides details of formulas, definitions and calculations used in CDMA2000 and IS95-CDMA documents.

15

CDMA2000 and IS-95 documents


XV CDMA2000 AND IS95-CDMA DOCUMENTS

XV.1 GENERAL PREDICTION STUDIES

XV.1.1 CALCULATION CRITERIA Three criteria can be studied in point analysis (Profile tab) and in common coverage studies. Study criteria are detailed in the table below:



Signal level received from a transmitter on a carrier (cell) ( ) ( ) Shadowing

Txipath

Txirec MLicEIRPicP −−=


Txipath Tx

+= model


Txipath

Txitotal RxTx

+−+++=

where,





is the receiver antenna gain, ic is a carrier number,

Notes: 1. It is possible to analyse all the carriers. In this case, Atoll takes the highest pilot power of cells to calculate the

signal level received from a transmitter. 2. TxantTxpilot LGicPicEIRP −+= )()( with LTx=Ltotal-DL.

3. Atoll considers that GantRx and L Rx

equal zero.

XV.1.2 POINT ANALYSIS

XV.1.2.a PROFILE TAB Atoll displays either the signal level received from the selected transmitter on a carrier ( ( )icPTxi

rec ), or the highest signal level received from the selected transmitter on all the carriers. Note: For a selected transmitter, it is also possible to study the path loss, LTxi



XV.1.2.b RECEPTION TAB Analysis provided in the Reception tab is based on path loss matrices. So, you can study reception from TBC transmitters for which path loss matrices have been computed on their calculation areas. For each transmitter, Atoll displays either the signal level received on a carrier, ( ( )icPTxi

rec ), or the highest signal level received on all the carriers. Reception bars are displayed in a decreasing signal level order. The maximum number of reception bars depends on the signal level received from the best server. Only reception bars of transmitters whose signal level is within a 30 dB margin of the best server can be displayed. Note: For a selected transmitter, it is also possible to study the path loss, LTxi





XV.1.3 COVERAGE STUDIES For each TBC transmitter, Txi, Atoll determines the selected criterion on each bin inside the Txi calculation area. In fact, each bin within the Txi calculation area is considered as a potential (fixed or mobile) receiver. Coverage study parameters to be set are:


XV.1.3.a SERVICE AREA DETERMINATION Atoll uses parameters entered in the Condition tab of the coverage study property dialog to predetermine areas where it will display coverage. We can distinguish three cases:

XV.1.3.a.i All the servers The service area of Txi corresponds to the bins where:


Txirec

XV.1.3.a.ii Best signal level and a margin The service area of Txi corresponds to the bins where:


Txirec


recij

Txirec −≥

≠



signal levels from transmitters, which are 2nd best servers.

XV.1.3.a.iii Second best signal level and a margin The service area of Txi corresponds to the bins where:


Txirec


recij

ndTxirec −≥

≠2



signal levels from transmitters, which are 3rd best servers.

XV.1.3.b COVERAGE DISPLAY

XV.1.3.b.i Plot resolution Prediction plot resolution is independent of the matrix resolutions and can be defined on a per study basis. Prediction plots are generated from multi-resolution path loss matrices using bilinear interpolation method (similar to the one used



to evaluate site altitude).

XV.1.3.b.ii Display types It is possible to display the transmitter service area with colours depending on any transmitter attribute or other criteria such as:








• 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. There is one coverage area per transmitter in the explorer.




XV.2 DEFINITIONS AND FORMULAS

Name Value Unit Description Fortho Clutter parameter or global parameter None Orthogonality factor Fmud Global parameter None MUD factor

),( _ icSThAS j Cell parameter None Threshold for macro diversity specified for a station on a given carrier ic

Simulation result

MMG ShadowingnpathShadowing

ULdiversitymacro −=−

n=2 or 3 ULdiversitymacroG −

Global parameter (default value)

None UL quality gain due to signal diversity in soft handoff10.

DLdiversitymacroG −

ShadowingnpathsShadowing


n=2 or 3 None

DL macro-diversity gain due to availability of several pilot signals at the mobile 11.

)(max lUL NNumChElts Site parameter None Number of channel elements

available for a site on uplink

)(max lDL NNumChElts Site parameter None Number of channel elements

available for a site on downlink

)(max lNVDONumChEltsE Site parameter None Number of EVDO channel elements available for a site on uplink and downlink

)( lUL NNumChElts Simulation result None Number of channel elements of a

site consumed by users on uplink

)( lDL NNumChElts Simulation result None

Number of channel elements of a site consumed by users on downlink

)( lNVDONumChEltsE Simulation result None Total number of EVDO channel elements of a site consumed by users on uplink and downlink

Fterm Global parameter None Terminal Noise Factor Ftx Transmitter parameter None Transmitter Noise Factor K 1.38 10-23 J/K Boltzman constant T 293 K Ambient temperature W Spreading bandwidth Hz Spreading Bandwidth

Xmax Simulation parameter None Maximum loading factor TxN0 WTKFTx ××× W Thermal noise at transmitter

TermN0 WTKFTerm ××× W Thermal noise at terminal Rc W Chips/s Chip rate

f ULiencyrake effic Equipment parameter None Uplink rake receiver efficiency

factor

f DLiencyrake effic Terminal parameter None Downlink rake receiver efficiency

factor

( )ServFrate DLSCH Simulation result None

SCH rate factor (drawn following the SCH probabilities of the service)

( )termRDLFCH Terminal parameter Bits/s Downlink FCH nominal rate

( )ServtermR DLSCH , ( ) ( )ServicexFrateterminalR DL

SCHDLFCH Bits/s Downlink SCH bit rate

( )ServFULcoding Service parameter None Service uplink coding factor

( )ServFDLcoding Service parameter None Service downlink coding factor

( )ServAF DLFCH

Service parameter None Activity factor FCH DL

( )ServAFULFCH

Service parameter None Activity factor FCH UL

( )ServR DLFCHb

− FR DLcoding

DLFCH × Bits/s Service downlink FCH effective

bit rate

( )ServR DLSCHb

− FR DLcoding

DLSCH × Bits/s Service downlink SCH effective

bit rate

10 npaths

ShadowingM corresponds to the shadowing margin evaluated from the shadowing error probability density function (n paths) in case of uplink soft

handoff modelling.

11 npathsShadowingM

corresponds to the shadowing margin evaluated from the shadowing error probability density function (n paths) in case of downlink Ec/Io modelling.



( )ServFrateULSCH Simulation result None

SCH rate factor (drawn following the SCH probabilities of the service)

( )termRULFCH Terminal parameter Bits/s Uplink FCH bit rate

),( servtermRULSCH ( ) ( )ServxFratetermR UL

SCHULFCH Bits/s Uplink SCH bit rate

( )ServR ULFCHb

− FR ULcoding

ULFCH × Bits/s Service uplink FCH effective bit

rate

( )ServR ULSCHb

− FR ULcoding

ULSCH × Service uplink SCH effective bit

rate

( )ServG DLFCHp

_ DLFCHR

W None Service downlink FCH process

gain

( )ServG DLSCHp

_ DLSCHRW

None Service downlink SCH process gain

( )ServG ULFCHp

_ ULFCHRW

None Service uplink FCH process gain

( )ServG ULSCHp

_ ULSCHRW

None Service uplink SCH process gain

)(icPSync Cell parameter W Cell synchro channel power

)(icPpaging Cell parameter W Cell other common channels (except CPICH and SCH) power

)(icPpilot Cell parameter W Cell pilot power

)(max icP Cell parameter W Max cell power

( )tchicPFCH , Simulation result including the term )(servAF DLFCH W Cell FCH power for a traffic

channel on carrier ic

( )icPFCH ( )∑))((

,icFCHtch

FCH tchicP W Total FCH power on carrier ic

( )tchicPSCH , Simulation result W Transmitter SCH power for a traffic channel on carrier ic

( )icPSCH ( )∑))((

,icSCHtch

SCH tchicP W Total SCH power on carrier ic

( )icPtx ( ) ( )icPicPicPicPicP FCHSCHpagingSyncpilot ++++ )()()( Transmitter total transmitted power on carrier ic

)(icPFCHterm

Simulation result including the term )(servAF ULFCH W Terminal FCH power transmitted

in carrier ic

)(icPSCHterm

Simulation result W Terminal SCH power transmitted on carrier ic

Gtx Transmitter parameter None Transmitter gain Gterm Terminal parameter None Terminal gain

Ltx Transmitter parameter (user-defined or calculated from

transmitter equipment characteristics) None Transmitter loss12

Lterm Terminal parameter None Terminal loss Lpath Propagation model result None Path loss

bodyL Service parameter None Body loss

MShadowing Result calculated from cell edge coverage probability and model standard deviation None Shadowing margin

Only used in prediction studies

EShadowing Simulation result None Random shadowing error drawn during Monte-Carlo simulation Only used in simulations

LT In prediction studies13

termTx

body ShadowingtermTxpath

GG

MLLLL×

××××

None Transmitter-terminal total loss MShadowing=1 in downlink extra-cellular interference calculations

12 ULtotalTx LL −= on uplink and DLtotalTx LL −= on downlink. 13 In uplink prediction studies, only carrier power level is downgraded by the shadowing margin (MShadowing). In downlink prediction studies, carrier power level and intra-cellular interference are downgraded by the shadowing margin (MShadowing) while extra-cellular interference level is not. Therefore, MShadowing is set to 1 in downlink extra-cellular interference calculation formulas.



In simulations

termTx

body ShadowingtermTxpath

GG

ELLLL×

××××

Transmitter-terminal total loss

)(icPc T

pilot

LicP )(

W Chip received power at terminal

( )tchicP DLFCHb ,_

( )T

FCH

LtchicP ,

W Bit received power at terminal for FCH on carrier ic

( )tchicP DLSCHb ,_

( )T

SCH

LtchicP ,

W Bit received power at terminal for FCH on carrier ic

( )tchicP DLb , ( ) ( )tchicPtchicP DLSCH

bDLFCH

b ,, __ + W Bit received power at terminal for FCH+SCH on carrier ic

( )icP ULFCHb

_ T

FCH

LP

term W Bit received power at transmitter for FCH on carrier ic

( )icP ULSCHb

_ T

SCH

LP

term W Bit received power at transmitter for SCH on carrier ic

( )icPULb ( ) ( )icPicP ULSCH

bULFCH

b__ + W Bit received power at transmitter

for SCH+FCH on carrier ic

( )icP DLtot

( )T

tx

LicP

W Total received power at terminal from a transmitter on carrier ic

( )icP DLtraf

( ) ( )∑ +)( ictch t

SCHFCH

LicPicP

W Total received power at terminal from traffic channels of a transmitter on carrier ic

( )icI DLtot )()(int icIicI DL

extraDL

ra + W Total effective interference at terminal on carrier ic (after unscrambling)

)(int icIDLra

)()1( icPF DLtot

txiortho ×−

W

Downlink intra-cellular interference at terminal on carrier ic14

)(icIDLextra

( )∑≠ ijtxj

DLtot icP

, W

Downlink extra-cellular interference at terminal on carrier ic

( )icI DL0

termDLextraDL

tottxi

NicIicP 0)()( ++ W Total received noise at terminal on carrier ic

( )icN DLtot NicI termDL

tot 0)( + W Total received noise at terminal on carrier ic

( )

⇔

0IEicQ c

pilot ( )icIicP

DLc

0

)( None Quality level at terminal on pilot

for carrier ic

( )icQBSipilot None Pilot quality from the best server

cell at the receiver

( )icQ sultingpilotRe ( )icQG

BSipilotDL

diversitymacro ×− None Best pilot quality level received on carrier ic with a fixed cell edge coverage probability

( )DL

t

bDLFCH

FCHNEtchicQ

⇔,

( )( ) ( ) ( ) ( )

1, _

_

serviceGicPFicN

tchicP DLFCHpDL

borthoDLtot

DLFCHb ×

×−− None

Quality level at terminal on a traffic channel from one transmitter for a FCH channel on carrier ic

)(icQDLFCH [ ]

( )∑

∈×

FCHset Active,

ASiAS

DLFCH

DLiencyrake effic IicQf None

Quality level at terminal for FCH using carrier ic due to combination of all transmitters of the active set (Macro-diversity conditions).

( )DL

t

bDLSCH

SCHNEtchicQ

⇔,

( )( ) ( ) ( ) ( )

1, _

_

serviceGicPFicN

tchicP DLFCHpDL

borthoDLtot

DLSCHb ×

×−− None

Quality level at terminal on a traffic channel from one transmitter for a FCH channel on carrier ic

14 In simulation outputs, Atoll evaluates downlink intra-cellular interference at terminal on carrier ic as follows:

),()1()()1()(int tchicPFicPFicI DLbortho

txi

DLtotortho

DLra ×−−×−=



)(icQDLSCH [ ]

( )∑

∈×

SCHset Active,

ASiAS

DLSCH

DLiencyrake effic IicQf None

Quality level at terminal for FCH using carrier ic due to combination of all transmitters of the active set (Macro-diversity conditions).

( )FCHDLSHOG

( )( )rBest servetchicQ

icQDL

FCH

DLFCH

,, None Downlink soft handover gain for

FCH channel on carrier ic

( )SCHDLSHOG


icQDL

SCH

DLSCH

,, None Downlink soft handover gain for

SCH channel on carrier ic

T Terminal parameter % Pilot power percentage

( )icPULtot

( ) ( ) )(

1001

icPicPTicP UL

cULb

ULb +=

−

W Total power transmitted by the

terminal on carrier ic

)(icPULc ( )icP

T ULtot×

100 W Chip received power at

transmitter

( )icI intraULtot

( )( )∑ +

cell sameterm

)(icPicP ULc

ULb

W Total received power at transmitter from intracell terminals using carrier ic

( )icI extraULtot

( )( )∑ +

othercellsterm

ULb icPicP UL

c )( W

Total received power at transmitter from extracell terminals using carrier ic

( )icIULtot ( ) ( ) ( )icIFicI raUL

totMUDULextratot

int1 ×−+ W Total received interference at transmitter on carrier ic

( )icNULtot ( ) txUL

tot NicI 0+ W Total noise at transmitter on carrier ic (Uplink interference)

pilotreqQ

threshold

c

IE

0

(mobility) parameter None Ec/Io target on downlink for the best server

pilotQmin Tdrop (mobility) parameter None Ec/Io target on downlink for active set members

DLFCHreqQ _

DLFCH

reqt

b

NE

_

(service, mobility) parameter None Eb/Io target on downlink FCH

DLSCHreqQ _

DLSCH

reqt

b

NE

_

(service, mobility, SCH rate multiple) parameter

None Eb/Io target on downlink SCH

DLreqCI

GQ

GQ

DLFCHp

DLFCHreq

DLSCHp

DLSCHreq

−

−

−

−

+

None Required quality on downlink

( )ULt

bULFCH N

EtchicQ

⇔,

( )( ) ( ) ( )

( )serviceGicPFicN

icP

ULFCHp

ULbMUD

ULtot

ULFCHb

_

_

1×

×−− None Quality level at transmitter on a traffic channel for carrier ic

( )ULt

bULSCH N

EtchicQ

⇔,

( )( ) ( ) ( )

( )serviceGicPFicN

icP

ULSCHp

ULbMUD

ULtot

ULSCHb

_

_

1×

×−− None Quality level at transmitter on a traffic channel for carrier ic

Without handoff )(icQUL

tch

Softer HO ∑∈

×

)(Activeset

)(

samesitei

ULtch

AS

ULiencyrake effic icQf

Soft HO, softer/soft

(without MRC) ( ) UL

diversitymacroULtch GicQMax

ActivesetiAS−×

∈

)( )(icQtch

UL

Softer/soft (+ MRC)

ULdiversitymacro

UL

tchi

ULtch

ULiencyrake effic

G

icQicQfMaxAS

−

∈

×

× ∑ )(,)(site other

site) (sameset Active

None

Quality level at site using carrier ic due to combination of all transmitters of the active set located at the same site and taking into account increasing of the quality due to macro-diversity (macro-diversity gain). tch could be FCH or SCH In simulations, 1=−

ULdiversitymacroG .

( )FCHULSHOG


icQUL

FCH

FCH

UL

,, None Uplink soft handover gain for FCH




( )SCHULSHOG


icQUL

TCH

TCH

UL

,, None Uplink soft handover gain for TCH


ULFCHreqQ _

ULFCH

reqt

b

NE

_

(service, mobility) parameter None Eb/Nt target on uplink

ULSCHreqQ _

ULSCH

reqt

b

NE

_

(service, mobility, SCH rate multiple) parameter

None Eb/Nt target on uplink

( )icP reqFCH ( ) ( )icP

icQQ

FCHDL

DLFCHreq

FCH

×_

W

Required transmitter FCH traffic channel power to achieve Eb/Nt target at terminal on carrier ic

( )icP reqSCH ( ) ( )icP

icQQ

SCHDL

DLSCHreq

SCH

×_

W

Required transmitter SCH traffic channel power to achieve Eb/Nt target at terminal on carrier ic

( )icP reqFCHterm

_ ( ) ( )icPicQ

Q FCHFCHUL

ULFCHreq

term×

_

W

Required terminal power to achieve Eb/Nt target at transmitter for FCH on carrier ic

( )icP reqSCHterm

_ ( ) ( )icPicQ

Q SCHSCHUL

ULSCHreq

term×

_

W

Required terminal power to achieve Eb/Nt target at transmitter for SCH on carrier ic

maxX Simulation constraint None Maximum uplink load factor allowed

( )icX UL

Simulation result ( )( )icNicI

ULtot

ULtot

Or cell parameter

None Uplink load factor on carrier ic

)(icFUL ( )

( ) )1(intmud

raULtot

ULtot

FicIicI

−× None Uplink reuse factor on carrier ic

( )iDL txicX , ∑

−+

−tch

orthoDLreq

orthoDL

FCI

FF

)1(1

None Downlink loading factor on carrier ic

)(icFDL ( )

( ) ( )icPFicI

icIicI

DLtotortho

DLtot

DLra

DLtot

×−=

1)()(

int None Downlink reuse factor on a carrier

ic

( )icNRDL ( )( )icX DL−− 1log10 dB Noise rise on downlink

( )icNRUL ( )( )icX UL−− 1log10 dB Noise rise on uplink

( )icPower DL% Simulation result

( )( ) 100/ max ×PicPtx Or cell parameter

None Percentage of max transmitter power used.

),(max icSNumCodes j Simulation constraint None Maximum number of Walsh codes available per cell (128)

),( icSNumCodes j Simulation result None Number of Walsh codes used by the cell

XV.3 ACTIVE SET MANAGEMENT Active set (AS) management is detailed hereafter. Cells entering the mobile’s active set must fulfil the following conditions:

• The best server (first cell entering active set) - The pilot quality from the best server cell must exceed the Ec/Io threshold. Best serving cell is the cell

with the best pilot quality. • Other cells of active set

- They must use the same carrier as the best serving cell, - The pilot quality from other candidate cells must be greater than the T-Drop value, - Other candidate cells must belong to the neighbour list of the best serving cell if this one is located on

a site where equipment imposes this restriction (the “restricted to neighbours” option is selected in the equipment properties).



XV.4 TRAFFIC DATA

XV.4.1 USER DENSITY When no multi-service geo-marketing data is available, user may input usual traffic data like network user densities per service (for example, from adapted GSM Erlang maps) to Atoll. In this case, user profile definition and calculation of deduced activity probability are not necessary to create a traffic scenario, traffic distribution will only depend on densities per service. If you know the network user densities (attempting a connection) per service, just shunt User profile step by defining one service per user profile and one full-hour communication profile per service.

- In service properties: make sure the sum of rate probabilities is 1, for no inactivity. - In user profile properties: define 1 call/hour of 3600s duration.

Therefore, the activity probabilities calculated during simulations will be equal to 1 and subscriber density values defined in Environments will be the network user densities as subscribers have a 100% probability of attempting a connection (no more subscriber densities). Elaborated traffic scenario will fully respect the user profile proportion (i.e. service) given in Environments. You will control the number of users in simulations as well as the service proportion that will drive random trials. Moreover, each user will be connected. Note: This method is not the usual nominal working mode for Atoll. Practical advice: 1. For example, you have Erlang/km2 data for, say, speech service in different environments. First of all, you will

define these environments. This can be translated into the number of traffic channel links using the Erlang B table (with a certain blocking probability), which is the number of users per km2 attempting to make a call. Now that you know the number of potential network user density, you can enter this value in the subscriber density and define the speech user profile as above (1 call/hour and 3600 sec/call).

2. If you have Erlang data per subscriber type and subscriber densities, you can use Atoll’s User Profile properties to enter this information and define environments with these subscriber densities. For the Erlang data, you will enter “number of calls per hour” and “call duration” (for CS services) or “UL and DL volume” (for PS services). For example, if a speech user is characterized by 20mE, this means that the probability that this subscriber will attempt to make a call is 0.02. So we will put a combination of values in the user profile such that the probability of activity = (Number of calls per hour)x(call duration)/3600 = 0.02.

3. If, instead of Erlangs, you have Mbytes per service per environment, you can start by defining these environments. You must convert this total volume per service into the number of attempting network user density. So, if you have 3.84 Mbytes in an environment for a service with 384kbps data rate, this implies that there are 10 users of this service attempting a call. Simply divide the surface of the environment by 10 to get the user density. Since this subscriber density represents attempting network user density, we have to keep the user profile properties (1 call per hour and 3600s per call) such that the probability of activity is 1. So the idea is again the same: if you know how many users will attempt a connection in an environment, you can put network user density value in subscriber density of environment, and give the user a 100% probability of activity (in user profiles).

4. Erlangs represent busy hour traffic. It is an average of the busy hour. But Atoll’s simulations are snapshots, meaning an instance of the busy hour. That instance is not necessarily the average traffic of the busy hour and can deviate. If we use the 20mE to produce 0.02 probability as above, it is a snapshot analysis on an average representation of busy hour. For the extreme cases (upper and lower extremities of the traffic curve), we need to raise or lower one or several values (calls/hr, call duration, subscriber density, or simply the global scaling factor while creating simulations), and run the simulations with different traffic cases: above and below the average.

5. The point to remember is that Atoll obtains, whatever the case, the number of attempting network users (with a certain service, terminal and mobility) to distribute in different areas to run a simulation.

XV.5 SIMULATIONS

XV.5.1 RANDOM TRIAL STRATEGIES During the simulation, a first random trial is performed to determine the number of users and their activity status. The determination of the number of users and the activity status allocation depend on the type of traffic cartography used.



XV.5.1.a SIMULATIONS BASED ON RASTER TRAFFIC AND VECTOR TRAFFIC MAPS Number of subscribers (X) per profile is inferred from surface calculation (S) and profile density (D).

DSX ×= For each behaviour described in a user profile, according to the service, frequency use and exchange volume, Atoll calculates the probability for the user being connected in uplink and in downlink at an instant t. Calculation of the service usage duration per hour ( p0 : probability of being connected):

36000dNp call ×=

where Ncall is the number of calls per hour and d is the average call duration. Calculation of the total number of users trying to access the service j ( ni ):

pXnj 0×= Activity status determination: Calculation of activity probabilities Users are always active on FCH for both links.

Probability of being active on UL: 0=pUL Probability of being active on DL: 0=pDL Probability of being active both on UL and DL: 1=+p DLUL Probability of being inactive: 0=pinactive

Thus, for voice and data services, we have:

Number of inactive users: ( ) 0=×= pninactiven inactivejj Number of users active on UL: ( ) 0=×= pnULn ULjj Number of users active on DL: ( ) 0=×= pnDLn DLjj Number of users active on UL and DL both: ( ) npnDLULn jDLULjj =×=+ +

( ) ( ) ( ) ( ) ( ) ( )DLULninactivenDLULnDLnULntotaln jjjjjj +=++++= Calculation of the total number of users trying to access the service j, for each SCH rate ( kr ) In case of a data service, j, several rate probabilities, PUL

k and PDLk , can be assigned to different rate factors, kr , for SCH

channel. For non-data services, these probabilities are 0. For data service users, a random trial of SCH rate following rate probabilities is performed for each link. For each SCH rate, r k , we have: On UL, ( ) ( )totalnPtotaln jk

kj

UL ×= On DL, ( ) ( )totalnPtotaln jk

kj

DL ×= Note: The total number of users attempting a connection with a certain service remains constant in all the simulations.


All user characteristics determined, a second random trial is performed to obtain their geographical positions.

XV.5.1.b SIMULATIONS BASED ON TRAFFIC MAP PER SERVICE AND PER TRANSMITTER

In case of a data service, j, several rate probabilities, PULk and PDL

k , can be assigned to different rates factor, kr , for SCH



channel. For non-data services, these probabilities are 0. Therefore, the service j global rates on UL and DL, RUL

j and RDLj , are respectively equal to:

AFRPPRrR ULFCH

ULFCHb

k

ULkkb

kk

ULj

ULULFCH ××

−+××= −∑∑ − 1

and

AFRPPRrR DLFCH

DLFCHb

k

DLkkb

kk

DLj

DLDLFCH ××

−+××= −∑∑ − 1

where R ULFCHb

− and R DLFCHb

− are respectively the terminal’s FCH effective rates on UL and DL. For each transmitter, Txi, and each service j:

- Either Atoll deduces the number of active users on UL and DL in the Txi cell using the service j, if you have selected the throughput map option.

RRN UL

j

ULt

UL = and RRN DL

j

DLt

DL =

where RUL

t is the number of kbits per second transmitted on UL in the Txi cell to provide the service j

RDLt is the number of kbits per second transmitted on DL in the Txi cell to supply the service j.

- Or Atoll directly uses the defined NUL and NDL values (number of active users on UL and DL in the Txi cell using the service j), if you have selected the user map option.

Active users on UL and DL both are included in the NUL and NDL values. Therefore, it is necessary to determine accurately the number of active users on UL (nj(UL)), on DL (nj(DL)) and on UL and DL (nj(UL+DL)) both. Calculation of activity probabilities Users are always active on FCH for both links.

Probability of being active on UL: 0=pUL Probability of being active on DL: 0=pDL Probability of being active on UL and DL both: 1=+p DLUL Probability of being inactive: 0=pinactive

Calculation of the number of active users trying to access the service j We have:

( ) Nnpp ULjDLULUL =×+ + ( ) Nnpp DLjDLULDL =×+ +

where, nj is the total number of active users in the Txi cell using the service j. Thus,

( ) ( )NNpppN

pppNDLULn DLUL

DLULDL

DLULDL

DLULUL

DLULULj ,min,min =

+×

+×

=++

+

+

+

( ) ( )DLULnNULn jULj +−=

( ) ( )DLULnNDLn jDLj +−=

and, ( ) ( ) ( )DLULnDLnULnn jjjj +++= Calculation of the number of inactive users trying to access the speech service j

( ) 01 =×−= ppninactiven inactiveinactive

jj

As for the other types of cartography, Atoll considers both active and inactive users for voice and data services.



Calculation of the total number of users trying to access the speech service j ( ) ( ) ninactivenntotaln jjjj =+=

Calculation of the total number of users trying to access the service j, for each SCH rate ( kr ) Therefore, for each SCH rate, kr , we have:

on UL, ( ) ( )totalnPtotaln jkkj

UL ×= on DL, ( ) ( )totalnPtotaln j

DLk

kj ×=

Note: The total number of users attempting a connection with a certain service remains constant in all the simulations.


XV.5.2 POWER CONTROL SIMULATION Based on W-CDMA air interface, CDMA2000 (IS95-CDMA) network automatically regulates itself using traffic driven uplink and downlink power control in order to minimize interference and maximize capacity. Atoll simulates this network regulation mechanism with an iterative algorithm and calculates, for each user distribution, network parameters such as base station power, mobile terminal power, active set and handoff status for each terminal. The power control simulation is based on an iterative algorithm. In each iteration, all the mobiles selected during the user distribution generation (1st step) try to connect to network’s active transmitters with a calculation area. The process is repeated from iteration to iteration until convergence is achieved. The algorithm steps are detailed below.

Initialisation

2nd step : Mi active set determination

3rd step : Uplink power control+

radio resource control

1st step : Mi best server determination

For each mobile Mi

4th step : Downlink power control +

radio resource control

5th step : Uplink and downlink interference update

Congestion and radio resource control

Convergence study



XV.5.2.a ALGORITHM INITIALIZATION Total power on carrier ic ( )icPTx of base station Sj is initialised to )()()( icPicPicP pagingsyncpilot

++ .

Uplink received powers on carrier ic, ( )icI ULintratot and ( )icIULextra

tot , at base station Sj are initialised to 0 W (no connected mobile).

( ) ( )( ) 0

,,

, ==⇔icSNicSI

icSXj

ULtot

jULtot

jk

XV.5.2.b PRESENTATION OF THE ALGORITHM The algorithm is detailed for any iteration k. Xk is the value of the variable X at the iteration k. In the algorithm, all ( )targettb NE and ( )targettb NE thresholds depend on user mobility and are defined in Service and Mobility parameters tables. All variables are described in Definitions and formulas part. For each mobile Mi

XV.5.2.b.i Determination of Mi’s Best server (SBS(Mi)) For each station Sj containing Mi in its calculation area,

Calculation of ( )ijk MSrBestCarrie , . For each carrier ic used by Sj, we calculate current load factor:

( ) ( )( )icSN

icSIicSX

jULtot

jULtot

jk ,,

, =

EndFor If carrier selection mode is “UL min noise”

( )ijk MSrBestCarrie , is the carrier with the lowest ( )icSX jk , Else if carrier selection mode is “DL min power”

( )ijk MSrBestCarrie , is the carrier with the lowest ( )kjtx icSP ,

Else if carrier selection mode is “Random”

( )ijk MSrBestCarrie , is randomly selected

Calculation of ( ) ( )( )( )ijk

DLjic

jipilot MSrBestCarrieIrBestcarrieSMP

rBestcarrieSMQk ,

,,,,

0

=


pilotreqjipilot MMobilityQrBestcarrieSMQ

k<,, then Sj is rejected by Mi

If ( ) ( )( )ipilotjipilot MQrBestcarrieSMQkk

max,, > Admission control (If simulation respects a load factor constraint and Mi was not connected in previous iteration). If ( )( ) max,, XMSrBestCarrieSX ijkjk > , then Sj is rejected by Mi Else

( ) ( )rBestcarrieSMQMQ jipilotipilot kk,,max =

( ) jiBS SMS = Endif

EndFor If no SBS has been selected, Mi cannot get a connection to the network In the following lines, we will consider ( )( )iiBSk

MMSrBestCarrieic ,=

XV.5.2.b.ii Determination of the active set For each station Sj containing Mi in its calculation area, using ic , and if neighbours are used, neighbour of SBS(Mi)



Calculation of ( ) ( )( )icI

SMPicSMQ DL

jicjipilotk

0

,,, =


pilotjipilot MMobilityQicSMQ

k min,, < then Sj is rejected by Mi

Ejection of Sj from the active set if difference with the best server is too high If ( ) ( ) ),(_,,max icSThASicSMQMQ BSjipilotipilot kk

>− then Sj is rejected Else Sj is included in the Mi active set Ejection of Sj if the Mi active set is full Station with the lowest

kpilotQ in the active set is rejected EndFor

XV.5.2.b.iii Uplink power control Calculation of the required power for Mi, ( )ki

reqterm icMP ,

If the mobile uses a circuit switched service (active or inactive in uplink) or a packet switched service (active in uplink) Note: For inactive mobile in packet switched mode, this power is calculated for information only.

For each cell (Sj,ic) present in the Mi active set Calculation of quality level on Mi traffic channel at (Sj,ic), with the minimum power allowed on traffic channel for the Mi service

( ) ( )( )jiT

FCHki

reqtermFCH

jiULb ,SML

icMPic,SMP 1,

, −= ( ) ( )( )jiT

SCHki

reqtermSCH

jiULb ,SML

icMPic,SMP 1,

, −=

( ) ( )( ) ( ) ( ) ( )( ) ( )serviceG

ic,SMPic,SMPFicNic,SMP

ic,SMQ FCH_ULpSCH

jiULb

FCHji

ULbMUD

ULtot

FCHji

ULbFCH

kjiULtch ×

+×−−=

,,1

,,

( ) ( )( ) ( ) ( ) ( )( ) ( )serviceG

ic,SMPic,SMPFicNic,SMP

ic,SMQ SCH_ULpSCH

jiULb

FCHji

ULbMUD

ULtot

SCHji

ULbSCH

kjiULtch ×

+×−−=

,,1

,,

End For If (Mi is not in handoff)

( ) ( )FCHFCH icS,MQMQ jiUL

tchiUL

k ,= ( ) ( )SCHSCH icS,MQMQ jiUL

tchiUL

k ,= Else if (Mi is in softer handoff)

( ) ( )∑∈

×=Active setS

FCHkji

ULtch

ULiencyrake effic

FCHi

ULk

j

ic,SMQfMQ ,

( ) ( )∑∈

×=Active setS

SCHkji

ULtch

ULiencyrake effic

SCHi

ULk

j

ic,SMQfMQ ,

Else if (Mi is in soft or softer/soft without MRC) ( ) ( )( ) ( )UL

diversitymacro linksFCHkji

ULtch

FCHi

ULk Gic,SMQMaxMQ

Active setASi−×=

∈2

,

( ) ( )( ) ( )ULdiversitymacro links

SCHkji

ULtch

SCHi

ULk Gic,SMQMaxMQ

Active setASi−×=

∈2

,

Else if (Mi is in soft/soft) ( ) ( )( ) ( )UL

diversitymacro linksFCHkji

ULtch

FCHi

ULk Gic,SMQMaxMQ

Active setASi−×=

∈3

,

( ) ( )( ) ( )ULdiversitymacro links

SCHkji

ULtch

SCHi

ULk Gic,SMQMaxMQ

Active setASi−×=

∈3

,

Else if (Mi is in softer/soft with MRC)

( ) ( )ULdiversitymacro links

FCHUL

tchothersite

FCH

)(same siteActive seti

ULtch

ULiencyrake effic

FCHi

ULk GicQ,icQfMaxMQ

AS

−∈

× ×

= ∑ 2)()(

( ) ( )ULdiversitymacro links

SCHUL

tchothersite

SCH

)(same siteActive seti

ULtch

ULiencyrake effic

SCHi

ULk GicQ,icQfMaxMQ

AS

−∈

× ×

= ∑ 2)()(

End If



( ) ( ) ( )( )( ) ( )FCH

kireq

termFCHi

ULk

iiFCH_ULreqFCH

kireq

term icMPMQ

M,MobilityMServiceQ,icMP 1, −×=

( ) ( ) ( )( )( ) ( )SCH

kireq

termSCHi

ULk

iiSCH_ULreqSCH

kireq

term icMPMQ

multiple,SCH_rate_M,MobilityMServiceQ,icMP 1, −×=

( ) ( ) ( )SCHki

reqterm

FCHki

reqtermki

reqterm ,icMP,icMP,icMP +=

If ( ) ( )itermkireq

term MPicMP min, < then

( ) ( )( ) ( )FCH

kireq

termki

reqterm

jitermFCHki

reqterm icMP

MP,SMP

icMP ,,min

×=

( ) ( )( ) ( )SCH

kireq

termki

reqterm

jitermSCHki

reqterm icMP

MP,SMP

icMP ,,min

×=

End If If ( ) ( )iterm

FCHi

reqterm MP,icMP

k

max> then Mi cannot select any station and its active set is cleared

If ( ) (Mi)PicMP termkireq

termmax, > and Mi uses SCH then

Downgrading of service SCH rate: While ( ) (Mi)PicMP termki

reqterm

max, > and ( )( ) ( )( ) 2×> −−i

ULFCHbi

ULSCHb MServiceRateMServiceRate

( )( ) ( )( )2

iULSCH

bi

ULSCHb

MServiceRateMServiceRate−

− =

( ) ( ) ( ) ( ) ( )( )( ) ( ) ( )( )22 ×

×= −

−

)Service(M,RateM,MobilityMServiceQ)Service(M,RateM,MobilityMServiceQ,icMP

,icMPi

ULSCHbii

SCH_ULreq

iULSCH

biiSCH_ULreq

SCHki

reqtermSCH

kireq

term

( ) ( ) ( )FCHki

reqterm

SCHki

reqtermki


EndWhile if ( ) ( )itermi

reqterm MP,icMP

k

max> then Mi will not use SCH Endif

Endif If required number of channel elements exceeds the available quantity in the site of Sj (Best server of Mi) and Mi uses SCH then

Downgrading of Service SCH rate: While ( ) ( )j

ULi

UL SNumChEltsMNumChElts max> and ( )( ) ( )( ) 2×> −−i

ULFCHbi

ULSCHb MServiceRateMServiceRate

( )( ) ( )( )2

MServiceRateMServiceRate iULSCH

bi

ULSCHb

−− =

( ) ( )2

iUL SCH

ki

UL SCHk

MNumChEltsMNumChElts =

( ) ( ) ( ) ( ) ( )( )( ) ( ) ( )( )22 ×

×= −

−

)Service(M,RateM,MobilityMServiceQ)Service(M,RateM,MobilityMServiceQ,icMP

,icMPi

ULSCHbii

SCH_ULreq

iULSCH

biiSCH_ULreq

SCHki

reqtermSCH

kireq

term

( ) ( ) ( )FCHki

reqterm

SCHki

reqtermki


( ) ( ) ( )FCHki

ULSCHki

ULki

UL MNumChEltsMNumChEltsMNumChElts += EndWhile

Endif

XV.5.2.b.iv Downlink power control If Mi uses an SCH on the downlink

For each cell (Sj,ic) in Mi FCH active set Calculation of quality level on (Sj,ic) FCH at Mi, with the minimum power allowed on FCH for the Mi service

( ) ( )( )( )jiT

iFCHFCHji

DLb SML

MPicSMP,

Service,,min

=

( ) ( )( ) ( ) ( ) ( )( )i

FCH_DLp

jiDL

borthoDLtot

FCHjiDL

b

kjiDLFCH MServiceG

ic,SMPFicN,SMP

ic,SMQ ××−−

=,1

,

If cell (Sj,ic) in Mi SCH active set

Calculation of quality level on (Sj,ic) FCH at Mi, with the minimum power allowed on FCH for the Mi service

( ) ( )( )( )SML

MServicePicSMPjiT

iSCHSCHji

DLb ,

,,min

=



( ) ( )( ) ( ) ( ) ( )( )i

SCH_DLp

jiDL

borthoDLtot

SCHjiDL

b

kjiDLSCH MServiceG

ic,SMPFicN,SMP

ic,SMQ ××−−

=,1

,

End if End For

( ) ( )( )

∑∈

×=FCHActivesetSj

kjiDLFCH

DLiencyrake efficFCHi

DLk icSMQfMQ ,,

( ) ( )( )

∑∈

×=SCHActivesetSj

kjiDLSCH

DLiencyrake efficSCHi

DLk icSMQfMQ ,,

Do For each cell (Sj,ic) in Mi FCH active set

Calculation of the required power for DL traffic channel between (Sj,ic) and Mi:

( ) ( ) ( ) ( )( )( ) ( )( )iFCH

FCHiDLk

FCHiDLSCH

biiDLreqFCH

kjireq

tch MPMQ

MServiceRateMMQicSMP service

)(,Mobility,Service,, min×=

−

If ( ) ( )( )iFCH

FCHji

reqtch MPicSMP

kService,, max> then ( )icS j , is tuned at max

tchP

Recalculation of a decreased DLreqQ (a part of the required quality is managed by the cells tuned at max

tchP )

If cell (Sj,ic) in Mi SCH active set Calculation of the required power for DL traffic channel between (Sj,ic) and Mi:

( ) ( ) ( )( )( ) ( )( )iSCH

SCHiDLk

SCHiiDLreqSCH

kjireq

tch MPMQ

MMQicSMP service

Mobility,Service,, min×=

Downgrading of Service SCH rate (Only for (Sj,ic) best server cell of Mi): While ( ) ( ) ( )( )( )i

DLSCHbiSCH

SCHji

reqtch MServiceRateMPicSMP

k

−> ,Service,, max or ( ) ( ) ( )icSPicSMPicSP jtxkjireq

tchkjtx ,,,, max>+

and ( )( ) ( )( ) 2ServiceService ×> −−i

DLFCHbi

DLSCHb MRateMRate

( )( ) ( )( )2

MServiceRateMServiceRate iDLSCH

bi

DLSCHb

−− =

( ) ( ) ( ) ( ) ( )( )( ) ( ) ( )( )2)(,Mobility,Service

)(,Mobility,Service2

,,,, _

_

××= −

−

iDLSCH

biiDLSCH

req

iDLSCH

biiDLSCH

reqSCHkji

reqtchSCH

kjireq

tch MServiceRateMMQMServiceRateMMQicSMP

icSMP

( ) ( ) ( )FCHkji

reqtch

SCHkji

reqtchkji

reqtch ic,SMPic,SMPic,SMP ,,, +=

EndWhile If ( ) ( )( )MServicePicSMP iSCH

SCHkji

reqtch

max,, > or ( ) ( ) ( )icSPicSMPicSP jtxji kreqtchj ktx ,,,, max>+ then Mi will not use SCH

Endif While ( ) ( )j

DLi

DL SNumChEltsMNumChElts max> and ( )( ) ( )( ) 2×> −−i

DLFCHbi

DLSCHb MServiceRateMServiceRate

( )( ) ( )( )2

iDLSCH

bi

DLSCHb

MServiceRateMServiceRate−

− =

2)(

)(MiNumChElts

MiNumChEltsDL SCH

kDL SCH

k=



,,,, _

_

××= −

−

iDLSCH

biiDLSCH

req

iDLSCH

biiDLSCH

reqSCHkji

reqtchSCH

kjireq


icSMP

( ) ( ) ( )FCHkji

reqtch

SCHkji

reqtchkji

reqtch icSMPicSMPicSMP ,,,,,, +=

( ) ( ) ( )FCHki

DLSCHki

DLki

DL MNumChEltsMNumChEltsMNumChElts += EndWhile If ( ) ( )j

DLi

DL SNumChEltsMNumChElts max> then Mi will not use SCH Endif While ( ) ( )icSNumCodesMNumCodes ji ,max> and ( )( ) ( )( ) 2ServiceService ×> −−

iDLFCH

biDLSCH

b MRateMRate

( )( ) ( )( )2

MServiceRateMServiceRate iDLSCH

bi

DLSCHb

−− =

( ) ( )2

MiNumCodesM iNumCodes

SCH

kSCH

k=





,,,, _

_

××= −

−

iDLSCH

biiDLSCH

req

iDLSCH

biiDLSCH

reqSCHkji

reqtchSCH

kjireq


icSMP

( ) ( ) ( )FCHkji

reqtch

SCHkji

reqtchkji

reqtch icSMPicSMPicSMP ,,,,,, +=

( ) ( ) ( )FCHki

SCHkiki MNumCodesMNumCodesMNumCodes +=

EndWhile If ( ) ( )ji SNumCodesMNumCodes max> then Mi will not use SCH Endif

Endif EndFor

( ) ( )( )

∑∈

×=FCHset Active

,,jS

kjiDLFCH

DLiencyrake efficFCHi

DLk icSMQfMQ

( ) ( )( )

∑∈

×=SCHset Active

,,jS

kjiDLSCH

DLiencyrake efficSCHi

DLk icSMQfMQ

While ( ) ( ) ( )( )iiDLreqi

DLk M,MobilityMServiceQMQ < and Mi FCH active set is not empty and

( ) ( ) ( )( )iiDLreqi

DLk MMQMQ Mobility,Service< (if SCH active set is not empty)

Endif

XV.5.2.b.v Uplink and downlink interference updates Update of interference on active mobiles only (old contributions of mobiles and stations are replaced by the new ones). For each cell (Sj,ic)

Update of ( )icSN jULtot ,

EndFor For each mobile Mi

Update of ( )icN DLtot

EndFor EndFor

XV.5.2.b.vi Control of radio resource limits (Walsh codes, cell power and site channel elements) For each cell (Sj,ic)

While ( ) ( )icSPicSP jtxkjtx ,, max>



EndFor For each cell (Sj,ic)

While ( ) ( )icSNumCodesicSNumCodes jkj ,, max> Ejection of last admitted mobile

EndFor For each site (Node B) Nl

While ( ) ( )lDL

klDL NNumChEltsNNumChElts max>


reqtch SMP , for the lowest service priority

While ( ) ( )lUL

klUL NNumChEltsNNumChElts max>

Ejection of mobile with highest ( )kireq

term icMP , for the lowest service priority EndFor

XV.5.2.b.vii Uplink load factor control For each cell (Sj,ic) with XUL(Sj,ic) > Xmax

Ejection of a mobile with the lowest service priority EndFor While at least one cell with XUL(Sj,ic) > Xmax exists



XV.5.2.c CONVERGENCE CRITERION The convergence criteria are evaluated at each iteration, and can be written as follow:

( ) ( )( )

( ) ( )( )

( ) ( )( )

( ) ( )( )

×

−

×

−=

×

−

×

−=

−−

−−

100max

int100maxintmax

100max

int100max

intmax

11

11

icN

icNicN,

icIicIicI∆

icN

icNicN,

icP

icPicP∆

kULuser

kULuserk

ULuserStations

kULtot

kULtotk

ULtot

StationsUL

kDLuser

kDLuserk

DLuserStations

ktx

ktxktxStationsDL

Atoll stops the algorithm if: 1st case: Between two successive iterations, UL∆ and DL∆ are lower ( ≤ ) than their respective thresholds (defined when creating a simulation). The simulation has reached convergence. Example: Let us assume that the maximum number of iterations is 100, UL and DL convergence thresholds are set to 5. If 5≤∆UL and 5≤∆DL between the 4th and the 5th iteration, Atoll stops the algorithm after the 5th iteration. Convergence has been achieved. 2nd case: After 30 iterations, UL∆ or/and DL∆ are still higher than their respective thresholds and from the 30th iteration,

UL∆ or/and DL∆ do not decrease during the next 15 successive iterations. The simulation has not reached convergence (specific divergence symbol). Examples: Let us assume that the maximum number of iterations is 100, UL and DL convergence thresholds are set to 5. 1. After the 30th iteration, UL∆ and/or DL∆ equal 100 and do not decrease during the next 15 successive iterations: Atoll stops the algorithm at the 46th iteration. Convergence has not been achieved. 2. After the 30th iteration, UL∆ and/or DL∆ equal 80, they start decreasing slowly until the 40th iteration (without going under the thresholds) and then do not change during the next 15 successive iterations: Atoll stops the algorithm at the 56th iteration without achieving convergence. 3rd case: After the last iteration. If UL∆ and/or DL∆ are still strictly higher than their respective thresholds, the simulation has not converged (specific divergence symbol). If UL∆ and DL∆ are lower than their respective thresholds, the simulation has converged.

XV.5.3 APPENDICES

XV.5.3.a ADMISSION CONTROL During admission control, Atoll calculates the uplink load factor of a considered cell assuming the mobile concerned is connected with it. Here, activity status assigned to users is not taken into account. So even if the mobile is not active on UL, it can be rejected due to cell load saturation. To calculate the cell UL load factor, either Atoll takes into account the mobile power determined during power control if mobile was connected in previous iteration, or it estimates a load rise due to the mobile and adds it to the current load. The load rise ( ULX∆ ) is calculated as follows:

RQWX

ULb

ULreq

UL

×+

=∆1

1

where QQQ SCHULreq

FCHULreq

ULreq

−− +=

XV.5.3.b WALSH CODE MANAGEMENT Walsh codes are managed on the downlink during a simulation. Atoll performs Walsh code allocation during the radio resource control step. Walsh codes form a binary tree with codes of a longer length generated from codes of a shorter length. Length-k Walsh



codes are generated from length-k/2 Walsh codes. Therefore, if a channel needs 1 length-k/2 Walsh code, it is equivalent to using 2 length-k Walsh codes, or 4 length-2k Walsh codes and so on.

128 128-bit-length Walsh codes per cell are available in CDMA2000 and IS95-CDMA documents. During the resource control, Atoll determines the number of codes that will be consumed by each cell. Therefore, it allocates:

• A code with the longest length per common channel for each cell, • A code per cell-receiver link, for FCH. The length of code to be allocated, Code-Length, is determined as

follows:

WRLengthCode DLFCHb =×− −

• A code per cell-receiver link for SCH, in case SCH is supported by the user radio configuration. The length of

code to be allocated, Code-Length, is determined as follows:

WRLengthCode DLSCHb =×− −

When the calculated code length does not correspond to the code lengths available in the tree, Atoll allocates the code with the shorter length. For instance, Atoll will use a 64 bit Walsh code in case the calculated code length is 100. The Walsh code allocation follows the “Buddy” algorithm, which guarantees that:

• If a k-length Walsh code is used, all of its children with lengths 2k, 4k, …, cannot be used as they are not orthogonal.

• If a k-length Walsh code is used, all of its ancestors with lengths k/2, k/4, …, cannot be used as they are not orthogonal.

Notes: 1. The Walsh code allocation follows the mobile connection order (mobile order in the Mobiles tab). 2. The Walsh code and channel element management is dealt with differently in case of “softer” handoff. Atoll

allocates Walsh codes for each transmitter-receiver link while it assigns channel elements globally to a site.

XV.5.3.c DOWNLINK LOAD FACTOR CALCULATION Approach for downlink load factor evaluation is highly inspired by the downlink load factor defined in the book “WCDMA for UMTS by Harry Holma and Antti Toskala”.

Let GQ

GQ

CI FCHDLp

SCHDLreq

FCHDLp

FCHDLreq

req −

−

−

−

+= be the required quality.

So, we have CICICI SCH

reqFCHreqreq +=

In case of soft-handoff, required quality is limited to the effective contribution of the transmitter.

∑+=++++=tch

tchortho

CCHFCHSCHpagingsyncpilotDL

tx icPicPicPicPicPicPicPicP )()()()()()()()(

where )()()()( icPicPicPicP pagingsyncpilot

orthoCCH ++=



)()()( icPicPicP FCHSCHtch

tch +=∑

At mobile level, we have a required power, Ptch:

( ) Tterm

raextrareqtch LNicIicICIicP ×++×= 0int )()()(

( ) ( )T

term

T

tchDLtx

orthoextrareqtch LNL

icPicPFicICIicP ×

+

−×−+×= 0

)()(1)()(

( )( )

( )orthoreq

TtermDL

txorthoTextratch

FCI

LNicPFLicIicP−+

×+×−+×=

11)(1)(

)( 0

where )(int icIDL

ra is the total power received at receiver from the cell to which it is connected. )(icIDL

extra is the total power received at receiver from other cells.

( )( )( )

∑−+

×+×−+×+=tch

orthoreq

TtermDL

txorthoTextraorthoCCH

DLtx

FCI

LNicPFLicIicPicP11

)(1)()()( 0

Let FDL be the downlink reuse factor:

DLtx

Textra

ra

extraDL

PLicI

icIicIF ×==− )(

)()(1

int

We have:

( )( )

∑−+

×+×−+×−+=tch

orthoreq

TtermDL

txorthoDLtx

DLorthoCCH

DLtx

FCI

LNicPFicPFicPicP11

)(1)()1()()( 0

( )( ) ( )

∑∑

−+

×+=−+

−−

tchortho

req

Tterm

orthoCCH

DLtx

orthoreq

tchortho

DL

DLtx

FCI

LNicPicPF

CI

FFicP

11)()(11)( 0

( )

( )∑

∑

−+

−−

−+

×+

=

tchortho

req

orthoDL

tchortho

req

Tterm

orthoCCH

DLtx

FCI

FF

FCI

LNicP

icP

111

11)(

)(

0

Therefore, the downlink load factor can be expressed as:

( )∑

−+

−=tch

orthoreq

orthoDL

DL

FCI

FFX11

The downlink load factor represents the signal degradation in relative to the reference interference (thermal noise).

XV.6 AUTOMATIC NEIGHBOUR ALLOCATION The intra-technology neighbour allocation algorithm takes into account all the cells of TBC transmitters. It means that all the cells of TBC transmitters of your .atl document are potential neighbours. The cells to be allocated will be called TBA cells. They must fulfil the following conditions:


folder or a group of transmitters.



Only TBA cells may be assigned neighbours. Note: If no focus zone exists in the .atl document, Atoll takes into account the computation zone.

XV.6.1 GLOBAL ALLOCATION FOR ALL CELLS We assume a reference cell A and a candidate neighbour, cell B.

When automatic allocation starts, Atoll checks following conditions:

1. The distance between both cells must be lower than the user-definable maximum inter-site distance. If the distance between the reference cell and the candidate neighbour is greater than this value, then the candidate neighbour is discarded.


Force co-site cells as neighbours: This option enables you to force cells located on the reference cell site in the candidate neighbour list. Force adjacent cells as neighbours: This option enables you to force cells geographically adjacent to the reference cell in the candidate neighbour list. Force neighbour symmetry: This option enables user to force the reciprocity of a neighbourhood link. Therefore, if the reference cell is a candidate neighbour of another cell, this one will be considered as candidate neighbour of the reference cell. Force exceptional pairs: This option enables you to force/forbid some neighbourhood relationships. Therefore, you may force/forbid a cell to be candidate neighbour of the reference cell. Reset neighbours: When selecting the Reset option, Atoll deletes all the current neighbours and carries out a new neighbour allocation. If not selected, the existing neighbours are kept.

3. There must be an overlapping zone ( SS BA I ) with a given cell edge coverage probability where: SA is the area where:

• The pilot signal received from the cell A is greater than minimum pilot signal level. • The pilot quality from A exceeds a user-definable minimum value (minimum Ec/I0). • The pilot quality from A is the best.

SB is the area where:

• The pilot signal received from the cell B is greater than minimum pilot signal level. • The pilot quality from B is greater than the pilot quality from A minus the Ec/I0 margin.

Notes: 1. SA is the zone where the cell A is the Ec/I0 best serving cell. It means that the cell A is the first in the active set. 2. SB is the zone where the cell B can enter the active set. 3. Two ways enable you to determine the I0 value: A: A reduction factor (% of maximum powers contributing to I0) may be applied to cell maximum powers (defined in Cell properties) to customize their contribution to I0. Thus, I0 represents the sum of effective powers received from the other cells. The entered percentage is a kind of downlink load factor estimation. If the % of maximum powers contributing to I0 is too low, i.e. if PP% pilot<× max , Atoll takes into account the pilot powers to evaluate the I0 value. B: Atoll takes into account load parameters defined per cell (such as the total downlink power used). I0 represents the sum of total transmitted powers.


BA






neighbour list if the maximum number of neighbours to be allocated to each cell is exceeded. The candidate neighbour priority depends on the neighbourhood cause. Priority assigned to each neighbourhood cause is listed in the table below (1 is a higher priority than 2 and so on).

Neighbourhood cause

When Priority




Adjacent cell Only if the Force adjacent cells as neighbours option is selected 4


Symmetric neighbourhood relationship Only if the Force neighbour symmetry option is selected 6 If there are 15 candidate neighbours and the maximum number of neighbours to be allocated to the reference cell is 8. Among 15 candidate neighbours, only 8 (those with the highest priority) will be allocated to the reference cell. In the Results part, Atoll provides the list of neighbours, the number of neighbours and the maximum number of neighbours allowed for each cell. In addition, it indicates the allocation cause for each neighbour. Therefore, a neighbour may be marked as exceptional pair, co-site, adjacent or symmetric. If the neighbour is not forced, but satisfies coverage conditions, Atoll displays the percentage of covered area and the overlap area (km2) in brackets. Finally, if cells have previous allocations in the list, neighbours are marked as existing. Notes 1. No simulation or prediction study is needed to perform an automatic neighbour allocation. When starting an

automatic neighbour allocation, Atoll automatically calculates the path loss matrices if not found. 2. The neighbour lists may be optionally used in the power control simulations to determine the mobile’s active set. 3. The percentage of covered area is calculated with the resolution specified in the properties dialog of the



5. The force neighbour symmetry option enables the users to consider the reciprocity of a neighbourhood link. This reciprocity is allowed only if the neighbour list is not already full. Thus, if the cell B is a neighbour of the cell A while the cell A is not a neighbour of the cell B, two cases are possible:

1st case: There is space in the cell B neighbour list: the cell A will be added to the list. It will be the last one. 2nd case: The cell B neighbour list is full: Atoll will not include cell A in the list and will cancel the link by deleting

cell B from the cell A neighbour list. 6. When the options “Force exceptional pairs” and “Force symmetry” are selected, Atoll considers the constraints

between exceptional pairs in both directions so as to respect symmetry condition. On the other hand, if neighbourhood relationship is forced in one direction and forbidden in the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the Event viewer.


XV.6.2 ALLOCATION FOR A GROUP OF CELLS In this case, Atoll allocates neighbours to:

- TBA cells, - Neighbours of TBA cells marked as exceptional pair, adjacent and symmetric, - Neighbours of TBA cells that satisfy coverage conditions.

XV.7 PN OFFSET ALLOCATION PN offset is used to identify a cell. It is a time offset used by a cell to shift a Pseudo Noise sequence. Mobile processes the strongest received PN sequence and reads its phase that identifies the cell. According to selected allocation options, the PN offset allocation algorithm takes into account either all the cells of TBC transmitters, or only cells of active and filtered transmitters located inside the computation zone. Atoll calculates a PN



offset for each of these cells. On the other hand, it commits PN offsets only to TBA cells (cells to be allocated). TBA cells fulfil the following conditions:


folder or a group of transmitters. Note: If no focus zone exists in the .atl document, Atoll takes into account the computation zone. The PN offset allocation algorithm takes into account the following constraints:

• Neighbourhood between cells, You may consider:

- The existing neighbours listed in the neighbours list if neighbour allocation has been performed beforehand (option “Existing neighbours”),

- The neighbours of listed neighbours (option “Second order neighbours”), Note: With the option “Second neighbours”, Atoll considers the neighbours and the neighbours of neighbours both.

• Cells fulfilling a criterion on Ec/Io (option “Additional Ec/Io conditions”),

For a reference cell “A”, Atoll considers all the cells “B” that can enter the active set on the area where the reference cell is the best server (area where (Ec/Io)A and (Ec/Io)B exceed the minimum Ec/Io).

Note: Atoll takes into account the total downlink power used by the cell in order to evaluate Io. Io equals the sum of total transmitted powers. In case this parameter is not specified in the cell properties, Atoll uses 50% of the maximum power.

• A reuse distance, • Exceptional pairs, • The domains of PN offsets assigned to cells.

Algorithm works as follows:

1. For each cell i, Atoll establishes a list of “near” cells. The “near” cells may be: a. Its neighbour cells: the neighbours listed in the neighbours list (option “Existing neighbours”), b. The neighbours of its neighbours (option “Second neighbours”), c. The cells that fulfil Ec/Io condition (option “Additional Ec/Io conditions”), d. The cells whose distance from the cell i is less than the reuse distance, e. The cells that make exceptional pairs with the cell i.

2. Atoll assigns different PN offsets to a given cell i and to all its “near” cells. The neighbours of the cell i cannot

have the same PN offset and, if you consider second neighbours, all the neighbours (first neighbours and second neighbours) cannot have the same PN offset.

Notes: 1. Atoll always considers symmetry relationship between a cell, its neighbours and the second neighbours. 2. When you select the option “Additional Ec/Io conditions”, Atoll calculates a PN offset for each TBC cell. If this

option is not selected, it determines PN offsets for cells of active and filtered transmitters located inside the computation zone.

Atoll calculates PN offsets starting with the most constrained cell and ending with the least constrained one. The constraint level of a cell depends on the number of its “near” cells and how many times the cell is “near” to other cells. When cells have the same constraint level, cell processing is based on order of transmitters in the Transmitters folder. The PN offset choice depends on domains associated with cells. When no domain is assigned to cells, Atoll considers that 512 PN offsets are available and can be allocated. In the Results table, Atoll only displays PN offsets allocated to TBA cells. Note: When there are not enough PN offsets available, the allocation fails and Atoll displays a warning in the Events viewer. This warning indicates the first cell for which domain constraint is not fulfilled and stops the algorithm. In the Results table of the PN offset allocation dialog, it gives PN offsets assigned to cells before the algorithm was stopped.



XV.8 AUTOMATIC GSM/TDMA-CDMA NEIGHBOUR ALLOCATION

XV.8.1 OVERVIEW It is possible to automatically calculate and allocate neighbours between GSM/TDMA and CDMA (or CDMA2000) networks. In Atoll, it is called inter-technology neighbour allocation. In order to be able to use the inter-technology neighbour allocation algorithm, you must have:

• An .atl document containing the GSM/TDMA network, GSM.atl, and another one containing the CDMA (or CDMA2000) network, CDMA.atl,

• An existing link on the Transmitters folder of GSM.atl into CDMA.atl or vice-versa. The external neighbour allocation algorithm takes into account all the GSM TBC transmitters. It means that all the TBC transmitters of GSM.atl are potential neighbours. The cells to be allocated will be called TBA cells which, being cells of CDMA.atl, fulfil following conditions:

• They are active, • They satisfy the filter criteria applied to Transmitters folder, • They are located inside the focus zone, • They belong to the folder for which allocation has been executed. This folder can be either the Transmitters

folder or a group of transmitters subfolder. Only CDMA TBA cells may be assigned neighbours.

XV.8.2 AUTOMATIC ALLOCATION DESCRIPTION The allocation algorithm takes into account criteria listed below:

• The inter-transmitter distance,

Transmitter azimuths are taken into account to evaluate the inter-transmitter distance (for further information on inter-transmitter distance calculation, please refer to paragraph XIV.9.3),

• The maximum number of neighbours fixed, • Allocation options,

• The selected allocation strategy,

Two allocation strategies are available: the first one is based on distance and the second one on coverage overlapping. We assume we have a CDMA reference cell, A, and a GSM candidate neighbour, transmitter B.

XV.8.2.a ALGORITHM BASED ON DISTANCE When automatic allocation starts, Atoll checks following conditions:

1. The distance between the CDMA reference cell and the GSM neighbour must be less than the user-definable maximum inter-site distance. If the distance between the CDMA reference cell and the GSM neighbour is greater than this value, then the candidate neighbour is discarded.



Force co-site cells as neighbours: It enables you to automatically include GSM transmitters located on the same site than the reference CDMA cell in the candidate neighbour list. This option is automatically selected. Force exceptional pairs: This option enables you to force/forbid some neighbourhood relationships. Therefore, you may force/forbid a GSM transmitter to be candidate neighbour of the reference CDMA cell. Reset neighbours: When selecting the Reset option, Atoll deletes all the current neighbours and carries out a new neighbour allocation. If not selected, existing neighbours are kept.

3. Atoll lists all candidate neighbours and sorts them by priority so as to eliminate some of them from the neighbour list if the maximum number of neighbours to be allocated to each cell is exceeded. The candidate



neighbour priority depends on the neighbourhood cause. Priority assigned to each neighbourhood cause is listed in the table below (1 is a higher priority than 2 and so on).

Neighbourhood cause

When Priority





If there are 15 candidate neighbours and the maximum number of neighbours to be allocated to the reference cell is 8. Among 15 candidate neighbours, only 8 (those with the highest priority) will be allocated to the reference cell. In the Results part, Atoll provides the list of neighbours, the number of neighbours and the maximum number of neighbours allowed for each cell. In addition, it indicates the allocation cause for each neighbour. Therefore, a neighbour may be marked as exceptional pair or co-site. If the neighbour is not forced but satisfies distance conditions, Atoll displays the distance from the reference cell. Finally, if cells have previous allocations in the list, neighbours are marked as existing.

XV.8.2.b ALGORITHM BASED ON COVERAGE OVERLAPPING When automatic allocation starts, Atoll checks following conditions:

1. The distance between the CDMA reference cell and the GSM neighbour must be less than the user-definable maximum inter-site distance. If the distance between the CDMA reference cell and the GSM neighbour is greater than this value, then the candidate neighbour is discarded.


Force co-site cells as neighbours: It enables you to automatically include GSM transmitters located on the same site than the reference CDMA cell in the candidate neighbour list. This option is automatically selected. Force exceptional pairs: This option enables you to force/forbid some neighbourhood relationships. Therefore, you may force/forbid a GSM transmitter to be candidate neighbour of the reference CDMA cell. Reset neighbours: When selecting the Reset option, Atoll deletes all the current neighbours and carries out a new neighbour allocation. If not selected, existing neighbours are kept.

3. There must be an overlapping zone ( SS BA I ) with a given cell edge coverage probability where: SA is the area where the pilot signal received from the cell A is greater than the minimum pilot signal level and the pilot quality from A exceeds a user-definable minimum value (minimum Ec/I0). SB is the area where the signal level received from candidate transmitter B on BCCH TRX type exceeds the specified minimum signal level.


BA






Neighbourhood cause

When Priority





If there are 15 candidate neighbours and the maximum number of neighbours to be allocated to the reference cell is 8. Among 15 candidate neighbours, only 8 (those with the highest priority) will be allocated to the reference cell. In the Results part, Atoll provides the list of neighbours, the number of neighbours and the maximum number of neighbours allowed for each cell. In addition, it indicates the allocation cause for each neighbour. Therefore, a neighbour may be marked as exceptional pair or co-site. If the neighbour is not forced but fulfils coverage conditions, Atoll displays the percentage of covered area and the overlap area (km2) in brackets. Finally, if cells have previous allocations in the list, neighbours are marked as existing. Notes: 1. No prediction study is needed to perform an automatic neighbour allocation. When starting an automatic

neighbour allocation, Atoll automatically calculates the path loss matrices if not found. 2. The percentage of covered area is calculated with the resolution specified in the properties dialog of the




XV.8.2.c THE RESET OPTION As explained above, Atoll keeps the existing inter-technology neighbours when the Reset option is not checked. We assume that we have an existing allocation of inter-technology neighbours. A new TBA cell i is created in CDMA.atl. Therefore, if you start a new allocation without selecting the Reset option, Atoll determines the neighbour list of the cell i, If you change some allocation criteria (e.g. increase the maximum number of neighbours or create a new GSM TBC transmitter) and start a new allocation without selecting the Reset option, it examines the neighbour list of TBA cells and checks allocation criteria if there is space in their neighbour lists. A new GSM TBC transmitter can enter the TBA cell neighbour list if allocation criteria are satisfied. It will be the first one in the neighbour list.

XV.9 AUTOMATIC CDMA-CDMA2000 NEIGHBOUR ALLOCATION

XV.9.1 OVERVIEW It is possible to automatically calculate and allocate neighbours between CDMA and CDMA2000 networks. In Atoll, it is called inter-technology neighbour allocation. In order to be able to use the external neighbour allocation algorithm, you must have:

• An .atl document containing the CDMA2000 network, CDMA2000.atl, and another one containing the CDMA network, CDMA.atl,

• An existing link of the Transmitters folder of CDMA.atl into CDMA2000.atl or vice-versa. The external neighbour allocation algorithm takes into account all the CDMA TBC cells. It means that all the TBC cells of CDMA.atl are potential neighbours. The cells to be allocated will be called TBA cells which, being cells of CDMA2000.atl, fulfil following conditions:

• They are active, • They satisfy the filter criteria applied to Transmitters folder, • They are located inside the focus zone,



• They belong to the folder for which allocation has been executed. This folder can be either the Transmitters folder or a group of transmitters subfolder.

Only CDMA2000 TBA cells may be assigned neighbours.

XV.9.2 AUTOMATIC ALLOCATION DESCRIPTION We assume we have a CDMA2000 reference cell, A, and a CDMA candidate neighbour, cell B. When automatic allocation starts, Atoll checks following conditions:

1. The distance between the CDMA2000 reference cell and the CDMA neighbour must be less than the user-definable maximum inter-site distance. If the distance between the CDMA2000 reference cell and the CDMA neighbour is greater than this value, then the candidate neighbour is discarded.



Force co-site cells as neighbours: It enables you to automatically include CDMA cells located on the same site than the reference CDMA2000 cell in the candidate neighbour list. This option is automatically selected. Force exceptional pairs: This option enables you to force/forbid some neighbourhood relationships. Therefore, you may force/forbid a CDMA cell to be candidate neighbour of the reference CDMA2000 cell. Reset neighbours: When selecting the Reset option, Atoll deletes all the current neighbours and carries out a new neighbour allocation. If not selected, existing neighbours are kept.


Neighbourhood cause

When Priority





If there are 15 candidate neighbours and the maximum number of neighbours to be allocated to the reference cell is 8. Among 15 candidate neighbours, only 8 (those with the highest priority) will be allocated to the reference cell. In the Results part, Atoll provides the list of neighbours, the number of neighbours and the maximum number of neighbours allowed for each cell. In addition, it indicates the allocation cause for each neighbour. Therefore, a neighbour may be marked as exceptional pair or co-site. If the neighbour is not forced but fulfils distance conditions, Atoll displays the distance from the reference cell. Finally, if cells have previous allocations in the list, neighbours are marked as existing. Notes: 1. Transmitter azimuths are taken into account to evaluate the inter-transmitter distance (for further information on

inter-transmitter distance calculation, please refer to paragraph XIV.9.3). 2. A forbidden neighbour must not be listed as neighbour except if the neighbourhood relationship already exists and



XV.9.2.a THE RESET OPTION As explained above, Atoll keeps the existing inter-technology neighbours when the Reset option is not checked. We assume that we have an existing allocation of inter-technology neighbours.



A new TBA cell i is created in CDMA2000.atl. Therefore, if you start a new allocation without selecting the Reset option, Atoll determines the neighbour list of the transmitter i, If you change some allocation criteria (e.g. increase the maximum number of neighbours or create a new CDMA TBC cell) and start a new allocation without selecting the Reset option, it examines the neighbour list of TBA cells and checks allocation criteria if there is space in their neighbour lists. A new CDMA TBC cell can enter the TBA cell neighbour list if allocation criteria are satisfied. It will be the first one in the neighbour list.

C H A P T E R 16

Repeaters This chapter focuses on the repeater model in GSM/TDMA, UMTS, CDMA2000, CDMA/IS95 documents in Atoll.

16

Repeaters


XVI REPEATERS

XVI.1 OVERVIEW Repeater modelling focuses on impact of the additional coverage they provide to transmitters. A repeater is modelled in the same manner for GSM/TDMA and UMTS/CDMA/CDMA2000 networks, except that in the 2G networks Atoll deals with EIRP while in the 3G it is concerned with a global amplification gain. We assume that all the TRXs of 2G donor transmitters and all the carriers of 3G donor transmitters are amplified. In UMTS/CDMA/CDMA2000 documents, Atoll calculates the signal level received from a repeater Rpk on a carrier ic as follows:

ShadowingRpkpath

Rpktotal

Txdpilot

Rpkrec MLGicPicP −−+= )()( (in dB)

where

( )icPTxdpilot is the pilot power of the donor transmitter on the carrier ic, RpktotalG is the output global amplification gain of repeater,

RpkpathL is the path loss between the repeater Rpk and the receiver,

ShadowingM is the shadowing margin. In GSM/TDMA documents, Atoll evaluates the signal level received from a repeater Rpk on a TRX type tt as follows:

( ) ( ) ( ) ( )RxantShadowingRpkpath

RpkRpkrec LGMLttPttEIRPttP Rx

−+−−∆−= (in dB) where

)(ttEIRP Rpk is the effective isotropic radiated power of the repeater on the TRX type tt, )(ttP∆ is the power offset defined for the selected TRX type,

RxL is the receiver loss, Gant Rx

is the receiver antenna gain, RpkpathL is the path loss between the repeater Rpk and the receiver,

ShadowingM is the shadowing margin. Global amplification gain and EIRP can be either user-specified or directly calculated by Atoll from the link budget.

XVI.2 AUTOMATIC CALCULATION

XVI.2.1 GLOBAL AMPLIFICATION GAIN Global amplification gain is calculated as follows:

sideerageRpkfeeder

sideerageRpkant

Rpkamp

sidedonorRpkfeeder

sidedonorRpkant

RpkTxdel

TxdDLtotal

Txdant

Rpktotal LGGLGLLGG −−−−−−−−−

− −++−+−−= covcovmod (in dB)

where

TxdantG is the gain of the donor transmitter antenna,

TxdDLtotalL − corresponds to the total downlink losses of the donor transmitter (user-defined or calculated considering

transmitter equipment characteristics), RpkTxdelL −

mod is the path loss calculated with UIT.526-5 propagation model between the donor transmitter and the repeater,

sidedonorRpkantG −− is the gain of the repeater’s donor side antenna,

sidedonorRpkfeederL −− refers to the losses of the repeater donor side due to feeders (see Transmitter radio equipments

part), RpkampG is the amplifier gain of the repeater,



sideerageRpkantG −−cov is the gain of the repeater coverage side antenna,

sideerageRpkfeederL −−cov corresponds to the losses of the repeater coverage side due to feeders (see Transmitter radio

equipments part).

XVI.2.2 EIRP EIRP is calculated as follows:

sideerageRpkfeeder

sideerageRpkant

Rpkamp

sidedonorRpkfeeder

sidedonorRpkant

RpkTxdel

TxdDLtotal

Txdant

TxdRpk LGGLGLLGPEIRP −−−−−−−−−− −++−+−−+= covcov

mod (dB) where

TxdP is the power of the donor transmitter, TxdantG is the gain of the donor transmitter antenna,

TxdDLtotalL − corresponds to the total downlink losses of the donor transmitter (user-defined or calculated considering

transmitter equipment characteristics), RpkTxdelL −

mod is the path loss calculated with UIT.526-5 propagation model between the donor transmitter and the repeater,

sidedonorRpkantG −− is the gain of the repeater donor side antenna,

sidedonorRpkfeederL −− refers to the losses of the repeater donor side due to feeders (see Transmitter radio equipments

part), RpkampG is the amplifier gain of the repeater,

sideerageRpkantG −−cov is the gain of the repeater coverage side antenna,

sideerageRpkfeederL −−cov corresponds to the losses of the repeater coverage side due to feeders (see Transmitter radio

equipments part.

XVI.3 STANDARD PREDICTION STUDIES

XVI.3.1 POINT ANALYSIS

XVI.3.1.a PROFILE TAB It is possible to study the profile between a repeater and a target receiver. Atoll displays the signal level received from the repeater, Rpk

recP , on a carrier ic or a TRX type tt (calculated as explained in the paragraph XVI.1).

XVI.3.1.b RECEPTION AND RESULTS TABS For each transmitter, Atoll displays the signal level received on a carrier ic or a TRX type tt:

Rpkrec

Txdrec

RpkTxdrec PPP +=− (not in dB*)

XVI.3.2 COVERAGE STUDIES The calculation area is the union of calculation areas of the donor transmitter and the repeater. Atoll displays a composite coverage. On each pixel, received signal (on a carrier ic or a TRX type tt) is calculated as follows:

Rpkrec

Txdrec

RpkTxdrec PPP +=− (not in dB*)

The unsynchronisation, which would lead to constructive or destructive effect on signals, is not modelled.

* Formula cannot be directly calculated from components stated in dB and, therefore, must be converted in linear values.

Repeaters


XVI.4 UMTS SPECIFIC PREDICTION STUDIES Ec/Io and downlink Eb/Nt are calculated using formulas described in XIV.1. In case of donor transmitters, Atoll models the influence of repeaters on received signal levels (grey rows in the following table).

Name Value Unit Description In predictions* (point predictions and coverage studies)

termRpktotal

ShadowingbodytermRpkpath

GGMLLL

××××

Repeater-terminal total loss ShadowingM =1 in downlink extra-

cellular interference calculations RpkTL

In simulations

termRpktotal

ShadowingbodytermRpkpath

GGELLL

××××

None

Repeater-terminal total loss

In predictions* (point predictions and coverage studies)

termTxd

ShadowingbodytermTxdTxdpath

GGMLLLL

×××××

Repeater-terminal total loss ShadowingM =1 in downlink extra-

cellular interference calculations TxdTL

In simulations

termTxd

ShadowingbodytermTxdTxdpath

GGELLLL

×××××

None

Repeater-terminal total loss

)(icP Rpkc Rpk

T

Txdpilot

LicP )(

W Received chip power from repeater at terminal

)(icPTxdc Txd

T

Txdpilot

LicP )(

W Received chip power from donor transmitter at terminal

)(icP RpkTxdc

− )()( icPicP Rpkc

Txdc + None

Received chip power from donor transmitter with repeater at terminal

( ) )(icP DLRpkb Rpk

T

Txdtch

LicP )( W Received bit power from

repeater at terminal on carrier ic

( ) )(icP DLTxdb Txd

T

Txdtch

LicP )( W

Received bit power from donor transmitter at terminal on carrier ic

( ) )(icP DLRpkTxdb

− ( ) ( ) )()( icPicP DLRpkb

DLTxdb + W

Received bit power from donor transmitter with repeater at terminal on carrier ic

)(icPTxd ∑+++)(

)()()()(ictch

tchotherCCHSCHpilot icPicPicPicP W Transmitter total transmitted power on carrier ic

( ) )(icP DLRpktot Rpk

T

Txd

LicP )( W Total received power at terminal

from repeater on carrier ic

( ) )(icP DLTxdtot Txd

T

Txd

LicP )( W

Total received power at terminal from donor transmitter on carrier ic

( ) )(icP DLRpkTxdtot

− ( ) ( ) )()( icPicP DLRpktot

DLTxdtot + W

Total received power at terminal from donor transmitter with repeater on carrier ic

* In downlink prediction studies, signal level and intra-cellular interference are downgraded by the shadowing margin (MShadowing) while extra-cellular interference level is not. Therefore, MShadowing is set to 1 in downlink extra-cellular interference calculation formulas.

INDEX

I

Index


Index


INDEX

A ACTIVE SET

MANAGEMENT CDMA2000................. 228 IS95-CDMA ................ 228 UMTS ......................... 189

ADMINISTRATION FILES ATOLL.INI FILE ......................... 35 STUDIES.XML .......................... 35 USER CONFIGURATION FILE (.CFG)

.......................................... 35 ADMISSION CONTROL

UMTS ......................... 197, 238 AFP

COST FUNCTION .................... 175 ANTENNA

ANTENNA ATTENUATION ......... 129 ANTENNA PATTERN................ 129 ATOLL DEFINITION ................. 87 REMOTE ELECTRICAL DOWNTILT

........................................ 129 SECONDARY ANTENNAS ......... 142

ANTENNA ATTENUATION............. 129 MODELLING METHOD.............. 129

ANTENNA PATTERN MODELLING METHOD.............. 129

ATOLL.INI FILE................... 132, 139 ATOLL.INI FILE.XML...................... 37 AUTOMATIC NEIGHBOUR ALLOCATION

CDMA2000 NETWORKS........ 240 IS95-CDMA NETWORKS ....... 240 UMTS NETWORKS ................ 210

B BIL FILE...................................... 92 BIL FORMAT................................ 91 BSIC ALLOCATION

AUTOMATIC ALLOCATION DESCRIPTION..................... 180

BSIC FORMAT ............................ 78 BTS ........................................ 140

C CALCULATE .............................. 107 CALCULATION AREA................... 107 CALCULATION BIN...................... 106 CALCULATION RADIUS................ 107 CDMA2000 DOCUMENTS.......... 221 CELL

ATOLL DEFINITION ................. 88 CELL EDGE COVERAGE PROBABILITY

................................... 105, 132 CELL TYPE

ATOLL DEFINITION ................. 87 CLC FILE ......................... 100, 101 CLUTTER

CLUTTER CLASSES................... 82

CLUTTER HEIGHTS ...................82 COMMON COVERAGE STUDIES

COVERAGE DISPLAY149, 185, 223

PLOT DISPLAY........149, 185, 223 PLOT RESOLUTION .149, 185, 223 SERVICE AREA .......148, 184, 222

COMMON PREDICTION STUDIES CALCULATION CRITERION.......147,

183, 221 COVERAGE STUDIES148, 184,

222 PROFILE ANALYSIS .................147 RECEPTION ANALYSIS.............147

COMPUTATION ZONE ..................107 COMPUTATIONS IN BANDS.............31 CONFIGURATION FILES

NETHASP.INI FILE .....................19 NHSRV.INI FILE ........................19

COORDINATE SYSTEM ..................69 CS FILE ..................................71 DISPLAY SYSTEM .....................69 INTERNAL SYSTEM....................70 PROJECTION SYSTEM ...............69

CO-PLANNING CDMA-CDMA2000 NEIGHBOUR

ALLOCATION ......................246 CDMA-GSM/TDMA NEIGHBOUR

ALLOCATION ......................244 UMTS-GSM NEIGHBOUR

ALLOCATION ......................214 COST FUNCTION

AFP.....................................175 COST-HATA MODEL ...................116 COVERAGE BY C/I LEVEL STUDY..163 COVERAGE STUDIES

COMMON STUDIES..147, 183, 221 DOWNLINK SERVICE AREA

ANALYSIS...........................205 DOWNLINK TOTAL NOISE STUDY

........................................209 PILOT RECEPTION ANALYSIS ....204 UPLINK SERVICE AREA ANALYSIS

........................................207 CS FILE......................................71

D DATUM .......................................70 DBASE III FILE (.DBF) FORMAT ....97 DCT FILE ...................................99 DIFFRACTION ............................126

DEYGOUT..............................127 DEYGOUT WITH CORRECTION ..128 EPSTEIN-PETTERSON.............128 KNIFE-EDGE DIFFRACTION.......126 MILLINGTON ..........................129

DIGITAL TERRAIN MODEL .............81 DIGITAL TERRAIN MODEL .............81 DISK SPACE REQUIREMENTS ........29 DISPLAY SYSTEM .........................69

DISTANCE UNIT ........................... 77 DL SOFT HANDOVER GAIN .......... 203 DOCUMENT TEMPLATE ................. 43 DOWNLINK LOAD FACTOR

CDMA2000......................... 239 IS95-CDMA ........................ 239 UMTS ................................. 199

DOWNLINK SERVICE AREA ANALYSIS........................................... 205

DOWNLINK TOTAL NOISE STUDY .. 209 DTM ......................................... 81

E E/GPRS COVERAGE STUDY

BEST CODING SCHEMES DISPLAY........................................ 170

CALCULATION OPTIONS .......... 169 CODING SCHEMES DISPLAY..... 169

ELLIPSOID .................................. 70 EQUIPMENTS

BTS .................................... 140 FEEDER................................ 140 TMA.................................... 140

F FEEDER ................................... 140 FILE FRAGMENTATION.................. 29 FLOATING LICENSE

MANAGEMENT SYSTEM............. 19 FORCE CALCULATION................. 107 FORMATS

SUPPORTED GEOGRAPHIC FORMATS ............................ 83

FREE SPACE LOSS..................... 126

G GEOGRAPHIC COORDINATE SYSTEM

............................................. 70 GEOGRAPHIC DATA

SUPPORTED FORMATS ............. 83 GPRS/EGPRS COVERAGE STUDY

COVERAGE AREA DETERMINATION........................................ 168

GSM NETWORK AUTOMATIC NEIGHBOUR

ALLOCATION ...................... 161

H HASP DEVICE DRIVER................. 19 HDR FILE.................................... 91 HEIGHT UNIT............................... 77 HEXAGONAL DESIGN

ATOLL DEFINITION ................. 87 HISTOGRAMS.............................. 99

I INSTALLATION

Index


ATOLL .................................. 17 INTERFERED AREAS STUDY......... 163 INTERFERENCE HISTOGRAMS

FILES ..................................... 99 INTERFERENCE STUDIES

COLLISION PROBABILITY ......... 166 COVERAGE AREA................... 167 COVERAGE DISPLAY............... 167 COVERAGE STUDIES .............. 163 POINT ANALYSIS .................... 167 SERVICE AREA ...................... 164 SIGNAL TO NOISE RATIO ......... 164

INTERNAL COORDINATE SYSTEM.... 70 INTER-TECHNOLOGY NEIGHBOURS

AUTOMATIC ALLOCATION214, 244, 246

INTRA-TECHNOLOGY NEIGHBOURS AUTOMATIC ALLOCATION161, 210,

240 IS95-CDMA DOCUMENTS ......... 221

L LAND-USE .................................. 82 LOS FILE .................................... 99

M MATRIX VALIDITY....................... 108 MEMORY REQUIREMENTS ............ 29 MERIDIAN................................... 71 MNU FORMAT ............................ 96 MODEL_SIG ................................ 98 MONTE-CARLO SIMULATION

CDMA2000 ......................... 229 IS95-CDMA ........................ 229 UMTS ................................. 190

MULTI-LAYER MANAGEMENT ....... 110

N NEIGHBOURS

CDMA2000 ......................... 240 CDMA-CDMA2000 NEIGHBOUR

ALLOCATION ...................... 246 CDMA-GSM/TDMA NEIGHBOUR

ALLOCATION ...................... 244 GSM ................................... 161 IS95-CDMA ........................ 240 UMTS ................................. 210 UMTS-GSM NEIGHBOUR

ALLOCATION ...................... 214 NETHASP LICENCE MANAGER ..... 19 NETHASP MONITOR ................... 19 NETHASP KEY........................ 19

O OFFSET UNIT .............................. 77 OKUMURA-HATA MODEL ............ 116 ORACLE DATABASE ..................... 23 OVSF CODES

UMTS DOCUMENTS .............. 198

P PATH LOSS ............................... 105 PATH LOSS CALCULATION

CLUTTER CLASS .................... 109

CLUTTER HEIGHT ...................110 GROUND ALTITUDE

DETERMINATION .................109 MULTI-LAYER MANAGEMENT ....110 PROFILE RESOLUTION.............113 RADIAL .................................112 SYSTEMATIC..........................113

PATH LOSS MATRIX ....................106 PILOT RECPTION ANALYSIS .........204 PLANET FORMAT..........................93 PN OFFSET

ALLOCATION..........................242 POINT ANALYSIS

INTERFERENCE ......................167 PROFILE................................147 RECEPTION ...........147, 183, 221

POINT ANALYSIS BASED ON PATH LOSS MATRICES .....................105

POPULATION ...............................83 POWER CONTROL SIMULATION

CDMA2000 .........................232 IS95-CDMA.........................232 UMTS..................................193

PREDICTIONS AS ANALYSIS.........................105 COVERAGE STUDIES...............105 INTERFERENCE ANALYSIS........105 OVERVIEW ............................105 PROFILE ANALYSIS .................105 RECEPTION ANALYSIS.............105

PROFILE EXTRACTION..........................112 RADIAL EXTRACTION...............112 RESOLUTION .........................113 SYSTEMATIC EXTRACTION .......113

PROJECTED COORDINATE SYSTEM.70 PROJECTION ...............................70 PROJECTION SYSTEM...................69 PROPAGATION...........................105 PROPAGATION MODELS ..............114

R RADIAL .....................................112 RADIO EQUIPMENTS ...................140 RAM REQUIREMENTS..................30 RECEPTION UNITS........................77 RELIABILITY LEVEL .....................132 REMOTE ELECTRICAL DOWNTILT ..129

MODELLING METHOD ..............131 REPEATER

ATOLL DEFINITION ..................87 EIRP....................................252 GLOBAL AMPLIFICATION GAIN...251 PREDICTIONS ........................252

RESOLUTION .............................106

S SCANNED IMAGE..........................83 SCRAMBLING CODE ALLOCATION .212

ALLOCATION EXAMPLES ..........213 AUTOMATIC ALLOCATION.........212

SECONDARY ANTENNAS .............142 SHADOWING

DL MACRO-DIVERSITY GAIN.....136 SHADOWING ERROR ...............139 SHADOWING MARGIN ..............133

UL MACRO-DIVERSITY GAIN .... 134 SHADOWING

MODELLING IN PREDICTIONS ... 133 MODELLING IN SIMULATIONS ... 139

SHADOWING MARGIN ................. 105 DL EC/IO ..................... 137, 138 N SIGNALS..................... 134, 137 ONE PATH ............................. 133 UL SOFT HANDOFF ................ 136

SIMULATION CDMA2000......................... 229 IS95-CDMA ........................ 229 POWER CONTROL .................. 232 POWER CONTROL SIMULATION 193 UMTS ................................. 190 USER DISTRIBUTION GENERATION

................................ 190, 229 SITE

ATOLL DEFINITION ................. 87 CLUTTER CLASS .................... 110 CLUTTER HEIGHT................... 110 GROUND ALTITUDE ................ 109

STANDARD PROPAGATION MODEL117 STATION

ATOLL DEFINITION ................. 87 STUDIES.XML FILE ....................... 40 SUBCELL

ATOLL DEFINITION ................. 87 SYSTEMATIC............................. 113

T TBC TRANSMITTERS ................. 106 TEMPLATE.................................. 43 TEMPORARY FILE ........................ 30 TFW FILE .................................... 93 TIFF FORMAT .............................. 92 TMA ....................................... 140 TRAFFIC ANALYSIS

GSM ................................... 150 TRAFFIC DATA

ENVIRONMENT TRAFFIC MAP ..... 82 LIVE TRAFFIC MAP.................... 83 MAP PER TRANSMITTER AND PER

SERVICE ............................. 83 USER DENSITY TRAFFIC MAP ..... 83 USER PROFILE TRAFFIC MAP ..... 82

TRANSMISSION UNITS .................. 77 TRANSMITTER

ATOLL DEFINITION ................. 87 TRX

ATOLL DEFINITION ................. 87

U UIT 370-7MODEL ..................... 125 UIT 526-5 MODEL .................... 124 UMTS NETWORK...................... 183 UMTS-GSM NEIGHBOUR

ALLOCATION INTER-TRANSMITTER DISTANCE216

UPLINK SERVICE AREA ANALYSIS. 207 UPLINK SOFT HANDOVER GAIN .... 204 USER CONFIGURATION FILE (.CFG) 35 USER DENSITY .................. 189, 229

Index


V VECTOR DATA............................. 83 VIENNA 93 MODEL..................... 125

W WALSH CODES

CDMA2000 .........................238

IS95-CDMA ........................ 238 WLL MODEL............................. 123

7 rue des briquetiers – 31700 – Blagnac – France Tel: +33 (0)5 62 74 72 10 – Fax: +33 (0)5 62 74 72 11 http://www.forsk.com – email: [email protected]

TECHNICAL REFERENCE GUIDE ATOLL

RELEASE 2.3.0

AT230_TRG_E1 JUNE 2004

technical reference guide

Documents

b installation

installation procedure

c installation

d installation

atoll installation

table of contents forsk

floating license installation

license server requirements