9153 OMC-R Product Description

9153 OMC-R Product Description

Alcatel-Lucent

File PD1353E9.DOC

Reference 3DC 21076 0005 TQZZA

Date 08/02/2008

Edition 09

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

Alcatel-Lucent

File PD1353E9.DOC

Reference 3DC 21076 0005 TQZZA

Date 08/02/2008

Edition 09

Page 2

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

CONTENTS

1. INTRODUCTION .................................................................................................. 6 1.1 1.2 2.1 Introduction to 9153 OMC-R Product................................................................. 6 9153 OMC-R embedded in the Network Management environment ............................ 8 Components of an 9153 OMC-R ....................................................................... 9 2.1.1 2.1.2 2.1.3 2.1.4 2.1.5 2.2 2.2.1 2.2.2 2.3 2.3.1 2.3.2 2.3.3 2.4 2.4.1 2.4.2 2.4.3 2.5 2.6 OMC-R Configurations........................................................................11 User Terminals ................................................................................12 HMI Servers ....................................................................................12 OMC-R Components Hardware Generations..............................................13 Software .......................................................................................13 BSS Capacity per OMC-R Configuration ...................................................15 User Sessions per OMC-R Configuration...................................................16 OMC-R Topologies ............................................................................17 OMC-R – BSC interconnection...............................................................19 OMC-R –MFS (GPRS) interconnection ......................................................20 Alarm Call Out ................................................................................20 Automatic O&M actions .....................................................................21 Centralized management via Network Management System (NMS)..................22

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

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

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

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

Network Management Interface .....................................................................23 BSS Performance Management .......................................................................24 2.6.1 2.6.2 9153 OMC-R Performance Management ..................................................24 9159 Network Performance Optimizer (NPO)............................................24

3. ALCATEL-LUCENT UNIVERSAL ROUTING ....................................................................25 3.1 3.2 3.3 3.4 Introduction .............................................................................................25 Routing and Trunking of O&M Links between BSC and OMC-R through MSC .................26 Routing and Trunking of O&M Links between BSC and OMC-R through NGN .................27 Alcatel-Lucent Universal Routing router configurations.........................................28 3.4.1 3.4.2 4.1 Case of networks with MSC .................................................................28 Case of networks with NGN.................................................................28

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

Alcatel-Lucent

File PD1353E9.DOC

Reference 3DC 21076 0005 TQZZA

Date 08/02/2008

Edition 09

Page 3

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

4.2 5.1 5.2

Site example ............................................................................................30 Generalities .............................................................................................31 UltraSparc III generation ..............................................................................31 5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 5.2.6 5.2.7 5.2.8 Small OMC-R master server platform .....................................................31 Standard OMC-R master server platform .................................................32 Large OMC-R master server platform .....................................................32 Extra Large OMC-R master server platform ..............................................32 Extra Large OMC-R agent server platform ...............................................32 Small standard HMI server ..................................................................33 Standard HMI server..........................................................................33 User WorkStation (WS) ......................................................................34 Small OMC-R master server platform .....................................................37 Standard OMC-R master server platform .................................................37 Large OMC-R master server platform .....................................................38 X Large and XX Large OMC-R master server platform ..................................38 X Large and XX Large OMC-R agent server platform ...................................38 Standard HMI server..........................................................................39 Large HMI server..............................................................................40

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

5.3

UltraSparc IV generation ..............................................................................37 5.3.1 5.3.2 5.3.3 5.3.4 5.3.5 5.3.6 5.3.7

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

Alcatel-Lucent

File PD1353E9.DOC

Reference 3DC 21076 0005 TQZZA

Date 08/02/2008

Edition 09

Page 4

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

................. 9 Figure 5: 9153 OMC-R Distributed Configuration Overview.......................... ...............................23 Figure 9: PM front-office and back-office approach ............................30 Alcatel-Lucent File PD1353E9.... use and communication of its contents not permitted without written authorization............................................................................. 8 Figure 3: Alcatel-Lucent BSS Network Management Environment ..................26 Figure 11: Server room............................................................................................. Passing on and copying of this document...25 links between BSCs and OMC-R .........DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 5 All rights reserved.........................................................30 Figure 12: Exploitation room ...................................................17 Figure 7: Alarm call out options........................................... 8 Figure 4: 9153 OMC-R Single Configuration Overview ........................................... 6 Figure 2: OMC-R positioning in TMN ...............................................................21 Figure 8: 9153 interfaces synoptic .......................................................24 Figure 10: MSC case for Routing and Trunking of X.................................................................................................................................................................................................................10 Figure 6: Single Agent OMC-R Topology ....9153 OMC-R Product Description List of figures Figure 1: 9153 OMC-R Functional Management Domain ............................

i.e.e. i. Passing on and copying of this document. 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.25 TCP/IP SGSN O&M GPRS O&M O&M Abis MFS Ater Ater O&M BTS O&M BTS BSC TC A Itf .GPRS Multi-BSS Fast packet Server (MFS). the BSS part of GPRS equipment. TCs and transmission systems .The whole set of BSSs. BTSs.1 Introduction to 9153 OMC-R Product In the GSM world. In compliance with the GSM specifications.9153 OMC-R Product Description 1. Functional Domain 9153 OMC-R 9153 OMC-R GPRS Physical Interfaces O&M Functional Interfaces Gb Itf. BSCs. X. . use and communication of its contents not permitted without written authorization. the 9153 Operation & Maintenance Center for Radio Part (OMC-R) is concerned with Element Management and Sub-Network Management of BSS network subsystem: . INTRODUCTION 1.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 6 All rights reserved. MSC Figure 1: 9153 OMC-R Functional Management Domain Alcatel-Lucent File PD1353E9. the OMC or Operation and Maintenance Center is defined as a system responsible for operation and maintenance of a given set of network equipments. Figure 1 shows an overview of OMC-R with respect to managed elements physical and functional interconnection.

(2) BSS performance indicators for dedicated supervision of QoS information and fast detection of telecom service degradation. use and communication of its contents not permitted without written authorization. These domains are: . e. software management (BSS software release migration). 9153 OMC-R also provides functions for extensive and time efficient logical configuration management with minimum telecom impact. presentation and archiving of measurement results. i. It provides retrieval. as well as BSS date and time management. Passing on and copying of this document. logical configuration management (BSS radio parameter adjustment for optimized configuration of radio related resources). forwarding.g. retrieval of proprietary measurement results for display. status monitoring of equipment and resources.3010. These indicators are also displayed and analyzed thanks to graphic or tabular reports.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 7 All rights reserved. Performance indicators can be compared with user defined thresholds allowing the generation of QoS alarms (handled by the standard OMC-R alarm handling function). processing. analysis and export (in binary or ASCII format). Alcatel-Lucent File PD1353E9. equipment handling and test management.e. In addition. reduction or reconfiguration).Fault Management (FM) BSS Fault Management offers network supervision through alarm handling. massive adjustment of parameters for an optimized radio configuration or network wide activation of a new frequency plan.Configuration Management (CM) BSS Configuration Management provides hardware management (BSS network extension. 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.9153 OMC-R Product Description 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.Performance Management (PM) BSS Performance Management handles administration. . At OMC-R level two types of measurement results are handled: (1) BSS observation counters. . . the Alcatel-Lucent BSS supports autonomous recovery of GSM resources through reconfiguration of BTS in case of TRX failures.

use and communication of its contents not permitted without written authorization.9153 OMC-R Product Description A single OMC-R configuration can supervise multiple BSSs (the BSCs with all related BTSs). it takes the functional role of an element manager of Alcatel-Lucent BSS network elements: Business Management Service Management NMC Network Management Element Management OMC-R BTS BSC MFS Network Element Figure 2: OMC-R positioning in TMN In order to support customer external applications such as BSS radio network planning and optimization. Passing on and copying of this document. 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.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 8 All rights reserved. 9135 or 9130 MFS Network Elements 9120 or 9130 9153 Alcatel or other OMC-R Element Manager NMC Network Manager BSC Network Elements Initial Configuration PM Data Configuration Data Alarms. 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. State Changes and User Logs 9155 9159 Cell Design Data Radio Network Planning Network Performance Optimizer Figure 3: Alcatel-Lucent BSS Network Management Environment Alcatel-Lucent File PD1353E9. BSSs connected to different MSCs depending on the chosen configuration and multiple GPRS MFSs. interfaces towards ‘Alcatel-Lucent Network Engineering Tools' are supported.2 9153 OMC-R embedded in the Network Management environment 9153 OMC-R follows the Hierarchical Network Management approach defined in TMN standards. Moreover.

9153 OMC-R Product Description 2. The main hardware configurations supported by 9153 are: . . By means of this configuration flexibility.Single server configuration with front-end workstations and X-terminals: NMC LAN / WAN DCN OMC-R Domain local lan local or remote lan HMI Server(s) User Terminals Peri Devices Printers User Terminals Peri Devices Printers Q3 Mediation OMC-R Master Server Database LAN/ WAN DCN X25 Connection IP Connection 9120 BSC 9130 BSC Evolution 9130 MFS Evolution 9135 MFS Figure 4: 9153 OMC-R Single Configuration Overview Alcatel-Lucent File PD1353E9. use and communication of its contents not permitted without written authorization. Passing on and copying of this document. adding new machines where necessary.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. OVERVIEW OF 9153 OMC-R CONFIGURATIONS 2.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 9 All rights reserved. the management system can evolve and be adapted to new dimensioning requirements.

Alarm Database and Surveillance module. and Xterminals: NMC LAN / WAN DCN OMC-R Domain local lan OMC-R Agent Server Database OMC-R Agent Server Database LAN/ WAN DCN local or remote lan HMI Server(s) User Terminals Peri Devices Printers User Terminals Peri Devices Printers Q3 Mediation OMC-R Master Server Database X25 Connection IP Connection X25 Connection IP Connection 9120 BSC 9135 MFS 9130 MFS Evolution 9120 BSC 9135 MFS 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 . . Passing on and copying of this document. this server hosts system administration functions.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 10 All rights reserved. In particular.Agent Server: Unix Server. In the Single server configuration only.Distributed configuration with three dedicated servers and front-end workstations.9153 OMC-R Product Description . this host server mediates also data from the Network Elements.Master Server: Unix Server. only present in the distributed configuration. . Q3 mediation and the Radio Network Configuration database. and stores these data in the BSS database. use and communication of its contents not permitted without written authorization. Alcatel-Lucent File PD1353E9. whose main purpose is to run the OMC-R management application. whose main purpose is to host the mediation of group of Network Elements in order to increase the capacity of the OMC-R.

use and communication of its contents not permitted without written authorization. Two generations of these servers are used: UltraSparc III generation since B7 release Alcatel-Lucent File PD1353E9.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. which might be limited by weak transmission capability.1: .DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 11 All rights reserved. Passing on and copying of this document. .Extra Extra Large OMC-R configuration (XX-Large) (XXLRG) The first three configurations have only one Master Server and no Agent Server.). X.Extra Large OMC-R configuration (X-Large) (SML) (STD) (LRG) (XLRG) . The XX-Large configuration is composed of one Master and two Agent servers (UltraSparc IV generation only). Besides the OMC-R application software. The relevant BSS capacity for each OMC-R configuration is listed in the table of Section 2. OSI stack.Large OMC-R configuration with two variants . 2. .Laser or line printers (optionally) The requirements in term of bandwidth on the OMC-R host server interfaces are described in ANNEX.25 protocol.1. a HMI server is required to ensure the terminal performances. The X-large configuration (distributed configuration) is composed of one Master Server and one or two Agent Servers (depending on server generations).9153 OMC-R Product Description .2. In case of remote user terminals.1 OMC-R Configurations Depending on the size of the BSS network that has to be supervised. Object Store database. etc.g. Sun Solaris OS.Standard OMC-R configuration . five types of OMC-R configurations have been described as generic. .Small OMC-R configuration . the software part includes third-party software (e. OMC-R host and HMI Servers are built on Sun Microsystems™ servers.User Terminal: Graphical Workstations connected to the master Server or to the HMI Server.

Alcatel-Lucent File PD1353E9. 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. use and communication of its contents not permitted without written authorization. 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. Passing on and copying of this document.Disk failure (RAID technology. each of them providing a different capacity in terms of number of operator sessions depending on the OMC-R type they are connected to. PC under Microsoft™ Windows. e. . 100 % data redundancy. Workstations are client graphical terminals running on their own operating system. They offer excellent Reliability.Memory failure .Power supply and cooling module failure .g. Availability. and Serviceability (RAS) features. The Citrix Metaframe™ client software is installed on the terminals and is communicating with the Citrix Metaframe™ server software.1. autonomous restoration mechanisms are supported in case of following failures: . measurement post processing) without impacting server resources.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 12 All rights reserved.CPU failure .9153 OMC-R Product Description - 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. As an example. The OMC-R supports the two following categories of terminal: • Terminals running SUN™ Solaris and supporting the X11 protocol • Terminals running Citrix Metaframe™ clients.g.2 User Terminals Workstations (WS) are used as user terminals.3 HMI Servers There are several kinds of HMI servers. 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 large capacity HMI servers are usually located at the OMC-R site when the small capacity servers are often remotely located. hot plug disks). All HMI servers can be located either at the OMC-R site or remotely depending on the chosen operating topology.1. 2. hosted on the OMC-R HMI server.

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. OMC-R server Tiny Small Sun Fire V880 Sun Fire V490 Standard Sun Fire V880 Sun Fire V490 Large Sun Fire V880 Sun Fire V490 with external disk bay SE3510 X-Large Sun Fire V880 (x2) Sun Fire V490 with external disk bay SE3510 (x2) XX-Large Sun Fire V490 with external disk bay SE3510 (x3) HMI server Sun Blade 150. Passing on and copying of this document. The architecture of ALMAP is object-oriented and complies with the major TMN and system management standards issued by ITU-T.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 13 All rights reserved.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. Alcatel-Lucent File PD1353E9. . use and communication of its contents not permitted without written authorization. The ALMAP architecture is designed to support integration. when NPO option is used on OMC-R.1. the number of user sessions supported by HMI servers is reduced. ETSI and ISO and with recommendations from industry forums such as NMF. 2. scalability and flexibility. or Sun Blade series 100/150.9153 OMC-R Product Description From release B10. Ultra25 Sun Fire 280R Sun Fire V440 or Netra 440 Sun Fire 280R Sun Fire V440 or Netra 440 Sun Fire V440 or Netra 440 - The workstations can be either Sun U5/U10. ALMAP offers a powerful development environment (COMET) and a set of reusable components that fulfill telecommunication operator requirements. or Ultra25 or any terminal when a Citrix solution is used (Universal terminal concept).1. 2.5 Software The software part of the 9153 OMC-R is based on the Alcatel Management Platform (ALMAP 3).

transmission. switching or mobile networks. from 2.Graphical window management: X11 and Motif. .DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 14 All rights reserved.25. The open architecture permits to reuse or share these components across the Alcatel Management products for different telecommunication areas. security (management of user accounts with profiles definition allowing to associate functions and network elements to a user) or system management functions.Help and documentation on-line: HTML Server and/or Navigator. ALMAP has been regularly updated according to the different version of Solaris.9153 OMC-R Product Description ALMAP provides a comprehensive family of generic component reusable for the development of Network Management products. Passing on and copying of this document. only the SUN Solaris compatible version of ALMAP is used. ALMAP is multi-OS platform. use and communication of its contents not permitted without written authorization. In the BSS case.Database for BSS Performance Management: Oracle Alcatel-Lucent File PD1353E9. such as alarm surveillance (compliant with X733 standards). . Windows CDE. . and also minimizing Alcatel Element and Sub-Network Managers cost of ownership. OSI and CMIP . other third-party softwares are used on OMC-R: .Communication stacks: Solstice X. These generic components cover the functions common to all Network Management products.OMC-R database: Object Store distributed database (Progress Software). In addition to ALMAP. . thus providing the operator with a homogeneous management system.6 up to Solaris 10. including access.

The following NE types must be considered: .DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 15 All rights reserved.MFS: 1 9120 BSC or 1 9130 BSC Evolution = 1 BSC equivalent 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. Higher number of network elements must be served by further OMC-R configurations (wherever located).2 9153 OMC-R Dimensioning The following tables give for each type of OMC-R configuration the maximum number of supervised equipments. .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). number of BSC equivalents 10 10 20 35 45 100 Max. the maximum number of BSS network elements that can be managed by each OMC-R configuration. number of of Cells 250 250 500 1 200 1 500 4 000 TRXs 1 250 1 250 2 500 6 000 7 500 20 000 • 1 'BSC equivalent' is defined as standardized load of the NE in terms of O&M capacity of the OMC-R. by type of equipment (BSC equivalents1. TRX) according to the release traffic model. Remark: Each configuration is the upper limit for a given OMC-R configuration. use and communication of its contents not permitted without written authorization. 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 Small Small with NPO embedded Standard Large-1 Large-2 X-Large Number of OMC-R servers 1 1 1 1 1 2 Max.2. Passing on and copying of this document. i.9153 OMC-R Product Description 2.e. 2. maximum number of either BSCs or cells or TRXs. number Max. Alcatel-Lucent File PD1353E9.BSC: . cells.

