Actix Analyzer UMTS Analysis Guide-libre

7/18/2019 Actix Analyzer UMTS Analysis Guide-libre

http://slidepdf.com/reader/full/actix-analyzer-umts-analysis-guide-libre 1/48

www.actix.com

November 2005

UMTS

Analysis Guide



www.actix.com

The content of this manual is provided for information only, is subject to change without

notice, and should not be construed as a commitment by Actix. Actix assumes noresponsibility or liability for any errors or inaccuracies that appear in this documentation.

Copyright © Actix 2 005-2008. All rights reserved. All trademarks are hereby acknowledged.



www.actix.com

Contents

1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

2 OPERATIONAL TASKS AND PROCESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

2. 1 S

ITEINTEGRATION AND

INFRASTRUCTURE

TESTING

. . . . . . . . . .. . . . . . . . . .. . . . . . . . . .. . . . . . . . . .. . . . . . . . . .. . 7

2. 2 DETAILED CALL SEQUENCE ANALYSIS . . . . . . . . . .. . . . . . . . . .. . . . . . . . .. . . . . . . . . .. . . . . . . . . .. . . . . . . . . .. . . . . . . . . 8

2. 3 BENCHMARKI NG AND STATISTICAL ANALYSIS. . . . . . . . . .. . . . . . . . . .. . . . . . . . . .. . . . . . . . . .. . . . . . . . .. . . . . . . . . .. 9

2. 4 RADIO LINK PERFORMANCE TROUBLESHOOTING........................................................10

3 FEATURE OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3. 1 ACTIX ANALYZER ...........................................................................................12

3. 2 APPLICATION LAYERS ......................................................................................13

3.2.1 Neighbor List Analysis Module .............. ............... ............... ............... ....14

3.2.2 CPICH Pollution Analysis Module ..... ..... ..... ..... ..... ..... ..... ..... ..... .... .... ..... .. 17

3.2.3 Handoff State Analysis Module (for scanner) ................ ............... ............ 19

3.2.4 Emulated Active Set Module................ ............... ............... ................ ....22

3.2.5 CPICH before RRC Connection Request Module .... ..... ..... ..... ..... ..... ..... ..... .23

3.2.6 CPICH before call end or drop Module.....................................................24 3.2.7 CPICH during call Module........................... ................ ............... ............ 25

3.2.8 CPICH after call end or drop Module............... ............... ................ ......... 26

3.2.9 Call Setup Status Module............ ............... ............... ................ ............ 27

3.2.10 Call Sequence Analysis Module ............... ................ ................ ............. 28

3.2.11 Call Statistics Module (CS or PS)..........................................................29

3.2.12 Call Sustainability Module ............... ................ ................ ................ ....30

3.2.13 Call Timing Analysis Module ............... ................ ................ ............... ..31

3.2.14 File Summ ary Module............... ............... ................ ............... ............ 32

3.2.15 Coverage Summ ary Module .............. ............... ............... ................ ....33

3.2.16 Handoff Breakdown Analysis Module (Handset) ..... ..... ..... ..... ..... ..... ..... ... 34

3.2.17 SHO per event 1a-1b-1c Module .............. ............... ................ ............. 35

3.2.18 Overall BLER Module .............. ............... ............... ............... ............... 36

3.2.19 BLER Per call Module................... ............... ................ ................ ........ 36

3.2.20 BLER during SHO Module ................ ................ ................ ................ ....37

3. 3 FILTERS .....................................................................................................37

3. 4 STATEFORMS................................................................................................38

3.4.1 UMTS Data Event Navigator ................ ............... ................ ............... ....38

3.4.2 UMTS Data Session ............... ................ ............... ................ ............... 39

3.4.3 UMTS Throughput .............. ............... ................ ............... ............... ....40

3.4.4 UMTS Top 10 Scan Measurements ................ ................ ............... .......... 41

3.4.5 UMTS UE Active + Monitored Set .............. ............... .............. ............... .42

3.4.6 UMTS UE Call I nformation................. ................ ................ ............... ..... 43

3.4.7 UMTS UE Measurements Charts...... ............... ............... ................ ......... 44

3.4.8 UMTS UE Radio Parameters ................ ............... ............... ................ ....45

3.4.9 UMTS UE Transport Channel I nfo ............... ................ ................ ............ 46

3.4.10 UMTS Voice Event Navigator (CS Only) .... ..... ..... ..... ..... ..... ..... ..... .... .... .. 47



Actix Analyzer UMTS Analysis Guide Novem ber 20 05 Introduction 4

www.actix.com

1 I ntroduction

It is widely recognized that increasing productivity fuelled much of t he global economic

expansion of the 1990’s. Technological advances in softw are and h ardware usually enable

