RANOPT Technical Overview PDF

Technical Overview
RANOPT Technical Overview
Release V6.1
Author: AIRCOM InternationalAIRCOM International

Date: 18 June 2008
Ref: I-SM-SR-EM-RA-004
Version: 3
Status: Approved
Sec. Class: Commercial in Confidence
Copyright 2006 AIRCOM International - All rights reserved. No part of this work, which is protected by copyright, may be reproduced in
any form or by any means - graphic, electronic or mechanical, including photocopying, recording, taping or storage in an information
retrieval system – without the written permission of the copyright owner.
Commercial in Confidence
Contents
1 Document Control..................................................................................................................4
1.1 Revision History ...............................................................................................................4
2 Introduction to RANOPT .........................................................................................................5
RANOPT within the Optimisation Analysis Process .......................................................................6
2.1 Why RANOPT? - Key Benefits of RANOPT ...........................................................................7
2.1.1 Architecture ............................................................................................................9
3 Key Modules ....................................................................................................................... 10
3.1 Data Loading ................................................................................................................. 10
3.1.1 Configuration ....................................................................................................... 10
3.1.2 Data Load ............................................................................................................ 11
3.2 Database Explorer ......................................................................................................... 12
3.3 Filtering – Filter Manager and Data View......................................................................... 13
3.3.1 Data Manipulation ................................................................................................ 16
3.3.2 Cell Snapshots ...................................................................................................... 16
3.4 Resolving Cells to Drive Files .......................................................................................... 17
3.4.1 Resolving cell sites for UMTS drive-test data ........................................................... 17
3.4.2 Resolving cell sites for GSM drive-test data............................................................. 19
3.4.3 Propagating missing UMTS parameters .................................................................. 20
3.4.4 Propagating missing GSM parameters .................................................................... 20
3.5 Workspace, Replay and Data View .................................................................................. 20
3.5.1 Work space .......................................................................................................... 20
3.5.2 Drive Down Analysis, Display and Replay ................................................................ 23
3.5.3 Network Message Analysis .................................................................................... 26
3.6 Reporting – Report Registry ........................................................................................... 27
3.6.1 Excel Analysis Reports ........................................................................................... 28
3.7 Benchmarking ............................................................................................................... 32
3.8 User Comment .............................................................................................................. 33
3.9 Scheduler ..................................................................................................................... 34
3.9.1 File Loading Tasks ................................................................................................. 35
3.9.2 Filter Creation (and Apply) .................................................................................... 36
3.9.3 Report Running Task ............................................................................................. 37
3.10 Exporting Data .......................................................................................................... 38
4 ENTERPRISE Integration ....................................................................................................... 38
5 Different RANOPT Product Versions ..................................................................................... 40
5.1 RANOPT Server (Server Version) ..................................................................................... 40
5.2 RANOPT Standard (Standalone user license) .................................................................... 40
5.3 RANOPT Lite (ASSET3G drive test module) ...................................................................... 41
6 RANOPT Physical Architecture: Windows Client-Server System............................................... 41
6.1 Software Requirements ................................................................................................. 41
6.2 IT hardware Requirements ............................................................................................. 42
7 Conclusion .......................................................................................................................... 43
Author: AIRCOM International RANOPT Technical Overview Page 3 of 42

Date: 18 June 2008 I-SM-SR-EM-RA-004 Commercial in Confidence
1 Document Control
1.1 Revision History
Revision Date Name Revision
Number
1 24/09/2007 D Fernando Initial doc
2 05/10/2007 D Fernando Reviewed to include updates for cell
resolving and smaller enhancements
2a 12/06/2008 D Fernando Updates for V6.1
3 16/06/2008 D Fernando Reviewed and Approved for Release

2 Introduction to RANOPT
RANOPT is an advanced and flexible, multi-technology, measurement based statistical
analysis tool developed for mobile operators looking to effectively optimise their radio
network plan. The solution provided aims to support all of the following criteria which an
operator would typically focus on:
Maximising ARPU – average revenue per user
Minimising operational costs
Maintaining satisfied subscribers
Diagnosing and resolving service problems quickly
Analysing data easily
The ability to assess which services are most successful
The successful introduction of new generation technologies and services
Designed in conjunction with a leading European operator, RANOPT is geared to undertake all
post processing and specific analysis requirements faced by optimisation engineers. Thus
whether the radio network meets coverage, grade of service and handover objectives etc. can
be quickly and easily analysed, assessed and necessary corrective action swiftly taken.
Based on a central database (DB) store, RANOPT has been designed to facilitate the loading
and analysis of 2G, 2.5G, EDGE, 3G, HSDPA and DVB-H drive data. Once data is loaded, the
possibilities to trouble-shoot and the capability of reporting on the measurement data is
limitless. RANOPT’s reporting use is not simply limited to engineering trouble shooting
activities but can be used for management level assessment of optimisation activities,
benchmarking and trending.
RANOPT’s full integration within the AIRCOM ENTERPRISE tool suite provides access to other
key planning/optimisation and performance modules. This integration enables transparency
of information crucial for effective optimisation and tuning of the network plan.
RANOPT’s unprecedented flexibility, powerful functionality and ease of use make it the
definitive tool for any operator looking to improve or enhance the quality and performance of
their network.

