NORTEL GSM Principles(1).pdf

7/26/2019 NORTEL GSM Principles(1).pdf

1/511

Global System for Mobile Communications (GSM)

Nortel GSM BSSFundamentalsOperatingPrinciplesRelease: V18.0 PC2Document Revision: 18.08

www.nortel.com

411-9001-007.


2/511

Global System for Mobile Communications (GSM)Release: V18.0 PC2Publication: 411-9001-007Document release date: 5 March 2010

Copyright 1999-2010 Nortel Networks. All Rights Reserved.

While the information in this document is believed to be accurate and reliable, except as otherwise expresslyagreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OFANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document aresubject to change without notice.

Nortel, Nortel Networks, the Nortel logo, and the Globemark are trademarks of Nortel Networks.

All other trademarks are the property of their respective owners.

.


3/511

3.

Contents

New in this release 11Features 11

Gb over IP on GERAN (22911) 12

Enhanced very early assignment (30259) 12

OMC-R T5140 Introduction (Maramba) (31737) 12

TFO support (32217) 13FACCH repetition for TCH/HR (32359) 13

Flexible BSC/OMC-R interface (33164) 13

Board reset command by OMC-R (33378) 13

S8000/S12000 smart power management (34351) 14

BTS 18k/9k/6k inventory (34497) 14

Adding TCU to the 10 BSC upgrade in parallel (34535) 14

S12000 S444 with stepped coupling and stepped PA (34784) 14

BTS 18000 family smart power management enhancement (34913) 15

Multiple ARFCN for GSM to UMTS FDD mobility (34944) 15

Smart Power Management: Feature Lock at OMC-R (34956) 15

Multizone cell enhancement step 2 (34960) 16

2G-3G cell reselection improvement (35083) 16

Abis over IP on BTS6000 / BTS9000 / BTS18000 (34966) 16

Abis over IP on BTS S8000 / S12000 (34967) 17

Abis over IP: end-to-end functions (34973) 17

Abis over IP: Feature Lock at OMC-R (34981) 17

New Type of OMC-R Client & CIUS (35040) 18

V18 support for GSM-R (35095) 18

GSM900-UMTS900 combination on the same antenna (35147) 18

Up to 8 ARFCN for GSM to 3G UTRAN FDD & TDD cell reselection(35179) 18

Abis over IP: Support of TDM-based LMU (35240) 19

Other changes 19

Introduction 21

Chapter 1 Overview 251.1 Overview of network operations 25

1.1.1 PCUSN performance management and preventative maintenance 25

Global System for Mobile Communications (GSM)Nortel GSM BSS FundamentalsOperating Principles

411-9001-007 18.08 5 March 2010



4/511

4

1.1.2 The OMC-R 25

1.1.3 Major operating principles 26

1.2 BSC 3000 functional characteristics 30

1.2.1 Facilities provided 30

1.2.2 Main systems 31

1.2.3 Software architecture 31

1.2.4 Electrical and optical configurations 32

1.3 OMC-R features and functions 35

1.3.1 Feature lock and the licensing process 35

1.3.2 Introduction to OMC-R data server (SDO) 35

1.3.3 Disaster recovery 38

1.3.4 Managing and monitoring the network with the OMC-R 38

1.3.5 OMC-R Servers 39

1.4 Basic definitions 39

1.4.1 OMC-R functional architecture 39

1.4.2 Objects 401.4.3 Databases 40

1.4.4 Object classes and instances 42

1.4.5 Parameters 43

1.4.6 Operations 43

1.4.7 Unsolicited messages 44

1.5 OMN access management 45

1.5.1 BSC 3000 OMN access management 45

1.6 OMC-R network configuration 52

1.6.1 TCP/IP over Ethernet 52

1.7 IP networking 53

Chapter 2 Configuration management 552.1 Object classes 55

2.1.2 Radio subsystem configuration 56

2.2 Managed entities 62

2.3 State parameters 63

2.4 Managed object relationships 65

2.4.3 Order of creating objects 66

2.5 Permanent parameter classes 73

2.6 Parameter validity controls 74

2.7 Hardware configuration 75

2.7.1 BSC 3000 hardware configuration 752.8 BSC 3000 load balancing 80

2.8.1 Introduction 80

2.9 Number radio site configuration 82

2.10 Basic operations 83

2.10.1 Configuration 84

2.10.2 Display 85


411-9001-007 18.08 5 March 2010



5/511

5

2.11 Secure operation in reparenting 86

2.11.3 Security 87

2.12 Improved build online performance 89

2.13 PCUSN configuration 89

Chapter 3 Performance management 933.1 Overview 93

3.2 Performance management 97

3.2.1 Permanent observations 97

3.2.2 Performance Monitor observation 109

3.2.3 Trace management 112

3.2.4 OMC-R message store 118

3.2.5 Performance management reporting 121

3.2.6 Obtaining distributions on radio measurements 123

3.2.7 Call drop analysis 128

3.2.8 Generating an Interference Matrix 132

Chapter 4 Fault management 1374.1 Definitions 137

4.1.1 Unsolicited message 137

4.1.2 Q3 notification 137

4.1.3 User notification 137

4.1.4 Alarm 137

4.2 Overview 138

4.3 Unsolicited message management 141

4.4 Alarm management 148

4.5 Alarm criteria 152

4.6 Man-machine commands 1564.7 Alarm counters and relays 161

4.8 PCUSN interface 163

Chapter 5 Security management 1655.1 Overview 165

5.2 Service access management 165

5.3 Work session management 172

5.4 Special cases 175

5.5 Output classes 176

Chapter 6 SMS-CB management 1796.1 Overview 179

6.2 Principles 179

6.3 Message management 180

6.4 Broadcast management 182

Chapter 7 Software management 1857.1 Definitions 185


411-9001-007 18.08 5 March 2010



6/511

6

7.2 BTS S8000 with CWSM 186

7.3 BSC 3000 software management 186

7.3.6 BTS software background downloading 197

7.4 Consulting BSS software versions 201

7.5 Centralized downloading of BTS by BSC 202

7.5.3 Improved BSC defense for centralized downloading 203

7.6 Automatic downloading of DRX software 206

7.7 Upgrade of BSC and TCU nodes in parallel 207

7.8 Flexible BSC/OMC-R interface 208

Chapter 8 Command file management 2098.1 Overview 209

8.2 Operating principles 209

8.3 File Execution time Duration (FED) 216

8.4 Command file directory management 216

Chapter 9 User facilities 2199.1 Overview 2199.2 System log services 219

9.3 System time management 222

9.4 Job scheduler 223

9.5 Inter-user mail facility 228

9.6 On-line help 229

Chapter 10 Network graphic management 23110.1 Network display 231

10.2 State management 249

Chapter 11 GSM evolutions 26311.1 General Packet Radio Service (GPRS) 263


11.1.2 Principles 263

11.1.3 Implementation 264

11.1.4 OAM interfaces evolution 264

11.1.5 GSM/GPRS/EGPRS TSs dynamic sharing 265

11.1.6 RLC polling improvement 267

11.1.7 TBF establishment improvements 268

11.1.8 GPRS TBF establishment improvement: one phase access 270

11.1.9 Extended uplink TBF 271

11.1.10 Full Keep Alive 272

11.1.11 Disabling TBF Keep Alive during GMM procedure 272

11.1.12 GPRS sleepy cells Step 1: automatic detection and recovery 273

11.1.13 Configure sending of SI13 and SI2Quater on Ext or NormalBCCH 273

11.1.14 PS paging duplication on BSC 275

11.1.15 GRPS/EDGE Suspend and Resume 275


411-9001-007 18.08 5 March 2010



7/511

7

11.1.16 Network Mode of Operation 276

11.2 AMR 282

11.2.1 Algorithms 283

11.2.2 BSS capacity 283

11.2.3 Effect of satellite links on AMR services link adaptation mechanism 283

11.2.4 AMR based on traffic 284

11.2.5 FACCH repetition 284

11.2.6 AMR-HR on pre-empted PDTCH 285

11.2.7 Wideband AMR 286

11.3 Location services 288


11.3.2 NSS-based solution 288

11.3.3 BSS-based solution 289

11.3.4 Location methods 296

11.3.5 A-GPS Assistance data support 299

11.4 EDGE 29911.4.1 Introduction 299

11.4.2 Data backhaul 300

11.4.3 TDMA selection 300

11.4.4 Link adaptation 302

