RNO - NPA To NPO

9159 NPO
RNO-NPA B9 to NPO B10

Evolutions
3FL12804AAAAWBZZA4
Edition 01
TRAINING MANUAL
9159 NPO - RNO-NPA B9 to NPO B10 Evolutions

All rights reserved 2007, Alcatel-Lucent
Copyright 2007 by Alcatel-Lucent - All rights reserved

Passing on and copying of this document, use and
communication of its contents not permitted without written
authorization from Alcatel-Lucent
All Rights Reserved 2007, Alcatel-Lucent
RNO-NPA B9 to NPO B10 Evolutions - Page 1
Legal Notice
2
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.
Caution
The equipment used during this course is electrostatic sensitive. Please observe correct anti-static precautions.
Trade Marks
Alcatel 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-Lucents
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
9159 NPO
All Rights Reserved Alcatel-Lucent 2007
without prior
written
permission
RNO-NPA
B9 to NPO
B10 Evolutions 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.
Disclaimer
In 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.

Table of Contents
3
1. NPO GSM

1. Introduction
2. Operation
3. Administration
9159 NPO
RNO-NPA B9 to NPO B10 Evolutions

Table of Contents [cont.]

4
9159 NPO
This page is left blank intentionally

Course Objectives
5
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 architecture

Perform all their operational tasks previously done on A9156 RNO and NPA, using A9153 NPA
Take profit of the new features & improvements of A9153 NPO
Perform typical administrative functions on A9153 NPO
9159 NPO

Course Objectives [cont.]

6
9159 NPO

About this Student Guide

7
Conventions used in this guide

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.
Warning
Alerts you to instances where non-compliance could result in equipment damage or
personal injury.
9159 NPO
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

About this Student Guide [cont.]

8
9159 NPO

Self-Assessment of Objectives
9
Contract number :
At the end of each section you will be asked to fill this questionnaire
Course title :
Please, return this sheet to the trainer at the end of the training
Client (Company, Center) :
Language Switch
:
to notes view!
Number of trainees :
Dates from :
to :
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
Instructional objectives
No (or
globally
no)
9159 NPO
Yes (or
globally
yes)

Comments
Self-Assessment of Objectives [cont.]

10
Instructional objectives
9159 NPO
Yes (or
Globally
yes)
No (or
globally
no)
Comments
Other comments
Thank you for your answers to this questionnaire

Do not delete this graphic elements in here:
Section 1
NPO GSM
Module 1
Introduction
3JK10680AAAAWBZZA Edition 04
9159 NPO RNO-NPA B9 to NPO B10 Evolutions


Section 1 Module 1 Page 1
Blank Page
NPO GSM Introduction
11
9159 NPO
Document History
Edition
Date
Author
Remarks
01
YYYY-MM-DD
Last name, first name
First edition

Objectives
9159 NPO
11

Objectives [cont.]
9159 NPO
11

Table of Contents
11
Page

1 Overview of A9159 NPO
1.1 Presentation of NPO
1.2 Comparison with previous architecture
1.3 Goals
1.4 Place in the mobile network
1.5 Configurations
1.6 Logical View
2 Interfaces with Data Sources
2.1 Overview (multi-standards)
2.2 Loaders
2.3 Dictionaries
3 Analysis Desktop
3.1 Overview
3.2 Network Resources Management
3.3 Properties & Functions
3.4 Views Browser
3.5 Right-pane browser
4 Questions
9159 NPO

7
8
9
10
12
16
21
22
23
24
25
27
28
32
33
35
37
38

11
9159 NPO

11
9159 NPO

1.1 Presentation of NPO

11
Network Performance Optimizer

Monitors the Quality Of Service of a network in a centralized way
z Integrates all QoS data and QoS services in one application
z
2G, 3G and WIMAX

Networks
9159 NPO
QoS Data & QoS Services :

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

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

z An analysis desktop composed of a graphical user interface that allows browsing and benefiting from the
optimization data of the data warehouse. It allows creating and displaying reports.
z External interfaces allowing an external system to extract QoS information from NPO

B10
B10
MR2
MR2
1.2 Comparison with previous architecture

11
Replacing the A9156 RNO, NPA and LASER.
A9157 LASER
B10 MR2
NPA
A9156 RNO
Advantages:
Easier O&M of softwares and databases
Faster access to QoS data
Simple and secure management of LAN
9159 NPO
A9159 NPO
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-networkengineering 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
11
Support radio network optimization activities
Planning
Optimization
Design
NPO
QoS
Monitoring
OMC-R
9159 NPO
Activities
Check 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

10
1.3 Goals [cont.]

11
Provide an effective way to:
Highlight
z
Detect network misbehaviors and QoS degradations
Rank
z
Help the optimization team to focus on the most urgent issues
Act
z
Fix the quality of service problems in a quick and accurate way
Manage
z
Decide the corrective actions to apply on the network
9159 NPO

11
1.4 Place in the mobile network

11
12
3 possible architectures:
1.
As an external software application (such as A9156 RNO)
GSM B9/B10 OMC-R
A9159 NPO
Software application
9159 NPO
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.]

B10
B10
MR2
MR2
11
13
2. As part of the A1353-MP Multi-Standard OMC Portal (in B10 MR2 : no multistandard)
1.
O&M
GSM B9/B10 OMC-R
O&M
MS NPO
MS SUP
MS PORTAL
WCDMA WNMS
(UA5)
9159 NPO
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.


11
14
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)
1.
NPOe
NPO with full features

and capacity < 250 cells
NPO Client (PC)
OMC-R Master
9159 NPO
OMC-R HMI
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 name
NPOE 250 OMC-R (NewHW, NewN HW) Small


11
15
As a standard feature, all OMC-R Master & OMC-R HMI provides basic
NPO functionalities.
z
z
z
z
z
z
ORACLE database in the OMC-R Master

Typical 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
MPM
NPO with limited

features and capacity up
to 6000 cells
OMC-R HMI
OMC-R Master
9159 NPO
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 name
MPM 250 OMC-R (V880, V490) Small
MPM 500 OMC-R (V880, V490) Standard
MPM 1200 OMC-R (V880, V490) Large-1
MPM 1500 OMC-R (V880) MPM 1800 OMC-R (V490) Large-2
MPM 4000 OMC-R (V880, V490) X-Large
MPM 6000 OMC-R (V490) XX-Large

1.5 Configurations
11
16
Webstart client
NPO Server
Windows XP SP2
Java Engine
V880/V490 Solaris 10
Oracle Server 10g
LAN
NPO Full Clients
Windows XP SP2
NPO HMI
ML370 series
Windows server 2003
Oracle client 10g
Citrix server 4
IP
WAN
256 kb/s
Citrix client
Citrix Client 9.0
9159 NPO
By compressing data over the network, the HMI server allows to use low bandwidth networks without decreasing
the 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

B10
B10
MR2
MR2
1.5 Configurations [cont.]

11
Max NPO
Users
Sessions Nb.
Max Users
Sessions
Nb./ HMI
Server
Hosted By
250
1(*)
OMC-R
NPO 2000
2000
8 NPO
10
Standalone machine
NPO 5000
5000
15 NPO
10
Standalone machine
NPO 8000
8000
25 NPO
10
Standalone machine
NPO 10500
10500
26 NPO
10
Standalone machine
NPO 12000
12000
28 NPO
10
Standalone machine
NPO 24000 (*)
24000
48 NPO
10
Cluster (*)
NPO
Configuration
Name
Cells Nb.
NPOe 250
MS
PORTAL
needed
(*) Uses 2 V480 SUN Servers (nodes) that cooperates as a single system. Based
on Oracle Real Application Clusters (RAC).
Available in B10 MR2.
9159 NPO
Sun Fire V880 = New HW

Sun Fire V490 = NewN HW
Starting from NPO 5000 configuration, External Disk Bay SE3510 is used.

17

NPO Clients
Configuration
Ram Memory
11
NPO Full & Webstart

based client
NPO Light client
>= 1 Gb DDRam
>= 512 Mb DDRam
Processor
Pentium >= 1.7 GHz
Hard disk
SATA or ATA 18 GB / 7200 rpm
DVD
Internal DVD-ROM 16x
Monitor
Operating system
18
21 "
Windows XP Professional 2
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.
9159 NPO
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.

B10
B10
MR2
MR2

NPO Server
Configuration
NPO 250
NPO 2000
NPO 5000
NPO 8000 (*)
Server
model
11
Processors
SUN V490
Memory
Internal disks
External disk array
See Small OMC configuration
SUN V880
SUN V490
2 x 1.35 GHz
8 GB
2 x 146 GB
SUN V880
2 x 900 MHz
4 GB
6 x 73 GB
None
None
SUN V490
2 x 1.35 GHz
8 GB
2 x 146 GB
SE 3510 : 6x73 GB 15Krpm

1 RAID controler
SUN V880
4 x 900 MHz
8 GB
6 x 73 GB
None
SUN V880
8 x 750 MHz
16 GB
12 x 73 GB
None
NPO 10500
SUN V490
4 x 1.35 GHz
16 GB
2 x 146 GB
SE 3510 : 12x73 GB 15Krpm

2 RAID controlers
NPO 12000
SUN V490
4 x 1.35 GHz
16 GB
2 x 146 GB
SE 3510 : 12x146 GB 15Krpm

2 RAID controlers
NPO 24000
2 x SUN V490
4 x 1.35 GHz per

V490
16 GB per
V490
2 x 146 GB per
V490
V880
9159 NPO
19
1 SE 3510 per V490 with :

-
12x146 GB 15Krpm
1 RAID controlers
1 FC switch
V490
(*)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.
data warehouse.


NPO HMI Server

Configuration
Operating system
Processor
11
ML370 G4
Max Numbers of users

Software
DL360 G5
Windows 2003 Server Enterprise Edition (with CAL servers)

2 x 3.4 GHz (single core)
RAM
Disks
20
2 x 2 GHz (dual core)
8 Gb [ 4Gb*]
1 x 36 Gb
1 x 72 Gb
10 [ 5*]
CITRIX Presentation Server Edition
* : Typical configurations of ex-RNO or ex-LASER servers (for reuse purposes)
9159 NPO
(*)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.
data warehouse.

1.6 Logical View

11
Optimization
Optimization(NPO)
(NPO)
NPO
NPOBrowser
Browser
Migration
MigrationFacilities
Facilities
Administration
AdministrationFacilities
Facilities
Offline
OfflineTools
Tools
Analysis
AnalysisDesktop
Desktop
Administration
Administration
User
UserInterface
Interface
Platform
Platform
External
External
Systems
Systems
Diagnostic
DiagnosticDev
Dev
Environment
Environment
Data
DataWarehouse
Warehouse
Consolidations
Consolidations
21
MAAT
MAAT
Tomcat
Tomcat
EQL
EQL
Mediations
Mediations
Security
Security
Generic
GenericLoader
Loader
Generic
GenericTuner
Tuner
System
System&&Utilities
Utilities
Loading
LoadingPlug-in
Plug-in
Tuning
TuningPlug-in
Plug-in
OMC-R
OMC-R//RNP
RNP
(data
(datasources)
sources)
9159 NPO
OMC-R
OMC-R
(tuneable
(tuneablesystem)
system)
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 suite
It 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.

11
9159 NPO

22
2.1 Overview (multi-standards)

11
23
GSM B9/B10 OMC-R

BSC
MFS
X25
X25
IP
IP
MS-NPO
(in MS-PORTAL)
WCDMA WNMS
IP
IP
RNC
IP
IP
WIMAX OMC-R
WAC
IP
IP
IP
IP
IP
IP
A9155 RNP
Planning
9159 NPO
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:
z
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:
z
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:
z
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
11
24
Generic loaders and specific plug-ins

Files from multiple sources
in multiple formats
NPO
Specific
SpecificPlug-Ins
Plug-Ins
Loader
RNP
RNPGeneric
Generic
Loader
Loader
QOS
QOSGeneric
Generic
Loader
Loader
Data
Warehouse
Param
ParamGeneric
Generic
Loader
Loader
CSV files
9159 NPO
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
11
25
z NPO relies on dictionaries to describe:

z
z
z
z
z
z
z
z
Radio parameters
QoS Counters and Indicators
QoS Thresholds (for indicators)
Reports & Views templates
Diagnosis
Thematic Layers
Rules
Reference Values
z Each dictionary can be customized by NPO administrator and system
user.
z A dictionary is an XML file.
9159 NPO
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.]

11
26
Dictionary
XML
NPO
NPO
Administration
AdministrationFacilities
Facilities
Data
DataWarehouse
Warehouse
Admin & System
9159 NPO
User
Creation/modification of user-defined indicators and reports can easily be performed through the Analysis
Desktop.
For standard operation & administration, creation of indicators / reports can be performed thanks to graphical
interface, 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.

11
3 Analysis Desktop
9159 NPO

27
3 Analysis Desktop
3.1 Overview
11
28
3 Ways to start NPO Analysis Desktop

1.
Webstart (Java interface)
2.
NPO Client application
9159 NPO
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:
z Standards and Modes Browser Standards define the technologies available on NPO (GSM, UMTS, WiMAX).
z 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.
z 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).
z 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
z View Browser The view browser is the target place for drag and drop of one or more network resources and one
or more functions.
z
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.
z 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.

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

z Data displayed in the report can be exported to Excel for further analysis.
3 Analysis Desktop
3.1 Overview [cont.]

11
29
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
9159 NPO
or more functions.
z


3 Analysis Desktop

11
30
Standards
Modes
Functions
Network object
management
Cartography, Diagnosis,
Tuning Session
& Reports Browser
Views Browser
9159 NPO
or more functions.
z


3 Analysis Desktop

11
31
Click
Drag and Drop
Drag and Drop
9159 NPO
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

11
Navigation
between GSM,
WCDMA, WIMAX
32
Different tree gadgets are used to display the

network resources by different sort criteria.
WIMAX
WCDMA WIMAX
WCDMA
Contextual menu
provides additional
functions.
Radio resources of the network are displayed in

tree gadgets and can be selected from there.
9159 NPO
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:
z Topology Classification Tabs These are the set of tabs for topology mode classification.
z 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.

z 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.

z 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

11
Properties (logical parameters) and functions

belonging to a network resource selected in the
Network resources management
Contextual menu
provides additional
functions.
9159 NPO

33
3 Analysis Desktop
3.3 Properties & Functions [cont.]

9159 NPO
11

34
3 Analysis Desktop
3.4 Views Browser

11
35
The browser can

handle several
executed views
Contextual menu
recaps the side
menu
Tools for further

analysis
Spreadsheet mode
Graph mode
9159 NPO
The executed view browser can contain:

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

3 Analysis Desktop
3.4 Views Browser [cont.]

11
36
Toggle between tabular mode and graph

Propagate
Export to Excel
Spatial Roll up & Drill down
Temporal Roll up & Drill down
Graph mode
Spreadsheet mode
Save the executed view as a template
Legend & comparisons

Highlights according to comparisons
Rotate the executed view
Zoom in / Zoom out
Clear all filters

Filter repeated value(s)
Display values at cursor
Filter
9159 NPO
The side bar offers different functions depending on the mode (graph or tabular mode).

3 Analysis Desktop
3.5 Right-pane browser

11
The right-pane browser allows to display several modules:

QoS Reports
Diagnosis
Tuning Sessions
Cartography
9159 NPO
The executed report browser can contain:

z One or more network objects
z One or more view templates / report templates.

37
11
4 Questions
9159 NPO

38
Answer the Questions

11
z What are the main types of data collected by NPO ?

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

For
a multi-RAT network, what is the only solution ?
z If one NPO user is getting a slow bandwidth,
which solution is to be implemented in order to increase the

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

39
Self-Assessment on the Objectives

11
z Please be reminded to fill in the form

for this module
z The form can be found in the first part
of this course documentation
9159 NPO

40
Summary
11
z B10 MR2 Features :

z Network unavailability and stability monitoring (LASER)
z Alarm statistic reporting (LASER)
z Centralized hardware inventory data management (LASER)
z Warrantee management (LASER)
z GoogleEarth export (Cartography)
z Support up to 12k GSM cells (24k with MS PORTAL)
TM
9159 NPO

41
11
End of Module
Introduction
9159 NPO

42
Section 1
NPO GSM
Module 2
Operation


Blank Page
NPO GSM Operation
12
9159 NPO
Document History
Edition
Date
Author
Remarks
01
YYYY-MM-DD
First edition

Objectives
NPO GSM Operation
9159 NPO
12

Objectives [cont.]
NPO GSM Operation
9159 NPO
12

Table of Contents
NPO GSM Operation
12

1 Introduction to radio network data
1.1 QoS Counters
1.2 QoS Indicators
1.3 Radio Parameters
2 Working with Views Browser
2.1 Execute a View
2.2 Analyse, in tabular mode
2.3 Analyse, in graphical mode
2.4 Favorites
3 Basic QoS Monitoring
3.1 Execute a Report
3.2 Analyze a Report
3.3 Collect relevant data
3.4 Create an Object Zone
3.5 Free fields
3.6 Create a Report
4 Parameters Checking
4.1 Parameters management
4.2 Tabular Comparisons
4.3 Events detections
4.4 Events Synthesis
4.5 Define Reference Settings
4.6 Assign Classes to Cells
9159 NPO
4.7
Customize Reference DictionnaryAll Rights Reserved Alcatel-Lucent 2007
4.8 Rules
5 Parameters Tuning
5.1 Benefits
5.2 Process
5.3 Interface
5.4 Reference cells
5.5 Post-its
6 Distribution Reports
6.1 Overview
6.2 Method
7 Import a cartography project
7.1 Overview
7.2 Project Structure
7.3 COF files
7.4 Format of background map
7.5 Import
7.6 Configuration files
8 Analyze a QoS problem
8.1 Presentation
8.2 Cartography pane
8.3 Cartography functions
8.4 Cartography & Tuning Session
8.5 Thematic Layers
8.6 Export in GOOGLE EARTH
8.6 Diagnosis
9 A day at work with NPO
9.1 Schedule
9.2 Know your colleagues
9.3 Interaction with other teams
9.4 Scheduled Reports
10 NPO Customization

Page
7
8
11
23
25
26
33
38
40
42
43
49
50
52
57
61
71
72
74
76
77
80
81
84
89
95
96
97
98
102
103
109
110
113
116
117
118
119
125
126
128
130
131
132
138
144
146
148
150
155
156
157
158
162
169

NPO GSM Operation
12
Page

10.1 Classification
10.2 User Preferences
10.3 Customer Topology Objects
11 Annex
11.1 Indicator Editor
9159 NPO
170
175
179
187
188

NPO GSM Operation
12
9159 NPO

1.1 QoS Counters

NPO GSM Operation
12
z Performance Management Counters describe events occurring on the
network
How many calls in this cell ?

z How many handovers ? Etc.
z
z There is a specific PM Counter associated to each event (# calls
established, # call drops, # handovers, etc)

z
Number of calls = Number of TCH's successfully allocated for a "Normal

Assignment" call (normal assignment = not a handover)
9159 NPO
QoS means "Quality of Service"

1.1 QoS Counters [cont.]

NPO GSM Operation
12
z There are 4 types of counters :

z
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
9159 NPO
Cumulative counters
MC01 : 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
NPO GSM Operation
12
z Associate cumulative counters to messages in this
protocol (Radio Link Establishment, MO)

MC8c
MC148
MC8b
5 minutes
MCO2h
C253
C255
9159 NPO
Refer to the previous slide to find the counters and their definition.

10
1.2 QoS Indicators

NPO GSM Operation
12
z An indicator is a formula of counters

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

i.e. SDNAUR = (# of requests # of successes) / (# of successes)
z
z There are many families of indicators
TCH, SDCCH, Handovers

z GSM, GPRS
z Traffic, Durations
z RMS averages,
z
9159 NPO

11
1.2 QoS Indicators [cont.]

NPO GSM Operation
12
z Unlike counters, indicators are consolidated !

z Temporal aggregation
z
Counters are only hourly, but indicators can be hourly, daily, weekly,
monthly or at busy hour.
z Spatial aggregation
z
Counters are only available for the basic network element, but indicators
can be aggregated at higher levels.
9159 NPO

12

NPO GSM Operation
raw
Indics
12
hourly
spatial
aggregation
normalisation
hourly
daily
QoS
files
temporal
aggregation
daily
temporal
aggregation
daily
weekly
monthly
monthly
measured object
temporal
aggregation
temporal
aggregation
weekly
9159 NPO
hourly
spatial
aggregation
temporal
aggregation
temporal
aggregation
13
weekly
monthly
intermediate object
network
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.


NPO GSM Operation
12
14
z N objects aggregated to the parent object

Qi=265
Qi=265
Aggregated values of day D

available only at D+1
Qi=45
Qi=45
Spatial aggregations are

performed each night, started
by the scheduler
Qi=80
Qi=80
Qi=27
Qi=27
Qi=113
Qi=113
Qi=25
Qi=25
Qi=40
Qi=40
Qi=15
Qi=15
9159 NPO
Qi = QoS Indicator
z 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.
z The spatial aggregation is always done on the normalized data, before the temporal aggregation.
Possible spatial aggregations are: MIN, MAX, SUM, AVG, ...


NPO GSM Operation
12
15
z N periods aggregated to the parent period
Aggregated values of day D

available only at D+1
Temporal aggregations are
performed each night, started
by the scheduler
W
9159 NPO
z 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.
z When the indicator is defined, it is possible to have several aggregation functions; in this case there are several
linked indicators.
z Two types of temporal aggregation can be defined:
z
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)
z Possible temporal aggregations are: SUM, MIN, MAX, BH, 3DAV, ...


NPO GSM Operation
12
16
Different types of aggregation are available:

z
z
z
z
z
z
Total (TOT)
Maximum (MAX)
Minimum (MIN)
Average (AVG)
Busy Hour (BH) (only for temporal aggregation)
3DAV,
9159 NPO
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

DELTA RNO-NPO
DELTA RNO-NPO
NPO GSM Operation
12
17
z If there are missing data :
9159 NPO
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.

DELTA RNO-NPO
DELTA RNO-NPO
NPO GSM Operation
12
With the RNO/NPA tool chain we have only two interpolation possibilities
1. Linear
2. Padding by zero
NPO interpolation possibilities was extended

1. Linear interpolation
2. No interpolation
3. Padding
4. Only OK
5. Extend
9159 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..

18

NPO GSM Operation
12
19
z It is possible to create a new indicator with NPO

z
Click on
5
2
3
9159 NPO
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")


NPO GSM Operation
12
20
z 3 types on Indicators : Basic, Calculated & Temporal Aggregation

z
Input & Storage policy :

COUNTERS
PARAMETERS
ORACLE DB
BASIC
INDICATORS
TEMPORAL AGGREGATION
INDICATORS
INDICATORS
CALCULATED
INDICATORS
INDICATORS
Stored in DB
On-the-fly
CALCULATED
INDICATORS
INDICATORS
Session
9159 NPO
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.


NPO GSM Operation
12
z Typical indicators :
Copy RTCH_assign_request (GTCNARQN)

z Copy RTCH_assign_cong_rate (GTCNACGR)
z Copy RTCH_Erlang_total (GTCTRE)
z
z Explore the contents of each indicator, especially their temporal
aggregations
z
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.
9159 NPO

21
Exercise
NPO GSM Operation
12
z Create one indicator "CD_per_Erl"
Calculated indicator
z Formula : Number of call drops / TCH erlang total
z
Calculated aggregation at busy hour

z Formula : Number of call drops BH / TCH erlang BH
z
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
9159 NPO

22

NPO GSM Operation
12
23
z A set of parameters defines the operationnal behaviour of one element
in the network
BCCH : frequency on which is broadcasted the BCCH

z # of SDCCH : number of SDCCH subchannels in the cell
z L_RXLEV_DL_H : threshold to trigger a handover cause 5 (low level in the
downlink)
z EN_DR : flag to activate the directed retry feature
z
z Most of them describe cells, but some can also describe BSC, TRX or
adjacencies
z There are two main types of parameters :

z
z
Logical Parameters
Design
9159 NPO

Exercise
NPO GSM Operation
12
24
1. What is the definition of these indicators :
HOOBRQR
z HOOBEFR
z
2. Extract the 2 indicators from NPO
For 1 cell
z Hourly, for the past 2 hours
z Daily, for yesterday
z
3. Find counters related to these indicators

z
Hourly, for the past 2 hours
10 minutes
9159 NPO
In indicators' properties (contextual menu), it is possible to find the definition and the formula of each indicator

DELTA RNO-NPO
DELTA RNO-NPO
NPO GSM Operation
12
9159 NPO

25
DELTA RNO-NPO
DELTA RNO-NPO
2.1 Execute a View

NPO GSM Operation
12
Modes
Functions
Network object
management
Cartography, Diagnosis,
Tuning Session
& Reports Browser
Views Browser
9159 NPO

26
2.1 Execute a View [cont.]

NPO GSM Operation
12
z To display reports
In tabular format (Excel-like)

z Or In graphical format (one "view" at a time)
z
z For instance, extract those indicators :

z
z
z
z
z
z
z
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)
z Then, extract this view

z
DELTA RNO-NPO
DELTA RNO-NPO
Alc_Call_Drop
9159 NPO
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 !

27
DELTA RNO-NPO
DELTA RNO-NPO

NPO GSM Operation
12
28
z 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
9159 NPO
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.
List of hours in the report

20
21
22
23
07/11/2007
10
18
07/12/2007
19
20
21
22
07/14/2007
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
20
21
22
23
07/11/2007
10
07/12/2007

23
07/15/2007
DELTA RNO-NPO
DELTA RNO-NPO

NPO GSM Operation
12
z "Trends" provide data for a typical day, a typical week or a typical
month.
Trends (only for Indicators)
9159 NPO
1.
Aggregated values for each hour (023) over

several days
2.
Aggregated values for each hour (023) 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

29
DELTA RNO-NPO
DELTA RNO-NPO

NPO GSM Operation
12
z The Options tab : QoS Requirements, Sampling/Reliability and
Interpolation for indicators only
QoS Requirements
Low, Medium or High. Changes the thresholds
for indicators.
Sampling / Reliability
Sampling : check if sampling is not enough
(gray)
Reliability : check if all data are missing
before aggregation (italic)
Interpolation
Only needed for indicators, and if "dynamic
interpolation" = TRUE (see user preferences)
9159 NPO

30
DELTA RNO-NPO
DELTA RNO-NPO

NPO GSM Operation
12
31
z The Options tab : other options
Forecast values
Select the tuning sessions whom forecast
values to display (Parameters only)
Unavailable objects
Filter out NE that are unavvailable, based on a
criteria applied on a QoS indicator
Event
Overlay events (parameter changes) on a
report (Parameters or Indicators, daily only)
9159 NPO

DELTA RNO-NPO
DELTA RNO-NPO
Exercise
NPO GSM Operation
12
32
Let's follow a typical scenario of report analysis

Clear the views browser
2. Extract (1) a list of indicators for all cells in one BSC
1.
3.
Periodicity = DAILY, DAY = YESTERDAY, QoS Requirements

= HIGH
Extract (2) the same report with

}
QoS Requirements = LOW
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 yesterday
6. Brainstorming : Define a list of KPI
7. Extract (5) those KPIs per BSC, for all BSCs
4.
8.
Periodicity = WEEKLY, DAY = one day last week, QoS Requirements = HIGH
Extract (6) a report containing BCCH, BSIC, FREQUENCIES and NUMBER

OF TRX per cell, for yesterday
10 minutes
9159 NPO
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, High
Report 2 : call drop indicators yesterday, Low
Report 3 : traffic indicators yesterday, Low
Report 4 : cell parameters yesterday (cell reselection)
Report 5 : BSC indicators, last week, High
Report 6 : cell design yesterday
Don't delete them, they will be use in the next exercise !
KPI : Key Performande Indicators
List of KPI (to fill up) :
1.
2.
3.
4. ...
5.
6.
7.
8.

2.2 Analyse, in tabular mode
DELTA RNO-NPO
DELTA RNO-NPO
NPO GSM Operation
12
z The side bar provide advanced tools for analysis

z
z
z
z
z
Legend and comparisons

Propagation
Filter
Roll up / Drill down,
Refer to "Introduction 4.3"
z Therefore, it is not necessary to export to Excel to perform an analysis

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

33
DELTA RNO-NPO
DELTA RNO-NPO
Exercise 1/4
NPO GSM Operation
12
FILTER and LEGEND
z Report 1
z Filter cells with RTCH drop rate > 3.0 %
z Select and propagate these cells
} How
many cells ?
Answer :
z Remove the filter

z Highlight 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
9159 NPO

34
DELTA RNO-NPO
DELTA RNO-NPO
Exercise 2/4
NPO GSM Operation
12
ORDER, PROPAGATE & ROLL UP
z Report
z
Highlight and open the legend : select and propagate all cells that exceed
the orange threshold for the RTCH drop rate
}
Answer :
Which cell is the worst one ?
Answer :
Select and propagate this cell. Find this cell's TRXs :

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

}
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 ?
9159 NPO
Answer :

35
DELTA RNO-NPO
DELTA RNO-NPO
Exercise 3/4
NPO GSM Operation
12
DRILL DOWN & ROLL UP
z Report 3
z Spatial drill down to check TRX traffic on those cells
} Is
there any TRX that carries no traffic ?
z Temporal drill down to check hourly traffic evolution for those TRX
} Is
there any activity ?
z Temporal roll-up (x2) to check weekly traffic
9159 NPO

36
DELTA RNO-NPO
DELTA RNO-NPO
Exercise 4/4
NPO GSM Operation
12
ROTATE, DRILL DOWN, ROLL UP
z Report
Rotate the view

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

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

Answer
Answer
Answer
Answer
:
:
:
:
37
DELTA RNO-NPO
DELTA RNO-NPO
2.3 Analyse, in graphical mode

NPO GSM Operation
12
z Instead of working with tabular
data, graphics are available
z Same set of advanced tools :

z
z
z What is a View ?
A graphic based on several QoS

indicators
z Designed by the user (a set of
standard views is proposed by
default)
z In the tab "View"
z
9159 NPO
z
z

Propagation
Roll up / Drill down
Navigation & Display
Toggle back to tabular mode

38
DELTA RNO-NPO
DELTA RNO-NPO
Exercise
NPO GSM Operation
12
z Close all current tabs in the views browser

z Execute "Alc_call_efficiency" and "Alc_RTCH_capacity"
Daily
z For the past 5 days
z For 2 cells
z
z Verify that both reports will allow a drill down at TRX level
z
Possible ?
Answer :
z Select one view :
Zoom in and out

z Toggle between graphical and tabular modes
z Perform a spatial drill down & roll up
z Perform a temporal drill down & roll up
z
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.
9159 NPO

39
DELTA RNO-NPO
DELTA RNO-NPO
2.4 Favorites
NPO GSM Operation
12
z Favorites are a simple way to save a selection of functions

z It is especially useful with QoS Indicators. The list of indicators chosen
before can be saved !
9159 NPO

40
DELTA RNO-NPO
DELTA RNO-NPO
2.4 Favorites [cont.]

NPO GSM Operation
12
z To organize favorites :
Menu bar : "Data > Favorites > Organize "

z Drag and Drop indicators from one group to another group
z
z One group of favorites can contain multiple sub-groups

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

}
TCH Assignment Unsuccess

{
{
{
{
{
TCH_Assign_Fail_Radio
TCH_Assign_Fail_BSS
TCH_Assign_Cong
TCH_Assign_prep_fail_BSS
TCH_Assign_Unsuccess_Rate
Sub Group "TCH Assignment Unsuccess" (5 indics)
SDCCH Drop
{
{
{
SDCCH_drop_radio
SDCCH_drop_BSS
SDCCH_drop_rate
Sub Group "SDCCH Drop" (3 indics)
Call_Setup_Success_rate
} SDCCH_assign_request
}
9159 NPO

41
NPO GSM Operation
12
9159 NPO

42
3.1 Execute a Report

NPO GSM Operation
12
z What is a Report ?
Stack of several Views

z Displays a set of QoS Indicators
z Advanced tools for analysis still available
z
z 5 families of QoS Reports
9159 NPO

43
3.1 Execute a Report [cont.]

NPO GSM Operation
12
z Drag and Drop several NE with several reports in the Reports Browser
z The Execution Context window appears
Identical to the Execution Context window when using the Views Browser
z Refer to "Working with Views Browser"
z
z Fill up the required information
9159 NPO

44
Exercise
NPO GSM Operation
12
z Connect each family to its specificity

z
You are welcome to use NPO in order to understand

the difference between each family
Mono
MonoObject
ObjectDistribution
Distribution
11NE,
NE,nnindicators,
indicators,nnperiods
periods
Mono
MonoObject
ObjectEvolution
Evolution
nnNE
NE>>threshold,
threshold,11period
period
Multi
MultiObject
ObjectComparison
Comparison
RMS
RMSmatrices
matrices&&vectors
vectors
Multi
MultiObject
ObjectEvolution
Evolution
nnNE,
NE,nnindicators,
indicators,11period
period
Warning
Warning
nnNE,
NE,11indicator,
indicator,nnperiods
periods
9159 NPO
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

45
3.1 Execute a Report [cont.]

NPO GSM Operation
12
z Notice that Reports are available for different NE's
9159 NPO
DELTA RNO-NPO
DELTA RNO-NPO

46
Exercise 1/2
NPO GSM Operation
12
For each need, find the appropriate report

1.
2.
3.
4.
5.
6.
7.
QoS manager needs an overview of the GSM network

O&M team needs to verify call drop causes on one cell
GPRS team needs the transmission resources usage of
each GPU's (and Ater's) of one BSC
Optimization team wants the list of the 10 cells with the
worst SDCCH drop rate
Design team needs to check the traffic split between a
cell and its neighbours
Design team needs to check the call efficiency rate
among the different TRX of a cell
An optimizer changed an adjacency parameter and needs
to check the evolution of HO flows between a cell and its
neighbours
20 minutes
9159 NPO
Advice : check the properties of a report, in order to know how the result will look like.

47
Exercise 2/2
NPO GSM Operation
12
48
By checking the properties of "Alc_Mono_QoS", you can read

its template. Answer the following questions :
1.
2.
3.
4.
5.
6.
7.
How many views ?

What is the name of the 1st view ?
Can you find it among the Views in the functions browser ?
How many indicators ?
Which ones are on the primary axis ?
On the secondary one ?
Why ?
Execute the 1st QoS view for one cell, for the last 10 hours
z Execute Alc_Mono_QoS for the same cell, for the past 10
hours
z Observe
z
9159 NPO
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 !

B10
B10
MR2
MR2
3.2 Analyze a Report

NPO GSM Operation
DELTA RNO-NPO
DELTA RNO-NPO
12
49
z All advanced tools for analysis are available

z
z
z
z
z

Propagation
Roll up / Drill down
Navigation & Display
Toggle back to tabular mode,
z Export to Excel provides a way to share the results with different teams
z Specific tools for reports are :
Link cursors
z Link zooms
z
Resize Legends
9159 NPO

DELTA RNO-NPO
DELTA RNO-NPO
3.3 Collect relevant data

NPO GSM Operation
12
z Default data might not suit your needs !
How can I compare

CDR between
GSM900 cells and
DCS1800 cells ?
z You must customize NPO
Create new object zones

z Create new QoS data (indicators, views, reports)
z
9159 NPO

50
3.3 Collect relevant data [cont.]
DELTA RNO-NPO
DELTA RNO-NPO
NPO GSM Operation
12
zWhat is an object zone ?
Subset of NE's that verifies a filter

z Filter(s) are defined by the user
z
zTo put it simply, an object zone is an intermediate step in the
consolidation of indicators
zNaming conventions :
Type of NE's
Name of the object zone
Cells
Cell Zone
TRX's
TRX Zone
TRXs from same zone, same

frequency, same cell split, and within
the same cell
Traffic Zone
Others
Generic Zone
9159 NPO
An object zone can be created from any network element ! GPU, BSC, A interface, etc
The traffic zones are AUTOMATICALLY generated by NPO.

51
3.4 Create an Object Zone

NPO GSM Operation
12
Object zones
9159 NPO
DELTA RNO-NPO
DELTA RNO-NPO
Click on the tab "Cell zone", "TRX zone" or "Generic zone"

Open the contextual menu, and click on Open Zone Manager

52
DELTA RNO-NPO
DELTA RNO-NPO
3.4 Create an Object Zone [cont.]

NPO GSM Operation
12
53
4
1
2
3
9159 NPO
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.)

DELTA RNO-NPO
DELTA RNO-NPO
3.4 Create an Object Zone [cont.]

NPO GSM Operation
12
z Logical operators
z
INTERSECTION(1,2) = 1 AND 2
UNION(1,2) = 1 OR 2
EXCLUSION(1,2) = 1 XOR 2
9159 NPO

54
DELTA RNO-NPO
DELTA RNO-NPO
Exercise
NPO GSM Operation
12
55
Create the following zones :

1.
2.
3.
4.
5.
6.
Cells from BSC 1

Depending on your network, create one zone per "CELL
TYPE" AND per "FREQUENCY RANGE" (single, umbrella, mini,
micro or indoor)
Cells with at least one TRX with TCH assign efficiency % <
90% and TCH allocated > 200, and that belongs to BSC 1
TRX with TRX PREF MARK = 0 and belongs to cells which have
more than 3 TRX
TRX with less than 1 erlang per day
GPUs from BSC 1 and BSC 2
Close the Zone Editor, and find your Zones in NPO

z "Compute" each zone
z
How many NE's for each zone ?
Zone
# of NE
1
2
3
4
5
6
15 minutes
9159 NPO
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.

DELTA RNO-NPO
DELTA RNO-NPO
Exercise
NPO GSM Operation
12
z Provide the following data :

z
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
9159 NPO
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.

56
DELTA RNO-NPO
DELTA RNO-NPO
3.5 Free fields

NPO GSM Operation
12
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 !
57
Create manually a "CSV" file, following a specific format

2. Import the "free fields" file within NPO
1.
z
z
With NPO interface

Or with command line
9159 NPO
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.]

NPO GSM Operation
DELTA RNO-NPO
DELTA RNO-NPO
12
58
z File format for "2G cells" 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>;
(*) LAC_ID : depends on mode CI
53;20;3;53231;<value1>; <value2>;
or LAC/CI
53;20;3;53232;<value1>; <value2>;
z File format for "other NE's" free fields

FREE FIELD;<optionnal comments>; <optionnal comments>;<TYPE>
OXEID;<field1>;<field2>;
GPU_BSC1/2/16779009;<value1>; <value2>;
9159 NPO
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.]

NPO GSM Operation
DELTA RNO-NPO
DELTA RNO-NPO
12
59
z Import Free Fields with NPO Import/Export Management
z Browser for your file and import it
9159 NPO
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:
z
cd /alcatel/muse/MUSE_QOS/topology/bin
./loadFreeFields.sh <fileName>
Where <fileName> is the absolute path and name of the Free Fields file.
Example:
z
./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.

DELTA RNO-NPO
DELTA RNO-NPO
Exercise
NPO GSM Operation
12
z Each client :
Create a Free Field file (from scratch)

z Import the MNC / MCC / CELL ID (and LAC ID) from NPO
z Create 2 new fields : CITY and PROVINCE
z Fill up the columns with random data
z
}
}
Ex : cities = Lannion, Stuttgart, Shanghai, Timisoara,

Ex : provinces = South, North,
Import in NPO, using NPO Import/Export Management

z Create a Cell Zone for one province
z
10 minutes
9159 NPO

60
DELTA RNO-NPO
DELTA RNO-NPO
3.6 Create a Report

NPO GSM Operation
12
View (1)
Secondary axis
Primary axis
Legend
9159 NPO

61
DELTA RNO-NPO
DELTA RNO-NPO
3.6 Create a Report [cont.]

NPO GSM Operation
12
Methodology
Define the purpose of this report
2. Define all indicators you need
3. Distribute indicators per view
4. Distribute indicators per axis
5. Create the views
6. Create the report
1.
View Editor tool
Report Editor tool
Click on
Click on
Or Data > Views Templates
Or Data > Reports Templates
Or "Ctrl + E"
Or "Ctrl + R"
9159 NPO

62

NPO GSM Operation
12
63
6
2
3
4
5
Existing views
9159 NPO
Properties of a view
List of functions
& properties
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


NPO GSM Operation
12
4
2
9159 NPO
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

64

NPO GSM Operation
12
65
z Distribution reports
Based on Matrix or Vector indicators

z Related only to RMS and GPRS Distribution indicators
z 1 view / indicator
z User can customize the cosmetics only
z
9159 NPO
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)


NPO GSM Operation
12
66
z Warning reports
Based on a standard views

z Additional information for filtering :
z
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"
Additional info in
"report editor"
9159 NPO
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)

DELTA RNO-NPO
DELTA RNO-NPO
Exercise 1/4
NPO GSM Operation
12
20 minutes
STANDARD REPORT
All together, design a report for daily monitoring

Purpose = GSM daily monitoring
z Which indicators ?
z In which views ?
z On which axis ?
z
Each group will create one view

z Once all views are created, each group will copy others' views
z Each group will create a new report
z
9159 NPO
Don't forget to create your views and your reports in your own "family"

67
DELTA RNO-NPO
DELTA RNO-NPO
Exercise 2/4
NPO GSM Operation
12
DISTRIBUTION REPORT
Create a report with 2 views :

1 matrix "DL RxLev vs Quality"
z 1 vector "Path Balance"
z
9159 NPO

68
DELTA RNO-NPO
DELTA RNO-NPO
Exercise 3/4
NPO GSM Operation
12
69
WARNING REPORT
z
z
Edit your own view refering to CDR

Set the missing "warning" information
z
z
z
z
z
z
Save, and copy this view

Change the warning information
z
z
z
z
Filtering indicator = RTCH Drop Rate

Ordering indicator = RTCH Drop Rate
Based on "orange + red" threshold
Display 5 days "before", 0 days "after"
Filtering indicator = RTCH Drop Rate

Ordering indicator = Call Drop (number)
Worst 20 cells
Display 2 days "before", 0 days "after"
Create a warning report, containing these 2 views
9159 NPO
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.

DELTA RNO-NPO
DELTA RNO-NPO
Exercise 4/4
NPO GSM Operation
12
70
EXECUTION
4. Exit the Report Editor, and execute your 3 reports

z Report 1 : good for daily monitoring ?
z Report 2 : difference between matrix and vector ?
z Report 3 : difference between the two views ?
9159 NPO
The report 1 teaches very important rules :
RULE 1 :
analysis.
Always associate a number to a rate !! A rate by itself does not give enough information for
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.

NPO GSM Operation
12
9159 NPO

71
4.1 Parameters management
DELTA RNO-NPO
DELTA RNO-NPO
NPO GSM Operation
12
z The parameters are imported from OMC-R to NPO every night
Open NPO DATA MANAGEMENT

Select Configuration System Scheduling
What time is your parameters import ?
z NPO will keep track of all daily configurations, for a duration of "MAX
PREVIOUS DAYS"
Open NPO Administration Data Management :

Select Configuration > Data Source
Choose an OMC-R, Click on "Update", "Next"
Check the MAX PREVIOUS DAYS field
How long are your daily configurations stored ?
9159 NPO
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

72
4.1 Parameters management [cont.]

NPO GSM Operation
12
73
z NPO can compare operationnal parameters with other values :
Operationnal parameters vs.
Historical values (from previous days)

Reference values (from your default settings)
Forecast values (from tuning session)
z Parameters checkings can be fully performed on NPO !
Tabular comparisons
z Events detections
z Events synthesis
z
9159 NPO
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

NPO GSM Operation
12
Navigate between
operationnal and
reference values
Drag and Drop
9159 NPO

74
4.2 Tabular Comparisons [cont.]

NPO GSM Operation
DELTA RNO-NPO
DELTA RNO-NPO
12
z The legend and highlight tools allow to compare operationnal values
with other values
z In the Legend window, you can select only cells which do not follow
reference values :
Green :
Yellow :
Orange :
Red :
OPE = REF
OPE REF boundaries
OPE(day=d) OPE(day=dOPE(day=d-1)
OPE REF boundaries
9159 NPO

75
DELTA RNO-NPO
DELTA RNO-NPO
4.3 Events detections

NPO GSM Operation
12
z Events show when a key information is changed
Highlight a logical/design parameters change

z Highlight a topology change
z
z An event is represented by a graphical symbol :
9159 NPO

76
DELTA RNO-NPO
DELTA RNO-NPO
4.4 Events Synthesis

NPO GSM Operation
12
z Overlay additional information on a report

z Same mechanism as "Events Detections"
z Choose "Display Event Synthesis" in the Execution Context
9159 NPO

77
DELTA RNO-NPO
DELTA RNO-NPO
Exercise 1/2
NPO GSM Operation
12
PARAMETERS & PROPAGATION
Extract a report containing all parameters related to cell reselection,

for all cells of a BSC, for yesterday
z
Use the legend to compare operationnal settings with reference settings

}
Answer :
Select and propagate cells with discrepancies

}
Is there a discrepancy ?
How many cells ?
Answer :
Select and propagate parameters with discrepancies

}
How many parameters ?
Answer :
20 minutes
9159 NPO

78
DELTA RNO-NPO
DELTA RNO-NPO
Exercise 2/2
NPO GSM Operation
12
79
z Check all changes on all cells of a BSC
Period : last 30 days

z Was there any change ?
z
Answer :
z Check the details for one event
What exactly was changed ?

z What was the initial value ?
z What is the changed value ?
z
Answer :
Answer :
Answer :
z Check that all "cell reselection" parameters follow the reference values
Legend with source = operationnal, target = reference

Select all "red" cells
z Propagate the selected cells
z How many cells ?
Answer :
z
z
9159 NPO

4.5 Define Reference Settings
DELTA RNO-NPO
DELTA RNO-NPO
NPO GSM Operation
12
80
z In order to compare operationnal settings with your own reference
settings
z Preparatory steps :
Define reference settings per cell type, per frequency band, per cell class,
etc.
z Assign cell classes
z
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)
9159 NPO
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

NPO GSM Operation
12
z With NPO Analysis Desktop interface

z
Several cells can be changed at once
9159 NPO
DELTA RNO-NPO
DELTA RNO-NPO

81
4.6 Assign Classes to Cells [cont.]

NPO GSM Operation
12
z With a planning project import
Along with geo-data, cell class can be defined by RNP

z Refer to chapter "Import a Cartography Project"
z
9159 NPO
DELTA RNO-NPO
DELTA RNO-NPO

82
4.6 Assign Classes to Cells [cont.]

NPO GSM Operation
DELTA RNO-NPO
DELTA RNO-NPO
12
z How to create a new class ?

z
In menu bar, choose "Topology > Network Object Class"
3
2
9159 NPO
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

83
4.7 Customize Reference Dictionnary
DELTA RNO-NPO
DELTA RNO-NPO
NPO GSM Operation
12
z In order to compare operationnal settings with your own reference
settings
z All references are contained in the Reference Dictionary

z Create an Excel file :
One sheet contains references for one object type

z References for one object type can be split over several sheets
z The file is mono-release
z
Example of reference file : for release B10, one sheet

per family of parameters
9159 NPO
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.

84
4.7 Customize Reference Dictionnary [cont.]

NPO GSM Operation
12
z The first sheet must contain the file header :
z Next sheets can contain this simplified header :
9159 NPO
DELTA RNO-NPO
DELTA RNO-NPO
Description in NPO User Guide 12.1.3

85
DELTA RNO-NPO
DELTA RNO-NPO
NPO GSM Operation
12
86
z Columns header and contents, in each sheet :
Default values
Parameters names
9159 NPO
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.

DELTA RNO-NPO
DELTA RNO-NPO

NPO GSM Operation
12
Typical Process
Open NPO Import / Export Manager
2. Export the Parameter Reference Values for your release
3. Edit the file with Excel, include your references (then Save, Close)
4. Import the new Excel file thanks to the NPO Import / Export Manager
1.
NPO
NPO
Import
Import//Export
ExportManagement
Management
OPEN Imp/Exp Mng
EXPORT FILE
Data
DataWarehouse
Warehouse
9159 NPO
EDITION
IMPORT MODIFIED FILE

Admin
87
DELTA RNO-NPO
DELTA RNO-NPO
Exercise
NPO GSM Operation
12
z Change a reference and observe the changes
Export the GSM B10 Parameter Reference Values

z Modify CELL_RESELECT_OFFSET reference
z
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)

z Check properties of CELL_RESELECT_OFFSET
z
Do they follow your new values ?
Execute a tabular view for all cells, with the logical parameter
"CELL_RESELECT_OFFSET"
z Highlight the legend
z
Do you see the impact of changing the reference values ?
20 minutes
9159 NPO
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

88
4.8 Rules
NPO GSM Operation
12
89
z A rule is reflecting the dependency between 2 or more parameters

z For example :
z
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 16

}
This rule checks if the cell is having the right number of SDCCH channels according
to the number of TRXs.
z It is a quick check of all parameters of all NE's !
9159 NPO

4.8 Rules [cont.]

NPO GSM Operation
12
90
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"
9159 NPO
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.

DELTA RNO-NPO
DELTA RNO-NPO
4.8 Rules [cont.]

NPO GSM Operation
12
z To add or change a rule:
Same process as changing a reference value

z Export the Rules dictionary as an Excel file
z Modify/Add the expressions
z Import the modified Excel file
z
NPO
NPO
Import
Import//Export
ExportManagement
Management
OPEN Imp/Exp Mng
EXPORT FILE
Data
DataWarehouse
Warehouse
9159 NPO
EDITION
IMPORT MODIFIED FILE
Admin
Refer to NPO User Guide 13.1 for a full description of the file (file header, column header, content)

91
DELTA RNO-NPO
DELTA RNO-NPO
4.8 Rules [cont.]

NPO GSM Operation
12
92
File header : only one

per file, in the 1st sheet
Body for CELL2G
9159 NPO
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.

DELTA RNO-NPO
DELTA RNO-NPO
4.8 Rules [cont.]

NPO GSM Operation
12
93
This rule is checked on

concentric cells only
These rules are

checked for all cells
except class = indoor
9159 NPO
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
NPO GSM Operation
12
z Check all rules related to HO PWRCTRL DETECTION

z
Execute these rules for all cells in one BSC

Is there any rule which is red or orange ?
Select/Propagate only this rule
} Check its properties
Expression :
}
}
Execute this selected rule for all cells in the BSC

z Select all cells which are red or orange
z Propagate the selection
z
How many cells do not follow the rule ?
Answer :
Select all parameters linked to this rule

z Execute the selection of cells and parameters
z Compare their operationnal & reference values
z
Does it follow the reference ?
Answer :
5 minutes
9159 NPO
In order to add new rules, or change rules, kindly refer to User Guide 13.1

94
NPO GSM Operation
12
5 Parameters Tuning
9159 NPO

95
5 Parameters Tuning
5.1 Benefits
NPO GSM Operation
12
OMC-R is not the most efficient tool to perform massive

tuning operations on a network
z Only light features to ease cell tuning
z In case of BSC, TRX or Adjacency tuning, it can take days !
z OMC-R operators are not optimizers, they are prone to
misinterpret your changes
NPO Tuning Browser translates your parameters tuning

into a PRC
z No risk of misunderstanding between different teams
z Ultra-fast & ultra-simple procedure, for cell, BSC,
adjacencies, etc.
OMC-R operators are still in charge of activating the

PRC or not
9159 NPO

96
5 Parameters Tuning
DELTA RNO-NPO
DELTA RNO-NPO
5.2 Process
NPO GSM Operation
12
NPO tuning requires a strong methodology :

1. Create a new tuning session
z Modify parameters settings
z Export the session to the OMC-R (s)
@
@ NPO
NPO Analysis
Analysis Desktop
Desktop
2. Open NPO Tuning Browser

z Translate the session into a set of ACIE files
3. Create a PRC in RNUSM

z Populate the PRC with these ACIE files
z Activate the PRC
To create a tuning session :

Click on Tuning > Tuning Session
z Or "Ctrl + H"
z
A new window appears in the "Report Browser"
9159 NPO
The "report browser" becomes the "tuning browser"

@
@ OMC-R
OMC-R
97
5 Parameters Tuning
DELTA RNO-NPO
DELTA RNO-NPO
5.3 Interface
NPO GSM Operation
12
Tuning Operation
Tuning Session
9159 NPO
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.

98
5 Parameters Tuning
DELTA RNO-NPO
DELTA RNO-NPO
5.3 Interface [cont.]

NPO GSM Operation
12
Functions
Adjacency, Frequency or Advice tuning

Add/Remove Adjacency
Create External Cells
Modify Frequencies/BSIC
Write advices to OMC-R operator
Logical Parameters tuning
Modify parameters values for the current
NE
Design Parameters tuning
Modify design values for the current NE
9159 NPO
Note : MAFA frequencies tuning is not available in M2.

99
5 Parameters Tuning
DELTA RNO-NPO
DELTA RNO-NPO
5.3 Interface [cont.]

NPO GSM Operation
12
For each NE, select the forecast value
9159 NPO

100
DELTA RNO-NPO
DELTA RNO-NPO
How to Do It
NPO GSM Operation
12
101
Create a Parameter Tuning Operation

Select the appropriate NE's
Select appropriate parameters in the Tuning tab
3. Drag'n'Drop to the TS browser
1.
2.
The "parameter tuning" window appears

Select the appropriate forecast value for each couple NE parameter
2. Repeat until all forecast values are tuned
1.
9159 NPO
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
DELTA RNO-NPO
DELTA RNO-NPO
5.4 Reference cells

NPO GSM Operation
12
102
z 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".
9159 NPO
"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
DELTA RNO-NPO
DELTA RNO-NPO
5.5 Post-its
NPO GSM Operation
12
z For any reason, a NPO user can put a "post-it" on a cell

z Especially useful to warn other users:
New parameters are set on this cell

z A QoS problem is being currently troubleshooted on this cell, etc.
z
A post-it symbol appears next

to the cell
9159 NPO

103
DELTA RNO-NPO
DELTA RNO-NPO
How to Do It
NPO GSM Operation
12
104
Create a Adjacency Tuning Operation

Select "Adjacency Tuning" in the Tuning tab
1.
2.
The "relation tuning" window appears

1.
Select relations to add or remove
9159 NPO
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.

DELTA RNO-NPO
DELTA RNO-NPO
How to Do It
NPO GSM Operation
12
105
Create an External Cell

Select the adjacent NE's
Select "Adjacency Tuning" in the Tuning tab
1.
2.

1.
Select "New ECELL 2G" and fill up the information
9159 NPO
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.

DELTA RNO-NPO
DELTA RNO-NPO
How to Do It
NPO GSM Operation
12
106
Create a Frequency Tuning operation

Select "Frequency Tuning" in the Tuning tab
1.
2.

Double-click on Forecast to change the frequency of the TRX
2. Select the BSIC
1.
9159 NPO
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.
DELTA RNO-NPO
DELTA RNO-NPO
Exercise 1/2
NPO GSM Operation
12
107
z Create a new tuning session
For all cells with cong %(*) > 2%, enable FDR and fast
traffic handover.
z Starting from exercise p.71, tune all cells that do not
follow the new CRO reference.
z Set
z
L_RXLEV_CPT_HO(Umbrella 900, Mini 900) = -74dBm

L_RXLEV_CPT_HO(Umbrella 900, Mini 1800) = -72dBm
HO_MARGIN(1800,900) = 7dB
HO_MARGIN(900,1800) = 3dB
Find the cell with the highest amount of HO caused by

interferences, and modify its frequencies.
z Find the cell with the highest time advance average,
and add some neighbourhood relationships
z Write an advice : "This is a test tuning session"
z
15 minutes
9159 NPO
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)

DELTA RNO-NPO
DELTA RNO-NPO
Exercise 2/2
NPO GSM Operation
12
z Apply a tuning session
Export the previous session to the OMC-R

z If the OMC-R is available, perform all the steps until
activation of the PRC
z
z Notice how long it took to perform a massive
tuning
9159 NPO

108
NPO GSM Operation
12
9159 NPO

109
6.1 Overview
NPO GSM Operation
12
110
z There is two types of distribution "view" :

z
Vectors
PathBalance Distribution
60
100
90
50
80
70
40
60
50
30
% PB distrib
Nb PB Samples
40
20
30
20
10
10
0
0
[-110,-50[
[-50,-30[
[-30,-20[
[-20,-10[
[-10,0[
[0,10[
[10,20[
[20,30[
[30,50[
[50,110]
Path Balance ( dB )
Matrices
9159 NPO
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)


NPO GSM Operation
12
z The content of each report depends on the measurements

z But the "steps" can be changed !
Between -10dB and

+10dB, not enough
details
9159 NPO
Between 20dB and

50dB, too many
details

111

NPO GSM Operation
12
112
z 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
9159 NPO
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 !!

DELTA RNO-NPO
DELTA RNO-NPO
6.2 Method
NPO GSM Operation
12
z In NPO Administration Data Management

z
Configuration > Manage RMS (or GPRS) templates
Edit the steps'

thresholds manually,
or by following an
interpolation method
9159 NPO

113
DELTA RNO-NPO
DELTA RNO-NPO
6.2 Method [cont.]

NPO GSM Operation
12
Export the template to the OMC-R

A file is export to the OMC-R, using the same format as a tuning session.
Go to the OMC-R and follow this method :

Export the RMS template using the NPO Tuning Browser
Create a PRC in RNUSM
3. Populate your PRC with your imported file
4. Activate your PRC
1.
2.
After activation, the new template is available in each BSC

z You still need to apply this template on the cells
z
Create a new PRC

2. Populate it with these cells
3. "Edit n cells" and choose the new template
4. Activate the PRC
1.
Now the new template will be used by the cell for the next RMS
campaign !
9159 NPO

114
DELTA RNO-NPO
DELTA RNO-NPO
Exercise
NPO GSM Operation
12
z Group per group, you will perform the update of
the path balance template, accordingly to the

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

z Activation is possible, if wanted.
15 minutes
9159 NPO

115
NPO GSM Operation
12
9159 NPO

116
7.1 Overview
NPO GSM Operation
12
117
z Highly valuable information can be displayed in the cartography module
z Offers new ways to investigate a problem
Interferences (co-channels, adjacent channels)

z Missing adjacencies
z Hot-spot locations
z Traffic & QoS distribution over time
z
9159 NPO

7.2 Project Structure

NPO GSM Operation
12
118
z A project is composed of
z
Planned Data
Text files containing the list of cells and all related information for
plotting them on a georeferenced map (coordinates, azimuth)
= COF FILES
Background Maps
Maps 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.
9159 NPO

7.3 COF files

NPO GSM Operation
12
119
z 3 mandatory files
CEL.COF : Description of the cell (CGI, coordinates, azimuth, omni/sector)

z FRQ.COF : Description of the TRXs
z ADJ.COF : Description of the Adjacencies
z
z Minimal amount of data is required to plot the cells

z All other information are optional
9159 NPO
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.

DELTA RNO-NPO
DELTA RNO-NPO
7.3 COF files [cont.]

NPO GSM Operation
12
z CSV format : each data is separated by a semi-colon
Windows > Configuration Panel > Regional Settings

z Choose "Customize"
z Set the "List Separator" as ; (semi-colon)
z
When saving a file as "CSV" with Excel, the files will be in the correct
format
z Each file starts with 2 identical lines :
Line 1 : GENERIC;B10;<project name>;<project version>;<date>;<creator>

Line 2 : L
For instance :
GENERIC;B10;ALCATEL_NETWORK;AUGUST_2007; 01/08/07;ALUL
L
9159 NPO

120

NPO GSM Operation
12
121
CEL.COF
Line 3 : column headers
z Line 4 n : 1 line per cell
z
Most useful headers :
1.
READ_ONLY
EXTERNAL
RNP_CELL_ID
CI
LAC
FREQUENCY_RANGE
MNC
MCC
CELL_CLASS
CELL_TYPE
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
9159 NPO
TRX_NUMBER
BCCH
HOPPING_MODE
X_SITE_LOC
Y_SITE_LOC
ANTENNA_ORIENTATION
ANTENNA_TYPE (not mandatory)
ANTENNA_HEIGHT (not mandatory)
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)


NPO GSM Operation
12
122
FRQ.COF
z Line 4 n : 1 line per TRX (depends on TRX_NUMBER defined in
CEL.COF)
z
Mandatory headers :
1.
RNP_CELL_ID
TRX_INDEX
ARFCN
ZONE_TYPE
BCCH_FLAG
PREFERENCE_MARK
2.
3.
4.
5.
6.
9159 NPO
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


NPO GSM Operation
12
123
ADJ.COF
z Line 4 n : 1 line per adjacency (it can be empty)
z
Mandatory headers :
1.
RNP_CELL_ID
NC_RNP_CELL_ID
HO_MARGIN
LINK_FACTOR
HO_MARGIN_LEV
HO_MARGIN_QUAL
HO_MARGIN_DIST
PRIORITY
2.
3.
4.
5.
6.
7.
8.
NEIGHBOUR_RXLEV
10. EN_TRAFFIC_HO
11. L_RXLEV_CPT_HO
12. OUTDOOR_UMB_LEV
9.
9159 NPO
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


NPO GSM Operation
12
124
z Create these files using EXCEL, and "Save As " CSV format
z Open the 3 files with NOTEPAD and remove the final semi-colons of line
1 and line 2
9159 NPO
After this step, your cells are ready to be imported !

7.4 Format of background map

NPO GSM Operation
12
Two supported format :

z
Vector files : Mapinfo Interchange Format (MIF + MID)

}
}
From A9155 RNP V6

From MapInfo versions 300 or 450
Raster files : an image (PNG, BMP, JPG, TIF, TIFF)

+ its georeference ASCII file (RAST)
Created manually
The ASCII file contains a list of points that allows to
georeference the map
} Only UTM wgs84 or a Long/Lat wgs84 coordinates are
supported
}
}
9159 NPO
DELTA RNO-NPO
DELTA RNO-NPO
Example of a MIF V450 vector file:

RAST file for LONG/LAT WGS84 :
VERSION 450
!table
Charset "WindowsLatin1"
!version 300
Delimiter ","
!charset WindowsLatin1
CoordSys Earth Projection 1,104 Bounds (94,95) (-1,0)
Definition Table
COLUMNS 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, 104
94.561412 -0.156046
Units "degree"
94.558724 -0.156045
Region 1
15
94.561412 -0.156046
94.561412 -0.155144
RAST file for UTM WGS84 :
!table
!version 300
!charset WindowsLatin1
Definition Table
File "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, 0
Units "m"
125
DELTA RNO-NPO
DELTA RNO-NPO
7.5 Import
NPO GSM Operation
12
Background file
1.
2.
3.
4.
5.
6.
7.
Open the Import/Export Management

Select Import > Raster File or Vector
File
Choose the layer name
Choose layer type = Background
Select the file
Click "OK"
Select the georeference file (for
Raster file only)
9159 NPO

126
DELTA RNO-NPO
DELTA RNO-NPO
7.5 Import [cont.]

NPO GSM Operation
12
Planned Data
1.
2.
3.
4.
5.
Open the Import/Export

Management
Select Import > Planned Data
Select the appropriate format
(GENERIC)
Select the 3 COF files for import
Choose DELTA or NON DELTA
z
6.
DELTA : the objects in the import files

are imported, other existing objects
are not changed
NON DELTA : the objects not present
in the import files are deleted
Click "OK"
9159 NPO

127
7.6 Configuration files

NPO GSM Operation
12
z On the client, connect to the server
9159 NPO

128
7.6 Configuration files [cont.]

NPO GSM Operation
12
z The important files :

z
For changing cells layout (editable) :
/alcatel/muse/technologies/GSM/cartography/config/
CartographyConfiguration.xml
For information (do not edit !) :
/alcatel/muse/technologies/GSM/plannedData/specificloader/config
fileNameObjectTypeMapping.cfg
9159 NPO

129
NPO GSM Operation
12
9159 NPO

130
8.1 Presentation
NPO GSM Operation
12
z Two main modules in NPO offer enhanced analysis support :
Cartography
z Diagnosis
z
z Cartography
Interference
z QoS mapping and distribution (thematic layers)
z Adjacencies management
z Layer management
z
z Diagnosis
Automatic investigation of poor QoS

z Based on standard scenarios and operator-customized scenarions
z
9159 NPO

131
DELTA RNO-NPO
DELTA RNO-NPO
8.2 Cartography pane

NPO GSM Operation
z Activation
12
2
Select all the cells
9159 NPO

132
8.2 Cartography pane [cont.]
DELTA RNO-NPO
DELTA RNO-NPO
NPO GSM Operation
12
z Description
Viewport
Toolbar
Mini Map
Layer
Management
Information
Bar
9159 NPO

133
DELTA RNO-NPO
DELTA RNO-NPO

NPO GSM Operation
12
134
z Layer Density : displayed information vs. zoom
9159 NPO
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 !)

DELTA RNO-NPO
DELTA RNO-NPO

NPO GSM Operation
12
135
z Cell Icons :
Collapsed cell
9159 NPO
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.

DELTA RNO-NPO
DELTA RNO-NPO

NPO GSM Operation
12
z Other icons :
Sector 1
Micro cell in sector 1
(to display the technology standard (G)

G cf
User Preferences)
Concentric cell in sector 1
Sector 2
Layer density = 7
9159 NPO

136
DELTA RNO-NPO
DELTA RNO-NPO

NPO GSM Operation
12
z Toolbar
Navigation
Mini map display
Adjacency wizard
Ruler
Selection
Viewport Mngt
Zoom in/out
Center on selection
z Information bar
Coordinates of the cursor
9159 NPO
Distance
(ruler tool)

Scale of
viewport
137
DELTA RNO-NPO
DELTA RNO-NPO
8.3 Cartography functions

NPO GSM Operation
12
z In the viewport, the contextual menu offers major functions :

z
Right-click on the background map

The contextual menu recaps toolbar functions
Left-click (= select) and Righ-click on a cell

New functions available !
Basic Functions
Open cell properties
Show adjacencies
Show co-sector cells
Propagate selection towards the
Network elements pane
Remove cell from viewport

9159 NPO

138
DELTA RNO-NPO
DELTA RNO-NPO
8.3 Cartography functions [cont.]

NPO GSM Operation
12
z Highlight :
z
All Parents / Children Objects

BSC
ch
ild
re
ns
nt
a re
s
BTS
Cell 2
Cell 1
TrafZ outer
TrafZ inner
TrafZ outer
TrafZ inner
TRX 1 TRX 2
TRX 3
TRX 1 TRX 2
TRX 3 TRX 4
9159 NPO
TrafZ = traffic zone (subset of TRX that belong to same BTS, same frequency band and same zone)

139

NPO GSM Operation
12
z Highlight
z
All incoming / All Outgoing /All Adjacencies

Outgoing adjacency towards the
other co-sector cell
Outgoing adjacency towards 2

co-sector cells
9159 NPO
DELTA RNO-NPO
DELTA RNO-NPO

140

NPO GSM Operation
12
141
z Highlight
z
Interfering / Interfered
Interference
Matrix
NPO
Import/Export Mngt
CARTOGRAPHY
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;
9159 NPO
The only use of the interference matrix in NPO

Import 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)


NPO GSM Operation
12
142
z Highlight
z
Frequency Reuse Checking
Checking radius (in meters)
Selected cell
One of the cell within the radius

that is using the same frequency as
the selected cell
9159 NPO
The current exemple shows that many surrounding cells are using the same frequencies. It might be a case of SFH
1x1.


NPO GSM Operation
12
143
z Highlight
z
CCA (Cell Contour Area, also known as "Best Server Area")
NPO computes Voronoi areas

between cells of same type
9159 NPO
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/

DELTA RNO-NPO
DELTA RNO-NPO
8.4 Cartography & Tuning Session

NPO GSM Operation
12
144
z Adjacency Wizard
Added relation
Removed relation
Untouched relation
Adjacencies with no usage or low usage

(based on the type 180) will be
removed
9159 NPO
If a Tuning Session is opened,

possibility to copy the wizard's result
as a tuning operation
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.xml
lowTrafficThreshold="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.]
DELTA RNO-NPO
DELTA RNO-NPO
NPO GSM Operation
12
145
z Field Trial Zone
Select only certain NEs, based on their parameters

Propagate the selected objects
2
9159 NPO
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.

DELTA RNO-NPO
DELTA RNO-NPO
8.5 Thematic Layers

NPO GSM Operation
12
146
z Objects in the map will be displayed differently, depending on
customized criteria.
z Example :
z
Thematic layer based on parameter "FREQUENCY BAND"

Thematic Layer Editor
9159 NPO
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.

DELTA RNO-NPO
DELTA RNO-NPO
8.5 Thematic Layers [cont.]

NPO GSM Operation
12
147
z Multiple criteria possible

Drag & drop a function here
Criteria can be applied on another object
Boundaries of
intervals
(static or
dynamic)
Intervals
distribution
method
Will define the background color for

each interval, from green to red
If static distribution :
define the min/max of each interval here
Double click in the cell to choose
graphical properties for this interval
9159 NPO
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

NPO GSM Operation
12
z Export a layer in KMZ format

z Open in Google Earth
9159 NPO
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.

148
DELTA RNO-NPO
DELTA RNO-NPO
Exercise
NPO GSM Operation
12
z Using the cartography,

z
Select all cells with

FREQ RANGE = GSM900
AND CELL CLASS = URBAN
} AND 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 on

RTCH_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
9159 NPO

149
8.6 Diagnosis
NPO GSM Operation
12
150
z A diagnosis is a suite of tests, based on parameters and indicators :
TCH congestion
above threshold ?
NO
No diagnosis
YES
RTCH always busy

?
YES
TRX frozen ?
YES
RTCH 100% busy
YES
TRX w/ no traffic
YES
Loss of TCH
ressources ?
YES
Too much TCH

traffic ?
Cant't check
YES
FDR acticated ?
YES
Queue is full ?
YES
Wrong
BTS_Q_LENGTH ?
Queue expires ?
YES
Wrong TQHO ?
Bad queue
settings ?
YES
YES
YES
9159 NPO
Wrong T11 ?
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

DELTA RNO-NPO
DELTA RNO-NPO
8.6 Diagnosis [cont.]

NPO GSM Operation
12
151
z Activation
z
Synthetic Mode
Drag and drop NE + Diagnosis in the Spreadsheet browser
Or
} From the menu bar "Diagnosis > Execute Diagnosis"
}
Detailed Mode
Drag and drop NE + Diagnosis in the Report browser
OR
} Right-Click on the value of a "
" indicator that exceeds the red threshold, choose
"Execute Diagnosis"
}
Synthetic Result
Detailed Result
9159 NPO


NPO GSM Operation
12
152
z Different diagnosis
V3_CDR : version 3 of "call drop rate" diagnosis

z V4_CDR : version 4 of "call drop rate" diagnosis
z V4_CDR_180 : already included in V4_CDR
z V4_CDR_TRX : includes V4_CDR + 3 additional tests per TRX
z
z Check the properties of diagnosis V2_SDR :
9159 NPO
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


NPO GSM Operation
12
153
z Detailed Output
Each node is detailed, with a

description of the test and the
value of the QoS Indicator
9159 NPO

DELTA RNO-NPO
DELTA RNO-NPO
Exercise
NPO GSM Operation
12
z Create a favorite with all

z
z
z
z
QoS Indicators located
in the family "QoS > Main"

Execute this tabular view for yesterday
"Highlight" the view
Execute a diagnosis on one of the "red" value
Verify one of the results of the diagnosis
10 minutes
9159 NPO

154
NPO GSM Operation
12
9159 NPO

155
9.1 Schedule
NPO GSM Operation
z
z
z
z
z
z
z
12
Monitoring
Check log files of indicators and
parameters import
Generate a "WORST 20" warning
report on KPI's
Generate a daily report of the
network (or weekly, on Monday)
Generate a detailed spreadsheet
report for all cells
Check reliability of the problems
Dispatch worst cells to relevant
teams
Update monitoring database
9159 NPO
z
z
z
z
z
z
z
156
Optimization
Tackle worst cells one by one
Check RMS & detailed indicators
Check interference and
frequencies reuse
Check adjacencies definition
Find the cause of the problem
Propose corrective action
Update 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

NPO GSM Operation
12
z Each type of problem should be solved by one specific team

z Find the few KPIs that define a team :
Call drop due to remote transcoder %
Deployment/planning team
Call drop due to internal BSS %

TCH Congestion % & High traffic
Frequency planning team
TCH Congestion % & Low traffic

HO Quality % or HO Intf % & CDR radio on
all TRXs
OMC-R team
RMS DL RxLev avg < -85dBm & poor CDR

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

& poor CSSR & path balance [-6;+8]
Optimization team
Too many HO from lower to upper layer
9159 NPO

157
9.3 Interaction with other teams

NPO GSM Operation
12
158
z From A9155 Radio Network Planning tool :
Extract maps in MIF format

z Extract CCA in MIF format
z Use satellite orthoimage
z Import
z
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
NPO
RNP
9159 NPO
Beside previous slide, supplementary information should flow between optimization team and other teams.

9.3 Interaction with other teams [cont.]

NPO GSM Operation
12
z To A9155 Radio Network Planning tool :

z
Update cells database with

Operational
Operational
} Operational
} Operational
}
}
frequencies
adjacencies
capacities
cell layer / type
Import additional data

}
}
Traffic in Erl, HO interf%, HO Quality%, HO/call, etc.

Experience Matrix (overlap measured with RMS)
Live config, QoS,

RMS, experience
matrix
NPO
RNP
9159 NPO

159
9.3 Interaction with other teams [cont.]

NPO GSM Operation
12
z To Dimensioning teams :
Provide traffic information

z Provide operational configuration
z
z From Design teams :
Collect the parameters templates, for each type/class of cell

z Or, rather, their NPO reference dictionnary
z
z To Design teams :
Provide operational parameters for all cells

z Provide QoS reports related to new settings
z Cells with optimized/different settings than their references
z
9159 NPO

160
Exercise
NPO GSM Operation
12
z Dimensioning team needs to verify the current load
of BSCs.
z Generate a report, including all BSCs, with :
z
z
z
z
z
z
SDCCH Erlang at BH
TCH Erlang FR at BH
TCH Erlang HR at BH
Number of TRX per BSC
Number of cell per BSC
Max congestion on Ater PS interface, for each GPU
15 minutes
9159 NPO

161
9.4 Scheduled Reports
DELTA RNO-NPO
DELTA RNO-NPO
NPO GSM Operation
12
z To gain time, Warning reports & Diagnosis can be automatically
generated by NPO :
Execution Context window
9159 NPO

162
DELTA RNO-NPO
DELTA RNO-NPO
9.4 Scheduled Reports [cont.]

NPO GSM Operation
12
163
Job title can be edited
Output format : in the

browser, or as an output file
Date at which the report will
be available
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.
9159 NPO


NPO GSM Operation
DELTA RNO-NPO
DELTA RNO-NPO
12
164
The report can be generated

periodically
Date at which the reports

will stop being created
9159 NPO


NPO GSM Operation
DELTA RNO-NPO
DELTA RNO-NPO
12
165
To view a scheduled report, 2 possibilities :

From the Analysis Desktop : Report > Display pending executed reports
2. From the NPO Administration :
Data Management > Administration > Manage Jobs Results
1.
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 browser
z Else, the report will be saved and opened with an exeternal application
(Excel, Acrobat Reader, etc.)
z
9159 NPO


NPO GSM Operation
12
z With NPO Analysis Desktop
9159 NPO
DELTA RNO-NPO
DELTA RNO-NPO

166

NPO GSM Operation
12
z With NPO Administration :
9159 NPO
DELTA RNO-NPO
DELTA RNO-NPO

167

NPO GSM Operation
DELTA RNO-NPO
DELTA RNO-NPO
12
168
z To delete an existing job, go to NPO Administration > Data Management
9159 NPO

NPO GSM Operation
12
9159 NPO

169
DELTA RNO-NPO
DELTA RNO-NPO
10.1 Classification
NPO GSM Operation
12
z Classification of objects and functions can be modified
Topology Classification
9159 NPO

170
DELTA RNO-NPO
DELTA RNO-NPO
10.1 Classification [cont.]

NPO GSM Operation
12
171
z Choose Topology > Topology Classification (Ctrl + T)

z Design your new classification : Cells classified per number of TRX
9159 NPO
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"

DELTA RNO-NPO
DELTA RNO-NPO

NPO GSM Operation
12
172
z Choose Data > Function Classification (Ctrl + U)

z Design your new classification : Logical parameters per Unit
9159 NPO
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"


NPO GSM Operation
12
z For better display, change the order of the tabs :
Display/Remove the
classification from the tabs
9159 NPO
DELTA RNO-NPO
DELTA RNO-NPO

173
DELTA RNO-NPO
DELTA RNO-NPO
Exercise
NPO GSM Operation
12
z Create a topology classification based on the free
fields "PROVINCE" and "CITY" (CITY is under

PROVINCE)
5 minutes
9159 NPO

174
DELTA RNO-NPO
DELTA RNO-NPO
10.2 User Preferences

NPO GSM Operation
12
175
z 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)
YES : soft deleted objects remain visible in
Analysis Desktop, with icon
Change font in the whole application
9159 NPO
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).

DELTA RNO-NPO
DELTA RNO-NPO
10.2 User Preferences [cont.]

NPO GSM Operation
12
176
When editing a view/report, open a new window

Allow interpolation while executing a view/report
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.)
9159 NPO

DELTA RNO-NPO
DELTA RNO-NPO

NPO GSM Operation
12
177
"Highlight" function activated by default when

executing a tabular view
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)
Quick Diag results in "verbose" or "icon" format
Keep these keys pressed to update an executed view
with new elements or functions.
In View editor, default graph type chosen.
An empty indicator value in a view is replaced by?
Data that will be available in a tabular view
9159 NPO

DELTA RNO-NPO
DELTA RNO-NPO

NPO GSM Operation
12
Zoom "step size"

Default colour for adjacencies
Default colour for selection
Default colour for highlighting
Consecutive highlights will append to previous
highlights
Choose operationnal or planned geo-data
(coordinates of cells from OMC-R or RNP files ?)
Display the symbol of each cell's standard on the
cartography
Factor applied on the radius if it is based on the
U_TIMEADVANCE (wizard adjacency)
9159 NPO

178
DELTA RNO-NPO
DELTA RNO-NPO
10.3 Customer Topology Objects

NPO GSM Operation
12
179
z NPO allows to create new network equipments or new relations
between equipments
z
Mostly defined by their parents/children relations
z This customized objects will be treated like the other network objects :
Available in Analysis Desktop

z Consolidations will be performed at their level
re
nt
New Relation
pa
GERAN
New Object
MSC B
ch
ild
re
n
MSC A
New Relation
BSC 1
9159 NPO
BSC 2
BSC 3
BSC 4
Usually, each new object should be associated with 2 new relations : object parent & object children

10.3 Customer Topology Objects [cont.]
DELTA RNO-NPO
DELTA RNO-NPO
NPO GSM Operation
12
There are two steps to define a new objects

Create the object type (e.g. type "MSC")
2. Define a new object (e.g. "MSC 1", "MSC 2")
1.
Both steps use a similar method :

Create or modify the related text file
2. Import the text file with NPO Import/Export Management
1.
Before importing an object, verify the object type is already

defined in NPO.
If the type doesn't exist, create it first.
9159 NPO

180
DELTA RNO-NPO
DELTA RNO-NPO

NPO GSM Operation
12
181
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 :
z
0 MSC
MSC_ID
GSM
GERAN
X_Coord
1 MSC_BSC
MSC_ID/BSC_ID
GSM
MSC
BSC
G
string
H
Y_Coord
I
string
Cf. Description in the comments of this slide
9159 NPO
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)

DELTA RNO-NPO
DELTA RNO-NPO

NPO GSM Operation
12
182
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 :
z
MSC
MSC 1
GERAN
X_coord W 03 59 31 Y_coord N 05 18 08
MSC
MSC 2
GERAN
X_coord W 03 57 26 Y_coord N 05 01 46
MSC_BSC 1/VNR_BSC1
MSC 1 - BSC VNR1
MSC
BSC
VNR_BSC1
MSC_BSC 1/VNR_BSC2
MSC 2 - BSC VNR2
MSC
BSC
VNR_BSC2
Cf. Description in the comments of this slide
9159 NPO
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)

DELTA RNO-NPO
DELTA RNO-NPO
NPO GSM Operation
12
z 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/"
z Open Import/Export Management > Import > Customer Objects Type
z
9159 NPO

183

NPO GSM Operation
DELTA RNO-NPO
DELTA RNO-NPO
12
z 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/"
z Open Import/Export Management > Import > Customer Topology Objects
z
9159 NPO

184
DELTA RNO-NPO
DELTA RNO-NPO
Exercise
NPO GSM Operation
12
It is highly intereting to create Abis links between

BSC-BTS and BTS-BTS :
Possibility to detect problems on chained BTS due to
faulty Abis
z Possibility to keep track of network architecture in
NPO
z
1. Create a new relationship type : ABIS

2. 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
9159 NPO

185

NPO GSM Operation
12

for this module
9159 NPO

186
NPO GSM Operation
12
11 Annex
9159 NPO

187
11 Annex
11.1 Indicator Editor

NPO GSM Operation
9159 NPO
12
188
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.]

NPO GSM Operation
12
Temporal Aggregations :
9159 NPO
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)

189
11 Annex
11.1 Indicator Editor [cont.]

NPO GSM Operation
12
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 the
spatial level defined by the ObjectType.
9159 NPO

190
NPO GSM Operation
12
End of Module
Operation
9159 NPO

191
Section 1
NPO GSM
Module 3
Administration


Blank Page
NPO GSM Administration
13
9159 NPO
Document History
Edition
Date
Author
Remarks
01
YYYY-MM-DD
First edition

Objectives
9159 NPO
13

Objectives [cont.]
9159 NPO
13

Table of Contents
13
Page

1 Data Loading
1.2 QoS Data
1.3 Consolidations
1.4 System Scheduling
1.5 Time Zone
1.6 Import Checking
2 Data Management
2.1 Overview
2.2 Configuration
2.3 Administration
3 Import / Export Management
3.1 Overview
4 Recovery Tasks
4.1 Presentation
4.1 Scenario A
4.2 Scenario B
4.2 Scenario C
4.3 Scenario D
9159 NPO
7
8
11
12
14
15
16
19
20
21
22
23
24
27
28
29
30
32
35


13
9159 NPO

13
1 Data Loading
9159 NPO

1 Data Loading
DELTA RNO-NPO
DELTA RNO-NPO

13
z Radio Parameters files imported from OMC-R

z
Last import saved in /alcatel/DATA_SOURCE/OMC1/ACIE
OMC-R
NPO SERVER
CRONTAB :
Directory : /alcatel/omc3/omc3rno/script/
Script : run_periodicExport all
/alcatel/var/share/AFTR/ACIE
/alcatel/var/share/AFTR/ACIE
/ACIE_NlExport_Dir1
/ACIE_NlExport_Dir1
LOADER :
Directory : /alcatel/muse/MUSE_PARAM/loader/bin/
Script : run_gl.sh
Using 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.sh
Based on :
Directory : /alcatel/muse/MUSE_ADMIN/config/
File : paramStorageDuration.cfg
DICTIONARY
/alcatel/muse/technologies/GSM/Parameter/specificloader/dictionary/
MSNPO_GSM_RP_M2S2.xml
9159 NPO
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 Source
Choose 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.]
DELTA RNO-NPO
DELTA RNO-NPO
13
z Before performing a Tuning Session, check the parameters values in
NPO are up to date

