Alcatel 9135 OMC-Radio.pdf

9153 OMC-R Product Description

Alcatel-Lucent File Reference Date Edition Page PD1353E9.DOC 3DC 21076 0005 TQZZA 08/02/2008 09 1

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization.

9153 OMC-R

Product Description




SCOPE

This document gives a description of the Alcatel-Lucent 9153 Operation & Maintenance Center Radio (9153 OMC-R) product managing Alcatel-Lucent GSM radio network.

Its major purpose is: - To provide general information about the 9153 OMC-R product, - To give technical data for the different 9153 OMC-R configurations and components.

Nota: 9153 OMC-R is the new name for the former A1353-RA OMC-R product. This new name simply replaces the previous one, without any changes in the functional content of the product.




CONTENTS

1. INTRODUCTION .................................................................................................. 6

1.1 Introduction to 9153 OMC-R Product................................................................. 6

1.2 9153 OMC-R embedded in the Network Management environment ............................ 8

2. OVERVIEW OF 9153 OMC-R CONFIGURATIONS .............................................................. 9

2.1 Components of an 9153 OMC-R ....................................................................... 9

2.1.1 OMC-R Configurations........................................................................11

2.1.2 User Terminals ................................................................................12

2.1.3 HMI Servers ....................................................................................12

2.1.4 OMC-R Components Hardware Generations..............................................13

2.1.5 Software .......................................................................................13

2.2 9153 OMC-R Dimensioning ............................................................................15

2.2.1 BSS Capacity per OMC-R Configuration ...................................................15

2.2.2 User Sessions per OMC-R Configuration...................................................16

2.3 BSS O&M Configuration................................................................................17

2.3.1 OMC-R Topologies ............................................................................17

2.3.2 OMC-R – BSC interconnection...............................................................19

2.3.3 OMC-R –MFS (GPRS) interconnection ......................................................20

2.4 Centralized Management..............................................................................20

2.4.1 Alarm Call Out ................................................................................20

2.4.2 Automatic O&M actions .....................................................................21

2.4.3 Centralized management via Network Management System (NMS)..................22

2.5 Network Management Interface .....................................................................23

2.6 BSS Performance Management.......................................................................24

2.6.1 9153 OMC-R Performance Management ..................................................24

2.6.2 9159 Network Performance Optimizer (NPO)............................................24

3. ALCATEL-LUCENT UNIVERSAL ROUTING ....................................................................25

3.1 Introduction .............................................................................................25

3.2 Routing and Trunking of O&M Links between BSC and OMC-R through MSC .................26

3.3 Routing and Trunking of O&M Links between BSC and OMC-R through NGN .................27

3.4 Alcatel-Lucent Universal Routing router configurations.........................................28

3.4.1 Case of networks with MSC .................................................................28

3.4.2 Case of networks with NGN.................................................................28

4. 9153 OMC-R – OPERATION SITE...............................................................................30

4.1 Site requirements ......................................................................................30




4.2 Site example ............................................................................................30

5. TECHNICAL DATA OF THE 9153 OMC-R COMPONENTS....................................................31

5.1 Generalities .............................................................................................31

5.2 UltraSparc III generation ..............................................................................31

5.2.1 Small OMC-R master server platform .....................................................31

5.2.2 Standard OMC-R master server platform .................................................32

5.2.3 Large OMC-R master server platform .....................................................32

5.2.4 Extra Large OMC-R master server platform..............................................32

5.2.5 Extra Large OMC-R agent server platform ...............................................32

5.2.6 Small standard HMI server ..................................................................33

5.2.7 Standard HMI server..........................................................................33

5.2.8 User WorkStation (WS) ......................................................................34

5.3 UltraSparc IV generation..............................................................................37

5.3.1 Small OMC-R master server platform .....................................................37

5.3.2 Standard OMC-R master server platform .................................................37

5.3.3 Large OMC-R master server platform .....................................................38

5.3.4 X Large and XX Large OMC-R master server platform..................................38

5.3.5 X Large and XX Large OMC-R agent server platform ...................................38

5.3.6 Standard HMI server..........................................................................39

5.3.7 Large HMI server..............................................................................40

6. ANNEX: BANDWIDTH REQUIREMENTS AT OMC-R INTERFACES ...........................................42

7. ABBREVIATIONS .................................................................................................43




List of figures

Figure 1: 9153 OMC-R Functional Management Domain.............................................................. 6

Figure 2: OMC-R positioning in TMN ..................................................................................... 8

Figure 3: Alcatel-Lucent BSS Network Management Environment.................................................. 8

Figure 4: 9153 OMC-R Single Configuration Overview ................................................................ 9

Figure 5: 9153 OMC-R Distributed Configuration Overview.........................................................10

Figure 6: Single Agent OMC-R Topology................................................................................17

Figure 7: Alarm call out options.........................................................................................21

Figure 8: 9153 interfaces synoptic......................................................................................23

Figure 9: PM front-office and back-office approach .................................................................24

Figure 10: MSC case for Routing and Trunking of X.25 links between BSCs and OMC-R .......................26

Figure 11: Server room....................................................................................................30

Figure 12: Exploitation room ............................................................................................30




1. INTRODUCTION

1.1 Introduction to 9153 OMC-R Product

In the GSM world, the OMC or Operation and Maintenance Center is defined as a system responsible for operation and maintenance of a given set of network equipments.

In compliance with the GSM specifications, the 9153 Operation & Maintenance Center for Radio Part (OMC-R) is concerned with Element Management and Sub-Network Management of BSS network subsystem:

- The whole set of BSSs, i.e. BSCs, BTSs, TCs and transmission systems - GPRS Multi-BSS Fast packet Server (MFS), i.e. the BSS part of GPRS equipment.

9153 OMC-R is a management system based on one or several UNIX servers connected with a number of user terminals via Ethernet-LAN or WAN (depending on the network configuration) and with a number of BSCs and MFSs that have to be managed. Figure 1 shows an overview of OMC-R with respect to managed elements physical and functional interconnection.

