Professional Documents
Culture Documents
Analysis Guide
November 2005
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 no responsibility or liability for any errors or inaccuracies that appear in this documentation. Copyright Actix 2005-2008. All rights reserved. All trademarks are hereby acknowledged.
www.actix.com
Contents
1 INTRODUCTION .........................................................................................4 2 OPERATIONAL TASKS AND PROCESSES .............................................................5
2.1 SITE INTEGRATION AND INFRASTRUCTURE TESTING .................................................... 7 2.2 DETAILED CALL SEQUENCE ANALYSIS .................................................................... 8 2.3 BENCHMARKING AND STATISTICAL ANALYSIS ............................................................ 9 2.4 RADIO LINK PERFORMANCE TROUBLESHOOTING........................................................10
www.actix.com
Introduction 4
1 Introduction
It is widely recognized that increasing productivity fuelled much of the global economic expansion of the 1990s. Technological advances in software and hardware usually enable these productivity improvements, although there is often a lag between the availability of the new technology, and its widespread acceptance and deployment 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 1980s in the US. When the technology initially became available, it was only sparingly deployed, and the units were often placed inside bank buildings where the productivity enhancements they offered were limited. Likewise, unattended gasoline pump technology has been slow to roll out in Europe, but as the technology has become widely adapted, huge efficiency gains have been realized. The wireless industry is now at a similar point. It understands that the traditional laborintensive techniques for maximizing 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 to fully optimize a UMTS network. It allows the engineer to understand the causes and reasons for drop calls and access failures. Analyzer offers an unprecedented capability to execute a detailed examination of message flows and automating statistical analyses of performance. Analyzer significantly accelerates the rollout, troubleshooting and optimization 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 embodies our extensive experience as the market leader in optimization solutions for CDMA, UMTS and GSM. All of the lessons learned and the techniques developed over a 10-year period have been incorporated into these powerful, vendor-independent solutions for UMTS infrastructure. This document provides an overview of the key benefits, applications and features of Analyzer. For additional information, including white papers and other literature, please refer to www.actix.com.
www.actix.com
Rollout Verification S l R&D Trials Initial Rollout Immature Buildout Mature Growth
Figure 1: Applicability of Analyzer begins in the Initial Rollout and continues throughout the lifecycle of the network deployment
Analyzer is a powerful tool designed to help the RF engineer analyze data from scanner and handset sources. It gives a detailed analysis during the whole drive route. From missing neighbor to pilot pollution detection, the different embedded events give an absolute advantage to the RF engineer in understanding the source of different problems. Figure 2 depicts some of the major processes performed by engineering teams during the initial rollout, immature buildout and mature growth phases; and indicates the key radiolink configuration tasks that are common across these processes. The following sections provide an outline (plus additional details) of the processes and tasks typically performed during those phases.
www.actix.com
Initial Rollout
Immature Buildout
Mature Growth
Phases
Processes
Subscriber-Perceived Performance
On-going Optimization
Network Growth
Power Measurements
Event Detections
Tasks
Benchmarking
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 tasks for site integration and testing, coverage analysis, troubleshooting and optimization:
Site Integration and Infrastructure Testing Detailed Call Sequence Analysis Benchmarking and Statistical Analysis Radio Link Performance Troubleshooting Event Detection and Drive 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 platformwhich includes
www.actix.com
user-definable query and open data import capabilitiesit may be used for many ad-hoc troubleshooting and performance analysis tasks beyond those covered in this document.
The file summary report allows the engineer to have a quick look at the 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 statistical analysis Automated report generation containing statistical summaries of key performance indicator
Figure 3: Charts and graphs for UMTS site integration and infrastructure testing
www.actix.com
Detailed call sequence analysis on a message by message basis Automated report generation for visualization of call sequence messages Automated report generation statistical summaries of call setup problems
www.actix.com
Automated report generation for quick visualization of call statistics such as drop calls, access failures, call sustainability, etc. Working with different sources of data to create homogeneous set of reports for benchmarking User-defined queries allowing easy access to different statistics
www.actix.com
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 attributes, depending on the specific vendor and specific source (handset or scanner):
www.actix.com
Mobile Transmit Power, Mobile Receive Power, BLER CPICH Ec/No, Ec/Io and RSCP per scrambling code Chip Offset and Delay Spread per SC Ec/Io, RSCP and Pathloss for Nth best SCs CPICH Ec/No and SC in Active and Monitored set Handoff State, Call ID
www.actix.com
Feature Overview 12
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 state event detection engine Time-series and multi-dimensional statistical query module Data merging and synchronization / correlation module Mapping, charting, and reporting modules Messaging and protocol stack browsers Network element database Open data import and export module
Analyzers flexibility allows it to be configured for a wide range of network performancedata analysis tasks.
www.actix.com
Feature Overview 13
Neighbor List Analysis Module Handoff State Analysis Module CPICH Pollution Module Emulated Active Set Module
UMTS CPICH 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 Statistics PS Module Call Sustainability Module Call Timing Analysis Module
UMTS Drive Test Summary File Summary Module Coverage Summary 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
Feature Overview 14
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
Feature Overview 15
C Neighbour 2
D Not a Neighbour
Figure 19: Cell A is the best server by CPICH Ec/Io. Cells B and C are within a user-specified threshold of Cell As 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 a measurable signal contribution at this point in the drive test.
A A B C D 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
Limitations of the algorithm: Results are only produced in areas that have been tested, so the test areas should be carefully considered before removing any Sectors from the neighbor lists Drive tests do not necessarily emulate the radio environment 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 the following application reports:
www.actix.com
Feature Overview 16
www.actix.com
Feature Overview 17
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 number of measurements points in each bin to create one value per bin optionally, no binning at all can be applied and the analysis will run on the full data set. At each point along the drive test, CPICH Ec/Io data for 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 more details). The Pollution Set consists of all SCs that are not in the Active Set, and have a CPICH Ec/Io within a user specified pollution threshold of the strongest CPICH Ec/Io 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 identify the Sector and Cell IDs of the 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 the log file are then processed into the pollution matrix.
www.actix.com
Feature Overview 18
B Active Set
Figure 21: Cell A, B and C are part of the Active Set, as determined by the Emulated Active Set module. Cell D has a CPICH Ec/Io within a user-specified pollution threshold of the Active Sets best server 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 ID A B C D
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 attribute in the workspace view.
www.actix.com
Feature Overview 19
Figure 22: The Pilot Pollution Analysis report indicates the worst interferers sorted by Scrambling Code
The Active Set of pilots is determined using the Emulated Active Set module Using the geographic information in the log file and the SC, the network 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 the Active Set as shown in Figure 23 All bins in the log file are then processed into the handoff state matrix
Reports showing the percentage of handoff state for each sector and for the total drive test may then be calculated as shown in Figure 24.
www.actix.com
Feature Overview 20
Single-sector
3-way Softer
Figure 23: The Handoff State Analysis examines Sector IDs involved in call at a given drive test point and determines which of the above states applies, based on UMTS scanner data
www.actix.com
Feature Overview 21
Figure 24: A report showing the percentage of drive test in each handoff state for scanner data
www.actix.com
Feature Overview 22
Figure 25: Using Scanner Ec/Io measurements to implement 3GPP handoff algorithms for the Active Set
Figure 26 shows the list of attributes available for modification by the user, as indicated in the 3GPP specifications:
Figure 26: Setting 3GPP handoff algorithm attributes including Reporting Range: Hysteresis Event and Time to Trigger Event
www.actix.com
Feature Overview 23
Call Identification, based on the attribute Uu_Call_id Time of the first RRC Connection Request for a specific call Site the call was placed, based on the attribute ServingCellid Scrambling Code the call originated on, based on the attribute Uu_ActiveSet_SC_0 Ec/Io of that same Scrambling Code, based on the attribute Uu_ActiveSet_EcNo_0 RSCP of that same Scrambling Code, based on the attribute Uu_ActiveSet_RSCP_0 or the calculated RSCP if the regular RSCP values are not present or were not logged. Site, SC, Ec/Io and RSCP of the Monitored Set if applicable End result of that particular 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 the parameters during those 5 seconds, the value 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 to look at the conditions before the call started and the end result.
Figure 27: Example of a log file analyzed by the CPICH before RRC Connection Request module
www.actix.com
Feature Overview 24
Call Identification, based on the attribute Uu_Call_id Time when the call ended or dropped (see event definitions) Site ID of the active site when the call ended or dropped (attribute ServingCellid) Scrambling Code of the 1st finger in the Active Set Ec/Io of that same Scrambling Code RSCP of that same Scrambling Code Site, SC, Ec/Io and RSCP of the Monitored Set if applicable End result of that particular call
Figure 28 shows a typical analysis executed by the CPICH before call end or drop module. For the engineer, it is an easy way to look at the 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
Feature Overview 25
Call Identification Site ID of the most common active site (site associated with the scrambling code of the first finger in the active set) Most common Scrambling Code of 1st finger in the Active Set Average Ec/Io during the 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 common Scrambling Code in the Monitored Set Average Ec/Io during the entire call Average RSCP during the entire call End result of that particular 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
Feature Overview 26
Call Identification Time when the call ended or dropped Site ID of the active site when the call ended or dropped Scrambling Code of the 1st finger in the Active Set Ec/Io of that same Scrambling Code RSCP of that same Scrambling Code Site, SC, Ec/Io and RSCP of the Monitored Set if applicable End result of that particular call
Figure 30 shows a typical analysis executed by the CPICH after call end or drop module. For the engineer, it is an easy way to look at the conditions right after the call ended.
Figure 30: Example of a log file analyzed by the CPICH after call end or drop module
www.actix.com
Feature Overview 27
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 Command 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 CC Connect, it should be pegged as a call failure and this module should give the reason for it. Refer to section 3.2 Event Definitions for more details. Figure 31 shows a typical analysis executed by the call setup status module.
Figure 31: Example of a log file analyzed by the call setup status module
www.actix.com
Feature Overview 28
Figure 32: Example of a log file analyzed by the call sequence analysis module
www.actix.com
Feature Overview 29
Figure 33: Example of a log file analyzed by the Call Statistics Module
www.actix.com
Feature Overview 30
Figure 34: Example of a log file analyzed by the call sustainability module
www.actix.com
Feature Overview 31
Figure 35: Example of a log file analyzed by the call timing analysis module
www.actix.com
Feature Overview 32
Quality: Good: Ec/Io > -8 dB Fair: -8 dB >= Ec/Io >= -15 dB Poor: -15 dB > Ec/Io
Figure 36: Example of a log file analyzed by the file summary module
www.actix.com
Feature Overview 33
Figure 37: Example of a log file analyzed by the coverage summary module
www.actix.com
Feature Overview 34
www.actix.com
Feature Overview 35
Also, it reports the number of completion for each of those events and calculates a percentage of success.
Figure 39: Example of a log file analyzed by the soft-handover performance module
www.actix.com
Feature Overview 36
Figure 40: Example of a log file analyzed by the Overall BLER module
Figure 41: Example of a log file analyzed by the BLER per call module
www.actix.com
Feature Overview 37
Figure 42: Example of a log file analyzed by the BLER during SHO module
3.3 Filters
Filters can be added to Analyzer to implement task or application-specific functionality. Analyzer includes the following pre-defined filters:
Poor Mobile Receive Power CPICH_RSCP_in_ActiveSet[0] < -95 dBm High Mobile Transmit Power UeTransmittedPower > 0 dBm Low Mobile Transmit Power UeTransmittedPower < -30 dBm High Mobile Receive Power CPICH_RSCP_in_ActiveSet[0] > -80 dBm Poor Ec/No CPICH_EcNo_in_ActiveSet[0] < -15 dB High Ec/No CPICH_EcNo_in_ActiveSet[0] > -8 dB
www.actix.com
Feature Overview 38
3.4 Stateforms
Stateforms can be added to Analyzer to implement task 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 + Monitored Set
UMTS UE Call Information UMTS UE Measurements Charts UMTS UE Radio Parameters UMTS UE Transport Channel Info UMTS Voice Event Navigator
While keeping track of the current SC in the active set. Figure 42 shows an example of those different events at different moments in time with the track at the top showing the SC.
Figure 43: Example of a log file analyzed by the UMTS Data Event Navigator Stateform
www.actix.com
Feature Overview 39
Figure 44: Example of a log file analyzed by the UMTS Data Session Stateform
www.actix.com
Feature Overview 40
Figure 45: Example of a log file analyzed by the UMTS Throughput Stateform
www.actix.com
Feature Overview 41
Top 10 Scrambling Code based on their Ec/Io Top 10 Ec/Io for these respective SC Top 10 RSCP for these respective SC Global RSSI
Figure 46: Example of a log file analyzed by the UMTS Top 10 Scan Measurements Stateform
www.actix.com
Feature Overview 42
The Scrambling Code The Ec/No for each of those scrambling code The RSCP for each of those scrambling code The Pathloss if applicable
It is a very quick way for the engineer to follow the active and monitored sets. Using the replay tool, the engineer can follow the drive test and analyze very quickly any particular events.
Figure 47: Example of a log file analyzed by the UMTS UE Active + Monitored Set Stateform
www.actix.com
Feature Overview 43
IMSI Mobiles Identification number used for testing Called Party Number called for that particular test/call Calling Party In 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 the mobile is on. Different states are: Init Idle RRC Con Request RRC Con Setup RRC Setup Complete Outgoing Call Setup Incoming Call Setup
Paging In Call Security Mode Command Security Complete CC Setup Authentication Request Authentication Response CC Call Proceeding RAB Setup RAB Complete Channel Reconfig Radio Bearer Reconfig GSM Mode LAC RAC
Figure 48: Example of a log file analyzed by the UMTS UE Call Information Stateform
www.actix.com
Feature Overview 44
EcNo Uu_ActiveSet_EcNo RSSI UTRA_UE_CarrierRSSI TxPower UE_TxPow SIR Uu_SIR SIR_Target Uu_TargetSIR
Figure 49: Example of a log file analyzed by the UMTS UE Measurements Charts Stateform
www.actix.com
Feature Overview 45
Figure 50: Example of a log file analyzed by the UMTS UE Radio Parameters Stateform
www.actix.com
Feature Overview 46
Figure 51: Example of a log file analyzed by the UMTS UE Transport Channel Info Stateform
www.actix.com
Feature Overview 47
While keeping track of the current SC in the active set. Figure 51 shows an example of those different events at different moments in time with the colored track at the top showing the SC.
Figure 52: Example of a log file analyzed by the UMTS Voice Event Navigator Stateform
www.actix.com
Feature Overview 48
www.actix.com