Aeriso Geo Technical Guide

Technical Guide

Page 2

Arieso Commercial-in-Confidence Copyright © 2013 Arieso Ltd

Version 1.0

Issued 01 May 2013

The information contained in this document and any documentation referred to herein or

attached hereto, is of a confidential nature and is supplied for the purpose of discussion only

and for no other purpose.

This information should only be disclosed to those individuals directly involved with

consideration and evaluation of any proposals, all of who shall be made aware of this

requirement for confidentiality.

All trademarks are hereby acknowledged.

Page 3


About Arieso

Arieso is the world's leading provider of intelligent, location aware solutions that enable

mobile network operators to focus their businesses on the evolving desires and expectations

of their customers. The company's solutions locate, store and analyse data from billions of

mobile connection events, giving operators a rich source of intelligence to help boost

network performance and enrich user experience. This intelligence transforms the

effectiveness of network performance engineering; enables customer-centric self-optimizing

networks; creates true understanding of customer experience and enables monetization of

unique insights.

Arieso’s proven carrier grade solutions are resilient and highly scalable. Operating on five

continents, Arieso’s clients include mobile operator groups such as América Móvil, AT&T,

MTN, Telefónica and Vodafone, and leading equipment vendors including Alcatel Lucent and

NSN.

More information on Arieso can be found at www.arieso.com.

Page 4


Page 5


Contents

ABOUT ARIESO ......................................................................................................................................... 3

CONTENTS.......................................................................................................................................... 5

1. INTRODUCTION......................................................................................................................... 7

2. ARIESOGEO CONCEPTS ............................................................................................................. 8

2.1 THE ARIESOGEO CALL MODEL ............................................................................................................ 8

2.1.1 Call segments ......................................................................................................................... 8

2.1.2 Active set and best cell ........................................................................................................... 9

2.1.3 Blocks and drops .................................................................................................................... 9

2.2 GEOLOCATION .............................................................................................................................. 10

2.2.1 Geolocation of UMTS Calls ................................................................................................... 10

2.3 LOADING CALL DATA ...................................................................................................................... 11

2.3.1 Loading data ........................................................................................................................ 11

2.3.2 Summarizing data ................................................................................................................ 13

3. METRICS AND KPIS .................................................................................................................. 14

3.1 CONNECTION FAILURES AND NORMAL RELEASES .................................................................................. 14

3.1.1 Blocks ................................................................................................................................... 14

3.1.2 Drops .................................................................................................................................... 16

3.1.3 Normal releases ................................................................................................................... 19

3.2 CALLS AND CONNECTIONS ............................................................................................................... 19

3.3 CELLS .......................................................................................................................................... 20

3.4 COMPLETION CODES ...................................................................................................................... 21

3.5 DEVICES AND SUBSCRIBERS .............................................................................................................. 22

3.6 EC/IO ......................................................................................................................................... 23

3.7 GEOLOCATION AND DISTANCE ......................................................................................................... 24

3.8 IFHO AND IRAT ........................................................................................................................... 25

3.9 LOAD CHAIN ................................................................................................................................. 26

Page 6


3.10 RSCP ..................................................................................................................................... 27

3.11 THROUGHPUT .......................................................................................................................... 29

3.12 TIME AND DURATION ................................................................................................................ 30

3.13 VOLUME AND TRAFFIC ............................................................................................................... 30

4. FILTERS ................................................................................................................................... 32

4.1 COMMON FILTERS ......................................................................................................................... 33

4.2 UMTS FILTERS ............................................................................................................................. 37

5. ANALYSES ............................................................................................................................... 44

5.1 UMTS ANALYSES .......................................................................................................................... 44

5.1.1 UMTS database tables ......................................................................................................... 44

5.1.2 UTMS analyses A-C ............................................................................................................... 45

5.1.3 UTMS analyses D-L ............................................................................................................... 61

5.1.4 UTMS analyses M-R ............................................................................................................. 74

5.1.5 UTMS analyses S-Z ............................................................................................................... 90

VERSION HISTORY ................................................................................................................................. 105

Page 7


1. Introduction

ariesoGEO is based around a call model that is similar across the different technologies. This

means that data from different technologies or equipment vendors can be compared

directly and meaningfully.

This document explains the ariesoGEO call model and how the parameters and KPIs based

on it are derived. It also provides additional technical detail on how to use analyses and

filters. It is intended for readers who are familiar with both mobile network infrastructure

and the core concepts of ariesoGEO.

The current version of this document focuses on UMTS technology and analyses, but future

versions will include information on GSM and LTE.

Page 8


2. ariesoGEO Concepts

2.1 The ariesoGEO call model

The measures used in ariesoGEO are based on the concept of a call, which is a single

connection. This connection is reconstructed from the events listed in the call event data

files.

For example, in UMTS and LTE call event data files that follow the 3GPP standard, a call is

defined as starting with an RRC CONNECTION REQUEST message and ending (if released

normally) with an RRC CONNECTION RELEASE message.

Note: For the purposes of call counts, a call is counted against the cell in which it is initiated.

For UMTS connections, this is the best cell in the active set.

In call event data files that follow a vendor-specific format, individual calls are reconstructed

in the same way using equivalent vendor-specific events.

Note: ariesoGEO counts are based on events rather than on transmission. This means that,

for example, ariesoGEO does not stop measuring duration when it receives an SCRI

message to establish fast dormancy.

Because ariesoGEO's model is event-based rather than transmission-based, it can provide

more insight into details of the network performance than traditional methods can. This

also means that KPIs calculated by ariesoGEO are not directly comparable with those

calculated by other tools, and should not be used to set benchmarks for them.

2.1.1 Call segments

A single call may consist of multiple call segments (also sometimes called call legs).

ariesoGEO creates a new call segment at the following triggers:

GSM triggers:

• A service change

• A handover

• At the end of ten seconds of measurement reports

• At the end of the 15-minute period

UMTS triggers:

• A service change

Note: A service may consist of multiple RABs, but only a single connection will be

counted. The service group the service belongs to may indicate if it is multi-RAB.

Page 9


• A measurement report is received that provides enough information to geolocate the

segment

• The end of the 15-minute period

• (For Ericsson only) A new GPEH file becomes available

A call segment can technically be any length up to 15 minutes, but in practice most call

segments are under 1 minute long.

Call segments are numbered in increasing order from the start of the call. Because

segments shorter than 5 seconds are combined during geolocation, the numbers are not

usually sequential. For example, a complete call might consist of the segments 0, 3, 10, 14

and 17. The first segment of a call is always numbered 0.

Call durations and other metrics are calculated by summing the relevant values for all the

call segments. For example, the Minutes of Use KPI for a cell would be the sum of the

duration of all the segments assigned to that cell.

2.1.2 Active set and best cell

In UMTS the UE is not connected to a single cell. Instead, the set of cells that the UE is

simultaneously connected to is called the active set. ariesoGEO uses information within the

call event data files to track the active set.

A call segment is assigned to the best cell of the active set during that segment. That is, the

cell with the best Ec/Io.

2.1.3 Blocks and drops

In the ariesoGEO call model, a block is a failure that occurs during establishment of a call,

and a drop is a failure that occurs within an active call. Drops are assigned to the cell and

service on which they occur, but calls are assigned to the originating cell and service.

Note: This assignment system means that some cells and services may sometimes show

more drops than calls.

ariesoGEO uses the messages within individual calls to classify blocks and drops. This

includes RRC messages, RANAP messages and vendor-specific messages.

For example, the 3GPP message INTERNAL SYSTEM BLOCK is used to classify blocks.

Details from the 3GPP messages RRC CONNECTION RELEASE, RANAP IU RELEASE

COMMAND and INTERNAL_SYSTEM_RELEASE are used to classify drops.

Vendor-specific messages are used both to classify blocks and drops and to assign them to

circuit switching, packet switching or signalling.

Page 10


Note: When a vendor-specific message arrives some time after the block or drop has been

registered, the block or drop may not be assigned correctly. This means that, for

example, a signalling service may occasionally register CS drops.

For multi-RAB calls that may have multiple drops on a service, each drop is reported

separately for the service on which it dropped.

2.2 Geolocation

ariesoGEO's geolocation algorithm is based on measurements provided by standard call

records. As not all vendors or technologies report the same measurements, the exact

algorithm used varies according to the available data.

Each geolocation has a confidence level assigned to it. This is calculated from the level of

consistency between the separate details used to geolocate it. Call segments can have a

confidence value of between 0 and 1, where values under 0.001 are considered low

confidence.

Note: The confidence level does not indicate how precisely the call segment has been

geolocated, and cannot be translated into an area approximation. It only indicates how

confident ariesoGEO is that the segment's location is correct.

Call segments with values below the minimum confidence level set in AriesoGEO will not be

included in analyses based on the call table, even if these analyses do not show location

information. The only exceptions to this are the VIP Locations analysis (UMTS) and the

Individual Connection Segments (Common), both available with the SubscriberManagement

license.

Administrators can change the minimum confidence level by clicking File > Options and

selecting the Other Parameters tab.

Subscriber movement

Using the locations of individual call segments, ariesoGEO can calculate a subscriber's speed,

and therefore whether that subscriber was stationary, walking, or in a moving vehicle. This

information is available on systems that have the Mobility license installed.

Indoor/outdoor location

By comparing signal measurements with those reported during call segments known to be

outdoors, ariesoGEO can even calculate whether a call was made from inside a building.

This information is available on systems that have the IndoorOutdoor license installed.

2.2.1 Geolocation of UMTS Calls

The following methods are used to geolocate UMTS calls:

Page 11


None

Where no further information is available for geolocation, a segment is located at the server

location with a confidence of 0. These segments are not normally included in analyses or

summarized. Only the CellSummary table includes information from non-geolocated call

segments.

Simplex

Simplex geolocation uses the propagation delay to determine the distance of the call from

the serving cell.

Simplex Spreading

Simplex spreading adds accuracy to simplex measurements by comparing the measured

Ec/Io of the call to the Ec/Io measurements of GPS calls within the cell.

Single Soft Handoff

Single soft handoff geolocation uses Ec/Io measurements, timing or power data from pairs

of cells (adjusted for the difference between the two cell clocks), and information from the

network configuration to locate each call segment.

Multiple Soft Handoff

Multiple soft handoff geolocation is similar to single soft handoff, but its algorithm uses the

timing information from three or more cells.

Softer Handoff

During a softer handoff, the call is geolocated using the difference in Ec/Io between the

serving cell and the next strongest cell on the same site.

Previous Location

If no information is available for a call segment, the previous location is used.

Historic Location

If no information is available for the initial segment of a call, the subscriber's last known

location is used.

2.3 Loading call data

2.3.1 Loading data

The loader process uses a set of individual steps to copy the files from each network

component (such as a BSC or RNC) to the loader server, parse the vendor-specific files and

measurements into a common format, identify and geolocate individual calls, and load the

resulting processed data into the call table.

Each stage of the loading process outputs a set of intermediate files that are used as inputs

to the next stage. These intermediate files make the loading process robust, because any

failed stage can be re-attempted without beginning the entire process again.

Page 12


The progress of each file through the loading process is recorded in the loading tables.

Copying files

The GeoDataLoader monitors the data directories for each network component. When call

data files from a network component appear in a data directory, the GeoDataLoader uses

FTP to copy the files to the loader server and begin the loading process.

At the same time, it enters details for each file it has detected into the loading tables so that

ariesoGEO can track the file's progress through the loading steps.

Parsing files

Event data files from different vendors may contain very different measurements. For each

vendor format, Arieso supplies a parser that:

• Extracts the required measurements and event records

• Sorts the event records into chronological order

• Processes the data into the form used in ariesoGEO. For example, this might include

using vendor-specific messages relating to RAB changes in order to track the RAB used

for a call segment

• Reconstructs each call and creates call segments

For each network component, the parser outputs a single vendor-independent file that

contains call segment and event data for a fifteen-minute period.

For some vendor data file formats that produce multiple data files (such as GPEH), the

parser uses information within the file set to detect how many files should be within the set.

If any files are missing it waits for a specified timeout period before parsing the files that are

available. If call termination messages are among the missing events, this may cause

irregularities in the data for the affected calls.

The files output by the parser are in one of three vendor-independent internal formats,

depending on the technology used. There are significant differences between GSM, UMTS

and LTE, such as the measurements they produce, and so a different file format is used for

each. These file types are in the form .xcmd, such as .ecmd for UMTS data.

Properties and limitations of the original vendor files will affect the data that is parsed. For

example, some vendor formats produce files that sometimes cover long periods of time and

are not available for copying and parsing until the earliest periods in them have already been

processed and closed based on data from other network components. In these cases, the

parser for that file format will parse the data from the open periods, but data from the

earliest periods cannot be entered into the database. Such issues are normally rare, and

Arieso is pushing the relevant vendors to resolve the issue.

Page 13


Geolocating files

A number of processes perform geolocation based on the files produced by the parser. For

more information on the geolocation algorithm, see Geolocation on page 10. The

geolocater outputs files in .glr format.

Loading data

The GeoOracleDataLoader loads the geolocated data into the call table in the Oracle

database. Call segments that cannot be geolocated are not loaded into the database.

Call segments that cannot be geolocated should not be confused with call segments that

have a 0 confidence, but that can be located to within the bounds of a specific cell.

2.3.2 Summarizing data

When call data is initially loaded into the database, it is placed in the call table. Because the

call table contains information on every call made on the system, it grows very large. Most

analyses are therefore performed against the summary tables that contain summarized

versions of this data.

For each GEO Area and technology, a summary process controller runs every fifteen minutes

to summarize data that has been loaded into the call table since it last ran.

Late or missing data

The lag period specifies how long the summarizer will wait for data that it knows to be in the

load chain. Once the summarizer has summarized the data for a period, it does not return

to that period, so very late data may not be included in analyses based on the summary

tables.

Multiple summarizers

No matter how many load servers a system has, it should have only a single summarizer

installed for each GEO Area.

In cases where the load servers have been incorrectly configured, a system may have

multiple summarizers installed. This may result in the same data being entered into the

summary tables multiple times.

Page 14


3. MetricsandKPIs

Metrics and KPIs are the information that is shown in analyses, such as Minutes of Use

(MOU) and Drop Rate. This section explains how they are calculated and what they mean.

3.1 Connection failures and normal releases

For more information about how blocks and drops are defined in ariesoGEO, see Blocks and

drops on page 9. Metrics such as the block rate and the drop rate are calculated in similar

ways using the same base data, and can be directly compared.

CS Failures

CS Blocks + CS Drops

The sum of all the failures that occurred on circuit switched connections.

PS Failures

PS Blocks + PS Drops

The sum of all the failures that occurred on packet switched connections.

Signalling Failures

Signalling Blocks + Signalling Drops

The sum of all the failures that occurred during signalling.

Total Failures

All Blocks + All Drops

The sum of all the failures that occurred within the filtered items.

Unknown Failures

Unknown Blocks + Unknown Drops

The sum of all the failures that could not be assigned to a specific failure domain.

3.1.1 Blocks

Blocks are defined as connection attempts that fail.

Blocks

Block Count

Total Blocks

The sum of all the calls that end with completion codes that ariesoGEO has assigned to the

block category. Completion codes are assigned to the block category using the same lookup

table that is used for the Network View (Combined) filter described on page 7.

Page 15


Block Rate

Blocks / Calls

The ratio of blocks to attempted calls. This is a number between 0 and 1. If the number of

attempted connections is 0, the drop rate will also be 0.

Block Rate (%)

(Blocks / (Blocks + Drops + Normal Releases) ) * 100

The percentage of attempted connections that are blocked. If the number of attempted

connections is 0, the Block Rate (%) will also be 0.

In the Performance KPIs analysis, the Block Rate (%) is based on the number of calls that