BTS

OMC-R

9153

BSC

MFS

TC MSC

SGSN

BTS

GPRS

GPRS

O&M O&M

O&M

O&M

O&M

Physical Interfaces O&M Functional Interfaces

Functional Domain9153 OMC-R

Abis Ater Ater A Itf .

Gb Itf.

X.25 TCP/IP

Figure 1: 9153 OMC-R Functional Management Domain




Operation and maintenance functions used for BSS and GPRS/EDGE management can be organized into some of the functional management domains specified by ITU-T M.3010. These domains are:

- Performance Management (PM)

BSS Performance Management handles administration, scheduling and triggering of measurement campaigns to be performed per BSC and MFS in order to supervise the Quality of Service (QoS) offered to telecom subscribers. It provides retrieval, forwarding, processing, presentation and archiving of measurement results. At OMC-R level two types of measurement results are handled:

(1) BSS observation counters, i.e. retrieval of proprietary measurement results for display, analysis and export (in binary or ASCII format).

(2) BSS performance indicators for dedicated supervision of QoS information and fast

detection of telecom service degradation. Performance indicators can be compared with user defined thresholds allowing the generation of QoS alarms (handled by the standard OMC-R alarm handling function). These indicators are also displayed and analyzed thanks to graphic or tabular reports.

- Configuration Management (CM)

BSS Configuration Management provides hardware management (BSS network extension, reduction or reconfiguration), software management (BSS software release migration), logical configuration management (BSS radio parameter adjustment for optimized configuration of radio related resources), as well as BSS date and time management. 9153 OMC-R also provides functions for extensive and time efficient logical configuration management with minimum telecom impact, e.g. massive adjustment of parameters for an optimized radio configuration or network wide activation of a new frequency plan.

- Fault Management (FM)

BSS Fault Management offers network supervision through alarm handling, status monitoring of equipment and resources, equipment handling and test management. In addition, the Alcatel-Lucent BSS supports autonomous recovery of GSM resources through reconfiguration of BTS in case of TRX failures.




A single OMC-R configuration can supervise multiple BSSs (the BSCs with all related BTSs), BSSs connected to different MSCs depending on the chosen configuration and multiple GPRS MFSs. Moreover, the OMC-R provides the capability to be connected to a Regional or Network Management Center (NMC) via vendor independent Q3 BSS mediation interface or via any available external interfaces.

1.2 9153 OMC-R embedded in the Network Management environment

9153 OMC-R follows the Hierarchical Network Management approach defined in TMN standards; it takes the functional role of an element manager of Alcatel-Lucent BSS network elements:

BTS MFS

OMC-R

NMC

Business Management

Service Management

Network Management

Element Management

Network ElementBSC

Figure 2: OMC-R positioning in TMN

In order to support customer external applications such as BSS radio network planning and optimization, interfaces towards ‘Alcatel-Lucent Network Engineering Tools' are supported. Benefit from these environment tools can be taken either by direct acquisition and usage through BSS network operators or by taking up dedicated all-in-One service options.

OMC-R NMC Element Manager Network Manager

Radio Network Planning

Network Performance Optimizer

9153

BSC Network Elements

9120 or 9130

9155 9159

Initial Configuration

ConfigurationData

PM Data

Cell Design Data

Alcatel or other MFS Network Elements

9135 or 9130

Alarms, State Changes and User Logs

Figure 3: Alcatel-Lucent BSS Network Management Environment




2. OVERVIEW OF 9153 OMC-R CONFIGURATIONS

2.1 Components of an 9153 OMC-R

9153 OMC-R architecture allows a flexible distribution of management components across the different nodes of the network according to specific needs related to for instance network dimensions and performance requirements. By means of this configuration flexibility, the management system can evolve and be adapted to new dimensioning requirements, adding new machines where necessary.

The main hardware configurations supported by 9153 are: - Single server configuration with front-end workstations and X-terminals: NMC

User Terminals

Peri Devices

Printers

Q3 Mediation

OMC-R Master Server

Database

LAN / WAN DCN

LAN/WANDCN

HMIServer(s)

local lan local or remote lan

OMC-R Domain

User Terminals

Peri Devices

Printers

X25 Connection IP Connection

9120 BSC

9130 BSC Evolution

9130 MFS Evolution9135 MFS

Figure 4: 9153 OMC-R Single Configuration Overview




- Distributed configuration with three dedicated servers and front-end workstations, and X-

terminals:

NMC

User Terminals

Peri Devices

Printers

Q3 Mediation OMC-R

Master Server

Database

OMC-RAgent Server

Database

LAN / WAN DCN

LAN/WANDCN

HMI Server(s)

local lan local or remote lan

OMC-R Domain

UserTerminals

PeriDevices

Printers


9120BSC

9135 MFS


9120BSC

9135 MFS

OMC-RAgent Server

Database

9130 MFS Evolution

9130 MFS Evolution

9130 BSC Evolution

Figure 5: 9153 OMC-R Distributed Configuration Overview

The physical hardware configuration of an OMC-R is composed of - Master Server:

Unix Server, whose main purpose is to run the OMC-R management application. In particular, this server hosts system administration functions, Alarm Database and Surveillance module, Q3 mediation and the Radio Network Configuration database. In the Single server configuration only, this host server mediates also data from the Network Elements, and stores these data in the BSS database.

- Agent Server:

Unix Server, only present in the distributed configuration, whose main purpose is to host the mediation of group of Network Elements in order to increase the capacity of the OMC-R.




- HMI Server:

Unix Server whose main purpose is to enhance the performance of the system by moving the user interface part of the processing from the master Server to the HMI Server. In case of remote user terminals, a HMI server is required to ensure the terminal performances, which might be limited by weak transmission capability.

- User Terminal:

Graphical Workstations connected to the master Server or to the HMI Server.

- Laser or line printers (optionally)

The requirements in term of bandwidth on the OMC-R host server interfaces are described in ANNEX.

Besides the OMC-R application software, the software part includes third-party software (e.g. Sun Solaris OS, Object Store database, X.25 protocol, OSI stack, etc.).

2.1.1 OMC-R Configurations

Depending on the size of the BSS network that has to be supervised, five types of OMC-R configurations have been described as generic. The relevant BSS capacity for each OMC-R configuration is listed in the table of Section 2.2.1:

- Small OMC-R configuration (SML) - Standard OMC-R configuration (STD) - Large OMC-R configuration with two variants (LRG) - Extra Large OMC-R configuration (X-Large) (XLRG) - Extra Extra Large OMC-R configuration (XX-Large) (XXLRG)

The first three configurations have only one Master Server and no Agent Server. The X-large configuration (distributed configuration) is composed of one Master Server and one or two Agent Servers (depending on server generations). The XX-Large configuration is composed of one Master and two Agent servers (UltraSparc IV generation only).

OMC-R host and HMI Servers are built on Sun Microsystems™ servers. Two generations of these servers are used:

- UltraSparc III generation since B7 release




- UltraSparc IV generation since B8 release

OMC-R host servers (Master or Agent) are built on Sun Fire™ (UltraSparc III and UltraSparc IV generations) servers which are the highest fault-resistant systems in their class. They offer excellent Reliability, Availability, and Serviceability (RAS) features. As an example, autonomous restoration mechanisms are supported in case of following failures:

- Power supply and cooling module failure - CPU failure - Memory failure - Disk failure (RAID technology, 100 % data redundancy, hot plug disks).

2.1.2 User Terminals

Workstations (WS) are used as user terminals. Workstations are client graphical terminals running on their own operating system. They can be used as terminals to operate the network with the OMC-R application but it is also possible to run some applications (e.g. measurement post processing) without impacting server resources.

OMC-R terminals are not dedicated to an OMC-R and an operator can use the same terminal to access different OMC-Rs (and possibly other applications).

The OMC-R supports the two following categories of terminal:

• Terminals running SUN™ Solaris and supporting the X11 protocol

• Terminals running Citrix Metaframe™ clients, e.g. PC under Microsoft™ Windows. The Citrix Metaframe™ client software is installed on the terminals and is communicating with the Citrix Metaframe™ server software, hosted on the OMC-R HMI server. The maximum number of user sessions supported by this Citrix HMI server is in this case reduced by one user (except for the Tiny HMI server)

2.1.3 HMI Servers

There are several kinds of HMI servers, each of them providing a different capacity in terms of number of operator sessions depending on the OMC-R type they are connected to.

All HMI servers can be located either at the OMC-R site or remotely depending on the chosen operating topology. The large capacity HMI servers are usually located at the OMC-R site when the small capacity servers are often remotely located.




From release B10, when NPO option is used on OMC-R, the number of user sessions supported by HMI servers is reduced.

2.1.4 OMC-R Components Hardware Generations

The following table defines the hardware reference of the OMC-R host and HMI server per type of configuration. OMC-R server HMI server

- Sun Blade 150, Ultra25 Tiny - - Sun Fire V880 Sun Fire 280R Small Sun Fire V490 Sun Fire V440 or Netra 440 Sun Fire V880 Sun Fire 280R Standard Sun Fire V490 Sun Fire V440 or Netra 440 Sun Fire V880 - Large Sun Fire V490 with external disk bay SE3510

Sun Fire V440 or Netra 440

Sun Fire V880 (x2) - X-Large Sun Fire V490 with external disk bay SE3510 (x2)

-

- - XX-Large Sun Fire V490 with external disk bay SE3510 (x3)

-

The workstations can be either Sun U5/U10, or Sun Blade series 100/150, or Ultra25 or any terminal when a Citrix solution is used (Universal terminal concept).

Please refer to the document “9153 OMC-R SUN Hardware Evolutions” (reference 3DC 20006 0019 UZZZA) to check the support of the different servers and configurations by the BSS software releases.

2.1.5 Software

The software part of the 9153 OMC-R is based on the Alcatel Management Platform (ALMAP 3). ALMAP offers a powerful development environment (COMET) and a set of reusable components that fulfill telecommunication operator requirements.

The architecture of ALMAP is object-oriented and complies with the major TMN and system management standards issued by ITU-T, ETSI and ISO and with recommendations from industry forums such as NMF. The ALMAP architecture is designed to support integration, scalability and flexibility.




ALMAP provides a comprehensive family of generic component reusable for the development of Network Management products. These generic components cover the functions common to all Network Management products, such as alarm surveillance (compliant with X733 standards), security (management of user accounts with profiles definition allowing to associate functions and network elements to a user) or system management functions. The open architecture permits to reuse or share these components across the Alcatel Management products for different telecommunication areas, including access, transmission, switching or mobile networks, thus providing the operator with a homogeneous management system, and also minimizing Alcatel Element and Sub-Network Managers cost of ownership.

ALMAP is multi-OS platform. In the BSS case, only the SUN Solaris compatible version of ALMAP is used. ALMAP has been regularly updated according to the different version of Solaris, from 2.6 up to Solaris 10.

In addition to ALMAP, other third-party softwares are used on OMC-R: - Communication stacks: Solstice X.25, OSI and CMIP - Graphical window management: X11 and Motif, Windows CDE, - OMC-R database: Object Store distributed database (Progress Software), - Help and documentation on-line: HTML Server and/or Navigator, - Database for BSS Performance Management: Oracle




2.2 9153 OMC-R Dimensioning

The following tables give for each type of OMC-R configuration the maximum number of supervised equipments, by type of equipment (BSC equivalents1, cells, TRX) according to the release traffic model.

2.2.1 BSS Capacity per OMC-R Configuration

