06_mn1780eu11mn_0001_om_tools

Operation and maintenance tools overview Siemens

MN1780EU11MN_0001 © 2005 Siemens AG

1

Contents 1 Operation and maintenance principles 3 2 Local Maintenance Terminal (LMT) 7 3 Radio commander 11 3.1 Radio commander HW 12 3.2 Operation and maintenance link 17 3.3 RC software 26 3.4 RC tasks 32 3.5 Graphical user interface 44 4 OMC Tool Set (OTS) 49 5 Exercise 53 6 Solution 57

Operation and maintenance tools overview

Siemens Operation and maintenance tools overview

MN1780EU11MN_0001© 2005 Siemens AG

2



3

1 Operation and maintenance principles



4

To meet the operator's requirements in terms of controlling the complexity of a GSM system in an efficient and cost-effective way, an enhanced Operation and Maintenance concept has been developed. It combines the O&M functionality within the SBS network elements via the LMT with the full graphical monitoring and control features relevant to an operation and maintenance terminal (OMT), incorporated into a centralized Operation and Maintenance Center (RC). For the Radio Commander, simply referred to as the RC in the following text, a modular software has been developed on the basis of a compact user-friendly commercial hardware, which can be easily maintained and expanded. In order to minimize the operator’s maintenance costs and maximize his revenue, the following features are provided:

• simple and effective fault location, fault isolation and recovery,

• effective software management (outage during SW download)

• advanced database handling,

• indication of File Process Completion (at the RC information about the completion ratio of important time-consuming file processes is displayed).

• alarm status overview and summary

• local O&M functionality on the LMT (on local Element Management Layer) for all BSS components,

• centralized Operation and Maintenance from the RC via the OMT (on global Element Management Layer),

• centralized post-processing of NE data with help of the RC toolset (OTS)

• user-friendly Man Machine Graphical User Interface (RC and LMT),

• a common Command Line Interface (CLI) between RC and LMT,

• enhanced security control,

• standardized communication interfaces,

• commercial HW platform (SUN/SOLARIS) with standard UNIX operating system for the RC,

• provision a standard Q3 interface to the superior Network Management Center (NMC) on Network Management Layer at RC



5

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RadioCommander

(RC)

CM+ Moduleof O&MToolSet

(OTS)

O-Link

AsubAbis

Radio Planning Tool

Q3

NMC: Network Management Center LMT: Local Maintenance Terminal

NMCNetworkManagementLayer

ElementManagementLayer

NetworkElementLayer

Manual input

BTSE site specific input

LMT

BTSE BSCMSC/VLR

global

local

TRAU

LMT LMT

A

interworki

nginterworking

remote

remote

Fig. 1 O&M tools



6



7

2 Local Maintenance Terminal (LMT)

Fig. 2 Graphical LMT



8

The LMT is a portable terminal, e.g. a laptop computer used for local or remote operation and maintenance functions. The LMT has the following characteristics:

• commercially-available hardware is used,

• facility for installation and maintenance visits for all on-site O&M actions e.g. initialization, diagnosis or test,

• all SBS entities can be installed without available communications to other entities by means of the LMT,

• the same LMT is used for all entities,

• an LMT connected to the BSC can control the BSC and the connected TRAUs and BTSEs,

• an LMT connected to BTSE or TRAU operates in local mode, i.e. to control only the equipment of that entity, or in remote mode i.e. also to control the functionality in the corresponding BSC,

• the RC is always informed of local LMT intrusion (LMT login/logout notification). A few screenshots illustrating LMT handling are given below:



9

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 3 Set Command in the tree view



10

Fig. 4 Wiring data BTSE



11

3 Radio commander

Fig. 5 Radio commander structure



12

3.1 Radio commander HW The hardware equipment of the Radio Commander is based on the state-of-the-art commercial computer hardware components for UNIX-based systems. The Radio Commander is designed as a distributed computing system consisting of a set of components connected via LAN. The architecture is governed by the client/server principle, which contributes to system flexibility and robustness. Within the Radio Commander hardware architecture, the functional roles are distributed as follows:

• the functions of the Server: OMP (Operation and Maintenance Processor)

• the functions of the Clients: OMTs (Operation and Maintenance Terminals), typically graphical work-stations, X-Terminals or X-Terminal Servers

In addition, the hardware is composed of the following components

• Connection equipment Hardware for LAN connectivity Hardware for X.25 or PCM connectivity

• Printer: LAN, or connected to OMP or OMT, supporting all standard paper formats (A4, letter,..), spool oriented Color, page oriented black-and-white Graphic, character Line printer

• Storage devices Additional streamer tapes External disk storage

• Special external alarm devices, configurable by operator via icon Lamps in different colors, to indicate the alarm severity Acoustic output for critical alarms

• an OMP-console (Digital VT520 or VT 420) or SUN Standard Color Monitor

• standard CD/DVD drive



13

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MSC

BSC

BSC

X Terminal X Terminal

CLI telnet access

CLI modemaccess

remote OMT remote OMT

X TerminalServer

X.25

LANDedicated

X.25

PCM30/24 "nailed-up"connection

Hub

OMTOMTLAN

OMPX.25 net

Modem

BSC

Ultra 1/10 / Sun Blade 150 E4x00 / Sun Fire F4800E420R / Sun Fire V480Ultra 60 / Sun Blade 2000

LAN

BSC

IP-based O-link

Fig. 6 Hardware Architecture, example



14

3.1.1 OMP - the server The OMP is the main hardware, where all the tasks for the supervision and control of a GERAN are processed. The OMP works as a server and is connected to the OMT via a Local Area Network (LAN), implemented as an Ethernet. On the other hand, the OMP is responsible for the connections to the BSC to be controlled. The OMP supports communication links to the

• local OMT via LAN through the Fast Ethernet 10/100BaseT (Switch/Hub)

• BSC via WAN / dedicated Link / IP-based O-link

• TRAU and BTSE via the BSC

• National OMP (to be defined)

Simultaneous sessions There is no limit to the number of terminals that can be configured to be connected to the OMP. As for multi-session capability, at the OMTs several active graphic user interface (GUI) sessions plus a number of alphanumeric sessions can run simultaneously, but with regard to acceptable response times (performance), up to 20 sessions are estimated to be open simultaneously. The sessions can be local or remote. GUI sessions can run on X-Terminals simultaneously. Alphanumeric sessions can be interactive when the operator is using the CLI or unattended when using scheduled scripts. The max number of CLI based sessions in addition to the GUI sessions that can run contemporaneously per OMX/OMT/OMT Server/RC are 16.

Management Capacity The RC can manage up to 48 BSC with the following maximum configuration

• 120 sites / 236 sites for HC-BSC (BTSE/BTSM, inclusive TRAU)

• 150 cells (BTS) / 400 cell for HC-BSC

• 250 transceiver (TRX) / 900 transceiver for HC-BSC If the OMP is also connected to NMC only 40 managed BSS are supported.



15

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

~20 GUI sessions by combination of several OMT servers and OMTs

8 GUI sessions 2 GUI sessions

OMT Server

X-T. X-T. OMT X-T.

Sun Blade 150Sun Blade 2000

OMPConsole

Disk Array

Sun Fire F4800SunFire V480

Disk Array

Fig. 7 General hardware structure of radio commander



16

3.1.2 OMT - the client The OMTs are the workstations with the Command Line Interface, which are used by the RC staff to enter their commands. Typically, the OMT (Operation and Maintenance Terminal) is a graphical workstation, but given the Radio Commander’s flexibility, abroad range of different hardware types of OMTs can be worked with:

• the Workstation (WS) Depending on the hardware used, the Workstations can handle one or two sessions: one local session and one additional session of an X-Terminal.

• the X-Terminal (XT) The X-Terminals do not require such a powerful hardware as the Workstations. However, they cannot run a session alone, but they need a Workstation or a dedicated X-Terminal-Server to process the user tasks. So the functions of the X-Terminal are restricted to handle the user input (keyboard and mouse) and to display the output (monitor).

• a dedicated X-Terminal-Server (OMX) Unlike the Workstations, which can handle just one additional session, the X-Terminal-Server can handle many sessions for X-Terminals. One of these sessions can also run locally, i.e. one session runs at the OMX and all the other sessions run at the XT. The OMT are connected to the OMP in a LAN (Local Area Network) configuration.



17

3.2 Operation and maintenance link The connection between RC and SBS is called OMAL. It can be implemented with redundancy.

Via A interface (PCM lines)and nailed-up connection (NUC)

through the MSC

Via X.25 packet data network(switched virtual circuit) or

point-to-point dedicated link

Via IP network (IP based O-linkbetween the BSC and the RC)

OMP - BSC connection: OMAL

Fig. 8 Implementation of OMAL



18

3.2.1 RC connections to the network elements (BSS) The RC system comes with three different possible connections to the managed BSS network entities:

• G.703 (PCM) connection via MSC (PCM link) This interface is implemented by the 2 Mbit/s | 1,54 Mbit/s board equipped into the OMP Server in the RC (PT card). The link is terminated on the STLP (or QTLP) module on the BSC side.

• X.21 serial connection, directly to the NE or via a WAN with HSI board (dedicated line) The new HSI/PCI board uses a different type of technology and provides four ports, each supporting 2 Mbit/s baud rate allowing to connect up to 32 remote systems at 64 Kbit/s each. At the BSC site the dedicated point to point X.25 link and connection via X.25 PSDN are provided by two IXLT boards (cold standby) and is based on the X.21/ V.11.

• a TCP-IP connection, through an additional LAN card inserted in the OMP. At the BSC site the TCP-IP connection is provided by two MPCCV9 boards (hot standby redundancy).



19

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MSC

BSC

BSC

X Terminal X Terminal

CLI telnet access

CLI modemaccess

remote OMT remote OMT

X TerminalServer

X.25

LANDedicated

X.25

PCM30/24 "nailed-up"

connection

Hub

OMTOMTLAN

OMPX.25 net

Modem

BSC

LAN

BSC

IP-based O-link

Fig. 9 RC connections to BSS



20

3.2.2 OMAL via PCM link The OMAL (at a transmission rate of 64 kbit/s) is mapped on the BSC site in the PCMS Link, connecting BSC with TRAU and the MSC site. The OMAL is transferred through the TRAU transparently. At the MSC the incoming OMAL of several incoming PCMA Links are multiplexed into a common 2 Mbit/s link (based on the PCM30 structure), which is directly connected with the RC. This implementation is called “nailed up connection“. The RC can control and supervise up to 31/23 BSS. A PT E1/T1 board, equipped inside the OMP, implements this communication interface.



21

PCMS

BSCIXLT

SYNCHRO

TS 30

OMAL

TRAUMSC

Semi permanent or nailed up

connection (64 kbit/s)

X25A

PT E1

OMP

Fig. 10 Interface card Newbridge sprite E1 (back view)

Fig. 11 PT card for E1 standard (PCI370 BPQ E1)



22

3.2.3 OMAL via dedicated line The connection via dedicated line can be realized in two ways:

• dedicated point to point X.25 link

• connection via a private or public X.25 Packet Switched Data Network At the RC an external communication controller, the HSI/PCI interface board, provides the interface. The X.25 packet switched data network requires special modems to convert the X.21/ V.11 interface into the X.25 protocol, used at the packet switched data network. A HSI/PCI board can be installed in the OMP server.



23

BSC

IXLT

OMP

HSI/PCI

PSDNX.25 network

Modem(DCE)

Modem(DCE)

dedicated point to point connection

connection via a packet switched data network

X.21/ V.11 Interface

Fig. 12 Two options for implementing a dedicated line

PCI BoardHSI Card

„Hydra-Cable“With

4 x 2 MbitPorts

Fig. 13 HSI/PCI board



24

3.2.4 OMAL via IP link In the third case the connection at the BSC site is the BSC front panel Ethernet10/100 Base T connector. This can be realized with the new MPCCV9 board in addition with the new TDPCV9 only, although the key functionality is implemented within the MPCC board. An Ethernet 10/100BaseT link via a RJ45 connector is used to transport information concerning the connection between OMP and the managed BSSs (either file transfer or O&M purposes). It is completely separated from the Ethernet link used for RC internal connections and it is referred as IP based O-link LAN. The communication protocol profile is Q3 on top of TCP-IP over Ethernet. Two IP addresses must be uniquely defined for each BSC, as each BSC is equipped with two MPCC boards – one active board and one standby board. The active IP address is always related to the active MPCC copy, while the additional one is always associated with the standby one. The RC or the CBC reaches the active MPCC board at the BSC via the corresponding active IP address. The additional IP address is necessary for testing purposes with respect to the standby MPCC board. To each Ethernet port there is assigned a unique Medium Access Control (MAC) address. There is only one active IP address, which corresponds at different times and in an exclusive way to two different MAC addresses.



