universal model user guide - infovistawebhelp.infovista.com/planet/62/content/pdfs/universal...page...

Planet Server 6.2

Universal Model User Guide

Copyright © 2017

InfoVista S.A.S. All rights reserved.

Notice

This document contains confidential and proprietary information of InfoVista S.A.S.and may not be copied, transmitted, stored in a retrieval system, or reproduced inany format or media, in whole or in part, without the prior written consent ofInfoVista S.A.S. Information contained in this document supersedes that found inany previous manuals, guides, specifications data sheets, or other information thatmay have been provided or made available to the user. This document is providedfor informational purposes only, and InfoVista S.A.S. does not warrant orguarantee the accuracy, adequacy, quality, validity, completeness or suitability forany purpose the information contained in this document. INFOVISTA S.A.S. mayupdate, improve, and enhance this document and the products to which it relates atany time without prior notice to the user. INFOVISTA S.A.S. MAKES NOWARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION,THOSE OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITHRESPECT TO THIS DOCUMENT OR THE INFORMATION CONTAINED HEREIN.

Trademark Acknowledgement

Planet is a registered trademark owned by InfoVista S.A.S. MapInfo Professionaland the Spectrum Suite are registered trademarks of Pitney Bowes Software Inc.Map data copyright OpenStreetMap contributors, CC BY-SA. This document maycontain other trademarks, trade names, or service marks of other organizations,each of which is the property of its respective owner.

Last updated Thursday, August 31, 2017 for Planet Server 6.2.2

Universal Model User Guide Universal Model v460

© Copyright 2004-2017 Orange, All rights reserved This documentation is protected by copyright and contains proprietary and confidential information. No part of the contents of this documentation may be disclosed, used or reproduced in any form, or by any means, without the prior written consent of Orange Labs. Although Orange Labs has collated this documentation to reflect the features and capabilities supported in the software products, the company makes no warranty or representation, either expressed or implied, about this documentation, its quality or fitness for particular customer purpose. You are solely responsible for the proper use of Universal Model software and the application of the results obtained. An electronic version of this document exists. This User Guide prepared by: Orange Labs & Infovista Last updated March, 2017


Contents Installing the Universal Model with Planet ......................................................... 7

Installation .......................................................................................................................... 8 License Management ......................................................................................................... 9

Using a Standalone License ........................................................................................................ 10 Using a Floating License ............................................................................................................. 10 Borrowing a Floating License .................................................................................................... 13 Troubleshooting installation and licensing issues .................................................................. 16

Distributed Predictions................................................................................................... 17

The Universal propagation Model ....................................................................... 19 Overview ........................................................................................................................... 20 The Universal Model ....................................................................................................... 21 Variations of the Universal Model ............................................................................... 22 The Profile Component .................................................................................................. 23

Management of Raster Geographic Data ................................................................................. 24 Profile Extraction of Raster Geographic Data .......................................................................... 25 Deygout's Methods of Calculating Diffraction ........................................................................ 26

Morphology....................................................................................................................... 28 Improving Propagation Accuracy Based on the Morphology .............................................. 28

Facets .................................................................................................................................. 29 The Principle behind the Facets Component ........................................................................... 29 The Modeling and Function of the Facets Component .......................................................... 29

Graphs ................................................................................................................................ 31 The Principle behind the Graphs Component ......................................................................... 31 The Modeling and Function of the Graphs Component ........................................................ 32

Trains .................................................................................................................................. 33 Multipath ........................................................................................................................... 34

Geographical Data ....................................................................................................................... 34 Electromagnetic Wave Model .................................................................................................... 35 Multipath Variables ..................................................................................................................... 35

Configuring the Universal Model for Planet ..................................................... 37 To edit the Universal Model .......................................................................................... 38 First Universal Model Window: General tab ............................................................. 39

General parameters ..................................................................................................................... 39 Information ................................................................................................................................... 39

Second Universal Model Window: Geodata tab ........................................................ 40 Geographical data ........................................................................................................................ 40 Specific data .................................................................................................................................. 42

Third Universal Model Window: Time optimization Tab ...................................... 46 Prediction resolution ................................................................................................................... 46 Radial ............................................................................................................................................. 46 Inner/outer area resolution........................................................................................................ 47 Optimized calculation area ........................................................................................................ 48

Fourth Universal Model Window: Radio optimization Tab ................................... 50 Radio optimization ...................................................................................................................... 50 Building calculations ................................................................................................................... 52 Train options ................................................................................................................................ 54 Typology effects ........................................................................................................................... 54 Depenetration ............................................................................................................................... 54

Fifth Universal Model Window: Advanced Tab ........................................................ 56 Key features .................................................................................................................................. 56

Sixth Universal Model Window: Multipath Tab ....................................................... 58 Advanced multipath component .............................................................................................. 58


Multipath variables ..................................................................................................................... 59 Multipath prediction settings..................................................................................................... 59

Universal Model Analysis / Tuning ..................................................................... 62 To analyze the Universal Model ................................................................................... 63 To tune the Universal Model ......................................................................................... 65


CHAPTER 1

Installing the Universal Model with Planet

From the UM460.yyyy_MP600.zip file you can install the 460 version of the Universal Model (build yyyy) for use with Planet (version 6.x).

In this Section: Installing the Universal Model with Planet ......................................................... 7

Installation .......................................................................................................................... 8 License Management ......................................................................................................... 9

Using a Standalone License ........................................................................................................ 10 Using a Floating License ............................................................................................................. 10 Borrowing a Floating License .................................................................................................... 13 Troubleshooting installation and licensing issues .................................................................. 16

Distributed Predictions................................................................................................... 17


Installation

The Universal Model is installed with Planet; you may, however, need to update the version used (e.g., in the case of a patch). In order to update the Universal Model with Planet, copy the .dll/.mdl files to the following Planet installation folders: <InstallDir>\Planet 6.x\Help\

• UM.chm <InstallDir>\Planet 6.x\lserver\Tool\FlexLM\

• LICPIFT.exe

• lmgrd.exe

• lmstat.exe

• lmtools.exe <InstallDir>\Planet 6.x\RPE\Mapping\

• UMPlugin.DpmMapping.dll <InstallDir>\Planet 6.x\RPE\Plugins\

• UMPlugin.dll <InstallDir>\Planet 6.x\RPE\UI\

• UMEditor.dll <InstallDir>\Planet 6.x\RPE\UM\

• UMWrapperManaged64.dll

• Universal_Model_masked64.mdl

• Universal_Model_unmasked64.mdl <InstallDir>\Planet 6.x\RPE\UM\3DComponent\

• QtCore_ 4.dll

• libgmp-10.dll

• Universal_Model_3D.exe


License Management

The Universal Model is installed with Planet but relies on different licensing software (i.e., the FLEXlm License Server Manager). The Universal Model uses a software-based security system, which requires that you have a valid license (version 4) on your workstation. This requirement prevents unauthorized use of the software. Two types of licenses are available: Standalone and Floating.

Standalone licenses

Using a standalone license, you can use the Universal Model on a single specific workstation (as identified by that workstation’s MAC address). A standalone license is the best option if you plan to use the Universal Model on only one workstation for independent projects with no multi-user collaboration. A separate license server is not required and no network connection is needed. When you purchase a Universal Model standalone license, you are provided with a license file (.lic). You must ensure that this file has a specific name (“Universal_Model.lic”) and is saved in the following folder:

• <InstallDir>\ Planet 6.x\Universal Model\

Note: A standalone license is not compatible whether you are logged on to a server or whether you use a remote connection.

Floating licenses

Using a floating license, a predefined number of users can use the Universal Model. Each time a user works with the Universal Model on a workstation, a license is automatically requested from a license server that has been configured by an administrator. If there are licenses available, the user is assigned a license and can use the Universal Model. If, however, there are no licenses available, the user will be unable to use Universal Model. Unlike a standalone license, a floating license is not tied to a specific workstation. However, a network connection is required between the workstation of the user requesting the Universal Model license and the license server. You must ensure that the license file has a specific name (“Universal_Model.lic”) and is saved in the following folder:

• <InstallDir>\Planet 6.x\Universal Model\

Note: The license is only assigned during propagation model use; it is freed as soon as the calculations have ended.


Borrowing a floating license

If you want to use the Universal Model when you are disconnected from the network, you can borrow (i.e., check out) a floating license for a limited amount of time. This can be useful, for example, if you are travelling, or are in the field, and you do not have access to the Universal Model license server. Once you have successfully borrowed a license, you can use Universal Model until the borrowing period expires.

Note: If you are using the Universal Model in a multi-thread mode, the number of threads that can be used depends on the type of license you have. If you are using a computer with multiple-cores (i.e., multi-processors), you can run four simultaneous predictions with a borrowed, standalone license or with one license of a floating license.

Using a Standalone License

The workflow for using the Universal Model with a standalone license is:

Step 1: If required, install the Universal Model on the workstation Step 2: Configure the standalone license

Configuring Standalone Licenses

• If you are using a standalone license, after you install the Universal Model on your workstation, ensure that your license is properly configured by verifying that the .lic file that you were sent after purchasing your copy of the Universal Model is in the following folder:

▪ <InstallDir>\Planet 6.x\Universal Model\ If necessary, copy the .lic file to this folder

• Ensure that the .lic file is named “Universal_Model.lic” If necessary, rename the .lic file

Using a Floating License

