Lzt 123 7371 r5 a wcdma ran operation

WCDMA RAN Operation

LZT 123 7371 R5A © Ericsson 2007 - 1 -

WCDMA RAN Operation

STUDENT BOOK LZT 123 7371 R5A

WCDMA RAN Operation

- 2 - © Ericsson 2007 LZT 123 7371 R5A

DISCLAIMER This book is a training document and contains simplifications. Therefore, it must not be considered as a specification of the system. The contents of this document are subject to revision without notice due to ongoing progress in methodology, design and manufacturing. Ericsson assumes no legal responsibility for any error or damage resulting from the usage of this document. This document is not intended to replace the technical documentation that was shipped with your system. Always refer to that technical documentation during operation and maintenance.

© Ericsson 2007 This document was produced by Ericsson. • It is used for training purposes only and may not be copied or

reproduced in any manner without the express written consent of Ericsson.

This Student Book, LZT 123 7371, R5A supports course number LZU 108 5920 .

1 WCDMA RAN System Overview

LZT 123 7371 R5A © 2007 Ericsson - 3 -

Table of Contents

1 WCDMA RAN SYSTEM OVERVIEW ............................................7 OBJECTIVES....................................................................................................7

OVERVIEW ............................................................................................9

WCDMA RAN ARCHITECTURE..........................................................10

WCDMA RAN CHARACTERISTICS....................................................11 GENERAL FEATURES OF WCDMA RAN .....................................................11 COVERAGE AND DATA RATES....................................................................12 MACRO DIVERSITY.......................................................................................13

WCDMA RAN FUNCTIONALITY.........................................................14 MANAGEMENT FUNCTIONALITY.................................................................14 SERVICES AND RABS FUNCTIONALITY .....................................................15 RADIO NETWORK FUNCTIONALITY............................................................16 TRANSPORT NETWORK FUNCTIONALITY .................................................16 O&M INFRASTRUCTURE FUNCTIONALITY ................................................17 OSS-RC FUNCTIONALITY.............................................................................18 TEMS FUNCTIONALITY.................................................................................19

2 WCDMA RAN SYSTEM DESCRIPTION.....................................21 OBJECTIVES..................................................................................................21

OVERVIEW ..........................................................................................23

RADIO NETWORK SUBSYSTEM .......................................................23 SERVICES AND RABS...................................................................................24 IU INTERFACE ...............................................................................................24 IUR INTERFACE.............................................................................................25

RNC-RBS SUBSYSTEM......................................................................25 ARCHITECTURE ............................................................................................26 LOCAL CELLS ................................................................................................27 UTRAN CELL..................................................................................................27 IUB INTERFACE.............................................................................................29

WCDMA RAN NODES.........................................................................32 RNC ................................................................................................................32

WCDMA RAN Operation

- 4 - © Ericsson 2007 LZT 123 7371 R5A

RBS.................................................................................................................46 RXI ..................................................................................................................48 CPP.................................................................................................................49

3 CUSTOMER PRODUCT INFORMATION....................................53 OBJECTIVES..................................................................................................53

OVERVIEW ..........................................................................................55

CPI STRUCTURE ................................................................................56 WCDMA RAN LIBRARY .................................................................................58 RNC LIBRARY ................................................................................................59 RBS LIBRARY ................................................................................................60

GETTING INFORMATION FROM CPI .................................................60

OPERATING INSTRUCTIONS.............................................................62

4 OPERATION AND MAINTENANCE APPLICATIONS................63 OBJECTIVES..................................................................................................63

OVERVIEW ..........................................................................................65

OPERATION AND MAINTENANCE CATEGORIES ............................65 CONFIGURATION MANAGEMENT ...............................................................65 FAULT MANAGEMENT ..................................................................................66 PERFORMANCE MANAGEMENT .................................................................66 SECURITY MANAGEMENT ...........................................................................66

OPERATION AND MAINTENANCE NETWORK.................................66 LOCAL ACCESS.............................................................................................67 O&M INTRANET .............................................................................................68 O&M INFRASTRUCTURE ..............................................................................69

OPERATION AND MAINTENANCE APPLICATIONS .........................72 MANAGEMENT SYSTEM ARCHITECTURE .................................................73 OPERATION SUPPORT SYSTEM FOR RADIO AND CORE (OSS-RC).......74 WCDMA RAN SYSTEM LEVEL MANAGEMENT...........................................75 RADIO NETWORK SUBSYSTEM LEVEL MANAGEMENT ...........................87 RNC-RBS SUBSYSTEM LEVEL MANAGEMENT..........................................87 WCDMA RAN NODE LEVEL MANAGEMENT ...............................................90


LZT 123 7371 R5A © 2007 Ericsson - 5 -

5 CONFIGURATION MANAGEMENT............................................99 OBJECTIVES..................................................................................................99

OVERVIEW ........................................................................................101

EQUIPMENT HANDLING ..................................................................101 HARDWARE CONFIGURATION ..................................................................101 HARDWARE MANAGEMENT APPLICATIONS ...........................................105 SOFTWARE CONFIGURATION...................................................................114 MANAGEMENT TOOLS ...............................................................................118

SOFTWARE MANAGEMENT ............................................................122 CONFIGURATION VERSION.......................................................................122 MANAGEMENT TOOLS ...............................................................................126

SYSTEM UPGRADE..........................................................................128 HARDWARE UPGRADE ..............................................................................129 SOFTWARE UPGRADE ...............................................................................130 MANAGEMENT TOOLS ...............................................................................133

CONFIGURATION DATA HANDLING ...............................................135 FALLBACK....................................................................................................136 DATA CONSISTENCY..................................................................................137

6 FAULT MANAGEMENT ............................................................139 OBJECTIVES................................................................................................139

OVERVIEW ........................................................................................141

WCDMA RAN FAULT MANAGEMENT FEATURES .........................141 FAULT CATEGORIES ..................................................................................141 FAULT MANAGEMENT FUNCTIONS ..........................................................142 FAULT ESCALATION PROCESS ................................................................143

FAULT HANDLING ............................................................................144 FAULT HANDLING PROCESS.....................................................................144 WCDMA RAN COMMON FAULTS ...............................................................148 WCDMA RAN KNOWN FAULTS AND DESCRIPTION................................150

7 PERFORMANCE MANAGEMENT............................................153 OBJECTIVES................................................................................................153

WCDMA RAN Operation

- 6 - © Ericsson 2007 LZT 123 7371 R5A

OVERVIEW ........................................................................................155

PERFORMANCE MANAGEMENT DEFINITION ...............................155 SUBSCRIPTION PROFILE...........................................................................155 SUBSCRIPTION PROFILE MANAGEMENT TOOL .....................................158

DATA COLLECTION PROCESS .......................................................158 PERFORMANCE STATISTICS ....................................................................159 PERFORMANCE RECORDINGS.................................................................160 GPEH............................................................................................................162 DATA COLLECTION MANAGEMENT..........................................................163

8 SECURITY MANAGEMENT......................................................165 OBJECTIVES................................................................................................165

OVERVIEW ........................................................................................167

SECURITY FEATURES .....................................................................167 SECURITY ZONES.......................................................................................167 TRAFFIC CONTROL ....................................................................................168

WCDMA RAN SECURE ACCESS .....................................................169 NMC ACCESS CONTROL............................................................................170 SITE LAN ACCESS CONTROL....................................................................171

DETECTION AND INVESTIGATION TOOLS ....................................172


LZT 123 7371 R5A © 2007 Ericsson - 7 -


This module describes the WCDMA Radio Access Network System.

OBJECTIVES

After this chapter the participants will be able to:

• List the applications and services provided by 3G networks,

• Explain the role and position of the WCDMA RAN in 3G networks,

• Explain the architecture of the WCDMA RAN,

• Detail the characteristics of the WCDMA RAN,

• Explain WCDMA RAN management functions,

• List the services provided by WCDMA RAN,

• Detail WCDMA RAN infrastructure.

Figure 1-1: Objectives.

WCDMA RAN Operation

- 8 - © Ericsson 2007 LZT 123 7371 R5A

Intentionally Blank


LZT 123 7371 R5A © 2007 Ericsson - 9 -

OVERVIEW This chapter describes at a high level Ericsson’s WCDMA RAN System.

The WCDMA RAN corresponds to the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) in 3GPP specifications.

The use of 3rd Generation (3G) technology increases the capabilities compared to earlier mobile communication systems. Systems based on 3G technology integrate all present services, such as speech and future multimedia services, into one system.

The circuit-switched and packet-switched traffic carries the necessary subscriber data. This adopts multimedia applications and saves spectrum resources.

The very high data rates allow the transmission of different types of information simultaneously. These information types include graphics, photos, text and figures, video clips, sound tracks, and software applications.

The figure below shows some examples of applications expected in a 3G system.

Remote LAN & Intranet• File Transfer• Groupware• E-mail• Corporate Info

Remote LAN & Intranet• File Transfer• Groupware• E-mail• Corporate Info

Video / Audio• High-quality voice• Music

Video / Audio• High-quality voice• Music

Videoconference

Videoconference

Internet applications• WWW browsing• Video telephone• E-mail• News push• Network games• Electronic commerce

Internet applications• WWW browsing• Video telephone• E-mail• News push• Network games• Electronic commerce

• Wireless postcard and electronic business card

• Multimedia electronic mail

• Wireless postcard and electronic business card

• Multimedia electronic mail

Specialized Application• Telemedicine• Remote security monitoring• Location services

ApplicationServer

Video Terminal

PSTNISDN3G

Internet

CorporateLAN

ApplicationServer

InternetService Provider

Figure 1-2: 3G Applications

WCDMA RAN Operation

- 10 - © Ericsson 2007 LZT 123 7371 R5A

WCDMA RAN ARCHITECTURE WCDMA RAN connects the Core Network (CN) and the User Equipment (UE). The WCDMA RAN also comprises interfaces towards different external management systems.

WCDMA RAN is made of several Radio Network Subsystems (RNS), each RNS connecting the CN to the UEs located over a geographical area.

Radio Network Controller (RNC) and Radio Base Station (RBS) are the traffic handling nodes in a RNS.

RNC-RBS Subsystem controls and carries traffic from and to an RBS coverage area.

Radio Access Network Aggregator (RANAG) is a transport network node, implemented as RXI.

Operation Support System Radio and Core (OSS-RC) manage the Operation and Maintenance in the network.

The following diagram summarizes the WCDMA RAN architecture.

Radio AccessNetwork

Iub

Iu

Iur

Mub

Mur

RNC Radio Network ControllerRBS Radio Base StationOSS-RC Operation Support System – Radio CoreTEMS TEMS Optimization Solution RXI Radio Access Network AggregatorUser Equipment

Uu

ExternalManagement

System

ExternalManagement

System

Mun

Mun

NetworkManagementEnvironment

OSS-RC

TEMS

Core Network

RNC

RXI

RNC

RBS

RBSRBS

Figure 1-3: WCDMA RAN Architecture


LZT 123 7371 R5A © 2007 Ericsson - 11 -

WCDMA RAN CHARACTERISTICS

GENERAL FEATURES OF WCDMA RAN

All WCDMA systems have built-in support for multimedia services and high spectrum efficiency. WCDMA RAN supports the following features:

Wide Bandwidth

The chip rate of 3.84 Mcps is used to provide a carrier bandwidth of approximately 5 MHz. The wide bandwidth reduces sensitivity to multi-path fading.

Power Control

Power is the common shared resource that makes WCDMA RAN flexible in handling mixed services and services with variable bit rate demand. Radio resource management allocates power to each subscriber and ensures that each user and service creates the minimum of interference.

One-cell Frequency Reuse

WCDMA RAN uses one-cell frequency reuse. This flexibility is supported in WCDMA RAN by the use of Orthogonal Variable Spreading Factor (OVSF) Codes for channelization of different subscribers.

These codes have the ability to maintain orthogonality between subscribers even if they operate at different bit rates. One physical resource can therefore carry multiple services with variable bit rates.

The power allocated to this physical resource is adjusted as the bit rate demand changes so that Quality of Service is guaranteed at any instant of the connection.

Coherent Detection

WCDMA RAN employs coherent detection on the radio uplink and downlink.

WCDMA RAN Operation

- 12 - © Ericsson 2007 LZT 123 7371 R5A

Frequency Division Duplex

FDD is a duplex method when radio uplink and downlink transmissions uses two separated radio frequencies. This is the most common technology used currently.

In the FDD mode of operation, each operator is allocated one or several pairs of radio frequencies. A pair of radio frequencies consists in a 5Mhz radio frequency band for the uplink and a 5 Mhz radio frequency band on the downlink. A pair of radio frequencies is commonly called a carrier.

Spectrum Allocation for WCDMA

The spectrum allocation in Europe, Japan, and the USA is shown in the figure below. In Europe and in most of Asia, the IMT-2000 bands of 2x60 MHz (1920-1980 MHz and 2110-2170 MHz) are available for WCDMA Frequency Division Duplex (FDD).

In the USA, no new spectrum bandwidth has yet been made available for 3G systems. Third-generation services can be implemented by reallocating the spectrum for 3G systems within the existing spectrum for 2G systems.

Figure 1-4: WCDMA Spectrum Allocations

COVERAGE AND DATA RATES

The WCDMA RAN transmits data from multiple subscribers across the 5 MHz spectrum using multiple frequencies with data rates up to 14 Mbps (downlink) and 1.46 Mbps (uplink) using the High Speed Packet Access (HSPA) radio technology.


LZT 123 7371 R5A © 2007 Ericsson - 13 -

RAN Release 99 vs HSPA

With the RAN release 99 radio technology data rates of up to 384 kbps, downlink and uplink, can be achieved. However, the actual rates available to a subscriber will vary depending on position in a cell, interference from other users and neighboring cells.

Other factors that influence the data rates are the speed at which the subscriber is traveling and the number of subscribers accessing the same cell.

At low traffic load, the radio coverage is higher because the subscriber interference in a cell is lower. At high traffic load, the power-controlled interference from the subscribers constitutes the main part of the total interference. This reduces the maximum radio coverage.

The HSPA technology increases the available bandwidth by implementing HSDPA on the downlink and E-UL on the Uplink.

With HSDPA all the downlink power not used by R99 traffic can be allocated to HSDPA users. Users connected using HSDPA are sharing a common channel, which is not power controlled. HSDPA is based on fast adaptation to radio propagation conditions using short TTI, fast rate adaptation, fast scheduling, dynamic power allocation, fast Hybrid HARQ with soft combining, Higher-Order modulation and shared channel transmission.

With E-UL all the RBS sensitivity not used by R99 traffic can be allocated to E-UL users. E-UL is based on fast adaptation to radio propagation conditions, using fast link adaptation (both rate and power), scheduling, shared resources and fast Hybrid HARQ with soft combining.

MACRO DIVERSITY

The WCDMA RAN uses macro diversity for the transmission of dedicated data between the UE and the RBS. This technique allows simultaneous use of links between the UE and two or more cells. This provides a smooth transition as the UE moves from one RBS to another (Soft Handover) or between cells of the same RBS (Softer Handover).

WCDMA RAN Operation

- 14 - © Ericsson 2007 LZT 123 7371 R5A

WCDMA RAN FUNCTIONALITY

Figure 1-5: WCDMA RAN Functionality

MANAGEMENT FUNCTIONALITY

• Customer Product Information: All WCDMA RAN Customer Product Information (CPI) is accessible on-line through an information browser accessing an ALEX server. The CPI contains descriptive information and procedural instructions on an overall RAN level, and on a more detailed level for all system nodes such as OSS-RC, RNC, RBS subsystems, and RANAG.

• Accessibility: This feature allows the operator to access the Element Management Application and Support (EMAS) in the node and to remotely access all nodes connected to the O&M Intranet.

• Site LAN: This feature allows the operator to connect to any External Auxiliary Units (EAUs), as long as the EAUs provide an IP connection for management purpose to the O&M Intranet at RBS, RNC or RANAG sites.

• Equipment Handling: This feature allows getting information and operating over hardware and software in the WCDMA RAN. The Ericsson management tools support GUI-based and command-based operations and reports.

• Backup: This feature provides the operator with all necessary tools to backup and restore a node’s software and configuration. The Ericsson management tools support backup procedures.


LZT 123 7371 R5A © 2007 Ericsson - 15 -

• Software Management: This feature allows the operator to install new and changed software. The software is collected in an Upgrade Package, and can be installed on RNCs, RBSs, and RANAGs. Once installed, the RNCs, RBSs, and RANAGs can subsequently be upgraded with the new Upgrade Package.

• Configuration management: This feature provides the operator the means to configure the Radio Network, the Transport Network and the equipment in the WCDMA RAN by controlling and collecting data from NEs. The applications used for Configuration Management are OSS-RC and EMAS.

• Fault Management: This feature includes functionality for supervision, test, and alarm handling of the WCDMA RAN. Faulty equipment is detected by supervision functions or self-tests in equipment. The operator is notified about the fault and automatic actions are taken by the system to minimize the effect of a fault. The notification together with the associated documentation provides a guide for correcting a fault.

• Performance management: This feature allows the operator to monitor the performance of the WCDMA RAN. Performance Statistics provides an overview of the WCDMA RAN status. Performance Recordings and General Performance Event Handling provide the means to analyze the traffic situation in detail. The feature provides the means for detailed trouble-shooting and data collection for the purpose of network optimization and tuning.

• Security Management: This feature provides protection of Internet protocol (IP) based O&M applications. The main functions are:

• Application Server (AS)

• Single Logon Server (SLS)

• Public Key Servers (PKS)

• Firewall protection and authentication

• Integrity protection

• Encryption of CORBA traffic

SERVICES AND RABS FUNCTIONALITY

WCDMA RAN role is to provide and maintain positioning, emergency call and data transport services between the CN and UEs. • WCDMA RAN positioning services provide the UEs position

at a certain resolution. These services can be used for network

WCDMA RAN Operation

- 16 - © Ericsson 2007 LZT 123 7371 R5A

purposes (roaming, emergency calls…) or for end-user purposes (yellow pages…).

• WCDMA RAN emergency call service ensures that, at any time, emergency calls can be set up with an acceptable establishment rate.

• WCDMA RAN data transport services are provided as Radio Access Bearers (RAB). Conversational RABs, Streaming RABs, Interactive RABs, Background RABs and combined RABs can be established over the WCDMA RAN with pre-defined traffic requirements.

RADIO NETWORK FUNCTIONALITY

Radio Network control provides functionality for connection control (initiating, maintaining, and terminating user connections for RAB services). It also includes functionality related to mobility, capacity optimization, synchronization, and functionality that relates to either common information or common resources.

The Radio Network control functionality is divided into the following three subgroups: • Connection control functions-Establishes and releases RABs

and associated functionality.

• Mobility control functions-Tracks UE movement in the Radio Network.

• Capacity control functions-Manages the capacity, admission and congestion control, as well as radio channel power control.

TRANSPORT NETWORK FUNCTIONALITY

The Transport Network connects the WCDMA RAN nodes, OMINF servers and OSS-RC.

The Transport Network can be built either with: • External ATM and Plesiochronous Digital Hierarchy (PDH)

and Synchronous Digital Hierarchy (SDH) equipment,

• External DSL/Ethernet equipment.

• Direct connections such as fiber lines, copper lines or microwave systems.

Connections between NEs use either: • ATM-based transport protocols.

• IP-based transport protocols, however only for some interfaces and types of traffic.


LZT 123 7371 R5A © 2007 Ericsson - 17 -

The NEs can thus be interconnected either through direct physical layer transmission services, such as those provided by a PDH, SDH or DSL network, or through an intermediate ATM or Ethernet network.

The RNC, RBS and RANAG products include ATM, AAL2 and Internet Protocol (IP) network node functions.

ATM is used because of the efficiency of packet data technology and the built-in Quality-of-Service support. This enables the network to carry a combination of delay-sensitive traffic (such as voice) and best-effort data traffic.

IP is used when concentration of traffic is possible, in order to reduce costs and simplify network management.

Each node contains Internet Protocol (IP) routing functionality for the WCDMA RAN O&M Intranet. This means that all nodes are accessible from servers in OMINF and from OSS-RC. No separate management transport links are required because the IP network can be carried over the same physical link as the user data.

The RNC, RBS and RANAG nodes can be configured with the following physical layer interfaces for connections between NEs:

• E1: 2 Mbps

• J1: 1.5 Mbps

• T1: 1.5 Mbps

• E3: 34 Mbps

• T3: 45 Mbps

• STM-1: 155 Mbps

• Channelized STM-1: 155 Mbps (63/21xE1 or 84/24xT1/J1)

• GigabitEthernet: 1000 Mbps

O&M INFRASTRUCTURE FUNCTIONALITY

The O&M Intranet interconnects all NEs in the WCDMA O&M system, using the IP technology. O&M traffic can use the same physical links as the traffic between the RNC, RBS and RANAG, or separate dedicated links.

O&M Intranet is an IP network, which uses the TCP/IP protocol stack. As all IP networks, it requires a number of support functions.

WCDMA RAN Operation

- 18 - © Ericsson 2007 LZT 123 7371 R5A

OMINF collects these support functions, which provide the software and hardware functionality together with a number of services for designing and implementing the complete O&M Intranet. The software part of OMINF is a mixture of third-party software and Ericsson-developed software.

The figure below describes the Operation and Maintenance Infrastructure used to manage the WCDMA RAN.

Security Solution• Application Server• PKS• SLS

Security Solution• Application Server• PKS• SLS

IP Network Services• DHCP• DNS• NTP• FTP

IP Network Services• DHCP• DNS• NTP• FTP

Alex Server• Web Server• ALEX Server

Alex Server• Web Server• ALEX Server

NMSNMS

OSS-RC ServerOSS-RC Server

Backup Solution• Backup server• Backup robot

Backup Solution• Backup server• Backup robot

Network Infrastructure• O&M router• Network switch• Firewall

Network Infrastructure• O&M router• Network switch• Firewall

RNCRBS RXI

Figure 1-6: O&M Infrastructure

OSS-RC FUNCTIONALITY

Operation Support System Radio Core (OSS-RC) is an extensive tool for supervision, configuration, deployment and optimization of 2G and/or 3G network infrastructures. It merges three sub-network management systems, GSM-OSS, RANOS and CN-OSS together.

OSS-RC has constant and direct access to the WCDMA RAN Nodes via the O&M Intranet. It provides a solid view of WCDMA RAN information, such as alarms, configurations, and basic performance and it includes functionality to perform coordinated tasks over several Nodes in the WCDMA RAN, and repetitive tasks where the same or similar operations are performed on multiple Nodes.


LZT 123 7371 R5A © 2007 Ericsson - 19 -

In addition, OSS-RC facilitates the integration of existing management systems with WCDMA RAN using a variety of standard interfaces and protocols. Its main functionalities for RAN are: • Configuration Management

• Fault Management

• Performance Management

• Security Management

TEMS FUNCTIONALITY

Test Mobile System (TEMS) provides tools for the planning and prediction of the WCDMA Radio Network. The tools are suitable both for initial Radio Network, and support for expansion planning.

The planning process generates radio configuration data that can be downloaded to the traffic nodes through OSS-RC. TEMS is a separate product offer from Ericsson, and not explicitly part of WCDMA RAN.

The TEMS CellPlanner is used to provide common coverage maps, neighbor cell information, and transmission network plans. This makes the process of designing and deploying the WCDMA network in coordination with a GSM network straightforward.

The TEMS CellPlanner runs on a PC (Windows NT). It can be used standalone to perform planning and design of the WCDMA RAN, as well as in coordination with OSS-RC.

TEMS CellPlanner imports existing network data. It simulates, predicts and graphically displays coverage, capacity, and traffic quality.

The tool supports GSM integration, including importing of a GSM site and cell data to enable GSM site reuse and GSM handover planning, including GSM neighboring cell generation.

WCDMA RAN Operation

- 20 - © Ericsson 2007 LZT 123 7371 R5A

Intentionally Blank

2 WCDMA RAN System Description

LZT 123 7371 R5A © 2007 Ericsson - 21 -


This module describes the WCDMA Radio Access Network System.

OBJECTIVES


• Detail the WCDMA RAN System Architecture, and its partition in Radio Network Subsystems (RNS),

• Explain the role and functions of a RNS,

• Explain the role of the Iu interface,

• Explain the inter-RNS mobility over the Iur interface,

• Describe the role and architecture of the RNC-RBS subsystem,

• Explain the role of the Iub interface,

• List the structure and functions of WCDMA RAN nodes, RNC, RBS and RXI.

Figure 2-1: Objectives

WCDMA RAN Operation

- 22 - © Ericsson 2007 LZT 123 7371 R5A

Intentionally Blank


LZT 123 7371 R5A © 2007 Ericsson - 23 -

OVERVIEW This module describes in details the WCDMA RAN System, with a top-bottom approach.

WCDMA RAN contains several Radio Network Subsystems (RNS), each of which providing all the WCDMA RAN Services over a specific geographic area. An RNS contains one Radio Network Controller (RNC) and several RNC-RBS subsystems.

The RNC-RBS subsystem is a critical part of an RNS. It ensures the working of the radio interface and implements the Iub interface. The RNC-RBS subsystem provides an adaptable, reliable solution, with easy management, for the very different radio interface configurations, transport conditions and geographical situations encountered on the WCDMA RAN.

The WCDMA RAN node types are RNC, Radio Base Station (RBS) and RAN Aggregators (RXI), all based on the Ericsson Connectivity Packet Platform (CPP). They contain hardware and software resources needed to implement WCDMA RAN services.

RADIO NETWORK SUBSYSTEM This section describes Radio Network Subsystems (RNS) in terms of position in WCDMA RAN, internal architecture and functions.

WCDMA RAN is geographically partitioned into several RNSs. An RNS implements services and RABs between Core Network and User Equipments over a geographical area.

All RNSs are meshed, in order to ensure mobility over the WCDMA RAN. The interface between two RNSs is called Iur.

An RNS contains one RNC, the RBSs controlled by this RNC and may contain some RXIs.

WCDMA RAN Operation

- 24 - © Ericsson 2007 LZT 123 7371 R5A

WCDMA RAN

Core Network

Uu

IurIur

Iur

IuIu Iu

RNS

Uu Uu

RNS

RNS

Figure 2-2: WCDMA RAN partition

SERVICES AND RABS

The role of the RNS is to provide services and carry Radio Access Bearers between the Core Network and the User Equipments.

The types of services are Positioning, Emergency Calls, QoS profiling, Conversational RABs, Streaming RABs, Interactive RABs, background RABs and combined RABs.

IU INTERFACE

An RNS is connected to the Core Network through the Iu interface.

The Iu interface is made of two parts: • The Iu Packet-Switched (IuPS) interface towards the Serving

GPRS Service Node (SGSN)

• The Iu Circuit-Switched (IuCS) interface towards Media Gateway (MGw) and Mobile Switch Centre (MSC).

An RNS can be connected to various Core Network Nodes of the same type, via the feature called IuFlex. This feature allows implementing SGSN/MSC in pool and Multi-Operator Core Network (MOCN) features.

Iu PS

The IuPS interface carries:


LZT 123 7371 R5A © 2007 Ericsson - 25 -

• The Radio Access Network Application Part (RANAP) protocol towards the SGSN,

• The User Plane for packet-switched traffic towards the SGSN.

Iu CS

The IuCS interface carries:

• The Radio Access Network Application Part (RANAP) protocol towards the MSC,

• The User Plane for circuit-switched traffic towards:

o the MGw in a split/layered architecture.

o The MSC in a monolithic architecture.

IUR INTERFACE

In WCDMA RAN, User Equipments can move from the coverage area of one RNS to the coverage area of another RNS.

If the Iur Mobility feature has been implemented, traffic from User Equipments, which have an established dedicated connection (Cell_DCH state) towards the Core Network, and which are moving from one RNS to another RNS, is forwarded from the Drift RNS (DRNS) to the Serving RNS (SRNS) using the Iur interface.

The Iur interface carries: • The Radio Network Subsystem Application Part (RNSAP)

protocol between RNSs,

• The User Plane traffic, for UEs in Cell_DCH state, between RNSs.

If the Iur Mobility is not implemented, a Core Network Hard Handover (CNHH) is performed .

RNC-RBS SUBSYSTEM This section describes the RNC-RBS subsystem, which is a critical part of WCDMA RAN. Indeed, because of the distance and propagation techniques used between RNC and RBS, it can be considered as the weakest link of the network. Moreover, because of cost issues, the bandwidth available is limited. Still, the link and the RBS have to carry the traffic, vital synchronization signals, and with the highest possible MTBF. On the following chapters, we will see that dedicated O&M applications are designed to provide quick and efficient localization of faults on this art of the network.

WCDMA RAN Operation

- 26 - © Ericsson 2007 LZT 123 7371 R5A

The RNC-RBS subsystem implements and controls the radio network cells over the area covered by the RBS.

Control and User Plane traffic is carried over the Iub interface in the RNC-RBS subsystem.

ARCHITECTURE

The RNC-RBS subsystem contains the followings: • Complete RBS hardware and software,

• ATM transport resources in the RNC,

• Hardware and software resources on the RNC used to control the RBS,

• Hardware and software resources on the RNC used to control Radio Network Cells associated with the RNC-RBS subsystem,

• Hardware and software resources on the RNC used to control UE connections and process UE data.

In the RNC, RNC Modules are in charge of the above tasks for several RNC-RBS subsystems at a time. The use of RNC modules increases the robustness of the system, while providing pooled resources.

RNS

RNC

User Equipments

RNCModule RNC-RBS

SubsystemRNC-RBSSubsystem

RNC-RBSSubsystem

Figure 2-3: RNC-RBS Subsystem


LZT 123 7371 R5A © 2007 Ericsson - 27 -

LOCAL CELLS

A local cell consists in the hardware and software implementing one sector on one carrier within the RBS. Yet a local cell is not operational by itself; a UTRAN cell in the RNC is linked to the local cell in the RBS, to provide a fully operational Radio Cell.

Local cells are defined and configured during RBS commissioning.

Figure presents local cells for an RBS with 3 sectors and 1 carrier, which corresponds to 3 local cells in total.

Figure 2-4: Local cells.

UTRAN CELL

In the RNC, logical cells are implemented for each local cell of the RBS, and are called UTRAN Cells.

Parameters

A UTRAN Cell contains several sets of parameters:

WCDMA RAN Operation

- 28 - © Ericsson 2007 LZT 123 7371 R5A

• Cell position,

• Capacity management parameters,

• Common channel parameters,

• Mobility parameters,

• Congestion control parameters,

• Admission control parameters.

Channels

Each UTRAN cell also implements common and dedicated channels, to control and carry UE connections: • Forward Access CHannel (FACH), is a downlink common

channel, and carries Control and User Plane data. This is a mandatory common channel for every UTRAN Cell.

• Random Access CHannel (RACH), is an uplink common channel, and carries Control and User Plane data. This is a mandatory common channel for every UTRAN Cell.

• Paging CHannel (PCH), is carrying the paging messages towards the UEs. This is a mandatory common channel for every UTRAN Cell.

• High-Speed Downlink Shared CHannel (HS DSCH) is a downlink shared channel carrying User Plane for HSDPA RABs. This channel is defined whenever HSDPA is implemented on the UTRAN Cell.

• Enhanced Dedictaed Channel (E-DCH) is an uplink dedicated channel carrying User Plane for EUL RABs. This channel is used whenever EUL is implemented on the UTRAN Cell.

Mobility

UTRAN Cells also handle mobility; a UTRAN Cell can have:

• UTRAN relations for handovers with adjacent UTRAN Cells,

• GSM relations for handovers with GSM cells,

• Coverage relations for HSPA to non-HSPA enabled UTRAN Cells on the same sector.


LZT 123 7371 R5A © 2007 Ericsson - 29 -

Figure 2-5: UTRAN Cells.

IUB INTERFACE

The Iub interface is the logical link between an RNC and an RBS. It practically implements the reference between one UTRAN and one local cell.

The Iub interface transmits: • Synchronization data,

• User Plane data,

• Node B Application Part Common (NBAP-C) signaling messages,

• Node B Application Part Dedicated (NBAP-D) signaling messages

The Iub has several protocol layers: the Physical Layer, the ATM Layer, the ATM Adaptation Layers and the Radio Network Layer.

WCDMA RAN Operation

- 30 - © Ericsson 2007 LZT 123 7371 R5A

Figure 2-6: Iub Interface.

Radio Network Layer

Synchronization Data

Synchronization data is exchanged by the RNC and the RBS, in order to ensure synchronized transmission of data over the air interface, especially during handovers.

Synchronization data is carried over an ATM VC using ATM Adaptation Layer 0 (AAL0).

User Plane

The User Plane carried by Iub corresponds to end-user traffic, RNC to UE signaling and CN to UE signaling.

User Plane traffic is carried by AAL2 connections, defined over a number of AAL2 Paths.

NBAP-C

NBAP-C signaling protocol is used by the RNC to control RBS parameters that are not related to any particular UE, like the configuration of common transport channels or the creation of communication contexts.

NBAP-C signaling is carried over ATM using User-to-Network Interface- Signaling ATM Adaptation Layer (UNI-SAAL) protocol.


LZT 123 7371 R5A © 2007 Ericsson - 31 -

NBAP-D

NBAP-D signaling protocol is used for procedures that are related to a specific UE context in the RBS.

NBAP-D signaling is carried over ATM using User-to-Network Interface- Signaling ATM Adaptation Layer (UNI-SAAL) protocol.

ATM Transport

The main transport technology used between RNC and RBS is ATM, implementing the concepts of Virtual paths (VP) and Virtual Channels (VC).

The main interest in using the ATM technology, beside its reliability, its Quality of Service (QoS) features and its maturity, is that it isolates traffic at the Radio Network level from physical layer issues and transport network architecture.

This major advantage of ATM is particularly interesting for Iub transport, as RBSs are spread over a geographical area, with all the constraints involved in terms of distance, propagation conditions and environment.

It is also possible to carry Best Effort traffic between the RBS and the RNC over a DSL/Ethernet based transport network, while keeping delay-sensitive traffic over ATM. This solution can help reduce costs for highly loaded RBSs.

WCDMA RAN Operation

- 32 - © Ericsson 2007 LZT 123 7371 R5A

WCDMA RAN NODES This section describes the WCDMA RAN nodes RNC, RBS and RXI, with a top bottom approach.

Then the common CPP platform is described, highlighting the O&M features.

RNC

The RNC, as a radio network controller, handles the Iu interface towards the core network, the Iur interfaces towards the other RNCs for inter-RNS mobility, and the RNC-RBS subsystems via the RNC Modules.

The implementation of these functions is described in details below.

Layered architecture

A layer represents a hierarchical level offering services to the layer(s) above through a well-defined interface. Each layer consists of a number of subsystems.

The service layer provides the control services offered by the RNC, such as Radio Network Control, functions for paging of UEs, signalling connection handling and Radio Access Bearer service handling. The following subsystems are included: RNH and UEH. It contains only software, no hardware.

The encapsulation layer hides how the resources in the resource layer are implemented. The following subsystem is included: DRH. It contains only software, no hardware.

The resource layer provides user and control plane resources administrated and controlled by the RNC. Examples of such resources are resources for Iu/Iub frame protocol handling, Uu L2 protocol handling. The following subsystems are included: DCS, CCS and PDR. It contains only software, no hardware.

The platform layer provides basic support to the other layers, for example an operating system, necessary internal communication mechanisms, mechanics and power. The following parts are included: RLIB, TAS, MPE and CPP. It contains both software and hardware.


LZT 123 7371 R5A © 2007 Ericsson - 33 -

Figure 2-7: RNC layered architecture

Service Layer

Figure 2-8: RNC Service Layer

Radio Network Handling (RNH)

The main functions of this subsystem are as follows:

Configuration management for logical radio resources:

Enables the user of the Mur interface to configure the radio network areas (URA, RA and LA), cells, common channels and their relations and also to configure system resources (RNC ID, Core Network identities, scrambling code sets and so on).

WCDMA RAN Operation

- 34 - © Ericsson 2007 LZT 123 7371 R5A

The user can also configure and establish, lock, unlock and remove signaling bearers through the Mur interface. Locking and unlocking can be performed on logical radio network resources, such as cells and common channels.

Control and mobility functions on common channels:

These include cell update, paging and system information distribution.

Capacity management:

These include power control on common channels, admission control and congestion control.

Handling of signaling bearers towards the Core Network:

The following is provided for RBSs and other RNCs to carry control signaling specified by the NBAP, RANAP and RNSAP protocols: • Supervision, error and redundancy handling message

distribution of:

the RANAP protocol

the NBAP protocol

the RRC protocol.

• Message termination of:

the common part of the RANAP protocol

the common part of the NBAP protocol

the global part of the RRC protocol

the RNSAP protocol.

Enables traffic functions to allocate and de-allocate RNTI, uplink scrambling codes and downlink channelization codes.

User Equipment Handling (UEH)


Configuration management: • Enables the user of the Mur interface to configure, for example,

timer values that are to be used in RRC signaling and mapping from RABs to RBSs and vice versa. Provides termination and message distribution of the dedicated part of RRC protocol.

• Termination of the dedicated part of the NBAP and RANAP protocols.


LZT 123 7371 R5A © 2007 Ericsson - 35 -

• Keeps track of the RRC State of each UE and the resources allocated to each UE in the RNC.

• Handles the setup and release of a signaling connection from the Core Network to the UEs.

• The signaling connection consists of an RRC connection from the RNC towards the UE and an Iu control plane connection from the RNC towards the Core Network.

• Transparent Message Transfer.

• Handling the setup and release of radio access bearers from the Core Network to the UE.

Radio Connection Supervision: Supervise control and user plane connections between the UE and the UTRAN. • Handover evaluation.

• Soft/Softer handover execution and handover between RNCs are also supported.

• Inter-Radio Access Technology Handover.

• Inter-Radio Access Technology Cell Change.

• UE Security Handling.

• Channel Switching.

• UE positioning.

• Compressed Mode Control.

• Inter Frequency handover.

Encapsulation Layer

Figure 2-9: RNC Encapsulation Layer.

WCDMA RAN Operation

- 36 - © Ericsson 2007 LZT 123 7371 R5A

Device and Resource Handling (DRH)

This subsystem is used by the Service layer to reserve and release resources implemented in the resource Layer

Resource Layer

Figure 2-10: RNC Resource Layer.

Dedicated Channel Support (DCS)


Iub Frame Transport for dedicated channel:

Transfers data and control frames between the RNC and the RBS over the Iub interface. In DCS, this includes frame handling of the DCH frame protocol.

Iu-c Frame Handling:

Transfers user plane data between the circuit-switched CN and RNC over the Iu-c interface, including frame protocol termination.

MAC-C - MAC-D Frame Transport:

Transfers data and control frames between RNC nodes over the Iur interface. In the case of a single RNC node, this Iur protocol is used internally between DCS and CCS SP processors.

Uu L1 Termination of Dedicated Channels:


LZT 123 7371 R5A © 2007 Ericsson - 37 -

Terminates the Uu L1 part that is handled by the RNC. This mainly includes the diversity handling of several legs in soft handover for dedicated channels.

In the uplink, the function also extracts Uu L1 measurement information that is needed by other RNC functions.

Uu L2 Termination:

Specifies the configuration and termination of the RLC and MAC-D protocols within the RNC. The protocols terminate the layer 2 signaling between the UE and the RNC.

RLC mainly handles segmentation, concatenation, buffering and ARQ.

MAC mainly handles scheduling; including choosing the transport format and flow handling between MAC-C and MAC-D.

The MAC-D and RLC protocols also handle ciphering when requested by the UE Security Handling function.

Uu L3 Termination:

Specifies the configuration and termination of the RRC protocol within the RNC. The protocol terminates the layer 3 control signaling between a UE and the RNC. Only RRC termination on SP is included in DCS. The rest of the RRC functionality is in UEH.

RNH and CCS handle the termination of the global part of RRC.

Frame synchronization:

Provides synchronization of uplink and downlink frames. In the downlink, in order to be transmitted on the air interface at a particular transmission time frames are synchronized.

The Connection Frame Number (CFN) and Transmission Time Instant (TTI) define the time at which the RNC has to send the frame to the RBS so that the frame is transmitted at the correct transmission time.

In the uplink, frames are synchronized towards the CN and also form a base for the macro diversity function.

Handover Evaluation:

WCDMA RAN Operation

- 38 - © Ericsson 2007 LZT 123 7371 R5A

Handles the handover evaluation for a number of handover functions. This is applicable for UE on dedicated transport channels and will provide the best possible continuous radio environment for the UE and the radio network.

Power Control, Dedicated Channels:

The uplink outer-loop includes calculating a quality target, which is the signal to interference ratio that is used by the inner-loop in the RBS.

Channel Switching Evaluation:

Monitor the traffic volume and buffer sizes. Based on these values the RNC can suggest changes in used transport channels

Common Channel Support (CCS)


Iub Frame Transport for common channel:

Transfers data and control frames between the RNC and the RBS over the Iub interface. In CCS, this includes frame handling of the FACH, RACH and PCH frame protocol.

Iur Frame Transport:

This function transfers data and control frames between RNC nodes over the Iur interface. In the case of a single RNC node, the Iur protocol is used internally between DCS and CCS SP processors.

MAC-C - MAC-D Frame Transport:

Transfers data and control frames between RNC nodes over the Iur interface. In the case of a single RNC node, the Iur protocol is used internally between DCS and CCS SP processors.

Uu L2 Termination:

Specifies the configuration and termination of the RLC and MAC-C protocols within the RNC. The protocols terminate the layer 2 signaling between the UE and the RNC.

RLC provides data segmentation/sequential sending from RNC to UE.


LZT 123 7371 R5A © 2007 Ericsson - 39 -

MAC-C maps the logical channels to transport channels. MAC-C schedules packets from the global part of RRC and QoS queues according to their priority, and selects suitable transport formats for each FACH from set transport format combinations. MAC-C also selects the transport formats for PCH.

Uu L3 Termination:

Specifies the configuration and termination of the global part of the RRC protocol within the RNC. The protocol terminates layer 3 control signaling (RRC) between the UE and the RNC.

Only RRC termination on SPB is included in the CCS. The rest of the RRC functions are in RNH.

UEH and DCS handle termination of other parts of RRC, excluding the global part.

Paging:

Specifies the configuration and data transport of UE paging within the RNC. Paging functions on SPB is included in CCS. The rest of the paging functions are in RNH.

Frame Synchronization:

This function provides synchronization of downlink frames be-tween the RNC and the RBS. The frames are synchronized for transmission on the air interface at a certain transmission time.

The Connection Frame Number (CFN) and Transmission Time Interval (TTI) define the time at which the RNC needs to send the frame to the RBS.

Configuration Control:

The configuration data from RNH is sent through the control agent (in the RLIB subsystem on the MP) to the control agent in the CCS subsystem (on the SP) and then further to the SP processing entities (in the CCS).

Packet Data Router (PDR)


UDP/IP termination: This protocol is terminated in the RNC and in the packet-switched Core Network.

WCDMA RAN Operation

- 40 - © Ericsson 2007 LZT 123 7371 R5A

GTP-U termination: This protocol is terminated in the RNC and in the packet-switched Core Network. It acts as a multiplexing layer for user data packets that belong to different radio access bearers.

LLC/SNAP termination: This protocol is terminated in the RNC and in the packet-switched Core Network. It indicates the protocol that is carried in an LLC/SNAP frame. (Both IP and the Inverse ATM Address Resolution Protocol (InATMARP) are used on top of AAL5).

User data forwarding: In the downlink direction, this function forwards user data packets coming from GTP-U tunnels towards correct RLC connections.

In the uplink direction, this function forwards user data packets coming from RLC connections to the correct GTP-U tunnels to be transported towards the packet-switched Core Network.

Platform Layer

RNC Component Library (RLIB)

RLIB contains software only. Its main functions are as follows:

Component Library:

Packages used by other RNC subsystems containing common procedures, data classes and constants.

Examples of procedures provided by RLIB are: common restart functionality and MP-SP signaling support.

Application proxy: enables signaling between different OSE processes.

Load Control: secures real time characteristics and avoids restarts due to overload situations

Debug Support.

Timing and Synchronization (TAS)

TAS contains software only. It main functions are as follows:

Distribution of timing information:

This information is used for node synchronization by other subsystems in the RNC.


LZT 123 7371 R5A © 2007 Ericsson - 41 -

Mechanics, Power and Environment (MPE)

MPE contains both hardware and software and its main functions are as follows:

Building Practice: • Cabinet and sub-rack mechanics • Backplane • Cables • Fan External Processor (XP) • Interface Connection Field (ICF), which is used for

connecting external cables.

Power:

Capacitor Unit (CU), used for smoothing out irregularities in the power supply.

Software Architecture

Overview

Functions, which are common to the whole RNC, are centralised on the main sub rack MPs for example: • Configuration of RNC resources (O&M),

• Circuit Switched, and Packet Switched, control plane Core Network termination (RANAP termination),

• UE Register (a common table where the RNC module identity for a specific UE Context is stored)

• Timing Distribution

• Packet Switched User Plane Core Network termination

• SCCP termination

• Inter-RNS mobility control plane (RNSAP termination)

RNC functionality, which is specific to Cell, NBAP and UE handling is distributed to MPs located in the extension sub-rack (or those specific MPs in the main sub-rack which deal with Cell, NBAP and UE handling).

RNC applications with high real time requirements, such as user plane processing functions, are located on the Cello Special purpose Processor Boards (SPB). These applications are executed on the Support Processors (SP), which reside on the SPB boards.

WCDMA RAN Operation

- 42 - © Ericsson 2007 LZT 123 7371 R5A

There are also RNC applications on Board Processors (BP). These BPs are located on SPBs and Timing Unit Boards (TUB).

Figure 2-11: RNC Software Architecture Overview.

Software languages and runtime environment

The code used to implement applications in the RNC is produced in the form of Load Modules (LM). LMs consist of the code and all the necessary parameters and variables needed to enable the code to execute.

SP applications

SP applications are:

• Dedicated Channel (DC), which deals with RRC, RLC, Ciphering, MAC-D for dedicated channels as well as Diversity Handling (DHO). This means that control signalling, circuit switched connections and packet switched data connections are handled by the same SP. This RNC application uses AAL2 and AAL5, which are terminated in Cello.

• Common Channel (CC), which deals with RRC, RLC, MAC-C for Common Channels. This RNC application uses AAL2, which is terminated in Cello.


LZT 123 7371 R5A © 2007 Ericsson - 43 -

• Packet Data Router (PDR), which deals with UDP/IP, GTP-U. Packet Data is mapped in both directions between Iu and UE (GTP-U tunnel endpoint is mapped into RLC reference and vice versa). This RNC application uses AAL5, which is terminated in Cello. PDR is only implemented in the RNC modules of the main sub-rack. Only 5 PDRs are defined, irrespective of the size of the RNC.

• Common Channels over the Iur interface (IurCC) is not used anymore in the RNC.

Definition of RNC Module

The RNC Module divides the RNC sub-rack into smaller manageable, logical modules.

Each module is responsible for controlling a number of RBSs, the part of the radio network implemented on these RBSs, and the UeContext handling initiated in this part of the radio network.

In terms of hardware an RNC Module consists of an MP (GPB) and a number of SPB-boards. This MP is called a “RNC Module MP".

The number of SPB-boards is defined for each type of module, and can differ between different RNC Modules.

The RNC Module MP is loaded with two main applications, the UE Context handling (RncLmUe) and the radio network handling (RncLmCell) application.

The resources offered by these MP applications are pooled on RNC Module level only, i.e. the resources can’t be shared between the RNC Modules.

The SPs on the SP Boards (SPB) are loaded with a free distribution of DC/CC/PDR application. The distribution can differ between different SPBs.

An SPB type is an SPB with a specific distribution of SP applications. The resources offered by the SP applications are pooled on node level, i.e. the RNC Modules can share SP resources.

The SPB21 contains 5 SPs (Hardware product number = ROJ 119 2103/41), whereas the SPB contains 3 SPs (Hardware product number = ROJ 119 2103/2).

WCDMA RAN Operation

- 44 - © Ericsson 2007 LZT 123 7371 R5A

Redundancy and MP/SP type slot positions

• General

Redundancy is very important since if the RNC experiences disturbances it can impact several other nodes within the WCDMA RAN. Therefore the software has some redundancy features.

There is no MP resource sharing between RNC Modules so from a robustness point of view this gives a simple resource handling.

• Main sub-rack

All executing MPs in the main sub-rack have a standby MP. A standby MP is normally not executing any program. It is only standby for a MP in case of hardware failure.

The MP types of the main sub-rack are SSCP MP, RANAP/RNSAP MP, Central MP, O&M MP and Module MP.

The main sub-rack includes two RNC Modules.

The different SP types share the load within the RNC Module. E.g. there are three SPs in RNC Module 1 that will take care of the CC tasks and if the hardware of one of them fails there are still two left in the RNC Module that will share the load.


LZT 123 7371 R5A © 2007 Ericsson - 45 -

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 281 SB 2 1 1 1 2 2

MP MP MP MP MP MP MP MP MP MP MP

Type 1 Type 2 <-- RNC Module Type

SC

B3

ET

ET

ET

ET

SP

B21

SP

B21

SP

B21

SP

B21

GP

B52

GP

B52

GP

B52

SP

B21

GP

B52

GP

B52

GP

B52

GP

B52

GP

B52

GP

B52

GP

B53

GP

B53

TUB

2

TUB

2

ET

ET

SC

B3

SX

B3

SX

B3

Pdr

SP

B21 Type 1

SP

B21 Type 1

SP

B21 Type 1

SP

B21 Type 1

SP

B21 Type 1

Pdr

Pdr

Pdr

Pdr

Dc

Cc

Cc

Cc

Cc

Cc

Dc

Dc

Dc

Dc

Dc

Dc

Dc

RN

C M

odule MP

Stand-by

RN

C M

odule MP

RN

C R

anapRnsap M

P

RN

C R

anapRnsap M

P

Dc

Dc

Dc

Dc

Dc

Dc

Dc

RN

C S

CC

P M

P

RN

C S

CC

P M

P S

tand-by

RN

C C

entral MP

RN

C C

entral MP

Stand-by

RN

C O

&M

MP

RN

C O

&M

MP

Stand-by

RN

C M

odule MP

Slot

Main Subrack - SW Configuration

Figure 2-12: MP Types and SP Types in the Main sub-rack

• Main sub-rack RNC Module Allocation

The main sub-rack contains two RNC Modules of type 1 and 2.

In the main sub-rack there is one dedicated MP that act as stand-by for the two RNC module MPs (2 +1 MP HW redundancy).

PDR devices are only located in the Main sub-rack, 1 device per SPB board. This simplifies the connection to the Core Network, and reduces the reconfigurations during extension processes. • Extension sub-rack

The extension sub-rack only has one type of MP, the RNC Module MP, refer figure on next page..

WCDMA RAN Operation

- 46 - © Ericsson 2007 LZT 123 7371 R5A

Figure 2-13: MP types and SP types in the Extension sub-rack.

• Extension sub-rack RNC Module Allocation

Each extension sub-rack contains five RNC modules. Within the extension sub-rack there is one dedicated MP to act as stand-by for the five RNC module MPs (5 +1 MP HW redundancy).

RBS

RBS 3000 family Main Functions

The RBS is the implementation of the node denominated Node B in WCDMA system.

The Node B is a logical node responsible for radio transmission/reception in one or more cells to/from the UE. The Node B terminates the Iub interface towards the RNC.

The RBS functions are divided into the function groups listed below.

• Platform Functions

• Radio Transport Functions

• Synchronization Functions

• Bearer Functions


LZT 123 7371 R5A © 2007 Ericsson - 47 -

• Traffic Control Functions

• Infrastructure Functions

In this chapter, the RBS 3206 is highlighted. However, the exact same principles apply to other RBS types, with differences mainly concerning the hardware type used.

Node Architecture

The general RBS architecture is depicted in the figure below.

Basically, the functionality is divided into two main parts.

User plane functions this includes transport, base band, radio and antenna near parts.

Control plane functions for both traffic and O&M.

As a basis, there are infrastructure and platform functionalities that make all parts fit together.

Figure 2-14: RBS architecture

Function Allocation on Hardware

In the figures below, depicts the main functional blocks in the user plane, matched to the hardware of an RBS 3206.

WCDMA RAN Operation

- 48 - © Ericsson 2007 LZT 123 7371 R5A

Figure 2-15: Functional view of the user plane – RBS 3206.

Software Architecture

The RBS can be equipped with one or two MPs, implemented on the CBU board.

In case of two MPs only one will be active and runs both the traffic application software and handles the node external O&M interface, the other MP will be in cold standby mode.

RXI

RXI is the Ericsson implementation of the 3GPP RANAG. It is a CPP node, without specific application, unlike RNC and RBS nodes.

The RXI is a pure transport node, which is used to optimize the transport layer over the WCDMA RAN by aggregating traffic at ATM and AAL2 level.

RXI Management is a reduced version of RBS or RNC management, limited to transport functionalities.


LZT 123 7371 R5A © 2007 Ericsson - 49 -

CPP

Role and Structure

The CPP platform consists in the hardware and software base required to host the specific RNC, RBS or RXI features.

Distributed control system and management services: • Provides fundamental software execution platform services

(based on OSE Delta) for application programs, such as a fault tolerant database, a Java Virtual Machine (JVM) and a fault tolerant file system.

• Provides management of the operation and maintenance part of a RAN node, which is built with Java technology.

• CPP implements loading, fundamental configuration and restart functions.

ATM transport services: • Termination of the ATM based links, using AAL0, AAL1,

AAL2 and AAL5 based user channels

• Spatial switching of ATM cells within the node (the ATM switch is used to interconnect all types of processors).

IP transport services: • Termination and control of the Ethernet based links

Synchronization and timing services: • Network synchronization:

• Real time clock

• Clock distribution.

Redundancy

Redundancy in the CPP platform is implemented at various levels, in different ways, thus ensuring no single point of failure exist on the node. • Board redundancy. At board level, the CPP platform

implements 1+1 redundancy:

o 2 x SCBs in each subrack

o Active/Standby pair of GPBs for CPP control

o Active/Standby pair of TUBs for CPP synchronization

o 2 x ET-MF4 or 2 x ET-MC41 using an MSPG cable

WCDMA RAN Operation

- 50 - © Ericsson 2007 LZT 123 7371 R5A

• Link redundancy. At link level, the CPP platform can implement redundancy at the following levels

o 1+1 or 2+2 redundancy on Inter-Subrack Links (ISL)

o MSP 1+1 redundancy on STM-1 links, only for ET-MC41 and ET-MF4 boards.

• Traffic-related program redundancy.

o For programs in charge of the UTRAN traffic control, running on GPB boards, it is important not to lose parameters, states and status at GPB board failure. Reliable Program Uniters (RPU) ensure that traffic related programs are switched to a standby GPB board with no effect on the traffic. It does so by keeping an exact copy of the running program’s parameters, states and status on the standby GPB.

