RNO_NPA to NPO

RNO-NPA B9 to NPO B10 Evolutions - All Rights Reserved © 2007, Alcatel-Lucent

All rights reserved © 2007, Alcatel-Lucent9159 NPO - RNO-NPA B9 to NPO B10 Evolutions

9159 NPORNO-NPA B9 to NPO B10

Evolutions

TRAINING MANUAL

3FL12804AAAAWBZZA4Edition 01

Copyright © 2007 by Alcatel-Lucent - All rights reservedPassing on and copying of this document, use and

communication of its contents not permitted without written authorization from Alcatel-Lucent


All Rights Reserved © Alcatel-Lucent 20079159 NPORNO-NPA B9 to NPO B10 Evolutions

2

Legal Notice

Switch to notes view!Safety Warning

Both lethal and dangerous voltages are present within the equipment. Do not wear conductive jewelry while working on the equipment. Always observe all safety precautions and do not work on the equipment alone.

CautionThe equipment used during this course is electrostatic sensitive. Please observe correct anti-static precautions.

Trade MarksAlcatel and MainStreet are trademarks of Alcatel.

All other trademarks, service marks and logos (“Marks”) are the property of their respective holders including Alcatel-Lucent. Users are not permitted to use these Marks without the prior consent of Alcatel or such third party owning the Mark. The absence of a Mark identifier is not a representation that a particular product or service name is not a Mark.

Copyright

This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No other use or transmission of all or any part of this document is permitted without Alcatel-Lucent’s written permission, and must include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from Alcatel-Lucent.

Use or transmission of all or any part of this document in violation of any applicable Canadian or other legislation is hereby expressly prohibited.

User obtains no rights in the information or in any product, process, technology or trademark which it includes or describes, and is expressly prohibited from modifying the information or creating derivative works without the express written consent of Alcatel-Lucent.

Alcatel-Lucent, The Alcatel-Lucent logo, MainStreet and Newbridge are registered trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is subject to change without notice.

© 2007 Alcatel-Lucent. All rights reserved.

DisclaimerIn no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including lost profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not Alcatel has been advised of the possibility of such damages.

Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an endorsement nor a recommendation.

Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment and its operation.



3

Table of Contents

Switch to notes view!1. NPO GSM

1. Introduction

2. Operation

3. Administration



4

Table of Contents [cont.]

Switch to notes view!

This page is left blank intentionally



5

Course Objectives


Welcome to RNO-NPA B9 to NPO B10 Evolutions

After successful completion of this course, you will be able to:

Describe the NPO Server-Client architecturePerform all their operational tasks previously done on A9156 RNO and NPA, using A9153 NPATake profit of the new features & improvements of A9153 NPOPerform typical administrative functions on A9153 NPO



6

Course Objectives [cont.]





7

About this Student Guide

Switch to notes view!Conventions used in this guide

Where you can get further information

If you want further information you can refer to the following:

Technical Practices for the specific product

Technical support page on the Alcatel website: http://www.alcatel-lucent.com

Note Provides you with additional information about the topic being discussed. Although this information is not required knowledge, you might find it useful or interesting.

Technical Reference (1) 24.348.98 – Points you to the exact section of Alcatel-Lucent Technical Practices where you can find more information on the topic being discussed.

WarningAlerts you to instances where non-compliance could result in equipment damage or personal injury.



8

About this Student Guide [cont.]





9

Self-Assessment of Objectives

At the end of each section you will be asked to fill this questionnairePlease, return this sheet to the trainer at the end of the training


Instructional objectives Yes (or globally

yes)

No (or globally

no) Comments

Contract number :

Course title :

Client (Company, Center) :

Language : Dates from : to :

Number of trainees : Location :

Surname, First name :

Did you meet the following objectives ?Tick the corresponding box

Please, return this sheet to the trainer at the end of the training



10

Self-Assessment of Objectives [cont.]


Instructional objectives Yes (or Globally

yes)

No (or globally

no) Comments

Thank you for your answers to this questionnaire

Other comments

Section 1 · Module 1 · Page 1

All Rights Reserved © 2007, Alcatel-Lucent3JK10680AAAAWBZZA Edition 04

Do not delete this graphic elements in here:

All Rights Reserved © Alcatel-Lucent 20079159 NPO · RNO-NPA B9 to NPO B10 Evolutions

Module 1Introduction

3JK10680AAAAWBZZA Edition 04

Section 1NPO GSM




NPO GSM · Introduction 1 · 1 · 2

Blank Page


First editionLast name, first nameYYYY-MM-DD01

RemarksAuthorDateEdition

Document History





Objectives





Objectives [cont.]






Table of Contents

Switch to notes view! Page

1 Overview of A9159 NPO 71.1 Presentation of NPO 81.2 Comparison with previous architecture 91.3 Goals 101.4 Place in the mobile network 121.5 Configurations 161.6 Logical View 21

2 Interfaces with Data Sources 222.1 Overview (multi-standards) 232.2 Loaders 242.3 Dictionaries 25

3 Analysis Desktop 273.1 Overview 283.2 Network Resources Management 323.3 Properties & Functions 333.4 Views Browser 353.5 Right-pane browser 37

4 Questions 38





1 Overview of A9159 NPO






1.1 Presentation of NPO

Network Performance OptimizerMonitors the Quality Of Service of a network in a centralized wayIntegrates all QoS data and QoS services in one application

2G, 3G and WIMAX Networks

QoS Data & QoS Services :

A data warehouse containing all data sources (counters, indicators, parameters, topology…) collected from thedifferent OMC managing the network

Consolidations processes manipulating the data warehouse content: consolidation per hour, day, week and month but also per topology level.

An analysis desktop composed of a graphical user interface that allows browsing and benefiting from theoptimization data of the data warehouse. It allows creating and displaying reports.

External interfaces allowing an external system to extract QoS information from NPO






1.2 Comparison with previous architecture

Replacing the A9156 RNO, NPA and LASER.

NPA A9156 RNOA9157 LASERB10 MR2

A9159 NPO

Advantages:Easier O&M of softwares and databasesFaster access to QoS dataSimple and secure management of LAN

B10MR2B10MR2

A9159 NPO tool supports radio-network-optimization activities and is associated with the Alcatel-Lucent Base Station System, releases B9 and B10.

The NPO software is introduced with the B10 BSS and replaces the previous generation of radio-network-engineering tools: A9156 RNO and NPA. The functionalities of the A9157 LASER product will also be integrated in the future. LASER is not introduced in the release of this course.

Furthermore, it simplifies the maintenance and management of servers and databases :

LASER : Operating System = WINDOWS SERVER 2003 / WINDOWS XP, Database = MS SQL SERVER

NPA : Operating System = UNIX, Database = METRICA

RNO : Operating System = WINDOWS SERVER 2003 / WINDOWS XP, Database = ORACLE

NPO : Operating System = UNIX (Server) / WINDOWS XP (Client), Database = ORACLE

The NPO software architecture is built on up-to-date technologies: full Java server and client, XML and Oracle Enterprise 10g R2 suite (data warehouse).






1.3 Goals

Support radio network optimization activities

Optimization

OMC-R QoSMonitoring

Design

Planning

NPO

ActivitiesCheck the consistency of resource design and configuration

Monitor the QoS

Diagnose the QoS decrease cause

Tune the radio resources configuration

Generate automatically reports for management and operational teams

…






1.3 Goals [cont.]

Provide an effective way to:

HighlightDetect network misbehaviors and QoS degradations

RankHelp the optimization team to focus on the most urgent issues

ActFix the quality of service problems in a quick and accurate way

ManageDecide the corrective actions to apply on the network






1.4 Place in the mobile network

3 possible architectures:1. As an external software application (such as A9156 RNO)

A9159 NPOSoftware application

GSM B9/B10 OMC-R

Max cells : 12000

NPO is the new renovated version of the radio optimization and QoS monitoring product used by many operators in Alcatel-Lucent radio networks up to the B9 BSS release: the A9156 RNO product used in conjunction with NPA and LASER products (note : LASER is integrated in NPO only in release B10 MR2).






1.4 Place in the mobile network [cont.]

3 possible architectures:1. As an external software application (such as A9156 RNO)2. As part of the A1353-MP Multi-Standard OMC Portal (in B10 MR2 : no multistandard)

MS PORTAL

WCDMA WNMS(UA5)

GSM B9/B10 OMC-R

MS NPOMS SUP

B10MR2B10MR2

O&M

O&M

B10 MR2 (MS PORTAL M2 MR2 & NPO M2.3): MONO STANDARD. MS PORTAL is used to increase NPO capacity, but for one RAT only.

max cells = 12000 with MS PORTAL with MS NPO + MS SUP

max GSM cells = 24000 with MS PORTAL with MS NPO only and with cluster configuration

max WCDMA cells = 18000 with MS PORTAL with MS NPO only and with cluster configuration

What is MS-PORTAL :

1. Supervision and Management of several OMC-R's (UMTS or GSM) –- OPTIONAL

2. Collection of QoS of all OMC-R's (ORACLE database located in the MS PORTAL)

3. Provides all functions of a NPO SERVER (the NPO server located in the MS PORTAL)

Therefore :

The MS Portal

- is a centralised management software, for multi-standard mobile networks, to navigate on several 2G and 3G machines.

- supports UMTS and GSM Radio Access Networks, and it is designed to also integrate other Alcatel OMC-R in future releases.

- provides a single access point to the radio networks through a multi-standard desktop and windows.







3 possible architectures:1. As an external software application (such as A9156 RNO)2. As part of the A1353-MP Multi-Standard OMC Portal (in B10 MR2 : no mulstistandard)

3. Embedded in the OMC-R : NPO embedded (NPOe)

NPOeNPOe

OMC-R HMI

NPO Client (PC)

OMC-R Master

NPO with full featuresand capacity < 250 cells

NPOe (NPO Embedded) is NPO with full features within an OMC-R (like NPA embedded) (option available for networks with less than 250 cells). NPO clients can access the application from a PC or from an OMC-R HMI.

NPOE client is named Analysis Desktop and is installed on both OMC master and HMI Master.

NPOE Configurations Hosted by OMC configuration nameNPOE 250 OMC-R (NewHW, NewN HW) Small







As a standard feature, all OMC-R Master & OMC-R HMI provides basicNPO functionalities.

