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.
Contents
ABOUT ARIESO ................................................................................................................................... 1

1.
2.
MINOR RELEASE: VERSION 6.1.1 ............................................................................................... 6
1.1
NEW FEATURES .............................................................................................................................. 6
1.2
FIXED BUGS ................................................................................................................................... 6
1.3
KNOWN ISSUES ............................................................................................................................... 7
MAJOR RELEASE: VERSION 6.0 .................................................................................................. 8

2.1
3.
4.
5.
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
MAINTENANCE RELEASE: VERSION 5.1.4................................................................................. 19

3.1
NEW FEATURES ............................................................................................................................. 19
3.2
FIXED BUGS ................................................................................................................................. 19
3.3
KNOWN ISSUES ............................................................................................................................. 20
3.4

4.1
NEW FEATURES ............................................................................................................................. 21
4.2
FIXED BUGS ................................................................................................................................. 21
4.3
Page 2
Commercial-in-Confidence
Copyright 2015 JDSU UK Ltd
5.1
NEW FEATURES ............................................................................................................................. 23
5.2
FIXED BUGS ................................................................................................................................. 24
5.3
KNOWN ISSUES ............................................................................................................................. 25
5.4
6.

6.1
NEW FEATURES ............................................................................................................................. 28
6.2
FIXED BUGS ................................................................................................................................. 28
6.3
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
7.6
8.

8.1
NEW FEATURES ............................................................................................................................. 41
8.2
FIXED BUGS ................................................................................................................................. 41
8.3
9.

9.1
NEW FEATURES ............................................................................................................................. 42
9.2
FIXED BUGS ................................................................................................................................. 42
9.3
KNOWN ISSUES ............................................................................................................................. 43
9.4
10.
10.1
FIXED BUGS............................................................................................................................. 45
Page 3
10.2
11.
INSTALLATION GUIDANCE ........................................................................................................... 45
11.1
NEW FEATURES ........................................................................................................................ 46
11.2
FIXED BUGS............................................................................................................................. 48
11.3
KNOWN ISSUES ........................................................................................................................ 49
11.4
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
12.6
13.
13.1
FIXED BUGS............................................................................................................................. 60
13.2
14.
14.1
FIXED BUGS............................................................................................................................. 61
14.2
15.
16.
16.1
GSM DROPPED CALL DEFINITION ................................................................................................. 63
16.2
16.3
FIXED BUGS............................................................................................................................. 64
16.4
KNOWN ISSUES ........................................................................................................................ 64
16.5
Page 4
17.
17.1
ERICSSON LTE DL THROUGHPUT CALCULATION ............................................................................. 66
17.2
FIXED BUGS............................................................................................................................. 66
17.3
KNOWN ISSUES ........................................................................................................................ 67
17.4
18.
MINOR RELEASE: VERSION 4.2 ................................................................................................ 68
18.1
NEW FEATURES........................................................................................................................ 69
18.2
DEPRECATED AND REMOVED ANALYSES ........................................................................................ 71
18.3
18.4
FIXED BUGS............................................................................................................................. 71
18.5
KNOWN ISSUES ........................................................................................................................ 72
18.6
Page 5
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
Page 6
Bug ID
Bug Summary
Cases
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
Page 7
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
Page 8
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.
Page 9
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.
Page 10
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:
Page 11
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:
Page 12
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.
Page 13
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
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.
Page 14
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
Page 15
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)
Page 16
2.4 Fixed Bugs

Bug ID
Bug Summary
Cases
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

Bug ID
Bug Summary
Fixed In
29190
After reconnecting to a Remote Desktop session with GEOperformance

running, opening a dialog may cause GEOperformance to crash.
6.1.1
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
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
Page 17
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
Page 18
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

Bug ID
Bug Summary
Cases
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
Page 19
Bug ID
Bug Summary
Cases
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

Bug ID
Bug Summary
Fixed In
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

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)
For full information on how to upgrade to GEOperformance 5.1.3, please refer to the
following document:
Upgrade Guide: 5.1.4

Page 20

Released February 2015
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
29128
Bug Summary
Undocumented changes in Ericsson LTE vL14b result in parsing failure
Cases
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
Page 21

5.1.2
5.1.x (Requires a completion code refresh)
following document:
Page 22

Released January 2015
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.
Page 23
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

Bug ID
Bug Summary
Cases
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
Page 24
Bug ID
Bug Summary
Cases
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

Bug ID
Bug Summary
Fixed In
Page 25
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
5.1.3
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
26950
5.1.3
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
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'
The Common analysis Performance KPIs by Service Group does not show
block and drop information for LTE.
25788
Page 26
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)
following documents:

GEOperformance tech note: Database Upgrade: 5.1.2
Page 27

Released December 2014
GEOperformance, especially for clients using Huawei GSM.
6.1 New features

Impact of changes
None
6.2 Fixed Bugs

Bug ID
Bug Summary
Cases
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)
following document:
Page 28
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
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
Page 29
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

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.
Page 30
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.
Page 31
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.
Page 32
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
Page 33
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)
Page 34
New UMTS analyses

Extra information on devices, subscribers and RF KPIs is provided to UMTS clients by the
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
Page 35
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
Page 36
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
Page 37
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.

No analyses have been deprecated or removed in this release.

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
Page 38
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

Bug ID
Bug Summary
Cases
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

Bug ID
Bug Summary
Fixed In
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
Page 39
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

