Arieso_GEO 6 1 1 Rel Guide

GEOperformance 6.1.1

Release Guide Version 2.34

Issued 30 April 2015

The information contained in this document and any documentation referred to herein or attached hereto, is of a confidential nature and is supplied for the purpose of discussion only and for no other purpose.

This information should only be disclosed to those individuals directly involved with consideration and evaluation of any proposals, all of who shall be made aware of this requirement for confidentiality.

All trademarks are hereby acknowledged.

JDSU acquired Arieso in March 2013, adding the world's leading intelligent, location aware solutions for mobile network operators to its Communications Test portfolio. Arieso solutions locate, store and analyse data from billions of mobile connection events, giving operators a rich source of intelligence to help boost network performance and enrich user experience. This intelligence transforms the effectiveness of network performance engineering; enables customer-centric self-optimising networks; creates true understanding of customer experience and enables monetization of unique insights.

The proven Arieso carrier grade solutions are resilient and highly scalable. Operating on five continents, clients include mobile operator groups such as Amrica Mvil, AT&T, MTN, Telefnica and Vodafone, and leading equipment vendors including Alcatel Lucent and NSN.

JDSU (NASDAQ: JDSU; and TSX: JDU) innovates and collaborates with customers to build and operate the highest-performing and highest-value networks in the world. Our diverse technology portfolio also fights counterfeiting and enables high-powered commercial lasers for a range of applications. Learn more about JDSU at www.jdsu.comand follow us on JDSU Perspectives, Twitter, Facebook and YouTube.

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

Commercial-in-Confidence Copyright 2015 JDSU UK Ltd

Contents ABOUT ARIESO ................................................................................................................................... 1

1. MINOR RELEASE: VERSION 6.1.1 ............................................................................................... 6

1.1 NEW FEATURES .............................................................................................................................. 6

1.2 FIXED BUGS ................................................................................................................................... 6

1.3 KNOWN ISSUES ............................................................................................................................... 7

2. MAJOR RELEASE: VERSION 6.0 .................................................................................................. 8

2.1 NEW FEATURES .............................................................................................................................. 9

2.1.1 Data Feeds ....................................................................................................................................... 9

2.1.2 Correlation Module .......................................................................................................................... 9

2.1.3 GEOperformance ........................................................................................................................... 10

2.1.4 ariesoGEO Platform ....................................................................................................................... 16

2.2 DEPRECATED AND REMOVED ANALYSES ............................................................................................. 16

2.3 IMPACT OF CHANGES ..................................................................................................................... 16

2.4 FIXED BUGS ................................................................................................................................. 17

2.5 KNOWN ISSUES ............................................................................................................................. 17

2.6 INSTALLATION GUIDANCE................................................................................................................ 18

3. MAINTENANCE RELEASE: VERSION 5.1.4 ................................................................................. 19

3.1 NEW FEATURES ............................................................................................................................. 19

3.2 FIXED BUGS ................................................................................................................................. 19

3.3 KNOWN ISSUES ............................................................................................................................. 20



4.1 NEW FEATURES ............................................................................................................................. 21

4.2 FIXED BUGS ................................................................................................................................. 21




5.1 NEW FEATURES ............................................................................................................................. 23

5.2 FIXED BUGS ................................................................................................................................. 24

5.3 KNOWN ISSUES ............................................................................................................................. 25



6.1 NEW FEATURES ............................................................................................................................. 28

6.2 FIXED BUGS ................................................................................................................................. 28


7. MINOR RELEASE: VERSION 5.1 ................................................................................................ 29

7.1 NEW FEATURES ............................................................................................................................ 30

7.1.1 GEOperformance ........................................................................................................................... 30

7.1.2 ariesoGEO Platform ....................................................................................................................... 37

7.2 DEPRECATED AND REMOVED ANALYSES ............................................................................................. 38

7.3 IMPACT OF CHANGES ..................................................................................................................... 38

7.4 FIXED BUGS ................................................................................................................................. 39

7.5 KNOWN ISSUES ............................................................................................................................. 39



8.1 NEW FEATURES ............................................................................................................................. 41

8.2 FIXED BUGS ................................................................................................................................. 41



9.1 NEW FEATURES ............................................................................................................................. 42

9.2 FIXED BUGS ................................................................................................................................. 42

9.3 KNOWN ISSUES ............................................................................................................................. 43



10.1 FIXED BUGS ............................................................................................................................. 45


10.2 INSTALLATION GUIDANCE ........................................................................................................... 45


11.1 NEW FEATURES ........................................................................................................................ 46

11.2 FIXED BUGS ............................................................................................................................. 48

11.3 KNOWN ISSUES ........................................................................................................................ 49


12. MAJOR RELEASE: VERSION 5.0 ................................................................................................ 51

12.1 NEW FEATURES ........................................................................................................................ 52

12.1.1 GEOperformance ........................................................................................................................... 52

12.1.2 ariesoGEO platform ....................................................................................................................... 56

12.2 DEPRECATED AND REMOVED ANALYSES ........................................................................................ 56

12.3 IMPACT OF CHANGES ................................................................................................................ 57

12.4 FIXED BUGS ............................................................................................................................. 57

12.5 KNOWN ISSUES ........................................................................................................................ 58



13.1 FIXED BUGS ............................................................................................................................. 60



14.1 FIXED BUGS ............................................................................................................................. 61




16.1 GSM DROPPED CALL DEFINITION ................................................................................................. 63


16.3 FIXED BUGS ............................................................................................................................. 64

16.4 KNOWN ISSUES ........................................................................................................................ 64




17.1 ERICSSON LTE DL THROUGHPUT CALCULATION ............................................................................. 66

17.2 FIXED BUGS ............................................................................................................................. 66

17.3 KNOWN ISSUES ........................................................................................................................ 67


18. MINOR RELEASE: VERSION 4.2 ................................................................................................ 68

18.1 NEW FEATURES ........................................................................................................................ 69

18.2 DEPRECATED AND REMOVED ANALYSES ........................................................................................ 71


18.4 FIXED BUGS ............................................................................................................................. 71

18.5 KNOWN ISSUES ........................................................................................................................ 72



1. Minor Release: Version 6.1.1 Released May 2015

This minor release builds on the foundations laid in release 6.0 to bring further new features and improvements.

1.1 New Features LTE Problem Identification Wizard: The Problem Identification Wizard previously available for UMTS and GSM has been extended to enable clients to quickly locate and examine problem areas in their LTE networks.

The Problem Identification Wizard for LTE analyzes drop and block rates and uses them to identify problem areas, which can then be viewed on the map or analyzed using drill-down templates.

In addition, like the UMTS wizard it can be scheduled to run automatically on a regular basis, and results can be accessed from the Data Explorer.

This feature uses the Identify Problems license. Clients who already have this license installed will receive this feature automatically with upgrade to version 6.1.

LTE Export to ACP It is now possible to export information about the performance of LTE networks to Arieso's ACP tool for cell planning and optimization purposes.

Data Feeds from Streamed Data The new Data Feeds feature announced in version 6.0 has been updated to ensure compatibility with the new architecture developed to handle streamed data from LTE data sources. Customers using the streaming data architecture can now extract and transform GEOperformance data for use in external applications.

Impact of changes On LTE systems, a minor configuration change is required. This will not affect system performance.

1.2 Fixed Bugs

Bug ID Bug Summary Cases

32239 GeoDataLoader crashes if other applications use its default port 5555 CAS-14161

31463 On UMTS systems, missing sectors underreported due to reusing existing messages to identify

CAS-14074 CAS-13720



31233 In Admin Console, when editing schedule, invalid credentials can cause crash CAS-13948

31162 Updating operator lists is a slow and manual process CAS-13850

30961 AD Module installer missing some binaries needed to manage the system CAS-13825

32276 LTE Connections KPIs analyses count incoming HOs in Connection Setup Successes, but not Connection Setup Requests