11.4.5 Dynamic allocation 303

11.4.6 ARQ window management and compressed bitmap feature 303

11.4.7 UL incremental redundancy 304

11.4.8 DL incremental redundancy 304

11.4.9 Configuration 305

11.4.10 Dynamic Agprs and EDGE: Joker handling algorithm 306

11.4.11 Rules applicable to EDGE 315

11.5 Wireless Priority Service 316


11.5.2 Queuing services 316

11.5.3 Public access bandwidth protection 317

11.5.4 Directed retry without queuing activation feature 317

11.5.5 Access class barring 317

11.6 GSM for Railways (GSM-R) 320


11.6.2 Advanced Speech Call Items (ASCI) 320

11.6.3 Activation of GSM-R features 323

11.6.4 Hardware constraints 323

11.6.5 Implemented features 323

11.6.6 Channel Release on BTS after Abis failure 332

11.7 EDGE dynamic Abis per site 333

11.8 Tandem-Free Operation (TFO) 334

11.9 Abis over IP 335

11.9.1 BSS IP networking hardware 335


411-9001-007 18.08 5 March 2010



8/511

8

11.9.2 IP BTS OAM Services (IBOS) 335

11.9.3 BSS Migration from TDM to IP 336

11.9.4 BTS configuration options 337

11.9.5 IP backhaul network design and configuration 339

11.10 Gb over IP 345


11.10.2 Capabilities 346

11.10.3 Restrictions 347

11.11 GSM900-UMTS900 combination on the same antenna 349


11.11.2 Specification 349

11.11.3 Feature locking 351

Chapter 12 Radio configuration principles 35312.1 Introduction 353

12.1.1 Dictionary of objects 353

12.1.2 Main principles 353

12.1.3 Joint diversity 353

12.2 Dictionary of objects 354

12.2.1 The omc object 354

12.2.2 The md subtree 355

12.2.3 The network subtree 359

12.2.4 The bsc subtree 359

12.2.5 The transcoder subtree 362

12.2.6 The btsSiteManager subtree 363

12.2.7 The multiple site object 367

12.2.8 The software object 36712.2.9 The short message object 367

12.2.10 Inter-object relationships 368

12.3 Radio entity management principles 370

12.3.1 BSC management 370

12.3.2 PCM link management 370

12.3.3 LAPD link management 380

12.3.4 Concentric cells 383

12.3.5 Software management 385

12.4 Radio measurement processing 386


12.4.2 Configuration parameters 38812.4.3 Definitions 390

12.4.4 Measurement processing 390

12.4.5 New power control algorithms 397

12.4.6 Single BCCH enhancement 399

12.5 Radio cell selection and reselection 403



411-9001-007 18.08 5 March 2010



9/511

9

12.5.2 Configuration parameters 403

12.5.3 Selection management 404

12.5.4 Reselection management 406

12.5.5 Network assisted cell change for release 4 MS 408

12.6 Handover management 409



12.6.3 Processing algorithms 421


12.6.5 Neighbor cells 430

12.6.6 Microcells 436

12.6.7 GSM to UMTS handover 438

12.7 Power control 440


12.7.2 Multi-zone cells 440

12.7.3 Configuration parameters 44112.7.4 Processing algorithms 443

12.7.5 Maximum transmission power 447

12.7.6 BTS smart power management 455

12.8 Call monitoring 458


12.8.2 Mobile distance control 458

12.8.3 Radio link monitoring 459

12.9 Radio resource allocation 461



12.9.3 Priority management 463

12.9.4 Queuing management 463

12.9.5 Processing algorithm 464


12.9.7 Downlink advanced receiver performance 465

12.9.8 Idle radio channel classification 466

12.10 Frequency hopping management 466


12.10.2 Frequency hopping management principles 467

12.10.3 Frequency redefinition process 468

12.10.4 timeslot reconfiguration 469

12.11 Frequency plan change for large scale networks 469

12.12 Synchronization 470

12.12.1 BTS Synchronization over Abis 470

12.12.2 Co-located BTS Synchronization 471

12.12.3 Network Synchronization 472

12.13 Defense and reconfiguration 473



411-9001-007 18.08 5 March 2010



10/511

10

12.13.2 Defense 474

12.13.3 Reconfiguration 476

12.14 Encryption 477

12.14.1 Purpose of A5/3 477

12.14.2 Principles of A5/3 477

12.14.3 Availability of A5/3 478


12.15 Abis over IP 479



Appendix A BTS TEI Numbering Rules 483A.1 S2000 H/L BTSs 483

A.2 e-cell BTSs 483

A.2.1 Monoband configurations 483

A.2.2 Dualband BCF configurations with monoband cells 483

A.3 S8002 BTSs 483

A.4 S8000 Outdoor/Indoor BTSs 484

A.4.1 Monoband S8000 BTS configurations 484

A.4.2 Dualband BCF S8000 BTS configurations with dualband cells 485

A.4.3 Dualband BCF S8000 BTS configurations with monoband cells 487

A.4.4 Dualband CBCF S8000 BTS configurations with dualband cells 488

A.4.5 Dualband CBCF S8000 BTS configurations with monoband cells 490

A.5 S12000 Outdoor/Indoor BTSs 491

A.5.1 Monoband S12000 BTS configurations 491

A.5.2 Dual band S12000 BTS configurations with dualband cells 493

A.5.3 Dualband CBCF S12000 BTS configurations with dualband sites 496A.6 BTS 18000 499

A.6.1 TEI Numbering 499

A.6.2 TEI Mapping 499

A.6.3 Location of shelves 501

A.7 BTS 6000 501

A.7.1 Modules 501

A.7.2 TEI numbering for TRXs 501

A.7.3 TEI numbering for ABMs 502

Appendix B GSM Equivalences 503

Appendix C Network Level Presence Identification of eDRX,ePA, and HePA 507C.1 Overview 507

C.2 Operating principles 507

C.3 Impacts 508


411-9001-007 18.08 5 March 2010



11/511

11.

New in this release

The following sections detail what are new in the Nortel GSM BSSFundamentalsOperating Principles(411-9001-007) for release V18.0Pick & Choose 2.

Features (page 11)

Other changes (page 19)

FeaturesSee the following sections for information about feature changes:

Gb over IP on GERAN (22911) (page 12)

Enhanced very early assignment (30259) (page 12)

OMC-R T5140 Introduction (Maramba) (31737) (page 12)

TFO support (32217) (page 13)

FACCH repetition for TCH/HR (32359) (page 13) Flexible BSC/OMC-R interface (33164) (page 13)

Board reset command by OMC-R (33378) (page 13)

S8000/S12000 smart power management (34351) (page 14)

BTS 18k/9k/6k inventory (34497) (page 14)

Adding TCU to the 10 BSC upgrade in parallel (34535) (page 14)

S12000 S444 with stepped coupling and stepped PA (34784) (page14)

BTS 18000 family smart power management enhancement (34913)(page 15)

Multiple ARFCN for GSM to UMTS FDD mobility (34944) (page 15)

Smart Power Management: Feature Lock at OMC-R (34956) (page15)

Multizone cell enhancement step 2 (34960) (page 16)


411-9001-007 18.08 5 March 2010



12/511

12 New in this release

2G-3G cell reselection improvement (35083) (page 16)

Abis over IP on BTS6000 / BTS9000 / BTS18000 (34966) (page 16)

Abis over IP on BTS S8000 / S12000 (34967) (page 17)

Abis over IP: end-to-end functions (34973) (page 17) Abis over IP: Feature Lock at OMC-R (34981) (page 17)

New Type of OMC-R Client & CIUS (35040) (page 18)

V18 support for GSM-R (35095) (page 18)

GSM900-UMTS900 combination on the same antenna (35147) (page 18)

Up to 8 ARFCN for GSM to 3G UTRAN FDD & TDD cell reselection(35179) (page 18)

Abis over IP: Support of TDM-based LMU (35240) (page 19)

Gb over IP on GERAN (22911)This feature addresses the optional use of IP for the transport layermechanism on the Gb interface, as an alternative to frame relay (FR).

Gb over IP on GERAN impacts this document through the following:

Added section1.7 IP networking (page 53)

Added section11.10 Gb over IP (page 345)

Updated section2.4.3 Order of creating objects (page 66)

Enhanced very early assignment (30259)This feature consists in broadcasting the NECI bit in the systeminformation. It allocates a traffic channel for a speech or a circuit switchedcall, as soon as possible.