Note: Before configuring the license server, you may want to move the License Manager folder, which contains the license server files (i.e., LICPIFT.exe, lmgrd.exe and lmtools.exe), out of the default program folder (<InstallDir>\Planet 6.x \lserver\Tool\FlexLM) and place it in a new folder. If you move the License Manager folder out of the Planet program folder, you can avoid reconfiguring the license server if you have to reinstall the Universal Model at some point in the future. If you do not move the License Manager folder, when you reinstall the Universal Model, new versions of the license server files will replace the existing files, and your configuration settings will not be retained


The workflow for using Universal Model with a floating license is:

Step 1: Configure the license server. Step 2: If required Install the Universal Model on a workstation with access to the

network on which the license server is hosted. Step 3: If the Universal Model is to be used in a situation where continuous access to

the network on which the license server is hosted will not be available (e.g., when travelling), borrow a license for Universal Model from the license server.

Configuring License Servers If you are using a floating license configuration of the Universal Model, an administrator must initially configure the license server on a host server (on which the Universal Model has been installed). The license server can then handle Universal Model license requests from users.

• You must use the tools in the dedicated folder (by default, <InstallDir>\Planet6.x\lserver\Tool\FlexLM)

• Double-click lmtools.exe. The LMTools dialog box opens.

Figure 1: LMTools – The Service/License File tab

• On the Service/License File tab, select Configuration Using Services.

• Enable the LMTOOLS ignores license file path environment variables

check box.

• Click the Config Services tab, and enter a name for the service in the Service

Name box (e.g., “Universal Model”).


Figure 2: LMTools - Config Services tab

• Click the Browse button next to the Path to the lmgrd.exe File box and navigate to the “lmgrd.exe” file.

• Click the Browse button next to the Path to the License File box and navigate to the floating license file

• Click the Browse button next to the Debug Log File box, navigate to the location where you want to save a debug log file, enter a name for the file in the File Name box, and then click Open

The debug log file provides useful information to the administrator about why a user cannot obtain a license (e.g., no license, license expired, licensed number of users already reached).

• Select the Use Services check box.

• Select the Start Server at Power Up check box (this option automatically starts the license server when the host server is restarted).

• Click the Save Service button.

• When you are prompted to save the service settings, click Yes.

• Click the Start/Stop/Reread tab.

• From the FLEXnet License Services Installed on this Computer list, choose the service that you created for the Universal Model license server in step 4, and click the Start Server button. You can check if the server is correctly started by reading the Debug Log File

and/or if the service’s status is ‘Started’ by consulting the Services window

• Select File -> Exit

• On the workstation, copy the .lic file in the following folder: ▪ <InstallDir>\Planet 6.x\Universal Model\

• Ensure that the .lic file is named “Universal_Model.lic” If necessary, rename the file.

Note: A license server can handle users’ requests for more than one application provided by Orange Labs. Therefore, if users have been issued .lic files that contain licenses for multiple applications created by Orange Labs, an administrator should configure only a single license server to issue floating licenses for all applications.


Borrowing a Floating License

To borrow a floating license, you must connect to the Universal Model license server and borrow a license from the license server. After you have obtained a floating license for the Universal Model, you can disconnect from the network and use Universal Model. You can use the Universal Model until the end of the defined borrowing period. You can also return a borrowed Universal Model floating license before the end of the defined borrowing period. When you return a floating license, the license becomes available for another user.

To borrow a floating license

• Close Planet.

• In case of RPE service, on the workstation, right-click My Computer and choose Manage to open the Computer Management dialog box, in the tree view, expand the Services and Applications node and choose Services, right-click the Planet RPE service and choose Stop.

• In Windows Explorer, navigate to the folder containing the Universal Model license server tools (i.e., LICPIFT.exe, lmgrd.exe, lmtools.exe, and lmstat.exe), right-click the lmtools.exe and choose Run as Administrator or, if you are using an OS other than Vista or Windows 7, double-click lmtools .exe

• The LMTools dialog box opens when you can click the Borrowing tab.

Figure 3: LMTools - Borrowing tab

• In the Vendor Name box, type LICPIFT.

• In the Return Date box, enter a date by which the license must be returned (the return date must be in a dd-mmm-yyyy format (e.g., 01-dec-2017). The borrowing period cannot exceed 30 days or the expiration date for the Universal Model license that was purchased)

• If you want to specify at what time the license must be returned on the return date, enter a time in the Return Time box (the time must be in an hh:mm


format (e.g., 14:00 defines a license expiration of 2 p.m.). If no return time is defined, the license will expire at midnight on the return date)

• Click Set Borrow Expiration

• In case of RPE service, restart the Planet 6.x RPE service using a user account (not the Local System account)

Figure 4: Planet RPE service

You must run Universal Model one time in Planet to complete borrowing the license Note: you have to not run a coverage calculation but another type of calculation (point to point, analysis, etc.).

• In the LMTools dialog box, click Don't Borrow Anymore Today in LMTools.

To return a borrowed floating license

To return a floating license before its expiration date, you must define an environment variable that is set to the path of the license file on the license server. You can then return the floating license to the license server.

• On the workstation, close LMTools.

• On the workstation that currently holds the borrowed license, select Start

Settings Control Panel System.

• In the System Properties dialog box, click the Advanced tab and click Environment Variables. The Environment Variables dialog box opens.


Figure 5: Environment Variables

• In the User Variables for the given user name section, click New

• In the New User Variable dialog box, enter “LM_LICENSE_FILE” in the Variable Name box

• In the Variable Value box, enter the path of the Universal Model.lic file and click OK

Figure 6: New User Variable

• In the Environment Variables dialog box, click OK

• In the System Properties dialog box, click OK

• In Windows Explorer, navigate to the folder containing the Universal Model license server tools (i.e., LICPIFT.exe, lmgrd.exe, lmtools.exe, and lmstat.exe), right-click the lmtools.exe and choose Run as Administrator or, if you are using an OS other than Vista or Windows 7, double-click lmtools .exe

The LMTools dialog box opens.

• Click the Borrowing tab.

• In the Feature Name box, enter “Universal_Model”.

• Click Return Borrowed Licenses Early. If the Return Borrowed Licenses Early fails, you must also type the display name in the Display Name (optional) box before clicking Return Borrowed Licenses Early


To retrieve the Display name

To check the Display Name, you must use the lmstat utility (available in the folder containing the Universal Model license server tools) to obtain information about the license server.

• Open a Command Prompt and type <lmstat.exe path>\lmstat.exe -c <Universal_Model.lic path> -f Universal_Model.

Figure 7: Display name

This command lists all licenses in use on the server. Lines that list the borrowed license contain the key word “linger”. The Display Name is the third piece of information contained in the line.

Troubleshooting installation and licensing issues If you encounter issues related to the installation and licensing of the Universal Model, step through the processes listed below before contacting Customer Care:

• If you have more than one license file on your workstation, search for .lic files and delete obsolete license files (i.e., files where the date has expired).

• Verify that the license server is started and can be contacted from your workstation.

• Ensure that ports between 27000 and 27009 are available for communication with the license server.

• Verify that the MAC address listed in the License (.lic) file corresponds to the MAC address of your workstation.

• On the machine that hosts the license server, in the firewall exceptions, add and enable the two executables files, LICPIFT.exe and lmgrd.exe, used by the license server.


Distributed Predictions

The Universal Model offers the possibility of generating simulations using several threads regardless of the type of license (i.e., standalone or floating):

• With a standalone license, the model is limited to four simultaneous threads

• With a floating license, the model is limited to four simultaneous threads per token For example, if you generate a set of predictions with Planet (6 threads), the model requires two licenses.

You can configure the Mentum Radio Propagation Engine in order to define the maximum number of threads used for the multi-threaded prediction calculation. This is done with the configKey MaxNumThreads in the RPEService.exe.config file. Contact Customer Care for more information. Similarly, it is possible to define how many threads the multi-threaded prediction calculation uses for the Universal Model. The configKey, which is called MaxNumThreadsUM in the RpeService.exe.config and RpeApp.exe.config file, can be set to the following values:

• 0 sets the number of threads to be used to the number of cores / processors in the system (e.g., on a two-core machine, it will use two calculation threads at most)

• Positive integer numbers define the number of threads to be used (it is not recommended that you exceed the number of cores/processors in the system).

Note: If MaxNumThreadsUM does not exist or if it is greater than MaxNumThreads, this variable is automatically set to the MaxNumThreads value. It is possible to define the maximal authorized memory for a Universal Model 64bits process. The configKey, which is called MaxProcess64BitsSizeGoUM in the RpeAgent64.exe.config file, can be set to the following values:

• Number in the interval [0;20] defines maximal authorized memory (in Go) Before the start the calculation, Universal Model estimates the memory to be assigned according to the geographical data, the calculation radius and the calculation resolution. If the estimation is up to the limit fixed via this parameter, Universal Model degrades the calculation resolution (in case of degradation of the resolution, the model returns a message to indicate the resolutions used for the calculation). Note: If MaxProcess64BitsSizeGoUM does not exist or if it is out of the authorized interval, this variable is automatically set to the default value (20Go).

Universal Model User Reference Guide Universal Model v460

Universal Model Reference Guide Universal Model v460

CHAPTER 2

The Universal propagation Model

In this Section: The Universal propagation Model ....................................................................... 19

Overview ........................................................................................................................... 20 The Universal Model ....................................................................................................... 21 Variations of the Universal Model ............................................................................... 22 The Profile Component .................................................................................................. 23

Management of Raster Geographic Data ................................................................................. 24 Profile Extraction of Raster Geographic Data .......................................................................... 25 Deygout's Methods of Calculating Diffraction ........................................................................ 26

Morphology....................................................................................................................... 28 Improving Propagation Accuracy Based on the Morphology .............................................. 28