CAS-13757

32391 Customer preview analysis does not work correctly on version 6.0 CAS-13196

31082 SFTP lack of KeepAlive means connection can be killed by firewalls CAS-13678

29190 After reconnecting Remote Desktop GEOperformance session, opening dialog causes crash

CAS-13512 CAS-13129 CAS-2246

30516 In Grid calculator, some functions use bounding box not polygon CAS-13506

30009 Some subscriber analyses have hardcoded filter, causing results to disagree CAS-10926

30962 New GeoMonitor does not support proxy CAS-13734

29954 On Ericsson LTE, max throughput sometimes wrongly calculated when throughput time is 0

1.3 Known Issues

Bug ID Bug Summary Fixed In

23350 Day hour settings ignores fractions of hour time difference


2. Major Release: Version 6.0 Released April 2015

This major release offers many new features to both new and existing clients, from an API to access geolocated data to LTE optimization. Highlights of this release include:

Data feeds: Arieso has developed a set of data feeds for all technologies to facilitate integration with third party systems. This enables mobile operators to extend Arieso's world-leading location and performance data to usage in other applications

Correlation Module: The Correlation Module has been extended to provide a greater overview into network problems GSM Support: The Correlation Module can now be used with GSM networks Golden Audit: This provides an easy way to detect potential misconfigurations in

cells and RNCs Event Distribution Counters: The Event Distribution Counters feature provides a quick

and easy way to view simple statistics for a map analysis, or to download an overview of its data as a table to use for calculations in an external tool

Event Ranking: Event Ranking continues to extend insight into map analyses, by offering an at-a-glance summary of the cells, devices or IMEIs associated with the most points

Extended analysis capabilities: This release provides a large number of new analyses to provide a more nuanced view of cell performance on GSM and UMTS networks, and to further extend GEOperformance's LTE insight, including VoLTE

Call Trace playback: It is now possible to play back a call's progress from the Layer 3 window, displaying segments on the map as they occur.

This release also provides a number of improvements to the ariesoGEO platform, including:

Geolocation of streamed LTE data: The improved architecture developed to handle streamed data from LTE data sources has been expanded to include data from NSN LTE systems and from ALU PCMD file-based systems. Clients not using streaming data or the streaming data architecture may still notice an improvement in parser performance

Improved vendor support: Ericsson: The ariesoGEO platform now supports Cell Trace data for W14A&B and

W15A&B. It also supports a 1-minute resolution on the GPEH profile Geolocation improvements: Arieso continues to improve and extend its world-leading

geolocation quality


2.1 New Features

2.1.1 Data Feeds The GEOperformance, GEOanalytics and GEOinsights Data Feeds provide a mechanism by which data can be extracted from the ariesoGEO platform in a scalable, secure and easy to integrate manner.

GEOperformance The GEOperformance Data Feed enables clients to use GEOperformance's geolocated, subscriber-centric data to conduct network planning and performance analysis. The Data Feed can also generate histograms of the RF metrics, delivered as Linear Average or as a histogram, representing the counts of the RF measurements for the Cell.

GEOinsights The GEOinsights Data Feed can be used to generate revenue streams based upon location intelligence data extracted from the ariesoGEO platform.

GEOanalytics The GEOanalytics Data Feed provides customer experience intelligence, designed to deepen customer relationships. In a similar manner to GEOperformance, the GEOanalytics Data Feed generates histograms of the RF metrics, representing the counts of the RF measurements for a Cell.

2.1.2 Correlation Module The Correlation Module is now available to clients running GSM systems. This enhances GEOperformance's GSM offering with the ability to link equipment faults and configuration changes to customer-centric network performance.

In addition, the Correlation Module has been extended with several new investigations. As well as a standard loading summary analysis for diagnostic purposes, it is now possible to investigate multiple cells in order to provide a picture of the system over time or identify particular hot spots:

Alarms Loading Summary: Table, Chart. Shows how many alarms of each severity were loaded into GEOperformance in each hour.

Top N Worst Cells by Alarms Count: Table, Chart. Displays the cells with the highest numbers of alarms active during the specified period.

Note: The Correlation Module is a licensed feature.

Golden Audit The Golden Audit is a new feature within the Correlation Module. It enables clients to compare the actual parameters used by cells and RNCs across their network with the preferred parameter ranges for their network.


This ability is provided by two new analyses, available from the All Cells topic of the Correlation Module:

Parameter Consistency Check Summary: Table. Shows the number of settings that are outside the specified ranges, broken down by network element type and parameter.

Configuration Parameter Audit: Table. Shows each network element that has settings outside the ranges specified for your network.

For example:

The Configuration Parameter Audit analysis, showing cells and RNCs whose parameters differ from the recommended network settings

Currently, the parameter ranges for the network are loaded into GEOperformance by Arieso personnel, but in future releases it may be possible for clients to upload their recommended parameters through a web interface, allowing for faster updates if recommendations change.

Note: Golden Audit is a licensed feature, and is currently only available for UMTS. For more information, speak to your Arieso representative.

2.1.3 GEOperformance Event Distribution Counters The Event distribution counters feature enables you to view map metadata, such as the precise number and distribution of events on a points layer or bins on a map layer, as a chart or table analysis.

Simply right-click on a map analysis layer in order to view its data as one of the following:

Statistics: Point and raster layers. Provides calculated statistics such as the minimum, maximum, median and standard deviation.

Histogram: Raster layers only. Shows the number of events of each value. CDF: Raster layers only. Shows the CDF for the values in the layer.


Each of these counters behaves in exactly the same way as a standard analysis, and so they can be sorted, filtered, exported and so on in all the ways that experienced GEOperformance users are familiar with.

Data Partitioning The new Data Partitioning feature provides a quick and easy way of running a set of identical analyses on each of a number of individual cells, eNodeBs or other elements.

This is achieved by setting a list of partitionable element values (such as a list of cells) when saving a document. When the document is opened, it will create a separate canvas for each cell, and each canvas will run all the specified analyses filtered by that cell. For example:


A document partitioned by cell. Each canvas shows the same analyses, filtered by the cell named in the tab

Note: This feature requires the Client - Data Partitioning license.

Event Ranking Event Ranking ranks the information on a points analysis by the number of events (points) associated with each instance of the specified item. This enables engineers to quickly see, for example, which cells are associated with large numbers of drops from a Drop Locations analysis.

The events on an analysis can be ranked by the following items:

Cell Device IMEI

Note: This feature requires the Client - Event Ranking license. It is currently available for UMTS and LTE.

GEOweb support for PDF Reports can now be downloaded as PDF files from the GEOweb Latest Reports list. In addition, subscribers to scheduled reports will now receive a PDF attachment with their email.

New Common analyses The following analyses have been added to provide greater insight into devices across all technologies:


Unidentified Devices: Table. Shows active devices that are not present in the TAC list, and the number of subscribers using them.

New GSM analyses Extra information on the likely effects of antenna changes, and on problem cells, is provided to GSM clients by the following new analyses:

Change Azimuth: Multi-map. Shows the projected KPIs for a single cell if the azimuth is changed. Use parameters to choose the cell and the azimuth change to model. The azimuth can be changed by between -30 degrees (anticlockwise) and 30 degrees (clockwise).

Change Power: Multi-map. Shows the projected KPIs for a single cell if the power is changed. Use parameters to choose the cell and the power change to model. The azimuth can be changed by between -10 and +10 dB.

Change Tilt: Multi-map. Shows the projected KPIs for a single cell if the mechanical tilt is changed. The tilt can be changed by between -10 degrees (upward) and 10 degrees (downward).

Turn Cell Off: Multi-map. Shows the projected KPIs for an area if a selected cell is turned off.

The above analyses provide parity with the functionality that already exists for UMTS. They require the AntennaTuning license.

Worst N Cells (Blocks) (Call Table): Table, Chart. The cells with the highest numbers of blocked calls.