these productivity improvements, although there is often a lag between the availability ofthe new t echnology, and it s widespread acceptance and deploym ent by industry. This gap

is sometimes called the productivity lag factor.

Some examples of this include the introduction of automated bank teller technology in the

1980’s in t he US. When t he technology initially became available, it w as only sparingly

deployed, and the units were oft en placed inside bank buildings where the pr oductivity

enhancement s they offered w ere limited. Likewise, unattended gasoline pump technology

has been slow t o roll out in Europe, but as the technology has become w idely adapted,

huge efficiency gains have been realized.

The wireless industry is now at a similar point. It understands that the traditional labor-

intensive techniques for maxim izing performance and capacity in wireless infrastructure

are fundamentally limited by a lack of structured algorithms to determine improvements.

Actix Analyzer offers the possibility to look at drive test data and scanner data t o fully

optim ize a UMTS network. It allows the engineer t o understand t he causes and reasons for

drop calls and access failures.

Analyzer offers an unprecedented capability t o execute a det ailed exam ination of message

flows and aut omat ing stat istical analyses of perform ance. Analyzer significantly accelerates

the rollout, troubleshooting and optim ization of the UMTS network. Actix has embedded

intelligence in the software to allow the RF engineer to visualize specific events and

understand real problems occurring in the network.

Analyzer em bodies our ext ensive experience as the mark et leader in opt imization solutions

for CDMA, UMTS and GSM. All of the lessons learned and the techniques developed over a

10-y ear period have been incorporated into t hese powerful, v endor-independent solutions

for UMTS infrastructur e.

This document provides an overview of the k ey benefits, applications and features of

Analyzer. For additional inform ation, including whit e papers and other lit erature, please

refer to www.actix.com.



Actix Analyzer UMTS Analysis Guide Novem ber 20 05 Operati onal Tasks and Processes 6

www.actix.com

Figure 2: Scanner and Drive tests analysis, Site Integration and Optimization are performed as part of

critical processes in the Initial Rollout, Immature Buildout and Mature Growth phases

Analyzer allows the user to focus on the following t asks for site integration and testing,

coverage analysis, troubleshooting and optim ization:

• Site Integration and Infrastructure Testing

• Detailed Call Sequence Analysis

• Benchm arking and Stat istical Analysis

• Radio Link Performance Troubleshooting

• Event Detection and Dr ive Test Analysis

The following sections describe the high-level capabilities of Analyzer for each of these

applications. Because Analyzer is based on an open architecture platform—which includes

Benchmarking

R&D / Tr ials& Planning

I nitialRollout

I mma t ur eBuildout

MatureGrowth

Scanner a nd

Drive TestsAnalysis

EventDetections

ServiceCoverageAvailability

Site CalibrationI nitial Testing

Throughputand RatesCalculation

I nitial CoverageAnalysis

Processes

Phases

Tasks

Subscriber-PerceivedPerformance

Radio LinkPerformance

On-goingOptimization

NetworkGrowth

PowerMeasurements

Site I ntegrat ionand

Optimization




www.actix.com

user-definable query and open data import capabilities—it m ay be used for many ad-hoc

troubleshooting and perform ance analysis tasks beyond t hose covered in this document.

2.1 Site I ntegrat ion and Infrastructure Testing

Part of the process in rolling out a network is to be able to test and int egrate new sites.Analyzer provides the following features for site integration and infrastructure testing:

• The file sum mary report allows the engineer to h ave a quick look at th e overall

performance during the entire drive test.

• Embedded charts and graphs help to visualize key parameters like Ec/No or RSCP

in the active set.

• Detailed reports on call statistics on cell by cell basis

• User-definable queries allow creation of customized statist ical analysis

• Automated report generation containing statistical summaries of key performance

indicator

Figure 3: Charts and graphs for UMTS site integrat ion and infrastruct ure testing




www.actix.com

2.2 Detailed Call Sequence Analysis

Analyzer provides these analyses of call sequence and call setup procedures:

•

Detailed call sequence analysis on a message by message basis

• Automat ed report generation for visualization of call sequence messages

• Automated report generation – statistical summaries of call setup problems

Figure 4: Stat istical summar ies of call setup procedures and failure causes

Figure 5: Detailed call sequence analysis




www.actix.com

2.3 Benchm arking and Stat istical Analysis

Analyzer provides the following features for benchm arking and stat istical analysis:

• Automat ed report generation for quick v isualization of call statistics such as drop

calls, access failures, call sustainability, etc.

• Working wit h different sources of data to create homogeneous set of reports for

benchmarking

• User-defined queries allowing easy access to different statistics

Figure 6: Charts and graphs representing different call statistics



Actix Analyzer UMTS Analysis Guide Novem ber 20 05 Operat ional Tasks and Processes 10