Facets .................................................................................................................................. 29 The Principle behind the Facets Component ........................................................................... 29 The Modeling and Function of the Facets Component .......................................................... 29

Graphs ................................................................................................................................ 31 The Principle behind the Graphs Component ......................................................................... 31 The Modeling and Function of the Graphs Component ........................................................ 32

Trains .................................................................................................................................. 33 Multipath ........................................................................................................................... 34

Geographical Data ....................................................................................................................... 34 Electromagnetic Wave Model .................................................................................................... 35 Multipath Variables ..................................................................................................................... 35


Overview

In the current context of the growth of mobile telecommunication networks, operators face innumerable technical and economic problems during the planning, deployment, and optimisation phases of mobile radio networks. To address these issues, operators use dedicated engineering tools that offer solutions to problems such as the calculation of coverage, determining hand-over zones, interference, frequency allocation, antenna optimisation, traffic localization, and so on. One of the most useful tools for mobile radio engineers is field prediction models. Also called wave propagation models, they are incorporated in engineering tools and allow mobile radio network creators to determine the coverage zones of emitting stations and, in turn, infer the interference zones. Providing key information to numerous tools for further analysis and exploiting the predicted fields, they occupy a privileged place in cellular engineering. Strongly dependent on geographic data that allows the extraction of a vertical cross-section of the terrain (called a “profile”), a propagation model is a mathematical simulation of a physical phenomenon between two points. Performing preliminary processing of the cross-section of the terrain in order to check the calculation hypotheses, the propagation model combines theory with profile information before statistically adjusting the results using field measurements. Programmable according to different requirements, a propagation model is developed with the objective of always respecting significant constraints in domains such as: speed, precision, strength, and versatility.


The Universal Model

Capping several years of research in domains such as: propagation, modelling, optimisation and algorithms, the Universal propagation Model is able to automatically adapt to all engineering environments (i.e., micro, mini, small, and macro cells), to all environments (i.e., dense urban, urban, suburban, mountainous, maritime, and open), and to all systems (i.e., DVB-H, GSM, GPRS, EDGE, UMTS, CDMA, TD_SCDMA, WiFi, WiMAX, LTE) in a frequency range starting from 150MHz to 5GHz.

Relying on very realistic modelling of the channel, it achieves the synergy of the three physical elementary contributions: diffraction in the vertical plane, guided propagation in the horizontal plane, and reflection on the relief.

Figure 8: Reflection + diffraction + guided propagation = the Universal Model trilogy


Variations of the Universal Model

The Universal Model is available in a masked version and in an unmasked version:

• Masked Universal Model—accounts for the total path loss, which includes the antenna losses.

• Unmasked Universal Model—accounts for the unmasked pathloss, the inclination angle, and the azimuth angle. The unmasked version does not take the antenna losses into consideration. The inclination angle is the angle between the horizontal plane and the transmitter axis-first diffraction edge or between the horizontal plane and the transmitter-receiver axis if there is no diffraction edge.


The Profile Component

The Principle behind the Profile Component of the Universal Model is based on two

parts:

• The first one is dedicated to environments for which the polygons’ geographical data is not available throughout the whole calculation zone or for occasions where you do not want to work with them.

• The second one combines the polygons’ geographic data (when available) and the raster geographic data representing the surface with raster geographic data of the relief.

The calculation of the loss of propagation is almost entirely determined by the relief analysis in the vertical plane passing through the transmitter and the receiver. This hypothesis enables the transformation of each relief obstacle to a 2D theoretically thin and infinite horizontal plane and reduces it to a problem of wave diffraction calculation on a succession of thin ridges that can be treated with Fresnel formulas. The first operation consists of elaborating the profile from the polygons’ geographical data or raster geographic data representing the surface (clutter and/or clutter heights) and the raster geographic data of the relief (height).

Figure 9: Profile example (without polygons)

Figure 10: Profile example (with polygons)

The solution chosen to construct the diffraction profile with the polygons’ geographic data is to add the profile of the height of the polygons to the altitude profile taken from the height as follows:


• For a building contour, the diffraction profile consists of ridges of equal heights. All the height ridges supporting the buildings, modified so that the building’s rooftop stays flat, are increased to the height of the building. The profile is then completed with the two ridges framing the building.

• For a forest contour, the diffraction profile is formed from the height ridges under the forest contour to which the height of the contour is added. The profile is then completed with the two frame ridges of the contour where the height portion is determined by interpolation.

Figure 11: Profile construction for polygons

Once the profile is obtained so that the diffraction loss is not over-estimated, it is best to delete certain diffraction edges; therefore, every diffraction edge less than one hundred meters away from a positive or negative diffraction edge is deleted. This means that a succession of diffraction edges that are so close to each other that they in fact represent only one ridge is not taken into consideration.

Deygout’s method is chosen to calculate the diffraction loss. The model also calculates different variables related to the profile. The loss of the profile component results in a linear combination of these variables for which the coefficients are determined by adjusting the smallest squares with the calibration tool.

Management of Raster Geographic Data

There are three types of raster geographical data:

• Heights (Digital terrain model): Description of altitudes above ground of the points at the centre of the pixel. This is a single point and not a calculated average on the various altitudes encountered on the pixel.

• Clutter (Digital surface model): Statistical description of the surface or principal theme on the pixel.

• Clutter heights (Digital elevation model): Descriptions of height above the surface of the points at the centre of the pixel.

The profile component adapts itself to all types of raster data. The management of raster geographic data is based on the construction of a “height” representation and a “surface” representation. A data representation is a zone of raster data that results from the fusion of various raster files (or from the data of one file if only one file is available). It is constructed across the following stages:


• Taking an inventory of the files where the intersection with the calculation area is not zero.

• Creating a result area and positioning of each pixel to “indefinite value”.

• Reading every file by order of resolution and fusion in the result area. During the fusion stage, a pixel from the resulting area is only affected if its previous value was “indefinite value”.

The “height” representation is a 2D matrix that contains the description of the relief while the “surface” representation is a 2D matrix that contains the surface height (for clutter data, each type is associated with a height by you in Planet). The resolution of the “height” representation can be inferior, equal, or superior to that of the “clutter” representation.

Profile Extraction of Raster Geographic Data

Taking into consideration the fact that propagation is principally done through diffraction on relief, the model constructs, in a vertical transmitter-receiver plane, a profile called the “knife edge”, which is comprised of ridges determined from the raster geographic data. To do this, the model extracts the profile ridges that are at the intersection points of the vertical planes (or the horizontal planes if α >=45) passing through the centre of the pixels with the transmitter-receiver segment. The height of each ridge is equal to the height of the bin containing the point of intersection.

Note: The transition between polygons and raster databases is optimised. As soon as the model detects that there is no polygon data in an area, it automatically switches to the available raster data

Figure 12: Extraction of a profile

Pixels

Vertical and horizontal planes

at the centre of the bins

X

Z

Y

X

Profile extract

R

E


The profile is extracted by adding a value estimated by interpolating the distance starting from the surface profile to the value of each point of the height profile. At each point of the height profile, the point that provides the best frame in distance in the surface profile is chosen, and the height of the surface ridge is estimated with a linear interpolation starting from the heights and the distances from the transmitter of the “framed” ridges.

Deygout's Methods of Calculating Diffraction

The phenomenon of diffraction is one of the most important factors contributing to the propagation of electro-magnetic waves. Deygout’s method has been chosen for the profile component. It uses three fundamental concepts to arrive at the calculation of diffraction losses:

a) The first Fresnel zone: It is generally understood that diffraction phenomena due to all obstacles situated outside this zone are negligible. The first Fresnel zone is the volume limited by the ellipsoid with starting points E and R, such

as EM + MR – ER ≤ /2 (with M points belonging to the Fresnel ellipsoid).

b) The Huyghens principle: The fundamental idea behind Deygout’s method is that in order to go from transmitter to receiver, the wave must, by diffraction, avoid a limited number of obstacles (thin ridges) taking each one into consideration after the other in order of importance with regards to the method of the Fresnel calculation; that is to say, in relation to the Fresnel zones defined as a result.

Figure 13: Profile example of obstacles in thin ridges

c) The superposition principle: As with other methods, the problem of diffraction on multiple ridges is treated as a succession of diffractions on a single ridge, for which the Fresnel calculation is applicable. This approach is both empirical and intuitive.

E

R


P0P1 P1P2 P2 P2 P2

1 756423

Ordre de l’obtension des arétes engagées positives

ER

Figure 14: Order of obtaining the positive edges committed

The algorithm calculates recursively by sets of three (thus with a maximum of 15 diffraction edges), between the transmitter and the receiver, the interference coefficient of each ridge in the Fresnel ellipsis. It conserves the ridges that have the largest interference coefficients, as well as the number of engaged ridges, and diffraction losses are calculated starting from these ridges. A positive edge corresponds to an obstacle which interferes with the Fresnel ellipsoid and crosses the main axis and a negative edge corresponds to an obstacle located in the Fresnel Ellipsoid, which does not block the main axis. The loss represented by the profile component, created by the accumulation of the different diffraction losses, is then corrected by adding the weighting of the calculated variables along the profile with coefficients that are determined by adjusting the least squares method by the calibration tool.


Morphology

Improving Propagation Accuracy Based on the Morphology

Morphological data is a representation of the ground specific to the Universal Model. Each geographic area is saved as a classified grid, in which each point is dependent on both the elevation and the clutter. The data point value is calculated in a continuous way. For example, a point representing “DENSE_URBAN_RELIEF” morphology cannot have a point representing “FOREST_FLAT” morphology as a neighboring point. It is strongly recommended that you use data representing the morphology of the area with the Universal Model in order to ensure accurate results, especially for the tuning mechanism. This data must be generated from both the clutter and elevation data. This can be done using the Universal Model user interface. There are ten types of morphologies:

• FOREST_FLAT

• FOREST_RELIEF

• OPEN_FLAT

• OPEN_RELIEF

• SUBURBAN_FLAT

• SUBURBAN_RELIEF

• URBAN_FLAT

• URBAN_RELIEF

• DENSE_URBAN_FLAT

• DENSE_URBAN_RELIEF


Facets

The Principle behind the Facets Component

The Universal Model uses facets to evaluate the contribution of multipath while the electro-magnetic connection takes place across an irregular terrain. It allows you to predict the signal strength received by the mobile taking into account the reflections produced on mountain slopes. This improves the precision in relation to classic components that only take into consideration the propagation phenomena in the vertical cross-section of the terrain between the transmitter and the receiver. The inclusion of reflection is very complex and depends on numerous factors. It is suitable then to make simplified hypotheses so that the component is usable by the operator of radio mobile networks.

• The first simplification is the inclusion of paths that encompass only the reflection on a mountain. It can be assumed that this hypothesis introduces a slight error because the received paths by multiple reflections on the topography are strongly mitigated and not significant at the receiver.

• The second simplification is that only the zones on mountain slopes that are in “height” visibility of both the transmitter and receiver are considered. Note that there is visibility when the different obstacles do not protrude from the axis of the Fresnel ellipsoid.

• The third hypothesis is that the determination of the reflected paths is only performed if the direct transmitter-receiver path is obstructed by the terrain.

• The fourth hypothesis is to limit the extent of the search area for possible reflectors by fixing a maximum delay for the consideration of the echoes. The measurement campaigns of impulse responses have allowed validation to a value of 50μs. Because of the calculation time, the value is, by default, fixed to 25μs, which corresponds to a maximum distance C.∆tmax = 300 x25 = 7500 m (where C equals the speed of light)

• Finally, the fifth hypothesis is the understanding that there is a reflection, or diffusion, (as opposed to a discrete reflection on plane surface) given the large irregularities of mountainous slopes in relation to wavelengths. The received signal is uniformly diffused in the half-space above the slope of the mountain, and the diffused power is inconsistent. Nevertheless, by analogy with the radar equation, it is assumed that all the contributions of the diffused power could be added together by the receiver. This hypothesis has been verified on the terrain and explains why large quantities of energy nonetheless reaches the mobile even though there are rarely discrete reflections in the direction of the mobile

The Modeling and Function of the Facets Component

Activating the facets component is only effective if the propagation context is hilly enough. The search of reflection zones is performed using the ‘Use facets’ parameter. The files generated with the aid of an algorithm based on the Delaunay triangulation method are defined via this parameter. These files contain information about the modeling of the relief (i.e., reflection facets, visibility in relation to the reflection facets, etc.)


Once you have obtained the reflection zones, the facets component calculates the loss of the reflected paths to determine the total strength received by the receiver.

Figure 15: Example of facets


Graphs

The Principle behind the Graphs Component

The graphs component is only effective for transmitters for which the polygons’ geographic data is available over the entire calculation zone. In a micro cellular context, the emitting and receiving antennas are positioned below the average level of the rooftops. In this case, the signal strength received by diffraction above the rooftops is significantly inferior to that of the signal strength received by propagation in the street and diffraction on the edges. The propagation hypothesis above the rooftops is therefore no longer sufficient, especially when the number of edges between the transmitter and receiver is not great. .

Figure 16: Profile example for the Graphs component

When the antenna is well below the rooftops, the electro-magnetic propagation occurs mainly along the streets, which act as street canyons. There is a “guiding” phenomenon of the electro-magnetic waves by the street that implies that major propagation phenomena are situated in the horizontal plane and no longer the vertical plane, as is the case with the profile models. In this way, there is a benefit from the canalization effect that increases propagation. To model this guiding phenomenon of the electro-magnetic waves by the streets, the model uses a graph of street axes. A graph is created by arcs representing the axes of the streets capable of acting as a wave guide.


Figure 17: Example of graph (Paris)

The Modeling and Function of the Graphs Component

This component is responsible for calculating all the contributions coming from the receiver by the different paths illustrated by the graph. It calculates the loss for each path as a result of distance, of the diffraction on the vertical ridges formed by street corners, and of multiple reflections along the street axes. All the elementary contributions are then added to constitute the total loss of the graphs component representing the electro-magnetic energy that propagates along the streets. The total number of paths analyzed is limited to 100, but the model only takes into account a maximum of 40 paths (the number of paths going from the transmitter to the receiver is not defined. Only those paths for which the loss is less than a defined threshold, that is to say sufficiently significant, are selected).

Figure 18: Examples of paths for the graphs component

The profile loss is calculated and is added to the graphs component loss to form the total loss of the Universal Model.

Receiver

Transmitter

Paths considered by the

Graphs component

Best path considered for the

Graphs component


Trains

The train component provides the corrections of additional losses while the receiver is in a train. When this option is used, the losses calculated for receivers on a railway track or very close to one are stronger than if no trains were found. These additional losses are highly dependent on the characteristics of the railway tracks (i.e., excavation, tunnel, embankment, viaduct, or soundproof). The losses are also different if the train is single-decker or double-decker. The Use railway tracks option must be selected for the train component to be taken into consideration.


Multipath The multipath component aims at providing insights on the spatiotemporal nature of electromagnetic wave propagation in dense urban environments, by the mean of three statistical variables: the delay-spread, the angle-spread and the Rice factor. To do so, it relies on a deterministic identification of the main propagation paths between the transmitter and the receivers. This is achieved by simulating the propagation of a Dirac impulse signal and its subsequent interactions with terrain and surface features.

Figure 19: Wave propagation simulated by the multipath component

Geographical Data

The multipath component uses polygons and heights data to model a 3D geographical environment. It cannot be activated if either is missing. The vectors are extruded according to their class and are assigned specific material properties (no reflection nor diffraction on forests, no transmission through water or ground).


Electromagnetic Wave Model

An electromagnetic wave is modelled through its electrical compound. It is a three-dimensional vector which initial value is given by the transmitter’s antenna configuration. The orientation in space is set by the polarization whereas the magnitude is set by the transmitted power. Polarization, magnitude, phase and delay are then tracked as the wave propagates. Any interaction with a geographical feature triggers one or more of the following phenomena: reflection, transmission and diffraction. Each one of them alters polarization, magnitude and delay depending on the material properties of the geographical feature and in a coherent way with the other UM components. In the end, all the identified propagation paths are combined to produce three multipath variables that further describe how the energy is received at each receiver.

Multipath Variables

From a multipath point of view, path loss is an estimation of the overall power that is received by a receiver. While it is the core metric behind any modern mobile network design, it does not account for the propagation paths that are exploited by multi-antenna technologies. Hence the three additional metrics simulated by the multipath component. Together with path loss, these variables can help spotting the areas where MIMO is suitable, select the best fit between diversity and multiplexing and adjust the antenna designs accordingly.

centroid

Figure 20: Extrusion of buildings

centroid

Figure 21: Extrusion of bridges

Figure 22: Extrusion of forests

Figure 23: Extrusion of water surfaces


Rice Factor: the Rice factor is a value that indicates how close a receiver is from line of sight conditions. A high value (usually >> -5dB) means that most of the energy is provided by a single propagation path which is almost always the case in line of sight conditions, but can still happen in other situations. A low value area (<< -5dB) usually is a good candidate to deploy MIMO optimisations. Delay-Spread: the delay-spread measures the time span during which most of the power arrives at a receiver. Values lower than the guard interval usually mean you can expect a significant improvement of data rates with either diversity MIMO or multiplexing MIMO. In such areas, choose diversity MIMO to enhance low signal-to-noise ratios and multiplexing MIMO otherwise.