25

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IXLT-0

IXLT-1

RC

CBC

LMTLAN

X

IP-0X.25 Dedicated

X.25 Dedicated

X.25 PCM Timeslot

X.25 PCM Timeslot

BSC

LMT V.11 64Kbit/sec

StandbyMPCC-1

ActiveMPCC-0

Testonly

Hub orSwitch or

Router

IPNETWORK

Fig. 14 Possible connections between BSC and RC



26

3.3 RC software The software architecture of the Radio Commander is governed by the client-server principle and strictly follows the object-oriented approach. It complies with common application software standards such as Q3, GDMO/ASN.1, SNMP, CORBA, standard C++. The whole system is modular and distributed, which increases its flexibility, scalability and robustness.

3.3.1 Logical layers The figure on next page shows the logical structure of the system, while not focusing on the complexity of the underlying processes. You can see how the different layers of the system are built one on top of the other. The two base layers are comprised of standard products, which increase the system’s flexibility and robustness. They encompass the operating system and the TMN platform as well as a number of tools. The three top layers are comprised of the special functions (RC specific applications):

• Application Base Services provide universal services that can be accessed and used by all applications, reducing the need for individual applications to implement services of their own.

• The next layer comprises the System Management Functions of the Radio Commander.

• The top layer is the user interface.



27

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Operating System (Solaris™ 8)

Oracle 8.1.6Commercial TMN platform(Solstice™ Enterprise Manager 4.0)

Portable Management Interface (PMI)Management Information Server (MIS)Management Protocol Adapters (MPA)

Application Base ServicesEvent Handler, Logging, File Handling,External Device Management,

Process Framework, Safeguarding, etc.

Solstice™FTAM

Solstice™DiskSuite

CORBA(Orbix)CORBA Services

System Management Functions (SMF)Fault and State Management, Configuration Management,

Performance Management, Security Management, NMC Mediator

User Interface (UI)Graphical User Interface (GUI)Command Line Interface (CLI)

Command Handler

DB

Fig. 15 RC software architecture, logical layers



28

3.3.2 Standard products SW used with RC (base layers) The following standard SW products building the main elements of the Radio Commander software are listed.

• OMP and OMT operating system The operating system used on both platforms, OMT and OMP, is SUN SOLARIS 8. It is based on the standard UNIX System V Release 4.0 (SVR4.0) and offers multi-user / multitasking capability, a high portability level and a very high communication capacity between all processes.

• TMN platform (SUN Solstice Enterprise Manager, SEM) The Solstice Enterprise Manager is the state-of-the-art, standard-compliant, commercial TMN platform for the Radio Commander and stands for improved functionality, flexibility and scalability.

• CORBA CORBA, the Common Object Request Broker Architecture, uses an object oriented approach for creating software objects that can be reused and shared between applications. Each object encapsulates the details of its inner workings and presents a well-defined interface, which reduces application complexity.

• FTAM The File Transfer, Access and Management is a time-tested and reliable commercial file transfer system.

• Database Management System (DBMS) The Radio Commander relies on a reliable state-of-the-art commercial Relational Database Management System (RDBMS) from ORACLE. In addition to the storing of the BSS database copy it contains the RC-Database as well as a database for measurement data, alarm log tables, active alarms and user administration data.



29

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Operating System (Solaris™ 8)

Oracle 8.1.6Commercial TMN platform(Solstice™ Enterprise Manager 4.0)

Portable Management Interface (PMI)Management Information Server (MIS)Management Protocol Adapters (MPA)

Solstice™FTAM

Solstice™DiskSuite

CORBA(Orbix)CORBA Services

DB

Fig. 16 Standard SW products



30

3.3.3 RC application SW (top layers)

Application base services These services, which form the first sublayer of the specific Radio Commander applications, provide universally required functions accessible by all applications, such as:

• Logging

• file handling

• safeguarding. This layer shows clearly how the Radio Commander software itself is modular and distributed, making for more flexibility and robustness.

System Management Function (SMF) The operation and maintenance functionality is based on the System Management Functions. The Radio Commander provides complete support of System Management Functions for all managed Siemens mobile radio networks, e. g. GSM BSS and UTRAN. The following System Management Functions, according to OSI definition, are covered:

• Fault Management

• Configuration Management

• Performance Management

• Security Management The uniformity of the SMF modularity on every system level is one of the main design principles, ensuring reliability and flexibility. In addition, the Radio Commander offers a standard Q3 interface to the superior Network Management Center (NMC). Thus, System Management tasks issued at NMC level are mediated by the Radio Commander to be applied to the Siemens network elements.

User interface (GUI-CLI-online help) The highly configurable and user-friendly Man-Machine Interface of the new Radio Commander features a Graphical User Interface (GUI), a Command Line Interface (CLI) and an Online Help System: Graphical applications of the Radio Commander are based on the X-Window system and OSF-Motif. The OMT application runs on the Common Desktop Environment (CDE).



31

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 17 SMFs: logical function split according to the TMN model



32

3.4 RC tasks The tasks of the RC can be classified into the following categories:

• Security Management

• Configuration Management

• Performance Measurement Management

• Software Management

• Fault and Test Management

3.4.1 Security management The Security Management is related to all the functions to prohibit an unauthorized access to the network. Examples for the Security Management are

• creation of log files containing the commands entered from all the terminals by all the operators

• protection of the RC access by access profiles and passwords

• distinction between RC application access and UNIX access

• supervision of local access on sites (LMT access supervision)



33

!

Fig. 18 Security Functions

Fig. 19 Creation of User Profile



34

3.4.2 Configuration management The configuration management is related to all changes in the structure of the PLMN and to changes of all parameters relevant for the communication in the radio cells. Some examples for configuration tasks are

• adding new sites to the PLMN (new BTSE)

• adding or removing TRX to/from a site

• changing frequencies in the radio cells Several ways of working in the configuration management are implemented:

• online

• using script files, and

• using the DBAEM tool.



35

Fig. 20 Configuration Management

Fig. 21 Create Commands



36

3.4.3 Performance measurement management Performance measurements are essential for the surveillance of a mobile network. The corresponding information enables the operator to identify failures or quality of service problem areas within the network, which are not detected by the fault management, and help to optimize and extend the existing network. The operator establishes measurements with individual parameters. He can schedule, delete, modify, deactivate and display parameters of existing measurements and administer them interactively. All the measurements coming from a NE and requested by the operator are logged in dedicated database tables (Oracle database) and can be displayed on the screen or exported to post-processing tools.

Fig. 22 Performance Measurements



37

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 23 Creation of Scanner



38

3.4.4 Software management From the RC the complete software of the BSS is administered. Therefore the RC operator is able to:

• import BSS Software images and data coming from software factory

• download the BSS software images and data files

• download and activate patches

• activate BSS software

• upload data files from the BSS

• migrate BSS data base

• export data (e.g. for backup procedure)



39

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 24 Software Management



40

3.4.5 Fault and test management Fault Management includes all the measures required to detect and repair faults in the mobile communications network. Hardware faults are usually isolated to a particular module. Operation is normally switched to another module that takes over the function of the defective unit. The defective unit can be replaced later. The operator receives information about the probable cause. In addition, he has access to the on-line maintenance documentation, which provides further information on how to deal with the fault. Fault handling can be divided into the following main functions:

• Fault detection

• Fault recovery

• Alarm logging

• Alarm reporting If a fault is detected, the state and status of the objects concerned changes. These changes are displayed on the graphical workstation by graphical symbols, colors and animation. Each single failure (failure source) generates a single alarm report. Therefore, all alarms are transferred from the BTSE and TRAU via the BSC to the RC and the LMT. Alarm reports always result in one of five error types specified by GSM:

• Equipment alarm

• Communication alarm

• Quality of service alarm

• Environment alarm

• Processing alarm Moreover, each alarm is qualified by a probable cause giving more detailed information about the nature of the fault and an alarm severity.



41

Fig. 25 Fault and Test management

Fig. 26



42

Test Management is closely related to the fault management. The operator is able to activate remote diagnostic procedures, so-called tests in order to get further information for maintenance. Test results coming from BSS are logged in a test result database table, which can be retrieved by operator’s request for further analysis.

Handling of RC faults The RC supervises the following connections in order to detect possible link failures:

• RC to SBS via layer 2 supervision (LAPB), and

• OMP to OMT via keep-alive messages (TCP/IP). BTSE, BSC and TRAU autonomously perform fault recovery. The recovery process can be seen as a sequence of defense actions, performed to minimize the loss of service caused by a fault. Also in the OMS the service is supervised in order to detect internal faults.



43

?

Test MPCC

Fig. 27 Fault and Test Management

Fig. 28 Lock Module



44

3.5 Graphical user interface The Radio Commander supports different network management views. Customized geographical maps, on different scales, represent the territorial structure of the network (e.g. nation, region and district). The new Radio Commander provides a special maintenance view to let the operator see at a glance what is going on in the system. Only vital information is displayed, icons are not overloaded with information. The Navigator supports the operator in navigating through the graphical user interface and Radio Commander’s network editor. The Navigator can be used totally independently of the GUI. Hence, it is possible to directly issue commands via the navigator panel. The Network Editor allows flexible customization for GUI online (without reboot). For basic configuration changes it is also possible to run the Network Editor in stand-alone mode. The Network Editor supports e.g. "drag & drop" in the customization process. The range of customization options include

• Panel window contents e.g. background, dimensions, graphical objects represented on the panel

• Operator-defined network views e.g. new panels, new summary objects

• Graphical objects e.g. panel and position in panel, link to managed or external object, graphical attributes (line or icon), popup menus



45

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Standard Network ViewOperator defined view ‘n’

Operator defined panel contains operator defined summary, ob-jectsand/or single MOs & passive objects

Operator defined panel contains links to the standard network tree

View summary summarizes all operator defined panels

Fig. 29 Network views on radio commander



46

Fig. 30 Application launcher

Fig. 31 Geographical Map



47

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 32 BTSone Panel with logical icons and rack layout (lower left), BSS region panel with help view for state attributes (upper right)



48



49

4 OMC Tool Set (OTS)



50

BSS data are available "on-line" at the RC and (after export) "off-line" for post-processing by the OMC Tool Set OTS. OTS integrates and replaces the existing tools

• SPOTS (performance management PM),

• MIXY (configuration CM and fault management FM) and

• DUIT (trace management TrM). Four packages are available which may be used individually or in combination:

FM+ package supports alarm statistics and reporting. PM+ package provides reports and analysis of performance and traffic measurements. CM+ package enhances CLI and GUI configuration management. TrM+ package supports IMSI tracing and Cell Traffic Recording CTR.



51

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 33 Operation and maintenance tool set



52



53

5 Exercise



54



55

Exercise Title: RC function and setup

Query

• Name the functions of the OMP and of the OMT.

• Which types of OMT do exist and how do they differ?

• Can the OMT be connected to the BSC directly?

• List the OMAL connection types and the hardware required.

• Can A interface connection and Dedicated Line connection be used simultaneously with one OMP?

• Name the tasks, which can be performed by the RC.



56



57

6 Solution



58



59

Solution Title: RC function and setup

Query

• Name the functions of the OMP and of the OMT. See page 20.

• Which types of OMT do exist and how do they differ? See page 20.

• Can the BSC be connected to the OMT directly? No. Always the interface cards of the OMP are required.

• List the OMAL connection types and the hardware required. See page 28-29.

• Can A interface connection and Dedicated Line connection be used simultaneously? Yes. Up to four boards can be mounted in the BSC, so e.g. a configuration with 2 Newbridge Sprite and one Aurora 3200/3500 and one HSI/PCI board is possible. However, not more than 48 BSS can be controlled.

• Name the tasks, which can be performed by the RC. See page 36.



60

Documents

06_mn1780eu11mn_0001_om_tools