RANOPT within the Optimisation Analysis Process
Figure 1: RANOPT in the optimisation cycle
Figure 1 shows RANOPT within a typical optimisation analysis process. RANOPT has been
designed to be the key tool in analysing and optimising the planned radio network. With the
ability to overlay coverage and performance data, the post processing tool can significantly
aid in the overall optimisation process by adding transparency of information crucial to
identifying and troubleshooting problem areas.
RANOPT’s placement within the AIRCOM ENTERPRISE tool suite enables easy integration with
key planning/optimisation and performance management modules such as:
Import, correlation and overlay of coverage data from ENTERPRISE ASSET / 3G
Correlation and overlay of performance data from ENTERPRISE OPTIMA
This enables engineers to see coverage issues such as shadowing or large fades that may be
causing the radio plan quality/grade of service to degrade. It could also investigate areas that
have been identified with good coverage but have shown consistently poor performance (for
example a large number drop calls) which could be due to effects of pilot pollution.

Seamless access to terrain, clutter data, scan maps, polygon and vector information, together
with the site database with all relevant radio plan parameters, enables RANOPT to therefore
be effectively used for analysis and optimisation activity.
Version 6.1 Highlights
1. . 40% increase in speed of TEMS loading on V6.1
 Compared to V6.0, increase in average speed of loading for larger files and
an exponential increment in speed of loading as the file size increases with use of all
CPU’s on the machine.
Benefit: Fast and reliable TEMS support and analysis for all released TEMS versions (TEMS
Investigation v6.x - v8.x) to date.
2. 50% less time spent on optimisation setup tasks
 By using the scheduler to automate work process thus increasing productivity. 50% less
mouse clicks to get to the problem if Scheduler Job/Tasks used.
Benefit: Fast and automated approach for optimisation workflow process improvements.
Saving of approx 2hrs of an engineer’s time per day (i.e. 25% of engineer’s time saved
per day considering an 8 hour day). Thus a possible 5 man days saved per
month with an automated workflow process incorporating the RANOPT Scheduler. The
time saving increases for benchmarking activities.
3. Improved usability/flexibility
 Log file management and Filter creation Enhancements for quick selection and running
of filters
 Workspace and analysis module (line chart) improvements to aid drill down analysis
Benefit: Usability improvements allowing 40% faster log file selection for creation of filters for
multiple device files and improvements to aid drill down analysis activity for
optimisation.
.
2.1 Why RANOPT? - Key Benefits of RANOPT

Analyse virtually any scanned data or UE/Test Mobile(TM) data format (including
AGILENT, ANRITSU, NEC (VTB, VTX) NEMO, TEMS, CLARIFY, R&S, ASCOM, SwissQual,
COMARCO(Scanner) )
Bulk load and management of drive test data (off line/out of hours if desired) - automatic
loading of multiple types of drive files with ability to monitor load progress, file only need
to be moved to a location specified, and it is checked, parsed and loaded

Data warehouse solution giving transparency all users across the organisation –
improves optimisation efficiency and avoids duplication of work.
Fast and flexible filtering system – allows for custom queries to be built up with quick
and easy selection of data and one click process for creation of multiple filters.
Quick and easy polygon filtering and optional data manipulation (binning/averaging) and
exclusion rules if required.
Call categorisation – identification and classification of calls
Incorporates powerful and flexible graphing system with replay functionality
Any data can easily be displayed on the 2D View – indicate best server Ec, Ec/Io, Rx Lev,
Rx Qual pilot polluted areas, C/I, throughputs, Events(call setups/drops/ failures etc)
Layer 3 analysis and decoding with easy to use search and find capabilities.
Comparison and synchronisation of Scanner and UE/TM data.
Benchmarking capabilities – compare 2 or more networks, vendors and allows easy
before and after analysis.
Ability to easily correlate drive SCs, BSIC/BCCH’s and Cell ID with snapshots of the
planning/optimisation site DB stored for future use.
Scheduler for of activities done at regular periods or for one off activities at a certain
time – e.g. file loading , creating and applying filters, batch reporting
Enables overlay of network performance stats and planning data
Shipped with library of integral optimisation reports, which include integrated reports
between Enterprise and RANOPT e.g. neighbour analyser for suggested neighbour auto
updates if required – full library of reports available for UMTS/HSDPA/GSM/GPRS and
EDGE, and allows the custom creation of reports as well.
Export resultant data to MapInfo and MS-Excel.
In addition to the above, integration into the planning tool allows drive data to be used
for CW (signia) file generation for model tuning activities.

2.1.1 Architecture
The system architecture is as shown above in Figure 2. All drives collected can be loaded, a
process that can be carried out off line e.g. overnight, with no user intervention. RANOPT can
be deployed using a terminal-server/client-server architecture thus allowing drives to be
loaded in from any location. It exploits the power of an Oracle database (DB) to store all of
the raw, filtered and manipulated (i.e. binned and/or averaged) data, and reports. All data
can be shared and accessed from anyone in the organisation at any time. RANOPT’s flexibility
allows the users to mine data through the use of custom reports, queries and algorithms.
Regularly done tasks can be scheduled which allows significant time savings in carrying out
day to day tasks and the scheduler also enables database maintenance activities to be carried
out via the tool itself.
Figure 2: RANOPT Architecture

3 Key Modules
3.1 Data Loading
3.1.1 Configuration
Through an administrator facility, RANOPT incorporates a powerful decode engine which
allows for many different formats of data to be loaded into the database, without changing
the program code every time a new format is introduced. The user creates the custom
decode engines via configuration of Equipments window, which essentially references the
vendor equipment, that is used to load specific vendor drive log files into the database.
The creation of these equipment types creates a folder structure (‘in’, ‘out’ and ‘err’
directories) in a user defined location and the user simply places a file to be loaded into a
specified directory - the ‘in’ folder. This directory is continuously monitored by the
parser/loader which runs as a service, thus the files placed in this directory are automatically
picked up and loaded into the DB. Error logs are kept on the loading done for analysis if any
problems occur during the loading process. Multiple different types of files can be loaded in
simultaneously. With this process of file load, drivers themselves who have collected data can
load logs into the DB, with no requirement for planning/optimisation engineers for this
activity. The file loading can be done independently and thus all analysis work can be
continued without interruption as file loading occurs. Loading can also take place offline or
out of hours at it does not require the application to be open. The only requirement is to have
the DB accessible and the windows RANOPT parser/loader service started. With a central DB
used across the organisation, once the drives are loaded, all users connected to the RANOPT
database have access to the loaded data and loading of measurement log files is a one off
activity.
Thus the concept of loading a drive test each time for analysis is no longer required. All the
data is stored in a fast and central Oracle database and thus does not need to be re-loaded.
The user is able to extract specific data through the use of the filtering functionality.
Figure 3a: RANOPT Administrator - Configuring Import Sources and Registry Settings

The RANOPT administrator is additionally used to define all the networks considered.
Automatic Network Detection can also be used in RANOPT for data loading (NEMO files only).
In this case, the system can be configured with the appropriate operator network details such
as the network code, carrier numbers and frequencies and this is used by RANOPT in order to
check the files and automatically load the drive logs under the correct network. The concept
of defining networks becomes useful when benchmarking activity for several networks is
done. Filtering for selection of specific files that belong to specific networks becomes easer
with the inclusion of the ‘Network’ defined in the filtering process.
Figure 3b: RANOPT Administrator - Configuring Networks
The RANOPT administrator also allows users to register all data manipulation techniques to
be used. Log of any errors which occur in importing files can also be viewed. Further, the
Registry Settings are set through the administrator to specifying the oracle database into
which the measurement data is to be loaded.
Other general administrative tasks are also handled through the RANOPT administrator,
including creation of user permissions and groups, DB and report upgrade and L3 message
updates. The Installation wizard can also be run from this module allowing a new empty
Oracle database to be created. The required tables in the database for RANOPT are then
automatically loaded and configured allowing for quick and easy installation of the DB for use.
3.1.2 Data Load

Once the required equipment type and network is configured within the RANOPT
Administrator, load of all drive files is possible via directly moving files a directory as
described in section 2.1.1 or by using the Submit Results – Files for Import window within
RANOPT. Each file loaded into the RANOPT database is indicated by its filename, listed under
the date it was loaded. The original file extension is kept. If a file with an extension .fs1 is
loaded, the extension will be visible. For example, filename.fs1. Drives files containing
multiple equipment files as can be obtained using for example TEMS or R&S. The file list in
this case has been reorganised in v6.1 and there is now an extra level in the hierarchy,
identifying each separate device in a single file as a sub-entity.

Rather than MS1, MS2 and so on, the device will be identified by their phone/scanner type if
this information is available in the measurement file.
Previously v6.0 and, a measurement file would be divided into separate files per device and
therefore had to be treated as separate entities, which were viewed, deleted and used in
filters individually. However, with the devices listed as sub-entities, it is much more helpful
because they can be viewed, deleted and used in filters as a group, by selecting the parent
file. Individual devices in a file can now be deleted.
Further geo-mapping of UE/TM measurements files not containing positional information
with GPS information from scanner measurement files can also be done prior to loading of
the files.
The information as seen in the ‘Load Progress Monitor’ tab is also stored in the error log
configured via the administrator.
Figure 4: File Loading
3.2 Database Explorer

Progress of file load into the database and listing of files already loaded can be found through
the RANOPT database explorer module. This module can be accessed via both the front end
of RANOPT and through the windows start menu under the Enterprise application options.
Details about the file loaded and any problems loading the file can be obtained from this
module as well.

Figure 5: Database Explorer
3.3 Filtering – Filter Manager and Data View

Following file load into the DB, the list of files displayed is the list of the latest files that have
been loaded in the last month. Each file loaded into the RANOPT database is indicated by its
filename, listed under the date it was loaded. As mentioned previously, the original file
extension is kept. The log files are in descending order in time, so that the most recently
driven drive test files are listed at the top.
A ‘Filtering’ process is used to isolate the required drives for analysis termed Filters in
RANOPT. Several categories are available to drill down to the files in the DB that the users are
interested in analysing
Technology type
Data type ( Scanner/ UE/TM)
Date/time
Networks/Operators
Carriers/Frequencies
Equipment
File Comments - if available for the equipment type used.
Further optional manipulation of the filter can done via

Data manipulation ( binning)
Exclusion rules
Polygons

Additionally, the filters generated can be associated with Cell Snapshots from the planning
site database taken via a one click process in RANOPT. Cell Snapshots taken allow drives to be
correlated to the correct site/cell configurations at the time the drives were done. Thus
regular snapshots can be taken from the planning DB and associated as required with the
Filters created, avoiding the need for import and export of site data from and to RANOPT.
Display of drives is done via the GIS available in Enterprise enabling all site information,
map/height/clutter information and drives logs to be display in one location. Drives can also
be overlaid on predicted data, with analysis on the GIS done via RANOPT to indicated
difference in measured and predicted data.
These filters created using the filter wizard are then stored in the database for all users to
access if created under the Public Filters window. When a user modifies a public filter, all
other users connected to the database are immediately alerted.
Filters with polygon information associated are also listed with a different icon to indicate
that polygon filtering has been carried out.
Figure 6: RANOPT Filter Manager and Filtering Creation Module
The way in which filters are created has been enhanced, to make filter creation more
straightforward in v6.1.
When creating a filter, there are now three different options, enabling the user to create
three different types of filter:
Figure 7: filter creation options

Choosing different types of filter
Merge All Files Filter

This option merges all of the devices in all of the selected measurement files into a single
filter.
Merge Devices Filter

This option takes all of the selected measurement files and groups them into several filters
each containing the devices that have the same device name. The device name is used to
link up the devices - for example, for Ericsson TEMS; this would be based on the device
names MS1, MS2 and so on. This is to ensure that the system is kept as generic as possible
as very few vendors specify how the equipment (device) is connected to the device name
used.
For example, we have two files - one with devices Nokia and Ericsson (device names MS1
and MS2 respectively) and one with devices Nokia and Samsung (MS1 and MS3
respectively). This picture shows an example:
Example of measurement files

If we use the Merge Devices option, then three filters are created - one with the two Nokia
devices (based on MS1), one with an Ericsson device (based on MS2) and one with the
Samsung device (based on MS3). This picture shows an example:
Figure 8: Merge Device Option Filter creation
Example of filters created using the Merge Devices option

The device name (MS1, MS2 and so on) is used to link up devices to go in the same filter.
All of the drive equipment should be set up in the same way, so as to merge all of the
required drives. It is best to pre-set a procedure for use of the devices as confirmed with
customers for which this features was designed to facilitate large scale filter
creation/merge.

Individual Filters
This option creates a separate filter for each device found in each measurement file.
Therefore, even if the same device exists in more than one file, a separate filter is created
for each instance.
3.3.1 Data Manipulation

In order to generate useful and accurate statistical analyses, the measured data needs to go
through a binning or normalisation process. This prevents invalid or unwanted data from
skewing the results.
For example, data pertaining to one particular scrambling code may not be a large enough
sample size to be included in the analysis with other scrambling codes. The data can also be
binned to reduce the number of measurement point required for analysis.
RANOPT comes standard with binning/averaging and normalisation techniques for both
scanner and UE data, although it is possible to create others.
3.3.2 Cell Snapshots

Cell Snapshots from the site database are used in order to ensure that the correct site
configurations are associated with the drives done at a particular time. This process of pulling
cell snapshots both 2G and 3G can also be an automated activity done at user defined time
intervals. Snapshots of static filters (from the planning DB) and from user and standard
polygon defined are also enabled with a view available for browsing information extracted.
Figure 9: Cell Snapshots

From V6.0 onwards enhancements to the way in which the cells resolving is done was carried
out. The previous algorithm used was based on a distance calculation. To make this resolving
process more accurate several methods which take a priority order as described in the next
section is used.
3.4 Resolving Cells to Drive Files
3.4.1 Resolving cell sites for UMTS drive-test data
Cell sites for UMTS data are resolved in the following order. First, RANOPT attempts to resolve
the cell by using the UCID. The cell UCID is a concatenation of the RNCID and CI values as a binary
string. If the UCID is not available, RANOPT will attempt to resolve the cell by using its CGI. The
cell CGI is constructed by concatenating the MCC, MNC, LAC and CI values. If neither the UCID
nor the CGI is available, RANOPT will attempt to resolve the cell by using a combination of
CI/MCC/MNC and distance, then CI/UARFCN and distance and finally SC/UARFCN and distance.

Resolve by UCID
Yes
Cell Resolved?
No
Resolve by CGI
Yes
Cell Resolved?
No
Resolve by CI/MCC/MNC and distance
Yes
Cell Resolved?
No
Resolve by CI/UARFCN and distance
Yes
Cell Resolved?
No
Resolve by SC/UARFCN and distance
Done
Figure 10: Resolving cell sites for UMTS drive-test data.

3.4.2 Resolving cell sites for GSM drive-test data
Cell sites for GSM data are resolved in the following order. First RANOPT attempts to resolve the
cell by using its CGI. The cell CGI is constructed by concatenating the MCC, MNC, LAC and CI
values. If the CGI is not available, RANOPT will attempt to resolve the cell by using a combination
of CI/MCC/MNC and distance, then CI/BCCH and distance and finally BCCH/BSIC and distance.
Resolve by CGI
Yes
Cell Resolved?
No
Resolve by CI/MCC/MNC and distance
Yes
Cell Resolved?
No
Resolve by CI/BCCH and distance
Yes
Cell Resolved?
No
Resolve by BCCH/BSIC and distance
Done
Figure 10: Resolving cell sites for GSM drive-test data.

3.4.3 Propagating missing UMTS parameters
Missing CI, RNCID, LAC, MCC and MNC values are propagated forward and backward, across
measurements with consecutive timestamps that share the same SC.
3.4.4 Propagating missing GSM parameters
Missing CI, LAC, MCC and MNC values are propagated forward and backward, across
measurements with consecutive timestamps that share the same BSIC/BCCH.
3.5 Workspace, Replay and Data View

Following filter creation for selection of the data of interest, analysis can begin immediately
by viewing measurement data and running first pass analysis on problems identified.
3.5.1 Work space

The workspace allows users to choose up to 10 filters at one time that will be used for
analysis from the full filter list Filter Manager and add these into a separate module for easy
view and access. Once a Filter is added to the Workspace the Replay icons become enabled
and full replay and display functionality for these filters is enabled.

Figure 11: Workspace and Analysis Menu List
The Analysis menu option can then be selected to open any type of analysis view required
such as Line, Bar, Grid or Table view.
The Voice/Data Summary report that can be viewed after applying a filter analyses and
classifies each call (WCDMA/GSM/GPRS/EDGE) indicating directly where problems have
occurred (call drops/setup failures/ Session/Data transfer failures etc) and where calls have
completed successfully. The report also provides key KPI for analysis which can be customised
by the user. The analysis can be done one both Layer 3 messaging and n Vendor specific
messaging and selecting an event allows the user to view the problem on the 2D view,
updating all replay windows as required enabling quick start on analysis of problems found.
The Data sessions can also be viewed in a similar manner and allows further information
about the call to be obtained e.g. durations, Session type, APN used, Throughputs etc.
Scanner measurements can also be analysed similarly.


Figure 12: Voice/Data Kips and Call Analysis Reporting and View
3.5.2 Drive Down Analysis, Display and Replay

RANOPT allows users to replay all measurement data in order for drill down analysis of the
drives to be done. This functionality enables the engineers to see the network from the
subscriber’s perspective and by employing a number of useful graphing details, analyse the
measurement data to optimise and fine tune the network performance. RANOPT additionally
allows the comparison of scanner and UE/TM measurement data with results obtained either
presented graphically or viewed on the 2D view. The replay functionality has full
synchronisation of windows enabling quick and easy problem analysis. Parameters for view
on any of the analysis modules are available via a central Parameter Selector window from
which for the GIS specifically, property attributes can be easily defined. Query Variables are
also used for specific selections and applying of thresholds on parameters.
The scanner replay functionality enables engineers to view all Pilots/BCCH-ARFCN detected
during the drive and resolve these to the cells ID’s and thus check and analyse the network on
handovers, pilot pollution, interference and neighbour plans.
The UE replay functionality additionally incorporates views for the Ec, Ec/Io for the Active,
Monitored and Detected Set scrambling code information, Rx Lev, Qual ( Full and Sub) for
BSIC-BCCH and line graphs across technologies. With the flexibility and configurability allowed
in RANOPT, additional parameters required for replay and detailed drill down analysis can be
via the parameter selector and easily viewed. Thus enabling easy assessment of inter-
technology analysis to be carried out. All relevant reports are also linked to the GIS and thus
synchronised with the analysis views as well.

Attributes tab: Allows colours and Query Variables tab: Allows editing
symbols styles editing of various parameter and threshold
settings
Figure 13: Parameter Selector and GIS Attributes and Query Variable Settings

Figure 14: Drill Down and Replay Analysis

Figure 15: GIS views
3.5.3 Network Message Analysis

The signalling/network message which allows for detailed analysis of Layer 3 and NAS
message information and decoding together MAC/RLC and LLC message support.
Filtering on specific network messages can be done and a unique list of all messages available
is provided by RANOPT for easy reference. Easy search for required messages can be done
and users can colour messages to highlight occurrences of these. The user is easily able to drill
down from a list of messages to view the decoded parameters. All filters in the workspace
are available for selection on the network messages window for quick display of L3 signalling
information
It is also possible to generate statistical reports that provide useful information and key
performance indicators on network messaging obtained.

Figure 16: Layer 3 Message Analysis Decoding
A similar view for vendor specific messaging is available where appropriate.
Figure 17: R&S Vendor Messaging
3.6 Reporting – Report Registry

The report registry is used to register all reporting modules and parameters across
technologies used in RANOPT and are stored in the database for all users to access. The
report registry thus lists all Excel reports (written in VBA and SQL) and parameters used for
display of data on the map, line, bar chart, grid and table analysis views.
With the configurability allowed in RANOPT, inclusion of additional analysis requirements (via
reports and analysis modules containing a preconfigured set of parameters) can be done as
easily as a plug and play module. The analysis module and parameters need only to be
imported into the Reports Registry. This avoids delays in downtimes as no upgrade of
software is required.

Once the report/parameter is created it can be associated with single or multiple types of
equipment and technology.
The parameters used for replay analysis (written in SQL) can be readily configured and
changed from within the report registry to customise for a particular operator’s
requirements.
RANOPT currently incorporates a full library of UMTS/HSPA/GSM/GPRS and EDGE reports and
customised reporting can be easily added by importing the required modules into the report
registry.
Figure 18: Report Registry - Excel Analysis Reports and Parameters
3.6.1 Excel Analysis Reports