The two following tables (one for UltraSparc III generation and one for UltraSparc IV generation) gives for each type of OMC-R configuration the number of hosts (master + agents), the maximum number of BSS network elements that can be managed by each OMC-R configuration. Higher number of network elements must be served by further OMC-R configurations (wherever located).

Remark: Each configuration is the upper limit for a given OMC-R configuration, i.e. maximum number of either BSCs or cells or TRXs. Those figures may also vary with the BSS software release (details are available in the document “9153 OMC-R SUN Hardware Evolutions” / reference 3DC 20006 0019 UZZZA).

OMC-R Capacity per configuration with UltraSparc III generation

OMC-R Configuration

Number of OMC-R servers

Max. number ofBSC equivalents

Max. number of Cells

Max. number of TRXs

Small 1 10 250 1 250

Small with NPO embedded 1 10 250 1 250

Standard 1 20 500 2 500

Large-1 1 35 1 200 6 000

Large-2 1 45 1 500 7 500

X-Large 2 100 4 000 20 000

• 1 'BSC equivalent' is defined as standardized load of the NE in terms of O&M capacity of the OMC-R. The following NE types must be considered:

- BSC: 1 9120 BSC or 1 9130 BSC Evolution = 1 BSC equivalent - MFS: 1 9135 MFS or 1 9130 MFS Evolution = 2 BSC equivalent

All BSCs and MFSs that are associated to each other must be connected to the same OMC-R configuration.




OMC-R Capacity per configuration with UltraSparc IV generation

OMC-R Configuration

Number of OMC-R servers

Max. number ofBSC equivalents

Max. number of Cells

Max. numberof TRXs

Small 1 10 250 1 250

Small with NPO embedded 1 10 250 1 250

Standard 1 20 500 2 500

Large-1 1 35 1 200 6 000

Large-2 1 50 1 800 9 000

X-Large 2 100 4 000 20 000

XX-Large 3 120 6 000 30 000

2.2.2 User Sessions per OMC-R Configuration

Exact architecture of an OMC-R depends both on PLMN network architecture and PLMN Operator’s internal organization (e.g. OMC-R user terminals concentrated in a single location or distributed among several different places).

In some cases, the OMC-R master can directly serve a few numbers of user terminals that are located in a single site (i.e. connected to a single local area network). In other cases, HMI servers might be required in order to handle remote terminals allocated to the local OMC-R or to increase the number of local sessions beyond some limit as defined in the document “9153 OMC-R SUN Hardware Evolutions” (reference 3DC 20006 0019 UZZZA).

The maximum number of user terminals is not limited in principle. One user session is used for each user connected to the OMC per user terminal (a session is identified by the couple user / user terminal).

Depending of the actual number of managed Network Element managed by the OMC-R, the configuration (number and type of HMI servers) can be different and only depends on the required number of user sessions.

All HMI servers of all generations can be used connected to an OMC-R whatever the generation of the server. But number of sessions can vary according to the BSS Release.

From B10 release, OMC-R controls globally the number of simultaneously opened views and windows. This new user activity control allows on principle an “unlimited” number of user logins and optimizes available OMC-R resources usage.




Due to available physical resources on HMI servers (processing power and memory), there is still a maximum number of user sessions per HMI server. And this limit can be lowered when NPO option is installed on the OMC-R.

2.3 BSS O&M Configuration

2.3.1 OMC-R Topologies

The OMC-R architecture offers several topologies that allow a wide flexibility to operate the network. Figure 6 represents a typical one with

- one OMC-R master server and several terminals at the local OMC-R site, - two remote sites with small HMI servers and remote terminals.

OMC-R Master Server

R

R

BSS

Remote Site

Remote Site

LocalSite

WAN WAN

SmallHMI Server

SmallHMI Server

R

WAN

PSDN BSS

IP

Figure 6: Single Agent OMC-R Topology

The terminals are connected with a LAN (Ethernet 10 or 100 Mbit/s) either directly to the OMC-R host server (master) or, where used, to the HMI server. To ensure proper operation and performance in communications between units on the LAN, a "true" IP Ethernet switch should be used (not a common hub unit) with:

- RJ45 ports with 10/100 Mbps base Tx auto detection flow rate, - IP multicast switching full duplex capacities - plug and play installation facilities.




In case of remote installations, a routing device (R) is needed in order to establish the necessary connection towards HMI clients or other OMC-R agents.




2.3.2 OMC-R – BSC interconnection

The OMC-R host can be connected to the BSC in several ways that give a high degree of flexibility in choosing the OMC-R site (see following Figures).

(1) Via PSDN

The OMC-R – BSC can be connected remotely through Packet Switched Data Network. In this case, up to two 64 kbit/s links at OMC-R site and one 64 kbit/s link at each BSC site may support the X.25 connection to the X.25 PSDN. For security reasons all physical X.25 connections can be configured redundantly.

(2) Co-located site

Without use of additional router, the OMC-R can be co-located with maximum one or two 9120 BSCs depending on the use of redundancy. In this case the interconnection is realized through dedicated serial lines.

In case of 9130 BSC Evolution, the BSC can be connected to the LAN where the OMC-R is also connected. In such case, there are no limitations in terms of number of BSC Evolution managed locally, except the maximum number of cells managed by OMC-R.

(3) Via A Interface – MSC Connection (Alcatel-Lucent Universal Routing)

The OMC-R can be connected remotely to the 9120 BSC or 9130 BSC at the MSC site by routing the O&M links over A/Ater interface (either X25 over A/Ater for 9120 BSC or IP over A/Ater for 9130 BSC Evolution).

BSC G2

BSC G2

OMC-R OMC-R PSDN

1

OMC-R OMC-R

9120BSC

9130BSC Evo

Dedicated X25 links

LAN

9120BSC

Trans- coder

Router

OMC-R OMC-R

A itf

MSC

9130BSC Evo




Thanks to the availability on the market of 'intelligent' multi-protocol routers, the Alcatel-Lucent ‘Universal Routing' solution is recommended as the standard solution. More detailed information about various routing configurations can be found in Chapter 3.

Deployment of NGN in the field, replacing the MSCs, requires a new way for routing the O&M links between OMC-R and NEs (BSC and MFS). This will be also detailed in chapter 3.

2.3.3 OMC-R –MFS (GPRS) interconnection

This interface requires an IP connection in order to support Q3 and FTP protocols. Whatever the generation, 9135 MFS or 9130 MFS Evolution, the MFS supports two Ethernet ports to connect directly the Local Maintenance Terminal and the OMC-R..

For the 9130 MFS Evolution, in case the MFS is co-located with BSC Evolution it is also possible to encapsulate the MFS O&M flow into the Ater interface and to use the Alcatel-Lucent Universal Routing solution to establish the O&M link between MFS and OMC-R.

The minimum bandwidth required for MFS - whatever the generation - is of 256 Kbits/s.

2.4 Centralized Management

Several possibilities exist to supervise several OMC-Rs from one central location. They are detailed here below:

2.4.1 Alarm Call Out

The Alarm Call Out (ACO) feature enhances the alarm handling service. It allows supervision of the network with a reduced number of operators, for example at nighttime or during the weekend.

ACO can be activated from any OMC-R terminal, either local or remote.

ACO applies a defined filter on the alarms received at OMC-R. Only one ACO filter can be activated per OMC-R.

The filter is based on criteria as alarm severity, alarm type, probable cause, event date and time.

This filter can be activated: - according to a defined schedule (range of days in the week and range of hours for

each day of the week) - on all the BSC or on a subset

The alarms complying with the filter are: - either sent to a printer




- or posted to predefined e-mail addresses (up to 2 different addresses), - or both sent to printer and posted to predefined e-mail addresses.

When mail is chosen as ACO output, for each alarm matching the ACO filter, a mail is sent. The definition of alarm in the mail is restricted to 160 characters.

The same 160 characters per alarm are printed out when printer is chosen as ACO output.

Printer can be either located on the OMC-R LAN or connected to a remote HMI server on a distant site.

The filtering criteria of ACO and of Alarm Surveillance (AS) module are the same. Consequently an alarm sub-list can be created in AS module in order to display the alarms verifying the ACO filter.

AS views are available on any terminals connected to local or remote HMI servers.

ACO filter and service definitions are available through a WEB browser interface.

Consequently, on condition that IP addresses of other OMC-R have been set, and routes have been opened, an operator can define the ACO filter and services for several OMC-Rs from his terminal, without having to do any remote connection on the other OMC-Rs.

.

.

.E-mail

LAN/WAN

OMC-R 5

OMC-R 1

Local or Remote HMIServer

Internet

Local Alarm

Printer

Terminal

Remote Alarm

Printer

Figure 7: Alarm call out options

2.4.2 Automatic O&M actions

Automatic O&M actions can be triggered upon immediate reception of an alarm.




These automatic actions are performed through command mode scripts defined by the operator specifically for each action.

Typical examples are:

- sending a SMS/email to on-duty people upon reception of a pre-defined set of alarms. This is equivalent to the previously described Alarm Call Out feature but with the benefit of a real-time reaction.

- Performing a well-defined action upon reception of a certain alarm (such as restarting the board concerned by the received alarm). This allows OMC-R operator concentrating on the most important alarms.

In both cases, main benefit from the feature is that it allows saving OPEX cost.

2.4.3 Centralized management via Network Management System (NMS)

Thanks to the real-time Q3 interface for Fault Management, it is possible to connect one or several OMC-R to a NMS, centralizing the network supervision.

Filtering capabilities are proposed on this interface in order to reduce the flow of alarms when several OMC-R are used, allowing central operators to concentrate only on important alarms.




2.5 Network Management Interface

The 9153 OMC-R is fully integrated in the Telecommunication Management Network (TMN). This Operation System has been designed to answer to the need for interoperability among the rapidly proliferating number of hardware and software products available today from different vendors inside the Operation and Maintenance Network of the operator. The consequence is the richness of opened interfaces allowing external applications (maintenance, engineering, customer care, quality) to access easily to the maximum data of the OMC-R.

This leads to support different 9153 OMC-R Interfaces: - The NMS/9153 OMC-R Q3 interface for network surveillance applications - The 9153 OMC-R Configuration Import/Export (ACIE) interface - The ASCII and binary interfaces for the Performance Measurement export interface - The Alarm/Event log ASCII export for the Alarm post-processing interface The Remote Inventory Export interface (ARIE)

9153 OMC-R

PMinterface(ASCII or

Binary) via FTP

Import/Export Radio

Configuration Via FTP

FM +Networkdiscovery

via Q3

ACIE RNL

BSS

mib

Export pool

BSS

mib

Q3 ACIE EML

Export equipment

Configuration Via FTP

Alarms/ Events/logs

interface ASCII via FTP

AS / ELM

ExportHardwareInventoryVia FTP

ARIE

Figure 8: 9153 interfaces synoptic

The description of the external interfaces of the 9153 OMC-R is done in the document "9153 OMC-R External interfaces Functional Description" (reference: 3DC 21010 0004 TQZZA).




2.6 BSS Performance Management

2.6.1 9153 OMC-R Performance Management

9153 OMC-R provides an internal component for the Quality of Service surveillance and alerts on the BSS network. This front office component is built upon industry standard database: Oracle. This component allows collection, processing and on-line display of BSS observation counters by means of graphs and tables (Counters and Indicators Browser). This component also warns the operator in case of QoS threshold crossing by generating alarms handled just like any other BSS alarm.

NPO Back office

OMC_PMfront office

BSS MFS

9153 OMC-R

Database binary files

Counters display and Quality of Service alerters (X733 alarm format)