Enhanced very early assignment impacts this document through thefollowing:

Updated subsection12.9.1 Principles (page 461)

Updated subsection12.9.2 Configuration parameters (page 462)

OMC-R T5140 Introduction (Maramba) (31737)This feature introduces a new OMC-R server: T5140 / ST2510.


411-9001-007 18.08 5 March 2010



13/511

Features 13

OMC-R T5140 Introduction impacts this document through the following:

UpdatedTable 1 "OMC-R maximum number of simultaneousinstances" (page 33)

Updated section1.3.5 OMC-R Servers (page 39)

Updated section1.6.1 TCP/IP over Ethernet (page 52)

Updated section2.13 PCUSN configuration (page 89)

Updated subsectionOMC-R observation record store (page 104) insection3.2.1.5 Storing permanent observation records (page 103)

TFO support (32217)The TFO feature purpose is to remove the speech coding/decoding in theMS-to-MS calls, in order to improve the perceived speech quality.

TFO support impacts this document through the following:

Added section11.8 Tandem-Free Operation (TFO) (page 334)

FACCH repetition for TCH/HR (32359)This feature secures the handover procedure in poor radio conditions (withAMR FR). The BTS retransmits the FACCH frames after 40 ms (withoutwaiting for the mobile acknowledgement).

FACCH repetition for TCH/HR impacts this document through thefollowing:

Added parameter enableRepeatedFacchHr in subsection11.2.5FACCH repetition (page 284)

Updated subsection11.2.5 FACCH repetition (page 284)

Flexible BSC/OMC-R interface (33164)This feature simplifies the interface between the BSC and the OMC-R,for the managed object dictionary (MOD) update. Updating the MOD isallowed with the same version and architecture of the BSC.

Flexible BSC/OMC-R interface impacts this document through thefollowing:

Added subsection7.8 Flexible BSC/OMC-R interface (page 208)

Board reset command by OMC-R (33378)This feature implements a new maintenance action at the OMC-R to resetan active or passive board at the BTS.


411-9001-007 18.08 5 March 2010



14/511


Board reset command by OMC-R impacts this document through thefollowing:

Updated subsection12.2.6.1 The btsSiteManager object (page 363)

S8000/S12000 smart power management (34351)This feature reduces S8000 and S12000 BTS power consumption byautomatically switching the PA off after a configurable period of timeelapses during which there is no circuit communication on the TRX.

S8000/S12000 smart power management impacts this document throughthe following:

Modified subsection12.7.6 BTS smart power management (page455)

BTS 18k/9k/6k inventory (34497)This feature allows having the hardware inventory on the BTS 18000, BTS9000, and BTS 6000, and facilitating the physical maintenance and thespares management.

BTS 18k/9k/6k inventory impacts this document through the following:

Added a paragraph in section1.3.2 Introduction to OMC-R data server(SDO) (page 35)to inform that the BTS inventory is also available asa CSV file.

Adding TCU to the 10 BSC upgrade in parallel (34535)This feature improves the BSS upgrade process to allow the TCU to beupgraded in parallel with up to 10 BSC nodes.

Adding TCU to the 10 BSC upgrade in parallel impacts this documentthrough the following:

Deleted sectionImproved upgrade performance since it is no longerrequired in Release 18.0.

Added section7.7 Upgrade of BSC and TCU nodes in parallel (page207)

S12000 S444 with stepped coupling and stepped PA (34784)The aim of this feature is to propose a solution that would free upsome antenna ports for UMTS on their existing GSM sites. Functionallyspeaking, it is requested to offer: -S12000 S444 with, per sector and percabinet, 2 HePA on H2D and 2 ePA on D/TxF. -S12000 O12 with, persector and per cabinet, 4 HePA on H2D and 8 ePA on D/TxF.


411-9001-007 18.08 5 March 2010



15/511

Features 15

It is expected that the concentric cell feature is not mandatory and that thesame RF output power is seen from the OMC for all coverage areas of theconsidered BTS: ie 3 cells only for the S444.

This RFF concerns outdoor cabinets (GIPS and non GIPS power systems

TBC). 2 extension cabinets need to be supported.

A V16 based patch is expected. CT2000 support is nice to have.

BTS 18000 family smart power management enhancement (34913)This feature improves power management on specific versions of the BTS6000, BTS 9000, and BTS 18000 by switching off power of the first of thetwo adjacent timeslots, in which they have no signals to transmit.

BTS 18000 family smart power management enhancement impacts thisdocument through the following:

Modified subsection12.7.6 BTS smart power management (page455)

Added subsection12.7.6.1 Smart power management (page 455)

Added subsection12.7.6.2 Enhanced smart power management (page 456)

Multiple ARFCN for GSM to UMTS FDD mobility (34944)This feature explains the cell reselection from a GSM network to a 3Gnetwork using the FDD or TDD technology.

Multiple ARFCN for GSM to UMTS FDD mobility impacts this documentthrough the following:

Added section12.5.4.4 GSM to 3G UTRAN FDD and TDD cellreselection (page 408)

Smart Power Management: Feature Lock at OMC-R (34956)This feature provides for the ability to unlock the smart power managementcapabilities of the BTS at the OMC-R.


411-9001-007 18.08 5 March 2010



16/511


Smart Power Management: Feature Lock at OMC-R impacts thisdocument through the following:

Updated subsection12.7.6 BTS smart power management (page455)

Multizone cell enhancement step 2 (34960)This feature improves the assignment success rate on the first TCHallocation, or on inter-zone handovers.

Multizone cell enhancement step 2 impacts this document through thefollowing:

Updated subsection12.4.6 Single BCCH enhancement (page 399)

Updated subsection12.7.2 Multi-zone cells (page 440)

2G-3G cell reselection improvement (35083)This feature explains the cell reselection improvement from a GSMnetwork to a 3G network using the FDD or TDD technology.

2G-3G cell reselection improvement impacts this document through thefollowing:

Added section2G-3G cell reselection improvement (35083) (page16)12.5.4.4 GSM to 3G UTRAN FDD and TDD cell reselection (page408)

Abis over IP on BTS6000 / BTS9000 / BTS18000 (34966)This feature allows a BTS 6000, BTS 9000, BTS 12000, BTS 18000, toconnect to the BSC using an Abis interface that runs over a packetizedIP network.

Abis over IP on BTS6000 / BTS9000 / BTS18000 impacts this documentthrough the following:

Added section11.9 Abis over IP (page 335)


Updated subsection12.3.3.5 Effect of satellite links on the Abisinterface (page 383)

Updated section12.12 Synchronization (page 470)


411-9001-007 18.08 5 March 2010



17/511

Features 17

Added subsection12.12.1 BTS Synchronization over Abis (page470)

Updated and renamed subsection BTS Synchronizationto12.12.2 Co-located BTS Synchronization (page 471)

Abis over IP on BTS S8000 / S12000 (34967)This feature allows an S8000 BTS or an S12000 BTS to connect to theBSC using an Abis interface that runs over a packetized IP network.

Abis over IP on BTS S8000 / S12000 impacts this document through thefollowing:




Updated section12.12 Synchronization (page 470)

Added subsection12.12.1 BTS Synchronization over Abis (page470)

Updated and renamed subsection BTS Synchronizationto12.12.2 Co-located BTS Synchronization (page 471)

Abis over IP: end-to-end functions (34973)This feature enables packet-based backhaul transmission as an alternativeto the TDM-based E1/T1 links on the BSC-to-BTS interface. The backhaulcarries voice and data traffic between BTSs and BSCs.

Abis over IP: end-to-end functions feature impacts this document throughthe following:

Added section1.7 IP networking (page 53)




Abis over IP: Feature Lock at OMC-R (34981)This feature allows the activation of the Abis over IP feature through theapplication of a right-to-use license at the OMC-R.


411-9001-007 18.08 5 March 2010



18/511


Abis over IP: Feature Lock at OMC-R impacts this document through thefollowing:



New Type of OMC-R Client & CIUS (35040)The feature raises the following main requirements:

Support of a T5140 server without a disk array as a hardware platformfor OMC-R workstations.

Maintenance of an SSGD (Sun Secure Global Desktop) softwareserver running separately from any other OMC-R software.

Possibility to install several CIUS and OMC-R workstations of different

versions on the same hardware.

See impacts of this feature in the following locations:

updated1.1.2 The OMC-R (page 25)

updated1.3.5 OMC-R Servers (page 39)

