CovMo User Guide

CovMo System User Guide
Groundhog Technologies Inc. Confidential
CovMo User Guide
Geo-locating Network Traffic and Events

with Subscriber-Based Intelligence
Release for Telkomsel, May 2019
COPYRIGHT INFORMATION
Copyright © 2002-2018 Groundhog Technologies Inc. All rights reserved. This manual may not be
copied, photocopied, reproduced, translated, or converted to any electronic or machine-readable
form in whole or in part without prior written approval of Groundhog Technologies Inc.
Groundhog Technologies is expanding its global business network and forming alliance with companies in different
countries.
United States (Headquarters)

One Broadway, 14th Floor, Cambridge, MA 02142, USA
Tel: +1 617 4751580
Fax: +1 617 4013621
E-mail: gtcontact@ghtinc.com
United States (West Coast)

15620 Kavin Lane, Los Gatos, CA 95030, USA
Tel: +1 408 3951188
Fax: +1 408 3955132
E-mail: uswcontact@ghtinc.com
Japan
No.22, 2-1-78, Yato-cho, Nishitokyo City, Tokyo 188-0001, Japan
Tel: +81 42 427-6740
Fax: +81 42 453-0275
E-mail: nhcontact@ghtinc.com
Italy
Via G. D'Arezzo, 4 20145 Milan, Italy
Tel: +39 0248559407
Fax: +39 024694998
E-mail: itcontact@ghtinc.com
Taiwan
9F, No.35 Bo’ai Road, Zhong Zheng Dist., Taipei 10044, Taiwan
Tel: +886 2 83691018
Fax: +886 2 83692368
E-mail: contacttw@ghtinc.com
China
Rm.5A28 Zhonghe Building No.159 QingChun Rd. HangZhou City,Zhejiang Province 310003 P.R.China
Tel: +86 571 8724-8773
Fax: +86 571 8724-8773
E-mail: contactcn@ghtinc.com
Information for all Groundhog Technologies Solutions is located at: Error! Hyperlink reference not valid.
CovMo User Guide Page 2

Table of Contents
1 ABOUT THIS GUIDE ..................................................................................................................................... 10
1.1 CHAPTER OVERVIEW ........................................................................................................................................ 10

1.2 AUDIENCE ...................................................................................................................................................... 11
1.3 LEARNING OBJECTIVE ....................................................................................................................................... 11
1.4 ABOUT THE USER GUIDE .................................................................................................................................... 12
2 INTRODUCING COVMO SYSTEM .................................................................................................................. 13

2.1 WELCOME TO COVMO SYSTEM .......................................................................................................................... 13
2.2 BENEFIT & ADVANTAGES OF GEO LOCATION SYSTEM .............................................................................................. 14
2.3 HOW COVMO SYSTEM WORKS ........................................................................................................................... 15
2.4 SYSTEM ARCHITECTURE AND DATA SOURCES.......................................................................................................... 15
2.4.1 System architecture ............................................................................................................................ 16
2.4.2 Source data details.............................................................................................................................. 17
3 GETTING STARTED WITH COVMO SYSTEM .................................................................................................. 19
3.1 LOGGING IN .................................................................................................................................................... 19

3.2 PLOTTING DATA............................................................................................................................................... 20
3.2 UNDERSTANDING MAJOR COMPONENTS............................................................................................................... 21
3.2 COLLAPSIBLE MENU OF TABS .............................................................................................................................. 23
4 NAVIGATING COVMO SYSTEM .................................................................................................................... 27
4.1 USER INTERFACE OVERVIEW .............................................................................................................................. 27

4.1.1 User interface default view ................................................................................................................. 28
4.1.2 User interface two panels view ........................................................................................................... 29
4.1.3 User interface only Map view ............................................................................................................. 30
4.2 CONTROL PANEL DETAILS.................................................................................................................................. 32
4.2.1 Panels within control view .................................................................................................................. 32
4.3 MAP VIEW ..................................................................................................................................................... 39
4.3.1 Map View ............................................................................................................................................ 39
4.3.2 KPI visibility control ............................................................................................................................. 42
4.3.3 Network Symbol and cell labels .......................................................................................................... 42
4.3.5 Location based KPIs............................................................................................................................. 45
4.3.6 User Polygon creation ......................................................................................................................... 47
4.3.7 Using Multi-Map View tab .................................................................................................................. 51
4.3.7 Map Graphics & Legends .................................................................................................................... 53
4.3.8 Heat Map/tiles export ......................................................................................................................... 54
4.4 PROPERTIES PANEL........................................................................................................................................... 56
4.4.1 KPI tab ................................................................................................................................................. 57
4.4.2 Chart tab ............................................................................................................................................. 58
4.4.3 Property tab ........................................................................................................................................ 59
4.4.3.1 – Viewing cell property..................................................................................................................... 61
4.4.3.2 – Viewing tile property ..................................................................................................................... 61
4.4.3.3 – Viewing PU property ..................................................................................................................... 62
4.5 REPORT VIEW ................................................................................................................................................. 63
4.5.1 Sorting data by column ....................................................................................................................... 64

4.5.2 Showing or hiding columns ................................................................................................................. 64
4.5.3 Report filters ....................................................................................................................................... 65
4.5.4 Reports drill down ............................................................................................................................... 65
4.5.5 Filtering protocol filter and causes ...................................................................................................... 69
5 COVMO SYSTEM KPIS ................................................................................................................................ 131
5.1 UMTS KPIS ................................................................................................................................................. 131

5.2 LTE KPIS ..................................................................................................................................................... 132
6 USER ROLES .............................................................................................................................................. 134
7. USE CASES ................................................................................................................................................ 135
1 USE CASE: INTRODUCTION .................................................................................................................. 135
2 USE CASE: COVERAGE ISSUE ................................................................................................................ 137
2.1 PROBLEM ..................................................................................................................................................... 137

2.2 ANALYSIS ..................................................................................................................................................... 137
2.3 RECOMMENDED SOLUTION ............................................................................................................................. 139
3 USE CASE: HIGHWAY RAILWAY ANALYSIS............................................................................................ 140
3.1 PROBLEM ..................................................................................................................................................... 140

3.2 ANALYSIS ..................................................................................................................................................... 140
4 USE CASE: SERVICE ANALYSIS VOLTE ................................................................................................... 142
4.1 PROBLEM ..................................................................................................................................................... 142

4.2 ANALYSIS ..................................................................................................................................................... 142
5 USE CASE: SUBSCRIBER KQI ANALYSIS ................................................................................................. 144
5.1 PROBLEM ..................................................................................................................................................... 144

5.2 ANALYSIS ..................................................................................................................................................... 144
6 USE CASE: GEO LOCATION CONTEXT ANALYSIS ................................................................................... 146
6.1 PROBLEM ............................................................................................................................................. 146

6.2 ANALYSIS .............................................................................................................................................. 146
7. USE CASE: CALL DROP AND DRILL DOWN ANALYSIS ............................................................................ 148
7.1 PROBLEM ..................................................................................................................................................... 148

7.2 ANALYSIS ..................................................................................................................................................... 148
8. USE CASE: IRAT ANALYSIS .................................................................................................................... 150
8.1 PROBLEM ..................................................................................................................................................... 150

8.2 ANALYSIS ..................................................................................................................................................... 150
9. USE CASE: TIME DOMAIN ANALYSIS .................................................................................................... 152

9.1 PROBLEM ..................................................................................................................................................... 152
9.2 ANALYSIS .............................................................................................................................................. 152
10. USE CASE: UE CAPABILITY MAP ....................................................................................................... 153
10.1 PROBLEM ............................................................................................................................................. 153
10.3 RECOMMENDED SOLUTION ........................................................................................................................... 155
11. USE CASE: USER THROUGHPUT MAP ............................................................................................... 156
11.1 PROBLEM................................................................................................................................................... 156

11.2 ANALYSIS ................................................................................................................................................... 156
12. USE CASE: SIGNAL QUALITY MAP .................................................................................................... 158
12.1 PROBLEM................................................................................................................................................... 158

12.2 ANALYSIS ................................................................................................................................................... 158
13. USE CASE: SIGNAL LEVEL MAP ......................................................................................................... 159
13.1 PROBLEM................................................................................................................................................... 159

13.2 ANALYSIS ................................................................................................................................................... 159
14. USE CASE: DATA IMPORT/EXPORT .................................................................................................. 160
14.1 EXPORT API .......................................................................................................................................... 160

EXPORTING DATA TO 3RD PARTY VIA CSV EXPORT OR JSON OBJECT. .............................................................................. 160
14.2 RESULTS ............................................................................................................................................... 161
14.3 DATA IMPORT........................................................................................................................................ 161
15. USE CASE: API INTERFACE TO EXPORT GRID NETWORK/SUBSCRIBER PROFILE ................................ 163
15.1 MAP DATA EXPORT ................................................................................................................................ 163

15.2 RESULTS .................................................................................................................................................... 164
16. USE CASE: STANDARD TROUBLE SHOOTING BY GEOLOCATION TOOL ............................................. 165
16.1 PROBLEM ............................................................................................................................................. 165
16.2 ANALYSIS ................................................................................................................................................... 165

17. USE CASE: IDENTIFY INTERFERENCE LOCATION ............................................................................... 168
17.1 PROBLEM................................................................................................................................................... 168

17.2 ANALYSIS ................................................................................................................................................... 168
18. USE CASE: IDENTIFY SWAP FEEDER.................................................................................................. 169
18.1 PROBLEM................................................................................................................................................... 169

18.2 ANALYSIS ................................................................................................................................................... 169
19. USE CASE: IDENTIFY DRAGGING-LATE HO ........................................................................................ 170
19.1 PROBLEM ............................................................................................................................................. 170

19.2 ANALYSIS .............................................................................................................................................. 170
19.3 RECOMMENDED SOLUTION ...................................................................................................................... 170

20 USE CASE: IDENTIFY MISSING NEIGHBORS AND UNNECESSARY NEIGHBOR RECOMMENDATION ........ 171
20.1 PROBLEM ............................................................................................................................................. 171

20.2 ANALYSIS ................................................................................................................................................... 171
20.2 RECOMMENDED SOLUTION ...................................................................................................................... 172
20.3 IMPLEMENTATION .................................................................................................................................. 172
21 USE CASE: HOT SPOT IDENTIFICATION (POTENTIAL TRAFFIC/PAYLOAD AND POTENTIAL REVENUE) ... 173
21.1 PROBLEM................................................................................................................................................... 173

21.2 ANALYSIS ................................................................................................................................................... 173
22 USE CASE: NETWORK PROFILING (TRAFFIC, PAYLOAD, THROUGHPUT, BADSPOT, UTILIZATION, ETC) PER
USER, PER BTS AND PER GRID ...................................................................................................................... 176
22.1 PROBLEM................................................................................................................................................... 176

22.2 ANALYSIS ................................................................................................................................................... 176
23 USE CASE: DEVICE PROFILING & SUBSCRIBER MOVEMENT (IMEI/IMSI) ............................................... 179
23.1 PROBLEM................................................................................................................................................... 179

23.2 ANALYSIS ................................................................................................................................................... 179

Figures
Figure 1 System Hardware Architecture ............................................................................................... 17

Figure 2 CovMo Client Login Screen ..................................................................................................... 19
Figure 3 CovMo Client Start page ......................................................................................................... 20
Figure 4 CovMo Client RSCP KPI applied ............................................................................................... 21
Figure 5 CovMo Work-Space ................................................................................................................ 22
Figure 6 Cell Property............................................................................................................................ 25
Figure 7 Tile Property ............................................................................................................................ 26
Figure 8 Workspace Menu .................................................................................................................... 28
Figure 9 New Workspace ...................................................................................................................... 28
Figure 10 CovMo Default Panel Layout ................................................................................................ 29
Figure 11 Hide Panel ............................................................................................................................. 29
Figure 12 Workspace with two Panel views open ................................................................................ 30
Figure 13 After collapsing other views, Map View expands ................................................................. 31
Figure 14 Apply Workspace .................................................................................................................. 32
Figure 15 History Menu ........................................................................................................................ 33
Figure 16 KPI Selector Pane .................................................................................................................. 33
Figure 17 Pull-down Menu in Service and Completion......................................................................... 34
Figure 18 Date & Time Filters ............................................................................................................... 34
Figure 19 Data & Time Filter ................................................................................................................. 35
Figure 20 Data Summary....................................................................................................................... 36
Figure 21 Network Topology Filters ...................................................................................................... 36
Figure 22 Fly to Location button ........................................................................................................... 37
Figure 23 Subscriber Filter .................................................................................................................... 37
Figure 24 Protocol Filter........................................................................................................................ 38
Figure 25 Handset Filter ........................................................................................................................ 38
Figure 26 Additional Rules .................................................................................................................... 39
Figure 27 Map Layer Options ................................................................................................................ 40
Figure 28 Map Menu Bar ...................................................................................................................... 40
Figure 29 KPI Visibility ........................................................................................................................... 42
Figure 30 Display Network Symbol Control .......................................................................................... 42
Figure 31 Display Network Symbol ....................................................................................................... 43
Figure 32 Network Symbol Label .......................................................................................................... 43
Figure 33 Display Network Symbol with Label ..................................................................................... 44
Figure 34 Network Symbol Options ...................................................................................................... 44
Figure 35 LTE Options ........................................................................................................................... 44
Figure 36 UMTS Options ....................................................................................................................... 45
Figure 37 Location KPI Menu ................................................................................................................ 46
Figure 38 Location KPI Legends ............................................................................................................ 47
Figure 39 User Polygon Menu ............................................................................................................... 47
Figure 40 Info Window.......................................................................................................................... 48
Figure 41 Create a New Polygon ........................................................................................................... 48

Figure 42 Polygon Creation Confirmation............................................................................................. 48
Figure 43 Reset Polygons ...................................................................................................................... 49
Figure 44 Polygon Properties ................................................................................................................ 50
Figure 45 Delete Polygon ...................................................................................................................... 51
Figure 46 Deletion succeeded ............................................................................................................... 51
Figure 47 Multi-Map View .................................................................................................................... 52
Figure 48 Enable Multi-Map Function .................................................................................................. 52
Figure 49 Analysis Performed on Map 1 ............................................................................................... 52
Figure 50 Analysis Performed on Map 2 ............................................................................................... 53
Figure 51 Display Label of Network ...................................................................................................... 54
Figure 52 Legend Example .................................................................................................................... 54
Figure 53 Map View Export ................................................................................................................... 55
Figure 54 Map View Export ................................................................................................................... 55
Figure 55 Tabs of Properties View ........................................................................................................ 56
Figure 56 Property Panel – KPI.............................................................................................................. 57
Figure 57 Property Panel – Chart .......................................................................................................... 58
Figure 58 Property Panel – Export Chart .............................................................................................. 58
Figure 59 Property Panel – Save Export Chart ...................................................................................... 59
Figure 60 Property panel – Cell and Tile property ................................................................................ 60
Figure 61 Property Panel – Measured Cell of a Tile Property ............................................................... 62
Figure 62 Network Display .................................................................................................................... 63
Figure 63 Sorting by columns................................................................................................................ 64
Figure 64 Display/Hide columns ........................................................................................................... 65
Figure 65 Using Filters to find out specific Cell, Tile or Subscriber ....................................................... 65
Figure 66 Subscriber Report ................................................................................................................. 66
Figure 67 Detail Report ......................................................................................................................... 66
Figure 68 Sequence Chart in the Call Analysis window ........................................................................ 67
Figure 69 Events view in the Call Analysis window............................................................................... 67
Figure 70 Detail view in the Call Analysis window ................................................................................ 68
Figure 71 Protocol Failure Event KPI ..................................................................................................... 69
Figure 72 RRC Messages are available from RRC drop down list ......................................................... 69
Figure 73 S1AP Failure Type.................................................................................................................. 70
Figure 74 S1AP Causes List .................................................................................................................... 70
Figure 75 X2AP Failure Type ................................................................................................................. 74
Figure 76 X2AP Causes List.................................................................................................................... 75
Figure 77 Login Admin Page ................................................................................................................ 134

Tables
Table 1 Chapter Overview..................................................................................................................... 10
Table 2 User Guide Overview ............................................................................................................... 12
Table 3 CovMo Input Data .................................................................................................................... 18
Table 4 Menu items of Network Topology Filters ................................................................................ 37
Table 5 OpenStreetMap Menu Bar Items Description ......................................................................... 41
Table 6 Properties Tab .......................................................................................................................... 57
Table 7 S1AP Radio Network Layer Cause ............................................................................................ 73
Table 8 S1AP Transport Layer Cause..................................................................................................... 73
Table 9 S1AP NAS Cause ....................................................................................................................... 73
Table 10 S1AP Protocol Cause .............................................................................................................. 73
Table 11 S1AP Miscellaneous Cause ..................................................................................................... 74
Table 12 X2AP Radio Network Layer Cause .......................................................................................... 77
Table 13 X2AP Transport Network Layer Cause ................................................................................... 77
Table 14 X2AP Protocol Cause .............................................................................................................. 77
Table 15 X2AP Miscellaneous Cause ..................................................................................................... 78
Table 16 UMTS KPIs ............................................................................................................................ 132
Table 17 LTE KPIs................................................................................................................................. 133
Table 18 User Role .............................................................................................................................. 134