Angle-Spread: the angle-spread measures the dispersion of the paths as they leave the transmitter to a receiver. This value is especially useful to fine tune your antenna designs. The lower the value, the more constrained the orientation is, but the more sectors you can set up. The angle spread is calculated at the receiver’s side and is purely on the horizontal plane. It is the weighted circular standard deviation of the directions of arrival. The weights are the power (in Watts) that comes from each direction. There is no threshold since the weightings will make low energy directions negligible anyway. The circular standard deviation accounts for the circular nature of angles : namely, that the average of 350° and 10° in [0,360[ is 0° and not 180° ; that the averages (emphasized plural) of 0°, 120° and 240° are indeed 0°, 120° and 240°. Note that cases where several average values exist yield by definition to a unique standard deviation anyway.


CHAPTER 3

Configuring the Universal Model for Planet

Propagation models are organized in the Propagation window. The icons of propagation models that have been assigned to a sector are displayed in color. The icons of propagation models that have not been assigned to a sector, but are located in the Model folder of the project, appear dimmed. You can refine how the Universal Model behaves by modifying the propagation model settings in the Universal Model dialog box. Once you have refined the model, you can apply the propagation model to an individual site or sector. Propagation models saved in the <ProjectDir>\Model folder will be available each time you create a project. Models saved in the project folder are project specific.

In this Section: Configuring the Universal Model for Planet ..................................................... 37

To edit the Universal Model .......................................................................................... 38 First Universal Model Window: General tab ............................................................. 39

General parameters ..................................................................................................................... 39 Information ................................................................................................................................... 39

Second Universal Model Window: Geodata tab ........................................................ 40 Geographical data ........................................................................................................................ 40 Specific data .................................................................................................................................. 42

Third Universal Model Window: Time optimization Tab ...................................... 46 Prediction resolution ................................................................................................................... 46 Radial ............................................................................................................................................. 46 Inner/outer area resolution........................................................................................................ 47 Optimized calculation area ........................................................................................................ 48

Fourth Universal Model Window: Radio optimization Tab ................................... 50 Radio optimization ...................................................................................................................... 50 Building calculations ................................................................................................................... 52 Train options ................................................................................................................................ 54 Typology effects ........................................................................................................................... 54 Depenetration ............................................................................................................................... 54

Fifth Universal Model Window: Advanced Tab ........................................................ 56 Key features .................................................................................................................................. 56

Sixth Universal Model Window: Multipath Tab ....................................................... 58 Advanced multipath component .............................................................................................. 58 Multipath variables ..................................................................................................................... 59 Multipath prediction settings..................................................................................................... 59


To edit the Universal Model

• In the Propagation window, right-click Propagation Models, and choose

New • In the Propagation Model Type dialog box, from the Propagation Model list,

choose one of the following variations of the Universal model and click OK: ▪ Universal Model (masked) - accounts for the total path loss which

includes the antenna losses

Figure 24: Create a new Masked Universal Model

▪ Universal Model (unmasked) - accounts for the unmasked path loss. The unmasked version does not take the antenna losses into consideration

Figure 25: Create a new Unasked Universal Model

• The Universal Model dialog box opens


First Universal Model Window: General tab

Figure 26: Universal Model - General tab

In this window, you can check the Universal Model parameters which are:

General parameters In this section, you select the general parameters:

• The Model Name parameter allows to specify a name for the model

• The Frequency parameter indicates the frequency of the model

• The Receiver height parameter indicates the height at the receiver

Information In this section, you have information about the Universal Model (for example, the version number to use when submitting a support request)


Second Universal Model Window: Geodata tab

Figure 27: Universal Model - Geodata tab

In this window, you can check the Universal Model parameters which are:

Geographical data

In order for the Universal Model to account for geodata, geodata files must be added to the appropriate folder in the Propagation window. Note: All geodata files must be in the same coordinate system as the project height file. In this section, you select the geographical data you want to use. Note: in each geographical data window, you have the possibility to Select all/Deselect all file(s) by right clicking on the columns headers. Raster data section:

• Use raster accuracy: When you use the parameter, the model exploits the accuracy of the geographical data with the goal of generating a more exact output. Otherwise, the model uses less detailed calculations in order to decrease processing time.

• Use heights: This type of data is compulsory for the model. To add additional heights files other than the project height file, click the Settings button and enable the check box associated with the height files you want to add. The Use Height file check box is always enabled but the Universal Model is able to account for several height files. You can also view


details of the files including cell size, x-min/x-max, and y-min/y-max> when you are finished, click OK

• Use clutter heights: The clutter height file is used when the resolution is better than the resolution of the clutter data. The Universal Model is able to take into account several clutter height files and processes the most accurate clutter file first. Click the Settings button to enable the check box associated with the clutter height files you want to use. You can also view details of the files including cell size, x-min/x-max, and y-min/y-max> when you are finished, click OK

• Use clutter: If you select this type of data, the Universal Model Clutter

Settings window appears:

Figure 28: Universal Model - Clutter Settings window

Click the settings button to enable the check box associated with the clutter files you want to use. In this window, the list of clutter classes appears. You must determine whether the clutter is a Building type (this information is used for the Buildings calculation option), a Water type (this information is used for the maritime optimization), a Forest type (this information is used for the forest optimization) or an Undefined type (meaning there is no data). You also must set the average height of each class and the buildings calculation losses for Building class(es).

You have the possibility to hide/show all the clutter classes of each file by right clicking a file and choose Hide clutter classes or Show clutter classes).

You can also view details of the files including cell size, x-min/x-max, and y-min/y-max> when you are finished, click OK

Note: Universal Model allows you to manage the priority of raster data with same resolution (right click a file and choose Up or Down)


Vector data section:

• Use polygons: Universal Model is able to take into account several polygon files. Click the Settings button to enable the check box associated with the polygon files you want to use. Valid polygon (.tab) files must be saved within the Geodata\Polygons folder in the Propagation window and consist of three columns with the following headings:

▪ Polygon_ID - valid values in this column include a unique identifier consisting of characters only. This column is required so that the file can be imported into the Propagation window.

▪ Polygon_Type - valid values in this column include “Buildings”, “Forest”, “Water” or “Bridge”

▪ AMSL or AGL - valid values in this column include the height of the building above the ground (if the column title is “AGL”) or height above sea level (if the column title is “AMSL”)

Universal Model is able to take into account the thickness of the bridges in order to improve the diffraction modelling close to the bridges. In order to do so, valid polygon (.tab) files must contain one additional column with the following heading:

▪ Bridge_Thickness - valid values in this column include the thickness of the bridge (in meters). During the diffraction calculation process:

▪ If the value is comprised in ]0;polygon’s height[, the thickness is considered from the top of the bridge

▪ If the value is set to the polygon’s height, the bridge is considered as a blind wall (like buildings)

▪ If there is no value or if the value is set to 0 or if the value is not comprised in [0;polygon’s height], the bridge is not considered as an obstacle

Note: in case of decimal value, the model only takes into account the first decimal.

• Use railway tracks: Universal Model is able to take into account several railway track files. Click the Settings button to enable the check box associated with the railway track files you want to use. Valid railway (.tab) files must be saved within the Geodata\Custom folder in the Propagation window and contain vector representations (a simple line with only 2 points) for railways. The file must consist of one column with the following heading:

▪ Description - valid values for the railways type are “train”, “train_excavation”, “train_embankment” “train_viaduct”, “train_tunnel”, and “train_soundproof”

Specific data

The Use facets parameter allows you to access to the facets geographic data type. If the parameter is not assigned, the model will calculate without taking this into consideration. To generate this data, click the Settings button.


The facets generator creates the facets for the project. This data is used to calculate the refection for mountainous areas. The facets generator automatically detects the mountainous areas and decides if it has to generate the facets in each case. Note: Depending to the size of the project area, the calculation time can be significant.

If the project area is not hilly enough, the model will consider that the reflection component is not significant and the facets generator will display the message: “No mountainous environment detected. Facets will not be generated”.

Figure 29: Universal Model - Facets generator window

In the Generation section, click the Start button. Progress is shown in the progress bar and, once the process is complete, several facets files as well as a facets index file are saved. If you want to stop the process without closing the dialog box, click Suspend. If you want to stop the process and close the dialog box, click Abort. Once the files have been generated, click Close.

The Use graphs parameter allows you to access to the graphs geographic data type. If the parameter is not assigned, the model will perform calculations without taking this into consideration. To generate this data, click the Settings button. The graphs generator creates the graphs on the project. This data is useful to help the model to compute 'guided' propagation for micro cells. The graphs generator automatically detects dense urban areas and decides if it has to generate the graphs in each case. Note: Depending to the size of the project area, the calculation time can be significant.

If the project area is not microcellular, the model will consider that the guided propagation is not significant and the graphs generator will display the message: “No microcell environment detected. Graphs will not be generated”.

Figure 30: Universal Model - Graphs generator window


In the Generation section, click the Start button. Progress is shown in the progress bar and, once the process is complete, several graphs files as well as a graphs index file are saved. If you want to stop the process without closing the dialog box, click Suspend. If you want to stop the process and close the dialog box, click Abort. Once the files have been generated, click Close.

The Use morphologies parameter allows you to access the morphology geographic data type. If the parameter is not assigned, the model uses the default morphology. To generate this data, click the Settings button. The morphologies generator creates the morphologies on the intersection of the height and the clutter data. The morphologies are used by the model to determine in which geographical context the prediction is performed, and depending on context, special optimizations are applied. You have to map each clutter class to one of 5 basic clutter classes

Figure 31: Universal Model - Morphologies generator window

Themes used by Universal Model:

• No data: This must be used for each theme for which there is no information (it means area where no data is available)

• Dense Urban: This must be used for a high density of construction (collective and/or individual). It can be areas with dense development where built-up features do not appear distinct from each other (heart of city for example), areas with group of skyscrapers or high towers, etc.

• Urban: This must be used for a mean density of construction (collective and/or individual). It can be areas with mean development where built-up


features appear distinct from each other, area with group of mean towers, areas including buildings with large footprints, dense industrial areas, etc.

• Suburban: This must be used for a low density of construction (collective and/or individual). It can be areas with small constructions such as residential areas, villages, mean industrial areas, etc.

• Forest: This must be used for each area related to vegetation (high density of trees, dense wood/vegetation area, etc.), no distinction is made between deciduous and coniferous

• Open: This must be used for areas with little or no construction/vegetation such as parks, agricultural fields, open spaces, sea/water areas, etc.

Note: The map each clutter class to one of the 5 basic clutter classes depends on the project/country, the notions of dense urban, urban and suburban is not really important, the objective is to characterize various propagation environments in order to apply dedicated optimisation coefficients. The morphologies generator does not apply a basic correspondence between project’s clutter classes and model’s default clutter classes, it is a complex process which implements several mathematical algorithms.

In the Generation section, click the Start button. Progress is shown in the progress bar and, once the process is complete, a morphology file as well as a morphology index file are saved. If you want to stop the process without closing the dialog box, click Suspend. If you want to stop the process and close the dialog box, click Abort. Once the files have been generated, click Close.


Third Universal Model Window: Time optimization

Tab

On this tab, you can choose the calculation parameters (each of which has a default value so that you can run the model without defining any values).

Figure 32: Universal Model - Time Optimization tab

You can define the following Universal Model parameters:

Prediction resolution

The Use resolution of project elevation file parameter enables you to generate predictions with the same resolution as the heights file. The User-defined resolution parameter enables you to generate prediction with the resolution you define. The Circular calculation areas parameter allows you to indicate whether the model has to consider the calculation areas as circular areas.

Radial

The Use radial mode parameter allows you to activate the radial calculation. During a coverage calculation, this mode allows you to reuse a profile extracted on the perimeter of the calculation area, approximating for the distance. The radial mode is


approximately three times as efficient. In fact, in a square calculation zone of n pixels long, in normal mode n² profiles are extracted, while in radial mode only 4n-4 profiles are extracted. Radial mode works as follows:

- The Universal Model associates a profile at several points (depending on the resolution) of the calculation area perimeter, while determining the closest profile by the orthogonal projection.

- The Universal Model extracts the first profile of the perimeter and uses it for each calculation point along the profile, and so on.

The Use prediction resolution parameter allows you to generate predictions with the same resolution as the prediction. The User-defined radial resolution parameter allows you to generate a prediction with the resolution you define.

Note: If the user-defined radial resolution is higher than the prediction resolution, the prediction resolution is used.

In the diagram below, the resolution corresponds to the prediction resolution.

Figure 33: Universal Model - Radial mode

Inner/outer area resolution

The Use second resolution parameter lets you activate or deactivate the inner/outer area resolution. The Resolution multiplier factor parameter allows you to set the second prediction resolution compared with the initial one (factor between 2 and 10).

dA

dB

Profile A

Profile B

Transmitter Extraction point of the profiles Calculation point Profiles of the perimeter of the calculation area Orthogonal projections

In this case: dA < dB so profile A is kept


The Distance threshold parameter enables you to specify the transmitter-receiver distance (in meters, 10,000 m by default) starting from which, during a calculation, the model changes from a grid using the transmitter’s resolution to a larger one. The model takes into account two different resolutions, the transmitter resolution (R1) and the resolution assigned by you (R2). The model checks whether the ”transmitter/receiver” distance is greater than distance threshold (the red circle in the diagram below). If so, it calculates the point under consideration and transfers the results to neighboring pixels. Otherwise, the model calculates each calculation point. For example, in the diagram below, Resolution multiplier factor is set to 4.

Figure 34: Universal Model - Second resolution mode

Optimized calculation area

The Use optimized calculation area parameter allows you to determine whether the model reduces the calculation zone behind the antenna. The reduction is done orthogonally at the azimuth. When you use this parameter, you have to define the recoil distance (in meters) starting from which the model no longer calculates behind the transmitter.

If you select the Automatic backwards distance option, the model automatically adjusts the value of the recoil distance, starting from which the model no longer calculates behind the transmitter. Limited to 30% of the distance along the azimuth, it is used by the model as described in the following equation:

Recoil distance =

)ln(

_ )_log( 10

20

20 MINADIRAZIMDIST

e Where: - Recoil distance: the maximum distance calculated behind the station at 30% of the distance along the azimuth.

Transmitter Effective calculation points Calculation points


- DIST_AZIM: the distance between the transmitter and the edge of the influence area according to the direction of the azimuth. - ADIR_MIN: the smallest directional loss of the antenna behind the station.

Figure 35: Universal Model - Optimized calculation area

If you select User-defined backwards distance, the model uses the defined recoil distance starting from which it no longer calculates behind the transmitter. Note: This distance is limited to 30% of the distance along the azimuth.

Azimuth DIST_AZIM

Recoil distance

Calculated pixels

Non calculated pixels Boundary of the zone to be calculated


Fourth Universal Model Window: Radio optimization

Tab

Figure 36: Universal Model - Radio optimization tab

You can define the following Universal Model radio parameters:

Radio optimization

The Loss correction parameter indicates the value of the correction (in dB, 0 by default) to add to the total loss of the model. For example, Loss correction = 3dB means 3dB more loss. Note: This parameter does not affect the tuning.

The Additional extraction distance parameter indicates the additional extraction distance (in meters, 0 by default, the value must be contained in the interval [0;300]) of polygons beyond the receiver (to the right of the receiver on the cross-section of terrain).

The Graphs extraction radius parameter indicates the distance (in meters, 1500 by default, the value must be contained in the interval [0;2000]) beyond which the graphs component is no longer used.


The Free space in line of sight parameter indicates the maximal distance (in meters, 0 by default) to apply free space attenuation for pixels that are in Line Of Sight of the transmitter without taking into account any model calibration.

The Calculate on water parameter allows you to indicate whether the model should calculate over water.

The Horizontal propagation parameter allows you to activate or deactivate horizontal diffraction. If activated, when the models finds an obstacle between the transmitter and the receiver, if the height of this obstacle is greater than the smallest apparent width of it, then the height is replaced by the apparent width on the profile. The purpose of this is to avoid taking into account diffraction on the top of the obstacle in the calculations carried out when the electro-magnetic field is mainly diffracted on the side of the obstacle.

Figure 37: Universal Model - Horizontal propagation

In the above example, if the height is greater than the ”right” apparent width (to the right of the Transmitter-Receiver axis when looking at the receiver), then this height is replaced by the “right” apparent width.

The Mobile on top of bridge parameter allows you to indicate whether the model should consider the receiver over bridges.

The Calculate indoor only parameter defines whether the model calculates only in buildings (other calculation points will not be calculated).

Note: This parameter is automatically enabled in case of multiple receiver heights for receiver heights different from the one set in the model. The Used weighted tuning coefficients parameter allows you to use a weighting between tuning coefficients used for polygons and for raster data; this weighting will take into account the distance crossed over polygons and raster data. In the example below, both tuning coefficients are taken into account after weighting them according to the distance over each area type.

‘Right’ apparent width

‘Left’ apparent width

E R


Figure 38: Universal Model - Used weighted tuning coefficients

Note: this parameter does not affect the tuning.

The Use clutter types parameter allows you, in case of forest/maritime optimization or buildings calculation, to indicate whether the model retrieves clutter information in case of clutter heights data. In others words, Clutter types, which have to be configured in the “Clutter Settings” window, allow the model to determine if clutter height data is located in building/forest/water area. Any clutter heights located within pixels of such clutter classes will be considered as building/forest/water. Note: For polygons, the model uses the parameters “Buildings”, “Forest” or “Water” located in the column with headings “Polygon_Type”.

The Downtilted antenna optimization parameter allows you to activate the down tilted antenna optimization. If activated, in case of antenna with a small aperture and/or important down tilt, in Line Of Sight, the model applies a dedicated optimization in order to consider the reflexion over the ground between the transmitter and the receiver.

Building calculations

The No calculation in buildings parameter allows you to inactivate the penetration feature. In this case, the model will not calculate predictions within buildings. If the Model-defined penetration parameter is activated, the model calculates only the outdoor pixels on a first pass, and then it calculates indoor pixels that border on at least one pixel calculated during the previous pass. Among the bordering pixels, the model selects the one with the smallest loss and adds a correction to get the loss on the new pixels. It carries on until there are no more uncalculated pixels left. The correction is automatically calculated by the model according to the frequency, the penetration angle and the distance with regard to the outside of the building.

Figure 39: Universal Model - Buildings calculation

Building First pass Second pass Third pass

Outdoor calculation pixels

Indoor calculation pixels (third)

pass)

