2G 3G User Manual

NICE Optimize

NES User Manual

Version 1.0

September 2014

Copyright 2014 NICE Systems Ltd. All rights reserved.

Important NoticeNICE Systems Ltd. shall bear no responsibility or liability to a client or to any person or entity with respect to liability, loss or damage caused or alleged to be caused directly or indirectly by any NICE product. This includes, but is not limited to, any interruption of service, loss of business or anticipatory profits or consequential damage resulting from the use or operation of any NICE products. Information in this document is subject to change without notice and does not represent a commitment on the part of NICE Systems Ltd. The systems described in this document are furnished under a license agreement or non-disclosure agreement.

All information included in this document, such as text, graphics, photos, logos and images, is the exclusive property of NICE Systems Ltd. and protected by United States and international copyright laws. Permission is granted to view and photocopy (or print) materials from this document for personal, non-commercial use only. Any other copying, distribution, retransmission or modification of the information in this document, whether in electronic or hard copy form, without the express prior written permission of NICE Systems Ltd., is strictly prohibited. In the event of any permitted copying, redistribution or publication of copyrighted material, no changes in, or deletion of, author attribution, trademark legend or copyright notice shall be made.

NICE Disclaimer: We own the following trademarks in different countries: ACTIMIZE, Actimize logo, Alpha, Customer Feedback, eGlue Interact, FAST, FAST alpha Silver, Fortent, Fortent Logo, IEX, Insight from Interactions, Intent. Insight. Impact., Interaction Capture Unit, Know More, Risk Less, Last Message Replay, Mass Detection, Center, Mirra, My Universe, NICE, NICE Analyzer, NICE Inform, NICE Logo, NICE Perform, NICE Situator, NICE SmartCenter, NICE Storage Center, NICE Systems, NiceCall, NiceCall Focus, NiceLog, NiceTrack, NiceTrack IP Probe, NiceTrack Location Tracking, NiceTrack Mass Detection Center, NiceTrack Monitoring Center, NiceTrack Pattern Analyzer, NiceTrack Traffic Analysis, NiceVision, NiceVision Alto, NiceVision Analytics, NiceVision ControlCenter, NiceVision Digital, NiceVision Net, NiceVision NVSAT, NiceVision Pro, Open Situation Management, Playback Organizer, Scenario Replay, Searchspace, Syfact, Syfact Investigator, TotalView are trademarks and/or registered trademarks of NICE Systems Ltd. All other trademarks are the property of their respective owners.

All contents of this document are: Copyright © 2014 NICE Systems Ltd. All rights reserved.

Contents

1 About This Manual.................................................................................................1

1.1 Who Should Read This Manual.................................................................1

1.2 Manual Overview......................................................................................1

1.3 Acronyms and Abbreviations.....................................................................1

1.4 Manual Conventions.................................................................................2

1.5 Related Documentation.............................................................................3

1.6 Technical Support.....................................................................................3

2 Introduction............................................................................................................4

3 New Project............................................................................................................5

3.1 GIS Database............................................................................................5

3.2 Network Configurations...........................................................................10

3.3 Create New NES Project.........................................................................17

3.4 Create Digital Terrain Map......................................................................18

3.5 Import Network........................................................................................24

4 Coverage..............................................................................................................35

4.1 Create Coverage Database.....................................................................35

4.2 Coverage Analysis Setup........................................................................37

4.3 Calculate Coverage by Host....................................................................41

4.4 Hawk Database.......................................................................................50

5 GSM Parsing and Location.................................................................................51

6 UMTS Network Consistency Analyzer...............................................................53

7 GEO Monitoring...................................................................................................55

7.1 Map Legends Setting..............................................................................55

7.2 Polygon Setting.......................................................................................56

7.3 UMTS Maps Based on EventDB Files....................................................57

7.4 UMTS Events Map Navigator..................................................................62

8 Network Optimization..........................................................................................64

8.1 Preparation..............................................................................................64

8.2 Optimization Process..............................................................................68

List of TablesTable 1-1: Manual Overview..............................................................................................1Table 1-2: Acronyms and Abbreviations............................................................................1Table 1-3: Typography Conventions..................................................................................2Table 1-4: Related Documents...........................................................................................3Table 3-1: ASCII Grid Digital Terrain Map File Format Parameters...................................6Table 3-2: DTM source Format Txt File Parameters..........................................................7Table 3-3: Clutters Index File Column Description.............................................................8Table 3-4: Clutters Data File Column Description..............................................................9Table 3-5: GSM Antenna Information Parameters...........................................................11Table 3-6: UMTS Antenna Information Parameters.........................................................12Table 3-7: LTE Antenna Information Parameters.............................................................12Table 3-8: Parameters With Predefined Prefix.................................................................14Table 3-9: Radio Information Parameters........................................................................14Table 3-10: GSM/UMTS Neighbor Cell Information.........................................................15Table 3-11: Antenna Pattern Information.........................................................................15Table 3-12: Antenna Pattern Files Format.......................................................................17Table 3-13: New Project Window Settings.......................................................................18Table 3-14: Import DTM Configuration Settings...............................................................20Table 3-15: Create Buildings Polygons Database Selection Parameters.........................22Table 3-16: ImportAntenna.ini File...................................................................................26Table 3-17: Adjacents Display Window Options...............................................................30Table 3-18: Site Dialog Window Description....................................................................32Table 3-19: Installtion Methods........................................................................................34Table 4-1: Create Coverage Database Settings...............................................................37Table 4-2: The Calculate Coverage by Hosts Settings.....................................................43Table 4-3: Host Job Operations.......................................................................................45Table 4-4: Sector Group Options.....................................................................................46Table 4-5: Results List Group Options.............................................................................46Table 4-6: Right Side Window Options............................................................................46Table 4-7: Sector Group Options.....................................................................................48Table 4-8: Results List Group Options.............................................................................48Table 4-9: Right Side Window Options............................................................................49Table 4-10: Create Hawk Database Window Settings.....................................................50Table 6-2: Analysis Window Description..........................................................................54Table 7-1: Layer Control Icons.........................................................................................56Table 7-2: Event Selector Interface..................................................................................57Table 7-3: Create Event Map Configuration Settings.......................................................58Table 7-4: Color By Options Window...............................................................................59Table 7-5: Practice - Event Selector Settings...................................................................61Table 7-6: Event 3G Maps Navigator Window Description..............................................62Table 8-1: Advanced Settings..........................................................................................69Table 8-2: Global Constraints Settings.............................................................................70Table 8-3: Changes Tab Settings.....................................................................................71

List of FiguresFigure 3-1: ASCII Grid DTM File Format............................................................................6Figure 3-2: Digital Terrain Map source in Txt File Format..................................................7Figure 3-3: Clutters Index.txt File.......................................................................................8Figure 3-4: Clutters Menu.txt file........................................................................................8Figure 3-5: Clutters Data *.txt File......................................................................................9

Figure 3-6: Building Polygons Table..................................................................................9Figure 3-7: Street Roads Table Format............................................................................10Figure 3-8: Antenna.txt Source File..................................................................................13Figure 3-9: Radio.txt Source File......................................................................................14Figure 3-10: Adjacent.txt Source File...............................................................................15Figure 3-11: Antenna_Pattern.nir File..............................................................................17Figure 3-12: Create DTM Tiles Window (Step 1 of 2)......................................................19Figure 3-13: Create DTM Tiles Window (Step 2 of 2)......................................................20Figure 3-14: New Files Created in Destination Folder......................................................21Figure 3-15: Project Editor...............................................................................................21Figure 3-16: Create Roads Database Window.................................................................24Figure 3-17: Sites and Sectors.........................................................................................25Figure 3-18: Map Displaying Cell Scrambling Code\PCI..................................................27Figure 3-19: Project Editor...............................................................................................28Figure 3-20: Map Displaying Sector Channels.................................................................29Figure 3-21: Adjacents Display........................................................................................31Figure 3-22: Site Dialog Window......................................................................................31Figure 3-23: Before and After Antenna Alignment............................................................33Figure 3-24: Sectors Selection.........................................................................................33Figure 3-25: Before and After Antennas Moved to the Corners.......................................34Figure 4-1: Polygon Drawn Around Map..........................................................................35Figure 4-2: Create Coverage Database Window..............................................................36Figure 4-3: Project Editor Window....................................................................................38Figure 4-4: Project and Technology Editor.......................................................................39Figure 4-5: Clutters List Table..........................................................................................40Figure 4-6: Sector Selection List Window........................................................................41Figure 4-7: Coverage Analysis Window...........................................................................41Figure 4-8: Calculate Coverage by Hosts........................................................................42Figure 4-9: Host Tasks Status Window............................................................................43Figure 4-10: NESHost Configuration Window..................................................................44Figure 4-11: Display Coverage Results Window..............................................................45Figure 4-12: Display Coverage Map.................................................................................47Figure 4-13: Display Coverage Results............................................................................48Figure 4-14: RSCP Map of UMTS_2100_f1.....................................................................49Figure 4-15: Create HAWK Database..............................................................................50Figure 5-1: IPDR_GL_EVENTS.......................................................................................51Figure 5-2: IPDR_GL_MSR.............................................................................................52Figure 5-3: MAP_AGGR_XY_PIXELS_FILE....................................................................52Figure 6-1: Network Consistency Analyzer Completed....................................................53Figure 7-1: Create Maps Configuration............................................................................61Figure 7-2: Event 3G Maps Navigator Window................................................................62Figure 8-1: Event Selector...............................................................................................65Figure 8-2: Optimization Polygons...................................................................................66Figure 8-3: Project Editor Default Technology..................................................................67Figure 8-4: Advanced Settings Window...........................................................................69Figure 8-5: Global Constraints Tab..................................................................................70Figure 8-6: Constraints List..............................................................................................71Figure 8-7: Optimization Changes by Status....................................................................72

NICE Optimize

NES User Manual UMTS Parsing and Location

1 About This ManualThis document describes how to use the Network Engineering Station (NES). It also contains detailed step-by-step procedures to make sure of correct use of NES.

1.1 Who Should Read This ManualIt is assumed that readers of this document are familiar with these topics: Cellular Network systems; Microsoft Windows operating systems; Geo location concepts, work processes and systems; communication concepts, and practices.

1.2 Manual OverviewAn overview of the information included in this manual is described in Table 1-1.

Table 1-1: Manual Overview

Section

Heading Description

1. About This Manual Defines the scope, structure, and purpose of the information contained in this document. Also contains general reference information and a list of related documents.

2. Introduction Outlines the optimization process provided by the NES application and operations performed by the user.

3. New Project Describes GIS import formats used by the NES and these operations: network configurations, create new project, create new digital terrain map and import network.

4. Coverage Describes how to create the coverage database, configure and calculate signal strength from each base station. The coverage analysis provides the Radio Frequency foot print for the area, roads and buildings with a predefined resolution.

5. Parsing and Location

Geo-Client, Pars-Gen, LME to create Network mass events Database.

6. Geo Monitoring Outlines the map legends setting, polygon setting, UMTS maps based on EventDB files and the Events Map Navigator.

7. Network Optimization

Describes the process used to optimize the performance of the NES system.

1.3 Acronyms and AbbreviationsThe abbreviations and acronyms used in this document are listed in Table 1-2.

Table 1-2: Acronyms and Abbreviations

Acronym Description

CDR Call Detail Record

DCR Drop Call Rate

DTM Digital Terrain Map

GSM Global System for Mobile

Page 1 of 77

NICE Optimize


Acronym Description

GIS Geographic Information Systems

GLE Geo Location Engine

GPEH General Performance Event Handler

HSPA High Speed Packet Access

IMSI International Mobile Subscriber Identity

LFE Location Front End

LME Location Manager Engine

PCI Physical Cell identifier,

RCSP Received Signal Code Power

RF Radio Frequency

RNC Radio Network Controller

UMTS Universal Mobile Telecommunications System

VDTA Virtual Drive Test Aggregated

1.4 Manual ConventionsThe typography conventions used in this manual are described in Table 1-3.

Table 1-3: Typography Conventions

Style Usage Example

Initial Capitals

+ Bold

Menus, dialog box options, and commands

To access the application, click Start > Programs > Accessories >Paint.

Italic Text Field names, file names, folder names, and file paths

Type the IP address in the Address field.

Run the setup.exe file in: C:\Installation\Setup.

Moonscape (Courier New font)

Code samples, error messages The following error message is displayed:

error opening database: database is currently in use.

UPPERCASE Code keywords and database elements

Use the INNER JOIN clause in SQL Server to join one table to another.

<Ctrl-x> Indicates a key that is pressed or a control character sequence

Press <Enter> means press the Enter key. Or, press <Ctrl-x> means press the Control key and the x key simultaneously.

This manual also contains text with special formatting to provide reference information, cautions, and warnings for the user.

NOTE: A NOTE identifies additional information or references that apply to an operation, procedure or practice.

Page 2 of 77

NICE Optimize


IMPORTANT: An IMPORTANT notice stresses the point more than a NOTE.

TIP: A TIP identifies topics or tutorials that apply to an operation, procedure or practice.

WARNING: A WARNING is stronger than a CAUTION.