9153 OMC-R Product Description OMC-R Capacity per configuration with UltraSparc IV generation OMC-R Configuration Small Small with NPO embedded Standard Large-1 Large-2 X-Large XX-Large Number of OMC-R servers 1 1 1 1 1 2 3 Max. number of Cells 250 250 500 1 200 1 800 4 000 6 000 Max. use and communication of its contents not permitted without written authorization. But number of sessions can vary according to the BSS Release. connected to a single local area network). number of BSC equivalents 10 10 20 35 50 100 120 Max.g. number of TRXs 1 250 1 250 2 500 6 000 9 000 20 000 30 000 2. .2. OMC-R user terminals concentrated in a single location or distributed among several different places). The maximum number of user terminals is not limited in principle. All HMI servers of all generations can be used connected to an OMC-R whatever the generation of the server.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. Passing on and copying of this document. 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). the OMC-R master can directly serve a few numbers of user terminals that are located in a single site (i. Depending of the actual number of managed Network Element managed by the OMC-R.e. This new user activity control allows on principle an “unlimited” number of user logins and optimizes available OMC-R resources usage. Alcatel-Lucent File PD1353E9.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 16 All rights reserved. In some cases. 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). OMC-R controls globally the number of simultaneously opened views and windows. From B10 release. the configuration (number and type of HMI servers) can be different and only depends on the required number of user sessions.

OMC-R Local Site Master Server R IP WAN WAN PSDN WAN BSS BSS R Remote Site Small HMI Server R Small HMI Server Remote Site 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.RJ45 ports with 10/100 Mbps base Tx auto detection flow rate. Passing on and copying of this document.one OMC-R master server and several terminals at the local OMC-R site. to the HMI server.two remote sites with small HMI servers and remote terminals. 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. .3.plug and play installation facilities. Figure 6 represents a typical one with . Alcatel-Lucent File PD1353E9.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 17 All rights reserved. use and communication of its contents not permitted without written authorization. a "true" IP Ethernet switch should be used (not a common hub unit) with: .1 OMC-R Topologies The OMC-R architecture offers several topologies that allow a wide flexibility to operate the network.IP multicast switching full duplex capacities . where used. 2. To ensure proper operation and performance in communications between units on the LAN.9153 OMC-R Product Description Due to available physical resources on HMI servers (processing power and memory).3 BSS O&M Configuration 2.

a routing device (R) is needed in order to establish the necessary connection towards HMI clients or other OMC-R agents. Alcatel-Lucent File PD1353E9.9153 OMC-R Product Description In case of remote installations. Passing on and copying of this document. use and communication of its contents not permitted without written authorization. .DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 18 All rights reserved.

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. Passing on and copying of this document.25 PSDN. there are no limitations in terms of number of BSC Evolution managed locally.9153 OMC-R Product Description 2. In this case.3. the BSC can be connected to the LAN where the OMC-R is also connected.25 connection to the X. use and communication of its contents not permitted without written authorization. For security reasons all physical X. 9130 BSC Evo LAN BSC G2 PSDN BSC G2 OMC-R 1 9120 BSC Dedicated X25 links OMC-R (3) Via A Interface – MSC Connection (AlcatelLucent Universal Routing) A itf 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). (2) Co-located site Without use of additional router. In this case the interconnection is realized through dedicated serial lines.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 19 All rights reserved. (1) Via PSDN The OMC-R – BSC can be connected remotely through Packet Switched Data Network.25 connections can be configured redundantly. except the maximum number of cells managed by OMC-R. the OMC-R can be co-located with maximum one or two 9120 BSCs depending on the use of redundancy.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). In case of 9130 BSC Evolution. In such case. 9120 BSC Transcoder MSC Router 9130 BSC Evo OMC-R Alcatel-Lucent File PD1353E9. .

whatever the generation . Deployment of NGN in the field. More detailed information about various routing configurations can be found in Chapter 3.1 Alarm Call Out The Alarm Call Out (ACO) feature enhances the alarm handling service. 2. 9135 MFS or 9130 MFS Evolution.9153 OMC-R Product Description Thanks to the availability on the market of 'intelligent' multi-protocol routers. replacing the MSCs. . event date and time. They are detailed here below: 2. This will be also detailed in chapter 3.3 OMC-R –MFS (GPRS) interconnection This interface requires an IP connection in order to support Q3 and FTP protocols.is of 256 Kbits/s.according to a defined schedule (range of days in the week and range of hours for each day of the week) .DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 20 All rights reserved. the MFS supports two Ethernet ports to connect directly the Local Maintenance Terminal and the OMC-R. Only one ACO filter can be activated per OMC-R. use and communication of its contents not permitted without written authorization. 2. It allows supervision of the network with a reduced number of operators. This filter can be activated: . ACO can be activated from any OMC-R terminal.4 Centralized Management Several possibilities exist to supervise several OMC-Rs from one central location.. 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 Alcatel-Lucent ‘Universal Routing' solution is recommended as the standard solution. for example at nighttime or during the weekend. Whatever the generation. Passing on and copying of this document. The minimum bandwidth required for MFS .on all the BSC or on a subset The alarms complying with the filter are: .3.4. alarm type. probable cause. The filter is based on criteria as alarm severity. requires a new way for routing the O&M links between OMC-R and NEs (BSC and MFS). ACO applies a defined filter on the alarms received at OMC-R. For the 9130 MFS Evolution.either sent to a printer Alcatel-Lucent File PD1353E9. either local or remote.

DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 21 All rights reserved.or posted to predefined e-mail addresses (up to 2 different addresses). without having to do any remote connection on the other OMC-Rs. The same 160 characters per alarm are printed out when printer is chosen as ACO output. for each alarm matching the ACO filter. a mail is sent. When mail is chosen as ACO output. Passing on and copying of this document. and routes have been opened. ACO filter and service definitions are available through a WEB browser interface. Printer can be either located on the OMC-R LAN or connected to a remote HMI server on a distant site.4. on condition that IP addresses of other OMC-R have been set.9153 OMC-R Product Description . . use and communication of its contents not permitted without written authorization. Consequently. LAN/WAN Terminal E-mail Remote Alarm Printer Internet OMC-R 5 Figure 7: Alarm call out options 2. an operator can define the ACO filter and services for several OMC-Rs from his terminal. . . .2 Automatic O&M actions Automatic O&M actions can be triggered upon immediate reception of an alarm. Alcatel-Lucent File PD1353E9. Local Alarm Printer OMC-R 1 Local or Remote HMI Server . Consequently an alarm sub-list can be created in AS module in order to display the alarms verifying the ACO filter. The filtering criteria of ACO and of Alarm Surveillance (AS) module are the same. AS views are available on any terminals connected to local or remote HMI servers. The definition of alarm in the mail is restricted to 160 characters.or both sent to printer and posted to predefined e-mail addresses.

Alcatel-Lucent File PD1353E9. .4. Performing a well-defined action upon reception of a certain alarm (such as restarting the board concerned by the received alarm). use and communication of its contents not permitted without written authorization. main benefit from the feature is that it allows saving OPEX cost. it is possible to connect one or several OMC-R to a NMS.9153 OMC-R Product Description These automatic actions are performed through command mode scripts defined by the operator specifically for each action. Passing on and copying of this document. centralizing the network supervision. Typical examples are: sending a SMS/email to on-duty people upon reception of a pre-defined set of alarms. allowing central operators to concentrate only on important alarms. Filtering capabilities are proposed on this interface in order to reduce the flow of alarms when several OMC-R are used. In both cases.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 22 All rights reserved. This is equivalent to the previously described Alarm Call Out feature but with the benefit of a realtime reaction. 2. This allows OMC-R operator concentrating on the most important alarms.3 Centralized management via Network Management System (NMS) Thanks to the real-time Q3 interface for Fault Management.

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. This leads to support different 9153 OMC-R Interfaces: . The consequence is the richness of opened interfaces allowing external applications (maintenance.The 9153 OMC-R Configuration Import/Export (ACIE) interface . Passing on and copying of this document. use and communication of its contents not permitted without written authorization.The Alarm/Event log ASCII export for the Alarm post-processing interface The Remote Inventory Export interface (ARIE) Export equipment Configuration Via FTP Import/Export Radio Configuration Via FTP Export Hardware Inventory Via FTP FM + Network discovery via Q3 PM interface (ASCII or Binary) via FTP Alarms/ Events/logs interface ASCII via FTP Q3 ACIE EML ACIE RNL ARIE AS / ELM Export pool 9153 OMC-R mib mib BSS BSS 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). engineering. Alcatel-Lucent File PD1353E9. customer care. .The NMS/9153 OMC-R Q3 interface for network surveillance applications . quality) to access easily to the maximum data of the OMC-R.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 23 All rights reserved.The ASCII and binary interfaces for the Performance Measurement export interface .9153 OMC-R Product Description 2.5 Network Management Interface The 9153 OMC-R is fully integrated in the Telecommunication Management Network (TMN).

For more details on NPO. The optional 9159 Network Performance Optimizer (NPO) product achieves this activity. Passing on and copying of this document. This front office component is built upon industry standard database: Oracle. .6. processing and on-line display of BSS observation counters by means of graphs and tables (Counters and Indicators Browser). months. This component also warns the operator in case of QoS threshold crossing by generating alarms handled just like any other BSS alarm. This component allows collection.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. 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. This data post-processing function generates Quality of Service and Network Performance Analysis reports with up to two years history. years) and allowing forecast and trends analysis for network optimization purpose. 9153 OMC-R Counters display and Quality of Service alerters (X733 alarm format) OMC_PM front office Database binary files NPO Back office BSS MFS Figure 9: PM front-office and back-office approach 2. Alcatel-Lucent File PD1353E9. In addition. refer to Alcatel-Lucent 9159 Network Performance Optimizer Product description (reference 3DC 21146 0062 TQZZA).DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 24 All rights reserved.6 BSS Performance Management 2. NPO embeds the full set of radio optimization functions formerly provided by RNO tool. widely recognized as reference in the domain of radio optimization.6.9153 OMC-R Product Description 2. use and communication of its contents not permitted without written authorization.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.

25 signaling links. This solution is made possible through the use of intelligent multi-protocol routers located at OMC-R site and MSC sites. Finally.Cost of establishing a private PSDN. it can be used to build the OMC-R IP network upon instead of sharing the PCM resources. if a private DCN – e. ALCATEL-LUCENT UNIVERSAL ROUTING 3. Hence.Cost of subscription. Besides. all BSC O&M channels (64 kbit/s each) are reserved on PCM trunk between each BSC and related MSC. an OMC-R must be connected to each of the supervised BSCs. . 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. Alcatel-Lucent File PD1353E9. especially if this private network has to be built only for this OMC-R – BSC interconnection purpose. Passing on and copying of this document. which is very important from an operational point of view. The principle of this solution is to use the transmission capabilities of the PLMN itself for physical base of X. a corporate WAN – is available. e. the PCM links between BSCs and MSCs and between MSCs themselves. To be applicable. including cost of dedicated leased lines. .9153 OMC-R Product Description 3. such a PSDN must be available. The disadvantage of this solution may be the cost: . either public or private.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 25 All rights reserved.g. the new solution is very flexible for re-configuration of the network and insensitive to any loss of PCM resources. if a public PSDN is used. use and communication of its contents not permitted without written authorization. with access to it at OMC-R site and at each BSC site. for nonoperating concentration. Alcatel-Lucent Universal Routing provides an alternative solution. i. This optional solution is applicable for both the BSS Universal Routing capability and the interconnection of OMC-Rs themselves.1 Introduction To be operational. A solution is to use a PSDN (Packet Switched Data Network). With this solution. This connection must be established through a Data Communication Network (DCN). Such a network uses transmission links external to those used for the PLMN itself.e.g.

Passing on and copying of this document. Figure below illustrates this principle in a simple case.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.Standard G. otherwise. This is done using: . TC) MFS Figure 10: MSC case for Routing and Trunking of X. The following chapter gives more details about the interconnection of the OMC-R to the co-located router. . .Semi-Permanent Connections (SPC) or 'Nailed-up' Connections within the MSC. MSC Transmission Network E1 links (Local) O&M over ATer E1 links (Local) BSC G2 Router Type1 IP flows TC X25 serial Router Type2 BSC Evolution MSC site OMC-R Site IP flows X25 flows (common with MFS.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 26 All rights reserved.25 links between BSCs and OMC-R • 2 SPCs is thus a prerequisite of the solution. Alcatel-Lucent File PD1353E9. a dedicated PCM trunk must be established additionally to the links already used for telecom traffic purposes). . (if OMC-R and MSC are co-located.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). use and communication of its contents not permitted without written authorization.703/704 PCM link between the MSC and the multi-protocol network router colocated to the OMC-R. a short piece of PCM wire can be used.9153 OMC-R Product Description 3. to route the different O&M links to a single PCM trunk towards the OMC-R 2. routing through internal PCM links is performed.

But some of the Media Gateways currently available on the market don’t support SPC function.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. X25 O&M extraction Router A at TC (serial) X25 over IP O&M over ATer Call-Server MGw IP Network IP Router STM-1 link ADM E1 links (Local) E1 links (Local) TC 9120 BSC Router B X25 serial OMC-R Site IP flows X25 flows MGw site (common with BSC. the IP O&M flow will be routed via the IP network up to the OMC-R site. Remark: In the particular case of the BSC Evolution. In case of network made partially or totally of 9120 BSC. when the BSCs are not collocated with the MSC site and O&M flows are routed through Ater interface.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 27 All rights reserved. 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. 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. In this case. if the customer has an IP network available. it is required to extract the O&M timeslots from the Ater links at TC side. .2). MFS. 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. 2.9153 OMC-R Product Description This scheme is valid for both 9120 BSC and 9130 BSC Evolution. TC) MFS 9130 BSC Evolution Figure 12: NGN Case for Routing and Trunking of O&M links between BSCs sites and OMC-R Alcatel-Lucent File PD1353E9. When Media Gateway communicates with other sites through an IP network. use and communication of its contents not permitted without written authorization. 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. 3. Passing on and copying of this document.

DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 28 All rights reserved.1 Case of networks with MSC . Alcatel-Lucent File PD1353E9.Router Type 1 is the router used systematically at OMC-R.9153 OMC-R Product Description 3. only the principles of the router configurations are provided. In the current Product Description document. use and communication of its contents not permitted without written authorization.25 connection: 2 × 64 kbps physical links.4 Alcatel-Lucent Universal Routing router configurations Remark: The router configurations are detailed in specific engineering rules documents. Passing on and copying of this document.Router Type 2 is located systematically at MFS site (close to the MSC). optionally can also be used to compress BSC O&M flow in order to reduce the bandwidth used in inter-MSC links. 3.25 link availability can be chosen: - Simple X.4. 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). 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 . they come from the same family of equipment but differ by the role they play and thus the type of modules they include.25 connection: 1 × 64 kbps physical link between each BSC and OMC-R. .2 Case of networks with NGN 2 routers are also needed in case of NGN. 3. Several router configurations have been identified from which the different network configurations can be built. Secured X. They are called ‘router types’. • 3 Two options regarding X.4. 1 active and 1 standby link.

This is a router Type1. . Passing on and copying of this document. use and communication of its contents not permitted without written authorization.9153 OMC-R Product Description The router B located at OMC-R site is fully similar with the one used for the MSC case. In case MediaGateway supports 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.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 29 All rights reserved. In case the Media Gateway does not support SPC function. no need of router A at MGw site. 1 Ethernet interface to connect to the IP network: all E1 TS are groomed/ungroomed to/from Ethernet link routed through the IP backbone of the customer to/from the OMC-R site. The MT120 boards can be located into several TCs. Alcatel-Lucent File PD1353E9.

Light 10 °C < T < 35 °C 20 % to 80 % non-condensing 100 micron/m3 400 Lux at 1 m above ground level 4.Maximum dust density in the air . Passing on and copying of this document. and the terminals are in the exploitation room with appropriate printers.Humidity . use and communication of its contents not permitted without written authorization.1 Site requirements The site where the OMC-R is installed should meet the following requirements: .9153 OMC-R Product Description 4. 9153 OMC-R – OPERATION SITE 4.2 Site example This is an example of a new site installation for an OMC-R with three local terminals. 400 cm 200 cm 100 cm System terminal OMC-R 300 cm Figure 11: Server room 450 cm 400 cm Terminals 250 cm Laser printer Figure 12: Exploitation room Alcatel-Lucent File PD1353E9.Temperature . The OMC-R server is in the server room with the administration console (system terminal) and the printer.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 30 All rights reserved. .

