WWW.ANITE.

COM/NEMO

NEMO CEM SOLUTION 3.0

TECHNICAL PRODUCT DESCRIPTION

© 2014
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

© 2015 Anite Finland Ltd. All rights reserved.

The content of this document shall not be transmitted, displayed, shown, used in its whole or partially
without prior notification to Anite.

This product description, as well as the software described in it, is furnished under license and may
only be used or copied in accordance with the terms of such license. The information in this paper is
intended for informational use only and is subject to change without notice. Anite Finland Ltd assumes
no responsibility or liability for any errors or inaccuracies that may appear in this material.

Except as permitted by such license, no part of this publication may be reproduced or transmitted in
any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written
permission of Anite Finland Ltd.

Last Edited: September 2015, Revision 3.0.0

Page 2
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

CONTENTS

1  INTRODUCTION ............................................................................................... 6 
1.1  Market overview ....................................................................................... 6 
1.2  Solution introduction ................................................................................. 6 

2  NEMO CEM SOLUTION OVERVIEW ....................................................................... 7 

2.1  Introduction ............................................................................................. 7 
2.2  Solution overview ..................................................................................... 8 
2.3  Modules and services ................................................................................ 8 
2.3.1  Nemo Qmon ..................................................................................... 8 
2.3.2  Nemo Qview Server........................................................................... 9 
2.4  Compatibility .......................................................................................... 10 
2.4.1  Nemo Qmon ................................................................................... 10 
2.4.2  Nemo Qview................................................................................... 10 

3  NEMO QMON.................................................................................................. 11 

3.1  Operation modes .................................................................................... 11 
3.1.1  OCM | On-Click Monitoring ............................................................... 11 
3.1.2  SSM | Silent Script Monitoring .......................................................... 11 
3.1.3  SLM | Silent Live Monitoring ............................................................. 12 
3.2  Footprint ............................................................................................... 12 
3.2.1  On the device ................................................................................. 12 
3.2.2  On the data plan ............................................................................. 12 
3.3  Privacy .................................................................................................. 13 
3.3.1  Install / Uninstall process ................................................................. 13 
3.3.2  User data gathering techniques ......................................................... 13 
3.3.3  Anonymous mode ........................................................................... 13 
3.4  Location management ............................................................................. 13 
3.4.1  General functionality ....................................................................... 13 
3.4.2  Location based on the network inventory ............................................ 14 
3.4.3  Location radius ............................................................................... 14 
3.5  Provisioning ........................................................................................... 15 
3.5.1  Private store .................................................................................. 15 
3.5.2  Public store .................................................................................... 15 
3.6  Software installation ............................................................................... 15 
3.7  Floating licenses ..................................................................................... 16 
3.8  Data collection and upload process ............................................................ 16 
3.8.1  Remote configuration ...................................................................... 16 
3.8.2  KPI collection ................................................................................. 17 
3.8.3  Results upload ................................................................................ 18 

Page 3
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

4  NEMO QVIEW SERVER ..................................................................................... 19 

4.1  Description ............................................................................................ 19 
4.2  Server modules ...................................................................................... 19 
4.2.1  QTrend view ................................................................................... 19 
4.2.2  QNetwork view ............................................................................... 20 
4.2.3  QCustomer view ............................................................................. 21 
4.3  QAdmin view .......................................................................................... 21 
4.3.1  Nemo Qmon configuration ................................................................ 21 
4.3.2  Customers ..................................................................................... 22 
4.3.3  Nemo Qmon management ................................................................ 22 
4.3.4  Solution settings ............................................................................. 22 
4.4  Running a scenario ................................................................................. 22 
4.4.1  Design a scenario............................................................................ 22 
4.4.2  Deploy and capture ......................................................................... 23 
4.5  Dashboard and reports ............................................................................ 24 
4.5.1  Reports ......................................................................................... 24 
4.5.2  Charts ........................................................................................... 25 
4.5.3  Maps ............................................................................................. 26 
4.5.4  Filters............................................................................................ 27 
4.6  Platform Manager ................................................................................... 29 
4.6.1  Users and rights ............................................................................. 29 

5  NEMO QVIEW ARCHITECTURE .......................................................................... 31 

5.1  Frameworks ........................................................................................... 31 
5.2  System overview .................................................................................... 32 
5.3  Requirements ......................................................................................... 33 
5.3.1  Software ........................................................................................ 33 
5.3.2  Connectivity ................................................................................... 33 
5.4  Data security ......................................................................................... 34 
5.4.1  Network access protocols ................................................................. 34 
5.4.2  Availability ..................................................................................... 34 
5.4.3  Integrity ........................................................................................ 34 
5.4.4  Confidentiality ................................................................................ 34 
5.4.5  Traceability .................................................................................... 34 
5.4.6  Auditability .................................................................................... 35 
5.4.7  Errors and congestion tolerance ........................................................ 35 
5.4.8  Security against attacks from hackers and viruses ............................... 35 
5.4.9  Password policy .............................................................................. 36 
5.5  Interfaces .............................................................................................. 36 
5.5.1  Imports ......................................................................................... 36 
5.5.2  Northbound interface ....................................................................... 37 
5.5.3  Third party ..................................................................................... 37 
5.5.4  IT & network .................................................................................. 37 

Page 4
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

6  INTEGRATION ................................................................................................ 38 

6.1  MSISDN enrichment ................................................................................ 38 
6.2  Cell Ref ................................................................................................. 38 
6.3  Nemo Qmon SDK .................................................................................... 39 

7  GLOSSARY .................................................................................................... 40 

Page 5
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

1 INTRODUCTION

1.1 Market overview

Since 2007 and the release of the first iPhone, the way customers are using and living the quality of
mobile network has tremendously changed. Data traffic has been skyrocketing ever since and legacy
services are becoming slowly but surely less important (decrease of revenue in SMS to reach 39% in
2017 – forecast by Analysis Mason).

Mobile Network Operators are facing a triple challenge with:

 A market reaching its maturity with new customers harder to target and already using
competition

 Real quality becoming a key feature for aware customers

 Over The Top (OTT) players influence that is growing on the MNO’s customers, pushing
more and more investments in the network data speed.

To ensure a high level of quality, an optimal connectivity that will keep customers loyal and drive
more revenue, the key is to know exactly what customers live and feel while they are using their
phones. Therefore, traditional data and troubleshooting tools such as probes or drive tests are still key
tools, but are not enough to ensure an optimal Quality of Service (QoS). To measure the quality of a
service, it is essential to put the customer directly at the heart of it. Like voice for data, Quality of
Service is changing for a more relevant and competitive analysis: Quality of Experience (QoE).

At the same time, phones are becoming more and more powerful with high capabilities of calculation
and memory. The key is to use a small amount of that power to measure, analyse, compute and
upload technical data, directly from the end user phone. Only this way will the operators really
measure, understand and improve what is really happening on their customers’ phones.

1.2 Solution introduction

Anite’s flagship software solution, Nemo CEM Solution, is the customer experience window of any
Service Quality Management (SQM) solution.

Key Business Advantages Overall Benefits

Real life, real time, customer centric solution Coverage and performance measures as mobile
subscribers feel and live it

Easy to Deploy on existing commercial Proactive customer care tool to handle Network
smartphones Experience issues

No network or device dependency Live benchmark of competition

Powerful and configurable web portal interfaces Focus troubleshooting where customers need it

Improves bottom lines result reducing and

optimizing costs of quality measurement and
quality related churn

Page 6
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

2 NEMO CEM SOLUTION OVERVIEW

2.1 Introduction
Nemo CEM Solution is a software solution for monitoring and testing interactions between a mobile
device and network infrastructures. Smart, flexible, easy to handle, and efficient, the solution is
divided in two modules that communicate over the network.

 Nemo Qmon (DQA): a mobile application on the end-user device that collects, computes and
uploads Key Quality and Key Performance Indicators (KQI & KPI). This solution can be
installed directly Over-the-air (OTA) on commercial smartphones and has a low impact on the
battery life.

 Nemo Qview: a server interface that controls the Nemo Qmon units, stores, transforms,
aggregates and displays the information gathered by the Nemo Qmon units. As a reporting
tool, it displays meaningful information on easy to understand charts and dashboards. As a
configuration tool, it enables OTA configuration of the Nemo Qmon for all available services.

Page 7
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

2.2 Solution overview

With the Nemo CEM Solution, end-to end measurement of service quality takes on a new meaning.

Feature Benefit

Real-life scenarios, real-time collection of Provide real Customer Experience Monitoring

network and device KPIs directly from the user and Management Analysis (CEM)
device.

Support all network wide range of wireless Fully agnostic solution (multi device and
technologies. Operating System, independent from network
and equipment vendors)

Multi-platform supporting all major mobile OS, Wide footprint of deployment, no jailbreaking or
and works on commercial phones. rooting required.

Monitor data, voice, coverage, web, video Capture the whole range of the user interactions
streaming, messaging and applications. with their device and the network.

Remotely manage scenarios that are running Quickly turn on or off monitoring scenarios for
on the Nemo Qmon without the need for an benchmarking or customer investigation
application update. purposes.

Mobile Nemo Qmon works even when the Capture events otherwise invisible to the user
device is on idle or on Wi-Fi. (e.g. handovers, offload, loss of coverage…).

Mobile application makes it easy to run, Fully transparent option on the end-user
understand, and visualize performance tests. terminal (smartphone) and network sides.
User in control, privacy fully respected.

On-device surveys triggered on specific events Enrich technical data with real customer
(e.g. dropped call), configurable from the experience feedback.
server.

2.3 Modules and services

This section introduces the main modules and important concepts of the solution.

2.3.1 Nemo Qmon

Nemo Qmon can run in three different modes.

Mode Name Type Definition Triggers

OCM Active and Manual Manual tests for different End user
(On Click services (data, web, video…)
Monitoring) via a scenario defined on the
server.

SSM Active and automatic Scripted tests launched Nemo

(Silent Script automatically, via a scenario Qview
Monitoring) defined on the server. server

Page 8
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

Mode Name Type Definition Triggers

SLM Passive Running in the background, it Normal

(Silent Live records information on the usage of
Monitoring) events and services used on the phone
the device.

2.3.2 Nemo Qview Server

The Nemo Qview Server is divided in three main modules, plus an additional administration module.

Name Description

Trend View Trend View is a reporting module providing the evolution over time of main
KPIs. 
It offers the ability to define custom dashboards, where main KPIs are
automatically aggregated by day, week, month and years, with the
possibility to breakdown the reports by different axis.
For instance, Trend View dashboards can present the daily evolution of the
HTTP Download Throughput over a month, with a breakdown by technology
(2G, 3G, and 4G). Or present the weekly evolution over a year of the Voice
Success Rate with a breakdown by OS.
Trend View module targets QoE Teams and Managers focused on key
indicators to monitor the evolution of QoE over time.

Network View Network View module offers a complete toolset to analyse in real-time all
measurements performed by Nemo Qmon units. 
This investigation module allows advanced filtering and drill-down
capabilities, as well as visualization of geolocalized data with network
inventory layer (cellref).
Focused on network cell KPIs, it simplifies analysis and correlation of various
data; for example, displaying data low 4G throughput, relative to distance to
cell and number of customer complaints in the same area becomes easy.
All data can be exported in CSV or KML format for post-processing.

Customer View Customer View module provides a comprehensive QoE cockpit focused on a
single customer. 
It not only enables understanding at a glance how good QoE perceived by
this customer is, but it also enables investigation for advanced users such as
correlation of Handovers with Voice Call Failures and distance to serving
cell.
From Customer View module, customer care team can easily interact with
the customer to answer his complaints and modify Nemo Qmon behaviour to
collect more data for later investigation.

Admin View Admin View is the administration module of the Nemo Qview server. It
allows administrators to manage the Nemo Qmon units registered on the
server, the scenarios, the licenses, and the export templates.

Page 9
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

2.4 Compatibility

2.4.1 Nemo Qmon

Nemo Qmon is a mobile application available on all major mobile operating systems. The full list of
KPIs and their availability per OS is available on demand.

2.4.2 Nemo Qview

Nemo Qview can be accessed remotely using any modern browsers. However, browsers having
varying levels of compliance with Internet standards such as CSS, there may be minor variations in
appearance.

Page 10
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

3 NEMO QMON

Nemo Qmon is a mobile application installed on the end-user mobile device (e.g. smartphone) which
extracts real-life information as they happen on the device. Associated with the GPS location of the
user, it allows the analysis and anticipation of the device behavior on the operator network.

Nemo Qmon is available today, offering quality and value by supporting the standard smartphone
operating systems:

 Apple iOS

 Google Android

 Windows Phone

Today, it supports all major wireless technologies used worldwide including GSM, GPRS, EDGE,
WCDMA, HSDPA, HSPA+, HSUPA, LTE, and LTE+, but also Wi-Fi.

3.1 Operation modes

Nemo Qmon is used for many professional applications such as mobile network performance test,
service benchmarking, coverage, proactive customer care, and network smart monitoring. The use
cases are varied and unlimited. Nemo Qmon has three operation modes.

3.1.1 OCM | On-Click Monitoring

In this mode, the end-user launches the service test themselves, based on a specific scenario
provisioned by the Nemo Qview server. With its user-friendly interface, the OCM mode is a quick and
easy-to-use tool to perform sporadic tests when needed. It performs service tests, displays
information in real time and records the main KPIs. The KPIs are then uploaded through HTTP/HTTPS
to the Nemo Qview server for post-processing and analysis.

For the list of all the available services in the OCM mode, please refer to document
Key_Performance_Indicators.pdf

3.1.2 SSM | Silent Script Monitoring

In this mode, the application is running in the background as a service. It performs tests
automatically, without any end-user action. This mode provides a pro-active and always-on automated
monitoring solution. Services, information and test scenarios are defined remotely on the server side.
The scenario administrator defines the number of tests they want to execute and the time between
each iteration of the test. The time between tests can either be:

• Fixed to execute tests at regular time intervals

• Adapted to the current user speed, triggering tests more frequently as the user speed
increases.

One of the SSM mode’s main use case is when a problem occurs within the mobile network at a
specific location, or to regularly collect measurements to build live coverage maps. The scenario
administrator can design a stress test ready to be spread out to any registered Nemo Qmon, and
immediately start gathering KPIs.
Page 11
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

3.1.3 SLM | Silent Live Monitoring

In this mode, the application is running in the background as a service. It monitors the real customer
experience as end-users live it. It records key information on a service as it is being used. This mode
provides information on the everyday use of the end-user, monitoring the quality of service in a real-
life context.

For instance, when the end-user receives a call, all network and voice service KPIs such as but not
limited to call duration, setup time, and call event (drop, fail) are recorded and sent to the Nemo
Qview server.

In addition, a customer experience survey can be displayed at the end of a service session (voice, web
browsing...). Thus, it will provide an overview of the real customer experience, on how your
subscribers perceive the quality of your network services, in addition to the technical data gathered
with the KPIs.

3.2 Footprint

3.2.1 On the device

Nemo Qmon complies with programing best practices in order to decrease as much as possible its
impacts on the user device. Through our Quality Assurance process1, we are constantly checking:

 Impact on battery with or without GPS

 Impact on battery with or without any usage (idle mode)

 Impact on the device performance (Memory and CPU) when data is collected by the Nemo
Qmon.

Our goal is to achieve a product that uses:

 Less than 5% of the device global performances,

 No more than 10% of the device battery per day.

It is important to note that the configuration of the scenario has a direct impact on the performance of
the device being monitored. A very aggressive scenario monitoring a lot of different services and
making automated tests at a high frequency will result in an increased impact on the battery life of
the device as well as provoking lags and slowdowns of the device. This is especially true on older or
lower spec devices.

For more information on the battery impact of the Nemo Qmon agent, please refer to the document
Nemo Qmon One Battery Impact.pdf.

3.2.2 On the data plan

A data pay-as-you-go or pre-paid offer subscription for every targeted device (panellist) is mandatory.

The use of the Nemo Qmon may impact the subscriber bill in some cases. Below is a detailed
description of the Nemo Qmon data usage, with modes that are always running in the background and
monitor the customer experience.

 Note: the automated tests can be configured to use specific URL’s defined by the
operator that will not be taken into account for the customer data plan.

1
(refer to the PLM documentation)

Page 12
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

For more information on the volumes of data generated by the Nemo Qmon agent, please refer to the
document Agent-Server Network Volumes.pdf.

3.3 Privacy
Nemo Qmon is not embedded within any commercial smartphones. Nemo Qmon is neither a
rootkit nor a modified firmware.

3.3.1 Install / Uninstall process

Nemo Qmon is abiding to rules and laws on private data protection, and on software terms of uses.
Nemo Qmon install process requires the full consent (opt-in) of the end-user. The Nemo Qmon terms
of use are available within the Monitoring Engine and can be customised for any language, and
adapted to conform to the legal context of specific countries. In addition, the terms of use process can
be enabled or disabled. However, we highly advise to enable this feature, including for internal use of
the application.

The Nemo Qmon cannot be installed directly or automatically on a mobile device without the user
input. The user has to accept the terms of use before downloading the application. If they decline, the
install process stops. In addition, they can uninstall the Nemo Qmon application on their mobile device
at any time, just like any other mobile application.

The user is always able to opt-out of a scenario either by uninstalling the application or by contacting
the scenario administrator.

3.3.2 User data gathering techniques

Anite only gathers technical data for a statistical purpose. Data collected is meant for MNO’s technical
departments in order to identify issues between mobile devices and the MNO network infrastructures.
For instance, Nemo Qmon gathers data such as RSSI (Reception Strength Signal Indicator),
handovers between technologies (e.g. 2G to 3G), Network Cell Identity, minimum or maximum
throughput, or failed call connections. The Nemo Qmon also collects the IMEI (UDID for Apple iOS) for
statistical purposes.

3.3.3 Anonymous mode

A version of our Nemo Qmon is available in a fully anonymous mode: private information such as IMEI
or IMSI is not collected and each panellist gets a unique Nemo Qmon ID to identify them. However, it
is impossible to identify the person behind this ID. This mode can be used for deployments with a
statistical purpose or in countries where regulation on private information is particularly sensitive. The
anonymous mode can also be used during network-only investigations where identifying the users is
not required.

See the Privacy Policy.pdf annex document for more details.

3.4 Location management

3.4.1 General functionality

The Nemo Qmon solution is compliant with location management best practices. The behaviour of the
Nemo Qmon is compliant with the standard practices defined by each mobile operating system
vendors. The Nemo Qmon automatically manages the activation of the location feature, and the
refresh rate of its different mode, such as GPS and GPS-A. The location information is available only if:

 It is activated in the user settings;

Page 13
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

 It is activated in the scenario settings

 If either GPS or network coverage is available for the user’s location

Location information is provided by the OS and can be either from:

 GPS

 GPS assisted with triangulation

 Network Location (triangulation)

Triangulation gives an approximate location, far less accurate than the GPS or the GPS Assisted. GPS
duration to compute an accurate location varies depending on the phone model, OS, location of the
user (indoor or outdoor, in a crowded place or not) and settings set in the Scenario Manager module.

For instance, an indoor location near a window with a Samsung Galaxy S2 takes around two minutes.
However, setting high value of location in order to have the most accurate location information will
have a high impact on the device battery.

The location provider information is only available on Android. For iOS and Windows Phone, the
location is entirely dependent of the OS.

The location can be taken at the beginning, at the end or during the full duration of a measurement.
This behavior can be set for each service on the Nemo Qview server and precisely from the Monitoring
Engine module. When raw data collection is activated remotely, the locations information will be
added on each raw data log, archived and sent to the server. Activating raw data collection gives a
much finer precision of the measurement location throughout the test, but as it generates a lot more
data, it may have a significant impact on the data usage of the user.

3.4.2 Location based on the network inventory

If the MNO imports their Network Inventory in the Nemo Qview server, a measurement with no
location other that Cell ID and LAC can be located by using the coordinates provided in the Network
inventory.

3.4.3 Location radius

Every measurement enriched with the location is provided with the following information:

 Latitude coordinates

 Longitude coordinates

 Location Radius

 Speed

 Altitude

 Time

When latitude and longitude coordinates are collected, a radius in meters is also added to the
measurement, providing an error margin. The real location of the device could be anywhere in a circle
of that radius centred on the latitude and longitude coordinates of the measurement.

See the Location Management.pdf annex for more details.

Page 14
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

3.5 Provisioning
There are two ways to install the Nemo Qmon on a mobile device:

 Using the private store process

 Using the public store process

Both have benefits and drawbacks which should be taken into account when deploying the application.

3.5.1 Private store

Benefits Drawbacks

A single URL to download and install the The URL can be shared to non-authorised
Nemo Qmon. panellists.

Update process is controlled directly from

the Nemo Qview server.

No validation required from the public

store, access to private API’s is possible

3.5.2 Public store

Benefits Drawbacks

Application is accessible to a large Not all the KPIs are accessible due to
audience in a standard installation restrictions applied on the use of private APIs.
process.

Scalable to support mass deployment of The panel of users of the application is not
the application. easily manageable.

Review and publication delays may occur that

do not depend on Anite or the customer.

For details on the agent provisioning, please refer to the specific document Agent Provisioning.docx
in the Annexes.

3.6 Software installation

The software installation process on the mobile device is only taking up to three finger taps.
Installation and user guides are available upon request for each mobile platforms.

Upon installation, the application must be launched manually the first time. If the end user reboots
their phone after having launched the application, SLM and SSM services start automatically.

This feature is not available on iOS due to an iOS restriction.

The Nemo Qmon is displayed in the device application manager. User can uninstall the application by
themselves. However, the Nemo Qmon can also be deactivated remotely from the server. Deactivation
can either be temporarily or definitive. When deactivated, the Nemo Qmon will not start. The
application cannot be uninstalled from the end user device remotely.

If the user wishes to keep the application but prevent it from sending data, an opt-out option is also
available in the application settings.

Page 15
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

3.7 Floating licenses

Nemo Qview uses a floating license scheme. A pool of licenses is automatically filled or emptied
according to the changes applied to the agents. This allows the administrator of the server to
dynamically and/or automatically reallocate licenses to a pool of agents depending on their needs.

As a result, an agent can be in one of two license states: Active or Idle.

Active Idle

An agent with a valid license token. It is fully An agent without a license token. Its
functional, monitoring and reporting functionalities are limited and the agent does
measurements to the server. It is possible to NOT collect nor send measurements to the
create agents that are active automatically after server.
installation.

However, idle agents are still communicating with the server at regular time intervals for the following
information

 Configuration updates

 Location updates (if activated in their scenario)

This information is useful to know if the agent is kept alive and where it is. This can be used to
evaluate if the agent must be granted a license.

Automatic rules are in place to grant licenses to specific agents and to revoke licenses of inactive
agents.

3.8 Data collection and upload process

3.8.1 Remote configuration

Nemo Qmon scenarios and behaviors can be activated and adapted remotely from the Nemo Qview.
To update its configuration file, Nemo Qmon regularly checks for a new version of the configuration
file via a heartbeat process. If a new version is available, the new configuration file is downloaded and
updated automatically on the device.

Heartbeat is a software routine that regularly sends a short message to the server to check for
updates. The frequency of the heartbeats can be configured on request. By default, the heartbeat
frequency is set to once per hour since the first heartbeat, at the installation and opt-in of the Nemo
Qmon. The server will send updates of the configuration file, updating therefore the Nemo Qmon
units.

The configuration file is in XML format. It is split in several parts. The first one specifies how the Nemo
Qmon globally behaves, and available options are:

 Location information can be enabled or disabled

 Operation modes to be activated (SSM, OCM, SLM)

 Services features to be activated (data throughput, voice, SMS…)

 Protocol to be used to upload KPIs (HTTP or HTTPS)

 Data collection in roaming can be enabled or disabled

 Log messages activation

 Address of the server that will receive the measurements

Page 16
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

The other parts are service-specific and contain settings or parameters for the activated services. For
instance, for the throughput feature, available options are:

 Size of files to be downloaded or uploaded according to technology (2G, 3G, 4G, WIFI)

 File URL’s

 Timeouts

 Frequency of measurements

3.8.2 KPI collection

Nemo Qmon permanently monitors the mobile OS events. Here is a list of some data gathered on
Android:

 Changes in the radio stack (CI, LAC, MNC, MCC, BEARER, RSSI …)

 Changes of the phone battery status

 Applications running in foreground or background

 Wi-Fi usage

 GSM data usage

 Voice call events

 Incoming/outgoing messaging (SMS / MMS / Email)

For the full list of KPIs collected by Nemo Qmon, please refer to the document
Key_Performance_Indicators.pdf.

Nemo Qmon uses the memory and CPU of the device to compute the results from the KPI collection
and decrease the weight of the data being transferred between the device and the server. Depending
on the mode (OCM, SSM, SLM), the KPI computation time differs to have as little impact on the user
experience as possible.

Specifics for each measure mode are detailed below.

OCM

In the active and on-demand testing mode, the KPI’s are computed at the end of the test. While
performing a throughput test, the Nemo Qmon takes measurements at specific intervals of time (by
default each second) and perform the calculation after the test has completed.

The results of the measurements are then sent to the server as soon as the calculation is complete. If
the Nemo Qmon fails to send the results to the server for any reason, an icon on the main screen will
alert the user that the KPI’s were not uploaded. In this case, a user action is required.

SSM

In the active and automated testing mode, the tests take place only if the user phone is in idle mode.
If not, the test is cancelled automatically to prevent any interference with the normal usage of the
device. The calculation process is the same as in the OCM mode, except that it takes place in the
background, without any notification on the end user side. If the Nemo Qmon fails to send the results
to the server, it will automatically retry again at the next heartbeat.

SLM

In the passive monitoring mode, the KPI calculation has absolutely to be delayed in order to decrease
as much as possible the impact on the end user. Nemo Qmon records all the meaningful information
during any SLM session supported by the device. Information is stored on the phone’s memory until

Page 17
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

the end-user stops using his phone. Once the screen is being turned off and the phone goes in idle
mode, KPIs are being computed and automatically sent to the server. If a value could not be
uploaded, the Nemo Qmon will retry to send them automatically at the next heartbeat. By default, it
will occur one hour after the last heartbeat.

3.8.3 Results upload

The collected data is gathered and aggregated directly on the mobile phone, just after using a service.
Once aggregated, the results are queued in a spooler. This spooler manages the upload of the
collected data to the server. The upload of the collected data occurs at regular time intervals that can
be configured on the server. After receiving the acknowledgement from the server that the results
have been correctly transmitted, the spooler is emptied.

The Nemo Qmon spooler uses the first data connection available (Wi-Fi or radio bearer). Data is sent
using secure HTTP (HTTPS) on port 443.

In the Nemo Qmon settings, the end user can choose to upload the results only when the device is
connected to a Wi-Fi network (Wi-Fi Mode). This feature is particularly useful for a passive scenario
using the SLM mode only. This feature intends to limit the impact of the application on the end user
data plan as much as possible.

Page 18
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

4 NEMO QVIEW SERVER

4.1 Description
The Nemo Qview has been designed to be part of the SQM (Service Quality Management) and CEM
(Customer Experience Management) approach introducing the customer experience and data device
metrics within the global reporting system of the Mobile Operator.

Nemo Qview acts in two main capacities.

 Manage and pilot the fleet of Nemo Qmon units using Over-the-Air configuration.

 Provide comprehensive reports on the data collected by the Nemo Qmon.

4.2 Server modules

To provide the most value out of the data collected by the Nemo Qmon, Anite has developed three
independent server modules that can best respond to the MNO’s use cases.

4.2.1 QTrend view

QTrend View is a Business Intelligence module that provides insightful dashboards that presents the
evolution and trends over time of the main KPIs, with advanced breakdown capabilities allowing for a
multi-axis analysis.

QTrend View is most relevant to LOB managers, QoE teams and strategic analysts.

The main features are:

 Configurable dashboards
Page 19
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

Define dashboard with selected reports and time aggregation: day, week, month, and year.

 Pre-calculated reports

Reports are continuously calculated on large amount of Nemo Qmon measurements, available for
instant access.

 Trend evolution

KPIs are presented over time to evaluate the trend at a glance.

 Easy analysis

Main KPIs are compared to configurable thresholds, for easy evaluation against target. Breakdown
analysis on user-defined axis (Technology, Scenario, OS, Operators, etc...)

4.2.2 QNetwork view

QNetwork View is a real time network analysis module that provides a complete toolset to analyse in
real time all of the Nemo Qmon measurements, with drill down and geo-mapping capabilities, allowing
for the investigation of issues correlated to the network inventory.

QNetwork View is most relevant to network engineers, support teams and QoE/QoS teams.

QNetwork module is only available on a low deployment environment. Over a thousand agents, this
module is disabled and only the investigation tool remains available.

The main features of QNetwork are:

 Comprehensive set of reports based on the Nemo Qmon data

The reports are available per functional area (Voice, Data, Coverage, Video streaming…) and provide
advanced multi-select filters and export capabilities.

 All-in-one investigation tool

The investigation tool allows for multidimensional investigation and advanced filtering capabilities.
Making extensive use of the network inventory (cell, azimuth, beam width, distance to site) and the
creation of personalized multi-layer maps.

Page 20
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

4.2.3 QCustomer view

QCustomer View is a customer-centric module that provides a comprehensive dashboard focused on

a single customer for residential or corporate customer support, customer complaints management
and issue investigation.

QCustomer View is most relevant to customer care and corporate support teams.

The main features are:

 Comprehensive customer QoE dashboard

360° degrees view of the customer experience, widget based reporting, compare to thresholds and
targets, customer score.

 Ticket management tool

Allows a one or two-way communication with the customer on their reported issues.

 Investigation tool

All-in-one tool on for root cause investigation.

 Easy customer management

Grant or revoke licenses to customers. Send personalized messages.

4.3 QAdmin view

QAdmin View enables the configuration of Scenarios, the follow-up of Customers and Licenses, the
creation of Messages and Surveys.

4.3.1 Nemo Qmon configuration

 Scenarios: create scenarios, import/export scenarios. In each scenario, specific settings can
be added/modified by service (voice, data, application …) and operation mode (OCM, SLM and
SSM). For more information on how to use and configure scenarios, please refer to paragraph
Running a scenario.

 Surveys: design, modify, consult and delete surveys. Manage the questions, their answers,
and the flow of the survey and save surveys as templates to be used in Scenarios, or in a
Page 21
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

particular service or on the Time Based Questionnaire. The Ticket feature also uses the Survey
mechanism.

 Coupons: manage coupons. A coupon is a short code that can be entered on the device to
select a specific scenario. Once entered on the device, the Nemo Qmon will be automatically
moved to the corresponding scenario by the server.

4.3.2 Customers
 Search: search customers using a wide variety of filters (operator, device, OS, installation
date…). A customer has a unique identifier, the Nemo Qmon ID. In normal mode, customers
can also be identified by either their IMEI or MSISDN (availability depending on the SIM). In
Anonymous mode, this feature is not available. From that search menu, it is also possible to
move customers between scenarios.

 Messages: communication module aimed towards anonymous users: select targeted

customers according to a set of criterions, write and send messages using the OS notification
system.

 Top 10 Customers: a report showing the ten most active customers on the server.

4.3.3 Nemo Qmon management

 License installation: install the encrypted license file on the server. To get a license file,
please contact Anite.

 Licenses Overview: provides comprehensive information on the number of Nemo Qmon

licenses with a drill down per OS. Helps to keep track of licenses.

 Nemo Qmon Upgrades: the Nemo Qmon Upgrade tool that allows administrators to manage,
create and deploy new versions of the Nemo Qmon.

4.3.4 Solution settings

 QCustomer View: manage settings for the QCustomer View module, such as the default
dashboard layout, categories of scenarios and thresholds.

 QTrend View: manage settings for the QTrend View module, the breakdown editor or the
map settings.

 Data Enrichment: manage the data enrichment that can be done on the server for every
measurements. A measurement can be enriched with two type of information:

o Customer enrichment: specific attributes attached to the customer that generated the
measurement

o Cell ref enrichment: information coming from the cell ref inventory, based on the CI
and LAC values of the measurement

 Misc: a set of options for the server, such as North Bound Interface (NBI) configuration or
email alerts.

4.4 Running a scenario

4.4.1 Design a scenario

In a scenario, the administrator defines which services are activated on the device, in which service
mode (OCM, SLM, SSM) and the settings for each of those services.

Page 22
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

The configuration of the scenario really drives the behavior of the Nemo Qmon and it has a serious
impact on the end-user experience of their device. A scenario with very few services activated and a
sparse measurement frequency will have little to no impact on the device and will fit a massive
deployment scenario. On the other side, an aggressive scenario with many services activated and a
high measurement frequency will gather a lot of data and is more fitted to a customer care
investigation, but its impact on the device will be more drastic (rapidly draining battery, high CPU
usage).

In this step, the creation of a measurement scenario and all the required settings will be explained.
The following steps are required:

 Define a name, a description, and the global settings (configuration URL, log activation,
roaming activation…),

 Define the scenario transitions (based on date, duration, or location),

 Activate and configure the services required in the scenario.

Before launching a scenario to real customers or to a mass deployment, it is advised to follow the
process below to check the scenario configuration:

1. Check the availability of the Nemo Qmon at the correct URL for each Operating System. Make
sure the latest version of the Nemo Qmon is deployed.

2. Create a new scenario from scratch. Configure the global settings, the activated services and
their settings.

3. Check if the Nemo Qmon behaves accordingly to the settings defined in the scenario, on each
service and on each device if possible.

4. If all is correct, deploy the scenario to the target customers.

Note that scenarios can be imported and exported for easy transfer over different servers or
duplication of scenarios.

4.4.2 Deploy and capture

As a user starts the application for the first time, they will be placed in the default scenario. If they
have a coupon, they may input it at this stage.

Page 23
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

The server is always configured with a default scenario. The default scenario is the one that new Nemo
Qmon units connecting for the first time will receive after validation of their license.

