Technical_Description_TED__RC_BR7.0.pdf

8/11/2019 Technical_Description_TED__RC_BR7.0.pdf

1/144

Information

Radio Commander BR 7.0/UMR 3.0/TD 2.0

Technical Description TED

A50023-X4002-A2-3-7618


2/144

2 A50023-X4002-A2-3-7618

Technical Description TED InformationRadio Commander BR 7.0/UMR 3.0/TD 2.0

f Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment. Some of theparts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in prop-erty damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to complywith the applicable safety standards.

The same text in German:Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Spannung. Einige Teileknnen auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverletzungen undSachschden fhren.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertesPersonal die Anlagen installiert undwartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Gertemssen die zutreffenden Sicherheitsbestimmungen erfllen.

Trademarks:

All designations used in this document can be trademarks, the use of which by third parties for theirown purposes could violate the rights of their owners.

Copyright (C) Siemens AG 2003-2003.

Issued by the Information and Communication Networks Group

Hofmannstrae 51

D-81359 Mnchen

Technical modifications possible.

Technical specifications and features are binding only insofar as

they are specifically and expressly agreed upon in a written contract.


3/144

A50023-X4002-A2-3-7618 3

InformationRadio Commander BR 7.0/UMR 3.0/TD 2.0


This document consists of a total of 144 pages. All pages are issue 3.

Contents

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 Brief Description of the Radio Commander . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.2 Who should Read this Document? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.3 Notational Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2 How the Operator benefits from the Radio Commander Concept - anOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.1 Key Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.2 Pick & Mix - Application Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 Hardware Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.2 OMP - the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.3 OMT - the Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.4 Performance Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4 Software Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.1 Basic Principles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.2 Main Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

4.2.1 Logical Layers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

4.2.2 O&M ToolSet and Open Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

5 Working with the Radio Commander . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