both start and finish within the specified time period. Calls that continue beyond the end

time are ignored.

CS Blocks

The sum of all the blocks that occurred on circuit switched connections.

CS Block Rate (%)

(CS Blocks / (CS Blocks + CS Drops + All Normal Releases) ) * 100

The percentage of all calls that suffer a circuit switched block. To show the rate of CS blocks

to CS calls, filter by Service or Service Group.

PS Blocks

The sum of all the blocks that occurred on packet switched connections.

PS Block Rate (%)

(PS Blocks / (PS Blocks + PS Drops + All Normal Releases) ) * 100

The percentage of all calls that suffer a packet switched block. To show the rate of PS blocks

to PS calls, filter by Service or Service Group.

Signalling Blocks

The sum of all the blocks that occurred during the attempt to set up signalling. Signalling

blocks are identified using SRB vendor tickets.

Signalling Block Rate (%)

(Signalling Blocks / (Signalling Blocks + Signalling Drops + All

Normal Releases) ) * 100

The percentage of all calls that suffer a signalling block. To show the rate of Signalling blocks

to Signalling calls, filter by Service or Service Group.

Unknown Blocks

The sum of all the blocks that cannot be straightforwardly assigned to a specific failure

domain.

Page 16


Unknown Block Rate (%)

(Unknown Blocks / (Unknown Blocks + Unknown Drops + All Normal

Releases) ) * 100

The percentage of all calls that suffer a block that cannot be assigned to a specific failure

domain.

Weighted Block Rate

Weighted Blocks

Blocks * Block Rate

The Weighted Block Rate is normally used to indicate items that have both a high number of

blocks and a high block rate. If both are low, the Weighted Block Rate will approach 0. If

both are very high, the Weighted Block Rate may approach or even exceed 1. If the number

of calls is 0, the Weighted Block Rate will also be 0.

Weighted CS Block Rate

CS Blocks * CS Block Rate

The Weighted CS Block Rate is normally used to indicate items that have both a high number

of circuit switched blocks and a high block rate. To ensure that only CS releases are used,

filter the connections included in the analysis by Service or Service Group.

Weighted PS Block Rate

PS Blocks * PS Block Rate

The Weighted PS Block Rate is normally used to indicate items that have both a high number

of packet switched blocks and a high block rate. To ensure that only PS releases are used,

filter the connections included in the analysis by Service or Service Group.

Weighted Signalling Block Rate

Signalling Blocks * Signalling Block Rate

The Weighted PS Block Rate is normally used to indicate items that have both a high number

of blocks during signalling and a high block rate. To ensure that only Signalling releases are

used, filter the connections included in the analysis by Service or Service Group.

3.1.2 Drops

Drops are successful connections that fail before completing normally. For information on

how drops are defined in ariesoGEO see Blocks and drops on page 9.

Note: Drops are assigned to the cell and service on which they occur, but calls are assigned

to the originating cell.

CS Drops

The sum of all the drops that occurred on circuit switched connections.

Page 17


CS Drop Rate (%)

(CS Drops / (CS Drops + All Normal Releases) ) * 100

The percentage of all calls that suffer a circuit switched drop. To show the rate of CS drops

to CS calls, filter by Service or Service Group.

Drops

Drop Count

Total Drops

The sum of all the calls that end with completion codes that ariesoGEO has assigned to the

drop category. Completion codes are assigned to the drop category using the same lookup

table that is used for the Network View (Combined) filter described on page 7.

Drop Rate

Drops / (Calls - Blocks)

The Drop Rate is the ratio of abnormally released calls to the number of successfully

connected calls. It is normally expressed as a number between 0 and 1. If the number of

successfully connected calls is 0 (that is, Calls-Blocks is 0), the drop rate will also be 0.

Note: If the drop rate is more than 1, this probably indicates a high number of handovers.

Calls that do not originate within a cell or service are not counted in the call count for

that cell/service, but if they terminate abnormally they are included in the drop count.

Drop Rate (%)

100 * (Drops / (Calls - Blocks))

The percentage of successfully connected calls that are released abnormally. If the number

of attempted connections is 0, the Block Rate (%) will also be 0.

In the Performance KPIs analysis, the Drop Rate (%) is based on the number of calls that both

start and finish within the specified time period. Calls that continue beyond the end time

are ignored.

PS Drops

The sum of all the drops that occurred on packet switched connections.

PS Drop Rate (%)

(PS Drops / (PS Drops + All Normal Releases) ) * 100

The percentage of all calls that suffer a packet switched drop. To show the rate of PS drops

to PS calls, filter by Service or Service Group.

Signalling Drops

The sum of all the blocks that occurred during active signalling, while the call is in the RRC

stage without a RAB. Signalling blocks are identified using SRB vendor tickets.

Page 18


Signalling Drop Rate (%)

(Signalling Drops / (Signalling Drops + All Normal Releases) ) * 100

The percentage of all calls that suffer a packet switched drop. To show the rate of Signalling

drops to Signalling calls, filter by Service or Service Group.

Unknown Drops

The sum of all the drops that could not be assigned to a failure domain.

Unknown Drop Rate (%)

(Unknown Drops / (Unknown Drops + All Normal Releases) ) * 100

The percentage of all calls that suffer a drop that cannot be assigned to circuit switching,

packet switching or signalling.

Weighted Drop Rate

Weighted Drops

Drops * Drop Rate

The Weighted Drop Rate is normally used to indicate items that have both a high number of

drops and a high drop rate. If both are low, the Weighted Drop Rate will approach 0. If both

are very high, the Weighted Drop Rate may approach or even exceed 1.

Weighted CS Drop Rate

CS Drops * CS Drop Rate

The Weighted CS Drop Rate is normally used to indicate items that have both a high number

of circuit switched drops and a high circuit switched drop rate. To show the rate of CS drops

to CS calls rather than all calls, filter by Service or Service Group.

Weighted PS Drop Rate

PS Drops * PS Drop Rate

The Weighted PS Drop Rate is normally used to indicate items that have both a high number

of packet switched drops and a high packet switched drop rate. To show the rate of PS

drops to PS calls rather than all calls, filter by Service or Service Group.

Weighted Signalling Drop Rate

Signalling Drops * Signalling Drop Rate

The Weighted Signalling Drop Rate is normally used to indicate items that have both a high

number of signalling drops and a high signalling drop rate. To show the rate of Signalling

drops to Signalling calls rather than all calls, filter by Service or Service Group.

Weighted Unknown Drop Rate

Unknown Drops * Unknown Drop Rate

Page 19


The Weighted Unknown Drop Rate is normally used to indicate items that have both a high

number of drops that cannot be assigned to either circuit or packet switching, and a high

drop rate.

3.1.3 Normal releases

Normal Release

Calls - Drops

The sum of all the calls that end with completion codes that ariesoGEO has not assigned to

the drop category. The Normal Release metric includes blocked connections.

Normal Release Rate

(Calls - Drops) / Calls

The ratio of normal releases to connections, expressed as a percentage. If the number of

connections is 0, the normal release rate will also be 0.

3.2 Calls and connections

For information on how calls are defined in ariesoGEO, see ariesoGEO Concepts

The ariesoGEO call model on page 8.

Calls

The number of calls, as determined by the number of starting segments (segments whose

number is 0). This includes dropped and blocked calls.

Note: In the Top N Calling Subscribers analysis, the number of calls is instead calculated

based on the number of terminating segments.

Call ID

ID

The globally unique ID assigned to this call by ariesoGEO.

Number of Segments

Count

The number of call segments that meet the specified criteria. Call segments are of variable

length, but the majority are less than 60 seconds long.

Segment ID

Segment

The number of the segment. All calls begin with a segment 0. Segments with higher ID

numbers are later in the call, but the segment numbers are not necessarily consecutive.

Start Reason

The establishment reason for each segment. Establishment reasons for a segment may be

based on 3GPP messages such as Inter-RAT Cell Reselection or Call Re-

Page 20


establishment, or on ariesoGEO call segment start criteria such as RAB Change. For

information on how ariesoGEO defines call segments, see Call segments on page 8.

3.3 Cells

Common cell-related analysis details such as Label, Cell ID, RNC, ARFCN, PSC, and Site are

taken from the network information provided by the operator. These details are not

discussed further within this document.

Active Set

The cells in the active set for this call segment. ariesoGEO can track the active set for each

call using active set change messages in the call event data files.

Average Active Set Links

Total Active Set Seconds / Total Active Link Seconds

The ratio of active set seconds to link seconds for the specified bin during the specified time

period.

Best Cell Footprint

The number of call segments where a selected cell or group of cells are the best server. The

best server in a bin is based on how frequently the cell is seen in the bin, and what Ec/Io

values are reported for it.

Conflict Score

The level of conflict for the selected scrambling code. This is calculated by weighting the

conflict with each cell according to the tier of that cell (the closeness of the neighbor

relationship).

For example, if a cell's PSC conflicted with the scrambling codes used by its neighbor the

Conflict Score would be 10 000. If it conflicted with its tier 3 neighbor the Conflict Score

would be 100.

Cumulative Conflict Score

Score

The level of conflict for the selected scrambling code. This is calculated by weighting all

conflicts according to the tier in which they occur (the closeness of the neighbor

relationship) and then summing them.

For example, if a cell's PSC conflicted with the scrambling codes used by its neighbor

(weighted 10 000) and its tier 3 neighbor (weighted 100) the score for that scrambling code

for that cell would be 10 100.

Missing Label

The name of the missing target cell.

Page 21


PollutedBins

The number of bins for which the cell is considered a polluter.

In the Pilot Pollution Top Polluters analysis, a cell is considered a polluter in a bin when it is

detected but is not the best cell. In the Pilot Pollution NdB analysis, polluters are defined by

a user-selected parameter.

RelativePollutedBinsPercent

( Polluted Bins / Selected Bins ) * 100

The ratio between the number of bins for which the cell is considered a polluter, and the

number of bins in the selection.

Source Label

The name of the source cell whose neighbor list includes the missing target cell.

Target Tier

The closeness of the neighbour relationship between the target cell and the source cell,

from 1-4. If the target cell is in the source cell's neighbor list, it is considered to be in Target

Tier 1. If the target is the neighbor of a neighbor, it will be in Target Tier 2, and so on.

3.4 Completion Codes

Combined Network View

Shows the termination category assigned to a call segment, such as drop or block. Network

View values are based on combined completion codes, each of which ariesoGEO assigns to a

single category using a lookup table. For more information on Network View termination

categories, see Network View (Combined) on page 39.

Completion Code (Combined)

Completion

The most detailed completion code of those available.

In order of decreasing preference, the combined completion code is set to:

1. The same as Completion Code (vendor specific)

2. The same as Completion Code (RANAP)

3. The same as Completion Code (RRC)

4. Unknown

The completion codes are shown in the format source - completion_code for example:

Ericsson UMTS - Power Exhaustion-RN_DL_POWER

Ranap - Failure in the radio interface procedure

Page 22


Note: For NSN completion codes, the source is shown as Emil. For example, Emil UMTS -

RAB release - Transmission Failure would be an NSN-specific completion

code.

If no completion code is available, ariesoGEO sets the combined completion code to

Unknown.

Completion Code (RANAP)

The RANAP completion code assigned to a call segment.

Completion Code (RRC)

The RRC completion code assigned to a call segment.

Completion Code (Vendor Specific)

Completion

The vendor-specific (for example, NSN or Ericsson) completion code assigned to a call

segment. Depending on the analysis, ariesoGEO may or may not indicate which vendor is

the source for each completion code.

3.5 Devices and subscribers

Device DL HS Category

Category

The HSDPA category of the device, including the maximum downlink speed supported.

Device UL HS Category

Category

The HSUPA category of the device, including the maximum uplink speed supported.

UE Transmit Power (Average)

UE TX Power

Log10 ( Sum of Linear TX Powers / Number of Linear TX Power

measurements )

Where

Linear TX Power = (RSCP / 10)10

The UE transmit (TX) power, averaged over the number of call segments for which a UE TX

power is recorded. The UE TX power recorded for each call segment is the median of the set

of UE transmit power measurements made during the course of the segment.

Because UE TX power is a logarithmic scale, it must be converted to a linear scale in order to

calculate a meaningful average. The linear average is then converted back to a logarithmic

UE TX power value.

Page 23


IMSI

Subscriber

The IMSI number. This is shown as encrypted for non-authorized users.

IMEI

The IMEI number. This is shown as encrypted for non-authorized users.

Subscriber List

The list a subscriber belongs to (if any). For more information about lists, see Filters on page

32.

SV

The software version installed on the device at the time of the call. This is taken from the

IMEISV number.

3.6 Ec/Io

Best Server

Best Server Original

The best server is based on how frequently the cell is seen in the bin, and what Ec/Io values

are reported for it.

This is calculated by converting all the Ec/Io values reported for that bin into linear values,

and summing each cell's linear Ec/Io values to give a total Ec/Io for each cell. This value is

compared to that of the other cells in the bin.

Best Server Tuned

The best server in each bin after the antenna configuration is changed.

Ec/Io Average

Log10 ( Sum of Linear EcIo / Number of EcIo measurements )

Where

Linear EcIo = (EcIo / 10)10

The Ec/Io of the best cell of the active set, averaged over the number of call segments for

which an Ec/Io is recorded.

Because Ec/Io is a logarithmic scale, it must be converted to a linear scale in order to


Ec/Io value.

In the Ec/Io Histogram (Average) analysis, the Ec/Io( Average) shows the number of bins for

which the listed entry is the average Ec/Io.

Page 24


Ec/Io (Best) (Average)

The average signal to noise ratio of the best server in each bin.

Ec/Io Median

The median value from the set of Ec/Io values recorded for the relevant call segments.

Ec/Io Original

The best Ec/Io value for each bin within the area.

Ec/Io Tuned

The calculated best Ec/Io value for each bin within the area, after the antenna configuration

is changed.

The algorithm used in optimization of individual antenna changes does not extrapolate what

the Ec/Io would be in bins in which the cell was not previously seen. It also does not

consider the effects of any change in the best server.

Ec/Io Sector Footprint (Best)

The signal to noise ratio of the best server in each bin.

Ec/Io (Strongest) (Average)

The average signal to noise ratio of the strongest server in each bin. The strongest server is

based on how frequently the cell is seen in the bin, and what RSCP values are reported for it.

Footprint Ec/Io (Average)

The average signal to noise ratio of the selected cell in each bin.

Footprint Ec/Io Original

The signal to noise ratio in all bins in which the cell was detected.

Footprint Ec/Io Tuned

The calculated signal to noise ratio, after the change in antenna configuration, in all bins in

which the cell was originally detected.

The algorithm used in optimization of individual antenna changes does not extrapolate what

the Ec/Io would be in bins in which the cell was not previously seen. It also does not

consider the effects of any change in the best server.

3.7 Geolocation and Distance

Classification

The speed at which the subscriber was moving during the call segment.

Note: This metric is only available on systems that have the GeolocationMobility license. On

unlicensed systems, all classifications appear as Unknown.

The mobility categories are:

Page 25


• Stationary Call segments in which the subscriber was stationary, or moving back and

forth.

• Pedestrian Call segments in which the subscriber was moving slowly.

• Vehicular Call segments in which the subscriber was moving fast.

• Unknown Call segments where the speed could not be calculated, usually because the

duration of the connection was short (less than 5 segments).

Confidence

The confidence level of the geolocation. This is calculated from the level of consistency

between measurement reports, propagation delays and cells. Call segments can have a

confidence value of between 0 and 1, where values under 0.001 are considered low

confidence.

Note: The confidence level does not indicate how precisely the call segment has been

geolocated, and cannot be translated into an area approximation. It only indicates how