1 ABOUT THIS GUIDE
This guide is designed to help you learn how to use the CovMo system. CovMo system provides
analysis for radio network KPIs using call trace data for cellular communication networks. It geo-
locates network events with subscriber-based intelligence.
This preface has the following sections:
• Chapter Overview
• Audience
• Learning Objectives
1.1 Chapter Overview
Chapter Name Content

Chap 1: ABOUT THIS GUIDE This chapter describes the structure and conventions of this user
guide.
Chap 2: INTRODUCING This chapter provides an overview of the CovMo system and
CovMo SYSTEM presents the features in this release and elaborates how
operators get benefit from the system.
Chap 3: GETTING STARTED This chapter provides information required for setting up and
WITH CovMo SYSTEM using CovMo, including system hardware architecture, system
hardware and data input requirements.
Chap 4: NAVIGATING CovMo This chapter provides the details of the window layout and menu
SYSTEM for users to perform and generate diagnostic information.
Chap 5: KPI DETAILS This chapter provides the details of CovMo KPIs and details about
deeper Optimization techniques.
Chap 6 USER ROLES This chapter is an overview to different user roles available in the
system
Table 1 Chapter Overview

1.2 Audience
This guide is designed for CovMo system users and gives details for continuously monitoring traffic
to diagnose problems in wireless cellular networks. The target audience for this guide includes the
following:
• Radio Network Operators
• Core Network Optimizers
• CovMo System Administrators
• Customer Care Administrators
As part of the above-mentioned roles, you will need to be familiar with:
• Domain know-how of wireless cellular networks, including basic concepts and terminology
used in inter-networking
• Network topology and protocols
• Browser-based interfaces.
1.3 Learning Objective
This guide aims to cover all functionalities of CovMo system. It provides ability for CovMo users to
use geo location system in their routine activates.
Users will be able to learn and understand:

- Meaning of system KPIs
- GUI functions under Control Panel
- Work flow to use KPI
- Understanding MAP view and using controls on MAP view
- Using automatic cell optimization process using PSC, feeder, NBO, PCI and RS.

1.4 About the user guide
Below table give quick highlights what this guide describes and covers:
This section Contains Information On
System Introduction Describe CovMo system and provide understanding

about geo location functionality and understanding about
data sources used for subscriber call location.
System architecture System architecture gives understanding of geo location
system about connectivity between various network
elements and data gateways, application servers.
Getting started Gives understanding about Logging into system. Details of
various tabs in system and usage workflow.
Works space Gives understanding about various panels after login.
description Workspace provides user interface details and
understanding of functions after login to system.
Control panel, map Details of each and every button, tab or control under
view and properties control panel, geo graphical map view using MAP APIs,
panel properties panel with information about KPI summary.
KPI description Details about KPIs available in CovMo.

Optimization Details of optimization modules and work flow of using
geo location based optimization results.
Subscriber tracing Understanding of subscriber trace, IMSI group creation
and using geo location results restricted to IMSI group or
individual IMSI analysis.
Table 2 User Guide Overview

2 INTRODUCING CovMo system
CovMo system empowers your network with subscriber mobility intelligence, empowering you to
monitor and analyze service quality in GSM, UMTS and LTE networks using Layer 3 events
information from call trace data.
Topics covered in this module:
• Welcome to CovMo system
• How you can get benefit from CovMo system
• CovMo system working mechanism
• Understanding of CovMo system architecture.
2.1 Welcome to CovMo system
Today’s cellular network operators face a rapidly evolving market with new technologies there are
various challenges to optimize such complicated networks. Following are some key challenges:
• The network structure going to cloud

• Exponential increase in traffic, the ever expansion of the network
• Interchanging network technologies
• Increase in demand for voice and data transmission
• Demand for high quality of transmitting video and related real-time multimedia
applications as essential for both existing and emerging future mobile networks.
These are making network optimization more complicated. CovMo system consolidates all these
factors and displays the relevant KPIs on a simple to understand web based interface to address
these challenges.
QoS metrics are measured in cellular networks but using cell based KPI, an effort should be made to
assess the subjective quality measures for subscribers KPIs. The criteria for evaluating QoS in voice
and data services may include following KPIs
- Accessibility
- Retainability
- Call quality
- Voice quality and connection
- Downlink and uplink throughput.

CovMo system effectively geo-locates network events using subscriber-based intelligence. This
allows operator to monitor various statistics using subscriber location, following are some key
factors for optimizing network using geo location system:
- It allows calls to be geo located not only outdoor but also indoor calls to detect coverage holes
- Pinpoint service disruptions across the entire network using 50x50 meter tile heat map
- All time periods analysis 24x7
- Subscriber based reports.
2.2 Benefit & advantages of Geo location system
Benefits:
• Unique map engine to support Open Street, Google and Bing map data
• Web client-server based design, no installation required in client side. Access system using
web browser
• Network coverage KPIs heat maps
• Network traffic and failure KPIs with view to present multiple KPIs at same time
• Identifying coverage shortfalls with subscriber reported measurement reports
• Almost real-time data available with small latency
• Data is taken from real customers of your network.
Following are key advantages of geo location system
Effective Troubleshooting Techniques: CovMo system supports network operators in

troubleshooting network and subscriber issues involving geo-locations, radio environments, and
network signaling from multiple dimensional perspectives.
Cost-saving Methodology: CovMo significantly reduces the number of drive tests and walk tests that
an operator needs to perform, call trace functionality allows user to trace any call using subscriber id
(IMSI) filter.
Instant Root-Cause Identification: CovMo system supports detailed call tracing, enabling users to
analyze the problematic calls of impacted subscribers in specific locations with layer 3 message
details.
User-perceived QoS Improvement: CovMo system provide KPIs like Protocol analysis with radio link
sync failure and data throughput KPIs for QoS improvement.
5. Subscriber based analysis: CovMo system provides subscriber-based analyses such as VIP group
analysis, femtocell strategy if subscriber reported coverage KPIs are bad.

2.3 How CovMo system works
Below section gives understanding to CovMo system user about input data required for geo location
and techniques used by geo location algorithm.
Data Input: CovMo system loads the network topology site database, call trace data and
configuration information by connecting to the operator’s RAN (Radio Access Network) network
elements.
Source data files are processed according to the following procedure after data parsing by Event
Parser and Network Topology Parser:
1. Positioning
2. Positioning Post-Processing
3. NBO (Neighbor Based Optimization) Processing
4. Inter-NBO Processing
5. Copy tables into RNC daily database
6. Inserting new data into daily database.
Positioning is based on MRs, cell locations and distances which is processed in steps 1 and 2. Steps 3
and 4 are for optimization and other 5 and 6 complete the data processing.
Web Client-Server Architecture: CovMo system geo-locates calls and visualizes network coverage
and various KPIs on user PC using a web browser. User PC needs connectivity to application server,
installed in Indosat IT environment. Users are able to access geo-location results with detailed charts,
reports and heat maps. The system incorporates map engine plug-ins to be installed on client for
geographic map visualization. Users are able to import any map layer view into Google Earth
application to enhance users’ analytical capabilities in the geographical map view.
Multi-dimensional Modeling: In addition to conventional multi-lateration geo-location algorithms,

CovMo system applies Chaos Theory for modeling multi-dimensional data in order to achieve higher
accuracy. CovMo system utilizes geo-positioning based on data collected at different times for the
same location in order to achieve a much higher accuracy rate and better map resolution.
CovMo system algorithm is designed to distinguish the indoor from outdoor when possibility of one
outcome is higher than the opposite one. This means that there is no 100% confidence in the call
definition. But when call has more outdoor characteristics it is defined as outdoor.
Signal strength, active set, cell, EnodeB cluster, RNC, GSM base station, time advance, distances,
moving speed and moving direction are values collected from source files and based on the CovMo
system algorithm they are inserted into the database. Algorithm goes through database values and
can determine if a call is indoor or outdoor, moving or stationary.
2.4 System architecture and data sources

Before you start using CovMo system, this section will provide you with basic information about
system architecture and gives understanding about data sources connectivity.
2.4.1 System architecture
CovMo system hardware uses client and server design model. It requires connectivity with existing
network elements as indicated in the diagram below. Description for required components are
below
a. CovMo Client: CovMo user’s personal computer or laptop with a browser installed.
Recommended Mozilla Firefox 26 above and Chrome 30 above. Suggest using the latest
browser version for best end user experience.
b. CovMo Database and Application Server (APP): This server makes use of CovMo system’s
major functionalities and made them accessible by CovMo clients via a browser. It hosts the
data required by CovMo for analysis. Data stored in this server database includes network
topology and configuration information, processed results of call trace event logs. Data
Gateway server stores its results in application server.
c. CovMo Data Gateway Server (DWG): Via the CovMo ETL tool installed on Data Gateway
Server, it can extract, decode, transform, and load the required data. Data is collected from
operator file systems by push and pull mechanisms. Data Gateway server host raw call trace,
configuration management and site database to process, and then store the processed
result onto Application Server via server internal connectivity between DGW and APP
servers.

Figure 1 System Hardware Architecture
2.4.2 Source data details
CovMo system collects various data types from Indosat existing network elements via vendor NBI
interface. The table below lists the items required for collection by the CovMo system.
Essential Input Detail

Event log/call trace data Huawei: 2G/3G CHR, LTE Max. depth trace data
Ericsson: 2G RPMO, 3G GPEH, LTE CTR
ALU: 3G/LTE 3GPP standard trace data

IMSI/IMEI Mapping data from MME
Network Topology (Vendor 2G: Site Database [LAC (Location Area Code)] and [Cell ID] be the key
Configuration Management for mapping to CM file, Longitude, Latitude, Indoor,
files from OSS and Site Cluster_Name_Region, Cluster_Name_Sub_Region,
Database) Cluster_Name_Zone, Azimuth, Antenna_Model, Antenna_Type,
Height, Beamwidth_H, Antenna_Gain, Downtilt_El, Downtilt_Mec,
Band, Site ID
3G: Site Database [LAC (Location Area Code)] and [Cell ID] be the key
for mapping to CM file, Longitude, Latitude, Indoor,
Cluster_Name_Region, Cluster_Name_Sub_Region,

Cluster_Name_Zone, Azimuth, Antenna_Model, Antenna_Type,
Height, Beamwidth_H, Antenna_Gain, Downtilt_El, Downtilt_Mec,
Band, Site ID
LTE: Site Database[Cell ID] & [TAC (Trackig Area Code)] to be the KEY
to find informaiton ; in Site Database[Cell ID] - (column-G) Ex 764152
(Where 76415 is eNodeBID, 2 is Local CellID), and in CM use
<eNOdeBId>+<CellId> and <TAC>, Longitude, Latitude, Indoor,
Cluster_Name_Region, Cluster_Name_Sub_Region,
Cluster_Name_Structure_Type, Azimuth, Antenna_Model,
Antenna_Type, Antenna_Height, Beamwidth_H, Antenna_Gain,
Down_Tilt_Mechanical, Down_Tilt_Electrical, Band, Site ID
Neighbor Relation Data Inter frequency, Intra frequency, IRAT neighbor data
Table 3 CovMo Input Data
Data source determines availability of measurements in CovMo system. ETL tool installed on the
CovMo Data Gateway will extract, transform, sort, merge and load collected data into the CovMo
Database Server automatically. Based on data complexity and its correlation, CovMo system will
utilize multicast and conditional split data process mechanisms. Data collection and processing tasks
are scheduled for automatic execution at every 15-minute interval. KPI calculations are done hourly
and daily basis for KPI type inputs. If data processing task fails, its cause will be captured in logs for
further troubleshooting.
Matching of correlated data from CM feed and SiteDB is highly important. This information is used to
make geolocation calculations. Incorrect data from either side would significantly impact the
geolocation process and geolocation accuracy.
Be advised to check internal SiteDB with Site information and vendor’s network topology
information before using CovMo geolocation system. Changes made to OSS database would take
affect only the next time data is imported. Typical CM and SiteDB data is loaded once a day so the
changes may take affect the next day the change is made.

3 GETTING STARTED WITH CovMo system
3.1 Logging in
Via operators’ computer Web browsers, users may log in and access the CovMo system. Operators can
access this by connecting across their IP network.
Follow the steps below to log in CovMo system.
Step 1: Open Web browser. Type the appropriate address in the address bar. For the URL address to
access CovMo, contact your administrator.
Step 2: The login screen will appear upon loading the CovMo page.
Step 3: Select CovMo, key in your username and password
Step 4: Click Sign in.
Figure 2 CovMo Client Login Screen
Step 5: After successful log-in, you will have access to the system. After first login, the Map View auto
center to focused country center.

Figure 3 CovMo Client Start page
3.2 Plotting data
After successful login default data and filters are auto selected. Click Apply all button to have KPI display.

Figure 4 CovMo Client RSCP KPI applied
Once user hit Apply all, the following changes appear:
- MAP view start displaying KPI as per selection of KPI Group and Analysis type, in above example
RSCP – Best Cell Average is displayed.
- Report panel displays the cell-wise KPI result. KPI columns are subject to selected KPI.
- Properties panel give information of selected KPI and time information.
3.2 Understanding major components
CovMo contains four major view components:
- Control Panel, which allows users to select key performance indicators and set filters
- Map View, which allows users to browse geo-locations on map;
- Properties Panel, allowing users to inspect property details
- Report View, where reports for further diagnosis can be found.

Figure 5 CovMo Work-Space
Brief description of CovMo components:
Control Panel: The main parts of control panel are
- KPI and analysis selection

- Date & time selection
- Network Topology selection
- Subscriber filter selection
- Protocol filter selection
- Failure cause filter selection
- Handset – Maker/Model filter selection
- Additional rules filter selection.
Control panel allow users to make selection of KPI group and analysis type. Selection for date, time and
network element for analysis is done in control panel. Network topology parameters need to be filtered
from control panel “Network Topology” section.
Map View: In order to display KPI heat maps, Map view is utilized. Map view is in center of user
interface after login and default view shows Open Street Map. All controls related to Map view are given
in later chapters.

Properties Panel: It is used to display summary of selection and important KPI results. There are
following tabs under property panel:
- KPI: to show selection results

- Chart: Triggered by clicking on any cell or tile display results as per selected KPI
- Property: To view selected element cell/tile/polygon parameters details
- Network: Provide tree view of GSM BSC, UMTS RNC, LTE ENODEB and their Cells and
Sectors/Clusters, double click in this panel triggers property tab.
Report Panel: Displays selected KPI report statistics, results are allowed to be export in CSV/excel
format from report panel.
Later sections cover functions of these components in details.
3.2 Collapsible menu of tabs
CovMo user interface is flexible to adjust the panel to maximize or minimize the various views. Control
to collapse these tabs is using on right top of each tab.

Control panel:
Properties panel:

Report panel:
The Property tab displays a list of details that exceeds the length of the panel. Dragging the scrollbar
downwards will show items that extend beyond the bottom of the panel.
Click on one cell in report and the switch to Property tab under Properties panel to display information.
Figure 6 Cell Property

User can also click one tile to see tile property.
Figure 7 Tile Property

4 NAVIGATING CovMo system
Featuring intuitive workflow and friendly graphical user interfaces, plus a Map View plug-in, CovMo is a
browser-enabled application that provides effortless methods for accessing and operating according to
individual users’ needs. Unlike standalone executable programs that run on only certain computing
environments - which often require installation and further configuration - CovMo includes all the
advantages of a browser-enabled client, running on browsers in any operating system.
This chapter begins by introducing workspace overview, followed by a detailed description of each
workspace view components, including the sections:
• User Interface Overview
• Control Panel Details
• Map View
• Properties Panel
• Report View
4.1 User Interface Overview
CovMo user interface view is maintained per user preferences and appears after login. Users can keep
control of their own default user interface in following ways.
Using Workspace to setup most commonly used queries as default (different KPIs)

Figure 8 Workspace Menu
When user chooses Add as workspace system automatically selects current KPI selection, user can give
name, set to use always latest data and share with other users. To save, click Submit.
Figure 9 New Workspace
4.1.1 User interface default view

Default user interface displays all four panels as shown in below screen capture.
Figure 10 CovMo Default Panel Layout
4.1.2 User interface two panels view
To allow reporting of Map and report view, Control and Property panels can be minimized. It provides
then bigger Map view.
Figure 11 Hide Panel
By clicking on the same icons, the hidden panels will again be visible.

Figure 12 Workspace with two Panel views open
4.1.3 User interface only Map view
In order to expand Map view all three Control, Report and Property panels can be minimized to allow
Map results report for KPI analysis.

Figure 13 After collapsing other views, Map View expands
This setting will be default view if user logs out while three panels are closed.