Indoor calculation pixels (second)

pass)

Only raster data available Polygons


The User-defined penetration parameter also allows you to activate the outdoor to indoor process, but for penetration, you manually set the correction.

• The OutsideInside parameter allows you to set the value in dB (the default is 10 dB) of the assigned additional loss to the receivers situated inside a building, when at least one of the eight receivers nearby is outside.

• The InsideInside parameter allows you to set the value in dB/m (the default is 0.66 dB) of the assigned additional loss to receivers inside a building, when the eight receivers nearby are inside a building.

Note: The penetration calculation can increase calculation time significantly for very high resolutions. The Universal Model is able to take into account a specific loss correction for each polygon. In order to do so, valid polygon (.tab) files must contain two additional columns with the following headings:

• Out_In_xxxxx_yyyyy_Mhz (example: Out_In_800_1200_Mhz) - Valid values include the assigned additional loss (in dB) to the receivers inside a building for frequency range [xxxxx Mhz ; yyyyy Mhz] while at least one of the eight surrounding pixels is found on the street. The value must be from 0 to 30.

• In_In_xxxxx_yyyyy_Mhz (example: In_In_2200_2600_Mhz) - Valid values include the assigned additional loss (in dB/m) to the receivers inside a building for frequency range [xxxxx Mhz ; yyyyy Mhz] while all of the eight surrounding pixels are found in the building. The value must be from 0 to 5.

If the antenna’s frequency is compatible with several fields, the model considers only

the first one. If there is no compatible field (no compatible frequency range), the

model searches the fields Outside_Inside and/or Inside_Inside which are compatible with all frequencies.

The Universal Model is able to take into account a specific loss correction for each clutter class via the Universal Model Clutter settings window, the clutter class as to be assigned to the Building type and the two dedicated columns have to be set:

• Outside inside (dB) - Valid values include the assigned additional loss (in dB) to the receivers inside a building, while at least one of the eight receivers nearby is outside.

• Inside inside (dB/m) - Valid values include the assigned additional loss (in dB/m) to the receivers inside a building, while the eight receivers nearby are inside a building.

Note: The buildings calculation coverage option can return incoherent results in case of raster data with low resolution.