www.actix.com

Figure 7: Various call statistics filtered by cells

2.4 Radio Link Performance Troubleshooting

Analyzer may be used to diagnose and determine rem edial action for key radio-link

configuration problems, including:

• Distant servers

• Too many servers

• Unnecessarily large neighbor lists

• Excessive soft handoff area

Figure 8: Identify problems for UMTS radio networks by visualizing

pilot signals as lines drawn to serving cells on a map

Radio Link Performance Metrics available from Analyzer will include the following

att ributes, depending on t he specific vendor and specific source (handset or scanner):



Actix Analyzer UMTS Analysis Guide Novem ber 20 05 Operat ional Tasks and Processes 11

www.actix.com

• Mobile Transm it Power, Mobile Receive Power, BLER

• CPICH Ec/No, Ec/I o and RSCP per scram bling code

• Chip Offset and Delay Spread per SC

• Ec/ I o, RSCP and Path loss for Nt h best SCs

• CPI CH Ec/ No and SC in Active and Monitor ed set

• Handoff State, Call ID

Figure 9: Charts and graphs for a handoff state analysis



Actix Analyzer UMTS Analysis Guide Novem ber 20 05 Feature Overview 12

www.actix.com

3 Feature Overview

3.1 Actix Analyzer

Depending on the licenses available to you, Analyzer is able to analyze cdma2000, GSM,GPRS and EDGE, as well as UMTS data. Analyzer provides a core set of capabilities to

analyze network performance data:

• Interfaces to a large number of network performance data sources

• Support for a wide variety of wireless protocols from the air-interface to the core

network

• Filtering and binning module

• Finite stat e event det ection engine

• Time-series and multi-dimensional statistical query module

• Data merging and synchronization / correlation module

• Mapping, charting, and reporting m odules

• Messaging and protocol stack browsers

• Network element database

• Open data import and export module

Analyzer’s flexibility allows it to be configured for a wide range of net work perfor mance-

data analysis tasks.




www.actix.com

3.2 Application Layers

Application Layers can be added to Analyzer t o im plement task or application specific

functionality. Analyzer includes the following application layers:

UMTS Accelerat ed Net w ork Rollout Solution

• Neighbor List Analysis Module

• Handoff State Analysis Module

• CPICH Pollution Module

• Emulated Active Set Module

UMTS CPI CH Level Analysis

• CPICH before RRC Connection Request Module

• CPICH before call end or drop Module

• CPICH during call Module

• CPICH after call end or drop Module

UMTS Call Setup Analysis

• Call Setup Status Module

• Call Sequence Analysis Module

UMTS Call Statistics

• Call Statistics Module

• Call Statist ics PS Module

• Call Sustainability Module

• Call Timing Analysis Module

UMTS Drive Test Summary

• File Summ ary Module

• Coverage Summ ary Module

UMTS Handoff Analysis

• Handoff Breakdown Analysis Module

• SHO per event 1a-1b- 1c Module

UMTS Quality Analysis

• Overall BLER Module

• BLER Per call Module

• BLER during SHO Module




www.actix.com

3.2 .1 Neighbor List Analysis Module

The Neighbor List Analysis provides an automat ed approach for generating optim al

neighbor lists and overcoming m ajor service-degrading problems such as missing

neighbors.

The key components of the neighbor- list analysis module are:

Generation of recommendat ions for optim al neighbor list sett ings based on UMTS/WCDMA

scanner drive test data.

Integration with Network Element Database to audit existing neighbor lists and suggest

changes, and t o correlate non-unique m easured data at tribut es such as Scrambling Code

with unique identifiers such as Sector I D.

The Neighbor List Module implements t he following algorithm:

Ec/I o measurement s below a noise floor are filtered out of the data set before analysis.

User definable binning is used to reduce the num ber of m easurement s points in each bin to

create one value per bin – opt ionally, no binning at all can be applied and the analysis will

run on the full data set.

At each point along th e drive t est, a list of prospective neighbors is accumulated asindicated in Figure 19. I f a neighbor signal is within a user-definable threshold of the best

server in the active set, t hen it is considered as a potential neighbor.

Using t he geographic inform ation in t he log file and t he SC, t he network element dat abase

is searched to identify the Sector and Cell I Ds of the SC.

A symmetrical neighbor array is created in memory which records the number of times

each sector I D is seen as a prospective neighbor of another sector I D as shown in Table 1.

Once all bins in t he log file have been compiled into t he symm etrical matr ix, t he results

are compared against actual neighbor lists contained in the netw ork element database and

the following are calculated:

• a list of sector IDs included in the matrix, but not the actual neighbor list

•

a list of sector IDs included in the actual list but not in the matrix




www.actix.com