To route new users to a specific scenario, the server administrator can create coupons. These are
short codes that the user can enter on their Nemo Qmon and that will move the customer to a
specified scenario.

A customer can be moved between scenarios. This can be done from the QCustomer View module or
in QAdmin View. The process can be manual and applied to one or several customers, or it can occur
automatically using scenario transitions.

Transitions

It is possible to define transitions between scenarios. A transition will occur either after a pre-defined
duration, at a specific date or based on the customer location. All those options are defined in the
settings of the scenario.

Transitions have been designed to prevent a user to remain indefinitely in a very demanding care
scenario that could degrade the user experience of their device. Using transitions, the customer will
automatically be switched after a pre-defined duration, typically a few days, the duration necessary to
gather enough measurements for an investigation.

It is also possible to transition users at a specific date. This can be useful to gather data during a fixed
period of time and automatically stop the collect after a specific date.

Finally, customers can transition between scenarios based on the device location. This allows for
instance the targeted monitoring of pre-defined locations (e.g. a city or a region).

The transitions can also have license rules attached (e.g. grant/revoke a license to the customer at
the time of the transition).

4.5 Dashboard and reports

Nemo Qview uses a set of dashboards and dynamic reports to display the results of the data collection
on the devices.

The frontend is web-based, with a simple but effective layout supported by AJAX, to create a
responsive web application working well across platforms. Administrators can customize the layout or
use the data export features to export the reports in the format best suited for the business.

4.5.1 Reports
The Nemo Qview reports consist of tables, charts or maps displaying the results of the data collection
by the Nemo Qmon in a comprehensive and interactive way. The results can be filtered for deeper
analysis and drill-down into the data.

The server stores all the collected KPIs for a year by default (up to three year on request and server
load capabilities) and the raw data for a period of three months.

On Nemo Qview, each report provides a tooltip that leads to a complete description of the report.

Page 24
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

4.5.2 Charts
The charts displayed in Nemo Qview are drawn in SVG (Scalable Vector Graphics). The library used for
drawing charts is Highcharts.

Figure 1. Example of a graph using HighCharts

Highcharts is a library written in pure JavaScript, offering an easy way of creating interactive charts.
Highcharts currently supports line, spline, area, areaspline, column, bar, pie and scatter chart types.
It works in all modern browsers including the iPhone/iPad and Internet Explorer from version 6.
Standard browsers use SVG for the graphics rendering. In legacy Internet Explorer graphics are drawn
using VML.

SVG is a mark-up language for describing two-dimensional graphics applications and images, and a
set of related graphics script interfaces.

The chart object is an object representing a single chart in the web page.

The Series object is the representation of each line, area series, pie etc.

A chart can have from 0 axes (pie chart) to multiples. In a normal, single series Cartesian chart, there
is one X-axis and one Y-axis.

The legend is a box containing a symbol and name for each series item or point item in the chart.

Page 25
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

4.5.3 Maps
The measurements can be displayed on a map if the location of the handset is active.

In case the location is not active, the Nemo Qmon collects automatically some radio measurements
(Cell ID/LAC/Mobile Network Code/Mobile Country Code). These measurements will be display only if
the network inventory has been integrated into the system, in this case, the measurement is place at
the cell location.

The Geo-mapping module uses the Open Layers API to represent data on a map.

Open Layers is an open source client-side JavaScript/AJAX framework for overlaying various mapping
services.

For more information on the Open Layers functionalities, please see the Open Layers.pdf annex
document.

Page 26
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

4.5.4 Filters
Filters are available throughout the Nemo Qview server and allow the user to easily search through
the data in order to display only the information they need.

There are two categories of filters: the main filters and the advanced filters. Main filters are applied
everywhere, whereas advanced ones only appear locally on the pages where they apply. Some filters
allow multiple selections of values.

Filter Available Description

Category Filters

General Period This filter enables a quick filter on the period of time, the
possible values are:
Today, Yesterday, last 7 days, Custom.
On Custom, you can define a period by using a calendar.

General Country The values in this quick filter are the country for which there
are data in Database, either voice calls or data sessions. The
country filter applies to the MCC sent by the platform, and
capture at the end of a call or a session.

General Operator The values in this quick filter are the telecom operators for
which measurements have been reported, either voice calls
or data sessions.
The value is based on the MNC registered at the end of a
session or at the end of a call. If the handset is not attached
to any operator, then the first operator recognized by the
end is used.
When a country is selected, this filter will automatically be
updated with the appropriate value, the list of operators for
this country and for which there are data in the database.

General Technology 2G, 3G, 4G, GSM, Wi-Fi

(Bearer)

Page 27
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

Filter Available Description

Category Filters

General Time zone It sorts data and changes hour aggregation according to the
time zone you have selected.

General Scenario Filter on one or several scenarios.

Advanced DQA ID Filter all the data to one single Nemo Qmon

Advanced Aggregation On some reports, you can choose if you want the data to be
displayed in the charts per Hour, per Day (01/01/13) or per
weekday (Monday, Tuesday…)

Advanced Manufacturer / The values in this quick filter are the handset manufacturers
Model and models for which there are data in Database, either voice
calls or data sessions.

Advanced IMEI (Normal The value in this quick filter enables to filter the data
mode only) according to the IMEI.
The IMEI area can contain only the first digits of the IMEI to
search for.
Example: IMEI filter: 213 will filter data with IMEI starting
with 213.

Advanced Detailed Detailed Technology used at the end of a measure or a test.

Technology All possible values are:

Bearer Bearer Group

GPRS 2G

EDGE 2G+

UMTS

CDMA 3G

1xRTT

EVDO_0 EVDO

EVDO_A

EVDO_B

HSDPA

HSUPA 3G+

HSPA

IDEN IDEN

LTE 4G

EHRPD 3G++

HSPA +

WIFI WIFI

ETHERNET ETHERNET

Page 28
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

Filter Available Description

Category Filters

GSM for iPhone store

GSM (2G-3G)
version

Advanced Cell ID Enter the value of the Cell ID you want to filter. Voice
Distribution report only.

Advanced Sort by Application only: Display charts according to another main

information such as data activity, data exchanged or
duration.

Advanced OS Filter per OS.

Advanced Roaming mode Filter on the roaming mode, e.g. Home Network,
International Roaming…

Advanced License status Filter customers depending on their license status.

4.6 Platform Manager

The Platform Manager is a module restricted to Administrators. It gives access to all of the Drupal CMS
features. There are two main goals for this module: manage user rights and create new reports.

4.6.1 Users and rights

User Account creation

The account creation is done via our web API, using Drupal framework. The user can optionally be
notified of his account creation. Integration with LDAP can be also implemented if needed.

Each user can be assigned to one or more group, the interface allows to create/modify or delete the
groups.

The right management is done through the web interface, rights (or permissions) can be assigned to
one or more group of users.

Users Permissions management

