Wms Cpo Oam06

<Title>

December 2008 UMT/OAM /INF/000005

Wireless Management System for

UTRAN Customer Product Overview OAM06.0

W-CDMA OAM CPO DECEMBER 2008

Alcatel-Lucent – Proprietary

See Notice on

UMT/OAM/INF/000005 - 3 / 99 V06.03 December 2008

Copyright © 2007 by Alcatel-Lucent Technologies. All Rights Reserved.

About Alcatel-Lucent

Alcatel-Lucent (Euronext Paris and NYSE: ALU) provides solutions that enable service

providers, enterprises and governments worldwide, to deliver voice, data and video

communication services to end-users. As a leader in fixed, mobile and converged broadband

networking, IP technologies, applications, and services, Alcatel-Lucent offers the end-to-end

solutions that enable compelling communications services for people at home, at work and on

the move. For more information, visit Alcatel-Lucent on the Internet: http://www.alcatel-

lucent.com

Notice

At the time of publication, this document reflects the latest information on Alcatel-Lucent’s

offer. However, as we are continually enhancing our products and solutions, we recommend

that 6 months after the date of publication you obtain the latest version of this document

from your Alcatel-Lucent representative.

Trademarks

The following trademarks are used throughout this document:

Alcatel-Lucent, Alcatel, Lucent Technologies and their respective logos are trademarks and

service marks of Alcatel-Lucent, Alcatel and Lucent Technologies.

Sun, Sun Microsystems, the Sun Logo, Java and all Java-based trademarks and logos are

trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

Microsoft, Microsoft Internet Explorer logo, Microsoft Office Compatible logo, NetMeeting,

Outlook, PowerPoint, Visio, Visual Basic, Windows, Windows logo, Windows NT, and/or other

Microsoft products referenced are either registered trademarks or trademarks of Microsoft

Corporation in the U.S. and/or other countries



See Notice on Page 2


CONTENTS

1 INTRODUCTION ................................................................................................7

1.1 OBJECT ....................................................................................................... 7 1.2 SCOPE OF THIS DOCUMENT...................................................................................... 8 1.3 AUDIENCE FOR THIS DOCUMENT ................................................................................. 8 1.4 EXPIRY ........................................................................................................ 8

2 RELATED DOCUMENTS ........................................................................................8

2.1 APPLICABLE DOCUMENTS ....................................................................................... 8 2.2 REFERENCE DOCUMENTS........................................................................................ 8

3 SOLUTION POSITIONING ......................................................................................9

3.1 VALUE PROPOSAL .............................................................................................. 9 3.2 WMS PLACE IN TMN REFERENCE MODEL........................................................................ 9 3.3 PRODUCT OVERVIEW..........................................................................................11

4 NETWORK MANAGEMENT PLATFORM .................................................................... 13

4.1 OVERVIEW....................................................................................................13 4.2 ARCHITECTURE ...............................................................................................14 4.3 GRAPHICAL NETWORK DISPLAY .................................................................................16 4.4 ON-LINE HELP SYSTEM........................................................................................18 4.5 CREATING LAYOUTS...........................................................................................18

4.5.1 The Layout Editor.................................................................................19 4.5.2 Creating Network Element Groups ............................................................19 4.5.3 Finding Network Element ......................................................................20

4.6 MANAGING ALARMS............................................................................................20 4.7 LAUNCHING CAPABILITIES AND CUSTOM COMMANDS .............................................................21

4.7.1 Defining Custom commands .....................................................................21 4.7.2 Launching Other Applications...................................................................21

5 FAULT MANAGEMENT....................................................................................... 23

5.1 OVERVIEW....................................................................................................23 5.2 RESOURCE BROWSER ..........................................................................................24 5.3 GRID LAYOUT VIEW...........................................................................................25 5.4 UTRAN MATRIX VIEW ........................................................................................26 5.5 UTRAN SERVICE VIEW .........................................................................................27 5.6 NETWORK BANNER............................................................................................27 5.7 ALARM MANAGEMENT .........................................................................................28

5.7.1 Alarm Browser.....................................................................................28 5.7.2 Alarm management ruleset......................................................................30 5.7.3 Audible Alarm .....................................................................................32 5.7.4 Alarm Correlation.................................................................................32

5.8 HISTORICAL FAULT BROWSER..................................................................................33 5.8.1 Historical Fault Browser tool....................................................................33 5.8.2 HFB input filtering................................................................................34 5.8.3 HFB advanced reporting..........................................................................34

5.9 TROUBLE TICKETING INTERFACE ...............................................................................34 5.10 STABILITY DATA ANALYSER ................................................................................35 5.11 SUPERVISING THE UTRAN ACCESS ..........................................................................36

5.11.1 Shelf Level Display................................................................................36 5.11.2 NodeB External and User Alarm Management ................................................37 5.11.3 Network Element Hardware Inventory.........................................................37 5.11.4 Notification Log Tool .............................................................................38





5.11.5 OSI State Reporting...............................................................................38 5.11.6 Logical and Physical Display GUI................................................................38 5.11.7 Operational Effectiveness GUI ..................................................................40 5.11.8 OAM - Network Elements Link Management ..................................................40

5.12 SUPERVISING OTHER NES..................................................................................41

6 CONFIGURATION MANAGEMENT .......................................................................... 42

6.1 OVERVIEW....................................................................................................42 6.2 GENERIC CONFIGURATION CAPABILITIES ........................................................................43

6.2.1 CM XML .............................................................................................43 6.2.2 Activation Manager ...............................................................................44 6.2.3 WPS Platform......................................................................................46 6.2.4 WICL / Wiclet......................................................................................54 6.2.5 Job Management ..................................................................................55

6.3 CONFIGURING THE UTRAN ACCESS............................................................................56 6.3.1 WPS for Access Network .........................................................................57 6.3.2 Object editor ......................................................................................59 6.3.3 On-line neighbouring manager..................................................................60 6.3.4 Optimized configuration activation............................................................60 6.3.5 FAP / NRP ..........................................................................................61 6.3.6 Audit NE............................................................................................61 6.3.7 Software Download NE ...........................................................................61 6.3.8 Network Element Software Inventory..........................................................63 6.3.9 Backup and Restore NE...........................................................................63 6.3.10 NodeB address GUI ................................................................................63 6.3.11 Command Manager / Access Job History ......................................................64 6.3.12 Network Element Licensing......................................................................64

6.4 CONFIGURING OTHER NES ....................................................................................65

7 PERFORMANCE MANAGEMENT............................................................................. 66

7.1 COUNTERS AND TRACES INTRODUCTION ........................................................................67 7.1.1 Counters families .................................................................................67 7.1.2 Call trace families ................................................................................67

7.2 PERFORMANCE MANAGEMENT GATEWAY........................................................................70 7.3 WIRELESS NETWORK PERFORMANCE OPTIMIZER.................................................................70

7.3.1 Base NPO for W-CDMA functionality : QoS Analysis..........................................70 7.3.2 Web Access module ...............................................................................72 7.3.3 QoS Alerter module...............................................................................73 7.3.4 Rules and Tuning Module ........................................................................74 7.3.5 Geographical Representation module..........................................................74 7.3.6 Diagnosis Module..................................................................................75

7.4 WIRELESS QUALITY ANALYZER – STATISTICAL TRACE ANALYSIS ..................................................75 7.4.1 CTn - Neighbouring Tuning / Mobility Analysis...............................................76 7.4.2 CFT - Call Failure analysis .......................................................................77 7.4.3 CTx - Radio Coverage Analysis ..................................................................78

7.5 RADIO FREQUENCY OPTIMIZER – PER CALL TRACE ANALYSIS .....................................................79 7.6 OPERATIONAL PERFORMANCE MGT.............................................................................81

7.6.1 Alarms On Threshold .............................................................................81

8 SECURITY MANAGEMENT ................................................................................... 82

8.1 WMS SYSTEM SECURITY ......................................................................................83 8.1.1 Security Vulnerability Assessment Process ....................................................83 8.1.2 OS Hardening ......................................................................................83 8.1.3 IP Filters on WMS Servers ........................................................................84 8.1.4 WMS SSL Support..................................................................................84 8.1.5 SSH on WMS Servers ..............................................................................84 8.1.6 Password storage encryption ....................................................................84 8.1.7 Centralized Security Log Auditing..............................................................85

8.2 CENTRALIZED USER MANAGEMENT .............................................................................85





8.2.1 User Administration ..............................................................................85 8.2.2 User Authentication ..............................................................................85 8.2.3 User Authrorization ..............................................................................86 8.2.4 Access Control .....................................................................................87 8.2.5 Role and Task Perimeter.........................................................................87 8.2.6 Password and Account Security Policies .......................................................88 8.2.7 User Session Management........................................................................89 8.2.8 External LDAP Interface .........................................................................89

8.3 SPECIFIC WMS SECURITY FOR UTRAN ACCESS NE.............................................................90 8.3.1 RNC Security .......................................................................................90 8.3.2 NodeB Security ....................................................................................90

9 INTERFACES .................................................................................................. 92

9.1 OVERVIEW....................................................................................................92 9.2 FAULT MANAGEMENT INTERFACES..............................................................................92 9.3 CONFIGURATION MANAGEMENT INTERFACES ....................................................................93 9.4 PERFORMANCE MANAGEMENT INTERFACES ......................................................................94 9.5 INVENTORY MANAGEMENT INTERFACE ..........................................................................94 9.6 NETWORK ELEMENT INTERFACES ...............................................................................95 9.7 SECURITY MANAGEMENT INTERFACES...........................................................................95 9.8 INTERFACE TO MS-PORTAL....................................................................................95 9.9 EAST-WEST INTERFACE .......................................................................................96

10 SYSTEM........................................................................................................ 97

11 ABBREVIATIONS AND DEFINITIONS ....................................................................... 99

11.1 ABBREVIATIONS ...........................................................................................99 11.2 DEFINITIONS ............................................................................................ 100





1 INTRODUCTION

1.1 Object

WMS (Wireless Management System) is the Alcatel-Lucent management platform for

its wireless networks. It simplifies the increasingly complex task of network

management by integrating a comprehensive set of tools and applications into a

coherent management solution targeted for wireless service providers.

WMS is a pre-integrated superior management solution that reduces the delays and

risks associated with extensive system integration. Because it is built around a

standards-based, open and modular architecture, it can also be easily customized or

integrated with other third party management systems. This forward-thinking

approach to solution design contributes to faster network deployment, improving

operators’ time-to-market and competitive positioning. In other words, it helps

generate profits more quickly, with lowered risk.

Better, faster, more efficient management of network resources and next-

generation wireless services results in reduced operational costs, increased revenue

generation opportunities, maximization of network performance, and, ultimately, a

better quality of service for Wireless service providers’ customers.

In this document, a Wireless Network refers to the totality or a part of a network

covering UMTS Radio and some ATM backbone nodes.

This document provides an overview of the Network Management features of the

Wireless Management System. These features are broadly classified into the

following areas:

• Solution Manager fit into operators TMN infrastructure

• Network Management Platform

• Fault Management and Troubleshooting

• Configuration and Inventory Management

• Centralized Network Element software, upgrade and path management

• Performance Management

• Interfaces

• Security Management

• Hardware platform and System Administration





1.2 Scope of this document

This document describes the network management features of the Wireless

Management System solution, covering OAM06.0 release.

1.3 Audience for this document

This document is intended to provide Sales, Marketing and Technical Sales Support

with an overview of the WMS solution, and is for use in preparing bids and other

customer facing documents.

1.4 Expiry

This document is released on a quarterly basis, and readers should obtain the latest

version prior to use. This document version (V06.03 - December 2008) has no

expiration date. However, updated version may be released.

2 RELATED DOCUMENTS

2.1 Applicable documents

[A1]

2.2 Reference documents

[R1] UMT/OAM/INF/000009 WMS Hardware Requirements and Strategy

[R2] NMS/COM/INF/018121 WMS: Feature Planning Guide OAM05.1

[R3] UMT/OAM/INF/021835 WMS: Feature Planning Guide OAM05.2

[R4] UMT/OAM/INF/021269 WMS: Feature Planning Guide OAM06.0





3 SOLUTION POSITIONING

3.1 Value proposal

Alcatel-Lucent strongly believes that it is the infrastructure vendor role to simplify

the operational practices to manage the network infrastructure and the carried over

services. The Solution Manager for Wireless is Alcatel-Lucent answer for enabling

best operating practices for Wireless networks. The value proposal spans over:

• Providing the operator full autonomy with a self-sufficient set of capabilities

including specific know-how in best-practices for Alcatel-Lucent network

planning, building, operating, maintenance.

• Designed for insuring carrier-grade network behavior across ends of the Alcatel-

Lucent Wireless solution contributing in the areas of configuration control,

patching and upgrade, recovery, permanent key network services availability

control.

• Preserving operator’s existing OSS investments and minimizing to highest degree

efforts and maintainability of integration into operator’s multi-vendor solution

enabling value.

• Designed for proper balance and clarity of responsibilities and complexity of

problem resolution between vendor, ISV, SIs and the operator leading to

manageable long term relationship and minimized operating and integration

costs.

• Enabler cost effective and fully controlled projects supported by Alcatel-Lucent

services team who accompanies the operators along plan, build, operate and

maintain activities upon customer requests.

3.2 WMS place in TMN Reference Model

Alcatel-Lucent Solution Manager for Wireless Networks fits in the TMN model as a

sub-network manager. The sub-network manager is an approach finding growing

interest and buy-in on the market from operators, vendors and OSS vendors for its

simplicity and value to the operator.

Networks evolution aiming at enriching drastically network logical / service

capabilities and speeding time to market by combining / reusing best of multiple

network elements capabilities. This evolution drives logical functions and services to

span across multiple heterogeneous network elements. Whereas in that context the

EMS reach their limit as they cannot handle the breath of network elements on

which the logical functions and services span, the OSS are facing the highest degree

of complexity in modeling of network elements specificities and interactions which

remains unsolved at this stage in a context of low agility due to inertia of large live

systems upgrades.





The sub-network manager is a solution of right balance between the EMS and multi-

vendor NMS system. Technically speaking, it simplifies to a high degree the

integration, deployment and upgrade paradigm of the network in the OSS solution by

reducing significantly the number of interfaces to integrate and maintain, it enriches

the quality of information pass through to the NMS system by filtering noisy events

and modeling the logical functions across the breath of network elements involved

enabling even more capabilities on the NMS, it delivers a consistent model of the

multi-structure functions that serves consistently the supervision, the configuration

and quality of service monitoring functions, it is a productized solution widely

deployed pre-packaging Alcatel-Lucent IPRs about its network elements and logical

functions offered and the associated operational processes required for planning,

building, operating and maintaining the network.

EML

SML

BML

Industry-leading Partners

Business

Service

Element

RAN ATM / IP

Other Vendors

Other Vendors

AL

U3r

d P

arti

es

Network

Sub-Network

Wireless Management

System

NML





3.3 Product Overview

W-CDMA Management Solution is focused on efficiently delivering the foundation on

which to deploy and maintain the Wireless Internet network resources, deliver

services, and account for network and service use by subscribers. W-CDMA OAM

solution offers an outstanding rich set of capabilities designed for best fit into

operator’s processes and OSS environment. It provides an integrated solution built

on advanced technology solutions offering end-to-end corporate framework for

Alcatel-Lucent solutions.

The functionalities includes

• Generic end-to-end capabilities based on common services framework

• Specific capabilities required to handle network element specificities

Administration

Services

Configuration

Services

Alarm

Services

Performance

Mgt Services

Interfaces

Services

Security

Services

100% Redundant

platform

Activation

mechanism Alarm mgt Collection mediation 3GPP basic CM Audit Trail

3 sizes OAM hardware

platform

NE Upgrade

mechanism

Alarm filtering &

correlation

NPO for W-CDMA -

Historical storage 3GPP Fault IRP

Centralized

Authentication

Performance

Characterization On-line configuration Launch points

Warnings on

thresholds 3GPP PM Access control

ROC/NOC

Deployment