Figure 19: Cell A is the best server by CPICH Ec/ Io. Cells B and C are wit hin a user- specified thresholdof Cell A’s Ec/Io, and so are counted as potential neighbors of A. Cell D is not within the required

threshold and so is not counted as a prospective neighbor, nor is Cell E which did not have ameasurable signal contribution at this point in the drive t est.

A B C D A N/A 10 2 15

B 10 N/A 40 0

C 2 40 N/A 12

D 15 0 12 N/A

Table 1: A sample symmetric prospective neighbor array using sector IDs A, B, C, and D

Limitat ions of t he algorithm:

Results are only produced in areas that h ave been tested, so t he test areas should be

carefully considered before removing any Sectors from the neighbor lists

Drive tests do not necessarily emulat e the radio environm ent encountered by pedestrian

and in-building users; however, walk tests and in-building tests may be included in the

analysis as desired

Results are presented in t he following application report s:

• Neighbor List Summary

Drive TestRoute

A

Best Server

B

Neighbour 1

CNeighbour 2

DNot a Neighbour

EExcluded from Analysis




www.actix.com

• Neighbor List Audit

• Recommended Neighbor Lists

Figure 20: A sample Recommended Neighbor Lists report




www.actix.com

3.2.2 CPICH Pollution Analysis Module

The CPICH or Pilot Pollution Analysis uses an emulated Active Set to estimate which pilots

would have been actively demodulated by the UE, and th en detects other pilots above a

user-definable threshold that cause excessive interference. Please see the Emulated Active

Set Module section for more details on how the Active Set is estimated based on WCDMA

scanner measurements.

The pilot pollution algorithm has these components:

• Ec/Io measurements below a noise floor are filtered out of the data set prior to

analysis.

• User definable binning is used to reduce the num ber of m easurement s points in

each bin t o create one value per bin – optionally, no binning at all can be applied

and the analysis will run on t he full data set.

• At each point along the drive t est, CPI CH Ec/I o data f or each Scrambling Code is

used to assign SCs to an Active Set or a Pollution Set (please see the Emulated

Active Set Module section for m ore details).

• The Pollution Set consists of all SCs that are not in the Active Set, and have aCPICH Ec/Io within a user specified pollution threshold of the strongest CPICH

Ec/I o in the Active Set (see Figure 21).

• Using the geographic information in the log file and the SC, the network element

database is searched to ident ify t he Sector and Cell I Ds of t he SC.

• A pollution array is created in memory which records the number of times each

sector ID is seen as a source of pilot pollution as shown in Table 2

• All bins in t he log file are then processed into the pollution m atrix.




www.actix.com

Figure 21: Cell A, B and C are part of t he Active Set, as determined by the Emulated Active Set

module. Cell D has a CPICH Ec/I o wit hin a user-specified pollut ion thr eshold of the Active Set’s bestserver Ec/Io, and so is counted as a contributor to pilot pollution at this point in the drive test. Cell E

has a CPICH Ec/Io that is not within this threshold and so is not a pollution source.

Sector I D Pollution

Count

A 0

B 150

C 45

D 12

Table 2: A sample pollution array indicating the number of points at which each sector caused pilot

pollution for sector IDs A, B, C, and D

Results are presented in the Pilot Pollution Analysis application report as shown in Figure

22. In addition, Pilot Pollution may be geographically analyzed for each SC by accessing

the Pollution_for_SC att ribute in t he workspace view.

DPollution Source

A

Active Set

B

Active Set

CActive Set

Drive Test

Route ENot a Pollution Source, or inActive Set




www.actix.com

Figure 22: The Pilot Pollution Analysis report indicates the worst interferers sorted by Scrambling Code

3.2.3 Handoff State Analysis Module (for scanner)

The Handoff State Analysis module uses the emulated Active Set to det ermine t he handoff

state at each point along a drive t est. Statistics on handoff state m ay th en be calculated

and presented in a report form at. Excessive handoff stat e reduces capacity and increase

infrastructur e costs f or a given tr affic level. Please see the Emulated Active Set Module

section for more details on how the Active Set is estimated based on WCDMA scanner

measurements.

The handoff state algorithm has the following components:

• The Active Set of pilot s is determined using t he Emulat ed Active Set module

• Using the geographic information in the log file and the SC, the network element

database is searched to ident ify t he Sector and Cell I Ds of t he SC

• Handoff state is calculated by determ ining the configuration of t he sectors in t he

Active Set as shown in Figure 23

• All bins in t he log file are then processed into the handoff stat e mat rix

Reports showing the percentage of handoff state for each sector and for t he tot al drive test

may then be calculated as shown in Figure 24.




www.actix.com

Figure 23: The Handoff State Analysis examines Sector IDs involved in call at a given drive test pointand determines which of the above states applies, based on UMTS scanner data