131. Higher figures of the CPU speed and amount of RAM are also possible. .g mainly based on UltraSparc II processors like E4500. non-condensing – Non-operating Temperature: -20 °C to 60 °C Humidity: 5 % to 93 % RH. Details of the configurations supported by each release is provided in the document “9153 OMC-R SUN Hardware Evolutions” / reference 3DC 20006 0019 UZZZA.2 UltraSparc III generation 5. non-condensing – Acoustic noise 56 dBA (acc. TECHNICAL DATA OF THE 9153 OMC-R COMPONENTS 5.9153 OMC-R Product Description 5. 47 – 63 Hz 1 500 VA per power supply Temperature: 5 °C to 35 °C Humidity: 20 % to 80 % RH. 23 °C) Height: Width: Depth: 714 mm 480 mm 836 mm Cabinet dimensions Weight Hardware MTBF max. Passing on and copying of this document. power consumption Environmental data – Operating 100 – 240 VAC.2. E450. 5.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 31 All rights reserved.0 kg 6 800 hours Alcatel-Lucent File PD1353E9.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 Max.1 Generalities These technical data refer only to current OMC-R configuration machines. U10) are supported but are not described in this product description. ISO 9296. Other existing configurations (e. Note that the specified CPU speed and amount of RAM are the minimum requirements of each configuration. use and communication of its contents not permitted without written authorization.

9153 OMC-R Product Description 5.2.2.1 5. use and communication of its contents not permitted without written authorization.2.1 Hardware MTBF 5.5 Extra Large OMC-R agent server platform 4 600 hours Sun Fire™ V880 Server Six 900 MHz UltraSparc III processors 12 GB RAM 12 x 73 GB disk See Section 5.4 Extra Large OMC-R master server platform 4 900 hours Sun Fire™ V880 Server Eight 900 MHz UltraSparc III processors 16 GB RAM 12 x 73 GB disk See Section 5. Passing on and copying of this document.2.2.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 32 All rights reserved.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.2.2.3 Alcatel-Lucent File PD1353E9. .1 Hardware MTBF 5.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.

non-condensing – Acoustic noise 56 dBA (acc. 34. 47 – 63 Hz 900 VA Temperature: 5 °C to 40 °C Humidity: 20 % to 80 % RH. ISO 9296. .6 Small standard HMI server Sun Fire™ 280R Server One 900 MHz UltraSparc III processors 1 GB RAM 73 GB disk Supply voltage Max.6 Hardware MTBF 11 800 hours Alcatel-Lucent File PD1353E9.9153 OMC-R Product Description 5. use and communication of its contents not permitted without written authorization.7 Standard HMI server Sun Fire™ 280R Server Two 900 MHz UltraSparc III processors 2 GB RAM 73 GB disk See Section 5. 23 °C) Height: Width: Depth: 176 mm 438 mm 692 mm Cabinet dimensions Weight Hardware MTBF max.2.0 kg 12 400 hours 5. Passing on and copying of this document.2.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 33 All rights reserved. power consumption Environmental data – Operating 100 – 240 VAC. non-condensing – Non-operating Temperature: -20 °C to 60 °C Humidity: 5 % to 93 % RH.2.

power consumption Environmental data – Operating 100 – 240 VAC. non-condensing – Non-operating Temperature: -40 °C to 65 °C Humidity: 5 % to 93 % RH. use and communication of its contents not permitted without written authorization. . 15. Passing on and copying of this document. ISO 9296.4 kg 33 000 hours Alcatel-Lucent File PD1353E9.8 User WorkStation (WS) Sun Blade™ 100 Workstation One 500 MHz UltraSparc. non-condensing – Acoustic noise 5. 47 – 63 Hz 300 VA Temperature: 5 °C to 35 °C Humidity: 10 % to 90 % RH. 23 °C) Height: Width: Depth: 118 mm 445 mm 464 mm Cabinet dimensions Weight Hardware MTBF appr.0 bels (acc.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 34 All rights reserved.9153 OMC-R Product Description 5.processor 128 MB RAM 20 GB disk Supply voltage Max.2.

47 – 63 Hz 300 VA Temperature: 5 °C to 35 °C Humidity: 10 % to 90 % RH. power consumption Environmental data – Operating 100 – 240 VAC. non-condensing – Acoustic noise 5.0 bels (acc. . 23 °C) Height: Width: Depth: 118 mm 457 mm 446 mm Cabinet dimensions Weight Hardware MTBF appr.9153 OMC-R Product Description Sun Blade™ 150 Workstation One 500 MHz UltraSparc III processor 128 MB RAM 40 GB disk Supply voltage Max. 12. non-condensing – Non-operating Temperature: -40 °C to 65 °C Humidity: 5 % to 93 % RH. use and communication of its contents not permitted without written authorization. Passing on and copying of this document.2 kg 33 000 hours Alcatel-Lucent File PD1353E9. ISO 9296.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 35 All rights reserved.

0 bels (acc. 26. power consumption Environmental data – Operating 100 – 240 VAC. Passing on and copying of this document. non-condensing – Acoustic noise 5.34 GHz UltraSparc IIIi processor 1 GB RAM 1 x 80 GB disk Supply voltage Max. 47 – 63 Hz 1000 VA Temperature: 2 °C to 35 °C Humidity: 7 % to 93 % RH. non-condensing – Non-operating Temperature: -40 °C to 68 °C Humidity: 5 % to 93 % RH. . ISO 9296.9153 OMC-R Product Description Sun Blade™ Ultra25 Workstation One 1.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 36 All rights reserved. use and communication of its contents not permitted without written authorization. 23 °C) Height: Width: Depth: 445 mm 205 mm 569 mm Cabinet dimensions Weight Hardware MTBF appr.31 kg 50000 hours Alcatel-Lucent File PD1353E9.

1 Alcatel-Lucent File PD1353E9. 47 – 63 Hz 2 078 VA Temperature: Humidity: 5 °C to 35 °C 20 % to 80 % RH. Passing on and copying of this document.3. use and communication of its contents not permitted without written authorization.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 Supply voltage Max. ISO 9296. . 44 kg 17 900 hours 5.3 UltraSparc IV generation 5.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 37 All rights reserved. non-condensing -20 °C to 60 °C 5 % to 93 % RH.3. non-condensing – Non-operating Temperature: Humidity: – Acoustic noise 40 dBA (acc. 23 °C) Height: Width: Depth: 222 mm 1446 mm 610 mm Cabinet dimensions Weight Hardware MTBF max. power consumption Environmental data – Operating 200 – 240 VAC.9153 OMC-R Product Description 5.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.

3.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 38 All rights reserved.3.3 Alcatel-Lucent File PD1353E9. Passing on and copying of this document.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 (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 Sun Fire™ V490 Server Four 1350 MHz (or 1800 MHz) UltraSparc IV processors 16 GB RAM 2 x 73 GB internal disk + 6x73 GB External Disk Bay SE3510 See Section 5.3.4 X Large and XX 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 disk + 12x73 GB External Disk Bay SE3510 See Section 5.1 Hardware MTBF V490 :13 100 hours SE3510 (6x73 Gb) : 160 000 hours 5.9153 OMC-R Product Description 5. use and communication of its contents not permitted without written authorization.

use and communication of its contents not permitted without written authorization. 37. 47 – 63 Hz 650 VA Temperature: Humidity: 5 °C to 40 °C 20 % to 80 % RH. power consumption Environmental data – Operating 100 – 240 VAC.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 39 All rights reserved. non-condensing – Non-operating Temperature: Humidity: – Acoustic noise Less than 6. Passing on and copying of this document.6 Standard HMI server Sun Fire V440 Server Two 1280 MHz UltraSparc IIIi processors 4 GB RAM 4x73 GB disk Supply voltage Max.3. .9153 OMC-R Product Description 5.7 B sound power when operating and idle Height: 174 mm Cabinet dimensions Width: 440 mm Depth: 635 mm Weight Hardware MTBF max. non-condensing -20 °C to 60 °C 5 % to 93 % RH.0 kg 22 600 hours Alcatel-Lucent File PD1353E9.

DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 40 All rights reserved. .3. use and communication of its contents not permitted without written authorization. power consumption Environmental data – Operating 100 – 240 VAC. 47 – 63 Hz 660 VA Temperature: Humidity: 5 °C to 40 °C 20 % to 80 % RH.6 Hardware MTBF 13 500 hours Alcatel-Lucent File PD1353E9.0 B sound power when operating and idle Height: 222 mm Cabinet dimensions Width: 440 mm Depth: 495 mm Weight Hardware MTBF max. non-condensing -20 °C to 60 °C 5 % to 93 % RH.3.9153 OMC-R Product Description Netra 440 Server Two 1280 MHz UltraSparc IIIi processors 4 GB RAM 4x73 GB disk Supply voltage Max. Passing on and copying of this document.0 kg 22 600 hours 5. 37.7 Large HMI server Sun Fire V440 Server Four 1280 MHz UltraSparc IIIi processors 8 GB RAM 4x73 GB disk See Section 5. non-condensing – Non-operating Temperature: Humidity: – Acoustic noise Less than 7.

3.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 41 All rights reserved. . use and communication of its contents not permitted without written authorization.9153 OMC-R Product Description Netra 440 Server Four 1280 MHz UltraSparc IIIi processors 8 GB RAM 4x73 GB disk See Section 5. Passing on and copying of this document.6 Hardware MTBF 13 500 hours Alcatel-Lucent File PD1353E9.

DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 42 All rights reserved. Passing on and copying of this document. UNIX terminal 1 Mbps 64 kbps per user (128 kbps is recommended ) OMC host server 64 kbps (128 kbps is recommended ) Citrix terminal HMI server 1 Mbps UNIX terminal 64 kbps 10 Mbps NPO server 1 Mbps NPO client 256 kbps 1Mbps per user HMI server NPO client Citrix Alcatel-Lucent File PD1353E9. the user terminals (either Unix terminal using X11 protocol or Citrix terminals).9153 OMC-R Product Description 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. . use and communication of its contents not permitted without written authorization. and 9159 NPO.

. ABBREVIATIONS ACO ALMAP Ater BSC BSS BTS CM CPU DCN ETSI FTP FM Gb GGSN GPRS GSM IMT IP LAN LASER MFS MSC NMC NPO OMC-R O&M PCM PLMN PM PSDN QoS RNO SPC TC TMN TRX WAN WS XT Alarm Call Out Alcatel Management Platform Sub-multiplexed TC – BSC Interface Base Station Controller Base Station System Base Transceiver Station Configuration Management Central Processing Unit Data Communication Network European Telecommunications Standards Institute File Transfer Protocol Fault Management Telecommunication interface between BSS and SGSN Gateway GPRS Support Node General Packet Radio Service Global System for Mobile communication Initialization and Maintenance Terminal Internet Protocol Local Area Network Lucid network Availability Stability and Event Reporting tool Multi-BSS Fast packet Server Mobile Services Switching Center Network Management Center Network Performance Optimizer Operation and Maintenance Center – Radio part Operation and Maintenance Pulse Code Modulation Public Land Mobile Network Performance Management Packet Switched Data Network Quality of Service Radio Network Optimization Semi-Permanent Connection (Nailed-Up Connection) Transcoder Telecommunication Management Network Transceiver Wide Area Network Workstation Xterminal. client user terminal End of Document Alcatel-Lucent File PD1353E9. Passing on and copying of this document.9153 OMC-R Product Description 7. use and communication of its contents not permitted without written authorization.DOC Reference 3DC 21076 0005 TQZZA Date 08/02/2008 Edition 09 Page 43 All rights reserved.

Sign up to vote on this title
UsefulNot useful