z Trace files are located in :
\alcatel\muse\data\trace
z Check successful parameter import in the file :
15/08/2007
14/08/2007
RTP_Loader_0.traces
9159 NPO
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
DELTA RNO-NPO
DELTA RNO-NPO
1.1 Radio Parameters [cont.]

13
10
z After a tuning session or an update of planning data, it is necessary to
wait for the next scheduled parameter import.
z 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
9159 NPO
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.
z The RNUSM: Export Operation window opens.
2. Select the required directory.
z To perform an export, the directory status must be Idle.
z 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
Ready
[Export].
[Free], and then [Export].
Export progress is displayed in the Follow-up window.

3. Click on [Close].
z

1 Data Loading
DELTA RNO-NPO
DELTA RNO-NPO
1.2 QoS Data

13
11
z QoS data files imported from OMC-R

z
Last imports saved in /alcatel/DATA_SOURCE/OMC1/APME
OMC-R
Regularly (1hr or less)

PM files are retrieved from BSS & MFS
/alcatel/var/share/AFTR/APME
/alcatel/var/share/AFTR/APME
NPO SERVER
LOADER :
/alcatel/muse/MUSE_QOS/loader/genericloader/scripts/
run_gl.sh
Using the plug-in :
/alcatel/muse/MUSE_QOS/loader/genericloader/lib
genericloader.jar
CONSOLIDATION & PURGE :
/alcatel/muse/MUSE_QOS/consolidation/bin/
consolidation.sh
Based on :
/alcatel/muse/MUSE_COMMON/config/
StorageDuration.csv
DICTIONARY
\alcatel\muse\technologies\GSM\QoS\dictionary/
QID.xml, B10_QCD.xml, QRD.xml
9159 NPO
TRACE
Data Management > Administration > Import Follow-up
Scheduler : the time of NPO import is defined in NPO Administration / Data Management / Configuration > System Scheduling
Dictionaries :
QID : indicators
QCD : counters
QRD : 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:
z 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:
z /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
DELTA RNO-NPO
DELTA RNO-NPO
1.3 Consolidations
13
12
z The indicators are consolidated automatically, temporaly and spatialy

z Temporal Consolidation can be customized :
z
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
-
9159 NPO
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.]

DELTA RNO-NPO
DELTA RNO-NPO
13
z 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=9
RELEVANT_HOUR_ENDS_ON=19
- Save
-
9159 NPO

13
1 Data Loading
1.4 System Scheduling
DELTA RNO-NPO
DELTA RNO-NPO
13
z Check the timing of consolidation, job computation, and import
parameter activities :
9159 NPO
It is also possible to disable / enable a job, but this is NOT recommended ! All jobs should be available.

14
1 Data Loading
DELTA RNO-NPO
DELTA RNO-NPO
1.5 Time Zone

13
z It is mandatory to select the same time zone between NPO Server and
the different Data Sources
9159 NPO

15
1 Data Loading
B10
B10
MR2
MR2
1.6 Import Checking

13
16
z QoS Import
Root Loading Object = BSC in GSM (entity that generates the PM files)
z Datasource = OMCR in GSM
z File type : 1 file per counter type (PM110, PM180, PM31,)
z
9159 NPO
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.]

13
z Parameters Import
CSV : set of ACIE files (12)

z RTP :
z
9159 NPO
B10
B10
MR2
MR2

17
1 Data Loading
B10
B10
MR2
MR2
1.6 Import Checking [cont.]

13
18
z QoS Consolidation
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
9159 NPO
Recovered Data : data that was recovered in the OMCR but after the consolidation was done.

13
2 Data Management
9159 NPO

19
2 Data Management
DELTA RNO-NPO
DELTA RNO-NPO
2.1 Overview
13
20
z Most functions have already been explained. This chapter will recap all
of them.
9159 NPO

2 Data Management
DELTA RNO-NPO
DELTA RNO-NPO
2.2 Configuration
13
Enable/Disable an import job

Modify inputs to detect unavailability
Modify working hours definition
Edit a RMS or GPRS template
Add / Edit a data source (storage
duration, login/password/IP, paths,
etc.)
9159 NPO

21
2 Data Management
DELTA RNO-NPO
DELTA RNO-NPO
2.3 Administration
13
22
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 data (for any date) (*)
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

9159 NPO

13
9159 NPO

23
DELTA RNO-NPO
DELTA RNO-NPO
3.1 Overview
13
24
z Import/Export Management allows the user to import, export and
delete various types of data :

z
z
z
z
z
z
Dictionaries
RMS / GPRS templates
Raster / Vector files (RNP)
Planned data (RNP)
Customer Topology Objects
Free Fields
z Export : for backup or import in another NPO server

z Import : update current NPO with dictionary from another NPO, or with
a new dictionary from Alcatel-Lucent (recommended for administrator

or root user only)
9159 NPO

DELTA RNO-NPO
DELTA RNO-NPO

9159 NPO
13
Refer to NPO Administation Guide for specific explanation on each function.

25
DELTA RNO-NPO
DELTA RNO-NPO
Exercise
13
26
z Export the Report dictionary

z Find one of the reports you created earlier
z Imports have been done earlier
Free fields
z Planned data, etc.
z
z Do you remember the process ?
10 minutes
9159 NPO
It is redundant to perform a import again : the most important imports have been done in the previous chapters
already.

13
4 Recovery Tasks
9159 NPO

27
4 Recovery Tasks
DELTA RNO-NPO
DELTA RNO-NPO
4.1 Presentation
13
z QoS Data were not retrieved by NPO :
Due to OMC-NPO link unavailability

z Due to BSC/MFS-OMC link unavailbility, etc.
z
z Several scenarios have to be considered
Scenario A : short outage (< 24 hours)

z Scenario B : short outage at bad time (< 24 hours)
z Scenario C : long outage (< 5 days)
z Scenario D : very long outage (> 5 days)
z
z Only scenario D requires a back-up recovery procedure
9159 NPO

28
4 Recovery Tasks
DELTA RNO-NPO
DELTA RNO-NPO
4.1 Scenario A
13
z Outage and resume before the consolidation time
No PM Files received
time
09:00
12:00
15:00
18:00
21:00
00:00
03:00
06:00
09:00
12:00
06:00
09:00
12:00
Consolidation
scheduled time
= 1:00am
Files automatically
retrieved
time
09:00
12:00
15:00
18:00
21:00
00:00
03:00
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
9159 NPO

29
4 Recovery Tasks
DELTA RNO-NPO
DELTA RNO-NPO
4.2 Scenario B
13
z Outage before the consolidation time, and resume after.
time
09:00
12:00
15:00
18:00
21:00
00:00
03:00
06:00
09:00
12:00
06:00
09:00
12:00
Consolidation
scheduled time
= 1:00am
Files automatically
retrieved
time
09:00
12:00
15:00
18:00
21:00
00:00
03:00
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)
9159 NPO

30
4 Recovery Tasks
4.2 Scenario B [cont.]

DELTA RNO-NPO
DELTA RNO-NPO
13
31
z 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.
9159 NPO
"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
DELTA RNO-NPO
DELTA RNO-NPO
4.2 Scenario C
13
z Outage for many days, but less than 5 days (120 hours).
time
18:00
21:00
00:00
03:00
06:00
09:00
12:00
Consolidation
scheduled time
= 1:00am
Files automatically
retrieved
time
10:00
Day 1
18:00
21:00
00:00
03:00
06:00
09:00
12:00
Day 6
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
9159 NPO

32
4 Recovery Tasks
DELTA RNO-NPO
DELTA RNO-NPO
4.2 Scenario C [cont.]

13
33
z During Day 6, launch the consolidation for Day 1, 2, 3, 4, 5.

z At Day 7, 1:00am, the consolidation of Day 6 is performed
automatically.
z 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.
Files automatically
retrieved
00:00
time
03:00
Day 6
06:00
09:00
12:00
Day 7
Consolidation of Day 6
scheduled time
= 1:00am
9159 NPO
In such cases, perform a manual consolidation of

Day 6 later, during Day 7.

4 Recovery Tasks
4.2 Scenario C [cont.]

13
z Manual Consolidation :
Choose the date of Day 6 (for

example)
Click on "start" to perform a
consolidation on the chosen date.
9159 NPO
DELTA RNO-NPO
DELTA RNO-NPO

34
4 Recovery Tasks
DELTA RNO-NPO
DELTA RNO-NPO
4.3 Scenario D
13
35
Outage for many days, more than 5 days.

z In such cases, the OMC-R does not have the data in memory anymore,
and data can be considered as lost.
z
Alternative solution :
Get a back-up from the OMC-R, no more than 5 days old
2. Extract the PM files between the start of the outage of the end of the
outage
3. Re-import the data in NPO
1.
Beware, even on a back-up, there are only 5 days of PM files !
9159 NPO
Re-importing PM files in NPO consists in loading the files in the ORACLE database, thanks to NPO loaders.


13

for this module
9159 NPO

36
13
End of Module
Administration
9159 NPO

37
DRAFT
@@SECTIONTITLE - @@MODULETITLE
@@SECTION - @@MODULE -
@@PRODUCT
@@COURSENAME
Copyright 2007 by Alcatel-Lucent - All rights reserved

Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel

RNO - NPA To NPO

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RNO - NPA To NPO

Uploaded by

Copyright:

Available Formats

9159 NPO

RNO-NPA B9 to NPO B10

9159 NPO - RNO-NPA B9 to NPO B10 Evolutions

Copyright 2007 by Alcatel-Lucent - All rights reserved

Switch to notes view!

All Rights Reserved 2007, Alcatel-Lucent

Switch to notes view!

All Rights Reserved Alcatel-Lucent 2007

All Rights Reserved 2007, Alcatel-Lucent

Table of Contents [cont.]

Switch to notes view!

All Rights Reserved Alcatel-Lucent 2007

This page is left blank intentionally

All Rights Reserved 2007, Alcatel-Lucent

Switch to notes view!

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 architecture

All Rights Reserved Alcatel-Lucent 2007

All Rights Reserved 2007, Alcatel-Lucent

Course Objectives [cont.]

Switch to notes view!

All Rights Reserved Alcatel-Lucent 2007

This page is left blank intentionally

All Rights Reserved 2007, Alcatel-Lucent

About this Student Guide

Conventions used in this guide

All Rights Reserved Alcatel-Lucent 2007

Where you can get further information

All Rights Reserved 2007, Alcatel-Lucent

About this Student Guide [cont.]

Switch to notes view!

All Rights Reserved Alcatel-Lucent 2007

This page is left blank intentionally

All Rights Reserved 2007, Alcatel-Lucent

Client (Company, Center) :

Surname, First name :

All Rights Reserved Alcatel-Lucent 2007

All Rights Reserved 2007, Alcatel-Lucent

Self-Assessment of Objectives [cont.]

Switch to notes view!

All Rights Reserved Alcatel-Lucent 2007

Thank you for your answers to this questionnaire

All Rights Reserved 2007, Alcatel-Lucent

Do not delete this graphic elements in here:

9159 NPO RNO-NPA B9 to NPO B10 Evolutions

All Rights Reserved 2007, Alcatel-Lucent

All Rights Reserved Alcatel-Lucent 2007

This page is left blank intentionally

Last name, first name

All Rights Reserved 2007, Alcatel-Lucent

All Rights Reserved Alcatel-Lucent 2007

All Rights Reserved 2007, Alcatel-Lucent

All Rights Reserved Alcatel-Lucent 2007

This page is left blank intentionally

All Rights Reserved 2007, Alcatel-Lucent

Switch to notes view!

All Rights Reserved Alcatel-Lucent 2007

All Rights Reserved 2007, Alcatel-Lucent

Table of Contents [cont.]

Switch to notes view!

All Rights Reserved Alcatel-Lucent 2007

This page is left blank intentionally