Clients can upgrade directly to GEOperformance version 5.1 from version 5.0 or later.
documents:
Upgrade Guide: 5.1

Page 40

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

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

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.
Page 41

Released October 2014
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
RF
Type
Multi-map
Data Source
ConnectionSummary
Description
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
Page 42
Bug ID
24088
Bug Summary
Import Network Layer requires Ericsson version but has no default
Cases
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
21118
CAS-11013
GSM uplink and downlink RXLEV values are swapped during loading
9.3 Known Issues

Bug ID
Bug Summary
Fixed In
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
Page 43
22354
In the Correlation Module, the Config Update and Alarms layers always
appear on top, no matter how they are ordered

5.0.2
Page 44
10.
Maintenance Release: Version 5.0.2
Released September 2014

This maintenance release provides important improvements to the 5.0 base version of
GEOperformance for clients using Huawei PCHR 15 and clients using the following analyses:
Worst N Cells (CS Drops)

Cell Performance
Custom analyses showing RSCP and Ec/Io averages by sector
10.1 Fixed Bugs

Bug ID
21768
Bug Summary
Network 'Valid since' in map control does not update if cells removed
Cases
CAS-10864
14281
Overlapping valid sector ranges in network configuration cause some blank

sector information columns in specific analyses
CAS-10141
CAS-9224
CAS-9200
22559
Large STAT blocks in PCHR 15 data cause an error and prevent data loading

5.0.2
Page 45
11.
Released August 2014

New vendor formats

New map provider options
Support for Chinese characters in network information
More fixed issues than in any previous release
11.1 New features

Support for new vendor formats
This version of GEOperformance extends support to the following vendor formats:
LTE
Ericsson L13B cell trace data
Huawei uncompressed .tmf format files
UMTS
Huawei PCHR 15 (including Layer3)
Support for MapBox maps

GEOperformance can now be used with custom-designed MapBox maps as well as with
Microsoft's Bing maps. This is especially advantageous for customers in the Far East as
MapBox maps for these regions display street names and other information in the native
language and character set. Customers can even use both map providers, choosing the best
maps to show on an ad-hoc basis from within the user interface.
Page 46
Selecting map provider and maps
In order to use MapBox maps, clients must purchase a MapBox plan and design a map or
maps according to their specific requirements.
Support for Chinese characters in network information
Network data that contains Chinese characters can now be successfully loaded into
GEOperformance and shown in analyses. Network Search and other GEOperformance
features fully support Chinese character sets.
Note: In order to support Chinese characters in network data, your database must have
been configured to use the AL32UTF8 character set during installation. This is the
standard GEOperformance database configuration.
LTE call table analyses
In order to provide extra filtering options, call table versions of some LTE summary analyses
have been added to the system. The following analyses can be found in the Call Table
folder:
Call Table Data KPIs: Multi-layer map. A set of raster maps displaying data volumes,
durations, throughputs, latencies and delays.
Call Table Performance KPIs: Multi-layer map. Displays a raster map of the traffic
volume (MOU).
Note: Faster-running summary versions of these analyses are available from the Data and
Performance folders
Dashboard time intervals
5.0 introduced the Dashboards feature, which enables clients to access an at-a-glance view
of network performance and trends from anywhere in the world. The latest version of
dashboards has been updated to enable dashboard viewers to specify whether data should
Page 47
be broken down into hourly or daily intervals, and how many of the previous days' data
should be shown.
The latest version of dashboards is compatible with both 5.0.1 and 5.0 versions of
GEOperformance.
Impact of Changes
As part of ensuring a better classification of services on NSN UMTS (see fixed issue CAS9034) the voice service types have changed. This means on NSN systems, analyses using the
old service types on will give inaccurate results. On NSN systems, GEOperformance
documents must be reviewed and updated to ensure that any service filters use the new
NSN UMTS voice service types.
Further changes to NSN UMTS have been made to improve the NSN throughput values (CAS8984). These changes relate to how volume values are assigned to individual call segments,
and how throughputs are calculated from this. Specifically:
The ariesoGEO platform now assigns the volume information in a single Throughput
Ticket between all the segments covered by that ticket
Throughput values can no longer exceed the rates specified by the RANAP (following
relocation) or the RAB
However, when switching from HS Data to LS Data the network may indicate that a segment
has a service of R99/R99, but a DL Throughput of the HS service. Arieso is working to find a
solution to this issue.
11.2 Fixed Bugs

Bug ID
Bug Summary
Cases
21052
Ericsson LTE parser does not recover from loss of Identity Server connection
CAS-10797
20956
GeoImageTileCacheService does not use proxy settings for base URL, causing
exception
CAS-10719
21242
GEOperformance crashes on LTE systems if UMTSClient/GSMClient license

not present
CAS-10715
CAS-10885
20432
Huawei Layer3 returns exception on calls without TMSI
CAS-10601
20412
Technical Guide omits list summarization for Device/Subscriber list analyses
CAS-10592
19871
GSM analysis Missing Neighbors returns no results on some systems
CAS-10421
19556
GSM analysis Cell KPIs vs Timing Advance returns no result after cell update
CAS-10337
18163
GeoSummaryProcessController hangs after DB connection interruption
CAS-9865
Page 48
Bug ID
Bug Summary
Cases
5941
UMTS Device Performance Summary per Individual analysis returns only the
top 1000 items
CAS-9725
19421
In LTE geolocation, Timing Advance is assigned to too few segments
CAS-9643
19532
LTE geolocation assigns non-zero confidence values to segments located at