o Non RPU protected programs are restarted on the standby GPB at board failure, thus losing all context data.

• Moveable Connection End Point. The processor in charge of the full UTRAN Signaling protocol stack can be allocated directly by the CPP node, thus reducing the configuration of redundancy at higher layers. This is especially used for Iub links, reserving only once the bandwidth needed for signaling protocols.

The redundancy features are described in the figure below.

Figure 2-16: CPP Platform - Redundancy


LZT 123 7371 R5A © 2007 Ericsson - 51 -

Logical Architecture

The figure below describes the CPP platform logical architecture.

Figure 2-17: CPP Platform Logical Architecture

Operating System

The CPP operating system is called OSE Delta (Operating System Ericsson Delta), and supports operation of the CPP platform.

Resources

Accessible and visible resources in a CPP node are the Cello Database, the file system and the Management Information Base (MIB). • Cello Database (DB): The Cello DB is used for live data

storage and retrieval. It is a real-time database stored in the primary MP of a CPP node. Fault tolerance is implemented via the mirroring of this Cello DB in a standby MP.

• File System: The files system in CPP allows persistent storage of data, and is implemented on the flash disks of the various CPP boards.

• MIB: The Management Information Base is a model of the hardware and software resources, enabling configuration, operation and statistics collection on CPP hardware and software resources.

Adaptation Layer

Several CPP entities in the adaptation layer allow access to CPP resources in a controlled fashion.

WCDMA RAN Operation

- 52 - © Ericsson 2007 LZT 123 7371 R5A

• Configuration Service (CS) implements configuration functions towards the MIB.

• Fault Manager (FM) implements fault handling and alarm notification towards the MIB.

• Performance Manager (PM) implements performance recordings (scanner), collecting statistics from selected MIB entities.

• Node Command Line Interface (NCLI) implements configuration and fault management access to the MIB.

• Command Line Interface (CLI/COLI) implements basic access to the Cello DB and file system for management of basic CPP functions.

Access Servers

The CPP platform implements a number of support functions providing access to CPP resources via standard communication protocols: • ORB: Object Request Broker Server terminating CORBA

requests.

• HTTP: HTTP server used for EMAS/OE access.

• FTP: FTP Server used for file transfer during software upgrades and ROP files collection.

• SSH: Secure Shell Server to access a node in secured mode.

• SFTP: Secure FTP Server for file transfer to/from a node in secured mode.

• Telnet: telnet server.

3 Customer Product Information

LZT 123 7371 R5A © 2007 Ericsson - 53 -


This module describes the Customer Product Information (CPI) for WCDMA Radio Access Network.

OBJECTIVES

After this chapter the participants will be able to:After this chapter the participants will be able to:

• Use the Customer Product Information (CPI)

• Explain the CPI Library structure of the node

• Find information in the Library with use of regular expression

• Find operational instructions (OPI) and maintain the node according to the OPI

• Find additional information on an alarm and solve the problem with the help of the CPI and Element Manager


WCDMA RAN Operation

- 54 - © Ericsson 2007 LZT 123 7371 R5A

Intentionally Blank


LZT 123 7371 R5A © 2007 Ericsson - 55 -

OVERVIEW All Ericsson CPI can be accessed online and either browsed on screen using the Active Library Explorer (ALEX) or printed.

CPI is accessed through the Ericsson e-business portal on the Ericsson Extranet https://ebusiness.ericsson.net.

A user id and a password are required to access the CPI Extranet service. Access is provided by the Key Account Managers (KAMs) at the Ericsson Local companies.

To be able to access the site you need to check the following:

Your company allows access to secure sites (HTTPS) through its firewall. Your PC has either Microsoft Internet Explorer 5.01 or higher / Netscape navigator 4.73 or higher.

Note: Netscape v6.x is not supported. The recommended browser is Internet Explorer 6.0. If you use older or newly released browsers, some interruptions may occur.

Your browser has the plug-ins necessary to view or download PDF and Microsoft Office files.

ALEX supports the retrieval of document files in both HTML and PDF format. For PDF files, the software application used for display is Acrobat Reader 3.1 or higher. The CPI library is viewed by using the Active Library Explorer (hosted by a web server or a stand alone PC) together with standard web browsers, such as Netscape Navigator 4.06 (or higher) and Internet Explorer version 4.01 SP1 (or higher).

WCDMA RAN Operation

- 56 - © Ericsson 2007 LZT 123 7371 R5A

CPI STRUCTURE The generic CPI structure is the common high-level structure used for all Ericsson CPI. CPI is the technical information that the customer needs to handle Ericsson products throughout the product lifecycle.

The CPI library contains the complete set of CPI needed to plan, install, operate, troubleshoot, repair, and maintain a WCDMA RAN system. This allows the users to recognize the structure of the CPI library regardless of which system node they access.

Figure 3-2: CPI Structure.

Note: The CPI library for each node only contains product information for the relevant information categories, therefore not all categories are covered for each separate CPI library.

Example of the CPI information categories:

• Safety and Environmental Issues

• Presentation - for example Supplier's Declaration of Conformity

• Description - for example Node Descriptions, Network Impact Report

• Site Solution - for example Mounting Drawing


LZT 123 7371 R5A © 2007 Ericsson - 57 -

• Installation - for example Installation Instructions

• Verification - for example Verification Instructions

• Operation and Maintenance - for example Alarm Operating Instructions

• Interface - for example Quick Guides

• Spare Parts - for example Spare Parts Catalog

• End-of-Life - for example End-of-Life Treatment Plan

• Glossary of Terms

WCDMA RAN Operation

- 58 - © Ericsson 2007 LZT 123 7371 R5A

WCDMA RAN LIBRARY

This section describes the CPI library for the WCDMA RAN at the system-generic level (also called 'subsystem level' in the CPI) and the RAN Parameters library. Information is structured on an overview level intended for a general understanding of the WCDMA RAN system. The RAN library describes, on this system-generic level, all system nodes and interfaces, the WCDMA RAN features, functions and principles of operation.

The WCDMA RAN libraries are comprised of documents grouped in folders and sub-folders as shown in the following figure:

Figure 3-3: WCDMA RAN CPI Library


LZT 123 7371 R5A © 2007 Ericsson - 59 -

RNC LIBRARY

The RNC CPI libraries are mainly for personnel working with planning, deploying, operating and maintaining RNC equipment.

The RNC libraries are comprised of documents grouped in folders and sub-folders as described on the following figure:

Figure 3-4: RNC 3810 CPI Library

WCDMA RAN Operation

- 60 - © Ericsson 2007 LZT 123 7371 R5A

RBS LIBRARY

The RBS CPI libraries are mainly for personnel working with planning, deploying, operating and maintaining RNC equipment.

The RBS libraries are comprised of documents grouped in folders and sub-folders as described on the following figure:

Figure 3-5: RBS 3206 CPI Library

GETTING INFORMATION FROM CPI CPI implements searching tools in order to get relevant documentation from keywords.

A simple Search window is always present at the top of CPI windows, and is pointed on the figure below by arrow 1.

For more advanced searches, the Advanced Search window is accessible through the icon pointed by arrow 2 in figure below.


LZT 123 7371 R5A © 2007 Ericsson - 61 -

21

Figure 3-6: Simple and Advanced Search windows.

Figure 3-7: Result of “HSDPA” search on the RBS 3202 Library.

WCDMA RAN Operation

- 62 - © Ericsson 2007 LZT 123 7371 R5A

OPERATING INSTRUCTIONS Each operation on WCDMA RAN has to follow a set of procedures in order to ensure safety of operators, standard working conditions for equipment, consistency of data…

CPI libraries provide various Operating Instructions (OPI), describing particular procedures on the WCDMA RAN.

These OPIs describe, step by step, the process to configure a node, fix a fault, and perform tests.

Figure 3-8: BatteryChargingFailure OPI.

4 Operation and Maintenance Applications

LZT 123 7371 R5A © 2007 Ericsson - 63 -


This module describes the Operation and Maintenance Applications for WCDMA Radio Access Network.

OBJECTIVES


• Explain the 4 Operation and Maintenance Categories,

• List Embedded Element Management Functions

• Detail the O&M Intranet

• Detail the O&M Infrastructure

• Explain the principles of Operation Support System for Radio and Core

• Use the tools adapted for WCDMA RAN level management

• Use the tools adapted for RNS level management

• Use the tools adapted for RNC-RBS Subsystem level management

• Use the tools adapted for WCDMA RAN node level management


WCDMA RAN Operation

- 64 - © Ericsson 2007 LZT 123 7371 R5A

Intentionally Blank


LZT 123 7371 R5A © 2007 Ericsson - 65 -

OVERVIEW In this module the main principles for operation and maintenance of the Ericsson WCDMA Radio Access Network are explained.

Operation and Maintenance is divided in four categories: Configuration Management, Fault Management, Performance Management, and Security Management.

Embedded Element Management functions are implemented on every WCDMA RAN node. They allow configuring the nodes, performing fault management, collecting performance data and implementing security features.

In order to access and use these Embedded Element Management functions, an O&M network is needed. It provides reliable and secure communication between these functions and the several applications available for the operator.

Applications are used by the operator to access, configure and manage, Element Management functions. Each application is adapted to manage one particular subsystem in WCDMA RAN, from the WCDMA RAN System itself down to the WCDMA RAN node level, via the RNS subsystem and the RNC-RBS subsystem levels.

OPERATION AND MAINTENANCE CATEGORIES The O&M activities performed in WCDMA RAN can be divided into the following categories:

Configuration ManagementFault ManagementPerformance ManagementSecurity Management

Figure 4-2: O&M Categories.

CONFIGURATION MANAGEMENT

Configuration Management consists of Equipment handling, Software Management and Trans port/Radio Network configuration.

WCDMA RAN Operation

- 66 - © Ericsson 2007 LZT 123 7371 R5A

Equipment Handling 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 and backup of RNC, RANAG, and RBS node software and configuration data.

One part of Configuration Management is not covered on this course. It deals with the setting of parameters in NEs in the Radio Network (RN), in the Transport Network (TN) and in the equipment in WCDMA RAN.

FAULT MANAGEMENT

Fault Management consists in: • WCDMA RAN Fault Management Features: detect and report

failures in WCDMA RAN as soon as they occur and limit the effects. Fault Management brings additional or redundant equipment into operation, recovers the failure or reconfigures existing equipment, without human action.

• Fault Handling: Triggered by alarm reports, fault handling is a process by which a system engineer fix faults, using available applications; OSS-RC and Element Managers.

PERFORMANCE MANAGEMENT

Performance prfoile Functions within this area monitor the performance of WCDMA RAN and store the Performance Management data collected from WCDMA RAN in OSS-RC.

This data can then be processed via Ericsson solutions or external solutions.

SECURITY MANAGEMENT

Functions within this area handle and administer security features for preventing unauthorized access to the management system. These functions for the administration of users and access privileges are included, for example, in Single-Logon Servers (SLS).

OPERATION AND MAINTENANCE NETWORK Embedded Element Management is implemented in all NEs, which means that each node contains all functions for its management.


LZT 123 7371 R5A © 2007 Ericsson - 67 -

The role of the Operation and Maintenance network is to give access to these Embedded Element Management functions to system engineers in charge of configuring, supervising and operating the WCDMA RAN.

The Operation and Maintenance Network for WCDMA RAN is made of: • Local access facilities on each WCDMA RAN node.

• An O&M intranet, which implements an IP network over all WCDMA RAN nodes,

• An O&M Infrastructure which implements the tools for subnetwork management.

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.

LOCAL ACCESS

Each WCDMA RAN node can be accessed locally via direct physical connections. Local access is required for node commissioning, troubleshooting of nodes in case of extreme failure and when remote connection is impossible due to transmission failure.

Two types of connections are available for local access: • Serial access via an RS-232 connection

• Site LAN access via an Ethernet connection

WCDMA RAN Operation

- 68 - © Ericsson 2007 LZT 123 7371 R5A

Figure 4-3: Local Access

Logging into the AS/SLS in the O&M infrastructure allows accessing remote WCDMA RAN nodes.

O&M INTRANET

The O&M Intranet is an IP-based intranet that connects all managing nodes (OSS-RC, EMs) with the managed nodes (like RBS, RNC and RANAG) and the central O&M services (like the DHCP, NTP, DNS, and FTP Servers).

The O&M Intranet enables the NEs to be controlled remotely using OSS-RC and the RNC, RANAG, and RBS EMs. 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.

Remote Access to RNC, RANAG, and RBS

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-authorized access in 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.


LZT 123 7371 R5A © 2007 Ericsson - 69 -

The transport of O&M data to/from Network Elements from the Network Management Center is described in the figure below. It makes use of the traffic-carrying ATM transport network between Network Elements and the O&M Router.

RBS OSS Server

ATM ATM ATM ATM ATM ATM

AAL5 AAL5 AAL5 AAL5 AAL5 AAL5

IPoATM IPoATM IPoATM IPoATMIPoATMIPoATM

VC for Mub

VC for Mut

VC for Mur

IP

EthernetEthernet

RXI RNC O&M Router

O&M

IPIP IP IP

O&M O&M O&M

Figure 4-4: Remote Access - Cross Connection Scenario

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.

Furthermore, in order to provide a redundant, complete O&M solution, several servers are implemented to support documentation services, applications and backup.

This is provided in the OSS-RC product through O&M INfrastructure (OMINF).

The O&M 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.

WCDMA RAN Operation

- 70 - © Ericsson 2007 LZT 123 7371 R5A

Figure below shows a logical view of the O&M infrastructure.

Figure 4-5: The O&M Infrastructure

The O&M infrastructure consists of the functions described below:

DHCP Server

Dynamic Host Configuration Protocol.

Used only for equipment connected to Site Local Area Network (LAN) of NEs.

By implementing DHCP client and servers, 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.


LZT 123 7371 R5A © 2007 Ericsson - 71 -

NTP is used to synchronize computer clock times in a network of computers.

In the WCDMA RAN, NTP servers are required to synchronize clocks for all Network Elements, OSS-RC and all OMINF servers. The NTP is used for logging and time-stamping alarms. GPS System Clock (GSC) is used as the NTP time source.

UTRAN FTP Server

File Transfer Protocol (FTP), a standard internet protocol, is the simplest way to exchange files between computers. An FTP server is required in WCDMA RAN O&M Intranet in order to support two functions: Upgrade Packages (UP) or software installation to networks elements in WCDMA RAN radio nodes (RBS).

Backup or Configuration Version (CV) of the networks elements in WCDMA RAN radio nodes.

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.

SLS Server

Single Logon Server.

WCDMA RAN Operation

- 72 - © Ericsson 2007 LZT 123 7371 R5A

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 (AS)

A central execution environment for OSS-RC client 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, RANAGs, 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.

OPERATION AND MAINTENANCE APPLICATIONS


LZT 123 7371 R5A © 2007 Ericsson - 73 -

MANAGEMENT SYSTEM ARCHITECTURE

The Management System Architecture comprises three layers, presented in figure below:

Figure 4-6: Management System Architecture.

• 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 3rd generation (3G) and 2nd generation (2G) systems. Applications at that level are typically interfacing with systems like OSS-RC for Ericsson equipments. In-house tools developed by operators, and interfacing with OSS-RC, also fall in this category.

• The middle layer is the Sub network Management Layer. This layer controls and manages several nodes or subsystem at a time. OSS-RC is typically a Sub network Management System. On an Ericsson only WCDMA RAN network, OSS-RC implements also the Network Management Layer. Applications such as SMO and WCDMA RAN Explorer work at the sub-network level.

• The lowest layer is the Element Management Layer. This layer manages individual RNC, RANAG, and RBS nodes. It is used to configure the Radio Network and the Transport Network, together with software and hardware attributes of the NEs. NCLI, OE and EMAS are examples of Element Management application.

WCDMA RAN Operation

- 74 - © Ericsson 2007 LZT 123 7371 R5A

OPERATION SUPPORT SYSTEM FOR RADIO AND CORE (OSS-RC)

OSS-RC operates the WCDMA RAN including coordinated handling of tasks on multiple NEs and providing access for Network Management Systems. Although OSS-RC is not hosted by RNCs, RANAGs or RBSs like the Element Manager, the operator can access it from any location within the O&M Intranet.

For activities that are technology and supplier independent, such as alarm presentation and statistics reports, OSS-RC offers integration to existing systems.

OSS-RC Framework

OSS-RC contains several tools, adapted for different management tasks: Software Management organizer (SMO) for Hardware and Software Management, Alarm viewers for Fault Management, WCDMA RAN Explorer for Radio and Transport Network Configuration and Management.

These tools have a framework: a database in OSS-RC collects and/or receives information from the network elements in the WCDMA RAN. Then, a GUI-based, a Command-based, or an external application is used to access the database and/or send commands to the Network Elements.

ServerServer

RNCRBS RXI

DatabaseScripts

User Interfaces Standard Interfaces

Figure 4-7: OSS-RC Framework.


LZT 123 7371 R5A © 2007 Ericsson - 75 -

WCDMA RAN SYSTEM LEVEL MANAGEMENT

Management at the WCDMA RAN System level is possible thanks to a set of tools contained in the OSS-RC application, and described below.

OSS-RC Network Explorer

OSS-RC Network Explorer (ONE) GUI is the starting tool for management on the WCDMA RAN System level.

WCDMA RAN view

ONE presents a complete view of WCDMA RAN System, in different manners: • Site-based view

• RNS Sub network-based view,

• Network Element-based view (For RANAG nodes only).

Figure 4-8: OSS Network Explorer.

Tools

ONE provides access to tools, or range of tools, needed by the operator, at the WCDMA RAN level: • Configuration Menu

WCDMA RAN Operation

- 76 - © Ericsson 2007 LZT 123 7371 R5A

o Add/Remove Network Element (ARNE)

o Software Management Organizer (SMO) for equipment handling,

o WCDMA RAN Explorer for Radio and Transport Configuration Management. It provides access to a range of tools for WCDMA RAN supervision and operation.

o Transport Topology Viewer

• Alarm Menu

o Alarm Status Matrix,

o Alarm List Viewer,

• Performance Menu

o Subscription Profile Manager,

• Administration Menu

o Log Viewer.

Add/Remove Network Element (ARNE)

ARNE is used to add, modify or remove a Network Element from OSS-RC.

A WCDMA RAN node can operate by itself, without connection to OSS-RC. Yet, in order to manage, monitor and configure this node remotely, collect performance data and supervise it, most of the operators use OSS-RC.

OSS-RC needs to be aware that the node exists in the WCDMA RAN. ARNE is used to define, in OSS-RC, where is the NE located, what type of NE it is, on which software and hardware version it runs, and how to access it.

Figure below presents the ARNE tool; the last step, when using ARNE, provides a summary of parameters defined.


LZT 123 7371 R5A © 2007 Ericsson - 77 -

Figure 4-9: ARNE.

It is possible to later modify parameters for this NE, such as the IP address or the security level. ARNE also allows deletion of NEs in OSS-RC.

Software Management Organizer (SMO)

SMO is the application used for remote software handling and hardware listing activities towards WCDMA RAN nodes.

NIO, for Network Inventory Organizer, is a subsystem of SMO in charge of hardware activities.

Framework

The SMO tool implements a server containing a database and a file store, and allows running commands towards the WCDMA RAN NEs.

WCDMA RAN Operation

- 78 - © Ericsson 2007 LZT 123 7371 R5A

Figure 4-10: SMO Framework

SMO Graphical User Interface

SMO provides a process oriented working environment for the user, and uniform software handling for all CPP-based nodes. With the graphical user interface of SMO, the operator may supervise parallel activation jobs towards multiple network elements from a single terminal.

SMO provides the following functions: • Software inventory, including compare between network

elements

• Software distribution from OSS to network elements

• Remote software upgrade

• Monitor upgrade jobs towards multiple network elements in parallel

• NE Backup administration, including transfer of NE backups to OSS

• Automatic Correction Deployment from Ericsson

• Uniform handling of different network element types

• Distribute license key files to CPP network elements


LZT 123 7371 R5A © 2007 Ericsson - 79 -

Figure 4-11: Software Manager Organizer GUI

SMO Command Line Interface

A command Line interface is also available for SMO, providing the exact same functionalities than the GUI, plus the possibility to export software information in an XML file.

Network Inventory Organizer

The NIO functionality (hardware inventory) is also available from the SMO GUI. NIO is implemented over the SMO database, and can be used to perform hardware to software compliance checks during upgrade, hardware inventory reports and listings.

NIO provides the following functions: • Collection of hardware data from the network.

• Export of hardware data to external inventory management systems.

NIO GUI

The NIO GUI is embedded into the SMO GUI, on the Hardware tab. It can list the sub racks for a NE or a group of NEs, and the boards on a sub-rack.

WCDMA RAN Operation

- 80 - © Ericsson 2007 LZT 123 7371 R5A

NIO CLI

A command Line interface is also available for NIO, providing the exact same functionalities than the GUI, plus the possibility to export software information in an XML file.

Figure below presents how NIO is started from a terminal window, as well as a few NIO commands.

Figure 4-12: NIO CLI

WCDMA RAN Explorer

WCDMA RAN Explorer is the tool used for Radio and Transport Network Configuration Management, at the WCDMA RAN System level.


LZT 123 7371 R5A © 2007 Ericsson - 81 -

Framework

WCDMA RAN Explorer uses, for WCDMA RAN configuration, a dedicated framework called Configuration Service (CS), described in the figure below.

Figure 4-13: Configuration Service Framework

The Configuration Service Framework maintains an up-to-date image of the real WCDMA RAN network transport and radio configuration, in the Valid Configuration.

Configuration procedures are performed on offline copies of this valid configuration, called planned configurations, using the Bulk Configuration manager (BCM) tool.

For backup purpose, Fallback Areas are introduced, storing WCDMA RAN radio and/or transport configuration backups, that can be restored at a later stage in case of major network outage.

User Interface

WCDMA RAN explorer provides a batch configuration tool, called Bulk Configuration, for both Transport and Radio Network. It uses XML files to import or export configuration data.

It is also the access point to WCDMA RAN specific tools such as Node Status Analyzer (NSA), Element Management Application and Support (EMAS) and Cell/Channel Manager.

WCDMA RAN Operation

- 82 - © Ericsson 2007 LZT 123 7371 R5A

WCDMA RAN Explorer contains a range of applications helping supervising the WCDMA RAN status.

Figure 4-14: WCDMA RAN Explorer.

Alarm Viewers

Alarms triggered on a WCDMA RAN Network Elements are forwarded to the Fault Manager in OSS-RC. Then, Alarm Status Matrix displays the alarms, and alarm details are available in Alarm List Viewer.

FM KernelFM Kernel

RNCRBS RXI

Log ofalarms

Alarm List Viewer Alarm Status Matrix Alarm Log Browser Commands forsearching alarms

Notification to NMS

Figure 4-15: Alarm Notification Framework.


LZT 123 7371 R5A © 2007 Ericsson - 83 -

Alarm Status Matrix

The Alarm Status Matrix gives an overview of the current alarm situation in the network. The Alarm Status Matrix allows you to do the following: • Supervise several objects in a compressed view,

• Configure the user interface to show certain severities, toggle compact view on and off and dynamically add or remove rows and columns to change the number of objects possible to view,

• Access other applications: Start the Alarm List Viewer to view details about current alarms from a specific supervised object; Start the Alarm Log Browser to access all logged alarms for a specific supervised object.

• Synchronize the alarm list in the Fault Manager with the alarm list in a supervised object.

Figure 4-16: Alarm Status Matrix.

Alarm List Viewer

The Alarm List Viewer shows the complete alarm situation for one or more network elements in the network. To ensure a complete overview of the most important information the following features exist: • Each Alarm List Viewer window can consist of any number of

individual alarm lists.

WCDMA RAN Operation

- 84 - © Ericsson 2007 LZT 123 7371 R5A

• Each Alarm List shows the alarms for one or several network elements divided into one or several lists, where the sorting and filtering can be set for each list.

• The most important information for each alarm is shown in the alarm list, with one line per alarm. What information to show, in which width and in which order are defined for each list.

To support prompt action on alarm situations, alarms can be selected and the user can perform various tasks. The following pre-defined actions are supported: • Acknowledge, clear, unacknowledge and attach comments to

alarms

• Distribute alarm information via printers, files and mailboxes

• Access all available alarm information

• View alarm handling instructions for an alarm in an external document viewing tool

User-defined actions can also be added that provide integration with external applications. Such actions can be both alarm type dependent and alarm type independent. Examples of alarm type dependent actions are: • Send a certain sequence of commands via a command handling

tool to rectify the problem

An example of an alarm type independent action is: • Create a trouble ticket for one or several alarms in an external

Trouble Ticket application

A configurable toolbar ensures that the most frequently used actions are immediately accessible.


LZT 123 7371 R5A © 2007 Ericsson - 85 -

Figure 4-17: Alarm List Viewer.

Transport Topology Viewer

The Transport Topology Viewer application provides 3GPP interfaces (Iu, Iub, Iur, Mur, Mub and Mut) configuration information. It can be used to verify the setup, continuity and consistency of data for these interfaces.

Transport Topology Viewer combines data from several nodes to provide a higher layer view. It does so by using a Managed Object at the OSS-RC level, called VirtualPath MO. This MO links a VplTp in the origin node to the connected VplTp in the destination node. ATM, Signaling, SS7 and IP information on peer nodes can then be correlated and displayed on the GUI, as shown in the figure below.

WCDMA RAN Operation

- 86 - © Ericsson 2007 LZT 123 7371 R5A

Figure 4-18: Transport Topology Viewer.

Logs

All events, commands and errors in OSS-RC or in a WCDMA RAN node are logged, allowing tracking of faults, security breaches and processes.

• OSS-RC Logs

Log Viewer in OSS-RC provides a searching tool, which can display logs of different types:

o System Event Logs

o Error Logs

o Command Logs

o Network Status Logs

o Security Logs


LZT 123 7371 R5A © 2007 Ericsson - 87 -

Figure 4-19: Log Viewer.

• WCDMA RAN NE Logs

Logs can be collected in OSS-RC from all the NEs in WCDMA RAN, via the Collect Network Element Logs option.

RADIO NETWORK SUBSYSTEM LEVEL MANAGEMENT

At the Radio Network Subsystem level, management tools are similar than at WCDMA RAN level.

The expanded view of a RNS is the preferred view among OSS-RC tools, presenting the RNC and the attached RBSs.

Alarm viewers can be configured to present alarms from a complete RNS subsystem.

RNC-RBS SUBSYSTEM LEVEL MANAGEMENT

Management at the RNC-RBS Subsystem level is possible thanks to Node Status Analyzer (NSA) and Cell and Channel Manager.

WCDMA RAN Operation

- 88 - © Ericsson 2007 LZT 123 7371 R5A

NSA

NSA is designed for fast identification and localization of faults and inconsistencies. A user receives an alarm or similar indication that the service level has degraded. This user then launches NSA based on UtranCell identity, Radio Base Station (RBS) node identity or a Channel (RACH, FACH, PCH, HS-DSCH or E-UL) from the WCDMA RAN Explorer GUI.

NSA presents the entire RNC-RBS subsystem information in one GUI, which should point the user in the direction of the area causing the service degradation. The user can then conduct the needed corrective action from NSA directly or, if more advanced actions are required, launch the EMAS, OE, NCLI to correct the fault.

NSA provides the user, from one single application, with the means to get a collected and comprehensive view of the status of an RNC-RBS subsystem. NSA displays the status for Radio Network Controller (RNC) related information, Iub link, RBS node and RBS hardware. The information presented is a snapshot of the status of the RNC, RBS and Iub links when NSA was launched

NSA also provides access to CLI on the RNC and RBS in the current NSA scope, which can be used to quickly operate on the nodes. As described later on the next section, NCLI can be accessed via CLI, making it possible to handle the node’s configuration directly from NSA.

Figure 4-20: Node Status Analyzer.


LZT 123 7371 R5A © 2007 Ericsson - 89 -

Cell and Channel Manager

GUI-based Radio Network configuration and management is possible via the Cell and Channel Manager tool. It allows configuring local and UTRAN Cells, HS-DSCH, FACH, RACH and PCH Channels, and power control parameters.

Cell and Channel Manager can be used directly on the valid area, thus having direct impact on the live network, or can be used on a planned area that would be activated later on in the process.

The manager can be used to lock/unlock cells, when maintenance/reconfiguration procedures are required.

WCDMA RAN Operation

- 90 - © Ericsson 2007 LZT 123 7371 R5A

Figure 4-21: Cell and Channel Management

WCDMA RAN NODE LEVEL MANAGEMENT

At WCDMA RAN node level, management is performed using the following applications: • Element Management Application and Support (EMAS),

commonly called Element Manager (EM) in the WCDMA RAN context.

• Object Explorer (OE)

• Cabinet Viewer, available from NSA, and for the RBS only

• Command Line Interface.

• Node Command Line Interface (NCLI) available from the CLI interface.

EMAS

Using EM, the following tasks can be performed: • Topology view management

• Configuration management

• Software management

• Alarm management


LZT 123 7371 R5A © 2007 Ericsson - 91 -

• Restarting

• Timing Unit (TU) management

• Object properties management

• Locking and unlocking of objects

• Viewing online help

EM Components

This section describes the components of the Element Manager window, for an RBS:

12

3 4

56

Figure 4-22: Element Manager Application and Support Window

Title Bar

The title bar [1] displays the application window name and includes the standard Minimize, Maximize and Close buttons.

Menu Bar

The menu bar [2] displays the menus available in EM. Panes

The Element Manager window consists of two panes: left [3] and right [4].

The left pane displays a topology view, which is a graphical representation of the node structure. The topology is a tree of objects. The right pane displays subordinate objects of the object selected in the left pane, and provides information about them.

WCDMA RAN Operation

- 92 - © Ericsson 2007 LZT 123 7371 R5A

Information Bar

The information bar [5] displays the name of the selected object in the left pane.

View Selector

Use the view selector [6] to select which topology view to show. Change to a different view, and the view automatically refreshes.

The following views are common for all nodes: • Equipment

• IP

• ATM

• Signaling

• Software

The following element is available only on RBS and RNC Element Managers:

• Radio Network

The following element is available only on RBS and RNC Element Managers:

• Area

EM Views

A view is a graphical representation of a node structure. It displays a hierarchy of objects in the left and right panes of the Element Manager window. View objects act as high-level containers with subordinate levels of objects beneath.

The following actions can be performed within the EM views: • Load a view into the Element Manager window

• Expand and collapse the tree structure

• Select an object in a view

• Use shortcut menu applications for selected objects

• View information about selected objects

To load a view into the Element Manager window, select it from the view selector.

To expand an object in a view, click the plus (+) sign or double-click the object. To collapse an object in a view, click the minus (-) sign or double-click the object.


LZT 123 7371 R5A © 2007 Ericsson - 93 -

Radio Network View

Figure 4-23: RNC EMAS – Radio network View

Equipment View

Figure 4-24: RBS EMAS – Equipment view

WCDMA RAN Operation

- 94 - © Ericsson 2007 LZT 123 7371 R5A

ATM View

Figure 4-25: RNC EMAS – ATM view

Object Explorer

Object Explorer is embedded in EMAS, providing an interface more closely tied to the node’s MIB structure.

The main interface of Object Explorer provides a graphical view of the MIB tree architecture.

Attributes, states and counters of each Managed Object can be displayed and setup using individual property windows.


LZT 123 7371 R5A © 2007 Ericsson - 95 -

Figure 4-26: Object Explorer

Cabinet Viewer

Available from NSA, Cabinet Viewer provides the operator with a remote tool to get information and operate on the RBS hardware.

Figure 4-27: Cabinet Viewer

WCDMA RAN Operation

- 96 - © Ericsson 2007 LZT 123 7371 R5A

Command Line Interface

On every Network Element, a Command Line Interface (CLI) is available, either via the serial port of the Central GPB, or via a telnet/SSH session locally on the site LAN or remotely using the O&M Intranet.

The functionalities available from the CLI are: • Software Backup (CV) handling

• File system browsing

• NE/board status checks

• Trace and error logs

Figure 4-28: CLI

CLI is also accessible directly from the NSA GUI, for the nodes in the current scope.

Node Command Line Interface

The Node Command Line Interface (NCLI) is an application, accessible from CLI that allows user to manage a node’s MIB through direct commands.

NCLI presents the MIB tree architecture to the user as a UNIX file system, where Managed Object parents and children are represented as folder and subfolders.

It is possible to create, update and delete Managed Objects attributes by directly addressing the parameter.

A list of alarms can also be extracted from the node using NCLI.

NCLI commands can be sent to the node from a script.


LZT 123 7371 R5A © 2007 Ericsson - 97 -

Figure 4-29: NCLI

WCDMA RAN Operation

- 98 - © Ericsson 2007 LZT 123 7371 R5A

Intentionally Blank

5 Configuration Management

LZT 123 7371 R5A © 2007 Ericsson - 99 -


This module describes the Configuration Management for WCDMA Radio Access Network.

OBJECTIVES


• Explain the hardware and software architecture in WCDMA RAN nodes,

• Display, export and handle hardware and software resources in a WCDMA RAN node via OSS-RC and EMAS.

• Detail the file system in a WCDMA RAN node,

• Explain the Configuration Version concept for a WCDMA RAN node,

• Manage WCDMA RAN node files with OSS-RC,

• Manage Configuration Versions using OSS-RC and EMAS.

• Detail the Upgrade process for a batch of WCDMA RAN nodes,

• List the steps of the upgrade process of a WCDMA RAN node.


WCDMA RAN Operation

- 100 - © Ericsson 2007 LZT 123 7371 R5A

Intentionally Blank


LZT 123 7371 R5A © 2007 Ericsson - 101 -

OVERVIEW This module describes the Operation and Maintenance view of configuration management for WCDMA RAN.

WCDMA RAN traffic-carrying nodes are RNCs, RANAGs and RBSs. These nodes are all based on the same platform, Ericsson’s Connectivity Packet Platform (CPP), which simplifies Operation and Maintenance of WCDMA RAN.

Equipment handling consists in identification, localization and handling of hardware and software resources by tools such as SMO/NIO, NSA, EMAS, Object Explorer, CLI and NCLI.

Configuration management consists in node backup management and Radio/Transport Network configuration management. It is performed thanks to SMO, WCDM RAN Explorer, EMAS, OE, NCLI and CLI tools.

Node upgrade consists in hardware and software upgrades, and is implemented when new features and/or more capacity are needed. Upgrades can be performed using SMO and EMAS.

EQUIPMENT HANDLING This section describes how the CPP platform is structured and can be handled, in terms of hardware and software resources.

HARDWARE CONFIGURATION

As described in chapter 2, hardware resources in the CPP platform are represented by Managed Objects (MO) within the Managed Information base (MIB).

Hardware identification is the first task in any hardware operation process, and consists in getting hardware properties and localization.

Hardware handling consists in altering the state of a hardware MO, replacing or inserting new hardware.

Several tools are available in order to manage hardware resources: • SMO/NIO on WCDMA RAN and RNS level,

• NSA on RNC-RBS subsystem level,

WCDMA RAN Operation

- 102 - © Ericsson 2007 LZT 123 7371 R5A

• EMAS, Object Explorer, NCLI and CLI on RAN Node level.

Hardware Identification

Properties

In order to uniquely identify different pieces of hardware like cabinets, sub racks, backplanes, boards, fan units… all have the five following properties, stored on the MO related to the resource:

• Name o Common name of the piece of equipment,

o Examples:

BACKPLANE,

FAN,

GPB43,

GPB53.

• Product Number o Identifies the product type,

o Examples:

BACKPLANE = ROJ 605 107/1,

FAN = BFD 509 08/4,

GPB43 = ROJ 119 2106/43,

GPB53 = ROJ 119 2106/53.

• Revision o Identifies the hardware revision of the product,

o Examples:

BACKPLANE R1A,

FAN R10A,

GPB43 R2A,

GPB53 R1A.

• Serial Number o Identifies uniquely the piece of hardware,

o Examples:

BACKPLANE = T821143239,

ET-M1 = TU81361775


LZT 123 7371 R5A © 2007 Ericsson - 103 -

• Date of Manufacturing

Name,Product Number,Revision,Serial Number,Date of Manufacturing.

Figure 5-2: Hardware Identification.

Localization

Localization of hardware is crucial for Configuration and Fault Management in particular.

The CPP platform equipment is modeled in the MIB, each resource or group of resources being represented by a Managed Object. The model on which the MIB is built is called Managed Object Model, and the equipment part of the MOM is roughly described below.

Figure 5-3: Hardware Managed Objects.

WCDMA RAN Operation

- 104 - © Ericsson 2007 LZT 123 7371 R5A

Hardware Handling

Hardware Status