A library of excel reports for a variety of analysis requirements across WCDMA/HSPA, GSM,
GPRS and EDGE is available in RANOPT. From Ec, Ec/Io, Ec vs. Ec/Io, Rx Lev, RxQual, Rx Lev
vs. Rx Qual, TA distribution to Messaging Events analysis, RRC message analysis, HO analysis
and Neighbour Analysis together with inter-technology HO and neighbour analysis. The
reporting includes distribution graphs allowing for analysis of signal strengths and
interference, drill down analysis reporting including call analysis and data analysis on Layer 3
and vendor messaging identifying required events. Setup time, call duration and throughput
analysis, time spent on different technologies, for example time on UMTS/ HSDPA. Further
neighbour analysis with suggestions and comparison to the planning DB can be provided.
Typical examples of reporting available is shown below

Figure19: RANOPT WCDMA, GSM/GPRS/EDGE Distribution, Events and KPIs

Figure 20: RANOPT Neighbour Analysis and Pilot Pollution/Poor Dominance Reports

Figure 21: RANOPT Trending Reports
All reports are defined and specified from experience gained from the AIRCOM consultancy
division and used on AIRCOM optimisation project activities across the globe. Custom reports
and KPI reports can also be readily generated as requested. All reports can also be used for
trending activities where applicable.
For most reports the results can be viewed on the GIS for visualisation of the analysis carried
out. Reports can also be setup to update the site DB if required. This for instance is the case
with the neighbour analyser report where results can be viewed with the planned
environment and the required neighbour definitions obtained via drive analysis done can be
selected for update on the planning DB and via a click of a button following confirmation from
the engineer, the neighbour relations on the planning DB will be updated.
Figure 22: Planned and Drive measurement based Neighbour View

Once an update is performed, a history of the changes made to the Planning DB is stored on
the neighbour analysis report for future reference.
A full list of available RANOPT reports can be provided on request. Please contact AIRCOM
support support@aircom.co.uk
3.7 Benchmarking
RANOPT allows for benchmarking various different types of scenarios including two or more
networks or services. Further the benchmarking feature can be adopted to run a before and
after analysis (separate delta analysis reports/views are also available in RANOPT).The
flexibility of the graphical and geographical graphing mechanism makes it possible to
benchmark on virtually any parameter. For example, compare voice or data call performance
for two or more networks or even coverage indicators (Ec and Ec/Io, Rx Lev, RX Qual) for
different operators. Benchmarking is also available for the Voice/Data Summary reports in
order to benchmark call statistics where required.
In addition to this, it is also possible to benchmark variable such as two different vendors
within the same network.
Figure 23: RANOPT Benchmarking Report Generation

Figure 24: RANOPT Benchmark Reporting
3.8 User Comment

User comments can also be added on to the 2D view again problem area and associated with
a Filter for easy information exchange across the organisation and for making self notes
during analysis work

Figure 25: User Comments
3.9 Scheduler
RANOPT also includes Scheduler for automation of activities done at regular periods or for
one off activities at a certain time. If configured and used correctly the Scheduler has the
capability to aid and automate the optimisation work flow processes allowing significant time
savings to be gained.
The scheduler has been significantly improved in V6.1 and can do a number of tasks that are
placed under Jobs for processing; further tasks are to be specified later. The following tasks
are now available
o File Loading
o Filter Creation (and Apply)
o Report Running

.
Figure 26: RANOPT Scheduled Jobs
Jobs are definitions are done with when and how often they will run and which RANOPT
database will be used:
Figure 27: Defining Jobs in RANOPT
3.9.1 File Loading Tasks
This task automatically loads selected drive test files into RANOPT.
The user can specify the source of the import files, and to which location they will be loaded
to in preparation for parsing/loading into RANOPT.

Figure 28: File loading Tasks Setup
In this example, files contained in the Drive Test Files folder on the C drive of the host
machine will be loaded into the RanoptImports folder from where they will be parsed
and loaded into RANOPT.
3.9.2 Filter Creation (and Apply)
This task automatically creates (and applies) new filters based on the files available in the
database.
It is possible to set the users own criteria for what will be included in the filter in the Filter
Criteria Wizard:
Figure 29: Filter Creation Task

Any available drive test file that matches the criteria defined will be included in the filter
when the task is run. It is possible to also include files from any file load tasks in the same job
that have been run prior to this.
3.9.3 Report Running Task
This task it is possible for users to create Report Running tasks, which automatically generate
selected reports for selected filters
It is possible to choose how the hierarchy of reports and filters is displayed - by filter or by
report. The report running task can be used for benchmark reports and for non benchmark
reports as well and has a number of user friendly settings to aid the user in creating multiples
reports required on demand
The user can also generate reports from the filters created in filter creation task within the
same job
The reports generated are saved to user specified location defined.
Figure 30: Report Running Task

3.10 Exporting Data