5.1 Graphical User Interface (GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

5.1.1 Typical GUI Elements and Controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

5.1.2 Command Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.1.3 GUI Customization, Network Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

5.2 Command Line Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

5.3 Online Help System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

5.4 Remote Web Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

6 Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

6.1 General Principles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

6.2 Management of BSS/RNS Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . 58

6.3 Management of OMC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

6.4 CM+ Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616.5 Remote Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

6.6 Network Optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

7 State Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

7.1 What is Radio Commander State Management? . . . . . . . . . . . . . . . . . . . . 65

7.2 State Summarization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

7.3 Maintenance State View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

8 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

8.1 General Principles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

8.1.1 Fault Localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

8.1.2 Alarm Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72


4/144

4 A50023-X4002-A2-3-7618


8.1.3 NMC Mediation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

8.1.4 Internal Fault Correction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

8.2 Alarm Surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

8.2.1 Alarm Reporting and Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738.2.2 Alarm Monitoring List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

8.2.3 Alarm Routing to External Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

8.2.4 Auto-acknowledgement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

8.2.5 Specific Alarm Category Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

8.2.6 Adding of Comments to Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

8.2.7 Access to Alarm Manual from Alarm List . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

8.2.8 Event Forwarding Discriminators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

8.2.9 Alarm Harmonization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

8.3 External Trouble Ticketing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

8.4 FM+ Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

9 Test Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

9.1 Test Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

9.2 Test Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

9.3 Test Result Presentation and Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

10 Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

10.1 Measurement Job Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

10.2 Data Collection, Storage and Processing . . . . . . . . . . . . . . . . . . . . . . . . . . 87

10.3 Presentation of Measurement Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

10.3.1 BSS measurement values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

10.3.2 RNS measurement values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

10.4 PM+ Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

10.5 Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

10.5.1 Call Tracing, IMSI Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

10.5.2 Cell Traffic Recording, CTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

11 Security Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

11.1 User Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

11.2 Authorization Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

11.3 Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

11.4 Secure Communication within the UMTS O&M Network. . . . . . . . . . . . . . 100

11.5 Security Audit Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

11.6 LMT Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10211.7 Screen Locking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

11.8 Forced Session Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

12 Software Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

12.1 File Import/Export/Administration on the RC. . . . . . . . . . . . . . . . . . . . . . . 103

12.2 Download and Upload between RC and BSC/RNC/Node B. . . . . . . . . . . 104

12.2.1 Download Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

12.2.2 Operator Control of Loading Operations. . . . . . . . . . . . . . . . . . . . . . . . . . 105

12.3 Storage and Administration of Software on BSS/RNS. . . . . . . . . . . . . . . . 106

13 Log Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

13.1 Log Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107


5/144

A50023-X4002-A2-3-7618 5



13.2 Log Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

13.2.1 Alarm Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

13.2.2 Command Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

13.2.3 Upload of BSC/RNC/Node B log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11314 High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

14.1 System Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

14.2 Data Safeguarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

15 External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

15.1 General Principles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

15.2 RC-NMC Realtime Q3 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

15.3 Offline Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

15.3.1 Data Access Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

15.3.2 Network Planning Interfaces (RNPC and TNPC Interface). . . . . . . . . . . . 124

15.3.3 Bulk CM IRP Interface (MCCM Interface). . . . . . . . . . . . . . . . . . . . . . . . . 125

16 UTRAN Transport Network Management . . . . . . . . . . . . . . . . . . . . . . . 127

17 Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

18 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

19 Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139


6/144

6 A50023-X4002-A2-3-7618


Illustrations

Fig. 1.1 Radio Commander, a part of the Siemens

network management concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Fig. 2.1 Radio Commander, the successor to OMC-B. . . . . . . . . . . . . . . . . . . . . 11

Fig. 2.2 Radio Commander, a platform concept combining both

second generation and third generation mobile radio networks . . . . . . . 13

Fig. 2.3 Package concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Fig. 3.1 Sun hardware for the Radio Commander . . . . . . . . . . . . . . . . . . . . . . . . 17

Fig. 3.2 Hardware architecture concept, example . . . . . . . . . . . . . . . . . . . . . . . . 18

Fig. 3.3 OMT-Server and X-Terminal configuration, example . . . . . . . . . . . . . . . 20

Fig. 3.4 Transparent Doubled Monitors, example. . . . . . . . . . . . . . . . . . . . . . . . 21

Fig. 4.1 Software architecture, logical layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Fig. 4.2 Hierarchical structure of a Siemens GSM Mobile Radio Network,

logical function split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Fig. 4.3 Process flow of operations, Radio Commander and tool environment . . 30

Fig. 4.4 Interfacing, Radio Commander and O&M ToolSet . . . . . . . . . . . . . . . . . 31

Fig. 5.1 Application Launcher of the Radio Commander as access point to Radio

Commander applications, example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Fig. 5.2 Radio Commander Applications window, that is the Application Launcher

of the Radio Commander, example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Fig. 5.3 Geographical map, example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Fig. 5.4 GSM BSS region panel with help view for state attributes, example . . . 36

Fig. 5.5 Network entity site panel with logical icons and rack layout, example. . 37

Fig. 5.6 GSM OMC panel, example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Fig. 5.7 Panel Navigator with GSM panel tree, example . . . . . . . . . . . . . . . . . . . 39

Fig. 5.8 Command handling via panel window, example. . . . . . . . . . . . . . . . . . . 42

Fig. 5.9 Command History List, example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Fig. 5.10 Input form, example of a CREATE operation. . . . . . . . . . . . . . . . . . . . . 44

Fig. 5.11 Output form, example of a GET operation . . . . . . . . . . . . . . . . . . . . . . . 45

Fig. 5.12 Network Editor window, example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Fig. 5.13 Operator defined hierarchy and standard hierarchy . . . . . . . . . . . . . . . . 48

Fig. 5.14 Bullet mode, example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Fig. 5.15 Command Line Interface, examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Fig. 5.16 Online help, possibile ways of use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Fig. 5.17 Components for remote access via Web interface . . . . . . . . . . . . . . . . . 56

Fig. 6.1 Changing attribute values of managed object instances, example. . . . . 59

Fig. 7.1 Creating a user-defined panel via Network Editor, example. . . . . . . . . . 68

Fig. 7.2 Maintenance State View, example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Fig. 8.1 Alarm Monitoring List, example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Fig. 9.1 Test Monitoring List, example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Fig. 11.1 Login window, example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Fig. 11.2 Creating an authorization profile, GSM example . . . . . . . . . . . . . . . . . . 98

Fig. 11.3 UTRAN management architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Fig. 13.1 Alarm Log records, GSM example. . . . . . . . . . . . . . . . . . . . . . . . . . . . 110


7/144

A50023-X4002-A2-3-7618 7



Fig. 13.2 Alarm Log records, UMR example, sector . . . . . . . . . . . . . . . . . . . . . . 111


8/144

8 A50023-X4002-A2-3-7618



9/144

A50023-X4002-A2-3-7618 9



1 Introduction

1.1 Brief Description of the Radio Commander

The Radio Commander (RC) is a cutting edge Operation & Maintenance Center (OMC)

incorporating feature-rich element management functions for current and future

mobile radio networks.

Merging operation and maintenance for both 2nd and 3rd generation mobile radio net-

works, the Radio Commander introduces a new concept for mobile radio network

element management.

The Radio Commander supports different radio technologies, such as GSM, GPRS,

HSCSD, EDGE, UMTS, TD-SCDMA. Thus it provides a seamless evolution to 3rd

generation cellular networks. This allows the operator to benefit from reduced trainingand operating costs in a highly competitive market.

The Radio Commander is based on the latest object oriented development tools,

methods and technologies as well as on a powerful and reliable hardware and

software platform.

All the operation and maintenance functions are accessible via the customizable

Graphical User Interface (GUI) and the alphanumerical Command Line Interface (CLI).

The Radio Commander is part of the overall Siemens network management concept,

see Fig. 1.1.

Fig. 1.1 Radio Commander, a part of the Siemens

network management concept

Featuring an open system architecturewith high-level standardized

interfaces, the Radio Commander offers flexibility for additional external applications.

Siemens Mobile OSS

Element Managers

Service

Interfaces

Netviewer

FulfillmentService Service

BillingAssurance

SPOTS

Radio

Comman-der Commander CommanderManager

Switch IP @vantage

Message

CoordinatorMicrowave

Mobile RadioMobile Core

Mobile Data IMS

Enabling Services

IP and 3rd partyequipment


10/144

10 A50023-X4002-A2-3-7618


This protects operators investment by providing a smooth integration into existing

TMN environments.

1.2 Who should Read this Document?

This document is intended for anyone who would like to

get an overviewof the:

benefits of using the Radio Commander

technical capabilities of the Radio Commander

1.3 Notational Conventions

In the text, the names of macros, commands and operands are shown initalics, as are

screen elements.

Important information in the text is highlighted in boldprint.All hardware and software names used are trademarks of their respective

manufacturers.

iSpecial notes

!Warnings


11/144

A50023-X4002-A2-3-7618 11



2 How the Operator benefits from the Radio

Commander Concept - an Overview

This chapter provides an overview of the wide range of the features and their inherent

benefits of the Radio Commander, the element manager for Siemens mobile radio

networks.

The first part of the chapter, Key Features on page 11, highlights general concepts, the

second part, Pick & Mix - Application Packages on page 15, presents the package

concept.

2.1 Key Features

The Radio Commander introduces a new concept for mobile network management by

merging operation and maintenance for the different radio technologies of the second

and third generation on a single platform. The managed technologies include

GSM, Global System for Mobile Communications

GPRS, General Packet Radio Service

EDGE, Enhanced Data Service for GSM Evolution

HSCSD, High Speed Circuit Switched Data

UMTS, Universal Mobile Telecommunications System

TD-SCDMA, Time Division - Synchronous Code Division Multiple Access

The Radio Commander is the new generation of the widely used Siemens OMC-B which

to date has performed the element management for GSM radio networks.

Fig. 2.1 Radio Commander, the successor to OMC-B

Radio Commander has been completely re-engineered and structured in a strictly

modular manner to offer communications service providers maximum flexibility and

early market entry in a highly dynamic and competitive market.

BTS TRAUBTS

+ O&M ToolSet

Main Functions:

Fault, Configuration, Performance, Security ManagementTrouble Ticketing Support, Event & Log ManagementIntegrated Tool Concept, NMC Interface

BSS

LMT (LocalMaintenanceTerminal)

LMT LMT

O interface

Radio Commander


12/144

12 A50023-X4002-A2-3-7618


With its future-proof system architecture, as well as being embedded in the overall

Siemens network management concept, the Radio Commander exceeds

the requirements of todays and meets the challenges of tomorrows element

management.

The Radio Commanders well structured system architecture:

achieves advanced performance, based on industry standard hardware,

hardware and software scalabilityallows easy extension of capacity, see

Hardware Architecture on page 17and Software Architecture on page 25

protects operators investments:

Radio Commander for Siemens Basestation Release 7.0 can reuse

existing OMC-B hardware, for details refer to the Technical Stocklist

minimizes training costs by using a similar GUI to the OMC-B (so it has the same

look and feel).

allows the rapid integration of new services in an economic way

keeps the system open to futuredevelopments

based on industry standard hardware and software platforms, the Radio Com-

mander is able to integrate Internet technology(Web clients)

standardized interfaces, e.g. on its northbound side towards a Network Manage-

ment Center (NMC), allow seamless integration of Radio Commander into oper-

ators workflow environment

is well prepared for the convergence of networks: voice-data, TDM-ATM-IP

offers a feature-rich and customizable graphical user interface (GUI) which makes it

easy to work with, putting control of the real network at the operators fingertips, see

Working with the Radio Commander on page 33.

The different radio technologies realized within the GSM and UMTS network elements

are connected to the Radio Commander via their respective standard interfaces.

On its northbound side, the Radio Commander provides several open interfaces. There

is the powerful Q3 realtime interface towards an NMC, the file interface and the SQL in-

terface (to offline databases) for comprehensive access to radio network data, the Bulk

CM IRP (Configuration Management Integration Reference Point) for advanced config-

uration tools, and the interfaces towards radio (RNPC) and transport network planning

centers (TNPC).

Single Platform Concept

In mobile communications, a smooth evolution from 2G GSM to 3G UMTS networks is

desired. As the number of network elements to be managed steadily increases,

networks diversify, presenting a multi-vendor environment, with decreasing margins for

operators in an even more competitive market.

A key aim of the Radio Commander therefore is the management of UMTS and GSM

as one network relying on the same O&M platform, thus providing a common

management platform for 2G, 2.5G and 3G networks. This allows the number of network

elements managed to be decoupled from manpower required in operations depart-

ments.

Fig. 2.2shows the principle architecture for element management in

Siemens mobile radio networks.


13/144

A50023-X4002-A2-3-7618 13



Fig. 2.2 Radio Commander, a platform concept combining both

second generationand third generationmobile radio networks

Although differences due to inherent technology characteristics exist, the utmost care

has been taken to provide

the same functions for all supported radio network technologies, and

a homogeneous representation to the operatorCommon management for GSM and UTRAN equipment consists of the entire range of

management functions, such as handling of both GSM and UMTS network alarms, and

stretching out to a homogeneous configuration handling, e.g. display and handling of bi-

technology network topologies.

Also covered are features such as similar logs for all connected network elements with

global search and retrieval, a state management based on a comfortable maintenance

state approach, as well as similar fault and performance management facilities.

In the same way the Radio Commanders Operation & Maintenance functions offer full

management support for General Packet Radio Service (GPRS) and Enhanced Data

Service for GSM Evolution (EDGE) networks.

All general management principles applicable to the GSM circuit-switched connections

are also valid for the GPRS packet-switched connections and EDGE networks. This

means the operator is able to:

verify the correct dimensioning of the network (short & long-term planning)

examine the network planning parameters

fine-tune the network configuration parameters

identify the Quality of Service and performance of the network

The Radio Commanders capabilities for UMTS terrestrial radio access network

(UTRAN) include common O&M management for Node B and for RNC functions. This

includes the radio parameters of Node B and RNC, as well as the parameters to config-

ure the ATM transport objects of these network entities.

RNC

Node BNode B

BSC/

TRAU

BTS BTS

Radio Commander

+ O&M ToolSet

OSS

2G 3G

N interface


14/144

14 A50023-X4002-A2-3-7618


Finally, the Radio Commander also provides the unique entry point for data from both

the GSM and UMTS radio networks and mediates it to an upper-layer NMC.

User interface

There are different ways for the operator to get things done:

by using the interactive functions of the GUI

The highly configurable GUI, which offers customization options as well as online

help and internationalization support, is easy to work with and helps to minimize

operator training costs.

by entering single commands (= fast) on the Command Line Interface (CLI) or by

executing command scripts (= automated) containing the corresponding

commands.

The Command Line Interface is a fast, man-machine interface for experienced

operators, providing useful options such as scheduling and scripting.

Future-proof open system architecture

The Radio Commander implements open standard technologies. Its component-

based architecture, in combination with the high-level open interfaces,allows the

operator to customize and develop new management applications.

The Radio Commander offers

industry standards, e.g. CORBA, Java, GDMO/ASN.1, Q3, SNMP, CMIP, RPC

support of shared resources, e.g. LAN equipment, databases

integrated database with external SQL access

flexible remote access: WindowsNT PCs, Web technology

supports management integration of multi-vendor equipment,

integrated tool support for network planning tools, trouble ticketing, mail, ...


15/144

A50023-X4002-A2-3-7618 15



2.2 Pick & Mix - Application Packages

As flexibility is one of the most important challenges in the dynamic world of mobile

communications, the RC is available in packages, one Kernel Package and additional

Application Packages.

Operators can pick and mix the packages to fulfill their specific needs.

Fig. 2.3 Package concept

Kernel - the basic package

The Radio Commanders basic Kernel Package includes the essential components for

operating and maintaining mobile radio networks and for keeping the system open for

new technologies:

technology Plug-Ins, supporting network elements for the different radio

technologies

complete core functions for Fault, Configuration and Performance Management

Security management

online documentation

Special Application Packages

Everything that goes beyond the basics is available in special Application Packages.

Added to the kernel the special packages allow a tailored solution for all needs and in-

terests.

Standard

Management

FaultSoftwarePerformanceConfiguration

TestLogSecurityStateManagement

Management Management Management Management

Management Management Management

Operability (GUI)

RC - O&M ToolSet Applications - Analysis and Configuration

GSM UTRAN TD-SCDMASW Plug-In SW Plug-InSW Plug-In

CM+ PM+ FM+PM Analysis Fault Statistics

Trace SCAVisualization

SQLInterface

MCCM Interface

(Bulk CM IRP)

Network Planning Interfacesto RNPC and TNPC

Extended SafeguardingB&R Mirroring

Add Services

GPRS, EDGE, LCS

Q3N-interface

File

Interface

Single

Features

Operability

RC - Optional Application Packages and Interfaces

RC Kernel - Basic Package - Common SW and HW Architecture


16/144

16 A50023-X4002-A2-3-7618


Special Application Packages are:

FM+, user and pre-defined alarm and event reporting, for preventive radio network

maintenance and monitoring, see also FM+ Package on page 80

PM+, powerful performance reporting and quality monitoring,

including trend analysis and threshold monitoring, see also PM+ Package on

page 91

CM+, full featured graphical and tabular network representation for fast and efficient

reconfiguration, see also CM+ Package on page 61

Trace Management, IMSI trace and Cell Traffic Recording analysis for GSM net-

works, using system-immanent tracing capabilities, offering user friendly charts and

presentations, see also Tracing on page 91

NMC I/F, a powerful realtime interface, see RC-NMC Realtime Q3 Interface on

page 121

Network Optimization, see Network Optimization on page 63

Extended Operability, see Working with the Radio Commander on page 33, with

extensive GUI customization facilities, online and offline, special Network Editor high-performance, secure, remote Web access to complete GUI

enhanced CLI handling and scheduling, ideal for permanent remote login, e.g.

from NMC

Data Safeguarding

Backup & Restore

Data Mirroring

Additional Services

full O&M support for GPRS/EDGE

location based services

Special Interfaceslike SQL, File, RNPC


17/144

A50023-X4002-A2-3-7618 17



3 Hardware Architecture

This section provides an overview of the hardware architecture of the RadioCommander.

The main hardware components as well as the major features are described in Over-

view on page 17, followed by a more detailed focus on the Operation and Maintenance

Processor, see OMP - the Server on page 19, the Operation and Maintenance Ter-

minals, see OMT - the Client on page 20, and the Performance Data on page 21.

3.1 Overview

The hardware of the Radio Commander is based on the state-of-the-art commercial

computer hardware components for UNIX-based systems. The hardware was chosen

with the aim of achieving a high degree of modularity and flexibility for further capacity extensions

provision of distributable and scalablesystem

utmost system reliability

local maintenance availability

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 roles are distributed as follows:

Server: OMP(Operation and Maintenance Processor), see OMP - the Server on

page 19

Clients: OMTs (Operation and Maintenance Terminals), typically graphical work-stations, X-Terminals, see OMT - the Client on page 20

The new state of the art hardware for the RC: Sun Fire 4800, used as OMP, Sun Blade

150, used as OMT, Sun Fire V480, used as OMT server or O&M ToolSet server.

The existing RC hardware - based on Sun Enterprise series, Sun Ultra series and Sun

Blade series - is still supported in BR 7.0/UMR 3.0/TD 2.0. All details concerning the de-

livered hardware components are listed in the Technical Stocklist, that is supplied to

customers with each new software load patch.

Fig. 3.1 Sun hardware for the Radio Commander

Of course, the Radio Commander will provide continued support for all the standard

hardware presently in field use, as far back as GSM release BR 4.5, with recommended

upgrading strategies.

Sun Fire V480Sun Fire F4800Sun Blade 150Sun Blade 2000


18/144

18 A50023-X4002-A2-3-7618


In addition to OMTs and OMPs, the hardware is composed of the following components:

Connection equipment

hardware for LAN connectivity

hardware for X.25 or PCM connectivity, for GSM 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

flexible dimensioned external disk storage

external autoloader

Special external alarm devices, configurable by operator via icon, distinguishing

between the three different events: incoming new alarm, ackknowledged alarm, andceased alarm, offering

lamps in different colors, to indicate the alarm severity

acoustic output for critical alarms

Fig. 3.2illustrates the hardware architecture concept of the Radio Commander.

Fig. 3.2 Hardware architecture concept, example

Node BBTS

BSC/ RNCTRAU

IPnetwork

X.25network

IPX.25Dedi-catedX.25

PCM30/24NUC

OMP

Operation and Maintenance Processor

OMT/OMT ServersOperation andMaintenance Terminals

X-Terminals O&M ToolSetServer

LAN

viaMSC

Radio Commander

2G 3G


19/144

A50023-X4002-A2-3-7618 19



3.2 OMP - the Server

The OMP is the main hardware, the server, where all the tasks for supervision and con-

trol are processed.

The Radio Commander uses the Sun server line for the OMP, a reliable and well-tested

product line.

The product line ranges from low-budget servers for small systems up to scalable high-

end servers for large systems. The servers are based on Sun Fire V480 (workgroup

server) and on Sun Fire 4800 (midrange server). Currently existing RC configurations

with Sun Enterprise 4500 or Sun Enterprise 420R (workgroup server) are supported. In

order to offer the latest and most advanced hardware available on the market, new

product families will be selected to continuously adapt Radio Commanders capacity on

to operator requirements.

Scalability of the configuration

The minimum configuration for the Radio Commander is an OMP, equipped with

2 CPU/2 GB RAM (plus storage devices for installation and backup purposes), providing

also the OMP functions.

With a growing number of network elements being connected to the system, the pro-

cessing power of the OMP can be easily extended (RAM, hard disk capacity, CPUs).

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, several active graphic user interface (GUI) sessions plus

a number of alphanumeric sessions can run simultaneously. Under normal conditionsup to 20 running sessions are supported.

The sessions can be local or remote. GUI sessions can run on X-Terminals simulta-

neously. Alphanumeric sessions can be interactive when the operator is using the CLI

or unattended when using scheduled scripts.

Management Capacity

The RC can manage up to 48 BSC in the following maximum configuration:

200 sites (BTSE/BTSM, inclusive TRAU)

400 cells (BTS)

250 transceiver (TRX), with a maximum of about 12 000 TRX per RC

The RC can support e. g.: 10 RNCs

5000 Node Bs

15 000 cells

The numbers given largely represent maximum configurations possible. As dynamic

network load may vary depending on exact network configuration and topology it is

strongly advised to check each configuration in particular detail.


20/144

20 A50023-X4002-A2-3-7618


3.3 OMT - the Client

The OMTs are the clients, used by the operators to enter their commands.

Typically, the OMT (Operation and Maintenance Terminal) is a graphical workstation,

but given the Radio Commanders flexibility, a broad range of different types of

OMTs can be worked with, such as for example:

graphical workstations

X-Terminals

graphical workstations acting as X-Terminal

PCs with X-Terminal emulation

PCs/workstations with alphanumeric terminal emulation (e.g. VT420, VT520) for

alphanumeric access (viatelnet)

Every type of OMT can act as a local or remote terminal. The protocol used on the link

between a remote OMT and the OMP is TCP/IP.

The currently recommended type is the Sun Blade 150, supported as well are Sun Blade

100, and Sun Ultra 1, 5 and 10. Introduced to act as OMT server is the Sun Fire V480,

for all details refer to the Technical Stocklist.

Fig. 3.3 OMT-Server and X-Terminal configuration, example

Local X-Terminals are connected via LAN. Remote X-Terminals provide quick and

easy access to RCs from any point in the network. The transmission rate on the link

between the OMT-Server and the X-Terminal has to be sufficient.

Technical Assistance Center support

The Radio Commander also supports TAC terminals, a special kind of terminal used

by the Siemens Technical Assistance Center staff for accessing different OMCs to pro-

vide quick, easy technical support.

OMTServer

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

Console

Disk Array

OMPAlarmPrinter

SpoolPrinter

Network Elements

LAN (Fast Ethernet10/100 BaseT)

2 GUI sessions8 GUI sessions

20 GUI sessions by combination of several OMT servers and OMTs

Radio Commander


21/144

A50023-X4002-A2-3-7618 21



Transparent Doubled Monitors

Another new feature of the Radio Commander is the hardware and software support

provided to allow 2 monitors connected to 1 OMT, thus doubling the viewing space in

a transparent way.The Radio Commander application runs simultaneously on both monitors and can be

controlled via one mouse and keyboard.

Fig. 3.4 Transparent Doubled Monitors, example

In the doubled display area of the two monitors, operators get a lot more information at

a glance, making the system handling easier. Windows can be moved seamlessly from

one screen to the other.

Transparent Doubled Monitors can be used with all standard OMT configurations, but

not with X-Terminals or an OMP used as OMT.

3.4 Performance Data

The Radio Commander is designed along the following guidelines.

O&M Commands

The following command response times are achieved under normal conditions (that is:

no overload situation, 3 to 4 running sessions, in general up to 20 are supported, no ad-

ditional jobs running on the OMP).

< 2 seconds for RC internal commands, no RC database retrieval commands, no

overload on the LAN (e.g. by traffic from other computers connected to the LAN)

< 5 seconds for database retrieval commands, with standard queries (e.g. alarms,

performance data)user defined queries that include a lot of selection and filter criteria can exceed

the value

RNS and BSS commands, for all network entities average

simple commands (e.g.GET/SETstates) 1 s

complex configuration commands (e.g.CREATE) 3 s

Tab. 3.1 Command response times


22/144

22 A50023-X4002-A2-3-7618


Events

Average time between occurrence of event and display on RC:

The peak rate for receivable events (including alarms) on the RC from all the connected

BSS/ RNS, without overload handling, is 200 per second for a duration of 1 minute.

Link transmission capacity

RC-BSS link: The transmission capacity is 64 kbit/s.

The RC detects and reports a communication break to the BSS within 2 minutes.

The peak transfer rate is 15 events per second.

RC-RNC/Node B link: The transmission capacity of the RC - RNC link is 256 kbit/s per

RNC, for the RC - Node B link it is 64 kbit/s per Node B (recommended value:

128 kbit/s).

The RC detects and reports a communication break to the RNS within 2 minutes.

Information loss due to an outage of the RC-BSS/RNS link is overcome in less than 3

minutes. This includes all necessary alignments, e.g. alarm alignment and alignment ofthe state display.

File transfer

A parallel down- and upload between RC and one BSC/ RNC is possible. That means

e.g. during a SW-download it is possible to start an upload of e.g. a performance data

file.

The RC provides parallel processingof file transfer to/from

all connected BSCs

The minimum number of parallel file transfers is ten, the maximum number is only

limited by the system resources

all connected RNCs and Node BsThe maximum number of parallel file transfers (ftp sessions) is 50.

The bandwith guaranteed for ftp is

256 kbit/s between RC and each RNC

64 kbit/s between RC and each Node B (recommended value: 128 kbit/s)

Average time for a complete SBS software download(RC to BSCs) is 60 minutes.

Assumptions

12 MB for complete SBS SW, uncompressed

no upload is running simultaneously on the O interface

no overload situation at the BSC

notification / event report average:alarm notification 1 s

state change notification 1 s

measurement result notification 5 s

test reports etc 3 s

Tab. 3.2 Display response times


23/144

A50023-X4002-A2-3-7618 23



Average time for a complete database download(via file) is 5 minutes.

Assumptions

no upload is running simultaneously on the O interface

no overload situation on the BSC/ RNC/ Node B

Logging capacity

The database of the RC can hold online:

Assumption:

system with maximum configuration of network entities with normal report rate.

Events are not only spontaneous events coming from the connected BSSs/ RNSs, but

also events produced in the OMP itself (e.g. the records of an uploaded performance

data file have to be logged).

The logging capability satisfies an assumed peak transfer rate of 200 events / second,

during one minute.

GUI response times

Time for opening a window: less than 5 seconds, including display of the current states

or the alarm information.

Exceptions

operator defined windows (own views) may need a longer time for opening, depends

on their definition

windows that display attribute values in addition to the states (additionalGETnec-

essary)

RC startup and restart times

A first level of operation is supplied after less than 35 minutes. This includes the initital

reboot / restart and the first basic alignment (e.g. alarm alignment).

This first level of operation allows at least the starting of CLI sessions and the entering

of CLI commands.

The normal state of operation, especially including a valid state display, is reached in

less than 55 minutes.

Alarm event reports 4 weeks

State change event reports 2 weeks

Security data 8 weeks

Configuration changes, including changed parameter values 4 weeks

Test results 2 weeks

Performance Measurement event reports 1 week

Other events 1 week

Operator command history stack, user specific last 300 commands

All operator commands 2 weeks


24/144

24 A50023-X4002-A2-3-7618


OMP outage times

a) reboot of an OMP and restart of the necessary applications: less than 15 minutes

