Gladiator StartUp Tocustomer

G StationG StationStartup Training

Module objective

• Understand the power of Gladiator solution based on its open architecture philosophy

• Step 1 - Loading data into Gladiator• Step 2 – Coverage Analysis• Step 3 – Quality Analysis• Step 4 – Neighbor Analysis

Start up

• Step 4 – Neighbor Analysis• Step 5 – Event Analysis• Step 6 – Reports

• Loading data into Gladiator– File converter and file conversion,

explanation of gladiator state machine– Standard versus interface specific

Start up – Step 1

– Standard versus interface specific frames

– System data and Vectors– Merging files

Types of project data

The Gladiator Project View

� Project – highest level of data organization

� Provides view of all data uploaded to Gladiator project

� A data base is created for each individual project and each project has a separate folder in Gladiator’s file structure

Gladiator Essentials 8 June 2010

� Used to group and organize data necessary for all post processing tasks

� Measured data (data base) – Organized the structure (File – Device – Table)

� Vector data - Support for MapInfo overlays

� Workspaces

� System view – Network configuration

Note: By default Project view is docked to the upper left corner of Gladiator’s main window

Case – File Converter

• What is File Converter?• What does it do? • Basic setting Vs. Advance settings.• What is conversion Plan?• What is conversion Plan?• What is compression plan?

Converting Measurement Data

Select the measured data files to be converted

Define the Project to upload the measured data

Start the conversion

to be converted

Project view – Systems Node

Provides easy way to display System(s)

Available Systems are shown in project view

Ability to import .gsf txt files or excel files

Ability to create a new systemAbility to create a new system

Supported Technologies:

GSM/GPRS/EDGE

UMTS

Note: More detail information about loading cell site information will be further presented

Project view – Vector Data Node

Displays all vectors loaded in the Project

Organize the Vectors with folders and subfolders

To load files into the vector node:

Right click on the Vector data node and select Import

Using File � Import � Vector data

Gladiator standard frames

• Gladiator groups the data in two types of frames (i.e. tables)– Equipment specific frames– Standard frames

• Standard frames

Standard frames

• Standard frames– Created by Gladiator – Contain the same data for all

measurement equipment– Contain the most important data– Used for different UMTS toolbox

analyses– UMTS phones create both GSM

and UMTS standard frames

Frames specific to equipmentNote: Standard frame name starts with G_

• Running Coverage Analysis– Define Workspace concept– Demonstrate the results of the Toolbox

analysis for Phone and Scanner

Start up – Step 2

analysis for Phone and Scanner– Usage of “Cell Data” feature– Usage of “Cell Coverage” feature– Usage of “Cell Trace” feature

Workspace Views

• Analysis Results of tool boxes

• Analysis Results of tool boxes

• Four views– Table view – Map view– Graph view– Replay

view

Gladiator views

• Used to present the data

• Feature various data analysis capabilities

Map View - Overview

• Parts of a map view� Map toolbar � Map display� Layer control� Legend� Overview map� Status Bar

• Map view displays� Measured data� Measured data� Cell sites� Vectors

• Map is synchronized to other views

• There can be multiple maps in a workspace

Gladiator map supports standard mapping tools: zoom in, zoom

out, pan, distance, annotations,…

Data is placed on the map through simple drag-n-drop

Cell data node

How to display other system-related data on the map?

Use Point data

� Drag-n-drop the table onto the Point data node in Layer control

� Properties are similar to system layers

Cell data node

The system can be display using a display scheme for any column of the point data table

Cell data node

Table example

Cell Name PSC Interference Poor Downlink Poor Uplink

GAATU00729 324 0 12 0GAATU00729 324 0 12 0

GAATU40029 292 0 0 0

GAATU40648 388 3 4 0

GAATU40917 148 1 22 0

Cell Coverage

• Using GSM Cell coverage• Drag-n-drop the desired

"G_GSMLayer1" table from the workspace to GSM �Cell coverage in Layer controlcontrol

• Select the desired measurement from the GSM Cell coverage analysis menu

• Select a cell to view its coverage data

Cell Coverage

• Customizing GSM cell coverage• Schemes