4.2 Control Panel Details
CovMo system Control Panel is key element to start using system. This allow user to make KPI selections
and provide analysis accordingly. Below sections describe meaning of each tab under control panel.
4.2.1 Panels within control view
On the left-hand side of the CovMo user interface, available KPIs and filters are organized into different
panes from top to bottom: Workspace, KPI selector, Data & Time Filter,
Workspace: It functions like a browser bookmark menu where you can save your analyzing sessions. It
captures the scenario like filter selection and display as per those selection in future.
Figure 14 Apply Workspace
History: It contains session history during the active session only. The list will be erased when the
current web session is closed, or user logs out.

Figure 15 History Menu
KPI selector: The KPI selector pane is the entrance in which users begin navigating the system. Inside
the KPI selector pane are four pull-down menus—Group, KPI, Service Type and Completion Code—as
shown below.
Figure 16 KPI Selector Pane
Each selection in the Group pull-down corresponds to its KPIs, followed by the common service types
and completion codes for further digging out. For example, this allows users to filter their research by
how Voice, PS 99, PS HSPA, Multi-RAB, or SMS (Short Message Service) appears from the Service Type
menu or to filter by normal, dropped or blocked calls from the Completion Code. The KPIs here are
known as Tile-based KPIs. The full list of the KPIs provided are provided later in the guide.

Figure 17 Pull-down Menu in Service and Completion
Date & Time Filters: To review the status of certain time periods, select from Date & Time for data by
the hour, the day or duration of your interest.
Figure 18 Date & Time Filters
Data summary on the bottom of Date & Time pane provides a great, comprehensive summary of dates
and BSCs/RNCs/eNodeBs that is available for analysis. Data summary is presented in a spreadsheet,

enabling a quick and efficient lookup for the dates with exact hours in 24-hour format and
BSCs/RNCs/eNodeBs information.
After clicking the “Data summary” button, a Data summary window pops up, listing dates with exact
hours when data was collected on the left-most column and RNCs IDs of which data belongs to on the
right.
Figure 19 Data & Time Filter
Column headers include Date and several PUs. Clicking Date column header can easily change its sorting
order. Taking 2017-02-09 as an example, data was collected and reported from 14:00 to 15:00 from RNC
107. Acquiring the information saves users’ time in looking for dates and data. It’s easy and accurate to
just select the date and hours from Date & Time Filters.

Figure 20 Data Summary
Network Topology Filters: Fed with network topology data, CovMo allows users to view data
hierarchically by layers of network structure elements. Full coverage governed by entire
BSC/RNC/eNodeB, or certain defined areas, or even more specifically by a single Cell/Sector can be
selected for viewing.
Figure 21 Network Topology Filters
The table below describes each item of the filter.
Menu Item Description

Vendor Network Equipment Manufacturer
After Area/RNC/BSC is chosen as the filter type, all
Area/RNC/BSC radio network controllers appear in the RNC/Area
list for either single or multiple selections
TAC TAC selection
eNodeB/NodeB/Site eNodeB/NodeB/Site selection
The selection criterion for choosing a radio
RF Band
frequency band
A list containing all available channels on the
EARFCN/UARFCN/ARFCN
chosen radio frequency band
When polygon is chosen as the filter type,
Polygon BSCs/RNCs/eNodeBs need to be identified first,
then one or more Polygon can be selected
Sector/Cell When Cell/Sector is chosen as the filter type,

BSCs/RNCs/eNodeBs need to be identified first,
then one or more Cells/Sectors can be selected
Table 4 Menu items of Network Topology Filters
The Go button can be found in the Network configuration pane. It is used to re-center the Map View to
where the selected cell/sectors in Network Topology are. When any single Cell/Sector has been chosen
in Network Topology filter, CovMo zooms in to the selected location; if multiple Cell/Sectors, Polygon or
BSCs/RNCs/eNodeBs are chosen, CovMo defaults to a central position, which is averaged from the
geographic coordinates of these cells.
Figure 22 Fly to Location button
Note: Because Go button navigates to a calculated average based on the latitude depends and longitude
of each sector, the central location displayed might be in suburbs or rural areas outside of the desired
area.
Subscriber Filters: VIP subscribers are classified to groups during system configuration. This
categorization allows users to quickly look up details of KPIs relevant to VIP subscribers by selecting their
defined groups in the filter pane.
Figure 23 Subscriber Filter
Note: For results while using the Subscriber filter, target VIP subscribers must have been engaged in
calls within the selected network location and time.

Protocol Filters: This is used to set specific layer 3 event to restrict the report. Below are the options
Figure 24 Protocol Filter
Handset Filters: in this pane, user can specify handset maker and model.
Figure 25 Handset Filter
To add a rule: Select Criteria, set Operator (>, =, or <), set numerical threshold, and then click Add.
To delete a rule: Select the rule to be deleted and then click Delete.

Figure 26 Additional Rules
After all desired KPI, date and time filter, network topology filter, radio frequency band and channel, or
even the specific subscriber group, have been selected, click Apply All. The Apply All button will display
different colors, shapes, patterns and symbols that represent the results of each KPI in Map View.
4.3 Map View
Adopting a Web map plug-in that combines with conventional maps, CovMo system transforms rows of
numerical data retrieved from user-input configurations in Control Panel into visualized geographical
information. These numbers are no longer hard to understand when reflected in Map View, which
provides operators a quick and comprehensive method for pinpointing possible geographical factors. By
geo-locating KPI values and other relevant information in Map View.
Map view is composed of various control to display KPI, Display Network Symbol, Display Location Based
Analysis, Export Current Displaying KPI, Search, User Polygon, Map Selection, Multi-Map, Enable
Distance Ruler, Help or User options.
4.3.1 Map View
CovMo system work in line with various Map View plug-in OpenStreetMap, Bing or Google maps.

Figure 27 Map Layer Options
Map View is positioned in the top center of the workspace. After logging in to CovMo, the initial screen
displays as shown below, based on OpenStreetMap.
Map View is composed of three primary elements

- a Menu Bar at the top
- a Navigation Control on the left
- a Map Scale on the bottom-left corner
Menu Bar: The Menu bar’s function icons are marked with numbers that correspond to the table below,
describing each menu item’s function.
Figure 28 Map Menu Bar
No. Item Description

1 KPI Visibility Conceals/display Tile/Location based analysis of KPIs on Map
Conceals/display indoor/outdoor Network Elements and cell ID’s on
2 Display Network Symbol
Map
Display Location Based Conceals/display geographical analysis of Position/Footprint in Map
3
Analysis View
4 Enable Cell Multi-Select Enable/disable multi cell selection
5 Export Current Exports and saves current results of KPI in KML or MapInfo format

Displaying KPI
Cell/Sector ID/Name numbers or location can be entered to locate
6 Search
them in Map View
7 User Polygon Define/select user-defined areas
8 Map Selection Allows to display current KPI analysis on map
9 Multi-Map Allows to display two maps with KPI for side by side analysis
10 Enable Distance Ruler Allows distance measurement between two points
11 Help Provides an online user guide (PDF)
12 User Change Password or Logout CovMo system
Table 5 OpenStreetMap Menu Bar Items Description
Navigation Controls are used to move and look around and zoom tab — the same results achieved with
a mouse. The controls also allow users to zoom in downward the view. The following picture and table
show the controls and explain their functions.
To use the Navigation Controls, move the cursor over to the left side of the Map View.
Directional pad for MAP navigation
MAP zoom in/out control

4.3.2 KPI visibility control
Same area with no tiles display, if user want to read MAP then tiles layer can be disabled or user
displayed multiple KPIs tiles, point foot print then whole MAP tiles can be removed using this control.
Figure 29 KPI Visibility
4.3.3 Network Symbol and cell labels
Display/Hide Network Symbol: In order to display base stations on Map view to check location of the
base stations, click on site symbol on Map meun bar.
Figure 30 Display Network Symbol Control
Example of cell display, different RNCs are shown by different colors.

Figure 31 Display Network Symbol
Use Label in the menu to indicate how the label should show.
Figure 32 Network Symbol Label
Below screenshot displays network symbols on openstreet map with site name in the labels.

Figure 33 Display Network Symbol with Label
Use Option to open additional options for other cell presentations:
Figure 34 Network Symbol Options
Figure 35 LTE Options

Figure 36 UMTS Options
4.3.5 Location based KPIs
Using location based KPI: Users can adjust configurations to analyze entire network coverage by
TAC/RNC/BSC under Tile Based KPIs, the Location Based KPIs display an individual cell’s point locations
of KPI occurrences in Map View.
Location Based KPIs pane is accessible via the white balloon icon in Map View, and there will be
different options for different technologies (LTE, UMTS, BSC)

Figure 37 Location KPI Menu
Steps to use:
a. Click on the desired KPI in the menu. The white balloon icon will turn into yellow after selection,
b. Click on the cell on Map view. The selected cell should be highlighted with a red border.
Location KPI shows different icons by various conditions. The picture below presents all conditions with
their corresponding icons.

Figure 38 Location KPI Legends
4.3.6 User Polygon creation
When user wants to restrict the analysis within a graphical area, a user-defined polygon can be drawn,
imported from User Polygon Menu on the Map Menu Bar. The polygon can be also selected from the
control panel as a filter too.
Steps to create geo graphical polygon:
a. Click Polygon icon

b. Choose New to create a user defined area on Map
Figure 39 User Polygon Menu
c. An Info window reminds user to click map to create user defined area. Click OK to continue.

Figure 40 Info Window
d. After confirmation to above box, point is displayed on MAP and user needs to complete the
polygon creation.
e. Double click to finish the polygon and a new selection box will open.
Figure 41 Create a New Polygon
f. On the New polygon window, enter the name of user defined area. To make this area visible to
all users, check the Public box. Click OK to confirm the area name.
g. An Info window confirms the new user area saved. Click OK to continue.
Figure 42 Polygon Creation Confirmation

Figure below shows the menu of user area. From the drop-down list, select the user area to be displayed
on the Map. Click Reset to clear the previous selection.
Figure 43 Reset Polygons
Check the Show Polygon check box to display the selected area on Map. Click Properties to review the
property of selected area on Properties window and see KPI for selected polygon.

Figure 44 Polygon Properties
Following are steps to delete a user polygon.
a. Select Polygon from MAP drop down

b. Click Delete on User Polygon Menu to delete the selected user area, then click Yes to confirm
the deletion of selected user area.

Figure 45 Delete Polygon
c. An Info window opens to confirm the user polygon was deleted. Click OK to continue.
Figure 46 Deletion succeeded
4.3.7 Using Multi-Map View tab
Multi-Map View can be used to compare two different KPIs for same area. To enable Multi-Map panel,
check the Multi-Map box on Map Tool Bar.
The Map View splits into two views displaying the two identical areas. Analyses can be performed and
contrasted on the two maps.

Figure 47 Multi-Map View
To visualize the first analysis on Map 1: On Map Tool Bar, click Multi-Map icon again, and then select
Map 1.
Figure 48 Enable Multi-Map Function
On Control, perform the first analysis, for example, the indoor RSCP analysis. The result is visualized on
(Left) Map 1.
Figure 49 Analysis Performed on Map 1

To visualize the second analysis on Map 2: On Map Tool Bar, click Multi-Map icon again, select Map 2.
For example, Drop Call, run query in Control panel for map 2.
Figure 50 Analysis Performed on Map 2
4.3.7 Map Graphics & Legends
In addition to the Menu Bar, Navigation Controls described in the previous section, map graphics for
network symbols and labels, and legends used for the KPIs are introduced here.
When the Display Network Symbol & Label functions in Menu Bar are enabled, sectors appear in two
kinds of graphics followed by Cell IDs. A fan-shaped graphic indicates a cell’s location and the direction
of its radio wave transmission; a square-shaped graphic suggests an indoor cell.

Figure 51 Display Label of Network
A legend defines the meanings of colors used to represent the performance statistics of selected KPIs.
The map is masked with tiles, which divide the network into squares by 50 meters, with each square
color-coded to make for easy identification of the network’s most problematic areas. Clicking on a
square will display the chosen network’s performance statistical data at that specific location (tile) and
its corresponding serving cells’ information (that which is listed in the Properties View panel).
Figure 52 Legend Example
4.3.8 Heat Map/tiles export
To export the Tiles Analysis:
- Click the Export icon on Map Tool Bar, and then select the file format. CovMo supports KML,
MapInfo formats for map export. The map will be exported into the selected format and saved
in browser’s Download folder.

Figure 53 Map View Export
Figure 54 Map View Export

4.4 Properties panel
Properties View consists of five tabs: KPI, Chart, Property and Network. It can be triggered in following
ways,
- Clicking any colored square that represents a certain tile in the Map View displays the tile’s details as
well as data of all associated cells in the Properties View.
- Clicking any fan-shaped cell in the Map View reveals information about the cell, Antenna and
Neighbors in the Properties View.
Figure 55 Tabs of Properties View
No. Item Description

Shows the KPI group, name, network status and time of user selection.
1 KPI It’s especially useful on Multi-Map mode or reviewing various KPIs on
a time difference
Shows various types of graphs such as an XY (scatter) or a pie chart
2 Chart
displaying relevant data of a selected cell or tile
Displays detailed attributed of cells, tiles, symbols or cell nodes
3 Property
selected from Map view, Report View or Network tab
Reveals the hierarchical relationship of network nodes in network
4 Network
topology tree view mode

Table 6 Properties Tab
4.4.1 KPI tab
Given below is an example of KPI tab.
Figure 56 Property Panel – KPI

4.4.2 Chart tab
The picture below is an example of the Chart tab.
Figure 57 Property Panel – Chart
To export a chart from Properties panel, click the Export icon on bottom-right corner of the chart, and
then select the file format. CovMo supports PNG, JPEG, PDF, SVG and CSV formats for chart export. The
chart will be exported into the selected format and saved in browser’s Download folder.
Figure 58 Property Panel – Export Chart

Figure 59 Property Panel – Save Export Chart
4.4.3 Property tab
The picture below shows one example of Property tab content. More details about the results of clicking
a cell or a tile are provided in the sub-sections below.

Figure 60 Property panel – Cell and Tile property

4.4.3.1 – Viewing cell property
Clicking a cell in Map View reveals its relevant information in Properties View, which displays Cell
Property, Antenna, Neighbors and CM attributes in sequence.
Cell Property displays a cell’s basic information, including: Cell ID, Cell Name, Site ID, LAC, Cluster Name,
RNC ID, Longitude, Latitude, Radio Frequency, etc.
Antenna section contains configuration information, such as Azimuth, Height, Gain, and so on.
Under Neighbor section the current neighbor cells for the selected cell are shown.
CM attributes section takes from daily CM files which are sent to CovMo system additional parameters
(if they are maintained in source system) for the current cell to help in finding additional information.
Another feature is that it lists cell pair parameters if they are found from the CM file.
4.4.3.2 – Viewing tile property
Clicking a tile in Map View shows its relevant information in Properties View, which displays Tile
Property and serving cells.
Tile Property contains the following basic items:
1. Best Pilot Average (Initial): Average of the strongest cell’s RSCP & EcN0 from the initial call
2. Call Initiated: Number of initial calls in the tile
3. Call Ended: Number of ended calls in the tile
4. Drop Call: Number of exceptional dropped calls in the tile
5. Best Pilot Average (All MMR): Average of the strongest cell’s RSCP & EcN0 from all MMRs
6. Best Server Average (1st MMR): Average of the best server’s RSCP & EcN0 from the 1st MMR
reported active set of each call
7. Longitude and Latitude

Measured Cells indicates whether they are the best pilot or the best serving cells in this tile. Each
Measured Cell section provides all relevant information about the cell with this tile:
1. Distance to tile: The distance between the cell and this tile
2. Best Server Average (Initial): Average of the RSCP & EcN0 from the active set of the initial
call, and the cell is the best server among active sets.
3. Call Initiated: Number of initial calls taken place from the cell and within this tile
4. Call Ended: Number of ended calls in the cell and within this tile
5. Drop Call: Number of exceptional dropped calls occurred in the cell and within the tile.
6. Best Pilot Count: Counts of which this cell was measured as the best pilot in the tile
7. Best Pilot Average (All MMR): Average of the RSCP & EcN0 from the all MMRs that the cell is
the best pilot
8. Longitude and Latitude
Figure 61 Property Panel – Measured Cell of a Tile Property
4.4.3.3 – Viewing PU property
Clicking the blue cube, representing a EnodeB, RNC or BSC under the Network tab, system switches
to view of Property tab which displays the attributes of selected EnodeB, RNC or BSC.
Note: Clicking the triangle icon collapses and expands network trees. The icon appears black
when the tree is expanded.

Figure 62 Network Display
4.5 Report View
CovMo automatically generates detailed reports in Report View which describes the performance
statistics after applying filters and selecting KPIs in Control View. Tabs and column headers of
reports vary with selected KPIs and filters.
In the report panel there are 4 tabs giving data in 3 levels of report granularity:
- Top level is presented with Cell and Tile Tabs. Here are major KPIs are shown with
respective values for cells of the network or tiles on map, like number of calls, average RSCP,
EcNo values…
- Subscriber level is presented by Subscriber Tab. On that Tab subscriber-centric KPIs are
gathered, like IMSI, IMEI, band support…