architecture

Off-line configuration Actions NO - Flexible

Reporting 3GPP Bulk CM Password policies

Server of Clients

enabler

Interfaces & NE

Configuration

Wizards

Display GND NPO for W-CDMA -

Predefined Reporting Inventory XML External Radius API

OAM Installation &

Upgrade Rules checking Layout Mgt Call trace Reporting XML interface User Session mgt

OAM Online Backup &

Restore Templates Topology G.I.S CLI Service (WICL) OS hardening

Online Archive &

Retrieval

Task oriented

assistants

Alarms on PM

threshold

NPO for W-CDMA -

QoS Diagnosis

IOT - Document

license agreement SSH, IPSec

Disaster plan Planning view NE realistic Shelf

level display

Wireless Quality

Analyzer

IOT - Lab

certification Network Design

OAM Software

inventory Work-orders

Sub-component

model Call Failure Trace East-West Interfaces

Software repository Reconfiguration

procedures

Sub-component

states

GIS assisted Cell

Adjacency tuning

Interface to MS-

Portal

Time synchronization Feature Activation

procedures Notifications

QoS & GIS driven

Parameter tuning

Processes mgt Synchronization State propagation

rules

System Management Software Download Alarms on state rules RF planning &

optimization

Stability Data

Analysis

On-line help NE backup & Restore Notification filtering RNP – Atoll Forsk™ RF

planning

Outage events

collection QoS alarms

Command manager NE inventory Mediation / protocol RF Optimizer tool Stability Reporting





At a glance, the W-CDMA OAM solution includes different rich products in its

portfolio to cover the three main aspects of the operation, administration and

Maintenance:

• Planning: Efficient RF planning, Fast pre-provisioning supporting massive roll-

out

- 9352 - Provisioning System (WPS)

- 9355 - Radio Network Planning tool (RNP)

• Operation: Field proven, robust and scalable system for network service

assurance

- 9353 - Management System (WMS)

• Optimization: Best technology for optimizing network quality and spectrum

efficiency

- 9351 - Wireless Quality Analyzer (WQA)

- 9357 - Stability Data Analyzer (SDA)

- 9358 - RF Optimizer (RFO)

- 9359 - Network Performance Optimizer (NPO)

RF Optimizer

9358 RFO

Network Performance Optimizer

9359 NPO

Provisioning System

9352 WPS

W-CDMA Management System

9353 WMS

WirelessQuality Analyzer

9351 WQA

W-CDMA Management Solution

RadioNetwork Planning

9355 RNP

Stability Data

Analyzer

9357 SDAOSS Interfaces – 3GPP





4 NETWORK MANAGEMENT PLATFORM

4.1 Overview

Wireless Management System’s network management capabilities are built upon

Network Services Platform (NSP) technology, a powerful next-generation network

management platform toolset that provides a consistent framework for the

operation, administration and maintenance (OAM) of Alcatel-Lucent UMTS network.

This approach lowers total cost of network management ownership by providing a

consistent management environment for the Alcatel-Lucent UMTS network. It also

offers a combination of simple “point and click” network navigation and list-based

alarm management, as well as a consistent look and feel for network management

capabilities. Together, these features contribute to increase ease of use, therefore

reducing training and operations costs.

The NSP framework provides:

• Integrated fault management across radio access and some ATM backbone

nodes.

• An integrated point of access to other network management capabilities (such

as configuration management tools) included in the WMS Solution.

• An easy-to-use, industry-leading, standards-based graphical user interface (GUI)

environment. This enhances the usability and effectiveness of the WMS solution

by giving a common navigation, functional and task model to the end-user.

• Standards-based (3GPP) fault and network element discovery interfaces for

integration into external OSS. This integration is backed by a program of

thorough interoperability testing with selected third party OSS applications.

• A suit of enhanced fault management capabilities, including:

- Ability to support alarm filtering, supporting both alarm delay and

inhibit capabilities of the alarm stream.

- Ability to perform modification of the alarm severity attribute on

alarms.

- Ability to customize (script) actions to be performed upon receiving an

alarm.

- Ability to set nodes in Maintenance Mode when they are being

maintained so as to not flood the management system with alarms.

- Temporal correlation to allow consolidation of an alarm type which is

being raised multiple times on a particular component.

• A suite of security framework capabilities, including

- a centralized User Directory for OAM user authentication, with the

possibility to use the embedded RADIUS gateway for authentication of

direct access to Network Elements supporting RADIUS





- a complete Role Based Access Control solution for definition of user

privileges as per their functional role

- a centralized audit trail service that provides a common mechanism for

storing audit logs generated within the OAM servers, all authentication

attempts into the NSP framework generate a security audit log

- Support of strong password and account control policies

• A comprehensive suite of administrative and system capabilities that allow the

WMS solution to be customized to meet the operational needs of a specific

Wireless service provider, such as distribution of operations centers and defined

job functions. These capabilities include:

- User access control, both on network elements and permitted actions.

- Customized network layouts and maps.

- Grouping of network elements to simplify management of large

networks, such as the thousands of Node Bs in a UMTS access network.

- System management tools for hardware, operating system and WMS

application supervision.

- On-line help support

- Configurable alarm severity color mappings on the GUIs

- Additional alarm display capabilities including support of components in

the alarm display, support of probable cause and specific problem and

additional text fields in the alarm display, as well as support of viewing

the entire raw alarm.

- Ability to launch fault OAM applications directly from the alarm display.

The Network Services Platform is built upon scalable, open client/server

architecture. Server components are connected through an open, robust Common

Object Request Broker Architecture (CORBA) bus. This is complemented by a

lightweight user interface environment, with a Java client/server architecture that

delivers flexible remote and local user access.

4.2 Architecture

The Network Services Platform is built upon an advanced multi-layer client/server

architecture that delivers superior scalability, openness, extensibility and

survivability. The Network Services Platform architecture is composed of three main

layers:

• Mediation Layer: the Mediation Layer is comprised of Device Adapters (DA) that

allow Network Elements (NEs) and Element Management Systems (EMS) to

communicate with the NSP. Device Adapters connect directly with servers or

building blocks (BBs) found in the Application layer. For example, DAs take

faults from NEs, convert this information to a common format and deliver it to

the NSP Application Layer across a CORBA bus. The NSP includes a set of pre-

integrated DAs that provide complete management of the UMTS access network.





• Application Layer: the Application Layer provides a common foundation of

services and data that underlies all NSP user and machine interfaces. In WMS,

these Application components are generally known as servers or building blocks

(BBs). These servers or BBs take information from the Mediation Layer using the

services of Device Adapters, process it and deliver this processed information to

the Presentation Layer via a set of CORBA contract interfaces. These building

blocks include a Fault Management Building Block (FMBB) and a NE Discovery

Building Block (TUMSBB).

• Presentation Layer: the Presentation Layer provides a consistent, high-

performance, multi-user Java GUI environment. GUI components provide a visual

organization of FCAPS information (Fault, Configuration, Accounting,

Performance, and Security), and facilitate the interaction between the user and

this information. The NSP Presentation layer is comprised of the Graphical

Network Display and the corresponding GUI clients, and is driven by the data

received from the Application Layer.

A simplified view of the NSP architecture is shown below:

This model allows a high degree of consistency and simplification at the user

interface level and permits information exchange with the embedded OAM sub-

systems.

CORBA

CORBA

ApplicationLayer

Mediation Layer

PresentationLayer

Device Adaptors

Servers/Contract Interfaces (Building

Blocks)

GUI Clients

Network Service Platform Architecture

DA DA DA

FM BB TUMSBB OtherBB





4.3 Graphical network display

The Network Services Platform Graphical User Interface (GUI), or Graphical Network

Display, provides a simple, intuitive and efficient user interface and runtime

environment that allows the user to:

• Easily navigate large Wireless networks to find relevant network resources via a

“point and click” interface

• Determine the current operational status of network resources

• Effectively partition the network via user-friendly access controls

• Quickly access value added network management applications

All aspects of the NSP GUI have been designed based on extensive ergonomic

analysis by Alcatel-Lucent Corporate Design Interpretive group (DI), including using

ILOG’s Telecom Graphic Objects (TGO) for Network Management Applications, which

Alcatel-Lucent was instrumental in defining.

The Graphical Network Display provides a graphical view of the managed network

along with tools to quickly navigate the entire network. It also provides fault

management capabilities for the detection, isolation, and correction of fault

conditions within the network (the fault management capabilities of the NSP

Graphical Display are described in further detail in the “Fault Management” chapter

of this document). Integrated into the main window are the following tools:

• A menu bar that provides standardized functional grouping of menus and dialogs

based on TMN recommendations. This consistent user environment increases

efficiency, driving down operational and training costs.

• The Resource Browser, which provides a layered, map-based representation of

the network.

• The Navigator, which provides a hierarchical view of the network organized in a

Windows Explorer TM style tree, based on NE groups (see "Creating Network

Element Groups"). The Navigator also provides a summary count of alarms at

each level in the network hierarchy.

• The Network Banner, which provides an “always on” summary of active alarms

in the network.

• Layout administration tools (Layout Editor and Network Definition toolbar)

• System Administration tools (Application Management, Access Control, and

Custom Commands)

• Status bar, Management and System Management Indicators





The Graphical Network Display is shown below:

The Graphical Network Display also includes a number of features that make it easy

to visualize large, complex UMTS networks, including:

• The variably-sized nodes feature, which enlarges a network element’s icon upon

detecting an alarm on that NE to draw the user’s attention to the problem.

• The ability to group network elements so that a number of NEs (e.g. an RNC and

associated Node Bs) can be shown as a single group icon. Users can see an

exploded view of all the NEs in the group by simply double clicking the group's

icon (additional information on the Network Element Groups is provided in the

“Creating Network Element Groups” section of this chapter).

Context-Sensitive Reach-Through Capabilities

The platform provides simple, in-context access to tools for each network element.

By simply right clicking on a NE or group icon, the user can access a drop down

menu. This contains both generic tools (such as the Alarm Manager, which provides

list-based alarm management), as well as tools which are tailored to the type of NE

(for example, specific EMS tools).





4.4 On-Line Help System

The platform has also offers an integrated web-based help system that provides the

capability to access system documentation from within the graphical user interface,

as well as from the Alarm Manager display.

The on-line help supported include help on alarms from Node B and RNC. The On-

Line Help system is shown below and includes a wildcard search:

4.5 Creating Layouts

A network layout is a

graphical

representation of all

the nodes managed by

the platform. The

platform provides a set

of layout tools that

allow the Resource

Browser to be

customized to address

the challenges of

individual job

functions, multiple

control centers and the

geographic distribution

of the network.





Layout management tools allow the user to position network elements in layouts,

create and modify groups, create physical and/or virtual links between network

elements, and add and modify text labels.

Multiple layouts can be defined according to geographical, organizational, as well as

technological views. Specific NEs can be included in more than one of these layouts.

Multiple layouts make it easy to manage large networks, such as the thousands of

NEs in a typical UMTS access network. By creating layouts optimized for specific

tasks, these tasks can be executed more easily and efficiently. Users can switch

between different layouts, allowing them to select the best layout for the work at

hand.

The platform provides a persistent store for all layouts, ensuring that optimal

layouts can be created and maintained over time. Access to the layout

administration tools can be set using the Access Control tool.

The background map feature allows users to arrange and interconnect NE icons in a

group against an imported background map to match the physical layout of the real

network, as shown below. This feature is capable of importing user-supplied JPEG or

GIF file formats.

4.5.1 The Layout Editor

The Layout Editor provides a

graphical based GUI that allows users

to create network layouts that can

then be displayed in the Resource

Browser. The Layout Editor (shown

below) is launched from the main

NSP Graphical Network Display.

The user can search for specific NEs

using the Find Resources tool (shown

on the left side of the diagram shown

right), and move selected resources to the layout they are editing. Once moved,

these resources can then be manually positioned on the layout.

4.5.2 Creating Network Element Groups

Using the Layout Editor,

the user can group NEs

and represent them by a

single group icon on the

NSP GUI. Groups are

displayed as a border

drawn around the

geographic area that the

group covers, with a

group icon in the centre

that displays summary





alarm information for the group (e.g. the number of critical alarms associated with

the given group). This feature provides a first-alert monitoring mechanism.

The area covered by the group can be a polygon of any shape, can be shaded in a

range colors, and can be translucent so that background maps are not obscured, as

shown right.

Double clicking on the group's icon automatically displays a more detailed group map

containing icons for the individual members of the group. These members can either

be individual network elements, or entire groups in themselves (nested groups).

Grouping reduces network element “clutter” at the highest-level network view,

thereby providing a powerful visualization tool that makes it easy to manage a large

Wireless network. For example, a group could be created containing an RNC and all

the Node Bs that are parented off of it. If two of the Node Bs each had one major

alarm, then the group icon would indicate two major alarms in the group. The user

could then locate the Node Bs which actually has a problem by simply double-

clicking on the group icon to bring up the group map.

4.5.3 Finding Network Element

The find window allows to

quickly retrieve the Network

Elements following various

search criteria: NE, Group,

Graphical Text, Link, NE

Shortcut, All Resources.

4.6 Managing alarms

The Network Services Platform provides first alert capabilities for alarms, allowing

the user to quickly detect and isolate alarms in order to efficiently correct abnormal

network conditions. This first alert capability is provided by (a full description of the

alarm management capabilities of the NSP, along with other value-added alarm

management applications included in the WMS UMTS Access Solution can be found in

the "Fault Management" section of this document):

• The Network Banner and Network Health Indicator, which provide network

alarm status and summary alarm counts

• The Navigator, which displays summary alarm’s counts on the network tree.

• The Resource Browser, which graphically shows alarms on the network map

• The Alarm Manager, which provides a list of active alarms: The alarm manager

displays the component attribute, as well as the probable cause and additional

text attributes. The Alarm Manager supports persistent user preferences so that

operators re-launch of the alarm manager will result in its display in the same





way it was left in the previous session. Sorting of information within the alarm

manager columns is also supported.

• Alarm Management Window, to support enhanced alarm management

capabilities including the creation of rules to allow alarm filtering (delay and

inhibit of alarms) and alarm severity modification. As well, the additional alarm

management capabilities of alarm toggling detection and management and

alarm threshold management capabilities are available via the enhanced alarm

management window. The alarm manager has the ability to display either the

alarms that are unfiltered, or the filtered alarms. A GUI is provided to allow the

operator to select the alarm stream for viewing.

4.7 Launching capabilities and Custom Commands

4.7.1 Defining Custom commands

In addition to Application Launch scripts, the framework provides a lightweight tool

for generating Custom Commands. Custom Commands are configurable commands

that system administrators add to the menus of the GUI to launch external

applications, URLs

into the user's view

or Wiclet based

applications.

Custom commands

can be added to

the menu bar of

any window and to

the right-click

menu of any

object. Examples of commands that can be added include other network

management applications, other applications such as word processors, or URLs for

commonly referenced pages on your company's intranet. This allows users to

customize and personalize their environment with links to specific tools or data that

improve their overall effectiveness.

4.7.2 Launching Other Applications

WMS provides the ability to launch non-embedded applications directly from

platform using Application Launch scripts, delivering a single point of access to

multiple applications. Where appropriate, applications can be launched in context

(e.g. against a specific NE).

The WMS solution comes with pre-integrated launch scripts for the various

applications that make up the WMS solution. Many of the applications within the

WMS solution share the common NSP “look-and-feel”, and combined with the NSP’s

launch capability, this delivers a seamless end-user environment.





The framework display also enables easy, in-context reach-through to underlying

Network Element interfaces or Element Management Systems (EMSs), via the drop-

down menu accessible from each NE’s icon. Users simply select the desired

application from the drop-down menu to launch the NE interface or EMS login

screen.

The framework supports launching of Windows Vista, XP, 2000 and X-Windows based

client applications.





5 FAULT MANAGEMENT

5.1 Overview

The Wireless Management System solution delivers a comprehensive set of fault

management tools, providing consistent, end-to-end management of Wireless access

domains.

These tools simplify the task of fault management in large, complex Wireless

networks. They make it easy for the user to detect, isolate and correct abnormal

network conditions, reducing operational costs and improving quality of service for

Wireless customers.

WMS provides superior first alert fault management capabilities, through a

comprehensive set of tools including:

• The Resource Browser, which graphically shows alarms on the network map

• The Grid layout view, which graphically shows alarms on the grid view

• The UTRAN matrix view, which displays the relationship between RNCs and

their related NodeB NEs

• The Utran Service view, allows efficient monitoring strategy based on

service and status

• The Alarm Manager, which provides a list of active alarms

• The Alarm Stream Management suite of tools, which provides a set of

capabilities to provide server side filtering and support of alarm delay and

inhibition, as well as alarm severity modification.

• Audible alarm capabilities

• The Network Banner, which provides an “always on” summary of alarms

• The Network Health Indicator, which provides a simple summary of system

alarms directly in the main Graphical Display window

• The Navigator, which displays summary alarm counts against a network

tree

• Shelf-Level displays for NodeBs and RNCs.

Simple, point-and-click navigation, best-in-class fault visualization and advanced

layout and grouping capabilities ensure that faults can be located in seconds, even in

networks with thousands of NEs (such as in UMTS access networks).

The Access domain in WMS is internationalized and Network Elements can optionally

be displayed in the following languages: Chinese – Mandarin, Japanese, Korean –

Hangul, and Hebrew.

In addition to these first-alert capabilities, WMS integrates a number of value-added

fault management tools:

• The Historical Fault Browser assists with historical analysis, incident

reporting and customer impact analysis.





• The Trouble Ticketing Interface simplifies and automates the task of

creating trouble tickets, reducing errors and improving help desk response.

• OSS interfaces via 3GPP: 3GPP OAM ITF-N standards compliant fault IRP

interface, which complies with R6 32.111 standards, allowing fault OSSes

to manage faults from Alcatel-Lucent wireless networks via an industry

standards compliant open interface. The 3GPP R6 solution also supports

the standards compliant heartbeat notification mechanism which allows

the OSSes to monitor the logical connection between itself and the Alcatel-

Lucent 3GPP IRP Agent.

WMS ensures the consistency of fault information across all these tools by driving

them with data from a common source, the Fault Management Building Block.

5.2 Resource browser

The Resource Browser is the primary tool for

graphically locating and isolating problems in

real-time on the Wireless network. The

Resource Browser displays alarm information

directly on NE and group icons using a range

of visualization techniques including colors to

distinguish alarm severity, balloons to

indicate new alarms and text indicating both

the number and severity of alarms.

Colored icons allow faults in network

condition to be accurately identified with a

single glance. This alarm information is

displayed directly on the NE and group icons

in the Resource Browser. Examples are shown

below:

2M+ 48

1m+

1m+

FLM 1C+

1C+

DCS

Critical alarm 2 Major alarms: 1 acknowledged, 1 unacknowledged

Minor alarm

Alarm Balloon

1M+

Alarm Acknowledgment

Indicator





The icon color indicates the highest severity alarm on the NE or within the group

(depending on the type of icon). Per default critical and major alarms are red, minor

alarms are orange and warnings are yellow. This color-coding allows the user to

identify problems at a glance. The color coding is configurable thru a dedicated

color coding chooser.

A total count of the highest severity alarms is displayed on the main icon; for

example "1C" indicates that there is one critical alarm (M, m and w and used to

indicate Major, Minor and Warning respectively). If there are also alarms of a lower

severity, then this is indicated by a "+" sign.

For example, "1C+" indicates there is one

critical alarm, but there are also alarms of

lower severity.

Alarm balloons contain information about new

alarms (those which have not been

acknowledged yet by the user). Alarm counts

are displayed in the same way as on the main

icon. For example, in the middle icon shown

above, the main icon ("2M+) indicates that

there are a total of 2 major alarms and further

alarms of lower severity. The alarm balloon

(1M+) indicates that there is one

unacknowledged major alarm (the other major alarm has been acknowledged).

5.3 Grid Layout View

The grid layout view is useful for displaying a large number of NEs in order to see

patterns of alarm occurrence across the network.

It includes the following display options.

• Grid Size - The grid size determines the amount of information displayed on

each NE icon. The smaller the grid size, the smaller the NE icon, resulting in a

larger number of NEs displayed in the Network Panel with less information for

each NE.

• Sort - NEs and groups are sorted from left to right and top to bottom. Sort by

Name: NE and group name in alphabetical order and by Severity: alarm severity

are possible.

Max. Load (100%) 75% Load 50% Load Min. Load (25%)





• Filter on - You can limit the display to NEs display can be limited by filtering on

All alarms, New alarms, Acknowledged alarms or No alarms

• Auto-refresh - When the grid view is sorted by alarm severity or a filter is

applied, the display will update dynamically when the Auto-refresh box is

checked.

With such new capability, the display of the network is simplified and easier to

manage.

5.4 UTRAN Matrix View

The Matrix View offers another network representation that shows the relationship

between an RNC and its related Node-B NEs. It aligns with the designs of other WMS

browser views, which include the ability to scroll, zoom, filter, and sort.

The following screenshot shows an example, where RNCs are presented at the top,

and their related

Node-B NEs are

grouped below. This

example shows a

zoomed-out view,

with NEs been sorted

by severity of

alarms. Additional

information about a

selected NE is shown

in an “In Focus:”

description at the

bottom.

Regular View Max sizeNot sortedNot filtered

Grid Layout View 25% sizeSorted by severityFiltered on alarms





5.5 Utran Service View

The specificities of UMTS Access networks also allow efficient monitoring strategy

based on service and status. WMS therefore offers a GUI providing network-wide

alarm and status summary of critical resources in a tabular format. This GUI displays

one line per group. For each group, the view provides an alarm summary as well as a

configurable status summary for the critical resources: radio cells and interfaces.

This GUI provides filtering and sorting capabilities, as well as navigation to resource

browser and double-tree equipment monitor, hence making it an efficient tool for

network monitoring and first alert.

Utran Service View

5.6 Network Banner

The framework provides a

top-level, real-time fault

summary in the active

layout using the Network

Banner shown right.





This tool uses the same color-coding and text conventions for displaying alarm

information as in the Resource Browser. The alarm color coding is configurable

through a dedicated GUI.

5.7 Alarm Management

5.7.1 Alarm Browser

The Alarm Manager complements the Resource Browser by providing users with a list

of active alarms. This list can be for a single NE, a specific set of NEs defined by the

user, all the NEs within a specific group or for all NEs in the current layout.

The alarm manager can be launched in context from a fault OSS that implements the

appropriate OSS launch invocation capabilities offered by WMS.

The alarm manager can also be accessed in context from the drop down menu

against any of the NE or group icons displayed on the Resource Browser, as well as

from the main menu system. When it is launched in context from the Resource

Browser, the list of alarms is automatically set to display alarms for the selected NE

icon(s) and/or group icon(s) only. This allows the user to easily access relevant alarm

information, leading to more efficient diagnosis and resolution of problems.

The Alarm Manager displays a list of alarms for the selected NEs, which can be

sorted by criteria such as NE Name, alarm severity, alarm type (as per ITU

recommendations), alarm name, and time of occurrence (local time zones are

supported). This list is updated in real-time, although the user has the option of

suspending updates.

The NSP provides a graphical indication of which alarms are acknowledged via the

alarm balloon icon displayed at the left-hand side of each alarm in the alarm list.

Alarms that are not acknowledged have a solid color alarm balloon, in the





appropriate color for the alarm severity, and icons for acknowledged alarms are

displayed without the balloon.

Users can acknowledge alarms by highlighting one or more entries in the alarm list,

by accessing the drop-down menu and selecting the "Acknowledge" option. It is also

possible to "Unacknowledge" alarms using the same mechanism. All

acknowledgements are tagged with the name, host IP and host name of the user who

acknowledged the alarm, as well as the time of acknowledgement. This information

is displayed as part of the alarm details and logged for historical display (see

Historical Fault Browser).

Certain NEs can generate alarms without generating alarm clear notifications. In

such cases, the user can manually clear these alarms using the same mechanism

described above for alarm acknowledgement. Manually clearing an alarm removes

the immediate alarm notification associated with the selected network element.

This option is only available for those alarms that require manual alarm clears,

preventing users from clearing other valid, active alarms. The system administrator

uses the Access Control tool to assign permission to manually clear an alarm.

The alarm manager provide in context launch point to the relevant supported on-line

help information with wildcard search support.

Details about a specific alarm can be displayed by selecting the alarm in the Alarm

Manager. These details are displayed directly below the alarm list. Details include

NE name, Alarm ID, Alarm Type, Unit, Probable Cause, Equipment Type, Common

Language Facility Identifier (CLFI), Reason, as well as acknowledgement information

as described above.





Optional, value added fault applications such as Trouble Ticketing can also be

accessed through the Alarm Manager. Additional information (such as Trouble Ticket

IDs) is also displayed in the Alarm Manager in this case. Details on integration of

these applications with the Alarm manager is described in the appropriate sections

below.

5.7.2 Alarm management ruleset

With the alarm management ruleset, alarm flow can be significantly reduced to

allow quick identification of the really impacting alarms on Network elements.

Alarm Stream Management Rule Set enables a user configuring a set of rules, which

are applied to each alarm received by NSP. It allows user to create a new rule,

remove or update existing rules, and specify whether a rule is applied to the

received alarms, that is, set the rule as activated or inactivated.

A rule consists of two parts, criteria and action.

• An alarm triggers a rule when and only when it meets the criteria specified in

the rule.

• An action specifies what NSP shall do when rule attached by the action is

triggered.

Following actions are available:

• Inhibit - Removes the alarm from the managed stream on a dedicated NE.

• Delay - Delays display of alarms that match the rule criteria for a specified

period of time that is configurable.





• Modify Severity - Replaces the default severity value of alarms that match the

rule criteria with a value selected in the Action area.

• Manage as Toggling - Creates a generated alarm when rule conditions are met,

so that one alarm is displayed in the Alarm Manager instead of having the same

alarm being raised and cleared on the same network element. Toggling ruleset is

especially useful in case of toggling microwave transmission.

• Manage as Threshold - Creates a generated alarm when rule conditions are met,

so that one alarm is displayed instead of multiple alarms. The alarms can be on

one or many NEs, and they can be raised without having been cleared. For

example, during a catastrophic event, a rule can be written to create a

threshold alarm that inhibits a “storm” of alarms in the Alarm Manager.

• Launch Application - Launches an application when rule conditions are met.

• Send email - For alarms that

match the rule criteria, all

alarm information is

automatically forwarded by

email to up to 5 destinations.

• Send SMS - For alarms that

match the rule criteria, most

important alarm information is

automatically forwarded by

short message.

• Auto-Acknowledge - Changes

alarm status to acknowledge

for alarms that match the rule criteria.

The user can filter additionally on criteria:

• Alarm Specific tab: Notification ID, Alarm Type, Severity, Time Raised,

Threshold Crossing

• NE Specific tab: NE Name or type, ID, Location, Component, CLFI, NE

Administrative or Operational State

• Problem specific: Probable Cause, Specific Problem, Additional Text

• Alarmed Component tab: Component DN name containing or equaling a

specified value

These filtering ruleset can be stored as private filtering that are available only for

the creator of the ruleset or as public, therefore available to all WMS users.

The user has the possibility to switch from the managed alarm stream to the

unmanaged alarm stream using this interface.





5.7.3 Audible Alarm

When an alarm occurs, if this

capability is invoked,

configurable audible indications

will be given to alert the

operator of the arrival of the

alarms.

5.7.4 Alarm Correlation

WMS embeds a powerful Correlation engine delivered with a set of predefined

correlation rules. The correlation rules perform alarm grouping and finds

dependencies between root causes and symptoms. Groups of correlated alarms are

graphically reported to the alarm manager. Intuitive alarm colouring associated with

generic graphical capabilities (filtering, sorting) allow for an efficient problem

detection and easy correction. Moreover, groups of correlated alarms can be

classified by service impact, allowing focusing in priority on most-service affecting

problems, hence maximizing troubleshooting efficiency.

Alarm manager displaying correlation information





5.8 Historical Fault Browser

5.8.1 Historical Fault Browser tool

The Historical Fault Browser (HFB) is a value added, optional application that gives

users access to a full set of fault data for historical analysis, incident reporting, and

customer impact analysis.

In WMS, all fault information flows from Device Adapters through the Fault

Management Building Block (FMBB), which distributes the information to client fault

applications - including HFB and the fault browser. This architecture ensures

complete consistency of fault information, so that historical information accurately

reflects the real-time alarm information originally reported to the user.

The Historical Fault

browser collects fault

information from the

FMBB and network

element information

from the TUMSBB. This

information is then

stored in a standard

RDBMS warehouse

(Oracle), with a

capacity of up to 31

million events.

The Historical Fault

Browser database

contains a complete set

of alarm information

for each event,

including:

• NE ID and Name and Unit (where available)

• Alarm Type, ID, Severity, Status, Probable Cause and Additional Text.

• UTC Date and Time

• Acknowledgement information

• Trouble Ticket ID (if the value added Trouble Ticketing Interface is

installed)

This database can be accessed for queries using the Historical Fault Browser Client,

which is a web based Java client that provides easy access to historical fault

information in Network Operations Centers or remote locations.

Users' search and sort criteria can be based on the large supported set of search

criteria.

It is possible to run and display multiple concurrent searches. Search results can be

printed or saved to file in HTML and plain text format.





5.8.2 HFB input filtering

Thanks to the “Advanced Alarm Management” and “Alarm correlation” features,

operators can process the raw alarm flow in order to extract the relevant

information. This introduces a lot of added-value and renders the troubleshooting

more efficient. This added-value processing is preserved in dedicated alarm fields in

the HFB. The operator can exploit those annotations to build statistics, see section

5.8.3.

5.8.3 HFB advanced reporting

The Historical Fault Browser provides an efficient query interface allowing for

advanced statistical reporting. The query interface is accessible from WICL and is

fully configurable by operators. Result of the query is saved in an ASCII file stored on

the main server and made available to external reporting tools for formatting.

5.9 Trouble Ticketing Interface

The Trouble Ticketing Interface (TT) application is a value-added, optional

application that gives users the ability to send trouble ticket requests for specific

alarms to trouble management systems (TMS). It gives network operators the ability

to create trouble reports with complete fault and originator information and allows

the tracking of trouble tickets to be centrally managed and controlled from a single

location.

The Trouble Ticketing Interface application interworks fully with the leading

ClarifyTM Clear Support Trouble Management System and RemedyTM Action Request

System, and can interface with a number of other third-party TMSs that support

SMTP email interfaces. The Trouble Ticketing Interface is a fully manageable CORBA

application (the centralized management of CORBA applications from the Network

Services Platform is described in further detail in the "Managing Applications" section

of this document).

To create a trouble ticket, the user simply selects an alarm in the Alarm Manager,

and chooses "Create Trouble Ticket" in the drop-down menu. The user is then

presented with a dialog box for trouble ticket creation, which is already filled with

all relevant alarm data. The user can then add additional information, such as

additional comments, and issues the trouble ticket.

The trouble ticket data is then stored in a local persistent store on the WMS Main

Server and sent off via SMTP to the TMS. The progress of the trouble ticket is

displayed in the Alarm Manager, and once the trouble ticketing system responds with

a Trouble Ticket ID, the trouble ticket information is displayed in the Alarm Manager

window. If the trouble ticketing system does not respond in a timely manner, a

failure is reported in the Alarm Manager.

Once an alarm is cleared in the WMS system, this information is forwarded to the

TMS using the previously assigned Trouble Ticket ID, allowing the alarm to be

properly cleared in the TMS. This bi-directional capability resolves the time-

consuming and error-prone process of manually synchronizing the two systems.





The TT application can be accessed directly from the NSP Alarm Manager, which

displays trouble ticket information for each alarm as shown below (the Trouble

Ticket ID appears in the right-hand column).

5.10 Stability Data Analyser

The Stability Data Analyzer is an advanced analysis tool highly used by network

management expert teams to provide the advanced capability of reporting on UTRAN

Nodal and interfaces availability and service outage as well as on SGSN nodal

availability. This optional tool is typically used to report on availability of the

network, outages, efficiency of network supervision and used in conjunction with

performance management tools to diagnose performance drop cause. Alcatel-Lucent

teams are structured in order to provide the necessary services of such reporting and

analysis as well as the necessary knowledge transfer on these advanced capabilities.

The tool provides:

• Collection of relevant alarms from HFB

• Collection of configuration management information from the WMS system

• Computation of Nodal availability metrics based on alarm and configuration

• Computation of Interface availability metrics based on alarms and configuration

• Computation of Cells availability metrics

• Reporting





5.11 Supervising the Utran Access

On top of the fault management function provided by the platform and described in

previous sections of this document, the operator benefits from specific access-

centric applications to supervise the Utran network elements.

5.11.1 Shelf Level Display

A shelf level display (or equipment monitor) is provided for both the Node B (iBTS or

OneBTS types) and RNC C/I-Node in the UTRAN. This tool can be accessed directly

from the drop down menu in the Resource Browser, and provides a graphical display

of the equipment in the NE (cabinets, shelves). Alarms are displayed both in a

WindowsTM Explorer type tree and on the shelf level display directly.

For multi-shelves network element (typically the RNC), each cabinet is displayed on

a separate "sheet" in the tool. The fact that a particular cabinet has an alarm is

indicated by a standard alarm severity color (as described previously) on the selector

tab for each sheet.

RNC Shelf Level Display

The shelf level displays can be launched from the NSP alarm list, and the NSP alarm

list can also be launched in context from the shelf level displays.

Shelf Level display includes multiple goodies for ease of use

such as zoom capabilities (zoom in / out / fit in window),

auto-discovery of boards plug in/out, representation of object

states with meaningful icons, help on icons, refresh button, etc.

Shelf level display contains different useful data types such as the dynamic data on

the RNC, PEC code inventory, alarm mapping on physical and logical board /

components, FDDcell attributes, FDDcell states, precise network element type

display, MSS IP address, etc

As for the RNC, the shelf level display is also applicable for the BTS equipment: Each

Node B type and its potential RRH (Radio Remote Head) have its own realistic

customized shelf level display.

In context menu for specific actions

Display of physical boards of the NE

Display of detailed parameter setting

Representation of states with icons

Representation of NodeBs under RNC

Display of logical object tree of the NE

Alarm mapped to the logical or physical component





Various actions can be performed from the Shelf level Display such as performing

reset card, switch card from active to standby, lock resource, shutdown NodeB, etc.

Node B Shelf Level Display

5.11.2 NodeB External and User Alarm Management

Depending of the NodeB type, up to 16 different external alarms specific problems

and up to 4 user alarms can be configured by the operator according to the NodeB

external alarm cabling. This configuration per NodeB instance can be performed

thru the object editor, WICL or thru WPS.

5.11.3 Network Element Hardware Inventory

The RNC and NodeB unitary network element inventory information (product code,

serial number) is displayed in the equipment monitor window except for the

Micro/Pico BTS type for which the LMT is used.

BTS 6010 Compact

BTS 12010Indoor 2

BTS 6020Street

BTS 12020Outdoor

BTS 1020Mono

dBTS6110 + RRH dNodeB 2U + RRH





5.11.4 Notification Log Tool

The Notifications Log Tool

is used to display the

notifications log /

notifications history. The

design of the GUI has been

defined to help the user to:

enter filters to limit the

amount of displayed

notifications and easily

navigate among all the

displayed notifications

(“Navigation” part, sort by

column, Find).

5.11.5 OSI State Reporting

The OSI State Reporting window

presents all NE of a NSP layout and

their sub-components that are not

in a correct OSI state.

5.11.6 Logical and Physical Display GUI

This WMS GUI allows to monitor in real-time some of the most critical resources on

the managed nodes. It relies on the “Dynamic Data” mechanism: the OAM can query

the value of some parameters directly on the node (RNC and iBTS). By default, the

dynamic data are available in raw format in the Equipment monitor. This advanced

GUI provides a graphical representation of those data, hence facilitating their

analysis. The GUI can be refreshed either manually or automatically.

The GUI provides the following data:

Physical RNC and BTS resources

On the RNC side, the GUI provides a tabular view of the CPU occupancy for each RNC

PSFP board, as well as the number of calls processed (MOT/MTC) by each board, split

by call type. It also provides the list of fddcells managed by each TMU.

Retrieval Criteria part

Details partNavigationpart

Banner

List of NEs of the layout with number of their sub-objects in failed state

Last update date

Current progression

List of sub-objects of the selected NE in failed state, with their OSI states





On the iBTS side, the GUI provides BBU usage for each CEM board.

OVSF tree

The GUI provides a graphical representation of the OVSF tree usage.

NodeB common channels status

The GUI provides the common channel status for the selected localcellId.





5.11.7 Operational Effectiveness GUI

WMS provides a set of Operational Effectiveness GUI (WICLETs) that aim at helping

day-to-day monitoring and management of Access networks. The following WICLETs

are available:

UTRAN interface display GUI

This Operational Effectiveness GUI provides a summary view of UTRAN interfaces

statuses for each RNC in the network:

• Operational State

• Administrative State

• Usage Status

VPI/VCI occupancy rate

This Operational Effectiveness GUI allows monitoring the occupancy rate of the ATM

interfaces of the RNC (IuB, IuR, IuCS, IuPS). For each interface, the following

information is provided:

• AtmIf: txCell, txLinkUtilization, rxCell, rxLinkUtilization

• AtmIf/VCC: txCell, rxCell

5.11.8 OAM - Network Elements Link Management

The link between WMS and the RNC and NodeB is constantly monitored.

� In case of link failure between WMS and the NodeB, the NodeB heartbeat

mechanism starts and try to reach regularly (every 90 seconds) its OAM

manager to re-establish the connection. The NodeB will send its list of





active alarms in case of change of serving OAM, OAM link re-establishment

(if new events have occurred during the cut) or BTS restart

� In case of link failure between WMS and the RNC, the OAM heartbeat

mechanism starts and try to reach regularly the RNC manager to re-

establish the connection. The RNC sends the complete list of active alarms

to the WMS system when the OAM link is recovered.

5.12 Supervising Other NEs

On top of the fault management function provided by the platform and the

supervision functions for the Utran network elements described in previous sections

of this document, the operator benefits from the toolset to supervise pure ATM

network elements such as Multi-Service Switch devices family and the 7670 devices

family (ESE and RSP version).

By such all the fault management toolset described in section 5.2 to 5.9 are

applicable to the ATM/IP devices.





6 CONFIGURATION MANAGEMENT

6.1 Overview

The Wireless Management System solution provides a comprehensive set of

capabilities for configuration of the Alcatel-Lucent Wireless Radio access network

elements.

The capabilities are provided through a set of dedicated configuration tools designed

to automate the most time-consuming aspect of configuration activities. These tools

are augmented by in-context reach-through from the Network Services Platform to a

number of underlying EMSs. WMS leverages the rich capabilities of existing EMS tools,

and adds new purpose-built tools where they have the most benefit.

• For the UMTS Access Network, WMS provides several configuration interfaces

adapted to different types of operations. CM XML is Alcatel-Lucent proprietary

main interface for configuration. The WMS server exports the Access Network

Elements configuration, I&C parameters and states over the CM XML interface,

in snapshot format. Conversely, the WMS can import CM XML work-orders,

pertaining to configuration parameters prepared offline. CM XML work-orders

can be prepared off-line using the Alcatel-Lucent WPS (Wireless Provisioning

System) for Access Network tool. WPS Access is part of the WPS configuration

tool suite. WMS also offers on-line configuration capabilities to support network

operations: object editors for parameter tuning, WICL (Wireless Internet

Common Language) for various purposes. Additionally, there is support of a

3GPP BulkCM solution, which allows OSSes to perform bulk provisioning of a set

of UMTS Access network standard RF parameters via a 3GPP standards compliant

interface. “Smart Activation” mechanism guarantees that the activation of a

new configuration on the managed NEs is done with a minimum impact on

service, while reducing the complexity of the activation procedure. WMS

configuration capabilities for the UMTS Access Network also include software

download tools

• For ATM backbone devices, online configuration is provided by reach-through

to underlying EMSs including: WMS Multiservice Data Manager (MDM co-resident

on the Main server) for Multiservice Switch based devices.

Together, these tools support fast, efficient and error-free configuration of the

Wireless network in a seamless network engineering environment - from initial

network design through to actual network configuration - for maximum usability and

effectiveness.





6.2 Generic Configuration capabilities

A very large number of parameters (equipment, neighboring, transmission, etc.)

must be configured to maintain a stable and optimized UMTS network. Moreover,

parameter consistency must be granted across Network Elements and domains. This

makes the engineering of configuration data parameters an increasingly complex

operation in UMTS networks.

WMS provides a set of dedicated configuration tools designed to automate the most

time-consuming aspect of configuration activities. These tools are augmented by in-

context reach-through from the Network Services Platform to a number of

underlying EMSs. WMS leverages the rich capabilities of existing EMS tools, and adds

new purpose-built tools where they have the most benefit.

WMS introduced a standard XML interface for Configuration Management that

federates many Network Elements across domains. This bi-directional interface

exports the actual configuration and imports work-orders for node configuration. A

brand new configuration tool suite, based on a common WPS framework is also

available. These high-performances, flexible tools provide valuable help to the users

for network audit and configuration.

6.2.1 CM XML

The WMS server provides a file import/export interface for the configuration data of

Network Elements. This interface is based on the eXtended Mark-up Language (XML)

format and is referred to as the CM XML interface format.

The CM XML intends to be a generic framework for data exchange

between WMS and external applications, covering multiple

Network Elements, and multiple configuration data. It is a

dissymmetrical interface and two slightly different formats are

defined for the import and export.

WMS exports XML snapshots: those files provide a flat XML

description of the actual configuration of the network. Snapshots

can be filtered, as the WMS provides ability to export the whole

network, an RNS, one or several Network Elements. They can be

scoped to a particular data type:

• Configuration parameters (100% of configuration)

• States and statuses

• I&C parameters (delivered in a separate snapshot) XML

interface

XML snapshot

XMLinterface

XMLwork-orders

XMLinterface

XML snapshot

XMLinterface

XML snapshot

XMLinterface

XMLwork-orders

XMLinterface

XMLwork-orders





Snapshots exported from WMS are tagged with the extraction date and time. They

are stored locally on server and are available to external applications. The export

lasts less than 1 for a typical Access Network and can therefore be scheduled during

the maintenance window.

CM XML sample work-order (left) and snapshot extract (right)

WMS imports XML work-orders: those XML files contain a sequence of operations,

“create”, “delete”, “modify” to be applied on the network in order to implement a

new configuration. Work-orders are generated by external applications, such as the

WPS tool suite (see dedicated sections). Work-orders are activated via the

Activation Manager.

Work-orders contain information fields such as title, originator, creation date and

comment for an efficient management.

The CM XML interface covers an increasing number of Network Elements. In

OAM06.0, it covers:

• 3G BTS (all types)

• RNC (CN, IN)

• MSS7k or MSS15 k based POC

6.2.2 Activation Manager

WMS provides an Activation Manager to assist users with CM access rights in

activating network configuration work-orders: when applying on the live network,

provisioning changes already prepared and consolidated impacting nodes listed

above in CM XML paragraph.

Provisioning Changes are provided in the form of CM XML Work-order files as

described in previous paragraph.

The activation of a work-order is controlled and monitored within an activation

session. This is a step-by-step assistant where the user can consecutively:





• Load a work-order to create a session while splitting WO content in NE

activation units with syntactic checks and application of provisioning changes on

OAM objects. System provides list of OAM and Node impacts then system applies

OAM modifications. Impacted Nodes are locked to prevent concurrent

activations.

• Validate a Session work-order to perform

- Semantic checks: The checks are executed, depending on the Node

capabilities, at WNMS level or at Node level. Semantic checks include intra

Node constraints only; constraints across Nodes have to be handled before

entering the activation process (for example using WPS).

- Analyze all service impact if NE activation units are downloaded. Impact

analysis consists in determining the full set of operations required to

activate the modifications, including the lock / unlock of resources.

According to this diagnostic, the system provides the user with the list of the

possible activation modes that can be used to activate the changes:

- On-line mode available for C-Node and NodeB node types: In this mode,

the system activates the modifications in a sequence that minimizes the

service downtime (as used to do "smart activation"). It is used when

service disruption needs to be prevented. When applicable, it is

proposed as the default activation mode.

- Critical mode available for C-Node and NodeB node types: The

activation is performed in a bulk fashion without considering the

operational state of the device. This mode is used when service

disruption is of minor importance with respect to the criticality of the

modification, or when no other mode is possible.

- Default mode for MSS node type: The activation is performed in one or

two steps according to the workorder content. When some components

have to be activated ahead of the other modifications (e.g. Card) the

system will split the activation in two steps. When applicable, it is

proposed as the default activation mode.

- Single step for MSS node type: The activation is performed in one step

whatever the work order content.

• Pre-activate a NE activation unit which downloads the configuration changes to

the NE to make them ready to be activated and updates WMS MIB working view

(cache memory) if not already done during the validate phase (such as done for

MSS devices)

• Activate a NE activation unit which applies/activates configuration changes on

the NE with the optimized activation policies and WMS MIB working view

becomes the running view

• Resume: The activation operation may be interrupted due to communication

problems with NE and because the activation process requires several activate

commands to be completed. The resume operation enables the user to carry on

the activation process where it stopped.





• Abort: This operation enables to abort an ongoing activation process. The

operation aborts the ongoing jobs without deleting the Activation Session.

• Fallback mechanism is also provided by the Activation Manager.:

It allows a "per NE" fallback, by opposition of a global fallback allowed by the

reverse work-order generated by WPS.

It allows a fallback in case of failure in the middle of a work-order execution and

also a fallback after a successful completion of a work-order execution during

existing Activation Session.

WMS Activation Manager

The Activation manager offers the possibility to activate several work-orders in a

session. In case of a multi work-orders session, all the previous steps are based on

the merge of the work-orders.

6.2.3 WPS Platform

WMS introduces a brand new generation of configuration tools based on a common

powerful platform known as Wireless Provisioning System (WPS).

The WPS platform is a high performance Java application. It is a generic engine

providing a wide range of configuration management and reporting capabilities,

described in this section.

The WPS platform generic approach makes it unique in its ability to easily handle

and manage various object models: WPS-based tools automatically inherit the engine

capabilities. WPS-based tools are therefore primarily characterized by the object





model they manage. Those tools provide a consistent “look & feel” across the

different domains and guarantee a seamless interface to the EMSs since the same

object model is used.

The main role of the WPS tool suite consists in providing the users with tools to

generate XML work-orders to be activated on the live network in order to implement

a target configuration.

The general philosophy of the tool is to preliminarily load a reference snapshot in

XML format (exported from the network) and incrementally modify this view by

generating XML work-orders, containing create, delete and modify unitary actions

that will pile up on top of the reference view, as shown on diagram below.

Current view in WPS tools is obtained by generating work-orders on top of

reference snapshot

It is possible to load up to 2 snapshots from 2 ROCs into WPS to be able to perform

some operations such as a complete scrambling code/frequency plan checks/update

or neighboring links reciprocities checks of the whole network. WPS manages those

snapshots and is able to generate related work-orders for each ROC.

The granularity and content of the work-orders is at the discretion of the user who

can arbitrarily close/open work-orders. Work-orders usually correspond to a given

operation. WPS tools offer the possibility to merge all work-orders or several

consecutive work-orders into one prior to activation.

Several snapshot loading modes have been defined to match operational needs. In

particular, the merge mode and delete mode provide a seamless interface to

external planning tools.

The synchronization feature is a generic mechanism allowing to compare a design

view against a snapshot. It can be used to re-synchronize the tool with current

network prior to work-order activation, in order to detect and correct potential

conflicts. The synchronization feature also provides a powerful audit function, and

provides tabular reports of discrepancies detected between two configurations (see

work-order edition).

Initial Snapshot

WO

WO

WO

WO

WO Current

Workorder

Current View





High performance – one major asset of the WPS platform is certainly its excellent

performance that has no comparison with other configuration tools. The

import/export and processing times allow a near real-time network management and

make the WPS tools suitable for a wide range of

activity, from bulk configuration to audit and daily

operations.

Network tree – The WPS main windows contain a

graphical representation of the managed objects in a

Windows™ Explorer type tree. A similar tree is

available for templates. Many capabilities are

available contextually from the tree. Network tree

can be displayed by object grouping when number of

instances has reached a configurable number.

Object creation – based on model auto-discovery,

hence incorporating object model constraints and

preventing from hazardous configurations

Copy/paste – ability to clone components and

structures (default identifiers assigned can be

modified)

Network tree

Component editor – for quick visualization and parameter update, sorting capability

Component creation window (left) and component editor (right)





Tabular editor – this functionality provides a tabulated view of attributes settings.

It displays, in the same window, all components of common type declared in the

network. The user selects the type he wishes to display by selecting one instance of

that type from the network tree. All common functions are available from the

tabular editor (component creation, single or multiple parameter settings, dataset

creation…).

The WPS tabular editor allows users to copy/paste data in tabular format from an

external application into the editor. Both create/update and delete modes are

supported.

Two contextual operations are available from the tabular editor:

• Create/update using clipboard data

• Delete instances using clipboard data

Note that this interface must be limited to small amount of data and is not intended

to replace the CM XML interface which remains the standard interface for data

exchange.

The copy/paste operation is based on column name matching. Therefore, the

columns headers in the input file must have the same syntax as the tabular editor.

Not matching columns are ignored. However, column can come in any order and not

all columns need to be present: an input file is valid as long as all identifiers are

present. Missing parameters are derived from default template.

Finally, the tabular editor offers the possibility to perform a global comparison

against a template. Discrepancies are highlighted in yellow.

RNC NodeB FDDCell UMTSFddNeighbouringCell Version localCellId locationAreaCode primaryScramblingCodeMY_RNC nodeB4 nodeB43 29.3871 04_00_00 203871 25004 257MY_RNC nodeB4 nodeB43 29.3872 04_00_00 203872 25004 249MY_RNC nodeB5 nodeB51 29.3892 04_00_00 203892 25004 145MY_RNC nodeB5 nodeB52 29.3891 04_00_00 203891 25004 137





Tabular editor views can be exported in HTML.

Dataset – WPS provides a mechanism to build heterogeneous lists of managed

objects. Datasets facilitate data manipulation by isolating working sets. Datasets are

created by selecting selection from the tree, or by converting existing datasets.

Template mechanism – Templates are user-defined containers of values shared

among several objects. Use of templates allows to drastically reduce the amount of

information to be typed in by the user. Several templates can be declared for the

same object class; one is selected as the default and is used during unitary object

creation. Templates can be imported / exported in XML format. Templates can be

cloned. An object configuration can be saved as a template. Template values can be

propagated to a large set of objects

Global update – The global update mechanism allows to modify, in a single action,

the value of one or several parameters to a list of objects (of the same object class).

This facility provides a fast and straightforward solution for bulk parameter setting,

e.g. in case of global threshold refinement on the air interface.

Creation, deletion and update of network elements are performed using the WPS

capabilities and translate in the generation of the corresponding work-order.

Network checker – In contextual launch, checker dynamically adapts: only

applicable checks are listed. Checks and auto-fix (when available) can be enabled /

disabled. Errors are listed in tabular format and provide navigation to object and

parameter on error. Check sessions are saved in the workspace and can be further

re-run. Users can therefore easily track the progress of error correction.

Users can build their own user profile by selecting the checks they are interested in

and save them in the application.

Basic audit capabilities – compare two objects, compare an object against a

template, global tabular display of a given object class, global comparison against

template, comparison against default value, synchronization report between two

days or between target and actual configuration. Most reports can be exported in

HTML and further processed in spreadsheet editors.

Check session report with navigation to object on error





Object comparison report window

Advanced audit automation:

WPS provides an advanced automated comparison with templates capabilities on an

object by object basis. Audit sessions are saved in the workspace and can be further

re-run. Users can build their own Audit profiles and save them in the application.

Audit Session Creation Window

The Audit sessions is launched on a set of objects grouped using WPS multiple

selection functionality, on datasets or on the whole network for a global audit

The output of an audit session is a report capturing the complete context of the

audit session, and that can be saved into a set of html pages, for publication or

archival purpose. The generated audit report contains the delta between the

selected objects and corresponding selected templates and can be visualized using

WPS GUI, web browser or any html editor. Html hyperlinks are implemented in the

report to ease the navigation between different Audit spread sheets.





Audit Report Window

Work-order edition – WPS provides a tabular edition that allows users to modify

work-order content. A navigation feature provides links between commands and

objects and parameters. Therefore, although it can be completed by XML editors

from the market, WPS is the ideal tool for XML work-order edition.

Tabular work-order edition

On top of the generic capabilities, WPS-based tools are delivered with added-value

domain-specific modules, providing high-level wizards and checks. See dedicated

sections for more information.

WPS tools are running on a PC (Windows NT, 2000 or XP) and can be installed in co-

residence on the WMS PC clients.

WPS data sharing environment and users collaboration – This WPS capability can

be optionally activated. It permits to define CM planning teams (e.g. ATM team, IP

team, RF team etc.) using dedicated workspaces. These “project/team” workspaces

within WMS Main Server will host the shared configuration files (XML snapshots &

XML work-orders): a WPS user will be granted access to the workspaces once

authenticated by WMS. From WPS, he will download/upload files from/to this

workspace in a transparent manner (e.g. no usage of manual ftp commands); the

transfer is seen by the user as a simple “open file”.





Team members have therefore a common view of the shared data and can append

their own contributions at any time. If the WPS user downloads a work-order from a

snapshot taken in a workspace originally stamped as version Vn, he will get a real-

time notification if the workspace has been modified in the meantime and therefore

has changed its version to Vn+x.

Local data publication on common workspace repository

Integration of WPS within WMS – WPS provides capability to perform transparent

file transfer (e.g. no usage of manual ftp commands) between WPS and WMS

Activation system. It is possible to retrieve latest live network snapshot or a work-

order from WMS and to deliver work-orders ready to be activated on WMS thanks to

a connection established with WMS main server.

Import snapshot and work-order from WMS





Export work-order on WMS

6.2.4 WICL / Wiclet

Wireless Internet Command Language (WICL) is an OAM scripting language that

allows the user to write scripts to automate time-consuming and repetitive

configuration tasks. Wireless Management System provides a WICL interface for the

Radio Access Network that can be used to manage and configure UTRAN NEs.

WICL allows to perform the following operations in a UMTS network:

• Object discovery

• Object manipulation:

- Access RAN objects (NodeB, RNC, BTSEquipment...)

- MSS based NE (I-Node...)

• Create / Delete objects that can be manipulated by WICL

• Get / Set objects' attributes manipulated by WICL

• Delay a command

• UTRAN operations:

- OAM CM XML import/export

- Download/Activate BTS Equipment Software and RNC Software

- Specific operations on NodeB, RNC or BTSEquipment: build, resetMib,

audit, check xml file, backup/restore, open/close OAM link, etc

WICL uses standard Multiservice Switch CAS commands and as a result, supports all

devices listed in MDM (Multiservice Switch standard EMS) release supplements. For

more details on MDM, please read the relevant MDM documentation





With the Plug-in framework for WICL and graphical page for WICL, the user is able to

put HTML server pages on the disks of the OAM solution. There are called WICLET.

These HTML pages have been designed using standard HTML editors and can be

accessed thanks to the Apache server installed on the servers. These HTML pages can

embed WICL scripts or refer to existing WICL scripts.

This can be considered as an OAM Web site offered to the user and powered with

WICL scripting capabilities.

6.2.5 Job Management

WICL job management - The WMS In-term GUI provides intuitive graphical interface

for WICL job definition and management. Thanks to this intuitive GUI, the operator

can graphically build his WICL scripts by adding WICL commands with a simple mouse

click. For each command, the GUI prompts the user for the mandatory parameters.

At any moment, the script can be edited for manual modification or fine tuning. The

in-term also allows to graphically browse the script repository.

WICL job scheduling – WICL scripts defined in the In-term can be scheduled once, or

on hourly, daily, weekly, monthly or yearly basis. The execution can be recurrent.

Schedule tasks from WMS GUI – WMS offers the possibility to schedule some tasks

from the related application GUI using dedicated button or menu. The user can

schedule the following tasks directly from the GUI:

• Maintenance mode

• CMXML export

• Rebuild/Reset/Audit RNC





• Rebuild/Reset/Audit BTS

• Software activation

• Activation sessions

Job scheduler - The Job scheduling GUI provides a calendar view of the jobs (WICL

jobs and scheduled tasks). The user can display the details of each job, including the

commands, the originator, the execution time…Upon failure, job can be discarded or

retried three times (user demand). Execution result is displayed with status.

The system tasks (tasks previously scheduled in the UNIX crontab at the installation

time) are also visible into the job scheduler. These tasks, tagged as “system

schedule” in the job scheduler, can not be removed and require specific super user

rights to be modified.

The Job scheduler provides a configurable reminder before the job execution; an

email is sent to the users to remind them about the upcoming scheduled jobs and

tasks.

6.3 Configuring the UTRAN Access

A very large number of parameters (equipment, neighboring, transmission, etc.)

must be configured to maintain a stable and optimized UTRAN network. Moreover,

parameter consistency must be granted across domains. This makes the engineering

of software data parameters an increasingly complex operation in UMTS networks.

Wireless Management System provides several configuration interfaces adapted to

different types of operations:





• CM XML is the Alcatel-Lucent proprietary main interface for configuration.

The WMS server exports the Access Network Elements configuration, I&C

parameters and states and statuses over the CM XML interface, in snapshot

format. Conversely, the WMS can import CM XML work-orders, pertaining to

configuration parameters prepared offline. CM XML work-orders can be

prepared off-line using the Alcatel-Lucent WPS (Wireless Provisioning

System) for Access Network tool. WPS Access is part of the WPS

configuration tool suite.

• On-line configuration capabilities (object editors, WICL scripting) are

typically used by operations personnel to make real-time adjustments to the

configuration of NEs, either to tune the performance of specific NEs when

required, or as part of troubleshooting procedures.

• WMS 3GPP R6 compliant BulkCM interface allows OSSes to perform bulk

provisioning of standards based RF parameters on the UMTS Access devices.

A new configuration loaded in the WMS operational database in CM XML format is

activated on the NEs in the most efficient manner thanks to the Activation Manager

which analyzes the modifications to be performed and provides the least service

impacting activation method.

WMS also provides a set of tools that simplify and automate the time-consuming task

of downloading software to the various network elements within the UTRAN.

6.3.1 WPS for Access Network

The WPS for Access Network tool, or WPS Access, is the Alcatel-Lucent UMTS Access

Network configuration tool. Based on the WPS platform, this optional product is an

external offline application of the Alcatel-Lucent Access OAM software.

Besides the basic WPS capabilities described in previous section, WPS for access

Network delivers added-value access-specific configuration capabilities, based on

Alcatel-Lucent expertise in UTRAN configuration.

WPS Access covers the following Network Elements:

• BTS (All types)

• RNC

• POC (MSS7k and MSS15k based)

Task-oriented wizards

In order to configure the thousands of NEs in a typical UMTS access network, WPS

provides high-level task-oriented configuration wizards that simplify the provisioning

task by relying on extensive use of templates and embedded engineering rules. 60 to

90% of parameters are automatically filled.

Wizards are implemented in a task-oriented approach, allowing de-correlated tasks

to be completed independently. The task break-down reflects a typical operator’s

organization and allow several departments to work on different aspects on the

same nodes.





Task-oriented wizards offer a very intuitive graphical support, and provide

contextual help and hyperlinks for a secure configuration.

RNC task-oriented wizard

Task-oriented wizards are available for all network elements and interfaces covered

by the tool:

• BTS (all types)

• RNC (incl. Control Node, Interface Node)

• Iub interface

• Iur interface

• IuCS / IuPS interfaces

Data integrity

A major added-value of the WPS lies in its ability to check the consistency of data to

be delivered on the live network. On top of the model checks delivered with the

object model, WPS provides a wide collection of engineering checks derived from

Alcatel-Lucent engineering expertise in configuring UTRAN networks. WPS has this

unique advantage of centralizing the configurations of all UTRAN Network Elements,

hence allowing cross-NEs consistency checks. Around 800 checks are implemented.

WPS also provides an ATM rule editor allowing the user to define its own rules for

the allocation of ATM parameters over the Iub interface (VPI, VCI, pathId). The rules

are used by the Iub assistant. They can be imported and exported to/from WPS. This

capability allows a flexible, secured and fast allocation method for the hundred

thousands ATM parameters along the Iub.





Operations

WPS user is greatly helped by operations that are a kind of macro-command, which

performs complex network configuration modifications. These modifications are

based on a set of parameters, which can be fine-tuned by the user such as: Delete

NodeB, Links Setting, FddCell feature activation (from a selected NodeB), Delete IuB

(from a selected parented NodeB), Create a new RouteSet, Add one LinkSet,

Configure RouteSets/LinkSets (from a selected RNC).

Neighboring management

WPS for Access Network offers the following for the neighboring management:

• additional operations to automatically create, delete and modify

neighboring links for both 3G/3G and 3G/2G relations (with or without

reciprocity)

• a new conversion mechanism for the incoming and outgoing links of a given

cell

The GUI displays a global view of the neighboring plan. It facilitates and secures the

link creation process. The operation allows also to create links toward Alien 3G cells

by entering the corresponding identification (RNCID, CellId) and other required

parameters.

6.3.2 Object editor

Object editors are available from the WMS GUI and are designed to support

operations personnel making real-time adjustments to NE configuration, for either

tuning or troubleshooting activities.

These default editors allow to display

multiple objects of any Network

Element type (NodeB, CNode, MSS

Based nodes). They provide the user

with information regarding the

parameter setting operation

(constraints, status…). If the

parameter is from previously known

“manufacturer” type, a special

caution message is displayed to warn

the user.

The user can optionally configure the display by grouping parameters in “families”

for improved legibility and usability.

When modifications are applied in off line mode in the object editor, the

corresponding work order is created, the related session is created in the Activation

Manager and the validation step is performed (cf. § Activation Manager for more

details). So the Activation Manager GUI is opened with the related per-NE impact

diagnosis.





6.3.3 On-line neighbouring manager

The On-line neighbouring manager GUI allows for on-line 3G/3G neighboring

management. User has the ability to add/delete/update UMTS neighboring links. The

GUI provides detection and correction of missing reciprocities.

WMS GUI also provides a centralized view of geographical coordinates of the BTSs. It

gathers in a single place the site information, including latitude, longitude, altitude,

but also mail address coordinates (city,street…)

6.3.4 Optimized configuration activation

A configuration task performed on WMS server through the Activation Manager, by

loading a work order or through on-line capabilities, translates into the update of

the WMS operational database. In some cases, the modifications are immediately

reflected on the NEs databases without any delay or impact on service (class3

parameters) during activation step. This is an on-line modification. In other cases,

however, the update of the NEs database is not immediate: the impacted object

must be locked / unlocked. The modification is service impacting (class2

parameters). In some cases, a MIB build is required (class0 parameters).

The validation step of WMS Activation Manager mechanism performs a per-NE

diagnosis and automatically selects the most adapted activation method, hence

reducing the time and service impact of the activation.

In this optimized activation method, the system activates the modifications in a

sequence that minimizes the service downtime by grouping the commands: sub-trees

associated to resources assuring service (Cell sub-trees for instance) are processed

one at a time so that there are never two resources locked at the same time.

Current number of instances/Maximum

number of instances

Identifier

Reciprocity

(y/n)





The availability of this mode depends on the node type ("Online" mode for SEPE

nodes and "default" mode for MSS nodes) and of the nature of modification. When

applicable, it is proposed as the default activation mode.

6.3.5 FAP / NRP

WMS delivers multiple Feature Activation Procedures and Network Reconfiguration

Procedures.

• FAP: IuPC – Agps location services, OCNS activation, 3G to 2G Handover with or

without Compress Mode, HSDPA/HSUPA activation

• NRP: Node B addition, Inter-RNC Node B reparenting, Neighboring plan update,

Scrambling code plan update, LAC/RAC update (Access part)

6.3.6 Audit NE

Network Element audit capabilities are provided by WMS for both the RNC and the

iBTS NodeB. Audit reports are accessible thru a browser and displayed using an XML

viewer.

6.3.7 Software Download NE

Software download tools are available for all network elements in the UTRAN, and

can be launched directly from the NSP GUI. These tools automate the process of

software download, and provide massive parallel download capabilities, as well as

single NE downloads.





BTS 6020Street

Main server

Insertion of NodeB module

NodeB notification to Main server

Automatic Software download

1

2

3

Three tools are provided for software download to the UTRAN. These cover Node Bs,

RNC C Nodes and RNC I/A Nodes respectively.

Node B Software Download and activation

Software can be easily downloaded to Node Bs using the tool shown right, which

enables the download of Node Bs in parallel. The user simply: selects the software

version to be downloaded, selects the set of RNCs whose Node Bs require a software

download, selects the specific Node Bs to which the software must be downloaded

and launches the download. In case of transmission problem during upgrade, the

upgrade is resumed where it was stopped, without needing to download the files

that were successfully received by the Node B.

The WMS assistant performs the necessary controls in order to ensure a smooth

upgrade and prevent any operator error.

Up to 200 Node Bs can be downloaded and activated in parallel.

In some cases, the software download to the Node B is automatic. In case of

insertion of a Node B module

(iCEM, CCM, iCCM), there is

an automatic verification of

software files in the Node B

and, if needed, an automatic

software download from WMS

Access module to BTS. The

insertion of a Node B module

can be replacement of a

faulty module, replacement

of a module by its new

generation (e.g. replacement

of CCM by iCCM) or extension (e.g. addition of a new CEM, of a new iCEM)

Command manager

window displays download to NE with individual progress bar

NodeB RNC

User selects the NE to retrieve

User selects the action





RNC I/C-Node Software Download and activation

A software download tool similar to the NodeB tool described above is provided for

downloading software to RNC I/C Nodes. In case of upgrade, the import of the new

work-order is now performed in hidden mode.

The build operation, which is separated from the download itself, can be performed

in automatic or commanded mode, allowing the operator to better control it.

Up to 5 RNC can be downloaded and activated in parallel.

6.3.8 Network Element Software Inventory

WMS includes a specific menu to retrieve all Access Network Elements running

software version and display it at a glance.

6.3.9 Backup and Restore NE

The backup of RNC control Node is performed as part of the data on-line OAM

backup. The backup of the Multiservice Switch based devices of the RNC (Interface

Node) is based on a WICL script. This procedure is automatically called before a

data on-line OAM backup to ensure consistency of the RNC backup.

NodeB master database is located in the OAM Main Server. By such, backup of the

NodeB is included in the “essential data” backup of the Main Server.

6.3.10 NodeB address GUI

The NodeB address window is a GUI on which the operator can fill some usuful site

information such as the mail address, the city, the geographical coordinates, and

even a free remark field. This address GUI covers both the regular sites and the

Remote sites such as the RRH.





6.3.11 Command Manager / Access Job History

The command manager tool displays all detailed operations performed on the Utran

network. It stores up to 30 days of jobs performed either by the user or in some

specific cases, automatically between WMS and the NE itself (e.g. automatic

software update with the NodeB).

The level of details logged by the command manager is very deep as it logs the

changes on the Utran NE down to the sub-components level (using reach-thru to the

work-order) and precise user name/id, the date/time of the operation, the location,

the type and result of the operation performed, etc.

The user can see the progression if it job thru a graphical progress bar, consult the

error log to identify the potential root cause of failed commands or even stop a

running command.

Advanced filtering options with wildcard are proposed to ease searches.

An efficient user command log participates to the security effort by helping the

operator to quickly sort out mistakes / voluntary hacker and ease the Alcatel-Lucent

support organization.

6.3.12 Network Element Licensing

When the customer is ordering a new hardware module, he/she can choose to order

it with a minimal initial capacity and subsequently purchase, through a capacity

licensing scheme, additional capacity only if and when needed. Capacity can hence

be remotely added to existing BTS sites without any need for site visit. WMS

includes a framework for iBTS capacity licensing allowing the operator to manage

smoothly at the OAM level, a pool of token representing different NodeB capacity.





From the licensing console, the user is able to retrieve all the NodeB on which a

given license have been installed and at the opposite to retrieve all the licenses that

are in use on a given NodeB.

6.4 Configuring Other NEs

As an option, Element Managers for other supported NEs can be accessed from the

NSP Resource Browser using drop-down menus on their corresponding NE icons.

Alcatel-Lucent would be pleased to provide a list of supported applications and

services as well as documentation on these platforms and their Element Managers.

The ATM backbone network element based on Multiservice Switch devices are

configured using the set of tools by the EMS Access described in section 6.3.

The ATM or IP backbone network element based 76xx or 77xx device family are

configured using respectively the 5620 NM or 5620 SAM EMS.





7 PERFORMANCE MANAGEMENT

The Alcatel-Lucent Wireless Management System WMS is a scalable and distributed

solution. The Performance Management solution covers all the Access Alcatel-Lucent

NEs and runs on a dedicated server. It consists of the following offerings:

• Standard offer: It encompasses the performance management gateway which

provides unified collection and mediation capabilities of all Alcatel-Lucent UMTS

Access raw counters and log files.

• Enhanced Performance Management offer: It is an optional offer which

provides sophisticated performance management, optimization and on

troubleshooting capabilities targeted to operational needs or engineering needs.

• Operational Performance Mgt

- Alarms on threshold

• Engineering Performance Mgt

- Network Performance Optimizer (aka NPO)

- Call Trace Reporting – Radio Frequency Optimizer (aka RFO)

- Wireless Quality Analyzer (aka WQA)

The following figure depicts the architecture the PM solution and how it is can be

integrated in an overall OSS system:

NML Layer

Network Planning

PerformanceReporting

SQM

Collectionand

Mediation


XM

L In

terf

ace

• Solution deployed in NOC – E2E Reporting in Multi-

vendor, multi-technology networks

– Alcatel-Lucent wireless Access network reporting

Vendor Collector

Other vendors

Other vendors

• Solution deployed in ROC configuration

– Base Offer:– Counters collection and

mediation– External Interface

– Advanced functions (options)– Performance reporting– Statistical trace analysis– Per Call trace analysis– Operational AoT

EML Layer

NE Layer

StatisticalTrace

Analysis

Per Call Trace

analysis

GERANOr

WIMAXAlcatel-Lucent

OMC-R

GERAN or WIMAXCollectors

Portal

UTRANGERAN

WIMAX


OtherOffice

application

UTRANCollectors

Fo

cuse

d In

terf

ace

Fo

cuse

d In

terf

ace

Off

ice

Exp

ort

OperationalAoT





7.1 Counters and Traces Introduction

7.1.1 Counters families

WMS collects, mediates, displays and correlates counters from the Access network

elements.

Utran Network Elements counter families

On the Node B, the following counter families are defined: PCM, ATM, Radio, BTS

Load management, RACH, EEC, IMA, and IP.

On the RNC, the families are: Radio Link management, Handovers, Power

management, RRC Connection, Iu interface, RAB and RB management, Security,

Paging, Mobility, Radio measurement, User Plane Common Traffic, Iur Interface,

User Plane Dedicated Traffic, RNC Load management.

Moreover, customers can take advantage of Alcatel-Lucent expertise in PM through a

Metric and Reports customization Service which allows supporting customers building

metrics adapted to her/his need.

7.1.2 Call trace families

Alcatel-Lucent provides a rich set of trace types. These traces can provide detailed

trace Information (Collected data) captured by UTRAN. The Collected data can vary

according to the trace types.

Trace types

The following Call trace types are available:

• CTa

This type of session allows tracing:

- one or several UE calls selected by the Core Network using either their

IMSI or IMEI.

- one or several UE emergency calls (FRS 25028)

- and one or several CallAbnormalityTraceDetectedCellInfo (FRS 27219)

A CTa session is permanently activated by an OMC with each RNC it controls.

No user action is needed for this at the OAM level; nevertheless the user has

to access the Core Network to enter the identifier (IMSI or IMEI) of the UE(s)

that needs to be traced.

• CTb

A Call Trace B session provides data related to all calls initiated for a

specified UE during the session activation.

There is one and only one UE traced in a CTb session.





Therefore if n mobiles are to be traced simultaneously, then n sessions are

created

The UE identity specified on WMS when creating a CTb session may be one of

all choices of the “Initial UE identity” IE supported by the RRC protocol

listed below:

- an IMSI

- a TMSI

- a P-TMSI

- an IMEI

• CTg

A Geographic Call Trace (CTg) session allows tracing calls established within

a geographical area.

Once established and traced, the calls may be traced even if the related UE

move into areas which do not belong to the defined geographical area

When creating a CTg session, the user has to specify:

- A geographic area; the geographic area may be a cell, a set of cells or

all the cells in the RNS.

- The types of calls that will be traced within the session (based on the

RRC establishment cause).

• CTn

Neigboring Call Trace (CTn) is used to monitor and optimize neighboring

relations by tracing information related to calls’ mobility.

The RNC logs events related to a traced call only when the call is inside the

configured area (when the call leaves the area the RNC stops tracing, and

when the call comes back into the configured area, the RNC resumes the

tracing).

A CTn session is created and activated on a geographic area (a cell, a set of

cells or all the cells in the RNS)

• OT (Object Traces)

Object Trace sessions are used to provide Trace data related to a network

elements (cell/RNC) or network interfaces.

Events are traced because they are attached to a given cell or interface and

not because they are attached to a call, then there is no tracekey

management.

Only common protocol messages (and common measurements) are logged by

OT sessions.

Depending on the OT session type, the session can be activated:

- On a NE or a list of NEs or

- On a network interface or a list of network interfaces





• CFT (Call Failure Trace)

This feature is to be used to trouble shoot and investigate call drops on a

specific network area.

When the Call Failure Trace (CFT) is activated the RNC logs a snapshot for all

the call drops that occur on the configured area.

A CFT session is activated on a geographic area (a cell, a set of cells or all

the cells in the RNS) that needs to be investigated trough a CTg session

activation with additional sub-function.

Collected data

Data Collected in the Trace Sessions can be the following:

• Dedicated protocol messages: Dedicated protocol messages can only be

traced through CTa, CTb and CTg session (not through OT-xxx sessions).

Dedicated measurements can be traced by CTb and CTg session but not by

CTa session.

• Common protocol messages: Common protocol and measurement messages

can only be traced through OT-xxx sessions (depending on the OT sessions

and message types of course).

• Snapshots: A snapshot is a record of data logged by the RNC when a specific

event occurred (it more or less reflects the context of the call when the

event occurred). Snapshots are useful for the monitoring of features that

can not be easily observed through protocol messages. Snapshots are call’s

related and thus only logged through Cta, Ctb and Ctg sessions.

• Inode traces: Inode traces are to be used to monitor the RLC Traffic and the

BLER before RNC combination. Inode traces are very heavy in terms of

generated volume of data.

Data to be logged by Network Elements are organized into different trace Functions

and Sub-Functions. Each traced Function / Sub-Function provides information on a

particular aspect of the Call processing. As an example, the trace sub-function

named “RRC dedicated traffic” covers the RRC signalling messages exchanged

between the UE and the network in dedicated mode.

NE collected records are presented according to three different “Trace modes”

• Mode 1 - “Event only” (contains the traced function and sub-function, the

event name, a time-stamp, the related cell Id, the related RNC Id)

• Mode 2 - “ASN.1” (contains a header and the full record information, coded

in ASN.1 - applies only to UTRAN protocols PDUs)

• Mode 3 - “Ctx_full” (provides a specific set of additional data associated to

the event)

To ease Call Trace configuration the traceable Functions / Sub-Functions and

associated Trace Modes are organised in predefined “Session Templates” (user

configurable) that can be selected during the call trace session configuration.





7.2 Performance Management Gateway

Raw counters collected from the various Access NEs are stored in measurement files

temporarily in flash or local disks on the NEs. They are then collected periodically

from the NEs and mediated in an XML format compliant to the 3GPP 32.401

recommendations by the Performance management gateway. Theses measurements

files are deleted as soon as the file transfer is successfully completed. This is the

regular North northbound interface used for integration with third party OSS

applications.

7.3 Wireless Network Performance Optimizer

Wireless Network Performance optimizer (NPO for W-CDMA) is the next generation

Performance reporting product of Alcatel-Lucent. It is based on the field proven

NPA/RNO product, which has been recognized as one of the most efficient

Performance reporting product for wireless access products.

The main values brought by NPO for W-CDMA are :

• User Efficiency :

- Integrates previous NPA and RNO functionality

- Additional features : Rool-up/ Drill Down, parameters history, …

- Common 2G / 3G framework

• Capacity and clustering

It leverages Alcatel-Lucent Intellectual Property Rights (IPR) in Network QoS

reporting, Assisted network tuning, QoS Diagnostics, Network availability reporting,

enabling :

• Time-to-market acceleration for Alcatel-Lucent WCDMA portfolio evolution

• Better performance management product support

• PM Portfolio mastered by Alcatel-Lucent services teams

NPO for W-CDMA provides state of the art QoS analysis capabilities (base NPO for W-

CDMA functions), as well as advanced functionality allowing full analysis of the

counters based performance of UTRAN network.

For hardware configurations, please refer to the WMS Hardware boilerplate.

7.3.1 Base NPO for W-CDMA functionality : QoS Analysis

For the quality of service analysis, and for back-office activities like network

optimization and network planning, periodical measurements on radio traffic, radio

resource usage, transmission and hand-over behavior are collected from the network

elements through WMS. The network-wide QoS analysis relies on the regular

collection of the same performance counters on all managed Network Elements.

The counters are stored in the NPO for W-CDMA database. Counters of both

permanent measurement campaigns and on-demand measurements campaigns are





kept whatever the granularity period of those campaigns. Based on the counters,

indicators are calculated and stored for up to 1 year.

Standard indicators are defined by Alcatel and provide expressive QoS analysis data.

Indicators are consolidated in daily, weekly and monthly values and can be

additionally consolidated on a group of Network Elements.

For specific needs where the standard indicators are not appropriate, it is possible

for the operator to define its own indicators called defined Indicators via a

customization toolbox. The optimizer can select and launch predefined or user-

defined QoS report based on those indicators.

NPO for W-CDMA provides a powerful dynamic graphical user interface that eases

QoS-report analysis. The operator can display the results in the form of reports

containing both tables and graphs (several counters/indicators graphically displayed

simultaneously). For easier adaptation to operator needs, the operator can

customize QoS reports.

Special functions allow identifying the worst or best cells related to a QoS indicator,

to get reports on the QoS evolution and to compare the service quality of different

cells. Comparing QoS indicator values with predefined thresholds, NPO for W-CDMA

allows a very fast verification of the quality of service in each single cell.

Additionally, the QoS evolution can be correlated with parameters or topology

changes. NPO FOR W-CDMA provides this capability by offering the possibility to

display a synthesis of those events in reports.





7.3.2 Web Access module

With this NPO for W-CDMA optional functionality, it becomes possible to extended

access to network performance. For instance, Executives or marketing team can

quickly visualize main performance criteria of the network and its evolution since a

month.

NPO for W-CDMA offers a public web interface to allow access to views and reports

with a web browser.

NPO for W-CDMA users publish some reports for external access by light client. These

NPO for W-CDMA users just need a web client on their PC to get access to published

reports.





7.3.3 QoS Alerter module

The aim of this NPO for W-CDMA option is to allow the user be alerted when a QOS

criteria is not met. Complementary to the alerter available in WMS, NPO for W-CDMA

alerters can be set on complex criteria (i.e. NPO for W-CDMA indicators) and are

evaluated with a minimum of 1 hour periodicity. When an indicator exceeds (or goes

below) a given threshold, NPO for W-CDMA can generate an internal alarm and can

warn external systems through SNMP Traps.

This combination indicator / threshold make a NPO for W-CDMA “alerter”. Standard

alerter and Variation alerter are available.

Standard alerter generate alerts in case of threshold crossing. The used threshold

value is defined by the selected threshold color. The stability parameter permits to

decide when an alert is to be generated: for example if the value given is 3, an alert

will be generated only if during the 3 last periods, the threshold was crossed. If the

sampling is used, alert is not be generated if the sampling conditions are not fulfilled

Variation alerter generates alerts if the variation of the indicator value compared to

a pre-defined “base line” exceeds pre-defined delta.

4 parameters are to be given to implement variation alerter:

• The number of observation periods P

• The number of smoothing periods Q. Q is always lower than P. It represents

the number of periods needed to compute the first (F) and the last value (L)

of the curve.

• The delta in percentage that is used to determine if alert must be

generated.

• Algorithm (Average, Max, Min, Sum)

One period matches on the granularity of the alerter (e.g. if granularity is 1 hour and

P=4, observation period is equal to 4 hours)

Example of variation computation with P=12 and Q=3:

0 2 4 6 8

10 12 14 16 18

1 2 3 4 5 6 7 8 9 10 11 12

P=12

F L Q=3





The variation coefficient is S = (L – F)/F

Average: (8 – 14)/14 = -0,42

Min: (7 – 12)/12 = - 0,42

Max: (9 – 16)/16 = - 0,44

Sum: (24 – 42)/42 = - 0,43

S is displayed in percentage (S multiplied by 100). It can be then compared to the

given delta percentage. If the absolute value of S is higher than delta, an alert is

generated.

7.3.4 Rules and Tuning Module

The radio resource configuration handling of NPO for W-CDMA allows verifying the

operational logical parameter settings by comparing the operational values with

reference values or with the value of the parameter at a previous In order to follow

the evolution of the logical parameter settings, the imported operational values are

stored in the NPO for W-CDMA database and appropriate reports can be requested at

any time.

At the end of a network optimization session the NPO for W-CDMA radio parameter

tuning function allows to use the results of the optimization session (monitoring,

checking, diagnosis) for tuning the radio configuration, in order to correct network

misbehavior.

With this NPO for W-CDMA option, the user can prepare radio resource configuration

modifications, frequency changes and prepare them to be consolidated through the

available facilities of WPS before the application on WMS.

7.3.5 Geographical Representation module

Geographical Representation is a NPO for W-CDMA optional feature displaying QoS

information on the geographical representation. Its purpose is to highlight

geographical areas according to QoS indicator and parameter values, analysis

results, etc…





NPO for W-CDMA provides a thematic layer editor where each operator can enter his

own layer requests and define the associated colour scheme for highlighting the

results.

7.3.6 Diagnosis Module

For QoS problem diagnosis, NPO for W-CDMA helps to investigate the cause of the

QoS degradations identified through the QoS Analysis optional functionality. Based

on diagnosis scenarios, NPO for W-CDMA proposes some corrective actions and/or

extra investigations. For

instance, these custom

diagnosis scenarios can detect

parameters setting errors.

7.4 Wireless Quality Analyzer – Statistical Trace Analysis

Wireless Quality Analyzer (WQA) allows UTRAN network optimization based on the

UTRAN traces generated by the RNC.

WQA follows a web-based architecture, working on a Microsoft Windows™ server.





WQA can come with one or several of the 3 modules below:

1. CTn - Neighboring tuning /Mobility Analysis

2. CFT - Call Failure Analysis

3. CTx - Radio Coverage Analysis

7.4.1 CTn - Neighbouring Tuning / Mobility Analysis

The purpose of this module is to provide customers with a product that helps users

to tune the mobility within UTRAN: a

neighboring tuning product.

Based on CTn traces generated from

UTRAN, WQA calculates per call KPIs

and per couple of cells which allows

users:

1. to detect useless neighboring

declarations

2. To detect if new neighboring

declarations should be added

3. to analyze ping pong effect within UTRAN

CTn traces are activated through the WMS call trace wizard, afterwards UTRAN

collects CTn data and sends these data to WMS. WMS then collect and mediates the

information in XML format. WQA then regularly polls the CTn data out of WMS and

computes the necessary information. Users can have access to the neighboring

tuning information though the pre-defined reports proposed.

Utran Report Definitions

Soft & Softer HO Matrix Detect unused links during Soft & Softer HO

Soft & Softer HO failure

cause Matrix

Insight of Soft & Softer handover failure causes

HSDPA HO Matrix Enables to detect unused neighbor links when HSxPA

HO

IF-HO Matrix Detects unused neighbor links when IF-HO

2G / 3G & 3G / 2G Matrix Detects unused neighbor links when inter RAT HO

Summary report Present all important information of previous reports

WMS

WPSWQA

Stat isticsComputation

Optimization

Cycle





7.4.2 CFT - Call Failure analysis

This feature WQA module allows optimization of the radio network quality. CFT and

WQA allows to reduce number of call failures in the UTRAN.

Whenever a Call failure occurs in a CTg zone, the RNC dumps call information. The

Call failure information is then uploaded from RNC to WQA through WMS for volume

analysis.

A top down approach is proposed: from the bulk list of call failure, the system allows

to pinpoint the major cause of Call failures in the system, through analysis of call

failure statistics (filtered by geographical zone, time period and Call failure

information).

The information available will be the following ones:

Call drop parameter detailed view

• High Level View

• Top N cell with most call failure

Presentation of distributions

• Call drop evolutions per cell/neighbor /RAB…

• Distribution of Drops per Radio Conditions

• Drop evolution per mobile identity (IMSI/IMEI/TMSI/P-TMSI…)

• Drop evolution per cause (RRC/RANAP/NBAP/RNSAP…)

Navigation

• direct link for presentation of distributions

• Pre defined according to most common use cases – build on engineering

know how

Export

• Different formats: XL, CSV, PDF, …

• “Call drop list” report defined on purpose





7.4.3 CTx - Radio Coverage Analysis

With this feature, users can analyze details of radio characteristics of the network,

represented by statistical distributions of radio characteristics of calls captured in

CTb & CTg call trace sessions.

1- Automated and assisted Call trace importation

2- KPi calculation

• Simple distribution of Ec/N0 & RSCP

- Number sample for each bin of information on cell basis

• Combined distributions :

- Ec/N0 versus RSCP per cell / per primary cell

- EC/N0 per cell versus active cells / best monitored / best detected…

3- Distribution mgt

• Presentation : tables and graphs

• Probability calculation

• Export to different format





7.5 Radio Frequency Optimizer – Per call Trace Analysis

The Radio Frequency Optimizer product includes sophisticated modules to perform

Call Trace analysis, play back calls and decode messages. RFO provides powerful

means to analyze the Alcatel-Lucent UTRAN RF network performance and support

troubleshooting activities.

The Radio Frequency Optimizer, has been developed for WCDMA engineering teams

since 5 years. RFO functionality has been driven by WCDMA engineering teams, and

it had good success within this community.

RFO is a complete application managing “Per call” trace analysis.

Traces (CTa, CTb, CTg, OTCell, OTIuCS, OTIuPS) are activated on the RNC from WMS

Call Trace wizard. Once generated by RNC, traces are collected by WMS and

mediated to XML format.

At this point RFO is able to fetch the traces XML files for parsing and analysis. RFO

takes traces from WMS, and allows detailed analysis of the call traced.

WMS

RFO

(Cell 1 - C ell 2 )

0,00%

0,50%

1,00%

1,50%

2,00%

2,50%

3,00%

3,50%

-35 -25 -15 -5 5 15 25 35 45 55

C/I (dB)

per

cen

tag

e t

otal

in

terf

ere

nce

0,00%

10,00%

20,00%

30,00%

40,00%

50,00%

60,00%

70,00%

80,00%

90,00%

100,00%

cu

mu

lati

ve d

istr

ibu

tio

n

Per Call trace analysis

UTRAN

FM

CM

SM

PM

Call Traceactivation

Call TraceMediation

& Collection





Functionalities that can be provided by RFO for CT analysis are:

• Protocol analysis like functions

- Call flow (Message view)

- Message decoding

- Data Flow Diagram

- statistics on messaging

- One Shot hexadecimal decoding

• Per call statistics

- Call KPI computation

- Call KPI presentation – tabular and graphical





7.6 Operational Performance Mgt

7.6.1 Alarms On Threshold

The engineering teams of operators associate with the raw counters and basic KPIs

threshold rulesets and conditions to monitor overall health of the network in almost

Near-Time. Upon violation of these conditions the authorized users are notified

through e-mail, paging, or alarms of the degradation of the performance of the

network and their root causes.

This functionality is available trough a services request to implement specific

synthetic counters and associated alarms.

These alarms/events are propagated to NSP fault platform and integrated within its

Trouble Ticketing system.

WMS Fault GUI provides an alert icon that appears when a performance threshold has

been crossed. When an alert icon is presented, the user can easily determine the

problem by viewing the details of the alerts in the Graphical Browser.





8 SECURITY MANAGEMENT

The WMS solution provides comprehensive integrated security management

capabilities covering the following key functions.

WMS System Security

• Security Vulnerability Assessment Process and OS Hardening

• IP Filters implemented on WMS servers

• Optional SSL (for session credential protection) or IPSec encryption (for

encryption of the whole traffic, with deployment of an IPSec Gateway in

front of WMS servers) between WMS Clients and WMS Servers

• Support of SSH on WMS servers

• Password Storage Encryption

• Centralized Security Log Auditing

• Single Sign-on (SSO) ready architecture for the various WMS applications and

the UTRAN NEs that can support SSO

Centralized User Management

• Centralized User Administration within the embedded WMS LDAP directory

• Centralized User Authentication and Authorization (Role and Rule

Management)

• Access Control, including UTRAN Configuration Management access control

with the Role and Task Perimeter feature

• Password and Accounts Security Policy, Configurable Login Banner

• User Session Management console

• External LDAP interface for delegation of user identity management to

external LDAP system. Provided through a Professional service

WMS Security for UTRAN Access NE

• Support of RADIUS Authentication for access to the RNC and the Node B

(xCCM based Node B)

• Support of IPSec for RNC OAM traffic protection





8.1 WMS System Security

8.1.1 Security Vulnerability Assessment Process

As part of the WMS software server software production cycle, a Security

Vulnerability Assessment is performed using the NESSUS scanning tool.

The NESSUS scan identifies the open ports on the WMS servers and the potential

vulnerabilities.

OS and application level vulnerabilities identified are analyzed to eliminate false

positives. Actual vulnerabilities are identified, analyzed, and fixed appropriately.

8.1.2 OS Hardening

The objective of OS hardening is to disable unused operating system processes,

unused ports, and network services that are not required by WMS solution.

• Disable unused services: Some services are enabled by default when

installing Solaris OS. These services pose potential security risks. Disabling

services that are not required by WMS solution strengthens security on the

servers. For example the OS hardening disables potentially exploitable

network services from the inetd.conf file and unused services from the start

up directories (/etc/rc*.d/). These services have known security risks

• Strengthens access control: Limiting and controlling access to the servers is

an important aspect of security. The OS hardening limits access to the root

user on the system console. Users that require root access from a remote

location to a server must log in to the server with their own login credentials

and then switch user (su) to the root user. Such restriction will force the

system to create an entry in the system logs that is useful investigating

security breaches. In addition the File Transfer Protocol (FTP) is a non

secure protocol which allows data to be exposed over the network. The OS

hardening limits access to the FTP service to users that absolutely need this

service. This limits the risk of having unauthorized personnel access the data

being transmitted by FTP

• Increases logging and monitoring Logs: System and application logs provide

valuable indications on intrusion attempts, abnormal behaviors, and many

other suspicious activities. Some basic level of logging is enabled by default

when the Solaris operating environment software is installed. For example,

the syslog file is enabled. The Solaris OS includes a logging application called

the Sun’s Basic Security Model (BSM) which captures security events on the

server and sends the audit logs to the WMS base logging services. Other

logging utilities such as auditing can be used to increase logging.





8.1.3 IP Filters on WMS Servers

The WMS solution includes an IP packet filtering utility called IP Filters. It provides

packet filtering by IP address, port, protocol, network interface, and traffic

direction.

It is configured using a simple rule language. It provides simple command line tools

for administration, including tools to load rules into the kernel, do monitoring,

logging, test, and statistics. A default rules file is provided per server which includes

rules to address common vulnerabilities (e.g. IP fragmenting and TCP SYN flooding).

The solution restricts also access to “weak services” and blocks “Local Ports” which

are the ports used only within WMS server that to not need to be exposed to external

applications.

8.1.4 WMS SSL Support

The SSL security protocol provides data encryption, server authentication, message

integrity, and optional client authentication for a TCP/IP connection at the transport

layer (layer 4). The WMS solution supports the SSL protocol to ensure confidentiality

of the authentication security credentials for:

• The WMS Client desktop to server interface

• The Historical Fault Browser application

SSL is not activated by default, the WMS solution provides procedures to optionally

activate SSL using trusted certificates provided by the customer from their desired

certificate authority.

Please note that only the authentication security credentials are made confidential,

other information over the connection is not encrypted.

8.1.5 SSH on WMS Servers

The WMS solution supports the deployment of SSH daemons (client and server) on

the WMS Main and Performance Servers.

This allows the OAM operators to (optionally) manually use SSH commands ssh and

sftp, instead of telnet and ftp, for secure OAM communications between the OAM

clients and servers, as well as between the OAM servers and the NEs that support

SSH.

The version of SSH supported is SSHv2.

8.1.6 Password storage encryption

The WMS solution provides for the encrypted storage of OAM passwords on the OAM

servers. By ensuring that any OAM passwords that are stored on the OAM servers are

encrypted, this minimizes the vulnerabilities to the OAM system.





8.1.7 Centralized Security Log Auditing

WMS provides a centralized audit trail service that is used by OAM main servers for

centralized storage of security audit logs. All security logs using the centralized

audit trail service are in W3C format. Authentication of WMS users results in security

audit logs being generated.

WMS includes a framework for generating, collecting and viewing logs such as

application logs or security logs.

8.2 Centralized User Management

8.2.1 User Administration

WMS performs user management at the user group (a user group is linked to a Role)

level. Each user group has access to the same network resources within the wireless

network and can perform the same network management functions. System

administrators can subdivide users into a number of user groups based on their

requirements to view resources and perform management tasks. The users are

created using the WMS Authorization Manager User Editor UI.

8.2.2 User Authentication

To ensure that only authorized users can log into the Network Services Platform,

initial launching of the NSP GUI invokes a user log-in procedure: the user is prompted

for a user name and password. The WMS client then authenticates user access to the

User to Role Mapping

User UNIX Attributes

User to Role Mapping

User UNIX Attributes





NSP server. Once the authentication process is complete, the NSP GUI client is

launched. The user then has access to the capabilities and network resources that

have been configured for its user group.

8.2.3 User Authrorization

WMS provides centralized User Authorization capabilities through the Authorization

Manager UI. The Authorization Manager allows to manage roles and associated rules

(set of permissions/privileges for users) and to assign users to roles and map rules to

role.

A set of predefined roles are provided by WMS for:

• Direct access to UTRAN Network Elements. Refer to section 8.3

• UTRAN Configuration Management tasks. Refer to section 8.2.5

The security administrator has the possibility to define additional roles based on

specific OAM user group requirements.

Role Management and Rule to

Role Assignment

Rule Management





8.2.4 Access Control

The Access Control tool allows the system administrator to create, modify and view

user access permissions in order to control the functions users perform and the

access to selected areas of the system based on those functions. Consequently, a

user group can only view and manage their own network resources.

Specific permissions can be given to View, View Alarm Counts, View Alarm Details,

Acknowledge Alarms and/or Manual Clear Alarms for NEs. For layouts, the ability to

View and Edit can be specified. Permissions can also be extended to control the

ability of a group to launch applications. For example, one user group could be

restricted to viewing only NEs in a specific regiona of the UMTS access network and

their associated alarms. Another group could be given this capability, plus the ability

to acknowledge and manually clear alarms on these NEs.

Using these controls, the administrator can effectively partition the network and

control the user’s ability to perform alarm monitoring and management functions on

resources that lie in an assigned area of responsibility. This feature prevents

unauthorized access to network information.

8.2.5 Role and Task Perimeter

The Role and Task Perimeter feature extends the WMS access control capabilities to

the UTRAN Configuration Management tasks. The user administrator has the ability

to allow access control to specific NEs, to specific actions depending on the service

impacts on the network.

Four predefined roles are included:

• No Action / No Modification with No service impact on NE (read only

privileges)

• Action / Modification with No service impact on NE

• Action / Modification with Limited service impact on NE

Per Role Permissions





• Action / Modification with Major Service impact on NE

For each role a set of permissions is provided among a set of rules that are linked to

UTRAN operational actions. Examples of UTRAN operational actions include: NE

creation, NE deletion, NE software download, NE MIB Build, NE parameter change,

etc.

8.2.6 Password and Account Security Policies

WMS supports strong password security management with global password policy

checking capabilities for WMS accounts stored in its centralized directory server. The

password policies supported include:

• Force password change after user creation or password reset by the security

administrator

• Password aging policy

• Password syntax checking and check against the WMS embedded password

dictionary

• Account lockout policy

• Password history avoiding reuse of a password

Password policies support enables operators to increase the level of security for

password management of WMS accounts and to help meet their desired security

policies related to password management.

The login warning text is configurable therefore can be customized as per operator

requirements.





8.2.7 User Session Management

The WMS User Session Management utility allows the security administrator to

monitor active user sessions to the WMS server.

The security administrator has the capability to kill a user session or to kill the

session and lock the user account.

8.2.8 External LDAP Interface

As an optional feature delivered through an Engineering Service, WMS supports an

interface to an external LDAP system for delegation of WMS user Identity

Management to the external LDAP system.

Minimum Length

Password History

Aging Policy

Account Lockout Policy and

Lockout Duration

Change Password after Reset





8.3 Specific WMS Security for UTRAN Access NE

8.3.1 RNC Security

The WMS solution supports security features for access to the Alcatel-Lucent RNC:

• Support of IPSec (with manual or IKE based key management) between the WMS

servers and the RNC

• Support of centralized RADIUS authentication for the RNC

Supporting IPSec to the RNC ensure confidentiality of OAM traffic between the OAM

servers and the network element.

Support of RADIUS to the RNC offer OPEX savings by centralizing the management of

the RNC OAM users.

Role Based Access Control is provided through RADIUS authentication and allows to

centrally manage the level of permissions assigned to RNC OAM users. Five default

roles for direct access to network elements are provided by WMS: NE Administrator

Role, NE Read-Write Role, NE Provisioning Role, NE Maintenance Role, NE Read Only

Role.

8.3.2 NodeB Security

The WMS solution supports RADIUS authentication for access to the Alcatel-Lucent

iBTS.

Support of RADIUS to the BTS offer OPEX savings by centralizing the management of

the RNC OAM users.

Role Based Access Control is provided through RADIUS authentication and allows to

centrally manage the level of permissions assigned to RNC OAM users. Five default

roles for direct access to network elements are provided by WMS: NE Administrator

Role, NE Read-Write Role, NE Provisioning Role, NE Maintenance Role, NE Read Only

1

W-NMSMain

Server

User X

9370 RNC

Authorize User X ?

LDAP databaseUser X --> R/W role

RequestAccess

Read-Write OK

Read-Write OK





Role. For the iBTS the first four roles are mapped to BTS administrator privileges

while the NE Read Only Role is mapped to BTS read only privileges.

RNC

Maintenance staff on Node RNC site

WMS User

SSH

Mainserver

Radius Agent

SunOne

IPsec IKE tunnel

RNC & NodeB:Configurable

Login

Banner

Node B

Maintenance staff on Node

B site

WMS User

Mainserver

Radius Agent

SunOne

RNC & NodeB: User central authentication

through Radius

RNC : IPSec Management

Traffic Protection

RNC : Support SSH as a secure

alternative to

Telnet





9 INTERFACES

9.1 Overview

The WMS solution offers 3GPP OAM standards compliant interfaces to allow customer

OSSes to manage the Alcatel-Lucent UMTS networks. The 3GPP compliant ITF-N

interfaces are based on the 3GPP R6 standards, and the solutions offered include

support for the Alarm IRP, the BasicCM IRP, the BulkCM IRP, as well as support of

XML transfer of 3G performance counters.

In addition to standard 3GPP interfaces compliancy, WMS provides other interfaces

for integration into a centralized Backup and Restore solution, to a Health

monitoring system, to Inventory solution, etc.

9.2 Fault Management Interfaces

3GPP Fault Management

Wireless Management System provides a single integrated OSS interface for fault

management of UMTS networks.

The 3GPP FM solution within WMS is an open, standards based solution, compliant to

the UMTS 3GPP R6 OAM standards (32.111 series), and offers the CORBA solution set.

WMS

FM 3GPP R6

PM XML 3GPP R5

CM Bulk 3GPP R6

Inventory Mgt

Server of Client

LDAP users/Pwd

B&R

Sys Mgt

3G-3G

HP Temip,

Micromuse ValentCramer

C itr ix

Metaframe

Veritas

Netbackup

Tivoli

TECiPlanner

N

S

W E2G-3G

CM XML

PM OSS

WQA NPOWPS

Cell Planning

Reports

Reports

WMS2G

OMC-R

SDA

Reports

NE

FM CM PM IT





As defined in the standards, the WMS 3GPP FM solution offers CORBA interfaces to

allow fault OSSes to do alarm queries, as well as receive event notifications.

This 3GPP FM solution acts as the single point of contact, to provide integrated

alarm management for the entire wireless network.

The 3GPP R6 solution set also offers the ability to monitor the health of the logical

connection between itself and the Alarm IRP Agent, replacing the previous Alcatel-

Lucent vendor specific heartbeat notification service over the Alarm IRP.

Trouble Ticketing

Refer to Trouble Ticketing section 5.9

Alarm on performance threshold

Refer to section 7.6.1.

9.3 Configuration Management Interfaces

3GPP Basic CM

Wireless Management System provides an integrated OSS interface 3GPP compliant

BasicCM, otherwise known as the BasicCM IRP.

The solution for this release is compliant to the 3GPP R6 BasicCM series

specifications.

The BasicCM capabilities can be described as offering Passive CM capabilities,

whereby the standards have defined the ability to query objects and their attributes,

but not to modify objects and their attributes.

The WMS solution implements and complies with the CORBA solution set as defined

in the 3GPP OAM standards. The solution supports the set of operations defined in

the standards, including for example, the ability to retrieve information about

network objects and their attributes, as defined in the standards.

As defined in the standards, the usage of this BasicCM solution capability relies upon

the support of the 3GPP standards defined Notification IRP, to allow the 3GPP OAM

clients to subscribe to notifications of the supported network objects.

3GPP Bulk CM (Utran)

Wireless Management System provides an integrated solution for 3GPP OAM

compliant BulkCM interface, otherwise known as the BulkCM IRP.

The solution for this release is compliant to the 3GPP 32.61X series specifications.

In this release of the 3GPP standards, the BulkCM capabilities supports bulk

configuration of the UMTS OAM standards based RF Parameters, for UTRAN devices

only.

The WMS solution implements and complies with the CORBA solution set, as well as

ftp and XML protocols where required, for the applicable solution requirements of

the BulkCM ITF-N.





CM XML

Refer to CM XML section 6.2.1

WICL

Refer to WICL section 6.2.4.

9.4 Performance Management Interfaces

3GPP PM XML

Wireless Management System provides an integrated solution for 3GPP OAM

compliant XML file format usage for 3GPP performance data.

The solution for this release is compliant to the 3GPP R5 32.401 specifications,

which specifies the requirements for the file formats of performance data

transferred between the OAM system and an OSS system for performance.

In the WMS solution for performance, any and all of the 3GPP performance data is

collected and gathered onto the main Server. From the Main server, the

performance data that is transferred to other systems (such as 3GPP compliant OSS

systems for performance) complies with the XML file format as defined in the 3GPP

standards.

The solution for this release is also compliant to a subset of 3GPP R5 32.403

specifications, which details the set of counters supported for UMTS networks.

Refer to Performance Management Gateway section 7.2.

9.5 Inventory Management Interface

WMS provides an Inventory external interface to allow customer to use an Inventory

management system. The NM is defined as the upstream inventory management

system. Inventory management is the management of field-replaceable units to

facilitate physical maintenance and spares management. Note that this refers to all

active components of network elements (active components are boards, entities,

etc. that can be detected and reported by the network element).

Inventory covers the Access NEs managed by WMS and distinct the various NE sub-

type in the XML result file.

The interface is providing the following functions:

• Bulk upload of inventory

• Time stamp (date of last modification) for some NE

• XML inventory file





MS-PORTAL

WMS

GSM UMTS

Interface with

MS-Portal

MS-SUP MS-NPO

OMC-R

9.6 Network Element Interfaces

The southbound interfaces from WMS to the BTS and the RNC are based on

proprietary protocol called SE/PE - ASN.1 and FMIP - CDL.

9.7 Security Management Interfaces

External LDAP Interface

Refer to section 8.2.8

9.8 Interface to MS-Portal

The aim of the Multi-Standard OMC Portal is to provide a modular solution for

building a Multi-Standard OMC in cooperation with the existing technology-dedicated

Alcatel-Lucent OMC-Rs (GSM and UMTS OMC-Rs).

For this purpose, MS-Portal is offering a unique user access point for a set of

incorporated OMCs and the integration of technology independent functions of GSM

and UMTS OMC-Rs in central software application. This single access point allows

accessing the multi-standard desktop and windows offering multi-standard O&M

functions.

The MS-OMC Portal user interface allows the operator

• To access to multi-standard software O&M applications

• To navigate to the existing OMC-R windows for technology-dependent

functions.

This product includes multi-standard software applications in all domains where the

multi-standard dimension is relevant:





UMTS Access

WMS

2G OMC-R

GSM

WMS 2G OMC-R

Update/delete

2G or 3G

neighboring

Updated/deleted

3G cell

Updated/deleted

2G cell

3G/2G

E/W interface

3G/3G

E/W interface

• Common alarm and supervision management

• Common Quality Of Service monitoring application

• Common security management features

The synergy gained from these multi-standard O&M functions drastically reduces the

Operating Costs (OPEX) of multi-standard networks. For example, a single team is

able to supervise simultaneously the Alcatel-Lucent GSM and UMTS radio access

networks and to optimize parameters between GSM and UMTS layers.

9.9 East-West Interface

WMS solution offers customer an East/West interface between the main server and

Alcatel 2G OMC and others WMS. It allows keeping synchronized data managed by

other 2G or 3G Alcatel-Lucent OMCs. It is an integrated interface on WMS to:

• delete and update 2G neighboring cells coming from 2G Alcatel OMC,

• to delete and update 3G neighboring cells coming from WMS,

• to generate 3G cells list and make it available on related WMS for other

WMS.

Automatic data collection of 2G neighboring cells and 3G neighboring cells is

performed through East-West Interface to neighboring 2G OMC and WMS.

Data Publication is done automatically to make 3G cells list available for 2G OMC

and WMS.

Related work-orders to delete and update 2G/3G neighboring cells are automatically

produced and made available to be activated automatically or not with the

Activation Manager.





10 SYSTEM

From a hardware standpoint, a WMS (regional or national) operating centre consists

of:

• 1 (or 2) Main Server(s): this SUNTM server is responsible for all FC(A)Ps

functionalities. A distributed architecture is implemented in the WMS Server,

allowing to deploy an optional Secondary Server to increase the capacity of

the WMS operating centre

• Clients: WindowsTM PCs are used to run client applications. A user from a

client station, once authenticated, is granted a certain level of management

capabilities across Network Elements (NEs) that are remotely attached to

the WMS servers of the operation center

• Optional PCs for WPS: this application permits off-line configuration

management of network planning work-orders

• 1 optional NPO Server: this Sun server is responsible for the post-processing

of PM counters.

• 1 optional WQA Server: this Windows-based server is responsible for the

post-processing of some Call Traces to support decision-making in the field

of network parameter tuning

• Optional PCs for RFO: this application runs on PCs and is the module to

analyze/screen all Call Trace sessions.

The middleware between the servers and between the clients / servers is CORBA-

based. Most of client GUI’s are coded in Java.

The servers are physically connected to an IP router with 2 or 3 1000baseT Ethernet

redundant IPMP links.

In order to scale to various network sizes, three WMS hardware configurations have

been defined:

• SUNTM Netra 240 servers are intended for the management of small Utran

networks, up to 150 BTS / 900 cells (on a single WMS server)

• SUNTM SF V890 servers are intended for the management of up to 700 BTS /

4200 cells (on a single WMS server)

• SUNTM SF E4900 servers are intended for the management of large networks,

up to 3000 BTS / 18000 cells (on a single WMS server)

Please refer to [R1] to get more details on:

* WMS hardware and ROC configuration

* System management capabilities

* System performances, capacities





* Administration utilities (software upgrade, patch applications, etc.)

* Backup & restore capabilities

* 3rd party software list





11 ABBREVIATIONS AND DEFINITIONS

11.1 Abbreviations

2G 2nd generation: GSM, GPRS

3G 3rd generation: UMTS

AAA Authentication, Authorization and Accounting

ADI ASCII Data Interface

API Access Data Interface

ATM Asynchronous Transfer Mode

CLI Command Line Interface

CM Configuration Management

CORBA Common Object Request Broker Architecture

CPU Central Processing Unit

DA Device Adapter

DHCP Dynamic Host Configuration Protocol

DNS Domain Name Server

EM Element Manager

FM Fault Management

FMBB Fault Management Building Block

GIS Geographic Information system

GUI Graphical User Interface

HFB Historical Fault Browser

LAN Local Area Network

MDM Multi-service Data Manager

MSS Multiservice Switch (previously known as Passport)

NDS Netscape Directory Server

NIMS Network Information Management System

NOC National Operation Centre

NSP Network Services Platform

OAM Operation, Administration and Maintenance





PM Performance Management

PSTN Public Switched Telephone Network

QoS Quality of Service

ROC Regional Operation Centre

RNC Radio Network Controller

RRM Radio Resource Measurement

SNMP Simple Network Management Protocol

SUMBB SUMmary Building Block

TMS Trouble Management System

TUMSBB Topology Universal Modeling Service Building Block

UMTS Universal Mobile Telecommunication System

UTRAN UMTS Terrestrial Radio Access Network

VPN Virtual Private Network

WAN Wide Area Network

WICL Wireless Internet Command Language

WMS Wireless Management System

WPS Wireless Provisioning System

XML eXtended Mark-up Language

11.2 Definitions

ACCESS NETWORK: provides radio access to Packet and Voice core network via the

RNC. A RNC controls multiple NodeBs.

CORE NETWORK: the Core Network is logically divided into CS domain and PS

domain which differ by the way they support traffic. The main entities common to

the CS and PS domains are: HLR/VLR.

VOICE CORE NETWORK: the Voice Core Network supports the CS domain. The main

entities specific to the CS domain are: MSC, HLR, MGW, IWF.

PACKET CORE NETWORK: the Packet Core Network supports the PS domain. The

main entities specific to the PS domain are: SGSN, GGSN.

Wms Cpo Oam06

Documents

Transcript of Wms Cpo Oam06