Permissions let you control what users can do on Nemo Qview server. Each user role has its own set
of permissions. For example, you could give users classified as Administrators permission to
administer nodes but deny this power to ordinary, authenticated users. You can use permissions to
reveal new features to privileged users (those Export Excel views, for example). Permissions also
allow trusted users to share the administrative burden of running a busy site.

One of the major permission since the 1.8 release is the permission to see only one or several
scenarios. An administrator has the ability to restrain scenario edition as well as access to scenario
results to specific users.

Roles

Roles allow you to fine tune the security and administration of Nemo Qview server. A role defines a
group of users that have certain privileges.

By default, Drupal comes with two user roles:

Page 29
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

 Anonymous
This is a default user that has no user name and password. With anonymous permissions, only
the login page can be accesses.

 Authenticated
Registered users need to authenticate by supplying both a local username and password. The
local username and password, hashed with Message Digest 5 (MD5), are stored in the
database. When the administrator enters a password it is also hashed with MD5 and compared
with what is in the database. If the hashes match, the username and password are correct.
Once a user authenticated session is started, and until that session is over, the user will not
have to re-authenticate. To keep track of the individual sessions, Drupal relies on PHP session
support. For security reasons, the cookie does not contain personal information but acts as a
key to retrieve the information stored on the server's side.

Nemo Qview server comes with additional user roles detailed in the table below.

Nemo Qview role Description

Portal Admin Portal administrator. Gives access to all the available modules and the
QAdmin View menu. Can configure scenarios and manage the customers.
Can switch customers between scenarios. Can create QTrend View reports
and dashboards.

QNetwork View User User that can only access the QNetwork module with read-only privileges.
They can access all of the report details for export purposes to 3rd party
systems or analysis.

QCustomer View Administrator for the QCustomer View module. They can edit the
Admin scenarios.

QCustomer View User for the QCustomer View module. Typically a Customer Care
User representative. Can access all of the QCustomer View pages. However,
they cannot edit the scenarios.

QTrend View Administrator for the QTrend View module. They can create dashboards
Admin and reports.

Administrator Full access to the Drupal administration, capability to modify page content
for other users, to create views, full access to Control Room, full access to
any other feature.

The administrator can always create a new group with specific permissions, according to their needs.

Page 30
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

5 NEMO QVIEW ARCHITECTURE

5.1 Frameworks
The Nemo Qview server provides a rich featured web application with reporting and dashboard
functionalities. It is 100% plug-in free with the highest usability levels and maximum customization
capabilities.

The architecture is based on open standards such as Apache, MySQL, Perl, PHP and HTML. It
leverages Ajax and Web 2.0 technologies to provide lightning speed screens and information loading.
The architecture uses Hazelcast and Elastic Search to provide the necessary horizontal scalability to
support large volumes of data processing and storing.

The Nemo Qview server is pre-configured with common functionalities (user management, multi
languages support, logging activities) while coming with pre-defined dashboard and reports.

The Nemo Qview server is based on the Drupal CMS platform.

Page 31
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

5.2 System overview

The Nemo Qview server solution is based on a three-tier architecture:

 Webserver: this layer exposes the web services required to communicate with Nemo Qmon as
well as hosting the front-end for the Nemo Qview server users. It uses Apache and Drupal.

Page 32
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

 Mediation: this layer is responsible for the processing and indexing of the data collected by
Nemo Qmon. It is based on Elastic Search and Hazelcast.

 Database: this layer is responsible for storing all of the standard ORM data.

Any measurements such as services KPIs or raw data information are directly sent through HTTP or
HTTPS to the mediation layer.

5.3 Requirements

5.3.1 Software
One of the following OS is recommended:

 Linux server RedHat (third party licence is not included in the product)

 Linux Debian

All operating systems should be set up with the default installation. Do not install any additional
software before deploying the Nemo Qview platform.

Always keep your operating system up to date.

Software Version / Description

Web server Apache

Database MySQL Community Edition

Engine PHP

Mediation Elastic Search

Oracle JRE

Backup A backup system is required for the database and configuration

files. It is not included in the product.

Maps By default, Nemo Qview server uses an open source maps solution.
However, it can be configured to use Google maps (third party
licence is not included in the product).

CMS Drupal framework and modules are included in Nemo Qview.

The installation settings, versions, and requirements for each of the software pieces required to run
the Nemo Qview solution are detailed in the release note and server pre-requisites and installation
guides.

5.3.2 Connectivity

Details

Internet Direct Internet connection with a public IP address.

The WLAN setup is not part of the installation. It is the customer’s
responsibility to provide WLAN in case of in-house hosting.

SSH To remotely manage the server, a SSH server must be installed

and running.
The SSH server settings are described in the server installation
guide.

Page 33
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

Details

Certificate If you plan to use an encrypted access to the web server (HTTPS),
the customer must provide a valid web certificate. It can be
obtained from a trusted provider such as Verisign Inc.
(www.verisign.com) or Thawte (www.thawte.com).

5.4 Data security

5.4.1 Network access protocols

The Nemo Qview server uses standard network protocols, like SSH, HTTPS, SFTP.

5.4.2 Availability
The server uses the MySQL high availability for its databases.

Availability refers to the ability to cope with, and if necessary recover from, failures on the host,
including failures of database, the operating system or the hardware and maintenance activity that
may otherwise cause downtime.

Nemo Qview server offers a range of certified and supported solutions, delivering the appropriate
levels of High Availability (HA) and scalability to meet service level requirements.

Selecting the right high availability solution for an application largely depends on:

 the level of availability required,

 the type of application being deployed,

 the standard practices accepted within the customer’s own environment.

The primary solutions supported by MySQL include:

 MySQL Replication

 MySQL Cluster

5.4.3 Integrity
Nemo Qview data integrity use standards third party tool, such as MySQL and Linux to ensure that the
data has complete data integrity. This includes sophisticated levels of transaction support,
synchronous and asynchronous data replication schemes and physical and logical backup mechanisms.

5.4.4 Confidentiality
All of the user confidential data that is transiting between the Nemo Qmon and the Nemo Qview is
sent over secure HTTP (HTTPS).

5.4.5 Traceability
Nemo Qview’s traceability is made through the dblog module available from Drupal.

The dblog core module monitors your system, capturing system events in a log that can be reviewed
by an authorized individual at a later time. This is useful for site administrators who want a quick
overview of activities on their site. The logs also record the sequence of events, allowing for easy
debugging in case of errors on the website.

Page 34
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

The dblog log is simply a list of recorded events containing usage data, performance data, errors,
warnings and operational information. Administrators should check the dblog report on a regular basis
to ensure their site is working properly.

5.4.6 Auditability
Nemo Qview auditability is made through a MySQL plugin integrated in Drupal framework.

The server provides a pluggable audit interface that enables information about the server operations
to be reported to the interested parties. Currently, audit notification occurs for these operations
(although the interface is general and the server could be modified to report others):

 Write a message to the general query log (if the log is enabled)

 Write a message to the error log

 Send a query result to a client