- Call level is presented by Detail Tab. On this tab is the deepest report granularity, giving the
overview of KPIs for the individual calls, like call duration, call termination, number of HOs
during the call…etc.
An example of Report View is shown below. The view comprises of the following parts:
- content tabs on the top,
- columns of statistics in the center pane and a bottom bar,
- page switching control,
- data number displaying information
- a Save icon
Whilst viewing one of the four reports, the bottom bar shows the total data and page volume of
reports. Clicking the left or right- forward arrow button allow users to view the data page by page.
Entering a number that does not exceed the total page count in the field next to Page immediately
jumps to the page of that number. The view displays the first or the last page of reports by clicking
or icon. And clicking icon saves reports in CSV format.
The way of viewing reports can be customized. See how it can be done in the following four tips.
4.5.1 Sorting data by column
Sorting data by either ascending or descending order in Report View is straight-forward and easy. A
triangle icon (or an inverted one) marked next to header name when clicking a column header, as
pictured below. The normal triangle icon indicates the current sorting rule of the column is
ascending. To the opposite, the inverted triangle icon says it’s sorted by descending method. Clicking
the column header again changes the sorting order.
Figure 63 Sorting by columns
4.5.2 Showing or hiding columns
By placing the cursor at the top of any column header and clicking the inverted triangle arrow at the
far right of the header, a list of sorting order and columns with header names appears. Shown below,

the list contains Sort Ascending, Sort Descending and Columns. This is another place to select a
specific sorting order of the data in that column. Checking or unchecking a box of header name
conceals or shows data of certain columns in the report view.
Figure 64 Display/Hide columns
4.5.3 Report filters
Clicking any data in column displays an object (a cell or a tile) in the center of Map View right away.
Specific Cells/Tiles among all these data can be found quickly without searching for page by page.
Users can point the cursor on top of Cell ID or Tile ID and click the inverted triangle arrow to call out
the pop-up menu, where in the bottom you will see “Filters” item. Just key in any Cell ID or Tile ID
you want to check in the Filters text field, and the result will appear in the Report pane. The same
action can serve the purpose of finding specific IMSI, too.
Figure 65 Using Filters to find out specific Cell, Tile or Subscriber
4.5.4 Reports drill down
Starting using CovMo user apply the KPI and Top level Report is opened. It may be Call Tab or Tile
Tab, depending on type of KPI. In order to get more details on the rows in the report user can trigger
a switch to higher granularity report by double-clicking on the row.

Double-clicking any row in Cell or Tile report turns the Report View to the Subscriber tab, which
provides details of subscriber activity on the cell or tile. Double-clicking any data in the Subscriber
tab opens Detail tab with more detailed information.
In case even deeper analysis is needed, more details can be found in Call Analysis window. The pop-
up window appears after double clicking on individual call in Detail Tab. In this window all Layer 3
messages, all events, processes and time stamps that the transmission has gone through may be
found in a chronological way. It also shows the content of source data input.
See the showcase in the following pictures.
Double Click from Cell/Tile ➔
Figure 66 Subscriber Report
Click on Details tab ➔
Figure 67 Detail Report
By double-clicking a call, call analysis with call sequence will open

Figure 68 Sequence Chart in the Call Analysis window
Figure 69 Events view in the Call Analysis window

Figure 70 Detail view in the Call Analysis window

4.5.5 Filtering protocol filter and causes
Call Cause can be filtered from the Failure Call - Protocol Failure Event. There are RRC, S1, X2 Causes
available.
Figure 71 Protocol Failure Event KPI
Figure 72 RRC Messages are available from RRC drop down list
Once you select S1 or X2, you can find the detailed causes available for selection and filtering.

Figure 73 S1AP Failure Type
Figure 74 S1AP Causes List

S1AP Cases and definition can be found in the following tables:
Radio Network Layer Cause Meaning

Unspecified Sent for radio network layer cause when none of the
specified cause values applies
TX2RELOCOverall Expiry The timer guarding the handover that takes place over X2
has abnormally expired.
Successful Handover Successful handover.
Release due to E-UTRAN Release is initiated due to E-UTRAN generated reason.
generated reason
Handover Cancelled The reason for the action is cancellation of Handover
Partial Handover Provides a reason for the handover cancellation. The
HANDOVER COMMAND message from MME contained E-
RABs to Release List IE and the source eNB estimated
service continuity for the UE would be better by not
proceeding with handover towards this particular target
eNB.
Handover Failure In Target The handover failed due to a failure in target EPC/eNB or
EPC/eNB Or Target System target system.
Handover Target not Handover to the indicated target cell is not allowed for the
allowed UE in question.
TS1RELOCoverall Expiry The reason for the action is expiry of timer TS1RELOCoverall.
TS1RELOCprep Expiry Handover Preparation procedure is cancelled when timer
TS1RELOCprep expires.
Cell not available The concerned cell is not available.
Unknown Target ID Handover rejected because the target ID is not known to
the EPC.
No radio resources Load on target cell is too high.
available in target cell
Unknown or already The action failed because the MME UE S1AP ID is either
allocated MME UE S1AP ID unknown, or (for a first message received at the eNB) is
known and already allocated to an existing context.
Unknown or already The action failed because the eNB UE S1AP ID is either
allocated eNB UE S1AP ID unknown, or (for a first message received at the MME) is
known and already allocated to an existing context.
Unknown or inconsistent The action failed because both UE S1AP IDs are unknown,
pair of UE S1AP ID or are known but do not define a single UE context.
Handover Desirable for The reason for requesting handover is radio related.
Radio Reasons
Time Critical Handover handover is requested for time critical reason i.e., this
cause value is reserved to represent all critical cases where
the connection is likely to be dropped if handover is not
performed.
Resource Optimisation The reason for requesting handover is to improve the load
Handover distribution with the neighbour cells.
Reduce Load in Serving Cell Load on serving cell needs to be reduced.
User Inactivity The action is requested due to user inactivity on all E-RABs,
e.g., S1 is requested to be released in order to optimise the

radio resources.
Radio Connection With UE The action is requested due to loosing the radio
Lost connection to the UE.
Load Balancing TAU The action is requested for all load balancing and offload
Required cases in the MME.
CS Fallback triggered The action is due to a CS fallback that has been triggered.
When it is included in UE CONTEXT RELEASE REQUEST
message, it indicates the PS service suspension is not
required in the EPC.
UE Not Available for PS The action is requested due to a CS fallback to GERAN that
Service has been triggered.
When it is included in the UE CONTEXT RELEASE REQUEST
message, it indicates that the PS service suspension is
required in the EPC due to the target GERAN cell or the UE
has no DTM capability.
Radio resources not No requested radio resources are available
available
Invalid QoS combination The action was failed because of invalid QoS combination.
Inter-RAT Redirection The release is requested due to inter-RAT redirection.
When it is included in UE CONTEXT RELEASE REQUEST
message, it indicates the PS service suspension is not
required in the EPC.
Failure in the Radio Radio interface procedure has failed
Interface Procedure
Interaction with other The action is due to an ongoing interaction with another
procedure procedure
Unknown E-RAB ID The action failed because the E-RAB ID is unknown in the
eNB
Multiple E-RAB ID The action failed because multiple instance of the same E-
Instances RAB had been provided to the eNB
Encryption and/or integrity The eNB is unable to support any of the encryption and/or
protection algorithms not integrity protection algorithms supported by the UE.
supported
S1 Intra system Handover The action is due to a S1 intra system handover that has
triggered been triggered.
S1 Inter system Handover The action is due to a S1 inter system handover that has
triggered been triggered.
X2 Handover triggered The action is due to an X2 handover that has been
triggered.
Redirection towards 1xRTT The release of the UE-associated logical S1 connection is
requested due to redirection towards a 1xRTT system e.g.,
CS fallback to 1xRTT, or SRVCC to 1xRTT, when the PS
service suspension is required in the EPC. During this
procedure, the radio interface message might but need not
include redirection information.
Not supported QCI Value The E-RAB setup failed because the requested QCI is not
supported.
Invalid CSG Id The CSG ID provided to the target eNB was found invalid.

Table 7 S1AP Radio Network Layer Cause
Transport Layer Cause Meaning

Transport Resource The required transport resources are not available
Unavailable
Unspecified Sent when none of the above cause values applies but still
the cause is Transport Network Layer related
Table 8 S1AP Transport Layer Cause
NAS Cause Meaning

Normal Release The release is normal
Authentication Failure The action is due to authentication failure.
Detach The action is due to detach.
the cause is NAS related
CSG Subscription Expiry The action is due to the UE becoming a non-member of the
currently used CSG.
Table 9 S1AP NAS Cause
Protocol Cause Meaning

Transfer Syntax Error The received message included a transfer syntax error.
Abstract Syntax Error The received message included an abstract syntax error
(Reject) and the concerning criticality indicated “reject”.
Abstract Syntax Error The received message included an abstract syntax error
(Ignore and Notify) and the concerning criticality indicated “ignore and notify”.
Message Not Compatible The received message was not compatible with the
with Receiver State receiver state.
Semantic Error The received message included a semantic error.
Abstract Syntax Error The received message contained IEs or IE groups in wrong
(Falsely Constructed order or with too many occurrences.
Message)
the cause is Protocol related
Table 10 S1AP Protocol Cause

Miscellaneous Cause Meaning
Control Processing Control processing overload
Overload
Not Enough User Plane No enough resources are available related to user plane
Processing Resources processing.
Available
Hardware Failure Action related to hardware failure
O&M Intervention The action is due to O&M intervention.
Unspecified Failure Sent when none of the above cause values applies and the
cause is not related to any of the categories Radio Network
Layer, Transport Network Layer, NAS or Protocol.
Unknown PLMN The MME does not identify any PLMN provided by the eNB
Table 11 S1AP Miscellaneous Cause
X2AP Causes are available like the following:
Figure 75 X2AP Failure Type

Figure 76 X2AP Causes List
X2AP Cases and meaning description can be found in the following table:
Radio Network Layer Meaning

Cause
Cell not Available The concerned cell is not available.
Handover Desirable for The reason for requesting handover is radio related.
Radio Reasons
Handover Target not Handover to the indicated target cell is not allowed for the UE
Allowed in question
Invalid MME Group ID The target eNB doesn’t belong to the same pool area of the
source eNB i.e. S1 handovers should be attempted instead.
No Radio Resources The target cell doesn’t have sufficient radio resources
Available in Target Cell available.

Partial Handover Provides a reason for the handover cancellation. The target
eNB did not admit all E-RABs included in the HANDOVER
REQUEST and the source eNB estimated service continuity for
the UE would be better by not proceeding with handover
towards this particular target eNB.
Resource Optimisation The reason for requesting handover is to improve the load
Handover distribution with the neighbour cells.
Time Critical Handover handover is requested for time critical reason i.e. this cause
value is reserved to represent all critical cases where the
connection is likely to be dropped if handover is not
performed.
TX2RELOCoverall Expiry The reason for the action is expiry of timer TX2RELOCoverall
TRELOCprep Expiry Handover Preparation procedure is cancelled when timer
TRELOCprep expires.
Unknown MME Code The target eNB belongs to the same pool area of the source
eNB and recognizes the MME Group ID. However, the MME
Code is unknown to the target eNB.
Unknown New eNB UE The action failed because the New eNB UE X2AP ID is unknown
X2AP ID
Unknown Old eNB UE X2AP The action failed because the Old eNB UE X2AP ID is unknown
ID
Unknown Pair of UE X2AP The action failed because the pair of UE X2 AP IDs is unknown
ID
Encryption And/Or The target eNB is unable to support any of the encryption
Integrity Protection and/or integrity protection algorithms supported by the UE.
Algorithms Not Supported
ReportCharacteristicsEmpty The action failed because there is no characteristic reported.
NoReportPeriodicity The action failed because the periodicity is not defined.
ExistingMeasurementID The action failed because measurement-ID is already used.
Unknown eNB The action failed because some eNB Measurement-ID is
Measurement ID unknown.
Measurement Temporarily The eNB can temporarily not provide the requested
not Available measurement object.
Load Balancing The reason for mobility settings change is load balancing.
Handover Optimisation The reason for mobility settings change is handover
optimisation.
Value out of allowed range The action failed because the proposed Handover Trigger
parameter change in the eNB2 Proposed Mobility Parameters
IE is too low or too high.
Multiple E-RAB ID Instances The action failed because multiple instances of the same E-
RAB had been provided to the eNB.
Switch Off Ongoing The reason for the action is an ongoing switch off i.e. the
concerned cell will be switched off after offloading and not be
available. It aides the receiving eNB in taking subsequent
actions, e.g. selecting the target cell for subsequent
handovers.
Not supported QCI value The action failed because the requested QCI is not supported

Unspecified Sent when none of the above cause values applies but still the
cause is Radio Network Layer related
Measurement not At least one of the concerned cell(s) does not support the
Supported For The Object requested measurement.
Table 12 X2AP Radio Network Layer Cause
Transport Network Meaning

Layer Cause
Transport resource The required transport resources are not available
unavailable
cause is Transport Network Layer related
Table 13 X2AP Transport Network Layer Cause
Protocol cause Meaning

Abstract Syntax Error The received message included an abstract syntax error and
(Reject) the concerned criticality indicated "reject"
Abstract Syntax Error The received message included an abstract syntax error and
(Ignore and Notify) the concerned criticality indicated "ignore and notify"
Abstract syntax error The received message contained IEs or IE groups in wrong
(falsely constructed order or with too many occurrences
message)
Message not Compatible The received message was not compatible with the receiver
with Receiver State state
Semantic Error The received message included a semantic error
Transfer Syntax Error The received message included a transfer syntax error
cause is Protocol related
Table 14 X2AP Protocol Cause
Miscellaneous Cause Meaning

Control Processing eNB control processing overload
Overload
Hardware Failure eNB hardware failure
Not enough User Plane eNB has insufficient user plane processing resources available

Processing Resources
O&M Intervention Operation and Maintenance intervention related to eNB

equipment
Unspecified Sent when none of the above cause values applies and the
cause is not related to any of the categories Radio Network
Layer, Transport Network Layer or Protocol.
Table 15 X2AP Miscellaneous Cause
UMTS RNAP Cause Codes,
Radio Network Layer cause Meaning

The action failed because RNC is not able to provide requested
Deciphering Keys Not Available
deciphering keys.
Conflict with already existing The action was not performed due to that the requested security mode
Integrity protection and/or Ciphering configuration was in conflict with the already existing security mode
information configuration.
Condition Violation For Guaranteed The action was not performed due to condition violation for guaranteed
Bit Rate bit rate.
Condition Violation For SDU The action was not performed due to condition violation for SDU
Parameters parameters.
Condition Violation For Traffic The action was not performed due to condition violation for traffic
Handling Priority handling priority.
Dedicated Assistance data Not The action failed because RNC is not able to successfully deliver the
Available requested dedicated assistance data to the UE.
Directed Retry The reason for action is Directed Retry
Failure In The Radio Interface
Radio interface procedure has failed.
Procedure
Incoming Relocation Not Supported The incoming relocation cannot be accepted by the target RNC because of
Due To PUESBINE Feature the PUESBINE feature.
Interaction With Other Procedure Relocation was cancelled due to interaction with other procedure.
Invalid RAB ID The action failed because the RAB ID is unknown in the RNC.
Invalid RAB Parameters Combination The action failed due to invalid RAB parameters combination.
Invalid RAB Parameters Value The action failed due to invalid RAB parameters value.
Iu UP Failure The action failed due to Iu UP failure.
No remaining RAB The reason for the action is no remaining RAB.
RAB Pre-empted The reason for the action is that RAB is pre-empted.
Radio Connection With UE Lost The action is requested due to losing radio connection to the UE
Release Due To UE Generated
Release requested due to UE generated signalling connection release.
Signalling Connection Release
Release Due To UTRAN Generated
Release is initiated due to UTRAN generated reason.
Reason
Relocation Cancelled The reason for the action is relocation cancellation.
Relocation Desirable for Radio
The reason for requesting relocation is radio related.
Reasons
Relocation Failure In Target CN/RNC
Relocation failed due to a failure in target CN/RNC or target system.
Or Target System

Relocation Not Supported In Target Relocation failed because relocation was not supported in target RNC or
RNC Or Target System target system.
Relocation to the indicated target cell is not allowed for the UE in
Relocation Target not allowed
question.
Relocation Triggered The action failed due to relocation.
Repeated Integrity Checking Failure The action is requested due to repeated failure in integrity checking.
Request Superseded The action failed because there was a second request on the same RAB.
Requested Ciphering And/Or
The UTRAN or the UE is unable to support the requested ciphering and/or
Integrity Protection Algorithms Not
integrity protection algorithms.
Supported
Requested Guaranteed Bit Rate For The action failed because requested guaranteed bit rate for DL is not
DL Not Available available.
Requested Guaranteed Bit Rate For The action failed because requested guaranteed bit rate for UL is not
UL Not Available available.
Requested Guaranteed Bit Rate Not
The action failed because requested guaranteed bit rate is not available.
Available
Requested Information Not Available The action failed because requested information is not available.
Requested Maximum Bit Rate For DL The action failed because requested maximum bit rate for DL is not
Not Available available.
Requested Maximum Bit Rate For UL The action failed because requested maximum bit rate for UL is not
Not Available available.
Requested Maximum Bit Rate Not
The action failed because requested maximum bit rate is not available.
Available
The RNC is not supporting the requested location request type either
Requested Request Type Not
because it doesn’t support the requested event or it doesn’t support the
Supported
requested report area.
The action was not performed due to an inability to support location
Location Reporting Congestion
reporting caused by overload.
Requested Traffic Class Not Available The action failed because requested traffic class is not available.
Requested Transfer Delay Not
The action failed because requested transfer delay is not achievable.
Achievable
Resource Optimisation Relocation The reason for requesting relocation is resource optimisation.
Successful Relocation The reason for the action is completion of successful relocation.
Relocation is requested for time critical reason i.e. this cause value is
Time Critical Relocation reserved to represent all critical cases where the connection is likely to be
dropped if relocation is not performed.
TQUEUING Expiry The action failed due to expiry of the timer TQUEUING.
Relocation Resource Allocation procedure failed due to expiry of the timer
TRELOCalloc Expiry
TRELOCalloc.
TRELOCcomplete Expiry The reason for the action is expiry of timer TRELOCcomplete.
TRELOCoverall Expiry The reason for the action is expiry of timer TRELOCoverall.
Relocation Preparation procedure is cancelled when timer TRELOCprep
TRELOCprep Expiry
expires.
Unable To Establish During RAB failed to establish during relocation because it cannot be supported
Relocation in the target RNC or the RAB did not exist in the source RNC.
Unknown Target RNC Relocation rejected because the target RNC is not known to the CN.
The action is requested due to user inactivity on one or several non real
User Inactivity
time RABs e.g. in order to optimise radio resource.
The action failed because requested user plane versions were not
User Plane Versions Not Supported
supported.
RNC couldn’t establish all RAB subflow combinations indicated within the
RNC unable to establish all RFCs
RAB Parameters IE.

No Radio Resources Available in
Load on target cell is too high.
Target Cell
The RAB establishment/modification/relocation failed because the GERAN
GERAN Iu-mode failure BSC cannot provide an appropriate RAB due to limited capabilities within
GERAN.
Access Restricted Due to Shared
Access is not permitted in the cell due to Shared Networks.
Networks
Traffic Load In The Target Cell Higher Relocation to reduce load in the source cell is rejected, as the target cell’s
Than In The Source Cell traffic load is higher than that in the source cell.
MBMS - No Multicast Service For The request for the Multicase Service list of one UE was not fulfilled
This UE because the UE does not have any active multicast service.
The request for the Multicase Service list of one UE was not fulfilled
MBMS - Unknown UE ID
because the CN does not know the UE.
Successful MBMS Session Start - No The MBMS Session Start procedure was successfully performed, but the
Data Bearer Necessary RNC does not have any interested UE.
The MBMS Session Start procedure was rejected because of successful
MBMS - Superseded Due To NNSF
operation towards another CN node.
The UE linking failed, because the UE has already been linked to the given
MBMS - UE Linking Already Done
Multicast service.
MBMS - UE De-Linking Failure - No The UE de-linking failed, because the UE had not been linked to the given
Existing UE Linking Multicast service.
The requested MBMS action failed because the indicated TMGI is
TMGI Unknown
unknown.
Successful MBMS Session Start – IP
The RNC was able to join the indicated IP Multicast Group.
Multicast Bearer established
Radio Network Layer cause
Meaning
extension
IP Multicast Address And APN Not The MBMS registration failed because the IP Multicast Address and APN
Valid are not valid.
MBMS De-Registration Rejected Due
The MBMS De-registration was rejected because of implicit registration.
To Implicit Registration
The MBMS Registration or De-registration was superseded due to another
MBMS - Request Superseded
ongoing procedure.
MBMS De-Registration During
The MBMS De-registration is not allowed during the MBMS session.
Session Not Allowed
MBMS - No Data Bearer Necessary The RNC no longer have any UEs interested in the MBMS data bearer.
Periodic Location Information not No UE position estimate was available when the periodic report was
Available triggered.
The RNC initiates RAB Release Request procedure with this error cause
GTP Resources Unavailable
value if it received a GTP-U error indication.
The RNC has an MBMS Session up and running with that TMGI, a parallel
TMGI in Use and overlapping MBMS
MBMS session with the same TMGI in another overlapping MBMS Service
Service Area
Area is not allowed.
MBMS - No Cell in MBMS Service
The RNC does not have any cell of the indicated MBMS Service Area.
Area
The relocation is triggered by CS call and the source RNC has no Iu CS user
No Iu CS UP relocation
plane.
CS Fallback triggered The relocation was triggered for CS Fallback reason at the source side.
Transport Layer cause Meaning

Iu Transport Connection Failed to The action failed because the Iu Transport Network Layer connection
Establish could not be established.

Signalling Transport Resource Failure Signalling transport resources have failed (e.g. processor reset).
NAS cause Meaning

Normal Release The release is normal.
A location report is generated due to entering a classified area set by
User Restriction Start Indication
O&M.
User Restriction End Indication A location report is generated due to leaving a classified area set by O&M.

The received message included an abstract syntax error and the
Abstract Syntax Error (Reject)
concerning criticality indicated "reject".
Abstract Syntax Error (Ignore And The received message included an abstract syntax error and the
Notify) concerning criticality indicated "ignore and notify".
Abstract Syntax Error (Falsely The received message contained IEs or IE groups in wrong order or with
Constructed Message) too many occurrences.
Message Not Compatible With
The received message was not compatible with the receiver state.
Receiver State
Semantic Error The received message included a semantic error.
Transfer Syntax Error The received message included a transfer syntax error.
Miscellaneous cause Meaning

Network Optimisation The action is performed for network optimisation.
No Resource Available No requested resource is available.
O&M Intervention The action is due to O&M intervention.
Unspecified Failure Sent when none of the specified cause values applies.
UMTS RNSAP Cause Codes,
Cell not Available The concerned cell is not available

Cell reserved for operator use The concerned cell is reserved for operator use
Cell Specific Tx Diversity Handling For Cell specific tx diversity handling for multi cell operation not available in the
Multi Cell Operation Not Available concerned cell(s)
Cell Specific Tx Diversity Handling For The concerned cell(s) do not support the cell specific tx diversity handling for multi
Multi Cell Operation Not Supported cell operation
CM not Supported The concerned cell(s) do not support Compressed Mode
Combining not Supported The DRNS does not support the RL combining for the concerned cells
Combining Resources Not Available The value of the received Diversity Control Field IE was set to “Must”, but the
DRNS cannot perform the requested combining
Common Transport Channel Type not The concerned cell(s) do not support the RACH and/or FACH Common Transport
Supported Channel Type
Continuous Packet Connectivity DTX-DRX CPC resources for DTX-DRX operation not available in the concerned cell(s).
operation not available
Continuous Packet Connectivity DRX not HSPA resources for DRX operation not available in the concerned cell(s). (for
available 1.28Mcps TDD only)
Continuous Packet Connectivity DRX not The concerned cell(s) do not support the Continuous Packet Connectivity DRX
supported operation (for 1.28Mcps TDD only)
Continuous Packet Connectivity DTX-DRX The concerned cell(s) do not support the Continuous Packet Connectivity DTX-DRX
operation not Supported operation

Continuous Packet Connectivity HS-SCCH The concerned cell(s) do not support the Continuous Packet Connectivity HS-SCCH
less operation not Supported less operation
Continuous Packet Connectivity UE DTX CPC resources for the UE DTX Cycle not available in the concerned cell(s).
Cycle not available
Dedicated Transport Channel Type not The concerned cell(s) do not support the Dedicated Transport Channel Type
Supported
Delayed Activation not Supported The concerned cell(s) do not support delayed activation of RLs
Directed Retry The reason for action is Directed Retry
DL Radio Resources not Available The DRNS does not have sufficient DL radio resources available
DL SF not Supported The concerned cell(s) do not support the requested DL SF
DL Shared Channel Type not Supported The concerned cell(s) do not support the Downlink Shared Channel Type
DPC Mode Change not Supported The concerned cells do not support the DPC mode changes
E-DCH MAC-d PDU Size Format not The selected E-DCH MAC-d PDU Size Format is not available in the concerned
available cell(s).
E-DCH not supported The concerned cell(s) do not support E-DCH
E-DCH TTI2ms not supported The concerned cell(s) do not support the E-DCH 2ms TTI operation
E-DPCCH Power Boosting not supported The concerned cell(s) do not support the E-DPCCH Power Boosting.
Enhanced Relocation not Supported The DRNS does not support the Enhanced Relocation.
F-DPCH not supported The concerned cell(s) do not support the Fractional DPCH
F-DPCH Slot Format operation not The concerned cell(s) do not support the F-DPCH Slot Format operation
supported
Frequency Specific Compressed Mode Frequency Specific Compressed Mode is not available in the concerned cell(s)
not available
HS-DSCH MAC-d PDU Size Format not The concerned cell(s) do not support the selected HS-DSCH MAC-d PDU Size
supported Format
Information Provision not supported for The RNS doesn’t support provision of the requested information for the
the object concerned object types
Information temporarily not available The RNS can temporarily not provide the requested information
Invalid CM Settings The concerned cell(s) consider the requested Compressed Mode settings invalid
Measurement not Supported For The At least one of the concerned cell(s) does not support the requested
Object measurement on the concerned object type
Measurement Repetition Rate not The requested parameters for a forwarded UE measurement are not compatible
Compatible with Current Measurements with the current measurement schedule in the SRNC.
Measurement Temporarily not Available The DRNS can temporarily not provide the requested measurement value
MIMO not available MIMO resources not available in the concerned cell(s).
MIMO not supported The concerned cell(s) do not support the MIMO operation
Multi Cell E-DCH operation not available Multi cell E-DCH operation is not available in the concerned cell(s).
Multi Cell E-DCH operation not The concerned cell(s) do not support Multi cell E-DCH operation
supported
Multi Cell operation not available Multi Cell operation resources not available in the concerned cell(s).
Multi Cell operation not supported The concerned cell(s) do not support Multi Cell operation
Multi Cell operation with MIMO not Multi Cell operation with MIMO resources not available in the concerned cell(s).
available
Multi Cell operation with MIMO not The concerned cell(s) do not support Multi Cell operationwith MIMO
supported
Multi Cell operation with Single Stream Multi Cell operation with Single Stream MIMO resources not available in the
MIMO not available concerned cell(s).
Multi Cell operation with Single Stream The concerned cell(s) do not support Multi Cell operationwith Single Stream
MIMO not supported MIMO
No Iu CS UP relocation The relocation is triggered by CS call and the source RNC has no Iu CS user plane.
Number of DL Codes not Supported The concerned cell(s) do not support the requested number of DL codes
Number of UL Codes not Supported The concerned cell(s) do not support the requested number of UL codes

Power Balancing status not compatible The power balancing status in the SRNC is not compatible with that of the DRNC.
Power Level not Supported A DL power level was requested which the concerned cell(s) do not support
Reconfiguration CFN not Elapsed The requested action cannot be performed due to that a COMMIT message was
received previously, but the concerned CFN has not yet elapsed
Reconfiguration not Allowed The SRNC does currently not allow the requested reconfiguration
Relocation Cancelled The reason for the action is relocation cancellation.
Relocation Desirable For Radio Reasons The reason for requesting relocation is radio related.
Relocation Failure In Target RNC Relocation failed due to a failure in target RNC.
Relocation Not Supported Due To The DRNS can not support the relocation due to the PUESBINE Feature.
PUESBINE Feature
Relocation Target not allowed Relocation to the indicated target cell is not allowed for the UE in question.
Requested Ciphering And/Or Integrity The DRNS does not support the requested ciphering and/or integrity protection
Protection Algorithms Not Supported algorithms.
Requested Configuration not Supported The concerned cell(s) do not support the requested configuration i.e. power
levels, Transport Formats, physical channel parameters,…..
Requested Tx Diversity mode not The concerned cell(s) do not support the requested transmit diversity mode
Supported
Resource Optimisation Relocation The reason for requesting relocation is resource optimisation.
RL Already Activated/ Allocated The DRNS has already allocated an RL with the requested RL ID for this UE Context
RL Timing Adjustment not Supported The concerned cell(s) do not support adjustments of the RL timing
Semi-Persistent scheduling not The concerned cell(s) do not support the Semi-Persistent scheduling operation
supported (for 1.28Mcps TDD only)
SixteenQAM UL not Supported The concerned cell(s) do not support the 16 QAM UL
SixtyfourQAM DL and MIMO Combined SixtyfourQAM DL and MIMO Combined not available in the concerned cell(s)
not available
SixtyfourQAM DL and MIMO Combined The DRNS does not support SixtyfourQAM DL and MIMO Combined for the
not supported concerned cells.
Synchronisation Failure Loss of UL Uu synchronisation
Time Critical Relocation Relocation is requested for time critical reason i.e. this cause value is reserved to
represent all critical cases where the connection is likely to be dropped if
relocation is not performed.
Traffic Load In The Target Cell Higher Relocation to reduce load in the source cell is rejected, as the target cell’s traffic
Than In The Source Cell load is higher than that in the source cell.
Transaction not Supported by The requested action cannot be performed due to lack of support of the
Destination Node B corresponding action in the destination Node B
TRELOCprep Expiry Relocation Preparation procedure is cancelled when timer TRELOCprep expires.
Single Stream MIMO not supported The concerned cell(s) do not support the Single Stream MIMO.
Single Stream MIMO not available Single Stream MIMO resources not available in the concerned cell(s).
TX diversity for MIMO UE on DL Control The DRNS does not have sufficient radio resources available to support transmit
Channels not available diversity on downlink control channels when the UE is configured in MIMO mode
with P-CPICH & S-CPICH as phase references (TS 25.211 [8])
UE not Capable to Implement The UE is not capable to initiate/report a requested measurement due to its
Measurement current state or capabilities.
UL Radio Resources not Available The DRNS does not have sufficient UL radio resources available
UL Scrambling Code Already in Use The concerned UL scrambling code is already in use for another UE
UL SF not Supported The concerned cell(s) do not support the requested minimum UL SF
UL Shared Channel Type not Supported The concerned cell(s) do not support the Uplink Shared Channel Type
Unknown C-ID The DRNS is not aware of a cell with the provided C-ID
Unknown RNTI The SRNC or DRNC is not aware of a UE indicated with the provided RNTI
Unspecified Sent when none of the above cause values applies but still the cause is Radio
Network Layer related

Transport Network Layer cause Meaning
Transport resource unavailable The required transport resources are not available
Unspecified Sent when none of the above cause values applies but still the cause is Transport
Network Layer related

Abstract Syntax Error (Reject) The received message included an abstract syntax error and the concerned
criticality indicated “reject” (see subclause 10.3)
Abstract Syntax Error (Ignore and Notify) The received message included an abstract syntax error and the concerned
criticality indicated “ignore and notify” (see subclause 10.3)
Abstract syntax error (falsely constructed The received message contained IEs or IE groups in wrong order or with too many
message) occurrences (see subclause 10.3)
Message not Compatible with Receiver The received message was not compatible with the receiver state (see subclause
State 10.4)
Semantic Error The received message included a semantic error (see subclause 10.4)
Transfer Syntax Error The received message included a transfer syntax error (see subclause 10.2)
Unspecified Sent when none of the above cause values applies but still the cause is Protocol
related

Control Processing Overload DRNS control processing overload
Hardware Failure DRNS hardware failure
Not enough User Plane Processing DRNS has insufficient user plane processing resources available
Resources
O&M Intervention Operation and Maintenance intervention related to DRNS equipment
Unspecified Sent when none of the above cause values applies and the cause is not related to
any of the categories Radio Network Layer, Transport Network Layer or Protocol.
UMTS NBAP Cause Codes,
BCCH scheduling error The Node B has detected an illegal BCCH schedule update (see subclause
8.2.16.3).
Bearer Re-arrangement needed The Node B cannot perform the requested Radio Link Reconfiguration
without bearer re-arrangement.
Cell not Available The concerned cell or local cell is not available.
Cell Synchronisation not supported The concerned cell(s) do not support Cell Synchronisation.
Cell Specific Tx Diversity Handling For Cell specific tx diversity handling for multi cell operation not available in
Multi Cell Operation Not Available the concerned cell(s)
Combining not supported The Node B does not support RL combining for the concerned cells.
Combining Resources Not Available The value of the received Diversity Control Field IE was set to "Must", but
the Node B cannot perform the requested combining.
CM not supported The concerned cell(s) do not support Compressed Mode.
Common Transport Channel Type The concerned cell(s) do not support the RACH and/or FACH Common
not supported Transport Channel Type.