server
CAS-9643
19533
In LTE geolocation, CQI spreading is insufficient
CAS-9643
19248
NSN UMTS shows Voice (Half Rate) and (Full Rate) not AMR-WB and AMRNB
CAS-9034
14229
NSN UMTS sometimes shows implausibly high throughput on a LS segment
CAS-8984
19388
UMTS NSN throughputs after SRNC relocation can exceed

RelocationResourceAllocation
CAS-8984
13999
Scheduled points analyses remain un-run after job complete
CAS-8973
8778
NSN Parser gives exception Unknown cell state: None in some networks
CAS-882
CAS-9141
19521
In Correlation Module, 'Is Negative' setting by Alarm Type/Severity filters
18345
Some LTE post-handover segments are not assigned a Timing Advance
11.3 Known Issues

Bug ID
Bug Summary
Fixed In
21426
When using the LTE Usage by QCI analysis on Ericsson LTE, some rows have a
blank QCI, some have blank UL/DL Data Durations, and some rows have 0 for
every column except the QCI.
5.0.3
21237
When a saved GEOperformance document includes a map without the

network layer, when the document is loaded the network layer is visible.
19878
The Huawei LTE parser cannot be configured using the Administrator Console.
19520
When you select Active alarms on map, and then correlate from the Cell
Details window, those latest alarms will not be shown because the Correlation
Window has inherited the Canvas/Document filters.
Workaround: Set the Canvas/Document filters to include the current day and
hour.
Page 49



From 4.2.x: GEOperformance tech note: Database Upgrade: 5.0
From 5.0: GEOperformance tech note: Database Upgrade: 5.0.1
Page 50
12.
Major Release: Version 5.0
Released June 2014

This major release provides a set of significant new features. Highlights of this release
include:
Advanced Diagnostics Module: The Advanced Diagnostics (AD) Module provides expert
users with the ability to dive deeper into information available from analyzing
measurement reports, timings between key events, and location area/routing area
updates. It follows a task-based, problem-solving approach that guides the user to the
appropriate analyses to use for their specific requirements. The AD module requires the
ADM - Advanced Diagnostics Module licence
Dashboards: The new GEOperformance dashboards facility provides the ability to see
KPIs and trends at a glance, from anywhere in the world, via a standard web browser
Email and SMS alerts: Automated email and SMS alerts
Small Cells: Small Cells provides the ability to view and analyze the performance of
femtocells and WiFi Access Points using all the tools available within GEOperformance,
such as maps and analyses
LTE Summaries: This version of GEOperformance introduces summary tables for LTE
data. These tables improve analysis performance and summarize key LTE data, enabling
users to run summary analyses that incorporate a far larger data set than was previously
possible
Extended analysis capabilities: This release provides a large number of new analyses to
provide extra insight into specific areas. These include:
UMTS Roamer analyses
UMTS Data analyses: Top N by volume
LTE Subscriber and Cell analyses
Small Cell WiFi and Femto analyses
VIP Module enhancements: The number of VIPs supported by the VIP Module has been
increased dramatically, and the overall performance of the module has been improved
Support for multiple new vendors: New parsers to support:

UMTS
i) ZTE
ii) Huawei Nastar 11 and PCHR R15
iii) Alcatel Lucent femtocell
LTE
i) Huawei
ii) NSN
Page 51
Numerous geolocation and performance improvements, including improved support for

Special Antenna Systems and Repeaters, LTE geolocation quality and indoor/outdoor call
classification
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:
Correlation Module: The Correlation Module adds alarm and configuration information
into GEOperformance, providing a link between equipment faults and configuration
changes to customer-centric network performance. 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 will be a licenced module
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
GEOson: GEOson is a brand new application, developed specifically to suit the task of
managing closed-loop SON tasks on a large scale. It uses the proven functionality of the
core ariesoGEO platform, but provides an entirely new environment optimized for the
configuration and operation of large numbers of SON tasks
ariesoGEO platform: Support for Cisco Wifi
12.1 New Features

Advanced Diagnostics Module (AD Module)
The Advanced Diagnostics (AD) Module was trialled in the previous version of
GEOperformance. It is now available for purchase.
The AD Module is a new way of allowing expert users to investigate detailed aspects of
important areas such as device performance, network performance, and customer mobility
using the extra intelligence provided by measurement reports, timings between key events
or within RRC states, and location area/routing area updates.
Page 52
The AD Module user interface
The AD Module requires some additions to the standard GEOperformance loading chain and
stores its data in a new and separate database so that there is no performance impact on
the rest of the application. Arieso recommends that customers use a separate server to host
the necessary AD Module infrastructure.
In addition, the following investigations have been added to extend the initial AD Module
capabilities:
Measurement Reports for Inter-frequency Events Points