Sin le- sect or

Softer Soft

3 - w a So ft er

3 sectorssame node B

Soft-softer


3-w ay soft





www.actix.com

Figure 24: A report showing the percentage of drive test in each handoff state for scanner data




www.actix.com

3.2.4 Emulated Active Set Module

CPICH Pollution Analysis and Handoff Analysis are both based on a calculated Active Set,

which is determined by the Emulated Active Set m odule. The Emulat ed Active Set m odule

implement s the 3GPP handoff algorithm and uses scanner Ec/I o m easurement s in

conjunction w ith user-specific 3GPP handoff t hresholds to emu late t he Active Set at each

point along a drive t est. Figure 25 shows a sample set of scanner data for t hree individual

SCs with color and v ertical lines indicating t ransitions of pilots into and out of the Active

Set.

Figure 25: Using Scanner Ec/Io measurements to implement 3GPP handoff algorithms for the Active

Set

Figure 26 shows the list of at tr ibutes available for m odification by the user, as indicated inth e 3GPP specifications:

Figure 26: Setting 3GPP handoff algorithm attributes including Reporting Range: Hysteresis Event and

Time to Trigger Event




www.actix.com

3.2.5 CPICH before RRC Connection Request Module

The CPICH before RRC Connection Request module helps the engineer to understand the

environment right before the call started or t o be more precise, before t he first RRC

connection r equest happens. For every call in the log file, t he report can show the

following parameters:

• Call Ident ification, based on the at tr ibute “ Uu_Call_id”

• Time of the first RRC Connection Request for a specific call

• Site the call was placed, based on the at tr ibute “ ServingCellid”

• Scrambling Code the call originated on, based on th e att ribute

“Uu_ActiveSet_SC_0”

• Ec/Io of that same Scrambling Code, based on the attribute

“Uu_ActiveSet_EcNo_0”

• RSCP of t hat sam e Scrambling Code, based on t he att ribute

“Uu_ActiveSet_RSCP_0” or the calculated RSCP if the regular RSCP values are notpresent or were not logged.

• Site, SC, Ec/ I o and RSCP of t he Monitor ed Set if app licable

• End result of t hat part icular call

For any of these parameters, the module searches 5 seconds before the first RRC

Connection Request for the specific details. If it cannot find t he parameters during t hose 5

seconds, the v alue “No Data” is shown.

Figure 27 shows a typical analysis executed by the CPICH before RRC Connection Request

module. For the engineer, it is an easy way t o look at th e conditions before the call started

and the end result.

Figure 27: Example of a log file analyzed by the CPICH before RRC Connection Request m odule




www.actix.com

3.2 .6 CPI CH before call end or drop Module

The CPICH before call end or drop module helps th e engineer to u nderstand t he

environment right before the call ended or dropped. For every call in the log file, the report

can show the following parameters:

• Call Ident ification, based on the at tr ibute “ Uu_Call_id”

• Time when t he call ended or dropped (see event definitions)

• Site ID of t he active site when the call ended or dropped (att ribute ServingCellid)

• Scrambling Code of t he 1 st finger in t he Active Set

• Ec/I o of th at same Scrambling Code

• RSCP of that same Scrambling Code


•

End result of t hat part icular callFigure 28 shows a typical analysis executed by the CPICH before call end or drop module.

For t he engineer, it is an easy way t o look at t he conditions right before the call ended.

Figure 28: Example of a log file analyzed by the CPICH before call end or drop module




www.actix.com

3.2 .7 CPI CH dur ing call Module

The CPICH during call module helps the engineer t o understand t he environment during a

particular call. For every call in the log file, t he report can show t he following parameters:

• Call I dentification

• Site ID of the most common active site (site associated with the scrambling code

of the first finger in the active set)

• Most com m on Scrambling Code of 1st finger in t he Active Set

• Average Ec/I o during t he entire call

• Average RSCP during the entire call

• Site ID of the most common monitored site (site associated with the scrambling

code of the first finger in the monitored set)

• Most comm on Scrambling Code in t he Monitored Set

• Average Ec/I o during t he entire call

• Average RSCP during the entire call

• End result of t hat part icular call

Figure 29 shows a typical analysis executed by the CPICH during call module. For the

engineer, it is an easy way to look at the average conditions during the call.

Figure 29: Example of a log file analyzed by the CPICH during call module




www.actix.com

3.2 .8 CPI CH after call end or d rop Module

The CPICH after call end or drop module helps the engineer t o understand t he environment

right after t he call ended or dropped. For every call in the log file, t he report can show th e

following parameters:

• Call I dentification

• Time when t he call ended or dr opped

• Site ID of t he active site when the call ended or dropped