Continuous Packet Connectivity CPC resources for DTX-DRX operation not available in the concerned
DTX-DRX operation not available cell(s).
Continuous Packet Connectivity UE CPC resources for the UE DTX Cycle not available in the concerned cell(s).
DTX Cycle not available
Dedicated Transport Channel Type The concerned cell(s) do not support the Dedicated Transport Channel
not supported Type.
Delayed Activation not Supported The concerned cell(s) do not support delayed activation of RLs.
DL Radio Resources not Available The Node B does not have sufficient DL radio resources available.
DL SF not supported The concerned cell(s) do not support the requested DL SF.
DL Shared Channel Type not The concerned cell(s) do not support the Downlink Shared Channel Type.
supported
DPC Mode Change not Supported The concerned cells do not support DPC mode changes.
E-DCH MAC-d PDU Size Format not The selected E-DCH MAC-d PDU Size Format is not available in the
available concerned cell(s).
Frequency Acquisition not supported The concerned cell(s) do not support Frequency Acquisition.
F-DPCH not supported The concerned cell(s) do not support the Fractional DPCH
Information Provision not supported The requested information provision is not supported for the concerned
for the object object types.
Information temporarily not The requested information can temporarily not be provided.
available
Invalid CM Settings The concerned cell(s) consider the requested Compressed Mode settings
invalid.
IPDL already activated The concerned cell(s) have already active IPDL ongoing.
IPDL not supported The concerned cell(s) do not support the IPDL.
IPDL parameters not available The concerned cell(s) do not have IPDL parameters defining IPDL to be
applied.
Measurement not Supported For The At least one of the concerned cell(s) does not support the requested
Object measurement on the concerned object type.
Measurement Temporarily not The Node B can temporarily not provide the requested measurement
Available value.
MICH not supported The concerned cell does not support MICH.
MIMO not available MIMO resources not available in the concerned cell(s).
Modificaton Period not available The Node B does not have modification period available.
Multi Cell operation not available Multi Cell operation resources not available in the concerned cell(s)
Multi Cell operation with MIMO not Multi Cell operation resources with MIMO not available in the concerned
available cell(s)
Multi Cell operation with Single Multi Cell operation resources with Single Stream MIMO not available in
Stream MIMO not available the concerned cell(s)
Multi Cell E-DCH operation not Multi Cell E-DCH operation resources not available in the concerned cell(s)
available
Node B resources unavailable The Node B does not have sufficient resources available.
Number of DL codes not supported The concerned cell(s) do not support the requested number of DL codes.
Number of UL codes not supported The concerned cell(s) do not support the requested number of UL codes.
Power Level not Supported A DL power level was requested which the concerned cell(s) do not
support.
Power Balancing status not The power balancing status in the SRNC is not compatible with that of the
compatible Node B.
PLCCH not supported The concerned cell does not support PLCCH.

Priority transport channel The CRNC cannot perform the requested blocking since a transport
established channel with a high priority is present.
RL Timing Adjustment not Supported The concerned cell(s) do not support adjustments of the RL timing.
Reconfiguration CFN not elapsed The requested action cannot be performed due to that a RADIO LINK
RECONFIGURATION COMMIT message was received previously, but the
concerned CFN has not yet elapsed.
Requested Configuration not The concerned cell(s) do not support the requested configuration i.e.
Supported power levels, Transport Formats, physical channel parameters.
Requested Type of Bearer Re- The Node B does not support the requested type of bearer re-
arrangement not supported arrangement.
Requested Tx Diversity mode not The concerned cell(s) do not support the requested transmit diversity
supported mode.
RL already Activated/ allocated The Node B has already allocated an RL with the requested RL-id for this
UE context.
S-CPICH not supported The concerned cell(s) do not support S-CPICH.
S-CPICH power offset support not The support for setting up the desired power offset on S-CPICH with
available respect to P-CPICH is not available
SIB Orgination in Node B not The Node B does not support the origination of the requested SIB for the
Supported concerned cell.
Signalling Bearer Re-arrangement The Node B does not support the Signalling bearer re-arrangement.
not supported
Single Stream MIMO not available Single Stream MIMO resources not available in the concerned cell(s).
SixtyfourQAM DL and MIMO SixtyfourQAM DL and MIMO Combined not available in the concerned
Combined not available cell(s).
Synchronisation Failure Loss of UL Uu synchronisation.
Cell Synchronisation Adjustment not The concerned cell(s) do not support Cell Synchronisation Adjustment.
supported
TX diversity for MIMO UE on DL The Node B does not have sufficient radio resources available to support
Control Channels not available transmit diversity on downlink control channels when the UE is configured
in MIMO mode with P-CPICH & S-CPICH as phase references (TS 25.211
[7])
Tx diversity no longer supported Tx diversity can no longer be supported in the concerned cell.
UL Radio Resources not Available The Node B does not have sufficient UL radio resources available.
UL SF not supported The concerned cell(s) do not support the requested minimum UL SF.
UL Shared Channel Type not The concerned cell(s) do not support the Uplink Shared Channel Type.
supported
Unknown C-ID The Node B is not aware of a cell with the provided C-ID.
Unknown Local Cell ID The Node B is not aware of a local cell with the provided Local Cell ID
Unspecified Sent when none of the above cause values applies but still the cause is
Radio Network layer related.
Semi-Persistent scheduling not The concerned cell(s) do not support the Semi-Persistent scheduling
supported operation (for 1.28Mcps TDD only)
Continuous Packet Connectivity DRX The concerned cell(s) do not support the Continuous Packet Connectivity
not supported DRX operation (for 1.28Mcps TDD only)
Continuous Packet Connectivity DRX HSPA resources for DRX operation not available in the concerned cell(s).
not available (for 1.28Mcps TDD only)
Transport Network Layer cause Meaning

Transport resource unavailable The required transport resources are not available.

Transport Network layer related.

Abstract Syntax Error (Reject) The received message included an abstract syntax error and the
concerned criticality indicated "reject" (see subclause 10.3).
Abstract Syntax Error (Ignore and The received message included an abstract syntax error and the
Notify) concerned criticality indicated "ignore and notify" (see subclause 10.3).
Abstract syntax error (falsely The received message contained IEs in wrong order or with too many
constructed message) occurrences (see subclause 10.3).
Message not Compatible with The received message was not compatible with the receiver state (see
Receiver State subclause 10.4).
Semantic Error The received message included a semantic error (see subclause 10.4).
Transfer Syntax Error The received message included a transfer syntax error (see subclause
10.2).
protocol related.

Control Processing Overload Node B control processing overload.
Hardware Failure Node B hardware failure.
Not enough User Plane Processing Node B has insufficient user plane processing resources available.
Resources
O&M Intervention Operation and Maintenance intervention related to Node B equipment.
Unspecified Sent when none of the above cause values applies and the cause is not
related to any of the categories Radio Network Layer, Transport Network
Layer or Protocol.
UMTS RRC & NAS release cause codes,
PROTOCOL CAUSE_NAME
RRC Failure Cause/configuration unsupported
RRC Failure Cause/physical channel failure
RRC Failure Cause/incompatible simultaneous reconfiguration
RRC Failure Cause/compressed mode runtime error
RRC Failure Cause/protocol error_ASN.1 violation or encoding error
RRC Failure Cause/protocol error_Message type non-existent or not
implemented
RRC Failure Cause/protocol error_Message not compatible with receiver state
RRC Failure Cause/protocol error_Information element value not
comprehended
RRC Failure Cause/protocol error_Information element missing
RRC Failure Cause/protocol error_Message extension not comprehended
RRC Failure Cause/cell update occurred_cell reselection
RRC Failure Cause/cell update occurred_periodical cell update
RRC Failure Cause/cell update occurred_uplink data transmission

RRC Failure Cause/cell update occurred_paging response
RRC Failure Cause/cell update occurred_re-entered service area
RRC Failure Cause/cell update occurred_radio link failure
RRC Failure Cause/cell update occurred_RLC unrecoverable error
RRC Failure Cause/cell update occurred_MBMS reception
RRC Failure Cause/cell update occurred_MBMS ptp RB request
RRC Failure Cause/invalid configuration
RRC Failure Cause/configuration incomplete
RRC Failure Cause/unsupported measurement
RRC Failure Cause/MBMS session already received correctly
RRC Failure Cause/lower priority MBMS service
RRC Failure Cause/unspecified
RRC Rejection Cause/congestion
RRC Rejection Cause/unspecified
RRC Failure Cause/Due to node B no response
RRC Failure Cause/Due to UE no response
RRC Setup success
RRC I-RAT Hanover Failure Cause/configuration unacceptable
RRC I-RAT Hanover Failure Cause/physical channel failure
RRC I-RAT Hanover Failure Cause/protocol error_ASN.1 violation or encoding
error
RRC I-RAT Hanover Failure Cause/protocol error_Message type non-existent or
not implemented
RRC I-RAT Hanover Failure Cause/protocol error_Message not compatible with
receiver state
RRC I-RAT Hanover Failure Cause/protocol error_Information element value
not comprehended
RRC I-RAT Hanover Failure Cause/protocol error_Information element missing
RRC I-RAT Hanover Failure Cause/protocol error_Message extension not
comprehended
RRC I-RAT Hanover Failure Cause/inter RAT protocol error
RRC I-RAT Hanover Failure Cause/unspecified
NAS_CAUSE_CC NAS_MM&GMM_Protocol error, unspecified
NAS_CAUSE_CC NAS_MM&GMM_IMSI unknown in HLR
NAS_CAUSE_CC NAS_MM&GMM_Illegal MS
NAS_CAUSE_CC NAS_MM&GMM_IMSI unknown in VLR
NAS_CAUSE_CC NAS_MM&GMM_IMEI not accepted
NAS_CAUSE_CC NAS_MM&GMM_Illegal ME
NAS_CAUSE_CC NAS_MM&GMM_GPRS services not allowed
NAS_CAUSE_CC NAS_MM&GMM_GPRS services and non-GPRS services not allowed
NAS_CAUSE_CC NAS_MM&GMM_MS identity cannot be derived by the network
NAS_CAUSE_CC NAS_MM&GMM_Implicitly detached
NAS_CAUSE_CC NAS_MM&GMM_PLMN not allowed
NAS_CAUSE_CC NAS_MM&GMM_Location Area not allowed
NAS_CAUSE_CC NAS_MM&GMM_Roaming not allowed in this location area

NAS_CAUSE_CC NAS_MM&GMM_GPRS services not allowed in this PLMN
NAS_CAUSE_CC NAS_MM&GMM_No Suitable Cells In Location Area
NAS_CAUSE_CC NAS_MM&GMM_MSC temporarily not reachable
NAS_CAUSE_CC NAS_MM&GMM_Network failure
NAS_CAUSE_CC NAS_MM&GMM_MAC failure
NAS_CAUSE_CC NAS_MM&GMM_Synch failure
NAS_CAUSE_CC NAS_MM&GMM_Congestion
NAS_CAUSE_CC NAS_MM&GMM_GSM authentication unacceptable
NAS_CAUSE_CC NAS_MM&GMM_Not authorized for this CSG
NAS_CAUSE_CC NAS_MM&GMM_Service option not supported
NAS_CAUSE_CC NAS_MM&GMM_Requested service option not subscribed
NAS_CAUSE_CC NAS_MM&GMM_Service option temporarily out of order
NAS_CAUSE_CC NAS_MM&GMM_Call cannot be identified
NAS_CAUSE_CC NAS_MM&GMM_No PDP context activated
NAS_CAUSE_CC NAS_MM&GMM_retry upon entry into a new cell

NAS_CAUSE_CC NAS_MM&GMM_Semantically incorrect message
NAS_CAUSE_CC NAS_MM&GMM_Invalid mandatory information
NAS_CAUSE_CC NAS_MM&GMM_Message type non-existent or not implemented
NAS_CAUSE_CC NAS_MM&GMM_Message not compatible with protocol state
NAS_CAUSE_CC NAS_MM&GMM_Information element non-existent or not implemented
NAS_CAUSE_CC NAS_MM&GMM_Conditional IE error
NAS_CAUSE_CC NAS_MM&GMM_Message not compatible with protocol state




NAS_CAUSE_CC NAS_SM_Service option temporarily out of order
NAS_CAUSE_CC NAS_SM_Protocol error, unspecified
NAS_CAUSE_CC NAS_SM_Operator Determined Barring

NAS_CAUSE_CC NAS_SM_MBMS bearer capabilities insufficient for the service
NAS_CAUSE_CC NAS_SM_LLC or SNDCP failure (A/Gb mode only)
NAS_CAUSE_CC NAS_SM_Insufficient resources
NAS_CAUSE_CC NAS_SM_Missing or unknown APN
NAS_CAUSE_CC NAS_SM_Unknown PDP address or PDP type
NAS_CAUSE_CC NAS_SM_User authentication failed
NAS_CAUSE_CC NAS_SM_Activation rejected by GGSN, Serving GW or PDN GW
NAS_CAUSE_CC NAS_SM_Activation rejected, unspecified
NAS_CAUSE_CC NAS_SM_Service option not supported
NAS_CAUSE_CC NAS_SM_Requested service option not subscribed
NAS_CAUSE_CC NAS_SM_NSAPI already used
NAS_CAUSE_CC NAS_SM_Regular deactivation
NAS_CAUSE_CC NAS_SM_QoS not accepted
NAS_CAUSE_CC NAS_SM_Network failure
NAS_CAUSE_CC NAS_SM_Reactivation requested
NAS_CAUSE_CC NAS_SM_Feature not supported
NAS_CAUSE_CC NAS_SM_semantic error in the TFT operation
NAS_CAUSE_CC NAS_SM_syntactical error in the TFT operation
NAS_CAUSE_CC NAS_SM_unknown PDP context
NAS_CAUSE_CC NAS_SM_semantic errors in packet filter(s),
NAS_CAUSE_CC NAS_SM_syntactical error in packet filter(s),
NAS_CAUSE_CC NAS_SM_PDP context without TFT already activated
NAS_CAUSE_CC NAS_SM_Multicast group membership time-out
NAS_CAUSE_CC NAS_SM_Request rejected, Bearer Control Mode violation

NAS_CAUSE_CC NAS_SM_PDP type IPv4 only allowed
NAS_CAUSE_CC NAS_SM_PDP type IPv6 only allowed
NAS_CAUSE_CC NAS_SM_single address bearers only allowed
NAS_CAUSE_CC NAS_SM_Collision with network initiated request
NAS_CAUSE_CC NAS_SM_Bearer handling not supported

NAS_CAUSE_CC NAS_SM_Invalid transaction identifier value
NAS_CAUSE_CC NAS_SM_Semantically incorrect message
NAS_CAUSE_CC NAS_SM_Invalid mandatory information
NAS_CAUSE_CC NAS_SM_Message type non-existent or not implemented
NAS_CAUSE_CC NAS_SM_Message not compatible with protocol state
NAS_CAUSE_CC NAS_SM_Information element non-existent or not implemented

NAS_CAUSE_CC NAS_SM_Conditional IE error
NAS_CAUSE_CC NAS_SM_Message not compatible with protocol state
NAS_CAUSE_CC NAS_SM_restriction value incompatible with active PDP context






NAS_CAUSE_CC NAS_Reject_Service option temporarily out of order
NAS_CAUSE_CC NAS_Reject_Protocol error, unspecified
NAS_CAUSE_CC NAS_Reject_IMSI unknown in HLR
NAS_CAUSE_CC NAS_Reject_Illegal MS
NAS_CAUSE_CC NAS_Reject_IMSI unknown in VLR

NAS_CAUSE_CC NAS_Reject_IMEI not accepted
NAS_CAUSE_CC NAS_Reject_Illegal ME
NAS_CAUSE_CC NAS_Reject_PLMN not allowed
NAS_CAUSE_CC NAS_Reject_Location Area not allowed
NAS_CAUSE_CC NAS_Reject_Roaming not allowed in this location area
NAS_CAUSE_CC NAS_Reject_No Suitable Cells In Location Area
NAS_CAUSE_CC NAS_Reject_Network failure
NAS_CAUSE_CC NAS_Reject_MAC failure
NAS_CAUSE_CC NAS_Reject_Synch failure
NAS_CAUSE_CC NAS_Reject_Congestion
NAS_CAUSE_CC NAS_Reject_GSM authentication unacceptable
NAS_CAUSE_CC NAS_Reject_Not authorized for this CSG
NAS_CAUSE_CC NAS_Reject_Service option not supported
NAS_CAUSE_CC NAS_Reject_Requested service option not subscribed

NAS_CAUSE_CC NAS_Reject_Call cannot be identified
NAS_CAUSE_CC NAS_Reject_retry upon entry into a new cell


NAS_CAUSE_CC NAS_Reject_Semantically incorrect message
NAS_CAUSE_CC NAS_Reject_Invalid mandatory information
NAS_CAUSE_CC NAS_Reject_Message type non-existent or not implemented
NAS_CAUSE_CC NAS_Reject_Message type not compatible with the protocol state
NAS_CAUSE_CC NAS_Reject_Information element non-existent or not implemented
NAS_CAUSE_CC NAS_Reject_Conditional IE error
NAS_CAUSE_CC NAS_Reject_Message not compatible with the protocol state







