WCDMA RAN O&M General

Operation and Maintenance
WCDMA RAN
USER DESCRIPTION
Copyright
© Ericsson AB 2005 – All Rights Reserved
Disclaimer
No part of this document may be reproduced in any form without the written
permission of the copyright owner.
The contents of this document are subject to revision without notice due to
continued progress in methodology, design, and manufacturing. Ericsson
shall have no liability for any error or damages of any kind resulting from the
use of this document.
Trademark List
Citrix® MetaFrame is a trademark of Citrix Systems, Inc.

XP™a Version 1.0
FeatureRelease 2
72/1553-HSD 101 02/4 Uen A 2005-09-06

Contents
1 Introduction 1
1.1 Scope 1
1.2 Target Groups 1
1.3 Revision Information 2
2 O&M Overview 3
2.1 WCDMA RAN 3
2.2 O&M Architecture 4
2.2.1 O&M Fundamentals 4
2.2.2 O&M Activities 6
3 O&M Systems 9
3.1 O&M Intranet 9
3.1.1 Remote Access to RNC, RXI, and RBS 9
3.1.2 O&M Infrastructure 11
3.2 OSS-RC 13
3.2.1 OSS-RC Functions 13
3.2.2 WCDMA RAN Explorer 15
3.2.3 OSS Network Explorer 16
3.2.4 Interface to NMS 16
3.3 Element Management 16
3.3.1 Element Management Functions 17
3.3.2 Using NE EMs 17
3.3.3 RNC EM 17
3.3.4 RXI EM 18
3.3.5 RBS EM 19
4 Fault Management 21
4.1 General Information 21
4.2 Fault Handling 23
4.3 Alarm Handling 25
4.4 FM Event Handling 25
4.4.1 Generating O&M Events 25
4.4.2 Viewing Logs 26
4.5 Test Functions 26
5 Configuration Management 27
5.1 Configuration Management Categories 27
5.2 Equipment Handling 29
72/1553-HSD 101 02/4 Uen A 2005-09-06

5.2.1 Background 29
5.2.2 Adding a New RBS 29
5.2.3 Adding a New RNC 30
5.2.4 Product Inventory 30
5.3 Transport Network Configuration 31
5.4 Radio Network Configuration 32
5.5 Software Management 33
5.5.1 Software Installation 33
5.5.2 Software Upgrades 34
5.5.3 Configuration Backup and Restore 34
5.5.4 OSS-RC Backup and Restore 35
6 Performance Management 37
6.1 Performance Management Functions 37
6.2 Performance Statistics 38
6.2.1 General 38
6.2.2 Counter Formats 39
6.2.3 Measurement Administration 40
6.2.4 Counters 40
6.3 Performance Recording 40
6.3.1 UETR 41
6.3.2 CTR 42
6.3.3 PM Recording Administration 42
6.4 GPEH 43
6.4.1 RBS Node-internal Events 44
6.4.2 RNC Node-internal Events 44
6.4.3 RNC Inter-node Events 44
6.4.4 GPEH Administration 44
7 Security Management 47
7.1 General 47
7.2 Security Management Functionality 47
8 Glossary 49
Reference List 51
72/1553-HSD 101 02/4 Uen A 2005-09-06

1 Introduction
This document describes the Operation and Maintenance (O&M) system for
Ericsson Wideband Code Division Multiple Access (WCDMA) Radio Access
Network (RAN).
For more information about the WCDMA RAN product, see Reference [8].
1.1 Scope
This document describes the main principles for O&M of the WCDMA RAN.
This includes principles for:
• Operation Support System — Radio and Core (OSS-RC)
• Element Manager (EM) for the Radio Network Controller (RNC)
• EM for Radio Base Station (RBS)
• EM for RXI. RXI is an Ericsson CPP-based node that implements ATM

aggregarion as well as IP routing functionality. See glossary Reference [4]
for more information
Furthermore this document describes the architecture, operation, and

functionality of the O&M system. In particular, it describes the use of the
different management applications and user interfaces to perform:
• Fault Management
• Configuration Management
• Performance Management
• Security Management
For information about abbreviations and terms used in this document, see
Reference [4].
1.2 Target Groups

This description is written for the following group of personnel: a general
audience interested in an overall understanding of the principles for managing
and operating WCDMA RAN.
Personnel working on Ericsson products or systems must have the training and
competence required to perform their work correctly.
72/1553-HSD 101 02/4 Uen A 2005-09-06 1

1.3 Revision Information

The revision history for this description is listed in Table 1 on page 2.
Table 1 Revision History

Revi- Reason for Revision
sion
A This document is based on 72/1553–HSD10102/3.
Collected data files remain in OSS-RC for 3 days for statistical
files before being deleted by OSS-RC (the default value was 10
before), see Section 6.2.3 on page 40
Reference [19] is added.
Software Management in OSS-RC is based on Software
Management Organiser (SMO), see Section 5.5 on page 33.
Information about Network Inventory Organiser (NIO) is added in
the product inventory chapter,Section 5.2.4 on page 30
RXI has replaced RANAG in the whole document. See Reference
[4] for defintions of RXI and RANAG.
Chapter 6.3 Performance Recording Section 6.3 on page 40, and
chapter 6.4 GPEH Section 6.4 on page 43 are updated to reflect
new fucntionality. See NIR Reference [20] for detailed information.
References 9,10,11,12 are updated.
2 72/1553-HSD 101 02/4 Uen A 2005-09-06

2 O&M Overview
This section describes the principles, architecture, and functions of the O&M
activities in WCDMA RAN.
2.1 WCDMA RAN

WCDMA RAN is a part of the Ericsson 3rd generation (3G) mobile system,
and comprises:
• OSS-RC
• RNC
• RXI
• RBS
WCDMA RAN has interfaces towards the Core Network (CN), and towards the
external Network Management Systems (NMS).
WCDMA RAN provides Radio Access Bearers (RAB) between the CN and the
subscriber’s User Equipment (UE) for speech, data, and multimedia services.
The Network Elements (NEs) RNC, RXI, and RBS provide and manage the
data links between WCDMA RAN and the UE. The links between the NEs in
WCDMA RAN carry the user data within WCDMA RAN. These physical links
are also used to carry O&M data. See Figure 1 on page 4 for an overview
of WCDMA RAN.
72/1553-HSD 101 02/4 Uen A 2005-09-06 3

Planning
NMS
Tools
CN
WCDMA RAN
RNC OSS-RC
RXI
RBS
O&M Intranet
Transport Network
UE
U 00 00032C
Figure 1 WCDMA RAN Overall Architecture
2.2 O&M Architecture

This section describes basic management principles and types for WCDMA
RAN from the overall network level down to the NE level. WCDMA RAN O&M
solution is based on a combination of an advanced O&M architecture, nodes
with embedded O&M functionality, and O&M tools that collect and maintain
detailed data from all nodes in an Ericsson network.
2.2.1 O&M Fundamentals

WCDMA RAN O&M solution consists of Embedded Element Management in
the NEs, the O&M Intranet, and OSS-RC. They provide full support for O&M
activities on WCDMA RAN. The O&M solution also provides advanced support
for activities requiring specific management. For activities that are technology
and supplier independent, such as alarm presentation and statistics reports,
OSS-RC offers integration to existing systems.
The management system architecture is shown in Figure 2 on page 5.
4 72/1553-HSD 101 02/4 Uen A 2005-09-06

NMS
OSS-RC (4)
RXI
EM
(3)
U 00 00022B
Figure 2 Management System Architecture
The design of the O&M system in WCDMA RAN base on the following
principles. The numbers refer to the numbering in Figure 2 on page 5.
1 Management System Architecture
The Management System Architecture comprises three layers. The

architecture is shown in Figure 2 on page 5.
The top layer is the Network Management Layer. This layer comprises
applications covering specific aspects (for example, Alarm Handling
or trouble ticketing) of all parts of a complete network, regardless of
technology, or vendor of the managed NEs. The layer is responsible for
the management of the complete network, which can consist of multiple
systems, for example 3G and 2nd generation (2G) systems.
The middle layer is the Subnetwork Management Layer. This layer

manages the system (from a top WCDMA RAN level).
The lowest layer is the Element Management Layer. This layer

manages individual RNC, RXI, and RBS nodes.
2 O&M Intranet
All system nodes are interconnected through an Internet Protocol-based

(IP-based) O&M Intranet. This enables all the NEs to be accessed remotely
from any location within the O&M Intranet, and includes the possibility to
72/1553-HSD 101 02/4 Uen A 2005-09-06 5

perform management from a central management location. See Section

3.1 on page 9 for a description of the O&M Intranet.
3 Embedded Element Management
The NEs platforms contain all management applications necessary for