• Scrambling Code of t he 1 st finger in t he Active Set

• Ec/I o of th at same Scrambling Code

• RSCP of that same Scrambling Code


•

End result of t hat part icular callFigure 30 shows a ty pical analysis executed by the CPICH after call end or drop module.

For t he engineer, it is an easy way t o look at t he conditions right after t he call ended.

Figure 30: Exam ple of a log file analyzed by the CPICH after call end or drop m odule




www.actix.com

3.2 .9 Call Setup Status Module

The Call Setup Status m odule offers a general overview on how and when t he call failed.

The normal call sequence should go like t his:

• RRC Connection Request (MOC)

or Paging Type1 (MTC)

• RRC Connection Setup

• RRC Connection Complete

• MM CM Service Request (MOC) or

Paging Response (MTC)

• MM CM Service Accept

• Authentication Request

• Authentication Accept

• Security Mode Comm and

• Security Mode Complete

• CC Setup

• CC Call Proceeding

• Radio Bearer Setup

• Radio Bearer Setup Complete

• CC Alert

• CC Connect

If all messages are received properly, the call is a success. If it fails to reach the CCConnect, it should be pegged as a call failure and this module should give t he reason for it.

Refer to section 3.2 Event Definitions for more details.

Figure 31 shows a typical analysis executed by t he call setup st atus m odule.

Figure 31: Example of a log file analyzed by the call setup status module




www.actix.com

3.2 .10 Call Sequence Analysis Module

The Call Sequence Analysis module offers a general overview on how call failed and when

they failed. This module has the same structu re and analysis as the call setup st atus

module except for a few differences. I t doesn’t sum marize as what is th e cause of the

failure. On the other h and, it giv es the call sequence with detailed inform ation on every

call and th e outcome of it . I t gives t he engineer th e possibility t o look at individual calls on

a m essage-by-m essage basis.

Figure 32: Example of a log file analyzed by the call sequence analysis module




www.actix.com

3.2 .11 Call Stat istics Module ( CS or PS)

The Call Statistics Module helps the engineer t o have a quick look at the ov erall

perform ance during a specific drive test. The following param eters' statistics are defined in

each file:

Total Number of calls: Number of Mobile Originated Calls (MOC) + Number of Mobile

Terminated Calls (MTC). This includes all calls, even failures.

Successful I ncomin g Calls: Num ber of successful Mobile Term inated Calls (MTC). To be

successful, a call needs to follow the call sequence as mentioned in section 3.2

Successful Outg oing Calls: Num ber of successful Mobile Originated Calls (MOC). To be

successful, a call needs to follow the call sequence as mentioned in section 3.2

Total Successful Calls:

Successful I ncoming Calls +

Successful Out going Calls

Connected Percentage: Total

Successful Calls/Total number

of calls * 100

Call Failures – In coming:

Access Failure for a Mobile

Terminated Call (MTC) as

defined in section 3. 2

Call Failures – Outgoing:

Access Failure for a Mobile

Originated Call (MOC) as

defined in section 3. 2

Access Failure Rate: Total

Access Failures/Total number

of calls * 100

Total Drops: Total number of

dropped calls. A dropped call is

defined as one of the

following:

Drop Rate percentage: Total

Drops/Total Successful Calls *

100

Total Completed Calls: Total

num ber of completed calls. A

completed call is defined as

the following:

Success Rate: Total completed

calls/Tot al Successful Calls *

100

Figure 33: Example of a log file analyzed by the

Call Statistics Module




www.actix.com

3.2.12 Call Sustainability Module

The call sustainability

module helps theengineer to have a

quick view at t he call

duration for all calls

during the drive route.

The statistic is

calculated on a per call

basis and is the

difference in time

when t he call ends and

when the call starts.

More precisely:

Call Sustainability =

Time when RRC

Connection request

happens (or paging

type 1) – Time when

call drops or ends.

Figure 34 shows the

call sustainability

statistics and t he call

duration distribution.

Figure 34: Examp le of a log file analyzed by thecall sustainability module




www.actix.com

3.2 .13 Call Timing Analysis Module

The Call Timing Analysis gives various time statistics on differences between specific

messages. In cases where the RRC Connection Request terminology is used, it relates to

the first RRC Connection Request m essage tr ansmitt ed.

Figure 35: Example of a log file analyzed by the call tim ing analysis module




www.actix.com

3.2.1 4 File Summ ary Module

The file summary module helps the

engineer t o visualize quickly t he

content of a file. The thr esholds for

the coverage and quality charts are:

Coverage:

Good: RSCP > -80 dBm

Fair: -80 dBm > = RSCP > = -95 dBm

Poor: -9 5 dBm > RSCP

Quality:

Good: Ec/I o > -8 dB