Note: When a loss correction defined in the polygons files or in the clutter settings is

not valid (no compatible frequency range and/or no valid value), the model automatically uses the selected penetration option (meaning Model-defined

penetration or User-defined penetration).

The Mobile on top of buildings parameter allows you to indicate whether the model should consider the height of the receiver from the top of the building (or from the ground if there is no building). Note: There is no penetration available with this parameter.


Train options The Calculate only along the railway tracks parameter defines whether the model calculates only along the railway tracks (other calculation points will not be calculated). The Train type parameter indicates the type of train on the railways: single-decker or double-decker.

Typology effects

The Forest optimization parameter allows you to activate the forest optimization. If activated, vegetation is not considered as an obstacle but as a transmission phenomenon which will be associated with specifics loss properties. Note: Using this parameter slightly increases calculation time.

The Maritime optimization parameter allows you to activate maritime optimization:

• Standard: if activated, the historical statistical optimization will be applied in the case of propagation over water

• Advanced: if activated, an advanced statistical optimization will be applied in the case of propagation over water

Note: Using this parameter slightly increases calculation time.

Depenetration The depenetration feature works as follows: for an antenna located in a building, the model applies a specific treatment to take into account the propagation inside this building. The model identifies several virtual transmitters and considers the one which generates the lowest losses.

Figure 40: Universal Model - Depenetration feature


In addition to the propagation phenomena between the virtual transmitter and the receiver, the model estimates the losses from the real transmitter (RT) to the virtual transmitter (VT) using the following formula:

Loss (from RT to VT) = 3