confident ariesoGEO is that the segment's location is correct.

Distance

Nearest Cell Distance

The distance (in km) between the source cell and the target cell.

In the Performance KPIs v Distance and Cell Performance KPIs v Distance analyses, the

distance is the distance from the cell, in meters. The KPIs are listed by distance bands, which

can be changed by editing the Binned Distance parameter.

Geolocated?

Whether a call has been geolocated. Call segments will not be geolocated if there is no

location information available for that connection.

Geolocation Type

The geolocation algorithm used to geolocate the segment. For information on the different

algorithms, see Geolocation on page 10.

Propagation Delay

If known, the propagation delay between the UE and the serving cell. This is measured in 3

chip units. For example, a propagation delay of 4 would mean 12 chips. The propagation

delay is used in some geolocation calculations.

3.8 IFHO and IRAT

Call Count (IFHO)

The number of call segments for which an inter-frequency handoff is recorded. This is based

on the point locations of the call segments (which are to the nearest meter) rather than bins

or cells.

Page 26


Call Count (IRAT)

The number of call segments for which an IRAT hand down is recorded for each location

shown on the raster map. This is based on the point locations of the call segments (which

are to the nearest meter) rather than bins or cells.

IFHO

Intra-Frequency Handovers

The number of call segments where an inter-frequency handoff has occurred.

End Reason (IRAT)

IRAT Handovers

The number of call segments where an IRAT hand down has occurred.

3.9 Load chain

#Cells

The number of cells for which data was loaded into the database.

#Cells Queried

The number of cells for which information was retrieved from the network tables.

#Cells Missing

The number of cells for which data was loaded but which could not be found in the network

tables.

#SC Missing

The number of occasions on which the parser encountered a scrambling code that it could

not recognise as one belonging to a nearby cell.

Calls Loaded

The number of calls in the loaded data.

Data Availability

The proportion of the specified time period for which data is available. This is based on

events rather than on numbers of files, so if unusually few events happened during parts of

the period the data availability may show 99% or even 98%.

A data availability of 97% or lower may indicate a problem with data loading for the relevant

period.

Errors

The number of errors encountered during data loading of the specified period.

LastSeen

The most recent fifteen-minute period for which ariesoGEO detected files in the specific

RNC's data directory. For more information, see Loading data on page 11.

Page 27


LastLoaded

The most recent fifteen-minute period for which data was loaded into the database.

Loaded Mbytes

The total size of the GLR files loaded into the database for that period. This is normally

different from the amount of data parsed, because Parsed Mbytes is based on the files input

to the parser, whereas Loaded Mbytes is based on the files output by the geolocation

process. However very large differences between the Parsed Mbyes and Loaded Mbytes

may indicate a problem, either in the load chain or with the initial data.

Message

The error message given for the failed file.

Parsed Files

The number of files from the RNCs that were successfully parsed.

An RNC file can contain data relating to multiple ariesoGEO periods. In that case, the file

would be counted multiple times, once for each of the periods it contains data for.

Parsed Mbytes

The total file size of the files from the RNCs, containing data for the specified period, that

were successfully parsed.

An RNC file can contain data relating to multiple ariesoGEO periods. In that case, the file

would be counted multiple times, once for each of the periods it contains data for.

Period

The fifteen-minute time period. This is based on the internal Tcode. For more information

on Tcode see page 30.

Segments Loaded

The number of call segments loaded into the database.

Stage

The stage in the load chain reached by the files from this period. For all periods but the

most recent this should be Loader, indicating that they have been loaded into the database.

3.10 RSCP

Footprint RSCP (Average)

The average signal strength in all bins in which the cell was detected.

Footprint RSCP Original

The signal strength in all bins in which the cell was detected.

Page 28


Footprint RSCP Tuned

The calculated signal strength, after the change in antenna configuration, in all bins in which

the cell was originally detected.

The algorithm used in optimization does not extrapolate what the signal strength would be

in bins in which the cell was not previously seen.

Processed RSCP

The RSCP for each bin, adjusted to account for the lower reporting rate of low values. The

Processed RSCP metric also shows the probable RSCP for bins where only the Ec/Io value is

known. This is intended to provide a more realistic view of actual subscriber experience.

To account for the lower reporting rate of low RSCP values, the RSCP of the cell seen most

often in a bin is taken as a standard, and the RSCP of every other cell seen in that bin is

adjusted downwards.

The recorded and adjusted RSCP values are then used to build a model for each cell, which is

used to fill in the RSCP values for missing bins.

RSCP (Average)

Log10 ( Sum of Linear RSCP / Number of RSCP measurements )

Where

Linear RSCP = (RSCP / 10)10

The signal strength of the best cell of the active set, averaged over the number of call

segments for which an RSCP is recorded.

Because RSCP is a logarithmic scale, it must be converted to a linear scale in order to


RSCP value.

In the RSCP Histogram (Average) analysis, the RSCP(Average) shows the number of bins for

which the listed entry is the average RSCP.

RSCP (Best) (Average)

The average RSCP reported for the best serving cell in each bin. The best server is based on

how frequently the cell is seen in the bin, and what Ec/Io values are reported for it.

RSCP (Median)

The median value from the set of RSCP values recorded for the relevant call segments.

RSCP Original

The best original RSCP value in each bin within the selected area.

Page 29


RSCP Tuned

The calculated best RSCP value for each bin within the selected area, after the antenna

configuration is changed.

RSCP (Strongest) (Average)

The average RSCP reported for the strongest serving cell in each bin. The strongest server is

based on how frequently the cell is seen in the bin, and what RSCP values are reported for it.

Strongest Server Original

The strongest server is based on how frequently the cell is seen in the bin, and what RSCP


This is calculated by converting all the RSCP values reported for that bin into linear values,

and summing each cell's linear RSCP values to give a total RSCP for each cell. This value is


Strongest Server Tuned

The cell that is calculated as having the best RSCP in each bin after the antenna

configuration is changed.

3.11 Throughput

Avg Downlink Throughput (kbit/s)

Data Throughput DL (kbits/sec)

The downlink volume recorded for each call segment (including retransmissions), summed

across all the segments and divided by the total of the data durations (in ms) recorded for

each segment.

Multiplying the volume by 1000 gives a value in bit/ms, which is the same as kbit/s.

Avg Uplink Throughput (kbit/s)

Mean Data Throughput UL (kbit/s)

The uplink volume (in kbit) recorded for each call segment, summed across all the segments

and divided by the total of the data durations (in ms) recorded for each segment.

Max Downlink Throughput (kbit/s)

The maximum downlink throughput recorded.

For analyses based on the call table, this is the maximum downlink throughput for a call

segment. For analyses based on the CellSummary table, this is the maximum downlink

throughput recorded for a cell.

Max Uplink Throughput (kbit/s)

Max Data Throughput UL (kbit/s)

The maximum uplink throughput recorded for a call segment.

Page 30


For analyses based on the call table, this is the maximum uplink throughput for a call

segment. For analyses based on the CellSummary table, this is the maximum uplink

throughput recorded for a cell.

3.12 Time and duration

Period Start Time

The starting time of the 15-minute period in which the call started. For daily analyses, such

as the Count By Day analysis, the Period Start Time is a day. Call details are assigned to the

day in which the period containing the call began.

Duration (secs)

Seconds of Use

Duration in Milliseconds / 1000

The duration recorded for each relevant call segment, summed across all the segments.

Call segment durations are recorded in ms. For the Seconds of Use metric, the call segment

durations are first summed and then divided by 1000.

Propagation Delay

See Geolocation and Distance on page 24.

Seconds

The peak seconds of use. This metric is used in the Busy Hour analyses.

Start Time

The start time of the call or segment, in the UTC timezone. The start time for a call is the

start time of segment 0.

Tcode

The internal calendar code used by ariesoGEO to uniquely identify each 15-minute period.

This is of the form YYYYMMDDHHQ, where HH is the hour (starting at 01) and Q is the period

(from 1 to 4). For example, the Tcode 20130501034 would indicate the period starting at

02:45 on the 1st of May. All times given are UTC.

3.13 Volume and traffic

Downlink Volume

Volume DL (kbit)

The sum of the total number of kilobits sent over the downlink, including retransmissions.

For analyses based on the call table, this is the total volume for the relevant call segments.

For analyses based on the CellSummary table, this is the total volume for the relevant cell

cells.

Page 31


Retransmission Rate UL

(Uplink Volume - User Uplink Volume) / User Uplink Volume

The retransmission rate is the ratio of the retransmission volume to the total uplink volume.

It is normally expressed as a number between 0 and 1. If the number of retransmissions is 0,

the retransmission rate will also be 0.

Retransmission Rate DL

(Downlink Volume - User Downlink Volume) / User Downlink Volume

The retransmission rate is the ratio of the retransmission volume to the total downlink

volume. It is normally expressed as a number between 0 and 1. If the number of

retransmissions is 0, the retransmission rate will also be 0.

Traffic Density (mErl/Km2)

The traffic density for each bin during the specified period of time. Bin size is stored in

meters, but the result is converted into km2 during the calculation.

Traffic Volume (MOU)

The total duration of all call segments that used this device, cell or other item, shown in

minutes.

Call segment durations are usually measured in ms, though some summary tables record

them in seconds. The durations recorded are therefore divided by either 60 000 or 60 to

convert them into minutes. Note that the digits after the decimal point show hundredths of

a minute, not seconds.

For example, if three subscribers made calls within a cell, each call lasting for 329 seconds

(approximately 5 ½ minutes), the Traffic Volume (MOU) for that cell would be 16.45

minutes.

Uplink Volume

Volume UL (kbit)

The sum of the total number of kilobits sent over the uplink, including retransmissions.

For analyses based on the call table, this is the total volume for the selected call segments.

For analyses based on the CellSummary table, this is the total volume for the selected cells.

User Downlink Volume

Downlink Volume [User]

The sum of the total number of kilobits sent over the downlink, not including

retransmissions.

User Uplink Volume

Uplink Volume [User]

The sum of the total number of kilobits sent over the uplink, not including retransmissions.

Page 32


4. Filters

Almost every analysis requires you to set filters in order to reduce the amount of data that

must be processed and displayed. Multiple filters act as AND conditions. For example, if you

set a Geographic Area filter and a Time Period filter, the analysis will only show calls that

occur within that area during that time period.

Filtering is especially important when using analyses based on the call table. Running

analyses on large sets of data, especially over long time periods, can seriously slow down the

system. This means that analysis results are always based on a specific subset of the data.

Some analyses will start running immediately when they are added to a canvas. For this

reason it may be helpful to uncheck the Enable Running of Analyses checkbox when setting

up a new analysis, and only enable analyses again once all the filters have been set.

Filters are hierarchical. By default, each analysis inherits the filters of the presentation

canvas, which in turn inherits the filters of the document. New documents use the time

period, geographic area and, for call table analyses, geolocation confidence level set in File >

Options.

In most cases, problems with analyses are caused by incorrectly set filters. If the filter

applied to the analysis is correct, it is important to check the canvas and document filters as

well.

Lists and variables

A filter cannot include more than 50 values. To filter by more than 50 values, create (or

import) a list containing all the values you want to filter by.

Variables are used to standardize filter values across a variety of different analyses. For

example, you could create a variable for a specific set of combined failure codes. Different

filters could then use this same variable to produce comparable data in a number of

different analyses.

Lists and variables cannot be used with every filter. The individual filter descriptions indicate

whether lists and variables can be used with that filter.

Excluding data

Some filters enable you to filter out the data you do not want instead of filtering in the data

that you do. To do this, select the categories of data to exclude from the analysis and check

the Is Negative checkbox. The individual filter descriptions indicate whether each filter can

be used as a negative filter.

Page 33


4.1 Common filters

Time Period

The Time Period filter is a Common filter that allows the user to specify the time period of

interest for the filter. The user can use a variable, define specific Start and End dates and

times, or specify a time period relative to the current time in days, weeks or months. When

specifying a relative time period, the period start time will default to the start of the day,

rather than the current time.

The summary tables record information for fifteen-minute or hourly periods, rather than at

specific times. For analyses based on the summary tables, setting the time period selects all

fifteen-minute or hourly periods that overlap with the time period set. For example, setting

a time period from 00:14:59 to 00:30:00 on an analysis based on a fifteen-minute summary

table would select the data for the three time periods starting at 00:00:00, 00:15:00 and

00:30:00.

If this filter is not set, the time period defaults to the previous five days.

• List or variable: Variable

• Negative filter: No

Geographic Area

The Geographical Area filter is a Common filter that allows the user to specify a specific

geographical boundary. There are several options for applying such a geographical filter:

• Use a variable (such as the Document Bounds, Network Bounds or Loaded Data

Bounds) to define the filter area.

• Select the minimum and maximum area co-ordinates in Latitude-Longitude format, or

drag the visible map area onto the filter using the icon at the bottom right of the map

control.

• Draw a polygon, or use a saved polygon, to filter based on a non-rectangular area.

For point analyses such as Block Locations, every point within the filtered area will be

included. For analyses based on cells (such as analyses based on the CellSummary table),

the cells contained within the filtered area will be included. For analyses based on bins (such

as analyses based on the SignalSummary or ServerSummary tables), a bin will be included in

the analysis if its center is within the geographical boundary.



Day Hour Settings

The Day Hour Settings filter is a Common filter that allows the user to filter analyses based

on the day, hour, or busy hour.

Page 34


To filter by busy hour, select one of the following:

• Single Busiest Hour filtered by Day/Hours below: The single busiest hour of the days

and hours selected.

• Average Busiest Hour filtered by Day/Hours below: The average busiest hour over the

days and hours selected.

Note: Analyses filtered by the Single Busiest Hour will only include data for a single hour.

Note: The busiest hour is determined according to the other filters used. It is not the busiest

hour over the entire network.

For example, if the Time Period filter included 21 days, the Single Busiest Hour filter would

produce data for the one busiest hour over the 21 day period. The Average Busiest Hour

filter would produce data for the same hour for all 21 days.



Cell

The Cell filter allows the user to filter by the starting cell of a call segment.

Note: For dropped call analyses, the Cell filter filters by the ending cell of a call segment.

• List or variable: Both

• Negative filter: Yes

Country

The Country filter filters by subscriber country of origin.

The Country lookups in ariesoGEO are based upon the Mobile Country Code, with a matched

text string allowing natural language filtering. A default Country List is provided with

ariesoGEO, but can also be updated by a system administrator.



Device

The Device filter is a Common filter that enables the user to filter by UE type.

The Device lookups in ariesoGEO are based upon the Type Allocation Codes (TAC) assigned

to each make and model of mobile device. The filter permits a matched text string allowing

natural language filtering. A default TAC List is provided with ariesoGEO, but can also be

updated by a system administrator.

Page 35


Note: The Device filter is similar to the TAC filter in that both provide searches based on TAC

details. However, the TAC filter searches directly for TAC values while the Device filter

performs a look-up to present TAC values in terms of device makes and models.



GEO Area

The GEO Area filter is only used for Administrative analyses. It is used to monitor ariesoGEO

system performance for a specific partition of the ariesoGEO database, relating to a specific

time zone or region.



ID

The ID filter allows the user to filter by Call ID, which is a unique key generated by

ariesoGEO.



IMEI

The IMEI filter allows the user to filter by International Mobile Equipment Identity (IMEI) or

Type Allocation Code (TAC).

Note: Reports filtered by IMEI will contain sensitive personal data. This data is shown in an

encrypted form unless the user has permission to view it.

Note: IMEI is not reported for all calls. ariesoGEO maintains a memory of the last IMEI that

an International Mobile Subscriber Identity (IMSI) was observed to use, enabling calls to

be associated with an IMEI even when no IMEI was reported.



Mobility

The Mobility filter enables the user to filter call segments according to the speed at which