Fair : - 8 dB > = Ec/Io > = -15 dB

Poor: - 15 dB > Ec/I o

Figure 36: Example of a log file analyzed

by the file summary module




www.actix.com

3.2.1 5 Coverage Summ ary Module

The file summ ary m odule helps the engineer to visualize quickly t he statistics related to

the st rongest RSCP and t he strongest Ec/No for a particular file.

Figure 37: Example of a log file analyzed by thecoverage summary module




www.actix.com

3.2.16 Handoff Breakdown Analysis Module (Handset)

The Handoff State Analysis

module for handset uses the Real

Active Set from the handset to

determine the handoff state at

each point along a drive t est.

Statistics on handoff state may

then be calculated and pr esented

in a report for mat . Excessive

handoff stat e reduces capacity

and increase infrastructure costs

for a given traffic level. Please see

section 3.2.3 for more details on

the Handoff Stat e Analysis for

scanner.

The handoff state algorithm has

the following components:

Using t he geographic inform ation

in the log file and the SC, thenetwork element database is

searched to identify the Sector

and Cell IDs of the SC

Handoff state is calculated by

determining the configuration of

the sectors in t he Active Set as

shown in Figure 23 – Section

3.3.3

All bins in the log file are then

processed into th e handoff state

matr ix

The Actual SHO Overhead

represents the sum of all soft-

handoff configurations

Reports showing t he percentage

of handoff stat e for each sector

and for the total drive test m ay

then be calculated as shown in

Figure 38.


handoff state analysis for handset




www.actix.com

3.2.1 7 SHO per event 1a-1b- 1c Module

The SHO per event 1a-1b-1c module gives a brief summary about the different types of

handoff that occur in a file. It shows quickly the number of:

Addition: Event 1a

Removal: Event 1b

Replacement : Event 1c

Also, it reports th e number of completion for each of those events and calculates a

percentage of success.

Figure 39: Example of a log file analyzed by thesoft-handover performance module




www.actix.com

3.2.18 Overall BLER Module

The overall BLER (Block Error

Rate) module gives a brief

summary about the

distribution and stat istical

analysis of BLER for an entire

file.

Figure 40: Example of a log file analyzed by the Overall

BLER module

3.2.19 BLER Per call Module

The BLER per call m odulegives a summary of the main

statistics associated wit h t he

BLER on a call-b y- call basis.

The maximum value

The minimum value

The average value for th at

particular call

Figure 41: Example of a log file analyzed by the BLER percall module




www.actix.com

3.2.20 BLER during SHO Module

The BLER during SHO (soft handover) m odule provides stat istics on the downlink t ransport