• RxLev• RxQual• TxPower• C/I• C/I• FER

Cell Trace Analysis

�Complementary to the cell coverage feature

�Helps to identify overshooting cell

20

• Running Quality Analysis– Demonstrate the results of the Toolbox

analysis for Phone– Usage of “Replay” feature

Start up – Step 3

– Usage of “Replay” feature– Usage of “Display Scheme” feature– Usage of “Co-channel” feature– Usage of “Star Mode” feature

Map View – Replay Tool

Setting up the Replay tool1. Click on the Replay tool button2. Select a point in the map3. Open a Replay view4. Select the File and Device

Replaying data on the map 1

35

4. Select the File and Device5. Press Play in the Replay tool

2 4

Replay Tool

• The Replay View�Select File�Select Device

• Possible to open multiple

Replay Views

• Possible to open multiple views and replay them simultaneously for different devices

• Possible to create and design custom Replay views

Display Scheme

Defined Schemes

� To create or open an existing Scheme, select Edit �Display schemes

� Configure a new scheme by clicking on the Add button

� Select an existing scheme and click on Edit to and click on Edit to reconfigure it

Display Scheme

� Ability to create discrete values or dynamic ranges

� Discrete values may be numeric or text

� Ability to generate up to 600 ranges

� Dynamic range generator� Dynamic color generator:

Scheme Options

� Dynamic color generator: gradient or random

� Ability to select large variety of symbols

Map View – Channel/Code

How to identify co- and adjacent channels on the map?

Use Channel/code mode

Map View – Star Mode

How to identify serving cell and neighbors on the map?

• Running Neighbor Analysis– Demonstrate the results of the Toolbox

analysis for Scanner– Usage of “Neighbor Data” feature

Start up – Step 4

– Usage of “Neighbor Data” feature

Neighbor data node

• Displays data for cell relations (such as neighbors)

• To use neighbor data• Drag-n-drop the table

onto the Neighbor data node in Layer control

• Configure neighbor • Configure neighbor mode

• Enable Neighbor mode in the toolbar

• Incoming or Outgoing

Neighbor data node

• Configuring neighbor data• Cell scheme or Arrows• Cell scheme or Arrows• Source and Neighbor

• Cell identification• Name, LAC-Cell ID,

Cell ID• Labels

Neighbor data node

• Table example

Server ID Server PSC Missing Neighbor ID Missing Neighbor PSC Bin Count

GAATU00817 316 GAATU40098 304 3

GAATU00817 316 GAATU03779 226 1GAATU00817 316 GAATU03779 226 1

GAATU04108 178 GAATU40039 452 1

GAATU04108 178 GAATU40038 244 1

• Running Event Analysis– Demonstrate the results of the Toolbox

analysis for Phone– Gladiator “State Machine” for call

Start up – Step 5

– Gladiator “State Machine” for call classification

– Usage of “G_Layer3”

Table View - Message decoder

• Decodes Layer 3 messages

• Technologies: �GSM/GPRS/EDGE�UMTS

Decoded message view

• Running Reports– Demonstrate the results of the Toolbox

analysis for Phone and Scanner– KPI’s

Start up – Step 6

– KPI’s

TOOL BOX INTRODUCTION

Overview

• Technology Toolbox� Set of tools for voice and data analysis� Contains RF, Handover, Call performance, Error, and Data

Throughput and Application analyses, etc� Each analysis generates a comprehensive report or map

•Gladiator Essentials

•

Running an analysis

• To execute an analysis from the Analysis Toolbox� Select Analysis � Toolbox ( or just press F5)� Select a Toolbox and a Function to execute

•

Analysis types

• Naming scheme�Technology: C – CDMA,E – EVDO, G – GSM, I –

iDEN, T – TDMA, U – UMTS�Analysis type: A – Area, E – Event, R – Report�Data type: P – Phone, S – Scanner

•

�Data type: P – Phone, S – Scanner• Area analyses

�Visualize data and identify problem areas• Event analyses

�Visualize voice and data call events• Reports

�Generate data statistics and event-based analyses

Content of GSM toolbox

• Three types of analysis– Area (coverage, interference,

missing neighbor)• Occur over larger area• Work with binned data

– Event (block call, dropped call,

Analysis in the GSM/UMTS toolbox

GSM/UMTS Tool BOX

•Gladiator Toolbox

•

– Event (block call, dropped call, handoff)

• Examine various events during the call

– Reports (various KPI stats)• Summarize overall stats for

the drive

Overview of the six step process

• Steps 1-3 RF optimization– Scanner / Phone

• Steps 1-4 RAN Optimization– Phone / Data device / Scanner

• Step 5 RAN troubleshooting– Phone / OSS (MRR, NCS and Call trace)– Measurement probes

Step 1: Coverage

Step 2: Quality

Step 3: Neighbor list

•GSM optimization

•

– Measurement probes• Step 6 Reporting

– Drive test / OSS / Probes dataStep 4: Events

Step 5: Troubleshooting / Fine tuning

Step 6: KPI Reports

Note: In GSM network optimization –various measured data sources used

Step 1: Coverage problems

• Coverage – area problem• In GSM

– Many different analysis of coverage – Dedicated to Network Rollout, Network

expansion and continuous optimization process

• Scanner is preferred

•GSM optimization

•

• Scanner is preferred– external antenna– no vehicle loss

• Phone measurements– Less repeatable than scanner– Dependent on vehicle losses

GAP_Coverage

• Phone based coverage analysis• Identifies: poor UL, poor DL, UL interference, DL interference• Data is geographically binned• Analysis parameters:

– RxLev interference threshold (dBm) - default value: -80– ER interference threshold - default value: 4– Poor RxLev threshold (dBm) - default value: -95

•GSM optimization

•

– High Tx Power threshold (dBm) - default value: 20– Tx Power interference threshold (dBm) - default value: 6

• Analysis produces (for each phone device)– Map with coverage plots (DL&UL coverage, DL&UL interference)– Map with point data indicating problematic cells– Results tables (with map data and summary)

GAP_Coverage

• Poor DL criterion– Poor Downlink' indicates there is low RxLev.– RxLev < Poor RxLev threshold (dBm)

• Poor UL criterion– 'Poor Uplink' indicates there is high Tx Power.– Tx Power (dBm) > High Tx Power threshold (dBm)

• DL Interference criterion– 'DL Interference' indicates there is high ER and high RxLev.– RxLev > RxLev interference threshold (dBm) AND ER > ER interference

threshold

•GSM optimization

•

– RxLev > RxLev interference threshold (dBm) AND ER > ER interference threshold

• UL Interference criterion– 'UL Interference' indicates there is high Tx Power and high RxLev.– RxLev > RxLev interference threshold (dBm) AND Tx Power (dBm) > Tx

Power interference threshold (dBm)Interference criterion

• RxLev notes: RxLev (sub)(dBm) is used by default. If it is null, then RxLev (full)(dBm) is used.• ER notes: FER is used when Hopping Flag = 1. If Hopping Flag = 0, then RxQual (sub) is used;

however, if RxQual (sub) is null, then RxQual (full) is used instead. RxQual values are converted to BER.

Step 2: Quality

• Interference (Quality) – area problem• In GSM

– Quality– Serving Cell Statistics

• Determined using phone only

•GSM optimization

•

GAP_Quality

• Phone based coverage analysis• Identifies: too many servers, non-dominance and

excessive interference• Data is geographically binned• Analysis parameters:

– ER threshold - default value: 4

•GSM optimization

•

– ER threshold - default value: 4

• Analysis produces (for each phone device)– Map with interference classification– Map with point data indicating problematic cells– Results tables (with map data and summary)

Step3: Missing neighbor

• Missing neighbor – area problem• In GSM – missing neighbor

creates coverage issues and interference issues

• Gladiator uses either scanner or phone/scanner

•GSM optimization

•

• phone/scanner is preferred – Scanner records all BCCH

signals– Phone is limited by existing

neighbor list

GAS_MissingNeighbor• Scanner based missing neighbor • Identifies: missing neighbor relationships• Analysis based on the binned drive test data and existing system

neighbor list• Input of phone and scanner information.• It uses system neighbor list, phone serving cell and scanner signal level• Analysis parameters:

– Relative RSL threshold (dB) - default value: 6– Significant MN threshold (bins) - default value: 5

•GSM optimization

•

– Significant MN threshold (bins) - default value: 5– Top missing neighbor count - default value: 5– Report up to N missing neighbors - default value: 10

• Analysis produces (for each scanner device)– Map with missing neighbor count– Map with point data indicating problematic cells– Results tables (with map data and summary)

Step3: Missing neighbor

• Missing neighbor – area problem• In GSM – missing neighbor

creates coverage issues and interference issues

• Gladiator uses either scanner or phone/scanner

•GSM optimization

•

• phone/scanner is preferred – Scanner records all BCCH

signals– Phone is limited by existing

neighbor list

GAS_MissingNeighbor

• Scanner based missing neighbor • Identifies: missing neighbor relationships• Analysis based on the binned drive test data and existing system

neighbor list• Input of phone and scanner information.• It uses system neighbor list, phone serving cell and scanner signal level• Analysis parameters:

– Relative RSL threshold (dB) - default value: 6– Significant MN threshold (bins) - default value: 5

•GSM optimization

•

– Significant MN threshold (bins) - default value: 5– Top missing neighbor count - default value: 5– Report up to N missing neighbors - default value: 10

• Analysis produces (for each scanner device)– Map with missing neighbor count– Map with point data indicating problematic cells– Results tables (with map data and summary)

Step 4: Events

• Analyses various events during the call

• The same analysis accommodates both voice and data

• Performed using phone device (either voice or data)

Gladiator event analyses

GAP_Event

GAP_Handover

•GSM optimization

•

(either voice or data)• The events analysis is based on

G_Layer3 frame• Events are presented on the map • Map is linked to appropriate layer

3 table

GAP_Events

• Phone based analysis• Identifies all call processing events • Creates maps with events, call ID and Ec/Io for the call

• Some tracked events– Call attempt

• Some tracked eventso Normal termination

•GSM optimization

•

– Call attempt– Call attempt retry– Access failure– Setup failure– Dropped call– No connection– No comm

o Normal terminationo iRAT handoverso Various types of handoverso TMSI reallocationo Dropped callo PDP context activationo PDP context activation failure

Voice call events - output

events

one call ID

found events

•GSM optimization

•

Note: only found events are included on the map

Link between map and layer 3

explanation

event on the map

associated message

events

•GSM optimization

•

Note: Map and layer 3 table are synchronized

Importing Ericsson OSS files

The following Ericsson OSS file types are supported:� GSM MRR (*.msmt & *.conf)� GSM NCS (*.msmt & *.conf)� UMTS MRR (*.txt)� UMTS NCS (*.msmt & *.conf)

•Gladiator Essentials

•

� UMTS UETR, CTR, and GPEH (*.tab)

GSM – OSS NCS Missing Neighbor

• The colors indicates which cells are missing the target serving cell and the percentage of samples the serving cell is reported as number one cells in the MRR

•Serving cell acting as a missing neighbor

in the MRR (neighbor measurement report)

• The cyan could be discard as missing since its percentage is below 0.25%, all the others could have the target serving cell added to their neighbor list

GSM – OSS Traffic Analysis

•56

UMTS OSS Toolbox CTR sample

• UMTS_MR Stats from CTR files

•Gladiator –QualiTest

• This analysis helps to optimize the UMTS neighbor list on a specific cell based on measurements results reported by all mobiles

UMTS OSS Toolbox MRR sample

• UMTS_MRR Stats

•Gladiator –QualiTest

• This analysis helps to optimize the UMTS worst KPI offenders over all monitored cells.

• Ex: BLER, Ec/Io, RSCP, TxPower for UL and DL

Step 6: Reports and KPI’s• GSM toolbox - 6 different reports• Analyze drive as a whole• In CDC relevant KPIs can be built

on the fly

•GSM optimization

•

•Support Contact Details•[email protected]•[email protected]• +91 80 4114 2121 (Sudheendra Gururaj)

Gladiator StartUp Tocustomer

Documents

Transcript of Gladiator StartUp Tocustomer