*30;3*)(

)(

OutsideInside

InsideInside

losshMaxlossd

Where: - d: the distance between the real transmitter and the virtual transmitter - h: the difference of height between the real transmitter and the virtual transmitter - loss(Inside->Outside): corresponds to the InsideOutside parameter, which allows you to set the value in dB (the default is 10 dB) of the assigned additional loss to the transmitter inside a building while the signal passes through the building. - loss(Inside->Inside): corresponds to the InsideInside parameter, which allows you to set the value in dB/m (the default is 0.66 dB/m) of the assigned additional loss to the transmitter inside a building, while the signal is propagated inside the building.

Crossing a concrete floor (and then the storey) is taken into account in the path loss formula. The model considers that the average height of storey is 3m:

- If h<= 3, the model does not take into account loss for propagation between two stories

- If h>3, the model applies a loss related to the propagation through the ceiling.

Note: The ‘transmitter-receiver’ angle is considered as the incidence angle.

The Universal Model is able to take into account a specific loss correction for each polygon. In order to do so, valid polygon (.tab) files must contain two additional columns with the following headings:

• Dep_In_Out_xxxxx_yyyyy_Mhz (example: Dep_In_Out_800_1200_Mhz) - Valid values include the assigned additional loss (in dB) to the transmitter inside a building for frequency range [xxxxx Mhz ; yyyyy Mhz] while the signal passes through the building. The value must be from 0 to 100.

• Dep_In_In_xxxxx_yyyyy_Mhz (example: Dep_In_In_2200_2600_Mhz) - Valid values include the assigned additional loss (in dB/m) to the transmitter inside a building for frequency range [xxxxx Mhz ; yyyyy Mhz] while the signal is propagated inside the building (the value must be from 0 to 5).

If the antenna’s frequency is compatible with several fields, the model considers only

the first one. If there is no compatible field (no compatible frequency range), the

model searches the fields Dep_Inside_Outside and/or Dep_Inside_Inside which are compatible with all frequencies.

Note: When a loss correction defined in the files is not valid (no compatible

frequency range and/or no valid value), the model automatically uses the values defined in the user interface.


Fifth Universal Model Window: Advanced Tab

Figure 41: Universal Model - Advanced tab

Note: When using this feature, it is recommended to limit to 1 the number of thread used for the multi-threaded prediction calculation. You can set the following Universal Model advanced parameters:

Key features The Antenna correction parameter allows you to determine whether the model verifies the coordinates of the antenna. Antenna correction works as follows: for an antenna located inside a building, the model calculates the new DX, DY or the height so that the antenna is on the exterior of the building (DX and DY correspond to the displacement in the direction of the azimuth according to the axis of the Xs and the Ys in the horizontal plane in relation to the transmitter).


Figure 42: Universal Model - Antenna correction

After that, you can move the antenna to the facade by applying DX and DY to the transmitter coordinates or on the rooftop (by modifying the transmitter’s height). A text file (which can be opened in a spreadsheet), called “AntennaCorrectionFile[(m)/(ft)].txt”, summing up the different correction parameters and the obtained results, is generated in the Model\Universal Model folder within the project folder (the correction will appear only for poorly located transmitters). It contains the following columns:

• DATE: The date the file was generated

• SITE_NAME: The transmitter name

• SITE_X: The transmitter coordinate (abscissa)

• SITE _Y: The transmitter coordinate (ordinate)

• NEW_STATION_DX (m/ft): Correction to apply if you want to move the transmitter to the facade (abscissa).

• NEW_STATION_DY (m/ft): Correction to apply if you want to move the transmitter to the facade (ordinate).

• NEW_STATION_HEIGHT (m/ft): Correction to apply if you want to move the transmitter to the roof.

• ANTENNA_CORRECTION_FACADE_DISTANCE (m/ft): Value of the parameter Minimal distance between antenna and facade.

• ANTENNA_CORRECTION_ROOF_DISTANCE (m/ft): Value of the parameter Minimal distance between antenna and roof.

• STATION_HEIGHT (m/ft): Transmitter’s height.

• ANTENNA_AZIMUTH: Transmitter’s azimuth.

Note: The use of this option implies that the result files of the model are not assigned; it means that there is no calculation done; the model only creates the “AntennaCorrectionFile[(m)/(ft)].txt” file.

• The Minimum distance between antenna and facade parameter allows you to set the minimum distance (in meters) between the antenna and the building facade that supports it.

• The Minimum distance between antenna and roof parameter allows you to set the minimum distance (in meters) between the height of the antenna and the roof of the building that supports it.

Roof distance

Facade

distance

Case of a possible difference in facade Case of an impossible difference in facade

Roof distance Facade distance

Position of the station

Correction of the station


Sixth Universal Model Window: Multipath Tab

Figure 43: Universal Model - Multipath tab

Note: The multipath module requires a masking algorithm that can handle multiple paths per receiver, i.e. masking each path individually and aggregate them into the multipath variables. Hence it is not available in unmasked computation modes. It demands a lot of processing power and random access memory. It is advised not to launch simulations in parallel to avoid splitting the computer resources amongst different model instances.

Advanced multipath component The multipath tab allows you to compute three additional map types - one per multipath variable - complementary to the main loss map. They provide statistical spatiotemporal descriptions of the multipath components of propagation: the delay-spread, the angle-spread and the Rice factor. They are especially suitable for dense urban environments or any other multipath-rich environment in general. Each map covers a square area centered on the location of the transmitter and is exported into <bin folder>\UM_Multipath as an independent file. The Use multipath component parameter allows you to activate the multipath component. Note: You cannot enable the multipath component without any of the multipath variables selected.


Multipath variables The box allows you to enable the desired variables to simulate: delay-spread, angle-spread and/or Rice factor. Unchecking all of them is equivalent to disabling the multipath component.

Multipath prediction settings

The Distance parameter (in meters, between 10 and 500) allows you to set the width of the simulation area, the resulting area is a square centered on the location of the transmitter.

Note: This parameter is the one that has most impact on the amount of random access memory needed to perform the simulation.

The Resolution parameter allows you to set the resolution used to sample the simulation area.

The Output file format parameter allows you to define the file format used to save the result of the simulations. The available formats are gridded data (.grd), comma separated values (.csv) and bitmap (.bmp). The generated files are saved under <bin folder>\UM_Multipath and are named after the following convention:

#1_#2_#3_#4_#5_#6_#7_#8_#9.#10,

where the #n are place holders for the following information.

1. Site name (eg. Site_1),

2. Sector name (eg. Sector_1),

3. The transmitter’s height in meters with two decimal places (eg. 25.00),

4. The, maybe negative, antenna tilt value in degrees with one decimal place (eg. -2.0),

5. The transmitter’s azimuth in degrees with one decimal place (eg. 5.0),

6. The distance set for the simulation in meters (eg. 200),

7. The resolution set for the simulation in meters (eg. 10),

8. The receiver’s height in meters with two decimal places (eg. 1.50),

9. The name of the exported multipath variable (angle_spread, delay_spread or rice_factor),

10. The extension of the selected file format (grd, csv or bmp).

As with any other propagation result, the generated files may overwrite previous versions if the simulation is run twice with the same settings. The available formats are raster-like. The specifications of the written values depend on the multipath variable being exported:

• Delay-spread, the value is given in microseconds


• Angle-spread, the value is given in 100 x degrees

• Rice factor, the value is given in 100 x decibels Note: There may be “no data” pixels when no significant multipath contributions were found during the simulation. The way “no data” values are written depends on the file format.

Gridded data (.grd) The “no data” value is:

• Rice Factor: 0dbx100 100*decibels

• Delay Spread: -1 microseconds

• Angle Spread: -1 100*degrees

Comma-separated value (.csv) This file format is provided as a mean to externally process the results of the simulations. The format is self-documented as in the following example: Version, 1.0 Bounding box (xmin ymin xmax ymax), 66120, 1212121, 66220, 1225333 Height (m), 1.5 Resolution (m), 5 Variable name, delay-spread X, Y, Value (ns) 66125, 1212126, 0.15 66130, 1212131, na …

Bitmap (.bmp) Exports an image file with the same size and resolution as the simulation area. The color legend blends from red (smallest value) to green (greatest value) in the tone-light-saturation color-space. The legend is automatically adjusted so as to provide no saturation at either end of the color range.

low high

No data is exported as a white pixel.


CHAPTER 4

Universal Model Analysis / Tuning

By generating analyses, you can validate the model using further measurements. Using tuning, you can calibrate the model (the aim of the Universal Model Automatic Tuning is to reduce the effects of imperfections and to enable the Universal Model to be as close to real propagation measurements as possible).

In This Section

Universal Model Analysis / Tuning ..................................................................... 62 To analyze the Universal Model ................................................................................... 63 To tune the Universal Model ......................................................................................... 65


To analyze the Universal Model

In the PLAN tab, click Tune button, the Model Tuning dialog box opens.

Figure 44: Universal Model - Model Tuning window

• Type a name for the model in the New Model Name box (use the same name for the new model as the name displayed in the Model box. In this way, you avoid creating a new model each time)

• From the Model Tuner list, choose Universal Model Analysis.

• If you want to edit the properties of the model before you analyze it, click Edit…, and in the Propagation Model Editor, edit the properties.

• Click OK.

• Once the analysis process is complete, click Close to view the model report.

Figure 45: Universal Model - Model analysis report

The Universal Model analysis report contains the following information:

• The Total Number of Points

• The Used Number of Points

• The Mean Error

• The Standard Deviation

• The Root Mean Square

• The Correlation Factor


• The Minimum Error

• The maximum Error

Note: The transmitters and the receivers located inside a building are not considered during the Universal Model Analysis process.


To tune the Universal Model

A fast and automated tuning module is integrated into the Universal Model that takes into account drive tests data and, as a result, improves prediction data and generates results that are closer to the real world. The tuning process results in the generation of two analyses that are used to adjust the coefficients of the model. In the last step of the tuning process, the Universal Model generates new predictions using the drive tests points with the tuned model. The tuning algorithm implemented in the Universal Model is based on a multi-linear regression method. The model recognizes that the amount of total loss is partly dependent on statistically estimated losses. This adjustable part is a sum of variables multiplied by coefficients. The tuning algorithm determines the value of these coefficients with the best fit of the test measurements. Because the statistical adjustment has no physical meaning, the Universal Model combines elementary physical theories prior to statically adjusting results. As the statistics are not the bases of the prediction results, poor measurements will not result in an unreliable tuned model.

In the PLAN tab, click Tune button, the Model Tuning dialog box opens.

Figure 46: Universal Model - Model Tuning window

• Type a name for the model in the New Model Name box.

• From the Model Tuner list, choose Universal Model Tuning.

• If you want to edit the properties of the model before you analyze it, click Edit…, and in the Propagation Model Editor, edit the properties.

• In the Tuning Parameters dialog box, you can define the drive tests quality control and the calibration type.


Figure 47: Universal Model - Tuning parameters window

When you select the Use automatic filtering checkbox, the tuning engine filters out drive tests where inconsistent values have been found, it means drive tests for which the mean error before tuning is outside the interval [-10;10] (these drive tests can generate inconsistency in the tuning coefficients). Note: When this option is selected, the process calculates and displays the percentage of CW files for which the mean error is comprised in the interval [-7;7] before the calibration (for example, if 10 CW files are available, and for one the mean error is outside the interval [-7;7], the quality will be 90%), a value close to 100 indicates that the drive tests files are of a good quality. This information is called Measures quality indicator and is displayed in the model tuning log. When you select the Do not consider indoor pixels for raster areas checkbox, the tuning engine filters out drive tests which are located inside Building clutter classes. When it is not enabled, drive tests which are located inside Building clutter classes are not considered as indoor, it means that tuning engine automatically sets the clutter classes type ‘Building’ to ‘Other’.

During the tuning process, the calibration tool optimizes coefficients for each type of morphology. Note that if the morphology option is not selected, the model will only use the default morphology meaning a unique optimisation for all environments. Before starting the tuning process, the calibration tool will separate the measurement points into different categories (boxes) according to the morphology they belong to and according to other criteria (typology (typology depends on the geographical data available on the considered area), Line of Sight, frequency, micro cellular context, etc.)

Note that there is an initial checking based on the minimum number of points: a

minimum of 1000 measurements points per box is required to start optimisation

otherwise the model uses default parameters.

The calibration process allows you to generate two different calibrations (it means

two different sets of coefficients):

- The first one, which will be apply when polygons are available on the

calculation area

- The second one, which will be apply when polygons are not available on the

calculation area The coefficients, which are calculated by the smallest square method, are passed as input parameters to the new tuned model.

You can choose between two types of tuning:


• When using the Standard calibration option, the calibration tool performs specific tuning for each box without any controls; it means that, for each box, it just tries to associate the variables calculated along the profile with the best coefficients to reduce the average and the standard deviation.

Note: The calibration tool optimizes all parameters (provided enough points

are available), which means the model can show very good stats against the

set of measurements used, but will probably be less robust when using the

same model in other types of environments, especially where a small number

of drive tests was used.

• When using the Advanced calibration option (recommended), the calibration

tool performs a specific calibration for each box but it first checks the

distribution of each variable calculated along the profile; it means that the

calibration tool will associate the variables calculated along the profile with

the best coefficients to reduce the average and the standard deviation but

only the variables considered as representative of the real-world environment.

The other variables will be associated to a default coefficient ('representative

of the reality' means in adequacy with what the model learnt during all steps

of its development).

Note: The calibration tool optimizes certain parameters (provided enough

points are available), which means the model can show very good statistics,

depending on the measurements used. Results can be a little less favorable

than with the other option but they will be more robust when using the same

model in other type of environment.

Note: The transmitters and the receivers located inside a building are not considered during the Universal Model’s Tuning process.

• Once the tuning process is complete, click Close to view the model report

Figure 48: Universal Model - Model tuning report

The Universal Model tuning report contains the following information:

• The Total Number of Points

• The Used Number of Points

• The Mean Error


• The Standard Deviation

• The Root Mean Square

• The Correlation Factor

• The Minimum Error

• The maximum Error


TABLE OF ILLUSTRATIONS Figure 1: LMTools – The Service/License File tab .......................................................................... 11 Figure 2: LMTools - Config Services tab ........................................................................................... 12 Figure 3: LMTools - Borrowing tab ................................................................................................... 13 Figure 4: Planet RPE service ............................................................................................................... 14 Figure 5: Environment Variables ....................................................................................................... 15 Figure 6: New User Variable .............................................................................................................. 15 Figure 7: Display name ....................................................................................................................... 16 Figure 8: Reflection + diffraction + guided propagation = the Universal Model trilogy .......... 21 Figure 9: Profile example (without polygons) ................................................................................... 23 Figure 10: Profile example (with polygons) ..................................................................................... 23 Figure 11: Profile construction for polygons .................................................................................... 24 Figure 12: Extraction of a profile ....................................................................................................... 25 Figure 13: Profile example of obstacles in thin ridges .................................................................... 26 Figure 14: Order of obtaining the positive edges committed ........................................................ 27 Figure 15: Example of facets ............................................................................................................... 30 Figure 16: Profile example for the Graphs component ................................................................... 31 Figure 17: Example of graph (Paris) .................................................................................................. 32 Figure 18: Examples of paths for the graphs component ............................................................... 32 Figure 19: Wave propagation simulated by the multipath component ....................................... 34 Figure 20: Extrusion of buildings ...................................................................................................... 35 Figure 21: Extrusion of bridges .......................................................................................................... 35 Figure 22: Extrusion of forests ........................................................................................................... 35 Figure 23: Extrusion of water surfaces .............................................................................................. 35 Figure 24: Create a new Masked Universal Model ......................................................................... 38 Figure 25: Create a new Unasked Universal Model ....................................................................... 38 Figure 26: Universal Model - General tab ........................................................................................ 39 Figure 27: Universal Model - Geodata tab ....................................................................................... 40 Figure 28: Universal Model - Clutter Settings window .................................................................. 41 Figure 29: Universal Model - Facets generator window ................................................................ 43 Figure 30: Universal Model - Graphs generator window .............................................................. 43 Figure 31: Universal Model - Morphologies generator window................................................... 44 Figure 32: Universal Model - Time Optimization tab ..................................................................... 46 Figure 33: Universal Model - Radial mode ...................................................................................... 47 Figure 34: Universal Model - Second resolution mode .................................................................. 48 Figure 35: Universal Model - Optimized calculation area ............................................................. 49 Figure 36: Universal Model - Radio optimization tab .................................................................... 50 Figure 37: Universal Model - Horizontal propagation ................................................................... 51 Figure 38: Universal Model - Used weighted tuning coefficients ................................................. 52 Figure 39: Universal Model - Buildings calculation ........................................................................ 52 Figure 40: Universal Model - Depenetration feature ...................................................................... 54 Figure 41: Universal Model - Advanced tab .................................................................................... 56 Figure 42: Universal Model - Antenna correction ........................................................................... 57 Figure 43: Universal Model - Multipath tab..................................................................................... 58 Figure 44: Universal Model - Model Tuning window .................................................................... 63 Figure 45: Universal Model - Model analysis report ...................................................................... 63 Figure 46: Universal Model - Model Tuning window .................................................................... 65 Figure 47: Universal Model - Tuning parameters window ........................................................... 66 Figure 48: Universal Model - Model tuning report ......................................................................... 67

universal model user guide - infovistawebhelp.infovista.com/planet/62/content/pdfs/universal...page...

Documents