Worst N Cells (Drops) (Call Table): Table, Chart. The cells with the highest numbers of dropped calls.

The above analyses are similar to the Worst N Cells summary analyses, but can be used to provide more nuanced and precisely filtered information.

New UMTS analyses Extra information on problem cells and call numbers is provided to UMTS clients by the following new analyses:

Count Against Time (Call Table): Table, Chart. The total number of calls that begin within the selected segments, for each fifteen minute period.

Worst N Cells (Blocks) (Call Table): Table, Chart. The cells with the highest numbers of blocked calls.

Worst N Cells (Drops) (Call Table): Table, Chart. The cells with the highest numbers of dropped calls.

The above analyses are similar to existing summary analyses, but can be used to provide more nuanced and precisely filtered information.


New LTE analyses Many new analyses have been provided in order to improve the insight that clients can gain into their LTE systems.

Extra information on the likely effects of antenna changes is provided to LTE clients by the following new analyses:

Change Azimuth: Multi-map. Shows the projected KPIs for a single cell if the azimuth is changed. Use parameters to choose the cell and the azimuth change to model. The azimuth can be changed by between -30 degrees (anticlockwise) and 30 degrees (clockwise).

Change Power: Multi-map. Shows the projected KPIs for a single cell if the power is changed. Use parameters to choose the cell and the power change to model. The azimuth can be changed by between -10 and +10 dB.

Change Tilt: Multi-map. Shows the projected KPIs for a single cell if the mechanical tilt is changed. The tilt can be changed by between -10 degrees (upward) and 10 degrees (downward).

Turn Cell Off: Multi-map. Shows the projected KPIs for an area if a selected cell is turned off.

The above analyses provide parity with the functionality that already exists for UMTS. They require the AntennaTuning license.

Insight into pollution, ERAB behavior, VoLTE and more are provided by the following analyses:

Call Table Dominance: Map. Shows the number of polluting cells in each bin. The user can define the definitions of polluter and best cell, and the RSRP averaging method used.

Call Table Nth Best Cell RF KPIs: Multi-layer map. Displays raster maps showing information about the RSRP, RSRQ and CQI of the Nth best cell in each bin.

The above analyses are also available as summary analyses, but the call table versions can be used to provide more nuanced and precisely filtered information.

Individual ERAB Segments: Table. Displays details of every selected ERAB segment. Multi ERAB End: Map, Table. Shows the points at which the number of ERABS used by a

connection reduces to fewer than 2. Multi ERAB Start: Map, Table. Shows the points at which the number of ERABS used by

a connection increases to more than 1.

Note: The ERAB analyses require the DeviceManagement and SubscriberManagement licenses.

CQI Statistics: Multi-layer map. Displays the mean and median CQI in each bin, as well as the number of measurements on which the calculations are based.


Dominance: Map. Shows the number of polluting cells in each bin. The user can define the definitions of polluter and best cell, and the RSRP averaging method used.

Downlink MIMO Usage by Connection (%): Map. Shows the percentage of the selected segments in each bin that use MIMO (Rank 2 with Transmission Modes 3, 4 or 8).

PUCCH Uplink SINR: Multi-layer map. Shows the mean and median SINR values on the Physical Uplink Control Channel recorded in each bin. The PUCCH Uplink SINR Measurement Volume layer provides an indication of the data reliability by displaying the number of measurements made within each bin.

PUSCH Uplink SINR: Multi-layer map. Shows the mean and median SINR values on the Physical Uplink Shared Channel recorded in each bin. The PUSCH Uplink SINR Measurement Volume layer provides an indication of the data reliability by displaying the number of measurements made within each bin.

Timing Advance: Multi-layer map. Shows the mean and median timing advances recorded in each bin for the selected call segments. The Timing Advance Measurement Volume layer provides an indication of the data reliability by displaying the number of measurements made within each bin.

VoLTE Block Locations: Multi-layer map, Table. Displays the point location of all blocks within the selected VoLTE connection segments.

VoLTE Drop Locations: Multi-layer map, Table. Displays the point location of all drops within the selected VoLTE connection segments.

VoLTE Locations: Multi-layer map, Table. Displays the point location of all selected VoLTE connection segments.

VIP Summary: Table. Displays a summary of the volume and duration of all the selected VIP calls.

Call Spider and Layer 3 Layer 3 now offers the ability to play back a call's progress, displaying segments on the map as they occur. Complete control over the speed of the playback is provided by a slider, which can be used to dynamically fast-forward or slow down the replay as required.

The following LTE measurements and ERAB properties can now be viewed from the Call Spider:

SINR PUCCH SINR PUSCH TBS Power Restricted TBS Power Unrestricted Event Type Start Outcome End Category


2.1.4 ariesoGEO Platform Improvements to Vendor Support To support Ericssons development of a 1 minute resolution for General Performance Event Handling (GPEH), GeoGpehParser will now accept either 1 minute or 15 minute GPEH files. No additional configuration options will be required to the Parser command line.

The introduction of 1 minute file set will enable our customers to reconfigure their systems to prevent issues arising from file size truncation. See Impact of Changes on page 16 for further details.

Additional LTE Identity Source Added JDSU TAA MME Data: Support has been provided to extract UE/IMSI identity data from

MMEs using the JDSU TAA or TSA agents and their associated equipment. The monitored interfaces (MMEs S6A/S10/S11 interfaces) are 3GPP standard specified and as a result can be used with MMEs from any vendor. See Impact of Changes on page 16 for further details.

Huawei MME Data: Support has been provided to handle MME identity data provided in the Huawei proprietary binary format.

2.2 Deprecated and Removed Analyses The following analyses have been deprecated in this release:

PUCCH Mean Uplink SINR - Deprecated in favour of PUCCH Uplink SINR PUSCH Mean Uplink SINR - Deprecated in favour of PUSCH Uplink SINR

These analyses were available only briefly for testing purposes, and their deprecation should not affect most clients.

2.3 Impact of Changes Golden Audit The Golden Audit feature requires some reconfiguration of your system and changes to the loading chain, but these should not affect your existing data or analysis results. For more information, contact your Arieso representative.

LTE Ericsson GPEH: For systems which are currently experiencing truncation, switching to 1

minute file sets will require an increase in database size, in order to hold the additional data that was previously lost.

LTE Identity source: Some topologies for MME and gateway may provide different degrees of identity data, determined by the availability of the interfaces. It is imperative that call segments are tagged with an identity before the LTE GeoLocator reads the LTE Call Measurement Data (LCMD)


2.4 Fixed Bugs


30749 UMTS analysis Top N Device by Subscriber Count runs slowly and should require filters

CAS-13765

30770 Loading sectors of lat/long 0,0 causes Neighbor Planning failure CAS-13736

30243 LTE analyses do not support Busy Hour filter CAS-13454

30045 FTP keeps trying to transfer files removed from OSS, causing delay CAS-13051

28590 On UMTS, failure to track carrier can result in resolving to wrong cell CAS-12781

30233 On some LTE systems, failure to track carrier results in wrong IFHO target cell

CAS-11858

25090 On some LTE systems, carrier info is not tracked during MRs CAS-11858

16635 Day Hour Settings filter returns results for an hour later than specified CAS-11094

20011 On Huawei PCHR, the Layer 3 Ec/Io chart may show wrong Traffic Channel and Active Service

CAS-10103

4751 In Layer 3, right-clicking outside the chart area can freeze the UI BUG-4468

26753 On UMTS Huawei, some failed Assignment Responses including PS RABs not classed as blocks

26752 On UMTS Huawei, some failed Release Requests with UE in FACH/PCH not classed as drops

26356 On UMTS Huawei, some failed Assignment Responses including CS RABs not classed as blocks

2.5 Known Issues


29190 After reconnecting to a Remote Desktop session with GEOperformance running, opening a dialog may cause GEOperformance to crash.