Measurement Reports for Inter-RAT Events Points
Measurement Reports for Intra-frequency Events Points
Measurement Reports for Traffic Volume Events Points
Measurement Reports for Ue Events Points
RRC State Timing Distribution CDF
RRC State Timing Distribution Histogram
Dashboards
Dashboards provide an at-a-glance view of network performance and trends, with
information from all three technologies (GSM, UMTS and LTE) alongside one another on
multiple reports.
Page 53
Example dashboard
The reports themselves can be easily rearranged and reformatted on-the-fly according to
individual requirements. Support for standard GEOperformance authentication means that
sensitive information is restricted only to appropriate personnel.
Email and SMS alerts
Daily email and SMS alerts can now be configured to be sent from GEOperformance when
customer-defined thresholds are breached. These email and SMS alerts can be sent to one
or many recipients.
Small Cells
Femtocells and WiFi Access Points can now be viewed within the Map Control, and their
performance analyzed using all the tools available within GEOperformance. It is currently
available for ALU version 3 femtocells, and being field tested with Cisco WiFi.
In order to support working with small cells, a number of analyses have been added to
GEOperformance to enable engineers to examine throughput and volume, handovers, RRC
and RAB setup success, and other aspects of small cell performance. The new Small Cell
analyses are listed below:
Cell Data Performance

Cell Data Performance
Cell Load
Cell Voice Performance
Handover Failure Reasons
Handover Failure Reasons by Cell
Handover Performance Femto
Handover Performance Femto to Macro
RAB Performance KPIs
RRC Performance KPIs
RRC Setup SR by Cause
System Performance Against Time
Worst N Cells (RAB Setup)
Worst N Cells (RRC Setup)

Worst N Groups (RAB Drops)
Worst N Groups (RAB Setup)
Worst N Groups (RRC Setup)
Femto Loading Summary
Active WiFi Access Points
WiFi KPIs Against Time
WiFi KPIs by Access Point
Multilayer Failure Reasons
Multilayer Cell Links Data Summary
Multilayer Cell Data Performance
Against Time
Page 54
LTE Summaries
A set of LTE summary tables have been added to the database for LTE systems, enabling
users to run summary analyses that incorporate a far larger data set than was previously
possible. A number of the existing CQI, Data and KPI analyses have been updated to run
with summary data.
New LTE analyses
A set of Subscriber and Cell analyses extend the intelligence available to LTE customers,
providing information on the subscribers and cells exhibiting problems such as high drop and
block rates, high latency or low throughput. In addition, it is now possible to identify the
number of unique subscribers seen in each bin, offering improved information on subscriber
behavior.
The new analyses are listed below:
Unique Subscribers
Worst N Cells (Blocks)
Worst N Cells (Drops)
Worst N Cells (High Latency)
Worst N Cells (Low Throughput)
Worst N Subscribers (Blocks)
Worst N Subscribers (Drops)
Worst N Subscribers (High Latency)
Worst N Subscribers (Low Throughput)
New UMTS analyses

Two new sets of analyses have been added to the analysis suite for UMTS:
Roamer: A set of new Roamer analyses provides visibility into the interaction of roaming
subscribers with the network, such as registration failures and the KPIs experienced.
These facilitate the speedy discovery of any unexpected problems facing roamers in
specific areas, using specific devices or from specific home networks:
Roamer Drops
Roamer Failures by Cell
Roamer Failures by Device
Roamer Registration Failures
Roamer Summary
Roamer Summary per Cell
Data: A set of new Data analyses offers insight into the subscriber experience for the
subscribers, devices and cells associated with the highest data volumes:
Top N Cell Volume
Page 55
Top N Device Volume

Top Subscribers Volume
In addition, a new RF Scatter analysis provides the ability to investigate the relationship
between KPIs.
VIP Module enhancements
For customers using the VIP Module, VIP processing has been streamlined in order to
provide a step-change improvement in performance. The number of VIPs now supported by
the VIP Module has also been increased dramatically.
12.1.2 ariesoGEO platform
Support for multiple new vendors: New parsers to support:

UMTS
i) ZTE: OSS V12 RNC V4
ii) Huawei Nastar 11 and PCHR R15
iii) Alcatel Lucent femtocell
LTE
i) Huawei Nastar 11
ii) NSN RL30 and above
The ariesoGEO platform now supports using Ericsson LTE with MMEs from any vendor,
via a separate Subscriber Identity Server that processes the MME data and provides the
necessary subscriber information to the parser
The DAS model introduced in version 4.2 has been extended to improve geolocation
around multi-antenna cell systems and repeaters
Geolocation is now performed more quickly, especially for rural cells with large
footprints
Indoor/outdoor call classification has been improved by using information about indoor
cells
Improvements in geolocation quality for LTE and GSM, particularly using double-pass
geolocation to select the most likely point from an initial set

No standard analyses have been deprecated or removed in this release.
LTE analysis changes
The following LTE analyses have been altered to run from the new summary tables:
Data Against Time

Data KPIs
Data KPIs per Bin Table
Downlink Data Throughput CDF
CQI by Downlink Channel Number

CQI by eNodeB
CQI by Frequency Band
CQI by Tracking Area Code
Page 56
Downlink Data Throughput Histogram

Downlink Data Volume CDF
Downlink Data Volume Histogram
Connection KPIs
Connection KPIs by Cell
Connection KPIs by Downlink Channel
Number
Connection KPIs by eNodeB
Connection KPIs by Frequency Band
Connection KPIs by Tracking Area Code
CQI by Cell
RF Health Index
Binned Mean Dominance CDF
Binned Mean Dominance Histogram
Binned Mean RSRP CDF
Binned Mean RSRP Histogram
Binned Mean RSRQ CDF
Binned Mean RSRQ Histogram
Performance KPIs
Best Cell Footprint RF KPIs
Best Cell RF KPIs