CAUTION: A CAUTION indicates a hazard. It identifies an operation, procedure, or practice, which, if not correctly performed or followed, can cause damage to or destruction of part or all of the system components. Do not perform any procedure indicated by a CAUTION sign until the indicated conditions are fully understood and followed.

1.5 Related DocumentationRelated documents are listed in Table 1-4.

Table 1-4: Related Documents

Item No. Title

1. Reference Guide, XXX 2014

2. Release Note, XXX 2014

3. Installation Manual, XXX 2014

1.6 Technical SupportThis document contains all the information necessary for correct operation of the NES. If the information you need is not in this document, refer to the related documents or contact your technical support representative.

The NES provides the highest level of technical support for its products. Technical support services include:

Training Services: The NES provides both in-house and on-site training courses for system operators, technical, and system administrators.

Documentation Resources: All NES products are supplied with comprehensive technical documentation. In addition, the NES provides customers with periodic release notes and technical bulletins.

Follow-on Support: NES provides a full range of support packages from telephone support to dedicated walk-through, project-building help.

For more information about NES documentation, training, and support services, contact your local NES representative.

Page 3 of 77

NICE Optimize


2 IntroductionService provider mobile networks are designed to provide the best possible performance as shown by Key Performance Indicators (KPI). The natural growth of the network requires that new sites, antennas and radios need to be added. The customer needs constantly change and the type of service used, for example, voice and data. These changes influence current mobile network performance and make fine tuning necessary to improve the key performances indicators.

The optimization process provided by the NES application includes:

1. Geographical Information System (GIS)

2. Network Configurations

3. Real network records (CDRs)

This user manual describes these operations:

Creating GIS Database (DTM, Building, Roads, Clutters)

Creating Network Database (Site, Sector, Antenna, Radio, Adjacent)

Coverage analysis

Creating HAWK Database

Events import (CDRs)

NCA analysis

Model Maintenance

Generating Event thematic maps

Optimization analysis

Optimization results

NOTE: The NES product installation procedure is described in the NES Installation Guide. The executable application (NES.exe) is displayed under the installation folder C:\Program Files\NES and also a shortcut icon in the desktop.

Page 4 of 77

NICE Optimize


3 New ProjectThis section describes Geographic Information Systems (GIS) import formats used by the NES to make an operational project. This includes the conversion of these formats into supported formats.

NOTE: The method used to import the formats into the product is described in section 3.3 which explains how to import network configuration files and finalize a new project.

3.1 GIS DatabaseNES simulates the Radio Frequency (RF) environment generated by the service providers network. This Radio Frequency (RF) footprint provides the most suitable coordinates to be used at a later time for the network events locations. To provide an accurate RF foot print the NES uses these measurements as inputs:

Surface heights (terrain)

Clutters dimensions (and optionally heights)

Building shapes

This section describes the formats that create the 3D Digital Terrain Map (DTM). The formats hold all the Geographic Information Systems (GIS) information necessary to simulate, real world geography.

3.1.1 Terrain FormatsThe Digital Terrain Map (DTM) information is represented in various formats. The CreateDTMTiles conversion utility supports these formats:

ASCII Grid: shown as: *.grd, *.asc, *.txt

Plain txt file: containing X,Y coordinates and Height

NOTE: Each format must contain the coordinate information shown in decimal meter units and not in degrees.

Page 5 of 77

NICE Optimize


An example of an ASCII Grid DTM file format is shown in Figure 3-1.

Figure 3-1: ASCII Grid DTM File Format

ASCII Grid Digital Terrain Map (DTM) file format parameters are described in Table 3-5.

Table 3-5: ASCII Grid Digital Terrain Map File Format Parameters

Parameter Description

Ncols Number of columns to calculate from the reference point on the X axis.

Nrows Number of columns to calculate from the reference point on the Y axis.

Xllcorner X coordinates of the lowest left corner in a metric coordinate system (reference point).

Yllcorner Y coordinates of the lowest left corner in a metric coordinate system (reference point).

Cellsize Resolution of the terrain source file, represented in meter units.

Nodatavalue Null value. This means that the height information at a certain point is unknown.

Page 6 of 77

NICE Optimize


An example of a DTM source in txt file format is shown in Figure 3-2.

Figure 3-2: Digital Terrain Map source in Txt File Format

DTM source Format Txt File Parameters are described in Table 3-6.

Table 3-6: DTM source Format Txt File Parameters


X Horizontal axis coordinates in a metric system units.

Y Vertical axis coordinates in a metric system units.

Z Height of the point in meters.

3.1.2 Clutters FormatThe Clutters information is represented in various formats. The CreateDTMTiles conversion utility supports these formats:

ASCII Grid formats are: *.grc, *.asc, *.txt

Plain txt files containing:

a) Main txt file contains X,Y coordinates, Clutter ID and Height (optional)

b) Index txt file shows the location of the main txt file\files

c) Clutter ID txt file contains Clutter Name and Clutter ID

NOTE: All formats must contain the coordinate information represented in decimal meters and not in degrees.

Page 7 of 77

NICE Optimize


The ASCII Grid Clutters file format is similar to the terrain ASCII grid format but Clutter ID replaces Height information.

Some examples of Clutters source files in txt file formats include, index.txt file, menu.txt file and data*.txt file shown in Figure 3-3 thru Figure 3-5.

Figure 3-3: Clutters Index.txt File

Each column in Figure 3-3 is described in Table 3-7.

Table 3-7: Clutters Index File Column Description

Column Description

First File containing clutters information.

Second Min X point of the file

Third Max X point of the file

Fourth Min Y point of the file

Fifth Max Y point of the file

Sixth Resolution of the file shown in meters

The naming of each clutter ID is shown in Figure 3-4.

Figure 3-4: Clutters Menu.txt file

Page 8 of 77

NICE Optimize


Each column in Figure 3-5 is described in Table 3-8.

Figure 3-5: Clutters Data *.txt File

Table 3-8: Clutters Data File Column Description

Column Description

First X coordinate of a certain point

Second Y coordinate of a certain point

Third Clutter ID

Fourth Clutters height (optional)

3.1.3 Building Polygons FormatThe Building Polygons table has a MapInfo supported file format in the coordinate system of the Digital Terrain Map (DTM). It contains polygons or regions that each has a maximum of 240 nodes. The table must contain at least one integer field with a unique building ID and a float field with the building height. The building height can be either absolute, above sea level or relative to ground height. The Building polygons table is shown in Figure 3-6.

Figure 3-6: Building Polygons Table

Page 9 of 77

NICE Optimize


You can change the structure of the fields of any table with the MapInfo menu tools. To view or modify the table structure, do these steps:

1. Select Table > Maintenance > Table Structure. The View/Modify Table Structure window is displayed.

2. Select a table to modify and click OK. The Modify Table Structure window is displayed.

3. Navigate to the column to modify, select the Indexed option for that column and click OK.

NOTE: You can also add new fields, remove fields and change the order of columns using the up and down arrows.

3.1.4 Street and Roads FormatThe Streets and Roads polyline table has a MapInfo supported file format in the coordinate system of the Digital Terrain Map (DTM). It contains polyline information for each street or road. The table must contain at least one integer field with a unique Street or Road ID.

An example of Streets and Roads table in a *.tab file format, which is opened with MapInfo is shown in Figure 3-7.

Figure 3-7: Street and Roads Table Format

3.2 Network Configurations Network configurations source files are divided into four categories:

Antenna file

Radio file

Adjacent file

Antenna Pattern files

When all four of these source file categories are successfully applied, the NES product completes the initial project construction phase and enables the analysis process to start.

Page 10 of 77

NICE Optimize


3.2.1 Antenna (Cell) Configuration FormatThe Antenna file uses a txt file format and contains information about sites, cells, radio and antennas of the service providers network. The parameters described in Table 3-9 thru Table3-11 are used in the source files for GSM, UMTS and LTE networks.

It is recommended to separate inner carrier bands into different technologies. For example: GSM_1800, GSM_900, LTE_1800_f1, LTE_1800_f2, UMTS_2100_f1, and UMTS_2100_f2. The separation of inner technology improves location accuracy and network optimization results.

NOTE: NES identifies the proper parameter by the exact Field Name specified in the corresponding tables, the order has no significance.

Table 3-9: GSM Antenna Information Parameters

Field Name Type Description

SiteName String Site Name

SectorName String Sector Name

BSC String Serving BSC

La_LACID Integer Location Area Identifier

CellID Integer Cell Identifier (the CI in the CGI)

Address String Site Location Address, Zip code, Location.

BSIC Integer Unique network identifier

BCCH Integer Cell BCCH Channel (for example 590)

TechName String Technology and band name, for example GSM_1800

Power Float Tx Power of the equipment output.

Active Boolean Cell On Air. (Yes, No)

X Float X coordinate of current antenna (Meters units)

Y Float Y coordinate of current antenna (Meters units)

AntennaHeight Float Antenna height above ground

Azimuth Integer Antenna Azimuth

Tilt Integer Antenna Mechanical Tilt

ETilt Integer Antenna Electrical Tilt (automatically taken from antenna pattern)

AntName String Current antenna Name (model of antenna, must be in the antennas Profile Database)

CableType String Antenna cable Type, for example ½ and 7/8

CableLength Integer Antenna Cable Length

Installation Type String Describes the position of antenna, for example Tower, Tower On Building, Roof Top Edge, Wall Installation, Indoor, and Underground.

Indoor Boolean Antenna covers only indoor area (Yes, No)

Indoor Detail String Describes the indoor antenna position. Building ID / Building Name and from Height to Height or Under Ground Station Name.

Page 11 of 77

NICE Optimize


Table 3-10: UMTS Antenna Information Parameters


SiteName String Site Name.

SectorName String Sector Name.

RNC String Serving RNC name

RNCID Integer Serving RNC ID

La_LACID Integer Location Area Identifier.

CellID Integer Cell Identifier (the CI in the CGI)

Address String Site Location Address, Zip code, Location.

ScramblingC Integer Cells Scrambling Code.

Carrier Integer Cell Carrier (e.g. 10788).

TechName String Technology and band name, for example UMTS_2100.

Power Float Max Tx Power of the available.

Active Boolean Cell On Air. (Yes, No)

X Float X coordinates of current antenna (Meters units).

Y Float Y coordinates of current antenna (Meters units).

Pilot Float CPICH Power at the Antenna input.

AntennaHeight Float Antenna height above ground.

Azimuth Integer Antenna Azimuth.

Tilt Integer Antenna Mechanical Tilt.

ETilt Integer Antenna Electrical Tilt.

AntName String Current antenna Name (model of antenna, must be in the antennas Profile Database).

CableType String Antenna cable Type (for example 1/2, 7/8).

CableLength Integer Antenna Cable Length.

Installation Type String Describe the position of antenna (for example Tower, Tower On Building ,Roof Top Edge ,Wall Installation ,Indoor, Underground).

Indoor Boolean Antenna covers only indoor area (Yes, No)

Indoor Detail String Describe the indoor antenna position. Building ID / Building Name and from Height to Height or Under Ground Station Name.

Installation Type String Describe the position of antenna (for example, Tower, Tower On Building, Roof Top Edge, Wall Installation, Indoor or Underground).

RET Boolean Does the antenna have an active RET.

Table 3-11: LTE Antenna Information Parameters


SiteName String Site Name, if not provided insert MRBTS

SectorName String Cell Name, if not provided insert eNBid

Antennaid Integer Set to 1 if not provided, used for split Antennas. Split antennas are the same Cell used in different directions

Page 12 of 77

NICE Optimize



MRBTS Integer Site ID identifier

eNBid Integer Unique Sector identifier. The two digits on the right are the Sector ID.( calculated as: MRBTS and IcrId)

lcrId Small integer

Sector identifier

eutraCelId integer Sector unique identity would be used also as SectorCode, if not provided calculated as: (256*MRBTS) and IcrId

earfcnDL string Carrier – channel number

pMax integer Maximum transmitted power , calculated by dividing by 10

PCI integer Physical Cell Identifier, instead of SC in UMTS

MimoActiveGain integer Mimo gain, calculated by dividing by 10

AntennaTotalLoss integer Power loss , calculated by dividing by 10, set in antenna loss

TotalPowerdBm integer set as Antenna_PWR (calculation: (pMax+ MimoActiveGain+ AntennaTotalLoss)/10 )

RefSignal integer Calculations of TotalPowerdBm(Watt)/300

Technology string Technology and band name

X Float X coordinate of current antenna (in meters)

Y Float Y coordinate of current antenna (in meters)

Address String Site Address

AntennaHeight Float Antenna height above ground

Azimuth Integer Antenna Azimuth

MTilt Integer Antenna Mechanical Tilt

ETilt Integer Antenna Electrical Tilt

AntName String Current antenna name (model of antenna must be in the Antenna Profile db)

Indoor Boolean Antenna covers only indoor area

RAD_Carrier String Cell Carrier, for example 1275.

RAD_RadioType String Radio service type, for example, BCCH

RAD_FreqSeq String Channel sequence, copy RadioType value

An example of an Antenna text file is shown in Figure 3-8.

Figure 3-8: Antenna.txt Source File

Additional parameters can be imported with a predefined prefix, for example, you can define an Installation Type parameter by adding the column, SCT_InstallationType where SCT is the prefix of Sector. Example parameters with a predefined prefix are listed in Table 3-12.