the subscriber was moving.

Note: This filter is only available on systems that have the GeolocationMobility license.

The mobility categories are:

• Stationary Call segments in which the subscriber was stationary, or moving back and

forth.

• Pedestrian Call segments in which the subscriber was moving slowly.

Page 36


• Vehicular Call segments in which the subscriber was moving fast.

• Unknown Call segments where the speed could not be calculated, usually because the

duration of the connection was short (less than 5 segments).



Roamer

The Roamer filter allows the user to filter by subscriber network of origin.

Roamer lookups in ariesoGEO are based upon the Mobile Country Code (MCC) and Mobile

Network Code (MNC). Users are classified as Home Subscriber or Roamer Subscriber

according to whether their MCC and MNC corresponds to that assigned to the network.



Service Group

Services are classified into the following Service Groups using a lookup:

• HSData: Bearers identified as carrying data services via the high speed shared packet

data channel

• LSData: Bearers identified as carrying directly negotiated data services on GPRS or UMTS

"R99" air interface connection

• MultiRAB: Bearers identified as carrying multiple service types simultaneously

• None: No identified connection between the UE and the network

• Signalling: Signaling connection used.

• Voice: Bearers identified as carrying circuit-switched connectivity for voice calls



Subscriber

The Subscriber filter is a Common filter which allows the user to filter directly by

International Mobile Subscriber Identity (IMSI). Since the IMSI begins with the MCC and

MNC, this means the Subscriber filter can also be used to filter by these.

Note: Reports filtered by Subscriber will contain sensitive personal data. This data is shown

in an encrypted form unless the user has permission to view it.



Page 37


Subscriber Home Network

The Subscriber Home Network filter is a Common filter that allows the user to filter by

subscriber network of origin. The Subscriber Home Network lookups in ariesoGEO are based

on the Mobile Country Code (MCC) and Mobile Network Code (MCC), with a matched text

string allowing natural language filtering. A default Subscriber Home Network List is

provided with ariesoGEO, but can also be updated by a system administrator.



TAC

The TAC filter is a Common filter that allows the user to filter by Type Allocation Codes

(TAC). The filter permits a matched text string allowing natural language filtering.

Note: The TAC filter is similar to the Device filter in that both provide searches based on TAC

details. The distinction is that the TAC filter searches directly for TAC values while the

Device filter performs a look-up to present TAC values in textual terms of device makes

and models.



Technology

The Technology filter is a Common filter that allows the user to filter directly by technology,

that is by one or more of GSM, UMTS and LTE. This filter is only available for Common

analyses that may search over multiple technologies.



VIP

The VIP filter is a Common filter that allows the user to filter by the named subscribers

defined in their VIP Lists. VIP filters can enable simple follow up of problems identified in

VIP Web Reporting.

Filter options



4.2 UMTS filters

The following filters are only available for UMTS analyses. For more information on these

analyses see UMTS analyses on page 44.

Page 38


ARFCN

The ARFCN filter allows the user to filter by Absolute Radio Frequency Channel Number, also

sometimes called the carrier.

If an ARFCN filter is not set, some analyses may be misleading. For example, Best Server

analyses may combine carrier layers.



Completion Code (Combined)

The Completion Code (Combined) filter is a UMTS-specific filter that allows the user to filter

by the most detailed completion code available. Filtering by the combined completion code

finds records with the specified completion code only if no more detailed code is available

for that record.

Note: This means that, for example, filtering by an RRC completion code may return very

few results because in most cases that RRC code has been superseded by a more

informative RANAP or vendor-specific completion code.

In order of decreasing preference, the combined completion code is set to:

5. The same as Completion Code (vendor specific)

6. The same as Completion Code (RANAP)

7. The same as Completion Code (RRC)

8. Unknown

The completion codes are shown in the format source - completion_code for example:

Ericsson UMTS - Power Exhaustion-RN_DL_POWER

Ranap - Failure in the radio interface procedure

Note: For NSN completion codes, the source is shown as Emil. For example, Emil UMTS -

RAB release - Transmission Failure would be an NSN-specific completion

code.

Completion codes are combined into categories by the Network View filters.



Completion Code (RANAP)

The RANAP Completion Codes in ariesoGEO are taken from the RANAP Iu Release

command.



Page 39


Completion Code (RRC)

The RRC Completion Codes in ariesoGEO are taken from the RRC Connection Release

message.



Completion Code (Vendor Specific)

This filter is shown in ariesoGEO as, for example, Completion Code (NSN).

The Ericsson Completion Codes in ariesoGEO are taken from GPEH

Internal_System_Block and Internal_System_Release messages.

The NSN Completion Codes in ariesoGEO are taken from the PMI_Ticket message.



Establishment

The Establishment filter is a UMTS-specific filter that allows the user to filter by connection

establishment type.



Network View (Combined)

4.3 The Network View (Combined) filter is a UMTS-specific

filter which allows the user to filter call segments according

to their termination category, such as drop or block. Network

View values are based on combined completion codes, each of

which ariesoGEO assigns to a single category using a lookup

table. For more information on combined completion codes,

see Cells

Common cell-related analysis details such as Label, Cell ID, RNC, ARFCN, PSC, and Site are

taken from the network information provided by the operator. These details are not

discussed further within this document.

Active Set

The cells in the active set for this call segment. ariesoGEO can track the active set for each

call using active set change messages in the call event data files.

Page 40


Average Active Set Links

Total Active Set Seconds / Total Active Link Seconds

The ratio of active set seconds to link seconds for the specified bin during the specified time

period.

Best Cell Footprint

The number of call segments where a selected cell or group of cells are the best server. The

best server in a bin is based on how frequently the cell is seen in the bin, and what Ec/Io


Conflict Score

The level of conflict for the selected scrambling code. This is calculated by weighting the

conflict with each cell according to the tier of that cell (the closeness of the neighbor

relationship).

For example, if a cell's PSC conflicted with the scrambling codes used by its neighbor the

Conflict Score would be 10 000. If it conflicted with its tier 3 neighbor the Conflict Score

would be 100.

Cumulative Conflict Score

Score

The level of conflict for the selected scrambling code. This is calculated by weighting all

conflicts according to the tier in which they occur (the closeness of the neighbor

relationship) and then summing them.

For example, if a cell's PSC conflicted with the scrambling codes used by its neighbor

(weighted 10 000) and its tier 3 neighbor (weighted 100) the score for that scrambling code

for that cell would be 10 100.

Missing Label

The name of the missing target cell.

PollutedBins

The number of bins for which the cell is considered a polluter.

In the Pilot Pollution Top Polluters analysis, a cell is considered a polluter in a bin when it is

detected but is not the best cell. In the Pilot Pollution NdB analysis, polluters are defined by

a user-selected parameter.

RelativePollutedBinsPercent

( Polluted Bins / Selected Bins ) * 100

The ratio between the number of bins for which the cell is considered a polluter, and the

number of bins in the selection.

Page 41


Source Label

The name of the source cell whose neighbor list includes the missing target cell.

Target Tier

The closeness of the neighbour relationship between the target cell and the source cell,

from 1-4. If the target cell is in the source cell's neighbor list, it is considered to be in Target

Tier 1. If the target is the neighbor of a neighbor, it will be in Target Tier 2, and so on.

Completion Codes on page 20.

The call termination categories are:

• Block Call segments identified as terminating due to a call block, an abnormal

termination of a request for a bearer, for example due to resource exhaustion.

• Drop Call segments identified as terminating due to a call drop, an abnormal termination

for a reason other than resource exhaustion.

• Continuation Call segments identified as preceding further call segments.

• Normal Call segments identified as terminating a call normally.

• Unknown Call segments with an unknown reason for termination (due to missing

messages).

• Unspecified Call segments with an unspecified completion code.



Network View (RANAP)

The Network View (RANAP) filter is a UMTS-specific filter which allows the user to filter call

segments according to their RANAP termination category, such as drop or block.



Network View (RRC)

The Network View (RRC) filter is a UMTS-specific filter which allows the user to filter call

segments according to their RRC termination category, such as drop or block.



Network View (Vendor Specific)

The Network View (Vendor Specific) filter is a UMTS-specific filter which allows the user to

filter call segments according to their vendor-specific termination category, such as drop or

block.


Page 42



RNC

The RNC filter is a UMTS-specific filter that allows the user to filter by cells served by the

specified RNC.



Scrambling Code

The Scrambling Code filter is a UMTS-specific filter that enables the user to filter by cells that

use a specific Primary Scrambling Code.

Note: In the Scrambling Code Suggestions analyses, this filter restricts the list of

recommended scrambling codes, rather than the cells considered.



Service

The Service filter is a UMTS-specific filter that allows the user to filter by specific service,

such as Voice & HS or Cell FACH. Service in ariesoGEO indicates a text definition of service

derived from the assigned Radio Access Bearer.

Services are combined into categories by the Service Group filter.



UE Capabilities

The UE Capabilities filter is a UMTS-specific filter that allows the user to filter by device

capabilities, such as support of compressed mode, GSM, or Multi-carrier operation.



UE Downlink Category

The UE Downlink Category filter is a UMTS-specific filter that allows the user to filter by

HSDPA UE category.



UE Power Class

The UE Power Class filter is a UMTS-specific filter that allows the user to filter by UE power

class.

Page 43




UE Release Indicator

The UE Release Indicator filter is a UMTS-specific filter which allows the user to filter by UE

release indicator, such as R99 or Rel11.



UE Uplink Category

The UE Uplink Category filter is a UMTS-specific filter that allows the user to filter by HSUPA

UE category.



Page 44


5. Analyses

Each analysis runs against one or more database tables. Most analyses run against one of

the summary tables, but some analyses run directly against call data and others may use

multiple tables to return information relating to both calls and cells.

When comparing analyses, remember that similar analyses that run against different tables

may produce slightly different results. This is especially true when comparing summary

analyses with call table analyses, or analyses based on bin summaries with analyses based

on cell summaries.

5.1 UMTS analyses

5.1.1 UMTS database tables

The database table used by an analysis determines what information can be shown, what

filters can be used, and how geographical filtering works. For example, analyses based on

the BinSummary table include call segments based on the central location of the bin in

which they are located, whereas analyses based on the CellSummary table include call

segments based on the location of the cell to which they are assigned.

Information about the main tables used by analyses is provided below.

BinSummary Table

A summary of the performance within a geographic bin. By default a bin is a 50m by 50m

square. This table is updated on an hourly basis.

Columns include the number of call segments, drops and blocks, and the seconds of use.

Analyses based on the BinSummary table can be filtered by area, service, carrier and time.

Filtering by area filters by map bins within the selected area.

Call Table

The call table contains full details of every single call segment loaded into the ariesoGEO

database. Most analyses only retrieve call segments that are geolocated to a minimum

confidence value, but some analyses retrieve all call segments that meet the conditions in

the filter.

The call table is very large, so analyses based on the call table should be filtered to include as

few call segments as possible or they may take a very long time to run. Filtering by area

filters by the point location of each call segment.

Page 45


CellSummary Table

A summary of the performance within a cell. This table records call segments (including

non-geolocated call segments), drops and blocks, throughputs and volumes for each cell.

This table is updated every fifteen minutes.

Analyses based on the CellSummary table can be filtered by area, completion code, carrier

and time. Filtering by area filters by cell locations within the selected area.

DataSummary Table

A summary of the data performance within a geographic bin. This table is updated on an

hourly basis.

Columns include throughput and volume information for both uplink and downlink.

Analyses based on the DataSummaryH table can be filtered by service, carrier and time.

ServerSummary Table

A summary of the cell signal performance within a bin. This table is updated hourly.

Columns include the median SNR value and signal strength.

Analyses based on the ServerSummary table can be filtered by area, completion code,

carrier and time. Filtering by area filters by bins within the selected area.

SignalSummary Table

A summary of the RF performance within a bin. This table is updated on an hourly basis.

Columns include the median and linear totals of Ec/I0, RSCP and UE TXPower.

Analyses based on the SignalSummaryH table can be filtered by area, service, carrier and

time. Filtering by area filters by bins within the selected area.

5.1.2 UTMS analyses A-C

Active Network Cells

Displays details of all the cells within the applied filter.

• In folder: Network

• Data source: Network tables

• Type: Table

• Filters (required): -

• Filters (optional): ARFCN, BSC, Cell, Cell Band, Frequency Band, Geographic Area, Time

Period

• Metrics: Antenna Electrical Downtilt, ARFCN, Azimuth, Cell Type, CPICH, Latitude,

Longitude, Mech Downtilt, Position Type, Scrambling Code

Page 46


Area Data Performance Against Time

Provides throughput and volume information (uplink and downlink), summarized from the

bins in the selected area, for each hour period.

• In folder: Time Series

• Data source: DataSummary

• Type: Table, Chart

• Filters (one required): -

• Filters (optional): ARFCN, Day Hour Settings, Geographic Area, Service, Service Group,

Time Period

• Metrics: Avg Downlink Throughput, Avg Uplink Throughput, Downlink, Max Downlink

Throughput, Max Uplink Throughput, Period Start Time, Uplink Volume

Best Server

The best serving cell in each bin. The best server is based on how frequently the cell is seen

in the bin, and what Ec/Io values are reported for it.

This is calculated by converting all the Ec/Io values reported for that bin into linear values,

and summing each cell's linear Ec/Io values to give a total Ec/Io for each cell. This value is


• In folder: RF

• Data source: ServerSummary

• Type: Map


• Filters (optional): ARFCN, Cell, DayHour Settings, Geographic Area, RNC, Scrambling

Code, Time Period

Best Server Footprint RF KPIs

Displays a raster map with the best EC/I0 and RSCP recorded for the selected cell in all the

bins in which it is the best server. The best server is calculated based on how frequently the

cell is seen in the bin, and what Ec/Io values are reported for it.

• In folder: RF\Best Server


• Type: Multi-layer map

• Filters (one required): Cell

• Filters (optional): ARFCN, DayHour Settings, Geographic Area, RNC, Scrambling Code,

Time Period

• Metrics: Ec/Io Cell Footprint (Best), RSCP Cell Footprint (Best)

Best Server RF KPIs

Displays a raster map with the mean EC/I0 and RSCP of the best server in each bin.

Page 47






• Filters (optional): ARFCN, Day Hour Settings, Geographic Area, RNC, Scrambling Code,

Time Period

• Metrics: RSCP (Best) (Average), Ec/Io (Best) (Average)

Block Locations

Displays the point location of all completion codes defined by ariesoGEO as blocks. When

this is shown as a map analysis, the block locations are color coded according to whether

they are circuit-switched, packet-switched or signalling drops.

Block Locations showing block domains

This analysis shows UMTS blocks only. To see blocks on all technologies, use the Block

Locations analysis in the Common Analyses folders.

• In folder: Points

• Data source: Call Table

• Type: Map, Table

• Filters (one required): ARFCN, Cell, Completion Code (Combined), Completion Code

(Ericsson), Completion Code (NSN), Completion Code (RANAP), Completion Code (RRC),

Country, Device, Establishment, ID, IMEI, Network View (Combined), Network View

(RANAP), Network View (RRC), Network View (Vendor Specific), RNC, Roamer,

Scrambling Code, Service, Service Group, Subscriber, Subscriber Home Network, TAC,

VIP

• Filters (optional): DayHour Settings, Geographic Area, Time Period, UE Capabilities, UI

Downlink Category, UE Power Class, UE Release Indicator, UE Uplink Category

Page 48


• Metrics: Classification, Completion Code (Combined), Completion Code (RANAP),

Completion Code (RRC), Completion Code (Vendor Specific), NetworkView (Combined),

ID, IMSI, IMEI, Latitude, Longitude, Operator, Segment, Service, SV, TCode

Busy Hour (Daily RNC)