V18 support for GSM-R (35095)This feature indicates that the V18.0 BSS release supports the GSM-Rapplication provided that the BTSs remain in V16.0.

V18 support for GSM-R impacts this document through the following:

11.6 GSM for Railways (GSM-R) (page 320)

GSM900-UMTS900 combination on the same antenna (35147)This feature addresses the impacts for the GSM BCCH TDMA mapping toa GSM band TRX, when the GSM 900 band TRX and a UMTS 900 bandTRX are sharing a single antenna.

This feature impacted the following section:

11.11 GSM900-UMTS900 combination on the same antenna (page349)

Up to 8 ARFCN for GSM to 3G UTRAN FDD & TDD cell reselection(35179)

This feature extends the number of ARFCNs from 4 to 8 for the 3Gneighboring cells definition (FDD or TDD).


411-9001-007 18.08 5 March 2010



19/511

Other changes 19

This feature impacts this document through the following:

Added section12.5.4.4 GSM to 3G UTRAN FDD and TDD cellreselection (page 408)

Abis over IP: Support of TDM-based LMU (35240)The benefit of the feature is to allow the usage of existing TDM-basedLMU & SMLC with the feature Abis over IP, without any impact on theexisting TDM-based TruePosition solution.

This feature impacts this document through the following:

added section11.9.5.10 LMU management in IP backhaul (page 344)

Other changes

See the following section for information about changes that are notfeature-related:

Deleted all instances ofDCU2and DCU4throughout the document

Deleted sectionTandem Hybrid solution

Deleted sectionUplink mapping

Deleted all instances ofS2000 Hand S2000 L

UpdatedTable 1 "OMC-R maximum number of simultaneousinstances" (page 33)

UpdatedFigure 1 "Position of the OMC-R in the mobile network" (page27)

Updated section3.2.5.1 NIMS-PrOptimaTM (page 121)

Updated section12.4.6 Single BCCH enhancement (page 399)

Updated section12.9.1 Principles (page 461)

Updated section1.3.1 Feature lock and the licensing process (page35)

UpdatedTable 4 "Order of creating objects in the BDE" (page 72)

Updated section2.13 PCUSN configuration (page 89)

Updated section12.2.4.8 The bscCounterList object (page 361) Updated section7.7 Upgrade of BSC and TCU nodes in parallel

(page 207)

updatedTable 7 "Correspondence between DRX hardware and EFTname" (page 206)

updated7.7 Upgrade of BSC and TCU nodes in parallel (page 207)


411-9001-007 18.08 5 March 2010



20/511



411-9001-007 18.08 5 March 2010



21/511

21.

Introduction

This Operations and Maintenance Center - Radio (OMC-R) operatingdocument contains principles on general operating mechanisms and radioconfiguration.

Prerequisites

Users must be familiar with radio and networking principles.

They must also be familiar with the following documents:

Nortel GSM BSS Documentation Roadmap (411-9001-000)

Nortel GSM BSS Overview (411-9001-001)

Nortel GSM OMC-R Fundamentals (411-9001-006)

Nortel GSM OMC-R Routine Maintenance and Troubleshooting(411-9001-032)

Nortel GSM BSS ConfigurationOperating Procedures (411-9001-034)

Nortel GSM BSS Parameter Reference (411-9001-124)

Nortel GSM BSS Performance ManagementObservation CountersDictionary (411-9001-125)

Nortel GSM OMC-R Commands ReferenceObjects and Fault menus(411-9001-128)

Nortel GSM OMC-R Commands ReferenceConfiguration,Performance, and Maintenance menus (411-9001-129)

Nortel GSM OMC-R Commands ReferenceSecurity, Administration,SMS-CB, and Help menus (411-9001-130)

Nortel GSM BSS Performance ManagementObservation CountersFundamentals (411-9001-133)

Nortel GSM PCUSN Performance ManagementObservationCounters Dictionary (411-9001-211)


411-9001-007 18.08 5 March 2010



22/511

22 Introduction

NavigationThis document consists of 12 chapters:

Chapter 1 Overview (page 25)describes the major operatingprinciples of the OMC-R in the BSS network

Chapter 2 Configuration management (page 55)describesConfiguration Management, which is based on the operating objectmodel

Chapter 3 Performance management (page 93)describesPerformance Management, which is based on observation countercollection

Chapter 4 Fault management (page 137)describes FaultManagement, which is based on the feedback of notifications to theOMC-R

Chapter 5 Security management (page 165)describes SecurityManagement, which controls user access to OMC-R services andmonitors their work sessions

Chapter 6 SMS-CB management (page 179)describes SMS-CBManagement, which provides unacknowledged, short messagebroadcast facilities in radio cells

Chapter 7 Software management (page 185)describes SoftwareManagement, which manages BSS software applications

Chapter 8 Command file management (page 209)describesCommand File Management, which provides network configuration orreconfiguration facilities

Chapter 9 User facilities (page 219)describes User Facilities, whichallows users to consult the system logs, manage the system referencetime, schedule jobs, and provides access to inter-user messaging andon-line help

Chapter 10 Network graphic management (page 231)describes StateManagement, which provides a graphic aid for monitoring the network

Chapter 11 GSM evolutions (page 263)describes optional GSMextensions:

General Packet Radio Service (GPRS)

AMR

Location services

EDGE

Wireless Priority Service

GSM for Railways (GSM-R)

EDGE dynamic Abis per site


411-9001-007 18.08 5 March 2010



23/511

Navigation 23

Tandem-Free Operation (TFO)

Gb over IP

Chapter 12 Radio configuration principles (page 353)introduces BSSradio configuration principles. It describes the relations between radio

operating parameters and the effects on the BSS.

Appendix A BTS TEI Numbering Rules (page 483)gives the TEInumbering rules for each BTS equipment.

Appendix B GSM Equivalences (page 503)presents the equivalencebetween radio parameter names used on the OMC-R Man-Machineinterface and the GSM series recommendation names.

Appendix C Network Level Presence Identification of eDRX, ePA,and HePA (page 507)describes how to differentiate in a system vieweDRX from DRX and ePA and HePA from PA.


411-9001-007 18.08 5 March 2010



24/511

24 Introduction


411-9001-007 18.08 5 March 2010



25/511

25.

Chapter 1 Overview

1.1 Overview of network operations1.1.1 PCUSN performance management and preventative maintenance

1.1.1.1 PCUSNThe preventive maintenance management functions for the Packet ControlUnit Support Node (PCUSN) are performed by the Network Information

Management System (NIMS) PrOptimaTM Performance Management tool,which is designed by third-party Mycom International. NIMS-PrOptimauser manual PRO-SUP-USM-NOR- 041-1.04-EN describes how to usethe modules offered in the NIMS-PrOptima solution including the QOSWarnings module, which performs Quality of Service (QoS) functions forthe PCUSN.

1.1.2 The OMC-RThe OMC-R is the Operations and Maintenance Center for the BSS Radiosubsystem.

A Base Station Subsystem (BSS) includes a Base Station Controller (BSC)connected:

to TransCoding Units (TCUs) for access to the MSC

to Packet Control Unit Support Node (PCUSN) for access to the SGSN(Serving GPRS Support Node)

In addition, the BSC manages a group of Base Transceiver Stations(BTSs).

The BSS and OMC-R are organized in a hierarchical tree structure:

A BSC can manage several BTSs but a BTS is connected to only one

BSC.

A BSC can be connected to several TCUs but a TCU is connected toonly one BSC.

An OMC-R can manage several BSCs but a BSC is connected to onlyone OMC-R.


411-9001-007 18.08 5 March 2010



26/511

26 Chapter 1 Overview

The BSCs and the OMC-R in the Public Land Mobile Network (PLMN)are connected using the operations and maintenance network interface(OMN).

OMC-R workstations of different versions can be installed on the same

hardware.

For more information about the position of the OMC-R in the mobilenetwork, seeFigure 1 "Position of the OMC-R in the mobile network"(page 27).

1.1.3 Major operating principlesThe OMC-R provides the following services to operate a digital mobilenetwork:

hardware and software resource management

control of BSS operating conditions

control of BSS/OMC-R links:

Ethernet link (BSSs and OMC-R communicate by Ethernet link forBSC 3000)

The Configuration Management function, including OMN Access andSoftware Management sub-functions, performs this task.


411-9001-007 18.08 5 March 2010



27/511


28/511