A WCDMA RAN node sets the Operational State of its hardware resources, depending on the condition of the hardware resource, on its configuration and/or its dependencies. A hardware resource is either in Enabled or Disabled Operational State.

Operators can set the Administrative State of hardware resources; board, physical port connected to the transport network, device on a board…

A hardware resource is either in Locked or Unlocked Administrative State. When a resource is locked, all the alarms that were issued by this resource are cleared. This condition is crucial when performing alarm mediation, as it can lead to misinterpretations of existing or non-existing alarms.

Each CPP board has three Light-Emitting Diodes (LED): green, amber and red. Depending on the state and activity of the board these LEDs can be OFF, steadily ON or blinking at 0.5 Hz, 2 Hz or 16 Hz.

Figure 5-4: LED Status.

Hardware Log

Whenever an event occurs on a board, an entry is added to the log of this board or the node. This allows later tracing of errors and problems.

Trace and error logs are available from CLI on the node.


LZT 123 7371 R5A © 2007 Ericsson - 105 -

Hardware Operation

Several operations are possible on hardware resources: replacing, reloading, restarting, locking, unlocking, testing, and setting parameters.

Each operation has to follow a predefined procedure, which ensures that the system stays in normal operation mode and that the downtime period, if any, is minimal.

These procedures are available in the Alex library relevant for the WCDMA RAN node involved, RNC, RBS or RXI.

Figure below presents the OPI for replacing a board on an RNC.

Figure 5-5: Hardware OPI - Replacing a Board.

HARDWARE MANAGEMENT APPLICATIONS

NIO

At WCDMA RAN and RNS levels, only display and export of hardware configuration information is possible, thanks to the Network Inventory Organizer (NIO) module, within Software Management Organizer (SMO).

WCDMA RAN Operation

- 106 - © Ericsson 2007 LZT 123 7371 R5A

The NIO module works on data from the SMO Database of OSS-RC, which contains hardware configuration information from the WCDMA RAN nodes

In order that the SMO database matches the real WCDMA RAN nodes hardware configuration, regular updates of the database are needed.

This operation is called hardware adjust. It can be scheduled to run periodically, and is recommended to be performed before viewing and/or handling hardware configuration data with OSS-RC.

Figure 5-6: Hardware Adjust.

Once the SMO database has been updated, two solutions exist for the operator to access the data:

• SMO GUI: the Software Management Organizer GUI provides a hardware view for one or several WCDMA RAN nodes. Sub rack and board configuration information are provided as shown on figure below.

• NIO CLI: the NIO Command Line Interface is used to export hardware configuration information to an XML file. Data from one or several node can be extracted. OSS-


LZT 123 7371 R5A © 2007 Ericsson - 107 -

RC CPI describes an export of several nodes at a time, using a text file as an input. An example of NIO CLI is presented on Figure below.

Figure 5-7: NIO in SMO GUI

WCDMA RAN Operation

- 108 - © Ericsson 2007 LZT 123 7371 R5A

Figure 5-8: NIO CLI.

NSA – Cabinet Viewer

At RNC-RBS subsystem level, collection of RBS software and hardware configuration information is possible, thanks to the Cabinet Viewer module within Node Status Analyzer (NSA).

The Cabinet Viewer displays a graphical view of the actual layout of the RBS type including all selectable objects, and their LED status. A selectable object can be a board, a unit, a subrack within the RBS, or the RBS cabinet itself. Information about the power system and the external alarm ports is also shown.

By selecting a board of the RBS in Cabinet Viewer, and by looking at the Details Pane, one can see all hardware and software properties.

Figure below presents the Details Pane for a GPB board on the RBS. These details can be saved on a text file using the Save Details option.


LZT 123 7371 R5A © 2007 Ericsson - 109 -

Figure 5-9: Cabinet Viewer –Resource Details

Yet, Cabinet Viewer not only provides configuration data about all selectable objects, but also allows the operator to perform the following tasks:

• Restart the RBS,

• Restart a Board or Unit,

• Lock/Unlock a board or Unit,

• Test a Board or Unit,

• Extract Logs from board,

• Save Board Details.

WCDMA RAN Operation

- 110 - © Ericsson 2007 LZT 123 7371 R5A

Figure 5-10: Cabinet Viewer - Hardware handling.

EMAS – Equipment View

At WCDMA RAN node level, collection of hardware configuration information and hardware handling are possible, thanks to Element Management Application and Support (EMAS).


LZT 123 7371 R5A © 2007 Ericsson - 111 -

Via the Equipment view, the operator has access to all hardware resources on the node, can view its properties and Operational status, and change its Administration status or its settings.

Figure 5-11: EMAS - Equipment View.

The Object Explorer application is now embedded in EMAS, providing an MIB tree view of the RAN Node. Equipment Managed Objects can be found under the Equipment MO, as shown in figure below.

Figure 5-12: OE– Equipment MO

WCDMA RAN Operation

- 112 - © Ericsson 2007 LZT 123 7371 R5A

NCLI

Node Command Line Interface provides access to Equipment Managed Objects via a Command Line Interface, allowing configuration and handling of hardware.

Figure 5-13: NCLI– Equipment MO

It is possible to lock/unlock hardware resources from NCLI, as well as changing parameters. NCLI is not “MOM aware”, so the operator is required to know and specify completely the attributes to be changed in an MO, as described in the figure below. In this figure, the board on slot 24 of the Main Subrack is locked and unlocked using NCLI.


LZT 123 7371 R5A © 2007 Ericsson - 113 -

Figure 5-14: NCLI – Locking/Unlocking Example

CLI

Command Line Interface enables the operator to get traces and error information for the CPP hardware, as well as the hardware status.

Figure 5-15: CLI – Hardware Management.

WCDMA RAN Operation

- 114 - © Ericsson 2007 LZT 123 7371 R5A

SOFTWARE CONFIGURATION

Architecture

Load Modules and Programs

The code running on WCDMA RAN CPP hardware is stored in the form of Load Modules (LM).

A Load Module consists of the code and all the parameters and variables required in order to implement a specific task on the node.

An executing Load Module is called a program. A program is running on the Operating System Embedded (OSE) Delta environment. Each program contains one or more processes and each process has an interface called an Actor.

Processes communicate with each other using OSE signals.

The figure below presents the software execution model.

ProgramProgram ProgramProgram

OSE Process OSE Process

OSE ProcessActor

OSE Signal

A running Load Module is called a

Program

A running Load Module is called a

Program

Figure 5-16: Software Execution Model.

Load Module Identification

In order to uniquely identify Load Modules, an MO stores all the following information:

• Name o Explicit name of the load module,

o Examples:

ss7mgr


LZT 123 7371 R5A © 2007 Ericsson - 115 -

• Product Number o Identifies the Load Module type,

o Examples:

CXC1323082

• Revision o Identifies the Load Module revision,

o Examples:

R12H01

• Date of Creation

Load Module Location

Each General Processor Board (GPB) in a RNC, RBS or RXI contains a hard disk that is divided into /c and /d partitions.

When downloading Load Modules into the node, for instance before an upgrade, all Load Modules are first downloaded to the Central GPB (slot 10 in RNC, slot 1 in RBS 3206 and slot 2 in RXI). The node itself then handles the distribution of load Modules to all of the other boards.

The /c drive is mirrored by the rest of the GPBs inside the cluster, and is accessible by all the boards in the node.It contains all LMs to be loaded on the boards in the node.

The /d drive is only locally accessible on the GPB board, and contains the load modules required by this GPB. Load modules on the /d drive must be replicated in all the GPBs inside the cluster.

The /f drive is only locally accessible on all other board than the GPB.

Note: The /c partition is called /c2 in backup mode.

WCDMA RAN Operation

- 116 - © Ericsson 2007 LZT 123 7371 R5A

Figure 5-17: LM in the RAN Node file system

Directory Structure

The /c drive is composed of the following directories: • CommandLog: Empty

• Configuration: Empty (This will be a /d/configuration security copy)

• Java: Java files (used by Thin Client tools)

• Loadmodules: LMs loaded on the /c drive

• Loadmodules_norepl: New Thin Client files (automatically created) after an upgrading process.

• Logs: Alarm and Events data record files

• Up: Upgrading system files

• Public_html: location for the nameroot.ior file.

The /d drive is composed of the following directories: • Loadmodules: LMs loaded in /d drive

• Configuration: Configuration Versions, which are saved backups.

Software Allocations

Software Allocation (SWA) is the link between hardware and software in the CPP Platform.


LZT 123 7371 R5A © 2007 Ericsson - 117 -

Load Modules are grouped into Repertoires. Each Repertoire has a particular function, and regroups LMs that implement this particular functionality. Follows some examples of Repertoires:

• Repertoire Cello_AAL2_RBS_MP regroups the Load Modules needed for handling AAL2 switching in an RBS, and which have to be loaded on the Main Processor of the GPB board of an RBS.

• Repertoire Cello_ETMC41 regroups all the LMs that need to be loaded on an ET-MC41 board.

A Software Allocation is linking one or several repertoires to one or several slots on the CPP node. Follows some example of SWAs for an RNC:

• SWA GPB_Module links:

o Repertoires:

RNC_Module_MP,

Cello_Common_MP,

Cello_AAL5_MP,

Cello_AAL2_RNC_MP,

Cello_AAL2_Cen_Rh_MP,

o To slots 14, 15 and 16 in the Main Sub rack, used by GPB boards handling the two RNC modules of the Main Sub rack.

Figure 5-18: Software Allocation for Module GPB in Main Sub-rack

• SWA GPB_Module links:

o Repertoires:

RNC_Module_MP,

Cello_Common_MP,

WCDMA RAN Operation

- 118 - © Ericsson 2007 LZT 123 7371 R5A

Cello_AAL5_MP,

Cello_AAL2_RNC_MP,

Cello_AAL2_Cen_Rh_MP,

o To slots 14, 15 and 16 in the Main Sub rack, used by GPB boards handling the two RNC modules of the Main Sub rack.

Reliable Program Uniter

A Reliable Program Uniter (RPU) is a controlling and addressing entity that provides a common addressing unit for parts of two reliable programs.

An RPU allows securing a program running on a processor, by specifying a stand-by location. In case of failure of the active resources where the program runs, the stand-by resources will automatically take over the program, without loss of information.

Backup & Basic Operative System

There are two different OSs in the node: BACKUP OS and BASIC OS. They are also referred to BACKUP Mode and BASIC Mode.

During the restart of the node, after HW initialization and processor start up, the main GPB chooses between loading the OS from the non-volatile memory (BASIC OS) and loading a minimum version that only supports a few maintenance tasks (BACKUP OS).

The BACKUP OS is used to guarantee that the board will be able to start up and maintain external communication despite faults or failures.

MANAGEMENT TOOLS

SMO

At WCDMA RAN and RNS levels, display and export of software configuration information is possible, at a Load Module level, thanks to SMO.

SMO works on data from the SMO Database of OSS-RC, which contains software configuration information from the WCDMA RAN nodes


LZT 123 7371 R5A © 2007 Ericsson - 119 -

In order that the SMO database matches the real WCDMA RAN nodes software configuration, regular updates of the database are needed.

This operation is called software adjust. It can be scheduled to run periodically, and is recommended to perform before viewing and/or handling software configuration data with OSS-RC.

Figure below describes how to perform a software adjust.

Figure 5-19: Software Adjust.

Once the SMO database has been updated, two solutions exist for the operator to access the data:

• SMO GUI: the Software Management Organizer GUI provides a software view for one WCDMA RAN node. Load Module configuration information is provided as shown on figure 5-20.

WCDMA RAN Operation

- 120 - © Ericsson 2007 LZT 123 7371 R5A

Figure 5-20: SMO - Software View.

• SMO CLI: the SMO Command Line Interface is used to export hardware configuration information to an XML file. Data from one or several node can be extracted. OSS-RC CPI describes an export of several nodes at a time, using a text file as an input.

EMAS – Software View

At WCDMA RAN node level, collection of software resources configuration information and software resources handling are possible, thanks to Element Management Application and Support.


LZT 123 7371 R5A © 2007 Ericsson - 121 -

Figure 5-21: RNC EMAS - Software Allocations.

Figure 5-22: RBS EMAS - Software Allocations.

WCDMA RAN Operation

- 122 - © Ericsson 2007 LZT 123 7371 R5A

Figure 5-23: RNC EMAS - RPUs.

SOFTWARE MANAGEMENT

CONFIGURATION VERSION

Overview

A configuration of the node is called a Configuration Version (CV). All resources on the node, defined as Managed Objects (MO) in the MIB, are stored in this CV, and can be restored on the node when needed.

A number of CVs can be stored in the node, and provide as many backup of the whole node, available in case of any node failure or for rolling back to a previous configuration.

Also stored on a CV is a reference to the Upgrade Package to be used along with the CV. It is possible to have CVs referring to different UPs, which can prove useful during an upgrade process. An Upgrade package corresponds to a certain software version of the node.


LZT 123 7371 R5A © 2007 Ericsson - 123 -

Configuration Versions Used

Current CVs

On each node, some CVs have a specific role; each node has one and only one:

• Startable CV: the CV will be loaded at the next node restart,

• Executing CV: the currently executing CV in the node,

• Loaded CV: the CV that has been used to configure the node at the last node restart,

• Last Created CV: the last created CV on the node.

The CVs listed above cannot be deleted from the node.

Rollback List

A Rollback List of CVs defines a priority list of CVs that should be used in case an error occurs with the startable CV at node restart.

The decision to move down on the Rollback List is dependent on the number of node restart that occurs in a certain period of time. Both the number of restarts and the period are configurable, using CLI command cv.

CV File Structure

Figure 5-24: CV Files in the RAN Node file system

WCDMA RAN Operation

- 124 - © Ericsson 2007 LZT 123 7371 R5A

Configuration Versions are stored under the directory /d/configuration/cv/<cv name>

The current Configuration Version is pointed out by the cv.ptr file in the /d directory. This file contains the name of the current CV directory.

A CV directory contains the following files: • db.dat Database

• LLP.LMID Loader_server

• ok CV ok?

• Attribute Text information about the CV

• ARMAMENT Start-up file,

• Md5checksum CV checksum using MD5 technology

The db.dat File

The db.dat file is a dynamic database and contains all the values required to generate the MIB.

Several databases must be considered: • Loaded db

• Startable db (will be loaded when the node is restarted)

• Actual db: this is the loaded db with the actual changes. To save these changes is necessary to create a new CV.

The LLP.LMID File

The LLP.LMID contains the name of the loader server Load Module. The loader server loads the node configuration, at startup, from the ARMAMENT file and then from the database into the node, for example, CXC1320785_R7C01.

The ok File

The ok file is mandatory and is used as a flag by the Configuration Version SW to indicate a successful creation of the CV. This file is empty when it is used for the first time.


LZT 123 7371 R5A © 2007 Ericsson - 125 -

The Attribute File

The Attribute file is mandatory and contains the attributes for the CV, such as operator, operator’s comment, Upgrade Package reference, and Configuration Version identifier. The file is empty when it is used for the first time.

The ARMAMENT File

The ARMAMENT file contains information about the Load Modules that need to be run before the database is in operation. It also indicates the boards that the Load Modules execute on.

The loader server program pointed out by the LLP.LMID file reads the ARMAMENT file. Once the database is started, the loader server fetches the configuration data from the database instead of from the ARMAMENT file.

The md5checksum File

The md5checksum file is used to ensure that the CV is correctly transferred from one file system to another. It runs the MD5 algorithm on the CV files, and creates a unique code, which is the signature of the CV.

Node Restart Sequence

Cold Restart

The following describes the sequence in which files are used during the startup procedure, for a cold restart.

1. Read contents of /d/cv.ptr (e.g. <cv name>)

2. Move to directory /d/configuration/cv/<cv name>

3. Check ok file. If missing or damaged the node checks for next file in Rollback list and resumes from point 2.

4. Read contents of LLP.LMID

5. Load server program pointed to by LLP.LMID reads ARMAMENT file.

6. When ARMAMENT load modules have been loaded the node uses db.dat to reconstruct the MIB.

WCDMA RAN Operation

- 126 - © Ericsson 2007 LZT 123 7371 R5A

If system goes into a cyclic restart, or if the Element Manager will not launch, it is essential to monitor these files in the order in which they are used by the node.

Another useful file held in the /d directory is cv.bak. This stores a reference to a CV other than the startable CV. This can be useful in handling some fault situations.

Warm Restart

The following describes the sequence in which files are used during the startup procedure, for a warm restart.

1. Read contents of /d/cv.ptr (e.g. <cv name>)

2. Move to directory /d/configuration/cv/<cv name>

3. Check ok file. If missing or damaged the node checks for next file in Rollback list and resumes from point 2.

4. Use db.dat to reconstruct the MIB.

Configuration Version Handling

It is critical for an operator to be able to backup the current network configuration at node level, so that the reconfiguration time is minimal in case of node failure.

Two options exist for storing CVs; one is using the local storage capacity of the node. The second one involves a Backup FTP server on the Application Server in OSS-RC.

It is recommended to implement a process, which periodically creates CVs, and transfers them to the Backup FTP server.

MANAGEMENT TOOLS

SMO

SMO is the preferred tool for Software Management at WCDMA RAN level.

Files can be distributed to the network elements using SMO. This may be performed either as a part of a software upgrade job, or as a standalone activity. It is also possible to perform basic file manipulation, on the network element for example rename and delete.


LZT 123 7371 R5A © 2007 Ericsson - 127 -

SMO allows initiating backup on the network element, restoring a previous configuration, and transferring backup files from the network element to SMO File Store. Files can also be exported to external media by SMO

Figure 5-25: SMO - Software management.

EMAS

From EMAS, the software view is used to manage CVs on the node, allowing creation, removal, setup and FTP transfer of CVs.

WCDMA RAN Operation

- 128 - © Ericsson 2007 LZT 123 7371 R5A

Figure 5-26: EMAS - CV handling.

CLI

The Configuration Versions can be managed directly from CLI, using the cv command, as described in figure below.

Figure 5-27: Specific CVs - CLI

SYSTEM UPGRADE Software and hardware upgrade in WCDMA RAN involve strict following of established and tested procedures, and have to be implemented with Ericsson technical support teams.


LZT 123 7371 R5A © 2007 Ericsson - 129 -

This section presents the general process involved when upgrading software and hardware, but should not be considered as definite or exhaustive.

HARDWARE UPGRADE

A hardware upgrade can imply adding, changing or removing of different hardware versions in run-time. In most cases, upgrading hardware has nothing to do with upgrading software. The UP concept is not used for upgrading the hardware while upgrading the software.