channel BLER aggregated across all SHOs and on a call-by-call basis (note that only the

calls wit h BLER measurements dur ing t he SHO procedure will be included in t his report.

Figure 42: Example of a log file analyzed by theBLER during SHO module

3.3 Filters

Filters can be added to Analyzer to im plement t ask or application- specific functionality.

Analyzer includes the following pre- defined filters:

• Poor Mobile Receive Power

CPI CH_RSCP_in_ActiveSet[ 0] < -95 dBm

• High Mobile Transmit Power

UeTransmit tedPower > 0 dBm

• Low Mobile Transmit Power

UeTransmit tedPower < -30 dBm

• High Mobile Receive Power

CPI CH_RSCP_in_ActiveSet[ 0] > -80 dBm

• Poor Ec/No

CPI CH_EcNo_in_ActiveSet[ 0] < -15 dB

• High Ec/No

CPI CH_EcNo_in_ActiveSet[ 0] > -8 dB




www.actix.com

3.4 Stateforms

Stateform s can be added to Analyzer to implem ent t ask or application-specific

functionality. Analyzer includes the following stateforms:

• UMTS Data Event

• Navigator

• UMTS Data Session

• UMTS Throughput

• UMTS Top 10 Scan

Measurements

• UMTS UE Active + Monitor ed Set

• UMTS UE Call Information

• UMTS UE Measurem ents Charts

• UMTS UE Radio Parameters

• UMTS UE Transport Channel Info

• UMTS Voice

• Event Navigator

3.4 .1 UMTS Data Event Navigat or

The UMTS Data Event Navigator stateform allows the engineer t o view th e entire drive t est

with just one quick look. During a data session, it is possible to keep tr ack of the following

events:

• GPRS_PDPContextAct_Successful

• GPRS_PDPContextDeact_Successful

• GPRS_Attach_Successful

• GPRS_Detach_Successful

• GPRS_PDPContextAct_Failure

• GPRS_RAU_Successful

• Event_Task_Start

While keeping tr ack of the current SC in the active set. Figure 42 shows an example of

those different events at different m oments in time w ith t he track at t he top showing the

SC.


UMTS Data Event Navigator Stateform




www.actix.com

3.4.2 UMTS Data Session

The UMTS Data Session stateform allows the engineer to view the dat a testing inf ormat ion

collected during a data session.


UMTS Data Session Stat eform




www.actix.com

3.4 .3 UMTS Throughput

The UMTS Throughput stateform chart allows the engineer t o view t he application and I P

downlink throughput graphically for the entire drive test. This information comes from the

data testing information collected during the drive test.

Figure 45: Example of a log file analyzed by theUMTS Throughput Stateform




www.actix.com

3.4 .4 UMTS Top 10 Scan Measurem ents

The UMTS Top 10 Scan Measurements stat eform allows the engineer to v iew import ant

details regarding the scanner measurement s. The following param eters are displayed at

any specific moment during the drive test replay:

• Top 10 Scrambling Code based on t heir Ec/ Io

• Top 10 Ec/Io for these respective SC

• Top 10 RSCP for th ese respective SC

• Global RSSI


UMTS Top 10 Scan Measurements Stat eform




www.actix.com

3.4 .5 UMTS UE Activ e + Monitored Set

The UMTS UE Active + Monitored Set stateform allows t he engineer to visualize rapidly the

content of the active and monitored sets at any specific moment during the drive test. The

following parameters are represented for both the active and the monitored sets.

• The Scrambling Code

• The Ec/No for each of those scrambling code

• The RSCP for each of those scrambling code

• The Path loss if applicable

It is a very quick way for the engineer to follow the active and monitored sets. Using the

replay tool, t he engineer can follow the driv e test and analyze very quickly any particular

events.

Figure 47: Example of a log file analyzed by theUMTS UE Active + Monitored Set Stat eform




www.actix.com

3.4 .6 UMTS UE Call I nform ation

The UMTS UE call information st ateform allows the engineer t o have a quick view at t he

following events:

• IMSI – Mobile’s Identification

number used for testing

• Called Party – Number called for

that particular test/call

• Calling Party – I n case of mobile

terminated calls, the number of

the party that called

• Call id – The call identification

based on the UMTS call tracker

• Call State – The state t he m obile

is on. Different states are:

• In i t

• Idle

• RRC Con Request

• RRC Con Setup

• RRC Setup Complete

• Outgoing Call Setup

• Incom ing Call Setup

• Paging

• I n Call

• Security Mode Comm and

• Security Com plete

• CC Setup

• Authentication Request

• Authentication Response

• CC Call Proceeding

• RAB Setup

• RAB Complet e

• Channel Reconfig

• Radio Bearer Reconfig

• GSM Mode

• LAC

• RAC

Figure 48: Example of a log file analyzed by theUMTS UE Call Information Stateform




www.actix.com

3.4.7 UMTS UE Measurements Charts

The UMTS UE Measurements Charts stateform allows the engineer to look at t he most

important information in a log file. It is very easy to visualize rapidly the following

parameters:

• EcNo – Uu_ActiveSet_ EcNo

• RSSI – UTRA_UE_CarrierRSSI

• TxPower – UE_TxPow

• SIR – Uu_SIR

• SIR_Target – Uu_TargetSIR


UMTS UE Measurements Charts Stateform




www.actix.com

3.4.8 UMTS UE Radio Param eter s

The UMTS UE Radio Parameters stateform allows the engineer to view radio parameters at

a specific mom ent during t he drive test. The available parameters are:

• TxPower

• RSSI

• SIR

• SIR Target

• UTRA_ARFCN_DL

Figure 50: Example of a log file analyzed by theUMTS UE Radio Parameters Stateform




www.actix.com

3.4 .9 UMTS UE Transport Channel I nfo

The UMTS UE Transport Channel Info allows the engineer to visualize the BLER per channel

and also the aggregate BLER.

Figure 51: Example of a log file analyzed by theUMTS UE Transport Channel I nfo Statefor m




www.actix.com

3.4 .10 UMTS Voice Event Navigator (CS Only)

The UMTS Voice Event Navigator stateform allows the engineer to view the ent ire drive

test w ith j ust one quick look. During a session, it is possible to k eep track of th e following

events:

• Uu_OutgoingCallOK

• Uu_IncomingCallOK

• Uu_OutgoingCallSetupFail

• Uu_IncomingCallSetupFail

• Uu_CallDropped

• Uu_CallCompleted

While keeping tr ack of the current SC in th e active set. Figure 51 shows an example of

those different events at different moments in time with the colored track at the top

showing t he SC.

Figure 52: Example of a log file analyzed by the UMTS Voice Event Navigator Stateform

Actix Analyzer UMTS Analysis Guide-libre

Documents

Transcript of Actix Analyzer UMTS Analysis Guide-libre