This section describes the main impact that the new and improved functionality will have on
existing GEOperformance systems.
LTE
The summary tables increase the size of the database for GEOperformance installations that
use LTE data by an additional 50%. So, for example, if the original LTE database was sized at
2TB, an additional 1TB of space should be allocated for the new summary tables.
There is no change in database size for customers who do not use GEOperformance for LTE.
Email and SMS alerts
Enabling email and SMS alerts require access and authentication to email and SMS
gateways.
12.4 Fixed Bugs

Bug ID
Bug Summary
Cases
19339
Missing Neighbours returns no results if GEOAreas share a network
CAS-10105
19027
Operator List shows out of date name for MCC/MNC 65502
CAS-10048
18155
Best Server Footprint RF KPIs analysis gives error with multiple GEOAreas
CAS-9874
5291
Encrypted IMSI/IMEI format differs between GEOperformance and GEOweb
CAS-9806
17682
Failure Reasons analysis does not show Signalling counts
CAS-9762
15889
Busy Hour (Daily Server) analysis always shows UTC time values
CAS-9469
18216
Problem Identification Wizard uses different Block % formula to analyses
CAS-9258
19411
NSN parser produces unexpectedly high Max throughput values on HS RAB
CAS-8984
Page 57
Bug ID
Bug Summary
Cases
15891
VIP IFHO Locations analysis uses different cell filter than other IFHO analyses
CAS-8802
13892
Some RF analyses aggregate by Best Sector, causing incorrect ARFCN filtering
CAS-8307
4635
Some multi-loader load servers give cache errors and stop loading
CAS-5153
CAS-9022
12.5 Known Issues

Bug ID
Bug Summary
Fixed In
19496
Some Common Performance KPIs analyses return rows with 0 values if LTE
and UMS technologies are not present on the system, but not if GSM is not
present
19466
In the variable editor, bounding boxes cannot be changed after creation
19457
New variables added to a document are not shown when the document is
opened.
Workaround: Click refresh to show the added variables
19376
When the filter for a map analysis is open, dragging a polygon onto the
analysis icon shows up in the tooltip but is not applied.
Workaround: Either drag the polygon onto the filter editor, or do not open
the editor and drag the polygon onto the filter icon. Do not drag a polygon
onto a filter icon while the editor is open
19296
If GEOperformance is shut down with a filter editor window open, a filter

editor window automatically opens the next time it starts up. However, this
window is not associated with any filters and cannot be used to set filters for
analyses
19252
The Loading Errors (UMTS) analysis cannot be sorted by TCode
16091
Cells' labels are still visible after cells are turned off in Network Layer
16068
Network Search displays distances rounded to two decimal places, but

searches on the original value
5.0.1
Workaround: To find cells based on a specific distance, click the Distance filter
and select the required distance from the list of values
14969
Right-clicking on a map icon representing a multi-technology site causes it to

become offset from the cells
Page 58

Clients can upgrade to GEOperformance version 5.0 from version 4.2 or later. Clients on
versions older than 4.2 will need to upgrade to 4.2 first.
documents:
Upgrade Guide: 5.0

Page 59
13.
Released June 2014

This maintenance release provides an important improvement to the 4.2 base version of
GEOperformance for clients using multiple GeoAreas with a single shared network. This
version of GEOperformance is compatible with Ericsson, Huawei and NSN vendor
equipment.
13.1 Fixed Bugs

Bug ID
19339
Bug Summary
Missing Neighbors returns results for only one GeoArea of shared network
Cases
CAS-10105

Clients can upgrade to GEOperformance version 4.2.5 directly from the following versions:
4.2.1 or later
4.2 (with database upgrade to 4.2.1)
This upgrade does not require a database upgrade.
Page 60
14.
Released June 2014

This maintenance release provides an important improvement to the 4.2 base version of
GEOperformance for clients using Huawei PCHR R14. This version of GEOperformance is
compatible with Ericsson, Huawei and NSN vendor equipment.
14.1 Fixed Bugs

Bug ID
19270
Bug Summary
Huawei R14 parser fails with RNC ID 0
Cases
CAS-10093

4.2.1 or later
Page 61
15.
4.2.3 is an internal maintenance release. It is not generally available.
Page 62
16.
Released May 2014

GEOperformance. This version of GEOperformance is compatible with Ericsson, Huawei and
NSN vendor equipment.
16.1 GSM dropped call definition

Version 4.2.2 of GEOperformance has been updated to correctly count some drops that
previous versions labeled as normal releases.
In previous releases of GEOperformance, for GSM dropped calls where call clearing was
initiated by a Clear Request from the BSC, the cause value in the Clear Request was
superseded by the cause value in the subsequent Clear Command from the MSC.
If this Clear Command had a cause value that is classed as a dropped call, for example Radio
Interface Message Failure, this resulted in the call being correctly classified as a drop.
However in some cases the MSC may be configured to map the Clear Request cause to a
Clear Command cause value that is classed as normal release, such as Call Control. In these
cases, the dropped call was incorrectly classified as a normal release.
Since clearing initiated by a Clear Request from the BSC always indicates a dropped call,
ariesoGEO 4.2.2 ensures that the cause value in a Clear Request takes priority over the cause
value in a subsequent Clear Command.

