System Informatio - GSM Overview (Motorola)

CHAPTER 1
GSM SYSTEM MANUAL

INTRODUCTION
CHAPTER 2
INTRODUCTION TO
MOTOROLA GSM
CHAPTER 3
BSS GENERAL
DESCRIPTION
CHAPTER 4
OMC-R OVERVIEW
CHAPTER 5
BSS SOFTWARE RELEASE
FEATURES
CHAPTER 6
OMC-R SOFTWARE RELEASE
FEATURES
CHAPTER 7
GLOSSARY
INDEX
SYSTEM INFORMATION
GSM OVERVIEW
GSM SOFTWARE RELEASE 6 (Horizon II)
GSR6 (Horizon II)
68P02901W01-M
68P02901W01-M
GSM SOFTWARE RELEASE 6 (Horizon II)
GSR6
(Horizon II)
SYSTEM INFORMATION
GSM OVERVIEW
Software Release GSR6 (Horizon II)
System Information
GSM Overview
E Motorola 1993-2003
All Rights Reserved
Printed in the UK.
System Information: GSM Overview

02 May 2003
68P02901W01-M
GSR6 (Horizon II)
Copyrights, notices and trademarks

Copyrights
The Motorola products described in this document may include copyrighted Motorola computer
programs stored in semiconductor memories or other media. Laws in the United States and other
countries preserve for Motorola certain exclusive rights for copyright computer programs, including the
exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any
copyright Motorola computer programs contained in the Motorola products described in this document
may not be copied or reproduced in any manner without the express written permission of Motorola.
Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by
implication, estoppel or otherwise, any license under the copyrights, patents or patent applications of
Motorola, except for the rights that arise by operation of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license
agreement and may be used and/or disclosed only in accordance with the terms of the agreement.
Software and documentation are copyright materials. Making unauthorized copies is prohibited by
law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored
in a retrieval system, or translated into any language or computer language, in any form or by any
means, without prior written permission of Motorola.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola
assumes no liability resulting from any inaccuracies or omissions in this document, or from the use
of the information obtained herein. Motorola reserves the right to make changes to any products
described herein to improve reliability, function, or design, and reserves the right to revise this
document and to make changes from time to time in content hereof with no obligation to notify any
person of revisions or changes. Motorola does not assume any liability arising out of the application
or use of any product or circuit described herein; neither does it convey license under its patent
rights of others.
Trademarks
and MOTOROLA are registered trademarks of Motorola Inc.

Intelligence Everywhere, M-Cell and Taskfinder are trademarks of Motorola Inc.
All other brands and corporate names are trademarks of their respective owners.
.
.
.
ii

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Contents
Issue status of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
Motorola manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
GMR amendment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
GMR amendment record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
Chapter 1
GSM system manual introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
Introduction to Motorola GSM documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

About this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of GSM customer support manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
13
13
Documentation coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manual coding system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Order number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
14
14
Distribution of Motorola manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Updating manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ordering manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Available formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
15
15
15
Overview of Motorola manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Manual types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
16
Summary of Motorola manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Service manuals - BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Service manuals - GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System information manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operating information manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Technical description manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation and configuration manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintenance information manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18
18
111
112
113
113
114
114
115
Other manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SPARC E3000/E3500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SPARCstation manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
INFORMIX manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printer manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
X.25 manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
116
116
116
116
116
116
116
Chapter 2
Introduction to Motorola GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to GSM system information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23
23

02 May 2003
68P02901W01-M
iii
GSR6 (Horizon II)
Overview of the Motorola GSM system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Motorola GSM system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network element overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Typical GSM system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unique features of Motorola GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to the unique features of Motorola GSM . . . . . . . . . . . . . . . . . . . . . . .
Systems advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Future system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Motorola network specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to Motorola network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OMC-R specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Functions of the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Optional processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OMC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Receiver specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transmitter specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Password levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Option level 3 control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Releated commands and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mobile station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to mobile stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mobile station components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Subscriber Interface Module (SIM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hand portable viability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment identity number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Subscriber identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GSM network specifications and recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GSM advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Digital networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Increase capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Frequency reuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Audio capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Link integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Subscriber services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Teleservices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GSM network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to GSM network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network managment centre functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
National management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Monitoring equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Monitoring routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Simulating the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv

68P02901W01-M
25
25
25
28
29
29
29
29
29
29
210
211
211
211
211
212
212
212
213
213
214
217
219
219
219
219
219
220
220
220
220
220
221
221
222
222
222
222
223
223
223
224
224
224
224
225
225
225
225
225
225
225
226
226
02 May 2003
GSR6 (Horizon II)
Operations and maintenance centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
227
227
Mobile services switching centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to the MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSC functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gateway MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSC flexible design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Location register interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message transfer link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Call control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Emergency calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Short message service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Local registration and call handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inter-MSC handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment identity register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Home location register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HLR master database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HLR data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Authentication centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Authentication key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Visitor location register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Controlling LAIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Controlling MSRNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Allocating handover numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Allocating TMSI numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Call handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MS to PSTN subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PSTN subscriber to MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MS to MS calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
228
228
228
229
229
229
229
230
230
230
230
231
231
231
232
233
233
234
234
234
234
235
235
235
235
236
237
237
238
239
Base station system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Motorola BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connection of MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Speech transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS application part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Physical channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logical channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logical channel types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Traffic channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
242
242
242
243
243
243
243
244
244
244
244
244
245
245
GSM subsystems (non-network elements) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to GSM non- network element subsystems . . . . . . . . . . . . . . . . . . . .
Interworking function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Echo canceller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Billing centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cell broadcast centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
246
246
246
246
246
246

02 May 2003
68P02901W01-M
GSR6 (Horizon II)
GSM system features and goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to GSM system features and goals . . . . . . . . . . . . . . . . . . . . . . . . . . .
Technological requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GSM goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
European standardization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Standardized electrical interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GSM interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ISDN compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signalling system 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hierarchical network architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Subscriber services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Link integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Increased capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Use of low bit rates for non-voice data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Lower cost infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Site size definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Timing adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Echo cancellers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Noise robustness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS Location Services support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LCS positioning mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Time of arrival positioning procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Timing Advance positioning (TA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E1/T1 links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Link types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E1 link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
T1 link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSC daisy chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Standardized interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interface types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GSM functional layering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSSAP messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ISDN messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSC to MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Location register interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OMC interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NMC interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interface summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signalling links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Abis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Air interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Lb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Protocol types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OSI/protocol relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ITU-TSS signalling system 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
X.25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAPDm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signalling link protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi

68P02901W01-M
247
247
247
247
247
248
248
248
248
248
249
249
249
249
250
250
250
250
250
250
251
251
251
251
252
252
252
252
253
253
253
253
253
254
254
255
256
256
256
256
256
256
257
257
258
258
259
260
262
262
262
264
265
265
265
02 May 2003
GSR6 (Horizon II)
GSM frequencies and channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to frequencies and channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GSM850 frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GSM850 channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Primary GSM900 frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Primary GSM900 channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EGSM frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EGSM channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
266
266
266
267
274
275
282
283
DCS1800 frequencies and channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DCS1800 frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DCS1800 channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
286
286
286
PCS1900 frequencies and channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCS1900 frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCS1900 channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2106
2106
2106
Chapter 3
BSS general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to BSS information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33
33
Base station system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS purpose and functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Typical BSS layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
34
34
34
35
BSC description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSC purpose and functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSC to MSC interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Digital switching matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terrestrial circuit device management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSC capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
36
36
36
36
36
37
BTS description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS purpose and functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Frequency reuse plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RF coverage areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Antenna systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38
38
38
38
38
Transcoder description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transcoder purpose and functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transcoding location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39
39
39
39
BSS site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to BSS site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Flexibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS maximum capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSSC cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS/MSC configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS with more than one BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Flexible neighbour cell processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
310
310
310
310
311
311
312
312
312
313
315

02 May 2003
68P02901W01-M
vii
GSR6 (Horizon II)
viii
Network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Basic configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Topology model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Star (spoke) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Open-ended daisy chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Daisy chain with fork and return loop to chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Daisy chain with fork and return loop to BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Drop and insert BTS site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
316
316
316
316
316
317
317
318
BSS standardized interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to BSS standardized interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Protocol layering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Abis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Air interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Lb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
319
319
319
319
319
320
320
Radio system and control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to radio system and control functions . . . . . . . . . . . . . . . . . . . . . . . . .
Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dynamic power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Discontinuous transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Discontinuous reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Timing adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Frequency synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
321
321
321
322
322
322
323
323
Cell system radio channel reuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to cell system radio channel reuse . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-site reuse pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-site 3-sector reuse pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-site reuse pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cell pattern reuse comparisons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
324
324
324
325
325
325
325
326
BSS redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to BSS redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Failed modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RF carrier redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interface redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSC redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RXCDR redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
327
327
327
327
327
327
328
328
328
General Packet Radio Service (GPRS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Packet control unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GSN complex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GSM/GPRS network architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
329
329
329
330
331
Packet control unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to the PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCU information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
332
332
332
PCU overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCU summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCU environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
333
333
333

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
PCU features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of PCU features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Point-to-point GPRS service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GPRS radio channel allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Medium access control mode dynamic allocation . . . . . . . . . . . . . . . . . . . . . . . .
Support of MS classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Coding schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dynamic adaptation of coding schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Two phase packet access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
One phase access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enhanced one phase access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Frequency hopping of PDCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power control uplink/downlink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCU load balancing and sharing (Gb and BTS) . . . . . . . . . . . . . . . . . . . . . . . . . . .
MS flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
334
334
335
336
336
337
338
338
339
339
339
340
340
340
341
341
PCU description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCU purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCU management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCU devices and equippage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
342
342
342
343
PCU architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to PCU architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bridge (PPB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E1 PMC module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fault tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
344
344
344
344
345
346
346
346
PCU interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to GPRS BSS interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCU interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
347
347
348
PCU system and control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System and control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCU processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
350
350
351
Chapter 4
OMC-R Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
Introducing the Motorola OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Definition of OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Naming conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communication with GSM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43
43
44
44
OMC-R network management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Event/alarm management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45
45
45
45
45
46
The OMC-R in GSM network management architecture . . . . . . . . . . . . . . . . . . . . . . . . . .

Network hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47
47
47

02 May 2003
68P02901W01-M
ix
GSR6 (Horizon II)
The OMC-R system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OMC-R content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The system processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GUI clients and servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Optional processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48
48
48
48
48
OMC-R configuration summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Scaleable configuration details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
410
410
The OMC-R user interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

User interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GUI interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OMC-R front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
411
411
411
411
412
The command line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UNIX-based utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
414
414
The OMC-R in a GSM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A typical GSM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OMC-R functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RXCDR functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
415
415
416
416
416
BSS and RXCDR configuration (SITES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RXCDR configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
417
417
417
NE device containment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Containment relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
418
418
418
Site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CELL resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS hardware relating to traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS software relating to traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
419
419
419
419
DRI/RTF groups - transceiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transceiving functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Types of RTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Redundancy (within a cell) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
420
420
420
420
CELL configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logical devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handover control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
421
421
421
422
Links in a GSM network: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Information on links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SITE link requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Link types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
423
423
423
423
Physical links - PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Physical link requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PATH devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
424
424
424
424
Logical links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Types of link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
425
425
425
426

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
OMC-R connection to the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transferring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
X.21 connection configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
427
427
427
Operations and maintenance of a BSS or RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Simplified network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
429
429
O&M information flow between OMC-R and NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Summary of information flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Information flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
430
430
430
OMC-R system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Motorola OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Typical hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
431
431
431
Communications handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communications software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
432
432
Packet switch/multiplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Packet switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
433
433
433
O&M network traffic capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Peak traffic capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
434
434
OMC-R system processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to the system processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
435
435
435
436
437
OMC-R GSM application software: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OMC-R processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System processor software elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
438
438
438
UNIX: Solaris 2.5.1 operating system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tools and applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
440
440
440
440
440
The OMC-R database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RDBMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database schema: defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Applications and utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
441
441
441
441
441
The SPARCstation configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Running the OMC-R GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The network file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAN configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
443
443
443
443
444
GUI processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Server client relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
445
445
The network status summary (NSS) feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
446
446
446
The CM MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description of the CM MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Populating the CM MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
447
447
447

02 May 2003
68P02901W01-M
xi
GSR6 (Horizon II)
xii
GUI Client - SPARCstation 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Software configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Night concentration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
448
448
448
449
How the network status summary feature works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Map process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The EM proxy process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
450
450
450
451
GUI clients and servers: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Client/server system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GUI servers and GUI clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
452
452
452
Network maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Different maps available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Map modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Consolidated alarm report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Map configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
453
453
454
454
454
454
The map display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Map backgrounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Map links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
State changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
455
455
455
455
455
455
How administrative and operational state changes work . . . . . . . . . . . . . . . . . . . . . . . . . .

State changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
457
457
How alarms work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alarm icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Colours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
458
458
459
How maps are configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to the CM MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Two object groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
460
460
460
Graphic objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Graphic objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MapNode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MapLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
461
461
461
461
461
Configuration objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logical links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ProxyCell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UserProfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automatically created network objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automatically created map display objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
462
462
464
465
465
466
467
467
467
468
Periodic Supervision of Accessibility (PSA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Definition of PSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PSA failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
469
469
469

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Disk usage exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System processor partition full . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
470
470
470
DataGen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to DataGen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DataGen configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Off-line MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
471
471
472
472
Chapter 5
BSS software release features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
Introduction to BSS software release features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
53
53
BSS software release 1.1.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Release 1.1.1.0 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54
54

56
56

57
57

58
58

59
59

510
510

512
512

513
513

514
514

Reason for this release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
515
515

Important information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
516
516
516
BSS software release 1.3.0.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Release 1.3.0.x features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
518
518

521
521

522
522

523
523

524
524

525
525

02 May 2003
68P02901W01-M
xiii
GSR6 (Horizon II)
xiv
BSS software release GSR2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR2 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
527
527

GSR3 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
529
529

GSR4 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
532
532
BSS software release GSR4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR4.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
534
534

GSR5 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS overload protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SMS CB upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Receive antenna VSWR and radio loopback test . . . . . . . . . . . . . . . . . . . . . . . . . .
Dynamic allocation of RXCDR-BSC circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enhanced XBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Horizonmicro2 / Horizoncompact2 generic BTS software . . . . . . . . . . . . . . . . . . .
Code corruption immune design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Propagate TSC changes to all timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single BCCH for dual band cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Support for E1/T1 conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enhanced power outage recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Improved MTL load balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS concentration resource optimization for handovers . . . . . . . . . . . . . . . . . . . .
Handover parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Per neighbour area for adaptive handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Optimized power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Support for the MTL stat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Support for frame erasure rate statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS concentration call priority handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GPROC function pre-emption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parallel cage enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enhanced MMI link device warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
536
536
536
537
537
538
538
539
539
539
539
539
540
540
540
540
541
541
541
541
541
542
542
542
BSS software release GSR5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR5.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSS processing of suspend message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CS3, CS4 and 32 kbits/s TRAU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GPROC fast reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unequip of TCU/CTU cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
850 MHz frequency range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1900 MHz Horizonmacro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single BCCH for dual band cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
543
543
543
544
545
545
545
545
546

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

GSR6 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enhanced Circuit Error Rate Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple GPRS carriers per Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enhanced GDP provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Call downgrade on CIC capability mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GPRS PCU recovery on last GSL failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Controlled (NC1 and NC2) cell reselection . . . . . . . . . . . . . . . . . . . . . . . .
Location services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Basic MPROC redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enhanced BSC capacity phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Improved MPROC software failures detection and recovery . . . . . . . . . . . . . . . . .
Inter Radio Access Technology (RAT) 2-G to 3-G handover . . . . . . . . . . . . . . . . .
Clean install (E3x00) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GPRS interleaving TBFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Link utilization improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Advanced load management for EGSM carriers . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enhanced GPRS One Phase Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remove support for collocated BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compress all BTS objects at the BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
547
547
548
549
550
552
553
554
556
557
558
558
559
560
561
563
564
564
565
565
BSS software release GSR6 (Horizon II) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II) features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Horizon II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enhanced two uplink timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removal of support for Horizonoffice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
566
566
566
568
570
Chapter 6
OMC-R software release features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
Introduction to OMC-R software release features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
63
63
OMC-R software release 1.1.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
64
64

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
65
65
65

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
66
66
66

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
68
68
68
69

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
610
610
610

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
611
611
611

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
614
614
614

02 May 2003
68P02901W01-M
xv
GSR6 (Horizon II)
xvi

617
617

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
618
618
618

619
619

620
620

Further features of OMC-R software release 1.4.0.1 . . . . . . . . . . . . . . . . . . . . . . .
622
622
623

Release 1.4.0.6 feature support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
624
624

Release 1.4.0.7 feature support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
625
625

626
626
OMC-R software release GSR2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR2 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
628
628

GSR3 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
631
631

GSR4 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
632
632
OMC-R software release GSR4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR4.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
633
633

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

GSR5 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS concentration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Optimized power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Propagation after audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EAS relay MMI control for InCell, M-Cell and Horizon . . . . . . . . . . . . . . . . . . . . . .
Intelligent congestion relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adaptive handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Support of BCCH and SDCCH for EGSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Coincident multiband boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reporting the results of alarms recovery action . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Flexible neighbour cell processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dynamic trace call flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Proxy cell autocreation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Proxy cell import/export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Completion of OMCRsupport for Horizonmacro . . . . . . . . . . . . . . . . . . . . . . . . . .
Q3 support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DRI and combiner operability improvement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NHA support maximum size GSM OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Integration of NHA with OMC-R EM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bay level cal default data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cell parameter import/export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Applix 4.41 upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enhanced SDCCH to TCH assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing NE ID of Assoc_BSSs or Assoc_RXCDRs . . . . . . . . . . . . . . . . . . . . . . .
OMC-R GUI usability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Datagen support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Increased OMC-R neighbour stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OMC-R GUI support for PCU device object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network expansion batch capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Increased capacity OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Increasing maximum number of trunks per BSC . . . . . . . . . . . . . . . . . . . . . . . . . . .
Expansion/de-expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Vanguard software upgrade support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Support for Vanguard 6455 router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removal of the clear stats command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCU alarms detected by HSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
634
634
635
635
635
635
635
636
636
636
636
637
637
637
638
638
638
638
639
639
639
639
639
640
640
640
641
641
641
641
641
642
642
643
643
643
643
643
OMC-R software release GSR5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR5.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
WebMMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CS3, CS4 and 32 kbits/s TRAU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GPROC fast reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unequip of TCU/CTU cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
644
644
644
644
644
645

GSR6 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Geographic command partitioning and region support . . . . . . . . . . . . . . . . . . . . . .
Enhanced circuit error rate monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OMC-R GUI usability for large network support . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enable cyclic neighbour statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Online network expansion - phase 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cell Xchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
646
646
647
648
649
650
650
651

02 May 2003
68P02901W01-M
xvii
GSR6 (Horizon II)
xviii
OMC-R software release GSR6 (Horizon II) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSR6 (Horizon II) features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Support for new UNIX server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
652
652
653
Chapter 7
Glossary of technical terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
71
Glossary of technical terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A Interface - AUTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B Interface - Byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C - CW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D Interface - DYNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E - EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F Interface - Full Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
G Interface - GWY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H Interface - Hyperframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I - IWU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
k - KW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
L1 - LV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
M - MUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NACK - nW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
O - Overlap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PA - PXPDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QA- Quiesent mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
R - RXU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
S7- SYSGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
T -TxBPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
U - UUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
V - VTX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
W - WWW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
X - X Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ZC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
73
73
77
710
718
722
725
728
730
731
735
735
738
743
745
747
753
753
758
765
770
771
773
774
774
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I1

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
List of Figures
Figure 2-1 GSM and GPRS Architecuture (GSN Complex) . . . . . . . . . . . . . . . . . . . . . . .
27
Figure 2-2 Typical GSM system layout Dual BSS system . . . . . . . . . . . . . . . . . . . . . .
28
Figure 2-3 Four cell frequency reuse pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
223
Figure 2-4 A interface protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
230
Figure 2-5 Handover control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
232
Figure 2-6 Database list summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
233
Figure 2-7 HLR configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
233
Figure 2-8 Authentification centre configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
234
Figure 2-9 Visitor location register configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
235
Figure 2-10 MS to PSTN subscriber call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
237
Figure 2-11 PSTN subscriber to MS call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
238
Figure 2-12 MS to MS call (same PLMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
239
Figure 2-13 MS to MS call (different PLMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
240
Figure 2-14 MS to MS call (different PLMN/different country) . . . . . . . . . . . . . . . . . . . . .
241
Figure 2-15 BSS configuration examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
242
Figure 2-16 GSM functional layering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
255
Figure 2-17 GSM interface summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
257
Figure 2-18 OSI layers main protocol relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . .
262
Figure 2-19 Network protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
263
Figure 2-20 GSM850 frequency range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
266
Figure 2-21 GSM900 frequency range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
274
Figure 2-22 EGSM frequency range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
282
Figure 2-23 DCS1800 frequency range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
286
Figure 2-24 PCS1900 frequency range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2106
Figure 3-1 Dual BSS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35
Figure 3-2 Multiple BTS sites per BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
313
Figure 3-3 Topology model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
316
Figure 3-4 Handover measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
322
Figure 3-5 9-site reuse pattern cellular system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
324
Figure 3-6 3-site (sectored) cellular system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
325
Figure 3-7 The GPRS network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
329
Figure 3-8 GPRS network architecture showing the PCU and GSN complex . . . . . . .
331
Figure 3-9 PCU within the GSM/GPRS network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
333
Figure 3-10 PCU managed from the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
342
Figure 3-11 Device and equipment hierarchy for the PCU device . . . . . . . . . . . . . . . . . .
343
Figure 3-12 BSS functional blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
347
Figure 3-13 Data and signalling paths between the PCU and MS . . . . . . . . . . . . . . . . .
348
Figure 3-14 PCU to BSC connection utilizing E1 links (four shown) . . . . . . . . . . . . . . . .
349

02 May 2003
68P02901W01-M
xix
GSR6 (Horizon II)
xx
Figure 3-15 Data and signalling paths between the PCU and SGSN . . . . . . . . . . . . . . .
349
Figure 4-1 The OMC-R in a GSM system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43
Figure 4-2 GSM network management architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47
Figure 4-3 Typical scaleable OMC-R system configuration . . . . . . . . . . . . . . . . . . . . . . .
49
Figure 4-4 The OMC-R GUI front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
412
Figure 4-5 The Expert OMC-R GUI Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
412
Figure 4-6 The OMC-R in a GSM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
415
Figure 4-7 The naming convention and physical links of BSS . . . . . . . . . . . . . . . . . . . . .
417
Figure 4-8 Site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
419
Figure 4-9 Example of path settings within a BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
424
Figure 4-10 The different logical links in a GSM network . . . . . . . . . . . . . . . . . . . . . . . . .
426
Figure 4-11 Communication between the OMC-R and other network elements . . . . . .
428
Figure 4-12 Simplified GSM network showing devices and links at BSSs . . . . . . . . . . .
429
Figure 4-13 Information flow between the OMC-R and BSSs . . . . . . . . . . . . . . . . . . . . .
430
Figure 4-14 An example Motorola OMC-R system configuration . . . . . . . . . . . . . . . . . .
431
Figure 4-15 Example Packet switch / multiplexer connections . . . . . . . . . . . . . . . . . . . .
433
Figure 4-16 Scaleable OMC-R - high-end system processor . . . . . . . . . . . . . . . . . . . . .
435
Figure 4-17 System processor software configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .
437
Figure 4-18 OMC-R GSM (System processor) software components . . . . . . . . . . . . . .
438
Figure 4-19 OMC-R database - database schema breakdown . . . . . . . . . . . . . . . . . . . .
441
Figure 4-20 OMC-R SPARCstation configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
443
Figure 4-21 Maps icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
446
Figure 4-22 The network status summary options on the GUI front panel . . . . . . . . . .
446
Figure 4-23 SPARCstation 5/IPX hardware and software configuration . . . . . . . . . . . .
448
Figure 4-24 Night concentration configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
449
Figure 4-25 Map processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
450
Figure 4-26 Map icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
456
Figure 4-27 State changes on the map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
457
Figure 4-28 Alarms and how they change on the map . . . . . . . . . . . . . . . . . . . . . . . . . . .
458
Figure 4-29 The CM MIB showing the different groups of managed objects . . . . . . . .
460
Figure 4-30 The containment relationship for the graphic objects . . . . . . . . . . . . . . . . .
461
Figure 4-31 The containment relationship for the configuration objects . . . . . . . . . . . . .
462
Figure 4-32 DataGen in a GSM environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
471
Figure 4-33 DataGen main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
472
Figure 4-34 Off-line MIB front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
472
Figure 5-1 Example of Interleaving DL TBFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
561
Figure 5-2 Multi-slot class 6 uplink/downlink bias timeslot allocation . . . . . . . . . . . . . . .
569
Figure 5-3 Multi-slot class 10 uplink/downlink bias timeslot allocation . . . . . . . . . . . . . .
569
Figure 6-1 GSM OMC-R hardware configuration for up to 45k TCH . . . . . . . . . . . . . . .
653

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Figure 6-2 GSM OMC-R hardware configuration for up to 60k TCH . . . . . . . . . . . . . . .
654

02 May 2003
68P02901W01-M
xxi
GSR6 (Horizon II)
List of Tables
xxii
Table 1-1 Typical manual history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
Table 1-2 Types of Motorola manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
Table 2-1 OMC-R functions and GSM & ITU-TSS references . . . . . . . . . . . . . . . . . . . . .
211
Table 2-2 OMC configurations (maximum values) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
212
Table 2-3 OMC-R/X.25 capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
213
Table 2-4 Receiver specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
214
Table 2-5 Transmitter specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
217
Table 2-6 BSS software function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
243
Table 2-7 Network element signalling links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
257
Table 2-8 GSM Frequency types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
266
Table 2-9 GSM850 channels 128 to 130 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
267
Table 2-10 GSM850 channels 131 to 140 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
267
268
268
269
269
270
270
271
271
272
272
273
Table 2-22 PGSM channels 1 to 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
275
Table 2-23 PGSM channels 11 to 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
275
276
276
277
277
278
278
279
Table 2-31 PGSM channels 91 to 100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
279
Table 2-32 PGSM channels 101 to 110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
280
280
281
Table 2-35 EGSM channels 975 to 984 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
283
Table 2-36 EGSM channels 985 to 994 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
283

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Table 2-37 EGSM channels 995 to 1004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
284
Table 2-38 EGSM channels 1005 to 1014 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
284
Table 2-39 EGSM channels 1015 to 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
285
Table 2-40 DCS 1800 channels 512 to 520 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
286
287
287
288
288
289
289
290
290
291
Table 2-50 DCS 1800 channels 611 to 620 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
291
292
292
293
293
294
294
295
295
296
296
297
297
298
298
299
299
2100
2100
2101
2101
2102
2102
2103
2103
2104

02 May 2003
68P02901W01-M
xxiii
GSR6 (Horizon II)
xxiv
2104
2105
Table 2-78 PCS 1900 channels 512 to 520 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2106
2107
2107
2108
2108
2109
2109
2110
2110
2111
2111
2112
2112
2113
2113
2114
2114
2115
2115
2116
2116
2117
Table 2-100 PCS 1900 channels 731 to 740 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2117
2118
2118
2119
2119
2120
2120
2121
Table 3-1 BSC maximum capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
37
Table 3-2 BTS - BSC main and alternate paths (fork with return loop) . . . . . . . . . . . . .
317
Table 3-3 BTS - BSC main and alternate paths (chain with return loop) . . . . . . . . . . . .
317
Table 3-4 Sector re-use pattern features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
326
Table 3-5 Failed module situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
327
Table 3-6 Cell reselection modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
335
Table 3-7 MS multi-slot class mapping for all GPRS multi-slot classes . . . . . . . . . . . . .
337

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Table 3-8 GPRS coding scheme characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
338
Table 4-1 Front panel icon description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
413
Table 4-2 Scaleable OMC-R configurations (maximum values) . . . . . . . . . . . . . . . . . . .
436
Table 4-3 GUI processor hardware specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
445
Table 4-4 GUI processor software specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
445
Table 4-5 Alarm icon colours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
459
Table 5-1 Release 1.1.1.0 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54
Table 5-2 Software release 1.1.2.0 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
56
57
58
59
510
512
513
514
Table 5-10 Release 1.2.3.0 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
516
Table 5-11 Release 1.3.0.x features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
518
521
Table 5-13 Release1.4.0.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
522
523
524
525
Table 5-17 Release GSR2 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
527
529
532
Table 5-20 Release GSR4.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
534
536
543
547
Table 5-24 Multiple GPRS carriers configured for performance (Default) . . . . . . . . . . .
549
Table 5-25 Operator specified options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
550
Table 5-26 Cell reselection modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
554
Table 5-27 Release GSR6 (Horizon II) features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
566
Table 5-28 CTU and CTU2 output power capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . .
567
Table 5-29 MS multi-slot class mapping for all GPRS multi-slot classes . . . . . . . . . . . .
568
68
610
611
614

02 May 2003
68P02901W01-M
xxv
GSR6 (Horizon II)
xxvi
Table 6-5 Release1.2.2.2 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
617
618
619
620
623
626
628
631
632
633
634
644
646
Table 6-18 Release GSR6 (Horizon II) features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
652

68P02901W01-M
02 May 2003
Issue status of this manual
GSR6 (Horizon II)
Issue status of this manual

Introduction
The following shows the issue status of this manual since it was first released.
Version information
The following table lists the versions of this manual in order of manual issue:
Manual
issue
Date of
issue
Remarks
03 Oct 1994
Issue O Original issue - Software release 1.2.2.x
30 Dec 1994
Issue A Software release 1.2.3.x
10 Sep 1995
Issue B Software release 1.3.0.x
31 May 1996
Issue C Software release 1.4.0.x
28 Mar 1997
Issue D Software release 1.4.1.x
29 Aug 1997
Issue E GSM Software Release 2
27 Apr 1998
Issue F GSM Software Release 3
12 Mar 1999
Issue G GSM Software Release 4
14 Jul 2000
Issue H GSM Software Release 4.1
31 Jul 2001
Issue J GSM Software Release 5
31 May 2002
Issue K GSM Software Release 5.1
30 Nov 2002
Issue L GSM Software Release 6
02 May 2003
Issue M GSM Software Release 6 (Horizon II)
Resolution of Service Requests

The following Service Requests are now resolved in this manual:
Service
Request
GMR
Number
N/A
N/A
Remarks

02 May 2003
68P02901W01-M
General information
GSR6 (Horizon II)
General information
Important notice
If this manual was obtained when attending a Motorola training course, it will not be
updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it
was supplied under normal operational circumstances, to support a major software
release, then corrections will be supplied automatically by Motorola in the form of
General Manual Revisions (GMRs).
Purpose
Motorola cellular communications manuals are intended to instruct and assist personnel
in the operation, installation and maintenance of the Motorola cellular infrastructure
equipment and ancillary devices. It is recommended that all personnel engaged in such
activities be properly trained by Motorola.
WARNING
Failure to comply with Motorolas operation, installation and

maintenance instructions may, in exceptional circumstances,
lead to serious injury or death.
These manuals are not intended to replace the system and equipment training offered by
Motorola, although they can be used to supplement and enhance the knowledge gained
through such training.
About this manual

This manual supports the following Motorola BSS equipment:
BTS4, BTS5, BTS6, BSSC, BSSC2, ExCell4, ExCell6, TopCell, M-Cell2, M-Cell6,
M-Cellmicro, M-Cellcity, M-Cellcity+, Horizonmicro2, Horizoncompact2, M-Cellaccess,
Horizoncompact, Horizonmicro, Horizonmacro and Horizon II.
The manual is an overview of the Global System for Mobile Communications (GSM) as
implemented by Motorola, and includes:
S
Chapter 1, Introduction to GSM system information.
Chapter 2, Introduction to Motorola GSM.
Chapter 3, BSS general information.
Chapter 4, OMC-R overview.
Chapter 5, BSS software release features.
Chapter 6, OMC-R software release features.
Chapter 7, Glossary of terms, acronyms and abbreviations.
Index
The information is intended for use by GSM operations and maintenance staff.

68P02901W01-M
02 May 2003
General information
GSR6 (Horizon II)
Cross references
Throughout this manual, cross references are made to the chapter numbers and section
names. The section name cross references are printed bold in text.
This manual is divided into uniquely identified and numbered chapters that, in turn, are
divided into sections. Sections are not numbered, but are individually named at the top of
each page, and are listed in the table of contents.
Text conventions
The following conventions are used in the Motorola cellular infrastructure manuals to
represent keyboard input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and
environmental variables that appear on the screen are shown like
this.
Special key sequences

Special key sequences are represented as follows:
CTRLc
Press the Control and c keys at the same time.
ALTf
Press the Alt and f keys at the same time.
Press the pipe symbol key.
CR or RETURN
Press the Return (Carriage Return) key. The Return key is

identified by the symbol on both the PC and the Sun
keyboards. The keyboard Return key may also be identified
by the word Return.

02 May 2003
68P02901W01-M
General information
GSR6 (Horizon II)
Feature references
Throughout this manual new and amended features are tagged to help users to assess
the impact on installed networks. The tags are the appropriate Motorola Roadmap
DataBase (RDB) numbers. The tags include index references which are listed in the
manual Index. The Index includes the entry feature which is followed by a list of the RDB
numbers for the released features, with page references and hot links in electronic copy.
The tags have the format:
Where:
is:
{nnnn}
the RDB database number
The tags are positioned in text as follows:

Tag position in text
New and amended feature information

New sentence/s or new or amended text.
Immediately before the affected text.
Complete new blocks of text as follows:

S
Full sections under a main heading
Immediately after the headings as follows:

S
Main heading
Full paragraphs under subheadings
Subheading
New or amended complete Figures and

Tables
After the Figure or Table number and

before the title text.
Warning, Caution and Note boxes.
Immediately before the affected text in the

box.
General command syntax, operator input

or displays (in special fonts).
On a separate line immediately above the

affected item.
For a list of Roadmap numbers and Roadmap DataBase (RDB) numbers of the features
included in this software release, refer to the manual System Information: Overview
(68P02901W01), or to the manual System Information: GPRS Overview
(68P02903W01).

68P02901W01-M
02 May 2003
Reporting safety issues
GSR6 (Horizon II)
Reporting safety issues

Introduction
Whenever a safety issue arises, carry out the following procedure in all instances.
Ensure that all site personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises:
1.
Make the equipment concerned safe, for example by removing power.
2.
Make no further attempt to adjust or rectify the equipment.
3.
Report the problem directly to the Customer Network Resolution Centre, Swindon
+44 (0)1793 565444 or China +86 10 68437733 (telephone) and follow up with a
written report by fax, Swindon +44 (0)1793 430987 or China +86 10
68423633 (fax).
4.
Collect evidence from the equipment under the guidance of the Customer Network
Resolution Centre.

02 May 2003
68P02901W01-M
Warnings and cautions
GSR6 (Horizon II)
Warnings and cautions

Introduction
The following describes how warnings and cautions are used in this manual and in all
manuals of this Motorola manual set.
Warnings
Definition of Warning
A warning is used to alert the reader to possible hazards that could cause loss of life,
physical injury, or ill health. This includes hazards introduced during maintenance, for
example, the use of adhesives and solvents, as well as those inherent in the equipment.
Example and format

WARNING
Do not look directly into fibre optic cables or data in/out

connectors. Laser radiation can come from either the data in/out
connectors or unterminated fibre optic cables connected to data
in/out connectors.
Failure to comply with warnings

Observe all warnings during all phases of operation, installation and maintenance of the
equipment described in the Motorola manuals. Failure to comply with these warnings,
or with specific warnings elsewhere in the Motorola manuals, or on the equipment
itself, violates safety standards of design, manufacture and intended use of the
equipment. Motorola assumes no liability for the customers failure to comply
with these requirements.
Cautions
Definition of Caution
A caution means that there is a possibility of damage to systems, software or individual
items of equipment within a system. However, this presents no danger to personnel.
Example and format

CAUTION
Do not use test equipment that is beyond its due calibration date;
arrange for calibration to be carried out.

68P02901W01-M
02 May 2003
General warnings
GSR6 (Horizon II)
General warnings
Introduction
Observe the following specific warnings during all phases of operation, installation and
maintenance of the equipment described in the Motorola manuals:
S
Potentially hazardous voltage
Electric shock
RF radiation
Laser radiation
Heavy equipment
Parts substitution
Battery supplies
Lithium batteries
Failure to comply with these warnings, or with specific warnings elsewhere in the
Motorola manuals, violates safety standards of design, manufacture and intended use of
the equipment. Motorola assumes no liability for the customers failure to comply with
these requirements.
Warning labels
Warnings particularly applicable to the equipment are positioned on the equipment.
Personnel working with or operating Motorola equipment must comply with any warning
labels fitted to the equipment. Warning labels must not be removed, painted over or
obscured in any way.

02 May 2003
68P02901W01-M
General warnings
GSR6 (Horizon II)
Specific warnings
Specific warnings used throughout the GSM manual set are shown below, and will be
incorporated into procedures as applicable.
These must be observed by all personnel at all times when working with the equipment,
as must any other warnings given in text, in the illustrations and on the equipment.
Potentially hazardous voltage

WARNING
This equipment operates from a hazardous voltage of 230 V

ac single phase or 415 V ac three phase supply. To achieve
isolation of the equipment from the ac supply, the ac input
isolator must be set to off and locked.
When working with electrical equipment, reference must be made to the Electricity at
Work Regulations 1989 (UK), or to the relevant electricity at work legislation for the
country in which the equipment is used.
Motorola GSM equipment does not utilise high voltages.
NOTE
Electric shock
WARNING
Do not touch the victim with your bare hands until the
electric circuit is broken.
Switch off. If this is not possible, protect yourself with dry
insulating material and pull or push the victim clear of the
conductor.
ALWAYS send for trained first aid or medical assistance
IMMEDIATELY.
In cases of low voltage electric shock (including public supply voltages), serious injuries
and even death, may result. Direct electrical contact can stun a casualty causing
breathing, and even the heart, to stop. It can also cause skin burns at the points of entry
and exit of the current.
In the event of an electric shock it may be necessary to carry out artificial respiration.
ALWAYS send for trained first aid or medical assistance IMMEDIATELY.
If the casualty is also suffering from burns, flood the affected area with cold water to cool,
until trained first aid or medical assistance arrives.
RF radiation
WARNING
High RF potentials and electromagnetic fields are present in

this equipment when in operation. Ensure that all
transmitters are switched off when any antenna connections
have to be changed. Do not key transmitters connected to
unterminated cavities or feeders.
Relevant standards (USA and EC), to which regard should be paid when working with RF
equipment are:
ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human
Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.
CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High

Frequency (10 kHz to 300 GHz).
68P02901W01-M
02 May 2003
General warnings
GSR6 (Horizon II)
Laser radiation
WARNING
Do not look directly into fibre optic cables or optical data

in/out connectors. Laser radiation can come from either the
data in/out connectors or unterminated fibre optic cables
connected to data in/out connectors.
Lifting equipment
WARNING
When dismantling heavy assemblies, or removing or

replacing equipment, a competent responsible person must
ensure that adequate lifting facilities are available. Where
provided, lifting frames must be used for these operations.
When dismantling heavy assemblies, or removing or replacing equipment, the competent

responsible person must ensure that adequate lifting facilities are available. Where
provided, lifting frames must be used for these operations. When equipments have to be
manhandled, reference must be made to the Manual Handling of Loads Regulations
1992 (UK) or to the relevant manual handling of loads legislation for the country in which
the equipment is used.
Parts substitution
WARNING
Do not install substitute parts or perform any unauthorized

modification of equipment, because of the danger of
introducing additional hazards. Contact Motorola if in doubt
to ensure that safety features are maintained.
Battery supplies
WARNING
Do not wear earth straps when working with standby battery

supplies.
Lithium batteries
WARNING
Lithium batteries, if subjected to mistreatment, may burst

and ignite. Defective lithium batteries must not be removed
or replaced. Any boards containing defective lithium
batteries must be returned to Motorola for repair.
Contact your local Motorola office for how to return defective lithium batteries.

02 May 2003
68P02901W01-M
General cautions
GSR6 (Horizon II)
General cautions
Introduction
Observe the following cautions during operation, installation and maintenance of the
equipment described in the Motorola manuals. Failure to comply with these cautions or
with specific cautions elsewhere in the Motorola manuals may result in damage to the
equipment. Motorola assumes no liability for the customers failure to comply with these
requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution
labels fitted to the equipment. Caution labels must not be removed, painted over or
obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this
manual. These must be observed by all personnel at all times when working with the
equipment, as must any other cautions given in text, on the illustrations and on the
equipment.
Fibre optics
CAUTION
Fibre optic cables must not be bent in a radius of less than

30 mm.
Static discharge
CAUTION
10
Motorola equipment contains CMOS devices. These metal

oxide semiconductor (MOS) devices are susceptible to
damage from electrostatic charge. See the section Devices
sensitive to static in the preface of this manual for further
information.

68P02901W01-M
02 May 2003
Devices sensitive to static
GSR6 (Horizon II)
Devices sensitive to static

Introduction
Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of
insulation that is susceptible to damage from electrostatic charge. Such a charge applied
to the leads of the device could cause irreparable damage.
These charges can be built up on nylon overalls, by friction, by pushing the hands into
high insulation packing material or by use of unearthed soldering irons.
MOS devices are normally despatched from the manufacturers with the leads shorted
together, for example, by metal foil eyelets, wire strapping, or by inserting the leads into
conductive plastic foam. Provided the leads are shorted it is safe to handle the device.
Special handling techniques

In the event of one of these devices having to be replaced, observe the following
precautions when handling the replacement:
S
Always wear an earth strap which must be connected to the electrostatic point
(ESP) on the equipment.
Leave the short circuit on the leads until the last moment. It may be necessary to
replace the conductive foam by a piece of wire to enable the device to be fitted.
Do not wear outer clothing made of nylon or similar man made material. A cotton
overall is preferable.
If possible work on an earthed metal surface or anti-static mat. Wipe insulated

plastic work surfaces with an anti-static cloth before starting the operation.
All metal tools should be used and when not in use they should be placed on an
earthed surface.
Take care when removing components connected to electrostatic sensitive

devices. These components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less
susceptible to electrostatic damage. However PCBs should be handled with care,
preferably by their edges and not by their tracks and pins, they should be transferred
directly from their packing to the equipment (or the other way around) and never left
exposed on the workbench.

02 May 2003
68P02901W01-M
11
Motorola manual set
GSR6 (Horizon II)
Motorola manual set

Introduction
The following manuals provide the information needed to operate, install and maintain the
Motorola equipment. CD-ROMs are available, with full navigation, for GSM, and GPRS
manual sets.
Each CD-ROM includes all manuals related to a specified main GSM or GPRS software
release, together with current versions of appropriate hardware manuals. A snapshot
copy of online documentation is also included, though it will not be updated in line with
subsequent point releases.
The CD-ROM does not include Release Notes or documentation supporting specialist
products such as MARS or COP.
Generic GSM manuals

The following are the generic manuals in the GSM manual set, these manuals are
release dependent:
Identification/Order
number
68P02901W01
68P02901W14 *
68P02901W19
68P02901W34**
68P02901W36
68P02901W23
68P02901W17
68P02901W43
68P02901W47
68P02901W26
68P02901W58
68P02901W57
68P02901W51
68P02901W56
68P02901W72
68P02901W74

Operating Information: GSM System Operation
Operating Information: OMC-R System Administration
Technical Description: OMC-R Database Schema
Technical Description: BSS Implementation
Technical Description: BSS Command Reference
Installation & Configuration: GSM System Configuration
Installation & Configuration: BSS Optimization
Installation & Configuration: OMC-R Clean Install
Maintenance Information: Alarm Handling at the OMC-R
Maintenance Information: BSS Timers
Maintenance Information: Device State Transitions
Maintenance Information: BSS Field Troubleshooting
Maintenance Information: GSM Statistics Application
Software Release Notes: BSS/RXCDR
Software Release Notes: OMC-R System
Not on paper - In the OMC-R Online Help as Network Operations.

A snapshot of online help is available on CD-ROM.
Not on paper - On CD-ROM only.
**
12
Name

68P02901W01-M
02 May 2003
Motorola manual set
GSR6 (Horizon II)
Related GSM manuals

The following are related Motorola GSM manuals:
number
68P02900W21
68P02900W22
68P02900W76
68P02900W25
68P02900W36
68P02900W77
68P02900W90
68P02900W94
Name
System Information: BSS Equipment Planning

System Information: DataGen
Software Release Notes: DataGen
System Information: GSM Advance Operational Impact
System Information: Network Health Analyst
Software Release Notes: Network Health Analyst
System Information: Cell Optimization (COP)
System Information: Motorola Analysis and Reporting System
(MARS)
Software Release Notes: Cell Optimization (COP)
Software Release Notes: Motorola Analysis and Reporting System
(MARS)
Operating Information: OMC-R System Administration (OSI)
Installation & Configuration: OSI Clean Install
Software Release Notes: OMC-R OSI System
68P02900W69
68P02900W68
68P02901W10
68P02901W39
68P02901W70
Generic GPRS manuals

The following are the generic manuals in the GPRS manual set, these manuals are
release dependent:
number
Name
68P02903W01
68P02903W03
68P02903W37
68P02903W46
68P02903W18 *
68P02903W47
68P02903W04
68P02903W19 *
68P02903W20
68P02903W76
68P02903W70
System Information: GPRS Overview

Operating Information: OMC-G System Administration
Operating Information: GSN System Administration
Technical Description: OMC-G Database Schema
Technical Description: GSN Command Reference
Installation & Configuration: GSN Clean Install
Installation & Configuration: OMC-G Clean Install
Maintenance Information: Alarm Handling at the OMC-G
Maintenance Information: GSN Statistics Application
Software Release Notes: GSN System
Software Release Notes: OMC-G System
Not on paper - In the OMC-G Online Help as Alarm Handling and

GSN Commands/Parameters. A snapshot of online help is
available on CD-ROM.
Related GPRS manuals

The following are related Motorola GPRS manuals:
number
68P02903W02
68P02903W38
Name
System Information: GPRS Equipment Planning

System Information: GSN Advance Operational Impact
02 May 2003
68P02901W01-M
13
Motorola manual set
GSR6 (Horizon II)
BSS service manuals

The following are the Motorola Base Station Subsystem service manuals, these manuals
are not release dependent. The internal organization and makeup of service manual sets
may vary, they may consist of from one to four separate manuals, but they can all be
ordered using the overall catalogue number shown below:
number
68P02901W37
68P02901W38
68P02901W75
68P02901W85
68P02901W95
68P02901W65
68P02901W90
68P02902W36
68P02902W15
68P02902W06
68P02902W12
68P02902W61
68P02902W66
68P02902W96
68P02902W97
Name
Service Manual: BTS

Service Manual: BSC/RXCDR
Service Manual: M-Cell2
Service Manual: M-Cell6
Service Manual: M-Cellcity and M-Cellcity+
Service Manual: M-Cellaccess
Service Manual: M-Cellmicro
Service Manual: Horizonmicro
Service Manual: Horizoncompact
Service Manual: Horizonmacro Indoor
Service Manual: Horizonmacro Outdoor
Service Manual: Horizonmicro2 Horizoncompact2
Service Manual: Horizonmacro 12 Carrier Outdoor
Service Manual:Horizon II macro
Installation & Configuration: Horizon II macro
GPRS service manuals

The following are the Motorola GPRS service manuals, these manuals include the
Packet Control Unit (PCU) service manual which becomes part of the BSS for GPRS:
number
68P02903W05
68P02903W07
68P02903W23
68P02903W10
68P02903W12
68P02903W24
Name
Service Manual: GPRS Support Node (GSN)

Installation & Configuration: GSN (legacy cabinets)
Installation & Configuration: GSN (common data cabinets)
Service Manual: Packet Control Unit (PCU)
Installation & Configuration: PCU (legacy cabinets)
Installation & Configuration: PCU (common data cabinets)
Order number
The Motorola 68P order (catalogue) number is used to order manuals.
Ordering manuals
All orders for Motorola manuals must be placed with your Motorola Local Office or
Representative. Manuals are ordered using the order (catalogue) number.
Manuals are available on the following media:
Printed hard copy
Electronic:
14
On the Motorola service web.
CD-ROM library produced in support of a major system software release.

68P02901W01-M
02 May 2003
GMR amendment
GSR6 (Horizon II)
GMR amendment
Introduction to GMRs
Changes to a manual that occur after the printing date are incorporated into the manual
using General Manual Revisions (GMRs). GMRs are issued to correct Motorola manuals
as and when required. A GMR has the same identity as the target manual. Each GMR is
identified by a number in a sequence that starts at 01 for each manual at each issue.
GMR availability
GMRs are published as follows:
S
Printed hard copy - Complete replacement content or loose leaf pages with
amendment list.
Remove and replace pages in this manual, as detailed on the GMR

instruction sheet.
Motorola service web - Updated at the same time as hard copies.
CD-ROM - Updated periodically as required.

02 May 2003
68P02901W01-M
15
GMR amendment record
GSR6 (Horizon II)
GMR amendment record

GMR instructions
When a GMR is inserted in this manual, the amendment record below is completed to
record the GMR. Retain the instruction sheet that accompanies each GMR and insert it
in a suitable place in this manual for future reference.
Amendment record
Record the insertion of GMRs in this manual in the following table:
GMR number
16
Incorporated by (signature)
Date
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

68P02901W01-M
02 May 2003
Chapter 1
GSM system manual introduction

02 May 2003
68P02901W01-M
11
GSR6 (Horizon II)
12

68P02901W01-M
02 May 2003
Introduction to Motorola GSM documentation
GSR6 (Horizon II)
Introduction to Motorola GSM documentation

About this chapter
This chapter contains listings of Motorola GSM manuals supplied to customers. The
chapter also includes a description of the Motorola documentation system and includes a
brief summary of the contents of each manual. Other documents available to Motorola
customers are also listed.
Overview of GSM customer support manuals

This manual is a guide to the Motorola GSM manuals customer support manuals, it
describes how the manuals are referenced, what manuals are available and how to
obtain them.
The Motorola system and hardware product manuals provide the required information for
a customer to manage, operate and maintain the GSM system, as implemented by
Motorola.
Further details of the Motorola GSM customer support manuals are provided in the
following sections:
S
Documentation coding.
Distribution of Motorola manuals.
Overview of Motorola manuals.
Summary of Motorola manuals.
Other manuals.

02 May 2003
68P02901W01-M
13
Documentation coding
GSR6 (Horizon II)
Documentation coding
Manual coding system
All manuals have a 68P... catalogue number which is a unique identifier, used for
ordering purposes.
Order number
The order number is an eleven character Motorola code, that starts with 68P... for
technical manuals. It is the part number used when ordering Motorola hardcopy
manuals. An additional suffix letter indicates the issue status of the manual. Note that
this starts at O for original then A, B, C and so on. For software dependent manuals, the
issue suffix letter corresponds to each major software release.
Other manuals, such as hardware service manuals, are re-issued as and when required,
and are not linked to a particular software release. Some other manuals contain
cumulative release information that is backward compatible, or cover more than one
release. Therefore, these manuals do not conform to the above suffix letter criteria.
Table 1-1 shows a typical issue history for a software dependent manual with the
identifying order number 68P02900W15 (an example only).
Table 1-1 Typical manual history
Order Number
Date of issue
Remarks
68P02900W15-O
03 Oct 1994
Software Release 1.2.2.x
68P02900W15-A
30 Dec 1994
68P02900W15-B
01 Sep 1995
68P02900W15-C
31 May 1996
68P02900W15-D
17 Dec 1996
68P02900W15-E
29 Aug 1997
Software Release GSR2 (1.5.0.x)
68P02900W15-F
27 Apr 1998
Software Release GSR3 (1.5.1.x)
68P02900W15-G
12 Mar 1999
Software Release GSR4
68P02900W15-H
24 Oct 2000
Software Release GSR4.1
68P02900W15-J
31 Jul 2001
Software Release GSR5
68P02900W15-K
30 Nov 2001
Software Release GSR5.1
68P02900W15-L
15 Nov 2001
Software Release GSR6 FT
Example
The order number, in this example is 68P02900W15-F, it is divided into three parts:
14
1.
The first three characters (68P) identifies the item as a technical manual.
2.
The second eight characters (02900W15) are allocated from a sequential list of
numbers, which are in effect unique identity numbers.
3.
The final letter is the issue suffix as described above.

68P02901W01-M
02 May 2003
Distribution of Motorola manuals
GSR6 (Horizon II)
Distribution of Motorola manuals

Updating manuals
Up-issuing a manual
For each new major software release, affected release dependent manuals are revised
and re-issued. When this happens, the issue suffix letter of the Order number
increments by one letter of the alphabet, for example, release GSR3 manuals have the
suffix -F and release GSR4 manuals have the suffix -G.
Other manuals, such as hardware service manuals, are up-issued as and when required
and do not follow the above suffix letter rules, but are sequentially lettered from O for
Original, followed by A, B and so on.
General Manual Revisions (GMRs)

GMRs are produced to update and correct manuals when required between major
releases. A GMR may be produced for release dependent manuals when a software
point release is issued. For all manuals, GMRs are produced to incorporate minor
technical changes and to correct any errors. An updated version of the documentation
CD-ROM is produced when the GMRs are incorporated in the manuals.
Motorola Order Fulfilment maintain a database of customers. Any customer who has
ordered manuals for a particular release will be supplied automatically with GMRs, as
and when they are produced. Similarly, any customer who has ordered a documentation
CD-ROM for a particular software load will be supplied automatically with the GMR
version of that CD-ROM.
Where a documentation CD-ROM is supplied free of charge, as part of the software load
package, an updated CD-ROM will be supplied, when available, by Motorola Controlled
Roll Out (CRO) Group.
Ordering manuals
Motorola manuals for customers must be ordered through the Motorola Local Office or
Representative. Manuals are ordered using the Order number. Remember to specify
the manual issue required by quoting the correct suffix letter, which relates to the
software load supported.
Available formats
Motorola manuals are available in the following formats:
S
Hardcopy
Motorola manuals are available in A4 and A5 paper sizes, also some manuals are
available in Wire bound.
CD-ROM
A CD-ROM containing all the GSM manuals. The data is structured in a navigable
Portable Document Format (PDF) to facilitate ease of search and location of
specific blocks of information.
Extranet
This facility offers direct online accessibility of Motorola manuals. The data
available is the same structured PDFs which are available on the CD-ROM
02 May 2003
68P02901W01-M
15
Overview of Motorola manuals
GSR6 (Horizon II)

A further listing of the Motorola manuals showing the various catagories can be found in
the front part of this manual under the name Motorola manual set.
Manual types
Table 1-2 provides a brief overview of the various manual types.
Table 1-2 Types of Motorola manuals
Manual Type
Service
Description
Contain service information for:
BSC.
BTS.
XCDR.
RXCDR.
GSN.
PCU.
System information
Contain system information for:

BSS equipment planning.
BSS Overview, DataGen.
Network Health Analyst.
Operating information
Contain the functions and procedures required to

perform:
Day-to-day operation of the network at OMC-R.
Management functions on the OMC-R.
Procedures to manage the OMC-R, users,
database, X.25 and troubleshooting tasks.
Management functions on the Open Systems
Interconnection (OSI).
Technical information
Contain technical descriptions of:

BSS implementation.
OMC-R database schema.
BSS Man Machine Interface (MMI) command
and parameter descriptions.
Configuration
Contain configuration procedures for:

Configuration of the Motorola GSM Network
Elements (NEs).
Installation and configuration of the optional
OSI processor.
Configuration and optimization information for
the Base Station System Control cabinet
(BSSC) and various BTS cabinets.
Scaleable OMC system staging and customer
site intallation procedures.
16

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Manual Type
Description
Installation
Contain installation procedures for:

BSC.
BTS.
XCDR.
RXCDR.
GSN.
PCU.
Maintenance information
Contain maintenance information for:

Alarm handling at the OMC-R.
BSS field troubleshooting.
GSM statistics application.
Device state transitions.
BSS software timers.
Parts information
Some service manuals contain Parts information.
Software release notes and

Upgrade Guides
Contain software release notes for:

Network Health Analyst.
OMC-R OSI System.
BSS/RXCDR.
Scaleable OMC-R.
Upgrade Guides for:
DataGen.
Other manuals
Contain information for:

SPARCstation.
INFORMIX.
Printer.
X.25.

02 May 2003
68P02901W01-M
17
Summary of Motorola manuals
GSR6 (Horizon II)

These descriptions are generic and not specific to any software release version.
Service manuals - BSS

68P02901W37 Service Manual: BTS
The manual contains hardware service information for the GSM base transceiver station
equipments BTS4, BTS5, and BTS6. It consists of one loose leaf binder containing the
following:
S
68P02901W02 General Information.
68P02901W03 Technical Description.
68P02901W04 Installation and Configuration.
68P02901W05 Maintenance Information.
68P02901W38 BSC/RXCDR
The manual contains hardware service information for the GSM base station controller
(BSC) and remote transcoder (RXCDR) equipment. It consists of one loose leaf binder
containing the following:
S
The manual contains hardware service information for the base station controller 2
(BSC2) and remote transcoder 2 (RXCDR 2) equipment, comprising the following.
S
The manual contains hardware installation and configuration information for the GPRS
base station controller 2 (BSC2) and remote transcoder 2 (RXCDR2) equipment.
68P02901W75 M-Cell2
The Service Manual contains details of the M-Cell2 base station equipment. It contains
the following:
18

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
68P02901W85 M-Cell6
The Service Manual contains details of the M-Cell6 base station equipment. It contains
the following:
S
68P02901W95 M-Cellcity and M-Cellcity+

The Service Manual contains details of the M-Cellcity and M-Cellcity+ micro GSM base
station equipment. It comprises one binder containing the following:
S
68P02901W65 M-Cellaccess
The manual contains hardware service information for the M-Cellaccess GSM base
transceiver station equipment. It comprises one loose leaf binder containing the
following:
S
68P02901W69 Parts Information.
68P02901W90: M-Cellmicro Documentation Set

The documentation set contains details of the M-Cellmicro base station equipment. It is
not a single manual, but comprises three loose leaf binders (each of which may be
ordered separately) containing the following:
S
68P02901W93 Installation and Commissioning.
68P02902W36 Horizonmicro
The Service Manual contains details of the Horizonmicro (formerly M-Cellarena) GSM
base transceiver station equipment. It comprises one binder containing the following:
S

02 May 2003
68P02901W01-M
19
GSR6 (Horizon II)
68P02902W15 Horizoncompact
The Service Manual contains details of the Horizoncompact (formerly M-Cellarena macro)
and RF Booster, which together form a macro GSM transceiver base station equipment.
It comprises one binder containing the following:
S
68P02902W06 Horizonmacro Indoor

The Service Manual contains details of the six carrier Horizonmacro indoor BTS
equipment. It comprises one binder containing the following:
S
68P02902W12 Horizonmacro Outdoor

The Service Manual contains details of the six carrier Horizonmacro outdoor BTS
equipment. It comprises one binder containing the following:
S
68P02902W61 Horizonmicro2 and Horizoncompact2

The Service Manual contains details of the Horizonmicro2 and Horizoncompact2 base
transceiver station equipment. It comprises one binder containing the following:
S
68P02902W66 Horizonmacro 12 Carrier Outdoor

The Service Manual contains details of the Horizonmacro 12 Carrier Outdoor base
transceiver station, which is an outdoor enclosure into which one or two standard six
carrier Horizonmacro indoor cabinets are fitted. It comprises one binder containing the
following:
110

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
68P02902W96 Horizon II macro

The Service Manual contains details of the Horizon II macro base transceiver station,
comprising the following information.
S
Technical Description.
Maintenance Information.
Parts Information.
68P02902W97 Horizon II macro

The Service Manual contains installation and configuration details for the
Horizon II macro base transceiver station.
Service manuals - GPRS

68P02903W05-A GPRS Support Node (GSN)
The Service Manual contains hardware service information for the GPRS Support Node
(GSN). The GSN is connected to the BSS, via the PCU, and is controlled from the
OMC-G. It comprises one binder containing the following:
S
68P02903W05-B GPRS Support Node (GSN)

The Service Manual contains hardware service information for the GPRS Support Node
(GSN). The GSN is connected to the BSS, via the PCU, and is controlled from the
OMC-G. It comprises one binder containing the following:
S
Parts Information.
68P02903W07-B GPRS Support Node (GSN)

The Service Manual contains legacy installation and configuration information for the
GPRS Support Node (GSN). The GSN is connected to the BSS, via the PCU, and is
controlled from the OMC-G.
68P02903W23-A GPRS Support Node (GSN)

The Service Manual contains common installation and configuration information for the
GPRS Support Node (GSN). The GSN is connected to the BSS, via the PCU, and is
controlled from the OMC-G.
68P02903W10-A Packet Control Unit (PCU)

The Service Manual contains hardware service information for the GPRS packet control
unit (PCU). The PCU is connected to the BSS and is controlled from the OMC-R. It
comprises one binder containing the following:
S

02 May 2003
68P02901W01-M
111
GSR6 (Horizon II)
68P02903W10-B Packet Control Unit (PCU)

The Service Manual contains hardware service information for the GPRS packet control
unit (PCU). The PCU is connected to the BSS and is controlled from the OMC-R. The
manual comprises one binder containing the following:
S
Parts Information.
68P02903W12-B Packet Control Unit (PCU)

The Service Manual contains legacy installation and configuration information for the
GPRS packet control unit (PCU). The PCU is connected to the BSS and is controlled
from the OMC-R.
68P02903W24-A Packet Control Unit (PCU)

The Service Manual contains common installation and configuration information for the
GPRS packet control unit (PCU). The PCU is connected to the BSS and is controlled
from the OMC-R.
System information manuals

68P02900W21 BSS Equipment Planning
The manual contains information about planning a GSM network using Motorola
equipment. The manual includes all the M-Cell planning information from 68P02900W31,
which is now discontinued.
68P02900W22: DataGen
The manual contains information on how to install and use DataGen. It also contains
details of the offline MIB.
68P02900W25 Advance Operational Impact

The manual provides a single source of information on the impact of a new GSM
software load. The purpose of the manual is two-fold:
S
It provides advance information on a per feature basis for planning purposes.
It provides a library of feature specific information for reference purposes.
The manual is available some time before the general availability of the features
described.
68P02900W36 Network Health Analyst

The manual outlines the Network Health Analyst (NHA) staging procedures and the
customer site installation procedures. The procedures consist of preparation of the
hardware platform, interconnection of the processor via ethernet, loading and
configuration of the system software. Details of the site requirements, on site installation
procedures, system start-up procedures and system backup and recovery procedures
are included.
68P02901W01 GSM Overview

The manual contains an overview of the Global System for Mobile Communications
(GSM), as implemented by Motorola. The manual also contains a description of the
Motorola document set, specifications for Motorola entities, a summary of Motorola
software release features and a glossary of technical terms and acronyms. The
information is intended for use by all GSM operations and maintenance personnel.
112

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Operating information manuals

68P02901W10 OMC-R System Administration (OSI)
The manual provides information on procedures required to perform management
functions on the Motorola OSI. The OSI feature is an option of the OMC-R. The OSI
Processor is added to the OMC network configuration and hosts most of the processes
of the OSI feature. The OSI feature contains the Mediation Device (MD) application and
the optional Security Application (SA).
68P02901W14 GSM System Operation

The manual contains the information required for a GSM operator to perform the general
procedures required for the day-to-day operation of the network at the Motorola
Operation and Maintenance Centre Radio (OMC-R).
Only available as part of the OMC-R on-line help information.
NOTE
68P02901W19 OMC-R System Administration

The manual provides information on procedures required to perform management
functions on the Motorola Operation and Maintenance Centre Radio (OMC-R).
Procedures to manage the OMC-R system, the users, the database, X.25 and perform
troubleshooting are described.
Technical description manuals

68P02901W23 BSS Command Reference
The manual contains descriptions of the BSS MMI commands and parameters used
within the Motorola GSM system.
68P02901W34 OMC-R Database Schema

The manual is a technical reference to support the procedures provided in the GSM
Operation and Administration manuals. It contains a complete description of the OMC
database schema. This information can be used to customize database reports.
NOTE
Only available on the CD-ROM.
68P02901W36 BSS Implementation

The manual provides a functional description of the BSS and the specific operations that
are controlled by the BSS. Information is provided on implementation and equippage of
the devices, functions and links required to facilitate BSS operation.

02 May 2003
68P02901W01-M
113
GSR6 (Horizon II)
Installation and configuration manuals

68P02901W17 GSM System Configuration
The manual provides information on procedures to configure the Motorola GSM Network
Elements (NEs) and thus populate the Configuration Management database.
68P02901W39 OSI Clean Install

The manual describes the staging and on site procedures for the installation and
configuration of the optional OSI Processor at the OMC-R. The procedures consist of
the preparation of the hardware, and the loading and configuration of the system
software. It also describes the installation, configuration and start-up of the OSI
Processor specific software.
68P02901W43 BSS Optimization

The manual contains configuration and optimization information for the BSSC and the
various BTS cabinets in Motorola GSM, EGSM, DCS1800 and PCS 1900 systems. The
manual contains details of the optimization and base site integration.
68P02901W47 Scaleable OMC-R Clean Install

The manual outlines the Scaleable OMC system staging procedures and the customer
site installation procedures. The staging procedures consist of preparation of the
hardware platform, interconnection of the processors and printer via ethernet, and
loading and configuration of the system software. Details of the site requirements, on
site installation procedures, system start-up procedures, and system backup and
recovery procedures are included.
Use with systems deploying Scaleable OMC.
Maintenance information manuals

68P02901W26 Alarm Handling at the OMC-R
The manual includes GSM alarm reference information. In addition, alarm diagnostics
information and procedures are included to resolve fault conditions from the Operations
and Maintenance Centre-Radio (OMC-R).
68P02901W51: BSS Field Troubleshooting

The manual contained troubleshooting and diagnostic procedures for field engineers or
technicians to follow at Base Station System (BSS) or Remote Transcoder (RXCDR)
sites. These procedures presume that operators at the Operations and Maintenance
Centre Radio (OMC-R) have diagnosed a problem, and have dispatched the engineer
or technician to the site to try and fix the problem from there.
68P02901W56 GSM Statistics Application

The manual contains information on the statistics used in a Motorola GSM network. It
provides a detailed description of all the statistics and their uses. A brief description of
the network interfaces, links, and protocols is also provided. The MMI commands used
to perform statistical operations (enabling, disabling and displaying) are also identified
and described.
68P02901W57 Device State Transitions

The manual contains an overview of the functionality and the transition states associated
with the devices supported in the Motorola GSM BSS.
114

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
68P02901W58 BSS Timers

The manual contains information on the timer based software parameters within the
Motorola GSM BSS. The information is provided for network optimization purposes.
Software release notes

68P02900W76: Software Release Notes: DataGen
The manual contains the DataGen software release notes and upgrade guides.
68P02900W77: Network Health Analyst

The manual contains the Network Health Analyst (NHA) software release notes.
68P02901W70: OMC-R OSI System

The manual contains the optional OSI software release notes and upgrade guides.
68P02901W72: BSS/RXCDR
The manual contains the BSS software release notes.
68P02901W74: Scaleable OMC-R System

The manual contains the Scaleable OMC-R software release notes and upgrade guides.

02 May 2003
68P02901W01-M
115
Other manuals
GSR6 (Horizon II)
Other manuals
Introduction
The manuals listed in the following sections are supplied to customers where
appropriate.
SPARC E3000/E3500
The SPARC E3000/E3500 and associated equipment is supplied with the relevant
manuals.
SPARCstation manuals
The SPARCstation is supplied with AnswerBook CD-ROM based on-line documentation.
This typically includes the following:
S
Release and Install binder.
Users Guide books.
Systems and Network Administration binder.
SunOS Reference Manual binder (three volumes).
Global Index binder.
SunOS Documentation Tools binder.
Programmers Guides binder.
Programmers Overview Utilities and Libraries binder.
Network Programming Guide binder.
Writing Device Drivers/STREAMS Programming binder.
SunView Programmers Guide binder.
SunView 1 System Programmers Guide binder.
INFORMIX manuals
INFORMIX 7 documentation may be obtained by ordering the following :
S
Part Number:
SWDN5378.
Printer manuals
The following manuals are typically supplied with the printer :
S
Laser Printer Manual.
X.25 manuals
The following manuals are typically supplied with the ISG equipment:
116
6250 Operators Guide/Installation Guide.
6500 Series Product Documentation.
6560 Operators Guide/Installation Guide.

68P02901W01-M
02 May 2003
Chapter 2
Introduction to Motorola GSM

02 May 2003
68P02901W01-M
21
GSR6 (Horizon II)
22

68P02901W01-M
02 May 2003
Chapter overview
GSR6 (Horizon II)
Chapter overview
Introduction to GSM system information
This chapter contains an introduction to the Global System for Mobile communications
(GSM) which includes GSM850, GSM900, Extended GSM (EGSM), Digital
Communications System 1800 (DCS1800) and Personal Communications System 1900
(PCS1900) digital cellular systems.
It is divided into the following main sections:
Overview of the Motorola GSM system

This section provides a high-level description of the Motorola cellular system. It also
includes illustrations that show the Motorola BSS architecture and a typical GSM system.
Unique features of Motorola GSM

This section describes some features of GSM as implemented by Motorola.
Motorola network specifications

This section introduces the Motorola GSM speicfications.
Security management
This section describes the three password levels required to access some commands in
the BSS system.
Mobile station
This section provides an introduction to the mobile station and descriptions of
components and mobile equipmnent.
GSM network specifications and recommendations

This section introduces the GSM specifications and recommendations for cellular
telephone networks.
GSM network elements

This section describes the major elements of the GSM network.
GSM subsystems (non-network elements)

This section describes the subsystem elements of the GSM network.
GSM system features and goals

This section describes in more detail GSM features and the technology requirements for
GSM and summarizes the goals of the GSM specifications.
E1/T1 links
This sections describe the physical link elements of the GSM network.
Standardized interfaces
These section describes the interfaces used on the GSM network.
02 May 2003
68P02901W01-M
23
Chapter overview
GSR6 (Horizon II)
Network protocols
This section describe the protocols used on the GSM network.
GSM frequencies and channels

This section describes frequency allocations for GSM850, GSM900, Extended GSM,
DCS1800 and PCS1900 digital cellular systems with their associated channel numbers.
24

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

The Motorola GSM system
Motorolas GSM cellular system provides radio coverage for communications with GSM
subscribers in a defined area. Its principle role is to support signalling and traffic channels
for Mobile Stations (MS)s across the Public Land Mobile Network (PLMN).
Network element overview

The GSM network incorporates a number of network elements to support mobile
telephones and other mobile equipment (known collectively as Mobile Stations, or MSs).
These elements form the major components of the GSM network.
Network Management Centre

The Network Management Centre (NMC) administers the entire cellular network to
provide operations and maintenance at the network level. Figure 2-1 shows the NMC
relationship to the other network elements.
Operations and Maintenance Centre-Radio

The Operations and Maintenance Centre-Radio (OMC-R) is a regional site which controls
and monitors the daily operation of network elements within its region and the quality of
service provided by the network. Figure 2-1 shows the OMC-R relationship to the other
network elements.
Mobile services Switching Centre

The Mobile services Switching Centre (MSC) is a telephone switching office for handling
calls to and from the MSs within a defined geographical area. The MSC also provides
the interface between the cellular network and the ordinary land-based Public Switched
Telephone Network (PSTN), allowing the GSM cellular system to function as an
extension of the PSTN. It also allows the GSM network to interface to other PLMNs.
There can be a number of MSCs within the region controlled by an OMC. Figure 2-1
shows the MSC releationship to the other network elements.
Locaton registers
Three Location Register (LR) network elements may be collocated with the MSC. These
are database-oriented processing nodes that manage subscriber data and keep track of
the location of an MS as it roams around the network. For detailed information regarding
LRs see the Mobile services Switching Centre section in this chapter.
The following are the LRs in the GSM Network:
S
Equipment Idnetity Register (EIR)
Home Location Register (HLR)
Visitor Location Register (VLR)

02 May 2003
68P02901W01-M
25
GSR6 (Horizon II)
Base Station System

The Base Station System (BSS) is the fixed end of the radio interface that provides
control and radio coverage functions for one or more cells and their associated MSs. It is
the link between the MS and the MSC. The BSS comprises one or more Base
Transceiver Stations (BTSs), each containing the radio components that communicate
with MSs in a given area, and a Base Site Controller (BSC) which supports call
processing functions and the interfaces to the MSC. Digital radio techniques are used for
the radio communications link, known as the Air Interface, between the BSS and the MS.
The BSS comprises:
S
Base Station Controller (BSC)

The BSC controls one or more Base Transceiver Stations (BTSs) and acts as the
digital processing interface between the BTS and the MSC. Detailed information
regarding the BSC can be found in Chapter 3 BSC description of this manual.
Base Transceiver Station (BTS)

The BTS contains the radio components that provide the interface to Mobile
Stations for one or more coverage areas or cells. Detailed information regarding
the BTS can be found in Chapter 3 BTS description of this manual.
Full-rate Transcoder (XCDR) and Remote Transcoder (RXCDR)

The Full-rate Transcoder (XCDR) is the digital signal processing equipment
required to perform GSM-defined speech encoding and decoding. In terms of data
transmission, the speech transcoder interfaces the 64 kbit/s PCM in the land
network to the 13 kbit/s vocoder format used on the Air Interface.
The Remote Transcoder (RXCDR) is used when the transcoding is performed at a
site away from the BSC, which is at or near the MSC. This enables 4:1
multiplexing in which the transcoded data for four logical channels is combined
onto one 64 kbit/s link, thus reducing the number of links required for
interconnection to the BSCs. Detailed information regarding the XCDR and
RXCDR can be found in Chapter 3 Transcoder description of this manual.
Packet Control Unt (PCU)

The PCU is an interface adaptor handler unit that permits the Motorola GSM
facility access to the packet network. As such the PCU needs interfaces with the
BSC on the GSM side, and the SGSN on the packet network side. The PCU
manages the packet radio interface and also enables the interface from the BSS to
the SGSN. The PCU itself, is managed by the existing OMC-R. Detailed
information regarding the PCU can be found in Chapter 3 Packet Control Unit of
this manual.
26

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
The Motorola GSM equipment architecture is shown in Figure 2-1 with other associated
network elements. The BSS components are shown shaded. Also shown is the GPRS
network architecture.
Figure 2-1 GSM and GPRS Architecuture (GSN Complex)

GSM EQUIPMENT
MSC
GSN EQUIPMENT
RADIUS SERVER
(NON-TRANSPARENT
MODE)
HLR
RXCDR
PDN
OMC-G
(Including Shelf
Manager)
OMC-R
BSC
PCU
ISS
BSSn
GGSN
GSN
COMMHUB
BSS2
BTSs
SGSN
GSNn
GSN1
BSS1
BILLING
SYSTEM
OPERATOR SERVER
COMPLEX
- RADIUS SERVER
(OPERATOR IS ISP,
TRANSPARENT MODE)
- DHCP SERVER
- DNS SERVER

02 May 2003
68P02901W01-M
27
GSR6 (Horizon II)
Typical GSM system

Figure 2-2 shows a typical layout of a system with two BSSs. Each BSS contains several
components to make the link between the MS and the MSC. The BSS components are
described in more detail later in this manual.
Figure 2-2 Typical GSM system layout Dual BSS system

EIR
AUC
HLR
EIR
MOBILE n
MOBILE n
VLR
VLR
MSC
MSC
XCDR
XCDR
EC
IWF
OMC-S
1001101
1001101
EC
BSS
BSC
NMC
MODEMS TO
OTHER NETWORKS
BSS
BTS
BSC
BTS
BTS
OMC-R
BTS
BTS
BTS
BTS
PSTN
and
ISDN
MS
MS
28

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

Introduction to the unique features of Motorola GSM
The following describes aspects of GSM equipment that are unique to Motorola. See
Chapter overview in Chapter 3 of this manual for a general description of the Motorola
BSS.
Systems advantages
Features of Motorola systems that can be used to maximise GSM capacity include
unique reuse patterns, sector sharing, and equipment sharing. Many of these features
are ideal for the system operator who has a limited number of radio channels with which
to initiate system operation.
Other features take maximum advantage of unique GSM capabilities. For example,
synchronization is provided to allow the rapid handover and in Motorola systems also
provides enhanced frequency hopping and flexible traffic channel allocation when a
limited number of GSM channels is available. Enhanced algorithms and techniques will
improve handover decisions and minimise handover traffic loading on the system.
System planning
A system planning capability, currently under development, is a computer program (using
artificial intelligence techniques) to assist and provide a degree of automation for
frequency planning. A plan checker capability will be included. The system includes
facilities for user interaction and user friendly (graphical) presentation of plan results and
system statistics. Future interconnection with the OMC to provide a feedback path for
performance assessment and learning is also anticipated.
Fault tolerance
All Motorola network equipment is designed with inherent fault tolerance. All network
elements except the BTS are designed to be fault tolerant to any single point failure. The
BTS is designed to provide redundancy economically, as required.
Maintenance
The cost of maintenance is an issue regarding the operation of a cellular network,
especially where cell sites are widely separated. Motorola equipment is high quality,
incorporating highly tolerant engineering design and manufacturing.
S
Extensive board-level self-diagnostics.
An extensive variety of alarms and indicators throughout the equipment.
Self-calibrating subsystems, including PA and Receiver (Rx) sensitivity.
Circuit designs that do not require tuning and are immune to drift. (For example,
direct digital synthesis for the modulation, etc).
Remotely and software controllable parameters, including transmitter power and

cavity frequency.
High-performance circuit and system designs that meet the intent of the GSM
recommendations. (For example, a low noise figure receiver achieving GSM
intermodulation rejection and spurious response rejection specifications).
02 May 2003
68P02901W01-M
29
GSR6 (Horizon II)
Future system
Note that a number of GSM services are not completely specified. As GSM
recommendations mature, Motorola intends to support them. Motorola anticipates a
continual system upgrade process which includes new feature introductions and system
evolution.
GSM is well positioned for the introduction of additional Intelligent Network (IN)
capabilities. As both the IN and the ISDN continue to expand, adding services and
facilities, Motorola will keep pace by providing interconnection to these services; and
thereafter, make these services available to GSM subscribers.
210

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

Introduction to Motorola network elements
The following sections provide specifications for the Motorola Network Elements (NEs) in
the GSM system (including EGSM, DCS1800 and PCS1900). Specifications described
in this secton are:
S
OMC-R.
Receiver.
Transmitter.
OMC-R specifications
The Motorola Operations and Maintenance Centre - Radio (OMC-R) is a UNIX-based
system. Specifications and performance data are provided in the following sections. The
OMC-R configuration for each software release is detailed in Chapter 6.
These specifications are for the Sun scaleable OMC-R platforms.
Functions of the OMC-R

The functions of the OMC-R are specified in the 12-series GSM Recommendations.
These are based on ITU-TSS recommendations. For example, ITU-TSS Rec. M.30.
Table 2-1 shows a list of functions together with GSM and ITU-TSS references
appropriate to each.
Table 2-1 OMC-R functions and GSM & ITU-TSS references
Function
Reference
Event and Alarm Management
GSM 12.07.
Fault Management
GSM 12.07.
Performance Management
GSM 12.04 and 12.07 (based on ITU-TSS

E.411, for example).
Configuration Management
GSM 12.07.
Security Management
GSM 12.03.
OMC-R Man Machine Interface

(MMI) and MML
ITU-TSS M.251 [44], and Z.301 to Z.337

[97 to 114].
Safety and protection aspects of

OMC operation
ITU-TSS E.410.

02 May 2003
68P02901W01-M
211
GSR6 (Horizon II)
System processor
The SUN ULTRA ENTERPRISE 3500/3000 system processor is a UNIX system. Acting
as the OMC system processor, it runs the OMC application software which handles all
O&M communication with the NE. It processes all incoming events, alarms,
uploads/downloads, and performance statistics, and the setting up of remote login
sessions to different NEs. The system processor contains a database based on an
INFORMIX Database Management System (DBMS), configured for storing performance
statistics, subscription lists, and network and map configuration data, enabling operators
to monitor incoming events and alarms.
System processor configurations

Table 2-2 provides a comparison between the Low-End (5 k TCH), mid range (10 k and
30 k TCH) and High-End (45 k TCH) OMC configurations.
Table 2-2 OMC configurations (maximum values)
Feature
OMC
Low-End
(5 k)
OMC
OMC
Mid-Range Mid-Range
(10 k)
(30 k)
OMC
High-End
(45 k)
Maximum RTFs supported
714
1430
4285
6000
NEs supported
15
30
120
120
Total GUI sessions supported
10
10
10
30
Dial-up sessions per GUI

Processor
Total remote dial-up sessions
Remote login sessions
20
30
Simultaneous downloads
12
12
Simultaneous uploads
16
32
Sustained event rate
8 alarms +
2 state
changes
8 alarms +
2 state
changes
12 alarms
+ 3 state
changes
12 alarms
+ 3 state
changes
Maximum event burst
20 events/s 60 events/s 60 events/s 60 events/s

over 20
over 20
over 20
over 20
mins
mins
mins
mins
A packet switch/multiplexer is required with the HSI/S card.

The E3500/E3000 system processor runs the Solaris 2.5.1 Operating System (OS).
The OMC uses an optional laser printer.
Operator workstations
The remainder of the OMC is made up of operator workstations, and is primarily
concerned with running the OMC operator interface, known as the OMC Graphical User
Interface (GUI). Typically the OMC configuration will contain a single application GUI
server, and several ULTRA/SPARCstation 5 workstations as GUI clients. Alternatively
newer workstations can be connected directly as GUI servers. Each operator
workstation is a complete UNIX system.
The operator workstations execute the OMC GUI software.
Optional processors
Optional processors, such as those for Mediation Device (OSI), Remote Login, Offline
BSS Configurator, can be included in the basic OMC configuration.
212

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
OMC configuration
The OMC, a system configuration based on SUN E3500/E3000 System Processor
hardware, is supplied in Low-End (5 k TCH), Mid-End (10 k or 30 k TCH) and High-End
(45 k TCH) versions. The hardware requirements (hard disks, CPUs, and so on) varies
depending on the version and System Processor in use, as does the disk partitioning.
This section describes the hardware architecture requirements for each System
Processor and each version, and the common software requirements.
Data communication
The OMC-R uses standard X.25 communication protocols on the interfaces with other
entities in the network.
For example, the NMC-OMC interface is defined in GSM 12.01 and corresponds to the
Q3 type of interface according to ITU-TSS M.30 [1]. The OMC-R X.25 capacities are in
Table 2-3.
Table 2-3 OMC-R/X.25 capacities
Functional area
Capacity
X.25 ports
8 V.35 ports @ 64 kbit/s (1 not used by the

Scaleable OMC).
X.25 virtual circuits per X.25 port
32 virtual circuits per X.25.
X.25 virtual circuits (aggregate)
192 total virtual circuits.
X.25 packets per second
100 packets per second (128-byte packets),

aggregate.
Speed
100 kbit/s per second, aggregate.

02 May 2003
68P02901W01-M
213
GSR6 (Horizon II)
Receiver specifications
Table 2-4 lists the specifications for the receiver.
Table 2-4 Receiver specifications
Functionality
Frequency range
Specification
GSM850
GSM900
824 to 849 MHz

890 to 915 MHz.
Extended GSM900
DCS1800
880 to 915 MHz.

1710 to 1785 MHz.
PCS1900
1850 to 1910 MHz.
Channel spacing
200 kHz.
Frequency stability
0.05 ppm.
RF sensitivity
(reference sensitivity)
The Receiver minimum sensitivity levels for GSM850,

GSM900/EGSM900, DCS1800 and PCS1900 are as
follows.
Each receiver input shall have a minimum sensitivity of
104 dBm complying with GSM 05.05, section 6.2, as
measured according to the method of GSM 11.20/11.21.
CTU, DRCU, SCU, TCU
TCU-B
As above, but minimum sensitivity of 108.5 dBm.
Diversity gain
(DRCU models only)
Both branches meet performance specifications stated

above.
Under flat Rayleigh faded conditions with V = 50 km/h,
class II RBER, class 1b RBER, and FER are evaluated.
Diversity gain can range from 2 to 7 dBm depending on
the individual system and measurement conditions.
S
Rx inputs perfectly correlated;

diversity gain Gd = 1.5 dB.
(1 to 2 dB is the approximate range.)
Rx inputs perfectly uncorrelated;

diversity gain Gd = 5 dB.
(4 to 6 dB is the approximate range.)
The above gains are measured relative to the signal level

of the poorest RX branch at any given time.
For channel type specifications, see GSM 05.05, section
6.2; refer to table 1 corresponding to section 6.2.
214

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Functionality
Specification
Nominal error rates
There are three additional Residual Bit Error Rates

(RBER): TCH/FS Class II RBER as a function of
propagation condition.
The RBER values vary depending the RBER type and
power level:
Static BER < .01% for input levels up to 40 dBm.
Static BER < .1% for input levels > 40 dBm.
EQ50 channel BER < 3%.
This performance shall be maintained for a mean signal
input level between 85 dBm and 40 dBm. The static
performance shall be maintained for signal level up to
15 dBm for GSM850/900 and 23 dBm for DCS1800 or
PCS1900.
Intermodulation rejection
The Intermodulation Rejection power levels for

GSM850/900 and DCS1800 or PCS1900 are as follows.
S
43 dBm minimum level for GSM850/900.
S
49 dBm minimum level for DCS1800/PCS1900.
These values comply with GSM 05.05, section 5.3, as

Spurious response rejection The Spurious Response Rejection power levels for
GSM850, GSM900, DCS1800 and PCS1900 are as
follows.
S
57 dBm: 9 kHz to 1 GHz.
S
47 dBm: 1 GHz to 12.75 GHz.
These values comply with GSM 05.05, section 5.4, as

(See the Note).
Blocking (GSM850)
The In-Band Blocking Signal Frequency Range is 804 to

869 MHz for GSM850.
Minimum power levels are as follows.
S
600 kHz < | 0| < 800 kHz: 26 dBm.
800 kHz < | 0| < 1 GHz: 16 dBm.
1 GHz < | 0| < 3 MHz: 16 dBm.
3 MHz < | 0|: 13 dBm.
Out-of-Band Blocking Signal Frequency Range:

S
100 kHz < < 870 MHz: 8 dBm (GSM850).
925 MHz < < 12.75 GHz: 8 dBm.
These blocking characteristics comply with GSM 05.05,

section 5.1, as measured according to the method of
GSM 11.20/11.21. (See the Note).

02 May 2003
68P02901W01-M
215
GSR6 (Horizon II)
Functionality
Blocking (GSM900)
Specification
The In-Band Blocking Signal Frequency Range is 870 to
935 MHz for GSM900; and 860 to 925 for EGSM900.
S
600 kHz < | 0| < 800 kHz: 26 dBm.
800 kHz < | 0| < 1 GHz: 16 dBm.
1 GHz < | 0| < 3 MHz: 16 dBm.
3 MHz < | 0|: 13 dBm.

S
100 kHz < < 870 MHz: 8 dBm (GSM900).

100 kHz < < 860 MHz: 8 dBm (EGSM900).
925 MHz < < 12.75 GHz: 8 dBm.
These blocking characteristics comply with GSM 05.05,

Blocking (DCS1800)
The In-Band Blocking Signal Frequency Range 1690 to

1805 MHz.
S
600 kHz < | 0| < 800 kHz: 35 dBm.
800 kHz < | 0|: 25 dBm.

S
100 kHz < < 1690 MHz: 0 dBm.
1805 MHz < < 12.75 GHz: 0 dBm.
The blocking characteristics comply with GSM 05.05,

Blocking (PCS1900)
The In-Band Blocking Signal Frequency Range is1830 to

1930 MHz.
S
600 kHz < | 0| < 800 kHz: 35 dBm.
800 kHz < | 0|: 25 dBm.

S
100 kHz < < 1690 MHz: 0 dBm.
1805 MHz < < 12.75 GHz: 0 dBm.
The blocking characteristics comply with GSM 05.05,

Interference performance
216
The Interference Performance is as specified in

GSM 05.05, section 6.3, as measured according to the
method of GSM 11.20/11.21.
The following refer to the C/I ratios:
S
Co-Channel Interference: 9 dB.
Adjacent Channel Interference: 9 dB

(TU50 only).
Alternate Channel Interference: 41 dB

(TU50 only).

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
For information regarding the exceptions that are related to the

blocking and spurious response rejection test, consult GSM
05.05, section 5.1 as per GSM 11.20/11.21.
NOTE
Transmitter specifications
Table 2-5 lists the specifications for the transmitter.
Table 2-5 Transmitter specifications
Functionality
Specification
Frequency range
GSM850
GSM900
Extended GSM900
DCS1800
869 to 894 MHz

935 to 960 MHz.
925 to 960 MHz.
1805 to 1880 MHz.
PCS1900
1930 to 1990 MHz.
Channel spacing
With Hybrid Channel Combiners 600 kHz (min).

With Remotely Tunable Channel Combiner 800 kHz (min).
Frequency stability
0.05 ppm.
Phase accuracy within

Timeslot
5 degrees rms, 20 degrees peak within useful part of burst.
Mean carrier output

power
During useful part of burst, measured at the top of the cabinet

after one stage of combining.
CTU, DRCU, SCU,

TCU
CTU, SCU, TCU
20 W 1 dB (GSM850/900).
TCU-B
16 W 1 dB.16 W 1 dB (DCS1800, PCS1900)

If there is no combining, 32 W 1 dB.
Output power adjust

range
12 dB in 2 dB steps. The tolerance is as stated in GSM

05.05, section 4.1.2, as tested according to the method of
GSM 11.20/11.21.
Carrier Off Level
70 dBc or 36 dBm, whichever is greater (Phase 1 GSM),

30 dBc (Phase 2 GSM850, GSM900, DCS1800 and
PCS1900).
Modulation type
GMSK BT = 0.3.
Dynamic power control

range
30 dB, complying with GSM 05.05, section 4.1.2, as

Intermodulation
attenuation
Complies with GSM 05.05, section 4.7.1, as measured

according to the method of GSM 11.20/11.21.
Intra-BTS
intermodulation
attenuation

Spectrum due to
modulation

8 W 1 dB (DCS1800, PCS1900).

02 May 2003
68P02901W01-M
217
GSR6 (Horizon II)
Functionality
218
Specification
Spurious emissions
from antenna
connector

Spurious Signal Frequency
100 kHz to 1 GHz
1 GHz to 12.75 GHz
890 MHz to 915 MHz
Radiated spurious
emissions

RF carrier ramp time
The RF carrier ramp time is 28 msec (max).

68P02901W01-M
02 May 2003
Security management
GSR6 (Horizon II)
Security management
Password levels
Passwords are required to access some commands in the BSS system. There are three
levels of security in the BSS system:
Level 1 - Permits only the display of certain system elements. This is the entrance level
after boot has completed.
Level 2 - Permits access to all user-visible system commands, including changing
passwords for Levels 1 and 2.
Level 3 - Permits access as for level 2, and access to the executive monitor. Two
passwords are required at this level. Only users who have purchased the level 3
password option have access at this level.
Option level 3 control

The optional level 3 control function provides control of the level 3 password at the MMI.
Level 1 is not password protected, and level 2 access is protected by one password that
can be changed by the customer. Level 3 access is normally protected by two
passwords that cannot be changed by the customer. Purchasing this feature allows the
customer to change the Level 3 passwords (and access the Exec Monitor emon) using
the chg_password command, so limiting the distribution of the Level 3 passwords to a
selected group of people.
Releated commands and parameters

The chg_password command can be used to change the two Level 3 passwords, as
well as the Level 2 password.
System impact
At the OMC-R GUI, the TTY (rlogin) and FORMS interfaces support the modified
chg_password MMI command.
A password is no longer required for Level 1 access to the BSS.

02 May 2003
68P02901W01-M
219
Mobile station
GSR6 (Horizon II)
Mobile station
Introduction to mobile stations
The subscriber uses the Mobile Station (MS) to access the services provided by the
PLMN. MSs can be installed in vehicles or can be portable or hand held stations. The
MS can include provisions for data communication as well as voice communication.
Different types of MSs can provide different types of data interfaces. To provide a
common model for describing these different MS configurations, GSM defines reference
configurations for MSs similar to those defined for ISDN land stations.
The Mobile Station (MS) together with the Subscriber Identity Module (SIM) are defined
as the radio equipment and Man-Machine Interface (MMI) that a subscriber needs to
access PLMN services. Typically, this is a mobile telephone though it may also be a
mobile data communications unit.
Mobile station components

The Mobile Station consists of the Mobile Equipment (ME) and the Subscriber Identity
Module (SIM).
Mobile equipment
The Mobile Equipment is the hardware used by the subscriber to access the network.
There are three types:
Vehicle mounted, with the antenna physically mounted on the outside of the
vehicle.
Portable mobile unit, which can be hand held, but the antenna is not on the
handset.
Hand portable unit, which consists of a small handset with the antenna attached
to the handset.
Subscriber Interface Module (SIM)

The SIM is a removable card that plugs into the ME. It identifies the mobile subscriber
and provides information about the service that the subscriber should receive.
Hand portable viability

The GSM specifications for hand portable MSs aim to minimise power consumption by
design features such as:
S
Discontinuous transmission (DTx). This ensures that the hand portable

transmitter is energised only when there is speech or data traffic to transmit.
Discontinuous reception (DRx). This is a group paging technique that allows the
hand portable to cycle to a low drain standby mode as much as 98% of the time.
Active power control. As the hand portable gets closer to the BTS, it uses less
power to transmit. This saves on battery life.
GSM hand portables also incorporate digital signal processing.
220

68P02901W01-M
02 May 2003
Mobile station
GSR6 (Horizon II)
Equipment identity number

International Mobile station Equipment Identity (IMEI)
Each MS is identified by an International Mobile station Equipment Identity (IMEI)
number which is permanently stored in the Mobile Equipment. On request, the MS
sends this number over the signalling channel to the MSC. The IMEI can be used to
identify MSs that are reported stolen or operating incorrectly.
Equipment Identity Register (EIR)

A listing of the allowed IMEIs is maintained by the PLMN in the Equipment Identity
Register (EIR) to validate the mobile equipment.
Subscriber identification
International Mobile Subscriber Identity (IMSI)
Just as the IMEI identifies the mobile equipment, other numbers are used to identify the
mobile subscriber. Different subscriber identities are used in different phases of call set
up. The International Mobile Subscriber Identity (IMSI) is the primary identity of the
subscriber within the mobile network and is permanently assigned to that subscriber.
Temporary Mobile Subscriber Identity (TMSI)

The GSM system can also assign a Temporary Mobile Subscriber Identity (TMSI). After
the subscribers IMSI has been initialized on the system, the TMSI can be used for
sending backwards and forwards across the network to identify the subscriber. The
system automatically changes the TMSI at regular intervals, thus protecting the
subscriber from being identified by someone attempting to monitor the radio channels.
The TMSI is a local number and is always transmitted with the Location Area
Identification (LAI) to avoid ambiguities.
Mobile Subscriber ISDN (MSISDN)

The Mobile Subscriber ISDN (MSISDN) number is the telephone number of the MS.
This is the number a calling party dials to reach the subscriber. It is used by the land
network to route calls toward the MSC.
Home Location Register (HLR) and Visitor Location Register (VLR)

The PLMN holds subscriber data in a series of registers: the Home Location Register
(HLR) and the Visitor Location Register (VLR).
Subscriber Information Module (SIM)

By making a distinction between the subscriber identity and the mobile equipment
identity, a GSM PLMN can route calls and perform billing based on the identity of the
subscriber rather than the mobile equipment being used. This can be done using a
removable Subscriber Information Module (SIM). A smart card is one possible
implementation of a SIM module.
The following information is stored in the SIM:
S
IMSI. This is transmitted at initialization of the mobile equipment.
TMSI. This is updated periodically by the PLMN.
MSISDN. This is made up of a country code, a national code and a subscriber

number.
Local Area Identity (LAI). This identifies the current location of the subscriber.
Subscriber Authentication Key (Ki). This is used to authenticate the SIM.
When the SIM is inserted in the mobile equipment, a location update procedure registers
the subscribers new location, allowing the correct routeing of incoming calls.
02 May 2003
68P02901W01-M
221
GSR6 (Horizon II)

GSM advantages
The advantages of GSM flow from the standardization of the GSM specifications, the
digital nature of the GSM network, and the increased capacity and low error rates
compared with analogue networks.
Digital networks
GSM networks are digital and can cater for high system capacities. They are consistent
with the world-wide digitization of the telephone network, and are an extension of the
Integrated Services Digital Network (ISDN), using a digital radio interface between the
cellular network and the mobile subscriber equipment.
Increase capacity
The GSM system provides a greater subscriber capacity than analogue systems. GSM
allows 25 kHz per user, that is, eight conversations per 200 kHz channel pair (a pair
comprising one transmit channel and one receive channel). Digital channel coding and
the modulation used makes the signal resistant to interference from cells where the same
frequencies are re-used (co-channel interference); a Carrier to Interference Ratio (C/I)
level of 9 dB is achieved, as opposed to the 18 dB typical with analogue cellular. This
allows increased geographic reuse by permitting a reduction in the number of cells in the
reuse pattern. Since this number is directly controlled by the amount of interference, the
radio transmission design can deliver acceptable performance.
222

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Frequency reuse
Cellular networks were developed to circumvent the problems of needing increasingly
powerful radio equipment and having to use a greater number of individual frequencies
as usage increased. With a GSM cellular network, the mobile equipment is not more
than a few kilometres from the transceiver, therefore pairs of frequencies (one for
transmit, one for receive), called reuse groups, can be reused in a geographic repeat
pattern across the network. Figure 2-3 shows a four-cell frequency reuse pattern.
Figure 2-3 Four cell frequency reuse pattern
FREQUENCY
REUSE
GROUP 1
FREQUENCY
REUSE
GROUP 2
FREQUENCY
REUSE
GROUP 3
FREQUENCY
REUSE
GROUP 4
FREQUENCY
REUSE
GROUP 1
REUSED
Audio capacity
Digital transmission of speech and high performance digital signal processors provide
good quality speech transmission. In regions of interference or noise-limited operation
the speech quality is noticeably better than analogue. Where noise or interference
obliterate speech frames, error correction is used to put back some of the missing
information, and if too much information is lost, a digital extrapolation algorithm is used to
fill the gap. While the precise implementation of the extrapolation algorithm is up to the
manufacturer, GSM recommends minimum and maximum permitted extrapolations.
Link integrity
GSM incorporates several features to achieve a high-integrity communication link and to
ensure high quality signalling performance. Call re-establishment procedures allow lost
subscribers to reconnect to an interrupted connection. These procedures reduce the
number of dropped or lost calls.
A unique feature of digital communication is the use of the error control coding to
estimate the bit error rate of the channel being used. In this way the system evaluates
link quality and can take action on co-channel and adjacent channel interference, even
when signal levels are relatively high. A subscriber is handed over to a different cell or
channel if detrimental interference is sensed.
02 May 2003
68P02901W01-M
223
GSR6 (Horizon II)
Subscriber services
Under GSM, subscriber services similar to those provided by an ISDN land network can
be made available to mobile and hand portable Mobile Stations. The Mobile Station is
provided with control channels (similar to the D channel on ISDN) and a traffic channel
for user data or digitized voice (similar to the ISDN B channel). Both data and voice are
carried in digital form on the radio interface, allowing end-to-end digital connections
through the land and GSM networks. The control channels also provide the mobile
subscriber with supplementary services similar to those in the ISDN land network, such
as calling number presentation, closed user groups, and in-call modifications.
Data communications
In addition to provisions for voice communication, GSM MSs can provide either an
ISDN S interface point, or an ITU-TSS X or V-series interface, to connect standard data
terminal equipment. A data interworking function allows interworking with other data
networks such as the ISDN land network. For interworking with an analogue-oriented
Public Switched Telephone Network (PSTN), the function connects data from the mobile
through a modem and converts the modem audio to Pulse Code Modulation (PCM)
format for connection to a PSTN digital trunk. Other types of interworking can also be
provided, such as access to packet-switched and circuit-switched public data networks.
The call set up message from the MS includes information on the MSs bearer capability
to indicate which type of data call is being set up.
Teleservices
GSM provides several categories of teleservices, including basic speech, Short Message
Service (SMS) (for messages such as those sent to a pager built into the MS), message
handling service, facsimile, videotex, and teletext. Data services are also available in
both circuit and packet modes and with a diversity of interworking functions to support
interfaces between the PSTN and the ISDN. This includes traditional land line analogue
modems provided for interface to the land network. Transparent transmission can be
used, which includes error correction. Data rates from 300 to 12,000 bits per second are
provided. If improved error control is desired, data services using a non-transparent
protocol can be invoked. This error detection/retransmission scheme provides for much
reduced net error rates, though the throughput rate is dependent on the radio channel
quality and is not affected by the error control.
Security features
Security features of GSM protect both users and operators against eavesdropping and
the misuse of valuable resources. Specific provisions protect subscriber identity and
authentication, user data, and elements of the signalling information.
224

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

Introduction to GSM network elements
The GSM network incorporates a number of network elements to support mobile
telephones and other mobile equipment (known collectively as Mobile Stations, or MSs).
These elements form the major components of the GSM network.
Network managment centre functions

The Network Management Centre (NMC) is an element defined by the GSM
recommendations for managing an entire GSM cellular network to provide operations
and maintenance at the network level..
The NMC performs the following functions:
S
Monitors trunk routes between nodes on the network.
Monitors high level alarms.
Monitors OMC-R regions and provides assistance to OMC-R staff.
Passes information from one OMC-R region to another to improve problem solving
strategies.
Enables long-term planning for the entire network.
National management
The NMC performs overall management of the PLMN, being responsible for operations
and maintenance at the network level and managing traffic on the network. It is a single
control point in systems with multiple MSCs, with the ability to co-ordinate interconnects
to networks such as alternative PSTNs.
Monitoring equipment
Both the OMC-S and OMC-R systems provide the NMC with information about the
network equipment. The NMC monitors this information for high level alarms, such as a
failed or overloaded network node, and also monitors the status of automatic controls
applied at the network equipment in response to conditions such as overload. NMC
operators monitor the network status, and in the event of a problem are able to give
guidance to staff at the appropriate OMC, according to the ability of other regions to
handle traffic flow increases.
Monitoring routes
The NMC monitors the signalling and trunk routes between nodes to prevent an overload
condition propagating through the network. Routes between the PLMN and the PSTN
are also monitored to avoid propagation of overload conditions between networks. NMC
staff are able to co-ordinate network management controls with the NMC facilities
supporting the other networks.
Managing traffic
The NMC also manages traffic on BSS network equipment. In extreme circumstances
NMC operators are able to invoke controls such as priority access, as described in GSM
recommendation 2.11. The control of traffic on the signalling and traffic routes between
the MSC and BSS can be used to isolate overloading problems within a region. The
NMC provides its operators with the ability to reconfigure cell parameters as needed and
to force handovers.
02 May 2003
68P02901W01-M
225
GSR6 (Horizon II)
Simulating the OMC-R

The NMC may be able to take regional responsibility when an OMC-R is not manned,
with the OMC-R acting as transit point between the NMC and the network equipment. In
this instance, the NMC can provide operators with functions equivalent to those available
at the OMC-R. The NMC also supports planned changes to, or expansion of the
network.
Interface
The interface between the NMC and OMC-R is defined by GSM to use Q3 protocol on a
64 kbit/s digital link.
226

68P02901W01-M
02 May 2003
Operations and maintenance centre
GSR6 (Horizon II)
Operations and maintenance centre

Introduction to the OMC
The GSM recommendations identify an element that controls and monitors the other
network elements within a region. In the Motorola GSM network, the Operations and
Maintenance Centre (OMC-R) performs this function. The OMC-R also monitors the
quality of service being provided by the network. The OMC-R is connected to the other
network elements via an X.25 packet network, and sends and receives control and
network information only, not speech or data traffic.
More detailed information on the OMC-R is given in Chapter 4 OMC-R Overview.

02 May 2003
68P02901W01-M
227
Mobile services switching centre
GSR6 (Horizon II)

Introduction to the MSC
The Mobile services Switching Centre (MSC) coordinates the setting up of calls to and
from GSM users within a defined geographical area. It is the telephone switching office
for MS originated or terminated traffic and provides the appropriate bearer services,
teleservices and supplementary services. It controls a number of Base Station Sites
(BSSs) within a specified geographical coverage area and gives the radio subsystem
access to the subscriber and equipment databases.
The MSC also provides the interface between the cellular network and the ordinary
land-based Public Switched Telephone Network (PSTN), allowing the GSM cellular
system to function as an extension of the PSTN. It also allows the GSM network to
interface to other PLMNs. There can be a number of MSCs within the region controlled
by an OMC.
The MSC controls the call set up and routeing procedures in a similar way to a land
network end office controlling land line calls. On the land network side, the MSC
performs call signalling functions using the ITU-TSS C7 communications protocol. The
forms of the protocol used are Telephone User Parts (TUPs) on the interface to the
PSTN and ISDN User Part (ISUP) on the interface to the ISDN.
MSC functions
The MSC acts as an exchange for all types of mobile calls: local, national, and
international. The following are mobile-specific call processing functions in the MSC:
228
Provision of access to the VLR and HLR.
Provision of access to the EIR.
Processing of telecommunication services and supplementary services. (For

example, Short Message Service).
Mobility management, for example:
Interrogation of MS.
Paging.
Handover.
Call re-establishment.
Location updating: interrogation and updating of VLR and HLR.
Interworking between the signalling systems of fixed networks and the signalling
system of the BSS.
Resource handling:
Queuing.
Off-air call set up.
Mobile subscriber charging.
Inter-administrative revenue accounting.
Security functions.
Simultaneous and alternate use of services.
Interworking for dual tone multifrequency signals.
User information language. (For example, recorded announcements).

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Gateway MSC
When the MSC provides the interface between the fixed and mobile networks, it is known
as the Gateway MSC (GMSC), since it gives the mobile network access to the land lines
of the PSTN, ISDN and data networks. It may also provide specific InterWorking
Functions (IWFs) to other networks.
MSC flexible design

The GSM recommendations define the functions of the MSC, but allow flexibility in its
design.
S
The most common solution is to combine the functions of the MSC, VLR, HLR,
AUC and EIR into one functional node. This has the advantage that the dynamic
load, caused for example by interworking through C7 signalling links, is kept to a
minimum.
Another approach is to separate all functional elements into separate network

nodes.
A third solution consists of combining functional elements in accordance with the

requirements of the operating company. For example, the MSC and VLR can be
combined, as can the HLR and AUC.
In practice, due to the transmission capacity of C7, the MSC should not be separated
from the VLR, nor the HLR from the AUC.
Interfaces
The MSC has interfaces to the following:
S
OMC-R.
Other MSCs within the same PLMN.
BSSs.
Location registers: HLR, VLR and EIR.
Emergency Service Centre.
Service Centre (SC) - Used for Short Message Service.
Other networks, including the PSTN/ISDN, PDN and other PLMNs.
A interface
This interface between the MSC and the BSS is defined as the A Interface. The
interface is based on the use of one or more E1/T1 digital links. The channels on these
links can be used for traffic or signalling.
The A Interface provides facilities to the traffic channels and signalling links for the
following functions:
S
Terrestrial management: allocation and blocking of the terrestrial traffic channels.
Radio channel management: BSS management radio channel

allocations/control.
Mobility management: location update transparency between the MS and MSC.
Call control: set up for mobile originating/terminating calls.
Supplementary services: transparency through the BSS.

02 May 2003
68P02901W01-M
229
GSR6 (Horizon II)
Layered signalling
The signalling is layered, similar to that in the OSI reference model. However, the layers
referred to are not identical but are specified by ITU-TSS C7.
BSSMAP and DTAP

The A Interface carries messages between the BSC and the MSC and the BTS (MS).
These two data flows are referred to respectively as BSSMAP and DTAP. In addition the
general BSC BSSMAP messages must be distinguished from the DTAP messages
specific to the mobile station connection, with the DTAP messages identified between
themselves. For the DTAP messages the virtual circuit approach is used with
independent connections established and released.
Protocols
Figure 2-4 shows how the signalling messages are transferred between the BSC (or
different mobile stations) and the MSC by using the C7 MTP-SCCP stack and protocols:
Figure 2-4 A interface protocols
DTAP
BSSMAP
DISTRIBUTION LAYER
SCCP
MTP
PHYSICAL LAYER
The SCCP defines several classes of services, of which only two are used in the GSM A
Interface: the basic connectionless mode and a connection orientated mode. These
modes are referred to as class 0 and class 2 SCCP services.
Location register interfaces

The lower level communication functions for the interfaces between the MSC, VLR, HLR,
and EIR follow ITUTSS recommendations for C7. At the application level, the
messages used on these interfaces are specified by GSM as the Mobile Application Part,
or MAP.
Message transfer link

The Message Transfer Link (MTL) is the Motorola name given to the signalling link
between the MSC and BSC.
It takes up one timeslot on the E1/T1 link.
Call control
The MSC performs call control functions such as number translations and routeing,
matrix path control, and allocation of outgoing trunks. It maintains PLMN synchronization
and provides synchronization to its BSSs. The MSC also collects traffic statistics for
performance management purposes.
Emergency calls
An international emergency number allows GSM subscribers to make emergency calls
wherever they are. The MSC receives the emergency call set up message, and routes
the call to the appropriate emergency centre.
230

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Short message service

The Service Centre (SC) sends point-to-point short messages destined for an MS to the
GMSC.
S
The GMSC checks for errors, interrogates the HLR to determine the location of the
MS and transfers the message to the appropriate MSC. (The GMSC and the MSC
may be the same equipment.) The MSC uses call set up parameters from the VLR
to establish the call, and reports the outcome back to the GMSC which in turn
reports to the MSC.
If the message is unsuccessful, the GMSC requests the HLR to store the SC
address as a Message Waiting Data for the MSISDN. The HLR determines when
the MS is next ready to receive a message, and informs the MSC that has the
interworking interface with the SC. (The interworking MSC and the MSC may be
the same equipment.) The interworking MSC in turn informs the SC so that a
further attempt to send the message can be made.
MSCs also handle short messages sent from an MS. The MSC local to the MS
checks the message for errors and transfers it to the appropriate interworking
MSC. The interworking MSC transfers the message to the destination SC,
receives the outcome and reports it back to the MSC, which reports it to the MS.
MSCs only handle point-to-point short messages. Short messages broadcast to all MSs
in a cell may be handled by the OMC-R and the BSS.
Security procedures
Other functions performed by the MSC are unique to the mobile environment. The MSC
supports the security procedures used to control access to the radio channels. These
procedures include:
S
Passing keys to the BSS which are used to validate the identity of the mobile
equipment and the subscriber.
Encrypting the data sent on the traffic channel and control channels.
Local registration and call handover

In addition to the call set up procedures, the MSC also controls location registration and
some handover procedures. Location registration (and location update) allows MSs to
report changes in their locations, enabling automatic completion of MS terminated calls.
The handover procedure preserves call connections as MSs move from one radio
coverage area to another during an established call. Handovers within cells controlled by
a single BSC are controlled by that BSC. When handovers are between cells controlled
by different BSCs, the primary control is at the MSC. Figure 2-5 shows how the two
types of handover are achieved.

02 May 2003
68P02901W01-M
231
GSR6 (Horizon II)
Figure 2-5 Handover control
BSC
MS
BTS
HANDOVER
EACH CELL CONTROLLED BY A

DIFFERENT BSC, SO MSC
CONTROLS HANDOVER
BTS
MSC
BSC CONTROLS BOTH

CELLS, SO IT CONTROLS
HANDOVER
BSC
BSC
MS
BTS
HANDOVER
BTS
Inter-MSC handovers
Handovers between MSCs can also be performed between BSSs connected to two
different MSCs. In these handovers, the MSC where the call originates functions as the
primary MSC, and retains ultimate control of the call through out its duration, even
though the call processing tasks are handed over to another MSC.
232

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Equipment identity register

The Equipment Identity Register (EIR) option, is a centralized database for validating the
International Mobile station Equipment Identity (IMEI).
The database contains three lists:
S
The white list contains the IMEIs of valid MSs.
The grey list contains IMEIs of equipment to be monitored and observed for
location and correct function.
The black list contains IMEIs of MSs which have been reported stolen or are to be
denied service.
The EIR database is remotely accessed by the MSCs in the network. The EIR can also
be accessed by an MSC in a different PLMN. A given PLMN may contain more than one
EIR, in which case each EIR controls certain blocks of IMEI numbers. The MSC
contains a translation facility, which, when given an IMEI, returns the address of the
proper EIR to access. Figure 2-6 summarises the three database lists.
Figure 2-6 Database list summary
WHITE LIST
GREY LIST
BLACK LIST
ALL VALID
ASSIGNED IDs
SERVICE ALLOWED
BUT NOTED
SERVICE
DENIED
MOBILE 5
MOBILE 1
MOBILE 2
MOBILE n
MOBILE 6
MOBILE n
MOBILE 9
MOBILE 10
MOBILE n
Home location register

Figure 2-7 shows the Home Location Register (HLR), which is a database of subscriber
information used in setting up calls. Various identification numbers and addresses are
stored as well as authentication parameters, services subscribed, special routeing
information. The current status of the subscriber is maintained.
Figure 2-7 HLR configuration
MSC
EXTERNAL
PLMN
MSISDN
MSISDN
or IMSI
IMSI
HLR
HOME LOCATION
REGISTER
BASIC SERVICE LIST
SUPPL. SERVICE LIST
CURRENT VLR
CALL FORWARD
NUMBER
etc.
MSISDN
VLR
IMSI
MSC
VLR

02 May 2003
68P02901W01-M
233
GSR6 (Horizon II)
HLR master database

The HLR contains the master database of the subscribers to a PLMN. This data is
remotely accessed by the MSCs and VLRs in the network. A PLMN may include more
than one HLR, in which case each HLR contains a portion of the total subscriber
database. The subscriber data may be accessed by either the IMSI or the mobile
subscriber ISDN number. The data can also be accessed by an MSC or a VLR in a
different PLMN to allow inter-system and inter-country roaming.
HLR data
The data stored in the HLR indicates which basic and supplementary services a given
subscriber is allowed to use. This data is changed only when new subscribers are added
or deleted, or the specific services they subscribe to are changed. The HLR data also
includes temporary information related to supplementary services such as the current call
forwarding number.
A subscribers HLR entry also includes the address of his current VLR. This information,
in connection with the VLR data explained below, allows completion of calls to the mobile
subscriber.
Authentication centre
The HLR function may also include the Authentication Centre (AUC) as shown in
Figure 2-8. The AUC generates and stores the parameters necessary to authenticate a
subscribers identity so as to guard against fraudulent system use.
Figure 2-8 Authentification centre configuration
AUTHENTICATION
CENTRE
AUTHENTICATION
KEY
REQUEST FOR
AUTHENTICATION
ONE PER
SUBSCRIBER
ALGORITHM
PROCESS
RANDOM
NUMBER
GENERATOR
SIGNED
RESPONSE
RANDOM
NUMBER
To VLR
To MS
Authentication key
To support the authentication process, each subscriber is assigned an authentication
key (Ki) which is stored only in the SIM of the MS and at the authentication centre. The
AUC generates a random number that is input to the authentication algorithm along with
the authentication key. The algorithm produces a new number called the signed
response. To authenticate a subscriber, the random number is sent to the MS. The
mobile, if it is a valid one, executes the same authentication algorithm as the AUC and
using its known Ki produces the same signed response that is sent back on the signalling
channel. Producing the same signed response from the same random number proves
the authenticity of the subscriber. This method provides increased security because no
fixed keys can be acquired by anyone monitoring the radio channel.
234

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Visitor location register

Figure 2-9 shows the Visitor Location Register (VLR), which is a local subscriber
database, holding details on those subscribers who enter the area of the network that it
covers. The details are held in the VLR until the subscriber moves into the area serviced
by another VLR. The data includes most of the information stored at the HLR, as well as
more precise location and status information. The VLR provides the system elements
local to the subscriber, with basic information on that subscriber, thus removing the need
to access the HLR every time subscriber information is required.
Figure 2-9 Visitor location register configuration
VLR
VISITOR LOCATION
REGISTER
VLR Database
IMSI
TMSI
INTERROGATION
ACCESS MODES
MSRN
COPY OF SELECTED
DATA FROM HLR
DATABASE FOR ALL
SUBSCRIBERS
CURRENTLY IN AREA
SERVICED BY THIS
VLR
MSRN
(MOBILE STATION
ROAMING
NUMBER)
GENERATOR
HANDOVER
NUMBER
GENERATOR
TMSI
(TEMPORARY MOBILE
SUBSCRIBER IDENTITY)
GENERATOR
MSRN
HANDOVER
NUMBER
NEW TMSI
Controlling LAIs
Cells in the PLMN are grouped into geographic areas and each is assigned a Location
Area Identification (LAI). Each VLR controls a certain set of LAIs. When a mobile
subscriber roams from one LAI to another, the current location is updated in his VLR
entry using the location validate procedure. If the old and new LAIs are under control of
two different VLRs, the entry on the old VLR is deleted and a new entry is created at the
new VLR by copying the basic data from the HLR entry. The subscribers current VLR
address, stored at the HLR, is also updated. This provides the information necessary to
complete calls to the mobile subscriber.
Controlling MSRNs
The VLR also controls the assignment of Mobile Station Roaming Numbers (MSRNs).
When an MS receives an incoming call, the HLR requests the correct VLR for a MSRN,
the VLR selects an MSRN from its pool of numbers and returns it to the MSC that initially
handled the call. The call is then forwarded using the MSRN as the called address. The
MSRN causes the call to be routed to the MSC which controls the base stations in the
area where the MS is currently located.
Allocating handover numbers

The VLR also allocates handover numbers for use in inter-MSC handovers. These
handovers require the call to be re-routed from the source MSC to the target MSC. The
handover number functions similarly to an MSRN, in that it allows the required trunk
connection to be set up by routeing the call through the land network.
02 May 2003
68P02901W01-M
235
GSR6 (Horizon II)
Allocating TMSI numbers

The VLR also controls allocation of new Temporary Mobile Subscriber Identity (TMSI)
numbers. A subscribers TMSI can be periodically changed to secure the subscribers
identity. The system configuration database controls when the TMSIs are changed.
Options include changing the TMSI during each location update procedure or changing it
within each call set up procedure.
The database in the VLR can be accessed by IMSI, TMSI, or MSRN. Typically, there will
be one VLR per MSC, but other configurations are possible.
236

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Call handling
The following figures illustrate the functions of the MSC in handling mobile originated or
terminated traffic.
MS to PSTN subscriber
Figure 2-10 shows a call from an MS to a subscriber in the land network (that is, the
PSTN). The MSC acts as an outgoing exchange. If the call is directed to another
country, the MSC routes it to the International Switching Centre. If the call is to a
subscriber on the national network, the call is routed to the PSTN, which sets up the
connection to the PSTN subscriber. The MSC performs the same function for a call
directed to the ISDN.
Figure 2-10 MS to PSTN subscriber call

PLMN
VLR
MSC
MS
BSS
PSTN/
ISDN

02 May 2003
68P02901W01-M
237
GSR6 (Horizon II)
PSTN subscriber to MS
Figure 2-11 shows a call from a subscriber in the land network (that is, the PSTN) to an
MS. The assumption is that the PSTN cannot interrogate the HLR, so the call has to be
directed to the Gateway MSC which performs the interrogation. The MSRN is then used
to route the call to MSC-B which pages MS-B and sets up the call to it. The connection
between the Gateway MSC and MSC-B may be routed through one or more transit
exchanges of the national ISDN/PSTN.
Figure 2-11 PSTN subscriber to MS call
PSTN/ISDN
PLMN
BSS
MSC-B
GMSC
VLR
HLR
MS-B
238

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
MS to MS calls
The scenarios covered include:
S
A call between MSs in the same PLMN.
A call between MSs in different PLMNs in the same country.
A call between MSs in different PLMNs in different countries.
MS to MS (same PLMN)
Figure 2-12 shows a call between a calling MS (MS-A) and a called MS (MS-B) in the
same PLMN. MSC-A analyses the called number for MS-B, via the VLR. It interrogates
the HLR to retrieve the MSRN which it uses to route the call to MSC-B. MSC-B acts as
an incoming exchange and establishes the call to MS-B. The connection between the
two MSCs may be routed through one or more transit exchanges of the national
ISDN/PSTN.
Figure 2-12 MS to MS call (same PLMN)
PLMN
HLR
VLR
MSRN of MS-B
RETRIEVED
MSC-A
BSS
MS-A
VLR
PSTN/ISDN
MSC-B
BSS
MS-B

02 May 2003
68P02901W01-M
239
GSR6 (Horizon II)
MS to MS (different PLMN/same country)

Figure 2-13 shows a call between a calling MS (MS-A) in one PLMN and a called MS
(MS-B) in another PLMN. MSC-A analyses the called number for MS-B. It interrogates
the HLR of the other PLMN to retrieve the MSRN which it uses to route the call to
MSC-B. MSC-B acts as an incoming exchange and establishes the call to MS-B.
Figure 2-13 MS to MS call (different PLMN)

PLMN
VLR
MSC-A
MS-A
BSS
PSTN/
ISDN
PLMN
VLR
HLR
MSC-B
MS-B
240
BSS

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
MS to MS (different PLMN/different country)

Figure 2-14 shows a call from an MS (MS-A) in one PLMN to an MS (MS-B) in a PLMN
in another country. MSC-A determines from the international prefix that the call is
directed to another country but cannot determine the location of the called MS. The call
is therefore routed to the Gateway MSC in the other country which interrogates the HLR
to discover the MSC area where MS-B is currently located. The HLR returns the MSRN
and the call is routed to MSC-B. MSC-B acts as an incoming exchange and establishes
the call to MS-B. The connection between the GMSC and whichever MSC area MS-B
roams to, may be routed through one or more exchanges of the national ISDN/PSTN.
Figure 2-14 MS to MS call (different PLMN/different country)

PLMN 1
VLR
MSC-A
BSS
MS-A
PSTN/ISDN
PSTN/ISDN
PLMN 2
MSC-B
GMSC
VLR
HLR
BSS
MS-B

02 May 2003
68P02901W01-M
241
Base station system
GSR6 (Horizon II)
Base station system

Introduction to the BSS
The Base Station System (BSS) is the fixed end of the radio interface that provides
control and radio coverage functions for one or more cells and their associated MSs. It is
the interface between the MS and the MSC. The BSS comprises one or more Base
Transceiver Stations (BTSs), each containing the radio components that communicate
with MSs in a given area, and a Base Site Controller (BSC) which supports call
processing functions and the interfaces to the MSC. Digital radio techniques are used for
the radio communications link, known as the Air Interface, between the BSS and the MS.
The BSS and the Air Interface are described in detail in the Base Station System
section of Chapter 3.
BSS configurations
Physically, a BTS may either be remote from its BSC. Where BTSs are remote from the
BSC, they may be linked in a variety of ways. Three possible configurations are shown
in Figure 2-15.
S
BSS 1 is a simple configuration, with a direct link from the BSC to a single BTS.
BSS 2 shows a spoke configuration, where each of the BTSs has its own link to
the BSC.
BSS 3 shows a closed loop configuration, with each BTS linked to the next, and a
link from the last BTS back to the BSC.
Figure 2-15 BSS configuration examples
BSS 1
BSS 2
BSS 3
BSC
BTS
MSs
LINK to MSC
LINK to MSC
LINK to MSC
BSC
BSC
BTS
MSs
BTS
MSs
BTS
MSs
BTS
MSs
The configuration used at any particular site depends on a number of factors, and a
mixture of configurations can be used within a single BSS. BTS configurations are
described in greater detail in the appropriate Service Manual.
242

68P02901W01-M
02 May 2003
Base station system
GSR6 (Horizon II)
Software functions
Table 2-6 summarizes the software functions of the BSS.
Table 2-6 BSS software function
Executive/Operating
System
Operations &
Maintenance
Radio Subsystem
TTY DLSP
Fault Translation
Process
LAYER 2 INTERFACE
Mobile Signalling
Translation, LAPDm
protocol, and Short
Message Service
functions
CM
Connectionless
Manager
TDM DLSP
CM
Abis INTERFACE
Interface between
BSC and BTS
SCCP STATE
MACHINE
Signalling Connection
Control Part
Handover and
Power Control
RRSM
Radio Resource
State Machine
Terminal Data Link

Service Process
Time Division Multiplex

Configuration
Data Link Service Process Manager
EXEC DLSP
MMI
Man-Machine
Executive/Process
Data Link Service Process Interface
Initialization Process
Call Processing
SM
Switch Manager
Process Control
Motorola BSS
In Motorola systems, the BSS equipment can be used both as a concentrator hub, as a
single site. The Motorola add and delete option allows BTSs to be strung one to another
in an open or closed loop topology. This enhancement provides reduced line charges in
low density coverage regions such as sparse rural areas or along roads.
The BSC controls the selection of signalling channels and speech channels and
manages the radio channels. It transfers signalling information to and from MSs via the
BTS.
Connection of MSC
The relationship between the radio channels at the BSS and the terrestrial circuits which
connect the BSS to the MSC is not fixed: a radio channel and terrestrial circuit must be
selected and assigned every time a call is set up. The BSC selects the radio channel,
while the MSC selects the terrestrial circuit. The BSC then uses a digital switching
matrix to connect the two together. The switching matrix also allows the BSS to perform
inter-BSS handovers without involving the MSC.
Speech transcoding
Speech transmitted on the GSM radio channel needs to be transcoded to reduce the
bandwidth requirement on the Air Interface. This is done by the speech transcoder
(XCDR). Transcoding may be performed at the BSC, or remotely at or near the MSC.
When transcoding is performed remotely, it can be combined with 4:1 multiplexing in
which the data for four logical channels is combined onto one 64 kbit/s link, thus reducing
the number of links required for interconnection to the BSCs.
02 May 2003
68P02901W01-M
243
Base station system
GSR6 (Horizon II)
BSS application part

At the application levels of the C7 communications protocol, GSM defines a special set of
messages, unique to the mobile application, called the BSS Application Part (BSSAP).
The BSSAP comprises:
S
The BSS Mobile Application Part (BSSMAP) which is used on the BSS-MSC link.
The Direct Transfer Application Part (DTAP) which is used over the radio interface
to the MS.
BSS interfaces
A interface
The interface between the MSC and the BSS is a standardized C7 interface (A Interface)
and is fully defined in the GSM recommendations. It enables the system operator to
purchase switching equipment (such as an MSC) from one supplier, and radio equipment
(such as a BSS) from another supplier, and still retain equipment compatibility.
Abis interface
The interface between the BSC and a remote BTS is also a standard interface (the Abis
Interface). However, Motorola offers a unique Motorola Abis Interface, called Mobis,
which reduces the amount of message traffic and thus the number of E1/T1 links
required between BSC and BTS.
Air interface
The radio communications link between the BSS and the MS is known as the Air
Interface.
The GSM Air Interface is a noise-robust transmission medium. The speed of a radio
channel used in GSM is 270.833 kbit/s. The modulation is 0.3 BT Gaussian Minimum
Shift Keying (GMSK).
Physical channels
The Air Interface is capable of handling simultaneous calls: any call sent on an RF carrier
can share that carrier with up to seven other calls. GSM systems achieve this by virtue
of the high speed of digital radio communication, which allows each call to take its turn on
the carrier with no loss of transmission quality.
Logical channels
The different types of information sent over GSM physical channels are called logical
channels. The term channel is therefore used differently when applied to logical
channels: the physical channel is a pathway for the information; the logical channel is the
type of information sent.
Logical channel types

There are two types of logical channel on the Air Interface: control (or signalling)
channels and traffic channels.
244

68P02901W01-M
02 May 2003
Base station system
GSR6 (Horizon II)
Control channels
The control channels are used to carry signalling information between the MS and BSS.
The four control channel groups are:
Broadcast control channels

S
Broadcast Control CHannel (BCCH). Contains information about the cell.
Frequency Correction CHannel (FCCH). Used by the MS to correct the frequency

of its internal time base.
Synchronization CHannel (SCH). Used by the MS to synchronize to the TDMA

frame structure in the cell.
Common control channels

S
Random Access CHannel (RACH). Transmitted by the MS to gain access to the

system.
Paging CHannel (PCH). Transmitted by the BTS to contact a specific MS.
Access Grant CHannel (AGCH). Transmitted by the BTS to grant or refuse a

specific MS access to the system.
Cell Broadcast CHannel (CBCH). Used to broadcast messages to all MSs in a

specific cell.
Dedicated control channels

Stand-alone Dedicated Control CHannel (SDCCH). Used during call set-up or to transmit
short messages.
Associated control channels

S
Slow Associated Control CHannel (SACCH). Used by the BSS to transmit power
and timing information to the MS and to receive measurement reports from the
MS.
Fast Associated Control CHannel (FACCH). Used to transmit signalling

information between the MS and BSS. The FACCH is used when information
must be passed quickly, for example, during a handover.
Traffic channels
These channels are used to carry speech or data information between the MS and BSS,
and include:
S
Speech channels. These channels carry speech information over the Air Interface.
There are two types of speech channels:
Full rate.
Half rate.
Data channels. These channels carry data information over the Air Interface.
There are three types of data channels, each named according to the data rate it
supports:
9.6 kbit/s.
4.8 kbit/s.
2.4 kbit/s.
02 May 2003
68P02901W01-M
245
GSR6 (Horizon II)

Introduction to GSM non- network element subsystems
The GSM network also includes the following additional subsystems, which are not
formally recognised as network elements.
Interworking function
The the Interworking Function (IWF) performs the data rate adaptation between the
PLMN and networks such as the PSTN, the Integrated Services Digital Network (ISDN),
and packet networks. Other functions of the IWF include provisions for mobile
subscribers to communicate with a PSTN-based modem, or to connect directly to
customer provided equipment, such as X.25 Packet Assembly/Disassembly facilities
(PADs).
Echo canceller
The Echo Canceller (EC) eliminates echo from voice circuits. The voice signal from the
PLMN has to be transformed from the 4-wire PLMN circuit to the 2-wire circuit on the
land network. If it were not cancelled, the total round-trip delay introduced by the GSM
system (typically 180 ms) would become audible to the PLMN subscriber as an echo.
Billing centre
The billing centre is a system provided by the PLMN administration which collects the
billing data from the GSM network elements and applies the billing data to subscribers
accounts. The details of the billing centres operation are not addressed by GSM, and the
billing centre is not considered to be a network element of the PLMN.
There are two types of billing data:
S
Call records
Call records are produced by the MSC, which may provide facilities for storing the
completed call records, as well as forwarding them to the billing centre. The
records are stored in a disk file as they are being generated. In this case, the file
has a fixed size and when the file becomes full, it is automatically closed and a
new one opened. The completed file is then automatically transferred to the billing
centre using X.25 communication links and the File Transfer, Access, and
Management (FTAM) file transfer protocol. A backup copy of the completed billing
files can be manually copied to magnetic tape. These same storage and
communication facilities can also be provided at HLRs and VLRs for the handling
of event records.
Event records
These are produced by the HLRs and VLRs. An event records the location
updates for the MS and the forwarding of MS terminated calls.
Cell broadcast centre

The Cell Broadcast Centre (CBC) is the call processing centre for Cell Broadcast Short
Message Service (CBSMS) messages, which are unacknowledged short messages (128
bytes maximum) that are broadcast to all MSs in a particular cell.
246

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

Introduction to GSM system features and goals
The following describes GSM features and the technology requirements for GSM in more
detail, and summarizes the goals of the GSM specifications.
Technological requirements
Motorola participated in the GSM validation exercise by providing an extensive validation
system, and in the process identified further technological requirements for GSM
systems, including:
S
A fast, highly reliable Automatic Gain Control (AGC) to facilitate capture of the
short random access burst.
Selection of proper filters to minimize spurious emissions without corrupting the

desired signal.
Stable quasi-linear RF PA to provide the rapid ramping needed to achieve GSM

specified time and spectral masks.
Adequate power supply decoupling and regulation to reduce transmitter pulsing

transients.
Proper distribution of gain and AGC receiver stages to achieve the necessary
100 dB of dynamic range.
Self calibrating techniques for generating and demodulating Gaussian Minimum

Shift Keying (GMSK) that do not require tuning and are immune to drift or ageing.
Adequate diagnostic capability, fault analysis tools, test equipment, and key
servicing test points.
Synthesizer technology that meets the very high switching speeds required for
frequency hopping.
GSM goals
The GSM digital cellular system is the culmination of years of concerted effort by
government, industry, and academic institutions to provide a fully digital, cellular
radio-telephone system.
The GSM digital cellular system provides:
S
European standardization.
Good audio quality and link Integrity.
Features supplying:
Subscriber services.
System-related features.
Increased capacity.
Lower cost infrastructure.
Hand portable viability.
European standardization
Before the introduction of GSM, most of the cellular networks used in Europe were
incompatible with one another. GSM aimed to provide a common European system, so
that a subscriber could be provided with uninterrupted service, regardless of the country
in which he or she was currently located. To achieve this, the (cellular network)
technology needed to be compatible, even to the extent of using common frequency
bands. This technology is now being employed world-wide.
02 May 2003
68P02901W01-M
247
GSR6 (Horizon II)
Standardized electrical interfaces

GSM defines standardized electrical interfaces and communications protocols for both
the fixed and subscriber equipment. This guarantees compatibility and interworking
between systems designed by different manufacturers and also allows the user to
choose equipment at the subsystem level, as well as the overall system level.
GSM interfaces
The following GSM interfaces are standardized and specified:
S
MSC PSTN/ISDN (of National concern).
MSC MSC (of National concern).
MSC BSC (of National concern).
BSC BTS (not used by Motorola).
BTS MS.
MSC All LRs.
LR LR.
Subscriber ISDN Interfaces.
ISDN compatibility
GSM is compatible with the Integrated Services Digital Network (ISDN) which will carry
both voice and data on standard telephone lines. This is the telecommunications
network that many countries are committed to implement.
Signalling system 7
As an extension of the land line telephone network, GSM clearly relies heavily on
signalling system 7 (C7) to provide the bearer level communications protocol.
Hierarchical network architecture

The use of a hierarchical network architecture is another feature that can be exploited by
system designers and individual equipment providers to reduce the operating cost,
particularly in line charges. A hierarchical network architecture employs intermediate
BSC controllers between the MSC and the radio channel equipment.
248

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Subscriber services
GSM systems can offer an enhanced range of services, such as teleservices, data and
speech services. These services can be augmented with a variety of supplementary
subscriber services
The following are examples of some of the supplementary subscriber services:
S
Number identification services.
Call forwarding services.
Charging services.
Call barring services.
Emergency services.
Mobile access hunting.
Call forwarding.
Call queuing.
Conference calls.
An international emergency call number.
Point-to-point and broadcast Short Message Services.
Separate personal and business numbers for a single subscriber.
Videotex, teletex and fax.
Security
GSM security features include the authentication of the mobile equipment and the
subscriber. Control information is encrypted, and speech is digitally encoded. These
features provide confidentiality and prevent stolen equipment from being used.
Handovers
GSM handovers are more tightly controlled than analogue handovers. MSs have built-in
intelligence to assist in the handovers, which ensures that the network is relieved of
unnecessary measurement reporting and associated overheads.
During the handover procedures, extensive measurements are made both by the MS and
the BSS of such parameters as uplink (MS-to-BSS) and downlink (BSS-to-MS) signal
levels, downlink signal levels of adjacent cells, BSS-to-MS distance, and so on. Many of
these measurements are cross-checked to ensure trustworthiness. For example, not
only is the received level of adjacent cells measured, but the associated control channel
ID is also received, decoded, and reported together with the quality of reception (bit error
rate). Both the BTS and the MS measure signal quality as well as the signal strength.
The MS also monitors signal strengths in up to 32 adjacent cells.
Link integrity
GSM incorporates several features to achieve a high-integrity communication link and to
ensure high quality signalling performance. Call re-establishment procedures allow lost
subscribers to reconnect to an interrupted connection. These procedures reduce the
number of dropped or lost calls.
A unique feature of digital communication is the use of the error control coding to
estimate the bit error rate of the channel being used. In this way the system evaluates
link quality and can take action on co-channel and adjacent channel interference, even
when signal levels are relatively high. A subscriber is handed over to a different cell or
channel if detrimental interference is sensed.
02 May 2003
68P02901W01-M
249
GSR6 (Horizon II)
Tracking
GSM systems keep track of the MS better than analogue systems because GSM uses
location updating. When the MS moves to a new location area, the VLR is updated. The
system also knows whether or not an MS is switched off, so does not waste resources
trying to page it unnecessarily.
Power saving
GSM uses methods that save on power usage and extend battery life in the MS:
S
MS and base station power control.
DTx (Discontinuous Transmission).
DRx (Discontinuous Reception).
Increased capacity
GSM systems have more capacity than analogue systems. Eight simultaneous calls can
be active on one RF carrier (as opposed to one call per carrier in analogue). Less RF
hardware is therefore required to expand a GSM system. GSM uses a radio channel
structure (TDMA) that will lead to an increased capacity of 16 simultaneous calls per
carrier if half rate is used.
Use of low bit rates for non-voice data

For data communications, GSM offers a better match than analogue, of provided radio
spectrum to data rate. GSM provides specialized data and message services, such as a
point-to-point Short Message Service (for messages such as those sent to a pager built
into the MS). The call lengths of these data services average much less than the
corresponding speech calls.
Lower cost infrastructure

GSM design is intended to minimize the cost of the service provided. For example, the
signalling rate and Time Division Multiplexing Access (TDMA) structure of 8 was selected
as a compromise between equipment complexity, system issues, and performance. The
use of a single radio carrier for multiple traffic channels reduces the cost per channel.
Half rate speech coding will provide further cost reduction.
Site size definitions

The GSM digital cellular system uses a 9-site pattern or a 3-site (3-sectored), 120 degree
sector arrangement, which provides about a 12 dB Carrier to Interference Ratio (C/I) for
90% location reliability.
In addition, a unique Motorola design proposes a 2-site (6-sectored) repeat pattern using
60 degree sectors. The capacity of this pattern is 40% greater than the 3-site repeat
generic pattern and provides nearly equivalent C/I performance. This capacity
improvement is further influenced by a trunking efficiency factor due to the fact that the
reduced cell reuse patterns allow a smaller number of frequency groups. The improved
C/I, in conjunction with the more accurate and sophisticated handover technique, allows
microcells to be used.
250

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Timing adjustment
The further the MS is from the base station, the longer it takes for the bursts of
transmission to travel the distance between them. The short duration of the TDMA burst
demands a high degree of accuracy, so the problem of a varying time lag has to be
overcome by timing corrections performed by the MS. The distance between the MS
and the base station is measured and used by the base station to calculate a timing
advance which the MS is instructed to use for all uplink transmissions. This timing
advance information is sent to the MS twice a second using the SACCH. The advance is
superimposed on the 3-timeslot offset of the frame structure which the MS uses when
transmitting.
Echo cancellers
Another problem is that of echo, which is made noticeable by hybrid transformers
converting the signal from 4-wire circuits in the PLMN to the traditional 2-wire circuits in
the land telephone network. High-performance echo cancellers are therefore provided
for every speech conversation in the interface between the MSC and the PSTN.
Synchronization
Synchronization is a key feature for GSM. All frequencies and times are locked to a high
stability (0.05 ppm) reference which can be referenced to a system-wide standard. MSs
lock to a reference transmitted from the base station.
Synchronizing clocks over a wide geographic area gives a GSM system advantages,
such as rapid, reduced interruption, handovers, as specified in the GSM
recommendations.
Synchronization also allows the effective number of channels available for frequency
hopping to be increased and the capacity of a limited number of radio channels to be
distributed more evenly. Both these enhancements are useful where a limited spectrum
is available for implementing the GSM system.
Noise robustness
The GSM radio interface is noise robust because:
S
All the information to be transmitted is digitally encoded. Under the encoding

scheme, the information is spread out by being interleaved, and the decoding
methods allow error detection and correction.
Each burst carrying encoded information includes a training sequence. An

equalizer in the receiver uses this to synchronize to the burst and then measures
signal distortion and calculates from that the most probable transmitted sequence
of bits.
Frequency hopping, as well as providing security, makes GSM systems more

resistant to the effects of multipath fading.
The use of two antennas at the BTS, placed several wavelengths apart, creates
diversity of radio paths from the MS, leading to improved reception.

02 May 2003
68P02901W01-M
251
GSR6 (Horizon II)
BSS Location Services support

The Location Services (LCS) feature implements emergency services functionality in
GSM systems (compliant with the Federal Communications Commission (FCC) 911
requirements) in two phases:
S
Phase 1
To transmit the originating number of an emergency call (911 in the United States)
and the location of the serving site to the Public Safety Answering Point (PSAP).
Phase 2
To transmit the emergency callers estimated position, expressed in latitude and
longitude coordinates within specified limits of accuracy.
Applications that request location estimates from location services can be located in the
MS, the network, or externally to the PLMN.
LCS positioning mechanisms

Locations services currently specify three positioning mechanisms in order to determine
the location of a Mobile Station. These positioning processes involve two main steps:
signal measurement and position computation based on the measured signals. The
standard SMG (Special Mobile Group) positioning mechanisms are:
S
Network-based uplink Time of Arrival (TOA) - not implemented by Motorola
Enhanced Observed Time Difference (E-OTD) - not implemented in this release,
Assisted GPS (A-GPS) - not implemented in this release.
Conventional GSM Timing Advance (TA) measurements can also be used in conjunction
with Cell ID determination to provide a coarser, lower quality location estimate.
Examples of applications to which LCS MS position determination can be applied are to
deliver tailored content to MSs in a physical locality (location specific advertising), or to
determine the routing of voice traffic (location sensitive routing). Motorola supports
Timing Advance (TA), Enhanced Observed Time Difference (E-OTD) and Assisted GPS
(A-GPS) positioning mechanisms.
Time of arrival positioning procedure

The BSS does not handle the Time of Arrival (TOA) positioning procedure, and therefore
must reject requests for this positioning method.
If the BSS receives a BSSLAP TOA Request from the BSS-based SMLC, the BSS
sends a BSSLAP Reject message to the BSS-based SMLC with cause value set to
positioning procedure not supported.
If the BSS receives a BSSLAP TOA Request from the MSC, the BSS sends a BSSLAP
eject message to the MSC with cause value set to positioning procedure not
supported.
Motorola does not support the TOA method.
NOTE
Timing Advance positioning (TA)

The Timing Advance positioning mechanism is based on the existing GSM timing
advance measurements, the frequency of sending of which is specified by the
timing_advance_period parameter. The timing advance value is known for the serving
BTS and when returned to the requesting LCS client, with the cell ID, provides the
approximate physical position of the MS.
252

68P02901W01-M
02 May 2003
E1/T1 links
GSR6 (Horizon II)
E1/T1 links
Link types
GSM uses two types of operating links, E1 and T1, to provide the physical links on the
network. Communication between the PSTN, MSC and BSS equipment is over E1/T1
links. X.25 and C7 information are sent using the physical protocols on these links.
NOTE
Throughout this manual, reference is made to E1/T1 links. Read

the information in the context of the type of link used.
E1 link
The E1 link has a signalling rate of 2.048 Mbit/s and provides thirty-two 64 kbit/s
timeslots, of which 30 are generally available:
S
Timeslot 0 is always reserved for synchronization purposes.
Although the remaining 31 are available for PCM or data channels, one is normally
reserved for control.
NOTE
The E1 link is sometimes referred to as a 2 Mbit/s link or bearer.
T1 link
The T1 link has a signalling rate of 1.544 Mbit/s and provides twenty four 64 kbit/s
timeslots, all of which are available for PCM or data channels:
S
Synchronization uses an additional bit, therefore one frame of data comprises 193
bits (24 timeslots of 8 bits, plus 1 synchronization bit).
Control information is either multiplexed with the PCM (bit stealing) or performed
via a 64 kbit/s timeslot.
NOTE
The T1 link is sometimes referred to as a 1.5 Mbit/s link or

bearer.
BSC daisy chain

When using the High bit-rate Digital Subscriber Line (HDSL) feature, a modem converts
E1 lines for less expensive transmission lines. The modem is daisy chain connected at
the BSC or at a point where the HDSL link is required to change to an E1 connection.

02 May 2003
68P02901W01-M
253
GSR6 (Horizon II)
Interface types
A major portion of GSM recommendations deals with standards for interfaces between
network elements. Communication between the PSTN, MSC, and BSS equipment is
over the E1/T1 physical links.
These links support the following major interfaces defined by GSM:
S
Air Interface:
MS-to-BTS (also referred to as the UM Interface).
Abis Interface: Remote BTS-to-BSC.
A Interface:
BSC-to-MSC.
B Interface:
MSC-to-VLR.
C Interface:
MSC-to-HLR/AUC.
E Interface:
MSC-to-MSC.
F Interface:
MSC-to-EIR.
G Interface:
VLR-to-VLR.
H Interface:
HLR-to-AUC.
Lb Interface:
BSS-to-BSS-based SMLC.
The use of these standardized interfaces throughout the mobile network allows
compatibility between network elements from different manufacturers.
For example, ITU-TSS Signalling System 7 (C7) is extensively used as the
communications protocol from the BSS through the MSC to the PSTN.
NOTE
ITU-TSS was previously known as CCITT. Signalling System 7

(C7) is sometimes referred to as SS7 or SS#7.
In general, the open systems interface recommendations of the International Standards

Organization (ISO) have been followed for the protocol layers of the Open Systems
Interconnection (OSI) seven layer model. The system can be changed from the ISO
standard C7 to the ANSI standard SS#7 for PCS1900.
254

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
GSM functional layering

The layering of GSM functions is partially based on the seven layer model for open
systems interconnection suggested by the ISO. Each layer performs a specific set of
functions that are isolated and enhances those performed by the lower layers. This
philosophy facilitates a modular approach to implementation. The functions occurring at
one layer have only limited interaction with those at another. This provides a degree of
flexibility for future improvements without redesigning the entire system.
Layer 1 Physical
Layer 1 comprises the physical channel layer and is concerned with transmitting and
receiving coded information symbols over the radio link. Layer 1 features include the
TDMA frame structure and frequency hopping.
Layer 2 Transport
Layer 2 features include the multiplexing and demultiplexing of logical channels.
Layer 3 Management
Layer 3 provides for the three major management functions:
S
Radio resource management (paging, cipher mode set, frequency redefinition,

assignments, handover, measurement reports, and so on).
Mobility management (authorization, location updating, IMSI attach/detach,

periodic registration, ID confidentiality and so on).
Call management (control, supplementary services, Dual Tone MultiFrequency

(DTMF), Short Message Service and so on).
Figure 2-16 shows the GSM functional layering.
Figure 2-16 GSM functional layering

Management Layer
Radio Resource
Management
Layer 3
For example:
Paging
Cipher mode set
Frequency redefinition
Assignments
Handover
Measurements
Reports
Mobility
Management
Call
Management
For example:
Authentication
Location updating
IMSI attach
IMSI detach
Periodic registration
ID confidentiality
For example:
Control
Supplementary services
DTMF
Short Message Service
Transport Layer
Layer 2
Multiplexes and demultiplexes logical channels:

Traffic
Control
Layer 1
Signalling
Synchronization
Physical Channel Layer

Transmits and receives coded information symbols over the radio link

02 May 2003
68P02901W01-M
255
GSR6 (Horizon II)
BSSAP messaging
The Ainterface and Lb-interface carry C7 BSSAP messaging. The four types of BSSAP
messaging on these interfaces are:
S
BSSMAP(-LE) on the BSS-based SMLC-BSS link (Lb Interface, a two-way

SMLCBSS protocol).
BSSMAP on the MSC-BSS link (A-interface, a two-way MSC-BSS protocol).
DTAP(-LE) on the BSS-based SMLC-LMU link (a two-way SMLC-LMU protocol).

The BSS transparently forwards DTAP-LE messages which the BSS-based SMLC
and LMU use to communicate with each other. There is, however, no direct link
between BSS-based SMLC and LMU.
DTAP on the BSS-MS link (Air Interface, a two-way MSC-MS protocol). The BSS
transparently forwards DTAP messages which the MSC and MS use to
communicate with each other. There is, however, no direct link between MSC and
MS.
ISDN messaging
Integrated Services Digital Network (ISDN) messaging is provided from the mobile
subscribers and extends throughout the terrestrial network, including other PLMNs.
MSC to MS
The MSC-MS interface is specified by BSS Application Part (BSSAP) of C7. The two
types of BSSAP messaging on these interfaces are:
S
BSSMAP on the MSC-BSS link (A Interface).
DTAP on the BSS-MS link (Air Interface).
Location register interfaces

For the interfaces between the MSC, VLR, HLR, and EIR, the lower level communication
functions also follow ITU-TSS recommendations for C7. At the application level, the
messages used on these interfaces are specified by GSM as the Mobile Application Part,
or MAP.
OMC interfaces
For the interfaces between the OMC and the other network elements, X.25 and OSI
upper layer protocols are used as specified by ISO open standards.
NMC interface
The interface between the NMC and OMC is defined by GSM to use a Q3 protocol on a
64 kbit/s digital link.
256

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Interface summary
Figure 2-17 summarizes the GSM Interfaces:
Figure 2-17 GSM interface summary

Interface
Name
GSM
interfaces
Interfacing network elements
Main messaging protocols used
Air Interface
BTS to MS
DTAP/LAPDm
Abis Interface
BSC to remote BTS
DTAP/LAPD
A Interface
BSC to MSC
BSSMAP/SCCP on C7, X25
B Interface
MSC to VLR
MAP/TCAP/SCCP on C7
C Interface
MSC to HLR/AUC
MAP/TCAP/SCCP on C7
D Interface
VLR to HLR
MAP/TCAP/SCCP on C7
E Interface
MSC to MSC
MAP/TCAP/SCCP on C7
F Interface
MSC to EIR
MAP/TCAP/SCCP on C7
G Interface
VLR to VLR
MAP on C7
H Interface
HLR to AUC
No specified protocol
Lb Interface
BSS to BSS-based SMLC
BSSLAP/BSSMAP/SCCP on C7
MSC to PSTN
TUP on C7
MSC to ISDN
ISUP on C7
OMC to all network elements
OMAP on X25
External
interfaces
Signalling links
The signalling links between the various network elements are listed in Table 2-7:
Table 2-7 Network element signalling links
Element
Link
Remote BTS-to-BSC
Radio Signalling Link (RSL)
BSC-to-BSS based SMLC
Location Services Message Transfer Link

(MTL)
OMC(R)-to-BSS
Operations and Maintenance Link (OML)
Remote XCDR-to-BSC
XCDR signalling Link (XBL)
CBC-to -BSC
Cell Broadcast Link (CBL)

02 May 2003
68P02901W01-M
257
GSR6 (Horizon II)
A interface
The interface between the MSC and the BSS is a standard interface, called the A
Interface. The A Interface is fully defined in the GSM recommendations.
The signalling portion of the interface between the MSC and the BSC uses the C7
protocol, for which application parts are defined, for example the Base Station System
Application Part (BSSAP).
The A Interface allows customers to purchase the switching equipment (for example the
MSC) from one supplier, and the radio equipment (such as the BSS) from another
supplier, and still have equipment compatibility.
For support of location services there are modifications to the A-interface: changes to
various protocols to support SMLC-BSS signalling through the MSC when the SMLC is
NSS-based.
The new messages for the Motorola implementation of location services for the BSSMAP
protocol are:
S
BSSMAP Connection Oriented Information
BSSMAP Connectionless Information
A new protocol, BSSLAP, has also been added. This protocol is used for SMLC-BSS
communication as well as a carrier for SMLC-MS messages. The BSSLAP messages
which are supported are:
S
BSSLAP TA Request
BSSLAP TA Response
BSSLAP MS Position Command
BSSLAP MS Position Response
BSSLAP Abort
BSSLAP Reset
BSSLAP Reject
Abis interface
The GSM defined interface between the BSC and the remotely located BTS equipment is
called the Abis interface. It uses Link Access Procedure D (LAPD).
At the application levels, GSM defines a special set of messages unique to the mobile
application.
258

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Mobis
The Motorola defined BSC-to-BTS interface is a modification of the Abis standard called
Mobis. It distributes functionality between the BSC and the remote BTS equipment, and
offers several advantages:
S
Reduced signalling link traffic, which permits efficient use of E1/T1 links. The BTS
performs handover data processing. This reduces the amount of data sent to the
BSC over the signalling link. This significantly reduces the amount of processing
required in the BSC.
Better synchronization of the BSC and BTS. This ensures better handover from
one traffic channel to another.
Improved overload control and fault recovery algorithms.
Efficient use of the paging and access grant channels.
Control of more than one BTS (sectors) on a single control link.
For support of location services, the Mobis interface is modified to support new BSC-BTS
signalling for location services. The following messages are new for this interface:
S
ta request
ta response
application information
Air interface
The GSM recommendations include detailed specifications for the radio channel (Air
Interface) between the MS and the BTS. The Air Interface uses a three layer protocol.
Layer 1 (physical channel)

Layer 1 is the physical channel layer. This layer transmits and receives coded
information symbols over the radio link. Layer 1 provides the basic time division
multiplexing (TDM) frame structure including timeslot, frame, multiframe, and so on.
Layer 1 also provides for multiplexing and demultiplexing (channel encoding/decoding) of
the different types of logical channels that the network requires, such as traffic channels,
signalling or control channels and synchronization channels.
Layer 2 (logical channel)

Layer 2 is a transport mechanism between layer 3 and layer 1. Layer 2 provides for error
free transport of layer 3 signalling.
Layer 3 (network control)

Layer 3 provides three major network management functions:
S
Radio resource management (paging, cipher mode setting, frequency redefinition,

channel assignments, handover, measurement reports).
Mobility management (authentication, location updating, International Mobile

Subscriber Identity (IMSI) attach/detach, periodic registration, ID confidentiality).
Call management (call set up, supplementary services, dual tone multifrequency
(DTMF), short message service).
Support for location services

A new message has been added to the RR protocol for transport of SMLC-MS
messages. The new message is:
S
RR Application Information
Also, LMUs are a new device for Location Services that use the Air Interface. However,
these LMUs act similarly to regular mobiles as far as the Air Interface is concerned.
However, LMUs are restricted in the messages they can send or accept.
02 May 2003
68P02901W01-M
259
GSR6 (Horizon II)
Lb interface
The Lb-interface is a new interface for support of location services. It is located between
the BSS and a BSS-based SMLC. The interface uses an C7 protocol, and is modelled
(from the BSS viewpoint) from the A-Interface. The interface is not present when the
SMLC is NSS-based.
At the physical level, the interface supports one or multiple 64kbit/s signalling timeslots
on E1 signalling link. By convention, these timeslots are typically placed only on timeslot
16 of a given E1 signalling link. The Lb-interface, like the A-interface, may consist of one
or multiple E1s between the BSS and the BSS-based SMLC. However, unlike the
A-Interface, no traffic carriers (CICs) are present on the E1 links (this could change in the
future if LMUs on a TCH were to be supported).
The Lb-interface fully supports all procedures in the MTPL2, MTPL3, and SCCP
protocols.
BSSMAP messages supported

For BSSMAP, the following messages are supported:
S
BSSMAP Clear Command
BSSMAP Clear Complete
BSSMAP Clear Request
BSSMAP Complete Layer 3 Information
BSSMAP Paging
BSSMAP Confusion
BSSMAP Classmark Update
BSSMAP Handover Required
BSSMAP Handover Required Reject
BSSMAP Handover Performed
BSS map enhancement

An enhancement to BSSMAP has been created for the Lb-interface called BSSMAP-LE.
The messages used for the BSSMAP-LE protocol are:
S
BSSMAP-LE Perform Location Request
BSSMAP-LE Perform Location Response
BSSMAP-LE Perform Location Abort
BSSMAP-LE Connection Oriented Information
BSSMAP-LE Connectionless Information
BSSMAP-LE Reset
BSSMAP-LE Reset Acknowledge
DTAP messages supported

For DTAP, the following messages are supported:
260
RR Paging Response
All MM messages
68P02901W01-M
02 May 2003
GSR6 (Horizon II)
DTAP enhancements
An enhancement to DTAP has been created for the Lb-interface called DTAP-LE. This is
used for SMLC-LMU communication. The messages used for DTAP-LE are:
S
DTAP-LE Register
DTAP-LE Facility
DTAP-LE Release Complete
BSSLAP protocol
A new protocol, BSSLAP, has been created for direct SMLC-BSS communication, as well
as a carrier for SMLC-MS messages. The messages used for BSSLAP are:
S
BSSLAP TA Request
BSSLAP TA Response
BSSLAP MS Position Command
BSSLAP MS Position Response
BSSLAP Abort
BSSLAP Reset
BSSLAP Reject

02 May 2003
68P02901W01-M
261
Network protocols
GSR6 (Horizon II)
Network protocols
Protocol types
The network protocols define the format of communication between two network entities.
The network protocols are:
S
E1/T1 PCM.
X.25.
ITU-TSS Signalling System 7 (C7).

ITU-TSS was previously known as CCITT. Signalling System 7
(C7) is sometimes referred to as SS7.
NOTE
Link Access Procedure D (LAPD).
Link Access Procedure Dm (LAPDm).
X.25 and C7 information are sent using the physical protocols on the E1/T1 links.
OSI/protocol relationship
Figure 2-18 shows the relationship between the OSI layers and the main protocols.
Figure 2-19 shows the overall network protocols.The individual C7 protocols are shown,
but not the interfaces on which these protocols are used.
Figure 2-18 OSI layers main protocol relationships

OSI Layers
Application
Presentation
Session
Transport
Network
Link
Physical
262
C7 Levels
C7
X25
MAP
4
TUP
BSSAP
(DTAP+BSSAP)
ISUP
TCAP
Others
X25
Applications
SCCP
3
MTP Level 3
MTP Level 2
MTP Level 1
2
1

68P02901W01-M
X25
Abis
LAPD
G.732
02 May 2003
Network protocols
GSR6 (Horizon II)
Figure 2-19 Network protocols
CBE
NMC
PSTN
OMC-R
OMC-S
C7
CBC
X.25
LAPB
X.25
RXCDR
EC
EIR
LAPD
C7
BSC
MSC
LAPD
IWF
HLR
VLR
BTS
BTS
AUC
LAPD
Base Station System

LAPDm
Mobile Station (MS)

ME
SIM

02 May 2003
68P02901W01-M
263
Network protocols
GSR6 (Horizon II)
ITU-TSS signalling system 7

The ITU-TSS signalling system 7 (C7) protocol is composed of several parts: the
Message Transfer Part (MTP), the Signalling Connection Control Part (SCCP), the X.25
link, the LAPDm protocol, and various signalling link protocols.
Message Transfer Part (MTP)

MTP is part of the C7 protocol that is used throughout the network. MTP provides layers
1, 2 and 3 of the seven layer model. MTP is the transport system for reliable transfer of
messages between users.
The three functions involved in MTP are:
S
MTP1 Signalling data link functions.

Physical, electrical and mechanical specifications for the interface.
MTP2 Signalling link functions.

Defines the functions and procedures for controlling the transfer of signalling
messages over a signalling link.
MTP3 Signalling network functions.

Defines the methods for message handling and routing on a signalling link.
MTP uses three types of Signalling Units (SU) to transmit information:

S
MSU Message Signalling Unit.
LSSU Link Status Signalling Unit.
FISU Fill-In Signalling Unit.
Signalling Connection Control Part (SCCP)

The SCCP is a layer 3 protocol and provides network connectivity as required.
The SCCP forms part of the Signalling Information Field (SIF) in the MTP signalling unit.
The SCCP can operate in four modes. Two of these modes are used for GSM. Protocol
class numbers carried in the mandatory fixed field of the SCCP message indicate which
mode is being used. The two modes used for GSM are:
S
Connectionless. Protocol Class 0 Single messages are sent to other SCCP

users. The Unit Data (UDT) is the only type of message sent in connectionless
mode.
Connection-oriented. Protocol Class 2 A signalling connection is established

before messages are sent. The following SCCP message types must be passed
to establish this connection:
CR Connection Request.
CC Connection Confirm.
CREF Connection Refused.
DT1 Data form 1.
IT Inactivity Test.
Once the communication is complete the link must be released. The following SCCP
message types are used to release the connection:
264
RLSD Released.
RLC Release Complete.

68P02901W01-M
02 May 2003
Network protocols
GSR6 (Horizon II)
X.25
The X.25 link uses LAPB and LAPD protocols for layer 2 messaging. Both LAPB and
LAPD protocols are variants of HDLC:
S
LAPB is used on the OML.
LAPD is used on Mobis, the XBL and the RSL.
LAPDm
The LAPDm protocol is a variation of LAPD link protocol used exclusively on the Air
Interface.
Signalling link protocols

The link protocols used on the signalling links are listed below:
S
RSL
(Remote BTS-to-BSC) LAPD.
MTL
(BSC-to-MSC)
C7 MTP-SCCP.
OML
(OMC(R)-to-BSS)
X.25 LAPB.
XBL
(RXCDR-to-BSC)
X.25 LAPD.
CBL
(CBC-to-BSC)
X.25.

02 May 2003
68P02901W01-M
265
GSR6 (Horizon II)

Introduction to frequencies and channels
The following sections describe frequency allocations for GSM850, GSM900, EGSM900,
DCS1800, and PCS1900 digital cellular systems with their channel numbers in both
decimal and hexadecimal notation.
Table 2-8 lists and describes GSM, DCS and PCS frequency types.
Table 2-8 GSM Frequency types
Frequency range
Description
GSM850
The GSM 850 MHz frequency range.
PGSM900
The standard GSM 900 MHz frequency

range.
EGSM
The Extended GSM frequency range

(additional 10 Mhz of bandwidth).
DCS1800
The standard DCS1800 MHz frequency

range.
PCS1900
The higher frequency range allocated in

countries such as the USA
GSM850 frequencies
GSM850 systems use radio frequencies between 824-849 MHz for receive and between
869-894 MHz for transmit, as shown in Figure 2-20. RF carriers are spaced every
200 kHz, allowing a total of 124 carriers for use. Other frequencies between 851 MHz
and 869 MHz are available for use by other (non-GSM) cellular systems. A guard band
of 2 MHz of unused frequencies between 849 and 851 MHz protects against interference
between the transmit and receive frequencies. Guard bands between GSM and
non-GSM frequencies depend on the prevailing standards in the country concerned and
on agreements reached by network operators. Any such guard bands are likely to be
quite small; for example, the last carrier of the frequency range may be left unused.
Transmit and receive frequencies are separated by 45 MHz, and this fixed frequency gap
reduces the possibility of interference.
Figure 2-20 GSM850 frequency range
2 MHz GUARD BAND
TRANSMIT FREQUENCIES
RECEIVE FREQUENCIES
OTHER CELLULAR
SYSTEMS
GSM
824
839
849
851
869
GSM
884
894
MHz
TRANSMIT AND RECEIVE FREQUENCIES

ALWAYS 45 MHz APART IN ANY CALL
266

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
GSM850 channels
Channels 128-130
Table 2-9 shows the frequencies for GSM850 channels 128-130.
Table 2-9 GSM850 channels 128 to 130
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
128
80
824.20
869.20
129
81
824.40
869.40
130
82
824.60
869.60
Channels 131-140
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
131
83
824.80
869.80
132
84
825.00
870.00
133
85
825.20
870.20
134
86
825.40
870.40
135
87
825.60
870.60
136
88
825.80
870.80
137
89
826.00
871.00
138
8A
826.20
871.20
139
8B
826.40
871.40
140
8C
826.60
871.60

02 May 2003
68P02901W01-M
267
GSR6 (Horizon II)
Channels 141-150
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
141
8D
826.80
871.80
142
8E
827.00
872.00
143
8F
827.20
872.20
144
90
827.40
872.40
145
91
827.60
872.60
146
92
827.80
872.80
147
93
828.00
873.00
148
94
828.20
873.20
149
95
828.40
873.40
150
96
828.60
873.60
Channels 151-160
Channel number
268
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
151
97
828.80
873.80
152
98
829.00
874.00
153
99
829.20
874.20
154
9A
829.40
874.40
155
9B
829.60
874.60
156
9C
829.80
874.80
157
9D
830.00
875.00
158
9E
830.20
875.20
159
9F
830.40
875.40
160
A0
830.60
875.60

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 161-170
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
161
A1
830.80
875.80
162
A2
831.00
876.00
163
A3
831.20
876.20
164
A4
831.40
876.40
165
A5
831.60
876.60
166
A6
831.80
876.80
167
A7
832.00
877.00
168
A8
832.20
877.20
169
A9
832.40
877.40
170
AA
832.60
877.60
Channels 171-180
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
171
AB
832.80
877.80
172
AC
833.00
878.00
173
AD
833.20
878.20
174
AE
833.40
878.40
175
AF
833.60
878.60
176
B0
833.80
878.80
177
B1
834.00
879.00
178
B2
834.20
879.20
179
B3
834.40
879.40
180
B4
834.60
879.60

02 May 2003
68P02901W01-M
269
GSR6 (Horizon II)
Channels 181-190
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
181
B5
834.80
879.80
182
B6
835.00
880.00
183
B7
835.20
880.20
184
B8
835.40
880.40
185
B9
835.60
880.60
186
BA
835.80
880.80
187
BB
836.00
881.00
188
BC
836.20
881.20
189
BD
836.40
881.40
190
BE
836.60
881.60
Channels 191-200
Channel number
270
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
191
BF
836.80
881.80
192
C0
837.00
882.00
193
C1
837.20
882.20
194
C2
837.40
882.40
195
C3
837.60
882.60
196
C4
837.80
882.80
197
C5
838.00
883.00
198
C6
838.20
883.20
199
C7
838.40
883.40
200
C8
838.60
883.60

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 201-210
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
201
C9
838.80
883.80
202
CA
839.00
884.00
203
CB
839.20
884.20
204
CC
839.40
884.40
205
CD
839.60
884.60
206
CE
839.80
884.80
207
CF
840.00
885.00
208
D0
840.20
885.20
209
D1
840.40
885.40
210
D2
840.60
885.60
Channels 211-220
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
211
D3
840.80
885.80
212
D4
841.00
886.00
213
D5
841.20
886.20
214
D6
841.40
886.40
215
D7
841.60
886.60
216
D8
841.80
886.80
217
D9
842.00
887.00
218
DA
842.20
887.20
219
DB
842.40
887.40
220
DC
842.60
887.60

02 May 2003
68P02901W01-M
271
GSR6 (Horizon II)
Channels 221-230
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
221
DD
842.80
887.80
222
DE
843.00
888.00
223
DF
843.20
888.20
224
E0
843.40
888.40
225
E1
843.60
888.60
226
E2
843.80
888.80
227
E3
844.00
889.00
228
E4
844.20
889.20
229
E5
844.40
889.40
230
E6
844.60
889.60
Channels 231-240
Channel number
272
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
231
E7
844.80
889.80
232
E8
845.00
890.00
233
E9
845.20
890.20
234
EA
845.40
890.40
235
EB
845.60
890.60
236
EC
845.80
890.80
237
ED
846.00
891.00
238
EE
846.20
891.20
239
EF
846.40
891.40
240
F0
846.60
891.60

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 241-251
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
241
F1
846.80
891.80
242
F2
847.00
892.00
243
F3
847.20
892.20
244
F4
847.40
892.40
245
F5
847.60
892.60
246
F6
847.80
892.80
247
F7
848.00
893.00
248
F8
848.20
893.20
249
F9
848.40
893.40
250
FA
848.60
893.60
251
FB
848.80
893.80

02 May 2003
68P02901W01-M
273
GSR6 (Horizon II)
Primary GSM900 frequencies

This section lists all the frequencies used in Primary GSM (PGSM), with their channel
numbers in both decimal and hexadecimal notation.
GSM900 systems use radio frequencies between 890-915 MHz for receive and between
935-960 MHz for transmit, as shown in Figure 2-21. RF carriers are spaced every
200 kHz, allowing a total of 124 carriers for use. Other frequencies between 917 MHz
and 935 MHz are available for use by other (non-GSM) cellular systems. A guard band
of 2 MHz of unused frequencies between 915 and 917 MHz protects against interference
between the transmit and receive frequencies. Guard bands between GSM and
non-GSM frequencies depend on the prevailing standards in the country concerned and
on agreements reached by network operators. Any such guard bands are likely to be
quite small; for example, the last carrier of the frequency range may be left unused.
Figure 2-21 GSM900 frequency range

2 MHz GUARD BAND
RECEIVE FREQUENCIES
OTHER CELLULAR
SYSTEMS
GSM
890
905
915
917
935
GSM
950
960
MHz

274

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Primary GSM900 channels

Channels 110
Table 2-22 shows the frequencies for Primary GSM (PGSM) channels 1 to 10.
Table 2-22 PGSM channels 1 to 10
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
01
890.20
935.20
02
890.40
935.40
03
890.60
935.60
04
890.80
935.80
05
891.00
936.00
06
891.20
936.20
07
891.40
936.40
08
891.60
936.60
09
891.80
936.80
10
0A
892.00
937.00
Channels 1120
Table 2-23 shows the frequencies for PGSM channels 11 to 20.
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
11
0B
892.20
937.20
12
0C
892.40
937.40
13
0D
892.60
937.60
14
0E
892.80
937.80
15
0F
893.00
938.00
16
10
893.20
938.20
17
11
893.40
938.40
18
12
893.60
938.60
19
13
893.80
938.80
20
14
894.00
939.00

02 May 2003
68P02901W01-M
275
GSR6 (Horizon II)
Channels 2130
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
21
15
894.20
939.20
22
16
894.40
939.40
23
17
894.60
939.60
24
18
894.80
939.80
25
19
895.00
940.00
26
1A
895.20
940.20
27
1B
895.40
940.40
28
1C
895.60
940.60
29
1D
895.80
940.80
30
1E
896.00
941.00
Channels 3140
Channel number
276
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
31
1F
896.20
941.20
32
20
896.40
941.40
33
21
896.60
941.60
34
22
896.80
941.80
35
23
897.00
942.00
36
24
897.20
942.20
37
25
897.40
942.40
38
26
897.60
942.60
39
27
897.80
942.80
40
28
898.00
943.00

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 4150
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
41
29
898.20
943.20
42
2A
898.40
943.40
43
2B
898.60
943.60
44
2C
898.80
943.80
45
2D
899.00
944.00
46
2E
899.20
944.20
47
2F
899.40
944.40
48
30
899.60
944.60
49
31
899.80
944.80
50
32
900.00
945.00
Channels 5160
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
51
33
900.20
945.20
52
34
900.40
945.40
53
35
900.60
945.60
54
36
900.80
945.80
55
37
901.00
946.00
56
38
901.20
946.20
57
39
901.40
946.40
58
3A
901.60
946.60
59
3B
901.80
946.80
60
3C
902.00
947.00

02 May 2003
68P02901W01-M
277
GSR6 (Horizon II)
Channels 6170
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
61
3D
902.20
947.20
62
3E
902.40
947.40
63
3F
902.60
947.60
64
40
902.80
947.80
65
41
903.00
948.00
66
42
903.20
948.20
67
43
903.40
948.40
68
44
903.60
948.60
69
45
903.80
948.80
70
46
904.00
949.00
Channels 7180
Channel number
278
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
71
47
904.20
949.20
72
48
904.40
949.40
73
49
904.60
949.60
74
4A
904.80
949.80
75
4B
905.00
950.00
76
4C
905.20
950.20
77
4D
905.40
950.40
78
4E
905.60
950.60
79
4F
905.80
950.80
80
50
906.00
951.00

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 8190
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
81
51
906.20
951.20
82
52
906.40
951.40
83
53
906.60
951.60
84
54
906.80
951.80
85
55
907.00
952.00
86
56
907.20
952.20
87
57
907.40
952.40
88
58
907.60
952.60
89
59
907.80
952.80
90
5A
908.00
953.00
Channels 91100
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
91
5B
908.20
953.20
92
5C
908.40
953.40
93
5D
908.60
953.60
94
5E
908.80
953.80
95
5F
909.00
954.00
96
60
909.20
954.20
97
61
909.40
954.40
98
62
909.60
954.60
99
63
909.80
954.80
100
64
910.00
955.00

02 May 2003
68P02901W01-M
279
GSR6 (Horizon II)
Channels 101110
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
101
65
910.20
955.20
102
66
910.40
955.40
103
67
910.60
955.60
104
68
910.80
955.80
105
69
911.00
956.00
106
6A
911.20
956.20
107
6B
911.40
956.40
108
6C
911.60
956.60
109
6D
911.80
956.80
110
6E
912.00
957.00
Channels 111120
Channel number
280
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
111
6F
912.20
957.20
112
70
912.40
957.40
113
71
912.60
957.60
114
72
912.80
957.80
115
73
913.00
958.00
116
74
913.20
958.20
117
75
913.40
958.40
118
76
913.60
958.60
119
77
913.80
958.80
120
78
914.00
959.00

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 121124
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
121
79
914.20
959.20
122
7A
914.40
959.40
123
7B
914.60
959.60
124
7C
914.80
959.80

02 May 2003
68P02901W01-M
281
GSR6 (Horizon II)
EGSM frequencies
This section lists all the extra frequencies used in Extended GSM (EGSM), with their
channel numbers in both decimal and hexadecimal notation. EGSM also uses all
frequencies listed in PGSM frequencies and PGSM channels.
Figure 2-22 shows that further 10MHz of bandwidth on both transmit and receive
allocations has now extended the GSM900 bandwidth.
Figure 2-22 EGSM frequency range

2 MHz GUARD BAND
RECEIVE FREQUENCIES
905
890
880
OTHER CELLULAR
SYSTEMS
GSM
915
917
935
GSM
950
960
MHz
925
EXTRA 10 MHz BANDWIDTH
BCCH frequency, SDCCH in EGSM

The following configurations are supported by this feature:
S
Stand alone extension band system.
Dual band system with EGSM and DCS1800.
Extension band system with originations across the entire 35MHz (BCCH+SDCCH
in EGSM).
Ensuring handovers stay on EGSM band

The advanced load handover management function offers the operator the ability to
specify EGSM band handovers only to other EGSM bands. Otherwise EGSM handovers
can occur to neighbouring cells that may not have an EGSM band available. DCS1800
bands may be used wastefully, particularly if the band_preference parameter is set, for
example, to DCS1800. A new parameter bss_egsm_alm_allowed enables the feature
and EGSM handovers will occur only to EGSM sites, whatever the setting of
band_preference.
282

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
EGSM channels
Channels 975984
Table 2-35 shows the frequencies for EGSM channels 975 to 984.
Table 2-35 EGSM channels 975 to 984
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
975
3CF
880.20
925.20
976
3D0
880.40
925.40
977
3D1
880.60
925.60
978
3D2
880.80
925.80
979
3D3
881.00
926.00
980
3D4
881.20
926.20
981
3D5
881.40
926.40
982
3D6
881.60
926.60
983
3D7
881.80
926.80
984
3D8
882.00
927.00
Channels 985994
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
985
3D9
882.20
927.20
986
3DA
882.40
927.40
987
3DB
882.60
927.60
988
3DC
882.80
927.80
989
3DD
883.00
928.00
990
3DE
883.20
928.20
991
3DF
883.40
928.40
992
3E0
883.60
928.60
993
3E1
883.80
928.80
994
3E2
884.00
929.00

02 May 2003
68P02901W01-M
283
GSR6 (Horizon II)
Channels 9951004
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
995
3E3
884.20
929.20
996
3E4
884.40
929.40
997
3E5
884.60
929.60
998
3E6
884.80
929.80
999
3E7
885.00
930.00
1000
3E8
885.20
930.20
1001
3E9
885.40
930.40
1002
3EA
885.60
93.60
1003
3EB
885.80
930.80
1004
3EC
886.00
931.00
Channels 10051014
Channel number
284
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
1005
3ED
886.20
931.20
1006
3EE
886.40
931.40
1007
3EF
886.60
931.60
1008
3F0
886.80
931.80
1009
3F1
887.00
932.00
1010
3F2
887.20
932.20
1011
3F3
887.40
932.40
1012
3F4
887.60
932.60
1013
3F5
887.80
932.80
1014
3F6
888.00
933.00

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 10150
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
1015
3F7
888.20
933.20
1016
3F8
888.40
933.40
1017
3F9
888.60
933.60
1018
3FA
888.80
933.80
1019
3FB
889.00
934.00
1020
3FC
889.20
934.20
1021
3FD
889.40
934.40
1022
3FE
889.60
934.60
1023
3FF
889.80
934.80
890.00
935.00

02 May 2003
68P02901W01-M
285
DCS1800 frequencies and channels
GSR6 (Horizon II)

DCS1800 frequencies
This section lists the frequencies used in Digital Cellular System (DCS)1800, with their
channel numbers in both decimal and hexadecimal notation.
DCS1800 systems use radio frequencies between 1710-1785 MHz for receive and
between 1805-1880 MHz for transmit, as shown in Figure 2-23. RF carriers are spaced
every 200 kHz, allowing a total of 373 carriers for use, with one used as a guard band. A
guard band of 20 MHz of unused frequencies between 1785 and 1805 MHz protects
against interference between the transmit and receive frequencies. There is a 100 kHz
guard band between 1710.0 MHz and 1710.1 MHz and between 1784.9 MHz and 1785.0
MHz for receive, and between 1805.0 MHz and 1805.1 MHz and between 1879.9 MHz
and 1880.0 MHz for transmit.
Figure 2-23 DCS1800 frequency range

20 MHz GUARD BAND
RECEIVE FREQUENCIES
1710
1735
1760
1785 1805
1830
1855
1880
MHz

DCS1800 channels
Channels 512520
Table 2-40 shows the frequencies for DCS1800 channels 512 to 520.
Table 2-40 DCS 1800 channels 512 to 520
Channel number
286
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
512
200
1710.2
1805.2
513
201
1710.4
1805.4
514
202
1710.6
1805.6
515
203
1710.8
1805.8
516
204
1711.0
1806.0
517
205
1711.2
1806.2
518
206
1711.4
1806.4

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
519
207
1711.6
1806.6
520
208
1711.8
1806.8
Channels 521530
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
521
209
1712.0
1807.0
522
20A
1712.2
1807.2
523
20B
1712.4
1807.4
524
20C
1712.6
1807.6
525
20D
1712.8
1807.8
526
20E
1713.0
1808.0
527
20F
1713.2
1808.2
528
210
1713.4
1808.4
529
211
1713.6
1808.6
530
212
1713.8
1808.8
Channels 531540
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
531
213
1714.0
1809.0
532
214
1714.2
1809.2
533
215
1714.4
1809.4
534
216
1714.6
1809.6
535
217
1714.8
1809.8
536
218
1715.0
1810.0
537
219
1715.2
1810.2
538
21A
1715.4
1810.4
539
21B
1715.6
1810.6
540
21C
1715.8
1810.8

02 May 2003
68P02901W01-M
287
GSR6 (Horizon II)
Channels 541550
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
541
21D
1716.0
1811.0
542
21E
1716.2
1811.2
543
21F
1716.4
1811.4
544
220
1716.6
1811.6
545
221
1716.8
1811.8
546
222
1717.0
1812.0
547
223
1717.2
1812.2
548
224
1717.4
1812.4
549
225
1717.6
1812.6
550
226
1717.8
1812.8
Channels 551560
Channel number
288
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
551
227
1718.0
1813.0
552
228
1718.2
1813.2
553
229
1718.4
1813.4
554
22A
1718.6
1813.6
555
22B
1718.8
1813.8
556
22C
1719.0
1814.0
557
22D
1719.2
1814.2
558
22E
1719.4
1814.4
559
22F
1719.6
1814.6
560
230
1719.8
1814.8

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 561570
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
561
231
1720.0
1815.0
562
232
1720.2
1815.2
563
233
1720.4
1815.4
564
234
1720.6
1815.6
565
235
1720.8
1815.8
566
236
1721.0
1816.0
567
237
1721.2
1816.2
568
238
1721.4
1816.4
569
239
1721.6
1816.6
570
23A
1721.8
1816.8
Channels 571580
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
571
23B
1722.0
1817.0
572
23C
1722.2
1817.2
573
23D
1722.4
1817.4
574
23E
1722.6
1817.6
575
23F
1722.8
1817.8
576
240
1723.0
1818.0
577
241
1723.2
1818.2
578
242
1723.4
1818.4
579
243
1723.6
1818.6
580
244
1723.8
1818.8

02 May 2003
68P02901W01-M
289
GSR6 (Horizon II)
Channels 581590
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
581
245
1724.0
1819.0
582
246
1724.2
1819.2
583
247
1724.4
1819.4
584
248
1724.6
1819.6
585
249
1724.8
1819.8
586
24A
1725.0
1820.0
587
24B
1725.2
1820.2
588
24C
1725.4
1820.4
589
24D
1725.6
1820.6
590
24E
1725.8
1820.8
Channels 591600
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
591
24F
1726.0
1821.0
592
250
1726.2
1821.2
593
251
1726.4
1821.4
594
252
1726.6
1821.6
595
253
1726.8
1821.8
596
254
1727.0
1822.0
597
255
1727.2
1822.2
598
256
1727.4
1822.4
599
257
1727.6
1822.6
600
258
1727.8
1822.8
Channels 601610
290

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
601
259
1728.0
1823.0
602
25A
1728.2
1823.2
603
25B
1728.4
1823.4
604
25C
1728.6
1823.6
605
25D
1728.8
1823.8
606
25E
1729.0
1824.0
607
25F
1729.2
1824.2
608
260
1729.4
1824.4
609
261
1729.6
1824.6
610
262
1729.8
1824.8
Channels 611620
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
611
263
1730.0
1825.0
612
264
1730.2
1825.2
613
265
1730.4
1825.4
614
266
1730.6
1825.6
615
267
1730.8
1825.8
616
268
1731.0
1826.0
617
269
1731.2
1826.2
618
26A
1731.4
1826.4
619
26B
1731.6
1826.6
620
26C
1731.8
1826.8

02 May 2003
68P02901W01-M
291
GSR6 (Horizon II)
Channels 621630
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
621
26D
1732.0
1827.0
622
26E
1732.2
1827.2
623
26F
1732.4
1827.4
624
270
1732.6
1827.6
625
271
1732.8
1827.8
626
272
1733.0
1828.0
627
273
1733.2
1828.2
628
274
1733.4
1828.4
629
275
1733.6
1828.6
630
276
1733.8
1828.8
Channels 631640
Channel number
292
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
631
277
1734.0
1829.0
632
278
1734.2
1829.2
633
279
1734.4
1829.4
634
27A
1734.6
1829.6
635
27B
1734.8
1829.8
636
27C
1735.0
1830.0
637
27D
1735.2
1830.2
638
27E
1735.4
1830.4
639
27F
1735.6
1830.6
640
280
1735.8
1830.8

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 641650
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
641
281
1736.0
1831.0
642
282
1736.2
1831.2
643
283
1736.4
1831.4
644
284
1736.6
1831.6
645
285
1736.8
1831.8
646
286
1737.0
1832.0
647
287
1737.2
1832.2
648
288
1737.4
1832.4
649
289
1737.6
1832.6
650
28A
1737.8
1832.8
Channels 651660
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
651
28B
1738.0
1833.0
652
28C
1738.2
1833.2
653
28D
1738.4
1833.4
654
28E
1738.6
1833.6
655
28F
1738.8
1833.8
656
290
1739.0
1834.0
657
291
1739.2
1834.2
658
292
1739.4
1834.4
659
293
1739.6
1834.6
660
294
1739.8
1834.8

02 May 2003
68P02901W01-M
293
GSR6 (Horizon II)
Channels 661670
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
661
295
1740.0
1835.0
662
296
1740.2
1835.2
663
297
1740.4
1835.4
664
298
1740.6
1835.6
665
299
1740.8
1835.8
666
29A
1741.0
1836.0
667
29B
1741.2
1836.2
668
29C
1741.4
1836.4
669
29D
1741.6
1836.6
670
29E
1741.8
1836.8
Channels 671680
Channel number
294
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
671
29F
1742.0
1837.0
672
2A0
1742.2
1837.2
673
2A1
1742.4
1837.4
674
2A2
1742.6
1837.6
675
2A3
1742.8
1837.8
676
2A4
1743.0
1838.0
677
2A5
1743.2
1838.2
678
2A6
1743.4
1838.4
679
2A7
1743.6
1838.6
680
2A8
1743.8
1838.8

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 681690
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
681
2A9
1744.0
1839.0
682
2AA
1744.2
1839.2
683
2AB
1744.4
1839.4
684
2AC
1744.6
1839.6
685
2AD
1744.8
1839.8
686
2AE
1745.0
1840.0
687
2AF
1745.2
1840.2
688
2B0
1745.4
1840.4
689
2B1
1745.6
1840.6
690
2B2
1745.8
1840.8
Channels 691700
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
691
2B3
1746.0
1841.0
692
2B4
1746.2
1841.2
693
2B5
1746.4
1841.4
694
2B6
1746.6
1841.6
695
2B7
1746.8
1841.8
696
2B8
1747.0
1842.0
697
2B9
1747.2
1842.2
698
2BA
1747.4
1842.4
699
2BB
1747.6
1842.6
700
2BC
1747.8
1842.8

02 May 2003
68P02901W01-M
295
GSR6 (Horizon II)
Channels 701710
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
701
2BD
1748.0
1843.0
702
2BE
1748.2
1843.2
703
2BF
1748.4
1843.4
704
2C0
1748.6
1843.6
705
2C1
1748.8
1843.8
706
2C2
1749.0
1844.0
707
2C3
1749.2
1844.2
708
2C4
1749.4
1844.4
709
2C5
1749.6
1844.6
710
2C6
1749.8
1844.8
Channels 711720
Channel number
296
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
711
2C7
1750.0
1845.0
712
2C8
1750.2
1845.2
713
2C9
1750.4
1845.4
714
2CA
1750.6
1845.6
715
2CB
1750.8
1845.8
716
2CC
1751.0
1846.0
717
2CD
1751.2
1846.2
718
2CE
1751.4
1846.4
719
2CF
1751.6
1846.6
720
2D0
1751.8
1846.8

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 721730
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
721
2D1
1752.0
1847.0
722
2D2
1752.2
1847.2
723
2D3
1752.4
1847.4
724
2D4
1752.6
1847.6
725
2D5
1752.8
1847.8
726
2D6
1753.0
1848.0
727
2D7
1753.2
1848.2
728
2D8
1753.4
1848.4
729
2D9
1753.6
1848.6
730
2DA
1753.8
1848.8
Channels 731740
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
731
2DB
1754.0
1849.0
732
2DC
1754.2
1849.2
733
2DD
1754.4
1849.4
734
2DE
1754.6
1849.6
735
2DF
1754.8
1849.8
736
2E0
1755.0
1850.0
737
2E1
1755.2
1850.2
738
2E2
1755.4
1850.4
739
2E3
1755.6
1850.6
740
2E4
1755.8
1850.8

02 May 2003
68P02901W01-M
297
GSR6 (Horizon II)
Channels 741750
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
741
2E5
1756.0
1851.0
742
2E6
1756.2
1851.2
743
2E7
1756.4
1851.4
744
2E8
1756.6
1851.6
745
2E9
1756.8
1851.8
746
2EA
1757.0
1852.0
747
2EB
1757.2
1852.2
748
2EC
1757.4
1852.4
749
2ED
1757.6
1852.6
750
2EE
1757.8
1852.8
Channels 751760
Channel number
298
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
751
2EF
1758.0
1853.0
752
2F0
1758.2
1853.2
753
2F1
1758.4
1853.4
754
2F2
1758.6
1853.6
755
2F3
1758.8
1853.8
756
2F4
1759.0
1854.0
757
2F5
1759.2
1854.2
758
2F6
1759.4
1854.4
759
2F7
1759.6
1854.6
760
2F8
1759.8
1854.8

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 761770
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
761
2F9
1760.0
1855.0
762
2FA
1760.2
1855.2
763
2FB
1760.4
1855.4
764
2FC
1760.6
1855.6
765
2FD
1760.8
1855.8
766
2FE
1761.0
1856.0
767
2FF
1761.2
1856.2
768
300
1761.4
1856.4
769
301
1761.6
1856.6
770
302
1761.8
1856.8
Channels 771780
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
771
303
1762.0
1857.0
772
304
1762.2
1857.2
773
305
1762.4
1857.4
774
306
1762.6
1857.6
775
307
1762.8
1857.8
776
308
1763.0
1858.0
777
309
1763.2
1858.2
778
30A
1763.4
1858.4
779
30B
1763.6
1858.6
780
30C
1763.8
1858.8

02 May 2003
68P02901W01-M
299
GSR6 (Horizon II)
Channels 781790
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
781
30D
1764.0
1859.0
782
30E
1764.2
1859.2
783
30F
1764.4
1859.4
784
310
1764.6
1859.6
785
311
1764.8
1859.8
786
312
1765.0
1860.0
787
313
1765.2
1860.2
788
314
1765.4
1860.4
789
315
1765.6
1860.6
790
316
1765.8
1860.8
Channels 791800
Channel number
2100
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
791
317
1766.0
1861.0
792
318
1766.2
1861.2
793
319
1766.4
1861.4
794
31A
1766.6
1861.6
795
31B
1766.8
1861.8
796
31C
1767.0
1862.0
797
31D
1767.2
1862.2
798
31E
1767.4
1862.4
799
31F
1767.6
1862.6
800
320
1767.8
1862.8

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 801810
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
801
321
1768.0
1863.0
802
322
1768.2
1863.2
803
323
1768.4
1863.4
804
324
1768.6
1863.6
805
325
1768.8
1863.8
806
326
1769.0
1864.0
807
327
1769.2
1864.2
808
328
1769.4
1864.4
809
329
1769.6
1864.6
810
32A
1769.8
1864.8
Channels 811820
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
811
32B
1770.0
1865.0
812
32C
1770.2
1865.2
813
32D
1770.4
1865.4
814
32E
1770.6
1865.6
815
32F
1770.8
1865.8
816
330
1771.0
1866.0
817
331
1771.2
1866.2
818
332
1771.4
1866.4
819
333
1771.6
1866.6
820
334
1771.8
1866.8

02 May 2003
68P02901W01-M
2101
GSR6 (Horizon II)
Channels 821830
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
821
335
1772.0
1867.0
822
336
1772.2
1867.2
823
337
1772.4
1867.4
824
338
1772.6
1867.6
825
339
1772.8
1867.8
826
33A
1773.0
1868.0
827
33B
1773.2
1868.2
828
33C
1773.4
1868.4
829
33D
1773.6
1868.6
830
33E
1773.8
1868.8
Channels 831840
Channel number
2102
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
831
33F
1774.0
1869.0
832
340
1774.2
1869.2
833
341
1774.4
1869.4
834
342
1774.6
1869.6
835
343
1774.8
1869.8
836
344
1775.0
1870.0
837
345
1775.2
1870.2
838
346
1775.4
1870.4
839
347
1775.6
1870.6
840
348
1775.8
1870.8

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 841850
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
841
349
1776.0
1871.0
842
34A
1776.2
1871.2
843
34B
1776.4
1871.4
844
34C
1776.6
1871.6
845
34D
1776.8
1871.8
846
34E
1777.0
1872.0
847
34F
1777.2
1872.2
848
350
1777.4
1872.4
849
351
1777.6
1872.6
850
352
1777.8
1872.8
Channels 851860
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
851
353
1778.0
1873.0
852
354
1778.2
1873.2
853
355
1778.4
1873.4
854
356
1778.6
1873.6
855
357
1778.8
1873.8
856
358
1779.0
1874.0
857
359
1779.2
1874.2
858
35A
1779.4
1874.4
859
35B
1779.6
1874.6
860
35C
1779.8
1874.8

02 May 2003
68P02901W01-M
2103
GSR6 (Horizon II)
Channels 861870
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
861
35D
1780.0
1875.0
862
35E
1780.2
1875.2
863
35F
1780.4
1875.4
864
360
1780.6
1875.6
865
361
1780.8
1875.8
866
362
1781.0
1876.0
867
363
1781.2
1876.2
868
364
1781.4
1876.4
869
365
1781.6
1876.6
870
366
1781.8
1876.8
Channels 871880
Channel number
2104
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
871
367
1782.0
1877.0
872
368
1782.2
1877.2
873
369
1782.4
1877.4
874
36A
1782.6
1877.6
875
36B
1782.8
1877.8
876
36C
1783.0
1878.0
877
36D
1783.2
1878.2
878
36E
1783.4
1878.4
879
36F
1783.6
1878.6
880
370
1783.8
1878.8

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 881885
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
881
371
1784.0
1879.0
882
372
1784.2
1879.2
883
373
1784.4
1879.4
884
374
1784.6
1879.6
885
375
1784.8
1879.8

02 May 2003
68P02901W01-M
2105
PCS1900 frequencies and channels
GSR6 (Horizon II)

PCS1900 frequencies
This section lists the frequencies used in PCS1900, with their channel numbers in both
decimal and hexadecimal notation.
PCS1900 systems use radio frequencies between 1850-1910 MHz for receive and
between 1930-1990 MHz for transmit, as shown in Figure 2-24. RF carriers are spaced
every 200 kHz, allowing a total of 299 carriers for use. A guard band of 20 MHz of
unused frequencies between 1910 and 1930 MHz protects against interference between
the transmit and receive frequencies. There is a 100 kHz guard band between 1850.0
MHz and 1850.1 MHz and between 1909.9 MHz and 1910.0 MHz for receive, and
between 1930.0 MHz and 1930.1 MHz and between 1989.9 MHz and 1990.0 MHz for
transmit.
Figure 2-24 PCS1900 frequency range

20 MHz GUARD BAND
RECEIVE FREQUENCIES
1850
1870
1895
1910 1930
1950
1975
1990
MHz

PCS1900 channels
Channels 512520
Table 2-78 shows the frequencies for PCS1900 channels 512 to 520.
Table 2-78 PCS 1900 channels 512 to 520
Channel number
2106
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
512
200
1850.2
1930.2
513
201
1850.4
1930.4
514
202
1850.6
1930.6
515
203
1850.8
1930.8
516
204
1851.0
1931.0
517
205
1851.2
1931.2
518
206
1851.4
1931.4

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
519
207
1851.6
1931.6
520
208
1851.8
1931.8
Channels 521530
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
521
209
1852.0
1932.0
522
20A
1852.2
1932.2
523
20B
1852.4
1932.4
524
20C
1852.6
1932.6
525
20D
1852.8
1932.8
526
20E
1853.0
1933.0
527
20F
1853.2
1933.2
528
210
1853.4
1933.4
529
211
1853.6
1933.6
530
212
1853.8
1933.8
Channels 531540
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
531
213
1854.0
1934.0
532
214
1854.2
1934.2
533
215
1854.4
1934.4
534
216
1854.6
1934.6
535
217
1854.8
1934.8
536
218
1855.0
1935.0
537
219
1855.2
1935.2
538
21A
1855.4
1935.4
539
21B
1855.6
1935.6
540
21C
1855.8
1935.8

02 May 2003
68P02901W01-M
2107
GSR6 (Horizon II)
Channels 541550
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
541
21D
1856.0
1936.0
542
21E
1856.2
1936.2
543
21F
1856.4
1936.4
544
220
1856.6
1936.6
545
221
1856.8
1936.8
546
222
1857.0
1937.0
547
223
1857.2
1937.2
548
224
1857.4
1937.4
549
225
1857.6
1937.6
550
226
1857.8
1937.8
Channels 551560
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
551
227
1858.0
1938.0
552
228
1858.2
1938.2
553
229
1858.4
1938.4
554
22A
1858.6
1938.6
555
22B
1858.8
1938.8
556
22C
1859.0
1939.0
557
22D
1859.2
1939.2
558
22E
1859.4
1939.4
559
22F
1859.6
1939.6
560
230
1859.8
1939.8
Channels 561570
2108

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
561
231
1860.0
1940.0
562
232
1860.2
1940.2
563
233
1860.4
1940.4
564
234
1860.6
1940.6
565
235
1860.8
1940.8
566
236
1861.0
1941.0
567
237
1861.2
1941.2
568
238
1861.4
1941.4
569
239
1861.6
1941.6
570
23A
1861.8
1941.8
Channels 571580
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
571
23B
1862.0
1942.0
572
23C
1862.2
1942.2
573
23D
1862.4
1942.4
574
23E
1862.6
1942.6
575
23F
1862.8
1942.8
576
240
1863.0
1943.0
577
241
1863.2
1943.2
578
242
1863.4
1943.4
579
243
1863.6
1943.6
580
244
1863.8
1943.8

02 May 2003
68P02901W01-M
2109
GSR6 (Horizon II)
Channels 581590
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
581
245
1864.0
1944.0
582
246
1864.2
1944.2
583
247
1864.4
1944.4
584
248
1864.6
1944.6
585
249
1864.8
1944.8
586
24A
1865.0
1945.0
587
24B
1865.2
1945.2
588
24C
1865.4
1945.4
589
24D
1865.6
1945.6
590
24E
1865.8
1945.8
Channels 591600
Channel number
2110
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
591
24F
1866.0
1946.0
592
250
1866.2
1946.2
593
251
1866.4
1946.4
594
252
1866.6
1946.6
595
253
1866.8
1946.8
596
254
1867.0
1947.0
597
255
1867.2
1947.2
598
256
1867.4
1947.4
599
257
1867.6
1947.6
600
258
1867.8
1947.8

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 601610
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
601
259
1868.0
1948.0
602
25A
1868.2
1948.2
603
25B
1868.4
1948.4
604
25C
1868.6
1948.6
605
25D
1868.8
1948.8
606
25E
1869.0
1949.0
607
25F
1869.2
1949.2
608
260
1869.4
1949.4
609
261
1869.6
1949.6
610
262
1869.8
1949.8
Channels 611620
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
611
263
1870.0
1950.0
612
264
1870.2
1950.2
613
265
1870.4
1950.4
614
266
1870.6
1950.6
615
267
1870.8
1950.8
616
268
1871.0
1951.0
617
269
1871.2
1951.2
618
26A
1871.4
1951.4
619
26B
1871.6
1951.6
620
26C
1871.8
1951.8

02 May 2003
68P02901W01-M
2111
GSR6 (Horizon II)
Channels 621630
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
621
26D
1872.0
1952.0
622
26E
1872.2
1952.2
623
26F
1872.4
1952.4
624
270
1872.6
1952.6
625
271
1872.8
1952.8
626
272
1873.0
1953.0
627
273
1873.2
1953.2
628
274
1873.4
1953.4
629
275
1873.6
1953.6
630
276
1873.8
1953.8
Channels 631640
Channel number
2112
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
631
277
1874.0
1954.0
632
278
1874.2
1954.2
633
279
1874.4
1954.4
634
27A
1874.6
1954.6
635
27B
1874.8
1954.8
636
27C
1875.0
1955.0
637
27D
1875.2
1955.2
638
27E
1875.4
1955.4
639
27F
1875.6
1955.6
640
280
1875.8
1955.8

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 641650
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
641
281
1876.0
1956.0
642
282
1876.2
1956.2
643
283
1876.4
1956.4
644
284
1876.6
1956.6
645
285
1876.8
1956.8
646
286
1877.0
1957.0
647
287
1877.2
1957.2
648
288
1877.4
1957.4
649
289
1877.6
1957.6
650
28A
1877.8
1957.8
Channels 651660
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
651
28B
1878.0
1958.0
652
28C
1878.2
1958.2
653
28D
1878.4
1958.4
654
28E
1878.6
1958.6
655
28F
1878.8
1958.8
656
290
1879.0
1959.0
657
291
1879.2
1959.2
658
292
1879.4
1959.4
659
293
1879.6
1959.6
660
294
1879.8
1959.8

02 May 2003
68P02901W01-M
2113
GSR6 (Horizon II)
Channels 661670
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
661
295
1880.0
1960.0
662
296
1880.2
1960.2
663
297
1880.4
1960.4
664
298
1880.6
1960.6
665
299
1880.8
1960.8
666
29A
1881.0
1961.0
667
29B
1881.2
1961.2
668
29C
1881.4
1961.4
669
29D
1881.6
1961.6
670
29E
1881.8
1961.8
Channels 671680
Channel number
2114
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
671
29F
1882.0
1962.0
672
2A0
1882.2
1962.2
673
2A1
1882.4
1962.4
674
2A2
1882.6
1962.6
675
2A3
1882.8
1962.8
676
2A4
1883.0
1963.0
677
2A5
1883.2
1963.2
678
2A6
1883.4
1963.4
679
2A7
1883.6
1963.6
680
2A8
1883.8
1963.8

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 681690
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
681
2A9
1884.0
1964.0
682
2AA
1884.2
1964.2
683
2AB
1884.4
1964.4
684
2AC
1884.6
1964.6
685
2AD
1884.8
1964.8
686
2AE
1885.0
1965.0
687
2AF
1885.2
1965.2
688
2B0
1885.4
1965.4
689
2B1
1885.6
1965.6
690
2B2
1885.8
1965.8
Channels 691700
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
691
2B3
1886.0
1966.0
692
2B4
1886.2
1966.2
693
2B5
1886.4
1966.4
694
2B6
1886.6
1966.6
695
2B7
1886.8
1966.8
696
2B8
1887.0
1967.0
697
2B9
1887.2
1967.2
698
2BA
1887.4
1967.4
699
2BB
1887.6
1967.6
700
2BC
1887.8
1967.8

02 May 2003
68P02901W01-M
2115
GSR6 (Horizon II)
Channels 701710
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
701
2BD
1888.0
1968.0
702
2BE
1888.2
1968.2
703
2BF
1888.4
1968.4
704
2C0
1888.6
1968.6
705
2C1
1888.8
1968.8
706
2C2
1889.0
1969.0
707
2C3
1889.2
1969.2
708
2C4
1889.4
1969.4
709
2C5
1889.6
1969.6
710
2C6
1889.8
1969.8
Channels 711720
Channel number
2116
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
711
2C7
1890.0
1970.0
712
2C8
1890.2
1970.2
713
2C9
1890.4
1970.4
714
2CA
1890.6
1970.6
715
2CB
1890.8
1970.8
716
2CC
1891.0
1971.0
717
2CD
1891.2
1971.2
718
2CE
1891.4
1971.4
719
2CF
1891.6
1971.6
720
2D0
1891.8
1971.8

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 721730
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
721
2D1
1892.0
1972.0
722
2D2
1892.2
1972.2
723
2D3
1892.4
1972.4
724
2D4
1892.6
1972.6
725
2D5
1892.8
1972.8
726
2D6
1893.0
1973.0
727
2D7
1893.2
1973.2
728
2D8
1893.4
1973.4
729
2D9
1893.6
1973.6
730
2DA
1893.8
1973.8
Channels 731740
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
731
2DB
1894.0
1974.0
732
2DC
1894.2
1974.2
733
2DD
1894.4
1974.4
734
2DE
1894.6
1974.6
735
2DF
1894.8
1974.8
736
2E0
1895.0
1975.0
737
2E1
1895.2
1975.2
738
2E2
1895.4
1975.4
739
2E3
1895.6
1975.6
740
2E4
1895.8
1975.8

02 May 2003
68P02901W01-M
2117
GSR6 (Horizon II)
Channels 741750
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
741
2E5
1896.0
1976.0
742
2E6
1896.2
1976.2
743
2E7
1896.4
1976.4
744
2E8
1896.6
1976.6
745
2E9
1896.8
1976.8
746
2EA
1897.0
1977.0
747
2EB
1897.2
1977.2
748
2EC
1897.4
1977.4
749
2ED
1897.6
1977.6
750
2EE
1897.8
1977.8
Channels 751760
Channel number
2118
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
751
2EF
1898.0
1978.0
752
2F0
1898.2
1978.2
753
2F1
1898.4
1978.4
754
2F2
1898.6
1978.6
755
2F3
1898.8
1978.8
756
2F4
1899.0
1979.0
757
2F5
1899.2
1979.2
758
2F6
1899.4
1979.4
759
2F7
1899.6
1979.6
760
2F8
1899.8
1979.8

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 761770
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
761
2F9
1900.0
1980.0
762
2FA
1900.2
1980.2
763
2FB
1900.4
1980.4
764
2FC
1900.6
1980.6
765
2FD
1900.8
1980.8
766
2FE
1901.0
1981.0
767
2FF
1901.2
1981.2
768
300
1901.4
1981.4
769
301
1901.6
1981.6
770
302
1901.8
1981.8
Channels 771780
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
771
303
1902.0
1982.0
772
304
1902.2
1982.2
773
305
1902.4
1982.4
774
306
1902.6
1982.6
775
307
1902.8
1982.8
776
308
1903.0
1983.0
777
309
1903.2
1983.2
778
30A
1903.4
1983.4
779
30B
1903.6
1983.6
780
30C
1903.8
1983.8

02 May 2003
68P02901W01-M
2119
GSR6 (Horizon II)
Channels 781790
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
781
30D
1904.0
1984.0
782
30E
1904.2
1984.2
783
30F
1904.4
1984.4
784
310
1904.6
1984.6
785
311
1904.8
1984.8
786
312
1905.0
1985.0
787
313
1905.2
1985.2
788
314
1905.4
1985.4
789
315
1905.6
1985.6
790
316
1905.8
1985.8
Channels 791800
Channel number
2120
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
791
317
1906.0
1986.0
792
318
1906.2
1986.2
793
319
1906.4
1986.4
794
31A
1906.6
1986.6
795
31B
1906.8
1986.8
796
31C
1907.0
1987.0
797
31D
1907.2
1987.2
798
31E
1907.4
1987.4
799
31F
1907.6
1987.6
800
320
1907.8
1987.8

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Channels 801810
Channel number
Frequency (MHz)
Decimal
Hex.
Receive
Transmit
801
321
1908.0
1988.0
802
322
1908.2
1988.2
803
323
1908.4
1988.4
804
324
1908.6
1988.6
805
325
1908.8
1988.8
806
326
1909.0
1989.0
807
327
1909.2
1989.2
808
328
1909.4
1989.4
809
329
1909.6
1989.6
810
32A
1909.8
1989.8

02 May 2003
68P02901W01-M
2121
2122

68P02901W01-M
GSR6 (Horizon II)
02 May 2003
Chapter 3
BSS general description

02 May 2003
68P02901W01-M
31
GSR6 (Horizon II)
32

68P02901W01-M
02 May 2003
Chapter overview
GSR6 (Horizon II)
Chapter overview
Introduction to BSS information
This chapter provides a general description of the Motorola Base Station System (BSS),
which forms part of the GSM digital cellular system.
The GSM recommendations define the functions of the BSS, but allow flexibility in its
design. This chapter also describes some of the unique features of the Motorola BSS.
The chapter contains the following information about the BSS:
S
Base station system.
BSC description.
BTS description.
XCDR description.
BSS site configuration.
Network topology.
BSS standardized interfaces.
Radio system and control functions.
Cell system radio channel reuse.
BSS redundancy.
Motorola PCU general description.

02 May 2003
68P02901W01-M
33
Base station system
GSR6 (Horizon II)
Base station system

BSS purpose and functions
The BSS is the interface between the Mobile Station (MS) and the Mobile services
Switching Centre (MSC) elements of the network.
The purpose of the BSS is to perform a variety of functions. The following comprise the
functions provided by the BSS:
S
Radio coverage areas and control functions for one or more cells.
Radio coverage areas and control functions for the MSs in the cells.
Signalling data processing and routing of the traffic data exchanged between the
MS and the MSC.
Digital signal interfaces to the land circuits linking the BSS and the MSC.
Links
The BSS has links to the MSC and the MSs. The following comprise the links:
Interface links
Land circuits link the Base Station Controller (BSC) to the MSC. Each interface link
contains a multiplexed E1/T1 serial data stream. The BSS places MS originated, or MS
terminated subscriber (signalling or traffic) data in a timeslot (channel) on a serial data
stream.
Air interface link

The communication link, or Air Interface, between the BSS and the MS uses digital radio
techniques.
BSS to MSC link

The BSS-to-MSC interface uses E1/T1 links.
BSS network elements

The BSS consists of three basic Network Elements (NEs). The following comprise the
network elements:
34
Base Station Controller (BSC).
Base Transceiver Stations (BTSs) assigned to the BSC.
Speech transcoder (XCDR) or remote speech transcoder (RXCDR) assigned to

the BSC.

68P02901W01-M
02 May 2003
Base station system
GSR6 (Horizon II)
Typical BSS layout

Figure 3-1 shows the layout of a typical system with two BSSs. Each BSS contains
several components to make the link between the MS and the MSC. The BSS
components are described in more detail in the following sections.
Figure 3-1 Dual BSS system
BSS #2
BSS #1
MS
BTS
SITE
MS
BTS
SITE
MS
BTS
SITE
MS
BSC
SITE
WITH
XCDR
BTS
SITE
BTS
SITE
MS
BTS
SITE
BSC
SITE
BTS
SITE
RXCDR
(NOTE 2)
A
MSC
LEGEND
Air Interface
A
PSTN/ISDN/PUBLIC DATA NETWORK
A Interface
NOTES
(1) DASHED LINES ENCLOSE NETWORK COMPONENTS
OF A PARTICULAR BSS AND DO NOT SHOW THE BSS
SERVICE AREA.
(2) REMOTE TRANSCODING (RXCDR) IS LOCATED AT
MSC SITE, BUT IS PART OF BSS #2.

02 May 2003
68P02901W01-M
35
BSC description
GSR6 (Horizon II)
BSC description
BSC purpose and functions
The BSC network element provides the control for the BSS. It controls and manages the
associated BTSs, and interfaces with the Operations and Maintenance Centre (OMC).
The purpose of the BSC is to perform a variety of functions. The following comprise the
functions provided by the BSC:
S
Controls the BTS components.
Performs Call Processing.
Performs Operations and Maintenance (O & M).
Provides the O & M link (OML) between the BSS and the OMC.
Provides the A Interface between the BSS and the MSC.
Manages the radio channels.
Transfers signalling information to and from MSs.
One BSC can support multiple BTSs, depending on traffic density.
BSC to MSC interaction

The MSC communicates with, and passes signalling and traffic data to BSCs. The BSCs
provide the opportunity for remote switching, distributed control, and traffic concentration.
Many types of call handling signalling do not affect the BSC directly. In these cases, the
BSC serves as a relay point between an MS and the MSC.
Digital switching matrix

The BSC includes a digital switching matrix. There is no fixed correspondence between
the radio channels at the BSS and the terrestrial circuits (trunks) which connect the BSS
to the MSC. While the BSC selects the radio channel, the MSC selects the trunks.
The BSC connects the traffic channel (TCH) assigned to a particular MS with the trunk
assigned by the MSC.
The switching matrix also lets the BSS perform handovers within a single BSS without
involving the MSC.
Terrestrial circuit device management

This feature enables CICs to be identified in three ways: By CIC number, on an MMS
basis, on an MMS basis providing timeslot and, if appropriate, group within a timeslot.
36

68P02901W01-M
02 May 2003
BSC description
GSR6 (Horizon II)
BSC capacity
Scaleable BSC capacity is enabled through the further exploitation of the increased
processing performance and memory of the GPROC2. As a result GPROC2s are
required for use throughout the BSC. The BSC maximum capacity is increased as
shown in Table 3-1.
Table 3-1 BSC maximum capacities
Parameter
GSR4/4.1
GSR5
GSR 5.1
GSR 6
Sites
100
100
100
100
Cells
250
250
250
250
Carriers (RTFs)
384
384
384
512*
DRIs
634
634
634
634
Trunks
1920
2400
2400
3200*
RSLs
250
250
250
250
MMSs
350
248
248
248
PATHs
200
200
200
200
DHPs
168
168
168
168
* Only if the enhanced BSC capacity feature is not restricted.

Otherwise as for GSR5.1
This increased capacity is achieved through the deployment of GPROC2s for each
function at the BSC, including Base Station Processor (BSP) and Link Control Function
(LCF). BSCs for a given capacity are available, with hardware and software, according
to the required capacity.

02 May 2003
68P02901W01-M
37
BTS description
GSR6 (Horizon II)
BTS description
BTS purpose and functions
The BTS network element consists of the hardware components, such as radios,
interface modules and antenna systems that provide the Air Interface between the BSS
and the MSs.
The BTS radio equipment used must be able to support the type of operation required,
that is, GSM900, EGSM900, DCS1800 or PCS1900. Refer to the GSM frequencies
section of Chapter 2 for an explanation of the characteristics of these systems.
The BTS provides radio channels (RF carriers) for a specific RF coverage area. The
radio channel is the communication link between the MSs within an RF coverage area
and the BSS. A single BTS site contains all the BTS network components that provide
RF channels for the same geographic area.
The BTS also has a limited amount of control functionality which reduces the amount of
traffic between the BTS and BSC.
Frequency reuse plan

The frequency reuse plan for the cellular system defines:
S
The RF coverage area of each cell.
The number of RF channels in each cell.
The RF frequency of the channels that each BTS site in the network will provide.
The reuse plan of RF frequencies across multiple cells.
RF coverage areas
The term, cell defines a single RF coverage area which may be either a multidirectional
and sectorized area, or an omnidirectional single area.
A BTS site can provide either of the following:
S
An omnidirectional RF coverage area, singular and undivided.
Multidirectional RF coverage area divided into sectors.
The antenna system at the BTS site determines the type of RF coverage area.
Antenna systems
BTS site equipment (RF hardware) can be configured for operation with the following
types of antenna systems for RF coverage areas:
38
1 omnidirectional sector.
2 directional sectors (for use along highways).
3 directional sectors (120_ or alternate 60_).
6 directional sectors (60_).

68P02901W01-M
02 May 2003
Transcoder description
GSR6 (Horizon II)
Transcoder description
Transcoder purpose and functions
The speech transcoder (XCDR) is the digital signal processing equipment that performs
GSM defined speech encoding and decoding within the network.
The speech transcoder is the interface between the 64 kbit/s PCM channel in the land
network and the 13 kbit/s vocoder (actually 22.8 kbit/s after channel coding) channel
used on the Air Interface. This reduces the amount of information carried on the Air
Interface and hence, its bandwidth.
NOTE
13 kbit/s is the data rate of speech. This is mapped onto 16

kbit/s Transcoder Rate Adaption Unit (TRAU) frames and then
channel coded for protection, finally comprising 22.8 kbit/s.
The transcoder can multiplex four traffic channels into a single 64 kbit/s channel
(timeslot). Therefore, an E1/T1 serial link can carry four times as many channels. This
can reduce the number of E1/T1 leased lines required to connect remotely located
equipment.
Remote transcoder
Speech transcoding can take place either at the BSC or between the MSC and BSC.
When the transcoder is between the MSC and the BSC it is called a remote transcoder
(RXCDR)
Transcoding location
The location of the XCDR affects the overall cost of leased lines.
Transcoding at the BSC

If transcoding takes place at the BSC, then the number of leased lines required to
connect the BSC to the required BTSs is reduced.
Remote transcoding at the MSC

If transcoding takes place remotely at the MSC, then the number of leased lines from the
MSC (RXCDR) to the BSC is also reduced, thus providing an even greater savings.

02 May 2003
68P02901W01-M
39
BSS site configuration
GSR6 (Horizon II)

Introduction to BSS site configuration
The Motorola BSS uses a variety of BSC, BTS and RXCDR site configurations to meet a
wide range of requirements.
The following items must be considered when meeting requirements for cell site
configuration:
S
The number of RF carriers.
The distribution of the RF carriers at a site.
The type of transmit channel combining.
The number of RF carriers configured for frequency hopping.
The antenna configuration.
The number of E1/T1 links for traffic/signalling channels.
The speech transcoder location.
The equipment redundancy provided for the site(s).
Congestion relief.
BSS configurations
The BSS is set up to perform a variety of functions. In order to perform those functions,
the following equipment is required:
S
A BSC site.
Up to 100 BTS sites.
A RXCDR site may be necessary if XCDR functionality is not integrated with BSC.
However, note that the RXCDR is considered a separate site which is not part of
the BSS.
Flexibility
Motorola BSS equipment uses a flexible architecture that expands easily. The BSC, BTS
and RXCDR can start small and expand incrementally. The size of the Motorola BSC
provides significant switching capability to handle a variety of different BTS sites and
network configurations.
310

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Definitions
BSC
Provides the BSC function for controlling BTS sites. A Base Station System Control
(BSSC) cabinet can contain the necessary modules for the BSC-to-BTS line interface
and for the BSC-to-MSC line interface, acting as different BSCs. Alternatively, the
equipment can be connected to form a single BSC.
RXCDR
Provides the RXCDR function for speech transcoding. For example, the BSSC2 cabinet,
contains the necessary modules for the BSC-to-RXCDR line interface and speech
transcoder modules as part of the line interface to the MSC. Alternatively, the two
shelves can be combined for more capacity.
Combined BSC and XCDR

The BSSC2 cabinet is equipped to provide both the BSC function for controlling BTS
sites and the XCDR function for speech transcoding within one shelf. Alternatively, it
could have the BSC in one shelf and the XCDR in the other. This cabinet contains the
modules needed for the BSC-to-BTS, BSC-to-MSC, and XCDR functions.
BSS maximum capacity

The maximum capacity of a BSS is 2400 trunks from the MSC. This maximum is
independent of the number of BTS sites.
In order to achieve 384 carriers for the BSC on the Dense Urban Call model (the primary
motivation for this feature), the following assumptions regarding the BSC are made:
S
Support of two Message Transfer Links (MTLs) per Link Control Function (LCF) at
40% MTL link utilization.
Support of: 25 LCFs.
GPROC2 processing is approximately four times that of a GPROC.

NOTE
Increasing the number of trunks limit will not provide value for
Dense Urban environments unless these assumptions hold true.

02 May 2003
68P02901W01-M
311
GSR6 (Horizon II)
BTS cabinet
A BTS cabinet contains the radio transceivers and associated Air Interface modules that
make up the BTS function. The BTS cabinet can contain equipment for up to 6 RF
carriers and support up to three different RF coverage areas or sectors.
A BTS cabinet can be configured to provide the BTS functions only. For this type of
cabinet, the following are the BTS functions provided:
S
The Air Interface to the MSs.
The line interface to a remote BSC.
BSSC cabinet
A single Base Station System Control (BSSC) cabinet can provide:
S
The BSC function.
The RXCDR function.
The combined BSC and RXCDR function.
The equipment configuration in the cabinet determines the function(s).
BSS/MSC configurations
The following BSS equipment can be installed at an MSC:
S
A BSSC2 cabinet with the BSC function.
A BSSC2 cabinet with the XCDR speech transcoding function.
If a BSSC2 cabinet with the XCDR is not implemented, speech transcoding can be
integrated into the BSSC2 cabinet with the BSC function.
312

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
BSS with more than one BTS

Figure 3-2 shows examples of two BSSs, designated BSS #1 and #2, with more than one
BTS site. The BTS sites in these BSSs contain BTS cabinets that perform the BTS
function only; they do not include the BSC function or transcoding.
A separate BSC site operates the BTS sites of BSS #1 remotely. The BSSC2 cabinet for
this BSS integrates transcoding for this BSS with the BSC function.
A separate BSC operates the BTS sites of BSS #2 remotely. Transcoding for this BSS is
located remotely in a BSSC2 cabinet at the MSC site.
Figure 3-2 Multiple BTS sites per BSS
LEGEND
NOTES
(1) DASHED LINES ENCLOSE NETWORK COMPONENTS
OF A PARTICULAR BSS AND DO NOT SHOW THE BSS
SERVICE AREA.
(2) REMOTE TRANSCODING (RXCDR) IS LOCATED AT
MSC SITE, BUT IS PART OF BSS #2.
Air Interface
A
A Interface
BSS #2
BSS #1
MS
BTS
SITE
MS
BTS
SITE
MS
BTS
SITE
MS
BSC
SITE
WITH
XCDR
BTS
SITE
BTS
SITE
MS
BTS
SITE
BSC
SITE
BTS
SITE
RXCDR
(NOTE 2)
A
MSC
PSTN/ISDN/PUBLIC DATA NETWORK

02 May 2003
68P02901W01-M
313
GSR6 (Horizon II)
For correct implementation of the multiple BTS feature, the BSS supports the following
functionality:
Non-imperative handover rejection

The BSS rejects an incoming non-imperative handover if it will cause congestion relief
procedures to be triggered. The BSS does not allow an incoming handover if the reason
for that handover is congestion relief and the handover itself will lead to the invocation of
congestion relief procedures. Should such a handover be allowed, then the net result
would simply be the movement of a congestion problem from one cell to another.
Congestion relief handover retry

The source cell will not attempt a congestion relief handover, for a period of time, to a
target cell which had rejected a previous handover attempt, both imperative and
congestion relief. A new timer element is used to control this period of time. It does not,
however, affect any imperative handover retries. These handovers are allowed to take
place regardless of such timers, as they are needed in order to keep the call active.
Incoming handover requests

If a BSS target cell rejects an incoming handover, because that handover would trigger
congestion relief procedures, the target cell attempts to inform the source cell of its
future, intra-BSS only, accessibility status. If the target cell is configured to optionally
invoke congestion relief procedures after rejecting the handover request, then it may be
capable of handling the necessary handovers.
If a BSS target cell accepts an incoming handover due to congestion relief, and this
handover itself triggers the target cell congestion relief procedures, the target cell does
not trigger any handover attempts back to the source cell which triggered the congestion
relief to begin with.
Handover retry
The source cell optionally retries an imperative, intra-BSS only, handover to target cells
which rejected the initial handover request and initiated a congestion relief procedure.
Multiband mobile station redirection

The BSS does not allow an incoming band preference handover should the servicing of
that handover cause this percentage to be exceeded. If such a handover is allowed to
be serviced, the net result would simply be the movement of a Multiband congestion
problem from one cell to another.
314

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Flexible neighbour cell processing

This feature enhances the existing handover decision process by adding more flexibility
in the way neighbour cell processing is handled for handovers.
This process has four blocks:
Neighbour with lower RXLEV readings

Neighbour cells with lower RXLEV readings than the servicing cell are valid candidates
for handovers.
Neighbours with low disuse counts

Neighbour cells whose disuse count is less than equal to the maximum disuse count are
valid candidates for handovers.
Disuse count is defined as the number of consecutive measurement reports a previously
reported neighbour is not reported by the Mobile.
Modified RXQUAL and RXLEV handover parameters

Neighbour cells will use RXQUAL or RXLEV handovers only when the Base or the
Mobile is at full power. This feature removes all candidates for interference handovers
until the mobile or the base reaches full power (Applicable only for decision algorithm 1).
Warmup period for neighbour cells

This parameter allows no warm up period for neighbour cells. Averaging and power
budget calculations begin immediately.
This feature uses an RXLEV of 0 if missing a measurement report.

02 May 2003
68P02901W01-M
315
Network topology
GSR6 (Horizon II)
Network topology
Basic configurations
There are three basic ways to configure BSS sites:
S
Star (spoke) configuration.
Daisy chain configuration.
Fork configuration (used in conjunction with a daisy chain configuration).
Combinations of these configurations can be used to connect the BSC-to-remote BTS

sites.
Topology model
Network topology is specified in terms of the continuous traffic routes between the BSC
and a terminating remote BTS site, including any intermediate remote BTS sites.
Physical site interconnections are through E1/T1 links.
Figure 3-3 shows a possible topology using combinations of the three basic
configurations. Site interconnections in the figure represent E1/T1 links, not traffic
routes. The actual connections between network sites may consist of single or multiple
E1/T1 links.
Figure 3-3 Topology model
Open-ended daisy chain.
MSC
BTS 12
BSC
BTS 13
BTS 14
Star
BTS 5
BTS 10
BTS 1
Daisy chain with a fork.
Daisy chain has a return-loop
back to the BSC.
BTS 4
BTS 6
BTS 2
BTS 7
BTS 11
BTS 3
Daisy chain with a fork.

Fork has a return-loop
back to the chain.
BTS 9
BTS 8
The subsections that follow describe typical traffic routes for each configuration.
Star (spoke)
The traffic route is from the BSC site to terminating site BTS 10.
Open-ended daisy chain

Open-ended daisy chain traffic routes comprise the following:
316
The BSC site to terminating site BTS 12.
The BSC site through intermediate site BTS 12 to terminating site BTS 13.
The BSC site through intermediate sites BTS 12 and BTS 13 to terminating site
BTS 14.
68P02901W01-M
02 May 2003
Network topology
GSR6 (Horizon II)
Daisy chain with fork and return loop to chain

Table 3-2 shows the main paths to the BSC for each BTS and the alternate path for each
BTS in the looped part of the network.
Table 3-2 BTS - BSC main and alternate paths (fork with return loop)
BTS site
Main path via...
Alternate path via...
Direct
BTS 5
BTS 6 and BTS 5
BTS 8, BTS 9, BTS 6 and BTS 5
BTS 7, BTS 6 and BTS 5
BTS 6 and BTS 5
BTS 8, BTS 7, BTS 6 and BTS 5
Fault condition
In the event of a fault anywhere in the fork, the return loop provides an alternative
communications route between the BSC and BTS 9.
For example, if there is a break in the E1/T1 link(s) fork between sites BTS 6 and BTS 9,
then sites BTS 5, BTS 6, BTS 7, BTS 8 and BTS 9 function like an open-ended chain
allowing site BTS 9 to communicate with the BSC.
Daisy chain with fork and return loop to BSC

Table 3-3 shows that for each BTS, one main path and at least one alternate path exists
to the BSC.
Table 3-3 BTS - BSC main and alternate paths (chain with return loop)
BTS site
Main path via...
Alternate path via...
Direct
BTS 1
BTS 3 and BTS 4
BTS 4
BTS 2 and BTS 1
Direct
11
BTS 2 and BTS 1
Fault condition
In the event of a fault anywhere in the chain, the alternate paths provide each BTS site
on the chain or fork with an alternate communications route to the BSC.
For example, assume there is a break in the E1/T1 link(s) between sites BTS 2 and
BTS 3. Sites BTS 11, BTS 2, and BTS 1 function like an open-ended chain and
communicate with the BSC via the traffic routes on the operational part of the loop. Sites
BTS 3 and BTS 4 function like an open-ended chain and communicate with the BSC via
the traffic routes on the operational part of the loop.

02 May 2003
68P02901W01-M
317
Network topology
GSR6 (Horizon II)
Drop and insert BTS site configuration

The drop and insert option enhances the flexibility of Motorola BSS equipment
configuration. This option allows a single E1/T1 circuit to connect several BTS sites in
either a linear daisy chain or a ring topology. The closing end of the ring of BTS sites
connects to a BSC.
Fault tolerance
A closed-loop or closed-ring topology enhances the fault tolerance of the drop and insert
configuration. This topology prevents any single line fault from interrupting
communication to any site.
Leased line saving
The Motorola drop and insert option for BTS sites saves on leased line costs when
addressing sparse rural or special coverage requirements such as roadways.
GSM compliance
A maximum of 10 BTS sites can be chained together in a closed loop and still comply
with GSM system timing and delay recommendations.
Maximum size
Each BTS site in the drop and insert configuration has one or more BTS cabinets. In the
case of chaining the maximum number of BTS sites together, each BTS cabinet in the
drop and insert configuration contains one radio transceiver and associated air interface
modules, and modules to provide the line interfaces to a BSSC or a BTS cabinet.
If a particular site requires additional transceivers, the maximum number of sites chained
together should be reduced, proportionately.
318

68P02901W01-M
02 May 2003
BSS standardized interfaces
GSR6 (Horizon II)

Introduction to BSS standardized interfaces
Many GSM recommendations deal with standards for interfaces between network
elements. Motorola employs internationally recognized standards for most of the
network communications. For example, Motorola uses ITU-TSS Signalling System 7
(C7) and X.25 protocols extensively throughout the network.
Using standardized interfaces throughout the GSM digital cellular system ensures
compatibility of network elements from different manufacturers.
Protocol layering
The functional layering of protocols is based in part on the seven layer model for open
systems interconnection suggested by the International Standards Organization (ISO).
Each layer performs a specific set of functions that are isolated from the other layers.
However, the functions of a particular layer enhance the functions performed by the lower
layers.
The following subsections detail the BSS related equipment-to-equipment interfaces that
are standardized and specified by GSM.
A interface
The interface between the MSC and the BSS is a standard interface, called the A
Interface. The A Interface is fully defined in the GSM recommendations.
The signalling portion of the interface between the MSC and the BSC uses the C7
protocol, for which application parts are defined (for example the base station system
application part (BSSAP)).
The A Interface allows customers to purchase the switching equipment (for example the
MSC) from one supplier, and the radio equipment (such as the BSS) from another
supplier, and still have equipment compatibility.
Abis interface
The GSM defined interface between the BSC and the remotely located BTS equipment is
called the Abis interface. It uses Link Access Procedure D (LAPD).
At the application levels, GSM defines a special set of messages unique to the mobile
application.
Mobis
The Motorola defined BSC-to-BTS interface is a modification of the Abis standard called
Mobis. It distributes functionality between the BSC and the remote BTS equipment, and
offers several advantages:
S
Reduced signalling link traffic, which permits efficient use of E1/T1 links. The BTS
performs handover data processing. This reduces the amount of data sent to the
BSC over the signalling link. This significantly reduces the amount of processing
required in the BSC.
Better synchronization of the BSC and BTS. This ensures better handover from
one traffic channel to another.
Improved overload control and fault recovery algorithms.
Efficient use of the paging and access grant channels.
Control of more than one BTS (sectors) on a single control link.

02 May 2003
68P02901W01-M
319
GSR6 (Horizon II)
Air interface
The GSM recommendations include detailed specifications for the radio channel (Air
Interface) between the MS and the BTS. The Air Interface uses a three layer protocol.
Layer 1 (physical channel)

Layer 1 is the physical channel layer. This layer transmits and receives coded
information symbols over the radio link. Layer 1 provides the basic time division
multiplexing (TDM) frame structure including timeslot, frame, multiframe, and so on.
Layer 1 also provides for multiplexing and demultiplexing (channel encoding/decoding) of
the different types of logical channels that the network requires, such as traffic channels,
signalling or control channels and synchronization channels.
Layer 2 (logical channel)

Layer 2 is a transport mechanism between layer 3 and layer 1. Layer 2 provides for error
free transport of layer 3 signalling.
Layer 3 (network control)

Layer 3 provides three major network management functions:
S
Radio resource management (paging, cipher mode setting, frequency redefinition,

channel assignments, handover, measurement reports).
Mobility management (authentication, location updating, International Mobile

Subscriber Identity (IMSI) attach/detach, periodic registration, ID confidentiality).
Call management (call set up, supplementary services, Dual Tone Multi-Frequency
(DTMF), short message service).
Lb interface
The Lb-interface is a new interface for support of location services. It is located between
the BSS and a BSS-based SMLC. The interface uses the C7 protocol, and is modelled
(from the BSS viewpoint) from the A-Interface. The interface is not present when the
SMLC is NSS-based.
320

68P02901W01-M
02 May 2003
Radio system and control functions
GSR6 (Horizon II)

Introduction to radio system and control functions
The Air Interface provides an associated control channel. This allows communication of
signalling control channel data simultaneously with (and transparent to) user traffic
channel (TCH) data.
The associated control channel is available for both the uplink and the downlink. It allows
continuous information reporting from the MS to the BSS, and continuous control of the
MS from the BSS.
Handover
The GSM handover process uses a mobile assisted technique for accurate and fast
handovers, in order to:
S
Maintain the user connection link quality.
Minimize interference.
Manage traffic distribution.
3-timeslot offset
The TDMA frame structure for uplink transmission is offset by three timeslots from the
downlink frame structure; this interval allows the MS to have only one synthesizer to
assess the signal level of adjacent cells. SACCH and other signalling information, which
is sent transparently with user traffic, allows continuous reporting of information from the
subscriber to the base and the continuous control of the mobile from the base.
Because of this offset, the MS never needs to transmit and receive simultaneously. The
ability of the MS to change frequency and monitor a neighbour channel while engaged in
a speech or data conversation is important for the high performance MS assisted
handover scheme employed.
MS assisted technique
The MS assists the handover decision process by performing certain measurements.
When the MS is engaged in a speech (or data) conversation, a portion of the TDMA
frame is idle while the rest of the frame is used for uplink (BTS receive) and downlink
(BTS transmit) timeslots. During the idle time period of the frame, the MS changes radio
channel frequency and monitors and measures the signal level of the six best adjacent
cells.
Handover decision process

Measurements which feed the handover decision algorithm are made at both ends of the
radio link.
MS end
At the MS end, measurements are continuously signalled, via the associated control
channel, to the BSS where the decision for handover is ultimately made.
MS measurements include:
S
Serving cell downlink quality (bit error rate (BER) estimate).
Serving cell downlink received signal level, and adjacent cells downlink received
signal level.
The MS also decodes the Base Station ID Code (BSIC) from the six best adjacent cells,
and reports the BSICs and the measurement information to the BTS.
S

02 May 2003
68P02901W01-M
321
GSR6 (Horizon II)
BTS end
At the BTS site end, measurements which are available to the handover algorithm
involve only the uplink communication path, link quality, received signal level, and MS to
BTS site distance. The MS RF transmit output power budget is also considered in the
handover decision. If the MS could be served by an adjacent cell at a lower power, the
handover is recommended. From a system perspective, handover may be considered
due to loading or congestion conditions. In this case, the MSC or BSC tries to balance
channel usage among cells.
Handover measurement summary

Figure 3-4 shows the measurements made for handovers.
Figure 3-4 Handover measurements
Downlink
(Received) Level
Uplink
(Received) Level
Uplink
Quality (BER)
BTS
(Base
Transceiver
Station)
Subscriber-to-Base
Distance
Downlink
Quality (BER)
Handover
Control
Adjacent Channel
Downlink Level
MS
(Mobile
Station)
Adjacent Channel
Cell ID
Dynamic power control

As an MS gets closer to the BTS, both use less power to transmit. Over a 30 dB range,
power is stepped up or down in 2 dB steps. Power control reduces interference with
other calls and also extends the battery life in MSs, which is particularly important in
hand portables.
Discontinuous transmission
The speech transcoder is equipped with a Voice Activity Detector (VAD) that detects the
presence of speech data. Transmission is stopped in the intervals when speech is
absent. This is called Discontinuous Transmission (DTx) of speech. The feature is
controlled by the system operator and may be enabled in either or both directions.
The benefits of DTx include the following:
S
In portable units, transmit battery power is consumed only when it is needed for
speech or data.
The potential for interference is reduced since transmitters are only energized
when needed. This has the side-effect of improving the system spectrum
efficiency.
The algorithm used to calculate DTx maximises the amount of off-time, while avoiding
speech clipping or distortion. Silences in the speech pattern are encoded by the VAD at
a rate of 500 bit/s rather than the full 13 kbit/s, producing background noise called
comfort noise which reduces noise contrast effects. The continuous transmission of
signalling information is unaffected by DTx.
Discontinuous reception
Once the MS is in synchronization with the BTS (it uses the FCCH and SCH channels to
get into synchronization), it monitors two control channels: the Broadcast Control
Channel (BCCH) and the Paging Channel (PCH). If the MS is not in use, it can
determine when control information is next due, and switch off between signals. This is
called Discontinuous Reception (DRx). The potential for 2% power cycling in standby
extends battery life in MSs.
322

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Timing adjustment
The TDMA bursts transmitted by MSs over the same radio channel must be kept apart
for proper recovery of received data at the BTS site. The MSs are not stationary,
therefore propagation delay of MS transmissions can vary. Sometimes the delay
becomes significantly long and a burst overlaps into the next timeslot. This causes
undesirable errors in the recovered data.
Timing correction is provided to maintain the guard time needed between bursts. A
closed loop mechanism provides timing correction for the MS. The BSS detects (via a
timing advance algorithm) changes in timing and if necessary the BSS sends timing
advance messages to the MS, commanding it to transmit earlier or later, as required, to
offset the modified propagation delay.
In addition, the timing advance algorithm provides an estimation of the distance between
the MS and the BTS site. This distance estimation can be a valuable parameter in
handover decision algorithms.
Frequency synchronization
All BSS frequencies and timing signals are synchronized to a high stability reference
oscillator in the BSS. This oscillator can free run or be synchronized to the recovered
clock signal from a selected E1/T1 serial link. Either case provides better than 0.05 ppm
stability. MSs lock to a reference contained in a synchronization burst transmitted from
the BTS site. This reference has a stability of 0.1 ppm.
BTS cabinet synchronization sources

For sites with collocated cabinets, considerable cost savings are possible by equipping
one cabinet with reference clock circuits and distributing the synchronized reference
signals to other cabinets eliminating their need for clock circuits. This distribution is via
fibre optic cables.

02 May 2003
68P02901W01-M
323
Cell system radio channel reuse
GSR6 (Horizon II)

Introduction to cell system radio channel reuse
Each MS is assigned to one of eight traffic channels (timeslots) carried on an RF channel
transmit/receive frequency pair 200 kHz wide. The combination of digital channel coding
and GMSK modulation provides robust radio channel transmissions and the ability to
operate with a carrier/interference (C/I) level of 9 dB. The RF frequency reuse distance
between cells (or sectors) is directly proportional to the C/I level. Reuse distance is the
minimum distance that can separate co-channel cells or sectors and still deliver
acceptable performance with a tolerable amount of radio transmission interference.
Because the C/I level is relatively small, RF frequencies used in a cell can be reused in
other cells that are a relatively small distance away. Thus, the frequency reuse patterns
are smaller, which permits more frequency reuse within a geographic area.
GSM digital cellular systems typically use a 9-site omni or 4-site/3-sector pattern. A
2-site (sectored) pattern, which requires a unique Motorola design, is also available.
NOTE
The GSM meaning of the term cell, as a coverage area/sector, is

being used here. In analogue systems the term cell is normally
used for a site.
9-site reuse pattern

Figure 3-5 shows how GSM cellular systems using a 9-site reuse pattern, are configured
with sites providing omni-directional RF coverage areas. These sites provide about a 15
dB C/I for 90% location reliability.
In this arrangement the allocated frequencies are divided into 9 reuse groups.
Figure 3-5 9-site reuse pattern cellular system
FREQUENCY
REUSE
GROUP 2
FREQUENCY
REUSE
GROUP 1
FREQUENCY
REUSE
GROUP 3
FREQUENCY
REUSE
GROUP 8
FREQUENCY
REUSE
GROUP 4
FREQUENCY
REUSE
GROUP 7
FREQUENCY
REUSE
GROUP 5
FREQUENCY
REUSE
GROUP 9
FREQUENCY
REUSE
GROUP 6
FREQUENCY
REUSE
GROUP 1
RE-USED
9-SITE (OMNI) REUSE
324

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
3-site 3-sector reuse pattern

Figure 3-6 shows a GSM cellular systems using a 3-site (3-sectored), 120 degree sector
arrangement. This system will provide about a 12 dB C/I for 90% location reliability.
Figure 3-6 3-site (sectored) cellular system

a2
a1
b2
a3
b1
c2
c1
b3
a2
c3
a1
a3
3-SITE (SECTORED) REUSE

(120 DEGREE SECTORS)
4-site reuse pattern

Systems using sites with three 120 RF coverage sectors provide about a 13.6 dB C/I for
90% location reliability. This arrangement requires dividing the allocated frequencies into
nine reuse groups.

Systems using sites with six 60 RF coverage sectors provide about a 13.5 dB C/I for
90% location reliability. This arrangement requires dividing the allocated frequencies into
18 reuse groups.

The Motorola unique 2-site reuse pattern is a 4-site repeat pattern that reuses each
frequency group twice. Therefore, this plan is an effective 2-site repeat pattern. Each
site is sectored into six 60 RF coverage areas. This patterns capacity is 40% greater
than the generic 3-site reuse pattern using cells sectored into three 120 RF coverage
areas, and provides an equivalent C/I performance.
In this arrangement, the allocated frequencies are divided into 12 reuse groups.

02 May 2003
68P02901W01-M
325
GSR6 (Horizon II)
Cell pattern reuse comparisons

Table 3-4 compares the features of the various reuse patterns.
Table 3-4 Sector re-use pattern features
Reuse
pattern
326
No. of sectors
per site
C/I ratio
No. of frequency
reuse groups
9-site
1 omnidirectional 15 dB for 90%

location reliability
4-site
3 of 120_
13.8 dB for 90%

3-site
6 of 60_
13.5 dB for 90%

18
2-site
6 of 60_
Equivalent to the
3 site/3 sector
pattern
12

68P02901W01-M
Comments
40% greater
capacity than
3 site/3 sector
pattern
02 May 2003
BSS redundancy
GSR6 (Horizon II)
BSS redundancy
Introduction to BSS redundancy
Redundancy can optionally be added to prevent single faults from producing a capacity
loss.
Redundancy means adding more modules than necessary to support a given capacity.
These additional modules are in standby mode until the system needs them to replace a
failed module. Fault management of the redundant modules minimizes the number of
additional modules the system requires to provide full redundancy. This design is
achieved by using N+1 redundancy wherever possible.
BSS fault management

When failures occur, the BSS software fault diagnostics can usually isolate the failure
down to a replaceable module. Fault Management (FM) classifies failures as type A
or B.
S
Type A failures cause an alarm at the Operations and Maintenance Centre (OMC)
and/or local terminal (TTY), and result in the faulty module being taken Out Of
Service (OOS).
Type B failures cause an alarm at the OMC and/or TTY, but the module is not
taken OOS.
Failed modules
Table 3-5 contrasts situations when a module fails:
Table 3-5 Failed module situations
If ...
Then ...
And ...
There is no redundant module...
Nothing happens...
Call capacity is lost.
There is a redundant module...
The BSS automatically

switches over to the
redundant module...
No call capacity is lost;

service continues
uninterrupted.
RF carrier redundancy
All RF carrier equipment can provide both signalling and traffic channels. Redundancy
can be provided by equipping the cell/sector with more carrier equipment than traffic
requirements dictate:
S
If additional radio channel frequencies for the cell/sector are available, the
redundant carrier can provide additional capacity until a carrier or associated
equipment fails.
If additional radio channel frequencies for the cell/sector are not available, the
redundant carrier is only switched into service in response to a failure.
Interface redundancy
Each site connects to the BSC or MSC through E1/T1 serial links as digital carriers.
Therefore, each site requires at least one line interface module (A interface or Abis
interface). Each line interface module provides an interface for two E1/T1 serial links.
To provide redundancy at the interface, an additional E1/T1 serial link and an additional
interface module are added.
02 May 2003
68P02901W01-M
327
BSS redundancy
GSR6 (Horizon II)
BTS redundancy
To provide BTS redundancy, one set of RF carrier modules and associated digital
modules for each cell or sector RF coverage area within one or more BTS cabinets at a
site are required.
BSC redundancy
To provide BSC redundancy, duplicate digital modules within the same BTS/BSSC
cabinet are required.
N+1 redundancy is available for the processing and power supply modules.
RXCDR redundancy
To provide RXCDR redundancy, duplicate digital modules within the same shelf of the
same BSSC cabinet are required.
N+1 redundancy is available for the processing and power supply modules.
328

68P02901W01-M
02 May 2003
General Packet Radio Service (GPRS)
GSR6 (Horizon II)

Introduction to GPRS
GPRS is a packet radio system that allows mobile subscriber (MS) units to access data
services (such as World Wide Web (WWW) or email) using a modified GSM air interface
protocol. The modified air interface protocol allows multiple MS units to share a single
timeslot, and also allows different mobiles to utilize the uplink and downlink timeslots.
This enables a more cost-effective use of network resources for data transfer.
Two units form the basis of the Motorola GPRS hardware:
S
The Packet Control Unit (PCU) located at the BSS.
The GSN complex module (SGSN, GGSN, GSN CommHub, and ISS).
Figure 3-7 shows an overview of the GPRS network.
Figure 3-7 The GPRS network
BSC
A interface
MSC
HLR
Gr
Mobis
BTS
Gs
BSS-PCU
interface
PCU
Gc
Gb
SGSN
GGSN
Gn
Gi
PDN
Gd
Um
Gp
MS
GGSN
SMC-GMSC
SMC-IWMSC
Other
PLMN
Packet control unit

GPRS introduces a new device at the BSS, known as the Packet Control Unit (PCU).
The PCU is an interface adaptor handler unit that permits the Motorola GSM facility
access to the packet network. As such the PCU needs interfaces with the BSC on the
GSM side, and the SGSN on the packet network side. The PCU manages the packet
radio interface and also enables the interface from the BSS to the SGSN. The PCU
itself, is managed by the existing OMC-R.
See Introduction to the Motorola Packet Control Unit (PCU) section for full details.
02 May 2003
68P02901W01-M
329
GSR6 (Horizon II)
GSN complex
Network elements
GPRS introduces the following new network elements, as shown in Figure 3-8:
S
The Serving GPRS Support Node (SGSN).
The Gateway GPRS Support Node (GGSN).
The Shelf Manager (at the OMC-G).
The GSN Complex.
The SGSN keeps track of the individual MS locations, and performs security functions
and access control. The SGSN is connected to the BSS via a Frame Relay network.
The GGSN provides interworking with external packet-switched networks and is
connected with SGSNs via an IP-based GPRS backbone network. This backbone
network includes the CommHub and ISS (IP Support Server) nodes.
The Shelf Manager at the OMC-G allows an operator to monitor the hardware in a shelf.
The Shelf Manager is displayed in the Navigator under its parent Complex and at the
same level as SGSN, GGSN, and so on.
A shelf is an entity housing 16 cPCI slots plus cooling fans and
power supply units. Four of the slots are taken up by system
cards leaving 12 of the slots free for SGSNs (each SGSN is a
two-card unit in release 1.6.1.3, one for the Control Function
(CF) and the other for the Transmission Function (TF) function).
NOTE
GSN complex
A GSN complex comprises the following:
S
Communications cabinet housing the CommHub and the Internet Support

Services (ISS) (consisting of Domain Name Server (DNS), Network Time Protocol
(NTP), Charging Gateway (CG), and Network File System (NFS)).
GGSN cabinet housing one or more GGSNs.
GSN cabinet housing a cPCI shelf.

NOTE
The GSN complex is not described in this manual. For further

information on the GSN complex, see the Motorola GSN Service
Manual.
Operations and Maintenance (O&M) applications

O&M applications are Load Management, Configuration Management, Fault
Management, Performance Management and Security Management. These applications
are provided for the GPRS network through an OMC-G. The OMC-G comprises NT and
UNIX.
330

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
GSM/GPRS network architecture

The Motorola specific implementation of GPRS, as integrated with the existing GSM
infrastructure equipment, is shown in Figure 3-8.
The new GPRS equipment consists of a PCU attached to the BSC, as part of the BSS.
The SGSN, GGSN, GSN CommHub, and ISS are included as part of the GSN complex
equipment.
Each BSC has a dedicated PCU, and multiple BSSs can be attached to one GSN
complex. Several GSN complexes can be networked together to serve one PLMN. One
OMC-G can manage several GSN complexes.
Figure 3-8 GPRS network architecture showing the PCU and GSN complex
GSM EQUIPMENT
MSC
GPRS EQUIPMENT
RADIUS SERVER
(NON-TRANSPARENT
MODE)
HLR
RXCDR
PDN
OMC-G
(including Shelf
Manager)
OMC-R
PCU
BSC
ISS
BSSn
GGSN
GSN
COMMHUB
BSS2
BTSs
SGSN
GSNn
GSN1
BSS1
BILLING
SYSTEM
OPERATOR SERVER
COMPLEX
- RADIUS SERVER
(OPERATOR IS ISP,
TRANSPARENT MODE)
- DHCP SERVER
- DNS SERVER

02 May 2003
68P02901W01-M
331
Packet control unit
GSR6 (Horizon II)
Packet control unit

Introduction to the PCU
The following text provides a general description of the Motorola Packet Control Unit
(PCU), which links between the GPRS Support Node (GSN) and the Motorola BSS.
The GSM recommendations define the functions of the GPRS, but allow flexibility in its
design and this text describes some of the unique features of the Motorola PCU.
PCU information
The following sections contain the following information about the PCU:
332
PCU overview.
PCU features.
PCU description.
PCU architecture
PCU interfaces.
PCU system and control of functions.

68P02901W01-M
02 May 2003
PCU overview
GSR6 (Horizon II)
PCU overview
PCU summary
The PCU is a collection of high-performance processors that are responsible for:
S
Packet scheduling on the air interface.
Ensuring that efficient use is made of the air interface.
Taking small uplink packets from the E1 links connected to the BSS that are
carrying user data from the MS units, and forming larger uplink packets to be sent
over the E1 links to the SGSN.
Packet segmentation and packetization on the frame relay link to the SGSN
network entity.
Taking downlink packets from the SGSN and segmenting these packets into small
packets to be sent to the MS units.
PCU environment
Figure 3-9 shows the PCU positioned within the GSM/GPRS network.
Figure 3-9 PCU within the GSM/GPRS network
HLR
Gs
MSC
PDN
Gr
MAP-G
Gn
SGSN
TE
Gi
GGSN
Gb
Gn
PCU
GGSN
BSC
Um
MS
Abis
BTS
OTHER
PLMN
SIGNALLING
SIGNALLING AND DATA TRANSFER

02 May 2003
68P02901W01-M
333
PCU features
GSR6 (Horizon II)
PCU features
List of PCU features
The PCU features are described in the following sections:
334
Point-to-point GPRS service.
GPRS radio channel allocation.
Medium Access Control mode - dynamic allocation.
Support of MS classes.
GPRS coding schemes.
Dynamic adaption of coding schemes.
Two phase packet access.
Enhanced GPRS one phase access.
Frequency hopping of PDCH.
Power control for uplink/downlink.
Gb interface.
PCU load balancing and sharing (Gb and BTS).
MS flow control

68P02901W01-M
02 May 2003
PCU features
GSR6 (Horizon II)
Point-to-point GPRS service

GPRS provides a new set of bearer services supporting packet mode transmission. This
supporting low-speed and high-speed signalling, a data transmission technique with
improved efficiency compared with circuit based techniques.
GPRS enables the subscriber to send and receive data in an end-to-end packet transfer
mode, without utilizing circuit switched network resources. General characteristics where
GPRS offers superior performance compared with circuit technology include applications
where:
S
The transmission of small volumes of data is frequent.
The transmission of large volumes of data is infrequent.
The time between successive transmissions greatly exceeds the average transfer
delay.
The network operator can size the network optimally for efficient support of a mix of
GPRS and voice traffic. To support this mix, each timeslot on a GPRS carrier can be
configured as dedicated to circuit traffic, or GPRS traffic, or can be configured as
switchable between the two. In the case of switchable timeslots, GPRS traffic has
precedence over circuit switched traffic on the last remaining timeslot.
The GPRS network supports cell reselection modes as shown in Table 3-6.
The reselection modes allow the network to provide the Mobile Station (MS) with
information regarding the quality and signal strength of the link. The MS then uses this
information to determine whether to perform a cell reselection based upon signal strength
of neighbour cells. GPRS carriers can also be configured to support the GSM
discontinuous transmission feature, defined for circuit switched traffic in an effort to
conserve MS battery life. In network operation mode 2 the network uses the CCCH
paging channel for both CS and GPRS paging.
Table 3-6 Cell reselection modes
Cell
reselection
mode
Control
element
Functionality
NC0
MS control
Normal GPRS MS control:

Autonomous cell reselection.
Enhanced
NC0
MS control
Functionality in NC0 mode plus:

BSS sends cell reselection commands to GPRS MS to
change cell reselection mode.
NC1
MS control

Autonomous cell reselection, MS sends measurement
reports to BSS.
Enhanced
NC1
MS control

BSS sends cell reselection commands to GPRS MS to
change cell reselection mode.
NC2
Network
control
MS sends measurement reports to BSS,

BSS sends cell reselection commands to GPRS MS,
BSS instructs MS to perform cell reselection.

02 May 2003
68P02901W01-M
335
PCU features
GSR6 (Horizon II)
GPRS radio channel allocation

Dynamic allocation of radio resources allows an operator to configure the radio resources
of a cell as dedicated circuit switched, dedicated GPRS, or switchable between circuit
switched and GPRS. This enables efficient use of air interface resources, and allows an
operator to tailor the cellular network to the packet data traffic requirements of the
operator.
This feature provides the flexibility for a cell supporting GPRS to allocate a given radio
resource to handle circuit switched voice/data or packet data, as required. A radio
resource can be configured as dedicated to circuit switched traffic, packet data traffic, or
switchable between the two. In the latter case, the traffic demands of the network
determine the type of traffic handled by the air interface timeslot. This provides the
operator with a degree of flexibility when configuring a GPRS capable network, and also
facilitates maximum utilization of resources. In a GPRS capable cell approaching
congestion, GPRS traffic can be given preference over the last switchable radio
resource, by setting a database parameter.
Originally the Motorola GPRS product offered the capability to configure up to eight
GPRS timeslots on a single carrier in a cell. The network operator can now configure
multiple GPRS carriers per cell for increased GPRS traffic handling capability to meet the
increase in packet data traffic and the expanding base of GPRS subscribers with
increased data throughput.
Medium access control mode dynamic allocation

Medium Access Control (MAC) includes the functions related to the management of the
common transmission resources. These include the packet data physical channels and
the radio link connections on packet data physical channels.
MAC supports the assignment of radio resources to MSs for transmission of GPRS
protocol data units (PDUs). In all cases, the network determines the assignment and
transmits this information for a given radio resource to all MSs sharing that resource.
The MAC also supports the provision of Temporary Block Flows (TBFs) allowing the
point-to-point transfer of signalling and user data between the network and an MS. A
temporary block flow is a physical connection used by the two entities to support the
transfer of GPRS protocol data units (PDUs) on packet data channels (PDCH). A TBF is
temporary and is maintained only for the duration of the data transfer.
Dynamic allocation mode

MAC operates in dynamic allocation mode. In this mode, three Uplink State Flag (USF)
bits are transmitted in every downlink block. Through these USF bits, the network
instructs one of the MSs sharing a timeslot to transmit data on the uplink. MSs monitor
the channel for their instruction to transmit. The advantage offered by dynamic allocation
mode is flexibility in the assignment of the air interface resource.
336

68P02901W01-M
02 May 2003
PCU features
GSR6 (Horizon II)
Support of MS classes
The GPRS network currently provides some form of support for all 29 multi-slot class
MSs, supporting multiple timeslot allocations in the UL and DL directions. An MS that
supports multiple UL timeslot allocation is always allocated a maximum of two UL
timeslots, for multi-slot classes mapped to GPRS classes 5, 6, 9, or 10. All other mapped
classes only allow allocation of one UL timeslot. Table 3-7 shows the mobile multi-slot
class mapping for all the GPRS multi-slot classes.
Table 3-7 MS multi-slot class mapping for all GPRS multi-slot classes
Multi-slot class
Supported as multi-slot class
01
01
02, 03
02
04
04
05
05
06, 07
06
08
08
09, 13
09
10 12, 14 29
10
GSM voice MSs are semi-duplex. The direction of speech information transfer alternates
rapidly, about 210 times per second, between the uplink and the downlink directions.
This rapid switching emulates a full duplex speech connection.
The basic GPRS MSs are semi-duplex as well. These MSs spend a significant
proportion of time switching directions, which significantly limits their total throughput.
For example, the most capable semi-duplex MS can receive 4 timeslots while
transmitting 1 timeslot, or receive 3 timeslots while transmitting 2.

02 May 2003
68P02901W01-M
337
PCU features
GSR6 (Horizon II)
Coding schemes
Four separate coding schemes, CS-1, 2, 3 and 4, are supported. These schemes provide
differing throughput rates, as shown in Table 3-8.
Table 3-8 GPRS coding scheme characteristics
Coding scheme
Throughput/T imeSlot
( k bits/s)
Effective approximate
convolutional coding rate
CS-1
9.05
1/2
CS-2
13.4
2/3
CS-3*
15.6
3/4
CS-4*
21.4
* switchable option only

All the coding schemes, except CS-4, provide a degree of forward error correction,
depending upon the prevailing RF conditions. Through support of these four coding
schemes, a higher throughput is enabled for MSs operating in those areas of the network
with excellent RF coverage, based upon reduced requirement for error correction. In
those areas of the network where RF coverage suffers, error correction can be boosted,
thereby maintaining a quality transmission, at a reduced throughput.
In the BSS architecture, the link which the GPRS data traverses from the channel coders
in the BTS to the PCU is currently implemented using 16 kbits/s TRAU-like links. These
links are carried over sub-rate switched E1 timeslots which have some signaling included
to ensure the link is synchronized between the channel coders and the PCU.
As additional protection and identification bits are included in the transmitted frame, there
is not enough bandwidth available on a 16 k bits/s link to carry CS-3 and CS-4. Thus a
new mechanism for associating two 16 k bits/s TRAU channels together, giving an
32 k bits/s TRAU, must be implemented to provide the bandwidth necessary to
implement CS-3 and CS-4.
Dynamic adaptation of coding schemes

This feature enables the network to change the coding scheme between MS
transmissions based upon the radio characteristics of the link.
During a GPRS transmission, the network monitors the characteristics of the radio link.
Based upon these measured characteristics, the network is able to change the coding
scheme in use in order to maximize throughput of the link. As an example, a MS with a
fairly high-quality radio connection can maximize throughput, with no error correction,
using CS-4. If the quality of the link deteriorates, the number of retransmissions required
would begin to increase due to the lack of of forward error correction. In this case, there
would eventually be a point at which the throughput enabled by CS-3 would exceed that
of CS-4, based upon the fact that the added error correction would reduce the number of
retransmissions. Similarly, if the link quality deteriorates still further, CS-2 would become
the better option.
338

68P02901W01-M
02 May 2003
PCU features
GSR6 (Horizon II)
Two phase packet access

GPRS supports two phase packet access. This feature allows an exchange of
information to take place between the MS and the network prior to assignment of
resources.
The purpose of the packet access procedure is to establish an uplink transmission to
support the transfer of packet data units from the MS to the network. The packet access
procedure can take place in either one or two phases. Two phase packet access avoids
contention. In this procedure, the MS requests a packet resource on the random access
burst. The network provides an immediate assignment of a single block, to which the MS
responds with its radio access capability (classmark) and MS ID, and the number of
octets of user data. Based upon this information, the network assigns a resource for the
uplink transmission.
One phase access

GPRS one phase uplink TBF access is an improvement over the two phase uplink TBF
access procedure.
In a GPRS one phase uplink TBF access, the MS initiates an uplink TBF by sending a
Random Access Channel (RACH) to the BSS. The RACH is received at the BTS, which
is then forwarded to the PCU. The PCU responds to the RACH with an Immediate
Assignment message containing an uplink assignment. The MS moves to the assigned
Packet Data (Traffic) Channel (PDTCH) and begins its uplink data transfer. This
procedure allows the MS to gain access to the network much quicker when comparing
against the two phase establishment procedure.
Enhanced one phase access

The enhanced GPRS one phase uplink TBF access procedure speeds up the one phase
packet access procedure even further.
The enhanced GPRS one phase access procedure improves PCU assignment of
resources for a one phase uplink TBF, by enabling the BTS to react more quickly to a
one phase RACH without forwarding the RACH to the PCU. This obviates RSL delay and
increasing RSL load. Depending on the RSL load, the RACH to Immediate Assignment
delay reduces by approximately 60 ms or more.
There are two versions of enhanced GPRS one phase access:
S
If the PCU has pre-allocated resources at the BTS and the pre-allocated timeslot is
not in the USF active state, the timeslot broadcasts the corresponding Uplink
Stage Flag (USF), once the MS has moved to the pre-allocated timeslot.
If the TS that was pre-allocated by the PCU is in the USF active state, the timeslot
broadcasts a valid USF continuously. Once an MS moves to the pre-allocated
timeslot (after the MS receives the Immediate Assignment message), the MS
receives the assigned USF immediately. This is the earliest possible opportunity
for the MS to transmit in the uplink. The only delay between the Immediate
Assignment message and the uplink data transmission is the MS reaction time.
Refer to Technical Description: BSS Implementation (68P02901W36) for a full description

of the differences between the two access methods.
02 May 2003
68P02901W01-M
339
PCU features
GSR6 (Horizon II)
Frequency hopping of PDCH

The GPRS network support frequency hopping of the packet data channel (PDCH).
Frequency hopping is one of the Motorola key techniques to improve capacity and quality
in a highly loaded GSM network. These same benefits are realized when frequency
hopping is implemented on GPRS carriers. For GPRS, all packet data channels
assigned to a single MS are included in the same frequency hopping system, which
specifies the frequencies over which the timeslots hop and the hopping sequence.
The principle of frequency hopping is as simple as changing the frequency used in
transmission at regular intervals. It has been included in GSM specifications mainly in
order to deal with two specific problems which can affect transmission quality:
S
Multipath fading.
Interference.
Multipath fading immunity can be increased by exploiting its frequency selectivity. By

using different frequencies, the probability of being continuously affected by fading is
reduced, so the transmission link quality is improved. This improvement is much more
noticeable for slow moving MSs.
Interference coming from neighbour cells transmitting the same or adjacent frequencies
can be reduced by using frequency hopping. This is because calls are moving through
different frequencies that are not equally affected by interfering signals.
Power control uplink/downlink

The power control feature enables power adjustment over the radio link based upon the
characteristics of the link.
Power control is supported over the radio interface on both the uplink and downlink.
Power adjustments are directed by the network based upon the measured characteristics
of the radio link.
Gb interface
The PCU interface/Gb interface provides connection between the BSS and the SGSN.
The Gb interface connects the BSS/PCU to the SGSN, allowing the exchange of
signalling information and user data. The Gb interface allows many users to share the
same physical resource. To facilitate cost-effective transmission, the Motorola GPRS
offering also supports infrastructure sharing, which allows the operator to carry
A interface (CS) and Gb interface (packet) traffic on a single E1 using the nailed
connections capability. These two features enable a cost-effective transmission solution
in a GPRS capable network. As GPRS traffic increases, it may become appropriate to
dedicate one or more E1 link lines to GPRS traffic and to accommodate this scenario, the
network also supports a direct connection between the PCU and the SGSN.
The Gb interface link layer is based on frame relay. Frame relay virtual circuits are
established between the SGSN and BSS, where PDUs from many users are multiplexed
on these virtual circuits. The virtual circuits may be multi-hop, and traverse a network of
frame relay switching nodes. Frame relay is used for both signalling and data
transmission.
340

68P02901W01-M
02 May 2003
PCU features
GSR6 (Horizon II)
PCU load balancing and sharing (Gb and BTS)

This feature provides high reliability through efficient resource management. It also
manages the movement of resources from one part of a BSS to another to meet varying
peak capacity requirements in a network designed primarily for coverage.
The primary objective of this feature is to economically support the use of multiple
timeslots per cell, with no delay penalty, in a BSS configured for coverage rather than
capacity. A coverage based GPRS network provides coverage over a large number of
cells, and assumes a low average throughput per cell. This feature allows a network to
effectively move or enable resources as needed throughout a BSS, to handle traffic
peaks.
Another objective of this feature is to provide high reliability. During periods when the
designated resource is not required due to a failure, the spare resource can be used to
manage peak loads. This is accomplished by means of load sharing of E1 link lines and
other key components within the BSS. A BSS/PCU can be configured to support a
maximum capacity of 270 active timeslots.
In the case of link line or equipment failures, the BSS provides load sharing of the
following resources:
S
E1 link lines on the BTS-BSC link.
E1 links on the BSS-PCU link.
PRP (RLC/MAC) boards within the PCU.
E1 link lines on the Gb (PCU-SGSN) interface.
MS flow control
MS flow control is implemented to regulate the flow of data from the SGSN to an MS by
sending a message containing the MSs logical identifier (TLLI), the current maximum
buffer depth (MS_Bmax) and the current buffer leak rate (MS_R). The flow of data is
then controlled on a per MS basis.
The BSS attempts a preset maximum number of times to send the message, in case it is
not acknowledged by the SGSN within the maximum time allowed. Successive
messages are sent a pre-defined delay (C) apart, unless the messages are
unacknowledged.
The MS flow control functionality complies to GSM 08.18.

02 May 2003
68P02901W01-M
341
PCU description
GSR6 (Horizon II)
PCU description
PCU purpose
The new BSS functionality for GPRS mainly resides at the Packet Control Unit (PCU).
The PCU includes the handling of frame relay, Network Services (NS) signalling, BSSGP
signalling, routeing of signalling messages, Radio Link Control (RLC), and Medium
Access Control (MAC) preload and transferring of user data.
User data is routed to the PCU via the Channel Codec Unit (CCU) uplink from the BTS to
the BSC and then over E1 to the PCU. At the PCU the RLC blocks are reformulated in
Logical Link Control (LLC) frames and forwarded to the SGSN.
BSSGP signalling and NS signalling occur between the PCU and the SGSN using frame
relay protocol. There is also signalling between existing functional process at the BSC
such as the between the Base Station control Processor (BSP) at the BSC and the PCU
via the E1 interface, as well as between the PCU and channel coders.
The purpose of the PCU is to perform a variety of functions and is responsible for the
following GPRS MAC and RLC layer functions:
S
LLC layer PDU segmentation into RLC blocks for downlink transmission.
LLC layer PDU re-assembly from RLC blocks for uplink transmissions.
PDCH scheduling functions for the uplink and downlink data transfers.
PDCH uplink ARQ functions, including RLC block ack/nak.
PDCH downlink ARQ function, including buffering and retransmission of RLC

blocks.
Channel access control functions, such as access requests and grants.
Radio channel management functions, such as power control, congestion control,

broadcast control information.
The functions inside the CCU are:

S
The channel coding functions, including Forward Error Correction (FEC) and
interleaving.
Radio channel measurement functions, including received quality level, received

signal level, and information related to timing advance measurements.
The BSS is responsible for allocation and de-allocation of radio resources. A PCU frame
can be transferred between the PCU and the CCU every 20 ms.
PCU management
The PCU is managed, including software download and operations, by the OMC-R as an
extension to the BSS. The OMC information destined for the PCU is passed through the
BSC. The Common Management Information Protocol (CMIP) interface is modified on
the BSC to include the management of the PCU as a new device.
A summary of this process is shown in Figure 3-10.
Figure 3-10 PCU managed from the OMC-R
OML
OMC-R
342
X.25
GSL
BSC

68P02901W01-M
64 kbit/s
E1
PCU
02 May 2003
PCU description
GSR6 (Horizon II)
PCU devices and equippage

Figure 3-11 shows the PCU devices and their equippage.
Figure 3-11 Device and equipment hierarchy for the PCU device
BSC
PCU
CAB 1
CAGE
PSP
DPROC
(PICP)
MSI
DPROC
(PRP)
MSI
MMS
MMS 2
GBL
(TRAU)
GDS
(TRAU)
GDS
(LAPD)
GDS
GSL
NOTES:
1
2
indicates automatically equipped devices, when a PCU is equipped.

indicates automatically equipped device, when an MSI is equipped.

02 May 2003
68P02901W01-M
343
PCU architecture
GSR6 (Horizon II)
PCU architecture
Introduction to PCU architecture
The PCU hardware is off-the-shelf equipment that is based upon the Compact PCI
(cPCI) standards. The cPCI is a set of standards that define a common chassis, power
supplies, and processor boards.
There are four cPCI board types:
S
The Master Processor (MPROC).
The Bridge (PPB).
The Data Processor (DPROC) consisting of:
The Packet Interface Control Processor (PICP).
The Packet Resource Processor (PRP).
The PICP and PRP boards may initially be the same hardware platform (the
DPROC), but in the long term they may be different hardware platforms.
There is a single PCI Mezzanine Card (PMC) module currently planned, the dual E1
PMC. These PMC modules are installed on the PICP and PRP boards.
The PCU also supports load sharing (fault tolerance).
MPROC
The MPROC is the system slot processor that is responsible for bus arbitration and CPCI
clock generation. It contains interface and BSSGP protocol functions, and is called the
PCU System Processor (PSP). Only one PSP may be equipped at a PCU.
MPROC board (PSP)

The MPROC is the main control processor for the system, and works in conjunction with
the PPB. It acts as PCI system host, and in conjunction with the PPB supports hot
removal control for all board slots. It performs resource allocation, fault management,
and gateway management functions (such as control of allocation of cells to PRP
boards). These functions comprise the PSP, which resides on the MPROC.
The MPROC requires a high-performance processor system such as the 266 MHz
MPC750 with an 83 MHz bus for the memory subsystem. A minimum of 128 M bytes of
DRAM is supported, upgradeable to 256 Mbytes.
Bridge (PPB)
The bridge, also referred to as the PCI to PCI Bridge (PPB), allows an MPROC to be
linked to a separate bus. The PPB and MPROC are paired boards.
The PPB allows the redundant operation of the system host PROC board, and gives the
host PROC access to all boards in the system. It supports control of hot swap for all
boards, and a communication link between bridge boards to allow checkpointing and
heartbeat messages between MPROC boards. This allows migration to a fully hot swap,
redundant, high-availability system, including hot standby/load sharing between MPROC
boards in the future, if required.
344

68P02901W01-M
02 May 2003
PCU architecture
GSR6 (Horizon II)
DPROC
The DPROC boards are non-system slot boards that have two PMC sockets and can
host two different functions. The DPROC can be configured as either a PICP or a PRP.
If configured as the PICP, the DPROC contains up to two PMC modules to provide the
E1 interfaces. The E1 interface can support the Gb interface or the GPRS Data Stream
(GDS) interface, including the GPRS Signalling Link (GSL).
If configured as a PRP, the DPROC performs air interface scheduling and the PMC
sockets can be used to support TRAU GDS devices. A single processor can support a
pool of 120 radio timeslots, of which 30 radio timeslots can be active at any one time.
DPROC (PICP)
The DPROC (PICP) is used for all network interfacing functions to the outside world,
such as the SGSN and BSC. The PICP has up to two interface modules installed and
data to/from these interfaces passes through the on-board processor. This processor
has different functions dependent on the interface type, but includes features such as
packet routeing on an incoming SGSN link, and packet scheduling to an outgoing SGSN
link.
DPROC (PRP)
The DPROC (PRP) is the processor where all of the radio related processing takes
place. Each of the GPRS channels is routed to a PRP, which performs all of the
RLC/MAC processing, air interface scheduling, and frame synchronization on BTS facing
channels.
The performance required from this board is such that it supports a minimum of 30 active
air interface timeslots, with the ability to monitor another 90 timeslots. A future tripling of
this capacity is envisaged. The PRP maintains synchronization to the air interface by the
exchange of the PCU-CCU frames (which is transmitted even on inactive timeslots).

02 May 2003
68P02901W01-M
345
PCU architecture
GSR6 (Horizon II)
E1 PMC module
The E1/T1 interfaces to both the BSS and the SGSN are provided by PMC modules that
reside on a PMC carrier board. The PMC board has a MPC 750 processor and two PMC
sites. These PMC modules are currently available with dual E1 ports and an 860 PPC
processor onboard.
This onboard processor is used for frame relay termination on the Gb link and contains
a small process to route the Gb interface signalling (control) information to the Gb
manager on the MPROC. E1 links are also used to interface the PCU to the BSC for
transfer of signaling information via LAPD protocol, as well as serial user data in the
remaining timeslots. The clock on the PMC module is free run and not synchronized to
an external signal from E1/T1 interface. The memory on the PMC module is used for the
code object storage of the frame relay protocol as well as the buffers which are
necessary for both the transmit and receive sides of the frame relay link.
The E1 interface can support the Gb interface or the (TRAU) GPRS Data Stream (GDS)
interface and (LAPD) GDS, including the GPRS signalling link. The GSL is a 64kb/s TCL
and is used to manage and control the PCU/BSC system. Multiple GSLs can be used to
manage and control the PCU/BSC system. Figure 3-14 shows a system where E1
PMCs are used to connect the TDM data to the BSC. The MSIs used for these links can
be equipped in any chassis of a multi-chassis BSC system.
A PMC module can support only one of the following:
S
(LAPD) GDS.
(TRAU) GDS.
Gb interface.
Additionally, if one span of the PMC module is used for a (TRAU) GDS, then the other
span is unusable.
Chassis
The chassis houses a maximum of 16 cPCI boards, with the ability to support redundant
host processors. The power supply system is part of this OEM solution. The host
processor, redundant host processor, and their associated bridge boards occupy four of
the slots, leaving 12 generic slots for the remaining boards. Hot removal of all boards is
supported.
The PCU is an additional chassis that is collocated with any BSC that supports GPRS
functionalityand interfaces to the BSC, utilizing E1 PMC modules on a DPROC (PICP)
board. This requires corresponding Multiple Serial Interface boards (MSIs) to be present
in the BSC.
The chassis is a19-inch rack-mounting module supporting sixteen 6U PCI slots, four of
these slots are taken by the two MPROC/bridge pairs for redundant systems. This
leaves 12 generic slots that can be populated by any combination of PICP, and PRP
boards with their associated PMC modules. It supports front access for all replaceable
modules, redundant/load sharing PSU system, and status LEDs. The interconnect
cabling is routeable from the rear, front, or bottom of the chassis.
Fault tolerance
The PCU supports load sharing across the PRP, PICP, and E1 PMC. The hardware can
be N+M redundant (and would generally be equipped as N+1 when load sharing is
active), but software loads share across all installed boards, with any failures causing a
loss in total capacity capability. The operator determines whether the hardware is
provisioned for greater capacity than required, such that failures do not affect the system
capabilities.
346

68P02901W01-M
02 May 2003
PCU interfaces
GSR6 (Horizon II)
PCU interfaces
Introduction to GPRS BSS interfaces
The Motorola GPRS BSS includes the:
S
Base Station Controller (BSC).
Base Transceiver Station (BTS).
Operations and Management Centre-Radio (OMC-R).
Packet Control Unit (PCU).
Figure 3-12 shows these components and their interfaces.
Figure 3-12 BSS functional blocks

SGSN
RXCDR
A
X.25
OMC-R
Gb
BSC
PCU
Abis
BTS
Um
KEY:
MS
optional
The BSC supports the following interfaces as illustrated in Figure 3-12:

S
BSC-BTS (Abis).
BSC-OMC-R (X.25).
BSC-RXCDR (A).
BSC-PCU.
PCU-SGSN (Gb).
This section defines the interfaces the PCU has with other elements of the GPRS.

02 May 2003
68P02901W01-M
347
GSR6 (Horizon II)
PCU interfaces
PCU-BSC interface
The PCU-BSC interface carries user data and radio resource management information,
called Radio Link Control/Medium Access Control (RLC/MAC) packets, between the PCU
and BTS. The GPRS Signalling Links (GSL) carry signalling information on 64 kbit/s E1
timeslots between the PCU and BSC.
A GDS carries the packet data on 16 kbit/s E1 timeslots between the PCU and BSC.
An RSL carries the signalling information on 16 kbit/s or 64 kbit/s E1 timeslots between
the BSC and BTS.
Another 16 kbit/s E1 TS or channel carries the TRAU-like framed data between the BSC
and BTS.
A BCCH or CCCH carries the signalling information between the BTS and MS.
Between the BTS and MS, the packet data is carried over CS1, CS2, CS3 or CS4
encoded PDCHs (see Figure 3-13).
Figure 3-13 Data and signalling paths between the PCU and MS
GSL
64 kbit/s TS
LAPD
PCU
BSC
Um
BCCH
CCCH
BTS
MS
SIGNALLING
SIGNALLING
SIGNALLING
SIGNALLING
DATA
DATA
DATA
DATA
GDS
16 kbit/s TS
348
RSL
16/64 kbit/s TS
LAPD
16 kbit/s
TRAU

68P02901W01-M
Um
PDCH
CS1, CS2,
CS3 or CS4
02 May 2003
GSR6 (Horizon II)
Figure 3-14 provides more detail of the E1 physical links.

Figure 3-14 PCU to BSC connection utilizing E1 links (four shown)
E1 LINKS
The number of MSI links

needed is dependent on the
PCU capacity. All MSIs can
reside in a single BSC
chassis even in expanded
systems.
DPROC
(PICP)
E1PMC
MSI
MSI
DPROC
(PICP)
E1PMC
BSC
PCU
E1 LINKS
Gb interface
The Gb traffic, user data and signalling, can take different paths between the PCU and
SGSN depending upon the needs of the voice and data networks. In all cases, the Gb
traffic is always carried over 64 kbit/s E1 channels. See Figure 3-15 for a summary of the
three connection methods. Option C, routeing a connection through the transcoder, is a
convenient way to bring GPRS traffic from multiple PCUs to a single SGSN.
Figure 3-15 Data and signalling paths between the PCU and SGSN
ALL INTERFACES ARE Gb nx64kbit/s E1 CHANNELS LAPF
PCU
PCU
PCU
BSC
BSC
RXCDR
SGSN
OPTION A: DIRECT
SGSN
SGSN
OPTION B: BSC
PASS-THROUGH
OPTION C: BSC AND

RXCDR
PASS-THROUGH

02 May 2003
68P02901W01-M
349
PCU system and control functions
GSR6 (Horizon II)

System and control functions
The Packet Control Unit (PCU) performs:
S
Radio functions.
GPRS network functions.
The PCU has interfaces to:

S
An OMC-R.
BSC.
SGSN.
Radio functions
The PCU is responsible for the following GPRS MAC and RLC layer functions, as
defined in GSM 03.64:
S
LLC layer PDU segmentation into RLC blocks for downlink transmission.
LLC layer PDU re-assembly from RLC blocks for uplink transmissions.
PDCH scheduling functions for the up-link and downlink data transfers.
PDCH up-link ARQ functions, including RLC block ack/nak.
PDCH down-link ARQ function, including buffering and retransmissions of RLC

blocks.
Channel access control functions, such as access requests and grants.
Radio channel management functions, such as power control, congestion control,

broadcast control information.
Interacting with existing BSS software for allocation/de-allocation of radio

resources for GPRS.
Multiplexes data and signalling onto BSC facing E1 links.
SGSN functions
The PCU and the SGSN use frame relay and the Base Station System GPRS Protocol
(BSSGP) protocols to exchange user data and signalling information. The frame relay
network can be point-to-point or an actual network. Signalling data, used for flow control
and congestion management, is exchanged between the PCU and SGSN.
350

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
PCU processes
There are three PCU functional areas:
S
PRP processes.
Gb processes.
GWM processes.
PRP processes
The PRP processes are:
S
The Packet Resource Manager (PRM):
Performs all RLC/MAC functions.
Realises UL/DL power control and timing advance.
The DownLink Segmentator (DLS) segments LLC frames into RLC data blocks to
be transmitted over the air interface
The UpLink Concatenator (ULC) concatenates RLC data blocks into LLC frames.
The SYstem information Manager (SYM) builds and sends GPRS system
information messages over the BCCH.
CCCH Paging Manager (CPGM) processes the paging messages coming from the
SGSN to the BSC/BTS.
Gb processes
The Gb processes are:
S
The Gb router (GR) routes incoming BSSGP PDUs from the SGSN to the relevant
SW process in the PCU.
The Flow control Buffer Manager (FBM) controls buffer capacity for each cell and
each mobile so that the incoming data from the SGSN matches the air throughput.
The Gb Manager (GBM) manages the state of all cell and signalling links between
the PCU and the SGSN.
The Gb Transmit Manager GTM) collects all UL frames from various ULCs and
sends them on the appropriate NS-VC.
The Network Service Tester (NST) periodically tests all alive Network
Service-Virtual Circuit (NS-VC) on a PICP board.
The Frame Relay (FR) performs the frame relay protocol functions.

02 May 2003
68P02901W01-M
351
352

68P02901W01-M
GSR6 (Horizon II)
02 May 2003
Chapter 4
OMC-R Overview

02 May 2003
68P02901W01-M
41
GSR6 (Horizon II)
42

68P02901W01-M
02 May 2003
Introducing the Motorola OMC-R
GSR6 (Horizon II)

Definition of OMC-R
A simplified GSM network is shown in Figure 4-1. The OMC-R supports the day to day
operations and maintenance of network components within a GSM network. It also
provides a configuration interface to set up and modify the radio part of the system and
to model the network to an interactive graphical map display.
NOTE
The zoom feature may be used while working on-line to make

the text easier to read. For information regarding on-line help
click on the on-line help icon located on the OMC-R front panel.
The OMC-R front panel section can be found later in this
chapter.
Figure 4-1 The OMCR in a GSM system
Mobile
Switching
Centre
MSC
OMC-S
(Switch Part)
Operation &
Maintenance Centre
(Radio Part)
Remote
Transcoder
RXCDR
Base
Station
System
BSS
BTS
BTS
Base Station
Controller
BSC
BTS
MS
OMC-R
Packet Control Unit

PCU
(optional GPRS interface)
BTS
MS
Base Transmitter
Stations
MS
Mobile Stations
(Phones)

02 May 2003
68P02901W01-M
43
GSR6 (Horizon II)
Naming conventions
The Operations and Maintenance Centre (OMC) designed to manage the radio part of
the system is referred to as the OMC-Radio (OMC-R) in this manual to prevent confusion
with other types of OMC.
A Network Element (NE) is a specific term used to represent various network items
including the BSS, RXCDR, MSC, OMC-R and OMC-S, but not lower level items, such
as SITE, PCU, DynetGroup and devices.
The BSS is a NE which includes the Base Station Controller (BSC) and Base Transceiver
Station (BTS) functions and can also include a local transcoding function.
S
site - normally refers to one or more physical pieces of equipment at a BSS

location.
SITE refers to a configuration object (as defined in the Navigation Tree).
Communication with GSM network

The Motorola OMC-R communicates with the GSM network using the X.25
communications protocol to exchange Operation and Maintenance (O&M) data with the
BSSs and speech Transcoders (RXCDRs or XCDRs) via a Private or Public Switched
Packet Data Network (PSPDN). The Transcoder (XCDR) is the digital signal processing
equipment required to perform GSMdefined speech encoding and decoding. In terms of
data transmission, the transcoder interfaces the 64 kbit/s PCM in the land network to the
13 kbit/s vocoder format used on the Air Interface. The Remote Trancoder (RXCDR) is
used when the transcoding is performed at a site away from the BSC, which is at or near
the MSC. This enables 4:1 multiplexing in which the transcoded data for four logical
channels is combined onto one 64 kbit/s link, thus reducing the number of links required
for interconnection to the BSCs.
An optional OSI Processor contains the Mediation Device (MD), Security Application
(SA) and File Transfer and Access Management (FTAM). The MD (which handles the Q3
interface) allows the OSI Processor to communicate between the Network Management
Centre (NMC) and OMC-R for network configuration, events and alarms. The optional SA
software allows the OSI Processor to communicate with a Security Management Centre
(SMC). The optional FTAM application is used with the SA function to transfer files from
the OSI to the SMC.
DataGen is an optional UNIX platform which can either be run from the OMC-R LAN or in
standalone mode. Datagen is designed to support large offline changes to a BSS
configuration database which can then be downloaded to the BSS when required.
44

68P02901W01-M
02 May 2003
OMC-R network management functions
GSR6 (Horizon II)

Fault management
Fault management provides the facility to change the status of any device using fault
handling procedures. From the OMC-R, the GSM network operator can react to changes
in the network and re-configure the site by taking devices in or out of service as required,
thus maintaining continuity of service to mobile phone users. Fault management tasks
can be performed from the map, the alarm window, Navigation Tree and through
contained devices.
Event/alarm management
A primary function of an OMC-R is to maintain the quality of service to customers/users
of the GSM network by monitoring the state of Motorola equipment in the network. Event
or alarm messages containing information on the state of the network, devices and links
in the system are sent, via the X.25 network, to the OMC-R. These messages notify the
operators of any potential problems occurring in the network. There is the optional Alarm
notification via Paging feature which automatically notifies key personnel of certain alarm
or state changes.
Operators can filter and select the way in which alarms are displayed and handled; for
example, alarms which have been handled, but not yet cleared, can be deferred. To
assist an operator in diagnosing specific events (and alarms) in the network, the Network
Availability Monitor provides an overview and allows trends to be identified. An optional
Network Health Analyst (NHA) provides a means by which operators can move from
being purely reactive to a more proactive role by observing a combination of events,
statistical information and configuration data that notifies them of network problems
before any faults are raised.
Performance management
Performance management provides collection and reporting of network performance
statistics. The OMC-R collects, processes and stores performance statistics on the
different NEs in the network, and provides reporting facilities for the presentation and
printing of the processed statistics. These statistics can be then used to analyse network
performance and aid long term planning.
Configuration management
The OMC-R provides the configuration management facilities for a scaleable system that
can cater for an expanding GSM network. The System Processor can be configured for a
variety of expandable traffic channel capacities on the same basic platform. The OMC-R
system allows customers to expand their network operations and maintenance support in
line with their business growth and provide orderly migration for existing users and rapid
deployment for new users. Network Expansion and Cell Parameter Import/Export under
the control of the OMC-R enables rapid and widescale network expansion. The OMC-R
also includes the Call Trace function. Optional tools may also include the Intelligent
Optimisation Product (IOP) and the Motorola Analysis and Reporting System (MARS).
Configuration management also provides centralized software load management,
database load management and the management of operating parameters. The OMC-R
provides facilities to initiate uploads and downloads of NE operating software, or to
back-up or download configuration databases for the different NEs. The OMC-R also
provides the facilities to reconfigure the operating parameters of NEs using the remote
login facility and facilities to optimize via the GUI.
Network configuration from the OMC-R also includes the optional Packet Control Unit
(PCU) interface to the GPRS system to incorporate the packet switching logical
connections and devices.
02 May 2003
68P02901W01-M
45
GSR6 (Horizon II)
Load management
Load Management forms part of the Configuration Management and provides the
operator with a central location to remotely load all the NEs with the latest compatible
version of operating software. New software loads are installed at the OMC-R and later
downloaded to the NEs under the OMC-Rs control.
46

68P02901W01-M
02 May 2003
The OMC-R in GSM network management architecture
GSR6 (Horizon II)
The OMC-R in GSM network management architecture

Network hierarchy
The position of the OMC-R within the GSM network management hierarchy, is shown in
Figure 4-2.
Figure 4-2 GSM network management architecture
FIVE-LAYER TMN MODEL (DEFINED IN ITU M.3010)
BUSINESS
MANAGEMENT
PHYSICAL IMPLEMENTATION
OF THE LOWER THREE LAYERS
SERVICES
MANAGEMENT
NETWORK
MANAGEMENT
NMC
NETWORK
ELEMENT
MANAGEMENT
OMC-R
OMC-R
NETWORK ELEMENT
LEVEL
NE
NE
NE
NE
NE
NE
Network levels
Operation and Maintenance (O&M) management of the BSS and RXCDR can be
performed at several network levels:
Local level
Local level monitoring, where reconfiguration, and software loading can be performed by
connecting a personal computer to the BSC or RXCDR (Remote Transcoder).
Regional level
The OMC-R provides facilities for performing functions on NEs at a regional level.
Built-in alarm and event management, configuration management, and fault handling
facilities enable operators at remote OMC-R sites to manage O&M in a consistent and
standardized manner. The OMC-R provides monitoring and control for a number of BSSs
in a specific geographical area. The prime function of the OMC-R, is to maintain the
quality of service to customers/users by monitoring the performance of the radio
equipment. Procedures are provided by which the radio resources can be dynamically
reconfigured, and faults rectified from a single remote location. Additionally, the OMC-R
provides databases for O&M data and system performance statistics.
Top level
The top level of network management is implemented by the Network Management
Centre (NMC). An NMC could perform O&M functions at a network-wide level with
OMC-Rs as its subordinates.
02 May 2003
68P02901W01-M
47
The OMC-R system
GSR6 (Horizon II)
The OMC-R system

OMC-R content
The OMC-R system configuration is shown in Figure 4-3. It is suitable for GSM networks
with low-end (10k) to high-end (45k) traffic channels (TCHs). Each processor is a
complete UNIX system, comprising the following:
S
A system processor.
A database/memory to store configuration settings
GUI clients(i.e. the Graphical User Interface used by operators ).
One or more GUI servers.
A laser printer.
The system processor

The system processor is a UNIX system that runs the OMC-R application software to
handle all O&M communications with the NE. It processes all incoming events, alarms,
uploads/downloads, and performance statistics. It also processes the setting up of
remote login sessions to different NEs. The system processor contains a database based
on an INFORMIX Database Management System (DBMS), configured for storing
performance statistics and subscription lists, enabling operators to monitor incoming
events and alarms.
The system processor contains the Configuration Management Information Base (CM
MIB) holding all the network and map configuration data.
GUI clients and servers

The remainder of the OMC-R is made up of SUN ULTRAs or SPARCstations, and is
primarily concerned with running the OMC-R operator Graphical User Interface (GUI)
client and server processes, known as the OMC-R GUI Servers and GUI clients. The
GUI server handles the more intensive GUI processing tasks and network messages
from the system. The GUI client handles the operator display and data entry tasks and
sends information requests to the GUI server. The GUI server responds by sending or
receiving information or by performing the required action.
Typically the OMC-R configuration contains several SPARCstation 5s, which run the GUI
clients. The faster ULTRA or SPARCstation 20 can run either the GUI server or client
processes.
Optional processors
Optional processors, such as those for OSI stack, remote login, and DataGen can be
included into the basic OMC-R configuration. The processors that can be used are
SPARCstation 20s or ULTRAs. The Network Health Analyst (NHA) can be used on a Sun
Enterprise 3000 or 3500, and WWW Server on a SPARCstation 5.
48

68P02901W01-M
02 May 2003
The OMC-R system
GSR6 (Horizon II)
Figure 4-3 Typical scaleable OMC-R system configuration

TO GSM
NETWORK
SUN HSI/S card (4-port HSI / interface )
Sunlink X.25 package

SYSTEM
PROCESSOR
X.25
OMC-R
Application
Software
System
Processor
LOCAL AREA NETWORK (LAN)
CM
MIB
Ultra 5
Ultra 200E
SUN SPARCstation 5*
OMC-R
DATABASE
(DBMS)
CONSOLE
FOR
OMC-R SYSTEM
ADMINISTRATOR
Applix
cm_mib
GUI PROCESSOR
GUI
GUI
GUI PROCESSOR
GUI
Workstation
Workstation
SUN SPARCstation 5*
WWW SERVER
PROCESSOR (optional)
SUN SPARCstation 5*
OSI PROCESSOR (G3)
(optional)
SUN SPARCstation 20 or
SUN Ultra 200E*
Network Health Analyst
PROCESSOR (optional)
NHA processor*
Laser
Printer
Lexmark Optra RN+

printer (with software)
*Optional

02 May 2003
68P02901W01-M
49
OMC-R configuration summary
GSR6 (Horizon II)
OMC-R configuration summary

Scaleable configuration details
A summary of the scaleable OMC-R configuration is as follows:
High-capacity TCH scaleable OMC-R

The high-capacity TCH configuration of the scaleable OMC-R provides support for
45,000 TCHs with a maximum of 120 NEs.
The GUI interface is provided on a SPARCstation 5/20 machine or a SUN ULTRA. One
of the high end machines must be configured as a GUI server. A second can be
configured as a GUI server when the two will share the load of the clients for
redundancy purposes should one server fail. Up to 10 GUI interfaces may be used in the
OMC-R system. The GUI servers run the GUI sessions while the GUI clients run the
display software only. The total number of GUI sessions supported is 10, as on the
standard OMC-R. Each processor can support one GUI session.
Mid-capacity TCH scaleable OMC-R

The mid-capacity TCH configuration of the scaleable OMC-R provides support for 30,000
TCHs with a maximum of 120 NEs.
The GUI interface is provided on a SPARCstation 5/20 or SUN ULTRA 5/1 machine. A
second ULTRA 5 or ULTRA 1 machine must be be configured as a GUI server.
SPARCstation machines can be added as GUI clients. The total number of GUI
sessions supported is 10, as on the standard OMC-R. Each machine can support one
GUI session.
Low-capacity TCH scaleable OMC-R

The minimum configuration of the scaleable OMC-R provides support for up to 5,000 or
10,000 TCHs with a maximum of 15 NEs.
For very small systems the GUI interface is provided on an ULTRA 200E or ULTRA 5/1
machine. A second ULTRA 5/1 machine must be be configured as a GUI server.
SPARCstation 5 machines can be added as GUI clients. The total number of GUI
sessions supported is 5. Each machine can support one GUI session.
410

68P02901W01-M
02 May 2003
The OMC-R user interfaces
GSR6 (Horizon II)

User interfaces
The OMC-R has two user interfaces to operate the OMC-R system:
S
The Graphical User Interface (GUI).
Command line interface.
The OMC-R GUI provides a Graphical User Interface (GUI), based on the Open
Software Foundation Motif (OSF-Motif).
GUI interface
The GUI presents the user with a Front Panel displaying icons that represent all the
modules of the OMC-R, shown in Figure 4-4. A smaller expert front panel, which does
not have icon titles, is also available for experienced personal. The expert front panel
prevents desktop clutter and is shown in Figure 4-5.
The OMC-R GUI enables operators to interact with the OMC-R and to carry out network
management functions. All maintenance, network reconfiguration, troubleshooting, and
network administration, apart from equipment repair and replacement, can be executed
through a single interface.
Command line interface

The UNIX-based system utilities are executed at the command line of an Xterm window
which is opened from the GUI Front Panel.

02 May 2003
68P02901W01-M
411
GSR6 (Horizon II)
OMC-R front panel

The GUI front panel contains icons that represent different modules of the OMC-R GUI.
A summary of the current alarms in the network is always displayed on the right hand
side of the GUI front panel. Figure 4-4 shows the OMC-R front panel and Figure 4-5
shows the expert OMC-R GUI front panel.
Figure 4-4 The OMC-R GUI front panel

1
8
2
9
16
15
14
13
12
11
10
Figure 4-5 The Expert OMC-R GUI Front Panel
412

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Table 4-1 describes the icons on the OMC-R GUI front panel (see Figure 4-4).
Table 4-1 Front panel icon description
Number
Description
1.
Operator (user name)
2.
Access to OMC-R console
3.
Access to configuration management
4.
Access to event management
5.
Access to performance management
6.
Access to load management
7.
Access to find facility
8.
Alarm summary
9.
Incoming alarms display icon
10.
Front Panel exit button
11.
Access to OnLine Help
12.
Access to UNIX command line
13.
Access to administrative and scheduled functions
14.
Access to system event logs
15.
Remote access to BSS or RXCDR
16.
Access to network maps

02 May 2003
68P02901W01-M
413
The command line interface
GSR6 (Horizon II)
The command line interface

UNIX-based utilities
UNIX-based utilities are provided to give additional network management functionality to
the OMC-R GUI in the following functional areas:
414
Remote login.
Synchronization of time with the OMC-BSS.
Event management.
Event log processing, searching and filtering event logs.
Performance management.
NE database management.
System administration utilities.

68P02901W01-M
02 May 2003
The OMC-R in a GSM network
GSR6 (Horizon II)

A typical GSM network
A typical GSM network (900 MHz, 1800 MHz or 900/1800 MHz), is shown in Figure 4-6.
It consists of an Operations and Maintenance Centre Radio (OMC-R) and one or more
Network Elements (NE or nodes), which may be a Base Station System (BSS), a
Remote Transcoder (RXCDR), Mobile Switching Centre (MSC) or Cell Broadcast Centre
(CBC).
Figure 4-6 The OMCR in a GSM network

MSC
O&M DATA FROM

BSS1, BSSn, &
RXCDR
64 kbit/s
64 kbit/s
X.25
X.25
64 kbit/s
VOICE
TRAFFIC
FROM
BSS1 AND
BSSn
CBC
OMC-R
2 Mbit/s link
64 kbit/s
2 Mbit/s link
RXCDR
64 kbit/s
4x16 kbit/s
TRAFFIC 64 kbit/s
O&M DATA
64 kbit/s
CBL
64 kbit/s
MESSAGE INFO
4x16 kbit/s
TRAFFIC
CBL
64 kbit/s
O&M DATA
BSSn
2 Mbit/s link
BSS1
BSC
BSC/BTS
2 Mbit/s link
MS
BTS
MS
16 kbit/s traffic
BTS
2 Mbit/s
link
BTS
MS
MS
BTS
MS
BTS
MS

02 May 2003
68P02901W01-M
415
GSR6 (Horizon II)
OMC-R functions
The OMC-R performs the following functions:
S
Direct management of BSS and RXCDR and the links between them.
Management of the NE devices associated with the links (on the RXCDR side)
between the MSC, the BSSs and RXCDRs. This is all done using the O&M data
packets sent to/from the NE.
Monitoring of events and alarms, performing fault handling, NE re-configuration,

NE software uploading and downloading, and performance data collection and
reporting for all the NE under its control.
Provides a centralized facility for network management of up to 120 NEs with up to

45,000 traffic channels for the Scaleable OMC-R.
RXCDR functions
The RXCDR routes the O&M data packets between the BSS and the OMC-R, and traffic
channels (voice) between the BSS and MSC. The O&M data packets are routed between
the OMC-R and the RXCDR using X.25 packet switching.
Each 2 Mbit/s link between the BSSs and the RXCDR typically consists of two 64 kbit/s
O&M links plus 120( ( 30 x 64 kbit/s) x (64 kbit/s) ) traffic channels.
The RXCDR is located between the MSC and the BSS, usually located in the same area
as the MSC. This is the most efficient arrangement, as the primary feature of the RXCDR
is that it converts the 64 kbit/s PCM output of the MSC to a 16 kbit/s rate required for
transmission over the air interface (between the BSS and the MS). Thus, four 16 kbit/s
channels from the RXCDR can be fitted on each 64 kbit/s terrestrial circuit. In this way,
each 30 channel 2 Mbit/s PCM link can carry 120 GSM-specified channels with obvious
cost savings.
Configurations
A BSS consists of a Base Site Controller (BSC) and one or more remote Base
Transceiver Stations (BTS). Every BTS must be physically connected to its controlling
BSC using a 2 Mbit/s link. A BTS can also be located in a BSC cabinet, thus creating a
collocated BSC/BTS, usually connected using a LAN. A BSS configuration may have all
BTS directly connected to the controlling BSC (spoke connection) or the BSS may be
connected via another BTS (daisy chaining). A BTS may also have more than one
connection to its controlling BSC for redundancy. The GPROC2 (second generation
processor board) allows the BSC to support 100 sites.
416

68P02901W01-M
02 May 2003
BSS and RXCDR configuration (SITES)
GSR6 (Horizon II)
BSS and RXCDR configuration (SITES)

BSS configuration
In a GSM network, the BSS is configured to contain a series of one or more SITES.
SITE 0 always contains the BSC equipment; it may also contain BTS equipment Sites
1 to 100 contain only BTS equipment, they cannot contain the BSC.
Thus there are three possible types of BSS site:
S
BSC site This is a BSS with all BTS functions at remote locations. This BSC also
provides the interface between the MSC and the remote BTS sites.
Remote BTS site This site forms the remote part of a BSS which is controlled by
the BSC site. The BSC provides the interface with the MSC.
Example
An example configuration is shown in Figure 4-7.
Figure 4-7 The naming convention and physical links of BSS

REDUNDANT LINK 2 Mbit/s TERRESTRIAL OR MICROWAVE LINK
SITE 1 (BTS)
SITE 0 (BSC)
SITE 2 (BTS)
SITE 3 (BTS)
MSI
BOARD
2 MMS
PORTS
2 Mbit/s
link
2 Mbit/s TERRESTRIAL OR MICROWAVE LINK TO/FROM RXCDR
RXCDR configuration
An XCDR placed at the MSC is known as a Remote Transcoder (RXCDR), and is
regarded as a separate NE (or node). Sometimes the transcoding functionality is located
within a BSC. In the example above, (Figure 4-7), the transcoding hardware is regarded
as a subset of the BSS SITE 0 configuration.

02 May 2003
68P02901W01-M
417
NE device containment
GSR6 (Horizon II)
NE device containment
Containment relationship
There is a containment relationship between each entity in the GSM Network that is
modelled at the OMC-R. This hierarchical structure is known as the Containment Tree.
Each entity is contained within a container, which may consist of more than one entity
known as containees. For example, an MMS (the Multiple Serial interface link) is
contained within an MSI (the Multiple Serial Interface board), which, in turn, is contained
within a SITE. This containment relationship is used for logical naming, configuration
purposes and event management.
For more details on containment relationships refer to manual Installation &
Configuration: GSM System Configuration (69P02901W17).
Ports
There are two MMS ports on an MSI board. There can be up to 48 MSI boards in a SITE
and up to 100 SITEs in a BSS. An instance of an MMS can be uniquely identified to an
MSI/XCDR card as follows:
Example
MMS port 1 on MSI board 2 in SITE 0 would be named MMS 2 1 X. The first digit is
the parent MSI card, the second refers to the port number and the third is not required.
418

68P02901W01-M
02 May 2003
Site configuration
GSR6 (Horizon II)
Site configuration
CELL resources
In the Motorola implementation of GSM, a single BTS consists of one or more cabinets
and controls one or more CELLs. The Motorola term CELL is equivalent to the GSM term
BTS, since Motorola BTS sites can contain more than one cell. GSM requirements
specify one cell per BTS.
The different related resources of a CELL configuration are shown in Figure 4-8.
Figure 4-8 Site configuration

SITE
Radio
Frequency
CELL
Handover
Control
Neighbour
Power
Control
DRI Group
RTF Group
DRI
RTF
BTS hardware relating to traffic

A BTS cabinet would contain one or more radio units.
Each CELL is serviced by one or more carriers, each of which is serviced by a single
radio unit. Each carrier has eight TDMA timeslots.
BTS software relating to traffic

From a software perspective, a BTS contains the following software devices/functions:
S
Digital Radio Interface (DRI) Groups, which contains DRIs.

There is one DRI Group per cell on each site for redundancy purposes.
Receive Transmit Function (RTF) Groups, which contain a number of (RTFs).

There is one RTF Group per cell on each site for redundancy purposes.
CELLs.

02 May 2003
68P02901W01-M
419
DRI/RTF groups - transceiving
GSR6 (Horizon II)
DRI/RTF groups - transceiving

Transceiving functionality
Motorola has implemented transceiving functionality using the DRIs and RTFs. This
provides the radio carrier which, in a GSM digital system, consists of eight TDMA
timeslots. These digital channels carry speech and various control data. One of the more
important of these control channels is the Broadcast Control Channel (BCCH). Every
CELL must have at least one BCCH.
Types of RTF
RTFs are used to carry the traffic part of the call (speech or data). They are defined as
functions rather than devices as they are a logical representation of the traffic, rather
than relating to a physical piece of hardware. An RTF contains eight digital channels, one
for each timeslot on the air interface.
There are two types of RTF:
S
BCCH (one of the timeslots is used as a BCCH).
Non-BCCH.
To provide redundancy of RTF traffic, it is possible to specify two routes or PATHs that
are potentially able to carry the RTF traffic from the BTS to the BSC. These are called
the Primary and Secondary PATHs. If two PATHs are available, the shorter will be the
connected PATH and the longer will be the redundant PATH. If the PATH availability
changes and a shorter PATH becomes available to the RTF, then a switchover will occur
so that the RTF starts to use this new PATH. Refer to Physical links - PATH for more
details of PATHS.
Each RTF function, equipped to a remote SITE, uses two PCM (that is, 2 x 64 kbit/s,
where 64 = 4 x16 kbit/s) timeslots per PATH device.
Each OMC-R is limited to supporting a particular number of RTFs, this is called the RTF
Limit, and is set by Motorola engineers during staging. Each OMC-R has a threshold
RTF value, which is 90% of the RTF Limit.
Redundancy (within a cell)

The DRIGroup and RTFGroup are used to support transceiving redundancy for CELLs.
Typically, for n RTFs there will be n+1 DRI devices equipped. When an RTF is equipped,
it attaches itself to an available In Service (INS) DRI. If the DRI goes Out Of Service
(OOS), the RTF will attach itself to another available DRI to maintain transceiving
functionality to the CELL.
420

68P02901W01-M
02 May 2003
CELL configuration
GSR6 (Horizon II)
CELL configuration
Logical devices
A CELL contains the following logical devices:
S
Neighbour.
Handover control.
Power control.
Handover control
Handover means switching a call from a channel in a given CELL, to another channel in
either the same or another CELL. This is done keeping disturbance to a minimum,
ideally in a way not noticeable by the users.
The BSS allows adaptive power budget handovers (if enabled) on a per cell or neighbor
basis. The adaptive handover methodology allows handovers to be recognized based on
a cumulative area rather than a vote. At each measurement report the cumulative area is
updated and compared to a cumulative trigger. If the power budget (pbgt) dips below the
handover margin temporarily the cumulative area will be decremented by the difference
and not reset. If this cumulative area is then greater than the cumulative pbgt trigger, a
need for a handover will be recognized. The cumulative area is based on either a per
cell or a per neighbor basis as decided by the operator.
Handover control, is the functionality required to detect and effect a handover, in order to
maintain acceptable service to the user.
Handover detection algorithm

There are a number of parameters used to detect when a handover should occur. A
number of factors are input to this algorithm. These factors are as follows:
S
Uplink and downlink receive signal strength.
Uplink and downlink receive signal quality.
Power budget.
When a power budget handover is enabled, the call will hand to a neighbouring cell
at the point where a lower power budget can be achieved (both the MS and the
BTS can reduce their TX power).
Interference.
Distance (between the BTS and the MS).

NOTE
Uplink is from the Mobile Station (MS) to the BTS, downlink is

from the BTS to MS.
There are thresholds supported for each measurement and when a threshold is
exceeded, a handover may occur.

02 May 2003
68P02901W01-M
421
CELL configuration
GSR6 (Horizon II)
Power control
In order to reduce Radio Frequency interference in the network, and increase battery life
on MSs, it is desirable to run all the BTSs and MSs in the network at the minimum TX
power that provides adequate rxqual (quality) and rxlev (level) for a call.
Power control is the functionality to detect and effect the modification of transmission
power, both for the MS and BTS, in order to maintain an acceptable service to the user.
A dynamic power reduction algorithm can be used in conjunction with the standard power
control algorithm. In the event that the power level exceeds the upper level threshold the
algorithm will allow the decrement step size to change dynamically based on the
proximity to the upper power threshold and will be used to reduce the power level to one
under the threshold level. The calculations will be made for both uplink and downlink
power control.
Power control detection algorithms

There are a number of parameters used to detect when power control should occur.
A number of factors are input to the algorithms. These factors are:
S
Uplink and downlink receive signal strength.
Uplink and downlink receive signal quality.
There are thresholds supported for each measurement. When a threshold is exceeded
transmission power modification may occur.
422

68P02901W01-M
02 May 2003
Links in a GSM network: overview
GSR6 (Horizon II)
Links in a GSM network: overview

Information on links
Note the following BSS link definitions:
S
All links to and within BSSs and RXCDRs are in reality links to and between
SITEs.
A link to a BSS, is a link to the SITE configured as a BSC within the BSS.
Similarly, links within a BSS, those between the BSC and BTSs and between one
BTS and another, are all links between SITEs.
SITE link requirements

Every SITE must contain at least one Multiple Serial Interface (MSI) board (NIU for
M-Cellt and Horizon), which is a communications controller that contains two 2 Mbit/s
(MMS) ports.
Link types
There are two types of links used in the GSM network:
S
Physical links.
Logical links.

02 May 2003
68P02901W01-M
423
Physical links - PATH
GSR6 (Horizon II)
Physical links - PATH

Connection
A physical link between two SITEs is made by connecting one MMS port of an MSI (NIU
for M-Cell) card on one SITE, to one MMS port of an MSI (NIU for M-Cell) card on
another SITE.
Physical link requirements

The following are physical link requirements:
S
Every BSC must be physically connected to the OMC-R. A BSC may be directly
connected to the OMC-R, or via the RXCDR or MSC.
Similarly, every BSC must be physically connected to its controlling MSC. A BSC
may be directly connected to its controlling MSC or it may be connected via an
RXCDR.
Every BTS must be physically connected to its controlling BSC. A BTS may be
directly connected to its controlling BSC or it may be connected via another BTS
(daisy chaining). A BTS may have more than one signalling and traffic connection
to its controlling BSC giving load sharing and redundancy.
PATH devices
A PATH device defines the connectivity between a BSC site and BTS sites under its
control. It is a logical representation of a 2 Mbit/s route between the BSC and a
destination BTS. This connectivity specifies the physical route from the BSC, through
intermediary BTSs to the destination BTS. A PATH may contain a route through a
maximum of 10 BTS sites. The connection information between any two sites consists of
an MSI (NIU for M-Cell)/MMS device at each end of the link.
Figure 4-9 shows two PATHs connecting BSC 0 with BTS 3, a PATH through BTS 1 and
BTS 2, (A-B-C), and one direct connection between BSC 0 and BTS 3 (D).
Figure 4-9 Example of path settings within a BSS

BSS
BSC 0
BTS 1
BTS 2
BTS 3
PATH 1 = A-B-C
PATH 2 = D
424

68P02901W01-M
02 May 2003
Logical links
GSR6 (Horizon II)
Logical links
Introduction to links
The 2 Mbit/s physical links in the GSM network, are configured to carry (as well as the
voice traffic channels) many logical links containing signalling information or O&M data.
These links are monitored by the OMC-R.
Types of link
The types of logical links are shown in Figure 4-10. These links generate events, alarms,
and performance statistics, at the BSC (or RXCDR) site where they are equipped. These
are reported to the OMC-R.
The different logical links are as follows:
Operation and Maintenance Link (OML)

The purpose of the OML is to provide communication between an OMC-R and a BSC or
RXCDR for transferring network management (O&M) data. Up to four OML links can be
configured between an OMC-R and BSC or RXCDR; one OML is used at any one time,
the other three OMLs exist for redundancy purposes.
Message Transfer Link (MTL)

The purpose of the MTL is to provide a link for signalling information between the BSC
and the MSC. In the Motorola system, when local transcoding is used, this is a physical
connection between the BSC and the MSC. When a Remote Transcoder is used, the
logical MTL is made up of two physical parts; the connection between the BSC and the
RXCDR and the connection between the RXCDR and the MSC.
S
When more than one MTL is configured between the BSC and MSC, both load
sharing and redundancy are present. Up to 16 MTLs may be configured between
a BSC and MSC.
Radio System Link (RSL)

A signalling link between a BSC and a remote BTS is called a Radio System Link (RSL).
The purpose of an RSL is to provide signalling information between a BSC and a remote
BTS. The timeslots used, are chosen automatically by the Motorola software. This is to
ensure that new BTSs, added to the network, can be communicated with on default
timeslots.
S
Each RSL link is associated with a PATH. It is possible to have multiple (up to
eight) RSLs between a BSC and a remote BTS. For example, in Figure 4-10,
there are two RSLs between BTS2 and the BSC. This is possible because of the
daisy chain connection in the BSS. The two RSLs provide both load sharing and
redundancy functions for the signalling link.
RXCDR to BSC Link (XBL)

An XBL link may be configured between the BSC and the RXCDR for exchanging
internal Fault Management (FM) data between them. An Enhanced XBL (EXBL) will
allow generic messaging between the RXCDR and BSC in support of current and future
operator needs.
Cell Broadcast Link (CBL)

S
A CBL link can be configured between the BSC or RXCDR and the Cell Broadcast
Centre (CBC). This is used for downloading messages to broadcast along with
other necessary information such as repetition rate and number of broadcasts.
02 May 2003
68P02901W01-M
425
Logical links
GSR6 (Horizon II)
Requirements
Figure 4-10 shows the different logical links in a GSM network. Logical link requirements:
S
A BSC will always contain at least one OML (with a maximum of four), one MTL or
XBL/EXBL (depending on how it is connected to the MSC) and at least one RSL
for each remote BTS under its control.
An RXCDR will always contain at least one OML, and at least one XBL/EXBL.
A BTS will always contain at least one RSL.

Figure 4-10 The different logical links in a GSM network
MSC
OMC-R
MTL 1
X.25
VOICE TRAFFIC
2 Mbit/s link
OML1
MTL2
VOICE TRAFFIC
2 Mbit/s link
RXCDR
OML2
Different logical links:

MTL:MSCBSC LINK
(C7 SIGNALLING INFORMATION)
OML:OMC-RBSC LINK
(O&M DATA)
XBL:RXCDRBSC LINK
(FAULT MANAGEMENT DATA)
RSL:BTSBSC LINK
(SIGNALLING INFORMATION))
CBL:BSCCBC Link
(MESSAGE INFORMATION)
Voice Traffic
OML3
CBL
MTL2 XBL2
2 Mbit/s link
OML2
XBL1
OML1
2 Mbit/s link
MTL1
CBL
CBC
CBC
2 Mbit/s link
BSC
BSC/BTS 1
RSL11
BTS2
BTS3
RSL11
RSL22
(BTS1 to BSC )
BTS1
RSL12
(BTS1 to BSC )
RSL21
RSL12
(BTS2 to BSC)
RSL22
(BTS2 to BSC)
426

68P02901W01-M
BTS2
02 May 2003
OMC-R connection to the network
GSR6 (Horizon II)

Transferring data
For every BSC in the network, one or two timeslots (64 kbit/s) on a 2 Mbit/s link is used
to carry the O&M data between the BSC and RXCDR. All the timeslots from the different
BSC-RXCDR links are grouped onto one or more 2 Mbit/s links by the RXCDR or the
MSC. The RXCDR transfers the information to a packet switch / multiplexer.
The X.21 links are connected to the OMC-R via a public or private X.25 network/switch.
Illustrated in Figure 4-11 is the method of transferring O&M data between the BSS and
OMC-R network elements (NEs). Other NEs can also communicate with the network.
X.21 connection configuration

The physical connection between the OMC-R processor and the packet switch /
multiplexer consists of two to seven X.21 connections. Each physical connection can
support up to 256 virtual circuits. There are four types of virtual circuits that can be made
on the OML:
S
Event Interface (EI) transfers data packets (events and alarms), plus the
OMC-BSS message from a NE (e.g. a BSS) to the OMC-R. The circuit is made by
the NE calling the OMC-R.
Bootload (BL), also called Download, transfers BSS software and BSS databases
to the NE. The circuit is made by the NE calling the OMC-R.
Upload (UL) transfers BSS database back-ups and raw statistics (performance
data) to the OMC-R. The circuit is made by the OMC-R calling a NE.
Remote login (RL) provides sessions for transfer of BSS GUI

commands/responses to a NE. The circuit is made by the OMC-R calling the NE.
The virtual circuits EI and BL can be accepted on any of the X.21 connections on the
OMC-R. Normally two connections are set up for EI and BL. If a given port is not
working, then the packet switch / multiplexer will switch to a different port. The UL
circuits consists of four processes and each is assigned to a single OMC-R connection.
The RL is assigned to a single OMC-R connection.
Figure 4-11 shows the communication between the OMC-R and other network elements.

02 May 2003
68P02901W01-M
427
GSR6 (Horizon II)
Figure 4-11 Communication between the OMC-R and other network elements
OMC-R
OMC-R
SYSTEM
PROCESSOR
X.25
O&M Data
Packets
RXCDR
X.21 connections
(two to seven physical
connections)
Packet switch /
multiplexer
2 Mbit/s
link
NAILED CONNECTIONS
(ONE PER O&M TIMESLOT)
64 kbit/s
O&M
TIMESLOT
2 Mbit/s link
BSS1
BSS2
428
RXCDR

68P02901W01-M
BSS3
64 kbit/s
O&M
TIMESLOT
2 Mbit/s link
BSSn
BSS4
02 May 2003
Operations and maintenance of a BSS or RXCDR
GSR6 (Horizon II)
Operations and maintenance of a BSS or RXCDR

Simplified network
A simplified network showing some of the hardware devices in the different sites, and the
links between them, is shown in Figure 4-12. BSS1 from Figure 4-11 is used as the
example BSS.
Figure 4-12 Simplified GSM network showing devices and links at BSSs
X.25
RXCDR
MTL
LINK
MSC
OML
MSI
X
C
D
R
OMC-R
RXCDR:
SITE0
KSW
MSI
XBL
LINK
BSS
BSS1: SITE0
MSI
KSW
DRCU
+
COLLOCATED
BSC/BTS
DRI
MSI
MSI
BTS
BTS
BSS1: SITE1
DRCU
+
DRI
K
S
W
M
S
I
BSS1: SITE2
MCell
RSL
LINKS
N
I
U
M
C
U
TCU

02 May 2003
68P02901W01-M
429
O&M information flow between OMC-R and NEs
GSR6 (Horizon II)
O&M information flow between OMC-R and NEs

Summary of information flow
A summary of the information flow between the OMC-R and other NEs (e.g. RXCDR and
BSS) is shown in Figure 4-13. The primary function of the OMC-R is to monitor the
health of the radio network.
Figure 4-13 Information flow between the OMCR and BSSs
OMC-R
OMC-R TO NE
1. GUI COMMANDS
(VIA GUI OR REMOTE LOGIN)
FAULT HANDLING
SITE CONFIGURATION
SITE RESETS
2. SOFTWARE and NE
DATABASE DOWNLOADS
3. NE DATABASE DOWNLOADS
NE
NE
NE TO OMC-R
1. EVENTS & ALARMS
2. NE RESPONSES TO
GUI COMMANDS
3. PERFORMANCE DATA
(RAW STATISTICS)
4. NE DATABASE UPLOADS
NE
NE
NE
Information flow
All events (changes of state of a hardware device, link, or function) and alarms (changes
which could be service affecting) are sent to the OMC-R, via the RXCDR and the X.25
packet switch, where they are processed into a standard format. The alarms can be
configured to update a network map, which will give the operator a visual warning by
causing the appropriate BTS or BSC to flash. The alarms or events can also be
displayed on the operator terminals, within different windows, depending on how the
network operator (or OMC-R administrator) has configured them.
The RXCDR contains several of the same devices, links and functions as the BSS, and
generates events and alarms in the same way.
The network operator then takes action to handle the reported fault, by remote logging in
to the BSS or RXCDR, diagnosing the problem, and taking appropriate action.
Regardless of the number of BTSs, the BSS is regarded as a single NE, and runs only
one software load, for example BSSGSM 1.6.0.x. When loading a BSS, the entire load
is first sent to the BSC which then distributes the appropriate load objects to the
configured BTSs. A copy of the active BSS load is stored at the OMC-R as is a copy of
the previous version of the BSS software. These software loads must be compatible with
the load installed on the OMC-R. The RXCDR receives the same software load as a
BSS, it just implements a different part of it.
Each BSS and RXCDR contains an operational database, in which the configuration data
for all the devices and links in the SITES within the NE is stored. A backup copy of the
active database is kept at the OMC-R.
Performance measurements for the different BSS and RXCDR are periodically routed
every 30 or 60 minutes to the OMC-R as raw statistics in a data file. This data is stored
in a database at the OMC-R, and processed into statistics which provide valuable
information for efficient network management and planning.
430

68P02901W01-M
02 May 2003
OMC-R system configuration
GSR6 (Horizon II)

Motorola OMC-R
A typical hardware configuration of a Motorola OMC-R, is shown in Figure 4-14.
Figure 4-14 An example Motorola OMCR system configuration
X.25 PACKET SWITCH

X.25
INTERFACE
TO GSM
NETWORK
X.25
PACKET SWITCH
& MULTIPLEXER
OMC-R SYSTEM
PROCESSOR
Laser
Printer
LOCAL AREA
NETWORK (LAN)
OSI processor
(optional)
OMC-R GUI processors Operator Workstations + GUI Server
Typical hardware configuration

An OMC-R comprises a central System Processor and several GUI processors. Each
processor is a complete UNIX system which provides a GUI interface presented on a
colour monitor. The system is connected via a LAN allowing all workstations access to a
laser printer. The GUI server is a server that allows the GUI processes to be run on a
fast machine while using the slower machine for the display process.
NOTE
Some systems may be configured differently; for specific

information the OMC-R Bill Of Materials (BOM) should be
consulted.

02 May 2003
68P02901W01-M
431
Communications handling
GSR6 (Horizon II)
Communications handling
Communications software
The OMC-R communications software, provides control and support for the protocol
stacks which interface the OMC-R with the following:
S
Internal OMC-R communications:
TCP/IP.
Ethernet.
X.11.
The NEs in the GSM network - X.25.
The X.25 software is loaded in the System Processor, and the X.11 driver software is
loaded in the GUI Processors. The remaining communication software is shared between
the two processors. The operating processes are linked between machines by
Interprocess Communication (IPC). The OMC-R network can be extended to include
further GUI Processors, or secondary GUI servers, connected either locally or via a Wide
Area Network (WAN). Bridges and gateways can also be used to connect to other
computer systems such as an NMC, or other OMC-Rs.
432

68P02901W01-M
02 May 2003
Packet switch/multiplexer
GSR6 (Horizon II)
Packet switch/multiplexer
Connections
The OMC-R is connected to the GSM Network, to receive O&M data using a packet
switch / multiplexer, (as shown in Figure 4-15). The Packet Switch makes a maximum of
256 x X.25 virtual circuits available for the exchange of O&M data between the OMC-R
and the NEs.
Figure 4-15 Example Packet switch / multiplexer connections

2 Mbit/s
Links
2 Mbit/s
Links
Packet Switch / multiplexer
HSI Card
HSI Connections
System processor
OMC-R
system
processor
Packet switch
The connection between the System Processor and the Packet Switch could be direct or
connected through a Private eXchange Public Data Network (PXPDN).

02 May 2003
68P02901W01-M
433
O&M network traffic capacity
GSR6 (Horizon II)
O&M network traffic capacity

Peak traffic capacities
The System Processor supports the following O&M peak network traffic capacities:
434
100 x X.25 packets per second, with a packet length of 128 bytes, aggregate.
100 kbit/s aggregate.
The system processor can be configured to handle up to 5,000 traffic channels,

10,000, 30,000 or 45,000 traffic channels, associated with a maximum of 120 NEs
via the 256 x X.25 virtual circuits.

68P02901W01-M
02 May 2003
OMC-R system processor
GSR6 (Horizon II)

Introduction to the system processor
The hardware configuration of the system processor (for example, the number of CPU
processors, memory, disk capacity) can be varied depending on whether the
low-capacity, mid-capacity or high-capacity TCH OMC-R is chosen. Thus, the scaleable
OMC-R provides easy and cost effective expansion/de-expansion from low-capacity TCH
through mid-capacity TCH to high-capacity TCH configuration. The software
requirements are the same for all capacity scaleable OMC-R configurations.
System processor
System specifications
The system processor software is installed on internal and external disks depending on
the system processor in use. All system and data areas are mirrored for redundancy.
Figure 4-16 shows the scaleable OMC-R high-end system processor.
Figure 4-16 Scaleable OMC-R - high-end system processor

E3000
SUN HSI/S card (4-port

HSI interface)
OMC-R System Processor

4 (or 7) x 2.1/4.2 Gb disks
(Internal and External)
Graphics
Head
Or E3500
OMC-R System Processor
Graphics
Head
System Processor
4 (or 8) x 9.1 Gb disks (Internal)
The system processor running Solaris 2.5.1 handles hardware failure by rebooting on
failure, and configuring out the broken hardware.
Connection to GSM network

The scaleable OMC-R uses Sunlink X.25 application software and connects to the
network using a HSI/S card. This allows the scaleable high-end OMC-R to be used
where there is existing packet switching and multiplexing equipment available, or to be
connected to a public packet switched network.
OMC-R application software impact

Existing system processor OMC-R application software has been ported to work on the
Solaris 2.5.1 OS. There is no performance impact due to the scaleable high-end OMC-R.

02 May 2003
68P02901W01-M
435
GSR6 (Horizon II)
Feature description
Table 4-2 gives a comparison between the four Scaleable OMC-R configurations.
Table 4-2 Scaleable OMC-R configurations (maximum values)
Feature
Scaleable
OMC-R
low-end
Scaleable
OMC-R
mid
range
Scaleable
OMC-R
mid
range
Scaleable
OMC-R
high-end
RTFs supported
714
1430
4285
6000
NEs supported
15
30
120
120
Total GUI sessions supported
10
10
10
Dial-up sessions per GUI

processor
Total remote dial-up sessions
Remote login sessions
20
30
Simultaneous downloads
12
12
Simultaneous uploads
16
32
8 alarms
+2 state
changes
8 alarms
+2 state
changes
Sustained event rate
Maximum event burst
12 alarms+ 12 alarms+
3 state
3 state
changes
changes
20 events/s 60 events/s 60 events/s 60 events/s

over 20
over 20
over 20
over 20
mins
mins
mins
mins
External interface (OMC-R to BSS)

The OMC-R-BSS (rlogin) and the SMASE-NMASE interface will not be affected by the
high-end scaleable OMC-R.
436

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Configuration
The configuration of the system processor is shown in Figure 4-17. It uses a Solaris 2.5.1
UNIX operating system and contains a DataBase Management System (DBMS) from
Informix (which is configured for storing the performance statistics). There is an Event
Management Information Base (EM MIB) that contains the incoming events and alarms
which update the map displays to present the operator with visual indication of alarms in
the network. The System processor also contains the CM MIB which holds the
configuration data required to run the network maps.
Figure 4-17 System processor software configuration

SYSTEM
PROCESSOR
Event Log
OMC-R
DATABASE
[Informix]
SOLARIS
(2.5.1)
OMC-R GSM
GSR 4
Applix
CM
MIB
ETHERNET
CONTROLLER
CONSOLE
FOR
SYSTEM
ADMINISTRATOR
X.25
HANDLER
cm_mib
GUI

02 May 2003
68P02901W01-M
437
OMC-R GSM application software: overview
GSR6 (Horizon II)

OMC-R processes
The functional software areas of the OMC-R are split between the OMC-R system
processor and the GUI processor. The processes of the OMC-R application software
installed on the OMC-R system processor are shown in Figure 4-18. The operator is
provided with a front end to all these processes at the OMC-R GUI, and additional front
end functionality is provided by command line utilities.
Figure 4-18 OMC-R GSM (System processor) software components
OMC-R (System Processor)
SW Load
Management
Performance
Management
Configuration
Management
Device
Management
Event
Interface
Event/Alarm
Management
Remote
Login
System processor software elements

The software elements that constitute the system processor software, perform the
network element O&M management tasks, provide database storage facilities, and
provide the interface to the network elements via the X.25 network. The OMC-R system
processor software elements are as follows:
Configuration management
Configuration management allows the operator to perform network configuration
tasks, and to maintain all details of the network configuration at the OMC-R.
Performance management
Performance management controls the collection, administration, processing, and
storage of NE performance statistics.
Software load management

Load management provides a facility for uploading and downloading NE software
loads, and NE operational databases. It also provides a means of managing
multiple copies of software loads for back-up purposes.
Event/alarm management
Event/Alarm management provides a mechanism at the OMC-R for alarm
surveillance. It manages events and alarms routed to the OMC-R from other NEs,
or generated within the OMC-R.
438

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Remote login
The remote login software manages the X.25 connection for remote login to
network elements from the OMC-R. Remote login is a means by which the
operator performs configuration management, fault management, and some
performance management procedures at the network elements.
Event interface
The event interface handles the X.25 alarm connections to the network elements,
then translates and forwards incoming events and alarms to the Event/Alarm
Management functional software.
Device management
Device management allows the operator to perform fault management and
configuration management at the OMC-R. The OMC-R supports most hardware
devices and software functions located at the remote network elements.

02 May 2003
68P02901W01-M
439
UNIX: Solaris 2.5.1 operating system
GSR6 (Horizon II)
UNIX: Solaris 2.5.1 operating system

Platform
The SUN system processor operates under the Solaris 2.5.1 operating system. This
provides the platform for the OMC-R software applications and provides facilities for
system administration.
Advantages
The main advantages of this operating system are that it is designed to provide:
S
An enhanced multi-architecture solution for systems to support Internet/Intranet

connectivity.
A system offering a scaleable, secure and reliable operating environment.
Features
The Solaris 2.5.1 release contains several 64-bit features, including Kernel
Asynchronous Input/Output (KAIO), which facilitates the fast asynchronous transfer of
large amounts of data between memory and disk.
Included with this release is the Common Desktop Environment (CDE). This provides
users with a flexible open user environment that has a common look and feel across all
major UNIX desktops. This environment allows transparent access to network resources;
and allows frequently used UNIX commands to be iconized. It is also possible to drag
and drop between files and commands.
Tools and applications

The Solaris 2.5.1 operating system includes the following tools and applications:
Solstice backup 5.1 utilities

S
The Solstice backup software allows a Solaris operating system server to provide
automated, high performance backup, recovery and storage management services
to machines on the network.
Solstice backup provides simple centralized administration, through a single unified

view of the entire data management operation from any point on the network.
Intuitive user interfaces simplify administrative tasks such as configuring clients
and servers, and setting up backup schedules for file systems and databases.
Solstice AdminSuite 2.3

Solstice AdminSuite software provides an integrated collection of graphical user
interfaces to perform administrative tasks such as managing hosts, users, groups,
administrative data, file systems, disks, printers, and serial port devices.
The Solaris operating system allows the OMC-R to be administered as a typical UNIX
system.
440

68P02901W01-M
02 May 2003
The OMC-R database
GSR6 (Horizon II)
The OMC-R database

RDBMS
The OMC-R database, maintained at the system processor, uses an industry standard
Relational Database Management System (RDBMS) known as INFORMIX. The DBMS
manages access to its own stored data and provides its own data protection. It is made
up of a PM sub-schema and an EM sub-schema. The PM sub-schema is used for storing
processed performance statistics from the GSM Network, while the EM sub-schema
stores the subscription lists used to subscribe to incoming events and alarms (see
Figure 4-19).
Database schema: defined

The OMC-R database may be thought of as a centralized data store for data that will
need to be further manipulated, either by system users or other OMC-R application
areas. A database schema is a data model of a precise, complete definition of the data
to be stored. It provides a formal notation data model of tables, rows, columns, and keys.
The tables in which the data is stored, are predefined by the database schema and their
physical structure cannot be altered, only their contents can be manipulated.
Figure 4-19 OMC-R database - database schema breakdown
RAW
STATISTICS
TABLES
NETWORK
CONFIGURATION
TABLES
PM SUB-SCHEMA
PM REPORT
TABLES
EM SUBSCRIPTION LISTS
EM SUB-SCHEMA
Database size
The database can be sized at installation to meet the requirements of the GSM Network.
The disk is hardware mirrored to provide a high level of protection against loss of data in
case of hardware failure.
Applications and utilities

The management of the OMC-R database is accomplished using INFORMIX-OnLine
utilities and OMC-R applications built around them. The OMC-R database supports the
following applications:
02 May 2003
68P02901W01-M
441
The OMC-R database
GSR6 (Horizon II)
Structured Query Language (SQL) and Applix access for custom

reporting
SQL and Applix are industry standard languages, which can be used to write
applications to extract performance management data from the database.
Read-only access to the data is available.
Database backup and administration utilities

The OMC-R system administrator is provided with a facility for on-line back-up of
the OMC-R database. This avoids halting the OMC-R during routine back-up
operations.
442

68P02901W01-M
02 May 2003
The SPARCstation configuration
GSR6 (Horizon II)

Running the OMC-R GUI
ULTRA 5/1 and SPARCstation 20/5s are primarily concerned with running the OMC-R
GUI. Typically the OMC-R configuration contains two ULTRA 5/1s or SPARCstation 20s
and several SPARCstation 5s. One of the ULTRA/SPARCstation 20s machines must be
configured as a GUI Server. A second can be configured as a GUI server or the system
processor can fulfil this GUI server role. Two GUI servers are the preferred arrangement
and each will support half of the GUI clients. This arrangement allows system operation
to continue should one of the GUI servers fail. The ULTRA machine configured as a GUI
server allows the slower SPARCstation 5 machines to run the GUI display tasks while the
server runs the GUI processes.
Each SPARCstation is a complete UNIX system, which runs the same GUI version. A
typical configuration is shown in Figure 4-20.
Figure 4-20 OMC-R SPARCstation configuration
SPARCUltra 5/1
SPARCUltra 5/1
GUI
GUI
GUI SERVER
GUI SERVER
SPARCstation 5
SPARCstation 5/10/20
GUI
GUI
GUI CLIENT
GUI CLIENT
SPARCstation 5
SPARCstation 5
GUI
GUI CLIENT
GUI
GUI CLIENT
LOCAL AREA NETWORK (LAN)
TO SYSTEM PROCESSOR
The network file system

The OMC-R GUI expects all the SPARCstations to be configured as standalone NFS
(Network File System) machines. This configuration allows each SPARC some degree
of independence while still allowing resources to be shared.
LAN configurations
The SPARCstation 5s execute the display process and function as operator workstations.
The OMC-R GUI software is made accessible over the LAN by configuring the
SPARCstations in the following way:
S
An ULTRA 5/1 or SPARCstation 20 is installed as a GUI Server to the

SPARCstation 5s.
This configuration allows the use of slower, older machines and the OMC-R GUI is made
accessible to the 5s through NFS.
02 May 2003
68P02901W01-M
443
GSR6 (Horizon II)
Other configurations
Other network configurations may also exist, such as a GUI processor configured to run
the OMC-R GUI from a remote site. In networks containing two OMC-Rs, a GUI
processor in the local OMC-R is configured to monitor a remote OMC-R during the night
shift (the local OMC-R is known as the night concentration centre).
444

68P02901W01-M
02 May 2003
GUI processor
GSR6 (Horizon II)
GUI processor
Server client relationship
Up to 10 additional processors can be added to the system to support the GUI interface.
One of the machines must be configured as a GUI server. The additional machines
mount the display software from the GUI server. The total number of GUI sessions
supported is 10, as on the standard OMC-R. Each processor will support one GUI
session.
An example of a GUI processor hardware configuration is shown in Table 4-3. The GUI
processor will be configured with software as shown in Table 4-4.
Table 4-3 GUI processor hardware specifications
Hardware
Applicable to both 0-10k TCH and 0-45k TCH
Model
SPARCUltra 5 or SPARCUltra1 or SPARCstation 5
Processor (CPU)
1 x 167 MHz, 1 x 250 MHz, 1 x 270 MHz or 1 x 360 MHz
Memory
64 MB or 256 MB
Disk Capacity
1/2 x 2.1 or 4.2 Gbyte disk drives
Network
Ethernet. Twisted pair interface
CD-ROM
Internal CD-ROM drive. SMCC
Drives
3.5 1.44 Mb Internal Floppy
Printer
Network Printer
Note: Exact specifications for the Sparc Ultra 1 are yet to be confirmed
Table 4-4 GUI processor software specifications
Software
Applicable to both 0-10k TCH and 0-45k TCH
SUN
Solaris 2.5.1
Solaris 2.5.1 OS patches
Solstice Backup Client 5.1/Solstice AdminSuite 2.3
Informix
I-Connect 7.xx UC2
X11
X11 Release 5 Version 26
Desktop
Motif 1.2.5G for SPARC 2.x single user licence

Sun Solaris CDE 1.0.2
Interleaf
(GUI Server only)
TCL (GUI Server only)
TCL Version 8.2
Expect (GUI Server only)
Expect Version 5.31
Applix (GUI Server only)
Applix 4.4
Wingz
Wingz 1.4.1

02 May 2003
68P02901W01-M
445
The network status summary (NSS) feature
GSR6 (Horizon II)
The network status summary (NSS) feature

Maps
Figure 4-21 shows the maps icon on the OMC-R GUI front panel.
Figure 4-21 Maps icon
The role of the OMC-R in a GSM network is to allow network operators to perform
network management functions to ensure that the network operates efficiently, and to
ensure that the service to the customer is maintained. The OMC-R acts as a central
collection point for measurement data used in the analysis of current performance and
future planning of the network.
Features
The NSS features are as follows (refer to Figure 4-22):
S
Network maps.
Alarms icon.
Alarm summary.
Figure 4-22 The network status summary options on the GUI front panel
Launches network
maps
446

68P02901W01-M
Incoming alarms
indicator
02 May 2003
The CM MIB
GSR6 (Horizon II)
The CM MIB
Description of the CM MIB
The system processor contains the CM Management Information Base (CM MIB) that
holds all the configuration data needed for the network maps of the OMC-R GUI and for
cell parameter optimization. Information in the CM MIB includes lists of the various types
of nodes in the GSM network, with their attributes and interconnections, as well as lists of
maps containing nodes and connections on each map. All the GUI processors which run
the NSS feature, communicate with the CM MIB using an internal process called
cm_mib.
Populating the CM MIB

The CM MIB can be populated with NE data by selecting:
S
Audit.
or
Detailed View Forms (for each object).

02 May 2003
68P02901W01-M
447
GUI Client - SPARCstation 5
GSR6 (Horizon II)

Software configuration
The Sun Microsystems SPARCstation 5s (the operator workstations) displays the GUI
data. This GUI client may be installed on either the System processor, or on one of the
SPARCUltra 5/1 stations. In all cases the OMC-R GUI Client software is executed on the
local SPARCUltra or SPARCstation 5. One of the SPARCUltra machines is also
designated as a GUI server to half the GUI clients, giving redundancy should one of the
GUI servers fail.
Figure 4-23 shows the SPARCstation 5/IPX hardware and software configuration.
Figure 4-23 SPARCstation 5/IPX hardware and software configuration

GUI PROCESSOR
SunOS
GUI Client
OPERATOR
WORKSTATION
Hardware features
The SPARCstation 5s contain the following hardware features:
S
Local Disk 535/424 Mb (minimum configuration).
20 inch colour terminal.
The SPARCstation 5s are complete UNIX systems and are loaded with the same UNIX
operating system as the SPARCUltras. They are usually configured as standalone NFS
(Network File System) machines.
448

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Night concentration
Figure 4-24 shows a night concentration centre with one SPARCUltra configured as a
GUI Server for both region A and region B. This means that only one SPARCUltra is
required during the quiet night periods enabling a reduction in operating personnel.
Figure 4-24 Night concentration configuration
Printer
Printer
GUI Server
LAN
Bridge/
Router
X.21
Router
GUI Client
GUI Client
SYSTEM
ProcESSOR
LAN
GUI Server
(region A)
GUI Server
(region B)
Leased
Line
Concentration centre
Regional OMC-R A (local)
Printer
GUI Server
GUI Server
LAN
Bridge/
Router
X.21
GUI Client
SYSTEM
ProcESSOR
Regional OMC-R B
(Remote)

02 May 2003
68P02901W01-M
449
How the network status summary feature works
GSR6 (Horizon II)

Map process
When a network map, for example, Network 1600b: Device Mode (see Figure 4-25), is
selected via the Maps icon on the OMC-R front panel, a map process is invoked on the
GUI processor.
Figure 4-25 Map processes
State change events
MAP_ALARMS
MAP_EVENTS
ALM_ALARMS
CM
MIB
Test-Network map
MAPNODES
MAPLINKS
FROM NETWORK
GUI front panel
Alarm events
Active NSS
subscription list
EM
Proxy
SYSTEM PROCESSOR
GUI PROCESSOR
Configuration data
All the configuration data needed to run the network map are stored in the CM MIB,
which is maintained on the OMC-R System Processor. The CM MIB stores a series of
managed objects to which relevant network configuration data and data needed to
configure maps are assigned. For example, both a BSS and a Map are regarded as
managed objects with different data. All the GUI processors that run the network maps
communicate with the CM MIB using an internal process called cm_mib.
450

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
The EM proxy process

The EM Proxy process contains a list of all NEs, SITEs, cells, and links. The process
examines the incoming alarm messages and compares it to the list. It updates the list if a
change has occurred. Every two seconds a changed list is forwarded to the GUI
processor. The list contains attributes which reflect the severity of the alarm and its
handling state. These in turn update the Alarm Summary on the GUI front panel, and the
attributes of the links and nodes on the active map, as configured in the CM MIB. The
Contained Devices form and alarm icons are also updated. Similarly, incoming
StateChangedEvents from SITEs and MMSs change the state of the attributes in the CM
MIB. This reflects the administrative and operational states of the different SITE and
CommsLink configuration objects, representing the physical devices in the network.

02 May 2003
68P02901W01-M
451
GUI clients and servers: overview
GSR6 (Horizon II)
GUI clients and servers: overview

Client/server system
The client/server concept is a common form of distributed system in which software
processes are split between server tasks and client tasks. A client sends requests to a
server, according to a standard protocol, asking for information or action, and the server
responds by sending the requested information or by performing the required action.
This is analogous to a customer (the client) who sends an order (request) on an order
form to a supplier (the server) who despatches the goods and an invoice (response). The
order form and invoice are part of the protocol used to communicate in this analogy.
The connection between a GUI Client and GUI server is normally by means of message
passing, which may be over a network or even within a single machine. For example, the
SPARC ULTRA 5 with the client and Sserver on the same machine. There may be a
single centralised server or several distributed Servers, depending on workloads. This
model allows clients and servers to be placed independently on nodes in a network,
possibly on different hardware and operating systems.
GUI servers and GUI clients

The GUI servers and GUI clients have now replaced the older MMI servers and clients,
however MMI servers and clients can both be re-deployed as GUI clients, but only the
high end MMI server (Ultra 5) have the power to run as a GUI server.
452

68P02901W01-M
02 May 2003
Network maps
GSR6 (Horizon II)
Network maps
Functionality
Network maps show status information on the network and enable the following different
types of functionality to be invoked for a selected NE:
Current network configuration

Network maps present the current network topology. Network configurations can be
updated using the Detailed Views and an Audit, initiated to ensure consistency between
the MIB and the Network. A full network map, which displays all NEs and links in the
network is available. Each NE can be expanded to show the SITEs and links within the
NE. Maps can be zoomed or expanded when displayed, (refer to Figure 4-25). If the
system is configured, more detailed maps of any part of the network can be displayed.
Alarm state
Incoming alarms are reported by a colour change in the NE and link icons on the map.
The alarms icon on the front panel will also flash, and where available, there will be an
audible warning.
MMS and SITE service states

The map display uses three different icon types to represent state changes in SITEs
(represented by SITE map nodes) and MMS devices (represented by map links). Refer
to State Changes in the Map Display section. The icon types represent in service (INS),
out of service (OOS), and unknown states. These are determined by the operational and
administrative states of the SITE or MMS.
An alarm display window for an NE or SITE on the map

Each map provides an alarm display window that subscribes only to incoming alarm
messages for selected NEs or SITEs. This window allows standard alarm handling to be
performed.
Remote login via TTY window for an NE on the map

Remote login, via a TTY window for a selected NE, allows BSS GUI commands to be
sent to the NE. The responses to the commands can be monitored.
Provide resynchronization functions

The system checks the active alarm list for any unhandled alarms and retransmits any
state changes that have occurred since the previous Resync operation.

02 May 2003
68P02901W01-M
453
Network maps
GSR6 (Horizon II)
Different maps available

The following maps are available for selection:
S
One map showing the full network configuration, containing all configured nodes
and links.
One map for each BSS or RXCDR, containing all configured SITEs and links.
All other maps can be configured by the administrator.
Map modes
There are two map modes available from the View menu:
S
Device Mode displays severities according to the impact of faults on devices. For
example, a critical redundant device will produce a critical severity.
Subscriber Mode displays severities according to the impact of faults on

subscribers. For example, service, capacity or redundancy loss.
Consolidated alarm report

Consolidated alarm reports provide information about the OMC-R map so that the
operator can identify problems in the network. This feature reduces the amount of alarms
reported to the operator, and consolidates all the information relating to a failure in a
report.
Map configuration
Different maps of the network can be displayed, depending on what type of information
the operator needs to monitor. This is achieved by adding the new map configuration
data to the CM MIB through the Detailed View forms and Audit. The OMC-R GUI
provides facilities for the automated process, followed by operator input for longitude and
latitude data.
When the MIB is initially populated with data from configuration files, default maps are
created. In the absence of any geographical map background files, the maps are
displayed on a default map background consisting of a single solid colour. To use map
backgrounds other than the default, a background map, usually a geographical map, is
assigned to the map object which configures the network map.
454

68P02901W01-M
02 May 2003
The map display
GSR6 (Horizon II)
The map display

Map backgrounds
When maps are initially configured they are displayed on a default map background of a
single solid colour. A background, usually a geographical map background, is assigned to
the network map. Each map background is specified when defining the MapNode object.
This map points to a physical file describing the actual shape of the background map.
Map links
Each map link represents one or more 2 Mbit/s links between the NEs or SITEs in the
network. This is set when the map is configured. A cluster icon is used to represent a
group of icons which are too close together to be displayed separately on the map.
Alarm reporting
If an icon on a map is flashing, it indicates that there are unhandled alarms for the device
or devices it contains. Alarms from links cause both the link and the node, where the
faulty MSI/MMS is contained, to flash. The icon colour will automatically be reset to the
colour representing Clear (defaulted to green) when the operator clears the alarm, or an
alarm clear message is received from the network.
State changes
The status of a SITE or MMS in the network determines whether it is in service (INS),
that is, it is supporting (or able to support) user traffic, or out of service (OOS), that is, it
is unable to support user traffic. The device status is determined by the administrative
state (controlled by the operator) and the operational state (controlled by the NE fault
management application).
The different combinations of operational and administrative states determine whether
the node or link is INS, OOS, or has an unknown state. For example, a SITE is INS if its
operational state is enabled or busy, and its administrative state is unlocked.
The normal state of a device is INS (busy/unlocked, or enabled/unlocked for a redundant
device). An operator or the NE fault management software can take a device OOS by
issuing a LOCK command, or a SHUT-DOWN command in the case of a transceiver. A
LOCK is intrusive as it terminates all activity on the device when the command is
executed. The SHUTDOWN command permits the operator to specify a time interval
before the device changes from UNLOCKED to LOCKED state.
The map display uses different icon types to represent a change in state of devices.
Figure 4-26 shows the indications of the icons for an INS, Unknown and OOS device:
Additional information
Refer to the OMC-R Online Help facility for a complete description of the network map
display, the subscription lists that control alarm and state changes, and icon colours.

02 May 2003
68P02901W01-M
455
The map display
GSR6 (Horizon II)
Pending state
An asterisk, , on a node icon represents nodes in a pending state. Figure 4-26 shows
the map icons.
Figure 4-26 Map icons
Icon name
INS
UNKNOWN
OOS
OMC
MSC
SGSN
RXCDR
RXCDRSite
?
BSS
BSC site
BSCBTSsite
BTS site
GPRS PCU
Link
How State is
determined
INS
OpState:
Enabled
AdminState:
&
Unlocked
or
UNKNOWN
Busy
&
Unlocked
or
Any
&
Unknown
Unknown
&
Any
OOS
All other
combinations
Options:
OpState: Enabled | Disabled | Busy | Unknown
AdminState: Locked | Unlocked | Shutting Down | Not Equipped | Unknown
456

68P02901W01-M
02 May 2003
How administrative and operational state changes work
GSR6 (Horizon II)
How administrative and operational state changes work

State changes
Administrative and operational state changes are only relevant for SITEs and links on the
map. Figure 4-27 illustrates how the icons representing the SITEs or links are changed to
reflect the change in state of the physical device.
Figure 4-27 State changes on the map

Map on
operator
workstation
Icon representing BTS1 on

the map changes to oos state
GUI processor
GUI front panel
MapNode (BTS1)
GUIState
INS
UNKNOWN
Map
Mapnodes (BTS1)
Maplinks
OOS
BTS1
OpState:
Enabled
AdminState: Locked
GUIState:
INS
Disabled
CM MIB
Shutting Down Not

Equipped
Unlocked
OOS
OOS
Busy
Network OMC-R MSC
Unknown
BSS1 RXCDR BSS2

BTS1
MSI1
MMS1
Represents previous attribute setting
CommsLink
EM proxy
Represents new attribute setting
StateChangeEvent
System
processor
MAP_EVENTS
Active NSS
subscription
lists
StateChangeEvent
(Operational state of BTS1 changes to disabled)

02 May 2003
68P02901W01-M
457
How alarms work
GSR6 (Horizon II)
How alarms work

Alarm icons
Incoming alarms are reported by a flashing MapNode or MapLink icon, coloured to
represent different alarm severities. If an icon on a map is flashing, it denotes the
presence of unhandled alarms for the device or devices it represents. Alarms from links
cause both the MapLink and the MapNode containing the faulty MMS to flash and
change colour.
Figure 4-28 Alarms and how they change on the map
Icon representing BTS1 on
the map changes colour to red and starts
flashing.
MAP on
operator
workstation
Alarms icon on gui front panel starts

flashing. alarms summary window
updated.
GUI processor
MapNode (BTS1)
GUIState
Colour
Red
Yellow
Blue Pink Turquoise Green

Flashing
Yes
No
BTS1
Map
Mapnodes (BTS1)
Maplinks
Critical
ALARM 001
AlarmState: Being Handled | Not Being Handled
AlarmSeverity: Critical | Major | Minor | Warning |
Investigate | Clear
[message fields]
ALARM 002
Investigate | Clear
[message fields]
ALARM 003
Investigate | Clear
[message fields]
Represents the previous attribute setting

Represents new attribute setting
(Alarm received from

BTS 1)
458
GUI front panel
Critical alarm
event

68P02901W01-M
Not handled
CM
MIB
Alarm
information
EM proxy
Critical alarm event
MAP_ALARMS
ALM_ALARMS
Active NSS
subscription
lists
System
processor
02 May 2003
How alarms work
GSR6 (Horizon II)
Colours
The colour of any displayed icon or link reflects the severity of alarms in the device or
group of devices represented by the icon. The default colours are defined in Table 4-5.
Table 4-5 Alarm icon colours
Colour
Alarm Severity
Default
Red
Critical
ON
Yellow
Major
ON
Blue
Minor
OFF
Pink
Warning
OFF
Turquoise
Investigate
OFF
Green
Clear (no alarms)
n/a (always on)
When an icon represents a group of devices, (for example, a BSS represents all the
devices in the BSC and BTSs within the BSS) an alarm occurrence in any device within
the group is shown at the displayed icon.
In the event of alarms of different severities existing for the same device, or group of
devices the display colour reflects the most severe alarm condition.
The icon colour will automatically be reset to the Clear colour when the operator clears
the alarm or an alarm clear message is received from the network.

02 May 2003
68P02901W01-M
459
How maps are configured
GSR6 (Horizon II)
How maps are configured

Introduction to the CM MIB
The CM MIB stores a series of managed objects to which relevant configuration data is
assigned. For example, both a BSS and a Map are considered to be managed objects
requiring different data. All the GUI processors that run the Network Map communicate
with the CM MIB using an internal process called cm_mib.
Figure 4-29 shows the CM MIB showing the different groups of managed objects.
Figure 4-29 The CM MIB showing the different groups of managed objects
GRAPHIC
OBJECTS
CONFIGURATION
OBJECTS
MAP
NODE
MAP
MAP
LINK
NETWORK
OMC-R
BSS RXCDR MSC
SITE MSI MMS
RTF DRI CELL
CommsLink
Two object groups

There are two different groups of objects needed for maps:
S
Graphic objects.
Used to build the different maps, and which take their data from the configuration
objects.
Configuration objects.
Hold all the data about the physical network. There is a containment relationship
between the different managed objects.
460

68P02901W01-M
02 May 2003
Graphic objects
GSR6 (Horizon II)
Graphic objects
Graphic objects
There are three graphic objects in the CM MIB. Figure 4-30 shows the containment
relationship between the graphic objects.
Figure 4-30 The containment relationship for the graphic objects
MAP
MapNode
MapLink
Map
The Map graphic object represents a map which appears in the Map List Display menu
on selecting the Maps icon from the front panel. It defines the map name and the
background map used with it.
MapNode
The MapNode graphic object specifies the type of NE or SITE to be represented on the
map.
A MapNode can represent any of the following configuration objects:
S
OMC-R.
BSC.
MSC.
RXCDR.
BSCBTS.
BTS.
MapLink
The MapLink graphic object represents one or more CommsLinks.

02 May 2003
68P02901W01-M
461
Configuration objects
GSR6 (Horizon II)
The containment relationship between the different configuration objects is shown in
Figure 4-31. The objects are grouped into four logical groups, namely, Hardware
Devices, Software Functions, Logical Links, and Radio Frequency. This reflects the
physical configuration of the devices in the network, and determines the upward
propagation of alarms. For example, an alarm from an MSI object will also be propagated
to its parent SITE, which in turn is propagated to its parent BSS.
Figure 4-31 The containment relationship for the configuration objects

Map
ProxyCell
UserProfile
MapNode MapLink
Network
CM MIB
BSS
RXCDR CommsLink MSC OMC-R

SWInventory
NESoftware
PCU
SoftwareLoad
Hardware
Devices
Logical
Links
Cabinet CAGE Processors MSI GDS GSL GBLNSVC
DPROC
PSP
MMS
Hardware
Devices
SITE
Software
Functions
BTF
LCF
Logical
Links
OMF
RSL
Radio
Frequency
PATH
RTF
DRI
Group Group
RTF
Cabinet CAGE EAS Processors COMB KSWpair GCLK IAS
GPROC
BSP
CELL
DRI
LAN TDM MSI
CSFP
FreqHopSys
SMSCBmsg
Neighbour TestNeighbour
Handover/
Power Control
TRX
* The handover control objects are:

RelTimAdvHC, RxlevDlHC, RxlevUlHC, RxqualDlHC, RxqualUlHC, SurrndCellHC
** The power control objects are:
RxlevDlPC, RxlevUlPC, RxqualDlPC, RxqualUlPC
462

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Network
The Network configuration object represents the overall network being managed. There
is only one Network configuration object in the MIB, and it is already configured on
delivery.
OMC-R
The OMC-R configuration object represents the Operations and Maintenance Centre.
There is usually only one OMC-R object in the MIB.
SoftwareLoad
The SoftwareLoad object is used to point to a BSS or RXCDR software load currently
stored in the OMC-R. A maximum of 2 147 483 647 SoftwareLoad objects can be
contained within a SWInventory object.
MSC
The MSC configuration object represents the Mobile Switching Centre. The OMC-R does
not directly manage the MSC, but manages the links between the BSSs, RXCDRs, and
the MSC. There are usually only two of these objects in the MIB.
BSS
The BSS configuration object represents the Base Station System. Each BSS in the
physical network (maximum of 120) is represented by an object.
RXCDR
The RXCDR configuration object represents the Remote Transcoder. There are as many
of these objects as exist in the physical network (maximum of 120).
CommsLink
The CommsLink configuration object defines the two MMS ports in the different SITES
that establish the 2 Mbit/s link between the SITES.
PCU
The Packet Control Unit (PCU) configuration object manages the packet radio interface,
and also enables the interface from the BSS to the Serving GPRS Support Node
(SGSN).
SITE
The SITE configuration object represents a BSS SITE in the network. The functionality of
any given SITE depends on the devices it contains.
Hardware configuration
All the different hardware cages in a SITE are connected by a LAN, and configured as a
BSC, a BTS. SITE 0 must always contain the BSC functionality, and is configured as a
BSC or a BSCBTS. The remaining SITEs may only be configured as BTSs. There are
as many of these objects as exist in the physical network (maximum of 100 per BSS). A
RXCDR can also have a SITE 0 associated with it.
02 May 2003
68P02901W01-M
463
GSR6 (Horizon II)
Hardware devices
The Hardware Devices represent an abstract logical container class. It is used to group
the different hardware devices on the BSS.
Cabinet
The cabinet object class describes a single cabinet within the site.
Cage
The cage object describes a single cage within a cabinet.
EAS
The EAS configuration object represents the detection of a single External Alarm System
device within the site.
Processors
The processors object represents a logical container class. It provides a grouping for the
GPROC (Generic Processor Boards) BSP (Base Site Control) and CSFP (Code Storage
Facility) processors within the site.
KSWpair
The KSWpair object is used to represent a pair of KSW (Kiloport Switch board) devices
which manage a single TDM highway.
GCLK
The GCLK object represent a Generic clock board. There is one per site.
IAS
The IAS configuration object represents the detection of an Internal Alarm Systems such
as a power supply failure. There is one IAS device per cabinet.
LAN
The LAN object represents a single Local Area Network within a site.
TDM
The TDM object represents a single Time Division Multiplex highway within a site.
MSI
The MSI configuration object represents a Multiple Serial Interface (MSI) board which
controls two MMS ports. There is a maximum of 101 MSIs at SITE 0 and 51 at other
SITES.
COMB
The COMB is a general abbreviation used for a Combiner which combines two or more
RF transmissions, from a BTS transceiver control unit (TCU), for a simultaneous
broadcast to a single antenna.
464

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Software functions
The Software Functions represent an abstract logical container class. It is used to group
the different software functions on the BSC.
BTF
The BTF object represents a Base Transceiver Function. There is a single instance of
this class in BSC site 0.
LCF
The LCF object represents a Link Control Function. There is a single instance of this
class in BSC site 0.
OMF
The OMF object represents a OMF GPROC Function. There is a single instance of this
class in BSC site 0.
Logical links
The logical links represent an abstract logical container class. It provides the grouping for
the various links present at the site.
CBL
A CBL link can be configured between the BSC or RXCDR and the Cell Broadcast
Centre (CBC). This is used for downloading messages to broadcast along with other
necessary information such as repetition rate and number of broadcasts.
MTL
The purpose of the MTL is to provide a link for signalling information between the BSC
and the MSC. In the Motorola system, when local transcoding is used, this is a physical
connection between the BSC and the MSC. When a Remote Transcoder is used, the
logical MTL is made up of two physical parts; the connection between the BSC and the
RXCDR and the connection between the RXCDR and the MSC.
OML
This link is for control and communications between the BSS and OMC. The RXCDR
provides an OML for each BSC connected to it.
XBL
An XBL link may be configured between the BSC and the RXCDR for exchanging
internal Fault Management (FM) data between them.
RSL
The RSL represent a Radio Signalling Link. The RSL can only be contained within the
remote BTS in which it terminates.
PATH
The PATH object specifies the path connection between a BSC and a specific BTS site.
The path connection is described as a series of MMS connections between sites. There
can be a maximum of 10 PATH objects contained in a SITE object.
02 May 2003
68P02901W01-M
465
GSR6 (Horizon II)
Radio frequency
The Radio Frequency represent an abstract logical container class. This provides the
grouping for the various radio related objects.
RTFGroup
The RTFGroup object is used to represent a single RTF function grouping within a site. A
maximum of 6 RTFGroup objects can be contained in a SITE object.
RTF
The RTF object is used to represent a single RTF function within a site. A maximum of
25 RTF objects can be contained in an RTFGroup object.
DRIGroup
The DRIGroup object is used to represent a single DRI device grouping within a site. It
contains one or more DRIs which are connected to the same antenna and use the same
portion of the TDM highway. A maximum of 6 DRIGroup objects can be contained in a
SITE object.
DRI
The DRI object is used to represent a single Digital Radio Interface (DRI) device within a
site. It provides the interface between the DRCU and the digital portion of a BSS. A
maximum of 25 DRI objects can be contained in a DRIGroup object.
CELL
The CELL object is used to describe the cells within a BTS site. Up to 6 CELL objects
can be created under a SITE object. A maximum of 250 CELLs can be contained within a
BSS.
FreqHopSys
The FreqHopSys object is used to represent a single frequency hopping system within a
cell.
SMSCBmsg
The SMSCBmsg object is used to represent a single Short Message Cell Broadcast
(SMS CB) message within a cell.
Neighbour
The Neighbour object is used to identify a neighbour cell for a specific cell, that is, those
cells to which it can handover calls. A maximum of 64 Neighbour objects can be created
under a CELL object.
TestNeighbour
The TestNeighbour object is used to describe the test neighbour cells for a specific cell.
One instance of this class represents one test neighbour cell.
Handover control
Handover Control objects are RelTimAdvHC, RxlevDlHC, RxlevUlHC, RxqualDlHC,
RxqualUlHC and SurrndCellHC. These objects describe the handover algorithms based
on certain criteria. For more details refer to the OMC-R Online Help.
466

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Power control
Power Control objects are RxlevDlPC, RxlevUlPC, RxqualDlPC and RxqualUlPC. These
objects describe the power control algorithms based on certain criteria. For more details
refer to the OMC-R Online Help.
ProxyCell
The ProxyCell object represents CELLs outside the current PLMN. A maximum of 500
ProxyCell objects can be contained in a SITE object.
UserProfile
The UserProfile object represents an OMC-R user who uses the OMC-R GUI. A
maximum of 256 UserProfile objects can be contained in an OMC-R object.
Automatically created network objects

The network objects which the cmMIB process creates automatically are as follows:
NESoftware
An NESoftware object is automatically created when a BSS or RXCDR object is created.
SWInventory
An SWInventory object is automatically created when an OMC-R object, with the active
flag set to TRUE, is created.
MMS
An MMS object is automatically created when an MSI object is created.
TRX
A TRX object is automatically created in a CELL object when an RTF object of type
BCCH is created at a SITE with its carrier attribute assigned to the relevant CELL.
Source
A Source object is automatically created when a Neighbour object is created if the CELL
it identifies exists. Otherwise, a Source object is automatically created when the CELL
object is created.

02 May 2003
68P02901W01-M
467
GSR6 (Horizon II)
Automatically created map display objects

The map display objects which the cmMIB process creates automatically are as follows:
Map
A Map object is automatically created when a Network, BSS or RXCDR object is
created.
MapNode
A MapNode object is automatically created when a BSS, OMC-R, MSC, RXCDR or SITE
object is created and must be associated with an object of the relevant type.
MapLink
A MapLink object is automatically created when a CommsLink object is created.
468

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Periodic Supervision of Accessibility (PSA)
Periodic Supervision of Accessibility (PSA)

Definition of PSA
Periodic Supervision of Accessibility (PSA) periodically sends messages to BSSs
requesting information on their current state. This verifies if the BSSs are operational or
not.
PSA failure
If a BSS fails to respond to a PSA request for its status, the OMC-R will generate an
alarm for that BSS. This alarm indicates that the BSS failed to respond to a message
requesting its status, and may be indicative of a problem at the BSS. The OMC-R
continues to send messages periodically to the BSS requesting its status. On receipt of
a response message from the BSS, the OMC-R changes the alarm severity of the
message to Clear.
An alarm is also generated when the BSS informs the OMC-R that it is not operational.
The OMC-R continues to send messages periodically to the BSS requesting its status.
On being informed that the BSS has returned to operating correctly, the OMC-R changes
the alarm severity of the message to Clear.

02 May 2003
68P02901W01-M
469
Disk usage exceeded
GSR6 (Horizon II)
Disk usage exceeded

System processor partition full
An alarm is raised when either of two (upper and lower) threshold values of disk usage
are exceeded on the /,the /home, the /usr, and the /usr/gsm/ne_data
partitions of the System Processor.
The System removes any logfiles older than three days from the $OMC_TOP/logs
directory using routine maintenance cron jobs, or if the upper disk usage threshold is
exceeded. The threshold value should return to the default value of 90%.
The file $OMC_TOP/config/global/FM_audit.CNFG contains the values that are
used for setting the timers for each audit and disk usage limits. These values are set at
installation time and can only be changed by the system administrator.
Further information
For information on setting the related parameters, see Maintenance Information: Alarm
Handling at the OMC-R, (68P02901W26).
470

68P02901W01-M
02 May 2003
DataGen
GSR6 (Horizon II)
DataGen
Introduction to DataGen
DataGen is a GSM product used to create BSS databases off-line. DataGen can store
past, current, and future versions in an Informix database. These databases can be
transferred to the OMC-R, then they are downloaded to the live BSSs. DataGen runs on
its own SPARC and can be integrated with the OMC-R if they are both on the same LAN.
DataGen is generally used to make major changes to a network, for example, upgrades
to the BSS software, frequency replans, and network expansion. Figure 4-32 shows the
DataGen configuration in a GSM environment.
Figure 4-32 DataGen in a GSM environment.

Data Gen
NMC
OMC-R
OSI
Local Area Network

System
Processor
Network Management
Centre Gateway
Processor
BSC
Operator
Workstations
X.25
BSC
BSC
BSC

02 May 2003
68P02901W01-M
471
DataGen
GSR6 (Horizon II)
DataGen configuration management

DataGen provides the user with the capability of performing off-line configuration of
Motorola GSM network entities (NEs). The Informix database contains two types of
information:
S
A representation of the information required to create a Sysgen script for all

supported BSS releases.
Included in this are details relating to syntax, parameters, elements, and their
associated ranges for the GUI commands in the Sysgen script.
Configuration information for a specific BSS area.

These areas are identified by country or network, name, software release, and
configuration number. The configuration number allows multiple BSSs to exist
within the DataGen database.
Figure 4-33 shows the DataGen main window.

Figure 4-33 DataGen main window
Off-line MIB
Figure 4-34 shows the Off-line MIB, which is used to create new networks, visualise, and
validate networks before deployment into a live network. It has a common user interface
with the online OMC-R. BSS binary files are used to create the network which is
displayed as a tree-like representation called the Navigation Tree. It is possible to update
multiple BSS binary files simultaneously, for example, propagating neighbour changes
from one BSS binary file to another.
The Navigation Tree allows:
S
Graphical editing of configuration management.
Neighbour propagation.
An interface to radio refrequency planning tools.

Figure 4-34 Off-line MIB front panel
GSR 4.1 1.6.1.0
472

68P02901W01-M
02 May 2003
Chapter 5
BSS software release features

02 May 2003
68P02901W01-M
51
GSR6 (Horizon II)
52

68P02901W01-M
02 May 2003
Introduction to BSS software release features
GSR6 (Horizon II)
Introduction to BSS software release features

In this chapter
This chapter summarizes the features of the Motorola BSS software releases. Motorola
GSM products are continually being updated. Releases of software before GSR2 were
identified by four-digit release numbers, such as 1.2.1.1. After the 1.4.1.x release, the
numbering system was revised, and release 1.5.0.x has been renamed GSR2.
This chapter describes the main features of each BSS software release:
S
BSS software release 1.1.1.0.
BSS software release 1.3.0.x.
BSS software release GSR2.
BSS software release GSR4.1.
BSS software release GSR5.1.
BSS software release GSR6 (Horizon II).

02 May 2003
68P02901W01-M
53
BSS software release 1.1.1.0
GSR6 (Horizon II)

Release 1.1.1.0 features
Table 5-1 summarizes the features of software release 1.1.1.0.
Table 5-1 Release 1.1.1.0 features
Feature
54
Description
Teleservice 11
Compliant with GSM 02.03 for speech, data and signal

transmission from the PSTN/ISDN.
Connectionless call
processing
Provides the functionality for dialogue between the

MSC and MS.
MTP
Part of the MSC-BSS A interface. Supports point to

point signalling, compliant with ITU-TSS SS7.
SCCP
Part of the MSC-BSS A interface. Compliant with

ITU-TSS SS7 and ITU-TSS Q.711-Q.714 and GSM
08.06 para 5.2 - para 5.5.
BSSAP
Part of the MSC-BSS A interface. Comprises two

distinct parts.
BSSMAP, compliant with GSM 08.08 para 3.
DTAP, compliant with GSM 08.06.
RR status
Sent by MS or network, can contain error conditions

(refer to GSM recommendation 4.08).
Multiplexing
Compliant with GSM 05.02, supports logical channels

for full rate speech channels.
Layer 3
Specifies the procedures used at the radio interface for

call control, mobility management and radio resource
management.
Modified Abis (Mobis)
Reduces 2 Mbit/s link traffic by increasing BSS

processing in the BTS.
MMI entry/response at local

TTY
Compliant with GSM 12.01, 12.06 allows command

entry and printing of responses and alarm messages
for the local network element.
System change control

administration
Provides services for the management and

administration of configuration or data changes.
Allows operating versions of hardware and software

components to be managed and tracked.
Limited change control
Provide in pre-op, compliant with GSM 12.06.
Local user validation
Provides security management of user IDs.
Alarm and status reporting
Reports alarms to the local TTY.
Cell capacities
Set at 60 cells per BSS.
Database site capacities
Can be BSC, BTS or BSC+BTS to a maximum of 50

per BSC.
BSS capacities
Set at 40 sites, 60 cells and 75 RCUs per BSS
Performance statistics
Provides measurements to GSM recommendation

12.04 and Motorola unique measurements.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Feature
Description
Collect limited stats
Provides a variety of statistics actions using MMI

commands.
Minimal daisy chain
Provides straight line open loop facility for BTSs.
XCDR
Allows configuration of remote XCDR.
16 k terrestrial circuits
Supports terrestrial circuit for a remote XCDR through

existing MMI commands and CM.
Classmark update
Call processing feature that allows the MS to indicate a

classmark change to the rest of the network.
Dynamic timeslot
reconfiguration
Call processing feature that allows timeslots to be

reconfigured as requested.
Packaging page access grant

messages
Call processing feature that allows multiple information

transfer in one message
Handover queuing
Call processing feature allowing queuing of messages

during and internal handover. Refer to GSM
recommendation 8.08.
Resource allocation
Call processing feature allowing the BSS to notify the

MSC of radio resources available on request. Refer to
GSM recommendation 8.08.
Call queuing
Allows call queuing until resources are available,

subject to pre-set time constraints. Refer to GSM
recommendation 8.08.
Remove SCCP piggy backing
Removes handover request from connection request

on SCCP.
Flexible ID format
Allows variable length ID elements as defined in GSM

recommendation 8.08
Call tracing
Initiates a call trace via an MMI command.
Fault recovery cleanup of

affected calls
Cleans up the BSC resources on restart of the BTS,

independent of the BSC.
Allocation of TDM resources
Supports allocation of timeslots when a radio carrier is

added.

02 May 2003
68P02901W01-M
55
GSR6 (Horizon II)

Table 5-2 summarizes the features of 1.1.2.0.
Table 5-2 Software release 1.1.2.0 features
Feature
56
Description
BSS-OMC agent statistics

reporting facility
Statistics can be reported to the OMC based on X.25

(without FTAM or CMISE).
Additional statistics provided
A series of measurements as required by GSM 12.04,

and some Motorola-unique measurements are
provided.
Collect and provide access to

listed statistics
Provides additional functionality for statistics values via

MMI commands.
BSC-OMC agent: Software

reporting
Reports software alarms to the OMC from the BSC.
BSC-OMC agent: Hardware

reporting
Reports hardware alarms to the OMC from the BSC.
Diversity option commands
Turns On or Off the diversity option for a site using an

MMI command.
Support antenna diversity

(BTS4-D)
Modification to the BSS software to provide support for

BTS4-D.
Fault management
Provides enhanced fault detection and management.
Fault reporting to the OMC
Collects alarms within the BSS and reports them locally

to the OMC.
Maximum system
configuration
Supports a database up to 6 Megabytes in size.
MMI commands
MMI commands are added or enhanced to support the

diversity option, XCDR maintenance and BSS
database control.
System commands
System commands are added or enhanced to support

fault management and configuration management.
Device management of a site
Supports a number of implementation commands for a

site.
Device management of BSS

devices
Supports implementation commands for BSS devices.

Provides minimal fault isolation and recovery.
Device management
operations
Supports a number of management operations for

implementation of devices.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

Function
Description
Handover algorithm - D1
Supports algorithm as specified in FEIN specifications

for Detecon (FS 05.08.1.1 (2.2), Chapter 3.3.1).
Force OMC download of

EEPROMs
Forces an OMC download of GPROC flash EEPROM

manually.
Device management of BSS

device (EAS)
Supports implementation commands on the EAS

device PIX.
System commands
Supports fault management and configuration

management.

02 May 2003
68P02901W01-M
57
GSR6 (Horizon II)

Feature
58
Description
BTS daisy chain with return

loop
The return loop feature, now known as a closed loop,

adds a closed loop capability for open loop BTS
configurations.
Signalling Point Inaccessible
SPI implements the BSSMAP procedures for signalling

point inaccessible and user OOS.
Remote tuning combiner
Allows combination of multiple RCUs.
Flash EEPROM
Prevents accidental write to the flash EEPROM.

Provides a downloadable bootstrap flash EEPROM for
GPROCS.
EAS enhancements
Includes optocoupler number and alarm text in EAS

optocoupler alarms sent to the OMC.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

Feature
Description
Advanced RCU download
Reduces BTS outage time during BTS initialisation by

improving overall DRI/RCU download and configuration
time. The time reduction increases as the number of
DRI/RCUs increase at a site.

02 May 2003
68P02901W01-M
59
GSR6 (Horizon II)

Feature
510
Description
Baseband hopping
Switches information generated by the channel

coding/interleaving function on the DRI to the
appropriate RCU.
Synthesizer hopping
Re-tunes RCUs in real time from frequency to

frequency.
Data services full-rate traffic

channels
Supports data services on full-rate radio traffic

channels.
Support alternate speech and

data
Allows MSC/BSS coordinated switching between

speech and datausing in-call modification procedures.
GPROC device management
Removes the need for BTS reinitialisation when RSL

links to the BSC are interrupted.
Device management of
GPROCs
Ensure synchronization of BSC and BTS call

processing after loss of all links or reinitialisation.
Cross load time improvement
Reduces the time to cross load between GPROCs at a

site.
Paging distributor
optimization
Ensures that only one message is sent to a BTS per A

interface paging message.
Short message service, point

to point
The BSS supports Short Message Service (MS

originated and MS terminated). Motorola will be phase
1 compatible as the BSS responds to a SAPI n clear
with a SAPI n clear complete although the SAPI 3
connection is not torn down.
Simple flow control
Provides BSS overload managment by barring MS

access classes as necessary when call information
block usage reaches a predetermind threshold.
Intra-BTS synchronized
handover
Allows handovers that do not require the BSS to send

a physical information (timing advance) message to the
MSC.
LAN device managment and

swap over
Provides managment for the LAN hardware devices

and enables switching between the two LAN hardware
loops that interconnect all GPROCs at a BSC or BTS
site.
Remote BTS add and delete
Provides an add and delete function allowing a BSC to

support an open or closed loop of BTSs.
Remote transcoder to BSC

link (XBL)
Notification of failed traffic circuits is sent from the

RXCDR to the BSC, and the BSC disables these
circuits by sending the appropriate blocking messages
to the MSC.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Feature
Description
System audits processes
The System Audits Processes (SAP) detects faulty or

degrading hardware and software (through the use of
audit tests) and notifies the Alarms handling software
of the condition. The SAP does not take any recovery
or further diagnostics action due to a fault. This is left
up to the Fault Translation Process (FTP) upon receipt
of the alarm indication.
Audit control
Provides SAP features using MMI commands at the

OMC or local MMI terminal.
Audits of soft devices
Verifies correct operation of the software proceeses

within a GPROC.
Audits of boards
Verifies correct operation of the hardware devices

within the BSS.
Audits of buses
Verifies correct operation of the communication busses

within a BSS site.
Database notification
The database notification feature ensures that any

operator-initiated change to data in the CM database is
distributed to all in-service GPROCs and that the
appropriate devices are notified of the change.
Data catagories
Handles changes to type 2 and 3 data within the CM

database.
BSS/OMC periodic
supervision of accessibilty
Enables periodic polling of the BSS from the OMC. An

alarm is generated if the BSS does not respond
correctly to the poll.
GCLK fault management
This feature provides fault management of the GCLK

device, together with more complete GCLK alarm
information than was previously available. Operator
commands are also provided to control which of the
two GCLKs is active.
Save alarm status upon OML

outage
Allows the BSS to store alarms which may be

generated within the BSS while OMC is inaccessible.
Alarm clearig and throttling
Alarms reported by the BSS can be categorized as

either intermittent or constant. The alarm clearing and
throttling feature clears constant alarms when the
underlying fault is no longer present and throttle
intermittent alarms which repeat frequently.
Multiple CCCH
This feature allows multiple CCCH timeslots to exist on

successive even timeslots on the BCCH carrier.
RF queuing priority without

pre-emption
Positions information elements in priority order in the

waiting queue if the queuing indicator is set to Allow.
The queue assignment requesrt is rejected if the
queueing indocator is set to Not Allowed.
KSW expansion
Up to four KSWs can be connected together to support

up to 4096 TDM timeslots at a site. The BSS
continues to support redundant KSWs. For
redundancy a KSW is required for each KSW required
for capacity.

02 May 2003
68P02901W01-M
511
GSR6 (Horizon II)

Table 5-7 summarizes the feature of 1.2.0.3.
Feature
Alarm and status
synchronization
Description
The BSS supports future development of the OMC
alarm and status synchronization feature within the
OMC. Impacted areas are Fault Management (CA and
FTP) and the OMC interface.The alarm and state
synchronization feature provides a mechanism for
synchronization of the OMC and BSS/RXCDR device
status. Status information is composed of both alarm
and device state information.
Normally, the BSS/RXCDR sends alarms and device
state change events to the OMC as they occur, so the
OMC keeps up to date with changes to the network
element device status. However, a mechanism for
device status synchronization is required both at OMC
initialization time, and after a failure of the OMC,
BSS/RXCDR or the links between them.
Synchronization can be initiated via operator request
OMC init, or it can be set up to occur automatically at a
configurable interval.
512

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

Table 5-8 summarises the features of 1.2.2.0.
Feature
Description
Switchover improvement
When a 2 Mbit/s link between a BSC and a remote

BTS fails, traffic is switched to a redundant 2 Mbit/s link
if one is available. The switchover improvement
feature reduces the time taken to switch links, thus
minimising any break in voice or data transmission.
GCLK synchronization
Ensures that air interface data timing and RF

frequencies remain within the GSM recommendations
and eliminates frame slips over the E1 interface.
Database level number
The database level number feature keeps a database

level number for each site in the BSS. Database level
number increments are sent to a remote BTS only if
the database changes for that site. This feature will
help prevent unnecessary database downloads to
remote BTSs and also reduce the message traffic in
the BSS.
BSC-BTS download
compression
This feature reduces the time taken by a BSC to

download the CM database to its BTSs. The BSC
compresses the information prior to downloading it,
and the BTS decompresses it on receipt.
Checksumming procedures prevent data loss or
corruption during compression and decompression.
Preventative cyclic
retransmission
Preventive Cyclic Retransmission (PCR) involves the

retention of a signal unit at the transmitting terminal
until acknowledgement is received from the receiving
terminal. During the period when there are no new
signal units to be transmitted, the transmitting terminal
cyclically retransmits all the signal units that have not
yet been acknowledged by the receiving terminal.
Multiple digital host processor
The multiple DHP cage feature allows more than one

DHP per cage.
Timeslot reservation
This feature allows ranges of timeslots on specified 2

Mbit/s links to be barred from use by a BSS (reserved)
using an MMI option or the OMC.
Internal alarm system
Monitors the status of the power distribution unit (PDU)

in a BTS and generates an alarm in the event of a
fault. The feature also provides for any alarms detected
by the digital power supply modules (DPSMs) in a cage
to be reported.

02 May 2003
68P02901W01-M
513
GSR6 (Horizon II)

Feature
514
Description
TopCell alarm enhancement
The BSS software supports the additional alarms that

are generated for each TopCell cabinet.
TopCell base
The BSS software supports the new TopCell hardware.

The TopCell product is a complete cell site (BTS).
TopCell requirements
Defines the new requirements for a TopCell site.
Six carrier BTS shelf
The BSS supports a six carrier BTS shelf for DRCU3.
ExCell 6
The BSS supports a six carrier version of the ExCell

product.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

Reason for this release
Release 1.2.2.3 addresses an internal problem that could pose a potential risk to
customers with medium to large configurations. This release supersedes release 1.2.2.2
and should be used instead of release 1.2.2.2.

02 May 2003
68P02901W01-M
515
GSR6 (Horizon II)

Important information
GSM BSS 1.2.3.0 is released on a limited basis to support DCS1800 First Office
Application (FOA). The extent of functionality supported by this release is limited to
basic cellular phone service. The following feature functionality is excluded until sufficient
testing has been accomplished to release these features for use in the DCS1800
environment:

Feature
516
Description
Excluded features
The following features are excluded from this release:

1800 MHz Remote Tuned Combiner (RTC).
DTX (Discontinuous Transmission).
Short Message Service (SMS) point to point.
Short Message Service (SMS) cell broadcast
single background message.
Data services alternate speech; data services
full rate.
Frequency hopping, baseband; frequency
hopping, synthesizer.
A BSS operating with BSGSM 1.2.3.0 in GSM900
mode has not been qualified to operate with another
BSS in DCS1800 mode, while both BSS are connected
to the same OMC. It is recommended that all BSS
connected to a single OMC remain homogenous with
respect to the radio spectrum they serve.
Fault isolation (enhanced)
This feature provides enhancements to existing fault

isolation capabilities for the DRI and GPROC devices.
Short message service, cell

broadcast (single background
message)
This feature is a means of unilaterally transmitting data

to mobiles on a per cell basis, by use of a Cell
Broadcast Channel (CBCH). This feature provides a
subset of the full GSM functionality. In particular, the
BSC interface to the CBC is not supported. Instead, a
single operator defined message may be entered using
appropriate MMI command. The full functionality as
defined by GSM will be implemented in a later release.
Real time traffic monitoring
This feature enhances the BSS and OMC to allow real

time traffic display of channels in use on both the A
interface (terrestrial circuits) and air interface (radio
channels).
Display of hardware revision

level from MMI
Operators use this feature to obtain the hardware

version number of certain boards, using an MMI
command. Alarms are reported with the hardware
version number of the board originating the alarm, if
the alarm originates from either a GCLK, GPROC,
DHP, BSP, BTP, KSW, MSI, XCDR or DRI.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Feature
Description
RCU ID MMI feature
Operators use this feature to display the serial number

of any RCU/DRCU, and the hardware version number
of its component boards. RCU/DRCU alarms are
correlated to a specific RCU/DRCU, using the
RCU/DRCU serial number.
BTS battery conservation at

main power failure
This feature enhances BTS battery backup operation

by selectively stopping RCUs from transmitting, so that
power is conserved. This extends the available BTS
battery time.
TopCell Alarm Enhancement
The BSS software supports the additional alarms that

are generated for each TopCell cabinet as follows:
Door open alarm.
PSU failure alarm.
Main power failure alarm.
DCS1800 frequencies
This feature provides the software support for the new

RF hardware being developed to operate in the 1800
MHz frequency band.
Update of LAN microcode
Due to a change to the TMS380C26 LAN adapter

device on the GPROC board, this release contains an
update of the vendor provided microcode for the
device.
Six carrier BTS shelf
The BSS supports a 6 carrier BTS shelf for DRCU3.
ExCells
The BSS supports a 6 carrier version of the ExCell

product.
Preventative Cyclic
Retransmission on C7-MTP
MSC-BSC A interface
The BSS supports Preventative Cyclic Retransmission

(PCR) error correction for connecting to the MSC (the
A interface) via a satellite link.
TopCell base
The BSS software supports the new TopCell hardware,

incorporating DCS1800 components. The TopCell
product is a complete cell site (BTS)
TopCell requirements
Defines the new requirements for a TopCell site.

02 May 2003
68P02901W01-M
517
BSS software release 1.3.0.x
GSR6 (Horizon II)

Release 1.3.0.x features
Release 1.2.3.0 features integrated into 1.3.0.x are included for customers upgrading
from release 1.2.2.3.
Table 5-11 summarizes the features of software release 1.3.0.x.
Table 5-11 Release 1.3.0.x features
Feature
518
Description
Large BSS configuration

capacity
This feature introduces capacity support for a system

consisting of 50 sites, 90 cells, and 90 active RCUs
(TRXs).
Fault isolation (enhanced)

DRI and GPROC
This feature provides enhancements to existing fault

isolation capabilities for the DRI and GPROC devices.
KSW, TDM and TBUS

management
Provides control for configuration of the listed devices

and allows switching of between TDMs without
re-booting the system.
Manage inactive GPROCS
This feature enhances the operations and maintenance

of GPROC devices.
BSC LCF swaps
Allows switching of logical links to the MPT layer 2

physical links if an MTL GPROC fails during
transmission.
BSC OMF
The BSS provides the capability to independently

handle OMF function (OMF GPROC) failures without
impacting the remaining GPROCs at the BSS site.
This capability does not prevent an interruption to call
processing service.
BTS DHP swaps
Shifts functionality of the RF carrier from a failed DHP

to a healthy device, thus limiting the effect of the failed
DHP recovery to a subset of the carriers at the
BSS/BTS site. All carriers on the failed DHP are
disabled and re-enabled on other surviving
DHPs/BTP/BTF within the same cage, if there is
available capacity.
BSC BTF swaps
Allows BTF swapping to ensure no loss of function

resources if a GPROC fails.
Code storage facility

processor
The Code Storage Facility Processor (CSFP) supports

propagation of new software instances with reduced
system downtime. Optional CSFP falback is also
provided.
Encryption algorithm, A5/2 or

Null
The BSS supports basic encryption operation using the

A5/2 and Null encryption algorithms. Encryption
provides security for user speech, data and signaling
information at the physical layer. Encryption and
decryption must be deployed at both the BSS and MS.
Multiple versions of A5
algorithm
The BSS supports the parallel operation of A5/1, A5/2

and Null encryption algorithms. The operator is able to
set the priority/order in which the algorithms shall be
chosen by the BSS. This order can be set at sysgen
time or via MMI command.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Feature
Description
Restrict optional feature
The BSS restricts use of optional features unless

purchased by the customer.
Short message service, cell

broadcast (single background
message)
Defines the operator controlled, Short Message

Service, Cell Broadcast (SMS CB) feature, which is a
means of unilaterally transmitting data to mobiles on a
per cell basis, by use of a Cell Broadcast Channel
(CBCH).
Emergency call pre-emption
Allows emergency calls to pre-empt all other calls,

even if system resources are utilized.
GSM phase 2 air interface/A

interface
Delivers part of an operating system upgrade, or

overall application package, for BSS support of GSM
phase 2 compliant messaging over the A and air
interfaces.
BSS signalling
Provides BSS signalling compatibility with phase 2

GSM, EGSM and DCS1800 systems. Also maintains
phase 1 GSM system compatibility.
Phase 2 compliant network

entities
Supports both phase 1 and 2 GSM mobiles over the

network.
Dynamic extended paging
Allows dynamic extended paging to be enabled through

MMI commands. Also allows automatic dynamic
extended paging in overload conditions.
Display of hardware revision

level
Allows display of version numbers or serial numbers of

hardware components.
BTS battery conservation

after main power failure
This feature enhances current BTS battery backup

operation by automatically stopping RCUs from
transmitting, so that power is conserved. This extends
the available BTS battery time. The non-BCCH
carriers are disabled before the BCCH carriers using
an algorithm in fault management the extent of which is
controlled by MMI.
DCS1800 frequencies
Supports the signalling required to operate in the

DCS1800 frequency bands.
DCS1800 hardware
Supports the RF hardware required to operate in the

DCS1800 frequency bands.
MSI-2/T1 signalling support

for PCS1900
This feature introduces support for PCS1900

configurations. The BSS will have the functional
capability to operate as both GSM900 and PCS1900
configurations.
Preventative cyclic
retransmission
The BSS supports Preventative Cyclic Retransmission

(PCR) error correction for connecting to the MSC (the
A interface) via a satellite link.
Network configuration
management
This feature provides the mechanism(s) to support

configuration management from the OMC using a
management interface to the BSS. Also includes
support of alarm and status synchronization.
Dual OML download
The redundant OML link supports load sharing for

downloading from the OMC providing BSS default
requirements are met.

02 May 2003
68P02901W01-M
519
GSR6 (Horizon II)
Feature
520
Description
Real time traffic channel

monitoring
This feature enhances the BSS and OMC, to allow real

time traffic display of channels in use on both the
A interface (terrestrial circuits) and air interface (radio
channels).
Transcoder downloadlink
volume control
This feature provides for an audio uplink and downlink

volume control offset on a per BSS basis.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

Feature
GCLK synchronization
Description
This is a standard 1.4.0.0 feature which enables any
current generation SITE to be configured so that it can
synchronize its GCLK to a known good clock source
in an uplink SITE via an E1 or T1 link.

02 May 2003
68P02901W01-M
521
GSR6 (Horizon II)

Table 5-13 Release1.4.0.1 features
Parameter
522
Description
Preserve RCU/SITE
calibration
Enables all types/versions of a malfunctioning radio

channel unit to be replaced without the need to remove
the Cell from service, in Cell configurations with two or
more radio channel units.
Indication of flow control

invocation
Provides a new Cell level statistic,

FLOW_CONTROL_BARRED, which measures the
duration for which channel access to the cell is
unavailable to any access class.
GSM short message service
The Motorola BSS supports GSM Short Message

Service - Cell Broadcast (SMS CB). Mobile
Subscribers with access to the short message service
are able to receive alphanumeric information messages
at any time while their Mobile Station (MS) is in contact
with a BSS.
SMS - Cell broadcast:

multiple background
messages
Enables the BSS to directly support SMS Cell

broadcast for single or multiple (up to four)
alphanumeric information messages to be sent to any
suitably configured MS.
SMS - Cell broadcast centre

support
Supports the use of a third party SMS Cell Broadcast

Centre (CBC) on the Motorola GSM network. The BSS
database and MMI commands have been modified to
support this feature.
Added nailed connections

(optional)
Enables non-GSM connections used by third party

services, such as, a paging network or analogue
mobile phone network, to share the use of the E1 or T1
links through a BSS without the need for external
multiplexing equipment. The existing Timeslot
reservation feature is modified to enable the reserving
of timeslots on any E1 or T1 link. The RESERVE
operation is currently allowed for MMSs on a PATH
only.
Remote network device

lock/unlock
Enables BSS device administration to be performed by

an OMC operator via the OMC GUI when carrying out
Fault Management (FM) and Configuration
Management (CM) procedures. A device
operational/administrative state report is possible from
a new window, Contained Devices for Selected Node,
which can be selected for any BSS, RXCDR, or SITE
on either the network maps or the navigation tree at
the OMC GUI. Also reduces the need for a OMC BSS remote login in order to perform either FM
activities or for Configuration Management activities

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

Function
Description
Software support of M-Cell2/6 This feature introduces BSS software support of the
GSM for 900 MHz
core M-Cell hardware, plus MCU, NIU and TCU
support.
Software support of M-Cell2/6 This feature introduces support of DCS1800 with both
GSM for 1800 MHz
the M-Cell2 and M-Cell6 BTS hardware platforms.
M-Cell EGSM
This feature introduces an EGSM-capable Transceiver

Control Unit (TCU) at 900 MHz. A TCU combines the
Radio Subsystem, DRI and DRCU functions into a
single package.
TCU backwards compatibility
Enables older generation BTSs to operate the current

TCU.
RSS functionality port to

carrier equipment (TCU)
M-Cell
This feature provides for the porting of RSS and DRI

functions to the Transceiver Station Manager (TSM)
board, which resides in the TCU.
Recovery escalation (M-Cell)
A new soft_reset command is available for M-Cell

BTS SITEs only. A soft reset is defined as a reset
where no equipment requires a code load and the reset
switch of no piece of equipment has been tripped. No
object comparisons or checksums are done at a soft
reset. This fulfils the requirements of the Recovery
escalation (Roadmap ID 31240) feature.
M-Cell6 remote tuner

combiner (900 MHz only)
This feature comprises BSS software support of a

Remote Tuning Combiner (RTC) for an M-Cell6 at 900
MHz only.
M-Cell6 receive matrix (900

MHz only)
This feature introduces an Extended GSM

(EGSM)-capable receiver RF matrix, which supports
up to six carriers in a single cabinet.
BSC CSFP redundancy
This feature provides for BSS software support for

equipping two Code Storage Facility Processors
(CSFPs) at the BSC to provide redundancy.
M-Cell hardware impact on

BSU-BTS
This requirement provides for BSC support of the new

M-Cell hardware with no degradation in service at the
BSC, except for outages necessary for interconnection
purposes.

02 May 2003
68P02901W01-M
523
GSR6 (Horizon II)

Feature
524
Description
M-Cellmicro GSM900
Software support for the M-Cellmicro site for GSM900

operation is provided in this release.
Low power DCS1800

BTS-site M-Cellmicro
Software support for the M-Cellmicro site for DCS1800

operation is provided in this release.
DCS1800 mast mounted

preamplifiers
An independently powered masthead preamplifier for

DCS1800 only. The preamplifier is manually configured
on-site. Preamplifier power failure and device failure
are reported through a single EAS alarm.
Optional filtering for front end
This feature is a receive bandpass filter with a narrow

specification specifically designed for when ETACS
frequency spectrum is used in conjuncture with a GSM
network.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

Feature
Description
Transient alarm handling
Enables the BSS software to perform more verification

and filtering of fault indications, to eliminate transient
alarm messages from the Transcoder TRAU, the RSL,
XBL and clock failures. The main impact of this feature
is that it decreases the number of alarms reported by
the BSS. This results in less alarm handling required
at the OMC.
Multiple trigger call trace

events
Enhances existing Call Trace functionality by providing

a finer trigger scope for call trace. This feature allows
triggers to be set on a Cell level and multiple Cell level.
All current triggering capability is supported on a per
Cell or per BSS level.
BSS level trace events - RF

failure (RF loss)
Enhances existing RF failure trace functionality by

providing the option to enable RF loss reporting on a
per cell basis (previously it was BSS level). It also
provides the facility to forward the RF failure trace
information via the event interface to the OMC
MSI-2 board with E1/T1
MSI-2 boards can be now ordered with either T1 or E1

interconnections. The software support at the BSS and
OMC is already available to support this.
Direct retry
Redirects new traffic when a Cell is congested resulting

in the new call being moved to the next most suitable
Cell.
Congestion relief: directed

retry altenative
An alternative to Directed Retry for the case of a

congested cell. This feature differs in that it chooses
the best candidates from all existing calls in the cell to
be moved to the alternate cell, thus freeing TCHs in the
congested cell.
Satallite A interface support

(optional)
Provides the BSS software support transmission of the

A interface via satellite.
Satallite Abis support

(optional)

Abis interface via satellite.
Optional level 3 password
Provides the facility for the BSS MMI security level 3

password to be controlled by the OMC operator.
All channels at full power
Sets all the call channels in the Cell to broadcast at a

constant power, the power level configured as the
maximum transmit power allowed in the Cell. This can
be used for worst case interference monitoring for
network optimization.

02 May 2003
68P02901W01-M
525
GSR6 (Horizon II)
Feature
526
Description
Fast initial MS power down

(optional)
Allows the initial power down of the Mobile Station

(MS) to be set so that the MS power is reduced quicker
than the standard ramp down time. When this feature
is enabled a separate power control procedure powers
the MS down rapidly when the BSS detects that the
signal strength of the MS is above the specified trigger
threshold.
Concentric cells (optional)
Used in GSM networks with constrained frequency

allocations, to increase network capacity by adding a
layer of Cells (known as minicells) on top of the
existing network.
Cell level call trace events
Enhances existing call trace functionality by providing

the option to forward call trace information to the
OMC-R. This information takes the form of new event
messages which the OMC-R then stores, as an
alternative to or in addition to sending it to the MMI.
Once sent to the OMC-R, the call trace data is stored
in a log file.
Link balance verification

statistics
The Link balance verification statistics feature will

identify those carriers which have unbalanced uplink
and downlink signal strengths. This feature supports
optimization activities.
Handover performace
statistics enhancements
Provides a package of enhanced handover

performance statistics which reduce network
optimization effort and time.
15,000 TCH support 1475

platform
Provides support for 15,000 traffic channels in

networks where the OMC-R is deployed with a Tandem
Integrity 1475 System Processor. Existing OMC-R
systems deployed with Tandem Integrity S300 System
Processors will continue to support 10,000 traffic
Enhanced GSM 12.04

statistics compliance
Enhanced GSM 12.04 statistics compliance feature,

ensures that the compliance of statistics to the GSM
12.04 recommendations will be improved, with
additional OMC-R Key Statistics reports and a package
of additional BSS statistics.
NIU-T1 support for M-Cell

sites
Provides the T1 NIU and T1 NIU-m boards to

accompany the E1 NIU and E1 NIU-m boards. M-Cell
BTSs can now support either T1 or E1
interconnections.
M-Cell2/6 MCU redundancy

(phase 1)
Provides the information required to install an M-Cell

site to optimize MCU redundancy.
Phase/frequency lock
(phase 1)
Provides enhancements to the 1.4.0.x feature, Generic

CLocK (GCLK) synchronization.
Synch boot
Sync boot is a 1.4.1.1 feature which provides

enhancements to the 1.4.0.x feature, M-Cell series
software support.

68P02901W01-M
02 May 2003
BSS software release GSR2
GSR6 (Horizon II)

GSR2 features
Table 5-17 summarizes the features provided in the BSGSM-GSR2 release with
OMC/BSS software support.
Table 5-17 Release GSR2 features
Feature
Description
GPROC2
Supports the introduction of the GPROC2. Because of

the increased reliability of the GPROC2 board, there
will be a decrease in the BSS unavailability due to
unplanned outages. Increased reliability is provided by
the error correcting RAM on the GPROC2 board.
Cell level/carrier level tracing
Enhances the existing Call Trace capabilities available

in the BSS.
Call trace via IMSI
Allows a Mobile Station (MS) to be tracked as it moves

across the network.
DCS1800 RTC
Supports the DCS1800 M-Cell CCB (Cavity Combining

Block) at M-Cell sites. As a result, the BSS software is
required to modify the management of remote tuned
combiners at an M-Cell site.
Transcoder On-line
Expansion
Allows the transcoder capacity of equipped transcoder

cards to be increased while on-line. The BSS remains
available while the equipped hardware is increased and
configured. This eliminates any site outages during the
expansion.
Type 7 Microcellular
Neighbour Class
Adds a Type 7 Microcellular neighbour cell.
Device (SITE/MTL/CBL)
Redistribution
Provides the capability to redistribute the SITE, MTL,

and CBL devices to different parent LCF functions.
This reassignment is service affecting.
Enhanced Frequency
Hopping
enhances the operability of the existing hopping feature

by introducing the following enhancements:
Hopping timeslots may be locked and
unlocked.
Carriers or timeslots may be specified as
hopping or non-hopping when brought into
service.
When a carrier or timeslot is unlocked, it will be
brought back into service as hopping or
non-hopping based on the database
configuration.
Only the affected site will have to be reset for
changes to frequency hopping parameter to be
effective.
Configurable X.25 for BSS
Allow the OML and CBL links to have configurable

X.25 layer 3 packet sizes and window sizes. This
feature will provide MMI commands and OMC interface
support for modification and viewing of these
parameters.
Satellite XBL Interface

(optional)
provides the BSS software support for transmission of

the XBL link via satellite.

02 May 2003
68P02901W01-M
527
528
GSR6 (Horizon II)
Feature
Description
Satellite OML Interface

(optional)
Provides the BSS software support for transmission of

the OML link via satellite.
On-Line Add/Copy/Delete
Cell BSS Command
Supports the on-line modification to the Cell

configuration of the SITEs within a BSS, while Cellular
service is maintained to subscribers.
CM Service Statistic
Break-out
Provides call success statistics that more closely

match MSC statistics. Call success criteria depend
upon the service requested.
Upgraded Remote Tuning

Combiner at 900 MHz
Provides an adaption kit to enable the new M-Cell

Remote Tuning Combiner, known as CCB, to be
retrofitted to BTS4 and BTS6 systems.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

GSR3 features
Table 5-18 summarizes the features are provided in the BSGSM-GSR3 release with
OMC/BSS software support.
Feature
Description
Concentric Cells
Allows the RF resource allocation for a cell to consist

of two frequency channel groups with a single BCCH
frequency to operate in the same coverage area.
Support for Extended Range

Cell
Allows the BTS to successfully handle the uplink

transmissions of a MS whose absolute timing advance
exceeds 63 bit periods.
16 kbit/s XBL
Eliminates the requirement for a full E1/T1 timeslot for

each XBL.
Non-redundant RTF-PATH
Fault Containment
Allows a cell to be available for calls even when all of

the paths on which a RTF is equipped fails, provided
there is another in-service RTF-PATH available for the
cell. Traffic capacity can be increased by removing any
redundant RTF-PATHs and using this feature to
manage RTF-PATH failures. This will also result in a
cell not being barred provided that there is at least one
in-service RTF-PATH available for the cell.
PCS1900 MHz Band

(M-Cell2/6)
supports the PCS1900 GSM band 8 Watt (after first

stage of combining) product on both the M-Cell2 and
M-Cell6 BTS hardware platforms. No remote tuning
combining is supported. This feature is for M-Cell2/6
only and supports all GSM900/DCS1800 features
except multiband.
Infrastructure Sharing
supports cells of different frequency bands in a single

BTS-site. This feature also supports the conversion of
single band BTS-BTUs and BCU-BTSs to multiband
BTS-sites.
16 kbit/s RSL for Preserving

Timeslots
Supports an interface between the BSC and the

BTS-site using a 16 kbit/s LAPD and Motorola
proprietary signalling.
Circuit Error Rate Monitor
Provides the means for identifying when discontinuity is

detected on a circuit path. The term circuit path refers
to the network communication path from the transcoder
(XCDR) to the BTS established during a call.
Adjustable Downlink Audio

Volume Control
Provides the firmware support for adjustable downlink

audio volume control in four steps of 2 dB each at the
transcoder.
GDP Support of Dual Rate,

Full Rate, and Enhanced Full
Rate
supports the transcoding functions for full rate,

enhanced full rate (EFR) and half rate. The GDP
board is one of the required components of the EFR
feature, which provides better overall speech quality
than full rate.

02 May 2003
68P02901W01-M
529
GSR6 (Horizon II)
Feature
Description
Enhanced Full Rate Vocoder
Implements the GSM defined Enhanced Full Rate

(EFR) for speech. EFR provides a speech service that
has better voice quality than normal full rate speech
service.
Multi-Band Inter-Cell
Handover
the BSS supports inter-cell handover where cells are

operating in different frequency bands. In addition, the
network operator can deploy cells of differing frequency
bands within the same BTS-Site(s). For example, a
single BTS-Site may support combination of the
DCS1800, PCS1900 and GSM900 cells.
OMC & DataGen common

GUI
Provides BSS support for a common OMC and

DataGen GUI.
GPROC2 removes CSFP

requirement
Provides the software support required to reallocate

M-Cell specific objects from the BSC CSFP GPROCs
to the BSPs which are GPROC2 boards. This
removes the requirement of having a CSFP GPROC at
the BSC to support M-Cell BTS sites.
Increased Capacity with

GPROC2 as LCF
Allows a single GPROC2 serving as a LCF to support

2 MTLs and 15 active BTS-sites. A new database
parameter indicating the number of links supported on
a GPROC2 is created.
MS handover power level

based on path loss
calculations
Sets the MS power level on an inter-cell intra-BSS

handover to the target cell based on path loss
calculations for promoting battery conservation.
SACCH on a Channel basis
Provides BSS support for SACCH system information

on a channel basis.
RTF Subequipping
Supports the unequipping of an RTF to reduce the

number of E1/T1 timeslots required for a site. A
unequipped RTF utilizes a single 64 kbit/s timeslot on
an E1/T1 link.
Prefer Different Carrier for

Intra-cell handover
Permits a different carrier to be used for an intra-cell

handover when the uplink interference level is the
same.
Micro-micro quality handovers Calls which experience a quality condition in a

microcell will be handed over to another microcell when
possible.
530
Timed offset upon RXQUAL

handovers
Adds a new timer that may be set up provide an

additional margin to the handover margin to prevent a
handover to a cell with a lower power budget.
Time limitation for excessive

intra-cell handovers
The number of intra-cell channel changes due to

interference can be limited, by performing an intercell
handover when the threshold has been reached.
Remaining 12.04 Statistics

(less 3)
Adds a number of raw statistics that are generated at

the BSS to more closely meet the 12.04 GSM
Specifications. In addition, a number of counter type
statistics have been changed to counter array statistics
permitting easier identification and analysis of events
on a cause or scenario basis.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Feature
Description
DRIM/RCU FW Alarm
Translation Adjustments
Optimizes the handling of DRIM/RCU firmware

generated alarms. This prevents spurious alarms
being reported to the operator. The Hard Reset alarm
was previously used to indicate a reset of the DRI due
to a recurring fault in addition to an actual hard reset.
Now a new DRI alarm (35) has been added to uniquely
identify this reset reason. DRI 35 is Reset due to
recurring fault.
Intra-cell Handover Ping Pong Provides a configurable time interval to reduce ping
Protection
pong effects. This permits increased handover
margins that may be applied to the original cell which
discourage handing a call back.
Enhanced full rate vocoder
transcoder
Provides firmware support for the GSM Phase 2+

enhanced full rate vocoder (codec) transcoding.
Concentric cells (interference

based cell resource
partitioning)
Provides an interference based algorithm which defines

the coverage area of the inner zone for concentric cell
structures.
Handover margin per

handover cause for candidate
ranking
Provides two new neighbour parameters to be used in

the handover decision process in the case where the
handover was due to RXQUAL or RXLEV. These
parameters are used to order candidates based on a
calculated value. This feature only applies to
microcells.
Increase BSC capacity with

introduction of GPROC2
Provides BSS support for up to 40 BTS sites, 126

cells, 255 carriers, and 1680 trunks.
High power DCS1800 with

increased sensitivity receiver
matrix
The result of the receiver sensitivity increase is

restriction of the a single cell in a single cabinet.
Enable Hopping with no Site

Reset
Allows frequency hopping parameters may be modified

without resetting the site and normal synthesizer and
baseband hopping to be enabled at different cells in the
same site using synthesizer frequency hopping
enhancement. A site reset will not occur when an FHI
is enabled or disabled.
Aggregate Abis
Provides support for third-party switching equipment

between a BSC and BTSs. Additional flexibility in the
allocation of E1/T1 timeslots at the BSC and BTSs is
provided to support the use of a switching network to
combine the timeslots from several low capacity BTSs
onto a single E1/T1 link to the BSC.
New Millennium
Provides Year 2000 compatibility for the BSS.
PCS1900 mast mounted

preamplifiers
Supports an independently powered masthead

preamplifier supported for PCS1900
Accelerated Handover to
Inner Concentric Cell Zone
Provides a mechanism that accelerates handovers to

the inner concentric cell zone for cells using the
interference-based algorithm.

02 May 2003
68P02901W01-M
531
GSR6 (Horizon II)

GSR4 features
Table 5-19 summarizes the hardware/software features provided in the BSGSM-GSR4
release with OMC/BSS software support.
532
Feature
Description
Call trace expansion
Provides enhanced operator features through the OMC

GUI for call tracing.
Carrier prioritization for

SDCCH
Provides the operator with the flexibility of prioritizing

the selection of Traffic Channels (TCHs) and
Standalone Dedicated Control Channels (SDCCHs) in
order to minimize the overall interference level in a
GSM network.
SMS alphabet extensions
Adds three new alphabets to the list of default

alphabets supported by the Short Message Service
feature.
BTS concentration
Provides the customer with an alternative mechanism

for allocating terrestrial backhaul for radio resources
between the BSC and the BTS. This feature preserves
the existing mechanism, but allows the operator the
choice, on a per BTS site basis, of whether to use the
existing mechanism, or the new dynamic allocation.
M-Cell HDSL interface
Introduces a High bit-rate Digital Subscriber Line

(HDSL) interface into the Motorola BSS product line.
HDSL is a data transmission mechanism which
supports duplex high speed digital communication (at
E1 rates) on one or more unshielded twisted pair lines.
Increased BSC capacity
Expands the capacity of a BSC must be GPROC2s for

all functions at a BSC.
Terrestrial circuit device

management
Allows the customer to manage terrestrial circuits in

much the same way as other devices.
Optimized power control
Improves uplink and downlink power control. This is

done by adding flexibility in defined power steps,
modifying the range of power steps, by allowing power
step sizes to be changed dynamically, and by
performing downlink oscillation prevention.
Frequency hopping
Enables each timeslot to use a set of frequencies

defined in one of up to four frequency hopping
systems.
New Millennium
Addresses all aspects of the Motorola system; OMC-R,

BSS, and the BTS and BSC hardware. It concerns
itself with internal clock operation and the use of the
date in various parts of the product, for example within
Event and Alarm reports.
Enhanced congestion relief
Enhances the effectiveness of the congestion relief

features which are already in place, having been
delivered by the 1.4.1.0 implementation of the
Congestion relief - directed retry alternative feature
as well as enhancement PRs to GSR2 and GSR3.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Feature
Description
GPROC2 required for all BSC With the GSR4 software release, all GPROCs at the
processors
BSC must be GPROC2s.
BCCH frequency, SDCCH in
EGSM
Allows the configuration of BCCH carriers and the

placement of SDCCH channels in the EGSM frequency
band based on an operator defined database
parameter. It provides the capability for the operator to
configure a stand alone EGSM cell and enables the
operator to implement a multiband/dual-band network
with EGSM as one of the supported frequency bands,
for example, DCS1800 and EGSM.
Flexible neighbour handling
Enhances the existing handover decision process by

adding more flexibility in the way neighbour cell
processing is carried out for handovers.
Coincident multiband
handover
Enables operators to install new radios in a different

frequency band. This installation will turn an
customers network into a multiband network.
Second assignment
Allows a second attempt to assign a Traffic Channel

(TCH) to an MS if the first TCH assignment attempt
fails.
The OMC provides the appropriate information to remind the operator that the BSC must
be all GPROC2 boards, before a conventional or CSFP download of release GSR4.

02 May 2003
68P02901W01-M
533
BSS software release GSR4.1
GSR6 (Horizon II)
GSR4.1 features
Table 5-20 summarizes the hardware features provided in the BSGSM-GSR4.1 release
with OMC/BSS software support.
Table 5-20 Release GSR4.1 features
534
Feature
Description
Point-to-point GPRS service.
Supports implementation of one to eight timeslots on a

single carrier per cell for the transmission of GPRS
traffic. This enables the Network Operator to optimally
size the network for efficient support of a mix of GPRS
and voice traffic.
GPRS radio channel

allocation.
Provides the flexibility for a cell supporting GPRS to

allocate a given radio resource to handle circuit
switched voice/data or packet data as required. A radio
resource can be configured as dedicated to circuit
switched traffic, packet data traffic, or switchable
between the two.
Medium Access Control

modes: fixed/dynamic
allocation.
Includes the functions related to the management of

the common transmission resources. These include the
packet data physical channels and the radio link
connections on packet data physical channels.
Support of MS classes.
Supports multislot MS classes 1-12, 19 and 20. This

includes support of both semi-duplex (classes 1-12)
and half-duplex (classes 19 and 20). Semi-duplex MSs
can support up to 4 TimeSlot (TS) downlink and 1 TS
uplink, or 2 TS downlink and 2 TS uplink. Half-duplex
MSs, can support 6 TS downlink or 2 TS uplink, or 1
TS downlink and 4 TS uplink (fixed allocation MAC
mode).
GPRS codes schemes CS-1

and CS-2.
Coding schemes CS-1 and CS-2, providing 9.05 kbit/s

and 13.4 kbit/s respectively, are supported.
Dynamic adaption of coding

schemes.
Enables the network to change the coding scheme

between MS transmissions based upon the radio
characteristics of the link. Movement between CS-1
and CS-2 is supported in the initial GPRS release.
Two phases packet access.
Allows an exchange of information to take place

between the MS and the network prior to assignment
of resources.
Frequency hopping of PDCH.
Supports frequency hopping of the packet data channel

(PDCH).
Power control:
uplink/downlink
enables power adjustment over the radio link based

upon the characteristics of the link. Power control is
supported over the radio interface on both the uplink
and downlink. Power adjustments are directed by the
network based upon the measured characteristics of
the radio link.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Feature
Description
Gb interface.
Provides connection between the BSS and the SGSN.
PCU load balancing and

sharing (Gb and BTS).
Provides high reliability through efficient resource

management. It also manages the movement of
resources from one part of a BSS to another to meet
varying peak capacity requirements in a network
designed primarily for coverage.

02 May 2003
68P02901W01-M
535
GSR6 (Horizon II)

GSR5 features
Table 5-21 summarizes the features of the GSR5 software release.
Description
BSC Overload Protection
SMS CB upgrade
Integrated RF loopback on Horizonmacro
Dynamic allocation of RXCDR-BSC circuits
Enhanced XBL
Horizonmicro2/Horizoncompact2 generic BTS software
Code corruption imune design
Propagate TSC changes to all timeslots
Single BCCH for dual band cells
Support for E1/T1 conversion
Enhanced Power Outage Recovery
Improved MTL load balancing
BTS concentration resource optimization for handovers
Handover parameter
Per neighbour area for adaptive handovers
Support for MTL stat
Support for frame erasure rate statistic
BTS concentration call priority handling
RF head external alarm
GPROC function pre-emption
Parallel cage enable
Enhanced MMI Link Device Warnings
BSS overload protection

The MSC Overload control feature introduces a mechanism for temporarily reducing
traffic between the MSC and the BSS. This mechanism allows the MSC to notify the BSS
that it is becoming overloaded and the amount of information being sent to the MSC from
the BSS should start to be reduced. The BSS receives the notification and starts to
reduce the traffic loading on the MSC immediately. The BSS reduces the traffic load on
the MSC by barring mobile access classes within cells in the BSS. The unbarring of the
access classes to increase the traffic to the MSC is controlled by a timer.
536

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
SMS CB upgrade
The short message service (SMS) cell broadcast (CB) attracts subscribers to the network
by broadcasting information of interest to the general public, for example, road
conditions, traffic information, news flashes, weather reports, etc.
The SMS CB upgrade feature integrates changes made to the ETSI GSM standards and
recommendations since the initial development of the SMS CB features, and provides
support for large SMS CB messages.
The main system changes are:
S
Multiple page message support. The initial implementation limited the number of
pages in a WRITE/REPLACE to 1.
Different message categories. Message categories have been introduced. These

categories are defined as High Priority, Background or Normal. The introduction of
different priority messages affects the scheduling of both the message itself and
the DRX scheduling messages. A new message is supported from the CBC which
reserves certain slots for potential High Priority messages.
CBC configurable DRX period. A configurable DRX message has been introduced.
The DRX message may be turned on and off via messages from the CBC. In
addition, the period of the DRX message may be set by the CBC.
CBC-BSC interface upgrade. The definition of the Repetition-rate parameter has

changed.
Support of extended SMS alphabets. ETSI 03.38 provides definitions of the

extended alphabets which can be used for SMS cell broadcast messages.
Extended SMS alphabets are supported for messages which are defined by the
CBC. The extended SMS alphabet is not be supported for SMS cell broadcast
messages which are defined via the OMC/customer MMI.
Backward compatibility. CBC vendors may be working to different versions of GSM

specifications 03.41 and 03.49. A mechanism has been introduced which allows
the BSC operator to select which version of the specification to use.
Receive antenna VSWR and radio loopback test

The Receive Antenna VSWR and Radio Loopback Test feature provides added radio
diagnostics to aid in fault detection in the field. Specifically, this feature provides:
S
Reduced maintenance costs; through quick and accurate verification of radio

serviceability, and prevention of unnecessary site visits.
Enhanced system operability and reliability; through minimizing operator

procedures for fault management, and enabling standby devices to be tested to
detect latent faults.
Enhanced quality of service; through enhanced system operability and reliability.
The diagnostics provided by this feature are:

S
Receive Preamplifier Input Loopback. This diagnostic is supported by

Horizonmacro.
Transmitter output is looped back at the receive preamplifier input (after being
down-converted to the receive frequency).
Receive Antenna VSWR. This diagnostic is supported by Horizonmacro.

Receive Antenna VSWR testing is first performed by gathering results from the
Receive Preamplifier Input Loopback test. Next, the receive-frequency-translated
transmitter output is directed to the receive antenna and the reflected signal
strength is measured. These two sets of results are used to compute a VSWR
measurement.
02 May 2003
68P02901W01-M
537
GSR6 (Horizon II)
Dynamic allocation of RXCDR-BSC circuits

The dynamic allocation of an RXCDR to BSC circuits feature introduces fault
management for call traffic on the BSC to RXCDR interface (referred to as the Ater
interface) by managing the individual 16 kbit/s channels (called Ater channels) on this
interface. In addition, this feature provides for validation of the Circuit Identity Code
(CIC) and Ater channel provisioning between the BSC and RXCDR to ensure that calls
are placed on the correct circuit between the BSC and the MSC. Without this feature in
place, no fault management of the Ater channels would be possible, and all Ater and CIC
information must be manually verified by the operator, resulting in a higher Operation and
Maintenance (O&M) cost for the Motorola BSS.
The dynamic allocation and release of RXCDR to BSC circuits provides the following
benefits:
S
Simplified network provisioning; there is no need to manually map CICs to Ater

channels at both the BSC and RXCDR.
Simplified network debugging; via automatic and manual audits of CIC and Ater
channel information between a BSC and RXCDR.
Better fault tolerance for call traffic, since calls do not necessarily need to be
terminated due to a single failure on the linkset between an RXCDR-BSC.
Better utilization of network resources.
This feature will remain consistent with the Terrestrial Circuit Device Management
feature, with respect to how the operator is permitted to manage the CIC devices.
Enhanced XBL
The term XBL, refers to a BSC-RXCDR link. The new Enhanced XBL (EXBL) feature
improves the robustness of communication between the BSC and the RXCDR. The
basis of this feature is to provide a generic messaging system between the BSC and the
RXCDR. This generic messaging system is used to suit both current operator needs and
the needs of future BSS features.
Operator-visible aspects of the EXBL feature are that runtime checks of database
consistency and connectivity are performed between the BSC and RXCDR to ensure that
traffic pathways are properly configured, and that every E1/T1 link to an RXCDR device,
at the BSC has a corresponding link configured at the appropriate RXCDR. Operators
are notified of any failure of these connectivity checks so that they can take the
appropriate action.
In the event of a verification failure, the BSS automatically disables the relevant CIC
devices to ensure that they are not used.
In addition, indications regarding maintenance activity, or faults, occurring at the RXCDR,
which indirectly affect the BSC link devices, are forwarded to the BSC for processing.
538

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Horizonmicro2 / Horizoncompact2 generic BTS software

The BSS software supports the 900/1800 Horizonmicro2/Horizoncompact2 feature as a
restrictable feature (Master and Slave combination). The 900/1800
Horizonmicro2/Horizoncompact2 feature is available on a per BSS basis. The operator is
not permitted to configure an Horizonmicro2 BTS site in the BSS database, if the
900/1800 Horizonmicro2/Horizoncompact2 feature is restricted (specific to the
Horizonmicro2/Horizoncompact2).
There are no new code objects required exclusively for the master Horizonmicro2 BTS,
they remain the same as existing Horizonmicro BTS platforms. The 900/1800
Horizonmicro2/Horizoncompact2 feature is implemented by modifying existing code
objects.
Dynamic power control is also supported on the Horizonmicro2 and Horizoncompact2
BTSs.
Synthesizer frequency hopping is also available over multiple BTSs in the same cell.
Code corruption immune design

This feature aims to reduce the number of field returns of M-Cell and Horizon based
equipment due to code corruption. It also maintains backward compatibility with previous
hardware and software loads.
Code corruption usually occurs during field code upgrades and a power outage disturbs
the programming process. In order to reduce the number of equipment returns,
modifications have been made to both software and hardware.
Hardware
Flash (non-volatile memory) is doubled in size. The flash is divided into two banks; the
first bank stores a master copy of the operational code, whilst the second bank stores the
recovery copy. A hardware switch is required to select either bank.
Software
The software validates the operational code in both banks of flash. If there are no
problems, then the operation of the equipment is allowed to continue. If one of the banks
has corrupt operation code, then a copy of the valid bank is made to immediately
overwrite the corrupt bank.
Propagate TSC changes to all timeslots

This feature provides more flexibility for automatically updating training sequence codes
(TSCs) of RTFs within a cell when a BSIC is changed. Three options are provided:
S
Current Implementation - only update TSCs of BCCH/CCCH timeslots.
Update TSCs for all timeslots on the BCCH carrier.
Update TSCs for all timeslots on all carriers of the cell.

The Single BCCH for Dual Band Cells feature is an enhancement to the GSR3 multiband
feature, to allow more efficient network operation by enabling a single BCCH carrier to
serve GSM900 and DCS1800 cells in the same coverage area.
Support for E1/T1 conversion

This feature removes the support for E1 to T1 conversion. In the future, any customers
needing T1 support can purchase multiple serial interface 2 boards (MSI-2) as well as the
T1 version of the generic DSP (GDP) boards.
02 May 2003
68P02901W01-M
539
GSR6 (Horizon II)
Enhanced power outage recovery

The Enhanced Power Recovery feature improves system availability in the event of a
total power loss to the site, by providing a non-volatile storage mechanism for BSS
Software. This feature works in conjunction with the present battery back up feature.
The non-volatile memory resides on a new piece of hardware, the Non-Volatile Memory
Card (NVM card). This card is located at BSC and RXCDR sites only.
A background task ensures that the NVM is loaded, and periodically updated, with the
same BSS software objects as the master GPROC board. When powering up after a
power loss, the site will retrieve code from the NVM board, if necessary.
Improved MTL load balancing

This feature improves the loadsharing of traffic on message transfer links (MTLs) in the
uplink direction from the base station system (BSS) to the mobile switching centre
(MSC). Loadsharing from the MSC to the BSC is based on the routeing function
implemented at the MSC and is beyond the scope of this feature. The granularity of the
load distribution is increased from 16 to 64, resulting in a more even distribution of traffic
across the MTLs.
The implementation of test traffic generation at the BSS for message transfer part (MTP)
Layer 3 testing is modified to support the new loadsharing mechanism. A new MTP
Layer 3 test message is added which allows the remote side to determine how the virtual
circuits are distributed over the active MTLs. A database element is added for setting the
loadshare granularity to either 16 or 64.
BTS concentration resource optimization for handovers

The BTS Concentration Resource Optimization for Handovers (BCROH) feature
optimizes the terrestrial backhaul between a BSC and BTS during handovers, when the
BTS concentration feature is applied. Previously when a handover occurred, a new
circuit for the destination radio channel was always allocated between the BSC and the
BTS. The BCROH feature means that if the source and destination BTS in a handover
are the same, then a new circuit is not allocated and the existing circuit is re-used for the
radio destination channel. It can only be used in conjunction with BTS equipment that
supports BTS concentration.
The BCROH feature reduces the number of resources required when intra cell handovers
or inter cell handovers (within the same site) occur and are controlled by the BSC. In
these handover scenarios the switch connections for the voice traffic from the radio
channel to the MSC are no longer made at the BSC during the handover. The BTS to
MSC path remains constant and the BTS must simply move the switch connection of the
Abis circuit from the source radio channel to the destination radio channel.
Handover parameter
The Handover parameter reorganization/reduction (also referred to as RSS Bin
Reduction) feature, removes a number of unused bins allocated to each of the radio
subsystem (RSS) handover and power control algorithms. It cleans up previously wasted
database space.
Additionally, this feature converts any test object functionality into MMI commands.
Extended range cell prioritization and the Uplink quality value of 7 on a missing
measurement report will be supported by CM/MMI commands.
540

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Per neighbour area for adaptive handovers

The adaptive handover methodology allows handovers to occur more rapidly when
conditions are deteriorating quickly and less rapidly when conditions are only marginally
poor.
This enhancement to adaptive handovers provides the operator with the option of setting
the cumulative area for adaptive power budget handovers on a per cell or per Neighbour
basis.

This enhancement to the existing optimized power control feature, allows the operator to
enable a power control algorithm that allows RXLEV based power reductions.
Calculations are made for both uplink and downlink power control.
Dynamic power reduction is used in the event of the RXLEV exceeding the upper level
threshold. If the algorithm is enabled, power level reduction step sizes can be changed
dynamically, based on the current proximity to the upper power level threshold. This will
allow the power to be brought down at a faster rate when it has strayed out of the power
box. The dynamic power reduction feature will be enabled in addition to the good quality,
poor quality, and low level adjustments. These three adjustments may also be chosen
without the high level adjustment provided by this feature.
Support for the MTL stat

This feature implements the BUSY_CICS statistic at the BSS.
The weighted distribution statistics produce a mean value indicating the average number
of circuit identity codes (CICs) in use during a statistic interval.
The statistic is pegged each time an allocation or deallocation of a CIC is detected. It is
an indication of the amount of active calls under the mobile switching centre (MSC).
Since each call is routed via the MSC (even intra-BSS and intra-cell), the number of CICs
represents the number of calls in progress under that MSC for the base station system
(BSS).
Support for frame erasure rate statistic

This feature implements frame erasure rate (FER) and residual bit error rate (RBER)
statistics at the BSS.
These statistics provide the following benefits:
S
Ability to target optimization efforts on cells and radios.
Meaningful call quality metrics for hopping network benchmarking and health
reporting.
Uplink FER offers an alternative to drive test for voice quality.
BTS concentration call priority handling

The BCCPH feature enables the BSS to prioritize the order in which non-emergency
circuit switched calls are pre-empted by emergency calls.
This feature pre-empts circuit switched calls based on priority as well as age. The BSS
attempts to pre-empt a non-emergency circuit switch call with the lowest priority first and
a non-emergency circuit switch call with the highest priority last. If two calls exist with the
same priority level then the oldest is chosen first.
02 May 2003
68P02901W01-M
541
GSR6 (Horizon II)
GPROC function pre-emption

This feature searches for a Busy-Unlocked generic processor board (GPROC) running a
lower priority function, when a GPROC hosting a higher priority function goes out of
service, and there are no Enabled-Unlocked GPROCs to host the higher priority function.
If such a GPROC is found, the lower priority function is pre-empted by the higher priority
function. The operator is able to configure the pre-emption algorithm using a database
element.
The levels of pre-emption that can be configured are:
S
No pre-emption.
Function level pre-emption: If a function of lower priority is running on a GPROC,

that function will be pre-empted. In the case of a pre-empted LCF, the LCF with the
highest function id will be pre-empted.
Intra function level preemption: If a function of lower priority is running on a

GPROC, that function will be pre-empted. If a GPROC running an LCF goes out of
service and there is no lower priority function type (e.g. BTF) running on a pool
GPROC, the function tables will be searched for a lower priority LCF to pre-empt.
Parallel cage enable

CAGEs at an InCell multl-cage site were previously brought into service serially. This
feature brings the CAGEs at InCell BSCs and RXCDRs into service in parallel. Cages at
an InCell BTS site will be brought into service in parallel when the master BTP is a
GPROC2.
Cages at an InCell BTS site will continue to be brought into service serially when the
master BTP is a GPROC1.
Enhanced MMI link device warnings

MMI issues confirmation warnings when the operator uses the lock, ins_device, or
reset_device commands on some link devices. Additionally, in some cases, MMI issues
confirmation warnings when an MSI, MMS, or DPROC is locked and it has an associated
link device.
The Enhanced MMI Link Device Warnings feature addresses a number of problems that
existed with the MMI link device warnings. The previous link warnings have been
replaced with a new, comprehensive set of warnings.
The affects of this feature are:
542
MMI issues a warning message and prompt for confirmation whenever the lock,
ins_device, or reset_device commands are used on a link device.
MMI issues a warning message and prompt for confirmation whenever the lock,
ins_device, or reset_device commands are used on a parent device that supports
link devices.
MMI issues confirmation warnings for link devices regardless of their current state.
The warnings that MMI issues for link devices define the link affected and the
consequences of locking the link device.
The warning that MMI issues for a particular link device is the same for all of the
MMI state change commands.
68P02901W01-M
02 May 2003
GSR6 (Horizon II)

GSR5.1 features
Table 5-22 summarizes the features provided at software release GSR5.1.
Description
BSS processing of suspend message
CS3, CS4 and 32 kbits/s TRAU
GPROC fast reset
Unequip TCU/CTU Cabinet
850 MHz frequency range
1900 MHz Horizon
BSS processing of suspend message

Feature overview
Previously, the BSS did not process the suspend message received from the mobile.
As stated in GSM 04.08, the BSS needs to process this message and to communicate it
to the Serving GPRS Support Node (SGSN) (GSM 08.18). This feature enables the BSS
to communicate the suspend message to the SGSN.
Feature description
When a GPRS attached MS enters CS dedicated mode to answer a CS page, and MS
limitations make it unable to continue to communicate for GPRS, the MS will request to
suspend GPRS services. The BSS processes this message from the mobile to suspend
its GPRS service and sends a suspend message to the SGSN via a Gb link (interface
between an SGSN and a BSC.
The SGSN, in turn, does not initiate any paging for this mobile while its in the suspend
state. When the mobile switches from the CS dedicated mode back to the GPRS mode,
it sends a routeing area update message asking the SGSN to resume the data transfers.

02 May 2003
68P02901W01-M
543
GSR6 (Horizon II)

Feature overview
The GPRS Coding Scheme 3, Coding Scheme 4 (CS3/CS4) and 32 kbits/s Transcoder
Rate Adaption Unit (TRAU) feature implements an alternative channel coding algorithm
over the air which enables increased data rates to GPRS mobile stations.
Software changes
The BSS and PCU changes necessary to implement Coding Scheme 3 and Coding
Scheme 4 are software changes. There are no hardware modifications or additions
necessary to support this feature.
32 kbps TRAU channels

The BSS supports 32 kbits/s TRAU channels that are comprised of two independently
synchronized 16 kbbits/s TRAU channels. Both component 16 kbits/s TRAU channels of
any given 32 kbits/s TRAU channel reside on a single GDS to ensure that a single TRAU
processing entity can handle the reassembly of the individual channels.
CM database parameters
Additionally, two new CM database parameters are necessary to control whether or not
the CS3, CS4 and 32 kbits/s TRAU is allowed in the BSS. If CS3, CS4 and 32 kbits/s
TRAU is allowed in the BSS, then cs34_enabled must be enabled. To support the
feature on a per carrier basis, every timeslot dedicated to GPRS must have sufficient
backhaul present to support the 32 kbits/s TRAU. This is enabled by a per carrier
parameter as part of the equip_rtf command called allow_32k_trau.
New statistic
A new statistic GPRS_32K_CHANNELS_SWITCHED is introduced to complement the
CS1 and CS2 statistics that are currently implemented.
Dynamic allocation
The use of the dynamic allocation feature in conjunction with the CS3, CS4 and
32 kbits/s TRAU feature is not supported at this time. In a network at sites using
dynamic allocation, the CS3, CS4 and 32 kbits/s TRAU feature is not allowed.
Restrictions
Every firmware platform that currently supports GPRS supports CS3, CS4 and 32 kbits/s
TRAU, consequently no additional restrictions need be placed on the carriers or RTF
equipage due to this feature.
544

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
GPROC fast reset

Feature overview
The Fast Reset (Soft Reset) feature enables a GPROC to come back into service
quicker, when recovering from a fatal Software Fault Management (SWFM). If the
GPROC is functioning as the master BSP/BTP, then the fast reset feature has the effect
of bringing the site into service sooner. This feature reduces the outage time for the
involved GPROC(s) and increases the total availability of the site.
Feature description
The fast reset feature decreases the recovery time for a reset by having the GPROCs
transition software from RAM back to RAM during a reset, without going through the
ROM process. The differences between a RAM-RAM software transition verses a
RAM-ROM software transition is that the RAM-RAM procedure does not execute the
functionality in ROM, as it is passed over.
During a RAM-RAM software transition, the GPROC that incurred the fatal SWFM is
taken off the LAN and all TDM connections for that GPROC are cleared. Then, instead
of performing a software transition to ROM, the GPROC comes back on the LAN in RAM
and performs the RAM initialization procedure.
The theory behind the fast reset feature is that a process executing in RAM, which
encounters a bus fault or any other fatal SWFM event, does not need to go through the
ROM transition to restore the GPROC. By halting all processes on that GPROC and
reinitializing it, the fault generating condition should no longer exist. If the fatal SWFM
condition still exists, an escalation mechanism eventually transitions (points) the GPROC
software into ROM.
Unequip of TCU/CTU cabinets

This feature enables the unequippage of extension cabinets of types TCU_2, TCU_6 and
Horizonmacro_ext at M-Cell and Horizonmacro sites without having to unequip the site.
This action can be done, provided that the cabinet is locked and there are no DRIs or
EASs equipped to the cabinet. All other cabinet types are not supported by this feature.
850 MHz frequency range

Provides software support for a BSS to operate in the 850 MHz frequency range using
features already introduced in prior releases.
1900 MHz Horizonmacro

Provides software support for for a BSS to operate in the 1900 MHz frequency range
using features already introduced in prior releases.

02 May 2003
68P02901W01-M
545
GSR6 (Horizon II)

The Single BCCH for Dual Band Cells feature is an enhancement to the GSR3 multiband
feature, to allow more efficient network operation by enabling a single BCCH carrier to
serve GSM900 and DCS1800 carriers in the same coverage area.
The main impacts of the Single BCCH for dual band cells feature are as follows:
S
Support of two different frequency bands within a single cell, using a concentric
cells configuration.
The operator can define the coverage area of the secondary band by use of BSS
database parameters.
Channel algorithms are supplied to incorporate selection of channels from different

frequency bands, and ensure the allocation of a secondary band (inner zone)
resource at TCH assignment when required criteria are met.
Power level conversions are provided for intra-cell channel changes and incoming
inter-cell handovers between channels on different frequency bands.
Other optional features that must be unrestricted in order to configure dual band cells
are:
S
Multiband handover - see Multiband intercell handover in the BSS software

release GSR3 section.
Concentric cells - see Concentric cells in the BSS software release GSR3
section.
Dual band cells - see BCCH frequency, SDCCH in EGSM in the BSS software
release GSR4 section.
The functions of these features on which the Single BCCH for dual band cells is
dependent are described in this manual. A technical description of the Single
BCCH for dual band cells feature, and these features are contained in the manual
Technical Description: BSS Implementation (68P02901W36).
Homogeneous cabinet - see the equip CAB command in the manual Technical
Description: BSS Command Reference (68P02901W23).
Heterogeneous cabinet (for combined cabinet configurations) - see the equip CAB
command in the manual Technical Description: BSS Command Reference
(68P02901W23).
546

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

GSR6 features
Table 5-23 summarizes the features provided at software release GSR6.
Description
Enhanced Circuit Error Rate Monitor
Multiple GPRS carriers per Cell
Enhanced GDP provisioning
Call downgrade on CIC capability mismatch
GPRS PCU recovery on last GSL failure
Network controlled cell reselection
Location Services (LCS)
Basic MPROC redundancy
Enhanced BSC capacity phase 2
Improved MPROC SW failures detection and recovery
Clean Install (E3x00)
Inter Radio Access Technology (RAT) 2-G to 3-G handover
GPRS interleaving TBFs
Link utilization improvements
Advanced load management for EGSM carriers
Enhanced GPRS One Phase Access
Remove support for collocated BSC
Compress all BTS objects at the BSC

02 May 2003
68P02901W01-M
547
GSR6 (Horizon II)
Enhanced Circuit Error Rate Monitor

Feature overview
The original Circuit Error Rate Monitor (CERM) optional feature provides a means for
identifying when discontinuity is detected on a circuit. The customer can:
S
Reduce cost of ownership
Reduce downtime of devices
Enhance system operability
Enhance quality of service.
A circuit is considered to be the path along which a connection is made, from the entry
point in the BSS (e.g. a radio at the BTS) to the exit point in the BSS (e.g. the MMS
timeslot that connects to the MSC or PCU).
The CERM is used to monitor the continuity and sanity of hardware processing elements
in a circuit, on a per call basis. Whenever a discontinuity is detected for a circuit during a
call, error counts are updated for the points monitored for the call. When the error count
at a particular monitoring point reaches or exceed an operator specified threshold, an
alarm is generated. The alarm contains information identifying the monitored path in
which the error is detected, thus allowing the operator to identify potentially faulty
devices.
Feature description
The CERM feature is enhanced, enabling the monitoring at various points in a GSM
network circuit, thus improving the ability of a operator to narrow down where a faulty
device may be located. Although having these monitoring points in the circuit path
narrows down the list of potentially faulty devices, it does not confirm that a device is
faulty. It is still up to the operator to determine which device is faulty.
The following points in a network can be monitored on a per timeslot basis:
S
Circuit identity Code (CIC) on a link between the RXCDR or BSC and the MSC
ATER Channel Identifier (ACI) groups on a link between the RXCDR and the BSC.
GPRS Circuit Identifier (GCI) in the radio hardware.
Radio Channel Identifier (RCI) in the radio hardware.
Path Identity Code (PIC) on a link between the BSC and a BTS.
The PIC is a special case because it is measured on a from-BSC-to-site basis. So, for
example, with a path leading from a BSC to two daisy chained BTSs, the PIC for the
second BTS encompasses the path through the first BTS to the BSC.
548

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Multiple GPRS carriers per Cell

Feature overview
Before GSR6 the Motorola GPRS product offered the capability to configure up to eight
GPRS TimeSlots (TSs) on a single carrier in a cell. The increase in packet data traffic
and availability of multiple timeslot GPRS MSs have increased the need for additional
GPRS capacity.
The Multiple GPRS carrier feature enables the network operator to configure multiple
GPRS carriers per cell for increased GPRS traffic handling capability to meet this
increase in packet data traffic and the expanding base of GPRS subscribers with
increased data throughput.
The operator is offered two options to configure GPRS TSs on multiple GPRS carriers
per cell:
S
Configure for performance,
Operator specified.
Configuration performance
Configure for performance provides the network the capability to configure all the
reserved and switchable GPRS timeslots in a cell contiguously to maximize performance.
The contiguous GPRS TSs configured on a carrier in a cell provide ease in scheduling
packet data and the capability to service multiple TS GPRS mobiles.
Table 5-24 is an example of multiple GPRS carriers where the default option, configured
for performance, is specified. The GPRS resources are configured contiguously on
GPRS carriers in the cell to maximize performance. The cell has five GPRS carriers, ten
reserved TSs and eleven Switchable TSs.
Table 5-24 Multiple GPRS carriers configured for performance (Default)
TS 0
TS 1
TS 2
TS 3
TS 4
TS 5
TS 6
TS 7
BCCH
SDCCH
RES
RES
RES
RES
RES
RES
SW
SW
SW
SW
RES
RES
RES
RES
TCH
SW
SW
SW
SW
SW
SW
SW
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH

02 May 2003
68P02901W01-M
549
GSR6 (Horizon II)
Operator specified
The operator specified option provides customers with the flexibility to configure the
maximum and minimum number of reserve and switchable GPRS timeslots on a per
carrier basis in a cell. Table 5-25 is an example of GPRS timeslots distributed over
carriers in the cell. The cell has five GPRS carriers, ten reserved timeslots and eleven
switchable timeslots. The max_gprs_ts_per_carrier element is set to 6.
Table 5-25 Operator specified options
TS 0
TS 1
TS 2
TS 3
TS 4
TS 5
TS 6
TS 7
BCCH
SDCCH
RES
RES
RES
RES
RES
RES
TCH
TCH
SW
SW
RES
RES
RES
RES
TCH
TCH
SW
SW
SW
SW
SW
SW
TCH
TCH
TCH
TCH
TCH
SW
SW
SW
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
When a carrier that has GPRS timeslots goes out of service, GPRS timeslots will be
reconfigured on a different carrier that supports GPRS based on the radio resources
available in the cell.

Feature overview
Enhanced GDP provisioning is an enabler for future features which require a reduction in
board channel capacity e.g. AMR.
A GDP is an Generic Digital Signal Processor (DSP) Processor board. It is
interchangeable with the XCDR board.
A GDP can provide either Basic or Enhanced transcoding.
Types of transcoding
A user can select the type of transcoding used by a GDP. The transcoding types are:
S
Basic - Transcoding for GSM Full Rate speech, Enhanced Full Rate speech and
phase 2 data services.
Enhanced - Transcoding for future applications, particularly Adaptive Multirate

(AMR) speech coding, in addition to existing GSM Full Rate speech, Enhanced
Full Rate speech and phase 2 data services.

Enhanced GDP Provisioning:
550
Supports GDPs that are capable of enhanced transcoding, particularly AMR

speech coding, in addition to supporting current transcoding services.
Allows GDPs to provide additional enhanced transcoding resources only without

making use of the E1 or T1 line interfaces.
68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Feature description
A GDP can be either a Primary or Secondary GDP, as follows:
S
A Primary GDP provides an E1 or T1 interface to the MSC. The GDP may provide
basic transcoding, or be paired with a Secondary GDP to provide enhanced
transcoding. Primary GDP can provide Enhanced transcoding only.
A Secondary GSD in a pair provides DSPs for transcoding for a set of CIC devices
routed to the MSC via the E1 or T1 interface of a Primary GDP. Secondary GDP
can provide Enhanced transcoding only.
The Enhanced GDP provisoning feature performs the following functions:

S
Supports provisioning for GDPs which are capable of enhanced transcoding

features, particularly AMR, in addition to supporting current services. Before this
feature, transcoding was performed by 15 DSPs on a GDP processing 2 calls
each. The processing requirement for future features demands that each of the
DSPs processes a single call. A pair of GDPs are required for provisioning of 30
transcoding circuits on an individual E1 link to the MSC, or 24 on a T1 link, which
are capable of the enhanced transcoding features.
Supports provisioning for GDPs to provide additional enhanced transcoding

resources only, without making use of their E1 or T1 link line interfaces.
Prerequisites for enhanced GDP provisioning

For Enhanced GDP Provisioning to be used for new transcoding applications, the
following feature must also be implemented:
S
Adaptive Multirate (AMR) Speech Coding.
The related MMS must exist before specifying it as an MSC MMS for a secondary GDP
or, if the MSC MMS is the GDPs own MMS, it is equipped (automatically). A GDP can
only provide an MSC MMS for one secondary GDP.

02 May 2003
68P02901W01-M
551
GSR6 (Horizon II)
Call downgrade on CIC capability mismatch

Feature overview
The call downgrade on CIC capability mismatch feature resolves erroneous call handling
that could cause loss of speech due to the requested speech version not matching the
capabilities of the underlying transcoding equipment.
This feature also enchances the support of the Generic DSP Processing board, adding
Enhance Full Rate capability as well as allowoing a staged migration to future advanced
transcoding technologies such as AMR.
Feature description
The Generic DSP Processor (GDP) board was introduced into the BSS and RXCDRs to
support EFR speech as the previous transcoder, the XCDR was not re-programmable
and could only support Full Rate (FR) speech and ETSI Phase 2 Data Services.
Previously, Motorola mandated that for EFR to be provided, all transcoders must be
GDPs. With local transcoding, this was easily enforced by not enabling EFR if XCDR
boards were fitted at the BSC. However, for remote transcoding, because no specific
signalling in terms of capabilities exested between the BSC and RXCDR, EFR could be
enabled at the BSC even though the RXCDR contained XCDRs.
Pooled transcoding at the MSC and the RXCDR was introduced to support this
co-existence of XCDRs and GDP within the BSS. EFR capable CICs terminating on GDP
boards, FR capable CICs terminating on XCDR boards with data services being
supported by both types of transcoder.
This configuration is satisfactory provided the pool of transcoders at the RXCDR match
that of the MSC. However, if mismatches do occur, EFR calls could be routed to XCDR
boards, resulting in calls with no speech.
Call downgrade on CIC capability mismatch resolves this problem by allowing the
co-existence of differing capability platforms, which match the capabilities of the
underlying hardware with those for incoming call requests. These are:
S
Calls specifying a preference for EFR, but also allowing the use of GSM FR, would
use EFR when utilizing a CIC supported by a GDP board.
Calls specifying a preference for EFR, but also allowing the use of GSM FR, would
use GSM FR when utilizing a CIC supported by a XCDR board.
Until the inclusion of AMR capable hardware is available, requests for AMR would
be targeted to match the capabilities of the associated CIC or supporting hardware
and use either GSM FR or EFR.
It also enhances the capability of the Generic DSP Processing board by adding EFR and
allowing a staged migration to AMR.
552

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
This feature introduces the following:

S
Mutli-platform support
Support of transcoding platforms with different capabilities within the BSS, that is
to say, to allow the XCDR and GDP boards to co-exist within the same BSC (in the
case of local transcoding) or RXCDR (in the case of remote transcoding).
Enhanced CIC management

Detection of CIC speech version capabilities by the BSS, based on the supporting
transcoding platform.
Enhanced call management

Validation of MSC call setup, in-call modification and handover requests to ensure
that the given permitted speech version(s) included are supported by the specified
CIC.
GPRS PCU recovery on last GSL failure

The GPRS Signalling Link (GSL) is a control link between the Base Station Controller
(BSC) and the Packet Control Unit (PCU). It is a required resource for providing the
packet data services as well as for operation and maintenance of the PCU. Previously,
if all the GSL links went out of service, the PCU reset itself to simplify the releasing and
rebuilding of the resources in the data services.
A problem with the previous design was that once the PCU reset itself, it took
unnecessary time to re-establish the link between the BSC and PCU and then to bring
back the PCU into service in order to process data calls again.
NOTE
If no GSL connection is made within 30 minutes the PCU will go

into RAM mode reset.
At the first GSL restoral, the first GSL IN Service (INS)
procedure will not be started until the las GSL Out Of Service
(OOS) procedures are completed. This protects the BSC and
PCU from unstable GSLs.
This feature enhances the availability of the PCU by preventing the PCU from resetting
upon the last GSL disconnection and quickly brings it up in service again upon the GSL
reconnection. When the last GSL goes out of service, the system software in the PCU
and BSC now manages and reconfigures the network resources promptly, smoothly
deallocating the resources for data calls and reallocating them for voice calls.
This feature also improves the problem analysis of the PCU because the processes on
the PCU stay up and continue to run during the last GSL failure allowing the operator to
interrogate the processes for problem analysis, locally.

02 May 2003
68P02901W01-M
553
GSR6 (Horizon II)
Network Controlled (NC1 and NC2) cell reselection

Feature overview
In a GPRS network, cell reselection is equivalent of a GSM circuit switched handover
triggered by, for example:
S
change in location of the mobile,
change in RF conditions,
cell congestion.
GPRS cell reselection offers mobility and performs network traffic management. The
different modes of cell reselection in GPRS network are referred as NC0, NC1, NC2 and
RESET. In the initial Motorola GPRS product offering, NC0 was provided. In cell
reselection mode NC0, the mobile performs autonomous cell re-selection based upon on
the radio environment. This feature release provides the remaining two modes of cell
reselection NC1 and NC2 to enhance the existing product offering. Table 5-26 shows the
different cell reselection modes, responsible network element and functionality.
Table 5-26 Cell reselection modes
Cell
reselection
mode
NC0
554
Control element
MS control
Functionality

Autonomous cell reselection.
Enhanced NC0 MS control

BSS sends cell reselection commands to
GPRS MS to change cell reselection mode.
NC1

Autonomous cell reselection,
MS sends measurement reports to BSS.
MS control
Enhanced NC1 MS control

GPRS MS to change cell reselection mode.
NC2
MS sends measurement reports to BSS,

GPRS MS,
BSS instructs MS to perform cell
reselection.
Network control

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Feature description
In the current Motorola GPRS network, the MS autonomously performs cell reselection
based solely on the RF measurements of the serving and neighbouring cells. The GPRS
MS is unable to reselect to a neighbour cell based on important factors: such as
congestion, availability of GPRS, ability to support mobiles and current grade of service.
The main objective of the network controlled cell reselection and congestion relief feature
is to increase network capacity and to provide the network operator with a tool for
network planning and improved quality of service. The operator is able to specify GPRS
cell reselection mode on a per cell basis, within the network of cells with the same cell
reselection command, thus providing the flexibility of virtual zones . A significant portion
of this feature incorporates the addition or modification of statistics that reflect radio
conditions at the MS and congestion in the GPRS network. Benefits of statistics
collection are as follows:
S
Provide network information to change cell reselection mode on a per MS basis,
Provide information to monitor network radio and congestion information to

determine and perform cell selection,
Provide network planning information and configuration of NC2 mode parameter.

In cell reselection mode, NC2 enables the BSS to take appropriate action to
reduce congestion if the originating cell is congested.

02 May 2003
68P02901W01-M
555
GSR6 (Horizon II)
Location services
BSS location services support
The Location Services (LCS) feature implements emergency services functionality in
GSM systems (compliant with the Federal Communications Commission (FCC) 911
requirements) in two phases:
Phase 1
To transmit the originating number of an emergency call (911

in the United States) and the location of the serving site to the
Public Safety Answering Point (PSAP).
Phase 2
To transmit the emergency callers estimated position,

expressed in latitude and longitude coordinates within
specified limits of accuracy.
Applications that request location estimates from location services can be located in the
MS, the network, or externally to the PLMN.
LCS positioning mechanisms

LCS currently specifies three positioning mechanisms in order to determine the location
of a Mobile Station. These positioning processes involve two main steps: signal
measurement and position computation based on the measured signals. The standard
SMG (Special Mobile Group) positioning mechanisms are:
S
Network-based uplink Time of Arrival (TOA),
Enhanced Observed Time Difference (E-OTD),
Assisted GPS (A-GPS).
Conventional GSM Timing Advance (TA) measurements can also be used in conjunction
with Cell ID determination to provide a coarser, lower quality location estimate.
Examples of applications to which LCS MS position determination can be applied are to
deliver tailored content to MSs in a physical locality (location specific advertising), or to
determine the routing of voice traffic (location sensitive routing). Motorola supports
Timing Advance (TA), Enhanced Observed Time Difference (E-OTD) and Assisted GPS
(A-GPS) positioning mechanisms.
Timing advance positioning

The Timing Advance (TA) positioning mechanism is based on the existing GSM timing
advance measurements, the frequency of sending of which is specified by the
timing_advance_period parameter. The timing advance value is known for the serving
BTS and when returned to the requesting LCS client, with the cell ID, provides the
approximate physical position of the MS.
556

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Basic MPROC redundancy

Feature overview
The purpose of the complete Master Processor (MPROC) redundancy feature is to
support a 2N redundancy scheme for the MPROC hardware within the Packet Control
Unit (PCU) platform.
NOTE
2N Redundancy is also called pair redundant. Essentially, it

means that there is twice the amount of hardware than there
would be for a non-redundant system. One unit is active whilst
the other is waiting in standby mode should the first unit fail.
In this scheme, one MPROC board serves as the active controller for the Packet Control
Unit (PCU) with a second MPROC board waiting in standby mode. Should the active
board fail or go out of service for some reason, the standby MPROC will automatically
take over control of the cage and continue normal system operation.
NOTE
MPROC failure will result in a PCU cage reset until the reserve
MPROC assumes control.
In addition to supporting the redundant hardware, this feature focuses on providing a fast
recovery from failures of the active MPROC. In the worst case, the PCU should make a
complete recovery within three to five minutes of the failure.
Feature description
This particular feature supports two MPROC boards within the PCU cage and provides
for an automatic switchover to the redundant board, should the active board fail. The
following benefits are provided by this feature:
S
Hardware-level failure of the MPROC board:

Should such a failure occur, and a redundant MPROC is not available, the PCU
will remain out of service until field personnel are able to perform an on-site
replacement of the faulty board. Once the board is replaced, the PCU will remain
out of service until all code and database objects are downloaded from the BSC.
By having a redundant MPROC in place, the PCU is able to remain in service until
the on-site replacement can be made.
Detection of MPROC failures:

The redundant hardware will constantly monitor the other MPROC board. When
the redundant board detects the active board is no longer in charge of the PCU
cage, the redundant will assume that the other board has failed and, therefore,
take over ownership of the cage (and re-initialize the PCU accordingly). Although
the assumption made by the redundant board may be incorrect, the operation of
the PCU will not be adversely affected, the only consequence is a longer recovery
time than would be necessary under ideal conditions.
Improved recovery times:

While this feature is not introducing ideal recovery times, this feature will be able to
recover from MPROC software faults faster than if redundant hardware were not
present. This improvement is possible because the PCU may begin recovery as
soon as the active board fails. Without this feature, the PCU would not be able to
begin recovery until the failed MPROC finished resetting.
02 May 2003
68P02901W01-M
557
GSR6 (Horizon II)
Enhanced BSC capacity phase 2

Feature overview
This feature increases the number of carriers to 512 and the number of Circuit Identity
Codes (CICs) to 3200.
The feature supports the following configurations:
S
The BSS supports the standard database configuration for 384 carriers if the
enhanced BSC capacity feature is restricted.
The BSS supports the standard database configuration for 2400 CICs if the
enhanced BSC capacity feature is restricted.
The BSS supports the enhanced database configuration for 512 carriers if the
enhanced BSC capacity feature is not restricted.
The BSS supports the enhanced database configuration for 3200 CICs if the
enhanced BSC capacity feature is not restricted.
To increase the number of CICs to 3200, 27 BSC-RXCDR connectivities are required at

the user interface, as each connectivity is equivalent to a physical MMS port / 2.04Mbit/s
link capable of supporting 120 traffic channels, as follows:
20 x 120 = 2400
27 x 120 = 3200
Because of this, the BSC-RXCDR connectivity table at the BSS needs to be increased
from 21 to 27 entries.
Improved MPROC software failures detection and recovery

Feature overview
To improve recovery time for extreme software failures, the MPROC board implements a
watchdog timer. A low-level software process on the board resets the timer on a regular
basis to keep it from expiring. If this process is impeded for some reason (for example,
the processing is locked-up on some other task) the timer expires.
Should a watchdog timer expire, an interrupt is generated to low-level software which
then attempts to collect information about the current task, stores its registers/stack in
compact Flash memory, and then immediately resets the board. Upon subsequent
initialization of the board, the software reads the compact flash memory and if any
watchdog reset information is stored, prints that information out to the internal Executive
Monitor (EMON) program.
558

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Inter Radio Access Technology (RAT) 2-G to 3-G handover

Feature overview
This GSM feature supports handovers between different Radio Access Technology (RAT)
networks in the Circuit Switched (CS) domain. The RAT can be either 3G Universal
Mobile Telecommunication System (UMTS) or 2G GSM.
Feature description
Current evolving 3G UMTS networks soon will allow operators to provide UMTS
coverage along with GSM/GPRS coverage in their networks.
This feature enables a multi-RAT Mobile Station (MS), a mobile station that can function
in multiple Radio Acess Networks (RAN) to hand over calls between a GSM Radio
Access Network (RAN) and a 3G UMTS Radio Access Network (UTRAN). To accomplish
this, support is needed from the MS, Core Network elements of the MSC and
UMTS/GSM network elements.
The GSM BSS support for this feature includes:
S
3G (UMTS) to 2G (GSM) handover in active mode and cell reselection in idle

mode.
2G (GSM) to 3G (UMTS) cell reselection in idle mode.
Being a completely new GSM function, a full description is available in the Technical
Description: BSS Implementation (68P02901W36) manual.

02 May 2003
68P02901W01-M
559
GSR6 (Horizon II)
Clean install (E3x00)

Feature overview
The purpose of this feature is to install the OMC-R on an E3000/E3500 server. As Sun
are making their current Solaris system obsolete, from 2001 only Solaris 8 is shipped.
Therefore, the Operations and Maintenance Centre-Radio (OMC-R) has its operating
system upgraded.
Feature description
This feature installs the OMC-R on an E3000/E3500 server. As part of the clean install,
OMC-R customers will be using the Solaris 8 operating system.
For customers upgrading from a previous OMC-R release, a procedure to upgrade from
Solaris 2.51 to Solaris 8 is included in the OMC-R Upgrade.
A Solaris 8 licence is provided as part of the GSR6 package.
560

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
GPRS interleaving TBFs

Feature overview
This release is an extension to the software feature which introduced the General Packet
Radio Service (GPRS).
The Interleaving Temporary Block Flow (TBF) feature allows the rapid multiplexing of
Radio Signalling Link (RLC) data blocks of many different MSs onto a common air
resource. Multiple MSs are then able to share a common air resource although effective
throughput of each MS on that shared resource may be decreased.
Feature description
Each MS sharing a common air resource is given a certain percentage of the shared
resource bandwidth. For example, if two MSs are interleaved on the same air timeslot,
one MS may be given 70% of the timeslot, while the second MS may be given the
remaining 30% of the timeslot. This is illustrated in Figure 5-1.
Figure 5-1 Example of Interleaving DL TBFs
RLC DATA BLOCKS
MOBILE A
MOBILE B
= IDLE RLC BLOCK
= RLC DATA BLOCK
This interleaving increases the number of users that can be on a single timeslot,
increasing the overall capacity of a serving cell.
Interleaving TBFs in the uplink and downlink direction use block-by-block multiplexing, in
which two or more MSs are multiplexed on a timeslot with the capability of switching
between MSs every block period.
All of the MSs on a timeslot are all simultaneously active in TBFs. The TBF setup phase,
TBF release phase, or data transfer phase of one MS TBF may overlap with the TBF
setup phase, TBF release phase, or data transfer phase of other TBFs belonging to other
MSs.
02 May 2003
68P02901W01-M
561
GSR6 (Horizon II)
Delayed release of downlink TBF

NOTE
Delayed release of downlink TBF is sometimes known as

Supercoattail.
The delayed release of downlink TBF extends the downlink Temporary Block Flow (TBF)
period by 4.5 seconds by transmitting dummy Logical Link Control (LLC) frames. By
delaying the downlink TBF release, there is no need to send a new Packet Downlink
Assignment (PDA), allowing data to be sent straight away in the next block period. It also
means that if the MS uplink needs to be established while being polled during the
extended downlink TBF period, the CCCH and RACH do not have to be accessed, and a
channel request in the DAK message is sent instead, reducing the UL TBF establishment
time by 500 ms.
Before the dummy LLC frames are sent, all previous LLCs are acknowledged by the MS.
If no meaningful data is sent by an MS on the PD channel for 4.5 seconds, interference
to other MSs transferring data can be caused. To reduce this interference, the CS1 data
blocks corresponding to the dummy LLCs are only sent on the Packet Associated Control
Channel (PACCH) timeslot when the MS needs to be polled.
562

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Link utilization improvements

Feature overview
Previously, within the BSS software, the signalling messages exchanged between the
Radio Sub System (RSS) and Packet Resource Manager (PRM) processes, over the
Radio Signaling Link (RSL) and the GPRS Signalling Link (GSL), had a large header
compared with the data part of the message and consequently this produced a
transmission delay. In addition, the BSS software sent one message per Link Access
Procedure for ISDN D-Channel (LAPD) frame on the RSL and GSL links; this did not fully
utilize the maximum size of the LAPD Unnumbered Information (UI) frame.
This feature improves the performance of the RSL/GSL links and alleviates the expected
pressure on the capacity and speed of the links from the expanded capacity and high
speed GPRS features. The link utilization improvements feature reduces the message
transmission time between the BTS and PCU for the InCell, Horizonmacro and
Horizonmicro/Horizoncompact by 35% to 40%, 20% to 35% and 15% to 30%
respectively. The number of GPRS timeslots that the RSL can support should be
increased by 40% in most GPRS BTS configurations.
Feature description
The link utilization improvements feature addresses the above issues to speed up
messages exchanged between the RSS and PRM. The following enhancements have
been made:
S
Smaller header for delivering messages between the RSS and PRM
The new message header is eight bytes and contains minimum information
necessary to deliver the messages between the two processes. The functionality
of the existing routeing functions will not change and a new set of routeing
methods and Application Programmer Interfaces (APIs) are created for the
application processes to use.
Message packing/unpacking mechanism at the RSL and GSL end-points

This improves both speed and utilization of the RSL/GSL links by packing more
than one signalling messages into the same LAPD frame thus reducing the LAPD
header overhead. Messages waiting in the RSL/GSL mailboxes are packed in one
LAPD frame before writing it to the link, and it is unpacked when it is read from the
link.
Creating a high priority mailbox
The feature creates a high priority mailbox call LUI mailbox in the Executive Data Link
Service Process (Exec DLSP) for certain high priority messages between the RSS and
PRM. This mailbox is created at both the BTS and PCU. This enables processing of
messages in the LUI mailbox at a higher priority than messages in all other RSL/GSL
mailboxes.
The RSS and PRM uses the small header with high priority for only certain high
priority messages. The messages sent with this option are routed to the LUI
mailbox and all other messages between the RSS and PRM (using the small
header/normal header) are sent to the RSL/GSL mailboxes. With this feature, the
RSS and PRM can send and receive the following messages:
Messages with normal headers, which go to RSL/GSL mailboxes.
High priority messages with small headers, which go to the high priority LUI
mailbox.
Normal priority messages with small headers, which go to the RSL/GSL
mailbox
02 May 2003
68P02901W01-M
563
GSR6 (Horizon II)
Advanced load management for EGSM carriers

The advanced load handover management function offers the operator the ability to
specify EGSM band handovers only to other EGSM bands. Otherwise EGSM handovers
can occur to neighbouring cells that may not have an EGSM band available. DCS1800
bands may be used wastefully, particularly if the band_preference parameter is set, for
example, to DCS1800. A new parameter bss_egsm_alm_allowed enables the feature
and EGSM handovers will occur to EGSM sites if available, whatever the setting of
band_preference.
When a handover is triggered with this feature set, the neighbour list of an EGSM MS on
an EGSM resource is manipulated such that EGSM internal neighbour cells are given
preference over non-EGSM neighbour cells.
Enhanced GPRS One Phase Access

Feature overview
This feature enables Enhanced General Packet Radio Service (GPRS) One Phase
Access with the Packet Control Unit (PCU) at the Base Station Controller (BSC)
(Pre-load).
In a GPRS network, there are two packet access procedures that the mobile can use to
establish an uplink TBF. The packet access can be done in either one phase or in two
phases. In the current GPRS software architecture, the Base Station System (BSS) only
supports the two phase access procedure. The intent of this feature is to introduce the
one phase procedure, as well as improvements to both procedures.
Enhanced GPRS One phase uplink TBF access is an improvement over the two phase
uplink TBF access procedure. In a one phase uplink TBF access, the MS initiates an
uplink TBF by sending a Random Access Channel (RACH) to the BSS. The RACH is
received at the BTS, which is then forwarded to the PCU. The PCU responds to the
RACH with a Immediate Assignment message containing an uplink assignment. The MS
moves to the assigned Packet Data (Traffic) Channel (PDTCH) and begins its uplink data
transfer. This procedure allows the MS to gain access to the network much quicker
when comparing against the Two Phase establishment procedure.
Refer to Technical Description: BSS Implementation (68P02901W36) for a full description
of the differences between the two access methods.
564

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Remove support for collocated BSC

Feature overview
Support for the collocated InCell/BSC will be disabled in GSR6 to enable compressed
BTS objects to be stored at the BSC in order to free up memory for new GSM and GPRS
features.
See also feature Compress all BTS objects at the BSC.
A collocated InCell/BSC site will not be able to continue to operate in GSR6 release.
This feature will enable all BTS objects to be stored in compressed form at the BSC in
order to free up memory for new GSM and GPRS features
Support for the collocated InCell/BSC will be disabled by blocking access to key
commands to prevent equipage of a collocated BSC.
Operators with collocated BSCs in their network have two choices:
S
Prior to upgrading from 1620 to 1650, all collocated InCell/BSC sites can be
converted to standalone InCell and BSC sites.
All collocated BSCs should remain at pre-1650 release, while remainder of network
will be upgraded to 1650.
Compress all BTS objects at the BSC

Feature overview
This feature is designed to save memory at the BSC by compressing all BTS objects at
the BSC and uncompressing them at the BTS. In addition it will speed up OMC to BSC
and BSC to BTS download times.
See also feature Remove support for collocated BSC.
All non-BSC objects (Incell BTS, M-Cell etc) are compressed as part of the object build
and are stored in compressed form at the BSC to save memory.
The compressed objects are downloaded to the BTS and uncompressed as part of BTS
initialization.

02 May 2003
68P02901W01-M
565
BSS software release GSR6 (Horizon II)
GSR6 (Horizon II)

GSR6 (Horizon II) features
Table 5-27 summarizes the BSS features provided at software release GSR6 (Horizon
II).
Table 5-27 Release GSR6 (Horizon II) features
Description
{4420} Horizon II
{4443} Enhanced two uplink timeslots
{4471}{ Removal of support for Horizonoffice
Horizon II
{4420}
Feature overview
The Horizon II feature provides support for the new Horizon II macro BTS and the CTU2
transceiver.
The Horizon II feature comprises the following elements:
S
Double density carrier CTU2 transceiver
Support of up to six double density CTU2s in the Horizonmacro and

Horizon II macro platforms.
Backwards compatibility with the existing Horizonmacro platform
The CTU2 transceiver provides the following functionality:

The CTU2 transceiver supports two logical carriers and can operate in either single or
dual carrier mode. It is backwards compatible with the Horizonmacro platform, and may
be operated in single or dual carrier mode in both the Horizonmacro and
Horizon II macro BTS cabinets.
Combinations of TCU-A, TCU-B, CTU and CTU2 in single carrier mode and dual carrier
mode are allowed within a cell providing RF power restrictions are obeyed.
Transmit power capability is different for single and dual carrier modes, see Table 5-28 .
566

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Table 5-28 CTU and CTU2 output power capabilities

Horizonmacro
Horizon II macro
Transceiver
type
Combining
EGSM900
DCS1800
EGSM900
DCS1800
CTU
None
40
32
N/A
N/A
External
20
16
N/A
N/A
None
40
32
63
50
Internal
20
16
28
22
None
10
10
20
16
Internal and
external
4.5
4.5
CTU2
Single carrier
mode
CTU2
Dual
D
al carrier
mode
In single carrier mode the CTU2 capabilities are similar to those of the existing CTU, and
the CTU2 can be used as a replacement for the CTU providing GSR6 (or later) software
is used.
In dual carrier mode, the CTU2 enables the Horizonmacro or Horizon II macro to support
up to twelve carriers. There are however certain restrictions when the CTU2 operates in
dual carrier mode:
S
Baseband hopping is not supported when the controlling cabinets are either
Horizonmacro or M-Cell, due to the switching capability of the MCU/MCUF.
Maximum output power capacity is reduced due to internal combining within the
CTU2.
In Horizonmacro cabinets, maximun output power of a CTU2 in either single

density or dual density modes, is also restricted by the Horizonmacro cabinet
power supply.
Remote Tune Combining (RTC) is not supported if the CTU2 is operating as a

master or standby controller of an RTC, however RTC can be used if the CTU2 is
not the master/standby controller.
Both carriers must be in the same cell because the CTU2 has one single RF
output.
The Horizon II macro BTS can be either the controlling cabinet or extension cabinet
connected to a controlling Horizon II macro/Horizonmacro/M-Cell BTS cabinet.
BTS sites with Horizonmacro/M-Cell6 as the controlling cabinet
must have a PCMCIA card fitted for CTU2 to be supported.
NOTE
The Horizon II macro BTS provides the following functionality:

S
Support of up to six double density CTU2s, which will provide up to 24 carriers in

two Horizonmacro/Horizon II macro cabinets.
Horizon II macro Site Controller (H2SC) with integrated NIU and FMUX, E1
support and enhanced E1 redundancy, and Increased removable flash media.
SURF2 (Sectorized Unified Receiver Front end)
XMUX
Site I/O Panel
Increased Radio Signalling Link (RSL) functionality
Interoperability with the existing Horizonmacro/M-Cell BTS platform.
Horizon II macro cabinets only support a single frequency band, 900 or 1800 MHz.
Multiband cabinets are not available.
02 May 2003
68P02901W01-M
567
GSR6 (Horizon II)
Enhanced two uplink timeslots

{4443}
Feature overview
Enhanced two uplink timeslots (2UL) is an extension to the GPRS feature (RDB2773)
introduced in GSR4.1, and the Multiple GPRS carriers per cell (RDB3725), Interleaving
TBFs (RDB4253), and Enhanced one phase access (RDB4386) features introduced in
GSR6.
This feature improves MS GPRS performance by allocating multiple timeslots in the
uplink direction.
Feature description
In GSR6, GPRS multi-slot class MSs which support multiple timeslot allocations in the
uplink and downlink directions, were only allocated one uplink timeslot. The Enhanced
2UL feature provides allocation of up to two uplink timeslots for the MSs that support
multiple uplink timeslot allocation.
This feature improves the performance of MSs that support multiple uplink timeslot
allocation and comprises two sub-features:
S
Enhanced 2UL timeslot scheduling
Advanced uplink/downlink bias detection
Enhanced 2UL Timeslot Scheduling

This enables operation of two uplink timeslots for MS multi-slot classes that support it. All
multi-slot classes that support multiple uplink timeslots in dynamic mode are mapped to
multi-slot class 5, 6, 9 or 10.
Table 5-29 shows the MS multi-slot class mapping for all GPRS multi-slot classes.
Table 5-29 MS multi-slot class mapping for all GPRS multi-slot classes
568
Multi-slot class
Supported as multi-slot class
01
01
02, 03
02
04
04
05
05
06, 07
06
08
08
09, 13
09
10 12, 14 29
10

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Advanced Uplink/Downlink Bias Detection

For some multi-slot class MSs the maximum number of uplink and downlink timeslots in
the MSs allocation is less than the sum of the maximum number of timeslots that can be
allocated in an individual TBF direction. These MSs can be allocated more timeslots in
one direction at the expense of fewer timeslots in the opposite direction. This type of
multi-slot class is called a biasable multi-slot class. The Enhanced Two Uplink Timeslots
feature supports biasable multi-slot classes 6 and 10.
Figure 5-2 shows the multi-slot class 6 MS uplink bias configuration of two timeslots in
both downlink and uplink directions, or downlink bias of three downlink timeslots and one
uplink timeslot.
Figure 5-2 Multi-slot class 6 uplink/downlink bias timeslot allocation
TS
DL
UL
UL Bias
Class 6
DL Bias
Class 6
Figure 5-3 shows multi-slot class 10 MS uplink bias configuration of two uplink timeslots
and three downlink timeslots, or downlink bias of four downlink timeslots and one uplink
timeslot.
Figure 5-3 Multi-slot class 10 uplink/downlink bias timeslot allocation

TS
DL
UL
UL Bias
Class 10
DL Bias
Class 10
The bias change mechanism is based on the data transfer characteristics in the uplink
and downlink directions. During uplink data transfer for example, the uplink direction is
highly active compared to the downlink direction, the MS therefore receives an uplink
biased timeslots allocation.
Although MS multi-slot classes 5 and 9 support multiple uplink timeslots, these MSs do
not have the restrictions of biasable classes. Consequently, uplink/downlink biasing does
not apply to MSs of class 5 or 9.
02 May 2003
68P02901W01-M
569
GSR6 (Horizon II)
Removal of support for Horizonoffice

{4471}
Feature overview
Support for the Horizonoffice BTS is removed in GSR6 (Horizon II).
570

68P02901W01-M
02 May 2003
Chapter 6
OMC-R software release features

02 May 2003
68P02901W01-M
61
GSR6 (Horizon II)
62

68P02901W01-M
02 May 2003
Introduction to OMC-R software release features
GSR6 (Horizon II)
Introduction to OMC-R software release features

In this chapter
The following chapter summarizes the configuration features of the Motorola OMC-R
software releases. Motorola GSM products are continually being updated. Releases of
software before GSR2 were identified by four-digit release numbers, such as 1.2.1.1.
After the 1.4.1.x release, the numbering system was revised, and release 1.5.0.x has
been renamed GSR2.
This chapter describes the main features of each OMC-R software release:
S
OMC-R software release 1.1.2.0.

NOTE
The 1.4.1.x OMC-R software provides support for the BSS

software release 1.4.1.1.
OMC-R software release GSR2.
OMC-R software release GSR4.1
OMC-R software release GSR6 (Horizon II).

02 May 2003
68P02901W01-M
63
OMC-R software release 1.1.2.0
GSR6 (Horizon II)

Configuration
In OMC-R release 1.1.2.0, the OMC-R configuration comprised the following:
S
System Processor: Tandem A21.
X.25 link.
Man-Machine Interface (MMI) Processor.

The following features were included in OMC-R release 1.1.2.0:
64
Sounding of a bell whenever a new alarm is sent to MMI.
A timeout variable for the X.25 connection establishment phase.
A timeout variable for the data transfer phase.
A timeout variable for the supervision of IPC response messages from both CM
and LM (Uploader).
Two versions of tabular key statistics reports, together with an interactive graph
option.
On parsing a BSS statistics file, the parser moves it to:
filename.parsed.
filename.bad_header.
filename.FATAL_ERROR.
Fatal errors cause the Parser to terminate.

(For example, unable to connect to db.)
The parser no longer accepts statistics following a PROCEDURE tag.
The parser expects a DURATION field in file headers. Durations of plus or minus
5 seconds are accepted for parsing. No other files are parsed.
The valid header year range changed from 1980 to 2079.
An MMI printer command is provided, and the ability to change the font of text in
Subscription List windows.
Subscription by device class.
Event log post-processing utilities (cel, fes, qfes, ces).
Automatic backup of uploaded database.
Automatic backup of load directory on selection of new software load.
The Event Interface subsystem generates a critical alarm for all Network Elements
(NEs) in the network as reported by CM on system start up. It generates a clear
alarm for each NE link brought into service, that is, for each link for which a
connect request is received. Subsequent link failures or recoveries are
accompanied by corresponding alarms and clears. In addition to the above,
whenever a link goes down or comes up, a message is written to the OMC-R audit
file indicating the current time and the NE device ID associated with the link.
Log files created for update and cutover procedures.
OMCINIT logs information to OMC-R audit file.
Uploads tagged in OMC-R audit file with process id.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

Configuration
S
MMI Processor.

S
IPC logging is ENABLED by default in this release.
OMC-R Database Schema upgraded to remove some indexes on the PM stats

tables.
The OMC-R Watchman script (omc_watchman) provides facilities for monitoring

the OMC-R processes running on the System Processor. It also provides facilities
for informing OMC-R operators if any of the OMC-R processes terminate.
Event Processing utilities.
The rate at which MMI attempts to process events and what action MMI takes
when flooded with events can be configured via environment variables.
$DBMS_ROOT/bin/db_pm_maint modified to:
Increase performance.
Accept additional parameters when invoked.
Manually, as well as automatically, cleared alarms change from red to black.
Six new parameters added to the BSS Add Cell command. The Change, Add and
Display Cell commands modified. The added parameters are:
d1_ncell_proc (01).
d1_missing_rpt (01).
d1_ba_alloc_proc (01).
full_pwr_rfloss (01).
d1_sdcch_ho (01).
d1_sdcch_timer_ho (031).

02 May 2003
68P02901W01-M
65
GSR6 (Horizon II)

Configuration
S
System Processor: Tandem A22
MMI Processor

S
Kernel parameter changes: MAXUMEM increased to 6 X 4096.
Installation: size of logical logs increased, number of logical logs decreased, size
of physical logs increased.
db_pm_maint utility: approach to maintenance is changed from the

lock-restrictions approach to a configuration row-set approach.
IPC logging is ENABLED by default.
Manual submission of stats files for parsing.
MMI support for multiple printers.
Manually handled and cleared alarms are written to the event log. The alarm is
written to the log with the current time, new status field and user name of the
operator handling or clearing the alarm. Note that the original alarm appears with a
status field NOT APPL in the event log.
Command partitioning: a new read-only OMC-R MMI, if required.
Notification of incoming events/alarms in iconized event/alarm windows.
Support for EAS in MMI.
Subscription list sorting: events extracted from AET are displayed in chronological
order.
Performance Management stats filtering:
66
Filter RF_LOSSES_TCH.
Filter CHAN_REQ_MS_FAIL.
PM_SD_FILTER.
Support for both 30 and 60 minute stats file collection.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Front End updates for release 1.1.2.2. The OMC release 1.1.2.2 Front End
supports both BSS version 1.1.2.1 and version 1.1.2.2. To change which BSS
version is supported, the BSS_VER environment variable can be set appropriately.
A new menu option, Version, has been added to display the current value of
BSS_VER.
Ability to view call trace output at the OMC-R.
Support for Remote Tune Combiner device.
Display of OMC-R software load version number (Tandem and MMI).
Display of additional alarm Information at OMC-R.
Channel number displayed in HEX at the OMC-R.
KSW displayed correctly in events and alarms (not as TDM).
Tab operation allowed in MMI dialogue boxes.
Naming of event log changed to evYYMMDDHHMMSS.
Input buffer size for X.25 data in the Event Interface application has been
increased from 165 to 1024 bytes.
Logging of messages added to the Event Router and List Manager processes.
Date format for PM is now user configurable (PM_DATE_FORMAT).

02 May 2003
68P02901W01-M
67
GSR6 (Horizon II)

Configuration
S
MMI Processor: OSF/MOTIF 1.1.1.

Table 6-1 summarizes the OMC-R release 1.1.2.3 main features.
Feature
Description
load_db and activate_db
Two scripts allow the installation from tape of a NE

database, generated on a test BSS system, on to the
OMC-R. The load_db script reads a NE database
from tape and installs it on the OMC-R. The
activate_db script moves a NE database, installed
via load_db, from the installation directory to the
current database location of a specified NE.
Critical alram threshold

exceeded
Supports for MMS alarm Critical alarm threshold

exceeded to inform the operator when the critical MMS
alarm threshold is exceeded and the MMS is disabled.
The alarm string is included in MMI MIT data file.
Comfirmation dialogues
Relates to confirmation of user commands. Throughout

the MMI area for delete and modify commands and
potentially dangerous commands (for example, Disable
Logging) the user is prompted with a confirmation
dialogue box. The user can select OK to continue or
CANCEL to cancel the operation.
Date/time on event logs
A date/time stamp written at the start of every event

log file when it is first opened. It is not visible to the
OMC-R operator and is intended to be used only by
event post processing utilities.
Customizing database reports Consists of two simple methods of retrieving database

data for display, namely, interactive ISQL, and a simple
INFORMIX report generator called ACE.
Alarms and events
highlighted when selected
68
Alarms and events are highlighted when selected in an

Alarm Display, Event Display or Event Log. An
alarm/event remains highlighted until another
alarm/event is selected.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Additional features
The following additional features were included in OMC-R release 1.1.2.3:
S
Customizing PM Reports document.
Support for new EAS alarm: the alarm Bad Daughter Board ID read possible bad
EAS board replaced the Bad ID alarm to get output when an EAS board is
unseated.
MMI maintains its local list of selectable NEs. There is no need to log out MMI
sessions after deletion of a node.
Potentially separate Subscription Lists for Events and Alarms, configurable using
MIT file.
BSP and DHP alarms added to MIT file.
No Object field changed to Object No in Upload Status window.
EM router no longer exits on an error return code from the IPC subsystem.
More description error messages added to EM List Manager.
Time Now option removed from PM reports.
On the MPC, getlogin replaced by cuserid.
Updated omc_db_ckspace script.
Immediate printing of events and alarms.

02 May 2003
68P02901W01-M
69
GSR6 (Horizon II)

Configuration
S
MMI Processor.

Table 6-2 summarizes the features included in OMC-R release 1.1.2.4.
Feature
Enhancement for
omc_watchman script
Description
The omc_watchman script sends a mail message to
the users specified by the variable MAIL_ADDRESS
when an OMC-R process terminates. The message
specifies which process has terminated. In addition
watchman.log logs any processes reports on
omcinit, and logs any processes that have terminated
while watchman.live reports which processes are
currently alive.
Disconnecting applications for The OMC-R database can be brought down to single
on-line DB maintenance
user mode for certain types of maintenance. The
applications connected to the database (EM and PM)
can handle database disconnection and reconnection.
This is to cater for db on-line maintenance.
610

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

Configuration
In OMC-R release 1.2.0.0 the OMC configuration comprised the following:
S
MMI Processor (MPC).
MMI Processor (SPARC 10).
In addition, the following is optional:

S
NCD XRemote software.
MMI Processor (SPARC IPX).

Table 6-3 summarizes the OMC-R release 1.2.0.0 features.
Feature
Description
Display of loads on i-CM

modifiy window
As part of the X upgrade to X11R4 the horizontal scroll

bar for the Load Names list (in the i-CM Node Modify
window) is not included by default. This list is
automatically resized, if possible, and the horizontal
scroll bar is only present when it is not possible to
resize the list.
Graph of raw stats
Default worksheets enable the graph option for all

statistics as soon as they become available.
Command constructor closing Command Constructor closes following confirmation of

on X.25 connection break
X.25 connection break error message and the Wingz
license is freed.
Add alarm strings for
transcoder to BSC link (XBL)
XBL alarms which will be supported by BSS Release

1.2.0.0 are supported at the OMC-R. These include
twelve hardware alarms and three PM alarms. The PM
alarms are similar to those defined for RSL and OML
devices.
Support XBL stats
A parser, database and PM-UI are provided to support

XBL statistics.
Periodic supervision of
accessibility
The OMC-R periodically polls the NEs with open

connections to the OMC-R for their status. If an NE
informs the OMC-R that is is not operating correctly, a
CRITICAL processing Failure Event is generated for
that NE, with an error Id of BSS Error State [30006]. If
an NE fails to respond to an OMC request for its
status, the OMC-R generates a CRITICAL processing
Failure Event for that NE, with an error Id of BSS Resp
Timeout [30005].
Save alarm context
If the BSS-OMC-R connection goes down, the BSS

buffers events/alarms until connection is
re-established. If the buffer overflows (with more than
100 events/alarms), an alarm is sent from BSS to the
OMC-R indicating this. The OMC-R supports this BSS
alarm (Id 4), alarm string Event Buffer Overflow.

02 May 2003
68P02901W01-M
611
GSR6 (Horizon II)
Feature
612
Description
BSS stats changes
Supports changes made to BSS statistics.
Support new BSS alarms
Introduces new BSS alarms.
Port of MPC applications to

SPARC
All current MPC applications are ported to the SPARC

platform.
Incorporation of cron jobs
New scripts support listing, removing, archiving and

rolling over log files produced by the OMC-R. These
scripts have been written with a view to running them
from cron.
Immediate sld program buffer

flushing
The sld program flushes its buffer immediately to

standard output following a buffer write. Previously this
was done only when the buffer was full. The change
enables immediate printing of alarms.
Remote x terminal support

over a dial up line
Users may access the OMC-R via a remote X terminal

using XRemote. When using XRemote the Event
Manager Subscription should not be displayed for long
periods, especially when high event rates are involved.
M and O defined on forms

worksheets
The two worksheets EquipDRI.wkz and

EquipRTF.wkz are updated with a description of
M/O/P (Mandatory/Optional/Predefined).
Error message if X.25

connection lost
In the absence of an X.25 connection, the command

constructor displays an error message. On
confirmation of the error message the command
constructor closes and the Wingz license is freed.
New directory BS GSM-1200

to support BSS
A directory BSGSM-1.2.0.0 is created as part of the

install/upgrade procedure on the MPC. The
install.M and update.M files are modified to create
the BSGSM-1.2.0.0 directory and its associated
sub-directories.
Management of
watchman.log file
When the omc_watchman.log script is executed a

log file is created. The script roll_watchman.log
forces a roll-over of the log file when executed. The
script moves the existing watchman.log file to the
filename watchman.log.yymmdd. It is recommended
that this script be executed once a day from cron.
Reason strings changes
The OMC-R reason strings are made consistent with

those used at BSS MMI and BSS FM and with those in
the Trouble shooting Guide. A new reason string is also
added for COMBINER CONTROLLER.
IAS device ID change
The Id for BSS device IAS is changed from

SITECAGEIAS to SITECABIAS.
Support new BSS PATH

device
Supports a new device, PATH, in BSS release 1.2.0.0.

The new path device Id is 42. The MMI name is PATH
and the format of the BSS MMI device identifier is
SITE,PATH. The SITE is the connected site on the
other end of the PATH. The PATH is a unique identifier
(0 9) within the reporting site.
Work in progress message

for Wingz
The command constructor displays a work in progress

message while being invoked. The performance
management reports generator also displays a work in
progress message while being invoked.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Feature
Description
MIT file updates
Two new tables are defined in the MIT File for Event
State Definitions and Alarm Format Definitions. These
are required for Event Log Processing utilities.
New 4GL reports
Consists of four key statistics 4GL report modules,

which provide key statistic data summary reports
summed over time for each cell and BSS. These
reports can be invoked interactively from the UNIX
command line, or automatically by using cron. These
report modules give an indication of the quality of
service the GSM network is currently providing.
OMC-R forms for BSS

modifications
Updates to the OMC-R (forms) support changes made

to the BSS software.
New directory
BSGSM-1.1.2.3
A new directory for the forms software supports

BSGSM1.1.2.3. The install and upgrade utilities are
modified to create this directory.
Using cron to produce key

stat reports for yeaterday
The key_stat_reps script is invoked from the cron

table early each morning. This produces reports in a
directory under the $PM_LOG directory, which may
also be printed on request. These reports are
key_stat reports for the network for the day previous
to which the script is called. The script removes all
previous reports from $PM_LOG prior to generating
the new ones.
OMC-R key stats on MMI

processor (MPC)
Key statistics are provided on the MMI processor.
OMC-R key stats on MMI

processor (SPARC)
Supports The key statistics used by the 4GL PM

command line reports.

02 May 2003
68P02901W01-M
613
GSR6 (Horizon II)

Configuration
In OMC-R release 1.2.2.1. the revised/additional requirements are as follows:
S
System Processor.
MIB Processor (SPARC).
In addition, the following is optional:

NCD XRemote software.
S
MMI Processor (SPARC IPX).
MMI Processor (SPARC 5).

Table 6-4 summarizes the OMC-R release 1.2.2.1. features.
Feature
614
Description
Network status summary
Allows the operator to select a map of all, or part of the

network. The selected map can be configured to
display the Network Elements (NEs), links in the
network and the sites and links contained within an NE.
Maps can be topological or geographical.
Alarm and state

synchronization
Provides a mechanism for synchronization of the

OMC-R and BSS/RXCDR device status at OMC-R
initialization time, and after a failure of the OMC-R or
BSS/RXCDR or the links between them. Status
information is composed of both alarm and device state
information. Synchronization occurs automatically at a
configurable interval.
Audible alarm
The OMC-R provides an output to drive an audible

alarm. The output is activated whenever alarms higher
than a programmable severity are detected. The alarm
severity level will be configurable on a system-wide
basis only.
OMC-R application fault

management
Unrecoverable failures in OMC-R applications generate

internal alarms. For OMC-R release 1.2.2.1, fault
notification only is provided.
OMC-R system
administration
Allows installation of the OMC-R software for the

1.2.2.1 release.
OMC-R installation utilities

and directory structure
Separates release dependent information from release

independent information so that the operator does not
loose configuration information during an upgrade.
4GL/GX performance
management reporting
Performance Management (PM) reporting is now

based on Informix 4GL/GX. Operators can access
performance data via the MMI processor using the PM
reporting module of the OMC-R MMI. There is also an
enhancement to PM reporting whereby it gives a value
for all the intervals present, but flags the fact that full
coverage of the interval measured was not possible.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Feature
Description
Total calls statistic
This statistic is added to the existing 16 key statistics.
Zero filter and rollup
The Parser is modified such that

CHAN_REQ_MS_FAIL statistics with zero values are
not inserted in the database. This saves insertion time
and database volume requirements as well as
eliminating the restrictions on the use of the 1.1.2.2
CHAN_REQ_MS_FAIL filter. A cell level value is also
inserted for this statistic, representing the sum of the
individual channel values for the collection period in
question.
Interim logging of change of

access rights
Provides information on which users are currently

installed in the OMC-R and what their privileges are. A
log record is added to the log file each time a user is
added or deleted.
Compression of BSS
software objects at the
OMC-R
Allows the OMC-R to store backup NE databases in a

compressed format on the OMC-R. This reduces the
amount of disk storage required to store databases at
the OMC-R and simplifies operator procedures.
OMC-R audit process
Monitors the following: X.25 lines connected to the

tandem system processor, tandem hardware unit
integrity, disk space usage on the Tandem /usr
partition. The feature produces alarms for these areas
under certain conditions.
Alarm filtering by device type

and alarm code
Provides the following event and alarm enhancements:

subscription of alarms by Error Id, subscription of all
events by Device Type (Obj Class), display of alarm
additional information fields.
Event log search and print

option
Provides the operator with the following facilities: one

or more event logs may be selected for
post-processing, searches for events can be performed
according to event log filtering criteria, a collection of
events which meet the specified search criteria is
formed, the collection of events is sent to standard
output, search and input of selection criteria can be
invoked from MMI menus.
Load management comment

and memo field
Provides enhanced user input capabilities from the

OMC-R MMI terminals.
All but subscriptions

(blocking)
The Add and Modify Subscription windows have been

modified to allow blocking of subscriptions for a specific
Subscription List. There is also an Equal/Not Equal
toggle button on the Error Id field.
Support of 1 Gbyte
configuration
From the 1.2.2.1 release onwards support is given for

a 1 Gbyte Tandem system disk. Support will continue
for the existing 650 Mbyte system disk. Note that the
1 Gbyte disk allows for increase in database size.
Night concentration
Allows an operator be able to handover management

of one network region to another OMC-R during the
night shift. This necessitates the provision of a
mechanism to allow a single workstation to access
multiple System/MIB processor pairs.

02 May 2003
68P02901W01-M
615
GSR6 (Horizon II)
Feature
616
Description
Blacklist subscription list
An alarm blacklist is introduced to provide system wide

blocking of specific alarms, to prevent them reaching
the MMI; they are still logged.
Change cell command split
The change cell command is split up into 11

sub-sections.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

Table 6-5 summarizes the OMC-R release 1.2.2.2 features to support the BTS6, ExCell6
and TopCell cabinets.
Table 6-5 Release1.2.2.2 features
Feature
Description
BSS support activities
Provides support for the statistics and alarms defined

by BSS release BSGSM 1.2.2.2.
Auto initiate alarm windows
Allows alarm/event subscription windows to be

automatically opened on start up of an MMI session.
Total calls statistics
The key statistic total calls replaces the existing paging

load in the call summary key statistic.
Forms updates
A new parameter called TRU identifier is added to the

EquipDRI worksheet after the Slot number.
Databse management
A new script, delete_CELL is added for deleting cells

from the schema. This script provides similar
functionality as the scripts for managing the deletion of
BSS and SITE information.

02 May 2003
68P02901W01-M
617
GSR6 (Horizon II)

Configuration
In OMC-R release 1.2.3.0. the revised/additional requirements are as follows:
S
System processor.
MIB processor software (either SPARCstation 10 or 20).
MMI processor software.

Table 6-6 summarizes the OMC-R release 1.2.3.0. features.
Feature
618
Description
NMC-OMC-R security
application (optional)
Supports the optional security application on the

interface to the NMC. The purpose of this feature is to
provide secure access to the OMC-R via Remote Login
over an OSI Stack.
System administration
Provides the necessary procedures and scripts to

install the 1.2.3.0 OMC-R and to install the SAC
application on the OSI and RLP processors.
BSS support activities
Provides support for the statistics and alarms defined

by BSS release BSGSM 1.2.3.0.
Graphical key statistics

save selection
Enables the Operator to save the Date and Time

selection and the NE selection.
MMI audit trail - BSS MMIs
Stores the commands carried out on the BSS, from the

OMC-R, along with a time stamp.
Rlogin modifications
Enables an Operator to remote login to a NE while a

database upload is in progress. The Operator is
warned of the database upload.
Batch based time updates
Provides a script which sets the time automatically at

the BSS, controlled by an OMC-R. The time is set
using BSS MMIs.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

The OMC-R software is supplied on one CDROM which includes software for the System
Processor (Tandem), the MMI Processor (SPARC) and the MIB Processor (SPARC). In
addition to the OMC software, the CDROM also contains third party product software for
Solaris patches, Informix, Motif and X11R5.
In addition to the OMC-R CDROM, one additional CDROM is supplied which contains the
Worldview version 2.0.1 software release, and one cartridge tape is supplied containing
the Wingz software release.
Table 6-7 summarizes the new OMC-R software release features for 1.3.0.0.
Feature
Description
Network Configuration
Management (NCM)
Augments the BSS configuration data maintained at

the OMC-R, allows the manipulation of the data from
the OMC-R and supports the synchronization of this
data with the BSS. It centralizes the configuration data
at the OMC-R, supports the logging of changes and
creates the infrastructure to support the creation of
BSS binary from the OMC-R.
Code Storage Facility

Processor (CSFP)
Allows the online download of a new BSS load, from

the OMC-R to the BSS, to support the fast swapover to
a new load, thus reducing BSS downtime. This feature
also includes support for electronic transfer of BSS
databases from the Datagen platform to the OMC-R.
Online help from GSM

documentation
Provides the OMC-R user with a context sensitive help

facility, covering all aspects of work at the OMC-R,
including information on the BSS.
1.3.0.x systems
administration
Provides the mechanisms for doing a clean installation

of the GSM OMC-R system or for upgrading a current
(1.2.2.X/1.2.3.0) OMC-R system to the 1.3.0.0
software release. Utilities for administrating the
OMC-R databases and log files are also included.
Operability enhancements
Provides a forms interface to support the following

Operations and Maintenance procedures:
Report all out of service devices.
Add devices.
Interface to the OMC-R batch facility.

02 May 2003
68P02901W01-M
619
GSR6 (Horizon II)

Most of the new features and enhancements to the OMC-R software for 1.4.0.0 are
brought about by the introduction of a revised hardware platform.
New OMC-R systems will use the new OMC-R System Processor, the Tandem Integrity
S1475, while existing Tandems will be upgraded to UNIX SV.4. (B series OS).
620
Feature
Description
Upgrade of Tandem operating

system software to UNIX
SV.4 (B series) including
Veritas file system manager.
The OMC-R System Processor Operating System

(OS) has been upgraded to UNIX SV.4 (B series OS).
The OMC-R System Processor software applications
have been ported to run on this operating system. The
B series Operating System on the System Processor is
fully compatible with the existing Solaris configuration
on the SPARCstations.
Port to Spider X.25.
The OMC-R X.25 application has been ported from

TITN X.25 to Spider X.25 on the System Processor to
facilitate the new operating system. The main impact of
this feature is that the X.25 trouble shooting
procedures change.
Dual 64 kbit/s file upload

circuits.
Provides support for an additional upload circuit. This

gives the OMC-R two 64 kbit/s X.25 circuits for file
uploads from the BSS to the OMC-R. The impact of
this feature is that up to eight simultaneous uploads are
now supported (four uploads was the previous limit).
The extra upload circuit increases redundancy.
Upgrade of database
software to INFORMIX
On-line 5.0.
The port to the B operating system also necessitates a

move to Informix 5.0 software as INFORMIX 4.1 is not
supported on the B series OS.
System Administration
Backup menus.
The backup menu program handles on-line backups,

file locking and data consistency as well as providing
an easy to use front end for both backups and restores
across the network.
Compatibility with existing

software
Tandem S300 or 1475 OMC-R systems, running

OMC-R software release 1.4.0.0 are compatible with
the BSS software releases BSGSM 1.4.0.x and
BSGSM 1.3.0.x. Tandem S300s and 1475s can be
used in the same cellular network. However, it is
recommended that a BSS software load compatible
with the appropriate OMC-R software revision of both
OMC-Rs be run so that BSSs may be quickly
transferred between OMC-R systems if the need
arises.
Installation and
commissioning impact
A menu driven install program is available which offers

the user a choice between upgrade and clean install
options. Once the OMC-R GSM 1.4.0.0/1.4.0.x
software release has been installed, utilities are
provided which will configure the System Processor file
system and X.25 software to meet the network
requirements.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Feature
Description
OMC-R upgrade/rollback
paths
Full details of the procedures required for

upgrade/rollback of the OMC-R will be provided by
Motorola at a later date. The 1.3.x to 1.4.0.0 upgrade
path will be supported. The 1.4.0.0 to 1.3.x rollback
path will be supported.
OMC-R administration impact
The port to B Series OS changes many of the OMC-R

system administration procedures.
Operations and maintenance

impact
The port to Spider X.25 changes the X.25 maintenance

and trouble shooting procedures.

02 May 2003
68P02901W01-M
621
GSR6 (Horizon II)

Most of the new features and enhancements to the OMC-R software for 1.4.0.1 are
brought about by the introduction of a revised hardware platform and are virtually
identical to the enhancements described in release 1.4.0.0, so a brief summary is
included here followed by the specific enhancements unique to 1.4.0.1.
New OMC-R systems will use the new OMC-R System Processor, the Tandem Integrity
1475, while existing Tandems will be upgraded to UNIX SV.4. (B series OS).
The following items summarize the features of 1.4.0.0 included in release 1.4.0.1:
622
Upgrade of Tandem operating system software to UNIX SV.4 (B series) including

Veritas file system manager.
Port to Spider X.25.
Dual 64 kbit/s file upload circuits.
Upgrade of database software to INFORMIX On-line 5.0.
System Administration Backup menus.
On-line documentation.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Further features of OMC-R software release 1.4.0.1

Table 6-9 summarizes the features that are only available from release 1.4.0.1.
Feature
Description
Cell parameter propagation
Allows the operator, via the CM MIB at the OMC-R, to

change parameters in any Cell in the GSM network
and apply any of those changes to other Cells in the
network.
Neighbour propagation
Automatically aligns the settings of some attributes of

the Cell and RTF objects, with dependent attributes of
the Neighbour object (and also DRI, RTF, and Source
objects).
MicoCellular
MicroCellular is a concept in which RF coverage is

structured in more than one layer. It is generally
applied as an extension to an existing MacroCell
network in order to significantly increase its capacity
and provide better coverage in areas of high traffic
density. MicroCellular supports a mixture of optional
and standard software features. They are identified as
follows:
Independent BCCH Allocations on
BCCH/SACCH.
Handover Flow Between Cells Statistics.
Microcellular (combined micro/macrocell)
support (optional).
Enhanced event log search

and print
Enables the OMC-R operator to filter event/alarm

messages in the Event Log windows via a filter which
corresponds in functionality to the subscription
selection dialogues used in the Event and Alarm
Displays windows.

02 May 2003
68P02901W01-M
623
GSR6 (Horizon II)

Release 1.4.0.6 feature support
There were no OMC-R specific features for 1.4.0.6. The OMC-R 1.4.0.6 release
supported the following BSS features:
624
M-Cell2 GSM900 MHz band.
M-Cell2 DCS1800 MHz band.
M-Cell6 GSM900 MHz band.
M-Cell6 DCS1800 MHz band.
M-Cell GSM900 MHz band with EGSM.
RSS functionality port to carrier to carrier equipment (TCU) M-Cell.
Recovery escalation.
BSC CSFP redundancy.
Dual rate and M-Cell impact on BSUBTS.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

Release 1.4.0.7 feature support
There were no OMC-R specific features for 1.4.0.7. The OMC 1.4.0.7 release supported
the following BSS features:
S
M-Cellmicro GSM900 MHz band.
M-Cellmicro DCS1800 MHz band.

02 May 2003
68P02901W01-M
625
GSR6 (Horizon II)

The OMC-R software release supports both BSS and OMC-R features. Although there
is no OMC-R 1.4.1.1 release, the OMC-R 1.4.1.0 software release supports the following
BSS 1.4.1.1 software release features:
S
NIU-T1 support for M-Cell sites.
M-Cell2/6 MCU redundancy.
Phase/frequency lock.
sync boot.
Table 6-10 summarizes the OMC-R features of release 1.4.1.0.

Feature
Description
BSS device management via

OMC-R GUI
Enhances the functionality already provided by the

OMC-R GUI for performing network level Fault
Management and Configuration Management activities
from the OMC-R GUIs Navigation Tree.
Proxy cell
Enables cells from external GSM Networks (managed

by another Motorola OMC-R or that of another vendor)
to be modelled at the OMC-R so that when changed,
they can be updated via neighbour propagation. It is
particularly useful in microcellular networks employing
equipment from more than one vendor.
Alarm context sensitive help
Provides on-line context sensitive information on any

selected alarm when alarm handling.
Improved PM GUI
Provides a new enhanced PM GUI, selectable from the

OMC-R GUI front panel. The graphing capability has
been improved to support multiple traces.
PM activation from MAP
Provides the facility to invoke the new PM GUI with

devices already preselected from other areas of the
OMC-R GUI such as the network maps or the
Navigation Tree.
Alarm handling improvements provides several enhancements to the Event

Management functionality provided by the OMC-R. The
enhancements are as follows:
Alarm blacklisting
OIC alarm clearing
Map event history
626
Command partitioning - GUI

only
Partitions OMC-R users into different security areas.

Depending on which security area the user has access
to they will be allowed/disallowed options on the
OMC-R GUI that could be used to alter OMC-R or BSS
information.
Handover performance
statisitcs enhancement
package
Provides a package of enhanced handover

performance statistics which reduce network
optimization effort and time.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Feature
Description
15,000 TCH support
Provides support for 15,000 traffic channels in

networks where the OMC-R is deployed with a Tandem
Integrity 1475 System Processor. Existing OMC-R
systems deployed with Tandem Integrity S300 System
Processors will continue to support 10,000 traffic
channels.
Alarm paging (optional)
Can be used to automatically notify on-call personnel

of certain alarms or state changes which have been
reported to the OMC-R.
DBMS upgrade
Details the changes required for the OMC-R DBMS in

the OMC-R 1.4.1.0 system in order to support the
other 1.4.1.0 features. The main impact of the feature
is to the tables and columns of the PM database on the
OMC-R System Processor.

02 May 2003
68P02901W01-M
627
OMC-R software release GSR2
GSR6 (Horizon II)

GSR2 features
Table 6-11 summarizes the OMC-R features supported by the GSR2 (1.5.0.0) software
release.
Feature
Description
Expanded Call Trace
With the introduction of the call trace expansion feature

the BSS will expand the data collected to be compliant
with GSM standards. This includes the collection of
RR and Abis messages.
MSC Initiated IMSI & IMEI

Call Trace
Allows an MS to be tracked as it moves across the

network.
On-line Transcoder expansion Allows the transcoder capacity, associated with

equipped transcoder cards, to be increased on-line
while cellular service is maintained to subscribers
within the associated Base Station System (BSS).
628
On-line Add/Copy/Delete Cell
Supports the on-line modification to the cell

configuration of the SITEs within a BSS while cellular
service is maintained to subscribers.
Microcellular neighbour
class 7
Provides additional microCellular functionality to cater

for special handover situations in contiguous
microCells in networks with limited frequency
spectrum, where it may be impossible to avoid
deploying adjacent cells on adjacent BCCH
frequencies.
Satellite BSC//XCDR
interface (optional)
Provides the BSS software support for transmission of

the OML link via satellite. This gives the facility for the
interconnection, via satellite, of the BSC or RXCDR
with the OMC-R.
Satellite XBL support

(optional)

XBL link via satellite. This gives the facility for the
interconnection of RXCDR to BSCs deployed in areas
where land based and microwave links needed for
interconnection are unavailable or cost prohibitive.
Enhanced GSM 12.04

Statistics Compliance
Provides a package of additional OMCR key statistics

reports and additional BSS statistics which greatly
improve the compliance of the Motorola statistics to
GSM 12.04 recommendations.
Downlink RXQUAL Stat

(OMC-R bin)
Provides an enhancement to existing OMC-R support

for the downlink RxQual raw statistic reported from the
BSS. The OMC-R now supports the full bin counts
gathered by the BSS, improving on current support of
distribution (min/mean/max values). This feature
provides improved system optimization support.
Link Balance Verification

Statistics
Provides a facility at the OMC-R to identify those

carriers which have unbalanced uplink and downlink
signal strengths. This feature supports optimisation
activities.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Feature
Description
CM Service Statistics
Breakout
Provides call success statistics that more closely

match MSC statistics. Existing Motorola raw statistics
have been modified to improve the accuracy of call
success statistics.
Network Health Reports
Enhances the OMC-R performance reporting

capabilities by providing additional PM reports that
measure network performance from the subscriber
perspective.
Map filtered Event Log

Search & Print
Enables the OMC-R operator to select a node on the

map and apply a user defined filter to events
associated with the node prior to display. Multiple log
files can be then be processed by the invoked Event
Log Search & Print window.
Generic RF data export
Provides a facility at the OMC-R to easily extract RF

data. The objective of this feature is to reduce the time
taken to implement major network updates.
GPROC2 support
Allows the use of either GPROC2 or GPROC1 in

BSCs, BTSs and RXCDRs.
Q3 NMC interface
(optional)
Provides the support for NMC read/write access of the

RF parameters stored in the OMC-R MIB via the Q3
interface.
Automatic instance naming

for Q3 (optional)
Provides the OMC-R support for Automatic Instance

Naming in the CM MIB which has been part of the
OMC-R Q3 Interface features since OMCR release
1.4.0.x.
Q3 NMC interface Call Trace

transfer
Provides the OMC-R support for the dynamic transfer

of Call Trace data, which is formatted according to
GSM 12.08 recommendations, from the OMC-R to the
NMC via the Q3 Interface.
SUN Scaleable OMC-R 0

20 k TCH
Allows the network operator to install an OMC-R

platform that can be cost effectively expanded as the
cellular network grows.
Common Desktop Manager
Provides an OMC-R desktop environment, which can

be customized on a per user basis, and which reduces
window clutter and provides a graphical front end to the
UNIX file system.
System Admin GUI
Provides a GUI for routine OMC-R system

administration tasks. It gives access from the front
panel of the OMC-R desktop to the different SUN
administration tools which support Solaris 2.5.1.
Enhanced Informix Database

Maintenance
Reduces the amount of time and expertise required to

maintain the OMC-R Informix database. INFORMIX
Version 7 supports multiprocessor systems and
includes GUI tools for database performance
monitoring and administration.
Enhanced OMC-R Software

Installation & Upgrade
This feature (known as Jumpstart) reduces the amount

of time and expertise required to install or upgrade an
OMC-R. Jumpstart allows multiple Sun workstations
(such as Operator workstations) to be replicated from
another similarly configured processor.

02 May 2003
68P02901W01-M
629
GSR6 (Horizon II)
The following list summarizes the hardware features provided in the BSGSM-1.5.0.0
release with OMCR/BSS software support:
630
GPROC2, enhanced processor board.
M-Cell Remote Tune Combiner (1800 only).
Retrofit M-Cell RTC (GSM900) for BTS4/BTS6.
Remote VSWR monitor.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

GSR3 features
Table 6-12 summarizes the OMC-R features supported by the GSR3 software release.
Feature
Description
Web Access to the OMC-R
Provides access to OMC-R Performance Management

(PM) data via a standard web browser (Netscape) on a
client machine connected to the OMC-R LAN. The
browser is supported on both Sun Solaris and
Windows NT (Intel-based) platforms to access OMC-R
PM data.
BSS Device Management via

OMC-R GUI
Enhances the BSS device and function management

capabilities from the OMC-R GUI.
Metrica Statistics
Introduces new statistics to support the BSS. Metrica

is a tool that gathers statistics from various types of
OMC-Rs and compares and consolidates those
statistics.

02 May 2003
68P02901W01-M
631
GSR6 (Horizon II)

GSR4 features
Table 6-13 summarizes the OMC-R features supported by software release GSR4.
Feature
632
Description
Network geographical access

control
NA
Transfer Motorola text detab

format to PlaNET
Converts Motorola text detab format files into a format

acceptable to PlaNET, which is necessary to transfer
data to PlaNET.
Task-based Routine
Operations and Maintenance
Provides a new OMC-R user interface that integrates

the tools necessary for routine maintenance of the
Motorola radio infrastructure equipment.
Operator specific regions
NA
Network optimization: cell

optimized GUI
NA
Scaleable OMC-R
The System Processor and the MIB Processor have

been consolidated into a single SUN E3500/E3000
server. This provides further reductions in cost of
ownership and improved system administration,
performance, and reliability.
Process restartability
Allows a subset of system processor processes

(Restartable processes) to restart automatically, if the
processes fail, without the need for a full OMC-R
stop/start. Other system processes (Non-restartable
vital processes) will cause an automatic OMC-R
stop/start on failure.
New Millennium
Addresses all aspects of the Motorola system; OMC-R,

BSS, and the BTS and BSC hardware. It concerns
itself with internal clock operation and the use of the
date in various parts of the product, for example within
Event and Alarm reports.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

GSR4.1 features
Table 6-14 summarizes the OMC-R features supported by software release GSR4.1.
Feature
Description
GPRS OMC-R (PCU)
Provides a fully integrated solution within the existing

OMC-R architecture. It consists of support for the PCU
as part of the BSS.
OMC-R capacity increased to

30k TCH and 120 NE
Increases the OMC-R capacity from the previous rating

of 20 kTCH and 64 network elements, to 30 kTCH and
120 network elements without requiring hardware
upgrades to the E3000/E3500. Also increases the
network traffic and NE count of the OMC-R by
extending the object model and increasing capacity of
the OMC-R databases and data storage areas. This
means that the increased size network can be
managed without altering the data storage
arrangements.

02 May 2003
68P02901W01-M
633
GSR6 (Horizon II)

GSR5 features
Description
BTS concentration
Propagation after audit
EAS relay MMI output control for InCell, M-Cell and Horizon
Intelligent congestion relief
Adaptive handovers
Support of BCCH and SDCCH for EGSM
Coincident multiband boundaries
Reporting the results of alarms recovery action
Flexible neighbour processing
Dynamic call trace flow control
Proxy cell autocreation
Proxy cell import/export
Completion of OMC-R support for Horizonmacro
Q3 support
DRI and combiner operability improvement
NHA support maximum size GSM OMC-R
Integration of NHA with OMC-R EM
Bay level cal default data
Cell parameter import/export
Applix 4.41 upgrade
System upgrade
Enhanced SDCCH to TCH assignment
Changing NE ID of Assoc_BSSs or Assoc_RXDRs
OMC-R GUI usability
Datagen support
Increased OMC-R neighbour stats
OMC-R GUI support for PCU device object
Network expansion batch capability
Increased capacity OMC-R
Increasing maximum number of trunks per BSC
Expansion/de-expansion
634

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Description
Vanguard software upgrade support
Support for Vanguard 6455 router
Removal of the clear stats command
PCU alarms detected by HSC
BTS concentration
The BTS concentration feature provides an alternative mechanism for allocating
terrestrial backhaul for radio resources between the BSC and the BTS. Previous to the
introduction of this feature, these resources were allocated when RTFs were equipped.
This feature preserves the existing mechanism, but allows the operator the choice, on a
per BTS site basis, of whether to use the existing mechanism, or the new dynamic
allocation. This feature is optional.

This feature, previously called Dynamic Downlink Power Control Steps, provides
optimized uplink and downlink power control. This is achieved by:
S
Adding flexibility in defining power steps.
Modifying the range of power steps (by allowing power step sizes to be changed
dynamically).
Performing downlink oscillation prevention.
These power control modifications cause the mobile and BSS to respond more effectively
to changing power level and quality conditions. This minimizes power output both for the
MS and the BSS, as well as reducing interference.
Propagation after audit

This feature will provide data consistency between different BSSs with the main focus is
on synchronizing neighbour information across BSSs.
If the CELL attributes change as a result of an audit, a Neighbour Propagation is initiated
to synchronize the neighbour information across BSSs.
EAS relay MMI control for InCell, M-Cell and Horizon

This external alarm system (EAS) relay configuration feature gives the operator the
capability to set a default relay state for the PIX relays at either an InCell site, an M-Cell
site or an Horizon site and display the relay states from the OMC-R GUI.
Intelligent congestion relief

With the implementation of the Intelligent Congestion Relief feature, the existing
congestion relief procedures can benefit from the following advantages:
S
Faster congestion relief (non-ideal targets will not be tried).
Reduced signalling (fewer handover attempts).
Less congestion and fewer congestion relief triggers (handovers that can lead to
congestion are not accepted).
Efficient congestion control in the preferred band of a multiband network.
Supported by OMC-R GUI.

02 May 2003
68P02901W01-M
635
GSR6 (Horizon II)
Adaptive handover
This feature will allow support of adaptive handovers and optimize type 3 and type 5
power budget handovers from the OMC-R.
Support of BCCH and SDCCH for EGSM

This feature allows the configuration of BCCH carriers and the placement of SDCCH in
the EGSM band. This impacts the operation of non-EGSM mobiles in that they may not
have service, since they are not able to access the BCCH frequency and SDCCH
channels in the EGSM band.
The support of the BCCH frequency and SDCCH channels in the EGSM band is based
on an operator defined database parameter.
The operator also has the capability to configure a standalone EGSM band cell by
selecting EGSM band frequencies.
With this feature, the operator is allowed to implement a multi-band/dual-band network
with EGSM as one of the supported frequency bands. It is possible for the operator to
select the EGSM band as the preferred band over the DCS1800 or GSM900 band.
In addition, this feature allows hopping systems to support the EGSM frequency band.
In a dual band system (EGSM and DCS1800), hopping is only supported within the
bands but not between the bands.
Coincident multiband boundaries

This feature allows operators to install new radios in a different frequency band and
easily configure multiple frequencies. The installation of new radios allow an operator to
have Multiband capabilities. The major hurdle to this type of upgrade is that the operator
has already spent significant time and money optimizing the existing infrastructure.
With the addition of a second frequency band, with different propagation characteristics,
the operator needs to increase efforts to optimize the infrastructure. This is a major
stumbling block to many operators who want the capacity increase but are reluctant to
configure and optimize two frequency bands.
To circumvent this multiple frequency band issue, the new secondary frequency band
compliments the existing infrastructure. To do this, the software allows a cell with a new
frequency band to be configured with the same cell boundaries established by the
original frequency band. Also, it allows the new frequency band cells to use the
handover measurement reports based on the cells in the original frequency band.
This can be done by using mobile reported measurement reports from the primary
frequency band while a call is established on the secondary frequency band. This
enables the mobile to be handled as if it were on the primary frequency band, whilst not
taking any primary frequency band resources.
This feature is designed to compliment the Multiband Inter-Cell Handover feature and its
use is dependent upon Multiband being enabled.
Reporting the results of alarms recovery action

The Alarms Consolidation feature provides the operator the ability to view all state
changes and secondary alarms associated with a primary alarm in a hands free manner,
that is, without the need to search through alarm and event logs. The Reporting the
Results of Alarm Recovery Action feature, enhances this hands free operation for the
end user by including information describing the result of an alarm recovery action.
636

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Flexible neighbour cell processing

This feature will modify the criteria for handover between neighbours. It has four main
elements that can be activated independent of each other.
Dynamic trace call flow control

The Dynamic Call Trace Flow Control feature significantly enhances the existing Call
Trace capabilities available in the BSS and is now supported by the OMC-R. The main
uses for Call Trace in GSM are fault management, optimization and security.
A network can be optimized by analyzing call trace data that is collected from a call made
by a designated MS as it travels through the network. Call Trace can be used to locate
stolen or defective GSM equipment. Network Operators can also use this feature to
determine why calls are being dropped due to RF Loss.
Depending on the amount of traffic between the BSS and OMC-R, the call trace flow
control techniques include:
S
Modifications of active call trace criteria.
Pre-emption of existing traces.
Controlling the number of new trace activations.
The operator may also choose whether or not MSC initiated call traces are exempt to the
call trace flow control mechanism.
NOTE
This feature consists of the operator enabled triggering of flow

control and the associated OMC-R GUI configuration support.
The intent of this feature is to address the outstanding issues surrounding the current
Call Trace functionality in the BSS, covering call trace usability.
Proxy cell autocreation

When the NeighbourGsmCellId is entered and the Neighbour has been initialized, if the
NeighbourGsmCellId does not exist either as a Cell or a Proxy Cell in the OMC-R MIB,
the feature informs the user that the Proxy Cell has been created using the parameters
of the neighbour just created.
During a BSS-OMC-R audit, the NeighbourGsmCellIds are checked against the
complete list of Cells and Proxy Cells existing in the MIB. If the NeighbourGsmCellId
does not exist a Proxy Cell will be autocreated using the NeighbourGsmCellId.

02 May 2003
68P02901W01-M
637
GSR6 (Horizon II)
Proxy cell import/export

The Proxy Cell Synchronisation feature ensures that Neighbour OMC-Rs are consistent
across all OMC-Rs managing a network by ensuring that the Proxy Cells in an OMC-R
are consistent with the original CELL that exists in another OMC.
The OMCRsupplies the user with a program pcellExport that exports Neighbour
related parameters of all CELLs within the OMCRthat have Neighbour relationships with
CELLs in other OMCs, into an ASCII file.
This ASCII file is then transferred by the user to all other OMCs and the pcellImport run
on it.
The import program:
S
Creates Proxy Cells if there are CELLs that contain Neighbours corresponding to
entries in the file and no Proxy Cell exists. The parameters of the Proxy Cell are
derived from the file.
Updates the Proxy Cells if parameters have changed.
Create/Update of Proxy Cells, results in all related Neighbours getting updated. Thus
CELL-Neighbour relationships across all OMCs are synchronized via the Proxy Cell
Export/Import mechanism.
The OMCRalso provides a single script pcellSync that synchronizes all OMCs in one
shot without any manual intervention.
This program in turn runs export and import on all OMCs connected in the network.
Detailed feature information was not available at the time of publication. Further
information will be included in the next revision of this manual.
Completion of OMCRsupport for Horizonmacro

This feature provides the completion of OMC-R support for the Horizonmacro.
Q3 support
The purpose of this feature is to port the GSR4 mediation device to GSR5 to enable
continued operation of Q3 in the field.
Motorolas Q3 OMC-R Mediation device support for GSR5 includes the following:
S
Interoperability testing of Q3 OMC-R interface functionality with GSR5 and BSS.
Support GPRS (PCU) specific alarms and events (GSR5).
Recognizing Motorolas leadership in Q3, further functional enhancements for our

Q3 OMC-R implementation is driven and agreed by the key Q3 customers and any
new generic requirement to enhance our implementation.
DRI and combiner operability improvement

This enhancement improves the operability of the Digital Radio Interface (DRI) and
Combiner devices by increasing the flexibility with which these devices can be equipped,
and unequipped.
This feature is achieved by specifying the DRIs role in system combining during the equip
of the DRI.
638

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
NHA support maximum size GSM OMC-R

This feature will enable Expert Adviser (EA) Network Health Analyst (NHA) to support the
maximum size GSM OMC-R (i.e. 45kTCH)
Integration of NHA with OMC-R EM

This feature allows the OMC-R operators to view Network Health Analyst (NHA)
problems through the standard OMC-R alarm windows.
The NHA sends the problems in the correct format to the OMC-R as alarms. The
OMC-R Event Manager (EM) is able to accept the messages and deal with them as
standard alarms and passes them to the GUI for viewing and handling in the standard
manner.
There is a new event type on the OMC-R for the NHA to facilitate easy filtering.
Detailed feature information was not available at the time of publication. Further
information will be included in the next revision of this manual.
Bay level cal default data

This feature permits operators to remotely insert default radio values.
A site visit is required for accurate calibration of radios.
NOTE
Cell parameter import/export

Cell parameter import/export enables the following:
S
Export of RF data from the OMC-R network into an RF planning environment.
Import of RF data from an RF planning environment into the OMC-R network.

NOTE
Current RF Planning data can be exported from the live OMC-R.
The export function generates two ASCII tab delimited files for cell and neighbour
parameters within the network.
The parameters that are exported or imported may be defined by the user. The cell file
contains a list of cells, their bsics, frequencies and other information. The neighbour file
contains a list of neighbours for each cell. The file format is published and is in ASCII
format. RF planning tools, for example, NetPlan can import these files and use it to carry
out a network frequency replan.
The output of the frequency replan can be imported into the OMC-R, and then used to
update the relevant network elements, new base station id codes (bsics) and frequencies
will be propagated to neighbour relations.
RF Planning data import and export may be carried out from the Navigation form of the
OMC-R or from the command line.
Applix 4.41 upgrade

This feature provides an upgrade of Applix from 4.3 to 4.41, so that PRs dependent on
this upgrade can be fixed. Some of these PRs are customer commitments. Applix 4.41
depends on having an Informix 7.2 engine.
02 May 2003
68P02901W01-M
639
GSR6 (Horizon II)
System upgrade
NOTE
This feature maintains compatibility with BSS GSR4 and GSR4.1

releases. GSR4.1 was a limited release for GPRS customers
only; GSR5 contains all GSR4.1 features. It is not possible to
directly upgrade the OMCRfrom GSR3 release to GSR5
release due to the Y2K compliant release being GSR4.
The capability implies the following high level requirements:

S
OMC GSR5 release can be directly upgraded from GSR4 and GSR4.1 releases.
BSS GSR5 release can be directly upgraded from GSR4 and GSR4.1 release.
OMC GSR5 release is capable of managing a network of BSSs running GSR4,

GSR4.1 and GSR5 releases simultaneously.
OMC GSR5 release can be directly downgraded to GSR4 and GSR4.1 for
roll-back.
BSS GSR5 release can be directly downgraded to GSR4 and GSR4.1 for
roll-back.
Enhanced SDCCH to TCH assignment

An enhancement has been made to increase the success rate of assignment to a
preferred band cell, that is, going from an SDCCH in a non-preferred band cell directly to
a TCH in a preferred band cell.
Changing NE ID of Assoc_BSSs or Assoc_RXCDRs

This feature enables a recovery mechanism for Associated Transcoder/ Associated BSS
(AXCDR)/(ABSS) configuration mistakes.
With the new GSR5 software release, the Enhanced XBL (EXBL) feature introduces the
AXCDR and ABSS devices.
The Dynamic Allocation RXCDR to BSC Circuits (DARBC) feature expands upon these
new devices. During initial configuration of these devices, it is possible that the operator
will make a configuration mistake which, if not caught early, may cause the operator to
enter upwards of a 100 commands in order to correct it. This feature enables an easy
mechanism to correct an early configuration mistake. Without this feature, the total
number of commands could be (21 + 10 + 10) x 2 = 82, to make a simple, device
identification number, change.
With this feature, an easy mechanism is provided to correct a mistake. The OMC-R is
able to propagate the BSS or RXCDR identifier (network_entity_id) changes to its
associated BSS or RXCDR devices and its contained devices (XBLs, CICs and
Conn_Links) by initiating a single operation from the GUI instead of <82> or more BSS
MMI commands. The GUI provides a simple screen to rectify these configuration
mistakes.
For example, the operator can select the AXCDR device whose network identifier needs
to be changed and initiate the Change Assoc NE ID operation. The operator should note
that a single invocation of the Change Assoc NE ID operation changes the identifier for
only one AXCDR (or ABSS) in a BSS (or RXCDR) database. If the operator changes the
identifier of an NE, the identifier must be changed in the NEs database. The Change
Assoc NE ID operation can be invoked to change the associated device id in each
database which includes the NE as an associated device.
Consider a BSS-1 and BSS-2 which are connected to RXCDR-3. The AXCDR-3 is
equipped in the databases of both BSS-1 and BSS-2. To change the NE id of the
RXCDR from 3 to 5, the operator must change the id of the RXCDR in the RXCDR
database and can then invoke the Change Assoc NE ID operation on the AXCDR-3 at
BSS-1 and BSS-2 to set the new AXCDR identifier to 5.
640

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
OMC-R GUI usability

OMC-R GUI usability has been enhanced; the new procedures can be contained within
the following five categories:
S
Handling AttributeValueChange Notifications from the BSS.
Better Status Bar Management on GUI windows.
AutoCreation/deletion of CommsLinks during Conn_Link creation/deletion.
Support for Default BSS Naming on Detailed Views.
Enhancements to the Contained Devices Form.
Datagen support
The purpose of this feature is to support all parameter changes introduced in this
release.
This is a standard activity for Datagen in each release.
Increased OMC-R neighbour stats

This feature provides an increase in the volume of neighbour statistics data that can be
stored at the OMC-R, that is, the number of cells with neighbour statistics enabled.
OMC-R GUI support for PCU device object

GPRS is a service supported under GSR4.1 and GSR5 which allows for the
packet-mode transmission of data within a GSM network. Using GPRS, a MS can send
and receive data in an end-to-end packet transfer. This enables a more cost-effective
and efficient use of network resources for data transfer.
Network expansion batch capability

The purpose of this feature is to support large scale network expansion in an on-line or
off-line environment providing a batch capability to allow for the grouping of multiple
expansion activities.
This is achieved from the Navigation Form by being able to:
S
Create a new BTS SITE by copying and pasting an existing BTS into a BSS
configuration.
Reparent a BTS within the same Intra- BSS or a different Inter-BSS.
Delete a BTS with its associated hardware devices and software functions in a
single operation.
Network Expansion can be performed either on the Off-Line MIB or OMC-R platform.
Fault management functions

In the case of on-line operations, the network expansion application performs mandatory
Fault Management procedures. If deleting or reparenting a Site, then the SIte is
gracefully shutdown, for example, DRIs are shutdown and RSLs are locked.
02 May 2003
68P02901W01-M
641
GSR6 (Horizon II)
Performance management functions

For both platforms the Network Expansion application maintains Performance
Management data on devices. Specifically during a copy SITE operation, the application
will copy the Performance Management configuration (enables statistics and thresholds
etc.), from the original SITE to the new SITE. Similarly during a reparent SITE operation
the application will maintain the Performance Management configuration.
Maintenance of Performance Management is limited to those statistics configured within
the containment of a BTS SITE. Statistics configured within a BTS SITE (CELL or
Carrier level) for example, RF LOSSES TCH or CALL VOLUME DRI, will be manipulated
during Network Expansion. Statistics outside the BTS SITE at the BSS level for
example, CPU_USAGE MAX will not be manipulated. These SITEs will inherit the
configurations from the parent BSS for inter-BSS operations.
Increased capacity OMC-R

This feature expands the capacity of the OMC-R to cater for a higher number of receive
transmit functions (RTFs) on a single platform. The capacity is 6000 RTF (45k TCH).
To cater for the handling of a larger network, a number of usability enhancements are
included, mostly notably the alarm deferral and split-screen alarm window option.
Increasing maximum number of trunks per BSC

This feature increases the maximum number of trunks (CICs) supported at the BSC from
the previous database limit of 1920 to a new limit of 2400. This is required to support
large capacity BSCs supporting up to 384 carriers using an aggressive Dense Urban call
model (as used in China). It was determined that a minimum of 2300 trunks are
required for the Dense Urban call model to support 384 carriers and the remaining trunks
would be used for redundancy.
NOTE
These new CICs must also be known to the MSC.
This feature allows the operator to provision larger capacity BSCs in networks supporting
heavy call traffic, provided that other limitations specified in the Planning Guide have not
already been reached.
The main impacts to the subsystems in the Base Station System (BSS) for increasing
the BSC trunk limitation from 1920 to 2400 trunks are in ensuring data consistency
throughout the system. For example, increasing the number of CICs will require
increasing the number of nails, so connections can be nailed through at the RXCDR.
NOTE
A nailed control link is a fixed 64 kbit/s link such as a MTL or

OML which passes through the RXCDR without the RXCDR
having any impact on that link, it is simply being used as a
medium to get the control link to the destination. This medium is
called a nail.
In order to achieve 384 carriers for the BSC on the Dense Urban Call model (the primary
motivation for this feature), the following assumptions regarding the BSC are made:
642
Support of two Message Transfer Links (MTLs) per Link Control Function (LCF) at
40% MTL link utilization.
Support of: 25 LCFs.
GPROC2 processing is approximately four times that of a GPROC.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Increasing the number of trunks limit will not provide value for
Dense Urban environments unless these assumptions hold true.
NOTE
Expansion/de-expansion
This feature enables the capacity of the OMC-R to cater for a higher number of TCHs.
The lowest level is a 5 k TCH system which can be expanded to a 10 k or 30 k TCH
system. The 30 k TCH can be expanded to 45 k TCH system. In ascending order there
are four available TCH sizes:
S
5 k TCH (low end).
10 k TCH (mid end).
30 k TCH (mid end).
45 k TCH (high end).
Vanguard software upgrade support

Motorolas Information Systems Group, Network Systems Division (NSD), in its
commitment to provide the highest value wide area multimedia access solutions, will
provide upgrade support for all routers. Software in the field will be upgraded to the
latest Vanguard router software.
Support for Vanguard 6455 router

Motorolas Information Systems Group , Network Systems Division (NSD), in its
commitment to provide the highest value wide area multimedia access solutions
introduces the Vanguard 6455 router (software and hardware) . The Vanguard 6400
Series from Motorola provides multiservice edge networking solutions for multimedia, IP
and serial traffic simultaneously over the WAN.
Removal of the clear stats command

The clear_stats command is no longer supported in GSR5.
PCU alarms detected by HSC

Provides software functionality to enable detection of PSU failures on a PCU cage.
When a failure is detected, an alarm is raised, and the operator notified. The alarm status
is also reflected through the LED indicators (when activated) on the PCU alarm panel
board.

02 May 2003
68P02901W01-M
643
GSR6 (Horizon II)

GSR5.1 features
Table 6-16 summarizes the OMC-R features supported by software release GSR5.1.
Description
Web MMI
GPROC fast reset
Unequip TCU/CTU Cabinet
WebMMI
The Web MMI is a new feature which provides a remote service to any user who has
access to the network that a PCU resides on. Through the intranet, and the availability
of the PCU cage and its ethernet capability, the BSS can be monitored and maintained.
The functionality that is offered consists only of the functionality
that the Operations and Maintenance (O&M) Man Machine
Interface (MMI) and the Executive Monitor (EMON) provide for a
single BSS, as opposed to the functionality that the OMC might
provide as a whole.
NOTE

The OMC-R to BSS interface will be updated to include the new database parameters
allow_32k_trau as well as the new and modified statistics.
The allow_32k_trau parameter is restricted by the GPRS restrictable feature and the 32k
TRAU CS3/CS4 restrictable feature and can only be used if the GPRS and 32k TRAU
CS3/CS4 features are unrestricted. Additionally, the dynamic allocation of terrestrial
resources feature must be disabled for any sites using GPRS. This parameter will
prevent GPRS usage on RTFs that are subequipped in the database. This parameter
can only be enabled if max_gprs_pdch is set to a nonzero value. Additionally, if
allow_32k_trau parameter is enabled, the value of max_gprs_pdch can not be set to zero
without first disabling allow_32k_trau. Verifications need to be performed to ensure that
there are enough terrestrial resources available when max_gprs_pdch is increased and
allow_32k_trau is enabled.
The allow_32k_trau parameter can be modified inside or outside SYSGEN mode.
GPROC fast reset

The OMC-R supports fast reset for all types of sites except:
644
PCU sites from Navig
PCU sites from SITE
PCU sites from Contaform.
PCU sites from Map

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Unequip of TCU/CTU cabinets

This feature enables support for the unequippage of extension cabinets of types TCU_2,
TCU_6 and Horizonmacro_ext at M-Cell and Horizonmacro sites without having to
unequip the site. This action can be done provided that the cabinet is locked and there
are no DRIs or EASs equipped to the cabinet. All other cabinet types are not supported
by this feature.

02 May 2003
68P02901W01-M
645
GSR6 (Horizon II)

GSR6 features
Description
{2636} Geographic command partitioning and region support
{3646} Enhanced circuit error rate monitor
{4083} OMC-R GUI usability for large network support
{4183} Enable cyclic neighbour statistics
{4237} {4177} Online network expansion - phase 3
{4301} Cell Xchange
646

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Geographic command partitioning and region support

Feature overview
The feature enables operators to set up geographical regions, populate these regions
with network elements (Base Station System (BSS) and Remote Transcoder (RXCDR))
and assign read and/or write access for these regions to individual users.
Feature description
As the networks grow in size, the amount of information available to the operator is
increased. The feature provides a method of reducing the amount of data visible to the
operator by allowing them to subscribe to a defined set of network elements. This
provides each Operations and Maintenance Centre-Radio (OMC-R) operator with a
sub-network for them to manage.
The feature provides a mechanism for defining geographic regions. Network elements
(BSS and RXCDR) can be added to these regions to represent sub-networks . Once the
regions are set up, the system administrator will have the ability to create, modify and
remove access controls to particular regions for each operator.
All operator specific security related information will be stored in that operators security
file. (This allows the OMC-R administrator to limit the access of each OMC-R operator to
certain geographical areas based upon the NEs to which the operator is given access).
The security administrator is able to:
S
Create an operations access control group.
Delete an operations access control group.
Modify an operations access control groups properties.
Copy a operations access control groups properties.
Add operations to an operations access control group.
Delete operations from an operations access control group.
Assign an operation to one or more operations access control groups.
Copy a user profile data record.
Help is provided for the command partitioning feature.
Benefits
This feature permits network operators to create geographical domains over which
specific operators have control. The restricted user access provides a level of security to
ensure that only authorised users can access certain geographical areas. The ability to
manage multiple networks on one OMC-R reduces the cost of ownership of the
networks.
Applications
This feature will find application in those networks where control of the network is
exercised in geographic regions.
Compatibility/dependencies/network elements affected

Geographic command partitioning and region support is supported by the GSR6 version
of the OMC-R. No changes are required to the network elements.
02 May 2003
68P02901W01-M
647
GSR6 (Horizon II)
Enhanced circuit error rate monitor

Feature overview
The original Circuit Error Rate Monitor (CERM) optional feature provides a means for
identifying when discontinuity is detected on a circuit. The customer can:
S
Reduce cost of ownership.
Reduce downtime of devices.
Enhance system operability.
Enhance quality of service.
A circuit is considered to be the path along which a connection is made, from the entry
point in the BSS (for example, a radio at the BTS) to the exit point in the BSS (for
example, the MMS timeslot that connects to the MSC or PCU).
The CERM is used to monitor the continuity and sanity of hardware processing elements
in a circuit, on a per call basis. Whenever a discontinuity is detected for a circuit during a
call, error counts are updated for the points monitored for the call. When the error count
at a particular monitoring point reaches or exceeds an operator specified threshold, an
alarm is generated. The alarm contains information identifying the monitored path in
which the error is detected, thus allowing the operator to identify potentially faulty
devices.
Feature description
The CERM feature is enhanced enabling the monitoring at various points in a GSM
network circuit, thus improving the ability of an operator to narrow down where a faulty
device may be located. Although having these monitoring points in the circuit path
narrows down the list of potentially faulty devices, it does not conform that a device is
faulty. It is still up to the operator to determine which device is faulty.
The following points in a network can be monitored on a per timeslot basis:
S
Circuit Identity Code (CIC) on a link between the RXCDR or BSC and the MSC.
ATER Channel Identifier (ACI) groups on a link between the RXCDR and the BSC.
GPRS Circuit Identifier (GCI) group on a link between the BSC and the PCU.
Radio Channel Identifier (RCI) in the radio hardware.
Path Identity Code (PIC) on a link between the BSC and a BTS.
The PIC is a special case because it is measured on a from-BSC-to-site basis. So, for
example, with a path leading from a BSC to two daisy chained BTSs, the PIC for the
second BTS encompasses the path through the first BTS to the BSC.
648

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
OMC-R GUI usability for large network support

Feature overview
This feature aims to provide an enhanced Graphical User Interface (GUI) and tools to
enable the operator to help operate and maintain large networks with relative ease. The
main enhancements are described below:
S
Neighbour Reciprocity: Previously, a significant number of CELLs in a network

exhibit neighbour reciprocity. This means that if CELL A is a neighbour of CELL B,
then CELL B must be a neighbour of CELL A (two way relationships).
Enhancements to the OMC-R to view reciprocal relations between CELLs in the
OMC-R, add or drop reciprocal neighbours enable operators manage large
networks with greater ease.
The source neighbour view is also now enhanced to provide the user with
information about Neighbour reciprocity.
Auto Reciprocation of Neighbours: Since most CELLs in a real network exhibit

Neighbour reciprocity, the user now has the option of auto creating the reciprocal
Neighbour when a neighbour is created.
Enhanced Find: The find form option is enhanced to support search for
parameters. The user is now able to locate the container of the given parameter
name.
Feature description
The OMC-R now supports the following enhancements to the GUI and Configuration
Management Information Base (CM MIB):
Neighbour reciprocity and enhancement source neighbour view

The OMC-R GUI is enhanced to provide a menu option on the navigation tree in order to
let the operator view all sources (CELLs in which mobile phones are located) and
neighbours for CELLs in the network being managed by the OMC-R.
The new GUI screen is an enhanced version of the source neighbour view, and enables
the user to add or remove neighbours and sources and thereby manage reciprocal
relations.
The OMC-R also enables fully automated creation of reciprocal neighbours by means of
an environment variable, since most of the neighbours in a practical network are two way
neighbours.
The ProxyCell synchronization processes are extended to synchronize sources along
with neighbours between OMC-Rs so that the correct cross OMC-R reciprocal relations
are presented to the user.
Autocreation of reciprocal neighbour during neighbour creation

The OMC-R now provides the user the ability to reciprocate neighbours if they wish to
during the equippage of the neighbours. The user is also be able to specify, on a per
neighbour basis, if it can be reciprocated or not.
Enhanced find
The OMC-R GUI is enhanced to let user find the container of the given parameter. The
find form option also supports the task of find attributes (parameters) in addition to the
find devices option.
02 May 2003
68P02901W01-M
649
GSR6 (Horizon II)
Enable cyclic neighbour statistics

Feature overview
The BSS and OMC-R were restricted in their ability to provide full neighbour statistic
coverage to the network operators. These limitations were based on hardware and
processing limitations.
This feature introduces the ability to automatically traverse the OMC-R network on a per
BSS basis and enable the neighbour statistics in rotation.
The feature also provides the operator with the ability to enable statistics based on
analysis carried out by the Network Health Analyst (NHA) and enables the operator to
provide a list of their own favourite cells for enabling.
Online network expansion - phase 3

Feature overview
The network expansion - phase 3 feature extends the functional capabilities of the
network expansion - phase 2 feature delivered in GSR5.
Feature description
The Online Network Expansion - Phase 3 feature provides the following
enhancements:
Daisy chain support

The Network Expansion Copy-SITE, Delete-SITE and Reparent-SITE operations
are enhanced to facilitate the insertion or deletion of a Base Transceiver Station
(BTS) within a static daisy chain Base Station System (BSS) configuration.
The path dependencies are handled by a stand-alone functionality, referred to as
the Path Configure.
It is also be possible to invoke the Path Configure from the Navigation Tree
Configuration Management menu , for any given site that is not within a
DYnamic NETwork (DYNET) device.
The Path Configure enables the operator to temporarily un-equip devices, to
delete paths, to create new paths and to re-equip the devices with their original
settings. Network Expansion invokes the Path Configure when it determines that
the operation selected by the user involves a site within a daisy chain.
650

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Scheduler functionality for CellChange

The network expansion scheduler is expanded to include the possibility of
scheduling a CellXChange operation and both a Cell-X-Import operation and
Cell-X-Export operation.
Benefits
The main benefit of this phase of network expansion is to improve the feature
applicability by introducing daisy chain support. It also extends the scheduler
functionality by adding support for CellXChange.
Cell Xchange
Feature overview
This feature is an extension of the RF Planning Interface feature (RDB 3416) and of the
Cell Parameter Import Export Feature (RDB 3780). It now allows the user to export and
import SITE/RTF/DRI parameters for direct amendment, as previously for CELL
parameters. The specific parameters to export/import are configurable by the user. The
name of the configuration file is :
/usr/omc/config/global/RF.CNFG
This feature is available both on the OffLine Management Information Base (MIB) and
also on the Operations and Maintenance Centre-Radio (OMC-R) providing a mechanism
to make large scale changes on-line.

02 May 2003
68P02901W01-M
651
OMC-R software release GSR6 (Horizon II)
GSR6 (Horizon II)

GSR6 (Horizon II) features
Table 6-18 summarizes the OMC-R features supported by software release GSR6
(Horizon II) .
Table 6-18 Release GSR6 (Horizon II) features
Description
{4475} Support for new UNIX server
652

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Support for new UNIX server

{4475}
Feature overview
From GSR6 (Horizon II) Volume Deployment onwards, the existing OMC-R platform will
be replaced by a new OMC platform.
Two new server types are introduced:
S
Netra 20
SunFire 4800
The Netra 20 is intended for smaller configurations of up to 45000 TCH, whilst the
SunFire 4800 platform is used for larger configurations of up to 60000 TCH.
Netra 20 OMC-R platform

This is used in configurations of up to 45000 TCH. The platform comprises a Netra 20
server with two 900 Mhz CPUs, 2 Gb memory, two I/O controllers and two HSI/P cards.
An external disk array of twelve 36 Gb disks is attached.
Figure 6-1 GSM OMC-R hardware configuration for up to 45k TCH

NETRA SERVER
2 x 900 MHz CPU

2 Gb RAM
DVD & DAT
SCSI controller + ethernet

HSI
SCSI controller + ethernet
HSI
External disk array

02 May 2003
68P02901W01-M
653
GSR6 (Horizon II)
SunFire 4800 OMC-R platform

This platform comprises a SunFire 4800 server configured as a single domain. There are
four 900 MHz processors on two CPU boards, providing a total memory of 4 Gb. The
system also comprises dual differential SCSI interfaces, dual HSI cards and quad fast
Ethernet cards for I/O. An external disk array of twelve 36 Gb disks is attached.
Figure 6-2 GSM OMC-R hardware configuration for up to 60k TCH

SunFire 4800 SERVER
4 x 900 MHz CPU

4 Gb RAM
DVD & DAT
QFE ethernet
QFE ethernet
HSI
HSI
SCSI controller
SCSI controller
PCI cage
PCI cage
External disk array
OMC-R GUI server

The OMC-R GUI platform comprises a Sunblade 150 server with 650 MHz CPU, 1 GB
RAM and two internal disks.
654

68P02901W01-M
02 May 2003
Chapter 7
Glossary of technical terms

02 May 2003
68P02901W01-M
71
GSR6 (Horizon II)
72

68P02901W01-M
02 May 2003
GSR6 (Horizon II)

This Glossary of technical terms contains standard Motorola acronyms, abbreviations
and numbers used throughout the documentation set.
A Interface - AUTO
A Interface
Interface between MSC and BSS. The interface is based on

the use of one or more E1/T1 digital links. The channels on
these links can be used for traffic or signalling.
A3
Authentication algorithm that produces SRES, using RAND

and Ki.
A38
A single algorithm performing the function of A3 and A8.
A5
Stream cipher algorithm, residing on an MS, that produces

ciphertext out of plaintext, using Kc.
A8
Ciphering key generating algorithm that produces Kc using

RAND and Ki.
AB
See Access Burst.
Abis interface
Interface between a remote BSC and BTS. Motorola offers a

GSM standard and a unique Motorola Abis interface. The
Motorola interface reduces the amount of message traffic and
thus the number of 2 Mbit/s lines required between BSC and
BTS.
ABR
Answer Bid Ratio. The ABR is the ratio of successful calls to

total number of calls. As a measure of effective calls, it
reflects the performance of the total network
ac-dc PSM
AC-DC Power Supply module.
ac
Alternating Current. In electricity, AC occurs when charge

carriers in a conductor or semiconductor periodically reverse
their direction of movement. Household utility current in most
countries is AC with a frequency of either 50 or 60 hertz
(complete cycles per second). The RF current in antennas
and transmission lines is another example of AC. An AC
waveform can be sinusoidal, square, or sawtooth-shaped.
Some AC waveforms are irregular or complicated. Square or
sawtooth waves are produced by certain types of electronic
oscillators, and by a low-end UPS when it is operating from
its battery.
AC
Access Class (C0 to C15).
AC
Application Context.
ACC
Automatic Congestion Control. A method by which congested

switches automatically communicate their congestion level to
other switches.
Access Burst
The Access Burst is used by the MS to access the BTS. It

carries RACH uplink from the MS to the BTS to start a call.
ACCH
Associated Control CHannel. Control information associated

with TCH or DCCH.
ACK, Ack
ACKnowledgement.

02 May 2003
68P02901W01-M
73
74
GSR6 (Horizon II)
ACM
Accumulated Call meter. The ACM is a function contained

within the SIM. It accumulates the total units (in the home
currency) for both the current call and all preceding calls. For
security reasons, the SIM only allows the value of the ACM to
be incremented, not decremented. Resetting of the ACM is
only possible after entering PIN2.
ACM
Address Complete Message.
ACPIM
AC Power Interface Module. Used in M-Cell6 indoor ac BTS

equipment.
AC PSM
AC Power Supply Module. Used in M-Cell6 BTS equipment.
ACSE
Association Control Service Element. The ACSE is one of the

three Application Service Elements (ASE) which reside in the
application layer of the OSI protocol and act as an interface to
the lower layer protocols. It is used by applications to create a
title for identification. See also ASI and ROSE.
ACU
Antenna Combining Unit.
A/D
Analogue to Digital (converter). See ADC.
ADC
ADministration Centre.
ADC
Analogue to Digital Converter. A device that converts a signal

that is a function of a continuous variable into a
representative number sequence carrying equivalent
information.
ADCCP
Advanced Data Communications Control Protocol. A

bit-oriented data-link-layer (DL) protocol used to provide
point-to-point and point-to-multipoint transmission of data
frames that contain error-control information. Note: ADCCP
closely resembles high-level data link control (HDLC).
ADM
ADMinistration processor.
ADMIN
ADMINistration.
ADN
Abbreviated Dialling Number. Abbreviated dialling is a

telephone service feature that (a) permits the user to dial
fewer digits to access a network than are required under the
nominal numbering plan, and (b) is limited to a
subscriber-selected set of frequently dialled numbers.
ADPCM
Adaptive Differential Pulse Code Modulation. Differential

pulse-code modulation (DPCM) in which the prediction
algorithm is adjusted in accordance with specific
characteristics of the input signal.
AE
Application Entity. The system-independent application

activities that are made available as application services to
the application agent.
AEC
Acoustic Echo Control. In a system, the reduction of the

power level of an echo or the elimination of an echo.
AEF
Additional Elementary Functions.
AET
Active Events Table. Alarms and events are sent to the

Events Log in the GUI. Different operators will have different
subscription lists. All alarms and events are sent to the AET
before they are re-routed to different subscription lists.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
AFC
Automatic Frequency Control. A device or circuit that

maintains the frequency of an oscillator within the specified
limits with respect to a reference frequency.
AFN
Absolute Frame Number.
AGC
Automatic Gain Control. A process or means by which gain is

automatically adjusted in a specified manner as a function of
a specified parameter, such as received signal level.
AGCH
Access Grant CHannel. A GSM common control channel

used to assign MS to a SDCCH or a TCH.
Ai
Action indicator.
AI
Artificial Intelligence. A branch of computer science whose

goal is to develop electronic devices that can operate with
some of the characteristics of human intelligence. Among
these properties are logical deduction and inference,
creativity, the ability to make decisions based on past
experience or insufficient or conflicting information, and the
ability to understand natural language.
AIB
Alarm Interface Board.
AIO
A class of processor.
Air interface
The radio link between the BTS and the MS.
AL
See Application Layer.
AM
Amplitude Modulation. Modulation in which the amplitude of a

carrier wave is varied in accordance with some characteristic
of the modulating signal.
AMA
Automatic Message Accounting (processor). A service

feature that automatically records data regarding user-dialled
calls.
AM/MP
Cell broadcast mobile terminated message. A message

broadcast to all MSs in a cell.
ANSI
American National Standards Institute. ANSI is the primary

organisation for fostering the development of technology
standards in the United States. ANSI works with industry
groups and is the U.S. member of ISO and the IEC. Long
established computer standards from ANSI include ASCII and
SCSI.
Antenna
A transmitter/receiver which converts electrical currents into

RF and vice versa. In GSM systems, transmits and receives
RF signals between the BTS and MS.
AoC
Advice of Charge.
AoCC
Advice of Charge Charging supplementary service.
AoCI
Advice of Charge Information supplementary service.
AOC
Automatic Output Control.
AP
Application Process.
Application Layer
See OSI RM. The Application Layer is the highest of seven

hierarchical layers. It interfaces directly to, and performs
common application services for, the application processes. It
also issues requests to the Presentation Layer. The common
application services provide semantic conversion between
associated application processes.

02 May 2003
68P02901W01-M
75
76
GSR6 (Horizon II)
ARFCN
Absolute Radio Frequency Channel Number. The GSM

available frequency is divided in two bands. Each band is
divided into 200kHz slots called ARFCN. Each ARFCN is
shared between 8 mobiles, each using it in turn. Each mobile
uses the ARFCN for one TS (Timeslot) and then waits for its
turn to come around again. A mobile has use of the ARFCN
once per the TDMA frame. The combination of a TS number
and ARFCN is called a physical channel.
ARQ
Automatic Repeat-reQuest. Error control for data

transmission in which the receiver detects transmission errors
in a message and automatically requests a retransmission
from the transmitter.
ARP
Address Resolution Protocol. A Transmission Control

Protocol / Internet Protocol (TCP/IP) protocol that dynamically
binds a Network Layer (NL) IP address to a Data Link Layer
(DL) physical hardware address, e.g., Ethernet address.
ASCE
Association Control Service Element. An ASE which

provides an AP with the means to establish and control an
association with an AP in a remote NE. Maps directly onto
the Presentation layer (OMC).
ASCII
American Standard Code for Information Interchange. ASCII

is a standard developed by ANSI to define how computers
write and read characters. It is the most common format for
text files in computers and on the Internet. In an ASCII file,
alphabetic, numeric, and special characters are represented
with a 7-binary digit binary number. 128 possible characters
are defined. UNIX and DOS-based operating systems (except
for Windows NT) use ASCII for text files. Windows NT uses a
newer code, Unicode. IBMs System 390 servers use a
proprietary 8-bit code called extended binary-coded decimal
interchange code. Conversion programs allow different
operating systems to change a file from one code to another.
ASE
Application Service Element (OMC). A coherent set of

integrated functions to help accomplish application
communication, e.g., within an application entity (AE).
ASE
Application Specific Entity (TCAP).
ASN.1
Abstract Syntax Notation One. A formal notation used for

describing data transmitted by telecommunications protocols,
regardless of language implementation and physical
representation of these data, whatever the application,
whether complex or very simple.
ASP
Alarm and Status Panel.
ASR
Answer Seizure Ratio. The percentage of calls that are

completed successfully.
ATB
All Trunks Busy. An equipment condition in which all trunks

(paths) in a given trunk group are busy.
ATI
Antenna Transceiver Interface.
ATM
Asynchronous Transfer Mode. A high-speed multiplexing and

switching method utilising fixed-length cells of 53 octets to
support multiple types of traffic.
ATT (flag)
ATTach.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
ATTS
Automatic Trunk Testing Subsystem. Ensures the quality of

telephone lines by means of a series of tests. ATTS can be
initiated by either an operator command or by a command
file, which can be activated at a predetermined time.
AU
Access Unit.
AUC
Authentication Centre. A GSM network entity which provides

the functionality for verifying the identity of an MS when
requested by the system. Often a part of the HLR.
AUT(H)
AUThentication.
AUTO
AUTOmatic mode.
B Interface
Interface between MSC and VLR.
BA
BCCH Allocation. The radio frequency channels allocated in a

cell for BCCH transmission.
BAIC
Barring of All Incoming Calls supplementary service.
BAOC
Barring of All Outgoing Calls supplementary service.
Baud
The unit in which the information carrying capacity or

signalling rate of a communication channel is measured. One
baud is one symbol (state transition or level-transition) per
second. This coincides with bits per second only for two-level
modulation with no framing or stop bits
BBBX
Battery Backup Board.
BBH
Base Band Hopping. Method of frequency hopping in which

each transceiver at the base station is tuned to a different
frequency, and the signal is switched to a different transceiver
for each burst.
BCC
Base station Colour Code. The BCC and the NCC are part of
the BSIC. The BCC comprises three bits in the range 000 to
111. See also NCC and BSIC.
BCCH
Broadcast Control CHannel. A GSM control channel used to

broadcast general information about a BTS site on a per cell
or sector basis.
BCD
Binary Coded Decimal. The representation of a decimal digit

by a unique arrangement of no fewer than four binary digits.
BCF
Base station Control Function. The GSM term for the digital
control circuitry which controls the BTS. In Motorola cell sites
this is a normally a BCU which includes DRI modules and is
located in the BTS cabinet.
B channel
Bearer channel. Used in ISDN services to carry 64kbit/s of

data, when used at full capacity.
BCIE
Bearer Capability Information Element. Specific GSM

parameters in the Setup message are mapped into a BCIE
for signalling to the network and within the PLMN. The BCIE
is used to request a bearer service (BS) from the network.
BCU
Base station Control Unit. A functional entity of the BSS

which provides the base control function at a BTS site. The
term no longer applies to a type of shelf (see BSC and BSU).
BCUP
Base Controller Unit Power.
B Interface - Byte

02 May 2003
68P02901W01-M
77
GSR6 (Horizon II)
BER
Bit Error Rate. The number of erroneous bits divided by the

total number of bits transmitted, received, or processed over
some stipulated period. The BER is usually expressed as a
coefficient and a power of 10; for example, 25 erroneous bits
out of 100,000 bits transmitted would be 25 out of 105 or 25 x
10-5.
BES
Business Exchange Services.
BFI
Bad Frame Indication. An indication of unsuccessfully

decoded speech frames. See FER.
BH
Busy Hour. In a communications system, the sliding

60-minute period during which occurs the maximum total
traffic load in a given 24-hour period.
BHCA
Busy Hour Call Attempt. A statistic based on call attempts

that a switch processes during a BH. See also BH.
BI
Barring of all Incoming call supplementary service.
BIB
Balanced-line Interconnect Board. Provides interface to 12

balanced (6-pair) 120 ohm (37-pin D-type connector) lines for
2 Mbit/s circuits. See also T43.
BIC-Roam
Barring of all Incoming Calls when Roaming outside the

Home PLMN Country supplementary service.
Bi-directional neighbour See Reciprocal neighbour..
78
BIM
Balanced-line Interconnect Module.
Bin
From BINary. An area in a data array used to store

information. Also, a name for a directory that contain files
stored in binary format.
BL
BootLoad. Also known as download. For example, databases

and software can be downloaded to the NEs from the BSS.
BLER
Block Error Rate
BLLNG
BiLLiNG.
bit
Binary digit. A character used to represent one of the two

states or digits (0 or 1) in the numeration system with a radix
of two. Also, a unit of storage capacity.
bit/s
Bits per second (bps). A measure of data transmission speed.

The number of binary characters (1s or 0s) transmitted in one
second. For example, an eight-bit parallel transmission link
which transfers one character (eight bits) per second is
operating at 8 bps.
block
A group of bits (binary digits) transmitted as a unit, over which

a parity check procedure is applied for error control purposes.
Bm
Full rate traffic channel. See also Full Rate.
BN
Bit Number. Number which identifies the position of a

particular bit period within a timeslot.
BPF
Bandpass Filter. A filter that ideally passes all frequencies

between two non-zero finite limits and bars all frequencies not
within the limits.
BPSM
mBCU Power Supply Module.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
BRI
Basic Rate Interface. An ISDN multipurpose user interface

allowing simultaneous voice and data services provided over
two clear 64 kb/s channels (B channels) and one clear 16
kb/s channel (D channel). The interface is also referred to as
2B+D.
BS
Base Station. See BSS.
BS
Basic Service (group).
BS
Bearer Service. A type of telecommunication service that

provides the capability for the transmission of signals
between user-network interfaces. The PLMN connection type
used to support a bearer service may be identical to that used
to support other types of telecommunication service.
BSC
Base Station Controller. A network component in the GSM

PLMN which has the digital control function of controlling all
BTSs. The BSC can be located within a single BTS cabinet
(forming a BSS) but is more often located remotely and
controls several BTSs (see BCF, BCU, and BSU).
BSG
Basic Service Group.
BSIC
Base Transceiver Station Identity Code. Each cell has a

BSIC. It is a local colour code that allows a mobile station to
distinguish between different neighbouring base stations. The
BSIC is an octet, consisting of three bits for the Network
Colour Code (NCC) and three bits for the Base station Colour
Code (BCC). The remaining two bits are unused. See also
NCC and BCC.
BSIC-NCELL
BSIC of an adjacent cell.
BSP
Base Site control Processor (at BSC).
BSN
Backward Sequence Number. A field in a signal unit (SU) that

contains the forward sequence number (FSN) of a correctly
received signal unit being acknowledged in the signal unit that
is being returned to the sender. See also FSN and SU.
BSS
Base Station System. The system of base station equipment

(Transceivers, controllers and so on) which is viewed by the
MSC through a single interface as defined by the GSM 08
series of recommendations, as being the entity responsible
for communicating with MSs in a certain area. The radio
equipment of a BSS may cover one or more cells. A BSS
may consist of one or more base stations. If an internal
interface is implemented according to the GSM 08.5x series
of recommendations, then the BSS consists of one BSC and
several BTSs.
BSSAP
BSS Application Part (part of SS7) . Protocol for LAPD or

LAPB signalling links on the A-interface. Comprises DTAP
and BSSMAP messages. Supports message communication
between the MSC and BSS.
BSSC
Base Station System Control cabinet. The cabinet which

houses one or two BSU shelves at a BSC or one or two RXU
shelves at a remote transcoder (RXCDR).
BSSMAP
Base Station System Management Application Part (part of

SS7). Call processing protocol for A-interface messages
exchanged between the MSC and BSS. The BSS interprets
these messages.

02 May 2003
68P02901W01-M
79
GSR6 (Horizon II)
BSSOMAP
BSS Operation and Maintenance Application Part (part of

SS7).
BSU
Base Station Unit shelf. The shelf which houses the digital
control modules for the BTS (part of BTS cabinet) or BSC
(part of BSSC cabinet).
BT
British Telecom.
BT
Bus Terminator. In order to avoid signal reflections on the

bus, each bus segment has to be terminated at its physical
beginning and at its end with the characteristic impedance.
BTC
Bus Terminator Card.
BTF
Base Transceiver Function.
BTP
Base Transceiver Processor (at BTS). One of the six basic

task groups within the GPROC.
BTS
Base Transceiver Station. A network component in the GSM

PLMN which serves one cell, and is controlled by a BSC.
The BTS contains one or more Transceivers (TRXs).
Burst
A period of modulated carrier less than one timeslot. The

physical content of a timeslot.
Byte
A sequence of adjacent binary digits operated upon as a unit.

Generally consists of eight bits, usually presented in parallel.
A byte is usually the smallest addressable unit of information
in a data store or memory.
Conditional.
C Interface
Interface between MSC and HLR/AUC.
C7
See SS7.
CA
Cell Allocation. The radio frequency channels allocated to a

particular cell.
CA
Central Authority. Software process that controls the BSS.
CAB
Cabinet.
CADM
Country ADMinistration. The Motorola procedure used within

DataGen to create new country and network files in the
DataGen database.
CAI
Charge Advice Information.
CAT
Cell Analysis Tool. The CAT is part of the Motorola Cell

Optimization product. It is intended for engineering staff and
OMC administrators. CAT provides information about GSM
network cell performance.
CB
Cell Balancer. The CB process balances the cells configured

for GPRS across PRPs. In the event of a PRP outage, this
process sends message(s) indicating that GPRS service is
unavailable to the appropriate CRM(s) for the cells that could
not be moved to an INS (IN Service) PRP.
CB
Cell Broadcast. See CBSMS.
CB
Circuit Breaker.
CBA
Cell Broadcast Agent.
C - CW
710

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
CBC
Cell Broadcast Centre. The call processing centre for CBSMS

messages.
CBCH
Cell Broadcast CHannel. The channel which is used to

broadcast messages to all MSs in a specific cell.
CBF
Combining Bandpass Filter.
CBL
Cell Broadcast Link. A bi-directional data link which allows

communications between the BSS and the CBC.
CBM
Circuit Breaker Module.
CDMA
Code-Division Multiple Access. CDMA is a digital cellular

technology that uses spread-spectrum techniques. Unlike
competing systems, such as GSM, that use TDM, CDMA
does not assign a specific frequency to each user. Instead,
every channel uses the full available spectrum. Individual
conversations are encoded with a pseudo-random digital
sequence.
CBMI
Cell Broadcast Message Identifier.
CBS
Cell Broadcast Service. See CBSMS.
CBSMS
Cell Broadcast Short Message Service. CBSMS allows a

number of unacknowledged general messages to be
broadcast to all MSs within a particular region. The content
may include information such as local traffic conditions, the
weather, the phone number of the local taxi company, etc.
The messages are sent from a CBC via a BSC to a BTS and
from there on a special cell broadcast channel to the MSs.
The CBC is considered as a node outside the PLMN and can
be connected to several BSCs. However, a BSC is only
connected to one CBC.
CBUS
Clock Bus.
CC
Connection Confirm. Part of SCCP network connectivity.
CC
Country Code. A one to three digit number which specifically

identifies a country of the world that an international call is
being routed to (e.g., 1 = North America, 44 = United
Kingdom).
CC
Call Control. CC functions, such as number translations and

routeing, matrix path control, and allocation of outgoing trunks
are performed by the MSC.
CCB
Cavity Combining Block, a three way RF combiner. There

are two types of CCB, CCB (Output) and CCB (Extension).
These, with up to two CCB Control cards, may comprise the
TATI. The second card may be used for redundancy.
CCBS
Completion of Calls to Busy Subscriber supplementary

service.
CCCH
Common Control CHannels. A class of GSM control

channels used to control paging and grant access. Includes
AGCH, PCH, and RACH.
CCCH_GROUP
Group of MSs in idle mode.
CCD
Common Channel Distributor.
CCDSP
Channel Coding Digital Signal Processor.
CCF
Conditional Call Forwarding. See CFC.

02 May 2003
68P02901W01-M
711
712
GSR6 (Horizon II)
CCH
Control CHannel. Control channels are channels which carry

system management messages.
CCH
Council for Communications Harmonization (referred to in

GSM Recommendations).
CCITT
Comit Consultatif International Tlgraphique et

Tlphonique. This term has been superseded. See
ITU-TSS.
CCM
Current Call Meter.
CCP
Capability/Configuration Parameter.
CCPE
Control Channel Protocol Entity.
CCS
Hundred call-seconds. A single call lasting one hundred

seconds is one CCS. Also, a measure of traffic load obtained
by multiplying the number of calls per hour by the average
holding time per call expressed in seconds, and dividing by
100. Often used in practice to mean hundred call seconds per
hour with per hour implied; as such, it is a measure of traffic
intensity. See also erlang.
CCU
Channel Codec Unit. The CCU performs the following

functions:
Channel coding functions, including FEC and interleaving,
Radio channel measurement functions, including received
quality level, received signal level, and information related to
timing advance measurements.
Cct
Circuit.
CDB
Control Driver Board.
CDE
Common Desktop Environment. Part of the SUN software

(crontab - cron job file).
CDR
Call Detail Record. A record of voice or data SVCs, which

includes calling and called numbers, local and remote node
names, data and timestamp, elapsed time, and call failure
class fields. This is the information needed to bill the
customer for calls and facility usage data for calls.
CD-ROM
Compact Disk-Read Only Memory.
CDUR
Chargeable DURation.
CEB
Control Equalizer Board (BTS).
CED
Called station identifier.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
CEIR
Central Equipment Identity Register.
Cell
By GSM definition, a cell is an RF coverage area. At an

omni-site, cell is synonymous with site; at a sectored site, cell
is synonymous with sector. This differs from analogue
systems where cell is taken to mean the same thing as site.
(See below).
1 Cell =
1 Sector
Omni Site
1-Cell Site
(1 BTS)
6-Sector Site
or
6-Cell Site
(6 BTSs)
CEND
End of charge point. The time at which the calling, or called,

party stops charging by the termination of the call or by an
equivalent procedure invoked by the network or by failure of
the radio path.
CEPT
Confrence des administrations Europennes des Postes et

Telecommunications.
CERM
Circuit Error Rate Monitor. Identifies when discontinuity is

detected in a circuit. An alarm is generated and sent to the
OMC-R when the error count exceeds an operator specified
threshold. The alarm identifies the RCI or CIC and the path
where the error is detected.
CF
Conversion Facility.
CF
Call Forwarding. A feature available to the mobile telephone

user whereby, after initiation of the feature by an authorised
subscriber, calls dialled to the mobile telephone of an
authorised subscriber will automatically be routed to the
desired number. See also CFC and CFU.
CF
Control Function. CF performs the SGSN mobility

management functions and OA&M functions for the GSN
module.
CFB
Call Forwarding on mobile subscriber Busy supplementary

service. Service automatically redirects incoming calls for
phone busy situations.
CFC
Call Forwarding Conditional supplementary service. Service

automatically redirects incoming calls for busy, no reply, or
not reachable situations. See also CFB, CFNRc, and CFNRy.
CFNRc
Call Forwarding on mobile subscriber Not Reachable

supplementary service. Service automatically redirects
incoming calls for not reachable situations.
CFNRy
Call Forwarding on No Reply supplementary service. Service

automatically redirects incoming calls for no reply situations.
CFU
Call Forwarding Unconditional supplementary service.

Service automatically redirects all incoming calls.
CG
Charging Gateway.

02 May 2003
68P02901W01-M
713
714
GSR6 (Horizon II)
CGF
Charging Gateway Function.
Channel
A means of one-way transmission. A defined sequence of

periods (for example, timeslots) in a TDMA system; a defined
frequency band in an FDMA system; a defined sequence of
periods and frequency bands in a frequency hopped system.
CIM
Coaxial Interconnect Module.
Channel Mode
See Full Rate and Half Rate. These are the channel modes
that are currently used.
CHP
CHarging Point.
CHV
Card Holder Verification information.
CKSN
Ciphering Key Sequence Number. The CKSN is a number

which is associated with the ciphering key, Kc. It is used to
ensure authentication consistency between the MS and the
VLR.
CI
Cell Identity. A block of code which identifies a cell within a

location area.
CI
CUG Index.
CIC
Circuit Identity Code. The unique identifier of the terrestrial

portion of a circuit path. A CIC is either a 64 kbit/s or 16 kbit/s
connection depending on whether a site has local or remote
transcoding. A CIC with local transcoding occupies a
complete E1/T1 timeslot. A 16 kbit/s CIC, at a site with
remote transcoding, occupies a sub-channel of an E1/T1
timeslot.
CIR, C/I
Carrier to Interference Ratio. Indicates the received signal

power level relative to the interference power level.
Ciphertext
Unintelligible data produced through the use of encipherment.
CKSN
Ciphering Key Sequence Number.
CLI
Calling Line Identity. The identity of the caller. See also CLIP
and CLIR.
CLIP
Calling Line Identification Presentation supplementary

service. Allows the called party to identify the caller. See also
CLIR.
CLIR
Calling Line Identification Restriction supplementary service.

Allows the caller to withhold their identity from the called
party. See also CLIP.
CLK
Clock.
CLKX
Clock Extender half size board. The fibre optic link that
distributes GCLK to boards in system (part of the BSS, etc).
CLM
ConnectionLess Manager. Coordinates global control over the

BSS by handling of all connectionless messages (that is,
messages that are not directly concerned with a connected
call). This includes such messages as global resets, load
limiting and circuit blocking.
CLR
CLeaR.
CM
Configuration Management. Configuration management

allows the operator to perform network configuration tasks,
and to maintain all details of the network configuration at the
OMC.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
CM
Connection Management. See CLM.
CM
Connectionless Manager. See CLM.
CMD
CoMmanD.
CMM
Channel Mode Modify. Message sent to an MS to request a

channel mode change. When it has received the CMM
message, the MS changes the mode to the indicated channel
and replies with a Channel Mode Modify Acknowledge
message indicating the new channel mode.
CMIP
Common Management Information Protocol. Protocol used

for communication over the OML.
CMISE
Common Management Information Service Element. An ASE

which provides a means to transfer management information
via CMIP messages with another NE over an association
established by ASCE using ROSE (OMC).
CMR
Cellular Manual Revision. Documentation updates.
CNG
CalliNg tone.
Codec
Coder/Decoder. A speech coding unit that converts speech

into a digital format for radio broadcast, and vice versa.
CODEX
Manufacturers name for a type of multiplexer and packet

switch commonly installed at the Motorola OMC-R.
Coincident Cell
A cell whose cell boundary follows the boundary of a

co-located neighbour cell. The coincident cell has a different
frequency type, but the same BSIC, as that of the neighbour
cell.
COLI
COnnected Line Identity. Identity of the connected line. See

also COLP and COLR.
Collocated
Placed together; two or more items together in the same

place.
Colour Code
An 8-bit code assigned to a BTS to distinguish interfering

signals from another cell.
COLP
COnnected Line Identification Presentation supplementary

service. Allows the calling party to identify the line identity of
the connected party. See also COLR.
COLR
COnnected Line Identification Restriction supplementary

service. Allows the connected party to withhold its line identity
from the calling party. See also COLP.
COM
Code Object Manager (software).
COM
COMplete.
COMB
Combiner. The purpose of a combiner in the BSS is to

combine transmitter outputs from the RCUs onto an antenna.
COMM, Comms
COMMunications.
CommHub
Communications Hub. Provides Ethernet switching and IP

routeing for the GSN complex local networking and GSN
complex E1 interfaces to the public data network.
CommsLink
Communications Link. See also 2 Mbit/s link.
Compact PCI
See cPCI.
CONF
CONFerence circuit. Circuit used for multi-party conference

calls.

02 May 2003
68P02901W01-M
715
716
GSR6 (Horizon II)
CONFIG
CONFIGuration Control Program.
Congestion
Situation occurring when an element cannot receive all the

service it is requesting.
CONNACK
CONNect ACKnowledgement. Part of the synchronization

process. After a connection has been established, the
CONNACK message indicates that traffic channels are
available.
CP
Call Processing. The CP process in the BTS controls the MS

to BSS to MS signalling link, MS originated and terminated
calls and inter-BSS and inter-BTS handovers.
cPCI
Compact Peripheral Component Interconnect. A set of

standards that define a common card cage, power supplies,
and processor boards.
CPGM
CCCH Paging Manager. The CPGM processes the paging

messages sent from the SGSN to the BSC/BTS.
CPU
Central Processing Unit. The portion of a computer that

controls the interpretation and execution of instructions.
Also, the portion of a digital communications switch that
executes programmed instructions, performs arithmetic and
logical operations on signals, and controls input/output
functions.
C/R
Command/Response field bit.
CR
Carriage Return (RETURN).
CR
Connection Request (Part of SCCP network connectivity). An

SCCP Connection Request message is sent from the BSS to
the MSC to establish a connection. See also CREF.
CRC
Cyclic Redundancy Check (3 bit). An error-detection scheme

that (a) uses parity bits generated by polynomial encoding of
digital signals, (b) appends those parity bits to the digital
signal, and (c) uses decoding algorithms that detect errors in
the received digital signal.
CRE
Call RE-establishment procedure. Procedure for

re-establishing a call in the event of a radio link failure.
CREF
Connection REFused (Part of SCCP network connectivity). In

a number of operating circumstances, a CREF message may
be sent from the MSC to the BSS in response to a
Connection Request (CR).
CRM
Cell Resource Manager. The CRM allocates and activates

timeslots and subchannels on the available carriers.
CRM
Cell Resource Machine.
CRM-LS/HS
Cellular Radio Modem-Low Speed/High Speed. Low speed

modem used to interwork 300 to 2400 bit/s data services
under V.22bis, V.23, or V.21 standards. High speed modem
used to interwork 1200 to 9600 bit/s data services under
V.22bis, V.32, or V.29/V.27ter/V.21 standards.
CRO
Motorola Controlled Roll Out Group. A CRO consists of a

customer site implementation of a new product, software
release, or combination of products/releases.
CRT
Cathode Ray Tube (video display terminal).
CS-1
GPRS Coding Scheme-1 (9.05 kbit/s per TCH).

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
CS-2
CS-3
CS-4
CSFP
Code Storage Facility Processor (at BSC and BTS). A

GPROC device which facilitates the propagating of new
software instances with reduced system down time. See also
IP.
CSP
Central Statistics Process. The statistics process in the BSC.
CSPDN
Circuit Switched Public Data Network. A publicly available

communications network using circuit switched digital data
circuits.
CT
Call Transfer supplementary service.
CT
Channel Tester.
CT
Channel Type.
CTP
Call Trace Product (Tool). The CTP is designed to help

operators of GSM900 and DCS1800 communication networks
tune and optimize their systems. CTP allows Call Trace data
to be analysed and decoded.
CTP
Control Terminal Port.
CTR
Common Technical Regulation.
CTS
Clear to Send. A handshake signal used with communication

links, especially RS232 or CCITT Rec. V.24, to indicate (to a
transmitter from a receiver) that transmission may proceed.
Generated in response to a request to send signal. See also
RTS.
CTU
Compact Transceiver Unit (M-Cellhorizon radio).
CUG
Closed User Group supplementary service. A CUG is used to

control who can receive and/or place calls, by creating a
unique group. When a CUG is configured for an interface,
only those subscribers that are members of the same CUG
can receive/place calls.
Cumulative value
The total value for an entire statistical interval.
CW
Call Waiting supplementary service. A subscriber feature

which allows an individual mobile telephone user currently
engaged in a call to be alerted that another caller is trying to
reach him. The user has a predetermined period of time in
which to terminate the existing conversation and respond to
the second call.

02 May 2003
68P02901W01-M
717
GSR6 (Horizon II)
D Interface - DYNET
718
D Interface
Interface between VLR and HLR.
D/A
Digital to Analogue (converter). See DAC.
DAB
Distribution Alarm Board (in BTS6 cabinet).
DAC
Digital to Analogue Converter. A device that converts an input

number sequence into a function of a continuous variable.
DACS
Digital Access Cross-connect System. A data concentrator

and organizer for Tl / El based systems.
DAK
Downlink Acknowledgement
DAN
Digital ANnouncer (for recorded announcements on MSC).
DAS
Data Acquisition System.
DAT
Digital Audio Tape. Audio-recording and playback

medium/format that maintains a signal quality equal to that of
the CD-ROM medium/format.
DataGen
Sysgen Builder System. A Motorola offline BSS binary object

configuration tool.
Data Link Layer
See OSI RM. This layer responds to service requests from

the Network Layer and issues service requests to the
Physical Layer. It provides the functional and procedural
means to transfer data between network entities and to detect
and possibly correct errors that may occur in the Physical
Layer.
dB
Decibel. A unit stating the logarithmic ratio between two

numeric quantities. See also dBm.
DB
DataBase.
DB
Dummy Burst (see Dummy burst).
DBA
DataBase Administration/Database Administrator.
dBm
A dB referenced to 1 milliwatt; 0 dBm equals one milliwatt.
DBMS
DataBase Management System.
dc
Direct Current. DC is the unidirectional flow or movement of

electric charge carriers, usually electrons. The intensity of the
current can vary with time, but the general direction of
movement stays the same at all times. As an adjective, the
term DC is used in reference to voltage whose polarity never
reverses.
DCB
Diversity Control Board (part of DRCU).
DCCH
Dedicated Control CHannel. A class of GSM control

channels used to set up calls and report measurements.
Includes SDCCH, FACCH, and SACCH.
DCD
Data Carrier Detect signal. Hardware signal defined by the

RS-232-C specification that indicates that a device such as a
modem is on-line and ready for transmission.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
DCE
Data Circuit terminating Equipment. The DCE performs

functions such as signal conversion and coding, at the
network end of the line between the DTE and the line.
Also, The RS232 configuration designated for computers.
DCE equipment can be connected to DTE equipment with a
straight cable, but to other DCE equipment only with a null
modem cable.
DCF
Data Communications Function.
DCF
Duplexed Combining bandpass Filter. (Used in

Horizonmacro).
D channel
Data channel. Used in ISDN to perform call signalling and

connection setup functions. In some circumstances, the
channel can also be used to carry user data.
DCN
Data Communications Network. A DCN connects Network

Elements with internal mediation functions or mediation
devices to the Operations Systems.
DC PSM
DC Power Supply Module.
DCS1800
Digital Cellular System at 1800 MHz. A cellular phone

network using digital techniques similar to those used in GSM
900, but operating on frequencies of 1710 - 1785 MHz
(receive) and 1805 - 1880 MHz (transmit).
DDF
Dual-stage Duplexed combining Filter. (Used in

Horizonmacro). The DDF is an integrated combiner, filter and
duplexer.
DDS
DataGen Data Store. Store area for DataGen input and

output files.
DDS
Data Drive Storage.
DDS
Direct Digital Synthesis. A technology for generating highly

accurate and frequency-agile (rapidly changeable frequency
over a wide range), low-distortion output waveforms.
DEQB
Diversity Equalizer Board.
DET
DETach.
DFE
Decision Feedback Equalizer. A receiver component/function.

The DFE results in a very sharp Bit Error Rate (BER)
threshold by using error feedback.
DGT
Data Gathering Tool. The DGT collects all the relevant data
relating to a specified problem and copies it to tape or file,
together with a problem description. The file or tape is then
sent to Motorola for analysis.
DHP
Digital Host Processor. A hard GPROC based device located

at Horizonmicro2 BTS sites. It represents the MCU of a slave
Horizonmicro2 FRU. The MCU that the DHP represents is
responsible for providing DRI and carrier support.
DIA
Drum Intercept Announcer.
DINO E1/HDSL
Line termination module (part of Horizonmicro).
DINO T1
Line termination module (part of Horizonmicro).
DISC
DISConnect.
Discon
Discontinuous.

02 May 2003
68P02901W01-M
719
720
GSR6 (Horizon II)
DIQ
Diversity In phase and Quadrature phase.
DIR
Device Interface Routine. Software routine used in the BSS.
DL
Data Link (layer). See Data Link Layer.
DL
See Downlink.
DLCI
Data Link Connection Identifier. In frame-relay transmission

systems, 13-bit field that defines the destination address of a
packet. The address is local on a link-by-link basis.
DLD
Data Link Discriminator.
DLNB
Diversity Low Noise Block.
DLS
DownLink Segmentator. The DLS segments LLC frames into

RLC data blocks to be transmitted over the air interface.
DLSP
Data Link Service Process. Handles messages for an OMP

and a shelf GPROC.
DLSP
Digital Link Signalling Processor.
Dm
Control channel (ISDN terminology applied to mobile service).
DMA
Deferred Maintenance Alarm. An alarm report level; an

immediate or deferred response is required (see also PMA).
DMA
Direct Memory Access. Transfer of data from a peripheral

device, such as a hard disk drive, into memory without that
data passing through the microprocessor. DMA transfers data
into memory at high speeds with no processor overhead.
DMR
Digital Mobile Radio.
DMX
Distributed Electronic Mobile Exchange (Motorolas

networked EMX family).
DN
Directory Number.
DNIC
Data Network Identifier Code. In the CCITT International

X.121 format, the first four digits indicate the international
data number, the next three digits are the data country code,
and the final digit is the network code.
DNS
Domain Name Service. A service that translates from logical

domain or equipment names to IP addresses.
Downlink
Physical link from the BTS towards the MS (BTS transmits,

MS receives).
DP
Dial/Dialled Pulse. A dc pulse produced by an end instrument

that interrupts a steady current at a sequence and rate
determined by the selected digit and the operating
characteristics of the instrument.
DPC
Destination Point Code. A part of the label in a signalling

message that uniquely identifies, in a signalling network, the
(signalling) destination point of the message.
DPC
Digital Processing and Control board.
DPCM
Pulse-code modulation (PCM) in which an analog signal is

sampled and the difference between the actual value of each
sample and its predicted value, derived from the previous
sample or samples, is quantified and converted, by encoding,
to a digital signal. Note: There are several variations of
differential pulse-code modulation.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
DPNSS
Digital Private Network Signalling System (BT standard for

PABX interface).
DPP
Dual Path Preselector. BTS module.
DPR, DPRAM
Dual Port Random Access Memory.
DPSM
Digital Power Supply Module.
DRAM
Dynamic Random Access Memory. A type of semiconductor

memory in which the information is stored in capacitors on a
integrated circuit.
DRC
Data Rate Converter board. Provides data and protocol

conversion between PLMN and destination network for 8
circuits. Part of IWF.
DRCU
Diversity Radio Channel Unit. Contains transceiver, digital

control circuits, and power supply. Part of the BSS.
DRI
Digital Radio Interface. Provides encoding/decoding and

encryption/decryption for radio channels. Part of BSS.
DRIM
Digital Radio Interface extended Memory. A DRI with extra

memory.
DRIX
DRI Extender half size board. Fibre optic link from DRI to
BCU. Part of the BSS.
DRX, DRx
Discontinuous reception (mechanism). A means of saving

battery power (for example in hand-portable units) by
periodically and automatically switching the MS receiver on
and off.
DS-1
Digital transmission System 1 (or Digital Signal level 1). Term

used to refer to the 1.44 Mbit/s (U.S.) or 2.108 Mbit/s
(Europe) digital signal carried on a T1 facility.
DS-2
German term for 2 Mbit/s line (PCM interface).
DSE
Data Switching Exchange.
DSI
Digital Speech Interpolation. A compression technique that

relies on the pauses between speech bursts to provide
additional compression. DSI enables users to gain an
additional 2:1 compression on the average on their line.
DSP
Digital Signal Processor. A specialized, programmable

computer processing unit that is able to perform high-speed
mathematical processing.
DSS1
Digital Subscriber Signalling No 1. N-ISDN user network

interface signalling.
DSSI
Diversity Signal Strength Indication.
DTAP
Direct Transfer Application Part (Part of SS7). Call processing

protocol for A-Interface messages exchanged directly
between the MSC and the mobile unit without interpretation
by the BSS.
DTE
Data Terminal Equipment. An end instrument that converts

user information into signals for transmission or reconverts
the received signals into user information.
Also, the RS232 configuration designated for terminals. DTE
equipment can be connected to DCE with a straight cable,
but to other DTE equipment only with a null modem.

02 May 2003
68P02901W01-M
721
GSR6 (Horizon II)
DTF
Digital Trunk Frame. A frame or electronic rack of digital trunk

interface equipment.
DT1
DaTa form 1 (Part of SCCP network connectivity).
DTI
Digital Trunk Interface.
DTMF
Dual Tone Multi-Frequency. Multifrequency signalling in which

specified combinations of two voice band frequencies, one
from a group of four low frequencies and the other from a
group of four higher frequencies, are used. The sounds a
push button tone telephone makes when it dials a number.
DTR
Data Terminal Ready signal. Method of flow control (RS232

Interface). A modem interface control signal sent from the
DTE to the modem, usually to indicate to the modem that the
DTE is ready to transmit data.
DTRX
Dual Transceiver Module. (Radio used in Horizonmicro

(M-Cellarena) and Horizonmacro (M-Cellarena macro)).
DTX, DTx
Discontinuous Transmission (mechanism). A means of

saving battery power (for example in hand-portable units) and
reducing interference by automatically switching the
transmitter off when no speech or data are to be sent.
Dummy burst
A period of carrier less than one timeslot whose modulation is

a defined sequence that carries no useful information. A
dummy burst fills a timeslot with an RF signal when no
information is to be delivered to a channel.
DYNET
DYnamic NETwork. Used to specify BTSs sharing dynamic

resources.
See Erlang.
E1
Also known as CEPT1. The 2.048 Mbit/s rate used by

European CEPT carrier to transmit 30 64 kbit/s digital
channels for voice or data calls, plus a 64 kbit/s signalling
channel and a 64 kbit/s channel for framing and maintenance.
E Interface
Interface between MSC and MSC.
EA
External Alarm. See EAS. Typical external alarms are: Door

open, High humidity, Low humidity, Fire, Intruder.
EAS
External Alarm System. The EAS is responsible for the

monitoring of all customer-defined environmental alarms at a
site. The customer defines the alarm string and the severity
of the alarms based on the individual requirements of the site.
Indications are provided when the alarms are set or cleared.
Eb/No
Energy per Bit/Noise floor, where Eb is the signal energy per

bit and No is the noise energy per hertz of noise bandwidth.
EBCG
Elementary Basic Service Group.
EC
Echo Canceller. Performs echo suppression for all voice

circuits. If cancellation does not take place, the PLMN
subscriber hears the voice signal as an echo, due to the total
round-trip delay introduced by the GSM system (typically 180
ms).
ECB
Provides echo cancelling for telephone trunks for 30 channels

(EC).
E - EXEC
722

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
ECID
The Motorola European Cellular Infrastructure Division.
ECM
Error Correction Mode. A facsimile mode, in which the

sending machine will attempt to send a partial page up to four
times.
Ec/No
Ratio of energy per modulating bit to the noise spectral

density.
ECT
Event Counting Tool. The ECT provides information about the

number and type of events and alarms generated throughout
the network. It extracts data from the event log files for
specified dates, allowing the user to generate reports on
individual network elements, groups of elements, or the whole
network.
ECT
Explicit Call Transfer supplementary service. ECT enables a

user to connect two other parties with which he is engaged in
a telephone call and leave the connection himself.
EEL
Electric Echo Loss.
EEPROM
Electrically Erasable Programmable Read Only Memory. An

EEPROM is a special type of PROM that can be erased by
exposing it to an electrical charge. Like other types of PROM,
EEPROM retains its contents even when the power is turned
off.
EGSM900
Extended GSM900. EGSM900 provides the BSS with a

further range of frequencies for MS and BSS transmit. EGSM
MSs can use the extended frequency band as well as the
primary band, while non-EGSM MSs cannot use the
extended frequency band. A GSM900 cell can contain both
GSM900 and EGSM900 carrier hardware. EGSM operates
on the frequency range, 880 - 915 MHz (receive) and
925 - 960 MHz (transmit).
EI
Events Interface. Part of the OMC-R GUI.
EIR
Equipment Identity Register. The EIR contains a centralized

database for validating the IMEI. The register consists of lists
of IMEIs organised as follows:
White List - IMEIs which are known to have been assigned to
valid MS equipment.
Black List - IMEIs which have been reported stolen or which
are to be denied service for some other reason.
Grey List - IMEIs which have problems (for example, faulty
software). These are not, however, sufficiently significant to
warrant a black listing.
EIRP
Effective Isotropically Radiated Power. The arithmetic product

of the power supplied to an antenna and its gain.
EIRP
Equipment Identity Register Procedure.
EL
Echo Loss.
EM
Event Management. An OMC-R application. It provides a

centralised facility for reporting network-wide generated
events and alarms, and for monitoring the status of the
Network.

02 May 2003
68P02901W01-M
723
724
GSR6 (Horizon II)
EMC
ElectroMagnetic Compatibility. The ability of systems,

equipment, and devices that utilize the electromagnetic
spectrum to operate in their intended operational
environments without suffering unacceptable degradation or
causing unintentional degradation because of electromagnetic
radiation or response.
EMF
Electro Motive Force. The rate at which energy is drawn from

a source that produces a flow of electricity in a circuit;
expressed in volts.
EMI
Electro Magnetic Interference. Any electromagnetic

disturbance that interrupts, obstructs, or otherwise degrades
or limits the effective performance of electronics/electrical
equipment.
eMLPP
enhanced Multi-Level Precedence and Pre-emption service.

This service has two parts: precedence and pre-emption.
Precedence involves assigning a priority level to a call in
combination with fast call set-up. Pre-emption involves the
seizing of resources, which are in use by a call of a lower
precedence, by a higher level precedence call in the absence
of idle resources. Pre-emption can also involve the
disconnection of an on-going call of lower precedence to
accept an incoming call of higher precedence.
EMMI
Electrical Man Machine Interface.
EMU
Exchange office Management Unit (part of Horizonoffice)
EMX
Electronic Mobile Exchange (Motorolas MSC family).
en bloc
Fr. all at once (a CCITT #7 Digital Transmission scheme);

En bloc sending means that digits are sent from one system
to another ~ (that is, all the digits for a given call are sent at
the same time as a group). ~ sending is the opposite of
overlap sending. A system using ~ sending will wait until it
has collected all the digits for a given call before it attempts to
send digits to the next system. All the digits are then sent as
a group.
EOT
End of Tape.
EPROM
Erasable Programmable Read Only Memory. EPROM is a

type of memory that retains its contents until it is exposed to
ultraviolet light. The ultraviolet light clears its contents,
making it possible to re-program the memory.
EPSM
Enhanced Power Supply Module. Used in +27 V positive

earth cabinets.
EQ50
Static model against which the performance of the equalizer

is tested to extremes. See also TU3, TU50, HT100 and
RA250.
EQB
Equalizer Board. Control circuit for equalization for 8 time

slots each with equalizing circuitry and a DSP.
EQCP
Equalizer Control Processor.
EQDSP
Equalizer Digitizer Signal Processor.
Equalization
The process by which attenuation and/or phase shift is

rendered essentially constant over a band of frequencies,
even though the transmission medium or the equipment has
losses that vary with frequency.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Equalizer
An electrical network in which attenuation (or gain) and/or

phase shift varies as a function of frequency. Used to provide
equalization.
Erlang
International (dimensionless) unit of traffic intensity defined as

the ratio of time a facility is occupied to the time it is available
for occupancy. One erlang is equal to 36 CCS. In the US
this is also known as a traffic unit (TU).
ERP
Ear Reference Point. Facility for assessing handset and

headset acoustic responses.
ERP
Effective Radiated Power. The power supplied to an antenna

multiplied by the antenna gain in a given direction.
ERR
ERRor.
ESP
Electro-static Point. Connection point on the equipment for an

anti-static wrist strap.
ESQL
Embedded SQL (Structured Query Language). An RDBMS

programming interface language.
E-TACS
Extended TACS (analogue cellular system, extended).
Ethernet
A standard protocol (IEEE 802.3) for a 10 Mbit/s baseband

local area network (LAN) bus using carrier-sense multiple
access with collision detection (CSMA/CD) as the access
method, implemented at the Physical Layer in the OSI RM,
establishing the physical characteristics of a CSMA/CD
network.
ETR
ETSI Technical Report.
ETS
European Telecommunication Standard.
ETSI
European Telecommunications Standards Institute.
ETX
End of Transmission.
EXEC
Executive Process.
F Interface - Full Rate

F Interface
Interface between MSC and EIR.
FA
Fax Adaptor. Device which complements Group 3 facsimile

apparatus in order to be able to communicate over a GSM
PLMN.
FA
Full Allocation.
FA
Functional Area.
FAC
Final Assembly Code.
FACCH
Fast Associated Control Channel. A GSM dedicated control

channel which temporarily uses the TCH to perform high
speed transmissions, and carries control information after a
call is set up. See also SDCCH.
FACCH/F
Fast Associated Control Channel/Full rate. See also Full

Rate.
FACCH/H
Fast Associated Control Channel/Half rate. See also Half

Rate.
FB
See Frequency correction burst.

02 May 2003
68P02901W01-M
725
726
GSR6 (Horizon II)
FBM
Flow control Buffer Management. FBM is a functional unit

residing on the PRP. It controls buffer capacity for each cell
and each mobile so that the incoming data from the SGSN
matches the air throughput.
FC-AL
Fibre Channel Arbitrated Loop. A serial data transfer

architecture. FC-AL is designed for mass storage devices and
other peripheral devices that require very high bandwidth.
Using optical fibre to connect devices, FC-AL supports
full-duplex data transfer rates of 100MBps.
FCCH
Frequency Correction CHannel. A GSM broadcast control

channel which carries information for frequency correction of
the MS.
FCP
Fault Collection Process. Part of the fault management

process in the BTS.
FCS
Frame Check Sequence. The extra characters added to a

frame for error detection and correction.
FDM
Frequency Division Multiplex. A multiplexing technique that

uses different frequencies to combine multiple streams of
data for transmission over a communications medium. FDM
assigns a discrete carrier frequency to each data stream and
then combines many modulated carrier frequencies for
transmission.
FDMA
Frequency Division Multiple Access. The use of frequency

division to provide multiple and simultaneous transmissions to
a single transponder.
FDN
Fixed Dialling Number. The fixed dialling feature limits dialling

from the MS to a pre-determined list maintained on the SIM
card. It can be used to limit calling to certain areas,
exchanges or full phone numbers.
FDP
Fault Diagnostic Procedure.
FEC
Forward Error Correction. Correction of transmission errors

by transmitting additional information with the original bit
stream. If an error is detected, the additional information is
used to recreate the original information.
FEP
Front End Processor. An OMC-R device. The FEP is a driver

that stores data in its own database about all of the sites in
the system. All bursts from the sites are directed to the FEP.
It can also interrogate the sites and collect its data either
manually or automatically at pre-defined times.
FER
Frame Erasure Ratio. The ratio of successfully decoded good

speech frames against unsuccessfully decoded bad frames.
FFS, FS
For Further Study.
FH
See Frequency Hopping.
FIB
Forward Indicator Bit. Used in SS7 - Message Transfer Part.

The forward indicator bit and backward indicator bit together
with the forward sequence number and backward sequence
number are used in the basic error control method to perform
the signal unit sequence control and acknowledgement
functions.
FIFO
Memory logic device in which the information placed in the

memory in a given order is retrieved in that order.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
FIR
Finite Impulse Response (filter type).
FK
Foreign Key. A database column attribute; the foreign key

indicates an index into another table.
FM
Fault Management (at OMC).
FM
Frequency Modulation. Modulation in which the instantaneous

frequency of a sine wave carrier is caused to depart from the
centre frequency by an amount proportional to the
instantaneous value of the modulating signal.
FMIC
Fault Management Initiated Clear. An alarm type. If an FMIC

alarm is received, the fault management software for the
network item clears the alarm when the problem is solved.
See also Intermittent and OIC.
FMUX
Fibre optic MUltipleXer module.
FN
Frame Number. Identifies the position of a particular TDMA

frame within a hyperframe.
FOA
First Office Application. A full functional verification of new

product(s) on a commercial system using accepted
technology and approved test plans.
FOX
Fibre Optic eXtender board.
FR
See Full Rate.
FR
Frame Relay. An interface protocol for statistically multiplexed

packet-switched data communications in which (a)
variable-sized packets (frames) are used that completely
enclose the user packets they transport, and (b) transmission
rates are usually between 56 kb/s and 1.544 Mb/s (the T-1
rate).
Frame
A set of consecutive Pulse Code Modulation (PCM) time slots

containing samples from all channels of a group, where the
position of each sample is identified by reference to a frame
alignment signal. Also, an information or signal structure
which allows a receiver to identify uniquely an information
channel.
Frame Alignment
The state in which the frame of the receiving equipment is

synchronized with respect to that of the received signal to
accomplish accurate data extraction.
FRU
Field Replaceable Unit. A board, module, etc. which can be

easily replaced in the field with a few simple tools.
Frequency Correction
Period of RF carrier less than one timeslot whose modulation

bit stream allows frequency correction to be performed easily
within an MS burst.
Frequency Hopping
The repeated switching of frequencies during radio

transmission according to a specified algorithm. Frequency
hopping improves capacity and quality in a highly loaded
GSM network. Multipath fading immunity can be increased by
using different frequencies and interference coming from
neighbour cells transmitting the same or adjacent frequencies
can be reduced.

02 May 2003
68P02901W01-M
727
GSR6 (Horizon II)
FS
Frequency Synchronization. All BSS frequencies and timing

signals are synchronized to a high stability reference
oscillator in the BSS. This oscillator can free run or be
synchronized to the recovered clock signal from a selected
E1/T1 serial link. MSs lock to a reference contained in a
synchronization burst transmitted from the BTS site.
FSL
Free Space Loss. The decrease in the strength of a radio

signal as it travels between a transmitter and receiver. The
FSL is a function of the frequency of the radio signal and the
distance the radio signal has travelled from the point source.
FSN
Forward Sequence Number. See FIB.
FTAM
File Transfer, Access, and Management. An ASE which

provides a means to transfer information from file to file.
(OMC).
ftn
forwarded-to number.
FTP
Fault Translation Process (in BTS).
FTP
File Transfer Protocol. A client-server protocol which allows a

user on one computer to transfer files to and from another
computer over a TCP/IP network. Also the client program the
user executes to transfer files.
Full Rate
Refers to the current capacity of a data channel on the GSM

air interface, that is, 8 simultaneous calls per carrier. See also
HR - Half Rate.
G Interface
Interface between VLR and VLR.
Gateway MSC
An MSC that provides an entry point into the GSM PLMN

from another network or service. A gateway MSC is also an
interrogating node for incoming PLMN calls.
GB, Gbyte
Gigabyte. 230 bytes = 1,073,741,824 bytes = 1024

megabytes.
GBIC
Gigabit Interface Converter Converter for connection to the

Gigabit Ethernet.
GCLK
Generic Clock board. System clock source, one per site (part
of BSS, BTS, BSC, IWF, RXCDR).
GCR
Group Call Register. The register which holds information about

VGCS or VBS calls.
GDP
Generic DSP Processor board. Interchangeable with the XCDR

board.
GDP E1
GDP board configured for E1 link usage.
GDP T1
GDP board configured for T1 link usage.
GGSN
Gateway GPRS Support Node. The GGSN provides internet

working with external packet-switched networks.
GHz
Giga-Hertz (109).
GID
Group ID. A unique number used by the system to identify a

users primary group.
GMB
GSM Multiplexer Board (part of the BSC).
GMR
General Manual Revision.
G Interface - GWY
728

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
GMSC
Gateway Mobile-services Switching Centre. See Gateway

MSC.
GMSK
Gaussian Minimum Shift Keying. The modulation technique

used in GSM.
GND
GrouND.
GOS
Grade of Service. A traffic statistic defined as the percentage

of calls which have a Probability of Busy or Queueing Delay.
An alternative criterion is a maximum time for a percentage of
calls to wait in the busy queue before they are assigned a
voice channel.
GPA
GSM PLMN Area.
GPC
General Protocol Converter.
GPROC
Generic Processor board. GSM generic processor board: a

68030 with 4 to 16 Mb RAM (part of BSS, BTS, BSC, IWF,
RXCDR).
GPROC2
Generic Processor board. GSM generic processor board: a

68040 with 32 Mb RAM (part of BSS, BTS, BSC, IWF,
RXCDR).
GPRS
General Packet Radio Service. A GSM data transmission

technique that does not set up a continuous channel from a
portable terminal for the transmission and reception of data,
but transmits and receives data in packets. It makes very
efficient use of available radio spectrum, and users pay only
for the volume of data sent and received.
GPS
Global Positioning by Satellite. A system for determining

position on the Earths surface by comparing radio signals
from several satellites.
GSA
GSM Service Area. The area in which an MS can be reached

by a fixed subscriber, without the subscribers knowledge of
the location of the MS. A GSA may include the areas served
by several GSM PLMNs.
GSA
GSM System Area. The group of GSM PLMN areas

accessible by GSM MSs.
GSM
Groupe Spcial Mobile (the committee).
GSM
Global System for Mobile communications (the system).
GSM900
See PGSM.
GSM MS
GSM Mobile Station.
GSM PLMN
GSM Public Land Mobile Network.
GSM RF
GSM Radio Frequency.
GSN
GPRS Support Node. The combined functions provided by

the SGSN and GGSN.
GSN Complex
A GSN Complex consists of an ISS Cluster, GGSN and

SGSNs connected to a single CommHub.
GSR
GSM Software Release.
GT
Global Title. A logical or virtual address used for routing SS7

messages using SCCP capabilities. To complete message
routing, a GT must be translated to a SS7 point code and
subsystem number.

02 May 2003
68P02901W01-M
729
GSR6 (Horizon II)
GTE
Generic Table Editor. The Motorola procedure which allows

users to display and edit MCDF input files.
Guard period
Period at the beginning and end of timeslot during which MS

transmission is attenuated.
GUI
Graphical User Interface. A computer environment or

program that displays, or facilitates the display of, on-screen
options. These options are usually in the form of icons
(pictorial symbols) or menus (lists of alphanumeric
characters) by means of which users may enter commands.
GUI client
A computer used to display a GUI from an OMC-R GUI

application which is being run on a GUI server.
GUI server
A computer used to serve the OMC-R GUI application

process running locally (on its processor) to other computers
(GUI clients or other MMI processors).
GWM
GateWay Manager.
GWY
GateWaY (MSC/LR) interface to PSTN.
H Interface - Hyperframe
730
H Interface
Interface between HLR and AUC.
H-M
Human-Machine Terminals.
HAD, HAP
HLR Authentication Distributor.
Half Rate
Refers to a type of data channel that will double the current

GSM air interface capacity to 16 simultaneous calls per
carrier (see also FR - Full Rate).
HANDO, Handover
HANDOver. The action of switching a call in progress from

one radio channel to another radio channel. Handover allows
established calls to continue by switching them to another
radio resource, as when an MS moves from one BTS area to
another. Handovers may take place between the following
GSM entities: timeslot, RF carrier, cell, BTS, BSS and MSC.
HCU
Hybrid Combining Unit. (Used in Horizonmacro). Part of the

DDF, the HDU allows the outputs of three radios to be
combined into a single antenna.
HDLC
High level Data Link Control. A link-level protocol used to

facilitate reliable point-to-point transmission of a data packet.
Note: A subset of HDLC, LAP-B, is the layer-two protocol for
CCITT Recommendation X.25.
HDSL
High bit-rate Digital Subscriber Line. HDSL is a data

transmission mechanism which supports duplex high speed
digital communication (at E1 rates) on one or more
unshielded twisted pair lines.
HLC
High Layer Compatibility. The HLC can carry information

defining the higher layer characteristics of a teleservice active
on the terminal.
HLR
Home Location Register. The LR where the current location

and all subscriber parameters of an MS are permanently
stored.
HMS
Heat Management System. The system that provides

environmental control of the components inside the ExCell,
TopCell and M-Cell cabinets.
68P02901W01-M
02 May 2003
GSR6 (Horizon II)
HO
HandOver. See HANDO.
HPU
Hand Portable Unit. A handset.
HOLD
Call hold supplementary service. Call hold allows the

subscriber to place a call on hold in order to make another
call. When the second call is completed, the subscriber can
return to the first call.
HPLMN
Home PLMN.
HR
See Half Rate.
HS
HandSet.
HSI/S
High Speed Interface card.
HSM
HLR Subscriber Management.
HSN
Hopping Sequence Number. HSN is a index indicating the

specific hopping sequence (pattern) used in a given cell. It
ranges from 0 to 63.
HT100
Hilly Terrain with the MS travelling at 100 kph. Dynamic model

against which the performance of a GSM receiver can be
measured. See also TU3, TU50, RA250 and EQ50.
HU
Home Units. The basic telecommunication unit as set by the

HPLMN. This value is expressed in the currency of the home
country.
HW
Hardware.
Hybrid Combiner
A combiner device which requires no software control and is

sufficiently broadband to be able to cover the GSM
transmitter frequency band. See also COMB.
Hybrid Transformer
A circuit used in telephony to convert 2-wire operation to

4-wire operation and vice versa. For example, every land-line
telephone contains a hybrid to separate earpiece and
mouthpiece audio and couple both into a 2-wire circuit that
connects the phone to the exchange.
Hyperframe
2048 superframes. The longest recurrent time period of the

frame structure.
Information frames. Part of RLP.
IA
Incoming Access supplementary service. An arrangement

which allows a member of a CUG to receive calls from
outside the CUG.
IA5
International Alphanumeric 5 character set.
IADU
Integrated Antenna Distribution Unit. The IADU is the

equivalent of the Receive Matrix used on BTSs that pre-date
the M-Cell range.
IAM
Initial Address Message. A message sent in the forward

direction that contains (a) address information, (b) the
signaling information required to route and connect a call to
the called line, (c) service-class information, (d) information
relating to user and network facilities, and (e) call-originator
identity or call-receiver identity.
I - IWU

02 May 2003
68P02901W01-M
731
732
GSR6 (Horizon II)
IAS
Internal Alarm System. The IAS is responsible for monitoring

all cabinet alarms at a BSS.
IC
Integrated Circuit. An electronic circuit that consists of many

individual circuit elements, such as transistors, diodes,
resistors, capacitors, inductors, and other active and passive
semiconductor devices, formed on a single chip of
semiconducting material and mounted on a single piece of
substrate material.
IC
Interlock Code. A code which uniquely identifies a CUG within

a network.
IC(pref)
Interlock Code of the preferential CUG.
ICB
Incoming Calls Barred. An access restriction that prevents a

CUG member from receiving calls from other members of
that group.
ICC
Integrated Circuit(s) Card.
ICM
In-Call Modification. Function which allows the service mode

(speech, facsimile, data) to be changed during a call.
ICMP
Internet Control Message Protocol. An extension to the

Internet Protocol (IP) that allows for the generation of error
messages, test packets, and informational messages related
to IP. The PING command, for example, uses ICMP to test an
Internet connection.
ID, Id
IDentification/IDentity/IDentifier.
IDN
Integrated Digital Network. A network that uses both digital

transmission and digital switching.
IDS
Informix Dynamic Server. The OMC-R relational database

management system.
IE
Information Element. The part of a message that contains

configuration or signalling information.
IEC
International Electrotechnical Commission. An international

standards and conformity assessment body for electrical,
electronic and related technologies.
IEEE
Institute of Electrical and Electronic Engineers. A non-profit,

technical professional association.
IEI
Information Element Identifier. The identifier field of the IE.
I-ETS
Interim European Telecommunication Standard.
IF
Intermediate Frequency. A frequency to which a carrier

frequency is shifted as an intermediate step in transmission
or reception.
IFAM
Initial and Final Address Message.
IM
InterModulation. The production, in a nonlinear element of a

system, of frequencies corresponding to the sum and
difference frequencies of the fundamentals and harmonics
thereof that are transmitted through the element.
IMACS
Intelligent Monitor And Control System.
IMEI
International Mobile station Equipment Identity. Electronic

serial number that uniquely identifies the MS as a piece or
assembly of equipment. The IMEI is sent by the MS along
with request for service. See also IMEISV.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
IMEISV
International Mobile station Equipment Identity and Software

Version number. The IMEISV is a 16 digit decimal number
composed of four elements:
- a 6 digit Type Approval Code;
- a 2 digit Final Assembly Code;
- a 6 digit Serial Number; and
- a 2 digit Software Version Number (SVN).
The first three elements comprise the IMEI. When the
network requests the IMEI from the MS, the SVN (if present)
is also sent towards the network. See also IMEI and SVN.
IMM
IMMediate assignment message. IMMs are sent from the

network to the MS to indicate that the MS must immediately
start monitoring a specified channel.
IMSI
International Mobile Subscriber Identity. Published mobile

number (prior to ISDN) that uniquely identifies the
subscription. It can serve as a key to derive subscriber
information such as directory number(s) from the HLR. See
also MSISDN.
IN
Intelligent Network. A network that allows functionality to be

distributed flexibly at a variety of nodes on and off the
network and allows the architecture to be modified to control
the services.
IN
Interrogating Node. A switching node that interrogates an

HLR, to route a call for an MS to the visited MSC.
INS
IN Service.
INS
Intelligent Network Service. A service provided using the

capabilities of an intelligent network. See also IN.
InterAlg
Interference Algorithm.
Intermittent
Intermittent alarms are transient and not usually associated

with a serious fault condition. After the intermittent alarms are
displayed in the Alarm window, the operator must handle and
clear the alarm. The system will report every occurrence of an
intermittent alarm unless it is throttled. See also FMIC and
OIC.
Interworking
The general term used to describe the inter-operation of

networks, services, supplementary services and so on. See
also IWF.
Interval
A recording period of time in which a statistic is pegged.
Interval expiry
The end of an interval.
I/O
Input/Output.
IOS
Intelligent Optimization Service. Tool for improving the

network quality. The IOS generates reports based on
performance data from the BTS and OMC-R.
IP
Initialisation Process. The IP is primarily responsible for

bringing up the site from a reset, including code loading the
site from a suitable code source. IP also provides the CSFP
functionality, allowing two BSS code load version to be
swapped very quickly, allowing the site to return to service as
soon as possible.

02 May 2003
68P02901W01-M
733
734
GSR6 (Horizon II)
IP
Internet Protocol. A standard protocol designed for use in

interconnected systems of packet-switched computer
communication networks. IP provides for transmitting blocks
of data called datagrams from sources to destinations, where
sources and destinations are hosts identified by fixed-length
addresses. The internet protocol also provides for
fragmentation and reassembly of long datagrams, if
necessary, for transmission through small-packet networks.
See also TCP and TCP/IP.
IPC
Inter-Process Communication. Exchange of data between

one process and another, either within the same computer or
over a network.
IP, INP
INtermodulation Products. Distortion. A type of spurious

emission.
IPR
Intellectual PRoperty.
IPSM
Integrated Power Supply Module (-48 V).
IPX
Internetwork Packet EXchange A networking protocol used

by the Novell NetWare operating systems. Like UDP/IP, IPX
is a datagram protocol used for connectionless
communications. Higher-level protocols are used for
additional error recovery services.
Iridium
A communications system comprising a constellation of 66

low-earth-orbiting (LEO) satellites forming a mobile wireless
system allowing subscribers to place and receive calls from
any location in the world. The satellite constellation is
connected to existing terrestrial telephone systems through a
number of gateway ground-stations.
ISAM
Indexed Sequential Access Method. A method for managing

the way a computer accesses records and files stored on a
hard disk. While storing data sequentially, ISAM provides
direct access to specific records through an index. This
combination results in quick data access regardless of
whether records are being accessed sequentially or randomly.
ISC
International Switching Centre. The ISC routes calls to/from

other countries.
ISDN
Integrated Services Digital Network. A digital network using

common switches and digital transmission paths to establish
connections for various services such as telephony, data
telex, and facsimile. See also B channel and D channel.
ISG
Motorola Information Systems group (formerly CODEX).
ISO
International Organisation for Standardization. ISO is a

world-wide federation of national standards bodies from some
130 countries, one from each country.
ISQL
An Interactive Structured Query Language client application

for the database server. See also IDS.
ISS
Integrated Support Server. The ISS resides on a Sun Netra

t 1125 and performs the CGF, DNS, NTP, and NFS functions
for the GSN.
ISUP
ISDN User Part. An upper-layer application supported by

signalling system No. 7 for connection set up and tear down.
IT
Inactivity Test (Part of SCCP network connectivity).

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
ITC
Information Transfer Capability. A GSM Bearer Capability

Element which is provided on the Dm channel to support
Terminal adaptation function to Interworking control
procedures.
ITU
International Telecommunication Union. An intergovernmental

organization through which public and private organizations
develop telecommunications. It is responsible for adopting
international treaties, regulations and standards governing
telecommunications.
ITU-T
International Telecommunication Union - Telecommunications

Standardization Sector. The standardization functions were
formerly performed by CCITT, a group within the ITU.
IWF
InterWorking Function. A network functional entity which

provides network interworking, service interworking,
supplementary service interworking or signalling interworking.
It may be a part of one or more logical or physical entities in a
GSM PLMN.
IWMSC
InterWorking MSC. MSC that is used to deliver data to/from

SGSN.
IWU
InterWorking Unit. Unit where the digital to analogue (and

visa versa) conversion takes place within the digital GSM
network.
kilo (103).
Windows size.
Constraint length of the convolutional code.
KAIO
Kernel Asynchronous Input/Output. Part of the OMC-R

relational database management system.
kb, kbit
kilo-bit.
kbit/s, kbps
kilo-bits per second.
kbyte
kilobyte. 210 bytes = 1024 bytes
Kc
Ciphering key. A sequence of symbols that controls the

operation of encipherment and decipherment.
kHz
kilo-Hertz.
Ki
Individual subscriber authentication Key. Part of the

authentication process of the AUC.
KIO
A class of processor.
KSW
Kiloport SWitch board. TDM timeslot interchanger to connect

calls. Part of the BSS.
KSWX
KSW Expander half size board. Fibre optic distribution of

TDM bus. Part of the BSS.
kW
kilo-Watt.
L1
Layer 1 (of a communications protocol).
L2
k - KW
L1 - LV

02 May 2003
68P02901W01-M
735
736
GSR6 (Horizon II)
L2ML
Layer 2 Management Link. L2ML is used for transferring layer

2 management messages to TRX or BCF. One link per TRX
and BCF.
L2R
Layer 2 Relay function. A function of an MS and IWF that

adapts a users known layer 2 protocol LAPB onto RLP for
transmission between the MT and IWF.
L2R BOP
L2R Bit Orientated Protocol.
L2R COP
L2R Character Orientated Protocol.
L3
LA
Location Area. An area in which an MS may move freely

without updating the location register. An LA may comprise
one or several base station areas.
LAC
Location Area Code. The LAC is part of the LAI. It is an

operator defined code identifying the location area.
LAI
Location Area Identity. The information indicating the location

area in which a cell is located. The LAI data on the SIM is
continuously updated to reflect the current location of the
subscriber.
LAN
Local Area Network. A data communications system that (a)

lies within a limited spatial area, (b) has a specific user group,
(c) has a specific topology, and (d) is not a public switched
telecommunications network, but may be connected to one.
LANX
LAN Extender half size board. Fibre optic distribution of LAN

to/from other cabinets. Part of BSS, etc.
LAPB
Link Access Protocol Balanced. The balanced-mode,

enhanced version of HDLC. Used in X.25 packet-switching
networks.
LAPD
Link Access Protocol D-channel (Data). A protocol that operates

at the data link layer (layer 2) of the OSI architecture. LAPD is
used to convey information between layer 3 entities across the
frame relay network. The D-channel carries signalling
information for circuit switching.
LAPDm
Link Access Protocol on the Dm channel. A link access

procedure (layer 2) on the CCH for the digital mobile
communications system.
Layer 1
See OSI-RM and Physical Layer.
Layer 2
See OSI-RM and Data Link Layer.
Layer 3
See OSI-RM and Network Layer.
Layer 4
See OSI-RM and Transport Layer.
Layer 5
See OSI-RM and Session Layer.
Layer 6
See OSI-RM and Presentation Layer.
Layer 7
See OSI-RM and Application Layer.
LC
Inductor Capacitor. A type of filter.
LCF
Link Control Function. LCF GPROC controls various links in

and out of the BSC. Such links include MTL, XBL, OMF and
RSL. See also LCP.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
LCN
Local Communications Network. A communication network

within a TMN that supports data communication functions
(DCFs) normally at specified reference points q1 and q2.
LCNs range from the simple to the complex. LCN examples
include point-to-point connections and networks based on
star and bus topologies.
LCP
Link Control Processor. An LCP is a GPROC or PCMCIA

board device which supplies the LCF. Once the LCF has been
equipped, and assuming GPROCs have been equipped,
processors are allocated by the software.
LE
Local Exchange.
LED
Light Emitting Diode. A type of diode that emits light when

current passes through it. Depending on the material used the
colour can be visible or infrared.
LF
Line Feed. A code that moves the cursor on a display screen

down one line. In the ASCII character set, a line feed has a
decimal value of 10. On printers, a line feed advances the
paper one line.
LI
Length Indicator. Delimits LLC PDUs within the RLC data

block, when an LLC PDU boundary occurs in the block.
LI
Line Identity. The LI is made up of a number of information

units: the subscribers national ISDN/MSISDN number; the
country code; optionally, subaddress information. In a full
ISDN environment, the line identity includes all of the address
information necessary to unambiguously identify a subscriber.
The calling line identity is the line identity of the calling party.
The connected line identity is the line identity of the
connected party.
LLC
Lower Layer Compatibility. The LLC can carry information

defining the lower layer characteristics of the terminal.
Lm
Traffic channel with capacity lower than a Bm.
LMP
LAN Monitor Process. Each GPROC which is connected to a

LAN has an LMP, which detects faults on the LAN. LAN
alarms are generated by the GPROC.
LMS
Least Mean Squares. Parameters determined by minimizing

the sum of squares of the deviations.
LMSI
Local Mobile Station Identity. A unique identity temporarily

allocated to visiting mobile subscribers in order to speed up
the search for subscriber data in the VLR, when the MSRN
allocation is done on a per cell basis.
LMT
Local Maintenance Terminal. Diagnostic tool, typically an IBM

compatible PC.
LNA
Low Noise Amplifier. An amplifier with low noise

characteristics.
LND
Last Number Dialled.
Location area
An area in which a mobile station may move freely without

updating the location register. A location area may comprise
one or several base station areas.

02 May 2003
68P02901W01-M
737
GSR6 (Horizon II)
LPC
Linear Predictive Coding. A method of digitally encoding

analog signals. It uses a single-level or multi-level sampling
system in which the value of the signal at each sample time is
predicted to be a linear function of the past values of the
quantified signal.
LPLMN
Local PLMN.
LR
Location Register. The GSM functional unit where MS

location information is stored. The HLR and VLR are location
registers.
LSSU
Link Stations Signalling Unit (Part of MTP transport system).
LSTR
Listener Side Tone Rating. A rating, expressed in dB, based

on how a listener will perceive the background noise picked
up by the microphone.
LTA
Long Term Average. The value required in a BTSs GCLK

frequency register to produce a 16.384 MHz clock.
LTE
Local Terminal Emulator.
LTP
Long Term Predictive.
LTU
Line Terminating Unit.
LU
Local Units.
LU
Location Update. A location update is initiated by the MS

when it detects that it has entered a new location area.
LV
Length and Value.
Mandatory.
Mega (106).
M-Cell
Motorola Cell.
M&TS
Maintenance and TroubleShooting. Functional area of

Network Management software which (1) collects and
displays alarms, (2) collects and displays Software/Hardware
errors, and (3) activates test diagnostics at the NEs (OMC).
MA
Mobile Allocation. The radio frequency channels allocated to

an MS for use in its frequency hopping sequence.
MAC
Medium Access Control. MAC includes the functions related

to the management of the common transmission resources.
These include the packet data physical channels and their
radio link connections. Two Medium Access Control modes
are supported in GSR5, dynamic allocation and fixed
allocation.
MACN
Mobile Allocation Channel Number. See also MA.
Macrocell
A cell in which the base station antenna is generally mounted

away from buildings or above rooftop level.
MAF
Mobile Additional Function.
MAH
Mobile Access Hunting supplementary service. An automatic

service which searches for the first available mobile user out
of a defined group.
MAI
Mobile Allocation Index.
M - MUX
738

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
MAIDT
Mean Accumulated Intrinsic Down Time.
MAINT
MAINTenance.
MAIO
Mobile Allocation Index Offset. The offset of the mobile

hopping sequence from the reference hopping sequence of
the cell.
MAP
Mobile Application Part (part of SS7 standard). The

inter-networking signalling between MSCs and LRs and EIRs.
MAPP
Mobile Application Part Processor.
MB, Mbyte
Megabyte. 220 bytes = 1,048,576 bytes = 1024 kilobytes.
Mbit/s
Megabits per second.
MCAP
Motorola Cellular Advanced Processor. The MCAP Bus is the

inter-GPROC communications channel in a BSC. Each card
cage in a BSC needs at least one GPROC designated as an
MCAP Server.
MCC
Mobile Country Code. The first three digits of the IMSI, used
to identify the country.
MCDF
Motorola Customer Data Format used by DataGen for simple

data entry and retrieval.
MCI
Malicious Call Identification supplementary service. This

feature is supported by a malicious call trace function by
printing the report at the terminating MSC when the mobile
subscriber initiates a malicious call trace request.
MCSC
Motorola Customer Support Centre.
MCU
Main Control Unit for M-Cell2/6. Also referred to as the Micro

Control Unit in software.
MCUF
Main Control Unit, with dual FMUX. (Used in M-Cellhorizon).
MCU-m
Main Control Unit for M-Cellmicro sites (M-Cellm). Also

referred to as the Micro Control Unit in software.
MCUm
The software subtype representation of the Field Replaceable

Unit (FRU) for the MCU-m.
MD
Mediation Device. The MD (which handles the Q3 interface)

allows the OSI Processor to communicate between the
Network Management Centre (NMC) and OMC-R for network
configuration, events and alarms.
MDL
mobile Management entity - Data Link layer.
ME
Maintenance Entity (GSM Rec. 12.00).
ME
Mobile Equipment. Equipment intended to access a set of

GSM PLMN and/or DCS telecommunication services, but
which does not contain subscriber related information.
Services may be accessed while the equipment, capable of
surface movement within the GSM system area, is in motion
or during halts at unspecified points.
MEF
Maintenance Entity Function (GSM Rec. 12.00). A function

which possesses the capability to detect elementary anomalies
and convey them to the supervision process.
MF
MultiFrame. In PCM systems, a set of consecutive frames in

which the position of each frame can be identified by
reference to a multiframe alignment signal.

02 May 2003
68P02901W01-M
739
740
GSR6 (Horizon II)
MF
Multi-Frequency (tone signalling type). See DTMF.
MF
MultiFunction block.
MGMT, mgmt
Management.
MGR
Manager.
MHS
Message Handling System. The family of services and

protocols that provides the functions for global electronic-mail
transfer among local mail systems.
MHS
Mobile Handling Service.
MHz
Mega-Hertz (106).
MI
MIB
Management Information Base. A Motorola OMC-R

database. There is a CM MIB and an EM MIB.
MIC
Mobile Interface Controller.
Microcell
A cell in which the base station antenna is generally mounted

below rooftop level. Radio wave propagation is by diffraction
and scattering around buildings, the main propagation is
within street canyons.
min
minute(s).
ms
micro-second (10-6).
mBCU
Micro Base Control Unit. The mBCU is the Macro/Microcell

implementation of a BTS site controller.
MIT
Management Information Tree. A file on the Motorola

OMC-R. The MIT file effectively monitors data on every
device and every parameter of each device that is in the
current versions of software on the OMC-R. The data is
stored as a text file on the OMC-R. The MIT file also contains
the hierarchical relationships between the network devices.
MM
Man Machine. See MMI.
MM
Mobility Management. MM functions include authorization,

location updating, IMSI attach/detach, periodic registration, ID
confidentiality, paging, handover, etc.
MME
Mobile Management Entity.
MMF
Middle Man Funnel process.
MMI
Man Machine Interface. The method by which the user

interfaces with the software to request a function or change
parameters. The MMI may run on a terminal at the OMC, or
an LMT. The MMI is used to display alarm reports, retrieve
device status, take modules out of service and put modules
into service.
MMI client
A machine configured to use the OMC-R software from an

MMI server.
MMI processor
MMI client/MMI server.
MMI server
A computer which has its own local copy of the OMC-R

software. It can run the OMC-R software for MMI clients to
mount.
MML
Man Machine Language. The tool of MMI.
MMS
Multiple Serial Interface Link. (see also 2Mbit/s link)

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
MNC
Mobile Network Code. The fourth, fifth and optionally sixth

digits of the IMSI, used to identify the network.
MNT
MaiNTenance.
MO
Mobile Originated.
MO/PP
Mobile Originated Point-to-Point messages. Transmission of a

SMS from a mobile to a message handling system. The
maximum length of the message is 160 characters. The
message can be sent whether or not the MS is engaged in a
call.
MOMAP
Motorola OMAP.
MoU
Memorandum of Understanding. Commercial term. An MoU

usually sets out the broad parameters of an understanding as
well as the general responsibilities and obligations of each
party in a proposed venture. It has little legal significance
except to indicate the parties commitments and acts as an
aid to interpreting the parties intentions. There are various
types of MOUs: compliance MOUs help ensure that all
Motorola units comply with applicable laws and regulations;
intellectual property MOUs deal with copyright, trademark,
and patent rights; and business arrangement MOUs relate to
the terms and conditions of a product or service transfer.
MPC
Multi Personal Computer (was part of the OMC).
MPH
(mobile) Management (entity) - PHysical (layer) [primitive].
MPTY
MultiParTY (Multi ParTY) supplementary service. MPTY

provides a mobile subscriber with the ability to have a
multi-connection call, i.e. a simultaneous communication with
more than one party.
MPX
MultiPleXed.
MRC
Micro Radio Control Unit.
MRN
Mobile Roaming Number.
MRP
Mouth Reference Point. Facility for assessing handset and

headset acoustic responses.
MS
Mobile Station. The GSM subscriber unit. A subscriber

handset, either mobile or portable, or other subscriber
equipment, such as facsimile machines, etc.
MSC
Mobile-services Switching Centre, Mobile Switching Centre.

The MSC handles the call set up procedures and controls the
location registration and handover procedures for all except
inter-BTS, inter-cell and intra-cell handovers. MSC controlled
inter-BTS handovers can be set as an option at the switch.
MSCM
Mobile Station Class Mark.
MSCU
Mobile Station Control Unit.
msec
millisecond (.001 second).
MSI
Multiple Serial Interface board. Intelligent interface to two

2 Mbit/s digital links. See 2 Mbit/s link and DS-2. Part of BSS.
MSIN
Mobile Station Identification Number. The part of the IMSI

identifying the mobile station within its home network.

02 May 2003
68P02901W01-M
741
742
GSR6 (Horizon II)
MSISDN
Mobile Station International ISDN Number. Published mobile

number (see also IMSI). Uniquely defines the mobile station
as an ISDN terminal. It consists of three parts: the Country
Code (CC), the National Destination Code (NDC) and the
Subscriber Number (SN).
MSRN
Mobile Station Roaming Number. A number assigned by the

MSC to service and track a visiting subscriber.
MSU
Message Signal Unit (Part of MTP transport system). A

signal unit containing a service information octet and a
signalling information field which is retransmitted by the
signalling link control, if it is received in error.
MT
Mobile Terminated. Describes a call or short message

destined for an MS.
MT (0, 1, 2)
Mobile Termination. The part of the MS which terminates the

radio transmission to and from the network and adapts
terminal equipment (TE) capabilities to those of the radio
transmission. MT0 is mobile termination with no support for
terminal, MT1 is mobile termination with support for an S-type
interface and MT2 is mobile termination with support for an
R-type interface.
MTBF
Mean Time Between Failures. An indicator of expected

system reliability calculated on a statistical basis from the
known failure rates of various components of the system.
MTBF is usually expressed in hours.
MTL
Message Transfer Link. The MTL is the 64 kbit/s PCM

timeslot that is used to convey the SS7 signalling information
on the A interface between the MSC and the BSC.
MTM
Mobile-To-Mobile (call).
MTP
Message Transfer Part. The part of a common-channel

signaling system that transfers signal messages and
performs associated functions, such as error control and
signaling link security.
MT/PP
Mobile Terminated Point-to-Point messages. Transmission of

a short message from a message handling system to a
mobile. The maximum length of the message is 160
characters. The message can be received whether or not the
MS is engaged in a call.
MTTR
Mean Time To Repair. The total corrective maintenance time

divided by the total number of corrective maintenance actions
during a given period of time.
Multiframe
Two types of multiframe are defined in the system: a

26-frame multiframe with a period of 120 ms and a 51-frame
multiframe with a period of 3060/13 ms.
MU
Mark Up.
MUMS
Multi User Mobile Station.
MUX
Multiplexer. A device that combines multiple inputs into an

aggregate signal to be transported via a single transmission
channel.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
NACK - nW
NACK, Nack
No Acknowledgement
N/W
Network.
NB
Normal Burst (see Normal burst).
NBIN
A parameter in the frequency hopping sequence generation

algorithm.
NCC
Network Colour Code. The NCC and the BCC are part of the
BSIC. The NCC comprises three bits in the range 000 to 111.
It is the same as the PLMN Colour Code. See also NCC and
BSIC.
NCELL
Neighbouring (of current serving) Cell.
NCH
Notification CHannel. Part of the downlink element of the

CCCH reserved for voice group and/or voice broad-cast calls
and notification messages.
ND
No Duplicates. A database column attribute meaning the

column contains unique values (used only with indexed
columns).
NDC
National Destination Code. Part of the MSISDN. An NDC is

allocated to each GSM PLMN.
NDUB
Network Determined User Busy. An NDUB condition occurs

when a call is about to be offered and the maximum number
of total calls for the channel has been reached. In practice,
the total number of calls could be three: one for the basic call,
one for a held call and one for call waiting.
NE
Network Element (Network Entity). A piece of

telecommunications equipment that provides support or
services to the user.
NEF
Network Element Function block. A functional block that

communicates with a TMN for the purpose of being
monitored, or controlled, or both.
NET
Norme Europennes de Telecommunications.
NetPlan
An RF planning tool, NetPlan can import data from the OMC

and use it to carry out a network frequency replan.
Network Layer
See OSI RM. The Network Layer responds to service

requests from the Transport Layer and issues service
requests to the Data Link Layer. It provides the functional
and procedural means of transferring variable length data
sequences from a source to a destination via one or more
networks while maintaining the quality of service requested by
the Transport Layer. The Network Layer performs network
routing, flow control, segmentation/desegmentation, and error
control functions.
NF
Network Function.
NFS
Network File System. A file system that is distributed over a

computer network. Also, a file system, on a single computer,
that contains the low-level networking files for an entire
network.

02 May 2003
68P02901W01-M
743
744
GSR6 (Horizon II)
NHA
Network Health Analyst. The NHA is an optional feature. It

detects problems by monitoring network statistics and events
via the OMC-R. The NHA analyses the event history,
statistics and network configuration data to try to determine
the cause of the detected problems.
NIC
Network Interface Card. A network interface device in the

form of a circuit card that provides network access.
NIC
Network Independent Clocking.
NIS
Network Information Service. It allows centralised control of

network information for example hostnames, IP addresses
and passwords.
N-ISDN
Narrowband Integrated Services Digital Network: Services

include basic rate interface (2B+D or BRI) and primary rate
interface (30B+D - Europe and 23B+D - North America or
PRI). Supports narrowband speeds at/or below 1.5 Mbps.
NIU
Network Interface Unit. A device that performs interface

functions, such as code conversion, protocol conversion, and
buffering, required for communications to and from a network.
NIU-m
Network Interface Unit, micro. M-Cellmicro MSI.
NL
See Network Layer.
NLK
Network LinK processor(s).
Nm
Newton metres.
NM
Network Management (manager). NM is all activities which

control, monitor and record the use and the performance of
resources of a telecommunications network in order to
provide telecommunication services to customers/users at a
certain level of quality.
NMASE
Network Management Application Service Element.
NMC
Network Management Centre. The NMC node of the GSM

TMN provides global and centralised GSM PLMN monitoring
and control, by being at the top of the TMN hierarchy and
linked to subordinate OMC nodes.
NMSI
National Mobile Station Identification number, or, National

Mobile Subscriber Identity. The NMSI consists of the MNC
and the MSIN.
NMT
Nordic Mobile Telephone system. NMT produced the worlds

first automatic international mobile telephone system.
NN
No Nulls. A database column attribute meaning the column

must contain a value in all rows.
Normal burst
A period of modulated carrier less than a timeslot.
NPI
Number Plan Identifier.
NRZ
Non Return to Zero. A code in which ones are represented by

one significant condition and zeros are represented by
another, with no neutral or rest condition.
NSAP
Network Service Access Point. An NSAP is a registration

made by an application which specifies its desired listening
criteria. The registration is limited to a particular CPU and port
number. Criteria can include: DNICs, national numbers,
subaddress ranges, protocol-ids, and extended addresses.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
NSP
Network Service Provider. A national or regional company

that owns or maintains a portion of the network and resells
connectivity.
NSS
Network Status Summary. A feature of the OMC-R MMI,

which provides different network maps giving visual indication
of the network configuration and performance, and how the
different network management functions are implemented by
the OMC-R.
NST
Network Service Test(er). A PCU process that periodically

tests all alive NS-VCs on a PICP board.
NS-VC
Network Service - Virtual Circuit.
NT
Network Termination. Network equipment that provides

functions necessary for network operation of ISDN access
protocols.
NT
Non Transparent.
NTAAB
NTRAC Type Approvals Advisory Board. Committee engaged

in harmonisation type approval of telecom terminals in
Europe.
NTP
Network Time Protocol. A protocol built on top of TCP/IP that

assures accurate local timekeeping with reference to radio,
atomic or other clocks located on the Internet. This protocol is
capable of synchronizing distributed clocks within
milliseconds over long time periods.
Numbers
# - The symbol used for number.

2 Mbit/s link - As used in this manual set, the term applies to
the European 4-wire 2.048 Mbit/s digital line or link which can
carry 30 A-law PCM channels or 120 16 kbit/s GSM
channels.
4GL - 4th Generation Language. Closer to human languages
than typical high-level programming languages. most 4GLs
are used to access databases.
NUA
Network User Access.
NUI
Network User Identification.
NUP
National User Part. (part of SS7).
NV
NonVolatile.
NVRAM
Non-Volatile Random Access Memory. Static random access

memory which is made into non-volatile storage either by
having a battery permanently connected, or, by saving its
contents to EEPROM before turning the power off and
reloading it when power is restored.
nW
Nano-Watt (10-9).
Optional.
OA
Outgoing Access supplementary service. An arrangement

which allows a member of a CUG to place calls outside the
CUG.
OA&M
Operation, Administration, & Management.
OAMP
Operation, Administration, Maintenance, and Provisioning.
O - Overlap

02 May 2003
68P02901W01-M
745
746
GSR6 (Horizon II)
O&M
Operations and Maintenance.
OASCU
Off-Air-Call-Set-Up. The procedure in which a

telecommunication connection is being established whilst the
RF link between the MS and the BTS is not occupied.
OCB
Outgoing Calls Barred within the CUG supplementary service.

An access restriction that prevents a CUG member from
placing calls to other members of that group.
OCXO
Oven Controlled Crystal Oscillator. High stability clock source

used for frequency synchronization.
OD
Optional for operators to implement for their aim.
OFL
% OverFlow.
offline
IDS shutdown state.
online
IDS normal operating state.
OIC
Operator Initiated Clear. An alarm type. OIC alarms must be

cleared by the OMC-R operator after the fault condition that
caused the alarm is resolved. See also FMIC and
Intermittent.
OLM
Off_Line MIB. A Motorola DataGen database, used to modify

and carry out Radio Frequency planning on multiple BSS
binary files.
OLR
Overall Loudness Rating.
OMAP
Operations and Maintenance Application Part (part of SS7

standard) (was OAMP).
OMC
Operations and Maintenance Centre. The OMC node of the

GSM TMN provides dynamic O&M monitoring and control of
the PLMN nodes operating in the geographical area
controlled by the specific OMC.
OMC-G
Operations and Maintenance Centre Gateway Part.

(Iridium)
OMC-G
Operations and Maintenance Centre GPRS Part.
OMC-R
Operations and Maintenance Centre Radio Part.
OMC-S
Operations and Maintenance Centre Switch Part.
OMF
Operations and Maintenance Function (at BSC).
OML
Operations and Maintenance Link. The OML provides

communication between an OMC-R and a BSC or RXCDR
for transferring network management (O&M) data.
OMP
Operation and Maintenance Processor. Part of the BSC.
OMS
Operation and Maintenance System (BSC-OMC).
OMSS
Operation and Maintenance SubSystem.
OOS
Out Of Service. Identifies a physical state. The OOS state

indicates the physical device is out of service. This state is
reserved for physical communication links. Also, identifies a
telephony state. The OOS state is used by the BTS device
software to indicate that the BTS is completely out of service.
OPC
Originating Point Code. A part of the label in a signalling

message that uniquely identifies, in a signalling network, the
(signalling) origination point of the message.
ORAC
Olympus Radio Architecture Chipset.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
OS
Operating System. The fundamental program running on a

computer which controls all operations.
OSI
Open Systems Interconnection. The logical structure for

communications networks standardized by the ISO. The
standard enables any OSI-compliant system to communicate
and exchange information with any other OSI-compliant
system.
OSI RM
OSI Reference Model. An abstract description of the digital

communications between application processes running in
distinct systems. The model employs a hierarchical structure
of seven layers. Each layer performs value-added service at
the request of the adjacent higher layer and, in turn, requests
more basic services from the adjacent lower layer:
Layer 1 - Physical Layer,
Layer 2 - Data Link Layer,
Layer 3 - Network Layer,
Layer 4 - Transport Layer,
Layer 5 - Session Layer,
Layer 6 - Presentation Layer,
Layer 7 - Application Layer.
OSF
Operation Systems Function block.
OSF/MOTIF
Open Software Foundation Motif. The basis of the GUI used

for the Motorola OMC-R MMI.
OSS
Operator Services System.
Overlap
Overlap sending means that digits are sent from one system
to another as soon as they are received by the sending
system. A system using ~ will not wait until it has received all
digits of a call before it starts to send the digits to the next
system. This is the opposite of en bloc sending where all
digits for a given call are sent at one time. See en bloc.
PA
Power Amplifier.
PAB
Power Alarm Board. Part of the BSS.
PABX
Private Automatic Branch eXchange. A private automatic

telephone exchange that allows calls within the exchange and
also calls to and from the public telephone network.
Packet
A sequence of binary digits, including data and control

signals, that is transmitted and switched as a composite
whole.
Packet Switching
The process of routing and transferring data by means of

addressed packets so that a channel is occupied during the
transmission of the packet only, and upon completion of the
transmission the channel is made available for the transfer of
other traffic.
PAD
Packet Assembler/Disassembler facility. A hardware device

that allows a data terminal that is not set up for packet
switching to use a packet switching network. It assembles
data into packets for transmission, and disassembles the
packets on arrival.
PA - PXPDN

02 May 2003
68P02901W01-M
747
748
GSR6 (Horizon II)
Paging
The procedure by which a GSM PLMN fixed infrastructure

attempts to reach an MS within its location area, before any
other network-initiated procedure can take place.
PATH
CEPT 2 Mbit/s route through the BSS network.
PBUS
Processor Bus.
PBX
Private Branch eXchange. In the general use of the term,

PBX is a synonym for PABX. However, a PBX operates with
only a manual switchboard; a private automatic exchange
(PAX) does not have a switchboard, a private automatic
branch exchange (PABX) may or may not have a
switchboard.
PC
Personal Computer. A general-purpose single-user

microcomputer designed to be operated by one person at a
time.
pCA
PCU Central Authority. One pCA software process is located

at every PCU. The CA is in control of the PCU. It is resident
on the master DPROC (MPROC) only, and maintains a list of
the status of every device and every software process at the
site.
PCH
Paging CHannel. A common access RF channel providing

point-to-multipoint unidirectional signaling downlink. Provides
simultaneous transmission to all MSs over a wide paging
area.
PCHN
Paging Channel Network.
PCHN
Physical Channel. The physical channel is the medium over

which the information is carried. In the case of GSM radio
communications this would be the Air Interface. Each RF
carrier consists of eight physical channels (or timeslots) used
for MS communications. In the case of a terrestrial interface
the physical channel would be cable. See also Physical
Layer.
PCI
Packet Control Interface.
PCI
Peripheral Component Interconnect. A standard for

connecting peripherals to a personal computer, PCI is a 64-bit
bus, though it is usually implemented as a 32-bit bus.
PCM
Pulse Code Modulation. Modulation in which a signal is

sampled, and the magnitude (with respect to a fixed
reference) of each sample is quantized and converted by
coding to a digital signal. Provides undistorted transmission,
even in the presence of noise. See also 2 Mbit/s link, which is
the physical bearer of PCM.
pCM
PCU Configuration Management. pCM is a GWM process. It

distributes all database changes performed at the BSC to the
PCU boards.
PCN
Personal Communications Network. Any network supporting

PCS, but in particular DCS1800.
PCR
Preventative Cyclic Retransmission. A form of error

correction suitable for use on links with long transmission
delays, such as satellite links.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
PCS
The U.S. Federal Communications Commission (FCC) term

used to describe a set of digital cellular technologies being
deployed in the U.S. PCS works over GSM, CDMA (also
called IS-95), and North American TDMA (also called IS-136)
air interfaces.
PCS System
Personal Communications Services System. In PCS, a

collection of facilities that provides some combination of
personal mobility, terminal mobility, and service profile
management. Note: As used here, facilities includes
hardware, software, and network components such as
transmission facilities, switching facilities, signalling facilities,
and databases.
PCS1900
A cellular phone network using the higher frequency range

allocated in countries such as the USA. It operates on the
frequency range, 1850 - 1910 MHz (receive) and
1930 - 1990 MHz (transmit).
PCU
Packet Control Unit. A BSS component that provides GPRS

with packet scheduling over the air interface with the MS, and
packet segmentization and packetization across the Frame
Relay link with the SGSN.
PCU
Picocell Control unit. Part of M-Cellaccess.
pd
Potential difference. Voltage.
PD
Protocol Discriminator field. The first octet of the packet

header that identifies the protocol used to transport the frame.
PD
Public Data. See PDN.
PDB
Power Distribution Board.
PDCH
Packet Data Channel. PDCH carries a combination of

PBCCH and PDTCH logical channels.
PDF
Power Distribution Frame (MSC/LR).
PDN
Public Data Network. A network established and operated by

a telecommunications administration, or a recognized private
operating agency, for the specific purpose of providing data
transmission services for the public.
PDTCH
Packet Data Traffic Channels
PDU
Power Distribution Unit. The PDU consists consisting of the

Alarm Interface Board (AIB) and the Power Distribution Board
(PDB).
PDU
Protected Data Unit.
PDU
Protocol Data Unit. A term used in TCP/IP to refer to a unit of

data, headers, and trailers at any layer in a network.
PEDC
Pan-European Digital Cellular network. The GSM network in

Europe.
Peg
A single incremental action modifying the value of a statistic.

Also, A number indicating the use of a device or resource.
Each time the device or resource is used the peg count is
incremented.
Pegging
Modifying a statistical value.
pFCP
PCU Fault Collection Process. See pFTP.

02 May 2003
68P02901W01-M
749
750
GSR6 (Horizon II)
pFTP
PCU Fault Transaction Process. The pFTP resides on the

PSP as part of the GWM Functional Unit process. All alarms
at the PCU are reported to pFTP. All DPROCs and the
MPROC have a local pFCP to handle Software Fault
Management indications (SWFMs). The pFTP forwards
alarms to the Agent at the BSC and generates messages to
pCA for device transitions as needed, based on faults
reported.
PGSM
Primary GSM. PGSM operates on the standard GSM

frequency range, 890 - 915 MHz (receive) and 935 - 960 MHz
(transmit).
PH
Packet Handler. A packet handler assembles and

disassembles packets.
PH
PHysical (layer). See Physical Layer.
PHI
Packet Handler Interface.
Physical Layer
See OSI-RM. The Physical Layer is the lowest of seven

hierarchical layers. It performs services requested by the
Data Link Layer. The major functions and services of the
layer are: (a) establishment and termination of a connection
to a communications medium; (b) participation in the process
of sharing communication resources among multiple users;
and, (c) conversion between the representation of digital data
in user equipment and the corresponding signals transmitted
over a communications channel.
PI
Presentation Indicator. The PI forms part of the calling name

information. Depending on database settings, the PI may
prevent the called party from seeing the identity of the calling
party.
Picocell
A cell site where the base station antenna is mounted within a

building.
PICP
Packet Interface Control Processor. A PCU hardware

component, the PICP is a DPROC board used for network
interfacing functions such as SGSN and BSC.
PICS
Protocol Implementation Conformance Statement. A

statement made by the supplier of an implementation or
system claimed to conform to a given specification, stating
which capabilities have been implemented.
PID
Process IDentifier/Process ID.
PIM
PCM Interface Module (MSC).
PIN
Personal Identification Number. A password, typically four

digits entered through a telephone keypad.
PIN
Problem Identification Number.
PIX
Parallel Interface Extender half size board. Customer alarm

interface, part of the BSS. The PIX board provides a means
of wiring alarms external to the BSS, BSC, or BTS into the
base equipment.
PIXT or PIXIT
Protocol Implementation eXtra information for Testing. A

statement made by a supplier or implementor of an
implementation under test (IUT) which contains information
about the IUT and its testing environment which will enable a
test laboratory to run an appropriate test suite against the
IUT.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
PK
Primary Key. A database column attribute, the primary key is

a not-null, non-duplicate index.
PL
See Presentation Layer.
Plaintext
Unciphered data.
PlaNET
Frequency planning tool.
PLL
Phase Lock Loop (refers to phase locking the GCLK in the

BTS). PLL is a mechanism whereby timing information is
transferred within a data stream and the receiver derives the
signal element timing by locking its local clock source to the
received timing information.
PLMN
Public Land Mobile Network. The mobile communications

network.
PM
Performance Management. An OMC application. PM

enables the user to produce reports specific to the
performance of the network.
PMA
Prompt Maintenance Alarm. An alarm report level; immediate

action is necessary. See also DMA.
PMC
PCI Mezzanine Card.
PMS
Pseudo MMS.
PM-UI
Performance Management User Interface.
PMUX
PCM MUltipleXer.
PN
Permanent Nucleus group of the GSM committee.
PNE
Prsentation des Normes Europennes. Presentation rules of

European Standards.
POI
Point of Interconnection. A point at which the cellular network

is connected to the PSTN. A cellular system may have
multiple POIs.
POTS
Plain Old Telephone Service. Basic telephone service without

special features such as call waiting, call forwarding, etc.
pp, p-p
Peak-to-peak.
PP
Point-to-Point.
ppb
Parts per billion.
PPB
PCI (Peripheral Component Interconnect) to PCI Bridge

board. The PPB allows an MPROC to be linked to a separate
bus. The PPB and MPROC are paired boards.
PPE
Primitive Procedure Entity.
ppm
Parts per million (x 10-6).
Pref CUG
Preferential CUG. A Pref CUG, which can be specified for

each basic service group, is the nominated default CUG to be
used when no explicit CUG index is received by the network.
Presentation Layer
See OSI RM. The Presentation Layer responds to service

requests from the Application Layer and issues service
requests to the Session Layer. It relieves the Application
Layer of concern regarding syntactical differences in data
representation within the end-user systems.

02 May 2003
68P02901W01-M
751
752
GSR6 (Horizon II)
Primary Cell
A cell which is already optimized in the network and has a

co-located neighbour whose cell boundary follows the
boundary of the said cell. The primary cell has a preferred
band equal to the frequency type of the coincident cell.
PRM
Packet Resource Manager. The PRM is a PRP process. It

performs all RLC/MAC functions and realises UL/DL power
control and timing advance.
PROM
Programmable Read Only Memory. A storage device that,

after being written to once, becomes a read-only memory.
PRP
Packet Resource Process(or). A PCU hardware component,

the PRP is a DPROC board which manages the packet
resources at the PCU and is the processor where all of the
radio related processing occurs. GPRS channels are routed
to PRPs which perform the RLC/MAC processing, air
interface scheduling, and frame synchronization of the
channels.
Ps
Location probability. Location probability is a quality criterion

for cell coverage. Due to shadowing and fading a cell edge is
defined by adding margins so that the minimum service
quality is fulfilled with a certain probability.
PSA
Periodic Supervision of Accessibility. PSA is a fault

management function. It periodically sends messages to
BSSs requesting information on their current state. This
verifies whether the BSSs are operational or not. If a BSS
fails to respond to a PSA request for its status, the OMC-R
will generate an alarm for that BSS.
PSAP
Presentation Services Access Point.
pSAP
PCU System Audit Process. pSAP is a GWM process. It

periodically monitors the soft devices to maintain the reliability
of the system.
PSM
Power Supply Module.
pSM
PCU Switch Manager. The pSM resides on the PSP as part

of the GWM Functional Unit process. The pSM maintains
data paths within the PCU and communicates with the BSC.
PSP
PCU System Processor board. Part of GPRS.
PSPDN
Packet Switched Public Data Network. See Packet Switching

and PDN.
PSTN
Public Switched Telephone Network. The domestic land line

telecommunications network. It is usually accessed by
telephones, key telephone systems, private branch exchange
trunks, and data arrangements.
PSU
Power Supply Unit.
PSW
Pure Sine Wave.
PTO
Public Telecommunications Operator.
PUCT
Price per Unit Currency Table. The PUCT is the value of the
Home unit in a currency chosen by the subscriber. The PUCT
is stored in the SIM. The value of the PUCT can be set by the
subscriber and may exceed the value published by the
HPLMN. The PUCT value does not have any impact on the
charges raised by the HPLMN.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
PVC
Permanent Virtual Circuit. Also, in ATM terminology,

Permanent Virtual Connection. A virtual circuit that is
permanently established, saving the time associated with
circuit establishment and tear-down. See also SVC.
PW
Pass Word.
PWR
Power.
PXPDN
Private eXchange Public Data Network. See also PDN.
QA- Quiesent mode

QA
Q (Interface) - Adapter. TMN interface adapter used to

communicate with non-TMN compatible devices and objects.
Used to connect MEs and SEs to TMN (GSM Rec. 12.00).
Q3
Interface between NMC and GSM network.
Q-adapter
See QA.
QAF
Q-Adapter Function.
QEI
Quad European Interface. Interfaces four 2 Mbit/s circuits to

TDM switch highway. See MSI.
QIC
Quarter Inch Cartridge (Data storage format).
QoS
Quality Of Service. An alarm category which indicates that a

failure is degrading service.
Queue
Data structure in which data or messages are temporarily

stored until they are retrieved by a software process. Also a
series of calls waiting for service. See also FIFO.
Quiescent mode
IDS intermediate state before shutdown.
Value of reduction of the MS transmitted RF power relative to

the maximum allowed output power of the highest power
class of MS (A).
RA
RAndom mode request information field.
RA250
Rural Area with the MS travelling at 250 kph. Dynamic model

measured. See also TU3, TU50, HT100 and EQ50.
RAB
Random Access Burst. Data sent on the RACH.
RACCH
Random Access Control CHannel. A GSM common control

channel used to originate a call or respond to a page.
RACH
Random Access CHannel. The RACH is used by the mobile

station to request access to the network. See also RAB.
Radio Frequency
A term applied to the transmission of electromagnetically

radiated information from one point to another, usually using
air or vacuum as the transmission medium. An
electromagnetic wave frequency intermediate between audio
frequencies and infrared frequencies used in radio and
television transmission.
RAM
Random Access Memory. A read/write, nonsequential-access

memory in which information can be stored, retrieved and
modified. This type of memory is generally volatile (i.e., its
contents are lost if power is removed).
R - RXU

02 May 2003
68P02901W01-M
753
754
GSR6 (Horizon II)
RAND
RANDom number (used for authentication). The RAND is

sent by the SGSN to the MS as part of the authentication
process.
RAT
Radio Access Technology
RATI
Receive Antenna Transceiver Interface.
RAx
Rate Adaptation.
RBDS
Remote BSS Diagnostic System (a discontinued Motorola

diagnostic facility).
RBER
Residual Bit Error Ratio. RBER is a ratio of the number of bits

in error to the total number of bits received, within error
detected speech frames defined as good. The measurement
period over which the calculation is made is 480 ms. During
this period, 24 speech frames are decoded and a ratio
calculated. By referring to a lookup table, the ratio is then
converted to an RBER Quality number between 0 and 7.
RBTS
Remote Base Transceiver Station. A BTS that is not

co-located with the BSC that controls it.
RCB
Radio Control Board. Part of the DRCU.
RCI
Radio Channel Identifier. The unique identifier of the radio

channel portion of the circuit path.
RCI
Radio Channel Interface. The RCI changes the MS address

used in the RSS (channel number) to the address used in
Layer 3 in the BSC CP.
RCP
Radio Control Processor.
RCU
Radio Channel Unit. Part of the BSS. Contains transceiver,

digital control circuits, and power supply. Note: The RCU is
now obsolete, see DRCU.
RCVR
Receiver.
RDBMS
Relational DataBase Management System (INFORMIX). The

database management system for the OMC-R database.
RDI
Restricted Digital Information.
RDIS
Radio Digital Interface System.
RDM
Reference Distribution Module. The RDM provides a stable

3MHz reference signal to all transceivers. It is used for carrier
and injection frequency synthesis.
RDN
Relative Distinguished Name. A series of RDNs form a

unique identifier, the distinguished name, for a particular
network element.
REC, Rec
RECommendation.
Reciprocal neighbour
Used to describe adjacent cells; each being designated as a

neighbour of the other. Also known as bidirectional and
twoway neighbour.
Registration
The process of a MS registering its location with the MSC in

order to make or receive calls. This occurs whenever the MS
first activates or moves into a new service area.
REJ
REJect(ion).
REL
RELease.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
RELP
Residual Excited Linear Predictive. A form of speech coding.

RELP coders are usually used to give good quality speech at
bit rates in the region of 9.6 kbit/s.
RELP-LTP
RELP Long Term Prediction. A name for GSM full rate. See
Full Rate.
Remotely Tuned
Combiner
A combiner device which houses two processors (for

paired-redundancy) and several tuneable cavities. See also
COMB
resync
Resynchronize/resynchronization.
REQ
REQuest.
Reuse Pattern
The minimum number of cells required in a pattern before

channel frequencies are reused, to prevent interference.
Varies between cell configuration type and channel type. The
pattern shows assignments of adjacent channels to minimize
interference between cells and sectors within the pattern
area.
Revgen
A Motorola DataGen utility for producing an MMI script from a

binary object database.
RF
See Radio Frequency.
RFC, RFCH
Radio Frequency Channel. A partition of the system RF

spectrum allocation with a defined bandwidth and centre
frequency.
RFE
Radio Front End (module).
RFE
Receiver Front End (shelf).
RFEB
Receiver Front End Board. Part of DRCU II.
RFI
Radio Frequency Interference.
RFM
Radio Frequency Module.
RFN
Reduced TDMA Frame Number.
RFU
Reserved for Future Use.
RJ45
Registered Jack 45. An eight-wire connector used commonly

to connect computers onto a local-area networks (LAN),
especially Ethernets.
RISC
Reduced Instruction Set Computer. A type of microprocessor

that recognizes a relatively limited number of instruction
types, allowing it to operate at relatively higher speeds.
RL
Remote login. RL is a means by which the operator performs

configuration management, fault management, and some
performance management procedures at the NEs. The RL
software manages the X.25 connection for remote login. The
circuit is made by the OMC-R calling the NE.
RLC
Release Complete. An SCCP message type used with RLSD

to release a connection.
RLC
Radio Link Control. Air interface transmission layer. The RLC

function processes the transfer of PDUs from the LLC layer.
RLP
Radio Link Protocol. An ARQ protocol used to transfer user

data between an MT and IWF. See GSM 04.22.
RLR
Receive Loudness Rating. See SLR.

02 May 2003
68P02901W01-M
755
756
GSR6 (Horizon II)
RLSD
ReLeaSeD. An SCCP message type used with RLC to

release a connection.
RMS
Root Mean Square (value). The most common mathematical

method of defining the effective voltage or current of an AC
wave. For a sine wave, the rms value is 0.707 times the peak
value.
RMSU
Remote Mobile Switching Unit. An RMSU is a line

concentrator. It may be inserted between the MSC and some
of the BSS sites served by the MSC to reduce the number of
terrestrial signalling and traffic circuits required.
RNTABLE
Table of 128 integers in the hopping sequence.
Roaming
Situation where mobile station operates in a cellular system

other than the one from which service is subscribed.
ROM
Read Only Memory. Computer memory that allows fast

access to permanently stored data but prevents addition to or
modification of the data. ROM is inherently non-volatile
storage - it retains its contents even when the power is
switched off.
ROSE
Remote Operations Service Element. An ASE which carries

a message between devices over an association established
by ASCE (a CCITT specification for O & M) (OMC).
Roundtrip
Time period between transmit and receive instant of a

timeslot in the BTS, propagation determined by the response
behaviour of the MS and the MS to BTS delay distance.
RPE
Regular Pulse Excited (codec). See RPE-LTP.
RPE-LTP
Regular Pulse Excitation - Long Term Prediction. The GSM

digital speech coding scheme. GSM uses a simplified RPE
codec, with long-term prediction, operating at 13 kbits/s to
provide toll quality speech.
RPOA
Recognised Private Operating Agency. Private

telecommunications operator recognised by the appropriate
telecommunications authority.
RPR
Read Privilege Required. Part of the table structure of the

OMC database schema. Access to the column is allowed only
for privileged accounts.
RR
Radio Resource management. Part of the GSM management

layer. The functions provided by RR include paging, cipher
mode set, frequency redefinition, assignments, handover and
measurement reports.
RR
Receive Ready.
RRSM
Radio Resource State Machine. Translates messages

through Call Processing (CP). Activates and deactivates radio
channels as controlled by the CRM.
RS232
Recommended Standard 232. The interface between a

terminal (DTE) and a modem (DCE) for the transfer of serial
data. Standard serial interface.
RSE
Radio System Entity.
RSL
Radio Signalling Link. RSL is used for signalling between the

BSC and BTSs. The interface uses a 64 kbit/s timeslot with a
LAPD protocol.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
RSLF
Radio System Link Function.
RSLP
Radio System Link Processor.
RSS
Radio SubSystem (replaced by BSS).
RSSI
Received Signal Strength Indicator. A parameter returned

from a transceiver that gives a measure of the RF signal
strength between the MS and BTS, either uplink or downlink.
RSZI
Regional Subscription Zone Identity. The RSZI defines the

regions in which roaming is allowed. The elements of the
RSZI are:
The Country Code (CC) which identifies the country in which
the GSM PLMN is located,
The National Destination Code (NDC) which identifies the
GSM PLMN in that country,
The Zone Code (ZC) which identifies a regional subscription
zone as a pattern of allowed and not allowed location areas
uniquely within that PLMN.
RTC
Remotely Tuneable Channel Combiner. RTCs are used to

fine-tune the cavities to the right frequency. A poorly tuned
cavity can cause power destined for the antenna to be
reversed.
RTE
Remote Terminal Emulator.
RTF
Radio Transceiver Function. RTF is the function that supports

the air interface channel and the DRI/Transceiver pair. When
equipping a DRI at a remote BTS, one or more RTFs must be
equipped.
RTF
Receive Transmit Functions.
RTS
Request to Send. A handshaking signal used with

communication links, especially RS232 or CCITT Rec. V.24 to
indicate (from a transmitter to a receiver) that data is ready
for transmission. See also CTS.
RU
Rack Unit.
Run level
System processor operating mode.
Rx
Receive(r).
RXCDR
Remote Transcoder. An RXCDR is used when the

transcoding is performed at a site away from the BSC. This
site would be at or near the MSC. This enables 4:1
multiplexing in which the transcoded data for four logical
channels is combined onto one 64 kbit/s link, thus reducing
the number of links required for interconnection to the BSCs.
See also XCDR.
RXF
Receive Function (of the RTF).
RXLEV
Received signal level. An indication of received signal level

based on the RSSI. RXLEV is one of the two criteria for
evaluating the reception quality (the basis for handover and
power control). See also RXQUAL. The MS reports RXLEV
values related to the apparent received RF signal strength. It
is necessary for these levels to attain sufficient accuracy for
the correct functioning of the system.
RXLEV-D
Received signal level downlink.
RXLEV-U
Received signal level uplink.

02 May 2003
68P02901W01-M
757
GSR6 (Horizon II)
RXQUAL
Received signal quality. An indication of the received signal

quality based on the BER. RXQUAL is one of the two criteria
for evaluating the reception quality (the basis for handover
and power control). See also RXLEV. The MS measures the
received signal quality, which is specified in terms of BER
before channel decoding averaged over the reporting period
of length of one SACCH multiframe.
RXQUAL-D
Received signal quality downlink.
RXQUAL-U
Received signal quality uplink.
RXU
Remote Transcoder Unit. The shelf which houses the

remote transcoder modules in a BSSC cabinet at a remote
transcoder site.
S7
See SS7.
S/W
SoftWare.
SABM
Set Asynchronous Balanced Mode. A message which

establishes the signalling link over the air interface.
SABME
SABM Extended.
SACCH
Slow Associated Control CHannel. A GSM control channel

used by the MS for conveying power control and timing
advance information in the downlink direction, and RSSI and
link quality reports in the uplink direction.
SACCH/C4
Slow Associated Control CHannel/SDCCH/4.
SACCH/C8
Slow Associated Control CHannel/SDCCH/8.
SACCH/T
Slow Associated Control CHannel/Traffic channel.
SACCH/TF
Slow Associated Control CHannel/Traffic channel Full rate.
SACCH/TH
Slow Associated Control CHannel/Traffic channel Half rate.
SAGE
A brand of trunk test equipment.
SAP
Service Access Point. In the reference model for OSI, SAPs

of a layer are defined as gates through which services are
offered to an adjacent higher layer.
SAP
System Audits Process. SAP is on each GPROC in the BSS.

It monitors the status of the BSS on a periodic (scheduled)
and on-demand basis during normal mode. SAP detects
faulty or degrading hardware and software (through the use of
audit tests) and notifies the Alarms handling software of the
condition.
SAPI
Service Access Point Indicator (identifier). The OSI term for

the component of a network address which identifies the
individual application on a host which is sending or receiving
a packet.
SAW
Surface Acoustic Wave. SAW devices basically consist of an

input transducer to convert electrical signals to tiny acoustic
waves, which then travel through the solid propagation
medium to the output transducer where they are reconverted
to electrical signals. SAW band pass filters are used for
sorting signals by frequency.
SB
Synchronization Burst (see Synchronization burst).
S7- SYSGEN
758

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
SBUS
Serial Bus. An SBUS is a logical device made up of the

communication path between the GPROCs and LANX cards
in a cage.
SC
Service Centre (used for Short Message Service).
SC
Service Code.
SCCA
System Change Control Administration. Software module

which allows full or partial software download to the NE
(OMC).
SCCP
Signalling Connection Control Part (part of SS7).
SCEG
Speech Coding Experts Group (of GSM).
SCH
Synchronization CHannel. A GSM broadcast control channel

used to carry information for frame synchronization of MSs
and identification of base stations.
SCI
Status Control Interface. A slave to the Status Control

Manager.
SCIP
Serial Communication Interface Processor.
SCM
Status Control Manager. Accepts messages from other

processors within the switch requesting status displays in the
form of one or more lights on a hardware panel. The SCM
maps the status display requests into specific commands to
the status control interface processor to turn on and/or turn
off lights.
SCN
Sub-Channel Number. One of the parameters defining a

particular physical channel in a BS.
SCP
Service Control Point (an intelligent network entity).
SCSI
Small Computer Systems Interface. A processor-independent

standard for system-level interfacing between a computer and
intelligent devices including hard disks, floppy disks,
CD-ROM, printers, scanners, and many more. SCSI-1 can
connect up to seven devices to a single SCSI adaptor (or
host adaptor) on the computers bus.
SCU
Slim Channel Unit.
SCU900
Slim Channel Unit for GSM900.
SDCCH
Stand-alone Dedicated Control CHannel. A GSM control

channel where the majority of call setup occurs. Used for
MS to BTS communications before MS assigned to TCH. A
SDCCH is used by a single MS for call setup, authentication,
location updating and SMS point to point.
SDL
Specification Description Language. A method for visually

depicting the functionality of call processing, operations and
maintenance software.
SDM
Sub-rate Data Multiplexor
SDT
SDL Development Tool. A software tool to model and validate

real-time, state-based product software designs.
SDU
Service Data Unit. In layered systems, a set of data that is

sent by a user of the services of a given layer, and is
transmitted to a peer service user semantically unchanged.

02 May 2003
68P02901W01-M
759
760
GSR6 (Horizon II)
SDR
Special Drawing Rights. The SDR is the International

Monetary Fund unit of account. It also serves as a basis for
the unit of account for a number of other international
organizations and as a basis for private financial instruments.
The SDR is based on the values of the euro, U.S. dollar,
Japanese yen and pound sterling.
SE
Support Entity. See SEF.
Secondary Cell
A cell which is not optimized in the network and has a

co-located neighbour whose cell boundary follows the
boundary of the said cell. The secondary cell has a preferred
band the same as that of its own frequency type.
SEF
Support Entity Function. SEFs are functions not directly

involved in the telecommunication process. They include fault
localisation, protection switching, etc. (GSM Rec.12.00).
Session Layer
See OSI RM. The Session Layer responds to service

requests from the Presentation Layer and issues service
requests to the Transport Layer. It provides the mechanism
for managing the dialogue between end-user application
processes. It provides for either duplex or half-duplex
operation and establishes checkpointing, adjournment,
termination, and restart procedures.
SFH
Synthesizer Frequency Hopping. The principle of SFH is that

every mobile transmits its time slots according to a sequence
of frequencies that it derives from an algorithm. The
frequency hopping occurs between time slots and, therefore,
a mobile station transmits (or receives) on a fixed frequency
during one time slot. It must then hop before the time slot on
the next TDMA frame. Due to the time needed for monitoring
other base stations the time allowed for hopping is
approximately 1 ms, according to the receiver
implementation. The receive and transmit frequencies are
always duplex frequencies.
SGSN
Serving GPRS Support Node. The SGSN provides the

control, transmission, OAMP, and charging functions. It keeps
track of the individual MS locations, and performs security
functions and access control. The SGSN is connected to the
BSS via a Frame Relay network.
SI
Screening Indicator. The supplementary service (SS)

screening indicator is sent by the MS at the beginning of the
radio connection to allow the network to assess the
capabilities of the MS and hence determine either whether a
particular network initiated SS operation may be invoked or
which version of a network initiated SS operation should be
invoked. The SS screening indicator is only relevant to
network initiated SS operation and is valid for the duration of
a radio connection.
SI
Service Interworking. Part of the IWF.
SI
Supplementary Information.
SIA
Supplementary Information A.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
SID
Silence Descriptor. The transmission of comfort noise

information to the RX side is achieved by means of a SID
frame. A SID frame is transmitted at the end of speech bursts
and serves as an end of speech marker for the RX side. In
order to update the comfort noise characteristics at the RX
side, SID frames are transmitted at regular intervals also
during speech pauses. This also serves the purpose of
improving the measurement of the radio link quality by the
radio subsystem (RSS).
SIF
Signal Information Field. The bits of a message signal unit

that carry information for a certain user transaction; the SIF
always contains a label.
Signalling System No.7 See SS7.

SIM
Subscriber Identity Module. Removable module which is

inserted into a mobile equipment; it is considered as part of
the MS. It contains security related information (IMSI, Ki,
PIN), other subscriber related information and the algorithms
A3 and A8.
SIMM
Single Inline Memory module.
SIMM
System Integrated Memory Module. A small plug-in circuit

board providing additional RAM for a computer.
SIO
Service Information Octet. Eight bits contained in a message

signal unit, comprising the service indicator and sub-service
field. A value in the SIF of an SS7 signalling message
specifying the User Part type.
SITE
BSC, BTS or collocated BSC-BTS site.
SIX
Serial Interface eXtender. Converts interface levels to TTL

levels. Used to extend 2 serial ports from GPROC to external
devices (RS232, RS422, and fibre optics).
SK
Secondary Key. A database column attribute, the secondary

key indicates an additional index and/or usage as a
composite key.
SL
See Session Layer.
SL
Signalling Link. The signalling links between the various

network elements are:
Remote BTS to BSC - Radio Signalling Link (RSL),
BSC to MSC - Message Transfer Link (MTL),
OMC(R) to BSS - Operations and Maintenance Link (OML),
Remote XCDR to BSC - XCDR signalling Link (XBL),
CBC to BSC - Cell Broadcast Link (CBL).
SLNK
Serial Link. One of four communications paths between SCIP

and peripheral equipment. The information on the link is sent
serially in a bit-synchronous format.
SLR
Send Loudness Rating. The SLR, in the mobile to land

direction, and the Receive Loudness Rating (RLR) in the land
to mobile direction, determine the audio signal levels for the
customers speech. The loudness ratings are calculated from
the send and receive sensitivity masks or frequency
responses.
SLTA
Signalling Link Test Acknowledge. Message sent from the

MSC to the BSC in response to an SLTM.

02 May 2003
68P02901W01-M
761
762
GSR6 (Horizon II)
SLTM
Signalling Link Test Message. During the process of bringing

an MTL link into service, the BSC sends an SLTM message
to the MSC. The MSC responds with an SLTA message.
SM
Switch Manager. The function of the SM is to connect a MS

terrestrial trunk from the MSC (designated by the MSC), to
the radio channel given to a MS by the cell resource manager
in the BSS software.
SM
Summing Manager.
SMAE
System Management Application Entity (CCITT Q795, ISO

9596). OSI terminology for a software Management
Information Server that manages a network.
SMASE
System Management Application Service Element.
SMCB
Short Message Cell Broadcast.
SME
Short Message Entity. An entity that may send or receive

Short Messages. The SME may be located in a fixed
network, an MS, or a SC. See also SMS.
SMG
Special Mobile Group. To avoid confusion between the GSM

system and the GSM committee with its wider responsibilities,
the committee was renamed SMG in 1992.
SMP
Motorola Software Maintenance Program. A Motorola

program designed to ensure the highest quality of software
with the highest level of support.
SMS
Short Message Service. SMS is a globally accepted wireless

service that enables the transmission of alphanumeric
messages between mobile subscribers and external systems
such as electronic mail, paging, and voice-mail systems. It
transfers the short messages, up to 160 characters, between
Smts and MSs via an SMS-SC. See also SMS-SC, SMS/PP
and Smt.
SMSCB
Short Message Service Cell Broadcast. SMSCB is a service

in which short messages may be broadcast from a PLMN to
MSs. SMSCB messages come from different sources (e.g.
traffic reports, weather reports). Messages are not
acknowledged by the MS. Reception of SMSCB messages by
the MS is only possible in idle mode. The geographical area
over which each message is transmitted is selected by the
PLMN operator, by agreement with the provider of the
information.
SMS-SC
Short Message Service - Service Centre. SMS-SC is an

interworking unit between stationary networks and the GSM
Network. It acts as a store and forward centre for short
messages. See also SMS, SMS/PP and Smt.
SMS/PP
Short Message Service/Point-to-Point. Two different

point-to-point services have been defined: Mobile Originated
(MO) and Mobile Terminated (MT). A short message always
originates or terminates in the GSM network. This means that
short messages can never be sent between two users both
located in stationary networks. See also SMS, SMS-SC and
Smt.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Smt
Short message terminal. See also SMS, SMS-SC and

SMS/PP. There are different types of Smt interfaces, one
being the Computer Access Interface which provides services
for external computers communicating with SMS-SCs through
the Computer Access Protocol.
SN
Subscriber Number.
SND
SeND.
SNDR
SeNDeR.
SNR
Serial NumbeR.
SOA
Suppress Outgoing Access (CUG SS). An arrangement

which prevents a member of a CUG placing calls outside the
CUG.
Software Instance
A complete set of software and firmware objects including the

database object.
SP
Service Provider. The organisation through which the

subscriber obtains GSM telecommunications services. This
may be a network operator or possibly a separate body.
SP
Signalling Point. A signalling point is a node within a SS7

network.
SP
Special Product.
SP
SPare.
SPARC
Scalable Processor ArChitecture. a 32- and 64-bit

microprocessor architecture from Sun Microsystems that is
based on the Reduced Instruction Set Computer (RISC).
SPARC has become a widely-used architecture for hardware
used with UNIX-based operating systems.
SPC
Signalling Point Code.
SPC
Suppress Preferential CUG. Prohibits the use of the

preferential CUG, on a per call basis.
SPI
Signalling Point Inaccessible.
SPP
Single Path Preselector.
SQE
Signal Quality Error.
SQL
Structured Query Language. The standard language for

relational database management systems as adopted by the
American National Standards Institute (ANSI X3.135-1989)
and the International Standards Organization (ISO
9075-1989).
SRD
Service Request Distributor.
SRES
Signed RESponse (authentication). The SRES is calculated

by the MS, using the RAND, and sent to the SGSN to
authenticate the MS.
SS
Supplementary Service. A modification of, or a supplement

to, a basic telecommunication service.
SS
System Simulator.

02 May 2003
68P02901W01-M
763
764
GSR6 (Horizon II)
SS7
ITU-TSS Common Channel Signalling System No. 7. Also

known as C7, S7 or SS#7. The standard defines the
procedures and protocol by which network elements in the
PSTN exchange information over a digital signalling network
to effect wireless (cellular) and wireline call setup, routing and
control.
SSA
SubSystem-Allowed. SSA is used for SCCP subsystem

management. An SSA message is sent to concerned
destinations to inform those destinations that a subsystem
which was formerly prohibited is now allowed. (see ITU-T
Recommendation Q.712 para 1.15).
SSAP
Site System Audits Processor.
SSC
Supplementary Service Control string. When a subscriber

selects a supplementary service control from the menu in a
GSM network, the mobile station invokes the SSC by sending
the network the appropriate functional signalling message.
SSF
Subservice Field. The level 3 field containing the network

indicator and two spare bits.
SSM
Signalling State Machine.
SSN
SubSystem Number. In SS7, each signalling point (SP) may

contain a number of subsystems. Each subsystem has a
unique ID, the SSN (e.g. 149 for SGSN and 6 for HLR).
SSP
Service Switching Point. Intelligent Network Term for the

Class 4/5 Switch. The SSP has an open interface to the IN
for switching signalling, control and handoff.
SSP
Subsystem-prohibited. SSP is used for SCCP subsystem

management. An SSP message is sent to concerned
destinations to inform SCCP Management at those
destinations of the failure of a subsystem.
SSS
Switching SubSystem. The SSC comprises the MSC and the

LRs.
STAN
Statistical ANalysis (processor).
STAT
STATistics.
stats
Statistics.
STC
System Timing Controller. The STC provides the timing

functions for the GPROC.
STMR
Side Tone Masking rating. A rating, expressed in dB, based

on how a speaker will perceive his own voice when speaking.
SUERM
Signal Unit Error Rate Monitor. A link error rate monitor.
STP
Signalling Transfer Point. A node in the SS7 telephone

network that routes messages between exchanges and
between exchanges and databases that hold subscriber and
routing information.
SU
Signal Unit. A group of bits forming a separately transferable

entity used to convey information on a signalling link.
SunOS
Sun Microsystems UNIX Operating System. SunOS was

renamed Solaris.
Superframe
51 traffic/associated control multiframes or 26

broadcast/common control multiframes (period 6.12s).

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Super user
User account that can access all files, regardless of

protection settings, and control all user accounts.
SURF
Sectorized Universal Receiver Front-end (Used in

Horizonmacro).
SVC
Switch Virtual Circuit. A temporary virtual circuit that is set up

and used only as long as data is being transmitted. Once the
communication between the two hosts is complete, the SVC
disappears. See also PVC.
SVM
SerVice Manager. The SVM provides overall management

authority for all in-service service circuits.
SVN
Software Version Number. The SVN allows the ME

manufacturer to identify different software versions of a given
type approved mobile. See also IMEI and IMEISV.
SW
Software.
SWFM
SoftWare Fault Management. Software faults are handled

through a SWFM facility which routes those events to the
OMC independently through the FCP.
SYM
SYstem information Manager. The SYM builds and sends

GPRS system information messages over the BCCH.
sync
synchronize/synchronization.
Synchronization burst
Period of RF carrier less than one timeslot whose modulation

bit stream carries information for the MS to synchronize its
frame to that of the received signal.
Synthesizer hopping
Synthesizer hopping is a method of frequency hopping in

which the RCUs are re-tuned in real-time, from frequency to
frequency.
SYS
SYStem.
SYSGEN
SYStem GENeration. The Motorola procedure for loading a

configuration database into a BTS.
Timer.
Transparent.
Type only.
T1
Digital WAN carrier facility that transmits DS-1-formatted data

at 1544 kbp/s through the telephone-switching network.
companies. T1 lines are widely used for private networks as
well as interconnections between an organizations PBX or
LAN and the telco.
T43
Type 43 Interconnect Board. Provides interface to 12

unbalanced (6-pair) 75 ohm (T43 coax connectors) lines for
2 Mbit/s circuits (See BIB).
TA
Terminal Adaptor. A physical entity in the MS providing

terminal adaptation functions (see GSM 04.02).
TA
See Timing Advance.
TAC
Type Approval Code. Part of the IMEISV.
TACS
Total Access Communication System. European analogue

cellular system.
T -TxBPF

02 May 2003
68P02901W01-M
765
766
GSR6 (Horizon II)
TAF
Terminal Adaptation Function.
TATI
Transmit Antenna Transceiver Interface. The TATI consists

of RF combining equipments, either Hybrid or Cavity
Combining. See CCB.
TAXI
Transparent Asynchronous Transmitter/Receiver Interface

(physical layer). A 100 Mbps ATM transmission standard
defined by the ATM Forum.
TBD
To Be Determined.
TBF
Temporary Block Flow. MAC modes support the provision of

TBFs allowing the point-to-point transfer of signalling and
user data between the network and an MS.
TBR
Technical Basis for Regulation. An ETSI document containing

technical requirements and procedures.
TBUS
TDM Bus. A TBUS is a logical device made up of the TDM

backplane of a cage, the KSW devices managing the TDM
highway of the cage, and local and remote KSWX devices (if
they exist).
TC
Transaction Capabilities. TC refers to a protocol structure

above the network layer interface (i.e., the SCCP service
interface) up to the application layer including common
application service elements but not the specific application
service elements using them. TC is structured as a
Component sub-layer above a Transaction sub-layer.
TCAP
Transaction Capabilities Application Part. The layer of the

SS7 protocol that is used to obtain Routing data for certain
services.
TCB
TATI Control Board.
TCH
Traffic CHannel. GSM logical channels which carry either

encoded speech or user data.
TCH/F
A full rate TCH. See also Full Rate.
TCH/F2.4
A full rate TCH at 2.4 kbit/s.
TCH/F4.8
TCH/F9.6
TCH/FS
A full rate Speech TCH.
TCH/H
A half rate TCH. See also Half Rate.
TCH/H2.4
A half rate TCH at 2.4 kbit/s.
TCH/H4.8
A half rate TCH at 4.8 kbit/s.
TCH/HS
A half rate Speech TCH.
TCI
Transceiver Control Interface.
TCP
Transmission Control Protocol. TCP is one of the main

protocols in TCP/IP networks. Whereas the IP protocol deals
only with packets, TCP enables two hosts to establish a
connection and exchange streams of data. TCP guarantees
delivery of data and also guarantees that packets will be
delivered in the same order in which they were sent. See also
IP and TCP/IP.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
TCP/IP
Transmission Control Protocol/Internet Protocol. Two

interrelated protocols that are part of the Internet protocol
suite. TCP operates on the OSI Transport Layer and IP
operates on the OSI Network Layer. See also IP and TCP.
TC-TR
Technical Commitee Technical Report.
TCU
Transceiver Control Unit.
TDF
Twin Duplexed Filter. Used in M-Cellhorizon.
TDM
Time Division Multiplexing. A type of multiplexing that

combines data streams by assigning each stream a different
time slot in a set. TDM repeatedly transmits a fixed sequence
of time slots over a single transmission channel. Within
T-Carrier systems, such as T-1 and T-3, TDM combines PCM
streams created for each conversation or data stream.
TDMA
Time Division Multiple Access. A technology for delivering

digital wireless service using TDM. TDMA works by dividing a
radio frequency into time slots and then allocating slots to
multiple calls. In this way, a single frequency can support
multiple, simultaneous data channels.
TDU
TopCell Digital Unit. Part of the TopCell BTS hardware. A

TDU is capable of supporting 6 TRUs for supporting up to 6
sectors.
TE
Terminal Equipment. Equipment that provides the functions

necessary for the operation of the access protocols by the
user.
Tei
Terminal endpoint identifier. A number that identifies a specific

connection endpoint within a service access point.
TEI
Terminal Equipment Identity.
TEMP
TEMPorary.
TEST
TEST control processor.
TF
Transmission Function. The TF provides layered protocol

software for handling payload information transfer and for
providing signalling communications between the control
function and external systems.
TFA
TransFer Allowed. An SPC route management message used

to notify adjacent signalling points of an accessible route.
TFP
TransFer Prohibited. An SPC route management message

used to notify adjacent signalling points of an inaccessible
route.
TFTP
Trivial File Transfer Protocol. TFTP is a simple form of FTP.

It uses UDP and provides no security features. It is often
used by servers to boot diskless workstations, X-terminals,
and routers.
TI
Transaction Identifier.
Timeslot
The multiplex subdivision in which voice and signalling bits

are sent over the air. Each RF carrier is divided into 8
timeslots. See also ARFCN.
Timing advance
A signal sent by the BTS to the MS. It enables the MS to

advance the timing of its transmission to the BTS so as to
compensate for propagation delay.
TL
See Transport Layer.

02 May 2003
68P02901W01-M
767
768
GSR6 (Horizon II)
TLV
Type, Length and Value. An encoding element composed of

three fields: a type identifier, a length indicator, and content
octets.
TM
Traffic Manager.
TMI
TDM Modem Interface board. Provides analogue interface

from IWF to modems for 16 circuits. Part of IWF.
TMM
Traffic Metering and Measuring. TMM provides system tools

to be used by traffic engineering and switch maintenance
personnel to determine if the system is operating correctly.
TMM reports are provided for trunk circuits, trunk groups,
service circuits, call routing and miscellaneous system data.
TMN
Telecommunications Management Network. The physical

entities required to implement the Network Management
functionality for the PLMN.
Also, TMN was originated formally in 1988 under the ITU-TS
as a strategic goal to create or identify standard interfaces
that would allow a network to be managed consistently across
all network element suppliers. The concept has led to a series
of interrelated efforts at developing standard ways to define
and address network elements. TMN uses the OSI
Management Standards as its framework. TMN applies to
wireless communications and cable TV as well as to private
and public wired networks.
TMSI
Temporary Mobile Subscriber Identity. A unique identity

temporarily allocated by the MSC to a visiting mobile
subscriber to process a call. May be changed between calls
and even during a call, to preserve subscriber confidentiality.
TN
Timeslot Number.
TON
Type Of Number.
Traffic channels
Channels which carry users speech or data. See also TCH.
Traffic unit
Equivalent to an erlang.
Training sequence
Sequence of modulating bits employed to facilitate timing

recovery and channel equalization in the receiver.
Transport Layer
See OSI RM. The Transport Layer responds to service

requests from the Session Layer and issues service requests
to the Network Layer. Its purpose is to provide transparent
transfer of data between end users, thus relieving the upper
layers from any concern with providing reliable and
cost-effective data transfer.
TRS
Timeslot Resource Shifter. The TRS determines which

timeslots are active in a PRP board to perform a control of
the GPRS traffic.
TRAU
Transcoder Rate Adaption Unit. TRAU converts the encoded

voice and rate adapted data into 64 kbps data for the PSTN.
TRU
TopCell Radio unit.
TRX
Transceiver(s). A network component which can serve full

duplex communication on 8 full-rate traffic channels according
to specification GSM 05.02. If Slow Frequency Hopping
(SFH) is not used, then the TRX serves the communication
on one RF carrier.
TS
Technical Specification.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
TS
TeleService. Any service provided by a telecommunication

provider.
TS
TimeSlot (see Timeslot).
TSA
TimeSlot Acquisition.
TSA
TimeSlot Assignment.
TSDA
Transceiver Speech & Data Interface.
TSC
Training Sequence Code. A training sequence is sent at the

centre of a burst to help the receiver identify and synchronize
to the burst. The training sequence is a set sequence of bits
which is known by both the transmitter and receiver. There
are eight different TSCs numbered 0 to 7. Nearby cells
operating with the same RF carrier frequency use different
TSCs to allow the receiver to identify the correct signal.
TSI
TimeSlot Interchange. The interchange of timeslots within a

TDM stream.
TSDI
Transceiver Speech and Data Interface.
TSM
Transceiver Station Manager.
TSW
Timeslot SWitch.
TTCN
Tree and Tabular Combined Notation. TTCN is a

programming language endorsed by ISO that is used to write
test suites for telecommunications systems.
TTL
Transistor to Transistor Logic. A common semiconductor

technology for building discrete digital logic integrated circuits.
TTY
TeleTYpe (refers to any terminal).
TU
Traffic Unit.
TU3
Typical Urban with the MS travelling at 3 kph. Dynamic model

measured. See also TU50, HT100, RA250 and EQ50.
TU50
Typical Urban with the MS travelling at 50 kph. Dynamic

model against which the performance of a GSM receiver can
be measured. See also TU3, HT100, RA250 and EQ50.
TUP
Telephone User Part. TUP was an earlier implementation of

SS7 and generally does not allow for data type applications.
TV
Type and Value.
Two-way neighbour
See Reciprocal neighbour.
Tx
Transmit(ter).
TXF
Transmit Function. See RTF.
TXPWR
Transmit PoWeR. Tx power level in the

MS_TXPWR_REQUEST and MS_TXPWR_CONF
parameters.
TxBPF
Transmit Bandpass Filter. See BPF.

02 May 2003
68P02901W01-M
769
GSR6 (Horizon II)
U - UUS
770
UA
Unnumbered Acknowledgment. A message sent from the

MS to the BSS to acknowledge release of radio resources
when a call is being cleared.
UCS2
Universal Coded Character Set 2. A codeset containing all of

the characters commonly used in computer applications.
UDI
Unrestricted Digital Information.
UDP
User Datagram Protocol. UDP is a connectionless protocol

that, like TCP, runs on top of IP networks. Unlike TCP/IP,
UDP/IP provides very few error recovery services, offering
instead a direct way to send and receive datagrams over an
IP network. It is used primarily for broadcasting messages
over a network.
UDUB
User Determined User Busy.
UHF
Ultra High Frequency. The UHF range of the radio spectrum

is the band extending from 300 MHz to 3 GHz.
UI
Unnumbered Information (Frame).
UIC
Union International des Chemins de Fer. The UIC is the

worldwide organisation for cooperation among railway
companies. Its activities encompass all fields related to the
development of rail transport.
UID
User ID. Unique number used by the system to identify the

user.
UL
Upload (of software or database from an NE to a BSS).
UL
UpLink.
ULC
UpLink Concatenator. The ULC concatenates RLC data

blocks into LLC frames.
Um
Air interface.
UMTS
Universal Mobile Telecommunication System. The European

implementation of the 3G wireless phone system. UMTS,
which is part of IMT-2000, provides service in the 2GHz band
and offers global roaming and personalized features.
Designed as an evolutionary system for GSM network
operators, multimedia data rates up to 2 Mbps are expected.
UNIX
A multiuser, multitasking operating system that is widely used

as the master control program in workstations and especially
servers. UNIX was developed by AT&T and freely distributed
to government and academic institutions, causing it to be
ported to a wider variety of machine families than any other
operating system. As a result, UNIX became synonymous
with open systems.
UPCMI
Uniform PCM Interface (13 bit). The UPCMI is introduced for

design purposes in order to separate the speech transcoder
impairments from the basic audio impairments of the MS.
UPD
Up to Date.
Uplink
Physical link from the MS towards the BTS (MS transmits,

BTS receives).

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
UPS
Uninterruptable Power Supply. A device that is inserted

between a primary power source, such as a commercial
utility, and the primary power input of equipment to be
protected, e.g., a computer system, for the purpose of
eliminating the effects of transient anomalies or temporary
outages. Backup power is used when the electrical power
fails or drops to an unacceptable voltage level.
UPU
User Part Unavailable.
Useful part of burst
That part of the burst used by the demodulator; differs from

the full burst because of the bit shift of the I and Q parts of
the GMSK signal.
USF
Uplink State Flag.
USSD
Unstructured Supplementary Service Data. The USSD

mechanism allows the MS user and a PLMN operator defined
application to communicate in a way which is transparent to
the MS and to intermediate network entities. The mechanism
allows development of PLMN specific supplementary
services.
UTRAN
UMTS Radio Access Network
UUS
User-to-User Signalling supplementary service. The UUS

supplementary service allows a mobile subscriber to
send/receive a limited amount of information to/from another
PLMN or ISDN subscriber over the signalling channel in
association with a call to the other subscriber.
Value only.
VA
Viterbi Algorithm (used in channel equalizers). An algorithm to

compute the optimal (most likely) state sequence in a model
given a sequence of observed outputs.
VAD
Voice Activity Detection. A process used to identify presence

or absence of speech data bits. VAD is used with DTX.
VAP
Videotex Access Point.
VBS
Voice Broadcast Service. VBS allows the distribution of

speech (or other signals which can be transmitted via the
speech codec), generated by a service subscriber, into a
predefined geographical area to all or a group of service
subscribers located in this area.
VC
See Virtual Circuit.
VCO
Voltage Controlled Oscillator. An oscillator whose clock

frequency is determined by the magnitude of the voltage
presented at its input. The frequency changes when the
voltage changes.
VCXO
Voltage Controlled Crystal Oscillator.
VDU
Visual Display Unit. A device used for the real-time temporary

display of computer output data. Monitor.
VGCS
Voice Group Call Service.
V - VTX host

02 May 2003
68P02901W01-M
771
772
GSR6 (Horizon II)
Videotex
The Videotex service is an interactive service, that by means

of proper access points and standardized procedures,
provides the access to data base information stored in host
computers external to the PLMN, via public
telecommunication networks.
Virtual Circuit
A connection between two devices, that functions as though it

is a direct connection, even though it may physically be
circuitous. The term is used most frequently to describe
connections between two hosts in a packet-switching
network.
VLR
Visitor Location Register. A GSM network element which

provides a temporary register for subscriber information for a
visiting subscriber. Often a part of the MSC.
VLSI
Very Large Scale Integration (in ICs). The process of placing

between 100,000 and one million electronic components on a
single chip.
VMSC
Visited MSC. (Recommendation not to be used).
vocoder
Abbreviation for voice-coder. A device that usually consists of

a speech analyzer, which converts analog speech waveforms
into narrowband digital signals, and a speech synthesizer,
which converts the digital signals into artificial speech sounds.
VOX
Voice Operated Transmission. An acoustoelectric transducer

and a keying relay connected so that the keying relay is
actuated when sound, or voice energy above a certain
threshold is sensed by the transducer. A vox is used to
eliminate the need for push-to-talk operation of a transmitter
by using voice energy to turn on the transmitter
VPLMN
Visited PLMN.
VSC
Videotex Service Centre.
V(SD)
Send state variable.
VSP
Vehicular Speaker Phone.
VSWR
Voltage Standing Wave Ratio. In a transmission line, the ratio

of maximum to minimum voltage in a standing wave pattern.
Note: The VSWR is a measure of impedance mismatch
between the transmission line and its load. The higher the
VSWR, the greater the mismatch. The minimum VSWR, i.e.,
that which corresponds to a perfect impedance match, is
unity.
VTX host
The components dedicated to Videotex service.

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
W - WWW
WAN
Wide Area Network. A physical or logical network that

provides data communications to a larger number of
independent users than are usually served by a LAN and is
usually spread over a larger geographic area than that of a
LAN. WANs may include physical networks, such as ISDN
networks, X.25 networks, and T1 networks.
WPA
Wrong Password Attempts (counter). Some supplementary

services have the option of the subscriber using a password.
If a password check is done with an incorrect password, the
WPA is incremented by one. If a password check is passed,
the WPA is set to zero. If the WPA exceeds the value three,
the subscriber will have to register a new password with the
service provider.
WS
Work Station. The remote device via which O&M personnel

execute input and output transactions for network
management purposes.
WSF
Work Station Function block.
WWW
World Wide Web. An international, virtual-network-based

information service composed of Internet host computers that
provide on-line information in a specific hypertext format.
WWW servers provide hypertext metalanguage (HTML)
formatted documents using the hypertext transfer protocol,
HTTP. Information on the WWW is accessed with a hypertext
browser.

02 May 2003
68P02901W01-M
773
GSR6 (Horizon II)
X - X Window
X.25
X.25, adopted as a standard by the CCITT, is a commonly

used protocol for public packet-switched networks
(PSPDNS). The X.25 protocol allows computers on different
public networks to communicate through an intermediary
computer at the network layer level. The protocol
corresponds closely to the data-link and physical-layer
protocols defined in the OSI communication model.
X.25 link
A communications link which conforms to X.25 specifications

and uses X.25 protocol (NE to OMC links).
XBL
Transcoder to BSS Link. The carrier communications link

between the Transcoder (XCDR) and the BSS.
XCB
Transceiver Control Board. Part of the Transceiver.
XCDR
Full-rate Transcoder. The XCDR is the digital signal

processing equipment required to perform GSM-defined
speech encoding and decoding. In terms of data
transmission, the speech transcoder interfaces the 64 kbit/s
PCM in the land network to the 13 kbit/s vocoder format used
on the Air Interface. See also RXCDR.
XCDR board
The circuit board required to perform speech transcoding at

the BSS or (R)XCDR). Also known as the MSI (XCDR)
board. Interchangeable with the GDP board.
XFER
Transfer.
XID
eXchange IDentifier.
xterm
X terminal window. A terminal emulator program for the X

Window System. A user can have many different invocations
of xterm running at once on the same display, each of which
provides independent input and output for the process
running in it (normally a shell).
X Window
A specification for device-independent windowing operations

on bitmap display devices.
ZC
Zone Code. Part of the RSZI. The ZC identifies a regional

subscription zone as a pattern of allowed and not allowed
location areas uniquely within a PLMN.
ZC
774

68P02901W01-M
02 May 2003
Index

02 May 2003
68P02901W01-M
I1
GSR6 (Horizon II)
I2

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Numbers
Bill Of Materials, BOM, 431

billing centre, 246
2 Mbit/s link, 253
BOM, bill of materials, 431
2-site repeat pattern, 250
bridge, PCI to PCI, 344
4 to 2-wire hybrid, 251
broadcast control channels

FCCH, 245
SCH, 245
64 kbit/s link, 243
Broadcast Control Channels (BCCH), 245
Access Grant CHannel (AGCH), 245

add and delete option, 243
Advanced load handover management, 282
Advanced load management for EGSM carriers, 564
air interface, 34
control, 321
radio channel, 256
BSC capacity, overview, 37
air interface (BSS to MS), 244

alarm, reporting, 455
alarm state, 453
alarms
colours, 455, 459
disk usage, 470
alarms icon, 458
alarms severity, icon colour, 459
allocating handover numbers, overview, 235
allocating TMSI numbers, overview, 236
architecture
network, hierarchical, 248
PCU, 344
associated control channel ID, 249
associated control channels, 245
FACCH, 245
SACCH, 245
audio quality, 223
AUthentication Centre, AUC, 234
authentication key, 234
B
background maps, 455
Base Station System (BSS)
configurations, 242
overview, 242
software functions, 243
BCCH, 420
BSC
interaction with MSC, 36
interfaces
to BTS, 319
to MSC, 258, 319
purpose and functions, 36
redundancy, 328
site configuration, 312
BSS, 35, 416
capacity, 311
fault management, 327
handover, overview, 321
links, overview, 34
network elements, overview, 34
network topology, 316
daisy chain with fork and return loop to chain,
317
daisy chain with fork and return loop to BSC,
317
drop and insert, 318
open ended daisy chain, 316
overview, 316
star (spoke), 316
operation and maintenance, 47
overview, 34
redundancy, 327
site configurations
BSC, 312
BTS, 312
flexibility, 310
introduction, 310
BSS definition, 44
BSS interfaces, 244
A interface, 244
Abis interface, 244
Lb interface, 320
BSS mobile application part, 244
BSS object, 463
BSS software feature, Enhanced GDP provisioning,
GSR6, 550

02 May 2003
68P02901W01-M
I3
GSR6 (Horizon II)
BSS software features

1900 MHz Horizonmacro, GSR5.1, 545
3646, GSR6, 548
4420, 566
4471, 566, 570
850 MHz frequency range, GSR5.1, 545
advanced load management for EGSM carriers,
GSR6, 564
basic MPROC redundancy, GSR6, 557
BSS overload protection, GSR5, 536
BSS processing of suspend message, GSR5.1,
543
BTS concentration call priority handling, GSR5,
541
BTS concentration resource optimization for
handovers, GSR5, 540
call downgrade on CIC mismatch, GSR6, 552
Clean install (E3x00), GSR6, 560
code corruption immune design, GSR5, 539
CS3, CS4 and 32 kbits/s TRAU, GSR5.1, 544
dynamic allocation of RXCDR-BSC circuits,
GSR5, 538
4443, 566, 568
enhanced BSC capacity phase 2, GSR6, 558
enhanced MMI link device warnings, GSR5, 542
enhanced power outage recovery, GSR5, 540
enhanced XBL, GSR5, 538
GPROC fast reset, GSR5.1, 545
GPROC function pre-emption, GSR5, 542
GPRS PCU recovery on last GSL failure, GSR6,
553
handover parameter, GSR5, 540
Horizonmicro2/Horizoncompact2 generic BTS
software, GSR5, 539
improved MPROC software failures detection and
recovery, GSR6, 558
improved MTL load balancing, GSR5, 540
Inter Radio Access Technology (RAT) 2G to 3G
handover, GSR6, 559
Introduction, 53
link utilization improvements, GSR6, 563
Multiple GPRS carriers per Cell, GSR6, 549
Network controlled (NC1 and NC2) cell
reselection, GSR6, 554
optimized power control, GSR5, 541
parallel cage enable, GSR5, 542
per neighbour area for adaptive handovers,
GSR5, 541
propogate TSC changes to all timeslots, GSR5,
539
receive antenna VSWR and radio loopback test,
GSR5, 537
Release 1.1.1.0, 54
Release 1.1.2.0, 56
Release 1.1.2.1, 57
Release 1.1.2.2, 58
Release 1.1.2.3, 59
I4
Release 1.2.0.0, 510

Release 1.2.0.3, 512
Release 1.2.2.0, 513
Release 1.2.2.2, 514
Release 1.2.2.3, 515
Release 1.2.3.0, 516
Release 1.3.0.x, 518
Release 1.4.0.0, 521
Release 1.4.0.1, 522
Release 1.4.0.6, 523
Release 1.4.0.7, 524
Release 1.4.1.1, 525
Release GSR2, 527
Release GSR3, 529
Release GSR4, 532
Release GSR5, 536
Release GSR5.1, 543
Release GSR6, 547
single BCCH for dual band cells, GSR5, 539
SMS CB upgrade, GSR5, 537
support for E1/T1 conversion, GSR5, 539
support for frame erasure rate statistic, GSR5,
541
support for the MTL stat, GSR5, 541
temporary block flow, GSR6, 561
unequip of TCU/CTU cabinets, GSR5.1, 545
BSSAP, 244
BSSMAP, 244
BTS
interfaces
to BSC, 319
to MS, 259, 320
radio types, 38
RCU, DRI, 419
redundancy, 328
site configuration, overview, 312
C
C7, 230, 264
call control functions, overview, 230
call handling, overview, 237
call management, functional layering, 255
capacity
BSS, 311
GSM system, overview, 250
CBC, 246
CBL, 425
XCDR, 26
Cell Broadcast Centre (CBC), 246

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
daisy chain
open ended, 316
with fork and return loop to BSC, 317
with fork and return loop to chain, 317
Cell Broadcast CHannel (CBCH), 245

cell configuration, logical devices, 421
channels
logical, overview, 244
logical types, overview, 244
physical, overview, 244
data channels, 245

data communication, overview, 224
database schema
definition, 441
size, 441
chassis, PCU, 346

CM MIB, 450
automatically created objects
MMS, 467
NESoftware, 467
source, 467
SWInventory, 467
TRX, 467
definition, 460
DBMS, 437
DCS1800, radio types, 38
DCS1800 channels, 286
DCS1800 frequencies, 286
dedicated control channels, 245
SDCCH, 245
co-channel interference, 250

coding schemes, software features, 338
common control channels, 245
AGCH, 245
CBCH, 245
PCH, 245
RACH, 245
definitions
E1 link, 253
T1 link, 253
device mgt, 438
digital communication, 223, 249
digital networks, overview, 222
CommsLink object, 463
Digital Signal Processor (DSP), 223
communication link, 34
digital switching matrix, overview, 36
Compress all BTS objects at the BSC, feature,

GSR6, 565
Direct Transfer Application Part (DTAP), 244
confidentiality
signalling information, 224
user data, 224
discontinuous reception, 322

discontinuous transmission, 322
configuration objects, 462
Distribution of Motorola manuals, 15

Available formats, 15
Ordering manuals, 15
Updating manuals, 15
configurations, BSS site, introduction, 310
Documentation coding, 14
configuration mgt, 438
containment, managed objects, 418

control, functions, 350
control channels
associated control channels, 245
broadcast control channels, 245
common control channels, 245
dedicated control channels, 245
controlling LAIs, overview, 235
controlling MSRNs, overview, 235
D
D channel, 224
downlink, 421
DPROC, 345
(PICP), 345
(PRP), 345
DRI, 419, 420
dropped calls, 223
DTAP, 244
dynamic adaptation of coding schemes, software
features, 338
E
E1, PMC, 346
E1 link, definition, 253
02 May 2003
68P02901W01-M
I5
GSR6 (Horizon II)
EGSM to EGSM handovers, 282
frequency reuse, overview, 223
EGSM900, radio types, 38
functional layering, 255
EIR, 25, 221
Emergency caller location, LCS, 252, 556
functions
control, 350
MSC, overview, 228
PCU system, 350
PSP, 344
radio, 350
SGSN, 350
emergency calls, overview, 230
future system, Motorola GSM, 210
electrical interfaces, standardized, overview, 248

EM proxy process, 451
EM sub schema, 441
enhanced frequency hopping, 29

Enhanced GPRS One Phase Access, feature, GSR6,
564
enhanced GPRS one phase access, software
features, 339
environment, PCU, 333
equipment identity, mobile, international, 221
equipment identity register, overview, 233
Equipment Identity Register (EIR), 221
ethernet, 432
ethernet support, 440
event interface, 438
event/alarm mgt, 438
expert front panel, 412
extrapolation algorithm, 223
F
Fast Associated Control CHannel (FACCH), 245
fault management, BSS, 327
fault tolerance
Motorola GSM, 29
PCU, 346
features, PCU, 334
features summary, PCU, 335
frequency
reuse
2-site 6-sector, 325
4-site, 325
introduction, 324
reuse, 9-site, 324
synchronization, 323
Gaussian Minimum Shift Keying (GMSK), 244, 247

Gb
interface, 349
processes, 351
Gb interface, software features, 340

Global System for Mobile Communications (GSM),
introduction, 23
A Interface AUTO, 73
B Interface Byte, 77
C CW, 710
D Interface DYNET, 718
E EXEC, 722
F Interface Full Rate, 725
G Interface GWY, 728
H Interface Hyperframe, 730
I IWU, 731
k KW, 735
L1 LV, 735
M MUX, 738
N/W nW, 743
O Overlap, 745
PA PXPDN, 747
QA Quiesent mode, 753
R RXU, 753
S7 SYSGEN, 758
T TxBPF, 765
U UUS, 770
V VTX host, 771
W WWW, 773
X X Window, 774
ZC, 774
GMSK, 244, 247
GPROC2, 416
Frequency Correction CHannel (FCCH), 245

frequency hopping of PDCH, software features, 340
I6
GPRS
network architecture, 331
overview, 329
GPRS radio channel allocation, software features,
336

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
graphic objects, maps, 461
increased capacity, overview, 222
GSM
interfaces, overview, 248
network, 415
radio channel, 243
radio interface, noise robustness, 251
sub-systems, 246
information flow, OMC and NEs, 430
GSM frequencies and channels, 266

EGSM frequencies, 282
ESGM channels, 283
GSM850 channels, 267
GSM850 frequencies, 266
GSM900 channels, 275
GSM900 frequencies, 274
GSM900, radio types, 38
GSN
overview of complex, 330
INFORMIX, 441
infrastructure, 250
inter-MSC handovers, 232
interfaces
BSC to BTS, 319
BTS to MS, 259, 320
Gb, 349
GSM, overview, 248
GUI, command line, 411
MSC to BSC, 258, 319
PCU, 347, 348
PCU-BSC, 348
protocol layering, 319
redundancy, 327
standardized, 254
standardized electrical, overview, 248
summary, 257
GUI
command line interface, 414
configurations, 443
GUI front panel, 412
processors, 443
interference
co-channel, 250
co-channel and adjacent channel, 223, 249
GUI client, SPARCstation 5, 448
International Mobile Subscriber Identity (IMSI), 221
GUI server, GUI client, 452
introduction
GPRS, 329
GSN complex, 330
PCU, 329
H
handover, 249
overview, 321
handover control, 421
handportable, 224
International Mobile station Equipment Identity (IMEI),

221
Introduction to Motorola GSM documentation, 13

introduction to the system processor, 435
ISDN, 210, 256
ISDN compatibility, overview, 248
hardware devices, 464

hierarchical network architecture, 248
hierarchy, network, 47
HLR, 25, 221
HLR data, 234
HLR master database, overview, 234
home location register, overview, 233
I
IMEI, 221
IMSI, 221
In Service (INS) state, 453
L
LAPD, 265
LCS, LoCation Services, 252, 556
link, types, 425
link quality, 223, 249
links
maps, 455
overview, 34
physical/logical, 423
local registration and call handover, overview, 231
Location Services (LCS), 252, 556
logical channels, 243
overview, 244
types, overview, 244
02 May 2003
68P02901W01-M
I7
GSR6 (Horizon II)
logical groups, 462

hardware devices, 464
logical links, 465
radio frequency, 466
Motorola manuals
CDROM, 15
Extranet, 15
Hardcopy, 15
logical links, 465

OML, MTL, RSL, XBL, CBL, 425
Motorola OMC, typical configuration, 431
Motorola network specifications, introduction, 211

MPROC, 344
(PSP), 344
lost calls, 223, 249

low bit rates, non-voice data, overview, 250
MS
interface to BTS, 259, 320

power saving, overview, 250
tracking, overview, 250
MS flow control, software features, 341

MS to MS calls
MS to MS
different PLMN different country, 241
different PLMN same country, 240
same PLMN, 239
overview, 239
maintenance, Motorola GSM, 29

MAP, 230, 256
Map, automatically created objects
Map, 468
MapLink, 468
MapNode, 468
MS to PSTN subscriber, overview, 237

MSC
interaction with BSC, 36
interface to BSC, 258, 319
site configurations, overview, 312
map, 450
configuration, 454
links, 455
state changes, 455
MSC object, 463
Map display, map icons, 456
MSI, MMS, 418, 429
MapLink, 461
MSI object, 464
MapNode, 461
MSISDN, 221
maps, 453
background maps, 455
configuration objects, 460
graphic objects, 460
MTL, 425
MTP, 264
multiplexer, 427, 433
multiplexing, 243
maps icon, 446

measured parameters, 249
medium access mode, software features, 336
Message Transfer Link (MTL), 230
NC1, Nework Controlled cell reselectionLoCation

Services, 554
MMS, MSI, 418
NC2, Network Controlled cell reselection, 554
Mobile Application Part (MAP), 230, 256
NE definition, network element, 44
mobile services switching centre, 228

overview, 25, 228
mobile station, 224
overview, 220
network
devices, 429
hierarchy, 47
traffic capacity, 434
network architecture , GSM/GPRS/GSN, 331
Mobile Subscriber ISDN (MSISDN) number, 221
network configuration, 453
mobility management, functional layering, 255
Network Controlled cell reselection, NC1/NC2, 554
modem, 224, 246

module, information, subscriber, 221
I8
network elements
location register, overview, 25
overview, 34
68P02901W01-M
02 May 2003
GSR6 (Horizon II)
Network File System (NFS), 443

Network Management Centre, (NMC), 47
network management centre
functions, overview, 225
overview, 25
network map, 450
configuration, 454
network maps, 453
network object, 463
network status summary, 446
network topology
BSS, 316
daisy chain with fork and return loop to BSC,
317
daisy chain with fork and return loop to chain,
317
drop and insert, 318
open ended daisy chain, 316
star (spoke), 316
NFS (Network File System), 443
night concentration configuration, 449
NMC, 47
noise robustness, radio interface, overview, 251
non-stop-UX A22 IPM02, 440
non-voice data, low bit rate use, overview, 250
NSS, features, 446
Objects
Map, automatic creation of, 468
MapLink, automatic creation of, 468
MapNode, automatic creation of, 468
MMS, automatic creation of, 467
NESoftware, automatic creation of, 467
SWInventory, automatic creation of, 467
TRX, automatic creation of, 467
objects, source, automatic creation of, 467
OMC software features, 4475, 652, 653
OMC-R
basic configuration, 48
command line interface, 414
communication with GSM network, 44
configuration summary, 410
definition, 43
GUI client, 448
GUI front panel, 412
network management architecture, 47
Network management functions, 45
PCU management, 342
processes, 438
SPARCstation 5, 448
OMC-R definition, 44
OMC-R, NSS feature, 446
OMC-R database, 441
OMC-R functions, 416
OMC-R object, 463
OMC-R software features
adaptive handover, GSR5, 636
Applix 4.41 upgrade, GSR5, 639
Bay level cal default data, GSR5, 639
BTS concentration, GSR5, 635
cell parameter import/export, GSR5, 639
cell Xchange, GSR6, 651
changing NE ID of Assoc_BSSs or
Assoc_RXCDRs, GSR5, 640
coincident multiband boundaries, GSR5, 636
completion of OMC support for Horizonmacro,
GSR5, 638
CS3, CS4 and 32 kbits/s TRAU, GSR5.1, 644
datagen support, GSR5, 641
DRI combiner operability improvement, GSR5,
638
dynamic trace call flow control, GSR5, 637
EAS relay MMI control for Incell, M-Cell and
Horizon, GSR5, 635
enable cyclic neighbour statistics, GSR6, 650
enhanced circuit error rate monitor, GSR6, 648
enhanced SDCCH to TCH assignment, GSR5,

02 May 2003
68P02901W01-M
I9
GSR6 (Horizon II)
640
expansion/de-expansion, GSR5, 643
flexible neighbour cell processing, GSR5, 637
geographic command partitioning and region
support, GSR6, 647
GPROC fast reset, GSR5.1, 644
increased capacity OMC-R, GSR5, 642
increased OMC-R neighbour stats, GSR5, 641
increasing maximum number of trunks per BSC,
GSR5, 642
intelligent congestion relief, GSR5, 635
interrogation of NHA with GSM OMC-R EM,
GSR5, 639
Introduction, 63
network expansion batch capability, GSR5, 641
NHA support maximum size GSM OMC-R,
GSR5, 639
OMC-R GUI supportfor PCU device object,
GSR5, 641
OMC-R GUI usability, GSR5, 641
OMC-R GUI usability for large network support,
GSR6, 649
online network expansion - phase 3, GSR6, 650
optimized power control, GSR5, 635
PCU alarms detected by HSC, GSR5, 643
propogation after audit, GSR5, 635
proxy cell autocreation, GSR5, 637
proxy cell import/export, GSR5, 638
Q3 support, GSR5, 638
Release 1.1.2.0, 64
Release 1.1.2.1, 65
Release 1.1.2.2, 66
Release 1.1.2.3, 68
Release 1.1.2.4, 610
Release 1.2.0.0, 611
Release 1.2.2.1, 614
Release 1.2.2.2, 617
Release 1.2.3.0, 618
Release 1.3.0.0, 619
Release 1.4.0.0, 620
Release 1.4.0.1, 622
Release 1.4.0.6, 624
Release 1.4.0.7, 625
Release 1.4.1.0, 626
Release GSR2, 628
Release GSR3, 631
Release GSR4, 632
Release GSR4.1, 633
Release GSR5, 634
Release GSR5.1, 644
Release GSR6, 646
Release GSR6 (Horizon II), 652
removal of clear stats command, GSR5, 643
reporting the results of alarms recovery action,
GSR5, 636
support for Vanguard 6455 router, GSR5, 643
I10
support of BCCH and SDCCH for EGSM, GSR5,

636
system upgrade, GSR5, 640
unequip of TCU/CTU cabinets, GSR5.1, 645
Vanguard software upgrade support, GSR5, 643
web MMI, GSR5.1, 644
hardware impact, 445
single platform processor, 48
OML, 425
one phase access, software features, 339
operating system, non-stop-UX A22 IPM02, 440
operations and maintenance centre, overview, 25
OSI, 262
Other manuals, 116
INFORMIX manuals, 116
Printer manuals, 116
SPARC E3000/E3500, 116
SPARCstation manuals, 116
X.25 manuals, 116
Out Of Service (OOS) state, 453
Overview of Motorola manuals, 16
Manuals types, 16
P
packet switch, 427, 433
PADS, X.25, 246
Paging CHannel (PCH), 245
part, application
BSS mobile, 244
direct transfer, 244
mobile, 230, 256
password protection, security management, 219
PATH, physical link, 424
PCI to PCI bridge, 344
PCS1900 frequencies and channels, 2106
PCS1900 channels, 2106
PCS1900 frequencies, 2106

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
PCU, 332
architecture, 344
chassis, 346
environment, 333
fault tolerance, 346
features summary, 335
interfaces, 347, 348
introduction of PCU, 463
list of features, 334
management, 342
overview, 329, 332
purpose, 342
roadmap features, 334
summary, 333
system functions, 350
PRP, 345
processes, 351
PSA, definition, 469
PSP, functions, 344
PSTN, 246
PSTN subscriber to MS, overview, 238
PXPDN, 433
Q
Q3 agent, 44
quality of reception, 249
PCU architecture, PPB, 344

PCU load balancing & sharing, software features,
341
PCU processes, PRP processes, Gb processes,

351
radio, functions, 350
PCU system, overview, 342
radio channel air interface, 256
PCU-BSC, interface, 348
radio channel bit rate, 244
performance measurements, 430
radio frequency, 466

radio planning, 250
performance mgt, 438

Periodic Supervision of Accessibility (PSA), 469
physical channels, overview, 244
Random Access CHannel (RACH), 245

RCU, 419
physical layer, functional layering, 255
RDBMS, 441
physical link, PATH, 424
received level, 249
PICP, 345
PM sub schema, 441
PMC, E1, 346
point-to-point GPRS service, software features, 335
power budget, 421
power control, 421
overview, 322
power control: uplink/downlink, software features,
340
redundancy
BSC, 328
BSS, 327
BTS, 328
interfaces, 327
RF carrier, 327
RXCDR, 328
related commands and parameters, security
management, 219
remote login, 438
Remove support for collocated BSC, feature, GSR6,
565
power saving, MS, overview, 250

PPB, PCU architecture, 344
Private eXchange Packet Data Network, PXPDN,
433
resource management, 259, 320

RF carrier, redundancy, 327
RSL, 425
procedures, handover, 249

protocol stacks, TCP/IP, Ethernet, X11, X25, 432
protocols, network, 262
radio resource management, functional layering, 255
RTF, 420
BCCH, 420
non-BCCH, 420

02 May 2003
68P02901W01-M
I11
GSR6 (Horizon II)
software features
coding schemes, 338
dynamic adaptation of coding schemes, 338
enhanced one phase access, 339
frequency hopping of PDCH, 340
Gb interface, 340
GPRS radio channel allocation, 336
medium access mode, 336
one phase access, 339
PCU load balancing & sharing, 341
PCU MS flow control, 341
point-to-point GPRS service, 335
power control: uplink/downlink, 340
support of mobile classes, 337
two phase packet access, 339
RXCDR, 26
functions, 416
operation and maintenance, 47
redundancy, 328
RXCDR object, 463
S
SCCP, 264
security management, password protection, 219
software load mgt, 438
security procedures, overview, 231
SPARCstation, 48
services, ISDN-type, 224
SPARCstation 5/IPX, 448

disk size, 448
SGSN, functions, 350

short message service, overview, 231
signaling performance, 223, 249
signalling link protocols, overview, 265
signalling links, summary, 257
specifications
OMC-R, 211
receiver, 214
transmitter, 217
speech transcoder, 26
remote, 26
SQL, 441
Stand-alone Dedicated Control CHannel (SDCCH),
245
signalling system 7, 230, 264

C 7, 248
standardized electrical interfaces, overview, 248
SIM, 221
star (spoke), network topology, 316
single BCCH for dual band cells, feature

dependencies, 546
single platform processor, 48
state changes
admin and operational, 457
on map display, 455
status summary window, 453
site configurations
BSC, overview, 312
BTS, overview, 312
CELL, 419
introduction, 310
MSC, overview, 312
site definition, 417
sub schema, EM, PM, 441

subscriber identity, mobile
international, 221
ISDN, 221
temporary, 221
Subscriber Information Module (SIM), 221
site definition, 44
SITE object, 463
Slow Associated Control CHannel (SACCH), 245
smart card, 221
software elements, system processor, 438
I12
Summary of Motorola manuals, 18

Installation and configuration manuals, 114
Maintenance information manuals, 114
Operating information manuals, 113
Service manuals-BSS, 18
Service manuals-GPRS, 111
Software release notes, 115
System information manuals, 112
Technical description manuals, 113

68P02901W01-M
02 May 2003
GSR6 (Horizon II)
support of mobile classes, software features, 337
transceiving, DRI/RTF groups, 420
switching matrix, 243
transcoder, speech, 26
synchronization, 251
transcoding, 243
location, 39
Synchronization CHannel (SCH), 245
transmission, discontinuous, 322
system impact, security management, 219
transport layer, functional layering, 255
system planning, Motorola GSM, 29
trunking, 250
system processor, 212, 435

software elements, 438
configurations, 212
trustworthiness, 249
two phase packet access, software features, 339
systems advantages, Motorola GSM, 29
uplink, 421
T1 link, definition, 253
TBF, 561
TCP/IP, 440
validation exercise, 247
technological requirements, 247
visited location register, overview, 235
teleservices, 249
overview, 224
VLR, 25, 221
Temporary Mobile Subscriber Identity (TMSI), 221
terrestrial circuit device management, overview, 36

The CM MIB, 447
WAN, 432
timing adjustment, 251
wide area network, 432
timing advance, overview, 323
TMSI, 221
topology, BSS network. See network topology
tracking, MS, overview, 250
traffic capacity, network, 434
speech channels
full rate, 245
half rate, 245
traffic channels, 245
X.11, 432
X.21 address, 427
X.25, 227, 265, 432
X.25 PADS, 246
X25, 265
XBL, 425

02 May 2003
68P02901W01-M
I13
GSR6 (Horizon II)
I14

68P02901W01-M
02 May 2003

System Informatio - GSM Overview (Motorola)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

System Informatio - GSM Overview (Motorola)

Uploaded by

Copyright:

Available Formats

CHAPTER 1

GSM SYSTEM MANUAL

GSR6 (Horizon II)

GSM SOFTWARE RELEASE 6 (Horizon II)

Software Release GSR6 (Horizon II)

System Information: GSM Overview

GSR6 (Horizon II)

Copyrights, notices and trademarks

and MOTOROLA are registered trademarks of Motorola Inc.

System Information: GSM Overview

GSR6 (Horizon II)

Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Motorola manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GMR amendment record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to Motorola GSM documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Distribution of Motorola manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of Motorola manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Summary of Motorola manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: GSM Overview

GSR6 (Horizon II)

Overview of the Motorola GSM system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: GSM Overview

GSR6 (Horizon II)

Operations and maintenance centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mobile services switching centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Base station system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GSM subsystems (non-network elements) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: GSM Overview

GSR6 (Horizon II)

GSM system features and goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: GSM Overview

GSR6 (Horizon II)

GSM frequencies and channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DCS1800 frequencies and channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCS1900 frequencies and channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Base station system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: GSM Overview

GSR6 (Horizon II)

BSS standardized interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Radio system and control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cell system radio channel reuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

General Packet Radio Service (GPRS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Packet control unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: GSM Overview

GSR6 (Horizon II)

PCU system and control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introducing the Motorola OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OMC-R network management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The OMC-R in GSM network management architecture . . . . . . . . . . . . . . . . . . . . . . . . . .

System Information: GSM Overview

GSR6 (Horizon II)

The OMC-R system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OMC-R configuration summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The OMC-R user interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The command line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The OMC-R in a GSM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BSS and RXCDR configuration (SITES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DRI/RTF groups - transceiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Links in a GSM network: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Physical links - PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .