Rno - Npa To Npo b10 Evolutn

9159 NPO
NPO Operation & Administration

3FL12802AAAAWBZZA5
Edition 05
TRAINING MANUAL
9159 NPO - NPO Operation & Administration

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
NPO Operation & Administration - Page 1
Legal Notice
2
Warning
Switch
Safety
to notes view!
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
9159 NPO
All Rights Reserved Alcatel-Lucent 2007
otherNPO
use
or transmission
Operation
& Administrationof all or any part of its contents may be used, copied, disclosed or conveyed to
any party in any manner whatsoever without prior written permission from Alcatel-Lucent.
Use or transmission of all or any part of this document in violation of any applicable Canadian or other
legislation is hereby expressly prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it
includes or describes, and is expressly prohibited from modifying the information or creating derivative
works without the express written consent of Alcatel-Lucent.
Alcatel-Lucent, The Alcatel-Lucent logo, MainStreet and Newbridge are registered trademarks of AlcatelLucent. 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 AlcatelLucent equipment and its operation.

Table of Contents
3
1. NPO GSM
Switch to notes view!

1. Introduction
2. Operation
3. Operation Advanced
4. Administration
9159 NPO

Table of Contents [cont.]

4
9159 NPO
This page is left blank intentionally

Course Objectives
5
Welcome to NPO Operation & Administration
After successful completion of this course, you will be able to:

Situate the NPO server in the Network and describe its architecture,
Use the NPO Analysis Desktop,
Monitor and analyze the Quality of Service,
Administrate NPO using Import/Export Management and Data Management interfaces.
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
Dates from :
to notes view!
Number of trainees :
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
No (or
globally
no)
Comments
Other comments
Thank you for your answers to this questionnaire
9159 NPO
Yes (or
Globally
yes)

Do not delete this graphic elements in here:
11
Section 1
NPO GSM
Module 1
Introduction
3JK11311AAAAWBZZA Edition 05
9159 NPO NPO Operation & Administration


Section 1 Module 1 Page 1
Blank Page
NPO GSM Introduction
9159 NPO
11
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 Communications 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
26
27
31
32
34
36
37

11
9159 NPO
All Rights
Reserved
Alcatel-Lucent
2007
This page
is left
blank
intentionally

11
9159 NPO

1.1 Presentation of NPO

11
Network Performance Optimizer

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

Networks
9159 NPO
QoS Data & QoS Services :

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

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

An analysis desktop composed of a graphical user interface that allows browsing and benefiting from the
optimization data of the data warehouse. It allows creating and displaying reports.
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 software and database
Single access point to all radio data
Simple and secure management of LAN
9159 NPO
A9159 NPO
LASER functionalities are 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
OMC-R
9159 NPO
QoS
Monitoring

10
1.3 Goals [cont.]

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

11
1.4 Place in the mobile network

11
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 GSM cells : 1200

12
1.4 Place in the mobile network [cont.]

B10
B10
MR2
MR2
11
2. As part of the A1353-MP Multi-Standard OMC Portal (in B10 MR2 : no multistandard)
O&M
GSM B9/B10 OMC-R
O&M
MS NPO
MS SUP
MS PORTAL
WCDMA WNMS
(UA5)
9159 NPO
MONO STANDARD. MS PORTAL is used to increase NPO capacity, but for one RAT only.
max GSM 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)

13

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

and capacity < 250 cells
NPO Client (PC)
OMC-R Master
9159 NPO
OMC-R HMI
NPOE Configurations Hosted by OMC configuration name

NPOE 250 OMC-R (NewHW, NewN HW) Small

14

11
As a standard feature, all OMC-R Master & OMC-R HMI provides basic
NPO functionalities.

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
It allows access to the analysis desktop (NPO main interface) from an OMC-R HMI.
The OMC-R Master contains a NPO server with its ORACLE database.
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

15
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/LAN
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.
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 next 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
Cells Nb.
MS
PORTAL
needed
Max NPO
Users
Sessions Nb.
Max Users
Sessions
Nb./ HMI
Server
Hosted By
NPOe 250
250
No
1(*)
OMC-R
NPO 2000
2000
No
8 NPO
10
Standalone machine
NPO 5000
5000
No
15 NPO
10
Standalone machine
NPO 8000
8000
No
25 NPO
10
Standalone machine
NPO 10500
10500
No
26 NPO
10
Standalone machine
NPO 12000
12000
No
28 NPO
10
Standalone machine
NPO 24000 (*)
24000
Yes
48 NPO
10
Cluster (*)
NPO
Configuration
Name
(*) 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
19
External disk array
See Small OMC configuration
SUN V880
SUN V490
2 x 1.35 GHz
8 GB
2 x 146 GB
None
SUN V880
2 x 900 MHz
4 GB
6 x 73 GB
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
1 SE 3510 per V490 with :

-
12x146 GB 15Krpm
1 RAID controlers
1 Fiber Channel switch
V880
9159 NPO
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.


NPO HMI Server

Configuration
Operating system
Processor
11
ML370 G4
Windows 2003 Server Enterprise Edition (with CAL servers)

2 x 3.4 GHz (single core)
RAM
Disks
Max Numbers of users
Software
DL360 G5
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

20
1.6 Communications View

11
21
TCP/IP
NPO Client
NPO Server
HTTP
Web Browser
Analysis Desktop
JAVA
CORBA
XML
Tomcat
MAAT
JDBC
JDBC
ORACLE
PL/SQL
JDBC
Datasource (OMC-R, WNMS, RNP)

FTP
Crontab / Script
9159 NPO
Plug-In
Generic Loader
This view is overly simplified in order to show only the most important mechanisms.
Analysis Desktop: it is the main optimization interface
Web Browser: can be launched from the icon box to access Administration Facilities
Tomcat: Web Server (using JSP and Servlets for dynamic HTTP/XML)
JDBC: Java Database Connectivity is an API for the Java programming language that defines how a client may access a database. It provides methods for
querying and updating data in a database.
PL/SQL: Procedural Language/Structured Query Language is Oracle Corporation's proprietary procedural extension to the SQL database language
MAAT: Muse Analysis Application Tier is a set of cooperating processes, which offer optimization services and allow browsing the data warehouse content
by translating high-level requests into the corresponding SQL queries.
Plug in and Generic loaders are described in the next chapter.

11
9159 NPO

22
2.1 Overview (multi-standards)

11
23
GSM B9/B10 OMC-R

BSC
MFS
X25
X25
IP
IP
NPO / MS-NPO
WCDMA WNMS
IP
IP
RNC
IP
IP
IP
IP
WIMAX OMC-R
WAC
IP
IP
9159 NPO
IP
IP
A9155 RNP
Planning
The represented case with multi-RAT data sources is not yet available. NPO would be in the MS-PORTAL.
Data Sources : All the possible NPO data providers (RNP, OMCR)
GSM NPO can interface with:
- Two OMC R releases (B9 / B10)
- The current version of A9155 RNP (A9155 V6.x)
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 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 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
NPO relies on dictionaries to describe:

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

11
3 Analysis Desktop
9159 NPO

26
3 Analysis Desktop
3.1 Overview
11
3 Ways to start NPO Analysis Desktop

1. Webstart (Java interface)
2. NPO Client application
9159 NPO
3. With CITRIX

27
3 Analysis Desktop
3.1 Overview [cont.]

11
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

28
3 Analysis Desktop

11
29
Standards
Modes
Functions
Network object
management
Cartography, Diagnosis,
Tuning Session
& Reports Browser
Views Browser
9159 NPO
Standards and Modes Browser Standards define the technologies available on NPO (GSM, UMTS, WiMAX).
Each standard tab has a set of modes. According to the selected mode, the list of displayed counters /
indicators / parameters / reports / views is not the same. It is filtered according to their availability
domain.
Topology Classification Browser Radio resources (cells), as well as physical resources (BTS, NodeB, BSC,
RNC...) are displayed in tree gadgets and can be selected from there. Different tree gadgets are used to
display the network resources by different classification criteria. The classification can be done for
example by LAC, hardware topology, cell type, routing area (for GPRS).
Function Classification Browser Functions belonging to a selected network resource from the topology
browser are also displayed inside tree gadgets and can be selected from there. This area allows the
operator to select: QoS indicators, QoS counters, logical / design parameters, or views / reports
View Browser The view browser is the target place for drag and drop of one or more network resources
and one or more functions.

It contains views that are used to display values of logical / design parameters, indicators, and
counters.
The displayed data in the view can be exported to Excel for further analysis.
Two mode forms are proposed: tabular and graphical.
Report Browser The report browser is the target place for drag and drop of one or more network
resources and one or more views or reports.

3 Analysis Desktop

11
Click
Drag and Drop
Drag and Drop
9159 NPO

30
3 Analysis Desktop
3.2 Network Resources Management

11
Navigation
between GSM,
WCDMA, WIMAX
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

31
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

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

9159 NPO
11

33
3 Analysis Desktop
3.4 Views Browser

11
34
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:

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

3 Analysis Desktop
3.4 Views Browser [cont.]

11
35
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:

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

36
11
4 Questions
9159 NPO

37
Answer the Questions

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

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

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

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

38
Self-Assessment on the Objectives

11
Please be reminded to fill in the form

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

39
Summary
11
B10 MR2 Features :

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

40
11
End of Module
Introduction
9159 NPO

41
12
Section 1
NPO GSM
Module 2
Operation


Blank Page
NPO GSM Operation
9159 NPO
12
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
Page

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
4.7 Customize Reference Dictionnary
9159 NPO
4.8 Rules
NPO 5
Operation
& Administration
Parameters
Tuning
5.1 Benefits
5.2 Process
5.3 Interface
5.4 Reference cells
5.5 Post-its
6 A day at work with NPO
6.1 Schedule
6.2 Interaction with other teams
6.3 Scheduled Reports
7 NPO Customization
7.1 Classification
7.2 User Preferences
8 Annex
8.1 Indicator Editor

7
8
10
20
21
22
28
29
30
32
33
36
37
39
42
45
51
52
54
56
57
58
59
62
66
71
72
73
74
78
79
83
84
85
88
95
96
100
104
105

NPO GSM Operation
12
Page
9159 NPO

NPO GSM Operation
12
9159 NPO

1.1 QoS Counters

NPO GSM Operation
12
Performance Management Counters describe events occurring on the
network
How many calls in this cell ?
How many handovers ? Etc.
There is a specific PM Counter associated to each event (# calls
established, # call drops, # handovers, etc)

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
There are 4 types of counters :
Exercise
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

1.2 QoS Indicators

NPO GSM Operation
12
An indicator is a formula of counters

For instance, SDCCH Assignment Unsuccess %
SDNAUR = [(MC148 + MC04) (MC01 + MC02)] / (MC148 + MC04)
i.e. SDNAUR = (# of requests # of successes) / (# of successes)

There are many families of indicators
TCH, SDCCH, Handovers
GSM, GPRS
Traffic, Durations
RMS averages,
9159 NPO

10
1.2 QoS Indicators [cont.]

NPO GSM Operation
12
Unlike counters, indicators are consolidated !

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

Spatial aggregation
Counters are only available for the basic network element, but indicators
can be aggregated at higher levels.
9159 NPO

11

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

12

NPO GSM Operation
12
13
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
Spatial Aggregation, containing the summarizing data of several network elements into one value that
defines the parent in the network hierarchy. Example: aggregation of cell data to BSC data.
The spatial aggregation is always done on the normalized data, before the temporal aggregation.
Possible spatial aggregations are: MIN, MAX, SUM, AVG, ...


NPO GSM Operation
12
14
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
Temporal Aggregation, containing summarizing data of one network element into one value that defines
the parent in the period hierarchy. Example: aggregation of raw data to daily data.
When the indicator is defined, it is possible to have several aggregation functions; in this case there are
several linked indicators.

Two types of temporal aggregation can be defined:
Stored Aggregation
Calculated Aggregation Calculated temporal aggregation can be used to avoid having too much stored
temporal aggregation when it is possible to calculate it using other indicators (on the fly)
Possible temporal aggregations are: SUM, MIN, MAX, BH, 3DAV, ...


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

Total (TOT)
Maximum (MAX)
Minimum (MIN)
Average (AVG)
Busy Hour (BH) (only for temporal aggregation)
3DAV,
9159 NPO
Busy Hour (BH) : 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
DELTARNO-NPO
RNO-NPO
NPO GSM Operation
12
16
If there are missing data :
Synchronization and
Interpolation to fill
a period (other data
available within this
same period)
Extrapolation to fill
a period which is
entirely empty (no
data within this
period)
9159 NPO
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.


NPO GSM Operation
DELTA
DELTARNO-NPO
RNO-NPO
12
17
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:

Linear interpolation
No interpolation: This does not fill the blanks at all. As a consequence, consolidations will be based only
on collected data.
Padding: Missing data are replaced by numerical value given by operator
Zero: missing data are replaced by 0
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


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

Input & Storage policy :
COUNTERS
ORACLE DB
BASIC
INDICATORS
TEMPORAL AGGREGATION
INDICATORS
INDICATORS
PARAMETERS
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
It is possible to create/edit an indicator with NPO
19
Exercise
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
A set of parameters defines the operationnal behaviour of one element
in the network
BCCH : frequency on which is broadcasted the BCCH
# of SDCCH : number of SDCCH subchannels in the cell
L_RXLEV_DL_H : threshold to trigger a handover cause 5 (low level in the
downlink)
EN_DR : flag to activate the directed retry feature
Most of them describe cells, but some can also describe BSC, TRX or
adjacencies
There are two main types of parameters :
Logical Parameters
Design
Exercise
9159 NPO

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

21
DELTA
DELTARNO-NPO
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

22
2.1 Execute a View [cont.]

NPO GSM Operation
DELTA
DELTARNO-NPO
RNO-NPO
12
23
Exercise
To display reports
In tabular format (Excel-like)
Or in graphical format (one "view" at a time)
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 !

DELTA
DELTARNO-NPO
RNO-NPO

NPO GSM Operation
12
24
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
23
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

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

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

25
DELTA
DELTARNO-NPO
RNO-NPO

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

26
DELTA
DELTARNO-NPO
RNO-NPO

NPO GSM Operation
12
27
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

2.2 Analyse, in tabular mode
DELTA
DELTARNO-NPO
RNO-NPO
NPO GSM Operation
12
The side bar provide advanced tools for analysis
Exercise
Legend and comparisons

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

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

28
DELTA
DELTARNO-NPO
RNO-NPO
2.3 Analyse, in graphical mode

NPO GSM Operation
12
Exercise
Instead of working with tabular
data, graphics are available

Same set of advanced tools :
What is a View ?
A graphic based on several QoS
indicators
Designed by the user (a set of
standard views is proposed by
default)
In the tab "View"
9159 NPO
29
Propagation
Roll up / Drill down
Navigation & Display
Toggle back to tabular mode

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

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

30
DELTA
DELTARNO-NPO
RNO-NPO
2.4 Favorites [cont.]

NPO GSM Operation
12
Exercise
To organize favorites :
Menu bar : "Data > Favorites > Organize "
Drag and Drop indicators from one group to another group
One group of favorites can contain multiple sub-groups
9159 NPO
31

NPO GSM Operation
12
9159 NPO

32
3.1 Execute a Report

NPO GSM Operation
12
What is a Report ?
Stack of several Views
Displays a set of QoS Indicators
Advanced tools for analysis still available
How many types of QoS Reports ? (Mono object, Multi object, )
9159 NPO

33
3.1 Execute a Report [cont.]

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

34
3.1 Execute a Report [cont.]

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

35
B10
B10
MR2
MR2
3.2 Analyze a Report

NPO GSM Operation
DELTA
DELTARNO-NPO
RNO-NPO
12
36
All advanced tools for analysis are available

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

DELTA
DELTARNO-NPO
RNO-NPO
3.3 Collect relevant data

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

CDR between
GSM900 cells and
DCS1800 cells ?
You must customize NPO

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

37
3.3 Collect relevant data [cont.]
DELTA
DELTARNO-NPO
RNO-NPO
NPO GSM Operation
12
What is an object zone ?

Subset of NE's that verifies a filter
Filter(s) are defined by the user
To put it simply, an object zone is an intermediate step in the
consolidation of indicators
Naming 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.

38
3.4 Create an Object Zone

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

Open the contextual menu, and click on Open Zone Manager

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

NPO GSM Operation
12
40
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
DELTARNO-NPO
RNO-NPO
3.4 Create an Object Zone [cont.]

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

DELTA
DELTARNO-NPO
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 ?
42
?
You need to attribute an additional information to each cell !
1. Create manually a "CSV" file, following a specific format

2. Import the "free fields" file within NPO

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.

DELTA
DELTARNO-NPO
RNO-NPO
3.5 Free fields [cont.]

NPO GSM Operation
12
File format for "2G cells" free fields

FREE FIELD;<optionnal comments>
CELL_MCC;
CELL_MNC;
53;
20;
53;
20;
53;
20;
53;
20;
53;
20;
53;
20;
LAC_ID;
3;
3;
3;
3;
3;
3;
43
(*) LAC_ID : depends on mode CI

or LAC/CI
CELL_ID;
50010;
50011;
50012;
53230;
53231;
53232;
<field1>; <field2>;
<value1>; <value2>;
<value1>; <value2>;
<value1>; <value2>;
<value1>; <value2>;
<value1>; <value2>;
<value1>; <value2>;
File format for "other NE's" free fields (ex. TYPE = GPU)
FREE FIELD;<optionnal comments>; <optionnal comments>;<TYPE>
OXEID;
<field1>;<field2>;
GPU_BSC1/2/16779009;
<value1>; <value2>;
GPU_BSC1/2/16779010;
<value1>; <value2>;
GPU_BSC1/2/16779011;
<value1>; <value2>;
GPU_BSC2/2/16779776;
<value1>; <value2>;
GPU_BSC2/2/16779777;
<value1>; <value2>;
GPU_BSC2/2/16779778;
<value1>; <value2>;
9159 NPO
Create "semi colon" delimited files (= CSV files) with the help of Excel, and save as CSV files.
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
DELTARNO-NPO
RNO-NPO
12
Import Free Fields with NPO Import/Export Management
44
Exercise
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:
cd /alcatel/muse/MUSE_QOS/topology/bin
./loadFreeFields.sh <fileName>
Where <fileName> is the absolute path and name of the Free Fields file.
Example:
./loadFreeFields.sh /files/FF.txt
The OEXIDs in the free fields file should match the ones imported by either the Qos/Param topology import
of the customer topology import.

DELTA
DELTARNO-NPO
RNO-NPO
3.6 Create a Report

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

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

NPO GSM Operation
12
Methodology
1. 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
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

46

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


NPO GSM Operation
12
Exercise
Distribution reports
Based on Matrix or Vector indicators
Related only to RMS and GPRS Distribution indicators
1 view / indicator
User can customize the cosmetics only
9159 NPO
49
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
50
Exercise
Warning reports
Based on a standard views
Additional information for filtering :
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)

NPO GSM Operation
12
9159 NPO

51
4.1 Parameters management
DELTA
DELTARNO-NPO
RNO-NPO
NPO GSM Operation
12
52
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 ?
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

4.1 Parameters management [cont.]

NPO GSM Operation
12
53
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)
Parameters checkings can be fully performed on NPO !

Tabular comparisons
Events detections
Events synthesis
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

54
4.2 Tabular Comparisons [cont.]

NPO GSM Operation
DELTA
DELTARNO-NPO
RNO-NPO
12
The legend and highlight tools allow to compare operationnal values
with other values

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

55
DELTA
DELTARNO-NPO
RNO-NPO
4.3 Events detections

NPO GSM Operation
12
Events show when a key information is changed

Highlight a logical/design parameters change
Highlight a topology change
An event is represented by a graphical symbol :
9159 NPO

56
DELTA
DELTARNO-NPO
RNO-NPO
4.4 Events Synthesis

NPO GSM Operation
12
Overlay additional information on a report

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

57
Exercise
4.5 Define Reference Settings
DELTA
DELTARNO-NPO
RNO-NPO
NPO GSM Operation
12
58
In order to compare operationnal settings with your own reference
settings
Preparatory steps :
Define reference settings per cell type, per frequency band, per cell class,
etc.
Assign cell classes
Cell class : family of cells, user-defined. Give more flexibility to references
than the cell type. For instance :
- DENSE URBAN, URBAN, RURAL, INDOOR (Alcatel default classes)
- RAILWAY, TUNNEL, AIRPORT, COLOCATED, (examples)
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
With NPO Analysis Desktop interface

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

59
4.6 Assign Classes to Cells [cont.]

NPO GSM Operation
12
With a planning project import

Along with geo-data, cell class can be defined by RNP
Refer to "Import a Cartography Project" (Advanced course)
9159 NPO
DELTA
DELTARNO-NPO
RNO-NPO

60
4.6 Assign Classes to Cells [cont.]

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

In menu bar, choose "Topology > Network Object Class"
3
1
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

4.7 Customize Reference Dictionnary
DELTA
DELTARNO-NPO
RNO-NPO
NPO GSM Operation
12
In order to compare operationnal settings with your own reference
settings
All references are contained in the Reference Dictionary
Create an Excel file :
One sheet contains references for one object type
References for one object type can be split over several sheets
The file is mono-release
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.

62
4.7 Customize Reference Dictionnary [cont.]

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

63
DELTA
DELTARNO-NPO
RNO-NPO
NPO GSM Operation
12
64
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
DELTARNO-NPO
RNO-NPO

NPO GSM Operation
12
Exercise
Typical Process
1. 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
NPO
NPO
Import
Import//Export
ExportManagement
Management
OPEN Imp/Exp Mng
EXPORT FILE
3
EDITION
Data
DataWarehouse
Warehouse
9159 NPO
65
IMPORT MODIFIED FILE

Admin
4.8 Rules
NPO GSM Operation
12
66
A rule is reflecting the dependency between 2 or more parameters

For example :
A_LEV_HO > A_LEV_PC :
Power control averaging window for signal level has to be short to give a good
reactivity to the Power Control algorithm. Handover averaging window for signal
level has to be long to mean correctly the high fluctuations of the propagation
channel.
IF Number_Of_TRX = 2 THEN Number_Of_SDCCH BETWEEN 8 AND 16

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

4.8 Rules [cont.]

NPO GSM Operation
12
67
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
DELTARNO-NPO
RNO-NPO
4.8 Rules [cont.]

NPO GSM Operation
12
To add or change a rule:

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

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

NPO GSM Operation
12
69
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
DELTARNO-NPO
RNO-NPO
4.8 Rules [cont.]

NPO GSM Operation
12
70
Exercise
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.

NPO GSM Operation
12
5 Parameters Tuning
9159 NPO

71
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
Only light features to ease cell tuning

In case of BSC, TRX or Adjacency tuning, it can take days !
OMC-R operators are not optimizers, they are prone to
misinterpret your changes
NPO Tuning Browser translates your parameters tuning
into a PRC
No risk of misunderstanding between different teams

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

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

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

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

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

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

@
@ OMC-R
OMC-R
73
5 Parameters Tuning
DELTA
DELTARNO-NPO
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.

74
5 Parameters Tuning
DELTA
DELTARNO-NPO
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.

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

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

76
5.3 Interface
DELTA
DELTARNO-NPO
RNO-NPO
How to Do It
NPO GSM Operation
12
77
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
1.
2.
Select the appropriate forecast value for each couple NE parameter

Repeat until all forecast values are tuned
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
DELTARNO-NPO
RNO-NPO
5.4 Reference cells

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

Especially useful to warn other users:
New parameters are set on this cell
A QoS problem is being currently troubleshooted on this cell, etc.
A post-it symbol appears next

to the cell
9159 NPO

79
5.5 Post-its
DELTA
DELTARNO-NPO
RNO-NPO
How to Do It
NPO GSM Operation
12
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.

80
5.5 Post-its
DELTA
DELTARNO-NPO
RNO-NPO
How to Do It
NPO GSM Operation
12
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.

81
5.5 Post-its
DELTA
DELTARNO-NPO
RNO-NPO
How to Do It
NPO GSM Operation
12
82
Create a Frequency Tuning operation

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

1.
2.
Double-click on Forecast to change the frequency of the TRX

Select the BSIC
Exercise
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.
NPO GSM Operation
12
9159 NPO

83
6.1 Schedule
NPO GSM Operation

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
84
Exercise

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.

6.2 Interaction with other teams

NPO GSM Operation
12
85
From A9155 Radio Network Planning tool :

Extract maps in MIF format
Extract CCA in MIF format
Use satellite orthoimage
Import
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.

6.2 Interaction with other teams [cont.]

NPO GSM Operation
12
To A9155 Radio Network Planning tool :

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

86
6.2 Interaction with other teams [cont.]

NPO GSM Operation
12
To Dimensioning teams :
Provide traffic information
Provide operational configuration
From Design teams :

Collect the parameters templates, for each type/class of cell
Or, rather, their NPO reference dictionnary
To Design teams :
Provide operational parameters for all cells
Provide QoS reports related to new settings
Cells with optimized/different settings than their references
9159 NPO

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

88
DELTA
DELTARNO-NPO
RNO-NPO
6.3 Scheduled Reports [cont.]

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

89

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

periodically
Date at which the reports

will stop being created
9159 NPO

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

1. From the Analysis Desktop : Report > Display pending executed reports
2. From the NPO Administration :
Data Management > Administration > Manage Jobs Results
In both cases, same principle : the list of executed reports is displayed

and each report can be viewed on demand
If the report is in NPO format, it will be displayed in the report browser
Else, the report will be saved and opened with an exeternal application
(Excel, Acrobat Reader, etc.)
9159 NPO


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

92

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

93

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

NPO GSM Operation
12
7 NPO Customization
9159 NPO

95
7 NPO Customization
DELTA
DELTARNO-NPO
RNO-NPO
7.1 Classification
NPO GSM Operation
12
Classification of objects and functions can be modified
Topology Classification
9159 NPO

96
7 NPO Customization
DELTA
DELTARNO-NPO
RNO-NPO
7.1 Classification [cont.]

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

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

97
7 NPO Customization
DELTA
DELTARNO-NPO
RNO-NPO

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

Design your new classification : Logical parameters per Unit
4
2
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"

98
7 NPO Customization

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

99
Exercise
7 NPO Customization
DELTA
DELTARNO-NPO
RNO-NPO
7.2 User Preferences

NPO GSM Operation
12
100
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).

7 NPO Customization
DELTA
DELTARNO-NPO
RNO-NPO
7.2 User Preferences [cont.]

NPO GSM Operation
12
101
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

7 NPO Customization
DELTA
DELTARNO-NPO
RNO-NPO

NPO GSM Operation
12
102
"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

7 NPO Customization
DELTA
DELTARNO-NPO
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

103
NPO GSM Operation
12
8 Annex
9159 NPO

104
8 Annex
8.1 Indicator Editor

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

8 Annex
8.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)

106
8 Annex
8.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

107
NPO GSM Operation
12
End of Module
Operation
9159 NPO

108
13
Section 1
NPO GSM
Module 3
Operation Advanced