All 2D view arrays in RANOPT can be export into MapInfo format for display and view in other
tools supporting MapInfo layers. The data from the arrays is also exported thus allowing users
to manipulate the data points if required for other analysis activities such as coverage/traffic
analysis.
Filtered or binned data can be exported to CSV, XML, HTML or MS-Excel for additional
analysis or post processing.
Export is performed through the use of a Wizard.
The wizard criteria are based on the following:
Select data, columns and order to be exported
Layout and format
Preview of the information is provided before executing the export
4 ENTERPRISE Integration
RANOPT seamlessly integrates with all other modules within the ENTERPRISE tool suite thus
enabling all radio planning parameters (WCDMA, HSDPA, GSM, GPRS and EDGE) from
ASSET/3G etc to be viewed and analysed with drive survey data. Thus comparison of
measured vs. predicted data can be analysed. RANOPT analysis modules are also available to
provide differences in signal strength seen at measured points.
Drive data from RANOPT can also be used for CW (Signia) file generation for module tuning
activities within ASSET/£G. Thus propagation model improvements, for improved predictions
and coverage analysis can be done. The ASSET/3G predictions, together with the interference
matrices generated can be fed into ILSA, The Enterprise AFP for frequency planning activities.

Figure 31: Measured vs. Predicted Data Analysis
RANOPT analysis reports can also be configured where appropriate to interface with the
Planning DB for automatic update of relevant information e.g. neighbour definitions.
Figure 32: Neighbour Relation Updates to Planning DB
All other modules can also be interfaced to for required investigation and analysis as
indicated below.

View network performance management data (OPTIMA)

Analyse and optimise network design (ADVANTAGE)
Implement network Configuration changes (DATASAFE)
Physical network changes (roll out and rigging teams)
5 Different RANOPT Product Versions

RANOPT is now available as three different products:
5.1 RANOPT Server (Server Version)

RANOPT Server is a multiple user project environment where all drive test files are continuously
loaded and managed in a centralised data warehouse for benchmark reporting, replay and
optimisation analysis. There are no restrictions on file load on this version.
RANOPT Server has the following features:

- Full GSM/GPRS/EDGE/UMTS/HSPA and DVB-H Optimisation Analysis functionality.
- Un-restricted file load (restriction only based on Oracle DB limitations)
- Graphical and Geographic display and replay.
- Layer 3 decode and analysis.
- Full library of reports for all technologies supported.
- RANOPT Server Scheduler - Automated Filtering, Batch Reporting etc.
- Trouble shooting module - suggested cause and highlight action to take (development
progressing).
- Automatic Reporting tool - GIS bitmap/jpeg creation - ( on road map).
Important: RANOPT Server requires Oracle Enterprise Edition with Partitioning and Spatial
component
5.2 RANOPT Standard (Standalone user license)

RANOPT Standard allows individual or standalone project users that require full optimisation
analysis functionality. The users are able to load up to 35 files and create 35 filters (if
partitioning is available – Oracle Personal/Enterprise) or only 10 drive files and create 5 filters
(if no partitioning - Oracle Standard) on a standalone machine at any one time for replay and
detailed optimisation analysis.
RANOPT Standard has the following features:

- Full GSM/GPRS/EDGE/UMTS/HSPA and DVB-H Optimisation Analysis functionality.
- Ability to load 35 log files for simultaneous review.
- Quick purge of data for further loading of files is available.
- Graphical and Geographic display and replay.
Layer 3 decode and analysis.
Full library of reports for all technologies supported.
Important: RANOPT Standard requires Oracle Standard as a minimum. Oracle
Personal/Enterprise Edition can be used. Oracle Spatial component (available on Oracle
Personal/ Enterprise) is required if measurement binning capability is required

5.3 RANOPT Lite (ASSET3G drive test module)

RANOPT Lite is a drive file import and replay module for planning tool. It is used for radio
planners to review signal strength and measurement quality comparisons with prediction
results in ASSET3G radio planning module. Users are able to load 10 files and create 5 filters.
RANOPT Lite has the following features:

- Limited analysis functionality restricted to file display and replay only.
- Ability to load up to 10 log files for simultaneous view.
- Quick purge of data for further loading of files is available.
- GSM/GPRS/EDGE/UMTS/HSDPA and DVB-H layer 1 graphical display and replay.
- Layer 3 decode and analysis is not available.
- Reports are not available.
Important: RANOPT Lite requires Oracle Standard as a minimum. Oracle Personal/Enterprise
Edition can also be used (file load limit remains the same). Oracle Spatial component (available
on Oracle Personal/Enterprise) is required if measurement binning capability is required
Note: All versions of the RANOPT product support all technologies currently supported. These
technologies are now licensed separately.
6 RANOPT Physical Architecture: Windows Client-Server System

Under normal conditions, the RANOPT database server will collect a large volume of data.
While new data is being loaded into the database, it is possible for multiple users to analyse
the data already present. Different users can access the same data, filters and reports. The
normal RANOPT deployment will be as follows:
Collected Drive
Test Files File Loader
RANOPT Server
and Database
RANOPT
Workstation(s)
Figure 33: RANOPT Physical Architecture
6.1 Software Requirements

Prior to installing RANOPT, there is Third Party software that must be installed. This
software is listed in the table below:

Software Supported Versions Software Modules

Oracle Client 10g Oracle SQL*Net
Oracle Call Interface (OCI)
Oracle Objects For OLE
Oracle ODBC
Microsoft Office 2000 Excel

2003
XP
6.2 IT hardware Requirements

It is recommended that you set up your hardware according to the requirements listed in
the table below for small standard installations:
Server Requirements
DATABASE OS Supported: UNIX, Windows 2000, Windows XP,Windows
Server 2003 Server
Memory Minimum: 1GB

Recommended: 2GB
HDD Disk space required is calculated using the algorithm

