A.F. COSME.

UMTS CAPACITY SIMULATION STUDY

2. Appendix: procedure for exporting a traffic map based on clutter data from ATOLL to Wines
This appendix describes the process to export an ATOLL traffic map based on clutter data to Wines format (ATOLL version used: 2.3.1) and it is based on [ATOLL] and [winesusermanual]. When ATOLL and Wines are installed on the same machine, Wines installs an add-in button in ATOLL so the selected project can be automatically opened in Wines just by pressing this button and therefore there is no need to follow the process described in this annex. This annex however, assumes that ATOLL and Wines are installed on different machines and therefore the project in ATOLL must be saved first in the specific formats described in this annex. The required steps to export the ATOLL project to Wines are as follows:

2.1 Project Export to a *.mdb file

Atoll allows to export a UMTS project to a Microsoft Access Database (*.mdb) file. This database contains Atoll UMTS radio data, including: Network layout (Node Bs, Antennas, cells) Environments definition User configuration

To export the currently open project in ATOLL to a mdb file, use the menu entry:

File -> Database -> Export.

16

2.2 Export of the Computation Zone and Focus Zone

The computation zone and the focus zone are not stored in the project database, so they need to be exported separately.

The computation zone (equivalent to Wines simulation area) can be exported using the menu entry:

Tools -> Computation Zone -> Save as . Enter a file name and save the zone in *.shp format.

The focus zone (equivalent to Wines Analysis Area) can be exported using the menu entry:

Tools -> Focus Zone -> Save as. Enter a file name and save the zone in *.shp format.

2.3 Export the path loss Data to Raster Data Files

Atoll uses a separate path loss map for each antenna. The antenna pattern is included in the path loss values. To filter a group of Node Bs in the ATOLL Project: Go to Data -> Sites -> Filter Inside a polygon. You will have two options: Computation zone Draw

The first option filters the node Bs and only the Node Bs inside the computation zone (simulation zone in wines) are taken into account.

The second option allows you to draw a polygon selecting only the nodes you want to work with.

17

Beneficiario COLFUTURO 2003

A.F. COSME. UMTS CAPACITY SIMULATION STUDY

To be able to export the path loss data, first you have to make sure that a prediction study already exists. If not, go to the prediction folder and generate a prediction of coverage by signal level. Create the prediction, then right click to execute the prediction and then you can export the path loss data.

In order to export the path loss data, right-click on the predictions item in the Data tab, select the Result Storage option. A dialog appears that allows for a selection of one or more transmitters. Use the select all and then Export items from the Actions button. In the calculation results export dialog, please specify a directory, select Path loss(dB) in the exported values box, choose binary format (*.bil) from the format box, and press OK

2.4 Export the Clutter map and Clutter Classes Definition

The clutter map must be saved as a raster file (e.g. BIL file).

To export the clutter map, use the menu entry Save as in the context menu of the Clutter folder of the Geo tab. It is recommended to save the clutter map as a BIL file because Atoll may crash in some cases when trying to save it as TIFF file.

The association of each clutter code with a clutter class is defined in the Clutter classes properties of the Atoll clutter map.

The clutter class definition (e.g. 0: default class, 1: water, 2:agriculture, 3:urban, etc) must be saved in addition to the clutter map. It can be stored in the same directory like the clutter map file to a *.mnu file. This *.mnu file must have the same name like the corresponding clutter map file, but with the extension *.mnu. It simply contains the clutter code and the associated clutter class name separated by a blank or tab.

For example, a *.mnu file could be as follows:

18

0 1 () 10

Default Class Water Coniferous Forest

2.5 Exporting background Maps with ATOLL

If you have a background map that you wish to use in an external application: a) Click the select area button b) define the area to be exported c) Select File -> Export Image command, and save it as a georeferenced image choosing TIFF format as the output format.

2.6 Exporting DEM (Digital Elevation Model) information

To export the DEM terrain map, select it in the GEO TAB, Digital Terrain Model folder, and select save as option, saving it as BIL file (ATOLL crashes some times when trying to generate a TIF file).

2.7 Traffic Map(s) and Environment Codes Definition

Traffic data can be represented in Atoll in different ways. For the importing process into WiNeS, two of these options are supported: Environment traffic maps, where each pixel is associated with an environment, which represents a certain service mix (each environment (e.g. Urban, Sub-urban, etc) has defined a list of clutter classes and weights). Cell traffic maps (based on transmitters and services), where the best server coverage area of each transmitter is associated with service-specific traffic values, which may additionally be subject to clutter-based weighting factors.

19

Beneficiario COLFUTURO 2003

A.F. COSME. UMTS CAPACITY SIMULATION STUDY