Workaround: On Windows Server 2008, apply a Windows Theme featuring Windows Aero to the Application Server to prevent crashing

On Windows Server 2012, Arieso recommends that you save your work and close down the GEOperformance application before closing your Remote Desktop session

6.1.1

31342 In the LTE analysis Measurement Event Types, the default color scheme does not specify a color for a small number of Measurement Event Types

31082 SFTP client does not fully support KeepAlive functionality. This means that it is possible for the connection between the FTP file transferer and the SSH FTP server to be killed by firewalls

6.1.1


30724 GEOperformance template documents, when set up to prompt for a variable value, do not then use that value in analyses

30651 UMTS Neighbour planning results, when dragged to a blank table control, ignore it and create a new table control

30650 GSM Neighbor Planning does not save its results so that they appear in the Data Explorer Results tab

29996 The LTE analysis Individual ERAB Segments returns duplicate rows when filtered by end category on a multi ERAB connection.

29601 In the UMTS analysis Failure Reasons By RNC, for RANAP failure reasons the Total Count does not always equal the sum of the individual counts.

29600 In the UMTS analysis Failure Reasons By Cell, for RANAP failure reasons the Total Count does not always equal the sum of the individual counts.

29559 In the UMTS Problem Identification Wizard, some bins that breach the set threshold for UL/DL Retransmission are not included in polygons, whereas bins that breach the thresholds less are.

29558 In the UMTS Problem Identification Wizard, drilling down from the polygon for DL and UL Retransmission Volume [kbits] shows empty table controls instead of the DL and UL Volume Against Time analyses

29022 With the 'Restrict to Map Area' option selected, changing the map boundary and rerunning the analysis fails to update results to the new area

29019 In the Common Points analyses, attempting to change the symbol color has no effect

28455 Common analyses intended for use with specific technologies still search across all technologies. This may cause those analyses to run slowly.

Workaround: Set the Technologies filter to the technologies the analysis should be used with

2.6 Installation Guidance Clients can upgrade directly to GEOperformance version 6.0 from version 5.1 or later. Clients on versions older than 5.1 will need to upgrade to 5.1.x first.

For full information on how to upgrade to GEOperformance 6.0, please refer to the following documents:

Upgrade Guide: 6.0 GEOperformance tech note: Database Upgrade: 6.0


3. Maintenance Release: Version 5.1.4 Released March 2015

This maintenance release provides several improvements to the 5.1 base version of GEOperformance, especially for clients using Ericsson GPEH systems.

3.1 New features Support for Ericsson W15A and W15B The ariesoGEO platform now supports the latest Ericsson WCDMA RAN versions W15A and W15B.

Improvements to ALU Parser ALU parser performance has been optimized to process data far more quickly, avoiding creating a backlog of data files to be parsed.

In addition, the ALU parser now supports the SRVCC CS-HO procedure for handing over a VoLTE connection to UMTS or GSM.

Impact of changes None.

3.2 Fixed Bugs


30514 LTE analysis IRAT Handovers by Target Technology returns no results if empty fields in data

CAS-13549

29663 Some LTE analyses have inaccurate tooltip CAS-13298

29489 If cannot communicate with ActiveDirectory, possible all users may see SPI CAS-13204

29215 On UMTS, bad data can cause list summarizer crash so device/subscriber analyses fail

CAS-13103

29069 GEOperformance Options dialog requires UMTS license CAS-13067

29067 AD module pane can sometimes show a 'Latest data' value in the future CAS-13054

29026 On ALU LTE systems, the Layer 3 drilldown shows unencrypted SPI CAS-13031

29038 On NASTAR GSM, single bad data handover loses detail for subsequent HOs CAS-13022

28990 On Ericsson UMTS, bad data can cause parser to fail without restart CAS-12984

28767 If only vendor selected is ALU, some geolocation files not installed CAS-12975

28544 If filters changed after raster analysis run, some values may be transparent CAS-12888

28245 For IRAT handovers from LTE to UMTS, target sector is not provided CAS-12755



27553 Ericsson LTE parser does not log Group details, and time combines UTC and local

CAS-12728

28507 Ericsson GPEH parser caches RNC version so does not update when changed CAS-12529

25663 Canvas filter does not permit dragging of map bounds CAS-12135

25557 LTE Active Network Cells analysis with polygon filter returns no results CAS-11606 CAS-13547

4572 NASTAR GSM parser can parse duplicate files, warning 'Too Many Periods' CAS-11517

10259 Ericsson GPEH parser classes RANAP drops with ReleaseCause 14 as normal CAS-8250

25244 On Huawei UMTS, final segment sometimes ends at period end, not L3 time

24680 GSM Worst N Subscribers/Devices include only initial segments Note: For bugs 29026 and 28245, this release provides a more comprehensive solution than

the fix offered in the previous release.

3.3 Known Issues


29227 NSN systems show a high number of Unknown failure reasons in analyses such as Combined Failure Reasons. This is because of an extra segment created to hold vendor messages that occur after the end of the call

29185 On Huawei PCHR, call end segments with no RABs active are set to a domain of Unknown rather than Signalling

29187 On Huawei PCHR, an extra segment is created for an RRC release within 1 s of a RAB release. This segment has an end reason of either Undefined or Signalling Normal Release

3.4 Installation Guidance Clients can upgrade directly to GEOperformance version 5.1.4 from the following versions:

5.1.3, 5.1.2 5.1.1, 5.1.0 (Requires a completion code refresh)

Clients on versions older than 5.1 will need to upgrade to 5.1.x first.

For full information on how to upgrade to GEOperformance 5.1.3, please refer to the following document:

Upgrade Guide: 5.1.4


4. Maintenance Release: Version 5.1.3 Released February 2015

This maintenance release provides several improvements to the 5.1 base version of GEOperformance, especially for clients using the following technologies:

Huawei UMTS ALU LTE Ericsson LTE version L14b

4.1 New features Extended support for Huawei UMTS This release adds support for the Huawei PCHR V100R015 format.

Impact of changes None.

4.2 Fixed Bugs

Bug ID Bug Summary Cases 29128 Undocumented changes in Ericsson LTE vL14b result in parsing failure CAS-13109

29026 On ALU LTE systems, the Layer 3 drilldown shows unencrypted SPI CAS-13031

28613 If OSS listing for unknown neighbor changes GSM > UMTS, network load fails CAS-12917

28565 Default summarizer config can lead to summarizing before loading complete CAS-12904

27554 On UMTS, Huawei NASTAR parser can time out before connection released CAS-12793

28246 For IRAT handovers from LTE to GSM, target sector is not provided CAS-12755

28245 For IRAT handovers from LTE to UMTS, target sector is not provided CAS-12755

29086 On Ericsson GSM, GCMD Identity Updater can crash and cause loading to fail CAS-12723

27489 GEOweb housekeeping requires log4netclient.dll though this is not used CAS-12709

27439 On LTE, Identity Server gives error if file already exists. Should overwrite CAS-12691

26950 On Nastar GSM, TCH RXLev UL data not shown in Layer 3 charts CAS-12566

26953 GSM Neighbour Planning interprets self measurements as neighbor relations CAS-12523

28295 On some UMTS systems, some periods can be summarized twice CAS-12280

25409 LTE points analyses by TAC use Type Allocation Code not Tracking Area Code CAS-11817

26989 For some analyses, Polygon filter uses rectangle based on polygon shape

24620 In L3, PCHR R15 CallStart message details omit Measurements in Fields table



5.1.2 5.1.x (Requires a completion code refresh)





5. Maintenance Release: Version 5.1.2 Released January 2015

This maintenance release provides several improvements to the 5.1 base version of GEOperformance, especially in the follow areas:

LTE analyses LTE parser support UMTS parser support

5.1 New features New LTE analyses Version 5.1 introduced the first Signal to Interference plus Noise Ratio (SINR) analyses. These provided insight into the median and distribution of SINR values on the PUCCH and PUSCH, on a cell-by-cell basis. GEOperformance now provides a full suite of SINR analyses:

RF\SINR\PUCCH PUCCH SINR PUCCH SINR by Cell (introduced in 5.1) PUCCH SINR by Device PUCCH SINR by Downlink Channel Number PUCCH SINR by eNodeB PUCCH SINR by Frequency Band PUCCH SINR by IMEI PUCCH SINR by Subscriber PUCCH SINR by Tracking Area Code

RF\SINR\PUSCH PUSCH SINR PUSCH SINR by Cell (introduced in 5.1) PUSCH SINR by Device PUSCH SINR by Downlink Channel Number PUSCH SINR by eNodeB PUSCH SINR by Frequency Band PUSCH SINR by IMEI PUSCH SINR by Subscriber PUSCH SINR by Tracking Area Code

All of these analyses are described in the User Guide and Technical Guide.


Improved parser for ALU LTE The ALU LTE parser has been rewritten for this release to supply extended support and improved performance. In particular, improvements include:

Accurate reporting of drop and block counts: Block and drop information is now included in the data. The drop rate reported is higher than that given by PM stats, but testing shows it to be a true reflection of 'drop' reports in the PCMD raw data

Provision of VoLTE data Provision of CS Fallback data Provision of data on inter-MME handovers Support for WM7.0 and WM8.0 Optimised performance for large data volumes

Extended parser support for Huawei and Ericsson UMTS The Huawei UMTS parser now supports PCHR R16 format data The Ericsson UMTS parser now supports W14B format data

Impact of changes In order to support Huawei PCHR R16 and the improved ALU LTE parser, an extended set of completion codes has been added to the database. This requires a database upgrade, although there are no changes to the database schema in this release.

To improve extensibility, the format of the internal .glr and .ecmd files used by the UMTS load chain has changed. Files in the new format have .uglr and .ucmd suffixes. This change does not affect already loaded data, but it will not be possible to parse any remaining .glr and .ecmd files after upgrade.

5.2 Fixed Bugs


27058 Too Many Periods error when parsing provides insufficient diagnostic details CAS-12608

26966 LTE geolocator default settings cause excessive RAM usage CAS-12606

26957 2G neighbour planning recommends ADDs for already defined neighbours CAS-12524

26671 Internal test analysis Performance KPIs_nocqi available to end users CAS-12489

26635 In 5.1.1 only, all Ericsson RPMO segments are geolocated At Server CAS-12461

26555 SINR analyses are wrongly filtered, making them slow and inaccurate CAS-12433

26550 IRAT Handovers by Target Technology analysis runs slowly CAS-12433

26075 Roamer Failures by Device analysis shows blank rows if device not in TAC list CAS-12285

25815 FTP file transfer fails with exception if expected directory is missing CAS-12232

26041 Top N Device Volume shows a row for the totals from unknown devices CAS-12184



25658 GEOperformance does not correctly calculate the most used MNC/MCC when identifying home network

CAS-12103

26002 In the Grid Calculator, using special characters in Name field causes crash CAS-12078

25415 On Ericsson LTE, measurement report during successful S1 handover causes incorrect drop classification

CAS-11913

25596 On Locations analyses, Start Outcome / End Category filters cause drops to be counted multiple times if multiple eRABs

CAS-11887

25595 Count of Drops by X analyses allow filters that cause incorrect results CAS-11887

26255 Common Individual Connection Segments analysis does not resolve UMTS cell label

CAS-11857

25278 UMTS System Performance analysis metrics calculated on unshown data CAS-11754

24619 Huawei PCHR parser accepts bad RSCP and Ec/Io values in some messages CAS-11657

25051 Cancelling analysis never finishes CAS-11562

25416 FtpFileTransfer does not restart after the thread hangs CAS-11476

25125 GEOperformance default configuration causes error near the end of running very large analyses

CAS-11382, CAS-11974

23327 Renaming default variables causes error on opening GEOperformance document

CAS-11323

21869 During ACP Export, GEOperformance crashes if cannot access ACP analyses CAS-10986

7779 In UMTS, segments without a Best Sector cause similar analyses to show different results

CAS-9909, CAS-10926

15118 Huawei NASTAR10 UMTS parser leaves late files in incoming folder CAS-9231

9848 In multimap analyses, selected layers are not shown unless parent is also selected

CAS-8280, CAS-8257

28279 On Huawei PCHR, very long calls cause parsing to fail with values in the future

26767 From 5.1, polygon filters are not correctly applied to GSM analyses based on SectorSummary source

24184 ALU small cell PSCs are not being resolved to small cell cell IDs in GPEH data

5.3 Known Issues



26989 The Polygon filter is not correctly used for some analyses. Instead of filtering based on cells and bins within the polygon, the polygon is used to define a rectangle which is then used as filter. Affected analyses include: GSM: Roamer Summary by Cell UMTS: Multilayer Cell Links Data Summary LTE: Connection KPIs by Cell, CQI by Cell

Workaround: Specify individual cells to include in the filter, or use map bounds and rectangular polygons to filter geographically when working with analyses that suffer this problem

5.1.3

26950 On NASTAR GSM, the Layer 3 RXLev chart gives the error 'There is no TCH RXLEV UL data for this call data'.

Workaround: It is still possible to view the RXLev data in individual messages. In addition, RXLev information can be viewed using analyses such as the following: Cell RF KPIs Device Comparison analyses Subscriber Comparison analyses Performance Against Time TCS Statistics analyses

5.1.3

26670 For both UMTS and GSM, the Busy Hour (Daily Server) analysis determines the Day of Week according to UTC rather than local time

26634 On ALU LTE, the Segment End Reasons filter does not offer all the valid end reasons

26598 In GSM, the TCH Frequency Reuse analysis can show a cell conflicting with itself. This occurs when the analysis is run over a time period that includes network updates.

Workaround: Only run the analysis for a time period that begins after the most recent network load

26592 In IRAT Neighbour Planning, UMTS to GSM ADD suggestions do not show site names or the neighbour type

26312 In Layer 3, within RANAP messages, the NAS PDU for Detach Accept displays a decode failure

26254 On Huawei GSM, missing serving cells are labeled 'BCCH 0 / BSIC 0' instead of 'Unknown'

25788 The Common analysis Performance KPIs by Service Group does not show block and drop information for LTE.


In the Correlation Module, the data shown by the Alarms Data Loading Summary analysis is not consistent with other data loading summary analyses


5.1.x (Requires a completion code refresh) 5.0.x (Requires a database upgrade to 5.1)


For full information on how to upgrade to GEOperformance 5.1.2, please refer to the following documents:

Upgrade Guide: 5.1.2 GEOperformance tech note: Database Upgrade: 5.1.2


6. Maintenance Release: Version 5.1.1 Released December 2014

This maintenance release provides several improvements to the 5.1 base version of GEOperformance, especially for clients using Huawei GSM.

6.1 New features Impact of changes None

6.2 Fixed Bugs


26063 On Huawei GSM, L3 Spider graph shows strongest Unknown neighbour only CAS-12269

25323 Busy Hour (Daily) analyses show single busy hour, not one for each day CAS-11991

25314 Huawei GSM L3 Measurement Reports show empty sectors as 'unknown' CAS-11990

25835 25836 26012

On Huawei GSM, when TRX ID not provided in Access Info/Release Info, serving cell is blank. Blank segments are omitted from some analyses

CAS-11893

25203 GSM Network fails to load correctly unless CSV file is sorted by label name CAS-11874

24714 Neighbor Planning considers PSC conflicts between cells on different ARFCNs CAS-11678

25689 Huawei GSM Neighbour Planning shows serving cell in BA list as 'unknown' CAS-11550

25597 Default Summarizer config can cause slow summarization on UMTS CAS-11487

23529 Underscores (_) in eNodeB names cause problems with Ericsson LTE parser CAS-11408