b) configuration and start of an installed backup-OMP (current RC SW-version) by us-

ing available backup-configuration data of a crashed OMP: less than 30 minutesc) installation, configuration (using back-up tape) and start of an OMP available in the

customer network in less than 2 hours

After those time intervals, the OMP is active and all configured connections to network

elements, OMTs and other management centers (e.g. NMC) are available. A full align-

ment is not included in this time interval.

The times in b) and c) do not necessarily include the complete restoration of the data

base - especially the logs - but all the data base structures are available and all the con-

figuration data the RC needs for proper operation is generated / restored.


25/144

A50023-X4002-A2-3-7618 25



4 Software Architecture

This section provides an overview of the software architecture of the Radio Commander.First, an overview of the basic principles and major features of the Radio Commander

software architecture is given in Basic Principles on page 25, followed by a more de-

tailed focus on the main software componentsin Main Elements on page 26.

4.1 Basic Principles

The software architecture of the Radio Commander is governed by the client-server

principleand strictly follows the object-orientedapproach.

The software has been designed with the following aims in mind:

Operability

Flexibility, Scalabilityand Reliability

High Performance

Continuity and Robustness

It complies with common interface and application software standards such as CMIP,

Q3, GDMO/ASN.1, SNMP, FTAM, CORBA, standard C++.

The whole system is modular and distributed, which increases its flexibility, scalability

and robustness.

As far as possible, the Radio Commander is based on standard software products.

This applies especially to the following parts of the software:

UNIX based operating system

protocol stacks database tools

communication software (TCP/IP,...)

products for file-handling, backup/restoration of data on the RC

window system (X-Windows / Motif)

name services (supports the use of DNS or NIS / NIS+ in an operator LAN)

commercial TMN platform

With regard to remote OMT connectivity, the Radio Commander is also compatible

with commonly used firewall products.


26/144

26 A50023-X4002-A2-3-7618


4.2 Main Elements

This section describes the main software elements of the Radio Commander. Fig. 4.1

illustrates how the Radio Commander software architecture is made up of logical layers.

The interfaces to BSS, RNS and NMC follow the Guidelines for the Definition of

Managed Objects (GDMO) and Abstract Syntax Notation One (ASN.1). For more details

see External Interfaces on page 121.

4.2.1 Logical Layers

Fig. 4.1 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 sys-

tems flexibility and robustness. They encompass the operating system and the TMN

platform as well as a number of tools.

The three top layersare comprised of the special functions:

Application Base Services provide universal servicesthat 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 Functionsof the Radio Com-

mander.

The top layer is the user interface.

Fig. 4.1 Software architecture, logical layers