Figure 9: PM front-office and back-office approach

2.6.2 9159 Network Performance Optimizer (NPO)

The above front-office activity is completed by a post-processing activity (back-office) consolidating Quality of Service information on a long period duration (weeks, months, years) and allowing forecast and trends analysis for network optimization purpose.

The optional 9159 Network Performance Optimizer (NPO) product achieves this activity. This data post-processing function generates Quality of Service and Network Performance Analysis reports with up to two years history.

In addition, NPO embeds the full set of radio optimization functions formerly provided by RNO tool, widely recognized as reference in the domain of radio optimization. For more details on NPO, refer to Alcatel-Lucent 9159 Network Performance Optimizer Product description (reference 3DC 21146 0062 TQZZA).

The small configuration of the OMC-R is able to embed the complete NPO software in order to optimize the number of needed server: one server for OMC-R and NPO.




3. ALCATEL-LUCENT UNIVERSAL ROUTING

3.1 Introduction

To be operational, an OMC-R must be connected to each of the supervised BSCs. This connection must be established through a Data Communication Network (DCN).

A solution is to use a PSDN (Packet Switched Data Network), either public or private. Such a network uses transmission links external to those used for the PLMN itself. To be applicable, such a PSDN must be available, with access to it at OMC-R site and at each BSC site. The disadvantage of this solution may be the cost:

- Cost of subscription, if a public PSDN is used, - Cost of establishing a private PSDN, including cost of dedicated leased lines, especially if

this private network has to be built only for this OMC-R – BSC interconnection purpose.

Alcatel-Lucent Universal Routing provides an alternative solution.

The principle of this solution is to use the transmission capabilities of the PLMN itself for physical base of X.25 signaling links. Hence, all BSC O&M channels (64 kbit/s each) are reserved on PCM trunk between each BSC and related MSC. This solution is made possible through the use of intelligent multi-protocol routers located at OMC-R site and MSC sites.

With this solution, the interconnection of OMC-Rs and relevant BSCs is thus realized with virtually no additional transmission means compared to those that are anyway necessary for telecom traffic purposes, i.e. the PCM links between BSCs and MSCs and between MSCs themselves. Besides, the new solution is very flexible for re-configuration of the network and insensitive to any loss of PCM resources, which is very important from an operational point of view.

Finally, if a private DCN – e.g. a corporate WAN – is available, it can be used to build the OMC-R IP network upon instead of sharing the PCM resources. This optional solution is applicable for both the BSS Universal Routing capability and the interconnection of OMC-Rs themselves, e.g. for non-operating concentration.




3.2 Routing and Trunking of O&M Links between BSC and OMC-R through MSC

Instead of interconnecting BSCs to the relevant OMC-R through PSDN links external to the PLMN itself, routing through internal PCM links is performed.

This is done using: - The O&M links available on the PCM trunks between BSC and MSC (the O&M links using

available dedicated timeslots inside the PCMs used for traffic); - Semi-Permanent Connections (SPC) or 'Nailed-up' Connections within the MSC, to route the

different O&M links to a single PCM trunk towards the OMC-R 2; - Standard G.703/704 PCM link between the MSC and the multi-protocol network router co-

located to the OMC-R. (if OMC-R and MSC are co-located, a short piece of PCM wire can be used; otherwise, a dedicated PCM trunk must be established additionally to the links already used for telecom traffic purposes).

Figure below illustrates this principle in a simple case. The following chapter gives more details about the interconnection of the OMC-R to the co-located router.

Figure 10: MSC case for Routing and Trunking of X.25 links between BSCs and OMC-R

•

2 SPCs is thus a prerequisite of the solution.

MSC site (common with MFS, TC)

BSC G2E1 links(Local)

Router Type2

E1 links(Local)

X25 serial

Router Type1

MFS

IP flowsX25 flows

O&M over ATer

MSC

OMC-R Site

BSC Evolution

TC

TransmissionNetwork

IP flows

MSC site (common with MFS, TC)

BSC G2BSC G2E1 links(Local)

Router Type2

E1 links(Local)

X25 serial

Router Type1

MFS

IP flowsX25 flows

O&M over ATer

MSC

OMC-R SiteOMC-R Site

BSC Evolution

TCTC

TransmissionNetwork

TransmissionNetwork

IP flows




This scheme is valid for both 9120 BSC and 9130 BSC Evolution, when the BSCs are not collocated with the MSC site and O&M flows are routed through Ater interface.

Remark: In the particular case of the BSC Evolution, if the customer has an IP network available, this network can be used for routing the O&M flow between the BSC Evolution and the OMC-R as well as between MFS and OMC-R.

3.3 Routing and Trunking of O&M Links between BSC and OMC-R through NGN

2 cases are possible when core infrastructure is based on NGN:

1. If the Media Gateway (MGw) offers the Semi Permanent Connection (SPC) function: the same solution as for MSC can be used (see above chapter 3.2).

2. But some of the Media Gateways currently available on the market don’t support SPC function. In this case, it is required to extract the O&M timeslots from the Ater links at TC side. Consequently, a dedicated router is used for grooming all these extracted timeslots into either an IP flow or an E1 flow depending on interfaces available at Media Gateway site.

When Media Gateway communicates with other sites through an IP network, the IP O&M flow will be routed via the IP network up to the OMC-R site. In case of network made partially or totally of 9120 BSC, another router at OMC-R site will be required in order to transform the O&M flow into its original X25 protocol terminated into the OMC-R.

MGw site (common with BSC, MFS, TC)

9120 BSC

E1 links (Local)

STM-1 link

IP Network

Call - Server

IP Router

MGw

TC

OMC - R Site

Router A

E1 links(Local)

X25 serial

Router B

MFS

ADM

IP flows X25 flows

X25 O&M extraction at TC (serial)

O&M over ATer

X25 over IP

MGw site (common with BSC, MFS, TC)

E1 links (Local)

STM-1 link

IP NetworkIP Network

Call - Server Call - Server

IP Router

9130 BSC Evolution

MGwMGw

TCTC

OMC - R Site OMC - R Site

Router A

E1 links(Local)

X25 serial

Router B

MFS

ADM

IP flows X25 flows

X25 O&M extraction at TC (serial)

O&M over ATer

X25 over IP

Figure 12: NGN Case for Routing and Trunking of O&M links between BSCs sites and OMC-R




3.4 Alcatel-Lucent Universal Routing router configurations

Remark: The router configurations are detailed in specific engineering rules documents. In the current Product Description document, only the principles of the router configurations are provided.

Several router configurations have been identified from which the different network configurations can be built. They are called ‘router types’, they come from the same family of equipment but differ by the role they play and thus the type of modules they include.

3.4.1 Case of networks with MSC - Router Type 1 is the router used systematically at OMC-R,

- has at least 2 serial interfaces towards the HSI board of the OMC-R for 9120 BSC

O&M flow (X25) - has 1 or 2 E1 interfaces for interconnection with the MSC which the O&M traffic

comes from (each E1 interface allows up to 31 BSCs max without O&M redundancy and up to 15 BSCs with link redundancy) 3

- has 1 Ethernet port for BSC Evolution O&M flow (IP) - optionally has 1 additional serial interface towards the SMS-CB Center when SMS-CB

feature has been bought by customer

- Router Type 2 is located systematically at MFS site (close to the MSC), - needed to convert MFS O&M IP flow over Ethernet into an IP flow over E1 (in order

to take benefit of the transmission network of the customer). - optionally can also be used to compress BSC O&M flow in order to reduce the

bandwidth used in inter-MSC links.

3.4.2 Case of networks with NGN

2 routers are also needed in case of NGN.

•

3 Two options regarding X.25 link availability can be chosen: - Simple X.25 connection: 1 × 64 kbps physical link between each BSC and OMC-R, - Secured X.25 connection: 2 × 64 kbps physical links, 1 active and 1 standby link.




The router B located at OMC-R site is fully similar with the one used for the MSC case. This is a router Type1.

In case the Media Gateway does not support SPC function, the router A located at Media Gateway site (same site as the MFS) is dedicated to groom/un-groom E1 TS extracted from the TC and has:

- up to 64 serial interfaces connected to same number of MT120 boards. The MT120 boards can be located into several TCs.

- 1 Ethernet interface to connect to the IP network: all E1 TS are groomed/un-groomed to/from Ethernet link routed through the IP backbone of the customer to/from the OMC-R site.

In case MediaGateway supports SPC function, no need of router A at MGw site.




4. 9153 OMC-R – OPERATION SITE

4.1 Site requirements

The site where the OMC-R is installed should meet the following requirements: - Temperature 10 °C < T < 35 °C - Humidity 20 % to 80 % non-condensing - Maximum dust density in the air 100 micron/m3 - Light 400 Lux at 1 m above ground level

4.2 Site example

This is an example of a new site installation for an OMC-R with three local terminals. The OMC-R server is in the server room with the administration console (system terminal) and the printer, and the terminals are in the exploitation room with appropriate printers.

300

cm

100

cm

200 cm

400 cm

OMC-RSystem terminal

Figure 11: Server room

Laser printer

400 cm

450 cm

250cm

Terminals

Figure 12: Exploitation room




5. TECHNICAL DATA OF THE 9153 OMC-R COMPONENTS

5.1 Generalities

These technical data refer only to current OMC-R configuration machines. Other existing configurations (e.g mainly based on UltraSparc II processors like E4500, E450, U10) are supported but are not described in this product description.

Note that the specified CPU speed and amount of RAM are the minimum requirements of each configuration. Higher figures of the CPU speed and amount of RAM are also possible. Details of the configurations supported by each release is provided in the document “9153 OMC-R SUN Hardware Evolutions” / reference 3DC 20006 0019 UZZZA.

5.2 UltraSparc III generation

5.2.1 Small OMC-R master server platform

Sun Fire™ V880 Server Two 900 MHz UltraSparc III processors

4 GB RAM

6 x 73 GB disk

Supply voltage 100 – 240 VAC, 47 – 63 Hz

Max. power consumption 1 500 VA per power supply

Environmental data

– Operating

– Non-operating

– Acoustic noise

Temperature: 5 °C to 35 °C

Humidity: 20 % to 80 % RH, non-condensing

Temperature: -20 °C to 60 °C


56 dBA (acc. ISO 9296, 23 °C)

Cabinet dimensions Height: 714 mm

Width: 480 mm

Depth: 836 mm

Weight max. 131.0 kg

Hardware MTBF 6 800 hours




5.2.2 Standard OMC-R master server platform

Sun Fire™ V880 Server Two 900 MHz UltraSparc III processors

4 GB RAM

6 x 73 GB disk

See Section 5.2.1

5.2.3 Large OMC-R master server platform

Sun Fire™ V880 Server Six 900 MHz UltraSparc III processors

12 GB RAM

12 x 73 GB disk

See Section 5.2.1


5.2.4 Extra Large OMC-R master server platform

Sun Fire™ V880 Server Eight 900 MHz UltraSparc III processors

16 GB RAM

12 x 73 GB disk

See Section 5.2.1


5.2.5 Extra Large OMC-R agent server platform

Sun Fire™ V880 Server Six 900 MHz UltraSparc III processors

12 GB RAM

12 x 73 GB disk

See Section 5.2.3




5.2.6 Small standard HMI server

Sun Fire™ 280R Server One 900 MHz UltraSparc III processors

1 GB RAM

73 GB disk


Max. power consumption 900 VA

Environmental data

– Operating

– Non-operating

– Acoustic noise





56 dBA (acc. ISO 9296, 23 °C)


Width: 438 mm

Depth: 692 mm