5.1 5.0.x (Requires a database upgrade to 5.1)





7. Minor Release: Version 5.1 Released November 2014

This minor release provides a set of significant new features. Highlights of this release include:

Extended LTE capabilities: New LTE analyses have been created in order to provide greater insight into indoor/outdoor traffic classification, handovers and user behavior. In addition, this release adds to Arieso's VoLTE solution capability by providing dedicated VoLTE analyses

Correlation Module: The GEOperformance Correlation Module allows network centric data such as performance management counters, fault management alarms and configuration changes to be viewed alongside the customer centric information already available within ariesoGEO. It empowers Optimization Engineers and Planning Engineers to monitor and troubleshoot network regions and optimize new sites more quickly and effectively, improving network responsiveness and customer experience. The Correlation Module is a licenced module

Advanced Diagnostics Module: The overall performance of this module has been significantly improved, enabling your RF experts to perform detailed investigations more quickly than ever. The Advanced Diagnostics Module is a licenced module

Cisco WiFi: Arieso's Small Cells capability has been extended to provide greater visibility into the performance of WiFi Access Points, including multiple new analyses

Extended analysis capabilities: This release provides a number of new analyses to provide extra insight into device and subscriber profiles. In addition, some analyses previously developed with the aid of individual customers have been updated and extended to a more general audience

LTE VIPs on GEOweb: Customers using the VIP Module can now access information on LTE VIPs from the Your customers tab

Improved ariesoGEO monitoring: The monitoring application provided with previous versions has been replaced by a new ariesoGEO Monitoring application that provides improved visibility into OSS and system status, including dashboard and trend views

GEOperformance Data Availability warning: GEOperformance filters now provide feedback to users on the data available for analysis, reducing wasted time and calls to Arieso Support

This release also provides a number of improvements to the ariesoGEO platform, including:

Improved vendor support: More detail and greater accuracy has been provided for existing LTE and UMTS vendors

NAS decoding: NAS messages can now be viewed in Layer 3 for UMTS technologies


Geolocation improvements: Arieso continues to improve and extend its world-leading geolocation quality

In Field Test The following features are currently being field tested, and are expected to be available for purchase in the future. If you are interested in field testing any of these capabilities, contact your Arieso Account Manager:

Small Cells Module: A completely new web-based module that simplifies the examination of your subscribers' experience whilst on small cells and also identifies candidate locations for new small cells based on observed subscriber behavior and network loading considerations. Identification and categorization of 'hotspots' in macro layer traffic and forecasts of possible performance enable small cells to be placed not only quickly, but also effectively

Geolocation of streamed LTE data: Arieso is breaking new ground in evolving ways to geolocate streaming data. A new loading and processing infrastructure is being developed in order to quickly and continuously handle messages that are continuously streamed by a third party system

Output data feeds: Arieso is developing data feeds to facilitate integration with third party systems, enabling mobile operators to extend the world-leading location and performance data to usage in other applications

GEOson: GEOson is a brand new application, developed specifically to suit the task of managing closed-loop Self-Optimizing Network (SON) tasks on a large scale. It uses the proven functionality of the core ariesoGEO platform, and provides an entirely new environment optimized for the configuration and operation of large numbers of SON tasks

7.1 New Features

7.1.1 GEOperformance Extended LTE analysis capabilities New LTE analyses are described below:

Indoor Outdoor Traffic: The number, data volume, and percentage minutes of use for indoor and outdoor traffic

Neighbour Performance Per Cell: Shows handover performance between the selected cells and the cells to which they performed handovers (or from which they received handovers)

IRAT Handovers by Target Technology: Shows the location of each handover attempt from or to UMTS or GSM

Block Locations: Displays the point location of all blocks within the selected connection segments.


Drop Locations: Displays the point location of all drops within the selected connection segments.

PUCCH SINR by Cell: For each cell in the selection, this analysis shows the median and distribution of Signal to Interference plus Noise Ratio (SINR) values on the Physical Uplink Control Channel.

PUSCH SINR by Cell: For each cell in the selection, this analysis shows the median and distribution of SINR values on the Physical Uplink Shared Channel.

Usage by Mean Number of Concurrent Users: The average number of active users in each bin

Usage by Mean Number of Concurrent Users/km2: The average density of active users for each bin, defined as concurrent users per square kilometer for ease of integration with external systems that use this metric

The extension to Arieso's VoLTE solution provides the following new analyses:

VoLTE Traffic (mErlangs): Shows the total VoLTE traffic intensity in each bin over the selected time period

VoLTE Traffic (mErlangs/km2): Map. Shows the VoLTE traffic density in each bin, defined as mErlangs per square kilometer for ease of integration with external systems that use this metric

VoLTE Traffic Volume (MOU): Shows the total VoLTE traffic in each bin over the selected time period

In addition to the new analyses, the LTE Call Table Performance KPIs analysis has been updated to show block- and drop-related layers.

New LTE filters Users can now filter analyses far more precisely than ever before, using the following new filters:

Handover Type HO Execution Outcome HO Preparation Outcome Physical Cell Id (Source) Physical Cell Id (Target)

Note: The above filters are particularly useful for selecting specific handovers to examine in the new Neighbour Performance Per Cell analysis.

UE Context Release Reason UE Context Release Command Reason

Note: The above filters are particularly useful for selecting abnormally released calls in analyses that show individual call segment details, such as point locations analyses.


PCI collisions It is now possible to show potential PCI collisions between LTE cells. This feature is similar to the existing scrambling code collisions feature and improves LTE support to closer parity with UMTS.

PCI Connector tool showing potential PCI collision

The PCI Connector tool is available from the Map Control.

Correlation Module The Correlation Module adds alarm and configuration information into GEOperformance, linking equipment faults and configuration changes to customer-centric network performance.

When viewing a map within GEOperformance for a region, cells with active alarms or configuration changes can be highlighted and displayed on a dedicated layer of the map. This allows the engineer to rapidly identify cells of interest and those events or changes that could be contributing to poor performance.


The Correlation Module provides:

Immediately visible information on the alarm or configuration status for all cells shown on the Map Control

Details of the alarm history of a cell, or of any configuration changes applied to it, available by clicking on that cell in the Map Control or in an analysis

Details of the alarm history and configuration changes for a cell's neighbors, enabling engineers to see at a glance any alarms or changes that might increase the load on the that cell

Analyses that show alarm details in specific areas, comparisons between cells, information on changes and similar useful tools

The ability to launch external applications pre-loaded with a reference to a specific cell of interest

Having access to contextually relevant network data in this way avoids the need to consult other OSS systems and significantly reduces the time taken to resolve performance issues.

New Common analyses The following analyses have been added to provide greater insight into subscriber behavior across all technologies:

Subscriber Data Usage vs Time: Displays information on individual subscriber data volumes over time, on each technology

Top N Subscribers by Volume: Shows the subscribers with the highest aggregate data usage across all technologies

New GSM analyses Extra information on geolocation, devices and roamers is provided to GSM clients by the following new analyses:


Indoor Outdoor Traffic: The number, data volume, and percentage minutes of use for indoor and outdoor traffic

Unique Device Counts: Information about each type of mobile device in the network, such as how many unique devices are in use, the services they are using, and the drops and blocks they are experiencing

Unique Device Maps: Shows the number of each type of mobile device in each bin, whether they used voice or data RABs, and how many devices experienced drops and blocks. This is based on the custom analysis Unique Device Map

Unique Devices: Shows a table of the number of each type of mobile device in each bin, the number using voice or data RABs, and the number that experienced drops and blocks. This is based on the custom analysis Unique Device Summary Table

Unique Devices Hourly Trend: A summary of the number of unique devices present in the selected segments during each hour of the selected time period. This is based on the custom analysis Unique Devices Hourly Trend Table

Unique Subscriber Count: A map of the number of unique subscribers (based on IMSI) in each bin. Additional raster layers show the number of unique users experiencing blocks or drops, or using data or voice connections