ORACLE database in the OMC-R MasterTypical NPO interface available in each OMC-R (Master & HMI's)Only QoS display (Graphs, reports, etc.)No parameters, no cartography, no tuning, etc.Only storage duration of 8 days (daily values) and 6 days (hourly values)Only aggregation to daily values

OMC-R Master

MPMMPM

OMC-R HMI

NPO with limitedfeatures and capacity up to 6000 cells

MPM (Metrica Performance Management) is NPO with limited features & capacity within an OMC-R server. It allows access to the analysis desktop (NPO main interface) from an OMC-R HMI.

the OMC-R Server contains a NPO server with its ORACLE database.

The MPM client is named Analysis Desktop and is installed on both OMC master and HMI Master.

MPM Configurations Hosted by OMC configuration nameMPM 250 OMC-R (V880, V490) Small

MPM 500 OMC-R (V880, V490) StandardMPM 1200 OMC-R (V880, V490) Large-1

MPM 1500 OMC-R (V880) MPM 1800 OMC-R (V490) Large-2MPM 4000 OMC-R (V880, V490) X-Large

MPM 6000 OMC-R (V490) XX-Large






1.5 Configurations

NPO HMI

NPO Server

IP

• V880/V490 Solaris™ 10• Oracle Server 10g

• ML370 series• Windows® server 2003• Oracle client 10g• Citrix server 4

• Windows XP SP2

NPO Full ClientsLAN

WAN256 kb/s

Citrix client

Citrix® Client 9.0

Webstart client

•Windows XP SP2•Java Engine

By compressing data over the network, the HMI server allows to use low bandwidth networks without decreasingthe performances.

- Full clients: these terminals are directly connected to A9159 NPO server without HMI server. A LAN connection is mandatory for the communication with the server. The NPO client software is installed on these clients.

- Light clients: these terminals are connected to the NPO server through one or several HMI servers. Only the Citrix Metaframe client software has to be installed on this terminal. The NPO client software is running on the HMI server.

In both cases, a 21” screen provides the right resolution for the sophisticated graphical user interface of A9159 NPO. Each client is equipped with an Ethernet-card for communication purposes.

The A9159 NPO HMI server is running under a Windows server 2003 environment on a HP hardware machine. Each HMI server can run up to 10 GUI instances whatever the NPO configuration. Whatever the number of used HMI servers, the global limit of the number of user sessions of each NPO configuration described in the table neext slide cannot be exceeded in order to keep satisfactory performance.

Configuration items PC Server

Model HP Proliant ML 370G4 or G5

Processors 2 x Xeon 3.4 GHz(or more)

Ram Memory 8 Gb DDRam (or more)

Hard disk 36 GB

Operating system Windows Server 2003 (NT5) SP4 Server






1.5 Configurations [cont.]

(*) Uses 2 V480 SUN Servers (nodes) that cooperates as a single system. Based on Oracle Real Application Clusters (RAC).Available in B10 MR2.

MS PORTAL needed

Cluster (*)10 48 NPO24000NPO 24000 (*)

Standalone machine10 28 NPO12000NPO 12000

Standalone machine10 26 NPO10500NPO 10500

Standalone machine10 25 NPO 8000NPO 8000



OMC-RX1(*)250NPOe 250

Hosted By

Max Users Sessions Nb./ HMI Server

Max NPO Users

Sessions Nb.Cells Nb.

NPO Configuration

Name

B10MR2B10MR2

Sun Fire V880 = New HW

Sun Fire V490 = NewN HW

Starting from NPO 5000 configuration, External Disk Bay SE3510 is used.







>= 512 Mb DDRam>= 1 Gb DDRamRam Memory

Windows XP Professional 2Operating system

21 "Monitor

Internal DVD-ROM 16xDVD

SATA or ATA 18 GB / 7200 rpmHard disk

Pentium >= 1.7 GHzProcessor

NPO Light clientNPO Full & Webstartbased client

NPO Clients Configuration

Webstart based client :This feature allows displaying computed views and reports in a web browser of any PC. Requirements on this PC are Web browser and Java 1.5.0 installed.

In both cases, a 21” screen provides the right resolution for the sophisticated graphical user interface of A9159 NPO. Each client is equipped with an Ethernet-card for communication purposes.







SE 3510 : 12x73 GB 15Krpm2 RAID controlers

2 x 146 GB16 GB4 x 1.35 GHzSUN V490NPO 10500

SE 3510 : 12x146 GB 15Krpm2 RAID controlers


1 SE 3510 per V490 with :- 12x146 GB 15Krpm- 1 RAID controlers

1 FC switch

2 x 146 GB per V490

16 GB per V490

4 x 1.35 GHz per V4902 x SUN V490NPO 24000

None12 x 73 GB16 GB8 x 750 MHzSUN V880NPO 8000 (*)

None6 x 73 GB8 GB4 x 900 MHzSUN V880

SE 3510 : 6x73 GB 15Krpm1 RAID controler


None6 x 73 GB4 GB2 x 900 MHzSUN V880

None2 x 146 GB8 GB2 x 1.35 GHzSUN V490NPO 2000

SUN V880See Small OMC configuration

SUN V490NPO 250

External disk arrayInternal disksMemoryProcessorsServer model

NPO Server Configuration

V490V490V880V880

B10MR2B10MR2

(*)NPO 8000 hardware configuration is based on an UltraSparcIII generation hardware and this configuration is proposed for hardware reuse of previous NPA/RNO configurations.

The A9159 NPO server is running under a UNIX Solaris environment on a SUN hardware machine. In each A9159 NPO configuration the hardware is equipped with high performance processors and sufficient memory and disk capacity for an appropriate performance in the optimization execution.

In order to reuse hardware previously delivered with the NPA/RNO applications, two hardware generations are supported as NPO server: UltraSparc III generation (V880 servers) and UltraSparc IV generation (V490 servers equipped with SE3510 external disk array for some configurations).

The A9159 NPO software application has been designed to deal with GSM radio configuration and QoS monitoring. The NPO software architecture is built on up-to-date technologies: full Java server and client, XML and Oracle data warehouse.







10 [ 5*]Max Numbers of users

1 x 72 Gb1 x 36 GbDisks

2 x 2 GHz (dual core)2 x 3.4 GHz (single core)Processor

Windows 2003 Server Enterprise Edition (with CAL servers)Operating system

8 Gb [ 4Gb*]RAM

CITRIX Presentation Server EditionSoftware

DL360 G5ML370 G4NPO HMI Server Configuration

* : Typical configurations of ex-RNO or ex-LASER servers (for reuse purposes)

(*)NPO 8000 hardware configuration is based on an UltraSparcIII generation hardware and this configuration is proposed for hardware reuse of previous NPA/RNO configurations.

The A9159 NPO server is running under a UNIX Solaris environment on a SUN hardware machine. In each A9159 NPO configuration the hardware is equipped with high performance processors and sufficient memory and disk capacity for an appropriate performance in the optimization execution.

In order to reuse hardware previously delivered with the NPA/RNO applications, two hardware generations are supported as NPO server: UltraSparc III generation (V880 servers) and UltraSparc IV generation (V490 servers equipped with SE3510 external disk array for some configurations).

The A9159 NPO software application has been designed to deal with GSM radio configuration and QoS monitoring. The NPO software architecture is built on up-to-date technologies: full Java server and client, XML and Oracle data warehouse.






1.6 Logical View

Optimization (NPO)Optimization (NPO)

Data WarehouseData Warehouse

PlatformPlatform

SecuritySecurity

System & UtilitiesSystem & Utilities

MediationsMediations

Generic LoaderGeneric Loader Generic TunerGeneric Tuner

Loading Plug-inLoading Plug-in Tuning Plug-inTuning Plug-in

OMC-R

(tuneable system)

OMC-R

(tuneable system)OMC-R / RNP

(data sources)

OMC-R / RNP

(data sources)

Migration FacilitiesMigration Facilities

Offline ToolsOffline Tools

ConsolidationsConsolidations MAATMAAT

Administration FacilitiesAdministration Facilities

TomcatTomcat

Administration User Interface

Administration User Interface

NPO BrowserNPO Browser

Analysis DesktopAnalysis Desktop

Diagnostic Dev Environment

Diagnostic Dev Environment

External Systems

External Systems

EQLEQL

Mediations:This sub system is in charge of communicating with all NPO data sources (OMCs, RNPs…) and tunable systems (OMCs).There are different mediation components per type of data source and functional domain (PM data collection, radio parameters…).Data sources:This sub system represents all the possible NPO data providers (for example OMC or RNP systems).Tunable system:This sub system represents the external systems that will get tuning information from NPO (OMCs).Optimization (so-called NPO):This sub system groups all the Network Performance Optimization tools provided by MS PORTAL.- Analysis desktop:- Administration user interface:This sub system is composed of web-based graphical user interfaces that allow performing NPO administration tasks.- NPO Browser:This sub system is composed of web-based graphical user interfaces that allow browsing NPO data such as historical alarms and logs, inventory information.- - MAAT (MUSE Analysis Application Tier):MAAT is a set of cooperating processes offering the NPO optimization services; it is in charge of providing added-value optimization services and allowing to

browse the data (QoS indicator, counters and parameters by translating high level requests into the corresponding data warehouse SQL queries).A part of the MAAT north API is public (visible by the customer through various interfaces); this part is called EQL (Extensible Query Layer).- TOMCAT:NPO needs Tomcat to support the administration pages and dynamic object property pages (JSP/servlets).- Data warehouse:The data warehouse is the central storage containing all NPO data, i.e. the data for all functional domains: Topology, QoS, radio parameters, …Based on Oracle Enterprise 10g R2 suiteIt contains data that vary over time. It contains mostly read only data (read-only once loaded). It integrates data coming from different data sources and

functional domains. It supports cross-domain queries and spatial/temporal aggregations.- Consolidations:Consolidations sub system contains a set of scripts or executables that manipulate the data warehouse content. Most of the functional domains have associated

consolidation scripts - in QoS case - the consolidations sub system is in charge of temporal and spatial aggregations.- Offline tools:This sub system provides a set of tools to load and update NPO metadata. It loads metadata into the data warehouse, checks updates consistency and modifies the

existing database schema.- Administration facilities:This sub system provides tools to manage the data sources (OMCs, RNPs…) declaration, parameters modification and deletion. Data source parameters are used by

the mediation sub system to collect information.It also provides some tools to customize the system behavior (storage durations for instance), import/export data.Legacy RNO/NPA systems:This sub system represents currently installed RNO/NPA systems.





2 Interfaces with Data Sources






2.1 Overview (multi-standards)

BSCMFS

MS-NPO(in MS-PORTAL)

GSM B9/B10 OMC-R

A9155 RNPPlanning

X25X25

IPIP

IPIP

WCDMA WNMS

IPIP

RNC IPIP

WIMAX OMC-RIPIP

WAC IPIP

In the represented case with multiple data sources, NPO will be in the MS-PORTAL.

Data Sources : All the possible NPO data providers (ie RNP, OMCR)

With NPO, less numbers of interfaces with external servers, but more data and processing are required internally.

A9159 NPO is integrated in the environment of Alcatel-Lucent BSS releases. NPO can interface with:

- Two OMC R releases (B9 / B10)

- The current version of A9155 RNP (A9155 V6.x)

The GSM RAN is composed of three main kinds of equipments:

The BTS base station (antenna),

The BSC (controller),

The MFS (packet traffic).

The BSS generates binary PM files and the MFS generates ASCII PM files (QOS). The OMC3 generates ASCII ACIE configuration files (TOPOLOGY) and stores PM Files in an exchange directory.

The UMTS RAN is composed of two main kinds of equipments:

The NodeB base station (antenna),

And the RNC (controller).

The UMTS OMC PM-IM component is in charge of managing RNS PM counter files. Its job consists in retrieving the RNC and nodeB PM counter files and producing one PM XML gzipped file per GP and per RNC (A & B types, 3GPP format). It then exports the produced PM A & B XML files into an exchange directory.

The WiMAX RAN will be composed of two main kinds of equipments:

The Base Station (antenna),

And the WAC (controller).

The BS and WAC equipment interfaces are SNMP based. As UMTS OMC, the WiMAX OMC generates A&B PM files in a 3GPP-like format.

RNP

The ouputs of a RNP tool are planned data (sites coordinates, planned configuration) and maps (vectors or rasters).






2.2 Loaders

Generic loaders and specific plug-ins

DataWarehouse

Files from multiple sources in multiple formats NPO

Loader

Specific Plug-InsSpecific Plug-Ins

CSV files

RNP GenericLoader

RNP GenericLoader

QOS GenericLoader

QOS GenericLoader

Param GenericLoader

Param GenericLoader

NPO contains several loaders. Those loaders are composed of two parts: a generic part called generic loader and a technology specific part (GSM, UMTS, WIMAX…) called plug-in.

The generic loader manages only CSV files; it is in charge of loading them into the data warehouse.

The aim of the plug-in is to convert incoming files into CSV files and to deal with specificities. The plug-in implements an interface defined by the generic loader. There may be several loaders (with different or same plug-ins) for a given technology – for example, in UMTS case, a loader for the RNC files and another one for the NodeB files.






2.3 Dictionaries

NPO relies on dictionaries to describe:Radio parametersQoS Counters and IndicatorsQoS Thresholds (for indicators)Reports & Views templatesDiagnosisThematic LayersRulesReference Values …

Each dictionary can be customized by NPO administrator and system user.

A dictionary is an XML file.

NPO metadata are composed of several dictionaries stored in the database. Metadata are used by the domain components for browsing or computation purposes.

There are two types of dictionaries: system dictionaries and customer dictionaries.

The system parameter,counter, indicator ,report and customer data (mostly threshold values) dictionaries are described in XML format.

The system dictionaries are delivered with the software and must be imported after the NPO installation (refer to NPO Administration Guide)

The customer dictionaries are edited in regards to the operator needs (new indicators or new reports, …)






2.3 Dictionaries [cont.]

NPONPO

Data WarehouseData Warehouse

Administration FacilitiesAdministration Facilities

Admin & System User

DictionaryXML

Creation/modification of user-defined indicators and reports can easily be performed through the AnalysisDesktop.

For standard operation & administration, creation of indicators / reports can be performed thanks to graphicalinterface, there is no need to access the XML files.

Export and Import of XML dictionnaries can be used to transfer dictionnaries from one NPO server to another.





3 Analysis Desktop





3 Analysis Desktop

3.1 Overview

3 Ways to start NPO Analysis Desktop1. Webstart (Java interface)

2. NPO Client application 3. With CITRIX

The user interface is based on an object-oriented design, all actions being accessible through contextual menus. Depending on the selected object(s), only the relevant commands are provided. Most operations can be done through the drag-and-drop mechanism or with the help of menu bars and toolbars.

The main NPO user interface (analysis desktop) is composed of five areas:

Standards and Modes Browser Standards define the technologies available on NPO (GSM, UMTS, WiMAX).

Each standard tab has a set of modes. According to the selected mode, the list of displayed counters / indicators / parameters / reports / views is not the same. It is filtered according to their availability domain.

Topology Classification Browser Radio resources (cells), as well as physical resources (BTS, NodeB, BSC, RNC...) are displayed in tree gadgets and can be selected from there. Different tree gadgets are used to display the network resources by different classification criteria. The classification can be done for example by LAC, hardware topology, cell type, routing area (for GPRS).

Function Classification Browser Functions belonging to a selected network resource from the topology browser are also displayed inside tree gadgets and can be selected from there. This area allows the operator to select: QoS indicators, QoS counters, logical / design parameters, or views / reports

View Browser The view browser is the target place for drag and drop of one or more network resources and one or more functions.

It contains views that are used to display values of logical / design parameters, indicators, and counters.

The displayed data in the view can be exported to Excel for further analysis.

Two mode forms are proposed: tabular and graphical.

Report Browser The report browser is the target place for drag and drop of one or more network resources and one or more views or reports.

A report is composed of several views, each displaying a set of defined indicators or parameters for a user defined report period.

Data displayed in the report can be exported to Excel for further analysis.





3 Analysis Desktop

3.1 Overview [cont.]

Launch the main NPO interface for QoS Monitoring and Optimization

Launch the web interfaces for Administration purposes

Launch the editor to create or modify diagnosis

Launch LASER modules for Remote Inventory and Unavailability modules


















3 Analysis Desktop


Views Browser

Cartography, Diagnosis, Tuning Session

& Reports Browser

Network objectmanagement

FunctionsModes

Standards


















3 Analysis Desktop


Drag and Drop

Drag and Drop

Click

Many operations inside the Analysis Desktop can be done using drag and drop. This facility can be used for

single or multiple objects





3 Analysis Desktop

3.2 Network Resources Management

Radio resources of the network are displayed in tree gadgets and can be selected from there.

Different tree gadgets are used to display the network resources by different sort criteria.

Contextual menu provides additional functions.

Navigation between GSM, WCDMA, WIMAX

WCDMAWCDMA WIMAXWIMAX

The standards define the available technologies: GSM, UMTS, WiMAX.

When one standard is selected, the tab is highlighted. This is called the 'active standard'.

Arrow buttons are available for accessing all standards if they are not visible due to the width of the

standard browser.

Each standard tab has a set of modes. When one mode is selected, it is highlighted. This is called the 'active

mode'

According to the selected mode, the list of displayed counters / indicators / parameters / reports / views and functions are not the same. It is filtered according to their availability domain.

The topology browser comprises:

Topology Classification Tabs These are the set of tabs for topology mode classification.

If all tabs cannot be displayed due to the width of the Topology Browser, arrow buttons appear allowing the user to scroll among all the existing tabs.

Topology Status Bar The topology status bar displays the number of selected objects and the total number of objects. It is dynamically refreshed when the selection changes.

Topology Tree The Topology Tree displays the network objects as a tree, for the selected mode and topology classification.





3 Analysis Desktop

3.3 Properties & Functions

Properties (logical parameters) and functions belonging to a network resource selected in the Network resources management

Contextual menu provides additional functions.





3 Analysis Desktop

3.3 Properties & Functions [cont.]





3 Analysis Desktop

3.4 Views Browser

Spreadsheet mode

Graph mode

The browser can handle several executed views

Tools for further analysis

Contextual menu recaps the side menu

The executed view browser can contain:

One or more network objects

One or more counters / indicators / view templates / parameters (design or logical) / rules / events / free fields / diagnosis.





3 Analysis Desktop

3.4 Views Browser [cont.]

Propagate

Save the executed view as a template

Export to Excel

Spatial Roll up & Drill down

Temporal Roll up & Drill down

Legend & comparisons

Highlights according to comparisons

Rotate the executed view

Clear all filters

Filter repeated value(s)

Filter

Toggle between tabular mode and graph

Zoom in / Zoom out

Display values at cursor

Spre

adsh

eet

mod

e

Gra

ph m

ode

The side bar offers different functions depending on the mode (graph or tabular mode).





3 Analysis Desktop

3.5 Right-pane browser

The right-pane browser allows to display several modules:

• QoS Reports

• Diagnosis

• Tuning Sessions

• Cartography

The executed report browser can contain:

One or more network objects

One or more view templates / report templates.





4 Questions





Answer the Questions

What are the main types of data collected by NPO ?

What are the 3 possible architectures of NPO within a wireless network ?

For a multi-RAT network, what is the only solution ?

If one NPO user is getting a slow bandwidth,which solution is to be implemented in order to increase the performances ?

What is the maximum number of cells that can be seen in one NPO ?





Self-Assessment on the Objectives

Please be reminded to fill in the formSelf-Assessment on the Objectivesfor this moduleThe form can be found in the first partof this course documentation





Summary

B10 MR2 Features :Network unavailability and stability monitoring (LASER)Alarm statistic reporting (LASER)Centralized hardware inventory data management (LASER)Warrantee management (LASER)GoogleEarthTM export (Cartography)Support up to 12k GSM cells (24k with MS PORTAL)





End of ModuleIntroduction





Module 2Operation


Section 1NPO GSM




NPO GSM · Operation 1 · 2 · 2

Blank Page




Document History





Objectives





Objectives [cont.]






Table of Contents


1 Introduction to radio network data 71.1 QoS Counters 81.2 QoS Indicators 111.3 Radio Parameters 23

2 Working with Views Browser 252.1 Execute a View 262.2 Analyse, in tabular mode 332.3 Analyse, in graphical mode 382.4 Favorites 40

3 Basic QoS Monitoring 423.1 Execute a Report 433.2 Analyze a Report 493.3 Collect relevant data 503.4 Create an Object Zone 523.5 Free fields 573.6 Create a Report 61

4 Parameters Checking 714.1 Parameters management 724.2 Tabular Comparisons 744.3 Events detections 764.4 Events Synthesis 774.5 Define Reference Settings 804.6 Assign Classes to Cells 814.7 Customize Reference Dictionnary 844.8 Rules 89

5 Parameters Tuning 955.1 Benefits 965.2 Process 975.3 Interface 985.4 Reference cells 1025.5 Post-its 103

6 Distribution Reports 1096.1 Overview 1106.2 Method 113

7 Import a cartography project 1167.1 Overview 1177.2 Project Structure 1187.3 COF files 1197.4 Format of background map 1257.5 Import 1267.6 Configuration files 128

8 Analyze a QoS problem 1308.1 Presentation 1318.2 Cartography pane 1328.3 Cartography functions 1388.4 Cartography & Tuning Session 1448.5 Thematic Layers 1468.6 Export in GOOGLE EARTH™ 1488.6 Diagnosis 150

9 A day at work with NPO 1559.1 Schedule 1569.2 Know your colleagues 1579.3 Interaction with other teams 1589.4 Scheduled Reports 162

10 NPO Customization 169







10.1 Classification 17010.2 User Preferences 17510.3 Customer Topology Objects 179

11 Annex 18711.1 Indicator Editor 188





1 Introduction to radio network data






1.1 QoS Counters

Performance Management Counters describe events occurring on thenetwork

How many calls in this cell ?How many handovers ? Etc.

There is a specific PM Counter associated to each event (# callsestablished, # call drops, # handovers, etc)

Number of calls = Number of TCH's successfully allocated for a "Normal Assignment" call (normal assignment = not a handover)

QoS means "Quality of Service"






1.1 QoS Counters [cont.]

There are 4 types of counters :

Cumulative (counting a message from or to the BSC)

Status Inspection (every 20s, inspect if a resource is in a certain state)

Discrete Event Registration (detailed information about an event, such as the time and date of an event)

Radio Measurements Statistics (collection of data from the Measurements Reports sent by mobiles)

All counters are counted by the BSC (or MSC in few cases), except the RMS, which are collected in the BTS

Cumulative countersMC01 : Incremented whenever an ESTABLISH INDICATION message is received by the BSC, as a "PAGING RESPONSE"

MC02h : Incremented whenever "ESTABLISH INDICATION" message is received by the BSC as a "MO CALL ESTABLISHMENT"

MC8b : Incremented whenever a "IMMEDIATE ASSIGN COMMAND" is sent by the BSC

MC8c : Incremented whenever a "CHANNEL REQUIRED" message is received by the BSC

MC148 : Incremented whenever "CHANNEL ACTIVATION" message is sent by the BSC in order to activate a SDCCH

C253 : Incremented whenever "CONNECTION REQUEST" is sent by the BSC

C255 : Incremented whenever "CONNECTION CONFIRM" is received by the BSC

MC04 : Incremented whenever all SDCCH sub-channels in the required cell were either Busy or Out of Service, when the "CHANNEL REQUIRED" message was received.

Status Inspection :

MC250 : Average number of available TCH/PDCH timeslots for traffic usage (available = operationnal)

MC28a : Average number of busy TCH radio timeslot (in FR or HR usage) and busy dynamic SDCCH/8 radio

timeslot allocated as TCH.





Exercise

Associate cumulative counters to messages in this protocol (Radio Link Establishment, MO)

MC8c

MC148

MC8b

C255

MCO2h

C253

5 minutes

Refer to the previous slide to find the counters and their definition.






1.2 QoS Indicators

An indicator is a formula of counters

For instance, SDCCH Assignment Unsuccess %SDNAUR = [(MC148 + MC04) – (MC01 + MC02)] / (MC148 + MC04)

i.e. SDNAUR = (# of requests – # of successes) / (# of successes)

There are many families of indicatorsTCH, SDCCH, HandoversGSM, GPRSTraffic, DurationsRMS averages, …






1.2 QoS Indicators [cont.]

Unlike counters, indicators are consolidated !

Temporal aggregationCounters are only hourly, but indicators can be hourly, daily, weekly, monthly or at busy hour.

Spatial aggregationCounters are only available for the basic network element, but indicators can be aggregated at higher levels.





normalisation

QoSfiles

hourly hourly hourly

daily daily daily

weekly weekly weekly

monthly monthly monthly

measured object intermediate object network

temporalaggregation

spatialaggregation

temporalaggregation

temporalaggregation

spatialaggregation

temporalaggregation

temporalaggregation

temporalaggregation

raw

Indics



Measured object : network entity for which is generated the raw indicators (TRX, or cells)

Intermediate object : GPU, BSC, MFS, i.e. it is a spatial aggregation of a subset of "measured objects"

Network : entity of the highest level, i.e. it is a spatial aggregation of all "measured objects"

Consolidations tasks are usually run on regular basis (via scheduling). The scheduler triggers a consolidation job that follows afterwards its own automaton (sequence of operations). Consolidation jobs is followed by the purge tasks, which removes older data in order to maintain the database at a nominal size. Data that are removed can be archived or deleted.

Normalisation is explained in next slides. It is the process of interpolation and synchronization of data.





Σ Qi=80Σ Qi=80

Qi=25Qi=25

Qi=40Qi=40

Qi=15Qi=15

Σ Qi=45Σ Qi=45

Σ Qi=113Σ Qi=113

Σ Qi=27Σ Qi=27

Σ Qi=265Σ Qi=265

N objects aggregated to the parent object

Spatial aggregations are performed each night, started by the scheduler

Aggregated values of day D available only at D+1



Qi = QoS Indicator

Spatial Aggregation, containing the summarizing data of several network elements into one value that defines the parent in the network hierarchy. Example: aggregation of cell data to BSC data.

The spatial aggregation is always done on the normalized data, before the temporal aggregation.

Possible spatial aggregations are: MIN, MAX, SUM, AVG, ...





N periods aggregated to the parent period

Temporal aggregations are performed each night, started by the scheduler

H

D

W

Σ

Σ

Aggregated values of day D available only at D+1



Temporal Aggregation, containing summarizing data of one network element into one value that defines the parent in the period hierarchy. Example: aggregation of raw data to daily data.

When the indicator is defined, it is possible to have several aggregation functions; in this case there are several linked indicators.

Two types of temporal aggregation can be defined:

Stored Aggregation

Calculated Aggregation Calculated temporal aggregation can be used to avoid having too much stored temporal aggregation when it is possible to calculate it using other indicators (on the fly)

Possible temporal aggregations are: SUM, MIN, MAX, BH, 3DAV, ...





Different types of aggregation are available:Total (TOT)Maximum (MAX)Minimum (MIN)Average (AVG)Busy Hour (BH) (only for temporal aggregation)3DAV, …



Busy Hour (BH) : There are two possible busy hours per indicator:

- one for the queries from the Analysis Desktop,

- one for the consolidations.

For each, indicator is associated to a reference indicator. The maximum hourly value of this reference indicator determines the busy hour.

Then the BH value of an indicator is its value during the ‘busy hour’.

The busy hour is determined:

- per day: highest hourly value for the reference indicator,

- per week: the busy hour of the day with highest value,

- per month: the busy hour of the week with highest value

Busy Hour 3 days (BH3) : average of 3 highest hourly BH values for the considered period.

This consolidation is only available per week and month (the 3 values are got from 3 different days).

Busy Hour 5 days (BH5) : average of 5 highest hourly BH values for the considered period.

This consolidation is only available per week and month (the 5 values are got from 5 different days).

Total (TOT) : total of the values for the considered period

Maximum (MAX) : maximum of the indicator value for the considered period

Minimum (MIN) : minimum of the indicator values for the considered period

Average (AVG) : arithmetic average of the indicator values for the considered period






1.2 QoS Indicators [cont.] DELTA RNO-NPODELTA RNO-NPO

If there are missing data :

Two interpolations :

1. If different PM arrive with different periodicity for different objects in order to "synchronize" PM, data are re-arranged. It might lead to missing data : interpolation is ALWAYS linear. Since most objects have the same periodictiy, this might never happen !

2. If data are missing for one whole period.

Step 1 : two parts

1. "synchronization", if measurements are received for different periodicities, it is required to align measurements to a reference period.

2. "interpolation", if there are missing values within one period, it is necessary to interpolate.

Note : interpolation is only performed on demand, during the report execution (and if the dynamic interpolation is enabled in the User Preferences)

Step 2 : "extrapolation", if there are missing values for a whole period, it is necessary to extrapolate.

A period can be an hour (if the real values are measured "hourly", there can't be interpolation within an hour : only one value per hour !), or it can be a day, a week, a month (…) in which case it is possible to have periods without measurements.





With the RNO/NPA tool chain we have only two interpolation possibilities1. Linear 2. Padding by zero

NPO interpolation possibilities was extended1. Linear interpolation2. No interpolation3. Padding4. Only OK 5. Extend


1.2 QoS Indicators [cont.] DELTA RNO-NPODELTA RNO-NPO

The available interpolation methods are:

• padding (missing data are replaced by numerical value given by operator),

• zero (missing data are replaced by ‘0’),

• Linear interpolation,

• OnlyOK: only periods comprising all elementary results are taken into account. If, for one period, one

elementary result is missing, OnlyOK interpolation fills the black with ‘Null’. As a consequence, any

consolidation on a display period containing missing data will result in NULL. This allows to see only

periods for which all data were really collected,

• Extend: reuse of the last value

• there is also the possibility not to do interpolation: This does not fill the blanks at all. As a

consequence, consolidations will be based only on collected data..







It is possible to create a new indicator with NPOClick on

1

2

3

4

5

1 : Create (or copy) an indicator

2 : Fill up all the basic information

(note : calculated indicators must be based on other indicators only, whereas stored indicators can be based on counters as well)

3 : Create the new indicator formula

4 : define thresholds and sampling limit (optional)

5 : Save (click on "Apply")





CALCULATEDINDICATORS



ORACLE DB

BASICINDICATORS

TEMPORAL AGGREGATIONINDICATORS

CALCULATEDINDICATORS

PARAMETERS

COUNTERS



3 types on Indicators : Basic, Calculated & Temporal AggregationInput & Storage policy :


Stored in DB

On-the-fly

Session

Basic indicators can use Counters !

Wehereas Calculated indicators can use only Basic Indicators

On-the-fly : based on stored indicators, the indicator values are computed on demand (each time an user wants to see it on the screen). Most of default indicators are "on the fly".

Session : the indicator (and its formula) are deleted from database as soon as the user exits its current session.







Typical indicators :Copy RTCH_assign_request (GTCNARQN)Copy RTCH_assign_cong_rate (GTCNACGR)Copy RTCH_Erlang_total (GTCTRE)

Explore the contents of each indicator, especially their temporal aggregations

Refer to Annex for additional info

Refer to NPO User Guide §10 Counters and Indicators for a full description and a step-by-step creation.





Exercise

Create one indicator "CD_per_Erl"

Calculated indicatorFormula : Number of call drops / TCH erlang total

Calculated aggregation at busy hourFormula : Number of call drops BH / TCH erlang BH

Use the same reliability indicator as for the TCH erlang total.

Typical thresholds : 5 in rural areas, 2 in urban areas.

Sampling : more than 1 erlang total or 0.2 erlang BH.

5 minutes






1.3 Radio Parameters

A set of parameters defines the operationnal behaviour of one element in the network

BCCH : frequency on which is broadcasted the BCCH# of SDCCH : number of SDCCH subchannels in the cellL_RXLEV_DL_H : threshold to trigger a handover cause 5 (low level in the downlink)EN_DR : flag to activate the directed retry feature

Most of them describe cells, but some can also describe BSC, TRX or adjacencies

There are two main types of parameters :Logical ParametersDesign





Exercise

1. What is the definition of these indicators :HOOBRQRHOOBEFR

2. Extract the 2 indicators from NPOFor 1 cellHourly, for the past 2 hoursDaily, for yesterday

3. Find counters related to these indicatorsHourly, for the past 2 hours

10 minutes

In indicators' properties (contextual menu), it is possible to find the definition and the formula of each indicator





2 Working with Views Browser

DELTA RNO-NPODELTA RNO-NPO






2.1 Execute a View

Views Browser

Network object management

Functions

Cartography, Diagnosis, Tuning Session

& Reports Browser

Modes







2.1 Execute a View [cont.]

To display reports In tabular format (Excel©-like)Or In graphical format (one "view" at a time)

For instance, extract those indicators :Call_drop_rate (QSCDR)RTCH_drop_rate (QSTCCDR)Call_drop (QSCDN)Call_drop_radio (QSCDRN)Call_drop_BSS_remote_TC (QSCDBTN)Call_drop_BSS_int_failure (QSCDBIN)Call_drop_HO (QSCDHN)

Then, extract this viewAlc_Call_Drop


In order to extract a report, you need to define :

A list of entities (a list of cells, for example)

A list of functions (a list of indicators, for example)

A periodicity (hourly, daily, weekly ?)

A date (or a period)

Check next slide for more information !



07/11/2007 07/12/2007 07/14/2007 07/15/2007

62 3 4 522 23 0 118 19 20 217 8 9 104 5 60 1 2 320 21 22 23





After each drag'n'drop, the Execution Context window appears :

Periodicity

Hour, Day, Week, Month : Standard

1/4h, 1/2h : depends on granularity of PM

Raw : same granularity as PM

At BH : at hour of max value for an indicator

Period

If n entities + n functions : only one day ("FROM")

If 1 entity + n functions : more than 1 day

If n entities + 1 function : more than 1 day

Hour format

0:00 = data from 12:00am to 1:00am

9:00 = data from 9:00am to 10:00am

23:00 = data from 11:00pm to 12:00am


If n elements + 1 function, or n function + 1 element, a whole period is available. For instance :

Periodicity = Hourly

Period = From 07/12/2007 00:00 to 07/14/2007 23:00

The result will be a table with PM data from 12th July '07, starting with data between 12am and 1am, until 14th July '07, ending with data between 23pm and 12am.

If n elements and n functions are chose, only one date is available. For instance :

Periodicity = Hourly

Period = From 7/12/2007 00:00

The result will be the value measured between 12am and 1am

List of hours in the report

07/11/2007 07/12/2007

7 8 9 104 5 60 1 2 320 21 22 23







"Trends" provide data for a typical day, a typical week or a typical month.

Trends (only for Indicators)

1. Aggregated values for each hour (0…23) over several days

2. Aggregated values for each hour (0…23) of each day of the week (monday … sunday), over several weeks

3. Aggregated values for each day of the week (monday … sunday), over several weeks

4. Aggregated values for each day of the month (1 ... 31), over several months








The Options tab : QoS Requirements, Sampling/Reliability and Interpolation for indicators only

QoS Requirements

Low, Medium or High. Changes the thresholds for indicators.

Interpolation

Only needed for indicators, and if "dynamic interpolation" = TRUE (see user preferences)

Sampling / Reliability

Sampling : check if sampling is not enough (gray)

Reliability : check if all data are missing before aggregation (italic)








The Options tab : other options

Forecast values

Select the tuning sessions whom forecast values to display (Parameters only)

Event

Overlay events (parameter changes) on a report (Parameters or Indicators, daily only)

Unavailable objects

Filter out NE that are unavvailable, based on a criteria applied on a QoS indicator






Exercise

Let's follow a typical scenario of report analysis1. Clear the views browser2. Extract (1) a list of indicators for all cells in one BSC

Periodicity = DAILY, DAY = YESTERDAY, QoS Requirements = HIGH

3. Extract (2) the same report with QoS Requirements = LOW

4. Extract (3) a list of indicators for few cells, daily, for yesterday.5. Extract (4) a report containing all parameters related to cell

reselection, for all cells of a BSC, for yesterday6. Brainstorming : Define a list of KPI7. Extract (5) those KPIs per BSC, for all BSCs

Periodicity = WEEKLY, DAY = one day last week, QoS Requirements = HIGH8. Extract (6) a report containing BCCH, BSIC, FREQUENCIES and NUMBER

OF TRX per cell, for yesterday

10 minutes


Reports 1 & 2 : in QoS / Call Drop > Call_drop, Call_drop_BSS_int_failure_rate, Call_drop_BSS_remote_TC_rate, Call_drop_HO_rate, Call_drop_radio_rate, Call_drop_rate, RTCH_drop_rate

Report 3: in "RTCH Assignment" and in "RTCH Traffic and Resources" > RTCH_assign_success, RTCH_assign_efficiency_rate, RTCH_Erlang_BH, RTCH_duration_average

At the end of the exercise : 5 reports must be displayed in the view browser of each NPO client Report 1 : call drop indicators yesterday, HighReport 2 : call drop indicators yesterday, LowReport 3 : traffic indicators yesterday, LowReport 4 : cell parameters yesterday (cell reselection)Report 5 : BSC indicators, last week, HighReport 6 : cell design yesterdayDon't delete them, they will be use in the next exercise !

KPI : Key Performande IndicatorsList of KPI (to fill up) :1. … 5. …2. … 6. …3. … 7. …4. ... 8. …






2.2 Analyse, in tabular mode

The side bar provide advanced tools for analysisLegend and comparisonsPropagationFilterRoll up / Drill down, …Refer to "Introduction §4.3"

Therefore, it is not necessary to export to Excel to perform an analysis

By doing the exercise next slide, you will learn about these tools






Exercise 1/4

Report 1Filter cells with RTCH drop rate > 3.0 %Select and propagate these cells

How many cells ? Answer : Remove the filterHighlight and open the legend : select and propagate all cells that exceed the orange threshold for the RTCH drop rate

How many cells ? Answer :

10 minutes

FILTER and LEGEND






Exercise 2/4

Report 2Highlight and open the legend : select and propagate all cells that exceed the orange threshold for the RTCH drop rate

How many cells ? Answer : Order the cells : highest call_drop_BSS_remote_TC_rate on top

Which cell is the worst one ? Answer :Select and propagate this cell. Find this cell's TRXs :

Which TRXs of this cell have the same problem ? Answer :Perform a spatial roll up (x2) on report 2

Is the problem impacting the BSC ? Answer :

ORDER, PROPAGATE & ROLL UP






Exercise 3/4

Report 3Spatial drill down to check TRX traffic on those cells

Is there any TRX that carries no traffic ?Temporal drill down to check hourly traffic evolution for those TRX

Is there any activity ?Temporal roll-up (x2) to check weekly traffic

DRILL DOWN & ROLL UP






Exercise 4/4

Report 4Rotate the viewHighlight

Is there any threshold exceeded ? Answer :Select BSC with highest CDR

Temporal drill down, is there one day with high CDR ? Answer :Temporal roll up, what is the monthly CDR ? Answer :Spatial drill down, is there one cell(s) with high CDR ? Answer :Spatial roll up, what is the CDR for the network ? Answer :

ROTATE, DRILL DOWN, ROLL UP







2.3 Analyse, in graphical mode

Instead of working with tabular data, graphics are available

What is a View ?A graphic based on several QoS indicatorsDesigned by the user (a set of standard views is proposed by default)In the tab "View"

Same set of advanced tools :Legend and comparisonsPropagationRoll up / Drill downNavigation & DisplayToggle back to tabular mode






Exercise

Close all current tabs in the views browserExecute "Alc_call_efficiency" and "Alc_RTCH_capacity"

DailyFor the past 5 daysFor 2 cells

Verify that both reports will allow a drill down at TRX levelPossible ? Answer :

Select one view :Zoom in and outToggle between graphical and tabular modesPerform a spatial drill down & roll upPerform a temporal drill down & roll up 5 minutes

When performing a spatial drill down on a BSC, it executes a view for EACH cell in the BSC ! It can take a lot of time.







2.4 Favorites

Favorites are a simple way to save a selection of functionsIt is especially useful with QoS Indicators. The list of indicators chosen before can be saved !







2.4 Favorites [cont.]

To organize favorites :Menu bar : "Data > Favorites > Organize …"Drag and Drop indicators from one group to another group

One group of favorites can contain multiple sub-groups

Call Setup Success RateTCH Assignment Unsuccess

TCH_Assign_Fail_RadioTCH_Assign_Fail_BSSTCH_Assign_CongTCH_Assign_prep_fail_BSSTCH_Assign_Unsuccess_Rate

SDCCH DropSDCCH_drop_radioSDCCH_drop_BSSSDCCH_drop_rate

Call_Setup_Success_rateSDCCH_assign_request

Main Group "Call Setup Success Rate" (10 indics)

Sub Group "TCH Assignment Unsuccess" (5 indics)

Sub Group "SDCCH Drop" (3 indics)






3 Basic QoS Monitoring






3.1 Execute a Report

What is a Report ?Stack of several ViewsDisplays a set of QoS IndicatorsAdvanced tools for analysis still available

5 families of QoS Reports






3.1 Execute a Report [cont.]

Drag and Drop several NE with several reports in the Reports Browser

The Execution Context window appearsIdentical to the Execution Context window when using the Views BrowserRefer to § "Working with Views Browser"

Fill up the required information





Exercise

Connect each family to its specificityYou are welcome to use NPO in order to understand the difference between each family

Mono Object DistributionMono Object Distribution

Mono Object EvolutionMono Object Evolution

Multi Object ComparisonMulti Object Comparison

Multi Object EvolutionMulti Object Evolution

WarningWarning

1 NE, n indicators, n periods1 NE, n indicators, n periods

n NE > threshold, 1 periodn NE > threshold, 1 period

RMS matrices & vectorsRMS matrices & vectors

n NE, n indicators, 1 periodn NE, n indicators, 1 period

n NE, 1 indicator, n periodsn NE, 1 indicator, n periods

NE : network element (i.e. a cell, a TRX, a BSC, …)

1 NE means only one network element per view

n NE means several network elements per view






3.1 Execute a Report [cont.]

Notice that Reports are available for different NE's






Exercise 1/2

For each need, find the appropriate report1. QoS manager needs an overview of the GSM network2. O&M team needs to verify call drop causes on one cell3. GPRS team needs the transmission resources usage of

each GPU's (and Ater's) of one BSC4. Optimization team wants the list of the 10 cells with the

worst SDCCH drop rate5. Design team needs to check the traffic split between a

cell and its neighbours6. Design team needs to check the call efficiency rate

among the different TRX of a cell7. An optimizer changed an adjacency parameter and needs

to check the evolution of HO flows between a cell and its neighbours

20 minutes

Advice : check the properties of a report, in order to know how the result will look like.





Exercise 2/2

By checking the properties of "Alc_Mono_QoS", you can read its template. Answer the following questions :1. How many views ?2. What is the name of the 1st view ?3. Can you find it among the Views in the functions browser ?4. How many indicators ?5. Which ones are on the primary axis ?6. On the secondary one ?7. Why ?Execute the 1st QoS view for one cell, for the last 10 hoursExecute Alc_Mono_QoS for the same cell, for the past 10 hoursObserve …

This exercise introduces the method to create a report, based on reverse engineering : by understanding why a report looks this way, it will be a piece of cake to create your own report !





All advanced tools for analysis are availableLegend and comparisonsPropagationRoll up / Drill downNavigation & DisplayToggle back to tabular mode, …

Export to Excel provides a way to share the results with different teams

Specific tools for reports are :Link cursorsLink zooms

Resize Legends


3.2 Analyze a Report DELTA RNO-NPODELTA RNO-NPOB10MR2B10MR2






3.3 Collect relevant data

Default data might not suit your needs !

You must customize NPO …Create new object zonesCreate new QoS data (indicators, views, reports)

How can I compare CDR between

GSM900 cells and DCS1800 cells ?







3.3 Collect relevant data [cont.]

What is an object zone ?Subset of NE's that verifies a filterFilter(s) are defined by the user

To put it simply, an object zone is an intermediate step in the consolidation of indicators

Naming conventions :

Traffic ZoneTRXs from same zone, same frequency, same cell split, and within the same cell

Generic ZoneOthers

TRX ZoneTRX's

Cell ZoneCells

Name of the object zoneType of NE's


An object zone can be created from any network element ! GPU, BSC, A interface, etc…

The traffic zones are AUTOMATICALLY generated by NPO.






3.4 Create an Object Zone

Object zones


Click on the tab "Cell zone", "TRX zone" or "Generic zone"

Open the contextual menu, and click on Open Zone Manager






3.4 Create an Object Zone [cont.]

1

2

3

4


1 : Create a new zone

2 : Name the zone, define access rights (private : only editable by the owner), and most importantly define the object type (e.g. by choosing CELL2G, the user will create a CELL zone)

3 : Create filters that will define the zone (cf next slide)

Visible : Checked All NPO operators can see the zone, Unchecked Only NPO administrator can see it

Auto-compute : the object zone is automatically computed at opening of a session (takes more time)

Families : to fill manually, it puts the zone within a certain directory (cf. left pane of the window)

Filter / Object Zone / Working Zone : it is possible to base a filter on an existing object zone or working zone

for instance : object zone = the intersection of two object zones (already defined)

Criteria : fill in this field by using drag and drop from the right pane !

Reference period :

Daily / Weekly / Monthly : period of measurements (for indicators only)

Absolute: the date used to retrieve the data is fixed. Otherwise, it is relative (for instance day – 1, which is yesterday, whichever the date the object zone is computed)

(Therefore, it is possible to retrieve older data for parameters, indicators, etc.)






3.4 Create an Object Zone [cont.]

Logical operatorsINTERSECTION(1,2) = 1 AND 2

UNION(1,2) = 1 OR 2

EXCLUSION(1,2) = 1 XOR 2

1 2

1 2

1 2






Exercise

Create the following zones :1. Cells from BSC 12. Depending on your network, create one zone per "CELL

TYPE" AND per "FREQUENCY RANGE" (single, umbrella, mini, micro or indoor)

3. Cells with at least one TRX with TCH assign efficiency % < 90% and TCH allocated > 200, and that belongs to BSC 1

4. TRX with TRX PREF MARK = 0 and belongs to cells which have more than 3 TRX

5. TRX with less than 1 erlang per day6. GPUs from BSC 1 and BSC 2

15 minutes

Close the Zone Editor, and find your Zones in NPO"Compute" each zone

How many NE's for each zone ?

3

4

5

6

2

1

# of NEZone


Create all zones in a special family (= your first name), in order to ease deletion of these objects after the course.

These exercises can work on all network, but feel free to adapt them to you own network configuration.





Exercise

Provide the following data :Weekly CDR, CSSR, RTCH DROP BSS RATE for the NETWORK, for the past 7 weeks (Tabular Spreadsheet)

What is the weekly CDR for last week ?

Hourly "Alc_Mono_QoS" for BSC 1, starting from yesterday 00:00 until now (Mono Object Evo Report)

Do you see a difference when doing it from "BSS mode" or from "Cell zone" ?

Display RTCH duration avg, RTCH assign success, TRX RTCH Drop Rate (Radio, HO and BSS) for all TRX with less than 1 erlang / day (Tabular Spreadsheet)

Using Filters, can you find TRXs with high CDR, high amount of success and short duration average ?

10 minutes


There is no need to create a new zone

For the second question, extract 2 reports : using

1. the mode "BSS", select "BSC 1" and extract the report.

2. the first cell zone (BSC1) created during the previous exercise.






3.5 Free fields

You want to create a new cell zone

But what if you can't find a common point between several NE's ?

You need to attribute an additional information to each cell !

1. Create manually a "CSV" file, following a specific format2. Import the "free fields" file within NPO

With NPO interfaceOr with command line

?


It is recommended to use EXCEL to create the file :

Check your regional settings : list separator should be semi-colon (;)

1. (Re-)Open Excel

2. Fill up a table following the standard "free field" format (cf. next slide)

3. Save As "comma delimited .csv" format

Your file is saved as a text file, delimited by semi-colon ( = CSV format). Now you need to "clean-up" the file.

1. Open this file with notepad

2. Remove the excess of ";" in the first line

3. Save

Now your file is ready for import.






3.5 Free fields [cont.]

File format for "2G cells" free fields

File format for "other NE's" free fields

FREE FIELD;<optionnal comments>CELL_MCC;CELL_MNC;LAC_ID;CELL_ID;<field1>;<field2>;…53;20;3;50010;<value1>; <value2>;…53;20;3;50011;<value1>; <value2>;…53;20;3;50012;<value1>; <value2>;…53;20;3;53230;<value1>; <value2>;…53;20;3;53231;<value1>; <value2>;…53;20;3;53232;<value1>; <value2>;…

FREE FIELD;<optionnal comments>; <optionnal comments>;<TYPE>OXEID;<field1>;<field2>;…GPU_BSC1/2/16779009;<value1>; <value2>;…GPU_BSC1/2/16779010;<value1>; <value2>;…GPU_BSC1/2/16779011;<value1>; <value2>;…GPU_BSC2/2/16779776;<value1>; <value2>;…GPU_BSC2/2/16779777;<value1>; <value2>;…GPU_BSC2/2/16779778;<value1>; <value2>;…

(*) LAC_ID : depends on mode CI or LAC/CI


If NPO is in LAC/CI mode : CELL_MCC;CELL_MNC;LAC_ID;CELL_ID

If NPO is in CI mode : CELL_MCC;CELL_MNC;CELL_ID

(this choice is done at NPO installation)

For other NE's, TYPE = GPU, PVC, CELL3G, N7_SL, etc. (cf different names in the "Mode" pane of NPO)

To know the mode of NPO : read \alcatel\muse\MUSE_COMMON\config\common.properties : CI_MODE=false (means at installation, the mode LAC/CI have been chosen)

Never edit this file !!!






3.5 Free fields [cont.]

Import Free Fields with NPO Import/Export Management

Browser for your file and import it


Details for Free fields import : "NPO Administrator Guide §4.1.16 and §4.2.15"

To load a free field with a script :

Run as root the following commands:

cd /alcatel/muse/MUSE_QOS/topology/bin

./loadFreeFields.sh <fileName>

Where <fileName> is the absolute path and name of the Free Fields file.

Example:

./loadFreeFields.sh /files/FF.txt

The OEXIDs in the free fields file should match the ones imported by either the Qos/Param topology import of the customer topology import.





Exercise

Each client :Create a Free Field file (from scratch)Import the MNC / MCC / CELL ID (and LAC ID) from NPOCreate 2 new fields : CITY and PROVINCEFill up the columns with random data

Ex : cities = Lannion, Stuttgart, Shanghai, Timisoara, …Ex : provinces = South, North, …

Import in NPO, using NPO Import/Export ManagementCreate a Cell Zone for one province

10 minutes







3.6 Create a Report

View (1)

Primary axisSecondary axis

Legend







3.6 Create a Report [cont.]

Methodology1. Define the purpose of this report2. Define all indicators you need3. Distribute indicators per view4. Distribute indicators per axis5. Create the views6. Create the report

View Editor toolClick on

Or Data > Views Templates

Or "Ctrl + E"


Report Editor toolClick on

Or Data > Reports Templates

Or "Ctrl + R"







12

3

4

5

Existing views Properties of a view List of functions & properties

6

1 : Create a new view (or copy an existing one)

2 : Fill up necessary information (name, title, family, etc.)

3 : Choose the functions/properties to display in the tabular view

4 : Choose the functions/properties to display on the first axis (left Y-axis)

5 : Choose the functions/properties to display on the second axis (right Y-axis)

6 : Apply to save

Rule : in one axis, display only indicators (or parameters) using the SAME UNIT !!!!

Preferred display type : when executing the view, do you prefer to display the tabular view or the graphical view first (both are accessible using the switch button tabular/graphical anyway)

Filtering indicator / Sorting indicator / Sorting direction : used for warning reports







1

2

3

4

1 : Create a new report (or copy an existing one)

2 : Fill up the necessary information

3 : Drag and drop the view in the report (you can change the order by using the up/down arrows)

4 : Apply to save







Distribution reportsBased on Matrix or Vector indicatorsRelated only to RMS and GPRS Distribution indicators1 view / indicatorUser can customize the cosmetics only

When creating a matrix, all parameters are already defined (intervals of X and Y axis, for instance)

The user can only define new intervals for the colors (most of the time, it relates to the number of samples)







Warning reportsBased on a standard viewsAdditional information for filtering :

Additional info in "report editor"

Additional info in "view editor"

Top N : top cells with best or worst values of "filtering" indicator

Top N variation : top cells with variation of "filtering" indicator above "variation value"

Color Filtering : all cells with "filtering" indicator with the color "value filtering on color"

Variation Filtering : all cells with variation of "filtering" indicator above "variation value"

Before and After : additional display of "filtering indicator" values for N days before and M days after the date chosen in execution context window.

Reference period : used to compute the variation value. If reference period = 3 and the periodicity chosen in execution context window = WEEK, then

1. Absolute variation :

variation(filter indic) = filter indic value(week ref = week_x - 3) - filter indic value(week_x = week chosen in execution context window)

2. Relative variation :

variation(filter indic) = [filter indic value(week ref = week_x - 3) - filter indic value(week_x = week chosen in execution context window)] / filter indic value(week ref)





Exercise 1/4

All together, design a report for daily monitoringPurpose = GSM daily monitoringWhich indicators ?In which views ?On which axis ?

Each group will create one viewOnce all views are created, each group will copy others' viewsEach group will create a new report

20 minutes

STANDARD REPORT


Don't forget to create your views and your reports in your own "family"





Exercise 2/4

Create a report with 2 views :1 matrix "DL RxLev vs Quality"1 vector "Path Balance"

DISTRIBUTION REPORT







Exercise 3/4

Edit your own view refering to CDRSet the missing "warning" information

Filtering indicator = RTCH Drop RateOrdering indicator = RTCH Drop RateBased on "orange + red" thresholdDisplay 5 days "before", 0 days "after"

Save, and copy this viewChange the warning information

Filtering indicator = RTCH Drop RateOrdering indicator = Call Drop (number)Worst 20 cellsDisplay 2 days "before", 0 days "after"

Create a warning report, containing these 2 views

WARNING REPORT



The report 1 teaches very important rules :

RULE 1 : Always associate a number to a rate !! A rate itself does not give enough information for analysis.

For instance : numbers on the left axis, rates on the right axis

RULE 2 : Fill up the legend

RULE 3 : Keep the same convention for all the reports, to ease the reading

For instance : radio problems = YELLOW, system problems = PURPLE

requests = BLUE, success = GREEN, etc.





Exercise 4/4

4. Exit the Report Editor, and execute your 3 reportsReport 1 : good for daily monitoring ?Report 2 : difference between matrix and vector ?Report 3 : difference between the two views ?

EXECUTION



The report 1 teaches very important rules :

RULE 1 : Always associate a number to a rate !! A rate by itself does not give enough information for analysis.

For instance : numbers on the left axis, rates on the right axis

RULE 2 : Fill up the legend

RULE 3 : Keep the same convention for all the reports, to ease the reading

For instance : radio problems = YELLOW, system problems = PURPLE

requests = BLUE, success = GREEN, etc.





4 Parameters Checking






4.1 Parameters management

The parameters are imported from OMC-R to NPO every night

Open NPO DATA MANAGEMENTSelect Configuration System Scheduling

What time is your parameters import ?

NPO will keep track of all daily configurations, for a duration of "MAX PREVIOUS DAYS"

Open NPO Administration – Data Management :Select Configuration > Data SourceChoose an OMC-R, Click on "Update", "Next"Check the MAX PREVIOUS DAYS field

How long are your daily configurations stored ?


To change the storage duration of your parameters, refer to "NPO ADMINISTRATION GUIDE", p.21 , §3.2.2 "Configure Parameters Storage Duration"

Click on "ADVANCED" button to edit this number of days.

Otherwise :

On NPO server, open a console

Type :

> more /alcatel/muse/MUSE_ADMIN/config/paramStorageDuration.cfg






4.1 Parameters management [cont.]

NPO can compare operationnal parameters with other values :

Operationnal parameters vs.

Parameters checkings can be fully performed on NPO !Tabular comparisonsEvents detectionsEvents synthesis

Historical values (from previous days)Reference values (from your default settings)Forecast values (from tuning session)

Two families of parameters :

Logical parameters : parameters that controls the algorithms (handovers, reselection, gprs, etc)

Design parameters : frequencies, capacity, neighbours, coordinates, etc.






4.2 Tabular Comparisons

Drag and Drop

Navigate betweenoperationnal andreference values






4.2 Tabular Comparisons [cont.]

The legend and highlight tools allow to compare operationnal values with other values

In the Legend window, you can select only cells which do not follow reference values :Green : Green : OPE = REFOPE = REFYellow : Yellow : OPE OPE ЄЄ REF boundariesREF boundariesOrange : Orange : OPE(day=d) OPE(day=d) ≠≠ OPE(day=dOPE(day=d--1)1)Red : Red : OPE OPE ЄЄ REF boundariesREF boundaries







4.3 Events detections

Events show when a key information is changedHighlight a logical/design parameters changeHighlight a topology change

An event is represented by a graphical symbol :







4.4 Events Synthesis

Overlay additional information on a reportSame mechanism as "Events Detections"Choose "Display Event Synthesis" in the Execution Context






Exercise 1/2

Extract a report containing all parameters related to cell reselection, for all cells of a BSC, for yesterday

Use the legend to compare operationnal settings with reference settingsIs there a discrepancy ? Answer :

Select and propagate cells with discrepanciesHow many cells ? Answer :

Select and propagate parameters with discrepanciesHow many parameters ? Answer :

PARAMETERS & PROPAGATION

20 minutes






Exercise 2/2

Check all changes on all cells of a BSCPeriod : last 30 daysWas there any change ? Answer :

Check the details for one eventWhat exactly was changed ? Answer :What was the initial value ? Answer :What is the changed value ? Answer :

Check that all "cell reselection" parameters follow the reference valuesLegend with source = operationnal, target = referenceSelect all "red" cellsPropagate the selected cellsHow many cells ? Answer :







4.5 Define Reference Settings

In order to compare operationnal settings with your own reference settingsPreparatory steps :

Define reference settings per cell type, per frequency band, per cell class, etc.Assign cell classes

Cell class : family of cells, user-defined. Give more flexibility to references than the cell type. For instance :- DENSE URBAN, URBAN, RURAL, INDOOR (Alcatel default classes)- RAILWAY, TUNNEL, AIRPORT, COLOCATED, … (examples)


Cell type, frequency band, cell class can be combined in order to provide very specific sets of references :

UMBRELLA MULTIBAND URBAN set of parameters A

UMBRELLA GSM900 URBAN set of parameters B

MINI MULTIBAND URBAN set of parameters C

MINI GSM900 URBAN set of parameters D, …






4.6 Assign Classes to Cells

With NPO Analysis Desktop interfaceSeveral cells can be changed at once







4.6 Assign Classes to Cells [cont.]

With a planning project importAlong with geo-data, cell class can be defined by RNPRefer to chapter "Import a Cartography Project"







4.6 Assign Classes to Cells [cont.]

How to create a new class ?In menu bar, choose "Topology > Network Object Class"

1

2

3


1 : create a new class

2 : Fill in the required information (system class : while displaying a cell that belongs to this class in the cartography, which layout should it use ? Indoor = small icon, rural = large icon)

3 : apply and close






4.7 Customize Reference Dictionnary

In order to compare operationnal settings with your own reference settings

All references are contained in the Reference Dictionary

Create an Excel® file :One sheet contains references for one object typeReferences for one object type can be split over several sheetsThe file is mono-release

Example of reference file : for release B10, one sheet per family of parameters


Reference values are Excel files that express the default value that a parameter

for a given network object should have.

These values depend on the network object configuration, i.e. values of other

parameters (for example, for GSM cells, on the cell type and cell class: urban,

rural, number of TRX…).

Alcatel publishes reference values for the parameters of its equipment. Some

operators directly use Alcatel-Lucent reference values, others change them to better

suit their needs.






4.7 Customize Reference Dictionnary [cont.]

The first sheet must contain the file header :

Next sheets can contain this simplified header :


Description in NPO User Guide §12.1.3







Columns header and contents, in each sheet :

Default values

Parameters names

Criteria : if a cell verifies a criterion, associated references are used(the criteria are checked from right to left)


Beware, the first sheet does not have the same header in lines 1 … 3 (cf previous slide)

If a criterion is verified, but there is no reference value associated, then the process continues : the next criterion is checked, etc, until reaching the "default"

A criterion is an expression that follows a precise grammar. Refer to NPO User Guide §12.1.7.







Typical Process1. Open NPO Import / Export Manager2. Export the Parameter Reference Values for your release3. Edit the file with Excel®, include your references (then Save, Close)4. Import the new Excel® file thanks to the NPO Import / Export Manager

NPONPO

Import / Export ManagementImport / Export Management

Data WarehouseData WarehouseAdmin

OPEN Imp/Exp Mng

EXPORT FILE

IMPORT MODIFIED FILE

1

4

2

3

EDITION






Exercise

Change a reference and observe the changesExport the GSM B10 Parameter Reference ValuesModify CELL_RESELECT_OFFSET reference

If cell = MINI 900 CRO = 2dB [0;2]If cell = MINI 1800 CRO = 4dB [2;4]If cell = MICRO CRO = 6dB [4;8]Otherwise, CRO = 0dB [0;2]

Import the new file (one group after the other)Check properties of CELL_RESELECT_OFFSET

Do they follow your new values ?Execute a tabular view for all cells, with the logical parameter"CELL_RESELECT_OFFSET"Highlight the legend

Do you see the impact of changing the reference values ?

20 minutes


Cell Reselect Offset is located in the sheet "Cell Selection"

The purpose of this parameter is to favour the reselection of the cell by x dB.

CRO = 6dB [4;8] means :

Reference = 6dB

Min = 4dB

Max = 8dB






4.8 Rules

A rule is reflecting the dependency between 2 or more parameters

For example :A_LEV_HO > A_LEV_PC :

Power control averaging window for signal level has to be short to give a good reactivity to the Power Control algorithm. Handover averaging window for signal level has to be long to mean correctly the high fluctuations of the propagation channel.

IF Number_Of_TRX = 2 THEN Number_Of_SDCCH BETWEEN 8 AND 16This rule checks if the cell is having the right number of SDCCH channels according to the number of TRXs.

It is a quick check of all parameters of all NE's !






4.8 Rules [cont.]

The rule expression is verified

The rule expression is false, and the rule severity is "WARNING"

The rule expression is false, and the rule severity is "ERROR"

Note : you can drag and drop a rule from the tab "rules" to the tabs "logical indicators" or "design". It will automatically select the parameters that are used in the expression.

As shown on the picture, it is possible to apply the legend.






4.8 Rules [cont.]

To add or change a rule:Same process as changing a reference valueExport the Rules dictionary as an Excel® fileModify/Add the expressionsImport the modified Excel® file

NPONPO

Import / Export ManagementImport / Export Management

Data WarehouseData WarehouseAdmin

OPEN Imp/Exp Mng

EXPORT FILE

IMPORT MODIFIED FILE

1

4

2

3

EDITION


Refer to NPO User Guide §13.1 for a full description of the file (file header, column header, content)






4.8 Rules [cont.]

File header : only one per file, in the 1st sheet

Body for CELL2G


Export this file from the server.

FILE HEADER (only one per document):Supplier : A value among

• Standard: for rules defined by the standard itself

• Alcatel-Lucent : for rules defined by Alcatel-Lucent

• Customer: for rules defined by the customer

Type : Type of the network object the rules apply on. It must be a MUSE type as defined in the topology metadata. (e.g. CELL2G)

The same type can be used in several sheets

BODY HEADER :

A The name of the rule. It must be unique among all rules.

B The type of the Rule (e.g. System or Expert): can be actually any free text.

C The Rule Severity. A value among (case insensitive): • ERROR • WARNIN

D The visibility: If any text is present, (e.g. X) it means true. (default is false)

E The Function, i.e. the family and subfamilies in the form <family>/<subfamily1><subfamily2><subfamily3><subfamily4>. The number of sub families can be 0 to 4. The family itself is optional.

F The description of the rule.






4.8 Rules [cont.]

This rule is checked on concentric cells only

These rules are checked for all cells except class = indoor


G The Rule expression. It must validate the grammar given in NPO User Guide §12.1.7 "Expression Grammar".

H The Rule condition that defines when the rule applies. It must validate the grammar given in Annex.

Starting from column "I", an additional set of conditions, based on CELL TYPE, CELL CLASS, CELL FREQUENCY RAGE and CELL BSS RELEASE.

If there is any text (such as "X" for example), then the rule will be applied on the cells that fulfill this condition. No text at all means : the rule is check on all cells.





Exercise

Check all rules related to HO – PWRCTRL DETECTIONExecute these rules for all cells in one BSC

Is there any rule which is red or orange ?Select/Propagate only this ruleCheck its properties

Expression :Execute this selected rule for all cells in the BSCSelect all cells which are red or orangePropagate the selection

How many cells do not follow the rule ? Answer :Select all parameters linked to this ruleExecute the selection of cells and parametersCompare their operationnal & reference values

Does it follow the reference ? Answer :

5 minutes

In order to add new rules, or change rules, kindly refer to User Guide §13.1





5 Parameters Tuning





5 Parameters Tuning

5.1 Benefits

OMC-R is not the most efficient tool to perform massive tuning operations on a network

Only light features to ease cell tuningIn case of BSC, TRX or Adjacency tuning, it can take days !OMC-R operators are not optimizers, they are prone to misinterpret your changes

NPO Tuning Browser translates your parameters tuning into a PRC

No risk of misunderstanding between different teamsUltra-fast & ultra-simple procedure, for cell, BSC, adjacencies, etc.

OMC-R operators are still in charge of activating the PRC or not





@ NPO Analysis Desktop@ NPO Analysis Desktop

@ OMC-R@ OMC-R

5 Parameters Tuning

5.2 Process

NPO tuning requires a strong methodology :1. Create a new tuning session

Modify parameters settingsExport the session to the OMC-R (s)

2. Open NPO Tuning BrowserTranslate the session into a set of ACIE files

3. Create a PRC in RNUSMPopulate the PRC with these ACIE filesActivate the PRC

To create a tuning session :Click on Tuning > Tuning SessionOr "Ctrl + H"

A new window appears in the "Report Browser"


The "report browser" becomes the "tuning browser"





5 Parameters Tuning

5.3 Interface

Tuning Session

Tuning Operation


A Tuning Session can be considered as a template. It contains tuning

operations and can be applied to create a tuning job.

A Tuning Job is a particular tuning session that has been applied at a given

date. It contains a copy of the tuning session used to create it. It is parsed

by MAAT Tuning to be split into different tuning tasks (one per impacted

OMC-R). Many tuning jobs can be created from a tuning session (one job per

application of the tuning session).

A Tuning Task contains all tuning operations that are impacting one particular

OMC-R.





5 Parameters Tuning

5.3 Interface [cont.]

Adjacency, Frequency or Advice tuningAdd/Remove AdjacencyCreate External CellsModify Frequencies/BSICWrite advices to OMC-R operator

Logical Parameters tuningModify parameters values for the current NE

Design Parameters tuningModify design values for the current NE

Functions


Note : MAFA frequencies tuning is not available in M2.





5 Parameters Tuning

5.3 Interface [cont.]

For each NE, select the forecast value






How to Do It

Create a Parameter Tuning Operation1. Select the appropriate NE's2. Select appropriate parameters in the Tuning tab3. Drag'n'Drop to the TS browserThe "parameter tuning" window appears1. Select the appropriate forecast value for each couple NE – parameter2. Repeat until all forecast values are tuned


First of all, open a new tuning session.

You can include several operations into a session : indeed, all the next operations can be included into one session.

"Parameters" can be logical or design !

Note : Only Parameters set as "tuneable" can be tuned with a TS. Some parameters might not be available in the tuning tab for this reason.

There are different pre-defined forecast values :

REFERENCE

PLANNED

HISTORICAL

REFERENCE OBJECT

If one requires to perform manual tuning, click on "user defined" and change the value accordingly.

"Apply to current object" : Apply the changes described in the lower pane to the object selected (black arrow in 1st column)

"Apply to all objects for current parameter" : Apply the changes described in the lower pane to all objects for the current parameter

"Apply to all objects for all parameters" : Apply the changes described in the lower pane to all objects for all parameters (useful if "reference object" is used ! Each parameter will be tuned to the value of the same parameter in the reference object)

"Cancel" : cancel the operation





5 Parameters Tuning

5.4 Reference cells

One cell can serve as a reference in a tuning session

The cell becomes blue, and can now be used as a reference cell.

To avoid mistakes, this cell can also be set as "not tuneable".


"not tuneable" : the cell cannot be tuned in a tunning session. Of course, it can still be tuned in the OMC-R.





5 Parameters Tuning

5.5 Post-its

For any reason, a NPO user can put a "post-it" on a cellEspecially useful to warn other users:

New parameters are set on this cellA QoS problem is being currently troubleshooted on this cell, etc.

A post-it symbol appears next to the cell






How to Do It

Create a Adjacency Tuning Operation1. Select the appropriate NE's2. Select "Adjacency Tuning" in the Tuning tab3. Drag'n'Drop to the TS browserThe "relation tuning" window appears1. Select relations to add or remove


To remove a relationship, do not use drag and drop, but rather the contextual menu. Select "Remove"

You can also choose the direction of the adjacency : from cell A to cell B, cell B to cell A, or both ways.





How to Do It

Create an External Cell1. Select the adjacent NE's2. Select "Adjacency Tuning" in the Tuning tab3. Drag'n'Drop to the TS browserThe "relation tuning" window appears1. Select "New ECELL 2G" and fill up the information


OMCEC : OMC-R External Cell

Fill up all fields : they provide enough information to the local OMC-R, so it can define an outgoing relationship.

Incoming HO from external cell to internal cell must be defined in the external OMC-R.





How to Do It

Create a Frequency Tuning operation1. Select the appropriate NE's2. Select "Frequency Tuning" in the Tuning tab3. Drag'n'Drop to the TS browserThe "relation tuning" window appears1. Double-click on Forecast to change the frequency of the TRX2. Select the BSIC


BSIC : The ’BSIC’ field displays the list of current forecast BSIC of the cell, or the

operational value if the BSIC has not been changed. This list proposes the

possible values that can be used.It is obtained using the following formula:

BSIC = BCC + 8 x NCC , where:

BCC varies from 0 to 7

NCC can take all the values indicated by the NCC_Permitted parameter.

ZONES / SPLITS : There will be one set of frequencies per zone (inner or outer or normal) and per split (main or secondary). Indeed, each zone/split has specific TRXs and specific hopping groups.

HOPPING :Non-hopping (NH) : refer to the slide. User can change frequency allocated to each TRX independantly

Baseband Hopping (BBH) : User can change the ARFCN's in the list, but the allocation of FHS group is transparent

all timeslots use all frequencies, except

* timeslot "0" of TRX 1, using BCCH frequency

* timeslots "0" of other TRX's, using all frequencies – BCCH frequency

Synthetized Hopping (RH/NH) : TRX 1 is not hopping, other TRX's are. Therefore there is a new choice in the first cell, instead of TRX : "TRX or FHS".

User can change the frequency of the TRX1, choosing "TRX"

User can change the ARFCN's in the FHS, choosing "FHS"

Allocation of FHS per TRX and per TS is performed automatically by the OMC-R.





Exercise 1/2

Create a new tuning sessionFor all cells with cong %(*) > 2%, enable FDR and fast traffic handover.Starting from exercise p.71, tune all cells that do not follow the new CRO reference.Set L_RXLEV_CPT_HO(Umbrella 900, Mini 900) = -74dBmL_RXLEV_CPT_HO(Umbrella 900, Mini 1800) = -72dBmHO_MARGIN(1800,900) = 7dBHO_MARGIN(900,1800) = 3dB

Find the cell with the highest amount of HO caused by interferences, and modify its frequencies.Find the cell with the highest time advance average, and add some neighbourhood relationshipsWrite an advice : "This is a test tuning session"

15 minutes


This exercise is only an example, the proposed values should not be applied on a network without prior study.

(*) TCH NA congestion rate at busy hour (TCNACGR_BH)





Exercise 2/2

Apply a tuning sessionExport the previous session to the OMC-RIf the OMC-R is available, perform all the steps until activation of the PRC

Notice how long it took to perform a massive tuning…






6 Distribution Reports






6.1 Overview

There is two types of distribution "view" :Vectors

Matrices

PathBalance Distribution

0

10

20

30

40

50

60

70

80

90

100

[-110,-50[ [-50,-30[ [-30,-20[ [-20,-10[ [-10,0[ [0,10[ [10,20[ [20,30[ [30,50[ [50,110]

Path Balance ( dB )

0

10

20

30

40

50

60

% PB distrib

Nb PB Samples

Vectors : X-axis = steps, Y-axis = value associated to the current step

Matrices : X-axis = steps, Y-axis = steps, each cell contains a value associated to the pair (X-step ; Y-step)







The content of each report depends on the measurementsBut the "steps" can be changed !

Between -10dB and +10dB, not enough details

Between 20dB and 50dB, too many details







By increasing the size of some steps & decreasing the sizes of other steps, we increase details where it is needed.

Now, more details between 0 to +12dB

In this example, the previous report couldn't show a problem. The new thresholds highlight a high number of calls with path balance between +9 and +12 !

In previous slide : most problems between 0 and 10

In current slide, we see that most problems are actually above 9 dB !!






6.2 Method

In NPO Administration Data ManagementConfiguration > Manage RMS (or GPRS) templates

Edit the steps' thresholds manually, or by following an interpolation method







6.2 Method [cont.]

Export the template to the OMC-RA file is export to the OMC-R, using the same format as a tuning session.Go to the OMC-R and follow this method :1. Export the RMS template using the NPO Tuning Browser2. Create a PRC in RNUSM3. Populate your PRC with your imported file4. Activate your PRCAfter activation, the new template is available in each BSCYou still need to apply this template on the cells1. Create a new PRC2. Populate it with these cells3. "Edit n cells" and choose the new template4. Activate the PRCNow the new template will be used by the cell for the next RMS campaign !






Exercise

Group per group, you will perform the update of the path balance template, accordingly to the previous slides.

The last group will import it in the OMC-R.

Activation is possible, if wanted.

15 minutes






7 Import a cartography project






7.1 Overview

Highly valuable information can be displayed in the cartography module

Offers new ways to investigate a problemInterferences (co-channels, adjacent channels)Missing adjacenciesHot-spot locationsTraffic & QoS distribution over time






7.2 Project Structure

A project is composed ofPlanned Data

Text files containing the list of cells and all related information for plotting them on a georeferenced map (coordinates, azimuth)= COF FILES

Background MapsMaps on which the planned data will be plotted= RASTER FILES or VECTOR FILES

Unlike RNO, there is no need of special RNO directories. The input files can be located anywhere.






7.3 COF files

3 mandatory filesCEL.COF : Description of the cell (CGI, coordinates, azimuth, omni/sector)FRQ.COF : Description of the TRXsADJ.COF : Description of the Adjacencies

Minimal amount of data is required to plot the cells

All other information are optional

CGI : cell global identifier

All the optional information will ONLY be used in NPO to be displayed as "planned" values (next to "operational", "reference" and "forecast").

It can be interesting to import the planned frequencies (BCCH, TCH) in order to compare it with the operational frequencies.






7.3 COF files [cont.]

CSV format : each data is separated by a semi-colonWindows > Configuration Panel > Regional SettingsChoose "Customize"Set the "List Separator" as ; (semi-colon)

When saving a file as "CSV" with Excel, the files will be in the correct format

Each file starts with 2 identical lines :

For instance :

Line 1 : GENERIC;B10;<project name>;<project version>;<date>;<creator>Line 2 : L

GENERIC;B10;ALCATEL_NETWORK;AUGUST_2007; 01/08/07;ALULL








CEL.COFLine 3 : column headersLine 4 … n : 1 line per cell

Most useful headers :1. READ_ONLY2. EXTERNAL3. RNP_CELL_ID4. CI5. LAC6. FREQUENCY_RANGE7. MNC8. MCC9. CELL_CLASS10. CELL_TYPE

11. TRX_NUMBER12. BCCH13. HOPPING_MODE14. X_SITE_LOC15. Y_SITE_LOC16. ANTENNA_ORIENTATION17. ANTENNA_TYPE (not mandatory)18. ANTENNA_HEIGHT (not mandatory)19. ANTENNA_TYPE_FLAG

Read_only : NO (not used)

External : NO if the planned cell exists in the list of CELL2G, YES if it is external to NPO

RNP_CELL_ID : key field, to link this cell with its TRXs in frq.cof and its adjacencies in adj.cof

CI : CELL ID, LAC : Location Area Code

FREQUENCY_RANGE : GSM850, GSM900, GSM1800,EGSM900, GSM1900,MULTIBAND, EMULTIBAND,GSM850-GSM1800, GSM850-GSM1900

MNC : mobile network code (3 digits) MCC : mobile color code (3 digits)

CELL_CLASS : URBAN, DENSE_URBAN, SUBURBAN, RURAL, INDOOR

CELL_TYPE : SINGLE, UMBRELLA, UMBRELLA_CONCENTRIC, MINI, MINI_CONCENTRIC, MICRO_CONCENTRIC, INDOOR, INDOOR_CONCENTRIC, CONCENTRIC, MICRO, EXTENDED_INNER, EXTENDED_OUTER

TRX_NUMBER : from 1 to 16 (tip : for fast file creation, put 1)

BCCH : ARFCN of the BCCH (tip : for fast file creation, put 1)

HOPPING_MODE : NH, BBH or SFH

X_SITE_LOC : geographical Longitude WGS 84 – decimal degrees in interval [-180.0, 180.0]

Y_SITE_LOC : geographical Latitude WGS 84 – decimal degrees in interval [-90.0, 90.0] (positive values in northern hemisphere)

ANTENNA_ORIENTATION : azimuth of the antenna in degrees (from 0.0 to 360.0)

ANTENNA_TYPE (not mandatory) : string

ANTENNA_HEIGHT (not mandatory) : integer

ANTENNA_TYPE_FLAG : 0 : panel antenna (the cell will be represented using the ANTENNA ORIENTATION), 1 : omnidirectionnal antenna (cell will be represented without orientation)







FRQ.COFLine 3 : column headersLine 4 … n : 1 line per TRX (depends on TRX_NUMBER defined in CEL.COF)

Mandatory headers :1. RNP_CELL_ID2. TRX_INDEX3. ARFCN4. ZONE_TYPE5. BCCH_FLAG6. PREFERENCE_MARK

In bold, needed fields

RNP_CELL_ID : key field, to link this trx with its cell in cel.cof

TRX_INDEX : index of the TRX in the cell (BCCH TRX = 1, TRX #2 = 2, …). At least one TRX per cell is needed

ARFCN : ARFCN of the TRX

ZONE_TYPE : NORMAL, OUTER, INNER (if TRX belongs to a concentric cell, it is assigned to a certain zone)

BCCH_FLAG : YES or NO (is this TRX carrying the BCCH timeslot ?)

PREFERENCE_MARK : TRX PREF MARK (GSM parameter) from 0 to 7

Tip : for fast file creation, define only one TRX / cell, with ARFCN = 1 and ZONE_TYPE = NORMAL







ADJ.COFLine 3 : column headersLine 4 … n : 1 line per adjacency (it can be empty)

Mandatory headers :1. RNP_CELL_ID2. NC_RNP_CELL_ID3. HO_MARGIN4. LINK_FACTOR5. HO_MARGIN_LEV6. HO_MARGIN_QUAL7. HO_MARGIN_DIST8. PRIORITY

9. NEIGHBOUR_RXLEV10. EN_TRAFFIC_HO11. L_RXLEV_CPT_HO12. OUTDOOR_UMB_LEV

This file can be empty (only the lines 1, 2 and 3 must be written)

In case adjacencies are imported, only the 2 RNP CELL ID fields are important. Other fields can use a dummy value.

RNP_CELL_ID : key field, serving cell of the adjacency, to link this serving cell with its cell definition in cel.cof

NC_RNP_CELL_ID : key field, target cell of the adjacency, to link this target cell with its cell definition in cel.cof

HO_MARGIN : GSM parameter, in dB

LINK_FACTOR : GSM parameter, in dB

HO_MARGIN_LEV: GSM parameter, in dB

HO_MARGIN_QUAL: GSM parameter, in dB

HO_MARGIN_DIST: GSM parameter, in dB

PRIORITY : GSM parameter, from 0 to 5

NEIGHBOUR_RXLEV: GSM parameter, in dBm

EN_TRAFFIC_HO: GSM parameter, 0 : DISABLE, 1 : ENABLE

L_RXLEV_CPT_HO: GSM parameter, in dBm

OUTDOOR_UMB_LEV: GSM parameter, in dBm







Create these files using EXCEL, and "Save As …" CSV format

Open the 3 files with NOTEPAD and remove the final semi-colons of line 1 and line 2

After this step, your cells are ready to be imported !






7.4 Format of background map

Two supported format :Vector files : Mapinfo Interchange Format (MIF + MID)

From A9155 RNP V6From MapInfo versions 300 or 450

Raster files : an image (PNG, BMP, JPG, TIF, TIFF) + its georeference ASCII file (RAST)

Created manuallyThe ASCII file contains a list of points that allows to georeference the mapOnly UTM wgs84 or a Long/Lat wgs84 coordinates are supported


Example of a MIF V450 vector file: RAST file for LONG/LAT WGS84 :VERSION 450 !tableCharset "WindowsLatin1" !version 300Delimiter "," !charset WindowsLatin1CoordSys Earth Projection 1,104 Bounds (94,95) (-1,0) Definition TableCOLUMNS 1 File "paris.bmp"LEGEND Char(50) Type "RASTER"DATA (0,0) (0,0) Label "",Region 1 (0.000002741134,0) (1,0) Label "",31 (0,0.000002741134) (0,1) Label ""94.556036 -0.154241 CoordSys Earth Projection 1, 10494.561412 -0.156046 Units "degree"94.558724 -0.156045Region 11594.561412 -0.15604694.561412 -0.155144RAST file for UTM WGS84 :!table!version 300!charset WindowsLatin1Definition TableFile "paris.bmp"Type "RASTER"(0,0) (0,0) Label "",(1,0) (73,108) Label "",(0,1) (70,18) Label ""CoordSys Earth Projection 8, 104, "m", -177, 0, 0.9996,500000, 0Units "m"






7.5 Import

Background file1. Open the Import/Export Management2. Select Import > Raster File or Vector

File3. Choose the layer name4. Choose layer type = Background5. Select the file6. Click "OK"7. Select the georeference file (for

Raster file only)







7.5 Import [cont.]

Planned Data1. Open the Import/Export

Management2. Select Import > Planned Data3. Select the appropriate format

(GENERIC)4. Select the 3 COF files for import5. Choose DELTA or NON DELTA

DELTA : the objects in the import files are imported, other existing objects are not changedNON DELTA : the objects not present in the import files are deleted

6. Click "OK"







7.6 Configuration files

On the client, connect to the server






7.6 Configuration files [cont.]

The important files :For changing cells layout (editable) :

/alcatel/muse/technologies/GSM/cartography/config/CartographyConfiguration.xml

For information (do not edit !) :/alcatel/muse/technologies/GSM/plannedData/specificloader/configfileNameObjectTypeMapping.cfg





8 Analyze a QoS problem






8.1 Presentation

Two main modules in NPO offer enhanced analysis support :CartographyDiagnosis

CartographyInterferenceQoS mapping and distribution (thematic layers)Adjacencies managementLayer management

DiagnosisAutomatic investigation of poor QoSBased on standard scenarios and operator-customized scenarions






8.2 Cartography pane

Activation

Select all the cells

1

2







8.2 Cartography pane [cont.]

Description

Mini Map

LayerManagement

Viewport

InformationBar

Toolbar








Layer Density : displayed information vs. zoom

2 3 4 5

6 7


Lock density : the layer density remains the same whichever the zoom chosen.

Layer density = 1 : objects are not displayed on the map

2 : one dot per site

3 : one line per sector

4 : colocalized cells or not (double lined or single lined)

5 : same as 4, but larger view

6 : each cell has its own icon

7 : cells are grouped per sector (one sector can contain one WCDMA cell, one GSM900 cell, one DCS1800 cell and one WIMAX cell !)







Cell Icons :


• “U-3” means that there are 3 UMTS cells grouped together

• “G-2” means that there are 2 GSM cells grouped together

• “W-1” means that there is 1 WiMAX cell in the collapsed cell.Collapsed cell







Other icons :

Layer density = 7

Sector 1

Sector 2

Micro cell in sector 1(to display the technology standard (G) cf User Preferences)

Concentric cell in sector 1

G








Toolbar

Information bar

Selection Zoom in/out

Center on selection

Viewport Mngt

Navigation

Ruler

Mini map display Adjacency wizard

Coordinates of the cursor Distance(ruler tool)

Scale of viewport







8.3 Cartography functions

In the viewport, the contextual menu offers major functions :Right-click on the background map

The contextual menu recaps toolbar functions

Left-click (= select) and Righ-click on a cellNew functions available !

Open cell properties

Show co-sector cells

Propagate selection towards theNetwork elements pane

Remove cell from viewport

Basic Functions

Show adjacencies







8.3 Cartography functions [cont.]

Highlight :All Parents / Children Objects

BTS

BSC

Cell 1

TRX 1 TRX 2 TRX 3

TrafZ innerTrafZ outer

Cell 2

TRX 1 TRX 2 TRX 3

TrafZ innerTrafZ outer

TRX 4

child

rens

parents


TrafZ = traffic zone (subset of TRX that belong to same BTS, same frequency band and same zone)







HighlightAll incoming / All Outgoing /All Adjacencies

Outgoing adjacency towards 2co-sector cells

Outgoing adjacency towards theother co-sector cell








HighlightInterfering / Interfered

InterferenceMatrix

NPO

Import/Export MngtCARTOGRAPHY

The interference matrix is produced by a RNP tool (A9155 for example)or manually.

The format of the file is the following :

COFF;1.01;<project name>;<project version>;<date>;<creator>>RNP_CELL_ID_INTERFERER;CI_INTERFERER;ZONE_TYPE_INTERFERER;RNP_CELL_ID_TARGET;CI_TARGET;

ZONE_TYPE_TARGET;CO_CHANNEL;ADJACENT_CHANNEL;CELL_A;134;NORMAL;CELL_B;137;NORMAL;45;9;CELL_A;134;NORMAL;CELL_C;139;INNER;20;0;CELL_B;137;NORMAL;CELL_C;139; INNER;34;0;CELL_B;137;NORMAL;CELL_C;139; OUTER;9;0;

The only use of the interference matrix in NPOImport in NPO of the Interference Matrix is performed during the import of planned data :

Locate the file "INM.rno" in the folder RNO_DATA/

Definition of the fields in the interference matrix :

RNP_CELL_ID_INTERFERER string 20 char Identifier of the cell. Could be a number or a char string.

CI_INTERFERER integer 1 .. 65535 Cell Identifier of the interferer cell.

ZONE_TYPE_INTERFERER string NORMAL, INNER, OUTER Specifies the zone of the interferer cell: INNER or OUTER for a concentric cell; NORMAL for the other cell types.

RNP_CELL_ID_TARGET string 20 chars Identifier of the cell. Could be a number or a char string.

CI_TARGET integer 1 .. 65535 Cell Identifier of the target cell.

ZONE_TYPE_TARGET string NORMAL, INNER, OUTER Specifies the zone of the target cell: INNER or OUTER for a concentric cell; NORMAL for the other cell types.

CO_CHANNEL integer percentage 1 .. 100 probability that the interferer cell interferes the target cell if they share a frequency. (Delta ARFN = 0)

ADJACENT_CHANNEL float percentage 0 .. 100 probability that the interferer cell interferes the target cell if they have two adjacent frequencies. (Delta ARFN = 1)







HighlightFrequency Reuse Checking

Selected cell

One of the cell within the radiusthat is using the same frequency asthe selected cell

Checking radius (in meters)

The current exemple shows that many surrounding cells are using the same frequencies. It might be a case of SFH 1x1.







HighlightCCA (Cell Contour Area, also known as "Best Server Area")

NPO computes Voronoi areasbetween cells of same type

CCA can be computed by NPO (using Voronoi computation : mathematical simulation)

Or they can be imported from RNP (prediction of the best server areas, based on coverage predictions, in MIF/MID format)

These MIF/MID must contain the RNP CELL ID, as used in the COF files

To import a CCA generated by RNP:

Locate the MIF/MID files in <project name>/<project version>/RP_MAPS/






8.4 Cartography & Tuning Session

Adjacency Wizard

• Adjacencies with no usage or low usage (based on the type 180) will be removed

• If a Tuning Session is opened, possibility to copy the wizard's result as a tuning operation

Added relationRemoved relationUntouched relation


The Adjacency Wizard can work with or without a tuning session opened.

To open the Adjacency Wizard, you must select one cell.

Low usage is defined in a configuration file located in NPO server :

\alcatel\muse\technologies\GSM\cartography\config\CartographyConfiguration.xmllowTrafficThreshold="0.1"

It means all adjacencies relationships that account for less than 10% of the overall handovers are considered "low".

This threshold might be considered a little high, especially in urban areas with a lot of overlap and traffic sharing mechanisms.






8.4 Cartography & Tuning Session [cont.]

Field Trial ZoneSelect only certain NEs, based on their parametersPropagate the selected objects

1

2

3


1 : select the cartography layer mode :

S : selectable

V : visible

2 : select the selection mode

3 : when selecting cells, only the selectable cells are selected. Selecting only certain cells is the first step, next step is to propagate these cells, in order to perform other functions (tuning, reports, etc.)

This mode of selection can work with any type of network elements (adjacencies, cells, BSC …) as long as they are displayed on the map.

After the propagation is done, one can create a new cell zone and/or tune the selected cells.






8.5 Thematic Layers

Objects in the map will be displayed differently, depending on customized criteria. Example :

Thematic layer based on parameter "FREQUENCY BAND"

Thematic Layer Editor


It is possible to create a thematic layer for any kind of object that can be mapped in the cartography module (mostly BSC, BTS)

Adjacency thematic layers are not supported in this version.






8.5 Thematic Layers [cont.]

Multiple criteria possible

Drag & drop a function here

Criteria can be applied on another object

Intervals distribution method

Boundaries of intervals (static or dynamic)

C

If static distribution : define the min/max of each interval here

Double click in the cell to choose graphical properties for this interval

Will define the background color for each interval, from green to red


Criterion Graphical Properties : graphical property which is common for all cells. It will not be changed depending in which interval the cell is.

When using two criteria, the second criteria cannot reuse the graphical properties used in the first criteria.

Auto-Background works only if the graphical properties of EACH interval have been pre-defined.






8.6 Export in GOOGLE EARTH™

Export a layer in KMZ formatOpen in Google Earth™

1

2

3

4

In google earth, it is possible to visualize buildings and streets at very high resolution.

It is useful to analyze surrounding terrains and obstacles, check roads which are passing by a site, etc.





Exercise

Using the cartography,Select all cells with

FREQ RANGE = GSM900AND CELL CLASS = URBANAND CELL TYPE = MICRO

And tune their parameter "A_PBGT_HO" to 12

Select one cell and use the Adjacency wizard to check relations within 400m, and remove relations with "No Usage" (import in the Tuning Session)

Create a thematic layer for CELL2G, based onRTCH_LOAD, 4 intervals : 0-50%, 50-75%, 75-100%, > 100% (green to red)Nb of TRXs, 3 intervals : 1-2, 3-4, >4 (scale : 0.4, 0.8, 1.2)

Apply this thematic layer for different hours during the day

30 minutes







8.6 Diagnosis

A diagnosis is a suite of tests, based on parameters and indicators :

TCH congestionabove threshold ?

No diagnosis

RTCH always busy ?

TRX frozen ?

Loss of TCH ressources ?

Too much TCH traffic ? FDR acticated ?

Queue is full ?

Queue expires ?

Bad queue settings ? Wrong T11 ?

Wrong TQHO ?

WrongBTS_Q_LENGTH ?

RTCH 100% busy

TRX w/ no traffic

Cant't check

NO

YES

YES

YES

YES

YES

YES

?

YES

YES

YES

YES

YES

YES

YES

The link between nodes is based on causality : the 1st node can be a consequence of those causes, etc.

In the end, the diagnosis will output all possible "root" causes.

For each node, there are :

a) 1 or several tests such as :

IF ("qos indicator 1" > threshold 1) AND ("qos indicator 2" > threshold 2)

THEN Problem Found

ELSE Problem Not Found

b) 3 possible outputs : problem is found, problem is not found or test is impossible (hardware check, OMC-R alarms check, or qos data unavailable)

When creating a diagnosis, the two longest steps are :

- Designing the tree of test nodes

- Finding the relevant indicators & parameters to use in each test






8.6 Diagnosis [cont.]

ActivationSynthetic Mode

Drag and drop NE + Diagnosis in the Spreadsheet browserOr

From the menu bar "Diagnosis > Execute Diagnosis"Detailed Mode

Drag and drop NE + Diagnosis in the Report browserOR

Right-Click on the value of a " " indicator that exceeds the red threshold, choose "Execute Diagnosis"

Synthetic Result

Detailed Result








Different diagnosisV3_CDR : version 3 of "call drop rate" diagnosisV4_CDR : version 4 of "call drop rate" diagnosisV4_CDR_180 : already included in V4_CDRV4_CDR_TRX : includes V4_CDR + 3 additional tests per TRX

Check the properties of diagnosis V2_SDR :

V4 CDR vs V3 CDR : V4 includes one additional node : test if call duration is different among the TRXs of the cell.

V4 CDR TRX : same as V4 CDR + TRX remote transcoder problem + TRX handover problem + TRX radio problem







Detailed Output

Each node is detailed, with a description of the test and the value of the QoS Indicator





Exercise

Create a favorite with all QoS Indicators located in the family "QoS > Main"Execute this tabular view for yesterday"Highlight" the viewExecute a diagnosis on one of the "red" valueVerify one of the results of the diagnosis

10 minutes






9 A day at work with NPO






9.1 Schedule

MonitoringCheck log files of indicators and parameters importGenerate a "WORST 20" warning report on KPI'sGenerate a daily report of the network (or weekly, on Monday)Generate a detailed spreadsheet report for all cellsCheck reliability of the problemsDispatch worst cells to relevant teamsUpdate monitoring database

OptimizationTackle worst cells one by oneCheck RMS & detailed indicatorsCheck interference and frequencies reuseCheck adjacencies definitionFind the cause of the problemPropose corrective actionUpdate troubleshooting database

Monitoring and Troubleshooting database are created by operator, to keep track of all worst cells and previous actions performed on the network.






9.2 Know your colleagues

Each type of problem should be solved by one specific teamFind the few KPIs that define a team :

Call drop due to remote transcoder %

Deployment/planning teamCall drop due to internal BSS %

TCH Congestion % & High traffic

TCH Congestion % & Low traffic

HO Quality % or HO Intf % & CDR radio on all TRXs

RMS DL RxLev avg < -85dBm & poor CDR & poor CSSR & path balance = [-6;+8]

RMS DL RxLev avg < -85dBm & poor CDR & poor CSSR & path balance ≠[-6;+8]

Frequency planning team

OMC-R team

Maintenance team

Optimization team

Too many HO from lower to upper layer






9.3 Interaction with other teams

From A9155 Radio Network Planning tool :Extract maps in MIF formatExtract CCA in MIF formatUse satellite orthoimageImport

Cell "geo" planned data (coordinates, azimuth)Planned radio data (new frequency planning, new adjacencies)Interference Matrix (predicted interference probability between 2 cells)

Maps, planning,interference matrix

RNP NPO

Beside previous slide, supplementary information should flow between optimization team and other teams.






9.3 Interaction with other teams [cont.]

To A9155 Radio Network Planning tool :Update cells database with

Operational frequenciesOperational adjacenciesOperational capacitiesOperational cell layer / type

Import additional dataTraffic in Erl, HO interf%, HO Quality%, HO/call, etc.Experience Matrix (overlap measured with RMS)

Live config, QoS,RMS, experience

matrix

RNP NPO






9.3 Interaction with other teams [cont.]

To Dimensioning teams :Provide traffic informationProvide operational configuration

From Design teams :Collect the parameters templates, for each type/class of cellOr, rather, their NPO reference dictionnary

To Design teams :Provide operational parameters for all cellsProvide QoS reports related to new settingsCells with optimized/different settings than their references





Exercise

Dimensioning team needs to verify the current load of BSCs. Generate a report, including all BSCs, with :

SDCCH Erlang at BHTCH Erlang FR at BHTCH Erlang HR at BHNumber of TRX per BSCNumber of cell per BSCMax congestion on Ater PS interface, for each GPU

15 minutes






9.4 Scheduled Reports

To gain time, Warning reports & Diagnosis can be automatically generated by NPO :

Execution Context window







9.4 Scheduled Reports [cont.]

Output format : in the browser, or as an output file

If checked : all the elements in the current working zone will be used in the report.If unchecked : only the elements selected will be used.

Date at which the report will be available

Job title can be edited








Date at which the reports will stop being created

The report can be generated periodically








To view a scheduled report, 2 possibilities :1. From the Analysis Desktop : Report > Display pending executed reports2. From the NPO Administration :

Data Management > Administration > Manage Jobs Results

In both cases, same principle : the list of executed reports is displayed and each report can be viewed on demand

If the report is in NPO format, it will be displayed in the report browserElse, the report will be saved and opened with an exeternal application (Excel®, Acrobat Reader®, etc.)








With NPO Analysis Desktop








With NPO Administration :








To delete an existing job, go to NPO Administration > Data Management






10 NPO Customization






10.1 Classification

Classification of objects and functions can be modified

Topology Classification







10.1 Classification [cont.]

Choose Topology > Topology Classification (Ctrl + T)Design your new classification : Cells classified per number of TRX

1

3

2

4


1 : create a new classification

2 : choose the name and the mode (the classification will be applied on which object?)

3 : select on the right-pane the functions that will be used for the classification (Topology (per BSC) ? Parameters (EN_GPRS) ? Design (per Cell Type) ?)

4 : Apply the changes and "close"







Choose Data > Function Classification (Ctrl + U)Design your new classification : Logical parameters per Unit

1

3

2

4


Note : Function Classification will rarely be useful for radio optimizers

1 : create a new classification

2 : choose the name and the mode (the classification will be applied on which object?)

3 : select on the right-pane the properties that will be used for the classification (Release, Unit, Consolidation, …)

4 : Apply the changes and "close"







For better display, change the order of the tabs :

Display/Remove the classification from the tabs






Exercise

Create a topology classification based on the free fields "PROVINCE" and "CITY" (CITY is under PROVINCE)

5 minutes







10.2 User Preferences

In the menu bar, choose "Edit > Preferences"

When selecting a "favorite", it doesn't clear the previous selection

On next start, same panel layout as on previous exit is displayed

Changes the orientation of the text in the network mode tabs (vertical = RNO alike)

Change font in the whole application


YES : soft deleted objects remain visible in Analysis Desktop, with icon

These settings apply only to the user currently logged on Analysis Desktop. They do not affect settings made by any other user when that user is logged. These settings can be changed by regular users, as well as administrator user.

Once these settings are saved, each time the operator re-opens Analysis Desktop, the chosen preferences are used.

Note : Objects that are marked as “soft” deleted for more than three years will be removed from the database (“hard” deleted).






10.2 User Preferences [cont.]

Allow interpolation while executing a view/report

When editing a view/report, open a new window

Define the mechanism to apply hilights and legend filtering : per row or per column

Default execution type when drag&drop indicators

When user copies a report, will he also copy the associated views, or will he keep the link to these original views ? (views might not belong to the user !)

Export of data from NPO to another format (xls, html, etc.)








Automatic : no warning message will be displayed when a new filter is activated, while previous filter(s) were already configured before but deactivated. All filters will be cumulated (deactivated + activated)

"Highlight" function activated by default when executing a tabular view

Keep these keys pressed to update an executed view with new elements or functions.

An empty indicator value in a view is replaced by…?

Data that will be available in a tabular view


Quick Diag results in "verbose" or "icon" format

In View editor, default graph type chosen.







Default colour for adjacencies

Zoom "step size"

Default colour for selection

Consecutive highlights will append to previous highlights

Display the symbol of each cell's standard on the cartography

Default colour for highlighting

Choose operationnal or planned geo-data (coordinates of cells from OMC-R or RNP files ?)

Factor applied on the radius if it is based on the U_TIMEADVANCE (wizard adjacency)







10.3 Customer Topology Objects

NPO allows to create new network equipments or new relations between equipments

Mostly defined by their parents/children relationsThis customized objects will be treated like the other network objects :

Available in Analysis DesktopConsolidations will be performed at their level

BSC 1

MSC A

child

ren

BSC 2 BSC 3

GERAN

BSC 4

MSC B

New Object

New Relation

New Relation

pare

nt


Usually, each new object should be associated with 2 new relations : object – parent & object – children






10.3 Customer Topology Objects [cont.]

There are two steps to define a new objects1. Create the object type (e.g. type "MSC")2. Define a new object (e.g. "MSC 1", "MSC 2")

Both steps use a similar method :1. Create or modify the related text file2. Import the text file with NPO Import/Export Management

Before importing an object, verify the object type is already defined in NPO.If the type doesn't exist, create it first.








How to create a new object type :1. Copy & rename the sample file

"/alcatel/muse/MUSE_QOS/topology/files/CustomerTypes.txt"2. Edit the copied file with excel :

BSCMSCGSMMSC_ID/BSC_IDMSC_BSC12

stringY_CoordstringX_CoordGERANGSMMSC_IDMSC01

IHGFEDCBA

Cf. Description in the comments of this slide


Col A : relation flag : when equals to 1, it defines a relationship. When equals to 0, it defines a network object type.

Col B : name of the object (e.g. MSC) or relationship (e.g. MSC_BSC)

Col C : External ID label e.g. MSC_ID (object) or MSC_ID/BSC_ID (relationship)

Col D : Technology standard (GSM)

Next columns, if it is a line defining a network object :Col E : Father Type (e.g. GERAN)

Col F : attribute 1 name (e.g. Longitude, name, address, etc.) (optionnal)

Col G : attribute 1 type (e.g. string, integer, …) (optionnal)

Col H : attribute 2 name (e.g. Longitude, name, address, etc.) (optionnal)

Col I : attribute 2 type (e.g. string, integer, …) (optionnal)

Etc.

Next columns, if it is a line defining a relationship :Col E : Source Type (e.g. MSC)

Col F : Target Type (e.g. BSC)







How to create a new topology object (i.e. "MSC 1" and "MSC 2")1. Copy & rename the sample file

"/alcatel/muse/MUSE_QOS/topology/files/CustomerData.txt"2. Edit the copied file with excel :

Cf. Description in the comments of this slide

VNR_BSC2BSC2MSCMSC 2 - BSC VNR21/VNR_BSC2MSC_BSC4

VNR_BSC1BSC1MSCMSC 1 - BSC VNR11/VNR_BSC1MSC_BSC3

N 05 01 46Y_coordW 03 57 26X_coord1GERANMSC 22MSC2

N 05 18 08Y_coordW 03 59 31X_coord1GERANMSC 11MSC1

IHGFEDCBA


Col A : Object Type or Relation Type (<source type>_<target type>)

Col B : External ID

Col C : Friendly Name

Next columns, if it is a line defining a network object :

Col D : Father Type (e.g. GERAN)

Col E : Father External ID

Col F : attribute 1 name (e.g. Longitude, name, address, etc.) (optionnal)

Col G : attribute 1 value (optionnal)

Col H : attribute 2 name (e.g. Longitude, name, address, etc.) (optionnal)

Col I : attribute 2 value (optionnal)

Etc.

Next columns, if it is a line defining a relationship :Col D : Source Type (e.g. MSC)

Col E : Source External ID

Col F : Target Type (e.g. BSC)

Col G : Target External ID

Col H : Link qualifier (optionnal)







How to import a new Customer Topology Objects Type file ?Save the file in CSV format (semicolon or comma separated) under"/alcatel/muse/MUSE_QOS/topology/files/"Open Import/Export Management > Import > Customer Objects Type








How to load the Customer Topology Objects file ?Save the file in CSV format (semicolon or comma separated) under"/alcatel/muse/MUSE_QOS/topology/files/"Open Import/Export Management > Import > Customer Topology Objects






Exercise

It is highly intereting to create Abis links between BSC-BTS and BTS-BTS :

Possibility to detect problems on chained BTS due to faulty AbisPossibility to keep track of network architecture in NPO

1. Create a new relationship type : ABIS2. Create a new link from one BSC to one BTS, and

from this BTS to another BTS (if possible, use a real example).

3. Load the changes in NPO

10 minutes






11 Annex





11 Annex

11.1 Indicator Editor

Pad Value : used only if the Interpolation is set to "Padding"

Consolidation Method : For instance, collected data at GP=1/4h but displayed data at GP=1h. In this case:

1. the First interpolation is performed, to "repair" within a 15-mins block

2. the consolidation is performed in order to build "1-hour" blocks (= 4 x 15 mins)

3. the Second interpolation is performed, in order to display missing 1-hour blocks.

Spatial Aggregation : Method used to aggregate from CELL to BSC, for instance.

Spatial Aggregation Path : read from left to right, the successive parents of the basic network element.

Group : select a compatible group (with same PM TYPE and same collected element) or create a new group

Support Dynamic Interpolation : If set to FALSE, it cancels all interpolation chosen before !! no interpolation





11 Annex

11.1 Indicator Editor [cont.]

Temporal Aggregations :

The "Reference Ext" is just a string of characters, to identify this temporal aggregated indicator.

The "Reference Ext" should be included in the "Name"

Temporal Aggregation Method :

Sum

Count

Average

Minimum

Maximum

BusyHour

BHPos (returns the hour of the busy hour, i.e. "1:00pm")

Dav3 (average of the 3 previous busy hours)

Dav5 (average of the 5 previous busy hours)





11 Annex

11.1 Indicator Editor [cont.]

Multiple spatial levels (Distributed indicators) :

Only 2 functions are needed :

ObjSup(Ind) - takes the value of the indicator ’Ind’ at the spatial level ’n+1’

ObjSupSel(Ind, ObjType) - takes the value of the indicator ’Ind’ at thespatial level defined by the ’ObjectType’.





End of ModuleOperation





Module 3Administration


Section 1NPO GSM




NPO GSM · Administration 1 · 3 · 2

Blank Page




Document History





Objectives





Objectives [cont.]






Table of Contents


1 Data Loading 71.1 Radio Parameters 81.2 QoS Data 111.3 Consolidations 121.4 System Scheduling 141.5 Time Zone 151.6 Import Checking 16

2 Data Management 192.1 Overview 202.2 Configuration 212.3 Administration 22

3 Import / Export Management 233.1 Overview 24

4 Recovery Tasks 274.1 Presentation 284.1 Scenario A 294.2 Scenario B 304.2 Scenario C 324.3 Scenario D 35





1 Data Loading





1 Data Loading

1.1 Radio Parameters

Radio Parameters files imported from OMC-RLast import saved in /alcatel/DATA_SOURCE/OMC1/ACIE

NPO SERVER

OMC-R CRONTAB :Directory : /alcatel/omc3/omc3rno/script/ Script : run_periodicExport –all

LOADER :Directory : /alcatel/muse/MUSE_PARAM/loader/bin/Script : run_gl.shUsing the plug-in :Directory : /alcatel/muse/technologies/GSM/Parameter/specificloader/lib/File : MuseGSMRTPPlugIn.jar

PURGE :Directory : /alcatel/muse/MUSE_PARAM/consolidation/bin/Script : run_consolidation.shBased on :Directory : /alcatel/muse/MUSE_ADMIN/config/File : paramStorageDuration.cfg

DICTIONARY/alcatel/muse/technologies/GSM/Parameter/specificloader/dictionary/MSNPO_GSM_RP_M2S2.xml

/alcatel/var/share/AFTR/ACIE/ACIE_NlExport_Dir1

/alcatel/var/share/AFTR/ACIE/ACIE_NlExport_Dir1

TRACE\alcatel\muse\data\trace/RTP_Loader_0.traces


To view XML files, use NOTEPAD++ (freeware)

Scheduler : the time of NPO import is defined in NPO Administration / Data Management / Configuration > System Scheduling

FTP parameters : are defined in NPO Administration / Data Management / Configuration > Data Sources

For each OMC-R, the field "PARAM_URL" contains information about IP Adress, login and password for the FTP.

Refer to the MS-OMC Portal/A9159-NPO Platform Administration Guide

To change the storage duration :

NPO Administration > Data Management > Configuration > Data SourceChoose an OMC-R, click "UPDATE", then "NEXT", then "ADVANCED".

Modify the value in the field "MAX_PREVIOUS DAYS"

Click "Save"





1 Data Loading

1.1 Radio Parameters [cont.]

Before performing a Tuning Session, check the parameters values in NPO are up to dateTrace files are located in :\alcatel\muse\data\trace

Check successful parameter import in the file :RTP_Loader_0.traces

15/0

8/20

0714

/08/

2007


Example of a successful import :

Aug 14, 2007 17:10:35.275 -(6)-[main] DEBUG: ParamGenericLoader::main (ParamGenericLoader::364) Loading of Parameter data is successful.





1 Data Loading

1.1 Radio Parameters [cont.]

After a tuning session or an update of planning data, it is necessary to wait for the next scheduled parameter import.

It is possible to force the import of ACIE files :

On the OMC-R, enter this command :/alcatel/omc3/omc3rno/script/run_periodicExport –all

Then, on the NPO server, enter this command :/alcatel/muse/MUSE_PARAM/loader/bin/run_gl.sh


ACIE : Alcatel-Lucent Configuration Import/Export (set of files containing all radio configuration of the network equipments)

The "run_gl" script will import the contents of directory "alcatel/var/share/AFTR/ACIE/ACIE_Nlexport_Dir1" from OMC-R.

To export a radio configuration:1. Login as administrator in OMC-R, open a console and type : /alcatel/omc3/omc3rno/script/run_periodicExport

–all

OR

1. In the RNUSM: PRC or SC main window, select Configuration -> Export.The RNUSM: Export Operation window opens.

2. Select the required directory.To perform an export, the directory status must be Idle.The default value of [CGI mode used for Cell Identification] is 'No'. If you need to activate it, set it to 'Yes'. The result is that the CSV files resulting from the export will contain the CellGlobalIdentity instead of the reference used to identify the cell.

If the Directory Status is... Click on...Idle [Export].

Ready [Free], and then [Export].

Export progress is displayed in the Follow-up window.3. Click on [Close].





1 Data Loading

1.2 QoS Data

QoS data files imported from OMC-RLast imports saved in /alcatel/DATA_SOURCE/OMC1/APME

NPO SERVER

OMC-R Regularly (1hr or less)PM files are retrieved from BSS & MFS

LOADER :/alcatel/muse/MUSE_QOS/loader/genericloader/scripts/run_gl.shUsing the plug-in :/alcatel/muse/MUSE_QOS/loader/genericloader/libgenericloader.jar

CONSOLIDATION & PURGE :/alcatel/muse/MUSE_QOS/consolidation/bin/consolidation.shBased on :/alcatel/muse/MUSE_COMMON/config/StorageDuration.csv

DICTIONARY\alcatel\muse\technologies\GSM\QoS\dictionary/QID.xml, B10_QCD.xml, QRD.xml

/alcatel/var/share/AFTR/APME/alcatel/var/share/AFTR/APME

TRACEData Management > Administration > Import Follow-up


Scheduler : the time of NPO import is defined in NPO Administration / Data Management / Configuration > System Scheduling

Dictionaries :QID : indicatorsQCD : countersQRD : views & reports

To change storage duration :To configure the indicator storage duration perform from the server as root the following steps:

1. Copy and rename the Storage duration file into a saved location.Example:

cp /alcatel/muse/MUSE_COMMON/config/StorageDuration.csv /alcatel/muse/MUSE_ADMIN/bin/NewStorageDuration.csv

2. Modify as apropiate the duration values in the new configuration storage duration file.Do not modify the first two lines of the file NewStorageDuration.csv file.

3. Run the /alcatel/muse/MUSE_ADMIN/bin/ConfigIndDuration.sh script, giving as argument the full pathname of the file that contains the duration values.

Example:/alcatel/muse/MUSE_ADMIN/bin/ConfigIndDuration.sh /alcatel/muse/MUSE_ADMIN/bin/NewStorageDuration.csv

In case the new values are smaller than the Evolium recommendations (recommended min values: Raw/Daily 5days, Weekly 1 week, Monthly 1 month), a warning is displayed. The administrator is not allowed to change the storage duration to a less than zero value. An error is displayed in case of setting a negative value. Only a positive or null value is allowed.

The storage duration values are then updated in the database and the status of the operation is displayed to the administrator.





1 Data Loading

1.3 Consolidations

The indicators are consolidated automatically, temporaly and spatialy

Temporal Consolidation can be customized :First day of the week, for WEEKLY consolidations

Login as root user :

- Open /alcatel/muse/MUSE_QOS/config/Consolidation.properties- Change the WEEKLY_CONSOLIDATION_ON attribute

Example: WEEKLY_CONSOLIDATION_ON=MONDAY- Save


change the WEEKLY_CONSOLIDATION_ON attribute to the day when you want the weekly consolidation to begin (usually the date when the weekly consolidation used to start on NPA).





1 Data Loading

1.3 Consolidations [cont.]

Working hours definition can be modified as well :

Login as root user :

- Open / alcatel/muse/MUSE_QOS/config/Consolidation.properties- Change the RELEVANT_HOUR_BEGINS_ON attribute- Change the RELEVANT_HOUR_ENDS_ON attribute

Example: working hours between 9 AM and 7 PM, the file should contain the following values RELEVANT_HOUR_BEGINS_ON=9RELEVANT_HOUR_ENDS_ON=19

- Save






1 Data Loading

1.4 System Scheduling

Check the timing of consolidation, job computation, and import parameter activities :


It is also possible to disable / enable a job, but this is NOT recommended ! All jobs should be available.





1 Data Loading

1.5 Time Zone

It is mandatory to select the same time zone between NPO Server and the different Data Sources






QoS Import

Root Loading Object = BSC in GSM (entity that generates the PM files)Datasource = OMCR in GSMFile type : 1 file per counter type (PM110, PM180, PM31,…)

1 Data Loading

1.6 Import CheckingB10MR2B10MR2

The value shown is the number of files collected by NPO. In this example :

1 file each 15 minutes = 48 files collected in the day

Less than this (orange or red), and NPO detects there are missing files.

(Note for future release : the value displayed might be in format xx/yy, it means xx files collected and yy files failed)





1 Data Loading

1.6 Import Checking [cont.]

Parameters Import

CSV : set of ACIE files (12)RTP :

B10MR2B10MR2





1 Data Loading

1.6 Import Checking [cont.]

QoS Consolidation

B10MR2B10MR2

There are recovered data not yet consolidated

There is an on-going consolidation

There is no on-going consolidation and no recovered data

Invalid response from the server

Re-consolidation of QoS with the recovered data

Recovered Data : data that was recovered in the OMCR but after the consolidation was done.





2 Data Management





2 Data Management

2.1 Overview

Most functions have already been explained. This chapter will recap all of them.






2 Data Management

2.2 Configuration

Enable/Disable an import job

Edit a RMS or GPRS template

Add / Edit a data source (storage duration, login/password/IP, paths, etc.)


Modify inputs to detect unavailability

Modify working hours definition





2 Data Management

2.3 Administration

Consolidate data (for any date) (*)

For objects not loaded for the last 5 days, NPO administrator can decide to remove them from display. These objects are not deleted, they can be re-activated.

Consolidate recovered data only (*)

Display licenses for NPO

Status of previous Data imports (QoS, params, planning, LASER)

Manage automatic reports execution (batch)

List of dictionaries and their versions

(*) Cf. next chapter for more details






3 Import / Export Management






3.1 Overview

Import/Export Management allows the user to import, export and delete various types of data :

DictionariesRMS / GPRS templatesRaster / Vector files (RNP)Planned data (RNP)Customer Topology ObjectsFree Fields

Export : for backup or import in another NPO server

Import : update current NPO with dictionary from another NPO, or with a new dictionary from Alcatel-Lucent (recommended for administrator or root user only)







3.1 Overview [cont.] DELTA RNO-NPODELTA RNO-NPO

Refer to NPO Administation Guide for specific explanation on each function.





Exercise

Export the Report dictionaryFind one of the reports you created earlier

Imports have been done earlier Free fieldsPlanned data, etc.

Do you remember the process ?

10 minutes


It is redundant to perform a import again : the most important imports have been done in the previous chapters already.





4 Recovery Tasks





4 Recovery Tasks

4.1 Presentation

QoS Data were not retrieved by NPO :Due to OMC-NPO link unavailabilityDue to BSC/MFS-OMC link unavailbility, etc.

Several scenarios have to be consideredScenario A : short outage (< 24 hours)Scenario B : short outage at bad time (< 24 hours)Scenario C : long outage (< 5 days)Scenario D : very long outage (> 5 days)

Only scenario D requires a back-up recovery procedure






4 Recovery Tasks

4.1 Scenario A

Outage and resume before the consolidation time

00:00

Consolidationscheduled time

= 1:00am

No PM Files receivedtime

09:00 12:00 18:0015:00 21:00 03:00 06:00 09:00 12:00

00:00

Files automatically retrieved

time09:00 12:00 18:0015:00 21:00 03:00 06:00 09:00 12:00

1

2

The PM files are kept in OMC-R for five days, whether they are imported by NPO or not.As soon as the link is resumed, NPO imports all data not yet imported automatically.

NO ACTION FROM THE USER IS NEEDED






4 Recovery Tasks

4.2 Scenario B

Outage before the consolidation time, and resume after.

00:00


= 1:00am


09:00 12:00 18:0015:00 21:00 03:00 06:00 09:00 12:00

00:00


time09:00 12:00 18:0015:00 21:00 03:00 06:00 09:00 12:00

1

2

Still, no manual import is needed.But it is necessary to re-consolidate the daily data : the previous consolidation used only data up to 11:00am (before the outage)






4 Recovery Tasks

4.2 Scenario B [cont.]

Consolidation of "automatically" recovered data

Automatically, NPO lists the dates with recovered data or not.Click on "recover" to perform a consolidation on all dates.


"Recovered data" : data that have been imported by NPO after a PM files outage, if the outage was fixed after the consolidation time.

If the outage was fixed before the consolidation, refer to scenario A.





4 Recovery Tasks

4.2 Scenario C

Outage for many days, but less than 5 days (120 hours).

00:00


= 1:00am


18:00 21:00 03:00 06:00 09:00 12:00

00:00


time18:00 21:00 03:00 06:00 09:00 12:00

1

2

Between "Day 1" 10:00am and "Day 6" 9:00am, there is 119 hours.All PM files are stored in OMC-R, and the retrieval process starts at 9:00am on day 6.Therefore, only one thing to do : Consolidate Restored Data (cf. previous slide)

Scenario B and C = same solution

10:00

Day 6Day 1






4 Recovery Tasks

4.2 Scenario C [cont.]

During Day 6, launch the consolidation for Day 1, 2, 3, 4, 5.At Day 7, 1:00am, the consolidation of Day 6 is performed automatically.

Possible problem : the time to retrieve all the data takes too much time, and all data of Day 6 are not imported before the consolidation of Day 6.

Consolidation of Day 6scheduled time

= 1:00am


time03:00 06:00 09:00 12:00

00:00

Day 7Day 6

In such cases, perform a manual consolidation of Day 6 later, during Day 7.






4 Recovery Tasks

4.2 Scenario C [cont.]

Manual Consolidation :

Choose the date of Day 6 (for example)Click on "start" to perform a consolidation on the chosen date.






4 Recovery Tasks

4.3 Scenario D

Outage for many days, more than 5 days.In such cases, the OMC-R does not have the data in memory anymore, and data can be considered as lost.

Alternative solution :1. Get a back-up from the OMC-R, no more than 5 days old2. Extract the PM files between the start of the outage of the end of the

outage3. Re-import the data in NPO

Beware, even on a back-up, there are only 5 days of PM files !


Re-importing PM files in NPO consists in loading the files in the ORACLE database, thanks to NPO loaders.





End of ModuleAdministration

RNO_NPA to NPO

Documents

Transcript of RNO_NPA to NPO