Below is a short description of the main elements of the Radio Commander software.

The OMP and OMT operating system: Sun Solaris

Both the OMP and the OMT use powerful Sun Solaris as their operating system.

CORBA

Graphical User Interface (GUI)

Command Line Interface (CLI)Command Handler

FTAM Commercial Commercial TMN platform

DBMS PMI, MIS, MPA

User Interface

System Management

Application Base

Functions

Services

Configuration, Fault,Performance, Security, ...

Event Handler, File Handler,External Device Handling,Logging, Database Services

Operating System Solaris

3 top layers

2 base layers

Radio Commander

FTP

CMIP

Q3


27/144

A50023-X4002-A2-3-7618 27



It has multi-user/multi-tasking capability, a high portability level and communication

capacity. Solaris incorporates matured security concepts. It is highly configurable to

cover the redundancy requirements of different operators. In addition, it supports

numerous applications such as TCP/IP, X-Windows, etc.

TMN platform

The state-of-the-art, standard-compliant, commercial TMN platform for the Radio Com-

mander makes for improved functions, flexibility, reliability and scalability. It maintains

consistent information relying on:

GDMO/ASN.1 model

Management Information Tree (MIT)

GUI data

integrated logging manager

The Management Information Server is the heart of the TMN platform. Other important

features are the Management Protocol Adapters (MPA), which support different proto-

cols (CMIP, SNMP, RPC), and the Portable Management Interface (PMI), which

ensures location and protocol transparency for the applications.

CORBA

CORBA, the Common Object Request Broker Architecture, as defined by the OMGs