Element Management. Element Management is used to configure the NE’s
hardware and software and to control the nodes’ operation. WCDMA RAN
uses the following applications for Element Management: the RNC EM, RXI
EM, and the RBS EM. The operator can access the EMs from any location
within the O&M Intranet. See Section 3.3 on page 16 for a description
of Element Management functions.
4 OSS-RC
OSS-RC contains online client applications for day-to-day handling of O&M

functions, such as the collection and evaluation of alarms and performance
data. Although OSS-RC is not hosted by RNCs, RXIs or RBSs like the
EMs, the operator can access it from any location within the O&M Intranet.
See Section 3.2 on page 13 for a description of OSS-RC.
2.2.2 O&M Activities

The O&M activities performed in WCDMA RAN can be divided into the following
categories:
• Fault Management
Functions within this area detect and report failures in WCDMA RAN
as soon as they occur and limit their effects. Fault Management brings
additional or redundant equipment into operation, reconfigures existing
equipment or recovers the failure. The applications used for Fault
Management are OSS-RC and the EMs. See Section 4 on page 21 for a
description of Fault Management.
• Configuration Management
Functions within this area set parameters in NEs in the Radio Network
(RN), in the Transport Network (TN) and in the equipment in WCDMA RAN.
The applications used for Configuration Management are OSS-RC and the
EMs. Configuration Management also includes Equipment Handling, that
is, the configuration of equipment (hardware and software) within an NE
based on Ericsson’s Connectivity Packet Platform (CPP). Configuration
Management also comprises Software Management, that is, the handling
of software in the NEs. This includes the installation, upgrade, backup and
restore of RNC, RXI, and RBS node software and configuration data. See
Section 5 on page 27 for a description of Configuration Management.
• Performance Management
Functions within this area monitor the performance of WCDMA RAN and
store the Performance Management data collected from WCDMA RAN
6 72/1553-HSD 101 02/4 Uen A 2005-09-06

in OSS-RC. See Section 6 on page 37 for a description of Performance

Management.
• Security Management
Functions within this area handle and administer security features for
preventing unauthorized access to the management system. Security
Management is achieved by the use of Single-logon servers (SLS),
Persistent Key server (PKS), TSS, etc. See Section 7 on page 47 for a
description of Security Management.
72/1553-HSD 101 02/4 Uen A 2005-09-06 7

8 72/1553-HSD 101 02/4 Uen A 2005-09-06

3 O&M Systems
This section describes how the system nodes use O&M functions. The operator
can perform WCDMA RAN O&M activities in one of the following ways:
• Subnetwork Management actions
These actions require operations on several nodes. This is handled by

OSS-RC, as described in Section 3.2 OSS-RC on page 13 or by an
external NMS.
• Element Management actions
These actions involve a single node. The RNC, RXI, and RBS EMs handle
these actions, as described in Section 3.3 Element Management on page
16.
3.1 O&M Intranet

The O&M Intranet enables the NEs to be controlled remotely using OSS-RC,
the RNC, RXI, and RBS EMs. This means that all O&M activities, such as
Element Management of one or all the nodes in WCDMA RAN, can be
performed anywhere on the O&M Intranet.
3.1.1 Remote Access to RNC, RXI, and RBS

All nodes in the WCDMA RAN O&M system are interconnected through the
O&M Intranet. This is an IP-based network used only for O&M purposes,
for example, downloading new software packages to NEs. The O&M data is
carried on the same physical links as the user data traffic, which means that a
separate physical network is not required for O&M.
In order to prevent un-authorised access to the O&M Intranet, it is recommended

to isolate the O&M Intranet with a firewall. Local access from a NEs site LAN
towards OSS-RC or towards another NEs EM is always done via the security
function in the OSS-RC Application Server (AS).
The O&M Intranet makes it possible to contact any NE in the WCDMA RAN
O&M system, independent of physical location, by logging in to the AS.
The different access alternatives for operating O&M functions in the system
nodes are shown in Figure 3 on page 10.
72/1553-HSD 101 02/4 Uen A 2005-09-06 9

O&M Intranet
1. Operation and
Maintenance
Center 3. Local Access
without
Connection
2. Local
Access
U 00 00014A
Figure 3 Access Alternatives for WCDMA RAN Nodes
The following three alternatives are available for accessing the RAN system
nodes (the numbering refers to the numbers in Figure 3 on page 10):
1 Operation & Maintenance Center
A central site where most O&M tasks are performed. From there, it is
possible to run OSS-RC or the EM for any NE. Access to the O&M Intranet
is authenticated by the Application Server (AS) and the Single Log-in
Server (SLS).
2 Local Access
Connect the thin client to an RNC, RXI, or RBS using the Site LAN (the
RNC, RXI, or RBS must already be connected to the O&M Intranet).
Remote nodes are accessed by first logging into the AS/SLS.
3 Local Access without Connection
Connect to an RNC, RXI, or RBS using the Site LAN. In this case, the NE is
not connected to the O&M Intranet, so it is not possible to access the other
nodes attached to the O&M Intranet.
It is also possible to access the O&M Intranet either over PSTN/ISDN cellular
or over the public Internet. Access through dial in operation or over the public
Internet has obvious and major security implications. This kind of access
should only be deployed after due consideration of the risks incurred and then
only using good Third Party Products (3PP) solutions for secured remote
access that provide strong and satisfactory authentication of the remote user.
However this is not a part of the Ericsson solution and is therefore not described
any further in this document.
10 72/1553-HSD 101 02/4 Uen A 2005-09-06

3.1.2 O&M Infrastructure
To carry and route IP traffic, the O&M Intranet needs to be supported using
equipment such as network routers, switches, and hubs. This is provided in the
OSS-RC product through O&M INfrastructure (OMINF).
The O&M Common Infrastructure consists of the following parts:
• IP Network Applications
• Active Library EXplorer (ALEX). The Active Library Explorer (ALEX) lets the
user browse Ericsson document libraries with a standard web browser.
• Security Functions
• Network Infrastructure
• Backup Solution
Figure 4 on page 11 shows a logical view of the O&M infrastructure.
IP Network ALEX Server

Applications Web server
ALEX server OSS-RC
DHCP DNS
Server
NTP FTP
Security Network
Solution Infrastructure
Application Server O&M router
PKS Network switch Backup
SLS Firewall Service
Backup server
Backup robot
U0000017E
Figure 4 Common O&M Infrastructure (COMINF)
The O&M infrastructure consists of the functions described in Table 2 on page

12:
72/1553-HSD 101 02/4 Uen A 2005-09-06 11

Table 2 O&M Infrastructure Functionality

Servers Function
DHCP Server Dynamic Host Configuration Protocol.
Used only for equipment connected to Site Local
Area Network (LAN) of NEs. By implementing DHCP,
the individual addresses of O&M network nodes
and their associated parameters can be established
dynamically.
DNS Server Domain Name System.
A distributed database used by applications in
WCDMA RAN to map between a domain name and
IP addresses.
NTP Server Network Time Protocol
Synchronizes the clocks within the WCDMA RAN
network. GPS System Clock (GSC) is used as the
NTP time source.
WRAN FTP Server An FTP server is required in WCDMA RAN O&M
Intranet in order to support 3 functions:
• Software installation of Upgrade Packages
• Backup and restore of Configuration Version (CV)
of the networks elements.
• License storage
ALEX Server The Active Library Explorer (ALEX) lets the user
browse Ericsson document libraries with a standard
www browser, for example Netscape Navigator. The
Customer Product Information (CPI) Store holds the
WCDMA RAN system documentation and ALEX
allows a user to browse the CPI Store. The document
libraries reside on a web server, so the documents
are accessible from all workstations connected to
the Web.
PKS Server Public Key Server.
A tool for generating and certifying asymmetric key
pairs used for authentication purposes in the system.
The PKS generates node credentials (key pairs
and certificates) and creates and issues the root,
PKS, and SLS key pair and the root, PKS, and SLS
certificate.
For security reasons it is recommended that PKS is
a stand-alone server, i.e. it should be disconnected
from the O&M network and it should only be
connected for transferring the keys it generates to
the rest of servers.
12 72/1553-HSD 101 02/4 Uen A 2005-09-06

Table 2 O&M Infrastructure Functionality