Weight max. 34.0 kg


5.2.7 Standard HMI server

Sun Fire™ 280R Server Two 900 MHz UltraSparc III processors

2 GB RAM

73 GB disk

See Section 5.2.6





5.2.8 User WorkStation (WS)

Sun Blade™ 100 Workstation One 500 MHz UltraSparc- processor

128 MB RAM

20 GB disk



Environmental data

– Operating

– Non-operating

– Acoustic noise





5.0 bels (acc. ISO 9296, 23 °C)


Width: 445 mm

Depth: 464 mm

Weight appr. 15.4 kg





Sun Blade™ 150 Workstation One 500 MHz UltraSparc III processor

128 MB RAM

40 GB disk



Environmental data

– Operating

– Non-operating

– Acoustic noise





5.0 bels (acc. ISO 9296, 23 °C)


Width: 457 mm

Depth: 446 mm






Sun Blade™ Ultra25 Workstation One 1.34 GHz UltraSparc IIIi processor

1 GB RAM

1 x 80 GB disk



Environmental data

– Operating

– Non-operating

– Acoustic noise





5.0 bels (acc. ISO 9296, 23 °C)


Width: 205 mm

Depth: 569 mm


Hardware MTBF 50000 hours




5.3 UltraSparc IV generation

5.3.1 Small OMC-R master server platform

Sun Fire™ V490 Server Two 1350 MHz (or 1800 MHz) UltraSparc IV processors

8 GB RAM

2 x 73 GB disk


Max. power consumption 2 078 VA

Environmental data

– Operating

– Non-operating

– Acoustic noise





40 dBA (acc. ISO 9296, 23 °C)


Width: 1446 mm

Depth: 610 mm

Weight max. 44 kg


5.3.2 Standard OMC-R master server platform

Sun Fire™ V490 Server Two 1350 MHz (or 1800 MHz) UltraSparc IV processors

8 GB RAM

2 x 73 GB disk

See Section 5.3.1




5.3.3 Large OMC-R master server platform

Sun Fire™ V490 Server Four 1350 MHz (or 1800 MHz) UltraSparc IV processors

16 GB RAM

2 x 73 GB internal disks + 6x73 GB External Disk Bay SE3510

See Section 5.3.1

Hardware MTBF V490 :13 100 hours

SE3510 (6x73 Gb) : 160 000 hours

5.3.4 X Large and XX Large OMC-R master server platform


16 GB RAM

2 x 73 GB internal disk + 12x73 GB External Disk Bay SE3510

See Section 5.3.1

Hardware MTBF V490 :13 100 hours

SE3510 (12x73 Gb) : 66 700 hours

5.3.5 X Large and XX Large OMC-R agent server platform

There are one Agent for the X-Large configuration and two for the XX-Large configuration


16 GB RAM

2 x 73 GB internal disk + 6x73 GB External Disk Bay SE3510

See Section 5.3.3




5.3.6 Standard HMI server

Sun Fire V440 Server Two 1280 MHz UltraSparc IIIi processors

4 GB RAM

4x73 GB disk



Environmental data

– Operating

– Non-operating

– Acoustic noise





Less than 6.7 B sound power when operating and idle


Width: 440 mm

Depth: 635 mm

Weight max. 37.0 kg





Netra 440 Server Two 1280 MHz UltraSparc IIIi processors

4 GB RAM

4x73 GB disk



Environmental data

– Operating

– Non-operating

– Acoustic noise





Less than 7.0 B sound power when operating and idle


Width: 440 mm

Depth: 495 mm

Weight max. 37.0 kg


5.3.7 Large HMI server

Sun Fire V440 Server Four 1280 MHz UltraSparc IIIi processors

8 GB RAM

4x73 GB disk

See Section 5.3.6





Netra 440 Server Four 1280 MHz UltraSparc IIIi processors

8 GB RAM

4x73 GB disk

See Section 5.3.6





6. ANNEX: BANDWIDTH REQUIREMENTS AT OMC-R INTERFACES

The following table shows the bandwidth requirements between the OMC-R host and its different interfaces: the HMI servers, the user terminals (either Unix terminal using X11 protocol or Citrix terminals), and 9159 NPO.

OMC host server

NPO server

NPO client

UNIX terminal

Citrix terminal

HMI server

1 Mbps

64 kbps (128 kbps is recommended )

64 kbps per user (128 kbps is recommended )

64 kbps 10 Mbps

HMI server NPO client Citrix

256 kbps 1Mbps per user

1 Mbps

UNIX terminal

1 Mbps




7. ABBREVIATIONS

ACO Alarm Call Out ALMAP Alcatel Management Platform Ater Sub-multiplexed TC – BSC Interface BSC Base Station Controller BSS Base Station System BTS Base Transceiver Station CM Configuration Management CPU Central Processing Unit DCN Data Communication Network ETSI European Telecommunications Standards Institute FTP File Transfer Protocol FM Fault Management Gb Telecommunication interface between BSS and SGSN GGSN Gateway GPRS Support Node GPRS General Packet Radio Service GSM Global System for Mobile communication IMT Initialization and Maintenance Terminal IP Internet Protocol LAN Local Area Network LASER Lucid network Availability Stability and Event Reporting tool MFS Multi-BSS Fast packet Server MSC Mobile Services Switching Center NMC Network Management Center NPO Network Performance Optimizer OMC-R Operation and Maintenance Center – Radio part O&M Operation and Maintenance PCM Pulse Code Modulation PLMN Public Land Mobile Network PM Performance Management PSDN Packet Switched Data Network QoS Quality of Service RNO Radio Network Optimization SPC Semi-Permanent Connection (Nailed-Up Connection) TC Transcoder TMN Telecommunication Management Network TRX Transceiver WAN Wide Area Network WS Workstation XT Xterminal, client user terminal

End of Document

Documents

Alcatel 9135 OMC-Radio.pdf