Blank Page
NPO GSM Operation Advanced
9159 NPO
13
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 Distribution Reports
1.1 Overview
1.2 Method
2 Import a cartography project
2.1 Overview
2.2 Project Structure
2.3 COF files
2.4 Format of background map
2.5 Import
2.6 Configuration files
3 Analyze a QoS problem
3.1 Presentation
3.2 Cartography pane
3.3 Cartography functions
3.4 Cartography & Tuning Session
3.5 Thematic Layers
3.6 Export in GOOGLE EARTH
3.7 Diagnosis
4 Topology Customization
4.1 Customer Topology Objects
9159 NPO
7
8
11
14
15
16
17
23
24
26
28
29
30
36
42
44
46
48
53
54


13
Page
9159 NPO

13
9159 NPO

1.1 Overview
13
There is two types of distribution "view" :

Vectors
PathBalance Distribution
100
60
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)


13
The content of each report depends on the measurements

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

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

50dB, too many
details


13
10
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
DELTARNO-NPO
RNO-NPO
1.2 Method
13
In NPO Administration Data Management

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

thresholds manually,
or by following an
interpolation method
9159 NPO

11
DELTA
DELTARNO-NPO
RNO-NPO
1.2 Method [cont.]

13
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 :

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

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

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

12
1.2 Method
DELTA
DELTARNO-NPO
RNO-NPO
Exercise
13
Group per group, you will perform the update of
the path balance template, accordingly to the

previous slides.
The last group will import it in the OMC-R.
Activation is possible, if wanted.
15 minutes
9159 NPO

13
13
9159 NPO

14
2.1 Overview
13
15
Highly valuable information can be displayed in the cartography module
Offers new ways to investigate a problem

Interferences (co-channels, adjacent channels)
Missing adjacencies
Hot-spot locations
Traffic & QoS distribution over time
9159 NPO

2.2 Project Structure

13
A project is composed of
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

16
2.3 COF files

13
3 mandatory files
CEL.COF : Description of the cell (CGI, coordinates, azimuth, omni/sector)
FRQ.COF : Description of the TRXs
ADJ.COF : Description of the Adjacencies
Minimal amount of data is required to plot the cells

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.

17
DELTA
DELTARNO-NPO
RNO-NPO
2.3 COF files [cont.]

13
CSV format : each data is separated by a semi-colon

Windows > Configuration Panel > Regional Settings
Choose "Customize"
Set the "List Separator" as ; (semi-colon)
When saving a file as "CSV" with Excel, the files will be in the correct
format
Each file starts with 2 identical lines :
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

18

13
19
CEL.COF
Line 3 : column headers
Line 4 n : 1 line per cell
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. TRX_NUMBER
12. BCCH
13. HOPPING_MODE
14. X_SITE_LOC
15. Y_SITE_LOC
16. ANTENNA_ORIENTATION
17. ANTENNA_TYPE (not mandatory)
18. ANTENNA_HEIGHT (not mandatory)
19. ANTENNA_TYPE_FLAG
9159 NPO
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,GSM850GSM1800, 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)


13
20
FRQ.COF
Line 4 n : 1 line per TRX (depends on TRX_NUMBER defined in
CEL.COF)
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


13
21
ADJ.COF
Line 4 n : 1 line per adjacency (it can be empty)
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.
9159 NPO
9. NEIGHBOUR_RXLEV
10. EN_TRAFFIC_HO
11. L_RXLEV_CPT_HO
12. OUTDOOR_UMB_LEV
This file can be empty (only the lines 1, 2 and 3 must be written)
In case adjacencies are imported, only the 2 RNP CELL ID fields are important. Other
fields can use a dummy value.
RNP_CELL_ID : key field, serving cell of the adjacency, to link this serving cell with its
cell definition in cel.cof
NC_RNP_CELL_ID : key field, target cell of the adjacency, to link this target cell with
its cell definition in cel.cof
HO_MARGIN : GSM parameter, in dB
LINK_FACTOR : GSM parameter, in dB
HO_MARGIN_LEV: GSM parameter, in dB
HO_MARGIN_QUAL: GSM parameter, in dB
HO_MARGIN_DIST: GSM parameter, in dB
PRIORITY : GSM parameter, from 0 to 5
NEIGHBOUR_RXLEV: GSM parameter, in dBm
EN_TRAFFIC_HO: GSM parameter, 0 : DISABLE, 1 : ENABLE
L_RXLEV_CPT_HO: GSM parameter, in dBm
OUTDOOR_UMB_LEV: GSM parameter, in dBm


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

DELTA
DELTARNO-NPO
RNO-NPO
2.4 Format of background map

13
Two supported format :

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
Example of a MIF V450 vector file:

VERSION 450
Charset "WindowsLatin1"
Delimiter ","
CoordSys Earth Projection 1,104 Bounds (94,95) (-1,0)
COLUMNS 1
LEGEND Char(50)
DATA
Region 1
31
94.556036 -0.154241
94.561412 -0.156046
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"
RAST file for LONG/LAT WGS84 :

!table
!version 300
!charset WindowsLatin1
Definition Table
File "paris.bmp"
Type "RASTER"
(0,0) (0,0) Label "",
(0.000002741134,0) (1,0) Label "",
(0,0.000002741134) (0,1) Label ""
CoordSys Earth Projection 1, 104
Units "degree"

23
DELTA
DELTARNO-NPO
RNO-NPO
2.5 Import
13
Background file
1. Open the Import/Export Management
2. Select Import > Raster File or Vector
3.
4.
5.
6.
7.
File
Choose the layer name
Choose layer type = Background
Select the file
Click "OK"
Select the georeference file (for
Raster file only)
9159 NPO

24
DELTA
DELTARNO-NPO
RNO-NPO
2.5 Import [cont.]