NAS_CAUSE_CC NAS_CC_normal, unspecified
NAS_CAUSE_CC NAS_CC_normal, unassigned (unallocated), number
NAS_CAUSE_CC NAS_CC_normal, no route to destination
NAS_CAUSE_CC NAS_CC_normal, channel unacceptable
NAS_CAUSE_CC NAS_CC_normal, operator determined barring
NAS_CAUSE_CC NAS_CC_normal call clearing
NAS_CAUSE_CC NAS_CC_normal, user busy
NAS_CAUSE_CC NAS_CC_normal, no user responding
NAS_CAUSE_CC NAS_CC_normal, user alerting, no answer
NAS_CAUSE_CC NAS_CC_normal, call rejected
NAS_CAUSE_CC NAS_CC_normal, number changed
NAS_CAUSE_CC NAS_CC_normal, call rejected due to feature at the destination
NAS_CAUSE_CC NAS_CC_normal, pre-emption
NAS_CAUSE_CC NAS_CC_normal, non-selected user clearing
NAS_CAUSE_CC NAS_CC_normal, destination out of order
NAS_CAUSE_CC NAS_CC_normal, invalid number format (incomplete number)
NAS_CAUSE_CC NAS_CC_normal, facility rejected
NAS_CAUSE_CC NAS_CC_normal, response to STATUS ENQUIRY
NAS_CAUSE_CC NAS_CC_resource unavailable, unspecified

NAS_CAUSE_CC NAS_CC_resource unavailable, no circuit/channel available
NAS_CAUSE_CC NAS_CC_resource unavailable, network out of order
NAS_CAUSE_CC NAS_CC_resource unavailable, temporary failure
NAS_CAUSE_CC NAS_CC_resource unavailable, switching equipment congestion
NAS_CAUSE_CC NAS_CC_resource unavailable, access information discarded
NAS_CAUSE_CC NAS_CC_resource unavailable, requested circuit/channel not available
NAS_CAUSE_CC NAS_CC_service or option not available, unspecified
NAS_CAUSE_CC NAS_CC_service or option not available, quality of service unavailable
NAS_CAUSE_CC NAS_CC_service or option not available, Requested facility not subscribed
NAS_CAUSE_CC NAS_CC_service or option not available, Incoming calls barred within the
CUG
NAS_CAUSE_CC NAS_CC_service or option not available, bearer capability not authorized
NAS_CAUSE_CC NAS_CC_service or option not available, bearer capability not presently
available
NAS_CAUSE_CC NAS_CC_service or option not implemented, unspecified
NAS_CAUSE_CC NAS_CC_service or option not available, bearer service not implemented
NAS_CAUSE_CC NAS_CC_service or option not available, ACM equal to or greater than
ACMmax
NAS_CAUSE_CC NAS_CC_service or option not available, Requested facility not
implemented
NAS_CAUSE_CC NAS_CC_service or option not available, only restricted digital information
bearer capability is available

NAS_CAUSE_CC NAS_CC_invalid message, semantically incorrect message
NAS_CAUSE_CC NAS_CC_invalid message, invalid transaction identifier value
NAS_CAUSE_CC NAS_CC_invalid message, user not member of CUG
NAS_CAUSE_CC NAS_CC_invalid message, incompatible destination
NAS_CAUSE_CC NAS_CC_invalid message, invalid transit network selection
NAS_CAUSE_CC NAS_CC_protocol error, invalid mandatory information
NAS_CAUSE_CC NAS_CC_protocol error, message type non-existent or not implemented
NAS_CAUSE_CC NAS_CC_protocol error, message type not compatible with protocol state
NAS_CAUSE_CC NAS_CC_protocol error, information element protocol error, non-existent
or not implemented
NAS_CAUSE_CC NAS_CC_protocol error, invalid message, conditional IE error
NAS_CAUSE_CC NAS_CC_protocol error, invalid message, message not compatible with
protocol state
NAS_CAUSE_CC NAS_CC_protocol error, recovery on timer expiry
NAS_CAUSE_CC NAS_CC_protocol error, unspecified
NAS_CAUSE_CC NAS_CC_interworking, unspecified

NAS_CAUSE_SM NAS_LU_Normal
NAS_CAUSE_SM NAS_LU_Periodic
NAS_CAUSE_SM NAS_LU_IMSI Attach
NAS_CAUSE_SM NAS_RAU_RA updating
NAS_CAUSE_SM NAS_RAU_Combined RA/LA updating
NAS_CAUSE_SM NAS_RAU_Combined RA/LA updating with IMSI attach
NAS_CAUSE_SM NAS_RAU_Periodic updating
NAS_CAUSE_SM NAS_Attach_GPRS attach
NAS_CAUSE_SM NAS_Attach_GPRS attach while IMSI attached
NAS_CAUSE_SM NAS_Attach_Combined GPRS/IMSI attached
NAS_CAUSE_SM NAS_Detach_Re-attach required
NAS_CAUSE_SM NAS_Detach_Re-attach not required
NAS_CAUSE_SM NAS_Detach_IMSI detach after VLR failure
GSM protocol release cause,
PROTOCOL CAUSE_NAME
BSSMAP Normal event_Radio interface message failure
BSSMAP Normal event_Radio interface failure
BSSMAP Normal event_Uplink quality
BSSMAP Normal event_Uplink strength
BSSMAP Normal event_Downlink quality
BSSMAP Normal event_Downlink strength
BSSMAP Normal event_Distance
BSSMAP Normal event_O and M intervention
BSSMAP Normal event_Response to MSC invocation
BSSMAP Normal event_Call control
BSSMAP Normal event_Radio interface failure, reversion to old channel
BSSMAP Normal event_Handover successful
BSSMAP Normal event_Better Cell
BSSMAP Normal event_Directed Retry
BSSMAP Normal event_Joined group call channel
BSSMAP Normal event_Traffic
BSSMAP Normal event_Reduce load in serving cell
BSSMAP Normal event_Traffic load in target cell higher than in source cell

BSSMAP Normal event_Relocation triggered
BSSMAP Normal event_Unknown
BSSMAP Normal event_Requested option not authorised
BSSMAP Normal event_Alternative channel configuration requested (NOTE)
BSSMAP Normal event_Response to an INTERNAL HANDOVER ENQUIRY message
BSSMAP Normal event_INTERNAL HANDOVER ENQUIRY reject
BSSMAP Normal event_Redundancy Level not adequate
BSSMAP Normal event_Reserved for national use
BSSMAP Resource unavailable_Equipment failure
BSSMAP Resource unavailable_No radio resource available
BSSMAP Resource unavailable_Requested terrestrial resource unavailable
BSSMAP Resource unavailable_CCCH overload
BSSMAP Resource unavailable_Processor overload
BSSMAP Resource unavailable_BSS not equipped
BSSMAP Resource unavailable_MS not equipped
BSSMAP Resource unavailable_Invalid cell
BSSMAP Resource unavailable_Traffic Load
BSSMAP Resource unavailable_Preemption
BSSMAP Resource unavailable_DTM Handover - SGSN Failure
BSSMAP Resource unavailable_DTM Handover - PS Allocation failure
BSSMAP Resource unavailable_Reserved for national use
BSSMAP Service or option not available but implemented_Requested
transcoding/rate adaption unavailable
BSSMAP Service or option not available but implemented_Circuit pool mismatch
BSSMAP Service or option not available but implemented_Switch circuit pool
BSSMAP Service or option not available but implemented_Requested speech
version unavailable
BSSMAP Service or option not available but implemented_LSA not allowed
BSSMAP Service or option not available but implemented_Requested Codec Type
or Codec Configuration unavailable
BSSMAP Service or option not available but implemented_Requested A-Interface
Type unavailable
BSSMAP Service or option not available but implemented_Invalid CSG cell
BSSMAP Service or option not available but implemented_Reserved for
international use
international use

international use
international use
international use
international use
international use
BSSMAP Service or option not available but implemented_Requested Redundancy
Level not available
BSSMAP Service or option not implemented or currently disabled_Ciphering
algorithm not supported
BSSMAP Service or option not implemented or currently disabled_GERAN Iu-mode
failure
BSSMAP Service or option not implemented or currently disabled_Incoming
Relocation Not Supported Due To PUESBINE Feature
BSSMAP Service or option not implemented or currently disabled_Access
Restricted Due to Shared Networks (NOTE)
BSSMAP Service or option not implemented or currently disabled_Requested
Codec Type or Codec Configuration not supported
BSSMAP Service or option not implemented or currently disabled_Requested A-
Interface Type not supported
BSSMAP Service or option not implemented or currently disabled_Requested
Redundancy Level not supported
BSSMAP Service or option not implemented or currently disabled_Reserved for
international use
national use
national use
national use
national use
national use
national use
national use
national use
BSSMAP Invalid message_Terrestrial circuit already allocated
BSSMAP Invalid message_Invalid message contents
BSSMAP Invalid message_Information element or field missing
BSSMAP Invalid message_Incorrect value
BSSMAP Invalid message_Unknown Message type

BSSMAP Invalid message_Unknown Information Element
BSSMAP Invalid message_DTM Handover - Invalid PS Indication
BSSMAP Invalid message_Call Identifier already allocated
BSSMAP Invalid message_Reserved for national use
BSSMAP Protocol error_Protocol Error between BSS and MSC
BSSMAP Protocol error_VGCS/VBS call non existent
BSSMAP Protocol error_DTM Handover - Timer Expiry
BSSMAP Protocol error_Reserved for international use
BSSMAP Protocol error_Reserved for national use
BSSMAP Interworking_Reserved for international use
BSSMAP Interworking_Reserved for national use
RSL RLM_Reserved
RSL RLM_Timer T200 expired (N200+1) times

RSL RLM_Re-establishment request
RSL RLM_Unsolicited UA response
RSL RLM_Unsolicited DM response
RSL RLM_Unsolicated DM response, multiple frame established state
RSL RLM_Unsolicited supervisory response
RSL RLM_Sequence error
RSL RLM_U-frame with incorrect parameters
RSL RLM_S-frame with incorrect parameters
RSL RLM_I-frame with incorrect use of M bit
RSL RLM_I-frame with incorrect length
RSL RLM_Frame not implemented
RSL RLM_SABM command, multiple frame established state
RSL RLM_SABM frame with information not allowed in this state
RSL RLM_Unknown
RSL Normal event_Radio interface failure
RSL Normal event_Radio link failure
RSL Normal event_Handover access failure
RSL Normal event_Talker access failure
RSL Normal event_Reserved for international use
RSL Normal event_O&M intervention
RSL Normal event_Unspecified
RSL Normal event_Reserved for national use

RSL Resource unavailable_Equipment failure
RSL Resource unavailable_Radio resource not available
RSL Resource unavailable_Terrestrial channel failure
RSL Resource unavailable_CCCH overload
RSL Resource unavailable_ACCH overload
RSL Resource unavailable_Processor overload
RSL Resource unavailable_Reserved for international use
RSL Resource unavailable_BTS not equipped
RSL Resource unavailable_Remote transcoder failure
RSL Resource unavailable_Notification overflow
RSL Resource unavailable_Reserved for national use
RSL Resource unavailable_Resource not available, unspecified
RSL Service or Option Not Available_Requested transcoding/rate adaption not
available
RSL Service or Option Not Available_Reserved for international use
RSL Service or Option Not Available_Service or option not available,
unspecified
RSL Service or Option Not Implemented_Encryption algorithm not
implemented
RSL Service or Option Not Implemented_Reserved for international use

RSL Service or Option Not Implemented_Service or option not implemented,
unspecified
RSL Invalid Message_Radio channel already activated/allocated
RSL Invalid Message_Reserved for international use
RSL Invalid Message_Reserved for national use
RSL Invalid Message_Invalid message, unspecified
RSL Protocol Error_Message discriminator error
RSL Protocol Error_Message type error
RSL Protocol Error_Message sequence error
RSL Protocol Error_General information element error
RSL Protocol Error_Mandatory information element error
RSL Protocol Error_Optional information element error
RSL Protocol Error_Information element non-existent
RSL Protocol Error_Information element length error
RSL Protocol Error_Invalid information element contents
RSL Protocol Error_Reserved for international use
RSL Protocol Error_Reserved for national use
RSL Protocol Error_Protocol error, unspecified
RSL Interworking_Reserved for international use

RSL Interworking_Reserved for national use
RSL Interworking_Unspecified
RR DTAP Normal event
RR DTAP Abnormal release, unspecified
RR DTAP Abnormal release, channel unacceptable
RR DTAP Abnormal release, timer expired
RR DTAP Abnormal release, no activity on the radio path
RR DTAP Preemptive release
RR DTAP UTRAN configuration unknown
RR DTAP Handover impossible, timing advance out of range
RR DTAP Channel mode unacceptable
RR DTAP Frequency not implemented
RR DTAP Originator or talker leaving group call area
RR DTAP Lower layer failure

RR DTAP Call already cleared

RR DTAP Semantically incorrect message
RR DTAP Invalid mandatory information
RR DTAP Message type non-existent or not implemented
RR DTAP Message type not compatible with protocol state
RR DTAP Conditional IE error
RR DTAP No cell allocation available
RR DTAP Protocol error unspecified




5 CovMo System KPIs
5.1 UMTS KPIs
Group Name KPI Name
RSCP Best Cell Average, All MR

RSCP Best Cell Average, 1st MR
RSCP Best Cell Average, Last MR
RSCP Best Cell Average
RSCP Best Server Average (initial)
ECN0 Best Cell Average, All MR
ECN0 Best Cell Average, Last MR
ECN0 Best Cell Average
ECN0 Best Server Average (initial)
Handover Intra RAT
Handover Inter RAT
Handover Inter Frequency
RF Condition Pilot Pollution
RF Condition Dominant Cell
RF Condition Serving Cell Overshoot (call-Base)
RF Condition Interference
RF Condition Voice Call Setup Time
RF Condition CSFB Cll Setup Time
RF Condition Location Update S.R.
RF Condition Routing Area Update S.R.
RF Condition RAB Assignment Response Time
RF Condition RSCP+ECN0
Traffic Call Distribution
Traffic CS Erlang
Traffic Data Volume
Traffic Data Throughput
Traffic Roamer Calls
Failure Call Setup Failure Call
Failure Call Drop Call
Failure Call CSSR
Optimization Scrambling Code
Optimization Inter-Freq. Neighbour
Optimization Intra-Freq. Neighbour
Optimization Swap Feeder
Statistics Report Cell Performance - PS
Statistics Report Cell Performance - CS
Statistics Report Worst N Cell - Setup Failure
Statistics Report Worst N Cell - Drop Call
Statistics Report Top N Subscriber - CS Erlang
Statistics Report Top N Subscriber - Data Volume
Statistics Report Worst N Subscriber - Drop Call
Statistics Report Worst N Subscriber - Setup Failure
MDT MDT Call Distribution

MDT Immediate RSCP (Best)
MDT Immediate ECN0 (Best)
MDT Immediate RSCP (First Server)
MDT Immediate ECN0 (First Server)
Table 16 UMTS KPIs
5.2 LTE KPIs
Group Name KPI Name
RSRP/RSRQ Serving Cell Average, All MR

RSRP/RSRQ Serving Cell Average, 1st MR
RSRP/RSRQ Serving Cell Average, Last MR
RSRP/RSRQ Serving Cell Average
Handover Inter Frequency
Handover Intra Frequency
Handover S1 Handover
Handover X2 Handover
Handover SRVCC Handover
Handover 4G to 3G Session Continuity
Handover 4G IRAT Redirect
RF Condition Dominant Cell
RF Condition Interference
RF Condition Pilot Dominance (1-2)
RF Condition Serving Cell Overshoot (Call-Base)
RF Condition Channel Quality
RF Condition RSRP+RSRQ (Initial)
Failure Call Setup Failure Call
Failure Call Drop Call
Failure Call CSSR
Traffic Call Distribution
Traffic Roamer Call
Traffic Data Throughput
Traffic Data Volume
Traffic Max. Data Throughput
Traffic CA Call
Optimization Inter-Frequency NBO
Optimization Intra-Frequency NBO
Optimization PCI Optimization
Optimization Swap feeder
Statistic Reports Cell Performance
Statistic Reports Worst N Cell- Block call
Statistic Reports Worst N Cell- Setup Failure Call
Statistic Reports Top N Subscriber - Data volume
Statistic Reports Worst N Subscriber - Setup Failure Call
Statistic Reports Worst N Subscribers- Drop call
MDT MDT Call Distribution
MDT Logged RSRP (Best)
MDT Logged RSRQ (Best)
MDT Immediate RSRP (Best)

MDT Immediate RSRQ (Best)
MDT Logged RSRP (Serving)
MDT Logged RSRQ (Serving)
MDT Immediate RSRP (Serving)
MDT Immediate RSRQ (Serving)
MDT RLF Distribution
Tile Base Cell-Footprint - RSRP
(Footprint)
Tile Base Cell-Footprint - RSRQ
(Footprint)
Tile Base Neighbors
(Footprint)
Tile Base Dominant Cell by Init Call
(Footprint)
Call Base Block Call
(Position)
Call Base Normal Call
(Position)
Call Base Drop Call
(Position)
Call Base Intra-Frequency
(Position)
Table 17 LTE KPIs

6 User Roles
Users may log in and access the CovMo system admin part. Operators can access this by connecting
across their IP network.
Follow the steps below to log in CovMo system.
Step 1: Type the appropriate address in the address bar. For the URL address to access CovMo,
contact your administrator.
Step 2: The login screen will appear upon loading the CovMo page.
Step 3: Select Administration, key in your username and password
Step 4: Click Sign in.
Figure 77 Login Admin Page
Depending on the right assigned to your user you will see the full admin part or limited one.
USER ROLE USER ROLE