Servers Function
SLS Server Single Logon Server.
The SLS generates user credentials (asymmetric
key pairs and certificates) that are downloaded to the
security support functions in the client environment.
This allows users to perform Element Management
on multiple WCDMA RAN nodes without entering a
user name and password for each node.
The functionality for Lightweight Directory Access
Protocol (LDAP) is part of the SLS server. The SLS
server runs on a web server.
Application Server A central execution environment for OSS-RC client
(AS) applications used in O&M of WCDMA RAN. The
operator reaches the AS from workstations with help
of a special client using the ICA protocol.
Firewall The firewall function helps prevent attacks on the
O&M Intranet. It does so by reducing the possibilities
for an intruder to mount attacks on nodes in the O&M
Intranet. The firewall shall be configured to allow
wanted traffic and to deny all other traffic.
O&M Router Provides the gateway to the IP over Asynchronous
Transfer Mode (ATM) connected NEs (RNCs, RXIs,
and RBSs).
The O&M Router plays an important part in restricting
IP connectivity in the O&M network for security
purposes.
Backup Server Used by WCDMA RAN nodes for automatic backup
according to a configured schedule.
3.2 OSS-RC
The management and support system OSS-RC is the Subnetwork Manager
(SNM) for WCDMA RAN. OSS-RC supports the day-to-day network O&M
procedures. OSS-RC provides coordinated management capabilities including
full status and properties views of the RNCs, the RXIs, and the RBSs. The
OSS-RC functionality includes alarm status and configuration data viewing,
product searches on all the nodes, and performance monitoring of WCDMA
RAN.
3.2.1 OSS-RC Functions

OSS-RC applications run on the OSS-RC Server. GUIs are provided for ease
of use and are accessed from the OSS-RC server. OSS-RC sends data such
72/1553-HSD 101 02/4 Uen A 2005-09-06 13

as fault notifications or configuration data to the NMS. For an illustration of the

OSS-RC functions, see Figure 5 on page 14.
OSS-RC
GUI
OSS-RC NMS
Server
Alarm Manager
O&M Intranet
Planning
RNC
Tools
Performance
Manager Report
RXI
Generator
RBS RBS
U 00 00003A
Figure 5 OSS-RC principles of operation
To perform the O&M tasks, OSS-RC provides the functions (not complete list)
described in Table 3 on page 14:
Table 3 OSS-RC Functions

Function Description
WCDMA RAN Explorer This function provides a topological
view of all network nodes.
Software Management This function provides remote
Software Installation and Upgrades
to multiple NEs at preset times. It
also provides backup and restore of
CVs.
Product Inventory This function provides a collection
and presentation of inventory
information from the NEs.
RN Configuration This function includes the viewing
and editing RN parameters for
several NEs.
14 72/1553-HSD 101 02/4 Uen A 2005-09-06

Table 3 OSS-RC Functions

TN Configuration This function includes the viewing
and editing TN parameters for
several NEs.
Alarm Mediation This function includes subscription,
viewing and forwarding alarms
generated by the NEs.
Performance Statistics This function provides collection,
administration, storage and
presentation of performance
counters generated by the NEs.
Performance Recording This function provides
administration, collection, and
storage of performance events and
radio environment measurements
generated by the NE.
External Interfaces Interfaces complying with 3GPP,
together with a set of published
interfaces to facilitate integration with
other systems. By using the same
GUI style in OSS-RC and in the
embedded EMs, the WCDMA RAN
O&M solution provides a seamless
way of working with OSS-RC
together with the embedded EMs.
3.2.2 WCDMA RAN Explorer

WCDMA RAN Explorer is the main application for launching WCDMA RAN
specific applications. It is launched from the OSS-RC main portal (OSS Network
Explorer, ONE) and gives a more detailed topological view of the WCDMA RAN,
for viewing the status and properties of all the RNCs, the RXIs, and the RBSs.
The WCDMA RAN Explorer features include the following:
• Import/Export Radio Network Configuration
• Transport Network Configuration
• Consistency
• View Properties
• Log Handling
• Collect Network Element Logs
72/1553-HSD 101 02/4 Uen A 2005-09-06 15

• Node Status Analyser
• Health Check
• Parameter Check
• Cell Availability
• Add RBS Wizard
3.2.3 OSS Network Explorer

ONE is the system portal, that is, the starting point of all O&M applications.
ONE provides access to all the available support activities for O&M in the radio
and core network. ONE also provides an overview of the
• connected radio network objects and their hierarchical relationship
• basic properties of the selected network objects
• system activities available for presentation of information
• system activities to support different tasks
ONE is a GUI that provides a topology overview to the radio and core network,
as well as access to all available applications (for example Fault Managament)
in O&M that are installed. It can be configured which network objects are
visible in the topology tree and which applications can be launched for the
respective network object. Furthermore, users can create personal network
views containing the desired network objects.
The EM for a particular NE can be opened from within OSS-RC through ONE.
3.2.4 Interface to NMS

OSS-RC includes interfaces to other systems. The interface functions includes
the forwarding of fault notifications (alarms) to the NMS and of configuration
data to external planning tools (such as TEMS CellPlanner). OSS-RC supports
standard and open interfaces for easy integration with the NMS.
3.3 Element Management

The O&M system for WCDMA RAN uses the principle of embedded Element
Management. This means that the NEs acts as host locally for all hardware
and software for O&M tasks. Embedded Element Management eliminates the
need for synchronizing management tools and system versions. To access the
management functions, the operator only requires a web browser.
16 72/1553-HSD 101 02/4 Uen A 2005-09-06

3.3.1 Element Management Functions
Element Management configures the different parts of WCDMA RAN using

applications such as the EMs that interact with hardware and embedded
software in the NEs. All O&M functions on a network node, except Performance
Management, can be performed via Element Management. Performance
Management is only accessible via OSS-RC.
The operator uses the EM to configure the RN and TN, together with software
and hardware attributes of the NEs. Element Management is performed using
OSS-RC and/or the RNC, RXI, and RBS EMs. These applications provide a
Java-based GUI that the operator can view with a web browser, which enables
all interaction with the NEs to be performed using the same type of user
interface.
Other Element Management features are:
• O&M Intranet support, using HTTP and other industry standard protocols.
Connection to the web browser computer, for example a PC, is established
via local Ethernet or remote over the O&M Intranet.
• Equipment Handling functions such as lock and unlock of devices and

resources
• Alarm and log handling
3.3.2 Using NE EMs

The RNC, RXI, and RBS EMs provide a GUI for setting the parameters for the
Radio Network, TN and for NE equipment. The RNC, RXI, and RBS EMs are
web-based applications, which can run with the following software:
• Netscape Navigator or Microsoft Internet Explorer
The operator use these web browsers to run the applications and to view
Customer Product Information (CPI).
• FTP server
The FTP server can be required when performing a Software Upgrade

for a node.
3.3.3 RNC EM
The operator uses the RNC EM to view and modify the attributes of the RNC.
The operator opens the application from OSS-RC or by entering the location of
the RNC EM in a web browser.
The RNC EM application is downloaded to the thin client in the form of Java
applets. It can run remotely from anywhere in the O&M Intranet with the RNC
connected to the O&M Intranet. If the RNC is not connected to the O&M
72/1553-HSD 101 02/4 Uen A 2005-09-06 17

Intranet, the RNC EM can run only by connecting the thin client directly to
the RNC (using an Ethernet cable). The RNC EM GUI is shown in Figure 6
on page 18.
Figure 6 Example of RNC EM GUI
For more information about RNC EM, see Reference [2].
3.3.4 RXI EM
The operator uses the RXI 820 ATM EM to view and modify the attributes of
the RXI. The operator opens the application from OSS–RC or by entering the
location of the RXI EM in a web browser.
The RXI EM application is downloaded to the thin client in the form of Java
applets. It can run remotely from anywhere in the O&M Intranet with the RXI
connected to the O&M Intranet. If RXI is not connected to the O&M Intranet, the
RXI EM can run only by connecting the thin client directly to the RXI (using an
Ethernet cable).
The RXI EM GUI is shown in Figure 7 on page 19.
18 72/1553-HSD 101 02/4 Uen A 2005-09-06

Figure 7 Example of RXI EM GUI
For more information about RXI EM, see Reference [5].
3.3.5 RBS EM
The operator uses the RBS EM application to view and modify the attributes of
an RBS. The operator opens the application from OSS–RC or by entering the
location of the RBS EM in a web browser.
The RBS EM application is downloaded to the thin client in the form of Java
applets. It can run remotely with the RBS connected to the O&M Intranet. If
the RBS is not connected to the O&M Intranet, the RBS EM can run only by
connecting the thin client directly to the RBS (using an Ethernet cable). The
RBS EM GUI is shown in Figure 8 on page 20.
72/1553-HSD 101 02/4 Uen A 2005-09-06 19

Figure 8 RBS EM GUI
For more information about RBS EM, see Reference [1].
20 72/1553-HSD 101 02/4 Uen A 2005-09-06

4 Fault Management
This chapter describes WCDMA RAN Fault Management. This comprises the
handling, subscription, and logging of NE alarms and events. If the system
detects faults or malfunctions in a NE (including OSS-RC internally generated
alarms as well), it sends notifications to OSS-RC and the NMS for further action.
4.1 General Information

Fault Management ensures that WCDMA RAN operates correctly and informs
the operator about the faults and actions needed to correct the faults in the
RAN. It does this by for example detecting and isolating faults, by forwarding
alarm and FM event notifications to subscribers like OSS-RC and the NMS. It
also handles the operational state of the resources affected by the fault. See
table 5 for the different functional parts of Fault Management.
Each potential fault in WCDMA RAN is grouped into one of the following
categories, as seen in Table 4 on page 21:
Table 4 Fault Categories

Fault Category Description
Hardware failures The malfunction of some physical
resource within an NE.
Software problems This includes software bugs or
database inconsistencies.
Functional faults A failure in some functional resource
in an NE, where no hardware
component can be found responsible
for the problem.
Overloading Loss of some or all of the
NEs specified capability due to
overloading.
Communication faults A communication failure, for example
between two RNCs or between two
operating systems.
72/1553-HSD 101 02/4 Uen A 2005-09-06 21

WCDMA RAN contains the Fault Management functions described in Table 5

on page 22:
Table 5 Fault Management Functions

Fault Handling The Fault Handling function represents the
lowest level of fault management. It is performed
close to the fault cause location. This function
monitors the system for faults and sends out
an alarm report if it detects a fault. The Fault
Handling function also covers state handling.
The Fault Handling function is further descibed
in Section 4.2 on page 23.
Alarm Handling This function handles any alarms the WCDMA
RAN issues; it maintains a list of active alarms,
distributes the alarms and logs the alarm history.
The Alarm Handling function is further descibed
in Section 4.3 on page 25.
FM Event Handling This function handles Fault Management-related
events; it distributes the FM events and logs the
FM event history. One example of an FM event
is "RNC node restart completed".
The Event and Log Handling function is further
descibed in Section 4.4 on page 25.
Test Functions In addition to the automatic supervision of
functions for monitoring the NE’s while in use,
the operator can request manual tests to verify
specific functions.
The Test Functions are described more in
Section 4.5 on page 26.
22 72/1553-HSD 101 02/4 Uen A 2005-09-06

The Fault Management model is shown in Figure 9 on page 23.
NMS
NMS
Alarm Event
Network Manager Notification Notification
Filtering
OSS-RC
FM RAN
RAN Alarm &
Alarm FM
List Event
Log
Subnetwork Manager
Alarm Event
Notification Notification
RBS/RNC/RXI
Network Element NE NE
Network NE NE
Alarm Handling Alarm Alarm Element FM Availability
List Log Event Log
Event Log
Handling
Element Manager Alarm Alarm Event

Report Report Report
External Alarms Fault Handling
U 00 000118B
Figure 9 Fault Management Model
For more detailed information about Fault Management, see Reference [3].
4.2 Fault Handling

If a fault occurs in WCDMA RAN, the Fault Handling function in the NE sends
notification to the Alarm Handling function.
When a fault occurs, the following events take place:
1 Detection
The system detects faults automatically in the NEs. Test functions typically
interfere with the normal operation of the unit so they have to be performed
while the unit is idle. Supervision functions observe the behavior of the
unit when it is in use. Together they are called fault detection functions.
Detection also includes fault filtering and suppression.
72/1553-HSD 101 02/4 Uen A 2005-09-06 23

2 Localization
The Fault Handling function identifies the faulty unit and includes
information about it in the alarm report.
3 Isolation
Once the Fault Handling function locates the fault, it minimizes the effects
of it through the isolation of the faulty unit by taking it out of service and
setting its operational state to DISABLED.
4 Recovery
If possible, the system is brought back into normal operation. This can
happen if there is a redundant unit available or a resource available
elsewhere. Another typical recovery action is to restart the faulty unit.
This will often bring the unit back into normal operation, even though the
software error can still exist.
5 Reporting
The system generates an alarm and sends it to OSS-RC and also to the
NMS if it subscribes to the alarm.
6 Correction
If the problem is hardware-related, a field technician replaces the faulty

board with new hardware. If the problem is software-related, the faulty
software has to be upgraded. Software errors cannot be corrected at the
site. The first step in the correction process is typically to lock the faulty
unit. It is done by setting the administrative state to LOCKED. This removes
all alarms from the locked unit. When the field technician inserts the new
unit, the fault detection functions automatically verifies it, and the operator
can also verify it further with manual test functions. If the unit is found to be
operating correctly, the operational state changes to ENABLED, and the
operator sets the unit to UNLOCKED.
7 Verification
Different tests and board verifications are performed to ensure that the
problem has been corrected.
8 Restoration
Restoration is typically achieved by unlocking the unit, that is, setting the
administrative state to UNLOCKED. If there are still faults on the unit, the
system issues alarms. Hot repair is also supported. This means that
the field technician can unplug the unit without previously locking it. This
causes another alarm (board removed alarm), but it removes the actual
fault alarm. When the field technician inserts the new board, the system
automatically verifies it and brings it into service if fault-free; otherwise a
corresponding alarm is issued.
24 72/1553-HSD 101 02/4 Uen A 2005-09-06

4.3 Alarm Handling

The Alarm Handling function, which is partly located in the NEs and partly
located in OSS-RC, administers all alarms that are generated in the WCDMA
RAN. The Alarm Handling function provides the services for distributing alarms
and other Fault Management-related events to the NMSs that subscribe to
these alarms and events. The Alarm Handling function also includes alarm
acknowledging functions.
Fault indications can be sent to the Alarm Handling function from the Fault
Handling function in the RBS, RXI, RNC and OSS-RC. The alarm handling
function converts the fault indications to alarms and publish them to the
subscribers.
When Alarm Handling issues an alarm, the alarm can be displayed in the
OSS-RC (Alarm List Viewer) or Element Manager GUI. OSS-RC and Element
Manager stores all alarm information for the active alarms and that information
can be viewed in GUIs, information like NE that issued the alarm, alarm severity,
specificProblem, affected resource etc.
The OSS-RC FM application provides the possibility to have “alarm to CPI

mapping” which by clicking on an alarm directs the user to a CPI document
for more information.
The OSS-RC FM application provides Alarm Status Matrix applications, which

allows the user to have a summary view of the alarms in a number of network
elements.
OSS-RC FM application maintains a complete log of alarms for the WCDMA

RAN. The operator can view the list of active alarms and the Alarm Log by
using OSS-RC or the Element Manager. The Alarm Handling is shown in
Figure 9 on page 23.
4.4 FM Event Handling

Fault Management Events can be categorized into different types depending on
their origin and cause. Each NE logs alarms in its NE alarm log which can be
retrieved by via the EM or via the SNM (OSS-RC). The SNM internal alarms are
also logged by the SNM alarm log and can be retrieved for presentation in GUI.
4.4.1 Generating O&M Events

The NE and SNM normally generate an FM event notification after there has
been an occurrence of a specific type in the network that gives useful FM
information but does not require action from an operator. For example: RNC
Node Restart Complete, redundancy shift, etc.
The alarm notications are issued when operator action is required. For example
HW failure.
72/1553-HSD 101 02/4 Uen A 2005-09-06 25

4.4.2 Viewing Logs
The operator can view the NE Event log stored in the RNC, RXI and RBS by
using the Element Manager. OSS-RC FM Application can retrieve and store
logs from each NE and stores these logs in the OSS-RC file directory. An
external NMS has the possibility to fetch these logs from the OSS-RC file
directory.
OSS-RC FM Application maintains a complete log of FM events for the WCDMA

RAN. FM event is an NE event that is published on the same interface as
alarms from the NEs.
4.5 Test Functions

In addition to the automatic supervision of functions for monitoring the NEs in
use, the operator can manually test some functions. Test functions are normally
carried out using the Element Manager. The operator can perform the following
manual tests:
• RBS Equipment Tests
• RNC Asynchronous Transfer Mode (ATM) end-to-end loopback tests
26 72/1553-HSD 101 02/4 Uen A 2005-09-06

5 Configuration Management
This chapter gives an overview of the WCDMA RAN Configuration Management

capabilities. These comprise configuration of equipment, the setting of Radio
Network (RN) and Transport Network (TN) parameters, and the upgrading or
amending of system software and hardware.
For more information about Radio Network Configuration, see Reference [19]
5.1 Configuration Management Categories

The Configuration Management functions configure parameters in the NEs for
the equipment, the TN and the Radio Network. The Configuration Management
functions are divided into the categories shown in Table 6 on page 27.
Table 6 Configuration Management Categories