13
Planned Data
1. Open the Import/Export
2.
3.
4.
5.
Management
Select Import > Planned Data
Select the appropriate format
(GENERIC)
Select the 3 COF files for import
Choose DELTA or NON DELTA
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
6. Click "OK"
9159 NPO

25
2.6 Configuration files

13
On the client, connect to the server
9159 NPO

26
2.6 Configuration files [cont.]

13
The important files :

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

27
13
9159 NPO

28
3.1 Presentation
13
Two main modules in NPO offer enhanced analysis support :

Cartography
Diagnosis
Cartography
Interference
QoS mapping and distribution (thematic layers)
Adjacencies management
Layer management
Diagnosis
Automatic investigation of poor QoS
Based on standard scenarios and operator-customized scenarions
9159 NPO

29
DELTA
DELTARNO-NPO
RNO-NPO
3.2 Cartography pane

Activation
13
2
Select all the cells
9159 NPO

30
3.2 Cartography pane [cont.]
DELTA
DELTARNO-NPO
RNO-NPO
13
Description
Viewport
Toolbar
Mini Map
Layer
Management
Information
Bar
9159 NPO

31
DELTA
DELTARNO-NPO
RNO-NPO

13
32
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
DELTARNO-NPO
RNO-NPO

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

33
DELTA
DELTARNO-NPO
RNO-NPO

13
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

34
DELTA
DELTARNO-NPO
RNO-NPO

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

Scale of
viewport
35
DELTA
DELTARNO-NPO
RNO-NPO
3.3 Cartography functions

13
In the viewport, the contextual menu offers major functions :

Right-click on the background map
The contextual menu recaps toolbar functions

Left-click (= select) and Righ-click on a 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

36
DELTA
DELTARNO-NPO
RNO-NPO
3.3 Cartography functions [cont.]

13
Highlight :
All Parents / Children Objects
BSC
nts
BTS
en
re
pa
Cell 2
ch
il
dr
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)

37

13
Highlight
All incoming / All Outgoing /All Adjacencies
Outgoing adjacency towards the

other co-sector cell
Outgoing adjacency towards 2

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

38

13
39
Highlight
Interfering / Interfered
Interference
Matrix
NPO
CARTOGRAPHY
Import/Export Mngt
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)


13
40
Highlight
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.


13
41
Highlight
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
DELTARNO-NPO
RNO-NPO
3.4 Cartography & Tuning Session

13
42
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.

3.4 Cartography & Tuning Session [cont.]
DELTA
DELTARNO-NPO
RNO-NPO
13
43
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
DELTARNO-NPO
RNO-NPO
3.5 Thematic Layers

13
Objects in the map will be displayed differently, depending on
customized criteria.
Example :
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.

44
DELTA
DELTARNO-NPO
RNO-NPO
3.5 Thematic Layers [cont.]

13
45
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.


13
Export a layer in KMZ format

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.

46
DELTA
DELTARNO-NPO
RNO-NPO
Exercise
13
Using the cartography,

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

47
3.7 Diagnosis
13
48
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
DELTARNO-NPO
RNO-NPO
3.7 Diagnosis [cont.]

13
49
Activation
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


13
50
Different diagnosis
V3_CDR : version 3 of "call drop rate" diagnosis
V4_CDR : version 4 of "call drop rate" diagnosis
V4_CDR_180 : already included in V4_CDR
V4_CDR_TRX : includes V4_CDR + 3 additional tests per TRX
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


13
51
Detailed Output
Each node is detailed, with a

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

3.7 Diagnosis
DELTA
DELTARNO-NPO
RNO-NPO
Exercise
13
Create a favorite with all

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

52
13
9159 NPO

53
DELTA
DELTARNO-NPO
RNO-NPO

13
54
NPO allows to create new network equipments or new relations
between equipments
Mostly defined by their parents/children relations
This customized objects will be treated like the other network objects :
Available in Analysis Desktop
pa
re
nt
Consolidations will be performed at their level

New Relation
GERAN
New Object
ch
ild
re
MSC A
MSC B
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

4.1 Customer Topology Objects [cont.]
DELTA
DELTARNO-NPO
RNO-NPO
13
There are two steps to define a new objects

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

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

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

55
DELTA
DELTARNO-NPO
RNO-NPO

13
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 :
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)

56
DELTA
DELTARNO-NPO
RNO-NPO

13
57
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 :
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
DELTARNO-NPO
RNO-NPO
13
How to import a new Customer Topology Objects Type file ?

Save the file in CSV format (semicolon or comma separated) under
"/alcatel/muse/MUSE_QOS/topology/files/"
Open Import/Export Management > Import > Customer Objects Type
9159 NPO

58
DELTA
DELTARNO-NPO
RNO-NPO
13
How to load the Customer Topology Objects file ?

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

59
DELTA
DELTARNO-NPO
RNO-NPO
Exercise
13
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
Possibility to keep track of network architecture in
NPO
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

60

13

for this module
9159 NPO

61
13
End of Module
Operation Advanced
9159 NPO

62
14
Section 1
NPO GSM
Module 4
Administration


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

Objectives
9159 NPO
14

Objectives [cont.]
9159 NPO
14

Table of Contents
14
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


14
9159 NPO
All Rights
Reserved
Alcatel-Lucent
2007
This page
is left
blank
intentionally

14
1 Data Loading
9159 NPO

1 Data Loading
DELTA
DELTARNO-NPO
RNO-NPO

14
Radio Parameters files imported from OMC-R

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
DELTARNO-NPO
RNO-NPO
14
Before performing a Tuning Session, check the parameters values in
NPO are up to date