Page 13 of 77

NICE Optimize


NOTE: All the network configurations can be imported with a single antenna file which has all the service providers technologies and bands.

Table 3-12: Parameters With Predefined Prefix


SCT_XXXX Sector add on field

RAD_XXXX Radio add on field

SIT_XXXX Site add on field

ANT_XXXX Antenna add on field

3.2.2 GSM Radio ConfigurationThe Global System for Mobile (GSM) Radio configuration uses a .txt file format. This file contains specific information about the radios for each cell and for each service providers network. The required table parameters for the source file are described in Table 3-13.

Table 3-13: Radio Information Parameters


SectorCode Integer Unique code representing the Cell containing this Radio

TRXId Integer Unique id per radio per cell

Type String Radio service type, for example, BCCH or TCH

Carrier String The configured channel

Sequence String The MAL id used by the radio (when it exists)

An example of a Radio source text file is shown in Figure 3-9.

Figure 3-9: Radio.txt Source File

Page 14 of 77

NICE Optimize


3.2.3 Adjacent ConfigurationThe Adjacent Configurations file uses a txt file format that contains specific information about the service provider networks adjacent relations. The mandatory table parameters for the source file are listed in Table 3-14.

Table 3-14: GSM/UMTS Neighbor Cell Information

Field Name Type Required Description

CellName Integer Mandatory Source Cell Identifier

Source Technology String Optional Source Technology (GSM and UMTS)

AdjName Integer Mandatory Target Cell Identifier

Target Technology String Optional Target Technology (GSM and UMTS)

Attempts Integer Optional Amount of Handovers

An example of an Adjacent.txt source file is shown in Figure 3-10.

Figure 3-10: Adjacent.txt Source File

3.2.4 Antenna Pattern ConversionEach antenna model has its own unique Radio Frequency (RF) signature. This makes it important to identify the serving antennas model for location calculation. The information necessary for each antenna model used in the network is described in Table 3-15.

Table 3-15: Antenna Pattern Information

Field Name Description Example Value Comment

Antenna Name Antenna model Ant60Deg Must be the file name.

Base Frequency

Base antenna frequency 1900

Max gain Max gain in the main lobe (dBi) 10.5

beam width Antenna beam width used for displaying the sector

60 Cosmetic (drawing) use only

range Antenna range used for 1000 Cosmetic (drawing) use

Page 15 of 77

NICE Optimize



displaying the sector only

description One line Antenna description Antenna 60 Deg Text

Cross polar attenuation

Fix attenuation when optimization while using cross polarization.

Cross polar attenuation

Must be zero if not used.

Horizontal Antenna Name

The name of the antenna that would replace this antenna if the polarization of the radio is changed.

Horizontal Antenna Name

Electrical Tilt Electrical Tilt 5 The vertical list must pointed into main lobe (Max gain)

Fix Title Vertical Refer to example file

V plan pattern in 0° 0.000000 Line 13

VERTICAL plan pattern in 1° -0.100000 Line 14


-0.300000

VERTICAL plan pattern in 359° 0.000000 Line 372

Fix Title Horizontal Line 373

H plan pattern in 0° 0.000000 Line 374

HORIZONTAL plan pattern in 1°

-0.100000 Line 375

HORIZONTAL plan pattern in 2°

-0.200000 Line 376

-0.300000

HORIZONTAL plan value in 359°

0.000000 Line 733

Fix Title Vertical Crosspolar

From this line (734) on, it is optional (Only when dealing with cross polarization antennas).




-0.300000


Fix Title Horizontal Crosspolar

Line 1095

HORIZONTAL LAN pattern in 0°

0.000000 Line 1096


-0.100000 Line 1097


-0.200000 Line 1098

-0.300000

HORIZONTAL plan pattern in 0.000000 Line 1455

Page 16 of 77

NICE Optimize



359°

Each antenna manufacturer provides an Antenna Profile File in different formats. The files are converted to a generic supported format, shown in Table 3-15. For antennas with electrical tilt, the sampled pattern refers to the main lobe. For example, if the electrical tilt is 4, the vertical antenna pattern shifts 4 steps upwards.

An example of an Antenna_Pattern.nir supported file is shown in Figure 3-11.

Figure 3-11: Antenna_Pattern.nir File

The new antenna pattern files must also be renamed with a specific naming convention as described in Table 3-16.

Table 3-16: Antenna Pattern Files Format

Format Example

Antenna_Name+_+Frequency+_E+Electrical tilt 742234_1800_E05.

The use of this naming convention means antenna patterns of the same antenna type in different frequency bands can be identified. All converted antenna files must be stored in the Antenna folder in the application installation folder.

3.3 Create New NES ProjectWhen the Geographic Information System (GIS) and Network data is available, a project is created with NES to simulate a service providers network coverage. The methods to create an operational project for the NES product are:

Page 17 of 77

NICE Optimize


Construct the network element manually one by one

Import the entire network configuration by using files in a predefined format.

This section describes the import of the entire network configuration.

To create a new project, do these steps:

1. Open the NES application. The MapInfo user interface is displayed with an additional menu items: NES.

2. Select NES > New Project > Empty Project from the menu bar. The new project window is displayed.

3. Click Browse, to browse for a folder or select an item from the list to configure settings for Project Name, Projection and Technology as described in Table 3-17.

Table 3-17: New Project Window Settings

Setting Description

Project Name Do this step:

Navigate to a project folder path and type a specific project name.

Note: it is recommended to store the project in a predefined Projects folder.

Projection Do these steps:

1. Click Browse. The Choose Projection window is displayed.

2. Select an item from the Category list

3. Select an item from the Category Members list

Note: this is the same projection as GISs

Technology Do this step:

Select the correct technology for the Technology list.

4. Click New. The Project Definition window is displayed.

5. Select Basic Map Layer under the Auto Option column.

6. Click the text box at the right of Basic Map Layer and navigate to streets.tab from under the SRC folder.

TIP: It is recommended to put all GIS files in a dedicated folder, for example, C:\Maps\SRC. This enables the streets map to be displayed in the main window by default.

7. Click OK. The NES is open and ready for DTM configuration.

NOTE: The demo project uses Universal Transvers Mercator (WGS 84), zone 36 north.

3.4 Create Digital Terrain MapThis section describes how to create the Digital Terrain Map (DTM) which is the basic GIS database. The Digital Terrain Map (DTM) contains 3D information about the ground surface, buildings and clutters (optional). Streets and roads are also added to the same DTM database.

Page 18 of 77

NICE Optimize


NOTE: This process uses the CreateDTMTiles.exe application which is usually found in the NES installation folder but can also be accessed through NES.

3.4.1 Create Digital Terrain Map TilesTo create Digital Terrain Map (DTM) tiles, do these steps:

1. Select Analysis > Database > Convert DTM from ASCII XYZ from the menu bar. The Create DTM Tiles (Step 1 of 2) window is displayed as shown in Figure 3-12.

2. Click Browse in the Source box and browse to the Terrain Source file.

3. Click Browse in the Destination box and browse to the folder where the converted DTM is stored.

WARNING: Do not select the Building exist option. This is only selected when the source terrain file also contains building information.

4. Select Import Clutter when there is a clutter source file and click Browse to browse to the folder where the Clutters index file is stored.

Figure 3-12: Create DTM Tiles Window (Step 1 of 2)

5. Click Next. The Create DTM Tiles (Step 2 of 2) window is displayed as shown in Figure 3-13.

Page 19 of 77

NICE Optimize


Figure 3-13: Create DTM Tiles Window (Step 2 of 2)

6. Type the configuration settings described in Table 3-18.

Table 3-18: Import DTM Configuration Settings

Setting Description

Tile dimension (m) Defines the inner tiles cut in meters (automatic analysis).

Pixel dimension (m) Sets the source file resolution.

– Recommended range is 20 to 50 meters.

Note: a resolution that is too high causes a slowdown in performance and resolution too low generates less accurate results.

Use Interpolation Note: This must be selected.

Borders Defines the 4 external coordinates of the source terrain.

Import Clutters (TXT) - left table

Defines the clutter id and clutter name of the clutter source file.

Note: The system enables you to define up to a maximum of 14 different clutters.

Import Clutters (TXT) - right table

Defines the clutter id, clutter source file name and the NES clutter name displayed by the application.

– When you select any new clutter item, a scroll menu is displayed that provides an option to combine source clutters into NES clutters.

Note: this usually applies when there are more than 14 different clutter types.

Page 20 of 77

NICE Optimize


7. Click Finish. Clutters are imported into the system. The application processes the terrain source file and adds the Clutter source file to it. New files are created in the user defined destination as shown in Figure 3-14. These include Digital Terrain Map (DTM) tile files and the DTMIndex.txt file which stores basic information about the DTM tiles:

Figure 3-14: New Files Created in Destination Folder

8. Select Project > Project and Technology Editor from the menu bar. The Project Editor is displayed as shown in Figure 3-15. This refers the application to the Digital Terrain Map (DTM) created in step 7.

9. Select Tables and Files from the menu in the left side window and make sure that the DTMindex.txt file is selected from the Terrain (3D layer) in the right side window.

NOTE: To change the file selected in the folder path to DTMindex.txt, click in the folder path box, the Define Terrain Tiles List window is displayed. Navigate to the folder containing the DTMindex.txt file

10. Click OK. A Digital Terrain Map (DTM) is now referenced in the project for the coverage analysis.

Figure 3-15: Project Editor

Page 21 of 77

NICE Optimize


To examine the DTM, do these steps:

1. Click Display Terrain found on the Display floating icons bar. The Height Map Preview window is displayed.

2. Select from among these default DTM display options:

– Default Colors: RGB or Atlas

– Add to Terrain: Clutter layer or Shading

– Click DTM Colors or Clutters to change the Colors resolution

3. Click OK. The Basic Layer Terrain Map is displayed.

NOTE: Each time you click Display Terrain the display changes between terrain view and non terrain view.

To recreate the display from a different Digital Terrain Map (DTM) using the window found in The Height Map Preview window, do this step:

Press <Ctrl> + Display Terrain from Display floating icons bar. The Height Map Preview window is displayed.

3.4.2 Add Building PolygonsThe building polygons layer is the most important add on to the Geographic Information Systems (GIS) layer. This is because it has a significant influence on the Radio Frequency (RF) footprint. Buildings diffract and reflect the Radio Frequency (RF) rays outside the buildings and cage the indoor cells transmission. Statistics show that about 70-80% of network traffic is generated inside buildings. To add building polygons, do these steps:

1. Select File > Open from the menu bar. The Open window is displayed.

2. Navigate to the source files, select the Buildings tab and click Open.

3. Click F2. The Browse Table window is displayed.

4. Select the Buildings polygon table. The Buildings polygon table is displayed.

NOTE: Make sure that the Building Unique ID is defined as an integer.

To create the buildings polygon database, do these steps:

1. Select Analysis > Database > Add Buildings Polygons into DTM. The Create Buildings Polygons Database window is displayed.

2. Select parameters from each list as described in Table 3-19.

Table 3-19: Create Buildings Polygons Database Selection Parameters

Setting Value

Source Table Select Buildings polygons table.

Get Polygon ID from Assign the unique Buildings Polygons ID

Note: This must be an integer

Get Polygon height from Select Height

Height method There are two options:

Page 22 of 77

NICE Optimize


Setting Value

Absolute height is above the sea level height ( Building Height+ DTM Height)

Above DTM contains just the Building Height ( Absolute Height – DTM Height)

3. Click OK. This process can run for several minutes. When the process is complete:

a) A process report is generated named ImportBuildingsReport.txt and stored in the map folder under the DTM folder.

b) New files are added to the DTM folder within the source files directory with the Polygons extension. This means that the DTM contains the Building polygons layer.

3.4.3 2D DisplayThe best method to check the Digital Terrain Map (DTM) build process is to display it with the 2D display option in the Path Profile Display. To display the path profile between two points, do these steps:

1. Click Display Path Profile in the Display floating icons bar.

2. Click one point on the map and drag to another point. The Path Profile window is displayed which shows the GIS items, such as Terrain, Clutters, and Buildings between these two points.

NOTE: If the Digital Terrain Map (DTM) or Buildings are not shown, verify map projections have the same coordinates as the projects initial setup, and then repeat steps from Create Digital Terrain Map Tiles 3.4.1.

3.4.4 Add RoadsThe Roads layer must also be added to the Digital Terrain Map (DTM) for further accurate coverage analysis. To add roads, do these steps:

1. Click F2. The Browse tables window is displayed.

2. Select the Basic Layer and click OK. The Roads table (defined as BasicLayer) is displayed.

NOTE: Make sure that the Roads ID unique identifier is defined as an integer.

To create the roads database, do these steps:

1. Select Analysis > Database > Add Road Lines into DTM. The Create Roads Database window is displayed as shown in Figure 3-16.

2. Select each parameter from the list as necessary.

Page 23 of 77

NICE Optimize


Figure 3-16: Create Roads Database Window

3. Click OK. The process can run for several minutes. On completion:

a) A process report is generated named ImportRoadsReport.txt and stored in the map folder under the DTM folder.

b) New files are added to the DTM folder within the source files directory with the roads extension. This means that the DTM contains the roads layer.