Configuration Categories Description
Equipment Handling This area involves the following
functions:
• Equipment configuration, the
configuration of Network Elements
equipment.
• State handling, used to set different
resource states
• Product Inventory
The Equipment Handling is further
TN Configuration This area comprises functions
for configuration of the Transport
Network-specific parameters in the
NEs.
The TN Configuration area is further
72/1553-HSD 101 02/4 Uen A 2005-09-06 27

Table 6 Configuration Management Categories

Configuration Categories Description
RN Configuration This area comprises functions
for configuration of the Radio
Network-specific parameters in the
NEs.
The RN Configuration area is further
Software Management This area comprises the handling
of software installation, upgrades,
backup and restore procedures on
the NEs.
The Software Management area is
further descibed in Section 5.5 on
page 33.
The NEs store configuration data that describe the attributes of the equipment,
TN and RN. A backup of the configuration data is also stored at the node
(RBS, RXI or RNC) in case of failure. OSS-RC stores configuration data used
when configuring a new NE. For a model of the Equipment Configuration, see
Figure 10 on page 28.
NMS
OSS-RC
Radio/Transport
Configuration
Radio/Transport
Configuration
RXI RNC
U 00 00019A
Figure 10 Equipment Configuration Overview
Configuration Management actions can be carried out as a single action

on one NE using the EM, or as part of a complex procedure on many NEs
using OSS-RC. The planning tools and/or other external systems use the
Mun-interface in OSS-RC to import and export RN and TN data. The
28 72/1553-HSD 101 02/4 Uen A 2005-09-06

Mun-interface, see Reference [14], supports configuration via the Bulk CM

interface.
When entering configuration data in the WCDMA RAN the operator must
comply to the RDN and URL naming conventions, see Reference [17].
5.2 Equipment Handling

This section describes the setting of parameters on a NE level. The Equipment
Configuration functionality enables the configuration of a NE based on CPP
(RNC, RBS, and RXI nodes). The EMs handle the Equipment Configuration
functionality.
Equipment handling also covers state handling and Product Inventory.
A more detailed description of Equipment Handling can be found in Reference

[15].
5.2.1 Background
Equipment Configuration involves setting the parameters in the NEs that control
the hardware and software. The equipment is factory pre-configured using
information provided by the operator. However, site-specific settings must be
configured on site using the Element Manager. Changes can be made to the
configuration of the equipment during operation using the EMs.
When expanding the capacity in a NE with additional equipment, the operator

can configure the added HW via EM. This can be done without affecting
ongoing traffic.
When the added HW is configured, the RN and TN parameters associated to

the new equipment can then be configured by OSS-RC.
Configuration Management and Hardware Test Management is performed via

the RBS EM, RXI EM, and RNC EM respectively. Equipment configuration for
NEs can also be performed via scripts.
5.2.2 Adding a New RBS
This section describes the principles for configuring new RBS equipment.
Some configuration is required on site before the RBS can connect to the O&M
Intranet.
Once the RBS is connected to the O&M Intranet, the transport and RN
parameters can be downloaded and installed in the RBS using OSS-RC. The
configuration process is shown in Figure 11 on page 30. OSS-RC downloads
and installs the configuration data for the NEs.
72/1553-HSD 101 02/4 Uen A 2005-09-06 29

Figure 11 RNC and RBS Configuration indicating the degree of configuration

made at factory, locally connected EM (stand-alone) and remotely connected
EM/OSS-RC for equipment, radio and transport network.
5.2.3 Adding a New RNC

This section describes the principles for configuring new RNC equipment that
is added to the system. The procedure for installing a new RNC is similar
to the procedure for installing a new RBS, see Figure 11 on page 30. The
only difference is that the ATM ports used to interface with the CN need to
be configured on site. The configuration of the ATM ports is performed by
connecting the thin client to the RNC using an Ethernet cable and entering
the ATM ports in the RNC EM GUI.
After the RNC is configured to connect to the O&M Intranet, the remaining
transport parameters and RN parameters is downloaded and installed in the
RNC using OSS-RC.
5.2.4 Product Inventory

OSS-RC SMO application provides the the following product inventory functions
for the operator:
• Software inventory, including compare between network elements.
30 72/1553-HSD 101 02/4 Uen A 2005-09-06

• The NIO functionality (hardware inventory) is also available from the SMO
GUI.
The Product Inventory function finds and reports Product Information Data
(PID) about all the WCDMA RAN installed products. The range of products that
are listed or searched are nodes, hardware, load modules, Upgrade Packages
(UPs), and Configuration Versions (CVs). The PID is stored within all the
products and includes information such as product type, product name, and
serial number.
NIO (Network Inventory Organiser) provides the operator with the ability to
gather hardware inventory information from CPP nodes. The data can be
viewed in the SMO GUI and exported to an XML file. In this way, the user
is able to keep track of installed boards and their inventory information. NIO
consists of Network Element specific modules that are responsible for data
collection towards different network element types.
SMO includes a network topology tree view, where you can access software
inventory functions. The inventory is adjusted from the network element, and
cached in a database by SMO.
To collect the hardware inventory data, the user has to perform an adjust on
selected NEs. It is possible to order immediate, periodic or scheduled adjusts
of one or more NEs, and the adjust may be sequential or in parallel.
Common reasons for using the Product Inventory of all the installed products
are the following:
• Inventory after installation
Inventory is done after installation to verify installed products.
• Inventory for testing or fault tracing
Inventory is done after test and verification to get correct information about
which products are used, in particular the exact identity of the software.
• Inventory for upgrade
Inventory can be used to determine where and when the Upgrade Packages
(UPs) are installed. The Product Inventory function can also be used to
find information about specific products and where they are installed. This
information is useful for planning repairs or estimating the costs of hardware
replacement. It is also useful for understanding where faults may occur.
5.3 Transport Network Configuration

The TN is based on ATM, and the links between the nodes are, in general,
interconnected through an Synchronous Digital Hierarchy (SDH) or a
Plesciochronous Digital Hierarchy (PDH) Transport Network.
72/1553-HSD 101 02/4 Uen A 2005-09-06 31

The Transport Network Configuration can be performed in a number of ways

in RAN:
• Import/Export transport network configuration data into/from RAN via the

Bulk CM interface in OSS-RC (Bulk CM for Transport, BCT). Note. BCT is
an optional feature.
• Enter data directly into NEs (RNC, RBS and RXI) using the Element
Management Applications.
• Low-level Script interfaces.
Some parameters indicating installed equipment in the Network Elements

(NEs) are factory preset based on data provided by the operator. Some of
the TN parameters defining network addresses need to be set by operator
via the Element Manager (EM) during site installation. This includes for RNC
parameters that specify the interface to the CN – these need to be set in the
RNC before it can be connected to the O&M Intranet.
An EM wizard is used to gain access to the OSS-RC from the NE, i.e. RNC, RXI
and RBS. A wizard is also available to configure alarms and cables in the RBS.
After this the remaining TN parameters are downloaded and installed in the
RNC using OSS-RC. Transport Network Configuration using the OSS-RC Bulk
CM for TN (BCT) procedure is the preferred method at large changes or at
expansions of the network. A complete Transport Network Configuration is
prepared externally, transferred to OSS-RC and imported to a planned area.
When the Planned Area is activated the network will be updated with the new
configuration data.
5.4 Radio Network Configuration

RN configuration includes the configuration of RN logical entities such as
cells, common channels, Location Areas and Routing Areas. It also includes
the configuration of adjacent cells to support handover and the configuration
of RN algorithms such as power control. RN configuration involves setting
the parameters in the NEs that control the air interface between the RBS and
the UE.
To be able to configure a WCDMA RAN, the Radio Network Design needs to be

performed, configuration data needs to be prepared, and site equipment needs
to be installed and defined. Prior to the configuration of the radio network, the
transport network and the O&M Intranet needs to be configured.
The Radio Network Configuration can be performed in a number of ways

in RAN:
• Import/Export radio network configuration data into/from RAN via the Bulk
CM interface in OSS-RC
32 72/1553-HSD 101 02/4 Uen A 2005-09-06

• Enter data into RAN via the RNH applications in OSS-RC with the
associated support of the OSS-RC graphical user interfaces.
• Enter data directly into RNC and RBS using the Element Management
Applications in RNC and RBS.
• Low-level Script interfaces.
Radio Network Configuration using the Bulk CM procedure is the preferred

method at large changes or at expansions of the network. A complete Radio
Network Configuration is prepared externally, transferred to OSS-RC and
imported to a planned area. When the Planned Area is activated the network
will be updated by using one transaction per involved Network Element.
See Reference [19] for more details about Radio Network Configuration.
5.5 Software Management

The Software Management functionality provides the ability to perform Software
Installation, Software Upgrade, Configuration Backup, Configuration Restore,
and Disc Management. The Software Management is performed either from
the OSS-RC GUI or through the different EM GUIs for each node in the RAN
system. A more detailed description of Software Management can be found
in Reference [7].
Software management in OSS-RC is run via the OSS-RC application Software

Management Organizer (SMO).
5.5.1 Software Installation
The Software Installation process transfers a software UP from Ericsson

Release Server to a central FTP server in WCDMA RAN and further to the
specific NEs. The operator can install the UP in one or several RBSs, RXIs or
RNCs. For installation on multiple NEs the operator must use OSS-RC.
The Software Installation can be aborted and re-started via OSS-RC.
The Software Installation can be scheduled to occur at a predefined time

in OSS-RC.
The UPs are stored on the FTP server and can be downloaded to the NEs,
either by downloading and installing only the parts that differ between the new
UP and the already installed UP (a Delta Transfer) or by downloading and
installing a complete UP (Complete Transfer).
72/1553-HSD 101 02/4 Uen A 2005-09-06 33

5.5.2 Software Upgrades
An OSS-RC Operator performs Software upgrades on an RBS, RXI or an RNC.

The Software Upgrade function uses UPs in which system upgrade components
are distributed. An UP includes all needed files and documents for that node.
The Software Upgrade function replaces and activates new software on a node.
This is done while ensuring that the current configuration data is converted to
the corresponding data used by the new software if the structure of the data
is changed.
All data conversion, that modifies the structure and parameters related to the
previous release to fit the new release, is done automatically. If new parameters
are introduced, they have default values.
After the upgrade, the operator is asked to confirm the new software. If the
operator does not confirm the upgrade, the node automatically rolls back to the
software and configuration state that was in use before the upgrade.
The administration and control of the upgrade is performed through the

OSS-RC or the EMs.
5.5.3 Configuration Backup and Restore

Configuration Backup Administration provides the functionality to create a
backup copy of the NE’s configuration. The backup consists of references to
the software versions, the hardware to be used, and other types of configuration
data such as Equipment Configuration data, TN and RN configuration data. The
backup copy (commonly called Configuration Version, CV) is used to reload the
configuration of the NE after restarting the node. Note that the software does
not need to be backed up as it is already stored on the FTP file server, and the
CV contains information about which software to use when restoring the node.
Backup can be performed simultaneously on several NEs using OSS-RC, or

on a single NE using the embedded EMs. Using the EM, the operator invokes
the backups either manually, or set them to run at a specific time of day. Using
OSS-RC, the operator invokes the backups either manually, scheduled once, or
scheduled periodically on specified weekdays in a week.
The CVs can also be entered into the Rollback List in the node, that is a list that
describes which CVs the system tries to use to restore the node when a fault
occurs, and in which order the CVs are invoked. It is also possible via OSS-RC
to list and delete CVs on all nodes.
The Configuration Restore function uses CV’s to restore these NEs. Restoring
node software is carried out if there is a node malfunction. OSS-RC is used as
the SNM for dispatching of node restore requests, but the EM is also capable of
restoring a node.
The restore procedure requires that a local CV is physically present on the node.
34 72/1553-HSD 101 02/4 Uen A 2005-09-06

A more detailed description of Configuration Backup and Restore can be found

in Reference [16].
5.5.4 OSS-RC Backup and Restore

The OSS-RC and FTP server are backed up via a NW backup system. This
system also provides the restore functionality. The backup of OSS-RC can
be set to run automatically, so that the operator does not need to invoke the
function manually.
72/1553-HSD 101 02/4 Uen A 2005-09-06 35

36 72/1553-HSD 101 02/4 Uen A 2005-09-06

6 Performance Management
WCDMA RAN generates performance data in the NEs. The performance

data consists of counters and performance events. The performance data is
collected regularly by OSS-RC. This performance data can be exported to an
external management system via OSS-RC and/or be converted to a database
format to be stored persistently.
6.1 Performance Management Functions

Performance Management provides data on the WCDMA RAN performance
with respect to accessibility, retainability, and integrity. WCDMA RAN has
several Performance Management applications that gather and process
performance data. This data can be used to monitor key Quality of Service
(QoS) indicators, optimize network performance, identify trends, and
troubleshoot problems in WCDMA RAN.
The basic performance applications are Performance Statistics, Performance

Recording and General Performance Event Handling (GPEH). These
applications have GUIs that are accessed using OSS-RC.
Performance Statistics is further descibed in Section 6.2 on page 38,

Performance Recording is further descibed in Section 6.3 on page 40 and
GPEH is further descibed in Section 6.4 on page 43.
The applications for Performance Management are physically located in

OSS-RC, whereas node-level applications are physically stored in each RNC,
RXI, and RBS. The applications for Performance Management functionality can
be accessed from anywhere in the O&M Intranet. The logical and physical
Performance Management architecture is shown in Figure 12 on page 38.
72/1553-HSD 101 02/4 Uen A 2005-09-06 37

NMS
SQL query of FTP of statistics and

performanace recordings in XML
management database and ASN.1 format
Performance Performance GPEH

Statistics Recording Application
Application Application
OSS-RC
Performance Performance GPEH

Statistics Recording Application
Application Application
RBS RNC RXI RNC RBS RNC
U 00 00018C
Figure 12 RBS, RNC, RXI and OSS-RC Performance Management

Applications
6.2 Performance Statistics
6.2.1 General
The performance statistics are generated from measurements on the radio and
the transport network’s live traffic. The Performance Statistics data is made up
from a number of predefined counters.
The statistical data is fetched by OSS-RC from the network element every
Result Output Period (ROP) on a file in XML format. The ROP file is fetched
every 15 minutes. The ROP file is automatically compressed using GZIP.
Once OSS-RC has retrieved the result, it saves the data for 3 days (default
value), unless some other value is configured. For added RBSs, statistics are
automatically started in the RBS.
A more detailed description of Performance Statistics can be found in Reference

[18].
38 72/1553-HSD 101 02/4 Uen A 2005-09-06

6.2.2 Counter Formats
There are seven types of counters available in the system:
• A Peg counter is a counter that is increased by 1 at each occurrence of a

specific activity.
• A Gauge counter is a counter that may be increased or decremented

depending on the activity in the system.
• An Accumulator counter is a counter that is increased by the value of

a sample. It indicates the total sum of all sample values taken during
a certain time. The name of an accumulator counter begins either with
pmSum or pmSumOfSamp
• A Scan counter is a counter that is increased by 1 each time the

corresponding accumulator counter is increased. It indicates how many
samples of a certain quantity have been taken. A scan counter can
therefore be considered a specific kind of peg counter. Due to these types
of counters, it is possible to get the average value of all samples by dividing
the accumulator counter by the scan counter. The name of a scan counter
begins with pmSamples or pmNoOfSamp.
• PDF measurements are a list of range counters. A value is sampled (read)

periodically. If the value falls within a certain range, the range counter for
that range is incremented. All range counter values are collected and
stored in a ROP file at the end of each reporting period. For example, if
SIR values are split into three ranges: Range1 = [-11 dB..-4dB], Range2 =
[-4dB..+4dB], Range3 = [+4dB..+20dB] and a value is read every 3 minutes
over a 15 minute period (values = -10, -3, +5, +5, +6), then the three
RangeCounters will be reported as RangeCounter1 = 1, RangeCounter2 =
1, RangeCounter3 = 3.
• Discrete distributed measurements are a series of values recorded during

a reporting period. Each series of values may be of one of the following
measurement types: Accumulated over a measurement period and read at
the end of each measurement period (a gauge or peg counter). Averaged
over the duration of a measurement period. Read at a specific time (the
measurement time), within the measurement period (at a specific frame).At
the end of a series of consecutive measurement periods (the reporting
period) all measurement values are collected and stored in a ROP file. For
example, if a SIR value is read every 3 minutes over a 15-minute period
(values = -10, -3, +5, +5, +6), then 5 DDM measurements are reported as
Meas1 = -10, Meas2 = -3, Meas3 = 5, Meas4 = 5, Meas5 = 6.
• A Calculated Statistics counter is a counter whose value is determined

by other counters. This is performed in the OSS-RC Statistics database.
72/1553-HSD 101 02/4 Uen A 2005-09-06 39

The ROP files are opened in order to be transferred into the database and
the calculations are done by the database itself during this process. This
means that these counters are not available when the Statistics Database
is not present.
6.2.3 Measurement Administration
OSS-RC acts as a centralized point for the initiation and collection of