(Object Management Group) international standards, 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 inter-

face, which reduces application complexity.

With its simple and future-safe Interface Description Language (IDL) CORBA provides

operating system and programming language independent interfaces to all the

services and objects available on a network. CORBA thus reduces client-server

interdependence, laying the basis for improved scalability.

CMIP/Q3

CMIP/Q3 is the major commonly used network protocol standard for telecommunica-

tions management.

FTAM/FTP

The File Transfer, Access and Management and File Transfer Protocol are time-tested

and reliable commercial file transfer systems. They are used for GSM and UTRAN

management respectively.

DBMS

The Radio Commander relies on a reliable state-of-the-art commercial Relational Data-

base Management System (RDBMS) by Oracle.

Application Base Services

These services, which form the first layer of the special Radio Commander applications,

provide universally required functions accessible by all applications, such as Log-

ging (see chapter Log Management on page 107 for a detailed description of this func-

tion), file handling or safeguarding. This layer shows clearly how the Radio Commander

software itself is modular and distributed, making for more flexibility and robustness.


28/144

28 A50023-X4002-A2-3-7618


System Management Functions, SMF

The operation and maintenance functions are based on the System Management

Functions, which are in accordance with OSI definitions. The Radio Commander pro-

vides complete support of System Management Functions for all managed Siemensmobile radio networks, e. g. GSM and UTRAN. The follwing System Management Func-

tions are covered:

Configuration Management

Fault Management

Logging Management

Performance Management

Security Management

Software Management

Test Management

Trace Management

In addition, the Radio Commander offers a standard Q3 interface to the superior Net-work Management Center (NMC). Thus, System Management tasks issued at NMC lev-

el are mediated by the Radio Commander to be applied to the Siemens network

elements, see Fig. 4.2.

Fig. 4.2 Hierarchical structure of a Siemens GSM Mobile Radio Network,

logical function split

The uniformity of the System Management Function (SMF) modularity on every sys-

tem levelis one of the main design principles, ensuring reliabilityand flexibility.

The SMFs make up the Radio Commanders typical operation and maintenance func-

tions, covering various specific tasks such as Fault and State Management, Configura-

tion, Performance and Security Management. More detailed descriptions of the

System Management Functions can be found in the sections Configuration Manage-

System Management

Functions

Network Management Center(NMC)

Radio Commander

Network Elements

Q3(RC-NMC link)

StandardApproach

Fault

Configuration

Performance

Security

...


29/144

A50023-X4002-A2-3-7618 29



ment on page 57, State Management on page 65, Fault Management on page 71,

Test Management on page 81, Performance Management on page 83 and Software

Management on page 103.

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: For more detailed information see Working with the Radio

Commander on page 33.

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

4.2.2 O&M ToolSet and Open Interfaces

The Radio Commander supports advanced interfacing to 3rd party tools, for further pro-

cessing of information related to the network elements. For optimum integration and

ease of use the Radio Commander offers a set of value adding applications. The net-

work management functions of the Radio Commander are complemented with Fault

Management statistics (FM+), performance analysis (PM+), and network configuration

(CM+). Additionally the IMSI and cell traces (in TrM) and the result files of Smart Carrier

Allocation (SCA) are analyzed and presented (SCA visualization).

The operator is able to interact with any external tools through Radio Commanders

interface. The external tools can be grouped in two categories:

Network Quality Surveillance (short-term orientation)

These include Trouble Ticketing, Quality and Alarm Monitoring.

Network Optimization (mid to long-term orientation)

These include Network Planning and Information.

Fig. 4.3illustrates the two processes and the relevant functions

element management by Radio Commander, providing SMFs

supplementary functions, e.g. Network Configuration Test

service functions, e.g. Trouble Ticketing

The O&M ToolSet supports functions within each process.


30/144

30 A50023-X4002-A2-3-7618


Fig. 4.3 Process flow of operations, Radio Commander and tool environment

In addition to the proven GUI and CLI, the Radio Commander provides an easy to use

interface for post-processing, see External Interfaces on page 121. This interface fa-cilitates the access to network element data for typical post-processing tasks such as

Fault and Alarms management, and also Performance and Traffic measurements. Inter-

action with network planning tools is also supported.

As Fig. 4.4 shows, these interfaces allow communication with the Siemens tool world

via a common interface, and also to existing or upcoming 3rd party applications. Thus,

the Radio Commander can also easily interact with other commercial tools that are al-

ready installed in the operator's TMN environment.

Trouble

Ticketing

ExpertSystem for

Problem MgmtNetwork

Configuration(Consistency)

NetworkInformation

(Status Config)

NetworkOptimization

Circle

Network QualitySurveillance

Circle Network Elements

Radio Commander

Network

Planning

InventoryNetworkDatabase

Quality and

AlarmMonitoring

O&M

ToolSet


31/144

A50023-X4002-A2-3-7618 31



Fig. 4.4 Interfacing, Radio Commander and O&M ToolSet

Key features and benefits of the Radio Commander and the complementing tool

environment:

Radio Commander provides open standard interfaces (SQL, CORBA)

comfortable access to RC database information

Radio Commander acts as information broker for other applications and tools

central, flexible and standardized data distribution from the RC Radio Commander provides complete core functions (CM, FM, PM)

O&M ToolSet: The former stand-alone tool functions of CADDIE and MIXY are now

optional but fully integrated modules (CM+, FM+, PM+, Trace Management) of the

O&M ToolSet.

simplifies the operation environment, rationalizes interfaces

Evolution towards user friendly operation process

streamlines process and data flow (handling, ease of use)

TrM

FM+ PM+ CM+

SCAVisualization

O&M ToolSet

RC Core Functions

Database 3rdparty

Radio Commander

(CM, FM,PM data)

applications

(System Management Functions:e.g. CM, FM, PM)


32/144

32 A50023-X4002-A2-3-7618



33/144

A50023-X4002-A2-3-7618 33



5 Working with the Radio Commander

One of the most important aspects of any software product is its man-machine interface- the way users can interact with the system. The Radio Commander platform incorpo-

rates advanced support capabilities to meet the operators demands for professional

network element management.

The flexible and user-friendly man-machine interface of the Radio Commander features

three main elements, each with customization options:

Graphical User Interface (GUI), see below, with the powerful Network Editor, see

GUI Customization, Network Editor on page 46

Command Line Interface (CLI), see Command Line Interface on page 51

Online Help System, see Online Help System on page 54

5.1 Graphical User Interface (GUI)The Radio Commander has a Graphical User Interface which offers a feature-rich, cus-

tomizable and interactive user guidance to support operators in their daily tasks. Its

overall concept of user-friendliness and its aim to provide a clear-cut network over-

view leads to easy-to-use operating facilities. Most of Radio Commanders features are

individually customizable. This adaptation capability and flexibility allows for easy inte-

gration into existing software environments.

Immediately after the login, the Application Launcher is opened. Fig. 5.1 illustrates, how

this window allows the operator easy access to Radio Commander applications.

Fig. 5.1 Application Launcher of the Radio Commander as access point to Radio

Commander applications, example