The Digital Terrain Map (DTM) now contains all available Geographic Information Systems (GIS) layers. The next step is Network configurations import.

3.5 Import NetworkThe import network section contains three imports:

Import Antenna: Contains the physical, logical parameters of the antenna, cell, and site. The file is based on an antenna property. Each antenna has a separate row.

Import Radio: Contains the radio configurations such as: Channel and used MAL.

Import Adjacent: Contains the Handover relations between two cells.

3.5.1 Import AntennaTo import an antenna, do these steps:

1. Select Project > Site Sector Radios > Import Network Antennas from the menu bar. When the import is successful, two results occur:

– The Import Antennas succeeded window is displayed.

– An import report named ImpAntReport_GSM_1800 and a log file named ImpAntLog_GSM_1800 is stored under the project\report folder.

Page 24 of 77

NICE Optimize


2. Click Apply. The imported elements are assigned in the database (site, sector, antenna tables). This process creates four new identities:

– Site

– Sector

– Radio

– Antenna

The sites and sectors are displayed in the main window as shown in Figure 3-17.

Figure 3-17: Sites and Sectors

These identities are MapInfo tables stored in the project folder. To view the data, do these steps:

1. Select the F2 hotkey. The Browse Table window is displayed.

2. Select one of the identities and click OK.

WARNING: Any changes in the tables Site, Sector, Antenna, and Radio are saved and can damage the projects structure.

To edit or view the configuration of a site, do these steps:

1. Click Edit a Site from the Edit floating icons bar and click any site from the map. The Sites window is displayed which shows site configurations.

2. Change parameters as necessary and click OK.

NOTE: The Find menu enables a user to search for any Site or Cell by Sector Name, Site Name, Cellid, Address, Sector Code and SC (PCI, BCCH – BSIC combination.

Page 25 of 77

NICE Optimize


3.5.1.1 Import Antenna Bound by Polygon and Coordinates Conversion

When an import antenna file contains site coordinates in decimal Longitude, Latitude, or WGS 84 format it can be imported without conversion with the ImportAntenna.ini file. The ImportAntenna.ini file can be used to define polygon borders and limit project sites to a specific area. The ImportAntenna.ini file is shown in Table 3-20.

Table 3-20: ImportAntenna.ini File

Setting Value

[Convert Method] Header

Convert Coordinates 0: No coordinates conversion

1: Converts Dec degrees to UTM WGS 84

2: Converts Dec degrees to Israel Old

3: Converts Dec degrees to Israel New

4: Israel Old to UTM wgs84 36N

UTM Zone Defines the UTM projects zone

UTM North 1: North

2: South

[Import Defaults] Header

Ignore small changes XY(define min changes) Defines in meters the min range to ignore site coordinates changes

Do not report site name changes 1: Do not report site name changes

0: Reports site name changes

Do not report site color changes 1: Do not report site color changes

0: Report site color changes

[Filter by polygon] Header

X<tab>Y

X<tab>Y

X<tab>Y

X, Y coordinates of the required bounding polygon

NOTE: The ImportAntenna.ini file is in the projects folder. This must be found before the import phase.

3.5.2 Scrambling Code\PCI Map ViewTo display cells Scrambling Code for Universal Mobile Telecommunications System (UMTS) or Physical Cell identifier, (PCI) for LTE projects, do these steps:

1. Select Display Scrambling Code\PCI from the Display floating icon bar. The Display dialog window is displayed.

2. Select the necessary Scrambling Code\PCI value to show on map.

3. Click OK. The Sites and Sectors map is updated to display the selected sector channels as shown in Figure 3-18.

Page 26 of 77

NICE Optimize


Figure 3-18: Map Displaying Cell Scrambling Code\PCI

To clear the cells display, do this step:

Click Scrambling Code\PCI from the Display floating icon bar.

NOTE: To show the Scrambling Code\PCI map for different carriers or technologies change the default technology option for the necessary view in the Technology Editor property.

3.5.3 Import Radio (GSM Only)To import a radio, do these steps:

1. Select Project > Site Sector Radios > Import Network Radios from the tool bar. The Import Radios window is displayed.

2. Navigate to the source folder and select the radio import file.

3. Click Open. When import is successful, the results shown are:

a) A confirmation window is displayed.

b) An import report named ImpRadReport_GSM_1800 and a log file named ImpRadLog_GSM_1800 are stored in the project\report folder.

4. Click Apply. The imported elements are assigned in the network database (table Radio).

Page 27 of 77

NICE Optimize


When the network radios are assigned with valid channels, the project frequency bands must be updated. To update the project frequency bands, do these steps:

1. Select Project > Site Sector Radios > Update Frequencies from Radio from the menu bar. When the update is successful, a confirmation window is displayed.

2. Click Apply. The results shown are:

a) An import report named FreqEditReport_GSM_1800 and a log file FreqEditLog_GSM_1800 are stored in the project\report folder.

b) The frequency list is assigned in the projects database (FrequencyList.txt).

To view the frequency list, do these steps:

1. Select Project and Technology Editor from the menu bar. The Project Editor is displayed.

2. Select Technology from the menu on the left side. Click the grey square next to Base Frequency, shown in Figure 3-19. The Frequencies Editor is displayed with project frequency settings. Changes to the project frequencies assignment are done with this window.

NOTE: You can also select the Project and Technology Editor with the Edit floating icon bar.

Figure 3-19: Project Editor

Page 28 of 77

NICE Optimize


To display Sector channels, do these steps:

1. Select Display Frequencies from the Display floating icon bar. The Display Frequencies window is displayed.

2. Select one of these display options:

– All Carriers

– Single Carrier

– Single Carrier with specific BSIC

3. Click OK. The Sites and Sectors map is updated to display the selected sector channels as shown in Figure 3-20.

Figure 3-20: Map Displaying Sector Channels

To clear the carriers display, do this step:

Click Display Frequencies from the Display floating icon bar.

3.5.4 Import AdjacentTo import MapInfo tables, called Adjacents, do these steps:

1. Select Project > Site Sector Radios > Import Adjacent List from the menu bar. This imports the new MapInfo tables called Adjacents into the project folder. The Import Adjacent List window is displayed.

2. Navigate to the Source directory, select the Adjacent import file and click Open.

3. Click Display Adjacents from the Analysis floating icon bar and select a specific sector from the Sectors Map. The Adjacents Display window is displayed.

4. Select from among the options described in Table 3-21.

Page 29 of 77

NICE Optimize


5. Click OK. The Adjacents MapInfo tables are imported. The Sectors Map changes to show the Adjacent sectors as shown in Figure 3-21.

Table 3-21: Adjacents Display Window Options

Option Description

Adjacent Technology Select technologies for adjacent sectors display as necessary.

Note: This applies to projects with multiple technologies.

Direction The options are:

Outgoing adjacent relations

Incoming adjacent relation

Both incoming and outgoing

Color sector by Colors the sector shape. The options include:

Network attempts (only if imported)

Predictions values

Note: the unit is selectable. The options are

Absolute

Percentage

Rank (of the relation)

Color spider by The options include:

Source: Relation from the network or from prediction or both network and prediction.

Technology Predicted: Colored by technology type is taken from the predicted adjacent analysis (if calculated).

Technology Network: Colored by technology type is taken from the network adjacent (if imported).

Recommendations: Pre-processed option to optimize adjacent list based on prediction (not supported).

Page 30 of 77

NICE Optimize


Figure 3-21: Adjacents Display

3.5.5 Site DialogTo access the Site Dialog window, do these steps:

1. Click Edit a Site from the Edit floating bar.

2. Click a Site property. The Site Dialog window is displayed. The Site Dialog window is shown in Figure 3-22 and the Site Dialog is described in Table 3-22.

Figure 3-22: Site Dialog Window

Page 31 of 77

NICE Optimize


Table 3-22: Site Dialog Window Description

Section Description

Top Left Specifies Site information Name, X, Y, MNC, RNC, Address, Site Ground Height, Max Pole Height, Building Height (if exists), Analysis Range in Km for the coverage analysis

Top Center The options include:

Highest Location: Finds the highest location in radios used in rural areas where the exact installation coordinates are not known.

Zoom Location: Each antenna property or the entire site can be moved to the correct installation point. To zoom location, do this step:

– Select the necessary property. Click on the correct installation point on the map.

Album : Site pictures album

Top Right Table fields contain four predefined fields as well as fields which can be created by the user at the import phase. To create extra user fields at import use the prefix SIT_ option:

Site Id

Last Modify: Date of last modifications

Color: Site Color, click to change Sites color

Visible: Checked, invisible uncheck

Antennas azimuths:

Left arrow moves all antennas clockwise by 1deg

Right arrow moves all antennas anticlockwise by 1deg

Round arrow moves all antennas clockwise by desired degrees

Sectors The options are:

Technology Type selection

Technology selection: All carriers view or specific carrier view

Sector: Display all Sectors or specific one

Right Arrow: Add new Sector

Left Arrow: Delete a Sector

Play Button: Copy certain value to all Sectors

Main Window: Sectors parameters displayed

Antennas Right Arrow: Add new Antenna

Left Arrow: Delete Antenna

Play Button: Copy certain value to all Antennas

Main Window: Antenna Properties

Radios Right Arrow: Add new Radio

Left Arrow: Delete Radio

Play Button: Copy certain value to all Radios

Main Window: Antenna Properties

OK

Delete

Cancel

Saves all done manual changes

Delete the entire Site

Nothing had changed

NOTE: It is recommended to use Zoom Location for all building installed sites which use different antenna positions. This maximizes coverage analysis accuracy by locating the antennas in their actual installed locations. This process is done by using a local RF engineer, Google earth, or Asmade database.

Page 32 of 77

NICE Optimize


An example of before and after the Antenna Alignment, is shown in Figure 3-23.

Figure 3-23: Before and After Antenna Alignment

3.5.6 Move Antennas to Buildings EdgeThe Move Antenna to Building Edge feature lets the user select specific cells which automatically change their installation location to building edges. This is done when accurate coverage analysis is necessary. It should be done as a last option if no relevant information is displayed. To move antennas to the buildings edge, do these steps:

1. Select MapInfo Selection and create a list of the cells as shown in Figure 3-24.

Figure 3-24: Sectors Selection

2. Select Project > Site Sector Radios > Move Antennas to Buildings Edge. The Move Antennas to Building Edge window is displayed.

3. Select Installation method. The Installation Methods window is displayed. The options are described in Table 3-23

Page 33 of 77

NICE Optimize


Table 3-23: Installtion Methods

Option Description

Move antennas to building corners: Find building edge according to building Contour: The buildings edges are found by the building shape.

Find building edge according to changes in the Heights: The preferred option if the buildings database contains several polygons in certain building positions with different heights.

Maximum building width Maximum search radios for the building edge

Use rooftop includes: Roof top installation: The antenna always moves to the corner of the building as rooftop installation (with the Additional roof height parameter stated)

Buildings wall installations: Keeps the current antenna height, even if it is less than buildings height.

4. Select Start to activate the procedure. An example of the before and after the Antennas are moved to the Corners is displayed in Figure 3-25.

Figure 3-25: Before and After Antennas Moved to the Corners

Page 34 of 77

NICE Optimize


4 CoverageThe coverage analysis provides the Radio Frequency (RF) footprint for the area, roads and buildings with a predefined resolution. It is important to provide accurate coverage, similar to the real Radio Frequency (RF) propagation as possible. This is because location based Radio Frequency (RF) is performed with the real measurement reports. When the mobile users are found, monitoring and optimization is based on that database.

NOTE: Some wideband projects (UMTS and LTE) contain different carriers for each band. It is recommended to name multiple technology properties, technology_carrier. This way the coverage database contains more detailed information for each carrier. The coverage database consists of up to 40 best RSSs in each geographical bin. By splitting the coverage database for example two technologies (UMTS_2100_f1, UMTS_2100_f2) makes 80 best RSSs (40 RSSs for each technology).

4.1 Create Coverage DatabaseTo create the coverage database, do these steps:

1. Select Project > Layers > Create Display Polygons Layer from the menu bar. A window is displayed that confirms that the New Display Polygons Table is created and ready to add Polygons with MapInfo tools. This creates a polygon to define coverage boundaries.

2. Click OK. The drawing tool icons are now enabled on the icons bar.

3. Click the Polygon icon and create a polygon on the map as shown in Figure 4-26.

Figure 4-26: Polygon Drawn Around Map

Page 35 of 77

NICE Optimize


NOTE: To complete the polygon, double click the last node.

4. Click F2. The Browse Table window is displayed.

5. Select the DisplayPoly from the list and click OK. The DisplayPoly table is displayed.

6. Enter a name for the new polygon in the Name field.

7. Select Analysis > Coverage > Create Coverage Database from the Menu bar. The Create Coverage Database window is displayed.

8. Select these parameters:

– Boundaries Table: Display Poly

– Specific Regions Table: Unknown

9. Click OK. The Create Coverage Database window is displayed as shown in Figure 4-27.

10. Select a Project Technology from the left window. Select from the definable configuration settings in the right window as described in Table 4-24.

11. Click OK. A new project folder called CA_GSM_1800, is created which stores the coverage calculations.

NOTE: The coverage folder must contain *.cvr, *.cbl, and *.crd files. cvr = area coverage, cbl = building coverage, and crd = roads coverage.