Shows details for the hour with the greatest average seconds of use across all the filtered

RNCs.

Note: The Rank metric in this analysis is a purely internal measure, and should always be 1.

• In folder: Busy Hour

• Data source: ServerBusyHours Table

• Type: Table


• Filters (optional): ARFCN, Cell, Completion Code (Combined), DayHour Settings,

Geographic Area, Network View (Combined), RNC, Scrambling Code, Service, Service

Group, Time Period

• Metrics: DayOfWeek, Hour, Rank, RNC, Seconds

Busy Hour (Daily Server)

Shows details for the hour with the greatest average seconds of use across all the filtered

cells.



• Type: Table




Group, Time Period


Busy Hour (Daily System)

Shows details for the hour with the greatest average seconds of use across the filter supplied

for the entire ariesoGEO area.



• Type: Table




Group, Time Period


Page 49


Busy Hour (Single RNC)

Shows details for the hour with the greatest seconds of use for each RNC filtered.



• Type: Table




Group, Time Period


Busy Hour (Single Server)

Shows details for the hour with the greatest seconds of use for each cell filtered.



• Type: Table




Group, Time Period


Busy Hour (Single System)

Shows details for the hour with the greatest average seconds of use across the filter supplied

for the entire ariesoGEO area.



• Type: Table




Group, Time Period


Call Count (Table)

Shows, for each service type, the number of blocks, drops, and calls started on that service.

Some services may show blocks and drops but no calls. This indicates that no calls started

on that service (no segment numbers of 0 are recorded for that service), but that some calls

then changed onto that service.

Page 50


• In folder: Calls

• Data source: CellSummary




Geographic Area, Network View (Combined), RNC, Scrambling Code, Service, Time

Period

• Metrics: Calls, CS Blocks, CS Drops, PS Blocks, PS Drops, Seconds, Service Name, Total

Blocks, Total Drops, Unknown Blocks, Unknown Drops

Call Table Analyses

The Call Table Analyses are a set of map layers showing information about different

performance metrics.

Each layer shows information based on the average for the bin, calculated across all the

filtered call segments in each bin.

• In folder: Call Table

• Data source: Call table







VIP

• Filters (optional): DayHour Settings, Geographic Area, Time Period, UE Capabilities, UE


• Metrics: Blocks, Block Rate, Call Count (IRAT), Call Count (IFHO), CS Blocks, CS Block

Rate, CS Drops, CS Drop Rate, CS Weighted Blocks, CS Weighted Drops, Drops, Drop

Rate, Ec/Io (Average), Ec/Io (Median), PS Blocks, PS Block Rate, PS Drops, PS Drop Rate,

PS Weighted Blocks, PS Weighted Drops, RSCP (Average), RSCP (Median), Signalling

Blocks, Signalling Block Rate, Signalling Drops, Signalling Drop Rate, Signalling Weighted

Blocks, Signalling Weighted Drops, Traffic Volume (MOU), Unknown Blocks, Unknown

Block Rate, Unknown Drops, Unknown Drop Rate, Unknown Weighted Blocks, Unknown

Weighted Drops, Weighted Drops, Weighted Blocks

Call Table Data KPIs

The Call Table Analyses are a set of map layers showing information about different volume

and throughput metrics.

Each layer shows information based on the average for the bin, calculated across all the

filtered call segments in each bin.

Page 51










VIP



• Metrics: Avg Downlink Throughput, Avg Uplink Throughput, Downlink Volume, Max

Downlink Throughput, Max Uplink Throughput, Uplink Volume

Calls Summary

Displays, for each call, the total uplink and downlink volumes, summed across all the

segments in that call.

Note: This analysis requires the Subscriber license.



• Type: Table

• Filters (required): ARFCN, Call ID, Cell, Completion Code (Combined), Completion Code

(RANAP), Completion Code (RRC), Completion Code (vendor specific), Country, Device,

Establishment Reason, IMEI, Network View (Combined), Network View (RANAP),

Network View (RRC), Network View (vendor specific), RNC, Roamer, Scrambling Code,

Service, Service Group, Subscriber, Subscriber Home Network, TAC, VIP

• Filters (optional): DayHour Settings, Geographic Area, UE Capabilities, UE Downlink

Category, UE Power Class, UE Release Indicator, UE Uplink Category

• Metrics: Downlink Volume, Downlink Volume [user], Duration (secs), Id, IMEI, IMSI, Start

time, SV, Uplink Volume, Uplink Volume [user]

Cell Daily Block Rate by RNC

Displays a table or chart showing the number of blocks for each RNC in each period.

• In folder: Subscriber and Cell




• Filters (optional): ARFCN, Cell, Completion Code (Combined), Day Hour Settings,


Group, Time Period

Page 52


• Metrics: Block Rate (%), Period

Cell Data Performance Against Time

Provides throughput and volume information (uplink and downlink), summarized from the

cells in the selected area, for each fifteen minute period.






Time Period

• Metrics: Avg Downlink Throughput, Avg Uplink Throughput, Downlink, Max Downlink

Throughput, Max Uplink Throughput, Period Start Time, Uplink Volume

Cell DL Data Throughput

Displays a table or chart showing data throughput performance for specific cells.

Note: This analysis requires the UMTSDataOptimization license.

Cell DL Data Throughput chart showing KPIs for ten cells

The Segment Average Throughput Threshold parameter can be used to exclude all segments

with a throughput below the threshold set. Setting the threshold very high may result in no

data appearing in the analysis.

You can also exclude very short data downloads from analysis using the Minimum Data

Percentage Threshold. This is the percentage of the call segment during which data was

downloaded.

• In folder: Performance\Cell Data Performance



• Filters (one required): RNC, Service, UE Downlink Category

Page 53


• Filters (optional): ARFCN, Cell, Completion Code (Combined), Completion Code


Country, Day Hour Settings, Device, Establishment, Geographic Area, ID, IMEI, Network

View (Combined), Network View (RANAP), Network View (RRC), Network View (Vendor

Specific), Roamer, Scrambling Code, Service Group, Subscriber, Subscriber Home

Network, TAC, Time Period, UE Capabilities, UE Power Class, UE Release Indicator, UE

Uplink Category, VIP

• Parameters: Segment Average Throughput Threshold, Minimum Data Percentage

Threshold

• Metrics: ARFCN, Cell ID, Label, Max Data Throughput DL (kbit/s), Mean Data Throughput

(kbit/s), Number of Segments, PSC, RNC, Site

Cell DL Data Throughput Histogram

Displays a table or chart showing the combined number of call segments in each throughput

band for one or more cells.


Cell DL Data Throughput Histogram for two cells

The lowest throughput band is set using the Segment Average Throughput Threshold

parameter. You can also exclude very short data downloads from analysis using the

Minimum Data Percentage Threshold. This is the percentage of the call segment that data

was downloaded for.










Page 54





Threshold

• Metrics: Max Data Throughput DL (kbit/s), Mean Data Throughput (kbit/s), Number of

Segments

Cell Footprint (Best)

Displays a raster map showing the number of call segments where a cell or group of cells are

the best server. The strongest server in a bin is based on how frequently the cell is seen in

the bin, and what Ec/Io values are reported for it.

• In folder: RF\Strongest Server


• Type: Map



Time Period

• Metrics: Best Cell Footprint

Cell Footprint (Strongest)

Displays a raster map showing the number of call segments where a cell or group of cells are

the strongest server. The strongest server in a bin is based on how frequently the cell is

seen in the bin, and what RSCP values are reported for it.



• Type: Map



Time Period

• Metrics: Strongest Cell Footprint

Cell Links Data Summary

Displays a table or chart showing throughput and volume information for individual cells.







Group, Time Period

Page 55


• Metrics: Avg Downlink Throughput (kbit/s), Avg Uplink Throughput (kbit/s), Downlink

Volume (kbit), Maximum Downlink Throughput (kbit/s), Maximum Uplink Throughput

(kbit/s), Uplink Volume (kbit)

Cell Performance

Displays a table or chart showing KPIs such as drops and blocks, as well as data volume and

throughput, for individual cells.







Group, Time Period

• Metrics: Avg Downlink Throughput (kbit/s), Avg Uplink Throughput (kbit/s), Block Rate

(%), CS Blocks, CS Block Rate (%), CS Drops, CS Drop Rate (%), Downlink Volume (kbit),

Drop Rate (%), Maximum Downlink Throughput (kbit/s), Maximum Uplink Throughput

(kbit/s), PS Blocks, PS Block Rate (%), PS Drops, PS Drop Rate (%), Signalling Blocks,

Signalling Block Rate (%), Signalling Drops, Signalling Drop Rate (%), Total Blocks, Total

Drops, Uplink Volume (kbit), Unknown Blocks, Unknown Block Rate (%), Unknown

Drops, Unknown Drop Rate (%)

Cell Performance KPIs vs Distance

Displays a table or chart showing how the KPIs for a single cell are affected by distance from

the cell.

Cell Performance KPIs v Distance with a Binned Distance of 500m

By default, the distance bands are 200m. This can be changed by editing the Binned

Distance parameter.

• In folder: Performance\Cell KPIs v Distance

Page 56




• Filters (required): Cell (one cell only)








• Parameters: Binned Distance

• Metrics: Blocks, Call Count, CS Blocks, CS Drops, Distance, Drops, Ec/Io Average, Normal

Release Count, PS Blocks, PS Drops, RSCP Average, Signalling Blocks, Signalling Drops,

Traffic MoU, UETxPower Average, Unknown Blocks, Unknown Drops

Cell Performance KPIs vs Distance Map

Displays a multi-layer map showing how the cell's KPIs are affected by distance from the cell.

Cell Performance KPIs vs Distance Map showing the call count at different distances

By default, the distance bands are 200m. This can be changed by editing the Binned

Distance parameter.

• In folder: Performance\Cell KPIs v Distance



• Filters (required): Cell (one cell only)





Page 57





• Parameters: Binned Distance

• Metrics: Blocks, Call Count, CS Blocks, CS Drops, Drops, Ec/Io Average, Normal Release

Count, PS Blocks, PS Drops, RSCP Average, Signalling Blocks, Signalling Drops, Traffic

MoU, UETxPower Average, Unknown Blocks, Unknown Drops

Cell UL Data Throughput

Displays a table or chart showing data throughput performance for specific cells.


The Segment Average Throughput Threshold parameter can be used to exclude all segments

with a throughput below the threshold set. Setting the threshold very high may result in no

data appearing in the analysis.

You can also exclude very short data uploads from analysis using the Minimum Data

Percentage Threshold. This is the percentage of the call segment during which data was

uploaded.













Threshold

• Metrics: ARFCN, Cell ID, Label, Max Data Throughput DL (kbit/s), Mean Data Throughput

(kbit/s), Number of Segments, PSC, RNC, Site

Cell UL Data Throughput Histogram

Displays a table or histogram showing the number of call segments in each throughput band

for one or more cells.


The lowest throughput band is set using the Segment Average Throughput Threshold

parameter. You can also exclude very short data uploads from analysis using the Minimum

Page 58


Data Percentage Threshold. This is the percentage of the call segment that data was

uploaded for.




• Filters (one required): RNC, Service, UE Uplink Category









Threshold

• Metrics: Max Data Throughput UL (kbit/s), Mean Data Throughput (kbit/s), Number of

Segments

Centroid of multiple locations

Displays the central point of all the selected segments, also called the mean position, either

as a point map or as a table. The locations of all the selected segments are equally

weighted.

• In folder: Centroid




(RANAP), Completion Code (RRC), Completion Code (Vendor Specific), Country, Device,

Establishment, ID, IMEI, Network View (Combined), Network View (RANAP), Network

View (RRC), Network View (Vendor Specific), RNC, Roamer, Scrambling Code, Service,

Service Group, Subscriber, Subscriber Home Network, TAC

• Filters (optional): Day Hour Settings, Device Software Version (SV), Geographic Area,

Time Period, UE Capabilities, UI Downlink Category, UE Power Class, UE Release

Indicator, UE Uplink Category

• Metrics: Latitude, Longitude, Type

Change Azimuth

Displays a raster map showing the projected KPIs for a single cell if the azimuth is changed.

Note: This analysis requires the AntennaTuning license.

The azimuth can be changed by between -30 degrees (anticlockwise) and 30 degrees

(clockwise).

Page 59


This analysis assumes flat terrain. If a bin contains no data for the selected cell within the

filters provided, then the analysis ignores that bin and does not extrapolate how the changes

would affect it. More sophisticated modeling is provided by the RF Shaping feature.

• In folder: Optimization\Antenna Tuning



• Filters (one required): - (Although the analysis will fail if run on too large an area)


Time Period

• Parameters: Cell to change, The azimuth delta value

• Metrics: Best Server Original, Best Server Tuned, Ec/Io Original, Ec/Io Tuned, Footprint

Ec/Io Original, Footprint Ec/Io Tuned, Footprint RSCP Original, Footprint RSCP Tuned,

RSCP Original, RSCP Tuned, Strongest Server Original, Strongest Server Tuned

Change Power

Displays a raster map showing the projected KPIs for a single cell if the power is changed.


The power can be changed by between -10 and +10 dB.



would affect it. More sophisticated modeling is provided by the RF Shaping feature.






Time Period

• Parameters: Cell to change, The power delta value (dB)




Change Tilt

Displays a raster map showing the projected KPIs for a single cell if the mechanical tilt is

changed.


The tilt can be changed by between can be changed by between -10 degrees (upward) and

10 degrees (downward).

Page 60




would affect it. Note this means that for upward changes in tilt the tuned footprint may

appear smaller than the actual. More sophisticated modeling is provided by the RF Shaping

feature.






Time Period

• Parameters: Cell to change, Choose the tilt delta value (deg)




Combined Failure Reasons

This analysis shows a summary of the number of calls that terminated with each combined

completion code, and the category (block, drop and so on) that code is assigned to.

Completion codes are only shown if at least one call terminated with that code.

• In folder: Failures


• Type: Table/Chart





Service Group, Subscriber, Subscriber Home Network, TAC, VIP



• Metrics: Completion Code (Combined), Count, Network View (Combined)

Count Against Time

Shows the total number of calls in the selected area, for each fifteen minute period.






Geographic Area, RNC, Scrambling Code, Service, Service Group, Time Period

Page 61


• Metrics: Calls, Period Start Time

Count By Day

Shows the total number of calls in the selected area, for each day period (00:00:00 to

23:59:59).

Note that Count By Day currently presents the UTC date of the data as being local date.

Arieso expects to address this in a future release.







• Metrics: Calls, Period Start Time

5.1.3 UTMS analyses D-L

Daily Block Rate by RNC

Displays a table or chart showing the block rate for each day for each RNC.






Geographic Area, Network View, RNC, Scrambling Code, Service, Service Group, Time

Period

• Metrics: Block Rate (%), Period

Daily Drop and Block Rate

Displays a table or chart showing the drop and block rate per day for each RNC.







Period

• Metrics: Block Rate (%), CS Block Rate (%), CS Drop Rate (%), Drop Rate (%), Period Start

Time, PS Block Rate (%), PS Drop Rate (%), RNC, Signalling Block Rate (%), Signalling Drop

Rate (%), Unknown Block Rate(%), Unknown Drop Rate (%)

Page 62


Daily Drop Rate by RNC

Displays a table or chart showing the drop rate for each day against each RNC.







Period

• Metrics: Drop Rate (%), Period

Data KPIs

Shows volumes and throughputs for each bin on a raster map, color-coded by size/rate.

• In folder: Performance

• Data source: DataSummary




Time Period

• Metrics: Avg Downlink Throughput (kbit/s), Avg Uplink Throughput (kbit/s), Max Uplink

Throughput (kbit/s), Uplink Volume (kbit), Downlink Volume (kbit)