Fig. 5.2gives a detailed view of the Radio Commander Applications window.

Application Launcher

Panel NavigatorNetwork Editor

Online Help

Command Line Interface

Command HistoryAlarm Monitoring

Network Management(Panel windows providinggraphical representationsof the objects)


34/144

34 A50023-X4002-A2-3-7618


Fig. 5.2 Radio Commander Applications window, that is the Application Launcher

of the Radio Commander, example

The Radio Commander supports different network management views. Customized

geographical maps, on different scales, represent the territorial structure of the network

(e.g. nation or region). On the maps the sites of the network elements are represented

by corresponding icons, with the current state of the element being indicated by the color

of the icons as well as by additional symbols on the icons. Node Bs are presented in a

list format.

The views are easily scalable. By simply pushing a button, the operator can quicklyscale the view in predefined steps.


35/144

A50023-X4002-A2-3-7618 35



Fig. 5.3shows a geographical map representation:

Fig. 5.3 Geographical map, example

To make the operators life easier the Radio Commander features a special

Maintenance View, which provides the operator at a glance with the key information onthe current network status, see Maintenance State View on page 69.

Each icon represents a network entity, a hardware unit or a functional unit. The back-

ground color of the icon indicates the current State of the represented managed object.

In addition, the respective Administrative State and the Stand-by State are indicated by

a separate symbol on the icon, if supported by the underlying entity.

To make things even easier for the operator, moving the mouse pointer over an icon will

automatically open a help view window. This help view displays the following informa-

tion:

label or symbolic name (if defined and activated)

managed object class (e.g. PCMB)

all relevant state attributes


36/144

36 A50023-X4002-A2-3-7618


The GUI provides an overview of all connected network entities (BSC, BTSE,

TRAU, RNC or Node B 1st platform, Node B 2nd platform) and links that are managed

by the RC.

Fig. 5.4 gives an example of a GSM BSS region panel, using Maintenance State Viewwith help view to present the relevant attributes of the managed objects:

Fig. 5.4 GSM BSS region panel with help view for state attributes, example

The presentation of the different hardware network entities is based on functional block

diagrams and rack layouts. Different icons and colors indicate the actual configuration

of the equipment and the corresponding alarm state, and relations between the man-

aged objects and their functional background. The embedding of hardware objects in

the corresponding rack layout helps to identify a faulty object easily. RNC hardware is

represented with stand-alone modules and groups of modules, that is shelves and partsof shelves.


37/144

A50023-X4002-A2-3-7618 37



Fig. 5.5 shows an example of anetwork entity sitepanel representing a GSM BTSE

site. The upper part of the panel contains leaf and summary icons e.g. for environmental

alarms (ENVA) and carrier frequencies (BTS). The lower part represents a detailed

physical view of the BTSE rack, containing dedicated icons for each physical hardware

unit.

Fig. 5.5 Network entity site panel with logical icons and rack layout, example

Similary to the administration of network elements, the Radio Commander also offers

advanced management capabilities for the RCs physical equipment, i. e. OMP, OMTs,

including redundancy, links and connected devices like printers.

The graphical presentation is realized according to the same principles as for the net-

work elements, also using aggregated maintenance views.


38/144

38 A50023-X4002-A2-3-7618


Fig. 5.6 shows an example of a Radio Commander window, displaying information

about all configured OMTs. The upper part of the panel contains dedicated icons for

general RC features and services.

Fig. 5.6 GSM OMC panel, example

The man-machine-interface is the focal point for all user activities. The system man-

agement functions are built around or even merged within this user interface for faster

and more effective overview and handling

Making configuration changes is easy: a few mouse-clicks on the appropriate icons is

all it takes to select the required actions. The same applies to all the other management

areas, for example to performance management. Not only is it easily administered via


39/144

A50023-X4002-A2-3-7618 39



the GUI, but with the help of the O&M ToolSet performance data can also be displayed

on the RC in a clearly arranged way.

Navigation tool

A special navigation tool supports the operator in navigating through the network hier-

archy.

Fig. 5.7 gives an example of a navigator window, presenting a GSM panel tree. The

window is split into the navigation area on the left and the object container on the right:

Fig. 5.7 Panel Navigator with GSM panel tree, example


40/144

40 A50023-X4002-A2-3-7618


5.1.1 Typical GUI Elements and Controls

The GUI of the Radio Commander is based on the X Window graphical operating envi-

ronment (X.11 Rel.5 and higher), the standard for UNIX platforms. The OSF/Motif Win-

dow Manager has been used in order to comply with standard operation guidelines.Also, the corresponding object libraries rely on OSF/Motif to obtain a common look and

feelfor the graphical user interface.

The Radio Commander GUI mainly uses the following standard elements:

pulldown menus

popup menus

dialog windows

icons

Panel window

A Panel window provides a graphical representation of the objects managed in the sys-

tem. Icons are used to represent managed objects, while colors or other visual effects(e.g. blinking) are used to indicate states and state changes. This is a quick way to

present information at a glance.

The Radio Commander comes with a predefined hierarchy of windows for different

network types: One standard hierarchy is optimized for GSM networks and one standard

hierarchy is especially defined for UTRAN.

At installation time operators can choose a standard view according to the configuration

of their network. The panels always contain all necessary elements for a full manage-

ment capability, offering rack-layouts, functional views and maps. The embedding of

hardware objects of network entities in a rack representation allows an easy identifica-

tion of a faulty element. The hardware objects of an RNC are embedded in a graphical

view of module groups and stand-alone modules.

Relations between managed objects and the functional background are illustrated with

block diagrams (e.g. the relations between TRAU and PCMA and PCMS objects are in-

dicated with lines/arrows between the ordered objects)

On top of the hierarchy is always the RC Region panel, followed by the panels for the

different network entities, with the network entity panels offering access to all kinds of

other Panel and List windows.

However the RC also offers the option of operator definable panels, which can be

stored in a new operator definable hierarchy (see GUI Customization, Network Editor

on page 46and Command Handling on page 41).

List window

In addition to Panel windows, the Radio Commander also offers an alphanumeric form

of data representation- the List window.

Just as with the panels, the lists provide information on the state a particular managed

object is in. However, the information in a List window is presented in form of a table,

with rows and columns.

To open a List window, the operator often only needs to click on the corresponding icon

in a panel. Other List windows are opened by selecting a command.

In addition to List windows for single objects operators can open many kinds of global

lists, e. g. the Global Alarm List.


41/144

A50023-X4002-A2-3-7618 41



All List windows offer a number of customizable functions such as searching, filtering,

sorting, even multilevel sorting, hiding and rearranging. Operators can save such set-

tings for their next sessions.

Lists can also display additional information that is not provided on the icons, e.g. chan-nel type. (see below 5.1.2 "Command Handling").

5.1.2 Command Handling

Services are provided directly at the icon (Panel window) or list entry (List window) con-

cerned, or in the menu e. g. of the Application Launcher.

All that operators have to do is right-click the icon, list entry, or menu Item to open the

context menu. The services available for this object are displayed and executable, tak-

ing into consideration the access rights that have been set for this particular operator in

the user profile.