Figure 4-27: Create Coverage Database Window

Page 36 of 77

NICE Optimize


Table 4-24: Create Coverage Database Settings

Setting Description

Defaults MS height (m): The height of the mobile user on top of the GIS layer.

Resolution (m): Area resolution for the coverage. For example, a resolution of 50 means the coverage is calculated at 50 meter intervals.

Max Tile Dimension (m): The whole coverage database is divided into this value for duration and space purposes.

Antenna name The antenna type to use for the mobile user reception.

Create Building Coverage

Vertical resolution (m): Building vertical resolution for coverage calculations. For example, a resolution of 3 means the coverage is calculated at 3 meter intervals on each building.

Envelop gap (meters): Buildings perimeter coverage calculation. For example, a gap of 1 means the coverage is calculated at 1 meter intervals on each building for each vertical resolution.

Create Roads Coverage: Resolution: Road resolution for the coverage. For example, a resolution of 10 means the coverage is calculated at 10 meter intervals in the road layers.

NOTE: In multi technology or band projects, set the parameters for all technologies or bands.

4.2 Coverage Analysis SetupBefore coverage analysis, it is necessary to do these two steps:

Configure specific parameters

Select sectors for coverage

4.2.1 Configure Specific ParametersTo configure the parameters, do these steps:

1. Select Project > Project and Technology Editor from the menu bar. The Project Editor is displayed as shown in Figure 4-28.

2. Select Propagation from the menu on the left side and click the Propagation model name, for example Hexagon 3D B as shown in Figure 4-28. The Propagation Models window is displayed.

3. Select Hexagon 3D B from the Generic propagation model list and click OK.

NOTE: This model is a simplified Ray-Tracing model that provides accurate results for an urban area.

Page 37 of 77

NICE Optimize


Figure 4-28: Project Editor Window

4. Click Clutters from the left side menu in the Project Editor window. The Clutters list table is displayed.

5. Click Get DTM Clutters to display the Clutter Names and Click OK. The Clutter names are now stored.

6. Select Project > Project and Technology Editor from the menu bar. The Project Editor is displayed as shown in Figure 4-29.

7. Click the grey square under the Technology column next to GSM_1800. The Technology configuration setting is displayed.

Page 38 of 77

NICE Optimize


Figure 4-29: Project and Technology Editor

8. Make sure Max analysis range (m) is 60000.

NOTE: Max analysis range (m) sets the maximum limit for coverage analysis per sector. In this example the range is set not to exceed 60km.

9. Click Clutters from the left side menu in the Technology Editor window. The Clutter List table is displayed as shown in Figure 4-30.

10. Enter 27 in the BPL (building penetration loss) dB column for each Clutter Name row as shown in Figure 4-30.

11. Click Apply and click OK.

12. Click OK to close the Project Editor window.

Page 39 of 77

NICE Optimize


Figure 4-30: Clutters List Table

4.2.2 Select Sectors for CoverageCoverage Analysis is applied to sectors. This means that is necessary to select those sectors to be applied for the Coverage. To select the sectors to be applied, do these steps:

1. Select Map > Layer Control from the Menu bar. The Layer Control window is displayed.

2. Select the Visible and Selectable options for the Sectors layer.

3. Click Up in the Reorder group to move this sector to the top of the list and click OK.

NOTE: Make sure the Sectors layer is below the Cosmetic Layer.

4. Click Polygon Select on the MapInfo menu bar and create a polygon around all the sectors. All Sector shapes become marked which means they are selected.

NOTE: Double click the last node to close the polygon.

5. Click Add Selected Cells to List from the Analysis floating icon bar. A sector list for the Coverage analysis is now created as shown in Figure 4-31.

6. Click OK and click Calculate Coverage from the Analysis floating icon bar. The Coverage Analysis window is displayed as shown in Figure 4-32.

Page 40 of 77

NICE Optimize


Figure 4-31: Sector Selection List Window

Figure 4-32: Coverage Analysis Window

IMPORTANT: Make sure no errors are found and the correct number of sectors is displayed. The Default Model is the one previously selected.

4.3 Calculate Coverage by HostThe first coverage analysis for a new project must contain all the cells. For large projects this process can take some time, depending on the area to cover, coverage resolution, Digital Terrain Map (DTM) resolution and the amount of cells. The Calculate Coverage by Host operation is actually a Central Processing Unit (CPU) sharing capability. This lets several machines be used at the same time to process coverage calculations by splitting the Coverage task into small coverage tasks.

Page 41 of 77

NICE Optimize


4.3.1 Sharing DirectoriesTo share a directory, do these steps:

1. Create a new folder to store the calculated small coverage tasks

– For example C:\Projects\Common.

2. Configure this folder as shared with full (Read\Write) access.

NOTE: It is recommended to create this folder on the main machine.

3. Configure the NES installation folder and the Project folder with shared (preferably full access).

4. Try to access each of these folders by using their network path. If this is not available, repeat the sharing process using the Windows sharing options.

4.3.2 Create Host TaskTo create the host task, do these steps:

1. Click Edit Cells List from the Analysis floating icon bar. The Sectors Selection window is displayed.

2. Make sure that specific cells have already been selected for coverage.

3. Click Calculate Coverage by Hosts from the Analysis floating icon bar. The Export to Hosts window is displayed as shown in Figure 4-33.

NOTE: The Calculate Coverage by Hosts feature applies to the default technology cells only. In multi technology projects you must create a second job by selecting second technology cells and defining their technology as default in the Project and Technology Editor.

Figure 4-33: Calculate Coverage by Hosts

Page 42 of 77

NICE Optimize


4. Type and select the options, and confirm the settings as described in Table 4-25.

5. Click OK. A Confirmation window is displayed when The Export task to NES host completes successfully.

6. Select Analysis > Coverage > Display Host Status from the menu bar. The Host Task Status window is displayed as shown in Figure 4-34.

Table 4-25: The Calculate Coverage by Hosts Settings

Item Description

Details Troubleshoots the network, if errors occur cancel the process and fix the errors.

Task Name Sets a name for the Coverage Analysis.

Note: Any task must have a unique name.

Local Project Path Shows the local path of the project.

Project network path Configures a network path to the projects folder.

Terrain (3D Layer) There are two options:

Selected: Makes all the hosts use a local copy of the DTM. Note: it is recommended to copy the Digital Terrain Map (DTM) to each hosting machine.

Unselected: Navigate to the DTMIndex.txt file as created in section 3.4 and click Open. This inserts the DTM network path for each of the Hosts for auto copy. Note: Make sure that the DTM folder is shared when using this option.

Hosts Common Folder Sets the network path to the Common folder.

Note: This folder stores the results of the coverage calculated by each of the host machines.

Technology Shows the technology that the coverage operates on.

Default Model Shows the default propagation model for the coverage calculations.

Layers All layers are calculated by default unless a specific layer is unselected.

Maximum points for job The quantity of coverage points for each small task.

Figure 4-34: Host Tasks Status Window

The Host Tasks Status is ready for calculations. To use this window, do these steps:

Double click the task to view the progress of the task, coverage calculations statistical information and connected Hosts.

Right click the task to refresh, reset, export to txt or delete it.

Page 43 of 77

NICE Optimize


4.3.3 Activate HostsAny computer connected to the main computer network can help process the task created in section 4.3.2, and run the host installation on the host computers. To activate the host computer, do these steps:

1. Type Regedit in the run box. Set RegEdit:

a) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NES Planning Tool\NESHost\ ServerAppPath. Insert the network path to the NES installation folder from which the work had been created.

b) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NES Planning Tool\NESHost\TerrainFN. Type the local terrain path including the DTMIndex.txt.

2. Open the NES_Host application from the Desk Top or from the Maintenance and Host folder, in the C:/NES_M&H Host installation folder (application CTNESHostApp.exe). The NES Host window is displayed as shown in Figure 4-35.

3. Select the Active option. The Host parameters are now configured and the Calculate Coverage by Hosts process is operational.

4. (Optional). Repeat steps 1 to 3 for other host machines.

Figure 4-35: NESHost Configuration Window

NOTE: When the DTM is sent by the NES application described in section 4.3.2, it is not necessary to update the registry through Regedit with the DTM path.

Host job operations are described in Table 4-26.

Table 4-26: Host Job Operations

Operation Description

To view the coverage process and get Click Display Host Status and double click on the

Page 44 of 77

NICE Optimize


Operation Description

the duration to completion recent job

To edit a Host job from the NES application

1. Select Analysis > Coverage > Display Host Status

2. Right click the job and select Delete or Refresh

4.3.4 Update Coverage from HostsWhen the process described in section 4.3.3 is complete, the coverage database must be updated with the new coverage calculated by the Hosts.

IMPORTANT: Before you update coverage from hosts, Coverage Analysis by Hosts calculates each host task found in order, for example job 1, followed by job 2 and so on. When a specific job is no longer necessary, it is recommended to delete it from the application through the Host Tasks Status window, so that the application can process the necessary jobs.

To update the coverage database from hosts, do this step:

1. Select Analysis > Coverage > Update Coverage from Hosts.

2. Select the proper completed job.

4.3.5 Display Coverage GSMThe coverage analysis is viewed by displaying and testing the coverage results. To display the coverage results, for the GSM network do these steps:

1. Click Display Coverage Results from the Display floating icon bar. The Display Coverage Results window is displayed as shown in Figure 4-36.

Figure 4-36: Display Coverage Results Window

2. Select options as necessary, described in Table 4-27 thru Table 4-29.

Page 45 of 77

NICE Optimize


3. Click OK. A new color sector map showing coverage and an accompanying legend is displayed with colors as shown in Figure 4-37.

NOTE: The Display Coverage Results window is divided into three parts: left, middle and right. The left part of the window displays the selected sectors in the cell list. There are three options for sector display as described in Table 4-27. The middle part of the window displays the results list group options. These include the options described in Table 4-28. The right part of the window contains the settings described in Table 4-29.

Table 4-27: Sector Group Options

Setting Description

Use Inactive Sectors

Displays coverage including inactive sectors.

Use Selection Sectors List

Displays coverage of sectors from the Cell List.

Note: When this option is not selected, coverage of all sectors is displayed.

Pack List Displays the best effort in terms of coverage When the best covering cell is not in the list but the second best cell is part of the list and the Pack List option is selected, the bin is colored with the second best cells coverage strength. When the Pack List option is not selected, the bin is not colored.

Table 4-28: Results List Group Options

Setting Description

Best RSS Provides the RSSI of the best cell in each bin.

RSS Provides the Nth cells RSSI value (up to the 40th cell).

Cell Rank Provides the rank of the selected cells in a certain margin from the best cell in each bin.

Table 4-29: Right Side Window Options

Setting Description

Coverage Layer Changes the display between the coverage layers (that is, area, buildings or roads).

Advance Provides the capability to change the legend to a certain display (temporary legend change).

Export data to MIF Saves the display for future use.

Page 46 of 77

NICE Optimize


Figure 4-37: Display Coverage Map

To display coverage information for any point on the map, do this step:

Click Display Coverage Point Info from the Display analysis floating icon bar and select any point on the map. The Coverage Info window is displayed for that point on the map.

4.3.6 Display Coverage UMTSThe coverage analysis can be examined by displaying and testing the coverage results. To view coverage results for the Universal Mobile Telecommunications System (UMTS) network, do these steps:

1. Select Project > Project and Technology Editor from the menu bar.

2. Click Technology. Select a UMTS technology and click OK.

3. Click Display Coverage Results from the Display floating icon bar. The Display Coverage Results window is displayed as shown in Figure 4-38.

NOTE: If the DisplayPoly is opened and contains polygons the next option is to select the coverage map boundaries.

Page 47 of 77

NICE Optimize


Figure 4-38: Display Coverage Results

4. Select options as necessary, described in Table 4-30 thru Table 4-32.

5. Click OK. The map and legend are displayed as shown in Figure 4-39.

Table 4-30: Sector Group Options

Setting Description

Use Inactive Sectors

Displays coverage including inactive sectors.

Use Selection Sectors List

Displays coverage of sectors from the Cell List.

Note: When this option is not selected, coverage of all sectors is displayed.

Pack List Displays the best effort in terms of coverage When the best covering cell is not in the list but the second best cell is part of the list and the Pack List option is selected, the bin is colored with the second best cells coverage strength. When the Pack List option is not selected, the bin is not colored.

Table 4-31: Results List Group Options

Setting Description

Best RSCP Provides the Received Signal Code Power (RSCP) of the best cell in each bin.

RSCP Provides the Nth cells Received Signal Code Power (RSCP) value in each bin (up to the 40th cell).

Cell Rank Provides the rank of the selected cells in a certain margin from the best cell in each bin.

Num of Servers Number of Cells or Sites in each bin up to a certain Received Signal Code Power (RSCP) criteria and range from the Best Cell.

Num of Neighbours

same as Num of Servers but the Best Cell

Neighbours Shows the coverage relations between two cells

Connection Mapped by best cell

Page 48 of 77

NICE Optimize


Setting Description

Remove All delete all coverage maps

Table 4-32: Right Side Window Options

Setting Description

Coverage Layer Changes the display between the coverage layers (that is, area, buildings or roads).