Unique Subscriber Count: A table of the number of unique subscribers (based on IMSI) in each bin. Also shows the number of unique users experiencing blocks or drops, or using data or voice connections

Unique Subscriber Count by Cell: Table. The number of unique subscribers (based on IMSI) in each cell. Also shows the number of unique users experiencing blocks or drops, or using data or voice connections

Roamer Drops: Details of drop numbers and rates for roamers, grouped by their home network. This analysis can be used to detect any problems with roamers from specific networks. This is based on the custom analysis Roamer Drop

Roamer Failures by Cell: Which failure reasons were encountered by roamers in each cell, grouped by home network and cell. This is based on the custom analysis Roamer Failure by Cell

Roamer Failures by Device: Which failure reasons were encountered by roamers using different devices, grouped by home network and device. This is based on the custom analysis Roamer Failure by Device

Roamer Summary: Numbers of unique roamers, failures, and RF and data KPIs for the selected connections, grouped by home network. This is based on the custom analysis Roamer Summary

Roamer Summary per Cell: Numbers of unique roamers, failures, and RF and data KPIs for the selected connections, grouped by home network and serving cell. This is based on the custom analysis Roamer Summary per Cell

Worst N Subscribers (Blocks): The subscribers with the highest numbers of blocked calls. This is based on the custom analysis Worst N Subscribers (Blocks)


New UMTS analyses Extra information on devices, subscribers and RF KPIs is provided to UMTS clients by the following new analyses:

Performance KPIs by Service: Shows information such as number of calls, traffic density, block rates and drop rates for each service. This is based on the custom analysis Call Table Call County by Service Summary Table

Device Report Summary: Shows a small number of key metrics, such as the number of unique devices, for every model of device. This is based on the custom analysis Device Report Summary

Devices Count by RNC: For each device, shows the associated TAC and the number of unique IMEIs of that TAC on each selected RNC

Device Data Volume by Service: Provides volume and throughput information for each device, broken down by service. This is based on the custom analysis Data analysis by Service

Top N Devices by Subscriber Count: Lists RF performance and KPIs summed or averaged for the types of the device that are used by the largest number of individual subscribers within the filter. This is based on the custom analysis Top N Devices by Subscriber Count

Unique Device Counts: Information about each type of mobile device in the network, such as how many unique devices are in use, the services they are using, and the drops and blocks they are experiencing. This is based on the custom analysis Unique Device Name Table

Unique Device Maps: The number of each type of mobile device in each bin, whether they used voice or data RABs, and how many devices experienced drops and blocks. This is based on the custom analysis Unique Device Map

Unique Devices: The number of each type of mobile device in each bin, the number using voice or data RABs, and the number that experienced drops and blocks. This is based on the custom analysis Unique Device Summary Table

Unique Devices Hourly Trend: A summary of the number of unique devices present in the selected segments during each hour of the selected time period. This is based on the custom analysis Unique Devices Hourly Trend Table

Unique Subscriber Count: A map of the unique subscribers (based on IMSI) in each bin. As well as the total number of users, shows the number of unique users experiencing blocks or drops, or using data or voice connections. This is based on the custom analyses Unique Subscriber Map and Unique Users Count Map

Unique Subscriber Count: The number of unique subscribers (based on IMSI) in each bin. As well as the total number of users, shows the number of unique users experiencing blocks or drops, or using data or voice connections. This is based on the custom analyses Unique Subscriber and Unique Users Count

Unique Subscriber Count by Cell: The number of unique subscribers (based on IMSI) in each cell. Also shows the number of unique users experiencing blocks or drops, or using


data or voice connections in each cell. This is based on the custom analyses Unique IMSI count by Sector and Unique User Count per Sector

Failure Reasons by Cell: For each cell, the number of calls that terminated with each combined completion code, and the number of failures for each domain within each completion code. This is based on the custom analysis Cell Drop Drill Down and various custom cell matrix analyses

Failure Reasons by RNC: For each RNC, the number of calls that terminated with each combined completion code, and the number of failures for each domain within each completion code. This is based on various custom cell matrix analyses

Ranked Server Stack: Shows the energy, footprint, RSCP and Ec/Io of the six best serving cells in each bin. This is based on the custom analysis Server Stack

UE TxPower per Sector: The UE TxPower distribution for each cell. This is based on the custom analysis UE TxPower per Sector

Footprint Diagnostics: Displays information about the area in which a cell is the best server, compared to its total footprint. This is based on the custom analysis RF Chronic Index

Propagation Delay by Cell: Shows the distribution of propagation delay values for each cell. This is based on the custom analysis Propagation Delay by Cell

RF Trend on Average Value by Sector: Shows the average Ec/Io and RSCP values for each cell in each hour period, across all the call segments included in the filter. This is based on the custom analyses EcIo Trend by Sector and RSCP Trend by Sector

Worst N Subscribers (Blocks): Displays the subscribers suffering the highest numbers of blocked calls. This is based on the custom analysis Worst N Subscriber (Blocks)

Note: The device and subscriber analyses require the DeviceManagement and SubscriberManagement licences.

In addition to the new analyses, the UMTS Locations and VIP Locations analyses have been updated to include a timestamp.

New WiFi analyses Customers using the Small Cells GEOperformance module to examine the performance of WiFi cells may now benefit from the following new analyses:

Aggregated WiFi KPIs Against Time: A summary of performance metrics such as uplink and downlink throughput and volume for each time period, summed across the selected connections

Data Usage Per Client Authentication Method: Shows the total volume and packet numbers for each client interface

Data Usage Per Device Manufacturer: Shows the total volume and packet numbers for devices from each manufacturer

Demand Per Access Point: Shows information about the number of number of users and devices using each access point, and their data usage


Device Usage Per IMSI: Shows information about the number of number of devices using each access point, and their data usage, broken down by IMSI

RF KPIs Per Access Point: Shows information about the RSSI and SNR of each access point

WiFi Sessions: Shows information about usage and performance metrics for individual sessions

Worst N WiFi Access Points By SNR: Shows the access points with the worst average SNR, and a summary of their RF KPIs and usage

ariesoGEO Monitoring application ariesoGEO Monitoring is a proactive tool used by JDSU personnel and customers to detect issues and investigate trends in the status of their ariesoGEO systems. Its web-based user interface displays system status in a far more flexible and scalable fashion than the old monitoring application.

ariesoGEO monitoring offers customized high-level overviews with the ability to drill down into details and trends over time, providing visibility into the impact of configuration changes and early warning of any issues with summarizer performance.

In future versions, this tool will also be available to diagnose problems such as missing sectors, network loading failures, system overload and slow analysis performance. For 5.1, these facilities are available via a seamless redirection to the previous monitoring system.

7.1.2 ariesoGEO Platform UMTS call model improvements Huawei: Domain information is now available for RAB (not signalling) drops and blocks.

It is also now possible to differentiate calls that use multiple PS RABs from calls that use only a single PS RAB


ZTE: The ZTE parser now provides volume and throughput information, as well as domain information for RAB drops and blocks. It is also now possible to differentiate calls that use multiple PS RABs from calls that use only a single PS RAB

NSN: It is now possible to differentiate calls that use multiple PS RABs from calls that use only a single PS RAB

NAS decoding: Layer 3 NAS data embedded in RANAP messages is now decoded and shown in the drill-down table under the relevant RANAP message. Note that this is not available for Huawei PCHR as there is no 3GPP signalling in the feed

LTE updates All existing vendors: Handover information has been improved to provide greater

visibility into the source technology Ericsson: Uplink SINR values are now stored for PUCCH and PUSCH

WiFi call model improvements The Cisco WiFi call model has been refined and improved in order to meet the requirements of the more extensive analysis suite.