GSM
On systems where the MSS is not configured to map Clear Request cause values to a droprelated Clear Command cause value, ariesoGEO will show an increased number of dropped
calls.
It is not possible to predict the impact of this change as that is entirely dependent on
individual MSC cause mapping configurations. However, for correctly configured MSCs there
will be no change in drop volume at all.
Ericsson UMTS
The ManagedNetworkLoader will now reject a network configuration if it contains Ericsson
RNCs (identified as RNCs where over 90% of the sectors use Ericsson technology) for which
no version is set. This may result in difficulty loading some networks until all RNC versions
have been correctly identified and set.
Page 63
This change is necessary to prevent bad data being loaded into the database.
Ericsson LTE
GEOperformance version 4.2.2 includes an enhancement that increases the number of
segments with associated timing advance information, resulting in improved LTE geolocation
accuracy. Sample field data shows an increase of connection segments with associated
timing advance information from 47% to 96%. Note timing advance information is only made
available to ariesoGEO if Ericssons Enhanced Cell ID feature is enabled.
16.3 Fixed Bugs

Bug ID
Bug Summary
Cases
16798
Day Hour Settings filter does not work correctly with summary analyses
CAS-9625
17259
Very late data summarized twice
CAS-9617
14597
Load Network From Database' option does not update network
CAS-9194
14255
Huawei UMTS Layer3 Measurement Report shows duplicate entries
CAS-9189
13750
NASTAR GSM does not parse data if first file is CHR
CAS-9152
14595
UMTS iterator performance slow for RNCs with large area footprint
CAS-9067
13995
Vendor-specific Completion Code filters not shown
CAS-8681
16500
ACP export returns no results for pathloss analysis
CAS-8384
12746
Confidence slider in user interface causes user errors
CAS-8377
14749
LTE does not associate TA received after handover with segments
11789
Some Ericsson GSM signalling drops reported as normal releases
16.4 Known Issues

Bug ID
Bug Summary
Fixed In
16069
In the Map Control, hovering over the top-level Network Layer shows a
different number of cells to hovering over the individual Cells layers
15889
In the Busy Hour (Daily Server) analysis, the time values are based on UTC
even when the GeoArea timezone is not UTC. Only the Hour correctly uses
the GeoArea timezone
14951
In the Chart Control, the random color chosen for the chart can be too light to
see clearly
5.0
Workaround: If the color is too light, click on that color in the key to change it
Page 64
14940
On GSM, cells with a latitude and longitude incorrectly set to 0 are loaded into
the database with a latitude and longitude of null. This causes problems with
neighbour analyses

4.2.1
Page 65
17.
Released March 2014

GEOperformance. This version of GEOperformance is compatible with Ericsson, Huawei and
NSN vendor equipment.
17.1 Ericsson LTE DL Throughput Calculation

In version 4.2.1, the downlink throughput calculation for Ericsson LTE has been updated to
align with the Ericsson PM calculation and ensure that the data volume used in the
numerator excludes data from the last TTI to correlate with the throughput time in the
denominator which excludes the last TTI.
The new calculation is:

Impact of Changes
Ericsson LTE downlink throughput in version 4.2.1 will be lower than in version 4.2.0, but
more accurate and consistent with the throughput reported by Ericsson PM.
Because GEOperformance aligns the calculations of volume and throughput, the final TTI will
not be included in data volume metrics, and these will therefore be lower than in version
4.2.0.
17.2 Fixed Bugs

Bug ID
Bug Summary
Cases
13324
Double-clicking .geo file prompts for server reboot
CAS-9303
8778
NSN parser gives 'Unknown cell state: None' error
CAS-8824
CAS-9141
11867
Color scheme applied to analysis reverts to default after recalculation/reload
CAS-8710
11816
GEOweb only stores last VIP call segment, resulting in wrong Voice MOU
CAS-8592
9735
ACP export: BS POWER and CPICH POWER PERCENT set to CPICH dBm
CAS-8582
11377
8833
CAS-9114
PCHR R14 538 Layer 3 Ec/Io Graph shows raw (positive) Ec/Io values
CAS-8505
Page 66
Bug ID
Bug Summary
Cases
10180
NSN parser parses no data when Megamon timestamps differ >5 mins from
event times
CAS-8179
9735
ACP export: Warning about CPICH power mismatch marked as error
CAS-8127
CAS-8277
11132
Manual focus change needed to commit list names in Admin Console
CAS-7803
13594
NSN: too many completion codes set to Unknown, especially IFHO failures
CAS-7227
Unknown
14575
UMTS UE Capabilities filter returns data with any of selections not all
13882
LTE geolocation produces artifacts on some systems
10667
Huawei 2G includes incoming handovers in block rate calculation
17.3 Known Issues

Bug ID
Bug Summary
Fixed In
14749
On Ericsson LTE, some segments do not have Timing Advance information.
4.2.2
Cause: TA details that arrive after a handover cannot always be assigned to

connection segments from before the handover
14270
When recalculating raster map analyses, custom gradient colors reset to the
default gradient
14167
In the Common Individual Connection Segments analysis, the Call ID column

should be named Connection ID
14138
In the Common Performance/Data KPIs by Frequency Band analysis, only

GSM information is usefully shown

4.2
This upgrade requires a database upgrade. For full information on how to upgrade to
GEOperformance 4.2.1, please refer to the following documents:

GEOperformance tech note: Database Upgrade: 4.2.1
Page 67
18.
Minor Release: Version 4.2
Released February 2014