ROLE_ADMIN Creates super user, capable of creating/editing/deleting any user,
managing administrative parameters
ROLE_USER_LTE Gives user an ability of operating LTE tab and its KPIs
ROLE_USER_UMTS Gives user an ability of operating UMTS tab and its KPIs
ROLE_CONFIGURATION Gives user an ability to use System alarming functionalities; this role
also affects to CovMo Admin console and allows to change KPI and
legend configuration or maintain IMSI groups in IMSI operation
IMSI_OPERATION Gives user an ability to create/edit IMSI lists
IMSI_SEARCH Gives user an ability to do subscriber trace with IMSIs or Groups
ROLE_MISC Gives user an ability of operating Misc tab for subscriber trace
Table 18 User Role

7. Use Cases
1 Use Case: Introduction
This document provides the details of the geo-location use case. Following is summary of
different use cases,
I. Coverage issue detection
II. Highway railway KPI analysis
III. Service analysis VoLTE
IV. Subscriber KQI analysis
V. Context analysis – Indoor/outdoor/moving/stationary
VI. Call drop and drill down analysis
VII. IRAT KPI analysis
VIII. Time domain analysis
IX. UE Capability map
X. User throughout map
XI. Signal Quality Map
XII. Signal Level Map
XIII. Data Import/Export
XIV. API interface to export Grid Network/Subscriber Profile
XV. Standard Trouble shooting by Geolocation Tool
XVI. Identify interference location
XVII. Identify cross feeder
XVIII. Identify dragging-late HO and feedback for HO parameter
XIX. Identify missing neighbors and unnecessary neighbor recommendation for event 1X and 2X
XX. Hot Spot Identification (Potential Traffic/Payload and Potential Revenue)

XXI. Network Profiling (traffic, payload, throughput, badspot, utilization, etc.) per user, per BTS
and per grid
XXII. Device Profiling & Subscriber movement (IMEI/IMSI)

2 Use Case: Coverage issue
2.1 Problem
To detect the areas with low RSRP/RSCP/RxLev related network coverage issues.
2.2 Analysis
Below is flow analysis,
a. Select KPI: Best Cell Average – All MR
b. Select desired date/time/duration
c. Add a filter under ‘Additional Rules’ and press ‘Apply All’
d. Map layer will display the filtered areas with weak signal strength,

e. For further analysis, do Map split in 2 parts and select different environments as “Indoor”
and “Outdoor”

2.3 Recommended Solution
Coverage hole analysis:
1. Outdoor coverage is quite weak

2. Switch to indoor, it is even weaker
3. Inter site distance is high
4. Antenna need to be high gain
5. Increase cell power
6. Sector addition to normalize outdoor coverage

3 Use Case: Highway railway analysis
3.1 Problem
To detect KPI issues on highway/railway and optimize KPI for it.
3.2 Analysis
a. Select KPI – drop call, data throughput

b. Select ‘Polygon’ – highway/railway
c. ‘Apply All’
d. In case of KPI degradation, select dominant cell to have optimized serving cell,

1. Down-tilt overshooting cells on highway

2. Run antenna optimization module for down-tilt and azimuth change

4 Use Case: Service analysis VoLTE
4.1 Problem
To detect the VoLTE call issues.
4.2 Analysis
Below is flow analysis:
a. VoLTE traffic call filter

b. Using QCI =1 as the criteria in ‘CovMo’ filters geo-located calls
c. VoLTE Call setup failure spot location identification with drill down to detailed call
trace for setup root cause identification.
d. End to end call trace from LTE to UMTS for any VoLTE.

1. Coverage optimization cells

2. Check for long call setup time and RSRP comparison for coverage improvement

5 Use Case: Subscriber KQI analysis
5.1 Problem
Continuous customer complaint about call quality.
Problem indications:
a. UMTS Call established normally but after normal speech suddenly A side cannot hear B side
or vice versa.
b. Call established normally but after normal speech both sides cannot hear each other. (it
happens rarely)
5.2 Analysis
1. Perform a signaling trace for A-party and B-party.

2. Check radio conditions in DL and radio link failure.
3. DL – Interference, RSCP/EcNo combinations.
Look for synchronization failures,

Compare sync failures with interference,
Interference reduction by running PSC conflict and suggestion optimization module.

6 Use Case: Geo location Context analysis
6.1 Problem
To detect the call-drop for moving subscriber or VIP drop issue.
6.2 Analysis
a. Select KPI Traffic > Call Density

b. Filter drop call locations
c. Apply filter for RSRP/RSCP/RxLev for subscriber trace locations.

1. Find the serving cell with drop.

2. Compare is one IMSI issue for all IMSI had drop in that area.
3. Check if device issue or network issue.

7. Use Case: Call drop and drill down analysis
7.1 Problem
To detect the areas (tiles) and cells with high drop.
7.2 Analysis
Below is flow analysis
a. Select KPI ‘Failure Call’ and analysis as ‘Drop Call’
b. Click on cell/tile to see drop breakdown for different 3GPP release cause and trending of drops.

c. Bin wise breakdown
Drill down to L3 call trace,

1. Check for drop reason category
2. Drop due to weak signal strength, or interference – apply necessary action accordingly
8. Use Case: IRAT analysis
8.1 Problem
To detect the areas with subscribers with LTE handset but latch to UMTS.
8.2 Analysis
a. Select KPI group > Handover, Analysis > Inter RAT

b. Highlight areas with high IRAT HOs
c. Handover due to radio reasons – Low RSRP in LTE cause IRAT to UMTS.

Optimize LTE coverage to get best serving cell to avoid IRAT to UMTS.

9. Use Case: Time domain analysis
9.1 Problem
To compare the KPIs after any parameter change.
9.2 Analysis
a. Select KPI of interest – RSRP/RSCP, Traffic > Data Volume, Drop Calls
b. Split map view using ‘Multi Map’ option
c. Select pre KPI time stamp before activity on left map, choose post KPI time stamp after
parameter change.
d. Compare number of tiles to get pre/post analysis.

10. Use Case: UE Capability Map
10.1 Problem
Call trace events report capability of UE with RRC_UE_CAPABILITY_INFORMATION,

S1_UE_CAPABILITY_INFO_INDICATION event. This provide capability for EUTRA, UTRAN and GSM.
Example:

Analysis
Visualizing call location for different UE capability devices
Compare data throughput DL/UL and compare it with device supported capabilities.
Identify device issue versus network issues and visualize accordingly.

11. Use Case: User Throughput Map
11.1 Problem
Find issues with user throughput on the map with drill down to subscriber and details level.
11.2 Analysis
Below is flow analysis;
a. Select KPI group > Traffic > Data Throughput
b. Click “Apply All.” To show user data throughput heat map
c. To show specific user or user group data throughput on map; click on IMSI group (Specified IMSI
or IMSI group) and click “Apply All.”

d. Find interference issues: check RSRP/EcNo/RxQual/CQI/SINR for cases of low throughput.
Improve RSRP/RSCP/RxLev by physical parameter optimization.

12. Use Case: Signal Quality Map
12.1 Problem
Display Signal Quality Coverage (4G: RSRQ, 3G: EcNo, 2G: RxQual)
12.2 Analysis
a. Select KPI group > RSRQ (or EcNo or RxQual), and click “Apply All”

13. Use Case: Signal Level Map
13.1 Problem
Display Signal Level Coverage (4G: RSRP, 3G: RSCP, 2G: RxLev)
13.2 Analysis
a. Select KPI group > RSRP (or RSCP or RxLev), and click “Apply All”

14. Use Case: Data Import/Export
14.1 Export API

Exporting data to 3rd party via CSV export or JSON object.
Data flow
CovMo can periodically export CDR (Call Detail Data) with subscriber call locations as flat files. This is
typically used by external applications with large data processing capability such as data warehouse
or data mining.
Periodic CSV export,
Rest API interface,

14.2 Results
Data files can be retrieved from CovMo FTP server periodically by third party applications. The
number of fields included in the export can be customized upon system integration. The following
fields on call information are available to be exported:
• IMSI
• Start_Time
• End_Time
• IMEI
• Make
• Model
• Call_Type
• Call_Status
• MNC
• MCC
• APN
• Start_Cell_ID
• Start_eNB_ID/RNC_ID/BSC_ID
• Start_Latitude*
• Start_Longitude*
• Start_RSRP/RSCp/RxLev
• Start_RSRQ/EcNo/RxQual
• End_Cell_ID
• End_eNB_ID/RNC_ID/BSC_ID
• End_Latitude*
• End_Longitude*
• End_ RSRP/RSCP/RxLev
• End_ RSRQ/EcNo/RxQual
• UL_Traffic_Volume*
• UL_Throughput_Max*
• DL_Traffic_Volume*
• DL_Throughput_Max*
• Technology
* - Fields requires vendor internal events.
14.3 Data import

CovMo allow import via various methods,
a. Polygon import,

b. POI import.

15. Use Case: API interface to export Grid Network/Subscriber
Profile
15.1 MAP data export
MAP tiles data can be exported using user interface in KML/MapInfo *.tab format,
MAP data export API is via SMTP (mail transfer protocol),

15.2 Results
Exported MAP data can be used in radio planning tool or other data warehouse systems.

16. Use Case: Standard Trouble shooting by Geolocation Tool
16.1 Problem
Drop call troubleshooting,
To detect the areas (tiles) and cells with high drop.
16.2 Analysis
a. Select KPI ‘Failure Call’ and analysis as ‘Drop Call’

b. Click on cell/tile to see drop breakdown for different 3GPP release cause and trending of drops.
c. Bin wise breakdown,

d. Drill down to L3 call trace,
1. Check for drop reason category

2. Drop due to weak signal strength, or interference – apply necessary action accordingly

17. Use Case: Identify Interference location
17.1 Problem
Identify Locations with high interference
17.2 Analysis
a. Select KPI group > RF conditions> Interference, and click “Apply All”
b. locations of high interference will be displayed on the map. Tile interference statistics will also be
shown in the reporting window

Interference reduction by running ACO.

18. Use Case: Identify Swap Feeder
18.1 Problem
Identify cells that have cross feeder issues.
18.2 Analysis
a. Select KPI group > Optimization> Swap Feeder, and click “Apply All”
b. Potential cases of swap feeder will be given in reporting along with statistics of the cell
c. Visually on the map, cells that have coverage overlap will be shown in yellow and coverage
direction of each cell will be shown.

a. Reduced list of swap sectors found network wide.
b. Physical visit to resolve swap antenna feeders.

19. Use Case: Identify dragging-late HO
19.1 Problem
Call drop or low throughput because of dragging late HO.
19.2 Analysis
Select KPI group > RF Condition and Analysis > Dominant Cell
Check for cell serving very far bins,
Dominant cell drag till next serving cell main lobe.
Check value of parameters a3offset and hysteresisa3, higher the value more it drag the calls to
neighboring cells.

20 Use Case: Identify missing neighbors and unnecessary neighbor
Recommendation
20.1 Problem
a. System detect missing neighbors

b. Provides suggestion for neighbor addition/removal
c. Neighbor recommendations based on best measurement and handover counts,
20.2 Analysis
Auto detection of neighbors.

Neighbor addition/removal.
20.3 Implementation
Manual/auto update of neighbor relations to OSS.

21 Use Case: Hot Spot Identification (Potential Traffic/Payload and
Potential Revenue)
21.1 Problem
Identify locations with high data volume and low throughput
21.2 Analysis
a. Select KPI group > Traffic> Data Throughput
b. Under “Additional Rules,” enter the hotspot threshold criteria.

c. In this example, we filtered for locations with more than 500MB data volume and less than
250kbps
d. click “Apply All’ to show hotspot locations on the map

Deploy expansion solutions for recommended location.
New nominal lat/long for planning process.

22 Use Case: Network Profiling (traffic, payload, throughput, badspot,
utilization, etc) per user, per BTS and per grid
22.1 Problem
To identify traffic, payload, throughput, badspot, utilization – CovMo additional rule filter with
various KPI combinations are required.
a. Traffic KPI > High data volume, high throughput ➔ Hotspot
b. Traffic KPI > High data volume, low throughput ➔ Badspot
c. Traffic KPI > High data volume, high call density ➔ Utilization
d. Traffic KPI > Call density ➔ Identify traffic (apply various service filters – Voice, Video, LTE-Traffic,
LTE-Signaling)
22.2 Analysis
KPI filter,

23 Use Case: Device Profiling & Subscriber movement (IMEI/IMSI)
23.1 Problem
Identify locations of specific subscribers and devices.
23.2 Analysis
a. Select KPI group > Traffic> Call Distribution
b. for Handset, go to Handset filter and enter Brand and/or Model of the phone, and click “apply all”
c. for Subscriber movement, go to IMSI filter and enter the VIP group or specific IMSI, then click
“Apply All”

d. Alternatively, to monitor only the location of a subscriber across all technology and regions: Goto
“Misc” tab=> Select Subscriber Trace, and enter the specific IMSI or IMSI group, and click “Apply All”

CovMo User Guide

Uploaded by

Copyright:

Available Formats

CovMo User Guide

Uploaded by

Document Information

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

CovMo User Guide

Uploaded by

Copyright:

Available Formats

CovMo System User Guide

Groundhog Technologies Inc. Confidential

CovMo User Guide

Geo-locating Network Traffic and Events

United States (Headquarters)

United States (West Coast)

CovMo User Guide Page 2

1 ABOUT THIS GUIDE ..................................................................................................................................... 10

1.1 CHAPTER OVERVIEW ........................................................................................................................................ 10

2 INTRODUCING COVMO SYSTEM .................................................................................................................. 13

3 GETTING STARTED WITH COVMO SYSTEM .................................................................................................. 19

3.1 LOGGING IN .................................................................................................................................................... 19

4 NAVIGATING COVMO SYSTEM .................................................................................................................... 27

4.1 USER INTERFACE OVERVIEW .............................................................................................................................. 27

CovMo User Guide Page 3

5 COVMO SYSTEM KPIS ................................................................................................................................ 131

5.1 UMTS KPIS ................................................................................................................................................. 131

6 USER ROLES .............................................................................................................................................. 134

7. USE CASES ................................................................................................................................................ 135

1 USE CASE: INTRODUCTION .................................................................................................................. 135

2 USE CASE: COVERAGE ISSUE ................................................................................................................ 137

2.1 PROBLEM ..................................................................................................................................................... 137

3 USE CASE: HIGHWAY RAILWAY ANALYSIS............................................................................................ 140

3.1 PROBLEM ..................................................................................................................................................... 140

4 USE CASE: SERVICE ANALYSIS VOLTE ................................................................................................... 142

4.1 PROBLEM ..................................................................................................................................................... 142

5 USE CASE: SUBSCRIBER KQI ANALYSIS ................................................................................................. 144

5.1 PROBLEM ..................................................................................................................................................... 144

6 USE CASE: GEO LOCATION CONTEXT ANALYSIS ................................................................................... 146

6.1 PROBLEM ............................................................................................................................................. 146

7.1 PROBLEM ..................................................................................................................................................... 148

8. USE CASE: IRAT ANALYSIS .................................................................................................................... 150

8.1 PROBLEM ..................................................................................................................................................... 150

9. USE CASE: TIME DOMAIN ANALYSIS .................................................................................................... 152

CovMo User Guide Page 4

10.1 PROBLEM ............................................................................................................................................. 153

10.3 RECOMMENDED SOLUTION ........................................................................................................................... 155

11. USE CASE: USER THROUGHPUT MAP ............................................................................................... 156

11.1 PROBLEM................................................................................................................................................... 156

12. USE CASE: SIGNAL QUALITY MAP .................................................................................................... 158

12.1 PROBLEM................................................................................................................................................... 158

13. USE CASE: SIGNAL LEVEL MAP ......................................................................................................... 159

13.1 PROBLEM................................................................................................................................................... 159

14. USE CASE: DATA IMPORT/EXPORT .................................................................................................. 160

14.1 EXPORT API .......................................................................................................................................... 160

15.1 MAP DATA EXPORT ................................................................................................................................ 163

16.1 PROBLEM ............................................................................................................................................. 165

16.2 ANALYSIS ................................................................................................................................................... 165

17. USE CASE: IDENTIFY INTERFERENCE LOCATION ............................................................................... 168

17.1 PROBLEM................................................................................................................................................... 168

18. USE CASE: IDENTIFY SWAP FEEDER.................................................................................................. 169

18.1 PROBLEM................................................................................................................................................... 169

19. USE CASE: IDENTIFY DRAGGING-LATE HO ........................................................................................ 170

19.1 PROBLEM ............................................................................................................................................. 170

CovMo User Guide Page 5

20.1 PROBLEM ............................................................................................................................................. 171

21.1 PROBLEM................................................................................................................................................... 173

22.1 PROBLEM................................................................................................................................................... 176

23.1 PROBLEM................................................................................................................................................... 179

CovMo User Guide Page 6