Trace files are located in :
\alcatel\muse\data\trace
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
DELTARNO-NPO
RNO-NPO
1.1 Radio Parameters [cont.]

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

It is possible to force the import of ACIE files :
On the OMC-R, enter this command :

/alcatel/omc3/omc3rno/script/run_periodicExport all
Then, on the NPO server, enter this command :
/alcatel/muse/MUSE_PARAM/loader/bin/run_gl.sh
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.
The RNUSM: Export Operation window opens.
2. Select the required directory.
To perform an export, the directory status must be Idle.
The default value of [CGI mode used for Cell Identification] is 'No'. If you need to activate it, set it to
'Yes'. The result is that the CSV files resulting from the export will contain the CellGlobalIdentity
instead of the reference used to identify the cell.
If the Directory Status is... Click on...
Idle
Ready
[Export].
[Free], and then [Export].
Export progress is displayed in the Follow-up window.

3. Click on [Close].

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

14
11
QoS data files imported from OMC-R

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:
cp /alcatel/muse/MUSE_COMMON/config/StorageDuration.csv
/alcatel/muse/MUSE_ADMIN/bin/NewStorageDuration.csv
2. Modify as apropiate the duration values in the new configuration storage duration file.
Do not modify the first two lines of the file NewStorageDuration.csv file.
3. Run the /alcatel/muse/MUSE_ADMIN/bin/ConfigIndDuration.sh script, giving as argument the full pathname of the
file that contains the duration values.
Example:
/alcatel/muse/MUSE_ADMIN/bin/ConfigIndDuration.sh /alcatel/muse/MUSE_ADMIN/bin/NewStorageDuration.csv
In case the new values are smaller than the Evolium recommendations (recommended min values: Raw/Daily 5days,
Weekly 1 week, Monthly 1 month), a warning is displayed. The administrator is not allowed to change the storage
duration to a less than zero value. An error is displayed in case of setting a negative value. Only a positive or null
value is allowed.
The storage duration values are then updated in the database and the status of the operation is displayed to the
administrator.

1 Data Loading
DELTA
DELTARNO-NPO
RNO-NPO
1.3 Consolidations
14
12
The indicators are consolidated automatically, temporaly and spatialy

Temporal Consolidation can be customized :
First day of the week, for WEEKLY consolidations
Login as root user :

- Open /alcatel/muse/MUSE_QOS/config/Consolidation.properties
- Change the WEEKLY_CONSOLIDATION_ON attribute
Example: WEEKLY_CONSOLIDATION_ON=MONDAY
- Save
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
DELTARNO-NPO
RNO-NPO
14
13
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

1 Data Loading
1.4 System Scheduling
DELTA
DELTARNO-NPO
RNO-NPO
14
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
DELTARNO-NPO
RNO-NPO
1.5 Time Zone

14
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

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

14
Parameters Import
CSV : set of ACIE files (12)

RTP :
9159 NPO
B10
B10
MR2
MR2

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

14
18
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.

14
2 Data Management
9159 NPO

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

2 Data Management
DELTA
DELTARNO-NPO
RNO-NPO
2.2 Configuration
14
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
DELTARNO-NPO
RNO-NPO
2.3 Administration
14
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

14
9159 NPO

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

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

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

or root user only)
9159 NPO

DELTA
DELTARNO-NPO
RNO-NPO

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

25
DELTA
DELTARNO-NPO
RNO-NPO
Exercise
14
Export the Report dictionary

Find one of the reports you created earlier
Imports have been done earlier
Free fields
Planned data, etc.
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.

26
14
4 Recovery Tasks
9159 NPO

27
4 Recovery Tasks
DELTA
DELTARNO-NPO
RNO-NPO
4.1 Presentation
14
QoS Data were not retrieved by NPO :

Due to OMC-NPO link unavailability
Due to BSC/MFS-OMC link unavailbility, etc.
Several scenarios have to be considered

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

28
4 Recovery Tasks
DELTA
DELTARNO-NPO
RNO-NPO
4.1 Scenario A
14
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
DELTARNO-NPO
RNO-NPO
4.2 Scenario B
14
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
DELTARNO-NPO
RNO-NPO
14
31
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
DELTARNO-NPO
RNO-NPO
4.2 Scenario C
14
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
DELTARNO-NPO
RNO-NPO
4.2 Scenario C [cont.]

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

At Day 7, 1:00am, the consolidation of Day 6 is performed
automatically.
Possible problem : the time to retrieve all the data takes too much
time, and all data of Day 6 are not imported before the consolidation of
Day 6.
Files automatically 00:00
retrieved
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.]

14
Manual Consolidation :
Choose the date of Day 6 (for

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

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

In such cases, the OMC-R does not have the data in memory anymore,
and data can be considered as lost.
Alternative solution :
1. Get a back-up from the OMC-R, no more than 5 days 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
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.


14

for this module
9159 NPO

36
14
End of Module
Administration
9159 NPO

37
DRAFT
@@SECTION - @@MODULE - 1
@@SECTIONTITLE - @@MODULETITLE
@@PRODUCT
@@COURSENAME

This page
is left blank intentionally
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 b10 Evolutn

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 b10 Evolutn

Uploaded by

Copyright:

Available Formats

9159 NPO

NPO Operation & Administration

9159 NPO - NPO Operation & Administration

Copyright 2007 by Alcatel-Lucent - All rights reserved

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 NPO Operation & Administration

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

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

Switch to notes view!

All Rights Reserved Alcatel-Lucent 2007

Where you can get further information

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

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 NPO Operation & Administration

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 2007, Alcatel-Lucent

NPO GSM Introduction