performance data for the WCDMA RAN. The nodes provide a GUI (Graphical
User Interface) and as also a machine-machine interface allowing OSS-RC to
administer the statistics. The Performance Management function, allocated
in OSS-RC, allows an OSS-RC operator to create Subscription Profiles
and subscribe to Performance Monitorings and through GUI subscribe to
performance recordings.
See Reference [18] for information regarding counters instances allowed to be

simultaneously active per network element type.
As a result of the collection one statistic files will be generated per RNC and
one statistics file will be generated per RBS. Collected data files remain in
OSS-RC for 3 days for statistical files before being deleted by OSS-RC. These
values can be changed by the modifying parameters statisticsFileStorageDays
and recordingFileStorageDay respectively. The minimum value is 24 hours and
the maximum is limited only by available hard drive disk space. All ROP files
are automatically fetched after the end of every ROP.
The Statistics database is a part of the optional OSS-RC Performance

Management feature. It provides the ability to store the data for up to one year.
All stored data can be accessed through the SQL interface. This feature offers
the ability to aggregate the raw data based on time and object, provides data
reliability indicators, and takes care of the Calculated Statistics counters.
OSS-RC also provides a report generator tool, Network Statistics Analyze,

NWS-A. To make reports on counter data accessed through the SQL interface.
A set of pre-defined report with relevant formulas (i.e. Key Performance
Indicators) is also provided.
6.2.4 Counters
For information about counters and their triggering conditions see Reference
[18].
6.3 Performance Recording

Performance Recording applications are used to collect performance events and
radio related measurements used for detailed network performance analysis,
troubleshooting and network optimization. RAN performance monitoring is
crucial for different user categories but in particular optimization engineers.
40 72/1553-HSD 101 02/4 Uen A 2005-09-06

They are the main users of the Performance Recording data ensuring the best
operational conditions in the network. Their typical tasks include:
• Detecting performance degradations in the network, enabling the operator

to take actions preserving high traffic accessibility and quality.
• Troubleshooting the network and providing solutions for potential

improvements.
• Monitoring and optimizing the network performance to improve

subscriber-perceived quality, or better utilization of the installed resources.
• Providing network planners with detailed information needed for

dimensioning and configuration obtaining optimal network operation.
The recording files (ROP files) are collected and stored in the OSS-RC local file
directory. Two different types of performance recordings are used:
• UE traffic recording (UETR)
A recording of selected performance events, and/or radio related

measurements, covering specific, operator-selected UE - using the IMSI.
• Cell Traffic Recording (CTR)
A recording of selected performance events, and/or radio related

measurements, covering specific cell, usually referred to as the recording
area.
These applications are based on a set of pre-defined events and periodic

measurements. Each recording collects events and radio environment
measurements according to the recording profile as defined by the user. The
main difference between CTR and UETR is that in UETR it is the operator who
decides which User Equipments (UEs) to record, while in CTR any UE for a
selected cell may be recorded. The RNC adds each received measurement
and event into the CTR or UETR file (depending on which one is activated).
The recordings are then accumulated into files for the duration of Report Output
Period (ROP), and are stored in the network elements (NEs). The duration
of ROP is 15 minutes.
6.3.1 UETR
The UETR function enables the operator to record important events and
measurements for a selected UE, traveling through a network. Only one UE can
be selected for recording per UETR, but up to 16 simultaneous UETR recordings
can run in parallel for one RNC. The selected UEs are identified by the operator
using the UE’s International Mobile Subscriber Identity (IMSI) number.
The operator can send out a test mobile (in particular, after changes or
extensions to the network) or record a UE conducting live traffic to investigate
72/1553-HSD 101 02/4 Uen A 2005-09-06 41

network performance a specific area. Typically recording UE related signaling,

and UE related measurement data either provided by the RBS or the UE itself.
The user may choose to record one or more of the messages within one
or more of the following protocol groups: Node B Application Part (NBAP),
Radio Access Network Application Part (RANAP), Radio Network Subsystem
Application Part (RNSAP) and Radio Resource Control (RRC). The radio
measurements and events that can be recorded for both the uplink and the
downlink are listed in Reference [10].
With this function the operator can monitor specific information that is sent
to and from the UEs. For example, the operator can monitor signalling data
that is used to make handover decisions. This enables the operator to identify
parameters that need to be adjusted, leading to improved performance.
6.3.2 CTR
The CTR function collects data for a number of UE connections within a certain
recording area. The recording area is defined as a specific cell in which the UEs
are going to be followed. CTR can record up to a maximum of 16 simultaneous
connections. The first 16 UEs satisfying triggering events in the recording area,
composed of an Access Cell, are recorded.
A maximum of two CTRs recording subscriptions with 16 simultaneous UE

connections each are allowed per RNC. A recording for a UE starts when it
fulfills triggering events in the selected Access Cell. Default triggering event is
the RRC Connection setup. This is the very first message that can be recorded
by the CTR function during a connection setup.
RNC Event data, and measurement data from the RBS and UE may be
selected for recording. The user can choose to record one or more messages
within of the following protocol groups: NBAP, RANAP, RNSAP and RRC. The
radio measurements and events that can be selected for both the uplink and the
downlink are listed in Reference [10].
CTR is specifically tailored to monitor limited network areas, like individual cell
performance. It is typically used for trouble shooting and verifying configuration
changes such as the handover parameters.
6.3.3 PM Recording Administration

The Performance Management function within OSS-RC enables operator to
initiate and manage (administer) Performance Recordings within the RAN
network. Performance Recordings (UETR/CTR) execute as one or more
Performance Monitorings on the RNC Nodes. The OSS-RC Operator controls
the Performance Recordings (Monitorings) by creating GUI driven Subscription
Profiles for Performance Recording data. For further details see Reference [9].
OSS-RC supports a machine-machine interface towards RNC that allows

OSS-RC to administer the PM recordings. For each ROP, the recorded result is
42 72/1553-HSD 101 02/4 Uen A 2005-09-06

one file per recording UETR or CTR. All ROP files are automatically collected
after the end of every ROP. The recording files are stored in the OSS-RC file
system, where external OSS-RC users such as Network Management System
users, are able to/may access them using FTP.
Collected ROP files are in combined ASN.1 binary format and remain in
OSS-RC for two days by default, before being deleted. This OSS-RC parameter
recordingFileStorageDaysrelated to ROP file storage time is user
controllable where the minimum value is 24 hours, and the maximum is only
limited by the available disk space.
OSS-RC provides an interface for retrieving ROP files in ASCII and tab-delimited
format Reference [11].
6.4 GPEH
Among the Performance Management applications is the OSS-RC GPEH
function. It is the most flexible recording function allowing the operators to
freely create subscriptions on various system levels. From basically full system
recording including all RBS/ RNC internal events and RNC node internal
events as available in WCDMA RAN, to only few selective events involved in
a particular traffic scenario.
By analyzing the event based information, the GPEH function provides

monitoring and evaluation capability of any traffic scenario taking place in a
WRAN. The GPEH recordings are specifically suited for detailed analysis and
troubleshooting support of a network, such as:
• Detecting unacceptable performance degradation in the network, enabling

the operator to take immediate actions to preserve quality of the network.
• Advanced troubleshooting of any traffic related function and it’s algorithm

in the network.
• Detailed performance monitoring and network optimization in order to

further improve subscriber-perceived quality or a better utilization of the
installed resources.
• Providing network planners with the detailed information related to

dimensioning and configuration of the network.
The GPEH recordings are collected by OSS-RC, and stored in the OSS-RC
local file directory.
Three different types of events are available to the GPEH recording function:
• RBS Node-internal events
• RNC Node-internal events
• RNC Inter-node events (protocol events)
72/1553-HSD 101 02/4 Uen A 2005-09-06 43

6.4.1 RBS Node-internal Events
The RBS node-internal events aim to observe the radio link supervision/
synchronization for a specific RBS node. These events carry massage header
data (including event name and timestamp) as well as the full message
contents. These events are recordable on RBS level and more detailed
description on supported events is according to Reference [13].
6.4.2 RNC Node-internal Events

The RNC node-internal events aim to observe the performance of traffic related
algorithms in the WCDMA RAN. These events in the GPEH recording carry
massage header data (including event name, timestamp, RNC module Id, Ue
context ID) as well as the full message contents. They are recordable on RNC
level for detailes see Reference [12].
6.4.3 RNC Inter-node Events

The Inter-node events are based on the RNC external protocols. The events
supported are the L3 messages according to the RRC, NBAP, RANAP, and
RNSAP protocols. These events are recordable on RNC level and carry
massage header data (including event name, timestamp, RNC module Id,
Ue context ID) with or without the full message contents. The parameter
gpehDataLevel controls the data level for protocol messages including or
excluding the ASN.1 part in the recording. For detailed list on supported events
and event description, see Reference [12].
6.4.4 GPEH Administration

