operations & maintenance principles ed10.pdf

Alcatel BSS

Operations & Maintenance

Principles

OMC Document

Reference Guide

Release B9

3BK 20954 AAAA PCZZA Ed.10

Status RELEASED

Short title O&M Principles

All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel/Evolium.

BLANK PAGE BREAK

2 / 116 3BK 20954 AAAA PCZZA Ed.10

Contents

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.1 GSM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.2 BSS/MFS and TMN Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1.2.1 BSS/MFS Telecom Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.2.2 BSS/MFS O&M Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.2.3 TMN Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

1.3 OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.3.1 OMC-R External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.3.2 OMC-R O&M Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.3.3 O&M Command Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241.3.4 Spontaneous Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241.3.5 Multiple LAN interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

1.4 Local Maintenance Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261.4.1 BTS Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271.4.2 BSC Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271.4.3 Transmission Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271.4.4 Compact TC Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281.4.5 IMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281.4.6 Universal Terminal Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

1.5 Object-oriented O&M Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291.5.1 Management Information Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291.5.2 Managed Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311.5.3 Manager and Agent Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321.5.4 SBL Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321.5.5 Mapping O&M Model to SBL Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

2 Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

2.1.1 Configuration Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.1.2 Types of Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

2.2 Radio Network Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402.2.1 High Speed Data Service (HSDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402.2.2 Assisted GPS (A-GPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402.2.3 Using O&M Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412.2.4 Data Flow in the Network Optimization Tool Chain . . . . . . . . . . . . . . . . . . . . . . . . . 412.2.5 Physical Organization of Network Optimization Tool Chain . . . . . . . . . . . . . . . . . 422.2.6 Unbalancing TRX Output Power per BTS sector . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

2.3 Parameter Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442.3.1 Radio Resource Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442.3.2 Cell Logical Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472.3.3 Default Parameter Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

2.4 Types of Working Contexts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532.4.1 SC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542.4.2 PRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

2.5 PRC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572.5.1 PRC Management Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572.5.2 PRC Content Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

2.6 Network Optimization Tool - A9156 RNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592.6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592.6.2 Network Optimization Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

2.7 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602.7.1 Inventory Data Retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612.7.2 Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

3BK 20954 AAAA PCZZA Ed.10 3 / 116

Contents

2.7.3 Remote Inventory Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622.8 Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

2.8.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632.8.2 Configuration Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642.8.3 BSS Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642.8.4 BTS Hardware Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662.8.5 Adding an MFS to a BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

2.9 Software Management and Database Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662.9.1 BSS Software Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672.9.2 MFS Software Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672.9.3 Database Backup/Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

2.10 Configuration Management Audits/Resynchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682.10.1 Audit Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692.10.2 Automatic Audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692.10.3 Operator-Initiated Audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

3 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

3.1.1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723.1.2 Fault Management Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733.1.3 Alarm Surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.1.4 A9157 LASER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

3.2 Alarm Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.2.1 Alarm Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.2.2 Fault Management Audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783.2.3 Alarm Management at Local Maintenance Terminals . . . . . . . . . . . . . . . . . . . . . . . 793.2.4 BSC/BTS/Transmission LMT Alarm Message Processing . . . . . . . . . . . . . . . . . . 793.2.5 IMT Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

3.3 Alarm Flow Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823.3.1 BSC Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823.3.2 BTS Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853.3.3 OMC Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

3.4 Fault Correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863.4.1 Hardware Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863.4.2 Scenarii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

3.5 System Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863.5.1 Recognizing the Symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.5.2 Using Equipment Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.5.3 Using Built-in Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.5.4 Troubleshooting by Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

3.6 Alarm Call Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

4 Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924.2 Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

4.2.1 Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 934.2.2 GSM Performance Management Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 934.2.3 GPRS Performance Management Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954.2.4 LCS Performance Management Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954.2.5 Reporting and Data Retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

4.3 Performance Management Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964.3.1 Campaigns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964.3.2 BSC Alerters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004.3.3 OMC-R Alerters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

4.4 Trace Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014.4.1 Trace Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014.4.2 Trace Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

4.5 Results Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

4 / 116 3BK 20954 AAAA PCZZA Ed.10

Contents

4.5.1 MPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054.5.2 NPA Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

5 OMC-R Security Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1105.2 Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1105.3 Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

5.3.1 Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1115.3.2 OADs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125.3.3 FADs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125.3.4 User Interface Profiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125.3.5 Operator Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1135.3.6 Terminal Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1135.3.7 Accessing Managed Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145.3.8 MFS Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

3BK 20954 AAAA PCZZA Ed.10 5 / 116

Figures

FiguresFigure 1: A BSS and MFS in the PLMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Figure 2: TMN Manager - Agent Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Figure 3: TMN Layered Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Figure 4: OMC-R External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Figure 5: BSS Local Maintenance Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Figure 6: TMN System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Figure 7: Manager and Agent Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Figure 8: Data Flow Between Planning, Optimization and Operation Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Figure 9: Architecture of the Optimization System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Figure 10: Basic Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Figure 11: SC and PRC Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Figure 12: PRC Life Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Figure 13: Stages of Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Figure 14: QoS Alerter Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Figure 15: Security Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Figure 16: MFS IMT Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

6 / 116 3BK 20954 AAAA PCZZA Ed.10

Tables

TablesTable 1: Terminal Functions and Affected Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Table 2: SBL Mapping for Managed Object Type Support Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Table 3: SBL Mapping for Managed Object Type Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Table 4: SBL Mapping for Managed Object Type O&M Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Table 5: SBL Mapping for Managed Object Type Support Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Table 6: SBL Mapping for Managed Object Type Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Table 7: SBL Mapping for Managed Object Type Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Table 8: Type of BTS and the Applicable FHS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Table 9: Hardware Configuration Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Table 10: Configuration Management Audit Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Table 11: Fault Management Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Table 12: Available Alarm Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Table 13: Equipment Responsible for Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Table 14: LMT Alarm Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Table 15: Campaign Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Table 16: Performance Measurement Campaign Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Table 17: Default Counter Storage Durations for MPM and NPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

3BK 20954 AAAA PCZZA Ed.10 7 / 116

Tables

8 / 116 3BK 20954 AAAA PCZZA Ed.10

Preface

Preface

Purpose The Operations and Maintenance Principles provides a conceptual overview ofthe O&M strategy used in the Alcatel BSS.

It introduces users to the O&M functions available in the BSS and the OMC-Rnetwork.

Whats New In Edition 10Improvements were made to External OMC-R Cells (Section 2.3.2.2) dueto system evolution.

In Edition 09Updates in chapter Multiple LAN interfaces (Section 1.3.5).

Update of section External OMC-R Cells (Section 2.3.2.2) with informationabout OMC-R adjacency consistency.

In Edition 08Section OMC-R (Section 1.3) has been improved.

In Edition 07MPM application is only optionally installed on the OMC-R. See more detailsin OMC-R Alerters (Section 4.3.3).

An improvement for customer network security allow a split of IP traffic inthis network. More about this optional feature can be found in Multiple LANinterfaces (Section 1.3.5).

External Alarm Box has been introduced for A9130 MFS and A9130 BSCEvolution.

In Edition 06A new feature allows the usage of TREs at their real power. More details inUnbalancing TRX Output Power per BTS sector (Section 2.2.6).

In Edition 05

3BK 20954 AAAA PCZZA Ed.10 9 / 116

Preface

The feature Unbalancing TRX Output Power per BTS sector has been added inUnbalancing TRX Output Power per BTS sector (Section 2.2.6)

In Edition 04Additional details about CITRIX on RNO and LASER have been included insection Universal Terminal Concept (Section 1.4.6).

In Edition 03Default Parameter Customization (Section 2.3.3) section has been updated:

A new parameter object type has been added: EXTERNAL CELL

parameters

More detailed description for update the default parameters

The link to the "Network Admin Handbook" has been removed.

Information concerning improvements in the utilization of the CITRIXMetaframe was added in Universal Terminal Concept (Section 1.4.6).

In Edition 02B9 improvements related to security

FADs are allowed to be modified (Access Rights (Section 5.3))

New chapter regarding Password Policy (Section 5.3.1)

Changes regarding FADs (Section 5.3.3)

System Administrators permissions to create, modify and delete FADs,inOperator Profiles (Section 5.3.5)

New chapter regarding Terminal Profiles (Section 5.3.6)The following features in the B9 package 2 were added:

VGCS feature and eMLPP improvements in Configuration Management

(Section 2) and in Performance Management (Section 4)

MFS Remote Inventory in Remote Inventory (Section 2.7)

Better Integration of IMT in IMT (Section 1.4.5) and in FADs (Section 5.3.3)to add the four new FADs to this section.

In Edition 01The following features in the B9 package 1 were added:

Default Parameter Customization (Section 2.3.3)

Radio Measurement Statistics (Section 4.2.2.4)

Enhanced RI interface: export of one csv file per OMC-R in Process

(Section 2.7.2).

10 / 116 3BK 20954 AAAA PCZZA Ed.10

Preface

Audience This manual is for:

Network managers who require a working knowledge of the Alcatel BSS

O&M

Network planners

Support and service engineers

Network operators.

Assumed Knowledge The reader must be familiar with the:

Basic architecture and functions of GSM/GPRS networks

Alcatel BSS

BSS System Introduction and BSS System Description documents.

3BK 20954 AAAA PCZZA Ed.10 11 / 116

Preface

12 / 116 3BK 20954 AAAA PCZZA Ed.10

1 Introduction

1 Introduction

This chapter introduces the basic concepts of O&M in the Alcatel BSS/OMC-Rand the architecture used to implement it.

3BK 20954 AAAA PCZZA Ed.10 13 / 116

1 Introduction

1.1 GSM OverviewGSM networks allow a mobile station to make calls to another mobilestation, or to a subscriber in the PSTN. GPRS allows packet-switched datatransmission. The BSS allows both circuit-switched transmission for voice andpacket-switched transmission for data.

The radio portion of the PLMN comprises a number of BSS. Each BSS providesboth telecom and O&M functions to the PLMN. Operators can define multiplePLMN for network sharing. A BSS consists of one BSC plus all NetworkElements that it controls.

The MFS fulfills the functionality for GPRS as well as SMLC functions for LCS.

In the Alcatel solution, the MFS implements:

the GSM-defined GPRS Packet Control Unit (PCU) function for GPRS

the SMLC function for LCS.

The architecture of the BSS and MFS network elements and their logicalinterfaces are shown in the following figure.

MobileStation

BTS

BTS

BTS

AtermuxInterface

A InterfacePSTNMSC

NetworkSubsystem

FixedNetwork

To other BSSs

Base Station Subsystem

Public Land Mobile Network (PLMN)

IP Interface

BSC

Interface SGSNGb Interface

OMCR

Gs Interface

TC

MFS

Gateway GPRS

Support Node(GGSN)

for CS traffic

Public Data Network (PDN) for PS traffic

X.25/IP

Figure 1: A BSS and MFS in the PLMN

The BSS is a distributed system consisting of the following subsystems:

BSC

BTSs

MFS

TCs.

The BSS/MFS interacts directly with the mobile station and with the MSC. TheOMC-R is not a part of the BSS/MFS, but provides the command and control

14 / 116 3BK 20954 AAAA PCZZA Ed.10

1 Introduction

facility for operation, configuration and maintenance of the BSS/MFS network.A single OMC-R typically serves a number of BSSs plus all the MFSs that areconnected to these BSS.

The SMLC is a functional NE in the BSS that is integrated into the MFS andconfigured by the OMC-R. As the MFS provides the GPRS services to severalBSCs, the SMLC performs location services for the same set of BSCs.

GSM/GPRS networks operate in four different frequency bands, centeredaround 850 MHz (GSM 850), 900 MHz (GSM 900), 1800 MHz (GSM 1800)and 1900 MHz (GSM 1900).

The Alcatel BSS supports the following multiband network configurations:

BSS with a mix of GSM 850 and GSM 1900 cells

BSS with a mix of GSM 850 and GSM 1800 cells

BSS with a mix of GSM 900 and GSM 1800 cells.

Any monoband network configuration involving one of the above frequencybands is supported.

For more information about the BSS and the MFS, and their place in thePLMN, refer to the:

BSS System Description

Evolium A9135 MFS Description

A9130 MFS Evolution Functional Description

A9130 MFS Evolution Hardware Description.

1.2 BSS/MFS and TMN FunctionsThe BSS/MFS performs two major classes of function:

Telecom functions

O&M functions.

The telecom and O&M resources are modeled as managed objects. Eachsubsystem in the BSS/MFS is composed of a number of managed objects (seeManaged Objects (Section 1.5.2) for more information).

1.2.1 BSS/MFS Telecom Functions

Telecom functions are the basic activity of the BSS/MFS. They are concernedwith establishing, maintaining and clearing calls and packet data flow, and withkeeping track of the mobile station during calls and when in idle mode. Theyare done in real time, and must be performed rapidly and efficiently.

The main BSS/MFS telecom functions are to:

Establish the radio link with the mobile station

Page the mobile station to receive a mobile-terminated call

Control and maintain the radio link (Power Control, Handovers, etc.)

Cipher, if required

3BK 20954 AAAA PCZZA Ed.10 15 / 116

1 Introduction

Transport bearer services (circuit-switched and packet-switched traffic)

Encode/decode speech

Transfer packet data.

1.2.2 BSS/MFS O&M Functions

O&M functions support the BSS/MFS telecom functions and enable theBSS/MFS to maintain its reliability and efficiency.

O&M functions fall into two major areas:

Operating the network - this includes monitoring performance and reacting

to problems

Tuning the network - this includes configuring hardware and software for

upgrades or to improve system performance.

The O&M functions implemented in the BSS/MFS are managed by operatorsusing terminals. The main O&M control station is the OMC-R (see Figure 1).Portable Local Maintenance Terminals (LMTs) can be used locally to managethe O&M functions for the BSC, BTS, transmission and MFS.

The O&M functions and operations provided are:

Performance Management

Fault Management

Configuration Management

Low-level maintenance via LMTs.

1.2.2.1 Performance ManagementPerformance Management allows you to monitor the efficiency of the systemand the telecom services. It is controlled entirely from the OMC-R and providesmeasurements and statistics about various traffic events and resource use inthe BSS/MFS.

1.2.2.2 Fault ManagementFault Management allows you to supervise and to repair the network whenanomalies occur. It does this through a sequence of steps from detection toreporting and recovery. These are carried out by all the BSS subsystemsand the MFS, and are reported to the operator at the OMC-R or at anotherdesignated maintenance site.

1.2.2.3 Configuration ManagementConfiguration Management is the process of viewing and controlling networkresources.

Configuration Management allows you to:

Configure the BSS/MFS hardware and software when it is first installed

Change the network by adding, deleting, or moving network entities

Upgrade to new hardware or software

Change equipment and telecom parameters to improve system performance.

16 / 116 3BK 20954 AAAA PCZZA Ed.10

1 Introduction

1.2.2.4 Low-level Maintenance via LMTsLMTs are used when performing maintenance and commissioning tasks at theequipment site. LMTs are connected directly to the equipment. The operationsavailable at the LMTs act only on the local hardware, not on logical resources.

1.2.3 TMN Architecture

In existing GSM networks, the communication protocols for networkmanagement between the OMC-R and the BSS/MFS are proprietary.

To facilitate management of networks comprising equipment from differentmanufacturers, the ITU-T and 3GPP have issued recommendationsdefining an architecture for the management of telecom networks called theTelecommunications Management Network (TMN).

The TMN supports a wide variety of management functions. These cover theplanning, installation, operation, administration, maintenance and provisioningof telecommunication networks and services.

The TMN contains two functional layers for equipment and networkmanagement. The OMC-R provides a clear split between these two layers byintroducing a radio network layer and an equipment management layer.

1.2.3.1 Open Systems InterconnectionTMN follows an object-oriented approach based on the OSI systemsmanagement model. The OMC-R has adopted this same approach for itsmethodology.

1.2.3.2 OMC-R/Network Management CenterStandardized network management as described above is provided throughthe OMC-R and an NMC. Some network operators choose to have an NMCsupervising one or more OMC-Rs in a hierarchical relationship, represented bythe Management Information Tree (MIT).

1.2.3.3 TMN ApplicationAlcatel monitors and manages the network via an advanced, distributed,object-oriented network management platform. This platform is called ALMAP.ALMAP conforms to the TMN and OSI standards.

ALMAP is completely object-oriented: resources of the TMN system aremodeled as managed objects (see Managed Objects (Section 1.5.2) formore information).

ALMAP and its TMN applications are organized according to the TMNmanager-agent concept (see the figure below) defined in the TMN standardITU-T M.3110. An application component can act as a manager and as anagent.

Operations

NotificationsManager Agent

Perform Operations

Notifications Emitted

ManagedObjects

Managed System

Managing System

Figure 2: TMN Manager - Agent Concept

3BK 20954 AAAA PCZZA Ed.10 17 / 116

1 Introduction

The fully-ordered hierarchy of managers and agents guarantees themaintainability of TMN systems:

An agent is a component of the TMN system representing a set of managed

objects for the purpose of management supervision. It receives and handlesrequests from one or more managers for operations defined for its managed

objects: creation or deletion, retrieval or modification of attributes andtriggering of actions. The agent also emits notifications in case a managed

resource changes state or detects an error

A manager is a component of the distributed TMN system that controlsand monitors the network agents. On behalf of the operator, it can send

management operations to the network agents and report events andalarms received from the network agentsManaged objects are organized in a tree-like directory structure: theManagement Information Tree (MIT). A manager can issue operations onindividual objects in this directory, or even on multiple objects by specifyinga sub-tree (scope) and selection criteria (filters).

1.2.3.4 Logical Layered ArchitectureThe TMN defines a layered architecture in which each layer deals with differentaspects of network management, as shown in the following figure.

OMCR

BTS BSC MFS

NMC/OMCR

Business Management

Service Management

Network Management

Element Management

Network Element

TC

Figure 3: TMN Layered Architecture

As management layers rely on lower layer functionality, the performance ofthe higher layers depends on the support they get from the lower layers.The supporting basis of the pyramid determines the quality of managementinformation at the top.

Implementing the TMN management hierarchy ensures that ALMAP providesextensive support at all the TMN layers.

18 / 116 3BK 20954 AAAA PCZZA Ed.10

1 Introduction

1.3 OMC-RThe OMC-R is based on the ALMAP platform. This platform offers a set ofcomponents that provide TMN functions and platform services.

In compliance with GSM specifications, the A1353-RA OMC-R is concernedwith element management and subnetwork management of the wholeBSS/MFS network system, i.e., all BSCs, BTSs, Transcoders, transmissionsystems and MFSs.

For more information about the OMC-Rs architecture, see System Architecturein the A1353-RA Getting Started document.

1.3.1 OMC-R External Interfaces

The figure below shows:

The Q3 interface

Other A1353-RA external interfaces.

A1353RA

Radio Network Level FilebasedExternal

Interfaces

BSSNE Level Q3ExternalInterface

Export FilesTransfer

Import FilesTransfer

NMC

CMIS OperationResponses

File UploadControl

CMIS OperationRequests

Figure 4: OMC-R External Interfaces

1.3.1.1 Q3 InterfaceSome networks have NMCs to help monitor the network. The OMC-R needsto exchange network information with the NMC reliably and efficiently. Thestrategy Alcatel has chosen to provide this is via a Q3 interface.

The Q3 interface is derived from an information model based on standards,particularly GSM 12.20 and M.3100. This ensures that the Q3 interfaceperforms real-time TMN supervision and control. Spontaneous and self-routingevents allow an upper TMN layer to be warned about changes in alarmsituations, attribute values, states, creations and deletions.

3BK 20954 AAAA PCZZA Ed.10 19 / 116

1 Introduction

1.3.1.2 Other External InterfacesThe OMC-R has a number of other external interfaces. These are basedon ASCII and binary files which can be exported or imported using eitherFTAM or FTP. These interfaces differ according to their domain (for example,Configuration Management, Fault Management, etc).

An example of an external interface is the A1353-RA ConfigurationImport/Export (ACIE) interface. This enables the operator to:

Import the whole, or part, of the externally accessible A1353-RA radionetwork level configuration data, view the OMC-R database, and modify

Radio Configuration

Export the whole (or part for an external application other than the NMC)

of the externally accessible configuration data - either at network level or

for a given BSS network element, view the OMC-R database, and modifyRadio Configuration.

For further information about:

Import / export file formats, refer to the OMC/BSC HW/SW Files Format

Specification

Exporting Performance Management data, refer to OMC-R Export Interface

for PM Data

Using the ACIE, refer to ACIE Supplementary Information.

20 / 116 3BK 20954 AAAA PCZZA Ed.10

1 Introduction

1.3.1.3 SNMP AgentAlcatel does not deliver an SNMP Agent for OMC-R, but customers can installone on their machine. The following conditions and rules must be applied wheninstalling an SNMP Agent:

The SNMP Agent software must be installed in the /alcatel/var directory.

The recommended maximum CPU / memory occupancy / used disk space

allowed for an SNMP Agent is:

Maximum CPU used by SNMP Agent: 3%

Maximum RAM used by SNMP Agent: 3%

Maximum disk used by SNMP Agent: 300 MB

SNMP Agent installation is not supported by Alcatel. The Solaris and

third party software patch level defined by Alcatel must not be changed

when introducing the agent.

Software migration to a new Alcatel BSS release will not take into account

any installed SNMP Agent.

Alcatel does not commit to any software corrections or evolutions linked tothe introduction of an SNMP Agent.

In case of problems in the OMC-R system, Alcatel cannot be held

responsible for problems due to the introduction of an SNMP agent. In theevent of an OMC-R system problem, regardless of the origin, Alcatel can

request the removal of the SNMP Agent in order to facilitate troubleshooting.

In order to ensure security, the SNMP Agent must include state-of-the-art,anti-hacking protection.

3BK 20954 AAAA PCZZA Ed.10 21 / 116

1 Introduction

1.3.2 OMC-R O&M Functions

The purpose of the OMC-R is to control the O&M functions of the BSS/MFS. Itcontains O&M application programs for this purpose. The OMC-R connects tothe BSS over an X.25 link, and to the MFS over an IP network.

The OMC-R also provides administrative and mediation functions such asmediation between the Alcatel BSS and an NMC over the Q3 interface.

For more information on the OMC-R terminal, refer to Getting Started with theA1353-RA OMC-R in the A1353-RA Getting Started document.

An overview of the OMC-R O&M tasks is given below.

1.3.2.1 Configuration Management TasksConfiguration Management tasks include:

Managing GSM radio resources (cells, carriers, channels...)

Managing transmission equipment (configuration of transmission path fordifferent types of data) at various levels

Supporting the network for O&M communications in GSM. This is based onX.25 for the BSC and IP for the MFS

Managing the SS7 connection in the system

Managing different support activities such as alarm management, logs...

Managing system date/time (display and modify)

Managing BSS/MFS software (download, activate, and file and versioncontrol)

Managing BSS/MFS database backup and restore

Using a proprietary application for OMC-R configurations to backup andrestore data across an entire network of computers

Managing logical configuration data

Managing hardware configuration (add, delete, extend, reduce, display,setup and reconfigure the network)

Managing the Control Stations and MFS database

Generating reports about system activity.

22 / 116 3BK 20954 AAAA PCZZA Ed.10

1 Introduction

1.3.2.2 Fault Management TasksFault Management tasks include:

Handling BSS equipment and resources (monitor states and execute

operator commands)

Managing BSS tests (diagnostic tests and audits)

Handling BSS alarms (states and history)

Generating alarm reports

Performing miscellaneous alarm maintenance functions from the IMT, e.g.:

View the alarm history file

Enable/disable the External Alarm Management function, so that if the

MFS generates an external alarm, it is displayed in the IMT (for A9135MFS) or at OMC-R (for A9130 MFS trough the External Alarm Box)

View MFS equipment and associated alarm status

Providing files in formats compatible with optimization tools.

1.3.2.3 Performance Management TasksPerformance Management tasks include:

Managing measurement campaigns (create, unlock, lock, delete)

Managing raw counters (QoS alarms)

Defining and supervising counter thresholds

Displaying measurement campaign results

Managing Call and IMSI traces.

3BK 20954 AAAA PCZZA Ed.10 23 / 116

1 Introduction

1.3.3 O&M Command Flows

O&M commands pass between BSS/MFS network elements and the OMC-Ralong three paths between the:

OMC-R and the BSC

BSC and the BTSs

OMC-R and MFS.

1.3.3.1 OMC-R / A9120 BSCO&M information is passed between the OMC-R and the BSC, usingCMISE and CMIP. CMIP is the OSI network management protocol over anX.25 connection. The X.25 connection also passes software uploads anddownloads, Performance Management result files, and BSC Hardware auditfiles to the OMC-R using the FTAM protocol.

A second physical X.25 connection is also used for communication with theBSC, either:

Simultaneously with the primary X.25 link

To load balance the flow between the OMC-R and BSC when the primarylink is busy

As a fallback link.

1.3.3.2 OMC-R / A9130 BSCThe O&M information is passed between the OMC-R and the A9130 BSC usingthe IP protocol. BSC A9130 allows two different ways for connection withOMC-R: over direct IP network or over Ater and IP network.

The IP connection passes software uploads and downloads, PerformanceManagement result files, alarms, and BSC Hardware audit files to the OMC-R.Protocol used for file transfer is FTP.

1.3.3.3 BSC/BTSThe O&M protocol between the BSC and the BTS uses the GSM standard08.59 (O&M signaling transport layer) header. This header handles thesequencing and encapsulation of data.

1.3.3.4 OMC-R/MFSNetwork Management operations take place on a Q3 protocol over IP. Networkelement management operations are via remote emulation of the IMT.

1.3.4 Spontaneous Notifications

Notifications such as alarms and events are spontaneous. Alarms aregenerated due to changes in the operation of the system. They are not inresponse to an action invoked by the OMC-R. These notifications are reportedover CMIP.

AlarmsAlarm-start and alarm-end commands use two messages. The alarm arrivesat the OMC-R as an alarm report. The OMC-R sends an acknowledgmentto the network element.

Event Changes

24 / 116 3BK 20954 AAAA PCZZA Ed.10

1 Introduction

Event messages are spontaneous. They inform the OMC-R of changes tothe managed object state.

1.3.5 Multiple LAN interfaces

Multiple LAN Interface improve the security of customer network, splittingthe traffic in two:

OMC network traffic (between Master/Agent/HMI/workstation/toolchain)

Network elements related traffic (between OMC Master/Agent/HMI and

A9135 MFS / A9130 MFS Evolution / BSC Evolution)

OMCR Agent

OMCR Master

OMCR HMI

RNO NPA LASER

MFS BSC Evolution

NMC is classified as OMC traffic.

This split can be configured either by adding a new Ethernet board, or usingmultiple IP addresses on the same port, if the HW allows it.

Each Master/Agent/HMI will have two different IP addresses and two differenthostnames. The IP address associated with NE network, will be used as OMCMaster/Agent IP address from NE. The IP associated with OMC network, willbe used from OMC network (Agent, HMI, toolchain, etc).

If the client is using a dedicated network interface for backup, he must take careto not overlap IP networks used or overwrite network interfaces configuration.

More information about this subject can be found inA1353-RA NetworkAdministration Handbook.

3BK 20954 AAAA PCZZA Ed.10 25 / 116

1 Introduction

1.4 Local Maintenance TerminalsAn LMT is used when performing maintenance tasks at a subsystem site.Tasks performed using an LMT affect mainly the subsystem to which it isconnected. LMTs do not provide the range of facilities and control of O&Mfunctions possible as when using the OMC-R. For the MFS, remote emulationof some IMT functions is possible at the OMC-R.

LMTs are connected to the main subsystems in the BSS, as shown in thefollowing figure.

BTS BSC

from/to OMCR

MSC

BTS Terminal

IMT

TC

X.25 or RS232

RS232

MFS SGSN

Transmission Terminal

Ethernet

RS232

X.25/ IP

A9120 BSC Terminal

IP

A9130 BSC Terminal

Figure 5: BSS Local Maintenance Terminals

The LMTs (the BSC terminal, BTS terminal, transmission terminal and theIMT) connect directly to local O&M controllers within each subsystem. It isthe local O&M controller that provides access to the O&M functions withinthe subsystem. Software running in the local terminal communicates withthe local O&M controller.

The IMT software can be accessed either from the IMT PC or from OMC-R.

The LMT for A9130 BSC Evolution can run on any PC connected in the BSCnetwork, or in the network of the OMC-R on that the BSC is connected to.

26 / 116 3BK 20954 AAAA PCZZA Ed.10

1 Introduction

The following table gives a summary of the functions available with eachterminal and the subsystems that are affected.

FunctionBTSTerminal

BSCTerminal

Transmission Terminaland Compact TCTerminal IMT

UniversalTerminal

Administration BTS BSC Transmission MFS OMC-R

ConfigurationManagement

BTS * BSS * Transmission * MFS ** OMC-R

FaultManagement

BTS BSC, BTS Transmission MFS OMC-R

PerformanceManagement

- - - - OMC-R

*: Configuration Management tasks performed with local terminals are limited to equipment management.

** : The IMT is used for configuring the MFS in the commissioning phase and for managing site parameters, equipmentand software domains.

Table 1: Terminal Functions and Affected Subsystems

The administration functions control basic facilities such as operatorlogin/logout, access to the O&M functions and access to the terminalsoperating system. In the case of the OMC-R, the operating system is UNIX; forthe other terminals, it is a Windows(TM)-based graphical interface.

1.4.1 BTS Terminal

The BTS Terminal performs configuration and fault management tasks thataffect only the BTS via a Windows(TM)-based graphical interface (see Table 1).

For more information about the BTS Terminal and the tasks that can beperformed, refer to the BTS Terminal User Guide.

1.4.2 BSC Terminal

The operator can use the BSC Terminal to perform fault and configurationmanagement tasks that affect the BSC and the Transcoder, via aWindows(TM)-based graphical user interface (see Table 1).

Syntax and semantics checks are performed by the BSC Terminal. The BSCsO&M software executes the command and sends a result report to the BSCTerminal. User reports are always saved on the BSC Terminal disk. Resultscan also be displayed as soon as they are received by the BSC Terminal.

Some transmission-handling functions are also available using the BSCTerminal. For more information about the BSC Terminal and the tasks thatcan be performed, refer to the BSC Terminal User Guide or A9130 BSCEvolution Terminal User Guide.

1.4.3 Transmission Terminal

The Transmission Terminal is primarily used for installation and commissioningtasks. These are performed via a Windows(TM)-based graphical user interface(see Table 1).

3BK 20954 AAAA PCZZA Ed.10 27 / 116

1 Introduction

For more information about the Transmission Terminal and the tasks that canbe performed, refer to the Transmission Terminal User Guide.

1.4.4 Compact TC Terminal

The Compact TC Terminal is primarily used for installation and commissioningtasks. These are performed via a Windows(TM)-based graphical user interface(see Table 1).

For more information about the Compact TC Terminal and the tasks that can beperformed, refer to the Evolium A9125 Compact TC Terminal User Guide.

1.4.5 IMT

The IMT is used for fault management, hardware and software management,and modification of telecom parameters on the MFS. The IMT uses aWeb-based browser. Some of these tasks can also be accessed from theOMC-R terminal. Others that are already generally available on the OMC-R,such as alarm management, can not be accessed. However, not all the MFStasks available at the OMC-R can be accessed from the IMT. Two sessionsof the IMT can be in use at the same time. For example, if there is one IMTconnected to the MFS, then only one IMT window can be opened at theOMC-R. With parallel access, up to eight users can be connected in a session,depending on the type of tasks being performed.

For more information about the IMT and the tasks that can be performed,refer to the:

Online help provided for the IMT

Evolium A9135 MFS IMT User Guide.

Evolution A9130 MFS IMT User Guide

1.4.6 Universal Terminal Concept

The Universal Terminal Concept allows users to log in, access applications,and perform management tasks from a terminal that supports the CITRIXmetaframe client. It is not dedicated to a specific OMC-R and enables accessto several OMC-Rs.

Note: CITRIX(TM) is now available with RNO and LASER.

The Universal Terminal Concept can be implemented on:

Windows(TM) PC terminals

LINUX (TM) PC terminals

UNIX(TM) terminals.

CITRIX Metaframe software is based on Client/Server paradigm.

CITRIX server for OMC-R can run on all the HMIs and master workstationssupporting users. The maximum number of users defined per HMI and

Master, if the CITRIX Metaframe Server is installed, is reduced by one,

compared to HMI or Master without CITRIX server.

28 / 116 3BK 20954 AAAA PCZZA Ed.10

1 Introduction

CITRIX server for RNO and LASER must be installed on PC machines withrunning Windows Server 2003. RNO or LASER clients must be installed

and published in top of this configuration.

CITRIX clients are installed on UNIX(TM) workstations or PCs.

The CITRIX client, regardless of the platform (UNIX(TM), Windows(TM),LINUX(TM)) is configured by the customer. A malfunction of the CITRIXMetaframe client is the responsibility of CITRIX. The navigation from oneOMC-R session to another OMC-R session is provided by Windows andCITRIX.

UNIX(TM) terminals support offers an alternative to using CITRIX with thefollowing:

The ssh command and export of the X.11 display (from UNIX(TM) or

LINUX(TM))

The X.11 client (whatever the platform) must be compatible with X.11 serverversion 6.4 (installed on the OMC-R)

1.5 Object-oriented O&M ModelThe OMC-R uses the TMN approach for managed objects. O&M applicationsvisible to the operator are object-oriented. Also, the topology the operator seesand follows is composed of managed objects.

1.5.1 Management Information Tree

TMNs object-oriented hierarchical structure is represented in the figure below.It graphically defines the respective management responsibilities in the threemain levels of the MIT:

Network management and network element management

Q3 Interface

Network element.

The ability to pass information between these TMN levels is defined by asuite of protocols called Q Interfaces.

3BK 20954 AAAA PCZZA Ed.10 29 / 116

1 Introduction

OMCR

BSC

BTSBTS

BTS

OSSDomain

Q3 Interface

Q3 Interface

BSSDomain Abis

AbisAbis

Network Management

Network Management at Regional LevelNetwork Element

Management

Network Element Management

NMC Operator (Network Supervisor)

OMCR Operator (Resource and Equipment

Management)

Maintenance Technician (Equipment Management)

NMC

Q3 Interface

MFS

Figure 6: TMN System Architecture

1.5.1.1 Network Management and Network Element ManagementSmall- to medium-sized GSM networks are usually controlled by a singleOMC-R. Larger networks sometimes have an NMC which provides a higherlevel of network supervision than the OMC-R.

1.5.1.2 Q3 InterfaceThe NMC communicates with the OMC-R using the TMN Q3 standard interface,as shown in the figure above.

The Q3 interface defines a set of communication protocols for the path betweenthe NMC and the OMC-R of a TMN. This protocol suite complies with ITU-Trecommendations.

1.5.1.3 Q3 MultimanagerAlcatels Q3 Multimanager feature allows the OMC-R to communicate overthe Q3 interface with multiple NMCs. This enables the network operator toconcentrate specific functions on each of several NMCs.

1.5.1.4 TMN Equipment DomainsThe three levels described above are further grouped into two EquipmentDomains:

The OSS, which contains the NMC and the OMC-R

The BSS, which contains the MFS, the BSC, and the BTS subsystems

(network elements).

30 / 116 3BK 20954 AAAA PCZZA Ed.10

1 Introduction

1.5.2 Managed Objects

The resources which comprise the TMN environment, and the managementfunctions performed on such resources, are known as managed objects.

The object-oriented approach is a prerequisite in the OSI management model.The managed object is used to represent elements of the TMN environment onthe Q3 interface in terms of system resources. This concept is also used torepresent the activities of management function blocks performed on theseresources.

A managed object is a single entity containing both the code and the datawhich control the managed network resource. It is composed of a set ofattributes, actions that can be performed and notifications that can be omitted.Attributes have values which are typically items of information that thenetwork management framework needs to manipulate, such as configurationparameters of logical cells controlled by a BTS.

In Alcatels network management model, a managed object can be a physicalentity, such as a BSS, BTS, BSC, or a hardware module within one of theseentities. It can also be a logical entity, such as a program or program routineswhich implement communication protocols.

Management Operations The operations that manipulate attribute values must be directed at themanaged object to which the attribute belongs. The managed object performsthe operations.

The operations are:

Get attribute value

Set attribute value

Add attribute value

Remove attribute value.

An attribute value can consist of more than a single value; it can have astructure encompassing a set of values. Here, the Add and Remove operationscan add or remove members of such a set.

There are also Create and Delete operations which are defined to act directlyon managed objects.

3BK 20954 AAAA PCZZA Ed.10 31 / 116

1 Introduction

1.5.3 Manager and Agent Communications

The management of a telecommunications environment is performed by aninformation processing application. The manager, which runs this application,issues directives to its agent and receives notifications from the agent. Theagent can deny a managers directive for various reasons, if it is not consistentwith the situation in the local environment. The figure below illustrates thecommunication between manager and agent. The figure also shows thecommunication that occurs within the Managed Open System from the agent tothe managed objects.

Management Operations

Notifications

NMC

Manager Agent

Performing Management Operations

Notifications Emitted

Local System Environment

Managed Open System

Q3 Interface OMCR BSS/MFS

ManagingOpen System Communication

Manager

ManagedObjects

Figure 7: Manager and Agent Communications

The OMC-R manages the BSS/MFS resources (i.e., managed objects). Itreflects a view of these managed resources and emits notifications regardingtheir behavior.

1.5.4 SBL Model

The Alcatel BSC has an internal object model structure, based on objectscalled SBLs. SBLs are visible to an operator performing local maintenanceusing terminals (BSC terminal, BTS terminal, or transmission terminal). TheOMC-R displays the SBL name after the BSS board name. The SBL model isnot used by the IMT. The IMT uses an object data base which is responsiblefor showing the objects tree as it is represented in the different views (alarmviews, equipment views, and management views).

32 / 116 3BK 20954 AAAA PCZZA Ed.10

1 Introduction

1.5.5 Mapping O&M Model to SBL Model

The following tables show the mapping of the managed objects to SBLs:

Support resource. The mapping of the managed objects to the SBLs for

this object type is shown in Table 2

Resource. The mapping of the managed objects to the SBLs for this object

type is shown in Table 3

O&M capabilities. The mapping of the managed objects to the SBLs forthis object type is shown in Table 4

Equipment. The mapping of the managed objects to the SBLs for this object


Board. The mapping of the managed objects to the SBLs for this object


Function. The mapping of the managed objects to the SBLs for this objecttype is shown in Table 7.

Note: Note that different actions can be available to managed objects, depending ontheir view at the OMC-R.

1.5.5.1 Mapping SBL - MO Type Support Resource

ActionMOs SBL

Lock/Unlock Shut Down Test Verify Allow/ InhibitAlarm

N7 N7 X X X X -

Circuit Group ATR X X - - -

Ater-Mux TP - - - - - X

Abis TP - - - - - X

A TP - - - - - X

ACH ACH X - - - -

RSL RSL X - - - -

OML OML - - - - -

GSL - X - - - -

N7 Synthesis - - - - - -

Table 2: SBL Mapping for Managed Object Type Support Resource

3BK 20954 AAAA PCZZA Ed.10 33 / 116

1 Introduction

1.5.5.2 Mapping SBL - MO Type Resource

ActionMOs SBL

Lock/Unlock Shut Down Logical Audit

Cell BTS_TEL X X X

BSC BSS_TEL X X X

TRX TRX X - -

Table 3: SBL Mapping for Managed Object Type Resource

1.5.5.3 Mapping SBL - MO Type O&M Capabilities

ActionMOs SBL

Lock/Unlock Logical Audit

BTS BTS_O&M X X

Table 4: SBL Mapping for Managed Object Type O&M Capabilities

34 / 116 3BK 20954 AAAA PCZZA Ed.10

1 Introduction

1.5.5.4 Mapping SBL - MO Type Support Equipment

ActionMOs SBL

Reset/ Restart Hardware Audit A&S Audit

BSC BSC X X X

BTS BTS X X X

Transcoder - X X X

All BSC boards/processe (DTC, TCUC,...)

All BSC boards/processes

X 1 - -

All Transcoder boards(TC16, DB2M ...)

All Transcoder boards X 1 - -

All BTS boards (DRFU,SMBI, ...)

All BTS boards X 1 - -

All BSC functions(TR_OM, ...)

All BSC functions X 2 - -

All BTS functions (FU,carrier unit, RA, ...)

All BTS functions X 2 - -

1: depending on board type.

2: depending on function type.

Table 5: SBL Mapping for Managed Object Type Support Equipment

3BK 20954 AAAA PCZZA Ed.10 35 / 116

1 Introduction

1.5.5.5 Mapping SBL - MO Type Board

ActionMOs SBL

Lock/Unlock Shut Down Reset/Restart

Test Verify

All BSCboards/processes(DTC, TCUC,...)

All BSCboards/processes

X 1 X 1 X 1 X 1 X 1

All Transcoderboards (TC16,DB2M ...)

All Transcoderboards

X 1 X 1 X 1 X 1 X 1

All BTS boards(DRFU, SMBI,...)

All BTS boards X 1 X 1 X 1 X 1 X 1

1: depending on board type.

Table 6: SBL Mapping for Managed Object Type Board

1.5.5.6 Mapping SBL - MO Type Function

ActionMOs SBL

Lock/Unlock Shut Down Reset/Restart

Test Verify

All BSCfunctions(TR_OM, ...)

All BSCfunctions

X 2 X 2 X 2 X 2 X 2

All BTSfunctions (FU,carrier unit,RA, ...)

All BTSfunctions

X 2 X 2 X 2 X 2 X 2

2: depending on function type.

Table 7: SBL Mapping for Managed Object Type Function

36 / 116 3BK 20954 AAAA PCZZA Ed.10

2 Configuration Management


This chapter introduces the concepts and uses of configuration management.

3BK 20954 AAAA PCZZA Ed.10 37 / 116


2.1 IntroductionA typical network is not a static entity. It is constantly and dynamically changingas subscriber traffic levels increase or decrease, and as resources areallocated and freed.

When the network is first installed, the configuration values are set to defaultswhich support maximum coverage and traffic densities. As subscriber trafficdensities change, network reconfiguration (modification, expansion or deletion)is required.

Examples of network reconfiguration include:

Adding or deleting a BSS/MFS to the OMC-R region

Adding or deleting BTS sectors or cells

Modifying BTS cell types

Changing thresholds for power control and handovers

Changing handover relationships between neighboring cells

Adding or deleting traffic channels

Adding or deleting a frequency hopping system

Assigning channels to radio time slots.

2.1.1 Configuration Phases

For network modifications to take effect, the equipment must physically exist inthe network, the system software must be aware that the equipment exists, andthe new equipment must be configured to interact with the rest of the network.Three phases of activity are required:

1. Physical installation of a new network element or of additional capacity (viaboards, subracks, etc.) in existing network elements. Equipment must beput in place, cabled, powered and tested.

2. Hardware Configuration, when the presence of the new hardware is declaredto the BSS and the OMC-R, and its capabilities are put in the appropriatedatabases. The installed component is then said to be equipped.

3. Logical Configuration determines the characteristics and behavior ofthe installed component in the network and how it interacts with othercomponents. Logical configuration is completely separate from theinstallation and hardware configuration phases, and can be performed atan earlier or a later date.

38 / 116 3BK 20954 AAAA PCZZA Ed.10


2.1.2 Types of Network Configuration

Configuration Management allows the operator to perform three types ofnetwork configuration:

Hardware

Using Hardware Configuration functions, an operator can:

Control the placement in service of BSS/MFS hardware

Determine the manner in which deployed hardware elements act andinteract within the BSS/MFS

Modify the parameters that control these elements

View the current hardware configuration status of the network.

Logical

Logical Configuration is the configuration of the Radio Network. There aretwo types of Logical Configuration:

Radio Resource Configuration allows the operator to change theparameters that control the Air Interface. This includes channel

definitions and the definition of FHS

Cell Logical Configuration displays and modifies BSS/MFS logical

parameters and threshold values which influence a cells operationalbehavior. These parameters are divided into several classes which

simplify searches. The display also allows the operator to see additionalinformation about cells, which is used during cell creation, modification

and deletion.

Software.

There are two types of Software Configuration:

Using Software Configuration, an operator can install new versions of theBSS/MFS software or display the current BSS/MFS software version

Using database backup and restore, an operator save a copy of thecurrent BSC or MFS database, and reload the database if required.

3BK 20954 AAAA PCZZA Ed.10 39 / 116


2.2 Radio Network OptimizationAs networks evolve and mature, operators need to be able to reconfigure thenetwork to maximize capacity, minimize outages, and provide a high level ofreliability (i.e., calls successfully established, maintained with a minimum ofinterference and normally terminated).

2.2.1 High Speed Data Service (HSDS)

HSDS provides CS1 to CS4 for GPRS, and MCS1 to MCS9 for (E)GPRS. It alsooffers additional functions that adapt radio resource allocation with (E)GPRSMSs to avoid Ater blocking by allocating more transmission resources on Abisand Ater to a radio time slot managing HSDS capability on a TRE basis.

HSDS is supported in each BSS and provides:

A second Abis link. When there are insufficient Abis time slots on one Abislink, a second Abis can be attached to the BTS

MPDCH handling. This allows the OMC-R to allocate a number of radio timeslots per cell that are reserved for packet-switched signaling

(E)GPRS protocol modulation and coding schemes. Nine different

modulation and coding schemes, MCS1 to MCS9, are defined for the(E)GPRS radio data blocks

Enhanced radio resource allocation. (E)GPRS traffic has priority over

GPRS traffic. TRXs with a high throughput are preferred for (E)GPRStraffic but GPRS throughput is optimized as long as it does not conflict

with (E)GPRS traffic

T4 allocation. This solves conflicts between uplink GPRS TBFs anddownlink (E)GPRS TBFs

Dynamic transmission handling. PDCHs are established with the maximumnumber of GCHs, whatever the supported traffic. Unused GCHs, depending

on traffic, are released in case of Ater congestion. For GPRS TBF allocation,

PDCHs are established with a reduced number of GCHs during the Atercongestion state.

2.2.2 Assisted GPS (A-GPS)

The A-GPS server can be physically connected to the MFS (Ethernetconnection/WAN), and provides both assistance data and geographicalposition, when requested.

A-GPS provides two types of assistance data via a GPS link to the GPS-MS:

Navigation data from satellites

Differential GPS (DGPS), providing corrections to measurement errors. Thisgreatly improves location accuracy.

40 / 116 3BK 20954 AAAA PCZZA Ed.10


2.2.3 Using O&M Data

The network optimization tools work with the BSS/MFS O&M as follows:

Operational radio and logical configuration information serves as a baseline,

to predict performance when compared with planned configurationsimported from planning applications. These parameters can also be

compared to GSM and expert rules

Performance Management statistics are used to:

Evaluate network efficiency

Help in network configuration planning.

Data from the OMC-R is produced in both ASCII and binary file formats.The OMC-R also exports data to and imports data from network planningapplications.

For more information on the binary files used by the OMC-R and the differentoptimization tools, refer to the A1353-RA Configuration Import/Export Interfaceand the A1353-RA Configuration Import/Export Interface: SupplementaryInformation documents.

2.2.4 Data Flow in the Network Optimization Tool Chain

The figure below shows the relationship between different tools in the cycleof planning, operating, and optimizing the network. Only the OMC-R actuallyconfigures the BSS/MFS network. Output from optimization or planning tools isprocessed by the OMC-R under the control of the OMC-R operator.

Data produced by RNO has a role in both daily operation and networkoptimization.

For more information on the binary files used by the OMC-R and the differentoptimization tools, refer to the A1353-RA Configuration Import/Export Interfaceand the A1353-RA Configuration Import/Export Interface: SupplementaryInformation documents.

3BK 20954 AAAA PCZZA Ed.10 41 / 116


NETWORK PLANNING

NETWORK OPTIMIZATION

NETWORK OPERATION

Network Planning Tools

A956 RNO

NPA/MPM

BSS NETWORK

OMCR OMCROMCR

Figure 8: Data Flow Between Planning, Optimization and Operation Tools

2.2.5 Physical Organization of Network Optimization Tool Chain

The following figure shows how the different elements of the optimizationprocess are interconnected.

Dashed lines correspond to a LAN that connect OMC-R, RNO and NPAmachines. Customer can use this optional network to separate the flow of datafor backup and restore operations from other information usually exchanged.

LAN

A956RNO ServerNPAQoS Database

OMCR

RNO Workstations

LAN 2

LAN 1

Figure 9: Architecture of the Optimization System

42 / 116 3BK 20954 AAAA PCZZA Ed.10


2.2.6 Unbalancing TRX Output Power per BTS sector

The feature allows unbalanced configurations on the same antenna network.This configuration behaves as a concentric cell, where the output powerbalancing is performed on a zone basis instead of on the sector basis.Furthermore for 3 TRXs per ANc configuration, 2 TRXs are used in combiningmode on the first antenna path and connected in by-pass mode. The thirdTRX is used on the second antenna path, thus resulting in the same sort ofconcentric cell configuration as in the case of different TRX output power.

The BTS informs the BSC, for each TRE, about the GMSK and 8PSK outputpower (after coupling). The BTS informs the OMC through HW audit about theoutput power of each TRE for GMSK and 8PSK modulation .

When the feature is activated on a concentric cell, the BSS system ensures thatthe more powerful TREs (factor1) are mapped on TRX configured on the outerzone, and the less powerful ones, on the TRX configured on the inner zone.

The feature can be activated at OMC through one of the Power Controlparameters: EN-Unbalanced-Output-Power. It is not an optional feature.

3BK 20954 AAAA PCZZA Ed.10 43 / 116


2.3 Parameter TuningBSS/MFS operational behavior is influenced by the setting of the logicalparameters and the allocation of resources, that is, the mapping betweenlogical and physical resources.

The operator uses the OMC-R to display, modify or delete logical parameters.

Changing these parameters depends on their relationships with one another. Italso depends on the ability of the BSS/MFS to incorporate the changes in theoperational environment.

2.3.1 Radio Resource Configuration

Radio Resource Configuration controls how the BSS/MFS uses the Airinterfaces resources. The operator can configure the BSC or MFS and modifythe channel configurations, switch to an alternate radio configuration, or use anautomatic non-hopping alternate configuration. There are a number of radioresource parameters, but the most important are:

Cell allocation of Absolute Radio Frequency Channel Numbers (ARFCNs)

TRXs

FHSs

Channel configurations.

Radio resource parameters are configured on the OMC-R, and only when allchanges have been entered is the new configuration transmitted to the BTSduring the activation process.

For further information about radio resource (logical) parameters, see CellLogical Configuration (Section 2.3.2).

For further information about configuring radio resource (logical) parameters,see Logical Configuration Management in the BSS Configuration Handbook.

2.3.1.1 Cell Allocation of ARFCNsARFCNs must be allocated to a cell or a sector before they can be assigned toan FHS or used in channel configuration. Up to 64 ARFCNs can be allocated.

The following actions apply to this set of parameters:

Search for a set of ARFCNs

Display the ARFCNs allocated to a cell or sector

Modify the cell/sector allocation of one or more ARFCNs (see Create RadioFrequency in the BSS Configuration Handbook).

Once allocated to a BTS, ARFCNs and certain related channel characteristicsare automatically assigned to specific carrier units (G1/G2 BTSs).

44 / 116 3BK 20954 AAAA PCZZA Ed.10


2.3.1.2 TRX ConfigurationAbis time slots are connected to the TCUs through the BIUA. The BTSconnects each radio time slot to one Abis nibble. All circuit-switched trafficnibbles for a given TRE are connected to the same TCU. The extra 16k nibblesare connected to any TSU TCU carrying the primary Abis, or any TSU TCUcarrying the secondary Abis. TRX transmission pools are defined for eachsector of each BTS. For a cell shared with a main and a secondary sector, TRXtransmission pools are defined for the main and/or the secondary sector.

2.3.1.3 FHSsAn FHS is the set of frequencies on which a single radio time slot (channel)hops. Before creating an FHS, ARFCNs must be allocated to a BTS usingthe Cell Allocation function.

Two types of Frequency Hopping are available:

Baseband hopping in G1/G2 BTSs, in which the maximum number offrequencies used is determined by the number of TRXs in the cell which

uses the FHS. There is a fixed frequency for each carrier unit

Synthesized (or radio) hopping in BTS A9100/A9110, in which the maximumnumber of frequencies is up to 64, depending on the configuration of the

system as a whole.

The types of frequency hopping and the BTS on which they are applicable areshown in the following table.

BTS Type NoHopping

BasebandHopping

SynthesizedHopping

G1/G2 BTS Yes Yes No

Micro-BTS Yes No Yes

BTS A9100/A9110 Yes No Yes

Table 8: Type of BTS and the Applicable FHS


Display all FHSs within a BTS

Display one specific FHS

Create an FHS (see Create Frequency Hopping System in the BSS

Configuration Handbook)

Modify an FHS (see Modify Frequency Hopping System in the BSS


Delete an FHS (see Delete Frequency Hopping System in the BSSConfiguration Handbook).

The OMC-R checks, before deleting an FHS, if the FHS is in use. If it is in use,the command to delete the FHS is rejected.

3BK 20954 AAAA PCZZA Ed.10 45 / 116


The types of frequency hopping are fully discussed in Frequency Hoppingin the BSS System Description. Procedures for configuring and managingFHSs are described in Logical Configuration Management Tasks in the BSSConfiguration Handbook.

2.3.1.4 Channel ConfigurationsThe parameters of this group are used to configure the time slots of theTransceivers in a BTS. The TRX is a logical entity not to be confused with theTRE, which is a physical entity. Each TRX handles 8 time slots, and can beconfigured as hopping or non-hopping. TRXs are assigned to a sector (theremust be one in a non-sectorized BTS), and each time slot is configured with thechannel type (BCCH, Traffic Channel (TCH), Voice Group Call Service Channel(VGCH), etc.) and frequency use. The use of TCHs for GPRS must alsobe configured, if required.

For non-hopping configurations, the use column contains the ARFCN, selectedfrom the list of ARFCNs allocated by Cell Allocation. All the time slots of theTRX must contain the same ARFCN. For hopping configurations, the usecolumn contains the Frequency Hopping System-Identity (FHS-ID) and theMobile Allocation Index Offset (MAIO). The time slot containing the BCCH(usually time slot 0 of the first TRX) has a fixed ARFCN as it never hops. Formore information about the FHS-ID and MAIO, refer to Frequency Hopping inthe BSS System Description.


Display the type and use of time slots in a configuration

Modify the type and use of time slots in a configuration

Define baseband hopping or non-hopping channel configurations

Add a TRX (see Create TRX in the BSS Configuration Handbook)

Delete a TRX (see Delete TRX in the BSS Configuration Handbook).

Channel configuration procedures are described in Radio ChannelConfiguration in the BSS Configuration Handbook.

46 / 116 3BK 20954 AAAA PCZZA Ed.10


2.3.2 Cell Logical Configuration

To optimize system performance, the operator can adjust cell characteristicswhich influence how the cells behave under different circumstances. Operatorstypically make such changes when adding or upgrading equipment, or toaccommodate special conditions or use patterns which occur around eventssuch as major holidays or sporting tournaments.

The parameters affected by Cell Logical Configuration are grouped intoparameter classes as follows:

BSS/MFS parameters

External OMC-R cells

Cell information elements

Cell power control and handover preprocessing

Cell handover relationships

Cell factors and thresholds for handover decision

Faster GPRS access

Full Intra-RA LLC PDU re-routing.

2.3.2.1 BSS/MFS ParametersThese are system-wide parameters. A modification of one of these parametersaffects all cells in the BSS.

BSS parameters include:

Timers

Parameters which are used to prevent channel overload under criticalconditions

Parameters which control the MSC-BSC interface.

The BSS parameters are further subdivided into logical groups. See thefollowing documents for details:

BSS Configuration Handbook

BSS O&M Parameters Dictionary

BSS Telecom Parameters Dictionary.

3BK 20954 AAAA PCZZA Ed.10 47 / 116


2.3.2.2 External OMC-R CellsThis group of parameters provides information to the OMC-R about cells whichbelong to another GSM or UMTS OMC-R. This is necessary to create outgoinghandover relationships with these 2G or 3G cells.

Using the Create function for these attributes means creating an object instancein the OMC-R for a cell 2G or 3G, which is controlled by another OMC-R. It hasno effect on the cell itself as the cell is controlled elsewhere. When an updatefor the 2G or 3G cell is performed on the host OMCR, the OMC-Rs that see thatcell as external are notified, and the information is updated. The data mustbe accurate as it is used by the mobile station when it needs a handover toone of these external OMC-R cells.

Outgoing inter-PLMN handovers allow operators to define handover adjacencylinks towards external cells belonging to foreign PLMNs. Foreign PLMNs arethose other than that to which internal OMC-R cells belong.

The Multi-PLMN feature allows operators to manage cells of different PLMNsby using the same OMC-R and MFS. This allows operators to put in placenetwork sharing.

Be aware of the following important considerations:

Every cell of the PLMN has a BSIC composed of the NCC and the BCC. The

BCC has to be carefully chosen during network planning so that the mobilestation can distinguish cells by BSC in a limited geographical area. This is

especially important if these cells share the same BCCH carrier frequency

If an external cell is modified by its OMC-R, handover relationships in theneighbor OMC-R can be affected. An automatic update mechanism for this

data is available and can be applied periodically or on demand.One OMC-R acts as supervisor and manages a list of the OMC-Rs itsupervises. Each OMC-R (both supervised and supervisor) detectsmodifications of its own cells. The supervisor OMC-R identifies allmodifications on its own cells and also on cells from the supervisedOMC-Rs. If these changes are not done on the OMC-Rs where the cellsare defined as external, it requests the neighbor OMC-Rs to perform thecorresponding updates.

Parameters of this class can be:

Displayed

Created (see Create External OMC Cell in the BSS Configuration Handbook)

Modified (see Modify External OMC Cell in the BSS ConfigurationHandbook)

Deleted (see Delete External Cell from PRC and Delete External Cell from

SC in the BSS Configuration Handbook).

48 / 116 3BK 20954 AAAA PCZZA Ed.10


2.3.2.3 Cell Information ElementsThis part of the Cell Logical Configuration function permits an operator todisplay and modify all the attributes of a specific cell. These are the cellinformation elements, which include:

Type of cell (normal, concentric, micro, extended, etc.)

BSIC

BCCH Frequency

Training Sequence Code

Cell options

Cell selection parameters

Parameters which configure the different control channels (BCCH, CCCH,

etc.)

Radio link supervision and handover control parameters.

A complete list of these parameters is found in the BSS Telecom ParametersDictionary and the BSS O&M Parameters Dictionary, and the procedures formodifying them are in Set Cell Telecom Parameters in the BSS ConfigurationHandbook.

2.3.2.4 Cell Power Control and Handover PreprocessingThese parameters are used to set the conditions under which handover (HO)occurs, and to enable or disable different types of handover. The setting ofthese parameters is crucial to the performance of the system. They includetimers, thresholds and flags used to control the following:

Handover type enabled or disabled

Attributes and thresholds for the implementation of each type of handover

Threshold values for each type of handover which are used to determine

when handover needs to take place

Quality and level power control parameters for both uplink and downlink,which, used in combination, determine when power is increased or

decreased

Quality and level HO thresholds for both uplink and downlink which, used incombination, determine whether a handover is necessary

Thresholds which generate a link alarm (due to link quality, link power level,

or mobile station to BTS distance). The link alarm, in turn, initiates the HOcandidate cell evaluation process

Cell handover evaluation process (see Cell Factors and Thresholds forHO Decision later in this chapter).

Parameters can be displayed and modified. They are divided into logicalsub-groupings. See Set Cell Telecom Parameters in the BSS ConfigurationHandbook for details.

3BK 20954 AAAA PCZZA Ed.10 49 / 116


2.3.2.5 Cell Handover RelationshipsIn the PLMN, every cell has a list of up to 64 adjacent cells which are monitoredby every mobile station with a call in progress in that cell. The mobile station isconstantly reporting signal strength of the BCCH channel back to the BTS andBSC. The BSC evaluates these reports to see if a handover is necessary.

Two major factors taken into account for handover are Power Budget, used todetermine the lowest possible power to provide acceptable signal quality, andHandover Margin, which determines the hysteresis threshold between cells.These parameters and the role they play in handover decisions are discussedin detail in the following sections:

Power budget, see Better Cell Handover in the BSS System Description

Handover margin, see Target Cell Evaluation in the BSS System Description.

Two types of adjacent cells are handled:

Adjacent cells for handover

Adjacent cells for roaming.

The OMC-R maintains a list in its database of all adjacent cells for roaming.This list is not duplicated in the BSC; the BSC only maintains a list ofneighboring BCCH frequencies.

Each time an adjacent cell for roaming is created, modified or deleted, theOMC-R updates its database, and updates the list of neighboring BCCHfrequencies in the BSC. Using the OMC-Rs Adjacent Cell Management form,the operator can:

Search for incoming and outgoing adjacent cell relationships

Display adjacent cell relationships

Modify adjacent cell parameters (see Modify Adjacency in the BSS


Create adjacent cell relationships (see Create Adjacency in the BSSConfiguration Handbook)

Delete all adjacent cell relationships (see Delete Adjacency in the BSS


Delete all outgoing adjacent cell relationships

Delete incoming adjacent cell relationships as long as they are controlled by

the OMC-R.

Deleting adjacent cell relationships with neighboring OMC-R cells (i.e., cellscontrolled by another OMC-R) requires co-ordination between the two OMC-Roperators to avoid degradation of service.

Voice Group Call Service (VGCS) links are considered by the BSS to behandovers, and the operator can define adjacency links that are only valid forVGCS. Note that defining a VGCS link does not increase the maximum numberof handovers allowed per serving cell. For more information about VGCSmanagement, refer to VGCS in the BSS System Description.

The creation and maintenance procedures for handover relationships arediscussed in detail in Logical Configuration Management Tasks in the BSSConfiguration Handbook.

50 / 116 3BK 20954 AAAA PCZZA Ed.10


2.3.2.6 Cell Factors and Thresholds fo

operations & maintenance principles ed10.pdf

Documents

om data

prc management functions

bssmfs om functions

bss software management

fault management

hardware configuration

radio network optimization

mfs software management