Professional Documents
Culture Documents
December 2008
UMT/OAM /INF/000005
W-CDMA OAM CPO DECEMBER 2008
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
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
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
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.
• Performance Management
• Interfaces
• Security Management
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
3 SOLUTION POSITIONING
• 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.
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.
BML
Business
3rd Parties
SML
Service
Industry-leading Partners
Network
NML
Sub-Network
Wireless
ALU
Management
Element
EML
System Other
Vendors
Other
Vendors
RAN ATM / IP
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:
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.
• Integrated fault management across radio access and some ATM backbone
nodes.
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.
Presentation
Layer GUI Clients
CORBA
Application Servers/Contract
FM BB TUMSBB OtherBB
Layer Interfaces (Building
Blocks)
CORBA
Mediation Device
Layer DA DA DA Adaptors
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.
• Easily navigate large Wireless networks to find relevant network resources via a
“point and click” interface
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 Network Banner, which provides an “always on” summary of active alarms
in the network.
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).
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).
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:
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.
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.
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).
• 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.
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.
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 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.
• 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.
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.
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.
• 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.
Max. Load (100%) 75% Load 50% Load Min. Load (25%)
• 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.
• 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
With such new capability, the display of the network is simplified and easier to
manage.
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.
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.
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.
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.
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.
• 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.
• 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.
• Auto-Acknowledge - Changes
alarm status to acknowledge
for alarms that match the rule criteria.
• Alarm Specific tab: Notification ID, Alarm Type, Severity, Time Raised,
Threshold Crossing
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.
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.
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.
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.
Alcatel-Lucent – Proprietary UMT/OAM/INF/000005 - 34 / 99
See Notice on Page 2 V06.03 December 2008
W-CDMA OAM CPO DECEMBER 2008
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).
• Reporting
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.
Display of logical
object tree of the NE Display of physical
boards of the NE
Representation of
NodeBs under RNC
Representation of
states with icons
Display of detailed
parameter setting
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 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.
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.
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.
On the iBTS side, the GUI provides BBU usage for each CEM board.
OVSF tree
The GUI provides the common channel status for the selected localcellId.
• Operational State
• Administrative State
• Usage Status
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:
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
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.
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
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.
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.
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.
XML
The CM XML intends to be a generic framework for data exchange work-orders
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.
XML
WMS exports XML snapshots: those files provide a flat XML interface
description of the actual configuration of the network. Snapshots
can be filtered, as the WMS provides ability to export the whole
XML
network, an RNS, one or several Network Elements. They can be
snapshot
scoped to a particular data type:
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.
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.
- 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.
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.
WO
WO
Current View
Current
Workorde WO
r
WO
WO
Initial Snapshot
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.
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
Component editor – for quick visualization and parameter update, sorting capability
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.
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.
Finally, the tabular editor offers the possibility to perform a global comparison
against a template. Discrepancies are highlighted in yellow.
Alcatel-Lucent – Proprietary UMT/OAM/INF/000005 - 49 / 99
See Notice on Page 2 V06.03 December 2008
W-CDMA OAM CPO DECEMBER 2008
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.
Users can build their own user profile by selecting the checks they are interested in
and save them in the application.
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.
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.
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”.
Alcatel-Lucent – Proprietary UMT/OAM/INF/000005 - 52 / 99
See Notice on Page 2 V06.03 December 2008
W-CDMA OAM CPO DECEMBER 2008
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.
• Object discovery
• Object manipulation:
• Delay a command
• UTRAN operations:
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.
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.
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.
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.
• RNC
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.
Task-oriented wizards are available for all network elements and interfaces covered
by the tool:
• Iub interface
• Iur interface
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:
• 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.
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.
Identifier
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…)
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.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.
Three tools are provided for software download to the UTRAN. These cover Node Bs,
RNC C Nodes and RNC I/A Nodes respectively.
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.
Command manager
window displays
download to NE with
individual progress bar
User selects
the action
NodeB RNC
The WMS assistant performs the necessary controls in order to ensure a smooth
upgrade and prevent any operator error.
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.
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.
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.
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.
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.
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
- Alarms on threshold
• Engineering Performance Mgt
The following figure depicts the architecture the PM solution and how it is can be
integrated in an overall OSS system:
Performance Portal
Reporting
– Alcatel-Lucent wireless
Access network reporting
Focused Interface
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.
Trace types
• CTa
- 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.
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
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).
• 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.
- On a NE or a list of NEs or
- On a network interface or a list of network interfaces
When the Call Failure Trace (CFT) is activated the RNC logs a snapshot for all
the call drops that occur on the configured area.
Collected data
• 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.
• 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)
• User Efficiency :
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.
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.
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.
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.
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)
18
16
14
12
10
8
6
Q=3 L
4 F
2
P=12
0
1 2 3 4 5 6 7 8 9 10 11 12
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.
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.
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.
Soft & Softer HO Matrix Detect unused links during Soft & Softer HO
Soft & Softer HO failure Insight of Soft & Softer handover failure causes
cause Matrix
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).
Presentation of distributions
Navigation
Export
2- KPi calculation
• Combined distributions :
3- Distribution mgt
• Probability calculation
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.
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.
RFO
Per Call trace analysis
(Cell 1 - C ell 2 )
3,50% 100,00%
90,00%
3,00%
80,00%
c u m u l ati ve d i st r ib u ti o n
2,50% 70,00%
p er c en t ag e t ot al
i nt er f er e nc e
60,00%
2,00%
50,00%
1,50%
40,00%
1,00% 30,00%
20,00%
0,50%
10,00%
0,00% 0,00%
-35 -25 -15 -5 5 15 25 35 45 55
C /I (dB)
FM
WMS Call Trace
CM Call Trace Mediation
SM activation & Collection
PM
UTRAN
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
• Single Sign-on (SSO) ready architecture for the various WMS applications and
the UTRAN NEs that can support SSO
• Support of RADIUS Authentication for access to the RNC and the Node B
(xCCM based Node B)
The NESSUS scan identifies the open ports on the WMS servers and the potential
vulnerabilities.
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.
• 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.
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.
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.
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.
WMS includes a framework for generating, collecting and viewing logs such as
application logs or security logs.
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.
Rule Management
The security administrator has the possibility to define additional roles based on
specific OAM user group requirements.
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.
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.
• Force password change after user creation or password reset by the security
administrator
• Password syntax checking and check against the WMS embedded password
dictionary
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.
Minimum Length
Password History
Account Lockout Policy and
Lockout Duration
Aging Policy
The security administrator has the capability to kill a user session or to kill the
session and lock the user account.
• Support of IPSec (with manual or IKE based key management) between the WMS
servers and the RNC
Request
Access Aut
ho
Use rize
rX
User X ?
Read-Write OK Rea
d -W
9370 RNC rite
OK
LDAP database
User X --> R/W role
W-NMS
Main
Server
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.
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
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.
Main
server
SunOne
Maintenance
WMS User Radius
Agent staff on Node
B site
Node B
Main
server
SSH
IPsec IKE tunnel
Radius
Agent Maintenance
WMS User SunOne
staff on Node
RNC site
RNC : IPSec Management RNC
Traffic Protection
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.
CM Bulk 3GPP R6
PM XML 3GPP R5
LDA P users/Pwd
Reports
S erv er of Client
Report s
Report s
Inventory Mgt
FM 3GPP R6
CM XML
Sys Mgt
B&R
WPS W QA NPO SDA
FM CM PM IT
N
2G
OMC-R
2G- 3G W WMS E 3G-3G W MS
S
NE
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.
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
The solution for this release is compliant to the 3GPP R6 BasicCM series
specifications.
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.
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
WICL
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.
Inventory covers the Access NEs managed by WMS and distinct the various NE sub-
type in the XML result file.
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.
MS-PORTAL
MS-SUP MS-NPO
Interface with
MS-Portal
OMC-R WMS
GSM UMTS
This product includes multi-standard software applications in all domains where the
multi-standard dimension is relevant:
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.
• to generate 3G cells list and make it available on related WMS for other
WMS.
3G/3G
2G OMC-R E/W interface
WMS WMS
3G/2G
E/W interface
Update/delete
2G or 3G Updated/deleted
2G OMC-R neighboring 3G cell
Updated/deleted
2G cell UMTS
GSM Access
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
• 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.
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)
11.1 Abbreviations
2G 2nd generation: GSM, GPRS
CM Configuration Management
DA Device Adapter
EM Element Manager
FM Fault Management
PM Performance Management
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.