network observations that provide users with the information requiredto monitor operations in order to optimize performances. ThePerformance Management function performs this task.

network maintenance repairs, malfunctions, and system failures. The

OMC-R saves all the information it receives and analyzes it in real timeor stores it for a later time. It sends alarm event messages to usersto facilitate equipment reconfiguration and the analysis of test results.The Fault Management function performs this task.

network preventive maintenance: the OMC-R enables the user tomanage growing networks and to anticipate equipment failures,outages, and quality of service deterioration. It allows the user toconfigure, schedule and activate preventive maintenance tests onBSS sub-systems and to view the associated results. The PreventiveMaintenance modules (one module for each test) perform this task.They can be installed as plug-ins without any OMC-R restart.

network protection which consists of controlling system usersaccess rights. Only a limited number of users can access all OMC-Roperations. The Security Management function performs this task.

network operations services that optimize user working conditions. TheCommand File Manager and User Facilities provide these services.

To facilitate the commissioning of new BSS versions when hardwareand software are upgraded, the OMC-R provides an effectiveFile Transfer Service with the BSSs that allow users to manageconfiguration files from the OMC-R. The Software Managementfunction uses this service to manage software and the Performance

Management function to collect certain types of observation data.

The OMC-R operations require the administration of its own resources:

The administration task consists of organizing its hardware andsoftware entities (and their use) to archive and restore the managedsystem data and specific OMC-R application data required to monitorits own hardware and software operations. The OMC Administrationfunction performs this task.

The OMC-R Data Server, or SDO, is used to export OMC-R data toexternal applications.

The Man-Machine Interface (MMI), developed for network management,provides a user-friendly communication interface. For more informationabout the MMI, see Nortel GSM OMC-R Commands ReferenceObjectsand Fault menus(411-9001-128) toNortel GSM OMC-R CommandsReferenceSecurity, Administration, SMS-CB, and Help menus(411-9001-130).


411-9001-007 18.08 5 March 2010



29/511

1.1 Overview of network operations 29

This document reviews the BSC and OMC-R digital mobile networkmanagement functions and details the major operating principles, apartfrom the OMC Administration function. For more information about theOMC Administration function, see Nortel GSM OMC-R Fundamentals(411-9001-006).

OMC-R centralized installation and upgrade service featureThis feature is used for OMC-R installations and upgrades. It isbased on Sun MicrosystemsTM JumpStart TM, LiveUpgrade and FlashArchive features, which facilitate the installation and upgrade of SunMicrosystemsTM SolarisTM machines by automating JumpStartTM,performing Operating System Upgrades On-Line (LiveUpgrade) andspeeding-up the installation and upgrade phase (Flash Archive). Coupledwith a GUI sequencer, this feature offers a full "Hands Free" efficientand automatic installation and upgrade package for the entire OMC-R

system. For more information, seeNortel GSM OMC-R Fundamentals(411-9001-006).

OMC-R Solaris jumpstart automated installation featureThis feature is an automatic installation process available in the SunMicrosystemsTM SolarisTM operating environment. It allows systemadministrators to categorize machines on their network and automaticallyinstall systems based on the category to which a system belongs. TheSolarisTM JumpStartTM Automated Installation feature provides the systemadministrator with the following advantages:

simplifies installations

speedFaster than CD-ROM installation allows unattended installation

replicationsame systems across the enterprise

All SolarisTM base installations require some basic configuration. With theJumpStartTM, Sun has enabled the system administrator to avoid repetitivetasks associated with bringing a Sun system online.

OMC-R system patch automation feature

This feature is used to manage OMC-R system patches automatically. Itwas added to the install_data tool, which is normally used to either installor apply patches and plug-ins in installed OMC-R configurations. TheOMC-R system patch automation feature performs the following functions:

installs and applies system patches automatically

performs fallback functions from system patches

displays the system patch level


411-9001-007 18.08 5 March 2010



30/511


The install_data tool performs these functions from an application scriptwhich is delivered with the patch by the Nortel team responsible forsystem patches. The system patch automation feature will be introducedprogressively as system patches are delivered with an applicationscript. For more information, seeNortel GSM OMC-R Fundamentals

(411-9001-006).

1.2 BSC 3000 functional characteristics1.2.1 Facilities provided

The BSC 3000 provides the following:

Radio resource management which:

processes radio access

allocates radio channels (traffic and signalling)

monitors radio channel operating states

Call processing which: sets up and releases terrestrial and radio links

transfers messages between the mobile stations and:

the MSC through TCU 3000 and the BTS

the SGSN through PCUSN and the BTS

commutes the switch channels between BTSs and MSC throughTCU 3000

commutes the packet channels between BTSs and SGSN throughPCUSN

Call sustaining procedures which:

process measurements from mobile stations and the BTSs

launches:

the power control procedures

the handover procedures

BTS management which:

sets physical channels, to control transceivers (TRX)

initializes the TRX and sets the channels

supervises BTS operating states

provides BTS reconfiguration, if needed

updates system parameters

TCU management

BSC 3000 defense which:


411-9001-007 18.08 5 March 2010



31/511


detects and corrects failures and operating anomalies

provides local defense by isolating faulty units, to avoid problemspreading

provides equipment unit reconfiguration using redundant units

These functions include the module switching and restartmechanisms for the BSC 3000.

1.2.2 Main systemsThe BSC 3000 houses the following main systems:

a cooling system

an alarm system

a power system

a control node an interface node

a PCM switching system

For more information about these systems, seeNortel GSM BSC3000/TCU 3000 Fundamentals (411-9001-126).

1.2.3 Software architectureThe BSC 3000 software architecture is based on a network model ofprocessors called a core system, which can be tailored to fit into differenthardware structures. The core system is divided into logical process units.

A set of modules which house boards and processors provide each logicalunit with the processing power they need.

The main types of processing unit are split up as follows:

for the control node:

the OMU modules enable the following basic BSC 3000 operatingfunctions:

MMS module management

BSC 3000 initialization sequences (loading the programs anddata into the different processors)

monitoring correct processor operations

OMC-R access and related function management

interface node

the TMU modules enable:


411-9001-007 18.08 5 March 2010



32/511


centralized call processing functions

communication with the BTS (such as traffic management,radio environment monitoring, message broadcasting, andtraffic overload control)

communication with the MSC (SS7 signalling channels) communication with the SGSN

TCU 3000 management

the ATM_SW (also named CC-1) modules enable:

conversion of the ATM 25 to the SONET interfaces (ATM 155)

conversion of the LAPD and SS7 channels on each TMUmodule through the VP-VC on AAL1

for the interface node:

the ATM-RM modules enable:

conversion of the AAL1 to S-link interfaces

conversion of the AAL5 to Spectrum messaging interfaces

the CEM modules enable:

management of the ATM-RM, 8K-RM and LSA-RC

management of the mixing order for the 64K and the 8Kswitching parts

the 8K-RM modules enable:

running of the mixing order to the 8K switching part

the LSA-RC enable:

management of the PCM/defect monitoring

conversion of the PCM to S-link interfaces

to support the optical interface:

CEM2 modules replace the CEM modules (the CEM2 modulesmanage ATM-RM, HSA-RC, and LSA-RC)

the 8K-SRT modules are removed

HSA-RC (High Speed Access) are introduced with the

equivalent role as the LSA-RCFor more information, see also1.2.4.5 Impacts on OAM (page34).

1.2.4 Electrical and optical configurationsV17.0 introduces an optical BSC 3000 configuration (in addition to theexisting pre-V17.0 configuration).


411-9001-007 18.08 5 March 2010



33/511


1.2.4.1 TerminologyIn this document, the following terminology is used:

"electrical BSC 3000" is used to refer to the configuration that supportselectrical connectivity (that is, the configuration that existed before

V17.0) "optical BSC 3000" is used to refer to the configuration that supports

both electrical and optical connectivity (that is, the configuration,introduced in V17.0)

"BSC 3000" is used to refer to a BSC 3000 of either configuration (thisterm is used where it is not necessary to distinguish between the twoconfigurations)

1.2.4.2 ConfigurationsThe configuration, technology used for connection, and implementation

of two new High Speed Access (HSA) cards distinguishes the twoconfigurations.

The BSC 3000 (both electrical and optical) can support 1 500 TRX andTDMAs.

The maximum number of transceivers, per OMC-R, are 14 400 for basiccapacity, 19 200 for SV880, and 28 800 for SV890 and T5140.