Geolocation LTE geolocation now uses information from recent previous connections to inform the calculation of the starting segments of a new connection. There are also a number of other improvements to the geolocation algorithms, notably increasing the accuracy of simplex LTE geolocation, and of UMTS small cell geolocation.

7.2 Deprecated and Removed Analyses No analyses have been deprecated or removed in this release.

7.3 Impact of Changes Prerequisites GEOperformance version 5.1 requires version 4.5.1 of the Microsoft .NET framework. Any servers that run the older version 4.5.0 must be updated.

GSM The Huawei GSM parser configuration has changed in this version. The command line parameters must be updated for each BSC.

UMTS The Huawei UMTS parser will produce a slightly larger number of call segments for each connection than in previous versions. This change is of the order of 0.14 segments per call.

In addition, extra care should be taken when upgrading a database that contains Huawei Nastar10 data. During the database upgrade, both the Huawei PCHR and the Huawei


NASTAR options must be selected. If only one is selected, existing data may become inaccessible, or new data may use incorrect service definitions.

LTE On systems with large numbers of eNodeBs in each group, and on which identities such as IMSI and IMEI are not present, LTE geolocation may run slowly. This can be resolved with a minor configuration change.

7.4 Fixed Bugs


13886 Unable to view a Google Earth Report in GEO Web CAS-9323

21027 GEOweb does not show maps if the name contains quotes CAS-10777

22408 GEOperformance freezes when trying to show very large color scheme legend

CAS-10981

23549 Daily drop/block rate analyses always run based on UTC CAS-11412

23647 On NSN UMTS, in some conditions RanapRelocationResourceAllocationRecord causes error

CAS-11445

23993 LTE Layer3 wrongly shows throughput in InternalPerUeRbTrafficReport message details

CAS-11380

24266 LTE Active Network Cells analysis shows ARFCN instead of Frequency Band CAS-10977

24319 LTE Session Bearers analysis shows unknown QCIs as QCI 0 CAS-11623

24544 LTE RF Health Index analysis ignores parameter changes CAS-12050, CAS-11228

25055 Technical Guide gives incorrect block/drop rate formula for LTE CAS-11644

25372 On some GSM systems, release reason incorrect for successful outgoing handovers

CAS-12011

25374 If only LTE/WiFi loaded, network loader shows database as empty CAS-12193, CAS-12017

7.5 Known Issues


25721 If the FTP configuration file is corrupted, FTP file transfer fails with no useful error indications

25698 The Band in L3 Segment Properties shows GSM900 when the Band is unknown


25591 On Huawei LTE (Maximum Depth), the final message in a call does not display correctly

25407 When the GSM Locations analysis results *.dat file is larger than 2 GB, GEOperformance freezes with the error: CPLRealloc(): out of memory

25367 On GSM, the Call Table RXQUAL Histogram analysis fails when GSMCallSegments table contains nulls in the Uncertainty column.

From GEOperformance 5.1 onwards, this field is no longer nullable

25328 On ALU LTE Version 7, no blocks and drops are reported 5.1.2

25244 In Huawei UMTS, the final call segment is sometimes shown as ending at the period boundary instead of the time indicated by Layer 3

5.1.4

25025 Wifi Connection Segments have a Service Group of None instead of HS Data

24620 In Layer 3, PCHR R15 Call Start message does not show Measurements in the Fields table

5.1.3

7.6 Installation Guidance Clients can upgrade directly to GEOperformance version 5.1 from version 5.0 or later. Clients on versions older than 5.0 will need to upgrade to 5.0.x first.

For full information on how to upgrade to GEOperformance 5.1, please refer to the following documents:

Upgrade Guide: 5.1 GEOperformance tech note: Database Upgrade: 5.1


8. Maintenance Release: Version 5.0.4 Released November 2014

This maintenance release provides numerous improvements to the 5.0 base version of GEOperformance, including:

Support for Alcatel Lucent LTE PCMD WM8.0.0, WM7.1.0 Improved Ericsson UMTS parser performance

8.1 New features Impact of changes On Ericsson UMTS, in order to take advantage of the performance improvements a configuration change must be made. This is described in the Upgrade Guide.

8.2 Fixed Bugs


25003 Unable to load GSM network data at longitudes greater than 90E or 90W CAS-11797

8.3 Installation Guidance Clients can upgrade to GEOperformance version 5.0.4 from the following versions:

5.0.3 5.0 (requires a completion code refresh) 4.2.x (requires a database upgrade)

Clients on versions older than 4.2 will need to upgrade to 4.2 first.

For full information on how to upgrade to GEOperformance 5.0.4, please refer to the following documents:



9. Maintenance Release: Version 5.0.3 Released October 2014

This maintenance release provides numerous improvements to the 5.0 base version of GEOperformance, including:

Support for Ericsson LTE L14A A new LTE analysis: Best Cell by MOU Improvements to the performance of LTE analyses

9.1 New features Best Cell by MOU analysis

Folder Type Data Source Description RF Multi-map ConnectionSummary Displays raster maps of the server that has the

highest MOU in each bin, and the corresponding MOU value.

More information on this analysis is available in the Technical Guide.

Impact of changes The LTE Loading Errors analysis has been updated to improve consistency with the LTE Loading Summary analysis. Further information regarding these analyses has been added to the Technical Guide.

On NSN UMTS, in order to use BLER measurement reports to provide UE Tx Power information a configuration change must be made on the RNC. This is described in the Upgrade Guide.

Deprecated analyses The following LTE analyses have changed their names:

Best Cell RF KPIs > Best Cell Best Cell Footprint RF KPIs analyses > Best Cell Footprint

Any documents that include these analyses must be updated to use the new names. The old names are considered deprecated. Instructions on how to use the Deprecated Analysis tool to locate documents using deprecated analyses can be found in the Upgrade Guide.

9.2 Fixed Bugs



Bug ID Bug Summary Cases 24088 Import Network Layer requires Ericsson version but has no default CAS-11568

23529 Ericsson LTE parser cannot handle underscore in eNodeB name CAS-11408

23390 CTUM information can't be loaded for Ericsson MME files without renaming CAS-11408

21984 LTE Individual Connection Segments analysis Rank columns need clarification CAS-11354

23108 On NSN systems, Layer3 does not work unless ZTE vendor was installed CAS-11312

22789 LTE CS Fallback Locations Count by TAC shows empty row for missing IMEI CAS-11134

22019 Ericsson LTE parser can fail when system is slow CAS-11034

23990 Log messages for missing payloads set to WARN instead of DEBUG CAS-10946

23388 Missing payloads on LTE RRC Reconfig messages cause wrong L3 error CAS-10946

21426 Missing values in LTE Usage by QCI analysis CAS-10903

23573 Ericsson LTE parser does not support L14A CAS-10884

21796 Smart LTE Layering categorised as Drop, not Normal Release CAS-10568

19329 GPEH parser does not correctly resume after loss of DB connection CAS-10191

19271 On some networks, running Indoor/Outdoor analysis on large area fails CAS-10090

CAS-11595

CAS-11598

CAS-11676

13553 In Ericsson UMTS, TM values not shown on L3 graph CAS-9975

20090 Ericsson UMTS L3 shows only reported value for UL Interference CAS-9910

22486 All current LTE Best Cell plots based on MR, making artifacts likely CAS-9643

18148 LTE Best Cell plots sometimes show artifacts CAS-9643

22488 On NSN, UE Tx Power measurements are ignored when they come with BLER measurements

CAS-9501

CAS-11013

21118 GSM uplink and downlink RXLEV values are swapped during loading

9.3 Known Issues


24210 The LTE Best Cell Footprint analysis shows the overall footprint rather than the area where the selected cell is the best cell

24186 In the Correlation Module, the alarms layer appears in the root of the layer view, but inherits the visibility of the Network>Cells>UMTS Cells layer


22354 In the Correlation Module, the Config Update and Alarms layers always appear on top, no matter how they are ord

Documents

Arieso_GEO 6 1 1 Rel Guide