Advance Provides the capability to change the legend to a certain display (temporary legend change).

Export data to MIF Saves the display for future use.

Figure 4-39: RSCP Map of UMTS_2100_f1

Page 49 of 77

NICE Optimize


4.4 Hawk DatabaseThe HawkDB is a separate structure to hold the coverage database. Instead of storing the coverage results per bin (that is, area, building or road) as is done in the coverage database, the HawkDB stores the coverage results for each sector and includes additional information about sectors, configurations and adjacents. This new method of coverage storing enhances the process of geo location by searching for the most suitable point to put each event. It does this through measurement reports which contain the sectors identity and their measurements as reported by the mobile unit.

To create the HawkDB, do these steps:

1. Select Analysis > Coverage > Create HAWK Database. The Create Hawk Database is displayed as shown as Figure 4-40.

2. Select settings from the Options group as described in Table 4-33.

3. Click Next. The time taken to complete the process can vary and depends on the quantity of cells and coverage dimensions. A HAWKDB folder is created inside the projects folder.

Figure 4-40: Create HAWK Database

NOTE: The Selected Sectors list displays the sectors in the cell list. The HawkDB has been designed to examine the coverage database regardless of the selected sectors.

Table 4-33: Create Hawk Database Window Settings

Setting Description

Create fast coverage database

When selected, creates the coverage database for each sector.

Create fast assign table When selected, it creates a fast assign table to speed up the location process.

Parameter Includes fast coverage and fast assign configurations.

Page 50 of 77

NICE Optimize


5 UMTS Parsing and LocationThis chapter describes the process used to collect data from the network, parse the data and then geo locate it. The parsing and geo location output is used to create monitoring maps and optimization.

5.1 Data CollectionData collection is done from these vendors:

NSN: From Nokia Megamon, though the GeoClient application

Ericson: From General Performance Event Handler (GPEH) files, taken from the Ericsson Probe

Huawei: With a soft probe

NOTE: Huawei is not described in this document

5.1.1 Data Collection from Nokia MegamonData collection from Nokia Megamon is done with the Geoclient application installed on the Megamon server.

5.1.1.1 Emil and Megamon Filter Verification

To confirm the Megamon filter is correct, do this step:

SR:((OFAM=4FD,507,508,509,997,0A49)AND(NUM=0A5EE,094E8,0A75B,0A5F4,094E7,0A8E8,0CA1,0CD6,0DAD0,0DACE,2070,6836,8515,952A,952B,9AAD,0A2BE,0A6D9,0A71C,0A7AF,0A9B8,0C465,0C466,0C6DD,0D330,0D331,0D7B6,0D7B5,0D332,0D333,0D334,0D335,0D336,0D4C0,0D4CD,0D4DD,0D5B6,0D5B7,0D5DD,0D5DE,0D6E5,0D6E6,0D87C,0D87E,0D8A7,0D8A8,0D8AA,0D8AB,0D9DA))

NOTE: The Megamon filter was used in Paris and Optus, but must be validated by Nokia

To confirm the Emil filter is correct make sure version 3.1.66.138 is installed.

5.1.1.2 Geoclient Configuration

When the Geoclient is installed to the server the NSNAdaptor.properties is configured, to configure the properties do these steps:

1. Navigate to the Geoclient installation directory.

2. Right Click NSNAdaptor.properties, Select Open with Notepad

3. Confirm these configurations are shown:

## NSN Emil Address

NSN_HOST_ADDRESS = 172.18.136.159

Page 51 of 77

NICE Optimize


NOTE: This IP represents Megamon Geo interface IP

## NSN Emil Port

NSN_HOST_PORT = 12345

NOTE: This Port represents Megamon Geo interface port

4. Click GeoClientWatchDog.exe

Once the connection of the GeoClient and Megamon interface is made, these files are created:

Collected Data in CSV Format: <GeoClient directory> \<data>\<RNC_name>\data

Log Files: <GeoClient directory> \<data>\<RNC_name>\log

5.1.1.3 GeoClient Output Collection

All csv and log files are transferred for post processing in the back office. This is done with external disks from the field and copied into a local folder.

5.1.2 Data Collection from Ericsson ProbeGeneral Performance Event Handler (GPEH) files are transferred for post processing in the back office. This is done with external disks from the field and copied into a local folder.

5.1.3 Data Collection from HuaweiTBD

5.2 ParsingWhen the data has been collected it is parsed. This is done with two applications depending on the source of the collected data:

PAR: For GPEH files collected from the Ericsson probe

GenTextParser: For csv files collected from Nokia Megamon

The parse output from both applications are binary files called EventDB. This is used as the input for the Geolocation engine.

5.2.1 PARWhen PAR is installed on the server, these actions must be done:

Confirm .NET 4 is installed

PAR is configured

IMPORTANT: Only .NET 4 will work not any higher versions

To confirm .NET 4 is installed, do these steps:

1. Open Regedit

Page 52 of 77

NICE Optimize


2. Navigate to registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full

3. Confirm DWORD value Release is present. This means .NET Framework 4 is installed.

To configure PAR, do these steps:

1. Navigate to the PAR directory.

2. Right Click ParCli.exe.cfg. Select Open with Notepad

3. Enter these configurations:

– To point to the Log file location:

<file value="C:\temp\PAR_GLE\ParCli\ParserApp.log" />

– To point to the Parsing configuration file

<add key="settingsFile" value="C:\temp\PAR_GLE\Config\GpehParsingService.xml" />

4. Click Save

5. Navigate to SettingEditor.exe. Double click SettingEditor.exe.The Settings Editor window is displayed.

6. Navigate to GpehParsingService.xml from the Settings File pane.

7. Enter these configurations:

– To point to the HAWKDBPublish directory

<HawkDbDirectory>R:\Projects\Cellcom_Opt\HAWK3GDBPublish</HawkDbDirectory>

– To point to the parsing home directory file

<ParserHomeDirectory>C:\temp\PAR_GLE\ParCli</ParserHomeDirectory>

– To point to the GPEH file location as an input directory

<InputRepository>R:\Users\Tatiana\Src_Prj_Optimization\GPEH_Old\4RNCs_3Hours</InputRepository>

– To point to the output directory, where EventDB is created

<OutputRepository>C:\temp\PAR_GLE\data</OutputRepository>

– To point to the lock file location

<LockFilePath>C:\temp\PAR_GLE\locfiles\GpehProcessingLockFile.bin</LockFilePath>

8. Click Save

NOTE: The lock file contains information about all the processed GPEH files. If the files need to be reprocessed, the lock file must be deleted.

9. Verify that Netconfig does not contain tilt and etilt columns. To do this, Open Netconfig in excel, and delete the columns if they are shown.

Page 53 of 77

NICE Optimize


When parsing is complete the EventDB files must be defined as an input for the GeoLocation engine (GLE).

5.2.2 GenTextParserTo configure GenTextParser, do these steps:

1. Navigate of the location the GenTextParser.

2. Right Click RunGenTextParse.cmd. Select Open with Notepad

3. Make sure these configurations are entered:

– Add this line if it is not there after the line, ECHO Start GenTextParse. This must point to the Borland dlls, that are delivered as part of the GenTextParser.

PATH=%PATH%;C:\Training\GenTextParser_18\System32;C:\Training\GenTextParser_18\System32\BCB2006

– Make sure the Input directory is:

---rpp = (C:\Training\GenTextinput\ - )

The Input directory must contain only the folder with the Radio Network Controller (RNC) name, as it is in the csv collected data. For examples file names are 22RR_ORNC00_01JUN2014_0000.csv. The folder name contains all files and must be in C:\Training\GenTextinput\22RR_ORNC00.

– Make sure the log file is shown as:

--lp=C:\Training\GenTextParser_18\logs

– Make sure the project is shown as:

--np = C:\Projects\Bondi project\NirProject.nir

NOTE: GenTextParser looks for HAWK3GDB (not for HAWK3GDB_publish directory )

– Make sure the AUC file is shown as:

--auc = C:\Training\AUC\AUC_bondi88.txt

IMPORTANT: Make sure no other parameters are changed, as it affects the time to process data and can crash the Gentext parser

4. Click Save

5. Do these checks:

– Check there is a connection to the NES project. To do this, type the full path to the folder from the Run Box/Search bar to make sure there is a connection.

– Make sure that Netconfig (located in the project directory under HAWK3GDB folder) does not contain tilt and etilt columns (delete them if needed ). To do this, Open Netconfig in excel and delete the columns.

– Make sure that HAWK DB is located under HAWKDB folder directly

– Make sure that input directory name is a Radio Network Controller (RNC) name. It must be the same name as the RncNetConfig3G.csv. To make it is correct check in the csv files. The csv files are located in the HAWK3GDB directory.

Page 54 of 77

NICE Optimize


– Make sure that both the Microsoft Visual C++ 2010 Redistributable Package (x86) and Microsoft Visual C++ 2010 Redistributable Package (x64) are installed.

6. Double click RunGenTextParse.cmd.

7. The EventDB files, which are the GenTextParsers output is created in the project folder, called EventsDB_Formatter.

5.3 GeoLocatingGeoLocation is done on the EventDB files which are created by one of the parsers (PAR or GenTextParser). The Geo Location Engine (GLE) uses this file as an input and adds locations (X, Y, Z) to each of the events that exist in this file.

Geo Location Engine (GLE) has two configuration files. One is configured with settingEditor.exe which is in the GLE folder under tools and the other using a notepad editor. To configure these files, do these steps:

1. Navigate of the location the GleCli.exe.config

2. Right Click GleCli.exe.config. Select Open with Notepad

3. Make sure these configurations are entered:

– This configuration directs to the main configuration file, (for example above LocationServiceSettings_paris.xml"/> )

<add key="settingsFile" value="d:\Data\GLE_3.9.5\SETTINGS_PAR_GLE\LocationServiceSettings_NEW.xml"/>

4. Click Save.

5. Navigate to SettingEditor.exe. Double click SettingEditor.exe.The Settings Editor window is displayed.

6. Navigate to LocationServiceSettings_NEW.xml from the Settings File pane.Enter the settings shown in Table 5-34.

Table 5-34: LocationServiceSettings_NEW.xml Configuration

Parameter Configuration Description

Input Repository D:\Data\EventsDB Non GeoLocated EventDB location

Lock File Path D:\Data\LocationRepositoryLockFile.bin GeoLocated EventDB location

Output Repository D:\Data\LocatedEventsDB

HawkDB Error Path D:\Data\HAWK3GDB\Errors

Hawk DB Path D:\Data\HAWK3GDB HAWKDB path is HAWK3DB_publish

Hawk Logs Directory D:\Data\HAWK3GDB

Temp Processing Folder D:\Data\Temp

7. Click Save

Page 55 of 77

NICE Optimize


The log4net dlls need to be copied to the GLE installation directory and global assembly. Before this the correct version of both dlls must be identified and downloaded. To download log4net.dll version 1.2.10.0, do these steps:

1. Download log4net.dll version 1.2.10.0 from: http://archive.apache.org/dist/incubator/log4net/1.2.10/

2. Select incubating-log4net-1.2.10.zip

3. Navigate to log4net-1.2.10\bin\net\2.0\release\

The log4net version 1.2.11 is included in the PAR / GLE distribution.To identify the dlls do these steps:

1. Navigate to the log4net.dll

2. Right click on the log4net.dll and select the properties. The property window is displayed

3. Select Details tab. The File Version is displayed

4. Copy log4net.dll, version 1.2.11.0 into the GLE directory

To register log4net.dll version 1.2.10.0 to the global assembly, do these steps:

1. Open Command Prompt as an Administrator. The Command Prompt window is displayed.

2. Type the command, to register log4net.dll

gacutil.exe /i log4net.dll

3. Type the command, to confirm log4net.dll was successfully registered

gacutil.exe /l log4net

4. If successful the output is:

Microsoft (R) .NET Global Assembly Cache Utility. Version 3.5.30729.1

Copyright (c) Microsoft Corporation. All rights reserved.

The Global Assembly Cache contains the following assemblies:

log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=1b44e1d426115821, processorArchitecture=MSIL

Number of items = 1

5. Download gdal version 1.9.0 from: http://trac.osgeo.org/gdal/wiki/DownloadingGdalBinaries

6. Press the Windows Key + Pause/Break. The Windows System Properties window is displayed.

7. Click Advanced system settings > Environment Variables. The Environment Variables window is displayed.

8. Click New System Variables. The New System Variable window is displayed.

Page 56 of 77

http://trac.osgeo.org/gdal/wiki/DownloadingGdalBinaries

http://archive.apache.org/dist/incubator/log4net/1.2.10/

NICE Optimize


9. Enter GDAL_DATA in the variable name field and the installation path in the Variable value.

10. Click OK.

11. Enter GDAL_DATA in the variable name field and the path to the GDAL bin folder in the Variable value.

12. Click OK.

13. Install Microsoft Visual C++ 2010 Redistributable Package (x64) http://www.microsoft.com/en-US/download/confirmation.aspx?id=14632\

14. Double click GleWatchDog.exe

Page 57 of 77

http://www.microsoft.com/en-US/download/confirmation.aspx?id=14632%5C

NICE Optimize


6 UMTS Network Consistency AnalyzerThe Network Consistency Analyzer (NCA) feature analyzes the parsed Events for up to 24 hours for each Radio Network Controller (RNC). It provides detailed reports on suspected network configuration mismatches. This analysis is done before the geo location process because it is done with the most recent network.

To use the Network Consistency Analyzer (NCA), do these steps:

1. Save the EventDB *.dat files created by PAR\Gen_PAR in the Events folder which is in the project folder.

2. Select Analysis > UMTS Analysis > Network Consistency Analyzer. The Scheduled Network Consistency Analyzer is displayed:

– The left hand pane displays all available project technologies which are selected by default and ready for analysis.

– The right side displays seven options for analysis. These are selected by default and ready for analysis, described in Table 6-35.

3. Click START. When complete, Network Consistency Analyzer (NCA) displays completed, shown in Figure 6-41.

Figure 6-41: Network Consistency Analyzer Completed

4. Double click the results in the Report File column. The results file is opens with excel, in a .csv format. The files are saved to the Report folder in the project. These files specify the problems that had been found.

5. When the reports are analyzed and action is taken to repair all mismatches, repeat the process from step 3.

Page 58 of 77

NICE Optimize


Table 6-35: Analysis Window Description

Analysis Type Description

Network Consistency Test

Provides summarized report of how many cells are missing as well as network data such as cable loss or how many cells are configured as Indoor but not found on any building.

Cross Feeder and Azimuth

Provides information about suspected cells which contain wrong Azimuths and cross feeders.

Site Location Test Provides information about suspected sites with the wrong location.

Indoor Test Detects suspected Indoor Cells that are defined as outdoor cells.

Site Statistic Analysis Detects ETilt and MTilt mismatches such as extreme tilts and duplicated tilts to MTilt and ETilt.

Malfunction Sector Detection

Detects active cells that do not have any recorded events.

Neighbor SC Test Detects imported neighbors to their SC recorded from the network.

Page 59 of 77

NICE Optimize


7 GEO Monitoring This chapter describes Geo Monitoring.

7.1 Map Legends SettingThe setup of the map legends is the first stage of map creation. The setup is for the number of thresholds for each map, their values and colours. Four types of maps can be configured for the Universal Mobile Telecommunications System (UMTS) by the user:

Received Signal Code Power (RSCP) absolute values

Ec/Io absolute values

Received Signal Code Power (RSCP) relative values

Ec/Io relative values

For the other Universal Mobile Telecommunications System (UMTS) maps, such as Number of drops, Drop Call Rate (DCR), Voice traffic, and HSPA the legend is set automatically. These values include the number of thresholds for each map, their values and colours. Automatic setup is necessary to overcome the uncertainty and the dynamic range of the values due to different hours of collection, load or the total number of hours.

The maps can be presented with absolute values, for example -85dBm to -95dBm for RSCP and -8dB to -10dB for Ec/Io. Maps can also be presented with relative values, for example 10% to 30% of the Ec/Io events were below threshold of -14dB. The user defines the threshold value and if it is above or below the threshold. The setup of the threshold is discussed in the section Create Map Events.

7.1.1 RSCP and Ec/Io Legends with Absolute Values The Received Signal Code Power (RSCP) and Ec/Io absolute values legends are configured with the Project Editor. To configure the Received Signal Code Power (RSCP) and Ec/Io absolute values legends, do these steps:

1. Open Project Editor

2. Select Technology, from the left pane

3. Click the grey square under the Technology column left of the technology name, the Technology Editor is displayed

4. Select General

5. Click Project Color Ranges. The Edit Projects Ranges window is displayed.

6. Click RSCP Range to set the RSCP ranges or Click Ec/lo Range to set the Ec/lo ranges

7. Select Number of Ranges to define a threshold

8. Click the values in the columns, From or To, to set them

9. Click the color in the column to set the color.

NOTE: Make sure to set the values separately for each technology.

Page 60 of 77

NICE Optimize


TIP: It is recommended to define a standard format for all technology.

7.1.2 RSCP and Ec/Io Legends with Relative Values Unlike the absolute values, the RSCP and Ec/Io legends with relative values are common to all technologies and the configuration is done in one location. To configure RSCP and Ec/Io legends with relative values, do these steps:

1. Open Project Editor

2. Select General, from the left hand pane

3. Click Project Color Ranges, the Edit Projects Ranges window is displayed

4. Click Standard Deviation Range, Set Std. Dev. Ranges window is displayed

5. Select Number of Ranges to define a threshold

6. Click the values in the columns, From or To, to set them. The values are in percent.

7. Click the color in the column to set the color.

7.2 Polygon SettingThe monitoring maps are created on the border of a specific polygon. NES polygons are created with the DisplayPoly table. The first step is to create the Display Polygons Layer and create the requested polygon. If an additional polygon is required or if it is necessary to change the polygon, then the DisplayPoly table can be edited. To create a display polygon layer, do these steps:

1. Click Project

2. Select Layers > Create Display Polygons Layers

3. Click OK

4. Click MapInfo Layer control. The Open Layer control window is displayed.

5. Select the Edit checkbox for DisplayPoly. The Layer Control window icons are described in Table 7-36.

6. Click OK. The Polygon and Polyline icons are activated

7. Click Polygon . Click the map and use the cursor to create the polygon.

NOTE: Only the Polygon icon can be used for the polygon drawing, even if the polygon is ellipse or rectangular.

Page 61 of 77

NICE Optimize


Table 7-36: Layer Control Icons

Icon Description

View

Edit

Selectable

Label

To modify the Polygon, do these steps:

1. Select the polygon

2. Click Reshape or Add Node icons .

3. Double click polygon. The Region Object window is displayed

4. Click Style to change the border style, color or width

5. Click Save

6. Select DisplayPoly from the list and click Save.

7.3 UMTS Maps Based on EventDB FilesThis section describes Universal Mobile Telecommunications System (UMTS) Maps based on EventDB files.

7.3.1 Select Events DatabaseThe current version of NES Universal Mobile Telecommunications System (UMTS) technology is based on file systems. All the geo located events are stored in a folder called eventsDB in the project directory. Each file contains one hour of geo located events for each Radio Network Controller (RNC). Any geo located event files that need to be analyzed should be copied to another folder called events. To filter the relevant hours, do these steps:

1. Click Analysis

2. Click UMTS Analysis

3. Click Select Event Database. The Event Selector window is displayed. A description of the Events Selector interface is in Table 7-37.

Page 62 of 77

NICE Optimize


Table 7-37: Event Selector Interface

Item Description

Filter by RNC Filters the results pane on the right hand side by RNC

Filter by Dates Filters the results pane on the right hand side by date

Filter by Day Filters the results pane on the right hand side by days

Filter by Hours Filters the results pane on the right hand side by hours

Delete exiting database

Removes previous events files from the events folder. If this remains unchecked the previous events files are added to the current one.

Create Aggregation VDT and Agg Res

Part of the optimization process described in the Optimization section.

Actv After events are filtered, additional events can be removed. Select a checkbox or right click and select Select or Unselect All. This reduces the Total Hour selected which is displayed underneath.

7.3.2 Create Events MapsAfter the selection of the events files with data generated by the Parser (PAR) and Geo Location Engine (GLE), you can create various map displays based on the located events or measurements from a real network environment. To create an Events Map, do these steps:

1. Select Analysis > UMTS_Analysis > Create Events Map. The Create Events Map wizard is displayed. The Create Events Map options include:

– New Map: Enter new map name. It is recommended to enter numbers before the name of the map as a chronologic method to create and for the display of the maps. The map name is entered to a map list.

– Load Map: Recreate map based on the original map list.

– Create All Maps: Create all the maps in the maps list. Useful for periodic routine of the same sets of maps.

2. Select New Map and type a name for the new map for example 000 001 RSCP.

3. Click Next. The Create Events Map window is displayed.

4. Select from the configuration settings in the Filters section described in Table 7-38.

Table 7-38: Create Event Map Configuration Settings

Setting Description

Database Select the button next to Database. The Event Selector wizard is displayed. This lets you to select manually or by filter, the options include:

Filter by (Radio Network Controller) RNC

Filter by Dates

Filter by Day

Filter by Hours

Mapping Type Select the button next to the Mapping Type option. The Select Mapping Type window is displayed. There are two options:

Image: Provides an aggregated display in predefined resolutions of 50m. The Min. Events/Pixel allows filtering out bins according to aggregated number of events.

Buildings: Provides an aggregated display of events by their height, from height to height with minimum required events for each building.

Page 63 of 77

NICE Optimize


Setting Description

Symbols: Provides a non aggregated map of all events. Note: This map creation can take longer than the other maps because of the number of events. This map enables low level analysis of each event.

Sectors Select the button next to the Sectors option. The Sectors window is displayed. The options include:

All: Selects all the sectors in the projects.

Use List: Selects all the sectors that were entered previously into the Project Sector Selection.

– Only Best: Allows events only from the reference cells.

– Max Rank: Defines the number of cells that are counted, from 0 to a maximum of 40.This option is only available if Only Best is not selected.

– SA Margin: Service Area margin. Defines the delta in dB between cells and the ref cells. For example, 20 are all sectors up to a 20dB difference from the monitored reference cell. This option is only available if Only Best is not selected.

Channel number and Technology: This filter is available for all options.

IMSI Select the button next to the IMSI option. The Select International Mobile Subscriber Identity (IMSI) window is displayed.

Enter the list of International Mobile Subscriber Identity (IMSI) to be monitored. Select the number and click ADD. This option can be useful for Drive test or VIP care.

Polygon Select the button next to the Polygon option. The Select Polygon to Display Results window is displayed.

Select the required polygon for the map display. For additional polygons use Display Polygon Layer.

Call Type Select the button next to the Call Type option. The Call Type window is displayed. Select one of these network event options:

Select Events: Defines the type of events displayed

– Regular (proper operation)

– Move to GSM (IRAT)

– Drops

– Pollution. Select the events that have one or more polluter cell. One or more can be selected.

Select Service: Defines the type of service displayed

– Voice

– Data

– HSPA (for HSPA service it is recommended to select also Data)

– Others (all other events that was not defined. For example SMS, registration, unknown). One or more can be selected.

Only Sessions with Measurements report: Check this box to eliminate events without a measurement report.

Advance: Not mandatory. Options to select different CS codecs, PS rates, HSDPA/HSUPA and Downlink/Uplink.

Create All segments

Select if hourly analysis is required. For example If 20 hours were selected and the checkbox is not selected, NES produces one map with event aggregation of all 20 hours. If checkbox is selected, NES produces 20 maps with event aggregation for each hour.

5. Click Next. The Color By window is displayed. Select one of the options described in Table 7-39.

Page 64 of 77

NICE Optimize


NOTE: The actual settings displayed in the Color By window are dependent on the Mapping Type and Call Type options selected.

6. Click Save. The Setup is saved as the original name

7. Click Create. A map is created

Table 7-39: Color By Options Window

Option Description

Event Percentage of the selected event, of all events in a specific pixel, would always be 100%. For example for Drop Call Rate (DCR) total events is the total number of calls (100%). The number of drops divided by the total number of calls is shown as a relative number such as 10%

Event (absolute) Number of events in each pixel.

Ec Shows Received Signal Code Power (RSCP) levels for Image or Building maps. The options include:

Mean: Shows average Ec/Io values of geo located events.

Threshold percent: Shows the percent of events above or below a threshold. The settings are done in the open window.

Ec/Io Shows Ec/Io levels for Image or Building maps. The options include:

Mean: Shows average Ec/Io values of geo located events.

Threshold percent: Shows the percent of events above or below a threshold. The settings are done in the open window.

# Polluting Sector Shows the average number of polluters for each bin or building.

# Active Set Links Shows the average number of Active Set Links for each bin or building.

UE Transmit Power The average UE Transmit Power for each image bin or building.

Voice Traffic Shows the Voice traffic in mErlang or in Minutes Of Use (MOU). The settings are done in the open window.

Data Traffic Shows the Data traffic of Rel99. The options include:

Mean: Shows average Data traffic for each hour (relevant for two or more selected hours of analysis).

Total: Total data traffic for each all selected hours of analysis.

HSPA Traffic Shows the High Speed Packet Access (HSPA) traffic.

User Traffic Shows the total traffic for Voice, HSPA and Rel99. The options include:

Mean: Shows average user traffic for each hour (relevant for two or more selected hours of analysis).

Total: Total user traffic for each all selected hours of analysis.

7.3.3 Practice - Image Map of RSCP To practice, create this map of the Received Signal Code Power (RSCP):

Polygon Examples_Poly, RSCP, Absolute values

Mean value of all events for all hours

Image Map with resolution of 50m, minimum number of events is 1

RNC 22RR_ORNCO, 07/06/2014, 09:00 – 20:00

NOTE: Make sure that only the these hours are used

Page 65 of 77

NICE Optimize


Map creation is done on the events files found in the Events directory. At first, all geo located events files are in eventsDB directory. The files can be copied manually to the eventsDB directory or can be selected with the Select Events Database. This operation can filter part of the files, copy events files from the eventsDB directory to Events directory, add to a previous list or delete the events files and start again. To create a map of the Received Signal Code Power (RSCP), do these steps:

1. Select Analysis > UMTS_Analysis > Select Event Database. The Event Selector window is displayed.

2. Set the Event Selector settings shown in Table 7-40.

Table 7-40: Practice - Event Selector Settings

Option Selection

Filter by RNC Select 22RR_ORNC0

Filter by Dates Select 2014/06/07

Filter by Days Select Sun, Mon, Tue, Wed, Thu, Fri, Sat

Filter by Hours Select From Hour 9, Select To Hour 20

Delete exiting database Select the checkbox. This makes sure only the required hours are in the Events directory. The tool creates an Events directory, if it does not exist and deletes files from the current directory if required. It copies the requested files and reports if the operation was completed successfully.

Create Aggregation VDT and Agg Res Make sure this is not selected

3. Select Analysis > UMTS_Analysis > Create Events Map. The Create Events Map wizard is displayed.

4. Write the new Map name 000 001 RSCP Image 50.and click Next.

5. Select the filters:

– Database

– Sectors

– Polygons

– Call Type

6. Make sure the Create all segments checkbox is not selected. Make sure the settings are the same as displayed in Figure 7-42.

Page 66 of 77

NICE Optimize


Figure 7-42: Create Maps Configuration

7. Click Next.

8. Select EC and Mean. Click Save

9. Click Create. The RSCP is created and displayed. The Map is stored in the project MapReport directory.

10. Click Show/Hide Legend

7.4 UMTS Events Map Navigator The function, Events Map can display different map types, examples include:

Performance: RSCP and Ec/Io

Key Performance Indicators (KPI): Drops, DCR, and Traffic

Resolution: Aggregation of hours and maps per hour.

To use the Events Map Navigator to display maps, do these steps:

1. Select Analysis > UMTS Analysis > Events Map Navigator. The Event 3G Maps Navigator is displayed, shown in Figure 7-43.

2. Set the Event 3G Maps Navigator as necessary. The window is described in Table 7-41.

3. When the option is selected in the Event 3G Maps Navigator the map is automatically displayed.

4. Click Show/Hide Legend to show or hide the map legend.

Page 67 of 77

NICE Optimize


Figure 7-43: Event 3G Maps Navigator Window

Table 7-41: Event 3G Maps Navigator Window Description

Option Description

Type Name of the map created during the Create Events Map process. The maps are organized according to their name. It is recommended to use a naming convention according to the user methodology.

Note: Make sure _ is not used in the naming convention.

Date Used to create a series of maps per hour. The user can choose the required day from the list.

Time Used to create a series of maps per hour. The user can choose the required hour from the list.

U, D, L, R Move the map view Up, Down, Left or Right.

Zoom In Zooms in on the Map.

Zoom Out Zooms out of the Map.

Previous View Returns the map view to the previous view.

Auto Zoom The map is displayed in the center of the screen.

Page 68 of 77

NICE Optimize


8 Network OptimizationThis chapter describes network optimization of the NES system.

8.1 PreparationBefore network optimization, the preparation steps include:

Virtual Drive Test Aggregation (VDTA)

Optimization Polygons

Select Technology and Carrier

Select Cells or Sectors to be Optimized

Constraints list

8.1.1 Virtual Drive Test Aggregation (VDTA)Legacy network optimization procedure operates on all coverage database layers, which include:

Area

Buildings

Roads

A feature of the NES tool is to add 3D Virtual Drive Test. The Virtual Drive test is the 3D geo location of different network events. Optimization based on VDTA can identify the difference between the traffic and its impact for different times of the day or different segments, for example residential or business.

The objective of network optimization in Universal Mobile Telecommunications System (UMTS) is to decrease the pilot pollution in areas which are most affected and populated. This is done without losing coverage and provides the best possible Ec\No. The basic operation of this procedure is to find the best antenna configuration (mechanical/electrical tilts, azimuths, power allocation and antenna types). Virtual Drive Test Aggregation (VDTA) creation is done with the Select events Database option.

To do network optimization in Universal Mobile Telecommunications System (UMTS), do these steps:

1. Select Analysis > UMTS Analysis > Select events Database. The Event Selector window is displayed, shown in Figure 8-44.

Page 69 of 77

NICE Optimize


Figure 8-44: Event Selector

2. Select the required RNCs and the hours to be optimized.

3. Select Create Aggregation VDT. Two options are displayed:

– Delete all: NES deletes all existing VDTA files and enter just the new files.

– Add to existing: NES adds new VDTA files to existing VDTA files.

4. Click OK. NES copies the selected eventsDB files from the directory eventsDB to Events and creates the VDTA file in all coverage directories, for example CA_UMTS_E.

5. Click Close.

8.1.2 Optimization PolygonsTwo polygons are required for the optimization process. The first one is necessary and it is named Optimization polygon. It defines the borders of an area to be optimized. The second one is not necessary and defines the guard or influence area. If this polygon is set NES optimizes the optimization polygon and minimizes the interference impact on the guard area. If the guard polygon is not set NES creates its own guard area taking into account the total impact of the optimized selected sectors. To set the guard polygon borders requires cellular radio experience, but the advantage is in the optimization time saving. The two polygons are shown in Figure 8-45.

The two polygon borders are defined with the Create Display Polygons Layers, described in the Monitoring chapter.

Page 70 of 77

NICE Optimize


Figure 8-45: Optimization Polygons

8.1.3 Select Technology and CarrierOptimization is done on one carrier in one technology. The selection is done through the Project Editor window. To select the carrier and technology, do these steps:

1. Click Technology and Project Editor . The Project Editor is displayed.

2. Select Technology.

3. Select the checkbox for the default technology and carrier. For example, select the carrier of UMTS 900MHz technology shown in Figure 8-46.

4. Click OK.

Page 71 of 77

NICE Optimize


Figure 8-46: Project Editor Default Technology

8.1.4 Select Cells or Sectors to be OptimizedOptimization is done on the cells of one carrier in one technology inside the optimization polygon. The user selects all cells, all technology and carriers inside the polygon and during the optimization process NES selects from this list, the relevant cells according to the selected default technology. To perform the cells selection process, do these steps:

1. <Ctrl> and click Boundary Select

2. Select the cells for optimization.

3. Click inside the optimization polygon until the inner polygon cells are highlighted.

4. Click Clear Cells List to delete previous selections.

5. Click Add Selected Cells to List. All technology and carriers inside the polygon are selected.

6. Click OK

Page 72 of 77

NICE Optimize


8.1.5 Constraints ListThe optimization process controls Radio and antenna parameters such as:

Power (CPICH)

Mechanical tilt

Electrical tilt

Azimuth

Antenna type.

Each network has its own limitations, for example CPICH power in congested sectors, azimuth and electrical tilt due to the environment. For this reason it is recommended that all network limitations for each cell are collected before the optimization process to avoid unnecessary optimization changes. The constraints list for each cell is created during the optimization process.

8.2 Optimization ProcessWhen the preparation has been completed, the optimization process is run. To run the optimization process, do these steps:

1. Select Analysis > Optimization > Network Optimization. The Network Optimization window is displayed.

2. Enter a name for the current optimization process. Make sure both polygons are selected.

NOTE: When no polygons are selected, cancel and repeat the optimization preparation.

3. Click Next. The Database window is displayed. Check the list of Sectors to make sure no sectors are missing or added. NES selects the relevant cells from the sectors list according to the selected default technology.

4. Click Next. The Optimization parameters window is displayed. This shows the Optimization Thresholds. The optimization process selects the Optimization Area by default. This means that all bins have equal traffic and data.

NOTE: Projects containing Virtual Drive Test Aggregated (VDTA), which is the aggregated measurement report already processed, must use the Area mode. This is because the events quantity represents traffic and data values.

5. Click Coverage Layers to select coverage layers to use. These include: area, building, road, and virtual drive test. The weighting between the layers, lets specific layers give a higher optimization weighting.

NOTE: All layer weights must add up to 100%.

6. Click OK

7. Set the RSS Threshold (dBm) and Ec/Io Threshold (dB) to define the RSS and Ec/Io levels above which a bin is to be covered.

Page 73 of 77

NICE Optimize


8. Click Advance to open additional settings. The Advanced Settings window is displayed as shown in Figure 8-47.

9. Select the configuration options described in Table 8-42. Click OK.

Figure 8-47: Advanced Settings Window

Table 8-42: Advanced Settings

Setting Description

Limit the Sectors to current range

This option tells the procedure not to make changes that would increase the coverage range dramatically. Thereby, avoiding possible interference to other clusters (usually in hilly areas or in very dense/industrial areas containing a lot of towers).

Existing Coverage There are two options:

Prevent Damage: Does not allow any change that would damage the coverage. For example, stops a previously covered bin from becoming uncovered.

Damages Penalty: Allows the procedure to uncover a bin, but only if other bins are covered. This is defined in the numerical field next to the Existing Coverage field. The options include:

– 0: This ignores the damaged bin. When comparing between changes those bins are not counted. For example if no other bins are improved then this change is discarded as it has fewer good bins.

– 1: Reduces the grade by 1 for each removed bin due to damages.

RSS Levels (or RSCP Levels) and C/I levels (or Ec/Io Levels).

A bin is considered covered when both parameters are above their lowest value. To reflect the fact that higher RSS and C/I levels are better, a set of levels can be defined. A bin of the second level is counted as 1+1/k better than the minimal bin. To define k click Step Factor.

10. Click Network Status to use histograms. The Coverage Histograms window is displayed.

NOTE: The histograms can be labeled when the Label checkbox is selected.

11. Click Next. The Global Constraints tab is displayed as shown in Figure 8-48. The parameters of the constraints are grouped and described in Table 8-43: Global Constraints Settings. Each setting has an option to define if the parameter is to be modified during analysis.

Page 74 of 77

NICE Optimize


Figure 8-48: Global Constraints Tab

Table 8-43: Global Constraints Settings

Setting Description

Power Changes the radio power relative to the existing power starting from Relative down (dB) but not lower than Min power (dBm) up to Relative up (dB), but not more than Max power (dBm). The power change is in steps of Power step dB.

Azimuth (Relative) Changes the antenna azimuth from Left azimuth (degrees) to Right Azimuth (degrees) in steps of Azimuth Step (degrees. This is relative to the actual antenna azimuth.

Down Tilt (Relative) Changes the antenna mechanical tilt from Up tilt (degrees) to Down tilt (degrees) in steps of Tilt Step (degrees) relative to the actual antenna mechanical tilt.

Note: Positive tilt is in the direction of below the horizon, down.

Electrical Tilt The tilt modification is made by electrical tilt first. This means that the antenna pattern is changed based on the tilt value.

Antennas When selected, a set of alternative antennas are replaced to see if performance is improved. The options include:

Adds antenna to the list

Deletes an antenna from the list

Loads a recently saved list of antennas

Saves the current list.

12. Click Constraints List to view local constraints. The list is based on the global constraints set by the user. The Constraints list can be edited to avoid changes, defined by the Global Constrains property, to specific cells made by the optimization process. The saved file is called LocalConstraints.txt and is found in the Optimization folder in the projects folder.

13. Click Create Local Constraints to create file of local constrains file. The Constraints List is shown in Figure 8-49.

Page 75 of 77

NICE Optimize


Figure 8-49: Constraints List

14. Click Next. The final optimization window is displayed.

15. Click Start ACP to run the optimization. During operation the Changes tab shows the recommended modifications. Progress is shown on the graph from the Statistics tab. The Changes tab options are described in Table 8-44.

Table 8-44: Changes Tab Settings

Options Description

Stop ACP Stops the operation at any time.

Save Saves the operation.

Reset Restarts the optimization.

Add Changes Add additional changes to the optimization recommendations and evaluate the impact.

Network Status Displays Coverage Histograms of the optimization with Before and After for RSCP/EcIO.

Evaluate View and evaluate each set of changes given by the analysis. The recommended changes can be selected (for each individual change) to be included in the set, by the options in the Actv column.

To evaluate the result of all the selected changes, do these steps:

1. Select Create Map of changes option.

2. Click Evaluate. This is shown on the graph under Coverage.

3. Click OK. A MapInfo table is generated.Note: The NetOptim_Changes tab contains the information of every bin that has been affected by the change.

The information options include:

Improved: The bin has been uncovered before the optimization process and is covered afterwards

Increased: The bin has been covered before but either RSS or the C/I or both are better after the optimization.

Decreased: The bin RSS or C/I deteriorated after the optimization

Spoiled: The bin was covered before the optimization but it is not covered after it.

To evaluate different Optimization scenarios, do these steps:

1. Select Analysis > Optimization > Network Optimization.

Page 76 of 77

NICE Optimize


2. Select the Load Optimization and select the optimization name.

3. Click Apply. The changes are applied to the network as shown in Figure 8-50.

To undo changes that are applied by the NES menu item, do these steps:

1. Select Analysis > Optimization > Restore Network Optimization Changes.

2. If the Create Map of Changes option is selected, the map of changes is displayed when the window is closed, either when Apply is clicked or the window is closed. It indicates the status for each bin.

NOTE: The table NetOptim_Changes.tab is found in the Optimization folder under the project. It contains all necessary information for each bin for the last optimization process. This includes RSS before and after, C/I before and after, RSS status and C/I status which is displayed with MapInfos thematic map options.

Figure 8-50: Optimization Changes by Status

Page 77 of 77