OSS-RC Performance Management GUI and a machine-machine interface
allows users to schedule, collect and manage the PM recordings. The log files
of GPEH Recording are temporarily stored by the NEs (RNC and RBS) with
one file per Module Processor (MP) and ROP.
The ROP files consisting of L3 protocol events (RNC files only) and internal
events (RNC/RBS files) will be stored in bit-packed binary format. The GPEH
data is stored for at least one hour, all depending on the file size and the
storage size configuration in the network element.
PM recording files are automatically fetched by the OSS-RC Performance

Management function after the end of each ROP. The files are locally stored
in the OSS-RC file system, where external users have full access to the files
using FTP. Collected GPEH files by default remain in OSS-RC for two days
before being deleted. The recordingFileStorageDays parameter is user
controllable and can be changed in OSS-RC. The minimum value is 24 hours
as ROP file storage period, and the maximum is only limited by the available
disk space.
44 72/1553-HSD 101 02/4 Uen A 2005-09-06

For a further description on how to use the administrative functions supported

by OSS-RC Performance Management GUI, see Reference [9].
A parser is available in OSS-RC to view and save recording files in either ASCII
format and/ or tab-delimited file format . For further details, see Reference [11].
72/1553-HSD 101 02/4 Uen A 2005-09-06 45

46 72/1553-HSD 101 02/4 Uen A 2005-09-06

7 Security Management
This chapter gives an overview of the Security Management capabilities in

the WCDMA RAN system. These include firewall set up and installation and
configuration of the Ericsson code verification certificates. For more information
on Security Management, see Reference [6].
7.1 General
The operator can perform the following security management actions:
• Administer user access rights in TSS in OSS-RC
• Set up Firewalls
• Install code verification certificates
• Managing user accounts for RAN management.
7.2 Security Management Functionality

Security Management in the WCDMA RAN provide security functions at the
system’s application layer as well as perimeter defence. These functions
include the following:
• Single Logon to OSS-RC and RAN Element Management
The SLS authenticates all users logging on to OSS-RC or NE EMs via a

supplied user name and password. Single logon is an important feature
which enables user to logon only once to access the O&M functions in
WCDMA RAN.
• Public Key Infrastructure (PKI)-based authentication of Common Object

Request Broker Architecture (CORBA) application communication
Application communication is authenticated and secured by use of public

key technology.
• Message Integrity Protection for CORBA applications
Application communication is integrity-protected to reject all unauthorized

data modification attempts.
• PKI support in the managed system
The Security Management function supports the generation of keys and

certificates for managed nodes.
72/1553-HSD 101 02/4 Uen A 2005-09-06 47

• Security Log
A logging mechanism for security events is provided to enable the trace of

security-threatening activities.
• Central Application Server (AS)
All access to the O&M network must be authenticated by the AS.
• Firewall Protection
Communication in and out of the perimeter defence is strictly defined and

controlled by firewalls.
• Secure Command Line Interface/Secure File Transfer Protocol (SCLI/SFTP)
SCLI and SFTP provide a secure alternative to telnet and ftp.
48 72/1553-HSD 101 02/4 Uen A 2005-09-06

8 Glossary
All acronyms and terms used in this description are listed in Reference [4].
72/1553-HSD 101 02/4 Uen A 2005-09-06 49

50 72/1553-HSD 101 02/4 Uen A 2005-09-06

Reference List
Reference List
[1] Element Manager RBS 3000, 2/1551–CRH 109 121/1 Uen
[2] Element Manager RNC 3810, 16/1551–AXD 105 03/1
[3] Fault Management, 79/1553–HSD 101 02/4 Uen
[4] Glossary of Terms, 2/00322–HSD 101 02/4 Uen
[5] RXI 820 Element Manager Graphical User Interface, 19605–CNX 901
280 Uae
[6] Security Management, 78/1553–HSD 101 02/3 Uen
[7] Software Management, 75/1553–HSD 101 02/4 Uen
[8] System Description, 2/1551–HSD 101 02/4 Uen
[9] PM, Subscription and Performance Monitoring User Guide, 1/1553-APR

901 91/3 Uen
[10] Performance Recording RNC 3810, 46/1551–AXD105 03/1 Uen
[11] REI, Recording and Events Interface User, 1/1553-APR 901 275/2 Uen
[12] General Performance Event Handling in RNC 3810, 45/1551-AXD10503/1
[13] General Performance Event Handling RBS, 61/1551-HRB 105 102/1
[14] Published UTRAN Management Interface, Mu, 1/155 19-HSD 101 02/4
[15] Equipment Handling, 88/1553-HSD 101 02/4
[16] Software Backup Administration, 77/1553-HSD 101 02/4
[17] RDN and URL Naming Conventions WCDMA RAN, 74/1553-HSD 101
02/4
[18] System Performance Statistics, 85/1553-HSD 101 02/4
[19] Radio Network Configuration, 100/1553–HSD 101 02/4
[20] WCDMA RAN Network Impact Report, 1/10948–HSD 101 02/4
72/1553-HSD 101 02/4 Uen A 2005-09-06 51

WCDMA RAN O&amp;M General

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

WCDMA RAN O&amp;M General

Загружено:

Авторское право:

Доступные форматы

Operation and Maintenance

© Ericsson AB 2005 – All Rights Reserved

Citrix® MetaFrame is a trademark of Citrix Systems, Inc.

72/1553-HSD 101 02/4 Uen A 2005-09-06

72/1553-HSD 101 02/4 Uen A 2005-09-06

72/1553-HSD 101 02/4 Uen A 2005-09-06

This includes principles for:

• Operation Support System — Radio and Core (OSS-RC)

• Element Manager (EM) for the Radio Network Controller (RNC)

• EM for Radio Base Station (RBS)

• EM for RXI. RXI is an Ericsson CPP-based node that implements ATM

Furthermore this document describes the architecture, operation, and

1.2 Target Groups

72/1553-HSD 101 02/4 Uen A 2005-09-06 1

1.3 Revision Information

Table 1 Revision History

2 72/1553-HSD 101 02/4 Uen A 2005-09-06

2.1 WCDMA RAN

72/1553-HSD 101 02/4 Uen A 2005-09-06 3

Figure 1 WCDMA RAN Overall Architecture

2.2 O&M Architecture

2.2.1 O&M Fundamentals

The management system architecture is shown in Figure 2 on page 5.

4 72/1553-HSD 101 02/4 Uen A 2005-09-06

Figure 2 Management System Architecture

1 Management System Architecture

The Management System Architecture comprises three layers. The

The middle layer is the Subnetwork Management Layer. This layer

The lowest layer is the Element Management Layer. This layer

All system nodes are interconnected through an Internet Protocol-based

72/1553-HSD 101 02/4 Uen A 2005-09-06 5

perform management from a central management location. See Section

3 Embedded Element Management

The NEs platforms contain all management applications necessary for

OSS-RC contains online client applications for day-to-day handling of O&M

2.2.2 O&M Activities

6 72/1553-HSD 101 02/4 Uen A 2005-09-06

in OSS-RC. See Section 6 on page 37 for a description of Performance

72/1553-HSD 101 02/4 Uen A 2005-09-06 7

8 72/1553-HSD 101 02/4 Uen A 2005-09-06

• Subnetwork Management actions

These actions require operations on several nodes. This is handled by

• Element Management actions

3.1 O&M Intranet

3.1.1 Remote Access to RNC, RXI, and RBS

In order to prevent un-authorised access to the O&M Intranet, it is recommended

72/1553-HSD 101 02/4 Uen A 2005-09-06 9

Figure 3 Access Alternatives for WCDMA RAN Nodes

1 Operation & Maintenance Center

3 Local Access without Connection

10 72/1553-HSD 101 02/4 Uen A 2005-09-06

3.1.2 O&M Infrastructure

The O&M Common Infrastructure consists of the following parts:

Figure 4 on page 11 shows a logical view of the O&M infrastructure.

IP Network ALEX Server

Figure 4 Common O&M Infrastructure (COMINF)

The O&M infrastructure consists of the functions described in Table 2 on page

72/1553-HSD 101 02/4 Uen A 2005-09-06 11

Table 2 O&M Infrastructure Functionality

12 72/1553-HSD 101 02/4 Uen A 2005-09-06

Table 2 O&M Infrastructure Functionality

3.2.1 OSS-RC Functions

72/1553-HSD 101 02/4 Uen A 2005-09-06 13

as fault notifications or configuration data to the NMS. For an illustration of the

WCDMA RAN O&M General

WCDMA RAN O&M General