Commands for ATM transport layer management can be started via CLI. All other O&Mcommands can be started via GUI or CLI.

To make command input and output as convenient as possible, the Radio Com-

mander provides dedicated forms for this purpose.

Such formsfeature

toolbar

object identification

attribute groups

specific representation for each data type

context sensitive help

Fig. 5.8 gives an example of command handling using panel windows. Clicking on an

icon in the related panel window opens a series of pop-up menus that offer the operator

all command actions that are allowed for the selected managed object.

A context menu might contain entries for single commands, script files or separate ap-

plications. Operators can add script files and separate applications for frequently per-

formed tasks, and arrange them in the menu as it suits them best. Thus they can tailor

the system to their needs.


42/144

42 A50023-X4002-A2-3-7618


Fig. 5.8 Command handling via panel window, example

Entry fields of input forms offer default and/or current values (forSETcommands), with

multiple selection possibilities. Before execution the RC checks the values and high-

lights faulty ones.

In input and output forms symbolic names are used, if defined and activated.Input and output forms can be opened in parallel, e. g. for comparison. Copy&Paste is

possible between open Service windows.

Operators can list their command history and choose and modify old commands for a

further execution. This command history contains all the O&M commands and started

services, both of GUI and CLI.


43/144

A50023-X4002-A2-3-7618 43



Fig. 5.9shows an example of a command history list window:

Fig. 5.9 Command History List, example


44/144

44 A50023-X4002-A2-3-7618


Fig. 5.10shows an example of an input form (CREATEoperation).

Fig. 5.10 Input form, example of a CREATE operation


45/144

A50023-X4002-A2-3-7618 45



Fig. 5.11 shows an example of an output form (GEToperation). As for the input form,

the appearance of the output form panels are also individualized depending on which

managed object the command was performed on:

Fig. 5.11 Output form, example of a GET operation


46/144

46 A50023-X4002-A2-3-7618


5.1.3 GUI Customization, Network Editor

What makes a GUI user-friendly is not only providing access to logically ordered func-

tions in a visually convincing layout and in a way that is easy-to-learn, but also to allow

its users to re-arrange and redefine things in the way that suits them best.Therefore, the Radio Commander offers a wide range of customizable features, such as

operator-definable network views

operator-definable comments for graphical objects

bullet mode for icons

desktop customization

flexible searching and filtering in lists

integration of operator specific CLI scripts

integration of applications

To help operators in their customization efforts the Radio Commander provides a

powerful tool - the Network Editor.

The Network Editor (NED) is a flexible application for GUI customization. All custom-

ization and configuration activities can be performed online, without requiring a software

or hardware reboot.

For basic GSM configuration changes it is also possible to run the Network Editor in

stand-alone mode, thus avoiding interference with online operations, and taking effect

at times when minimum interference with online operations is expected.

The Network Editor supports the operator with state-of-the-art graphic design meth-

ods, such as drag & drop, in the customization process.

The range of customization options offered by the Network Editor includes:

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 at-

tributes (line or icon), popup menus


47/144

A50023-X4002-A2-3-7618 47



Fig. 5.12shows Radio Commanders Network Editor window.

Fig. 5.12 Network Editor window, example

Operator-definable network views

The Radio Commander offers a predefined network view that contains all the configured

objects: rack layouts, functional views, maps.

In addition, every operator can define any number of new viewsby

defining new panels (with an operator-defined new hierarchy)

defining new summary objects and passive objects using the Network Editor


48/144

48 A50023-X4002-A2-3-7618


Fig. 5.13 shows a comparison of the standard hierarchy and an operator-defined hier-

archy:

Fig. 5.13 Operator defined hierarchy and standard hierarchy

It is also possible to link parts of the standard view to an operator-defined view.

The network view system is as flexible as can be: operators can choose which view

they want to work in, either at GUI session startup time or they can switch to it during an

active GUI session at any time.

Operator-definable comments for graphical objects

The operator can add, change and delete comments referring to a graphical object and

have that text displayed in a separate window. This feature lets operators use a desig-

nation for a particular object in a specific context that is easier for them to understand

and remember.

One use of this feature could be the addition of comments which give further explanation

of operators network specific information e.g. configuration details such as leased line

of company xy.

Bullet mode for icons

To keep network views as uncluttered as possible, the Radio Commander has intro-

duced the bullet mode for icons:

Bullet icons, which represent managed objects, open to full size only if their state dif-

fers from the default state. This allows the integration of a large number of icons in one

panel and presents only the relevant information to the operator.

As this feature depends largely on the preferences of the operator, it is fully

configurable:

bullet mode for specific panels

switching between bullet and normal mode

bullets for all managed objects

icon labels switched on or off

Operator defined panelscontains operator definedsummary objects and/orsingle managed objectsand passive objects

View summarysummarizesall operator defined parts

Operator defined viewsStandard network view

Operator defined panelcontains links to thestandard network tree


49/144

A50023-X4002-A2-3-7618 49



This feature allows operators a high degree of flexibility in designing the screen, so they

can get the information they need displayed in the way they prefer.

Fig. 5.14 shows a screen with only a one icon displayed in normal size. The mainte-

nance states obviously differ from the default state. All other managed objects are pre-sented by bullets as they are in their default states.

Fig. 5.14 Bullet mode, example


50/144

50 A50023-X4002-A2-3-7618


Desktop customization

Of course, operators can configure their own desktop workspace the way it suits them

best, using all the available GUI modification functions.

Flexible searching and filtering capabilities in lists

The data pertaining to the managed objects is kept in tables made up of rows and col-

umns. To make such tables easier to read for operators, they can hide the columns

they are not interested in and re-arrange the order in which the columns are presented

in the List windows. Sorting by field contents is possible, too.

The system provides flexible and powerful searching and filtering functions:

filtering by all object attributes

filtering based on columns, with the possibility of combining criteria using Boolean

operators (AND,OR,NOT)

filter settings can be saved for reuse, on an operators basis

The filtered data and data entries in general can then be sent to a printer or saved to file,on the hard disk or on an external device.

Integration of scripts

To make routine tasks faster, easier and less repetitive, the Radio Commander provides

the option to integrate operator-defined commands in the GUI. New commands such

as command scripts written for a specific routine task, can be added to the list of possi-

ble actions of an object and then be easily accessed from the GUI.

It is also possible to add common UNIX scripts or tools to a suitable menu in the Radio

Commander GUI.

Integration of applicationsThe Radio Commander even provides the option to integrate application programs that

are not part of the new Radio Commander software in its GUI

as an additional item in a popup menu

as an icon in the Application Launcherl

Examples of such applications are post-processing tools for performance measure-

ments, a Trouble Ticketing tool and mail or pager programs, which would then be easily

accessible for the operator from the Radio Commander GUI, see also O&M ToolSet

and Open Interfaces on page 29.


51/144

A50023-X4002-A2-3-7618 51



5.2 Command Line Interface

In addition to the object-oriented interaction model via the graphical user interface (GUI),

the Radio Commander also features a Command Line Interfa

Documents

Technical_Description_TED__RC_BR7.0.pdf