Audit plugins may register with the audit interface to receive notification about server operations.
When an auditable event occurs within the server, the server determines whether notification is
needed. For each registered audit plugin, the server checks the event against those event classes in
which the plugin is interested and passes the event to the plugin if there is a match.

This interface enables audit plugins to receive notifications only about operations in event classes they
consider significant and to ignore others. The interface provides for categorization of operations into
event classes and further division into event subclasses within each class.

When an audit plugin is notified of an auditable event, it receives a pointer to the current THD
structure and a pointer to a structure that contains information about the event. The plugin can
examine the event and perform whatever auditing actions are appropriate. For example, the plugin
can see what statement produced a result set or was logged, the number of rows in a result, who the
current user was for an operation, or the error code for failed operations.

5.4.7 Errors and congestion tolerance

All errors are logged either in databases or in log files available on the Nemo Qview server. This allows
a follow-up of any error occurring on the system.

The Nemo Qview server architecture is based on spoolers, which use the rule “first in, first served”. If
no slot is available when new data is coming, the Nemo Qmon keep the data locally stored and will
retry on regular intervals to upload the data. This mechanism ensures that the server will not have
congestion.

5.4.8 Security against attacks from hackers and viruses

The LAN/WAN connections between the Nemo Qview server and client workstations is considered
secure, i.e. no unauthorized physical access to the LAN/WAN is possible. For this purpose, we
recommend that the server remains protected behind a firewall. Nemo Qview security is based on
Linux security.

Page 35
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

5.4.9 Password policy

A password policy can be defined with a set of constraints that must be met before a user password
change is accepted. Each constraint has a parameter allowing for the minimum number of valid
conditions that must be met before the constraint is satisfied.

Example: an uppercase constraint (with a parameter of 2) and a digit constraint (with a parameter of
4) means that a user password must have at least 2 uppercase letters and at least 4 digits for it to be
accepted.

Current constraints include:

 Complexity constraint

 Digit constraint

 Letter constraint

 Letter/Digit constraint (Alphanumeric)

 Length constraint

 Uppercase constraint

 Lowercase constraint

 Punctuation constraint

 Delay constraint

 Username constraint

 Digit placement constraint

 History constraint (checks hashed password against a collection of users previous hashed
passwords looking for recent duplicates)

The module also implements a password expiration feature. The user gets blocked or is forced to
change his password when his old password expires.

Administrators can force specific users or entire roles to change their password on their next login and
can made a password tab available to users instead of the usual user/#/edit screen for password
changes.

5.5 Interfaces

5.5.1 Imports
Nemo server provides import interfaces that allow the enrichment of the measurements gathered by
the Nemo Qmon. The available interfaces are:

 Cell Ref import: see paragraph Cell Ref for more information on the import of the network
inventory

 Custom fields: it is possible to import data attached to each customer using the custom fields
attached to Customers. This data will allow an easier management and selection of the
customers based on customized and pre-defined fields. See the Qview Admin user guide for
more details.

Page 36
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

5.5.2 Northbound interface

The Nemo Qview North Bound Interface enables periodic dump of all the CSV exports of the details
views to a distant server using the SFTP protocol. Export is working on an incremental process, i.e.
after an initial export, only the new records are uploaded periodically. The interval between the data
uploads can be configured on the Nemo QView server.

5.5.3 Third party

Nemo Qview server has a very flexible architecture, based on the Drupal Framework. This framework
allows the integration with many third party interfaces. Integration with such interfaces is not in the
default installation and should be customized on demand, depending on the requirements.

Examples of third party interfaces:

 Nagios (for server monitoring)

 LDAP

 SNMP

5.5.4 IT & network

The web interface, based on Drupal, provides tool to integrate external databases or external files.
Standards interfaces, such as SOAP, are supported.

Page 37
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

6 INTEGRATION

6.1 MSISDN enrichment

For details about the MSISDN enrichment, please refer to the dedicated document MSISDN
Enrichment.pdf in Annex.

6.2 Cell Ref

That option enables the import of the Network Inventory in the Nemo Qview server. The Network
Inventory must follow a format specific to the Nemo Qview server. A template can be provided on
demand to the MNO.

Once the network inventory has been imported, every measure made on a particular Cell ID/LAC
combination will be enriched with information coming from the network inventory. This greatly
improves the value of the measurement, and allows deeper investigation. The Investigation module of
QNetwork View can make extensive use of the Cell Ref.

The Cell Ref, combined with the GPS location of the measurement, allows for advanced investigation,
such as the calculation of the distance between device and cell, analyse if the best serving cell was the
one the device was connected to

Figure 2. Example of CSV export with cell ref information

Page 38
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

6.3 Nemo Qmon SDK

The Nemo Qmon SDK is a powerful tool that enables the integration of the Nemo Qmon capabilities
into any mobile application, giving this application all of the benefits from the QoE/QoS features of the
Nemo CEM Solution platform.

Provided as a pre-compiled library, it can be integrated into an existing application, or used as a core
set of functionalities to build a custom User Interface.

Sample project with SDK integration

The Nemo Qmon SDK is available on iOS, Android, and Windows Phone. The table below gives an
overview of the features available for each OS and platform version for which they are available.

API Description

Core Init, start, stop the Nemo Qmon

SSM, SLM background modes
Server communication (KPI Spooler, Configuration)

Settings Configuration and user preferences (e.g. GPS location,

WiFi mode…)

OCM OCM tests: start test, stop test, and test progress
(HTTP/FTP, Web, Video Streaming)

Results Access the tests and monitoring results for OCM, SSM and
SLM modes

Page 39
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

7 GLOSSARY

DQA

Nemo Qmon units, the mobile application that collects data on the mobile device.

Nemo Qview Server

Nemo Qview server, the server side of the Nemo CEM Solution. It is composed of three reporting
modules, QTrend View, QNetwork View and QCustomer View, as well as one administration module,
QAdmin View.

KPI

Key Performance Indicator. It allows the evaluation of the performance of a service or an activity. On
Nemo Qview, KPIs are calculated on the server based on the aggregation of the measurements
coming from the mobile devices.

Measurement

A line of values coming from the mobile device generated by an event (e.g. a voice call) or based on a
time with the attached conditions of the device at the moment the measurement was taken (radio
network, location…)

OCM

On Click Monitoring. The active and manual test mode of the Nemo Qmon.

Scenario

A specific set of configuration that can be applied to a Nemo Qmon. It defines the activation and
configuration of the services on the agent.

Page 40
 NEMO CEM SOLUTION TECHNICAL PRODUCT DESCRIPTION

Service

A service is a functional area of the device that can be monitored and/or provide measurements and
results. It can relate to the, Voice, Data, Messaging or time based measurements or feedback. All
services can be configured from the Nemo Qview Server.

SLM

Silent Live Monitoring. The passive monitoring mode of the Nemo Qmon.

SSM

Silent Script Monitoring. The active and automated test mode of the Nemo Qmon.

Page 41