You are on page 1of 268

Desktop

User Guide

November 2012

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 2012. All rights reserved. All trademarks are hereby acknowledged.

www.actix.com

Contents
1 ABOUT SPOTLIGHT ..................................................................................... 6
1.2 USING SPOTLIGHT TO SOLVE NETWORK PROBLEMS ...................................................... 7 1.3 ABOUT SPOTLIGHT PROJECTS ............................................................................... 9

2 IMPORTING CELL SITE DATA ....................................................................... 10
2.1 IMPORTING NETWORK DATA .............................................................................. 10 2.2 UPDATING CELL SITE DATA ............................................................................... 19 2.3 LOADING CELL SITE DATA ................................................................................ 19 2.4 CELL SITE DISPLAY ........................................................................................ 20 2.5 SETTING THRESHOLDS FOR DATA IMPORT .............................................................. 25

3 STARTING SPOTLIGHT ............................................................................... 26 4 CREATING A PROJECT ................................................................................ 27
4.1 STEP 1: CHOOSE NAME AND TEMPLATE ................................................................. 27 4.2 STEP 2: SET PREFERENCES AND THRESHOLDS ......................................................... 28 4.3 STEP 3: CHOOSE DATA ................................................................................... 31

5 USING THE SUMMARY DASHBOARD ................................................................ 33
5.1 NAVIGATING AROUND SPOTLIGHT ........................................................................ 34 5.2 THE TOP PANEL ............................................................................................. 35 5.3 THE ISSUES PANEL ......................................................................................... 36 5.4 THE MAP ..................................................................................................... 37

6 USING SPOTLIGHT REPORTS ........................................................................ 38 7 USING THE RADIO NETWORK EXPLORER .......................................................... 40
7.1 ABOUT THE RADIO NETWORK EXPLORER ................................................................ 40 7.2 CDMA / EVDO CELL COVERAGE ANALYSIS ............................................................ 42 7.3 CDMA / EVDO NEIGHBOR LIST ANALYSIS ............................................................. 48 7.4 CDMA / EVDO PILOT POLLUTION ANALYSIS .......................................................... 54 7.5 EVDO SYSTEM PERFORMANCE ANALYSIS ............................................................... 58 7.6 GSM CELL COVERAGE ANALYSIS ......................................................................... 63 7.7 GSM 2G MISSING NEIGHBORS ANALYSIS .............................................................. 73 7.8 LTE CELL COVERAGE ANALYSIS .......................................................................... 79 7.9 LTE 4G – 3G/2G MISSING NEIGHBORS ............................................................... 83 7.10 UMTS / HSPA 3G NEIGHBOR LIST ANALYSIS ....................................................... 87 7.11 UMTS / HSPA 3G-2G NEIGHBOR LIST ANALYSIS .................................................. 93 7.12 UMTS / HSPA CELL COVERAGE ANALYSIS ........................................................... 99 7.13 UMTS / HSPA CELL PILOT POLLUTION ANALYSIS ................................................. 106 7.14 ABOUT THE INTERFERENCE FACTOR (‘F’ FACTOR) .................................................. 110

8 USING THE EVENT EXPLORER ..................................................................... 113
8.1 ABOUT THE EVENT EXPLORER ........................................................................... 113 8.2 DATA SERVICE ANALYSIS ............................................................................... 116 8.3 DRILL DOWN FROM THE EVENT EXPLORER ............................................................ 131

www.actix.com

9 PERFORMING A MORE DETAILED ANALYSIS ..................................................... 135
9.1 BEFORE YOU START ...................................................................................... 135 9.2 TO LOAD DATA INTO ANALYZER CLASSIC.............................................................. 135

10 BATCH SECTOR PLOT ............................................................................ 137 11 CREATING A SPOTLIGHT PROJECT TEMPLATE ................................................. 140
11.1 STEP 1: CHOOSE NAME AND STARTING TEMPLATE ................................................ 141 11.2 STEP 2: CHOOSE DEVICES ............................................................................ 142 11.3 STEP 3: CHOOSE KPIS AND REPORTS............................................................... 146 11.4 STEP 4: CHOOSE ATTRIBUTES ........................................................................ 147 11.5 STEP 5: CHOOSE GLOBAL FILTERS .................................................................. 151

12 TROUBLESHOOTING SPOTLIGHT ................................................................ 152
12.1 NO REPOSITORY DETECTED ............................................................................ 152 12.2 THE MAPS IN YOUR REPORT ARE EMPTY .............................................................. 152

13 APPENDIX A: CELL SITE PARAMETERS ........................................................ 153
13.1 CDMA CELL SITE PARAMETERS ...................................................................... 153 13.2 GSM / GPRS / EDGE CELL SITE PARAMETERS ................................................... 154 13.3 LTE CELL SITE PARAMETERS ......................................................................... 155 13.4 UMTS / HSPA+ CELL SITE PARAMETERS .......................................................... 156

14 APPENDIX B: SPOTLIGHT REPORTS ............................................................ 158
14.1 CDMA SPOTLIGHT REPORT ........................................................................... 158 14.2 EVDO SPOTLIGHT REPORT ........................................................................... 161 14.3 EVDO REV A SPOTLIGHT REPORT ................................................................... 165 14.4 GSM SPOTLIGHT REPORT ............................................................................. 170 14.5 HSPA SPOTLIGHT REPORT ............................................................................ 175 14.6 UMTS SPOTLIGHT REPORT ........................................................................... 180

15 APPENDIX C: CDMA THRESHOLDS, KPIS AND DIAGNOSES ............................... 185
15.1 CDMA THRESHOLDS ................................................................................... 185 15.2 CDMA EVENTS IN THE EVENT EXPLORER ............................................................ 188 15.3 DROPPED CALL DIAGNOSIS FOR CDMA ............................................................. 189

16 APPENDIX D: DATA SERVICE ANALYSIS THRESHOLDS ...................................... 191
16.1 DSA THRESHOLDS...................................................................................... 191

17 APPENDIX E: EGPRS KPIS AND DIAGNOSES ................................................ 194
17.1 EGPRS THRESHOLDS .................................................................................. 194 17.2 EGPRS EVENTS IN THE EVENT EXPLORER........................................................... 196 17.3 EGPRS DIAGNOSES .................................................................................... 198

18 APPENDIX F: EVDO KPIS AND DIAGNOSES .................................................. 200
18.1 EVDO THRESHOLDS ................................................................................... 200 18.2 EVDO EVENTS IN THE EVENT EXPLORER ............................................................ 204 18.3 DROPPED CONNECTION DIAGNOSIS FOR EVDO .................................................... 205
www.actix.com

18.4 LOW THROUGHPUT DIAGNOSIS FOR EVDO ......................................................... 207 18.5 SCHEDULING ISSUES DIAGNOSIS FOR EVDO ...................................................... 209

19 APPENDIX G: GSM THRESHOLDS, KPIS AND DIAGNOSES ................................. 211
19.1 GSM THRESHOLDS ..................................................................................... 211 19.2 GSM EVENTS IN THE EVENT EXPLORER.............................................................. 215 19.3 CALL SETUP FAILURE DIAGNOSIS FOR GSM ........................................................ 216 19.4 LOCATION UPDATE FAILURE DIAGNOSIS FOR GSM ................................................ 218 19.5 DROPPED CALLS DIAGNOSIS FOR GSM.............................................................. 220 19.6 HANDOVER FAILURE DIAGNOSIS FOR GSM ......................................................... 221

20 APPENDIX H: HSPA THRESHOLDS, KPIS AND DIAGNOSES ................................ 222
20.1 HSPA EVENT EXPLORER ANALYSIS ................................................................... 222 20.2 HSPA CALL DROP ANALYSIS EXAMPLE .............................................................. 222 20.3 HSDPA LOW THROUGHPUT EXAMPLE ................................................................ 225 20.4 HSPA EVENTS IN THE EVENT EXPLORER ............................................................ 229 20.5 HSPA THROUGHPUT KPIS ............................................................................ 233 20.6 HSDPA THRESHOLDS .................................................................................. 235

21 APPENDIX I: LTE THRESHOLDS, KPIS AND DIAGNOSES .................................... 239
21.1 LTE THRESHOLDS ...................................................................................... 239 21.2 LTE_CT THRESHOLDS ................................................................................. 243 21.3 SPOTLIGHT THRESHOLDS .............................................................................. 247 21.4 LTE EVENTS IN THE EVENT EXPLORER ............................................................... 247 21.5 RRC DROP DIAGNOSIS FOR LTE ..................................................................... 248 21.6 LTE IRAT MISSING NEIGHBOR ANALYSIS .......................................................... 250

22 APPENDIX J: UMTS THRESHOLDS, KPIS AND DIAGNOSES................................. 252
22.1 UMTS THRESHOLDS ................................................................................... 252 22.2 UMTS EVENTS IN THE EVENT EXPLORER ............................................................ 256 22.3 DROPPED CALLS DIAGNOSIS FOR UMTS ............................................................ 258 22.4 CALL SETUP FAILURE DIAGNOSIS FOR UMTS ...................................................... 260 22.5 EXCESSIVE CALL DIAGNOSIS FOR UMTS............................................................ 262

23 APPENDIX L: INFORMATION FOR ADMINISTRATORS ......................................... 263
23.1 HIDING ANALYZER EVENT DIAGRAMS FROM SPOTLIGHT USERS .................................. 263

24 INDEX .............................................................................................. 264

www.actix.com

1. dropped calls.1.3 Reporting Spotlight displays the results of its automatically generated analyses on integrated.1. Prioritizes which cells in the network are strong candidates for tilts and coverage optimization. for optimization engineers.actix. Neighbor List Analyses – this grooms 3G-3G and 3G-2G neighbor lists. coverage and interference identification.2 Event-based troubleshooting Based on the drive test data provided for the analysis. 1.1 Radio Network Analyses Spotlight provides the following analyses for examining the performance of the radio network:     Coverage and Overspill Analysis – this determines the coverage footprint of cells and identifies overshoot against coverage design boundaries. professional-quality reports including embedded maps. based on scanner data for sites positioned within a user-defined radius. costly. provides automated root-cause troubleshooting. www.com . Designed by optimization engineers. and concise reporting. 1.1. Grade of Service – this determines the relative grade of service for cells. Pilot Pollution – this automatically identifies inbound vs. Engineers can solve and report on more problems faster by eliminating time consuming data manipulation and manual deduction.Actix Spotlight Desktop User Guide November 2012 6 1 About Spotlight Today’s performance optimization and troubleshooting processes are typically inefficient. based on user-defined thresholds. Engineering teams commonly use disparate tools that are poorly integrated lacking the automation and scalability fundamental for rolling out and maintaining complex wireless networks. outbound pilot pollution. and error prone. Spotlight identifies key performance indicators. Actix Spotlight lowers the overall cost of performance optimization by delivering maximum engineering productivity in a managed workflow. Spotlight automatically generates root-cause diagnostics for the most common subscriber problems—for example.

2.  Using Spotlight reports (see page 38) www. you can follow them up by using the Radio Network Explorer or Event Explorer investigation pages. which might indicate the presence of one or more problems. links to these are shown as Critical Issues (6) in the Issues panel.1 Perform a quick overview of network performance Examine the available Spotlight report(s) to see whether any of the performance criteria thresholds have been exceeded. 5 3 6 2 1 4 Some typical scenarios for using Spotlight are outlined below: 1. These might then point you at specific problem events which you can examine and diagnose using the Event Explorer (5). missing neighbors and pilot pollution problems can be investigated from the Radio Network Explorer analyses (3).actix. Examine the summary map (1) and then the appropriate report for the loaded data (2). However. Cell coverage. If there are any problems. a typical general analysis of the data in Spotlight would be to start from the Summary Dashboard (shown below).2 Using Spotlight to solve network problems Spotlight is designed to allow you to follow your own investigations throughout the various analysis pages and reports. links to these are also shown as Important Issues (4) in the Issues panel of the Summary Dashboard.com .Actix Spotlight Desktop User Guide November 2012 7 1.

2.com . and throughout the life of the network as changes to traffic and tilt affect the coverage pattern and interference interaction between the cells. or open the Event Explorer.3 Determine cell coverage Use the Cell Coverage analyses in the Radio Network Explorer. www. or open the Event Explorer (p113). This process should be performed as part of the rollout phase of a network to construct and optimize the adjacency lists of each cell. Now select the Drilldown option (see p116).2.7 Investigate problems in detail at the message level Select a Critical Issue from the Summary Dashboard. 1. determine the relative degree of pollution for each cell and prioritize which cells in the network are strong candidates for downtilts and coverage optimization. 1.     CDMA/EVDO Cell Coverage (see p42) GSM Cell Coverage (see p63) LTE Cell Coverage (see p79) UMTS/HSPA Cell Coverage (see p99) 1.actix.2. outbound pilot pollution Use the Pilot Pollution analyses in the Radio Network Explorer.6 Investigate failure events Select a Critical Issue from the Summary Dashboard (p40).     CDMA/EVDO Neighbor List (see p48) GSM 2G Missing Neighbors (see p73) UMTS/HSPA 3G Neighbor List (see p79) UMTS/HSPA 3G-2G Neighbor List (see p93) 1.Actix Spotlight Desktop User Guide November 2012 8 1.4 Identify inbound vs.5 Identify sites failing their recommended design targets Use the EVDO System Performance analysis in the Radio Network Explorer (see p58). You can visualize the offending sectors on the map.2.2.2 Optimize neighbor lists and export suggested changes to the OMC Use the Neighbor List analyses in the Radio Network Explorer.   CDMA/EVDO Pilot Pollution (see p54) UMTS/HSPA Cell Pilot Pollution (see p106) 1.2.

etc. charts. The term KPI (key performance indicator) means not simply a statistic that reflects network performance in some way.3 About Spotlight projects In Spotlight. and include automated root cause diagnosis and drilldown to the sequential message data at the click of a button. call setup or location update failures. For all of the KPIs that represent an issue. depending on the KPI type:  Event KPIs . However. and so on. such as coverage. and maps that can be saved as an Excel workbook or Web page. This defines the extent of the data from the drive test files that you want to process and store within Spotlight's database. pilot pollution. Radio Network KPIs . missing neighbors. For these KPIs. a project is a collection of saved application settings and data files relating to a particular drive test initiative. some of these KPIs relate to general events (such as call attempts) in order to provide context for the failure events and these do not include diagnostics and drilldown functionality. www. an overall summary is shown in the Spotlight Summary Dashboard side panel.  Reports provide summaries. Preferences that determine how the data is to be loaded. Network information that you want to use (the cellrefs file).Actix Spotlight Desktop User Guide November 2012 9 1. such as dropped calls or handover.Most of these KPIs relate to a specific type of call or session failure event. but also a related pre-defined analysis. and defines which KPIs and reports will be used in the project.com . Thresholds that trigger particular conditions or Events in Spotlight's analyses. tables. the analysis is provided in either the Event Explorer or the Radio Network Explorer. specifically the:      Template used for the project.These KPIs relate to general issues for the radio network. However.actix. the Radio Network Explorer provides a detailed analysis that is very specific to the particular issue. Drive test files that you want to examine.

txt. Analyzer will be able to import the data. Numeric identifier for the Site. Network Explorer also lets you browse and edit this network information once it has been loaded into Analyzer. To maximize the benefit Analyzer can bring to network analysis. CDMA network data is used as an example. Locates Site icons on map. with one row for each individual sector in a network. but the appendices show important information relating to other network technologies. A blank file. As long as the data is in a tabular format. containing only Analyzer header information. CDMA Cell Site Parameters for Import: Parameter Site Name Site Number Latitude Longitude Sector Number Analyzer Group CDMA_Site CDMA_Site CDMA_Site CDMA_Site CDMA_Cell Analyzer Name SiteName SiteID Latitude Longitude Sector ID Purpose Text description of the Site for display on map.1 Obtaining Site Data in Tabular Format In order to import cell site data from your own network.1. All other parameters are optional.com .Actix Spotlight Desktop User Guide November 2012 10 2 Importing Cell Site Data 2. The data may come from a network database or a planning tool configuration file. A full list of network parameters for different technologies is given in Appendix A: Cell Site Parameters. Analyzer’s network data import process requires two files:   A delimited text file that contains unformatted data arranged in tabular form. creating a cell plan file called cellrefs. the parameters listed in bold in the table on the following page are required for cell data to function with logged data in the main workspace. Sector-specific information useful for display on maps (can be alpha or numeric) Orients the sector icons on the map.actix. using various Analyzer features. Locates Site icons on map. 2. Azimuth CDMA_Cell Azimuth www. to be populated with formatted data.1 Importing Network Data This chapter describes how to import delimited network element data into Spotlight. In this chapter. Analyzer’s Network Explorer feature allows you to import network element data. with one row for each sector. you will need to obtain a delimited text file containing the data listed in the table below.

Base station power. For information only.Actix Spotlight Desktop User Guide November 2012 11 Parameter Beamwidth Analyzer Group CDMA_Cell Analyzer Name Beamwidth Purpose Governs the shape of the sector ‘wedge’ icon to reflect the beamwidth of antenna deployed at the site. Used in CDMA Toolkit calculations to compare current search window settings with those suggested by Analyzer. Use to color sectors on the map by a custom integer field. For information only. Used in CDMA Toolkit calculations to compare current search window settings with those suggested by Analyzer. Used in CDMA Toolkit calculations. For information only. For information only. For information only. lines to neighbor cells and to color sector/site icons on maps to reflect PN planning. Used in CDMA Toolkit calculations to compare current neighbor list settings to those suggested by Analyzer. PN Offset CDMA_Cell PN Base Station Power Mobile Country Code System Identity Network Identity Broadcast Identity PctPilot PctTraffic PctPaging PctSync Active Set Search Window Setting CDMA_Cell CDMA_Cell CDMA_Cell CDMA_Cell CDMA_Cell CDMA_Cell CDMA_Cell CDMA_Cell CDMA_Cell CDMA_Cell EIRP MCC SID NID BID PctPilot PctTraffic PctPaging PctSync SRCH_WIN_A Neighbor Set Search Window Setting CDMA_Cell SRCH_WIN_N List of neighbors CDMA_Cell CDMANeighborList Sector Display – Wildcard Sector Display – Wildcard Sector Display – Wildcard CDMA_Cell CDMA_Cell CDMA_Cell Face_Display Azimuth_Display Phase_Display www.actix.com . Use to color sectors on the map by a custom integer field. Use to color sectors on the map by a custom integer field. For information only. For information only. For information only. used in CDMA Toolkit calculations.

Site Names do not need to be unique – they are just used for labeling purposes. as should latitudes with a 'South' notation. the figure shows all of the REQUIRED fields.1.Actix Spotlight Desktop User Guide November 2012 12 Parameter Layer Type Analyzer Group CDMA_Cell Analyzer Name LayerType Purpose Use this field to manage multiple cell layers to be displayed and hidden separately. www. Beware of non-unique Site IDs – that is.actix. Though the columns can be in any order for import into Analyzer. Additionally. 2. but to get the best results. the Excel spreadsheet must be saved as a TEXT file for import into Analyzer.2 Guidelines for Formatting Tabular Data Analyzer does not need the cell site data fields to be listed in a particular order. Position information must be accurate for Analyzer to correctly display sites in the right location on the map. follow these guidelines:  The Site ID field must contain a unique value for each site location. The figure below is an example of a delimited CDMA file that could be used to import a site list into Analyzer. entries that have multiple sets of latitudes and longitudes for the same Site ID. Longitudes that have a 'West' notation should be represented as a negative decimal value. Duplicated Site IDs will result in site markers appearing on the map without sector wedges. Sites will appear skewed on the map if the latitude and longitude fields are transposed.com  .

select Cells > Network Explorer. www. The following example is for CDMA technology.txt located in the directory called: C:\Program Files\Actix\Analyzer\Bin\Cellrefs  The file to be populated need not be named “cellrefs.Actix Spotlight Desktop User Guide November 2012 13   Before importing new cells into Analyzer. but the method works across all network technologies.1. 2.3 Importing the Data Once you have obtained your cell site database in delimited format and pointed Analyzer to a valid cellrefs file. To point the Analyzer to the file you wish to populate with the new cell site data. A valid cell site database is a text file in which the first line contains the text below: . you are ready to open the Network Explorer and import the site information.com .actix. 1 To access the Network Explorer. See Appendix A: Cell Site Parameters for more information on other technologies. Rename this file with a meaningful name in order to prevent the file from being overwritten during reinstallation. #NetworkData – datafile  Every Analyzer installation comes with a clean file called cellrefs. ensure that Analyzer is pointing to a valid cell site database.txt”. See the section on Loading Cell Site Data later in this document for more details. use the File Location line in the Tools > Preferences dialog.

actix.Actix Spotlight Desktop User Guide November 2012 14 The Network Explorer display consists of two panels. 5 6 7 Give the Template a meaningful Template Name. In most cases. The right panel shows details about relevant parameters for the current selection. Adjust these settings if necessary. the default information under the General Settings and Coordinate Information headers will apply.com 8 . you will not see any cell site data at this time. www. If you have pointed Analyzer to a cellrefs file containing only header information. The left panel contains a tree view of the network element data. Check the appropriate Delimiter. select Import > Import From New Template to open the Import dialog. Click Open to display the Import Settings dialog. Click Next. 2 3 4 From the toolbar. Select the appropriate network data file.

Required Required www. Click in the Column field next to the Site_Name parameter.com .Actix Spotlight Desktop User Guide November 2012 15 9 Expand the CDMA_Site data node. based on the table below (See Appendix A: Cell Site Parameters for more information on other technologies): Field Site_Name SiteID Latitude Longitude Mapping required for proper operation? Optional. but this field is frequently used for the site label. and this field must be unique for each site in the database. Repeat for each of the required fields in the CDMA_Site data node. Select the parameter name from your site database that corresponds to the Site_Name parameter.actix. Required.

Select the parameter name from your site database that corresponds to the Sector_ID parameter. based on the table below (See Appendix A: Cell Site Parameters for more information on other technologies): Field Sector_ID Required for proper operation? Required. Click in the Column field next to the Sector_ID parameter. 2 = blue. Required Required Optional Required Optional Optional Azimuth Beamwidth EIRP PN MCC SID www. Repeat for each of the required fields in the CDMA_Cell data node. This field can be used to color sectors on the map by face number (i.actix.Actix Spotlight Desktop User Guide November 2012 16 10 Expand the CDMA_Cell data node. 3 = green). 1 = red.e.com .

Actix Spotlight Desktop User Guide November 2012 17 Field NID BID PctPilot PctTraffic PctPaging PctSync SRCH_WIN_A SRCH_WIN_N CDMANeighborList Face_Display Required for proper operation? Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional. An example of a custom field would be the phase of the site where: 1 = On Air 2 = Under Construction 3 = Planned for Next Year LayerType Optional.actix. but map this field to the integer azimuth field in order to color sectors on the map by azimuth range. Select Yes to overwrite existing data. The error log specifies the cause of each error encountered and can be found in: C:\Program Files\Actix\Analyzer\Bin\Cellrefs\ImportErrors. Drill into the CDMA Cell Elements folder and examine the values corresponding to each sector. If any errors occur during the import.log 12 Inspect the cell data in the Network Explorer by expanding the All_CDMA_Site_Elements folder in the left-hand pane of the Network Explorer. as well as a folder containing CDMA Cell Elements. 13 Double-click on any site name in the right hand pane. Use this field to manage multiple cell layers. If the current workspace contains existing site data. 11 Click Finish when all the columns have been assigned. select the Save button. but map this field to a custom integer field to color sectors on the map by that field. but map this field to a custom integer field to color sectors on the map by that field. a pop-up message will indicate that an error log has been created. Cells can be displayed or hidden on the map by layer. An example of a custom field would be the phase of the site where: 1 = On Air 2 = Under Construction 3 = Planned for Next Year Azimuth_Display Phase_Display Optional. Location and ID of the site will appear. Optional. Select No to append to existing data.com . you will be asked whether you want to remove existing data before importing new data. The Name. 14 To save the formatted site information. www.

this is probably due to nonunique Site IDs in the imported cell site data. www. 17 If cell icons do not appear on the map.actix. right click on the CDMA_Cell layer in the map legend at the left hand side of the map window. Sites can also appear skewed on the map if the latitude and longitude information has been transposed. Be sure to close the map with the “X” at the upper right hand corner to save all changes to the map view. If you see site markers appearing on the map without sector wedges.com . 16 After closing the Network Explorer.Actix Spotlight Desktop User Guide November 2012 18 15 Close the Network Explorer by clicking the “X” at the upper right hand corner. Select Zoom to Layer to zoom the map to the appropriate location. view a new map by selecting View > Display New Map.