Device Comparison

Lists RF performance and KPIs summed or averaged for each individual device within the

filter.

Note: This analysis requires the DeviceManagement license.

• In folder: Device and Subscriber\Device\Device Comparison

• Data Source: Device Summary

• Type: Table

• Filters (one required): Device

• Filters (optional): Day Hour Settings, Service, Service Group, Time Period

• Metrics: Average Data Throughput DL (kbit/s), Average Data Throughput UL (kbit/s),

Blocks, Block Rate (%), Calls, CS Blocks, CS Block Rate (%), CS Drops, CS Drop Rate (%), CS

Weighted Block Rate, CS Weighted Drop Rate, Device, Downlink Volume (kbit), Drops,

Drop Rate (%), ECI0 Average, End Reason IRAT, IFHO, Max Data Throughput DL (kbit/s),

Max Data Throughput UL (kbit/s), Seconds of Use, Normal Release Count, Normal

Release Rate, PS Blocks, PS Block Rate (%), PS Drops, PS Drop Rate (%), PS Weighted

Block Rate, PS Weighted Drop Rate, Retransmission Rate DL, Retransmission Rate UL,

RNC, RSCP Average, Signalling Blocks, Signalling Block Rate (%), Traffic Volume (MOU),

Unknown Blocks, Unknown Block Rate (%), Unknown Drops, Unknown Drop Rate (%),

Page 63


Unknown Weighted Block Rate, Unknown Weighted Drop Rate, Uplink Volume (kbit),

User Data Volume DL (kbit), User Data Volume UL (kbit), Ue Tx Power, Weighted Block

Rate, Weighted Drop Rate

Device Comparison By Cell

Lists RF performance and KPIs summed or averaged for each cell for the selected individual

devices.




• Type: Table



• Metrics: ARFCN, Average Data Throughput DL (kbit/s), Average Data Throughput UL

(kbit/s), Blocks, Block Rate (%), Calls, Cell ID, CS Blocks, CS Block Rate (%), CS Drops, CS

Drop Rate (%), CS Weighted Block Rate, CS Weighted Drop Rate, Device, Downlink

Volume (kbit), Drops, Drop Rate (%), ECI0 Average, End Reason IRAT, IFHO, Label, Max

Data Throughput DL (kbit/s), Max Data Throughput UL (kbit/s), Seconds of Use, Normal

Release Count, Normal Release Rate, PS Blocks, PS Block Rate (%), PSC, PS Drops, PS

Drop Rate (%), PS Weighted Block Rate, PS Weighted Drop Rate, Retransmission Rate DL,

Retransmission Rate UL, RNC, RSCP Average, Signalling Blocks, Signalling Block Rate (%),

Site, Traffic Volume (MOU), Unknown Blocks, Unknown Block Rate (%), Unknown Drops,

Unknown Drop Rate (%), Unknown Weighted Block Rate, Unknown Weighted Drop Rate,

Uplink Volume (kbit), User Data Volume DL (kbit), User Data Volume UL (kbit), Ue Tx

Power, Weighted Block Rate, Weighted Drop Rate

Device Comparison trend over time

Lists RF performance and KPIs summed or averaged for each fifteen-minute time period for

the selected individual devices.




• Type: Table





Weighted Block Rate, CS Weighted Drop Rate, Downlink Volume (kbit), Drops, Drop Rate

(%), ECI0 Average, End Reason IRAT, IFHO, Max Data Throughput DL (kbit/s), Max Data

Throughput UL (kbit/s), Seconds of Use, Normal Release Count, Normal Release Rate,

Page 64


Period Start Time, PS Blocks, PS Block Rate (%), PS Drops, PS Drop Rate (%), PS Weighted

Block Rate, PS Weighted Drop Rate, Retransmission Rate DL, Retransmission Rate UL,

RNC, RSCP Average, Signalling Blocks, Signalling Block Rate (%), Signalling Weighted

Block Rate, Traffic Volume (MOU), Unknown Blocks, Unknown Block Rate (%), Unknown

Drops, Unknown Drop Rate (%), Unknown Weighted Block Rate, Unknown Weighted

Drop Rate, Uplink Volume (kbit), User Data Volume DL (kbit), User Data Volume UL

(kbit), Ue Tx Power, Weighted Block Rate, Weighted Drop Rate

Device List Comparison

Lists RF performance and KPIs summed or averaged for the manufacturers of the selected

devices.




• Type: Table





Weighted Block Rate, CS Weighted Drop Rate, Device List, Downlink Volume (kbit),

Drops, Drop Rate (%), ECI0 Average, End Reason IRAT, IFHO, Max Data Throughput DL

(kbit/s), Max Data Throughput UL (kbit/s), Seconds of Use, Normal Release Count,

Normal Release Rate, PS Blocks, PS Block Rate (%), PS Drops, PS Drop Rate (%), PS

Weighted Block Rate, PS Weighted Drop Rate, Retransmission Rate DL, Retransmission

Rate UL, RNC, RSCP Average, Signalling Blocks, Signalling Block Rate (%), Traffic Volume

(MOU), Unknown Blocks, Unknown Block Rate (%), Unknown Drops, Unknown Drop Rate

(%), Unknown Weighted Block Rate, Unknown Weighted Drop Rate, Uplink Volume

(kbit), User Data Volume DL (kbit), User Data Volume UL (kbit), Ue Tx Power, Weighted

Block Rate, Weighted Drop Rate

Device List Comparison By Cell

Lists RF performance and KPIs summed or averaged for each cell for the manufacturers of

the selected devices.




• Type: Table



Page 65




Drop Rate (%), CS Weighted Block Rate, CS Weighted Drop Rate, Device List, Downlink










Device List Comparison trend over time


the manufacturers of the selected devices.




• Type: Table





Weighted Block Rate, CS Weighted Drop Rate, Device List, Downlink Volume (kbit),

Drops, Drop Rate (%), ECI0 Average, End Reason IRAT, IFHO, Max Data Throughput DL




Rate UL, RNC, RSCP Average, Signalling Blocks, Signalling Block Rate (%), Traffic Volume

(MOU), Unknown Blocks, Unknown Block Rate (%), Unknown Drops, Unknown Drop Rate

(%), Unknown Weighted Block Rate, Unknown Weighted Drop Rate, Uplink Volume

(kbit), User Data Volume DL (kbit), User Data Volume UL (kbit), Ue Tx Power, Weighted

Block Rate, Weighted Drop Rate

Device Performance Summary Per Individual

Shows the RF performance and KPIs for every single device of the type or types specified in

the filter.


Page 66


Although only the Device filter is required, using only this filter can return a very large

amount of data. Arieso recommends that you set several optional filters to limit the number

of devices shown to only those you are interested in.

• In folder: Device and Subscriber\Device

• Data Source: Call table

• Type: Table

• Filters (one required): Device, Subscriber

• Filters (optional): ARFCN, Cell, Completion Code (Combined), Completion Code (RANAP),

Completion Code (RRC), Completion Code (Vendor Specific), Country, DayHour Settings,

Establishment, Geographic Area, ID, IMEI, Mobility, Network View (Combined), Network

View (RANAP), Network View (RRC), Network View (Vendor Specific), RNC, Roamer,


Time Period, UE Capabilities, UE Downlink Category, UE Power Class, UE Release

Indicator, UE Uplink Category, VIP

• Metrics: Avg Downlink Throughput (kbit/s), Avg Uplink Throughput (kbit/s), Avg User

Downlink Throughput (kbit/s), Avg User Uplink Throughput (kbit/s), Blocks, Block Rate

(%), Calls, CS Blocks, CS Block Rate (%), CS Drops, CS Drop Rate (%), CS Weighted Block

Rate, CS Weighted Drop Rate, Downlink Volume (kbit), Drops, Drop Rate (%), ECI0

Average, ECI0 Median, End Reason IRAT, IFHO, Max Downlink Throughput (kbit/s), Max

Uplink Throughput (kbit/s), Normal Release, Normal Release Rate, PS Blocks, PS Block

Rate (%), PS Drops, PS Drop Rate (%), PS Weighted Block Rate, PS Weighted Drop Rate,

RSCP Average, RSCP Median, Seconds of Use, Subscriber, Unknown Blocks, Unknown

Block Rate (%), Unknown Drops, Unknown Drop Rate (%), Unknown Weighted Block

Rate, Unknown Weighted Drop Rate, Uplink Volume (kbit), User Downlink Volume (kbit),

User Uplink Volume (kbit), Ue Tx Power, Weighted Block Rate, Weighted Drop Rate

Devices by Cell & DL HS Category

For each cell, shows the number of calls started in that cell by devices of each HS category.

Page 67


Devices by Cell & DL HS Category. Some cell details have been hidden.






Completion Code (RRC), Completion Code (Vendor Specific), Country, Day Hour Settings,

Device, Device Software Version (SV), Establishment, Geographic Area, ID, IMEI,

Mobility, Network View (Combined), Network View (RANAP), Network View (RRC),

Network View (Vendor Specific), RNC, Roamer, Scrambling Code, Service, Service Group,

Subscriber, Subscriber Home Network, TAC, Time Period, UE Capabilities, UE Downlink

Category, UE Power Class, UE Release Indicator, UE Uplink Category, VIP

• Metrics: ARFCN, Category, Cell ID, Label, PSC, Site

Devices by Cell & UL HS Category

For each cell, shows the number of calls started in that cell by devices of each HS category.











Category, UE Power Class, UE Release Indicator, UE Uplink Category, VIP

• Metrics: ARFCN, Category, Cell ID, Label, PSC, Site

Page 68


Drop Locations

Displays the point location of all completion codes defined by ariesoGEO as drops. When

this is shown as a map analysis, the drop locations are color coded according to whether

they are circuit-switched, packet-switched or signalling drops.

This analysis shows UMTS drops only. To see blocks on all technologies, use the Drop

Locations analysis in the Common Analyses folders.









VIP






Drops Against Time

Shows the total number of drops in the selected area, for each fifteen minute period.






Time Period

• Metrics: Period Start Time, CS Drops, PS Drops, Signalling Drops, Total Drops, Unknown

Drops

Ec/I0 Histogram (Best)

This displays the number of best server cells or groups of cells that have the specified Ec/Io

range.





Page 69



Time Period

• Metrics: Entry, Count

Failure Reasons

This analysis shows the number of calls that terminated with each combined completion

code, and the number of failures for each domain (circuit switched, packet switched or

during signalling) within each completion code.







Group, Time Period

• Metrics: Completion Code (Combined), CS Count, Network View (Combined), PS Count,

Signalling Count, Total Count, Unknown Count

IFHO Locations

Displays the point location of all completion codes defined by ariesoGEO as inter-frequency

handovers within the applied filter.









VIP






Individual Call Segments

Displays detailed information such as completion codes and data volumes for each individual

call segment.

Note: This analysis requires the Subscriber license.

Page 70


This analysis can retrieve a very large amount of data, so ensure you set your filters very

restrictively to retrieve the minimum possible information.



• Type: Table

• Filters (required): ARFCN, Call ID, Cell, Completion Code (Combined), Completion Code

(RANAP), Completion Code (RRC), Completion Code (vendor specific), Country, Device,

Establishment Reason, IMEI, Network View (Combined), Network View (RANAP),

Network View (RRC), Network View (vendor specific), RNC, Roamer, Scrambling Code,

Service, Service Group, Subscriber, Subscriber Home Network, TAC, VIP

• Filters (optional): DayHour Settings, Geographic Area, UE Capabilities, UE Downlink


• Metrics: Active Set, Call ID, Cell, Classification, Completion Code (RANAP), Completion

Code (RRC), Completion Code (vendor specific), Confidence, Downlink Volume (kbits),

Downlink Volume [User] (kbits), Duration (secs), Geolocated? Geolocation Type, IMSI,

IMEI, Propagation Delay, Reason, Segment ID, Service, Start Time, Start Reason, SV,

TCode, Uplink Volume (kbits), Uplink Volume [User] (kbits)

Indoor Outdoor Traffic

Displays a raster map showing the number, data volume, and percentage minutes of use for

indoor and outdoor traffic.

Note: This analysis requires the IndoorOutdoor license.









Note: If using the Cell filter, all the selected cells must use the same ARFCN




• Metrics: All Traffic Count, All Traffic Volume (MOU), Indoor Traffic Count, Indoor Traffic

Volume (MOU), Outdoor Traffic Count, Outdoor Traffic Count Percentage, Outdoor

Traffic Volume (MOU), Outdoor Traffic MOU Percentage

Page 71


IRAT Locations

Displays a point map representing the location of every IRAT handover (for example, UMTS

to GSM) within the applied filter.



• Type: Single layer map






VIP






Loading Errors

Shows the loading errors that occurred for each RNC in each fifteen-minute time period.

• In folder: Administrative\Data Loading

• Data source: LoadedFilesets

• Type: Table


• Filters (optional): GEO Area, Time Period

• Metrics: Message, RNC, TCode

Loading Summary

Shows details of the data that was loaded for each RNC for each fifteen-minute time period.



• Type: Table



• Metrics: #Cells, #Cells Missing, #Cells Queried, #SC Missing, Data Availability (%), Calls

Loaded, End, Errors, Loaded Mbytes, Message, Parsed Files, Parsed Mbytes, Segments

Loaded, RNC, Stage, Start

Page 72


Loading Summary Daily

Shows, for each RNC, how many fifteen-minute periods were loaded into the database on

each day. If all periods were loaded, the number shown will be 96.

Loading Summary Daily, showing some minor loading issues



• Type: Table



• Metrics: Period, Count

Loading Summary GLR Rows

Shows, for each RNC, how many call segments were loaded from .glr files into the

database for each fifteen-minute period. For more information on .glr files see Loading

data on page 11.







Loading Summary GLR Rows Daily

Shows, for each RNC, how many call segments were loaded from .glr files into the

database on each day. For more information on .glr files see Loading data on page 11.



• Type: Table




Page 73


Loading Summary GLR Size

Shows, for each RNC, how many MB of data were loaded from .glr files into the database

for each fifteen-minute period. For more information on .glr files see Loading data on

page 11.







Loading Summary Parsed Size

Shows, for each RNC, how many MB of RNC data were parsed during each fifteen-minute

period.







Loading Summary Parsed Size Daily

Shows the total number of MB of RNC data parsed on each day.



• Type: Table




Loading Summary Period

Shows, for each period, the total number of call segments and calls loaded into the

database.



• Type: Table




Page 74


Loading Summary Pivot

Shows, for each RNC, how many files were parsed during each fifteen-minute period.







Locations

Displays a point map representing the location of every call segment (for example, UMTS to

GSM) within the applied filter.



• Type: Single layer map






VIP




Completion Code (RRC), Completion Code (Vendor Specific), Network View (Combined),


5.1.4 UTMS analyses M-R

Missing Neighbors

Shows cells that have entered the reporting range within the selected cell or cells (that is, an

E1A event occurred) but that have not been added to the active set (there was no

corresponding E1B event).

Note: This analysis requires the MissingNeighbour license.

The analysis displays the details of both cells, as well as the number of times the missing

neighbor has been observed, and the distance between the cells (in km).

• In folder: Optimization

• Data source: The information for this analysis is stored in the Mongo flat file database

• Type: Table

• Filters (one required): Cell, RNC

Page 75


• Filters (optional): ARFCN, Day Hour Settings, Geographic Area, Time Period

• Metrics: Call Count, Distance, Missing ARFCN, Missing Label, Missing Latitude, Missing

Longitude, Missing Name, Missing RNC, Missing PSC, Missing Site, Source ARFCN, Source

Label, Source Latitude, Source Longitude, Source Name, Source RNC, Source PSC, Source

Site

Mobility

Displays a raster map showing the percentage of total calls, minutes of use, drops, and