This minor release provides a set of significant new features. Highlights of this release
include:
New call model for LTE: The LTE database and analyses have been improved in order to
provide a basis for market-leading location intelligence on LTE networks. Future
versions of GEOperformance will be able to provide a level of insight into LTE similar to
that it currently provides for UMTS
Support for Alcatel-Lucent LTE: Arieso expands its LTE GEOperformance offering with
the capacity to enjoy customer-centric location intelligence on Alcatel-Lucent LTE
networks
Improved neighbor planning: A number of improvements have been made to the
neighbor planning algorithms, including better handling of building and tunnel cells, and
cells with small neighbor lists
Numerous geolocation improvements, infrastructure upgrades and improvements to the
support for existing vendor formats
In Development
The following features are being tested in the current version of GEOperformance, and are
expected to be available for purchase in future versions. If you are interested in field testing
any of these capabilities, contact your Arieso Account Manager:
Advanced Diagnostics Module: The Advanced Diagnostics (AD) Module provides expert
users with the ability to delve into information available from analyzing measurement
reports, timings between key events, and location area/routing area updates. The AD
module requires the ADM - Advanced Diagnostics Module licence
Automatic Neighbor Relations (ANR): This GEOson capability is initially included within
the GEOperformance application to enable effective open loop and per-project
operation during customer field tests. The ANR updates in GEOperformance 4.2 extend
GEOperformance's existing Neighbor Planning capabilities to allow engineers to actuate
the network updates directly from the application following the generation of a new
GEOperformance Neighbor Plan
Automatic Analysis Triggers: Enables GEOperformance to regularly search for network
performance issues, and automatically generate analyses that will help resolve them. In
the initial version, network analyses are limited to neighbor relations
Crossed Feeder analysis: A sophisticated algorithm uses information about cell neighbor
relationships and geographical locations in order to identify sites whose cells may have
had their antenna feeders crossed
Page 68
Support for ZTE UMTS: Clients will be able to exploit Arieso's market-leading customer
centric location intelligence on ZTE networks
18.1 New Features

New LTE Call Model
The LTE database tables have been restructured to supply an enhanced view of LTE calls,
bringing the analysis functionality up to a comparable level as UMTS.
The existing Ericsson parser and LTE analyses (including Common analyses that show LTE
data) have been adapted in order to use the improved database structure.
Some aspects of the changes include increasing the accuracy of call counts and changing the
definition of segments, so numbers of both calls and segments shown in the LTE analyses
will be lower after the upgrade and more in-line with other views of the same data in other
systems deployed in operators.
Note: During upgrade to the new database structure, any LTE data currently stored in the
database will be lost.
New Alcatel-Lucent Parser
Data from Alcatel-Lucent LTE networks can now be loaded into the GEOperformance
database, enabling clients using Alcatel-Lucent technologies to employ GEOperformance's
unique insights to deliver customer-centric location intelligence on their networks.
Note: Drop and block information cannot yet be investigated on Alcatel-Lucent networks.
Improved Neighbor Planning
The existing neighbor planning wizard has been significantly improved with new features
and more sophisticated algorithms.
Specific improvements include:
The parameters used to calculate a neighbor plan can now be saved as a scenario,
enabling users to run later exercises with exactly the same settings
In UMTS neighbor plans, users can now choose whether to always keep rarely-used
neighbor relations where one cell's neighbor list is dominated by a single neighbor,
and/or where there are high propagation delays. These conditions often indicate cells in
buildings and tunnels, which have rarely-used neighbor relations that must be kept
In UMTS neighbor plans, users can now specify a target neighbor list length. Where the
removal of neighbors would reduce the list below this length, the best of the neighbors
are added back to the list
The existing neighbor plan scheduling has been extended. Inter-RAT neighbor plans can
now be scheduled to run at specific intervals
Page 69
Improved Problem Identification

New functionality has been added to the existing problem identification feature in order to
reduce the manual element of searching for problems. The latest version of problem
identification provides:
Scheduling: Problem searches can be set up to run regularly on known problem areas
without the need for manual intervention
Storing of problem results: The results of problem searches are now saved in the Results
tab. This enables users to investigate the problem areas that were identified by
automatic problem searches, or to view the results of old searches to compare them
with the current status of the same area
Support for HSPA+ in UMTS

GEOperformance now provides the ability to view the HSPA+ capabilities of cells and
perform investigations using HSPA+ services:
HSPA+ capabilities for cells are shown in the Cell Group Details window
The UMTS Active Network Cells analysis now includes each cell's HSPA+ capabilities
HSPA+ information for calls can now be viewed in Layer 3
UMTS analyses can be filtered by specific HSPA+ services and the HSPA+ Data service
group
Improved support for DAS

The GEOperformance network model more accurately represents all antennas in a smallscale distributed antenna system (DAS), and determines the footprint of the DAS based on
information about the individual antennas. The locations of the individual antennas are
reflected by the cell icons in the map control.
Geolocation algorithms use this information when geolocating calls in the area of in a multiantenna cell configuration.
The new DAS model is optional, and requires a change to network loading. If preferred,
customers can continue using the old model without making any changes to their system.
Other changes
Improved LTE geolocation algorithms provide increased accuracy and calculation speed
Ericsson-specific messages introduced in Ericsson RNC Software versions W12 and W13
are now available in Layer 3
Raster maps can now be exported as IMG files, enabling them to be viewed and
analyzed in popular GIS tools
ACP Export has been improved by updating GEOperformance to provide additional
sector information
The RF KPIs analysis now offers the option of using linear averaging (in Watts) or
logarithmic (in dB) for each of Ec/Io, RSCP and UE Transmit Power
Page 70