and integrate cell site data with real-time measurements. if any changes to cell site data are made. Be sure to close the map with the “X” at the upper right hand corner to save all changes to the map view. In the new workspace. the cell sites are now visible. www. A message box will be displayed saying that the new cellrefs file takes effect when a new workspace is loaded. If cell icons do not appear on the map.) directly from the Network Explorer. on the File Location line. Follow these steps to point Analyzer to a formatted cell site file: 1 2 3 4 5 From the main menu. select Tools > Preferences. Click OK to close the message box. 6 By default. 2. Import the second technology and save that cellrefs file. choose File > New Workspace to create a new workspace. In Analyzer. Therefore. From the Main Menu. Select Zoom to Layer to zoom the map to the appropriate location. click View > Display New Map. Analyzer reads cell site data upon opening a new workspace. you must start a new workspace (or reopen Analyzer) in order for the changes to take effect. although this file can have any name. etc. In the Open dialog. the formatted cell site file is known as the ‘cellrefs’ file. In the Change Preferences dialog. Simply browse to find the site and sector of interest and double click on a single parameter to activate the text. Analyzer loads cells upon opening Analyzer or starting a new workspace. PNs. click on the name of the current cellrefs file. follow this procedure: 1 2 3 Import the first technology and save the cellrefs file. copy all of the second cellrefs file apart from the first line.4 Importing multiple technologies To import multiple technologies using the same cellrefs file. a formatted cell site database must exist that contains location and configuration data for each cell site.2 Updating Cell Site Data You can make minor cell plan changes (a few azimuths. The previous section explained how to create a cell site file from a spreadsheet containing network parameters.3 Loading Cell Site Data In order to display cell sites in Analyzer. navigate to the cellrefs file you would like to use and select Open.Actix Spotlight Desktop User Guide November 2012 19 2.com . Using a text editor such as Windows Notepad.1. and paste it in at the end of the first cellrefs file. You now have a cellrefs file that can import data for both technologies. Click OK to close the Preferences dialog. Be sure to save the modifications before exiting the Network Explorer! 2.actix. right click on the CDMA_Cell layer in the map legend at the left hand side of the map window.

You can leave the labels as they are. Select OK to exit the Label Properties dialog. Next. 5 6 7 If you wish to offset the label from the cell site symbol. or Beamwidth.4.4 Cell Site Display 2. If you wish to change the font of the labels.com . then cell labeling: 1 2 3 In the Layer Control dialog box. or turn them off entirely. there are two formats of labels from which to choose: ▫ ▫ The Site_Name (default) shows only the site name. site and cell labels will be displayed on the Analyzer map.actix. The site labels are displayed independently of cell labels. In Analyzer. Check each of the following options: ▫ ▫ ▫ 4 Show Allow overlapped text (recommended) Hide adjacent duplicate text (optional) In the Label Properties box. use the drop down Data Field menu to determine the label format to display.1 Displaying Site Labels By default. modify the way they are displayed. This allows you to display of Site Name or Site ID in addition to or instead of PN. Check each of the following options: ▫ ▫ ▫ Show Allow overlapped text (recommended) Hide adjacent duplicate text (optional) www. The MapInfo-style Label Properties box will appear. “sectors” are called “cells” based on the European terminology. select the cell layer (named CDMA_CellBeamwidth-PN) Under the Properties heading in the Layer Control dialog. use the Label Style button in the Properties dialog. The Site Labels have been formatted. press the Labels button The MapInfo-style Label Properties box will appear.Actix Spotlight Desktop User Guide November 2012 20 2. Currently. Azimuth. press the Labels button. use the options in the Position box in the Label Properties dialog. format the Cell Labels: 1 2 3 In the Layer Control dialog box. select the site layer (named CDMA_SiteSite_Name) Under the Properties heading in the Layer Control dialog. The following instructions specify first site labeling. The KeyField label shows only the site ID.

In the Series drop-down. Sector_ID.4. sectors are colored by PN on the map.2 Coloring Sectors on the Map By default. If you wish to change the font of the labels. displayed next to the sector. www. Click OK in the Label Properties dialog. All CDMA_Cell parameters are available as options for labeling. and then OK in the Layers dialog to apply the labels.Actix Spotlight Desktop User Guide November 2012 21 4 In the Label Properties box. to color sectors by face). If you wish to offset the label from the cell site symbol. To color the sectors according to a different field (i. The PN Label shows the PN for each sector.com . use the options in the Position box in the Label Properties dialog. choose CDMA_Cell.actix. or to make all sectors the same color: 1 2 Click the Cell Sites button at the top of the map.e. use the Label Style button in the Properties dialog. 5 6 7 2. use the drop down Data Field menu to determine the label format to display.

To make all sectors the same color. expand the CDMA_Cell parameter in the legend. www.e. Use the Layer Control dialog to adjust labeling as desired.e. To modify face colors. Site coloring will appear as specified.actix. MCC). The figure below shows sectors colored by Sector_ID and labeled with the PN. 4 5 Note that the sector need not be colored and labeled by the same parameter.com . 2 = yellow. 1 = red. Click OK to exit the Sites / Cell Properties dialog. To color sectors by face (i. specify an unused field (i.Actix Spotlight Desktop User Guide November 2012 22 3 Use the Cell Color drop-down choose how to color the field. 3 = blue) choose Sector_ID. Right-click on individual ranges and choose Selected Range’s Style to modify colors.

Ensure that CDMA is visible in the Technology drop-down. Click the Highlight All button to highlight all matching sectors on the map. From the main menu. select Cells > Search for Cells. To conduct a search: 1 2 3 Display site data of interest on the map.actix. select a row to highlight and center the corresponding sector on the map.Actix Spotlight Desktop User Guide November 2012 23 2. Edit and Delete buttons to modify search criteria. www.com .4. From the main menu. select Window > Tile Horizontally or Window > Tile Vertically to arrange the CellRefs Search dialog and the map in the workspace. Use the Add.3 Searching for Cells Search for Cells provides a mechanism for locating specific cell sites based on user-defined search criteria. Click the Search Now button to show in the Results window all matching cell sites from the current cellrefs file. 4 5 6 7 8 From the Results window.

Beamwidth and Sector ID can be obtained by running the mouse over a sector on the map.Actix Spotlight Desktop User Guide November 2012 24 2. select Window > Tile Horizontally or Window > Tile Vertically.com . www. Details about that sector or site will appear in the Display Cell Data window. From the main menu. To obtain more detailed information on each site or sector: 1 2 3 4 Display site data of interest on the map.actix.4. Click on a sector wedge or site dot on the map.4 Viewing Cell Site Information A cell’s Azimuth. From the main menu. select Cells > Display Cell Data.

See the relevant appendix for details. you set the appropriate technology thresholds to enable Spotlight to use your own criteria for identifying particular events and circumstances. www.actix.5 Setting Thresholds for Data Import Ensure that before entering Spotlight.Actix Spotlight Desktop User Guide November 2012 25 2.com .

www. In the example screenshot shown above.  Note that you can also choose to start in classic mode. without the Spotlight interface and analyses. note that you will be asked to confirm your choice. you will want to create a New Project. and directly investigate the data using Analyzer's rich tool set. if you have a combination of licensed products. select Spotlight from the Engineering Process dialog).actix. click the project's related Open button to proceed to the Summary Dashboard. If you want to Delete a listed project. click on Actix Software from the Windows Start menu (or. If you already have an existing project within Spotlight's database. This screen is now displayed:   If you have just started using Spotlight.Actix Spotlight Desktop User Guide November 2012 26 3 Starting Spotlight To start Spotlight.com . there are several existing projects.

 Either select a predefined Template from the scrolling list. highlight it in the scrolling list and click Delete Template. www. To delete a particular template.actix. A Master Template is available at the bottom of the list. or click on New Template to create your own.  Type in a unique Project Name. Note that templates that are shipped as standard with Spotlight may not be deleted.  Click Next to go on to the next step.Actix Spotlight Desktop User Guide November 2012 27 4 Creating a Project 4. Project templates define the extent of the data from the drive test files that you want to process and store within Spotlight's database under the project name. Templates shipped as standard with Spotlight are shown in blue and do not have creation dates associated with them.com .1 Step 1: Choose Name and Template This page is the first step in creating a new Spotlight project. with all KPIs and reports selected.

and location. in case the original cellrefs file is updated to reflect changes made to the network. There are also a number of neighbor list settings for CDMA and UMTS – these are used to fine-tune the algorithms used by the neighbor list analyses in the Radio Network Explorer. the project will no longer work.  Settings – Click this link to open the Preferences dialog box. If you want to analyze data from more than one technology. many of which configure the way various specific types of data are decoded.) of all of the cell sites and sectors that you want to analyze.Actix Spotlight Desktop User Guide November 2012 28 4. simply create a new project that references the new cellrefs file. This has many options. the cellrefs file must contain the information for all of those technologies. Spotlight is designed to be used for short-duration drive test campaigns. etc.2 Step 2: Set Preferences and Thresholds  In the second step in creating a new Spotlight project. The Spotlight project database relies on the associated cellrefs file remaining unchanged – if it is.  You can also use the settings and thresholds links to set various other options for your project.  CellRefs – Select a valid cellrefs file that contains the details (name. so this should not present a problem – and if you do need to use the new cellrefs data. Note A cellrefs file contains network configuration information in a delimited text format. www. you must specify a cellrefs file for your project.actix. ID. Note Spotlight always makes a local copy of the selected cellrefs file.com . and is usually created using the output from a planning tool.

although a few might be based on multiple event attributes (for example. The documentation provides a list of these thresholds for each technology. www. Thresholds are also used in the calculations that are subsequently performed on the data as it is retrieved from the repository prior to display in Spotlight. when incoming and outgoing call setup failures are stored in separate event attributes).com . This is useful when reading about event detection thresholds and helps you to look up the definition of those attributes in the Attribute Help system. Many of the analyses in the Radio Network Explorer are also based on event attributes. When an event detection algorithm involves a user-definable threshold. the UMTS pilot pollution analyses are based on the UuPilotPollution and Uu_Scan_PilotPollution event attributes. The documentation provides information about the names of the event attributes that underlie each KPI and analysis.  Thresholds – Click this link to open the Thresholds Editor. These KPIs are usually based on a single event attribute (for example. Thresholds are used in Spotlight in two main ways: ▫ Event detection – Most of the KPIs in the Event Explorer are ultimately based on event attributes that are detected by the Actix event detection mechanism as the data is loaded into the project's repository. which also provides information about which attributes are affected. you can configure the corresponding KPIs and analyses by changing those thresholds. ▫ KPI definitions – Thresholds are used in the queries that define the raw data that is to be stored in the repository and from which the various KPIs are derived. the GSM dropped call KPI is based on the EventCallDropped event attribute). where you can configure the user-defined thresholds that are used in Spotlight. make sure that you do not enable the Automatic Import options in the CellRefs group of Preferences.actix. For example. Note When you work in Spotlight.Actix Spotlight Desktop User Guide November 2012 29 Although you can change these settings using the Data Settings link in the Radio Network Explorer's top panel. The thresholds used in the event detection mechanisms for the various technologies are documented in detail in the Settings and Preferences section of the help. you should set them using the link on this page when you create the project.

Although changing these settings after you have started loading data into the project should not invalidate the results.  By saving and reloading the cellrefs file and other preferences and thresholds with the project. These saved settings are automatically reloaded whenever you subsequently open the project. the neighbor list settings will revert to those that were selected when you originally created the project.com .Actix Spotlight Desktop User Guide November 2012 30 4.  Click Next to go on to the next step. However. For example. Although changing most of the preferences and thresholds will not affect the data stored in your project's repository. www.2. you can change the neighbor list preferences using the Data Settings link in the Radio Network Explorer's neighbor list pages. the page will be updated to reflect the new settings. with a potential for confusing discrepancies between the two sets of results. You should therefore think through your requirements and set the settings and preferences accordingly before you start loading data. it will affect drilldown data and any data that you load into Analyzer Classic for detailed analysis. next time you reload the project. this is not recommended when using Spotlight. as explained earlier. As soon as you close the dialog box.) Changing other preferences and thresholds can result in subtle changes in how Spotlight decodes data.actix. Also.1 What happens to the project’s preferences and threshold settings After you click the last step’s Done button. defines events and determines what to store in the repository. This is done for several reasons:  Spotlight does not expect that the cellrefs file will change after you have started loading data—the addition of even a single cell sector in the cellrefs file can result in incorrect results within Spotlight (this is why Spotlight is not compatible with the Automatic Import option for cellrefs data. However. it does mean that any changes you subsequently make to the preferences and thresholds while working on the project will be lost next time you reload the project. Spotlight avoids these potential problems. Note Although you can change preferences and settings at any time using the Display Thresholds and Preferences options on the main Tools menu. the changes will be lost when you reload the project. because changing the CellRefs file can cause incorrect results and changing the other settings is potentially confusing. Spotlight automatically saves the preferences and thresholds that are currently selected (including a copy of the entire cellrefs file). it can lead to confusion and the potential for different definitions being used to generate the same event.

the file list is empty:  Choose the data files to be processed by Spotlight: If you have just a few files to process.actix. The template selected in step 1 defines the information that will be loaded into the project database and how it will be processed. click the Add Files button and select one or more files.Actix Spotlight Desktop User Guide November 2012 31 4. which will be added to the list of chosen files. Initially.com . check the Add all subfolders box. If you have a folder full of file to be processed into Spotlight.3 Step 3: Choose Data In the third step in creating a new Spotlight project. you must specify the data files that you want to examine. click the Add Folder button and select the folder. www. If underneath the selected folder there are subfolders that also contain required data files.

The entire process of loading data is dependent on the volume of data to be loaded into the project. You can also use the Remove All Files button if necessary. once the data has been loaded into the repository. you can remove a specific file by clicking the remove link at the end of the row. The project will be saved to this folder: \Documents and Settings\All Users\Application Data\Actix\Analyzer\Projects (depending on your current Windows user settings) For best use.com .actix.  Click Done to load the data and open the Summary Dashboard. it can be reattached very quickly. aim for at least 1GB of free disk space per project.Actix Spotlight Desktop User Guide November 2012 32 Once the list of chosen files has been populated. www. However. Spotlight supports a maximum populated data volume of about 3GB.

Note that due to the potential amount of information on display. a separate tab per device will appear in the dashboard. Spotlight is designed to be used at full application window size.actix.Actix Spotlight Desktop User Guide November 2012 33 5 Using the Summary Dashboard The Summary Dashboard shows an overview of the data loaded in the current Spotlight repository project. so you should keep your Spotlight application window maximized at all times. If you have configured multiple devices during the template configuration phase. www.com .

If you have configured regional filtering.actix.com . It also provides some useful functions from any stage of your analysis: If your current project uses Global Filters. note that you need to click the Add Filter link on the right to create the filter.Actix Spotlight Desktop User Guide November 2012 34 5. a related link appears in the navigation bar. www. the navigation bar allows you to move around in Spotlight. and allows you to filter by time (not shown above).1 Navigating around Spotlight At the top of the page. this dialog will also give you the option to filter by region. Click on the link to show a dialog similar to this: This dialog allows you to specify any files or streams that you want to exclude from the analysis. Once you have specified the filter.

The three tabs allow you to filter by File and Stream. The Log Files link displays a dialog listing the log files processed in the project.com . The Reports link in this table displays all the existing reports defined to run on the template. or by Stream.actix. The panel also includes a Summary table consisting of information on the loaded dataset.2 The Top Panel The top panel has buttons linking to the Event Explorer and Radio Network Explorer pages. The Analyzer Classic tab allows you to load selected files for analysis in Analyzer: www.Actix Spotlight Desktop User Guide November 2012 35 5.

com . The Critical Issues section includes event-based key performance indicators (KPIs) like dropped call rate.Actix Spotlight Desktop User Guide November 2012 36 5. The Important Issues section includes the various radio network analyses. Depending on the nature of the issue. click on one of these issues to open the appropriate analysis on either the Radio Network Explorer page or the Event Explorer page. www. failed call rate and rate of calls with excessive setup time. based on the current threshold settings.actix.3 The Issues Panel On the left of the screen. this panel highlights particular issues that have been identified in the loaded data. If you have access to multiple technologies in the loaded data. a drop-down menu at the top of the panel allows you to switch between the technologies.

com . Cell sector wedges are color-coded as follows: green sectors were serving during part of the drive yellow sectors were seen during the drive but were never serving empty sectors were not seen during the drive Note that this image shows the map window undocked. by default the map view is docked in Spotlight.4 The Map In Spotlight.actix. The Summary map shows the entire drive with the default (technology-dependent) attribute plotted:     CDMA EVDO GSM UMTS / HSPA EcIo_1stBest Consolidated_SINR_For_Nth_Best_Pilot[0] ServRxLevSub Uu_ActiveSet_EcNo[0] The drive test data is binned according to the selections made in step 4 of defining the project template. resulting in the Map icon being displayed next to the File menu at the top left of the screen. From this map.Actix Spotlight Desktop User Guide November 2012 37 5. www. so they may not necessarily align with the data points. using a Spotlight report or by following a link for a critical or important issue. the map is an integral part of the interface. However. you may be able to see one or more areas that may require investigation. Click on this icon to control the size of map window and its docked or undocked condition. any events displayed on the map will use the exact position rather than a binned position.

a report must have been activated in the current project's template.actix. Note that. to be available.Actix Spotlight Desktop User Guide November 2012 38 6 Using Spotlight reports Reports are a good place to start when attempting to identify problems in the loaded data. Spotlight provides the following reports:       CDMA (see p158) EVDO (see p161) EVDO Rev A (see p165) GSM (see p170) HSPA (see p175) UMTS (see p180) www. A report shows all unfiltered data in the project database for the associated technology. Here's an example HSPA report: Navigation tabs on the bottom left let you explore the various pages of the report.com . These can be accessed by clicking on the Reports link from Spotlight's Summary Dashboard page.

the map bitmaps will be updated to reflect the data in project B. because otherwise the report will be updated with the maps from project B.gif. Make sure you choose the Don't Update option. From here. Note that the maps are inserted into the Excel file as linked bitmaps. you can use the functionality of Excel to perform further analyses on the data. Note that the web page has an associated subfolder with a unique name containing various image and other files relating to that report. www.gif.com . Excel will display a message saying that the workbook contains links to other data sources and asking whether you want to update them. the image files in each subfolder are always called image1. which may cause you problems in some situations. The Save button exports the report as a web page. or simply save the report as an Excel file or print it out. This means that if you save the report in Excel for a project (A) and then run the report again on a different project (B). If you subsequently reopen the workbook that you saved for project A. image2.actix. the Show Excel Report button lets you open the report as a Microsoft Excel file. However.Actix Spotlight Desktop User Guide November 2012 39 On the bottom right.

.com .1 About the Radio Network Explorer You can access the Radio Network analyses from the Radio Network Explorer icon at the top of the Summary Dashboard page: .actix.or by clicking on an appropriate Issue link in the Issues panel on the left of the Summary Dashboard page: www.Actix Spotlight Desktop User Guide November 2012 40 7 Using the Radio Network Explorer 7..

taking you to the appropriate analysis. At the top left. you may find that several analysis conditions apply. you will see a tab for each of these.Actix Spotlight Desktop User Guide November 2012 41 The available Radio Network analyses for all technologies are as follows:             CDMA/EVDO Cell Coverage CDMA/EVDO Neighbor List CDMA/EVDO Pilot Pollution EVDO System Performance LTE Cell Coverage LTE 4G – 3G/2G Missing Neighbors GSM 2G Missing Neighbors GSM Cell Coverage UMTS/HSPA 3G Neighbor List UMTS/HSPA 3G-2G Neighbor List UMTS/HSPA Cell Coverage UMTS/HSPA Cell Pilot Pollution When you are viewing a particular Radio Explorer analysis page.actix.com . www. depending on the data loaded in the project.

7.Actix Spotlight Desktop User Guide November 2012 42 7.2 Using the cell coverage analysis 1 Click on an appropriate issue link (or on the Radio Network Explorer image followed by the Cell Coverage tab) to open the Cell Coverage analysis page. Visualize where a cell is the best server.actix.com .2.1 Before you start You can use scanner or handset data for this analysis. Visualize where cells are overshooting their coverage design boundary.2. shown by the red line surrounding a selected cell.2 CDMA / EVDO Cell Coverage analysis You can use this analysis to:     Determine the coverage footprint for each cell. Determine the relative grade of service as regards to EcIo. www. 7. based on user-defined thresholds. Mobile Rx Power and Mobile TX Power for selected cell(s). as defined by SL_Overspill_Dist_Threshold.

Here is one such site . click on the column heading # > Dist. 2 3 From the top table.com . to sort the table by this value. any events displayed on the map (for example. Some samples (highlighted) are shown well outside the overspill threshold (the red circle around the selected cell) and close to another cell. Look for differences between the # > Dist. by using the Events drop-down menu) will use the exact position rather than a binned position. below 50) as these will not be statistically relevant. www. value and # Samples. Be careful not to include sectors with low sample counts (for example.Actix Spotlight Desktop User Guide November 2012 43 Note that drive test data is binned according to the selections made in step 4 of defining the project template. However. Sector 3.Site A. so events might not align with the data points.actix.

scanner data is available.Actix Spotlight Desktop User Guide November 2012 44 4 In this example. Note that as the samples are now no longer seen.com .actix. so select the Analysis to be Scanner . this is not a problem. www.Where Seen to visualize the coverage situation for the loaded data.

There may be a problem with the highlighted neighboring sector. which could be solved by downtilting the selected sector. www.Actix Spotlight Desktop User Guide November 2012 45 Continuing to investigate the sectors from the top table.actix. check that the two cells are twoway neighbors. First. we find another potential problem sector. Site B Sector 2.com .

3 Features of this analysis page   Top Panel . as defined by SL_Overspill_Dist_Threshold. So while looking at pilot pollution you could dump the CDMA Dropped Call event on the map and quickly find out if the call dropped due to pilot pollution.When no rows are selected. Currently plotted events are shown in red in the list.Shows summary information. A red line indicates the maximum range for the analysis. configured using SL_Overspill_Dist_Threshold. Attributes – List of most commonly used attributes that can be plotted on the map. When a site is selected. EcIo and the CDMA_Important_Issues (CDMA Grade of Service) attribute. The currently selected attributes will be kept as you move between Spotlight's analysis pages.Actix Spotlight Desktop User Guide November 2012 46 7. Analysis – Select Scanner (Best Server/Where Seen) or Handset (Best Server/Where Seen) analysis. the side panel displays overview information. plus Grade of Service percentages for the entire drive. The red circle represents the coverage design boundary. Side Panel . and CDMA Grade of Service. and shows the coverage footprint for only those cells that were the best servers at some point in the drive. The map also shows the Grade of Service (the legend also shows sample counts). Select a PN to color red all the sites with this PN.actix. Overview – Displays in the left panel an overview of statistics. Data points outside this circle represent overspill.2. The analysis can operate in two modes: Best Server and Where Seen. Clicking on a row in this table causes the side panel to display more information about the site.        www. the map shows the coverage wedge for the selected cell. PN Search – Visualize a PN on the map. so you can quickly identify co-PN locations. Best Server mode shows the Ec/Io when the selected cell was the best server is displayed. and the map zooms to the site and displays its coverage. Where Seen mode shows the Ec/Io whenever the cell was measured.When you click a row in the top table or on a site on the map. Rx Power. A table shows details of the sites: Best EcIo. Currently plotted attributes are shown in red in the list. Map .com . Events – List of the event attributes that can be plotted on the map. Filters – Select this link to specify filters for the table on the top panel. the panel shows various KPI values for the site and a histogram of the distances at which the cell was measured. Changing the mode affects the Ec/Io attribute that is displayed on the map.

Values should vary between -16 and -12 dB. Values should vary between 0 and 10 dBm. failed call and voice call with poor quality.This condition is used in conjunction with EcIo and Mobile Rx Power Thresholds to determine the diagnosis for the dropped call. Recommended value is -12 dB. Recommended value is -80 dBm. failed call and voice call with poor quality.actix.Actix Spotlight Desktop User Guide November 2012 47 This table shows how the CDMA Grade of Service is computed at each point: CDMA Grade of Service Excess interference External interference Weak reverse link Weak forward link Low Rx signal Poor coverage *Conditions: EcIo condition* Within Within Exceed Within Exceed Within MRx Power condition* Exceed Exceed Exceed Within Within Within MTX Power condition* Within Exceed Exceed Within Exceed Exceed  EcIo compared with CDMA_EcIoCombinedThreshold . Values should vary between -75 and -90 dBm. Mobile Rx Power compared with CDMA_MobileRxPowerThreshold .This condition is used in conjunction with Mobile Rx Power and Mobile Tx Power Thresholds to determine the diagnosis for the dropped call. Recommended value is 5 dBm. Mobile Tx Power compared with CDMA_MobileTxPowerThreshold . failed call and voice call with poor quality.com .   www.This condition is used in conjunction with EcIo and Mobile Tx Power Thresholds to determine the diagnosis for the dropped call.

check the data settings that control the neighbor list analysis algorithm. You can now see the sector with the highest number of recommended additions to its neighbor list.1 Before you start For this analysis.3.3 CDMA / EVDO Neighbor List analysis This lets you use scanner data to optimize neighbor lists for sites within a userdefined radius of the selected cell. 2 3 Go to the top table and sort by the Add column. and these can be exported directly to a CSV file for easy import and to update the switch directly. the project will need to contain scanner data.3. 7.Actix Spotlight Desktop User Guide November 2012 48 7. The missing neighbor algorithm generates add. remove and retain neighbor recommendations for each site and cell based on scanner measurements. or click on an appropriate Issue in the left-hand Issues panel. www.actix. from the Summary Dashboard page click on the Radio Network Explorer button and click on this tab.2 Using the neighbor list analysis 1 To start this analysis. 7.com . If you have not done so before.

you may think that the number of samples was too small to justify the addition . You may have reasons for refusing to accept the suggestion on geographical grounds (for example. If you disagree with a suggested addition. by using the Events drop-down menu) will use the exact position rather than a binned position. you may want to use the PN Search feature to find an alternative sector to add to the neighbor list. The map also displays the data points used in the analysis. However.actix.com . existing cells between the sector and the suggested addition. any events displayed on the map (for example. you may know that one or more sites will be going off-air and should not be selected. or for reasons related to the data settings. For example. www.in which case you may also want to alter the related data setting. and will need to make the correction to the switch manually (for example. Note that drive test data is binned according to the selections made in step 4 of defining the project template. The map now shows green lines to each new neighbor recommendation. which will immediately update the analysis. Also. so events might not align with the data points. The thickness of each line shows how well the suggestion meets the criteria of the analysis.Actix Spotlight Desktop User Guide November 2012 49 4 Click on the top row in the table to show information for that sector. Note that in this case you will not be able to output your choice. as occurs several times in this example). by editing the CSV file). 5 Examine each suggested additional neighbor. The circle represents the user-defined radius used by the analysis to identify potential neighbors.

This can be useful if there are a large number of recommendations and you need to keep track of how many you have already selected. as necessary.actix. So if you selected 3 additions. the number would read 6/6. Note that the number beside the button changes to match your selection. click the Export data link. For example. Note that by default the map does not show lines for removal recommendations. Once you are satisfied with the recommendations that you have selected. if there were 6 suggested additions in the first row. you can use the table in the side panel on the left. From the top of the page. this would result in the number reading 3/6. If you clicked the button. 7 8 Repeat this process for each row in the top table. which shows each recommendation for a sector individually. 9 www.com . with none currently selected for export. the number would show 0/6.Actix Spotlight Desktop User Guide November 2012 50 6 If you accept all suggestions for a sector. you can output them to a CSV file. you can click the related button in the table to mark your choice. If you do not want to select every recommendation for a sector. You can now go through the same process for the 'Removals' column.

Actix Spotlight Desktop User Guide November 2012 51 7.4 Data Settings Setting Ec/Io Threshold (dB) Maximum Neighbors Addition Threshold (%) Default -17 Description Only scanner measurements above this used-defined EcIo threshold will be included in the analysis. Defines the percentage of samples that must be reached to trigger a cell being added as a suggested neighbor. Side Panel . This helps in quickly identifying co-PN locations.actix. 13 1 www. This is used to reduce the effect of stray signals. which can be used to build lists of suggested neighbor cells to add and remove. Data Settings – This link opens up a dialog box for configuring the algorithm that Spotlight uses for the missing neighbor analysis. Clicking on a row in this table causes neighbor information for the selected cell to be displayed in the side panel. Defines the maximum number of cells in the neighbor list. Currently plotted events are shown in red in the list.3. Currently plotted attributes are shown in red in the list.com . Check boxes next to a recommendation can be selected for export to a CSV file. Map .Summary information is displayed in the top panel.3. lines to neighbors are drawn from that site. Export data – Select this link to export neighbor recommendations to a CSV file. All of the options take effect immediately after you click OK. See below for more information. PN Search – Visualize a PN on the map. Events – List of the event attributes that can be plotted on the map.3 Features of this analysis page  Top Panel . Input a PN to visualize on the map and this feature would color red all the sites with this PN. Attributes – List of most commonly used attributes that can be plotted on the map.Details of the neighbor recommendations are displayed on the side panel. It includes in a tabular form number of addition. The currently selected attributes will be kept as you move between Spotlight's analysis pages. Filters – Select this link to specify filters for the table on the top panel. and lines to neighbors to be drawn on the map. The circle represents the user defined radius (Maximum Intersite Distance) used by the analysis to identify potential neighbors.         7. removals and retains neighbor recommendations for every site.When a row is clicked in the top panel or a site is clicked on the map.

com . cells will be recommended for removal from the list. and are also within the Maximum Intersite Distance (the blue circle). for that cell to be considered for inclusion in the serving cell's neighbor list.2 Description Defines the minimum percentage of samples that cells in the current neighbor list must achieve in order to be recommended for retention in the list. set this value to 0. For rural areas where the average intersite distance is naturally greater than a dense urban environment. Minimum Measurements Maximum Intersite Distance (meters) 50 20000 Angle to site threshold (degrees) 90 In this example. use a higher value. When the percentages of samples fall below this threshold. To disable this feature. This threshold ensures that missing neighbors are not suggested from reflected signals or back-lobes. Only sectors which have been measured above the Ec/Io Threshold at least this many times will be included in the analysis. the beam width is shown as a darker blue arc. To disable this feature. set this value to 0. Defines the maximum angle between the edge of a cell's beam width and the data point.actix.Actix Spotlight Desktop User Guide November 2012 52 Setting Removal Threshold (%) Default 0. www. and also that only cells angled towards the data point are suggested. Acceptable data points are within this threshold of the candidate sector's beam width. Note that the algorithm works off Binned data. and the angle to site threshold in lighter blue arcs on either side. Defines the maximum line-of-sight distance in meters between two cells for one to be considered for inclusion on the other's neighbor list.

com . Selected 32 Once a potential neighbor list has been calculated for each data point. the longer it will take a handset to find appropriate neighbors. Select this option to analyze the neighbors of the best cell only. they are aggregated by serving cell to produce the recommended neighbor list. This is compared with the existing list to calculate which are additions.actix. Allows you to define the maximum number of recommended neighbors. De-select this option if you want to analyze the neighbor list of all of the cells within the reporting range. Note that the more potential neighbors you add. conceivably resulting in a dropped call.Actix Spotlight Desktop User Guide November 2012 53 Setting Include existing neighbors Only process first best PN Max Neighbor List Size Default Selected Description Select this option for the current neighbor list in the cellrefs file to be considered for additions and removals. retentions and removals. www.

so events might not align with the data points. www.Actix Spotlight Desktop User Guide November 2012 54 7.2 Using the pilot pollution analysis 1 To start this analysis.com . by using the Events drop-down menu) will use their exact position rather than a binned position. and view the offending sectors on the map.4. events plotted on the map (for example. from the Summary Dashboard. However. click on the Radio Network Explorer button and click on the Cell Pilot Pollution tab. click on an appropriate Issue in the left-hand Issues panel.1 Before you start You can use scanner or handset data for this analysis.4 CDMA / EVDO Pilot Pollution analysis This lets you quickly identify pilot pollution in the inbound (how the selected sector is being polluted by other sectors) and outbound (how the selected sector is polluting other sectors) directions. 7. 7.4. Alternatively. such as Too Many Servers (a pilot pollution issue). Note that drive test data is binned according to the selections made in step 4 of defining the project template. The map shows the drive test data and the Pilot Pollution events. You can determine the relative degree of pollution for each cell and prioritize which cells in the network are strong candidates for downtilts and coverage optimization.actix.

In this example.com . Inbound pilot pollution lines are drawn in blue. In this example that is CDMA_Site_41. www. which has 183 pilot pollution events. The arrow on each line points from the polluting sector to the polluted sector.Actix Spotlight Desktop User Guide November 2012 55 2 Sort the top table by Pilot Pollution Events and click on the top row (that is. The map now highlights the selected sector. the selected sector is polluting three other sectors. the sector with the most associated pilot pollution problems). The thickness of the lines indicates the degree to which pilot pollution was detected for the selected sector. based on the loaded data.actix. Outbound pollution lines are drawn in red from the selected sector to the sectors being polluted. Sector 3. The left hand panel displays details of the outbound pollution for the selected sector. Rolling over a line with the cursor shows a pop-up message box giving more information on the pollution.

www.Actix Spotlight Desktop User Guide November 2012 56 3 Now de-select the Outbound Pilot Pollution Total box to hide the outbound polluting lines and select the Inbound Pilot Pollution Total box. In this example. the selected sector is being polluted by five other sectors. The left hand panel displays details of the inbound pollution for the selected sector. Note that you can also sort this table . which helps you identify distant sectors that might need downtilting.actix.com .for example by distance. or if the serving cell needs uptilting for greater coverage.

When you click a row in the top table or on a site on the map. It includes in a tabular form the number of pilot pollution events for each site and the total number of inbound/outbound polluters.actix. Clicking on a row in this table displays pilot pollution information for the selected cell in the side panel.4. Currently plotted events are shown in red in the list.         www. Select one or more to plot on the map. lines to inbound as well as outbound pollution are drawn from that site. The lines to polluters have a direction arrow suggesting inbound or outbound pollution. The currently selected attributes will be kept as you move between Spotlight's analysis pages. Attributes – Lists the most commonly used attributes. All the pilot pollution events involving the site are also plotted on the map. Select one or more to plot on the map.com .3 Features of this analysis page  Top Panel . and draws lines to polluters on the map.Shows summary information. PN Search – Visualize a PN on the map. Analysis – Select Scanner or Handset analysis. Map . Currently plotted attributes are shown in red in the list.Actix Spotlight Desktop User Guide November 2012 57 7. Side Panel . So. Select a PN to color red all the sites with this PN so you can quickly identify co-PN locations.Shows details of the inbound and outbound pollution for the selected site. while looking at pilot pollution you could dump the CDMA Dropped Call / EVDO Dropped Connections event on the map and quickly find out if the connection was dropped due to pilot pollution. Overview – Click to display an overview of pilot pollution for the entire drive. Events – Lists event attributes. Click on a column title to sort the table by this value. Filters – Select this link to specify filters for the table on the top panel.

2 www. Click on the Radio Network Explorer icon and then the System Performance tab.5 EVDO System Performance analysis EVDO system coverage tests are intended to characterize network performance and coverage. Examine the report to obtain an overview of the system performance.1 Before you start For this analysis. select the EVDO Report. and verify that the system meets the following recommended performance criteria:    Signal to Interference & Noise Ratio (SINR) Packet Error Rate (PER) Mobile Tx Power     Mobile Rx Power RLP Rx Throughput RLP Tx Throughput DRC Rate 7. the project will need to contain handset data.actix. from the Summary Dashboard.Actix Spotlight Desktop User Guide November 2012 58 7.2 Using the system performance analysis 1 Before using this analysis.5.com . 7.5.

However. Note that drive test data is binned according to the selections made in step 4 of defining the project template. www. with 50 or more samples. by using the drop-down menu) will use the exact event position rather than a binned position. 5 Click on a row in the table to show various KPI values for the selected site and a distribution chart for the currently selected metric.actix.com . 3 4 Select from the Metrics drop-down menu the performance metric that you want to examine.for example. any Events displayed on the map (for example. Check the # Samples column to make sure that you are looking at data that is statistically significant . Click the column title # < Threshold to show the sectors with the highest number of samples that exceed the performance threshold.Actix Spotlight Desktop User Guide November 2012 59 The System Performance page provides information on whether a particular performance metric has been met for the various sectors shown in the top table. The Performance Met column shows whether the currently selected metric has been achieved or failed for each sector. so events might not align with the data points.

Side Panel . performance met/not met result etc. The currently selected attributes will be kept as you move between Spotlight's analysis pages.Shows summary information.com .3 Features of this analysis page  Top Panel .Actix Spotlight Desktop User Guide November 2012 60 6 Click on the sector icon next to the Performance Met column heading to show on the map those sectors that are not performing adequately.When you click a row in the top table or on a site on the map. A table shows information on individual sites. 7. overview information is displayed in the side panel and on the map.actix. Clicking on a row in this table causes the side panel to display more information about the site and a distribution chart for the metric. Attributes – List of most commonly used attributes that can be plotted on the map. total samples.5. Filters – Select this link to specify filters for the table on the top panel. the map shows the corresponding metric for the selected site.Displays various KPI values for the selected site and a distribution chart for the currently selected metric. including information such as the Average metric. When no rows are selected. You can select the metric on which to run the test from the Metrics drop-down menu. and by default the SINR analysis is presented. Map .     www. Currently plotted attributes are shown in red in the list.

if: (1 .% of High PER) > (EVDO_PER_Recommended_Performance_Threshold) % Mobile Rx Power Compares AGCPower_Received_Antenna0 with the userdefined Rx Power threshold EVDO_MobileRxPower_Threshold. High PER % = (Measurement bins with PER > Thresh) / (Total measurement bins) X 100 Performance criteria met.% of Low RX) > (EVDO_RXPWR_Recommended_Performance_Threshold) % Mobile Tx Power Compares TotalPower_Transmitted with the user-defined TX Pwr threshold EVDO_MobileTxPower_Threshold. if: ((1 . High TX Power % = (Meas Bins with TX Power > Thresh) / (Total measurement bins) X 100 Performance criteria met. You can easily switch between metrics. if: (1 . if: (1 . Metrics – Select the performance metric to be used for the analysis.4 Performance metrics Metric SINR Notes Compares Consolidated_SINR_For_Nth_Best_Pilot_0 with the user-defined SINR threshold Average_SINR_PN0_Threshold.% of Low SINR) > (EVDO_SINR_Recommended_Performance_Threshold) % PER Compares PER_Instantaneous with the user-defined PER threshold Average_PER_Threshold. to quickly identify Co-PN locations.Actix Spotlight Desktop User Guide November 2012 61     Events – List of the event attributes that can be plotted on the map. PN Search – Visualize a PN on the map. Low SINR % = (Measurement bins with SINR < Thresh) / (Total Measurement bins)) X 100 Performance criteria met.% of High TX) > (EVDO_TXPWR_Recommended_Performance_Threshold) % www. Specify a PN to color red all the sites with this PN. Low Rx Power % = (Meas Bins with Rx Power < Thresh) / (Total measurement bins) X 100 Performance criteria met.actix. 7.5. Currently plotted events are shown in red in the list. Overview – Click on this link to display an overview of system performance for the entire drive.com .

Actix Spotlight Desktop User Guide November 2012

62

Metric RLP Rx Throughput

Notes Compares EVDO_RLP_Rx_Throughput_Instantaneous with the user-defined RLP threshold Average_RxRlpThputInst_Threshold. Low RLP Rx Thpt % = (Meas Bins with RLP Rx Thpt < Thresh) / (Total measurement bins) X 100 Performance criteria met, if: (1 - % of Low RLP Rx) > (RLPRxThpt_Recommended_Performance_Threshold) %

RLP Tx Throughput

Compares EVDO_RLP_Tx_Throughput_Instantaneous with the user-defined RLP threshold Average_TxRlpThputInst_Threshold. Low RLP TX Thpt % = (Meas Bins with RLP TX Thpt < Thresh) / (Total measurement bins) X 100 Performance criteria met, if: (1 - % of Low RLP TX) > (RLPTxThpt_Recommended_Performance_Threshold) %

DRC Rate

Compares DataRate_Requested_ShortTermAverage_Kbps with the user-defined DRC Rate threshold EVDO_DRC_Rate_Requested_Threshold. Low DRC % = (Bins with DRC < Thresh) / (Total measurement bins) X 100 Performance criteria met, if: (1 - % of Low DRC) > (EVDO_DRC_Recommended_Performance_Threshold) %

www.actix.com

Actix Spotlight Desktop User Guide November 2012

63

7.6 GSM Cell Coverage analysis
You can use this analysis to:

    

Determine the coverage footprint for each cell. Visualize where a cell is the best server. Determine the relative grade of service as regards to EcIo, Mobile Rx Power and Mobile TX Power for selected cell(s), based on a user-defined threshold. Visualize where cells are overshooting their coverage design boundary as defined by SL_Overspill_Dist_Threshold (drawn as a red circle on the map). Visualize the neighbor BCCH, TCH and BSIC plans, within the range G_Interference_Radius (drawn as a dotted blue circle on the map).

7.6.1 Before you start
You can use scanner or handset data for this analysis.

7.6.2 Example of No Dominance
The Summary Dashboard shows an Important Issue: '% area with No Serving Cell Dominance'. See Coverage criteria to see how this was derived.

1 2

From the Summary Dashboard, click on an appropriate 'issue' link to open the Cell Coverage analysis page, for example the issue shown above. Note that several rows in the top table have a low sample count, '#', and so are unreliable to use in this investigation.

www.actix.com

Actix Spotlight Desktop User Guide November 2012

64

3

To remove rows with low sample counts, apply a Filter with a threshold of, say, 50 counts. Click Add Filter and OK.

4

From the Attribute drop-down menu, select an attribute to plot on the map, base on the related Important Issue from the Summary Dashboard (for this example, No Serving Cell Dominance): Attribute ServRxQualSub ServRxLevSub NumNeighbors within 5 dB

Important Issue Poor Voice Quality Poor Signal Strength No Serving Cell Dominance

The attribute is used in the calculation to identify the issue, as explained in Coverage criteria. Note that drive test data is binned according to the selections made in step 4 of defining the project template. However, any events displayed on the map (for example, by using the Events drop-down menu) will use the exact position rather than a binned position, so events might not align with the data points.

www.actix.com

Actix Spotlight Desktop User Guide November 2012

65

5

Examine the top table of the analysis for indications of poorly performing cells relating to the Important Issue, and select likely candidate rows. In the example below, a problem row has been selected. The first map image shows the 'NumNeighbors within 5 dB' attribute plotted, which highlights an area of poor dominance (drawn in red). The second map image shows RxLev (Where Seen) plotted for the same sector, which shows that it covers an unnecessarily large area. This could be corrected by applying some downtilt to the sector.

www.actix.com

Actix Spotlight Desktop User Guide November 2012

66

7.6.3 Example of GSM visualization
This analysis can also be used to highlight and investigate interference issues, based on the information held in the cellrefs file. In this example, the Quality tab of the side panel shows a high percentage of Poor RxQual at the same time as Good RxLev, which is usually an indicator of interference. 1 2 Use the top table to locate and select cells exhibiting this combination of poor RxQual and good RxLev. Now from the side panel, select the Visualization tab.

Depending on the information available, up to four radio buttons are displayed at the top of the panel with which you can pick the required type of cell plan visualization. If you have interference, you may need to see if there are any cells in the area that have the same frequencies. On the map you can see the selected sector in gray, together with colored co-channel, adjacent lower and adjacent higher interference sectors. The cell coverage radius is shown as a red circle, and the cell plan visualization radius is shown as a dotted blue circle. If TCH information is present in the cellrefs file, radio buttons will be displayed for the two TCH display options, and TCHList information will appear in the pop-up sector information.

www.actix.com

The Where Seen mode shows RxLev whenever the cell was measured.Shows a table of summary information. Filters – Select this link to specify filters for the table on the top panel. Input a SC to visualize on the map and this feature would color red all the sites with this SC. the map shows the coverage wedge for the selected cell.4 Features of this analysis page  Map . Note that clicking on the icon only displays the Average value. (Average. if the difference is greater the 8 dB. RxLev.com . This quickly identifies co-SC locations. % > Beam – Percentage of points outside the cell beamwidth.Number of samples greater than the coverage design boundary (defined by SL_Overspill_Dist_Threshold).6.) . Best Server mode shows the Ec/Io attribute when the selected cell was the best server (and also RxQual). Ensure that the site you are looking at has a statistically viable number of samples. % >180 Beam – Percentage of points outside a hypothetical beamwidth of 180 degrees. Events – Lists the event attributes that can be plotted on the map. EcIo & RSCP.Number of samples. Link Diff – This is the difference between UL and DL pathloss and is used to highlight cell with possible LNA (TMA) issues.BTS Sensitivity + BTS Antenna Gain DL = BTS EIRP . Top Panel . RxQual.actix. Analysis – The page can operate in two analysis modes: Best Server and Where Seen. > D(ist. Attributes – Lists the most commonly used attributes that can be plotted on the map.When you click a row in the top table or on a site on the map.RxLevSub www. coverage footprints can only be seen for those cells that were best servers at least once during the drive. Min). Clicking on a row in this table causes the side panel to display more information about the site and the map zooms to the site and displays its coverage. SC Search – Visualize a SC on the map. The currently selected attributes will be kept as you move between Spotlight's analysis pages. The table containing the following information: ▫ Handset (Where Seen / Best Server)       BCCH # . Currently plotted events are shown in red in the list. The red circle represents the user-configured coverage design boundary. Currently plotted attributes are shown in red in the list. where: UL = UE Tx Power . and data points outside this circle represent overspill. Max.Actix Spotlight Desktop User Guide November 2012 67 7.

Actix Spotlight Desktop User Guide November 2012 68 Poor Ql.Each tab displays various KPIs for the selected site. you will lose the other tabs. ▫ Scanner (Where Seen / Best Server) As Handset but no RxQual or Link Diff information in the top table.(Handset data only) Shows the percentage of Good and Poor RxQual and RxLev in the data (see Coverage criteria for details). www. ▫ Quality tab .com .  Side Panel . Poor Lv and No Dom . Note that if you have the Visualization tab selected and you select a sector not included in the visualization.see Coverage criteria below for details.actix. and will need to click on a row in the top table to show them again.

A red line at the top indicates the maximum range for the analysis (equating to the red circle on the map).Actix Spotlight Desktop User Guide November 2012 69  Distance tab . BCCH adjacent lower.Displays a histogram of the distances at which the cell was measured.Displays BCCH. www. See also the previous worked example of GSM visualization. so if you set the Analysis (see below) to 'Where Seen'. TCH (if available in the cellrefs file) and Co BSIC co. the map will only show Where Seen data. TCH adjacent lower.  Visualization tab . as defined by SL_Overspill_Dist_Threshold (changeable from the Tools. in the following order: BCCH co-interference. BCCH adjacent upper. Display Thresholds command). out to a distance defined by the threshold G_Interference_Radius (which can be changed using the Tools. Display Thresholds command). Note that the color is determined by the first satisfied condition. so there may appear to be a discrepancy between the two views. Note that the side panel only shows Best Server data.com .and adjacent channel interference on the map by coloring in the interfering sectors. TCH co-interference.actix. TCH adjacent upper.

and so the %Intrf is 100% x 3/4 = 75%. there is 1 BCCH channel and 3 TCH channels used by the sector. In the TCH example below.Actix Spotlight Desktop User Guide November 2012 70 %Intrf or %Interference in the visualization table is the ratio between the number of interfering channels in common and the sum of all the channels on the cell. Each row shows only one interfering BCCH channel. So in the BCCH example below. and so the %Intrf is 100% x 1/4 = 25%. Each row shows three interfering TCH channels. www.com .actix. there is 1 BCCH channel and 3 TCH channels used by the sector.

and red sectors show that the cell also has the same BCCH. where baseband or synthesized traffic channels are being used.actix. Co BSIC visualization is shown below.com .that is. This type of visualization is inappropriate for frequency hopping .Actix Spotlight Desktop User Guide November 2012 71 TCH Co/adjacent Channel % is shown below. This is used to distinguish between two different cells which are on the same BCCH. www. Orange sectors show that there is another cell on the same BSIC (co BSIC channel interference).

Actix Spotlight Desktop User Guide November 2012 72 7.com . Where none of the above conditions is true. where n is 0 to 5.actix.6. www. Poor Lv No Dom Criteria ServRxQualSub < G_RxQualSub_Max threshold ServRxLevSub < G_RxLevSub_Min threshold If the sum of all these conditions is > 2: ((ServRxLevSubNborRxLev[n])<5) * (abs(ServBCCHNborBCCH[n])<375). Poor Ql Poor Leverl. Design % *This is the percentage of data points where one (or more than one) condition applies.5 Coverage criteria Condition Poor Voice Quality Poor Signal Strength No Serving Cell Dominance Top table column or Quality tab* Poor Quality. Good Design G.

click on the Radio Network Explorer button and click on this tab. In this example. 2 3 Sort the top table by the Add column. the call needs to be moved to a better cell. remove and retain recommendations for each site and cell. or click on an appropriate link in the left-hand Issues panel. You can export the suggestions made by the analysis directly to a CSV file for easy import and to update the switch directly.7 GSM 2G Missing Neighbors analysis This lets you use scanner data to optimize neighbor lists for sites within a userdefined radius (Maximum Intersite Distance) of the selected cell. from the Summary Dashboard page. If you have not done so before. Where the serving cell cannot carry a call due to interference or poor radio conditions.actix. the analysis will immediately update. If the cellrefs file contains neighbor information. www.com . 7. If you alter a data setting. Check that the Server Count column shows an acceptable value (you can also define a cutoff threshold using Minimum Samples in the Data Settings dialog as shown above). we will be interested in the Minimum Samples and the Addition Threshold.Actix Spotlight Desktop User Guide November 2012 73 7.2 Using the neighbor list analysis 1 To start this analysis. You can now see the sector with the highest number of recommended additions to its neighbor list.1 Before you start You will need to have loaded a suitable GSM scanner stream.7. the analysis examines the relationship between the existing neighbors and the potential neighbors as seen by the scanner. check the data settings that control the neighbor list analysis algorithm.7. and generates add. 7.

therefore there are also no retentions or removals suggested). by using the Events drop-down menu) will use the exact position rather than a binned position.Actix Spotlight Desktop User Guide November 2012 74 4 Click on the top row in the table to show information for that sector. The side panel on the left shows each recommendation for a sector individually. sorted by the % of data points that meet the recommendation algorithm. so events might not align with the data points. any events displayed on the map (for example.com . The map also displays the data points used in the analysis. Note that drive test data is binned according to the selections made in step 4 of defining the project template. The thickness of each line shows how well the suggestion meets the criteria of the analysis. The circle represents the radius of the Maximum Intersite Distance (defined in the Data Settings dialog) used by the analysis to identify potential neighbors. The map now shows lines to the recommended additions (there are many additions in this example as the cellrefs file does not contain any 3G-2G neighbor definitions .actix. However. www.

You could now go through the same process for the 'Removals' column (this example contains no 'removals' suggestions). existing cells between the sector and the suggested addition). So if you selected 5 additions. This can be useful if there are a large number of recommendations and you need to keep track of how many you have already selected. Note that the more potential neighbors you add.Actix Spotlight Desktop User Guide November 2012 75 5 Examine each suggested additional neighbor. You may have reasons for refusing to accept the suggestion on geographical grounds (for example. Also. conceivably resulting in a dropped call. with none currently selected for export. if there were 12 suggested additions in the first row. Note that by default the map does not show lines for removal recommendations.actix. you can use the table in the side panel on the left. You may well have an upper limit already defined by your internal guidelines. or for reasons related to the data settings. you may know that one or more sites will be going off-air and should not be selected. For example. If you do not want to select every recommendation for a sector. the number would show 0/12. but you can also control this using the Data Settings link at the top of the screen and specify a new Max Neighbor List Size value. www. If you accept all suggestions for a sector. this would result in the number reading 5/12.com . the longer it will take for a handset to find appropriate neighbors. the number would read 12/12. Note that the number beside the button changes to match your selection. you can click the related button in the table to mark your choice. 6 7 Repeat this process for each row in the top table. If you clicked the button. as necessary.

7. 7.Shows details of the neighbor recommendations.Shows add.Actix Spotlight Desktop User Guide November 2012 76 8 Once you are satisfied with the recommendations that you have selected. The map also shows the data points used in the analysis. lines to neighbors are drawn from that site. Currently plotted events are shown in red in the list. Filters – Select this link to specify filters for the table on the top panel. which can be used to build lists of suggested neighbor cells to add and remove. The currently selected attributes will be kept as you move between Spotlight's analysis pages. From the top of the page. click the Export data link.com . Data Settings – This link opens up a dialog box for configuring the algorithm that Spotlight uses for the missing neighbor analysis. Clicking on a row in this table displays neighbor information for the selected cell in the side panel. See below for more information.actix. The box beside each recommendation type shows which color it will be drawn in on the map click on the check box to show or hide that particular recommendation type (by default. Events – Lists the event attributes that can be plotted on the map.        www. Currently plotted attributes are shown in red in the list.3 Features of this analysis page  Top Panel . Attributes – Lists the most commonly used attributes that can be plotted on the map. Map . together with related site information. you can output them to a CSV file. Check boxes next to a recommendation can be selected for export to a CSV file. The circle represents the user-defined radius (Maximum Intersite Distance) used by the analysis to identify potential neighbors.When you click a row in the table or a site on the map. Removals are not shown). and draw lines to neighbors on the map. removal and retention neighbor recommendations for every site. Export data – Select this link to export neighbor recommendations to a CSV file. All of the options take effect immediately after you click OK. Side Panel .

com . For rural areas where the average intersite distance is naturally greater than a dense urban environment. Defines the maximum line-of-sight distance in meters between two cells for one to be considered for inclusion on the other's neighbor list. see below) from X’s neighbor list.actix. Allows you to define the maximum number of recommended neighbors. 5 1 Minimal Samples Maximum Intersite Distance (meters) 50 5000 Only process first best ARFCN Max Neighbor List Size Selected 32 www.2 Defines the minimum percentage of samples that cells in the current neighbor list must achieve in order to be recommended for retention in the list. cells will be recommended for removal from the list. The RxLev of any candidate neighbor cell must be no worse than this value from the RxLev Threshold for the cell to be considered in this analysis (so no worse than –100 dB if using the default value for RxLev Threshold). Defines the percentage of samples that must be reached to trigger a cell being added as a suggested neighbor. use a higher value. set this value to 0. When the percentages of samples fall below this threshold. Note that the more potential neighbors you add. the longer it will take for a handset to find appropriate neighbors. De-select this option if you want to analyze the neighbor list of all of the cells meeting the other criteria. conceivably resulting in a dropped call. Only sectors which have been measured above the Ec/Io Threshold at least this many times will be included in the analysis. where the percentage is: 100 * (No. of samples where X is the serving cell) where the thresholds relate to whether Y should be added (or removed. Removal Threshold (%) 0. of samples where cell X is the serving cell to Y) / (Total no.4 Data settings for this page Setting RxLev Threshold (dB) Reporting Range (dB) Addition Threshold (%) Default -95 Description The RxLev of the serving cell must be better than this threshold value for the cell to be considered in this analysis. Select this option to analyze the neighbors of the best cell only.7. This is used to reduce the effect of stray signals. To disable this feature. Note that the algorithm works off Binned data.Actix Spotlight Desktop User Guide November 2012 77 7.

they are aggregated by serving cell to produce the recommended neighbor list. and also that only cells angled towards the data point are suggested. In this example. set this value to 0. retentions and removals. and the angle to site threshold in lighter blue arcs on either side. To disable this feature. for that cell to be considered for inclusion in the serving cell's neighbor list. Once a potential neighbor list has been calculated for each data point. and are also within the Maximum Intersite Distance (the blue circle).actix. the beam width is shown as a darker blue arc. This threshold ensures that missing neighbors are not suggested from reflected signals or back-lobes. Acceptable data points are within this threshold of the candidate sector's beam width. This is compared with the existing list to calculate which are additions.com .Actix Spotlight Desktop User Guide November 2012 78 Setting Angle to site threshold (degrees) Default 90 Description Defines the maximum angle between the edge of a cell's beam width and the data point. www.

8 LTE Cell Coverage analysis You can use this analysis to:    Determine the coverage footprint for each cell.1 Before you start You can only use scanner data for this analysis. 7.8. 1 From the Summary Dashboard. Hovering over the link shows the thresholds used to identify this issue. 7. click on an appropriate issue link or the Radio Explorer icon to open the Cell Coverage analysis page.com . and changing the thresholds at this point will have no effect on the analysis. Visually determine where cells are overshooting their coverage design boundary (defined by SL_Overspill_Dist_Threshold). Note that these thresholds have already been applied to the loaded data.Actix Spotlight Desktop User Guide November 2012 79 7. Quickly visualize where a cell is the best server.actix. www. by selecting a cell.2 Example The Summary Dashboard shows an Important Issue relating to Poor Coverage.8.

Actix Spotlight Desktop User Guide November 2012

80

2

The Issues panel showed a high percentage of Poor Coverage issues, so examine the top table of the analysis for indications of poorly performing cells. Note that several rows have a low sample count and so are unreliable to use in this investigation. To remove rows with low sample counts, apply a Filter with a threshold of, say, 50 counts by selecting #Samples, > and enter 50. Click Add Filter and OK.

3

4

Sort by Av RSRP by clicking on the column heading.

www.actix.com

Actix Spotlight Desktop User Guide November 2012

81

5

Color the cells by RSRP by clicking on the multi-cell icon beside the column heading (the icon should become colored to indicate this is toggled on).

6

Select the top sector row.

7

Looking at the map, note that there are some samples with poor RSRP despite being very close to the problem sector.
www.actix.com

Actix Spotlight Desktop User Guide November 2012

82

7.8.3 Features of this analysis page

Top Panel - Shows a table of summary information. The table contains the following information: ▫ Scanner # - Number of samples. Ensure that you are looking at a statistically sensible number of samples. > Dist - Number of samples greater than the coverage design boundary (defined by SL_Overspill_Dist_Threshold). RSRP, RSRQ (Max, Min, Ave). > Beam – Percentage of points outside the cell beamwidth. >180 Beam – Percentage of points outside an imaginary beamwidth of 180 degrees. Clicking on a row in this table causes the side panel to display more information about the site. The map zooms to the site and displays its coverage.

Map - When you click a row in the top table or on a site on the map, the map shows the coverage wedge for the selected cell, RSRP and RSRQ. The red circle represents the user-configured coverage design boundary, and data points outside this circle represent overspill. Side Panel Quality tab – Displays a quadrant chart with the percentage values of points in good/bad RSRP and good/bad RSRQ, as defined by LTE_Scan_PoorRSRP_Threshold and LTE_Scan_PoorRSRQ_Threshold. Dist tab – Displays a histogram of the distances at which the cell was measured. A red line indicates the maximum range for the analysis, as defined by SL_Overspill_Dist_Threshold. Vis tab – Displays cell details.

Analysis – Select LTE Scanner Where Seen or Best Server analysis mode. Changing the mode affects the RSRP attribute that is displayed on the map. Best Server mode shows the RSRP when the selected cell was the best server. The Where Seen mode shows the RSRP whenever the cell was measured; coverage footprints can only be seen for those cells that were best servers at least once during the drive. In multi-carrier environments, you can perform analyses from the perspective of one carrier. Cell Search – Visualize a cell on the map. Input a Site Name, Sector ID, or PCI (previously named L1_CID) to visualize; this feature would color red all the cell(s) matching the selected criteria. Filters – Select this link to specify filters for the table on the top panel. Events – Lists the event attributes that can be plotted on the map. Currently there are no events to display. Attributes – Lists the most commonly used attributes that can be plotted on the map. Currently plotted attributes are shown in red in the list. The currently selected attributes will be kept as you move between Spotlight's analysis pages.
www.actix.com

   

Actix Spotlight Desktop User Guide November 2012

83

7.9 LTE 4G – 3G/2G Missing Neighbors
This lets you optimize neighbor lists for sites within a user-defined radius (Maximum Intersite Distance) of the selected cell. Where the serving cell cannot carry a call due to interference or poor radio conditions, the call needs to be moved to a better cell. If the cellrefs file contains neighbor information, the analysis examines the relationship between the existing neighbors and the potential neighbors as seen by the scanner, and generates add, remove and retain recommendations for each site and cell. You can export the suggestions made by the analysis directly to a CSV file for easy import and to update the switch directly.

7.9.1 Using the missing neighbors analysis
This analysis is accessible via the left hand panel under LTE > Important Issues. Spotlight aggregates the LTE, UMTS and GSM measurements and bins them according to the template settings (by default 3 arc-second location bins). For each bin, Spotlight determines which LTE sectors may need IRAT neighbors defined, based on the data settings for the analysis (see p83). For each bin and each LTE sector matching the IRAT neighbor analysis criteria, Spotlight determines which UMTS and GSM sectors should be added, retained or removed from the IRAT neighbor list based on the thresholds below. At the end of this process, for each LTE sector, Spotlight has established the number of bins where the missing neighbor analysis criteria is met, and a corresponding list of UMTS and GSM sectors with the number of bins where each sector meets the addition, retention or deletion criteria. Typically you would now search by Server Count (the number of bins where the sector is best).

7.9.2 Features of this analysis page

Top Panel - Shows add, removal and retention neighbor recommendations for every site, together with related site information. Clicking on a row in this table displays neighbor information for the selected cell in the side panel, and draw lines to neighbors on the map. The box beside each recommendation type shows which color it will be drawn in on the map click on the check box to show or hide that particular recommendation type (by default, Removals are not shown). Map - When you click a row in the table or a site on the map, lines to neighbors are drawn from that site. The circle represents the user-defined radius (Maximum Intersite Distance) used by the analysis to identify potential neighbors. The map also shows the data points used in the analysis. Side Panel - Shows details of the neighbor recommendations. Check boxes next to a recommendation can be selected for export to a CSV file.

www.actix.com

Actix Spotlight Desktop User Guide November 2012

84

    

Cell Search – Visualize a cell on the map. Input a Site Name, Sector ID, or PCI (previously named L1_CID) to visualize; this feature would color red all the cell(s) matching the selected criteria. LTE EARFCN, UMTS UARFCN – Specify these UARFCN frequencies to use to search for missing neighbors. Filters – Select this link to specify filters for the table on the top panel. Events – Lists the event attributes that can be plotted on the map. Currently there are no events to display. Attributes – Lists the most commonly used attributes that can be plotted on the map. Currently plotted attributes are shown in red in the list. The currently selected attributes will be kept as you move between Spotlight's analysis pages. Data Settings – This link opens up a dialog box for configuring the algorithm that Spotlight uses for the missing neighbor analysis, which can be used to build lists of suggested neighbor cells to add and remove. All of the options take effect immediately after you click OK. See below for more information.

7.9.3 Data settings for this page
Setting RSRQ Threshold (dB) RSRP Threshold (dBm) LTE Threshold Type Maximum intersite Distance (meters) Angle to site threshold (degrees) Default -10 Description An LTE sector may only need IRAT neighbors in locations with poor LTE coverage. This threshold represents the RSRQ value below which missing neighbor analysis will be performed in a bin. An LTE sector may only need IRAT neighbors in locations with poor LTE coverage. This threshold represents the RSRP value below which missing neighbor analysis will be performed in a bin. This indicates whether Analyzer should use "LTE RSRQ Threshold", "LTE RSRP Threshold", any of them, or both of them. An IRAT sector should not be considered as a missing neighbor if it is too distant from an LTE sector. This value defines the maximum distance that a UMTS or GSM sector should be from a LTE sector above which it will not be considered as a missing neighbor. The LTE IRAT missing neighbor analysis should only be performed on bins where the LTE sector is expected to provide coverage. This value defines the maximum angle the bin should make with the LTE sector azimuth in order to be considered for the IRAT missing neighbor analysis in a bin. 4G Thresholds

-95

RSRP Only 5000

90

www.actix.com

If more IRAT missing neighbors are found. above which it is considered a valid IRAT neighbor. This threshold represents the minimum CPICH Ec/N0 value for a UMTS sector. a GSM sector should only be considered a missing neighbor if its coverage is sufficient. For an IRAT sector. Therefore it is usually better to only optimize an IRAT neighbor list for the best LTE sector in a bin. If this option is selected. the list will only show those with the best addition ratio (see "Addition Threshold (%)"). This threshold represents the minimum CPICH RSCP value for a UMTS sector. the UE should be connected to the strongest LTE sector. a UMTS sector should only be considered a missing neighbor if its coverage is sufficient. In a bin. a UMTS sector should only be considered a missing neighbor if its coverage is sufficient. above which it is considered a valid IRAT neighbor. 3G-2G Thresholds EcIo Threshold (dB) -15 RSCP Threshold (dBm) -95 RSSI Threshold (dBm) Addition Threshold (%) -95 1 Max GSM Neighbor list size 32 Max UMTS Neighbor list size 32 www. In a bin. This threshold represents the minimum RSSI value for a GSM cell.com . the list will only show those with the best addition ratio (see "Addition Threshold (%)"). In a bin. An IRAT sector should only be added to the neighbor list of an LTE sector if it meets the missing neighbor criteria in a sufficient number of bins.actix. this threshold is the minimum value of the ratio (number of bins where IRAT sector meets IRAT missing neighbor criteria) / (number of bins where LTE sector meets IRAT criteria). above which it is considered a valid IRAT neighbor. This value represents the maximum number of IRAT missing neighbors that the side panel view will list. or else this addition would increase the risk of radio failures just after the IRAT handover. If more IRAT missing neighbors are found. Analyzer will only consider the best LTE sector for the IRAT missing neighbor analysis. above which the IRAT sector is considered for addition to the neighbor list. This value represents the maximum number of IRAT missing neighbors that the side panel view will list.Actix Spotlight Desktop User Guide November 2012 85 Setting Only process first best PCI Default On Description In a given bin.

com .2 Description An IRAT sector should only be removed from the neighbor list of an LTE sector if it meets the missing neighbor criteria in a very few number of bins. www. For an IRAT sector. below which the IRAT sector is considered for removal from the neighbor list. or else one might remove a valid IRAT neighbor from the neighbor list.Actix Spotlight Desktop User Guide November 2012 86 Setting Removal Threshold (%) Default 0. this threshold is the minimum value of the ratio (number of bins where IRAT sector meets IRAT missing neighbor criteria) / (number of bins where LTE sector meets IRAT criteria).actix.

7. If you alter a data setting. Check that the Server Count column shows an acceptable value (you can also define a cutoff threshold using Minimum Samples in the Data Settings dialog as shown above). In this example.Actix Spotlight Desktop User Guide November 2012 87 7. If you have not done so before. If the cellrefs file contains neighbor information. from the Summary Dashboard page. the analysis examines the relationship between the existing neighbors and the potential neighbors as seen by the scanner.10 UMTS / HSPA 3G Neighbor List analysis This lets you use scanner data to optimize neighbor lists for sites within a userdefined radius (Maximum Intersite Distance) of the selected cell.10. You can now see the sector with the highest number of recommended additions to its neighbor list. or click on an appropriate link in the left-hand Issues panel. You can export the suggestions made by the analysis directly to a CSV file for easy import and to update the switch directly. click on the Radio Network Explorer button and click on this tab. the analysis will immediately update. 7.1 Before you start You will need to have loaded a suitable GSM scanner stream. the call needs to be moved to a better cell.com . check the data settings that control the neighbor list analysis algorithm. and generates add.actix.2 Using the neighbor list analysis 1 To start this analysis. remove and retain recommendations for each site and cell.10. we will be interested in the Minimum Samples and the Addition Threshold. www. Where the serving cell cannot carry a call due to interference or poor radio conditions. 2 3 Sort the top table by the Add column.

Actix Spotlight Desktop User Guide November 2012 88 4 Click on the top row in the table to show information for that sector. However. any events displayed on the map (for example. The circle represents the radius of the Maximum Intersite Distance (defined in the Data Settings dialog) used by the analysis to identify potential neighbors. The side panel on the left shows each recommendation for a sector individually.therefore there are also no retentions or removals suggested). sorted by the % of data points that meet the recommendation algorithm. The map now shows lines to the recommended additions (there are many additions in this example as the cellrefs file does not contain any 3G-2G neighbor definitions .com . so events might not align with the data points. Note that drive test data is binned according to the selections made in step 4 of defining the project template. The map also displays the data points used in the analysis. The thickness of each line shows how well the suggestion meets the criteria of the analysis.actix. www. by using the Events drop-down menu) will use the exact position rather than a binned position.

Note that the more potential neighbors you add. Also. as necessary. you can use the table in the side panel on the left. or for reasons related to the data settings. For example. the number would show 0/12. www. You may well have an upper limit already defined by your internal guidelines. Note that the number beside the button changes to match your selection. If you do not want to select every recommendation for a sector.actix. with none currently selected for export. So if you selected 5 additions. this would result in the number reading 5/12. If you accept all suggestions for a sector. conceivably resulting in a dropped call. there were 12 suggested additions in the first row. You could now go through the same process for the 'Removals' column (this example contains no 'removals' suggestions). If you clicked the button. You may have reasons for refusing to accept the suggestion on geographical grounds (for example.com . existing cells between the sector and the suggested addition). the longer it will take a handset to find appropriate neighbors. you may know that one or more sites will be going off-air and should not be selected. but you can also control this using the Data Settings link at the top of the screen and specify a new Max Neighbor List Size value.Actix Spotlight Desktop User Guide November 2012 89 5 Examine each suggested additional neighbor. the number would read 12/12. This can be useful if there are a large number of recommendations and you need to keep track of how many you have already selected. Note that by default the map does not show lines for removal recommendations. 6 7 Repeat this process for each row in the top table. you can click the related button in the table to mark your choice.

From the top of the page.Shows details of the neighbor recommendations. The map also shows the data points used in the analysis. and draw lines to neighbors on the map. Events – Lists the event attributes that can be plotted on the map.Shows add. Currently plotted attributes are shown in red in the list. The box beside each recommendation type shows which color it will be drawn in on the map click on the check box to show or hide that particular recommendation type (by default.          www. Export data – Select this link to export neighbor recommendations to a CSV file. See below for more information. Side Panel . Map . Data Settings – This link opens up a dialog box for configuring the algorithm that Spotlight uses for the missing neighbor analysis. Check boxes next to a recommendation can be selected for export to a CSV file.actix. Specify an SC and this feature colors red all the sites using this SC. which can be used to build lists of suggested neighbor cells to add and remove. The currently selected attributes will be kept as you move between Spotlight's analysis pages.Actix Spotlight Desktop User Guide November 2012 90 8 Once you are satisfied with the recommendations that you have selected. The circle represents the user-defined radius (Maximum Intersite Distance) used by the analysis to identify potential neighbors. removal and retention neighbor recommendations for every site. Filters – Select this link to specify filters for the table on the top panel. Removals are not shown). Currently plotted events are shown in red in the list.com . Find SC – This link allows you to visualize an SC on the map. All of the options take effect immediately after you click OK. Attributes – Lists the most commonly used attributes that can be plotted on the map. 7. together with related site information. you can output them to a CSV file.When you click a row in the table or a site on the map.3 Features of this analysis page  Top Panel . click the Export data link.10. Scanner Frequency – The results can be filtered by carrier. Clicking on a row in this table displays neighbor information for the selected cell in the side panel. lines to neighbors are drawn from that site.

use a higher value. Only sectors which have been measured above the Ec/Io Threshold at least this many times will be included in the analysis. Select this option to analyze the neighbors of the best cell only.actix. Allows you to define the maximum number of recommended neighbors. set this value to 0.10. Defines the minimum percentage of samples that cells in the current neighbor list must achieve in order to be recommended for retention in the list.com . The RxLev of the serving cell must be no further than this from the RxLev Threshold before the cell will be considered in the analysis (so no worse than -100 dB if using the default values).Actix Spotlight Desktop User Guide November 2012 91 7.4 Data settings for this page Setting RxLev Threshold (dB) Reporting Range (dB) Addition Threshold (%) Removal Threshold (%) Default -95 Description The RxLev of the serving cell must be better than this value before the cell will be considered in the analysis. When the percentages of samples fall below this threshold. 5 1 0. cells will be recommended for removal from the list. conceivably resulting in a dropped call. This is used to reduce the effect of stray signals. Defines the percentage of samples that must be reached to trigger a cell being added as a suggested neighbor. To disable this feature. For rural areas where the average intersite distance is naturally greater than a dense urban environment.2 Minimal Samples Maximum Intersite Distance (meters) 50 5000 Only process first best ARFCN Max Neighbor List Size Selected 32 www. Note that the more potential neighbors you add. Note that the algorithm works off Binned data Defines the maximum line-of-sight distance in meters between two cells for one to be considered for inclusion on the other's neighbor list. the longer it will take for a handset to find appropriate neighbors. De-select this option if you want to analyze the neighbor list of all of the cells meeting the other criteria.

actix. Once a potential neighbor list has been calculated for each data point. the beam width is shown as a darker blue arc. and the angle to site threshold in lighter blue arcs on either side. retentions and removals. To disable this feature. they are aggregated by serving cell to produce the recommended neighbor list. and also that only cells angled towards the data point are suggested. Acceptable data points are within this threshold of the candidate sector's beam width. for that cell to be considered for inclusion in the serving cell's neighbor list. This threshold ensures that missing neighbors are not suggested from reflected signals or back-lobes. In this example.Actix Spotlight Desktop User Guide November 2012 92 Setting Angle to site threshold (degrees) Default 90 Description Defines the maximum angle between the edge of a cell's beam width and the data point. This is compared with the existing list to calculate which are additions. and are also within the Maximum Intersite Distance (the blue circle). www.com . set this value to 0.

7.are typically caused by missing neighbors.2 Using the neighbor list analysis 1 To start this analysis. which must contain a field called GSMNeighborList on the WCDMA_Cell network element. These are cells that have not been defined in the neighbor list of the strongest cell at a given location.11.com . and generates add.actix.and the call needs to be carried out or completed in the 2G network . If a handset stream is used. but which have an RxLevel good enough to be added to the UE’s neighbor list as a potential cell to hand over from 3G to 2G. UMTS scanners are able to scan several frequencies (identified by the UARFCN) simultaneously. the analysis examines the relationship between the existing neighbors and the potential neighbors as seen by the scanner. 7. Situations where the 3G network cannot carry a call due to interference or poor radio conditions . remove and retain recommendations for each site and cell. If the cellrefs file contains neighbor information. Increasingly. or click on an appropriate Issue in the left-hand Issues panel: www. You can export the suggestions made by the analysis directly to a CSV file for easy import and to update the switch directly. A GSM scanner or handset stream that was logged at the same time.11. These must have been loaded using a suitable matching cellrefs file. click on the Radio Network Explorer button and click on this tab.Actix Spotlight Desktop User Guide November 2012 93 7. from the Summary Dashboard page.11 UMTS / HSPA 3G-2G Neighbor List analysis This lets you use scanner data to optimize neighbor lists for sites within a userdefined radius (Maximum Intersite Distance) of the selected cell. it must have been logged in idle mode.1 Before you start You will need to have loaded the following:    A UMTS scanner stream that relates to a single UMTS frequency.

Actix Spotlight Desktop User Guide November 2012 94 2 If you have not done so before. check the data settings that control the neighbor list analysis algorithm.com .actix. 3 Sort the top table by the Add column. www. In this example. the analysis will immediately update. You can now see the sector with the highest number of recommended additions to its neighbor list. 4 Click on the top row in the table to show information for that sector. Check that the Server Count column shows an acceptable value (you can also define a cutoff threshold using the Minimum Sample Count as shown above). we will be interested in the Minimum Sample Count and the Addition Threshold. If you alter a data setting.

you can use the table in the side panel on the left. If you accept all suggestions for a sector. If you clicked the button. If you do not want to select every recommendation for a sector. the number would show 0/51. Note that the number beside the button changes to match your selection. so events might not align with the data points. there are a large number of recommendations and you need to keep track of how many you have already selected. the number would read 51/51.therefore there are also no retentions or removals suggested). 5 Examine each suggested additional neighbor. sorted by the % of data points that meet the recommendation algorithm. For example. So if you selected 13 additions. The map also displays the data points used in the analysis. www. you can click the related button in the table to mark your choice. this would result in the number reading 13/51. The side panel on the left shows each recommendation for a sector individually. The thickness of each line shows how well the suggestion meets the criteria of the analysis.Actix Spotlight Desktop User Guide November 2012 95 The map now shows lines to the recommended additions (there are many additions in this example as the cellrefs file does not contain any 3G-2G neighbor definitions . with none currently selected for export. The circle represents the user-defined radius (Maximum Intersite Distance) used by the analysis to identify potential neighbors. by using the Events drop-down menu) will use the exact position rather than a binned position. This can be useful if. as in this example.actix. if there were 51 suggested additions in the first row.com . Note that drive test data is binned according to the selections made in step 4 of defining the project template. any events displayed on the map (for example. However.

Clicking on a row in this table displays neighbor information for the selected cell in the side panel. Currently plotted events are shown in red in the list. You could now go through the same process for the 'Removals' column (this example contains no 'removals' suggestions). by editing the CSV file). Events – Lists the event attributes that can be plotted on the map. The currently selected attributes will be kept as you move between Spotlight's analysis pages. or for reasons related to the data settings. Currently plotted attributes are shown in red in the list. compared with the maximum permitted number of 32. Removals are not shown). Once you are satisfied with the recommendations that you have selected. removal and retention neighbor recommendations for every site. Check boxes next to a recommendation can be selected for export to a CSV file. Filters – Select this link to specify filters for the table on the top panel. and draw lines to neighbors on the map. conceivably resulting in a dropped call.Actix Spotlight Desktop User Guide November 2012 96 You may have reasons for refusing to accept the suggestion on geographical grounds (for example. The circle represents the user-defined radius (Maximum Intersite Distance) used by the analysis to identify potential neighbors. as necessary. Side Panel .When you click a row in the table or a site on the map.actix. From the top of the page. 6 If you disagree with a suggested addition. Note that by default the map does not show lines for removal recommendations. The map also shows the data points used in the analysis. You may well have an upper limit already defined by your internal guidelines. Map . The box beside each recommendation type shows which color it will be drawn in on the map click on the check box to show or hide that particular recommendation type (by default. click the Export data link. existing cells between the sector and the suggested addition). you can output them to a CSV file. Note that the more potential neighbors you add. you may know that one or more sites will be going off-air and should not be selected. the longer it will take for a handset to find appropriate neighbors. and will need to make the correction to the switch manually (for example. Repeat this process for each row in the top table.com      . lines to neighbors are drawn from that site.Shows details of the neighbor recommendations.3 Features of this analysis page  Top Panel . you may want to use the SC Search feature to find an alternative sector to add to the neighbor list. Attributes – Lists the most commonly used attributes that can be plotted on the map. Note that in this case you will not be able to output your choice.Shows add. together with related site information. www. Also. Another problem that arises from this example (due to no 3G2G neighbor data in the cellrefs file) is the sheer number of suggested additions: 51. 7 8 9 7.11.

Only sectors which have been measured above the Ec/Io Threshold at least this many times will be included in the analysis. A neighboring cell must have an RSCP of less than or equal to this value to be included on the potential neighbor list. use a higher value. of samples where cell X is the serving cell to Y) / (Total no. All of the options take effect immediately after you click OK. Note that the algorithm works off Binned data. Find SC – Visualize an SC on the map.4 Data settings for this page Setting UMTS Threshold Type EcIo Threshold (dBm) RSCP Threshold (dBm) GSM Neighbor Threshold (dBm) Minimal Sample Count Maximum Intersite Distance (meters) 0 Default Description Depending on which measurement your network uses for determining when to hand over. EcIo or RSCP. See below for more information.  7.11. set this value to 0. Specify an SC and this feature colors red all the sites using this SC. To disable this feature. A neighboring cell must have an EcIo of less than or equal to this value to be included on the potential neighbor list.actix. -100 -95 50 5000 Addition Threshold (%) 1 www. Defines the percentage of samples that must be reached to trigger a cell being added as a suggested neighbor.Actix Spotlight Desktop User Guide November 2012 97    Export data – Select this link to export neighbor recommendations to a CSV file. RSCP. This is used to reduce the effect of stray signals. Scanner Frequency – The results can be filtered by carrier. of samples where X is the serving cell) where the thresholds relate to whether Y should be added (or removed. where the percentage is: 100 * (No. Defines the maximum line-of-sight distance in meters between two cells for one to be considered for inclusion on the other's neighbor list. which can be used to build lists of suggested neighbor cells to add and remove.com . now the potential neighbor must have a measured BSIC greater than or equal to this value to be included on the potential neighbor list. For rural areas where the average intersite distance is naturally greater than a dense urban environment. or EcIo and RSCP. see below) from X’s neighbor list. If a potential neighbor has passed the UMTS threshold criteria described above. Data Settings – This link opens up a dialog box for configuring the algorithm that Spotlight uses for the missing neighbor analysis. select EcIo.

Once a potential neighbor list has been calculated for each data point. This threshold ensures that missing neighbors are not suggested from reflected signals or back-lobes. the longer it will take for a handset to find appropriate neighbors. set this value to 0. www. and the angle to site threshold in lighter blue arcs on either side. they are aggregated by serving cell to produce the recommended neighbor list.Actix Spotlight Desktop User Guide November 2012 98 Setting Removal Threshold (%) Default 0. Only process first best SC Max Neighbor List Size Selected 32 Angle to site threshold (degrees) 90 In this example. Acceptable data points are within this threshold of the candidate sector's beam width. retentions and removals. and are also within the Maximum Intersite Distance (the blue circle). Note that the more potential neighbors you add. To disable this feature. This is compared with the existing list to calculate which are additions.actix. cells will be recommended for removal from the list.2 Description Defines the minimum percentage of samples that cells in the current neighbor list must achieve in order to be recommended for retention in the list. and also that only cells angled towards the data point are suggested. Select this option to analyze the neighbors of the best cell only. Defines the maximum angle between the edge of a cell's beam width and the data point. When the percentages of samples fall below this threshold.com . for that cell to be considered for inclusion in the serving cell's neighbor list. the beam width is shown as a darker blue arc. Allows you to define the maximum number of recommended neighbors. De-select this option if you want to analyze the neighbor list of all of the cells meeting the other criteria. conceivably resulting in a dropped call.

7. 7. Hovering over the link shows the thresholds used to identify this issue.12 UMTS / HSPA Cell Coverage analysis You can use this analysis to:    Determine the coverage footprint for each cell. Note that these thresholds have already been applied to the loaded data.Actix Spotlight Desktop User Guide November 2012 99 7. by selecting a cell. 11 The Issues panel showed a high percentage of System Interference issues. Note that several rows have a low sample count and so are unreliable to use in this investigation.12. www.2 Example using handset data The Summary Dashboard shows an Important Issue relating to Poor Coverage. 10 From the Summary Dashboard. Quickly visualize where a cell is the best server. Visually determine where cells are overshooting their coverage design boundary (defined by SL_Overspill_Dist_Threshold).com . and changing the thresholds at this point will have no effect on the analysis.12. so examine the top table of the analysis for indications of poorly performing cells.actix.1 Before you start You can use scanner or handset data for this analysis. click on an appropriate issue link or the Radio Explorer icon to open the Cell Coverage analysis page.

13 Sort by Ave EcIo by clicking on the column heading.actix.Actix Spotlight Desktop User Guide November 2012 100 12 To remove rows with low sample counts. say. 50 counts. 14 Color the cells by EcIo by clicking on the icon beside the column heading. apply a Filter with a threshold of.com . Select the top sector row. www. Click Add Filter and OK.

However. by using the Events drop-down menu) will use the exact position rather than a binned position. Note that drive test data is binned according to the selections made in step 4 of defining the project template.actix. www. Site 8130 Sector B.Actix Spotlight Desktop User Guide November 2012 101 15 Looking at the map. 16 So what other cells are interfering to cause this situation? Experiment with plotting various Events and Attributes .plotting the Uu_ActiveSet_Count attribute shows that there is only one clear server. any events displayed on the map (for example.com . note that there are some samples with poor EcIo despite being very close to the problem sector. This may indicate a missing neighbor. so events might not align with the data points.

www. so exporting and using that new neighbor should solve the problem. Note that the map and table keep the focus on the selected cell.actix.com .Actix Spotlight Desktop User Guide November 2012 102 17 Click on the 3G Neighbor List tab. Here we can see that there is a suggested addition to the neighbor list. See the 3G Neighbor List analysis for more information.

Select the top sector row. Filter out any rows with low sample counts.Actix Spotlight Desktop User Guide November 2012 103 7. sort by >180 Beam by clicking on the column heading.com . As the problem concerns data points outside the serving cell beamwidth. Color the map cells by >180 Beam by clicking on the icon next to the column heading. 1 2 3 4 Click on the issue link to open the Cell Coverage analysis page. Note that the top two sectors are in the same site.actix.3 Example using scanner data The Summary Dashboard shows an Important Issue where a large percentage of data points were identified as being outside the beamwidth of the serving cell. 5 www. as described in the previous example.12.

4 Features of this analysis page  Top Panel . . Looking at the map. www.Actix Spotlight Desktop User Guide November 2012 104 6 7 Ensure that in the top panel.Number of samples. you select the Analysis 'Scanner . .Number of samples.Shows a table of summary information. ▫ Handset # . Select the other sector from the table or the map to confirm that this is a crossfeeder situation. – Percentage of points outside an imaginary beamwidth of 180 degrees. EcNo. Ensure that you are looking at a statistically sensible number of samples. note that the samples seen for the selected sector appear in the beam of the other offending sector. > Dist. The table contains the following information: ▫ Scanner # . if the difference is greater the 8 dB. >180 Beam. Ave). EcNo.Number of samples greater than the coverage design boundary (defined by SL_Overspill_Dist_Threshold). Min.Where Seen'. > Dist.Number of samples greater than the coverage design boundary (defined by SL_Overspill_Dist_Threshold).com . Link Diff. Ensure that you are looking at a statistically sensible number of samples. RSCP (Max. Min. RSCP (Max.actix.12. > Beam. 7. – This is the difference between UL and DL pathloss and is used to highlight cell with possible LNA (TMA) issues. Ave). – Percentage of points outside the cell beamwidth.

Analysis – Select Scanner (Best Server/Where Seen) or Handset (Best Server/Where Seen) analysis. EcIo & RSCP. Events – Lists the event attributes that can be plotted on the map. Filters – Select this link to specify filters for the table on the top panel. Note that in multi-carrier environments. The currently selected attributes will be kept as you move between Spotlight's analysis pages. coverage footprints can only be seen for those cells that were best servers at least once during the drive.  Map .Displays various KPI values for the site selected and a histogram of the distances at which the cell was measured. Attributes – Lists the most commonly used attributes that can be plotted on the map. Changing the mode affects the Ec/Io attribute that is displayed on the map. The Where Seen mode shows the Ec/Io whenever the cell was measured. A red line indicates the maximum range for the analysis. System interference % Limited coverage % Poor UL & DL % Clicking on a row in this table causes the side panel to display more information about the site. and data points outside this circle represent overspill. the map shows the coverage wedge for the selected cell. Best Server mode shows the Ec/Io when the selected cell was the best server. www. you can perform analyses from the perspective of one carrier.com .actix. The red circle represents the user-configured coverage design boundary. as defined by SL_Overspill_Dist_Threshold. Input a SC to visualize on the map and this feature would color red all the sites with this SC. This quickly identifies co-SC locations. The map zooms to the site and displays its coverage. Side Panel .When you click a row in the top table or on a site on the map.Actix Spotlight Desktop User Guide November 2012 105 Downlink Interference factor. The page can operate in two modes: Best Server and Where Seen. Currently plotted events are shown in red in the list.       SC Search – Visualize a SC on the map. Currently plotted attributes are shown in red in the list.

Alternatively. 2 Sort the top table by Outbound Cells and click on the top row. click on the Radio Network Explorer button and click on the Cell Pilot Pollution tab.1 Before you start You can use scanner or handset data for this analysis. www.13. 7.actix. You can determine the relative degree of pollution for each cell and prioritize which cells in the network are strong candidates for downtilts and coverage optimization. click on an appropriate Issue in the left-hand Issues panel.13 UMTS / HSPA Cell Pilot Pollution analysis This lets you quickly identify pilot pollution in the inbound (how the selected sector is being polluted by other sectors) and outbound (how the selected sector is polluting other sectors) directions. from the Summary Dashboard. 7.13.Actix Spotlight Desktop User Guide November 2012 106 7. and view the offending sectors on the map.2 Example using scanner data 1 To start this analysis. such as Too Many Servers (a pilot pollution issue).com . You can also select single or multiple events to see lines to the sectors contributing to the pollution.

any events displayed on the map (for example. The map now highlights the selected sector. Inbound pilot pollution lines are drawn in blue. and Outbound and Inbound Cell polluters. 5 www. De-select Outbound Cells and select Inbound Cells. Rolling over the lines with the cursor displays more detailed information (see the example below). The thickness of the lines indicates the degree to which pilot pollution was detected for the selected sector. drag a box around the area with a cluster of Too Many Server events.com . and that you can hide or show these polluting lines by clearing or checking the related box in the top table. so events might not align with the data points. based on the loaded data. The arrow on each line points from the polluting sector to the polluted sector. as the selected sector 55662 looks like the best candidate for investigation as it has a high number of Too Many Servers events. 3 De-select the Inbound Cells box to hide the inbound polluting lines. However. to show lines to cells.Actix Spotlight Desktop User Guide November 2012 107 In this example. 4 The inbound polluters are shown by blue lines. by using the Events drop-down menu) will use the exact position rather than a binned position.actix. The map also shows the Too Many Server events. Note that drive test data is binned according to the selections made in step 4 of defining the project template. Outbound pollution lines are drawn in red from the selected sector to the sectors being polluted. On the map.

Actix Spotlight Desktop User Guide November 2012 108 There is no clear dominator in this area.actix. At this point you could use the Cell Coverage tab to see the best way to improve the coverage for the selected sector. In the image below.com . 6 To see how the selected sector is polluting other sectors. de-select Inbound Cells and select Outbound Cells. from the top table. the EcIo values have been plotted on the map to confirm the situation near the Too Many Server events. and a few polluting cells are some distance away. www. so you would need to improve the coverage in that area.

The lines to polluters have a direction arrow suggesting inbound or outbound pollution. Select one or more to plot on the map.13. 7. to draw lines to inbound as well as outbound pollution from that site. It includes in a tabular form the number of pilot pollution events for each site and the total number of inbound/outbound polluters.actix. past much closer sectors. Map . Filters – Select this link to specify filters for the table on the top panel. Use the Cell Coverage tab to see how best to improve the coverage for the selected sector. Clicking on a row in this table causes pilot pollution information for the selected cell to be displayed in the side panel. All the pilot pollution events involving the site are also plotted on the map. and lines to polluters to be drawn on the map. This confirms that the selected sector may need some downtilt to avoid causing the pollution and to increase nearby coverage.Shows details of the inbound and outbound pollution for the selected site.Summary information is displayed in the top panel.Click a row in the top panel or a site on the map.3 Features of this analysis page  Top Panel . Side Panel .Actix Spotlight Desktop User Guide November 2012 109 The selected sector is causing pollution at quite a distance. Currently plotted attributes are shown in red in the     www.com . Attributes – Lists the most commonly used attributes.

So.com . such as in UMTS FDD mode.  Events – Lists event attributes. the interference level is directly related to the user density in the considered cell and neighbors. The more users in the system. The F factor can be calculated from measurements as follows: CPICH Ec/Io = CPICH RSCP – UE RSSI UE RSSI = Nt + Is + Io where: Nt = thermal noise of the UE (-100 dBm) Is = Interference (received power fraction) coming from same cell Io = Interference (received power fraction) coming from other cell We know that in an unloaded network. Is = 2 x CPICH RSCP So the F factor. So. you could plot the UMTS Dropped Call event on the map and quickly see if the call dropped due to pilot pollution. Currently plotted events are shown in red in the list. A satisfactory Eb/N0 value is of paramount importance in maintaining a satisfactory quality of service (measured using Frame Erasure Rate or Block Error Rate). so you can quickly identify co-SC locations. the higher the interference and the smaller the cell range. can be written as: F = Io / Is = ( UE RSSI – Nt – (2 x CPICH RSCP)) / (2 x CPICH RSCP) 2 x RSCP is also measured RSCP + 3dB. and therefore interference is directly linked to the coverage and capacity of such a network. Note that the formula is only valid for unloaded networks that do not experience much fading. understanding the relationship between coverage and capacity — and how it is affected by interference and transmit power—is essential for UMTS network planning. The currently selected attributes will be kept as you move between Spotlight's analysis pages. and affects both the cell range and capacity of the system. whether you are looking at a totally new network or a secondgeneration network that is migrating to 3G. interference is a critical factor because communication occurs on the same frequency band and time slot. Select one or more to plot on the map. Analysis – Select Scanner or Handset analysis. Input a SC to color red all the sites with this SC.14 About the Interference factor (‘F’ factor) With CDMA technology.actix. Io / Is.Actix Spotlight Desktop User Guide November 2012 110 list. One important source of interference in a WCDMA network comes from the signals transmitted by surrounding cells (inter-cell interference). defined as Home cell noise/Total noise. www. SC Search – Visualize a SC on the map. Of course all additions and subtractions should be done linearly (first convert from dB to Watts…). while looking at pilot pollution.   7. As a result. The F factor can also indicate pilot pollution—coverage quality will suffer from an increased load as the F factor increases. This is represented by the F factor.

7.14. If a cell has a higher value. most of the DL interference (F-factor) is below 5 across most of the drive. the F-Factor is very dependent on the route. Note When examining drive data.com .Low 'F' factor In the example below.actix. because at the edge of cells the F-factor will naturally be higher.1 Example 1 . and even more so when the network becomes loaded. the capacity of this cell will be impacted. www.Actix Spotlight Desktop User Guide November 2012 111 A good value for the F factor is below 3 (or 4) over 95% of the cell area.

or new sites.com .14. www. there are areas where the DL interference is high. the region needs some optimization.Actix Spotlight Desktop User Guide November 2012 112 7.actix. in the form of downtilts.High 'F' factor In the example below. The region could suffer from capacity issues as the network usage increases. even with a cell site in the area (for example . azimuth changes.2 Example 2 . Thus.middle bottom).

you can work from the data in the top table or from the diagnostics panel on the left. The side panel lists all the critical events occurring in the drive. When using this page.Actix Spotlight Desktop User Guide November 2012 113 8 Using the Event Explorer 8. www. The table in the top panel has a row for each site and lists the failure rates for that site.1 About the Event Explorer The Event Explorer provides a detailed analysis of critical failure events. 8. Note that the table shows a set of KPIs that correspond to the current Category (selected from a drop down menu above the top table – this prevents the table from becoming cluttered by only showing a small set of related KPIs at the same time).actix.1 Worked example investigating dropped calls In this case. You could arrive at this page from the Summary Dashboard as a result of clicking on an appropriate Issue or on the Event Explorer icon. we have chosen to analyze call drops and so all the dropped call events appear on the map. The cell wedges are color coded to represent dropped call numbers.1.com .

If the top table shows high values for a particular problem KPI. www. The symbol beside the top table heading indicates the additional effect of selection: Selecting a heading with an on the map.Actix Spotlight Desktop User Guide November 2012 114 Selecting the heading sorts the table by that KPI. If there are many rows in the table. you might want to sort by the Diagnostics column to see the diagnostic types grouped alphabetically. check the top left hand box to enable the selection boxes for each row. Then check each row with high problem KPIs.com . The side panel is now filtered to show the events appearing for only the selected site/sector rows.actix. icon allows you to visualize the KPIs and events Selecting a heading with an icon allows you to visualize the KPIs and events on the map and also displays the diagnostics on the left panel.

Plotting pilot pollution events may also help you to understand the situation here. you could see if EcNo is higher around a dropped call.2 Features of this analysis page   Filters – The table on the top panel can be filtered by adding filters through this dialog Attributes drop-down menu – List of attributes that are most useful in analyzing drive data. 8.1. See the Attribute / Event Help (available from the Help menu) for more information.actix. which is expected for a handover problem. However.Actix Spotlight Desktop User Guide November 2012 115 In this example. Events drop-down menu – List of the event attributes that can be plotted on the map. see the section on Drilldown on p116. Note that drive test data is binned according to the selections made in step 4 of defining the project template. From the map. See the Attribute / Event Help (available from the Help menu) for more information. so they may not necessarily align with the data points. EcIo has been selected from the Attributes menu at the top and displayed on the map. which would suggest that the call quality was degrading immediately before the event.  www. for UMTS data you could select Uu_ActiveSet_EcNo. For example.com . There are some poor values surrounding the dropped call event. any events displayed on the map will use the exact position rather than a binned position. For more information. Drilldown allows you to view selected data related to the event on the Drilldown page. which shows a range of analysis views appropriate to the type of diagnosis.

you will need to have selected a template that includes Data Service Analysis when you create your Spotlight project.The left hand side panel provides a diagnosis for the failure event.com .2.actix. 8.Provides RF measurement data around the event 8.Actix Spotlight Desktop User Guide November 2012 116  Detailed event diagnostics . Note that for this functionality to be available. probably working in conjunction with some legacy UMTS or GPRS areas.1 Using the Data Service Analysis Page The screenshot below shows the Data Service Analysis page. Typically this will be for an HSPA network. consisting of these sections: ▫ ▫ ▫ ▫ Causes – Shows possible causes for the event Further Explanation – Provides details on the causes for the event Further Analysis – Suggests how to proceed with further analysis Measurement Information .2 Data Service Analysis You can use this analysis to examine the data service performance of your network. www.

To set the thresholds. if a PDP Context Activation procedure fails).actix.A Service Drop is detected when the UE loses the end to end connection to the core network (for instance. A failure is detected when the Task did not complete (for instance. after a Routing Area Update procedure failure). an FTP ‘put’ or ‘get’. As an example of how the composite threshold value is calculated.but fails . Percentage of FTP or HTTP upload or download tasks below the absolute threshold value . shown above) DSA All Services and Tasks DSA Task Summary www. from the top menu select Tools > Display Thresholds and go to the Data Service Analysis section.Task is used to refer to any data upload or download. Service Drop Rate . The technology threshold is derived by Analyzer from a set of configurable technology thresholds based on the time the UE spent on each technology. The composite throughput threshold is: (80% x ApplicationLowTput_UMTS_DL_Threshold) + (20% x Application_LowTput_HSDPA_DL_Threshold) Note the dropdown selector at the top of the left hand panel. This allows you to select one of several Analysis pages:    DSA Failures (the default page.This corresponds to Tasks for which the average throughput was less than a technology dependant threshold*.to get an IP address (for instance. if the UE failed to download a file in case of a FTP DL test).Actix Spotlight Desktop User Guide November 2012 117 The panel reports on the following issues:  Service Setup Failure Rate . browsing a web page or a ‘ping’ test.com . consider a data download Task where the UE spends 80% of the time in Cell_DCH R99 and 20% in HSPA. Percentage of FTP or HTTP upload or download tasks below the composite threshold value .     *Make sure that you set the Data Service Analysis thresholds to suit your requirements before loading the data. A Service Setup Failure is detected when the UE attempts . for example. Task Failure Rate .Service is used to refer to the end-to-end connection between the UE and the core network.This corresponds to Tasks for which the average throughput was less than a configurable threshold*.

Actix Spotlight Desktop User Guide November 2012 118 From the DSA All Services and Tasks page. The following example screenshot shows the Event Explorer view for the FTP DL link Display All 57 Tasks: www.actix.com . you can click on the Display All links to view the related Event Explorer view.

you could also sort by Throughput.Interrupted (unknown whether this failed or not) OK . www. Scrolling down the left hand panel.Successful task To identify worst/best performing tasks. as well as the technologies that the UE experienced during the task. The Status codes are: D .Cancelled by user I .actix. The information displayed depends on the task type (upload or download). you can see useful data service statistics.Drop C .Actix Spotlight Desktop User Guide November 2012 119 To better understand the situation.com . the user has sorted the table on the left by Status.

Once you are ready to proceed. click the Begin Drilldown button. you can select the box next to it and complete the Drilldown section to define the data that will be included in the drilldown. www.actix. a low throughput task.Actix Spotlight Desktop User Guide November 2012 120 Once you find an interesting task (for instance.com . or task with multiple Radio Access Technologies).

actix. Several examples of DSA drilldown analysis are included in the following sections. go to the top of the left panel and click on the Event Explorer link.com . www.Actix Spotlight Desktop User Guide November 2012 121 When the drilldown processing has completed. you will see a drilldown analysis page similar to this: If you want to return from a drilldown.

com . and CPICH RSCP are all good. we can see that the UE is in HSPA+ mode throughout. whereas frame usage. The cause could be that the FTP server cannot sustain more than 4 Mbps on average. instantaneous throughput measurements are erratic. Although on average the throughput is about 4.5 Mbps. CPICH EcN0. www.2. Note also that the throughput does spike at > 10Mbps. resulting in ‘bursty’ data transmissions on the air interface. ranging from 0 to 10 Mbps. that 64QAM modulation usage is high throughout.2 Example of a good HSPA+ task In this HSPA+ example. HSDPA codes and throughput are all erratic.actix. and CQI.Actix Spotlight Desktop User Guide November 2012 122 8. This behavior is symptomatic of a buffer filling / emptying somewhere along the data transmission chain. From these observations we can conclude that:   The radio conditions were good throughout this section of drive. allowing for maximum download data rate. In these conditions the UE could have achieved ~10 Mbps.

this indicates the HSDPA NACK rate measured from subframes where a single transport block was received. These statistics are measured from the portion of the task where the UE is configured in MIMO mode:    MIMO configuration (%) . NACK Rate (%) . Usage (% frames) . TB Size Avg. Data Rx (%) .    www. It indicates the percentage of subframes in MIMO mode for which a single transport block was received. the side panel also shows HSPA+ MIMO measurements statistics.This is the average of the CQI measurements sent whilst the UE is in MIMO mode. and if in MIMO mode.3 Example of a MIMO HSPA+ FTP download There are three areas of interest in this example:    MIMO statistics Modulation TCP slow start MIMO statistics Note that the application throughput is ~5 times lower than the HSDPA L1 data rate: this is because in this log files.2. and the percentage for which two transport blocks were received. and where two transport blocks were received. to the total number of HSDPA subframes received. it can be using 1 transport block (diversity mode) or 2 transport blocks (spatial multiplexing mode). HSPA+ can either be in MIMO mode or non-MIMO mode.In MIMO mode.In MIMO mode.Actix Spotlight Desktop User Guide November 2012 123 8.This is the ratio of: the number of HSDPA subframes received when MIMO was configured. there were 5 simultaneous FTP downloads. and how much on two transport block transmissions. this indicates how much data was received on a single transport block transmissions.This is measured from subframes received in MIMO mode.In MIMO mode.com . MIMO CQI Average . since the UE has been configured to MIMO during the task. this indicates the average number of bits received per TTI.actix. (bits) . In this case.

spatial multiplexing was used 34.com . The HSDPA NACK rate is high in MIMO mode and also significantly higher with spatial multiplexing than with diversity: possibly the Node B settings should be changed to reduce the NACK rate. www.actix. Although the UE received two transport blocks in MIMO mode 34.80 % of the data received: spatial multiplexing is more efficient than diversity. it amounted to 48.16% of the time.Actix Spotlight Desktop User Guide November 2012 124 In this task we see the following:    In MIMO mode.16 % of the time.

and the data transfer fails. The best modulation is then 16 QAM.com . because this 3GPP release 7 handset cannot use both MIMO and 64 QAM modulation at the same time. during which the UE sometimes benefits from MIMO spatial multiplexing configuration. Eventually the RRC connection drops. the UE is configured for MIMO. the radio conditions degrade to a point where the UE is virtually only using QPSK modulation. the UE is not configured for MIMO and uses 64 QAM. During this third period.actix. 2 3 www. During this second period.Actix Spotlight Desktop User Guide November 2012 125 Modulation A quick analysis of the HSDPA radio chart tells us that there is a situation involving modulation usage. We can break down this task into three periods (labeled in the screenshot): 1 During this first period.

These problems are presented in a declining order of importance (problem 1 being the most significant).com .2.4 Example of a problematic HSDPA task This HSDPA example highlights three problems.actix. This is a typical effect of TCP flow control after a reconnection.    Problem 1 – UE spends time in DCHR99 mode Problem 2 – congestion causing low HSDPA frame usage Problem 3 – low modulation order www.Actix Spotlight Desktop User Guide November 2012 126 TCP Slow Start We can see that after most of the HSPA cell changes. based on the proportion of the call where these conditions were occurring. 8. known as TCP slow start. the HSDPA data rate and the number of HSDPA codes allocated to the UE both drop to a low value and then slowly ramp up.

actix.com . The transition to Cell_DCH R99 mode could be caused by the poor radio conditions.Actix Spotlight Desktop User Guide November 2012 127 Problem 1 – UE spends time in DCHR99 mode Here we can see periods were the CPICH EcN0 is low and the UE is in Cell_DCH R99 mode. www. or possibly the maximum number of concurrent HSDPA users has been reached on this site. The downlink throughput achieved during these periods is very low compared to what can be achieved in HSDPA mode.

www.com . although there are good radio conditions (high CPICH EcN0). This is likely to be the result of congestion.Actix Spotlight Desktop User Guide November 2012 128 Problem 2 – congestion causing low HSDPA frame usage In this case.actix. HSDPA is being used and the UE is allocated a large number of HSDPA codes when scheduled. the frame usage is very low.

Actix Spotlight Desktop User Guide November 2012 129 Problem 3 – low modulation order In this last case. In the latter case. the low modulation order is likely to be responsible for the low throughput. there are periods of high throughput coinciding with good CPICH EcN0 and high 16QAM modulation usage.com .actix. but there are also periods where the opposite is occurring. www.

the frame usage is only ~50%. some equipment or data link cannot support a throughput higher than 10 Mbps. spatial multiplexing usage is good at > 80%.Actix Spotlight Desktop User Guide November 2012 130 8. However. www. which is probably due to a bottleneck along the data transmission chain – that is. CQI is at maximum throughout the call. and system bandwidth allocation is good at > 80% (40 Resource Blocks in this case).actix. there is a high (> 10 Mbps) throughput.com .2.5 Example of a reasonable LTE task In this LTE example.

8.actix. A simple method is to check the Load Entire File box to load the whole file containing the event for further analysis. on the bottom side panel. other reasons to use drilldown may be that you may have some engineering knowledge or familiarity with the locality that leads you to suspect that the diagnosis may not be considering these factors. If you want to drill down further to investigate at the message level.3 Drill Down from the Event Explorer All Spotlight analyses in the Event Explorer and Radio Network Explorer pages use data from the project database. 8.com .Actix Spotlight Desktop User Guide November 2012 131 8. www. As you become familiar with Spotlight’s event diagnostics. This is faster than loading the entire file. The Drilldown controls let you specify the amount of data you want to load from the related data file and display on the Drilldown page. Note If you do not define a large-enough drilldown window. If you leave Load Entire File blank. Spotlight will only load data for that time window. the window might not include the appropriate messages that trigger the event.1 Why use drilldown?   Initially you will want to be reassured that the Spotlight diagnosis is correct. This may take a long time for a large file. click on the check box next to an event to drill down further. In this example on the right.3. there is only one dropped call event and that has been selected.3. although in practice it is more efficient to select multiple calls for the drilldown analysis. you can specify a window of time around the event using the Before Window and After Window fields.2 Specifying a drilldown window Check the Drill Down box for one or more events.

Actix Spotlight Desktop User Guide November 2012 132 The technology of the loaded data determines how the drilldown window actually operates: Once you have input the Before Window and After Window values.actix. This will take you to the detailed Drilldown page. www.com . click on Begin Drilldown.

clicking on the Begin Drilldown button starts the drilldown process and displays the drilldown page.actix. www.3 The Drilldown page In this example. The top Dropped Call event has been selected for drilldown.3. we are examining a series of dropped call events.com . together with a diagnosis of the cause.Actix Spotlight Desktop User Guide November 2012 133 8. The table on the left shows a row for each Dropped Call event selected for further drilldown.

also showing the originating data file name. This set of views. The charts give the SIR. called a screen layout. and also make use of the Replay control to step through the data.Actix Spotlight Desktop User Guide November 2012 134 The page shows several views to help you analyze the event in more detail. You can access standard Analyzer views from the View menu.actix. This particular layout provides most of the information needed to diagnose a dropped call.com . A Protocol Stack Browser provides detailed messaging around the event.    Detailed Event Diagnostics are in a panel on the left. is standard for this type of event. The UMTS Event Navigator shows the event and the serving SC. RSCP and Tx power information around the event. www. A map and the UMTS Event Navigator window display attributes relating to the selected event. Note All the views will have data only for the time window specified in the previous step. Each drilldown that is based on a different failure event will have its own screen layout. EcNo.

com . click on the Log Files link. In order to do this.2 To load data into Analyzer Classic 1 From the Summary Dashboard's Repository Summary table. 9. 4 Click the Analyzer Classic tab to show a list of loaded files. www. 5 Check the box to the left of each file that you want to load into Analyzer Classic.Actix Spotlight Desktop User Guide November 2012 135 9 Performing a more detailed analysis You may want to perform a detailed analysis of the selected data.1 Before you start You must already have created a project and loaded files into the repository. you can view a list of the files loaded into the current project's repository and select which of them to load into Analyzer Classic. 9.actix.

6 Click the Load Files button. the current views are minimized and two new views are displayed: an Attribute Explorer on the left. 7 8 Perform analyses on the data using the advanced tools available in Analyzer Classic. This loads any checked files that are not already loaded. and can be unloaded using the Unload All button (which is disabled if there are no loaded files). Note that this does not affect the project database in any way. Once the load is complete. containing a single Return to Spotlight link. If you do not want to return to Analyzer Classic and re-examine the selected data.com . When you have finished using Analyzer Classic. you can now click on the Unload All button to close files loaded into Classic. and a new Task Window positioned in the top right corner of the available screen area.actix. www.Actix Spotlight Desktop User Guide November 2012 136 Files that are already loaded have their boxes checked and disabled. which will restore the Spotlight view. you can click on the Return to Spotlight link. Note that this will not close any files that have been loaded into Analyzer Classic which are not listed as loaded into the project repository.

www. where a set of selected criteria apply. click on the Reports link to open the Reports dialog. you require a set of images to use in a management report that shows the results from drive test data imported into Actix Spotlight. To use Batch Sector Plot 1 9 From the Spotlight Dashboard. The available options will depend on the data currently loaded.com . 10 Select the appropriate Technology.actix. This would be useful if. UMTS. for instance. but include Scanner and Handset for CDMA. Now click on the Batch Sector Plot link.Actix Spotlight Desktop User Guide November 2012 137 10 Batch Sector Plot The Batch Sector Plot function lets you export a series of images. Each image shows a particular attribute plotted in relation to a sector. GSM. This opens the Batch Sector Plot dialog. and Handset only for EVDO.

where Size X is the width of the image and Size Y is the height. then all sectors on that SC (and UARFCN if defined in the cellrefs) will be exported in one image. BMP – This results in much larger graphics files. Some sectors may appear on the screen very briefly – these failed to match the selected criteria. If you use Insert Object in Excel. and the choice is By SC or By Sector. Select the Map Image Format: PNG – The default map image format option. This depends on the selected Technology. 12 Now select the Footprint for the cell in each output image: Where Seen – the image only includes those points where the cell could be seen during the drive(s). check the Coverage Wedge box. 15 Each image will cover the area of the Union of the bounds of the attributes.com . 17 To display the coverage wedge and overspill circle. The legend is not be exported by default. The coverage wedge and overspill distance circle are drawn by default 18 To export the legend for each image as a separate BMP image. you have the ability to link to a graphics file. check the Legend box. The cell is only included if it was best server at some point in the drive(s). Spotlight will now cycle through the sectors and create an image for each one that matches your criteria. the example shown is for UMTS Scanner. 19 Once you are satisfied with your selections. and is only recommended if you intend to use the images with Microsoft Excel.Actix Spotlight Desktop User Guide November 2012 138 11 Select the Attribute that you want to display on the output images. Where Best – the image only includes those points where the cell was the best server during the drive(s). If by SC (or BCCH etc. plus a 4% padding. The number of points for the attribute must be equal to or higher than this value for an image to be exported. Only one attribute may be exported for each use of this function. Only links to BMP files will show the actual image – other formats will only show an image icon. plus the highlighted cells. The legend for a plot is always output in BMP format regardless of this selection.actix. 13 Select how you want to Plot the results. 14 Select the Min Sample Count threshold. One image will be exported for each SC. The available options will depend on the selected Technology. click the Generate button. Sector or other selection that meets the other criteria entered in this dialog. Cells on the same SC but that were not seen during the drive will not be highlighted. as PNG files are small yet remain clear. 16 Enter the Map Image Size in pixels. www.) is chosen.

com . Windows Explorer opens at that folder. Any legend BMP files are output into the same folder using the same number.actix. Some sample results are shown below: www.bmp yyyy-mm-dd-hhmm.png When the batch run ends.Actix Spotlight Desktop User Guide November 2012 139 The images are consecutively numbered and placed in a folder with a time-stamped name: yyyy-mm-dd-hhmm. so they can easily be matched to the related plot file.

For example. performance may be slower than necessary. In addition. if you include KPIs and reports that are not relevant. start a new Spotlight project and on the Creating a New Project: Step 1 page. To create a Spotlight project template. and how the data is to be stored in the repository. You then need to fill out options on the following pages:      Step 1: Choose Name and Starting Template Step 2: Choose Devices Step 3: Choose KPIs and Reports Step 4: Choose Attributes Step 5: Choose Global Filters www. project templates are not the same as repository templates.com . Although Spotlight is based on repository technology. During this process. When you create a project template using Spotlight's New Template option.Actix Spotlight Desktop User Guide November 2012 140 11 Creating a Spotlight Project Template Spotlight project templates define which KPIs. reports and attributes are available within Spotlight. but also when subsequently closing and reloading it. Spotlight also generates a repository template based on the KPIs and other options that are selected. particularly when creating the project and loading data into it. the way you configure the project template can affect the performance of the projects that are based on it. Configuring a project template correctly is important. Spotlight uses a default repository template that is supplied with Spotlight. because it controls not only what analysis is available. click New Template. but also how the data is organized and this can affect the validity of the analysis.actix.

Enter a unique name for the template. This must not contain any of the following characters: \ / : * ? " < > |.com . www. where the new template appears in the list of project templates. Spotlight appends the date on which it was created to the project template's name.actix. The Master Template. which contains all available KPIs. 1 Template Name .Actix Spotlight Desktop User Guide November 2012 141 After clicking Done on the last page. you are returned to the New Project start page. Note that templates shipped with the product are shown in blue.1 Step 1: Choose Name and Starting Template This page is the first step in creating a new Spotlight project template. 21 Click Next to go the next page. Note For convenience. is at the bottom of the dropdown list.Select the existing project template on which you want to base your new template. 11. 20 Based on Template .

you should create the smallest number of devices that are required to separate the data in such a way that the KPIs and reports will provide statistically valid results. one handset does a succession of short (approximately 90-second) calls separated by 30 seconds of idle time.com  . Typically. the short calls provide data for event KPIs. 11.2 Step 2: Choose Devices The second step in creating a new Spotlight project template involves defining how you want the data to be stored. Essentially.actix. Another common scenario is when data is logged by two handsets and one scanner in a single drive test unit. Combining the data would normally give misleading results. whereas the long calls provide data for measuring the radio performance. However. Typically. because generally.2. In this scenario. in which the handset stays in call until the call drops. The other handset is for "long calls". such as the percentage of call setups that were successful. the handset and scanner data is stored in different attributes and the KPIs and statistics are based on one type of attribute or another and therefore provide a means of separating the two types of data. it would skew the dropped call rate. you need to consider how and why the data was logged:  The simplest scenario is when the data was logged by one handset and optionally one scanner in a single drive test unit. For www.. you might want to separate the handset and scanner data into separate devices for convenience or clarity. the long call data would by definition have an almost 100% dropped call rate and so if used for event KPIs. etc. it is generally safe to combine the data from both logging devices into a single Spotlight device. You can choose to combine all of the data (this is the default) or to separate it into silos called devices.Actix Spotlight Desktop User Guide November 2012 142 11. For example. and so ideally. whereupon the dialer immediately starts a new long call. When determining how many devices to create.1 How many devices do I need? Each additional device adds a performance overhead. you should separate the data into multiple devices when combining it would be statistically invalid and the structure of the attributes and KPIs and the statistics in the reports do not provide a mechanism for separating the data.

Actix Spotlight Desktop User Guide November 2012

143

this scenario, you should therefore create separate devices for the short and long call data.

A similar scenario occurs when a single drive test unit has two devices, but one was used for voice calls and the other for data. Like scanner and handset data, generally, data logged from voice and data calls is stored in separate attributes, and KPIs and statistics are typically based on one type or the other. However, for clarity it is generally advisable to separate the data into different logical devices. This avoids any risk of combining data inappropriately and thereby creating invalid KPIs. All of the drive test scenarios that we have considered so far involve a single drive test unit (that is, one vehicle plus logging equipment). When there are multiple drive test units driving different routes on the same days, there is no reason why you should not combine data logged for the same purpose in the different drive test units. For example, it would typically be valid to combine short call data collected by different drive test units on the same days in different parts of a city or state. However, if the data was logged for different purposes (such as the short and long call data described above), you should generally separate it into different logical devices, for the reasons explained earlier. Sometimes you may want to base optimization and troubleshooting work on benchmarking data, which is data that has been collected from several different operators' networks simultaneously in order that the KPIs from the various networks can be compared. In this scenario, you would be interested in the data from your own network only. When Spotlight is to be used for this purpose, provided all of the data for that network was logged for the same purpose, you would normally store it in one device. However, you need to create a suitable filter for the device (as described below) in order to exclude all of the data from the other networks.

11.2.2 Adding a device
When you create a new project template, by default, Spotlight creates a single all-purpose device that has no filter. If you want to separate data into multiple devices, you must specify a filter for each one. The filter identifies the data streams that are to be loaded into that device. For example, suppose you define two devices, A and B. When you subsequently select data files to load into the project, data streams that match the filter for device A will be loaded into device A, data streams that match the filter for device B will be loaded into device B, and data streams that do not match either filter will not be loaded. Note that data streams that match the filter for device A and B will be loaded into both devices.

www.actix.com

Actix Spotlight Desktop User Guide November 2012

144

1

You create a new device by clicking the Add Device button, which opens this dialog:

22 Device Name - This is used to identify the device wherever it is used, so try to make the name meaningful. 23 Filter - This defines a single sequence of characters that must be present in the stream's long name in order for it to be loaded into this device. The long name is composed of the stream name preceded by the file name like this: FileName:StreamName. 24 Import From File - You can use this button to browse to a typical log file that will be loaded into the project. When you select the file, Spotlight lists the name of every data stream that it contains. When you select a name in the list, Spotlight inserts the stream name into the Filter box above. Typically, you would then edit it in the Filter box, in order to make the filter more generally applicable. 25 When you are ready, click Add to add the device to the project template.

www.actix.com

Actix Spotlight Desktop User Guide November 2012

145

11.2.3 More on device filters
Setting up good device filters takes some thought. Typically, you would use the Import from File button on several of the log files that you want to use in the project, in order to examine the pattern of their stream names. Some stream names include the handset's identifier, such as the mobile identification number (MIN) or phone number, and sometimes you can use this as the filter. For example, suppose you are setting up a project template that will be used for troubleshooting your network's data from a benchmarking study, in which five handsets were used to log data from five different networks in one drive test unit (vehicle). If the stream names include the phone numbers, you could base the filter on the phone number of the handset that was attached to your network. However, suppose you have several drive test units logging the data and you want to combine your network data from all of the units. Using the phone numbers will not achieve this, because even if everything else is the same in each drive test unit, the phone numbers will always be different. Typically, the logging equipment has a number of slots into which the handsets are plugged. Sometimes the slots can be configured with a label (such as the name of the network), and these are generally incorporated into the stream names. If the slots in each drive test unit are given the same labels in all of the drive test units, you could base the filter on the label. Alternatively, the slots might have an identifying number, which often appears in parentheses in the stream name, such as (0), (1), etc. These are often used successfully as filters. However, for this to work correctly, the handsets for your network would need to be in the same slot in all of the drive tests units. When filtering on the stream name part of the stream, long names cannot provide the results you require - you might need to consider filtering on the file name part of the long name. If necessary, you could rename the files. For example, consider a benchmarking study, in which the data for each network is written out to different files. You could include the name or ID of the network in the log file names and then base the stream name filter on the network name or ID. If necessary, you might need to rename the files manually or using a script. This technique can be particularly useful when working with TEMS data.

Click Next to go the next page.

www.actix.com

Actix Spotlight Desktop User Guide November 2012

146

11.3 Step 3: Choose KPIs and Reports
The third step in creating a new Spotlight project template involves selecting the KPIs and reports that you want to include in the project. Spotlight lists all of the KPIs and reports that are available.

1

For performance reasons, select only those KPIs and reports that are relevant for the tasks you plan to perform and the data you plan to load into the projects based on this template. For example, if you are planning to load only GSM voice data, deselect all of the KPIs and reports that do not relate to GSM voice calls.

26 Click Next to go to the next page.

www.actix.com

Actix Spotlight Desktop User Guide November 2012

147

11.4 Step 4: Choose Attributes
The fourth step in creating a new Spotlight project template involves selecting the attributes that you want to include in the project and defining the binning settings.

One of the attributes is highlighted in red to indicate that it has been chosen from the Attribute Picker panel.

www.actix.com

Contains the scanner attributes. if you are adding a UMTS scanner attribute.This lists the attributes and binned queries that are in the binned data query that is selected on the left side and any additional attributes that you have added using the Attribute Picker on the right side. etc. indicating that you can remove them. because they are required for the features that are associated with the selected KPIs and reports. Typically each technology has two or more binned data queries.com  .) Attribute Picker . Spotlight automatically adds a separate item to the list of attributes for each possible index position (provided there are less than 32 possible index positions). The additional attributes are highlighted. For example. when you select an array attribute. for UMTS there are binned data queries as follows: ▫ UMTS UE BinnedData . you can add additional attributes using the Attribute Picker on the right side.  Attributes .actix. UMTS UE SectorHandle BinnedData . Do not add attributes to this query. rather than expandable items.This is a special query that is used internally. ▫ ▫ ▫ If you want to add additional attributes. Each of these contains a number of attributes and binned queries that are used for display on the map. Select any attributes that you want to include. the attributes and binned queries it contains are listed in the central Attributes panel.Contains the handset attributes. and is the main query used in the Event Explorer Drill Down pages. When you select a binned data query. It is also used to populate the Radio Network Neighbor List analysis pages.4. and is used in the Radio Network Cell Coverage and Cell Pilot Pollution pages when the user has selected a 'scanner' Analysis. select the appropriate binned data query to add them to. select the UMTS Scanner BinnedData query. You can then delete any index positions that you www. (You do this by selecting the attribute and clicking Remove Attribute.This is a special query that is used internally. Note that array attributes are shown in the tree view as individual items. It is also used to populate the Radio Network Cell Coverage and Cell Pilot Pollution pages when the user has selected a 'handset' Analysis.Actix Spotlight Desktop User Guide November 2012 148 11. What happens when you select an array attribute depends on the internal structure of the binned data query that is selected: ▫ Generally.This is a tree view that lists all of the possible attributes. You cannot remove these. UMTS Scanner BinnedData . Queries that have Sector Handle in their name are for internal use and you should not add any attributes to them. For example.1 Choose Attributes The top part of this page has three panels:  Binned Data Queries . However. Make sure you add the attributes to the appropriate binned data query as described above. Do not add attributes to this query.This lists the binned data queries that relate to the KPIs and reports that you selected in Step 3. UMTS Scanner SectorHandle BinnedData .

it is considerably slower. you can www. a simple average operation is performed.The possible units are meters and arc seconds. 11. For example. In addition when working with very large volumes of data. The averaging operation that is performed is determined by the internal attribute definition. changing the binning settings in the Preferences dialog does not affect data loaded into the Spotlight repository. You must choose the unit that matches the projection system that you are using. ▫ However. Note that once the project is created. Spotlight adds it to the list of attributes as a single item (using the array indexer syntax) and automatically includes every index position for which there is data. This means that in bins that the drive test(s) passed through more than once. For most attributes. If the data will be displayed on vector-based maps. For example. You cannot add array attributes that have 32 or more possible index positions. De-select this option if you want the results from all of the drives to be aggregated together. Units of measurement . particularly when displaying data on the map.2 Binning The binning settings control how the device's binned data is stored in the repository and how it is subsequently displayed on the map and the other binned data views.Actix Spotlight Desktop User Guide November 2012 149 do not want to use. See Fast Bin Aggregation in the online help for more information. you might want to delete all but the first three or four index positions.Select this option if you want to use the fast bin aggregation method (this is recommended). Note that the fast binning option detailed below creates more compact databases and avoids problems with the limit to the number of "subselects" documented in the linked topic. for a "Top n" attribute.com  .4. Note Although Spotlight can handle a considerable number of attributes. Although this is technically more accurate. This has the effect of smoothing the data and reducing the number of rows or data points that would otherwise be stored in the database and subsequently displayed. which sorts the raw data values into a geographical grid and then performs an averaging operation to produce a single value for each square in the grid (sometimes call a bin).actix. there are limits imposed by the technologies that underlie the repository technology.) Spotlight always uses the location binning mechanism. but some use other operations. the increased accuracy is likely to be of limited value in practice. for some binned data queries (such as the GSM Scanner BinnedData query). such as the mode or count. These limits are documented in detail in the Repository Manager section. (However. when you select an array attribute. the results from the last drive will be displayed. The binning options are:  Fast binning . the binning settings cannot be changed. it does affect the drilldown data and any Spotlight data that you have loaded into Analyzer Classic.

The X axis corresponds to longitude and the Y axis to latitude. all of the location grids are the same.  X and Y bin size . using this formula shows that a Y axis bin size of 100 meters is approximately three arc seconds.actix. the formula for converting between meters and arc seconds for the X axis is more complicated. For the Y axis. if the data is to be displayed on raster maps. However. by default. You do this by specifying an offset for either or both of the coordinates in the X origin and/or Y origin text boxes. the approximate size in arc seconds can be calculated from a size in meters using the following formula: Where REarth is the radius of the earth (approximately 6. This has the advantage that. www. The default sizes are 3 arc seconds and 50 meters.By default. you should generally choose the projection system used in those maps and the correct units for that system. which is used by GPS.  X and Y origin . because it depends on the radius of the earth at that latitude. the starting point for the geographical grid is the false origin (0. However.400 kilometers at the equator). See Map Projections in the online help for an overview of the issues. You must specify the offset in the same units as you used to define the size of the bins (and this must correspond to the measurement system used by the projection system). However. which is the World Geodetic System 1984 (WGS 84) projection system.Actix Spotlight Desktop User Guide November 2012 150 generally use arc seconds and the default projection system. you want to align the grid with one used in another system. for example. sometimes you may want to move the start point because.com .These define the dimensions of the squares in the geographical grid. Note that using larger bin sizes reduces the size of the database and improves performance. The sizes must be specified in the appropriate units for the projection system. For example. 0) defined for the selected projection system.

you can choose to allow filtering by Cluster Name and Clutter Type. you are returned to the new project page. You need to select the appropriate zone for the area in which the data was collected. See the online help section ED79 UTM Zone Lookup for more information. To enable filtering by region. If these options are enabled.Actix Spotlight Desktop User Guide November 2012 151  Projection . www. For the Regional Filters.Select the projection system that you want to use. When you click Done. you can activate or modify them by clicking on the Global Filters link in the top right of an analysis page.actix.  11. ED79 UTM is a generic map projection system that divides the globe up into a number of zones. but you can use one of the ED79 UTM (Universal Transverse Mercator) system options.5 Step 5: Choose Global Filters The fifth step in creating a new Spotlight project template involves choosing whether to enable File/Stream. created a new Spotlight Template and on the Filtering page checked the relevant region types under Region Filters. There is no default option for meters.com . The options in the drop-down list are the projection systems that are supported directly by Analyzer and that use the units of measurement selected above. Note Regional filtering option is not shown in the above example. Click Next to go to the next page. Time and regional filtering in the project (as well as the Device filtering enabled in Step 2). you need to have already defined the regions. where the new template appears in the list of project templates. The Default option for arc seconds corresponds to the WGS 84 projection system.

28 If the service does not restart. from the toolbar. which associates to itself a number of image file formats. 27 In the table of services. Services. select Control Panel. and from the Tools menu select File Types. Open Picture Manager. click on the Start Service button. go back to Spotlight and attempt to reload your project.bmp) is left unchecked (that is. locate the 'SQL Server (ACTIXSQLEXPRESS)' row. If the Status is blank. 12.com . www. from the toolbar. click on the Resume Service button. following these steps: 1 From the Windows Start menu. you will need to uninstall and reinstall Actix Spotlight. ▫ ▫ ▫ If the Status is 'Paused'. Administrative Tools.1 No repository detected Spotlight was unable to find your project database. Ensure that your MS SQL service is active and try to start your project again.actix. Ensure that the box for Windows Bitmap (.Actix Spotlight Desktop User Guide November 2012 152 12 Troubleshooting Spotlight 12. empty). you will need to create a new project and reload the data. If you changed your license after creating the project.2 The maps in your report are empty This is an issue cause by Microsoft Picture Manager. If the Status is 'Started'.

Actix Spotlight Desktop User Guide November 2012 153 13 Appendix A: Cell Site Parameters 13. Used in CDMA Toolkit calculations. For information only. www. Numeric identifier for the Site.3 etc. or a combination of site numbers Azimuth Beamwidth Purpose Text description of the Site for display on map. For information only. Azimuth Beamwidth CDMA_Cell CDMA_Cell Orients the sector icons on the map.1 CDMA Cell Site Parameters Imported Parameter Site Name Site Number Latitude Longitude Sector Number Analyzer Group CDMA_Site CDMA_Site CDMA_Site CDMA_Site CDMA_Cell Analyzer Name SiteName SiteID SiteLatitude SiteLongitude Sector ID Can be 1. Locates Site icons on the map. lines to neighbor cells and to color sectors/sites on maps to reflect PN planning. For information only. For information only. For information only. Sector-specific information useful for display on maps.actix. Base station power. Mobile Country Code. For information only. For information only.com PN Offset CDMA_Cell PN Base Station Power* Mobile Country Code* System Identity* Network Identity* Broadcast Identity* PctPilot* PctTraffic* PctPaging* CDMA_Cell CDMA_Cell EIRP MCC CDMA_Cell CDMA_Cell CDMA_Cell CDMA_Cell CDMA_Cell CDMA_Cell SID NID BID PctPilot PctTraffic PctPaging . Locates Site icons on the map. used in CDMA Toolkit calculations. Governs the shape of the sector 'wedge' on the map to reflect the beamwidth of the antenna deployed at the site.2.

Locates Site icons on map. Locates Site icons on map. band. Used to color sectors on the map by a custom integer field. 13. purpose or status) that the site belongs to. Used to color sectors on the map by a custom integer field. Used as the linking column to associate the GSM_Site and GSM_Cell rows.2 GSM / GPRS / EDGE Cell Site Parameters Imported Parameter Site Name Site Number Analyzer Group GSM_Site GSM_Site Analyzer Name SiteName SiteID Purpose Text description of the Site for display on map. CDMA_Cell SRCH_WIN_N List of neighbors* CDMA_Cell CDMANeighborList Sector Display – Wildcard* Sector Display – Wildcard* Sector Display – Wildcard* Layer type* CDMA_Cell Face_Display CDMA_Cell Azimuth_Display CDMA_Cell Phase_Display CDMA_Cell Layer_type *Optional.actix.Actix Spotlight Desktop User Guide November 2012 154 Imported Parameter PctSync* Active Set Search Window Setting* Neighbor Set Search Setting* Analyzer Group CDMA_Cell CDMA_Cell Analyzer Name PctSync SRCH_WIN_A Purpose For information only. Used to color sectors on the map by a custom integer field. Used in Analyzer’s CDMA Toolkit calculations to compare current search window settings with those suggested by Analyzer. Used for multiple cell layers. www. Text that specifies which cell layer (for example. Used in Analyzer’s CDMA Toolkit calculations to compare current search window settings with those suggested by Analyzer. Numeric identifier for the Site. by technology. Used in Analyzer’s CDMA Toolkit calculations to compare current search window settings with those suggested by Analyzer.com Latitude Longitude GSM_Site GSM_Site Latitude Longitude .

actix. Governs the radius of the sector 'wedge' icon to reflect the beamwidth of antenna deployed at the sector. by technology. comprising of a concatenation of the NCC and BCC values.3 LTE Cell Site Parameters Imported Parameter Site Name Site Number Latitude Analyzer Group LTE_Site LTE_Site LTE_Site Analyzer Name Site_Name SiteID Latitude Purpose Text description of the Site for display on map. or a combination of site numbers Azimuth Beamwith Purpose Sector-specific ID information useful for display on maps. Base Station Identity Code. Azimuth Beamwidth GSM_Cell GSM_Cell Orients the sector icons on the map. Base Station Power Broadcast Control Channel Mobile Network Code Mobile Color Code Location Area Code Cell ID value Base Station Identity Code Layer type GSM_Cell GSM_Cell EIRP BCCH GSM_Cell MNC Mobile Network Code. etc.com . GSM_Cell Layer_type 13. purpose or status) that the site belongs to.3. band. Numeric identifier for the site.Actix Spotlight Desktop User Guide November 2012 155 Imported Parameter Sector Number Analyzer Group GSM_Cell Analyzer Name SectorID Can be 1.2. Base Station Power. GSM_Cell GSM_Cell GSM_Cell GSM_Cell MCC LAC CI BSIC Mobile Color Code. www. Broadcast Control Channel. Cell ID value. Locates site icons on map. Used for multiple cell layers. Location Area Code. Text that specifies which cell layer (for example.

The fields DL_EARFCN and PCI must be present to calculate lines to cells. Governs the shape of the sector “wedge” icon to reflect the beamwidth of antenna deployed at the site. Locates site icons on map. Locates site icons on map.actix.4 UMTS / HSPA+ Cell Site Parameters Imported Parameter Site Name Site Number Latitude Longitude Sector Number Analyzer Group UMTS_Site UMTS_Site UMTS_Site UMTS_Site UMTS_Cell Analyzer Name SiteName SiteID Latitude Longitude Sector_ID Purpose Text description of the Site for display on map. The fields DL_EARFCN and PCI must be present to calculate lines to cells. National Domain Code – for informational purposes only.Actix Spotlight Desktop User Guide November 2012 156 Imported Parameter Longitude Sector Number Azimuth Beamwidth Analyzer Group LTE_Site LTE_Cell Analyzer Name Longitude Sector_ID Purpose Locates site icons on map.com . Numeric identifier for the site. Sector-specific information useful for display on maps (can be alpha or numeric) Orients the sector icons on the map. Equivalent Isotropic Radiated Power – for informational purposes only. Mobile Country Code – for informational purposes only. The downlink EARFCN of the cell. Sector-specific information useful for display on maps (can be alpha or numeric) www. LTE_Cell LTE_Cell MCC MNC 13. The physical layer cell identity (previously named L1_CID). LTE_Cell LTE_Cell Azimuth Beamwidth EIRP* LTE_Cell EIRP Downlink EARFCN LTE_Cell DL_EARFCN Layer1 Cell Identity LTE_Cell PCI MCC* MNC* * Optional.

Configurable text field that specifies which cell layer (for example. Equivalent Isotropic Radiated Power – for informational purposes only. Used for cell site identification and to calculate lines to cells. Used to define a pre-defined neighbor list for each cell.com . Used for multiple cell layers. Cell Identity – for informational purposes only. www. band or status) the site belongs to. SC EIRP* UMTS_Cell UMTS_Cell SC EIRP MCC* MNC* LAC* CI* Neighbor List* UMTS_Cell UMTS_Cell UMTS_Cell UMTS_Cell UMTS_Cell MCC MNC LAC CI WCDMANeighborList Layer Type* UMTS_Cell LayerType * Optional. Governs the shape of the sector “wedge” icon to reflect the beamwidth of antenna deployed at the site.actix. Used during neighbor list recommendations analysis.Actix Spotlight Desktop User Guide November 2012 157 Imported Parameter Azimuth Beamwidth Analyzer Group UMTS_Cell UMTS_Cell Analyzer Name Azimuth Beamwidth Purpose Orients the sector icons on the map. National Domain Code – for informational purposes only. Mobile Country Code – for informational purposes only. by technology. Location Area Code – for informational purposes only.

www. This is a good place to start using Spotlight.1 Report tab This tab provides summary information on the loaded data. 14.1.Actix Spotlight Desktop User Guide November 2012 158 14 Appendix B: Spotlight reports 14. as the report indicates which thresholds have been passed and which have failed.actix. Related tables provide additional information to let you decide where to go to follow up any problems.1 CDMA Spotlight Report This report provides information on unfiltered CDMA data within the current project database.com .

www.2 Radio Link tab This tab provides tables showing radio link information.Actix Spotlight Desktop User Guide November 2012 159 14.1.com .actix.

Actix Spotlight Desktop User Guide November 2012 160 14. www.actix.3 Map tab This tab provides maps for dropped calls.1. failed calls and forward FER.com .

actix.2 EVDO Spotlight Report This report provides information on unfiltered EVDO data within the current project database.Actix Spotlight Desktop User Guide November 2012 161 14. as the report indicates which thresholds have been passed and which have failed. Related tables provide additional information to let you decide where to go to follow up any problems. This is a good place to start using Spotlight.1 Report tab www. 14.com .2.

2 Map tab www.actix.com .2.Actix Spotlight Desktop User Guide November 2012 162 14.

actix.3 Air Interface Quality Analysis tab www.com .Actix Spotlight Desktop User Guide November 2012 163 14.2.

com .actix.2.Actix Spotlight Desktop User Guide November 2012 164 14.4 DL/UL Throughput Metrics tab www.

Related tables provide additional information so you can decide how to follow up any problems. www. This is a good place to start using Spotlight.actix.com .3 EVDO Rev A Spotlight Report This report provides information on unfiltered EVDO Rev A data within the current project database.Actix Spotlight Desktop User Guide November 2012 165 14. as the report indicates which thresholds have been passed and which have failed.

3.actix.Actix Spotlight Desktop User Guide November 2012 166 14.1 Overview Map www.com .

3.3.actix.com .2 Main 14.Actix Spotlight Desktop User Guide November 2012 167 14.3 Connection Details www.

4 RF 14.com .3.actix.3.Actix Spotlight Desktop User Guide November 2012 168 14.5 Throughputs www.

actix.3.com .Actix Spotlight Desktop User Guide November 2012 169 14.6 Per Flow Throughputs www.

Actix Spotlight Desktop User Guide November 2012 170 14. Related tables provide additional information to let you decide where to go to follow up any problems.1 Report www.4. 14.actix.4 GSM Spotlight Report This report provides information on unfiltered GSM data within the current project database. as the report indicates which thresholds have been passed and which have failed.com . This is a good place to start using Spotlight.

actix.4.com .2 File Overview www.Actix Spotlight Desktop User Guide November 2012 171 14.

com .4.Actix Spotlight Desktop User Guide November 2012 172 14.actix.3 Overview Map www.

4 Radio www.Actix Spotlight Desktop User Guide November 2012 173 14.4.actix.com .

Actix Spotlight Desktop User Guide November 2012 174 14.4.actix.5 CD Domain www.com .

Related tables provide additional information to let you decide where to go to follow up any problems.actix. 14.5.com .Actix Spotlight Desktop User Guide November 2012 175 14.5 HSPA Spotlight Report This report provides information on unfiltered HSPA data within the current project database. as the report indicates which thresholds have been passed and which have failed.1 Report www. This is a good place to start using Spotlight.

5.actix.com .2 Overview Map www.Actix Spotlight Desktop User Guide November 2012 176 14.

com .Actix Spotlight Desktop User Guide November 2012 177 14. the tables report the following statistics for CQI:  Mean  Mode www.actix. In addition.3 Radio The PDF and CDF of ALL the actual CQI samples present in the logs are provided.5.

Actix Spotlight Desktop User Guide November 2012 178    Median Maximum Minimum   Total # samples 95% Percentile The HARQ statistics section shows the distribution between ACK.com .4 HS mobility www. NACK and DTX samples of all the HARQ processes recorded. Details per call can be accessed at the bottom of the page by clicking on the link below the table. 14.5.actix.

5.com .5 Channel Usage www.actix.Actix Spotlight Desktop User Guide November 2012 179 14.

actix. 14. This is a good place to start using Spotlight. Related tables provide additional information to let you decide where to go to follow up any problems. as the report indicates which thresholds have been passed and which have failed.6 UMTS Spotlight Report This report provides information on unfiltered UMTS data within the current project database.com .1 Report www.Actix Spotlight Desktop User Guide November 2012 180 14.6.

com .Actix Spotlight Desktop User Guide November 2012 181 14.2 Overview www.actix.6.

actix.3 Overview Map www.com .6.Actix Spotlight Desktop User Guide November 2012 182 14.

actix.com .6.Actix Spotlight Desktop User Guide November 2012 183 14.4 Radio www.

6.actix.5 CS Domain and PS Domain www.com .Actix Spotlight Desktop User Guide November 2012 184 14.

1.Actix Spotlight Desktop User Guide November 2012 185 15 Appendix C: CDMA thresholds. Display Thresholds command.2. Default is 5000m. good Rx problems cases less than the threshold.1 CDMA_AvgForwardFER This threshold is used for diagnosing areas of poor quality.2 CDMA_EcIoCombinedThreshold This threshold is used in conjunction with Mobile Rx Power and Mobile Tx Power Thresholds to determine the diagnosis for the dropped call. KPIs and diagnoses 15.1 Spotlight Thresholds 15. if there is no Max_ServerDist information in the cellref and indicates the maximum serving distance (in meters) a cell should serve.1.3 CDMA_ImportantIssue_ExcessInterference This threshold is used for filtering out files that have percentage of excess interference cases less than the threshold. Recommended value is 2.2. diagnosis and display of data in Spotlight.2.com .2 CDMA / Coverage 15. www. Values should vary between -16 and -12 dB.1.1.5 CDMA_ImportantIssue_FwdLinkProblem This threshold is used to filter out the display of data in the CDMA Dashboard that have percentage of forward link problems cases less than the threshold. Recommended value is -12 dB. Recommended value is 2. 15. It is important to set your threshold before loading the data because it will affect the analysis. 15.1. Recommended value is 2.2.1. Recommended value is 2. 15.1 SL_Overspill_Dist_Threshold This threshold is used. To modify the value. 15.1. simply click on the associated number and type in the new value. failed call and voice call with poor quality. 15. 15.2.1.1 CDMA thresholds You can modify threshold values for event detection using the Tools.1.actix. high Tx.4 CDMA_ImportantIssue_ExternalInterference This threshold is used to filter out the display of data in the CDMA Dashboard that have percentage of bad EcIo.

2.1.9 CDMA_ImportantIssue_RevLinkProblem This threshold is used to filter out the display of data in the CDMA Dashboard that have percentage of rev link problems cases less than the threshold.1.2.13 CDMA_MobileTxPowerThreshold This threshold is used in conjunction with EcIo and Mobile Rx Power Thresholds to determine the diagnosis for the dropped call. 15. The recommended value is 3 and values should lie between 2 and 4. failed call and voice call with poor quality.2.Actix Spotlight Desktop User Guide November 2012 186 15.6 CDMA_ImportantIssue_LowRX This threshold is used to filter out the display of data in the CDMA Dashboard that have percentage of low rx problems cases less than the threshold.2.1. 15.1. 15. Recommended value is 2. Recommended value is -80 dBm.2.1.com .1.2.2. Recommended value is -14 dB. Recommended value is 2.2. failed call and voice call with poor quality.8 CDMA_ImportantIssue_PoorQuality This threshold is used to filter out the display of data in the CDMA Dashboard that have percentage of calls with poor quality cases less than the threshold. Values should lie between -10 and -18 dB. 15.2.1.2. Default is 23. Recommended value is 5 dBm.10 CDMA_MobileRxPowerThreshold This threshold is used in conjunction with EcIo and Mobile Tx Power Thresholds to determine the diagnosis for the dropped call. Recommended value is 2.7 CDMA_ImportantIssue_PoorCoverage This threshold is used for filtering out files that have percentage of poor coverage cases less than the threshold. 15.11 CDMA_MobileTxPowerMinFilterThreshold This threshold is used in conjunction with Mobile Tx Power Max Threshold to filter out messages when the transmitter is disabled due to high FFER. Default is -30. 15.1.actix. 15.1.15 CDMA_PilotPollutionThreshold This threshold alerts the user of pilot pollution when the signal level falls below this threshold.12 CDMA_MobileTxPowerMaxFilterThreshold This threshold is used in conjunction with Mobile Tx Power Min Threshold to filter out messages when the transmitter is disabled due to high FFER. Values should lie between 0 and 10 dBm. Values should vary between -75 and 90 dBm.14 CDMA_PilotPollution_Count_Threshold This is the absolute number of pilots (with Ec/Ios above CDMA_PilotPollutionThreshold) required to trigger a pilot pollution event. 15. www. Recommended value is 2.1. 15.

2 CDMA_EVDO_TooManyActivePNsThreshold In calculating "Too Many Servers".1. Default is 0.1. it will be flagged as accepted and will show up as a green tick mark in the KPI table. 15.1. 15. 0 = CDMA Server Key analysis is turned off to improve file load speeds.5. Default is 0.2 EVT_CDMANeighborListIssueDetect 1 = Turns on the CDMA Neighbor List Issue Detect event diagram for CDMA Troubleshooter. 15. www. when 4 or more pilots (including the best server) are within the threshold value in dB of the best server.Actix Spotlight Desktop User Guide November 2012 187 15. 15.1. Default is 0. If the resulting KPI is equal or less than this value.4.1.1.4 UniqueNeighborList 1 = Turns on the unique neighbor list analysis for CDMA.1 CDMA_CallDropRate This threshold is used to determine the criterion for KPI acceptance in the Repository views. Default is 0. 0 = CDMA Important Issue analysis is turned off to improve file load speeds.1. it creates a "too many server" event. 0 = unique neighbor list analysis is turned off to improve file load speeds.4.4 CDMA / Other 15.4. If it is higher than this value. Recommended value is 5 dB and the minimum and the maximum should be around 1 and 10 dB. it will be flagged as failed and will show up as a red cross in the KPI table.1.1 EVT_CDMAImportantIssue 1 = Turns on the CDMA Important Issue Detect event diagram for CDMA Troubleshooter.3.1.1.3 EVT_CDMAServerKey 1 = Turns on the CDMA Server Key event diagram for CDMA Troubleshooter. 15.actix.3. Recommended value is 5 dB and the minimum and the maximum should be around 1 and 10 dB. The default value is 2%. 15. 0= CDMA Neighbor List Issue Detect analysis is turned off.1 CDMA_EcIoInterferenceThreshold Recommended value is -15 dBm.1.com . it creates a "too many server" event.3 CDMA_TooManyActivePNsThreshold In calculating "Too Many Servers".5 CDMA / Performance 15. The maximum should not be higher than 0 and minimum should not be lower than -25 dBm. 15. when 4 or more pilots (including the best server) are within the threshold value in dB of the best server. EVDO Troubleshooter. The Call Drop Rate should not exceed 2% of all successful calls in the busy hour.3.3.3 CDMA / Events 15.

it will be flagged as accepted and will show up as a green tick mark in the KPI table. If it is less than this value. If the resulting KPI is equal or in excess to this value.actix.1. Recommended value is 2000 ms. The Call Setup Success Rate should be in excess of 98% for most GSM networks in the busy hour. If it is less than this value.5.2 CDMA events in the Event Explorer The following events are displayed in the top table of the Event Explorer: # Call Attempts # Dropped Calls # Failed Calls # Excessive Setup These events are affected by the following thresholds: CDMA_AvgForwardFER CDMA_PilotPollution_Count_Threshold CDMA_PilotPollutionThreshold www.3 CDMA_CallSetupTime This threshold is used for determining calls with excessive setup time. 15.com . If the resulting KPI is equal or in excess to this value.5. it will be flagged as accepted and will show up as a green tick mark in the KPI table. it will be flagged as failed and will show up as a red cross in the KPI table. The default value is 98%.2 CDMA_CallSetupSuccessRate This threshold is used to determine the criterion for KPI acceptance in the Repository views.5.Actix Spotlight Desktop User Guide November 2012 188 15. 15. The Overall Success Rate should be in excess of 98% for most GSM networks in the busy hour.1.4 CDMA_OverAllSuccessRate This threshold is used to determine the criterion for KPI acceptance in the Repository views. 15.1. it will be flagged as failed and will show up as a red cross in the KPI table. The default value is 98%.

com .3 Dropped Call diagnosis for CDMA www.Actix Spotlight Desktop User Guide November 2012 189 15.actix.

com . High EcIo. FER > Average Forward FER threshold. Low EcIo. low MRx Power. low MRx Power. www. More investigation is needed. high MTx Power. high MRx Power. low MRx Power. high MTx Power. High EcIo.Actix Spotlight Desktop User Guide November 2012 190 Diagnosis Coverage Issue Excessive Interference Poor Coverage Reverse Link Problem External Interference Forward Link Problem Low Rx Signal Poor Quality Neighbor List Issue Pilot Pollution Other Condition and notes Evaluate the CDMA Important Issues parameter to identify the type of coverage issue present. Low EcIo. high MRx Power. high MTx Power. Low EcIo. Low EcIo. 4+ pilots have EcIo > CDMA_PilotPollutionThreshold. high MTx Power.actix. high MTx Power. high MRx Power. New originating PN (Sync PN) is not contained in the neighbor list of the serving cell. low MTx Power. Use other tools and views to refine your understanding of the problem.

1 8.0 24.1.7 -1.1 23.1 8. It is important to set your threshold before loading the data because it will affect the analysis. 16.1 5.2 0.8 28. The default value of 18 corresponds to ~10 dB.1.1.1 2.0 7.6 -5.0 27. Threshold Value 0 1 2 3 4 5 6 7 8 9 10 11 12 13 dB -9.2 HSUPA_SGI_Threshold This threshold is used to determine the minimum acceptable Serving Grant Index value.5 -8.4 -2.com .0 27.actix.0 18.0 15. diagnosis and display of data in Spotlight.0 14.0 13. 16.0 21.0 12.0 17.0 22.0 1.0 26.1 HSDPA_CQI_Threshold This threshold is used to determine the minimum acceptable Channel Quality Indicator value.1.9 4.1 Threshold Value 14 15 16 17 18 19 20 21 22 23 24 25 26 27 dB 6. To modify the value.0 16.9 9.9 11.5 -4.8 None N/Av www. The HSUPA SGI format group controls the exact mapping of the threshold values to dB values (shown below). Display Thresholds command.Actix Spotlight Desktop User Guide November 2012 191 16 Appendix D: Data Service Analysis thresholds 16.0 19.1 DSA thresholds You can modify threshold values for Data Service Analysis using the Tools.0 -6. simply click on the associated number and type in the new value. The default is 15.0 25.0 Threshold Value 28 29 30 31 32 33 34 35 36 37 38 63 dB 20.9 -1.1 2.

Actix Spotlight Desktop User Guide November 2012

192

16.1.2 Throughput thresholds
16.1.2.1 Absolute_ApplicationLowTput_DL_Threshold

This threshold is used to determine the minimum acceptable application throughput value for downlink for the Below Absolute Threshold KPI. The default value is 1000 kB/sec. 16.1.2.2 Absolute_ApplicationLowTput_UL_Threshold

This threshold is used to determine the minimum acceptable application throughput value for uplink for the Below Absolute Threshold KPI. The default value is 1000 kB/sec. 16.1.2.3 Application_LowTput_GPRS_DL_Threshold

This threshold is used to determine the minimum acceptable application throughput value for downlink in GPRS for the Below Composite Threshold KPI. The default value is 40 kB/sec. 16.1.2.4 Application_LowTput_GPRS_UL_Threshold

This threshold is used to determine the minimum acceptable application throughput value for uplink in GPRS for the Below Composite Threshold KPI. The default value is 10 kB/sec. 16.1.2.5 Application_LowTput_HSDPA_DL_Threshold

This threshold is used to determine the minimum acceptable application throughput value for downlink in HSDPA for the Below Composite Threshold KPI. The default value is 1000 kB/sec. 16.1.2.6 Application_LowTput_HSDPA_UL_Threshold

This threshold is used to determine the minimum acceptable application throughput value for uplink in HSDPA for the Below Composite Threshold KPI. The default value is 40 kB/sec. 16.1.2.7 Application_LowTput_HSPA_DL_Threshold

This threshold is used to determine the minimum acceptable application throughput value for downlink in HSPA for the Below Composite Threshold KPI. The default value is 1000 kB/sec. 16.1.2.8 Application_LowTput_HSPAPlus_DL_Threshold

This threshold is used to determine the minimum acceptable application throughput value for downlink in HSPA+ for the Below Composite Threshold KPI. The default value is 1000 kB/sec. 16.1.2.9 Application_LowTput_HSPAPlus_UL_Threshold

This threshold is used to determine the minimum acceptable application throughput value for uplink in HSPA+ for the Below Composite Threshold KPI. The default value is 600 kB/sec.

www.actix.com

Actix Spotlight Desktop User Guide November 2012

193

16.1.2.10 Application_LowTput_HSUPA_UL_Threshold This threshold is used to determine the minimum acceptable application throughput value for uplink in HSUPA for the Below Composite Threshold KPI. The default value is 600 kB/sec. 16.1.2.11 ApplicationLowTput_Idle_DL_Threshold This threshold is used to determine the minimum acceptable application threshold value for downlink in Idle mode for the Below Composite Threshold KPI. Default is the same as HSPA. Change this to correspond to the network that you are testing. 16.1.2.12 ApplicationLowTput_Idle_UL_Threshold This threshold is used to determine the minimum acceptable application threshold value for uplink in Idle mode for the Below Composite Threshold KPI. Default is the same as HSPA. Change this to correspond to the network that you are testing. 16.1.2.13 ApplicationLowTput_UMTS_DL_Threshold This threshold is used to determine the minimum acceptable application throughput value for downlink in UMTS for the Below Composite Threshold KPI. The default value is 200 kB/sec. 16.1.2.14 ApplicationLowTput_UMTS_UL_Threshold This threshold is used to determine the minimum acceptable application throughput value for uplink in UMTS for the Below Composite Threshold KPI. The default value is 40 kB/sec.

www.actix.com

Actix Spotlight Desktop User Guide November 2012

194

17 Appendix E: EGPRS KPIs and diagnoses
17.1 EGPRS thresholds
You can modify threshold values for event detection using the Tools, Display Thresholds command. It is important to set your threshold before loading the data because it will affect the analysis, diagnosis and display of data in Spotlight. To modify the value, simply click on the associated number and type in the new value.

17.1.1 EGPRS / Analysis
17.1.1.1 G_Cell_Reselect_Duration

This threshold determines the maximum time for a cell reselection. Any values above this threshold will be flagged as excessive high cell reselection time. Default is 15000ms. 17.1.1.2 G_Cell_Reselect_Time

This threshold determines the window during which cell reselections may take place. Any two reselections occurring within this threshold will be flagged as abnormally high cell reselections. Default is 15000ms. 17.1.1.3 G_RMAC_C_Value_Min

This threshold is used to determine the minimum acceptable C Value criterion. Typical values range from -80 to -95, though this is highly dependent on the coding scheme employed. Default is -85. 17.1.1.4 G_RMAC_CV_BEP_Max

This threshold is used to determine the minimum acceptable CV BEP parameter. Default is 4. 17.1.1.5 G_RMAC_DL_TS_Min

This threshold is used to determine the minimum acceptable timeslot allocation. Default is 2. 17.1.1.6 G_RMAC_MEAN_BEP_Max

This threshold is used to determine the minimum acceptable MEAN BEP parameter. Default is 25. 17.1.1.7 G_RMAC_Power_Reduction_Max

This threshold is used to determine the maximum acceptable Power reduction values on the RMAC interface. Default is 2. 17.1.1.8 G_RMAC_Sign_Var_Min

This threshold is used to determine the minimum acceptable signal quality variation as denoted by the RMAC_Sign_Var attribute. Default is 24.
www.actix.com

Actix Spotlight Desktop User Guide November 2012

195

17.1.1.9

G_RMAC_TAI_Max

This threshold is used to determine the maximum acceptable TAI value. Default is 10.

17.1.2 EGPRS / Events
17.1.2.1 G_T3240_RAUTimer

This timer is used to determine the time (in ms) the system will wait for GPRS MM Routing Area Update Request messages to be answered with a GPRS MM Routing Area Update Accept before registering a Routing Area Update Failure. Default is 15000ms. 17.1.2.2 G_T3310_AttachTimer

This timer is used to determine the time (in ms) the system will wait for GPRS MM Attach Request messages to be answered with a GPRS MM Attach Accept before registering an Attach Failure. Default is 15000ms. 17.1.2.3 G_T3321_DetachTimer

This timer is used to determine the time (in ms) the system will wait for GPRS MM Detach Request messages to be answered with a GPRS MM Detach Accept before registering an Detach Failure. Default is 15000ms. 17.1.2.4 G_T3380_PDPActTimer

This timer is used to determine the time (in ms) the system will wait for GPRS SM Activate PDP Context Request messages to be answered with a GPRS SM Activate PDP Context Accept before registering a PDP Context Activation Failure. Default is 8000ms.

17.1.3 EGPRS / Spotlight
17.1.3.1 EGPRS_Duration_Period

This threshold is used to determine the period over which the minimum acceptable throughput value for RLC / LLC are evaluated in EGPRS. Default is 15000ms. 17.1.3.2 EGPRS_LLC_DL_Min

This threshold is used to determine the minimum acceptable throughput value for LLC downlink in EGPRS. This factor is highly dependent on the typical allocation of static / dynamic pdTCHs in your network. Default is 5. 17.1.3.3 EGPRS_LLC_UL_Min

This threshold is used to determine the minimum acceptable throughput value for LLC uplink in EGPRS. This factor is highly dependent on the typical allocation of static / dynamic pdTCHs in your network. Default is 1. 17.1.3.4 EGPRS_RLC_DL_Min

This threshold is used to determine the minimum acceptable throughput value for RLC downlink in EGPRS. This factor is highly dependent on the typical allocation of static / dynamic pdTCHs in your network. Default is 10.
www.actix.com

Actix Spotlight Desktop User Guide November 2012

196

17.1.3.5

EGPRS_RLC_UL_Min

This threshold is used to determine the minimum acceptable throughput value for RLC uplink in EGPRS. This factor is highly dependent on the typical allocation of static / dynamic pdTCHs in your network. Default is 2. 17.1.3.6 GPRS_Duration_Period

This threshold is used to determine the period over which the minimum acceptable throughput value for RLC / LLC are evaluated in GPRS. Default is 15000ms. 17.1.3.7 GPRS_LLC_DL_Min

This threshold is used to determine the minimum acceptable throughput value for LLC downlink in GPRS. This factor is highly dependent on the typical allocation of static / dynamic pdTCHs in your network. Default is 5. 17.1.3.8 GPRS_LLC_UL_Min

This threshold is used to determine the minimum acceptable throughput value for LLC uplink in GPRS. This factor is highly dependent on the typical allocation of static / dynamic pdTCHs in your network. Default is 1. 17.1.3.9 GPRS_RLC_DL_Min

This threshold is used to determine the minimum acceptable throughput value for RLC downlink in GPRS. This factor is highly dependent on the typical allocation of static / dynamic pdTCHs in your network. Default is 10. 17.1.3.10 GPRS_RLC_UL_Min This threshold is used to determine the minimum acceptable throughput value for RLC uplink in GPRS. This factor is highly dependent on the typical allocation of static / dynamic pdTCHs in your network. Default is 2.

17.2 EGPRS events in the Event Explorer
TASK Failure Low Throughput High Cell Reselection Long Cell Reselection RAU Failure (10 second window up to the event) Where time - default(prev_time_where(x), 0) > 5000 and GPRS_RAU_Reject or GPRS_RAU_Failure or GPRS_RAU_Aborted or TEMSEvent_GPRS_RAU_Failure or GPRS_Events==13
www.actix.com

Actix Spotlight Desktop User Guide November 2012 197 or GPRS_Events==14 or GPRS_Events==15 Attach Failure (10 second window up to the event) Where time .actix. 0) > 5000 and GPRS_Attach_Reject or GPRS_Attach_Failure or GPRS_Attach_Aborted or TEMSEvent_GPRS_Attach_Failure or TEMSEvent_GPRS_Attach_Aborted or GPRS_Events==8 or GPRS_Events==9 or GPRS_Events==10 PDP Context Activation Failure (10 second window up to the event) Where time .default(prev_time_where(x). 0) > 5000 and GPRS_PDPContextAct_Reject or GPRS_PDPContextAct_Failure or GPRS_PDPContextAct_Aborted or TEMSEvent_GPRS_PDPContextActivation_Failure or GPRS_Events==2 or GPRS_Events==3 or GPRS_Events==4 www.default(prev_time_where(x).com .

3 EGPRS diagnoses www.Actix Spotlight Desktop User Guide November 2012 198 17.actix.com .

0) >= G_RMAC_Power_Reduction_Max default(GPRS_DL_Timeslot_Numbers_Num. 0)) < 2] > 0 where n = 0 to 5 AND default(RMAC_C_Value. 31) <= G_RMAC_MEAN_BEP_Max + default(ServRxQualSub. 0) >= G_RxQualSub_Max + default(RMAC_8PSK_MEAN_BEP. 0) >= G_RMAC_Sign_Var_Min + default(RMAC_8PSK_CV_BEP. 0) >= G_RMAC_TAI_Max The 'default' function means 'use the first value in brackets if possible. www. -75) <= G_RMAC_C_Value_Min default(RMAC_Sign_Var. 7) <= G_RMAC_CV_BEP_Max + default(RMAC_GMSK_CV_BEP. 3) <= G_RMAC_DL_TS_Min + default(RMAC_DL_NumTimeslots_Used_Actual.Actix Spotlight Desktop User Guide November 2012 199 Diagnosis Poor Radio Conditions Rapidly Changing Radio Conditions Condition and notes default(RMAC_C_Value. otherwise use the second value'.default(NborBCCH[n]. 0) >= G_RxQualSub_Max >0 default(RMAC_Power_Reduction. 7) <= G_RMAC_CV_BEP_Max >0 default(RMAC_RxQual.com .actix. -110) > G_RxLevSub_Min Interference Excessive Power Reduction Low bandwidth allocation Co/Adjacent Channel allocations between neighbors Distant Serving Cell default(RMAC_TimingAdvanceIndex. 3) <= G_RMAC_DL_TS_Min >0 Σ[abs(ServBCCH . 31) <= G_RMAC_MEAN_BEP_Max + default(RMAC_GMSK_Mean_BEP.

1 EVDO / Coverage 18. Recommended value is -80 dBm.1. 18.5 CDMA_EVDO_PilotPollutionThreshold In calculating pilot pollution. Default is 3.1 EVDO thresholds You can modify threshold values for event detection using the Tools. 18. 18.Actix Spotlight Desktop User Guide November 2012 200 18 Appendix F: EVDO KPIs and diagnoses 18.4 CDMA_EVDO_PilotPollution_Count_Threshold This is the absolute number of pilots (with Ec/Io above CDMA_EVDO_PilotPollutionThreshold) required to trigger a pilot pollution event.1 Average_PER_Threshold This threshold is used to indicate a pass threshold for the Average PER (%) for cluster acceptance. It is important to set your threshold before loading the data because it will affect the analysis.1.3 CDMA_EVDO_MobileRxPowerThreshold This threshold is used in conjunction with EcIo and Mobile Tx Power Thresholds to determine the diagnosis for the dropped call. Recommended valus is -15 dB and the minimum and the maximum should be around -18 and -10 dB respectively.1.1. When 4 or more pilots are above this threshold.1. Display Thresholds command. 18. a pilot pollution event is created. Default is 3.com . 18. www.1. To modify the value.1.1.1. diagnosis and display of data in Spotlight.1. Default is 3.1. this threshold sets up the level of interference required for pegging the events (based on scanner info). 18.actix. 18.1.2 Average_SINR_PN0_Threshold This threshold is used to indicate a pass threshold for the Average SINR for PN_Nth_Best_0 (dB) for cluster acceptance.6 Max_TxPower_Threshold This threshold is used to indicate a pass threshold for the maximum Transmit Power (in dBm) for cluster acceptance.7 Min_TxPower_Threshold This threshold is used to indicate a pass threshold for the minimum Transmit Power (in dBm) for cluster acceptance. failed call and voice call with poor quality.1. Values should vary between -75 and 90 dBm.1.1. simply click on the associated number and type in the new value.

3 EVT_VerituneEVDOPilotPollution 1 (default) = Turns on the analysis for EVDO pilot pollution. 0 = this analysis is turned off to gain on file load speeds.4 EVDO / Other 18. 18.1.1.1. Default is 3. 18.com . 18. 0 = this analysis is turned off to gain on file load speeds.1.2. Default is 3.2 EVT_EVDOServerKey 1 (default) = Turns on the EVDO Server Key event diagram for EVDO troubleshooter.2 EVDO / Events 18. 18.1. 18. Default is 3. 0 = this analysis is turned off to gain on file load speeds.2.1.4 PPPSetupTime_Threshold This threshold is used to indicate a pass threshold for the PPP Session Setup time for cluster acceptance.1.actix.3 CDMA_EVDO_DRCRate_10 This is the data rate requested in bps for DRC Index 10.3 EVDO / Network Parameters 18. 18. Default is 0.2 CDMA_EVDO_DRCRate_1 This is the data rate requested in bps for DRC Index 1.1. 18.2 ConnectionAttemptDuration_Threshold This threshold is used to indicate a pass threshold for the Connection Attempt Setup time for cluster acceptance.1 CDMA_EVDO_DRCRate_0 This is the data rate requested in bps for DRC Index 0.1 AccessAttemptDuration_Threshold This threshold is used to indicate a pass threshold for the Access Attempt Setup time for cluster acceptance.Actix Spotlight Desktop User Guide November 2012 201 18.1.1.1.1. 18.3 ConnectionReleaseDuration_Threshold This threshold is used to indicate a pass threshold for the Connection Release time for cluster acceptance.3.1. Default is 3.4 SchedulerAnalysis 1 (default) = Turns on the scheduler analysis for EVDO troubleshooter.2. Default is 1228800.3.3. 0 = this analysis is turned off to gain on file load speeds.1.3. www.4.4.4.1 EVT_EVDOLowThroughput 1 (default) = Sets low throughput for EVDO troubleshooter.2. Default is 38400. 18. 18.

Default is 2457600. 18.4. www.1.1.1. Default is 921600. This value is reserved.4.4. Default is 76800.4.actix.1.14 CDMA_EVDO_DRCRate_7 This is the data rate requested in bps for DRC Index 7.com . 18.13 CDMA_EVDO_DRCRate_6 This is the data rate requested in bps for DRC Index 6.1. Default is 0.1. The maximum should not exceed 0 and the minimum should not be below -25 dBm.4.4. 18. Default is 1843200.4.7 CDMA_EVDO_DRCRate_14 This is the data rate requested in bps for DRC Index 14.1. 18.Actix Spotlight Desktop User Guide November 2012 202 18. Default is 614400.1. This value is reserved. Default is 1228800. Default is 307200.4.6 CDMA_EVDO_DRCRate_13 This is the data rate requested in bps for DRC Index 13.4.1.1. Default is 0.4.4 CDMA_EVDO_DRCRate_11 This is the data rate requested in bps for DRC Index 11. The DRC Channel is Off for Index 15.12 CDMA_EVDO_DRCRate_5 This is the data rate requested in bps for DRC Index 5.17 CDMA_EVDO_EcIoInterferenceThreshold Recommended value is -15 dBm. 18.8 CDMA_EVDO_DRCRate_15 This is the data rate requested in bps for DRC Index 15.4.16 CDMA_EVDO_DRCRate_9 This is the data rate requested in bps for DRC Index 9. 18.1.1. 18. 18. 18. 18. 18. 18.5 CDMA_EVDO_DRCRate_12 This is the data rate requested in bps for DRC Index 4.1.9 CDMA_EVDO_DRCRate_2 This is the data rate requested in bps for DRC Index 2.11 CDMA_EVDO_DRCRate_4 This is the data rate requested in bps for DRC Index 4.1. Default is 307200.10 CDMA_EVDO_DRCRate_3 This is the data rate requested in bps for DRC Index 3.4. Default is 153600.15 CDMA_EVDO_DRCRate_8 This is the data rate requested in bps for DRC Index 8. 18.4.4. Default is 0. Default is 614400.

The default is 100 kbps. 18. 18.4 Average_RxRlpThputInst_Threshold This threshold is used to indicate a pass threshold for the Average Receive RLP Throughput Inst.5. 18.actix. The default is 95%. The default is 5%.1.9 ConnectionAttemptSuccessRate_Threshold This threshold is used to indicate a pass threshold for the EVDO Connection Attempt success rate for cluster acceptance. (kbps) for cluster acceptance.5.1.5. The default is 95%.1. The default is 25 kbps.1.5. The default is 100 kbps.3.1.5.1.5 EVDO / Performance 18.5.11 PPPConnectionSuccessRate_Threshold This threshold is used to indicate a pass threshold for the PPP Connection Success Rate for cluster acceptance.7 Average_TxRlpThputInst_Threshold This threshold is used to indicate a pass threshold for the Average Transmit RLP Throughput Inst.com .5.5.10 ConnectionReleaseSuccessRate_Threshold This threshold is used to indicate a pass threshold for the EVDO Connection Release Success rate for cluster acceptance. www.1.6 Average_Tx_RlpRetransmissionRate_Threshold This threshold is used to indicate a pass threshold for the Average Transmit RLP Retransmission rate for cluster acceptance. 18.5.5.3.5 Average_RxTCHThroughput_Threshold This threshold is used to indicate a pass threshold for the Average Receive TCH Throughput (kbps) for cluster acceptance. 18.5. The default is .1.1. 18. Default is 5%. The default is 95%. 18.8 ConnectionAttemptFailRate_Threshold This threshold is used to indicate a pass threshold for the EVDO Connection Attempt Fail rate for cluster acceptance.Actix Spotlight Desktop User Guide November 2012 203 18. 18.1.1 AccessAttemptFailRate_Threshold This threshold is used to indicate a pass threshold for the EVDO Access Attempt Fail rate for cluster acceptance.1. 18.2 AccessAttemptSuccessRate_Threshold This threshold is used to indicate a pass threshold for the EVDO Access Attempt success rate for cluster acceptance. 18. The default is 95%.1. The default is . (kbps) for cluster acceptance.3 Average_Rx_RlpRetransmissionRate_Threshold This threshold is used to indicate a pass threshold for the Average Receive RLP Retransmission rate for cluster acceptance.

6. All Single User Throughput values less than or equal to SU_Rx_Throughput_Threshold value for continuously SU_Rx_Throughput_TimeLimit_Threshold seconds will be flagged as a Low SU Throughput issue. 18.1 RL_Throughput_Threshold This threshold (in kbps) is used to set the Low Throughput event for RL for both HICAP and LOLAT modes over all packet sizes. 18.6. The default is 50 kbps.2 EVDO events in the Event Explorer The following events are displayed in the top table of the Event Explorer: # Dropped Connections # Setup Failures # Access Attempt Failures # Excessive Setup # Low Throughput # Scheduling Issues % Low SU Throughput (RevA) % Low RL Throughput (RevA) These events are affected by the following thresholds: Average_PER_Threshold Average_SINR_PN0_Threshold CDMA_EVDO_PilotPollution_Count_Threshold CDMA_EVDO_PilotPollutionThreshold Average_RxRlpThputInst_Threshold Average_TxRlpThputInst_Threshold EVDO_Number_of_Users T2P_Avg_Threshold (RevA) www. 18.2 RL_Throughput_TimeLimit_Threshold This threshold is used to set the time limit in seconds to be used in computing the Low Throughput event for RL Packets.1. All RL Throughput values less than or equal to RL_Throughput_Threshold value for continuously RL_Throughput_TimeLimit_Threshold seconds will be flagged as Low RL Throughput issue. Default is 500 kbps.1.6 RevA 18.3 SU_Rx_Throughput_Threshold This threshold (in kbps) is used to set the Low Throughput event for TC averaged over time including the time the AN did not serve the AT.1. All RL Throughput values less than or equal to RL_Throughput_Threshold value for all continuously RL_Throughput_TimeLimit_Threshold seconds will be flagged as a Low RL Throughput issue. 18.Actix Spotlight Desktop User Guide November 2012 204 18.6.1.com .6. Default is 15 seconds.actix. The default value is 10 dB.1.4 T2P_Avg_Threshold This threshold (in dB) indicates the optimum value above which the transmission data rate is satisfactory.

Actix Spotlight Desktop User Guide November 2012 205 18. www.actix.com .3 Dropped Connection diagnosis for EVDO The following diagram outlines Spotlight's procedure for determining a diagnosis of Dropped Connection events.

Use other tools and views to refine your understanding of the problem. More investigation is needed.Actix Spotlight Desktop User Guide November 2012 206 Diagnosis Abnormal Connection Release Condition and notes ConnectionRelease_Reason parameter gives the reason for any abnormal connection releases.actix. 4+ pilots have EcIo > CDMA_EVDO_PilotPollutionThreshold. PER > Average PER threshold Average 1st Best SINR < Average_SINR_PN0_Threshold.com . Poor Quality Low Signal Pilot Pollution Other www.

Actix Spotlight Desktop User Guide November 2012 207 18.com . www.4 Low Throughput diagnosis for EVDO The following diagram outlines Spotlight's procedure for determining a diagnosis of Low Throughput events.actix.

4+ pilots have EcIo > CDMA_EVDO_PilotPollutionThreshold.actix. Tx RLP Throughput < Average_TxRlpThputInst_Threshold. Number of users > EVDO_Numberof_Users (Threshold). PER > Average PER threshold. www. Average 1st Best SINR < Average_SINR_PN0_Threshold.com . Rx RLP Throughput < Average_RxRlpThputInst_Threshold. Ave. More investigation is needed. Use other tools and views to refine your understanding of the problem.Actix Spotlight Desktop User Guide November 2012 208 Diagnosis Low RLP Rx Throughput Low RLP Tx Throughput Network Overload Low Signal Poor Quality Pilot Pollution Other Condition and notes Ave.

5 Scheduling Issues diagnosis for EVDO The following diagram outlines Spotlight's procedure for determining a diagnosis of Scheduling Issue events.actix.com .Actix Spotlight Desktop User Guide November 2012 209 18. www.

PER > Average PER threshold.com . Average 1st Best SINR < Average_SINR_PN0_Threshold. More investigation is needed. Use other tools and views to refine your understanding of the problem.Actix Spotlight Desktop User Guide November 2012 210 Diagnosis Network Overload Low Signal Poor Quality Pilot Pollution Other Condition and notes Number of users > EVDO_Number_of_Users (Threshold).actix. www. 4+ pilots have EcIo > CDMA_EVDO_PilotPollutionThreshold.

3.2.1 G_Distance_Max This threshold is used to determine the maximum distance allowed per cell.1.1. before a Dragged Handover Failure or Dragged Dropped Call is triggered.2. The default value is 10000 ms.1 Spotlight 19. Display Thresholds command. KPIs and diagnoses 19. 19. The default value is 5 dBm. www.actix.1 GSM thresholds You can modify threshold values for event detection using the Tools. Typically.2. To modify the value. values in excess of 8000 meters are usually regarded as distant serving cells. The default value is 6000 ms.1. and indicates the maximum serving distance (in meters) a cell should serve. Default is 5000m. Dominance loss = ServRxLevSub < (Best_Nbr Hysteresis). 19.1 SL_Overspill_Dist_Threshold This threshold is used if there is no Max_ServerDist information in the cellref file. diagnosis and display of data in Spotlight. 19.Actix Spotlight Desktop User Guide November 2012 211 19 Appendix G: GSM thresholds.1.3 Ping_Pong_HO_Window This threshold is the number of milliseconds during which a handover back to the previous cell will trigger the Ping Pong Handover Event.2 Dragged_HO_Window This threshold is the number of milliseconds that the MS must lose dominance for.2 GSM / Advanced_Handover_Analysis 19.1.com .1. It is important to set your threshold before loading the data because it will affect the analysis.1. and not re-established before the Dragged_HO_Window timer expires. then any subsequent Handover Failure or Dropped Call will trigger the Dragged Handover Failure or Dragged Drop. simply click on the associated number and type in the new value.3 GSM / Analysis 19.1. 19.1. 19. Once a loss of dominance is triggered.1 Dragged_Dominance_Hysteresis This threshold is the dBm hysteresis applied to the Best Neighbor Level to trigger a loss of dominance of the server.

19. 19. You can set the units to be used (either miles or kilometers) in Preferences. General Settings.5. www. approximately 8 km) are usually regarded as distant serving cells.Actix Spotlight Desktop User Guide November 2012 212 19.6 G_RxQualSub_Max This threshold is used in conjunction with the signal strength to determine whether there is interference present on the cell.1.3. Recommended value: -95 dBm.5 GSM / Events 19.1.2 G_ScanSortSigLevel_Min This value is used in relation to the scanner signal level. for example.3. Typically.2 G_Handover_Min This threshold is used in conjunction with handover to determine the minimum possible signal difference for handover to take place.7 G_TimingAdvance_Max This threshold is used in absence of the Distance parameter to determine the maximum distance allowed per cell.1.1. 19. Any signal below this threshold is categorized as poor coverage. Default is 3000 ms.4 GSM / Cell_Plan_Viewer 19.3.1 G_Timeout_ChannelRequest This value is used to determine the time (in ms) the system will wait for RR Channel Request messages to be answered before registering a Call Setup Failure.4. 19.3 G_MsTxPowStepOrdered_Min This threshold is used in conjunction with the signal strength to determine incorrect uplink power balance.4 G_Prolong_Interf_timer This threshold is used in conjunction with the signal strength and signal quality to determine prolong interference – that is.3.1.4. values over 16 (that is. good signal strength but bad quality in this time window will cause a prolong interference event.1 G_Interference_Radius This value is used to define a radius of analysis about a selected sector for coadjacent interference and neighbors visualizations in the Cell Plan Viewer.com .3. 19. 19. in the Channel Overlap analysis in the GSM Cell Plan Viewer. values in excess of 3 with good signal strength usually indicate the presence of interference.1.1. Typically.5 G_RxLevSub_Min This threshold is used to determine the minimum acceptable value for signal strength. Recommended values are 56 dB. 19. 19. Distance Units.3.1.actix.1. This value is usually set to 0 to indicate maximum uplink power.1.1.

Values less than 5000 ms will tend to be more accurate.8 SL_GSM_Site_Issues_Dist_Threshold This threshold is used in the ‘outside beamwidth’ analysis.6. The default value is 3000 ms.1. The default value is 5 dB. but with relatively low accuracy since the time under analysis is large.1 SL_GSM_Ant_Gain_Threshold This threshold is the default Antenna gain. www. 19.4 dB. The default value is 2. 19. and only data within this distance from the site is considered for the analysis.7 SL_GSM_RapidPathloss_Time_window_Threshold This threshold is used to define the window over which Rapid Pathloss is performed.Actix Spotlight Desktop User Guide November 2012 213 19. The default value is -120 dBm.6. but less attributes will be detected. used in the calculation of DL pathloss. The default value is 55.actix. used in the calculation of UL pathloss.7 GSM / Troubleshooter 19. while values in excess of 10000 ms tend to have a high detection of attributes. values of 5000 to 10000 ms are used.1 G_Analysis_Time_After This value is used to determine the time (in ms) allocated to investigate the radio conditions AFTER the detected event occurrence.1.4 SL_GSM_High_TX_Power_Threshold This threshold is used for determining a ‘High TX’ condition.1. 19.2 SL_GSM_BTS_Sens_Threshold This threshold is the default BTS receive sensitivity. Typically.3 SL_GSM_EIRP_Threshold This threshold is the default EIRP.6 SL_GSM_RapidPathloss_RxQual_Threshold This threshold is used in Rapid Pathloss detection. 19.1.1.6. a condition of which is that RxLev has dropped by at least this threshold value within the defined time window.5 SL_GSM_RapidPathloss_RxLev_Threshold This threshold is used in Rapid Pathloss detection.6. The RxQual condition must also be met for Rapid Pathloss to be detected.com .6. 19. The default value is 18.6.1. The default value is 5000m. The RxLev condition must also be met for Rapid Pathloss to be detected. 19. a condition of which is that RxQual has dropped by at least this threshold value within the defined time window.1. The default value is 30. used in the calculation of pathloss. 19.1.7.6. 19.6.1.1.6 GSM / Spotlight 19.1.

www. If the resulting KPI is equal or in excess to this value. If the resulting KPI is equal or in excess to this value. The Handover Success Rate should be in excess of 98% for most GSM networks in the busy hour.Actix Spotlight Desktop User Guide November 2012 214 19. it will be flagged as accepted and will show up as a green tick mark in the KPI table. If the resulting KPI is equal to or in excess of this value. If it is less than this value.2 G_Analysis_Time_Before This value is used to determine the time (in ms) allocated to investigate the radio conditions PRIOR to the detected event occurrence.1.1. it will be flagged as failed and will show up as a red cross in the KPI table. 19.5 G_HandoverSuccessRate This threshold is used to determine the criterion for KPI acceptance in the repository views.3 G_CallDropRate This threshold is used to determine the criterion for KPI acceptance in the repository views. it will be flagged as accepted and will show up as a green tick mark in the KPI table. Typically.6 G_LocationUpdateSuccessRate This threshold is used to determine the criterion for KPI acceptance in the repository views. 19. while values in excess of 10000 ms tend to detect a large number of attributes. If the resulting KPI is equal or in excess to this value.7 G_OverAllSuccessRate This threshold is used to determine the criterion for KPI acceptance in the repository views. If it is less than this value. If the resulting KPI is equal to or less than this value. it will be flagged as failed and will show up as a red cross in the KPI table.actix. The Location Update Success Rate should be in excess of 98% for most GSM networks in the busy hour. it will be flagged as accepted and will show up as a green tick mark in the KPI table.1. If it is less than this value. 19. The Call Setup Success Rate should be in excess of 98% for most GSM networks in the busy hour. it will be flagged as failed and will show up as a red cross in the KPI table.com . it will be flagged as accepted and will show up as a green tick mark in the KPI table.1.7. values of 5000 to 10000 ms are used.7.7. it will be flagged as failed and will show up as a red cross in the KPI table. it will be flagged as failed and will show up as a red cross in the KPI table. If it is less than this value.7. If it is higher than this value. Values less than 5000 ms will tend to be more accurate. it will be flagged as accepted and will show up as a green tick mark in the KPI table. but fewer attributes will be detected. 19. 19.4 G_CallSetupSuccessRate This threshold is used to determine the criterion for KPI acceptance in the repository views.7.1.7. The Overall Success Rate should be in excess of 98% for most GSM networks in the busy hour.1. The Call Drop Rate should not exceed 2% of all successful calls in the busy hour. but with relatively low accuracy since the time under analysis is large.

com .Actix Spotlight Desktop User Guide November 2012 215 19.2 GSM events in the Event Explorer The following event information is displayed in the top table of the Event Explorer: GSM: Circuit Switched category # Call Attempts #Dropped Calls # Call Setup Failures # LU Fails GSM: Handover Issues category # HO Att # HO Fails GSM: NBR Neighbor Issues category % Strong NBR % Strong NBR Diff Band % NBRs with 5dB % NBRs with 5dB Diff Band GSM Diagnoses Call Setup Failure diagnosis Location Update Failure diagnosis Dropped Calls diagnosis Handover Failure diagnosis www.actix.

com .3 Call Setup Failure diagnosis for GSM The following diagram outlines Spotlight's procedure for determining a diagnosis of Call Setup Failure events.actix. www.Actix Spotlight Desktop User Guide November 2012 216 19.

Actix Spotlight Desktop User Guide November 2012 217 Diagnosis RR Failed Condition and notes An RR Channel Request is not followed by an RR Immediate Assignment with matching establishment cause and random reference within the time period specified by the G_Timeout_ChannelRequest threshold. Use other tools and views to refine your understanding of the problem. Another RR Channel Request with a different establishment cause or random reference occurs at any time after the RR Immediate Assignment and before the call setup is complete.com . Immediate Reject Another Call Started  Another RR Channel Request with the same establishment cause and random reference occurs more than 200 milliseconds after the RR Immediate Assignment and before the call setup is complete.  CM Service Abort / Reject User Release Poor Coverage Interference Other A CM Service Abort / Reject message was received. If ServRxQualSub > G_RxQualSub_Max. If ServRxLevSub < G_RxLevSub_Min.actix. More investigation is needed. www. When a call setup procedure is aborted by the UE with a UL CC Disconnect message. An Immediate Reject message was received.

com .actix.4 Location Update Failure diagnosis for GSM The following diagram outlines Spotlight's procedure for determining a diagnosis of Location Update Failure events. www.Actix Spotlight Desktop User Guide November 2012 218 19.

If ServRxQualSub > G_RxQualSub_Max. More investigation is needed.actix. An Immediate Reject message was received.Actix Spotlight Desktop User Guide November 2012 219 Diagnosis RR Failed Condition and notes An RR Channel Request is not followed by an RR Immediate Assignment with matching establishment cause and random reference within the time period specified by the G_Timeout_ChannelRequest threshold. 42) in either the NAS message or the RR Channel Release message. Immediate Reject Another Call Started  Another RR Channel Request with the same establishment cause and random reference occurs more than 200 milliseconds after the RR Immediate Assignment and before the call setup is complete.com . Other www. Use other tools and views to refine your understanding of the problem. Another RR Channel Request with a different establishment cause or random reference occurs at any time after the RR Immediate Assignment and before the call setup is complete.  LU Reject Poor Coverage Interference System Released A Location Update Failure message was received. When the cause code is Not Normal (0-31. If ServRxLevSub < G_RxLevSub_Min.

www.Actix Spotlight Desktop User Guide November 2012 220 19.com .actix.5 Dropped Calls diagnosis for GSM The following diagram outlines Spotlight's procedure for determining a diagnosis of Dropped Call events.

If ServRxLevSub < G_RxLevSub_Min. Use other tools and views to refine your understanding of the problem. Scanner: If one of the top 6 BCH is not in the BA list before the drop. CauseCodeRR = 9 Handover Failure message. 19. BCH is not in the BA list.actix. CauseCodeRR = 10 www.Actix Spotlight Desktop User Guide November 2012 221 Diagnosis System Released Condition and notes When the cause code is Not Normal (0-31. For example: Diagnosis Handover Impossible (TA out of Range) Channel mode unacceptable Frequency not implemented Condition and notes Handover Failure message. More investigation is needed. CauseCodeRR = 8 Handover Failure message. 42) in either the NAS message or the RR Channel Release message.com . See GSM Dragged Handovers. Missing Neighbor Handover Problem Poor Coverage Interference Other If stronger neighbors than the serving cell for a period. but was before the drop. If ServRxQualSub > G_RxQualSub_Max. Handset: If after the drop.6 Handover Failure diagnosis for GSM The diagnosis for Handover Failure is derived directly from the CauseCodeRR value.

At the top of the Event Explorer page is a list of occurrences of HSPA Call drops. Please refer to the description of HSPA KPIs on p222 for details of HSPA diagnostics. select the HSPA Call Drop from either the HSPA Summary Dashboard in the Critical Issues section. 20. you select a long 'After Window' (in the tens of seconds). or the top table of the Event Explorer page.1.2 Detailed Event Diagnostics Of the HSPA KPIs listed in the top table.actix. by default the following HSPA event KPIs are displayed.1. we strongly recommend that. KPIs and diagnoses 20. www. aggregated by site:         Call Attempts Dropped Calls Call Setup Failures Average RAW Throughput RAW Throughput Peak Cell Change Failures (not yet implemented) Low Raw Throughput Instances Low Net Throughput Instances 20. these have diagnostic information (and can be investigated further using the Drilldown mechanism):    Call Drop Low Raw Throughput Low Net Throughput For failure scenarios where a transition to Idle mode occurs (such as the dropped call under investigation in this example).1 HSPA Event Explorer analysis 20.Actix Spotlight Desktop User Guide November 2012 222 20 Appendix H: HSPA thresholds.1 Event Explorer dashboard In the top table of the Event Explorer dashboard.com .2 HSPA Call Drop Analysis example To access the HSPA Call Drop analysis. in the Drilldown options. An associated root cause analysis is shown in the diagnostic panel on the left.

which then re-establishes the radio connection on the new site in R99.1 Drilldown You can investigate all the KPIs with diagnostic information with the Drilldown mechanism.actix. DCH_R99. This can also be clearly seen on the map. By plotting this binned data on the map. which indicates what kind of resources (if any) are allocated to the UE (HSPA. and the target SC in R99 (45).com . www. includes a transition to Idle mode. The UE goes out of HSPA coverage and is forced into Idle mode by the network.Actix Spotlight Desktop User Guide November 2012 223 The first example of an HSPA Dropped Call is a case of HSPA to R99 transition via Idle mode. The diagnostic panel provides essential information. we can confirm the diagnosis.2. a long 'After Window' of 30 seconds was selected. so in the Drilldown options. such as the last SC under HSPA coverage (104). 20. One interesting binned data attribute to display on the map is the UE state. FACH). and can visualize the transitions from HSPA to DCH_R99. The dropped call under investigation in this example.

actix. but in R99. as the throughput remains at reasonable levels.Actix Spotlight Desktop User Guide November 2012 224 The drilldown screen looks like this: The main aspects to point out from the screen layout are:   The Active Set analysis: it can be clearly seen that at the moment of the call drop. Due to the UE dropping to Idle for several seconds. Further down in the signaling. the HSPA radio performance is less essential for the analysis as the user experience is compromised anyway. the HSPA connection provides a good performance up to a few seconds before the drops. SC_45 is much stronger than SC_104 (the current HSPA server) In the Protocol Stack Browser. the user is paged by the network.com . The radio charts report the typical HSPA L1 measurements and give an idea of the quality of the HSPA connection before the call drops. and the radio connection is re-established on SC_45. it is worth noting that the user consistently reports that SC_45 has a better signal than SC_104 (several Measurement Report messages).  www. until the network decides to release the radio connection (RRC Connection Release message). However.

so the settings of the thresholds that control Low Throughput detection (see above) play a fundamental role here. www. like in this demo.that is. However. Three different results from the root cause analysis are shown. or from the top table of the Event Explorer Once one of the Low Throughput KPIs is selected. Cell Changes that involve a change of site cause longer interruptions therefore these are the most common in the diagnostic panel. as they coincide with the dropped call events seen above. the interruption is normally even longer. the Event Explorer displays in the diagnostic panel a list of five occurrences of Low Throughput and associated root cause analyses. Whenever an HSPA Call Drop event is detected. when the network points the user at another HS server cell. It is important to highlight that the diagnostic information provides information on the type of Cell Change in terms of site and frequency. the technology seems not mature yet to allow Direct Cell Changes with change of frequency (but we have seen change of frequency cases with transitions to Idle mode).actix. If a change of frequency occurs.3 HSDPA Low Throughput example You can access the Low Throughput analysis by selecting either Low Raw HS Throughput or Low Net HS Throughput KPI from the Summary Dashboard's Critical Issues section. because transitions to Idle involve a service interruption noticeable by the user.Actix Spotlight Desktop User Guide November 2012 225 20. These cases should introduce relatively short interruptions. a Low Throughput event is also pegged.com . Skip the cases related to HSPA to R99 transition via Idle mode. The first case to analyze is the event caused by a Direct HS Cell Change .

The performance slightly increases right after the cell change. the performance should improve following a Cell Change. and this is a clear example of network not optimized. casing a so-called ping-pong scenario. but as we can see.actix. For a well-designed network. In the Drill-down section. It highlights that numerous Cell Changes occurred in a very short time. we will be able to see that the cell changes occur between the same two cells. the quality of the signal (EcIo) in the target cell is already degrading. as we will see shortly. That is not always the case.Actix Spotlight Desktop User Guide November 2012 226 Other useful information to mention is signal strength of source and target cell and all the HSPA physical layer measurement provided before and after the event. www.com . Now look at the second case of Direct Cell Change shown on the right.

Just like for the HSDPA Call Drop KPI. the “lack of data to transmit” scenario identified here is independent of the conditions occurring after. However. 20.1 Drilldown All the KPIs with diagnostic information can be investigated further via the Drilldown mechanism. and this will be clear from the Drill-down page.3. www.com . The noticeable quality degradation after the event is due to radio condition getting worse.Actix Spotlight Desktop User Guide November 2012 227 Another case that can be shown is the “Lack of Data to Transmit” scenario. remember to select a long “after window” in the Drilldown options for scenarios that include Idle transitions. In the map the user is very close to the serving cell. which justifies the high level of CQI (23) measured during the low throughput window of time. where throughput is extremely low but the radio conditions are good.actix.

The Event Navigator below confirms the occurrence of several HS Cell changes within a short time. Also. Finally.com . www.Actix Spotlight Desktop User Guide November 2012 228 For the HS Direct Cell Change case. an After Window of 5 seconds is enough. the Protocol Stack Browser window shows the signaling associated with these mobility procedures. the radio graphs give an overview of the level of degradation suffered from this poor design issue.actix.

The most recurrent scenarios are:   Terminal spontaneously (that is.Actix Spotlight Desktop User Guide November 2012 229 For the “Lack of Data to Transmit” case. but a HSPA Drop call is only pegged when the UE is in HSPA state at the moment the call drops. 20. Therefore.com . Usually. Here we can see that despite good radio conditions (check the numeric values of CQI and its visual representation on the map) throughput is null before the event detection. it is possible to see quite easily from the Event Navigator form that a HS Cell Change occurs. whenever the UE goes from HSPA to Idle without a normal call release. an HSPA Drop Call event is detected. Radio conditions get worse afterwards. not network-forced) dropping the radio connection Network releasing the radio connection for causes other than user inactivity or normal PDP Context deactivation www. But as mentioned above this is another issue and completely unrelated to the lack of data to transmit.1 HSPA Call Drops An HSPA call is a UMTS PS Call where the UE is in 'HSPA' state.4 HSPA events in the Event Explorer 20. maintain the Drill -down settings used above. and in fact. the trigger of HSPA Drop call is the same as UMTS PS Drop call.actix.4.

2. 20. UE drops to idle The UE drops to idle when radio link conditions becomes poor. For more information on Raw and Net MAC-HS Throughput.4.4. 20.   20.2. RRC Connection Release The network (RNC) releases the RRC Connection with a cause other than 'Normal' or 'User Inactivity'. You can configure the detection mechanism via the following HSDPA thresholds: 20.com .Actix Spotlight Desktop User Guide November 2012 230 The following failure cases are supported:  Deactivation of PDP Context due to abnormal situations When the network (SGSN) releases the PDP context for abnormal scenarios (this is detected via a Deactivation PDP Context Request downlink message with SM cause different from 'Regular deactivation'.actix.) that the HSDPA throughput is allowed to stay under a certain value (Uu_HSDPALowRawThrou_Thresh or Uu_HSDPALowNetThrou_Thresh).4. please see the section HSPA Throughput KPIs on p233.1 Uu_HSDPALowRawThrou_Thresh The value (in kbps) under which the instantaneous Raw HSDPA throughput is considered LOW .It is used in conjunction with the threshold Uu_HSDPALowThrouMaxTimeWin_Thres.2.Excessive interference .The UE is moving in an area where HSPA is not supported (and the network does not handle direct HSDPA to R99 transitions). to peg Low Raw MAC-HS Throughput events in Drive Test. to peg Low Net MAC-HS Throughput events in Drive Test.No coverage . If the throughput stays under those raw or net throughput thresholds for a period longer than Uu_HSDPALowThrouMaxTimeWin_Thres a Low Raw(Net) MAC-HS Throughput event is pegged for Drive Test www.It is used in conjunction with the threshold Uu_HSDPALowThrouMaxTimeWin_Thres.3 Uu_HSDPALowThrouMaxTimeWin_Thres The time (in msec.2 Uu_HSDPALowNetThrou_Thresh The value (in kbps) under which the instantaneous Net HSDPA throughput is considered LOW . Typical scenarios are: . The analysis can be based on Raw MAC-HS throughput or Net MAC-HS throughput.2 Low Throughput Issues Low throughput conditions are detected when the user throughput exceeds a certain threshold for a specified period of time.4.

com . www.2. during which the UE receives a limited amount of data .or no data at all.actix. expect throughput degradation.4 Raw HS Throughput  Mobility scenarios Whenever a mobility scenario occurs. as with Idle transitions.Actix Spotlight Desktop User Guide November 2012 231 KPI/attribute Uu_LowRawHSDPAThroughput Uu_LowNetHSDPAThroughput Uu_HSCellNotBestPilot Low Tput KPI event (Used for diagnostic purposes only) Related threshold Uu_HSDPALowRawThrou_Thresh Uu_HSDPALowThrouMaxTimeWin_Thres Uu_HSDPALowNetThrou_Thresh Uu_HSDPALowThrouMaxTimeWin_Thres Uu_WinTimeHSnotBest Uu_HSDPALowCQI_Thresh Uu_HSDPAAvRegularSched_Thresh Uu_HSDPAAvLowSched_Thresh Uu_HSDPANet_To_L1_Throu_Thresh Uu_HSDPAL1_To_Raw_Throu_Thresh SL_UMTS_DT_Spotlight_CriticalIssues_HSDPAPea kTput HSDPA Peak Tput (threshold determines if this is a critical issue in the Summary dashboard) HSDPA Setup Failure rate Overall PS Setup Failure rate Average HSDPA Call Setup time HSDPA Call Drop rate Overall PS Call Drop rate Average EcIo 95 percentile MAC-HS Tput Average RSCP 95 percentile DL TCP Tput 95 percentile CQI Tput 95 percentile EcIo Tput 95 percentile RSCP Tput HSDPA_NW_Acceptance_HSDPA_Failure_Rate HSDPA_NW_Acceptance_Overall_PS_Failure_Rate HSDPA_NW_Acceptance_HSDPA_Setup_Time HSDPA_NW_Acceptance_HSDPA_Drop_Rate HSDPA_NW_Acceptance_PS_Drop_Rate HSDPA_NW_Acceptance_EcIo_Threshold HSDPA_NW_Acceptance_95_Percentile_MACHS_T hroughput_Threshold HSDPA_NW_Acceptance_RSCP_Threshold HSDPA_NW_Acceptance_95_Percentile_TCP_Thro ughput_Threshold HSDPA_NW_Acceptance_95_Percentile_CQI_Thre shold HSDPA_NW_Acceptance_95_Percentile_EcIo_Thr eshold HSDPA_NW_Acceptance_95_Percentile_RSCP_Th reshold The following failure cases are supported: 20.4. The level of degradation is proportional to the duration of the mobility procedure.

30 is the maximum value a UE can report. Net HS Throughput   20. However some useful measurement data are included in the table for the Net Tput KPI and this data might be sufficient)..com . despite a good Raw Throughput. which would explain why only Net Throughput issues are detected. However the diagnostic alerts you that the threshold for Low Raw Throughput event detection might not be restrictive enough.4. and Uu_HSDPALowCQI_Thresh is a number between 0 and 1. the average scheduling rate (from the instantaneous scheduling rate dataset Uu_HSDPA_FrameUsage) is below the user-specified threshold Uu_HSDPAAvRegularSched_Thresh (0.Actix Spotlight Desktop User Guide November 2012 232 The sub-cases below are self-explanatory and are all mutually exclusive by definition: ▫ ▫ ▫ ▫ ▫ HS Direct Cell change ongoing Intra-F HS Cell Change via Idle mode Inter-F HS Cell Change via Idle mode HS to DCH_R99 direct transition HS to DCH_R99 transition via Idle mode  Low CQI values These are detected when the average CQI in the last 3 seconds is below the user-specified threshold Uu_HSDPALowCQI_Thresh. This scenario typically occurs when there is no activity (data).2. Low CQI values are an indication of poor radio downlink conditions. because under certain scenarios UEs might only report 15 as the maximum CQI. Lack of data to transmit This is detected when the Statistical Mode of the Instantaneous Raw Tput in the last 3 seconds is 0.5 A Low Net HS Throughput can usually be associated with an underlying Raw Throughput scenario. This may occur when more than one HSPA user is present in the HS Serving Cell where the event is detected. Low scheduling rate This is detected when in the last 3 seconds. the Net Throughput does not reach satisfactory levels:  Low Raw HS Throughput If Low RAW Tput is also detected.1). The threshold needs to be a factor ranging from 0 to 1 rather than an absolute CQI threshold between 0 and 30. but the handset is kept in HSPA mode by the network. there are some interesting cases where. Low Raw HS Throughput not detected All the cases listed for Raw Throughput are still valid. However. Check through the Low Raw Throughput KPI list of occurrences for the right event (timestamp would be the same as the Low Net Tput event.  www. the diagnostic simply reports that the cause of Net Tput degradation is related to underlying Raw Tput.actix.

if a UMTS PS call fails at an early stage. the event can be missing from the diagnostic panel in the KPI dashboard. it is not possible to know whether a R99 or a HSPA bearer would have been used. However. leading to a discrepancy in the number of events displayed. An attempt to establish a HSPA call can be detected only when the bearer is being set up. Therefore. 20.actix.5 HSPA Throughput KPIs The following types of HSPA throughput are provided in the HSPA Network Acceptance report:   Raw MAC-HS throughput Net MAC-HS throughput  Net DL TCP throughput www.5 Known Issues If a particular KPI event (for example.com .4 HSPA Call Setup Failure This event is detected whenever a failure occurs during the setup of the HSPA bearer.4. Two scenarios are analyzed:  High retransmissions due to packet incorrectly received in Downlink This is detected when: Uu_HSDPA_Throughput_L1 < Uu_HSDPAL1_To_Raw_Throu_Thresh Uu_HSDPA_PayloadRate_L1 For the definition of the different types of HSDPA throughput. HSDPA requires clear pilot dominance for an efficient service delivery (good throughput). the 'Further Information' section provides additional information regarding Net throughput. HSPA Call Drop) occurs very close to the end of the logfile. Identifying zones with a lack of pilot dominance is a very important task in the rollout and optimization of HSDPA. the event will be flagged in both the initial dashboard (as part of the % Call Drop Critical Issue if the relevant threshold condition is fulfilled) and the top table of the KPI dashboard. please refer to the section on HSDPA Throughput KPIs. In these cases.  High retransmissions due to poor Uplink quality conditions This is detected when: Uu_HSDPA_Throughput_MAC Uu_HSDPA_Throughput_L1 < Uu_HSDPANet_To_L1_Throu_Thresh For the definition of the different types of HSDPA throughput.3 Lack of pilot dominance issues This is essentially very similar to 'Pilot pollution' or 'Too many servers' but focused on HSDPA. 20. the Call Setup Failure is pegged only as a UMTS PS Call Setup Failure.4. 20. please refer to the section on HSDPA Throughput KPIs.4. 20.Actix Spotlight Desktop User Guide November 2012 233 If high levels of retransmission occur.

com . 95% percentile) are derived from the MAC-HS instantaneous throughputs. For the purpose of throughput calculation.actix.Actix Spotlight Desktop User Guide November 2012 234 MAC-HS throughput KPIs (e. Mean. Mode.5.HS instantaneous throughput = (bytes received by the UE over 200ms)/200ms The difference between Raw and Net MAC-HS throughput is that Raw throughput includes ALL the packets scheduled for the UE. MAC-HS net throughput and RLC throughput do not coincide: The Net DL TCP throughput is simply the downlink TCP throughput that excludes TCP re-transmissions. but in reality the Net throughput is always lower than the Raw throughput. this includes MAC-HS header and padding. the size of the entire MAC-HS PDU is used.1 Notes   In ideal scenarios. while Net throughput does not include packets unsuccessfully decoded or re-transmitted: Raw throughput -> All packets received by UE Net throughput -> Only successfully decoded (not re-transmitted) packets The following figure further clarifies the approach used for the calculation of Raw and Net MAC-HS throughput: Total # packets contributing to Raw MAC-HS throughput -> 7 Total # packets contributing to Net MAC-HS throughput -> 5 20. www. For this reason.g. Raw and Net MAC-HS throughput are equal. Both raw and net instantaneous throughputs are calculated every 200 msecs: MAC .

). To modify the value.com .2.6 HSDPA thresholds You can modify threshold values for event detection using the Tools. www. The default value is 3000 ms. For a definition of Raw HSDPA Throughput see Uu_HSDPA_PayloadRate_L1. The default value is 400 kbps.1 SL_Overspill_Dist_Threshold This threshold is used.2 HSDPA thresholds The following thresholds are available under the root of the HSDPA node: 20.4 Uu_HSDPALowThrouMaxTimeWin_Thres This threshold is used to set the period of time (in msec. Display Thresholds command. to peg Low Net MAC-HS Throughput events in Drive Test.6.6. The time interval is as lons as the duration of the Cell Change procedure.6.Actix Spotlight Desktop User Guide November 2012 235 20.6. see Uu_HSDPA_Throughput_MAC.5 Uu_ThresGapBeforeThrComparison This parameter indicates the gap between the end of the Cell Change procedure and the start of the time interval used to calculate the TCP throughput for comparison with the throughput during the cell change.6.3 Uu_HSDPALowNetThrou_Thresh This threshold is used to set the value (in kbps) under which the instantaneous Net HSDPA throughput is considered LOW .1 IUB_THROUGHPUT_PERIOD_THRES This threshold is used to set the sampling period (in msec. It is important to set your threshold before loading the data because it will affect the analysis. Note that MACd throughput includes the header of RLC and layer above (PDCP. For a definition of Net HSDPA Throughput.1. if there is no Max_ServerDist information in the cellref and indicates the maximum serving distance (in meters) a cell should serve. 20.2 Uu_HSDPALowRawThrou_Thresh This threshold is used to set the value (in kbps) under which the instantaneous Raw HSDPA throughput is considered LOW . Default is 5000m. simply click on the associated number and type in the new value. 20. 20.6.actix. to peg Low Raw MAC-HS Throughput events in Drive Test.2. etc. IP.2. The default value is 1000 ms.2.) for the calculation of MACd throughput over the Iub.It is used in conjunction with the threshold Uu_HSDPALowThrouMaxTimeWin_Thres.6.) that the HSDPA throughput is allowed to stay under a certain value (Uu_HSDPALowRawThrou_Thresh or Uu_HSDPALowNetThrou_Thresh). 20.6.It is used in conjunction with the threshold Uu_HSDPALowThrouMaxTimeWin_Thres. The default value is 1000 ms. If the throughput stays under those raw or net throughput thresolds for a period longer than Uu_HSDPALowThrouMaxTimeWin_Thres a Low Raw(Net) MAC-HS Throughput event is pegged for Drive Test. The default value is 300 kbps. diagnosis and display of data in Spotlight. 20.1 Spotlight Thresholds 20. 20.2.

3.3 HSDPA_NW_Acceptance_HSDPA_Setup_Time This threshold is used to indicate an average HSPA call setup acceptance time.9 HSDPA_NW_Acceptance_95_Percentile_TCP_Throughput_Thr eshold This threshold is used to indicate the lowest required TCP Throughput value at the 95 percentile for HSPA Network acceptance (unit is kbit/sec).6.6. to setup thresholds above which measurements from the UE as seen good for HSPA Network acceptance.6 Uu_WinTimeHSnotBest This threshold is used to set the period of time (in msec. 20.4 HSDPA_NW_Acceptance_HSDPA_Drop_Rate This threshold is used to indicate a pass threshold for the HSPA call drop rate.6. 20. to setup thresholds above which measurements from the UE a seen good for HSPA Network acceptance. www.6. If the quality of the HS Serving Cell is below the best pilot in the AS for a period longer than this threshold a Uu_HSCellNotBestPilot event is pegged for Drive Test.6. 20. 20. 20.5 HSDPA_NW_Acceptance_PS_Drop_Rate This threshold is used to indicate a pass threshold for the PS R99 call drop rate.3.3.1 HSDPA_NW_Acceptance_HSDPA_Failure_Rate This threshold is used to indicate a pass threshold for the HSPA call setup failure rate.3.6.6.3.6 HSDPA_NW_Acceptance_EcIo_Threshold This threshold is used in conjunction RSCP threshold.6. 20.3. 20.Actix Spotlight Desktop User Guide November 2012 236 20. The default value is 1000 ms.6.3.3.2 HSDPA_NW_Acceptance_Overall_PS_Failure_Rate This threshold is used to indicate a pass threshold for the overall PS call setup failure rate (HSPA and R99).com .3. 20.8 HSDPA_NW_Acceptance_95_Percentile_MACHS_Throughput_ Threshold This threshold is used to indicate the lowest required Raw MAC HS Throughput value at the 95 percentile for HSPA Network acceptance (unit is kbit/sec).) that the EcIo of the HS Serving Cell is allowed to be lower than the best pilot EcIo in the Active Set.actix. 20.7 HSDPA_NW_Acceptance_RSCP_Threshold This threshold is used in conjunction EcIo threshold.3 HSDPA / HSDPA_NW_Acceptance Thresholds These are used for the HSPA Spotlight Reports.2.6. 20.6.

20.12 HSDPA_NW_Acceptance_95_Percentile_RSCP_Threshold This threshold is used to indicate the lowest required RSCP value at the 95 percentile for HSPA Network acceptance.10 HSDPA_NW_Acceptance_95_Percentile_CQI_Threshold This threshold is used to indicate the lowest required CQI value at the 95 percentile for HSPA Network acceptance.6. The default value is 0.7.6.4.4.Actix Spotlight Desktop User Guide November 2012 237 20. See also Uu_HSDPALowNetThrou_Thresh and Uu_HSDPALowThrouMaxTimeWin_Thres www.1 Uu_HSDPALowCQI_Thresh This threshold is used to set the value under which the average CQI is considered low (average calculated on the 5 secs.11 HSDPA_NW_Acceptance_95_Percentile_EcIo_Threshold This threshold is used to indicate the lowest required EcIo value at the 95 percentile for HSPA Network acceptance. The default value is 0.6.4. 20.6.4.3 Uu_HSDPANet_To_L1_Throu_Thresh This threshold is used to set the value under which the ratio between Net HS Throughput average and L1 HS Throughput average is considered low enough to assign the cause of Low Net HS Throughput not only to lack of data sent by the network. The max achievable CQI is a function of the UE category and the modulation used (QPSK or 16 QAM).1) of the max achievable CQI..6.4 Uu_HSDPAL1_To_Raw_Throu_Thresh This threshold is used to set the value under which the ratio between L1 HS Throughput average and Raw HS Throughput average is considered low enough to assign the cause of Low Net HS Throughput not only to lack of data sent by the network. The average of the Throughput values is calculated on the 5 secs.3. NOTE: the threshold is expressed as the ratio (0. NOTE: the threshold is expressed as the ratio (0. 20.. before the occurrence of the Low Net Throughput event).4. See more information about this threshold in the help under "HSPA Low Raw Throughput". 20. before the occurrence of a failure event).com . The average of the Throughput values is calculated on the 5 secs.2 Uu_HSDPAAvRegularSched_Thresh This threshold is used to set the value under which the average HS Scheduling is a possible sign of regular scheduling in presence of other HSPA users (average calculated on the 5 secs. but for example due to high retransmission levels.6.actix.. and Uu_HSDPA_Throughput_L1 and Uu_HSDPA_Throughput_MAC for a definition of L1 and Net HS throughput.1). NOTE: the threshold is expressed as a percentage value (0.100). but for example due to high retransmission levels. See also Uu_HSDPALowNetThrou_Thresh and Uu_HSDPALowThrouMaxTimeWin_Thres for the exact definition of the Low Net HS Throughput event. NOTE: the threshold is expressed as the ratio (0. 20. before the occurrence of the Low Net Throughput event). before the occurrence of a failure event).4 HSDPA / Spotlight Thresholds 20. The default value is 70%.3.6.3.6.1).. See more information about this threshold under "HSPA Call Drop". 20.

5 SL_UMTS_DT_Spotlight_CriticalIssues_HSDPAPeakTput This threshold is used to filter out HSDPA Raw Tput peak performance issues from the HSPA dashboard that are equal or less this value. www.actix. The default value is 0.7.6.com . The default value is 1500 (kbps).Actix Spotlight Desktop User Guide November 2012 238 for the exact definition of the Low Net HS Throughput event. 20. and Uu_HSDPA_Throughput_L1 and Uu_HSDPA_PayloadRate_L1 for a definition of L1 and Raw HS throughput.4.

above which the CS Fallback call drop rate is considered too high.1. Recommended value is 5.1. KPIs and diagnoses 21. 21. 21.1 LTE thresholds 21. 21. above which the RRC handover failure rate is considered too high.actix.com .1.1.1. above which the RRC re-establishment failure rate is considered too high. 21. Recommended value is 5.1.8 LTE_CA_RRC_Drop_Rate_Threshold This is the threshold in percent.9 LTE_CA_Slow_RRC_Setup_Rate_Threshold This threshold is used in conjunction with the RRC Setup Time threshold.1. and is the target above which too many CSFB call setups in a cluster are seen as too slow.2 LTE_CA_CSFB_Drop_Rate_Threshold This is the threshold in percent. Recommended value is 10. above which the RRC connection setup failure rate is considered too high.1. Recommended value is 3. 21.1.1.1. 21.1 LTE / Cluster_Acceptance 21. www.1. 21.4 LTE_CA_CSFB_Slow_Setup_Threshold This is the threshold in milliseconds.1.6 LTE_CA_ReEst_Failure_Rate_Threshold This is the threshold in percent. Recommended value is 3.3 LTE_CA_CSFB_Slow_Setup_Rate_Threshold This threshold is used in conjunction with the CSFB Slow Setup threshold. above which the RRC connection drop rate is considered too high. Recommended value is 10. above which the CS Fallback call setup failure rate is considered too high. above which a CS Fallback call setup time is considered too long. 21.1.1.1. and is the target above which too many RRC connection setups in a cluster are seen as too slow.1.1.7 LTE_CA_RRC_Block_Rate_Threshold This is the threshold in percent.1 LTE_CA_CSFB_Block_Rate_Threshold This is the threshold in percent.1. Recommended value is 3.Actix Spotlight Desktop User Guide November 2012 239 21 Appendix I: LTE thresholds.5 LTE_CA_HO_Failure_Rate_Threshold This is the threshold in percent. Recommended value is 10. Recommended value is 8000.

1. Recommended value is 10.13 LTE_CA_TaskUL_Failure_Rate_Threshold This is the threshold in percent.1.12 LTE_CA_TaskDL_LowTput_Rate_Threshold This is the threshold in percent.1.1.1.1.1.1. Recommended value is 5.1.1 LTE_CSFB_LTEReAttach_Timer This threshold is the maximum time in milliseconds above which the Attach procedure on LTE following a CS fallback procedure is considered too slow. Recommended value is 10.16 LTE_CA_UE_GoodRSRP_Rate_Threshold This threshold is used in conjunction with the RSRP coverage threshold. above which the percentage of uplink tasks that did not achieve an acceptable throughput is considered too high. and is the target above which the signal quality in a cluster is seen as acceptable.1. Recommended value is 95.Actix Spotlight Desktop User Guide November 2012 240 21. 21. above which the percentage of uplink tasks that did not achieve an acceptable throughput is considered too high. 21. Recommended value is 95. Recommended value is 90. Recommended value is 5. above which the uplink tasks failure rate is considered too high. above which a LTE connection setup time is considered too long.1.15 LTE_CA_UE_GoodCoverage_Rate_Threshold This threshold is used in conjunction with RSRP and RSRQ coverage thresholds. Recommended value is 60.2.11 LTE_CA_TaskDL_Failure_Rate_Threshold This is the threshold in percent.2 LTE_CSFB_LTEReselection_Timer This threshold is the maximum time in milliseconds above which the reselection procedure from UMTS Idle to LTE following a CS fallback procedure is considered www. Recommended value is 1000 ms. 21. 21. 21.1. 21.14 LTE_CA_TaskUL_LowTput_Rate_Threshold This is the threshold in percent.actix. A value of 0 means that the procedure cannot fail because of timeout. 21. above which the downlink tasks failure rate is considered too high.17 LTE_CA_UE_GoodRSRQ_Rate_Threshold This threshold is used in conjunction with the RSRQ coverage threshold.1.1. and is the target above which the signal strength in a cluster is seen as acceptable.1.com . 21.10 LTE_CA_Slow_RRC_Setup_Threshold This is the threshold in milliseconds.1.2.2 LTE / Event_Control 21. 21. and is the target above which coverage in a cluster is seen as acceptable.1.1.1.

The default value is 1.6 LTE_HO_Drop_timer Analyzer pegs a LTE handover fail event if the LTE RRC connection drops after a RRC Reconfiguration message that triggered a handover. 21.2. This threshold is the maximum time after which a measurement report message where the Serving cell is weaker in terms of RSRP than the best neighbor cell is considered to be old to be the cause of a handover. Recommended value is 15000 ms. A value of 0 means that the reselection to LTE is always considered successful regardless of how much time it took.com .1. Analyzer may also peg a handover fail event if the RRC connection drops shortly after the handover completion.1. Recommended value is 6000 ms. and set the call start time to the time of the RRC Connection Request message if the call was initiated in Idle mode. 21. then Analyzer will detect the initiation of the call at the last logging tool marker indicating a call setup attempt preceding the Extended Service Request message. 21. 21. If this threshold is set to 0.1.1. The handover is considered successful after a handover completion (RRC Connection Reconfiguration Complete message) when this timer expires and the RRC connection did not drop.7 LTE_NAS_wait_timer When two LTE NAS messages of the same type (for instance EMM Attach Request) are logged consecutively in a file.8 LTE_Redirection_fromUMTS_timer Analyzer measures the time elapsed from the RRC Connection Release message which redirects the UE to from UMTS to LTE.4 LTE_CSFB_OnlyUseProtocolMsgs This threshold controls whether Analyzer should only use protocol messages when setting CS fallback events.1. This threshold is the time in milliseconds measured from the RRC Reconfiguration message during which Analyzer pegs a handover failure if the RRC connection drops.2. A value of 0 means that that the time is measured from the time when the UE entered UMTS Idle mode. then the redirected cell www. The unit is milliseconds. Recommended value is 2000 ms.1. 21.5 LTE_HO_Attempt_timer Analyzer measures the time in milliseconds it took to perform a handover as the time from the last measurement report message where the Serving cell is weaker in terms of RSRP or RSRQ than the best neighbor cell. Recommended value is 2000 ms.2. this threshold is used to determine whether the second LTE NAS message is a duplicate of the first message or whether the procedure initiated by the first LTE NAS message failed and the procedure is attempted another time.actix.2.Actix Spotlight Desktop User Guide November 2012 241 too slow. A value of 1 (the default value) means that the time is measured from the time when the UE received UMTS System Information Block 19. 21.2.3 LTE_CSFB_LTEReselection_Trigger This threshold controls the starting point at which the time to reselect LTE from UMTS Idle is measured. or if the UE receives a DL-DCCH message.2. and if this time exceeds the value of this threshold and the UE is still in UMTS mode.

and if this time exceeds the value of this threshold and the UE is still in LTE mode.2.3. 21.1 SL_LTE_DT_Spotlight_ImportantIssues_Threshold This threshold is used to filter out Important Issues from the LTE dashboard that occur with a frequency greater than this value. a value of 1 means that Analyzer pegs an LTE RRC drop following a successful Detach procedure if the RRC Connection Release message is not logged.4. www.actix. This default value is overwritten if T300 is present in the log file.3 LTE / Scan_Coverage 21. Recommended value is -95 dBm and the minimum should not be lower than -105 dBm.3. Recommended value is 1000 ms.2.1.1.1. 21. 21.10 LTE_Redirection_toUMTS_timer Analyzer measures the time elapsed from the RRC Connection Release message which redirects the UE to UMTS.11 LTE_RRC_DropAfterDetach This threshold indicates whether Analyzer may peg an LTE RRC drop event following a successful Detach procedure.1. This timer is disabled if its value is set to 0. 21.2.9 LTE_Redirection_toCDMA2000_timer Analyzer measures the time elapsed from the RRC Connection Release message which redirects the UE to CDMA2000. 21.2 LTE_Scan_PoorRSRQ_Threshold This threshold is used to indicate poor RSRQ values from scanner data. This timer is disabled if its value is set to 0. A value of 0 (the default value) means that Analyzer never pegs an LTE RRC drop event following a successful Detach procedure.2.12 LTE_t300_wait_timer This threshold is the default value in milliseconds that the event detection uses for LTE RRC timer T300. Recommended value is 0. 21. then the redirected cell reselection procedure is considered failed.1. and if this time exceeds the value of this threshold and the UE is still in LTE mode. This timer is disabled if its value is set to 0.1.4 LTE / Spotlight 21. then the redirected cell reselection procedure is considered failed.com .1 LTE_Scan_PoorRSRP_Threshold This threshold is used to indicate poor RSRP values from scanner data.1.1.Actix Spotlight Desktop User Guide November 2012 242 reselection procedure is considered failed.1. Recommended value is -13 dB and the value should range between -10 and -18 dB. 21.

1.1. Values should vary between -10 and -18 dB.2 LTE_CT thresholds These Call Trace thresholds are mainly for use with ActixOne. Recommended value is 10 dBm. 21. The units are in percent and the default value is 5%.2.actix. 21.1 LTE_UE_HighPUCCHPower_Threshold This threshold is used to indicate high PUCCH transmit power values from UE data.5 LTE / UE_Coverage 21.2 LTE_CT_CA_CSFB_Redirection_Fail_Rate_Threshold This is the threshold above which the CS fall back redirection failure rate is considered too high. The units are in percent and the default is 5%.7 LTE_CT_CA_RRC_Block_Rate_Threshold This is the threshold above which the RRC setup failure rate is considered too high.1.1.1.Actix Spotlight Desktop User Guide November 2012 243 21. 21.com .2 LTE_UE_PoorRSRP_Threshold This threshold is used to indicate poor RSRP values from scanner data. 21.1. Recommended value is -13 dB.6 LTE_CT_CA_IFHO_Failure_Rate_Threshold This is the threshold above which the RRC handover failure rate is considered too high.2.1.2.2.1.5. 21.2. www.3 LTE_CT_CA_Detach_Fail_Rate_Threshold This is the threshold in percent above which the Detach failure rate is considered too high.2.1 LTE_CT_CA_Attach_Fail_Rate_Threshold This is the threshold in percent above which the Attach failure rate is considered too high. The units are in percent and the recommended value is 3%.1.4 LTE_CT_CA_EPS_Procedure_Fail_Rate_Threshold This is the threshold above which the EPS activation or modification failure rate is considered too high.3 LTE_UE_PoorRSRQ_Threshold This threshold is used to indicate poor RSRQ values from UE data. 21.1. Recommended value is -110 dBm.5. and the minimum value should not be lower than -120 dBm. The units are in percent and the default value is 3%. 21. The units are in percent and the recommended value is 3%. The units are in percent and the default value is 5%.1.1 Cluster_Acceptance_Procedures 21. 21. 21.2.5.2. Values should vary between 0 and 20 dBm. 21.5 LTE_CT_CA_HO_Failure_Rate_Threshold This is the threshold above which the RRC handover failure rate is considered too high. The units are in percent and the default is 5%.

The units are milliseconds and the default is 60.12 LTE_CT_CA_Slow_CSFB_Redirection_Threshold This threshold is the time above which a CS fall back redirection procedure is considered too slow.16 LTE_CT_CA_Slow_EPS_Procedure_Threshold This threshold is the time above which an EPS activation or modification procedure is considered too slow.actix.1.2.2. 21.2. 21.1.9 LTE_CT_CA_Slow_Attach_Rate_Threshold This threshold is used in conjunction with the slow Attach threshold.15 LTE_CT_CA_Slow_EPS_Procedure_Rate_Threshold This threshold is used in conjunction with the slow EPS procedure threshold.1. 21.com . and is the target above which too many EPS procedures in a cluster are seen as too slow. The units are milliseconds and the default value is 60.1.1. The units are in percent and the recommended value is 5%.2. and is the target above which too many Attach procedures in a cluster are seen as too slow.1.10 LTE_CT_CA_Slow_Attach_Threshold This threshold is the time above which an Attach procedure is considered too slow. 21. www.2. 21.2. 21.17 LTE_CT_CA_Slow_HO_Rate_Threshold This threshold is used in conjunction with the slow handover threshold.2. The units are in percent and the default value is 10%. The units are milliseconds and the default value is 60. 21. The units are milliseconds and the default is 50.1. and is the target above which too many CS fall back redirection procedures in a cluster are seen as too slow. and is the target above which too many Attach procedures in a cluster are seen as too slow. The units are in percent and the default is 10%. 21.8 LTE_CT_CA_RRC_Drop_Rate_Threshold This is the threshold above which the RRC connection drop rate is considered too high.1.2.13 LTE_CT_CA_Slow_Detach_Rate_Threshold This threshold is used in conjunction with the slow Detach threshold.1. and is the target above which too many intra-frequency handover procedures in a cluster are seen as too slow.11 LTE_CT_CA_Slow_CSFB_Redirection_Rate_Threshold This threshold is used in conjunction with the slow CS fall back redirection threshold.2.Actix Spotlight Desktop User Guide November 2012 244 21. The units are in percent and the default value is 10.2.1. The units are in percent and the recommended value is 10%. 21.14 LTE_CT_CA_Slow_Detach_Threshold This threshold is the time above which an Detach procedure is considered too slow. The units are in percent and the default is 10%.

21 LTE_CT_CA_Slow_RRC_Setup_Rate_Threshold This threshold is used in conjunction with the slow RRC setup threshold.2. The units are in percent and the recommended value is 10.22 LTE_CT_CA_Slow_RRC_Setup_Threshold This threshold is the time above which a RRC Connection setup procedure is considered too slow.2 Cluster_Acceptance_Radio 21.24 LTE_CT_CA_Slow_TAU_Threshold This threshold is the time above which a Tracking Area Update procedure is considered too slow.1.1. The units are milliseconds and the recommended value is 300. The units are in percent and the default is 10%.18 LTE_CT_CA_Slow_HO_Threshold This threshold is the time above which an intra-frequency handover procedure is considered too slow. 21.2.2.actix.20 LTE_CT_CA_Slow_IFHO_Threshold This threshold is the time above which an inter-frequency handover procedure is considered too slow. 21.Actix Spotlight Desktop User Guide November 2012 245 21. and is the target above which too many inter-frequency handover procedures in a cluster are seen as too slow.2.com .1 LTE_CT_CA_DL_High_Nack_Rate_Threshold This threshold is used in conjunction with the "high Nack" threshold. The units are in percent and the default value is 10. The units are in percent and the default is 5%. 21.1.2. 21.2. The units are in percent and the recommended value is 5%.25 LTE_CT_CA_TAU_Fail_Rate_Threshold This is the threshold above which the Tracking Area Update failure rate is considered too high. and is the target above which too many HARQ Nack rate measurements in a cluster are seen as too high.2. The units are milliseconds and the default value is 60. 21. www. and is the target above which too many Tracking Area Update procedures in a cluster are seen as too slow. The units are milliseconds and the default is 300. and is the target above which too many RRC connection setup procedures in a cluster are seen as too slow.1. 21. The units are milliseconds and the recommended value is 60.1.1.2. 21.1.23 LTE_CT_CA_Slow_TAU_Rate_Threshold This threshold is used in conjunction with the slow Tracking Area Update threshold.1.2. 21.2.2.19 LTE_CT_CA_Slow_IFHO_Rate_Threshold This threshold is used in conjunction with the slow handover threshold.

21.Actix Spotlight Desktop User Guide November 2012 246 21. The units are in percent and the default is 20%. 21.2. and is the target above which too many throughput measurements in a cluster are seen as too low.2. The units are in percent and the default is 100% 21. and is the target above which too many HARQ Nack rate measurements in a cluster are seen as too high.2.6 LTE_CT_CA_DL_Low_Tput_Rate_Threshold This threshold is used in conjunction with the low throughput threshold.2 LTE_CT_CA_DL_High_Nack_Threshold This threshold is the average HARQ Nack rate value above which the average HARQ Nack rate is considered too high. The units are in Kbps and the default value is 100.2. Units are in percent and the default is 20%.2.3 LTE_CT_CA_DL_Low_CQI_Rate_Threshold This threshold is used in conjunction with the low CQI threshold.2. The units are in percent and the default value is 10.2.2. This threshold is the downlink throughput value below which the downlink throughput is ignored. for instance during signaling procedures) and high throughput values corresponding to periods of time where the UE is transferring user data (for instance web browsing).2.9 LTE_CT_CA_UL_High_Nack_Threshold This threshold is the average HARQ Nack rate value above which the average HARQ Nack rate is considered too high.2. 21. there is a mix of low throughput values (corresponding to periods of time where the UE is not transferring user data. above which the downlink throughput is considered too low.2.actix.2.7 LTE_CT_CA_DL_Low_Tput_Threshold This threshold is the downlink throughput value.2.8 LTE_CT_CA_UL_High_Nack_Rate_Threshold This threshold is used in conjunction with the "high Nack" threshold.5 LTE_CT_CA_DL_Low_Tput_Ignore_Threshold In a typical RRC connection. and is the target above which too many CQI measurements in a cluster are seen as too low. there is a mix of low throughput values (corresponding to periods of time where the UE is not transferring user data.2. 21.2. The units are in Kbps and the default value is 1000.10 LTE_CT_CA_UL_Low_Tput_Ignore_Threshold In a typical RRC connection. 21.2.2.com . The default value is 5.2. It may be useful to provide throughput statistics only considering throughput samples that are above a certain value. for instance during signaling procedures) and high throughput values corresponding to periods of time where the UE is transferring user data (for instance web www.4 LTE_CT_CA_DL_Low_CQI_Threshold This threshold is the average CQI value below which the average CQI is considered too low. 21. The units are in percent and the default is 20%. 21.

3 Spotlight thresholds 21.12 LTE_CT_CA_UL_Low_Tput_Threshold This threshold is the uplink throughput value above which the uplink throughput is considered too low.com . The units are in percent and the default is 10% 21.2.actix. 21.2. It may be useful to provide throughput statistics only considering throughput samples that are above a certain value.2. The units are Kbps and the default is 50. This threshold is the uplink throughput value below which the uplink throughput is ignored.1 SL_Overspill_Dist_Threshold This threshold is used (for all Cell Coverage analyses) if there is no Max_ServerDist information in the cellref and indicates the maximum serving distance (in meters) a cell should serve.1. 21.1 Spotlight 21.2. and is the target above which too many throughput measurements in a cluster are seen as too low. Default is 5000m. 21.3.11 LTE_CT_CA_UL_Low_Tput_Rate_Threshold This threshold is used in conjunction with the low throughput threshold. The units are Kbps and the default is 500.3.Actix Spotlight Desktop User Guide November 2012 247 browsing).4 LTE events in the Event Explorer Connections # Dropped Connections # Failed Connection # Attach Failures Handover # Failed Handover # Slow Handover IRAT UMTS # Redirection to UMTS OK # Redirection to UMTS Failures # Handover to UMTS OK # Handover to UMTS Failures # Redirection from UMTS OK # Redirection from UMTS Failures # Redirection to UMTS Time IRAT CDMA2000 # Redirection to CDMA2000 OK # Redirection to CDMA2000 Failures www.

www.Actix Spotlight Desktop User Guide November 2012 248 21.5 RRC Drop diagnosis for LTE The following diagram outlines the procedure used by Spotlight to determine the diagnosis of RRC Drop events.actix.com .

and therefore no reliable diagnosis can be made.Actix Spotlight Desktop User Guide November 2012 249 Diagnosis No radio messaging Condition and notes Analyzer detected that the UE dropped from ‘LTE connected’ mode to ‘LTE idle’ mode but there were not enough messages (for instance.com . LTE ANR Failure Missing handover Poor coverage Interference Handover fail Limited coverage UL Investigate Further (unknown diagnosis) www. The UE reported that another intra-frequency or interfrequency LTE cell was better than its serving cell. The UE reported that another intra-frequency and interfrequency LTE cell was better than its serving cell. in an LTE RRC measurement report message that was not followed by a handover procedure.actix. The LTE RRC drop occurred within the time threshold “LTE>Event_control>LTE_HO_Drop_timer” of a LTE RRC connection reconfiguration message for a handover procedure. The serving cell RSRQ was less than the threshold value “LTE>UE_Coverage>LTE_UE_PoorRSRQ _Threshold”. in terms of RSRP or RSRQ. in an LTE RRC measurement report message that was not followed by a handover procedure (with an LTE RRC connection reconfiguration message). The serving cell RSRP was less than the threshold value “LTE>UE_Coverage>LTE_UE_PoorRSRP _Threshold”. Just before the drop. This may indicate a logging tool malfunction. in terms of RSRP or RSRQ. RRC messages) to detect within 5 seconds when the drop occurred. the PUCCH or PRACH transmit power was greater than the threshold value "LTE>UE_Coverage>LTE_UE_HighPUCCHPower_Threshold". Use other tools and views to refine your understanding of the problem. Instead the UE received an RRC connection reconfiguration message requesting to measure the CGI (cell global identity) of the best cell reported in the measurement report message.

Actix Spotlight Desktop User Guide November 2012 250 21.6 LTE IRAT Missing Neighbor analysis The purpose of the LTE inter-RAT missing neighbor analysis is to help building the GSM and UMTS neighbor list for LTE cells.actix. www. Spotlight determines the best LTE sector for each EARFCN. Spotlight requires the following: LTE data: this can be either LTE scanner or LTE handset data. GSM and/or UMTS scanner data. either from scanner data or handset data. This inter-RAT neighbor list is required by the network so that it can inform the UE of which GSM and/or UMTS it should measure to support handovers from LTE to other technologies. The process is as follows: For each location bin.com . A cellrefs files with up-to-date LTE network information. For this analysis.

Spotlight has established the list of LTE cells that where best cells and met the missing neighbor criteria in at least one bin. Spotlight increments a counter by 1 for the cell and checks for missing. and for each of these bins the list of GSM and UMTS cells that met the missing neighbor criteria. Cell removal criteria: if an IRAT cell (that is already defined as a neighbor) is detected as a missing neighbor less than this number of times. then Spotlight will only use the scanner data. As an example for an LTE cell "LTE_Cell_1" that was best LTE cell and met the missing neighbor criteria in 10 bins we could get the following results: IRAT cell Number of bins where missing neighbor criteria are met 9 7 2 8 1 Percentage of bins where missing neighbor criteria are met 90% 70% 20% 80% 10% UMTS_Cell_1 UMTS_Cell_2 UMTS_Cell_3 GSM_Cell_1 GSM_Cell_2 Cell addition criteria: if an IRAT cell is detected as a missing neighbor this number of times or more. the cell will be removed from the neighbor list. If that cell meets the missing neighbor criteria.actix. www.com . Spotlight also determines the list of GSM and UMTS sectors measured that met the missing neighbor criteria. For each location bin where the best LTE cell met the missing neighbor criteria. the cell will be added to the neighbor list. At the end of this procedure.Actix Spotlight Desktop User Guide November 2012 251 Note that if both scanner and handset data are available.

1.1. 22. Recommended value is -15dB and the value should be between -18 and -10 dB.1 SL_Overspill_Dist_Threshold This threshold is used.1. 22.1.1.2 UMTS / Scan_coverage 22.2.com .1. Recommended value is 3 and the value should be between 2 and 4. diagnosis and display of data in Spotlight. Recommended value is -15 dB and should lie between -18 and -10 dB. 22. 22. simply click on the associated number and type in the new value. The default value is -100 dBm.2.actix.1 UMTS thresholds You can modify threshold values for event detection using the Tools.2.1. When 4 or more pilots are above this threshold.3 Uu_Scan_PilotPollutionThreshold In calculating Pilot Pollution. this threshold sets up the level of interference required for pegging the events (based on scanner info). KPIs and diagnoses 22.4 Uu_Scan_Poor_EcNoThreshold This is used to indicate poor EcIo values from scanner data.Actix Spotlight Desktop User Guide November 2012 252 22 Appendix J: UMTS thresholds. Default is 5000m.1.2 Uu_Scan_PilotPollution_RSCP_Threshold The RSCP threshold used by the “Poor Interference with Strong Signal Strength” pilot pollution model (a Veritune feature). 22.1 Spotlight 22. Recommended value is -95 dBm and should not be lower than -105 dBm. To modify the value.2.2. 22.1. it creates a pilot pollution event. Display Thresholds command. It is important to set your thresholds before loading the data because it will affect the analysis.1 Uu_Scan_PilotPollution_Count_Threshold This is the absolute number of pilots (with Ec/Ios above Uu_Scan_PilotPollutionThreshold) required to trigger a pilot pollution event. if there is no Max_ServerDist information in the cellref and indicates the maximum serving distance (in meters) a cell should serve. and the value should be between -90 and -110 dBm. www.5 Uu_Scan_Poor_RSCP_Threshold This is used to indicate poor RSCP values from scanner data.

1. 22. www.6 SL_MaxTimeBetweenRRC_REQandCallStart This threshold is used for determining UMTS CS calls with excessive setup time. Recommended value is 6000 ms. Recommended value is 3 and the value should be between 2 and 4. The default value is 50. The default value is -15 dB. a condition of which is that EcIo has dropped by at least this threshold value within the defined time window. The default value is 5 dB. The default value is -120 dBm.1.1. The default value is -104 dBm and the value should be between -90 and -110 dBm. used in the calculation of UL pathloss. used in the calculation of DL pathloss.actix. The default value is 10 dB.8 Uu_Scan_TooManyServersThreshold In calculating "Too Many Servers".1. 22.1. 22.3.4 dB.3.1 SL_Ant_Gain_Threshold This threshold is the default Antenna gain.1. 22. 22.2. 22.3.1.6 Uu_Scan_TooManyServers_Count_Threshold The absolute number of pilots (with Ec/Ios within Uu_Scan_TooManyServersThreshold of the Ec/Io of the best server) required to trigger a “too many servers” event (based on scanner info).3 UMTS / Spotlight 22. when 4 or more pilots (including the best server) are within the threshold value in dB of the best server. Recommended value is 5 dB and the minimum and the maximum should be around 1 and 10 dB. The default value is 18.1.3.3.1.2.7 Uu_Scan_TooManyServers_RSCP_Threshold The CPICH RSCP threshold above which a Uu_Scan_TooManyServers event may be pegged. 22.com .2.Actix Spotlight Desktop User Guide November 2012 253 22. 22.4 SL_Detectedset_EcIo_Threshold This threshold is used for determining if a detected set member strong enough to be consider as a neighbor.2 SL_BLER_Threshold This threshold is used for determining a UMTS ‘lost DL channel’ condition.3.1.5 SL_EIRP_Threshold This threshold is the default EIRP. 22.3 SL_BTS_Sens_Threshold This threshold is the default BTS receive Sensitivity.7 SL_RapidPathloss_EcIo_Threshold This threshold is used in Rapid Pathloss detection. used in the calculation of pathloss.3. The RSCP condition must also be met for Rapid Pathloss to be detected.1. it creates a "too many server" event (based on scanner info).

1.1. Values should lie between 0 and 25 dBm.3.3.1 Uu_CoverageLimitedUE_TxPowerThreshold This is used in the Coverage Limited event. 22. If the UeTransmittedPower is greater than Uu_CoverageLimitedUE_TxPowerThreshold AND the CPICH_RSCP_in_ActiveSet is less than Uu_Poor_RSCP_Threshold AND the CPICH_EcNo_in_ActiveSet is less than Uu_Poor_EcNoThreshold. 22. The minimum should not be lower than 0 and the maximum should not be higher than 25 dBm.1. Recommended value is 15 dBm. Recommended value is -15 dB.1.Actix Spotlight Desktop User Guide November 2012 254 22.actix.4 UMTS / UE_Coverage 22.com . 22.3. The default value is 5.1. Recommended value is 0.3. then a Coverage Limited event will appear on the map. a condition of which is that RSCP has dropped by at least this threshold value within the defined time window. The EcIo condition must also be met for Rapid Pathloss to be detected. and only data within this distance from the site is considered for the analysis.8 SL_RapidPathloss_RSCP_Threshold This threshold is used in Rapid Pathloss detection.4.3.10 SL_Site_Issues_Dist_Threshold This threshold is used in the outside beamwidth analysis.3 Uu_HighUE_TxPower This is used in the Poor Uplink Coverage event.1. 22.2 Uu_EcNoInterferenceThreshold This is used in conjunction with the RSCP Interference Threshold for the System Interference event. Values should lie between -10 and -18 dBm. 22.9 SL_RapidPathloss_Time_window_Threshold This threshold is used to define the window over which Rapid Pathloss is performed. www. 22.1. If the CPICH_RSCP_in_ActiveSet is greater than Uu_RSCP_Interference_Threshold and the CPICH_EcNo_In_ActiveSet is less than Uu_EcNoInterferenceThreshold. If the UeTransmittedPower is greater than Uu_HighUE_TxPower AND the CPICH_RSCP_in_ActiveSet is greater than Uu_Poor_RSCP_Threshold AND the CPICH_EcNo_in_ActiveSet is greater than Uu_Poor_EcNoThreshold. The default value is 3000 ms. Recommended value is 10 dBm.4. 22. then Poor Uplink Coverage will appear on the map.1. The default value is 5000m.11 SL_UMTS_DT_Troubleshooter_CriticalIssues_Threshold This threshold is used to filter out critical issues from the UMTS dashboard that are equal or less then this value.12 SL_UMTS_DT_Troubleshooter_ImportantIssues_Threshold This threshold is used to filter out Important issues from the UMTS dashboard that are equal or less then this value. then a System Interference event appears on the map. Recommended value is 0.4.1.

22. Other conditions must be satisfied for these events to occur please note the other thresholds involved.5 Uu_PilotPollutionThreshold In calculating Pilot Pollution. If the UeTransmittedPower is less than Uu_LowUE_TxPower AND the CPICH_RSCP_in_ActiveSet is less than Uu_Poor_RSCP_Threshold AND the CPICH_EcNo_in_ActiveSet is less than Uu_PoorEcNoThreshold. When 4 or more pilots are above this threshold. In the cases where CPICH_RSCP_in_ActiveSet is lower than Uu_Poor_RSCP_Threshold. it will trigger either a Coverage Limited event or a Poor Downlink Coverage event. Recommended value is -15 dB and should lie between -18 and -10 dB. Values should lie between -30 and 0 dBm.4.1. Recommended value is 5 dB and the minimum and the maximum should be around 1 and 10 dB. 22.1.4. 22.7 Uu_Poor_RSCP_Threshold This is used in three different events.1. then the Poor Downlink Coverage event will appear on the map. www. it creates a "too many server" event (based on scanner info). Recommended value is -80 dBm and should lie between -90 and -60 dBm.Actix Spotlight Desktop User Guide November 2012 255 22.4.1.6 Uu_Poor_EcNoThreshold This is used in the Coverage Limited event. If the CPICH_RSCP_in_ActiveSet is greater than this threshold and the CPICH_EcNo_in_ActiveSet is less than Uu_Poor_EcNoThreshold. it creates a Pilot Pollution event. 22. Recommended value is -15 dB and should lie between -18 and -10 dB. If the CPICH_EcNo_in_ActiveSet is less than Uu_PoorEcNOThreshold AND CPICH_RSCP_in_ActiveSet is less than Uu_Poor_RSCP_Threshold AND Ue_TransmittedPower is greater than Uu_CoverageLimitedUE_TxPowerThreshold.4. this threshold sets up the level of interference required for pegging the events.4 Uu_LowUE_TxPower This is used in the Poor Downlink Coverage event. In the case where it is greater than Uu_Poor_RSCP_Threshold.8 Uu_RSCP_InterferenceThreshold This is used for the System Interference event.4. when 4 or more pilots (including the best server) are within the threshold value in dB of the best server. then a System Interference event appears on the map. Recommended value is -15 dBm. It is also used in the Poor Uplink and Downlink Coverage event. then a Coverage Limited event will appear on the map. 22. it will trigger a Poor Uplink Coverage event.9 Uu_TooManyServersThreshold In calculating "Too Many Servers".actix.4. Recommended value is -95 dBm and should not be lower than -105 dBm.1.1.com .

determined from the RRC signaling. or weaker by less than "Uu_Scan_UE_dB_Threshold" decibels. This is the number of times the event Uu_UE_Scan_Issue is set.2 UMTS events in the Event Explorer Circuit Switched KPIs # Call Attempts # Dropped Calls Truncated Calls Drops # Setup Failures # Excessive Call Setup Packet Switched KPIs # PS Attempts # Dropped PS # Failed Connection Handover Issues % Handoff Overhead Based on measurements made when the UE is in RRC connected mode. 2 or more cells in the active set) to the time the UE spent with only 1 active cell. Furthermore. # AS Fail (Active Set Failures) This is the ratio of the number of active set update failures to the total number of active set update procedures. Note that this statistic needs a valid cellrefs file in order to work correctly. The number of active set update procedures is determined from the RRC signaling. # AS Att (Active Set Attempts) This is the number of active set update procedures.com .e. # Server Inconsist. this statistic gives the ratio (as a percentage) of the time the UE spent in handover (i. This event is set when the best cell measured by the scanner is not measured by the UE as an active or monitored cell over a period of time of "Uu_Scan_UE_Timer" milliseconds. www.Actix Spotlight Desktop User Guide November 2012 256 22.actix. and The scanner's best cell is stronger than the best cell in the active set. and the number of active set update failures corresponds to the number of active set update procedures for which the UE sends an RRC Active Set Update Failure message. this event is only set if the following conditions are met:   The UE is in RRC connected mode.

Actix Spotlight Desktop User Guide November 2012 257 The thresholds "Uu_Scan_UE_Timer" and "Uu_Scan_UE_dB_Threshold" are configurable using Tools > Display Thresholds > UMTS > Event Control.actix. Hard Handover Issues # 3G 2G Attempts # 3G 2G Failures # 3G 2G OK # IF Attempts # IF Failures www.com .

Note that the window size used to evaluate the condition is the period from 5 seconds before the drop.com .Actix Spotlight Desktop User Guide November 2012 258 22.actix. up to the drop itself. www.3 Dropped Calls diagnosis for UMTS The following diagram outlines Spotlight's procedure for determining a diagnosis of CS and PS Dropped Call events.

Multiple Active Set update messages are received and a particular SC is not added to the Active Set. CPICH_EcNo_in_ActiveSet > Uu_Poor_EcNoThreshold (-15 dB) AND CPICH_RSCP_in_ActiveSet > Uu_Poor_RSCP_Threshold (-95 dBm) AND UeTransmittedPower > Uu_HighUE_TxPower (15 dBm). Coverage Limitation Problem Poor DL Coverage Problem Poor UL Coverage Problem Lost DL Channel Investigate Further (unknown diagnosis) www. For the Raked RF Condition. CPICH_EcNo_in_ActiveSet < Uu_EcNoInterferenceThreshold (-15 dB) AND CPICH_RSCP_in_ActiveSet > Uu_RSCP_InterferenceThreshold (-80 dBm). More investigation is needed. Use other tools and views to refine your understanding of the problem. CPICH_EcNo_in_ActiveSet < Uu_Poor_EcNoThreshold (-15 dB) AND CPICH_RSCP_in_ActiveSet < Uu_Poor_RSCP_Threshold (-95 dBm) AND UeTransmittedPower > Uu_CoverageLimitedUE_TxPowerThreshold (10 dBm). providing it is higher than the specified threshold: Pilot Pollution Pilot Pollution: Too Many Servers Interference Problem 4+ pilots in Active or Monitored Set with Ec/No > Uu_PilotPollutionThreshold (-15 dB). on average. SC in Active Set after event < > SCs in Active Set and Neighbor list before event. Uu_Trch_DownlinkBLERAGG > SL_BLER_Threshold.Actix Spotlight Desktop User Guide November 2012 259 Diagnosis System Released Missing Neighbor Handover Problem Condition and notes When the cause code is Not Normal (0-31.com . CPICH_EcNo_in_ActiveSet < Uu_PoorEcNoThreshold (-15 dB) AND CPICH_RSCP_in_ActiveSet < Uu_Poor_RSCP_Threshold (-95 dBm) AND UeTransmittedPower < Uu_LowUE_TxPower (-15 dBm).actix. 42) in either the NAS message or the RRC message. the system picks the diagnosis with the highest value. 4+ pilots in the Active or Monitored Set with Ec/No within Uu_TooManyServersThreshold dB of the best server (Uu_ActiveSet_EcNo_0). Over 5-seconds.

actix.Actix Spotlight Desktop User Guide November 2012 260 22.com .4 Call Setup Failure diagnosis for UMTS The following diagram shows the procedure used by Spotlight to determine the diagnosis of CS and PS Call Setup Failure events: www.

CPICH_EcNo_in_ActiveSet > Uu_Poor_EcNoThreshold (-15 dB) AND CPICH_RSCP_in_ActiveSet > Uu_Poor_RSCP_Threshold (-95 dBm) AND UeTransmittedPower > Uu_HighUE_TxPower (15 dBm). CPICH_EcNo_in_ActiveSet < Uu_Poor_EcNoThreshold (-15 dB) AND CPICH_RSCP_in_ActiveSet < Uu_Poor_RSCP_Threshold (-95 dBm) AND UeTransmittedPower > Uu_CoverageLimitedUE_TxPowerThreshold (10 dBm). Over 5-seconds. providing it is higher than the specified threshold: Pilot Pollution Pilot Pollution: Too Many Servers Interference Problem 4+ pilots in Active or Monitored Set with Ec/No > Uu_PilotPollutionThreshold (-15 dB). 42) in either the NAS message or the RRC message. CPICH_EcNo_in_ActiveSet < Uu_PoorEcNoThreshold (-15 dB) AND CPICH_RSCP_in_ActiveSet < Uu_Poor_RSCP_Threshold (-95 dBm) AND UeTransmittedPower < Uu_LowUE_TxPower (-15 dBm). Uu_Trch_DownlinkBLERAGG > SL_BLER_Threshold.com Limited Coverage Problem Poor DL Coverage Problem Poor UL Coverage Problem Lost DL Channel Investigate Further (unknown diagnosis) . When the cause code is Not Normal (0-31.actix. Use other tools and views to refine your understanding of the problem. SC in Active Set after event < > SCs in Active Set and Neighbor list before event. CPICH_EcNo_in_ActiveSet < Uu_EcNoInterferenceThreshold (-15 dB) AND CPICH_RSCP_in_ActiveSet > Uu_RSCP_InterferenceThreshold (-80 dBm).Actix Spotlight Desktop User Guide November 2012 261 Diagnosis System Rejected / RRC Failure CM Service Abort / Reject System Released Missing Neighbor Handover Problem Condition and notes When an RRC message contains an RRC Reject. www. the system picks the diagnosis with the highest value. A CM Service Abort / Reject message was received. For the Raked RF Condition. Multiple Active Set update messages are received and a particular SC is not added to the Active Set. 4+ pilots in the Active or Monitored Set with Ec/No within Uu_TooManyServersThreshold dB of the best server (Uu_ActiveSet_EcNo_0). on average.

www.actix.Actix Spotlight Desktop User Guide November 2012 262 22.5 Excessive Call diagnosis for UMTS The following diagram outlines the procedure used by Spotlight to determine the diagnosis of Excessive Call events. up to the drop itself. Note that the window size used to evaluate the condition is the period from 5 seconds before the drop.com .

www.actix.1 Hiding Analyzer Event Diagrams from Spotlight users Central tools teams may want to hide the details of particular KPI calculations from their Spotlight users. A checkbox enables this in the Diagram Info dialog in Analyzer. The checkbox is called ‘Hide diagram from read-only users’.com .Actix Spotlight Desktop User Guide November 2012 263 23 Appendix L: Information for Administrators 23. when defining event diagrams (license permitting).

133 drilldown window. 8 CDMA_AvgForwardFER. 187 CDMA_EVDO_DRCRate_0. 231 Average RSCP. 186 CDMA_ImportantIssue_RevLinkProblem. 63 Coverage Issue. 132 Dropped Call diagnosis for CDMA. 231 DL TCP Tput. 203 ConnectionAttemptSuccessRate_Threshold. 185 CDMA_ImportantIssue_FwdLinkProblem. 256 CM Service Abort / Reject. 211 Dragged_HO_Window. 186 CDMA_MobileRxPowerThreshold. 185 CDMA/EVDO Pilot Pollution. 37 Binned Data Queries. 203 B Batch Sector Plot. 185 CDMA_EcIoInterferenceThreshold. 201 ConnectionAttemptFailRate_Threshold. 186 CDMA_ImportantIssue_PoorCoverage. 203 AccessAttemptSuccessRate_Threshold. 186 CDMA_MobileTxPowerThreshold. 8 cellrefs file. 186. 200 D data files. 116 Data Settings link. 186 CDMA_OverAllSuccessRate. 231 CDMA_EVDO_PilotPollution_Count_Threshold. 186 CDMA_MobileTxPowerMaxFilterThreshold. 142 Circuit Switched KPIs. 185 CDMA_ImportantIssue_ExternalInterference. 187 CDMA_CallSetupSuccessRate. 188 CDMA_PilotPollutionThreshold. 63 binned data. 231 RSCP Tput. 217. 203 Add Device. 199 ConnectionAttemptDuration_Threshold. 188 CDMA_TooManyActivePNsThreshold. 185 CDMA_ImportantIssue_LowRX. 219 Attribute Picker. 28 Channel mode unacceptable. 47. 201 AccessAttemptFailRate_Threshold. 201 ConnectionReleaseSuccessRate_Threshold. 220 Dropped Calls diagnosis for UMTS. 29 DCHR99 mode. 200 CDMA_EVDO_TooManyActivePNsThreshold. 203 Average_TxRlpThputInst_Threshold. 205 www. 148 Average EcIo. 42. 217. 188 CDMA_CallDropRate. 200 CDMA_EVDO_PilotPollutionThreshold. 203 ConnectionReleaseDuration_Threshold.actix. 203 Average_RxTCHThroughput_Threshold. 258 Dropped Connection diagnosis for EVDO. 211 DRC Rate. 189 Dropped Calls diagnosis for GSM. 188 CDMA_CallSetupTime. 134 device filters. 62 Drill Down. 147 Choose Devices. 31 Data Service Analysis. 158 CDMA thresholds. 200 Average_Rx_RlpRetransmissionRate_Threshold. 259 Critical Issues section. 186 CDMA_MobileTxPowerMinFilterThreshold.Actix Spotlight Desktop User Guide November 2012 264 24 Index 9 95 95 95 95 95 percentile percentile percentile percentile percentile CQI Tput. 42 CDMA cell site parameters. 9. 50 A Abnormal Connection Release. 200 Average_Tx_RlpRetransmissionRate_Threshold. 188 CDMA_EcIoCombinedThreshold. 137 best serving cell. 42. 188 CDMA Neighbor List. 185. 135 Another Call Started. 231 Average_PER_Threshold. 202 CDMA_EVDO_MobileRxPowerThreshold. 144 Analyzer Classic. 8 CDMA Cell Coverage analysis. 127 Detailed Event Diagnostics. 131 Drilldown page. 187 CDMA_ImportantIssue_ExcessInterference. 54 CDMA Spotlight Report. 37 coverage design boundary. 216 Call Setup Failure diagnosis for UMTS. 148 binning settings. 153 CDMA events in the Event Explorer. 42 coverage footprint. 206 AccessAttemptDuration_Threshold.com . 231 EcIo Tput. 186. 203 Average_SINR_PN0_Threshold. 261 Co/Adjacent Channel allocations between neighbors. 8 CDMA Neighbor List analysis. 69 Distant Serving Cell. 260 CDMA Cell Coverage. 199 Dragged_Dominance_Hysteresis. 188 CDMA_PilotPollution_Count_Threshold. 47. 221 Choose Attributes. 149 C Call Setup Failure diagnosis for GSM. 187 cell coverage. 48 CDMA Pilot Pollution analysis. 201 CDMA_EVDO_EcIoInterferenceThreshold. 186 CDMA_ImportantIssue_PoorQuality. 47. determining. 145 Distance tab. 203 Consolidated_SINR_For_Nth_Best_Pilot[0]. 36 CSV file. 190 Coverage Limitation Problem. 231 MAC-HS Tput. 231 Average HSDPA Call Setup time. 203 Average_RxRlpThputInst_Threshold.

201 EVT_VerituneEVDOPilotPollution. 37 EDGE cell site parameters. 194 G_Distance_Max. 198 EGPRS events in the Event Explorer. 66 GSM/GPRS cell site parameters. 200 event detection. 212 G_ScanSortSigLevel_Min. 196 grade of service. 106 HSDPA Low Throughput example. 214 G_MsTxPowStepOrdered_Min. 256 Handover Problem. 8 EVDO Neighbor List analysis. 195 EGPRS_RLC_UL_Min. 58 EVDO thresholds. 161 EVDO System Performance analysis. 154 EGPRS diagnoses. 211 GSM visualization. 231 HSDPA Cell Coverage analysis. 42 EVDO events in the Event Explorer. 154 E EcIo_1stBest. 212 G_RxQualSub_Max. 93 HSDPA Call Drop rate. 47 GSM 2G Missing Neighbors.actix. 195 EGPRS_LLC_UL_Min. 231 HSDPA Spotlight Report. 214 G_Cell_Reselect_Duration. 201 EVT_EVDOServerKey. 236 HSDPA_NW_Acceptance_HSDPA_Drop_Rate. 233 HS mobility. 196 GPRS_LLC_DL_Min. 212 G_TimingAdvance_Max. 187 EVT_EVDOLowThroughput. 212 G_HandoverSuccessRate. 212 G_T3240_RAUTimer. 231. 196 GPRS_RLC_UL_Min. 63 GSM events in the Event Explorer. 236 HSDPA_NW_Acceptance_95_Percentile_RSCP_Thre shold. 29 Event Explorer. 257 High retransmissions due to packet incorrectly received in Downlink. 196 EGPRS thresholds. 8 GSM Cell Coverage analysis. 170 GSM thresholds. 187 EVT_CDMAServerKey. 233 High retransmissions due to poor Uplink quality conditions. 195 G_RxLevSub_Min. 215 GSM Spotlight Report. 212 G_LocationUpdateSuccessRate. 196 empty maps. CDMA. 194 G_RMAC_DL_TS_Min. 73 GSM Cell Coverage. 63. 8. 259. 187 EVT_CDMANeighborListIssueDetect. 231 HSDPA Setup Failure rate. 178 HSDPA. 50 export suggested changes to the OMC. 213 G_Analysis_Time_Before. 236 HSDPA_NW_Acceptance_EcIo_Threshold. 221 Handover Issues. 262 Excessive Interference. 195 EGPRS_LLC_DL_Min. 128 HSDPA 3G Neighbor List analysis. 194 G_RMAC_CV_BEP_Max. 204 EVDO Neighbor List. 54 EVDO Rev A Spotlight Report. 195 G_T3310_AttachTimer. 231. 261 Hard Handover Issues. 194 G_Cell_Reselect_Time. 149 Forward Link Problem. 225 HSDPA Peak Tput. 152 EVDO Cell Coverage. 194 G_RMAC_Power_Reduction_Max. 231. 249 Handover Impossible. 190 H Handover fail (LTE). 212 G_RMAC_C_Value_Min. 236 www. 190 Excessive Power Reduction. 165 EVDO Spotlight Report.com F F factor.Actix Spotlight Desktop User Guide November 2012 265 G_RMAC_Sign_Var_Min. 151 GPRS_Duration_Period. 195 EGPRS_RLC_DL_Min. 212 Global Filters. choosing. 237 HSDPA_NW_Acceptance_95_Percentile_TCP_Throu ghput_Threshold. 175 HSDPA thresholds. 42 Grade of Service. 196 GPRS_RLC_DL_Min. 199 Export data. 231. 211 G_Handover_Min. 212 G_OverAllSuccessRate. 137 External Interference. 195 G_T3380_PDPActTimer. 34 Global Filters. 194 G_RMAC_MEAN_BEP_Max. 237 HSDPA_NW_Acceptance_95_Percentile_EcIo_Thres hold. investigating. 8 GSM 2G Missing Neighbors analysis. 214 G_Prolong_Interf_timer. 231. 233 HSDPA_NW_Acceptance_95_Percentile_CQI_Thres hold. 214 G_CallDropRate. 231. 195 G_T3321_DetachTimer. 214 G_Interference_Radius. 190 Frequency not implemented. 221 G G_Analysis_Time_After. 87 HSDPA 3G-2G Neighbor List analysis. 113 EVT_CDMAImportantIssue. 8 exporting a series of images. 195 G_Timeout_ChannelRequest. 110 failure events. 221. 194 EGPRS_Duration_Period. 99 HSDPA Cell Pilot Pollution analysis. 194 . 8 EVDO Cell Coverage analysis. 196 GPRS_LLC_UL_Min. 231. 214 G_CallSetupSuccessRate. 194 G_RMAC_TAI_Max. 235 HSDPA Throughput KPIs. 237 HSDPA_NW_Acceptance_95_Percentile_MACHS_Th roughput_Threshold. 201 Excessive Call diagnosis for UMTS. 48 EVDO Pilot Pollution analysis. 8 Fast binning.

26 New Template. 39 MIMO statistics. 232 Limited Coverage Problem. 8 HSPA Call Drop Analysis example. 261 Investigate Further. 74. 219. 8 HSPA Event Explorer analysis. 123 Min_TxPower_Threshold. 141 Projection. 199 relative grade of service. 259. 249 interference factor. 199 Poor UL Coverage Problem. 61 Pilot Pollution. 210 network performance overview. 61 Mobility scenarios. 30 neighbor lists. identifying problems at the. 146 P Packet Switched KPIs. 231. 155 LTE reasonable task example. 134 L Lack of data to transmit. 259. 62 RLP Tx Throughput. 190 Low scheduling rate. 231 LTE IRAT Missing Neighbor analysis. 219 R Radio Network Explorer. 219 RRC Drop diagnosis for LTE. 83. 131 Location Update Failure diagnosis for GSM. 232 Low RLP Rx Throughput. 135 Return to Spotlight link. 129 modulation usage. 217. 259. 232 Low Signal. 219. 219. 208 Low RLP Tx Throughput. 204 RL_Throughput_TimeLimit_Threshold. 206. 190. 190. 7 New Project. 248 www. 231. 206. 190. 218 Log Files link. 249. 9 KPI. 261 PPPConnectionSuccessRate_Threshold. 208 Low Rx Signal. 151 Protocol Stack Browser. 236 HSPA 3G Neighbor List. 261 Ping_Pong_HO_Window. 261 IRAT Missing Neighbor analysis for LTE. 259. 236 HSDPA_NW_Acceptance_RSCP_Threshold. 9 KPIs and Reports. 259. 199 Low CQI values. 211 PN Search. 190 RL_Throughput_Threshold.actix. 236 HSDPA_NW_Acceptance_Overall_PS_Failure_Rate. 49 Poor Coverage. 206. 51. 95 message level. 199. exporting a series of. 236 HSDPA_NW_Acceptance_PS_Drop_Rate. 210 Low Throughput diagnosis for EVDO. 156 266 Maximum Intersite Distance. 61 Mobile Tx Power. 261 Rapidly Changing Radio Conditions. 110 Interference Problem. 210. selecting. 137 Immediate Reject. 222 HSPA events in the Event Explorer. 208. 208. 235 O Other. 231 modulation order low. 40 Raked RF Condition. 236 HSDPA_NW_Acceptance_HSDPA_Setup_Time. 8 Microsoft Excel. 200 . 259. 190 neighbor list preferences. 249 Missing Neighbor. 210 Poor Radio Conditions. 221 Overall PS Call Drop rate. 248 LTE Cell Coverage analysis. 88. 87. 204 RLP Rx Throughput. 135 Lost DL Channel. 250 issues panel. 130 LU Reject. 208. 79 LTE cell site parameters. 249 Poor Quality. 229 HSPA+ cell site parameters. 73. 8 Interference. 259. 38 Repository Summary table. 152 I images. 27. 190. 261 Load Entire File. 222 HSPA Cell Coverage. optimize. 261 Poor LTE coverage. 203 PPPSetupTime_Threshold. 217. 201 Preferences dialog box. 36 IUB_THROUGHPUT_PERIOD_THRES. 232 Low Raw HS Throughput. 261 Mobile Rx Power. 210. 208. 259. 231. identifying. 8 Network Overload. 207 Low Tput KPI event. 140 No LTE radio messaging. 136 Reverse Link Problem. 36 inbound vs. 231 K key performance indicator. 52. 221 Interference (LTE).com M Max_TxPower_Threshold. 206. 42 Reports. 62 RR Failed. 231. 217. 93. 231. 250 RRC Drop diagnosis. 249 No repository detected. 221. 221 Poor DL Coverage Problem. 200 Missing handover (LTE). 231 Overall PS Setup Failure rate. 256 PER. 217. 261 Low bandwidth allocation. 28 project template.Actix Spotlight Desktop User Guide November 2012 HSDPA_NW_Acceptance_HSDPA_Failure_Rate. 219 Important Issues section. 208. 217. 125 N Neighbor List Issue. outbound pilot pollution. 232 Low Raw HS Throughput not detected.

217. 213 SL_GSM_RapidPathloss_RxLev_Threshold. 253 SL_BTS_Sens_Threshold. 238 SL_UMTS_DT_Troubleshooter_CriticalIssues_Thres hold. 156 UMTS events in the Event Explorer. 230. 213 SL_GSM_High_TX_Power_Threshold. 201 Scheduling Issues diagnosis for EVDO. 252 Uu_Scan_PilotPollution_RSCP_Threshold. 254 SL_RapidPathloss_Time_window_Threshold. 35 267 S SchedulerAnalysis. 253 Uu_Scan_TooManyServersThreshold. 261 U UMTS Excessive Call diagnosis. 231. 204 Summary Dashboard. 255 Uu_Poor_EcNoThreshold. 33 Summary map. setting for data import. 213 SL_GSM_EIRP_Threshold. 7 status codes. 37 setting thresholds for data import. 262 UMTS 3G Neighbor List. 37 System Rejected. 231. 252 SL_RapidPathloss_EcIo_Threshold. 231. 247. 231 Uu_HSDPAAvRegularSched_Thresh. 221.actix.com . 231. 187 Unload Files button. 211. 29 thresholds. 29 T T2P_Avg_Threshold. 253 SL_Overspill_Dist_Threshold. 99 UMTS Cell Pilot Pollution analysis. 8 UMTS 3G-2G Neighbor List analysis. 255 Uu_RSCP_InterferenceThreshold. 219. 126 thresholds. 136 Uu_ActiveSet_EcNo[0]. 254 SL_Site_Issues_Dist_Threshold. 27 Spotlight Report. 237 Uu_HSDPAL1_To_Raw_Throu_Thresh. 231. identifying. 8 UniqueNeighborList. 63. 253 SL_EIRP_Threshold. 61 sites failing recommended design targets. 254 Spotlight projects about. 99. 69 www. 213 SL_MaxTimeBetweenRRC_REQandCallStart. 255 Uu_Poor_RSCP_Threshold. 119 SU_Rx_Throughput_Threshold. 25 settings. 261 System Released. 231. 235 Uu_HSDPALowRawThrou_Thresh. 252 Uu_Scan_Poor_RSCP_Threshold. 253 SL_Detectedset_EcIo_Threshold. 255 Uu_WinTimeHSnotBest. 252 Uu_Scan_PilotPollutionThreshold. 253 SL_GSM_Ant_Gain_Threshold. 253 SL_RapidPathloss_RSCP_Threshold. 252 UMTS/HSPA Cell Pilot Pollution. 231 Uu_LowRawHSDPAThroughput. 87 UMTS 3G-2G Neighbor List. 230. 254 SL_UMTS_DT_Troubleshooter_ImportantIssues_Th reshold. 93 UMTS Cell Coverage. 69. saving the project. 237 Uu_HSDPALowCQI_Thresh. 30 Show Excel Report. 235. 237 Uu_HSDPALowNetThrou_Thresh. 261 top panel. 254 Uu_EcNoInterferenceThreshold. 230. 261 V Visualization tab. 231 Uu_HSDPAAvLowSched_Thresh. 213 SL_GSM_BTS_Sens_Threshold. 255 Uu_Scan_PilotPollution. 79. 39 SINR. 255 Uu_PilotPollutionThreshold. 256 UMTS Spotlight Report. 259. 259. 235 Uu_TooManyServersThreshold. 25 Too Many Servers. 8 UMTS 3G Neighbor List analysis. 209 ServRxLevSub. 204 TCP slow start. 9 creating. 37 Uu_CoverageLimitedUE_TxPowerThreshold. 185. 254 Uu_HSCellNotBestPilot. 237 Uu_LowNetHSDPAThroughput. 231. 235 Uu_HSDPALowThrouMaxTimeWin_Thres. 8 SL_Ant_Gain_Threshold.Actix Spotlight Desktop User Guide November 2012 RRC Failure. 213 SL_GSM_Site_Issues_Dist_Threshold. 253 Uu_ThresGapBeforeThrComparison. 106 UMTS cell site parameters. 213 SL_GSM_RapidPathloss_RxQual_Threshold. 231 Uu_LowUE_TxPower. 29 Uu_Scan_PilotPollution_Count_Threshold. 253 SL_BLER_Threshold. 252 Uu_Scan_Poor_EcNoThreshold. 42. 180 UMTS thresholds. 236 UuPilotPollution. 253 Uu_Scan_TooManyServers_RSCP_Threshold. 252 Uu_Scan_TooManyServers_Count_Threshold. 231. 235 Uu_HSDPANet_To_L1_Throu_Thresh. 8 UMTS Cell Coverage analysis. 254 SL_UMTS_DT_Spotlight_CriticalIssues_HSDPAPeak Tput. 254 Uu_HighUE_TxPower. 231. 213 SL_GSM_RapidPathloss_Time_window_Threshold.

actix.com .Actix Spotlight Desktop User Guide November 2012 268 www.