blocks corresponding to different mobility classifications.

Note: This analysis requires the Mobility license.












• Metrics: Pedestrian Blocks Percentage, Pedestrian Count Percentage, Pedestrian Drops

Percentage, Pedestrian MOU Percentage, Stationary Blocks Percentage, Stationary

Count Percentage, Stationary Drops Percentage, Stationary MOU Percentage, Unknown

Blocks Percentage, Unknown Count Percentage, Unknown Drops Percentage, Unknown

MOU Percentage, Vehicular Blocks Percentage, Vehicular Count Percentage, Vehicular

Drops Percentage, Vehicular MOU Percentage

Neighbor and Code Relationships

This analysis displays, for each cell selected, all the cells in its neighbor list and in the lists of

its neighbors, down to tier 4. Details such as distance, scrambling code and relative bearing

are shown for each neighbor.

Note: This analysis requires the ScramblingCodeTuning license.

• In folder: Optimization\Scrambling Code

• Data source: Neighbor table

• Type: Table

• Filters (required): Cell

• Filters (optional): ARFCN, Geographic Area, RNC, Scrambling Code

• Metrics: Distance, Priority, Relative Bearing, Source ARFCN, Source Label, Source

Latitude, Source Longitude, Source Name, Source PSC, Source RNC, Source Site, Target

Page 76


ARFCN, Target Label, Target Latitude, Target Longitude, Target Name, Target PSC, Target

RNC, Target Site, Target Tier

On Air UMTS to GSM Neighbors List

This analysis lists UMTS cells that have a GSM neighbor, and shows details of both cells.



• Type: Table



• Metrics: Priority , Source ARFCN, Source Label, Source Name, Source RNC, Source SC,

Source Site, Target ARFCN, Target Label, Target Name, Target RNC, Target SC, Target

Site, Type

On Air UMTS to UMTS Neighbors List

This analysis lists UMTS cells that have a UMTS neighbor, and shows details of both cells.



• Type: Table



• Metrics: Priority, Source ARFCN, Source Label, Source Name, Source RNC, Source SC,

Source Site, Target ARFCN, Target Label, Target Name, Target RNC, Target SC, Target

Site, Type

Performance Against Time

For each fifteen minute period, lists RF performance and KPIs for every single device

specified within the filter.


• In folder: Device and Subscriber



• Filters (one required): Device, Subscriber, VIP


Completion Code (RANAP), Completion Code (RRC), Completion Code (Vendor Specific)

Country, Day Hour Settings, Device Software Version (SV), Establishment, Geographic

Area, ID, IMEI, Mobility, Network View (Combined), Network View (RANAP), Network


Service Group, Subscriber Home Network, TAC, Time Period, UE Capabilities, UE


Page 77


• Metrics: Avg Downlink Throughput (kbit/s), Avg Uplink Throughput (kbit/s), Avg User

Downlink Throughput (kbit/s), Avg User Uplink Throughput (kbit/s), Blocks, Block Rate

(%), Calls, CS Blocks, CS Block Rate (%), CS Drops, CS Drop Rate (%), CS Weighted Block

Rate, CS Weighted Drop Rate, Downlink Volume (kbit), Drops, Drop Rate (%), ECI0

Average, ECI0 Median, End Reason IRAT, IFHO, Max Downlink Throughput (kbit/s), Max

Uplink Throughput (kbit/s), Normal Release, Normal Release Rate, PS Blocks, PS Block

Rate (%), PS Drops, PS Drop Rate (%), PS Weighted Block Rate, PS Weighted Drop Rate,

RSCP Average, RSCP Median, Seconds of Use, Subscriber, Unknown Blocks, Unknown


Rate, Unknown Weighted Drop Rate, Uplink Volume (kbit), User Downlink Volume (kbit),

User Uplink Volume (kbit), Ue Tx Power, Weighted Block Rate, Weighted Drop Rate

Performance KPIs

Shows information such as number of call segments, traffic density, block rates and drop

rates for each bin on a raster map.

• In folder: Performance

• Data source: BinSummary




Time Period

• Metrics: Average Active Set Links, Blocks, Block Rate (%), Count, Drops, Drop Rate (%),

Traffic Density (mErl/km2), Traffic Volume (MOU), Weighted Blocks, Weighted Drops

Performance KPIs per Device DL HS Category

Lists RF performance and KPIs summed or averaged for each UL HS category.

• In folder: Device and Subscriber\Device\Device Capability





Establishment, IMEI, Network View (Combined), Network View (RANAP), Network View

(RRC), Network View (Vendor Specific), RNC, Roamer, Scrambling Code, Service, Service

Group, Subscriber, Subscriber Home Network, TAC, VIP

• Filters (optional): Day Hour Settings, Device Software Version (SV), Geographic Area, ID,

Mobility, Time Period, UE Capabilities, UE Downlink Category, UE Power Class, UE Uplink

Category, UE Release Indicator




(%), ECI0 Average, End Reason IRAT Handovers, Intra-frequency Handovers, Max Data

Page 78


Throughput DL (kbit/s), Max Data Throughput UL (kbit/s), Minutes of Use, Normal

Release Count, Normal Release Rate, PS Blocks, PS Block Rate (%), PS Drops, PS Drop

Rate (%), PS Weighted Block Rate, PS Weighted Drop Rate, Retransmission Rate DL,

Retransmission Rate UL, RSCP Average, Unknown Blocks, Unknown Block Rate (%),

Unknown Drops, Unknown Drop Rate (%), Unknown Weighted Block Rate, Unknown

Weighted Drop Rate, Uplink Volume (kbit), User Data Volume DL (kbit), User Data

Volume UL (kbit), Ue Tx Power, Weighted Block Rate, Weighted Drop Rate

Performance KPIs per Device UL HS Category

Lists RF performance and KPIs summed or averaged for each UL HS category.















(%), ECI0 Average, End Reason IRAT Handovers, Intra-frequency Handovers, Max Data

Throughput DL (kbit/s), Max Data Throughput UL (kbit/s), Minutes of Use, Normal

Release Count, Normal Release Rate, PS Blocks, PS Block Rate (%), PS Drops, PS Drop


Retransmission Rate UL, RSCP Average, Unknown Blocks, Unknown Block Rate (%),




Performance KPIs per Device DL HS Category By Cell

Lists RF performance and KPIs summed or averaged for each combination of DL HS category

and cell.






Page 79










Drop Rate (%), CS Weighted Block Rate, CS Weighted Drop Rate, Downlink Volume (kbit),

Drops, Drop Rate (%), ECI0 Average, End Reason IRAT Handovers, Intra-frequency

Handovers, Label, Max Data Throughput DL (kbit/s), Max Data Throughput UL (kbit/s),

Minutes of Use, Normal Release Count, Normal Release Rate, PS Blocks, PS Block Rate

(%), PSC, PS Drops, PS Drop Rate (%), PS Weighted Block Rate, PS Weighted Drop Rate,

Retransmission Rate DL, Retransmission Rate UL, RNC, RSCP Average, Signalling Blocks,

Signalling Block Rate (%), Site, Unknown Blocks, Unknown Block Rate (%), Unknown




Performance KPIs per Device UL HS Category By Cell

Lists RF performance and KPIs summed or averaged for each combination of DL HS category

and cell.















Drops, Drop Rate (%), ECI0 Average, End Reason IRAT Handovers, Intra-frequency

Handovers, Label, Max Data Throughput DL (kbit/s), Max Data Throughput UL (kbit/s),

Minutes of Use, Normal Release Count, Normal Release Rate, PS Blocks, PS Block Rate

(%), PSC, PS Drops, PS Drop Rate (%), PS Weighted Block Rate, PS Weighted Drop Rate,

Retransmission Rate DL, Retransmission Rate UL, RNC, RSCP Average, Signalling Blocks,

Page 80


Signalling Block Rate (%), Site, Unknown Blocks, Unknown Block Rate (%), Unknown




Pilot Pollution NdB

Displays a raster map showing, for each bin, the number of servers other than the strongest

three that have a median Ec/Io within a configurable number of dB of the best server's Ec/Io.

Polluter > Best Server - N

The Pilot Pollution Threshold (dB) parameter enables you to ignore the cells with very low

signal to noise ratios. The analysis does not consider cells whose median EC/I0 is lower than

the best server's dB minus the parameter number of dB. The analysis also does not consider

the cells whose median EC/I0 is ranked second and third in the cell, as they are assumed to

be part of the active set.

Note: The Pilot Pollution NdB analysis does not have exactly the same definition of a polluter

as the Pilot Pollution Top Ten Polluters analysis.

• In folder: RF

• Data source: ServerSummary table

• Type: Map

• Filters (required): ARFCN

• Filters (optional): Cell, DayHour Settings, Geographic Area, RNC, Time Period,

Scrambling Code

• Parameters: Pilot Pollution Threshold (dB)

• Metrics: Cell, PollutedBins, Rank, RelativePollutedBinsPercent

Pilot Pollution Top Polluters

Shows the top ten cells responsible for pilot pollution within the filter area.

A cell is considered a polluter for any bin in which it is reported but it is not the best cell.

This analysis shows the ten cells that are considered polluters for the most bins within the

selected area.

Note: The Pilot Pollution Top Ten Polluters analysis does not have exactly the same

definition of a polluter as the Pilot Pollution NdB analysis.

• In folder: RF




• Filters (optional): ARFCN, Cell, DayHour Settings, Geographic Area, RNC, Time Period,

Scrambling Code

Page 81


• Metrics: Cell, PollutedBins, Rank, RelativePollutedBinsPercent

Processed RSCP

This analysis adjusts the reported RSCP to account for the lower reporting rate of low values,

and calculates the probable RSCP for bins where only the Ec/Io value is known.

• In folder: RF





Scrambling Code

• Metrics: Processed RSCP

RANAP Failure Reasons

This analysis shows a summary of the number of calls that terminated with each RANAP

completion code. Completion codes are only shown if at least one call terminated with that

code.









• Filters (optional): Day Hour Settings, Geographic Area, Time Period, UE Capabilities, UE


• Metrics: Completion Code (RANAP), Count, Network View (RANAP)

RF Cdf

Shows the cumulative distribution function (CDF) for the chosen KPI. The cumulative

distribution function is the probability that the KPI will have a value better than that shown

in the key.

Page 82


UMTS RF Cdf showing the cumulative distribution of Ec/Io against the key on the X axis

By default, this analysis shows the CDF for Ec/Io. To change this, edit the Name of the CDF

to create parameter. Possible values are:

• DownlinkThroughput, DownlinkVolume, Duration, Rscp, UplinkThroughput, Uplink

Volume, UeTxPower, UserDownlinkThroughput, UserDownlinkVolume,

UserUplinkThroughput, UserUplinkVolume

• In folder: RF\Statistics






Device, Device Software Version (SV), Establishment Reason, Geographic Area, ID, IMEI,

Network View (Combined), Network View (RANAP), Network View (RRC), Network View

(Vendor Specific), Roamer, RNC, Scrambling Code, Service, Service Group, Subscriber,

Subscriber Home Network, TAC, Time Period, UE Capabilities, UE Downlink Category, UE

Power Class, UE Release Indicator, UE Uplink Category, VIP

• Parameters: Name of the CDF to create

• Metrics: Key, Value

RF Distance

Shows the RF KPIs at each distance band from each of the cells in the filter.

The KPI value shown is that of the specified percentile, where the percentile indicates the

percentage of values that are better than the KPI shown. For example, if you chose to show

KPIs at the 95th percentile, an Ec/Io of -13dB for a distance band would indicate that 95% of

Ec/Io values for that distance were -13dB or better.

The default percentile value is 50.

Page 83













• Parameters: Percentile value to display (if appropriate)

• Metrics: Blocks, Calls, Cell, Distance, Drops, Ec/Io, Mou, Rscp, UeTxPower

RF Footprint KPIs

Displays the average EC/I0 and RSCP for the selected cells across all call segments included in

the filter.

• In folder: RF\Footprints




• Filters (optional): ARFCN, DayHour Settings, Geographic Area, RNC, Time Period,

Scrambling Code

• Metrics: Footprint EC/I0 (Average), Footprint RSCP (Average)

RF Histograms

Shows the distribution of values for the selected KPI.

UMTS RF Histograms showing number of call segments against measured Ec/Io

By default, this analysis shows the distribution for Ec/Io. To change this, edit the Name of

the histogram to create parameter. Possible values are:

Page 84
















• Parameters: Name of the histogram to create


RF KPIs

Displays the average Ec/Io and RSCP for the selected filters.

• In folder: RF





Scrambling Code

• Metrics: EcI0 (Average), RSCP (Average)

RF KPIs at Percentiles

Shows the value of the Ec/Io and RSCP at the selected percentile for each bin.

Page 85


RF KPIs at Percentiles showing the Ec/Io value at the 25th percentile in each bin

The KPI value shown is that of the specified percentile, where the percentile indicates the

proportion of values that are better than the KPI shown. For example, if you chose to show

KPIs at the 95th percentile, an Ec/Io of -13dB for a distance band would indicate that 95% of

Ec/Io values for that distance were -13dB or better.













• Parameters: Percentile value to display (if appropriate)

• Metrics: Value

RF KPIs Percentiles per Threshold

Shows the proportion of values in each bin that are better than the set Ec/Io or RSCP

threshold.

The default threshold values are:

• Ec/Io -14

Page 86


• RSCP -80

• UE Tx Power -5












• Parameters: Ec/Io threshold to show values over, RSCP threshold to show values over,

UE Tx Power threshold to show values over

• Metrics: Value

RF KPIs Uplink

Displays the average UE transmit power for the selected filters.

• In folder: RF

• Data source: SignalSummary table




Scrambling Code

• Metrics: UE Transmit Power (Average)

RF Overview

Shows the value of the selected KPI at the selected percentile across all the call segments

included in the filter.

The percentile indicates the percentage of values that are better than the KPI shown. For

example, if you chose to show KPIs at the 95th percentile, an Ec/Io of -13dB for a distance

band would indicate that 95% of Ec/Io values for that distance were -13dB or better.


By default, this analysis shows the overview for Ec/Io. To change this, edit the Name of the

overview to create parameter. Possible values are:

Page 87
















• Parameters: Name of the histogram to create, Percentile value to display (if

appropriate)


RF Processed Footprint RSCP

Displays the Processed RSCP for the selected cells. Processed RSCP is adjusted to account

for the lower reporting rate of low values, and includes the probable RSCP for bins where

only the Ec/Io value is known.

• In folder: RF\Footprints




• Filters (optional): ARFCN, DayHour Settings, Geographic Area, RNC, Time Period,

Scrambling Code

• Metrics: Processed RSCP

RF Trend

Shows the value of the selected KPI at the selected percentile for each fifteen-minute

period, across all the call segments included in the filter.

The percentile indicates the percentage of values that are worse than the KPI shown. For

example, if you chose to show KPIs at the 95th percentile, an Ec/Io of -13dB for a period

would indicate that 95% of Ec/Io values for that distance were -13dB or better.


Page 88


By default, this analysis shows the trend for Ec/Io. To change this, edit the Name of the

trend to create parameter. Possible values are:















• Parameters: Name of the histogram to create, Percentile value to display (if

appropriate)

• Metrics: Period Start Time, Value

RNC Count Against Time

Shows the total number of calls in the selected area for each 15 minute period, broken down

by RNC.

When displayed as a chart, this shows the number of calls against time and the number of

RNCs against time. To see the number of calls per RNC against time, use the RNC Count

Against Time (Pivot) analysis.







• Metrics: Calls, Period Start Time, RNC

RNC Count Against Time (Pivot)

Shows the total number of calls in the selected area for each day period, broken down by

RNC.

Page 89