1.2.4.3 Maximum number of OMC-R instancesSince they are distributed on several interfaces (A, Abis, Agprs, and Ater),

the number of instances of the LapdLink and PcmCircuit objects is notproportional to the number of instances of the Transceiver object.

The OMC-R can manage the maximum number of simultaneous instancesof the different classes shown in the following table.

Table 1OMC-R maximum number of simultaneous instances

Object

Basic

Capacity

SF V880/V890

/T5140 (HC)

Enhanced

Capacity

SF V880

(VHC)

EnhancedCapacity

SF V890 (UHC)

Basic

Capacity

T5140/ST2510

(UHC)

Channel 115200 153600 230400 230400

frequencyHoppingSystem

14400 19200 28800 28800

LapdLink 32520 43360 64160 64160

PcmCircuit 13200 17600 17600 17600


411-9001-007 18.08 5 March 2010



34/511


Table 1OMC-R maximum number of simultaneous instances (contd.)

Object

BasicCapacity

SF V880/V890

/T5140 (HC)

EnhancedCapacity

SF V880

(VHC)

EnhancedCapacity

SF V890 (UHC)

BasicCapacity

T5140/ST2510

(UHC)

Transceiver 14400 19200 28800 28800

TransceiverEquipment 14400 19200 28800 28800

1.2.4.4 ConnectivityConnectivity is one of the key drivers so that the BSC 3000 can supportfeatures that require additional backhaul. Using optical carriers cansignificantly increase the BSC 3000 connectivity.

The BSC 3000 evolves from a BSC 3000 that is fully electrical to a BSC

3000 which is dual electrical and optical, depending on the types ofinterfaces supported.

The introduction of optical carriers:

is fully compatible with the BSC 3000 installed base

increases the BSC 3000 connectivity from 126 E1 / 168 T1 to 231 E1 /308 T1

reduces site cabling

An electrical BSC 3000 supports up to six lsaRc (126 E1 / 168 T1).

An optical BSC 3000 (that is, dual electrical and optical) supports up to fivelsaRc (105 E1 / 140 T1) and two hsaRc (126 E1 / 168 T1).

1.2.4.5 Impacts on OAMAt the OAM level, the main impact consists in adding to the object modelthe equivalent of the lsaRc and iem objects for the optical interfaces.

These objects are:

hsaRc

iomwhere:

lsaRc = Low speed access Resource Complex

iem = Interface Electrical Module


411-9001-007 18.08 5 March 2010



35/511


hsaRc = High speed access Resource Complex

iom = Interface Optical Module (a generic name object for OC-3 andSTM-1)

The characteristics of the hsaRc and iom objects are mainly the same asthe lsaRc and iem objects. These new objects lead to a new architecturefor the BSC 3000 and a new MMI.

1.3 OMC-R features and functionsThe OMC-R enables BSS subsystem operations and maintenanceoperations in digital GSM and dualband mobile networks. It performs thefunctions required by the network operator for management.

1.3.1 Feature lock and the licensing processThe activation of certain features is now controlled by the OMC-R. Thesefeatures are locked by default. In order to unlock these features, thecustomer has to request a specific set of license codes for each neededfeature. These licenses are usable on one and only one OMC-R. Sucha license makes possible the use of 4 000-Erlang capacity; TRX, EDGE,AMR and Optical features (according to the license bought) on a specificOMC-R, whatever the number of BSC, BTS site manager, BTS, DRX orany other element that the OMC-R manages.

When the need for an increase is identified over a current right-to-use(RTU), a special license is needed. This license is provided by Nortelagainst a proof of purchase (either a Purchase Order or Contract) and canbe obtained by contacting your Nortel account manager. It is used to take

into account the new additional RTU at the OMC-R level.

ATTENTIONThese licenses need to be accessible on the OMC-R sites at the beginning ofthe OMC-R upgrade to V18.0 P&C1.

The licenses may be imported and exported between OMC-Rs using thelicense management tool. For more information, see Nortel GSM OMC-RRoutine Maintenance and Troubleshooting (411-9001-032).

1.3.2 Introduction to OMC-R data server (SDO)The OMC-R Data Server, or SDO, is installed by the manufacturer when

the system is commissioned.

The SDO Data Server application is a communication interface betweenthe OMC-R and the peri-OMC applications. It does the following:

processes data records and radio network configuration parameters inan ASCII readable format:


411-9001-007 18.08 5 March 2010



36/511


counters of the Fast Statistic Observation - OFS records

counters of the General Statistic Observation - OGS

counters of the PCUSN observation

counters of the PCU/BSC observation

call tracing records

call path tracing records

distributions on radio measurements

call drop data

interference matrix data

cellTiering records

fault and stateChange notification records

radio network configuration parameters

zones of interest (ZI) of the connected workstations

OMC-R session log

bts inventory data

transfers OMC-R data in the following ways, depending on data typesand SDO configuration parameters:

periodically (up to one day)

at start time (only for automatic transfer mode), to recover thecurrent day data records produced at the OMC-R level since the

last SDO has been stopped.

on event reception: each time a data record is received by theOMC-R

on demand: these transfers apply to data collection period definedas part of one or more days using the beginSearchTimeand theendSearchTimeinput criteria.

builds per-record reports for:

observation data

builds per-period transfers for:

fault and stateChange notifications

builds consolidated reports (daily or user-defined time interval) for:


411-9001-007 18.08 5 March 2010



37/511


observation data

call tracing data

call path tracing data

fault and stateChange notifications

builds reports for:

radio network configuration

OMC-R system session log

zone of interest

provides the following administration facilities:

start and stop

suspend and continue delay management

survey and defense mechanisms

daily purge

defense purge

on-demand purge

data archival

log SDO activity

automatic data file compression algorithm

transform and stores data on radio distribution measurements

For more information, see3.2.6 Obtaining distributions on radiomeasurements (page 123).

transform and stores data on call drops

For more information, see3.2.7 Call drop analysis (page 128).

transform and stores interference matrix data

For more information, see3.2.8 Generating an Interference Matrix

(page 132).

BTS inventory is also available as a CSV file that can be used by a thirdparty post-processing inventory system. The retention period of inventoryfiles is seven days plus the current day (SDO).


411-9001-007 18.08 5 March 2010



38/511


For more information, seeNortel GSM OMC-R Fundamentals(411-9001-006) andNortel GSM OMC-R Commands ReferenceSecurity,Administration, SMS-CB, and Help menus (411-9001-130).

1.3.3 Disaster recovery

If a disaster occurs on an OMC-R, all of the supervision is lost on thatOMC-R. The disaster plan describes how an OMC-R can be reconfiguredto minimize the amount of time a loss of supervision lasts when an OMC-Rfails.

The disaster plan is divided into the following three main parts:

Configuration: sites are configured to perform daily backup operationsas part of the disaster recovery plan process.

Recovery: a recovery of the backed-up OMC-R configuration occurs ona spare configuration to replace the failed OMC-R.

Site restoration: the site which failed is restored to normal operations.

For more information about the disaster recovery plan, seeNortel GSMOMC-R Fundamentals (411-9001-006).

1.3.4 Managing and monitoring the network with the OMC-RThe OMC-R manages resources, initializes the system, configuresBSS entities, and controls the start and end of operations. The OMC-Rmanages the entire radio chain or the OMUs.

The OMC-R monitors the network from the Airinterface to the Ainterface. It stores BSC observation data and allows users to analyze themeasurements in real time or at a later time.

The OMC-R monitors the GPRS network and reports observations andalarms. The OMC-R enables dynamic queries.

The OMC-R provides system maintenance facilities by reportingmalfunctions and failures, saving the information on disk, and enablingequipment reconfiguration.

The OMC-R controls system access rights that vary according to the user.

A graphic user interface enables user dialogues for network management.The user can enter commands, view traffic conditions, and eventualmalfunctions.

The OMC-R also provides services for backing up data to cartridges suchas fault files, observation reports, trace data, and operating data files.


411-9001-007 18.08 5 March 2010



39/511


40/511


Figure 2OMC-R design

1.4.2 ObjectsBSS and OMC-R interchanges are based on an object model definition. Allthe transactions between BSSs and OMC-R and between OMC-R agentand manager use a specific application data description.

The managed objects check the managed object defined by ISO (ISO/IEC7498-4 OSIBasic reference model - Management framework):

"A managed object is defined in terms of its parameters, the operations itcan perform, the notifications it can issue, and its relationship with otherobjects".

The OMC-R manager recognizes the BSS subsystem by the objectsthat describe it on the Q3 interface (as the user sees the objects onthe Man-Machine interface). The OMC-R agent recognizes the BSSsubsystem by the objects that describe it on the Q3 and OMN interfaces.

BSS subsystems and OMC-R agent are described by objects managed onthe Q3 interface. Each object describes a function or an equipment.

1.4.3 DatabasesObjects are managed in two databases.

The OMC-R operations database (BDE) is the main database. It ismanaged by the OMC-R and built as the objects are created. It isstored on the OMC-R agent disks.


411-9001-007 18.08 5 March 2010



41/511


The BDE is automatically updated after each operation and containsall the BSS objects, and certain specific OMC-R objects that are notknown to the BSC.

The BSC application database (BDA) is stored on the BSC disk. It isbuilt from the BDE. The BSC database building operation is controlledby users.

To allow the system to function correctly, the two databases must beconsistent. Users can check their consistency by using an auditingcommand. The system warns the user if the two bases are inconsistent,by sending a specific message in response to the command. For moreinformation, seeFigure 3 "Operations database and application database"(page 42).


411-9001-007 18.08 5 March 2010



42/511


Figure 3Operations database and application database

1.4.4 Object classes and instancesAn object, as defined above in terms of parameters, operation notifications,and relationships is a generic object. The same information structure

describes same-kind individual objects that can be configured and behavedifferently.

For example, the same information structure is used to describe all thebts objects modelling the radio cells under OMC-R management control.The description differentiates a non-operational cell C1 configured withtwo TRX/DRXs at a given time from an operational cell C2 configured withfour TRX/DRXs at the same time.


411-9001-007 18.08 5 March 2010



43/511


To avoid any ambiguity between the generic object and the individualobject, a difference is made between the object class and the objectinstance. In the example above, C1 and C2 are both instances of the btsobject class.

1.4.5 ParametersAll the objects in a same class are described in the same way by a set ofparameters. The values of these parameters vary according to the object.

There are three kinds of parameters:

Permanent parameters,which are defined by the users

They are recorded in the BDE and BDA databases. Most of them aremandatory and are defined with the object that uses them. Some ofthem are optional and their value depends on the radio subsystemconfiguration. They are designated by the abbreviation DP (PermanentData) in this document.

Dynamic parameters,which are not controlled by the users

They are not recorded in the databases. The BSC manages dynamicparameters that are updated by BSC applications and can beconsulted on request. They are designated by the abbreviation DD(Dynamic Data) in this document.

Internal parameters,which are managed from the OMC-R

They are recorded in the BDE database and cannot be modified byusers. They supply additional information on the object configuration ata given time and can be consulted on request. They are designated bythe abbreviation DI (Internal Data) in this document.

For more information about these parameters

In alphabetical order, seeNortel GSM BSS Parameter Reference(411-9001-124).

Grouped according to the objects, seeNortel GSM OMC-R CommandsReferenceObjects and Fault menus (411-9001-128).

1.4.6 OperationsOperations on objects are commands that the user sends to the OMC-Ron the Man-Machine interface. They allow users to communicate with theOMC-R and update the databases when necessary.

The OMC-R checks the command semantics before forwarding thecommands to the BSC to ensure that it only receives commands that arelikely to be correctly executed.


411-9001-007 18.08 5 March 2010



44/511


The same set of operations apply to all the objects in a given class. Themain types of operation are as follows:

Create an object.

Delete an object.

Lock or unlock an object.

Set the permanent parameters of an object.

Display permanent and internal parameters of an object

Display permanent, internal, and dynamic parameters of an object

Audit a BDA to check consistency.

Perform an action on an object.

1.4.7 Unsolicited messagesUnsolicited messages sent by the managed objects are translated intonotifications that provide users with information on network operatingconditions.

The same types of message apply to all the objects in a given class.These messages are grouped as follows:

software anomaly

hardware fault

warning

state change parameter value change

restart

BIST result

purge

observation

trace

build BDA request


411-9001-007 18.08 5 March 2010



45/511


1.5 OMN access management1.5.1 BSC 3000 OMN access management

1.5.1.1 OverviewThe Operations and Maintenance Network (OMN) is a packet switcheddata network used for communications between the OMC-R and the

BSS in the Public Land Mobile Network (PLMN). The OMN is a layeredcommunication network complying with the layers of the OSI referencemodel.

The BSC 3000 cabinet and the OMC-R communicate through an OSIprotocol stack which covers the following needs:

physical connection capability

LAN/RFC1006 (TCP/IP): two Ethernet links at up to 100 Mbps.

association management capability

The associations manager is interfaced upon the Transport layer API.

the FTAM (File transfer Access Management)

The FTAM contains the following characteristics:

only the responder capability is needed

restart and recovery capabilities are used

content list types needed: NBS9, FTAM-1 and FTAM-3

The OSI protocol stack is compliant with the following recommendations:

General

ISO 7498/ITU-T X.200Basic Reference model of Open Systems Interconnection

ITU-T Q.811

Lower layer Protocol Profiles for the Q3 Interface

ITU-T Q.812

Upper Layer Protocol Profiles for the Q3 Interface

Application Layer

ISO 8571

File Transfer, Access and Management Protocol ISO 8649/ITU-T X.217

Association Control Service Element Service

ISO 8649/ITU-T X.227

Association Control Service Element Protocol

Presentation Layer


411-9001-007 18.08 5 March 2010



46/511



Connection-Oriented Presentation Definition


Connection-Oriented Presentation Protocol


ASN 1, Basic Service Element Protocol

Session Layer


Connection Oriented Session Service Definition


Connection Oriented Session Protocol

Transport Layer


Connection Oriented Transport Service


Connection Oriented Transport Protocol Class 4,2,0

RFC1006

OSI Transport Services on top of TCP

Network Layer

ISO 8208/ITU-T X.25

Packet Level Protocol for DTE


Network Service Definition

Datalink & Physical Layer

Essentially an Ethernet link:

LAN/RFC1006 (TCP/IP): two Ethernet links at up to 100 Mbps.

The OMC-R has two OMN network access points. Both access pointsare used to handle communications with the BSC 3000 on a load-sharing

mode. If one access is inhibited, the other handles its load until the otheraccess is restored.

The following associations with a BSS can be opened on the OMNinterface:

INIT association (initialization)

FAULT association (fault message transfer)


411-9001-007 18.08 5 March 2010



47/511


MARK association (marking message transfer)

PERF association (observation message transfer)

TRACE association (trace message transfer)

TRANSAC association (TGEs) UPDATE association (on-line build operation)

The INIT and FAULT associations are opened when the BSS/OMC-R linkis established. The INIT association is opened first.

The MARK, PERF, TRACE, and TRANSAC associations are opened whenthe BSC 3000 application database (BDA) is being built.

1.5.1.2 OMN access equipmentThe standard OMC-R configuration includes one or two working server(s)

and three local workstations.

Figure 4 "OMC-R communication equipment for BSC 3000" (page48)shows the OMC-R equipment connected to an Ethernet Local AreaNetwork (LAN) and the OMN connection between the OMC-R server and aBase Station Controller (BSC 3000). The OMN LAN connection betweenthe OMC-R server and the BSC 3000 uses two Ethernet links, which havea combined capacity up to 100 Mbps.

For more information about the OMC-R equipment, see Nortel GSMOMC-R Fundamentals (411-9001-006).


411-9001-007 18.08 5 March 2010



48/511


Figure 4OMC-R communication equipment for BSC 3000

1.5.1.3 BSS equipmentThe BSC 3000 provides the BSS with OMN access points. The two accesspoints of the BSC 3000 are defined by Ethernet addresses. One is thepreferred address, the other is used as a backup address.


411-9001-007 18.08 5 March 2010



49/511


1.5.1.4 TerminalsIn addition to local workstations, the system contains the following:

remote workstations, identical to the local workstations, and connectedto the OMC-R.

X terminals, selected by the operator, and connected across a localarea network through local or remote workstations

remote access terminals, connected to the OMC-R by telephone linkand modem through a terminal server. The remote access terminals(RACEs) are PCs running under Windows.

1.5.1.5 Link managementPort selection principles Each BSS has one link with the OMC-R.

A BSS/OMC-R link uses an Ethernet Network.

The network operator selects the access port for OMC-R communicationswhen the link is created. The OMN Access Management function canautomatically select the port to use on the basis of equal loads.

Identifying a link Each BSS/OMC-R link in the OMC-R operationsdatabase (BDE) is described by a bscMdInterface object. Specificcommands on this object allow users to manage the BSC 3000 circularfiles that contain spontaneous messages transmitted by the BSC 3000.

Creating a link The OMC-R always initiates BSS/OMC-R link setup. The

OMC-R is the calling party (outgoing connections) and the BSS are thecalled parties (incoming connections).

Since OMC-R and BSC 3000 each have two OMN access points, theaccess used to set up a link are selected as follows:

The preferred BSC 3000 Ethernet address is used. If the connectionfails, the backup address is used.

The access port is selected by the user or the OMN AccessManagement function.

Link states A BSS/OMC-R link is managed as an equipment. ThebscMdInterface object that describes the link is characterized by three ISOstates: administrativeState, operationalState, and availabilityStatus.

Setting up a link The OMC-R agent attempts to set up a BSS/OMC-Rlink when the bsc e3 object is created and if the provided bscMdInterface


411-9001-007 18.08 5 March 2010



50/511


object describing the link is unlocked. Users may request link setup if thelink has been taken out of service (bscMdInterface object locked).

The operation consists of setting up a first transport connection from thelist of parameters selected in descending order of preference.

If link setup procedure fails, attempts to reconnect the link are made atintervals defined in static configuration data.

Table 2OMC-R port selection by the user

1st choice destination = preferred BSC 3000 access

2nd choice destination = backup BSC 3000 access

Table 3

Automatic OMC-R port selection

1st choice destination = preferred BSC 3000 accessOMC-R port = least loaded port

2nd choice destination = backup BSC 3000 accessOMC-R port = least loaded port

3rd choice destination = preferred BSC 3000 accessOMC-R port = most loaded port

4th choice destination = backup BSC 3000 accessOMC-R port = most loaded port

Releasing a link

A BSS/OMC-R link is released by locking the bscInterface object thatdescribes the link to disconnect the link between the OMC-R and the BSC3000. The link remains created but the BSC 3000 is out of reach andcannot communicate with the OMC-R.

Deleting a link

User requests to delete a BSS/OMC-R link must be confirmed and areaccepted if the bsc object has been deleted. It is then impossible tocommunicate with the BSS.

Fault handling

Since the OMC-R always initiates BSS/OMC-R link setup, any disconnectindication for which the user is not responsible is considered abnormal.


411-9001-007 18.08 5 March 2010



51/511


The OMN Access Management function sends a hardware fault messageto the Fault Management function that generates a notification for OMC-Rusers.

Periodic attempts are made to set up the link. When the OMC-R starts up,

the value of the interval between two attempts is set with a minimum valuedefined in static configuration data. It is reset when the connect attemptis successful. It is multiplied by two after each unsuccessful attempt untilit reaches a maximum value defined in static configuration data. Whenthe maximum value is reached, the attempts are stopped and the link isdeclared defective.

1.5.1.6 Transport layer configurationThe values of transport layer operating parameters are stored in OMC-Rsystem files. They must be compatible with the connected BSS transportlayer definitions.

1.5.1.7 Management mechanismsLink configuration at start-up BSS/OMC-R links are configured fromthe information recorded in the OMC-R operations database (BDE).

1.5.1.8 Restoring links when servers switch overThe server switchover mechanism is used when the OMC-R has twoservers operating in duplex mode (standard configuration). It does notapply in single-server configurations with redundancy.

The standby server is declared active when the system switches over.

Since the operations database managed by the standby server is an exactcopy of the other server database, the link restoration mechanism usesthe information in the ex-standby server database to automatically restoreBSS/OMC-R links.

The normal start-up procedure is used.

Reconfiguring links at shutdown When the OMC-R shuts down,the OMN Access Management function automatically releases all theBSS/OMC-R links without changing their administrativeState.

When the OMC-R starts up again, the link configuration is restored as itwas before shutdown.

Choosing the OMC-R Channel There are two Ethernet ports whichmay be called by the OMC-R, each with a different IP address. Both areaccessible for local maintenance with a local TML, but only the active onewill answer to the OMC-R call.


411-9001-007 18.08 5 March 2010



52/511


The operator can choose to switch ports according to the active OMU.

If the active Ethernet link fails, the OMC-R tries to connect to the secondIP address. Because the second IP address corresponds to the passiveOMU, no connection will be established.

1.6 OMC-R network configurationNetwork configuration includes the OMC-R server and station and everydevice that is used to connect the OMC-R components either through aLAN or a WAN.

An OMC-R server uses TCP/IP over Ethernet network connection.

1.6.1 TCP/IP over EthernetTCP/IP over Ethernet can be used to connect the OMC-R server to:

Clients: Workstations

Q3 External Manager

Network elements: BSC 3000, PCUSN

The recommended Ethernet bandwidth is 1000baseT/100baseT FullDuplex per machine. The Sun Fire V890 and T5140/ST2510 can support aGigabit LAN.

A LAN, with one or more IP subnets, is usually used. However, whenequipment is located far from the OMC-R server, a WAN is requiredbetween the two LANs. For more information, seeFigure 5 "OMC-R WAN"

(page 52).

Figure 5OMC-R WAN


411-9001-007 18.08 5 March 2010



53/511

1.7 IP networking 53

1.7 IP networkingUsing IP networking, the Gb over IP and Abis over IP features areintroduced. The Gb over IP enables the Gb interface to operate over anIP network and mostly affects the network service (NS) layer of the Gb

protocol stack in the Nortel PCUSN, while the Abis over IP feature aimsto enable a packet-based voice and data traffic between the BSC to BTSAbis interface.

For more information about the Abis over IP feature, see 11.9 Abis overIP (page 335)and12.15 Abis over IP (page 479).

For more information about the Gb over IP feature, see 11.10 Gb overIP (page 345).


411-9001-007 18.08 5 March 2010



54/511



411-9001-007 18.08 5 March 2010



55/511

55.

Chapter 2 Configuration management

2.1 Object classesThe system configuration is based on object class definitions. Figure6 "Object main tree structure" (page 56)toFigure 9 "Network subtreeobjects" (page 58)show the tree structure of the configuration objectsmanaged on the OMC-R:

main tree structure

omc subtree

md subtree

network subtree

bsc subtree

The present paragraph only details the objects that model the radiosubsystem, which are managed by the OMC-R Configuration Managementfunction, that is, the bscMdInterface object of the md subtree and the

objects of the bsc subtree.

2.1.1 OMN access managementThe md object describes the OMC-R agent that mediates Q3 objectsand OMN objects, and handles exchanges with the BSSs on theOMN interface. The md object is unique to the OMC-R and is createdautomatically by the system.

The bscMdInterface objects describe the BSS/OMC-R links. They dependon the md object.


411-9001-007 18.08 5 March 2010



56/511

56 Chapter 2 Configuration management

OMN Access Management is a Configuration Management subfunction.It controls BSS/OMC-R links and:

Ethernet links for BSC 3000

2.1.2 Radio subsystem configurationEach object that describes a radio subsystem item depends directly orindirectly on the bsc object that models the BSC and is identified by aspecific number.

Equipment

The bsc objects describe the architecture and the hardware of the BSCsmanaged on the OMC-R. They allow users to manage processing OMUmodules for the BSC 3000 and date/time.

The pcmCircuit objects describe external BSC (Abis, Agprs and Aterinterfaces) and TCU (A interface) PCM links.

The lapdLink objects describe the Level 3 links used by the BSCs forLAPD signalling.

Figure 6

Object main tree structure


411-9001-007 18.08 5 March 2010



57/511

2.1 Object classes 57

Figure 7OMC subtree objects

Figure 8MD subtree objects


411-9001-007 18.08 5 March 2010



58/511


Figure 9Network subtree objects


411-9001-007 18.08 5 March 2010



59/511

2.1 Object classes 59

Figure 10BSC 3000 subtree objects (electrical)

Figure 11BSC 3000 subtree objects (optical)


411-9001-007 18.08 5 March 2010



60/511


Figure 12BSC 3000 subtree objects (optical high capacity)

A interface

The signallingPoint and signallingLinkSet objects describe the A interfaceon BSC and MSC ends, respectively.

The transcoder objects describe the remote transcoding units (TCUs),connected to the BSC but install

NORTEL GSM Principles(1).pdf

Documents

Transcript of NORTEL GSM Principles(1).pdf