No standard analyses have been deprecated or removed in this release.

This section describes the main impact that the new and improved functionality will have on
existing GEOperformance systems.
LTE
Any LTE data that has already been loaded into the database will be lost when the database
is upgraded.
Numbers of both calls and segments shown in the LTE analyses will be significantly lower
after the upgrade.
Improvements to LTE geolocation also require an update to the load chain configuration.
UMTS
On Ericsson systems, in order to be more consistent with PM Stats, a number of completion
codes have been redefined from Block to Unspecified. Analyses on Ericsson data will
therefore show lower numbers of blocks following upgrade. This is in line with the
representation of the same data in other systems deployed within the operator.
On NSN systems, an improvement in tracking multiple radio links results in analyses showing
lower numbers of segments. In addition, enhancements to the parser's handling of calls that
are active when the parser closes a fifteen minute period result in more segments being
successfully recorded from such calls. Overall, on NSN systems GEOperformance will show
slightly more segment 0s, but fewer segments in total.
Automatic network loading must be updated in order to provide base station power
information for the ACP Export feature. In addition, customers wishing to use the improved
DAS model will need to reconfigure their load chains.
18.4 Fixed Bugs

Bug ID
Bug Summary
Cases
13482
Import of GSMA TAC list fails if device model names contain quotes ("")
CAS-8940
8881
UMTS GLR Size analysis fails to update RNCs unless number of RNCs changed
CAS-7990
11869
Some Ericsson failure reasons assigned to incorrect completion code
CAS-7723
7279
Message log does not include LTE progress when running Common analyses
CAS-7184
13464
Neighbor plan sometimes incorrectly recommends ADD instead of KEEP, and actuation fails
Page 71
18.5 Known Issues

Bug ID
Bug Summary
Fixed In
13907
On Huawei R12 systems, if a multiRAB call with the service CS (AMR) + PS

(General) is dropped, GEOperformance records two CS (AMR) drops and no PS
(General) drops
13886
Unable to view a Google Earth report in GEOWeb
5.1
13882
The latest LTE geolocation algorithms can produce straight line artifacts on
systems that do not provide Timing Advance or Measurement Report data
4.2.1
13759
In LTE Ericsson, events that are reported more than 10 seconds after
handover will not be attributed to the session. This can result in values such
as data volume and throughput appearing different between analyses and
Layer3
5.0
13716
After export to Google Earth, points analyses do not display a color legend
13542
In UMTS, analyses filtered by a packet-switched service group may show

circuit-switched drops and blocks, and vice versa
Workaround: Use specified services rather than service groups. Filtering by
service group includes multiRAB PS + CS services that will generate blocks and
drops on the unwanted domain
13408
In UMTS, the RF KPIs at Percentiles analysis shows values that are better than
the specified percentile for some KPIs, and values worse than the specified
percentile for others
4.2.1

Clients can upgrade to GEOperformance version 4.2 from version 4.1.3 or later. Clients on
versions older than 4.1.3 will need to upgrade to 4.1.3 first.
documents:
Upgrade Guide: 4.2

Page 72
JDSU UK Ltd
Astor House
Newbury Business Park
London Road
Newbury
Berkshire
RG14 2PZ
United Kingdom
JDS Uniphase Corporation

Embassy Row 300
6600 Peachtree Dunwoody Road
Suite 150
Atlanta GA
30328
USA
Tel:
Fax:
Tel:
Fax:
Email:
Web:
+44 (0) 1635 232470

+44 (0) 1635 232471
+1 678 904 2424

+1 678 904 2429
info@arieso.com
www.arieso.com
Page 73

Arieso - GEO 6 1 1 Rel Guide

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Arieso - GEO 6 1 1 Rel Guide

Caricato da

Copyright:

Formati disponibili

GEOperformance 6.1.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

MAINTENANCE RELEASE: VERSION 5.1.3................................................................................. 21

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

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

MAINTENANCE RELEASE: VERSION 5.1.2................................................................................. 23

Copyright 2015 JDSU UK Ltd

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

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

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

MAINTENANCE RELEASE: VERSION 5.1.1................................................................................. 28

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

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

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

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

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

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

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

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

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

MAINTENANCE RELEASE: VERSION 5.0.4................................................................................. 41

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

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

MAINTENANCE RELEASE: VERSION 5.0.3................................................................................. 42

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

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

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

MAINTENANCE RELEASE: VERSION 5.0.2................................................................................. 45

Copyright 2015 JDSU UK Ltd

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

MAINTENANCE RELEASE: VERSION 5.0.1................................................................................. 46

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

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

INSTALLATION GUIDANCE ........................................................................................................... 50

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

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

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

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

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

INSTALLATION GUIDANCE ........................................................................................................... 59

MAINTENANCE RELEASE: VERSION 4.2.5................................................................................. 60

INSTALLATION GUIDANCE ........................................................................................................... 60

MAINTENANCE RELEASE: VERSION 4.2.4................................................................................. 61

INSTALLATION GUIDANCE ........................................................................................................... 61

MAINTENANCE RELEASE: VERSION 4.2.3................................................................................. 62

MAINTENANCE RELEASE: VERSION 4.2.2................................................................................. 63