It might, however, be necessary to upgrade the software, before or after, to take the new hardware into operation. Normally, software can be upgraded first. Depending on the composition of the Repertoires, one or two restarts will occur.

Upgrading of a board can be required if a board is replaced, but also if a board is inserted into an empty slot. Both cases result in the board being started with the correct SW if the following prerequisites are met:

• The relevant UP has been activated, that is, the software is available and the hardware is known by the system.

• The new slot has a defined role, that is, it has a Software Allocation configured. When a new board is inserted, the Product Identity Data (PID) is read from the board to make sure that the correct software is loaded which is indicated in the Repertoires.

If the process cannot continue because the prerequisites are not fulfilled, manual actions have to be taken before the board is started. Therefore, it is better to make sure that the required reconfigurations are made before the board is inserted. That way, the operator while on site can monitor the start on the LEDs.

Add, replace, remove board.Upgrade Software before Hardware,Allocate LMs to Slots with Software Allocations,PID read from board, and correct version of Software loaded on Hardware,

Figure 5-28: Hardware Upgrade.

WCDMA RAN Operation

- 130 - © Ericsson 2007 LZT 123 7371 R5A

Figure 5-29: Hardware Upgrade Scenario

SOFTWARE UPGRADE

Upgrade Package

Load Modules are installed and activated in the node through Upgrade Packages (UP). An Upgrade Package contains all information needed to activate the Load Modules, documentation on the LM and the LMs themselves.

The UP is delivered in one UP directory on the local GSDC Release Servers. The UP directory has the following architecture:

• /loadmodules: All Cello loadmodules for the target SW version.

• /loadmodules_norepl: Cello loadmodules that do not need to be replicated in the target SW version.

• /public_html: All Cello loadmodules for EMAS and for the target SW version.

• /java: All Cello java-related loadmodules for the target SW version.

• /doc: documentation regarding the upgrade package and example files needed for the upgrade procedure.

• /aue: Application upgrade engine(s), that is special data conversion loadmodule(s) to be used in the upgrade procedure.

• /dtd: Upgrade Package Definition and Control file (UCF) for the target SW version.

• /onlinehelp: All the online-Help files required for the target SW version.


LZT 123 7371 R5A © 2007 Ericsson - 131 -

The upgrade package also contains the following documents • Work Instruction,

• XML control File.

Several UP can coexist on a node, and it is not recommended to remove an older UP without having successfully tested and commissioned a newer UP.

/loadmodules/loadmodules_norepl/public_html/java/doc/aue/dtd/onlinehelp

Figure 5-30: Upgrade Package Content.

Process

Software upgrade consists in installing new or modified version of existing Load Modules in a WCDMA RAN node.

Several steps are involved in the upgrading process, in order to ensure reduced downtime and controlled activation of new features:

• Health Check over the complete WCDMA RAN, to prepare the Software deployment. Particularly important checks are the Disk Space available on WCDMA RAN nodes involved in the upgrade process, and hardware checks, to ensure that no hardware maintenance is needed. This Health Check must be performed well in advance, to allow for troubleshooting any fault.

• Install Software on the target nodes. Installing basically consists in downloading the needed Upgrade Package from OSS-RC FTP Server to the nodes to upgrade.

• Backing up the nodes, in case a roll-back is needed during the upgrade process.

• Select the target nodes, which should be included in the upgrade process,

• Run pre-upgrade Health Check, to identify nodes that should be removed from target because of an identified

WCDMA RAN Operation

- 132 - © Ericsson 2007 LZT 123 7371 R5A

problem. Health Check performed before and after the upgrade step will be used to compare status of nodes.

• Upgrade of the nodes, possible in batches of no more than 500 nodes. Confirmation of the upgrade, after it had been performed, is needed to validate it.

• Run post-upgrade Health Check, to compare with pre-upgrade Health Check. Particularly important checks are Cell Availability and Active Alarm checks.

Upgrade Modes

Both installation and upgrade can be done in Soft or Hard mode: • Soft mode: The system is not going to overwrite the

previous information. So in an installation, when the system is copying files, it founds that one file already exists, the system is not going to overwrite it. In the upgrade case, when the system is creating the new configuration, if it founds for example that a Load Module is already loaded in a board, the system does not overwrite the definition.

• Hard mode: If the system found that a file or a definition already exists, it is going to overwrite the file or definition.

Typical Upgrade Duration

• Release (major) upgrade: 1 night (6 hours maintenance window) for 1 RNS (1 RNC, 150 RBS),

• Upgrade without MOM change: up to 500 nodes per batch (2-3 batches per night),

• Upgrade with MOM change: up to 80 nodes per batch.

Disturbances Caused by the Upgrade

Node restart cannot be avoided during Upgrade. However, there are no traffic disturbances during the installation and confirmation phases of the SW Upgrade.

Following the Upgrade phase, the node automatically restarts: traffic disturbance cannot be avoided.


LZT 123 7371 R5A © 2007 Ericsson - 133 -

The node performs one restart in basic mode, then two restarts in backup mode and finally another restart in basic mode before setting the CV to Temporary Upgrade: Tm_3%CXP9010029_x_yyyyyy_zzzz (Where x is the Revision, y is the Date and z is the Time).

After confirming the upgrade, the final new upgrade CV will become the startable CV. This CV will look like the following example: Fi_3%CXP9010029_x_yyyyyy_zzzz.

Process– HealthCheck,– Install SW on nodes,– Backup nodes,– Select SW upgrade target nodes,– Pre-upgrade HealthCheck,– Upgrade,– Post-Upgrade HealthCheck

Mode– Soft Upgrade,– Hard Upgrade

Disturbances

Figure 5-31: Software Upgrade.

MANAGEMENT TOOLS

HealthCheck

Before and after performing Software Upgrade, a HealthCheck job is run. It helps define: • the “before” condition of the network, and if the upgrade is

possible

• Compare the “before” and “after” status of the network to control the upgrade didn’t create extra problems.

WCDMA RAN Operation

- 134 - © Ericsson 2007 LZT 123 7371 R5A

Figure 5-32: Health Check GUI

SMO

SMO is the preferred tool for Software Upgrades, as it allows upgrading several nodes simultaneously, allow the scheduling of the install and download processes, and traces the progress of processes.

Software Packages are delivered from Ericsson to the customer. The Software Packages contain an SMO configuration file, which provides information on the recommended upgrade process. Based on information from the configuration file, you will be guided through the process of setting up an upgrade job towards multiple network elements. Once the job execution is started, the user receives progress and status information for each network element.


LZT 123 7371 R5A © 2007 Ericsson - 135 -

Figure 5-33: SMO GUI

EMAS

EMAS can be used for the Software Upgrade process, yet is focusing on a single node at a time.

CONFIGURATION DATA HANDLING The WCDMA RAN network is a complex system, which requires databases in several nodes to have consistent data in order to provide the required services.

The main concern of operators is to maintain these databases in case of network or node outage, in order to reduce the disturbances and the down time on billable traffic. The Fallback feature allows restoring the Radio and/or Transport Network configuration over part or the full WCDMA RAN.

In order to ensure that data consistency is kept through various configuration phases, a number of tools are available in OSS-RC: Transport Topology Viewer, Consistency Check, Node Status Analyzer… They combine information from several RAN nodes to provide an overall picture of the network configuration.

WCDMA RAN Operation

- 136 - © Ericsson 2007 LZT 123 7371 R5A

FALLBACK

Figure 5-34: Fallback

The fallback application allows taking a snapshot (fallback area) of part of or the full WCDMA RAN network configuration, and store it on the file system.

A fallback area can then be restored at a later stage by writing it into a planned area, which can then be activated.

The fallback application will also allow exporting a fallback area to a 3GPP export file, to modify a fallback area, or to delete already created fallback areas.

It is implemented as an optional part of BCG; if the BCG server is not activated then the functionality will not be available.


LZT 123 7371 R5A © 2007 Ericsson - 137 -

Figure 5-35: Fallback Area GUI

DATA CONSISTENCY

Figure 5-36: Data Consistency

It is vital to ensure the consistency of Configuration Data at different levels: • At management level, OSS needs to keep track of all

modifications on the RAN nodes, as well as reflect UTRAN Cell relations modifications.

• At UTRAN interfaces level, configuration data in connected nodes needs to match, in order to provide services with the desired quality of service.

• At transport network level, consistency of data can be checked by performing loopback tests on the ATM VPs and VCs.

6 Fault Management

LZT 123 7371 R5A © 2007 Ericsson - 139 -

6 Fault Management

This module describes the Fault Management for WCDMA Radio Access Network.

OBJECTIVES


• List the different fault categories,

• Explain the Fault Management model,

• Explain the fault escalation process,

• Follow Fault Handling procedures,

• Handle the most common faults of a WCDMA RAN network.


6 Fault Management

LZT 123 7371 R5A © 2007 Ericsson - 141 -

OVERVIEW Fault Management, described in this module, has two different aspects: • WCDMA RAN Fault Management features, which aim at

detecting faults and malfunctions on the WCDMA RAN nodes, reporting them to the operator,

• Fault Handling, performed by the operator, to correct the faults and malfunctions, thanks to a set of tools.

WCDMA RAN FAULT MANAGEMENT FEATURES 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.

FAULT CATEGORIES

Each potential fault in WCDMA RAN is grouped into one of the following categories: • Hardware failures: malfunction of a physical resource within

an NE.

• Software problems: includes software bugs or database inconsistencies.

• Functional faults: 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: communication failure, for example between two RNCs or between two operating systems.

WCDMA RAN Operation

- 142 - © Ericsson 2007 LZT 123 7371 R5A

Hardware failuresSoftware problemsFunctional faultsOverloadingCommunication faults

Figure 6-2: Fault Categories.

FAULT MANAGEMENT FUNCTIONS

Fault Management Model

Fault HandlingFault HandlingExternal AlarmsExternal Alarms

NE AlarmHandling

NE AlarmHandling

NE EventHandling

NE EventHandling

Element Manager

Filtering

NMSNMS

FMFMNE

AlarmLog

RAN Alarm& FM

event log

NEAlarmLog

NEAlarmList

NE FMEventLog

NEAvailability

Log

Alarm Notification Alarm Notification

Alarm ReportAlarm ReportAlarm Report

Alarm Notification Alarm Notification

SubnetworkManager

NE

OSS-RC

NMSNetwork Manager

Figure 6-3: Fault Management Model

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.

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.

6 Fault Management

LZT 123 7371 R5A © 2007 Ericsson - 143 -

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

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.

FAULT ESCALATION PROCESS

When a fault occurs on a resource, the following events take place:

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

• Localization: The Fault Handling function identifies the faulty unit and includes information about it in the alarm report.

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

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

• Reporting: The system generates an alarm and sends it to OSS-RC and also to the NMS if it subscribes to the alarm. From then on, an action by the operator is needed.

Then the following events take place:

• Correction: A process is started by the operator in order to analyze and correct the fault. This process is looked at in more details on the next section.

WCDMA RAN Operation

- 144 - © Ericsson 2007 LZT 123 7371 R5A

It is possible to set up an automatic correction process via the Fault Management eXpert (FMX) tool, which simplifies operator’s tasks for common faults.

• Verification: Different tests and board verifications are performed to ensure that the problem has been corrected.

• Restoration: Restoration consists in bringing the isolated units back into the working system. The operator performs restoration manually or via the FMX tool.

Fault Management FeaturesDetectionLocalizationIsolationRecoveryReporting

Fault HandlingCorrectionVerificationRestoration

Figure 6-4: Fault Escalation Process.

FAULT HANDLING

FAULT HANDLING PROCESS

Report

Prior to the network commissioning, the operator has made sure that he is monitoring alarms reported by the system, either thanks to Ericsson tools or its own tools, in order to know when faults occur in the system.

An Ericsson-based alarm reporting solution makes use of Alarm Status Matrix (ASM) and Alarm List Viewer (ALV).

Once alarm reporting is set up, and when a fault occurs, the operator receives a notification by the alarm-reporting tool. This is the starting point of the fault handling process.

Analyze

This step aims at getting enough information about an alarm so that existing procedures can be found to fix the related fault.

6 Fault Management

LZT 123 7371 R5A © 2007 Ericsson - 145 -

Alarm details

In order to get as many information as possible on an alarm, Alarm List Viewer is used. Many alarm attributes can be displayed, some of the most important being as follow: • Perceived Severity: Critical, Major, Minor or Warning,

• Alarm ID, unique within OSS-RC,

• Event Time,

• Object of Reference, pointing to the resource linked to the alarm,

• Probable Cause,

• Specific Problem, used to search within ALEX for the appropriate OPI.

Figure 6-5: Alarm Report.

Fault Localization

The hardware, software and all resources in WCDMA RAN nodes are defined in the MOM (Managed Object Module) as individual MOs (Managed Object). When a fault occurs in a RAN node, the RBS, RXI and RNC will rise an alarm, and the alarm raised will be related to the MO where the fault occurred.

WCDMA RAN Operation

- 146 - © Ericsson 2007 LZT 123 7371 R5A

The MOs are identified using RDN, LDN or FDN.

• RDN – Relative Distinguished Name

This is used to identify an MO in relation to its nearest parent in the MO tree. The RDN contains MO Class (also called MO Type), the equal sign, and MO identity. Example:

AtmPort=MS-24-1

AtmPort is the MO Class, and MS-24-1 is the identifier.

• LDN – Local Distinguished Name

This is used to uniquely identify an MO within a RAN node. The LDN shows the hierarchy above the MO within the Managed Element’s MO tree. Example:

ManagedElement=1,TransportNetwork=1,AtmPort=MS-24-1

• FDN – Full Distinguished Name

This is used to uniquely identify an MO within a network (used by OSS-RC). The MeContext field identifies the node. Example:

SubNetwork=AUS,SubNetwork=Test_Plant,MeContext=RNC55, ManagedElement=1,TransportNetwork=1,AtmPort=MS-24-1

RDN – Relative Distinguished Name

AtmPort=MS-24-1

LDN - Local Distinguished Name

ManagedElement=1,TransportNetwork=1,AtmPort=MS-24-1

FDN – Full Distinguished Name

SubNetwork=AUS,SubNetwork=Test_Plant,MeContext=RNC55, ManagedElement=1,TransportNetwork=1,AtmPort=MS-24-1

Figure 6-6: MO Localization.

Fault Type

Several alarm attributes help the operator define what type of fault triggered the alarm. Some of these attributes follow:

6 Fault Management

LZT 123 7371 R5A © 2007 Ericsson - 147 -

• Event Type

• Probable Cause,

• Specific Problem

It can be noted that the Specific Problem attribute provides a direct search entry for the CPI library. The search will return a link to an Operating Instruction (OPI) page, which contains a detailed description of the fault cause and recovery procedures. The process from ALV to OPI is shown in figure below.

Figure 6-7: Alarm Report to OPI.

Procedures

For every type of alarm triggered by the system, a set of procedures exists in CPI.

Operators may also have implemented a dedicated database collecting a history of alarms and associated procedures, used to fix corresponding faults. This can help reduce the fault handling process by reapplying already performed procedures.

Correction

This step aims at applying existing procedures in order to fix a fault, whether these procedures come from the OPI database or an external database.

WCDMA RAN Operation

- 148 - © Ericsson 2007 LZT 123 7371 R5A

OPIs involve tasks and tools that have been described on other modules of this course.

Fault correction often involves a succession of actions and testing steps, before solving a problem

Action

When available, an OPI will describe, step-by-step, the process to follow in order to fix the fault.

Test

After actions are taken by the operator, tests are performed, either manually or automatically by the system. Depending on the result of these tests, more actions might be needed.

Manual testing can consist in alarm monitoring, to ensure that the alarm has been cleared. Several other tests are available for the user, like F4 and F5 tests on ATM VPs and VCs, from the Transport Topology Viewer.

Restoration

After the correction phase, fixed resources may need to be manually brought back into the active system.

Restoration typically consists in unlocking resources, so that they can be used by the operative system.

WCDMA RAN COMMON FAULTS

This section describes the most common faults observed on WCDMA RAN. For each alarm, the fault handling process is described in details.

AuxplugInUnit_PiuConnectionLost

Analyze

• Fault Type

AuxplugInUnit_PiuConnectionLost

6 Fault Management

LZT 123 7371 R5A © 2007 Ericsson - 149 -

The AuxPlugInUnit MO issues the Piu Connection Lost alarm when communication between one of the Auxiliary Plug In Units and its Device Board is lost. This alarm is also generated when the device board, to which the AUX is connected, is removed.

These can be generated due to different issues such as restarts of nodes or boards, where there is a temporary loss, as it takes time to recover. When this is accompanied by the temperature faults, it is more than likely the fan unit has been disabled.

• Procedures

Correction

Based on operator’s experience, this fault can be fixed by restarting the Capacitor Unit (CU). If the alarm is not cleared, the CU should be replaced.

RNC – UtranCell_RbsLocalCellNotAdded

Analyze

• Fault Type

RNC – UtranCell_RbsLocalCellNotAdded

This alarm appears when the Radio Network Controller (RNC) sends an AUDIT REQUEST message to a connected Radio Base Station (RBS) asking to activate a cell, and the RBS answers with an AUDIT RESPONSE message "Empty Local Cell". The likely cause of this alarm is that the RBS Local Cell corresponding to the cell that RNC is trying to activate is not configured. As a result of this alarm, the RNC disables the cell.

Correction

Change the Local Cell ID on the RBS.

RBS – Loss of Signal

Analyze

• Fault Type

RBS – Loss of Signal

WCDMA RAN Operation

- 150 - © Ericsson 2007 LZT 123 7371 R5A

The alarm is issued when the ET cannot detect any signal at the input port.

The possible causes are:

• Failure in the remote node

• Line interruption

• ET failure in this node

As a result of the fault, the traffic on the affected transmission link is lost.

RNC – NbapCommon_RncRbsControlLinkDown

Analyze

• Fault Type

RNC – NbapCommon_RncRbsControlLinkDown

The alarm appears when one signaling bearer (with no redundancy) or two bearers (with redundancy) for NBAP common loses its assured mode. This occurs when there is a problem with the IUB or a problem with the ETB in either RNC or RBS. As a result of this alarm, the RBS disables all cells; therefore the RNC drops calls from these cells.

WCDMA RAN KNOWN FAULTS AND DESCRIPTION

RBS or RNC – Hardware incompatibility

Hardware at the wrong revision for the current Upgrade Package installed on the node.

No C.S traffic