provided in the 'Database Growth' section lower down in
this document.
Processors Minimum: 1 CPU * 1.8 GHz

Recommended: 2 CPUs * 2.0 GHz
LOADER/PARSER OS Supported: Windows 2000, Windows XP, Windows 2003

Machine Server
Memory Minimum: 1GBMB

Recommended: 2GB
HDD Minimum: 20GB
Recommended: 80MB
Note: The loader keeps a copy of the results file, after
loaded into the database. Although this may be removed or
archived, it is recommended that the loader machine has
capacity for at least a month's worth of result files.
Processors Recommended: 1 CPU * 2.0GHz
CLIENT OS Supported: Windows 2000, Windows XP
Memory Minimum: 512MB

Recommended: 1GB
HDD Minimum: 300MB
Recommended: 500MB
Processors Recommended: 1 CPU * 2.0GHz

For larger centralized installations, the HW requirements will need to specified on a per
case basis
7 Conclusion
RANOPT has been designed to be a fast and flexible measurement based analysis tool
addressing operator’s requirements on effectively analysing and optimising the radio
network plan and making required quality assessments for services provided. A powerful
common oracle database backend enables data transparency and warehousing allowing
users to filter, diagnose and fault-find problems with ease. The unlimited flexible
reporting and analysis capability enables RANOPT to be geared to specific operator’s
optimisation needs. The scheduling module allows unparalleled flexibility and automation
of workflow processes to effectively aid engineer’s day to day activities. In addition,
RANOPT integration with the Enterprise tool suite offers operator’s a powerful, flexible,
user friendly solution addressing the organisations planning and optimisation tool
requirements.
Copyright 2006 AIRCOM International - All rights reserved. No part of this work, which is protected by copyright, may be reproduced in
any form or by any means - graphic, electronic or mechanical, including photocopying, recording, taping or storage in an information
retrieval system – without the written permission of the copyright owner.

RANOPT Technical Overview PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RANOPT Technical Overview PDF

Uploaded by

Copyright:

Available Formats

Technical Overview

RANOPT Technical Overview

Author: AIRCOM InternationalAIRCOM International

Sec. Class: Commercial in Confidence

Author: AIRCOM International RANOPT Technical Overview Page 3 of 42

Author: AIRCOM International RANOPT Technical Overview Page 4 of 42

Author: AIRCOM International RANOPT Technical Overview Page 5 of 42

RANOPT within the Optimisation Analysis Process

Figure 1: RANOPT in the optimisation cycle

Author: AIRCOM International RANOPT Technical Overview Page 6 of 42

Version 6.1 Highlights

1. . 40% increase in speed of TEMS loading on V6.1

2. 50% less time spent on optimisation setup tasks

2.1 Why RANOPT? - Key Benefits of RANOPT

Author: AIRCOM International RANOPT Technical Overview Page 7 of 42

Author: AIRCOM International RANOPT Technical Overview Page 8 of 42

Figure 2: RANOPT Architecture

Author: AIRCOM International RANOPT Technical Overview Page 9 of 42

Author: AIRCOM International RANOPT Technical Overview Page 10 of 42

Figure 3b: RANOPT Administrator - Configuring Networks

3.1.2 Data Load

Author: AIRCOM International RANOPT Technical Overview Page 11 of 42

Figure 4: File Loading

3.2 Database Explorer

Author: AIRCOM International RANOPT Technical Overview Page 12 of 42

Figure 5: Database Explorer

3.3 Filtering – Filter Manager and Data View

Further optional manipulation of the filter can done via

Author: AIRCOM International RANOPT Technical Overview Page 13 of 42

Figure 6: RANOPT Filter Manager and Filtering Creation Module

Figure 7: filter creation options

Author: AIRCOM International RANOPT Technical Overview Page 14 of 42

Choosing different types of filter

Merge All Files Filter

Merge Devices Filter

Example of measurement files

Figure 8: Merge Device Option Filter creation

Example of filters created using the Merge Devices option

Author: AIRCOM International RANOPT Technical Overview Page 15 of 42

3.3.1 Data Manipulation

3.3.2 Cell Snapshots

Figure 9: Cell Snapshots

Author: AIRCOM International RANOPT Technical Overview Page 16 of 42

3.4 Resolving Cells to Drive Files

3.4.1 Resolving cell sites for UMTS drive-test data

Author: AIRCOM International RANOPT Technical Overview Page 17 of 42

Resolve by CI/MCC/MNC and distance

Resolve by CI/UARFCN and distance

Resolve by SC/UARFCN and distance

Figure 10: Resolving cell sites for UMTS drive-test data.

Author: AIRCOM International RANOPT Technical Overview Page 18 of 42

3.4.2 Resolving cell sites for GSM drive-test data

Resolve by CI/MCC/MNC and distance

Resolve by CI/BCCH and distance

Resolve by BCCH/BSIC and distance

Figure 10: Resolving cell sites for GSM drive-test data.

Author: AIRCOM International RANOPT Technical Overview Page 19 of 42

3.4.3 Propagating missing UMTS parameters

3.4.4 Propagating missing GSM parameters

3.5 Workspace, Replay and Data View

3.5.1 Work space

Author: AIRCOM International RANOPT Technical Overview Page 20 of 42

Figure 11: Workspace and Analysis Menu List