When displayed as a chart, this shows the number of calls on each RNC against the time

period.







• Metrics: Calls, Period Start Time, RNC

RNC Summary

Shows, for each RNC, the most recent fifteen-minute period for which ariesoGEO detected

data files, and the most recent fifteen-minute period for which files were loaded into the

database.



• Type: Table



• Metrics: RNC, LastSeen, LastLoaded

RRC Failure Reasons

This analysis shows a summary of the number of calls that terminated with each RRC


code.











• Metrics: Completion Code (RRC), Count, Network View (RRC)

Page 90


5.1.5 UTMS analyses S-Z

Scrambling Code Choices Ranked By Score

Displays a list of the possible scrambling codes that could be used for the selected cell or

cells, ranked according to the level of conflict with existing scrambling codes (Score).


A Score of 1-10 indicates that any conflict is with fourth or fifth tier neighbors, whereas a

Score of 10 000 or more indicates a conflict with an immediate neighbor.

For each scrambling code, the nearest cell that reuses that code (in terms of distance rather

than neighbor tier) is shown.



• Type: Table



• Metrics: Nearest ARFCN, Nearest Cell Distance, Nearest Cell Relative Bearing, Nearest

Label, Nearest Latitude, Nearest Longitude, Nearest Name, Nearest PSC, Nearest RNC,

Nearest Site, Priority, Score, Selected SC, Source ARFCN, Source Label, Source Latitude,

Source Longitude, Source Name, Source PSC, Source RNC, Source Site

Scrambling Code Conflicts

Lists scrambling code conflicts between cells, ranked according to the level of conflict with

existing scrambling codes (Cumulative Conflict Score).


A Cumulative Conflict Score of 10 indicates a conflict with a fourth tier neighbor, whereas a

Cumulative Conflict Score of 10 000 or more indicates a conflict with an immediate

neighbor. Conflicts with neighbors more distant than the fourth tier are not shown.

Page 91


Analysis showing Conflict Scores for different tiers. Some cell details have been hidden.



• Type: Table

• Filters (one required): Cell, RNC

• Filters (optional): ARFCN, Geographic Area, Scrambling Code

• Metrics: Nearest ARFCN, Nearest Cell Distance, Nearest Cell Relative Bearing, Nearest

Label, Nearest Latitude, Nearest Longitude, Nearest Name, Nearest PSC, Nearest RNC,

Nearest Site, Priority, Score, Selected SC, Source ARFCN, Source Label, Source Latitude,

Source Longitude, Source Name, Source PSC, Source RNC, Source Site

Scrambling Code Suggestions (Advanced)

Displays the best scrambling code to use for the selected cell or cells, based on conflict with

existing scrambling codes.


If multiple cells are selected, the analysis ensures that its selections do not conflict.

Non-conflicting scrambling code suggestions. Some cell details have been hidden.


Page 92



• Type: Table

• Filters (required): Cell (maximum 9)


• Metrics: ARFCN, Cell ID, Comment, Label, Latitude, Longitude, PSC, Recommended SC,

RNC, Site

Note: In this analysis, the Scrambling Code filter restricts the list of recommended

scrambling codes, rather than the cells considered.

Scrambling Code Suggestions (Basic)

Displays the best scrambling code to use for the selected cell or cells, based on conflict with

existing scrambling codes.


If multiple cells are selected, conflicts between the suggestions are not considered.

Conflicting scrambling code suggestions. Some cell details have been hidden.



• Type: Table



• Metrics: ARFCN, Cell ID, Comment, Label, Latitude, Longitude, PSC, Recommended SC,

RNC, Site

Note: In this analysis, the Scrambling Code filter restricts the list of recommended

scrambling codes, rather than the cells considered.

Strongest Server Footprint RF KPIs

Displays a raster map with the best Ec/Io and RSCP recorded for the selected cell, in all the

bins in which it is the strongest server. The strongest server is calculated based on how

frequently each cell is seen in the bin, and what RSCP values are reported for it.


Page 93






Time Period

• Metrics: Ec/Io Cell Footprint (Strongest), RSCP Cell Footprint (Strongest)

Strongest Server RF KPIs

Displays a raster map with the mean Ec/Io and RSCP of the strongest server in each bin. The

strongest server is calculated based on how frequently each cell is seen in the bin, and what

RSCP values are reported for it.






Time Period

• Metrics: RSCP (Strongest) (Average), Ec/Io (Strongest) (Average)

Subscriber Comparison

Lists RF performance and KPIs summed or averaged for each individual subscriber within the

filter.

Note: This analysis requires the SubscriberManagement license.

• In folder: Device and Subscriber\Subscriber\Subscriber Comparison

• Data Source: Call Table

• Type: Table

• Filters (one required): Subscriber, VIP






Subscriber Home Network, TAC, UE Capabilities, UE Downlink Category, UE Power Class,

UE Release Indicator, UE Uplink Category




(%), ECI0 Average, ECI0 Median, End Reason IRAT, IFHO, Max Data Throughput DL



Page 94



Rate UL, RNC, RSCP Average, RSCP Median, Signalling Blocks, Signalling Block Rate (%),

Signalling Drops, Signalling Drop Rate, Signalling Weighted Block Rate, Signalling

Weighted Drop Rate, Subscriber, Traffic Volume (MOU), Unknown Blocks, Unknown


Rate, Unknown Weighted Drop Rate, Uplink Volume (kbit), User Data Volume DL (kbit),

User Data Volume UL (kbit), Ue Tx Power, Weighted Block Rate, Weighted Drop Rate

Subscriber Comparison By Cell

Lists RF performance and KPIs summed or averaged for each cell for the selected individual

subscribers.




• Type: Table










(kbit/s), Blocks, Block Rate (%), Calls, Cell, CS Blocks, CS Block Rate (%), CS Drops, CS

Drop Rate (%), CS Weighted Block Rate, CS Weighted Drop Rate, Device, Downlink










Subscriber Comparison trend over time


each individual subscriber within the filter.


Page 95




• Type: Table














Normal Release Rate, Period Start Time, PS Blocks, PS Block Rate (%), PS Drops, PS Drop


Retransmission Rate UL, RNC, RSCP Average, RSCP Median, Signalling Blocks, Signalling

Block Rate (%), Signalling Drops, Signalling Drop Rate, Signalling Weighted Block Rate,

Signalling Weighted Drop Rate, Subscriber, Traffic Volume (MOU), Unknown Blocks,

Unknown Block Rate (%), Unknown Drops, Unknown Drop Rate (%), Unknown Weighted

Block Rate, Unknown Weighted Drop Rate, Uplink Volume (kbit), User Data Volume DL

(kbit), User Data Volume UL (kbit), Ue Tx Power, Weighted Block Rate, Weighted Drop

Rate

Subscriber List Comparison

Lists RF performance and KPIs summed or averaged for the subscriber lists containing the

selected subscribers.




• Type: Table









Page 96











Weighted Drop Rate, Subscriber List, Traffic Volume (MOU), Unknown Blocks, Unknown


Rate, Unknown Weighted Drop Rate, Uplink Volume (kbit), User Data Volume DL (kbit),

User Data Volume UL (kbit), Ue Tx Power, Weighted Block Rate, Weighted Drop Rate

Subscriber List Comparison By Cell

Lists RF performance and KPIs summed or averaged for each cell for the subscriber lists

containing the selected subscribers.




• Type: Table












Drops, Drop Rate (%), ECI0 Average, End Reason IRAT, IFHO, Label, Max Data

Throughput DL (kbit/s), Max Data Throughput UL (kbit/s), Seconds of Use, Normal




Site, Subscriber List, Traffic Volume (MOU), Unknown Blocks, Unknown Block Rate (%),




Page 97


Subscriber List Comparison trend over time


the subscriber lists containing the selected subscribers.




• Type: Table














Normal Release Rate, Period Start Time, PS Blocks, PS Block Rate (%), PS Drops, PS Drop


Retransmission Rate UL, RNC, RSCP Average, RSCP Median, Signalling Blocks, Signalling

Block Rate (%), Signalling Drops, Signalling Drop Rate, Signalling Weighted Block Rate,

Signalling Weighted Drop Rate, Subscriber, Traffic Volume (MOU), Unknown Blocks,

Unknown Block Rate (%), Unknown Drops, Unknown Drop Rate (%), Unknown Weighted

Block Rate, Unknown Weighted Drop Rate, Uplink Volume (kbit), User Data Volume DL

(kbit), User Data Volume UL (kbit), Ue Tx Power, Weighted Block Rate, Weighted Drop

Rate

Subscriber Performance Summary Per Individual

Lists RF performance and KPIs summed or averaged for each individual subscriber within the

filter.


• In folder: Device and Subscriber\Subscriber


• Type: Table




Page 98
















Weighted Drop Rate, Subscriber, Subscriber List, Traffic Volume (MOU), Unknown

Blocks, Unknown Block Rate (%), Unknown Drops, Unknown Drop Rate (%), Unknown

Weighted Block Rate, Unknown Weighted Drop Rate, Uplink Volume (kbit), User Data

Volume DL (kbit), User Data Volume UL (kbit), Ue Tx Power, Weighted Block Rate,

Weighted Drop Rate

System Performance

Displays performance information such as number of connections, block rate and drop rate,

summed across the entire system and selected time period.



• Type: Table




Period

• Metrics: Block Rate (%), CS Blocks, CS Block Rate (%), CS Drops, CS Drop Rate (%), Drop

Rate (%), Drops, Minutes, Normal Releases, PS Blocks, PS Block Rate (%), PS Drops, PS

Drop Rate (%), Signalling Blocks, Signalling Block Rate (%), Signalling Drops, Signalling

Drop Rate (%), Total Blocks, Unknown Blocks, Unknown Block Rate (%), Unknown Drops,


System Performance Against Time

Shows key system performance indicators such as the block and drop rate for each fifteen

minute period.



Page 99






• Metrics: Block Rate (%), Calls, CS Blocks, CS Block Rate (%), CS Drops, CS Drop Rate (%),

Minutes, Normal Releases, Period Start Time, PS Blocks, PS Block Rate (%), PS Drops, PS

Drop Rate (%), Signalling Blocks, Signalling Block Rate (%), Signalling Drops, Signalling

Drop Rate (%), Total Blocks, Unknown Blocks, Unknown Block Rate (%), Unknown Drops,


Top N Calling Subscribers

Displays the subscribers who made the most calls, and the number of calls they made.


For this analysis, the number of calls is calculated based on the number of segments that

terminate a call. That is:

Calls = Total Segments - Continuations

This analysis is available only on systems that have the Subscriber license.












• Parameters: Number of Values

• Metrics: Calls, Subscriber

Turn Cell Off

Displays a raster map showing the projected KPIs for an area if a selected cell is turned off.




would affect it. A more sophisticated model is provided by the RF Shaping feature.


Page 100






Time Period

• Parameters: Cell to turn off


Ec/Io Original, Footprint RSCP Original, RSCP Original, RSCP Tuned, Strongest Server

Original, Strongest Server Tuned

Vendor Specific Failure Reasons

This analysis shows a summary of the number of calls that terminated with each vendor


code.











• Metrics: Completion Code (Vendor Specific), Count, Network View (Vendor Specific)

VIP Block Locations

Displays the point location of all blocks that occurred on the selected VIP calls.


• In folder: VIP



• Filters (one required): Call ID, IMEI, Subscriber, VIP


Completion Code (RRC), Completion Code (Vendor Specific), Day Hour Settings, Device,

Device Software Version (SV), Establishment, Geographic Area, Network View

(Combined), Network View (RANAP), Network View (RRC), Network View (Vendor

Specific), RNC, Roamer, Scrambling Code, Service, Service Group, Subscriber Home

Network, TAC, UE Capabilities, UE Downlink Category, UE Power Class, UE Release


Page 101


• Metrics: Completion Code (Combined), Completion Code (RANAP), Completion Code

(RRC), Completion Code (Vendor Specific), NetworkView (Combined), ID, IMSI, IMEI,

Operator, Segment, Service, SV, TCode, X (Longitude), Y (Latitude)

VIP Drop Locations

Displays the point location of all drops that occurred on the selected VIP calls.


• In folder: VIP












(RRC), Completion Code (Vendor Specific), NetworkView (Combined), ID, IMSI, IMEI,


VIP Drop Locations Data

Displays the point location of all drops that occurred on any of the selected VIP calls that

were packet switched.


• In folder: VIP












(RRC), Completion Code (Vendor Specific), ID, IMSI, IMEI, NetworkView (Combined),


Page 102


VIP Drop Locations Voice

Displays the point location of all drops that occurred on any of the selected VIP calls that

were circuit switched.


• In folder: VIP












(RRC), Completion Code (Vendor Specific), ID, IMSI, IMEI, NetworkView (Combined),


VIP Locations

Displays the point location of all the selected VIP call segments.


Note: There is no confidence filter applied to this analysis. It shows all the filtered call

segments, regardless of how accurate their location might be.

• In folder: VIP












(RRC), Completion Code (Vendor Specific), Confidence, ID, IMSI, IMEI, NetworkView

(Combined), Operator, Segment, Service, SV, TCode, X (Longitude), Y (Latitude)

Page 103


VIP Summary

Displays a summary of the volume and duration of all the selected VIP calls.


• In folder: VIP











• Metrics: Call ID, Downlink Volume (Kbits), Downlink Volume [user] (Kbits), Duration,

IMSI, IMEI, Start Time, SV, Uplink Volume (Kbits), Uplink Volume [user] (Kbits)

Weighted centroid of multiple locations

Displays the central point of all the selected segments, also called the mean position, either

as a single point on a point map or as a table.

The locations of all the selected segments are weighted by the confidence of their

geolocation.

• In folder: Centroid











• Metrics: Latitude, Longitude, Type

Worst N Cells (Blocks) / Worst N Cells (CS Blocks) / Worst N Cells (PS Blocks)

Displays the cells with the highest numbers of blocked calls. This is determined purely by

number of blocks, not by the block rate.


Page 104







Group, Time Period


• Metrics: ARFCN, Block Rate (%), Blocks, Cell ID, PSC, Label, RNC, Site

Worst N Cells (Drops) / Worst N Cells (CS Drops) / Worst N Cells (PS Drops)

Displays the cells with the highest numbers of dropped calls. This is determined purely by

number of drops, not by the drop rate.

Different versions of this analysis show the cells with the highest number of specifically

circuit-switched drops or packet-switched drops.







Group, Time Period


• Metrics: ARFCN, Cell ID, Drop Rate (%), Drops, PSC, Label, RNC, Site

Worst N Subscribers (Drops)

Displays the subscribers that have the highest numbers of dropped calls. This is determined

purely by number of drops, not by the drop rate.








Group, Time Period


• Metrics: Calls, CS Drops, CS Drop Rate, Drop Rate (%), Drops, Normal Releases, PS Drops,

PS Drop Rate, Signalling Drops, Signalling Drop Rate, Subscriber, Unknown Drops,

Unknown Drop Rate

Page 105


Version History

Ver.

No.

Ver. Date Revised/Actioned

By

Event/Description

0.1 28 Jan 13 S. Blake Initial draft

0.2 21 Apr 13 S. Blake UMTS information essentially complete

1.0 30 Apr 13 S. Blake Initial version complete

Page 106


Arieso Ltd

Astor House

Newbury Business Park

London Road

Newbury

Berkshire

RG14 2PZ

United Kingdom

Tel: +44 (0) 1635 232470

Fax: +44 (0) 1635 232471

Arieso Inc

3495 Piedmont Rd Bldg 11

Suite 550

Atlanta GA

30305

USA

Tel: +1 678 904 2424

Fax: +1 678 904 2429

Email: [email protected]

Web: www.arieso.com

Documents

Aeriso Geo Technical Guide