Customer care has received complaints of not being able to make speech or video calls.

RNC – Loss of Frame

This shows the result of an unlocked unused port.

6 Fault Management

LZT 123 7371 R5A © 2007 Ericsson - 151 -

RNC or RBS – Loss of Frame

This shows the result of a loop back on a port.

7 Performance Management

LZT 123 7371 R5A © 2007 Ericsson - 153 -


This module describes the Performance Management for WCDMA Radio Access Network.

OBJECTIVES


• Detail the Performance Management Architecture,

• Explain the Subscription Profile principle,

• Explain the process of performance statistics data collection,

• Explain the process of performance recording data collection,

• Explain the process of General Performance Event Handling,

• Explain the Performance Data flow.



LZT 123 7371 R5A © 2007 Ericsson - 155 -

OVERVIEW This module describes the Operation and Maintenance view of Performance Management in WCDMA RAN.

Subscription profiles are defined to collect data on the WCDMA RAN Nodes. Different types of data collection can be setup: Performance Statistics, Performance Recordings (User Equipment Traffic Recordings (UETR) and Cell Traffic Recording (CTR)) and General Performance Event Handling (GPEH).

The data collection, specified within a Subscription Profile, is performed on the WCDMA RAN nodes by performance monitorings or scanners.

Scanners are feeding ROP files with the performance data from the observed objects. These ROP files are regularly transferred and stored in OSS-RC file system.

Performance Management toolOSS-RC

WCDMA RAN O&M NetworkWCDMA RAN O&M Network Scanner Scanner

File TransferScanner Configuration

ROP files

Observed Objects

WCDMA RAN Node

Figure 7-2: Performance Management Model.

PERFORMANCE MANAGEMENT DEFINITION

SUBSCRIPTION PROFILE

A Subscription Profile is an OSS-RC process in charge of collecting performance related data from WCDMA RAN nodes.

WCDMA RAN Operation

- 156 - © Ericsson 2007 LZT 123 7371 R5A

Subscription Profile setup consists in answering the following questions: • Which Network Elements are in the scope?

• What data is to be collected?

• When is the data to be collected?

There are three main types of Subscription Profiles: • Performance Statistics (Counter-based)

• Performance Recordings (Counter-based)

• General Performance Event Handling (Event-based)

All Subscription Profiles are persistently stored in the OSS-RC node to ensure that user settings are not lost during controlled or uncontrolled system downtime.

Performance Statistics

The performance statistic is generated from the radio and the transport network's live traffic.

The performance statistic data is created by a number of pre-defined counters in the network elements.

For new Network Elements, important statistics are pre-configured to start automatically at initial start-up. After restart, counters which were active before restart will be activated again. It is possible to manually suspend and resume statistical counters.

Performance Recordings

Using performance recordings it is possible for the operator to collect a variety of network recordings that can be used to troubleshoot, tune and optimize the network. The O & M system supports two different recordings.

User Equipment Traffic Recording (UETR)

UETR is used to record the operator-selected inter-node events (layer 3 messages) and/or radio environment measurements for selected mobiles. The mobiles to trace are defined by the operator using their IMSI numbers. The UETR function allows the operator to trace a selected UE travelling through a network and record its behavior. Up to 16 UETRs per RNC can run in parallel with one UE connection each


LZT 123 7371 R5A © 2007 Ericsson - 157 -

Cell Traffic Recording (CTR)

CTR is used to record the inter-node events (layer 3 messages) for a selected cell. The operator may select one triggering event from a list of available triggering events to initiate the start of the recording of each UE connection. The default triggering event is the RRC protocol message, RRC Connection Setup. Up to 2 CTRs per RNC each with up to 16 UE connections is possible to run simultaneously.

General Performance Event Handling

In order to efficiently being able to monitor, tune and perform trouble shooting in a radio network it is important that the RAN system can provide suitable measurement data. Typically, statistical counters provide good information for continuous monitoring and tuning of the network, but for deeper trouble shooting, statistical data is often not enough. Event recording, with possibilities to follow what happens with specific calls, is therefore an important complement to counters.

General Performance Event Handling (GPEH) provides powerful means for monitoring, tuning and performing trouble shooting of the radio network, using more than 240 possible events.

GPEH can monitor the following different kinds of event data: • Node (RNC and RBS) internal events

• RNC node external signaling events

• "Smart events"

Node internal events are events that are triggered by and provide information about the internal processes of the RNC and the RBS, e.g. the capacity management function, channel switching function.

Node external signaling events are events that capture the interface protocol signaling, i.e. RANAP, RNSAP, NBAP and RRC, going to and from the RNC. The events can optionally be configured to include the signaling message contents.

Smart events are events that have been specially designed to capture important error, fault or service failure cases. Two such events are available, System Release Event and the System Blocking Event: • The System Release Event is triggered whenever an abnormal

release of a service is performed. It includes information on UE identity, Radio Access Bearer and rate, the best cell and the other cells in the active set, the latest uplink interference

WCDMA RAN Operation

- 158 - © Ericsson 2007 LZT 123 7371 R5A

measurements and a large number of cause codes with indications of why the call was released

• The System Blocking Event is triggered when there is an admission reject. It includes among other things information about current and requested Spreading Factor, blocking procedure, if the request is for handover, if it is over Iur, if it is for Compressed Mode as well as a large number reasons for the blocking

SUBSCRIPTION PROFILE MANAGEMENT TOOL

In order to manage Subscription Profiles, the Performance menu of OSS-RC Network Explorer is used.

Figure 7-3: Performance Management Tool

DATA COLLECTION PROCESS The data collection process aims at gathering data, required by the active subscription profiles, from the WCDMA RAN Nodes to OSS-RC in an efficient way, while ensuring data consistency in case of network disturbances.

The data collection process is roughly similar for all types of subscription profiles: • A performance monitoring, or scanner, in each WCDMA RAN

node, is associated to a subscription profile, and collects performance data from the node’s resources.

• Data is stored locally in ROP files, and collected by OSS-RC.

• Data is stored in the Performance Management System file system in OSS-RC, ready for further processing.


LZT 123 7371 R5A © 2007 Ericsson - 159 -

RBS RNC

CTR GPEHGPEHSTATS UETRSTATSSTATS

Core Network

Iub Iur

Iu Iu

UE

Uu

CTR GPEHSTATS UETR

STATSSTATS

WCDMA Recording File

ViewerCTR GPEH UETR

PMS File system

GPEHGPEH

GPEHGPEH Recording & Events Interface (REI)

Figure 7-4: Performance Management Data Collection Process

PERFORMANCE STATISTICS

Performance Statistics ROP files are following the flow described in figure below.

RBS RNC

STATSSTATSSTATSIub

UE

Uu

STATS

STATSSTATS

PMS file system Xml ROP files(Stored for configurable time)Xml ROP files(Stored for configurable time)

Xml ROP files (Stored for at least 1 hour)Xml ROP files (Stored for at least 1 hour)

Figure 7-5: Performance Statistics Data Collection Process

Performance Monitoring

The statistical data is made available every Result Output Period (ROP) in a file in XML format that is automatically compressed. The statistical ROP files are prepared every 15 minutes and the granularity of the fetched ROP files is 15 minutes. At the end of each period the files are fetched by OSS-RC.

The statistical ROP files are stored persistent at the Network Element itself for at least 24 hours as backup in case any transmission problem would occur during transfer time.

The network elements (RNC, RBS and RXI) provide a machine-machine interface allowing OSS-RC to collect generated ROPs and also to administer the setup and collection of them.

WCDMA RAN Operation

- 160 - © Ericsson 2007 LZT 123 7371 R5A

Performance Management Subsystem File Access

Performance Statistics ROP files, transferred from the RAN nodes, are first stored, in OSS-RC, on the Performance Management Subsystem (PMS) file system.

They can then be fed into a data processing chain, based on Statistical Data Mart (SDM - Ericsson Solution) or an external system.

PERFORMANCE RECORDINGS

Performance Recording ROP files are following the flow described in figure below.

RBS RNC

CTR UETR

Core Network

Iub Iur

Iu Iu

UE

Uu

CTR UETR


ViewerCTR UETR

PMS file system

Binary ROP files collected from nodes

Converted to or tab-delimited text using WCDMA Recording File Viewer

Converted to or tab-delimited text using WCDMA Recording File Viewer

Recording & Events Interface (REI)

Figure 7-6: Performance Recording Data Collection Process


The recorded data is collected into files (ROP Files) and are fetched from the network elements by OSS-RC after each ROP period (15 minutes).

The recording data uses a proprietary Ericsson format.

The recording file will be stored persistently at the network element itself for at least one hour as backup in case any transmission problem would occur during transfer time.


LZT 123 7371 R5A © 2007 Ericsson - 161 -

The RNC provides a machine-machine interface allowing OSS-RC to collect generated ROPs and also to administer the setup and collection of them.


Performance Recordings ROP files, transferred from the RAN nodes, are first stored, in OSS-RC, on the Performance Management Subsystem (PMS) file system.

They can then be read using the WCDMA Recording File Viewer OSS-RC application, as shown in figure below.

Figure 7-7: WCDMA Recording File Viewer

WCDMA RAN Operation

- 162 - © Ericsson 2007 LZT 123 7371 R5A

GPEH

GPEH ROP files are following the flow described in figure below.

RBS RNC

GPEH

Core Network

Iub Iur

Iu Iu

UE

Uu

GPEH


ViewerGPEH

PMS file system

GPEHGPEH

GPEHGPEH

Binary ROP files collected from nodes

Converted to text or tab-delimited using WCDMA

Recording File Viewer

Recording & Events Interface (REI)

Figure 7-8: General Performance Event Handling Data Collection Process


The recorded data is collected into files (ROP Files) and are fetched from the network elements by OSS-RC after each ROP period (15 minutes).

The recording data uses a proprietary Ericsson format.

The recording file will be stored persistently at the network element itself for at least one hour as backup in case any transmission problem would occur during transfer time.

The RNC provides a machine-machine interface allowing OSS-RC to collect generated ROPs and also to administer the setup and collection of them.


Performance Recordings ROP files, transferred from the RAN nodes, are first stored, in OSS-RC, on the Performance Management Subsystem (PMS) file system.


LZT 123 7371 R5A © 2007 Ericsson - 163 -

As for the Performance Recordings, the files can be read using the WCDMA Recording File Viewer OSS-RC application, as shown in figure 7-7.

Moreover, GPEH data, typically used for tracing problems, can be compiled in an XML file by the Event Based System for WCDMA (EBS-W). It can then be used to create event-based reports.

DATA COLLECTION MANAGEMENT

Management of the data collection process is done mainly from the Performance Monitoring Management GUI, accessible from the Data Collection Subscription Profile GUI, as shown in figure below.

Figure 7-9: Performance Monitoring Management GUI

The transfer of files from the WCDMA RAN nodes to the OSS-RC Performance Management System (PMS) file system is performed over the management interfaces Mub (RBS), Mur (RNC) and Mut (RXI).

The collection process is automatic, and logs an event if a problem occurs during the transfer. Recovery of files is activated automatically when the connection to the node is back up and running.

8 Security Management

LZT 123 7371 R5A © 2007 Ericsson - 165 -


This module describes the Security Management for WCDMA Radio Access Network.

OBJECTIVES


• Detail the architecture of security management in WCDMA RAN,

• Explain the principle of Security Zones,

• Explain how secure access to WCDMA RAN nodes and management is implemented,

• Get information related to attacks and misuses of the system.



LZT 123 7371 R5A © 2007 Ericsson - 167 -

OVERVIEW The purpose of Security Management in WCDMA RAN is to: • Provide a perimeter protection for resources located in the

Operation and Maintenance Center (OMC)

• Limit connectivity and exposure of resources through filtering in the O&M Router and division in security zones

• Use secure protocols for O&M communication towards Network Elements (NEs)

• Stop, limit and track external and internal attacks, whether malicious or fortuitous.

SECURITY FEATURES This section describes the security features implemented on a scenario where OSS-RC is used to manage WCDMA RAN.

Security Zones are defined with a dedicated role and security features adapted to the possible threats.

Traffic between Security Zones is tightly controlled by a central firewall.

Basic tools used to detect and investigate security breaches are Alarm Status Matrix and Alarm List Viewer, Log Viewer.

SECURITY ZONES

In order to securely manage WCDMA RAN using OSS-RC, six Security Zones have been defined. This division allows stopping or limiting the extent of an attack to one zone. The six Security Zones involved are: • WCDMA RAN Security Domain,

• OSS Services Security Domain,

• NMS Security Domain,

• OCS Thin Client Security Domain,

• OCS Services Security Domain,

• Infrastructure Security Domain.

WCDMA RAN Operation

- 168 - © Ericsson 2007 LZT 123 7371 R5A

FirewallFirewall

OCS Thin ClientSecurity Domain

OCS Thin ClientSecurity Domain

OCSThin Client

OSS ServicesSecurity DomainOSS Services

Security Domain

OSS Master Server,PM Server, BAS,

Alex


Security Domain


Alex

WRAN Security DomainWRAN Security Domain

RBSs RXIs RNCs

NMS Security DomainNMS Security Domain

NetworkManagement

System


NetworkManagement

System

OCS ServicesSecurity DomainOCS Services

Security Domain

Application Server,Unix WS,

Windows WS


Security Domain


Windows WS

InfrastructureSecurity DomainInfrastructure

Security Domain

DNS, DHCP, NTPSMRS, SLS, DS


Security Domain


Figure 8-2: Security Zones.

Each Security Zone has a specific role, and has built-in security features adapted to its environment. For instance, on the WCDMA RAN Security Domain, an attacker, who would have managed to connect to a WCDMA RAN node, would not be able to access any other WCDMA RAN node.

TRAFFIC CONTROL

Traffic between the different Security Zones is tightly controlled in order to prevent attackers from altering or accessing data on the network.

Traffic control is performed by the firewall, which is a mandatory waypoint. Traffic control can be based on protocol type and/or port number. ALEX provides guidelines on the protocols and ports that need to be allowed between Security Zones.

NMS Traffic

The Network Management Systems (NMS) of operators need to get access to services and applications like alarm notification, performance data or Bulk Configuration Manager (BCT and BCR), available in OSS-RC. These services are all implemented on the OSS Services Security Zone, so NMS access needs to be restricted to this zone, with only authorized protocols, as described in the following figure.


LZT 123 7371 R5A © 2007 Ericsson - 169 -

FirewallFirewall


Security Domain


Alex


Security Domain


Alex


NetworkManagement

System


NetworkManagement

System

All Protocols

• FTP• SSH• SNMP• SQL• IIOP• SSL-IIOP

Figure 8-3: NMS Traffic.

SMO Traffic

The SMO tool is available on the Unix/Windows Workstations of the OCS Services Security Domain. SMO commands are transferred to the SMO server on the OSS Services Security Domain through the firewall, and information is sent back to the Workstation again via the firewall.

The SMO database is updated with information coming from the NEs in the WCDMA RAN. Direct connection, via the firewall, between OSS Services and WCDMA RAN Security Domains allows it.


Security Domain


Windows WS


Security Domain


Windows WS

FirewallFirewall


Security Domain


Alex


Security Domain


Alex

• IIOP/SSL-IIOP for SMO GUI

IIOP to SMO Java applet


RBSs RXIs RNCs


RBSs RXIs RNCsIIOP for CORBA

requests

• IIOP/SSL-IIOP for Cello NE to SMO callback

Figure 8-4: SMO Traffic.

WCDMA RAN SECURE ACCESS In order to protect WCDMA RAN from attackers and misuse, all available accesses to WCDMA RAN implement security features.

The WCDMA RAN Security Domain is accessible by:

WCDMA RAN Operation

- 170 - © Ericsson 2007 LZT 123 7371 R5A

• Network Management Centre (NMC) domains, via a firewall,

• Any person on a WCDMA RAN node site, via Site LAN.

NMC ACCESS CONTROL

Access to the Embedded Element Management functions in the WCDMA RAN NEs, from the NMC, is controlled by the firewall.

Secure traffic protocols are used, on authorized ports.

Security Checks

In order to ensure that WCDMA RAN node access is performed with secured protocols, the operator can check that the Node Security State is set to ON.

From the OSS-RC Network Explorer (ONE) GUI, right click on the node you want to check, and then select Modify Network Element. Go to Connectivity 1 pane, and check Security State attribute.

Figure below presents a NE, which has its Security State set to OFF. This NE will not require secure protocols to be used by OSS-RC.

Figure 8-5: Node Security State.

In order to enable the use of secure protocols for a Network Element, Security State needs to be set to ON. Then, a secured username and password need to be specified


LZT 123 7371 R5A © 2007 Ericsson - 171 -

Figure 8-6: Secure Password setup

SITE LAN ACCESS CONTROL

WCDMA RAN sites, and especially RBS sites, are spread over a whole region or country, and so are the less protected against physical intrusion. An attacker getting access to a WCDMA RAN site, and connecting to the local node via site LAN, could be a major threat to both WCDMA RAN and O&M networks if no security features were implemented.

Node Isolation

At O&M traffic level, WCDMA RAN nodes are not directly connected to each other, but are all directly connected to the Common O&M Infrastructure.

So, when a connection request is sent from the site LAN of a WCDMA RAN node, the user needs to go through a secure identification process, implemented on the OCS Services Security Domain zone.

This is enforced using, amongst other features, strict static IP routes in the RAN nodes. Access to these IP routes is critical in term of security, and should be restricted to security engineers.

WCDMA RAN Operation

- 172 - © Ericsson 2007 LZT 123 7371 R5A

FirewallFirewall


Security Domain


NE

Site LAN

NE1

2


Security Domain


Windows WS


Security Domain


Windows WS

3

Figure 8-7: Node Isolation.

DETECTION AND INVESTIGATION TOOLS In terms of security breaches, most of the tools used for detection and investigation are focusing on layers from IP up to Application.

Several tools are available on WCDMA RAN level. Alarm Status Matrix combined with Alarm List Viewer can be used to detect some security breaches; for instance an opened door on a site, which could be increasing the risk of attack, can be set up to trigger an alarm.

The Log Viewer tool can be regularly checked to track what is done from OSS-RC to the network. The most noticeable logs in an investigation are the command logs, which stores all the commands used from OSS-RC, and the security logs.

Figure below shows the command logs for OSS-RC. The user attribute can be used to detect misuse or attacks originating internally at the operator NMC.

Lzt 123 7371 r5 a wcdma ran operation

Documents

Transcript of Lzt 123 7371 r5 a wcdma ran operation