If Environment traffic maps are used in Atoll, each map must be saved as a raster file, e.g. in TIF format. This can be done using the menu entry Save as in the context menu of the respective Environment map in the UMTS Traffic folder of the Geo tab. The association of each environment code number (and color) with an Environment (as defined in the Atoll UMTS Parameters) is defined in the properties of the respective environment traffic map, e.g. as shown in Fig. 1.

Figure 2-1: Example Environment Codes definition in the Atoll Environment Traffic map properties

That Environment codes definition must be saved in addition to each environment traffic map. There are two ways to provide that information to the WiNeS ASM import process: either through a *.mnu file for each environment traffic map or if only one environment traffic map is used or several environment traffic maps with the same environment codes definition, through the ASM configuration file (atollimportmodule.ini). The preferred way is the export of *.mnu files one for each environment map, which must be stored in the same directory like the environment map files. Such a *.mnu file must have the same name like the corresponding environment map file, but with the extension *.mnu . It simply contains the Environment code and the associated Environment name separated by a blank or tab (refer also to [A-UM] section III.5.3). For the example in Figure 2-1 the *.mnu file contents must be:
0 no data 1 Urban 2 Rural

If there is only one environment traffic map defined in the Atoll project or if all defined environment traffic maps have the same Environment Codes definition, an alternative way is the definition in the [EnvironmentCodes]
20

section of the ASM configuration file (atollimportmodule.ini) in the following format: EnvironmentName = CodeNumber For the example in Fig. 1, the appropriate definition is as follows:
[EnvironmentCodes] no data = 0 Urban = 1 Rural = 2

For the most convenient usage of the ASM in connection with Atoll environment traffic maps it is recommended to create a *.mnu file for each environment traffic map.

If Cell traffic maps are used in Atoll the traffic data should be imported to WiNeS using the traffic matrix import function based on raster layers, which is described as creating a Traffic Matrix from a Surface Plot Layer in [W-UG].

Below a simple procedure is given to create an inhomogeneous traffic Map with ATOLL, based on the clutter weights defined per each environment: a) Go to Data Tab, Environments; Select for instance just one of them (e.g. Dense Urban). Assign weights to the clutter inside, something like this:

Clutter class Default Suburban: <6m Garden Suburban: <6m Suburban: <6m Dense Suburban: <9m Wooded Suburban: 6-9m Garden Suburban: 6-9m

Weight 0 10 10 10 10 10 10

% Indoor 0 30 30 30 30 30 30

21

Beneficiario COLFUTURO 2003

A.F. COSME. UMTS CAPACITY SIMULATION STUDY

Suburban: 6-9m Dense Urban: 9-12m Open Urban: 9-12m Urban: 12-18m Open Urban: 12-18m Urban: 18-27m Open Urban: 18-27m Urban: 18-27m Dense City: 27-40m Open City: 27-40m City: >40m

10 15 15 15 15 15 15 15 20 20 20

30 50 50 50 50 50 50 50 60 60 60

Table 2-1: Example of assigned clutter class weights The combined weights together with the area size of each clutter class determine the final number of users per each pixel. This number of users is given by the formula: Nk = Nclass x Wk Sk / ( Wj * Sj) Where Nk = Number of users in the k clutter Nclass = Number of users in an environment class (defined in the environments Tab). Wk = k clutter weight at a fixed surface (value assigned for each Environment) Sk = k clutter surface.

For more information, consult ATOLL user guide section VIII.5.2.e.v, page 287. b) In the GEO Tab, select UMTS Traffic, right click and then select new map. Afterwards select map based on environments (raster) option. c) Now you have a box open. Replace the entry no data of the list with the environment that you defined (in this case, Dense Urban). d) Select the draw polygon tool. Use this tool to draw the polygon where this traffic map is going to be created (usually we can take the same simulation area). When finish press double click.
22

e) In UMTS Traffic folder, select the option export cumulated traffic. f) To check that it is working, we can export it first as BMP image and check if the image shows the different traffic densities in the map. g) After the check, to be able to work with it in Wines, we have to export cumulated traffic but now we are going to save it as BIL file. Finally, in Wines select the appropriate service profile, right click over it, Select the option import traffic from Raster Image and select the BIL file created in step g.

23

Beneficiario COLFUTURO 2003

pgina anterior
A.F. COSME. UMTS CAPACITY SIMULATION STUDY

Volver a empezar

References: [ATOLL] ATOLL: Technical Reference Guide, Version 2.1.3, Forsk, 2004. [WINESUSERMANUAL] J. Deiner, J. Hbner, D. Hunold, D. Stachorra, J. Voigt. User Guide for WiNeS Control Center User version 3.3. Radioplan GmbH, Dresden, Germany, 2005.

24